safeword 0.6.3 → 0.6.5

package/templates/guides/architecture-guide.md

@@ -1,6 +1,6 @@
 # Architecture & Design Documentation Guide
 
-**See:** `@.safeword/guides/llm-instruction-design.md` for LLM-consumable documentation principles.
+**See:** `@.safeword/guides/llm-guide.md` for LLM-consumable documentation principles.
 
 ---
 

package/templates/guides/cli-reference.md

@@ -0,0 +1,35 @@
+# Safeword CLI Reference
+
+Commands for managing safeword in projects.
+
+## Commands
+
+| Command                       | Purpose                                        |
+| ----------------------------- | ---------------------------------------------- |
+| `npx safeword@latest setup`   | Install safeword in current project            |
+| `npx safeword@latest check`   | Check project health and versions              |
+| `npx safeword@latest upgrade` | Upgrade to latest version                      |
+| `npx safeword@latest diff`    | Preview changes before upgrading               |
+| `npx safeword sync`           | Sync linting plugins with project dependencies |
+| `npx safeword reset`          | Remove safeword from project                   |
+
+## When to Use
+
+| Situation                  | Command                       |
+| -------------------------- | ----------------------------- |
+| New project setup          | `npx safeword@latest setup`   |
+| Check if update available  | `npx safeword@latest check`   |
+| Update after CLI release   | `npx safeword@latest upgrade` |
+| See what upgrade changes   | `npx safeword@latest diff`    |
+| Added/removed framework    | `npx safeword sync`           |
+| Remove safeword completely | `npx safeword reset --full`   |
+
+## Options
+
+Run `npx safeword <command> --help` for command-specific options.
+
+Common flags:
+
+- `-y, --yes` - Skip confirmations (setup, reset)
+- `-v, --verbose` - Show detailed output (diff)
+- `-q, --quiet` - Suppress output (sync)

package/templates/guides/code-philosophy.md

@@ -1,6 +1,6 @@
 # Code Philosophy & Practices
 
-**Note:** This file provides instructions for LLM-based coding agents. For comprehensive framework on writing clear, actionable LLM-consumable instructions, see `@.safeword/guides/llm-instruction-design.md`.
+**Note:** This file provides instructions for LLM-based coding agents. For comprehensive framework on writing clear, actionable LLM-consumable instructions, see `@.safeword/guides/llm-guide.md`.
 
 ---
 
@@ -41,19 +41,21 @@ Examples:
 - **Explicit error handling** - NEVER suppress or swallow errors silently
 
 **Error handling examples:**
-| ❌ Bad | ✅ Good |
-|--------|---------|
-| `catch (e) {}` (swallowed) | `catch (e) { throw new Error(\`Failed to read ${filePath}: ${e.message}\`) }`|
-|`catch (e) { console.log(e) }`|`catch (e) { logger.error('Payment failed', { userId, amount, error: e }) }` |
-| Generic "Something went wrong" | "Failed to save user profile: database connection timeout" |
+
+| ❌ Bad                         | ✅ Good                                                                       |
+| ------------------------------ | ----------------------------------------------------------------------------- |
+| `catch (e) {}` (swallowed)     | `catch (e) { throw new Error(\`Failed to read ${filePath}: ${e.message}\`) }` |
+| `catch (e) { console.log(e) }` | `catch (e) { logger.error('Payment failed', { userId, amount, error: e }) }`  |
+| Generic "Something went wrong" | "Failed to save user profile: database connection timeout"                    |
 
 **Naming examples:**
-| ❌ Bad | ✅ Good |
-|--------|---------|
-| `calcTot` | `calculateTotalWithTax` |
+
+| ❌ Bad             | ✅ Good                        |
+| ------------------ | ------------------------------ |
+| `calcTot`          | `calculateTotalWithTax`        |
 | `d`, `tmp`, `data` | `userProfile`, `pendingOrders` |
-| `handleClick` | `submitPaymentForm` |
-| `process()` | `validateAndSaveUser()` |
+| `handleClick`      | `submitPaymentForm`            |
+| `process()`        | `validateAndSaveUser()`        |
 
 **When to comment:**
 
@@ -63,13 +65,14 @@ Examples:
 - ❌ Restating the function name
 
 **Bloat examples (avoid these):**
-| ❌ Bloat | ✅ Instead |
-|----------|-----------|
-| Utility class for one function | Single function |
-| Factory pattern for simple object | Direct construction |
-| Abstract base class with one implementation | Concrete class |
-| Config file for 2 options | Hardcode or simple params |
-| "Future-proofing" unused code paths | Delete, add when needed |
+
+| ❌ Bloat                                    | ✅ Instead                |
+| ------------------------------------------- | ------------------------- |
+| Utility class for one function              | Single function           |
+| Factory pattern for simple object           | Direct construction       |
+| Abstract base class with one implementation | Concrete class            |
+| Config file for 2 options                   | Hardcode or simple params |
+| "Future-proofing" unused code paths         | Delete, add when needed   |
 
 **When to push back:** If a feature request would add >50 lines for a "nice to have", ask: "Is this essential now, or can we add it later?"
 
@@ -106,7 +109,7 @@ Examples:
 - ✅ If a test fails, fix the implementation—not the test
 - ✅ If a test seems wrong or requirements changed, explain why and ask before changing it
 
