@ikon85/agent-workflow-kit 0.35.0 → 0.36.1

package/.agents/skills/kit-update/SKILL.md

@@ -54,6 +54,10 @@ release contain the same artifact.
    data, infer an external fact, or manufacture `pending`/`not-applicable` to
    make a capability appear ready.
 
+   File identity includes the package-declared mode as well as bytes. A
+   mode-only Core delta is an update and must be applied transactionally; it
+   must not survive preview as `unchanged` only to fail candidate verification.
+
    Readiness-schema adoption also keeps the Claude and Codex instruction
    surfaces compatible. When exactly one applicable instruction surface has a
    non-empty `## Prod` section and another has no such section, the staged
@@ -103,16 +107,25 @@ release contain the same artifact.
 
    For each conflicted kit-shipped file, always ask the user whether the local
    edit is a generic improvement or project-specific; never decide or act
-   automatically. For a generic improvement, offer to file an issue in the
-   public kit repository and keep the local edit in place as a bridge until a
-   kit release containing the improvement lands. Before running
-   `gh issue create --repo <owner>/agent-workflow-kit`, show a sanitized preview
-   of the exact title and body with consumer identifiers and secrets stripped,
-   then require the user's explicit approval. The consumer user does not need
-   to be a kit maintainer. For a project-specific edit, recommend
+   automatically. For a generic improvement retained as a bridge, run
+   `contribute status <path> --surface=pre-update` and follow only its
+   repository-capability routes. Missing, disabled, invalid, or unverifiable
+   configuration is a generic Consumer and receives preserve/Explicit-fork
+   guidance, never maintainer language or an inferred upstream target. A valid
+   capability may add local preparation and may describe an upstream pull
+   request, but the latter still needs a sanitized exact preview and separate
+   explicit approval before any remote command. For a project-specific edit, recommend
    `npx @ikon85/agent-workflow-kit@latest own <path> --as=explicit-fork` so
-   future updates treat that path as an independent fork. A generic experiment
-   retained only until it returns upstream uses `--as=contribution-bridge`.
+   future updates treat that path as an independent fork. `own` snapshots the
+   path's current local bytes as the explicit-fork ledger identity, including
+   when it follows an already-detected local edit. A generic experiment
+   retained only until it returns upstream uses
+   `npx @ikon85/agent-workflow-kit@latest contribute start <path>`. Prepare its
+   bounded local artifact, when the route report permits it, with `contribute prepare <path>
+   --output=.agent-workflow-kit/contributions/<name>.json`. Both commands are
+   local-only; opening an issue/PR or pushing remains a separate explicit
+   approval. A matching released Core version retires the bridge during
+   reimport.
 
 4. If a candidate is interrupted, discard its reported stage directory or
    resume the transaction through the update API's `resumeFrom` option. Do not

package/.agents/skills/retro/SKILL.md

@@ -164,9 +164,17 @@ Before formulating a patch in step 4, place **every** friction point on the thre
 
 **A GitHub issue is NOT a weight tier.** A real follow-up = work to track → `python3 scripts/board-sync.py create` (step-4 table), **orthogonal** to the ladder; its "weight" follows the follow-up scope. The ladder classifies **config patches**, not "turn it into a ticket".
 
