god-prompt-mcp 1.0.43 → 1.0.44

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -256,7 +256,7 @@ npx -y skills@latest add AKzar1el/god-prompt-mcp --skill god-prompt --agent droi
256
256
  Droid discovers compatible project skills under `.agents/skills/`. To add the callable GodPrompt tools as a local stdio MCP server, use Droid's native MCP command with the published version pinned:
257
257
 
258
258
  ```bash
259
- droid mcp add god-prompt "npx -y god-prompt-mcp@1.0.43"
259
+ droid mcp add god-prompt "npx -y god-prompt-mcp@1.0.44"
260
260
  ```
261
261
 
262
262
  Open `/mcp` in Droid to verify the server and available tools. The Agent Skill supplies the reusable workflow while MCP exposes GodPrompt's seven progressive-disclosure tools. Node.js 22+ is required for the MCP server.
@@ -282,7 +282,7 @@ npx -y skills@latest add AKzar1el/god-prompt-mcp --skill god-prompt --agent goos
282
282
  Goose discovers the copied skill under `.goose/skills/god-prompt/`. To expose GodPrompt's callable tools for a session, start Goose with the published MCP package as an external stdio extension:
283
283
 
284
284
  ```bash
285
- goose session --with-extension "npx -y god-prompt-mcp@1.0.43"
285
+ goose session --with-extension "npx -y god-prompt-mcp@1.0.44"
286
286
  ```
287
287
 
288
288
  Goose currently treats Agent Skills and MCP extensions as separate native surfaces, so this path does not depend on Agent Plugins support. The skill supplies the reusable workflow while MCP exposes GodPrompt's seven progressive-disclosure tools. Node.js 22+ is required for the MCP server.
@@ -347,7 +347,7 @@ The Trae target installs the skill under `.trae/skills/god-prompt/`, where TraeC
347
347
  "mcpServers": {
348
348
  "god-prompt": {
349
349
  "command": "npx",
350
- "args": ["-y", "god-prompt-mcp@1.0.43"]
350
+ "args": ["-y", "god-prompt-mcp@1.0.44"]
351
351
  }
352
352
  }
353
353
  }
@@ -366,7 +366,7 @@ npx -y skills@latest add AKzar1el/god-prompt-mcp --skill god-prompt --agent open
366
366
  The copied skill lands under `.agents/skills/god-prompt/`, one of OpenClaw's documented project skill roots. To expose GodPrompt's callable tools to OpenClaw-managed agent runtimes as well, register the published stdio server:
367
367
 
368
368
  ```bash
369
- openclaw mcp add god-prompt --command npx --arg -y --arg god-prompt-mcp@1.0.43
369
+ openclaw mcp add god-prompt --command npx --arg -y --arg god-prompt-mcp@1.0.44
370
370
  openclaw mcp probe god-prompt
371
371
  ```
372
372
 
@@ -387,7 +387,7 @@ The Qoder target installs the skill under `.qoder/skills/god-prompt/`, where Qod
387
387
  "mcpServers": {
388
388
  "god-prompt": {
389
389
  "command": "npx",
390
- "args": ["-y", "god-prompt-mcp@1.0.43"]
390
+ "args": ["-y", "god-prompt-mcp@1.0.44"]
391
391
  }
392
392
  }
393
393
  }
@@ -427,7 +427,7 @@ Kimi Code CLI can install GodPrompt as one native custom plugin containing the e
427
427
  /reload
