Poketo

`/api/v1/cli/invoke` route exists and returns the CLI client response shape for supported apps.

`/api/v1/cli/invoke` route exists and returns the CLI client response shape for supported apps.

`/api/v1/cli/invoke` route exists and returns the CLI client response shape for supported apps.

`/api/v1/cli/invoke` route exists and returns the CLI client response shape for supported apps.

`/api/v1/undo` route exists and supports undoable action recovery or returns a typed non-undoable response for expired/unknown transaction ids.

`/api/v1/undo` route exists and supports undoable action recovery or returns a typed non-undoable response for expired/unknown transaction ids.

`/api/v1/undo` route exists and supports undoable action recovery or returns a typed non-undoable response for expired/unknown transaction ids.

`/api/v1/undo` route exists and supports undoable action recovery or returns a typed non-undoable response for expired/unknown transaction ids.

`/onboarding/aha` reads agency onboarding metadata and defaults to the agency ICP path.

`first_triage_completed`, `aha_completed`, and `first_action_approved` are tracked correctly.

`import_started` is tracked with provider and ICP path.

`org.agencyOnboarding.activation` stores first-run state without losing existing agency onboarding metadata.

Agency sample data includes CRM, Work, Report, Billing Follow-up, and Brain-context signals where existing entity support allows it.

Agency sample data is labeled, idempotent, and removable or deactivatable as a group.

All legacy kanban skill references are verified cut over from `kanban.mjs` direct database access.

All legacy kanban skill references are verified cut over from `kanban.mjs` direct database access.

All legacy kanban skill references are verified cut over from `kanban.mjs` direct database access.

All legacy kanban skill references are verified cut over from `kanban.mjs` direct database access.

All phase tests pass.

All phase tests pass.

All phase tests pass.

All phase tests pass.

Default first safe action creates a Work follow-up card linked to the stale CRM deal.

Demo/sample data is not silently mixed into real import flows.

Existing Work/CRM gateway action and tools behavior remains unchanged.

Existing Work/CRM gateway action and tools behavior remains unchanged.

Existing Work/CRM gateway action and tools behavior remains unchanged.

Existing Work/CRM gateway action and tools behavior remains unchanged.

First triage displays 3-5 findings with source labels.

Gateway registry covers Work, Report, Chat, Brain, and CRM with action metadata and scope requirements.

Gateway registry covers Work, Report, Chat, Brain, and CRM with action metadata and scope requirements.

Gateway registry covers Work, Report, Chat, Brain, and CRM with action metadata and scope requirements.

Gateway registry covers Work, Report, Chat, Brain, and CRM with action metadata and scope requirements.

Import path exposes only provider options supported by the current import stack or clearly labels unsupported providers.

Import path keeps the target first-triage window within 15-20 minutes when the provider works.

Imported data can produce the first triage when signal sufficiency passes.

No regressions in previous phase tests.

No regressions in previous phase tests.

No regressions in previous phase tests.

No regressions in previous phase tests.

Production rate limiting is backed by shared infrastructure when configured and falls back to in-memory only for local/test environments.

Production rate limiting is backed by shared infrastructure when configured and falls back to in-memory only for local/test environments.

Production rate limiting is backed by shared infrastructure when configured and falls back to in-memory only for local/test environments.

Production rate limiting is backed by shared infrastructure when configured and falls back to in-memory only for local/test environments.

Signal sufficiency check blocks an empty first triage and offers demo scenarios, import, or setup checklist fallback.

Sparse or failed imports offer explicit sample/demo fallback without silently mixing fake and real data.

Step 8.5: Add shared-store-capable production rate limiting **(automated)**

Step 8.6: Re-verify kanban hard-cutover evidence and update docs **(automated)**

Step 8.7: Run gateway completion verification and fix regressions **(automated)**

Step 8.8: Final docs/status reconciliation while tests stay green **(automated)**

Triage findings preserve imported, workspace, and demo/source labels.

User can approve, modify, dismiss, or view source for the first recommendation.

User can choose sample, import, or workspace data path, with sample data as the primary CTA.

Work onboarding completion can route to `/onboarding/aha`.

`/onboarding/aha` reads agency onboarding metadata and defaults to the agency ICP path.

`first_triage_completed`, `aha_completed`, and `first_action_approved` are tracked correctly.

`import_started` is tracked with provider and ICP path.

`org.agencyOnboarding.activation` stores first-run state without losing existing agency onboarding metadata.

`rawCrmBillingFollowUpCollectionRiskSummaryQuery` exists and returns the 10-field shape scoped to an org.

`rawCrmBillingFollowUpCollectionRiskSummaryQuery` exists in `packages/db/src/lib/crm-db/` and returns `{ wonDealsNeedingFollowUpCount, expectedValueNeedingFollowUp, openFollowUpCount, openExpectedValue, overdueCount, overdueExpectedValue, blockedCount, blockedExpectedValue, reminderDueCount, reminderDueExpectedValue }` scoped to an org.

`specs/quote-to-cash.md` MVP surfaces `[x] Report` and `[x] Flow` checked.

