Skip to content

Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.

docs(api): document pullboard badge and teach it to agents [A1,I11]

Corey Olsonc56e5d760074
diff --git a/docs/api.md b/docs/api.md
index b09d3fdb..75e85090 100644
--- a/docs/api.md
+++ b/docs/api.md
@@ -124,6 +124,7 @@ For example: `flow: review wait average 61 min (1 measured; > 60 min); bottlenec
| `run` | `version:number`, `messages:array` |
| `sweep` | `version:number`, `messages:array` |
| `next` | `version:number`, `item:object`, `review:boolean`, `held:boolean`, `shared:array` |
+| `badge` | `version:number`, `items:number`, `checked:number`, `percent:number\|null`, `changed:array` |
| `check` | `version:number`, `id:number`, `green:boolean`, `seconds:number`, `check:string`, `receipt:object`, `report:string` |
| `check accept` | `version:number`, `id:number`, `digest:string`, `check:string` |
| `claim` | `version:number`, `id:number`, `renewed:boolean`, `leaseUntil:string`, `digest:string` |
diff --git a/skills/pullboard-run/SKILL.md b/skills/pullboard-run/SKILL.md
index 2e57de28..de6ea26e 100644
--- a/skills/pullboard-run/SKILL.md
+++ b/skills/pullboard-run/SKILL.md
@@ -119,6 +119,7 @@ When the board lands in two tiers (`landing.publish` set to `"separate"` in pull
| A site or relay down | `pullboard relay` prints the relay link's state; open the site's front page | you, at the start of each cycle |
| npm and the site disagreeing | `npm view <package> version` beside `pullboard version` and the version the site shows | you, after each release |
| Main CI red | the CI's latest run on the trunk (on GitHub, `gh run list --branch main --limit 3`); `pullboard submit` names a test that fails on main too | you, at the start of each cycle, and the builder's shout |
+| The Pullboard-verified badge out of date | `pullboard badge` rewrites the board-derived badge files offline (landing also refreshes them) and lists what changed | you, after a merge that skipped landing |
| A release past its day | `pullboard health`: `release <tag> overdue` | the listener's loop |
A row you check by hand is a check waiting to be built. When one catches something twice, add it to the board as an item, the way #772 grew out of a coordinator's private board monitor.