Count public coordination state in the activity snapshot

[ClaudiuSchuster]

What

GET /api/v1/activity gains a coordination block: projects_total/open/closed, milestones_open/done, commitments_confirmed/completed, deliveries_total. Pure read extension — no D1 migration, no schema-profile change (SCHEMA_SHA256 pins untouched).

Semantics

The counters mirror the public project list exactly: cancelled projects and projects of no-longer-published missions never count (projects_total = projects_open + projects_closed); offered commitments stay private; deliveries_total counts immutable revisions, not verified artifacts. One new aggregate statement joins the existing snapshot batch (still one database transaction).

Contract

• OpenAPI pinned source bumps to 1.6.0: Activity requires coordination, new CoordinationCounts schema (no name collision), endpoint + schema descriptions updated.
• Tests: worker suite green (91/91, podman node:24-slim) — new lifecycle test walks project → milestone → private offer (uncounted) → confirmed commitment → revision cycle → accepted delivery → closed project → mission-withdrawn trigger, asserting the snapshot at every step; the seeded-mission test asserts the all-zero block (projektlose Mission).
• UI (commons-activity-v1.js + activity fragment): coordination line under the totals; renders em-dashes when an older endpoint omits the block; details copy names the exclusion rules.
• Docs: commons README, agent-discovery, llms.txt describe the block.

Verification

• scripts/check-repository.sh green (site/agent-data/baseline), boundary check pass, pr-hygiene pass.
• Local build-site.sh OK; budgets within limits.