skillwiki 0.10.71 → 0.10.73

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.10.71",
+  "version": "0.10.73",
   "type": "module",
   "bin": {
     "skillwiki": "dist/cli.js",

package/skills/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.10.71",
+  "version": "0.10.73",
   "skills": "./",
   "description": "Project-aware Karpathy-style knowledge base for Claude Code: 21 prompt-only skills (wiki-*, proj-*, using-skillwiki, skillwiki-mcp) backed by the deterministic `skillwiki` CLI.",
   "author": {

package/skills/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.10.71",
+  "version": "0.10.73",
   "description": "Project-aware Karpathy-style knowledge base for Codex with 21 prompt-only skills backed by the deterministic skillwiki CLI.",
   "author": {
     "name": "karlorz",

package/skills/.cursor-plugin/plugin.json

@@ -0,0 +1,31 @@
+{
+  "name": "skillwiki",
+  "version": "0.10.73",
+  "description": "Project-aware Karpathy-style knowledge base: 21 prompt-only skills (wiki-*, proj-*, using-skillwiki, skillwiki-mcp) backed by HTTP MCP wiki_capture.",
+  "author": {
+    "name": "karlorz"
+  },
+  "repository": "https://github.com/karlorz/llm-wiki",
+  "license": "MIT",
+  "keywords": [
+    "knowledge-base",
+    "wiki",
+    "mcp",
+    "skillwiki"
+  ],
+  "variables": {
+    "type": "object",
+    "properties": {
+      "SKILLWIKI_MCP_TOKEN": {
+        "type": "string",
+        "title": "SkillWiki HTTP MCP bearer",
+        "description": "Bearer for https://wiki.karldigi.dev/mcp. Same SKILLWIKI_MCP_TOKEN used by Grok CLI. Never put the value in plugin files."
+      }
+    },
+    "required": [
+      "SKILLWIKI_MCP_TOKEN"
+    ]
+  },
+  "skills": "./",
+  "mcpServers": "./mcp.json"
+}

package/skills/agents/proj-work.md

@@ -21,8 +21,10 @@ You are a project work item manager specializing in creating and executing work
 
 **Execution Process:**
 
+If `$VAULT/.WIKI_GIT_FROZEN` exists after `skillwiki path`: do not create or mutate work folders; do not `page publish` or git commit. Capture a close note via HTTP MCP `wiki_capture` or STOP. Work-item close waits unpublished Tier 2 (`wiki_workitem_write`). Reads of existing folders are allowed.
+
 ### Creating a New Work Item
-1. **Resolve vault.** Run `skillwiki path`.
+1. **Resolve vault.** Run `skillwiki path`. If `.WIKI_GIT_FROZEN` exists, STOP (see freeze rule above).
 2. **Determine slug and kind.** From task prompt: kind (`feature` | `issue` | `refactor` | `decision`) and work slug.
 3. **Create folder.** `projects/{slug}/work/YYYY-MM-DD-{work-slug}/`.
 4. **Write spec.md.** Frontmatter with kind, status=planned, project wikilink. Body with context and scope.
@@ -53,11 +55,13 @@ Return:
 - Log entries appended
 
 **Stop Conditions:**
+- `$VAULT/.WIKI_GIT_FROZEN` exists and the task would create, mutate, or close a work item
 - `validate` non-zero
 - Conflicting work folder name
 - No project context and no `playground` fallback
 
 **Forbidden:**
+- Creating or mutating work items on a vault that has `.WIKI_GIT_FROZEN`
 - Writing spec/plan files outside the work folder
 - Marking `status: completed` without a `completed:` date
 - Accepting tasks.md DONE labels without independent disk verification

package/skills/mcp.json

@@ -2,7 +2,7 @@
   "mcpServers": {
     "skillwiki": {
       "type": "http",
-      "url": "${SKILLWIKI_MCP_URL:-https://wiki.karldigi.dev/mcp}",
+      "url": "https://wiki.karldigi.dev/mcp",
       "headers": {
         "Authorization": "Bearer ${SKILLWIKI_MCP_TOKEN}"
       }

package/skills/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skillwiki/skills",
-  "version": "0.10.71",
+  "version": "0.10.73",
   "private": true,
   "files": [
     "wiki-*",

package/skills/proj-work/SKILL.md

@@ -28,6 +28,15 @@ install with `grok plugin update skillwiki`, not `skillwiki install`.
 ## Pre-orientation reads
 Standard four + project context (project README, last ~5 work logs).
 
+## Frozen-leaf write freeze (Phase 5)
+
+After `skillwiki path`, if `$VAULT/.WIKI_GIT_FROZEN` exists:
+
+- **Reads** of existing work folders are allowed.
+- **Do not** create or mutate `projects/*/work/**`, `knowledge.md`, or run `skillwiki page publish` on this leaf.
+- **Do not** `git commit` / `wiki-sync` push to “close” the item.
+- Work-item close is unpublished until Tier 2 (`wiki_workitem_write` / `wiki_page_publish`). If the user asked to close or complete work, capture a note via HTTP MCP `wiki_capture` (`kind: note` or `task`) and STOP. Do not local-write the work folder.
+
 ## Executing an Existing Work Item
 
 When the user asks to "get work of X" or "run work item Y" for review, you are in EXECUTION mode — not creation mode. Steps:
@@ -90,10 +99,12 @@ Rules:
 - **Re-marking without doing**: do not simply re-write tasks.md to say DONE without applying the corresponding fix. The next session will find the same gap.
 
 ## Stop conditions
+- `$VAULT/.WIKI_GIT_FROZEN` exists and the user asked to create, mutate, or close a work item — capture via `wiki_capture` or STOP; do not local-write.
 - `validate` non-zero.
 - Conflicting work folder name.
 
 ## Forbidden
+- Creating or mutating work items on a vault that has `.WIKI_GIT_FROZEN`.
 - Writing spec/plan files outside the work folder.
 - Marking `status: completed` without a `completed:` date.
 - Accepting tasks.md status labels without independent disk verification.

package/skills/skills/proj-work/SKILL.md

@@ -28,6 +28,15 @@ install with `grok plugin update skillwiki`, not `skillwiki install`.
 ## Pre-orientation reads
 Standard four + project context (project README, last ~5 work logs).
 
+## Frozen-leaf write freeze (Phase 5)
+
+After `skillwiki path`, if `$VAULT/.WIKI_GIT_FROZEN` exists:
+
+- **Reads** of existing work folders are allowed.
+- **Do not** create or mutate `projects/*/work/**`, `knowledge.md`, or run `skillwiki page publish` on this leaf.
+- **Do not** `git commit` / `wiki-sync` push to “close” the item.
+- Work-item close is unpublished until Tier 2 (`wiki_workitem_write` / `wiki_page_publish`). If the user asked to close or complete work, capture a note via HTTP MCP `wiki_capture` (`kind: note` or `task`) and STOP. Do not local-write the work folder.
+
 ## Executing an Existing Work Item
 
 When the user asks to "get work of X" or "run work item Y" for review, you are in EXECUTION mode — not creation mode. Steps:
@@ -90,10 +99,12 @@ Rules:
 - **Re-marking without doing**: do not simply re-write tasks.md to say DONE without applying the corresponding fix. The next session will find the same gap.
 
 ## Stop conditions
+- `$VAULT/.WIKI_GIT_FROZEN` exists and the user asked to create, mutate, or close a work item — capture via `wiki_capture` or STOP; do not local-write.
 - `validate` non-zero.
 - Conflicting work folder name.
 
 ## Forbidden
+- Creating or mutating work items on a vault that has `.WIKI_GIT_FROZEN`.
 - Writing spec/plan files outside the work folder.
 - Marking `status: completed` without a `completed:` date.
 - Accepting tasks.md status labels without independent disk verification.

package/skills/skills/skillwiki-mcp/SKILL.md

@@ -14,6 +14,7 @@ SkillWiki captures are HTTP MCP only (`type: http`). Claude/Grok use `SKILLWIKI_
 ## First-run readiness
 
 - Resolve the installed plugin root from `GROK_PLUGIN_ROOT`, falling back to `CLAUDE_PLUGIN_ROOT`, and run `python3 "$PLUGIN_ROOT/scripts/check_readiness.py" --apply --json` before the first SkillWiki MCP call.
+- **Cursor / Grok Bot:** the Cursor-native plugin requires `SKILLWIKI_MCP_TOKEN` under **Plugins → Configure**. It pins `https://wiki.karldigi.dev/mcp`. Grok Bot does not inherit Mac process env or `~/.cursor/mcp.json`. `failed_to_load` with no token box means this package is missing; after this package is installed, Configure is the token field (same pattern as grok-search).
 - `missing_prereq` means `SKILLWIKI_MCP_TOKEN` is absent from process environment; stop and ask for a bearer. Do not invent a stdio MCP.
 - `in_sync` means the probe has a usable URL/token decision.
 - A 401 is an MCP handshake failure, not a readiness-probe status. Report that the token is missing or rejected and stop.
@@ -27,7 +28,7 @@ On leaf hosts, wiki captures go through MCP. Do **not** write `raw/transcripts/`
 
 1. Call MCP `wiki_capture` with `kind` (`task` | `idea` | `bug` | `note`), `project`, `title`, and `content`. Optional `agent_note`.
 2. Call MCP `wiki_log_append` when a structural `log.md` line is needed. Pass append-only `content`. Do not rewrite log history.
-3. Write surface is captures-only. Do not call unpublished Tier 2 tools. Do not `git commit` / `wiki-push` against `~/wiki` for these captures.
+3. Write surface is captures-only. Do not call unpublished Tier 2 tools (`wiki_workitem_write`, `wiki_page_publish`). Those tools are not on the live daemon. Work-item close is not available from this MCP. Do not `git commit` / `wiki-push` against `~/wiki` for these captures. If `$VAULT/.WIKI_GIT_FROZEN` exists, that freeze is the reason nearby agents cannot close wiki work until Tier 2 ships.
 
 ## Reads
 

package/skills/skills/using-skillwiki/SKILL.md

@@ -162,6 +162,17 @@ The vault is shared across hosts, so host-local absolute paths are not durable s
 | Entry | When | What happens |
 |-------|------|-------------|
 | `wiki_capture` | You're on a frozen-leaf host with HTTP MCP | Calls MCP `wiki_capture(kind, project, title, content)`; server writes `raw/transcripts/` remotely |
+
+### Frozen-leaf write authority (Phase 5)
+
+If the vault has `.WIKI_GIT_FROZEN`:
+
+| Intent | Allowed? | How |
+|---|---|---|
+| Capture note/idea/bug/task | Yes | HTTP MCP `wiki_capture` / `wiki_log_append` |
+| Close or mutate a work item (`projects/*/work/**`, `knowledge.md`) | **No** until Tier 2 | Do not `page publish` or git commit. Capture a close note via MCP or STOP. |
+| `wiki-sync` push/commit | **No** | GitHub is sg01 `wiki-snapshot`. |
+| Read local `~/wiki` | Yes | Mirror reads only |
 | `/wiki-add-task <text>` | You're in an interactive session on an authoring host | Creates `raw/transcripts/YYYY-MM-DD-{type}-{slug}.md` with ad-hoc capture frontmatter |
 | Filesystem drop | You're NOT in a Claude session (Obsidian, editor, sync) on an authoring host | Create a new `.md` file in `raw/transcripts/` — dev-loop discovers it on next cycle; do not edit it after capture |
 | Dev-loop discovery | Automatic, next cycle | Scans `raw/transcripts/` for new files since last cycle, surfaces as claimable work |

package/skills/skills/wiki-sync/SKILL.md

@@ -14,6 +14,16 @@ Standard four reads.
 ## Steps
 0. Resolve vault: `skillwiki path` (record source for context).
 
+## Frozen-leaf git freeze (Phase 5)
+
+If `$VAULT/.WIKI_GIT_FROZEN` exists, **fail closed** before any stash, commit, pull, or push:
+
+- Do **not** `git add`, `git commit`, `git pull`, `git push`, or `skillwiki sync push`.
+- Captures go through HTTP MCP `wiki_capture` / `wiki_log_append`.
+- Closing or mutating work items is unpublished until Tier 2 (`wiki_workitem_write` / `wiki_page_publish`). Capture a close note via MCP or STOP.
+- GitHub promotion is sg01 `wiki-snapshot`, not this leaf.
+- Report the freeze marker and stop. Do not treat dirty `~/wiki` as a sync job.
+
 ## Pre-flight peer check (multi-session safe)
 
 **Before any git stash or pull/push operation**, check for peer sessions:
@@ -210,6 +220,7 @@ High-signal safety rule:
 Some older deployments separated a cloud-backed live vault from a Git snapshot worktree. That architecture still exists on protected snapshotters, but the snapshot worktree is **pipeline-internal**. Historical recipes that rsync into the worktree, reset it hard to origin/main, or run snapshot shell scripts by hand are obsolete and must not be copied.
 
 ## Stop conditions
+- `$VAULT/.WIKI_GIT_FROZEN` exists — frozen leaf; refuse git close/sync. Captures via HTTP MCP; work-item close waits Tier 2.
 - `skillwiki sync status` reports `not_a_repo` — the vault is not a git repository. On protected snapshotters this is expected for the FUSE live path; do not switch to `/root/wiki-git` to force a push.
 - Lint errors are found before a push — do not push until resolved.
 - `git push` or `git pull` fails with a network error — report and stop.
@@ -218,6 +229,7 @@ Some older deployments separated a cloud-backed live vault from a Git snapshot w
 - Host is a protected snapshotter and the requested operation would author or push via `/root/wiki-git` — refuse and use managed live-vault publication + timer promotion instead.
 
 ## Forbidden
+- `git add` / `git commit` / `git push` on a vault that has `.WIKI_GIT_FROZEN`.
 - Pushing when lint errors exist.
 - Auto-resolving body conflicts without user review.
 - Force-pushing (`git push --force`).

package/skills/skillwiki-mcp/SKILL.md

@@ -14,6 +14,7 @@ SkillWiki captures are HTTP MCP only (`type: http`). Claude/Grok use `SKILLWIKI_
 ## First-run readiness
 
 - Resolve the installed plugin root from `GROK_PLUGIN_ROOT`, falling back to `CLAUDE_PLUGIN_ROOT`, and run `python3 "$PLUGIN_ROOT/scripts/check_readiness.py" --apply --json` before the first SkillWiki MCP call.
+- **Cursor / Grok Bot:** the Cursor-native plugin requires `SKILLWIKI_MCP_TOKEN` under **Plugins → Configure**. It pins `https://wiki.karldigi.dev/mcp`. Grok Bot does not inherit Mac process env or `~/.cursor/mcp.json`. `failed_to_load` with no token box means this package is missing; after this package is installed, Configure is the token field (same pattern as grok-search).
 - `missing_prereq` means `SKILLWIKI_MCP_TOKEN` is absent from process environment; stop and ask for a bearer. Do not invent a stdio MCP.
 - `in_sync` means the probe has a usable URL/token decision.
 - A 401 is an MCP handshake failure, not a readiness-probe status. Report that the token is missing or rejected and stop.
@@ -27,7 +28,7 @@ On leaf hosts, wiki captures go through MCP. Do **not** write `raw/transcripts/`
 
 1. Call MCP `wiki_capture` with `kind` (`task` | `idea` | `bug` | `note`), `project`, `title`, and `content`. Optional `agent_note`.
 2. Call MCP `wiki_log_append` when a structural `log.md` line is needed. Pass append-only `content`. Do not rewrite log history.
-3. Write surface is captures-only. Do not call unpublished Tier 2 tools. Do not `git commit` / `wiki-push` against `~/wiki` for these captures.
+3. Write surface is captures-only. Do not call unpublished Tier 2 tools (`wiki_workitem_write`, `wiki_page_publish`). Those tools are not on the live daemon. Work-item close is not available from this MCP. Do not `git commit` / `wiki-push` against `~/wiki` for these captures. If `$VAULT/.WIKI_GIT_FROZEN` exists, that freeze is the reason nearby agents cannot close wiki work until Tier 2 ships.
 
 ## Reads
 

package/skills/using-skillwiki/SKILL.md

@@ -162,6 +162,17 @@ The vault is shared across hosts, so host-local absolute paths are not durable s
 | Entry | When | What happens |
 |-------|------|-------------|
 | `wiki_capture` | You're on a frozen-leaf host with HTTP MCP | Calls MCP `wiki_capture(kind, project, title, content)`; server writes `raw/transcripts/` remotely |
+
+### Frozen-leaf write authority (Phase 5)
+
+If the vault has `.WIKI_GIT_FROZEN`:
+
+| Intent | Allowed? | How |
+|---|---|---|
+| Capture note/idea/bug/task | Yes | HTTP MCP `wiki_capture` / `wiki_log_append` |
+| Close or mutate a work item (`projects/*/work/**`, `knowledge.md`) | **No** until Tier 2 | Do not `page publish` or git commit. Capture a close note via MCP or STOP. |
+| `wiki-sync` push/commit | **No** | GitHub is sg01 `wiki-snapshot`. |
+| Read local `~/wiki` | Yes | Mirror reads only |
 | `/wiki-add-task <text>` | You're in an interactive session on an authoring host | Creates `raw/transcripts/YYYY-MM-DD-{type}-{slug}.md` with ad-hoc capture frontmatter |
 | Filesystem drop | You're NOT in a Claude session (Obsidian, editor, sync) on an authoring host | Create a new `.md` file in `raw/transcripts/` — dev-loop discovers it on next cycle; do not edit it after capture |
 | Dev-loop discovery | Automatic, next cycle | Scans `raw/transcripts/` for new files since last cycle, surfaces as claimable work |

package/skills/wiki-sync/SKILL.md

@@ -14,6 +14,16 @@ Standard four reads.
 ## Steps
 0. Resolve vault: `skillwiki path` (record source for context).
 
+## Frozen-leaf git freeze (Phase 5)
+
+If `$VAULT/.WIKI_GIT_FROZEN` exists, **fail closed** before any stash, commit, pull, or push:
+
+- Do **not** `git add`, `git commit`, `git pull`, `git push`, or `skillwiki sync push`.
+- Captures go through HTTP MCP `wiki_capture` / `wiki_log_append`.
+- Closing or mutating work items is unpublished until Tier 2 (`wiki_workitem_write` / `wiki_page_publish`). Capture a close note via MCP or STOP.
+- GitHub promotion is sg01 `wiki-snapshot`, not this leaf.
+- Report the freeze marker and stop. Do not treat dirty `~/wiki` as a sync job.
+
 ## Pre-flight peer check (multi-session safe)
 
 **Before any git stash or pull/push operation**, check for peer sessions:
@@ -210,6 +220,7 @@ High-signal safety rule:
 Some older deployments separated a cloud-backed live vault from a Git snapshot worktree. That architecture still exists on protected snapshotters, but the snapshot worktree is **pipeline-internal**. Historical recipes that rsync into the worktree, reset it hard to origin/main, or run snapshot shell scripts by hand are obsolete and must not be copied.
 
 ## Stop conditions
+- `$VAULT/.WIKI_GIT_FROZEN` exists — frozen leaf; refuse git close/sync. Captures via HTTP MCP; work-item close waits Tier 2.
 - `skillwiki sync status` reports `not_a_repo` — the vault is not a git repository. On protected snapshotters this is expected for the FUSE live path; do not switch to `/root/wiki-git` to force a push.
 - Lint errors are found before a push — do not push until resolved.
 - `git push` or `git pull` fails with a network error — report and stop.
@@ -218,6 +229,7 @@ Some older deployments separated a cloud-backed live vault from a Git snapshot w
 - Host is a protected snapshotter and the requested operation would author or push via `/root/wiki-git` — refuse and use managed live-vault publication + timer promotion instead.
 
 ## Forbidden
+- `git add` / `git commit` / `git push` on a vault that has `.WIKI_GIT_FROZEN`.
 - Pushing when lint errors exist.
 - Auto-resolving body conflicts without user review.
 - Force-pushing (`git push --force`).