@allstak/wizard 0.1.7 → 0.1.8

package/docs/architecture/v02-java-host-fix-spec.md

@@ -1,121 +0,0 @@
-# v0.2 spec — Java SDK host configurability
-
-**Status:** PROPOSED. No code in `allstak-java-sdk` has been modified by this wizard release.
-
----
-
-## Problem
-
-The wizard's `--host` / `--ingest-host` / `--dashboard-host` flags allow users
-to point the wizard at a self-hosted AllStak deployment. For most SDKs this
-flows through to a runtime `host` field on `init()` config.
-
-For `sa.allstak:allstak-spring-boot-starter` and `sa.allstak:allstak-java-core`,
-the host is **hardcoded** to `https://api.allstak.sa` in the SDK source.
-Wizard's `--host` is silently a no-op for Java users — events go to the wrong
-backend without any error.
-
-Per the v0.1 implementation report (2026-05-07): "filed below as a v0.2
-SDK-side blocker."
-
----
-
-## Required SDK-side change
-
-Target package: `allstak-java-sdk` (the Java SDK in the AllStak SDK
-monorepo, sibling of `@allstak/wizard`). The change is small but must land
-in the SDK before the wizard's `java` integration can graduate from
-`experimental`:
-
-### 1. Add a `host` field to `AllStakConfig`
-
-```java
-public class AllStakConfig {
-  private String apiKey;
-  private String environment;
-  private String release;
-  private String serviceName;
-  private String host;          // NEW — defaults to "https://api.allstak.sa"
-  // …existing fields…
-
-  // Builder method:
-  public Builder host(String host) { this.host = host; return this; }
-}
-```
-
-### 2. Read `ALLSTAK_HOST` env var in the auto-config
-
-```java
-@ConfigurationProperties(prefix = "allstak")
-public class AllStakProperties {
-  // existing fields…
-  private String host = System.getenv().getOrDefault("ALLSTAK_HOST", "https://api.allstak.sa");
-}
-```
-
-### 3. Spring Boot `application.yml` exposure
-
-```yaml
-allstak:
-  api-key: ${ALLSTAK_API_KEY}
-  host: ${ALLSTAK_HOST:https://api.allstak.sa}    # NEW
-```
-
-### 4. Pass `host` through to the HTTP transport
-
-The transport class (likely `AllStakHttpClient` or similar) currently has a
-hardcoded base URL. Replace with `config.getHost()`.
-
----
-
-## Compatibility implications
-
-- **Backwards compatible:** existing users who pass nothing get the old
-  default. No breaking change to the public API.
-- **Bumps the minor version** — first SDK release with the field should be
-  `0.2.0` (not `0.1.x`) per semver.
-- **Wizard manifest update:** once shipped, edit
-  `src/integrations/java.ts` and the manifest's `compatibility` to require
-  the new minimum version: `{ name: 'sa.allstak:allstak-java-core',
-  minVersion: '0.2', maxMajorExclusive: null, required: true }`.
-- **Wizard's `java` integration warning** can be removed from
-  `manifest.stabilityNote` once v0.2.0 of the SDK is the minimum.
-
----
-
-## Wizard-side validation v0.2 must add
-
-After the SDK ships:
-
-1. Update `src/integrations/java.ts` to actually patch `pom.xml` /
-   `build.gradle` (currently the integration is `experimental` and only
-   writes env vars).
-2. Add `fixtures/spring-boot/` with a minimal Spring Boot 3.x project
-   (`./mvnw test` runs in CI).
-3. Doctor stage `event-ingest` should be runnable against a Java-emitted
-   event (the existing doctor probe is a generic event so this Just Works
-   once the SDK respects `--host`).
-
----
-
-## Why the wizard does NOT change this from this side
-
-- CLAUDE.md's monorepo policy: "Do not modify unrelated SDKs unless required."
-- Even with permission, modifying a Java SDK from a TypeScript wizard
-  session has no path to validate the change (no `mvn` in the wizard's CI
-  matrix).
-- The change is small enough (~20 LoC) that it belongs in a focused PR
-  against `allstak-java-sdk` rather than being smuggled in through wizard
-  work.
-
----
-
-## Action items for whoever picks this up
-
-1. Open a ticket against `allstak-java-sdk` referencing this spec.
-2. Implement the `host` field + env-var lookup in the SDK.
-3. Bump SDK to `0.2.0` and publish to Maven Central.
-4. Update `src/integrations/java.ts` manifest to require `0.2+`.
-5. Remove the warning blurb from the manifest's `stabilityNote`.
-6. Move the integration's `stability` from `experimental` toward `beta`
-   once Spring Boot fixture validation lands.

