Test protected MI input boundaries #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue/1-mi-input-guard-tests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #1. Add test-only regression coverage for hard-linked MI publication rejection and the 256 KiB trust-file boundary, including one byte over the limit. No production validation changes.
Validation: focused MI tests 10/10 passed; full Foundry suite 32 passed, 4 Docker runtime tests skipped because
FOUNDRY_TEST_SR_IMAGEwas not set. Prior independent GLM-5.3 review found no defects and verified the tests detect removal of link-count enforcement, a raised size limit and an incorrect inclusive limit. Final commit review anchoring is being checked separately.This does not establish viable-resource acceptance or close #1; SR #245 and #246 remain independent M1 gates.
Independent GLM-5.3 review is anchored to exact HEAD
5fbdfadddc5e0ee73116c0968c1875286c7249caand parent83a5b630576e7652a33b5811c1271a2119839498. The reviewer confirmed the committed 15-line patch matches the previously reviewed and mutation-tested diff; test file blob is102fe662587d3b56e9d63e8a5805be7471aac6fe, and the guard files are unchanged from the parent. Both new tests also passed from the exact committed objects. No defects found. Prior mutation checks detected removal of link-count enforcement, an increased size limit, and a changed boundary operator.Full suite: 32 passed, 4 Docker runtime tests skipped without
FOUNDRY_TEST_SR_IMAGE; focused MI suite: 10 passed. This is review evidence, not an assertion of a Forgejo approval.