jb/eden
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: isolate anonymous rollout rate limits

Browse Source
This commit is contained in:
jb
2026-09-19 10:01:23 -04:00
parent 01b8b4642b
commit 6af610d9ce
6 changed files with 38 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/restore-rehearsal.md
+8 -15
View File
@@ -132,17 +132,11 @@ allocated loopback ports. Do not use a production callback or provider key.
configuration against the restored instance using this same in-memory key
is the credential continuity check.
3. Run the existing synthetic write smoke against this backend, with
`SMOKE_ALLOW_WRITE=1`, and record its output without recording secrets. It
exercises login/session, staged publication, failed publication preserving
the previous generation, tenant isolation, JWT audience checks, and local
revocation:
```sh
SMOKE_ALLOW_WRITE=1 CONVEX_SELF_HOSTED_URL="http://127.0.0.1:$CONVEX_PORT" \
bun "$repo/scripts/smoke-convex.ts" | tee "$work/convex-smoke.log"
```
3. The legacy `scripts/smoke-convex.ts` exercises useful synthetic writes,
but currently accepts an arbitrary `CONVEX_SELF_HOSTED_URL` when write is
enabled. Do **not** execute it as part of this runbook; it remains
unexecuted evidence until it is wrapped with the same loopback target,
explicit disposable confirmation, and key scoping as the marker tool.
Then write a deterministic marker that can be looked up after restore. Use
a fresh marker and synthetic character ID for every rehearsal; do not use a
random-only smoke result as proof of record survival:
@@ -217,8 +211,9 @@ allocated loopback ports. Do not use a production callback or provider key.
bun "$repo/scripts/configure-convex.ts" >/dev/null
```
3. Verify the deterministic marker before running any fresh smoke, then run
the synthetic Convex smoke with fresh IDs:
3. Verify the deterministic marker before any other restore evidence. The
legacy synthetic Convex smoke remains unexecuted for the safety reason
above; do not substitute its arbitrary-target behavior for restore proof:
```sh
RESTORE_MARKER="$RESTORE_MARKER" \
@@ -226,8 +221,6 @@ allocated loopback ports. Do not use a production callback or provider key.
RESTORE_MARKER_SESSION_EXPIRES_AT="$RESTORE_MARKER_SESSION_EXPIRES_AT" \
CONVEX_SELF_HOSTED_URL="http://127.0.0.1:$CONVEX_PORT" \
RESTORE_MARKER_PHASE=verify bun "$repo/scripts/smoke-restore-marker.ts"
SMOKE_ALLOW_WRITE=1 CONVEX_SELF_HOSTED_URL="http://127.0.0.1:$CONVEX_PORT" \
bun "$repo/scripts/smoke-convex.ts" | tee "$work/convex-restore-smoke.log"
```
Verify: