CompatScope

Highlights

• Full Russian localization for the in-game interface.
• Improved and standardized technical terminology across the UI.
• Non-blocking Fixes and Simulation screens.
• Verified SAFE Apply for real SERVER_DATA resources.
• SAFE support for:
  • mod-provided server data;
  • external datapacks;
  • vanilla/built-in minecraft resources;
  • other live SERVER_DATA providers.
• SHA-256 verification of source resources before Stage/Apply.
• Fail-closed behavior when a provider is missing, unreadable or changed since Scan.
• Client assets remain Stage-only and are not treated as SAFE.
• Improved Fix Preview provider selection and state synchronization.
• Correct runtime classification for registry tag validation.
• More accurate and transparent HTML report totals.
• Improved runtime diagnostic structure and attribution.
• Stable behavior validated on both Fabric and NeoForge.

Localization

• Added complete Russian (ru_ru) localization for the in-game interface.
• Localized:
  • Fixes;
  • Fix Preview;
  • Simulation;
  • Search;
  • Reports;
  • Changes;
  • Dependency Graph;
  • Diagnostics;
  • Fix History;
  • Runtime;
  • Settings;
  • Help;
  • Mod/Object Inspector;
  • Server API.
• Dynamic messages, fix descriptions, validation results and compatibility guidance are localized.
• Technical identifiers remain unchanged where appropriate, including:
  • SAFE;
  • CONDITIONAL;
  • MANUAL;
  • UNSUPPORTED;
  • priorities and severities;
  • resource IDs;
  • paths;
  • config keys;
  • operation IDs;
  • raw log text.
• Added localization consistency checks for English/Russian key parity, placeholders and protected technical values.

Fixes and SAFE Apply

• Reworked the generated-fix pipeline to use stricter SAFE validation.
• A fix can become SAFE only when:
  • it targets supported SERVER_DATA;
  • the provider is explicitly selected;
  • the source still exists;
  • the source can be read;
  • the current source bytes match the SHA-256 recorded during Scan.
• Source validation is repeated immediately before Apply.
• Missing, changed or unverifiable sources fail closed and remain non-SAFE.
• Original mod JARs are never modified.
• Duplicate recipe IDs and other ambiguous compatibility cases are not automatically promoted to SAFE.
• Material-policy choices remain non-SAFE.
• External datapacks can now be validated through the live ResourceManager.
• Vanilla/built-in minecraft SERVER_DATA can also be selected and verified safely.
• Fix Preview now prefers a uniquely effective provider when live ResourceManager ownership is known.
• Provider suggestions are never applied automatically.
• SAFE state now remains synchronized after:
  • provider selection;
  • validation;
  • Stage;
  • Apply;
  • repeated Scan.
• Fixed a case where the UI could show a verified SAFE provider while still displaying the old CONDITIONAL plan.
• Already-applied SAFE fixes now remain visibly SAFE while correctly reporting that they are already prepared/applied.

Performance and UI

• Moved Fix availability calculation off the Minecraft render thread.
• Added asynchronous loading and error states for the Fixes screen.
• Added bulk Fix Preview generation using a shared fix context.
• Returning from Fix Preview no longer causes unnecessary full list rebuilding.
• Moved remove-mod Simulation processing off the render thread.
• Added an in-progress Simulation state.
• Optimized graph traversal using indexed node/edge adjacency.
• Optimized owned tag/resource counting.
• Added regression checks for heavy UI work and Simulation behavior.

Runtime Diagnostics

• Improved runtime operation, subject and impact metadata.
• Fixed registry_tag_validation classification so registry tag problems are consistently reported as: runtime:registry
• Registry tag diagnostics are no longer affected by incidental wording such as data pack or biome.
• Improved source/provider attribution using verified physical resource ownership.
• Runtime failures now distinguish framework reporters from actual source providers more reliably.
• Added structured handling for missing datapack lookups:
  • category: runtime:resource;
  • operation: data_pack_missing;
  • impact scope: ENTRY;
  • subject: data_pack:<id>;
  • affected target: pack:<id>.
• CompatScope's own early startup lookup for: compatscope/generated_data is treated as an informational observation instead of a false actionable warning.
• Improved handling of runtime recipe, loot, advancement, registry and resource failures.
• Expanded regression coverage for runtime category isolation and structured diagnostic invariants.

Reports

• Fixed misleading HTML report totals.
• HTML reports now clearly distinguish:
  • total diagnostics in the complete Scan;
  • diagnostics included in the bounded HTML detail section.
• Informational findings now show:
  • total INFO findings;
  • INFO findings actually included in the HTML.
• Fix availability is explicitly marked as applying to findings included in the HTML report.
• Bounded HTML output no longer implies that the first 500 entries represent the complete result set.
• Improved report metadata, diagnostic summaries and investigation grouping consistency.

Reliability

• SAFE Apply remains fail-closed.
• Added regression checks for:
  • external datapack verification;
  • vanilla SERVER_DATA verification;
  • changed/missing providers;
  • client asset rejection;
  • registry tag category isolation;
  • generated datapack startup lookup semantics;
  • report invariants;
  • localization consistency;
  • UI performance boundaries.
• Validated with real Fabric and NeoForge modpacks.

Schema Versions

• Report format: 52
• Diagnostic schema: diagnostics-52
• Analysis schema: analysis-63