docguard-cli 0.40.2__tar.gz → 0.40.4__tar.gz

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/.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.2
+  version: 0.40.4
   source: extensions/spec-kit-docguard/skills/docguard-fix
 ---
-<!-- docguard:version: 0.40.2 -->
+<!-- docguard:version: 0.40.4 -->
 
 # DocGuard Fix Skill
 

{docguard_cli-0.40.2/extensions/spec-kit-docguard → docguard_cli-0.40.4/.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.2
+  version: 0.40.4
   source: extensions/spec-kit-docguard/skills/docguard-guard
 ---
-<!-- docguard:version: 0.40.2 -->
+<!-- docguard:version: 0.40.4 -->
 
 # DocGuard Guard Skill
 

{docguard_cli-0.40.2/extensions/spec-kit-docguard → docguard_cli-0.40.4/.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.2
+  version: 0.40.4
   source: extensions/spec-kit-docguard/skills/docguard-review
 ---
-<!-- docguard:version: 0.40.2 -->
+<!-- docguard:version: 0.40.4 -->
 
 # DocGuard Review Skill
 

{docguard_cli-0.40.2/extensions/spec-kit-docguard → docguard_cli-0.40.4/.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.2
+  version: 0.40.4
   source: extensions/spec-kit-docguard/skills/docguard-score
 ---
-<!-- docguard:version: 0.40.2 -->
+<!-- docguard:version: 0.40.4 -->
 
 # DocGuard Score Skill
 

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/.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.2
+  version: 0.40.4
   source: extensions/spec-kit-docguard/skills/docguard-sync
 ---
-<!-- docguard:version: 0.40.2 -->
+<!-- docguard:version: 0.40.4 -->
 
 # DocGuard Sync Skill
 

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/.docguard-specs.json

@@ -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:b5e9f78c62a085b06c30a1ef2a67c45df9a2177aa75f25049c42c7c71e99e543"
+            "digest": "sha256:a69909db1d7c93b320eb330e2fc23336eb31029c2a17aa6db09337078ac0d45a"
           },
           {
             "path": "specs/011-tokenless-scheduled-releases/plan.md",
-            "digest": "sha256:f833cdcbe825ab6a75ab484ac586ef3e36a984b7856f196730bb6ca5cdd0393e"
+            "digest": "sha256:c28be466978c5e7ba99229ab0c0a6c58614dc1f649039d068be3219278c9be8b"
           },
           {
             "path": "specs/011-tokenless-scheduled-releases/tasks.md",
-            "digest": "sha256:9b49cf5672efd0bea5ccca4e1c83239c77854e5733630ab64e800185e1fa44a9"
+            "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.4/.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.2 → docguard_cli-0.40.4}/.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.2 → docguard_cli-0.40.4}/.github/workflows/release.yml

@@ -3,6 +3,11 @@ name: Auto Release — Tag, GitHub Release, npm, PyPI
 # Triggers on push to main — detects version bumps automatically
 on:
   workflow_dispatch: # Allow manual trigger for recovery
+  schedule:
+    # GitHub suppresses push workflows when native auto-merge was armed by
+    # GITHUB_TOKEN. This cheap tag-driven sweep makes late approvals recover
+    # within an hour without a PAT, App key, or continuously polling runner.
+    - cron: '17 * * * *'
   push:
     branches: [main]
     paths:
@@ -454,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).
@@ -480,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.2 → docguard_cli-0.40.4}/.github/workflows/scheduled-release.yml

@@ -11,9 +11,9 @@ name: Scheduled Release
 # HOW IT TRIGGERS THE ACTUAL RELEASE: the repository token validates and opens a
 # protected PR, then arms GitHub's native squash auto-merge. GitHub intentionally
 # holds that PR's workflows for one maintainer approval. Once approved, ordinary
-# PR CI satisfies the required checks, native auto-merge updates main, and the
-# package.json push starts release.yml. A later schedule retries publication when
-# package.json has no corresponding tag.
+# PR CI satisfies the required checks and native auto-merge updates main. The
+# scheduler waits briefly and dispatches release.yml after that merge; an hourly
+# tag-driven sweep recovers approvals that happen after the wait ends.
 #
 # NO-OP WHEN NOTHING CHANGED: if there are no commits since the last release
 # tag, this exits without bumping — no empty releases.
@@ -159,6 +159,24 @@ jobs:
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
+          wait_for_merge_and_publish() {
+            PR_URL="$1"
+            for ATTEMPT in $(seq 1 40); do
+              STATE=$(gh pr view "$PR_URL" --json state --jq '.state')
+              if [ "$STATE" = "MERGED" ]; then
+                echo "Release PR merged; dispatching tag-driven publication."
+                gh workflow run release.yml --ref main
+                return 0
+              fi
+              if [ "$STATE" = "CLOSED" ]; then
+                echo "::error::Release PR closed without merge."
+                return 1
+              fi
+              sleep 15
+            done
+            echo "::notice::Release PR remains open after 10 minutes. The hourly tag-driven release sweep will publish after later approval and merge."
+          }
+
           BRANCH="release/v${NEW_VERSION}"
           node .github/scripts/validate-release-candidate.mjs \
             --base-version "${{ steps.check.outputs.current }}" \
@@ -173,6 +191,7 @@ jobs:
             fi
             gh pr merge --auto --squash "$EXISTING"
             echo "Auto-merge armed. Maintainer action required: approve the PR workflows in GitHub."
+            wait_for_merge_and_publish "$EXISTING"
             exit 0
           fi
           if git ls-remote --exit-code --heads origin "$BRANCH" >/dev/null 2>&1; then
@@ -186,7 +205,7 @@ jobs:
           git commit -m "release: v${NEW_VERSION} — automated weekly batch
 
           Cut by .github/workflows/scheduled-release.yml. Publishing itself is
-          handled by release.yml after protected native auto-merge updates main."
+          dispatched after protected native auto-merge updates main."
           git push origin "$BRANCH"
 
           PR_URL=$(gh pr create \
@@ -197,7 +216,8 @@ jobs:
 
           Batches everything merged since \`${{ steps.check.outputs.last_tag }}\`. Tests and \`guard\` already passed on this tree before the PR was opened.
 
-          **Maintainer action required:** select **Approve workflows to run** in GitHub. The ordinary pull-request CI then satisfies branch protection; GitHub's protected native auto-merge merges the exact green head, and the resulting \`package.json\` push starts \`release.yml\` to tag and publish.")
+          **Maintainer action required:** select **Approve workflows to run** in GitHub. The ordinary pull-request CI then satisfies branch protection; GitHub's protected native auto-merge merges the exact green head, and the waiting scheduler dispatches \`release.yml\`. An hourly tag-driven sweep recovers later approvals.")
 
           gh pr merge --auto --squash "$PR_URL"
           echo "Opened $BRANCH with auto-merge armed. Approve its workflows in GitHub to continue the release."
+          wait_for_merge_and_publish "$PR_URL"

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/.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.2 → docguard_cli-0.40.4}/.wolf/buglog.json

@@ -5743,6 +5743,44 @@
       ],
       "occurrences": 1,
       "last_seen": "2026-09-15T02:18:57.000Z"
+    },
+    {
+      "id": "bug-347",
+      "timestamp": "2026-09-15T02:37:35.000Z",
+      "error_message": "Repository-token native auto-merge completed release PR #383 but its package.json push did not start release.yml",
+      "file": ".github/workflows/scheduled-release.yml; .github/workflows/release.yml",
+      "root_cause": "GitHub treated the native merge armed by GITHUB_TOKEN as repository-token-originated activity and suppressed the downstream push workflow",
+      "fix": "Keep the scheduler alive for a bounded merge wait and dispatch publication explicitly, with an hourly tag-driven release sweep for approvals after that window and interrupted publication",
+      "tags": [
+        "release",
+        "github-token",
+        "native-auto-merge",
+        "workflow-recursion",
+        "recovery"
+      ],
+      "related_bugs": [
+        "bug-346"
+      ],
+      "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"
     }
   ]
 }

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/.wolf/cerebrum.md

@@ -78,7 +78,7 @@
 - **2026-09-14** — Never treat a Git object ID as durable recovery by itself; unreachable commits and blobs can be garbage-collected after squash merges or branch deletion. Require the source revision to be an ancestor of a recorded retention ref and report recoverability explicitly.
 - **2026-09-14** — Never count a bare requirement ID as feature-completion evidence. Once the original spec is retired, a formerly ambiguous `FR-012` can become unique and silently rebind to another feature. Feature gates require a qualified stable identity; retired identities remain tombstoned.
 - **2026-09-14** — A document retirement command must reject source files, submodules, untracked/ignored leftovers, dirty evidence, and live links before mutation. `Completed` artifact maturity does not authorize removal, especially when the Spec Kit Archive extension intentionally retains completed feature files.
-- **2026-09-14** — Protected scheduled releases can avoid a persistent credential, but GitHub requires one maintainer approval for workflows on a PR created by `GITHUB_TOKEN`. Dispatched jobs do not satisfy required pull-request checks, and approving an `action_required` run does not emit a second `workflow_run` completion. Validate the generated candidate in the trusted scheduler before push, arm native auto-merge only where required checks are configured, and let the merged version push start publication. A missing tag is recovered before another bump; retain failed release attempts as evidence and close their generated PRs and branches.
+- **2026-09-14** — Protected scheduled releases can avoid a persistent credential, but GitHub requires one maintainer approval for workflows on a PR created by `GITHUB_TOKEN`. Dispatched jobs do not satisfy required pull-request checks, approving an `action_required` run does not emit a second `workflow_run` completion, and a native merge armed by the repository token suppresses downstream push workflows. Validate the candidate in the trusted scheduler before push, arm native auto-merge only where required checks exist, wait briefly to dispatch publication after merge, and run an hourly tag-driven recovery for later approvals. Retain failed release attempts as evidence and close their generated PRs and branches.
 
 - **2026-07-15** — `docguard ci` was silently routed through `runInit --with ci` since v0.20: the pipeline gate scaffolded missing docs into the workspace and corrupted `--format json` stdout with init chrome (bug-228). Un-deprecated in v0.33 (direct runCI dispatch). Lesson: when a command is deprecated-with-routing, verify the ROUTE preserves the command's contract (read-only? machine stdout?) — a passing test suite didn't catch it because the consolidation test only asserted the warning text, not the side effects.
 - **2026-07-03** — Adding a machine output format to a command is TWO changes, not one: the format branch in the command AND the dispatcher's `jsonMode` gate (docguard.mjs ~line 515). `guard --format sarif` initially emitted the banner + ensureSkills chrome INTO the SARIF stream because `jsonMode` only recognized `'json'` — caught by the spawn test's no-ANSI assertion before ship. Any future format (`junit`, `csv`, …) must join that gate or stdout is corrupted for parsers. Same class as the READ_ONLY_COMMANDS gotcha (learning #17).

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/CHANGELOG.md

@@ -7,6 +7,51 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [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`.
+
+### Changed
+
+- fix: recover tokenless release publication (#385)
+
+
+### Added
+
+- Add an hourly tag-driven release recovery sweep. Already tagged versions stop
+  after detection, while a merged but unpublished package version enters the
+  existing serialized test, tag, and registry publication transaction.
+
+### Fixed
+
+- Keep the scheduled release job alive for a bounded ten-minute approval window
+  and dispatch publication once native auto-merge completes. This covers the
+  normal operator flow without a persistent credential or an always-on poller.
+- Stop relying on the `package.json` push from a native auto-merge armed by
+  `GITHUB_TOKEN`; GitHub suppresses downstream push workflows for that merge.
+
 ## [0.40.2] - 2026-09-15
 
 Automated weekly release — batches everything merged since `v0.40.1`.

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: docguard-cli
-Version: 0.40.2
+Version: 0.40.4
 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.2 → docguard_cli-0.40.4}/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,8 +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;
-its repository-token provenance proof remains the only open R8 evidence 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.2 → docguard_cli-0.40.4}/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)
@@ -62,18 +62,37 @@ Before the branch is pushed, the trusted scheduler validates the base repository
 bot author, branch/title/version agreement, next-version increment, synchronized
 package surfaces, and changed-file allowlist. It then arms GitHub's native squash
 auto-merge. Native auto-merge remains blocked by the four required checks, binds
