thevoidforge-methodology 23.5.1 → 23.5.2

package/.claude/commands/void.md

@@ -6,6 +6,16 @@
 1. Read `/docs/methods/FORGE_KEEPER.md`
 2. Read `VERSION.md` (~30 lines — current version + history)
 
+## CRITICAL: Write Target Safety
+
+**NEVER write methodology files to `~/.claude/`.** All files MUST go to the PROJECT root (where `.voidforge` marker or `.git` exists). Writing to `~/.claude/commands/` or `~/.claude/agents/` creates user-level duplicates that appear alongside project-level commands in every project — Claude Code shows both "(user)" and "(project)" copies.
+
+**Detect and fix duplicates (auto-cleanup):** Before any sync, check if `~/.claude/commands/` or `~/.claude/agents/` contain VoidForge methodology files. If they do:
+1. Run `ls ~/.claude/commands/ 2>/dev/null | head -3` and `ls ~/.claude/agents/ 2>/dev/null | head -3`
+2. If VoidForge commands exist there (assess.md, build.md, qa.md, etc.), warn: "Found VoidForge commands in ~/.claude/ (user-level). These cause duplicate commands in Claude Code. Removing..."
+3. Run `rm -rf ~/.claude/commands/ ~/.claude/agents/` to clean them
+4. Confirm: "User-level duplicates removed. Project-level commands will be used."
+
 ## Step 0 — Tune the Forge (Bombadil)
 Orient to the current state:
 1. Read `VERSION.md` — identify the current VoidForge version

package/CHANGELOG.md

@@ -6,6 +6,14 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/), and this
 
 ---
 
+## [23.5.2] - 2026-04-12
+
+### Fixed
+- **Duplicate commands in Claude Code** — `/void` now auto-detects and removes VoidForge files from `~/.claude/commands/` and `~/.claude/agents/` (user-level). Guard added to prevent future writes to `~/.claude/`. Both void.md and FORGE_KEEPER.md updated.
+- **Git init stack trace** — project creation via wizard showed full Error stack trace when git identity wasn't configured. Now shows clean one-line message.
+
+---
+
 ## [23.5.1] - 2026-04-12
 
 ### Fixed

package/VERSION.md

@@ -1,6 +1,6 @@
 # Version
 
-**Current:** 23.5.1
+**Current:** 23.5.2
 
 ## Versioning Scheme
 
@@ -14,6 +14,7 @@ This project uses [Semantic Versioning](https://semver.org/):
 
 | Version | Date | Summary |
 |---------|------|---------|
+| 23.5.2 | 2026-04-12 | /void auto-cleanup ~/.claude/ duplicates + git init stack trace fix |
 | 23.5.1 | 2026-04-12 | Fix CLI self-upgrade: wrong package name (voidforge → thevoidforge) + stale npx cache on re-exec |
 | 23.5.0 | 2026-04-12 | The Herald — intelligent agent dispatch: Haiku pre-scan, agent registry, 40 tags, --focus flag, 14 commands wired. ADR-047. Campaign 37. |
 | 23.4.1 | 2026-04-12 | Gauntlet security fix — XSS escaping in blueprint banner, ROADMAP staleness, lobby a11y |

package/docs/methods/FORGE_KEEPER.md

@@ -46,6 +46,7 @@ Keep your VoidForge installation current without breaking your project. Every up
 7. **Log what changed.** After updating, write a brief entry to `/logs/` noting what was synced and from what version.
 8. **Keep the mood light.** Bombadil sings. Updates are good news, not chores.
 9. **Batch sync when multiple versions behind.** Compare directly to the latest upstream version — don't step through each intermediate version. Sync to the latest in one pass and batch all content handoffs together. (Field report #35)
+10. **NEVER write to `~/.claude/`.** All methodology files go to the PROJECT root (where `.voidforge` or `.git` exists). Writing to `~/.claude/commands/` or `~/.claude/agents/` creates user-level duplicates that appear alongside project-level commands in Claude Code. Before any sync, check if `~/.claude/commands/` or `~/.claude/agents/` contain VoidForge files — if so, remove them automatically and warn the user.
 
 ## Shared Methodology Files
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "thevoidforge-methodology",
-  "version": "23.5.1",
+  "version": "23.5.2",
   "description": "VoidForge methodology — agents, commands, methods, patterns.",
   "license": "MIT",
   "files": [