Repository navigation
ForgeFlow 4.7.0 packages the capability foundation and review runtime for managed Claude Code and Codex installations.
- Choose among nine specialized procedures on demand after recording the task need, scope, available prerequisites and budget. Existing permissions and exclusions still apply.
- Preserve immutable source/input evidence with exact retrieval and freshness checks.
- Keep focused specialist assignments and bounded follow-up requests, with explicit unresolved outcomes.
- Prepare scope, packets, budgets and bounded review waves through one operation. Return ready inputs or named blockers while retaining required coverage, proof and safe recovery.
- Keep ordinary feature validation proportional; comparative studies require a separate request.
- Refresh the README, wiki and generated reference pages.
Validation: a fresh disposable checkout with Node 24.21.0 and locked dependencies passed 227/228 deterministic test commands initially. The sole failing assertion expected obsolete capability-boundary wording; after correction, the focused context-packet check passed. Final documentation/link/version/wiki checks, source smoke, strict bridge typecheck and public-summary rendering passed. Both managed hosts installed successfully from the runtime archive into disposable homes; installed bytes match the archive, and archive bytes match the release commit. Existing owned-PR functional evidence was reused. No model comparisons were run. GitHub Actions remains disabled.
Download forgeflow-4.7.0-runtime.tar.gz and SHA256SUMS, verify with sha256sum -c SHA256SUMS, extract the archive, then run node scripts/forgeflow/install-template.js --target codex or --target claude from its directory. Restart host sessions after updating. This archive includes managed runtime files and documentation; evaluation fixtures and completion study runners are excluded. Use the source checkout for research reproduction.
Limits: all nine procedures retain evaluation benefit labels. No general accuracy, speed or cost advantage is claimed. Live client restart/discovery, manual settings, additional operating systems, live providers, public deployment and physical fabrication remain separate qualification. The lean Codex plugin does not expose the managed capability entry point. GitHub's automatic source archives retain historical research material; no new redistribution-rights claim is made for upstream-derived fixtures.