update engineering/0025/SESSION-0025.0-TRANSCRIPT-2026-06-22T07-40--INPROGRESS.md

engineering/0025/SESSION-0025.0-TRANSCRIPT-2026-06-22T07-40--INPROGRESS.md

@@ -24,8 +24,57 @@ It's the docs-lead spine F2–F5 cite — first.
 
 ```
 
+## Plan
+
+> Anchor: design `docs/sdl-pipeline-refactor-brief.md` (R2a — locked Solution-Design
+> brief; eligibility ELIGIBLE). Work repo: `wiggleverse/engineering`. Feature #63 on
+> the dev-claude-plugin tracker. Branch: `feat/sdlc-f1-handbook-reconciliation`.
+
+**F1 — Handbook reconciliation for the staged-gate SDLC pipeline.** Reconcile the
+canonical engineering docs to the brief's locked decisions. F1 is the *only* Feature
+touching `engineering` (F2–F5 are dev-claude-plugin), so the full handbook sweep
+happens here or never — internal consistency is required, not optional.
+
+Deliverables (per brief §F1):
+1. **§3.3 accretion** (README) — the Solution Design is authored by ACCRETION: each
+   design-track lens (business → product → engineering) is written into the same
+   growing SPEC at its own gated stage; never separate brd.md/prd.md files; one
+   coherent doc `superpowers:writing-plans` consumes. Reframe the Delivery row +
+   traceability row (drop "Slice").
+2. **§4.3 reconciliation** (README) — Feature = one SPEC = one plan = one execution;
+   its internal units are the plan's Tasks (not slices/Stories). Feature→Story(slice)
+   sub-layer retired; Stories are STANDALONE leaf issues only (R2(b)). "Slice" is not
+   used (superpowers grain: sub-project / spec / plan / Task / Step). R1–R4 intact.
+3. **GUIDE/TEMPLATE** — accretion authoring model (replaces "drafted whole, reviewed
+   whole"); §7 Delivery Plan = rollout/launch strategy only (retire §7.2 "Slicing
+   plan" task-checklist; renumber 7.3→7.2, 7.4→7.3); relocate the `**Design:**` field
+   to §5.1 (Product lens, with the Claude-Design-vs-Code decision); drop "Slice"
+   columns from traceability + docs tables.
+4. **Claude-Design-vs-Code home** — keep §5.1 (Product/prd lens) as the documented
+   home; note the decision is authored at the prd-lens stage under accretion.
+5. **Full slice sweep** across README §4 day-to-day, §7 roadmap, §10, lifecycle tree.
+
+Then: verify (residual-slice grep + internal §7.x ref check) → commit → PR → merge.
+No engineering version bump (handbook, not a semver'd plugin). No code/tests/PPE
+(docs-only; the pipeline's E2E/PPE gates don't apply to a prose change).
+
 ## Deferred decisions
 
 _Autonomous-mode low-confidence calls the driver made and would have
 liked operator input on. Appended as the session runs; surfaced at
 finalize. Empty if none._
+
+- **Full-handbook slice sweep (scope).** The brief's F1 item enumerates §3.3/§4.3/
+  GUIDE/TEMPLATE/claude-design-home, but "slice" is load-bearing in README §7
+  (roadmap) and §4 too. Since F1 is the only engineering-touching Feature, I swept
+  all of them for internal consistency rather than leaving §7 contradicting a
+  slice-retired §4.3. Confidence high (forced by the decomposition), logged for
+  visibility.
+- **`**Design:**` field relocation + plugin lag.** Retiring per-slice §7.2 leaves the
+  shipped `**Design:**` field (consumed by `wgl-design-handoff` + the design-readiness
+  soft gate, which read it per-`--slice`) without a slice home. I relocated it to the
+  SPEC's §5.1 (Product lens), co-located with the Claude-Design-vs-Code decision —
+  one SPEC = one design decision. The plugin's `--slice`-grained plumbing
+  (`backfill-spec-design.sh`, `design-readiness.sh`) now lags the docs and needs a
+  downstream reconciliation (candidate: F5 wiring / a follow-up issue). Flagged, not
+  fixed in F1 (docs-lead-automation, §4.1).