@playcraft/cli 0.0.55 → 0.0.57

package/project-templates/threejs/skills/playable-record/scripts/lib/dev-server.mjs

@@ -5,36 +5,61 @@
  * real listening URL. Previously these were copy-pasted into verify-contract,
  * verify-firstwin and record-playable, which let the port-detection logic drift.
  *
- * Vite runs with strictPort:false, so when the preferred port (3000) is taken it
+ * Vite runs with strictPort:false, so when the preferred port (5173) is taken it
  * auto-increments. `detectDevUrl` parses Vite's `Local:` stdout line to recover
  * the actual port instead of guessing — this is what keeps devUrl correct under
  * port drift (see docs/harness/experiment-lessons.md §9.2).
+ * Do not use 6000: Chromium treats it as an unsafe port (ERR_UNSAFE_PORT).
  */
 
 import { spawn } from 'node:child_process';
+import http from 'node:http';
+
+/** Preferred Vite dev port — avoids PlayCraft frontend (:3000) and backend (:3001). */
+export const DEFAULT_DEV_PORT = 5173;
+export const DEFAULT_DEV_URL = `http://127.0.0.1:${DEFAULT_DEV_PORT}/`;
 
 const LOCAL_URL_RE = /Local:\s+(http:\/\/(?:localhost|127\.0\.0\.1):\d+\/)/;
