Repository navigation
fix: harden runtime parity and prepare 0.5.5 - #43
Merged
Merged
Conversation
|
Docs7 for cynrath/agent-context-kit
Commit |
context7
Bot
temporarily deployed
to
Docs7 Preview: fix/repository-audit-055
November 17, 2026 13:39
Destroyed
context7
Bot
temporarily deployed
to
Docs7 Preview: fix/repository-audit-055
November 17, 2026 14:04
Destroyed
This branch was successfully deployed
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.
Fixes Action severity failures being cleared by CLI success and removes the clean-tag dependency on missing ignored runtime files. The Action now builds its exact source with pinned setup actions and a frozen lockfile, then runs offline against the consumer (ADR-0034).
The patch also restores the SDK's built-in scan catalog, packages VS Code SDK resources correctly, confines finding navigation, enforces real extension lint/unit/Electron checks, aligns MCP inputs and startup-root/CI semantics, and uses canonical URI-safe SARIF projections for scan/optimize/drift. README/SDK documentation and task namespace references are corrected. Compatible runtime security dependency updates bring the production audit to zero.
Validation on Windows, Node 26.13.1, pnpm 11.22.0:
Source and extension metadata are coupled at 0.5.5. The published-stable pointer and stable install pins remain 0.5.4 until Marketplace, npm and GitHub Release are independently verified, then move in a follow-up PR (ADR-0029). Publication authorization is recorded in TASK-0103; no direct master push, dispatch/rerun, tag movement or immutable artifact overwrite is permitted.
Known scope limits: TASK-0097 retains its real external Docs7/account/build blockers. Historical blocked tasks remain intact. The full development-tool audit still reports 19 pre-existing tool-only advisories (6 high); their unused/runtime-excluded paths are explicitly triaged in TASK-0101. Production dependency audit is clean. No secret, permission, data migration or deployment change.
Hosted Node 22/24 on Linux/Windows/macOS and the required Action/extension/package jobs must all pass on this exact PR head before merge.
Hosted failures on the first head were corrected with regression evidence: workspace-relative Action manifest resolution for the pinned pnpm setup, serialized completed workspace refresh snapshots, and canonical temporary-path alias redaction. Existing lifecycle/redaction assertions and all required checks remain enforced.