chore(release): cut 0.1.30

[Jason Robert (jrob5756)]

Release 0.1.30

Previous release: v0.1.29 (2026-08-13) → new version: 0.1.30, tag v0.1.30.

Commit audit

1 commit in v0.1.29..main, all audited:

Commit	Subject	Disposition
d785a28	feat(fleet): the Fleet Manager — run records, conductor fleet, and an interactive TUI (#431)	Added + Changed + Fixed — reconciled below

Changelog reconciliation

#431's six changelog entries were merged into the already-released [0.1.28] section's ### Fixed heading — a stale-branch artifact — while [Unreleased] was left empty. This PR:

• removes those six entries from the released [0.1.28] section, restoring every previously released section byte-for-byte identical to v0.1.29:CHANGELOG.md;
• re-files them under [0.1.30] with correct Keep a Changelog headings:
  • Added — Fleet Manager run records + conductor stop/fleet list discovery of every run mode (including the foreground-stop confirmation behavior change and stop --run-id); the optional conductor fleet Textual TUI (conductor-cli[tui]); ~/.conductor/config.toml with [fleet.retention];
  • Changed — workflow_started now records the run's resolved inputs;
  • Fixed — conductor stop against a foreground run was a silent no-op under the interactive keyboard listener; a questions node never emitted the matching gate_resolved.
• adds a fresh empty [Unreleased] section compared against v0.1.30.

Entry prose is preserved from #431; only placement, category, and PR links changed.

Version

• pyproject.toml[project].version → 0.1.30
• uv.lock regenerated with uv lock (only the conductor-cli project version changed; no dependency movement)

Diff is limited to CHANGELOG.md, pyproject.toml, and uv.lock.

Validation

All run against this branch:

• make check — ruff check, ruff format --check (406 files), ty check — all clean
• make test — 7060 passed, 39 skipped, 0 failures (4m37s)
• make validate-examples — exit 0 (run for extra confidence; no schema or example changes in this release range)
• git diff --check — clean

After merge

Merging this PR will be followed by tagging the merge commit v0.1.30 and pushing it, which triggers .github/workflows/release.yml to build and publish the GitHub Release with its artifacts.

[Jason Robert (jrob5756)]

Note on the red check — pre-existing, unrelated to this release

Test (Python 3.13, windows-latest) fails on this PR, but it is already failing on main at d785a280 (the #431 merge) — run 31807814847.

• It is a step timeout, not a test failure: .github/workflows/ci.yml:157 caps Run tests with coverage at timeout-minutes: 10. The job log reaches [100%] and is then interrupted with KeyboardInterrupt inside pytest's pytest_sessionfinish tmpdir cleanup.
• feat(fleet): the Fleet Manager — run records, conductor fleet, and an interactive TUI #431 added ~400 tests (including the Textual TUI pilot tests), pushing the Windows leg past 10 minutes. The ubuntu legs finish in ~6m40s and pass.
• This PR cannot have caused it — the diff is limited to CHANGELOG.md, pyproject.toml, and uv.lock.
• The tag-triggered release is unaffected:.github/workflows/release.yml runs its test matrix on ubuntu-latest only (Python 3.12 + 3.13), with no Windows leg.

Every other check passes: Lint, Type Check, Frontend, Test (3.12/3.13 ubuntu), Install Scripts (ubuntu + windows), Validate Example Workflows, CLA.

Suggested follow-up, separate from this release: raise the Windows timeout-minutes for that step (or split/parallelise the suite) so main goes green again.