@olegkoval/agent-skills 1.59.1 → 1.59.3

package/.github/copilot-instructions.md

@@ -31,6 +31,7 @@ Available reusable prompt files:
 - release-day: .github/prompts/release-day.prompt.md
 - changelog-generator: .github/prompts/changelog-generator.prompt.md
 - store-listing-copy: .github/prompts/store-listing-copy.prompt.md
+- ingest-publication-slice: .github/prompts/ingest-publication-slice.prompt.md
 - product-builder: .github/prompts/product-builder.prompt.md
 - mvp-oneshot: .github/prompts/mvp-oneshot.prompt.md
 - ux-ui-audit-loop: .github/prompts/ux-ui-audit-loop.prompt.md

package/.github/prompts/ingest-publication-slice.prompt.md

@@ -0,0 +1,43 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+description: "Build and verify a small end-to-end publication path for validated ingested data, including atomic persistence, read fallback, and static artifact precedence."
+---
+
+Use the olko:ingest-publication-slice skill.
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence.*
+
+# Ingest Publication Slice
+
+Use this workflow when an ingest pipeline must make a validated record available immediately while a static or cached publication artifact may be generated later.
+
+## Define the contract
+
+Before changing code, read the repository instructions and trace the current path from ingest entry point through validation, job completion, persistence, request handling, and static artifact generation. Record existing invariants and preserve unrelated work.
+
+Write acceptance criteria for one complete slice:
+
+- Only a completed, validated active dataset can be published.
+- The persistent publication record and terminal ingest state commit atomically.
+- The canonical read path can serve from the persistent record when no static artifact exists.
+- A static artifact remains authoritative once present, if that is the established product contract.
+- Retries are idempotent, and collisions, invalid states, hidden records, and takedowns cannot publish.
+
+Adapt these criteria to the actual product contract. Do not invent a static-artifact precedence rule if the system has none.
+
+## Implement test-first
+
+Use the repository's required test command and style. Add focused failing tests before implementation for:
+
+1. A valid ingest publishes the record and terminal state together.
+2. A failure between writes leaves neither half committed.
+3. The canonical read path uses the persisted record when the artifact is absent.
+4. The artifact wins when both sources exist, when precedence is required.
+5. Repeated delivery is safe and invalid, hidden, colliding, or withdrawn records stay unpublished.
+
+Test the production boundary and transaction behavior, not only helper functions. Keep the change to the smallest vertical slice; avoid unrelated schema or routing refactors.
+
+## Verify the composed path
+
+Run the focused tests, then the repository's required broader checks. Inspect the final diff and trace the completed path again from ingest through the canonical response. Confirm behavior for retries, partial failures, and transitions from no artifact to artifact present. Report any unavailable integration or deployment evidence explicitly.

package/.kiro/steering/ingest-publication-slice.md

@@ -0,0 +1,42 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Build and verify a small end-to-end publication path for validated ingested data, including atomic persistence, read fallback, and static artifact precedence."
+---
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence.*
+
+# Ingest Publication Slice
+
+Use this workflow when an ingest pipeline must make a validated record available immediately while a static or cached publication artifact may be generated later.
+
+## Define the contract
+
+Before changing code, read the repository instructions and trace the current path from ingest entry point through validation, job completion, persistence, request handling, and static artifact generation. Record existing invariants and preserve unrelated work.
+
+Write acceptance criteria for one complete slice:
+
+- Only a completed, validated active dataset can be published.
+- The persistent publication record and terminal ingest state commit atomically.
+- The canonical read path can serve from the persistent record when no static artifact exists.
+- A static artifact remains authoritative once present, if that is the established product contract.
+- Retries are idempotent, and collisions, invalid states, hidden records, and takedowns cannot publish.
+
+Adapt these criteria to the actual product contract. Do not invent a static-artifact precedence rule if the system has none.
+
+## Implement test-first
+
+Use the repository's required test command and style. Add focused failing tests before implementation for:
+
+1. A valid ingest publishes the record and terminal state together.
+2. A failure between writes leaves neither half committed.
+3. The canonical read path uses the persisted record when the artifact is absent.
+4. The artifact wins when both sources exist, when precedence is required.
+5. Repeated delivery is safe and invalid, hidden, colliding, or withdrawn records stay unpublished.
+
+Test the production boundary and transaction behavior, not only helper functions. Keep the change to the smallest vertical slice; avoid unrelated schema or routing refactors.
+
+## Verify the composed path
+
+Run the focused tests, then the repository's required broader checks. Inspect the final diff and trace the completed path again from ingest through the canonical response. Confirm behavior for retries, partial failures, and transitions from no artifact to artifact present. Report any unavailable integration or deployment evidence explicitly.

