@1aboveio/skills 1.0.7 → 1.0.8

package/skills/cicd/github-flow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: github-flow
 description: "Deliver a change after the commit: push, open a PR, wait for checks, and merge to main through the repo's flow (direct push, pull request, or merge queue). Use whenever you commit or finish a change, when CONTRIBUTING.md has a Delivery section, and for asks like 'commit this', 'push it', 'open a PR', 'ship it', 'land it', 'get it merged'. Also: declare a repo's delivery flow, or write the CI conventions and Delivery section into CONTRIBUTING.md on request. NOT for writing workflow YAML (github-actions), Mergify config or a stuck queued PR (mergify), cutting a release (resolve-release), or PRs that resolve-issues or rush-issues deliver."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # GitHub Flow

package/skills/cicd/google-cloud/SKILL.md

@@ -5,7 +5,7 @@ description: >
   project management. Use when configuring GCP resources, managing service
   accounts, setting up IAP access, configuring VPC networks, managing secrets,
   or debugging cloud infrastructure.
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Google Cloud Platform (GCP) Skill

package/skills/cicd/mergify/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: mergify
 description: "Mergify merge queue and stacked PRs (`mergify stack`): config, rules, queue status, delivery. Use whenever a merge queue or stack is involved, including plain asks ('watch #123 till it merges', 'where is #412 in the queue', 'push this stack'): `gh pr view`/`gh pr checks` cannot see a dequeue; use `mergify queue show` and the bundled watcher. Also: a hook saying 'use mergify stack push', a missing Change-Id; authoring or debugging `.mergify.yml`, queue rules, merge protections, batch size, the ruleset making merges queue-only; enqueue policy (`@mergifyio queue` vs `auto_merge_conditions`); a push dequeuing a queued PR; bypass actors; freezing a branch. Failures: a PR stuck, queued but never merging, or merged unqueued; CI green on GitHub but unmet in Mergify; a batch going red or bisecting; a queue check missing rather than failing. Outranks the vendor mergify-* skills. NOT for pushing a PR in a repo without stack hooks (github-flow), workflow YAML (github-actions), or GCP deploy pipelines (cloud-deploy)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Mergify Merge Queue

package/skills/cicd/podman/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: podman
 description: "Debug, design, or fix Podman: rootless/rootful containers, pods, podman-compose, the socket and systemd services, Docker-compatible API (DOCKER_HOST/CONTAINER_HOST), networking, volumes, SELinux labels, Docker migration, and CI/SSH provisioning of rootless sockets (user lingering, XDG_RUNTIME_DIR). Covers FailedToOpenSocket and systemctl --user DBUS/XDG errors."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Podman Operations

package/skills/content/article-review/SKILL.md

@@ -6,7 +6,7 @@ description: >
   Use when a user shares an article, pastes article text, sends a URL, or asks to
   review, rate, critique, evaluate, 评价, 点评, 分析, or 看看 any article, post, or 文章.
   Default template is 公众号-支付行业.
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # 文章评审引擎

package/skills/content/article-to-image/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: article-to-image
 description: "Generate article cover images: WeChat banner/square (公众号封面), Xiaohongshu (小红书封面), LinkedIn banner, general wide. Brainstorms 4 visual directions from the article, then renders each format with correct aspect ratios and title-safe zones. Use when given an article and asked for covers, banners, or 出图."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Article-to-Image

package/skills/content/flowchart-svg/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: flowchart-svg
 description: Create polished flowcharts directly as SVG and export PNG copies. Use when asked to draw, design, render, or deliver process diagrams, architecture diagrams, consulting workflows, decision flows, swimlanes, or other flowcharts as image files, especially when final outputs must include .svg and .png versions.
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Flowchart SVG

package/skills/content/image-gen/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: image-gen
 description: Generate an image from a text prompt with OpenAI gpt-image-2 or Google Nano Banana (Gemini), saved to an image file. Use whenever the user asks to generate, create, make, draw, paint, render, or design an image, picture, illustration, photo, artwork, logo, icon, avatar, banner, hero image, thumbnail, poster, wallpaper, sticker, or concept art — including phrasings like "an image of X", "a picture of X", "show me what X would look like", or a request for a visual for a slide, blog post, README, or social post. Also triggers on Chinese phrasings such as 生成图片, 画一张图, 做一张海报, 设计一个 logo. NOT for charts or data visualizations (dataviz), flowcharts or architecture diagrams (flowchart-svg), or editing an existing image file.
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Image Generation

