Skip to content

ForgeFlow 4.4.0: Task evidence and recovery

Choose a tag to compare

View all tags
@BrandedTamarasu-glitch BrandedTamarasu-glitch released this 07 Sep 02:58
· 63 commits to main since this release
v4.4.0
304cfe3

ForgeFlow 4.4.0 connects a task objective to acceptance criteria, current-source proof, and resumable phase history in Claude Code and Codex.

New capabilities

  • Start and inspect tasks with /task in Claude Code or $task in Codex. Checks bind results to source and artifact hashes; changed evidence becomes stale while history remains available.
  • Inspect task criteria, proof, phase history, and next action in the workshop. Background verification keeps the dashboard responsive.
  • Plan balanced no-agent, single-agent, and ForgeFlow comparisons with explicit actual, fixture, and unknown outcomes.
  • Suppress stale or contradicted memory through dependency evidence and task-linked feedback.
  • Validate fleet ownership and resource declarations; turn supplied CI failures into bounded local repair/check/draft workflows.

Reliability

Oversized task writes preserve the last readable record. Fleet checks committed, staged, unstaged, and untracked changes independently. Task scans share verification within each scan, bound concurrent workers, and deliver timeout errors promptly while cleanup completes.

Also included since 4.3.72

The refreshed workshop and Ember companion, session dashboard opening, visual HTML/PDF guide, rewritten wiki onboarding, Codex model inheritance, research divergence tools, memory and command-learning controls, runtime hardening, and deterministic CI.

Update

Use /update-forgeflow in Claude Code or $update-forgeflow in Codex. Restart the host and any running dashboard to load the new runtime. Existing workflows without task records remain supported.

Task evidence requires a Git worktree with an initial commit. Recovery restores saved phase context, not hidden model state. Initialized Git submodules remain unsupported by whole-repository snapshots. Fleet checks declarations without reserving infrastructure; maintenance prepares local drafts without publishing a PR. Evaluation fixtures do not establish model superiority or user adoption.

Validation

195 test commands and 25 browser tests passed for the implementation and corrective review. A fresh dependency install and 195/195 test commands also passed in a clean release checkout. GitHub Actions passed on the exact release commit, including the clean-tree check.

Task guide · Release notes

Assets 2
Loading