package/.windsurf/rules/ingest-publication-slice.md

@@ -0,0 +1,41 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+description: "Build and verify a small end-to-end publication path for validated ingested data, including atomic persistence, read fallback, and static artifact precedence."
+---
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence.*
+
+# Ingest Publication Slice
+
+Use this workflow when an ingest pipeline must make a validated record available immediately while a static or cached publication artifact may be generated later.
+
+## Define the contract
+
+Before changing code, read the repository instructions and trace the current path from ingest entry point through validation, job completion, persistence, request handling, and static artifact generation. Record existing invariants and preserve unrelated work.
+
+Write acceptance criteria for one complete slice:
+
+- Only a completed, validated active dataset can be published.
+- The persistent publication record and terminal ingest state commit atomically.
+- The canonical read path can serve from the persistent record when no static artifact exists.
+- A static artifact remains authoritative once present, if that is the established product contract.
+- Retries are idempotent, and collisions, invalid states, hidden records, and takedowns cannot publish.
+
+Adapt these criteria to the actual product contract. Do not invent a static-artifact precedence rule if the system has none.
+
+## Implement test-first
+
+Use the repository's required test command and style. Add focused failing tests before implementation for:
+
+1. A valid ingest publishes the record and terminal state together.
+2. A failure between writes leaves neither half committed.
+3. The canonical read path uses the persisted record when the artifact is absent.
+4. The artifact wins when both sources exist, when precedence is required.
+5. Repeated delivery is safe and invalid, hidden, colliding, or withdrawn records stay unpublished.
+
+Test the production boundary and transaction behavior, not only helper functions. Keep the change to the smallest vertical slice; avoid unrelated schema or routing refactors.
+
+## Verify the composed path
+
+Run the focused tests, then the repository's required broader checks. Inspect the final diff and trace the completed path again from ingest through the canonical response. Confirm behavior for retries, partial failures, and transitions from no artifact to artifact present. Report any unavailable integration or deployment evidence explicitly.

package/README.md

@@ -32,7 +32,7 @@ These skills are opinionated by design. They encode working defaults, preferred
 
 ## Start here
 
-Ten skills across different plugins that cover the most common jobs. Full catalog is below.
+Eleven skills across different plugins that cover the most common jobs. Full catalog is below.
 
 | What you're doing | Skill | Key principle |
 |--------------------|-------|----------------|
@@ -43,6 +43,7 @@ Ten skills across different plugins that cover the most common jobs. Full catalo
 | Closing out a finished piece of work | [wrap-up](plugins/olko-reflection/skills/wrap-up/SKILL.md) (`olko:wrap-up`) | Verify the objective and propose safe cleanup |
 | Running a recurring engineering retrospective | [retro-analysis](plugins/olko-reflection/skills/retro-analysis/SKILL.md) (`olko:retro-analysis`) | Evidence from delivery and code, not vibes |
 | Going from idea to a shippable MVP | [mvp-oneshot](plugins/olko-product/skills/mvp-oneshot/SKILL.md) (`olko:mvp-oneshot`) | Scope for one week, not the whole roadmap |
