claw/docs/superpowers/specs/2026-04-19-g6-host-bridge-callback-state-verification-design.md

G6 Host-Bridge Callback State Verification Design

Date: 2026-04-19 Status: Draft Upstream Report: 2026-04-19-g6-host-bridge-callback-semantics-report.md

1. Intent

This design defines the next bounded slice after G6 host-bridge callback semantics.

The target is:

G6 host-bridge callback state verification

2. Why This Slice

The callback states are now explicit, but they have not yet been bounded into a verification-oriented slice.

The next pressure is narrower:

1. verify state transitions as a bounded model
2. keep that verification separate from real execution and host-runtime implementation

3. Scope Boundary

This design is limited to callback state verification only.

It may include:

1. defining bounded verification targets for ok/partial/blocked/error
2. defining what evidence is sufficient for each transition
3. defining how verification narrows a later G6 real-sample entry

It must not include:

1. implementing host-runtime directly
2. executing a G6 real sample
3. opening G8
4. reopening G7

4. Target Outcome

The bounded target outcome is one state:

1. one bounded G6 host-bridge callback state verification plan

5. Exit Condition

This design is complete when implementation can be bounded to one plan that:

1. freezes callback-state verification scope
2. defines bounded verification targets
3. emits one bounded follow-up plan