Agent context compatibility — landed evidence

The canonical policy link, measured context budget, reusable manifest and black-box acceptance fixtures are live and passing.

Canonical user policy flowing through the Codex entrypoint and project instruction chain into a verified context manifest. — The implementation verifies each layer by path, byte count and digest without exposing instruction contents.

Quick status

shipped

Compatibility shim

~/.codex/AGENTS.md resolves to ~/.agents/AGENTS.md.

pass

Budget

65,536-byte limit; 32,754 project bytes; 32,782 bytes remaining.

pass

Acceptance

12 focused fixtures and 1,193 total tests passed.

clean

Live doctor

Exit 0 with no findings for the Reckon checkout.

Outcomes

Item	Result	Commit / artifact	Evidence
Reusable target-path preflight	landed	`02d7276` · `reckon/agent_context.py`	Deterministic JSON and concise human reports.
CLI doctor	landed	`reckon agent-context doctor`	Missing, unreadable, split-brain and overflow failures return nonzero.
Canonical entrypoint	verified	`~/.codex/AGENTS.md`	Canonical-link relationship; matching SHA-256 digest.
Instruction budget	verified	`~/.codex/config.toml`	Largest measured nested project chain is 35,547 bytes; configured limit is 65,536.
Regression suite	pass	`tests/test_agent_context.py`	12 focused; 1,193 total passed in 28.84 seconds.

Negative findings retained

Read-only inspection confirmed Nova still contains stale worktree recipes that conflict with the canonical global git policy. S5 did not mutate that unrelated repository; the doctor now makes split-brain and target-path drift observable without silently mirroring policy.

What’s next

Use the manifest in bounded execution

The next dependent plan can consume this target-path preflight before dispatch. Typed provenance work in the same sprint will make this page a first-class Evidence artifact.

Execution and Orchestration Hardening