@infinitedusky/indusk-mcp 1.1.3 → 1.2.0

package/dist/bin/cli.js

@@ -75,6 +75,13 @@ ext
     const { extensionsRemove } = await import("./commands/extensions.js");
     await extensionsRemove(process.cwd(), names);
 });
+ext
+    .command("update [names...]")
+    .description("Update third-party extensions from their original source")
+    .action(async (names) => {
+    const { extensionsUpdate } = await import("./commands/extensions.js");
+    await extensionsUpdate(process.cwd(), names);
+});
 ext
     .command("suggest")
     .description("Recommend extensions based on project contents")

package/dist/bin/commands/extensions.d.ts

@@ -4,4 +4,5 @@ export declare function extensionsEnable(projectRoot: string, names: string[]):
 export declare function extensionsDisable(projectRoot: string, names: string[]): Promise<void>;
 export declare function extensionsAdd(projectRoot: string, name: string, from: string): Promise<void>;
 export declare function extensionsRemove(projectRoot: string, names: string[]): Promise<void>;
+export declare function extensionsUpdate(projectRoot: string, names?: string[]): Promise<void>;
 export declare function extensionsSuggest(projectRoot: string): Promise<void>;

package/dist/bin/commands/extensions.js

@@ -68,7 +68,8 @@ export async function extensionsStatus(projectRoot) {
                     .map((r) => r.name)
                     .join(", ")}`;
         }
-        console.info(`  ${ext.manifest.name} — ${healthStatus}`);
+        const source = ext.manifest._source ? ` (from ${ext.manifest._source})` : " (built-in)";
+        console.info(`  ${ext.manifest.name}${source} — ${healthStatus}`);
     }
 }
 export async function extensionsEnable(projectRoot, names) {
@@ -194,9 +195,40 @@ export async function extensionsAdd(projectRoot, name, from) {
         console.info(`  ${name}: invalid JSON in manifest`);
         return;
     }
+    // Store the source in the manifest so `extensions update` can re-fetch
+    try {
+        const parsed = JSON.parse(manifestContent);
+        parsed._source = from;
+        manifestContent = JSON.stringify(parsed, null, "\t");
+    }
+    catch {
+        // leave as-is if parsing fails
+    }
     const targetPath = join(extensionsDir(projectRoot), `${name}.json`);
     writeFileSync(targetPath, manifestContent);
     console.info(`  ${name}: added from ${from}`);
+    // Run post-update hook if defined
+    try {
+        const manifest = JSON.parse(manifestContent);
+        if (manifest.hooks?.on_post_update) {
+            console.info(`  ${name}: running post-update hook...`);
+            try {
+                execSync(manifest.hooks.on_post_update, {
+                    cwd: projectRoot,
+                    timeout: 30000,
+                    stdio: ["ignore", "pipe", "pipe"],
+                });
+                console.info(`  ${name}: post-update hook completed`);
+            }
+            catch (e) {
+                const err = e;
+                console.info(`  ${name}: post-update hook failed: ${err.stderr?.trim() ?? "unknown error"}`);
+            }
+        }
+    }
+    catch {
+        // ignore parse errors
+    }
 }
 export async function extensionsRemove(projectRoot, names) {
     for (const name of names) {
@@ -221,6 +253,42 @@ export async function extensionsRemove(projectRoot, names) {
         }
     }
 }
+export async function extensionsUpdate(projectRoot, names) {
+    const extDir = extensionsDir(projectRoot);
+    if (!existsSync(extDir)) {
+        console.info("No extensions installed.");
+        return;
+    }
+    // Find all third-party extensions (ones with _source)
+    const files = readdirSync(extDir).filter((f) => f.endsWith(".json"));
+    let updated = 0;
+    for (const file of files) {
+        const name = file.replace(".json", "");
+        if (names?.length && !names.includes(name))
+            continue;
+        try {
+            const manifest = JSON.parse(readFileSync(join(extDir, file), "utf-8"));
+            if (!manifest._source) {
+                if (names && names.includes(name)) {
+                    console.info(`  ${name}: built-in extension — updated via package update, not extensions update`);
+                }
+                continue;
+            }
+            console.info(`  ${name}: updating from ${manifest._source}...`);
+            await extensionsAdd(projectRoot, name, manifest._source);
+            updated++;
+        }
+        catch {
+            console.info(`  ${name}: failed to read manifest`);
+        }
+    }
+    if (updated === 0) {
+        console.info("No third-party extensions to update.");
+    }
+    else {
+        console.info(`\n${updated} extension(s) updated.`);
+    }
+}
 export async function extensionsSuggest(projectRoot) {
     const builtins = getBuiltinExtensions();
     const suggestions = [];

package/dist/lib/extension-loader.d.ts

@@ -17,6 +17,7 @@ export interface ExtensionManifest {
     name: string;
     description: string;
     version?: string;
+    _source?: string;
     provides: {
         skill?: boolean;
         networking?: {
@@ -38,6 +39,7 @@ export interface ExtensionManifest {
     hooks?: {
         on_init?: string;
         on_update?: string;
+        on_post_update?: string;
         on_health_check?: string;
         on_onboard?: string;
     };

package/hooks/check-gates.js

@@ -216,11 +216,25 @@ for (const item of newlyChecked) {
 	for (const phase of oldPhases) {
 		if (phase.number >= item.phase) break;
 
-		const isOverridden = (text) =>
-			gatePolicy !== "strict" &&
-			(text.includes("(none needed)") ||
+		const isOverridden = (text) => {
+			if (gatePolicy === "strict") return false;
+
+			const hasBareOptOut =
+				text.includes("(none needed)") ||
 				text.includes("(not applicable)") ||
-				text.includes("skip-reason:"));
+				text.includes("skip-reason:");
+
+			if (gatePolicy === "auto") return hasBareOptOut;
+
+			// ask mode: requires conversation proof
+			// Format: (none needed — asked: "{question}" — user: "{answer}")
+			const hasConversationProof =
+				/\(none needed\s*—\s*asked:\s*"[^"]+"\s*—\s*user:\s*"[^"]+"\)/.test(text) ||
+				/\(not applicable\s*—\s*asked:\s*"[^"]+"\s*—\s*user:\s*"[^"]+"\)/.test(text) ||
+				/skip-reason:.*—\s*asked:\s*"[^"]+"\s*—\s*user:\s*"[^"]+"/.test(text);
+
+			return hasConversationProof;
+		};
 
 		const uncheckedGates = phase.items.filter(
 			(i) => !i.checked && !isOverridden(i.text) && requiredGates.includes(i.gate),
@@ -231,7 +245,9 @@ for (const item of newlyChecked) {
 			const skipHint =
 				gatePolicy === "strict"
 					? "Gate policy is 'strict' — no overrides allowed.\n"
-					: "To skip a gate item, ask the user first, then mark with (none needed) or skip-reason: {why}\n";
+					: gatePolicy === "ask"
+						? 'Gate policy is \'ask\' — to skip, you must ask the user and include proof.\nFormat: (none needed — asked: "your question" — user: "their answer")\n'
+						: "To skip a gate item, mark with (none needed) or skip-reason: {why}\n";
 			process.stderr.write(
 				`Phase ${item.phase} blocked (policy: ${gatePolicy}): complete Phase ${phase.number} gates first:\n${missing}\n${skipHint}`,
 			);

package/hooks/validate-impl-structure.js

@@ -194,7 +194,9 @@ for (const phase of phases) {
 	}
 
 	// In strict mode, opt-outs are not allowed — sections must have real items
-	if (gatePolicy === "strict") {
+	// In ask mode, opt-outs are not allowed at write time — every gate must have a real item
+	// Opt-outs only happen during /work (execution time), not during /plan (write time)
+	if (gatePolicy === "strict" || gatePolicy === "ask") {
 		const optOuts = [];
 		if (requirements.verification && phase.hasVerification && phase.verificationIsOptOut)
 			optOuts.push("Verification");
@@ -202,8 +204,12 @@ for (const phase of phases) {
 		if (requirements.document && phase.hasDocument && phase.documentIsOptOut)
 			optOuts.push("Document");
 		if (optOuts.length > 0) {
+			const modeHint =
+				gatePolicy === "strict"
+					? "strict mode — no opt-outs allowed"
+					: "ask mode — every gate must have a real item when the impl is written. Opt-outs happen during /work after asking the user";
 			errors.push(
-				`Phase ${phase.number} (${phase.name}): ${optOuts.join(", ")} cannot use opt-outs in strict mode — add real items`,
+				`Phase ${phase.number} (${phase.name}): ${optOuts.join(", ")} cannot use opt-outs at write time (${modeHint})`,
 			);
 		}
 	}
@@ -217,7 +223,9 @@ if (errors.length > 0) {
 	const skipHint =
 		gatePolicy === "strict"
 			? "Gate policy is 'strict' — all sections must have real items, no overrides.\n"
-			: "If a section isn't needed, add it with (none needed) or skip-reason: {why}\nExample: #### Phase 1 Document\\n(none needed)\n";
+			: gatePolicy === "ask"
+				? "Gate policy is 'ask' — every gate must have a real item when writing the impl. Opt-outs happen during /work after asking the user.\n"
+				: "If a section isn't needed, add it with (none needed) or skip-reason: {why}\nExample: #### Phase 1 Document\\n(none needed)\n";
 	process.stderr.write(
 		`Impl structure incomplete (workflow: ${workflow}, policy: ${gatePolicy}):\n${msg}\n\nThis workflow requires: ${reqNames.join(", ")} sections per phase.\n${skipHint}To change requirements, add 'workflow: bugfix' to the impl frontmatter.\n`,
 	);

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@infinitedusky/indusk-mcp",
-	"version": "1.1.3",
+	"version": "1.2.0",
 	"description": "InDusk development system — skills, MCP tools, and CLI for structured AI-assisted development",
 	"type": "module",
 	"files": [

package/skills/plan.md

@@ -78,7 +78,11 @@ Workflow templates are in `templates/workflows/` in the package. They describe w
 
 6. **If ADR is accepted** (or brief is accepted for bugfix/refactor), write the impl. Break into phased checklists with concrete tasks. For refactor workflows, include a `## Boundary Map` section. For multi-phase impls of any type, consider adding a boundary map.
 
