Skip to content

EMRY-003 registry + EMRY-002 review fixes (recover dropped stacked merge) - #51

Merged
vxfemboy merged 2 commits into
mainfrom
emry-003-registry-recovery
Jun 25, 2026
Merged

EMRY-003 registry + EMRY-002 review fixes (recover dropped stacked merge)#51
vxfemboy merged 2 commits into
mainfrom
emry-003-registry-recovery

Conversation

@vxfemboy

Copy link
Copy Markdown
Member

Recovers two already-reviewed commits that did not reach main: PR #49 was merged at its original commit before the EMRY-002 review fixes were pushed, and PR #50 (registry) merged into #49's branch rather than main. This brings both onto main.

Contains:

Gate green: fmt, clippy -D warnings, 21 tests, registry 100% line coverage.

Going forward: branch each issue off main and merge sequentially (no stacking) to avoid this.

vxfemboy added 2 commits June 24, 2026 20:39
…ack contract

- Pin the 'type' tag string of every Event variant against rename drift
- Document on Event: msgpack needs with_struct_map; JSON encodes NaN/Inf as
  null (lossy) so non-finite values must be caught and surfaced via Alert
- Fix MetricId doc capacity 65 535 -> 65 536
Add MetricRegistry mapping names to dense u16 MetricIds for the hot path.
Idempotent register(), try_register() for the full-table case, name()/get()
resolution, and MAX_METRICS = 65536 cap. Stable-id and duplicate-name tests.
@vxfemboy
vxfemboy merged commit de012bd into main Jun 25, 2026
3 checks passed
@vxfemboy
vxfemboy deleted the emry-003-registry-recovery branch June 25, 2026 00:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant