ForgeFlow v3.0.0-alpha.1

First v3 prerelease. Adds the Antigravity bridge, adaptive thinking, deterministic multi-model routing, supply-source priority/failover, Business Team-first worker routing, and usage telemetry. CI passed on PR #115 and on the merged main commit. Live GCP acceptance verified T3 → Pi → ForgeFlow worker routing to business-team/openai-codex/gpt-6.1-sol.

ForgeFlow v2.0.2

ForgeFlow v2.0.2

Runtime compatibility and deployment hygiene patch.

Changes

• Upgrade the supported LangGraph Agent Server line to langgraph-api 0.14.x (0.14.0 locked) with langgraph-runtime-inmem 0.34.0.
• Preserve the existing local durable LangGraph state across the minor-line upgrade.
• Treat normal SIGTERM/exit 143 as a successful systemd shutdown so planned deploys and restarts no longer appear as failures.
• Document the Python 3.14 runtime contract and the intentionally disabled loopback run-completion webhook.

Validation

• 161 pytest tests pass and Ruff passes.
• Main CI passes on the release commit.
• Real GCP Dev deployment remained healthy after upgrading from LangGraph API 0.13.4 to 0.14.0.
• All 17 previously visible durable threads remained available across the upgrade/restart.
• Explicit stop reports Result=success with ExecMainStatus=143; restart returns to active/running.

ForgeFlow v2.0.1

ForgeFlow v2.0.1

Patch release for the v2 self-hosted Open SWE/LangGraph deployment path.

Fixed

• Persist LangGraph local-dev state in the stable ForgeFlow state directory instead of tying it to whichever Git worktree is currently deployed.
• Safely migrate/link existing deployment state when switching the service to a different checkout.
• Fail closed on divergent or unsafe state migration instead of starting a second checkpoint universe.
• Restore the previously active policy service when deployment fails before the replacement is healthy.
• Restart the Codex OAuth broker after unit updates so deployment changes take effect consistently.

Validation

• 160 pytest tests pass on the release commit.
• Ruff passes.
• GitHub Actions CI passes on main at 110954dbcf23f13222dcb01954087e549ccb6e0d.
• GCP Dev was redeployed from the stable main checkout and reports the ForgeFlow Policy service healthy on 127.0.0.1:58810.
• LangGraph state now resolves to ~/.local/share/forgeflow-policy/langgraph, independent of the deployed worktree.

ForgeFlow v2.0.0

ForgeFlow v2.0.0

ForgeFlow v2 is a breaking rebuild of the project around one principle: ForgeFlow governs software-engineering quality; Open SWE owns autonomous execution.

Highlights

• Replaced the legacy Node/SQLite autonomous control plane with a small Python 3.14 policy graph running beside pinned Open SWE in LangGraph.
• Added evidence-owned completion: an agent run reporting success cannot advance work without authoritative PR/head evidence.
• Added exact-head CI and Official Open SWE Reviewer gates before READY.
• Added bounded P0/P1/P2 repair loops that reuse the implementation thread and require provenance on repair commits.
• Added a self-hosted Docker execution plane for Open SWE on GCP Dev with non-root execution, read-only rootfs, explicit noexec tmpfs mounts, AppArmor/seccomp/no-new-privileges, resource limits, private-network/metadata blocking, and provider-owned GC.
• Added least-privilege GitHub App credentials: reviewer/dependency access is read-only; implementation write access is scoped to the primary repository.
• Added persistent sandbox workspace/cache/artifact support, Python 3.14 + uv provisioning, safe reconnect/replacement after GC, and workflow-push handling for non-default base branches.
• Removed OpenHands/Antigravity/legacy TypeScript execution ownership from the current runtime. Remaining OpenHands references are migration history, purge guards, or regression tests only.
• Reworked README and docs/ to describe the implemented v2 architecture rather than the retired runtime or an aspirational design.

Acceptance evidence

The v2 policy path was exercised end-to-end on a real GitHub PR. A controlled regression removed the Docker read-only-rootfs boundary while deterministic CI still passed; the Official Reviewer raised a blocking high-severity finding, ForgeFlow entered REPAIRING, Luna xhigh repaired the issue on the same implementation thread, exact-head CI passed, the Official Reviewer resolved the finding on re-review, and the policy returned to READY with repair_round=1.

Additional real-project validation on Digital Biome exercised Open SWE implementation/reviewer sandboxes, private submodule hydration, exact-head CI, review findings, repair, and re-review.

Breaking changes

• The v1 autonomous runtime, SQLite workflow state, legacy API/client compatibility surface, OpenHands execution plane, and old systemd topology are not migrated.
• Git/GitHub/Open SWE/LangGraph are the source of truth for v2 work and durable execution state.
• Existing v1 runtime state should not be restored into v2.

Runtime

