Revion Crew Board

Two manual drafts stood in #ach-payouts-production with no send or reconciliation after them at the 2 Sep collection: 27 Aug ($1,139.16, pay on or after 28 Aug, 9 orders) and 1 Sep 19:27Z ($358.16, settlement window 25 Aug – 1 Sep, 2 orders, “this Slack notification does not initiate a transfer”). New today from Linear: REV-150 (arm production payouts) is still [Backlog] p1 with its last update on 27 Aug — 16 days — and REV-191 (full automation) has dropped out of the open list entirely. Meanwhile the one payout commit of the last ten days is Nur’s “Fix self-contained manual payout instructions” (12 Sep, promoted the same day in #423): the tooling is being improved for the manual mode, not replaced. Slack and the prod DB have been dark since 2 Sep, so a send since then is unverified — nothing anywhere evidences one.

Next action

Hand Andrew both amounts with Halo’s approved banking (Mercury checking ••••2806) and the business address from app_R89kpf0lM4Jd5X_r for the BofA portal; record both bank references in Revion. Then make Nur say on REV-150 whether automation is still coming, or whether REV-191 was closed as “manual is the answer”.

31 Aug 15:54Z Jarrod: his accountant says a Washington business must collect WA tax on these orders. You answered 16:36Z citing agreement sections 8.5 (Revion registers, collects, remits) and 8.7 (resale certificate). 31 Aug 23:48Z: “my contract ends at section 8.4, so I never saw 8.5 or 8.7.” 1 Sep 05:57Z you conceded the text is from the master document, not the one he signed, and promised to discuss with Aadil that day — nothing in #rhp-rhpeptides by the 2 Sep collection, and Slack has been unreadable since, so any later reply is unverified. His store is live for real: RC-2026-1000243, $598, AUTHORIZED 2 Sep 05:08Z (avs=Y, cvv=M). Linear today confirms REV-190 is still [Backlog] (upd 6 Sep), so the RHP skip on the reminder sweep is still in force.

Next action

Get the executed RHP agreement from Aadil (on his list), decide addendum vs. accepting his position on WA tax, reply in-channel today — and mark the $598 while you are there. Nur’s REV-196 is the same question in Florida; answer both with one policy.

Set live + banking approved 31 Aug 15:24Z (done). At the 2 Sep read he was still registered as https://www.biopepusa.com — the www/apex shape that broke RHP’s and Kiyora’s first checkouts. Casey created a session himself 31 Aug 15:37Z ($59.00, info@biopepusa.com) which expired with no payment intent: he reached our checkout and never submitted a card — why is unverified. #biopep-usa-llc held only our team, no welcome posted. Ten days on, whether the domain got corrected or Casey retried is still unverified: the prod DB and Slack failed again in today’s 12:57Z collection.

Next action

Correct the domain to https://biopepusa.com via single-field DB update (never suspend — it wipes credentials), then email Casey directly: welcome, “run the $59 test again and we void it”, accept the Slack invite.

Banking approved 31 Aug 12:55Z; both test refunds confirmed to her and her only reply was “Thanks so much” (31 Aug–2 Sep window). Prod DB at 2 Sep 13:05Z: 0 sessions, 0 orders for mrc_zinhzQp6eyBC since 31 Aug — the ten days since are unknown (every watch-merchant read from 7 Sep onward has come back empty). Aadil (2 Sep 05:46Z): “one transaction in five days” — Andrew is counting, and this is the merchant closest to adding some.

Next action

Ask Jenifer plainly when Revion goes on as the live payment option and offer to watch the first day; no reply by tomorrow → Aadil calls (his chase task).

app_uHyTgAc1QXxFQKBW (coreresearchpeptides.com) moved received → under review 1 Sep 21:07Z and was still there at the 2 Sep 13:05Z read; the DB reads since have failed, so the current state is unverified. Approving provisions credentials + Slack automatically (Middesk gating), and Slack welcome v2 (#412, 7 Sep; pack delivery fixed 8 Sep, #415/#416) auto-posts the integration pack once the channel exists. What is new: REV-214 “Onboarding: verify callback, activate, then send portal credentials”, REV-218 “Custom merchant setup pack and callback submission before portal access” and REV-219 “Verify callbacks while inactive before first merchant activation” — all p1, all filed 11 Sep, all Nur’s. Sean is the first merchant that sequence would apply to.

Next action

Approve → descriptor → banking → welcome; then onboarding-check.sh app_uHyTgAc1QXxFQKBW before telling him “check Slack”. Decide with Nur whether Sean waits for REV-219’s callback verification or goes through by hand with you watching. The credentials email still carries the “payments disabled” line (REV-169, touched 11 Sep, still open) — correct it in-channel.

Chased 31 Aug 09:06Z with the $143.96 abandoned-session evidence; no reply by 2 Sep, and Slack has been unreadable in the five collections since. Prod DB at 2 Sep: 0 sessions for mrc_4JFn-SyBlVNP since 31 Aug. Chris last spoke 28 Aug 04:07Z.

Next action

Stop nudging in Slack — hand to Aadil for a phone call with a booked slot (cal.com/team/revion); the idle-reminder email (merged + promoted 6 Sep) lands too once Nur arms it.

Linear, first readable since 2 Sep: REV-127 “Plugin: store each order’s Revion payment link in Woo order notes + meta” is [In Progress] p2 @tim, last updated 2 Sep — ten days without an update, and one of only two tickets showing you as the active assignee (the other is REV-101, the revioncaps.com redesign, also In Progress). The companion complaint, REV-159 (payment links die after 30 minutes — Halo’s auto-sent links), sits in Nur’s conversion cluster.

Next action

Either finish it this week or hand it to Nur and say so on the ticket — an In Progress p2 with no update is what Andrew reads as “nobody is on it”.

Whether the ticket has been resolved is still unverified (no billing-inquiry rows in any bundle since 2 Sep; the prod DB failed again today). Linear does move the picture on the QA side: REV-60 “QA daily user stories — edit me” was updated 11 Sep, and the dailies are being filed again (REV-215 on 11 Sep, REV-220 today) — so the plan Narboto works from is live, and the “clean up after yourself” insert is worth landing now rather than after another week of ZZTEST leftovers. Verified at 2 Sep: the 1 Sep QA run ended US-7 + US-8 FAIL with three ZZTEST applications still “received”.

Next action

revioncaps.com/admin/billing-inquiries → Resolve, note “QA daily test — no action”. Locally: source ~/RevionCaps/creds.sh && python3 ~/RevionCaps/linear_cleanup_rev60.py (idempotent; it also comments on REV-170).

banking_approved 2 Sep 06:28Z; 0 sessions since 31 Aug at the 2 Sep read; their dev has not written since 20 Aug (“Alright, scheduled for next week”). The 31 Aug chase proposed a 20-minute call; no answer by 2 Sep, nothing readable since. New in git: “Fix embedded checkout binding with CHIPS” (#419) and “fall back when CHIPS is unavailable” (#420) both landed 10 Sep under REV-200 and were promoted the same day (#421) — the embed now binds its session with partitioned cookies and degrades instead of breaking where the browser has none. Whether that was ever the dev shop’s blocker is unverified, but it is a concrete reason to re-open the conversation.

Next action

The call is the test: Aadil books it by phone/email (contact is the dev shop, dev@guardedpaypro.com); run and void the first embedded order together, on the 10 Sep build.

Your question (2 Sep 05:46Z, “drop-off due to people not being able to check out with their chosen card brand”) has a measured answer from Tim (2 Sep 06:04Z): declines of $380 (31 Aug 11:15Z, txn 12495306934) and $361 (1 Sep 10:01Z, txn 12500637032), both card_declined, both non-Visa — “the Visa-only wall”. Every merchant is still told “Visa only for now” (Halo 20 Aug, Zen 28 Aug). The rest of the funnel was normal: 5 completions, ~65–70% cart abandonment, zero technical failures. (The 2 Sep declines on Halo were the processor’s “Pick up card” response, code 253; the same $151.20 went through on the third attempt — a different cause.) No brand answer is visible in any source since: Slack and TG failed again today, and no brand-enablement ticket appears among Linear’s 50 most recently updated open issues.

Next action

With Andrew/Ignacio: what enables Mastercard/Amex/Discover on the NMI MID, and by when — give Tim a date. Until then the checkout should say “Visa only” before a buyer types a card (Nur, next to REV-100).

Open since 28 Aug; Nur asked again on the morning of 29 Aug. No update in Core Engineering by 2 Sep, and TG has failed in the five collections since — whether it went out is unverified. He kept shipping meanwhile: the webhook-identification pair (#417/#418, 9 Sep), the embedded-checkout CHIPS binding and fallback (#419/#420, 10 Sep, promoted #421), and “Fix self-contained manual payout instructions” today (12 Sep, promoted #423). Keep him shipping.

Next action

Send it, confirm in the thread.

Hudaifa Elahi rejoined #halo-peptides 31 Aug 15:52Z (the “restore the channel” half of REV-163 is done); nobody had written there by the 2 Sep collection, and Slack has been unreadable since. Verified today in Linear: REV-163 is still [Todo] p2 @aadil, last updated 2 Sep. Owed: $1,139.16 + $358.16. The ticket asks you to explain what was fixed (Apple Pay encoding, consent gate, order-note links) and what is coming (stable payment links, REV-159), give a payout date, and get Sufyan to retest after the payment-link fix.

Next action

Call, then post the payout date in #halo-peptides so it is on record.

Jarrod’s copy ends at 8.4 (31 Aug 23:48Z); Tim: “that text is from the master document, not the one you signed… I will discuss with Aadil today” (1 Sep 05:57Z). His accountant wants WA tax collected; Tim also tagged you 31 Aug 16:36Z on Washington registration timing ($100k trailing-12-month threshold). The same question is open in Florida — REV-196 asks to switch FL collection off until Revion is registered there — so one policy answers both.

Next action

Send Tim the executed RHP agreement plus your call: an addendum carrying the tax clauses, or accept his position. He transacted for real on 2 Sep ($598).

Prod DB since 31 Aug, at the last successful read (2 Sep): Kiyora 0 sessions, Zen 0, Best Peptide 0, Biopep 1 (Casey’s own $59 attempt, expired). Tim (2 Sep 06:05Z): “we have to push merchants from all sides to transact. Slack does not work very well.” You offered to do the chasing on 31 Aug. Two automated channels exist alongside the call — the idle-reminder email (merged + promoted 6 Sep, #376/#402, still unarmed per REV-190) and Tim’s admin bulk email with recipient preview (REV-208, #414, 7 Sep) — and a third is queued as REV-210, the outreach campaign to GPP merchants and ~200 prospects. None of them replaces a call.

Next action

Per merchant: Kiyora — switch real traffic on; Zen — one $-test with Tim watching; Best Peptide — book the 20-minute embed call (the embed was rebuilt 10 Sep); Biopep (Casey) — retry the test and accept the Slack invite.

1 Sep 20:52Z: “can we approve Apex Peptide Supply… no payment methods at all… desperate guy.” Tim (2 Sep 06:02Z): “we do not have his application.” Provisioning starts from /apply (Middesk KYB); nothing can be created by hand. The ask got cheaper since: the 3-field apply-fast intake shipped 5 Sep (#399). Warn him about one thing — REV-93 says /apply still rejects real-world scanned PDFs, so his documents need to be clean exports.

Next action

Send him revioncaps.com/apply today and agree the rate — the fee-rate ticket (REV-189) has left Linear’s open list, so check with Nur what rates the system now accepts before you promise one.

VAPI_PRIVATE_KEY etc. are SET on revioncaps-prod; calls are held off only by VAPI_OUTBOUND_ENABLED=false. No calling-window, DNC, or consent gates exist in vapi-outbound.ts. Unchanged since 31 Aug — and with Linear readable again today, no VAPI ticket appears among the 50 most recently updated open issues, so the decision lives nowhere but this board.

Next action

Either unset the prod keys or commission the TCPA gates. Deciding is the task; whichever way it goes, file it so it stops living in a chat.

Verified today: REV-164 is [Todo] p3 @aadil, last updated 27 Aug — unchanged since the day it was filed. Readable by anyone who scrolls Core Engineering.

Next action

Rotate it, delete the message, close the ticket.

Variants live in the “Revion Home Variants” artifact (REV-101, [In Progress] @tim, upd 2 Sep). Waiting since 27 Aug; no letter seen by 2 Sep and TG has failed in the five collections since. The brand-identity pass landed regardless (nur/home-brand-identity → #406, 7 Sep, four introduced defects fixed same-day in #408), and REV-174 is still [Todo] p2 @nur, untouched since 27 Aug — waiting on you, not on him.

Next action

Reply with a letter in the Core Engineering thread.

Decided 31 Aug 13:37–13:43Z; filed as REV-187 “Integrate DocuSeal for document e-signing (replace DocuSign seats)” 1 Sep 00:16Z. Verified today: still [Backlog] p3 @unassigned, upd 1 Sep. The 5-contract batch (REV-192, 2 Sep — Pura 8.5, Planet 8.5, Fit Aminos 9, Sports Tech 10, Epic 12) used DocuSign envelopes meanwhile, and none of those five has shown up as an application since.

Next action

Set up the Docuseal template (generic + company/signature/signer/title/date fields), assign REV-187, and chase the five signed-but-never-applied merchants yourself this week (your own words, 31 Aug).

Tim (2 Sep 06:12Z): “REV-150 (URGENT)”. Today it reads [Backlog] p1 @nur, last update 27 Aug — no state change in sixteen days. The ticket’s three gaps stand: (1) settlement evidence for Halo’s NMI orders — confirm the evidence sweep + NMI reporting creds run on revioncaps-prod, clear the 2 manual_review rows; (2) ACH generation — prod ships PAYOUT_ACH_SLACK_ENABLED="false" and has no ACH_* secrets (sandbox has the set), plus the Slack roster env; (3) maturity math (t+4 FedACH days). REV-191, which carried the automation end state, is no longer in the open list; the one payout commit since is “Fix self-contained manual payout instructions” (12 Sep, promoted #423). Outstanding drafts: 27 Aug $1,139.16, 1 Sep $358.16.

Next action

Gaps 1–2 today (ACH values from Mercury/Aadil), penny-test file to Mercury before the first real one. And say plainly on the ticket whether automation is still the plan now REV-191 has closed — if it is not, REV-150 should be reprioritised rather than sit at p1 unread.

All movement is in git: PR #376 (branch feat/idle-merchant-reminder, off by default) merged 6 Sep (d4fd4a1), promotion-review fixes followed (#403), and the promotion PR from sandbox (#402) merged the same day; 7 Sep brought the reminder into the new palette (5d0f09e). Linear today: REV-190 is still [Backlog] p2, last updated 6 Sep. What no source can show: whether prod has REVION_IDLE_REMINDER_ENABLED=true + REVION_IDLE_REMINDER_SKIP=mrc_gu6vQA07rA7D (RHP stays out until the 8.5/8.7 question closes), whether the Fly apps rolled the promotion, or whether any 14–18 UTC window has produced reminder emails.

Next action

Set/confirm both flags on prod, verify the rollout, then after the window: emails rows of kind merchant_idle_reminder delivered, merchant_idle_reminders max 1 per merchant per 72h. Pre-check block in REV-190.

The newest cluster in your queue, and the only p1 product work filed this week outside QA: REV-214 “Onboarding: verify callback, activate, then send portal credentials” (Todo, 11 Sep), REV-218 “Custom merchant setup pack and callback submission before portal access” (Todo, 11 Sep), REV-219 “Verify callbacks while inactive before first merchant activation” (Todo, 11 Sep). Together they describe the ordering defect behind several of the last six onboardings — credentials and “you are live” arriving before anything proved the merchant could receive our calls. Adjacent and already shipped: outbound webhooks now identify themselves (#417/#418, 9 Sep), which is what makes a pre-activation callback test recognisable on the merchant’s side. Sean Finck is the first merchant this would apply to; five signed contracts (REV-192) queue behind him.

Next action

Sequence them 219 → 218 → 214 and say which lands before Sean Finck is provisioned. REV-169’s credentials-email copy is part of the same handover — fold it in rather than fixing it twice.

emails.ts:368 still carried the line at the 2 Sep read. Linear today: REV-169 “Fix the merchant credentials email copy” is [Backlog] p0 @nur, last updated 11 Sep — so it was picked up in the same sweep that produced REV-214/218/219, but with no state change. It went to Biopep on 31 Aug; humans correct it in-channel each time — the template is the fix. Slack welcome v2 (#412, 7 Sep; delivery fixed 8 Sep, #415/#416) reworked the channel welcome, but nothing in git names the credentials-email line.

Next action

One template edit, shipped with the REV-214 sequence: state what is live, what is pending, and what the merchant does next — no “payments disabled”.

REV-189 (“fee rate 8.5 / 9 / 10 and any %”, open at the 2 Sep read) is not among Linear’s 50 most recently updated open issues today, so it was closed or cancelled during the blind window; no commit in the 9–12 Sep git window names fee rates, so what actually shipped is unverified. The defect it was filed for, at the 2 Sep code read: zod locks feeRate to 12|14 in three places, the admin types it as 12 | 14, sandbox-provisioning-client.ts:66 refuses other values, and settlement.ts guards fee_rate IN (12, 14) twice. REV-192 sent Pura 8.5, Planet 8.5, Fit Aminos 9, Sports Tech 10, Epic 12.

Next action

One line back: closed as done, or cancelled? If done — prove 8.5 round-trips to fee_cents, renders “8.5%”, and passes both settlement guards. If cancelled — Aadil has five contracts to re-paper at 12/14, and he needs to know today.

support_admin_alert emails to support@send.revioncaps.com showed [failed] repeatedly from ~28 Aug in the prod email log (seen at the 31 Aug board build); earlier alerts to support@revioncaps.com delivered. No bundle since has carried email-log rows, so still-failing is unverified — and nothing in git through 12 Sep touches it. The general fix, REV-146 (“capture every checkout/gateway/plugin/webhook failure into an admin page + Slack”, Nar’s ask), is [Todo] p2, last updated 7 Sep.

Next action

Compare the sending domain on send.revioncaps.com with the delivered revioncaps.com alerts and say which one is wrong; you are the only person who can read that log while the DB is unreachable from here.

Linear today: REV-210 “Outreach email campaign to external lists (GPP merchants + ~200 prospects) with integration instructions”, [Backlog] p0 @nur, last updated 7 Sep. Two send paths already exist — Tim’s admin bulk email with recipient preview (REV-208, #414, 7 Sep) and the idle-reminder sweep (#376/#402, promoted 6 Sep, still unarmed) — so the missing pieces are the list, the copy, and sending-domain reputation. That last one is not theoretical: send.revioncaps.com is the subdomain whose support alerts have been failing since ~28 Aug.

Next action

Say which of list / copy / sending domain is missing, and whether #414 is the send path. A p0 with five days of silence should either move this week or drop to p2 honestly.

Linear today: REV-196 “Turn OFF Florida sales-tax collection until registered: $0 FL quotes, refund collected tax, purge TaxJar test transactions”, [Backlog] p2 @nur, last updated 2 Sep. It is live, not hypothetical: TaxJar is genuinely answering rather than falling back — a Miami 33131 quote returned $3.85 on $54.99 (7%, Miami-Dade incl. county surtax) per BACKLOG.md — so FL buyers are being quoted and charged real tax. It is the same class of problem as Jarrod’s Washington question, open for eleven days.

Next action

$0 FL quotes behind a config flag today, then produce the list of FL orders already charged so the refunds can be issued, and purge the TaxJar test transactions.

Tim filed REV-191 on 2 Sep 06:30Z: auto-draft after cutoff → run-level approval → Mercury API send → auto-reconciliation, PAYOUT_MANUAL_INSTRUCTIONS_ONLY off, plus Aadil’s 31 Aug ask that a merchant’s FIRST payout post carry the business address (name + breakdown afterwards). It is not among the 50 most recently updated open issues today. The only related code since is “Fix self-contained manual payout instructions” (12 Sep, promoted in #423) — which reads like the address-on-the-post half rather than the automation. Whether the payout Slack post now carries everything Andrew needs is unverified: Slack has been dark since 2 Sep.

Next action

Say what REV-191 was closed as, and whether PAYOUT_MANUAL_INSTRUCTIONS_ONLY is still true on prod next to PAYOUT_AUTOPILOT_ENABLED=true. If the automation half moved into REV-150, note it there so the plan lives in one place.

REV-152 completed 28 Aug 15:05Z and is absent from today’s open list, as expected. Prod at the 2 Sep read: mrc_roNy1mlK9Ij5 domain https://www.biopepusa.com. PR #364 folds a leading www for success_url/cancel_url and public-checkout CORS; whether “verify at registration”, “log rejected checkouts” and a correction path that does not route through suspend shipped is still unverified from any bundle since.

Next action

Say which of the three items shipped; if any did not, file the remainder — closing the parent while merchants keep landing on www is how this reaches a fifth merchant. Tim fixes Biopep’s row by hand meanwhile.

Moved 10 Sep: REV-200 — “Fix embedded checkout binding with CHIPS” (#419) and “fall back when CHIPS is unavailable” (#420), promoted the same day (#421); the ticket is no longer in the open list, so the embedded flow now binds with partitioned cookies and degrades instead of breaking. Still open today, verified in Linear: REV-124 loading overlay swallows clicks (Backlog p2) · REV-100 Apple Pay failures undiagnosable (Backlog p2) · REV-166 checkout link exposes buyer PII (In Review p2, ten days) · REV-203 storefront bootstrap fires unused /public/products, /public/cart, /customer/auth/me on the hosted-checkout page (Backlog p0) · REV-204 /apply loses everything on refresh + 2h upload expiry (Backlog p1). Ops/visibility: REV-146 error log + Slack · REV-142 alert when a merchant goes silent (p0, unchanged since 25 Aug) · REV-145 admin plugins page · REV-173 plugin telemetry null · REV-165 daily funnel/decline report. Money correctness: REV-172 gateway refunds invisible to settlement · REV-175 payout export with stale banking.

Next action

Land REV-203 next — a p0 that costs three wasted requests on the exact page where buyers are dropping, and the cheapest item in the list.

slack_provisioning_status/_error exist on the merchant row but nothing shows them. #biopep-usa-llc still held only our team 48 hours after creation (as of 2 Sep), and only a shell query can say whether Casey’s invite failed or sits unaccepted. Welcome v2 (#412, 7 Sep; delivery fixed 8 Sep, #415/#416) auto-posts the integration pack once a channel exists — invite status in admin is still unexposed, and REV-218’s “setup pack before portal access” assumes someone can see it.

settlement.ts deducts refunded_cents but never recalculates fee_cents down; MFSA 16.4 argues the fee share should come off too. Invisible until a merchant partially refunds a settled order — cheaper to fix before one does. Adjacent and still open today: REV-172 (gateway-side refunds invisible to the settlement sweep, [Todo] p2, unchanged since 27 Aug).

Git 4–7 Sep on nur/home-brand-identity: the Revion identity across every Revion-controlled interface, /apply-fast + onboarding editor brought into it, the mark named “Revion Caps”, the Clash Display gate corrected — merged as #406 (7 Sep), four introduced defects fixed same-day (#408). Linear today: REV-174 is [Todo] p2, untouched since 27 Aug; REV-101 (the variants, Tim) is [In Progress], upd 2 Sep. Whether a letter was picked is unverified — TG has been dark since 2 Sep.

Next action

Once Aadil’s letter lands, implement the chosen layout on top of the new identity (the logos are already in). Nothing to do before that.

Asked in Core Engineering 31 Aug 13:48Z mid-triage of a phantom inquiry: “Would be sick if we had the customers number ready for anyone/me/andrew/pat to call them right away too.” The buyer’s phone is collected at checkout; the billing-inquiry queue and its alert email do not surface it. Verified today: no such ticket appears among the 50 most recently updated open issues.

Next action

Show the buyer’s phone on the billing-inquiry admin view + in the alert email. File it in Linear with the LLM pre-check block so it stops depending on this board to be remembered.

Tim (2 Sep 06:04Z): ~20 real sessions in the 28 Aug – 2 Sep window, 5 completed, 2 non-Visa declines, ~9 reached our page and never submitted a card (~$2k) — “that is exactly the PostHog replays — Narboto has the invite, replay review of these session IDs is the next step.” Halo sessions to pull first: cs_1MxLyGmlAnYE1uDVNOXz $340 · cs_iCIj0VavIkfhPcP5IFQG $205.20 · cs_42nR0ZkxuLfKm7MsBVBV $292.50 · cs_aBS89ts7SbcqM7oZVV2n $321 · cs_w5dSBawUW7yVwtrTWsUW $80 · cs_1da8x8iU3zmd6bY8lThA $151.20 (expired, then completed on retry) · cs_2G4sPw1W9GLgBLT_NKYX $69; plus Biopep’s cs_f5kPI4eMiSQd1xpSPnrk $59. Server-side payment_success/payment_failed events (#404) plus privacy hardening and wider outcome coverage (#410) landed 7 Sep, so replays can now be joined to server truth. REV-193, the 2 Sep QA issue this was to be commented on, has closed; today’s issue is REV-220.

Next action

Watch each replay; one line per session — where they stopped (price / trust / card form / error) — as a comment on REV-220 and in Core Engineering; anything reproducible becomes a qa issue.

Prod DB, merchant mrc_rhnnN_Yat26u (Halo), since 31 Aug: orders RC-2026-1000228, -232, -233, -235, -236, -242 — all $0.50, all AUTHORIZED, all from narbotokerimov@gmail.com (31 Aug 11:32Z → 1 Sep 16:47Z), none refunded at the 2 Sep 13:05Z read; every DB read since has failed, so a refund in the last ten days is unverified. Nur’s expired $0.50–$3.00 sessions and Aadil’s $106 one sit on the same merchant. REV-216, which you filed today, is the structural end of this.

Next action

Say what they were; refund the six from admin today. Also the 1 Sep leftovers: US-7 + US-8 FAIL, three ZZTEST applications still “received” at the last read.

Filed and updated today: REV-216 [Todo] p1 @narbotokerimov. It pairs with REV-217 (Nur, p2, also filed today: “QA digest must count skipped, missing and incomplete daily tests”) — both sides of the daily are being rebuilt this week — and with REV-60, the shared plan, edited 11 Sep. The onboarding half matters right now: Sean Finck is next to provision and Nur’s REV-214/218/219 change the sequence, so the first person to run the new order should be you on a throwaway store, not a merchant.

Next action

Stand up one Woo store and one custom-integration store on your own account (Narboto inc / getrevion-capsule.com), move every $-test off Halo, then run one adversarial onboarding end to end and file what it breaks.

Linear today: REV-93 [Todo] p1 @narbotokerimov, last updated 31 Aug — twelve days. Two unassigned tickets describe the same wound from the product side: REV-186 (“/apply document uploads silently rejected — store CDR rejection codes + actionable error messages”, p2) and REV-183 (“sanitizer rejections shown as a generic error with no reason logged”, p2). The 3-field apply-fast intake (#399, 5 Sep) shortened the form but not the upload path, and REV-204 (loses everything on refresh + 2h upload expiry, p1) is the third leak in the same funnel. Aadil is about to send Apex Peptide Supply through it.

Next action

Reproduce with a genuinely phone-scanned PDF, capture the CDR rejection code, and post it on REV-93 — that code is exactly what REV-186 needs in order to show an applicant something actionable.

Open dailies in today’s Linear read: REV-220 (12 Sep, p0) · REV-215 (11 Sep, p1) · REV-209 (7 Sep) · REV-207 (6 Sep) · REV-206 (5 Sep) · REV-202 (3 Sep) · REV-181 (30 Aug) · REV-180 (29 Aug) — eight, spanning two weeks, none closed. REV-98 (“validate merchant dashboard production release 5565719”) has been [In Review] since 2 Sep. This is the gap REV-217 was filed for today: the digest cannot currently count skipped, missing and incomplete runs, so an unrun day and a passed day look identical from outside.

Next action

Close or explicitly mark-skipped every daily older than 9 Sep, one line each, so REV-217’s counter starts from a true baseline instead of inheriting a two-week backlog.

Today’s 12:57Z bundle is the first partial recovery since 2 Sep: Linear returned 50 open issues, and the marks fetch answered — empty, so there were no ticks or comments on the 10 Sep board. Everything else failed exactly as on 7–10 Sep: nine Slack sections “check fly auth”, all six watch-merchant reads empty (“machine/auth?”), the DB summary crashed with the same raw JSONDecodeError, TG unavailable. The split is the finding: the two sources that returned need neither binary — Linear is HTTPS with an API key, /api/marks is Cloudflare Pages — while Slack (token in Fly), the six DB reads (Fly machine) and TG (MTProto via node) all do. Also visible: the marks fetch still asks for day=2026-09-10, so no board published on 11 Sep, and the ticks from the 7, 8 and 9 Sep boards have never been read.

Next action

flyctl auth whoami + machine state by hand, then an explicit PATH export (node + flyctl) at the top of collect.sh and generate.sh — or plist EnvironmentVariables — and a FORCE=1 re-collect. Then fetch marks for 2026-09-07/08/09 so three boards’ ticks are not lost, and log an unavailable-sections count per run so a blind bundle is loud.

Merges into production: #373 (1 Sep), #378 (2 Sep), #402 (6 Sep, carrying the idle-reminder sweep #376 + review fixes #403), #421 (10 Sep, carrying the CHIPS pair #419/#420) and #423 (12 Sep, carrying “Fix self-contained manual payout instructions”), with #422 the reverse merge from production on 10 Sep. Prod CD needs the CLAMAV/CDR tokens set 28 Aug; no deploy log has appeared in any bundle since. The 7–8 Sep batch (#404 · #406 · #407 · #408 · #410 · #412 · #414 and the REV-171 delivery pair #415/#416) is in the same unverified state. Last charges known to have served: RHP $598 and Halo $151.20, both 2 Sep.

Next action

flyctl releases per app + release tag (the same auth the collector needs, so do both in one sitting); then the Playwright checkout E2E gate on the live sandbox channel against the CHIPS binding. Never place a payment on sandbox.revioncaps.com — prod keys.

RHP’s first real sale (2 Sep 05:08Z) and Halo’s 2 Sep morning order passed unwatched. Next: Casey’s Biopep retry, Chris (Zen), the Best Peptide embed call on the 10 Sep build, Sean Finck once provisioned — watch-merchant.sh <mrc> during the order, confirm each step, void after. Gated on the same Fly access as the collector: all six watch-merchant reads came back empty again today.

File one labelled Charge inquiry via the sandbox public support endpoint and confirm the alert email carries both admin links. (Claude’s live POST was classifier-blocked — needs a human-run curl or Tim’s go.) Worth pairing with Nur’s failing support_admin_alert item: the same send path is what would carry it.

The 31 Aug chases drew two replies (Jarrod — tax; Jenifer — thanks); Chris and Best Peptide stayed silent through 2 Sep. With Slack and the DB unreadable for the fifth collection the sweep still has no fresh input — the collector fix comes first. The idle-reminder email takes over the routine nudge once armed (REV-190), and Tim’s admin bulk email (#414) plus REV-210 add the broadcast paths.