Repository navigation
A gate-1 evaluator can read the research when the record lives elsewhere
With personal records, including every shadow install, the gate into refined
raised its evaluator in the primary worktree and pointed it at the item in the
records clone, outside that worktree. A sandboxed seat could not open it: on
Windows, Codex runs as a separate account and was refused research.md, so an
item that asked for research returned BLOCKED at its first gate every time.
The research raise's own kept output had the same problem.
Now a raise in the primary worktree gets the item the way every gate after a
delivery already did. Its artefacts are copied into the worktree for the raise
and taken away afterwards, and its output is kept there and brought home to the
record. The copy's folder ignores itself, so an interrupted raise leaves nothing
for Git to stage. The evaluator at that gate is also handed the research whole
in its briefing, as it is handed the brief, so it no longer depends on opening a
file.
A Codex raise writes only to its own worktree
A Codex raise inherited any [sandbox_workspace_write] writable_roots from the
practitioner's own ~/.codex/config.toml, so a root written for another project
was writable from every raise. remit now clears that list for the raise, and the
worktree, its scratch root and the system temp are its only writable places.
An unrun delivered-when line does not pass
An evaluator could pass a delivery while saying the proof for one of its
delivered-when lines was UNRUN. Its pull request then left draft as ready, even
when the unrun part was exactly what was failing. Evaluators are now told that a
delivered-when line whose proof they could not see run is not met, and that a
verdict leaving one unmet is not a pass. It is a FAIL where the delivery could
have produced the proof, and BLOCKED where nothing before the pull request
can, such as hosted CI. remit still does not read CI.
Upgrading
Nothing to migrate. An item stopped BLOCKED at its gate into refined
because research could not be read continues with remit resume. If your
Codex config lists writable_roots for another project, your own Codex
sessions keep them; only remit's raises clear them.
Validation: the kept-output suite adds a personal-records item with research,
taken through the gate into refined. It asserts that the research raise and
its evaluator keep output inside the primary worktree, that what research kept
reaches the record, and that the evaluator finds that output and the item's
research.md in the worktree and is handed the research. It also asserts that
the copy is gone afterwards and Git reports nothing under the item path. The
invocation suite asserts that a Codex raise clears writable_roots and that the
research handed to an evaluator reaches its briefing. The full Linux unit tier
passes.