docs: promote lessons-housekeeping residue from small-tooling-batch (#921)#924
docs: promote lessons-housekeeping residue from small-tooling-batch (#921)#924cuioss-oliver wants to merge 1 commit into
Conversation
…921) The phase-6 lessons-housekeeping step (PR #921) retired three shipped lessons and promoted their durable residue into docs, but the promotion edits landed post-merge on protected main and could not ride #921. This follow-up ships them: - build-pyproject/standards/pyproject-impl.md: add a Verification-Target Trust section (un-trusted-green principle, validate against a clean mypy cache before trusting local green, environment-divergent-import exclude guidance) and correct the stale `verify` row in the Quality Commands table to quality-gate + test-compile + module-tests. - manage-adr/SKILL.md: document the cross-session ADR-numbering race caveat (provisional-until-merge) in the File Naming Convention section. Co-Authored-By: Claude <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @cuioss-oliver, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
Warning Review limit reached
Next review available in: 10 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository: cuioss/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
1 participant
Summary
Follow-up to #921 (small-tooling-batch). The phase-6
lessons-housekeepingstep retired three shipped lessons and promoted their durable residue into docs, but those promotion edits were produced post-merge and could not ride #921 (protectedmain). This PR ships them.Changes
2026-07-15-12-001: validate against a clean mypy cache before trusting a localtest-compile/verifygreen, and use a[tool.mypy] exclude(not a per-codetype: ignore) for.claude-local test dirs whose imports resolve differently in CI vs local. Also corrects the staleverifyrow in the Quality Commands table toquality-gate + test-compile + module-tests(the D4 change in fix: batch four independent tooling fixes (ADR/npm-gate/lessons/CI) #921).2026-07-16-17-005.Docs-only. No code or test changes.