Validate the supplied Praxis Mine kit

From the extracted complete-kit root, run python tools/verify_release.py . --component-only. Require exit 0, ok:true and no findings. This checks declared file identities, local customer links, portable archive names and parity among the native plugin, standalone skill and Claude upload. It does not authenticate the publisher; compare any trusted external digest separately.

From codex/praxis-mine/skills/praxis-mine, run python -B -m unittest discover -s tests -v. The included local fixtures exercise explicit decisions, missing rights/comparison evidence, material changes, transactional failures, read-only missing-home handling, integrity errors, recovery and exports. Fictional fixtures are not model trials or evidence that a particular outside product is useful.

The maintenance review also exercises the actual isolated Windows room: first source/finding, evaluation, both environments, comparisons, stale assessment display, history, import/export, conflict recovery and narrow layout. The retained maintainer report identifies exact candidate bytes and what ran; historical receipts do not qualify changed bytes. Native macOS execution, fresh account activation, assistive-technology use and representative-user studies remain untested.

Documentation-manifest.json lists the full customer corpus. The scoped documentation-authorship.json binds only the files materially revised in this pass; documentation-custody.json identifies their current scope and unchanged files retaining prior authorship. Neither is independent verification. The source inspection, local runtime controls and native extraction support bounded claims, not defect freedom, source truth, legal correctness, accessibility conformance, directory approval or customer outcomes.

See Host compatibility, Limitations and Troubleshooting.