-**Kit-repo routing target (always ask; never automatic).** When a finding lands on a kit-shipped file (a consumer-manifest entry with kit origin), ask whether the improvement is generic or project-specific. For a generic improvement, offer to file a lightweight issue against the public kit repo: a title plus a short body that states the finding, affected file, and why it is generic. For a project-specific improvement, recommend `own` (keep it consumer-owned). The consumer user does not need to be the kit maintainer.
-
-Before any `gh issue create --repo <owner>/agent-workflow-kit` runs, show the user a **sanitized preview** of the exact title and body with consumer identifiers and secrets stripped. Create the issue only after the user explicitly approves that exact text; if the title or body changes, show the revised preview and ask again. This approval is additional to the per-patch approval in step 5.
+**Kit-repo routing target (capability-driven; never automatic).** When a finding
+lands on a kit-shipped file (a consumer-manifest entry with kit origin), ask
+whether the improvement is generic or project-specific. If it enters a
+Contribution Bridge, run `agent-workflow-kit contribute status <path>
+--surface=retro` and use only the reported repository-capability routes.
+Missing, disabled, invalid, or unverifiable configuration is a generic Consumer:
+offer preserve or Explicit fork, never infer maintainer status or an upstream
+target from identity. A valid capability may offer local preparation. Before
+any reported remote route runs, show the **sanitized exact preview** and require
+separate explicit approval; changing the preview requires approval again. For a
+project-specific improvement, recommend `own` (keep it consumer-owned).
 
 **Target missing in the project — separate two cases cleanly:**
 - **(a) Tier skill missing entirely** (e.g. a foreign project without `spec-self-critique`): no durable spec-time gate exists. **Memory is NOT a substitute** — passive recall doesn't catch a recurring spec defect before building. Report honestly: *"this project has no durable target for this tier"* + propose a `/setup-workflow` follow-up. **No fake guard via memory.**

package/.agents/skills/setup-workflow/SKILL.md

@@ -293,7 +293,8 @@ decisions without repository evidence and user confirmation.
 > manifest. It is advisory only: it never blocks, reads the manifest once, uses
 > no network, and silently fails open when the manifest cannot be read. Shell
 > redirection, formatters, and IDE edits are knowingly outside its coverage; the
-> skills remain the rule's primary carrier.
+> skills remain the rule's primary carrier. Its Contribution Bridge follow-up
+> calls the same read-only route resolver with `--surface=guard`.
 
 Activate the shipped hook by reconciling this exact entry into
 `.claude/settings.json`:
@@ -357,6 +358,26 @@ unaffected surfaces, autonomy, and advanced values. Re-read the profile before
 activation and use its fingerprint plus the exclusive profile lock; a
 concurrent user-local change blocks activation and remains byte-preserved.
 
