ModStatusKit 0.1.7

Changes

• Added a CBA-inspired Fabric embedded reference with optional ModMenu UI guidance, helper-based tone rendering, and copy/paste-oriented networking/status snippets.
• Clarified that ModMenu is only the reference UI choice and is not required to use ModStatusKit.
• Clarified that UIs should render ModStatusDisplay.tone(), including teal build mismatch, orange WARN/default mismatch, red BREAKING mismatch, and gray unknown/disconnected states.

Verification

• .\scripts\test-java-core.ps1
• .\scripts\test-release-gate.ps1
• .\scripts\check-fabric-reference.ps1
• git diff --check
• .\scripts\check-release-gate.ps1 -Mode PreRelease

ModStatusKit 0.1.6

Changes

• Added first-class StatusTone.TEAL for matched base versions with different reported build metadata.
• Updated ModStatusKit.display(...) so consuming UIs can render the documented blue/teal diagnostic tone directly from display.tone().
• Updated the Fabric embedded reference and README guidance to use the core tone instead of re-implementing build comparison.

Verification

• .\scripts\test-java-core.ps1
• .\scripts\test-release-gate.ps1
• .\scripts\check-release-gate.ps1 -Mode PreRelease

ModStatusKit 0.1.5

ModStatusKit 0.1.5 adds optional server-declared public version mismatch severity.\n\nHighlights:\n- Add VersionMismatchSeverity.WARN and BREAKING.\n- Add StatusTone.RED for server-declared breaking public/base version mismatches.\n- Keep default version mismatch behavior orange/WARN.\n- Keep build mismatch diagnostic only; it remains a consuming-UI teal/blue treatment and never becomes red in core behavior.\n- Add optional structured MSK2 status payload helpers while preserving legacy payload compatibility.\n- Update README and Fabric embedded reference guidance for mod writers.