diff --git a/0059/SESSION-0059.0-TRANSCRIPT-2026-06-01T08-00--2026-06-01T08-21.md b/0059/SESSION-0059.0-TRANSCRIPT-2026-06-01T08-00--2026-06-01T10-16.md similarity index 58% rename from 0059/SESSION-0059.0-TRANSCRIPT-2026-06-01T08-00--2026-06-01T08-21.md rename to 0059/SESSION-0059.0-TRANSCRIPT-2026-06-01T08-00--2026-06-01T10-16.md index 4619742..01b54d6 100644 --- a/0059/SESSION-0059.0-TRANSCRIPT-2026-06-01T08-00--2026-06-01T08-21.md +++ b/0059/SESSION-0059.0-TRANSCRIPT-2026-06-01T08-00--2026-06-01T10-16.md @@ -7,9 +7,10 @@ > > Outcome: **Shipped rfc-app v0.31.4 (CSS-only patch) fixing invisible > light-surface `.btn-link` buttons + harmonizing the RFC breadcrumb -> action bar, and bumped the OHM pin to 0.31.4. Both PRs MERGED to main -> (rfc-app #5, ohm-rfc #9), `v0.31.4` tagged on the rfc-app merge commit. -> Remaining: rebuild + deploy the OHM frontend against 0.31.4.** +> action bar; bumped the OHM pin to 0.31.4; merged + tagged + **deployed +> live** to ohm.wiggleverse.org and verified the fix in the served CSS. +> Also corrected the stale `rfc-app/deploy/` docs after discovering the +> GCP name-alignment drift (PR #6). Nothing left blocking.** > > Highlights: > - Root-cause, not whack-a-mole: the "missing buttons" were @@ -117,20 +118,54 @@ afterward (ohm-rfc left clean). `npm run build` clean. 307-redirects to `ben.stull` (a Gitea rename) — use `ben.stull/...` since the script's curl doesn't follow redirects. +### Arc 6 — Deploy to live OHM + deploy-doc correction + +Operator: "you do it" (the deploy). The `rfc-app/deploy/` docs turned out +to be **stale** — they name project `wiggleverse-rfc` / VM `rfc-app` / IP +`34.132.29.41` / path `/opt/rfc-app`, none of which exist post the GCP +name-alignment. Discovery path: `wiggleverse-rfc` "project not found" → +listed projects → the live project is `wiggleverse-ohm`, VM `ohm-rfc-app`, +IP `136.116.40.66`; direct SSH port 22 timed out → **IAP-only** +(`--tunnel-through-iap`). Probed the box: install `/opt/ohm-rfc-app`, +service `ohm-rfc-app.service` (running), user `ohm-rfc-app`, meta repo +`wiggleverse/ohm-content`. + +Critically, the VM's git origin is **`git.benstull.org/benstull/rfc-app`** +— a *separate* Gitea from the release one (`git.wiggleverse.org`) that +does not auto-mirror. `git ls-remote benstull v0.31.4` was empty, so the +VM couldn't see the release. Pushed `main` + tag `v0.31.4` to the +`benstull` remote (fast-forward), then on the VM: `git fetch --tags` → +`git checkout v0.31.4` (the box tracks a detached tag) → `npm ci && npm +run build` (Node 20 on the box) → `systemctl restart ohm-rfc-app`. + +Verified: backend startup `RFC app started — meta repo +wiggleverse/ohm-content`; `https://ohm.wiggleverse.org` returns 200 from +`136.116.40.66` serving the new bundle (`index-B2Q74zqG.css`); the public +CSS carries the fix (`.btn-link{…border:1px solid var(--c-gray-300)…}` +and `.app-header .btn-link{…}`). + +Then corrected `deploy/DEPLOY-NEW-SESSION-PROMPT.md` + +`deploy/RUNBOOK.md` (new names, IAP, two-remote, tag-checkout, +meta-repo) as a docs-only change — branch `docs/deploy-infra-realignment`, +commit `714c2ae`, PR **#6**, merged (`0062510`). No version bump (docs +precedent: the docs-only commit after v0.31.3). + --- ## Cut state (end of session) | | | | --- | --- | -| rfc-app | PR #5 MERGED to main @ `551d240`; release commit `76c82a5`; tag `v0.31.4` on the merge commit. VERSION 0.31.4. Branch deleted. | -| ohm-rfc | PR #9 MERGED to main @ `10836c0`; commit `ee5b90b`. pin 0.31.4. Branch deleted. | -| OHM live | unchanged this session; still running pre-0.31.4 (deploy pending). | +| rfc-app | PR #5 MERGED @ `551d240` (tag `v0.31.4`); docs PR #6 MERGED @ `0062510`. main tip `0062510`. VERSION 0.31.4. | +| ohm-rfc | PR #9 MERGED to main @ `10836c0`; commit `ee5b90b`. pin 0.31.4. | +| OHM live | **0.31.4 DEPLOYED** on VM `ohm-rfc-app` (project `wiggleverse-ohm`); `ohm-rfc-app.service` active; `https://ohm.wiggleverse.org` 200, fix confirmed in served CSS. | +| benstull remote | `git.benstull.org/benstull/rfc-app` main + tag `v0.31.4` pushed (VM deploy source). | | ohm-rfc pin (main) | 0.31.4 | | Ledger | Status | | --- | --- | -| Button UX: invisible light-surface `.btn-link` + breadcrumb polish (rfc-app v0.31.4) | ✅ shipped (merged + tagged) — only the OHM frontend rebuild/deploy remains | +| Button UX: invisible light-surface `.btn-link` + breadcrumb polish (rfc-app v0.31.4) | ✅ **shipped + deployed** — live on ohm.wiggleverse.org | +| Deploy-doc correction (GCP name-alignment drift) | ✅ shipped (rfc-app PR #6) | --- @@ -146,17 +181,27 @@ afterward (ohm-rfc left clean). `npm run build` clean. Every push this session went via an explicit SSH URL. Worth either switching origin to SSH or storing a credential, so future sessions don't rediscover this. +3. **Two-Gitea drift (deploy source ≠ release source).** Releases land + on `git.wiggleverse.org` (`ben.stull/rfc-app`), but the live VM + deploys from `git.benstull.org/benstull/rfc-app`, which does not + auto-mirror — every deploy needs a manual `git push benstull main + ` first. Wiring the two instances to mirror (or repointing the + VM origin at the release Gitea) would remove a footgun. Documented in + the deploy docs for now (PR #6); the mirror itself is unbuilt. --- ## What lands on the operator's plate -1. ~~Merge rfc-app PR #5 + tag `v0.31.4`.~~ Done this session - (merge `551d240`, tag on the merge commit). -2. ~~Merge ohm-rfc PR #9.~~ Done this session (merge `10836c0`). -3. **Rebuild the OHM deployment's frontend against 0.31.4 and ship** — - plain code deploy, no env/config/migration. This is the only - remaining gesture. +Everything this session set out to do is done — merged, tagged, +**deployed**, and the deploy docs corrected. Nothing is blocking. + +Optional follow-ups (not blocking): +1. ~~Merge PRs #5/#9, tag, deploy.~~ Done this session. +2. **Wire the two Gitea instances to mirror** (§19.2 #3) so deploys stop + needing a manual `git push benstull`. Or repoint the VM's origin at + `git.wiggleverse.org`. +3. Consider a real button vocabulary (§19.2 #1) on the next UI pass. --- @@ -164,22 +209,26 @@ afterward (ohm-rfc left clean). `npm run build` clean. ``` You reserve your own session ID (claim-session-id.sh). Context: the -prior session (0059) fixed a button-UX bug in rfc-app and shipped it as -v0.31.4 (CSS-only patch in frontend/src/App.css): the .btn-link class -was a dark-header style reused on light surfaces, so secondary buttons -(Metadata / Claim ownership / Invitations on the RFC breadcrumb) were -rendering white-on-white and looked missing; the breadcrumb action bar -was also harmonized + made to wrap. Both PRs are MERGED to -main (rfc-app #5 @ merge 551d240, tag v0.31.4 on the merge commit; -ohm-rfc #9 @ merge 10836c0, .rfc-app-version now 0.31.4 on main). The -ONLY remaining gesture is to rebuild + deploy the OHM frontend against -0.31.4 — plain code deploy, no env/config/migration. +prior session (0059) fixed a button-UX bug in rfc-app, shipped it as +v0.31.4 (CSS-only patch in frontend/src/App.css), and DEPLOYED it live +to ohm.wiggleverse.org — done, nothing pending. The bug: .btn-link was a +dark-header style reused on light surfaces, so secondary buttons +(Metadata / Claim ownership / Invitations on the RFC breadcrumb) +rendered white-on-white and looked missing; the breadcrumb action bar +was also harmonized + made to wrap. rfc-app PR #5 @ merge 551d240 (tag +v0.31.4); ohm-rfc pin #9 @ merge 10836c0; deploy-doc fix PR #6 @ 0062510. -If you're picking this up: do that deploy and confirm the breadcrumb -action bar renders the secondary buttons (Metadata / Claim ownership / -Invitations) legibly on the live site. (rfc-app origin is https with no -non-interactive credential — push via +Hard-won infra facts for the next deploy (the deploy docs were stale — +now fixed in PR #6): the live VM is `ohm-rfc-app` in project +`wiggleverse-ohm`, SSH is IAP-only +(`gcloud compute ssh ohm-rfc-app --zone=us-central1-a +--project=wiggleverse-ohm --tunnel-through-iap`), install path +`/opt/ohm-rfc-app`, service `ohm-rfc-app`. The VM's git origin is a +SEPARATE Gitea (`git.benstull.org/benstull/rfc-app`) that does NOT +mirror the release Gitea (`git.wiggleverse.org`) — so push `main` + the +tag to the `benstull` remote before deploying. Releases push via ssh://git@git.wiggleverse.org:2222/ben.stull/…; PRs via -ohm-infra/scripts/rfc-authoring.sh, owner ben.stull.) Otherwise, fresh -OHM driver session. +ohm-infra/scripts/rfc-authoring.sh (owner ben.stull). Open §19.2: wire +the two Gitea instances to mirror so the manual benstull push goes away. +Otherwise, fresh OHM driver session. ```