M6: Matt migration

[Sandstorm831]

This was generated by AI during triage.

Delivers

M6 migrates the Matt planning-to-implementation workflow onto Secant's existing Step vocabulary and promotes it as the one v1 Built-in Workflow Bundle. The maintained Matt front already contains an Interactive agent grill, an approve/reject Human Gate, and an Agent step that writes a spec. The maintainer will supply the original skill folders for the completed Bundle; M6 does not assume that current or legacy skill files are copied. The migration satisfies the fourth pass condition of #11: any capability it needs lands at a named generic Step seam, with no runtime branch on Bundle identity. The Test Repair Proof Bundle remains a maintained External Workflow Bundle.

The built-in .wfb is release-built, digest-locked, embedded as an asset in the Bun-compiled single-file executable, and installed at startup through the ordinary Bundle ingestion path in both TUI and headless invocations. ADR 0029's ADR 0030 amendment governs the shipping path; its earlier npm-tarball text does not.

M6 also resolves #70: a user starting the TUI in legacy Windows conhost has a practical opportunity to read the Windows Terminal notice before the TUI takes over. The first release candidate includes the Matt built-in and the notice fix. The v1 Harnesses are Claude Code and Codex.

Hard constraints

• Preserve the Sequence vertical slices, refactoring gates, and legacy deletion #20 order: the Test Repair workflow passed before Matt migration, and G3 is closed before M6. G4 follows M6. The maintainer-supplied original skill folders are an input to the later M6 spec and implementation; no legacy skill files or folders are assumed reusable.
• Apply the eight slicing rules: both clients share the Projection Port, every slice has a three-OS CI acceptance scenario, Bundles under the maintained Bundle tree are built and exercised as user Bundles, no Module scaffolding is created early, no source branches on workflow identity, and TUI slices carry the applicable Prototype Crucible's launch and Run information architecture #23 interaction and platform evidence. Ticket packets carry Owner:, Ratchet:, Deletes:, Gate:, and Dependencies: and are published without ready-for-agent until curated.
• Headless v1 refuses any Bundle containing an Interactive agent step at Preflight with the remediation to run it in the TUI. The Matt Bundle's interactive opening therefore needs a headless-compatible or fake-Harness CI path that proves the built-in shipping and runtime behavior without pretending a headless interactive Run is supported.
• Follow ADR 0029 as amended by ADR 0030: build exact .wfb bytes once, embed them in each compiled binary, lock the authored Bundle version to its digest, ensure at startup through the ordinary ingestion contract, and preserve upgrade coexistence. The Proof Bundle is never shipped as a built-in.
• Keep the existing three-OS semantic, standalone runtime-conformance, compiled-binary consumer, terminal, and protected release gates. Real Harnesses do not run in CI. Release claims require the recorded human evidence and support matrix specified by ADR 0027.
• The legacy-conhost notice remains the ADR 0030 mitigation. Legacy conhost is not a claimed support-matrix row, and Windows Terminal suppression and headless behavior remain intact.

Gate introduced

M6 supplies the first release candidate and its built-in Bundle evidence to the existing three-OS and protected release gates. G4, the post-M6 human-in-the-loop refactoring plan review, follows M6; it introduces no new automated gate.

Done when

• Every M6 implementation ticket and Keep the legacy-conhost startup notice readable before TUI takeover #70 are closed, and Audit: M6 has a decision with every fix-now ticket closed.
• The full Matt Bundle is built, installed, and exercised through the generic Bundle and Run contracts; Choose Crucible's genericity-proof workflow #11 pass condition 4 is reviewed at the named Step seam. The maintained External Proof Bundle still passes.
• Compiled binaries on Windows x64, macOS arm64, and Linux x64 carry only the allow-listed built-in bytes, install the locked identity and digest on first startup, leave it unchanged on a second startup, and preserve the ADR 0029 upgrade and collision behavior.
• The Keep the legacy-conhost startup notice readable before TUI takeover #70 notice is observed to remain readable in a real legacy-conhost launch before TUI takeover; Windows Terminal does not show it, and headless use remains unaffected.
• The first release candidate passes the established three-OS CI and release-candidate validation paths, with required human evidence recorded. The support matrix and built-in identity and digest in the release approval summary are current. G4 can then open.

[Sandstorm831]

This was generated by AI during triage.

Starting context

Files are pinned at 219d99b3e9b291cbe18148850f7d0c022d44f0d8 (HEAD). The legacy oracle is pinned to the legacy-devflow tag. Read the authority column before using older wording.

Input	Why it matters	Authority
Parent wayfinder #2, sequencing resolution, handoff amendment, runtime amendment, and third-Harness amendment	Fix the M6 Matt migration and first-release-candidate row, eight slicing rules, audit and gate order, Bun compiled runtime, and the two-Harness v1 scope after OpenCode qualification failed.	Canonical decisions; the map is an index
G3 decision #208 and M5 close-out	G3 unblocks M6, explicitly adds #70, confirms no M5 handover, and identifies the current green three-OS and consumer baseline.	Canonical handoff
Genericity-proof resolution #11	The Test Repair Proof Bundle remains external; Matt migration must satisfy pass condition 4 by adding any new capability at a named generic Step seam without branching on workflow identity.	Canonical decision
Current Matt front manifest	Records the maintained External Bundle's already-working Interactive agent → approve Gate → spec Agent opening. Its current skill references do not decide which skill folders M6 ships; the maintainer will supply the original folders for the completed Bundle.	Current behavior only
Legacy grill and stage flow and legacy Run and execution flow	Historical descriptions of stage behavior only. They are not a source for Bundle skill files, folders, or prompts.	Advisory historical evidence
ADR 0029, ADR 0030, and Workflow Bundle glossary	Defines the Shipped/Built-in distinction, digest lock, startup ensure, coexistence, and the amended location of the .wfb: embedded in the compiled binary, not placed beside an npm tarball.	Canonical; ADR 0030 and ADR 0029's amendment supersede old Shipping and Verification text
#70 unreadable notice, ADR 0018, and ADR 0030	Exact legacy-conhost failure and the existing terminal mitigation: the notice must be readable before TUI takeover while Windows Terminal suppression and headless behavior stay correct. The supplied OpenCode checkout is comparison evidence, not Secant's policy.	Canonical bug and ADRs; OpenCode advisory
Slicing rulebook and ADR 0024	Headless Preflight refuses every Bundle with an Interactive agent step and says to run it in the TUI. M6 needs a headless-compatible or fake-Harness CI path; user-facing slices otherwise use the same Projection Port in both clients.	Canonical
ADR 0027, release checklist, and release workflow policy	The first candidate uses existing three-OS semantic, standalone conformance, compiled-consumer, and terminal evidence, then the manual candidate validation and human release checklist. Real Harnesses do not run in CI.	Canonical release policy

Reading rule

Start with #20's amended M6 row and G3's handoff. Read the current Matt front and #11 before shaping its remaining routing; use the legacy glossary only for historical stage behavior. Obtain the original skill folders from the maintainer before the later spec fixes the Bundle assets; do not copy current or legacy skills by assumption. For built-in shipping, read ADR 0029's final amendment with ADR 0030 before its historical Shipping section. Keep the headless Interactive-step refusal visible while choosing the CI path. Resolve #70 from its real-console observation and ADR 0030, then apply ADR 0027 to the first release candidate. The supplied OpenCode checkout may inform presentation comparison, but its behavior cannot override Secant's ADRs.