v0.18.0

Team skills now lead with their own name, plans are for any work your team executes, and ox upgrade confirms you actually got the new version.

New

• Experimental Claude Code trace attachments — opted-in recordings can include compressed execution traces and events in the Ledger, with identity attributes removed. Paused intervals are excluded, retries preserve the stop boundary, and trace failures do not block the recording. Enablement remains local; no project settings are changed.

Improved

• Team skills lead with their own name — a skill your team publishes as grill-me is now /grill-me-team instead of /sageox-team-grill-me, and ox skills list shows the name that actually works. Team Rules take the same -team suffix; old directories are removed automatically.
• Plans are for any work your team executes — ox plan help and the guidance your AI coworker gets now name design, GTM, rollout, and engineering plans alike, not just implementation plans.

Deprecated

• External adapters: rules_installer removal is postponed — 0.17.0 said this release would stop calling it; ox still does, for adapters that declare no rule_targets. Declare rule_targets now: the fallback will be removed in a later release.

Fixed

• ox upgrade and the installer confirm you're on the new ox — both could report success while an older ox kept running; now they check the ox your shell runs and name the stale copy if it isn't the new one. go install works again, too.
• Status stops reporting a Ledger problem after it's fixed — once a Ledger you repaired syncs again, ox status, ox daemon status, and ox doctor stop showing its conflict, suspended sync, and last error.
• A team skill never overwrites one you wrote — if your repo already has a committed skill at the name a team skill wants, ox leaves it alone and reports the clash, and ox doctor warns when git hides a skill you named *-team from your teammates.
• Plan checks fit what you saved — saving a mockup, review sheet, or evidence page no longer runs plan-only checks or says it saved a plan, and ox plan lint and ox plan render take --kind so the check before saving matches the one after.
• ox murmur says it's safe to run while planning — its note goes to your Ledger, never your project, but AI coworkers in plan mode were skipping it as if it changed your repo.
• Concurrent updates no longer leave a recording's state unreadable — two ox processes updating the same recording at once could corrupt its saved state; errors about it now also name the file.