test: Stage 6

Author: tzanko-matev

README.md

@@ -45,6 +45,15 @@ Basic workflow:
   - from codetracer_python_recorder import hello
   - hello()
 
+#### Testing & Coverage
+
+- Run the full split test suite (Rust nextest + Python pytest): `just test`
+- Run only Rust integration/unit tests: `just cargo-test`
+- Run only Python tests (including the pure-Python recorder to guard regressions): `just py-test`
+- Collect coverage artefacts locally (LCOV + Cobertura/JSON): `just coverage`
+
+The CI workflow mirrors these commands. Pull requests get an automated comment with the latest Rust/Python coverage tables and downloadable artefacts (`lcov.info`, `coverage.xml`, `coverage.json`).
+
 ### Future directions
 
 The current Python support is an unfinished prototype. We can finish it. In the future, it may be expanded to function in a way to similar to the more complete implementations, e.g. [Noir](https://github.com/blocksense-network/noir/tree/blocksense/tooling/tracer).

codetracer-python-recorder/tests/README.md

@@ -34,6 +34,9 @@ CI configuration:
   in `codetracer-python-recorder/target/coverage/python/`.
 - `just coverage` is a convenience wrapper that invokes both commands in sequence.
 
+CI runs the same helper and posts a coverage summary comment on pull requests so
+reviewers can see the per-file breakdown without downloading artefacts.
+
 All commands create their output directories on first run, so no manual setup is
 required beyond entering the Nix shell (`nix develop`) or syncing the UV virtual
 environment (`just venv`).

design-docs/adr/0003-test-suite-governance.md

@@ -1,6 +1,6 @@
 # ADR 0003: Test Suite Governance for codetracer-python-recorder
 
-- **Status:** Proposed
+- **Status:** Accepted
 - **Date:** 2025-10-02
 - **Deciders:** Platform / Runtime Tracing Team
 - **Consulted:** Python Tooling WG, Developer Experience WG
@@ -67,7 +67,7 @@ We will adopt a tiered test governance model and reorganise the repository to ma
 
 ## Status Tracking
 
-- This ADR is **Proposed**. It becomes **Accepted** once the restructuring PR and the initial coverage additions (TraceSessionBootstrap, TraceOutputPaths, ActivationController, Python facade helpers) are merged and `just test` runs green with the new layout.
+- This ADR is **Accepted**. Directory restructuring, unit/integration coverage for the targeted modules, and the split CI/coverage jobs have landed; future adjustments will be tracked in follow-up ADRs if required.
 
 ## Alternatives Considered
 

design-docs/test-suite-improvement-plan.status.md

@@ -17,8 +17,10 @@
 - ✅ Stage 5 – CI & Coverage Instrumentation: CI now runs the split Rust/Python
   test jobs plus a non-blocking coverage job that reuses `just coverage`, uploads
   LCOV/XML/JSON artefacts, and posts a per-PR summary comment.
-- ⏳ Stage 6 – Cleanup & Documentation: not started.
+- ✅ Stage 6 – Cleanup & Documentation: ADR 0003 is now Accepted, top-level
+  docs describe the testing/coverage workflow, and the tests README references
+  the CI coverage comment for contributors.
 
 ## Next Actions
-1. Evaluate coverage report stability and prepare enforcement thresholds before
-   Stage 6.
+Plan complete; monitor coverage baselines and propose enforcement thresholds in
+a follow-up task.