wiggleverse/session-history
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update engineering/0016/SESSION-0016.0-TRANSCRIPT-2026-06-10T20-34--INPROGRESS.md

Browse Source
This commit is contained in:
Ben Stull
2026-06-10 20:36:13 -07:00
parent aff4b86180
commit 2863859501
1 changed files with 24 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
engineering/0016/SESSION-0016.0-TRANSCRIPT-2026-06-10T20-34--INPROGRESS.md
+24
View File
@@ -17,6 +17,30 @@ Do the gitea VM service-account scope maintenance window (stop → set-service-a
```
## Plan
> Anchor: design specs/gitea-forge-backups.md (engineering#30, graduated; D-3 / §13 Q1: operator approved the maintenance window)
Execute the gitea VM service-account scope maintenance window — the SLICE-1
unblock (spec §7.2 SLICE-1, risk R-1). Procedure is canonical in
`infra/deploy-gitea-on-gcp.md` "Backups" box:
1. Checkpoint-publish this transcript BEFORE the window (session-history lives
on the VM being stopped).
2. Pre-checks via `CLOUDSDK_ACTIVE_CONFIG_NAME=gitea` (§8.4): VM RUNNING,
record current SA (`1061347810527-compute@developer.gserviceaccount.com`)
+ scopes (`devstorage.read_only`).
3. `gcloud compute instances stop gitea --zone=us-central1-a`
4. `gcloud compute instances set-service-account gitea --zone=us-central1-a --scopes=cloud-platform`
5. `gcloud compute instances start gitea --zone=us-central1-a`
6. Verify: scopes = cloud-platform, same SA email, forge healthy
(HTTPS git.wiggleverse.org + SSH :2222), on-VM ADC write-test to
`gs://wiggleverse-gitea-backups` (proves the unblock; spec D-3).
7. Update the runbook's PENDING box (DOC-2) → branch → PR → merge.
Session runs isolated in worktree `gitea-vm-scope-window` (live concurrent
SESSION-0009 in flight).
## Deferred decisions
_Autonomous-mode low-confidence calls the driver made and would have