@1aboveio/skills 1.0.12 → 1.0.14

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

@@ -1,7 +1,7 @@
 ---
 name: cloud-build
 description: "Build or debug Cloud Build pipelines for Cloud Run: cloudbuild.yaml, triggers, Artifact Registry, builds, migrations, deploys, secrets, VPC, notifications. Use cloud-deploy for staged promotion. NOT for GitHub Actions PR checks (github-actions)."
-release-version: 0.45.1
+release-version: 0.46.0
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Cloud Build Direct Deploy to Cloud Run

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

@@ -1,7 +1,7 @@
 ---
 name: cloud-debug
 description: "Debug Cloud Build or Deploy failures: builds, deployments, health checks, and pipeline errors. Inputs: service, build ID, region. NOT for GitHub Actions runs (github-actions) or runtime errors in a running service (app-debug)."
-release-version: 0.45.1
+release-version: 0.46.0
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Cloud Build & Cloud Deploy Debug Skill

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

@@ -5,7 +5,7 @@ description: >
   CI/CD pipelines with staged promotion, verification gates, or GitFlow branching.
   Also use when debugging Cloud Deploy pipeline failures. NOT for simple single-container
   deploys — use cloud-build instead.
-release-version: 0.45.1
+release-version: 0.46.0
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Cloud Deploy + Skaffold + Kustomize for Cloud Run

package/skills/cicd/docker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: docker
 description: Docker/Podman container architecture and build patterns. Read when designing or reviewing containerization, Dockerfile structure, multi-stage builds, PyPI mirror support, or docker-compose setup for Python/uv projects, and when a Dockerfile's dependency install misses the layer cache on every build (build args such as a commit SHA or version declared too early) or an image build is slow in CI.
-release-version: 0.45.1
+release-version: 0.46.0
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Docker Build Patterns

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

@@ -1,7 +1,7 @@
 ---
 name: github-actions
 description: "Author, review, audit, profile, optimize, or debug GitHub Actions workflows (.github/workflows/*.yml): run-history audits, job and step timing, resource bottlenecks, before/after comparisons, conditional CI by changed path, the one required gate check, PR and merge-queue lanes, sharding, workers, caching, self-hosted runners, timeouts, concurrency, permissions and action pinning, post-deploy verification, npm publishing. Use for 'set up CI', 'CI is slow', 'profile CI', 'optimize our pipeline', 'audit CI for redundant or wasted jobs', 'why is this check stuck expected or never started', 'harden this workflow', or 'browser not found on the runner'. NOT for pushing, opening, or merging a PR, or writing CI conventions into CONTRIBUTING.md (github-flow), queue rules or a check unmet inside Mergify (mergify), Playwright config and specs (e2e-test), cloudbuild.yaml or Cloud Run deploys (cloud-build), or which gates a repo must prove (ensure-coverage)."
-release-version: 0.45.1
+release-version: 0.46.0
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # GitHub Actions

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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **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.45.1
+release-version: 0.46.0
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Engineering
@@ -140,8 +140,8 @@ resolve the destination before any issue creation. Never infer a Linear project.
 
 | File or section | Init owns |
 | --- | --- |
-| `AGENTS.md` | Missing `Feature delivery` section and a pointer to `CONTRIBUTING.md` |
-| `CONTRIBUTING.md` | Missing `Engineering conventions`, `Testing conventions`, and `Issue tracking` sections |
+| `AGENTS.md` | Missing pointer to `CONTRIBUTING.md`; no policy sections |
+| `CONTRIBUTING.md` | Missing `Feature delivery`, `Engineering conventions`, `Testing conventions`, and `Issue tracking` sections |
 
 The templates are [feature delivery](references/feature-delivery.md),
 [engineering conventions](references/engineering-conventions.md),
@@ -152,6 +152,12 @@ without invoking its writer. `test-quality` owns the testing rules and deliberat
 updates; init only adds a missing section. The [skill review](references/init-scope.md)
 explains what is included and what remains opt-in.
 
+Project policy lives in `CONTRIBUTING.md`; `AGENTS.md` carries only the loader. A
+`Feature delivery` section already in `AGENTS.md`, including one an earlier init wrote,
+stays where it is: init neither migrates nor deletes it, and it does not add a competing
+copy to `CONTRIBUTING.md`. Existing `CONTRIBUTING.md` policy wins the same way.
+Initialization moves no existing rules between files and refreshes neither.
+
 Existing sections, including legacy `conventions:tracker` blocks written by
 `contributing`, are preserved byte-for-byte. Repeated init is not a refresh and
 leaves manual edits unchanged. No force/update mode is implied. If policy needs to

package/skills/engineering/engineering/references/init-scope.md

@@ -15,7 +15,7 @@ not initialization sources; pinned external skills keep their upstream ownership
 
 | Skill | Include in guidance | Keep as a separate action |
 | --- | --- | --- |
