Rare Platform Integration

If the human does not choose, recommend public-only and proceed with that mode.

Required Outcome

Unless the repo shape blocks it, finish all of these:

1. Install the Rare platform dependencies for the detected stack.
2. Add Rare kit bootstrap using the stack's fromEnv helper.
3. Add the auth challenge route.
4. Add the auth complete route.
5. Add session storage plus a session helper or middleware.
6. Add or document the required env values.
7. Give local test steps using the Rare Agent CLI.

Framework Routing

• Next.js App Router: read references/nextjs-app-router.md
• Express: read references/express.md
• FastAPI: read references/fastapi.md
• Other Python services: read references/python-generic.md

Interaction Rules

• Detect the app framework from the repo before editing.
• Start by telling the human which framework was detected and present the two Rare integration modes.
• Prefer the adoption-first helpers over raw createRarePlatformKit(...) wiring:
  • TypeScript: createRarePlatformKitFromEnv(...)
  • Python: create_rare_platform_kit_from_env(...)
• If the human selects public-only, implement it directly.
• If the human selects full-mode, explain that the first step is still the quickstart auth routes, then extend toward registration and production wiring.
• If the human does not select a mode, keep the initial integration public-only even if the SDK supports full-mode.
• Preserve protocol red lines: replay protection, triad consistency, identity token verification, delegation token verification.
• For local-only demos, in-memory stores are acceptable. For production codepaths, call out that durable stores are required.

Resource Map

• Env and mode defaults: references/env-and-modes.md
• Next.js App Router steps: references/nextjs-app-router.md
• Express steps: references/express.md
• FastAPI steps: references/fastapi.md
• Generic Python fallback: references/python-generic.md
• Local validation flow: references/test-flow.md