feat(w0-pr4): Shift Crew Phase 6 — hooks, settings wiring, TAC entries

[POWERFULMOVES]

Summary

• Add kilo-brief-check.sh PostToolUse hook — validates KiloCode command brief format (.kilo/command/*.md) on every Edit/Write; advisory-only, always exit 0
• Add shift-crew-trail.sh PostToolUse hook — emits NATS branch.<segments>.trail.v1 events when Shift Crew pipeline tools are modified; graceful NATS fallback
• Wire both hooks into .claude/settings.json with Edit|Write matchers (3s / 5s timeouts)
• Add Phase 6 TAC subtree n4090.shift-crew covering 7 skill nodes + 2 hooks for the 4090 node

Context

This is the Phase 6 addition to node-4090-laptop.tac.yaml — Shift Crew skills (beats_to_voice, bpm_encoder, analyze_beats, beats_to_cgp, geometry_bridge) wired into Claude Code sessions via hooks and skills.

The branch also carried the w0-pr3/w0-pr4 probe script work and CI fix, all of which were already on main via PRs #1476, #1481, and the d415b565d fix. Those commits were dropped during rebase — this PR is net-new content only.

Test plan

• Edit a .kilo/command/*.md file and verify kilo-brief-check.sh fires (stderr warning if sections missing, no block)
• Edit a Shift Crew tool file and verify shift-crew-trail.sh fires; check NATS branch.feat.w0-pr4-ghost-detector.trail.v1 subject if NATS available
• Confirm CI passes (pat-health-check should now parse cleanly — same fix as main's d415b565d)
• TAC tree n4090.shift-crew entries visible under Phase 6

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@POWERFULMOVES, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 1 review/hour. Refill in 12 minutes and 14 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4a8ccce4-d22e-477d-a449-e06b725be481

📥 Commits

Reviewing files that changed from the base of the PR and between c904a19 and f0f0b05.

📒 Files selected for processing (2)

• .claude/hooks/shift-crew-trail.sh
• pmoves/docs/AGENTS/AGNOTE4482PHI.t1.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/w0-pr4-ghost-detector

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}