Repository navigation
0.9.0 — resource-diff + DAG executor + apply --output/--emit
Three architectural changes land as 0.9.0. Breaking JSON shape changes — see CHANGELOG.
New
- Resource-diff plan model: `DesiredState` / `ObservedState` / `StateDiff` with `computeStateDiff()`. `planApply` returns `{ diff, actions }`; each action carries a `driftRef: StateDiffField[]`.
- DAG executor: `executeDag(actions, deps)` replaces abort-on-failure. Independent actions run concurrently; a failure skips only its downstream, peers still run. Tri-state status `"ok" | "failed" | "skipped"`.
- `flaker apply --output ` writes `ApplyArtifact` JSON.
- `flaker apply --emit daily|weekly|incident` produces the matching cadence artifact. `daily` and `weekly` fully wired; `incident` is a stub that points at `flaker ops incident` until 1.0.0.
Breaking JSON shape changes
- `flaker apply --json`: `executed[].ok: boolean` → `executed[].status: "ok"|"failed"|"skipped"`. Top-level `aborted` removed. New `executed[*].skippedReason`.
- `flaker status --json`: `drift.unmet[].field` → `.kind`; `drift.unmet[].threshold` → `.desired`.
Agents that parsed these shapes need to read the new keys.
Deprecated (removed in 1.0.0)
- `flaker ops daily` — use `flaker apply --emit daily`. The 0.7.0 Phase 1 deprecation was reverted in 0.7.0 Phase 2 because apply didn't emit the daily artifact. 0.9.0 closes that gap. `ops weekly` / `ops incident` remain first-class.
Empirical eval (Iter 8, 5 scenarios)
| Scenario | 0.8.0 | 0.9.0 |
|---|---|---|
| A: Day 1 Playwright setup | 100% | 88% |
| B: Promotion decision | 92% | ~92% |
| C: CI failure debug | 92% | 100% |
| D: Vitest hold-out | 91.7% | 93% |
| E: ops daily → apply --emit migration (new) | — | 95% (pre-doc-fix: 55%) |
Pre-doc-fix E surfaced that new features were CHANGELOG-only. Final commit before merge added --output/--emit references in operations-guide / how-to-use / README.
See CHANGELOG.md for the full 0.9.0 notes.