docguard-cli 0.40.3__tar.gz → 0.40.5__tar.gz

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/.agent/skills/docguard-fix/SKILL.md

@@ -6,10 +6,10 @@ description: AI-driven documentation repair with structured research workflow, t
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.40.3
+  version: 0.40.5
   source: extensions/spec-kit-docguard/skills/docguard-fix
 ---
-<!-- docguard:version: 0.40.3 -->
+<!-- docguard:version: 0.40.5 -->
 
 # DocGuard Fix Skill
 

{docguard_cli-0.40.3/extensions/spec-kit-docguard → docguard_cli-0.40.5/.agent}/skills/docguard-guard/SKILL.md

@@ -7,10 +7,10 @@ description: Run DocGuard guard validation against Canonical-Driven Development
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.40.3
+  version: 0.40.5
   source: extensions/spec-kit-docguard/skills/docguard-guard
 ---
-<!-- docguard:version: 0.40.3 -->
+<!-- docguard:version: 0.40.5 -->
 
 # DocGuard Guard Skill
 

{docguard_cli-0.40.3/extensions/spec-kit-docguard → docguard_cli-0.40.5/.agent}/skills/docguard-review/SKILL.md

@@ -6,10 +6,10 @@ description: Cross-document consistency analysis and quality assessment. Perform
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.40.3
+  version: 0.40.5
   source: extensions/spec-kit-docguard/skills/docguard-review
 ---
-<!-- docguard:version: 0.40.3 -->
+<!-- docguard:version: 0.40.5 -->
 
 # DocGuard Review Skill
 

{docguard_cli-0.40.3/extensions/spec-kit-docguard → docguard_cli-0.40.5/.agent}/skills/docguard-score/SKILL.md

@@ -6,10 +6,10 @@ description: CDD maturity assessment with category-aware improvement roadmap. Ru
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.40.3
+  version: 0.40.5
   source: extensions/spec-kit-docguard/skills/docguard-score
 ---
-<!-- docguard:version: 0.40.3 -->
+<!-- docguard:version: 0.40.5 -->
 
 # DocGuard Score Skill
 

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/.agent/skills/docguard-sync/SKILL.md

@@ -4,10 +4,10 @@ description: Keep canonical documentation ALWAYS UP TO DATE. Refreshes code-trut
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.40.3
+  version: 0.40.5
   source: extensions/spec-kit-docguard/skills/docguard-sync
 ---
-<!-- docguard:version: 0.40.3 -->
+<!-- docguard:version: 0.40.5 -->
 
 # DocGuard Sync Skill
 

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/.docguard-specs.json

@@ -423,12 +423,12 @@
           {
             "requirementId": "FR-018",
             "file": "tests/hooks-contract.test.mjs",
-            "line": 11
+            "line": 13
           },
           {
             "requirementId": "FR-019",
             "file": "tests/hooks-contract.test.mjs",
-            "line": 12
+            "line": 14
           },
           {
             "requirementId": "FR-020",
@@ -2030,7 +2030,7 @@
           ]
         },
         "reconciliation": {
-          "lastReviewedRevision": "46531e4918f9479b81ffb52e6e27c24b533575da",
+          "lastReviewedRevision": "9e4a68f5a79d3439806396e7dcf4e5729b90bb57",
           "outcomes": [
             {
               "revision": "46531e4918f9479b81ffb52e6e27c24b533575da",
@@ -2042,6 +2042,30 @@
               ],
               "deviations": [],
               "successor": null
+            },
+            {
+              "revision": "f4bb00638da2d1a53ad1a67928e35e1dfe1b401d",
+              "reason": "Verified v0.40.3 repository-token release PR #386: scheduled run 34922506777 armed native auto-merge; approved CI 34922605581 and supply-chain 34922605917 passed; merge e27d6bf triggered publication run 34922784629; npm, PyPI, GHCR, GitHub Release, extension ZIP, MCPB, and catalog reminder completed with no accepted deviations.",
+              "evidence": [
+                ".github/scripts/validate-release-candidate.mjs",
+                "cli/release-pr-policy.mjs",
+                "docs-canonical/CI-RECIPES.md",
+                "tests/scheduled-release.test.mjs"
+              ],
+              "deviations": [],
+              "successor": null
+            },
+            {
+              "revision": "9e4a68f5a79d3439806396e7dcf4e5729b90bb57",
+              "reason": "Finalized the v0.40.3 tokenless release evidence at durable main revision 9e4a68f: scheduled run 34922506777 created release PR #386; approved CI 34922605581 and supply-chain 34922605917 passed; native auto-merge produced e27d6bf; publication run 34922784629 completed npm, PyPI, GHCR, GitHub Release, extension ZIP, MCPB, and catalog reminder with no accepted deviations.",
+              "evidence": [
+                ".github/scripts/validate-release-candidate.mjs",
+                "cli/release-pr-policy.mjs",
+                "docs-canonical/CI-RECIPES.md",
+                "tests/scheduled-release.test.mjs"
+              ],
+              "deviations": [],
+              "successor": null
             }
           ]
         }
