Repository navigation
ci: include QA in CaptureKit verification - #2431
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.
CaptureKit changes now select the QA package tests alongside CaptureKit, CLI and MCP tests. QA already declares the shared package and product in its manifest; the owner guide and Tools overview now document that third consumer.
The Live package inventory update is tracked separately in #2433, extracted from broader pending #2336. This extraction leaves that broader PR and the Companion-only inventory change in #2418 untouched.
Validation: independent full three-file factual/matrix review GREEN. Eleven mapped checks PASS, including 79 CaptureKit, 149 CLI, 272 MCP and 106 QA tests. Agent context selects QA for a CaptureKit source path; preflight passes and verify-change reports no applicable app check. The main-based fast and E2E commands are deliberately BLOCKED with exit 3 pending safe isolation integration, so the canonical proof records FAIL rather than a full pass. No native, real-library, SDK, model or account-isolation proof is claimed.