[unicoderbot]

Summary

Skills and the ffca-layer-auditor agent referenced plugin files (references/…, scripts/…) with bare relative paths. Nothing resolves those to the plugin's own files: Claude Code only expands ${CLAUDE_PLUGIN_ROOT}, and an agent working in a user's repo resolves a relative path against that repo. The references only worked when the model guessed the base from an earlier ${CLAUDE_PLUGIN_ROOT} mention in the same file. In ffca-audit, dart run scripts/validate_layers.dart --all failed outright when run from a user's repo.

This PR prefixes every such path in skills/ and agents/ with ${CLAUDE_PLUGIN_ROOT}/. Downstream tools such as vgv_ai_cli rewrite that placeholder for Codex, Copilot and Antigravity, so they can now resolve these paths too.

Changes

• Prefix bare references/… and scripts/… paths with ${CLAUDE_PLUGIN_ROOT}/ in agents/ffca-layer-auditor.md and the ffca-architecture, ffca-audit, ffca-cross-feature, ffca-feature and ffca-routing skills.
• Add a plugin-paths CI job that greps skills/ and agents/ for a bare references/ or scripts/ path and fails with an error message if one is found, so the problem can't regress.
• Document the new check in the Checks section of AGENTS.md.

The change is path-prefix only, with no change to the wording or the instructions themselves.

Closes #37

[ryzizub]

${CLAUDE_PLUGIN_ROOT} feels like the right convention to me: one variable for skills and agents, and no symlinks. One blocker, though: vgv_ai_cli doesn't handle it in skill or agent content yet, so as written this breaks the Codex, Copilot and Antigravity exports.

• vgv_ai_cli rewrites ${CLAUDE_PLUGIN_ROOT} only in hook commands (claude_plugin_parser.dart). In skill and agent bodies it is left as-is. Only ${CLAUDE_SKILL_DIR} is expanded there (skills_translator.dart).
• It copies only each skill's own directory, so references/ and scripts/ at the plugin root never reach the other harnesses.

Proposal: teach vgv_ai_cli to expand ${CLAUDE_PLUGIN_ROOT} in skill and agent content and install the referenced plugin-root files, then merge this PR. Wingspan could later move from its symlinks to the same convention, so every VGV plugin works the same way.

cc @marcossevilla