[efraespada]

Closes #776.

Linux tool-cache CPython can install successfully yet fail to start because its shared library is absent from the verifier’s closed environment. The documented setup now derives a step-local bootstrap library path. The Git adapter independently captures the trusted tool-cache root before candidate execution and derives one contained library directory before the existing preflight, dependency preparation and configured command. Copied private venvs use bounded, stable, no-follow pyvenv.cfg metadata; inherited loader options remain excluded and the parent Node environment stays unchanged.

The native fixture selects CPython 3.11.17 on Linux and retains its complete pytest, Node/pnpm and JDK/Gradle verifiers, existing platform selections and deferred post/cleanup checks. Documentation, owner/companion SDDs, catalog evidence and strict coverage budgets are updated together.

Validation:

• Meaningful regression controls: the previous production adapter blocks the real official CPython 3.11.17 artifact; the corrected adapter runs the full unittest verifier with both copied and symlinked private venvs, unchanged candidate bytes, two fresh profiles and cleanup. The positive expectation fails against the previous adapter.
• 73 additional Jest cases (including a real CRLF checkout regression); initial complete root coverage: 792 suites, 14,733 passed, 35 existing platform skips. The CRLF regression adds one test; fresh exact-head CI runs the complete coverage suite again. All module budgets pass. New derivation module: 100% all metrics; Git adapter: 100% statements/functions/lines, 93.18% branches.
• Extension coverage: 100% all metrics. Build, types, lint, web checks, package validation/smoke, extension reproducibility, documentation/workflow/specification validators and AST graph update pass.

The initial Windows run found an LF-only fence extractor in two new documentation tests; native Python acceptance passed. The added CRLF regression first reproduces the failure, then passes with the extractor accepting both checkout line endings. Production code, platform skips, timeouts and coverage floors are unchanged by that correction.

The PR’s exact-head CI, native Linux/macOS/Windows acceptance, Codecov and complete review remain the merge gates. Consumer repositories were used only as read-only evidence.

[docs-page]

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/copilot~794

Documentation is deployed and generated using docs.page

[vypbot]

Bugbot: review complete

Current status: No active findings on 593d831.

Pull request · Verified commit · Workflow run

[vypbot]

Copilot approval · Human review needed

Status: A protected workflow, policy, or trust-boundary file changed.
Completed: 1/1 observed checks succeeded; Bugbot complete.
Action required: Ask a human reviewer to decide.
Impact: No new approval is confirmed for this revision.
See checks

Technical evidence

Revision: 593d831a6543; base: 229c576e5a0b; reason: protected-path.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.91%. Comparing base (5b3664f) to head (593d831).
⚠️ Report is 74 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #794      +/-   ##
===========================================
+ Coverage    94.50%   94.91%   +0.41%     
===========================================
  Files         1035     1091      +56     
  Lines        33299    35375    +2076     
  Branches      9824    10514     +690     
===========================================
+ Hits         31468    33576    +2108     
+ Misses         699      677      -22     
+ Partials      1132     1122      -10     

Files with missing lines	Coverage Δ
src/infrastructure/git_commit_adapter.ts	93.87% <100.00%> (+3.40%)	⬆️
...ructure/verification_python_library_environment.ts	100.00% <100.00%> (ø)

... and 102 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.