Fix cheatsheet type-check errors in scaffolded projects

Rename cheatsheet.d.ts to cheatsheet.txt so it's never type-checked.
Fix multi-line signature collapsing (track brace depth in awk).
Add scaffolded-project type-check step to release process.

Bump version to 0.12.1.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: jsvd

.claude/skills/release/SKILL.md

@@ -47,6 +47,21 @@ cargo check --no-default-features 2>&1 | tail -3  # Headless check
 
 All must pass before proceeding. Record the test counts (e.g., "2028 Node + 2125 V8 + 292 Rust").
 
+Also verify that generated declaration files type-check correctly in a scaffolded project:
+
+```bash
+# Regenerate declarations (ensures cheatsheet is fresh)
+scripts/generate-declarations.sh
+
+# Create a temp project and type-check it
+TMPDIR=$(mktemp -d)
+cargo run -- new "$TMPDIR/release-check" 2>&1
+cd "$TMPDIR/release-check" && npx -p typescript tsc --noEmit 2>&1
+cd - && rm -rf "$TMPDIR"
+```
+
+If type-checking fails, fix the generated files before proceeding.
+
 ### 4. Update status docs with fresh test counts
 
 #### a. `README.md`

CHANGELOG.md

@@ -2,6 +2,11 @@
 
 All notable changes to Arcane are documented here.
 
+## [0.12.1] - 2026-02-18
+
+### Fixed
+- **Cheatsheet breaks type-checking** — renamed `cheatsheet.d.ts` to `cheatsheet.txt` so it's never type-checked. Fixed multi-line signature collapsing in the generator script. Added scaffolded-project type-check verification to the release process.
+
 ## [0.12.0] - 2026-02-18
 
 ### Added

CLAUDE.md

@@ -4,7 +4,7 @@
 
 Arcane is a code-first, test-native, agent-native 2D game engine. Rust core for performance, TypeScript scripting for game logic.
 
-**Current status: v0.12.0 — DX improvements. Unified Color API, particle presets, knockback, palette. 2082 TS (Node) + 2179 (V8) + 292 Rust tests passing. Next: Phase 26 (Atmosphere).**
+**Current status: v0.12.1 — DX improvements. Unified Color API, particle presets, knockback, palette. 2082 TS (Node) + 2206 (V8) + 292 Rust tests passing. Next: Phase 26 (Atmosphere).**
 
 ## Repository Structure
 

Cargo.lock

@@ -96,7 +96,7 @@ Rails for games. Rails didn't beat Java by being more powerful — it beat it by
 
 ## Status
 
