Four claims in the core preamble an isolated launch makes false: that the
workspace is the real project, that ~/shared is shared with every session
against it, that the harness keeps state on the host, and that the work is
recoverable there afterwards. A session acts on these - one that believes
its transcript outlives the container leaves work for a resume that cannot
happen.
The two paragraphs carrying them become placeholders with a variant each,
which is the mechanism the preamble already uses, so the ordinary briefing
comes out byte-identical apart from two reworded clauses. The harness
fragment, which is what promises the resume, is replaced rather than
dropped: a session told nothing would assume the usual arrangement.
The worktree block's whole rationale is that the bind-mounted project is
the only path backed by host storage, which inverts here. Both worktree
workflows also stated its first bullet identically in their own fragments,
leaving one argument in three places and only two of them substitutable -
it is core's now, so a workflow says where the block goes and nothing
about what it says.
"outside the project directory" became "outside your working directory",
which is true in both modes rather than vacuous in one.
branderson
537ab56b04