feat: log parent snapshot and clone names from sticky disk response

[pbardea]

Summary

Log parent snapshot name and clone name from sticky disk response

This PR adds logging for the parent_snapshot_name and clone_name fields that are now returned from the getStickyDisk gRPC call (added in https://github.com/FastActions/fa/pull/2361).

Changes

• Updated getStickyDisk return type to include parent_snapshot_name and clone_name
• Extract these fields from the gRPC response
• Log both values in setupStickyDisk when the disk is first obtained

This will help with debugging and understanding which snapshot and clone are being used for each build.

Example output

Sticky disk parent snapshot: snapshot-abc123
Sticky disk clone name: clone-xyz789

🤖 Generated with Claude Code

---

Note

Log parent_snapshot_name and clone_name from sticky disk response; extend getStickyDisk return type; update buf agent dependencies and add update-proto script.

• Setup/Sticky Disk:
  • Extend getStickyDisk return to include parent_snapshot_name and clone_name and map them from the gRPC response in src/setup_builder.ts.
  • Log both values when obtaining the sticky disk in startAndConfigureBuildkitd.
• Tooling/Deps:
  • Bump @buf/blacksmith_vm-agent.bufbuild_es to 1.9.0-20251006151057-c11382a97f51.2 and @buf/blacksmith_vm-agent.connectrpc_es to 1.6.1-20251006151057-c11382a97f51.2.
  • Add package.json script update-proto for updating these packages.
  • Update pnpm-lock.yaml accordingly.

^{Written by Cursor Bugbot for commit bedba08. This will update automatically on new commits. Configure here.}

[pbardea]

Example run: https://github.com/useblacksmith/web/actions/runs/18416452281/job/52484105494?pr=2386