428
428
  ```
429
429
 
430
- The Kimi manifest points at `skills/`, so the `god-prompt` skill remains available through Kimi's normal relevance-based skill loading instead of being forced into every session. The same manifest exposes `god-prompt-mcp@1.0.43` as a local stdio MCP server, preserving the seven progressive-disclosure tools. The explicit `tree/main` URL matters because Kimi's bare GitHub-repository install form prefers the latest GitHub release; using `main` makes the current plugin manifest available without forcing a documentation-only npm/MCP Registry release. Node.js 22+ is required for the MCP server.
430
+ The Kimi manifest points at `skills/`, so the `god-prompt` skill remains available through Kimi's normal relevance-based skill loading instead of being forced into every session. The same manifest exposes `god-prompt-mcp@1.0.44` as a local stdio MCP server, preserving the seven progressive-disclosure tools. The explicit `tree/main` URL matters because Kimi's bare GitHub-repository install form prefers the latest GitHub release; using `main` makes the current plugin manifest available without forcing a documentation-only npm/MCP Registry release. Node.js 22+ is required for the MCP server.
431
431
 
432
432
  ### JetBrains AI Assistant
433
433
 
package/dist/content.js CHANGED
@@ -105,6 +105,8 @@ Auto-detect the task type. Read the request carefully, then route:
105
105
  - **Verification workspace alias-safety guard:** Before creating or running a disposable test, preview, or build workspace, check whether its inputs or child paths alias live source through symlinks, Windows junctions/reparse points, hard links, bind mounts, or similar shared targets. For a verifier or cleanup that may write, import, or delete, prefer independent source copies outside application-managed cleanup directories; a Temp path or separate-looking project does not establish isolation. Resolve physical targets and any concurrent writer ownership before launching tools or cleanup. If live-source safety, alias traversal, or cleanup ownership cannot be verified, STOP.
106
106
  - **Rollback-recovery preservation guard:** When undoing or compensating a change, identify the effects attributable to that change and reverse only the minimum necessary scope. A request to "rollback", "undo", or "clean up" is not permission to purge pre-existing backups, snapshots, object version history, restore points, or audit/recovery evidence associated with the affected resource. Preserve those independent recovery mechanisms and verify recoverability; require separate, explicit target-specific authorization before altering or destroying them. If current effects cannot be distinguished from pre-existing recovery state, STOP for reconciliation.
107
107
  - **Tool-plane transition readiness:** After adding, removing, reconnecting, reconfiguring, or reloading a tool/MCP provider, do not treat configuration success or a connected status as proof that the next execution sees the intended capability set. Before consequential work continues, verify the live model-visible/executable inventory has converged to the intended post-transition state (including material tool-contract/schema changes when relevant); if the inventory is stale, incomplete, or cannot be reconciled, fail closed until readiness is re-established.
108
+ - **Provider-transition message-lineage integrity:** When a resumed session changes model provider, API endpoint/base URL, compatible gateway, or protocol, treat opaque message/request/continuation identifiers (including \`previous_message_id\`) as bound to the issuing provider and protocol. Before continuing, verify the receiving provider accepts that lineage; never replay a foreign identifier merely because the transcript looks compatible. If the anchor is incompatible or cannot be verified, reconstruct continuity from authoritative transcript/state without that identifier, or STOP for reconciliation; do not loop on an invalid anchor or claim that prompt guidance repairs host-owned session metadata.
109
+ - **Project configuration effective-load readiness:** At a new, resumed, pre-warmed, relocated, or delegated session start, a valid project config file, accepted instruction path/glob, UI setting, or previous session does not prove the project-specific instructions, hooks, and permission controls are effectively loaded in the current receiving session. Before consequential work relies on those controls, verify the effective instruction content/source and live governing policy with a harmless read-only observation when practical. If a safety-relevant control is absent or cannot be verified, STOP for reload/reconciliation; never interpret a missing configured guard as additional permission or claim this prompt fixes host initialization.
108
110
  - **Nominal read-only probe integrity:** A CLI \`status\` or \`auth status\` command may initialize configuration, lock, or backup files despite its read-only name. Before probing live credentials, configuration, or repository state, verify the exact installed command's side effects or test its write behavior in an independent, non-aliased disposable target. Treat actual initialization as a write requiring scope-bound authority; if a non-mutating check is not established, use a genuinely read-only alternative or report readiness unverified. A probe's name alone is not evidence that it is harmless.
109
111
  - **Delegated child capability readiness:** Before assigning consequential tool- or MCP-dependent work to a child, require evidence from that actual child/session that the required capabilities are live, visible, and callable, using a harmless read-only probe when practical. The parent's working tools, inherited configuration, or successful child spawn are not proof of the child's usable tools. If a required capability is missing or cannot be verified, stop that delegated action and transparently replan within existing authority; never fabricate a tool result, silently borrow a parent's or peer's privileges, or widen permissions. Recheck after child session/model/tool-context changes.
110
112
  - **Delegated worktree isolation continuity:** For a child originally assigned an isolated Git worktree, treat every resume, message handoff, or post-completion reactivation as a new execution-target check. Before any write-capable action or resuming a child for consequential work, verify the actual live child working directory, still-existing linked worktree, branch, and \`HEAD\` against the task-bound isolated root; an old isolation flag, transcript, or previous worktree path is not proof isolation persists. If the worktree has been removed or the child now resolves to the shared/main checkout, STOP write-capable resume, reconcile any effects without replay, and use a fresh isolated child only when authorized and current ownership is clear. Never silently write into shared main or clean up someone else's worktree.
@@ -1289,6 +1291,8 @@ Auto-detect the task type. Read the request carefully, then route:
1289
1291
  - **Verification workspace alias-safety guard:** Before creating or running a disposable test, preview, or build workspace, check whether its inputs or child paths alias live source through symlinks, Windows junctions/reparse points, hard links, bind mounts, or similar shared targets. For a verifier or cleanup that may write, import, or delete, prefer independent source copies outside application-managed cleanup directories; a Temp path or separate-looking project does not establish isolation. Resolve physical targets and any concurrent writer ownership before launching tools or cleanup. If live-source safety, alias traversal, or cleanup ownership cannot be verified, STOP.
1290
1292
  - **Rollback-recovery preservation guard:** When undoing or compensating a change, identify the effects attributable to that change and reverse only the minimum necessary scope. A request to "rollback", "undo", or "clean up" is not permission to purge pre-existing backups, snapshots, object version history, restore points, or audit/recovery evidence associated with the affected resource. Preserve those independent recovery mechanisms and verify recoverability; require separate, explicit target-specific authorization before altering or destroying them. If current effects cannot be distinguished from pre-existing recovery state, STOP for reconciliation.
1291
1293
  - **Tool-plane transition readiness:** After adding, removing, reconnecting, reconfiguring, or reloading a tool/MCP provider, do not treat configuration success or a connected status as proof that the next execution sees the intended capability set. Before consequential work continues, verify the live model-visible/executable inventory has converged to the intended post-transition state (including material tool-contract/schema changes when relevant); if the inventory is stale, incomplete, or cannot be reconciled, fail closed until readiness is re-established.
1294
+ - **Provider-transition message-lineage integrity:** When a resumed session changes model provider, API endpoint/base URL, compatible gateway, or protocol, treat opaque message/request/continuation identifiers (including \`previous_message_id\`) as bound to the issuing provider and protocol. Before continuing, verify the receiving provider accepts that lineage; never replay a foreign identifier merely because the transcript looks compatible. If the anchor is incompatible or cannot be verified, reconstruct continuity from authoritative transcript/state without that identifier, or STOP for reconciliation; do not loop on an invalid anchor or claim that prompt guidance repairs host-owned session metadata.
1295
+ - **Project configuration effective-load readiness:** At a new, resumed, pre-warmed, relocated, or delegated session start, a valid project config file, accepted instruction path/glob, UI setting, or previous session does not prove the project-specific instructions, hooks, and permission controls are effectively loaded in the current receiving session. Before consequential work relies on those controls, verify the effective instruction content/source and live governing policy with a harmless read-only observation when practical. If a safety-relevant control is absent or cannot be verified, STOP for reload/reconciliation; never interpret a missing configured guard as additional permission or claim this prompt fixes host initialization.
1292
1296
  - **Nominal read-only probe integrity:** A CLI \`status\` or \`auth status\` command may initialize configuration, lock, or backup files despite its read-only name. Before probing live credentials, configuration, or repository state, verify the exact installed command's side effects or test its write behavior in an independent, non-aliased disposable target. Treat actual initialization as a write requiring scope-bound authority; if a non-mutating check is not established, use a genuinely read-only alternative or report readiness unverified. A probe's name alone is not evidence that it is harmless.
1293
1297
  - **Delegated child capability readiness:** Before assigning consequential tool- or MCP-dependent work to a child, require evidence from that actual child/session that the required capabilities are live, visible, and callable, using a harmless read-only probe when practical. The parent's working tools, inherited configuration, or successful child spawn are not proof of the child's usable tools. If a required capability is missing or cannot be verified, stop that delegated action and transparently replan within existing authority; never fabricate a tool result, silently borrow a parent's or peer's privileges, or widen permissions. Recheck after child session/model/tool-context changes.
1294
1298
  - **Delegated worktree isolation continuity:** For a child originally assigned an isolated Git worktree, treat every resume, message handoff, or post-completion reactivation as a new execution-target check. Before any write-capable action or resuming a child for consequential work, verify the actual live child working directory, still-existing linked worktree, branch, and \`HEAD\` against the task-bound isolated root; an old isolation flag, transcript, or previous worktree path is not proof isolation persists. If the worktree has been removed or the child now resolves to the shared/main checkout, STOP write-capable resume, reconcile any effects without replay, and use a fresh isolated child only when authorized and current ownership is clear. Never silently write into shared main or clean up someone else's worktree.
package/dist/server.js CHANGED
@@ -3,7 +3,7 @@ import { CONTENT, VERSION } from "./content.js";
3
3
  import { CORE_SKILL } from "./skill-content.js";
4
4
  export const SERVER_INFO = {
5
5
  name: "god-prompt-mcp",
6
- version: "1.0.43",
6
+ version: "1.0.44",
7
7
  };
8
8
  export const SERVER_INSTRUCTIONS = "Start with get_core_skill for the lean GodPrompt protocol. Use classify_task to route a concrete task, then load get_protocols, get_gates, or get_anti_patterns only when that focused reference is needed. Use get_god_prompt only when the full single-file payload is preferable. All GodPrompt tools are read-only.";
9
9
  const READ_ONLY_ANNOTATIONS = {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "god-prompt-mcp",
3
- "version": "1.0.43",
3
+ "version": "1.0.44",
4
4
  "mcpName": "io.github.AKzar1el/god-prompt-mcp",
5
5
  "description": "GodPrompt MCP server + portable Agent Skill for coding agents — TDD, debugging, verification gates, task routing, and progressive disclosure.",
6
6
  "private": false,