Skip to content

v0.7.0

Latest

Choose a tag to compare

@JRS1986 JRS1986 released this 28 May 12:11
· 13 commits to main since this release
26785f2

Cleanup + performance release. Honors the --tool both deprecation from v0.6.0 and delivers a measured 3× speedup on doctor and pilot warm calls via cached hardware probing.

Highlights

Removed (breaking)

  • --tool both removed. The CLI exits with the standard three-line error block when it's used. Replace with --tool opencode,openclaude. See Upgrading.
  • _normalize_persisted_intake back-fill helper removed. A project.json written by 0.5.x that was never updated through 0.6.x silently ignores its legacy tool / agent keys and falls back to DEFAULT_TOOLS (opencode). Re-run coding-scaffold setup run to regenerate.
  • IntakeAnswers.agent property removed. Use IntakeAnswers.tools[0].
  • Stale "both"-handling branches in installers.build_install_plans and cli._maybe_setup_knowledge cleaned up.

Changed

  • probe_hardware() is now cached at $XDG_CACHE_HOME/coding-scaffold/hardware.json (default ~/.cache/coding-scaffold/hardware.json). 1-hour TTL keyed on OS / arch / Python version so it self-invalidates when any change.

    Surface Cold Warm Speedup
    doctor 243ms 78ms 3.1×
    pilot 235ms 79ms 3.0×

    New --no-probe-cache flag on doctor / pilot / probe forces a fresh probe — use after installing a new local runtime like ollama.

  • CODING_TOOLS / VALID_TOOLS consolidated into one source of truth in intake.py. The drift-detection test that policed the previous duplication is replaced with a one-line derivation invariant.

Tests

  • pytest-xdist enabled. Test suite ~22s sequential → ~3s parallel (-n auto). 637 tests passing.

Upgrading from 0.6.x

uv tool upgrade coding-scaffold     # or: pipx upgrade coding-scaffold
coding-scaffold setup update --target .

If any of your scripts still call --tool both, replace with --tool opencode,openclaude. If you have a project.json written by 0.5.x that was never updated through 0.6.x, run setup run to regenerate it in the modern shape. See the Upgrading guide for the full breaking-change story.

What's not here

Release-cycle discipline matters: this release honors only the deprecation promise from v0.6.0 and delivers one real perf optimization. No new features.