docs: document Windows test prerequisites - #2667
Conversation
There was a problem hiding this comment.
Graphify reviewed this change.
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Graphify review — findings
This pull request adds a new "Windows note" callout to the README's testing section. The note documents Windows-specific test suite considerations, such as enabling Developer Mode for symbolic links, the LongPathsEnabled policy, and clarifies that CI runs on Ubuntu with Python 3.10/3.12 while Pyright is a non-blocking advisory check. The change is documentation-only.
No blocking issues surfaced.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 25 functions depend on the 25 functions this change touches.
Health — grade A; no new coupling hotspots.
Verification — 25 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 25 function(s) in the blast radius were not formally verified this run
|
Shipped in v0.9.42 ( |
Summary
Verification
uv run --frozen ruff check .tools.skillgenconsistency guardsgit diff --checkScope
Documentation-only:
README.md. No source, test, generated artifact, hook, skill, or system-setting changes.