dflow-sdd-ddd 0.15.0 → 0.16.0

package/lib/doc-shapes.json

@@ -53,6 +53,105 @@
             ["note","Resume Pointer","","6282e389a109b5f3"],
             ["comment","Resume Pointer","","5b3dcd00f70f0239"]
           ]
+        },
+        {
+          "number": 2,
+          "digest": "d0d9702bc58d71fb69e8faae01b209fdcca194ae83df02842e660dde035477fc",
+          "changes": [
+            {"kind":"reworded","from":["note","Checkpoint Log","","7ba7cd7e457fce40"],"to":["note","Checkpoint Log","","f0076376f5650ae1"]}
+          ],
+          "skeleton": [
+            ["field","spec-id"],
+            ["field","slug"],
+            ["field","status"],
+            ["field","created"],
+            ["field","branch"],
+            ["field","follow-up-of","optional"],
+            ["h2","Goals & Scope"],
+            ["h2","Phase Specs"],
+            ["column","Phase Specs","",1,1,"Phase"],
+            ["column","Phase Specs","",1,2,"Date"],
+            ["column","Phase Specs","",1,3,"Slug"],
+            ["column","Phase Specs","",1,4,"Status"],
+            ["column","Phase Specs","",1,5,"File Link"],
+            ["h2","Current BR Snapshot"],
+            ["column","Current BR Snapshot","",1,1,"BR-ID"],
+            ["column","Current BR Snapshot","",1,2,"Current Rule"],
+            ["column","Current BR Snapshot","",1,3,"First Seen (phase)"],
+            ["column","Current BR Snapshot","",1,4,"Last Updated (phase)"],
+            ["column","Current BR Snapshot","",1,5,"Status"],
+            ["h2","Lightweight Changes"],
+            ["column","Lightweight Changes","",1,1,"Date"],
+            ["column","Lightweight Changes","",1,2,"Tier"],
+            ["column","Lightweight Changes","",1,3,"Description"],
+            ["column","Lightweight Changes","",1,4,"Commit"],
+            ["h2","Checkpoint Log"],
+            ["column","Checkpoint Log","",1,1,"Timestamp"],
+            ["column","Checkpoint Log","",1,2,"Checkpoint"],
+            ["column","Checkpoint Log","",1,3,"Result"],
+            ["h2","Resume Pointer"],
+            ["comment","","","43746d19844776ca"],
+            ["note","Goals & Scope","","6bf4aa3e408ea8bc"],
+            ["note","Phase Specs","","5dff0b02b2fefdac"],
+            ["comment","Phase Specs","","60305a8c385cd40f"],
+            ["note","Current BR Snapshot","","6a432bf9bd86ac85"],
+            ["comment","Current BR Snapshot","","44a797a7db5f5224"],
+            ["note","Lightweight Changes","","673f6f4bda4182b3"],
+            ["comment","Lightweight Changes","","013165e8c56f2b73"],
+            ["note","Checkpoint Log","","f0076376f5650ae1"],
+            ["note","Resume Pointer","","6282e389a109b5f3"],
+            ["comment","Resume Pointer","","5b3dcd00f70f0239"]
+          ]
+        },
+        {
+          "number": 3,
+          "digest": "b8531afb23e1244c53e31d41a8566adfa53e68057165426b8252285aab4a1833",
+          "changes": [
+            {"kind":"reworded","from":["note","Lightweight Changes","","673f6f4bda4182b3"],"to":["note","Lightweight Changes","","3f9caac2c8fb4600"]},
+            {"kind":"reworded","from":["note","Checkpoint Log","","f0076376f5650ae1"],"to":["note","Checkpoint Log","","006cc4257a5c13f2"]}
+          ],
+          "skeleton": [
+            ["field","spec-id"],
+            ["field","slug"],
+            ["field","status"],
+            ["field","created"],
+            ["field","branch"],
+            ["field","follow-up-of","optional"],
+            ["h2","Goals & Scope"],
+            ["h2","Phase Specs"],
+            ["column","Phase Specs","",1,1,"Phase"],
+            ["column","Phase Specs","",1,2,"Date"],
+            ["column","Phase Specs","",1,3,"Slug"],
+            ["column","Phase Specs","",1,4,"Status"],
+            ["column","Phase Specs","",1,5,"File Link"],
+            ["h2","Current BR Snapshot"],
+            ["column","Current BR Snapshot","",1,1,"BR-ID"],
+            ["column","Current BR Snapshot","",1,2,"Current Rule"],
+            ["column","Current BR Snapshot","",1,3,"First Seen (phase)"],
+            ["column","Current BR Snapshot","",1,4,"Last Updated (phase)"],
+            ["column","Current BR Snapshot","",1,5,"Status"],
+            ["h2","Lightweight Changes"],
+            ["column","Lightweight Changes","",1,1,"Date"],
+            ["column","Lightweight Changes","",1,2,"Tier"],
+            ["column","Lightweight Changes","",1,3,"Description"],
+            ["column","Lightweight Changes","",1,4,"Commit"],
+            ["h2","Checkpoint Log"],
+            ["column","Checkpoint Log","",1,1,"Timestamp"],
+            ["column","Checkpoint Log","",1,2,"Checkpoint"],
+            ["column","Checkpoint Log","",1,3,"Result"],
+            ["h2","Resume Pointer"],
+            ["comment","","","43746d19844776ca"],
+            ["note","Goals & Scope","","6bf4aa3e408ea8bc"],
+            ["note","Phase Specs","","5dff0b02b2fefdac"],
+            ["comment","Phase Specs","","60305a8c385cd40f"],
+            ["note","Current BR Snapshot","","6a432bf9bd86ac85"],
+            ["comment","Current BR Snapshot","","44a797a7db5f5224"],
+            ["note","Lightweight Changes","","3f9caac2c8fb4600"],
+            ["comment","Lightweight Changes","","013165e8c56f2b73"],
+            ["note","Checkpoint Log","","006cc4257a5c13f2"],
+            ["note","Resume Pointer","","6282e389a109b5f3"],
+            ["comment","Resume Pointer","","5b3dcd00f70f0239"]
+          ]
         }
       ]
     },
