Wipe data and reset jams

Answer

There are three ways to start over, a jam reset, a brand reset and a full flush, plus a deletion for a data request; this page says what each removes, what it never touches and which tool to run now that both sites keep their records in Postgres.

Today

What each one does

• Both brand tools are dry runs until --yes, and print every row, workspace, job and file they would remove. brew/db/brand-wipe.js:2, 135-149, 218
• Both refuse while a job for the brand is running. brew/db/brand-wipe.js:219
• tools/reset-brand.sh and tools/flush-live.sh now exit 3 unless STORAGE=gcs, and print the brew-ops commands instead. brew/tools/reset-brand.sh:11-19; brew/tools/flush-live.sh:17-26
• There is no Postgres full flush. A flush is a brand reset per slug. brew/tools/flush-live.sh:21; brew/docs/production.md:73-77
• The brand reset does not touch the treg and Apify cache or made media, which the "wipe data" steps also clear. brew/db/reset-brand.mjs:5-6; memory brew-wipe-data

How a reset stops the live instance writing back

• The live instance holds jams and workspaces in memory and flushes them, so editing records alone gets overwritten. memory brew-jam-reset
• A stop marker in control/live.json with a wipe list makes every instance of the live revision exit; a fresh one never reads, writes or builds those brands. A second marker with an empty list ends the hide. brew/retire.js:1-9
• On Postgres the marker is a row. The brand tools write it themselves, which is why staging needs --rev-n <n>. brew/retire.js:29-30; brew/db/brand-wipe.js:220-225
• Production sets RETIRE_OFF=1, so there is no marker: the tool removes, waits and sweeps three times for anything an instance wrote back, then verifies. brew/tools/prod-env.sh:9; brew/db/brand-wipe.js:228-234; brew/docs/production.md:95-96

Who may be reset or deleted

• The five design partners, Arata, Nutrova, Mana, PUMA India and Scrubroom, are refused in code unless --partner-override --confirm-slug <slug> is given. Only if the partner asked. brew/db/brand-wipe.js:28-30; memory brew-live-stores
• A brand in PROTECTED_CONNECTIONS, Arata by default, is never deleted by the tool. A reset keeps its connections. brew/db/brand-wipe.js:27; brew/connectors/protected.js:3
• Risky tests run on Cozy Snugglet or Zenant. memory brew-live-stores
• Tests cover a dry run, the partner refusal, a reset that leaves every connection as it was, the stop marker, a deletion with its audit row, and the bucket era scripts refusing. brew/test/brand-wipe-pg.test.js:46-142

Where it runs

• Staging: brew-ops, with the code on origin/main once this deploy lands. brew/docs/production.md:83-93; deploy state 26 Oct
• Production: no brew-prod-ops job yet, and the data_deletions table arrives with the next promote. brew/docs/production.md:95-106; deploy state 26 Oct

Tomorrow

How we do it

Jam reset on staging

1. Find the live revision number n, from the name shopos-feed-<n>-xxx.
2. Run:

gcloud run jobs execute brew-ops --region=asia-south1 --args=db/reset-jams.mjs,--all,--rev-n,<n> --wait
gcloud run jobs execute brew-ops --region=asia-south1 --args=db/reset-jams.mjs,--slug,<slug>,--rev-n,<n> --wait

3. Check with db/status.mjs through brew-ops that Arata's connections still read.

memory brew-jam-reset brew/db/reset-jams.mjs:3

"Wipe data" on a test brand

When Param says "wipe data", every step runs, without asking. memory brew-wipe-data

1. /api/ops/busy on staging is 0.

2. Dry run the brand reset and read every line:

   gcloud run jobs execute brew-ops --region=asia-south1 --args=db/reset-brand.mjs,--slug,<slug> --wait
   

3. Run it, with n from shopos-feed-<n>-xxx. It hides the brand, removes it, sweeps three times and lifts the hide. Repeat for old or misspelt slugs.

   gcloud run jobs execute brew-ops --region=asia-south1 --args=db/reset-brand.mjs,--slug,<slug>,--rev-n,<n>,--yes --wait
   

4. The treg and Apify cache, made media and saved video reads have no Postgres tool yet; stop and ask Param before touching them.

5. Verify: the run ends with VERIFY: <slug> holds nothing to reset any more and the kept connection rows unchanged; landing 200, busy 0.

6. Tell Param to test in a private window; the browser remembers onboarding per brand.

brew/docs/production.md:83-93; brew/db/brand-wipe.js:234-235

A data request

Follow data requests, 12.9. The tool is db/delete-brand.mjs, dry run first.

Numbers

Open

1. May a brand reset run on production? The code allows it, with no archive. Proposal: no; production runs only db/delete-brand.mjs for a data request.
2. What clears the cache and made media on Postgres? Proposal: add it to db/reset-brand.mjs behind a --with-cache flag, so "wipe data" is one job.