Pack AI Assistant (PAIA)

Pack AI Assistant 0.2.0

The AI now drives the recipe cards itself, and enchant / repair questions are answered from the game's own data instead of a viewer.

• AI-managed recipe cards. The model calls the recipe-card tool directly, so every card lands right after the numbered method it belongs to (workbench / auto-crafter / material recipes). Mirror recipes (same machine family, e.g. Kinetic Crafter / Mixer) merge into one card with an "also usable on" note. "Used as material" cards pick the ones the answer actually names. A safety net emits catalog cards even when the model forgets.
• Enchant answers grounded in the pack. Which enchants apply is read from the game's registry (not a recipe viewer), so modded items answer correctly even when JEI/EMI pages are silent. Enchant-table questions (能附什么魔 / what can I enchant) are recognized semantically, not by keyword.
• Repair vs upgrade separated. Anvil self-repair recipes are split by JEI category; anvil repair materials come from the actual repair predicate (isValidRepairItem), so answers say what really repairs the item.
• Tooltip-backed obtain hints. When the item's own tooltip states how to get it (e.g. green lore), that shows as a low-confidence hint instead of a flat "unknown" — with sources labelled.
• Maintenance machine cards (optional tier) — upgrade / repair machines (anvil, weapon infusion, etc.) get their own recipe cards when relevant.
• AskTool plugin API (Scope Y) — third-party mods and pack authors can register their own Ask tools through the public api/ package and registration events (validated, rejected loudly if malformed).
• Internals: LLM intent classification hop replaces the online keyword gate; dual-tree (Forge/NeoForge) kept in lockstep; AskTool loop hardening (dedupe fingerprints, no infinite retries on TOOL_MISS).

Covers both lines: Forge 1.19.2 (packai-0.2.0+mc1.19.2-forge.jar) and NeoForge 1.21.1 (packai-0.2.0+mc1.21.1-neoforge.jar).