arcane-cli 0.14.0 → 0.15.0

package/package.json

@@ -1,72 +1,72 @@
-{
-  "name": "arcane-cli",
-  "version": "0.14.0",
-  "description": "Arcane framework CLI — scaffold and manage governance files in consuming repositories",
-  "keywords": [
-    "arcane",
-    "cli",
-    "sdlc",
-    "methodology",
-    "governance",
-    "ai-agents",
-    "agent",
-    "spell",
-    "scaffolding",
-    "templates"
-  ],
-  "homepage": "https://github.com/codemagicianhq/arcane#readme",
-  "bugs": "https://github.com/codemagicianhq/arcane/issues",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/codemagicianhq/arcane.git"
-  },
-  "license": "MIT",
-  "author": "Code Magician LLC",
-  "type": "module",
-  "bin": {
-    "spell": "dist/index.js",
-    "arcane": "dist/index.js"
-  },
-  "files": [
-    "dist/"
-  ],
-  "engines": {
-    "node": ">=18"
-  },
-  "scripts": {
-    "build": "tsup && tsx scripts/copy-assets.ts",
-    "test": "vitest run",
-    "test:watch": "vitest",
-    "test:coverage": "vitest run --coverage",
-    "lint": "eslint src test",
-    "typecheck": "tsc --noEmit",
-    "check:version-bump": "tsx scripts/check-version-bump.ts",
-    "prepare": "husky"
-  },
-  "dependencies": {
-    "@inquirer/prompts": "^7.10.1",
-    "chalk": "^5.6.2",
-    "commander": "^12.0.0",
-    "gradient-string": "^3.0.0",
-    "yaml": "^2.8.3"
-  },
-  "devDependencies": {
-    "@eslint/js": "^9.0.0",
-    "@types/gradient-string": "^1.1.6",
-    "@types/node": "^20.0.0",
-    "@vitest/coverage-v8": "^3.2.7",
-    "eslint": "^9.0.0",
-    "husky": "^9.1.7",
-    "tsup": "^8.0.0",
-    "tsx": "^4.7.0",
-    "typescript": "^5.4.0",
-    "typescript-eslint": "^8.0.0",
-    "vitest": "^3.2.7"
-  },
-  "overrides": {
-    "esbuild": "^0.28.1"
-  },
-  "publishConfig": {
-    "registry": "https://registry.npmjs.org/"
-  }
-}
+{
+  "name": "arcane-cli",
+  "version": "0.15.0",
+  "description": "Arcane framework CLI — scaffold and manage governance files in consuming repositories",
+  "keywords": [
+    "arcane",
+    "cli",
+    "sdlc",
+    "methodology",
+    "governance",
+    "ai-agents",
+    "agent",
+    "spell",
+    "scaffolding",
+    "templates"
+  ],
+  "homepage": "https://github.com/codemagicianhq/arcane#readme",
+  "bugs": "https://github.com/codemagicianhq/arcane/issues",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/codemagicianhq/arcane.git"
+  },
+  "license": "MIT",
+  "author": "Code Magician LLC",
+  "type": "module",
+  "bin": {
+    "spell": "dist/index.js",
+    "arcane": "dist/index.js"
+  },
+  "files": [
+    "dist/"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
+  "scripts": {
+    "build": "tsup && tsx scripts/copy-assets.ts",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "test:coverage": "vitest run --coverage",
+    "lint": "eslint src test",
+    "typecheck": "tsc --noEmit",
+    "check:version-bump": "tsx scripts/check-version-bump.ts",
+    "prepare": "husky"
+  },
+  "dependencies": {
+    "@inquirer/prompts": "^7.10.1",
+    "chalk": "^5.6.2",
+    "commander": "^12.0.0",
+    "gradient-string": "^3.0.0",
+    "yaml": "^2.8.3"
+  },
+  "devDependencies": {
+    "@eslint/js": "^9.0.0",
+    "@types/gradient-string": "^1.1.6",
+    "@types/node": "^20.0.0",
+    "@vitest/coverage-v8": "^3.2.7",
+    "eslint": "^9.0.0",
+    "husky": "^9.1.7",
+    "tsup": "^8.0.0",
+    "tsx": "^4.7.0",
+    "typescript": "^5.4.0",
+    "typescript-eslint": "^8.0.0",
+    "vitest": "^3.2.7"
+  },
+  "overrides": {
+    "esbuild": "^0.28.1"
+  },
+  "publishConfig": {
+    "registry": "https://registry.npmjs.org/"
+  }
+}

