os-sdlc phase 3.5: register the PostToolUse hook in the marketplace manifest #333
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#333
Loading…
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?
Hook registration/matcher config is explicitly TBD (dispatch-hook.md). Do this LAST before shakedown — registration makes the runner live on every Agent call machine-wide. Depends on #330 and #332.
Deviation incident 2026-08-15 — /os-sdlc:implement run for #402+#405, session https://claude.ai/code/session_01GSYJVRGmBiLGjPppHjY3bZ. Deviating skill: plugins/os-sdlc/skills/implement/SKILL.md.
Expected: the PostToolUse hook advances the pipeline on its own when a pipeline agent finishes. Actual: every stage of both tickets needed hand-piped bare-name events (echo '{"tool_name":"Agent","tool_input":{"subagent_type":"code-probe"},"cwd":...}' | ruby plugins/os-sdlc/hooks/post_tool_use.rb) because (a) the hook is not armed in the marketplace manifest and (b) dispatches carry namespaced subagent_type (os-sdlc:code-probe) which the hook does not map to bare stage names. Note the events must use tool_name Agent, not Task. Repro context: any /os-sdlc:implement run in a session on this machine.
Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.