diff --git a/.agents/skills/apm-workflow/references/apm-bootstrap.json b/.agents/skills/apm-workflow/references/apm-bootstrap.json index b27efca..d8cca87 100644 --- a/.agents/skills/apm-workflow/references/apm-bootstrap.json +++ b/.agents/skills/apm-workflow/references/apm-bootstrap.json @@ -1,40 +1,40 @@ { - "version": "v0.34.0", - "published_at": "2026-10-19T12:00:55Z", + "version": "v0.35.0", + "published_at": "2026-10-22T22:51:41Z", "cooldown_days": 7, - "eligible_on": "2026-10-26T12:00:55Z", - "release_url": "https://github.com/microsoft/apm/releases/tag/v0.34.0", + "eligible_on": "2026-10-29T22:51:41Z", + "release_url": "https://github.com/microsoft/apm/releases/tag/v0.35.0", "download_url_template": "https://github.com/microsoft/apm/releases/download/{version}/{asset}", "assets": [ { "platform": "macos-arm64", "archive": "apm-darwin-arm64.tar.gz", "extracted_directory": "apm-darwin-arm64", - "sha256": "030b381825799333ac60a369aaf021ffc9f9e92558b375feec656c42e50e8e5a" + "sha256": "cb2c54152e3bd39acfe2fbda4a2aa91d2af914e24859d3623423efd7b27e3dd0" }, { "platform": "macos-x86_64", "archive": "apm-darwin-x86_64.tar.gz", "extracted_directory": "apm-darwin-x86_64", - "sha256": "55b4ab44eaca6f3a56f59a8e9ca84082c9ed3333a76fe255d6bc62c2a14678a9" + "sha256": "ee17daf433c49ed481d9f2ddee31825cbced9390637cab9a5138815bbace327c" }, { "platform": "linux-arm64", "archive": "apm-linux-arm64.tar.gz", "extracted_directory": "apm-linux-arm64", - "sha256": "bf355449cbb74b960e3a6ebe851a35ec2c1df6f5178fbb36b90c5a3a015d2c2a" + "sha256": "ada8901ce1b29e5d188629eeed64e8499853a8cb5f047630ebedbde24008508e" }, { "platform": "linux-x86_64", "archive": "apm-linux-x86_64.tar.gz", "extracted_directory": "apm-linux-x86_64", - "sha256": "4487af55604b4fa6f4587f3ee6e833b44ce99c491f11069790e4e13e297cde8c" + "sha256": "5aa23ce61eebae9411668f507772cdb5d87252c760078dc59b5acdc5188d785b" }, { "platform": "windows-x86_64", "archive": "apm-windows-x86_64.zip", "extracted_directory": "apm-windows-x86_64", - "sha256": "e9b3dd16b8533af681ea70128ceb8baed983c47cd73d0488ff28dbd5df85def0" + "sha256": "9a0a912b3ba68ac154b940e1931425c85f03edcfcc2339661d3aa32d8fa17c2f" } ] } diff --git a/.agents/skills/code-quality-check/README.md b/.agents/skills/code-quality-check/README.md index b4a72ed..ac0f3a3 100644 --- a/.agents/skills/code-quality-check/README.md +++ b/.agents/skills/code-quality-check/README.md @@ -2,7 +2,8 @@ ## Overview -Review implementation changes for readability, maintainability, and verification. +Review implementation changes for readability, maintainability, verification, +and evidence-backed migration or compatibility needs. ## Install diff --git a/.agents/skills/code-quality-check/SKILL.md b/.agents/skills/code-quality-check/SKILL.md index 24eaff8..b6b915c 100644 --- a/.agents/skills/code-quality-check/SKILL.md +++ b/.agents/skills/code-quality-check/SKILL.md @@ -26,9 +26,10 @@ description: >- 1. Read the changed files and nearby call sites, not just the patch. 2. Identify code that is hard to scan, overly nested, duplicated, misleadingly named, or coupled to hidden assumptions. -3. When a change adds future-facing structure, abstraction, validation, dependencies, tests, or - defensive behavior, use [avoiding overengineering](references/avoiding-overengineering.md) to - check that each addition has a current consumer, contract, failure mode, or evidenced risk. +3. When a change adds future-facing structure, abstraction, validation, dependencies, tests, + compatibility layers, migration paths, or defensive behavior, use + [avoiding overengineering](references/avoiding-overengineering.md) to check that each addition has + a current consumer, contract, failure mode, or evidenced risk. 4. Make safe local readability refactors where practical. 5. Add or update comments only when the design intent is not obvious from the code and cannot be made obvious with a small refactor. diff --git a/.agents/skills/code-quality-check/references/avoiding-overengineering.md b/.agents/skills/code-quality-check/references/avoiding-overengineering.md index de93ffe..ef837f8 100644 --- a/.agents/skills/code-quality-check/references/avoiding-overengineering.md +++ b/.agents/skills/code-quality-check/references/avoiding-overengineering.md @@ -1,5 +1,14 @@ # Avoiding overengineering +## Contents + +- [Purpose](#purpose) +- [Decision rule](#decision-rule) +- [Migration and backward compatibility](#migration-and-backward-compatibility) +- [Common review examples](#common-review-examples) +- [Boundaries that justify structure](#boundaries-that-justify-structure) +- [Review outcome](#review-outcome) + ## Purpose Use this reference when a change introduces structure or safeguards beyond the direct feature edit. @@ -57,6 +66,41 @@ Ask these questions during review: An unclear answer is a reason to defer or narrow the addition, not proof that it is unnecessary. Investigate high-impact correctness and security uncertainty before removing a safeguard. +## Migration and backward compatibility + +Before adding migration code, compatibility shims, legacy formats, or upgrade +instructions, establish the transition that actually needs support: + +- Which released behavior, persisted data, deployed configuration, external + caller, or user workflow must continue to work or move to the new state? +- What breaks under a direct change, and what evidence establishes the affected + consumers and the supported old-to-new boundary? +- Does that boundary need automated conversion, temporary compatibility, a + later user/operator action, or only a coordinated change within this task? + +A rename, internal refactor, or new feature does not establish a migration +requirement by itself. When no supported old state or consumer needs a +transition, update the current implementation and its canonical documentation +without inventing legacy readers, version switches, upgrade machinery, or a +permanent migration guide. Keep transient implementation steps and migration +history in the PR when no later reader needs a procedure. Preserve rationale +needed to understand or maintain current behavior in canonical architecture +docs or nearby comments. + +When a real transition exists, choose the smallest path that preserves the +required contract and data. Keep migration or compatibility support, focused +verification, and instructions for affected users/operators when they will need +them after the PR. A migration performed once by each installation can still +need lasting upgrade documentation. Use `domain-architecture-docs-workflow` to +choose the maintained document and audience; link rather than duplicate it in +the PR. Bound compatibility support to the supported versions or formats and +record a removal condition only when the support policy establishes one. + +Unknown deployment, data, or caller state is a reason to investigate, not proof +that a direct breaking change or data reset is safe. Preserve existing migration +and recovery safeguards while investigating their consumers and retirement +conditions. Do not remove protection merely because it looks old or costly. + ## Common review examples | Situation | Proportionate change | Likely overengineering | diff --git a/.agents/skills/docker-quality-check/assets/github/actions/check-docker-source/action.yml b/.agents/skills/docker-quality-check/assets/github/actions/check-docker-source/action.yml index 81c3bd6..bf96a81 100644 --- a/.agents/skills/docker-quality-check/assets/github/actions/check-docker-source/action.yml +++ b/.agents/skills/docker-quality-check/assets/github/actions/check-docker-source/action.yml @@ -7,7 +7,7 @@ runs: - name: Set up reviewed APM CLI uses: microsoft/apm-action@d723bb64ed70c135bbaf87d126b721dd2dae0439 # v1.10.0 with: - apm-version: "0.28.0" + apm-version: "0.35.0" setup-only: "true" - name: Audit APM deployment @@ -15,7 +15,7 @@ runs: run: apm audit --ci - name: Lint Markdown source - uses: DavidAnson/markdownlint-cli2-action@21c1be1b93ad9ed58fa840aacc3f279cde2a72ff # v24.2.0 + uses: DavidAnson/markdownlint-cli2-action@696eb3f2509270d7b882d2aa68347bc676e7af34 # v25.0.0 with: config: .markdownlint-cli2.yaml globs: "**/*.md" diff --git a/.agents/skills/docker-quality-check/assets/github/workflows/main.yml b/.agents/skills/docker-quality-check/assets/github/workflows/main.yml index 2429f20..b51c387 100644 --- a/.agents/skills/docker-quality-check/assets/github/workflows/main.yml +++ b/.agents/skills/docker-quality-check/assets/github/workflows/main.yml @@ -28,10 +28,10 @@ jobs: uses: ./.github/actions/check-docker-source - name: Set up Docker Buildx - uses: docker/setup-buildx-action@bb05f3f5519dd87d3ba754cc423b652a5edd6d2c # v4.2.0 + uses: docker/setup-buildx-action@f87e5991a6d7451dcb8d9637bfbc97413f497069 # v4.4.1 - name: Check Docker build configuration - uses: docker/build-push-action@53b7df96c91f9c12dcc8a07bcb9ccacbed38856a # v7.3.0 + uses: docker/build-push-action@c3c9e263c25d99ce0380d002d59b67737d91b0dc # v7.4.0 with: call: check context: . @@ -52,10 +52,10 @@ jobs: persist-credentials: false - name: Set up Docker Buildx - uses: docker/setup-buildx-action@bb05f3f5519dd87d3ba754cc423b652a5edd6d2c # v4.2.0 + uses: docker/setup-buildx-action@f87e5991a6d7451dcb8d9637bfbc97413f497069 # v4.4.1 - name: Build Docker image without publishing - uses: docker/build-push-action@53b7df96c91f9c12dcc8a07bcb9ccacbed38856a # v7.3.0 + uses: docker/build-push-action@c3c9e263c25d99ce0380d002d59b67737d91b0dc # v7.4.0 with: context: . file: ./Dockerfile diff --git a/.agents/skills/docker-quality-check/assets/github/workflows/pull-request.yml b/.agents/skills/docker-quality-check/assets/github/workflows/pull-request.yml index 3cafa7b..c988f16 100644 --- a/.agents/skills/docker-quality-check/assets/github/workflows/pull-request.yml +++ b/.agents/skills/docker-quality-check/assets/github/workflows/pull-request.yml @@ -31,10 +31,10 @@ jobs: uses: ./.github/actions/check-docker-source - name: Set up Docker Buildx - uses: docker/setup-buildx-action@bb05f3f5519dd87d3ba754cc423b652a5edd6d2c # v4.2.0 + uses: docker/setup-buildx-action@f87e5991a6d7451dcb8d9637bfbc97413f497069 # v4.4.1 - name: Check Docker build configuration - uses: docker/build-push-action@53b7df96c91f9c12dcc8a07bcb9ccacbed38856a # v7.3.0 + uses: docker/build-push-action@c3c9e263c25d99ce0380d002d59b67737d91b0dc # v7.4.0 with: call: check context: . diff --git a/.agents/skills/prose-quality-check/README.md b/.agents/skills/prose-quality-check/README.md index 4339e53..7d22eb5 100644 --- a/.agents/skills/prose-quality-check/README.md +++ b/.agents/skills/prose-quality-check/README.md @@ -2,7 +2,11 @@ ## Overview -Review explanatory prose for readability, local structure, and preserved nuance. +Review explanatory prose for readable structure, self-contained context, and preserved nuance. +Balance section, paragraph, sentence, and list size without fixed length limits. +Remove unnecessary time dependencies and make useful time boundaries explicit in durable documents. +Omit redundant qualifiers and unintended differences between parallel statements +while retaining distinctions readers need. ## Install diff --git a/.agents/skills/prose-quality-check/SKILL.md b/.agents/skills/prose-quality-check/SKILL.md index fadb49f..3359d80 100644 --- a/.agents/skills/prose-quality-check/SKILL.md +++ b/.agents/skills/prose-quality-check/SKILL.md @@ -2,8 +2,8 @@ name: prose-quality-check description: >- Review or revise explanatory prose for readability, local structure, - audience fit, and preserved nuance. Use for wording in documentation, - comments, release notes, issues, pull requests, changelogs, handoff notes, + audience fit, self-contained context, and preserved nuance. Use for wording + in documentation, comments, release notes, issues, pull requests, changelogs, handoff notes, and Agent Skills after the document's purpose and factual ownership are known. Use domain-architecture-docs-workflow instead for repository-wide document maps, canonical ownership, technical evidence, coverage, or migration. @@ -11,111 +11,175 @@ description: >- # Prose Quality Check +## When to Use + +Use this Skill when the destination, factual source, and ownership are known +and the task is to improve how the text communicates. Use +`domain-architecture-docs-workflow` for repository-wide document maps, +canonical ownership, evidence, coverage, or migration decisions, then return +here to refine the prose. Flag unsupported technical claims rather than +silently repairing them through copyediting. + ## Goals -- Make prose easy to scan without flattening meaning. -- Preserve nuance that affects reader decisions, implementation safety, or release interpretation. -- Match structure to content: sentences for simple ideas, lists for enumerations, and nested bullets - for grouped details. -- Keep wording aligned with the target audience and the local document style. +- Make prose easy to scan without flattening meaning or adding distractions. +- Preserve nuance needed for decisions, safe implementation, or release interpretation. +- Fit the audience, document purpose, and local style. +- Make durable prose understandable without its originating conversation or an unstated date. -## Responsibility boundary +## Workflow -Use this skill when the destination document, factual source, and ownership are already known and -the task is to improve how the text communicates. Do not use it to decide which repository -documents should exist, where a technical fact belongs, whether evidence is sufficient, or how a -documentation migration should preserve coverage. Use `domain-architecture-docs-workflow` for -those decisions, then return here to refine the resulting prose. +### Establish the edit -Do not silently repair unsupported technical claims while copyediting. Flag the evidence gap and -use the applicable documentation-system or domain-specific skill. +1. Identify the audience, purpose, intended claim, factual source, and destination. + Reuse supplied context; resolve only gaps that could change the edit. + Stop prose-only revision where ownership or evidence is disputed. +2. Select information for the reader's task. Retain what supports understanding + or sound decisions; omit or separate distracting material. Brevity alone is + not the goal. Apply the same test to references: keep those needed for + understanding, verification, practical use, or attribution. Do not add links + merely because they were consulted during research. Be able to explain why + the particular source fits that need, such as its authority on the specific + claim, direct evidence, or the feature an example illustrates. Include that + explanation only when readers need it; do not repeat what context already + makes clear. Official status alone does not justify inclusion. Distinguish + illustrative examples from authoritative documentation. Omit references that add no value + for the reader, weighing optional references against link rot, content + changes, access limits, and maintenance. +3. Before editing prose intended for later independent use, read + [durable context](references/durable-context.md) for conversation references, + dates, versions, and history. This includes documentation, comments, Skills, + and saved handoffs. A wording request does not authorize new publication or + access changes. -## Workflow +### Review structure + +Inspect the rendered text, not just physical source lines. Treat counts and +length as review cues, not quotas. Judge readability by meaning, relationships, +audience, language, and local format; do not impose fixed character, word, +sentence, paragraph, or item limits. Keep a longer coherent unit when splitting +would obscure its meaning, and avoid fragmented prose or excessive nesting. + +1. Review each relevant level: + - **Section:** Check how many paragraphs sit under a heading and how much + material readers must scan. When distinct subtopics are hard to locate, + shorten distractions, regroup paragraphs, or add meaningful subheadings. + - **Paragraph:** Check sentence count and focus. Keep one coherent topic or + reasoning unit; retain its useful evidence and consequences. Split at a + genuine shift rather than turning every sentence into a paragraph. + - **Sentence:** Check length, stacked clauses, and nested qualifications. + Separate independently understandable ideas when this eases reading, while + keeping conditions, causes, exceptions, and their consequences connected. + - **List item:** Keep one independently reviewable point or action by default. + Separate unrelated facts or independently actionable requirements. Related + elements or supporting details may stay together; shorten or restructure + an item when its length hides its point, not merely because it has several sentences. + - **List:** Check item count, comparability, and scanning effort. Remove + redundancy or group meaningful categories when that helps. Keep a coherent + list intact when it is easier to use, preserving required items and sequence. +2. Choose the structure that helps the reader find and compare information. + - Use familiar section patterns suited to the genre; do not force a report + template onto every document. + - Use concise, content-descriptive headings in a written register unless + the genre or requested style calls for another tone. Prefer one clear + expression over overlapping topics such as "Background and Purpose." + Split topics when readers need to find them separately; do not ban + punctuation within terms or meaningful enumerations. Add a short qualifier + only when it distinguishes otherwise similar headings. + - Prefer lists for enumerations, allowing inline wording when short and + natural or clearer in the local style. Use subheadings, paragraphs, + grouped bullets, or tables when they improve navigation or comparison. +3. Separate rendering from source wrapping. Prefer sentence-per-line source + wrapping within an existing paragraph when the format permits it and review + becomes easier. It is not a paragraph break. Do not disrupt short prose, + links, lists, tables, or formatter-controlled comments, or change wording + merely to accommodate wrapping. + +For the rationale and limits of external guidance, consult +[writing guides](references/writing-guides.md). + +### Preserve meaning + +1. Preserve certainty, scope, timing, sequence, exceptions, limitations, + dependencies, and compatibility. Keep original, backfilled, observed, inferred, + planned, superseded, withdrawn, and unconfirmed statements distinguishable. + - Name each independently readable spatial or state condition's subject and + reference position; avoid an ambiguous "that position." + - Keep independently evaluated conditions separate unless the factual + source requires their conjunction. Splitting must not change AND to OR, + detach a qualification, or change modality, tense, or voice without cause. + - Preserve attribution and upstream relationships. A bare "official" must + not transfer authority between projects. For example, describe the + [Astral distributions used by uv](https://docs.astral.sh/uv/guides/install-python/) + as Astral-published Python distributions, not official Python distributions. +2. Remove explanations or caveats that do not help readers act, decide, or + understand. Prefer the current valid instruction when sufficient; do not + narrate irrelevant rejected or legacy alternatives. + - Disclose uncertainty that matters, without unrelated unknowns or + precautionary "unverified" labels. Remove an unnecessary unsupported claim; + flag a necessary evidence gap without implying verification. + - Retain compatibility or migration context when the document owns the + history or readers need it to update usage, interpret a release, or avoid + a concrete transition risk. +3. Assess status and process wording by the information it adds in context. + This applies to body text, headings, names, filenames, and version labels. + - Treat "verified," "reviewed," "approved," "adopted," "adapted," and + equivalents in other languages as review cues, not banned words or + interchangeable states. Omit a label that adds no useful distinction, + even when true or already clear from context. Prefer the subject or actual + change over a process label; do not replace one empty label with another. + - Retain distinctions needed for decisions, safe use, required approvals, + attribution, or legal obligations. Describe the supported fact at the + needed scope: a lockfile pin or presence on a branch does not by itself + establish review or approval. Omit version and branch wording too when + it serves no reader need. + - When status matters, check evidence for the relevant object and revision. + Make its basis clear at the precision readers need, such as who reviewed + what against which criteria, or the reference point or release channel + that defines "latest." Do not assert a status whose basis cannot be + established. + Do not turn a proposal, planned check, or pending approval into a completed + state, including in a pull request's proposed text. Review of an earlier + revision does not automatically cover later changes. State necessary + evidence gaps without inventing a result or expanding a prose edit into + approval of the work. + - When approval is required, make the approver clear unless the reader can + already identify them unambiguously from context. If that identity is + necessary but unknown, flag the gap rather than guessing or weakening the + approval requirement. +4. Compare modifiers and their scope across parallel statements, including + component lists and installation steps. A lone "latest," "verified," or + "required" can imply an unintended difference or leave its application to + later items unclear. For a shared requirement, state the common scope clearly + or repeat the modifier where items need to stand alone. Make actual differences + explicit. Omit unnecessary modifiers instead of adding them everywhere for + superficial consistency. Preserve real compatibility constraints and literal + identifiers, tags, commands, and configuration values. Resolve a consequential + evidence gap with the factual owner instead of assuming either uniform or + different requirements. + +For examples, see [status and process wording](references/status-wording.md). + +### Verify in context + +1. Re-read the edited passage with review depth proportionate to scope and risk. + Compare its destination, claim, and retained wording with the request. + Confirm each section, paragraph, and list has a clear job and still conveys + the supported meaning without unnecessary caveats or repeated context. +2. Keep adequate surrounding headings and structure unless content or navigation + gives a concrete reason to change them. Do not inflate a heading to squeeze + in a new topic. Offer wider restructuring when needed rather than silently + expanding a local edit into a full-document audit. +3. Use the owning domain Skill for document-specific checks. For a requested + resumable handoff, use [handoff notes](references/handoff-notes.md), preserving + factual ownership and the user's destination and level of detail. + +## Markdown validation -1. Classify the text audience before revising: - - Developer-facing. - - User-facing. - - Maintainer-facing. - - External-contract text. -2. Confirm the purpose, intended claim, factual source, and destination for this edit. - Reuse context already supplied by the request or document; resolve only missing context that - could change the edit. If ownership or evidence is disputed, stop prose-only revision at that - boundary and report the gap. -3. Identify overloaded prose: - - Sentences carrying multiple ideas, conditions, time references, confidence levels, or - relationships. - - Paragraphs that mix context, decision, evidence, and consequence. - - List items that contain several facts, exceptions, examples, or follow-up notes. - - Spatial or state conditions whose thresholds use different subjects or reference positions. - Name the subject and reference in every independently readable item; do not rely on a - deictic phrase such as "that position" when it could refer to more than one value. - - Independently evaluated conditions phrased as though they were one conjunction. Keep them - separate unless the factual source establishes that every part is required together. -4. Prefer lists when presenting enumerations. - - Use inline prose only when the enumeration is short enough to read naturally or when the local - document style clearly favors inline wording. -5. Split or restructure dense text when it becomes hard to scan. - - Use separate paragraphs, parent bullets with indented child bullets, tables, or another local - document pattern that makes each idea easy to review. - - When a sentence continues the same paragraph or comment block, prefer starting it on a new - physical line if the local format allows that without changing the rendered structure. - - Treat sentence-per-line wrapping as a reviewability aid, not as a paragraph break. Do not - apply it when it would make short prose, Markdown links, lists, tables, or formatter-controlled - code comments harder to read. - - Do not change wording strength, modality, tense, or voice only to make sentence wrapping work. - Keep wording unchanged unless an independent readability issue justifies rewriting it. -6. Remove negative-space explanations that do not help the reader act or decide. - - Prefer the current valid instruction or example when it is sufficient on its own. - - Do not add a disclaimer that an old or omitted form is rejected merely because the - implementation no longer accepts it. - - Retain compatibility or migration context when the document owns that history or the audience - needs it to update existing usage, interpret a release, or avoid a concrete transition risk. -7. Preserve the nuance that made the original wording important: - - Certainty or confidence level. - - Scope and applicability. - - Timing and sequence. - - Exception or limitation status. - - Dependency or compatibility relationships. - - Attribution and upstream relationships. Avoid a bare "official" when it - could transfer authority from one project to another. For example, - [uv documents](https://docs.astral.sh/uv/guides/install-python/) that it - uses Astral's `python-build-standalone` distributions because Python does - not publish official distributable binaries. Describe those artifacts as - "Astral-published Python distributions used by uv," not as "official - Python distributions" or "uv's official Python distributions." - - Whether a statement is original, backfilled, inferred, superseded, withdrawn, or still - unconfirmed. -8. Use as many short sentences or nested bullets as needed. Do not force a fixed sentence count - when the content needs a different shape. -9. Re-read the result as a whole and use the domain-specific skill when one owns the document type. - - Compare the actual edited destination and scope with the request and any wording or meaning - the user asked to retain. - - Confirm it still answers the same question as the original wording. - - Confirm each list or paragraph has one clear job. - - Confirm the structure did not imply a stronger, weaker, broader, or narrower claim than the - source material supports. -10. When establishing repository-wide Markdown validation, copy - `assets/markdownlint-cli2.yaml` to `.markdownlint-cli2.yaml` without - deleting its rationale comments or changing its rule baseline. Add a local - ignore or exception only for an evidenced generated, vendored, submodule, - renderer, or document-format requirement, and document that reason beside - the narrow override. When an applicable domain Skill owns a reviewed derived - configuration, such as `hugo-quality-check`, use that asset instead of - recreating its exceptions in the consumer. Use `github-actions-quality-check` - to wire the repository-owned configuration into CI. - -## Optional handoff notes - -For a requested resumable handoff, use [handoff-notes.md](references/handoff-notes.md) to select the -decisions and open questions the next reader needs. Keep the existing factual-ownership boundary -and preserve the user's choice of destination and level of detail. - -## Output checklist - -- Audience and document type were considered before rewriting. -- Factual ownership and evidence gaps were not silently decided through wording changes. -- Enumerations are lists unless inline prose is clearer for the local context. -- Dense paragraphs or list items were split or intentionally left intact. -- Current instructions do not narrate irrelevant rejected or legacy alternatives. -- Important certainty, scope, timing, relationship, and status nuances were preserved. -- The final text is easier to scan and still communicates the same claim. +When establishing repository-wide Markdown validation, copy +`assets/markdownlint-cli2.yaml` to `.markdownlint-cli2.yaml`, preserving rationale +comments and the rule baseline. Add a narrow override only for an evidenced +generated, vendored, submodule, renderer, or document-format requirement, and +document its reason beside the override. Prefer +an owning Skill's derived configuration, such as `hugo-quality-check`, +over recreating its exceptions. Use `github-actions-quality-check` for CI wiring. diff --git a/.agents/skills/prose-quality-check/agents/openai.yaml b/.agents/skills/prose-quality-check/agents/openai.yaml index 0a530df..eb7873c 100644 --- a/.agents/skills/prose-quality-check/agents/openai.yaml +++ b/.agents/skills/prose-quality-check/agents/openai.yaml @@ -1,4 +1,4 @@ interface: display_name: "Prose Quality Check" short_description: "Improve prose without changing its meaning" - default_prompt: "Use $prose-quality-check to revise this prose for readability, local structure, audience fit, and preserved nuance." + default_prompt: "Use $prose-quality-check to revise this prose for readability, local structure, audience fit, self-contained context, and preserved nuance." diff --git a/.agents/skills/prose-quality-check/references/durable-context.md b/.agents/skills/prose-quality-check/references/durable-context.md new file mode 100644 index 0000000..4fb1bde --- /dev/null +++ b/.agents/skills/prose-quality-check/references/durable-context.md @@ -0,0 +1,64 @@ +# Durable Context + +Use these checks before revising prose intended to stand on its own after the +originating conversation. Preserve information readers need without making +every stable fact carry a date or version. + +## Conversation references + +Replace "this conversation" or "this chat" with the relevant decision, +subject, rationale, or scope. Remove the reference when it adds nothing. +Supply essential context in the document or cite an established supporting +source accessible to the audience. Check availability and audience access; a +link alone does not make private or unavailable context usable. + +Flag unresolved context or access gaps. Do not publish a new external document +or change access permissions merely to make prose self-contained; those +operations require separate authorization. + +## Time boundaries + +Treat "currently," "previously," "existing," and similar expressions as review +cues, not banned strings. Remove a time distinction that does not help readers +act or interpret the claim rather than dating an otherwise durable fact. + +For a changing fact that needs a time boundary, use the source-supported +observation or effective date at the coarsest unambiguous precision: a year or +month for a broad period, a full date for a dated state, or a timestamp with +time zone for a rapidly changing state. Include the year. Flag missing temporal +evidence; do not invent precision or substitute the editing date. + +Keep useful dated snapshots and qualified expectations. Distinguish observations +from planned or possible changes without turning forecasts into guarantees. + +## Version scope + +State reader-relevant compatibility or applicability at the needed precision. +Omit irrelevant version detail and incidental exact pins duplicated from +configuration or lockfiles. Prefer major or minor precision when sufficient; +retain exact revisions needed for behavior, compatibility, or reproduction. +Do not broaden a supported or tested range to simplify its notation. + +Give human readers the version information they need directly in the document, +even when an exact revision matters. Consult authoritative pins during +verification without sending human readers to a lockfile for that information. +Agent-facing instructions may direct the agent to authoritative lockfiles. + +## Executable runbooks + +Keep human-facing runbooks self-contained for safe execution, including necessary +exact commands and version constraints. Allow duplication needed for safety and +reasonable reader effort. Keep the authoritative source and update needs clear +to control drift; use the owning workflow or domain Skill to verify the procedure +and coordinate updates. + +## Earlier behavior + +After a behavior change, do not leave "existing behavior" dependent on the +pre-change editing context. Retain earlier behavior when readers need it, +naming the relevant version, state, or date and why the distinction matters. + +Use `domain-architecture-docs-workflow` to decide whether audience impact +justifies retained history in maintained documentation or a reference to +version-specific documentation. Preserve explicit compatibility, migration, +and support requirements, including necessary transition steps. diff --git a/.agents/skills/prose-quality-check/references/status-wording.md b/.agents/skills/prose-quality-check/references/status-wording.md new file mode 100644 index 0000000..8d5cd76 --- /dev/null +++ b/.agents/skills/prose-quality-check/references/status-wording.md @@ -0,0 +1,50 @@ +# Status and Qualifying Wording + +Use these examples when a status or process term may be unnecessary, ambiguous, +or stronger than the evidence. The issue is the information added in context, +not the presence of a particular word. + +## Editorial examples + +- If the surrounding workflow already identifies the document under review, + prefer its subject as the title rather than adding "reviewed version." + A real distinction between a reviewed revision and a changed revision can + still matter; retain it where readers need to choose between them. +- Replace "the approved version in the lockfile" with "the version pinned in + the lockfile" when the pin is the relevant fact. If the instruction already + says to use the lockfile and no version distinction matters, omit the extra + phrase. A pin alone is not evidence of approval. +- A repository's own usage guide ordinarily belongs to the revision being read. + Do not add "reviewed version," "approved version," or "default-branch + version" merely to identify that context. Remove the qualification when + unnecessary. Name a branch or revision when a real distinction matters, + such as a branch workflow, release procedure, or CI target. Presence on the + default branch alone does not establish review or approval. +- A pull request proposing a version update must not describe that proposal + as already approved merely because approval is expected before merge. + Use the version or proposed change, or state the pending decision when + readers need it. Preserve an actual approval of the same revision when + supported and relevant. +- "Get approval before publishing" needs an approver if readers cannot tell + whose decision is required. "Ask the user to review the draft. Publish only + after approval" already identifies the approver; repeating "by the user" + need not help. +- A test report may need the checked environment, revision, and result. + Include only the detail needed to interpret that result, rather than giving + every use of "verified" a fixed date-and-version template. + A needed "reviewed" claim must have an identifiable review basis; a needed + "latest" claim must have a meaningful reference point or release channel. + If the basis is unavailable, flag the consequential gap instead of inventing + criteria or replacing the label with another unsupported assurance. +- In parallel installation requirements, "Install A, the latest B, and C" + implies that B has a distinct freshness requirement. If no such difference + is intended or needed, use "Install A, B, and C" rather than extending + "latest" to all three. Preserve genuine minimum versions, security update + requirements, or release-channel differences, making their scope clear. + A literal `latest` tag or command argument is not a stylistic qualifier; + do not change its operational meaning as part of a prose edit. +- If "latest" really applies to each item in "the latest A, B, and C," make + that shared scope explicit, for example "the latest supported releases of A, + B, and C." Repeat a necessary modifier in each independently read list item. + Do not rely on readers guessing whether the first item's modifier extends + to later items. Use different modifiers when different requirements apply. diff --git a/.agents/skills/prose-quality-check/references/writing-guides.md b/.agents/skills/prose-quality-check/references/writing-guides.md new file mode 100644 index 0000000..f487ccc --- /dev/null +++ b/.agents/skills/prose-quality-check/references/writing-guides.md @@ -0,0 +1,39 @@ +# Writing Guide Rationale + +These English technical and web-writing guides inform the structure review. +Their numerical suggestions are contextual editorial heuristics, not universal +limits or a basis for Japanese character caps. Apply semantic unity, audience, +genre, navigation, and preservation of meaning before counts. + +## Sections + +[Microsoft's heading guidance](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings) +recommends dividing substantial content into meaningful subtopics without +manufacturing subdivisions or filler. It sets no paragraph-count ceiling. + +## Paragraphs + +[Google's paragraph guidance](https://developers.google.com/tech-writing/one/paragraphs) +centers a paragraph on a coherent unit of reasoning. Its sentence-count advice +also warns against excessive one-sentence paragraphs. Use counts to prompt +review of focus and reader effort rather than automatic splitting. + +## Sentences + +[Google's short-sentence guidance](https://developers.google.com/tech-writing/one/short-sentences) +recommends one idea, removing unnecessary words, and clarifying complicated +embedded enumerations. It does not impose a universal word-count ceiling. +Related conditions and consequences still need an intelligible connection. + +## Lists + +[Microsoft's list guidance](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists) +favors related, parallel, scannable items. Its suggested item count is qualified +by "if possible," and it permits occasional longer items. +[Google's list guidance](https://developers.google.com/style/lists) also allows +multi-paragraph items. Neither supports an unconditional one-sentence rule. + +One independently reviewable point per item is this Skill's working default, +not a quoted universal rule. Closely related elements and necessary supporting +details can stay together. List length warrants regrouping only when meaningful +categories or easier scanning justify it; preserve complete requirements and order. diff --git a/.agents/skills/python-quality-check/assets/github/actions/setup-python-locked/action.yml b/.agents/skills/python-quality-check/assets/github/actions/setup-python-locked/action.yml index 587e992..f7b5cca 100644 --- a/.agents/skills/python-quality-check/assets/github/actions/setup-python-locked/action.yml +++ b/.agents/skills/python-quality-check/assets/github/actions/setup-python-locked/action.yml @@ -28,7 +28,7 @@ runs: run: bash "${{ github.action_path }}/resolve-python-contract.sh" - name: Install uv - uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0 + uses: astral-sh/setup-uv@68559e99cc807c1eb7e9238fd43a15bba460eec2 # v10.3.3 with: enable-cache: true python-version: ${{ steps.toolchain.outputs.python_version }} diff --git a/.agents/skills/python-quality-check/assets/github/actions/setup-python-locked/resolve-python-contract.sh b/.agents/skills/python-quality-check/assets/github/actions/setup-python-locked/resolve-python-contract.sh index 5f82c84..6978e6b 100644 --- a/.agents/skills/python-quality-check/assets/github/actions/setup-python-locked/resolve-python-contract.sh +++ b/.agents/skills/python-quality-check/assets/github/actions/setup-python-locked/resolve-python-contract.sh @@ -16,7 +16,7 @@ main() { { printf 'python_version=%s\n' "$python_version" - printf 'uv_version=0.12.3\n' + printf 'uv_version=0.13.6\n' } >>"$GITHUB_OUTPUT" } diff --git a/.agents/skills/security-check/README.md b/.agents/skills/security-check/README.md index 2d4f1db..d9ae53b 100644 --- a/.agents/skills/security-check/README.md +++ b/.agents/skills/security-check/README.md @@ -2,7 +2,8 @@ ## Overview -Review repository changes for practical security and supply-chain risks. +Review repository and development-environment changes for practical security +and supply-chain risks. ## Install diff --git a/.agents/skills/security-check/SKILL.md b/.agents/skills/security-check/SKILL.md index 612e175..3ffe05f 100644 --- a/.agents/skills/security-check/SKILL.md +++ b/.agents/skills/security-check/SKILL.md @@ -1,7 +1,8 @@ --- name: security-check description: >- - Review repository changes for practical security and supply-chain risks. Use + Review repository and development-environment changes for practical security + and supply-chain risks. Use when work touches secrets, permissions, untrusted input, dependencies, executable or downloaded artifacts, CI or deployment configuration, containers, vendored/generated files, or compiled and bundled software whose @@ -14,7 +15,7 @@ description: >- ## Goals -- Provide a single repository-local security reference point for agents and +- Provide a single security reference point for agents and maintainers. - Treat this guidance as a practical project baseline, not permission to take a less safe path than a tool, platform, organization policy, package manager, or @@ -94,6 +95,11 @@ description: >- 7. Inspect repository scripts, lockfiles, and tool configuration so the recommendation is grounded in the project instead of inventing a new ad hoc path. + For development-environment work, inspect the relevant installed package and + tool inventory, sources, and update commands as well as affected repository + requirements. Use `development-environment-update-workflow`, when available, + for host/package-manager scope and operational verification; this Skill + retains the security findings and adoption gates. Use `mise-workflow` when the reviewed surface includes `mise.toml`, `mise.lock`, mise-managed tool artifacts, or mise tasks; retain this Skill as the owner of cooldown, provenance, integrity, secret, and execution findings. @@ -125,6 +131,12 @@ description: >- ## Supply-Chain Baseline +- For dependency adoption, updates, or vulnerability assessment, use + [advisory-review.md](references/advisory-review.md) to identify trustworthy + advisory sources for the actual package, distribution, or artifact and assess + applicability. `dependency-update-workflow`, when available, coordinates + repository inventory and update candidates; this Skill owns security findings + and exception requirements. An update workflow does not replace these gates. - For tool-specific fixed-install and execution patterns, consult [external-code-execution.md](references/external-code-execution.md) when the listed tool applies. diff --git a/.agents/skills/security-check/agents/openai.yaml b/.agents/skills/security-check/agents/openai.yaml index 62afb43..93ae0fb 100644 --- a/.agents/skills/security-check/agents/openai.yaml +++ b/.agents/skills/security-check/agents/openai.yaml @@ -2,8 +2,9 @@ interface: display_name: "Security Check" short_description: "Review security, supply-chain, and distribution risks." default_prompt: >- - Use $security-check to review this repository work for security and supply-chain risks, including + Use $security-check to review this repository or development-environment work for security and supply-chain risks, including secrets, permissions, unsafe defaults, supply-chain-sensitive artifacts, - ad hoc executable tools, dependencies, CI actions, containers, compiled or + ad hoc executable tools, dependencies, applicable security advisories, + CI actions, containers, compiled or bundled software licensing, FFmpeg configurations, private-repository disclosure boundaries, and reviewer-visible blockers or residual risk. diff --git a/.agents/skills/security-check/references/advisory-review.md b/.agents/skills/security-check/references/advisory-review.md new file mode 100644 index 0000000..1199a72 --- /dev/null +++ b/.agents/skills/security-check/references/advisory-review.md @@ -0,0 +1,90 @@ +# Dependency Advisory Review + +Use this procedure for dependency adoption, update decisions, or assessment of +known vulnerabilities. Keep cooldown, execution, disclosure, and exception +requirements in `security-check`; an advisory finding does not change them. + +## Identify the reviewed artifact + +Record the ecosystem, registry, canonical publisher/source, current and proposed +version or commit, distribution/release, architecture, and dependency path. +Distinguish upstream source versions from distributor packages and actual +downloaded or bundled artifacts. Include direct and resolved transitive +dependencies, including development, build, and CI uses. + +Use the final image/package inventory or a source-matched SBOM when available. +Record its generating revision and platforms. A source manifest, Docker tag, +binary filename, or old SBOM alone may not identify what is shipped. Mark +unresolved portions explicitly; do not execute an unreviewed scanner or candidate +merely to obtain a version or advisory report. + +## Choose sources for that dependency + +Start from canonical project, registry, or distributor documentation to locate +its security page, advisory feed, supported-version policy, or security tracker. +Corroborate the publisher/source relationship rather than trusting a search +result's rank, a familiar-looking domain, a badge, or popularity. Prefer the +authority responsible for the exact artifact, with relevant ecosystem databases +as additional evidence. + +| Dependency | Sources and identity checks | +| --- | --- | +| Language package | Publisher advisories and registry-linked source; ecosystem advisory database, GitHub Advisory Database, or OSV where that ecosystem is covered. Match package name, registry, and version scheme. | +| Runtime, CLI, downloaded binary | Runtime/tool vendor's security notices and supported release branches. Identify the binary distributor separately when it rebuilds or bundles upstream software. | +| GitHub Action or reusable workflow | Canonical repository advisories and release/security notices, mapped to the exact pinned commit. Include bundled code and its execution runtime; a SHA pin may not be covered by a version-based alert. | +| Container base image | Image publisher's advisories and platform-specific contents, plus the underlying distribution's security tracker for OS packages. A new digest or tag is not proof that every included package is fixed. | +| apt, apk, rpm, or other OS package | The actual distribution/release security tracker and package changelog for the installed source/binary package version and configured repositories. Account for vendor backports. | +| Vendored or compiled bundle | Upstream advisories mapped to the vendored revision, build features, linked libraries, and downstream patches; use distributor evidence when it changes the affected status. | + +Search engines, release aggregators, and issue reports can locate leads. Verify +claims against the originating advisory or a maintained database that identifies +its sources. Do not treat syndicated copies as independent corroboration. +Use general CVE databases to fill gaps or cross-check; they may not encode a +distributor's release-specific fix status. An unavailable authoritative source +or unsupported scanner ecosystem remains a coverage gap, not a clean result. + +## Assess applicability and evidence quality + +1. Match ecosystem, exact package/source identity, affected and fixed ranges, + commit ancestry where relevant, platform, enabled features, and distribution + release. Use that ecosystem's version comparison; lexical or generic SemVer + comparison may misclassify distro revisions or other version schemes. + For OSV data, consult the [affected-package and range semantics](https://ossf.github.io/osv-schema/#affected-fields) + when interpreting package identities, Git ranges, and ecosystem ranges. +2. Check the advisory's publication, modification, and withdrawal state, aliases, + original references, and fixed-version evidence. Record the check time. + A release note saying "security fixes" without the affected identity/range + does not establish whether this artifact or deployment is remediated. +3. Follow direct and transitive paths to the resolved artifact. Distinguish + version-range applicability from demonstrated reachability, runtime exposure, + or active exploitation; do not infer the latter from a severity score alone. + Assess current and proposed versions, not only whether the candidate fixes + one known advisory while introducing another affected dependency. +4. For a distro package with backported fixes, compare the installed distro + revision against that distributor's fixed status. Do not label an older + upstream version vulnerable solely because a generic scanner ignores the + backport, or label it fixed without matching release/package evidence. +5. Reconcile conflicting vendor and database claims with their scope and dates. + Record a source-backed conclusion or an unresolved finding; do not discard a + report merely because another source is green. Missing metadata, a failed + query, or an unscanned platform must not become "no vulnerabilities." + +## Return findings for the decision + +For each relevant finding, record the advisory link/ID, artifact and dependency +path, affected/fixed ranges, applicability evidence, exposure evidence and gaps, +and available remediation or mitigation. Distinguish confirmed applicability, +possible applicability, and an evidenced non-applicable result. State which +sources and graph/platform scope were checked, and which were unavailable. +"No findings" is limited to those checked sources and that scope. + +If a fix fails a cooldown or another adoption gate, compare risk of waiting, +available eligible fixes, and temporary mitigations. Return an exception proposal +with the exact artifact, unmet gate, urgency evidence, and residual risk to the +authorized user or maintainer. Approval must be explicit and documented under +the main Skill and any stricter ecosystem policy. A security label, bot priority, +or high severity alone does not authorize early execution or adoption. + +Keep sensitive, unpublished vulnerability details in the approved private +reporting path. Public update proposals should contain only the non-sensitive +findings needed for the decision. diff --git a/.github/actions/check-docker-source/action.yml b/.github/actions/check-docker-source/action.yml index e9d2546..baa9605 100644 --- a/.github/actions/check-docker-source/action.yml +++ b/.github/actions/check-docker-source/action.yml @@ -7,7 +7,7 @@ runs: - name: Set up reviewed APM CLI uses: microsoft/apm-action@d723bb64ed70c135bbaf87d126b721dd2dae0439 # v1.10.0 with: - apm-version: "0.34.0" + apm-version: "0.35.0" setup-only: "true" - name: Audit APM deployment diff --git a/AGENTS.md b/AGENTS.md index c3bc260..234c0aa 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -30,7 +30,7 @@ directly. ### Approved cooldown exception -Use APM CLI 0.34.0 for lock operations. It is the newest reviewed release +Use APM CLI 0.35.0 for lock operations. It is the newest reviewed release that satisfies the normal seven-day cooldown; using it is not an exception. A maintainer may explicitly waive the normal seven-day wait for the latest diff --git a/THIRD_PARTY_NOTICES.md b/THIRD_PARTY_NOTICES.md index 91e0313..5482b4f 100644 --- a/THIRD_PARTY_NOTICES.md +++ b/THIRD_PARTY_NOTICES.md @@ -27,9 +27,9 @@ that are present in that checkout. - Source: [aoirint/skills](https://github.com/aoirint/skills), selected from `.apm/skills/` - Pinned commit: - [`22fe4f84018358059adcf7709cb9df28d1260fd8`](https://github.com/aoirint/skills/tree/22fe4f84018358059adcf7709cb9df28d1260fd8) + [`1bbdf247da61492e8c1531f341aae400a04b9503`](https://github.com/aoirint/skills/tree/1bbdf247da61492e8c1531f341aae400a04b9503) - Deployed paths: `.agents/skills/{apm-workflow,changelog-workflow,code-quality-check,commit-message-quality-check,docker-quality-check,git-worktree-workflow,github-workflow,gitignore-workflow,prose-quality-check,python-quality-check,release-note-workflow,security-check}/` -- License: [MIT](https://github.com/aoirint/skills/blob/22fe4f84018358059adcf7709cb9df28d1260fd8/LICENSE) +- License: [MIT](https://github.com/aoirint/skills/blob/1bbdf247da61492e8c1531f341aae400a04b9503/LICENSE) - Copyright: Copyright (c) 2026 aoirint - Cooldown: the maintainer requested immediate adoption of this exact direct diff --git a/apm.lock.yaml b/apm.lock.yaml index 50b6e71..80a54ea 100644 --- a/apm.lock.yaml +++ b/apm.lock.yaml @@ -1,11 +1,11 @@ lockfile_version: '1' -apm_version: 0.34.0 +apm_version: 0.35.0 dependencies: - repo_url: aoirint/skills name: skills host: github.com - resolved_commit: 22fe4f84018358059adcf7709cb9df28d1260fd8 - resolved_ref: 22fe4f84018358059adcf7709cb9df28d1260fd8 + resolved_commit: 1bbdf247da61492e8c1531f341aae400a04b9503 + resolved_ref: 1bbdf247da61492e8c1531f341aae400a04b9503 version: 0.0.0 package_type: apm_package deployed_files: @@ -69,7 +69,10 @@ dependencies: - .agents/skills/prose-quality-check/SKILL.md - .agents/skills/prose-quality-check/agents/openai.yaml - .agents/skills/prose-quality-check/assets/markdownlint-cli2.yaml + - .agents/skills/prose-quality-check/references/durable-context.md - .agents/skills/prose-quality-check/references/handoff-notes.md + - .agents/skills/prose-quality-check/references/status-wording.md + - .agents/skills/prose-quality-check/references/writing-guides.md - .agents/skills/python-quality-check - .agents/skills/python-quality-check/README.md - .agents/skills/python-quality-check/SKILL.md @@ -92,6 +95,7 @@ dependencies: - .agents/skills/security-check/README.md - .agents/skills/security-check/SKILL.md - .agents/skills/security-check/agents/openai.yaml + - .agents/skills/security-check/references/advisory-review.md - .agents/skills/security-check/references/artifact-inspection.md - .agents/skills/security-check/references/distributed-software-licensing.md - .agents/skills/security-check/references/external-code-execution.md @@ -99,7 +103,7 @@ dependencies: .agents/skills/apm-workflow/README.md: sha256:e346edab06f5ec792cdb77edcaa8042f523af67753dc4fe72498ae1899b87c89 .agents/skills/apm-workflow/SKILL.md: sha256:e0d74b6166c810e57869ac349e400b73fb6502e46c3b979b9489bd3305b7faa0 .agents/skills/apm-workflow/agents/openai.yaml: sha256:f3c083196472ec9253886b369202ddeb8eb2534fd2da9799798bae2eb33b2e55 - .agents/skills/apm-workflow/references/apm-bootstrap.json: sha256:0b193b2dc7be40069ae30d5efa8f3c1f229cdef044487264e8554f102a6b26a0 + .agents/skills/apm-workflow/references/apm-bootstrap.json: sha256:9112412627ced083e1e687d4b3623217af40cc3f815a2ce294e5e8d5aac1c331 .agents/skills/apm-workflow/references/bootstrap-refresh.md: sha256:e12c66f02ca6b3b56d5679fe2f28b9c23d4ce060cf7f448204da40d7508c0e32 .agents/skills/apm-workflow/references/cli-acquisition.md: sha256:9274eeaab5ea5d1c6e9ec015ee36a4dcc2dc3e8f2be8bcad3f5cdac5ebde3dd4 .agents/skills/apm-workflow/references/cli-selection.md: sha256:fb363afd421212d2e19d7e7125e0a49224fbfc329f9f493ad175d055fafe06e6 @@ -113,19 +117,19 @@ dependencies: .agents/skills/changelog-workflow/README.md: sha256:7ef8167d26522d95f62b9f11d752487d62b6bfdae05850315189fbe2a19fed83 .agents/skills/changelog-workflow/SKILL.md: sha256:8d9de8e0e3c31c4a2c176a0d14e3f1a45daf3db364ede7dd86983c8c3f571f54 .agents/skills/changelog-workflow/agents/openai.yaml: sha256:6264e6dbd0433ab63370e15033ecb94da8dd131c4edcb1d3f2b9abdeb4f680f1 - .agents/skills/code-quality-check/README.md: sha256:b2cfd8bf9c3c7bd16cf86718877fa025396d15a380de88045122c4d162682cc2 - .agents/skills/code-quality-check/SKILL.md: sha256:7415164c33885676d4b579db0560287762a5c2e0e25001dac0e848af1b6c10b0 + .agents/skills/code-quality-check/README.md: sha256:398fd9d399fbe979bae75b23c277e9b13fac6edd7bdbc645821fc60e9ac856ac + .agents/skills/code-quality-check/SKILL.md: sha256:1a7897522ac360d9f5607f4fba3141e9745584c9fe3943d11bb7c0a9520659d4 .agents/skills/code-quality-check/agents/openai.yaml: sha256:69a8a75579e3b47dc69a176417b97441adf81bc54984d3f6bc114e47a68bc9b3 - .agents/skills/code-quality-check/references/avoiding-overengineering.md: sha256:f35ad2036a18151dc9dfef8a334989d2b88439478505cd5b047f0621dd613098 + .agents/skills/code-quality-check/references/avoiding-overengineering.md: sha256:51d42dc39ad47c4f3b908caa0b1fad8835acc516fc5ce6c917733dd410201342 .agents/skills/commit-message-quality-check/README.md: sha256:c23949080d05f47cce728410ca3190225397aa41ac2015c6f02ee478ec412a24 .agents/skills/commit-message-quality-check/SKILL.md: sha256:cbe89b115e778b2417abf5fb15d98b2d1403c3ea0c99bf5ce9a0a65bef0cd6d7 .agents/skills/commit-message-quality-check/agents/openai.yaml: sha256:faffd948a0989dcfc87dcd3b0580c4a7003d01ef436e66dab9f280df57de652c .agents/skills/docker-quality-check/README.md: sha256:912a73d3de06babc6eed1ecdaf275139ae465797083dc5427affb54d00c57bf0 .agents/skills/docker-quality-check/SKILL.md: sha256:85b24dafab008013de4edada0ab17defd1bd06ac879b3a0342648620b4e56cce .agents/skills/docker-quality-check/agents/openai.yaml: sha256:56a5f1b83f050b12555bbf85d1fd66c206016b8f939b79370e250b4e661cafd7 - .agents/skills/docker-quality-check/assets/github/actions/check-docker-source/action.yml: sha256:d3d30f80b163e6e60e6a47c46b79fc6f1afc6047ba093aacd5459432a069872e - .agents/skills/docker-quality-check/assets/github/workflows/main.yml: sha256:7aaaecf2bc58c849c1877264f8c1363cd3376a158d25f948111f2adda7a1bf51 - .agents/skills/docker-quality-check/assets/github/workflows/pull-request.yml: sha256:f2571d65cf632f40ecdaca58334cb1ff793c7770aafffa0d691450216cf50a83 + .agents/skills/docker-quality-check/assets/github/actions/check-docker-source/action.yml: sha256:983ef785b2daf4b9f46fcf1416bbf39a12ae7d331f7347ceb33270e614a3eeb5 + .agents/skills/docker-quality-check/assets/github/workflows/main.yml: sha256:d18b2a7f7162779fcba2af1e4fc662a58f4a30856d1934482dc9668931b3e409 + .agents/skills/docker-quality-check/assets/github/workflows/pull-request.yml: sha256:1adbb3ab5bcae8bb7e61ac9bf9cca70bf6a80311e088e7ceace7cd54b8e7c3e0 .agents/skills/docker-quality-check/references/accelerator-runtime-validation.md: sha256:0a37c8eebe89a3d293603145708b6876a49ace3d856edf848ac74be07c596f45 .agents/skills/docker-quality-check/references/ci-template-contract.md: sha256:e9d1a4f0c2e472dbe18f062a968f79e10daf10a87fa54091edfaead7222749b9 .agents/skills/docker-quality-check/references/registry-image-deletion.md: sha256:a02688f52be5fccef96a2f25a70451eb8c579a46aa21ce27ee57ebc3a3f71a7e @@ -143,16 +147,19 @@ dependencies: .agents/skills/gitignore-workflow/README.md: sha256:0de188ebcdd40ea1aec701410e1c2182049b66bc4ec4d83a3bf55685b4267d47 .agents/skills/gitignore-workflow/SKILL.md: sha256:2ef38f42e418c10e0ba7632e3ba37614df97044dfa8847ad1338e6c4c896c089 .agents/skills/gitignore-workflow/agents/openai.yaml: sha256:f6a9b176003028588ff4c1d9ee4e23c625892d00b65086bf4b6b26a3f896030d - .agents/skills/prose-quality-check/README.md: sha256:8e4d9f8f8fdfba1cf7fe71fa88cac6baffa0d3c7616f744c0e3b1add102be5e7 - .agents/skills/prose-quality-check/SKILL.md: sha256:689e54128f766928a5594529c7f7fab4372fff4de42975f98a8eb7698acbceb1 - .agents/skills/prose-quality-check/agents/openai.yaml: sha256:b83e0a5d151e6e20df6f7d97f268955c6abfd105d53820f6baad0de8403fc062 + .agents/skills/prose-quality-check/README.md: sha256:0e1c7df4ddf1875dc36643dc6547a07f03e7fae79031b7a51e21f2ed367b9e81 + .agents/skills/prose-quality-check/SKILL.md: sha256:80470e0ff754f1db845bcff8123e39bcba7ab68b6d2705bd9dce775851b3d718 + .agents/skills/prose-quality-check/agents/openai.yaml: sha256:a0abf6489b64a09c4322c23e453912ecdc88a3dcf1131ee39d2367e8a2d865e0 .agents/skills/prose-quality-check/assets/markdownlint-cli2.yaml: sha256:1044e29915fe15e9083f808d1170c84cfc0b848123c0da435cabb9512d39c203 + .agents/skills/prose-quality-check/references/durable-context.md: sha256:027cc12a9d479890c4a6a88d223c619b2568370aeb6ff37fabb351af85f1dd28 .agents/skills/prose-quality-check/references/handoff-notes.md: sha256:15470b6bb5ad5ad5e618392d7ae1a3939c0c4e63b2f630196f3d4b6ca56c39f7 + .agents/skills/prose-quality-check/references/status-wording.md: sha256:3831cad93369c01130ec10084a644e7e86a60760494a302535b9083e8a0064db + .agents/skills/prose-quality-check/references/writing-guides.md: sha256:40264bc89a19402ef0b8eaf4401dbd8e8213612c47f600b5d9a79cdf5ec5415d .agents/skills/python-quality-check/README.md: sha256:20a23003a24a8caf2f03dd5a06bed99c81cf93ab53fe5a196c6a67ab59c53b0e .agents/skills/python-quality-check/SKILL.md: sha256:f32a4b7f394e73c3d7ed56cd8c525cc679010573d8586776dbb54b1aff1c6491 .agents/skills/python-quality-check/agents/openai.yaml: sha256:f0b4ad3807e177becec02271314fb32c1ec8d5a7682725ddd4a611a5381084d1 - .agents/skills/python-quality-check/assets/github/actions/setup-python-locked/action.yml: sha256:a78b34f3bfdd20cd2624bb093f0a927ea6c2edddc4301a2d60ec8a86e0fa2589 - .agents/skills/python-quality-check/assets/github/actions/setup-python-locked/resolve-python-contract.sh: sha256:71e09fff0baf2630e766c8dd32eef32d0735dbc11b4f25fe335cca10f99548e8 + .agents/skills/python-quality-check/assets/github/actions/setup-python-locked/action.yml: sha256:5722aa8c85e0c180c695778ddf1c199e109782ec054cee85494f90c7e9d4e774 + .agents/skills/python-quality-check/assets/github/actions/setup-python-locked/resolve-python-contract.sh: sha256:909608e195549256e86bc041c48fa0de83e43107d80093bc0635c6006ec0c4c5 .agents/skills/python-quality-check/references/ci-and-distribution.md: sha256:bfd313b057b0a93518f641bbc1b0f0fa8ada41f06fbb075c8315d00225684784 .agents/skills/python-quality-check/references/tooling-and-testing.md: sha256:dd55defe261fd16e88e9ef4acf2487ec4c05cca160c153db1a0e6746b3e39b44 .agents/skills/python-quality-check/scripts/check_project.py: sha256:8175b500198399a2ce8b79b4fc8d1902f791d163a0d6dfd35b5ce56b41c5ccc5 @@ -164,13 +171,14 @@ dependencies: .agents/skills/release-note-workflow/README.md: sha256:f13446e75a1c77495c4d55476ba8ca919aa3181e0864feb7a668a20a5cdf964b .agents/skills/release-note-workflow/SKILL.md: sha256:518296cb00d1ef181785ea8abd0150b9704b5cdd05a48fc0390284c548ef421c .agents/skills/release-note-workflow/agents/openai.yaml: sha256:30cfe7d4520783cfc8c72f5f81cc3e7a5708a5827e691f0003a665d89558fda0 - .agents/skills/security-check/README.md: sha256:d321689b998388180ac852fdb6374ab3b79bec508a53d00461a9db79fb246d2e - .agents/skills/security-check/SKILL.md: sha256:cdc808990ce5eece96a6cb439a389f6611ba8c34ae954789df4ed8936732f63e - .agents/skills/security-check/agents/openai.yaml: sha256:b1021ca2df7466813d0a376fc8bdff83603f568b02ef712e236fb2cfeef377c0 + .agents/skills/security-check/README.md: sha256:77d4bcc70596b8f4d215ab50ca009e6f325b322240bdd7c69348f4373cb1bc3d + .agents/skills/security-check/SKILL.md: sha256:0b919d18cd67918421bd9d4044968e28c5a795fb632c29e766db98f28ef4d522 + .agents/skills/security-check/agents/openai.yaml: sha256:6dc7863bcac5c5019b10945b3f4a7d0525f5611a12278b872d45954572ba2a13 + .agents/skills/security-check/references/advisory-review.md: sha256:bd01b017828ae75ca0baf126d20545669175dde84f8dd4d385cb701dbfc33dc9 .agents/skills/security-check/references/artifact-inspection.md: sha256:9842555f4789e77e6cf3d22b000116497207ecf6fa5587f2b1fe0dc20e7dffda .agents/skills/security-check/references/distributed-software-licensing.md: sha256:dce7c9fbfe665eb875388ab732b63b0226a5fd4592b12a62c42b6d1372c0d025 .agents/skills/security-check/references/external-code-execution.md: sha256:03d666ef02095acc8b6d5e03d1bb8378f8b38ce01c6f006d2f7934fcfb6bfe4b - content_hash: sha256:5ffd3a54ff67dcb1007f91ce6d29ad72f3859245e41655b26ceb5ec60231e691 + content_hash: sha256:196cc31549849300ef96c80a2f2f50b4b142946fd70ac448e85a2acc2b3afe30 skill_subset: - apm-workflow - changelog-workflow @@ -230,7 +238,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:0b193b2dc7be40069ae30d5efa8f3c1f229cdef044487264e8554f102a6b26a0 + content_hash: sha256:9112412627ced083e1e687d4b3623217af40cc3f815a2ce294e5e8d5aac1c331 - kind: project-relative target: codex value: .agents/skills/apm-workflow/references/bootstrap-refresh.md @@ -374,7 +382,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:b2cfd8bf9c3c7bd16cf86718877fa025396d15a380de88045122c4d162682cc2 + content_hash: sha256:398fd9d399fbe979bae75b23c277e9b13fac6edd7bdbc645821fc60e9ac856ac - kind: project-relative target: codex value: .agents/skills/code-quality-check/SKILL.md @@ -383,7 +391,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:7415164c33885676d4b579db0560287762a5c2e0e25001dac0e848af1b6c10b0 + content_hash: sha256:1a7897522ac360d9f5607f4fba3141e9745584c9fe3943d11bb7c0a9520659d4 - kind: project-relative target: codex value: .agents/skills/code-quality-check/agents/openai.yaml @@ -401,7 +409,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:f35ad2036a18151dc9dfef8a334989d2b88439478505cd5b047f0621dd613098 + content_hash: sha256:51d42dc39ad47c4f3b908caa0b1fad8835acc516fc5ce6c917733dd410201342 - kind: project-relative target: codex value: .agents/skills/commit-message-quality-check @@ -482,7 +490,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:d3d30f80b163e6e60e6a47c46b79fc6f1afc6047ba093aacd5459432a069872e + content_hash: sha256:983ef785b2daf4b9f46fcf1416bbf39a12ae7d331f7347ceb33270e614a3eeb5 - kind: project-relative target: codex value: .agents/skills/docker-quality-check/assets/github/workflows/main.yml @@ -491,7 +499,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:7aaaecf2bc58c849c1877264f8c1363cd3376a158d25f948111f2adda7a1bf51 + content_hash: sha256:d18b2a7f7162779fcba2af1e4fc662a58f4a30856d1934482dc9668931b3e409 - kind: project-relative target: codex value: .agents/skills/docker-quality-check/assets/github/workflows/pull-request.yml @@ -500,7 +508,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:f2571d65cf632f40ecdaca58334cb1ff793c7770aafffa0d691450216cf50a83 + content_hash: sha256:1adbb3ab5bcae8bb7e61ac9bf9cca70bf6a80311e088e7ceace7cd54b8e7c3e0 - kind: project-relative target: codex value: .agents/skills/docker-quality-check/references/accelerator-runtime-validation.md @@ -698,7 +706,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:8e4d9f8f8fdfba1cf7fe71fa88cac6baffa0d3c7616f744c0e3b1add102be5e7 + content_hash: sha256:0e1c7df4ddf1875dc36643dc6547a07f03e7fae79031b7a51e21f2ed367b9e81 - kind: project-relative target: codex value: .agents/skills/prose-quality-check/SKILL.md @@ -707,7 +715,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:689e54128f766928a5594529c7f7fab4372fff4de42975f98a8eb7698acbceb1 + content_hash: sha256:80470e0ff754f1db845bcff8123e39bcba7ab68b6d2705bd9dce775851b3d718 - kind: project-relative target: codex value: .agents/skills/prose-quality-check/agents/openai.yaml @@ -716,7 +724,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:b83e0a5d151e6e20df6f7d97f268955c6abfd105d53820f6baad0de8403fc062 + content_hash: sha256:a0abf6489b64a09c4322c23e453912ecdc88a3dcf1131ee39d2367e8a2d865e0 - kind: project-relative target: codex value: .agents/skills/prose-quality-check/assets/markdownlint-cli2.yaml @@ -726,6 +734,15 @@ deployments: - aoirint/skills active_owner: aoirint/skills content_hash: sha256:1044e29915fe15e9083f808d1170c84cfc0b848123c0da435cabb9512d39c203 +- kind: project-relative + target: codex + value: .agents/skills/prose-quality-check/references/durable-context.md + runtime: null + scope: project + owners: + - aoirint/skills + active_owner: aoirint/skills + content_hash: sha256:027cc12a9d479890c4a6a88d223c619b2568370aeb6ff37fabb351af85f1dd28 - kind: project-relative target: codex value: .agents/skills/prose-quality-check/references/handoff-notes.md @@ -735,6 +752,24 @@ deployments: - aoirint/skills active_owner: aoirint/skills content_hash: sha256:15470b6bb5ad5ad5e618392d7ae1a3939c0c4e63b2f630196f3d4b6ca56c39f7 +- kind: project-relative + target: codex + value: .agents/skills/prose-quality-check/references/status-wording.md + runtime: null + scope: project + owners: + - aoirint/skills + active_owner: aoirint/skills + content_hash: sha256:3831cad93369c01130ec10084a644e7e86a60760494a302535b9083e8a0064db +- kind: project-relative + target: codex + value: .agents/skills/prose-quality-check/references/writing-guides.md + runtime: null + scope: project + owners: + - aoirint/skills + active_owner: aoirint/skills + content_hash: sha256:40264bc89a19402ef0b8eaf4401dbd8e8213612c47f600b5d9a79cdf5ec5415d - kind: project-relative target: codex value: .agents/skills/python-quality-check @@ -779,7 +814,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:a78b34f3bfdd20cd2624bb093f0a927ea6c2edddc4301a2d60ec8a86e0fa2589 + content_hash: sha256:5722aa8c85e0c180c695778ddf1c199e109782ec054cee85494f90c7e9d4e774 - kind: project-relative target: codex value: .agents/skills/python-quality-check/assets/github/actions/setup-python-locked/resolve-python-contract.sh @@ -788,7 +823,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:71e09fff0baf2630e766c8dd32eef32d0735dbc11b4f25fe335cca10f99548e8 + content_hash: sha256:909608e195549256e86bc041c48fa0de83e43107d80093bc0635c6006ec0c4c5 - kind: project-relative target: codex value: .agents/skills/python-quality-check/references/ci-and-distribution.md @@ -914,7 +949,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:d321689b998388180ac852fdb6374ab3b79bec508a53d00461a9db79fb246d2e + content_hash: sha256:77d4bcc70596b8f4d215ab50ca009e6f325b322240bdd7c69348f4373cb1bc3d - kind: project-relative target: codex value: .agents/skills/security-check/SKILL.md @@ -923,7 +958,7 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:cdc808990ce5eece96a6cb439a389f6611ba8c34ae954789df4ed8936732f63e + content_hash: sha256:0b919d18cd67918421bd9d4044968e28c5a795fb632c29e766db98f28ef4d522 - kind: project-relative target: codex value: .agents/skills/security-check/agents/openai.yaml @@ -932,7 +967,16 @@ deployments: owners: - aoirint/skills active_owner: aoirint/skills - content_hash: sha256:b1021ca2df7466813d0a376fc8bdff83603f568b02ef712e236fb2cfeef377c0 + content_hash: sha256:6dc7863bcac5c5019b10945b3f4a7d0525f5611a12278b872d45954572ba2a13 +- kind: project-relative + target: codex + value: .agents/skills/security-check/references/advisory-review.md + runtime: null + scope: project + owners: + - aoirint/skills + active_owner: aoirint/skills + content_hash: sha256:bd01b017828ae75ca0baf126d20545669175dde84f8dd4d385cb701dbfc33dc9 - kind: project-relative target: codex value: .agents/skills/security-check/references/artifact-inspection.md diff --git a/apm.yml b/apm.yml index 991f03b..2b0ee41 100644 --- a/apm.yml +++ b/apm.yml @@ -8,7 +8,7 @@ targets: dependencies: apm: - git: aoirint/skills - ref: 22fe4f84018358059adcf7709cb9df28d1260fd8 + ref: 1bbdf247da61492e8c1531f341aae400a04b9503 skills: - apm-workflow - changelog-workflow