Why this project matters
It keeps two things apart that are easy to conflate. Learning that a treatment exists is not permission to copy the asset that demonstrated it, so rights are recorded per example and reference-only material is never presented as cleared. It keeps a third apart: an engine that can find, classify and publish is implementation, and shipping it is release, and neither one is demand. Its own backup records that nobody has yet rated, reported, disputed or objected to anything it found.
Where the work stands
Local folders are now a first-class source alongside GitHub. Byte inspection, intent-first discovery, portable packs and backup-and-restore work have landed. The report records an exact production verification for an earlier release; newer source work is ahead of that receipt.
The next useful proof
Prove the newer source in production, expand useful handlers and discovery, and observe outside builders completing real hunts.
What this record does not claim
A dated summary of the operator-supplied 7 October report. Reported release evidence is distinct from a fresh Woodhouse inspection, physical-device acceptance and demonstrated external use.
Project state is specific to the reviewed report. An implementation, merge, test result, production deployment and physical observation are separate claims; one does not automatically prove the next.
