@inharness-ai/claude4spec 1.0.0

package/dist/server/skills/layered-vertical-slices/workflows/daily.md

@@ -0,0 +1,77 @@
+# Daily workflow (existing spec)
+
+Use this when **the `<index>` file already exists in the CWD** — the spec is in place and the user is feeding ideas, problems, or explicit edits into it. For greenfield bootstrap, see `workflows/bootstrap.md`.
+
+This is the mode you spend most hours in. The user almost never speaks in spec-language — they speak in *intent* ("what if endpoints could be versioned?"), in *complaint* ("this auth flow feels off"), or in concrete edits ("add a `retries` column to M03"). Your job is to translate, locate, and edit — without breaking the rules in SKILL.md §6.
+
+**Default to small, focused changes.** If a single user message implies a sweep across many files, propose splitting it before you touch anything.
+
+## Step 0 — Hear the user (always run this first)
+
+Before reading the spec, before classifying, before locating files: restate the user's *intent* in their own terms — what they're trying to enable, for whom, why now. Do this **even when the user thinks they're filing an explicit edit** ("add column X"). Edits without grounded intent become entries in the spec that no one — human or code-gen agent — can later interpret.
+
+Output a 2–3 line restatement and ask one targeted clarification if anything is murky. Format:
+
+> *"Read as: you want endpoint authors to be able to express retry policy per-endpoint, because the current spec forces retry logic into shared middleware. Confirm? (Or is the goal narrower — just a `retries` count column without the policy framing?)"*
+
+Only after the user confirms (or after you've read enough of the existing spec to confidently restate without asking) move to Step 1.
+
+If the user is in **explicit-change mode** (Mode A in Step 2), the restatement is shorter — one line — but still mandatory. Routine edits still benefit from verifying the *why*; tautological "yes please add the column" is the cheap case, not a reason to skip. The cost of one extra line of confirmation is tiny; the cost of writing a column whose purpose dissolves in three months is real.
+
+This step is also the place to push back: if you cannot construct a coherent user-need behind the request — if the request reads as architectural taste or speculative cleanup with no user-visible improvement — say so plainly and ask. The skill is not a stenographer; it's a translator, and a translator can refuse to translate noise.
+
+## Step 1 — Orient
+
+Read `<index>`. Skim the layer table and module table. Read any module or layer the user mentions, plus the file that you suspect will need editing. Do not propose a change until you've read the file you'd be changing — never rely on memory or on a previous session's context.
+
+If the user references a relation between modules (e.g. "the link between Endpoint and DTO"), read both module files.
+
+## Step 2 — Classify what the user is asking
+
+Decide explicitly which mode the user is in. State the mode out loud if it isn't obvious; this gives the user a chance to correct.
+
+- **Mode A — explicit change.** *"Add column `retries` to M03."* / *"Rename L4 from 'Library API' to 'SDK'."* The location and shape of the change are stated. → Skip to Step 4.
+- **Mode B — idea / problem / vague concern.** *"What if endpoints could be versioned?"* / *"This auth flow feels off."* / *"We should track who edited what."* The user has intent, not an edit. → Go to Step 3.
+- **Mode C — bug / inconsistency report.** *"M04 says X but L1 says Y."* / *"This module is missing a layer it clearly touches."* / *"`<index>` lists M07 but the file isn't there."* → Treat like Mode A but read both sides of the inconsistency before proposing a fix.
+
+If you cannot decide between A and B in one read, ask the user a single short clarification.
+
+## Step 3 — Translate (only Mode B)
+
+Map the idea or problem onto the specification grid. State your mapping out loud and ask for confirmation before editing. The candidate buckets:
+
+- **New module.** The user introduces a new entity or feature. Propose a module number (next free), a slug, and which layers it touches.
+- **Change to an existing module.** New column, new operation, new edge case, new acceptance criterion, new dependency.
+- **Layer-level change.** A new convention, a new pattern, or a contract change that affects multiple modules. Apply the layer-purity rule (SKILL.md §6) *before* placing anything in a layer: if the candidate paragraph stops being true once you imagine any single module gone, it is not a layer change.
+- **Cross-module relation.** A new dependency between two existing modules. The change goes in *both* module files' `Dependencies` tables and possibly in `<index>`'s relations diagram.
+- **Not a spec change at all.** Implementation detail, UX micro-decision, code style, choice of internal helper. Say so plainly and stop. The spec is for architecture; not every interesting thought belongs in it.
+- **Not yet decided.** The idea is real but unresolved. Add it to `<index>`'s `Open questions` section verbatim instead of editing modules. Move it out of `Open questions` later when the user resolves it.
+
+Present your translation as 2–4 lines and wait for confirmation. Always thread the user-need from Step 0 through the translation — the architectural mapping is *in service of* the intent, not parallel to it:
+
+> *"I read this as: change to M03 (new column `retries: int`), plus a new edge case (retry exhaustion). Motivated by the intent from Step 0 — endpoint authors expressing retry behavior per-endpoint. No layer change needed — retry counts are per-endpoint, not a cross-cutting concern. Confirm?"*
+
+## Step 4 — Edit
+
+Make the focused change to the relevant file(s). Apply *all* of SKILL.md §6, especially:
+- Module-specific details stay in the module, not in the layer (layer-purity rule).
+- Each module-side section follows the schema declared in its layer's `## Module slice schema`.
+- The module lists every layer it actually touches.
+- When you relocate content between files (module → module, section → layer, sub-layer split-out), preserve the anchor and just move the content. Do **not** leave a "moved to MXX" line in the source file.
+
+If the change makes a module file head past ~250 lines, propose splitting it: convert `modules/MXX-<slug>.md` into `modules/MXX-<slug>/`, keep the module's own substance in `MXX-<slug>.md`, and move the dominant layer slice to `LY-<slug>.md` (filename matches `layers/LY-<slug>.md`).
+
+## Step 5 — Drift check
+
+After non-trivial edits, scan `<index>` against files-on-disk:
+
+- Every entry in the module table has a file? Every module file has a row?
+- Every layer touched by any module appears in the layer table?
+- Every relation declared in a module's `Dependencies` table appears in the index's relations diagram?
+- If something was removed, is it marked retired rather than silently deleted?
+
+If you find drift, surface it as a short punch list and ask the user before fixing — drift can be intentional (work-in-progress).
+
+## Step 6 — Stop
+
+State what changed, point to the file(s), and stop. Do not auto-loop into "what else can we improve?" — wait for the user. The user drives the next round.

package/dist/server/ws/gateway.d.ts

@@ -0,0 +1,10 @@
+import type { Server as HttpServer } from 'node:http';
+import type { WsEvent } from '../../shared/types.js';
+export declare class WsGateway {
+    private wss;
+    private clients;
+    constructor(server: HttpServer);
+    broadcast(event: WsEvent): void;
+    private send;
+    close(): Promise<void>;
+}

package/dist/server/ws/gateway.js

@@ -0,0 +1,35 @@
+import { WebSocketServer } from 'ws';
+export class WsGateway {
+    wss;
+    clients = new Set();
+    constructor(server) {
+        this.wss = new WebSocketServer({ noServer: true });
+        server.on('upgrade', (req, socket, head) => {
+            if (req.url !== '/ws')
+                return;
+            this.wss.handleUpgrade(req, socket, head, (ws) => {
+                this.clients.add(ws);
+                ws.on('close', () => this.clients.delete(ws));
+                this.send(ws, { kind: 'hello', ts: Date.now() });
+            });
+        });
+    }
+    broadcast(event) {
+        const payload = JSON.stringify(event);
+        for (const ws of this.clients) {
+            if (ws.readyState === ws.OPEN)
+                ws.send(payload);
+        }
+    }
+    send(ws, event) {
+        if (ws.readyState === ws.OPEN)
+            ws.send(JSON.stringify(event));
+    }
+    async close() {
+        for (const ws of this.clients)
+            ws.close();
+        this.clients.clear();
+        await new Promise((resolve) => this.wss.close(() => resolve()));
+    }
+}
+//# sourceMappingURL=gateway.js.map

package/dist/server/ws/gateway.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"gateway.js","sourceRoot":"","sources":["../../../src/server/ws/gateway.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,eAAe,EAAkB,MAAM,IAAI,CAAC;AAGrD,MAAM,OAAO,SAAS;IACZ,GAAG,CAAkB;IACrB,OAAO,GAAG,IAAI,GAAG,EAAa,CAAC;IAEvC,YAAY,MAAkB;QAC5B,IAAI,CAAC,GAAG,GAAG,IAAI,eAAe,CAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC;QACnD,MAAM,CAAC,EAAE,CAAC,SAAS,EAAE,CAAC,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE;YACzC,IAAI,GAAG,CAAC,GAAG,KAAK,KAAK;gBAAE,OAAO;YAC9B,IAAI,CAAC,GAAG,CAAC,aAAa,CAAC,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC,EAAE,EAAE,EAAE;gBAC/C,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;gBACrB,EAAE,CAAC,EAAE,CAAC,OAAO,EAAE,GAAG,EAAE,CAAC,IAAI,CAAC,OAAO,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;gBAC9C,IAAI,CAAC,IAAI,CAAC,EAAE,EAAE,EAAE,IAAI,EAAE,OAAO,EAAE,EAAE,EAAE,IAAI,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC;YACnD,CAAC,CAAC,CAAC;QACL,CAAC,CAAC,CAAC;IACL,CAAC;IAED,SAAS,CAAC,KAAc;QACtB,MAAM,OAAO,GAAG,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,CAAC;QACtC,KAAK,MAAM,EAAE,IAAI,IAAI,CAAC,OAAO,EAAE,CAAC;YAC9B,IAAI,EAAE,CAAC,UAAU,KAAK,EAAE,CAAC,IAAI;gBAAE,EAAE,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;QAClD,CAAC;IACH,CAAC;IAEO,IAAI,CAAC,EAAa,EAAE,KAAc;QACxC,IAAI,EAAE,CAAC,UAAU,KAAK,EAAE,CAAC,IAAI;YAAE,EAAE,CAAC,IAAI,CAAC,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,CAAC,CAAC;IAChE,CAAC;IAED,KAAK,CAAC,KAAK;QACT,KAAK,MAAM,EAAE,IAAI,IAAI,CAAC,OAAO;YAAE,EAAE,CAAC,KAAK,EAAE,CAAC;QAC1C,IAAI,CAAC,OAAO,CAAC,KAAK,EAAE,CAAC;QACrB,MAAM,IAAI,OAAO,CAAO,CAAC,OAAO,EAAE,EAAE,CAAC,IAAI,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,EAAE,CAAC,OAAO,EAAE,CAAC,CAAC,CAAC;IACxE,CAAC;CACF"}

package/dist/shared/anchor-pattern.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Canonical anchor comment pattern per M06 spec (anchors `kkz1e7d6`, `15u7sazr`).
+ *
+ * Length contract: parsing/validation uses {6,12} — covers:
+ *  - auto-generated 8-char nanoids (section indexer + plan generator)
+ *  - manual semantic anchors (e.g. `m21chatcols`, `anchorscr`, `hdgcopy01`)
+ *
+ * Generation contract is separate: `customAlphabet(...).8` in
+ * `section-indexer.ts` and `plan.ts` stays strict 8 — only parsing/validation
+ * uses {6,12}.
+ *
+ * Single source of truth — re-used by all section-aware consumers per spec
+ * `kkz1e7d6` ("pojedynczy regex per kodbase").
+ */
+export declare const ANCHOR_PATTERN_SOURCE = "<!--\\s*anchor:\\s*([a-z0-9]{6,12})\\s*-->";

package/dist/shared/anchor-pattern.js

@@ -0,0 +1,16 @@
+/**
+ * Canonical anchor comment pattern per M06 spec (anchors `kkz1e7d6`, `15u7sazr`).
+ *
+ * Length contract: parsing/validation uses {6,12} — covers:
+ *  - auto-generated 8-char nanoids (section indexer + plan generator)
+ *  - manual semantic anchors (e.g. `m21chatcols`, `anchorscr`, `hdgcopy01`)
+ *
+ * Generation contract is separate: `customAlphabet(...).8` in
+ * `section-indexer.ts` and `plan.ts` stays strict 8 — only parsing/validation
+ * uses {6,12}.
+ *
+ * Single source of truth — re-used by all section-aware consumers per spec
+ * `kkz1e7d6` ("pojedynczy regex per kodbase").
+ */
+export const ANCHOR_PATTERN_SOURCE = '<!--\\s*anchor:\\s*([a-z0-9]{6,12})\\s*-->';
+//# sourceMappingURL=anchor-pattern.js.map

package/dist/shared/anchor-pattern.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"anchor-pattern.js","sourceRoot":"","sources":["../../src/shared/anchor-pattern.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAG,4CAA4C,CAAC"}

package/dist/shared/diagram-source-escape.d.ts

@@ -0,0 +1,2 @@
+export declare function escapeDiagramSource(source: string): string;
+export declare function unescapeDiagramSource(escaped: string): string;

package/dist/shared/diagram-source-escape.js

@@ -0,0 +1,19 @@
+export function escapeDiagramSource(source) {
+    return source
+        .replace(/&/g, '&')
+        .replace(/"/g, '"')
+        .replace(/\n/g, '
')
+        .replace(/\r/g, '
')
+        .replace(/</g, '&lt;')
+        .replace(/>/g, '&gt;');
+}
+export function unescapeDiagramSource(escaped) {
+    return escaped
+        .replace(/&gt;/g, '>')
+        .replace(/&lt;/g, '<')
+        .replace(/&#13;/g, '\r')
+        .replace(/&#10;/g, '\n')
+        .replace(/&quot;/g, '"')
+        .replace(/&amp;/g, '&');
+}
+//# sourceMappingURL=diagram-source-escape.js.map

package/dist/shared/diagram-source-escape.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"diagram-source-escape.js","sourceRoot":"","sources":["../../src/shared/diagram-source-escape.ts"],"names":[],"mappings":"AAAA,MAAM,UAAU,mBAAmB,CAAC,MAAc;IAChD,OAAO,MAAM;SACV,OAAO,CAAC,IAAI,EAAE,OAAO,CAAC;SACtB,OAAO,CAAC,IAAI,EAAE,QAAQ,CAAC;SACvB,OAAO,CAAC,KAAK,EAAE,OAAO,CAAC;SACvB,OAAO,CAAC,KAAK,EAAE,OAAO,CAAC;SACvB,OAAO,CAAC,IAAI,EAAE,MAAM,CAAC;SACrB,OAAO,CAAC,IAAI,EAAE,MAAM,CAAC,CAAC;AAC3B,CAAC;AAED,MAAM,UAAU,qBAAqB,CAAC,OAAe;IACnD,OAAO,OAAO;SACX,OAAO,CAAC,OAAO,EAAE,GAAG,CAAC;SACrB,OAAO,CAAC,OAAO,EAAE,GAAG,CAAC;SACrB,OAAO,CAAC,QAAQ,EAAE,IAAI,CAAC;SACvB,OAAO,CAAC,QAAQ,EAAE,IAAI,CAAC;SACvB,OAAO,CAAC,SAAS,EAAE,GAAG,CAAC;SACvB,OAAO,CAAC,QAAQ,EAAE,GAAG,CAAC,CAAC;AAC5B,CAAC"}