docs(global-rules): make canonical worktree path <repo-name>/<worktree-name>#13
Open
andrei-hasna wants to merge 1 commit into
Open
docs(global-rules): make canonical worktree path <repo-name>/<worktree-name>#13andrei-hasna wants to merge 1 commit into
andrei-hasna wants to merge 1 commit into
Conversation
…e-name> Rule 8 (and the mirrored global-prompt and Antigravity-overlay entries) documented only the worktree ROOT $HOME/.hasna/repos/worktrees, so agents placed worktrees flat or under a <station-id> segment. Spell out the canonical two-segment path $HOME/.hasna/repos/worktrees/<repo-name>/<worktree-name>, forbid the station-id and flat variants, and point to 'repos scan'. Matches knowledge convention k_mrj32xhu_efxkxl (reaffirmed 2026-07-20 after a station01 drift audit: 40 flat + ~201 station-prefixed of 362 worktrees). The @hasna/repos enforcement gap is tracked as open-repos task 10a0f26e.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Rule 8 (CODE AND LANDING RULES) and its mirrored entries in the global-agent prompt (line 150) and the Antigravity overlay (line 329) documented only the worktree root
$HOME/.hasna/repos/worktrees. That under-specification let agents place worktrees flat (.../worktrees/<name>) or under a<station-id>segment (.../worktrees/station01/<repo>/<name>).This change spells out the canonical two-segment path:
$HOME/.hasna/repos/worktrees/<repo-name>/<worktree-name>(e.g.
.../worktrees/codewith/pr307-attestation), explicitly forbids the station-id and flat variants, and tells agents to runrepos scanafter a manualgit worktree add.Why
Read-only drift audit on station01 (2026-07-20): of 362 worktree markers under
~/.hasna/repos/worktrees, only 91 followed<repo>/<worktree>; 40 were flat and ~201 were station-prefixed. The rule text was the root cause of the ambiguity.Source-of-truth alignment
k_mrj32xhu_efxkxl("Git worktree location convention") already specifies<repo-name>/<worktree-name>and was reaffirmed 2026-07-20 (station-id layout retired).@hasna/reposenforcement gap (no worktree-create/validate command) tracked as open-repos task10a0f26e.Verification
bun test src/index.test.ts-> 38 pass / 0 fail (assertions at lines 871-872 still hold; change is string-literal-only).Rollout note (needs maintainer)
This is a fleet-wide agent-rule change. After merge it must be published (
@hasna/identities) and rolled out via instructions/configs so all machines re-render CLAUDE.md/AGENTS.md. A[POLICY]announcements heads-up should precede that rollout. Do not auto-merge without that coordination.