package/docs/architecture/v02-sourcemaps-e2e-spec.md

@@ -1,157 +0,0 @@
-# v0.2 spec — Source-maps end-to-end roundtrip
-
-**Status:** Wizard wires bundler plugins via `SourceMapProvider` (v0.1.1) but
-does NOT yet validate the upload → release-binding → symbolication chain
-against the live backend. This spec documents what v0.2 must add.
-
----
-
-## What works today (v0.1.x)
-
-- `vite` provider: imports `allstakSourcemaps` from `@allstak/react/vite`, adds it to the real Vite `plugins` array, and enables `build.sourcemap`.
-- `next` provider: managed-block hint pointing the user at `withAllStak`.
-- `webpack` provider: managed-block hint only.
-- `metro` provider: intentionally inert; `detect()` returns false.
-- `doctor` reports per-provider `wired` / `drifted` / `missing` state.
-
-What this gives us: the bundler is correctly configured to produce + upload
-source maps. What it does NOT verify: that uploaded maps actually resolve
-stack frames in the dashboard.
-
----
-
-## Backend contract (verified 2026-05-07)
-
-Endpoint:
-
-```
-POST /api/v1/sourcemaps/upload?projectId=:id&release=:version&fileName=:path&bundleUrl=:url
-  Content-Type: application/json
-  Authorization: Bearer <user JWT>
-
-  Body: raw .map JSON content (size limit 16 MB)
-
-  Response: 200 OK
-  {
-    "id": "uuid",
-    "release": "1.2.3",
-    "fileName": "assets/main-abc123.js.map",
-    "sizeBytes": 12345,
-    "uploadedAt": "2026-05-07T..."
-  }
-```
-
-Server-side resolution: the dashboard's error detail view symbolicates frames
-on read by looking up `(projectId, release, fileName)`. Maps are stored
-indefinitely (no TTL).
-
-Symbolication endpoint (used by error-detail UI; we can use it to verify):
-
-```
-POST /api/v1/sourcemaps/symbolicate
-  Body: { projectId, release, frames: [stackString] }
-  Response: { release, totalFrames, resolvedFrames, frames: [{ raw, resolved }] }
-```
-
----
-
-## Validation matrix v0.2 must pass
-
-| # | Check | Pass condition |
-|---|-------|----------------|
-| 1 | Upload happens during `npm run build` | Per-bundler post-build hook actually POSTs `.map` files. |
-| 2 | Release binding | Uploaded maps are queryable by `(projectId, release)`. |
-| 3 | Round-trip resolution | Send a synthetic event with a stack frame referencing the uploaded bundle → symbolicate endpoint resolves it to the original source line. |
-| 4 | Idempotent upload | Re-running build with same `(release, fileName)` is a no-op or a clean overwrite — never a duplicate. |
-| 5 | Auth scope | Upload requires JWT (not API key). Wizard's `requireUserCredentials` already handles this. |
-
----
-
-## What v0.2 needs to build
-
-### A. A real upload runner
-
-`src/sourcemaps/upload.ts`:
-
-```ts
-export async function uploadSourceMap(
-  apiHost: string,
-  accessToken: string,
-  params: {
-    projectId: string;
-    release: string;
-    fileName: string;     // e.g. "assets/main-abc123.js"
-    bundleUrl?: string;   // public URL of the bundle (helps dashboard match)
-    mapContent: string;   // raw JSON from .map
-  },
-): Promise<{ id: string }> {
-  // Use apiRequest from src/api/http.ts with body=mapContent and contentType='application/json'.
-}
-```
-
-This already has a slot in `src/api/http.ts` (the `contentType` override
-parameter exists for exactly this case).
-
-### B. A `wizard sourcemaps upload` CLI subcommand
-
-```bash
-allstak sourcemaps upload \
-  --project-id <uuid> \
-  --release "$GIT_SHA" \
-  --build-dir dist \
-  --pattern "**/*.js.map"
-```
-
-Walks `build-dir`, POSTs each `.map` file, prints the upload manifest. Reuses
-`getCredentialStore()` + `requireUserCredentials()`.
-
-### C. End-to-end doctor stage
-
-Extend `runDoctor` with a new stage `source-maps-e2e` that runs only with
-`--live-probe`:
-
-1. Build a tiny known fixture into a temp dir.
-2. Upload its `.map`.
-3. Send a probe event whose stack frame points at the uploaded bundle.
-4. Hit `/api/v1/sourcemaps/symbolicate` and assert `resolvedFrames > 0`.
-
-### D. CI matrix entry
-
-Add a `source-maps-e2e` job to the wizard's CI workflow gated on a
-repository secret (`ALLSTAK_E2E_API_KEY` + `ALLSTAK_E2E_PROJECT_ID`).
-Without those secrets the job skips.
-
----
-
-## Risks
-
-1. **`.map` files can be huge** (50MB+ for production bundles). Backend
-   currently caps at 16MB. v0.2 should either:
-   - Detect maps larger than the cap and skip with a warning, OR
-   - Negotiate a larger cap with the backend team.
-2. **`bundleUrl` parameter is optional but improves resolution accuracy.**
-   The wizard should compute it from the project's deploy target where
-   possible (Vercel? Netlify? Cloudflare Pages? — heuristics).
-3. **Hermes maps require a different upload format.** Bytecode → JS source
-   resolution is a separate symbolication pipeline; the v0.1 wizard does NOT
-   support this. Document explicitly when implementing.
-4. **Token rotation during long uploads.** The user JWT has a 15-minute TTL.
-   If uploading 100 `.map` files takes >15 minutes, the wizard must
-   `refreshTokens()` mid-upload. The credential store + auth client already
-   support this; just needs a wrapper.
-5. **Idempotency**: backend probably accepts the same `(release, fileName)`
-   twice and overwrites. Verify before relying on this.
-
----
-
-## Why this is deferred
-
-End-to-end validation requires:
-- A live AllStak instance (production or staging).
-- A real org + project the engineer can write to.
-- Credentials with both ingest scope AND user scope.
-- The ability to assert dashboard-side symbolication output.
-
-None of these are available in the v0.1.x wizard test environment. The
-provider abstraction landed in v0.1.1 specifically so this work can plug in
-without rewriting integrations.

