Epic — W-F implementation program. Approved by Jason 2026-08-11 via the Task-18 assignment packet (jarvis-brain docs/scratchpads/lease-remediation/dispatch/TASK-18-ASSIGNMENT-PACKET.md). Design frozen at REV3 (2ef725ffe, verdict verdict-HARNESS-HOMES-REV3-FREEZE.md); full design: docs/scratchpads/lease-remediation/dispatch/HARNESS-HOMES.md.
Owner: shaggy (Stack code owner). Base:IMPLEMENTATION_BASE_SHA is deliberately NOT pinned yet — pin to post-#1145 next once #1145 lands (it currently blocks compiled-mode boot, so W-F acceptance would otherwise only ever run in dev mode). Branches (one per sub-lane: feat/wf1-composition, feat/wf2-bundle-migration, feat/wf4-plugin-acquisition, feat/wf5-refresh-safety) are cut at pin time, not before — an empty branch on a defective base invites work on the wrong foundation.
Prioritization (Jason, 2026-08-11): focus on extensible harness plugins, Pi + OpenAI models first — establish PoC and working implementation, then extensibility. scrappy holds the detailed P3 direction; coordinate there.
Sequencing (approved):
0. Fail-loud audit runs as its own item (see sub-issue) — small, mechanical, do first.
#1145 first — unblocks P5 and compiled-mode acceptance; also the first instance of the fail-loud class, sets the pattern.
Re-pin IMPLEMENTATION_BASE_SHA to post-#1145 next.
Resolve#1109 (currently has conflicts) before W-F1 starts — it and W-F1 both touch packages/mosaic/src/commands/launch.ts. Note: the native Pi RPC adapter (P3 lane) is a third claimant on the same launcher seam.
W-F2 and W-F4/F6 may run in parallel (no launcher contact).
W-F5 last, as its own gate — highest risk, never evidenced; P3's persistent per-conversation sessions make concurrent refresh the steady state, raising its priority.
**Epic — W-F implementation program.** Approved by Jason 2026-08-11 via the Task-18 assignment packet (jarvis-brain `docs/scratchpads/lease-remediation/dispatch/TASK-18-ASSIGNMENT-PACKET.md`). Design frozen at REV3 (`2ef725ffe`, verdict `verdict-HARNESS-HOMES-REV3-FREEZE.md`); full design: `docs/scratchpads/lease-remediation/dispatch/HARNESS-HOMES.md`.
**Owner:** shaggy (Stack code owner). **Base:** `IMPLEMENTATION_BASE_SHA` is deliberately NOT pinned yet — pin to post-#1145 `next` once #1145 lands (it currently blocks compiled-mode boot, so W-F acceptance would otherwise only ever run in dev mode). Branches (one per sub-lane: `feat/wf1-composition`, `feat/wf2-bundle-migration`, `feat/wf4-plugin-acquisition`, `feat/wf5-refresh-safety`) are cut at pin time, not before — an empty branch on a defective base invites work on the wrong foundation.
**Prioritization (Jason, 2026-08-11):** focus on extensible harness plugins, Pi + OpenAI models first — establish PoC and working implementation, then extensibility. scrappy holds the detailed P3 direction; coordinate there.
**Sequencing (approved):**
0. Fail-loud audit runs as its own item (see sub-issue) — small, mechanical, do first.
1. #1145 first — unblocks P5 and compiled-mode acceptance; also the first instance of the fail-loud class, sets the pattern.
2. Re-pin `IMPLEMENTATION_BASE_SHA` to post-#1145 `next`.
3. Resolve #1109 (currently has conflicts) before W-F1 starts — it and W-F1 both touch `packages/mosaic/src/commands/launch.ts`. Note: the native Pi RPC adapter (P3 lane) is a third claimant on the same launcher seam.
4. W-F2 and W-F4/F6 may run in parallel (no launcher contact).
5. W-F5 last, as its own gate — highest risk, never evidenced; P3's persistent per-conversation sessions make concurrent refresh the steady state, raising its priority.
shaggy
self-assigned this 2026-08-11 22:01:30 +00:00
#1162 — Durability — user services, restart recovery (reboot proof needs separate approval)
Sequencing gates per the approved packet: #1145 first (base pin only after it lands); #1109 / W-F1 / native-Pi-RPC three-claimant coordination on launch.ts before any launcher edit.
Task-18 sub-issues posted under this epic:
- #1156 — Fail-loud audit: defaults/fallbacks that make absence indistinguishable from presence
- #1157 — W-F1: launch composition — three-layer merge, schema rejection, one-registry launch, dry-run
- #1158 — W-F2: bundle migration — account→bundle compat, backup/sync exclusions
- #1159 — W-F4/W-F6: plugin acquisition — versioned clean-room, role-scoped activation (Pi+OpenAI first)
- #1160 — W-F5: refresh safety — write-through vs rename-replace, concurrent-refresh race (gate, runs last)
- #1161 — A3–A6 transaction safety — no-clobber/rollback, primary lock contract, fault injection
- #1162 — Durability — user services, restart recovery (reboot proof needs separate approval)
Sequencing gates per the approved packet: #1145 first (base pin only after it lands); #1109 / W-F1 / native-Pi-RPC three-claimant coordination on launch.ts before any launcher edit.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Epic — W-F implementation program. Approved by Jason 2026-08-11 via the Task-18 assignment packet (jarvis-brain
docs/scratchpads/lease-remediation/dispatch/TASK-18-ASSIGNMENT-PACKET.md). Design frozen at REV3 (2ef725ffe, verdictverdict-HARNESS-HOMES-REV3-FREEZE.md); full design:docs/scratchpads/lease-remediation/dispatch/HARNESS-HOMES.md.Owner: shaggy (Stack code owner). Base:
IMPLEMENTATION_BASE_SHAis deliberately NOT pinned yet — pin to post-#1145nextonce #1145 lands (it currently blocks compiled-mode boot, so W-F acceptance would otherwise only ever run in dev mode). Branches (one per sub-lane:feat/wf1-composition,feat/wf2-bundle-migration,feat/wf4-plugin-acquisition,feat/wf5-refresh-safety) are cut at pin time, not before — an empty branch on a defective base invites work on the wrong foundation.Prioritization (Jason, 2026-08-11): focus on extensible harness plugins, Pi + OpenAI models first — establish PoC and working implementation, then extensibility. scrappy holds the detailed P3 direction; coordinate there.
Sequencing (approved):
0. Fail-loud audit runs as its own item (see sub-issue) — small, mechanical, do first.
IMPLEMENTATION_BASE_SHAto post-#1145next.packages/mosaic/src/commands/launch.ts. Note: the native Pi RPC adapter (P3 lane) is a third claimant on the same launcher seam.Task-18 sub-issues posted under this epic:
Sequencing gates per the approved packet: #1145 first (base pin only after it lands); #1109 / W-F1 / native-Pi-RPC three-claimant coordination on launch.ts before any launcher edit.