Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (43)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughReady-task summaries and contributor task details now show compensation from each task’s locked contribution policy version. Active exact-project Submitters and Reviewers can read these terms. The change also adds CLI validation and display; task claim and start remain Submitter-only. ChangesLocked compensation visibility
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant TaskQueueRouter
participant TaskRepository
participant ContributionPolicyRepository
TaskQueueRouter->>TaskRepository: read ready tasks
TaskRepository->>ContributionPolicyRepository: read terms for locked policy version IDs
ContributionPolicyRepository-->>TaskRepository: return locked compensation terms
TaskRepository-->>TaskQueueRouter: return ready summaries with compensation
Merge Risk: ⚪ Minimal · up to No identified defect prevents merging. The reported current-head hosted CI run and required human approval remain outstanding. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 34.62% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 78 functions across 36 files. (7 skipped: 7 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
e3b8120 to
677101a
Compare
Fixes #506.
Released tasks expose the exact compensation terms from their locked
ContributionPolicyVersionin contributor ready rows and task detail. Active exact-project Submitters and Reviewers see bothaccepted_submissionandcompleted_reviewas eitherunpaidor award rows containing only the policy UUID, instrument, unit, and exact decimal-string quantity. Claim/start remain Submitter-only. Responses exclude Finance bindings, route keys, payment state, and fulfillment state.CONTRIBUTIONS supplies one bounded public locked-version port. TASK owns its response DTO and resolves only
WorkstreamTask.locked_contribution_policy_version_id; it never falls back to the project's current policy. The CLI validates and displays the same block fortask readyandtask show. No migration, policy locking/publication, payment, award creation, or fulfillment behavior changes.Current review target:
36e8a615f01801cecd6ccf83d7411235ab1cfa8fff62b273bccbe670071f2876bc64b306945186376cd83dc9e66b32bfe87f72bbccebe23a9dbb9c8bValidation and provenance:
ec4c8505: 2 real-PostgreSQL paid/unpaid locked-term cases passed with exact decimals, successor-policy immutability, Submitter/Reviewer/outsider authority, and complete database cleanup.677101a8source passed 60 TASK owner projections, 7 changed AUTH matrix cases, 39 architecture/module-boundary cases, and 12 built-CLI HTTP process cases. That hosted run used an older base and is historical evidence, not current-main CI proof.gofmt,task ready --help, Commitrail validation, Markdown links, and diff hygiene.The branch has been reconciled with current
main, preserving PR #504 dispatch, PR #505 guide reads, PR #509 request delivery, and PR #507's qualified gVisor experiment limits. Human review and merge remain required.Summary by CodeRabbit