@@ -2070,19 +2094,19 @@
         "artifacts": [
           {
             "path": "specs/011-tokenless-scheduled-releases/spec.md",
-            "digest": "sha256:507528b6a9e43ae748a000fa8b6bf166d1408e271ee1e9c6348729eda172e30c"
+            "digest": "sha256:a69909db1d7c93b320eb330e2fc23336eb31029c2a17aa6db09337078ac0d45a"
           },
           {
             "path": "specs/011-tokenless-scheduled-releases/plan.md",
-            "digest": "sha256:f902658d4173718522335f70ec436040db5a7a8ee7677975d38d4984c832d30a"
+            "digest": "sha256:c28be466978c5e7ba99229ab0c0a6c58614dc1f649039d068be3219278c9be8b"
           },
           {
             "path": "specs/011-tokenless-scheduled-releases/tasks.md",
-            "digest": "sha256:1af12c52080eaa54711646ced72490094d17383b157510c98e7df7012e9ace22"
+            "digest": "sha256:2930c32b2128cb0dbfaa98a1cf84ddce037e0639fcdcb49bafdef74e2d500361"
           }
         ],
         "taskCompletion": {
-          "checked": 14,
+          "checked": 15,
           "total": 15
         },
         "implementationEvidence": [
@@ -2106,6 +2130,11 @@
             "file": "cli/release-pr-policy.mjs",
             "line": 7
           },
