feat(constants): render atom-disagg as Mooncake ATOM framework

[adibarra]

Note

Low Risk
Small constants-only change with tests; ETL and UI pick up aliases automatically with no auth or data-schema changes.

Overview
Adds mooncake-atom to the shared framework registry with display label Mooncake ATOM¹, and maps the legacy atom-disagg identifier to that canonical key with disagg: true in FRAMEWORK_ALIASES (same pattern as sglang-disagg → mori-sglang).

Because ETL normalizeFramework and UI label resolution already read these constants, atom-disagg in artifacts and config keys (e.g. dsv4-fp4-mi355x-atom-disagg) now normalize to mooncake-atom and show as Mooncake ATOM¹. Coverage is extended in framework-aliases and ETL normalizer tests.

^{Reviewed by Cursor Bugbot for commit 35789e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
inferencemax-app	Ready	Preview, Comment	Jun 12, 2026 4:12am

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 35789e4. Configure here.}

[cursor]

Mooncake atom skips disagg forcing

Medium Severity

This change introduces canonical mooncake-atom for disaggregated Mooncake ATOM runs, but ETL normalizeFramework only forces disagg for dynamo-* and mori-* canonical names. Rows ingested with framework already set to mooncake-atom and disagg false can keep disagg: false, unlike other disagg-only frameworks.

 

^{Reviewed by Cursor Bugbot for commit 35789e4. Configure here.}