rollout-readiness-reviewlisted
Install: claude install-skill tstapler/stapler-squad
# Rollout Readiness Review
This repo's rollout flags (`config.TymuxFeatureFlag`, `StreamHubFeatureFlag`,
`NativeWorktreeFeatureFlag`, `NativeMergeFeatureFlag` — `config/config.go`) all
share one shape: a `config.FeatureFlags` entry, an `Effective<X>Enabled(cfg)`
reader, `Set<X>GlobalOverride`/`Set<X>SessionOverride` config methods, a
`<X>RolloutService` RPC (`server/services/`), and a `<X>RolloutPanel` in
`web-app/src/components/settings/`. A code read of this plumbing tells you
what's *supposed* to happen. It does not tell you what actually happens —
this review's Step 4 found a production-blocking bug (BUG-106) that six
passing test suites and a clean `go build` both missed, because the bug only
existed at the boundary between stapler-squad and a real spawned `tymuxd`
process, which no unit test exercises.
Don't skip straight to "run the tests and call it GO." Each step below found
something the previous one didn't, on the one review this skill is written
from (`tymux`, 2026-09-12).
## Step 1 — Inventory
Find every piece for the flag under review, mirroring an existing one if the
shape is unclear:
```bash
grep -n "func Effective.*Enabled\|FeatureFlag = \"" config/config.go
rg -l "<Flag>RolloutService" server/services/
rg -n "<Flag>RolloutServiceGetRolloutStatusProcedure\|Procedure = " gen/proto/go/session/v1/sessionv1connect/*.go # RPC paths (needs `make build`/proto-gen to exist locally)
find web-app/src/components/settings -iname "*<Flag>*"
find project_plans -ipat