fix(logs): match server LogEvent body field, docs fixes (VOL-648 sub-tickets)

[swkeever]

Summary

Fixes for VOL-648 sub-tickets scoped to volcano-cli:

• VOL-636: volcano-hosting renamed LogEvent's content field from message (string) to body (oneOf string/object/array/number/boolean) in a prior release, but the vendored OpenAPI spec and generated client here were never updated — volcano cloud frontends logs/volcano functions logs streamed blank lines for every event since event.Message no longer existed in the API response. Regenerated the client from a corrected spec and updated both log-rendering call sites and the affected tests.
• VOL-645: docs/databases.md's --region example used a plain AWS region (us-east-1); the API expects Neon-style aws-<region> identifiers and 400s otherwise. Fixed the example.
• VOL-646: investigated "no CLI/API way to retrieve a project's anon key" — found this already fully shipped (volcano projects keys, PR feat(cli): add 'volcano projects keys' command to retrieve a project's anon key #86) but undocumented in the CLI overview, so a user searching under cloud wouldn't find it. Added it to docs/README.md.

VOL-640 (setup --harness/--yes mutual exclusivity) is scoped to a different in-flight ticket and not touched here — also independently already resolved on main (--agent rename, PR #146).

Ticket

VOL-648 (umbrella, cancelled as duplicate) — sub-tickets VOL-636, VOL-645, VOL-646

Todo (gates — each requires evidence)

• Ownership confirmed and ticket In Progress
• Research prior art and relevant UI/UX guidance (n/a — CLI/docs only)
• Finalize the implementation plan and acceptance checks
• Regenerate OpenAPI client for LogEvent/LogSearchEvent body field (VOL-636)
• Fix region format + surface projects keys docs (VOL-645/VOL-646)
• Add or update automated tests
• Run focused and broader local validation — commands listed under Testing
• Verify the integrated flow in a local browser, or record why not applicable
• self-review-work clean — cycles: 3, final pass no blockers
• Required CI checks passing
• Merged to default branch — commit 057dbacc
• Staging validation succeeded — see Testing (CLI has no separate "deployment"; validated by running the built binary against the live staging API)
• Staging smoke test passed — see Testing
• Jira tickets moved to Done — VOL-636, VOL-645, VOL-646

Prior Art

• internal/output/functions.go's existing pattern for other oapi-codegen oneOf union types — reused the MarshalJSON/string-unmarshal accessor pattern rather than inventing a new one.

Testing

• make openapi-generated-check
• make test (now passes cleanly, go build ./... + go vet ./... clean)
• make lint — fails on a pre-existing, unrelated issue in internal/auth/auth.go (stale //nolint:contextcheck directive now flagged as unused); reproduced on a clean origin/main checkout with none of this branch's changes, so it predates this PR. Flagged separately for its own fix.
• self-review-work: 3 cycles.
  • Round 1: the null-body case in the new table test only proved no panic — asserted nothing about the rendered output. Fixed by asserting the render doesn't contain the literal "null".
  • Round 2: no blocking findings. Two optional nits — LogEvent/LogSearchEvent render helpers' test-fixture builders still named their string param message post-rename (fixed for consistency with client_test.go's already-renamed logsResponse); extra LogSearchEvent non-string coverage suggested but skipped as low-value (shares the same bodyText helper LogEvent already covers for all variants).
  • Separately, self-caught (not a review finding): running the full go test ./... — broader than either review pass's own scope of "packages touched by the diff" — surfaced that internal/cmd/frontends, internal/cmd/functions, and internal/logfollow still built their test log fixtures with the old message field, so TestFrontendsLogs/TestFunctionsLogs silently asserted on blank rendered output, and internal/logfollow's stream tests hung indefinitely (the follow loop never observed a non-empty body to detect progress). Fixed all three files' fixtures to use body.
  • Round 3 (confirming pass after the fixture fixes and a param-naming cleanup): no blocking findings.
• Local browser: N/A (CLI-only change; verified via unit tests)
• Staging smoke test: pending merge

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Copilot]

Pull request overview

Updates log handling to match the server’s polymorphic body field and corrects database/project documentation.

Changes:

• Regenerates API log models and renders all supported body types.
• Updates log fixtures and regression tests.
• Corrects database-region guidance and documents project anon keys.

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
openapi/openapi.yaml	Defines the new log body schema.
internal/apiclient/client.gen.go	Regenerates log models and unions.
internal/output/functions.go	Renders polymorphic log bodies.
internal/output/functions_test.go	Tests body variants and null handling.
internal/logfollow/follow_test.go	Updates streaming fixtures.
internal/cmd/functions/logs_test.go	Updates function-log fixtures.
internal/cmd/frontends/logs_test.go	Updates frontend-log fixtures.
internal/api/log_stream_test.go	Verifies streamed body decoding.
internal/api/frontends_test.go	Updates frontend API assertions.
internal/api/client_test.go	Adds body extraction test support.
internal/cmd/databases/create.go	Clarifies region flag help.
docs/README.md	Documents project anon-key retrieval.
docs/databases.md	Corrects database region examples.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.