package/docs/beta/README.md

@@ -1,17 +0,0 @@
-# `@allstak/wizard@beta` — public beta docs
-
-| Doc | What it covers |
-|-----|----------------|
-| [quickstart](./quickstart.md) | Install + run in five minutes |
-| [react](./react.md) | React (Vite or CRA) integration |
-| [next](./next.md) | Next.js 13+ integration |
-| [node](./node.md) | Vanilla Node.js / TypeScript |
-| [doctor](./doctor.md) | Deterministic diagnostics + `--live-probe` |
-| [restore](./restore.md) | Persistent snapshots + rollback |
-| [config](./config.md) | `allstak.config.*` schema + precedence + migrations |
-| [ci](./ci.md) | Running unattended in CI |
-| [privacy](./privacy.md) | Telemetry contract — what we send and how to disable |
-| [known-limitations](./known-limitations.md) | Honest list of what's NOT supported |
-| [troubleshooting](./troubleshooting.md) | Common errors mapped to fixes |
-| [errors](../errors.md) | Canonical error catalog |
-| [architecture](../architecture/) | Internal design docs (registry, transaction, rollback, etc.) |

package/docs/beta/ci.md

@@ -1,122 +0,0 @@
-# Running in CI
-
-The wizard is designed to run unattended once you've committed an
-`allstak.config.*` and stashed an API key.
-
-## One-shot setup in a CI step
-
-```yaml
-# .github/workflows/setup-allstak.yml (excerpt)
-- name: Configure AllStak
-  env:
-    ALLSTAK_API_KEY: ${{ secrets.ALLSTAK_API_KEY }}
-  run: |
-    npx @allstak/wizard@beta -i react -y \
-      --skip-deps \
-      --release "$GITHUB_SHA"
-```
-
-Why these flags:
-
-- `-y`: skip the confirmation prompt. The wizard refuses with `E_USER_CANCELLED`
-  in non-interactive mode otherwise.
-- `--skip-deps`: don't run a package install — your CI step before this
-  already installed dependencies.
-- `--release "$GITHUB_SHA"`: stamp the deploy commit on every event.
-
-The CLI exits 0 on success, 2 on `WizardError`, and 130 on user cancel
-(impossible in `-y` mode but documented for completeness).
-
-## Doctor in CI (smoke check)
-
-```yaml
-- name: Doctor
-  env:
-    ALLSTAK_API_KEY: ${{ secrets.ALLSTAK_API_KEY }}
-  run: |
-    npx @allstak/wizard@beta --json doctor \
-      --live-probe \
-      --project-id ${{ vars.ALLSTAK_PROJECT_ID }} \
-      > doctor.json
-    jq -e '.outcome == "success"' doctor.json
-```
-
-`--live-probe` sends a real test event and polls for ingestion. Use it as
-a deploy gate — if the ingestion path is broken, fail the deploy before
-users hit it.
-
-## JSON output everywhere
-
-`--json` writes a single JSON object to stdout (status text goes to stderr).
-Pipe it to `jq` or your own parser. Shape:
-
-```json
-{
-  "schemaVersion": 1,
-  "command": "init",
-  "outcome": "success",
-  "errorCode": null,
-  "durationMs": 4200,
-  "events": [...],
-  "diff": [...],
-  "doctor": [...],
-  "data": { ... }
-}
-```
-
-## Telemetry in CI
-
-Telemetry is on by default. To disable:
-
-```bash
-ALLSTAK_WIZARD_TELEMETRY=0 npx @allstak/wizard@beta ...
-# or
-npx @allstak/wizard@beta --no-telemetry ...
-```
-
-See [privacy.md](./privacy.md) for the exact payload shape. Telemetry
-failures NEVER abort the wizard.
-
-## Snapshot retention in CI
-
-Each wizard run writes a snapshot to `.allstak-wizard/backups/`. In CI the
-default retention of 10 is usually fine. To disable pruning entirely
-(useful when you keep a separate audit log):
-
-```bash
-npx @allstak/wizard@beta -i react -y --snapshot-keep 0
-```
-
-To skip persistent snapshots entirely (in-process rollback only) — not
-currently supported. Plans for v0.2.
-
-## Self-hosted in CI
-
-Either pass flags or commit a config:
-
-```bash
-npx @allstak/wizard@beta \
-  --host https://api.allstak.acme.com \
-  --dashboard-host https://app.allstak.acme.com \
-  -i react -y
-```
-
-## Validating the wizard itself
-
-The wizard ships a CI matrix workflow under `.github/workflows/ci.yml` that
-runs install/repair/uninstall/restore cycles against React+Vite, Next, and
-Node fixtures across Node 18/20/22. Fork the workflow if you want to
-gate your own CI on it.
-
-## Recommended pre-deploy chain
-
-```bash
-npm ci
-npm run test
-npx @allstak/wizard@beta config validate
-npx @allstak/wizard@beta -i react -y --release "$GIT_SHA"
-npx @allstak/wizard@beta --json doctor --live-probe \
-  --project-id "$ALLSTAK_PROJECT_ID" \
-  --api-key "$ALLSTAK_API_KEY"
-npm run build
-```

