Repository navigation
fix(api): grid restores original name for std companion series (B21ru) → 0.1.0a10 - #52
Merged
Merged
Conversation
SumoSession.grid inverse-mapped the response key but not its companion:
the engine hangs the predicted-std column off the MAPPED response name
(y1_std), which passed the inverse mapping's unknown-key passthrough --
so GridResult.data carried y1_std for an underscored QoI. Consumers
look gridData[qoi + "_std"] up; the leak camelCases on the wire and the
lookup silently misses (caught by mmux_vite's V47pk route test).
- grid loop renames {mapped_response}_* companions to {response}_*
(suffix kept) beside the plain response rename (V21pf)
- regression test: QoI renamed to max_abs_stress asserts no y1* leak
and std companions subset of {max_abs_stress_std}
- SPEC B21ru; version 0.1.0a9 -> 0.1.0a10
Co-Authored-By: Qwen3.8 Flash Next NVFP4 (AWS vLLM) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mmux_vite's V47pk route test caught a V21pf leak on the grid path:
SumoSession.gridinverse-mapped the response key but not the engine's COMPANION series — the predicted-std column hangs off the MAPPED response name (y1_std), passed the inverse-mapping unknown-key passthrough, and surfaced as a mapped-name key inGridResult.data. Consumers look upgridData[qoi + "_std"]; the leak camelCases on the wire and the FE lookup silently misses (empty 2D/3D plot at HTTP 200 — the exact B29dr bug class mmux hardened with V47pk).{mapped_response}_*companions to{response}_*(suffix kept) beside the plain response renamemax_abs_stress; asserts noy1*key ∧ std companions ⊆{max_abs_stress_std}