Release: Efficiency Gaps, Outcome Capture, And Runtime Grouping

Forgeflow 4.3.37 adds a safer way to find the next highest-leverage improvement, tightens outcome evidence guidance, and makes runtime drift easier to understand before an update or release.

Efficiency Gap Planning

• New /forgeflow-efficiency-gaps reviews local evidence and ranks the top five token-reduction, workflow-efficiency, or quality gaps.
• The planner stays advisory: it does not edit files, rebuild packets, spawn agents, commit, push, or change runtime installs.
• Gap output now includes evidence, boundaries, safe slices, validation commands, and a next-command recommendation for each phase.

Learning And Failure Evidence

• /forgeflow-learning-status now surfaces outcome-capture readiness and recorder prompts directly in the learning health view.
• Outcome capture now uses local JSONL evidence as the source of truth when stale rollups disagree with current project artifacts.
• Validation plans now include failed-command capture prompts so test, lint, build, and smoke failures can feed the failure digest without rerunning unsafe commands.

Runtime Drift Clarity

• Runtime helper inventory now groups helpers by feature area so large install or drift reports are easier to triage.
• /forgeflow-version and runtime drift snapshots now summarize missing helper groups before listing individual files.
• Large missing-helper lists are capped in detailed output while preserving totals and grouped remediation context.

Validation

• Full scripts/forgeflow/test-*.js suite
• node scripts/forgeflow/smoke-check.js --mode source --json
• git diff --check
• Release-version, command coverage, docs links, install manifest, update, runtime inventory, outcome capture, validation capture, and efficiency-gap tests