[NewMe505]

Cuts [Unreleased] into [0.9.0]. It is a minor bump under the SemVer rule (docs/IDEAS_TRIAGE.md item 1), because of a new command (scio dashboard), a new optional extra (dashboard) and a new docs check (check_guardrails).

Contents:

• scio dashboard (issue feat: a live read-only dashboard (FastAPI, WebSocket, plain HTML/JS) #68, PR feat(dashboard): a live, read-only dashboard: scio dashboard (#68) #70, ADR 0017): a live, read-only web view of every thread across workspaces, plus docs/OBSERVABILITY.md. Ledger I-120 to I-139.
• The Always/Never guardrails with enforced guards, and the push-gate hook (issue chore: Always/Never guardrails with enforced guards, a push gate, per-pass bottleneck audits #61, PR feat(guardrails): Always/Never rules with enforced guards, a push and commit gate, per-pass audits #62).
• The fixes from the live graphcalc run so far (PR fix(product): bugs from the graphcalc live run (I-107 to I-112) #65, PR fix(github): create a missing label before naming it; no traceback on a GitHub refusal (I-113) #67, PR fix(product): worker python is the product's env; advisor-cap text; skip defers (I-114 to I-118) #71):
  • the quality bar follows the stack (I-107);
  • scio new threads report (I-108);
  • hand edits of PRODUCT.md survive (I-109);
  • spend spans invocations (I-110);
  • GitHub labels are created before use (I-113);
  • on the Claude Code worker a feature's python is the product's environment (I-114);
  • the advisor-cap halt names the cap that fired (I-115);
  • skip defers a feature instead of dropping it (I-116).
• scio report reads a live run's half-written ledger line without dying (I-127).

PR #71 merged while this PR waited, so main was merged into this branch (b5db814). Its three fixes stay under [0.9.0], the README status line lists issue #69, and the release date is the day of the tag. Guardrails 35 to 38 follow the dashboard's 20 to 34, and the ledger runs I-114 to I-118, then I-120 to I-139.

The version is 0.9.0 in pyproject.toml, scio/__init__.py and uv.lock (tests/unit/test_version.py checks all three). The README status line says v0.9.0 released, and PRODUCT_MODE marks the dashboard done.

Tag v0.9.0 follows the merge. .github/workflows/release.yml builds the GitHub Release from the changelog section, and check_released_section_frozen keeps that section as tagged from then on (I-089).

Test evidence

ruff check . && ruff format --check . && mypy && python -m pytest -n 4 && python scripts/check_docs.py && python -m evals.runner --suite regression --provider fake --trials 5 --min-pass-pow-k 1.0
on 1c37c5a: ruff and mypy clean · 482 passed, 18 skipped in 495 s · docs-check: 0 problem(s) · regression pass@1 1.00, pass^5 1.00
on b5db814 (after merging #71): ruff and mypy clean · 500 passed, 18 skipped in 628 s · docs-check: 0 problem(s) · regression pass@1 1.00, pass^5 1.00

CI on 1c37c5a: checks and docker-live passed.

Continuous improvement

• Issue ledger: no new problem in this release PR
• check_release_cadence passes

🤖 Generated with Claude Code