Validation

Validation and limits

The cleaned development edition passed 818 full-suite tests in 741.912 seconds in a fresh protocol clone on Windows with Python 3.14. The validation receipt records the exact runtime revision, commands and scope. A fresh clone from the new GitHub repository subsequently passed 19 focused runtime/history/workflow tests, including all seven specialist invocations and missing-factor controls.

Four test modules containing 32 cases for the omitted real-source Canadian pack remain privately archived. They are not counted as passing public-edition checks. Original 842-test and later subset witnesses belong to their recorded historical snapshots; they do not silently transfer to changed code or excluded packs.

The stored-object audit covers Git objects and expanded workbook parts under declared credential/privacy patterns and structured source-payload screening. Missing original source objects and repository-context 404 checks support the clean-copy verification; they are not a blanket legal or provenance determination. See remote verification.

Controlled arithmetic, schema and fictional-workflow checks do not establish professional fitness, independent domain expertise or general agent reliability. The earlier independent food-workflow evaluation retained answer-exposure limits. Source, organization, professional and public-v1 acceptance remain separate.

To run the repository suite:

.\.venv\Scripts\python.exe -m unittest discover -s tests -v

The repository defines a manual Windows/Ubuntu, Python 3.11/3.14 GitHub workflow. Configuration is not evidence of a successful hosted run. Native Linux execution and broad agent-host discovery remain unverified.