-| engineering (formerly contributing) | Feature priorities, guidance lookup, tracker routing | Tracker refresh or project-policy changes |
+| engineering (formerly contributing) | Feature priorities, guidance lookup and tracker routing, written as `CONTRIBUTING.md` sections; `AGENTS.md` gets only the loading pointer | Tracker refresh or project-policy changes |
 | resolve-issues | Agreed outcome, bounded supporting work, explicit stopping point | Issue planning, workers, PRs, scheduling |
 | rush-issues | Same delivery principles as resolve-issues | Shortcut workflow invocation |
 | ensure-coverage | Smallest sufficient proof, stable acceptance, required checks preserved | Ledger adoption, broad audits, new gates |
@@ -37,8 +37,12 @@ not call other skills' convention writers: they own their sections and may need
 additional decisions. Init reads `test-quality`'s canonical template directly;
 the testing owner and `conventions:testing` section identity remain unchanged.
 Existing project sections, including old testing and tracker blocks, stay unchanged.
-Delivery, CI, and Data Catalog conventions require separate explicit setup with
-their owning skills. Setup may point to these capabilities without requiring them.
+Project policy is persisted in `CONTRIBUTING.md`, so `AGENTS.md` keeps only the short
+loader. A `Feature delivery` section written into `AGENTS.md` by an earlier release
+stays there: init does not migrate or delete it, and it does not add a competing copy
+to `CONTRIBUTING.md`. Delivery, CI, and Data Catalog conventions require separate
+explicit setup with their owning skills. Setup may point to these capabilities without
+requiring them.
 
 Stack-specific tools, commands, cloud projects, release branches, required gates,
 and golden paths are project facts, not defaults to manufacture. Read established

package/skills/engineering/engineering/references/scope-management.md

