- Shipped
- November 1, 2026 at 12:39 AM UTC
- Author
- Kamo
- Commit
- 50a5195
With the service deployed, its source showed the contract's prose left shapes open, and the canvas had guessed them differently. Each of these failed quietly against the deployed image: stages as { status, subStatuses } left every stage picker empty, members as { id: number, name } and roles as { id, title } left those lists empty, tokens was { lead, loan }, and a refused publish carried problems under detail, so they never reached the cards. automation-service a6f0a1f moves to flat lists and top-level problems. Until that is the running image both can answer, so the client reads both, and each is pinned by a test. Also adds what the service supports and the canvas lacked: pipeline stages on Set stage, the loan milestone trigger and Move the loan, a loan stream's own actions and merge words, a test run with no lead for a loan stream, number fields, and no value box for "has a value" and "is empty". A plan or rights refusal now shows the service's own sentence.