@cr8rcho/alkahest 0.1.74 → 0.1.76

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cr8rcho/alkahest",
-  "version": "0.1.74",
+  "version": "0.1.76",
   "publishConfig": {
     "access": "public"
   },

package/presets/as-built/CLAUDE-snippet.md

@@ -3,15 +3,15 @@
 
 This repo keeps **as-built documentation** under `docs/` (four layers: system / components /
 features / modules — see docs/README.md) and **ADRs** under `docs/decisions/`. The writing
-instructions live in the account skills `as-built-docs` and `adr` — read them via the
+instructions live in the account skills `alkahest/as-built-docs` and `alkahest/adr` — read them via the
 alkahest MCP `skills` tool before writing docs.
 
 1. **After finishing any code change, update the affected docs in the same session.**
-   The layer mapping and the update checklist are in the `as-built-docs` skill. Write an
+   The layer mapping and the update checklist are in the `alkahest/as-built-docs` skill. Write an
    ADR only for decisions whose "why" a code diff cannot reconstruct (criteria and the
-   template are in the `adr` skill).
+   template are in the `alkahest/adr` skill).
 2. **First documentation pass (repo has no docs yet)?** Follow the bootstrap protocol in
-   the `as-built-docs` skill: one system map + 2–3 core modules + ADR-001 (architecture
+   the `alkahest/as-built-docs` skill: one system map + 2–3 core modules + ADR-001 (architecture
    snapshot) — small first, then mirror and hand the user the note-map link. Grow the rest
    incrementally with later work.
 3. **After changing `docs/`, mirror it to the hosted note maps** by running

package/presets/as-built/preset.json

@@ -3,8 +3,8 @@
   "name": "as-built docs",
   "description": "Living as-built documentation + an ADR log, written by your agent and mirrored to note maps.",
   "skills": [
-    { "name": "as-built-docs", "file": "skills/as-built-docs.md" },
-    { "name": "adr", "file": "skills/adr.md" }
+    { "name": "alkahest/as-built-docs", "file": "skills/as-built-docs.md" },
+    { "name": "alkahest/adr", "file": "skills/adr.md" }
   ],
   "scaffold": "scaffold",
   "snippet": "CLAUDE-snippet.md",

package/presets/as-built/scaffold/docs/README.md

@@ -2,7 +2,7 @@
 
 This directory holds this repository's **as-built documentation** — documents that record
 how the system is actually built (never plans or PRDs). Writing instructions live in the
-`as-built-docs` account skill (read it via the alkahest MCP `skills` tool).
+`alkahest/as-built-docs` account skill (read it via the alkahest MCP `skills` tool).
 
 ## Layers
 

package/presets/as-built/scaffold/docs/decisions/README.md

@@ -2,7 +2,7 @@
 
 This folder collects **Architecture Decision Records** — the why / alternatives /
 trade-offs of decisions, frozen at decision time. Writing instructions and the template
-live in the `adr` account skill (read it via the alkahest MCP `skills` tool).
+live in the `alkahest/adr` account skill (read it via the alkahest MCP `skills` tool).
 
 Quick rules:
 
@@ -10,3 +10,15 @@ Quick rules:
 - Append-only: a changed decision gets a NEW ADR with `Supersedes:`; the old one keeps its
   body and gets `Status: Superseded by …`.
 - Start the practice with **ADR-001 — architecture snapshot** of the current code.
+
+## Tag vocabulary
+
+Every ADR opens with `tags:` frontmatter, and **this table is the vocabulary** — pick from
+it; extend it deliberately (add the row in the same commit as the ADR that needs it). On the
+hosted `adr` note map each tag becomes a hub node, so the vocabulary's shape IS the map's
+shape: one **surface** tag per ADR (the product/code area it touches) plus at most two
+**arc** tags (a storyline several ADRs share), and keep each tag attached to roughly 3–12
+ADRs. The first documentation pass seeds the surface rows from the codebase's actual areas.
+
+| Tag | Kind | Meaning |
+|---|---|---|

package/presets/as-built/skills/adr.md

@@ -1,4 +1,4 @@
-# adr — decision records
+# alkahest/adr — decision records
 
 ADRs (`docs/decisions/NNN-kebab-title.md`) record the **why** of decisions: context,
 alternatives, trade-offs. They are a separate axis from as-built docs — as-built documents
@@ -38,6 +38,13 @@ one **surface** tag (the area of the product it touches) plus at most two **arc*
 node — keep every tag attached to roughly 3–12 ADRs so the map stays legible, and prefer
 reusing an existing tag over inventing a new one.
 
+**The vocabulary lives in `docs/decisions/README.md`'s tag table, and the repo owns it.**
+On the bootstrap pass, seed it: derive 3–7 surface tags from the codebase's *actual* areas
+(the folders/verticals you just documented), record them in the table, and tag ADR-001 from
+that set. Afterwards, every ADR picks from the table; a genuinely new tag means adding its
+row in the same commit. Arc tags are not invented up front — they emerge when several ADRs
+turn out to share a storyline.
+
 ## Template
 
 ```markdown

package/presets/as-built/skills/as-built-docs.md

@@ -1,4 +1,4 @@
-# as-built-docs — writing instructions
+# alkahest/as-built-docs — writing instructions
 
 You are maintaining this repository's **as-built documentation**: documents that record how
 the system **is actually built**. Never plans, PRDs, or aspirations — present tense, code as
@@ -25,7 +25,7 @@ summary + link in the other.
 Title each document with a **classed H1**: `# System — <name>`, `# Component — <name>`,
 `# Feature — <name>`, `# Module — <name>`. The note-map mirror strips the class prefix,
 so the hosted note is titled just `<name>` while the file stays unambiguous in the repo.
-(ADRs have their own H1 shape — see the `adr` skill.)
+(ADRs have their own H1 shape — see the `alkahest/adr` skill.)
 
 ## Bootstrap — when the repo has no docs yet
 
@@ -35,7 +35,7 @@ the user sees a map fast:
 1. `docs/system/<app>.md` — one system map: layers, data flow, key dependencies, honest
    Known Limitations.
 2. Two or three `docs/modules/*.md` for the load-bearing modules only.
-3. One decision record (see the `adr` skill): **ADR-001, an architecture snapshot** — the
+3. One decision record (see the `alkahest/adr` skill): **ADR-001, an architecture snapshot** — the
    decisions already embedded in the current code.
 4. Add each document to the index in `docs/README.md`, then **mirror to the note maps and
    hand the user the map link** (the mirroring rule lives in this repo's CLAUDE.md).
@@ -52,7 +52,7 @@ code changes touch.
 - **As-built, present tense** — "this is how it is built." Cite real file paths, function
   names, and constants so readers can jump straight to code.
 - **Decision history is a separate axis** — why / alternatives / trade-offs belong in ADRs
-  (`docs/decisions/`, see the `adr` skill), not in these documents.
+  (`docs/decisions/`, see the `alkahest/adr` skill), not in these documents.
 - **Known Limitations, honestly** — the most valuable section of a post-hoc document.
   Remove limitations you fixed; add the ones you introduced.
 - **Overwrite freely** — these documents always describe the present. (ADRs are the

package/presets/index.json

@@ -4,7 +4,7 @@
       "id": "as-built",
       "name": "as-built docs",
       "description": "Living as-built documentation + an ADR log, written by your agent and mirrored to note maps.",
-      "skills": ["as-built-docs", "adr"],
+      "skills": ["alkahest/as-built-docs", "alkahest/adr"],
       "maps": ["as-built", "adr"],
       "contents": ["skills", "scaffold", "claude-snippet", "sync-script"]
     }