• Python 3.14
• Open SWE pinned to 0ff86e22a94cc84e32883fcb1beee568560d4140
• LangGraph deployment with agent, reviewer, analyzer, chat, scheduler, and forgeflow graphs
• Self-hosted Docker sandbox provider on GCP Dev

See README.md and docs/README.md for the current architecture and operational documentation.

ForgeFlow v1.4.0

ForgeFlow v1.4.0 adds generated semantic SDK operations on top of the existing typed OpenAPI client.

Highlights:

• client.operations.<operationId>() for all 45 hardened V1 operations;
• operationId-to-method/path mapping generated directly from the committed OpenAPI contract;
• required path, header, query, and request-body types remain compile-time enforced;
• response types continue to come directly from generated OpenAPI operations;
• existing raw GET / POST / request APIs remain compatible;
• no hand-written DTO or competing SDK contract authority is introduced.

Release evidence:

• PR #16 and main CI passed from clean GitHub runners;
• exact deployed source: cd85706;
• fresh real-provider acceptance completed two same-wave implementations and two independent exact-SHA PASS reviews;
• provider cleanup proof exists for every execution, all five worktrees retired, the project lease released, and activation failures were zero;
• release acceptance is ATTESTED for the exact source/artifact identity.

ForgeFlow v1.3.1

ForgeFlow v1.3.1 closes the Phase-6 platform hardening line.

Highlights:

• complete V1 OpenAPI contract hardening with 45/45 operation coverage and stable operationId identities;
• generated typed-client operation surface protected by additive compatibility floors;
• retired legacy core adapter compatibility paths and moved Maintenance contracts to a core-owned boundary;
• terminal Plan retirement now tolerates decision-equivalent descriptive evidence drift while remaining fail-closed on revision/verdict/status drift;
• durable meaningful-progress ordering no longer depends on same-millisecond UUID ordering.

Release evidence:

• PR and main CI passed from clean GitHub runners;
• exact deployed source: 3e2268f;
• the failed v1.3.0 candidate was never tagged or released;
• v1.3.1 recovered that candidate's stuck terminal cleanup automatically after deployment;
• a fresh real-provider lifecycle smoke then passed with two implementations, two independent exact-SHA PASS reviews, provider cleanup proof for every execution, 5/5 worktrees retired, project lease released, zero activation failures, and release acceptance ATTESTED.

ForgeFlow v1.2.1

ForgeFlow v1.2.1

• Retires the legacy src/core/adapters compatibility layer.
• Moves provider-neutral Improvement and self-change contracts under src/core/maintenance.
• Hardens architecture CI against recreating the retired adapter boundary.
• Makes meaningful-progress durable ordering use the controller-owned sequence rather than same-millisecond UUID tie-breaking.
• Production exact-SHA lifecycle acceptance passed with provider retry/failover, two independent exact-SHA reviews, provider cleanup, five worktree retirements, lease release, and zero activation failures.

ForgeFlow v1.2.0

ForgeFlow v1.2.0

• Adds the standalone @forgeflow/client typed OpenAPI SDK workspace.
• Generates client path types deterministically from api/openapi.v1.json with contract SHA-256 provenance.
• Adds client drift, type, runtime, build, and npm-pack gates to the default repository check.
• Restores the Phase-4 integration package fitness functions and Delivery assembly ownership.
• Production exact-SHA lifecycle acceptance passed, including provider-stall retry/failover, two independent exact-SHA reviews, provider cleanup, worktree retirement, and lease release.

ForgeFlow v1.1.5

Phase-4 integration architecture closure.

• external Provider, Workspace, Resource, Delivery, Release, and Intake I/O live under src/integrations
• Supervisor core depends only on SupervisorConversationHost port, not OpenHands
• governed execution-provider selection uses a fail-closed exact-one CapabilityRegistry
• workspace/resource/delivery concrete construction is hidden behind capability-specific package assemblies and ports
• API/Application have no concrete integration dependencies; bootstrap consumes only package public surfaces
• deprecated core/adapters re-export shims remain only for compatibility until Phase 6
• full deterministic checks, architecture gates, and exact-SHA real-provider lifecycle acceptance passed

Release provenance and autonomous lifecycle acceptance are bound to the exact source SHA and artifact digest.

ForgeFlow v1.1.4

Phase-3 focused reconciler closure.

• one generic lifecycle manager owns scheduling and shutdown
• focused Runtime Admission, Supervisor, Resource, Plan, Improvement, and Storage reconcilers own automatic convergence
• bootstrap and feature controllers own no timers
• Runtime Admission refresh/shutdown has one authority above the low-level execution runtime
• shutdown closes capabilities and drains in-flight reconciliations before DB close
• 392 deterministic tests and exact-SHA real-provider lifecycle acceptance passed

Production acceptance verified same-wave implementations, two independent exact-SHA PASS reviews, combined integration, provider cleanup, five worktree retirements, lease release, and zero activation failures.