-**Workflow:** See `@.safeword/guides/testing-methodology.md` for comprehensive TDD workflow (RED → GREEN → REFACTOR phases)
+**Workflow:** See `@.safeword/guides/development-workflow.md` for comprehensive TDD workflow (RED → GREEN → REFACTOR phases)
 
 ## Debugging & Troubleshooting
 

package/templates/guides/context-files-guide.md

@@ -224,7 +224,7 @@ See @README for project overview and @package.json for available npm commands.
 
 ## Coding Standards
 
-@.safeword/guides/llm-prompting.md
+@.safeword/guides/llm-guide.md
 
 ## Git Workflow
 
@@ -415,7 +415,7 @@ Brief description. Current status.
 
 **Critical:** These files are instructions consumed by LLMs.
 
-**See:** `@.safeword/guides/llm-instruction-design.md` for 13 core principles for writing LLM-consumable documentation.
+**See:** `@.safeword/guides/llm-guide.md` for 13 core principles for writing LLM-consumable documentation.
 
 ### Quality Checklist
 

package/templates/guides/data-architecture-guide.md

@@ -2,7 +2,7 @@
 
 **Context:** How to document data architecture decisions, models, and flows for software projects. Applies LLM instruction design principles for clarity and reliability.
 
-**See:** `@.safeword/guides/llm-instruction-design.md` for comprehensive framework on writing LLM-consumable documentation.
+**See:** `@.safeword/guides/llm-guide.md` for comprehensive framework on writing LLM-consumable documentation.
 
 ---
 

package/templates/guides/design-doc-guide.md

@@ -168,4 +168,4 @@ Before saving, verify:
 
 **Important:** Design docs are instructions that LLMs read and follow.
 
-**See:** `@.safeword/guides/llm-instruction-design.md` for comprehensive framework on writing clear, actionable documentation that LLMs can reliably follow.
+**See:** `@.safeword/guides/llm-guide.md` for comprehensive framework on writing clear, actionable documentation that LLMs can reliably follow.

package/templates/guides/{testing-methodology.md → development-workflow.md}

@@ -614,5 +614,5 @@ npm run test:e2e # E2E tests only
 
 **Cascading precedence:**
 
-1. **Global** (`~/.claude/testing-methodology.md`) - Universal methodology (test type selection, TDD workflow)
+1. **Global** (`~/.claude/development-workflow.md`) - Universal methodology (test type selection, TDD workflow)
 2. **Project** (`tests/SAFEWORD.md`) - Specific stack, commands, patterns

package/templates/guides/learning-extraction.md

@@ -2,7 +2,7 @@
 
 Extract reusable knowledge from debugging sessions and implementation discoveries. Ensures insights compound across sessions.
 
-**LLM Instruction Design:** Learnings are documentation that LLMs read and follow. Apply best practices from `@.safeword/guides/llm-instruction-design.md` when writing learning files (concrete examples, explicit definitions, MECE principles).
+**LLM Instruction Design:** Learnings are documentation that LLMs read and follow. Apply best practices from `@.safeword/guides/llm-guide.md` when writing learning files (concrete examples, explicit definitions, MECE principles).
 
 ---
 

package/templates/guides/{llm-instruction-design.md → llm-guide.md}

@@ -1,12 +1,76 @@
-# Writing Instructions for LLMs
+# LLM Guide
 
-**Context:** When creating documentation that LLMs will read and follow (like AGENTS.md, CLAUDE.md, testing guides, coding standards), different best practices apply than when prompting an LLM directly.
+This guide covers two related topics:
 
-## Core Principles
+**Part 1: Integration** - How to call LLMs effectively (API calls, structured outputs, caching, testing)
 
-**1. MECE Principle (Mutually Exclusive, Collectively Exhaustive)**
+**Part 2: Writing for LLMs** - How to write documentation that LLMs will read and follow (SAFEWORD.md, CLAUDE.md, guides)
 
-Decision trees and categorization must have no overlap and cover all cases. Research shows LLMs struggle with overlapping categories—McKinsey/BCG MECE framework ensures clear decision paths.
+---
+
+## Part 1: Integration
+
+### Structured Outputs
+
+Use JSON mode for predictable LLM responses. Define explicit schemas with validation. Return structured data, not prose.
+
+```typescript
+// ❌ BAD - Prose output
+"The user wants to create a campaign named 'Shadows' with 4 players"
+
+// ✅ GOOD - Structured JSON
+{ "intent": "create_campaign", "name": "Shadows", "playerCount": 4 }
+```
+
+### Cost Optimization
+
+**Prompt Caching (Critical for AI Agents):**
+
+- Static rules → System prompt with cache_control: ephemeral (caches for ~5 min, auto-expires)
+- Dynamic data (character state, user input) → User message (no caching)
+- Example: 468-line prompt costs $0.10 without caching, $0.01 with (90% reduction)
+- Cache invalidation: ANY change to cached blocks breaks ALL caches
+- Rule: Change system prompts sparingly; accept one-time cache rebuild cost
+
+**Message Architecture:**
+
+```typescript
+// ✅ GOOD - Cacheable system prompt
+systemPrompt: [
+  { text: STATIC_RULES, cache_control: { type: 'ephemeral' } },
+  { text: STATIC_EXAMPLES, cache_control: { type: 'ephemeral' } },
+];
+userMessage: `Character: ${dynamicState}\nAction: ${userInput}`;
+
+// ❌ BAD - Uncacheable (character state in system prompt)
+systemPrompt: `Rules + Character: ${dynamicState}`;
+```
+
+### Testing AI Outputs
+
+**LLM-as-Judge Pattern:**
+
+- Use LLM to evaluate nuanced qualities (narrative tone, reasoning quality)
+- Avoid brittle keyword matching for creative outputs
+- Define rubrics: EXCELLENT / ACCEPTABLE / POOR with criteria
+- Example: "Does the GM's response show collaborative tone?" vs checking for specific words
+
+**Evaluation Framework:**
+
+- Unit tests: Pure functions (parsing, validation)
+- Integration tests: Agent + real LLM calls (schema compliance)
+- LLM Evals: Judgment quality (position/effect reasoning, atmosphere)
+- Cost awareness: 30 scenarios ≈ $0.15-0.30 per run with caching
+
+---
+
+## Part 2: Writing for LLMs
+
+When creating documentation that LLMs will read and follow (AGENTS.md, CLAUDE.md, testing guides, coding standards), apply these principles:
+
+### 1. MECE Principle (Mutually Exclusive, Collectively Exhaustive)
+
+Decision trees must have no overlap and cover all cases. LLMs struggle with overlapping categories.
 
 ```markdown
 ❌ BAD - Not mutually exclusive:
@@ -26,7 +90,7 @@ Problem: A function with database calls could match both
 Stops at first match, no ambiguity.
 ```
 
