Review handoff
Phonton should hand back evidence, not just prose. A useful handoff answers:
- What goal was attempted?
- What plan was followed?
- Was swarm mode enabled or disabled, and why?
- Which files changed?
- Which checks ran?
- What passed, failed, or was skipped?
- What index backend and context sources influenced the run?
- What MCP or extension evidence was involved?
- What still needs human review?
Inspect the latest review payload:
phonton review latest
phonton review latest --json
Record a human decision:
phonton review approve latest
phonton review reject latest
phonton review rollback latest 1
Handoff evidence
v0.19.0 threads more planning and capability evidence into typed surfaces:
| Evidence | Why it matters |
|---|---|
PlanGraph | Shows assignments, dependency intent, expected touch scopes, and conflict groups. |
index_backend | Names whether code retrieval used local HNSW or configured Qdrant. |
McpCapabilitySnapshot | Preserves negotiated protocol, tool descriptors, and proposed permission rules when capability preview was used. |
PermissionLedger | Records approved or denied privileged actions. |
VerifyReport | Separates passed checks, findings, and skipped checks. |
Good handoff language
Use concrete status:
| Status | Use when |
|---|---|
| Ready for review | Verification passed and the diff is scoped. |
| Needs direction | The plan or implementation hit an ambiguity. |
| Failed verification | A check failed and the failure is included. |
| Not run | A check was skipped and the reason is stated. |
Do not call work done when verification did not run.