[mohammadfawaz]

Package loading could read or write outside the intended package and build paths. Distinct names such as foo and foo.aleo could also replace the same build artifact.

• Validate primary and dependency names before constructing paths. Require local Aleo bytecode to declare the requested program ID.
• Reject dependency aliases that share an output path, including an alias for the primary program and names that differ only in ASCII case.
• Reject symlinks and nonregular entries in manifests, lock files, source and test directories, cached Git checkouts, and build output. Apply the source checks to the compiler and LSP.
• Validate locked Git commit hashes before constructing checkout paths. Preserve the network pins, dependency updates, and atomic lock replacement from Lock network dependencies and add explicit dependency updates #29641.

For example, a local dependency named ../outside.aleo now fails before build output is written. A dependency named app cannot replace the output for primary program app.aleo. A linked src, tests, or leo.lock now causes an error. Explicit local dependency paths remain supported, including a path that selects a package through a directory symlink. Library Helper and program helper.aleo cannot share a package graph or workspace, so the build remains portable across filesystems. Manifest and lock formats do not change. The checks do not prevent filesystem changes by another process during a build.

Findings addressed

• VERIA-38: unsafe package symlinks, source reads, and lock paths. https://veria.dev/dashboard/findings/n5AWPUXjfpayqyKgkdW7Y
• VERIA-39: dependency aliases that replace the primary build artifact. https://veria.dev/dashboard/findings/YjsTrJIAH6lHK6d-3nvI7
• VERIA-44: path traversal through local dependency names and redirected build output. https://veria.dev/dashboard/findings/Kryvats8XWjkLg0og7SHM
• Zkao ZK-b4307699: network dependency name traversal is already fixed by merged Lock network dependencies and add explicit dependency updates #29641. This PR adds manifest validation and regression coverage for that boundary. https://zkao.io/projects/cmprhqiat000b01im8jqltl47/repos/cmu11hn3700li01jwwpffxji5?view=findings&finding=fi_18e7b2f63e054f2eb4307699

This PR includes the changes from #29643, #29645, and #29648. Review the combined fix here.