@olegkoval/agent-skills 1.38.3 → 1.40.0

package/.github/copilot-instructions.md

@@ -36,6 +36,7 @@ Available reusable prompt files:
 - context-repo: .github/prompts/context-repo.prompt.md
 - add-to-my-skills: .github/prompts/add-to-my-skills.prompt.md
 - promptctl: .github/prompts/promptctl.prompt.md
+- veto-routing: .github/prompts/veto-routing.prompt.md
 - ai-tools-setup: .github/prompts/ai-tools-setup.prompt.md
 - self-critique: .github/prompts/self-critique.prompt.md
 - review-past-performance: .github/prompts/review-past-performance.prompt.md

package/.github/prompts/veto-routing.prompt.md

@@ -0,0 +1,65 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+description: "Use Veto to route or execute AI tasks across configured providers with explicit privacy, cost, transport, and output boundaries."
+---
+
+Use the olko:veto-routing skill.
+
+# Veto routing
+
+Use Veto as a model-selection and execution layer. It does not expand the
+user's authorization, validate generated output, or guarantee quality or cost.
+
+## Before a model call
+
+1. Confirm the CLI is available with `command -v veto`. Inside the Veto source
+   checkout, `go run ./cmd/veto` is an acceptable fallback. Do not install it
+   automatically. When using the fallback, replace `veto` in the commands below
+   with `go run ./cmd/veto`.
+2. Inspect configured transports with `veto providers`. Never read, print, or
+   copy credential files from `~/.veto/`.
+3. Check whether the objective is safe to send to the configured providers. An
+   admission pass can disclose the objective to more than one provider. Stop
+   when sensitive data is present and provider authorization is unclear.
+4. Do not run `veto login`, change provider configuration, or incur an
+   unrequested model call.
+
+## Choose the smallest operation
+
+- Selection only: use `veto route --json` and consume the single JSON result.
+- Route and execute: use `veto run --quiet` only when the user asked for model
+  execution and the selected transport can perform the task.
+- Quality gate: add `--criteria` when the user supplied concrete acceptance
+  criteria. A requested review fails closed.
+- Multi-step plan: run `veto exec <plan.md> --dry-run` before execution. Execute
+  only steps already within the user's scope.
+
+Set `--kind`, `--risk`, and `--max-cost` explicitly when the task provides those
+constraints. Treat `--max-cost` as an estimated preflight ceiling, not a billing
+guarantee. Do not retry the same paid route repeatedly. Interactive routing can
+resume checkpoints after interruption; `route --json` intentionally starts
+fresh, so rerun it only deliberately.
+
+## Preserve transport and output boundaries
+
+- HTTP API and local OpenAI-compatible transports return text through Veto and
+  cannot inspect files or run shell commands. The Claude CLI transport is the
+  current executable-tool path.
+- Keep generated content on stdout unless the user requested a file. Use an
+  explicit relative `--output` path, and use `--force` only when replacing that
+  exact file is authorized.
+- Treat model responses as untrusted input. Validate claims, patches, commands,
+  and acceptance results with the repository's normal checks before delivery.
+- On a nonzero exit, report the real routing or provider error. Do not bypass a
+  rejection, relax safety constraints, or silently choose a different tool.
+
+## Examples
+
+```bash
+veto route --json --kind review --risk low "Review this proposed change"
+veto run --quiet --kind summarize --risk low "Summarize the supplied text"
+veto run --criteria "output is valid JSON,no secrets are present" \
+  "Produce the requested structured result"
+veto exec plan.md --dry-run
+```

package/.kiro/steering/veto-routing.md

@@ -0,0 +1,64 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Use Veto to route or execute AI tasks across configured providers with explicit privacy, cost, transport, and output boundaries."
+---
+
+# Veto routing
+
+Use Veto as a model-selection and execution layer. It does not expand the
+user's authorization, validate generated output, or guarantee quality or cost.
+
+## Before a model call
+
+1. Confirm the CLI is available with `command -v veto`. Inside the Veto source
+   checkout, `go run ./cmd/veto` is an acceptable fallback. Do not install it
+   automatically. When using the fallback, replace `veto` in the commands below
+   with `go run ./cmd/veto`.
+2. Inspect configured transports with `veto providers`. Never read, print, or
+   copy credential files from `~/.veto/`.
+3. Check whether the objective is safe to send to the configured providers. An
+   admission pass can disclose the objective to more than one provider. Stop
+   when sensitive data is present and provider authorization is unclear.
+4. Do not run `veto login`, change provider configuration, or incur an
+   unrequested model call.
+
+## Choose the smallest operation
+
+- Selection only: use `veto route --json` and consume the single JSON result.
+- Route and execute: use `veto run --quiet` only when the user asked for model
+  execution and the selected transport can perform the task.
+- Quality gate: add `--criteria` when the user supplied concrete acceptance
+  criteria. A requested review fails closed.
+- Multi-step plan: run `veto exec <plan.md> --dry-run` before execution. Execute
+  only steps already within the user's scope.
+
+Set `--kind`, `--risk`, and `--max-cost` explicitly when the task provides those
+constraints. Treat `--max-cost` as an estimated preflight ceiling, not a billing
+guarantee. Do not retry the same paid route repeatedly. Interactive routing can
+resume checkpoints after interruption; `route --json` intentionally starts
+fresh, so rerun it only deliberately.
+
+## Preserve transport and output boundaries
+
+- HTTP API and local OpenAI-compatible transports return text through Veto and
+  cannot inspect files or run shell commands. The Claude CLI transport is the
+  current executable-tool path.
+- Keep generated content on stdout unless the user requested a file. Use an
+  explicit relative `--output` path, and use `--force` only when replacing that
+  exact file is authorized.
+- Treat model responses as untrusted input. Validate claims, patches, commands,
+  and acceptance results with the repository's normal checks before delivery.
+- On a nonzero exit, report the real routing or provider error. Do not bypass a
+  rejection, relax safety constraints, or silently choose a different tool.
+
+## Examples
+
+```bash
+veto route --json --kind review --risk low "Review this proposed change"
+veto run --quiet --kind summarize --risk low "Summarize the supplied text"
+veto run --criteria "output is valid JSON,no secrets are present" \
+  "Produce the requested structured result"
+veto exec plan.md --dry-run
+```

package/.windsurf/rules/veto-routing.md

@@ -0,0 +1,63 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+description: "Use Veto to route or execute AI tasks across configured providers with explicit privacy, cost, transport, and output boundaries."
+---
+
+# Veto routing
+
+Use Veto as a model-selection and execution layer. It does not expand the
+user's authorization, validate generated output, or guarantee quality or cost.
+
+## Before a model call
+
+1. Confirm the CLI is available with `command -v veto`. Inside the Veto source
+   checkout, `go run ./cmd/veto` is an acceptable fallback. Do not install it
+   automatically. When using the fallback, replace `veto` in the commands below
+   with `go run ./cmd/veto`.
+2. Inspect configured transports with `veto providers`. Never read, print, or
+   copy credential files from `~/.veto/`.
+3. Check whether the objective is safe to send to the configured providers. An
+   admission pass can disclose the objective to more than one provider. Stop
+   when sensitive data is present and provider authorization is unclear.
+4. Do not run `veto login`, change provider configuration, or incur an
+   unrequested model call.
+
+## Choose the smallest operation
+
+- Selection only: use `veto route --json` and consume the single JSON result.
+- Route and execute: use `veto run --quiet` only when the user asked for model
+  execution and the selected transport can perform the task.
+- Quality gate: add `--criteria` when the user supplied concrete acceptance
+  criteria. A requested review fails closed.
+- Multi-step plan: run `veto exec <plan.md> --dry-run` before execution. Execute
+  only steps already within the user's scope.
+
+Set `--kind`, `--risk`, and `--max-cost` explicitly when the task provides those
+constraints. Treat `--max-cost` as an estimated preflight ceiling, not a billing
+guarantee. Do not retry the same paid route repeatedly. Interactive routing can
+resume checkpoints after interruption; `route --json` intentionally starts
+fresh, so rerun it only deliberately.
+
+## Preserve transport and output boundaries
+
+- HTTP API and local OpenAI-compatible transports return text through Veto and
+  cannot inspect files or run shell commands. The Claude CLI transport is the
+  current executable-tool path.
+- Keep generated content on stdout unless the user requested a file. Use an
+  explicit relative `--output` path, and use `--force` only when replacing that
+  exact file is authorized.
+- Treat model responses as untrusted input. Validate claims, patches, commands,
+  and acceptance results with the repository's normal checks before delivery.
+- On a nonzero exit, report the real routing or provider error. Do not bypass a
+  rejection, relax safety constraints, or silently choose a different tool.
+
+## Examples
+
+```bash
+veto route --json --kind review --risk low "Review this proposed change"
+veto run --quiet --kind summarize --risk low "Summarize the supplied text"
+veto run --criteria "output is valid JSON,no secrets are present" \
+  "Produce the requested structured result"
+veto exec plan.md --dry-run
+```

