Release: Dogfood Promotion Report

Forgeflow 4.3.65 lands Phase 12 of the architecture intelligence path. The new dogfood report turns recent local evidence into a conservative keep, refine, or consider-promote recommendation before any higher automation is considered.

Dogfood Report

• /forgeflow-dogfood-report summarizes Phase 8-11 architecture, ownership, invocation, and context-pack injection evidence.
• render-dogfood-report.js reads local artifacts, flags missing or invalid evidence, and reports context-pack signals such as compact tokens, packet count, latest-insights status, and architecture guidance injection.
• The report can write .forgeflow/<project>/context/dogfood-report.md and .json only when --write is explicit.

Automation Boundary

• The recommendation is advisory only: keep read-only, refine, or consider narrow opt-in promotion.
• The helper does not patch files, call GitHub, push, publish, batch fixes, create PR comments, or promote automation automatically.
• Invalid or unsafe local evidence downgrades the report to refine instead of treating incomplete dogfood data as proof.

Install And Docs Coverage

• The new command and runtime helper are managed by install, update, health, runtime inventory, and release readiness checks.
• README and wiki pages now document the report alongside architecture docs, ownership maps, and invocation hints.
• Release gate docs include the dogfood report fixture test so future releases catch drift.

Validation

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