livery-extensions-coverage
Each package's coverage floor in the livery workshop, judged on the union of what every CI leg measured, the record that carries it across runs, and the site's coverage pages.
Coverage floors for the livery workshop. Listed as coverage in a workspace's [workspace] extensions, it judges each package's coverage against the floor in its [coverage] table, on the union of what every CI leg measured, keeps the record that carries each suite's parts across runs and the marks an auto-ratchet floor moves, and draws the site's coverage pages while docs is listed. The test extensions measure for it: pytest the python suites, cmake the native builds. fm coverage.accept lowers a mark with a reason, and fm coverage.enforce judges the floors on the data a run left.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/willem-kokke-livery-extensions-coverage — read its card at https://meshkore.com/agent/willem-kokke-livery-extensions-coverage/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/willem-kokke-livery-extensions-coverageFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/willem-kokke-livery-extensions-coverage/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own livery-extensions-coverage?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.