Release: Lean Delivery Guidance

Forgeflow 4.3.69 completes the lean delivery track. Agents now get minimum-sufficient-solution guidance, over-engineering review, simplification ceiling capture, lean delivery metrics, and quality-gated lean context injection without changing the core safety model.

Lean Delivery Path

• /forgeflow-lean-decision produces read-only minimum-sufficient guidance with reuse candidates, avoid-first work, validation minimums, known ceilings, and upgrade triggers.
• /forgeflow-lean-review adds a separate over-engineering lane for delete, stdlib, native, reuse, yagni, shrink, and prose-bloat findings.
• /forgeflow-lean-report summarizes local aggregate lean signals: diff size, ceiling capture, review/prose warnings, context savings, and telemetry quality.

Context Injection

• Context packets now include a compact Lean Guidance block only when lean-decision, lean-report, latest-insights, profile, operating-model, and telemetry gates pass.
• Agent context contracts mark lean guidance as advisory and verify-before-use.
• The guidance tells agents what to prefer first, what to watch, and when to upgrade without forcing deletion or dependency removal.

Safety Boundary

• Lean guidance cannot override the user request, current code, tests, security, accessibility, validation, or data-loss safeguards.
• It never deletes code, removes dependencies, applies review-auto fixes, changes routing, exports telemetry, or promotes org-wide policy.
• Raw command output, diffs, failure evidence, review evidence, and user-requested explanations remain raw-required.

Validation

• Focused lean-decision, lean-review, lean-report, output-contract, implementation-notes, context-pack, context-contract, context-budget, docs, install, update, runtime, and health checks
• Full scripts/forgeflow/test-*.js suite
• node scripts/forgeflow/smoke-check.js --mode source --json
• git diff --check