bridge-config

<!-- GTKB-ANTIGRAVITY-SKILL-ADAPTER Generated: true Generated by: scripts/generate_antigravity_skill_adapters.py Canonical source: .claude/skills/bridge-config/SKILL.md Canonical source sha256: 9c674fade46e95b76bf877f059253ddac687aba75d54eb3c054399b6f83d58a3 Generated at: 2026-06-16T19:22:39Z Do not edit this adapter directly. Edit the canonical source and regenerate. GTKB-ANTIGRAVITY-SKILL-ADAPTER -->

Bridge Dispatch Configuration

Use this skill when you need to inspect or diagnose the bridge dispatch topology without mutating project state. Trigger this skill for questions about bridge dispatcher configuration, dispatchability, selected harnesses, event-firing capability, rule eligibility, dispatch health, or whether configured harnesses are receiving work.

Answer those questions from dispatcher/TAFE state, status-bearing numbered bridge files, and the CLI surfaces below. Aggregate queue artifacts are not dispatcher topology, dispatch health, target-selection evidence, or current bridge-state authority.

Commands

gt bridge dispatch config
gt bridge dispatch status --json
gt bridge dispatch health --json

The direct aliases gt bridge config, gt bridge status, and gt bridge health are equivalent shortcuts. gt bridge dispatch config and gt bridge dispatch status are read-only status surfaces. gt bridge dispatch health exits non-zero when a required role has no eligible dispatch target.

What To Check

• Active role holders in harness-state/harness-registry.json.
• can_fire_events for event-source harnesses.
• can_receive_dispatch for headless dispatch targets.
• Headless invocation template presence.
• Rule eligibility from config/dispatcher/rules.toml.
• Last result evidence from dispatch-state JSON.
• Dispatch-run stdout/stderr/exit evidence when the question asks whether a target actually launched or returned work output.

Dispatch Model

Role assignment and dispatchability are orthogonal. Multiple active harnesses may hold the same role. Dispatch target selection filters by active status, can_receive_dispatch, declarative rules, and readiness, then ranks by the configured availability, cost, quality, and precedence order.

gt bridge dispatch status is the topology/eligibility surface. gt bridge dispatch health must reveal operational health: recent launches, exit codes, returned output, stderr, failure counts, stale or absent dispatch evidence, circuit breakers, and contradictory dispatcher state. A green result must not be treated as proof of work delivery unless it includes that runtime evidence.