2 Commits

Author	SHA1	Message	Date
nux	c66dc4594c	fix(hook): enable cross-prefix bead hooking with database routing ... The `gt hook` command was failing to persist hooks for beads from different prefixes (e.g., hooking an hq-* bead from a rig worker). The issue was that `runHook` used `b.Update()` which always writes to the local beads database, regardless of the bead's prefix. Changes: - Use `beads.ResolveHookDir()` to determine the correct database directory for the bead being hooked, based on its prefix - Execute `bd update` with the correct working directory for cross-prefix routing - Call `updateAgentHookBead()` to set the agent's hook_bead slot, enabling `gt hook status` to find cross-prefix hooked beads - Add integration test for cross-prefix hooking scenarios This matches the pattern already used by `gt sling` for cross-prefix dispatch. Fixes: gt-rphsv Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-26 12:18:43 -08:00
slit	2d56b6c02b	test: Add E2E integration tests for hook slot verification (mi-3zc) ... Add comprehensive integration tests covering hook slot operations: - BasicHook: Verify bead can be hooked to an agent - Singleton: Document that bd allows multiple hooks (gt enforces singleton) - Unhook: Verify hook removal via status change - DifferentAgents: Verify independent hooks per agent - HookPersistence: Verify hooks survive beads instance recreation - StatusTransitions: Test open -> hooked -> open -> hooked -> closed Also fix missing json import in install_integration_test.go. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-04 19:46:27 -08:00