Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›DevOps›DevOps Foundation·35 in this wave

Approve: DevOps FoundationTo do · blocker NEEDS MATTHEW: staging STRIPE_WEBHOOK_SIGNING_SECRETBlocked · blocker main is RED — 8 unit tests failing on origin/main, so pnpm verify cannot gate any PRDone · blocker The production account's data is 42 days stale — Analytics renders empty at any default windowBlocked · blocker MATTHEW: add db_url to the 1Password Supabase item — two RLS audits have never been runnableDone · blocker Wire apps/api test suite into CIDone Wire Playwright specs into CIDone Wire verify:swift-parity into CIDone Enable branch protection on mainBlocked Verify the staging environment is actually liveDone Web deploy workflow (manual trigger only)To do API deploy workflow (manual trigger only)To do Add post-deploy smoke test to the deploy workflowsTo do Write the rollback procedureTo do Add Sentry to iOSTo do Add Sentry to AndroidTo do Configure uptime monitoringTo do Set the three missing staging secrets on tactile-api-stagingDone Playwright is failing on main and producing no report — every run that gets a runner failsTo do Playwright job must free port 3000 BEFORE its first suite — a watchdog-killed job leaks its server and fails every later runDone Add CHANGELOG.mdTo do Automate release tagging on mainTo do Fix stale Vercel references in the observability runbookDone Add apps/api typecheck to CIDone Clean the SAST baselineTo do Flip SAST to blockingTo do Edge function deploy workflow (manual trigger only)To do Supabase migration check in CITo do Write the release procedureTo do Configure Supabase log drainTo do Centralize Cloudflare Workers logsTo do Replace console.* with structured logging in apps/apiTo do Two runners share one ~/.gradle — scope it per runner without losing the warm cacheTo do MATTHEW: CI capacity — one Mac, two runners, and a full Xcode build now runs on every pushTo do Auto-cancel queued CI runs whose head branch was deletedTo do

Wave

DevOps Foundation

Unblocked now — nothing waits on the surfaces. Wiring existing tests into CI, deploy automation, base observability.

TacTile › Launch TacTile › DevOps › DevOps Foundation

10/35 done25 open3 open blockers

Selected taskclear

Two runners share one ~/.gradle — scope it per runner without losing the warm cache

To doOwner · ait_e7bfca45

No dependencies in this wave — nothing gates it, and nothing waits on it.

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Two runners share one ~/.gradle — scope it per runner without losing the warm cache** · to do

Where it sits: TacTile › Launch TacTile › DevOps › DevOps Foundation

## The brief on file

Filed 2026-08-15. The round-24 Android session raised this as a scope question and DECLINED to do it, correctly — the cost was unmeasured. This row records the answer and the option neither of us had at the time.

THE HAZARD: the self-hosted runners plus Matthew's interactive shell all share one `~/.gradle`. That is exactly the shape #461 fixed for pnpm, where `pnpm/action-setup` defaulted to a single `~/setup-pnpm` and a run died on `ENOTEMPTY` cleaning the previous run's tree. Two Gradle daemons mutating one home concurrently is the same class of bug.

WHY IT IS LESS URGENT THAN IT LOOKED, measured 2026-08-15 AFTER #470 landed:
  · `~/.gradle/caches/build-cache-1` is **85 MB**, not the 4.4 GB reported mid-round. #470 stopped `gradle/actions/setup-gradle` writing its own cache on a self-hosted runner, which is what had inflated it.
  · Disk is 2.6 TB free of 3.6 TB.
  · Runner count went 3 → 2 the same day (three concurrent monorepo jobs saturated a 10-core M1 Max — load 235), so the collision window is smaller.
So this is now a CORRECTNESS question, not a capacity one.

THE OPTION NEITHER OF US NAMED. The session considered exactly two and rejected both, rightly:
  (a) leave it shared — the hazard above;
  (b) `GRADLE_USER_HOME=${{ runner.temp }}/gradle` — `runner.temp` is WIPED between runs, turning a ~50-second job into a full cold dependency resolution every time. Unmeasured cost, plausibly minutes.
The third option is a PERSISTENT PER-RUNNER home: `GRADLE_USER_HOME=$HOME/.gradle-$RUNNER_NAME` (or any stable path keyed on the runner). Isolation without the cold start, because it survives between runs. That is what #461 actually did for pnpm — the fix there was not "use a temp dir", it was "stop sharing one mutable path across runners".

BEFORE DOING IT, MEASURE — the session was right that this needs numbers, not reasoning:
  1. Time `:app:testDebugUnitTest` warm on the shared home (baseline; ~31s for the tier per scripts/verify/android-unit-tests.sh).
  2. Time the same with a fresh `GRADLE_USER_HOME` — that is the worst case the per-runner home pays ONCE per runner, not per run.
  3. Disk: one home per runner roughly doubles it. At 85 MB of build cache that is nothing; re-measure before assuming.
State both numbers in the PR. If the cold-start cost is large, the per-runner home still wins because it is paid once, but say so with the figure rather than asserting it.

DO NOT use `runner.temp`. Do not add a cleanup step that races the other runner.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

DevOps Foundation

Two runners share one ~/.gradle — scope it per runner without losing the warm cache