@1aboveio/skills 1.0.21 → 1.0.22

package/skills/cicd/mergify/scripts/watch-pr-delivery-core.mjs

@@ -319,9 +319,8 @@ export const DEFAULT_SLOW_JOB_MINUTES = 5
 //
 // Over-ceiling values are REFUSED (exit 2), not silently clamped. Clamping would let a caller
 // believe it had a four-hour watch while getting one hour, and the two streams here are already
-// committed: stdout is exactly one terminal JSON verdict, stderr is one NDJSON heartbeat per
-// poll, so there is no channel for a warning that would not break a documented contract. An
-// exit-2 usage error is loud, immediate, and matches how every other bad bound is handled.
+// committed: stdout is exactly one terminal JSON verdict; stderr contains NDJSON transitions
+// and diagnostics. An exit-2 usage error is loud, immediate, and matches other bad bounds.
 export const MAX_MINUTES_CEILING = 60
 
 export function readTimeoutMs(intervalSeconds, boundMinutes, readsPerPoll = 1) {
@@ -730,28 +729,12 @@ export function classifyDequeue({ rawReason = null, failedChecks = [] } = {}) {
   return 'unknown'
 }
 
-// Every poll's observation, as one compact NDJSON record — the watcher's heartbeat.
-//
-// Before this existed the loop's ONLY output sites were the three terminal ones (`MERGED`/
-// `DEQUEUED`/`CLOSED_UNMERGED` below, plus the two `STALLED` paths), so a watch sitting in
-// `NOT_YET_QUEUED` or `QUEUED` — the overwhelmingly common case, and the entire healthy path —
-// wrote zero bytes for its whole life. Reproduced live on PR #1396: 25 minutes of watching a
-// PR that was never queued produced a log containing only the harness's own spawn banner, and
-// the watch was killed 4 minutes short of the then-30-minute stall bound, so it never printed
-// even its terminal verdict. (The bound is 10 now, so that same watch would settle on its own
-// well before a human gave up on it — but the heartbeat is what makes the wait legible while
-// it runs, and no bound short enough to substitute for it would be long enough to be correct.) A silent process is indistinguishable from a hung or dead one, which is
-// exactly the state the caller is trying to resolve, and the hand-written shell watchers this
-// script is meant to replace all printed a per-poll status line. Losing that on the way to a
-// correct state machine traded one failure (wrong answers) for another (no answers).
-//
-// Deliberately stderr, not stdout: stdout is the machine contract — exactly one pretty-printed
-// terminal JSON object, which callers parse whole — and interleaving heartbeats into it would
-// break every such caller. stderr is unparsed by the contract and is merged into the log by
-// every process supervisor that would run this, which is the place a human actually looks.
-// `terminal: false` and the separate stream both distinguish these from the real verdict.
+// Emit the initial delivery snapshot and subsequent delivery/readability transitions.
+// Repeated snapshots stay quiet: process supervisors count newly written bytes as activity
+// even when a record says progress:false. A readability transition remains visible without
+// resetting the delivery change clock. stdout remains one terminal JSON verdict.
 export function progressRecord({ payload, changed, sinceChangeMs, nowIso }) {
-  return JSON.stringify({ ...payload, progress: true, changed, sinceChangeMs, at: nowIso })
+  return JSON.stringify({ ...payload, activity: true, progress: changed, changed, sinceChangeMs, at: nowIso })
 }
 
 // Defaults. `stallMinutes` is a NO-CHANGE bound, not an elapsed-time one — any observable
@@ -813,11 +796,12 @@ Options:
   --seen-queued                  Resume hint only: keep phases/callers aware the PR was queued.
                                  Does NOT seed lost-membership counting — membership must be
                                  observed in this process (everActive) before DEQUEUED can fire.
-  --quiet                        Suppress the per-poll progress heartbeat on stderr
+  --quiet                        Suppress delivery/readability transition records on stderr
 
 Output:
   stdout  exactly one pretty-printed terminal JSON verdict, at exit
-  stderr  one compact JSON progress record per poll (progress:true), unless --quiet;
+  stderr  one compact JSON record per delivery/readability change (activity:true, progress:<the delivery state
+          actually changed>), unless --quiet;
           plus one {"warning":"slow-ci-job"} record per CI job that runs past
           --slow-job-minutes (emitted even with --quiet); and, last of all, one
           {"ciProfileSummary":true} line (outcome, profile verdict, slow jobs) so a
@@ -882,6 +866,7 @@ export async function runCli(argv) {
   let missingActiveReads = 0
   let stallObservationCache = null
   let lastChangeMs = startedMs
+  let lastReadability = null
   let observations = 0
   let phases = []
   let lastBatchPrNumber = null
@@ -890,7 +875,7 @@ export async function runCli(argv) {
   const warnedSlowJobs = new Set()
   const slowThresholdMs = args.slowJobMinutes * 60_000
   // Warn once per slow job run. Warnings go to stderr even under --quiet: they are the point
-  // of profiling, and --quiet only silences the routine heartbeat.
+  // of profiling, and --quiet only silences routine transition records.
   const warnSlowJobs = () => {
     for (const { key, job } of newSlowJobs(ciJobs, { thresholdMs: slowThresholdMs, warned: warnedSlowJobs })) {
       warnedSlowJobs.add(key)
@@ -1025,12 +1010,12 @@ export async function runCli(argv) {
       lastChangeMs = Date.now()
     }
 
-    // Heartbeat before the bound checks below, so the last thing in the log before a STALLED
-    // verdict is the unchanging observation that produced it — see `progressRecord`.
-    if (!args.quiet) {
+    const readability = JSON.stringify([pr.readable !== false, queue.readable !== false])
+    if (!args.quiet && (changed || readability !== lastReadability)) {
       const now = Date.now()
       console.error(progressRecord({ payload, changed, sinceChangeMs: now - lastChangeMs, nowIso: new Date(now).toISOString() }))
     }
+    lastReadability = readability
 
     const elapsedMs = Date.now() - startedMs
     if (elapsedMs >= args.maxMinutes * 60_000) {

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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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: API key for direct xAI or the explicitly configured Responses gateway
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **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, write-report or plain-language. Preserve manual edits and separate document types. NOT for drafting a document (write-doc) or analytical report (write-report) or saving chat-only preferences (plain-language)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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, write-report and domain report skills. NOT for Chinese wording (polish-cn) or code review (better-review)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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 analytical report (write-report) or reviewing one (editorial-review)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **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 or write-report)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **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), writing a gap-analysis report (write-report), or writing a policy from the checklist (write-doc)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **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 analytical reports (write-report) or the code domain model (domain-modeling)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **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 that define or propose something: BRD, PRD, technical spec, integration guide, proposal, policy or risk procedure; English, Chinese or bilingual. Use automatically for drafting or revising these documents. Markdown by default; export when requested. NOT for analytical reports or writing up findings (write-report), ordinary chat replies (plain-language), learning style or saving preferences alone (distill-writing), performing an audit (compliance-audit), or WeChat articles (wechat-article-writer)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Write a document

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

@@ -1,7 +1,7 @@
 ---
 name: write-report
 description: "Write or edit analytical reports from data, research, analysis or findings: payment, fraud, operational, performance, research, gap-analysis, audit, external assessment, management and Visa VARS reports. Use whenever asked to report results, write up findings, or turn analysis into a report, even without naming this skill. English, Chinese or bilingual; Markdown by default, export when requested. NOT for defining requirements, policies or proposals (write-doc), performing the underlying domain analysis or audit, chat-only answers (plain-language), or learning house style (distill-writing)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Write an analytical report

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.50.1
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Better Review

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

@@ -1,7 +1,7 @@
 ---
 name: e2e-test
 description: "Playwright end-to-end guidance for affected browser journeys, render health and presentation checks, with route manifests and sweeps for broader audits. 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.50.1
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # E2E Testing Standard

package/skills/engineering/engineering/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: engineering
 description: "Engineering conventions: feature-delivery priorities, focused verification and review, operational boundaries, and tracker routing. Standalone /engineering offers Global, Project, or Session setup and targeted resets for configured scopes; /engineering init keeps explicit project setup. Use when setting up AGENTS.md or CONTRIBUTING.md, saving or resetting engineering defaults, or before creating an engineering issue, spec, epic, ticket, or sub-issue on GitHub or Linear. Reads existing policy without writing during ordinary work. NOT the issue-to-PR workflow (resolve-issues), release execution (resolve-release), Git delivery (github-flow), or CI setup (github-actions)."
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Engineering

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.50.1
+release-version: 0.50.2
 ---
 **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": "528de8e948bcd1cfdbe92bcb4c14129cbb78d5d9037d8d378d5ac540017cd248",
+      "contentDigest": "522a4876e0519a4163ff85976caa478a024aaacb3115f1e0cb1b4ac2832c90df",
       "digestExcludes": []
     },
     {
@@ -382,7 +382,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "1b1074c002a7d3ca2dfebe625b65128aee10a662f7f9d4060a018fbaecf3225f",
+      "contentDigest": "e1d2a60487eec9d1fd4fec1a4f0357069904db25577c08b811a72106da86c140",
       "digestExcludes": []
     },
     {
@@ -395,7 +395,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "61d744eeddd5b3a5d2fa7a94ea01ec3a570c72a7c19ad526761f21aac993abff",
+      "contentDigest": "81c172a2db0fe9750447af937247b8e6aed9c47928db1c0e003bba7e5c64bbc3",
       "digestExcludes": []
     },
     {
@@ -408,7 +408,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "3140da610485146538ee76048446ea7bac8927890a1469eb8108e63e4056d655",
+      "contentDigest": "351eaa56339849c1994c0d5735a287d5bb1aabc02225b93336b1bbc547696390",
       "digestExcludes": []
     },
     {
@@ -421,7 +421,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "12f5230e47afdeab750cb6b1454b3172edb29b922155b2994e96a93f386b6dbd",
+      "contentDigest": "6a1a1689ae2616d2f6f4afe4442ec72f0a54e8d829ddbf38546ed0d881a14da1",
       "digestExcludes": []
     },
     {
@@ -434,7 +434,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "b8d908580483f3954545e392c11d439ed100688eadc3b41ce508569f6dddc3bc",
+      "contentDigest": "b740e99373209a7691f412d5bf7e685d82f5a50a1943ef2fd75f0395048aec4a",
       "digestExcludes": []
     },
     {
@@ -447,7 +447,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "256eac4a31f95d536ef487359df4c84fe7e85436c3b7550f6200f1b15cca4d0b",
+      "contentDigest": "d6589a126bc271d6b7953fc68c316c3f5b229c34215c3624074c0ffe657ef718",
       "digestExcludes": []
     },
     {
@@ -460,7 +460,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "25ad674c96748cb5313d13c80dd1ac4be5bdb287e75e7f978d8e5b97f5892833",
+      "contentDigest": "e38611409ef33c5b33ae489c43c476f85e176003db7d24b031891e52c2875d8e",
       "digestExcludes": []
     },
     {
@@ -473,7 +473,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "1d10c734eaef6bb20bf99bf9fa6dcfde6460ea2eecb84c33d7c0474e470684a9",
+      "contentDigest": "7f78a80abbadcc3bfdf9d70f477b26370758d4ad3a3f860c1b73db5d3166c10a",
       "digestExcludes": []
     },
     {
@@ -486,7 +486,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "229a6d752c9b17c298172a022c36f8e28e409d665df4ed89f1655c17f37db3f3",
+      "contentDigest": "ae28f9f440c015a3ac9935cd050f8d489d6355172cb3cff5df72ab50e1c7dc89",
       "digestExcludes": []
     },
     {
@@ -499,7 +499,7 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "c44aa11db1f62995c8b77929143892e421d7068193c959930c8af4fbe8a2d7f5",
+      "contentDigest": "ffc64d184a564bcc131edb40d2b71ecfb63ba96a53cb25d810235e09ad0222b4",
       "digestExcludes": []
     },
     {
@@ -512,13 +512,13 @@
         "repository": "1aboveio/ai",
         "revision": "main"
       },
-      "contentDigest": "14439c4b1390b3dde50dcf8d56ff5c578bbbe08b17627f7bd504db099ba5e92a",
+      "contentDigest": "3f11192933319bed874a91b004a2f41629a74b3d5f44e0c27d6a8ba2b31ce2dd",
       "digestExcludes": [
         "coherence/workflow.json"
       ]
     }
   ],
-  "releaseIdentity": "d7ab71565826655a05f576e53932870e4d0176329a1b4110a460457e5cb2d0b8",
+  "releaseIdentity": "40e572635a1e002b4ab249a50b88a1e07cc59a64d8fcb39b5efa91c3bd6091ff",
   "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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **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.50.1
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Harness Runtime
@@ -14,6 +14,7 @@ This support-only runtime package exposes shared programmatic contracts plus can
 
 - `contracts.md` defines the neutral values, planner boundary, discovery handoff, and topology rules.
 - `native-question-contracts.md` pins the Pi, Codex, and Claude Code adapter schemas and response behavior.
+- Read [references/subagent-sessions.md](references/subagent-sessions.md) when continuing a Pi worker: it distinguishes attempt ids from native session ids, checks the active spawn schema, and defines local/global discovery.
 - `index.mjs` exports neutral constructors plus pure question planning and response normalization.
 - `agent-catalog.mjs` is the consumer bridge to the harness-owned agent catalog: it resolves the four worker roles for a harness, with no skill-owned ladder and an explicit blocked result when no resolver is available.
 - `discover-models.mjs` enumerates model evidence; `model-catalog.mjs` manages per-harness classifications. Both remain import-compatible for existing consumers and are no longer used to select model slots.

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

@@ -8,6 +8,8 @@ Question and answer values are harness-neutral immutable data. `planStructuredQu
 
 Model discovery unions explicit current-turn spawn ids and human-named runnable ids with configured or credentialed evidence. Its `{ discovered: [{ id, source }] }` output is evidence, not a neutral model-availability value: callers map each item to `{ id, sources: [source] }`, preserve `harness` and `completeness`, then pass that shape to `defineModelAvailability`; discovery `notes` remain operator diagnostics. Pi labels configuration discovery `full` even when it finds no runnable ids because its credential-aware configuration is the complete evidence class. Codex and Claude Code static configuration remains partial unless current-turn or runtime-enumeration evidence completes it. Catalog writes remain isolated to each harness's user directory, and the installation-relative team seed is read-only.
 
+For saved Pi worker conversations, read [subagent session contracts](references/subagent-sessions.md) before choosing a continuation call. The active spawn schema determines capability; the native session id selects the conversation, while the returned attempt id tracks one execution. This reference adds no inferred tools to the neutral capability value.
+
 Shell code cannot invoke a native question tool inside the agent's current turn. It may validate and plan data; the agent performs each planned native tool call and passes the responses back for normalization.
 
 When no supported native question tool is advertised, concise free-text input is permitted only for one optionless question. Textual multiple-choice emulation is forbidden. Unsupported multi-select and all secret input fail explicitly rather than degrading silently.

package/skills/engineering/harness-runtime/references/subagent-sessions.md

@@ -0,0 +1,75 @@
+# Saved subagent conversations on Pi
+
+Use this contract when an engineering workflow continues a Pi worker after its
+attempt has finished. Other harnesses use their advertised continuation API.
+
+## Check the active interface
+
+Read the tool schema advertised in the current turn. Continuation requires
+`subagent_spawn` with `session_id`; a tool name or an installed package version
+alone does not establish that the running extension has loaded that parameter.
+A stale running extension may need the human's `/reload` after an update. Report
+that mismatch and use the workflow's documented fallback; updating packages or
+changing tool permissions is a separate authorized action.
+
+## Record the conversation separately from the attempt
+
+Keep these values from the actual launch receipt:
+
+- `runId`: the attempt used for results, failures, logs, and the active worker slot.
+- `sessionId`: the native Pi conversation used for later follow-up.
+- `cwd`: the worker's recorded workspace.
+
+Every continuation creates a new `runId` while keeping `sessionId`. Read the
+native session id from the structured receipt, batch launch entry, or explicit
+`session_id` in list output. An attempt id is not a substitute, even when the two
+happen to match on the first launch.
+
+For an older plan missing `sessionId`, locate the exact recorded `runId` in
+`subagent_list` and record its native `session_id` before continuing. Use
+`all: true` when it is outside the caller's folder. If that identity cannot be
+verified, report unavailable continuity and follow the workflow's explicit
+replacement path with its saved evidence.
+
+## Continue through spawn
+
+```javascript
+subagent_spawn({ session_id: owner.sessionId, prompt: "Fix the remaining findings." })
+```
+
+The prompt is the next turn, not a repetition of the original assignment or role.
+Keep the saved worker configuration; pass model or effort only for an explicit,
+authorized escalation supported by the current schema. Record the returned new
+attempt id and verify that its session id is still the selected conversation.
+Per-job `session_id` in `subagent_spawn_batch` has the same meaning; the shared
+batch options do not select one conversation for every job.
+
+The caller may be a different foreground session. Completion reports to that
+caller. Continue from a completed attempt; a running or orphaned writer must
+settle before another continuation starts. A failed, killed, lost, or otherwise
+refused attempt follows the workflow's recovery or replacement rules rather than
+selecting an older completion. Current mandatory permissions still apply.
+Missing history or workspace is a refusal, not permission to create a replacement
+conversation under the same identity.
+
+## Discover locally or globally
+
+`subagent_list()` searches the current folder and descendants across foreground
+sessions. `subagent_list({ all: true })` searches globally. Each row identifies
+both the attempt and the saved conversation. `session_name` is a convenience for
+one exact, unambiguous name in the local folder scope; a workflow with recorded
+ownership uses its exact `sessionId` rather than choosing a worker by name.
+Duplicate names require an explicit session id.
+
+## Keep the lifecycle small
+
+Native session history and completed launch recipes persist by default.
+`subagent_resume`, `subagent_release`, and `retain_session` are not part of this
+contract. A completed attempt frees its capacity slot automatically. Ordinary
+workspace/resource cleanup remains owned by the workflow; no session-release
+acknowledgement is required. Preserving history does not keep a deleted workspace
+available for later continuation.
+
+Keep the implementation conversation through repairs. An unfinished review may
+continue only within the workflow's existing HEAD and scope rules. A completed
+independent review round gets a fresh reviewer for the next required round.

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

@@ -8,7 +8,7 @@ dependencies:
   - better-review
   - golden-path
   - harness-runtime
-release-version: 0.50.1
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Resolve issues
@@ -187,7 +187,7 @@ efforts are run metadata, never a question.
 ### 2. Implement and open the PR
 
 Give each unit a branch, its prepared workspace, and an implementer with its findings entry
-and parents' contracts; retain its [implementation owner](references/implementation.md#implementation-owner)
+and parents' contracts; keep its [implementation owner](references/implementation.md#implementation-owner)
 through review/CI fixes, separately from its active worker slot. State outcome and validation, not method. Refill
 slots at once. At a unit's first coherent commit its PR opens as a draft, so CI
 starts and the work is safe; later work goes to the same PR (in a Mergify stack

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

@@ -117,10 +117,8 @@ provider shows that PR merged.
 
 Clean that unit's workspace and resources, then finish it, in every scheduler
 mode: `next-actions.mjs` prints `cleanup-workspace` until its cleanup settles.
-First [release any session retention still held](implementation.md#settle-session-retention)
-for it, even while other units remain active; a conversation launched without protection has
-nothing to release. Then record the intent through the [checkpoint mechanism](task-plan.md#checkpoints) (`lifecycle.cleanup`
-`{state: applying, headSha: <the unit's headSha>}`), then run:
+Record the intent through the [checkpoint mechanism](task-plan.md#checkpoints) (`lifecycle.cleanup`
+`{state: applying, headSha: <the unit's headSha>}`), while other units remain active, then run:
 
 ```bash
 node <skill-base-dir>/scripts/cleanup-runs.mjs cleanup --run <run> --unit <unit> \