Internal sample executed on Linux, October 10, 2026. No customer order or payment.
70fe3b34cd6dff1b3bba046638edc72a6467a4fb. Eight checks: six passed, two failed with ENOENT; exit 1.445c3c5ae3fca98168a3af0e28609d31b3ae6f03. Eight checks: eight passed; exit 0. Two expected warnings identified the skipped dangling symlink.Both upstream file walkers were exercised. Controls covered intact sibling contents, valid file symlink contents and target permissions, valid directory aliases and explicit ignore rules. Broken-link ignore count was checked where exposed by the API.
The fix is the existing upstream author's work, not ours. See issue #300 and PR #303. The recorded run used actual pinned upstream source, not a reimplementation.
Function-level regression evidence on Linux only. Not a full MCPB CLI build, full upstream suite, Windows/macOS test, interoperability test, security approval or recommendation to deploy the entire PR. Symlink cycles, outside-root links, permission failures and time-of-check/time-of-use races were not covered. No maintainer acceptance or merge status is asserted here.
The harness used Node's test runner and ignore@7.0.5 with lifecycle scripts disabled. Temporary test fixtures were removed after execution. No customer credentials were involved.