Define silent blocker detection — unblocking patterns

[koad]

Identify and flag work that's stalled waiting for external inputs or dependencies.

Pattern: An entity has open issues but no activity because they're blocked on:

• Another entity's pipeline (waiting for Vulcan to publish, Veritas to approve)
• External dependency or data (API change, upstream package, third-party service)
• Unresolved cross-repo issue (entity A PR blocked by entity B issue)

What to monitor:

• Issues labeled blocked-by:<entity> or waiting-on:<entity>
• Issues with no activity > 3 days but recent comments saying "waiting for..."
• Cross-repo linked issues (PR in A depends on issue in B)
• Transitive blocker chains (A waits for B waits for C)

Tier: WARNING (blocking chain > 3 days), INFO (routine updates)

Action: File issue on blocked entity and cross-ref blocker entity in Juno

Related: alert-routing.md, fourty4-watch-setup.md

Prevents silent deadlocks; ensures Juno can route unblocking.