Add a lint rule to block the ../AGENTS.md reference pattern from returning #172
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/agentic-os#172
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from coilyco-bridge/agentic-os-kai#267 (the
../AGENTS.mdreference-pattern sweep, now complete across all 17 sibling repos).Add a catalog lint rule so the brittle relative-path opener can not return. A repo
AGENTS.mdshould never open with:The relative path only resolves when the repo sits as a sibling of
agentic-os-kai/; from a worktree, remote build, or isolated clone it points nowhere. The canonical form is the coily-style header:Suggested shape: extend
context-load-points(or a small newagents-mdcheck) to fail when a trackedAGENTS.mdcontains a\../AGENTS.md`reference. Wire it into.pre-commit-hooks.yaml`, then bump the rev across consumers.Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag:
burndown-2026-06.