v0.6.1 — Right-sized discipline

Makes the discipline proportional — the fix for agents either over-ceremonying tiny changes or skipping the memory entirely.

npx persist-os@latest init

Fixed

• Match ceremony to scope — both ways. A genuinely new feature, module, integration, data model, or security/architecture decision gets proper planning; a small addition or fix in an already-decided area just gets implemented with focused tests. Judged by novelty + blast radius, not line count. (Previously a one-button change could trigger a full module plan + docs.)
• Reliably contribute memory. Front-loaded rule: record substantial work via the persist CLI (feature create, adr create+accept) so the durable trail actually exists — "if it's not in a file, it didn't happen." (Previously agents oriented from memory but never wrote any back.)
• Tightened plan-module / plan-feature / create-prd triggers to exclude small changes (loads on-demand → also cuts token cost); implement-task no longer forces the full PRD→plan pipeline for every task.

Verified

typecheck · lint · format · build · 290/290 tests · persist doctor PASSED. Live-tested by building a real to-do app: right-sizing held, the contribute loop created durable memory, and the gates caught two corner-cuts.

Local-first: no network, no telemetry, no AI calls.