Repository navigation
Reconcile the roadmap and current report benchmark evidence - #145
Merged
Merged
Conversation
PrzemyslawKlys
changed the title
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.
The roadmap still lists the completed assessment fixes as open PR work. Replace that checklist with the remaining full-report measurement, release qualification, and legacy issue decisions, and describe streaming and evidence privacy as current capabilities.
The legacy issue guide now describes the integrated history, streaming, and export contracts while retaining the distinction between current source and an installed package. This does not close or relabel any issue.
Retain the current report-rendering baseline with published HtmlForgeX.Email 2.0.0 and mobile stacked records alongside the historical 1.6 projection comparison. Email allocation stays approximately constant at 11.9 MB for 1,000 and 10,000 input events with 25 displayed records. The current dependency and markup differ from the earlier fixture, and full-detail HTML still scales with retained rows.
Validation: checked the documented owners and capabilities against current source and the merged changes; verified local documentation links and a clean diff. The retained benchmark run has twelve successful samples using one warmup, three measured iterations and rotated case order. This change updates human-authored documentation and recorded benchmark evidence only.