status
Transitions a component's build lifecycle state after pre-commit gates and delta/seam tests pass, recording readiness, QA, verified, failed, or stale outcomes.
Instructions
Step 4 (Transition Status): Transition a component's build lifecycle status (e.g. new_status='VERIFIED' after pre-commit gate and delta/seam tests pass).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"component": "<component>",
"new_status": "<new_status>"
},
"name": "status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| board | No | Target board name (default: lattice_core) | |
| reason | No | Optional failure diagnostic | |
| core_tag | No | Optional core tag | |
| build_tag | No | Optional build tag | |
| component | Yes | Component scope ID | |
| new_status | Yes | Target status (READY, IN_PROGRESS, IN_QA, VERIFIED, FAILED, STALE) | |
| project_root | No | Optional repository root path (auto-discovered by board name or file paths if omitted) |