[Extension]: Update DocGuard — CDD Enforcement (v0.41.6)

[raccioly]

Extension ID

docguard

Extension Name

DocGuard — CDD Enforcement

Version

0.41.6

Description

Documentation integrity for AI-assisted repositories: lifecycle registry, drift validation, traceability, safe archival, SARIF/JUnit, MCP, GitHub Actions, and Spec Kit hooks.

Author

raccioly

Repository URL

https://github.com/raccioly/docguard

Download URL

https://github.com/raccioly/docguard/releases/download/v0.41.6/spec-kit-docguard-v0.41.6.zip

License

MIT

Homepage (optional)

https://www.npmjs.com/package/docguard-cli

Documentation URL (optional)

https://github.com/raccioly/docguard/blob/main/extensions/spec-kit-docguard/README.md

Changelog URL (optional)

https://github.com/raccioly/docguard/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.1.0

Required Tools (optional)

• node (>=18.0.0) - required
• npx - required
• specify - optional (auto-initializes the SDD workflow during docguard init)

Number of Commands

12

Number of Hooks (optional)

5

Tags

documentation, validation, traceability, ai-agents, spec-kit

Key Features

• Configurable quality gate with severity triage and a remediation plan
• AI-driven documentation repair with codebase research and validation loops
• Cross-document semantic consistency analysis (read-only review)
• CDD maturity score with an ROI-based improvement roadmap
• Reverse-engineers canonical docs from an existing codebase
• spec-kit workflow hooks (before_specify, after_implement, after_converge, before_tasks, after_tasks)

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Release verification: Record the platforms and results actually tested before submission.

Install:

specify extension add docguard --from https://github.com/raccioly/docguard/releases/download/v0.41.6/spec-kit-docguard-v0.41.6.zip

Scenarios to verify for this release:

1. Extension installs from the release ZIP without manifest validation errors.
2. All 12 declared speckit.docguard.* commands resolve and run.
3. All 5 declared workflow hooks register against spec-kit's lifecycle.

Example Usage

# Install the extension
specify extension add docguard --from https://github.com/raccioly/docguard/releases/download/v0.41.6/spec-kit-docguard-v0.41.6.zip

# Run the documentation quality gate
/speckit.docguard.guard

Proposed Catalog Entry

{
  "docguard": {
    "name": "DocGuard \u2014 CDD Enforcement",
    "id": "docguard",
    "description": "Documentation integrity for AI-assisted repositories: lifecycle registry, drift validation, traceability, safe archival, SARIF/JUnit, MCP, GitHub Actions, and Spec Kit hooks.",
    "author": "raccioly",
    "version": "0.41.6",
    "download_url": "https://github.com/raccioly/docguard/releases/download/v0.41.6/spec-kit-docguard-v0.41.6.zip",
    "repository": "https://github.com/raccioly/docguard",
    "homepage": "https://www.npmjs.com/package/docguard-cli",
    "documentation": "https://github.com/raccioly/docguard/blob/main/extensions/spec-kit-docguard/README.md",
    "changelog": "https://github.com/raccioly/docguard/blob/main/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.1.0",
      "tools": [
        {
          "name": "node",
          "version": ">=18.0.0",
          "required": true
        }
      ]
    },
    "provides": {
      "commands": 12,
      "hooks": 5
    },
    "tags": [
      "documentation",
      "validation",
      "traceability",
      "ai-agents",
      "spec-kit"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0
  }
}

Additional Context

This is an update to an existing catalog entry (docguard) for a new release — please bump the version and download URL on the current entry rather than adding a duplicate.

Release notes (v0.41.6):

Automated weekly release — batches everything merged since v0.41.3.

Changed

• fix: correct the validator-surface claim and document DOCGUARD_API_KEY (Feature Request: specify upgrade command #408)
• fix: harden adoption precision boundaries (Update for better maintainability #406)

Fixed

• Document DOCGUARD_API_KEY in the canonical environment doc. ENVIRONMENT.md
  claimed DocGuard uses "no API keys" and needs no environment variables, which
  contradicted SECURITY.md and the HTTP MCP server, where the variable is
  required to bind a non-loopback host. Core CLI commands still need no credential.
• Enforce the published validator count in npm test. Canonical-Sync and
  Metrics-Consistency already detect a stale "N validators" claim, but they emit
  warnings and the CI self-scan deliberately tolerates guard's warnings-only exit,
  so a wrong count could reach main with every check green. The count is now
  asserted against the shipped cli/validators/*.mjs modules, and README explains
  why guard prints 30 result rows for 29 validators.
• Count DocGuard validator claims from one shared source of truth: the
  validator modules shipped in the installed package. A consumer's intentionally
  disabled validators and extra guard checks cannot create a false MET001 or
  CSY003 finding, or an unsafe count rewrite.
• Keep instruction-pointer basename resolution out of Git-ignored directories
  and nested Git checkouts, including linked worktree copies.
• Keep planned lifecycle registries that are new, removed from the Git index,
  or modified pending commit non-authoritative for TRC004 while explaining how
  to restore or commit the registry and current spec artifacts; the remediation
  no longer suggests adding an artificial @req marker.

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Pull request created: #4608

Generated by Add Community Extension from Issue Submission · 100.5 AIC · ⌖ 33.2 AIC · ⊞ 29.5K

[github-actions]

Extension submission validation failed

The repository, manifest, README, LICENSE, version, repository ownership, download URL pinning, and GitHub release checks passed for docguard v0.41.4. The submission cannot proceed because the required issue-form checklists are incomplete:

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Please complete and check every required box, then submit a new or updated issue so the validation can be rerun.

Generated by 🧩 Add Community Extension from Issue Submission for #4590 · copilot · gpt52codex · 1.88 AIC · ⌖ 6.75 AIC · ⊞ 26.1K · ◷