-eligibility to the current PR head, and resets when that head changes. The merged
-`package.json` push starts the idempotent release workflow. If publication is
-interrupted, the next schedule sees the current package version without a tag and
-retries publication before considering another bump. An orphaned release branch
-fails closed; an existing open release PR is reused and has auto-merge re-armed.
+eligibility to the current PR head, and resets when that head changes. The
+scheduler waits up to ten minutes for the merge and then dispatches the
+idempotent release workflow. An hourly tag-driven release sweep covers approvals
+that happen after this bounded wait; tagged versions exit after the small detect
+job. If publication is interrupted, either the hourly sweep or the next release
+schedule sees the current package version without a tag and retries publication
+before considering another bump. An orphaned release branch fails closed; an
+existing open release PR is reused and has auto-merge re-armed.
 
 Do not use a post-approval `workflow_run` listener as the release continuation.
 The approval-required completion is the event that listener observes; approving
 the held run executes its jobs without producing a second completion event for
 the listener. Release PR #380 demonstrated this boundary while publishing
-v0.40.1. Repository native auto-merge avoids polling and another credential while
-leaving the required checks as the merge authority.
+v0.40.1. Release PR #383 then proved repository-token native auto-merge, while
+also proving that its resulting push is recursion-suppressed and cannot be the
+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
 

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/extensions/spec-kit-docguard/extension.yml

