Adapt IntentBuilder residue — language-agnostic .intent migration

🤖 Auto-generated by Claude Opus 4.8 (claude-opus-4-8) via Claude Code — NOT human-reviewed. Verify before acting.

Flagging (not editing — these are your maintained skills) from the fleet-wide language-agnostic intent migration sweep: ovos-skill-easter-eggs's __init__.py still registers intents via Adapt IntentBuilder (17 occurrences). The campaign is moving every skill to file-intents only — @intent_handler("X.intent"), zero IntentBuilder/adapt/_kw in code (skill code language-agnostic; locales are pure data).

Method (staged, en-first): strip the Adapt registrations → each intent becomes a .intent template; .voc STAYS where it's consumed (voc_match/kw_match, inline <name> refs in templates, or {slot}+.entity) — delete only genuinely-orphaned Adapt-keyword .voc; then per-language .intent PRs restore non-en coverage. Watch for coverage loss: Adapt matched loosely (keywords, any order); .intent matches templates — so probe the removed bridge's phrasings and recover any gap in .intent (reuse native .voc via <name>, needs ≥2 entries). Pin ovos-padatious>=2.0.17a1 (pure Apache, no libfann/fann2).

Landed reference: ovos-skill-mark1-ctrl#45 (14 IntentBuilder intents → file-intents, same pattern). Happy to hand off the exact diff/pattern if useful — leaving the migration to you since it's your repo.

Start in init.py and inventory the 17 Adapt IntentBuilder registrations, then compare the landed ovos-skill-mark1-ctrl#45 migration pattern. Convert the registrations to file-intents, preserve only consumed .voc files, and probe the removed bridge phrasings for template coverage; done means no IntentBuilder, adapt, or _kw remains in skill code.