Expand Peated CLI into an API-backed tool for agent-assisted data fixes and backfills

Summary

We should expand the existing CLI into a Peated CLI that can be used by humans and agents to backfill and repair data without needing direct server or DB access.

Goals

• Map CLI commands onto existing API/oRPC endpoints wherever possible.
• Make batch and agent workflows easier for backfills, one-off fixes, and data cleanup.
• Add an auth flow for CLI usage via an API token instead of direct app internals.
• Reuse the existing access-token pattern where possible, likely similar to how iOS authenticates today.

Scope

• Audit the current endpoints that already support data maintenance workflows.
• Add command groups around the highest-value operations instead of bespoke server-only logic.
• Support generating, storing, and using a bearer token from the CLI.
• Prefer thin wrappers over existing endpoints so CLI behavior stays aligned with the app.

Open Questions

• Should this build on the current apps/cli package or ship as a separate user-facing CLI package?
• Do we want personal-access-token style auth, or a login flow that exchanges for an access token?
• Which commands should be first-class in v1: bottles, entities, prices, reviews, tastings, or something else?

Success Criteria

• A contributor or agent can authenticate from the CLI.
• Common backfill and repair workflows can run through existing endpoints.
• CLI output is predictable and scriptable enough for automation.

Start in the existing apps/cli package and audit the API/oRPC endpoints that support data maintenance workflows. Compare the possible CLI authentication approaches with the existing iOS access-token pattern, then resolve which command group and package direction should be first. Done means the scope, auth flow, initial commands, and scriptable output behavior are agreed and implemented.