js: key the page runner's report by target, not suite - #72
Merged
Conversation
Several targets may run one suite — a plain and a delegated composition of the same corpus — and the report keyed by suite name collides for them. The target is the identity that is unique per run by construction (one aggregate row each). Caught designing the first consumer, before anything baked the suite keying in.
This was referenced Aug 7, 2026
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.
One-line correction to #71, caught while building its first consumer (polymorph-tls#32): tls runs the same suite identity as two targets (plain and delegated compositions), so a report keyed by suite name collides. Targets are unique per run by construction — one aggregate row each. No consumer had adopted the suite keying.