Companion to the skill/rule rollout completed on 2026-04-24 (see
TMHSDigital/Developer-Tools-Directory#1).

Adds `<!-- standards-version: 1.6.3 -->` as the first line of
AGENTS.md and/or CLAUDE.md in this repo. HTML comment format used
instead of YAML frontmatter to preserve the pure-markdown convention
of these prose guidance documents and avoid risk with GitHub Pages
generators.

Enables the agent-file drift checker (Phase 2) to verify project-level
guidance files reference the current meta-repo standards version.

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com

GitHub Actions paths-ignore globs are root-only - the existing *.md
filter does not match subdirectory files like skills/foo/SKILL.md
or rules/bar.mdc. As a result, agent file changes were triggering
release.yml on push to main, even though those files are
documentation, not features.

Adds explicit paths-ignore entries for skills/**, rules/**/*.mdc,
AGENTS.md, and CLAUDE.md so agent-file-only commits do not trigger
releases.

Discovered during Phase 2 Session D D-0 audit. Prerequisite for the
v1.7.x signal rollout (Session D main batch).

See TMHSDigital/Developer-Tools-Directory#1 Phase 2 Session D.

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
Made-with: Cursor

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com

…low (#4)

Bumps standards-version signals across all skills, rules, and agent
context files from 1.6.3 to 1.7.0 to align with the meta-repo's
v1.7 standards generation.

Adds .github/workflows/drift-check.yml as a standalone workflow that
runs the meta-repo's drift checker against this repo's checkout on
every PR and push to main. Standalone rather than integrated into
existing CI workflows, matching the pattern established in CFX
canary (TMHSDigital/CFX-Developer-Tools#4).

Phase 2 Session D rollout. Parallel batch following the validated
canary pattern.

See TMHSDigital/Developer-Tools-Directory#1 Phase 2 Session D.

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
Made-with: Cursor

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com

…lock scalars in two workflows (#6)

Fixes #5. Same root cause class as the CFX YAML quoting cluster
(TMHSDigital/CFX-Developer-Tools#5, #6, #7, fixed in CFX PR #8).

`validate.yml` and `update-unity-api.yml` had two distinct flavors of
the same bug, both producing YAML scanner errors that prevented all
jobs from running:

1. Three `python3 -c "..."` blocks in `validate-plugin-manifest`
   (lines 100-130 of validate.yml). The unquoted multiline form is
   parsed as a plain scalar and the embedded colons (`for n in data:`,
   `assert ...:`) terminate the scalar prematurely.

2. Seven `python3 << 'PYEOF'` blocks across both files where the python
   body started at column 0 with no `run: |` block-scalar marker. The
   `run` value is parsed as the single-line plain scalar
   `python3 << 'PYEOF'` and the column-0 python body is then treated as
   top-level YAML tokens, producing
   `ScannerError: while scanning a simple key, could not find expected ':'`.

Both flavors are fixed by wrapping each `run` value in a `run: |`
literal block scalar with the python heredoc body indented to match.
Heredoc delimiter `PYEOF` is preserved across both files for
consistency with the rest of the original file.

Surfaced during ecosystem audit on 2026-04-25
(TMHSDigital/Developer-Tools-Directory#1 close-out, audit report
ecosystem-audit-2026-04-25.md).

Verified locally:
- Both workflow files parse cleanly under PyYAML safe_load with
  newlines preserved in every python script body (10 blocks total).
- Every python validation block runs successfully against the actual
  repo data:
  - 5 MCP data JSONs validated (unity_api_common 59, deprecated_patterns
    17, lifecycle_order 25, shader_properties 6, platform_defines 9).
  - plugin manifest schema (name, version, author, keywords) valid.
  - All 18 skills + 8 rules pass frontmatter checks.
  - All 20 snippets non-empty.
  - All 5 templates have README.md and C# scripts.
  - Counts confirmed: 18 skills, 8 rules, 20 snippets, 5 templates
    match plugin.json and README.md.
- Representative heredocs exercised end-to-end via bash to confirm
  the heredoc-to-python pipe works.

Closes #5.

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com
Made-with: Cursor

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com

Adds the release-doc-sync@v1.0 composite action from the meta-repo
to release.yml. After plugin.json is bumped on auto-release, the
action prepends a stub entry to CHANGELOG.md for the new version.

This repo does not ship CLAUDE.md or ROADMAP.md, so the action's
CLAUDE/ROADMAP edits are no-ops here (the action reports them as
"missing" and exits cleanly).

The existing "Commit version bump" step uses a selective
`git add .cursor-plugin/plugin.json README.md` rather than
`git add -A`, so CHANGELOG.md is added to that list to ensure the
prepended entry actually lands in the release commit. Without this
change the action would run but its sole useful output (the
CHANGELOG prepend) would be silently discarded.

Phase 2c rollout following the Docker smoke test pattern. The action
is verified working at v1.8.2 (pinned via @v1.0 floating tag).

Refs TMHSDigital/Developer-Tools-Directory#5.

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com

Signed-off-by: 154358121+TMHSDigital@users.noreply.github.com

Empty commits are suppressed by release.yml paths-ignore (vacuous match), so this touches a non-ignored path to force a release run that exercises the newly-integrated release-doc-sync@v1.0 action.

Refs TMHSDigital/Developer-Tools-Directory#5.