Repository navigation
docs: correct CaptureKit limits and summary comments - #2428
Merged
Merged
Conversation
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.
Correct CaptureKit's classification-prefix comment to 512 KB, matching the existing constant and Core frontmatter limit. Remove an obsolete app-parser reference and the incorrect two-shape wording from the summary parser documentation.
Only documentation comments changed; non-comment lines are byte-identical to the base. Independent factual/source review: GREEN. The same two comment hunks also appear in pending #2336; that broader PR remains untouched.
Validation: nine mapped checks PASS, including the 79 CaptureKit, 149 CLI and 272 MCP package tests. Preflight passes; verify-change reports no applicable app check. E2E is deliberately BLOCKED with exit 3 on this account pending the reviewed isolation union, so the canonical proof records FAIL. No native app, model, SDK or real capture-library proof is claimed. Draft retained for review.