chapterhouse 0.3.16 → 0.3.17

package/dist/copilot/agents.js

@@ -222,6 +222,8 @@ You are an agent within Chapterhouse, a team-level AI assistant for engineering
 ### Shared Wiki
 All agents share a wiki knowledge base for persistent memory. Use \`wiki_read\` and \`wiki_search\` to find existing knowledge, and \`wiki_update\` to save important findings.
 
+Invoke \`wiki-conventions\` before wiki writes or restructuring work. Treat \`wiki_update\`, \`remember\`, \`forget\`, \`wiki_ingest\`, \`wiki_lint\`, and \`wiki_rebuild_index\` as write-sensitive workflows. Before using them, read \`pages/index.md\`, scan the last 20-30 entries of \`pages/_meta/log.md\`, and run \`wiki_search\` for the topic when the wiki is large or the topic is ambiguous.
+
 ### Communication
 - You receive tasks from @chapterhouse (the orchestrator) or directly from the user
 - Your results are relayed back to the user by @chapterhouse

package/dist/copilot/agents.test.js

@@ -0,0 +1,22 @@
+import assert from "node:assert/strict";
+import test from "node:test";
+import { composeAgentSystemMessage, } from "./agents.js";
+function makeAgent(slug) {
+    return {
+        slug,
+        name: slug,
+        description: `${slug} test agent`,
+        model: "claude-sonnet-4.6",
+        systemMessage: `You are ${slug}.`,
+    };
+}
+test("composeAgentSystemMessage steers wiki-capable agents to wiki-conventions", () => {
+    for (const slug of ["coder", "general-purpose"]) {
+        const message = composeAgentSystemMessage(makeAgent(slug));
+        assert.match(message, /invoke `wiki-conventions` before wiki writes/i);
+        assert.match(message, /wiki_update[\s\S]{0,80}remember[\s\S]{0,80}forget[\s\S]{0,80}wiki_ingest[\s\S]{0,80}wiki_lint[\s\S]{0,80}wiki_rebuild_index/i);
+        assert.match(message, /read `pages\/index\.md`/i);
+        assert.match(message, /scan the last 20-30 entries of `pages\/_meta\/log\.md`/i);
+    }
+});
+//# sourceMappingURL=agents.test.js.map

package/dist/copilot/skills.test.js

@@ -0,0 +1,10 @@
+import assert from "node:assert/strict";
+import test from "node:test";
+import { listSkills } from "./skills.js";
+test("listSkills includes bundled wiki-conventions skill metadata", () => {
+    const skill = listSkills().find((entry) => entry.slug === "wiki-conventions" && entry.source === "bundled");
+    assert.ok(skill);
+    assert.equal(skill.name, "wiki-conventions");
+    assert.match(skill.description, /creating, editing, linting, restructuring, or reviewing Chapterhouse wiki content/i);
+});
+//# sourceMappingURL=skills.test.js.map

package/dist/copilot/system-message.js

@@ -122,6 +122,8 @@ You can delegate **multiple tasks simultaneously**. Different agents can work in
 - With \`remember\`, pass \`entity\` for entity categories (and \`facet\` to target a sub-page). With \`wiki_update\`, give the full canonical path — bad paths are rejected with a suggested correction; just retry with the suggestion.
 - If the structure ever looks wrong, call \`wiki_rebuild_index\` to regenerate the index from disk.
 
+**Wiki writes and restructuring**: Before writing or restructuring wiki content, invoke the \`wiki-conventions\` skill. Treat \`wiki_update\`, \`remember\`, \`forget\`, \`wiki_ingest\`, \`wiki_lint\`, and \`wiki_rebuild_index\` as write-sensitive workflows. Before using them, read \`pages/index.md\`, scan the last 20-30 entries of \`pages/_meta/log.md\`, and run \`wiki_search\` for the topic when the wiki is large or the topic is ambiguous.
+
 **Learning workflow**: When the user asks you to do something you don't have a skill for:
 1. **Search skills.sh first**: Use the find-skills skill to search for existing community skills.
 2. **Present what you found**: Tell the user the skill name, what it does, and its security status.

package/dist/copilot/system-message.test.js

@@ -22,4 +22,15 @@ test("orchestrator prompt omits version banner when version is not provided", ()
     const message = getOrchestratorSystemMessage();
     assert.doesNotMatch(message, /chapterhouse v\d/);
 });
+test("orchestrator prompt requires wiki-conventions before write-sensitive wiki work", () => {
+    const message = getOrchestratorSystemMessage();
+    assert.match(message, /wiki-conventions[\s\S]{0,500}wiki_update[\s\S]{0,200}remember[\s\S]{0,200}forget[\s\S]{0,200}wiki_ingest[\s\S]{0,200}wiki_lint[\s\S]{0,200}wiki_rebuild_index/i);
+    assert.match(message, /before writing or restructuring wiki content/i);
+});
+test("orchestrator prompt describes the wiki orientation ritual", () => {
+    const message = getOrchestratorSystemMessage();
+    assert.match(message, /read `pages\/index\.md`/i);
+    assert.match(message, /scan the last 20-30 entries of `pages\/_meta\/log\.md`/i);
+    assert.match(message, /run `wiki_search` for the topic/i);
+});
 //# sourceMappingURL=system-message.test.js.map

package/dist/wiki/topic-structure.js

@@ -27,6 +27,9 @@ export const EXEMPT_PREFIXES = [
     "pages/kpis/",
     "pages/shared/",
 ];
+export const EXEMPT_PAGES = [
+    "pages/index.md",
+];
 /** Map a `remember`-style category name to its directory under pages/. */
 const CATEGORY_DIR_MAP = {
     person: "people",
@@ -65,7 +68,8 @@ function isFlatCategory(dir) {
     return FLAT_CATEGORIES.includes(dir);
 }
 function isExemptPath(relativePath) {
-    return EXEMPT_PREFIXES.some((p) => relativePath.startsWith(p));
+    return EXEMPT_PAGES.includes(relativePath)
+        || EXEMPT_PREFIXES.some((p) => relativePath.startsWith(p));
 }
 /** Slugify a free-text name into a wiki-safe path segment. */
 export function slugify(name) {

package/dist/wiki/topic-structure.test.js

@@ -25,6 +25,7 @@ test("topicPagePath builds canonical paths", () => {
     assert.equal(topicPagePath("tool", "Kubernetes"), "pages/tools/kubernetes/index.md");
 });
 test("validateTopicPath accepts canonical and exempt paths", () => {
+    assert.deepEqual(validateTopicPath("pages/index.md"), { ok: true });
     assert.deepEqual(validateTopicPath("pages/projects/chapterhouse/index.md"), { ok: true });
     assert.deepEqual(validateTopicPath("pages/projects/chapterhouse/decisions.md"), { ok: true });
     assert.deepEqual(validateTopicPath("pages/people/brian/index.md"), { ok: true });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chapterhouse",
-  "version": "0.3.16",
+  "version": "0.3.17",
   "description": "Chapterhouse — a team-level AI assistant for engineering teams, built on the GitHub Copilot SDK. Web UI only.",
   "bin": {
     "chapterhouse": "dist/cli.js"

package/skills/wiki-conventions/SKILL.md

@@ -0,0 +1,145 @@
+---
+name: wiki-conventions
+description: Use when creating, editing, linting, restructuring, or reviewing Chapterhouse wiki content.
+when_to_load: Wiki tools, remember/forget workflows, or direct edits under the Chapterhouse wiki.
+related_skills:
+  - squad
+---
+
+# Wiki Conventions
+
+Use this skill before creating, editing, linting, restructuring, archiving, or reviewing Chapterhouse wiki content.
+
+## Orientation Ritual — Mandatory Before Any Wiki Write
+
+Perform this checklist before using `wiki_update`, `remember`, `forget`, `wiki_ingest`, `wiki_lint`, or `wiki_rebuild_index`:
+
+1. Read `pages/index.md` with `wiki_read`.
+2. Scan the last 20-30 entries of `pages/_meta/log.md` to see recent edits, archives, and reorganizations.
+3. If the wiki is large, the topic is ambiguous, or you might be creating a page, run `wiki_search` for the topic first.
+
+Do not skip the ritual because the task feels small. The point is to avoid duplicate pages, category mistakes, stale contradictions, and taxonomy drift.
+
+## Wiki Structure Recap
+
+- **Entity categories** live at `pages/<category>/<topic>/index.md` with optional facet pages beside the overview.
+- **Flat categories** live in a single page such as `pages/preferences.md`, `pages/facts.md`, or `pages/routines.md`.
+- **Decisions** always belong to an entity and should land in `pages/<entity-category>/<topic>/decisions.md`.
+
+## Naming Conventions
+
+- Use lowercase only.
+- Use kebab-case slugs.
+- Do not put dates in slugs.
+- Keep facet names predictable and durable, such as `decisions`, `feature-ideas`, or `architecture`.
+- If a name feels ad hoc, it probably belongs as a section on an existing page instead of a new facet.
+
+## `index.md` vs Facet Pages
+
+- Use `index.md` for the durable overview of a topic, entity, or area.
+- Use a facet page only when the subtopic has ongoing value and a stable identity.
+- Do not create a facet page as random overflow for a page that merely feels long today.
+- If a page is growing because it contains several durable subtopics, split those into facets and keep `index.md` as the orientation page.
+
+## Page Creation Thresholds
+
+- Create a new page when a topic appears in two or more distinct sources or interactions.
+- Create a new page when the topic is central to one major source, even if it is only one source so far.
+- Add to an existing page when coverage already exists.
+- Do not create a page for a passing mention, transient detail, or one-off aside.
+- Split pages once they approach roughly 300 lines.
+- Archive fully superseded pages into `pages/_archive/` and remove them from the active index rather than letting stale content linger in place.
+
+## Decision Recording Protocol
+
+- With `remember`, use `category: "decision"` plus both `about` and `entity`.
+- Record the decision against the actual entity that owns it.
+- Keep decision facets canonical; prefer `decisions.md` over inventing one-off decision page names.
+
+## Cross-Reference Standards
+
+- Prefer wiki-relative paths over raw URLs when a wiki page exists.
+- Avoid raw local absolute paths in the body when a canonical wiki page can be linked instead.
+- Add reciprocal links when the relationship is durable enough that future readers should discover it from either side.
+
+## Tag Usage
+
+- Treat the merged taxonomy as the source of truth: code-defined defaults plus optional `pages/_meta/taxonomy.md` extensions.
+- Read `pages/_meta/taxonomy.md` before inventing a new tag.
+- If a new durable tag is needed, extend `pages/_meta/taxonomy.md` first instead of inventing the tag inline on a page.
+
+## Contradiction Update Policy
+
+When two sources disagree:
+
+1. Compare dates first.
+2. If the conflict is real, preserve both claims instead of collapsing them into one "truth".
+3. Keep dates, sources, or citations in the page body so the disagreement is auditable.
+4. Add reciprocal `contradictions:` frontmatter references.
+5. Set `contested: true` while the issue remains unresolved.
+6. Use `confidence` to describe certainty; do not smooth over disagreement with vague prose.
+
+## Tone
+
+- Be terse.
+- Be factual.
+- Be dated when the timing matters.
+- Avoid speculative voice such as "I think" unless the uncertainty itself is the fact being recorded.
+- Prefer explicit source attribution over implied certainty.
+
+## Frontmatter Shape
+
+Required fields:
+
+```yaml
+---
+title: Chapterhouse
+summary: Team-level AI assistant for engineering teams.
+---
+```
+
+Recommended fields for most durable pages:
+
+```yaml
+---
+title: Chapterhouse
+summary: Team-level AI assistant for engineering teams.
+updated: 2026-05-12
+tags: [engineering, orchestration]
+related: [pages/projects/chapterhouse/decisions.md]
+---
+```
+
+Use contradiction-supporting fields when needed:
+
+```yaml
+---
+title: Chapterhouse
+summary: Coordination notes about the runtime architecture.
+updated: 2026-05-12
+tags: [engineering, architecture]
+related: [pages/projects/chapterhouse/index.md]
+confidence: low
+contested: true
+contradictions: [pages/projects/chapterhouse/decisions.md]
+---
+```
+
+Use `autostub: true` only for genuine stubs that are intentionally thin and expected to grow later.
+
+## Common Mistakes
+
+- **Wrong category:** move the content to the correct entity or flat page instead of stretching the path rules.
+- **Page created too early:** merge it into an existing page or section until the topic earns a standalone page.
+- **Invented tag:** update `pages/_meta/taxonomy.md` first.
+- **Skipped orientation ritual:** stop, orient, then retry.
+- **Collapsed contradiction:** preserve both claims, date them, and mark the relationship explicitly.
+
+## Routing Guide — "I want to record X. Where does it go?"
+
+- A durable fact about a named project, tool, person, org, topic, or area -> `pages/<category>/<slug>/index.md`
+- A durable subtopic of an existing entity -> `pages/<category>/<slug>/<facet>.md`
+- A decision about an entity -> `remember` with `category: "decision"`, `about`, and `entity`, or write to that entity's `decisions.md`
+- A user preference or routine -> the corresponding flat category page
+- Source material you want preserved before synthesis -> `wiki_ingest`
+- A passing mention with no durable value yet -> do not create a new page; add it to existing context or leave it out