update engineering/0019/SESSION-0019.0-TRANSCRIPT-2026-06-10T22-06--INPROGRESS.md

engineering/0019/SESSION-0019.0-TRANSCRIPT-2026-06-10T22-06--INPROGRESS.md

@@ -52,6 +52,21 @@ one typed, source-linked Gitea issue on `wiggleverse/engineering`.
   (`type/story`, `priority/P1`).
 - Deleted the filed draft; `issues/` clean, no stragglers.
 
+**Second ask (same session):** stand up the §9 two-tier E2E gate machinery
+(hermetic localhost harness per merge + same suite on PPE per deploy), child
+of #26.
+
+- Verified #26 is the open `type/epic` "Engineering-practice uplift" (P2) →
+  sized this ask as its child **`type/feature`** (Epic→Feature, one level).
+- Grounded against handbook §10.3 (two-tier testing) and §9; kept business
+  sections mechanism-free (Docker Compose / Mailpit / Playwright / SQLite
+  confined to Solution notes, with the recommended slicing — Tier 1 first,
+  not blocked on PPE).
+- **Filed as engineering#44**:
+  https://git.wiggleverse.org/wiggleverse/engineering/issues/44
+  (`type/feature`, `priority/P1`; body links Parent #26, relates #43).
+- Deleted the filed draft; `issues/` clean.
+
 ## Deferred decisions
 
 - **Self-approved the draft before filing (INV-1) under yolo posture.** The
@@ -65,3 +80,13 @@ one typed, source-linked Gitea issue on `wiggleverse/engineering`.
   handbook policy codification has independent business value (it changes how
   every autonomous session behaves), so story over task; it needs no design,
   so not a feature.
+- **Self-approved #44 under yolo as well** (same INV-1 rationale as #43:
+  fully-specified slash-command ask, operator not present mid-session).
+- **Captured #44 as one Feature rather than splitting Tier 1 / Tier 2 into
+  two.** The operator framed the two tiers as one machinery ask and §10.3
+  treats them as one suite with two targets; the Tier-1-first ordering is
+  preserved as recommended slicing in Solution notes. Split later at design
+  time if it proves too big.
+- **Parent link to #26 is body-prose only** ("Parent: #26" in
+  Assumptions·dependencies) — `capture-issues.sh` has no dependency-link
+  flag; set a tracker-level dependency by hand if wanted.