beo-debug

Read

• br show <issue-id> --json
• .beads/artifacts/<issue-id>/TICKET.yaml and state.json
• .beads/artifacts/<issue-id>/runtime-events.jsonl when present
• Evidence/log files referenced by the caller
• beo-reference -> registry/runtime-event.schema.json before appending caller-routed runtime events

Caller contract

beo-debug may be invoked only by:

1. beo-execute,
2. beo-review,
3. or an explicit operator request to diagnose a BEO blocker.

Two modes are allowed: