EmakiForge | Blueprint Forging

Added

• Three action-chain actions: emakiforge_refresh_held, emakiforge_refresh_player, emakiforge_refresh_all.
• /emakiforge debug stats (alias status) reporting generation, files, parsed, skipped, registered, duplicates, issues, warnings, elapsed time, and source state.
• Localizable config precheck and recipe-load diagnostics (directory creation failure, blank id, duplicate id, load failure) plus localizable player-facing runtime state messages (reloading, no recipes, load failed, capability missing, index not ready, closed, session expired).
• Optional soft dependency on EmakiItem, so the EmakiAttribute integration degrades gracefully when that plugin is absent instead of hard-failing.

Changed

• Reload is atomic: a candidate runtime is built in the background and installed only when no blocking problems exist. A failed reload keeps the previous runtime serving, and a superseded reload is reported as stale.
• Reload summary numbers come from that reload's own result, so concurrent reloads no longer report mixed counts.
• Forge settlement has an explicit commit boundary, so a stale completion no longer returns already-consumed inputs a second time.
• The recipe book binds to the runtime snapshot taken when it was opened, so paging during a reload cannot mix generations.
• GUI templates are loaded by their own loader and participate in reload candidate validation.
• Message prefix switched to a new brand gradient.
• api-version raised from 1.21 to 1.21.8; only 1.21.8+ is supported. The build base moved from spigot-api to paper-api, so API consumers must switch their compile base. Java target stays 25, folia-supported: true and the permission set (use/book/reload/debug/admin) are unchanged.
• Cross-plugin hard API version gating was removed, so mixing slightly different Emaki minor versions is no longer blocked at startup.

Fixed

• /emakiforge reload used to report success unconditionally and swallow failures; it now reports failure with detail (the general.reload_fail message key existed but was never sent).
• Reload replies are delivered on the sender's own execution domain, which is required for correctness on Folia.

Removed

• The browser-based Web Console layer (web-console.yml, web-extensions/, the web-console/ frontend project). Owners who edited config through the browser must edit YAML directly.
• gui/editor_gui.yml, the admin recipe-editor template, whose only entry point was the removed web editor.
• Backward compatibility for the old recipe result structure: result.item_sources, result.meta_actions.name_actions, result.meta_actions.lore_actions and result.actions become result.success.outputs[].item_sources and result.success.name_actions / lore_actions / actions. Only success is read; if it is missing the recipe silently produces nothing, so all custom recipes must be migrated.
• The flat GUI slot item structure: item: "<MATERIAL>" with display_name, lore and hidden_components: [tooltip] becomes item.source with item.components.custom_name, item.components.lore and item.components.tooltip_display.hide_tooltip. All custom gui/*.yml must be migrated.
• The commands: section, as the descriptor moved from plugin.yml to paper-plugin.yml and commands register at runtime. Plain Spigot is no longer supported; Paper or a Paper fork is required.

Notes

• Requires EmakiCoreLib 4.6.0.
• Back up recipes/ and gui/ before updating, then migrate all custom recipes and GUI templates to the structures above.
• After updating, run /emakiforge reload and /emakiforge debug stats to confirm the registered recipe count matches expectations, then verify the forge GUI and recipe book.