List view

• 4: Hardening & polish

  Non-breaking readiness wave: cost safety, multi-human security, delivery reliability, first-hour onboarding, and the docs/community files. Fourth of four — after this lands (plus fresh-VM install passes), the system is ready for users beyond the developer, whenever that moment comes.

  No due date

  •0/25 issues closed
  0% complete25 open0 closed

• 3: Template & API surface

  The surface breaks: template/lifecycle refactors (minds' copied src/), single API prefix, routable system events, and the external-connection docs written against the stabilized API. Third of four — needs mind-upgrade verification across every template.

  No due date

  •0/6 issues closed
  0% complete6 open0 closed

• 2: Data model & naming

  The schema-and-vocabulary breaks: user_type refactor, house/system split, terminology renames, Notes+Pages merge, plus removals approved by the compat inventory (#732). Second of four — breaking changes only, nothing else rides along.

  No due date

  •0/4 issues closed
  0% complete4 open0 closed

• 1: Upgrade foundation

  Make breaking changes safe to ship: fix the migration history, prove upgrades in CI, and harden the update path itself. First of four release-readiness trains — everything schema-touching waits on this.

  No due date

  •6/6 issues closed
  100% complete0 open6 closed

• New-user onboarding

  Make a new user's first hour work: no dead-ends, visible errors, and minds that show life out of the box.

  No due date

  •16/16 issues closed
  100% complete0 open16 closed

• Timeline correctness

  No due date

  •11/11 issues closed
  100% complete0 open11 closed

• Variants work right

  No due date

  •9/9 issues closed
  100% complete0 open9 closed

• Memory footprint

  No due date

  •7/7 issues closed
  100% complete0 open7 closed

• Spirit correctness

  No due date

  •11/11 issues closed
  100% complete0 open11 closed

• Sleep & delivery reliability

  No due date

  •14/14 issues closed
  100% complete0 open14 closed