docs(0.4.0): reconcile assistance milestone and Medic sidecar

[mberrys]

What changed

Approved 2026-09-23 reconciliation for Loop 0.4.0 — Evidence-Grounded Correction Assistance. Medic is a separate cross-milestone bleed-reconstruction sidecar, and its delivery, research gates, and integration are expressly NOT dependencies for Loop 0.4.0 exit.

• Replace stale 0.4.0 milestone text that still promised NL JobSpec compilation/job context with the actual selected-finding → explanation → safe proposal → canonical plan → existing governed approval vertical.
• Link the single exit issue [0.4.0-D] Qualify evidence-grounded finding-to-approved-plan vertical on an exact SHA #686; actual executable arc issues are [0.4.0-A] Grounded finding explanation, evidence context, safe next actions, and timeline #584, [0.4.0-B] Assemble deterministic multi-step correction plans from selected findings #590, and [0.4.0-C] Optional provider boundary, injection defense, provenance, and evaluation #371.
• Identify [0.3.0] A write job after an Action List apply is finished Stale before it runs #662, [0.3.0-C] Record immutable PDF operation history with approvals, provenance, and rollback #32, [0.3.0] No check inspects formal GWG 2022/2024 sheetfed or packaging conformance #664 and [0.3.0] Close architecture contracts D1–D5 before qualification #675/PR Close architecture contracts D1–D5 (#675) #679 as inherited 0.3.0 correctness/truth limits, not duplicate 0.4.0 feature issues.
• Carry Medic non-gating/cross-milestone policy into the 0.5.0 description and roadmap.
• Correct advisory milestone manifest mapping: existing live milestone Validate output-intent and ICC-profile presence, identity, and color-space consistency #12 is titled 0.5.0 and currently has 0.6.0 description/issue assignments; old Add decoded-stream, decompression-ratio, memory, depth, and execution budgets #11 is not an assignable 0.5.0 milestone. Leave 0.6.0 numeric ID pending creation/reconciliation rather than guessing an ID.
• Document safe sync-and-migrate order in docs/github-milestones/README.md.

GitHub issue edits performed separately

• [0.4.0-A] Grounded finding explanation, evidence context, safe next actions, and timeline #584 — catalog-driven offline explanation, typed non-success states, remove future 0.8.0-S10: Operator documentation, first-run onboarding, grounded explanation guides, and sample corpus #477 as release prerequisite.
• [0.4.0-B] Assemble deterministic multi-step correction plans from selected findings #590 — no 0.5.0 JobSpec prerequisite; [0.4.0-C] Optional provider boundary, injection defense, provenance, and evaluation #371 optional; registry/plan parity and [0.3.0] A write job after an Action List apply is finished Stale before it runs #662 write-path proof.
• [0.4.0-C] Optional provider boundary, injection defense, provenance, and evaluation #371 — full replaceable provider contract with consent, provenance, hostile tests, Medic sidecar boundary.
• [0.4.0-D] Qualify evidence-grounded finding-to-approved-plan vertical on an exact SHA #686 — new exact-SHA 0.4.0 release qualification owner; Medic explicitly non-gating.

Important: milestone sync remains a separate write

This PR edits checked-in source of truth, not GitHub milestone REST metadata or issue milestone assignments. The currently available GitHub connector cannot PATCH or create milestone objects. scripts/github/sync_milestones.py must be dry-run and applied by a GitHub-authenticated operator after review/merge. That script matches by title, updates descriptions, and creates the absent 0.6.0 milestone, but does NOT remap issues.

After it creates a distinct 0.6.0 milestone, migrate the pre-existing 0.6.0 cohort off #12 into that new ID; only then move the 17 active 0.5.0 cohort out of #10 into #12. Verify that no 0.6.0 work remains on 0.5.0, #10 retains only #584/#590/#371/#686 plus its closed historical entries, and milestone title/description/issue membership agree. Do not use stale manifest numeric IDs for remote writes.

Proof / review

• Changes are documentation, tracking manifest, and release-scope clarification only; no source-code, protocol, or runtime feature change.
• changes/chore-040-evidence-grounded-medic-sidecar.md records this scope correction.
• Review the repo documentation truth / milestone manifest validation checks on the PR exact SHA.
• No CI result, remote milestone migration, or GitHub live-description update is claimed as complete in this PR.

Refs #584. Refs #590. Refs #371. Refs #686.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}