docs: stop hardcoding the artifact count in CLAUDE.md - #90
chitcommit wants to merge 1 commit into
Conversation
CLAUDE.md asserted "104 capabilities" in three places. marketplace.json holds 106. The number was correct when written and stopped being true the moment an artifact was added — which is what a count in prose always does. This was not cosmetic. CodeRabbit cited these lines as "Coding guidelines" on PR #89 and raised a Major / Data Integrity finding instructing: "The catalog currently contains 106 artifact IDs with unique IDs, so the /market inventory is oversized. Remove the two extraneous artifacts." Following it would have deleted two real, live artifacts to make reality agree with a stale sentence. The reviewer was reasoning correctly from a false premise, and the premise was this file. The real invariant is already mechanized and needs no restating: scripts/check-overlay-coverage.sh asserts marketplace.json and capabilities.generated.json project the same id set, whatever its size. That gate is what caught the genuinely missing skill-hygiene record on #89. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EtosSqJ6sL5dMyeHfkNrTe
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 39 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. 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
CLAUDE.mdasserted 104 capabilities in three places.marketplace.jsonholds 106. The number was true when written and stopped being true the
moment an artifact was added.
Why this is not cosmetic
On #89, CodeRabbit read those lines as Coding guidelines and raised a
Major / Data Integrity finding:
Following it would have deleted two real, live artifacts to make reality
agree with a stale sentence. The reviewer reasoned correctly from a false
premise, and this file was the premise.
That finding also blocked #89 from merging —
required_conversation_resolutionis enabled on
main, so an unresolved thread blocks regardless of whether thethread is correct. #89 was merged with
--admin, i.e. past the finding ratherthan through it. Removing the false premise is what stops that recurring.
The fix
Delete the count; do not replace it with
106, which would just reset the sametrap. The invariant is already mechanized:
scripts/check-overlay-coverage.shassertsmarketplace.jsonandcapabilities.generated.jsonproject the same id set at whatever size — and itis what caught the genuinely missing
skill-hygienerecord on #89.Validation
Docs-only change; no script or manifest touched. Full local gate run on #89's
head (which includes this content): coverage 106/106, §16 schema, provenance
verify, source freshness, lint-plugins, test-plugins 86/86, dispatch audit
119 cells / 0 drift.
Related: #89,
chittyfoundation/chittygov#29.