Repository navigation
Integration test: writ-deploy scenario — fresh user, personal layer, three platforms #346
Description
Tracking issue for docs/plans/writ-deploy-scenario.md: an end-to-end user-journey integration test — pristine sandbox user, real binaries on PATH, writ configured with only the personal layer, writ deploy noblefactor thenobles, assertions on the filesystem, writ status, and the execution store. Source of truth: the devlore-cli/writ-layer branch on the owner's personal repo (dogfooding staging ground), mirrored by a neutral checked-in fixture for CI. Phases: branch scaffold (owner-run) → harness + fixture → deploy leg → CI matrix (ubuntu+macos) → Windows per the staging ruling.
Metadata
Metadata
Assignees
Labels
No labels
Activity
docs(plans): the writ-deploy scenario — fresh user, personal layer, t…
test(writ): the scenario harness — a pristine user, the real binary, …
test(writ): the deploy leg — and the three defects it caught (#349)
ci(scenario): the writ-deploy scenario on ubuntu and macos (#350)
ci(scenario): the windows leg — GOEXE binaries, bash shell, empirical…
David-Noble-at-work commentedon Aug 9, 2026
Delivered across PRs #348–#353: phase 0 (the devlore-cli/writ-layer branch scaffold, secrets verified encrypted), phase 1 (harness + fixture, two repo modes), phase 2 (the deploy leg — which caught and fixed three real defects: missing provider registration in the writ/lore binaries, dangling snapshot-targeted symlinks, second-resolution trace overwrites), phase 3 (ubuntu+macos matrix), phase 4 (windows green after the ToSlash and paths-only-constructor fixes). The harness now dogfoods writ repo add (#352) with the URL form landing in #353. Every acceptance criterion holds; the queued Tuckr-parity question gates the dogfooding cutover and lives in docs/plans/writ-deploy-scenario.md.