@@ -599,6 +698,105 @@
             ["note","Resume Pointer","","6282e389a109b5f3"],
             ["comment","Resume Pointer","","5b3dcd00f70f0239"]
           ]
+        },
+        {
+          "number": 2,
+          "digest": "7d4a5014ba47bb069f170d5a1db2b96c9f4292bf2d87e00b104b7f6e47ad0970",
+          "changes": [
+            {"kind":"reworded","from":["note","Checkpoint Log","","359aef25b21362ca"],"to":["note","Checkpoint Log","","87725d2856e7692d"]}
+          ],
+          "skeleton": [
+            ["field","spec-id"],
+            ["field","slug"],
+            ["field","status"],
+            ["field","created"],
+            ["field","branch"],
+            ["field","follow-up-of","optional"],
+            ["h2","Goals & Scope"],
+            ["h2","Phase Specs"],
+            ["column","Phase Specs","",1,1,"Phase"],
+            ["column","Phase Specs","",1,2,"Date"],
+            ["column","Phase Specs","",1,3,"Slug"],
+            ["column","Phase Specs","",1,4,"Status"],
+            ["column","Phase Specs","",1,5,"File Link"],
+            ["h2","Current BR Snapshot"],
+            ["column","Current BR Snapshot","",1,1,"BR-ID"],
+            ["column","Current BR Snapshot","",1,2,"Current Rule"],
+            ["column","Current BR Snapshot","",1,3,"First Seen (phase)"],
+            ["column","Current BR Snapshot","",1,4,"Last Updated (phase)"],
+            ["column","Current BR Snapshot","",1,5,"Status"],
+            ["h2","Lightweight Changes"],
+            ["column","Lightweight Changes","",1,1,"Date"],
+            ["column","Lightweight Changes","",1,2,"Tier"],
+            ["column","Lightweight Changes","",1,3,"Description"],
+            ["column","Lightweight Changes","",1,4,"Commit"],
+            ["h2","Checkpoint Log"],
+            ["column","Checkpoint Log","",1,1,"Timestamp"],
+            ["column","Checkpoint Log","",1,2,"Checkpoint"],
+            ["column","Checkpoint Log","",1,3,"Result"],
+            ["h2","Resume Pointer"],
+            ["comment","","","ebf6a0dffec4e89d"],
+            ["note","Goals & Scope","","47f7d220a44ffc70"],
+            ["note","Phase Specs","","5dff0b02b2fefdac"],
+            ["comment","Phase Specs","","60305a8c385cd40f"],
+            ["note","Current BR Snapshot","","bb237977c8b6a9c8"],
+            ["comment","Current BR Snapshot","","44a797a7db5f5224"],
+            ["note","Lightweight Changes","","5194f717a8955b59"],
+            ["comment","Lightweight Changes","","013165e8c56f2b73"],
+            ["note","Checkpoint Log","","87725d2856e7692d"],
+            ["note","Resume Pointer","","6282e389a109b5f3"],
+            ["comment","Resume Pointer","","5b3dcd00f70f0239"]
+          ]
+        },
+        {
+          "number": 3,
+          "digest": "6a45d40b5f5cdefa1afcdca62cb8f5b320dc6da9aacd6ff42e34d059c5683319",
+          "changes": [
+            {"kind":"reworded","from":["note","Lightweight Changes","","5194f717a8955b59"],"to":["note","Lightweight Changes","","5d6225b2a04687b3"]},
+            {"kind":"reworded","from":["note","Checkpoint Log","","87725d2856e7692d"],"to":["note","Checkpoint Log","","f3336d6c95603aa2"]}
+          ],
+          "skeleton": [
+            ["field","spec-id"],
+            ["field","slug"],
+            ["field","status"],
+            ["field","created"],
+            ["field","branch"],
+            ["field","follow-up-of","optional"],
+            ["h2","Goals & Scope"],
+            ["h2","Phase Specs"],
+            ["column","Phase Specs","",1,1,"Phase"],
+            ["column","Phase Specs","",1,2,"Date"],
+            ["column","Phase Specs","",1,3,"Slug"],
+            ["column","Phase Specs","",1,4,"Status"],
+            ["column","Phase Specs","",1,5,"File Link"],
+            ["h2","Current BR Snapshot"],
+            ["column","Current BR Snapshot","",1,1,"BR-ID"],
+            ["column","Current BR Snapshot","",1,2,"Current Rule"],
+            ["column","Current BR Snapshot","",1,3,"First Seen (phase)"],
+            ["column","Current BR Snapshot","",1,4,"Last Updated (phase)"],
+            ["column","Current BR Snapshot","",1,5,"Status"],
+            ["h2","Lightweight Changes"],
+            ["column","Lightweight Changes","",1,1,"Date"],
+            ["column","Lightweight Changes","",1,2,"Tier"],
+            ["column","Lightweight Changes","",1,3,"Description"],
+            ["column","Lightweight Changes","",1,4,"Commit"],
+            ["h2","Checkpoint Log"],
+            ["column","Checkpoint Log","",1,1,"Timestamp"],
+            ["column","Checkpoint Log","",1,2,"Checkpoint"],
+            ["column","Checkpoint Log","",1,3,"Result"],
+            ["h2","Resume Pointer"],
+            ["comment","","","ebf6a0dffec4e89d"],
+            ["note","Goals & Scope","","47f7d220a44ffc70"],
+            ["note","Phase Specs","","5dff0b02b2fefdac"],
+            ["comment","Phase Specs","","60305a8c385cd40f"],
+            ["note","Current BR Snapshot","","bb237977c8b6a9c8"],
+            ["comment","Current BR Snapshot","","44a797a7db5f5224"],
+            ["note","Lightweight Changes","","5d6225b2a04687b3"],
+            ["comment","Lightweight Changes","","013165e8c56f2b73"],
+            ["note","Checkpoint Log","","f3336d6c95603aa2"],
+            ["note","Resume Pointer","","6282e389a109b5f3"],
+            ["comment","Resume Pointer","","5b3dcd00f70f0239"]
+          ]
         }
       ]
     },

