Current evidence in shipping handoffs
This minor release adds optional memory and installation capabilities and corrects how shipping summaries select validation evidence.
Shipping evidence
- Pass
--task <id>toship-prepare.shto use the selected task's latest evidence for each acceptance criterion. Source changes and replaced or missing artifacts invalidate old proof. - Automated tests, manual checks and review evidence are presented separately. Failed, stale, missing, waived and pending outcomes stay visible in the JSON, presentation and draft description.
- Historical project notes no longer become current test results or review approval. Without a selected task, validation is explicitly missing. Review verdicts still require independent verification against the current source.
Also included since 4.4.0
- Optional Obsidian vault memory and portable handoffs.
- Advice and memory selection focused on the current task, with proportional design and validation guidance.
- Explicit checks for workaround limitations and long-term follow-up, logging unrelated bugs, user impact and training, and actionable errors.
- Optional RTK setup during installation, safer missing-option handling in the Codex generator, and Ember installation and dashboard startup fixes.
- ForgeFlow repository validation runs locally. GitHub Actions is disabled and its workflow removed; GitHub is used only for authorized release pushes and artifacts. Downstream projects retain their own policies.
Use and limitations
Choose the task matching the current objective and run ship-prepare.sh --task <id> "Title". Existing invocations without a task still prepare artifacts, but cannot claim current validation. Curate relevant historical decisions and follow-ups manually. Task readiness is not an approval verdict.
The helper uses existing task evidence, not a new test run. The task's declared scope limits what that evidence covers. Review the local artifacts before any authorized publication. No migration or GitHub-hosted model credentials are needed for ForgeFlow's own release workflow.
Validation coverage
Regression cases cover explicit selection, unrelated newer tasks, superseded results, failing checks, changed source, replaced and missing artifacts, pending actions, invalid task IDs, historical note isolation, HTML escaping, and both installed host packages. Run npm test locally for the full release gate.