check-refs

# check-refs ## When to use Use this skill when: - A skill, rule, command, guideline, or context has been renamed or deleted - Linking a newly added artifact from elsewhere in `src/` - Preparing a PR that touches cross-references between agent artifacts - CI's `check-refs` job failed and the broken reference needs to be located Do NOT use when: - Only the body of a single file changed and no names or paths were touched - Checking frontmatter shape or required sections — use `lint-skills` instead - Verifying condensed vs uncondensed pairs — use `bash scripts/condense.sh --check` instead ## Procedure ### 1. Inspect the scope of recent changes Identify whether any artifact was renamed, moved, or removed since the last clean run. Cross-reference checks are relevant only when names or paths shift; pure body edits cannot break references. ### 2. Dispatch via the runtime layer Invoke the skill through the runtime dispatcher so the `execution:` block in this skill's frontmatter governs the call: ```bash ./scripts-run src/scripts/runtime_dispatcher run --skill check-refs ``` The dispatcher resolves the request, the shell handler runs `./scripts-run src/scripts/check_references`, captures stdout/stderr, and returns a typed `ExecutionResult`. ### 3. Verify the result Check the returned `ExecutionResult`: - `exit_code: 0` → all cross-references resolve - `exit_code: 1` → at least one broken reference — read `stdout` for file, line, and the offending ref, then fix the sou...