com.wallstop-studios.dxmessaging 2.1.5 → 2.1.7

package/.github/workflows/prettier-autofix.yml

@@ -2,7 +2,31 @@ name: Prettier Auto Fix
 
 on:
   pull_request:
+    paths:
+      - "**/*.md"
+      - "**/*.json"
+      - "**/*.asmdef"
+      - "**/*.yml"
+      - "**/*.yaml"
+      - ".github/workflows/**"
+      - ".prettierrc*"
+      - ".markdownlint*"
+      - "package.json"
+      - "package-lock.json"
+      - "scripts/check-eol.ps1"
   pull_request_target:
+    paths:
+      - "**/*.md"
+      - "**/*.json"
+      - "**/*.asmdef"
+      - "**/*.yml"
+      - "**/*.yaml"
+      - ".github/workflows/**"
+      - ".prettierrc*"
+      - ".markdownlint*"
+      - "package.json"
+      - "package-lock.json"
+      - "scripts/check-eol.ps1"
   workflow_dispatch:
 
 concurrency:
@@ -28,8 +52,8 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: '20'
-          cache: 'npm'
+          node-version: "20"
+          cache: "npm"
           cache-dependency-path: package.json
 
       - name: Install dependencies
@@ -53,23 +77,40 @@ jobs:
 
       - name: Renormalize line endings
         if: ${{ github.event.pull_request.user.login == 'dependabot[bot]' }}
-        run: git add --renormalize -- '*.md' '**/*.md' '*.markdown' '**/*.markdown' '*.json' '**/*.json' '*.asmdef' '**/*.asmdef' '*.asmref' '**/*.asmref' '*.yml' '**/*.yml' '*.yaml' '**/*.yaml'
+        shell: bash
+        run: |
+          # Renormalize each extension separately to avoid "pathspec did not match" failures
+          # when certain file types don't exist or aren't accessible in this checkout context
+          # yaml excluded: dotfiles (.pre-commit-config.yaml) match git ls-files but not git add globs
+          for ext in md json asmdef yml; do
+            if git ls-files "*.$ext" "**/*.$ext" | grep -q .; then
+              git add --renormalize -- "*.$ext" "**/*.$ext"
+            fi
+          done
 
       - name: Commit formatting changes to PR branch (Dependabot only)
         if: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository && github.event.pull_request.user.login == 'dependabot[bot]' }}
+        id: auto-commit
         uses: stefanzweifel/git-auto-commit-action@v7
         with:
           commit_message: "chore(format): apply Prettier/markdownlint fixes"
           branch: ${{ github.head_ref }}
           add_options: --renormalize
+          # NOTE: yaml excluded - all .yaml files are dotfiles, which git add patterns don't match
           file_pattern: |
             **/*.md
-            **/*.markdown
             **/*.json
             **/*.asmdef
-            **/*.asmref
             **/*.yml
-            **/*.yaml
+
+      - name: Refresh checkout after auto-commit
+        if: ${{ steps.auto-commit.outputs.changes_detected == 'true' }}
+        env:
+          HEAD_REF: ${{ github.head_ref }}
+        run: |
+          # Fetch the newly pushed commit and checkout to get normalized line endings in working tree
+          git fetch origin "$HEAD_REF"
+          git checkout -f FETCH_HEAD
 
       - name: Prettier check (Markdown)
         run: npm run format:md:check
@@ -104,8 +145,8 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: '20'
-          cache: 'npm'
+          node-version: "20"
+          cache: "npm"
           cache-dependency-path: package.json
 
       - name: Install dependencies
@@ -126,7 +167,16 @@ jobs:
         run: npx --yes markdownlint-cli2@0.20.0 "**/*.md" "**/*.markdown" --fix
 
       - name: Renormalize line endings
-        run: git add --renormalize -- '*.md' '**/*.md' '*.markdown' '**/*.markdown' '*.json' '**/*.json' '*.asmdef' '**/*.asmdef' '*.asmref' '**/*.asmref' '*.yml' '**/*.yml' '*.yaml' '**/*.yaml'
+        shell: bash
+        run: |
+          # Renormalize each extension separately to avoid "pathspec did not match" failures
+          # when certain file types don't exist or aren't accessible in this checkout context
+          # yaml excluded: dotfiles (.pre-commit-config.yaml) match git ls-files but not git add globs
+          for ext in md json asmdef yml; do
+            if git ls-files "*.$ext" "**/*.$ext" | grep -q .; then
+              git add --renormalize -- "*.$ext" "**/*.$ext"
+            fi
+          done
 
       - name: Detect changes
         id: changes
