Skip to content

Handle Planner collection setup states - #3

Merged
callumalpass merged 1 commit into
mainfrom
agent/fix-planner-setup-flow
Aug 16, 2026
Merged

callumalpass merged 1 commit into
mainfrom
agent/fix-planner-setup-flow

Conversation

@callumalpass

Copy link
Copy Markdown
Owner

What changed

  • render explicit loading, authorization-required, and collection setup-review states
  • let users apply reviewed TaskNotes type-pack and Base-view setup before opening Planner
  • show the exact setup changes in the existing TaskNotes planning-ledger style
  • preserve access to sample tasks and choosing another collection
  • add regression coverage for setup-review details

Why

After a successful mdbase authorization, the application session can enter setup_review_required. Planner treated every non-ready state as the generic welcome page, so an authorized user appeared to be stuck instead of being given the required apply action.

Impact

Users can finish provisioning the reviewed TaskNotes setup and continue into Planner. The copy explicitly states that task records, custom types, and unrelated collection settings remain unchanged.

Validation

  • pnpm typecheck
  • pnpm lint
  • pnpm test — 35 tests passed
  • pnpm build

@callumalpass
callumalpass merged commit 4ec7b92 into main Aug 16, 2026
1 check passed
@callumalpass
callumalpass deleted the agent/fix-planner-setup-flow branch August 16, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant