@olegkoval/agent-skills 1.41.0 → 1.41.2

package/README.md

@@ -342,7 +342,7 @@ When adding or changing a skill:
 
 ### Shared context store
 
-![How the agent context store works: the five resolution steps, the three skills that use the store, and the four states every run ends in](docs/assets/context-store-card.png)
+![How the agent context store works: the five resolution steps, the three skills that use the store, the four states every run ends in, and how the store is read](docs/assets/context-store-card.png)
 
 `retro-analysis` and `shared-knowledge-artifact` share one private GitHub repository,
 resolved through the `context-repo` skill the first time either one runs. It finds a

package/adapters/claude/olko-github-pr/skills/lekker-review/scripts/selftest.mjs

@@ -41,9 +41,17 @@ function liftConst(name) {
 }
 
 const preamble = [
-  liftConst('HARD_RULES'),
+  // HARD_RULES is absent from the current workflow.js: the allowlist went away
+  // with the exemption it gated. It is still lifted-with-a-fallback rather than
+  // dropped, because this suite must stay runnable against an OLDER workflow.js
+  // (see the target argument above) to prove it discriminates. Without the
+  // fallback the old file throws ReferenceError instead of reporting FAIL, and a
+  // suite that crashes on the pre-fix input has proved nothing.
+  (() => { try { return liftConst('HARD_RULES') } catch { return 'const HARD_RULES = []' } })(),
   (() => { try { return liftConst('SAME_ISSUE_LINE_WINDOW') } catch { return 'const SAME_ISSUE_LINE_WINDOW = 30' } })(),
   "const SEVERITY_RANK = { observation: 0, idiomatic: 1, important: 2, critical: 3 }",
+  // hardRuleCorroborated is likewise gone from the current file and kept in this
+  // list for the same reason: an older workflow.js calls it from isHardRule.
   ...['titleTokens', 'sameIssue', 'nearbyLines', 'spanWithinWindow', 'hardRuleCorroborated',
       'isHardRule', 'longest', 'mergeFindings', 'dedup', 'shouldVerify'].map(n => {
         try { return lift(n) } catch { return `function ${n}() { throw new Error('${n} absent from this workflow.js') }` }
@@ -98,46 +106,51 @@ check('different files never merge', dedup([
   { file: 'b.ts', line: 7, severity: 'critical', title: 'Off-by-one loop skips the first line', badCode: '', description: '' },
 ]).length, 2)
 
-console.log('\nhard rules: a tag must be corroborated to skip verification')
-// Regression: any agent could bypass the verifier by writing rule: "TS-1".
-// Observed live - a test-coverage finding and a comment-policy finding both did.
-check('TS-1 on a comment-policy finding is NOT exempt',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 6, title: 'Comment restates the function', badCode: '/** Sum a cart. */', description: 'a comment earns its place' }), false)
-check('TS-1 on a test-coverage finding is NOT exempt',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 8, title: 'No test coverage', badCode: 'for (let i = 1;', description: 'zero test files added' }), false)
-check('an unknown rule string is NOT exempt',
-  isHardRule({ rule: 'MADE-UP', file: 'a.ts', line: 1, title: 't', badCode: 'x as Foo', description: '' }), false)
-// TS-1 is judged on quoted code only: prose is full of `as` and `any`.
-check('the word "any" in PROSE alone is NOT exempt',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'fails on any cart with items', badCode: 'total += lines[i].price', description: 'any agent could trip this' }), false)
-check('the phrase "such as" in prose alone is NOT exempt',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'issue', badCode: 'const n = 1', description: 'a primitive such as String is used' }), false)
+// This section used to assert that a `rule` tag had to be corroborated against a
+// hardcoded HARD_RULES list before it could SKIP verification. That guard existed
+// because a fabricated tag could buy exemption. It is gone because the exemption
+// is gone: shouldVerify now returns true for every Critical and Important finding,
+// and a hard rule takes the verifier's rule-specific anchor and applicability path
+// instead of its runtime challenges, validated against the configured canonical
+// rules file. A hardcoded list also could not recognise a custom house rule, which
+// the current design supports on purpose.
+//
+// So the tag no longer buys a free pass; it selects a verification path. The
+// predicate is correspondingly narrow: does this finding claim a rule at all.
+console.log('\nhard rules: the tag selects a verification path, it does not skip one')
+// Regression, still worth holding: a finding with no rule tag must never be
+// treated as one. That is what routes it to the runtime challenges.
+check('no rule tag is not a hard rule',
+  isHardRule({ file: 'a.ts', line: 1, title: 't', badCode: 'x as Foo', description: '' }), false)
+check('an empty rule tag is not a hard rule',
+  isHardRule({ rule: '', file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), false)
+check('a whitespace-only rule tag is not a hard rule',
+  isHardRule({ rule: '   ', file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), false)
+check('a non-string rule tag is not a hard rule',
+  isHardRule({ rule: 1, file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), false)
 
-console.log('\nhard rules: genuine violations must STILL be exempt')
-check('TS-1 with a real cast',   isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'cast', badCode: 'const x = y as Foo;', description: '' }), true)
-check('TS-1 with a real any',    isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'any',  badCode: 'function f(x: any) {}', description: '' }), true)
-check('TS-2 with a .js path',    isHardRule({ rule: 'TS-2', file: 'web/thing.js', line: 1, title: 'js added', badCode: '', description: '' }), true)
-check('GQL-1 with a nodes query',isHardRule({ rule: 'GQL-1', file: 'q.graphql', line: 1, title: 'no pageInfo', badCode: 'products { nodes { id } }', description: '' }), true)
-check('PR-1 anchored on the PR title', isHardRule({ rule: 'PR-1', file: 'PR title', line: 1, title: 'missing prefix', badCode: '', description: '' }), true)
-// A cast to a lowercase built-in is as much a TS-1 violation as a cast to a
-// named type. Missing it sent a genuine hard rule to a verifier that cannot
-// answer a policy claim, where it could be dropped.
-for (const cast of ['x as string', 'x as number', 'x as unknown as Foo', 'x as const', 'x as boolean']) {
-  check(`TS-1 corroborated by \`${cast}\``,
-    isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'cast', badCode: cast, description: '' }), true)
+console.log('\nhard rules: built-in and custom tags both route to rule-specific verification')
+for (const rule of ['TS-1', 'TS-2', 'GQL-1', 'PR-1']) {
+  check(`built-in ${rule} is a hard rule`,
+    isHardRule({ rule, file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), true)
 }
-check('TS-1 corroborated by an any annotation',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'any', badCode: 'function f(x: any) {}', description: '' }), true)
-check('TS-1 corroborated by an any[] ',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'any', badCode: 'const xs: any[] = []', description: '' }), true)
+// A house rule defined in the operator's canonical rules file cannot be known to
+// this workflow. Rejecting it here is what a hardcoded list did, and it silently
+// disabled every custom rule a deployment configured.
+check('a custom house rule is a hard rule',
+  isHardRule({ rule: 'SEC-1', file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), true)
 
-console.log('\nverification scope by depth')
+console.log('\nverification scope: depth controls breadth, never the trust bar')
 const crit = { severity: 'critical' }, imp = { severity: 'important' }, obs = { severity: 'observation' }
-check('scan verifies nothing',            [crit, imp, obs].map(f => shouldVerify(f, 'scan')),   [false, false, false])
-check('medium verifies criticals only',   [crit, imp, obs].map(f => shouldVerify(f, 'medium')), [true, false, false])
-check('deep verifies crit + important',   [crit, imp, obs].map(f => shouldVerify(f, 'deep')),   [true, true, false])
-check('a corroborated hard rule is never verified',
-  shouldVerify({ severity: 'critical', rule: 'TS-2', file: 'x.js', badCode: '', description: '', title: '' }, 'deep'), false)
+// shouldVerify takes one argument now. Depth used to be able to switch verification
+// off entirely, which meant a scan-depth review shipped unverified Criticals.
+check('shouldVerify takes the finding alone', shouldVerify.length, 1)
+check('critical and important are verified, observation is not',
+  [crit, imp, obs].map(f => shouldVerify(f)), [true, true, false])
+check('a hard rule is NOT exempt from verification',
+  shouldVerify({ severity: 'critical', rule: 'TS-2', file: 'x.js', badCode: '', description: '', title: '' }), true)
+check('a custom hard rule is NOT exempt either',
+  shouldVerify({ severity: 'critical', rule: 'SEC-1', file: 'x.ts', badCode: '', description: '', title: '' }), true)
 
 // Per-host model routing is optional: a deployment may pin models per host via
 // a MODEL_TABLE, or leave every agent() call to name its own model. Test it

package/docs/agent-context-store.md

@@ -229,6 +229,52 @@ into it:
   where they do not conflict with this contract. It cannot override lease acquisition,
   validation, append-only writes, secret handling, or the private-repository requirement.
 
+## Reading the store
+
+Everything above is the write side, and it is enforced: a lease, a validator, and CI
+that runs the validator again on push. The read side had none of that. For a while the
+only instruction to read the ledger was one sentence in `AGENTS.md`, which is a rule an
+agent has to remember rather than a mechanism. It did not hold. Two notes written on
+2026-08-25 described failures that both recurred by 2026-08-31: one about stating the
+denominator behind a percentage, one about cache reads dominating a long-session bill.
+Recording a lesson and delivering it are different jobs.
+
+The store therefore ships a reader, `recipes/tools/ledger-index`, built on the shape
+that already works for per-user memory: a cheap index is always in context, and the
+body is fetched on demand. The index is titles only, roughly 1.9k tokens for 84 notes,
+grouped by scope with traps first. The ledger itself is around 50KB and does not belong
+in every session.
+
+```text
+ledger-index                          the index, grouped by scope
+ledger-index --show n41               one note in full, body and Why
+ledger-index --kind trap --scope shell
+ledger-index --count
+```
+
+It resolves the ledger through the same pointer `context-repo` writes, so a machine
+that has resolved the store once needs no further configuration. An explicitly named
+`--ledger` or `LEDGER_PATH` that does not exist is an error rather than a fallback:
+silently reading a different ledger than the one you asked for is the failure this
+whole document exists to prevent.
+
+Hosts wire it in their own way and neither owns the format. A Claude `SessionStart`
+hook injects the index once per session; a Codex prompt shells out to the same binary.
+The reference hook is `recipes/hooks/ledger-index.sh`, which prints nothing and exits 0
+when the store is absent, so it can never fail a session.
+
+The index states its own horizon. It reads from disk and never fetches, because a
+session start is the wrong place for a network call, so the header carries the commit,
+its age in days, and a plain statement that a newer commit may exist upstream. Past
+three days it prints the `pull --rebase` command for that clone. Age of `HEAD` conflates
+a quiet repository with a checkout that is behind, and only a fetch separates them, so
+the limit is stated rather than implied.
+
+One consequence is worth making explicit. The fixed clone path is not a convention, it
+is the point: a second working copy of the store is the copy nothing keeps current, and
+it will be the one an index or an `AGENTS.md` symlink ends up reading. Resolve through
+the pointer and keep one checkout.
+
 ## What is never committed
 
 Raw session content, tokens, private prompts, and customer data never go into the

package/docs/assets/context-store-card.html

@@ -367,6 +367,30 @@
     <p class="proof-line">A push that appears to succeed is <strong>not proof</strong>. <strong>CREATED</strong> is claimed only after a <strong>fresh read-back agrees</strong>.</p>
   </section>
 
+  <section class="state-strip" aria-labelledby="read-title">
+    <p class="strip-label" id="read-title">AND ONE WAY IT IS READ</p>
+    <div class="state-row">
+      <div class="state-item">
+        <p class="state-name">LEDGER-INDEX</p>
+        <p class="state-detail">titles only, grouped by scope, traps first</p>
+      </div>
+      <div class="state-item">
+        <p class="state-name">--SHOW n41</p>
+        <p class="state-detail">one note in full, body and Why</p>
+      </div>
+      <div class="state-item">
+        <p class="state-name">--KIND --SCOPE</p>
+        <p class="state-detail">narrow it to the task in front of you</p>
+      </div>
+      <div class="state-item">
+        <p class="state-name">DATED HEADER</p>
+        <p class="state-detail">read from disk, no fetch, age stated</p>
+      </div>
+      <p class="state-copy">A cheap index is always in context; the body is fetched on demand. The ledger never enters a session whole.</p>
+    </div>
+    <p class="proof-line">A rule that is <strong>recorded but not delivered</strong> is a diary. The index is a <strong>table of contents</strong>, never the rule itself.</p>
+  </section>
+
   <footer class="closing-band">
     <p class="closing-line">One consented store gives every skill durable context with explicit verification.</p>
     <div class="metadata-line">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@olegkoval/agent-skills",
-  "version": "1.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-github-pr/skills/lekker-review/scripts/selftest.mjs

@@ -41,9 +41,17 @@ function liftConst(name) {
 }
 
 const preamble = [
-  liftConst('HARD_RULES'),
+  // HARD_RULES is absent from the current workflow.js: the allowlist went away
+  // with the exemption it gated. It is still lifted-with-a-fallback rather than
+  // dropped, because this suite must stay runnable against an OLDER workflow.js
+  // (see the target argument above) to prove it discriminates. Without the
+  // fallback the old file throws ReferenceError instead of reporting FAIL, and a
+  // suite that crashes on the pre-fix input has proved nothing.
+  (() => { try { return liftConst('HARD_RULES') } catch { return 'const HARD_RULES = []' } })(),
   (() => { try { return liftConst('SAME_ISSUE_LINE_WINDOW') } catch { return 'const SAME_ISSUE_LINE_WINDOW = 30' } })(),
   "const SEVERITY_RANK = { observation: 0, idiomatic: 1, important: 2, critical: 3 }",
+  // hardRuleCorroborated is likewise gone from the current file and kept in this
+  // list for the same reason: an older workflow.js calls it from isHardRule.
   ...['titleTokens', 'sameIssue', 'nearbyLines', 'spanWithinWindow', 'hardRuleCorroborated',
       'isHardRule', 'longest', 'mergeFindings', 'dedup', 'shouldVerify'].map(n => {
         try { return lift(n) } catch { return `function ${n}() { throw new Error('${n} absent from this workflow.js') }` }
@@ -98,46 +106,51 @@ check('different files never merge', dedup([
   { file: 'b.ts', line: 7, severity: 'critical', title: 'Off-by-one loop skips the first line', badCode: '', description: '' },
 ]).length, 2)
 
-console.log('\nhard rules: a tag must be corroborated to skip verification')
-// Regression: any agent could bypass the verifier by writing rule: "TS-1".
-// Observed live - a test-coverage finding and a comment-policy finding both did.
-check('TS-1 on a comment-policy finding is NOT exempt',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 6, title: 'Comment restates the function', badCode: '/** Sum a cart. */', description: 'a comment earns its place' }), false)
-check('TS-1 on a test-coverage finding is NOT exempt',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 8, title: 'No test coverage', badCode: 'for (let i = 1;', description: 'zero test files added' }), false)
-check('an unknown rule string is NOT exempt',
-  isHardRule({ rule: 'MADE-UP', file: 'a.ts', line: 1, title: 't', badCode: 'x as Foo', description: '' }), false)
-// TS-1 is judged on quoted code only: prose is full of `as` and `any`.
-check('the word "any" in PROSE alone is NOT exempt',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'fails on any cart with items', badCode: 'total += lines[i].price', description: 'any agent could trip this' }), false)
-check('the phrase "such as" in prose alone is NOT exempt',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'issue', badCode: 'const n = 1', description: 'a primitive such as String is used' }), false)
+// This section used to assert that a `rule` tag had to be corroborated against a
+// hardcoded HARD_RULES list before it could SKIP verification. That guard existed
+// because a fabricated tag could buy exemption. It is gone because the exemption
+// is gone: shouldVerify now returns true for every Critical and Important finding,
+// and a hard rule takes the verifier's rule-specific anchor and applicability path
+// instead of its runtime challenges, validated against the configured canonical
+// rules file. A hardcoded list also could not recognise a custom house rule, which
+// the current design supports on purpose.
+//
+// So the tag no longer buys a free pass; it selects a verification path. The
+// predicate is correspondingly narrow: does this finding claim a rule at all.
+console.log('\nhard rules: the tag selects a verification path, it does not skip one')
+// Regression, still worth holding: a finding with no rule tag must never be
+// treated as one. That is what routes it to the runtime challenges.
+check('no rule tag is not a hard rule',
+  isHardRule({ file: 'a.ts', line: 1, title: 't', badCode: 'x as Foo', description: '' }), false)
+check('an empty rule tag is not a hard rule',
+  isHardRule({ rule: '', file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), false)
+check('a whitespace-only rule tag is not a hard rule',
+  isHardRule({ rule: '   ', file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), false)
+check('a non-string rule tag is not a hard rule',
+  isHardRule({ rule: 1, file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), false)
 
-console.log('\nhard rules: genuine violations must STILL be exempt')
-check('TS-1 with a real cast',   isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'cast', badCode: 'const x = y as Foo;', description: '' }), true)
-check('TS-1 with a real any',    isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'any',  badCode: 'function f(x: any) {}', description: '' }), true)
-check('TS-2 with a .js path',    isHardRule({ rule: 'TS-2', file: 'web/thing.js', line: 1, title: 'js added', badCode: '', description: '' }), true)
-check('GQL-1 with a nodes query',isHardRule({ rule: 'GQL-1', file: 'q.graphql', line: 1, title: 'no pageInfo', badCode: 'products { nodes { id } }', description: '' }), true)
-check('PR-1 anchored on the PR title', isHardRule({ rule: 'PR-1', file: 'PR title', line: 1, title: 'missing prefix', badCode: '', description: '' }), true)
-// A cast to a lowercase built-in is as much a TS-1 violation as a cast to a
-// named type. Missing it sent a genuine hard rule to a verifier that cannot
-// answer a policy claim, where it could be dropped.
-for (const cast of ['x as string', 'x as number', 'x as unknown as Foo', 'x as const', 'x as boolean']) {
-  check(`TS-1 corroborated by \`${cast}\``,
-    isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'cast', badCode: cast, description: '' }), true)
+console.log('\nhard rules: built-in and custom tags both route to rule-specific verification')
+for (const rule of ['TS-1', 'TS-2', 'GQL-1', 'PR-1']) {
+  check(`built-in ${rule} is a hard rule`,
+    isHardRule({ rule, file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), true)
 }
-check('TS-1 corroborated by an any annotation',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'any', badCode: 'function f(x: any) {}', description: '' }), true)
-check('TS-1 corroborated by an any[] ',
-  isHardRule({ rule: 'TS-1', file: 'a.ts', line: 1, title: 'any', badCode: 'const xs: any[] = []', description: '' }), true)
+// A house rule defined in the operator's canonical rules file cannot be known to
+// this workflow. Rejecting it here is what a hardcoded list did, and it silently
+// disabled every custom rule a deployment configured.
+check('a custom house rule is a hard rule',
+  isHardRule({ rule: 'SEC-1', file: 'a.ts', line: 1, title: 't', badCode: '', description: '' }), true)
 
