Estimate: 40m · Depends on: 6.10.3
Teach the seed loader (scripts/plan-seed/seed.ts + the seed data) about the org tier so pnpm db:seed models the moooon org over its workspace(s) — the dev/demo data that exercises the new hierarchy. This keeps the seeded world consistent with the 6.10.3 schema + the 6.10.4 gating (every seeded workspace lives under an org; the seeding owner is an org owner).
moooon Organization and attach the existing seeded workspace(s) to it via organizationId (the seed’s workspaces no longer top-level-orphan — they nest under moooon).OrganizationMembership(owner) for the seed’s owning/admin user, plus a couple of org members at different org-roles (owner / admin / member) so the cross-workspace member management UI (6.10.5) + the e2e (6.10.8) have realistic data.moooon (or a second seeded org if the demo needs the multi-org switcher case) — pick whichever exercises the org switcher + cross-workspace roster. Document the choice in the seed module.pnpm db:seed, the moooon Organization exists, owns its workspace(s) (each workspace’s organizationId points at it), and has an owner OrganizationMembership for the seed owner + a few members at varied org-roles.pnpm db:seed is idempotent (no duplicate org / memberships) and agrees with the 6.10.3 migration backfill.motir-core/scripts/plan-seed/seed.ts — the loader to extend (it already builds the moooon/motir workspace + project tree).motir-core/CLAUDE.md § 4-layer (the seed goes through the same repositories where practical).