P10-S1: ship identity and workspace bootstrap

.ai/active/SPRINT_PACKET.md

@@ -1,33 +1,161 @@
 # Sprint Packet
 
-## Status
+## Sprint Title
 
-- No active build sprint is open.
-- Context Compaction 01 is complete and archived under `docs/archive/planning/2026-04-08-context-compaction/` and `.ai/archive/planning/2026-04-08-context-compaction/`.
-- Phase 10 planning docs are not defined yet.
+Phase 10 Sprint 1 (P10-S1): Identity + Workspace Bootstrap
 
-## Why This File Exists
+## Sprint Type
 
-- Control Tower expects `.ai/active/SPRINT_PACKET.md` to exist even when the repo is between planning cycles.
-- Keep this file as an idle-state pointer, not as a fake active sprint.
+feature
 
-## Current Approval Branch
+## Sprint Reason
 
-- Branch purpose: one-off context compaction and archival cleanup before Phase 10 planning, not a new product sprint.
-- Branch name: `codex/refactor-context-compaction-01`
-- Base branch: `main`
-- PR strategy: create-or-update
-- Merge policy: squash-merge only after `REVIEW_REPORT.md` is `PASS` and Control Tower issues explicit merge approval.
+Phase 9 proved Alice can be installed, interoperate, remember, and resume deterministically. Phase 10 must make Alice usable without local-only developer setup. `P10-S1` establishes the hosted identity and workspace foundations required before Telegram, chat-native continuity, and scheduled briefs can ship.
 
-## Branch Scope
+## Sprint Intent
 
-- compact live operating docs so active project memory reflects only current, durable Phase 9 truth
-- preserve superseded planning/control material in archive instead of deleting it
-- keep shipped Phase 9 release/quickstart/integration artifacts live and canonical
-- limit non-doc code changes to validation tooling/tests required for the new archive and idle-state control truth
+- hosted account and session model
+- magic-link authentication only for the first hosted entry path
+- workspace creation and bootstrap flow
+- deterministic device linking and device management
+- preferences and hosted settings foundation for timezone and future brief policy inputs
+- beta cohort and feature-flag support
 
-## Next Activation Criteria
+## Git Instructions
 
-- Run the Phase 9 release checklist and runbook on a clean environment.
-- Add canonical Phase 10 planning docs.
-- Replace this placeholder only when a new approved sprint is activated.
+- Branch Name: `codex/phase10-sprint-1-identity-workspace-bootstrap`
+- Base Branch: `main`
+- PR Strategy: one sprint branch, one PR
+- Merge Policy: squash merge only after review `PASS` and explicit approval
+
+## Redundancy Guard
+
+- Already shipped baseline:
+  - Alice Core local-first runtime
+  - deterministic CLI continuity contract
+  - deterministic MCP transport
+  - OpenClaw, Markdown, and ChatGPT importers
+  - continuity engine, approvals, and eval harness
+- Required now:
+  - hosted identity, sessions, and device trust model
+  - workspace bootstrap and preferences model
+  - onboarding/settings foundations that later sprints can attach Telegram to
+- Explicitly out of `P10-S1`:
+  - passkeys or alternate auth methods beyond magic-link
+  - Telegram transport
+  - Telegram link/unlink UX
+  - chat-native continuity flows
+  - daily brief delivery
+  - scheduler execution
+  - backup or sync payload movement
+  - admin/support dashboards
+  - launch hardening
+
+## Exact APIs In Scope
+
+- `POST /v1/auth/magic-link/start`
+- `POST /v1/auth/magic-link/verify`
+- `POST /v1/auth/logout`
+- `GET /v1/auth/session`
+- `POST /v1/workspaces`
+- `GET /v1/workspaces/current`
+- `POST /v1/workspaces/bootstrap`
+- `GET /v1/workspaces/bootstrap/status`
+- `POST /v1/devices/link/start`
+- `POST /v1/devices/link/confirm`
+- `GET /v1/devices`
+- `DELETE /v1/devices/{device_id}`
+- `GET /v1/preferences`
+- `PATCH /v1/preferences`
+
+## Exact Data Additions In Scope
+
+- `user_accounts`
+- `auth_sessions`
+- `magic_link_challenges`
+- `devices`
+- `device_link_challenges`
+- `workspaces`
+- `workspace_members`
+- `user_preferences`
+- `beta_cohorts`
+- `feature_flags`
+
+## Exact Files And Modules In Scope
+
+- `apps/api/src/alicebot_api/main.py`
+- `apps/api/src/alicebot_api/config.py`
+- `apps/api/src/alicebot_api/contracts.py`
+- `apps/api/src/alicebot_api/store.py`
+- new hosted auth / workspace bootstrap / device / preferences modules under `apps/api/src/alicebot_api/`
+- API migrations under `apps/api/alembic/versions/`
+- hosted onboarding/settings pages and supporting UI under `apps/web/app/` and `apps/web/components/`
+- sprint-owned unit, integration, and web tests under `tests/` and `apps/web/app/**/*.test.tsx`
+- sprint-owned documentation updates required to keep active control truth aligned
+
+## Implementation Workstreams
+
+### API And Persistence
+
+- add hosted account, session, workspace, device, and preference contracts
+- add magic-link challenge lifecycle and authenticated session resolution
+- add workspace bootstrap state and feature-flag visibility needed by hosted onboarding
+- keep hosted identity/workspace records mapped cleanly onto the shipped Alice Core user/workspace semantics
+
+### Hosted UX
+
+- add the minimal hosted web flow needed to sign in, create or bootstrap a workspace, manage linked devices, and update preferences
+- keep the surface narrow and utilitarian; this sprint is foundation, not launch polish
+- show hosted bootstrap readiness only; do not imply Telegram is available yet
+
+### Verification
+
+- add unit coverage for auth, session, device, workspace bootstrap, and preference logic
+- add integration coverage for all `P10-S1` endpoints, including invalid token, expired token, duplicate bootstrap, and revoked-device paths
+- add web tests for the hosted onboarding/settings slice
+- keep control-doc truth checks passing after packet and current-state updates
+
+## Required Deliverables
+
+- hosted account model
+- magic-link auth
+- device linking
+- workspace bootstrap flow
+- hosted settings page for timezone, brief-preference inputs, quiet-hours inputs, and device visibility
+- beta cohort and feature-flag support
+
+## Acceptance Criteria
+
+- a new user can create a workspace without touching a repo
+- a returning user can log in securely
+- device linking works deterministically
+- preferences persist and are exposed in hosted bootstrap/settings responses for later brief scheduling
+- Phase 9 shipped scope is baseline truth, not sprint work
+- hosted identity does not diverge from local workspace semantics
+- no `P10-S1` screen or API claims that Telegram is already linked or available
+
+## Required Verification Commands
+
+- `python3 scripts/check_control_doc_truth.py`
+- `./.venv/bin/python -m pytest tests/unit tests/integration -q`
+- `pnpm --dir apps/web test`
+
+## Review Evidence Requirements
+
+- `BUILD_REPORT.md` must list the exact sprint-owned files changed and the exact command results above
+- `REVIEW_REPORT.md` must grade against `P10-S1` specifically, not generic Phase 10 planning
+- if local archive paths remain dirty, they must be called out explicitly as excluded from sprint merge scope
+
+## Implementation Constraints
+
+- do not fork continuity semantics between hosted surfaces and Alice Core
+- keep OSS versus product boundaries explicit in docs and API naming
+- preserve existing approval, provenance, and correction discipline
+- do not widen Phase 10 scope to Telegram or notifications inside this sprint
+- do not ship a scheduler in `P10-S1`; preference storage is enough
+- do not represent Telegram channel state before `P10-S2`
+- prefer additive hosted-control-plane seams over invasive rewrites of shipped Phase 9 paths
+
+## Exit Condition
+
+`P10-S1` is complete when a user can authenticate by magic link, create or bootstrap a workspace, link and revoke devices, persist hosted preferences, and land in a hosted bootstrap state that is explicitly ready for later Telegram linkage without reopening shipped Phase 9 scope.