-**v0.12.0 — DX improvements: color API, particle presets, knockback, palette!**
+**v0.12.1 — DX improvements: color API, particle presets, knockback, palette!**
 
 Install: [`cargo install arcane-engine`](https://crates.io/crates/arcane-engine)
 

README.md

@@ -1,6 +1,6 @@
 [package]
 name = "arcane-engine"
-version = "0.12.0"
+version = "0.12.1"
 edition.workspace = true
 license.workspace = true
 description = "Arcane game engine — agent-native 2D engine with embedded TypeScript runtime"
@@ -17,7 +17,7 @@ name = "arcane"
 path = "src/main.rs"
 
 [dependencies]
-arcane-core = { version = "0.12.0", path = "../core", features = ["renderer"] }
+arcane-core = { version = "0.12.1", path = "../core", features = ["renderer"] }
 clap = { version = "4", features = ["derive"] }
 tokio = { version = "1", features = ["full"] }
 anyhow = "1"

cli/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "arcane-core"
-version = "0.12.0"
+version = "0.12.1"
 edition.workspace = true
 license.workspace = true
 description = "Core library for Arcane - agent-native 2D game engine (TypeScript runtime, renderer, platform layer)"

core/Cargo.toml

@@ -125,15 +125,16 @@ for entry in "${MODULES[@]}"; do
 done
 
 # Step 3: Generate cheatsheet (compact one-liner signatures from all modules)
+# Output is .txt (not .d.ts) so it never gets type-checked — it's a reference doc.
 echo "Generating cheatsheet..."
-CHEATSHEET="$OUT_DIR/cheatsheet.d.ts"
+CHEATSHEET="$OUT_DIR/cheatsheet.txt"
 {
-  echo "// Arcane Engine — API Cheatsheet"
-  echo "// Generated from runtime source. Do not edit manually."
-  echo "// Regenerate with: ./scripts/generate-declarations.sh"
-  echo "//"
-  echo "// One-liner signatures for every exported function, grouped by module."
-  echo "// For full JSDoc, argument types, and examples, see the per-module files in types/."
+  echo "Arcane Engine — API Cheatsheet"
+  echo "Generated from runtime source. Do not edit manually."
+  echo "Regenerate with: ./scripts/generate-declarations.sh"
+  echo ""
+  echo "One-liner signatures for every exported function, grouped by module."
+  echo "For full JSDoc, argument types, and examples, see the per-module .d.ts files in types/."
   echo ""
 
   for entry in "${MODULES[@]}"; do
@@ -144,34 +145,49 @@ CHEATSHEET="$OUT_DIR/cheatsheet.d.ts"
       continue
     fi
 
-    echo "// --- $dir (@arcane/runtime/$dir) ---"
+    echo "=== $dir (@arcane/runtime/$dir) ==="
 
     # Extract type names (one-liner summary)
     type_names=$(grep -E '^\s+export type \w+ ' "$module_file" 2>/dev/null | sed 's/.*export type \([A-Za-z_][A-Za-z0-9_]*\).*/\1/' | sort -u | tr '\n' ', ' | sed 's/, $//') || true
     if [ -n "$type_names" ]; then
-      echo "// Types: $type_names"
+      echo "Types: $type_names"
     fi
 
-    # Extract function declarations (just the signature line)
-    grep -E '^\s+export declare function ' "$module_file" 2>/dev/null | while IFS= read -r line; do
-      # Strip leading whitespace and "export " prefix
-      trimmed="${line#"${line%%[! ]*}"}"
-      trimmed="${trimmed#export }"
-      echo "$trimmed"
-    done || true
-
-    # Extract const declarations (just name and type)
-    grep -E '^\s+export declare const ' "$module_file" 2>/dev/null | while IFS= read -r line; do
-      trimmed="${line#"${line%%[! ]*}"}"
-      trimmed="${trimmed#export }"
-      echo "$trimmed"
-    done || true
+    # Extract function and const signatures, collapsing multi-line ones.
+    # Tracks brace depth so "loop?: boolean;" inside {…} doesn't end the sig.
+    awk '
+      BEGIN { buf = ""; depth = 0 }
+      /^[[:space:]]+export declare (function|const) / {
+        sub(/^[[:space:]]+/, "")
+        sub(/^export /, "")
+        buf = $0
+        depth = 0
+        for (i = 1; i <= length($0); i++) {
+          c = substr($0, i, 1)
+          if (c == "{") depth++
+          else if (c == "}") depth--
+        }
+        if (depth <= 0 && buf ~ /;[[:space:]]*$/) { print buf; buf = ""; depth = 0 }
+        next
+      }
+      { if (buf != "") {
+          sub(/^[[:space:]]+/, "")
+          buf = buf " " $0
+          for (i = 1; i <= length($0); i++) {
+            c = substr($0, i, 1)
+            if (c == "{") depth++
+            else if (c == "}") depth--
+          }
+          if (depth <= 0 && buf ~ /;[[:space:]]*$/) { print buf; buf = ""; depth = 0 }
+        }
+      }
+    ' "$module_file" || true
 
     echo ""
   done
 } > "$CHEATSHEET"
 cheatsheet_lines=$(wc -l < "$CHEATSHEET")
-echo "  cheatsheet.d.ts ($cheatsheet_lines lines)"
+echo "  cheatsheet.txt ($cheatsheet_lines lines)"
 
 # Step 4: Clean up
 rm -rf "$DIST_DIR"

scripts/generate-declarations.sh

@@ -231,7 +231,7 @@ Read the **Essential** guides first, then the genre-specific guides for your gam
 
 ## API Quick Reference
 
-See [`types/cheatsheet.d.ts`](types/cheatsheet.d.ts) for every exported function as a one-liner, grouped by module. The 20 most common functions:
+See [`types/cheatsheet.txt`](types/cheatsheet.txt) for every exported function as a one-liner, grouped by module. The 20 most common functions:
 
 | Function | Module | What it does |
 |----------|--------|-------------|
@@ -262,7 +262,7 @@ Per-module type files with JSDoc documentation. Check these before using unfamil
 
 | File | Module |
 |------|--------|
-| `types/cheatsheet.d.ts` | **All modules** — compact one-liner signatures |
+| `types/cheatsheet.txt` | **All modules** — compact one-liner signatures |
 | `types/rendering.d.ts` | `@arcane/runtime/rendering` |
 | `types/ui.d.ts` | `@arcane/runtime/ui` |
 | `types/physics.d.ts` | `@arcane/runtime/physics` |

templates/default/AGENTS.md

@@ -2,6 +2,6 @@
 
 Read [AGENTS.md](AGENTS.md) for the full guide on building this game with Arcane.
 
-API declarations are in `types/*.d.ts` (one file per module: rendering, physics, game, ui, etc.). Start with [`types/cheatsheet.d.ts`](types/cheatsheet.d.ts) for a compact overview of every function. Use `/api` to look up specific functions.
+API declarations are in `types/*.d.ts` (one file per module: rendering, physics, game, ui, etc.). Start with [`types/cheatsheet.txt`](types/cheatsheet.txt) for a compact overview of every function. Use `/api` to look up specific functions.
 
 **Essential topic guides** (read before coding): rendering, coordinates, tweening, particles, juice, transitions, input, entities. See the full list and genre-specific reading order in AGENTS.md.