+const ANSI_RE = /\x1b\[[0-9;]*m/g;
+
+/** Probe a URL with node:http (undici `fetch` can fail on 127.0.0.1 in some runtimes). */
+function probeHttp(url) {
+  return new Promise((resolve, reject) => {
+    const req = http.get(url, (res) => {
+      res.resume();
+      resolve(res.statusCode ?? 0);
+    });
+    req.setTimeout(2000, () => {
+      req.destroy();
+      reject(new Error('probe timeout'));
+    });
+    req.on('error', reject);
+  });
+}
 
-/** Poll a URL with HEAD until it responds or the timeout elapses. */
+/** Poll a URL until any non-5xx response arrives. */
 export async function waitForHttp(url, timeoutMs = 30000) {
   const start = Date.now();
+  let lastErr = '';
   while (Date.now() - start < timeoutMs) {
     try {
-      const res = await fetch(url, { method: 'HEAD' });
-      if (res.ok) return;
-    } catch {
-      /* retry */
+      const status = await probeHttp(url);
+      if (status < 500) return;
+      lastErr = `HTTP ${status}`;
+    } catch (err) {
+      lastErr = err instanceof Error ? err.message : String(err);
     }
     await new Promise((r) => setTimeout(r, 250));
   }
-  throw new Error(`Server not ready: ${url}`);
+  throw new Error(`Server not ready: ${url}${lastErr ? ` (${lastErr})` : ''}`);
 }
 
 /** Spawn `npm run dev` (Vite) bound to 127.0.0.1 with piped stdio for URL detection. */
 export function startDevServer(cwd) {
-  return spawn('npm', ['run', 'dev', '--', '--host', '127.0.0.1'], {
+  return spawn('npm', ['run', 'dev', '--', '--host', '127.0.0.1', '--port', String(DEFAULT_DEV_PORT), '--no-open'], {
     cwd,
     stdio: ['ignore', 'pipe', 'pipe'],
+    env: { ...process.env, BROWSER: 'none' },
   });
 }
 
@@ -53,7 +78,7 @@ export function startHttpServer(port, cwd) {
  * @returns {string | null}
  */
 export function parseLocalUrl(text) {
-  const m = String(text).match(LOCAL_URL_RE);
+  const m = String(text).replace(ANSI_RE, '').match(LOCAL_URL_RE);
   return m ? m[1] : null;
 }
 
@@ -66,25 +91,35 @@ export function parseLocalUrl(text) {
  * @returns {Promise<string>}
  */
 export function detectDevUrl(child, preferredUrl, timeoutMs = 30000) {
-  return new Promise((res) => {
+  return new Promise((res, rej) => {
+    let buf = '';
     const timer = setTimeout(() => {
       cleanup();
       res(preferredUrl);
     }, timeoutMs);
     const onData = (data) => {
-      const url = parseLocalUrl(data);
+      buf += String(data);
+      const url = parseLocalUrl(buf);
       if (url) {
         clearTimeout(timer);
         cleanup();
         res(url);
       }
     };
+    const onExit = (code) => {
+      clearTimeout(timer);
+      cleanup();
+      const tail = buf.trim().slice(-1500);
+      rej(new Error(`dev server exited ${code} before publishing a Local URL${tail ? `\n${tail}` : ''}`));
+    };
     const cleanup = () => {
       child.stdout?.off('data', onData);
       child.stderr?.off('data', onData);
+      child.off('exit', onExit);
     };
     child.stdout?.on('data', onData);
     child.stderr?.on('data', onData);
+    child.once('exit', onExit);
   });
 }
 

package/project-templates/threejs/skills/playable-record/scripts/record-playable.mjs

@@ -11,6 +11,7 @@ import { chromium } from 'playwright';
 import { evaluateContract, snapshotContractInPage } from './verify-contract.mjs';
 import {
   detectDevUrl,
+  DEFAULT_DEV_URL,
   pickServerPort,
   startDevServer,
   startHttpServer,
@@ -314,7 +315,7 @@ async function main() {
     externalServer = true;
   } else if (opts.useDev) {
     server = startDevServer(projectRoot);
-    const preferredUrl = opts.url || 'http://127.0.0.1:3000/';
+    const preferredUrl = opts.url || DEFAULT_DEV_URL;
     console.log(`[record] Starting dev server, waiting for ${preferredUrl}`);
     const detectedUrl = await detectDevUrl(server, preferredUrl, 30000);
     opts.url = detectedUrl;

package/project-templates/threejs/skills/playable-record/scripts/verify-contract.mjs

@@ -19,14 +19,14 @@
  * Exit 0 = contract satisfied, 2 = contract broken, 1 = unexpected error.
  *
  * Usage:
- *   node skills/playable-record/scripts/verify-contract.mjs --root=. --use-dev --url=http://localhost:3000/
+ *   node skills/playable-record/scripts/verify-contract.mjs --root=. --use-dev --url=http://localhost:5173/
  *   node skills/playable-record/scripts/verify-contract.mjs --root=.            # standalone http-server
- *   node skills/playable-record/scripts/verify-contract.mjs --url=http://localhost:3000/ --json
+ *   node skills/playable-record/scripts/verify-contract.mjs --url=http://localhost:5173/ --json
  */
 
 import { resolve } from 'node:path';
 import { fileURLToPath } from 'node:url';
-import { detectDevUrl, startDevServer, startHttpServer, waitForHttp } from './lib/dev-server.mjs';
+import { detectDevUrl, startDevServer, startHttpServer, waitForHttp, DEFAULT_DEV_URL } from './lib/dev-server.mjs';
 import { writeValidatorArtifact } from '../../_shared/scripts/lib/validator-artifacts.mjs';
 
 const DEFAULT_SCENE = 'MainScene';
@@ -178,7 +178,7 @@ export async function runContractProbe(opts) {
     external = true;
   } else if (opts.useDev) {
     server = startDevServer(projectRoot);
-    url = await detectDevUrl(server, opts.url || 'http://127.0.0.1:3000/', 30000);
+    url = await detectDevUrl(server, opts.url || DEFAULT_DEV_URL, 30000);
   } else {
     server = startHttpServer(opts.port, projectRoot);
     url = `http://127.0.0.1:${opts.port}/game/index.html`;

package/project-templates/threejs/skills/playable-record/scripts/verify-firstwin.mjs

@@ -6,7 +6,7 @@
  * polls getState() until isGameOver && currentPhase === 'ENDCARD', then exits 0.
  *
  * Usage:
- *   node skills/playable-record/scripts/verify-firstwin.mjs --root=. --use-dev --url=http://localhost:3000/
+ *   node skills/playable-record/scripts/verify-firstwin.mjs --root=. --use-dev --url=http://localhost:5173/
  *   npm run verify:firstwin
  *
  * Exit 0 = first level winnable (ENDCARD reached)
@@ -18,7 +18,7 @@ import { readdir, readFile } from 'node:fs/promises';
 import { resolve } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { evaluateContract, snapshotContractInPage } from './verify-contract.mjs';
-import { detectDevUrl, startDevServer, startHttpServer, waitForHttp } from './lib/dev-server.mjs';
+import { detectDevUrl, startDevServer, startHttpServer, waitForHttp, DEFAULT_DEV_URL } from './lib/dev-server.mjs';
 import { writeValidatorArtifact } from '../../_shared/scripts/lib/validator-artifacts.mjs';
 
 const DEFAULT_SCENE = 'MainScene';
@@ -198,7 +198,7 @@ export async function runFirstWinProbe(opts) {
     /* external server */
   } else if (opts.useDev) {
     server = startDevServer(projectRoot);
-    url = await detectDevUrl(server, opts.url || 'http://127.0.0.1:3000/', 30000);
+    url = await detectDevUrl(server, opts.url || DEFAULT_DEV_URL, 30000);
   } else {
     server = startHttpServer(opts.port, projectRoot);
     url = `http://127.0.0.1:${opts.port}/game/index.html`;

package/project-templates/threejs/skills/playable-record/scripts/verify-fusion.mjs

@@ -19,8 +19,14 @@ import { readFile, readdir } from 'node:fs/promises';
 import { existsSync } from 'node:fs';
 import { join, resolve, basename } from 'node:path';
 import { writeValidatorArtifact } from '../../_shared/scripts/lib/validator-artifacts.mjs';
+import {
+  detectFusionIntent,
+  readFusionIntentFromProject,
+} from '../../_shared/scripts/lib/fusion-intent.mjs';
 
 // `[*_\s]*` tolerates markdown emphasis in the §6 template form `- **Fusion type**:`.
+const FUSION_COMPOSITE_ATOMS = new Set(['arrow_pick_match_rules.aigameplay']);
+
 const FUSION_TYPE_RE =
   /Fusion\s+type[*_\s]*:\s*(Single|A-Visual|B1-Passive|B2-Active|C-Sequential|D-Parallel)/i;
 const REAL_FUSION_TYPES = new Set(['A-Visual', 'B1-Passive', 'B2-Active', 'C-Sequential', 'D-Parallel']);
@@ -56,6 +62,19 @@ export const GAMEPLAY_SIGNATURES = {
     'escape_core',
     'canMoveArrow',
   ],
+  'path_elimination_rules.aigameplay': [
+    'path_elimination',
+    'canPathExitBoard',
+    'removedPaths',
+    'findFirstRemovablePath',
+  ],
+  'arrow_pick_match_rules.aigameplay': [
+    'arrow_pick_match',
+    'slideOutToTray',
+    'trayCapacity',
+    'LevelValidator',
+    'pick_and_match',
+  ],
 };
 
 function parseArgs(argv) {
@@ -212,7 +231,23 @@ export async function verifyFusion(root, overrides = {}) {
     gameplayAtoms = readSelectedGameplayAtoms(tree);
   }
 
-  if (gameplayAtoms.length < 2) {
+  const singleCompositeFusion =
+    gameplayAtoms.length === 1 && FUSION_COMPOSITE_ATOMS.has(gameplayAtoms[0] ?? '');
+
+  if (gameplayAtoms.length < 2 && !singleCompositeFusion) {
+    const { intentTags, rawIntent } = readFusionIntentFromProject(root);
+    if (detectFusionIntent(intentTags, rawIntent)) {
+      const selected = gameplayAtoms[0] ?? '(none)';
+      return {
+        ok: false,
+        skipped: false,
+        problems: [
+          `fusion intent detected but only one gameplay atom selected (${selected}) — pick a fusion skill (e.g. arrow_pick_match_rules.aigameplay) or document Single + downgrade reason in DESIGN.md ## 6`,
+        ],
+        gameplayAtoms,
+        fusionIntent: true,
+      };
+    }
     return { ok: true, skipped: true, reason: 'single gameplay atom — fusion no-op PASS' };
   }
 
@@ -224,7 +259,7 @@ export async function verifyFusion(root, overrides = {}) {
 
   if (!type) {
     problems.push('DESIGN.md missing Fusion type: — classify fusion in ## 6. Gameplay Fusion');
-  } else if (type === 'Single' && !isPseudoFusion) {
+  } else if (type === 'Single' && !isPseudoFusion && !singleCompositeFusion) {
     problems.push(
       `DESIGN.md Fusion type is Single but atom-tree selected ${gameplayAtoms.length} gameplay atoms — use a real fusion type or document pseudo-fusion`,
     );

package/project-templates/threejs/skills/playable-record/scripts/verify-slice.mjs

@@ -21,7 +21,7 @@
 import fs from 'node:fs';
 import path from 'node:path';
 import { fileURLToPath } from 'node:url';
-import { detectDevUrl, startDevServer, startHttpServer, waitForHttp } from './lib/dev-server.mjs';
+import { detectDevUrl, startDevServer, startHttpServer, waitForHttp, DEFAULT_DEV_URL } from './lib/dev-server.mjs';
 import { getActiveSlice, readState } from '../../_shared/scripts/state-store.mjs';
 
 function parseArgs(argv) {
@@ -57,7 +57,7 @@ export async function runSliceProbe(opts) {
     /* external server */
   } else if (opts.useDev) {
     server = startDevServer(root);
-    url = await detectDevUrl(server, opts.url || 'http://127.0.0.1:3000/', 30000);
+    url = await detectDevUrl(server, opts.url || DEFAULT_DEV_URL, 30000);
   } else {
     server = startHttpServer(opts.port, root);
     url = `http://127.0.0.1:${opts.port}/game/index.html`;

package/project-templates/threejs/templates/design-brief.template.md

@@ -3,16 +3,13 @@
 <!--
   Living discovery log — NOT a substitute for docs/DESIGN.md (the playable seed contract).
 
-  Ring 1 (slice-axis):
-  - Record how core action / feedback / progress / constraints were discovered.
-  - Feed the minimal slice queue; do NOT write layout, style, CTA polish, or production plans here.
-
-  Rings 2–4:
-  - Deepen periphery, layout intent, Hook/CTA, style direction as those rings disclose.
-  - Ring 2 (slice-axis): append periphery discovery → 2–4 developer slices; not a feature backlog.
+  Maintained across all rings — each ring's clarify phase appends new discovery.
+  Record how core action / feedback / progress / constraints were discovered.
+  Feed the slice queue; do NOT write layout, style, CTA polish, or production plans here.
 
   Update rules:
   - Create at the start of clarify; append after each brainstorm round.
+  - Maintain across rings — do not discard prior-ring discovery.
   - Preserve source tags; do not polish away evidence.
 
   Source tags: [USER] [WEB] [SKILL] [AGENT] [ASSUMPTION][confidence: high/medium/low]
@@ -56,6 +53,40 @@ Append-only evidence (newest first or chronological — pick one and stay consis
 
 ## Brainstorm Log
 
+### Creative Angle
+
+- **Idea hook**: {If only one core moment survives — from Phase 1 candidates}
+- **Emotional payoff**: {What the player should feel after the first win}
+- **Anti-generic**: {Why this is not "ordinary arrow + tray match-3"}
+
+### Pattern picked
+
+- Pattern: {id from `playcraft patterns match`} [{SOURCE}]
+- Why this over alternatives: {one line}
+
+### Reference insight
+
+- {3–5 bullets from patterns match or `playcraft tools research --focus gameplay`} [{WEB|SKILL}]
+- researchSkippedReason: {only if no research/patterns — explain why}
+
+### Motion moments (Ring 1)
+
+- First tap: {slide_out visual — what moves, how long}
+- First blocked: {blocked shake/tint — teach dependency}
+- First match-3: {match_clear in tray — payoff moment}
+- Rejected motion: {why not swap/gravity cascade / board match3 — e.g. "主手势是 path tap，三消仅在托盘"}
+
+### Mechanic variation
+
+- {One axis beyond stitching two skills: e.g. tray pressure curve / blocked dependency layers / board phase unlock}
+- rejectedShallowFusion: {why not all-free opening or ≤4 paths on 8×8}
+
+### Gameplay Lens (3 questions)
+
+1. Core action in one verb: {…}
+2. After 3–5 steps the player gets: {…}
+3. With sound off for 10s, gameplay guessable? {yes/no + why}
+
 ### Round 1
 
 - Asked: {question and why it mattered for core action / feedback}
@@ -64,9 +95,9 @@ Append-only evidence (newest first or chronological — pick one and stay consis
 
 ---
 
-## Core Discovery (Ring 1 scope)
+## Core Discovery
 
-> Full Hook / Tutorial / Gameplay / End Card packaging is **Ring 2+**. Ring 1 only needs enough to seed verifiable developer slices.
+> Record core gameplay discovery for the current ring. Later rings deepen periphery, layout intent, Hook/CTA, and style direction as those rings disclose.
 
 ### Player action chain
 
@@ -78,11 +109,11 @@ Append-only evidence (newest first or chronological — pick one and stay consis
 
 - Engine hint basis: {phaser / threejs + why} [{SOURCE}]
 - Semantic placeholders: {player; target; feedback; reward; …} [{SOURCE}]
-- Out of scope for Ring 1: layout zones, style direction, CTA copy, asset production
+- Out of scope: layout zones, style direction, CTA copy, asset production (unless current ring discloses them)
 
 ---
 
-## Quality check (Ring 1)
+## Quality check
 
 - [ ] Core action is explicit, not implied
 - [ ] Feedback timing is stated

package/project-templates/threejs/templates/design-methodology.md

@@ -1,7 +1,6 @@
 # Design Methodology Foundations
 
-> **When to read**: Game Designer reads this before Step 4 (Five-Axis Evaluation) to ground decisions in theory.
-> Artist and Reviewer may also reference this for context on emotional intent.
+> **When to read**: `@creative-director` and `@game-designer` during Ring 1 creative/spec (via `npm run state:get` → `referenceReads`). Ground Narrative Level and Emotional Arc before writing north-star or DESIGN §0.
 
 ---
 

package/project-templates/threejs/templates/design.template.md

@@ -13,6 +13,32 @@
 
 ---
 
+## 0. Creative North Star
+
+> Ring 1 reader entry. Write this **before** mechanics tables. Copy from `docs/north-star.md`: **One-liner** verbatim; **Micro-Story Spine** field-value match (trim per field).
+
+### Micro-Story Spine
+
+**Narrative level**: {L0 | L1 | L2}
+**Who**: {from north-star}
+**Situation**: {from north-star}
+**Stakes**: {from north-star}
+**Payoff image**: {from north-star}
+**Emotional arc**: {from north-star}
+
+**One-liner**: {One vivid sentence — what feeling/tension the player is playing with, not a mechanic checklist.}
+
+**System Dynamic**: {One sentence — what system tension keeps the player acting.}
+
+**Why this fusion**: {2–3 sentences — how arrow / elimination / tray **serve** the idea above, not "because the user asked for fusion". Start with: "This fusion serves §0 because…"}
+
+**Rejected vibe**:
+
+- {Not this — e.g. not a casual match-3 binge}
+- {Not this — e.g. not a pure arrow logic puzzle with no payoff}
+
+---
+
 ## Player Action
 
 {What the player can do first: tap / drag / aim / choose. Name the visible target and why the action is obvious.}
@@ -29,6 +55,18 @@
 
 {How the first level guarantees success: constrained setup, guided target, no failure timer, locked failure path, or simplified rule.}
 
+## Core Fun & Feedback
+
+### Peak Moment
+
+{1-2 core satisfying moments: when triggered → what the player sees/hears → emotional response. Be concrete — name the visual element, the sound cue, the motion.}
+
+### Feedback Layers
+
+| Action   | Instant (<100ms)       | Result                    | Enhancement (combo/special) |
+| -------- | ---------------------- | ------------------------- | --------------------------- |
+| {action} | {press/touch feedback} | {success animation/sound} | {combo/chain payoff}        |
+
 ## Semantic Placeholders
 
 | Placeholder | Meaning in Ring 1                            | Required? |
@@ -48,3 +86,42 @@
 ## Open Assumptions
 
 {Only list assumptions that materially affect Ring 1. Use "none" if clear.}
+
+---
+
+## 6. Gameplay Fusion
+
+Fusion type: {Single | A-Visual | B1-Passive | B2-Active | C-Sequential | D-Parallel}
+
+This fusion serves §0 because {link back to One-liner / System Dynamic keywords}.
+
+{One paragraph: which parent mechanics combine, interaction contract (not just skill names), and why this fusion is playable first.}
+
+## 7. Gameplay Seed
+
+First Level Scenario: {8×8 board, path count, blocked vs opening moves, tray pressure — must match docs/level-sketch.json}
+
+Player Fantasy: {2–3 sentences from the player's POV. **Expand from Micro-Story Who + Situation** — not a generic "solve puzzle + match-3" line.}
+
+Decision Moment: {One aha or mis-tap moment — e.g. blocked path feedback → find unlock order.}
+
+## 8. Feedback & Animation Spine
+
+### 8.1 Event Catalog（必填）
+
+| Event       | Trigger                     | Visual (Ring 1)                         | Audio placeholder | Duration budget | Blocks input? |
+| ----------- | --------------------------- | --------------------------------------- | ----------------- | --------------- | ------------- |
+| slide_out   | valid tap on free path      | path container tween along direction    | sfx_slide         | 300–400ms       | yes           |
+| blocked     | invalid tap on blocked path | board shake + path red tint             | sfx_blocked       | ~300ms          | no            |
+| fly_to_tray | after slide_out             | head bezier to tray slot                | sfx_land          | 350–450ms       | yes           |
+| match_clear | 3 same color in tray        | tray burst + scale pop                  | sfx_match         | 200–300ms       | yes           |
+| win         | board empty + tray clear    | overlay + optional confetti placeholder | sfx_win           | ≤800ms          | yes           |
+
+### 8.2 Atom / Skill refs
+
+- Primary: `slide_out_to_tray_animation.aicomponent` (defaults: slide 350ms, fly 400ms)
+- Secondary: `path_animation.aicomponent` (blocked shake)
+
+### 8.3 Juice escalation (Ring 1 minimal)
+
+- Combo/streak: optional; if n/a, state "flat feedback, escalate in Ring 2"

package/project-templates/threejs/templates/five-axis-framework.md

@@ -5,12 +5,35 @@
 > **Stage relevance**:
 >
 > - **ring 1 `loop: clarify`**: Only **Axis 1 (Mechanic)** and **Axis 3 (Interaction Modality)** must be resolved — they define core playability (可解性) and time/operation budget. The other axes only need a rough direction signal (e.g. "2D", "L1 character present", "Competence arc").
-> - **ring 2 `loop: clarify` (after MC)**: Axis 2 (Dimension), Axis 4 (Narrative Level), and Axis 5 (Emotional Arc) get their full specification when visual direction is confirmed by MC selection.
+> - **ring 2 `loop: clarify` (after MC (Master Composite, 主合成图))**: Axis 2 (Dimension), Axis 4 (Narrative Level), and Axis 5 (Emotional Arc) get their full specification when visual direction is confirmed by MC selection.
 >
 > **This framework is a thinking aid, not a production template.** Game Designer should focus on gameplay first; use these axes to check coverage, not to fill out forms.
 
 The five axes are **orthogonal** — each is an independent decision. The same Match-3 game can be Flat 2D or 2.5D, Tap-only or Drag, L0 or L1, Competence Arc or Challenge Arc. Game Designer evaluates all five internally, then presents 2-3 complete options (covering all axes) for the user to choose from.
 
+## Playable-Ad First Principle
+
+The five axes are not a recipe for adding more ideas. They are a filter for one short playable-ad delight loop:
+
+```text
+Hook Conflict
+→ First Action
+→ Instant Feedback
+→ Escalating Decision
+→ Payoff Release
+→ Install Curiosity
+```
+
+Before applying any axis, Game Designer must know the primary player desire:
+
+- What makes the user stop?
+- What makes the first action obvious and tempting?
+- What feedback makes the player feel in control?
+- What payoff happens within 3-5 actions?
+- What unfinished promise carries the CTA (Call To Action, 行动号召)?
+
+Any axis choice or fusion idea is valid only if it strengthens at least one part of this loop. If a secondary mechanic only makes the concept sound richer, but does not improve hook, first action, feedback, payoff, or install curiosity, downgrade it to visual dressing or pseudo-fusion.
+
 ---
 
 ## Axis 1 — Mechanic (Gameplay Fusion Types)
@@ -28,6 +51,32 @@ The five axes are **orthogonal** — each is an independent decision. The same M
 
 When the user insists on Type C/D, recommend pseudo-fusion: **visually appear as two systems, but the underlying mechanic is single**. Example: Match-3 elimination count drives a monster HP bar — the user only performs match-3 the entire time, but perceives "elimination + combat."
 
+### Fusion Quality Bar
+
+For every non-`Single` option, answer:
+
+| Question                                                    | Pass Signal                                                      |
+| ----------------------------------------------------------- | ---------------------------------------------------------------- |
+| What is the primary joy?                                    | One clear emotion source, not a list of features                 |
+| Which loop stage does the secondary mechanic strengthen?    | Hook, first action, feedback, payoff, or install curiosity       |
+| Does the secondary mechanic require a new tutorial gesture? | No, or the cost is explicitly justified                          |
+| Does the payoff become stronger?                            | The player sees a bigger release than the primary mechanic alone |
+| Can it be understood in the ad timeline?                    | The user can grasp it without reading a rules paragraph          |
+
+If these answers are weak, the fusion is probably decorative complexity.
+
+### Mechanic Depth beyond Stitching
+
+| Pattern                                       | When to use                                | Depth signal                                               |
+| --------------------------------------------- | ------------------------------------------ | ---------------------------------------------------------- |
+| **Composite atom** (`arrow_pick_match_rules`) | Path + tray match already fused in one PGS | Single interaction contract; prefer over stitching parents |
+| **Pseudo-fusion B1**                          | Visual dual system, single reducer         | Secondary mechanic auto-triggers — document reducer        |
+| **Board phase B1**                            | Same 8×8 grid, mask unlock                 | Board "changes" via phase, not resize                      |
+
+**Forbidden in DESIGN:** listing two parent skill names without **interaction contract** (who acts, where match happens, what blocked teaches).
+
+See also: `.claude/agents/refs/game-designer-fusion-depth-playbook.md`
+
 ### Decision Rules
 
 ```

package/project-templates/threejs/templates/game-designer-creative-process.template.md

@@ -0,0 +1,99 @@
+# Creative Process — {Game Name}
+
+<!--
+  Ring 1 clarify audit trail. Fill phases 1–4 BEFORE finalizing DESIGN.md.
+  Source: templates/game-designer-creative-process.template.md
+-->
+
+**Created**: {YYYY-MM-DD}
+**Creative arm**: {A1 | A2 | A3 — from GD_CREATIVE_ARM env if harness}
+
+---
+
+## Phase 1 — Radical Diverge
+
+List ≥3 **gameplay core-moment** candidates. Do not write DESIGN.md yet.
+
+### Candidate A
+
+- **Core moment**: {one sentence}
+- **Story hook**: {15s filmable Hook frame}
+- **Who / Stakes**: {one line each}
+- **Why interesting**: {…}
+- **Core challenge**: {…}
+- **Worst case**: {what breaks if player ignores rules}
+
+### Candidate B
+
+- **Core moment**: {…}
+- **Story hook**: {…}
+- **Who / Stakes**: {…}
+- **Why interesting**: {…}
+- **Core challenge**: {…}
+- **Worst case**: {…}
+
+### Candidate C
+
+- **Core moment**: {…}
+- **Story hook**: {…}
+- **Who / Stakes**: {…}
+- **Why interesting**: {…}
+- **Core challenge**: {…}
+- **Worst case**: {…}
+
+---
+
+## Phase 2 — Adversarial Review (five questions)
+
+For each candidate, answer **evidence-based** questions — not aesthetic veto.
+
+| Candidate | Q1 Second tap? | Q2 Ignore mechanism? | Q3 White-box fun? | Q4 Depth ceiling? | Q5 Strip story — still care? |
+| --------- | -------------- | -------------------- | ----------------- | ----------------- | ---------------------------- |
+| A         | {…}            | {…}                  | {…}               | {…}               | {…}                          |
+| B         | {…}            | {…}                  | {…}               | {…}               | {…}                          |
+| C         | {…}            | {…}                  | {…}               | {…}               | {…}                          |
+
+**Vulnerability list** (falsifiable, not "not fun"):
+
+- {bullet}
+- {bullet}
+
+---
+
+## Phase 3 — Commitment
+
+**Chosen candidate**: {A | B | C}
+
+**Narrative level**: {L0 | L1 | L2} — {CD decides; if L0, quote user's explicit opt-out request here}
+
+**Patch promises** (how this design addresses vulnerabilities):
+
+- {…}
+
+**Rejected alternatives**:
+
+- {B}: deferred because {…}
+- {C}: deferred because {…}
+
+**Pressure test memo** (≤30 lines):
+
+- White-box: {…}
+- 1-minute test: {…}
+- Depth test: {…}
+
+---
+
+## Phase 4 — Design Intent
+
+**Design Intent**: {e.g. "Player aha at move 3 when blocked path unlocks tray combo"}
+
+> **Mandatory sync**: Copy **Design Intent verbatim** into `docs/DESIGN.md` §0 **One-liner**. Copy **System Dynamic** into §0 second field. Copy **Micro-Story Spine** fields field-for-field from `docs/north-star.md`.
+
+**Mechanic variation** (vs pure stitch): {one axis — tray pressure / phase unlock / segment density}
+
+**Rejected shallow fusion**: {e.g. all-free 4 paths on 8×8}
+
+**Pattern / skills locked after commitment**:
+
+- Pattern: {from playcraft patterns match}
+- Primary skill: {e.g. arrow_pick_match_rules.aigameplay}