Release: Install Confidence And Next-Work Guidance

Forgeflow 4.3.15 closes the loop from local learning to release confidence. It keeps updater repair usable during partial installs, turns project intelligence into advisory next-work candidates, normalizes pilot evidence state fields, and adds a release-to-install preflight before a release is treated as ready.

Update And Install Safety

• update-forgeflow.js can now repair installs that are missing the newer runtime-helper-contract.js bootstrap helper.
• The updater only tolerates that exact missing bootstrap dependency; unrelated module and syntax failures still surface.
• render-release-readiness.js now includes a non-mutating release-to-install preflight.
• The preflight verifies every managed runtime helper source is present, regular, managed, and resolves inside the checkout.
• Preflight blockers use the distinct release-to-install-preflight kind.

Project Intelligence

• build-project-intelligence.js now emits advisory next_work_items alongside the next-work brief.
• Each candidate includes priority, source, rationale, start-with hints, validation hints, and a proof boundary.
• Same-source risk signals remain distinct, and internal dedupe state does not leak into JSON output.

Pilot Evidence

• record-pilot-evidence.js now records the state-aware fields consumed by pilot rollups.
• Project-intelligence readiness, living project-map status, and agent-feedback signal values are normalized before writing.
• Invalid, falsy non-string, and whitespace-only state values are rejected instead of being silently dropped.

Validation

• Focused tests, full scripts/forgeflow/test-*.js, live release readiness, docs checks, and Forgeflow reviews passed.
• Review fixes covered same-source risk collapse, validation edge cases, source-tree ownership, preflight proof boundaries, and blocker classification.