build-cli: misleading output path after build

[sekulicd]

Summary

Running make build-cli prints a misleading build output path:

Building ark cli binary...
Building ark for darwin arm64
Version: v0.9.3-1-g9d2f1ae3
Build complete: build/ark-darwin-arm64

The message Build complete: build/ark-darwin-arm64 suggests the binary is at build/ark-darwin-arm64 relative to the repo root, but it's actually at pkg/ark-cli/build/ark-darwin-arm64.

This is because the build script (pkg/ark-cli/scripts/build) does pushd into pkg/ark-cli/ before building, so build/ is relative to that directory — not the repo root where make build-cli was invoked.

Expected behavior

The build output should print the full path (or repo-root-relative path) so the user knows where to find the binary, e.g.:

Build complete: pkg/ark-cli/build/ark-darwin-arm64

Steps to reproduce

make build-cli
ls build/ark-darwin-arm64        # No such file or directory
ls pkg/ark-cli/build/ark-darwin-arm64  # ← actual location

[arkanaai]

Arkana triage — 2026-04-22T20:00:00Z

Classification: bug (UX/DX)

Summary: The make build-cli target invokes pkg/ark-cli/scripts/build which does a pushd into $PARENT_PATH (i.e. pkg/ark-cli/) before building, then prints Build complete: build/ark-$GOOS-$GOARCH. That path is relative to pkg/ark-cli/, not the repo root — so the printed path does not match where a user running make build-cli from the root would look.

Relevant code:

• pkg/ark-cli/scripts/build line 30: echo "Build complete: build/ark-$GOOS-$GOARCH" — printed after pushd $PARENT_PATH; $PARENT_PATH is resolved to the pkg/ark-cli/ directory.
• Makefile lines 36–38: build-cli target calls bash ./pkg/ark-cli/scripts/build from repo root.

Fix: Change the echo in the build script to print the repo-root-relative path:

# After pushd $PARENT_PATH, get the path relative to where make was invoked
echo "Build complete: pkg/ark-cli/build/ark-$GOOS-$GOARCH"

Or capture the original $PWD before pushd and print a relative path from there.

Protocol-critical: No. This is a DX/messaging issue only — no protocol logic affected.

Triaged by Arkana issue-triage agent