Teams Todo: command locality

Status: SQLite-only command-local runtime implemented. The former root model, storage, network and view monoliths were removed. Public command grouping is still a future decision; existing list, show, new and task commands remain in use.

References: landing ownership, Todo command architecture, current schemas and execution progress.

Current layout

teams-todo/
  init.ts                         # database composition and lifecycle
  app.ts                          # parsing/routing and captured peer context
  definition.ts                   # aggregates owning definitions
  db/
    schema.ts                     # peer schema composition
    settings.ts
  commands/
    boards/
      schema.ts
      db.ts
      create/{definition,handler}.ts
      list/{definition,web}.ts
      show/{definition,handler,web}.ts
    tasks/{definition,schema,db,handler,web,styles}.ts
    changes/{schema,db,causality,summary}.ts
    incoming/{definition,db,handler,review,web}.ts
    invitations/{schema,web}.ts      # app metadata validation and invitation UI
    priority/{definition,db,model,handler,web}.ts
    peers/
      schema.ts
      db.ts
      definition.ts
      identity.ts                 # labels from verified FIPS roster
      network.ts                  # identity, exact grants, publication, Sync/probes
      delivery.ts                 # bounded automatic delivery/retry/coalescing
      network-db.ts               # external stream cursors and receipts
      wire.ts                     # bounded semantic framing/reassembly
      sharing.ts                  # app entrypoint to FIPS owner member chooser
      web.ts
    common/{schema,definition,view}.ts

Ownership rules

Public grouping proposal

Still proposed, not registered:

/teams-todo boards --list
/teams-todo boards --create --title "Work board"
/teams-todo boards --show --board <id>

The current metadata has one subcommand level. Grouped action flags fit it; positional boards list needs a deliberate help/catalog/parsing design. Confirm spelling before changing all definitions, forms, navigation and refresh actions. Do not register unfinished future invite/grant/merge operations merely to match folders.

Progress

Simulation/reset entries below record the completed former phase; those command owners and controls have since been removed. See the active FIPS transition in the implementation plan.

No test suite, release hooks or publication is required for ordinary locality work.