@chamba/claude-extras 0.6.1 → 0.6.2

package/README.md

@@ -20,8 +20,8 @@ Check the MCP server's version the same way: `npx @chamba/mcp --version`.
 
 It installs into `~/.claude/`:
 
-- **Slash commands**: `/orq`, `/workspace`, `/worktrees`, `/recall`
-- **Subagents**: `implementer`, `reviewer`, `tester`
+- **Slash commands**: `/ticket`, `/workspace`, `/map`, `/worktrees`, `/orq`, `/recall`, `/vault`
+- **Subagents**: `planner`, `implementer`, `reviewer`, `tester`
 - **Hooks**: warn on destructive commands, validate worktree edits
 
 …and registers the `chamba` MCP server in `~/.claude.json`. It never overwrites your
@@ -184,6 +184,24 @@ model + effort you configured above.
 > `worktrees.root` (e.g. `WORKTREES/`) to `.gitignore` so they're never committed. It's
 > off by default.
 
+## Bootstrap the architecture map with `/map`
+
+What makes `/ticket` precise is a vault that already describes how your repos fit
+together. On a small or new project, seed that in one shot:
+
+```
+/map          # asks EN/ES, then maps every repo
+/map es web   # Spanish notes, scoped to the `web` repo
+```
+
+`/map` resolves the vault (`chamba_vault_status` — run `/workspace init` first if you
+don't have one), asks which language to write in, reads the repos for their cross-repo
+wiring (REST, async/events, shared data, build deps), and writes **living notes** with
+stable names: `Topology.md`, `Data flows.md`, `Domain entities.md`, and `repos/<repo>.md`.
+Re-run it as the project grows — it updates its own notes in place and **never touches a
+note you edited by hand** (it only rewrites notes marked `source: chamba`). It's opt-in;
+on a big monorepo, mapping everything is expensive.
+
 ## License
 
 MIT

package/assets/commands/map.md

@@ -0,0 +1,41 @@
+---
+description: Map the workspace architecture (cross-repo wiring) into living vault notes
+argument-hint: "[en|es] [repo ...]"
+---
+
+You are mapping the architecture of this workspace into the Obsidian vault: **$ARGUMENTS**
+
+This is an opt-in command for small or new projects — bootstrap the cross-repo
+context the `/ticket` flow relies on. Stay grounded in the real code: cite the
+files you read, never invent a connection, and mark anything you can't confirm as
+unknown rather than guessing.
+
+Parse the arguments: a leading `en` or `es` sets the notes' language; any other
+tokens are repos to scope the map to (default: every repo in the workspace).
+
+1. Resolve the vault with `chamba_vault_status`. If no vault is found, tell me to
+   run `/workspace init` first (it bootstraps one) and stop here.
+2. **Language.** If I didn't pass `en`/`es`, ask me whether to write the notes in
+   English or Spanish, and wait for my answer. Write ALL notes in that language.
+3. Call `chamba_load_context` with "map the workspace architecture" to pull the
+   repo map, coding rules, and any notes already in the vault.
+4. Do cross-repo reconnaissance, grounded in real code (read the relevant files):
+   - **REST/HTTP** — clients, base URLs, route handlers → who calls whom.
+   - **Async** — pub/sub topics, queues, events, webhooks → producers and consumers.
+   - **Shared data** — databases, schemas, entities crossing repos.
+   - **Build/deploy** — workspace dependencies, shared packages.
+5. Write **stable, named notes** into the vault root (use your file tools to write
+   directly under the resolved vault path). Each note gets YAML frontmatter with
+   `tags: [chamba, architecture]`, `source: chamba`, and the date:
+   - `Topology.md` — the service graph: which repos talk over REST and which events
+     connect them. A diagram (Mermaid) plus prose.
+   - `Data flows.md` — the key end-to-end flows across repos.
+   - `Domain entities.md` — the shared entities / domain model.
+   - `repos/<repo>.md` — one overview per repo: purpose, stack, entry points, and
+     what it talks to (in and out).
+6. **Never clobber my edits.** Before writing a note that already exists, read it:
+   if it does NOT carry `source: chamba` in its frontmatter, I edited it by hand —
+   leave it untouched, report it as skipped, and move on. If it does, regenerate it
+   in place. The `source: chamba` marker is how you know which notes are yours.
+7. Report what you wrote, updated and skipped, with the vault paths. Do NOT commit,
+   merge or push — these are notes, I'll review them.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chamba/claude-extras",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "description": "Optional Claude Code extras for chamba: slash commands, subagents and hooks installer",
   "license": "MIT",
   "type": "module",
@@ -31,8 +31,8 @@
   ],
   "dependencies": {
     "@inquirer/prompts": "^7.0.0",
-    "@chamba/adapters": "0.6.1",
-    "@chamba/core": "0.6.1"
+    "@chamba/adapters": "0.6.2",
+    "@chamba/core": "0.6.2"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",