-**2. Explicit Over Implicit**
+### 2. Explicit Over Implicit
 
 Never assume LLMs know what you mean. Define all terms, even "obvious" ones.
 
@@ -41,7 +105,7 @@ Examples needing definition:
 - "Pure function" → Input → output, no I/O (define edge cases like Date.now())
 ```
 
-**3. No Contradictions**
+### 3. No Contradictions
 
 Different sections must align. LLMs don't reconcile conflicting guidance. When updating, grep for related terms and update all references.
 
@@ -57,7 +121,7 @@ Section B: "All critical multi-page user flows have at least one E2E test"
 - Definition of "critical" with examples
 ```
 
-**4. Concrete Examples Over Abstract Rules**
+### 4. Concrete Examples Over Abstract Rules
 
 Show, don't just tell. LLMs learn patterns from examples. For every rule, include 2-3 concrete examples showing good vs bad.
 
@@ -78,9 +142,9 @@ expect(calculateDiscount(100, 0.20)).toBe(80)
 })
 ```
 
-**5. Edge Cases Must Be Explicit**
+### 5. Edge Cases Must Be Explicit
 
-What seems obvious to humans often isn't to LLMs. After stating a rule, add "Edge cases:" section with common confusing scenarios.
+What seems obvious to humans often isn't to LLMs. After stating a rule, add "Edge cases:" section.
 
 ```markdown
 ❌ BAD: "Unit test pure functions"
@@ -94,9 +158,9 @@ Edge cases:
 - Mixed pure + I/O → Extract pure part, unit test separately
 ```
 
-**6. Actionable Over Vague**
+### 6. Actionable Over Vague
 
-Give LLMs concrete actions, not subjective guidance. Replace subjective terms (most/some/few) with optimization rules + red flags.
+Replace subjective terms with optimization rules + red flags.
 
 ```markdown
 ❌ BAD: "Most tests: Fast, Some tests: Slow"
