Release: Efficiency And Token Reduction Planning

Forgeflow 4.3.35 targets the biggest measured efficiency gaps: over-budget context packs, noisy command output, broad memory hits, repeated validation, and stale local guidance artifacts.

Context Budget Control

• New /forgeflow-context-wave-plan reads the latest context telemetry, file manifest, and synthesis input, then recommends staged review waves when packets exceed the target token budget.
• Context-pack memory hits now dedupe repeated text, cap low-signal source repetition, and weight project learnings plus implementation notes ahead of broad history.
• The planner stays read-only: it does not rebuild packets, spawn agents, edit files, commit, or push.

Command Output Capture

• New /forgeflow-capture-output compacts already-produced command output safely and can save a failure digest from provided output.
• Unsafe exact-output classes such as diffs, patches, SHAs, and exact file lists remain raw with an explicit reason.
• The helper does not execute commands; it only consumes supplied output or a supplied file.

Validation And Freshness Planning

• New /forgeflow-validation-plan maps changed files to focused validation commands and states when full suite or source smoke are required.
• New /forgeflow-stale-artifact-plan converts stale trend, latest-insights, failure-digest, and context-budget signals into minimal refresh commands.
• README, workflow docs, user paths, context intelligence docs, health inventory, install manifest, update tests, and release gates cover the new helpers.

Validation

• Full scripts/forgeflow/test-*.js suite
• node scripts/forgeflow/smoke-check.js --mode source --json
• git diff --check
• Install, update, command coverage, runtime-helper, release-version, docs, and wrapper-safety guards