Repository navigation
The first pinned, known-good HydraFlow for downstream HydraFlow-format repos to build on.
Placed on the promoted main SHA fa13878bf (RC #11624), not on staging and not on a checkout HEAD. Anything merged after this SHA is main, not v1.0.0.
The bar this tag clears
- No open data-loss or wrong-branch paths: squash-merge worktree GC (#11502), wrong-branch worktree creation (#11501), the closed-issue landed-check gap (#11503/#11507), the false-close blind spot (#11481) — all closed.
mainCI green on this SHA (Quality, CI, CodeQL, Build Agent Image all pass) and the RC promotion ran the full required suite including six sandbox shards.- Zero open high-severity code-scanning alerts. No open P0.
- Version bumped
0.9.7 → 1.0.0.
Installing a pinned HydraFlow
uv pip install git+https://github.com/T-rav/hydraflow@v1.0.0
hydraflow --version
The wheel ships the flat src/ modules plus packaged resources — prompts/, templates/, static/, and assets/ all resolve from an installed wheel with the working directory outside any checkout (#11580, #11591, #11589). Running the full server still expects a checkout for the UI bundle.
Scope
778 PRs merged to staging after the 0.9.7 bump (#9763, 2026-07-18) through 2026-08-22, carried to main by 57 RC promotions. Headline changes, with the full per-change list in CHANGELOG.md:
- Credit failover — Claude credit exhaustion reroutes work spawns to z.ai GLM instead of pausing the factory (ADR-0119).
- In-framework flow (DAG) primitive — every pipeline phase and the wiki compiler run on one flow substrate; bespoke control code retired.
- Observability moved out of the factory — Honeycomb/OTel and Sentry removed, ownership handed to the SRE agent (ADR-0118).
- Two-tier branch model — PRs land on
staging;mainadvances only through auto-promoted RC PRs (ADR-0042). - Factory as a service — launchd service with a boot-correctness liveness kernel that honours the operator's Stop latch (ADR-0135).
- Erosion ratchets — god-class mass and test-suite hygiene sensors, each filing one standing class issue, with PR-time ratchets that cannot rise.
- Implement-path throughput — the test-adequacy gate repairs in-run before rejecting an attempt; build timeouts tiered by complexity; zero-commit attempts routed to diagnose; the implement path off the host-wide quality lock.