Correct mismatched release artifact paths #1

Summary

The release workflow writes compiled binaries to a parent build directory but stages assets from a repository-local build directory. Every release run reaches asset preparation without a matching binary at the path it copies.

Location

• File(s): .github/workflows/release.yaml
• Line(s) / function(s): Build Binary and Prepare Release Assets steps at L40-L49

Category

functional

Severity

high

Release publication cannot attach any generated binaries, leaving users without downloadable release assets.

Reproduction / Evidence

Verified by code analysis: L40-L43 execute from the repository root and send go build output to ../build. L45-L49 then copy from ./build. These resolve to different directories, so the copy source does not contain the generated binary.

Expected Behavior

The binary produced by the build step is present in the directory consumed by the asset preparation step.

Actual Behavior

The binary is written to ../build while asset preparation reads ./build, causing release asset staging to fail.

Root Cause

The build and staging steps use inconsistent relative paths for the build directory.

Notes

The v1.0.0 release workflow failed and the published release contains no assets.