+          {
+            "requirementId": "FR-009",
+            "file": ".github/scripts/validate-release-candidate.mjs",
+            "line": 8
+          },
           {
             "requirementId": "FR-011",
             "file": "cli/release-pr-policy.mjs",

docguard_cli-0.40.5/.github/scripts/upsert-catalog-reminder.sh

@@ -0,0 +1,50 @@
+#!/usr/bin/env bash
+
+set -euo pipefail
+
+VERSION="${1:?usage: upsert-catalog-reminder.sh <version> <body-file>}"
+BODY_FILE="${2:?usage: upsert-catalog-reminder.sh <version> <body-file>}"
+REPOSITORY="${GITHUB_REPOSITORY:?GITHUB_REPOSITORY is required}"
+TITLE="📦 Submit DocGuard v${VERSION} to the spec-kit community catalog"
+
+if [[ ! "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
+  echo "Invalid release version: $VERSION" >&2
+  exit 1
+fi
+if [[ ! -f "$BODY_FILE" ]]; then
+  echo "Reminder body does not exist: $BODY_FILE" >&2
+  exit 1
+fi
+
+reminders=$(
+  gh issue list \
+    --repo "$REPOSITORY" \
+    --state open \
+    --limit 100 \
+    --json number,title \
+    --jq '.[] | select(.title | startswith("📦 Submit DocGuard v") and endswith(" to the spec-kit community catalog")) | .number' \
+    | sort -n
+)
+
+if [[ -z "$reminders" ]]; then
+  gh issue create --repo "$REPOSITORY" --title "$TITLE" --body-file "$BODY_FILE"
+  echo "✅ Opened catalog-submission reminder issue"
+  exit 0
+fi
+
+current=$(printf '%s\n' "$reminders" | tail -n 1)
+gh issue edit "$current" --repo "$REPOSITORY" --title "$TITLE" --body-file "$BODY_FILE"
+echo "✅ Refreshed reminder issue #${current}"
+
+while IFS= read -r duplicate; do
+  if [[ -z "$duplicate" ]]; then
+    continue
+  fi
+  if [[ "$duplicate" == "$current" ]]; then
+    continue
+  fi
+  gh issue close "$duplicate" \
+    --repo "$REPOSITORY" \
+    --comment "Superseded by the current catalog reminder #${current}."
+  echo "✅ Closed superseded reminder issue #${duplicate}"
+done <<< "$reminders"

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/.github/scripts/validate-release-candidate.mjs

@@ -4,6 +4,8 @@
  * Validate the scheduler-generated release diff before it leaves the trusted
  * default-branch checkout. GitHub's native auto-merge then enforces the
  * repository's required pull-request checks on every candidate revision.
+ *
+ * @implements docguard.tokenless-scheduled-releases#FR-009
  */
 
 import { execFileSync } from 'node:child_process';

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/.github/workflows/release.yml

@@ -459,7 +459,6 @@ jobs:
         run: |
           VERSION="${{ steps.meta.outputs.version }}"
           SUBMIT_URL=$(cat /tmp/submit-url.txt)
-          TITLE="📦 Submit DocGuard v${VERSION} to the spec-kit community catalog"
 
           # Compose the reminder body: one-click prefilled form link + the full
           # field-by-field body as a paste fallback (URL prefill can truncate).
@@ -485,21 +484,7 @@ jobs:
             echo "</details>"
           } > /tmp/reminder.md
 
-          # Idempotent per-version: refresh the existing reminder, else open one.
-          EXISTING=$(gh issue list \
-            --repo "$GITHUB_REPOSITORY" \
-            --state open \
-            --search "in:title \"DocGuard v${VERSION}\" spec-kit catalog" \
-            --json number,title \
-            --jq "[.[] | select(.title | contains(\"v${VERSION}\"))][0].number" 2>/dev/null || echo "")
-
-          if [ -n "$EXISTING" ] && [ "$EXISTING" != "null" ]; then
-            gh issue edit "$EXISTING" --repo "$GITHUB_REPOSITORY" --body-file /tmp/reminder.md
-            echo "✅ Refreshed reminder issue #${EXISTING}"
-          else
-            gh issue create --repo "$GITHUB_REPOSITORY" --title "$TITLE" --body-file /tmp/reminder.md
-            echo "✅ Opened catalog-submission reminder issue"
-          fi
+          bash .github/scripts/upsert-catalog-reminder.sh "$VERSION" /tmp/reminder.md
 
       - name: Write run summary
         run: |

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/.github/workflows/sync-speckit-catalog.yml

@@ -58,7 +58,6 @@ jobs:
         run: |
           VERSION="${{ steps.meta.outputs.version }}"
           SUBMIT_URL=$(cat /tmp/submit-url.txt)
-          TITLE="📦 Submit DocGuard v${VERSION} to the spec-kit community catalog"
 
           {
             echo "Update the spec-kit community catalog for **v${VERSION}**"
@@ -82,20 +81,7 @@ jobs:
             echo "</details>"
           } > /tmp/reminder.md
 
-          EXISTING=$(gh issue list \
-            --repo "$GITHUB_REPOSITORY" \
-            --state open \
-            --search "in:title \"DocGuard v${VERSION}\" spec-kit catalog" \
-            --json number,title \
-            --jq "[.[] | select(.title | contains(\"v${VERSION}\"))][0].number" 2>/dev/null || echo "")
-
-          if [ -n "$EXISTING" ] && [ "$EXISTING" != "null" ]; then
-            gh issue edit "$EXISTING" --repo "$GITHUB_REPOSITORY" --body-file /tmp/reminder.md
-            echo "✅ Refreshed reminder issue #${EXISTING}"
-          else
-            gh issue create --repo "$GITHUB_REPOSITORY" --title "$TITLE" --body-file /tmp/reminder.md
-            echo "✅ Opened catalog-submission reminder issue"
-          fi
+          bash .github/scripts/upsert-catalog-reminder.sh "$VERSION" /tmp/reminder.md
 
       - name: Write run summary
         run: |

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/.wolf/buglog.json

@@ -5763,6 +5763,100 @@
       ],
       "occurrences": 1,
       "last_seen": "2026-09-15T02:37:35.000Z"
+    },
+    {
+      "id": "bug-348",
+      "timestamp": "2026-09-15T03:05:00.000Z",
+      "error_message": "Each successful release opened another version-specific Spec Kit catalog reminder and left all prior reminders open",
+      "file": ".github/workflows/release.yml; .github/workflows/sync-speckit-catalog.yml; .github/scripts/upsert-catalog-reminder.sh",
+      "root_cause": "Both workflows searched only for an open issue containing the current release version, so the documented refresh path could never find a reminder from an earlier version",
+      "fix": "Route both workflows through one tested helper that refreshes the newest open DocGuard catalog reminder and closes every older matching reminder as superseded",
+      "tags": [
+        "release",
+        "catalog",
+        "github-issues",
+        "idempotency",
+        "cleanup"
+      ],
+      "related_bugs": [],
+      "occurrences": 5,
+      "last_seen": "2026-09-15T03:05:00.000Z"
+    },
+    {
+      "id": "bug-349",
+      "timestamp": "2026-09-15T03:45:00.000Z",
+      "error_message": "The published Spec Kit extension installed successfully while fix and review resolved to the wrong command files and three shipped commands were undeclared",
+      "file": "extensions/spec-kit-docguard/extension.yml",
+      "root_cause": "The installer validated manifest syntax and file existence but the repository had no contract test for one-to-one command identity or completeness against the shipped commands directory",
+      "fix": "Map each namespaced command to its same-named file, declare init/sync/trace, add a read-only review command, and enforce unique complete name-to-file registration in tests",
+      "tags": [
+        "release",
+        "spec-kit",
+        "manifest",
+        "command-routing",
+        "packaging"
+      ],
+      "related_bugs": [
+        "bug-311",
+        "bug-331"
+      ],
+      "occurrences": 1,
+      "last_seen": "2026-09-15T03:45:00.000Z"
+    },
+    {
+      "id": "bug-350",
+      "timestamp": "2026-09-15T03:52:00.000Z",
+      "error_message": "The published extension manifest description exceeded Spec Kit's documented 200-character limit and differed from the catalog description",
+      "file": "extensions/spec-kit-docguard/extension.yml; .github/scripts/speckit-submission.py",
+      "root_cause": "The installer accepted the overlong value and the manifest and catalog generator maintained independent untested descriptions",
+      "fix": "Use one bounded description on both surfaces and test exact parity plus the upstream length limit",
+      "tags": [
+        "release",
+        "spec-kit",
+        "manifest",
+        "catalog",
+        "metadata"
+      ],
+      "related_bugs": [
+        "bug-311",
+        "bug-349"
+      ],
+      "occurrences": 1,
+      "last_seen": "2026-09-15T03:52:00.000Z"
+    },
+    {
+      "id": "bug-351",
+      "timestamp": "2026-09-15T04:00:00.000Z",
+      "error_message": "gh pr diff rejected the unsupported --check flag during self-review",
+      "file": "session GitHub CLI commands",
+      "root_cause": "The whitespace-check flag belongs to git diff, not gh pr diff",
+      "fix": "Use git diff --check for whitespace validation and gh pr diff --patch or --name-only for pull-request review",
+      "tags": [
+        "tooling",
+        "github-cli",
+        "self-review"
+      ],
+      "related_bugs": [],
+      "occurrences": 1,
+      "last_seen": "2026-09-15T04:00:00.000Z"
+    },
+    {
+      "id": "bug-352",
+      "timestamp": "2026-09-15T04:15:00.000Z",
+      "error_message": "A passing freshness assertion failed the v0.40.5 release gate when temporary Git repository cleanup raised ENOTEMPTY",
+      "file": "tests/freshness.test.mjs",
+      "root_cause": "The suite removed Git object directories with a single rmSync attempt even though filesystem and antivirus activity can transiently repopulate or retain entries during recursive deletion",
+      "fix": "Use Node's bounded maxRetries and retryDelay options for recursive cleanup, matching the repository's established Git-fixture cleanup pattern",
+      "tags": [
+        "tests",
+        "release",
+        "filesystem",
+        "flaky-test",
+        "cleanup"
+      ],
+      "related_bugs": [],
+      "occurrences": 1,
+      "last_seen": "2026-09-15T04:15:00.000Z"
     }
   ]
 }

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/.wolf/cerebrum.md