-console.log('\nverification scope by depth')
+console.log('\nverification scope: depth controls breadth, never the trust bar')
 const crit = { severity: 'critical' }, imp = { severity: 'important' }, obs = { severity: 'observation' }
-check('scan verifies nothing',            [crit, imp, obs].map(f => shouldVerify(f, 'scan')),   [false, false, false])
-check('medium verifies criticals only',   [crit, imp, obs].map(f => shouldVerify(f, 'medium')), [true, false, false])
-check('deep verifies crit + important',   [crit, imp, obs].map(f => shouldVerify(f, 'deep')),   [true, true, false])
-check('a corroborated hard rule is never verified',
-  shouldVerify({ severity: 'critical', rule: 'TS-2', file: 'x.js', badCode: '', description: '', title: '' }, 'deep'), false)
+// shouldVerify takes one argument now. Depth used to be able to switch verification
+// off entirely, which meant a scan-depth review shipped unverified Criticals.
+check('shouldVerify takes the finding alone', shouldVerify.length, 1)
+check('critical and important are verified, observation is not',
+  [crit, imp, obs].map(f => shouldVerify(f)), [true, true, false])
+check('a hard rule is NOT exempt from verification',
+  shouldVerify({ severity: 'critical', rule: 'TS-2', file: 'x.js', badCode: '', description: '', title: '' }), true)
+check('a custom hard rule is NOT exempt either',
+  shouldVerify({ severity: 'critical', rule: 'SEC-1', file: 'x.ts', badCode: '', description: '', title: '' }), true)
 
 // Per-host model routing is optional: a deployment may pin models per host via
 // a MODEL_TABLE, or leave every agent() call to name its own model. Test it

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.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "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.41.0",
+  "version": "1.41.2",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-web-ops/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-web-ops",
   "description": "Operate a website: WAF rules, search console audits, analytics bootstrap, docs indexes.",
-  "version": "1.41.0",
+  "version": "1.41.2",
   "author": {
     "name": "Oleg Koval"
   },