V7.17.3 Audit Report¶
The stable Release was published at 2026-10-29 13:37:22 UTC, with draft and prerelease false. All six assets were anonymously downloaded and checked against digests, witnesses, ZIP contents and GitHub signed provenance. The tag binds commit 1255fb0d18bc8b4e1ab580ca666a880aee15cdf3 and public assets were not replaced. See the validation report for the complete matrices and digests.
The adaptation implementation received independent logical-readonly source review. Early junction-blocked reports remain BLOCKED and two later reports remain incomplete. A final finite supplement passed with no findings and explicitly covered their named remaining source gaps. After versioning, 178 runtime, related installer and test files were rehashed and matched the reviewed candidate exactly; current full CI separately validates version metadata and artifacts. Old Review Packets were not presented as a fresh review of the complete current baseline, and neither incomplete reports nor the generic machine semantic UNVERIFIED result were rewritten as passed.
The independent reviewer did not repeat external Desktop workflows, mutating tests or installation and did not establish system-readonly isolation. Separate actual-operation evidence supports the listed native runtime paths; it does not certify enforcement of every enhancement path.
Provenance recovery requires host registration and native-turn evidence. Account-root aliases must prove the same directory and file before strict canonical-path checks. Inner junctions, foreign directories, file replacements and foreign-project input remain denied. Original task roots, spending, human grants, cancellations and late-callback ownership remain unchanged. Automatic goal context cannot grant authority.
Some source post-write audit receipts remain missing and UNVERIFIED. Actual bytes, current tests and payload digests have separate readback evidence; no write was replayed and no receipt fabricated. Capability-index exclusions for oversized files, sensitive fixtures and this phase's SENSITIVE_CONTENT result remain explicit. Neither full-index coverage nor semantic reuse approval is claimed.
PR #29 used the repository's existing maintainer exception for an explicitly authorized squash merge after every required CI check succeeded; protection rules were unchanged. This exception is not a GitHub peer approval, and independent Agent review was not represented as one. Post-release documentation is backfilled through a separate PR while signed tags and assets retain their original contents.
Actual client evidence is limited to Desktop 26.1023.50603 / build 22391. Formal publication, account installation and post-restart activation are separate facts. This phase did not separately install formal 7.17.3 or restart Desktop, and later client versions were not accepted.