+### 2i. Section A10 — Optional contribution return routing
+
+> Contribution return routing lets a repository advertise a verifiable Kit
+> upstream without guessing who the user is. It controls offered routes, never
+> remote authorization.
+
+Read [contribution-routing.md](./contribution-routing.md) in full. If
+`contributionRouting` is absent, ask whether this repository should advertise
+an upstream contribution route. **Yes** records only the user-confirmed
+owner/repository and local Git remote after verifying that the remote URL
+matches. **Later / No** leaves the section absent or records `enabled: false`
+only when the user requests a durable opt-out. Adopt an existing valid section
+without normalization and preserve every other profile section and unknown key.
+
+Missing, disabled, contradictory, or unverifiable configuration must keep the
+generic preserve/Explicit-fork routes. Never infer capability from username,
+machine, checkout path, repository name, credentials, or current GitHub login.
+Even a valid capability authorizes local preparation only; a pull request,
+push, publish, or merge remains a separate explicit approval.
+
 ### 3. Section B — Triage labels
 
 > When `triage` processes an incoming issue it applies labels (or your tracker's equivalent). It needs strings you've actually configured, or it creates duplicates.

package/.agents/skills/setup-workflow/contribution-routing.md

@@ -0,0 +1,52 @@
+# Contribution return routing
+
+Contribution return is an optional repository capability. It controls which
+routes agents may *offer* for an explicit Contribution Bridge; it never grants
+permission to mutate a remote.
+
+The consumer-owned section in `docs/agents/workflow-capabilities.json` is:
+
+```json contribution-routing-capability
+{
+  "contributionRouting": {
+    "schemaVersion": 1,
+    "enabled": true,
+    "upstream": {
+      "repository": "<owner>/<repository>",
+      "remote": "<local-git-remote>"
+    },
+    "workflows": {
+      "prepareLocal": true,
+      "upstreamPullRequest": {
+        "enabled": true,
+        "requiresExplicitApproval": true
+      }
+    }
+  }
+}
+```
+
+The resolver accepts the maintainer-capable route only when the configured Git
+remote exists and its GitHub owner/repository matches `upstream.repository`.
+It does not inspect usernames, home paths, machine names, the consumer
+repository name, credentials, or GitHub account identity.
+
+- Missing configuration is a generic Consumer: offer preserve or Explicit fork.
+- `enabled: false` is an explicit opt-out with the same generic routes.
+- Invalid, contradictory, or unverifiable configuration fails closed to those
+  generic routes and reports one bounded diagnostic.
+- Valid configuration additionally offers local artifact preparation. It may
+  describe an upstream pull-request route only with
+  `requiresExplicitApproval: true`; this flag documents the gate and does not
+  satisfy it.
+
+Use the same read-only resolver on every surface:
+
+```sh
+agent-workflow-kit contribute status <path> --surface=retro
+agent-workflow-kit contribute status <path> --surface=pre-update
+agent-workflow-kit contribute status <path> --surface=guard
+```
+
+Only `contribute prepare` writes a local bounded artifact. No contribution
+command opens an issue or pull request, pushes, publishes, or merges.

package/.claude/hooks/kit-origin-edit-hint.py

@@ -12,12 +12,6 @@ from pathlib import Path
 
 MANIFEST = "agent-workflow-kit.json"
 TOOLS = {"Edit", "Write"}
-HINT = (
-    "This file has kit origin. Before editing, ask: should this change go "
-    "upstream to agent-workflow-kit, or should the consumer own this file?"
-)
-
-
 def manifest_path(file_path: str, root: Path) -> str | None:
     try:
         target = Path(file_path)
@@ -28,31 +22,42 @@ def manifest_path(file_path: str, root: Path) -> str | None:
     return normalized or None
 
 
-def is_kit_origin(payload: object, root: Path) -> bool:
+def kit_origin_path(payload: object, root: Path) -> str | None:
     if not isinstance(payload, dict) or payload.get("tool_name") not in TOOLS:
-        return False
+        return None
     tool_input = payload.get("tool_input")
     if not isinstance(tool_input, dict) or not isinstance(tool_input.get("file_path"), str):
-        return False
+        return None
     path = manifest_path(tool_input["file_path"], root)
     if path is None:
-        return False
+        return None
     manifest = json.loads((root / MANIFEST).read_text(encoding="utf-8"))
     installed = manifest.get("installed", []) if isinstance(manifest, dict) else []
-    return any(
+    return path if any(
         isinstance(entry, dict) and entry.get("path") == path and entry.get("origin") == "kit"
         for entry in installed
+    ) else None
+
+
+def hint(path: str) -> str:
+    return (
+        "This file has kit origin. Before editing, ask whether the change should "
+        "stay Consumer-owned or return upstream. If it becomes a Contribution "
+        "Bridge, read the repository-scoped route with "
+        f"`agent-workflow-kit contribute status {path} --surface=guard`; "
+        "missing or invalid capability configuration offers preserve/fork only."
     )
 
 
 def main() -> int:
     try:
         payload = json.load(sys.stdin)
-        if is_kit_origin(payload, Path.cwd()):
+        path = kit_origin_path(payload, Path.cwd())
+        if path:
             print(json.dumps({
                 "hookSpecificOutput": {
                     "hookEventName": "PreToolUse",
-                    "additionalContext": HINT,
+                    "additionalContext": hint(path),
                 }
             }))
     except (OSError, ValueError, TypeError):

package/.claude/skills/kit-update/SKILL.md

@@ -54,6 +54,10 @@ release contain the same artifact.
    data, infer an external fact, or manufacture `pending`/`not-applicable` to
    make a capability appear ready.
 
+   File identity includes the package-declared mode as well as bytes. A
+   mode-only Core delta is an update and must be applied transactionally; it
+   must not survive preview as `unchanged` only to fail candidate verification.
+
    Readiness-schema adoption also keeps the Claude and Codex instruction
    surfaces compatible. When exactly one applicable instruction surface has a
    non-empty `## Prod` section and another has no such section, the staged
@@ -103,16 +107,25 @@ release contain the same artifact.
 
    For each conflicted kit-shipped file, always ask the user whether the local
    edit is a generic improvement or project-specific; never decide or act
-   automatically. For a generic improvement, offer to file an issue in the
-   public kit repository and keep the local edit in place as a bridge until a
-   kit release containing the improvement lands. Before running
-   `gh issue create --repo <owner>/agent-workflow-kit`, show a sanitized preview
-   of the exact title and body with consumer identifiers and secrets stripped,
-   then require the user's explicit approval. The consumer user does not need
-   to be a kit maintainer. For a project-specific edit, recommend
+   automatically. For a generic improvement retained as a bridge, run
+   `contribute status <path> --surface=pre-update` and follow only its
+   repository-capability routes. Missing, disabled, invalid, or unverifiable
+   configuration is a generic Consumer and receives preserve/Explicit-fork
+   guidance, never maintainer language or an inferred upstream target. A valid
+   capability may add local preparation and may describe an upstream pull
+   request, but the latter still needs a sanitized exact preview and separate
+   explicit approval before any remote command. For a project-specific edit, recommend
    `npx @ikon85/agent-workflow-kit@latest own <path> --as=explicit-fork` so
-   future updates treat that path as an independent fork. A generic experiment
-   retained only until it returns upstream uses `--as=contribution-bridge`.
+   future updates treat that path as an independent fork. `own` snapshots the
+   path's current local bytes as the explicit-fork ledger identity, including
+   when it follows an already-detected local edit. A generic experiment
+   retained only until it returns upstream uses
+   `npx @ikon85/agent-workflow-kit@latest contribute start <path>`. Prepare its
+   bounded local artifact, when the route report permits it, with `contribute prepare <path>
+   --output=.agent-workflow-kit/contributions/<name>.json`. Both commands are
+   local-only; opening an issue/PR or pushing remains a separate explicit
+   approval. A matching released Core version retires the bridge during
+   reimport.
 
 4. If a candidate is interrupted, discard its reported stage directory or
    resume the transaction through the update API's `resumeFrom` option. Do not

package/.claude/skills/retro/SKILL.md

@@ -164,9 +164,17 @@ Before formulating a patch in step 4, place **every** friction point on the thre
 
 **A GitHub issue is NOT a weight tier.** A real follow-up = work to track → `python3 scripts/board-sync.py create` (step-4 table), **orthogonal** to the ladder; its "weight" follows the follow-up scope. The ladder classifies **config patches**, not "turn it into a ticket".
 
-**Kit-repo routing target (always ask; never automatic).** When a finding lands on a kit-shipped file (a consumer-manifest entry with kit origin), ask whether the improvement is generic or project-specific. For a generic improvement, offer to file a lightweight issue against the public kit repo: a title plus a short body that states the finding, affected file, and why it is generic. For a project-specific improvement, recommend `own` (keep it consumer-owned). The consumer user does not need to be the kit maintainer.
-
-Before any `gh issue create --repo <owner>/agent-workflow-kit` runs, show the user a **sanitized preview** of the exact title and body with consumer identifiers and secrets stripped. Create the issue only after the user explicitly approves that exact text; if the title or body changes, show the revised preview and ask again. This approval is additional to the per-patch approval in step 5.
+**Kit-repo routing target (capability-driven; never automatic).** When a finding
+lands on a kit-shipped file (a consumer-manifest entry with kit origin), ask
+whether the improvement is generic or project-specific. If it enters a
+Contribution Bridge, run `agent-workflow-kit contribute status <path>
+--surface=retro` and use only the reported repository-capability routes.
+Missing, disabled, invalid, or unverifiable configuration is a generic Consumer:
+offer preserve or Explicit fork, never infer maintainer status or an upstream
+target from identity. A valid capability may offer local preparation. Before
+any reported remote route runs, show the **sanitized exact preview** and require
+separate explicit approval; changing the preview requires approval again. For a
+project-specific improvement, recommend `own` (keep it consumer-owned).
 
 **Target missing in the project — separate two cases cleanly:**
 - **(a) Tier skill missing entirely** (e.g. a foreign project without `spec-self-critique`): no durable spec-time gate exists. **Memory is NOT a substitute** — passive recall doesn't catch a recurring spec defect before building. Report honestly: *"this project has no durable target for this tier"* + propose a `/setup-workflow` follow-up. **No fake guard via memory.**

package/.claude/skills/setup-workflow/SKILL.md

@@ -293,7 +293,8 @@ decisions without repository evidence and user confirmation.
 > manifest. It is advisory only: it never blocks, reads the manifest once, uses
 > no network, and silently fails open when the manifest cannot be read. Shell
 > redirection, formatters, and IDE edits are knowingly outside its coverage; the
-> skills remain the rule's primary carrier.
+> skills remain the rule's primary carrier. Its Contribution Bridge follow-up
+> calls the same read-only route resolver with `--surface=guard`.
 
 Activate the shipped hook by reconciling this exact entry into
 `.claude/settings.json`:
@@ -357,6 +358,26 @@ unaffected surfaces, autonomy, and advanced values. Re-read the profile before
 activation and use its fingerprint plus the exclusive profile lock; a
 concurrent user-local change blocks activation and remains byte-preserved.
 
+### 2i. Section A10 — Optional contribution return routing
+
+> Contribution return routing lets a repository advertise a verifiable Kit
+> upstream without guessing who the user is. It controls offered routes, never
+> remote authorization.
+
+Read [contribution-routing.md](./contribution-routing.md) in full. If
+`contributionRouting` is absent, ask whether this repository should advertise
+an upstream contribution route. **Yes** records only the user-confirmed
+owner/repository and local Git remote after verifying that the remote URL
+matches. **Later / No** leaves the section absent or records `enabled: false`
+only when the user requests a durable opt-out. Adopt an existing valid section
+without normalization and preserve every other profile section and unknown key.
+
+Missing, disabled, contradictory, or unverifiable configuration must keep the
+generic preserve/Explicit-fork routes. Never infer capability from username,
+machine, checkout path, repository name, credentials, or current GitHub login.
+Even a valid capability authorizes local preparation only; a pull request,
+push, publish, or merge remains a separate explicit approval.
+
 ### 3. Section B — Triage labels
 
 > When `triage` processes an incoming issue it applies labels (or your tracker's equivalent). It needs strings you've actually configured, or it creates duplicates.

package/.claude/skills/setup-workflow/contribution-routing.md

@@ -0,0 +1,52 @@
+# Contribution return routing
+
+Contribution return is an optional repository capability. It controls which
+routes agents may *offer* for an explicit Contribution Bridge; it never grants
+permission to mutate a remote.
+
+The consumer-owned section in `docs/agents/workflow-capabilities.json` is:
+
+```json contribution-routing-capability
+{
+  "contributionRouting": {
+    "schemaVersion": 1,
+    "enabled": true,
+    "upstream": {
+      "repository": "<owner>/<repository>",
+      "remote": "<local-git-remote>"
+    },
+    "workflows": {
+      "prepareLocal": true,
+      "upstreamPullRequest": {
+        "enabled": true,
+        "requiresExplicitApproval": true
+      }
+    }
+  }
+}
+```
+
+The resolver accepts the maintainer-capable route only when the configured Git
+remote exists and its GitHub owner/repository matches `upstream.repository`.
+It does not inspect usernames, home paths, machine names, the consumer
+repository name, credentials, or GitHub account identity.
+
+- Missing configuration is a generic Consumer: offer preserve or Explicit fork.
+- `enabled: false` is an explicit opt-out with the same generic routes.
+- Invalid, contradictory, or unverifiable configuration fails closed to those
+  generic routes and reports one bounded diagnostic.
+- Valid configuration additionally offers local artifact preparation. It may
+  describe an upstream pull-request route only with
+  `requiresExplicitApproval: true`; this flag documents the gate and does not
+  satisfy it.
+
+Use the same read-only resolver on every surface:
+
+```sh
+agent-workflow-kit contribute status <path> --surface=retro
+agent-workflow-kit contribute status <path> --surface=pre-update
+agent-workflow-kit contribute status <path> --surface=guard
+```
+
+Only `contribute prepare` writes a local bounded artifact. No contribution
+command opens an issue or pull request, pushes, publishes, or merges.

package/README.md

@@ -331,10 +331,22 @@ npx github:iKon85/agent-workflow-kit uninstall   # remove kit-installed files
 - a file you **did** edit is kept — the incoming version is backed up with a
   timestamp and a diff is printed, never silently overwritten;
 - a file you intentionally fork can be detached with
-  `npx github:iKon85/agent-workflow-kit own <path> --as=explicit-fork`, retained
-  temporarily with `--as=contribution-bridge`, and returned to kit ownership
-  with `npx github:iKon85/agent-workflow-kit disown <path>`; owned files are
+  `npx github:iKon85/agent-workflow-kit own <path> --as=explicit-fork` and
+  returned to kit ownership with
+  `npx github:iKon85/agent-workflow-kit disown <path>`; owned files are
   skipped by updates even after the package stops shipping them;
+- a modified declared Core path enters the temporary Contribution Bridge with
+  `contribute start <path>`. `contribute prepare <path>
+  --output=.agent-workflow-kit/contributions/<name>.json` writes one local,
+  schema-versioned diff/provenance artifact and performs no remote action. A
+  release whose Core bytes match the bridged bytes retires the bridge
+  automatically on reimport;
+- `contribute status <path> --surface=retro|pre-update|guard` reads the same
+  repository-scoped route decision on every workflow surface. Without a valid
+  `contributionRouting` section in `docs/agents/workflow-capabilities.json`,
+  only preserve/Explicit-fork guidance is available. A configured upstream must
+  match its local Git remote; even then, the remote pull-request route requires
+  a separate explicit approval;
 - a file removed upstream is offered for deletion (a hook still referenced by your
   `settings.json` is kept regardless);
 - a new Kit path that already exists locally is an `ambiguous-collision` until
@@ -358,7 +370,33 @@ Ownership commands are designed for a single-user CLI workflow and are not
 concurrency-safe. Do not run manifest-mutating commands concurrently. Flags:
 `--force` (overwrite pre-existing untracked files on `init`), `--yes` / `-y`
 (confirm only already-classified safe update actions), and
-`--as=contribution-bridge|explicit-fork` for `own`.
+`--as=explicit-fork` for `own`.
+
+The optional Contribution Routing capability is consumer-owned:
+
+```json
+{
+  "contributionRouting": {
+    "schemaVersion": 1,
+    "enabled": true,
+    "upstream": {
+      "repository": "owner/repository",
+      "remote": "kit-upstream"
+    },
+    "workflows": {
+      "prepareLocal": true,
+      "upstreamPullRequest": {
+        "enabled": true,
+        "requiresExplicitApproval": true
+      }
+    }
+  }
+}
+```
+
+The resolver verifies the configured remote URL and never infers capability
+from a username, machine, checkout path, consumer repository name, credentials,
+or current GitHub login.
 
 ### Project extensions versus forks
 
@@ -407,6 +445,27 @@ the old way. Decision record:
 
 ## Release notes
 
+### 0.36.1
+
+- changed: `.agents/skills/kit-update/SKILL.md`
+- changed: `.claude/skills/kit-update/SKILL.md`
+- changed: `src/lib/manifest.mjs`
+
+### 0.36.0
+
+- added: `.agents/skills/setup-workflow/contribution-routing.md`
+- added: `.claude/skills/setup-workflow/contribution-routing.md`
+- changed: `.agents/skills/kit-update/SKILL.md`
+- changed: `.agents/skills/retro/SKILL.md`
+- changed: `.agents/skills/setup-workflow/SKILL.md`
+- changed: `.claude/hooks/kit-origin-edit-hint.py`
+- changed: `.claude/skills/kit-update/SKILL.md`
+- changed: `.claude/skills/retro/SKILL.md`
+- changed: `.claude/skills/setup-workflow/SKILL.md`
+- changed: `scripts/find-by-marker.py`
+- changed: `src/lib/manifest.mjs`
+- changed: `src/lib/ownershipClassifier.mjs`
+
 ### 0.35.0
 
 - added: `scripts/project-skill-extension.mjs`

package/agent-workflow-kit.package.json

@@ -1,5 +1,5 @@
 {
-  "kitVersion": "0.35.0",
+  "kitVersion": "0.36.1",
   "files": [
     {
       "path": ".agents/skills/ask-matt/SKILL.md",
@@ -377,7 +377,7 @@
       "ownerSkill": "kit-update",
       "surface": "codex",
       "installRole": "consumer",
-      "sha256": "ac067a33cfbc98a6eb520ab2a819d7cc68b78a39201cd719f40a03a59f499814",
+      "sha256": "ea34bd16072783325c263b4afc4eefc39f0aabdbb53731b84500b46db69ef2c1",
       "mode": 420,
       "origin": "kit"
     },
@@ -547,7 +547,7 @@
       "ownerSkill": "retro",
       "surface": "codex",
       "installRole": "consumer",
-      "sha256": "7466183b55696edc5c7da36eba1de3b218da802de5ea622baa4d6d3c12eb5e42",
+      "sha256": "adaafe450e014a08318f6676a27cd950bb1d48d3dc85515f0cd79d51d50b195e",
       "mode": 420,
       "origin": "kit"
     },
@@ -611,6 +611,16 @@
       "mode": 420,
       "origin": "kit"
     },
+    {
+      "path": ".agents/skills/setup-workflow/contribution-routing.md",
+      "kind": "skill",
+      "ownerSkill": "setup-workflow",
+      "surface": "codex",
+      "installRole": "consumer",
+      "sha256": "1bc224902709868b5e6aa5efa73b48b90a13f956ffe9d8779365f030e6399f67",
+      "mode": 420,
+      "origin": "kit"
+    },
     {
       "path": ".agents/skills/setup-workflow/domain.md",
       "kind": "skill",
@@ -677,7 +687,7 @@
       "ownerSkill": "setup-workflow",
       "surface": "codex",
       "installRole": "consumer",
-      "sha256": "b74b8662f786a662460fe259379f00440c0ccdc10ddecd8af468ebbc220910b9",
+      "sha256": "697ef6f6cdb749bf0646b2add95d4d3246df39c48ca6d9ade063a775690ce462",
       "mode": 420,
       "origin": "kit"
     },
@@ -1117,7 +1127,7 @@
       "path": ".claude/hooks/kit-origin-edit-hint.py",
       "kind": "hook",
       "installRole": "consumer",
-      "sha256": "43e9b9597213c03f7da862602f81e6d6addd3a87e7b20cd52a6a2908b3e90f03",
+      "sha256": "d6662eb75ccdd0bad7bea8e41024b8fd865c00c61ddeb81b8cc9d93f813c75e3",
       "mode": 493,
       "origin": "kit"
     },
@@ -1689,7 +1699,7 @@
       "ownerSkill": "kit-update",
       "surface": "claude",
       "installRole": "consumer",
-      "sha256": "ac067a33cfbc98a6eb520ab2a819d7cc68b78a39201cd719f40a03a59f499814",
+      "sha256": "ea34bd16072783325c263b4afc4eefc39f0aabdbb53731b84500b46db69ef2c1",
       "mode": 420,
       "origin": "kit"
     },
@@ -1859,7 +1869,7 @@
       "ownerSkill": "retro",
       "surface": "claude",
       "installRole": "consumer",
-      "sha256": "290729bb2cb0542fca7aad082e6d0ecc0ab17e377c8ef2723d0597d4f2cefc62",
+      "sha256": "59b31704c9ec7cb25f65efb1c090551a70ebe14b8841be98f87e9e8dfb2dddf2",
       "mode": 420,
       "origin": "kit"
     },