package/docs/beta/config.md

@@ -1,124 +0,0 @@
-# `allstak.config.*`
-
-Optional project-level config so you don't repeat `--org`, `--project`,
-`--host`, etc. on every wizard invocation. Discovered from the project root
-upward; the first matching file wins.
-
-Loader order (first match wins):
-
-1. `allstak.config.ts`
-2. `allstak.config.mts`
-3. `allstak.config.mjs`
-4. `allstak.config.js`
-5. `allstak.config.cjs`
-6. `allstak.config.json`
-
-`.ts` / `.mts` configs require running the wizard via a TypeScript-aware
-launcher (`npx tsx`, `bun`, or `deno run`). Plain `.mjs` / `.json` work
-without any toolchain.
-
-## Schema
-
-```ts
-import { defineConfig } from '@allstak/wizard/config';
-
-export default defineConfig({
-  schemaVersion: 1,
-  organization: 'my-org',
-  project: 'my-project',
-  environment: 'production',
-  release: process.env.GIT_SHA,
-  sourceMaps: {
-    enabled: true,
-    ignore: ['node_modules'],
-  },
-  selfHosted: {
-    apiHost: 'https://api.allstak.example',
-    ingestHost: 'https://api.allstak.example',
-    dashboardHost: 'https://app.allstak.example',
-  },
-  snapshotKeep: 10,
-});
-```
-
-All fields are optional. `defineConfig` is a typed-identity helper; at
-runtime it just returns its input.
-
-## Precedence
-
-```
-CLI flag  >  env var  >  config file  >  built-in default
-```
-
-Examples:
-
-| Setting | CLI | Env | Config | Default |
-|---------|-----|-----|--------|---------|
-| organization | `--org` | `ALLSTAK_ORG` | `organization` | — |
-| project | `--project` | `ALLSTAK_PROJECT` | `project` | — |
-| environment | `--environment` | `ALLSTAK_ENVIRONMENT` | `environment` | `production` |
-| release | `--release` | `ALLSTAK_RELEASE` | `release` (string or function) | — |
-| api host | `--host` | `ALLSTAK_HOST` | `selfHosted.apiHost` | `https://api.allstak.sa` |
-| ingest host | `--ingest-host` | `ALLSTAK_INGEST_HOST` | `selfHosted.ingestHost` | matches api host |
-| dashboard host | `--dashboard-host` | `ALLSTAK_DASHBOARD_HOST` | `selfHosted.dashboardHost` | derived from api |
-| source-maps | `--skip-source-maps` | — | `sourceMaps.enabled` | `true` |
-| snapshot-keep | `--snapshot-keep` | `ALLSTAK_SNAPSHOT_KEEP` | `snapshotKeep` | `10` |
-
-## Validation
-
-```bash
-npx @allstak/wizard@beta config validate
-```
-
-Reports the discovered file path, the declared `schemaVersion`, and any
-deprecation warnings.
-
-## Migration
-
-When the wizard ships a new schema, `allstak config migrate` upgrades your
-config in place.
-
-```bash
-npx @allstak/wizard@beta config migrate            # rewrites .json files
-npx @allstak/wizard@beta config migrate --dry-run  # prints planned changes
-```
-
-For `.ts` / `.mjs` configs the wizard prints the migrated shape and asks
-you to apply it manually — we don't roundtrip TypeScript through an AST
-serializer that would mangle your imports and comments.
-
-The wizard treats a missing `schemaVersion` as `1`. Always declaring it
-explicitly future-proofs your config.
-
-## Self-hosted
-
-Wizard never assumes `api.allstak.sa`. For a self-hosted deployment:
-
-```ts
-export default defineConfig({
-  schemaVersion: 1,
-  selfHosted: {
-    apiHost: 'https://api.allstak.acme.com',
-    ingestHost: 'https://api.allstak.acme.com',
-    dashboardHost: 'https://app.allstak.acme.com',
-  },
-});
-```
-
-CLI users can also pass `--host`, `--ingest-host`, `--dashboard-host`
-directly. **Caveat:** the Java SDK currently hardcodes its host; the wizard
-will warn when `-i java` runs against a non-default host until the SDK
-ships a configurable host field.
-
-## Release as a function
-
-Useful for CI:
-
-```ts
-release: process.env.GIT_SHA,                 // string at config-load time
-release: () => process.env.GIT_SHA,           // function evaluated each run
-release: () => execSync('git rev-parse HEAD').toString().trim(),
-```
-
-If the function returns `undefined`, the wizard falls through the precedence
-chain (env, default).

