Skip to content

Commit 0b5262d

Browse files
V48 Gate 3 (specification-only): correct the staging-testnet Supabase project map (three projects)
The earlier two-project model mislabeled mwugicjpxmrtctvjghjg as staging-testnet. Corrected (Garrett, 2026-07-06): staging-testnet = tkpyosihuouusyaxtbau (the live custom:bitcode-bitcoin wallet auth provider is here), local-testnet = mwugicjpxmrtctvjghjg (where the 2026-07-05 migrations + asset-pack bucket actually landed), production-mainnet = rinalyjfecxnmyczrpzo. Records that local Gate-3 deposit QA develops against tkpyosihuouusyaxtbau, that its schema is behind the current branch (has the OTF table, no asset-pack bucket), and that the Vercel production env's SUPABASE_URL currently points at the local-testnet project and must be corrected for mainnet. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent 6e4ea4f commit 0b5262d

1 file changed

Lines changed: 39 additions & 26 deletions

File tree

BITCODE_V48_QA.md

Lines changed: 39 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -7,32 +7,45 @@
77
- Posture: interactive local experiential QA of the first live commercial (testnet) experience; app runs locally (`pnpm -C uapi dev:remote`) against the staging Supabase project; wallet network testnet4
88
- Source-safety posture: source-safe evidence only; no secrets, protected source, provider payloads, wallet material, service-role keys, database credentials, or raw private prompts are serialized here.
99

10-
## Environments (decided 2026-07-05)
11-
12-
TWO deployed environments plus local:
13-
14-
- **production-mainnet** — bitcode.exchange + the original Supabase project;
15-
GitHub App `bitcode-github-auxillary`
16-
(https://github.com/apps/bitcode-github-auxillary — renamed 2026-07-05 from
17-
`bitcode-github-app-auxillary`; the code fallback
18-
`BITCODE_GITHUB_APP_PUBLIC_URL` names this app); mainnet posture.
19-
**Production == staging FOR NOW (Garrett, 2026-07-05):** the Vercel
20-
production environment is configured AS staging-testnet entirely — the full
21-
staging matrix (staging Supabase project, testnet4 network, stag-test GitHub
22-
App + public URL, shared wallet-OAuth secret) was pushed to BOTH
23-
`staginglocal-testnet` and `production` targets. The mainnet matrix returns
24-
at mainnet relaunch; until then bitcode.exchange serves the testnet posture.
25-
- **staging-testnet** — THE single non-production clone (Vercel custom
26-
environment `staginglocal-testnet` with domain `testnet.bitcode.exchange`,
27-
Supabase project `mwugicjpxmrtctvjghjg`, GitHub App
28-
`bitcode-github-auxillary-stag-test`, app id 4224019); testnet4 posture.
29-
- **local** — develops AGAINST staging-testnet as much as possible
30-
(`localhost:3000` for every browser-facing hop; `testnet.bitcode.exchange`
31-
only for flows requiring hosting, e.g. Supabase-cloud-reachable OAuth
32-
endpoints). Vercel allows one custom environment, so
33-
`staginglocal-testnet` serves both postures; a separate local-testnet
34-
Supabase project is DEFERRED — local points at the staging-testnet
35-
project for now.
10+
## Environments (project map corrected 2026-07-06)
11+
12+
**THREE Supabase projects (Garrett, 2026-07-06 — supersedes the earlier
13+
two-project model that mislabeled `mwugicjpxmrtctvjghjg` as staging-testnet):**
14+
15+
- **staging-testnet** — Supabase **`tkpyosihuouusyaxtbau`**; the LIVE
16+
`custom:bitcode-bitcoin` wallet auth provider is configured here (authorize →
17+
302). Its provider OAuth endpoints point at `bitcode.exchange`
18+
(Authorization/Token/Userinfo/JWKS). Schema is BEHIND the current branch: it
19+
has the full execution + BTD-ledger schema (59 tables — `executions`,
20+
`user_connections`, `vcs_repositories`, `btd_*`) but still carries
21+
`deliverable_pipeline_otf_instructions` (Gate 3 drops it), has no `profiles`
22+
table, and has no `asset-pack-artifacts` bucket — the current migrations must
23+
be applied to it (needs its DB password + `supabase link`).
24+
- **local-testnet** — Supabase **`mwugicjpxmrtctvjghjg`** (created 2026-07-05).
25+
This is where the 2026-07-05 bring-up actually landed: all 10 current
26+
migrations + the `asset-pack-artifacts` bucket. (The bring-up notes below
27+
that say "staging-testnet = mwugicjpxmrtctvjghjg" are the OLD mislabel —
28+
read them as local-testnet.)
29+
- **production-mainnet** — Supabase **`rinalyjfecxnmyczrpzo`** + the
30+
`bitcode.exchange` / `www.bitcode.exchange` domains; GitHub App
31+
`bitcode-github-auxillary` (the `BITCODE_GITHUB_APP_PUBLIC_URL` code
32+
fallback names this app); mainnet posture. NOTE: the 2026-07-05
33+
"production == staging" Vercel push pointed the `production` env's
34+
`SUPABASE_URL` at `mwugicjpxmrtctvjghjg` (local-testnet) — that must be
35+
corrected to `rinalyjfecxnmyczrpzo` when mainnet returns.
36+
37+
- **local** — for Gate-3 deposit QA, `localhost:3000` develops AGAINST
38+
**staging-testnet (`tkpyosihuouusyaxtbau`)** so the wallet auth provider is
39+
available; browser-facing hops stay on `localhost:3000`, and the wallet
40+
OAuth server endpoints resolve through `www.bitcode.exchange` (the provider's
41+
`bitcode.exchange` URLs 307→www, method-preserving). `uapi/.env.local` was
42+
repointed to `tkpyosihuouusyaxtbau` on 2026-07-06 (Supabase URL + anon /
43+
service / publishable / secret keys synced from `uapi/.env.local.remote`;
44+
`SUPABASE_JWT_SECRET` left as its placeholder — vestigial, no app code reads
45+
it), the stag-test GitHub App creds (`GITHUB_APP_ID=4224019`, base64 private
46+
key, `GITHUB_APP_CLIENT_ID/SECRET`), `NEXT_PUBLIC_GITHUB_APP_PUBLIC_URL` =
47+
the stag-test app, and `NEXT_PUBLIC_BITCODE_BITCOIN_NETWORK=testnet4`.
48+
`.env.local.bak.*` backups retain the prior state.
3649

3750
Bring-up state (2026-07-05): all 10 migrations applied to
3851
`mwugicjpxmrtctvjghjg` (schema + asset-pack-artifacts bucket verified live);

0 commit comments

Comments
 (0)