package/skills/content/mermaid/SKILL.md

@@ -2,7 +2,7 @@
 name: mermaid
 description: Create and edit Mermaid diagrams for architecture, API flows, database schemas, workflows, and data models.
 user-invocable: true
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Mermaid Diagram Creation

package/skills/content/wechat-article-writer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: wechat-article-writer
 description: "Write WeChat 公众号 articles in Chinese content styles — 踩坑型 (pitfall-story), 实操型 (how-to), 对比型 (comparison), 观察型 (industry insight) — in the account's house style from the nearest WRITING.md. Use for drafting from scratch, rewriting a draft, adapting source material into a publishable article, or picking the right style. NOT for business or technical documents (write-doc)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # WeChat Article Writer (公众号写作)

package/skills/content/wechat-publisher/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: wechat-publisher
 description: "Publish articles to a WeChat Official Account (公众号) via API: push Markdown to the draft box (or auto-publish with --publish), convert Markdown to WeChat HTML, upload images to the media library. Requires AppID + AppSecret + whitelisted server IP on a 认证订阅号/服务号. Consumes wechat-article-writer's Markdown."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # WeChat Publisher (公众号发布)

package/skills/content/wechat-search/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: wechat-search
 description: "Search WeChat 公众号 articles via Sogou Weixin, or read/summarize an article from a mp.weixin.qq.com URL (读/分析/总结) — suggest proactively when such a URL appears. Use for Chinese WeChat content, industry reports, competitor or trending topics. Requires Chrome Browser Relay. NOT general web search (web_search)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # WeChat Article Search & Reader (搜狗微信搜索)

package/skills/content/xai-search/SKILL.md

@@ -9,7 +9,7 @@ metadata:
         type: secret
         required: true
         description: xAI API key (get from console.x.ai)
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # xAI Search (X/Twitter + Web)

package/skills/core/distill-writing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: distill-writing
 description: "Learn a house writing style from approved sample documents, or save an explicitly stated project document preference, into WRITING.md and writing/templates/. Use for sample-based style learning, house-style setup or refresh, and requests such as 'remember this for future PRDs' or 'make this our report default', including handoffs from write-doc or plain-language. Preserve manual edits and separate document types. NOT for drafting a document (write-doc) or saving chat-only preferences (plain-language)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Distill a writing style

package/skills/core/doc-to-md/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: doc-to-md
 description: "Convert documents (PDF, DOCX, PPTX, XLSX, images) to Markdown so agents can read them. Use as the preprocessing step whenever binary files need to enter agent context — contract review, compliance audit, document analysis, evidence review."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # doc-to-md

package/skills/core/editorial-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: editorial-review
 description: "Review a document or generated report for what it says (does the reader get the answer, is the argument sound, is anything unsupported, obvious or repeated), then fix the content. Use to review, tighten or clarify a doc or report, and as the review step of write-doc and the report skills. NOT for Chinese wording (polish-cn) or code review (better-review)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Editorial review

package/skills/core/house-style/SKILL.md

@@ -3,7 +3,7 @@ name: house-style
 description: "Shared reference the writing skills read by path: WRITING.md lookup and precedence, template choice, gap markers, template shape, the bundled templates, and the default English and Chinese style guides. Never select or invoke it as a task."
 disable-model-invocation: true
 user-invocable: false
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # House style

package/skills/core/plain-language/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: plain-language
 description: "Session mode: every reply and status line in plain language — lead with the point, everyday words, full sentences, no filler — in English or Chinese, until turned off. Enable by default when the project has an applicable WRITING.md, even without a slash command. Use for /plain-language, 'talk plainly', '说人话', and explicit requests to remember project reply preferences; /plain-language init persists the default and loading instructions. Save reply rules only under Agent replies; route document preferences to distill-writing. Ordinary mode toggles remain session-only. Turn off with '/plain-language off' or 'normal mode'. NOT for writing a document (write-doc) or reviewing one (editorial-review)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Plain language

package/skills/core/polish-cn/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: polish-cn
 description: "Polish the Chinese wording of a finished document or report, with a script proving every number, date, identifier, link and protected term is unchanged; prefers a Chinese model and records which ran. Use for '中文润色' or as a report skill's last step. NOT for cutting or restructuring content (editorial-review) or translating (write-doc)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Polish Chinese

package/skills/core/reg-parser/SKILL.md

@@ -2,7 +2,7 @@
 name: reg-parser
 version: 1.1.0
 description: "Parse regulatory/scheme documents into structured outputs: convert a regulation (AML, VARS, PCI-DSS, KYC, GDPR) into an audit-ready compliance checklist, or trace contract clauses to a mandate source. Suggest proactively when a regulation PDF accompanies a contract review or compliance task. NOT general summarization (doc-to-md), or writing the gap analysis or policy from the checklist (write-doc)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # reg-parser

package/skills/core/terminology/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: terminology
 description: "Build and keep a project's TERMINOLOGY.md: the preferred term per concept in English, 简体 and 繁體, and the terms to avoid. Use to set it up from the project's documents, when the user settles or corrects a term, or when another writing skill needs the format. NOT for writing documents (write-doc) or the code domain model (domain-modeling)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Terminology

package/skills/core/write-doc/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: write-doc
 description: "Write or edit documents and compliance reports in the project's house style: BRD, PRD, gap analysis, technical spec, integration guide, proposal, policy, risk procedure, audit report, external assessment, management report or Visa VARS Review Report; English, Chinese or bilingual. Use automatically whenever asked to draft, write, revise or edit a document, without needing a slash command, including 'write up the findings'. Route explicit requests to remember a writing preference to its persistence owner. Markdown by default; export when requested. NOT for ordinary chat replies (plain-language), learning style from samples or preference-only saves (distill-writing), performing an audit (compliance-audit), or WeChat articles (wechat-article-writer)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Write a document

package/skills/engineering/better-review/SKILL.md

@@ -4,7 +4,7 @@ description: "Slash/explicit-only (/better-review). Single-agent adversarial rev
 disable-model-invocation: true
 dependencies:
   - engineering-runtime
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Better Review

package/skills/engineering/contributing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: contributing
 description: "The conventions a repo's CONTRIBUTING.md holds, starting with tracker routing: which tracker an issue belongs in (GitHub for engineering, Linear for product), duplicate search, and linking back to the source requirement. Use before creating any issue, spec, epic, ticket or sub-issue on GitHub or Linear, including inside /to-spec, /to-tickets and /triage, and whenever work that started from a Linear issue turns into engineering work. Also writes the rules as the Issue tracking section of the repo's CONTRIBUTING.md. NOT for delivering a PR (github-flow) or splitting work into slices (to-tickets)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Contributing

package/skills/engineering/e2e-test/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: e2e-test
 description: "Playwright end-to-end standard: the 3-tier suite (render-health / functional / journey), generated route manifest, and presentation sweep. Use when browser routes or user flows ship or change, or a Playwright test flakes. NOT for non-browser tests, defining what to test (ensure-coverage), the curated ALIVE/DEAD golden-path gate (golden-path), or CI workflow YAML (github-actions)."
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # E2E Testing Standard

package/skills/engineering/engineering-runtime/SKILL.md

@@ -3,7 +3,7 @@ name: engineering-runtime
 description: Internal support package for shared Engineering Workflow executable behavior. Never select or invoke this package as a user capability.
 disable-model-invocation: true
 user-invocable: false
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Engineering Runtime

package/skills/engineering/engineering-runtime/coherence/workflow.json

@@ -369,7 +369,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "8f0be335debec8a0b64bb40201a412eb0bc9ccc402074a7af0a483609daac28e",
+      "contentDigest": "a37292865bf496db5c900602b3a2fefb87b5ebc9e6e7a185e2c8471d498c9a38",
       "digestExcludes": []
     },
     {
@@ -382,7 +382,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "54c4c3e8579168b32c9d894f91d9bd6950dde2bf44ebd908cc7c548bdc0f6435",
+      "contentDigest": "76e79c091a20274fc7a11296e5dbb2bb128525499596129baae4a11179ef7f71",
       "digestExcludes": []
     },
     {
@@ -395,7 +395,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "8e6ae6a6065c670b6ed61c2b881dbea921847a7d80818916e853c4b73dd02e56",
+      "contentDigest": "e4c79b9b236babd8413778b57b67e157edc81b7870302ac38153ebd15eca6b66",
       "digestExcludes": []
     },
     {
@@ -408,7 +408,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "d5c96b3b0a7272a6ae6d4670f3deca7196c39cdb857d52936b076e880d338bcd",
+      "contentDigest": "c91d1d12fb3110f42779c00aa7666a7f9401bae04e63c681034c84276adab222",
       "digestExcludes": []
     },
     {
@@ -421,7 +421,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "077317f2b2e8a142bd46c75d00bf2ba23b34cc24daa3f49bb9e4bb7247f7590c",
+      "contentDigest": "800748e040c2c47a78b65713fd88d1586206feb7f5a5ce052da051a72cc82743",
       "digestExcludes": []
     },
     {
@@ -434,7 +434,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "a755c90afd1aef1e3de56fd35af08e98fc111b7cea775a63c7a34593ec1e499b",
+      "contentDigest": "5441c5a8c40c27c1455001ee65b5cf055d25932963410b852d6fd7753e03c7e0",
       "digestExcludes": []
     },
     {
@@ -447,7 +447,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "937c2139aa3ca8f9f0a325c8a1300b1a84faba2f16132f8c608169e4e0732631",
+      "contentDigest": "22b2d51f863c5e215dda1036ada423d65873652d05aee4efa83ff4e4995dfc2d",
       "digestExcludes": []
     },
     {
@@ -460,7 +460,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "a2e269f07c9309c5404eafe1b2ca2f5913dd390711c9a3ea7bffb3ae13c88a58",
+      "contentDigest": "f293e919a756e073894e959f25d874d69ef94839ccd98a92aa5073308f18f643",
       "digestExcludes": []
     },
     {
@@ -473,7 +473,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "9c2920ba1dd60e6546831d5c5e0d32c2ce620cfd81cbb6b336c19dde223cacbb",
+      "contentDigest": "3d9dd1501f80995d27026e1b7ba9751e2e10f4db7f1a427c36bd1f9eec24fcdf",
       "digestExcludes": []
     },
     {
@@ -486,7 +486,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "4b85a0b25eec4594b40d95f41307ae1960b57d648df6e032cc0c780187432805",
+      "contentDigest": "4d5e6c1570bb2395813382991aa04437b60b7f20fd54234d07a7af5dbd2b31e3",
       "digestExcludes": []
     },
     {
@@ -499,7 +499,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "ee9204746c76d9734873b6f4953c2bf4854d01544bdd8212fe93df80d51e1c28",
+      "contentDigest": "8d32ffe5807e680193e4ee05d51a7c6691e25ffea54bd657405e1025e318cf09",
       "digestExcludes": []
     },
     {
@@ -512,13 +512,13 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "1924382a6facdc4ad20cf9a70ee608c33c9d3dcba0babc2c1ed900876f6f1bb2",
+      "contentDigest": "6fcf7271652b12f8a64e03cdce85fdeee10cc8456f89ac1b39631281e2e52615",
       "digestExcludes": [
         "coherence/workflow.json"
       ]
     }
   ],
-  "releaseIdentity": "931e08c86e3cec4a44ba5568386488328de64187ae452e1db2a952043068d0f6",
+  "releaseIdentity": "0e956b77698da11b37a94d960a5f7a7102af5b761b788f1fe52a6c9716cf132d",
   "lifecycleAuthority": "native-skills-cli",
   "repairRecipe": {
     "id": "engineering-workflow-dependency-first",

package/skills/engineering/ensure-coverage/SKILL.md

@@ -2,7 +2,7 @@
 name: ensure-coverage
 description: "Define or audit behavior-first test criteria — ACs, required test levels, mock/integration/E2E policy — across three axes: breadth (Coverage Ledger), depth (over-mocking), presentation (perceivability of browser surfaces). NOT judging whether a single test is any good (test-quality), authoring browser tests (e2e-test), reviewing a PR (better-review), or delivering issues (resolve-issues)."
 disable-model-invocation: true
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Ensure Coverage

package/skills/engineering/golden-path/SKILL.md

@@ -3,7 +3,7 @@ name: golden-path
 description: "Golden-path E2E: the short list of user journeys whose failure blocks a release, kept in a repo as one contract (golden-paths.json) with a generated GOLDEN_PATHS.md and a generated GitHub Actions workflow, and run against a local build or a deployed URL for an ALIVE/DEAD verdict. Use to set golden paths up in a repo ('init golden paths', 'add golden-path CI'), to migrate an older smoke.manifest.json or a hand-built smoke setup ('audit', 'migrate smoke'), to add, change, or remove a golden path, to ask 'is the build alive?' or run them before a PR or release, or when a change touches a flow listed in GOLDEN_PATHS.md. NOT for writing the Playwright specs themselves (e2e-test), deciding what a change must prove (ensure-coverage), or general workflow YAML (github-actions)."
 dependencies:
   - e2e-test
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Golden path

package/skills/engineering/harness-runtime/SKILL.md

@@ -3,7 +3,7 @@ name: harness-runtime
 description: Internal import-only library shared by first-party engineering packages. Not a workflow skill; never select or invoke it as a user capability.
 disable-model-invocation: true
 user-invocable: false
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Harness Runtime

package/skills/engineering/resolve-issues/SKILL.md

@@ -8,7 +8,7 @@ dependencies:
   - better-review
   - golden-path
   - harness-runtime
-release-version: 0.43.0
+release-version: 0.43.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Resolve issues
@@ -78,7 +78,7 @@ ships sooner at the same bar.
 `/rush-issues` runs this workflow with every answer defaulted ([shortcut mode](references/preflight.md#shortcut-mode)).
 
 **Bounds:** the harness times and stops workers · retry while cycles reach new lows; 2 without one,
-then [expire.md](references/expire.md) (a fix cycle progresses only on a new low; a resume, when it adds work the PR needs; diagnostics and records never) · workers within [live host capacity](references/implementation.md#live-capacity), one local emulator, queued for device-only work
+then [expire.md](references/expire.md) (fixes and resumes progress through verified checkpoint advances or fewer established failures; added work, diagnostics and records alone do not reset counts) · workers within [live host capacity](references/implementation.md#live-capacity), one local emulator, queued for device-only work
 and non-CI emulator proof ([scheduling](references/implementation.md#scheduling); CI confirms, never debugs) · one PR per issue · every runnable unit in one run, in dependency order · blocking review hands back
 after 2 fix rounds without a new low of open P0/P1 path rows; no fixed round cap.
 
@@ -150,26 +150,17 @@ Read each procedure right before its stage; never substitute your own.
   steps are only the read-only warehouse canary (never blocks) and the isolated, run-owned resources
   [preflight.md](references/preflight.md#never-block-on-the-human) allows.
 
+## Delivery progress
+
+Before briefing or continuing a unit, read [delivery-progress.md](references/delivery-progress.md).
+Keep one existing acceptance checkpoint per unit, preserve failure history, justify new
+infrastructure, and report verified behavior. Full acceptance and required CI still apply.
+
 ## Every brief contains
 
-- the source and criteria, as a file already in the run directory
-- the plan's `standingOrders`, verbatim, and the decisions that answer this unit's questions
-- absolute run, workspace, and findings paths; for implementers, the unit's
-  findings entry and its parents' `contracts`
-- model id, effort, and a required read-back
-- an absolute skill path when the stage invokes a leaf skill; for validating, the unit's `proof.suite` `skill` (read it first) and `local`, when set
-- the outcome and validation, with no prescribed method or evidence format
-- the [Goal](#goal) and [Principles](#principles), verbatim (a reviewer gets review.md's two rules instead)
-- the result path, `<run>/results/<unit>-<label>.json` (`<label>`: kind and attempt, e.g. `fix-2`), with `unit` and `decisionNeeded` (null or a choice)
-- at the deadline: stop starting work, commit, and report
-- environment rules: write only inside the workspace (and the findings directory for the explorer),
-  with tool caches and temp files there (`TMPDIR`, `npm_config_cache`, `UV_CACHE_DIR`); use the machine's
-  installed JDK, Android SDK, system images, and browsers (`JAVA_HOME`, `ANDROID_HOME`) where they fit,
-  or the repo's pinned Playwright image where the runner has no browser (`github-actions` runners.md);
-  edit with the harness's tools, never a shell `apply_patch`
-
-Treat a missing or unreadable result as an incomplete stage: resume a dead
-spawn once in the same workspace, never with a success claim.
+Use the full [brief checklist](references/delivery-progress.md#every-brief-contains),
+including the Goal and Principles verbatim, checkpoint history and result contract.
+Treat a missing or unreadable result as incomplete; resume a dead spawn once in its workspace.
 
 ## Workflow
 

package/skills/engineering/resolve-issues/references/delivery-progress.md

@@ -0,0 +1,63 @@
+# Delivery progress
+
+For each active unit, name **one immediate acceptance checkpoint** from its existing
+criteria: the next observable behavior or contract to prove. A narrow checkpoint guides
+the next action; it does not replace the unit's full acceptance or required CI. Independent
+units keep their own checkpoints and continue in parallel within actual resource limits.
+
+- **Preserve an existing working baseline.** Keep its source/artifact identity, relevant
+  environment and passing result as a comparison. Reuse it while those inputs remain
+  valid; do not create a new baseline campaign when none exists or treat an old artifact
+  as acceptance of the candidate. Keep only what the repo's ownership/retention rules allow.
+- **Debug the smallest failing behavior first.** Name the failing command and the
+  observation that would distinguish the remaining causes. Run the relevant host,
+  integration or device check before another broad acceptance cycle. After a correction,
+  run affected checks and the required delivery checks, not extra assurance work.
+- **Justify infrastructure before adding it.** State which existing criterion requires
+  it, why the current path cannot provide that proof, and the smallest alternative.
+  Record the choice in the existing decision/note, within current authorization. Routine
+  choices need no new approval; shared-resource changes and changes to the acceptance
+  bar retain their existing authorization rules. A failed screen alone does not justify
+  a new service, transport layer or test platform.
+- **Continue on evidence, not activity.** A handoff identifies what changed at the
+  checkpoint: a reproduction, a discriminating observation, a verified correction or
+  a concrete blocker, and the next test. A new worker, commit, diagnostic helper, test
+  count or green unrelated check is not delivery progress. Useful diagnostic evidence
+  can justify a bounded experiment; it does not reset acceptance/non-convergence counts.
+- **Reassess repeated failure at the same checkpoint.** Carry prior evidence and
+  no-progress history across worker/model changes and new infrastructure. Follow
+  [expiry](expire.md); do not restart the same approach with a fresh brief or
+  count newly invented setup milestones as progress. Replan around a smaller case or a
+  different distinguishing test, keeping the original criteria and truthful blockers.
+- **Report delivered behavior first.** Use existing plan notes/results to state criteria
+  completed and the current checkpoint. When available, include time to reproduction,
+  time to verified correction and full CI runs spent on this change. Do not invent
+  missing timings or create a separate reporting system to collect them.
+
+These rules apply to briefs and coordinator decisions; they add no plan schema, check,
+issue or automatic scheduler gate. They do not waive required validation.
+
+## Every brief contains
+
+- the source and criteria, as a file already in the run directory
+- the plan's `standingOrders`, verbatim, and the decisions that answer this unit's questions
+- absolute run, workspace, and findings paths; for implementers, the unit's
+  findings entry and its parents' `contracts`
+- model id, effort, and a required read-back
+- an absolute skill path when the stage invokes a leaf skill; for validating, the unit's `proof.suite` `skill` (read it first) and `local`, when set
+- the outcome and validation, with no prescribed method or evidence format
+- the [immediate acceptance checkpoint](#delivery-progress), existing baseline (or none),
+  and, for a continuation, the last result, remaining uncertainty and next distinguishing
+  test; retain the same checkpoint/history when changing workers
+- the [Goal](../SKILL.md#goal) and [Principles](../SKILL.md#principles), verbatim (a reviewer gets review.md's two rules instead)
+- the result path, `<run>/results/<unit>-<label>.json` (`<label>`: kind and attempt, e.g. `fix-2`), with `unit` and `decisionNeeded` (null or a choice)
+- at the deadline: stop starting work, commit, and report
+- environment rules: write only inside the workspace (and the findings directory for the explorer),
+  with tool caches and temp files there (`TMPDIR`, `npm_config_cache`, `UV_CACHE_DIR`); use the machine's
+  installed JDK, Android SDK, system images, and browsers (`JAVA_HOME`, `ANDROID_HOME`) where they fit,
+  or the repo's pinned Playwright image where the runner has no browser (`github-actions` runners.md);
+  edit with the harness's tools, never a shell `apply_patch`
+
+Treat a missing or unreadable result as an incomplete stage: resume a dead
+spawn once in the same workspace, never with a success claim.
+

package/skills/engineering/resolve-issues/references/expire.md

@@ -9,10 +9,12 @@ commit alone is not progress. Lows only fall, so the loop always ends.
 Example: CI fails 5 tests, then 3, then 3, then 3: expire after the fourth
 cycle. 3, 2, 3, 2 expires too: the second 2 is no new low. 5, 4, 3, 2, 1
 never expires. A failing journey run, local or dispatched, counts as one
-failing check, so count its furthest checkpoint instead (the last step its
-log reports passing): login, store, charge, charge, charge expires;
-login, store, charge, receipt keeps going. Checkpoints are finite, so this
-loop ends too.
+failing check, so count its furthest **existing acceptance checkpoint** instead
+(the last relevant step its log reports passing): login, store, charge, charge,
+charge expires; login, store, charge, receipt keeps going. Extra instrumentation,
+new infrastructure milestones or renaming a checkpoint do not extend this sequence.
+Carry the comparison history across worker/model changes and retries; a genuinely
+changed requirement needs an explicit scope decision, not an implicit reset.
 
 | Scope | Count that must reach a new low | Expire after |
 |---|---|---|
@@ -21,9 +23,17 @@ loop ends too.
 | Warehouse canary | distinct errors | 2 attempts without progress; record a follow-up, never block |
 | Review | open P0/P1 path rows | `review-verdict.mjs` verdict `handback` ([review.md](review.md#fix-loop)) |
 | CI and merge | failing checks and tests; a failing journey run (local or `gh workflow run`) is one check, so it progresses when it passes a checkpoint no earlier run of the attempt passed | 2 fix-and-watch cycles without progress |
-| Any worker the harness reports stuck, late, or at its ceiling | none: a resume [progresses](#retry-by-failure-mode) when it adds work the unit's PR needs (product code, tests, CI config, a fix of what blocks it) or meets another acceptance criterion; diagnostics and records alone are not progress | 2 resumes in a row that add neither |
+| Any worker the harness reports stuck, late, or at its ceiling | a resume progresses when its verified result advances the existing checkpoint or reduces the established failure count; added product/test/CI code without that result is not progress, and diagnostics alone do not reset the count | 2 resumes in a row without such progress |
 
-Leave timing to the harness; never stop a worker still making progress.
+Use [Delivery progress](../SKILL.md#delivery-progress) to choose the next bounded
+experiment before applying this ladder. Reproducing a failure or collecting a missing
+observation can be useful without advancing acceptance. Record that distinction; do
+not count logs, helper code or a changed worker as a new low. On repeated non-convergence,
+reassess the approach and preserve unpassed criteria rather than creating another setup
+chain. Existing retry/block/replan rules below still apply.
+
+Leave timing to the harness for worker lifetimes. Bound individual test/subprocess waits
+explicitly with cleanup time; an outstanding tool call or heartbeat is not progress.
 
 ### Retry by failure mode
 
@@ -102,8 +112,9 @@ hours.
   wakes the run at the printed time.
 - `check-worker` means the worker changed no workspace file for
   `--quiet-minutes` (45 by default): read its latest output. Stuck: stop it
-  and take the `timeout-task` response. Still working (a long test run with
-  live output): let it run.
+  and take the `timeout-task` response. A long test with advancing test/phase results
+  inside its declared command deadline may continue. Repeated heartbeats, unchanged
+  logs or an unbounded child wait are not that evidence.
 - A watcher that ends with nothing new (a queue `STALLED` with no failing
   check) is a wait: restart it and report it in one line, or not at all.
 
@@ -202,14 +213,14 @@ logs, and record one line, with the reason code, in the unit's plan row.
 
 | Failure | Response |
 |---|---|
-| `timeout-task` or `spawn-death` | Resume in the kept workspace: commit what is there, then finish or report. Keep resuming while each resume makes [progress](#retry-by-failure-mode); after 2 in a row that add nothing, mark the unit `blocked` (`blockedReason: timeout-task` or `spawn-death`) and hand it back. A result with `decisionNeeded` is decided first ([Decide before you defer](#decide-before-you-defer)), and the resume that carries the decision always runs. Example: a fix worker loses its model stream twice but committed a fixture each time; start a third continuation. |
+| `timeout-task` or `spawn-death` | Resume in the kept workspace: commit what is there, then finish or report. Keep resuming while each resume makes [progress](#retry-by-failure-mode); after 2 in a row without verified checkpoint/failure-count progress, mark the unit `blocked` (`blockedReason: timeout-task` or `spawn-death`) and hand it back. A result with `decisionNeeded` is decided first ([Decide before you defer](#decide-before-you-defer)), and the resume that carries the decision always runs. Example: a fix worker loses its model stream after its focused regression passes; resume the remaining work with that result. Two resumes that only add fixtures without advancing the existing checkpoint trigger reassessment. |
 | Environment or infrastructure (a check cannot run: cache, emulator, runner, network, credentials) | See [Infrastructure failures](#infrastructure-failures). |
 | Implement: a fix cycle without progress | Resume with the failing command and its output as the only target, using the escalation model. 2 cycles in a row without progress: `blocked` (`blockedReason: retry-implement`), deferred on its issue. |
 | Review: `review-verdict.mjs` verdict `fix` | Follow its `action` ([review.md](review.md#fix-loop)). |
 | Review: `review-verdict.mjs` verdict `handback` (`not-converging`) | Stop fixing; mark the unit `blocked` (`blockedReason: review-handback`) and defer the PR with its open findings on its issue. |
 | Review: `review-verdict.mjs` verdict `decide`, or a worker's `decisionNeeded` | [Decide before you defer](#decide-before-you-defer). |
 | CI: a fix cycle without progress | Treat the failing check as the failing test: the next fix worker runs on the escalation model with that check as its only target. 2 cycles in a row without progress: `blocked` (`blockedReason: retry-ci`), deferred on its issue. |
-| Too big for one attempt | Resume in the kept workspace while each resume makes [progress](#retry-by-failure-mode); after 2 in a row that make none, draft a split in `<run>/splits/`, file it into the spec's tree, and run the slices the sync adds ([preflight.md](preflight.md#put-every-filed-issue-in-the-tree)). |
+| Too big for one attempt | Resume in the kept workspace while each resume makes [progress](#retry-by-failure-mode); after 2 in a row without verified checkpoint/failure-count progress, draft a split in `<run>/splits/`, file it into the spec's tree, and run the slices the sync adds ([preflight.md](preflight.md#put-every-filed-issue-in-the-tree)). |
 | A required proof the unit has no environment for yet | The unit builds it; see [Proof stays with its unit](#proof-stays-with-its-unit). |
 | Dependency | Fix the edge; resume when runnable. |
 | A capability the unit needs is missing and no unit builds it (a shared driver, fixture, or hook) | Build it inside the first unit that needs it; units that need it later get `dependsOn` on that unit. Only when that puts the unit past the size check's line limit, file it as its own issue beside them, with `blocked_by` on the units that use it, never on their parent issue. Example: three proof units each need a device-state reader: the first builds it, the other two depend on the first. |
@@ -229,7 +240,9 @@ dependents start while the parent still proves itself; only the unit's own
 merge waits for its proof.
 
 - **No working suite or environment yet? The unit builds what its proof
-  needs**, with access the run already has (the run's local emulator, when
+  needs**, after recording why the existing path cannot prove that criterion and why
+  the proposed addition is the smallest suitable option ([Delivery progress](../SKILL.md#delivery-progress)),
+  with access the run already has (the run's local emulator, when
   [its queue](implementation.md#scheduling) hands it over, a
   disposable database, a container, a tunnel hostname), counted in its
   lines like a missing prerequisite. When two or more units need the same