Development record
AGENTS.md tells a verifier to work on a copy made with git archive into a scratch directory, and the local scratch tier lives inside the worktree. A copy extracted there is not a git checkout, so every abcd verb run from it that reads git or the record store resolves upward to the live worktree that contains it. In the v0.13.3 cut the binary verbs run from the export read the release worktree, which was only equivalent because that worktree was clean at the content commit.
issueresolvedminoriss-2610090642392144
AGENTS.md tells a verifier to work on a copy made with git archive into a scratch directory, and the local scratch tier lives inside the worktree. A copy extracted there is not a git checkout, so every abcd verb run from it that reads git or the record store resolves upward to the live worktree that contains it. In the v0.13.3 cut the binary verbs run from the export read the release worktree, which was only equivalent because that worktree was clean at the content commit.
Grounds
- pursued: a verifier following either form extracts its copy where no enclosing checkout exists, so git -C <copy> rev-parse --show-toplevel fails; a form that drops the location, or a copy that still resolves to a worktree, shows it wrong
Frontmatter
| id | iss-2610090642392144 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610090642392144-agents-md-tells-a-verifier-to-work-on-a.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26101000000000062026-10-10 — A finding of the ruthless reviewer of lane-1 of run-2610101926030564 (iss-2610090642392144) is deferred, not fixed in the change that puts a verifier's copy outside every working tree: the bundled `OPINIONS` rule in `internal/core/rules/defaults/rules.json` ("The user's directory is theirs") still allows a verifier's copy in the checkout's `.abcd/.work.local/` tier, against the repository's own `CONCURRENCY` rule, AGENTS.md, itd-193 and the users-directory principle, which now forbid it. Reason: the bundled rule is injected into every managed repository, so changing it is a user-visible change the issue's remedy did not name, and it waits on a person's ruling, recorded as iss-2610102021042657.
- iss-2610102021042657Once the drain lane for iss-2610090642392144 lands, this repository's AGENTS.md and .abcd/rules.json say a verifier's copy goes outside every working tree, never under .abcd/.work.local/scratch/. The bundled default CONCURRENCY rule every managed repository receives and the principle the-users-directory-is-theirs.md still allow it in the checkout's .abcd/.work.local/ tier, and itd-193 and adr-2609091014087993 quote the archive command without saying where the copy goes. Changing the bundled rule changes what every managed repository is taught, so that lane left it alone.