Release: Connected Readiness Track

Forgeflow 4.3.13 lands the Connected Readiness track: guided repair now checks installed runtime helpers, release readiness gets a non-publishing preflight, code maps become living project guidance, agent feedback feeds project intelligence, and the new-user pilot path becomes state-aware.

Install And Release Readiness

• /forgeflow-repair now verifies installed runtime helpers against the canonical runtime manifest and points broken installs at /update-forgeflow --repair.
• /forgeflow-release-readiness runs the documented local release-check list, groups blockers by area, supports plan-only mode, and never tags, pushes, publishes, or calls GitHub.
• Release-readiness and repair checks scrub unsafe Node preload environment where needed and fail closed when required release-check source is missing.

Living Project Map

• /forgeflow-code-map and /forgeflow-trends now expose a living project-map block based on code-map history.
• Categories include baseline, missing history, new hotspot, cooling hotspot, import-gap growth or reduction, changed-section churn, graph-growth score, and stable structure.
• Import-gap movement is tracked per metric so unresolved and dynamic import changes cannot hide each other.

Agent Feedback Intelligence

• rollup-agent-feedback.js now summarizes correction themes, promotion candidates, stale markers, skipped private lines, and public-safe examples.
• build-project-intelligence.js threads those signals into the agent-feedback section and review-prep notes while keeping promotion manual and advisory-only.
• Staleness wording calls out old records without implying the whole feedback log is stale.

State-Aware New-User Path

• /forgeflow-pilot --path new-user now starts with guided repair, release-readiness preview, and smoke before the first real task.
• Project orientation includes project trends, living code map, project learnings, project intelligence, and agent-feedback rollup.
• The public-safe result template asks for project-intelligence readiness, living project-map status, and agent-feedback signal so the next task can start with better guidance.

Validation

• Each phase passed focused tests, full scripts/forgeflow/test-*.js, docs/release guards, and Forgeflow review.
• Security-sensitive release-readiness hardening received focused verification before merge.
• The release gate passed for the final packaged version.