Repository navigation
ForgeFlow 4.5.0
Changes
Shipping summaries now use the explicitly selected task's current evidence. The helper checks source and artifact freshness, uses each criterion's latest result, and keeps automated tests, manual checks and review evidence separate. Historical notes no longer become passing tests or approval; missing, stale and failed proof remains visible.
Also included since 4.4.0:
- Optional Obsidian vault memory and portable handoffs.
- Task-focused advice and memory selection, with proportional design and validation guidance.
- Checks for workaround durability, tracking unrelated bugs, user impact and training, and actionable errors.
- Optional RTK installation, safer Codex generator option handling, and Ember/dashboard startup fixes.
- Local validation for the ForgeFlow repository, with GitHub Actions disabled and GitHub reserved for release pushes and artifacts.
Using the change
Run ship-prepare.sh --task <id> "Title" for the task matching the current objective. Existing invocations without a task still prepare artifacts but report validation as missing. Curate relevant historical notes manually, and verify explicit reviewer verdicts against the current source before publication. Task readiness is not review approval.
Validation
On release commit a0a8a85, the complete local runner passed 199/199 test commands using Node 24.21.0, including service tests, TypeScript checks and installed-host regressions. All eight source smoke checks passed. Four specialist agent reviews approved; Arbiter approved and Compass confirmed. All 18 reviewed file hashes match the committed source.
No GitHub-hosted jobs are required. Task evidence covers the task's declared scope; this release does not claim automated enforcement of agent compliance or model performance gains.