Repository navigation
CI: run the suite as python -m pytest - #66
Conversation
47fdf33 to
e547218
Compare
|
The failing |
- .github/workflows/test.yml: full pytest, --help/doctor smoke, wheel installed into a clean venv to prove the four data trees actually ship (test_packaged_runtime only asserts pyproject TEXT), and both knowledge linters — on every push and PR. Signal only for now: making it a merge gate needs the suite job set as a required status check in repo settings, which no commit can do. - DEVELOPMENT.md documents that workflow and its limits; CODE_TOUR updated to cover all 80 source files with the staged reading route. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Run the suite as `python -m pytest`: bare `pytest` omits the repo root from sys.path, and upstream test_release_audit.py imports the root-level tools/ package — the exact command DEVELOPMENT.md documents.
e547218 to
775c535
Compare
|
Update: #64 accidentally merged this PR's original CI/docs content instead of the Direct/MCP work (branch ref mishap on my side — details in #67). Consequences for CI: main's red |
Reduced scope: the workflow and doc refresh originally in this PR already landed on main as 47fdf33. What remains is the one fix its first run surfaced.
Bare
pytestomits the repo root fromsys.path, andtest_release_audit.pyimports the root-leveltools/package — so collection dies in 20s (ModuleNotFoundError: No module named 'tools') on every run.python -m pytestinserts cwd, and is the exact command DEVELOPMENT.md documents. Both suite invocations updated.With #64 merged (the config.py ratchet fix), this is the last known blocker to a green
suitejob.🤖 Generated with Claude Code