shotops-mcp 0.9.4 → 0.9.6

package/README.md

@@ -74,7 +74,7 @@ The key is never copied, printed, or sent to ShotOps, and no release tool is ins
 - **`panelPresetId`** — App Store size: `r69` (default, 6.9″ iPhone 1290×2796), `r65`, `r55`.
   **iPhone sizes only** — the iPad presets are deliberately not offered, because no iPad device
   model exists yet and rendering one would put an iPhone body in an iPad-shaped canvas. The
-  accepted set is `RENDERABLE_PANEL_PRESET_IDS` in `shotops-mcp/src/panelCatalog.ts`, a subset of
+  accepted set is `RENDERABLE_PANEL_PRESET_IDS` in `shotops-mcp/src/render/panelCatalog.ts`, a subset of
   the hand-kept `PANEL_PRESET_IDS` copy of `mockup-engine/appstore.ts`'s `PANEL_PRESETS` — when
   Apple revises required sizes, add the preset in the engine first, then mirror it here.
 - **`style`** — the structured styling input. On both the hosted MCP and the local
@@ -630,29 +630,18 @@ point — connect directly to the hosted server (above) for those.
 ```
 shotops-mcp/
   src/
-    app.ts          the Express app as a pure factory (OAuth AS router + /oauth/callback +
-                    /mcp's per-request auth gate + stateless transport) — driveable in tests
-                    with injected deps; server.ts calls it with the real Supabase-backed ones
-    server.ts       wires app.ts's real deps (Supabase-backed auth/looks/oauth) + listens
-    auth.ts         thin wrapper over the verifyApiToken substrate (covers both shotops_ tokens
-                    and OAuth-minted tokens — both are api_tokens rows)
-    oauthProvider.ts  the OAuth 2.1 Authorization Server (DCR + PKCE + token mint) the SDK's
-                    mcpAuthRouter drives; delegates human login to Supabase Google sign-in
-    oauthStore.ts   OAuth AS persistence (mcp_oauth_clients / mcp_oauth_auth_codes), raw
-                    service-role PostgREST, RLS-on-no-policies like api_tokens/share_links
-    supabaseLogin.ts  the Supabase Google-login leg (server-side PKCE, /oauth/callback)
-    tools.ts        render/bundle/project/look/upload/import/delete handlers + registrar
-    schemas.ts      zod input schemas incl. the structured `style` (no store-credential field exists) + panel presets
-    renderer.ts     StripRenderer — boots Vite (hosted) or the static harness (local) + Chromium once, exposes render(input)
-    staticServer.ts  the tiny node:http static server for harness-dist/ (local mode's serve path)
-    lookStore.ts    per-PROJECT looks + projects resolver (ownership enforced in code; D1 record/pinned_record pair)
-    shareEmit.ts    emit_bundle's server-side share-link creation (reuses Phase-2 modules)
-    uploads.ts      Phase 10 — upload slots, ref ownership check, output:'urls' storage
-    screenshotInput.ts  Phase 10 — resolves screenshots[] (inline/ref/url/path) to base64
-    env.ts          loads ../.env.local; MCP_PORT / STUDIO_ORIGIN / SHOTOPS_AUTH_ORIGIN / MCP_PUBLIC_URL
-    local.ts        the LOCAL npx entry point — stdio transport, no auth required to preview
-    localDeps.ts     the local ToolDeps fork — static-serve renderer, no-op/bridged persistence
-    hostedBridge.ts  local→hosted bridge (a real MCP client using your shotops_ token)
+    server.ts       hosted HTTP entry point
+    local.ts        local stdio server and release CLI entry point
+    nitroApp.ts     Nitro adapter for the hosted app
+    packagePaths.ts stable runtime asset anchor for source and bundled execution
+    tools/          registration and tool handlers; shared dependency contract
+    contracts/      schemas, instructions, result envelopes and tool metadata
+    project/        project/Look resolution, persistence and refinement adapters
+    render/         screenshot intake, rendering and output delivery
+    production/     authorization, charging and durable production workflows
+    release/        local release preparation, review, commit and recovery
+    auth/           OAuth, caller authentication, consent and anonymous access
+    runtime/        server/dependency wiring, process state, environment and widgets
   harness/          the browser render page Chromium loads (render.js exposes window.renderStrip)
   vite.config.mjs   hosted (Vite dev server) harness config — mirrors mockup-mcp's headless-render setup
   vite.harness.config.mjs  the STATIC harness build (local mode's publish prerequisite) → harness-dist/
@@ -663,3 +652,7 @@ shotops-mcp/
   static-parity.ts  pixel-diffs the static-serve render against the Vite-dev render (must be 0)
   pack-smoke.ts     THE publish gate — npm pack, install OUTSIDE the repo, drive a real render
 ```
+
+Tests and fixtures live beside their subjects. Shared services import each other directly;
+`tools/tools.ts` only registers handlers. Folder placement rules live in
+[the file-moves skill](../.claude/skills/file-moves/SKILL.md#mcp-source-folder-placement).