docs: start milestone v2.0 PAX8 Integration

.planning/PROJECT.md

@@ -15,6 +15,29 @@ A manager can open Pulse on their phone and, in under 30 seconds, see the
 state of the business and triage tickets — without ever needing to switch to
 desktop for read-only awareness.
 
+## Current Milestone: v2.0 PAX8 Integration
+
+**Goal:** Sync PAX8 licensing/subscription data into Pulse, read-only, mapped
+to Autotask companies, so managers can see subscription costs and seat counts
+alongside existing company data.
+
+**Target features:**
+- PAX8 client + factory (OAuth2 client-credentials; credentials already
+  provisioned)
+- Read-only sync of companies, subscriptions, product catalog, and
+  orders/invoices into Postgres
+- Fuzzy-name matching of PAX8 companies to Autotask companies, with a
+  manual-review path for unmatched/ambiguous cases
+- New `/pax8` page (company list, subscriptions, cost breakdown)
+- Daily sync via the existing scheduler pattern
+
+Unrelated in domain to the v1.0 Mobile Shell Redesign above — this milestone
+adds a new backend integration and admin-facing surface, not a mobile change.
+See `.planning/seeds/SEED-002-pax8-integration.md` for the exploration that
+scoped this milestone. `.planning/seeds/SEED-003-general-pulse-data-assistant.md`
+(NL chatbot over Pulse data) is explicitly out of scope here — a separate
+future milestone that will consume this data once it exists.
+
 ## Requirements
 
 ### Validated
@@ -112,14 +135,20 @@ desktop for read-only awareness.
 
 ### Active
 
-<!-- Hypotheses for this milestone — see docs/superpowers/specs/2026-05-03-mobile-shell-design.md -->
+<!-- Hypotheses for this milestone — see .planning/seeds/SEED-002-pax8-integration.md -->
 
-_No active hypotheses — all planned milestone phases validated._
+- PAX8 client + factory, read-only sync of companies/subscriptions/catalog/
+  orders into Postgres, fuzzy-name Autotask company matching, new `/pax8`
+  page, daily sync cadence — v2.0 PAX8 Integration milestone (see above)
 
 ### Out of Scope
 
 <!-- From spec §7. Explicit boundaries to prevent scope creep. -->
 
+- PAX8 write access (seat adjustments, placing orders) — read-only in v2.0;
+  revisit only if reconciliation surfaces a concrete need to act, not just view
+- General natural-language data assistant / chatbot over Pulse data — separate
+  future milestone (SEED-003), deliberately not bundled with the PAX8 data sync
 - Service worker / offline cache / push notifications — deferred until a clear
   offline use-case lands
 - Tablet breakpoint (`md:max-w-2xl`) — noted as follow-up, keep `max-w-lg`
@@ -198,4 +227,4 @@ This document evolves at phase transitions and milestone boundaries.
 4. Update Context with current state
 
 ---
-*Last updated: 2026-05-11 — Phase 9 complete (User Profile & Preferences)*
+*Last updated: 2026-07-10 — v2.0 PAX8 Integration milestone started*