@@ -151,8 +201,14 @@ jobs:
           git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
           git checkout -B "$BRANCH"
           # Stage only files we format; avoid workflows to prevent permission issues
-          # Use --renormalize to ensure LF line endings in git index per .gitattributes
-          git add --renormalize -- '*.md' '**/*.md' '*.markdown' '**/*.markdown' '*.json' '**/*.json' '*.asmdef' '**/*.asmdef' '*.asmref' '**/*.asmref' '*.yml' '**/*.yml' '*.yaml' '**/*.yaml'
+          # Use --renormalize to ensure line endings in git index per .gitattributes
+          # Renormalize each extension separately to avoid "pathspec did not match" failures
+          # yaml excluded: dotfiles (.pre-commit-config.yaml) match git ls-files but not git add globs
+          for ext in md json asmdef yml; do
+            if git ls-files "*.$ext" "**/*.$ext" | grep -q .; then
+              git add --renormalize -- "*.$ext" "**/*.$ext"
+            fi
+          done
           git commit -m "chore(format): apply Prettier/markdownlint fixes for PR #${{ github.event.pull_request.number }}"
           git remote add upstream "https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}.git"
           git fetch upstream

package/.github/workflows/release-drafter.yml

@@ -21,7 +21,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
 
       - name: Extract version from package.json
         id: version
@@ -85,7 +85,7 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Update release body with changelog
-        uses: actions/github-script@v7
+        uses: actions/github-script@v8
         env:
           RELEASE_ID: ${{ steps.release_drafter.outputs.id }}
           VERSION: ${{ steps.version.outputs.version }}

package/.github/workflows/sync-wiki.yml

@@ -27,7 +27,7 @@ jobs:
       should-deploy: ${{ steps.check.outputs.should-deploy }}
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           fetch-depth: 2
 
@@ -80,7 +80,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout main repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           path: main
 
@@ -89,7 +89,7 @@ jobs:
           git clone "https://x-access-token:${{ github.token }}@github.com/${{ github.repository }}.wiki.git" wiki
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: '20'
 

package/.github/workflows/yaml-format-lint.yml

@@ -2,19 +2,45 @@ name: YAML Format + Lint
 
 on:
   pull_request:
+    paths:
+      - "**/*.yml"
+      - "**/*.yaml"
+      - ".github/workflows/**"
+      - ".yamllint.yaml"
+      - ".prettierrc*"
+      - "package.json"
+      - "package-lock.json"
   push:
     branches:
       - main
       - master
+    paths:
+      - "**/*.yml"
+      - "**/*.yaml"
+      - ".github/workflows/**"
+      - ".yamllint.yaml"
+      - ".prettierrc*"
+      - "package.json"
+      - "package-lock.json"
   workflow_dispatch:
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
 jobs:
   yaml-checks:
     name: Prettier and yamllint
     runs-on: ubuntu-latest
+    timeout-minutes: 5
     steps:
       - name: Checkout
         uses: actions/checkout@v6
+        with:
+          persist-credentials: false
 
       - name: Setup Node
         uses: actions/setup-node@v6

package/.llm/context.md

@@ -14,7 +14,7 @@
 - Format: `dotnet tool restore` then `dotnet tool run csharpier format`.
 - Build generators: `dotnet build SourceGenerators/WallstopStudios.DxMessaging.SourceGenerators/WallstopStudios.DxMessaging.SourceGenerators.csproj`.
 - Unity tests: open a Unity 2021.3+ project that references this package, then Window > Test Runner > PlayMode. CLI example: `Unity -batchmode -nographics -quit -projectPath <your_project> -runTests -testPlatform PlayMode -testResults ./TestResults.xml`.
