refactor(claude-hooks): retire the issue-ref hook #949
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure!949
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/ff54-retire-issue-refs"
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?
Rollout half of retiring
check-issue-refs.sh. The script itself is deleted in agentic-os, and theup-to-date.pyassertion is already dropped in agentic-os-kai (393da23).Why
The hook policed how an agent spelled a reference in chat rather than anything durable. Its Stop leg also read the transcript slice after the last
userrecord, and tool results are recorded asuser, so a tool-heavy turn inspected an empty string rather than the reply.What unwires
Three tasks, following the retirement pattern this role already uses for the o2r nudge and the agent-compose refresh:
mcp__forgejo__(create_issue|edit_issue|comment_issue)that no role ever wrote. It exists in a converged host'ssettings.jsonas hand-wiring, so unwiring by marker is what keeps it from outliving the hook.Drop all three once every fleet host has converged past this, per the note in the header block.
🤖 Generated with Claude Code