hook-augment emits nothing on 0.9.1-rc.1, including payloads that work on 0.9.0

[dergachoff]

Problem

hook-augment on v0.9.1-rc.1 (macOS arm64, release tarball, permanent daemon active) exits 0 with no stdout/stderr for every payload, including ones 0.9.0 answers.

Evidence

One-file Python repo, indexed by the rc.1 binary:

echo '{"session_id":"probe","hook_event_name":"PreToolUse","tool_name":"Grep","tool_input":{"pattern":"create_stripe_checkout","path":"<repo>"},"cwd":"<repo>"}' | codebase-memory-mcp hook-augment

binary	project name	result
0.9.0	default path slug	emits additionalContext, 1 symbol
0.9.1-rc.1	default path slug	silent, exit 0
0.9.1-rc.1	custom name	silent, exit 0

SessionStart and SubagentStart payloads are silent too, so the cbm-subagent-reminder hook the rc installer adds is a no-op. cli search_graph returns correct results for the same projects, so this is specific to the hook path. Custom-name resolution from #1069 worked when I ran main at d587dea; on rc.1 both custom and default-slug are silent.

Expected fix

hook-augment emits additionalContext again for indexed projects; a regression test on the release path would catch the next one.

[DeusData]

Thank you for testing known-good 0.9.0 payloads against 0.9.1-rc.1. The hook path has a tight default deadline and silent skip behavior, so a zero-output result can hide whether startup, daemon dispatch, or augmentation consumed the budget. I have routed this as a high-priority 0.9.1-rc stability regression; the red case should assert both bounded completion and visible diagnostics for each failure stage.