Release: Follow-Through And Evidence Refinement

Forgeflow 4.3.34 adds five local-first refinements that make release follow-through, command argument validation, review-auto inputs, learning policy changes, and first-task adoption decisions easier to trust.

Release Follow-Through

• New /forgeflow-release-follow-through checks post-publish release verification, update verification, and runtime consumability in one read-only report.
• The helper maps update verification states into pass, info, or attention so ready installs do not look unresolved.
• The command does not tag, push, publish, call GitHub, repair installs, or edit settings.

Safer Command And Review Inputs

• New /forgeflow-command-args validates boolean, value, and path flags against an explicit allowlist without executing commands.
• New /forgeflow-review-evidence-schema --findings <json> checks captured findings for missing title, file, source, tier, path hazards, and obvious secret material before review-auto classification.
• /forgeflow-review-auto-evidence now includes review evidence schema status and issue counts in its local artifact.

Learning And Adoption

• /forgeflow-learning-policy --compare <json> previews policy deltas and advisory impact labels without writing policy state.
• New /forgeflow-first-task-adoption-loop turns first-task and first-useful-win evidence into a repeat, fix, defer, or expand decision.
• The adoption loop reports aggregate counts only, keeping raw local outcome records private.

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