frontier-os-app-builder 1.0.0 → 1.1.0

package/README.md

@@ -1,6 +1,13 @@
 # Frontier OS App Builder
 
-A meta-prompting framework for building Frontier OS apps with Claude Code. Provides a guided workflow from idea to deployed app, with built-in knowledge of the Frontier SDK, app patterns, and deployment requirements.
+[![npm version](https://img.shields.io/npm/v/frontier-os-app-builder.svg)](https://www.npmjs.com/package/frontier-os-app-builder)
+
+A meta-prompting framework for building [Frontier OS](https://os.frontiertower.io) apps with [Claude Code](https://claude.ai/code). Provides a guided workflow from idea to deployed app, with built-in knowledge of the Frontier SDK, app patterns, and deployment requirements.
+
+## Prerequisites
+
+- [Claude Code](https://claude.ai/code) installed
+- Node.js 18+
 
 ## Install
 
@@ -16,15 +23,17 @@ To uninstall:
 npx frontier-os-app-builder --uninstall
 ```
 
-## Usage
+## Quick Start
 
-Create a new directory for your app, then run:
+1. Create a directory for your new app
+2. Open Claude Code in that directory
+3. Run:
 
 ```
-/fos:new-app "a room booking app for Frontier members"
+/fos:new-app "A tip jar app where members can tip baristas and staff with FND"
 ```
 
-The framework guides you through each step, telling you when to `/clear` and what command to run next:
+4. Follow the guided workflow — the framework tells you what to do next after each step:
 
 ```
 /fos:new-app "description"     → gather requirements, infer SDK modules, create roadmap
@@ -39,6 +48,16 @@ The framework guides you through each step, telling you when to `/clear` and wha
 /fos:ship                       → deploy to Vercel + register in app store
 ```
 
+5. Keep building — add features or start a new version:
+
+```
+/fos:add-feature "leaderboard"  → adds a new phase to the current milestone
+  /clear
+/fos:discuss N → /fos:plan N → /fos:execute N   → same loop
+
+/fos:new-milestone "v2 features" → archives v1, creates new phases for v2
+```
+
 ## Commands
 
 | Command | Purpose |
@@ -63,20 +82,36 @@ The framework is a multi-layered meta-prompting system:
 - **References** — built-in Frontier SDK and app pattern knowledge
 - **Templates** — production-tested boilerplate from existing Frontier OS apps
 
-Each command reads state from `.frontier-app/` on disk, does its work, writes updated state, and tells you what to do next. The `/clear` between steps keeps your context window fresh.
+Each command reads state from `.frontier-app/` on disk, does its work, writes updated state, and tells you what to do next. Running `/clear` between steps keeps your context window fresh — the file-based state bridges the gap.
 
 ## Key features
 
-- Infers SDK modules from your app description ("room booking" → Events + Wallet)
-- Asks smart domain questions, not generic ones
-- Researches patterns from production Frontier OS apps
-- Uses proven templates instead of generating code from scratch
-- Verifies against Frontier-specific rules (CORS, iframe detection, permissions)
-- Milestone system for iterative development (v1 → v2 → v3)
+- **Module inference** — describe your app in plain English and the framework maps it to the right SDK modules ("room booking" → Events + Wallet + User)
+- **Smart questions** — asks domain questions ("Should bookings require FND payment?"), not technical ones ("Which SDK modules?")
+- **Production templates** — boilerplate extracted from real Frontier OS apps, not generated from scratch
+- **Frontier-specific verification** — checks CORS origins, iframe detection, standalone fallback, SDK permissions, dark theme
+- **Milestones** — iterative development with `/fos:new-milestone` for v2, v3, and beyond
 
-## State
+## SDK Coverage
 
-All project state lives in `.frontier-app/` as human-readable Markdown and JSON:
+The framework has built-in knowledge of all 10 Frontier SDK modules:
+
+| Module | What it does |
+|---|---|
+| Wallet | Balances, FND transfers, token swaps, fiat on/off-ramp |
+| User | Profiles, referrals, KYC, access controls |
+| Events | Event management, room listings, bookings |
+| Communities | Community management, internship passes |
+| Partnerships | Sponsor passes |
+| Offices | Building access passes |
+| Storage | Persistent key-value storage |
+| Chain | Network config, contract addresses |
+| ThirdParty | App registration, webhooks, developer accounts |
+| Navigation | App-to-app deep linking |
+
+## Project State
+
+All state lives in `.frontier-app/` as human-readable Markdown and JSON — no database, no server:
 
 ```
 .frontier-app/
@@ -90,3 +125,19 @@ All project state lives in `.frontier-app/` as human-readable Markdown and JSON:
     ├── 02-feature/
     └── ...
 ```
+
+## Example Apps
+
+Ideas to get started:
+
+| App | Description | SDK Modules |
+|---|---|---|
+| Tip Jar | Members tip baristas with FND | Wallet, User |
+| Visitor Check-in | Kiosk for building access passes | Offices, User |
+| Room Booking | Book coworking rooms with payment | Events, Wallet, User |
+| Event Organizer | Create and manage community events | Events, Communities, User |
+| Sponsor Dashboard | Manage partnership passes | Partnerships, User |
+
+## License
+
+MIT

package/agents/fos-executor.md

@@ -27,7 +27,26 @@ Before executing, discover project context:
 
 <execution_flow>
 
-<step name="load_project_state" priority="first">
+<step name="verify_cwd" priority="first">
+**CRITICAL — Verify working directory before anything else.**
+
+When spawned in a worktree, your CWD may be the worktree root, not the app directory. Check:
+
+```bash
+ls .frontier-app/manifest.json 2>/dev/null && echo "CWD OK" || echo "CWD WRONG"
+```
+
+If `CWD WRONG`: look for the app directory inside the current directory. The worktree contains a copy of the repo — `cd` into it:
+```bash
+# Find the app directory (has .frontier-app/)
+APP_DIR=$(find . -maxdepth 2 -name "manifest.json" -path "*/.frontier-app/*" -exec dirname {} \; | head -1 | sed 's|/.frontier-app||')
+cd "$APP_DIR"
+```
+
+**All subsequent commands and file paths must be relative to the app root (where `.frontier-app/` exists).** Never use absolute worktree paths in git add commands — use paths relative to the repo root (e.g., `git add .frontier-app/phases/01-scaffold/01-01-SUMMARY.md`, NOT `git add frontier-os-app-name/.frontier-app/...`).
+</step>
+
+<step name="load_project_state">
 Load execution context:
 
 1. Read `.frontier-app/PROJECT.md` — app name, description, SDK modules
@@ -102,27 +121,42 @@ node $HOME/.claude/frontier-os-app-builder/bin/fos-tools.cjs scaffold <template>
 | Template | Destination |
 |----------|-------------|
 | `index.html` | `./index.html` |
-| `package.json` | `./package.json` |
+| `package-standalone.json` | `./package.json` |
 | `postcss.config.js` | `./postcss.config.js` |
 | `tsconfig.json` | `./tsconfig.json` |
-| `vercel.json` | `./vercel.json` |
+| `vercel-standalone.json` | `./vercel.json` |
 | `vite.config.ts` | `./vite.config.ts` |
-| `sdk-context.tsx` | `./src/lib/sdk-context.tsx` |
-| `layout.tsx` | `./src/views/Layout.tsx` |
-| `main-router.tsx` or `main-simple.tsx` | `./src/main.tsx` |
+| `frontier-services.tsx` | `./src/lib/frontier-services.tsx` |
+| `layout-standalone.tsx` | `./src/views/Layout.tsx` |
+| `main-router.tsx` or `main-simple-standalone.tsx` | `./src/main.tsx` |
 | `router.tsx` | `./src/router.tsx` |
 | `index.css` | `./src/styles/index.css` |
 | `test-setup.ts` | `./src/test/setup.ts` |
 | `gitignore` | `./.gitignore` |
 
 **Critical scaffold requirements:**
-- `src/lib/sdk-context.tsx` — NEVER modify after scaffold. Identical across all apps.
-- `src/views/Layout.tsx` — Must include `isInFrontierApp()` detection, `createStandaloneHTML()` fallback, `SdkProvider` wrapping children
+- `src/lib/frontier-services.tsx` — Exports `useServices()` with mock backend. Modified only during SDK Integration phase.
+- `src/views/Layout.tsx` — Dark-themed shell wrapping Outlet with FrontierServicesProvider. SdkProvider added during SDK Integration phase.
 - `src/styles/index.css` — Must include `@import "tailwindcss"`, complete `@theme` block with ALL CSS variables, `@layer base` with body styles
 - `index.html` — Must have `<body class="dark">`, Plus Jakarta Sans font links
-- `vercel.json` — Must have all 5 CORS origin blocks + SPA rewrite
+- `vercel.json` — SPA rewrite only at scaffold time. CORS origins added during SDK Integration phase.
 - `package.json` — Must have correct scripts (dev, build, preview, lint, test) and all required dependencies
 
+**Phase 1 scaffold BLOCKLIST — If any of these exist after scaffold, you have a bug. Fix it before committing:**
+- ❌ `src/lib/sdk-context.tsx` — DELETE if created. This file belongs to SDK Integration phase only.
+- ❌ `@frontiertower/frontier-sdk` in package.json — REMOVE from dependencies. SDK is added in SDK Integration phase.
+- ❌ `isInFrontierApp` or `createStandaloneHTML` in Layout.tsx — REWRITE Layout to use simple FrontierServicesProvider + Outlet pattern.
+- ❌ `SdkProvider` anywhere — REPLACE with FrontierServicesProvider.
+- ❌ `useSdk` anywhere — REPLACE with useServices.
+- ❌ Any import from `@frontiertower/frontier-sdk` — REMOVE. The SDK package does not exist in Phase 1.
+- ❌ CORS headers in vercel.json — REMOVE. Use SPA rewrite only.
+
+**Self-check after scaffold (run before committing):**
+```bash
+# All of these must return NO matches. If any match, fix before committing.
+grep -r "sdk-context\|useSdk\|SdkProvider\|@frontiertower/frontier-sdk\|isInFrontierApp\|createStandaloneHTML" src/ package.json vercel.json --include="*.tsx" --include="*.ts" --include="*.json" 2>/dev/null | grep -v node_modules || echo "CLEAN: No SDK artifacts in Phase 1"
+```
+
 </scaffold_execution>
 
 <feature_execution>
@@ -131,29 +165,29 @@ node $HOME/.claude/frontier-os-app-builder/bin/fos-tools.cjs scaffold <template>
 
 For feature tasks (Phase 2+), write actual TypeScript/React code.
 
-### SDK Code Patterns
+### Services Code Patterns
 
 **Always use these exact patterns:**
 
-**Import SDK:**
+**Import services:**
 ```typescript
-import { useSdk } from '../lib/sdk-context';
+import { useServices } from '../lib/frontier-services';
 ```
 
 **Access module:**
 ```typescript
-const sdk = useSdk();
-const wallet = sdk.getWallet();
+const services = useServices();
+const wallet = services.wallet;
 ```
 
 **Create hooks with loading/error states:**
 ```typescript
 import { useState, useEffect } from 'react';
-import { useSdk } from '../lib/sdk-context';
+import { useServices } from '../lib/frontier-services';
 import type { ReturnType } from '@frontiertower/frontier-sdk';
 
 export function useFeature() {
-  const sdk = useSdk();
+  const services = useServices();
   const [data, setData] = useState<ReturnType | null>(null);
   const [loading, setLoading] = useState(true);
   const [error, setError] = useState<string | null>(null);
@@ -161,7 +195,7 @@ export function useFeature() {
   useEffect(() => {
     const fetchData = async () => {
       try {
-        const result = await sdk.getModule().method();
+        const result = await services.module.method();
         setData(result);
       } catch (err) {
         setError(err instanceof Error ? err.message : 'Failed to load data');
@@ -170,7 +204,7 @@ export function useFeature() {
       }
     };
     fetchData();
-  }, [sdk]);
+  }, [services]);
 
   return { data, loading, error };
 }
@@ -224,8 +258,83 @@ Always use these semantic classes (defined in index.css @theme block):
 - If a type is not exported by the SDK, define a local interface that matches the SDK's return shape
 - Always use `strict: true` TypeScript
 
+### Module Access Reference
+
+When accessing modules via `useServices()`, use these property names:
+
+| Service Property | Description |
+|-----------------|-------------|
+| `services.wallet` | Wallet operations (balance, transactions, send) |
+| `services.storage` | Storage operations (get, set, delete) |
+| `services.chain` | Chain/blockchain operations |
+| `services.user` | User profile and authentication |
+| `services.partnerships` | Partnerships module |
+| `services.thirdParty` | Third-party integrations |
+| `services.communities` | Communities module |
+| `services.events` | Events module |
+| `services.offices` | Offices module |
+| `services.navigation` | Navigation module |
+
 </feature_execution>
 
+<frontier_os_rules>
+**CRITICAL — These rules apply to ALL code written for Frontier OS apps.**
+
+**Read the current phase and sdkPhase from manifest.json to determine which tier applies.**
+
+**TIER 1 — ALL PHASES:**
+1. **Dark theme:** Tailwind dark theme. Backgrounds: `bg-background`, `bg-card`, `bg-muted-background`. Text: `text-foreground`, `text-card-foreground`, `text-muted-foreground`. No hardcoded colors (no bg-white, text-black, bg-gray-900).
+2. **Error handling:** All service calls wrapped in try/catch. Loading states for async operations. Error states with user-friendly messages.
+3. **TypeScript strict:** All code in TypeScript strict mode. No `any` types unless explicitly justified.
+4. **Testing:** Vitest for unit tests. Test files in `src/test/`.
+5. **Service access:** Feature phases use `useServices()` from `src/lib/frontier-services.tsx`. Never import SDK directly in feature hooks or views.
+6. **Mock layer:** Mock services return realistic data matching SDK return types. Hooks must work identically whether backed by mocks or real SDK.
+
+**TIER 2 — SDK INTEGRATION PHASE ONLY:**
+7. **SDK access:** `useSdk()` hook from `src/lib/sdk-context.tsx`, used only inside `sdk-services.tsx` and `Layout.tsx`.
+8. **Iframe detection:** `isInFrontierApp()` check in Layout.tsx. Standalone mode shows fallback banner.
+9. **SdkProvider wrapping:** App wrapped in SdkProvider when inside iframe. SDK initialized once via useRef, destroyed on unmount.
+10. **Permissions:** Every SDK method used must have permission declared in manifest.json.
+11. **CORS:** vercel.json must include all 3 Frontier OS origins (os.frontiertower.io, sandbox.os.frontiertower.io, localhost:5173).
+12. **SDK imports:** Use `@frontiertower/frontier-sdk` for SDK classes. Exact import paths, not barrel imports.
+</frontier_os_rules>
+
+<sdk_integration_execution>
+
+### SDK Integration Phase Execution
+
+For the SDK Integration phase (always the final phase), perform these mechanical operations:
+
+**Step 1: Add SDK dependency**
+```bash
+npm install @frontiertower/frontier-sdk
+```
+
+**Step 2: Create sdk-context.tsx**
+Render from `templates/app/sdk-context.tsx` to `src/lib/sdk-context.tsx`.
+This file is IDENTICAL across all apps — never customize it.
+
+**Step 3: Create sdk-services.tsx**
+Render from `templates/app/sdk-services.tsx` to `src/lib/sdk-services.tsx`.
+This adapter maps each `FrontierServices` method to the corresponding `sdk.getModule().method()` call.
+
+**Step 4: Upgrade frontier-services.tsx**
+Modify `src/lib/frontier-services.tsx` to add environment detection:
+- Import `isInFrontierApp` from `@frontiertower/frontier-sdk/ui-utils`
+- If in iframe: import and use `createSdkServices` from `./sdk-services`
+- If standalone: use existing `createMockServices()` (no change to mock code)
+
+**Step 5: Upgrade Layout.tsx**
+Follow standard Layout pattern from `templates/app/layout.tsx`:
+- Add `isInFrontierApp()` detection
+- Add `createStandaloneHTML()` fallback for standalone mode
+- Wrap children in `SdkProvider` when in iframe
+
+**Step 6: Add CORS origins to vercel.json**
+Replace vercel.json with full version from `templates/app/vercel.json` (has all 3 CORS origin blocks plus SPA rewrite).
+
+</sdk_integration_execution>
+
 <deviation_rules>
 **While executing, you WILL discover work not in the plan.** Apply these rules automatically. Track all deviations for Summary.
 
@@ -239,7 +348,7 @@ No user permission needed for Rules 1-3.
 
 **Trigger:** Code doesn't work as intended (broken behavior, errors, incorrect output)
 
-**Examples:** Wrong SDK method call, type errors, null pointer exceptions, broken imports, incorrect hook dependencies, missing await on SDK promises
+**Examples:** Wrong service method call, type errors, null pointer exceptions, broken imports, incorrect hook dependencies, missing await on service promises
 
 ---
 
@@ -247,7 +356,7 @@ No user permission needed for Rules 1-3.
 
 **Trigger:** Code missing essential features for correctness, security, or basic operation
 
-**Examples:** Missing error handling on SDK calls, no loading states, missing null checks on SDK responses, no standalone fallback in Layout, missing CORS headers in vercel.json, no dark theme on new components
+**Examples:** Missing error handling on service calls, no loading states, missing null checks on service responses, no dark theme on new components
 
 ---
 
@@ -255,7 +364,7 @@ No user permission needed for Rules 1-3.
 
 **Trigger:** Something prevents completing current task
 
-**Examples:** Missing dependency, wrong import path, build error, TypeScript error, missing SDK type export, Vite config issue
+**Examples:** Missing dependency, wrong import path, build error, TypeScript error, missing type export, Vite config issue
 
 ---
 
@@ -263,7 +372,7 @@ No user permission needed for Rules 1-3.
 
 **Trigger:** Fix requires significant structural modification
 
-**Examples:** Changing SDK module approach, switching from single view to router, changing state management strategy, adding a new SDK module not in manifest
+**Examples:** Changing service module approach, switching from single view to router, changing state management strategy, adding a new service module not in manifest
 
 **Action:** STOP --> return checkpoint with: what found, proposed change, why needed, impact, alternatives. **User decision required.**
 
@@ -400,11 +509,11 @@ tasks_completed: N/N
 
 - [Decision and rationale]
 
-## SDK Methods Used
+## Service Methods Used
 
 | Method | Module | Permission | Files |
 |--------|--------|------------|-------|
-| getBalanceFormatted() | Wallet | wallet:getBalanceFormatted | src/hooks/useBalance.ts |
+| wallet.getBalanceFormatted() | Wallet | wallet:getBalanceFormatted | src/hooks/useBalance.ts |
 
 ## Deviations from Plan
 

package/agents/fos-plan-checker.md

@@ -74,6 +74,8 @@ Then verify each level against the actual plan files.
 3. Check method signatures match (parameter types, return types)
 4. Verify the correct module accessor is used (e.g., `getWallet()` not `wallet()`)
 
+Feature phases access methods via `services.module.method()` (not `sdk.getModule().method()`). The method NAMES are the same — validate against sdk-surface.md for correctness. The import path should be `../lib/frontier-services`, not `../lib/sdk-context`.
+
 **Validation rules:**
 - Method must exist in @frontier-os-app-builder/references/sdk-surface.md
 - Module accessor must use the correct getter: `sdk.getWallet()`, `sdk.getStorage()`, etc.
@@ -101,6 +103,8 @@ issue:
 
 **Question:** Do SDK methods used in plans have corresponding permissions in manifest.json?
 
+For feature phases: permission mismatches are severity **warning** (permissions are enforced at SDK Integration). For SDK Integration phase: permission mismatches are severity **blocker** (permissions must match real SDK calls).
+
 **Process:**
 1. Extract all SDK method calls from plan tasks
 2. Map each to its required permission using the pattern: `sdk.getModule().method()` --> `module:method`
@@ -147,13 +151,14 @@ issue:
    - Files outside `src/` that should be inside
    - Wrong casing (lowercase views, PascalCase hooks)
    - Tests not in `src/test/`
-   - SDK-context.tsx modification (it must be identical across apps)
+   - Feature phase tasks importing from `sdk-context` instead of `frontier-services`
 
 **Red flags:**
 - `src/components/layout.tsx` (wrong case — should be `Layout.tsx`)
 - `src/useBalance.ts` (wrong location — should be `src/hooks/useBalance.ts`)
 - `tests/` at root (wrong — should be `src/test/`)
-- Any task modifying `src/lib/sdk-context.tsx`
+- Feature phase task importing from `src/lib/sdk-context` (should be `src/lib/frontier-services`)
+- Any task modifying `src/lib/sdk-context.tsx` (only created during SDK Integration phase)
 
 **Example issue:**
 ```yaml
@@ -176,30 +181,42 @@ issue:
    - `package.json` (correct scripts, dependencies)
    - `postcss.config.js` (imports @tailwindcss/postcss)
    - `tsconfig.json` (strict mode, correct types)
-   - `vercel.json` (all 5 CORS origins)
+   - `vercel.json`
    - `vite.config.ts`
    - `src/main.tsx`
-   - `src/lib/sdk-context.tsx`
-   - `src/views/Layout.tsx` (with isInFrontierApp, createStandaloneHTML, SdkProvider)
+   - `src/lib/frontier-services.tsx` (with `useServices()` export and `createMockServices()` export)
+   - `src/views/Layout.tsx` (with `FrontierServicesProvider`)
    - `src/styles/index.css` (Tailwind import, @theme block with all CSS variables, @layer base)
    - `.gitignore`
 2. Check that task actions mention key requirements:
-   - iframe detection via `isInFrontierApp()`
-   - Standalone fallback via `createStandaloneHTML()`
-   - SdkProvider wrapping children
+   - `useServices()` export in frontier-services.tsx
+   - `createMockServices()` export in frontier-services.tsx
+   - `FrontierServicesProvider` wrapping children in Layout
    - Dark theme CSS variables (all variables from T-01)
    - Plus Jakarta Sans font loading (T-03)
-   - 5 CORS origins in vercel.json (C-01)
    - Correct package.json scripts: dev, build, preview, lint, test (C-04)
 
+3. **BLOCKLIST CHECK** — Scan the plan for any of these. If found, it is a **blocker**:
+   - ❌ `sdk-context.tsx` referenced as a file to create — belongs to SDK Integration phase only
+   - ❌ `@frontiertower/frontier-sdk` in dependencies — SDK not installed until SDK Integration
+   - ❌ `isInFrontierApp` or `createStandaloneHTML` in any task action — SDK Integration concerns
+   - ❌ `SdkProvider` in any task action — use `FrontierServicesProvider` instead
+   - ❌ `useSdk` in any task action — use `useServices` instead
+   - ❌ `layout.tsx` template (without `-standalone`) — use `layout-standalone.tsx`
+   - ❌ `package.json` template (without `-standalone`) — use `package-standalone.json`
+   - ❌ `vercel.json` template (without `-standalone`) — use `vercel-standalone.json`
+   - ❌ `main-simple.tsx` template (without `-standalone`) — use `main-simple-standalone.tsx`
+
+   If the researcher recommended SDK patterns from production apps, the planner should NOT have included them in Phase 1. Flag as blocker with fix hint: "Phase 1 is standalone-first. Remove SDK artifacts and use standalone templates."
+
 **Example issue:**
 ```yaml
 issue:
   dimension: scaffold_completeness
   severity: blocker
-  description: "Scaffold plan missing vercel.json creation — required for CORS and SPA routing"
+  description: "Phase 1 plan creates sdk-context.tsx — this belongs to SDK Integration phase, not scaffold"
   plan: "01-01"
-  fix_hint: "Add task or expand existing task to create vercel.json with all 5 CORS origin blocks and SPA rewrite"
+  fix_hint: "Remove sdk-context.tsx from plan. Phase 1 uses frontier-services.tsx for the services layer."
 ```
 
 ## Dimension 5: Task Completeness
@@ -227,7 +244,7 @@ issue:
 issue:
   dimension: task_completeness
   severity: blocker
-  description: "Task 2 action says 'create payment handler' without specifying which SDK method (payWithFrontierDollar? transferOverallFrontierDollar?)"
+  description: "Task 2 action says 'create payment handler' without specifying which SDK method (transferFrontierDollar? transferOverallFrontierDollar?)"
   plan: "02-01"
   task: 2
   fix_hint: "Specify exact SDK method, parameters, return type, and error handling in action"
@@ -244,13 +261,14 @@ issue:
 
 **Frontier OS specific wiring patterns:**
 ```
-Hook --> Component: Does a view import and call the hook?
-Component --> SdkProvider: Is the view rendered inside SdkProvider?
-SDK call --> Error handling: Does the action mention try/catch?
-Router --> View: Does the router import the view component?
-Layout --> SdkProvider: Does Layout wrap children with SdkProvider?
+Hook --> Component: Does view import and call hook?
+Hook --> Services: Does hook import useServices() from frontier-services?
+Service call --> Error handling: Does action mention try/catch?
+Router --> View: Does router import view component?
 ```
 
+Note: SdkProvider wiring is checked only for SDK Integration phase plans.
+
 **Red flags:**
 - Hook created but no view imports it
 - View created but not added to router
@@ -329,6 +347,23 @@ issue:
 - Test files in wrong location
 - Test task with vague action ("write tests") instead of specific test cases
 
+## Dimension 10: SDK Integration Phase Completeness
+
+**Applies to:** SDK Integration phase plans only. Skip for feature phase plans.
+
+**Question:** Does the plan cover all mechanical steps for SDK Integration?
+
+**Checklist:**
+1. Plan includes task to add `@frontiertower/frontier-sdk` dependency (`npm install`)
+2. Plan includes task to create `src/lib/sdk-context.tsx` from template
+3. Plan includes task to create `src/lib/sdk-services.tsx` adapter
+4. Plan includes task to upgrade `src/lib/frontier-services.tsx` with environment detection
+5. Plan includes task to upgrade `src/views/Layout.tsx` with iframe detection + SdkProvider
+6. Plan includes task to add CORS origins to `vercel.json`
+7. Plan includes verification task (build, typecheck, full validation)
+
+**Severity:** blocker for any missing step — SDK Integration is standardized and every step is required.
+
 </verification_dimensions>
 
 <output_format>
@@ -357,6 +392,7 @@ Return structured PASS/FAIL with issues list:
 | 7 | Context Compliance | PASS/FAIL/N/A | [count] |
 | 8 | Scope Sanity | PASS/FAIL | [count] |
 | 9 | Test Coverage | PASS/FAIL | [count] |
+| 10 | SDK Integration Completeness | PASS/FAIL/N/A | [count] |
 
 ### Issues