Repository navigation
Collect complete upgrade changelog statements with shared filters - #479
Merged
Merged
Conversation
Record the reviewed one-increment migration, authenticated schema and complexity evidence, effective filters, minimal projections and complete collection rules. Correct the backlog to distinguish resolved backend data support from remaining supersession questions.
Replace capped risk items with source-ordered statements and shared tier filters. Fetch mode-specific projections, retain whole-range triage counters and keyword evidence, and document the JSON migration with CLI/MCP parity coverage.
Close review findings across keyword text, signals and URLs; avoid repeated locators and nest sources beneath versions. Resolve view and tier selection once in the shared request builder and clarify oversize classifications in the MCP schema.
Restore aggregate security variable, minimal-selection, advisory mapping and backend error guards alongside complete statement tests. Cover strict field validation and record the final agent workload limitations.
The final Opus round is clean and all accepted findings are closed. Permanent implementation docs retain the contract, query budget, dev evidence and eval limits; the backend supersession gap remains in the backlog. Deliver for owner review without merging.
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.
Upgrade reviews now collect every matching parsed changelog statement, replacing the priority-ordered 50-item risk cap. CLI and MCP share source-ordered bullets with nearby links, backend-owned uncertainty and the changelog filter syntax. The default remains focused;
--changes actionable|important|all/ MCPchangeslimits statement evidence while whole-range counters still drive batch triage.Compact batches fetch counters without statement or entry arrays. Detailed views collect 100-item pages; JSON includes full statement/context text, source positions and per-item provenance. Existing security, dependency and keyword evidence remain available.
JSON migration:
changelog.riskItemsbecomeschangelog.statementswith effectiveselection, complete counts/items and per-version coverage.riskCoverage.itemsOmittedis removed. Both public artifacts have pending minor release fragments; production aggregate-schema availability is a prerequisite for release.Validation:
Review: internal preflight/correctness passes and external Opus review are clean. Round3 verified all sanitation, presentation, request ownership and test-coverage findings closed. The temporary implementation plan is retired; permanent docs and the backend supersession backlog retain relevant facts.
Dev totals (warm stored labels):
All three ranges had zero not-assessed, without-notes and unparseable versions. Fixture coverage includes pending, missing/zero/oversize statements, truncation, multi-page completeness, changed evidence, filters, sanitization and CLI/MCP parity. No backend contract problems found. Backend supersession relations for fixes later reverted remain a documented backlog item, with no client inference added.