@@ -3,7 +3,7 @@ schema_version: "1.0"
 extension:
   id: "docguard"
   name: "DocGuard — CDD Enforcement"
-  version: "0.40.2"
+  version: "0.40.4"
   description: "Canonical-Driven Development enforcement as a true spec-kit extension. LLM-first design with automated validators, 5 AI behavior skills, spec-kit skill chaining, and workflow hooks. One pinned runtime dependency (@babel/parser); pure Node.js otherwise."
   author: "Ricardo Accioly"
   repository: "https://github.com/raccioly/docguard"

{docguard_cli-0.40.2 → docguard_cli-0.40.4}/extensions/spec-kit-docguard/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.2
+  version: 0.40.4
   source: extensions/spec-kit-docguard/skills/docguard-fix
 ---
-<!-- docguard:version: 0.40.2 -->
+<!-- docguard:version: 0.40.4 -->
 
 # DocGuard Fix Skill
 

{docguard_cli-0.40.2/.agent → docguard_cli-0.40.4/extensions/spec-kit-docguard}/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.2
+  version: 0.40.4
   source: extensions/spec-kit-docguard/skills/docguard-guard
 ---
-<!-- docguard:version: 0.40.2 -->
+<!-- docguard:version: 0.40.4 -->
 
 # DocGuard Guard Skill
 

{docguard_cli-0.40.2/.agent → docguard_cli-0.40.4/extensions/spec-kit-docguard}/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.2
+  version: 0.40.4
   source: extensions/spec-kit-docguard/skills/docguard-review
 ---
-<!-- docguard:version: 0.40.2 -->
+<!-- docguard:version: 0.40.4 -->
 
 # DocGuard Review Skill