chore: bump goose backend pin to 616cdce9

[kalvinnchau]

Category: infrastructure
User Impact: Berd's bundled Goose backend now builds from upstream commit 616cdce9898b79b8b9eae601b005d2e11bf4e0b7.

Problem: The pinned Goose backend in goose-backend.lock.json pointed at an older upstream commit, so dev runs and release bundles kept using stale backend behavior.

Solution: Resolved the requested SHA against the aaif-goose upstream repo via scripts/update-goose-backend-lock.sh and repinned goose-backend.lock.json to it. This lock controls the default backend used by just setup, just dev, and just bundle.

File changes

goose-backend.lock.json
Updated ref and commit to pin the Goose backend at 616cdce9898b79b8b9eae601b005d2e11bf4e0b7 (resolved directly from the SHA, so ref equals the commit).

[morgmart]

🤖 Automated code review

APPROVE. The exact three-dot comparison only updates the supported Goose backend lock to one immutable upstream commit. No publishable changed-line findings remain. Supplied GitHub check evidence is structurally valid; required checks still govern merge readiness.

Deterministic publication result: 0 blocking and 0 non-blocking inline finding(s) publishable; 0 duplicate(s) suppressed; 0 blocking screenshot-evidence requirement(s) in this review body.

Pending checks: 3 check(s) are not complete.

This approval reflects the completed code review only; merge readiness remains governed by the repository's required checks.