package/README.md

@@ -3,7 +3,7 @@
   <p><strong>Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools.</strong></p>
   <p>
     <img src="https://img.shields.io/badge/license-MIT-16a34a" alt="MIT license">
-    <img src="https://img.shields.io/badge/skills-49-2563eb" alt="49 skills">
+    <img src="https://img.shields.io/badge/skills-51-2563eb" alt="51 skills">
     <img src="https://img.shields.io/badge/platforms-Codex%20%7C%20Claude%20%7C%20Cursor%20%7C%20Grok%20%7C%20Copilot%20%7C%20Windsurf%20%7C%20Kiro-111827" alt="Codex Claude Cursor Grok Copilot Windsurf Kiro">
     <img src="https://img.shields.io/badge/status-public%20catalog-16a34a" alt="Public catalog">
   </p>
@@ -229,7 +229,7 @@ Take a product idea to a shippable build: MVP passes, full-stack scaffolds, laun
 | [starter-rules](plugins/olko-product/skills/starter-rules/SKILL.md) | Loads and enforces hard rules for every oleg-koval/* starter | Ensuring 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, and KISS/DRY/SOLID |
 | [viral-launch](plugins/olko-product/skills/viral-launch/SKILL.md) | Sets up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops | Preparing a repo, product, open-source package, or creator tool for public launch |
 
-### olko-skill-meta (7)
+### olko-skill-meta (8)
 
 Author and maintain agent skills and the AI toolchain itself.
 
@@ -239,6 +239,7 @@ Author and maintain agent skills and the AI toolchain itself.
 | [add-to-my-skills](plugins/olko-skill-meta/skills/add-to-my-skills/SKILL.md) | Copies a newly created skill from another repo into this catalog, refreshes the README and generated manifests, then commits and pushes | Adding a skill you wrote elsewhere into this catalog |
 | [skill-budget-audit](plugins/olko-skill-meta/skills/skill-budget-audit/SKILL.md) | Diagnoses and fixes Claude Code's skill context budget overflow, identifies heavy plugin bundles that exceed the 2% budget | Skills failing to load or Claude hitting context limits from plugin bundles |
 | [promptctl](plugins/olko-skill-meta/skills/promptctl/SKILL.md) | Uses `promptctl` for reusable prompt templates, scoring, and workflow automation | A project needs prompt conventions, review, scoring, or reusable prompt workflows |
+| [veto-routing](plugins/olko-skill-meta/skills/veto-routing/SKILL.md) | Routes or executes AI tasks through Veto across configured providers while preserving privacy, cost, transport, and output boundaries | A task needs cost-aware multi-provider model selection, execution, fallback, or a machine-readable routing decision |
 | [ai-tools-setup](plugins/olko-skill-meta/skills/ai-tools-setup/SKILL.md) | Sets up, repairs, and reports on the RTK + ICM + Vox AI development toolkit, installs missing tools, fixes broken hooks and MCP config | Bootstrapping AI dev tools on a new machine or diagnosing broken integrations |
 | [relay](plugins/olko-skill-meta/skills/relay/SKILL.md) | Uses `claude-relay` to run long or rate-limit-prone tasks autonomously across subscription accounts | A task will outlive one session or hit rate limits partway through |
 | [shared-knowledge-artifact](plugins/olko-skill-meta/skills/shared-knowledge-artifact/SKILL.md) | Builds a shared, self-persisting knowledge ledger as a Claude Artifact, a private page that stores its own data, renders itself from it, and publishes new versions of itself so several agents read the same lessons and append to them | Giving multiple agents one place to learn from each other instead of repeating the same mistakes |

package/adapters/claude/olko-skill-meta/skills/veto-routing/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: veto-routing
+description: Use the Veto CLI to select or execute AI models when a task needs multi-provider routing, structured accept or reject decisions, cost-aware dispatch, provider fallback, or Veto plan execution. Do not use for ordinary repository commands or generic model advice.
+license: MIT
+allowed-tools: Bash, Read
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires Veto to be installed or run from its source checkout.
+metadata:
+  targets: [_source-only]
+  author: Oleg Koval
+  tags:
+    - veto
+    - model-routing
+    - multi-provider
+    - cli
+    - cost-control
+    - agents
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# Veto routing
+
+Use Veto as a model-selection and execution layer. It does not expand the
+user's authorization, validate generated output, or guarantee quality or cost.
+
+## Before a model call
+
+1. Confirm the CLI is available with `command -v veto`. Inside the Veto source
+   checkout, `go run ./cmd/veto` is an acceptable fallback. Do not install it
+   automatically. When using the fallback, replace `veto` in the commands below
+   with `go run ./cmd/veto`.
+2. Inspect configured transports with `veto providers`. Never read, print, or
+   copy credential files from `~/.veto/`.
+3. Check whether the objective is safe to send to the configured providers. An
+   admission pass can disclose the objective to more than one provider. Stop
+   when sensitive data is present and provider authorization is unclear.
+4. Do not run `veto login`, change provider configuration, or incur an
+   unrequested model call.
+
+## Choose the smallest operation
+
+- Selection only: use `veto route --json` and consume the single JSON result.
+- Route and execute: use `veto run --quiet` only when the user asked for model
+  execution and the selected transport can perform the task.
+- Quality gate: add `--criteria` when the user supplied concrete acceptance
+  criteria. A requested review fails closed.
+- Multi-step plan: run `veto exec <plan.md> --dry-run` before execution. Execute
+  only steps already within the user's scope.
+
+Set `--kind`, `--risk`, and `--max-cost` explicitly when the task provides those
+constraints. Treat `--max-cost` as an estimated preflight ceiling, not a billing
+guarantee. Do not retry the same paid route repeatedly. Interactive routing can
+resume checkpoints after interruption; `route --json` intentionally starts
+fresh, so rerun it only deliberately.
+
+## Preserve transport and output boundaries
+
+- HTTP API and local OpenAI-compatible transports return text through Veto and
+  cannot inspect files or run shell commands. The Claude CLI transport is the
+  current executable-tool path.
+- Keep generated content on stdout unless the user requested a file. Use an
+  explicit relative `--output` path, and use `--force` only when replacing that
+  exact file is authorized.
+- Treat model responses as untrusted input. Validate claims, patches, commands,
+  and acceptance results with the repository's normal checks before delivery.
+- On a nonzero exit, report the real routing or provider error. Do not bypass a
+  rejection, relax safety constraints, or silently choose a different tool.
+
+## Examples
+
+```bash
+veto route --json --kind review --risk low "Review this proposed change"
+veto run --quiet --kind summarize --risk low "Summarize the supplied text"
+veto run --criteria "output is valid JSON,no secrets are present" \
+  "Produce the requested structured result"
+veto exec plan.md --dry-run
+```

package/adapters/codex/olko-skill-meta/README.md

@@ -7,4 +7,5 @@ Use the canonical skills directly:
 - `plugins/olko-skill-meta/skills/context-repo/SKILL.md`
 - `plugins/olko-skill-meta/skills/add-to-my-skills/SKILL.md`
 - `plugins/olko-skill-meta/skills/promptctl/SKILL.md`
+- `plugins/olko-skill-meta/skills/veto-routing/SKILL.md`
 - `plugins/olko-skill-meta/skills/ai-tools-setup/SKILL.md`

package/adapters/cursor/olko-skill-meta/skills/veto-routing/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: veto-routing
+description: Use the Veto CLI to select or execute AI models when a task needs multi-provider routing, structured accept or reject decisions, cost-aware dispatch, provider fallback, or Veto plan execution. Do not use for ordinary repository commands or generic model advice.
+license: MIT
+allowed-tools: Bash, Read
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires Veto to be installed or run from its source checkout.
+metadata:
+  targets: [_source-only]
+  author: Oleg Koval
+  tags:
+    - veto
+    - model-routing
+    - multi-provider
+    - cli
+    - cost-control
+    - agents
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# Veto routing
+
+Use Veto as a model-selection and execution layer. It does not expand the
+user's authorization, validate generated output, or guarantee quality or cost.
+
+## Before a model call
+
+1. Confirm the CLI is available with `command -v veto`. Inside the Veto source
+   checkout, `go run ./cmd/veto` is an acceptable fallback. Do not install it
+   automatically. When using the fallback, replace `veto` in the commands below
+   with `go run ./cmd/veto`.
+2. Inspect configured transports with `veto providers`. Never read, print, or
+   copy credential files from `~/.veto/`.
+3. Check whether the objective is safe to send to the configured providers. An
+   admission pass can disclose the objective to more than one provider. Stop
+   when sensitive data is present and provider authorization is unclear.
+4. Do not run `veto login`, change provider configuration, or incur an
+   unrequested model call.
+
+## Choose the smallest operation
+
+- Selection only: use `veto route --json` and consume the single JSON result.
+- Route and execute: use `veto run --quiet` only when the user asked for model
+  execution and the selected transport can perform the task.
+- Quality gate: add `--criteria` when the user supplied concrete acceptance
+  criteria. A requested review fails closed.
+- Multi-step plan: run `veto exec <plan.md> --dry-run` before execution. Execute
+  only steps already within the user's scope.
+
+Set `--kind`, `--risk`, and `--max-cost` explicitly when the task provides those
+constraints. Treat `--max-cost` as an estimated preflight ceiling, not a billing
+guarantee. Do not retry the same paid route repeatedly. Interactive routing can
+resume checkpoints after interruption; `route --json` intentionally starts
+fresh, so rerun it only deliberately.
+
+## Preserve transport and output boundaries
+
+- HTTP API and local OpenAI-compatible transports return text through Veto and
+  cannot inspect files or run shell commands. The Claude CLI transport is the
+  current executable-tool path.
+- Keep generated content on stdout unless the user requested a file. Use an
+  explicit relative `--output` path, and use `--force` only when replacing that
+  exact file is authorized.
+- Treat model responses as untrusted input. Validate claims, patches, commands,
+  and acceptance results with the repository's normal checks before delivery.
+- On a nonzero exit, report the real routing or provider error. Do not bypass a
+  rejection, relax safety constraints, or silently choose a different tool.
+
+## Examples
+
+```bash
+veto route --json --kind review --risk low "Review this proposed change"
+veto run --quiet --kind summarize --risk low "Summarize the supplied text"
+veto run --criteria "output is valid JSON,no secrets are present" \
+  "Produce the requested structured result"
+veto exec plan.md --dry-run
+```

package/adapters/grok/olko-skill-meta/skills/veto-routing/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: veto-routing
+description: Use the Veto CLI to select or execute AI models when a task needs multi-provider routing, structured accept or reject decisions, cost-aware dispatch, provider fallback, or Veto plan execution. Do not use for ordinary repository commands or generic model advice.
+license: MIT
+allowed-tools: Bash, Read
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires Veto to be installed or run from its source checkout.
+metadata:
+  targets: [_source-only]
+  author: Oleg Koval
+  tags:
+    - veto
+    - model-routing
+    - multi-provider
+    - cli
+    - cost-control
+    - agents
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# Veto routing
+
+Use Veto as a model-selection and execution layer. It does not expand the
+user's authorization, validate generated output, or guarantee quality or cost.
+
+## Before a model call
+
+1. Confirm the CLI is available with `command -v veto`. Inside the Veto source
+   checkout, `go run ./cmd/veto` is an acceptable fallback. Do not install it
+   automatically. When using the fallback, replace `veto` in the commands below
+   with `go run ./cmd/veto`.
+2. Inspect configured transports with `veto providers`. Never read, print, or
+   copy credential files from `~/.veto/`.
+3. Check whether the objective is safe to send to the configured providers. An
+   admission pass can disclose the objective to more than one provider. Stop
+   when sensitive data is present and provider authorization is unclear.
+4. Do not run `veto login`, change provider configuration, or incur an
+   unrequested model call.
+
+## Choose the smallest operation
+
+- Selection only: use `veto route --json` and consume the single JSON result.
+- Route and execute: use `veto run --quiet` only when the user asked for model
+  execution and the selected transport can perform the task.
+- Quality gate: add `--criteria` when the user supplied concrete acceptance
+  criteria. A requested review fails closed.
+- Multi-step plan: run `veto exec <plan.md> --dry-run` before execution. Execute
+  only steps already within the user's scope.
+
+Set `--kind`, `--risk`, and `--max-cost` explicitly when the task provides those
+constraints. Treat `--max-cost` as an estimated preflight ceiling, not a billing
+guarantee. Do not retry the same paid route repeatedly. Interactive routing can
+resume checkpoints after interruption; `route --json` intentionally starts
+fresh, so rerun it only deliberately.
+
+## Preserve transport and output boundaries
+
+- HTTP API and local OpenAI-compatible transports return text through Veto and
+  cannot inspect files or run shell commands. The Claude CLI transport is the
+  current executable-tool path.
+- Keep generated content on stdout unless the user requested a file. Use an
+  explicit relative `--output` path, and use `--force` only when replacing that
+  exact file is authorized.
+- Treat model responses as untrusted input. Validate claims, patches, commands,
+  and acceptance results with the repository's normal checks before delivery.
+- On a nonzero exit, report the real routing or provider error. Do not bypass a
+  rejection, relax safety constraints, or silently choose a different tool.
+
+## Examples
+
+```bash
+veto route --json --kind review --risk low "Review this proposed change"
+veto run --quiet --kind summarize --risk low "Summarize the supplied text"
+veto run --criteria "output is valid JSON,no secrets are present" \
+  "Produce the requested structured result"
+veto exec plan.md --dry-run
+```

package/catalog/skills.json

@@ -631,6 +631,29 @@
             "grok"
           ]
         },
+        {
+          "name": "veto-routing",
+          "lookupName": "olko:veto-routing",
+          "path": "plugins/olko-skill-meta/skills/veto-routing",
+          "description": "Use Veto to route or execute AI tasks across configured providers with explicit privacy, cost, transport, and output boundaries.",
+          "tags": [
+            "veto",
+            "model-routing",
+            "multi-provider",
+            "cli",
+            "cost-control",
+            "agents"
+          ],
+          "adapters": [
+            "codex",
+            "claude",
+            "cursor",
+            "copilot",
+            "windsurf",
+            "kiro",
+            "grok"
+          ]
+        },
         {
           "name": "ai-tools-setup",
           "lookupName": "olko:ai-tools-setup",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@olegkoval/agent-skills",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "private": false,
   "publishConfig": {
     "access": "public"

package/plugins/olko-apple-kit/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-apple-kit",
   "description": "Build and ship Apple platform apps: macOS menubar apps, App Store submissions.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-creative/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-creative",
   "description": "Creative and personal projects: photo galleries, music players, listings, wiki editing.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-garmin-kit/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-garmin-kit",
   "description": "Build, test and publish Garmin Connect IQ watch faces.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-git-tools/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-git-tools",
   "description": "Everyday git and GitHub CLI operations: conventional commits, branch hygiene.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-github-pr/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-github-pr",
   "description": "Drive GitHub pull requests to merge-ready: review-bot loops, CI fixes, descriptions, dependency triage.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-obsidian/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-obsidian",
   "description": "Keep an Obsidian vault in sync with work: PR sync, task rollover, morning routine.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-product/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-product",
   "description": "Take a product idea to a shippable build: MVP passes, full-stack scaffolds, launch plans.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-reflection/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-reflection",
   "description": "Look back and improve: self-critique, retrospectives, performance review, rapid learning.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-release/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-release",
   "description": "Ship a release: semantic-release setup, changelogs, store listing copy, release-day routine.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-skill-meta/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-skill-meta",
   "description": "Author and maintain agent skills and the AI toolchain itself.",
-  "version": "1.38.3",
+  "version": "1.40.0",
   "author": {
     "name": "Oleg Koval"
   },