fix(kyberforge): restore skill-audit's script-failure fallback and E100 diagnostic

The ADR-0020 body trim took `skill-audit` from 2,623 body words to a dispatch
shape, and two things went out with it that were not padding.

The manual structural fallback was one. Its replacement was a single sentence
telling the auditor to report an INFO when `validate.sh` cannot run — so with no
`python3` or no PyYAML, `skill-audit` reported the gap honestly and then audited
nothing structural at all. Every ADR-0020 measurement, the whole-file ceilings,
the name-to-directory match, the `references/` pointer check and the script
hygiene checks silently left the audit. A skill's whole Structure dimension
hanging on one optional interpreter is the same vacuous-pass shape the gate
scripts were just fixed for, one layer up.

The `E100 Runtime error ... does not exist` diagnostic was the other. That exit
code means an explicit relative `--config` was passed to `vale-wrap.sh` while
vale itself was installed and working; without the note, Step 1's fallback reads
exit 2 as "vale unavailable" and downgrades the description, body-discipline and
patterns dimensions to full LLM judgment for a config error it could have fixed.
That misreading is already recorded in CONTEXT.md as the reason both audit skills
stopped passing `--config` at all.

Both are restored in `references/validation-scripts.md`, loaded only when a Step 1
script fails — so the body pays nothing for them on a clean run, which is what the
dispatch pattern is for. The file also carries the by-hand boundary-target
procedure and the three ways to misread the result, including that
`INFO ... DID NOT RUN` is not a pass.

`references/file-structure.md` gains the one sanctioned spelling for a cross-skill
reference. The possessive form (``skill-audit's references/validation-scripts.md``)
is the only spelling both rules accept: a full repo path is what that section
already forbids, and a bare `references/<file>.md` is now a hard ERROR from the
ADR-0020 pointer check, which requires the file to exist in the skill's *own*
directory. Without the rule the two constraints look mutually exclusive.

Refs: ADR-0020

plugins/kyberforge/.apm/skills/skill-audit/references/file-structure.md

@@ -28,6 +28,14 @@ resolving there. Flag any `../`, `../../`, or absolute repo path (`plugins/<plug
 and its APM-native equivalent `.apm/skills/<other>/`) appearing in `SKILL.md`, `scripts/`,
 `references/` or `assets/`.
 
+**Referring to another skill's file.** There is one sanctioned spelling, and it is possessive:
+`skill-audit's references/validation-scripts.md`. Write the skill by name and let the reader
+resolve it — do not spell the repo path. The full path is the thing this section forbids, and
+`references/validation-scripts.md` on its own is a hard ERROR from the ADR-0020 gate, which
+requires an unqualified `references/` pointer to exist in the skill's OWN directory. The
+possessive form is the only spelling both rules accept; the gate recognises it and skips the
+on-disk check. Flag any other spelling of a cross-skill reference.
+
 Two directories are exempt, and the exemptions are structural rather than discretionary:
 
 - **`references/sources.md`.** Its `Research doc:` fields are development-time provenance pointers,