diff --git a/MILESTONES.md b/MILESTONES.md
index 07a593c..a976265 100644
--- a/MILESTONES.md
+++ b/MILESTONES.md
@@ -444,7 +444,7 @@ before any design or implementation:
 
 ### M7: Real Provider Integration
 
-- State: current
+- State: done
 - Outcome: Enable an operator to turn an approved plan into real landed work — a real agent
   driver doing real edits, a real execution host with proven confinement, real Forge/GitHub
   landing, and real work-source intake — recorded in durable, inspectable records under
@@ -509,6 +509,14 @@ before any design or implementation:
      exit. Lifecycle-edge split: no codex-plugin-cc-style lifecycle edges (broker, interrupt,
      cleanup, Windows process-tree) gate M7 exit; all of them gate the transport ADR and,
      through it, the freeze.
+     - **Exit evidence — met 2026-07-04.** EVRUN-partial merged as jig PR #45 (squash
+       `707d2114f`): a real work-source → Forge → records-integrity run against the private
+       `jig-smoke-target` sandbox with a scripted agent leg (real GitHub Issues intake, real
+       `open-pr` landing, HMAC integrity sidecar verified), committed as the citable record
+       `docs/design/evidence/2026-07-04-evrun-partial-smoke.md` under jig's evidence convention.
+       This satisfies the D-EXIT Option A condition, so M7's `State` is flipped to `done` above.
+       EVRUN-full (the Codex-driven agent leg) remains the named debt retired by the post-M7
+       Codex-transport track (N1); it is not a reopening of M7 exit.
   2. **Packaging (N2) — internal SDK boundary now, no publishing.** Rationale: extensibility and
      single-responsibility; the SDK's first-party consumers are jig's CLI and a future MCP
      surface. Packages stay `private: true`; the posture can flip to public later, and no
diff --git a/ROADMAP.md b/ROADMAP.md
index ea08a92..baa2d06 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -102,8 +102,10 @@ parallel. The current sequence is tracked in [`MILESTONES.md`](./MILESTONES.md).
   Per the 2026-07-04 post-M7 sequencing decisions (`MILESTONES.md`), the tail is now
   replanned rather than open-ended: a Codex-transport evidence-capture track and an internal
   SDK packaging boundary (no publishing) are authorized to start; a first-party TUI/dashboard
-  stays an extension-point-only non-goal; and any v0 contract freeze still waits on M7 exit
-  evidence plus the packaging and transport decisions.
+  stays an extension-point-only non-goal. M7's exit evidence landed 2026-07-04 (Jig PR #45,
+  a real work-source -> Forge -> records-integrity run), closing M7 as `done`; any v0
+  contract freeze still waits on the transport and packaging design decisions, not on M7
+  exit evidence.
 - **References (curated):**
   - Product (own, drafted): `jig/docs/product/jig.md`, `guarantees.md`, `use-cases.md`,
     `concepts.md`.
diff --git a/profile/README.md b/profile/README.md
index 5d80578..46dafca 100644
--- a/profile/README.md
+++ b/profile/README.md
@@ -54,14 +54,16 @@ The shared vocabulary is intentionally small:
 
 ## Current Focus
 
-The current org focus is closing the M7 Jig spine and replanning the remaining tail work now that
-Product, Technical Design, and Planning contract shapes are seeded. M4 seeded `design-to-plan` so
-approved technical designs can become Jig-ready execution plans without re-deciding product or design
-scope.
-
-Jig's M7 real-provider spine is merged through PR #39 at `3b3d224`: real agent/host, Forge,
-work-source, and records-integrity behavior are exercised behind the same contracts. Remaining tail
-items are gated for replanning before implementation.
+The current org focus has moved past closing the M7 Jig spine into the post-M7 workstreams that
+replan its tail, now that Product, Technical Design, and Planning contract shapes are seeded. M4
+seeded `design-to-plan` so approved technical designs can become Jig-ready execution plans without
+re-deciding product or design scope.
+
+Jig's M7 real-provider spine is merged through PR #39 at `3b3d224`, and M7 closed `done` on
+2026-07-04 once its exit evidence (Jig PR #45, a real work-source -> Forge -> records-integrity
+run) landed: real agent/host, Forge, work-source, and records-integrity behavior are exercised
+behind the same contracts. Remaining tail items (Codex-transport evidence, packaging/SDK
+boundary, v0 contract freeze) proceed as their own gated workstreams.
 
 Start with [`define-product`](https://github.com/agentic-workflow-kit/define-product) for product
 intent and acceptance-criteria IDs, [`technical-design`](https://github.com/agentic-workflow-kit/technical-design)