Repository navigation
test(agents): mode-card skill-reference closure + autoresearch entry-points re-point - #539
aarontrowbridge wants to merge 1 commit into
Conversation
…points re-point (#537)
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
Hygiene triage 2026-08-27: Open since 2026-08-23 — mode-card skill-reference closure test. Related to #537. If still needed, rebase; if superseded by #537 work, close. Tagging @aarontrowbridge. |
|
Closing — 3 weeks stale. The mode-card skill-reference closure system has evolved significantly since (mode surface shipped Sep 7, #862). The test should be re-authored against the current mode-card shape. |
Summary
test/skill_reference_closure.test.ts): every skill-invocation directive in all agent cards must resolve against repo skills plus the committed internal-registry fixture (develop,director-core,implement-issue); registry entries are cross-checked against the armonissima team mount when present (conditional, same pattern as the mode-card parity suite). Non-vacuous guards on both the card side and the registry side.director-core(canonical loop protocol); this skill is the research-mode instantiation carrying what director-core deliberately does not (spec-gate review budget, checkout registry, probe/experiment boundary). Conflict rule: director-core wins; report the conflict, never resolve it by edit.Born from the 2026-08-23 outage: both mode cards invoke
director-corefirst, the server's staging allowlist omitted it, and runtime died withskill director-core unavailable. CI now catches what staging forgets.Closes #537
Verification
npm test— 107 files / 1515 tests, full suite green (run on this branch)npm run typecheck— clean