feat: Rollup surfacing: priority + stuck (attempts)#34
Merged
Conversation
|
👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow. |
There was a problem hiding this comment.
QA Audit — PR #34 | feat: Rollup surfacing: priority + stuck (attempts)
VERDICT: WARN (pending CI — test in_progress; re-reviewing on terminal green)
CI Status
- test: in_progress
Diff Review
_rollup_onenow carriespriorityon everyblockedandcritical_pathentry; P0-first sort with id tiebreaker (__init__.py:225-226)- New
stucklist surfaces non-terminal features with>= 2attempts, sorted attempts-desc then priority-asc (__init__.py:228-233) - Terminal (done/cancelled) features now excluded from all three lists via
_TERMINAL_LANEScheck — previouslyblockedhad no exclusion andcriticalmissedcancelled(__init__.py:215-217) - Comprehensive new test
test_rollup_priority_and_stuckcovers P0-first sort, stuck threshold, terminal exclusion, and empty board (tests/test_portfolio.py:236-291)
Observations
- No findings. Implementation is clean, well-documented, and the test coverage is thorough across all acceptance criteria.
- Backward-compatible: new fields (
priority,stuck) are additive; existing consumers that ignore unknown keys are unaffected.
— Quinn, QA Engineer
|
Submitted COMMENT review on #34. |
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
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.
Let me check the rest of the file and understand the formatting issue.
Let me check the current state of the file more carefully and look for formatting issues.
Now I'll apply the ruff format fix to
__init__.py:Now let me verify the test file is comprehensive. Let me re-read the rollup tests:
Let me verify the full file is now clean:
All formatting and linting checks pass. Let me verify the final state of
_rollup_oneto confirm the implementation is correct:The implementation and tests are complete. Here's a summary of what was done:
Fix applied:
ruff format __init__.pyto fix the formatting issue flagged by the gate. The only change was wrapping thestuck.sort()key argument across multiple lines (ruff's line-length rule).Verification:
ruff format --check .→ all 8 files already formattedruff check .→ all checks passedImplementation already in place (from the previous rejected attempt):
_rollup_onereturnspriorityon everyblockedandcritical_pathentryblockedsorted P0-first, then by idstucklist: non-terminal features withlen(attempts) >= 2, sorted attempts-desc then priorityTests cover all acceptance criteria:
test_rollup_priority_and_stuck— priority present, P0-first sort, stuck threshold (1 attempt → not stuck, 2 → stuck), terminal exclusion, empty board