Summary

Meta-repo (Developer-Tools-Directory)'s own release.yml retains paths-ignore patterns that exclude content from release triggers, mirroring the bug DTD#47 just fixed across 7 tool repos.

Current state

release.yml push trigger excludes:

• *.md
• docs/**
• standards/**
• LICENSE
• .github/release-drafter.yml

The bugs (same systemic argument as DTD#47)

1. standards/** is excluded. Standards documents are arguably the meta-repo's primary product; edits to them should fire release-doc-sync to keep CLAUDE.md / ROADMAP.md aligned.
2. docs/** is excluded. The catalog site is part of the deliverable.
3. *.md blanket exclusion catches AGENTS.md, CLAUDE.md, ROADMAP.md, README.md, CHANGELOG.md. release-doc-sync cannot reconcile version markers on these.
4. Asymmetric with the tool repos: 7 tool repos now have empty paths-ignore (per DTD#47), but the meta-repo enforces the standard while not following it itself.

Recommendation: same Option A as DTD#47

Remove the paths-ignore block from release.yml's push trigger. Every push starts the workflow; commit message prefix decides whether release fires.

Possible exception: .github/release-drafter.yml. This is config for an external workflow that updates release notes; arguably it should not trigger its own release. Decision in this fix: include it in the removal anyway (consistent with the pattern across tool repos), trust commit message prefix to gate release.

Scope

Single PR on Developer-Tools-Directory. Single-line removal of paths-ignore block. Bump VERSION (PATCH). Closes when merged and meta-repo auto-release fires.

Out of scope

• Tool-repo paths-ignore (DTD#47, closed)
• meta-repo's own scaffold's emitted patterns (DTD#41, closed)