@@ -1943,6 +1953,16 @@
       "mode": 420,
       "origin": "kit"
     },
+    {
+      "path": ".claude/skills/setup-workflow/contribution-routing.md",
+      "kind": "skill",
+      "ownerSkill": "setup-workflow",
+      "surface": "claude",
+      "installRole": "consumer",
+      "sha256": "1bc224902709868b5e6aa5efa73b48b90a13f956ffe9d8779365f030e6399f67",
+      "mode": 420,
+      "origin": "kit"
+    },
     {
       "path": ".claude/skills/setup-workflow/domain.md",
       "kind": "skill",
@@ -2009,7 +2029,7 @@
       "ownerSkill": "setup-workflow",
       "surface": "claude",
       "installRole": "consumer",
-      "sha256": "b74b8662f786a662460fe259379f00440c0ccdc10ddecd8af468ebbc220910b9",
+      "sha256": "697ef6f6cdb749bf0646b2add95d4d3246df39c48ca6d9ade063a775690ce462",
       "mode": 420,
       "origin": "kit"
     },
@@ -2511,7 +2531,7 @@
       "path": "scripts/find-by-marker.py",
       "kind": "script",
       "installRole": "consumer",
-      "sha256": "afaec50d8214dc3d89d28fbcb20faa9f997fc58158593618fcc80fb800b367ea",
+      "sha256": "5c6c4fae9af11cd1fb25eb5310643961fa8d24b10cb41d013574de78c07e855e",
       "mode": 493,
       "origin": "kit"
     },