@@ -43,6 +43,10 @@ new global defaults or new loading pointer in unique `engineering:<id>:start/end
 comments before recording their hashes. Do not rewrap existing text or claim it as
 owned. Keep existing valid records and add only new entries; deduplicate entries.
 
+Project policy sections, including `Feature delivery` (`conventions:feature-delivery`),
+live in `CONTRIBUTING.md`; `AGENTS.md` holds only the loading pointer. Record a new
+pointer as an `engineering:<id>` loading addition, never as a policy section.
+
 Set `createdFile` only when this save created that file. Preserve unrelated bytes
 and existing links. Do not create a sidecar, global settings entry, or project file
 for a session choice. A repeated save with no additions leaves files unchanged.
@@ -73,6 +77,11 @@ scope's saved defaults, not a reinstall, refresh, or reset of every scope.
 5. Remove owned loading pointers only if they are unchanged and no longer needed
    by retained guidance. Keep a pointer that still loads user policy. Remove an
    empty ownership record and any empty wrapper heading added by this save.
+   For a legacy `Feature delivery` section in `AGENTS.md`, honor a valid existing
+   ownership record and unchanged hash under step 3, even if an earlier initializer
+   recorded it. Preserve and report unrecorded or edited policy under step 4; do not
+   infer ownership from its location or migrate it during reset. Keep the pointer
+   while retained `CONTRIBUTING.md` policy still needs it.
    Delete a file only if `createdFile` proves this skill created it and nothing
    except the original generated title and whitespace remains. Preserve pre-existing
    files, symlinks, hand edits, and unrelated sections; never delete an instruction

package/skills/engineering/engineering/scripts/init.mjs

@@ -2,7 +2,7 @@
 import fs from 'node:fs'
 import path from 'node:path'
 import { spawnSync } from 'node:child_process'
-import { fileURLToPath } from 'node:url'
+import { fileURLToPath, pathToFileURL } from 'node:url'
 
 const reference = name => fs.readFileSync(fileURLToPath(new URL(`../references/${name}.md`, import.meta.url)), 'utf8').trim()
 const usage = 'node init.mjs [--repo-root <dir>] [--github-repo <owner/name>] [--linear-project <name>]... [--write]'
@@ -54,7 +54,7 @@ function append(current, body) {
   return `${current}${separator}${body.trim()}\n`
 }
 
-function preserveOrAdd(current, title, id, body) {
+function sectionState(current, title, id) {
   const start = `<!-- conventions:${id}:start -->`
   const end = `<!-- conventions:${id}:end -->`
   const starts = current.split(start).length - 1
@@ -62,8 +62,12 @@ function preserveOrAdd(current, title, id, body) {
   if (starts !== ends || starts > 1 || (starts && current.indexOf(start) > current.indexOf(end))) {
     throw new Error(`malformed ${title} section markers; preserve and repair existing guidance first`)
   }
-  if (starts || current.split(/\r?\n/).some(line => line.trim() === `## ${title}`)) return current
-  return append(current, `${start}\n${body}\n${end}`)
+  return Boolean(starts) || current.split(/\r?\n/).some(line => line.trim() === `## ${title}`)
+}
+
+function addSection(current, title, id, body) {
+  if (sectionState(current, title, id)) return current
+  return append(current, `<!-- conventions:${id}:start -->\n${body.trim()}\n<!-- conventions:${id}:end -->`)
 }
 
 function linkFrom(from, to) {
@@ -73,11 +77,14 @@ function linkFrom(from, to) {
 function hasLoader(current, from, to) {
   const links = /\[[^\]\r\n]*\]\(\s*(?:<([^>]+)>|([^\s)]+))(?:\s+["'][^"'\r\n]*["'])?\s*\)/g
   for (const match of current.matchAll(links)) {
-    const href = (match[1] ?? match[2]).split(/[?#]/)[0]
+    const href = match[1] ?? match[2]
     if (!href || /^[a-z][a-z\d+.-]*:|^\/\//i.test(href)) continue
     let target
     try {
-      target = path.resolve(path.dirname(from.target), decodeURIComponent(href))
+      const link = new URL(href, pathToFileURL(from.target))
+      if (link.hash) continue
+      link.search = ''
+      target = fileURLToPath(link)
     } catch {
       continue
     }
@@ -114,23 +121,38 @@ function planInitialization(root, options) {
     throw new Error('agent instructions and CONTRIBUTING.md must use distinct files')
   }
 
-  let agentText = preserveOrAdd(agents.current ?? '# Agent instructions\n', 'Feature delivery',
-    'feature-delivery', reference('feature-delivery'))
+  // AGENTS.md loads the policy; it does not carry it. Init adds only the pointer.
+  const agentBase = agents.current ?? '# Agent instructions\n'
+  // An earlier release put Feature delivery in AGENTS.md. That policy stays where it is:
+  // init neither migrates it nor adds a competing copy to CONTRIBUTING.md.
+  const featureDeliveryInAgents = sectionState(agentBase, 'Feature delivery', 'feature-delivery')
+  let agentText = agentBase
   if (!hasLoader(agentText, agents, contributing)) {
     agentText = append(agentText, `## Contributing\n\nFollow [CONTRIBUTING.md](${linkFrom(agents, contributing)}) for this project's engineering conventions and existing delivery requirements.`)
   }
 
-  let contributingText = preserveOrAdd(contributing.current ?? '# Contributing\n', 'Engineering conventions',
+  let contributingText = contributing.current ?? '# Contributing\n'
+  const featureDeliveryInContributing = sectionState(contributingText, 'Feature delivery', 'feature-delivery')
+  if (!featureDeliveryInAgents && !featureDeliveryInContributing) {
+    contributingText = addSection(contributingText, 'Feature delivery', 'feature-delivery',
+      reference('feature-delivery'))
+  }
+  contributingText = addSection(contributingText, 'Engineering conventions',
     'engineering', reference('engineering-conventions'))
   const testing = fs.readFileSync(new URL('../../test-quality/references/testing-conventions.md', import.meta.url), 'utf8').trim()
-  contributingText = preserveOrAdd(contributingText, 'Testing conventions', 'testing', testing)
-  contributingText = preserveOrAdd(contributingText, 'Issue tracking', 'tracker',
+  contributingText = addSection(contributingText, 'Testing conventions', 'testing', testing)
+  contributingText = addSection(contributingText, 'Issue tracking', 'tracker',
     trackerBody(options.githubRepo ?? githubRepo(root), options.linearProjects))
 
-  return [
-    { ...agents, next: agentText },
-    { ...contributing, next: contributingText },
-  ]
+  return {
+    entries: [
+      { ...agents, next: agentText },
+      { ...contributing, next: contributingText },
+    ],
+    notes: featureDeliveryInAgents
+      ? ['Feature delivery stays in AGENTS.md; no competing section added to CONTRIBUTING.md']
+      : [],
+  }
 }
 
 function main(argv) {
@@ -142,13 +164,14 @@ function main(argv) {
   const selected = options.repoRoot ?? gitOutput(process.cwd(), ['rev-parse', '--show-toplevel']) ?? process.cwd()
   const root = fs.realpathSync(selected)
   if (!fs.statSync(root).isDirectory()) throw new Error('project root is not a directory')
-  const plan = planInitialization(root, options)
+  const { entries, notes } = planInitialization(root, options)
   console.log(`engineering init: ${options.write ? 'write' : 'preview only'} (${root})`)
-  for (const entry of plan) {
+  for (const entry of entries) {
     const action = entry.current === entry.next ? 'unchanged' : entry.current === null ? 'create' : 'update'
     if (options.write && action !== 'unchanged') fs.writeFileSync(entry.target, entry.next)
     console.log(`  ${entry.name}: ${!options.write && action !== 'unchanged' ? 'would ' : ''}${action}`)
   }
+  for (const note of notes) console.log(`  note: ${note}`)
   console.log('Existing sections are preserved; initialization does not refresh project policy or authorize delivery actions.')
 }
 

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.45.1
+release-version: 0.46.0
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Engineering Runtime