SkillRadar v0.3.2 — Registry-first explicit routing

SkillRadar v0.3.2 — Registry-first explicit routing

v0.3.2 fixes a routing-policy regression discovered during a real Codex acceptance test.

What was wrong

The v0.3.1 plugin correctly bundled the safety-gated Registry and could route fully offline, but skill-router/SKILL.md still told Codex to inspect obvious local skills first and allowed it to skip the Registry when local skills already looked suitable.

That meant an explicit $skill-router request could return a plausible local shortlist without proving that SkillRadar's Registry, scoring, or safety evidence had been used.

Fix

• Explicit $skill-router, Top N, recommendation, comparison, ranking, and routing requests are now Registry-first.
• Codex must run the bundled read-only lookup before selecting candidates.
• Installed/local skills are supplemental availability metadata only; they cannot replace the SkillRadar ranking.
• Successful explicit routes must expose source: skillradar-registry, registry.mode, match_score, skillradar_score, security, source, and reason.
• If Registry lookup fails, the skill must say so instead of presenting a local-only shortlist as a successful SkillRadar route.
• Offline acceptance now includes a static policy-contract guard so the local-first bypass cannot be accidentally reintroduced.

Safety boundary

Discovery is still not execution. D/Blocked entries remain excluded from automatic routing, and SkillRadar's internal lookup CLI remains read-only.