fix: signed PDFs move to a GCS archive (consumer SAs have zero Drive quota)

[agent-refr]

AI-assisted change proposal. Filed by agent driven by @Cervator via GDD.

Summary

• The live e2e hit storageQuotaExceeded at the final Drive upload: Google grants consumer-account service accounts zero Drive storage, so an SA can never own an uploaded file or created folder, and the Workspace escape hatches (Shared Drives, delegation) don't exist here. Signed PDFs now live in the public-read GCS bucket skipta-amendments-teralivekubernetes under per-customer prefixes — keeping the zero-stored-credentials model (bucket-scoped storage.objectUser via Workload Identity).
• Idempotency contract preserved: deterministic per-amendment blob name, find-or-upload before mark_signed, honest 502s. The pdf_drive_url sheet column now carries the public object URL.
• app/drive.py removed (nothing consumes Drive anymore — the Skipta/ folder remains the human-side SoW archive); app/gcs.py replaces it with matching test fakes.
• ConfigMap/Deployment gain gcs_bucket/SKIPTA_GCS_BUCKET; design doc updated to as-built, including the public-bucket demo caveat and the promote-to-real path (private bucket + signed URLs).

Test plan

• ci green (29 tests + the CI-only WeasyPrint render; suite covers upload/marks-signed, retry-reuses-existing-blob with no re-upload, and blob naming).
• Post-merge live: re-apply k8s base + rollout restart, then re-sign draft amendment amend_smith_20260702051053 — expect the PDF at the bucket URL and the sheet row flipping signed (the draft row survived the 502 exactly as designed).

Related

• Follow-up to feat: field amendments MVP — extraction, pricing, signing, PDF to Drive #1 (MVP), which validated everything up to the Drive upload live.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 6 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2a5a7205-7e9d-4885-97c6-a8dc88851167

📥 Commits

Reviewing files that changed from the base of the PR and between 2c19df7 and dec5d04.

📒 Files selected for processing (13)

• app/config.py
• app/drive.py
• app/gcs.py
• app/google_clients.py
• app/main.py
• docs/plans/2026-07-01-skipta-field-amendments-design.md
• k8s/base/configmap.yaml
• k8s/base/deployment.yaml
• requirements.txt
• tests/conftest.py
• tests/test_drive.py
• tests/test_gcs.py
• tests/test_routes_sign.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/pdf-home-gcs

---

_{Comment @coderabbitai help to get the list of available commands.}