+| Publishing validated ingested data immediately | [ingest-publication-slice](plugins/olko-product/skills/ingest-publication-slice/SKILL.md) (`olko:ingest-publication-slice`) | Test the atomic write, fallback read, and artifact precedence end to end |
 | Ramping up on an unfamiliar codebase fast | [crash-course](plugins/olko-reflection/skills/crash-course/SKILL.md) (`olko:crash-course`) | Source-grounded, timed, and testable |
 | Cutting a release from ready-code to submitted-build | [release-day](plugins/olko-release/skills/release-day/SKILL.md) (`olko:release-day`) | One orchestrated pass, not five manual steps |
 | Starting the workday with the queue synced | [morning-routine](plugins/olko-obsidian/skills/morning-routine/SKILL.md) (`olko:morning-routine`) | Chain the routines instead of running them separately |
@@ -264,7 +265,7 @@ Ship a release: semantic-release setup, changelogs, store listing copy, release-
 | [changelog-generator](plugins/olko-release/skills/changelog-generator/SKILL.md) | Transforms git commits into polished user-facing changelogs by categorising changes and rewriting technical commit messages | Preparing release notes, a CHANGELOG entry, or "what changed since the last release"; for setting up the release pipeline itself use semantic-release-beta |
 | [store-listing-copy](plugins/olko-release/skills/store-listing-copy/SKILL.md) | Generates platform-validated App Store, Google Play, and Connect IQ store listing copy (title, subtitle, description, what's new, keywords) from a git changelog | Writing store copy before submitting to apple-store-submit or the garmin-watchface store workflow |
 
-### olko-product (6)
+### olko-product (7)
 
 Take a product idea to a shippable build: MVP passes, full-stack scaffolds, UX/UI quality loops, launch plans.
 
@@ -275,6 +276,7 @@ Take a product idea to a shippable build: MVP passes, full-stack scaffolds, UX/U
 | [ux-ui-audit-loop](plugins/olko-product/skills/ux-ui-audit-loop/SKILL.md) | Audits and improves a web UI through browser evidence, severity triage, minimal fixes, and before/after verification | The user says "audit this UI", "fix the UX", "review this page visually", "make this page polished", or asks for an autonomous screenshot-and-fix loop |
 | [frontend-direction](plugins/olko-product/skills/frontend-direction/SKILL.md) | Chooses a distinctive, coherent visual direction and source-backed components before writing frontend code | Building a new page or a substantial UI redesign, or making an interface less generic; small fixes keep the existing design |
 | [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 |
+| [ingest-publication-slice](plugins/olko-product/skills/ingest-publication-slice/SKILL.md) | Builds a test-first ingest-to-publication path with atomic persistence, read fallback, and static artifact precedence | Publishing validated ingested data before a static artifact exists |
 | [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, or package for public launch ("prep for Product Hunt", "write the launch post", "make this shareable"); for building the thing itself use mvp-oneshot or product-builder |
 
 ### olko-skill-meta (8)

package/adapters/claude/olko-github-pr/skills/lekker-review/SKILL.md

@@ -29,6 +29,7 @@ description: >
   the PR", provides a GitHub PR URL, or asks for a pull request review in any
   form.
 license: MIT
+model: sonnet
 allowed-tools: Bash, Read, Write, Edit, Agent, Workflow, AskUserQuestion, Artifact, spawn_agent, wait_agent, followup_task, send_message, interrupt_agent, list_agents
 compatibility: >
   Claude Code and OpenAI Codex. Claude uses Workflow/Agent/Artifact. Codex uses

package/adapters/claude/olko-product/skills/ingest-publication-slice/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: ingest-publication-slice
+description: Build and verify a small end-to-end publication path for validated ingested data, including atomic persistence, read fallback, and static artifact precedence.
+source: weekly-pattern-learner
+source_reason: "Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence."
+source_date: "2026-10-24"
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence.*
+
+# Ingest Publication Slice
+
+Use this workflow when an ingest pipeline must make a validated record available immediately while a static or cached publication artifact may be generated later.
+
+## Define the contract
+
+Before changing code, read the repository instructions and trace the current path from ingest entry point through validation, job completion, persistence, request handling, and static artifact generation. Record existing invariants and preserve unrelated work.
+
+Write acceptance criteria for one complete slice:
+
+- Only a completed, validated active dataset can be published.
+- The persistent publication record and terminal ingest state commit atomically.
+- The canonical read path can serve from the persistent record when no static artifact exists.
+- A static artifact remains authoritative once present, if that is the established product contract.
+- Retries are idempotent, and collisions, invalid states, hidden records, and takedowns cannot publish.
+
+Adapt these criteria to the actual product contract. Do not invent a static-artifact precedence rule if the system has none.
+
+## Implement test-first
+
+Use the repository's required test command and style. Add focused failing tests before implementation for:
+
+1. A valid ingest publishes the record and terminal state together.
+2. A failure between writes leaves neither half committed.
+3. The canonical read path uses the persisted record when the artifact is absent.
+4. The artifact wins when both sources exist, when precedence is required.
+5. Repeated delivery is safe and invalid, hidden, colliding, or withdrawn records stay unpublished.
+
+Test the production boundary and transaction behavior, not only helper functions. Keep the change to the smallest vertical slice; avoid unrelated schema or routing refactors.
+
+## Verify the composed path
+
+Run the focused tests, then the repository's required broader checks. Inspect the final diff and trace the completed path again from ingest through the canonical response. Confirm behavior for retries, partial failures, and transitions from no artifact to artifact present. Report any unavailable integration or deployment evidence explicitly.

package/adapters/codex/olko-product/README.md

@@ -4,6 +4,7 @@
 
 Use the canonical skills directly:
 
+- `plugins/olko-product/skills/ingest-publication-slice/SKILL.md`
 - `plugins/olko-product/skills/product-builder/SKILL.md`
 - `plugins/olko-product/skills/mvp-oneshot/SKILL.md`
 - `plugins/olko-product/skills/ux-ui-audit-loop/SKILL.md`

package/adapters/cursor/olko-product/skills/ingest-publication-slice/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: ingest-publication-slice
+description: Build and verify a small end-to-end publication path for validated ingested data, including atomic persistence, read fallback, and static artifact precedence.
+source: weekly-pattern-learner
+source_reason: "Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence."
+source_date: "2026-10-24"
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence.*
+
+# Ingest Publication Slice
+
+Use this workflow when an ingest pipeline must make a validated record available immediately while a static or cached publication artifact may be generated later.
+
+## Define the contract
+
+Before changing code, read the repository instructions and trace the current path from ingest entry point through validation, job completion, persistence, request handling, and static artifact generation. Record existing invariants and preserve unrelated work.
+
+Write acceptance criteria for one complete slice:
+
+- Only a completed, validated active dataset can be published.
+- The persistent publication record and terminal ingest state commit atomically.
+- The canonical read path can serve from the persistent record when no static artifact exists.
+- A static artifact remains authoritative once present, if that is the established product contract.
+- Retries are idempotent, and collisions, invalid states, hidden records, and takedowns cannot publish.
+
+Adapt these criteria to the actual product contract. Do not invent a static-artifact precedence rule if the system has none.
+
+## Implement test-first
+
+Use the repository's required test command and style. Add focused failing tests before implementation for:
+
+1. A valid ingest publishes the record and terminal state together.
+2. A failure between writes leaves neither half committed.
+3. The canonical read path uses the persisted record when the artifact is absent.
+4. The artifact wins when both sources exist, when precedence is required.
+5. Repeated delivery is safe and invalid, hidden, colliding, or withdrawn records stay unpublished.
+
+Test the production boundary and transaction behavior, not only helper functions. Keep the change to the smallest vertical slice; avoid unrelated schema or routing refactors.
+
+## Verify the composed path
+
+Run the focused tests, then the repository's required broader checks. Inspect the final diff and trace the completed path again from ingest through the canonical response. Confirm behavior for retries, partial failures, and transitions from no artifact to artifact present. Report any unavailable integration or deployment evidence explicitly.

package/adapters/grok/olko-product/skills/ingest-publication-slice/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: ingest-publication-slice
+description: Build and verify a small end-to-end publication path for validated ingested data, including atomic persistence, read fallback, and static artifact precedence.
+source: weekly-pattern-learner
+source_reason: "Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence."
+source_date: "2026-10-24"
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence.*
+
+# Ingest Publication Slice
+
+Use this workflow when an ingest pipeline must make a validated record available immediately while a static or cached publication artifact may be generated later.
+
+## Define the contract
+
+Before changing code, read the repository instructions and trace the current path from ingest entry point through validation, job completion, persistence, request handling, and static artifact generation. Record existing invariants and preserve unrelated work.
+
+Write acceptance criteria for one complete slice:
+
+- Only a completed, validated active dataset can be published.
+- The persistent publication record and terminal ingest state commit atomically.
+- The canonical read path can serve from the persistent record when no static artifact exists.
+- A static artifact remains authoritative once present, if that is the established product contract.
+- Retries are idempotent, and collisions, invalid states, hidden records, and takedowns cannot publish.
+
+Adapt these criteria to the actual product contract. Do not invent a static-artifact precedence rule if the system has none.
+
+## Implement test-first
+
+Use the repository's required test command and style. Add focused failing tests before implementation for:
+
+1. A valid ingest publishes the record and terminal state together.
+2. A failure between writes leaves neither half committed.
+3. The canonical read path uses the persisted record when the artifact is absent.
+4. The artifact wins when both sources exist, when precedence is required.
+5. Repeated delivery is safe and invalid, hidden, colliding, or withdrawn records stay unpublished.
+
+Test the production boundary and transaction behavior, not only helper functions. Keep the change to the smallest vertical slice; avoid unrelated schema or routing refactors.
+
+## Verify the composed path
+
+Run the focused tests, then the repository's required broader checks. Inspect the final diff and trace the completed path again from ingest through the canonical response. Confirm behavior for retries, partial failures, and transitions from no artifact to artifact present. Report any unavailable integration or deployment evidence explicitly.

package/adapters/hermes/olko-product/README.md

@@ -5,6 +5,7 @@
 Run `./scripts/install-hermes-symlinks.sh` from the repository root to link these skills
 into the active Hermes profile. The canonical packages are:
 
+- `plugins/olko-product/skills/ingest-publication-slice/SKILL.md`
 - `plugins/olko-product/skills/product-builder/SKILL.md`
 - `plugins/olko-product/skills/mvp-oneshot/SKILL.md`
 - `plugins/olko-product/skills/ux-ui-audit-loop/SKILL.md`

package/catalog/skills.json

@@ -514,6 +514,28 @@
       "name": "olko-product",
       "description": "Take a product idea to a shippable build: MVP passes, full-stack scaffolds, UX/UI quality loops, launch plans.",
       "skills": [
+        {
+          "name": "ingest-publication-slice",
+          "lookupName": "olko:ingest-publication-slice",
+          "path": "plugins/olko-product/skills/ingest-publication-slice",
+          "description": "Build and verify a small end-to-end publication path for validated ingested data, including atomic persistence, read fallback, and static artifact precedence.",
+          "tags": [
+            "ingest",
+            "publication",
+            "testing",
+            "workflow"
+          ],
+          "adapters": [
+            "claude",
+            "codex",
+            "cursor",
+            "copilot",
+            "grok",
+            "windsurf",
+            "kiro",
+            "hermes"
+          ]
+        },
         {
           "name": "product-builder",
           "lookupName": "olko:product-builder",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@olegkoval/agent-skills",
-  "version": "1.59.1",
+  "version": "1.59.3",
   "private": false,
   "publishConfig": {
     "access": "public"
@@ -52,6 +52,6 @@
     "@semantic-release/npm": "^13.2.0",
     "@semantic-release/release-notes-generator": "^14.1.1",
     "semantic-release": "^25.0.9",
-    "semantic-release-npm-github-publish": "^1.8.2"
+    "semantic-release-npm-github-publish": "^1.8.3"
   }
 }

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

package/plugins/olko-github-pr/skills/lekker-review/SKILL.md

@@ -29,6 +29,7 @@ description: >
   the PR", provides a GitHub PR URL, or asks for a pull request review in any
   form.
 license: MIT
+model: sonnet
 allowed-tools: Bash, Read, Write, Edit, Agent, Workflow, AskUserQuestion, Artifact, spawn_agent, wait_agent, followup_task, send_message, interrupt_agent, list_agents
 compatibility: >
   Claude Code and OpenAI Codex. Claude uses Workflow/Agent/Artifact. Codex uses

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.59.1",
+  "version": "1.59.3",
   "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, UX/UI quality loops, launch plans.",
-  "version": "1.59.1",
+  "version": "1.59.3",
   "author": {
     "name": "Oleg Koval"
   },

package/plugins/olko-product/skills/ingest-publication-slice/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: ingest-publication-slice
+description: Build and verify a small end-to-end publication path for validated ingested data, including atomic persistence, read fallback, and static artifact precedence.
+source: weekly-pattern-learner
+source_reason: "Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence."
+source_date: "2026-10-24"
+---
+
+> 🤖 *Auto-generated by **weekly-pattern-learner** · Repeatedly implement a validated ingest-to-publication flow with atomic persistence, fallback reads, and static artifact precedence.*
+
+# Ingest Publication Slice
+
+Use this workflow when an ingest pipeline must make a validated record available immediately while a static or cached publication artifact may be generated later.
+
+## Define the contract
+
+Before changing code, read the repository instructions and trace the current path from ingest entry point through validation, job completion, persistence, request handling, and static artifact generation. Record existing invariants and preserve unrelated work.
+
+Write acceptance criteria for one complete slice:
+
+- Only a completed, validated active dataset can be published.
+- The persistent publication record and terminal ingest state commit atomically.
+- The canonical read path can serve from the persistent record when no static artifact exists.
+- A static artifact remains authoritative once present, if that is the established product contract.
+- Retries are idempotent, and collisions, invalid states, hidden records, and takedowns cannot publish.
+
+Adapt these criteria to the actual product contract. Do not invent a static-artifact precedence rule if the system has none.
+
+## Implement test-first
+
+Use the repository's required test command and style. Add focused failing tests before implementation for:
+
+1. A valid ingest publishes the record and terminal state together.
+2. A failure between writes leaves neither half committed.
+3. The canonical read path uses the persisted record when the artifact is absent.
+4. The artifact wins when both sources exist, when precedence is required.
+5. Repeated delivery is safe and invalid, hidden, colliding, or withdrawn records stay unpublished.
+
+Test the production boundary and transaction behavior, not only helper functions. Keep the change to the smallest vertical slice; avoid unrelated schema or routing refactors.
+
+## Verify the composed path
+
+Run the focused tests, then the repository's required broader checks. Inspect the final diff and trace the completed path again from ingest through the canonical response. Confirm behavior for retries, partial failures, and transitions from no artifact to artifact present. Report any unavailable integration or deployment evidence explicitly.

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

package/scripts/lib/catalog.mjs

@@ -20,7 +20,7 @@ export const PLUGIN_ASSIGNMENT = {
   },
   'olko-product': {
     description: 'Take a product idea to a shippable build: MVP passes, full-stack scaffolds, UX/UI quality loops, launch plans.',
-    skills: ['product-builder', 'mvp-oneshot', 'ux-ui-audit-loop', 'frontend-direction', 'starter-rules', 'viral-launch'],
+    skills: ['product-builder', 'mvp-oneshot', 'ux-ui-audit-loop', 'frontend-direction', 'starter-rules', 'viral-launch', 'ingest-publication-slice'],
   },
   'olko-skill-meta': {
     description: 'Author and maintain agent skills and the AI toolchain itself.',