July 19 Daily Completion Report¶
Release-candidate outcome¶
The repository is prepared as GuardianNode 0.1.0-alpha.2, with a rebuilt
embedded dashboard, release notes, sample configuration, mock/live instructions,
troubleshooting, synthetic demo data, and an explicit clean-Windows checklist.
No API key is embedded.
Exact local verification¶
Environment: Linux 7.0.12 x86_64, Python 3.12.13, Node 24.18.0, npm 11.16.0. This is an independent source verification environment, not the Windows developer workstation and not a substitute for Windows installer qualification.
| Suite / command | Result | Duration |
|---|---|---|
python -m pytest -q backend/tests tests/e2e |
276 passed, 0 failed, 0 skipped | 54.59 s pytest / 56.78 s wall |
python -m pytest -q agent-windows/tests |
59 passed, 0 failed, 0 skipped | 4.10 s pytest / 5.08 s wall |
npm test -- --run |
19 passed, 0 failed | 6.38 s latest runner |
python -m pytest -q tests |
58 passed, 0 failed, 0 skipped | 5.12 s pytest / 6.41 s wall |
| Unique suite total | 412 passed | — |
Additional gates passed:
- Backend and agent Ruff; backend mypy (81 source files); dashboard typecheck/build.
- Python compile, feature matrix, version consistency, generated hardware tiers, third-party notices, repository controls, Linux installer shell syntax.
- Rules benchmark: 196 cases, 100% recall/precision in the frozen rules corpus, zero gate failures; this is corpus evidence, not universal accuracy.
- Backend and agent direct dependency audits: no known vulnerabilities.
- Dashboard production dependency audit: zero vulnerabilities.
- Strict MkDocs build and tracked Git-history gitleaks scan.
The first local agent run could not collect because its virtualenv was absent;
the intended locked dependencies were installed into the isolated test
environment and the full 59-test suite then passed. The first mypy command was
run from the wrong directory and exposed known platform/configuration errors;
the exact CI command from backend/ passed. These setup errors are documented,
not counted as product test failures.
Release decision¶
The source candidate is ready for GitHub CI and Windows artifact generation. It is not yet qualified as a dependable Windows beta installer: fresh Windows 11 install, first launch, service/reboot recovery, firewall behavior, uninstall, reinstall, signatures, and exact artifact checksums remain manual. Do not create or publish the RC tag unless branch/PR checks pass; do not promote the draft artifacts until the clean-install checklist is completed.