`specs/quote-to-cash.md` MVP-surfaces checklist updated: `[x] Report` and `[x] Flow`.

Accelerator path is selectable or inferable without disrupting the agency path.

Accelerator path is selectable or inferable without disrupting the agency path.

Accelerator preset activates the intended app set or clearly documents unavailable app placeholders.

Accelerator preset activates the intended app set or clearly documents unavailable app placeholders.

Agency and accelerator activation behavior remain unchanged.

Agency Phase 1 activation behavior remains unchanged.

Agency Phase 1 activation behavior remains unchanged.

Agency sample data includes CRM, Work, Report, Billing Follow-up, and Brain-context signals where existing entity support allows it.

Agency sample data is labeled, idempotent, and removable or deactivatable as a group.

Agent primitive `startBillingFollowUpTool.execute()` no longer returns a stub — it calls the same underlying create path and returns the created follow-up id.

Agent primitive `startBillingFollowUpTool.execute()` no longer stubs.

All phase tests pass.

All phase tests pass.

All phase tests pass.

All phase tests pass.

All phase tests pass.

App expansion prompts are contextual rather than catalog-first.

App expansion prompts are contextual rather than catalog-first.

Client share prompt appears only after the core cross-app loop is visible.

Client share prompt appears only after the core cross-app loop is visible.

Cohort and mentor sample scenarios are labeled and removable.

Cohort and mentor sample scenarios are labeled and removable.

Default first safe action creates a Work follow-up card linked to the stale CRM deal.

Demo/sample data is not silently mixed into real import flows.

Department handoff and KPI-risk sample scenarios are labeled and removable.

First accelerator triage identifies milestone, mentor-note, and demo-day risk.

First accelerator triage identifies milestone, mentor-note, and demo-day risk.

First SMB Ops triage identifies late sales handoffs, blocked delivery work, and KPI risk.

First triage displays 3-5 findings with source labels.

Flow `action-crm-start-billing-follow-up` has a concrete execute handler that invokes the existing `createBillingFollowUp` tRPC procedure with inputs derived from the upstream `trigger-crm-deal-won` payload.

Flow `action-crm-start-billing-follow-up` has a working execute handler.

Founder sees post-aha next steps after recommendation interaction or approval.

Founder sees post-aha next steps after recommendation interaction or approval.

Import path exposes only provider options supported by the current import stack or clearly labels unsupported providers.

Import path keeps the target first-triage window within 15-20 minutes when the provider works.

Imported data can produce the first triage when signal sufficiency passes.

Invite PM/team nudges are contextual and do not block the aha completion state.

Invite PM/team nudges are contextual and do not block the aha completion state.

No new DB tables, no native-invoice entities, no provider integration code introduced.

No new DB tables, no native-invoice entities, no provider integration code, no Stripe/QuickBooks/Xero/FreshBooks API calls introduced.

No regressions in previous phase tests.

No regressions in previous phase tests.

No regressions in previous phase tests.

No regressions in previous phase tests.

No regressions in previous phase tests.

Payload labels avoid accounting / recognized-revenue / provider vocabulary.

Payload labels use "billing follow-up" / "collection-risk" vocabulary; serialized payload must not contain `revenue`, `recognized`, `invoice`, `booked`, or accounting/payment-provider terminology.

PM acceptance lands on role-relevant Work boards and client status/reporting surfaces where available.

PM acceptance lands on role-relevant Work boards and client status/reporting surfaces where available.

Report `dashboardPage` returns `billingFollowUpCollectionRisk` matching test fixture.

Report `dashboardPage` returns a `billingFollowUpCollectionRisk` field matching the test fixture in `packages/trpc/src/server/routers/report/__tests__/collection-risk.test.ts`.

Signal sufficiency check blocks an empty first triage and offers demo scenarios, import, or setup checklist fallback.

SMB Ops path is selectable or inferable without disrupting agency or accelerator paths.

SMB Ops preset activates the intended app set or clearly documents unavailable app placeholders.

Sparse or failed imports offer explicit sample/demo fallback without silently mixing fake and real data.

Sponsor-ready reporting next step is available from the same activation data.

Sponsor-ready reporting next step is available from the same activation data.

Step 8.1: Write failing gateway completion contract tests **(automated)**

Step 8.2: Add shared gateway route helpers for invoke and undo **(automated)**

Step 8.3: Implement `/api/v1/cli/invoke` and `/api/v1/undo` Flow routes **(automated)**

Step 8.4: Expand gateway app registry coverage with safe metadata and adapters **(automated)**

Team-member acceptance lands on assigned tasks or a personal work queue with linked context where available.

Team-member acceptance lands on assigned tasks or a personal work queue with linked context where available.

Triage findings preserve imported, workspace, and demo/source labels.

User can approve one safe cross-department escalation.

User can approve, modify, dismiss, or view source for the first recommendation.

User can choose sample, import, or workspace data path, with sample data as the primary CTA.

Work onboarding completion can route to `/onboarding/aha`.