[Gemini] 5.5: Push changes upstream to seren-replicator

[taariq]

Parent: #28

Workflow Instructions for Gemini

Repo: seren-replicator (/Users/taariqlewis/Projects/Seren_Projects/seren-replicator)

When to Start: After ALL other Phase 5 tasks are complete (#42, #43, #44, #45)

Dependencies: #45 (all Phase 5 Codex and Gemini tasks must be done first)

---

Task

Push all database-replicator changes upstream to seren-replicator repo.

What to Do

1. Copy changed files from database-replicator

# From database-replicator, copy relevant changed files
cp /Users/taariqlewis/Projects/Seren_Projects/database-replicator/src/remote/models.rs \
   /Users/taariqlewis/Projects/Seren_Projects/seren-replicator/src/remote/models.rs

# Copy any other shared files that changed

2. Verify seren-replicator builds and passes tests

cd /Users/taariqlewis/Projects/Seren_Projects/seren-replicator
cargo fmt
cargo clippy --all-targets --all-features -- -D warnings
cargo test

3. Commit and push

git add -A
git commit -m "feat: Sync API-key flow changes from database-replicator"
git push

Files to Sync

• src/remote/models.rs - JobSpec changes (required)
• Any other shared modules that changed during Phase 5

Verification

• Both repos should build without errors
• All tests should pass in both repos
• Lambda handler and worker script changes should be ready for deployment

Commit Message

feat: Sync API-key flow changes from database-replicator

[taariq]

Pushed the Phase 5 changes upstream in seren-replicator (branch api-key-sync, PR #202). The repo now has the updated JobSpec, Lambda validation, and worker logic synced from database-replicator, with cargo fmt/clippy/test passing.