Release: Release And Context Verification Refinements

Forgeflow 4.3.27 tightens the release loop and agent-context safety checks. It adds a post-release install verification command, validates generated agent packets against their context contract, and makes local learning signals age-aware before agents rely on them.

Release Verification

• New /forgeflow-post-release-install-verify combines release verification, install consumability, and downstream smoke into one read-only after-update verdict.
• render-release-notes.js can include changed files and optional release evidence JSON, so draft release notes separate substantiated validation from advisory context.
• Release gate docs and tests now cover the new post-release verification helper.

Agent Context Safety

• New /forgeflow-context-contract checks generated agent packets against agent-context-contract.json, required packet sections, size limits, and advisory-boundary language.
• The context contract helper is installed as a managed runtime helper and included in update, health, and installed-runtime dogfood coverage.
• Packet checks are read-only and do not refresh artifacts, approve work, or mutate project files.

Learning And Timeline Clarity

• /forgeflow-learning-status now applies age and reinforcement decay so old or sparse guidance loses trust unless recent evidence reinforces it.
• /forgeflow-health-timeline now reports comparable deltas between recent local health events.
• README and wiki docs now explain the new release, learning, context-contract, and timeline behavior.

Validation

• Full scripts/forgeflow/test-*.js suite
• node scripts/forgeflow/smoke-check.js --mode source --json
• git diff --check
• Focused context-contract, post-release install verify, release notes, learning status, health timeline, command coverage, install/update, docs, release-version, and installed-runtime dogfood tests