package/docs/beta/doctor.md

@@ -1,79 +0,0 @@
-# `allstak doctor`
-
-Deterministic diagnostic with named stages. Read-only by default;
-`--live-probe` adds a real test event roundtrip.
-
-## Stages
-
-The doctor runs all stages in this fixed order, even when an early stage
-fails (so you see the whole picture):
-
-| Stage | What it checks |
-|-------|----------------|
-| `auth` | Credentials present + accepted (`--api-key` or stored JWT). Auto-refreshes JWT if it expires soon. |
-| `reachability` | Configured host responds (HTTP-level only — no `/health` exists, so it probes `/api/v1/auth/me` and treats `401` as "alive"). |
-| `config` | `allstak.config.*` discovered (or absent — both fine). Reports the source path. |
-| `integration` | Delegates to the integration's own doctor — env present? entry patched? imports wired? |
-| `event-ingest` | (only with `--live-probe`) Sends a real event to `/ingest/v1/errors`, polls `/api/v1/errors` for ingestion. |
-| `release-linkage` | Confirms the configured release is attached to the test event. |
-| `source-maps` | Asks each registered source-map provider for its wired/drifted/missing state. |
-
-## Output
-
-Each stage emits exactly one line: `pass`, `warn`, `fail`, or `skip`, plus
-a fix hint when applicable. `--json` produces a structured array under
-`data.stages` for programmatic consumption.
-
-```bash
-npx @allstak/wizard@beta doctor
-```
-
-```
-» Doctor
-✓ [auth] Authenticated as me@example.com.
-✓ [reachability] Reached https://api.allstak.sa.
-✓ [config] Loaded config from /repo/allstak.config.ts.
-✓ [integration] react: ok (4 checks)
-- [event-ingest] Skipped (pass --live-probe to enable).
-- [release-linkage] Skipped: live probe required to verify release linkage end-to-end.
-✓ [source-maps] Wired: vite
-✓ Doctor: setup looks good.
-```
-
-## Live probe
-
-Requires both:
-
-- `--api-key` (project-scoped — sends the test event),
-- `--project-id <uuid>` (the project UUID, visible in the dashboard URL).
-
-```bash
-npx @allstak/wizard@beta doctor --live-probe \
-  --api-key ask_live_... \
-  --project-id 7e8e... \
-  --live-probe-timeout 60000
-```
-
-Flow:
-
-1. Wizard generates a random fingerprint (`wizard-probe-<6-hex>`).
-2. POSTs an event to `/ingest/v1/errors` with that fingerprint in metadata.
-3. Polls `/api/v1/errors?projectId=&from=&query=<fingerprint>` every 2.5s.
-4. Reports the dashboard URL of the captured event when found.
-
-If polling times out, the doctor returns `E_INGEST_VERIFY_FAILED` with the
-event id you can hand to support.
-
-## JSON mode
-
-```bash
-npx @allstak/wizard@beta --json doctor | jq '.data.stages'
-```
-
-Each entry is `{ stage, status, detail, fix?, data? }`.
-
-## When stages fail
-
-The CLI exits non-zero (code 2) on any `fail`. `warn` and `skip` do not
-change exit code. See [errors.md](../errors.md) for the canonical error
-codes each stage can emit.

