quantmodel — Require durable searchable task note + changelog entry for every completed task

Objective

PR comments were unreadable — reviewer could not tell what task was based on details there. Earlier research/findings Markdown notes actually detailed in plain English what the task was about and what was accomplished. Make that durable, searchable, and enforced by the pipeline, with the same note surfacing in the changelog (docs/results.html / docs/site-data/results.json) and duplicated into the PR Summary.

Approach

Extended the pipeline completion node contract in research/pipeline/graph.json to require result_entry_path (research/results/<task-id>.md) and result_entry_summary (one-paragraph plain-English summary duplicated into the PR).
Updated research/pipeline/prompts.json completion prompt to instruct agents to write that Markdown note with YAML front matter (id/title/summary/category/completed_at) plus body sections Objective/Approach/Files changed/Validation/Results, then rebuild with python3 -m research.reports.results or build --render.
Added runtime enforcement in research/pipeline/runtime.py: completion now validates result_entry_path shape and that the file exists at repo_root before reaching awaiting_shipping.
Added artifact contract changelog_entry in research/pipeline/artifact_contracts.json requiring research/results/{result_id}.md, docs/site-data/results.json, docs/results.html, docs/results/{result_id}.html and python3 -m research.reports.results + static check. Moved completion out of generic_change.
Updated offline verifier research/pipeline/verify.py to exercise the new completion fields, ensure the durable note exists for every route, and route repo_root correctly for file checks.
Made PRs self-explanatory in research/scripts/pr_body.py (--result-file) and research/scripts/open_pr.sh (auto-discovers research/results/<task-id>.md from --task-id and duplicates its summary into ## Summary with a Task note: <path> footer). The same note file is what the changelog renders, so search is git grep on Markdown, PR body has a quick duplicate, and docs/site-data/results.json is the changelog source.
Updated docs: research/results/README.md (pipeline MUST), docs/site-data/README.md (results.json payload).

Files changed

research/pipeline/graph.json — completion required_output now includes result_entry_path + result_entry_summary
research/pipeline/prompts.json — completion prompt with durable note + rebuild instructions
research/pipeline/runtime.py — completion semantic + file-existence check (repo_root aware)
research/pipeline/artifact_contracts.json — new changelog_entry contract, completion removed from generic_change
research/pipeline/verify.py — fixture completion note, repo_root plumbing, new overrides
research/scripts/pr_body.py — --result-file support, _extract_result_note, duplicate into Summary + Task header
research/scripts/open_pr.sh — --result-file + auto-discover from --task-id
research/results/README.md — pipeline contract note
docs/site-data/README.md — results.json changelog payload description
research/results/qm-9kwp.md — this durable note (example of the new contract)

Validation

python3 -m research.pipeline validate
# → {"status":"passed", "nodes":28, "edges":38, "graph_hash":"sha256:6802..."}

python3 -m research.pipeline verify --offline
# → {"status":"passed", "node_coverage":{"covered":28,"total":28}, ...}

python3 -m research.reports.results
# → writes docs/site-data/results.json, docs/results.html, docs/results/qm-9kwp.html

python3 research/scripts/check_static_reports.py docs
# → static site checks pass (progress/coverage linkage intact)

# PR helper duplicate check
python3 research/scripts/pr_body.py --summary "dummy" --considerations "c" --changes "c" --validation "c" --risks "None" --task-id qm-9kwp --result-file research/results/qm-9kwp.md --output /tmp/body.md
grep -q "Task note:" /tmp/body.md && echo "PR duplicate ok"

git grep -l "durable searchable task note" research/results
# → research/results/qm-9kwp.md (proves git-grep searchability)

Results

Every future pipeline completion now has:

A searchable Markdown file at research/results/<task-id>.md (front matter + plain English). git grep finds it without opening a PR.
A PR Summary that duplicates that file's summary with a Task note: research/results/<id>.md link — instant readability.
A changelog entry in docs/site-data/results.json + docs/results.html + docs/results/<id>.html rebuilt deterministically via research.reports.results.

Legacy research/findings/*<em>/</em>.md notes remain valid and are referenced via source_report pointer instead of duplicated.

Risks / follow-ups

Existing tasks that already passed completion will not retroactively gain a result file; they remain searchable only via PR bodies/commit messages. A backfill is not required unless audit finds high-value tasks missing.
The file-existence check in completion fail-closes the run if the agent forgets to write research/results/<id>.md — correct behavior, but agents must remember to write before submitting the final node.
--result-file auto-discover in open_pr.sh only triggers when --task-id matches a file that exists on disk at PR creation time; manual --result-file may be needed for out-of-directory runs.