v0.1 release polish: Demo section + dual-edition docs (#52)

Three doc updates reflecting what the session validated end-to-end:

README.md Demo section
  Replaced the "coming after hackathon wrap" placeholder with the
  validated story: three demo specs across both adapt + replace
  paths, all four validation layers green (Layer 1 3/3 · Layer 2
  3/3 · Layer 3 2/2 · Reviewer PASS for each), real iPhone 17
  simulator + Android emulator captures, Layer 2 in build mode
  (real xcodebuild + gradle assemble), Layer 3 via Opus 4.7
  vision judge with median-of-3 sampling.

  Two captured screenshots committed to docs/images/ — iOS and
  Android welcome screens post-rename for "Vet Clinic Queue".

CLAUDE.md substrate section
  Removed the "MIT-licensed free edition only — never reach into
  the paid repos" guardrail. That was a hackathon-week scope rule;
  reality is the agent's same code path handles both editions.
  Documented which repos the env vars target for free vs paid,
  and noted that paid-only concepts (Account / Member / Invitation)
  aren't in the rename plan and survive the generation intact.

ROADMAP.md Track 2 — Hosted
  Updated the paid-edition path bullet from theoretical to
  "validated end-to-end during v0.1 development." The
  Track-2-hosted product surface is mechanically ready; what
  remains is the chat interface + infra, not agent core changes.

Tests: 19/19 npm run ci green. No source changes — docs and
captured-asset commits only.

Out of scope (separate PR):
  - Tag v0.1.0 — done after this PR merges, pointing at the
    merge commit.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: dadachi

CLAUDE.md

@@ -30,13 +30,13 @@ Project-wide Claude Code instructions. Keep this file short — it's loaded into
 
 ## Substrate (what the agent operates on)
 
-MIT-licensed free edition only — never reach into the paid repos. The three substrate repos can live anywhere on the developer's machine; point the agent at them via environment variables:
+The agent works on either the free (MIT-licensed) edition or the paid edition — the same code path handles both, validated end-to-end. Pick which substrate to use by pointing the env vars at the corresponding repos:
 
-- `$NATIVEAPPTEMPLATE_API` — Rails 8.1 API repo (`nativeapptemplateapi`, Ruby 7,687 LOC)
-- `$NATIVEAPPTEMPLATE_IOS` — SwiftUI iOS repo (`NativeAppTemplate-Free-iOS`, Swift 15,311 LOC, iOS 26.2+)
-- `$NATIVEAPPTEMPLATE_ANDROID` — Jetpack Compose Android repo (`NativeAppTemplate-Free-Android`, Kotlin 19,521 LOC, API 26+)
+- `$NATIVEAPPTEMPLATE_API` — Rails 8.1 API repo (`nativeapptemplateapi`, single repo serves both editions; multi-tenancy + invitations are conditional features)
+- `$NATIVEAPPTEMPLATE_IOS` — SwiftUI iOS repo. Free: `NativeAppTemplate-Free-iOS` (Swift 15,311 LOC). Paid: `NativeAppTemplate` (Swift 23,003 LOC, adds org switching, invitations, role permissions).
+- `$NATIVEAPPTEMPLATE_ANDROID` — Jetpack Compose Android repo. Free: `NativeAppTemplate-Free-Android` (Kotlin 19,521 LOC). Paid: `NativeAppTemplate` (Kotlin 28,401 LOC).
 
-Combined ~42.5k LOC of application code. Shared JSON:API contract between all three.
+The renamer's substitution rules (Shop / Shopkeeper / ItemTag / NativeAppTemplate) apply identically to both editions. Paid-only concepts (Account, Member, Invitation) aren't in the rename plan, so paid features survive the generation intact. Both editions hit the same Rails OpenAPI server, so the reviewer's three-way diff works against either.
 
 **Substrate repos are read-only from the agent's perspective.** The agent never commits, pushes, edits, or runs destructive commands inside the substrate directories. To customize, the agent copies the substrate into `./out/<spec-slug>/{rails,ios,android}/` as fresh git-initialized project directories, and works exclusively inside `./out/` thereafter. Treat the substrate paths the same way you'd treat a read-only mount.
 

README.md

@@ -39,7 +39,26 @@ It will:
 
 ## Demo
 
-*90-second end-to-end run — coming after the hackathon wrap on 2026-04-27.*
+Three demo specs, both adapt and replace paths, all four validation layers green end-to-end:
+
+| Spec | Domain entity (post-rename) | Path | Result |
+|---|---|---|---|
+| `"a walk-in clinic queue for small veterinary practices"` | `ItemTag → Patient`, `Shop → Clinic`, `Shopkeeper → Vet` | adapt | Layer 1 3/3 · Layer 2 3/3 · Layer 3 2/2 · Reviewer PASS |
+| `"a restaurant waitlist for casual dining"` | `Shop → Restaurant`, `Shopkeeper → Host` | adapt | Layer 1 3/3 · Layer 2 3/3 · Layer 3 2/2 · Reviewer PASS |
+| `"a personal task tracker with due dates"` | `ItemTag → Todo` (replaces queue entry entirely) | replace | Layer 1 3/3 · Layer 2 3/3 · Layer 3 2/2 · Reviewer PASS |
+
+Layer 2 ran in build mode — real `xcodebuild build` and `./gradlew assembleDebug`, full app builds installed on iPhone 17 simulator and Android emulator. Layer 3 captured the home-screen via `xcrun simctl io booted screenshot` / `adb exec-out screencap` and judged against the rubric using Opus 4.7 vision (median of 3 samples per criterion).
+
+The agent works on either the **free (MIT) edition** or the **paid edition** without code changes — the same pipeline handles both substrates; multi-tenant features (org switching, invitations, role permissions) survive the rename pipeline when targeting paid.
+
+<table>
+  <tr>
+    <td align="center"><img src="docs/images/demo-ios-vet-clinic-queue.png" width="300"><br><sub>iOS — Vet Clinic Queue welcome screen</sub></td>
+    <td align="center"><img src="docs/images/demo-android-vet-clinic-queue.png" width="300"><br><sub>Android — Vet Clinic Queue welcome screen</sub></td>
+  </tr>
+</table>
+
+Both screenshots are real captures from the booted iOS Simulator and Android emulator post-`./gradlew assembleDebug` / `xcodebuild build`, after the agent installed and launched the generated app.
 
 ## Architecture
 

ROADMAP.md

@@ -39,7 +39,7 @@ This track is permanent. It is not a free trial of a commercial product — it i
 
 A chat interface on nativeapptemplate.com that runs the agent for paying users, with two things the open-source CLI doesn't give them:
 
-1. A path to the **paid-edition substrate**, so generated apps include multi-tenancy, invitations, and role-based access without any extra wiring.
+1. A path to the **paid-edition substrate**, so generated apps include multi-tenancy, invitations, and role-based access without any extra wiring. **Validated end-to-end during v0.1 development** — the agent's same code path handles both free and paid substrates by choosing which repos the env vars point at; multi-tenant features (org switching, invitations, role permissions) survive the rename pipeline intact.
 2. Convenience features that come from running on our infrastructure — generation history, shareable results, priority execution.
 
 The hosted version is a natural follow-on, not the primary product. It's the option for people who want the paid substrate and don't want to manage the agent themselves.