Skip to content

chore(ei-parity): empty known-deltas registry + fix anonymous deadCount parity - #238

Merged
Roddygithub merged 2 commits into
mainfrom
chore/ei-parity-known-deltas-empty
Aug 16, 2026
Merged

Roddygithub merged 2 commits into
mainfrom
chore/ei-parity-known-deltas-empty

Conversation

@Roddygithub

Copy link
Copy Markdown
Owner

Part of the ei-parity certification cleanup that was stranded in the closed #232/#234 branches.

Commit 1 — chore(ei-parity): empty known-deltas registry
Restores known-deltas.json to the spec-defined end state (story 2 'Normaliser le rapport de certification': schema v1, registre vide, les écarts sont FAIL). The 31 rules held private account names (krill le faucheur.1679, etc.) which violate the certification's no-private-data-in-versioned-artifacts constraint.

Commit 2 — fix(ei-compare): aggregate deadCount for anonymous agents sharing an instance
EI groups every anonymous agent sharing an instance into one Non Squad Player entity. The static player_agent_ids fallback returned {agent.id} whenever a named agent recycled the instance, dropping the other anonymous agents' deaths (actual=1 vs expected=2). Un-skips the previously skipped deadCount parity test.

Signed-off-by: Roland Salardon <r.salardon@gmail.com>
…instance

EI groups every anonymous agent sharing an instance into one Non Squad
Player entity, so deaths sourced by any of them count toward the kept
first agent. The static player_agent_ids fallback bailed to {agent.id}
whenever a named agent recycled the instance, dropping the other
anonymous agents' deaths. Un-skip the deadCount parity test that
asserts this.

Signed-off-by: Roland Salardon <r.salardon@gmail.com>
@Roddygithub
Roddygithub merged commit 9592793 into main Aug 16, 2026
11 checks passed
@Roddygithub
Roddygithub deleted the chore/ei-parity-known-deltas-empty branch August 16, 2026 07:01
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