Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Milestones

Completion is scoped to macOS ARM64 and the acceptance surfaces below. Visual baseline approval, idle-host performance measurement, other platforms and consumer adoption remain separate qualification work.

M1/M4 review: the attach/output race correction adds deterministic initial-output coverage. Hosted qualification completes full source CI, packaged consumers and cold standalone macOS ARM64 acceptance at the immutable correction revision. Desktop native consumer acceptance remains a separate pending gate.

M5 review: main and the signed version PR passed full hosted CI, Pages is live, and version PR #1 was subsequently merged with explicit user authorization. See hosted delivery.

M6 review: all three 0.1.1 Cargo crates are published, publisher registrations are verified, live OIDC authentication and token revocation passed, and the registry consumer ran a real PTY. See Cargo delivery. Main protection applies to administrators and all future changes.

M3 review: composition controls cover the Design Core selector, icon actions, resting tabs and narrow frame. Visual baseline approval remains separate.

TaskStatusDependenciesGateEvidenceNext action
M0DonenoneStandalone governance and pinned importsQualificationMaintain contracts and evidence
M1DoneM0Engine, runtime and real PTY testsQualificationSeparate idle-host performance gate
M2DoneM1Scoped Tauri helpers and native demoQualificationQualify additional platforms when requested
M3DoneM1Viewport and Storybook interaction/axeQualification, Shell examples, Output alignment and colorsSeparate visual baseline approval
M4DoneM2, M3Packaged consumers and cold native acceptanceQualificationQualify additional consumer adoption independently
M5DoneM4CI, coordinated version PR and specification PagesGitHub automation, Hosted deliveryMaintain protected version-PR checks
M6DoneM5Protected main and Cargo trusted publishingCargo publishing, Cargo deliveryRelease future prepared versions through protected PRs and OIDC

M5/M6 review: the npm delivery lane qualifies immutable artifacts and exact registry verification. npm bootstrap, trusted-publisher registration and completed publication remain explicit gates until external receipts are recorded. Existing source and Cargo evidence stands.

M1/M4 review: ordered output capture tracks the additional idle-prompt resize race. The new exact regression and source/native qualification must pass before the next version PR merges. Desktop native consumer qualification remains separate.

M5/M6 0.1.2 review: the delivery receipt completes the authorized version-PR approval/merge, all three Cargo versions, real registry PTY consumer, npm latest/public bytes, source-bound signatures/ provenance, clean frozen npm consumer, trusted-publisher registration and scoped GitHub release. Native Desktop adoption, other platforms, visual baselines and the known-idle performance gate remain separate.

M1/M4 follow-up: replacement sink fencing retains the published 0.1.2 receipt while qualifying the Rust-only immutable Git consumer repair. Forced interleaving, real PTY and Desktop/native evidence stay separate; no new Cargo publication or visual approval is implied.