@@ -14,6 +14,8 @@
 
 ## Key Learnings
 
+- **2026-09-15 — A successful Spec Kit install does not prove manifest correctness.** The v0.40.4 ZIP passed validation and installed, yet `fix` resolved to `generate`, `review` resolved to `diagnose`, three shipped command files were absent from `provides.commands`, and its description exceeded the documented 200-character limit. Treat the manifest as an executable public API: require unique names and files, match every `speckit.docguard.<verb>` to `commands/<verb>.md`, compare declarations with the complete shipped directory, keep catalog metadata byte-aligned, and inspect the installed inventory before catalog submission.
+
 - **2026-09-14 — Release-generated skill parity:** The scheduled release updates extension skill metadata through `fix --write`, whose headless mode correctly skips setup. It must then run an explicit managed-agent sync before tests and staging; otherwise `.agent/skills` remains one release behind. A repository parity test should compare every managed copy byte-for-byte with its extension source.
 - **2026-09-14 — Lifecycle control plane:** Active approved prose owns behavioral intent; `.docguard-specs.json` owns reviewed lifecycle, lineage, scope, and persistence policy while regenerating observed evidence deterministically. Approval, delivery, context, retirement reason, storage, and persistence model are separate dimensions. Use immutable `specId#requirementId` identities and preserve retired tombstones; path-qualified IDs are only a migration format.
 - **2026-09-14 — Retirement is stricter than completion:** Checked tasks and `Status: Completed` are review signals. Verification requires exact-revision implementation/test evidence plus reconciled canonical outcomes. Retirement additionally requires a retained Git ref, clean replacement/evidence docs, no live backreferences, a compatible persistence model, and fresh context. The public verb is `retire` because Spec Kit Archive already means consolidation.

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/CHANGELOG.md