-   **Gate policy applies when writing impls.** Set `gate_policy` in the impl frontmatter (`strict`, `ask`, or `auto`). See the work skill "Gate Override Policy" for what each mode means. The `validate-impl-structure` hook enforces this at write time.
+   **Gate policy applies when writing impls.** Set `gate_policy` in the impl frontmatter (`strict`, `ask`, or `auto`). The `validate-impl-structure` hook enforces this at write time:
+   - **`strict` / `ask`**: Every gate section (Verification, Context, Document) must have a real item — `(none needed)` and `skip-reason:` are blocked at write time. Opt-outs only happen during `/work` execution.
+   - **`auto`**: Gate sections can be pre-filled with `(none needed)` or `skip-reason:` at write time.
+
+   Default is `ask`. See the work skill "Gate Override Policy" for full details on what each mode enforces at execution time.
 
 7. **If impl is completed** (all items checked off by `/work`), invoke the retrospective skill (`/retrospective {plan-name}`). This handles the structured audit (docs, tests, quality, context), knowledge handoff to the docs site, and archival. Do not write a freeform retrospective — use the skill. (Bugfix and refactor workflows may skip retrospective for small changes — user's call.)
 
@@ -193,6 +197,22 @@ because **{rationale}**.
 ### Risks
 - {Risk and mitigation}
 
+## Documentation Plan
+{Decide upfront what documentation this feature produces. This shapes the Document gates in the impl.}
+
+### Pages
+- {New page or existing page to update — e.g., "New: reference/tools/settlement-api.md", "Update: guide/getting-started.md"}
+
+### Diagrams
+- {What diagrams are needed — e.g., "Architecture diagram showing settlement flow", "Sequence diagram for agent registration"}
+- {Where they go — e.g., "Mermaid in reference/tools/settlement-api.md", "Standalone in guide/architecture.md"}
+
+### Changelog
+- {What changelog entry — e.g., "Added settlement API with EIP-712 receipts"}
+
+### ADR in Docs
+- {Should this ADR be published to the docs site? If yes, which section — e.g., "decisions/settlement-architecture.md"}
+
 ## References
 - {Links to research, brief, related plans, external resources}
 ```

package/skills/toolbelt.md

@@ -10,7 +10,7 @@ You have MCP tools from two servers: **indusk** (dev system) and **codegraphcont
 /work → executes impl checklist, phase by phase
          each phase has four gates:
            implement → verify → context → document → next phase
-         hooks enforce gates — can't skip
+         hooks enforce gates — can't skip (see Gate Policy below)
                 ↓
 /retrospective → audit, quality ratchet, knowledge handoff, archive
 ```
@@ -52,6 +52,18 @@ While executing impl items:
 - After completing context items, call `get_context` to verify CLAUDE.md was updated correctly.
 - After completing document items, call `list_docs` to verify the doc page exists.
 
+## Gate Policy
+
+Gates prevent skipping important work. Three enforcement levels, set via `gate_policy` in impl frontmatter or `.claude/settings.json`:
+
+| Mode | Writing the impl (`/plan`) | Executing the impl (`/work`) |
+|------|---------------------------|------------------------------|
+| **`strict`** | Every gate must have a real item. No `(none needed)`. | Every item must be completed. No skipping. |
+| **`ask`** (default) | Every gate must have a real item. No `(none needed)`. | Skip only with conversation proof: `(none needed — asked: "..." — user: "...")` |
+| **`auto`** | `(none needed)` / `skip-reason:` allowed at write time. | Skip without asking using `(none needed)` or `skip-reason:`. |
+
+Hooks enforce both stages. See the work skill "Gate Override Policy" for full details.
+
 ## Advancing Phases
 
 When you think a phase is complete:

package/skills/work.md

@@ -69,9 +69,9 @@ Three modes, configured via `gate_policy` in the impl frontmatter or `.claude/se
 
 | Mode | Behavior |
 |------|----------|
-| **`strict`** | No overrides. Every gate item must be completed. `(none needed)` and `skip-reason:` are not accepted. Use for critical work where nothing should be skipped. |
-| **`ask`** (default) | Agent must ask the user before skipping any gate item. The agent explains why it wants to skip and waits for approval. Only after the user says yes can it mark with `skip-reason:`. |
-| **`auto`** | Agent can skip with `skip-reason:` without asking. Use when running autonomously or when you trust the agent's judgment. |
+| **`strict`** | No overrides at any stage. Every gate must have a real item when the impl is written (`/plan`), and every item must be completed during `/work`. No `(none needed)`, no `skip-reason:`, no conversation proof. |
+| **`ask`** (default) | Every gate must have a real item when the impl is written. During `/work`, the agent must ask the user before skipping, and include proof of the conversation in the skip format. Hooks enforce both stages. |
+| **`auto`** | Gates can be pre-filled with `(none needed)` or `skip-reason:` at write time. During `/work`, the agent can skip without asking. Use when running autonomously. |
 
 ### How to set the mode
 
@@ -100,14 +100,30 @@ Priority: per-invocation > per-plan > per-project > default (`ask`).
 
 When the agent encounters a gate item it thinks should be skipped:
 
-> "Phase 2 has a Document gate: 'Write reference page for the new API.' I don't think this phase needs a new docs page because we only changed internal implementation — the public API didn't change. Can I mark this as `skip-reason: internal change, no public API change`?"
+> "Phase 2 has a Document gate: 'Write reference page for the new API.' I don't think this phase needs a new docs page because we only changed internal implementation — the public API didn't change. Can I skip the document gate?"
 
 The user can say:
-- **"yes"** — agent marks it with skip-reason and continues
+- **"yes, skip it"** — agent marks it with conversation proof and continues
 - **"no, do it"** — agent completes the gate item
-- **"no, but mark it (none needed)"** — if the gate truly doesn't apply
 
-**The agent must NEVER skip a gate without asking in `ask` mode.** This is the core enforcement. The hooks block unauthorized skips, and the skill enforces the conversation.
+### Conversation proof format (enforced by hooks)
+
+In `ask` mode, skipped gates MUST include proof that the conversation happened:
+
+```markdown
+#### Phase 2 Document
+- [x] (none needed — asked: "Phase 2 is internal refactoring with no public API changes. Can I skip the document gate?" — user: "yes, skip it")
+```
+
+The hook validates that both `asked:` and `user:` are present with non-empty quoted content. Bare `(none needed)` or `skip-reason:` without conversation proof will be **blocked by the hook**.
+
+| Mode | At write time (`/plan`) | At execution time (`/work`) |
+|------|------------------------|---------------------------|
+| `strict` | No opt-outs — real items required | No skipping — everything completed |
+| `ask` | No opt-outs — real items required | Skip only with conversation proof |
+| `auto` | `(none needed)` / `skip-reason:` allowed | Skip without asking |
+
+**The agent must NEVER skip a gate without asking in `ask` mode.** This is enforced by hooks at both stages — not just instructional.
 
 11. **Verification items.** The Verification section requires proof, not assumption. See the verify skill for full guidance.
    - Run checks in order: type check → lint → affected tests → build. Skip checks that don't apply (see verify skill's skip logic table).