docs: Bamboo Specs equivalent of the GitHub Actions CI/CD

[kiro-agent]

This pull request was created by @kiro-agent on behalf of @ccrsxx 👻

Comment with /kiro fix to address specific feedback or /kiro all to address everything.
_{Learn about Kiro Web}

---

Learning reference, not meant to run anywhere. Translates .github/workflows/ci.yaml + deployment.yaml into Bamboo YAML Specs.

What's here

• bamboo-specs/bamboo.yaml — 4 YAML documents: build plan (= ci.yaml), plan permissions, deployment project (= deployment.yaml), deployment permissions. Heavily commented with the GH line each block replaces.
• bamboo-specs/README.md — concept mapping table and the gotchas that don't translate.

Key mappings

• needs: -> stage boundaries. Bamboo has no per-job DAG; jobs in a stage are parallel and the stage is a hard barrier.
• job outputs: -> inject-variables with scope: RESULT, i.e. write key=value to a file. That's how extract-tools-version outputs are carried into later stages and into the deployment.
• if: always() -> final-tasks: (the Postgres teardown in the vet job).
• actions/setup-go -> either an agent capability or docker: golang:<ver>-alpine per job. No action marketplace.
• secrets.* -> plan/environment variables; sensitive keys must be committed as encrypted BAMSCRT@... blobs or the import fails.
• workflow_dispatch + inputs.sha + the image-existence check -> Bamboo releases, which give redeploy/rollback for free.

Verification

Parses as 4 valid YAML documents with the expected structure (2 stages, 4 verify jobs, 2 deployment environments). Not schema-validated against a real Bamboo server — no instance available here, so treat the field names as documented-but-unverified.

Safe to delete the branch once read.