@@ -7,6 +7,50 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.40.5] - 2026-09-15
+
+Automated weekly release — batches everything merged since `v0.40.4`.
+
+### Changed
+
+- test: retry transient freshness cleanup (#393)
+- fix: make Spec Kit command manifest complete (#392)
+
+
+### Fixed
+
+- Retry removal of temporary Git repositories when the operating system reports
+  a transient `ENOTEMPTY`, preventing a completed freshness test from randomly
+  blocking the release gate during teardown.
+- Register every command shipped by the Spec Kit extension, route `fix` and
+  `review` to their matching command files, keep the manifest description inside
+  Spec Kit's 200-character limit, and add release-contract tests that reject
+  missing, duplicate, mismatched, undeclared, or divergent metadata.
+- Record the supported `git diff --check` and `gh pr diff --patch` split in the
+  project learning log so release self-review does not repeat an invalid CLI call.
+
+## [0.40.4] - 2026-09-15
+
+Automated weekly release — batches everything merged since `v0.40.3`.
+
+### Changed
+
+- fix: consolidate catalog reminders (#390)
+- docs: finalize durable R8 outcome (#389)
+- docs: close R8 release verification (#388)
+
+
+### Changed
+
+- Reuse one open Spec Kit catalog reminder across releases and close older
+  reminders as superseded, preventing the release workflow from accumulating a
+  stale version-specific issue queue.
+- Close the R8 living release contract with exact v0.40.3 evidence: the
+  repository-token release PR armed protected native auto-merge, passed the
+  approved CI and supply-chain checks, merged automatically, and triggered the
+  complete npm, PyPI, GHCR, GitHub Release, extension, MCPB, and catalog flow
+  through the scheduler's bounded continuation.
+
 ## [0.40.3] - 2026-09-15
 
 Automated weekly release — batches everything merged since `v0.40.2`.

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: docguard-cli
-Version: 0.40.3
+Version: 0.40.5
 Summary: The enforcement tool for Canonical-Driven Development (CDD). Audit, generate, and guard your project documentation. No Python dependencies (requires Node.js 18+).
 Project-URL: Homepage, https://github.com/raccioly/docguard
 Project-URL: Documentation, https://github.com/raccioly/docguard#readme

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/ROADMAP.md

@@ -1,6 +1,6 @@
 # DocGuard Roadmap
 
-<!-- docguard:last-reviewed 2026-09-14 -->
+<!-- docguard:last-reviewed 2026-09-15 -->
 
 This file contains current product intent only. Released work belongs in
 `CHANGELOG.md`; implementation history remains recoverable from Git. Completed or
@@ -19,8 +19,7 @@ ideas below are research candidates rather than unfinished commitments.
 
 ## Delivered roadmap
 
-R1–R8 are implemented and evidence-reviewed. R1–R7 are released; R8 is verified
-on `main` and will ship with the next substantive release. The maintained living
+R1–R8 are implemented, evidence-reviewed, and released. The maintained living
 specifications remain current verification contracts; historical implementation
 plans are recoverable from Git and do not create a second source of truth.
 
@@ -216,7 +215,7 @@ Node 18, 20, 22, and 24. Packed-package tests run task context without the
 optional parser, and the independent detector corpus remains regression-free
 across 24 evaluable cases plus one explicit unsupported case.
 
-### R8 — Tokenless scheduled releases (verified on `main`)
+### R8 — Tokenless scheduled releases (released in v0.40.3)
 
 Governing spec: `specs/011-tokenless-scheduled-releases/spec.md`.
 
@@ -235,8 +234,8 @@ a missing tag before another version increment.
   no accepted deviations.
 - [x] Publish v0.40.1 through release PR #380 and verify npm, PyPI, GHCR, GitHub
   release assets, and the Spec Kit catalog reminder.
-- [ ] Verify the corrected repository-token native auto-merge continuation on
-  the next release and retain exact evidence.
+- [x] Verify the corrected repository-token native auto-merge continuation on
+  v0.40.3 and retain exact evidence.
 
 The retained live probe used CI run `34912654565` and privileged gate run
 `34912788971`. All Node 18, 20, 22, and 24 jobs passed. The trusted gate
@@ -247,12 +246,18 @@ evidence landed through pull requests #371, #373, and #374.
 Release PR #380 passed CI run `34920481989` and supply-chain run `34920482409`,
 merged at `5b2dfe4`, and published v0.40.1 in run `34920702346`. That run also
 proved the final GitHub boundary: approving the held workflow does not emit a
-second `workflow_run` completion. Native auto-merge is now the continuation;
-release PR #383 proved the repository token can arm it and GitHub can merge after
-approved checks. That merge also proved its bot-originated push does not trigger
-publication. A bounded scheduler wait plus hourly tag-driven recovery is the
-final continuation under verification; exact publication evidence remains the
-only open R8 item.
+second `workflow_run` completion. Release PR #383 proved the repository token
+can arm native auto-merge and GitHub can merge after approved checks, while its
+bot-originated push proved publication needs an explicit continuation.
+
+Scheduled run `34922506777` created repository-token release PR #386 and armed
+native auto-merge. After one maintainer approval, CI run `34922605581` and
+supply-chain run `34922605917` passed; GitHub merged the exact head at
+`e27d6bf0203708ee8206a1434eb292520f4c4494`. The bounded scheduler wait then
+dispatched publication run `34922784629`, which passed the four-runtime matrix,
+self-guard, npm, PyPI, GHCR, GitHub Release, extension ZIP, MCPB, and catalog
+reminder jobs. The published npm and PyPI versions and GitHub tag all resolve to
+v0.40.3, completing R8 without a stored release credential.
 
 ## Contribution standard
 

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/docs-canonical/CI-RECIPES.md

@@ -1,6 +1,6 @@
 # CI Recipes
 
-<!-- docguard:last-reviewed 2026-09-14 -->
+<!-- docguard:last-reviewed 2026-09-15 -->
 <!-- docguard:status active -->
 
 ## Recipe 1 — Guard (mandatory CI gate)
@@ -81,6 +81,19 @@ sole publication trigger. The bounded wait handles the normal approval path; the
 hourly tag sweep supplies durable recovery without continuous polling or another
 credential.
 
+The v0.40.3 release is the retained end-to-end proof. Scheduled run
+`34922506777` opened repository-token PR #386 and armed native auto-merge. After
+one maintainer workflow approval, CI run `34922605581` and supply-chain run
+`34922605917` passed, GitHub merged
+`e27d6bf0203708ee8206a1434eb292520f4c4494`, and the bounded wait dispatched
+publication run `34922784629`. That run published npm, PyPI, GHCR, the GitHub
+Release, extension ZIP, and MCPB and refreshed the catalog reminder.
+
+Catalog submission remains an explicit human action. The release and manual
+catalog workflows maintain one open reminder in this repository: each run
+refreshes the newest matching issue to the current version and closes older
+matching reminders as superseded.
+
 ## Recipe 3b — Spec completion and post-hoc reconciliation
 
 Run `docguard reconcile --since <merge-base> --format json` when implementation

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/docs-canonical/TEST-SPEC.md

@@ -58,6 +58,7 @@ All test files live in `tests/` and match the glob `tests/*.test.mjs` — the te
 | `cli/commands/agents.mjs` | `tests/commands.test.mjs` | ✅ |
 | `cli/commands/agent.mjs`, `cli/scanners/task-context.mjs` | `tests/agent.test.mjs`, `tests/task-context.test.mjs` | ✅ |
 | `cli/commands/hooks.mjs` | `tests/commands.test.mjs` | ✅ |
+| `extensions/spec-kit-docguard/extension.yml`, `extensions/spec-kit-docguard/commands/*.md` | `tests/hooks-contract.test.mjs` | ✅ |
 | `cli/commands/diagnose.mjs` | `tests/commands.test.mjs` | ✅ |
 | `cli/commands/badge.mjs` | `tests/commands.test.mjs` | ✅ |
 | `cli/commands/ci.mjs` | `tests/commands.test.mjs` | ✅ |

{docguard_cli-0.40.3 → docguard_cli-0.40.5}/extensions/spec-kit-docguard/README.md

@@ -45,12 +45,15 @@ docguard score
 
 | Command | Alias | Purpose |
 |---------|-------|---------|
+| `speckit.docguard.init` | `docguard.init` | Initialize CDD in a project |
 | `speckit.docguard.guard` | `docguard.guard` | Run configurable quality gate with severity triage |
 | `speckit.docguard.fix` | `docguard.fix` | AI-driven documentation repair with codebase research |
 | `speckit.docguard.review` | `docguard.review` | Cross-document semantic consistency analysis (read-only) |
 | `speckit.docguard.score` | `docguard.score` | CDD maturity score with ROI improvement roadmap |
 | `speckit.docguard.diagnose` | — | Diagnose issues + generate multi-perspective AI prompts |
 | `speckit.docguard.generate` | — | Reverse-engineer canonical docs from codebase |
+| `speckit.docguard.sync` | — | Refresh code-truth sections and flag prose for review |
+| `speckit.docguard.trace` | — | Generate requirements traceability matrix |
 | `speckit.docguard.brief` | — | Load current spec intent before specification |
 | `speckit.docguard.preflight` | — | Gate the generated spec before task generation |
 | `speckit.docguard.complete` | — | Plan reviewed completion and regenerate active context after verification |

docguard_cli-0.40.5/extensions/spec-kit-docguard/commands/review.md

@@ -0,0 +1,50 @@
+---
+description: "Review documentation against code without modifying the repository"
+allowed-tools: Bash, Read
+handoffs:
+  - label: Fix Reviewed Issues
+    agent: docguard.fix
+    prompt: Fix the documentation issues confirmed by the review
+  - label: Run Guard
+    agent: docguard.guard
+    prompt: Validate all checks after approved fixes
+---
+
+# DocGuard Review
+
+Perform a read-only semantic review of canonical documentation against the
+repository. Report evidence and recommendations; do not edit files.
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding when it is not empty.
+
+## Execution
+
+1. Run the deterministic inventory and quality checks:
+
+```bash
+npx --yes docguard-cli@latest diagnose $ARGUMENTS
+npx --yes docguard-cli@latest diff $ARGUMENTS
+npx --yes docguard-cli@latest score $ARGUMENTS
+npx --yes docguard-cli@latest verify --evidence --format json $ARGUMENTS
+npx --yes docguard-cli@latest verify --semantic $ARGUMENTS
+```
+
+2. Read the canonical documents and their cited code. Check architecture,
+   schemas, security claims, test coverage, terminology, and cross-references.
+3. For every contradiction, identify whether approved documentation or current
+   code owns the intended behavior. A mismatch can be a code regression.
+4. Return a severity-ranked report with exact file paths, evidence, confidence,
+   and a proposed next action. Keep unsupported claims explicitly unverified.
+
+## Constraints
+
+- Do not modify files or treat a clean structural guard as proof that prose is
+  factually correct.
+- Do not rewrite canonical intent to match code until ownership is resolved.
+- Cap the report at 50 findings and aggregate lower-priority overflow.