Release: Dashboard Evidence API

Forgeflow 4.3.67 lands Phase 14 of the dashboard and operating-model track. The optional local dashboard now has a read-only readiness API that gathers existing project evidence into one compact response.

Readiness API

• GET /api/readiness returns project health, learning status, context budget, release readiness, dogfood report, and dogfood refresh-plan cards.
• The aggregator reads existing local artifacts under the project Forgeflow state instead of recomputing or refreshing them.
• The response includes a compact next action so the dashboard can point users to the evidence command that matters most.

Safety Boundary

• The endpoint is read-only and sends Cache-Control: no-store.
• It does not write artifacts, spawn agents, run shell commands, refresh evidence, call GitHub, or export telemetry.
• Project artifact paths are normalized so the API does not expose absolute local filesystem roots.

Docs And Planning

• The dashboard docs describe the new readiness endpoint and its non-mutating boundary.
• The dashboard service context documents the response shape and privacy expectation for future UI work.
• The roadmap records Phases 14 through 18 for the dashboard panel and cross-project operating-model track.

Validation

• node --test services/dashboard/__tests__/readiness.test.js
• Full scripts/forgeflow/test-*.js suite
• node scripts/forgeflow/smoke-check.js --mode source --json
• node scripts/forgeflow/render-release-readiness.js --json
• git diff --check