---
name: connector:status
description: Show where a connector run has got to — phases, scope, open gaps
triggers:
  - /connector:status
  - connector status
  - show progress
argument-hint: <provider>
---

# Status

`$ARGUMENTS`

Everything is derived from the run file. Nothing here is inferred from conversation history —
if it is not in `run.json`, it did not happen.

```bash
node ${CLAUDE_PLUGIN_ROOT}/scripts/state/run.js summary --provider {{provider}}
```

```json
{
  "provider": "ashby",
  "currentPhase": "validate",
  "phases": { "research": "complete", "build": "exhausted", "validate": "pending" },
  "openGaps": 3,
  "outcome": null
}
```

For the full record — scope contract, gap ledger, per-phase unmet checks:

```bash
node ${CLAUDE_PLUGIN_ROOT}/scripts/state/run.js read --provider {{provider}}
```

## Reading it

| Phase status | Means |
|---|---|
| `pending` | Not started |
| `complete` | Its gate exited 0 |
| `exhausted` | The gate never passed but the loop stopped converging. The run moved on, carrying the gaps. **Not an error.** |

| Outcome | Means |
|---|---|
| `null` | Still running |
| `complete` | All three gates passed |
| `partial` | At least one phase exhausted — connector delivered with its gap list |

## Resuming

Re-issue the original request. Completed phases are skipped; the run picks up from the first
phase that is not yet terminal. There is no separate resume command.