@@ -108,9 +172,9 @@ Give LLMs concrete actions, not subjective guidance. Replace subjective terms (m
 - Red flag: If you have more E2E tests than integration tests, suite is too slow
 ```
 
-**7. Decision Trees: Sequential Over Parallel**
+### 7. Decision Trees: Sequential Over Parallel
 
-Structure decisions as ordered steps, not simultaneous checks. Sequential questions force the LLM through a deterministic decision path.
+Structure decisions as ordered steps, not simultaneous checks.
 
 ```markdown
 ❌ BAD - Parallel branches:
@@ -118,11 +182,11 @@ Structure decisions as ordered steps, not simultaneous checks. Sequential questi
 ├─ Multiple components?
 └─ Full user flow?
 
-✅ GOOD - Sequential (see Principle 1 example above)
+✅ GOOD - Sequential:
 Answer questions IN ORDER. Stop at the first match.
 ```
 
-**8. Tie-Breaking Rules**
+### 8. Tie-Breaking Rules
 
 When multiple options could apply, tell LLMs how to choose.
 
@@ -134,9 +198,9 @@ Reference in decision trees:
 "If multiple seem to apply, use the tie-breaking rule stated above: choose the faster one."
 ```
 
-**9. Lookup Tables for Complex Decisions**
+### 9. Lookup Tables for Complex Decisions
 
-When decision logic has 3+ branches, nested conditions, or multiple variables to consider, provide a reference table.
+When decision logic has 3+ branches, provide a reference table.
 
 ```markdown
 | Bug Type           | Unit? | Integration? | E2E? | Best Choice       |
@@ -146,16 +210,16 @@ When decision logic has 3+ branches, nested conditions, or multiple variables to
 | CSS layout broken  | ❌    | ❌           | ✅   | E2E (only option) |
 ```
 
-**10. Avoid Caveats in Tables**
+### 10. Avoid Caveats in Tables
 
-Keep patterns clean. Parentheticals break LLM pattern matching. Add separate rows for caveat cases.
+Keep patterns clean. Parentheticals break LLM pattern matching.
 
 ```markdown
 ❌ BAD: | State management bug | ❌ NO (if mocked) | ✅ YES |
 ✅ GOOD: | State management bug (Zustand, Redux) | ❌ NO | ✅ YES |
 ```
 
-**11. Percentages: Context or None**
+### 11. Percentages: Context or None
 
 Don't use percentages without adjustment guidance.
 
@@ -167,7 +231,7 @@ Don't use percentages without adjustment guidance.
 ✅ BEST: "Write as many fast tests as possible. Red flag: More E2E than integration = too slow."
 ```
 
-**12. Specificity in Questions**
+### 12. Specificity in Questions
 
 Use precise technical terms, not general descriptions.
 
@@ -178,7 +242,7 @@ Use precise technical terms, not general descriptions.
 Note: React Testing Library does NOT require a browser - that's integration testing.
 ```
 
-**13. Re-evaluation Paths**
+### 13. Re-evaluation Paths
 
 When LLMs hit dead ends, provide concrete next steps.
 
@@ -195,13 +259,17 @@ When LLMs hit dead ends, provide concrete next steps.
    - Login form → Dashboard → E2E test (multi-page)"
 ```
 
-## Anti-Patterns to Avoid
+---
+
+## Anti-Patterns
 
 ❌ **Visual metaphors** - Pyramids, icebergs—LLMs don't process visual information well
 ❌ **Undefined jargon** - "Technical debt", "code smell" need definitions
 ❌ **Competing guidance** - Multiple decision frameworks that contradict each other
 ❌ **Outdated references** - Remove concepts, but forget to update all mentions
 
+---
+
 ## Quality Checklist
 
 Before saving/committing LLM-consumable documentation:
@@ -216,11 +284,7 @@ Before saving/committing LLM-consumable documentation:
 - [ ] Complex decisions (3+ branches) have lookup tables
 - [ ] Dead-end paths have re-evaluation steps with examples
 
-## Research-Backed Principles
-
-- **MECE (McKinsey):** Mutually exclusive, collectively exhaustive decision trees for reliable LLM decisions
-- **Prompt ambiguity (2025):** "Ambiguity is one of the most common causes of poor LLM output" (Zero-Shot Decision Tree Construction)
-- **Concrete examples (2025):** Structured approaches with concrete examples consistently improve performance over "act as" or "###" techniques
+---
 
 ## Example: Before and After
 

package/templates/guides/tdd-best-practices.md

@@ -2,7 +2,7 @@
 
 Patterns and examples for user stories and test definitions following TDD best practices.
 
-**LLM Instruction Design:** These templates create documentation that LLMs read and follow. For comprehensive framework on writing clear, actionable LLM-consumable documentation, see `@.safeword/guides/llm-instruction-design.md`.
+**LLM Instruction Design:** These templates create documentation that LLMs read and follow. For comprehensive framework on writing clear, actionable LLM-consumable documentation, see `@.safeword/guides/llm-guide.md`.
 
 ---
 
@@ -64,7 +64,7 @@ Patterns and examples for user stories and test definitions following TDD best p
 - "Create a design doc for [feature]" → Uses design doc template (2-3 pages)
 - "Update the project architecture doc" → Adds to existing ARCHITECTURE.md
 
-**TDD Workflow:** See `@.safeword/guides/testing-methodology.md` for comprehensive RED → GREEN → REFACTOR workflow with latest best practices
+**TDD Workflow:** See `@.safeword/guides/development-workflow.md` for comprehensive RED → GREEN → REFACTOR workflow with latest best practices
 
 ---
 

package/templates/guides/test-definitions-guide.md

@@ -325,7 +325,7 @@ npm run test:e2e -- tests/feature-name.spec.ts --grep "specific test name"
 
 **Important:** Test definitions are instructions that LLMs read and follow. Apply best practices for clarity.
 
-**See:** `@.safeword/guides/llm-instruction-design.md` for comprehensive framework including:
+**See:** `@.safeword/guides/llm-guide.md` for comprehensive framework including:
 
 - MECE decision trees (mutually exclusive, collectively exhaustive)
 - Explicit definitions (never assume LLMs know what you mean)

package/templates/guides/user-story-guide.md

@@ -221,7 +221,7 @@ After filling out story, mentally check:
 
 **Core principle:** User stories are instructions that LLMs read and follow. Apply LLM instruction design best practices.
 
-**See:** `@.safeword/guides/llm-instruction-design.md` for comprehensive framework on writing LLM-consumable documentation.
+**See:** `@.safeword/guides/llm-guide.md` for comprehensive framework on writing LLM-consumable documentation.
 
 **When filling templates:**
 

package/templates/guides/zombie-process-cleanup.md

@@ -26,7 +26,7 @@ When running dev servers and E2E tests across multiple projects, zombie processe
 - **Dev port**: Project's configured port (e.g., 3000, 5173, 8080) - manual testing
 - **Test port**: Dev port + 1000 (e.g., 4000, 6173, 9080) - Playwright managed
 
-See `testing-methodology.md` → "E2E Testing with Persistent Dev Servers" for full port isolation strategy.
+See `development-workflow.md` → "E2E Testing with Persistent Dev Servers" for full port isolation strategy.
 
 **Decision rule:** If unsure which cleanup method to use → port-based first (safest), then project script, then tmux.
 

package/dist/check-PECCGHEA.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/commands/check.ts"],"sourcesContent":["/**\n * Check command - Verify project health and configuration\n */\n\nimport { join } from 'node:path';\nimport { VERSION } from '../version.js';\nimport { exists, readFile, readFileSafe } from '../utils/fs.js';\nimport { info, success, warn, header, keyValue } from '../utils/output.js';\nimport { isNewerVersion } from '../utils/version.js';\n\nexport interface CheckOptions {\n  offline?: boolean;\n}\n\ninterface HealthStatus {\n  configured: boolean;\n  projectVersion: string | null;\n  cliVersion: string;\n  updateAvailable: boolean;\n  latestVersion: string | null;\n  issues: string[];\n}\n\n/**\n * Check for latest version from npm (with timeout)\n */\nasync function checkLatestVersion(timeout = 3000): Promise<string | null> {\n  try {\n    const controller = new AbortController();\n    const timeoutId = setTimeout(() => controller.abort(), timeout);\n\n    const response = await fetch('https://registry.npmjs.org/safeword/latest', {\n      signal: controller.signal,\n    });\n\n    clearTimeout(timeoutId);\n\n    if (!response.ok) return null;\n\n    const data = (await response.json()) as { version?: string };\n    return data.version ?? null;\n  } catch {\n    return null;\n  }\n}\n\n/**\n * Check project configuration health\n */\nfunction checkHealth(cwd: string): HealthStatus {\n  const safewordDir = join(cwd, '.safeword');\n  const issues: string[] = [];\n\n  // Check if configured\n  if (!exists(safewordDir)) {\n    return {\n      configured: false,\n      projectVersion: null,\n      cliVersion: VERSION,\n      updateAvailable: false,\n      latestVersion: null,\n      issues: [],\n    };\n  }\n\n  // Read project version\n  const versionPath = join(safewordDir, 'version');\n  const projectVersion = readFileSafe(versionPath)?.trim() ?? null;\n\n  // Check for required files\n  const requiredFiles = ['SAFEWORD.md', 'version', 'hooks/session-verify-agents.sh'];\n\n  for (const file of requiredFiles) {\n    if (!exists(join(safewordDir, file))) {\n      issues.push(`Missing: .safeword/${file}`);\n    }\n  }\n\n  // Check AGENTS.md link\n  const agentsMdPath = join(cwd, 'AGENTS.md');\n  if (exists(agentsMdPath)) {\n    const content = readFile(agentsMdPath);\n    if (!content.includes('@./.safeword/SAFEWORD.md')) {\n      issues.push('AGENTS.md missing safeword link');\n    }\n  } else {\n    issues.push('AGENTS.md file missing');\n  }\n\n  // Check .claude/settings.json\n  const settingsPath = join(cwd, '.claude', 'settings.json');\n  if (!exists(settingsPath)) {\n    issues.push('Missing: .claude/settings.json');\n  }\n\n  return {\n    configured: true,\n    projectVersion,\n    cliVersion: VERSION,\n    updateAvailable: false,\n    latestVersion: null,\n    issues,\n  };\n}\n\nexport async function check(options: CheckOptions): Promise<void> {\n  const cwd = process.cwd();\n\n  header('Safeword Health Check');\n\n  const health = checkHealth(cwd);\n\n  // Not configured\n  if (!health.configured) {\n    info('Not configured. Run `safeword setup` to initialize.');\n    return;\n  }\n\n  // Show versions\n  keyValue('Safeword CLI', `v${health.cliVersion}`);\n  keyValue('Project config', health.projectVersion ? `v${health.projectVersion}` : 'unknown');\n\n  // Check for updates (unless offline)\n  if (!options.offline) {\n    info('\\nChecking for updates...');\n    const latestVersion = await checkLatestVersion();\n\n    if (latestVersion) {\n      health.latestVersion = latestVersion;\n      health.updateAvailable = isNewerVersion(health.cliVersion, latestVersion);\n\n      if (health.updateAvailable) {\n        warn(`Update available: v${latestVersion}`);\n        info('Run `npm install -g safeword` to upgrade');\n      } else {\n        success('CLI is up to date');\n      }\n    } else {\n      warn(\"Couldn't check for updates (offline?)\");\n    }\n  } else {\n    info('\\nSkipped update check (offline mode)');\n  }\n\n  // Check project version vs CLI version\n  if (health.projectVersion && isNewerVersion(health.cliVersion, health.projectVersion)) {\n    warn(`Project config (v${health.projectVersion}) is newer than CLI (v${health.cliVersion})`);\n    info('Consider upgrading the CLI');\n  } else if (health.projectVersion && isNewerVersion(health.projectVersion, health.cliVersion)) {\n    info(`\\nUpgrade available for project config`);\n    info(\n      `Run \\`safeword upgrade\\` to update from v${health.projectVersion} to v${health.cliVersion}`,\n    );\n  }\n\n  // Show issues\n  if (health.issues.length > 0) {\n    header('Issues Found');\n    for (const issue of health.issues) {\n      warn(issue);\n    }\n    info('\\nRun `safeword upgrade` to repair configuration');\n  } else {\n    success('\\nConfiguration is healthy');\n  }\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AAIA,SAAS,YAAY;AAsBrB,eAAe,mBAAmB,UAAU,KAA8B;AACxE,MAAI;AACF,UAAM,aAAa,IAAI,gBAAgB;AACvC,UAAM,YAAY,WAAW,MAAM,WAAW,MAAM,GAAG,OAAO;AAE9D,UAAM,WAAW,MAAM,MAAM,8CAA8C;AAAA,MACzE,QAAQ,WAAW;AAAA,IACrB,CAAC;AAED,iBAAa,SAAS;AAEtB,QAAI,CAAC,SAAS,GAAI,QAAO;AAEzB,UAAM,OAAQ,MAAM,SAAS,KAAK;AAClC,WAAO,KAAK,WAAW;AAAA,EACzB,QAAQ;AACN,WAAO;AAAA,EACT;AACF;AAKA,SAAS,YAAY,KAA2B;AAC9C,QAAM,cAAc,KAAK,KAAK,WAAW;AACzC,QAAM,SAAmB,CAAC;AAG1B,MAAI,CAAC,OAAO,WAAW,GAAG;AACxB,WAAO;AAAA,MACL,YAAY;AAAA,MACZ,gBAAgB;AAAA,MAChB,YAAY;AAAA,MACZ,iBAAiB;AAAA,MACjB,eAAe;AAAA,MACf,QAAQ,CAAC;AAAA,IACX;AAAA,EACF;AAGA,QAAM,cAAc,KAAK,aAAa,SAAS;AAC/C,QAAM,iBAAiB,aAAa,WAAW,GAAG,KAAK,KAAK;AAG5D,QAAM,gBAAgB,CAAC,eAAe,WAAW,gCAAgC;AAEjF,aAAW,QAAQ,eAAe;AAChC,QAAI,CAAC,OAAO,KAAK,aAAa,IAAI,CAAC,GAAG;AACpC,aAAO,KAAK,sBAAsB,IAAI,EAAE;AAAA,IAC1C;AAAA,EACF;AAGA,QAAM,eAAe,KAAK,KAAK,WAAW;AAC1C,MAAI,OAAO,YAAY,GAAG;AACxB,UAAM,UAAU,SAAS,YAAY;AACrC,QAAI,CAAC,QAAQ,SAAS,0BAA0B,GAAG;AACjD,aAAO,KAAK,iCAAiC;AAAA,IAC/C;AAAA,EACF,OAAO;AACL,WAAO,KAAK,wBAAwB;AAAA,EACtC;AAGA,QAAM,eAAe,KAAK,KAAK,WAAW,eAAe;AACzD,MAAI,CAAC,OAAO,YAAY,GAAG;AACzB,WAAO,KAAK,gCAAgC;AAAA,EAC9C;AAEA,SAAO;AAAA,IACL,YAAY;AAAA,IACZ;AAAA,IACA,YAAY;AAAA,IACZ,iBAAiB;AAAA,IACjB,eAAe;AAAA,IACf;AAAA,EACF;AACF;AAEA,eAAsB,MAAM,SAAsC;AAChE,QAAM,MAAM,QAAQ,IAAI;AAExB,SAAO,uBAAuB;AAE9B,QAAM,SAAS,YAAY,GAAG;AAG9B,MAAI,CAAC,OAAO,YAAY;AACtB,SAAK,qDAAqD;AAC1D;AAAA,EACF;AAGA,WAAS,gBAAgB,IAAI,OAAO,UAAU,EAAE;AAChD,WAAS,kBAAkB,OAAO,iBAAiB,IAAI,OAAO,cAAc,KAAK,SAAS;AAG1F,MAAI,CAAC,QAAQ,SAAS;AACpB,SAAK,2BAA2B;AAChC,UAAM,gBAAgB,MAAM,mBAAmB;AAE/C,QAAI,eAAe;AACjB,aAAO,gBAAgB;AACvB,aAAO,kBAAkB,eAAe,OAAO,YAAY,aAAa;AAExE,UAAI,OAAO,iBAAiB;AAC1B,aAAK,sBAAsB,aAAa,EAAE;AAC1C,aAAK,0CAA0C;AAAA,MACjD,OAAO;AACL,gBAAQ,mBAAmB;AAAA,MAC7B;AAAA,IACF,OAAO;AACL,WAAK,uCAAuC;AAAA,IAC9C;AAAA,EACF,OAAO;AACL,SAAK,uCAAuC;AAAA,EAC9C;AAGA,MAAI,OAAO,kBAAkB,eAAe,OAAO,YAAY,OAAO,cAAc,GAAG;AACrF,SAAK,oBAAoB,OAAO,cAAc,yBAAyB,OAAO,UAAU,GAAG;AAC3F,SAAK,4BAA4B;AAAA,EACnC,WAAW,OAAO,kBAAkB,eAAe,OAAO,gBAAgB,OAAO,UAAU,GAAG;AAC5F,SAAK;AAAA,qCAAwC;AAC7C;AAAA,MACE,4CAA4C,OAAO,cAAc,QAAQ,OAAO,UAAU;AAAA,IAC5F;AAAA,EACF;AAGA,MAAI,OAAO,OAAO,SAAS,GAAG;AAC5B,WAAO,cAAc;AACrB,eAAW,SAAS,OAAO,QAAQ;AACjC,WAAK,KAAK;AAAA,IACZ;AACA,SAAK,kDAAkD;AAAA,EACzD,OAAO;AACL,YAAQ,4BAA4B;AAAA,EACtC;AACF;","names":[]}

package/dist/chunk-6CVTH67L.js

@@ -1,43 +0,0 @@
-// src/utils/project-detector.ts
-function detectProjectType(packageJson) {
-  const deps = packageJson.dependencies || {};
-  const devDeps = packageJson.devDependencies || {};
-  const allDeps = { ...deps, ...devDeps };
-  const hasTypescript = "typescript" in allDeps;
-  const hasReact = "react" in deps || "react" in devDeps;
-  const hasNextJs = "next" in deps;
-  const hasAstro = "astro" in deps || "astro" in devDeps;
-  const hasVue = "vue" in deps || "vue" in devDeps;
-  const hasNuxt = "nuxt" in deps;
-  const hasSvelte = "svelte" in deps || "svelte" in devDeps;
-  const hasSvelteKit = "@sveltejs/kit" in deps || "@sveltejs/kit" in devDeps;
-  const hasElectron = "electron" in deps || "electron" in devDeps;
-  const hasVitest = "vitest" in devDeps;
-  const hasPlaywright = "@playwright/test" in devDeps;
-  const hasTailwind = "tailwindcss" in allDeps;
-  const hasEntryPoints = !!(packageJson.main || packageJson.module || packageJson.exports);
-  const isPublishable = hasEntryPoints && packageJson.private !== true;
-  return {
-    typescript: hasTypescript,
-    react: hasReact || hasNextJs,
-    // Next.js implies React
-    nextjs: hasNextJs,
-    astro: hasAstro,
-    vue: hasVue || hasNuxt,
-    // Nuxt implies Vue
-    nuxt: hasNuxt,
-    svelte: hasSvelte || hasSvelteKit,
-    // SvelteKit implies Svelte
-    sveltekit: hasSvelteKit,
-    electron: hasElectron,
-    vitest: hasVitest,
-    playwright: hasPlaywright,
-    tailwind: hasTailwind,
-    publishableLibrary: isPublishable
-  };
-}
-
-export {
-  detectProjectType
-};
-//# sourceMappingURL=chunk-6CVTH67L.js.map

package/dist/chunk-6CVTH67L.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/utils/project-detector.ts"],"sourcesContent":["/**\n * Project type detection from package.json\n *\n * Detects frameworks and tools used in the project to configure\n * appropriate linting rules.\n */\n\nexport interface PackageJson {\n  name?: string;\n  version?: string;\n  private?: boolean;\n  main?: string;\n  module?: string;\n  exports?: unknown;\n  types?: string;\n  dependencies?: Record<string, string>;\n  devDependencies?: Record<string, string>;\n}\n\nexport interface ProjectType {\n  typescript: boolean;\n  react: boolean;\n  nextjs: boolean;\n  astro: boolean;\n  vue: boolean;\n  nuxt: boolean;\n  svelte: boolean;\n  sveltekit: boolean;\n  electron: boolean;\n  vitest: boolean;\n  playwright: boolean;\n  tailwind: boolean;\n  publishableLibrary: boolean;\n}\n\n/**\n * Detects project type from package.json contents\n */\nexport function detectProjectType(packageJson: PackageJson): ProjectType {\n  const deps = packageJson.dependencies || {};\n  const devDeps = packageJson.devDependencies || {};\n  const allDeps = { ...deps, ...devDeps };\n\n  const hasTypescript = 'typescript' in allDeps;\n  const hasReact = 'react' in deps || 'react' in devDeps;\n  const hasNextJs = 'next' in deps;\n  const hasAstro = 'astro' in deps || 'astro' in devDeps;\n  const hasVue = 'vue' in deps || 'vue' in devDeps;\n  const hasNuxt = 'nuxt' in deps;\n  const hasSvelte = 'svelte' in deps || 'svelte' in devDeps;\n  const hasSvelteKit = '@sveltejs/kit' in deps || '@sveltejs/kit' in devDeps;\n  const hasElectron = 'electron' in deps || 'electron' in devDeps;\n  const hasVitest = 'vitest' in devDeps;\n  const hasPlaywright = '@playwright/test' in devDeps;\n  const hasTailwind = 'tailwindcss' in allDeps;\n\n  // Publishable library: has entry points and is not marked private\n  const hasEntryPoints = !!(packageJson.main || packageJson.module || packageJson.exports);\n  const isPublishable = hasEntryPoints && packageJson.private !== true;\n\n  return {\n    typescript: hasTypescript,\n    react: hasReact || hasNextJs, // Next.js implies React\n    nextjs: hasNextJs,\n    astro: hasAstro,\n    vue: hasVue || hasNuxt, // Nuxt implies Vue\n    nuxt: hasNuxt,\n    svelte: hasSvelte || hasSvelteKit, // SvelteKit implies Svelte\n    sveltekit: hasSvelteKit,\n    electron: hasElectron,\n    vitest: hasVitest,\n    playwright: hasPlaywright,\n    tailwind: hasTailwind,\n    publishableLibrary: isPublishable,\n  };\n}\n"],"mappings":";AAsCO,SAAS,kBAAkB,aAAuC;AACvE,QAAM,OAAO,YAAY,gBAAgB,CAAC;AAC1C,QAAM,UAAU,YAAY,mBAAmB,CAAC;AAChD,QAAM,UAAU,EAAE,GAAG,MAAM,GAAG,QAAQ;AAEtC,QAAM,gBAAgB,gBAAgB;AACtC,QAAM,WAAW,WAAW,QAAQ,WAAW;AAC/C,QAAM,YAAY,UAAU;AAC5B,QAAM,WAAW,WAAW,QAAQ,WAAW;AAC/C,QAAM,SAAS,SAAS,QAAQ,SAAS;AACzC,QAAM,UAAU,UAAU;AAC1B,QAAM,YAAY,YAAY,QAAQ,YAAY;AAClD,QAAM,eAAe,mBAAmB,QAAQ,mBAAmB;AACnE,QAAM,cAAc,cAAc,QAAQ,cAAc;AACxD,QAAM,YAAY,YAAY;AAC9B,QAAM,gBAAgB,sBAAsB;AAC5C,QAAM,cAAc,iBAAiB;AAGrC,QAAM,iBAAiB,CAAC,EAAE,YAAY,QAAQ,YAAY,UAAU,YAAY;AAChF,QAAM,gBAAgB,kBAAkB,YAAY,YAAY;AAEhE,SAAO;AAAA,IACL,YAAY;AAAA,IACZ,OAAO,YAAY;AAAA;AAAA,IACnB,QAAQ;AAAA,IACR,OAAO;AAAA,IACP,KAAK,UAAU;AAAA;AAAA,IACf,MAAM;AAAA,IACN,QAAQ,aAAa;AAAA;AAAA,IACrB,WAAW;AAAA,IACX,UAAU;AAAA,IACV,QAAQ;AAAA,IACR,YAAY;AAAA,IACZ,UAAU;AAAA,IACV,oBAAoB;AAAA,EACtB;AACF;","names":[]}

package/dist/chunk-75FKNZUM.js

@@ -1,15 +0,0 @@
-import {
-  exists
-} from "./chunk-ARIAOK2F.js";
-
-// src/utils/git.ts
-import { execSync } from "child_process";
-import { join } from "path";
-function isGitRepo(cwd) {
-  return exists(join(cwd, ".git"));
-}
-
-export {
-  isGitRepo
-};
-//# sourceMappingURL=chunk-75FKNZUM.js.map

package/dist/chunk-75FKNZUM.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/utils/git.ts"],"sourcesContent":["/**\n * Git utilities for CLI operations\n */\n\nimport { execSync } from 'node:child_process';\nimport { join } from 'node:path';\nimport { exists, readFile, writeFile, ensureDir, makeExecutable } from './fs.js';\n\nconst MARKER_START = '# SAFEWORD_ARCH_CHECK_START';\nconst MARKER_END = '# SAFEWORD_ARCH_CHECK_END';\n\n/**\n * Check if directory is a git repository\n */\nexport function isGitRepo(cwd: string): boolean {\n  return exists(join(cwd, '.git'));\n}\n\n/**\n * Initialize a git repository\n */\nexport function initGitRepo(cwd: string): void {\n  execSync('git init', { cwd, stdio: 'pipe' });\n}\n\n/**\n * Get the pre-commit hook content to add\n */\nfunction getHookContent(): string {\n  return `\n${MARKER_START}\n# Safeword pre-commit linting\n# This section is managed by safeword - do not edit manually\nif [ -f \".safeword/hooks/git-pre-commit.sh\" ]; then\n  bash .safeword/hooks/git-pre-commit.sh\nfi\n${MARKER_END}\n`;\n}\n\n/**\n * Install safeword markers into pre-commit hook\n */\nexport function installGitHook(cwd: string): void {\n  const hooksDir = join(cwd, '.git', 'hooks');\n  const hookPath = join(hooksDir, 'pre-commit');\n\n  ensureDir(hooksDir);\n\n  let content = '';\n\n  if (exists(hookPath)) {\n    content = readFile(hookPath);\n\n    // Check if already has safeword markers\n    if (content.includes(MARKER_START)) {\n      // Remove existing safeword section and re-add (update)\n      content = removeMarkerSection(content);\n    }\n  } else {\n    // Create new hook file with shebang\n    content = '#!/bin/bash\\n';\n  }\n\n  // Add safeword section\n  content = content.trimEnd() + '\\n' + getHookContent();\n\n  writeFile(hookPath, content);\n  makeExecutable(hookPath);\n}\n\n/**\n * Remove safeword markers from pre-commit hook\n */\nexport function removeGitHook(cwd: string): void {\n  const hookPath = join(cwd, '.git', 'hooks', 'pre-commit');\n\n  if (!exists(hookPath)) return;\n\n  let content = readFile(hookPath);\n\n  if (!content.includes(MARKER_START)) return;\n\n  content = removeMarkerSection(content);\n\n  // If only shebang remains, we could delete the file\n  // but safer to leave it\n  writeFile(hookPath, content);\n}\n\n/**\n * Remove the section between markers (inclusive)\n */\nfunction removeMarkerSection(content: string): string {\n  const lines = content.split('\\n');\n  const result: string[] = [];\n  let inMarkerSection = false;\n\n  for (const line of lines) {\n    if (line.includes(MARKER_START)) {\n      inMarkerSection = true;\n      continue;\n    }\n    if (line.includes(MARKER_END)) {\n      inMarkerSection = false;\n      continue;\n    }\n    if (!inMarkerSection) {\n      result.push(line);\n    }\n  }\n\n  return result.join('\\n').trim() + '\\n';\n}\n\n/**\n * Check if git hooks have safeword markers\n */\nexport function hasGitHook(cwd: string): boolean {\n  const hookPath = join(cwd, '.git', 'hooks', 'pre-commit');\n  if (!exists(hookPath)) return false;\n  const content = readFile(hookPath);\n  return content.includes(MARKER_START);\n}\n"],"mappings":";;;;;AAIA,SAAS,gBAAgB;AACzB,SAAS,YAAY;AASd,SAAS,UAAU,KAAsB;AAC9C,SAAO,OAAO,KAAK,KAAK,MAAM,CAAC;AACjC;","names":[]}