package/docs/beta/expo.md

@@ -1,69 +0,0 @@
-# Expo (React Native)
-
-**Stability:** internal experimental. Managed workflow only. The wizard refuses to run on
-projects that have already prebuilt to native (i.e. an `ios/` or `android/`
-directory at the project root) — bare-via-prebuild has too many failure
-modes for an unattended patcher and remains `unsupported` in v0.1.
-
-## What you get
-
-- `@allstak/react-native` installed.
-- `.env` populated with `ALLSTAK_API_KEY` (and the standard companions).
-- `app.json` gets the AllStak Expo plugin appended to `expo.plugins[]`
-  (idempotent — re-running does not duplicate the entry).
-- `App.tsx` gets:
-  - An AST-injected `import { AllStakProvider } from '@allstak/react-native'`.
-  - A managed-block hint reminding you to wrap your root component in
-    `<AllStakProvider>…</AllStakProvider>`.
-- `app.config.{js,ts}` gets the same managed-block hint if it exists.
-
-## Run
-
-```bash
-npx @allstak/wizard@beta -i expo
-```
-
-## Compatibility
-
-- `expo >= 50`. Older versions refused with `E_UNSUPPORTED_VERSION`.
-- `react-native >= 0.73`.
-- **Managed workflow only.** Bare/prebuilt projects (`ios/` or `android/`
-  present) are refused with a clear error. To use AllStak in a bare RN
-  app, follow the SDK README directly — the wizard will not patch native
-  Xcode/Gradle config in v0.1.
-
-## Wiring `<AllStakProvider>`
-
-The wizard cannot safely AST-edit your component tree (App.tsx shapes
-vary too much — function/class/forwardRef/HOC). It places a managed-block
-hint and you wire the provider yourself:
-
-```tsx
-import { AllStakProvider } from '@allstak/react-native';
-
-export default function App() {
-  return (
-    <AllStakProvider apiKey={process.env.EXPO_PUBLIC_ALLSTAK_API_KEY}>
-      {/* your app */}
-    </AllStakProvider>
-  );
-}
-```
-
-`doctor` reports `warn` on `provider-wired` until the live call is detected
-(comments inside the managed-block hint are stripped before matching, so
-the example above does not produce a false positive).
-
-## Capabilities the wizard does NOT claim
-
-- **No source-map upload wiring.** Metro source-maps are deferred to v0.2
-  (no-op `skip` in `doctor`).
-- **No native edits.** No Podfile / Gradle / Info.plist / AndroidManifest
-  changes. EAS Build users get the plugin reference in `app.json` and Expo
-  takes care of the rest.
-
-## Verify
-
-```bash
-npx @allstak/wizard@beta doctor -i expo
-```