package/dist/assets/.claude/commands/spell-eas-ios-deploy.md

@@ -1,9 +0,0 @@
-# EAS iOS Deploy
-
-Invoke the Arcane `spell-eas-ios-deploy` spell workflow.
-
-See the full prompt at `.github/prompts/spell-eas-ios-deploy.prompt.md` for the complete workflow definition.
-
----
-
-@.github/prompts/spell-eas-ios-deploy.prompt.md

package/dist/assets/.github/prompts/spell-eas-ios-deploy.prompt.md

@@ -1,183 +0,0 @@
----
-name: Spell — EAS iOS Deploy
-description: Ship an Expo/React Native app to TestFlight and the App Store via EAS Build + EAS Submit — initial one-time setup and every deploy after that
-argument-hint: What you need — "initial setup", "deploy" (cut + submit a new build), or a specific symptom (e.g. "capability sync failed", "build stuck")
-agent: agent
----
-
-## Executive Summary
-
-- This prompt ships an Expo/React Native app to Apple TestFlight/App Store using **EAS Build + EAS
-  Submit** — Expo's cloud build service. No local Mac or Xcode install is required.
-- Covers two flows: **initial one-time setup** (Apple enrollment → credentials → first build →
-  first submit) and **repeat deployments** (the two-command loop you run for every release after that).
-- Produces a signed production build uploaded to App Store Connect, visible in TestFlight once Apple
-  finishes processing it, with the app's native build number bumped and committed to the repo.
-- **Not** a general CI/CD ship spell — see `spell-ship` for the branch-merge / backend-deploy
-  lifecycle. This spell is the mobile-app-store-specific leaf step, and it is scoped deliberately to
-  the **EAS Build/Submit** tech stack — it does not cover local Xcode builds, Xcode Cloud, or Fastlane.
-  A team on one of those instead needs a different spell; the steps below assume EAS.
-
----
-
-Ship the app to TestFlight/App Store, or troubleshoot an EAS deploy issue, per the request in the
-prompt argument. If no argument was given, ask whether this is initial setup or a repeat deploy.
-
-### Placeholders
-
-Resolve each from `.arcane.json` / the project's `app.json` / `eas.json` / frontmatter; **ask the
-user rather than guessing or inventing a value** if any is unset. Never proceed with an unresolved
-placeholder still in a command you're about to run.
-
-| Placeholder | What it is | Where it lives once resolved |
-| --- | --- | --- |
-| `{APP_NAME}` | Display name shown on the App Store / home screen | `app.json` → `expo.name` |
-| `{BUNDLE_ID}` | iOS bundle identifier (and Android package, if shipping both) | `app.json` → `expo.ios.bundleIdentifier` |
-| `{APPLE_TEAM_ID}` | Apple Developer Team ID | `eas.json` → `submit.production.ios.appleTeamId` |
-| `{ASC_APP_ID}` | Numeric App Store Connect app ID | `eas.json` → `submit.production.ios.ascAppId` |
-| `{APPLE_ID_EMAIL}` | Apple ID used for the Developer/ASC account | `eas.json` → `submit.production.ios.appleId` |
-| `{EAS_PROJECT_ID}` | EAS/Expo project ID | `app.json` → `expo.extra.eas.projectId` |
-| `{EAS_ACCOUNT}` | EAS/Expo account or org slug the project lives under | `eas build`/`eas submit` output, or `eas whoami` |
-
-### Context files this spell reads
-
-- **`app.json`/`app.config.js`** (Expo config) — bundle identifier, current `version`, native
-  `buildNumber`, EAS project ID. If it doesn't exist, this isn't an Expo project — stop and say so.
-- **`eas.json`** — build + submit profiles. **If missing**, run `eas build:configure` first (it
-  scaffolds a starter `eas.json` interactively) before continuing with the steps below.
-- **Apple Developer Program membership** for `{APPLE_ID_EMAIL}` — must be an active, paid enrollment.
-  If you don't know whether it's active, ask the user to confirm at
-  developer.apple.com/account before starting initial setup — everything downstream depends on it.
-
-If **none** of these exist yet (a brand-new Expo project with no `eas.json` and no App Store Connect
-app record), start at **Phase A, step 1** — every step is written to work from that empty state.
-
----
-
-## Phase A — Initial one-time setup
-
-Run once per app. Skip to Phase B if `eas.json` already has a `submit.production.ios` block and a
-first build has already reached TestFlight.
-
-1. **Confirm Apple Developer Program enrollment** is active for `{APPLE_ID_EMAIL}` (paid,
-   developer.apple.com/account). Nothing below works without it.
-2. **Create the App Store Connect app record** — appstoreconnect.apple.com → My Apps → "+" → New App.
-   Fill in `{APP_NAME}`, `{BUNDLE_ID}` (create a matching Identifier first if one doesn't exist yet),
-   a SKU, and user access. Capture the numeric app ID it's assigned — that's `{ASC_APP_ID}`.
-3. **Log in to EAS**: `npx eas-cli login` (skip if already authenticated — `eas whoami` confirms).
-4. **Configure `eas.json`** if it doesn't already have what's needed:
-   ```jsonc
-   {
-     "cli": { "appVersionSource": "local" },
-     "build": {
-       "production": { "channel": "production", "autoIncrement": true }
-     },
-     "submit": {
-       "production": {
-         "ios": {
-           "appleId": "{APPLE_ID_EMAIL}",
-           "ascAppId": "{ASC_APP_ID}",
-           "appleTeamId": "{APPLE_TEAM_ID}"
-         }
-       }
-     }
-   }
-   ```
-   `appVersionSource: "local"` + `autoIncrement: true` on the build profile means EAS bumps the
-   native build number in `app.json` for you on every build — no manual version-bump step, ever.
-5. **First build**: `eas build --platform ios --profile production`. On a project with no
-   credentials yet, EAS interactively generates everything it needs **remotely** — Distribution
-   Certificate, Provisioning Profile, and (if the app uses push) an APNs key. No local keychain, no
-   Mac. Confirm each prompt; let EAS manage the private key material — you should never need to see
-   or copy it.
-6. **First submit**: `eas submit --platform ios --profile production --latest`. First time through,
-   it also sets up an **App Store Connect API key** for non-interactive submits (EAS-managed is
-   simplest — pick that unless there's a reason to upload your own). Confirm the role it grants when
-   asked (App Manager is enough for build submission).
-7. **Confirm it landed**: App Store Connect → your app → TestFlight → iOS builds. Apple's binary
-   processing takes ~5–10 minutes after a successful `eas submit` before the build appears there.
-
-## Phase B — Repeat deployments
-
-The two-command loop for every release after Phase A:
-
-1. Land the code changes; typecheck/build clean locally first.
-2. `eas build --platform ios --profile production --non-interactive`
-   (add `EXPO_NO_CAPABILITY_SYNC=1` up front if you know a capability-sync failure is coming —
-   see **Known pitfalls** below).
-3. `eas submit --platform ios --profile production --latest --non-interactive`
-4. **Commit the build-number bump**: step 2's `autoIncrement` rewrote `app.json`'s native build
-   number locally — `git add`/`git commit` it so the repo matches the binary that just shipped.
-5. Confirm in TestFlight (same as Phase A step 7).
-
-Re-running either command is always safe: `eas build` reuses existing valid credentials rather than
-regenerating them (it only creates new ones when something actually changed, like a new capability),
-and re-running `eas submit` after a failed attempt is a normal retry, not a duplicate submission risk.
-
-## Known pitfalls (verified, not hypothetical)
-
-- **"Failed to patch capabilities: X ON, Y OFF"** — happens when the App Store Connect app record is
-  already linked to `{BUNDLE_ID}` and Apple rejects EAS's automatic capability sync. Fix: set
-  `EXPO_NO_CAPABILITY_SYNC=1` for the build command, **and** manually toggle the capability (Push
-  Notifications, Sign in with Apple, Associated Domains, whatever the app just added) on in the Apple
-  Developer console under Identifiers → `{BUNDLE_ID}` → Capabilities. EAS syncing capabilities and you
-  toggling them by hand are two ways to the same end state; when the app is already linked, only the
-  manual toggle works.
-- **"Command must be re-run to pick up new updates configuration"** — EAS auto-installed
-  `expo-updates` mid-build because the config needed it and it wasn't present. Just re-run the exact
-  same build command once; it picks up cleanly the second time.
-- **A brand-new entitlement was just added** (e.g. Associated Domains, Sign in with Apple) — confirm
-  the App ID capability is toggled on in the Apple Developer console *before* building. A successful
-  build with a fresh "Provisioning Profile ... Updated: N seconds ago" in the credentials output is
-  itself the confirmation that the new entitlement is correctly provisioned — if the capability isn't
-  on yet, the build will fail at the signing step instead.
-- **Apple "Internal Server Error"** during API key creation or submission — Apple's servers are
-  occasionally flaky. Retry the identical command; no code or config change needed.
-- **Build succeeds but nothing changed on-device** — before assuming the deploy is broken, rule out
-  the mundane cause first: the tester didn't force-quit and reopen the app after installing the new
-  TestFlight build (a backgrounded process can survive an update). Confirm the visible build/version
-  number inside the app (a settings screen, an About row) matches what you just shipped before
-  debugging further.
-
-## Acceptance checklist
-
-- [ ] `eas build` output ends with "Build finished" and an artifact URL.
-- [ ] `eas submit` output ends with "Submitted your app to Apple App Store Connect!"
-- [ ] App Store Connect → TestFlight → iOS builds shows the new build number (allow 5–10 min for
-      Apple's processing).
-- [ ] The `autoIncrement`-bumped build number in `app.json` is committed — `git status` is clean.
-- [ ] If an entitlement changed this deploy, it visibly works on a fresh install of the new build.
-
-## Cross-references
-
-- **`spell-ship`** — the surrounding branch-merge / backend-CI-CD lifecycle, if this app ships
-  alongside a paired backend. This spell is the mobile-store-specific leaf step; run it after
-  `spell-ship`'s checklist is green for anything the app depends on, not instead of it.
-- **`spell-dotnet-expert`** and other stack-expert spells — the sibling "load expertise into any
-  agent" pattern. This spell goes one step further: it doesn't just load context, it executes the
-  actual build/submit commands.
-- **`spell-bump`** — coordinate with it if the app's marketing `version` (not just the native build
-  number this spell auto-increments) also needs a bump before shipping.
-- **`spell-todo`** — if a pitfall or gap surfaces mid-deploy that shouldn't block shipping today,
-  capture it there rather than scope-creeping this deploy.
-
-## Rules
-
-- **Never guess a placeholder.** If `{BUNDLE_ID}`, `{APPLE_TEAM_ID}`, `{ASC_APP_ID}`, or
-  `{APPLE_ID_EMAIL}` is unresolved, ask — do not invent a value or proceed with a literal placeholder
-  string in a real command.
-- **Never handle real credential material.** You should never need to see, paste, or commit a
-  Distribution Certificate private key, an App Store Connect API private key (`.p8`), or any
-  password — EAS manages all of it remotely. If a step seems to require pasting one, stop; something
-  is set up wrong.
-- **Confirm before `eas submit`.** Submitting puts a real binary in front of Apple's review /
-  TestFlight testers — it's outward-facing and not something to undo casually. Say what you're about
-  to submit and to which environment before running it.
-- **Confirm before setting `EXPO_NO_CAPABILITY_SYNC=1`.** Explain why it's needed (it disables an
-  automatic sync that would otherwise silently turn a capability off) rather than setting it
-  silently.
-- **Never force-regenerate credentials** (revoke + recreate a Distribution Certificate or
-  Provisioning Profile) without explicit confirmation — revoking a certificate invalidates every
-  build ever signed with it, including ones already live.
-- **A backend/API prod deploy the app depends on is a separate, separately-confirmed action.** Do
-  not fold it into a mobile build/submit step just because they're related.