report-run

Files (1)

• SKILL.md

SKILL.md (first lines)

# Report run

Tool: `run_report`

## When

Starting work, hitting a blocker, or finishing a claim.

## How

- `work_id` + `status` (`running` | `blocked` | `completed`) + short `phase` / `summary`.
- Use `idempotency_key` for safe retries.
- Reuse `run_id` when continuing the same run.
- **No secrets** in summaries.

## Rules

- Completed → In Review. Never move work to Done yourself.
- Do not substitute chat comments for run reports.
- Blocked summaries must name the missing human/input path.

## Execution ownership (INV-943)

`work_claim` returns a secret `claim_token` and an `executionId`. Keep the token in this execution’s secret state; never put it in a comment, receipt, log or Git. Pass `claim_token` when renewing the lease, reporting a run, attaching evidence, releasing your claim (`work_claim_release`, with a reason), or retracting your own pre-acceptance evidence (`evidence_retract`, with a reason). Sharing an actor identity does not share execution authority. After lease expiry, acquire a new claim and use its new token; old runs cannot resume. A lost token cannot be recovered from context: wait for expiry or ask a person to release the claim in the UI. Completed runs retain their token binding for attaching evidence after completion.

From fakechris/Involute, Apache-2.0.

More from fakechris/Involute