package/lib/init.js

@@ -5765,7 +5765,12 @@ async function listShapeScopeDocuments(specsRoot) {
   return { docs: docs.sort(), unreadable };
 }
 
-async function checkDocumentShapes(cwd, findings) {
+// The registry, and whether this package can trust it: the entries' own shape,
+// and coverage of every template the shape check covers. Shared with
+// `dflow check-closeout` (PROPOSAL-105), which derives its spec set from the same
+// registry and has to stop, not skip, when the package is damaged — a registry
+// missing one template's entry still reads as valid JSON.
+async function readDocShapesRegistry() {
   const packageDamage = [];
   let registry = null;
   try {
@@ -5818,6 +5823,11 @@ async function checkDocumentShapes(cwd, findings) {
       registry = null;
     }
   }
+  return { registry, packageDamage };
+}
+
+async function checkDocumentShapes(cwd, findings) {
+  const { registry, packageDamage } = await readDocShapesRegistry();
 
   // The current number of every template: its own marker, in THIS package.
   const current = new Map();
@@ -6809,5 +6819,10 @@ module.exports = {
   // fixture removed one of the three structural signals and stayed on the
   // single-candidate path while claiming to test the other, so the test asserts
   // the precondition directly instead of assuming it.
-  inferProjectBundleEdition
+  inferProjectBundleEdition,
+  // Shared with `dflow check-closeout` (PROPOSAL-105): the registry it derives its
+  // spec set from, read and trusted by the same rules doctor uses, and the line a
+  // document copied whole from a projected template starts with.
+  readDocShapesRegistry,
+  WORKFLOW_BUNDLE_GENERATED_MARKER
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dflow-sdd-ddd",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Spec-first SDD/DDD workflow kit for AI-assisted development",
   "type": "commonjs",
   "bin": {
@@ -39,7 +39,7 @@
   },
   "homepage": "https://github.com/weilung/dflow-sdd-ddd#readme",
   "scripts": {
-    "test": "node test/smoke.mjs && node test/skill-default.mjs && node test/registry-parity.mjs && node test/agent-inject.mjs && node test/upgrade-drift.mjs && node test/doc-shapes.mjs && node test/bundle-guards.mjs && node test/lightweight-families.mjs && node test/render.mjs"
+    "test": "node test/smoke.mjs && node test/skill-default.mjs && node test/registry-parity.mjs && node test/agent-inject.mjs && node test/upgrade-drift.mjs && node test/doc-shapes.mjs && node test/bundle-guards.mjs && node test/lightweight-families.mjs && node test/render.mjs && node test/closeout-check.mjs"
   },
   "license": "AGPL-3.0-or-later",
   "publishConfig": {

package/templates/brownfield/references/finish-feature-flow.md

@@ -26,9 +26,10 @@ state, archives the feature directory, and emits a Git-strategy-neutral
   stance — the AI helps at natural checkpoints, you keep the final say.
 - The BC-layer sync in Step 3 **reuses the existing documentation-sync
   mechanism** from `new-feature-flow` (§ 8.3) and `modify-existing-flow`
-  (Step 6.3) — it does not introduce a new sync flow. Treat it as "lift
-  that step out of the per-phase checklist and run it once at feature
-  closeout, with the `_index.md` Current BR Snapshot as input."
+  (Step 6.3) — it does not introduce a new sync flow. § 8.3 and Step 6.3
+  sync when the work they record completes; Step 3 runs the same mechanism
+  once more at feature closeout, with the `_index.md` Current BR Snapshot as
+  input.
 
 **Step Gates** in this flow (stop-and-confirm before proceeding):
 - Step 1 → Step 2 (validation passed → flip status)
@@ -160,8 +161,9 @@ Step 4's post-commit verification, and to Step 5's Integration Summary fields.
       carries none. Decide from the artifact, not from a
       declaration: "the feature is intentionally no-BR" is a claim, and the
       record is what settles it. A classic BR-delta spec carrying ADDED /
-      MODIFIED / RENAMED entries **and** an empty Snapshot means finalization
-      never refreshed it (`modify-existing-flow.md` Step 1.7) and **blocks**.
+      MODIFIED / RENAMED entries **and** an empty Snapshot means the
+      completion checklist never refreshed it (`modify-existing-flow.md`
+      Step 6.3, before checkpoint 1) and **blocks**.
 
 If any check fails:
 > "Cannot finish feature `{SPEC-ID}-{slug}` yet — {N} validation issues
@@ -376,10 +378,10 @@ Deltas are the audit trail. **Cross-reference each hosted lightweight-spec's
 recorded delta the same way** — on any host shape, for the reason above.
 
 > Note: this step does NOT read individual phase-specs to re-derive the BR
-> set — that work was already reconciled by `/dflow:new-phase` Step 7 each
-> time a phase completed. We trust `_index.md` Current BR Snapshot as the
-> feature-level truth here. If the developer finds drift between Snapshot
-> and the phase-specs, fix `_index.md` first, then re-run
+> set. `/dflow:new-feature` § 8.4 and `/dflow:new-phase` Step 7 reconcile the
+> Snapshot when they complete a phase, and we trust `_index.md` Current BR
+> Snapshot as the feature-level truth here. If the developer finds drift
+> between Snapshot and the phase-specs, fix `_index.md` first, then re-run
 > `/dflow:finish-feature`.
 
 Also update `migration/tech-debt.md` / `models.md` / `glossary.md` /
@@ -486,13 +488,13 @@ Then, in this order:
 
 1. **Record the checkpoint row first.** Write one row in the moved
    `_index.md` Checkpoint Log — `closeout | committed` for Y, `closeout |
-   skipped` for N. The closeout row carries **no commit hash**: the closeout
-   commit cannot contain its own hash. Trace it later via
+   skipped` for N. The closeout row carries **no commit hash**: no later
+   commit of this host carries it. Trace it later via
    `git log -1 -- dflow/specs/features/completed/{SPEC-ID}-{slug}` (or the
-   optional `Dflow-Checkpoint` trailer). The "hash only after success" rule
-   still applies to spec / implementation rows — closeout is the documented
-   exception (see `references/git-integration.md` § Commit Checkpoints,
-   Branch Gate & AI Commits).
+   optional `Dflow-Checkpoint` trailer). On any other checkpoint row, a
+   `committed ({hash})` Result is written after its commit and carried by the
+   host's next commit (see `references/git-integration.md` § Commit
+   Checkpoints, Branch Gate & AI Commits).
    **Backfill any unfilled hosted `Commit` cell in the same edit** — a hosted row
    waits for the host's *next* commit and this is it. **Unfilled means empty *or*
    holding a placeholder** — `{hash}`, `{pending}`, `（待 commit）`, anything that
@@ -526,10 +528,11 @@ Then, in this order:
    `migration/tech-debt.md`) — Step 3 is **skipped entirely for a no-BC host**
    (and for a baseline host), so this half is empty there; **and**
    **(b)** the **documentation-sweep step of the flow that produced *this
-   change*** — take the paths from that step, not from a list kept here. It runs
-   *after* that flow's implementation checkpoint and *before* closeout, so **that
-   flow** leaves its deltas uncommitted; a later phase's own checkpoints may have
-   committed them since, and staging an already-committed path is a no-op.
+   change*** — take the paths from that step, not from a list kept here. A
+   commit may already have carried them — `modify-existing-flow.md`'s
+   checkpoint 1 carries its own sweep, and a later phase's checkpoint may have
+   carried a `new-feature-flow.md` sweep — and staging an already-committed path
+   is a no-op, so stage them either way.
    Those sweeps reach
    Domain-layer documents under `dflow/specs/domain/`, plus the **global**
    documents `glossary.md`, `domain/analysis.md` and `migration/tech-debt.md`,
@@ -571,7 +574,8 @@ Then, in this order:
    admitted. On a **phase-bearing** host there is **no allow-list at all** —
    that check is minimal-host-only and lives in that branch file — so read the
    sweep directly and **do not go looking for a list that host never produced.**
-   Read each delta (`git diff -- {path}`) and scope every one to *this change*;
+   Read each delta (`git diff HEAD -- {path}`, which includes what is already
+   staged) and scope every one to *this change*;
    staging only "what Step 3 wrote" leaves a no-BC host's global delta dirty and
    the post-commit clean-tree check fails.
 3. **Commit (Y) or stop (N).** For Y the AI commits. If a pre-commit hook
@@ -621,10 +625,9 @@ every item:
       only when the baseline became unreadable *during* closeout.
       Step 1 blocks unless every
       spec in the host already reads `status: completed`, so those flips are
-      already **in** the baseline whichever step made them: a **minimal** host's
-      come from `modify-existing-flow.md` Step 1.7's finalization, a
-      **phase-bearing** host's from its phases completing — no phase-bearing
-      host runs Step 1.7, whichever flow opened it. Either way the
+      already **in** the baseline whichever step made them: a lightweight-spec's
+      comes from `modify-existing-flow.md` Step 6.3, a phase-spec's from its
+      phase completing. Either way the
       flips are not differences this check admits; they are part of what it
       compares against. (They are differences only from the *pre-flip* record,
       which is not the baseline.)
@@ -756,8 +759,8 @@ itself, state in the conversation *how* Step 4's post-commit verification
 reached its result — not that it passed, but how it was computed:
 
 1. **The baseline** — the tree Step 1 read, and which step put each spec's
-   `status: completed` flip into it (Step 1.7's finalization on a minimal host;
-   the phases completing on a phase-bearing one, which never runs Step 1.7).
+   `status: completed` flip into it (`modify-existing-flow.md` Step 6.3 for a
+   lightweight-spec; the phase completing for a phase-spec).
 2. **The differences you derived, each with the step that ordered it** —
    Step 2, Step 4's terminal Resume Pointer write, or Step 4 instruction 1. This
    is the set the check *derives* instead of listing, so printing it is what

package/templates/brownfield/references/finish-feature-minimal-host.md

@@ -185,15 +185,17 @@ A `✗` here stops closeout there, on the same terms.
       `Commit` must still name the **same single documentation commit**.
 - [ ] **Minimal host (zero-phase) only** — **nothing that constitutes the change
       itself is still uncommitted.** This is deliberately not "the host
-      directory is clean": **checkpoint 1 carries the change, the closeout
-      commit carries the record the flow writes afterwards.** Checkpoint 1 sits
-      at `modify-existing-flow.md`'s Step 5 → Step 6 gate and holds the change
-      itself — for a **T2** its lightweight-spec plus the implementation source,
-      for a **T3** its `_index.md` row plus the implementation source, and for a
-      **baseline** host the capture itself, which *is* that host's
-      change. What the flow writes *after* that gate — Step 6's completion
-      checklist and Step 1.7's "Finalize + close" — is derived record and rides
-      into the closeout commit.
+      directory is clean": **checkpoint 1 carries the change and the record
+      Step 6 writes; the closeout commit carries what the flow writes after
+      checkpoint 1.** Checkpoint 1 is offered at the end of
+      `modify-existing-flow.md`'s Step 6 (§ 6.5) and holds the change itself —
+      for a **T2** its lightweight-spec plus the implementation source, for a
+      **T3** its `_index.md` row plus the implementation source, and for a
+      **baseline** host the capture itself, which *is* that host's change —
+      together with Step 6's completion checklist. What the flow writes *after*
+      checkpoint 1 — Step 1.7's "Finalize + close" — is derived record and
+      rides into the closeout commit, and so may a correction to Step 6's
+      record made after checkpoint 1.
       **A post-hoc host (Step 1.8) inverts the source half, and this is where
       the reconciliation contract is enforced.** Its change is the *already
       merged* hotfix; checkpoint 1 is the **documentation** commit. So that
@@ -236,8 +238,9 @@ A `✗` here stops closeout there, on the same terms.
       to both phase-spec and lightweight-spec"): ticking the tasks this change
       completed and labelling each unchecked one as follow-up (6.1), and — when
       the developer accepted the offer — collapsing or removing the section
-      (6.2). On a minimal host that checklist necessarily runs *after*
-      checkpoint 1, so these edits are uncommitted here by construction;
+      (6.2). That checklist runs before checkpoint 1, so these edits are
+      normally committed already; this admits a correction to them made after
+      checkpoint 1;
       (iii) the Domain-layer documents **this change's Step 6.3 sweep** updates
       — under `dflow/specs/domain/`, plus
       `dflow/specs/migration/tech-debt.md` — scoped to *this change's* delta.
@@ -251,11 +254,24 @@ A `✗` here stops closeout there, on the same terms.
       and therefore still qualify under (iii). **(iii) never covers a baseline
       host** either — its capture *is* the change, and is blocked
       above.
-      Read each delta (`git diff -- {path}`) — do not infer it from the
-      filename. **The list is closed** — if a later change adds another
+      Read each delta with `git diff HEAD -- {path}` — plain `git diff` hides
+      what is already staged — and do not infer it from the filename.
+      **The list is closed** — if a later change adds another
       finalization field, add it here explicitly; "a host file is dirty" is never
       on its own a reason to pass. (Unrelated work in progress elsewhere is
       fine; say which files you judged unrelated.)
+      **Checkpoint 1's own record, corrected after checkpoint 1, is outside the
+      list** — the spec's content beyond (ii)'s edits, a row's own text, a
+      document a baseline capture wrote, or the reverse-link row a follow-up
+      wrote into its original's `_index.md`. It blocks: the closeout commit
+      does not carry checkpoint 1's content. The dispatch right after this
+      item gives the repair.
+
+**Open `references/finish-feature-record-correction.md` and follow it there.**
+Do this only when the check above blocked on a correction to checkpoint 1's own
+record: the repair depends on where checkpoint 1 stands now, and that file gives
+it for each case. Otherwise go on to the next check.
+
 - [ ] **Minimal host (zero-phase), no-BC only** — **the host did not commit a
       bounded context it does not have.** This file's `nothing that constitutes
       the change itself is still uncommitted` check reads the *working
@@ -330,10 +346,11 @@ A `✗` here stops closeout there, on the same terms.
       assertion.
       The plausibility conditions, all required: the
       `reconciled ({merged-hotfix-hash})` value passes hash evidence — (a) and
-      (b) as usual, and for **(c)** its diff touches the implementation paths
-      the T2 lightweight-spec or the T3 row **declares** (Step 1.7 requires that
-      declaration; an artifact naming none leaves (c) nothing to compare and
-      **blocks** rather than passing vacuously). It must also **differ**
+      (b) as usual, and for **(c)** its diff touches **at least one** of the
+      implementation paths the T2 lightweight-spec or the T3 row **declares**
+      (Step 1.7 requires that declaration; an artifact naming none leaves (c)
+      nothing to compare and **blocks** rather than passing vacuously). It
+      must also **differ**
       from the Lightweight Changes row's documentation-commit hash (different
       provenance; see Step 1.8). The per-tier trace must exist too: a **T2**
       carries `hotfix-branch:` in its lightweight-spec frontmatter, a **T3** has
@@ -345,6 +362,10 @@ A `✗` here stops closeout there, on the same terms.
       for a **T3**. An uncited hash **blocks** closeout: it leaves pr-review
       nothing to confirm against, and this gate is not a substitute for that
       confirmation.
+      **When (b) fails for the `reconciled (...)` hash, do not report only
+      "not an ancestor".** Open `references/modify-existing-post-hoc-hotfix.md`
+      item 6: it names the causes and the repair for each; report the one that
+      is true.
 
 > **Zero-phase minimal host (`modify-existing-flow.md` Step 1.7 / the Step 1.6
 > minimal variant / Step 1.8's post-hoc hotfix, whose linkage resolves to one of

package/templates/brownfield/references/finish-feature-record-correction.md

@@ -0,0 +1,45 @@
+# Correcting Checkpoint 1's Own Record — Brownfield Progressive Extraction
+
+Branch file of `references/finish-feature-minimal-host.md`. It **adds** the
+repair for one case that file's working-tree check blocks; it does not restate
+or override anything in that file.
+
+**You are here because** that file's `nothing that constitutes the change
+itself is still uncommitted` check blocked on a correction to checkpoint 1's
+own record — it owns that judgement — or because
+`references/modify-existing-post-hoc-hotfix.md` item 6 found that a post-hoc
+record names a different fix.
+
+The correction belongs in checkpoint 1 itself, and whether it can go there
+depends on where checkpoint 1 stands now. Report the case that is true and give
+the developer its repair:
+
+- **Not pushed, and checkpoint 1 is `HEAD`** (`git rev-parse HEAD` prints
+  checkpoint 1's hash) — first set every entry that holds checkpoint 1's hash
+  back to what checkpoint 1 has (`git show HEAD:{path}`); the refill below
+  writes them again. Then stage the correction alone (in `_index.md`, `git add
+  -p` only its hunk: the Resume Pointer rides the closeout commit), check that
+  `git diff --cached` shows nothing else, and `git commit --amend`. Then write
+  the new hash into every entry that names checkpoint 1 — the Checkpoint Log
+  `committed (...)` and each row's `Commit` cell. An entry left on the old hash
+  fails hash evidence (b).
+- **Not pushed, but a later commit sits on top of checkpoint 1** — stop:
+  rewriting an earlier commit is the developer's to do.
+- **Already pushed** — stop and leave it to the developer. Rewriting a pushed
+  commit is the team's call (refill the entries as above if they do). The other
+  way is to commit the correction on its own: add no Checkpoint Log row for it
+  (a second row blocks), and ask for it to be named in the PR description — it
+  departs from the two-commit lifecycle, and
+  `references/pr-review-checklist.md`'s whole-history item sees it only when it
+  touches this host's directory.
+
+**A post-hoc host's `reconciled (...)`** names the hotfix, not checkpoint 1, so
+refilling after an amend leaves it as it is — **unless the correction changes
+which fix the record names** (`references/modify-existing-post-hoc-hotfix.md`
+item 6, "The record names a different fix"). Then `reconciled (...)` names the
+wrong fix too. Item 3 wrote it before checkpoint 1, so checkpoint 1 carries it:
+correct it to the right fix's commit — the one item 3 says to record — as part
+of the same correction, whichever way that lands (the amend, the developer's
+rewrite, or the correction's own commit). Put that commit through item 6's test
+before closeout continues; that item gives the repair if (b) fails for it as
+well.