bug(/wavemachine skill): wave_health_check blocks on pending deferral; defer-accept resolution not in skill body

[bakeb7j0]

Summary

wave_health_check blocks the /wavemachine loop when there's a pending deferral. Resolution requires running wave-status defer-accept N — which is not mentioned anywhere in the /wavemachine skill body. Operators / orchestrators get stuck without a documented path forward.

Two valid resolution shapes (pick one):

1. Make the skill responsible. /wavemachine calls wave-status defer-accept itself when launching after a deferral, with appropriate gating (e.g. only if the deferral was previously surfaced to the operator).
2. Document the workflow. Add a "Pending deferral resolution" subsection to the /wavemachine skill body explaining the manual defer-accept step.

Severity: medium — campaign launch fails with no clear recovery path; operator must dig into wave-status CLI.

Origin: Reported by sibling-campaign agent. @Scryer to expand and pick the resolution shape.

Implementation Steps

TBD — @Scryer to expand.

Test Procedures

TBD.

Acceptance Criteria

• /wavemachine either auto-accepts deferrals on launch, OR documents the manual step
• Operators following the skill body alone can recover from a pending-deferral block without reading source code or memory files

Dependencies

• None

Metadata

Severity: severity::major (campaign launch reliability)
Origin: sibling-campaign tracker. @Scryer owns expansion.