@@ -2863,7 +2883,7 @@
       "path": "src/lib/manifest.mjs",
       "kind": "script",
       "installRole": "consumer",
-      "sha256": "8696964e50e00eadc5aa3dd1527a8b4fa1b9e5bfe7c061e77fd464ae6843d9a1",
+      "sha256": "f2920f2b25a700be080fbba122a809bf509080673b806aaab2b0c773c8d8267f",
       "mode": 420,
       "origin": "kit"
     },
@@ -2871,7 +2891,7 @@
       "path": "src/lib/ownershipClassifier.mjs",
       "kind": "script",
       "installRole": "consumer",
-      "sha256": "acc70a493626542a686df3b0805feae9b36648c8636d3fe8a4c23b092b851bbb",
+      "sha256": "06a8a455752308db63c4b2aa6f360c540c18dfd3d7f153e52706005c1a51f4e9",
       "mode": 420,
       "origin": "kit"
     },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ikon85/agent-workflow-kit",
-  "version": "0.35.0",
+  "version": "0.36.1",
   "description": "Portable AI-agent workflow skills (plan → execute → land → learn) for Claude Code & Codex — grilling, TDD, diagnosis, two-axis code review, cross-model Codex review, design & domain-modeling, plus a skill router (ask-matt). npx init/update/diff/uninstall.",
   "type": "module",
   "bin": {

package/scripts/find-by-marker.py

@@ -29,6 +29,8 @@ def _gh(args: list[str]) -> str:
     except subprocess.TimeoutExpired as exc:
         raise RuntimeError(
             f"gh api timed out after {GH_TIMEOUT_SECONDS}s") from exc
+    except OSError as exc:
+        raise RuntimeError(f"gh CLI unavailable: {exc.strerror or exc}") from exc
     if result.returncode != 0:
         raise RuntimeError(result.stderr.strip() or "gh api failed")
     return result.stdout

package/scripts/test_marker_lib.py

@@ -149,6 +149,14 @@ class MarkerLookupTest(unittest.TestCase):
             with self.assertRaisesRegex(RuntimeError, "timed out after 30s"):
                 cli._gh(["api", "--paginate", "repos/example/repo/issues"])
 
+    def test_cli_classifies_a_missing_github_binary(self):
+        with patch.object(
+            cli.subprocess, "run",
+            side_effect=FileNotFoundError(2, "No such file or directory", "gh"),
+        ):
+            with self.assertRaisesRegex(RuntimeError, "gh CLI unavailable"):
+                cli._gh(["api", "--paginate", "repos/example/repo/issues"])
+
 
 if __name__ == "__main__":
     unittest.main()