-- Actionlint: Runs in CI on PRs/pushes to validate GitHub Actions workflows. Available as a pre-push hook (requires `actionlint` installed locally).
+- Actionlint: Runs in CI on PRs/pushes to validate GitHub Actions workflows. Available as a pre-push hook (requires `actionlint` installed locally). See the [Workflow Consistency skill](./skills/github-actions/workflow-consistency.md) for required workflow structure.
 - Spellcheck: Runs in CI on PRs/pushes via `cspell` to check spelling in Markdown, C#, JSON, YAML, and script files. Dictionary is maintained in [.cspell.json](../.cspell.json). Available as a pre-push hook via `npx cspell`.
 
 ## Coding Style & Naming Conventions
@@ -78,11 +78,20 @@ $extensions = @('.cs', '.csproj', '.sln', ...)
 const crlfExts = new Set(['.cs', '.csproj', '.sln', ...]);
 ```
 
+### SYNC Note Best Practices
+
+- **Always bidirectional**: When code A has a SYNC note referencing code B, code B must also have a SYNC note referencing code A. One-way SYNC notes are easily missed during updates.
+- **Never use line numbers**: Reference function names, class names, or named anchors instead. Line numbers become stale as code evolves.
+- **Use descriptive identifiers**: `SYNC: Keep logic in sync with validate-skills.js validateSkill() tags validation` is better than `SYNC: Keep in sync with validate-skills.js lines 224-250`.
+- **Verify references exist**: Before adding a SYNC note, confirm the referenced function, variable, or block actually exists with the exact name.
+
 ### Shell Pattern Matching
 
 - Use `grep -F` for literal string matching (paths, filenames with special characters like `.`).
 - Use `grep -E` only when regex features are explicitly needed.
 - Remember that `.` in a regex matches any character, not just a literal dot.
+- **Count escape sequences carefully**: Each `\.` matches exactly one literal dot. The pattern `^\.\.$` matches the literal string `..` (two consecutive dots), not "any string with dots at each end."
+- **Dotfile matching**: To match dotfiles (files starting with `.`), use `^\.` which is sufficient for `git ls-files` output since `..` directory entries are never listed.
 - Always quote variable expansions in patterns: `grep -F "$PATH_VAR/"` not `grep -F $PATH_VAR/`.
 - **`grep` exit codes**: `grep` returns exit code 1 when no matches are found, which fails CI pipelines. Use `|| true`, `|| echo "0"`, or pipe to `wc -l` instead of `grep -c` when zero matches is acceptable.
 
@@ -99,10 +108,14 @@ This project uses CRLF for most files but LF for shell scripts (`.sh`, `.bash`,
 - **Prefer `fix-eol.js` for working tree fixes**: Run `node scripts/fix-eol.js` to directly fix line endings in your working tree. This is the recommended approach after cloning or when files have incorrect endings.
 - **`git add --renormalize` only updates the index**: This command updates the git staging area based on `.gitattributes` but does **not** modify working tree files. Use it only when you need to re-stage files with updated normalization rules.
 - **`git add --renormalize` must target specific paths**: Never use `git add --renormalize .` as it stages all files. Always specify exact patterns like `git add --renormalize -- '*.md' '**/*.md'`.
+- **Use per-extension loops for `git add --renormalize`**: Multi-pattern renormalize commands fail with exit code 128 if any pattern matches no files. Use a loop to process each extension separately with existence checks. Example: `for ext in md json yml; do if git ls-files "*.$ext" "**/*.$ext" | grep -q .; then git add --renormalize -- "*.$ext" "**/*.$ext"; fi; done`.
+- **Dotfiles do not match glob patterns in `git add`**: The command `git ls-files "*.yaml"` matches dotfiles like `.pre-commit-config.yaml`, but `git add --renormalize -- "*.yaml"` does NOT match dotfiles. This causes the existence check to pass but the renormalize to fail. Exclude `yaml` from extension loops since the only `.yaml` files are typically dotfiles; use `yml` instead.
+- **Generalized rule for dotfile-only extensions**: Exclude any extension from `git add --renormalize` loops when ALL tracked files of that extension are dotfiles (files whose names start with `.`). To check: run `git ls-files "*.$ext" "**/*.$ext"` and verify whether any results are non-dotfiles. If all matches are dotfiles, exclude that extension.
 - **Error messages must be specific**: Indicate which policy was violated (e.g., "Expected LF for shell scripts" vs "Expected CRLF per project policy").
 - **git-auto-commit-action `file_pattern`**: This only limits what gets newly added; previously staged files still get committed. Ensure preceding `git add` commands target the same file set.
+- **`file_pattern` does not match dotfiles**: Like `git add`, the `file_pattern` option in `git-auto-commit-action` uses glob patterns that do not match dotfiles. Exclude patterns like `**/*.yaml` from `file_pattern` when all `.yaml` files are dotfiles (e.g., `.pre-commit-config.yaml`). This follows the same rule as excluding `yaml` from `git add --renormalize` loops.
 
-See the [Git Workflow Robustness skill](./skills/testing/git-workflow-robustness.md) for detailed patterns.
+See the [Git Workflow Robustness skill](./skills/testing/git-workflow-robustness.md) and the [Git Renormalize Patterns skill](./skills/github-actions/git-renormalize-patterns.md) for detailed patterns.
 
 ### Forbidden Commands
 
@@ -116,6 +129,83 @@ See the [Git Workflow Robustness skill](./skills/testing/git-workflow-robustness
 - Prefer `const` over `let`; use `let` only when reassignment is necessary.
 - When adding validation constants (e.g., `VALID_X`), ensure corresponding validation logic uses them.
 
+#### Presence vs Value Validation
+
+When validating input, clearly separate "presence" checks (is the value defined?) from "value" checks (is the defined value valid?). This two-phase approach produces clearer error messages and more maintainable code.
+
+##### Checking for missing values (undefined/null)
+
+```javascript
+// CORRECT: Explicit null/undefined check
+if (frontmatter[field] === undefined || frontmatter[field] === null) {
+  errors.push(`Required field '${field}' is missing`);
+}
+
+// ALSO CORRECT: Loose equality shorthand (null == undefined is true)
+if (frontmatter[field] == null) {
+  errors.push(`Required field '${field}' is missing`);
+}
+
+// WRONG: Falsy check conflates missing with empty/invalid
+if (!frontmatter[field]) {
+  errors.push(`Required field '${field}' is missing`); // Misleading: also triggers for ""
+}
+```
+
+###### Two-phase validation pattern
+
+```javascript
+// Phase 1: Check presence
+if (value === undefined || value === null) {
+  errors.push("Value is missing");
+} else if (value === "") {
+  // Phase 2: Check value validity (only if present)
+  errors.push("Value is empty");
+} else if (!isValidFormat(value)) {
+  errors.push("Value has invalid format");
+}
+```
+
+###### When to use falsy checks (`!x`)
+
+- Only when you explicitly want to catch ALL falsy values: `undefined`, `null`, `0`, `""`, `false`, `NaN`
+- Common legitimate uses: `if (!array.length)` to check empty arrays, `if (!str.trim())` to check whitespace-only strings
+
+###### Common pitfalls
+
+- **Empty array is truthy**: `[]` is truthy, so `![]` is `false`. Use `!array.length` instead.
+- **Zero is falsy**: `0` is falsy, so `!count` fails when count is legitimately zero.
+- **Empty string vs missing**: `!value` treats `""` the same as `undefined`, but they often need different error messages.
+
+###### Guard clause for enum validation
+
+When checking if a value is valid according to an enum/allowlist, guard against missing and empty values first. This prevents spurious "invalid value" errors for empty strings:
+
+```javascript
+// CORRECT: Guard against missing and empty before enum check
+if (value != null && value !== "" && !VALID_VALUES.includes(value)) {
+  errors.push(`Invalid ${fieldName}: '${value}'`);
+}
+
+// WRONG: Missing guard allows empty string to be flagged as "invalid"
+if (!VALID_VALUES.includes(value)) {
+  errors.push(`Invalid ${fieldName}: '${value}'`); // Reports "" as "Invalid: ''"
+}
+```
+
+###### Type coercion for YAML values
+
+YAML parsers may return non-string types (e.g., `1.0.0` becomes number `1`). Use `String()` after presence checks:
+
+```javascript
+if (value != null && value !== "") {
+  const strValue = String(value);
+  if (!strValue.match(/^\d+\.\d+\.\d+$/)) {
+    errors.push(`Invalid format: '${strValue}'`);
+  }
+}
+```
+
 ### Jest Test Style
 
 For JavaScript tests using Jest:
@@ -123,6 +213,9 @@ For JavaScript tests using Jest:
 - **Use `test()` not `it()`**: All tests must use `test()` for consistency with existing tests.
 - **Descriptive names**: Test descriptions should clearly state what is being tested.
 - **Group with `describe()`**: Use `describe()` blocks to group related tests logically.
+- **Accurate categorization**: `describe()` block names must accurately reflect the tests they contain. Do not group "undefined/null" checks under "falsy" if falsy wrong-type values (empty string, 0, false) are tested separately.
+- **Test accuracy**: Test names, descriptions, and comments must be factually correct. Never include statements that contradict how JavaScript actually behaves (e.g., claiming "empty array is falsy" when it is truthy).
+- **Message content tests**: When code produces user-facing messages, add tests that verify message content matches actual UI/output terminology.
 
 ```javascript
 // CORRECT
@@ -197,6 +290,17 @@ This project maintains a strict **zero-flaky test policy**. Every test failure i
 
 See the [Test Failure Investigation skill](./skills/testing/test-failure-investigation.md) for detailed investigation patterns and procedures.
 
+### Test Production Code Directly
+
+Tests must import and exercise actual production code, never re-implement production logic locally. Re-implementing validation or business logic in tests creates a false sense of security - tests can pass while production code regresses.
+
+- **Import production functions**: Tests should import and call the actual production functions, not local copies.
+- **Export testable helpers**: Structure production code with exported helper functions that tests can verify.
+- **Avoid duplication**: If test files contain utility functions that mirror production logic, refactor to import instead.
+- **Use SYNC notes for unavoidable duplication**: When parallel implementations are necessary (e.g., PowerShell scripts tested via JavaScript), use bidirectional SYNC notes referencing function names.
+
+See the [Test Production Code skill](./skills/testing/test-production-code.md) for patterns and examples.
+
 ## Documentation Guidelines
 
 After any new feature or bug fix, documentation must be updated:
@@ -206,20 +310,24 @@ After any new feature or bug fix, documentation must be updated:
 - **XML docs**: Update `<summary>`, `<param>`, `<returns>`, and `<remarks>` for public APIs.
 - **Code samples**: Ensure examples are correct, compilable, and tested.
 - **README**: Update [the README](../README.md) for significant features or breaking changes.
+- **MkDocs navigation**: When adding new pages to `docs/`, always add corresponding entries to `mkdocs.yml` nav section.
 
 When documenting new behavior, note the version it was introduced (e.g., "Added in v1.2.0").
 
-See the [Documentation Updates skill](./skills/documentation/documentation-updates.md) and [Changelog Management skill](./skills/documentation/changelog-management.md) for detailed guidance.
+See the [Documentation Updates skill](./skills/documentation/documentation-updates.md), [Changelog Management skill](./skills/documentation/changelog-management.md), and [MkDocs Navigation skill](./skills/documentation/mkdocs-navigation.md) for detailed guidance.
 
 ### Markdown Formatting Conventions
 
 - **Ordered lists**: Use lazy numbering (`1.`, `1.`, `1.`) not sequential (`1.`, `2.`, `3.`). This matches Prettier behavior and markdownlint MD029 configuration.
 - **Fenced code blocks**: Use triple backticks (```), not indented blocks.
+- **Nested fences**: When showing code blocks inside code blocks (e.g., documenting markdown), the outer fence must have MORE backticks than inner fences. Use ``for outer when inner uses` ```.
 - **Line endings**: CRLF, no UTF-8 BOM (enforced by pre-commit hooks).
 - **Headings**: Use ATX-style headings (`#`, `##`, `###`) not underlined style.
 - **Line length**: Not enforced. Write naturally; let lines wrap as needed.
 - **Inline code spacing**: Always include a space before and after inline code when adjacent to text. Write ``the `code` here`` not ``the`code`here``. This improves readability and matches CommonMark best practices.
 
+See the [Markdown Compatibility skill](./skills/documentation/markdown-compatibility.md) for MkDocs-specific syntax to avoid.
+
 ## Changelog Guidelines
 
 Every user-facing change must be added to [the changelog](../CHANGELOG.md):
@@ -229,6 +337,8 @@ Every user-facing change must be added to [the changelog](../CHANGELOG.md):
 - Include proper version headers with dates (e.g., `## [1.2.0] - 2026-01-22`).
 - Link issues and PRs in entries (e.g., "Fixed registration bug (#123)").
 - Write entries from the user's perspective, focusing on impact.
+- Entries must describe **user-visible** changes only; do not document internal tooling, AI agent guidance, or developer-only changes like `.llm/` skill files.
+- Use accurate scope: if only some files/assemblies were changed, name them specifically rather than implying all were changed.
 
 See the [Changelog Management skill](./skills/documentation/changelog-management.md) for detailed guidance.
 

package/.llm/skills/documentation/changelog-management.md

@@ -171,6 +171,44 @@ MAJOR.MINOR.PATCH
 - Link issues or PRs when available
 - Flag breaking changes explicitly with migration guidance
 
+## Anti-Patterns
+
+### Anti-Pattern 1: Internal Tooling or AI Agent Documentation
+
+```markdown
+<!-- WRONG -->
+
+### Added
+
+- MkDocs navigation skill documenting navigation patterns
+```
+
+Changelog entries describe changes that **users experience**, not internal tooling, AI agent guidance, or developer-facing documentation. Skills, context files, and internal process documentation are invisible to package consumers and do not belong in the changelog.
+
+**What to document instead**: Changes to user-facing documentation (API docs, tutorials, README) may warrant changelog entries if they significantly improve the user experience.
+
+### Anti-Pattern 2: Overly Broad Scope
+
+```markdown
+<!-- WRONG -->
+
+### Changed
+
+- Updated test assembly definitions
+```
+
+This entry implies all test assembly definitions were changed, which is rarely accurate. Entries must accurately scope what was actually affected.
+
+```markdown
+<!-- CORRECT -->
+
+### Fixed
+
+- `WallstopStudios.DxMessaging.Tests.Runtime` assembly definition now specifies Editor-only platform to prevent Burst compilation errors during player builds
+```
+
+**Rule**: Be specific about what changed. Name the exact files, assemblies, or components that were modified. Vague entries create confusion about which components were affected and make it harder to trace issues back to specific changes.
+
 ## See Also
 
 - [Changelog Entry Writing](changelog-entry-writing.md)

package/.llm/skills/documentation/documentation-style-guide.md

@@ -131,6 +131,24 @@ MessageRegistrationHandle handle = _messageRegistrationToken.RegisterGameObjectT
 ```
 ````
 
+### Use Correct Brand Capitalization
+
+Technology brands have specific capitalization. Using incorrect forms looks unprofessional:
+
+| Correct       | Incorrect                   |
+| ------------- | --------------------------- |
+| GitHub        | Github, github              |
+| JavaScript    | Javascript, java script     |
+| TypeScript    | Typescript, typescript      |
+| Node.js       | NodeJS, Nodejs, node.js     |
+| npm           | NPM, Npm (always lowercase) |
+| C#            | c#, CSharp                  |
+| .NET          | .Net, dotnet (in prose)     |
+| Unity         | unity (in prose)            |
+| NuGet         | Nuget, nuget                |
+| Visual Studio | VisualStudio                |
+| VS Code       | VSCode, vscode (in prose)   |
+
 ## Anti-Patterns
 
 ### Bad: Placeholder Documentation

package/.llm/skills/documentation/documentation-update-workflow.md

@@ -60,6 +60,7 @@ related:
   - "documentation-xml-docs"
   - "documentation-code-samples"
   - "changelog-management"
+  - "mkdocs-navigation"
 
 status: "stable"
 ---
@@ -133,6 +134,7 @@ Documentation updates needed:
 - [Documentation Updates](documentation-updates.md)
 - [XML Documentation Standards](documentation-xml-docs.md)
 - [Documentation Code Samples](documentation-code-samples.md)
+- [MkDocs Navigation](mkdocs-navigation.md)
 - [Changelog Management](changelog-management.md)
 
 ## References

package/.llm/skills/documentation/documentation-updates.md

@@ -69,6 +69,7 @@ related:
   - "documentation-code-samples"
   - "documentation-style-guide"
   - "documentation-update-workflow"
+  - "mkdocs-navigation"
   - "test-failure-investigation"
 
 status: "stable"
@@ -132,6 +133,7 @@ Outdated documentation misleads users and increases support load.
 - [Code Sample Requirements](documentation-code-samples.md)
 - [Documentation Style Guide](documentation-style-guide.md)
 - [Documentation Update Workflow](documentation-update-workflow.md)
+- [MkDocs Navigation](mkdocs-navigation.md)
 - [Changelog Management](changelog-management.md)
 
 ## References