.ai/handoff/CURRENT_STATE.md

@@ -2,26 +2,37 @@
 
 ## Status
 
-- Phase 9 is complete.
-- No active build sprint is open.
-- Phase 10 planning docs are not defined yet.
+- Phase 9 is complete and shipped.
+- Phase 10 planning is defined as Alice Connect.
+- P10-S1 (Identity + Workspace Bootstrap) is the first execution sprint packet.
+- No Phase 10 product surface is shipped yet.
 
-## Canonical Shipped Surface
+## Canonical Baseline
 
-- Alice ships a local-first runtime, deterministic CLI, deterministic MCP transport, OpenClaw/Markdown/ChatGPT importers, and a reproducible local evaluation harness.
-- Canonical Phase 9 launch references remain under `docs/quickstart/`, `docs/integrations/`, `docs/examples/phase9-command-walkthrough.md`, `docs/release/`, `docs/runbooks/phase9-public-release-runbook.md`, and `eval/`.
+- Shipped OSS surface: local-first runtime, deterministic CLI, deterministic MCP transport, OpenClaw/Markdown/ChatGPT importers, continuity engine, approvals, and evaluation harness.
+- Canonical shipped docs remain under `docs/quickstart/`, `docs/integrations/`, `docs/examples/phase9-command-walkthrough.md`, `docs/release/`, `docs/runbooks/phase9-public-release-runbook.md`, and `eval/`.
+- Repo runtime remains a modular monolith: FastAPI API/core, Next.js web app, workers, Postgres, Redis, and MinIO.
 
-## Active Constraints
+## Current Phase 10 Target
 
-- Do not reopen shipped Phase 9 product scope while the repo is waiting for Phase 10 planning.
-- Keep public claims tied to runnable commands and committed evidence.
-- Archive planning history instead of carrying it in live control files.
+- hosted identity and workspace bootstrap
+- device and channel linking
+- Telegram-first chat access
+- chat-native capture, recall, resume, correction, open-loop review, and approvals
+- daily brief and notification loop
+- beta rollout, support, and observability tooling
+
+## Active Sprint Focus
 
-## Next Control Move
+- `P10-S1` covers account/session foundations, workspace bootstrap, device linking, preferences, and beta controls.
+- Telegram transport, chat-native continuity, daily briefs, and launch hardening are later Phase 10 milestones.
+- Phase 9 shipped scope is baseline truth and must not be reopened as sprint work.
 
-- Run the Phase 9 release checklist and runbook end to end on a clean environment.
-- Cut `v0.1.0` only after those gates pass and explicit approval is given.
-- Add Phase 10 planning docs before activating another sprint.
+## Active Constraints
+
+- Preserve parity between local, CLI, MCP, and future Telegram behavior.
+- Keep OSS versus hosted product scope explicit in docs and APIs.
+- Archive planning history instead of carrying it in live control files.
 
 ## Archive Pointers