API Key Flow: Interactive SerenDB target selection

[taariq]

This is the parent tracking issue for implementing the API-key flow feature.

Overview

Allow SerenDB users to select their target project and database interactively using an API key, eliminating the need to manually construct PostgreSQL connection strings.

Implementation Plan

See docs/plans/api-key-flow-implementation.md for complete implementation details.

Child Issues

Phase 1: Foundation (Codex) - database-replicator

• [Codex] 1.1: Add SerenDB API data structures #29 - [Codex] 1.1: Add SerenDB API data structures
• [Codex] 1.2: Add list_projects API method #30 - [Codex] 1.2: Add list_projects API method
• [Codex] 1.3: Add branch listing methods #31 - [Codex] 1.3: Add branch listing methods
• [Codex] 1.4: Add database listing and creation methods #32 - [Codex] 1.4: Add database listing and creation methods
• [Codex] 1.5: Add connection string retrieval method #33 - [Codex] 1.5: Add connection string retrieval method

Phase 2: State Persistence (Gemini) - database-replicator

• [Gemini] 2.1: Create target state persistence module #34 - [Gemini] 2.1: Create target state persistence module
• [Gemini] 2.2: Create interactive project/database picker #35 - [Gemini] 2.2: Create interactive project/database picker

Phase 3: CLI Integration (Codex) - database-replicator

• [Codex] 3.1: Add target mode resolution logic #36 - [Codex] 3.1: Add target mode resolution logic
• [Codex] 3.2: Make --target optional, add --api-key global option #37 - [Codex] 3.2: Make --target optional, add --api-key global option
• [Codex] 3.3: Integrate API-key flow into init command #38 - [Codex] 3.3: Integrate API-key flow into init command
• [Codex] 3.4: Integrate API-key flow into sync command #39 - [Codex] 3.4: Integrate API-key flow into sync command

Phase 4: Testing & Documentation (Claude Review)

• [Claude] 4.1: Add SerenDB API integration tests #40 - [Claude] 4.1: Add SerenDB API integration tests
• [Claude] 4.2: Add SerenDB API key flow documentation #41 - [Claude] 4.2: Add SerenDB API key flow documentation

Phase 5: Remote Execution (Gemini) - seren-replicator

• [Gemini] 5.1: Update JobSpec with project identifiers #42 - [Gemini] 5.1: Update JobSpec with project identifiers
• [Gemini] 5.2: Update Lambda validation for project-based targets #43 - [Gemini] 5.2: Update Lambda validation for project-based targets
• [Gemini] 5.3: Update EC2 worker for project-based targets #44 - [Gemini] 5.3: Update EC2 worker for project-based targets
• [Codex] 5.4: Update CLI remote submission for API-key flow #45 - [Codex] 5.4: Update CLI remote submission for API-key flow
• [Gemini] 5.5: Push changes upstream to seren-replicator #46 - [Gemini] 5.5: Push changes upstream to seren-replicator

Task Dependencies

Phase 1 (Codex) ─────────────────────────────────────┐
  1.1 → 1.2 → 1.3 → 1.4 → 1.5                        │
                                                      ├─→ Phase 4 (Claude Review)
Phase 2 (Gemini) ────────────────────────────────────┤      4.1, 4.2
  2.1 → 2.2                                          │
                                                      │
Phase 3 (Codex) ─────────────────────────────────────┤
  (depends on Phase 1 & 2)                           │
  3.1 → 3.2 → 3.3 → 3.4                              │
                                                      │
Phase 5 (Gemini - seren-replicator) ─────────────────┘
  (depends on Phase 3)
  5.1 → 5.2 → 5.3 → 5.4 → 5.5

Agent Assignment Summary

Agent	Tasks	Repo
Codex	10 tasks (Phase 1, 3, 5.4)	database-replicator
Gemini	6 tasks (Phase 2, 5.1-5.3, 5.5)	database-replicator + seren-replicator
Claude	2 tasks (Phase 4)	database-replicator

Note: Gemini handles ALL seren-replicator (upstream) changes to keep it manageable.

Labels

• api-key-flow - All issues in this feature
• agent:codex - Tasks for Codex
• agent:gemini - Tasks for Gemini
• agent:claude-review - Tasks for Claude to review