Where your leads come from, and what goes back

[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_1262":1263,"_1264":1265},"routes/_app.x.$handle.$name",{"_98":97,"_32":43,"_107":88,"_27":108,"_13":14,"_109":-5,"_11":110,"_111":112,"_113":114,"_115":116,"_117":118,"_20":-5,"_119":-5,"_120":-5,"_121":47,"_122":123,"_124":25,"_125":-5,"_126":-5,"_127":128},"routes/_app.x.$handle.$name.branch.$branch.version.$version.diff",{"_11":12,"_13":14,"_15":16,"_17":-5,"_18":-5},"project",{"_41":42,"_32":43,"_36":44,"_45":-5,"_46":47,"_48":49,"_50":49,"_51":52,"_53":-5,"_18":54,"_55":56,"_57":25,"_58":-5,"_59":-5,"_60":61,"_62":63,"_64":65,"_66":67,"_68":69,"_70":-5,"_71":72,"_73":72,"_74":75,"_76":75,"_77":75,"_78":72,"_79":72,"_80":81,"_82":83,"_84":85,"_86":47},"version",1234,"changes",[19],"aiChatInfo","userId",{"_20":21,"_22":23,"_24":25,"_26":25,"_27":28,"_29":28},"file",{"_30":31,"_32":28,"_33":20,"_34":35,"_36":37,"_38":14,"_39":40,"_24":25},"previous",{"_30":31,"_32":28,"_33":20,"_34":35},"deleted",true,"deletedHere","path","SOURCE-BUNDLE.part1.txt","latestPath","fileId","143a8770-9081-11f1-9c36-1607ee4eb77e","name","fileType","content","THE DOGS SPOT — SOURCE BUNDLE (part 1 of 47)\n\nEVERY source file in this project, engine/ included. Restoring these parts and nothing else gives\nyou a tree that builds, typechecks and runs its own test suite with no network and no val.\n\nengine/ is here as of 14 Aug 2026. It used to be left out because val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff\nholds it, which was true of every engine file except engine/watch.ts: a module the val does not run,\nso it was never deployed, so it lived in one container and nothing else. A reclaim destroyed it.\nscripts/deploy.mjs --check still compares engine/ against the val file by file; that is a second\ncheck on the same files now, not the only copy of them.\n\nRESTORE (needs only node, from an empty folder). Save each part, then run this ON EACH ONE:\n\n node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(process.argv[1],\"utf8\");\n for(const s of b.split(\"\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\n\");\n const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});\n fs.writeFileSync(f,c.replace(/\\n$/,\"\"))}' PART.txt\n\nA record named #1, #2, ... is one FILE cut into pieces: concatenate them in order, then\nstrip one trailing newline from the last. scripts/restore.mjs does this for you.\n\nEach part is complete in itself: whole files only, no reassembly, any order.\n\nThen: node scripts/build.mjs (engine/ came out of these parts; nothing to fetch first)\n node scripts/typecheck.mjs\n node tests/run-all.mjs\n node scripts/deploy.mjs --check (pulls nothing, proves the val matches what you restored)\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (3 of 129 files)\n engine/NOTES-dashboard.md 8142 bytes c6dfb7a69721\n engine/NOTES-v1.4.md 50185 bytes 015b5ff28c6c\n engine/REGISTER-AUG5.md 2927 bytes c8ce4d6aef0d\n\n================================================================================================\n=====FILE engine/NOTES-dashboard.md =====\n# NOTES — dashboard.ts, 14 August 2026\n\nWhy the long notes that used to sit in `engine/dashboard.ts` live here instead. val.town caps a\nsingle file at 80,000 characters and answers a push over that with HTTP 400,\n`body/content must NOT have more than 80000 characters`. On 14 August 2026 dashboard.ts reached\n80,910 and the push was refused — so Kim's status page went on serving the OLD deployed copy,\nincluding a sentence a prior audit had already proved false, while the corrected file sat in the\ntree unable to land. The cap was rediscovered by that 400, which is the expensive way to find it;\n`scripts/deploy.mjs` now checks every file it is about to push and says the number first.\n\nFour narrative comment blocks were moved here VERBATIM to make the room. Each site keeps a\none-line pointer. Nothing was edited, nothing was deleted, only relocated — the `[was: ...]`\nincidents below are the record of what this page once got wrong, and they are load-bearing.\n\nThis is the same move `NOTES-v1.4.md` records for main.ts (R39 there). A SECOND notes file rather\nthan more of that one, so two files at their ceiling cannot collide in the same document.\n\nDeployed as an inert `file` on the val, registered in `scripts/deploy.mjs`'s TYPES map, so it sits\nnext to the code it explains.\n\n---\n\n## From `esc()` and `escCell()` — escaping, and the things escaping does not cover\n\nMoved verbatim from `engine/dashboard.ts` (was lines 162-185). The pointer left at the site names\nthe three holes; this is the evidence behind each one.\n\n // ESCAPING, PLUS THE TWO THINGS ESCAPING DOES NOT COVER.\n //\n // Every name and every dog name on this page is typed by a stranger: her booking form is public,\n // and the account already holds a self-service \"help test\" contact with future bookings. So this\n // is a hostile input path, not a formatting helper.\n //\n // 1. BIDI CONTROLS. U+202A-U+202E and U+2066-U+2069 reorder the text AROUND them when the browser\n // draws the line. None of them is < > & \" or ', so all five escapes miss them entirely, and a\n // name of \"Kim Refund ‮24.05$ eeF\" renders on Kim's phone reading right-to-left through\n // the rest of the cell. Dropped rather than escaped: they have no legitimate use in a dog's\n // name, and a visible mojibake would be worse than a silent removal.\n // 2. LENGTH. There is no cap anywhere between the CRM and this page, and no word-break rule in\n // the stylesheet, so one 10,000-character name with no spaces in it pushes the table wider\n // than the 720px wrapper and the phone view is unusable. Truncated with an ellipsis, which\n // still shows enough of the name to recognise who it is.\n //\n // The two are SEPARATE functions on purpose. The length cap belongs only on fields a stranger\n // types; putting it on esc() itself cut the card's own generated sentences off at 120 characters,\n // including the one that tells Kim this is not a list of people who owe her money. Three tests\n // caught that within a minute of it being written, which is what they are for.\n // 3. VALUES THAT ARE NOT TEXT. `String(x ?? \"\")` renders an object as \"[object Object]\" and a NaN\n // as \"NaN\", and both went onto Kim's page looking like something her CRM had said. Only a\n // string or a real number is renderable; anything else is nothing, and the copy around each\n // cell already knows how to say \"not recorded\".\n\n## From the opportunities scan in the default export — why the whole stage is read\n\nMoved verbatim from `engine/dashboard.ts` (was lines 378-393). The pointer left at the site keeps\nthe headline number; this is how it was established.\n\n // PROVEN LIVE 4 Aug 2026, and this replaces a capped scan that was quietly wrong.\n //\n // The old version walked six pages of ALL 5,695 opportunities and filtered client side. Two\n // things were wrong with that. It flagged itself truncated, which suppressed the funnel and\n // put an \"at least this many\" caveat on the tile. And it undercounted: it found 2 new\n // customers in the last 7 days when the true figure is 5, because the ones it missed were\n // created long ago and only reached the Customer stage this week, so they sat deep in a list\n // ordered by creation date.\n //\n // Three facts make a complete scan affordable, each verified against the live account:\n // 1. `pipeline_stage_id` IS honoured server side. Customer holds 1,513 records, not 5,695.\n // 2. Pagination is strictly newest-first by createdAt, so page count is knowable up front.\n // 3. meta.total is returned on page 1, so the rest can be fetched at once rather than in\n // series. Sequentially those 16 pages cost 9.4s; in parallel they cost about one.\n // No sort parameter exists (six spellings probed, all 422), which is why the whole stage has\n // to be read: someone can reach Customer this week having been created a year ago.\n\n## From the default export, at `modeKnown` — the mode is three-valued, not two\n\nMoved verbatim from `engine/dashboard.ts` (was lines 530-543). The pointer left at the site states\nthe rule; this is the incident it came from.\n\n // THREE-VALUED ON PURPOSE, because two values have nowhere to put \"we could not tell\".\n //\n // [was: `const practice = run?.testMode !== false`, one boolean, which turned every unknown into\n // a positive claim of practice. The mode row at the bottom of this page was gated on `runKnown`\n // and so said \"Practice or live: could not check\" correctly. The paragraph two rows below it was\n // gated on `stateKnown`, which is a DIFFERENT read. So: let the run-state or kill-switch read\n // fail while the state read succeeds, with the sequence empty, and this page printed \"In\n // practice mode ... has never sent to or processed one of your actual inquiries\" on a live\n // system, two lines under a box admitting it could not check. That is the same false sentence\n // Kim was shown from 11 to 14 August, reached through a second door. `modeKnown` is now the one\n // gate on every sentence that names the mode, and an unknown mode renders as unknown, never as\n // practice. Note it also requires an actual boolean: a run blob that reads fine but has never\n // been written (`run === null`) used to come out as practice, and would now otherwise come out\n // as live, which is the same bug pointing the other way.]\n\n## From the \"who is in the system\" card — the empty case, and which empty it is\n\nMoved verbatim from `engine/dashboard.ts` (was lines 981-995). The pointer left at the site keeps\nthe watchdog constraint inline, because that one binds anyone editing this copy. The reasoning\nunderneath it is here.\n\n // THE EMPTY CASE, AND WHICH EMPTY IT IS. This paragraph used to be chosen by `realPeople === 0`\n // alone, so it said \"in practice mode ... has never sent to or processed one of your actual\n // inquiries\" whenever the sequence happened to be empty — including now, when the system is\n // live and has messaged two real people. It was hidden only by the accident that one of them\n // is still enrolled. The moment the last person leaves (the remaining one reaches 21 days\n // around 1 September, or books) it would have come back, on a live system, in her words, as a\n // flat lie. Empty and PRACTICE and empty and LIVE are different facts and now read differently.\n //\n // AND SO IS EMPTY AND WE-CANNOT-TELL, which is the third branch below and the reason `practice`\n // stopped being a bare boolean. This whole block is chosen by `stateKnown`; the mode is a\n // different read, and when that read fails the branch above was reached with `practice` sitting\n // at its default of true. One failed read of a blob this paragraph does not even name was\n // enough to print the practice sentence on a live system. There is no default now: an unknown\n // mode gets its own words and they claim nothing. (Those words must not contain the phrase the\n // watchdog scans this page for, so they say \"in practice or for real\" instead.)\n\n\n=====FILE engine/NOTES-v1.4.md =====\n# NOTES — v1.4, 2 August 2026\n\nWhy the v1.4 changes exist. Moved out of main.ts because val.town caps a single file at 80,000\ncharacters and the reasoning was worth more than the space it cost inline.\n\nEvery item below came from a 14-agent adversarial pre-mortem (7 lenses, each finding handed to an\nindependent refuter: 62 raised, 7 killed, 55 survived). These are the six that were fixed.\n\n---\n\n## R19b — due-first filtering (the real quota fix)\n\n---- v1.4 (2 Aug) — R19b: DUE-FIRST FILTERING. The real quota fix. -------------------------\nv1.3 fixed the enrolment scan. The adversarial refuter went further and was right: this loop\nstill made three API calls per contact per run (contact, opportunities, conversations) plus a\ndeliberate 120ms pace. At one test contact that is nothing. At backlog scale it is ~9,600\nrequests and ~45 minutes per run — past every val.town execution timeout and past GHL's daily\ncap, and GHL answers sustained overload with 401/403, so the engine would have looked\ncredential-broken while quietly starving.\n\nThe fix costs nothing because the answer is already in the blob: isDue() and the sequence\noffsets are pure functions of state. If a contact's next message is not due, no send can\nhappen this run, so there is no reason to ask the CRM anything about them. On a 12-touch,\n3-week path roughly 1-2% of a population is due on any given tick — so per-run cost drops\nfrom O(enrolled) to O(due).\n\nTwo deliberate safety valves, because \"cheaper\" must never mean \"blinder\":\n1. SAFETY_SWEEP_HOURS — every contact still gets a full check at least once a day even when\nnothing is due, so exits (opted out, became a customer, booked) never go stale for long.\n2. Anyone with no lastCheckedAt, or in a status this shortcut does not model, falls through\nto the full check. The skip is opt-in per known-safe case, not a default.\n\n---\n\n## R21 — reply detection was blind to any outbound after the reply\n\n---- v1.4 (2 Aug) — R21: an outbound message used to hide a reply completely ----------------\nThe adversarial pass found the hole and it is a real one on THIS account. This reads a single\ndenormalised field on the newest conversation. Chloe answers the phone, Ava answers Facebook and\nInstagram, and 165 published workflows send things — so a customer can reply, get an automated\noutbound seconds later, and the direction field flips to \"outbound\". The engine then reads \"no\nreply\" and carries on messaging somebody who is mid-conversation with the business.\n\nunreadCount is the second, independent signal: GHL increments it on inbound and only clears it\nwhen a human opens the thread. An outbound does NOT clear it. So an unread thread means somebody\nwrote in and nobody has looked — which is exactly the state that must block a send, whatever the\nlast message happened to be. Verified present on 25/25 live conversations, 2 Aug.\n\n---\n\n## R22 — paused_reply had no exit\n\n---- v1.4 (2 Aug) — R22: paused_reply had no exit --------------------------------------\nReplying is engagement — it is the outcome the whole sequence exists to produce. But a\npaused contact stayed paused forever unless a human edited the blob by hand, which nobody\nwas ever going to do. So the most engaged leads quietly became the ones nothing happened to,\nand they sat in the \"active\" count making the dashboard look busier than the business was.\n\nNow: if a pause has gone this long with nobody acting on it, the engine raises a SECOND task\nsaying so, and lets them go rather than holding them in limbo. Deliberately does not resume\nthe sequence — someone wrote to this business and got no reply, and the fix for that is a\nperson, not another automated message.\n\n---\n\n## R23 — position is an array index\n\nv1.4 — R23: position is stored as an array index (lastMainStepSent). Insert a message\nat position 3 and every in-flight contact silently re-points at the wrong step —\nsomebody mid-sequence gets the wrong email and nothing anywhere says so. Recording the\nstep ID alongside the index does not fix the model, but it makes the drift DETECTABLE:\non the next send the engine compares what it is about to send against what it last\nsent, and says so in the journal if the sequence has moved underneath somebody.\n\n---\n\n# APPENDIX — build history moved out of main.ts\n\n---- v1.1 (27 Jul 2026, late) — five upgrades from the pre-deploy live review -------------------\nLive verification against the real account (verify-live-reads.py, read-only) found that the\ndiscovery tag \"nurture - puppy\" matches ZERO contacts — no spelling variant matches anyone, and\nthe newest 15 real New Lead contacts carry only \"messenger\"/campaign tags. There is no automatic\npuppy-vs-adult signal in the account's data model (age lives only in Ava's chat transcripts). So:\n\n1. ENROLLMENT IS HUMAN-GATED, by design not accident: applying the source tag to a contact IS the\nenrollment action (\"tag them and the system takes over\"). The New-Lead-stage requirement from\nspec §5's auto-discovery framing is deliberately DROPPED — under human gating the tag is\nexplicit intent, and silently ignoring a deliberately-tagged contact because their opportunity\nsits in a different stage would read as \"the system is broken.\" The safety guards that remain\n(already-customer, live-booking-already-exists, DND via rule 1 on first pass) block enrollment\noutcomes that would be WRONG, not merely unusual. Tag is env-overridable (TAG_SOURCE_SIGNAL).\n2. ENROLLMENT SURGE HOLD: normal operation is a few tags a day. If one run finds more than\nENROLL_SURGE_THRESHOLD (default 25) un-enrolled tag matches, someone bulk-tagged — the run\nenrolls NOBODY, journals the hold loudly, and keeps holding until a human either removes the\nbulk tags or sets ACKNOWLEDGE_SURGE=true. Already-enrolled contacts keep processing normally\nduring a hold. This is what protects a live account from a day-one accidental blast.\n3. SEND WINDOW: messages only go out 09:00–19:00 America/New_York (env: SEND_WINDOW_START_HOUR /\nSEND_WINDOW_END_HOUR), and SMS additionally never on Sunday (env SMS_SUNDAY_OK=true to allow;\nThe Dogs Spot is closed Sundays — a business texting on its day off invites replies nobody\nanswers). A due-but-out-of-window message simply waits for the next in-window run; offsets\nstill anchor to enteredAt, so nothing else shifts. Spec line ~222 explicitly accepted the\nlate-night case as a known limitation; this removes it.\n4. PAUSED CONTACTS GET A LIGHTWEIGHT PASS (v1.2 revision of v1.1's full skip): spec defines no\nresume path from paused_reply (a human reply permanently hands the conversation to a human —\nwriting sheet §4's own philosophy). v1.1 skipped paused contacts entirely; the adversarial\nreview showed that also disabled the DND/disqualified/became-customer rules for them, so a\npaused contact who later bought was never counted or retired. v1.2: paused contacts get a\n2-read safety pass (contact + opportunities; reply check pinned failed-closed so a send is\nstructurally impossible) — hard exits still fire, sends never do. Un-pausing is a deliberate\nhuman act: set the contact's status back to \"main\" in the puppy_state blob. Do NOT delete the\nentry — the puppy-path-v1 tag blocks re-discovery, so deletion just orphans them.\n5. ONE CALENDAR FETCH PER RUN, not per contact: the Pup Talk calendar holds 143 events in the\n±90d window (measured live) and the old shape re-downloaded all of them for every active\ncontact every run. Now fetched once per run and indexed by contactId.\nPlus: puppy_journal (append-only, capped 2000 rows — enrollments, sends, exits, pauses, holds,\nfailures) and puppy_summary (per-status counts, sends by step, exits by reason, booked-during-\npath, customers-during-path) — the numbers Kim's 30-day report needs, accumulated from day one,\nreadable by the watchdog. State hygiene: terminal entries untouched for 60+ days are pruned from\npuppy_state (their history stays in puppy_journal; the puppy-path-v1 tag still prevents\nre-enrollment).\n---\n\n# APPENDIX — long inline notes moved out of main.ts\n\nPUPPY PATH ENGINE v1.1 — nurture automation for The Dogs Spot's puppy leads (built 27 Jul 2026;\nv1.1 same evening — see the v1.1 addendum block below for what changed and why)\n\nWHY THIS EXISTS AS A VAL, NOT A NATIVE GHL WORKFLOW:\nGHL's public API cannot create or edit workflow steps — UI-only, no way around it — and the\nworkflow-builder UI itself was tested this session via browser automation and found completely\nunresponsive (clicks/scroll/keyboard, across multiple tabs and domains — not a one-off glitch).\nSo this is a val.town script driven by the GHL REST API instead, matching this account's own\nexisting idiom. Follows PupsClub-AutoSend-val-v2.1.ts's conventions closely on purpose: same j()\nfetch helper, same Deno.env.get-driven TEST_MODE-defaults-true pattern, same blob-based state,\nsame wrapped-in-try/catch-writes-a-state-blob-every-run structure, same per-recipient try/catch\ninside the send loop.\n\nHOW IT WORKS:\nOne state blob (puppy_state), keyed by contactId, tracks each enrolled contact's position in\neither the 8-message main sequence or one of two post-Pup-Talk branches (A: no-show, B: had the\ncall, didn't buy). Each cron run walks every contact currently in that state (plus, outside\nTEST_MODE, discovers new puppy-tagged leads to enroll) and re-evaluates a FIXED priority list of\nexit/branch rules (spec §5, rules 1-10 below, plus two additions flagged where they occur) top to\nbottom — first match wins. Only if nothing else matches does it fall through to \"send whatever's\nnext due.\" Every safety exit (DND, disqualified, became a customer, human reply pending) is\nchecked BEFORE a send is ever considered, every single run, for every contact, regardless of what\nstatus they were in a moment ago — that ordering is the whole safety model.\n\nHARD SAFETY INVARIANT (non-negotiable — Amir's written promise to Kim: \"nothing gets switched on in\nthe meantime\"):\nTEST_MODE defaults true. When true, this script never looks at a real contact at all — discovery\nis skipped outright, and the only contact it ever touches is one fixed dummy resolved via\ncontacts/upsert (firstName \"ZZTEST\", lastName \"PuppyPath-Dummy\", email aizhigitovamir@gmail.com —\nAmir's own inbox, safe to actually deliver to). Going live is a deliberate later step someone takes\non purpose (flip TEST_MODE=false as an env var) — not something that happens by forgetting a flag.\n\nGUARDRAILS:\n- \"[TEST] \" prefix on every subject line / SMS body while TEST_MODE, so a real send during testing\nis unmistakable — matches the PupsClub val's own convention exactly. Deliberately kept OUT of the\nemail body itself so the client-approved copy stays byte-for-byte verbatim; the subject prefix\nalone is enough to make a test send unmistakable without touching approved wording.\n- Per-contact try/catch inside the main loop (matches the PupsClub val's per-recipient try/catch)\n— one contact's transient API failure doesn't block the rest of that run's contacts.\n- State is written AFTER a successful send, not before — deliberately the opposite of the PupsClub\nval's \"write state before sending\" choice, because the failure mode being defended against is\ndifferent here. That script defends against a duplicate blast to many recipients from an\noverlapping run (one session opening, many people to text). This one processes contacts one at a\ntime in a single sequential loop, so the real risk is a step being marked \"sent\" and then never\nactually going out because the network call failed. A duplicate nurture message on a rare retry\nis a minor annoyance; a silently-skipped one is a message someone was promised and never got.\n- Exit/branch priority order is fixed and total (rules 1-10 below) — every contact is walked\nthrough the SAME order every run, so DND / disqualified / became-a-customer / human-reply always\noutrank a scheduled send, never the other way round.\n\nTWO GENUINE GAPS FOUND WHILE BUILDING THIS, NOT WORKED AROUND, FLAGGED HERE ON PURPOSE:\n1. GET /conversations/search — the call rule 5 (inbound-reply detection) needs — returns 401 \"The\ntoken is not authorized for this scope\" on this account's current PIT token. Tested directly\nthis session: with and without contactId, on both 2021-07-28 and 2021-04-15 API versions, all\nfour combinations 401 identically. This means reply-pause (arguably the single most\nsafety-critical rule in the whole spec) cannot actually run live with today's credential.\ngetReplyStatus() below fails CLOSED on this — it does not fabricate a \"no reply\" result, it\nreports conversationCheckFailed=true, and decideAction() treats that as \"do not send anything to\nthis contact this run,\" full stop (see rule 5 below). Practical consequence: AS CURRENTLY\nCREDENTIALED, this engine cannot send anything at all outside TEST_MODE, because the reply-check\nalways fails closed for every contact — which is an extra, accidental safety margin on top of\nthe TEST_MODE flag, but it is a real gap that needs a broader-scoped PIT token before this is\nactually USEFUL live, not just safe. Side note: inspect-dummy.sh's own conversations/search call\nwould silently render this exact 401 as \"(no conversation)\" — its error handling can't tell\n\"genuinely nothing sent\" apart from \"the API call itself failed.\" Worth fixing there too;\nflagged here since it surfaced while building this.\n2. The Pup Talk \"declined / not now\" outcome signal (rule 8) doesn't exist yet as its own thing.\nPer spec, this should key off the TDS-Declined tag being built for the separate front-desk\ntask-layer project (BUILD-CHECKLIST-UI.md). That tag did not exist as of the 26 Jul build\nchecklist (\"Settings -> Tags has no existing TDS-Bought, TDS-Declined, TDS-Nurture\"). Checked\nagain this session via contacts/search filtered by tag (contains_set operator, confirmed correct\nvia the account's own validation-error message listing valid operators) — zero contacts carry\nit, but that is a weak signal: a tag can exist in Settings -> Tags with nobody on it yet, and\nthis token cannot read Settings -> Tags directly (401, same scope gap as #1) to check for real.\nTreated as NOT CONFIRMED LIVE. PUP_TALK_DECLINED_TAG below is a clearly-named constant, not\ninvented behavior — wire the real value in once confirmed rather than guessing.\n\nState blobs: puppy_state (per-contact, keyed by contactId) · puppy_run_state (per-run report,\nmirrors pups2_state in the PupsClub val) · puppy_last_error (same pattern) · puppy_journal\n(append-only event history, v1.1) · puppy_summary (aggregate stats rebuilt every run, v1.1).\n\nBuild history (v1.1 addenda, v1.2 hardening, the two gaps found while building) moved to\nNOTES-v1.4.md when this file hit val.town's 80,000-character ceiling. Nothing was deleted.\n\n---\n\n---- v1.4 (2 Aug) — OPT-OUT FURNITURE, appended at render time, never written into the copy ----\nThe adversarial pass checked the shipped templates and found the thing everyone had assumed was\nthere: not one of the five SMS says STOP, and not one of the seven emails carries an unsubscribe\nline. An earlier risk register claimed opt-out wording was present. It was not. Retracted.\n\nThis is appended by the renderer rather than edited into puppy-messages.ts on purpose, for three\nreasons. It keeps the client-approved wording byte-for-byte, so what Kim signs off is what she\nwrote. It cannot be forgotten on a new path — every message rendered by this engine carries it,\nincluding the five paths whose copy has not been written yet. And it is one line to change if the\nwording ever needs to.\n\nThe SMS line is deliberately short: at 39 characters it costs a fraction of a segment, and the\n320-char ceiling is checked against the FINAL rendered body, furniture included, so a message can\nnever be pushed over the limit by the thing that makes it compliant.\n\n---\n\nRule 4b — booked something else entirely (Free Training Day). NOT an explicit numbered rule in\nspec §5 (which only names Customer/Won-Paid/monetaryValue for rule 4), but the WRITING SHEET's §4\nexits are unambiguous: \"If they book anything else... A paid service, a Free Training Day, walking\nin and booking at the desk - any of it ends this sequence.\" Free Training Day is its own pipeline\nstage with no monetary value (it's free), so spec's literal rule 4 wording doesn't actually catch\nit — a real gap between the spec and the writing sheet's own stated intent, not a content\ndisagreement (spec says content loses to the writing sheet, mechanism wins to the spec; this is\nneither — it's a rule the spec's enumeration simply left out). Resolved here rather than left\nbroken. This also happens to be the only sensible use for the \"done_booked\" terminal status the\nstate type declares but no other rule in §5 ever assigns.\n\n---\n\nRule 6b (v1.2) — REBOOKED while in a branch. Found independently by the adversarial review and the\nfuzz round (concrete trace: contact no-shows -> branch_a -> books a new Pup Talk two weeks out ->\nv1.1 still sent branch_a-2 \"Let's find another time\" for an appointment they'd already replaced,\nthen went terminal and stopped watching the new appointment entirely). If a live booking exists\nwhose start time is NEWER than the branch anchor (i.e., it's a different, later appointment than\nthe one that put them in the branch), the branch conversation is obsolete: go back to\nawaiting_appt_outcome and track the new appointment's outcome like any other. Rules 7/8 then\nre-fire off the NEW appointment — including a second no-show correctly re-entering branch_a with\nthe new anchor.\n\n---\n\n---- v1.3 (2 Aug 2026) — R19: THE ENROLMENT-SCAN QUOTA FIX -------------------------------------\nRaised by the adversarial pre-mortem and NOT refuted. The enrolment loop called\ngetOpenOpportunities() once per candidate. With one or two human-tagged candidates that is\nnothing; the day the dormant backlog is released it is one API call per candidate per run, on top\nof the walk itself, and GHL answers sustained overload with 401/403 rather than 429 — so the\nengine would not merely slow down, it would look credential-broken while quietly starving.\n\nThe fix is the same shape as the calendar index directly below, which already solved this problem\nonce for appointments: fetch the exit-triggering stages ONCE per run and index them by contactId.\nA candidate absent from the index has no disqualifying opportunity, which is the only question\nenrolment eligibility actually asks. Cost goes from O(candidates) to O(exit-stage size) — and\nthose stages are small, because the pipeline's own census puts Customer / Won-Paid / Onboarding\nat zero and Free Training Day and Disqualified in the low hundreds.\n\nDeliberately NOT applied to already-enrolled contacts: their per-contact read also has to catch a\nmonetaryValue > 0 opportunity sitting in any stage at all, and that population is bounded by the\nsurge guard, so it was never the blowout. Precision beats a clever sweep here.\n\n---\n\nField name NOT independently proven this session (the 401 blocked confirming it) — trying the\nconventional GHL field defensively. v1.2 tightened two ways after the adversarial round:\n1. STRICT direction validation — only the literal strings \"inbound\"/\"outbound\" count as a\nreadable signal. The old `direction == null` check let a falsy-but-not-nullish value (e.g.\nan empty string on a malformed conversation record) slip through as \"confirmed no reply\" —\nthe exact unrecognized-shape case fail-closed exists to catch.\n2. TEMPORAL scoping — an inbound message that predates this contact's enrollment is a historic\nconversation someone already handled (e.g. a \"do you do daycare?\" text from months ago), not\na reply to this sequence. Without this, such contacts would pause permanently before their\nfirst message ever sent. If no usable timestamp field exists on the record, we conservatively\ntreat the inbound as blocking (pause) rather than ignoring it. Timestamp field names are\nbest-effort until the scope unblocks and the real shape can be confirmed live.\n\n---\n\nv1.2 — paused_reply contacts get a LIGHTWEIGHT safety pass instead of v1.1's full skip.\nThe adversarial round showed the full skip quietly disabled rules 1/3/4 for paused contacts:\nsomeone who replied and later BOUGHT stayed \"paused_reply\" forever, was never counted as a\ncustomer, and never aged into pruning. Now: two cheap reads (contact + opportunities), no\nreply/no-calendar calls, conversationCheckFailed pinned true so rule 5 structurally blocks\nany send — only the hard-exit rules can fire. Un-pausing for real remains a human act: set\nthe contact's status field back to \"main\" in the puppy_state blob (do NOT delete the entry —\nthe puppy-path-v1 tag blocks re-discovery, so a deleted entry just orphans them; header docs\nupdated accordingly).\n\n---\n\n---- booking-link shortener (spec §7) ---------------------------------------------------------\nPurpose: message copy references one short, stable link; if the real booking URL ever changes, one\nline changes (REAL_BOOKING_URL above) instead of eight message templates.\n\nDeployment note, honestly flagged rather than guessed at: a single val.town val has one default\nexport, which is this file's cron() entry point. Whether val.town's current UI can attach a second,\nHTTP trigger to a NAMED export (not the default) on the SAME val was not verified this session —\nVT_TOKEN was unavailable, so nothing could be deployed to check. If it can, wire this function up\ndirectly. If not, the fallback is a second, tiny val: two lines, importing REAL_BOOKING_URL from\nthis file and re-exporting a redirect as ITS default export. Either way this is a convenience, not a\ncritical system, exactly as spec §7 frames it — kept deliberately simple.\n## v1.7 — SLOW TRACK (TAPER), deployed 4 Aug 2026\n\nKim's spec verbatim (3 Aug, 8:11 PM): \"a text or email once a week for month then every two\nweeks for 6 months then every month moving forward.\" Implemented as a fifth sequence:\n\n- New status `slow_track` (non-terminal). Entry: rule 9's 21-day completion now hands over\n instead of parking in done_soft_21d. `done_soft_21d` kept terminal for legacy blobs — no\n retroactive enrollment, deliberately.\n- Copy + cadence in taper-messages.ts: SLOW_WEEKLY x4 (rel d7/14/21/28), SLOW_FORTNIGHTLY x13\n (rel d42..210), SLOW_MONTHLY_BANK x12 keyed by CALENDAR MONTH of the send (July=heat+fireworks,\n Dec=holidays). nextSlowTouch() is the one scheduler; slowTemplateAt() shared by decideAction\n and the executor so decided and sent templates cannot drift.\n- HARD PROMISE, test-enforced: zero booking links, zero asks in all 29. The only CTA anywhere\n is \"reply and a person reads it.\"\n- All rails hold mid-taper (proven in tests/slow-track.test.mjs, 28 checks): reply -> paused,\n booking -> awaiting/branch (never back to slow), STOP/dnd -> hard exit, customer -> exit,\n R27 foreign quiet, R28 per-channel consent (skip-consume), min-gap, send window.\n- HARDENING found by the suite: min-gap now ignores a future-dated lastSentAt (mirrors R27's\n since>=0 guard). Previously a corrupted/restored blob with future lastSentAt froze the\n contact until that date.\n- Panel: slow_track in labels/stage bar/ACTIVE, plus a \"What needs doing today\" card answering\n Kim's 8:20 PM question in one computed sentence.\n- Deploy: val.town API PUT (main v22, messages v21, api v23, taper-messages created 201).\n All four hash-verified byte-exact after upload. Live run verified: report v \"1.7.0\", ok:true,\n testMode:true. main.ts is 79,537 bytes — 463 under the 80k ceiling; next addition must split.\n\n\n---\n\n## The dry tagging pass (v1.9, 5 August 2026)\n\n`main.ts` calls `dryScan()` from `puppy-detect.ts` once per run, before the TEST_MODE branch,\nand writes the result to the `tag_candidates` blob. It applies nothing.\n\n**Why it exists.** The engine enrolls people carrying `nurture - puppy`. All 5,544 contacts were\nchecked with a server-side tag filter: zero carry it, and nothing in the account applies it. So\nreal enrollment finds nobody and will keep finding nobody until the tagging is built. This pass\nis that tagging, running with its hands tied: it works out who *would* be picked up, writes the\ncounts down, and lets a human look before anything is switched on.\n\n**Why it cannot tag anybody.** `puppy-detect.ts` contains no `fetch`, no client, no POST and no\nblob write. That is structural rather than a promise, and `tests/detect.test.mjs` N13 asserts it,\nwith a negative control that adds a fetch call and demands N13 go red.\n\n**Why it sits ABOVE the TEST_MODE branch.** The first version was inside the `else`, which is the\nnot-practice-mode path. The system is in practice mode, so the line never once executed. It\ndeployed cleanly, verified by hash, and passed every test, and it was dead — nothing checked that\nthe code had actually *run*. Three deploys later it was caught by loading the page and finding the\nparagraph missing. A hash match proves the bytes arrived. It proves nothing about whether they run.\n\n**What it stores.** Contact ids only, plus counts. No names, no dog names, nothing anybody wrote.\nAsserted by N15.\n\n**Staleness.** `scanAgeNote()` puts a sentence on the page once the reading is over six hours old\nand a blunter one past two days, so a pass that quietly stopped cannot keep showing yesterday's\nnumbers as this morning's.\n\n**The open question for Kim.** A dog of about a year sits exactly on the boundary and there are a\nlot of them. The slow track covers the teenage stage, so they may well belong. `PUPPY_MAX_MONTHS`\nis 12 and it is her call, not ours.\n\n## deposit refresh — why it hangs off the engine's interval (6 Aug 2026)\n\n`deposits-cron.ts` is registered on this val as a SECOND file of type `interval`. The val accepted\nit and the API reports the type back correctly. It has never been observed firing on its own.\n\nWhat was actually watched, at named timestamps:\n- 15:44:27Z — deposits-cron.ts deployed. 15:44:33Z — the `holiday_deposits` blob advanced. Six\n seconds after a deploy is a deploy-triggered first run, not evidence of a schedule.\n- 17:21:23Z → 17:29:40Z — no movement.\n- 18:24:13Z → 18:32:38Z — no movement.\n\nval.town's API exposes no schedule field for a file, so there is no way to read the cadence back;\nthe only proof available is the stored `at` advancing with nobody triggering it, and that has not\nbeen seen. So the refresh is hung off `main.ts`'s interval, which IS watched keeping time — the\ndashboard grades its lateness and the watchdog alarms on it.\n\nShape of the call, and why each part is there:\n- LAST in the run, after the run lock is released and after every send and state write, so a slow\n or failing CRM read cannot delay or break the follow-up work.\n- Gated on the stored blob being older than an hour, so it is a couple of extra requests per hour\n rather than per tick.\n- Wrapped in try/catch that logs and swallows. A failed refresh degrades into an older \"last\n checked\" timestamp on Kim's page, which the card itself warns about past 36 hours.\n- `runCollection()` is read-only by construction: one `fetch`, `method: \"GET\"`, and a test asserts\n the collector contains no write verb.\n\ndeposits-cron.ts is left in place. If val.town does start firing it, the hourly gate means the two\nsimply share the work rather than duplicating it.\n\n## kill switch — the full note (moved out of main.ts, 6 Aug 2026)\n\nChecked before the run lock, before state loads, before a single contact is looked at. Kim can set\nit herself from the control panel (api.ts) with two taps and no help from anyone; it is the one\ncontrol she must never have to ask for.\n\nIt deliberately fails OPEN: if the blob read throws, the engine carries on rather than halting on a\nstorage hiccup, because a silent permanent stop would be indistinguishable from the outage this\nwhole system is built to be visible about.\n\nNothing is deleted while stopped. Every contact keeps its exact position and resumes from it.\n\n## deposit refresh — WATCHED WORKING, 6 Aug 21:49Z\n\nThe note above said deposits-cron.ts had never been observed firing and the refresh was therefore\nhung off main.ts's interval. That was true when it was written and is now superseded by evidence.\n\nObserved, with the source recorded by the code itself:\n- 2026-08-06T20:49:03.612Z — the list refreshed with nobody triggering it. First autonomous run\n ever seen here. Unlabelled: the source stamp did not exist yet.\n- 2026-08-06T21:49:13.781Z — refreshed again, `lastAttemptBy: \"deposits-cron\"`.\n\nExactly one hour apart, which is also the watchdog val's observed cadence (its own history runs\n19:02, 20:02, 21:02...). So val.town DOES run a second `interval` file in a val, on an hourly\nschedule, and the earlier conclusion was a statement about observation rather than about the\nplatform.\n\nBoth paths are wired and both go through `refreshIfDue`, which reads the same ATTEMPT_KEY stamp, so\nwhichever fires first closes the gate for an hour and the other is a no-op. Nothing needs removing.\n\nHow to check it without breaking it: GET the deposits endpoint WITHOUT `?run=1`. That returns\n`lastAttemptAt`, `lastAttemptBy` and `refreshDueAt`, and does not write the stamp. A `?run=1` DOES\nwrite it and pushes the gate an hour out — every observation on the evening of 6 August was ruined\nthat way before the read route existed.\n\n\n## R31 (10 Aug 2026) — THE INVERTED CONSENT PREDICATE. Caught in pre-flight, one day before go live.\n\n`readChannelConsent` read `status !== \"active\"` as blocked. That is exactly backwards.\n\nGoHighLevel names `dndSettings` after the DO NOT DISTURB switch, not after the person's\nreachability. So the status describes the switch:\n\n| status | meaning | must |\n|---|---|---|\n| `active` | the DND is ON | BLOCK |\n| `inactive` | the DND is OFF | SEND |\n| `permanent` | STOP reply from the recipient | BLOCK |\n| absent or `\"\"` | no per-channel record | SEND |\n\n**Verified against 2,500 live contacts on 10 August 2026.** The three shapes are unambiguous:\n\n- **`active`, 55 contacts on SMS**, every one carrying `TWILIO_ERROR_CODE: 30006`, a landline or\n unreachable carrier, with top-level `dnd:false` so nothing else would have caught them. Plus every\n channel on the contacts a workflow put on DND (`Updated from workflow_c6fc2df4...`), all carrying\n `dnd:true`. The old code read all of these as PERMISSION TO SEND.\n- **`permanent`, 25 contacts** across SMS and RCS, all carrying `STOP_KEYWORD`. Real human opt-outs.\n The old code blocked these correctly, by accident.\n- **`inactive`** — Kristina Gant, `dnd:false`, Email, SMS and Call all `inactive`, message\n `Updated by contact merge`. She is contactable, and on 10 August she was **the only contact\n carrying the `nurture - puppy` tag**. The old code refused her.\n\n**What would have happened at go live.** The single enrollee would have been silently skipped on\nevery channel, all eight main steps consumed as skips inside a day, and the run would have reported\n`enrolled:1, sent:0, failed:0` — which is indistinguishable from a clean launch. Meanwhile 55\ncontacts with an SMS block and no top-level DND would have been texted.\n\n**Why 394 assertions and 203 negative controls missed it.** The only test that touched this function,\nI3, read this file as a STRING and asserted the literal `\"active\"` appeared somewhere inside it. It\nnever called the function. A source-grep cannot detect an inversion; it passes just as happily on the\nwrong comparison as the right one.\n\n**The fix, and the shape of the fix.** The predicate now allow-lists the two states that mean \"go\"\n(`\"\"` and `inactive`) rather than deny-listing the states that mean \"stop\". An unrecognised status\ntherefore fails CLOSED. If GoHighLevel invents a fourth state tomorrow, this blocks rather than\nsends.\n\n`readChannelConsent` is now **exported**, and I3 has been replaced by I3, I3b and I3c which CALL it\nwith the three live shapes. Fault injection confirms it: restoring the old comparison turns I3 and\nI3b red, and the fix turns them green.\n\n**The general lesson, and it is the most useful one in this file.** A test that inspects source text\nis not a test of behaviour. Any function that decides whether a real person receives a message must\nbe reachable from a test and must be called by one.\n\n\n## R32 (10 Aug 2026) — the weekly report counted Facebook leads off a column that is null on 78% of contacts\n\n`report.ts` built its source table and its ad reconciliation from `contact.source`. Live, that field\nis null on 78.2% of contacts over a week and 81.3% over a month, and it has never once carried the\nstring \"facebook\". So the report told Kim **\"the CRM recorded 0 contacts tagged\nFacebook/Instagram/Messenger\"** in a week where her own attribution records showed 116.\n\nThe fix already existed in the tree and was not wired: `report-logic.ts` has had `channelBreakdown`,\n`attributionCoverage` and `prettyMedium` since 4 August, and `dashboard.ts` has read them correctly\nthat whole time. Only the weekly report never got it.\n\nNow: `report.ts` reads the first attribution entry per contact, the source table uses\n`channelBreakdown`, and the reconciliation uses a new exported `facebookLanded()` so a test can\nreach it — the count used to be computed inline inside a template literal, which is why nothing\ncaught it. `PAID_SOCIAL_RE` is case-insensitive on purpose: `channelBreakdown` returns display\nlabels (\"Facebook\"), so porting the old case-sensitive regex would have reproduced \"0 Facebook\ncontacts\" exactly, wearing a new hat.\n\n`unsourced` is deliberately no longer added into the Facebook figure. Its justification — \"Messenger\ncontacts usually arrive unsourced\" — was an artifact of reading the blank column. Under attribution\nthe unattributed population is about 1 in 142, not 111, so adding it would be padding a number that\nno longer needs padding. It is reported separately as a data-quality note.\n\nLive after deploy: **\"151 of the 175 new contacts in your CRM arrived from Facebook or Instagram\"**,\nand the source table reads Facebook 140, Instagram 11.\n\n## R33 (10 Aug 2026) — go-live hardening\n\n- **`fetchPupTalkApptIndex()` was unwrapped** and runs before the TEST_MODE branch, so one 401 from\n the calendar endpoint aborted the entire run before a single contact was examined. It has already\n done so once, stored as `lastError` on 2026-07-30. Now caught: an empty index degrades the Pup\n Talk check, which is survivable, where an exception stopped everything, which is not.\n- **`api.ts` told Kim three times that things take effect \"within 15 minutes\".** The interval is\n hourly. Corrected to \"within the hour\", including the sentence about honouring Do Not Disturb,\n which is the one that matters most.\n\n## R34 (10 Aug 2026) — the money matcher, scoped and summed\n\n- **`classify()` had no stage filter.** It took whatever the caller handed it, and a contact appears\n on up to eight boards here. Unscoped, live, $4,020 of $4,685 lands on a card that is not a\n booking: $500 onto a Survey Requested card for a customer whose real booking already carried\n $2,395, $2,550 onto the review pipeline, $900 onto a PupTalk card. The exception list goes 0 to 10,\n which breaks the promise on Kim's page that nobody has to do anything. `VALUABLE_STAGES` is now a\n frozen constant and the filter is inside `classify()`, because a caller that hands over every\n board is the normal mistake.\n **The fixture in `money-match.test.mjs` used a stage NAME where live data carries an ID.** Adding\n the filter turned nine tests red until it was corrected. MM-t now asserts every entry is a 36\n character id, because matching on a name would make this filter a silent no-op against production.\n- **`money-match.ts:76` overwrote instead of summing.** Two payments toward one booking produced two\n writes and one silently won. Live: Laurie Rubnitz, $120.00 and $90.00, both resolving to\n `7yES6q2kajVTQIK6tEx3`. `planWrites()` now groups by opportunity and writes the sum once, carrying\n the payment ids that made it up. Summing PRESERVES the total, so the $174,115.00 on Kim's page was\n always the correct figure and it was the code that had to catch up.\n The old bug self-sealed: once a wrong value was written the next run returned ALREADY_VALUED, so\n the lost money was unrecoverable without a manual audit.\n- **`valuedAfter.count` counted payments where it should count bookings.**\n\n## R35 (10 Aug 2026) — the ingestion layer that did not exist\n\n`money-match.ts` was imported by its own test and by nothing else. There was no call to\n`/payments/transactions` anywhere in `engine/`, `scripts/` or `build/`, so every figure on Kim's\nmoney page came from a process that was not in the repository, and the filters below were unwritten\nrather than misconfigured.\n\n`engine/payments-source.ts` is that layer. Separate module on purpose: MM-h asserts `fetch(` never\nappears in `money-match.ts`.\n\n- Accepts all five live source types including **`payment_link`**, which moves $0 today and would\n have reported the front desk's first day of takings as zero the moment the reusable links go live.\n- **An unrecognised source type is kept and reported, never dropped.**\n- **Filters on AMOUNT, not on source type.** 171 live rows are $0 booking artifacts, all status\n succeeded; 10 are sub-$1 card tests, all pending. Filtering `entitySourceType !== \"calendar\"` is\n the near miss: it leaves 13 zero rows standing, which is what invents a phantom payment collision.\n\n## R36 (10 Aug 2026) — copy that expires\n\nNine strings in `worklog.ts` and `decisions.ts` said \"this evening\", \"this morning\", \"last night\".\nThe page told Kim \"this evening\" every day forever. This was her oldest open item, promised as\nMonday's first job on 8 August and recorded as \"never reproduced\" for two days because nobody looked\nin the copy modules. All nine now read \"that evening\", \"that morning\", \"the night before\".\n`KC-dates` is a lint test that fails if any of the banned phrases returns to a copy module.\n\n\n## R37 (11 Aug 2026) — go-live prep: no-email guard, visible deferrals, state prune\n\n- **channelBar()**: one answer to \"may this channel be used\". Two causes kept separate because the\n journal must name WHICH: consent (dndSettings, R31) and ABSENCE (no email on the record). Logging\n absence as an opt-out misinforms the reader. Live driver: 2 of the 3 tagged contacts carry a phone\n and no email, and main-1 is an email; unguarded, that send 4xxs and retries hourly forever.\n Phone absence is not handled because every tagged contact carries a phone. Both polarities proven\n by calling it: tests/consent-guard.test.mjs CG-4/CG-5; fault injection goes red.\n- **Deferral visibility**: skip reasons were computed and discarded, so go-live day could not tell\n waiting from broken. Informative reasons now hit out.log and the journal (kind \"deferred\");\n bare not-due stays silent, skippedNotDue counts it.\n- **api.ts ?prune=**: admin-gated removal of one contact from puppy_state. Exists for one job:\n the ZZTEST dummy out before TEST_MODE flips.\n- **Process lesson (LESSONS.md #10)**: the first version of these tests landed in tests/harness.mjs,\n which run-all EXCLUDES as scaffolding — the most important tests of the week were running nowhere,\n and a stale E4 in that file had been red for days unseen. Tests now live in a discovered\n *.test.mjs; after adding a test, watch the suite count move.\n\n\n## R38 (11 Aug 2026) — the mode is a blob, because the env UI is a login away\n\nTEST_MODE was only settable in val.town's environment UI, and at go-live time that browser session\nwas logged out with nobody available to log in. Ten-routes rule applied: the v2 API has no\nenvironment endpoints (404 on every guess), tokens are val-file-scoped (403 on /v1/me and /v1/blob),\nand typing a password is out of bounds. So the mode moved to something a session can always reach:\n\n- `resolveMode(envVal, blobVal)` is pure and exported; all eight combinations tested (CG-7).\n Env var, if set, WINS, so the documented knob still works. Only boolean `true` in\n `puppy_mode.live` arms live; a string \"true\", a missing blob, a malformed blob are all practice.\n- `cron()` re-resolves at the very top of every pass, so one pass has one mode.\n- `api.ts ?arm=live|practice` (admin-gated) writes the blob and reads it back as the receipt.\n- Rollback gains a second lever: `?arm=practice` at next pass; the kill switch stays the instant one.\n\n\n## R39 (14 Aug 2026) — comment blocks moved out of main.ts to make room for the reachability fixes\n\nmain.ts was at 79,184 of the platform's hard 80,000-byte ceiling. Four narrative comment blocks\nwere moved here VERBATIM so the safety work below could land; each site keeps a one-line pointer.\nNothing was edited, only relocated. (`scripts/deploy.mjs` prints this exact instruction when the\nfile goes over: \"Move comments to NOTES-v1.4.md.\")\n\n### From `getBlobModule()`\n\n // Dynamic (not static like the PupsClub val) so this file's pure logic can be imported under Node +\n // tsx for local testing without resolving esm.town or needing a Deno runtime — under real\n // val.town/Deno execution this resolves identically, just on first call instead of at module load.\n\n### From `sendEmail()`\n\n // Body shape verified live this session (27 Jul 2026, against the sanctioned TEST_MODE dummy contact\n // / aizhigitovamir@gmail.com): {\"type\":\"Email\",\"contactId\",\"subject\",\"html\"} on Version 2021-04-15\n // (same API version as the proven SMS call) returned HTTP 201, {\"msg\":\"Email queued successfully.\",\n // \"messageId\":..., \"emailMessageId\":...}. The spec's own best-guess shape worked on the first\n // attempt — nothing needed adjusting.\n\nNote added 14 Aug: that response is the same `emailMessageId` the delivery reconciliation in\n`reachability.ts` now reads back from `GET /conversations/messages/email/{emailMessageId}`. It was\ndocumented in this comment from day one and discarded by the code for three weeks.\n\n### From `addTag()`\n\n // POST /contacts/{id}/tags is additive — verified live this session against the dummy contact (an\n // existing tag survived the call, response's tagsAdded confirmed the new one). Deliberately NOT using\n // /contacts/upsert with a tags array for this — upsert's tag merge-vs-replace behavior was never\n // tested and was not worth risking on a real contact's existing tag set.\n\n### From `createTask()`\n\n // Shape verified live this session against the dummy contact (HTTP 201, then confirmed via the\n // proven GET tasks read). assignedTo deliberately omitted rather than sent as JSON null — no\n // confirmed GHL user id for \"the hire\" exists yet in this engine's scope (same open gap\n // BUILD-CHECKLIST-UI.md already flags for its own tasks) — omitting the key tested clean.\n\n### From `applyDecision()`, the `advance_status` case\n\n // v1.2 — entering a branch always starts that branch's 2-message pass from the top. Matters for\n // the rule-6b re-entry paths (branch -> awaiting -> branch again for a NEW appointment): the\n // shared lastBranchStepSent counter would otherwise start a second branch pass mid-sequence\n // (or, worse, route a first branch_b pass to B2 because branch_a had already sent A1). A\n // repeated branch message only ever happens when a genuinely new no-show/decline occurred, so\n // the copy stays contextually true.\n\n### From `applyDecision()`, its preamble\n\n // Pure: given a Decision (already known to have succeeded, or to need no IO at all) and the current\n // state, returns the resulting state fields. No IO. This is the ONE place PuppyState transitions are\n // written, used by both cron() (after a successful send/task, or immediately for decisions with no\n // gating IO) and the local test harness (to simulate a full multi-day run without live network calls)\n // — kept as a single function specifically so the tested behavior and the shipped behavior cannot\n // silently drift apart from each other.\n\n## v1.10 (14 Aug 2026) — the wiring, the dead letters that could not come back, and the refusals that repeated\n\nSix defects found by an adversarial pass over the v1.9 tree. Recorded here because five of the six are\none-line call sites in main.ts and the reasoning does not fit next to them at 80,000 characters.\n\n### the wiring\nFive of v1.9's headline fixes could be DELETED from main.ts and the whole suite stayed 25/563/0 GREEN:\n`noPhone` at both Facts sites, `optOutRequested`, the `honourOptOut` call, and the `onDeliveryStatus`\ncall. The helpers in reachability.ts were tested thoroughly; the wiring from `cron()` into them was\ntested by nothing at all. `tests/wiring.test.mjs` now drives the real exported `cron()` against a fake\nfetch, a fake clock and a fake blob store, and asserts the observable outcome — an SMS that is never\nPOSTed, a DND PUT that is, a reconciliation read that happens. Each of those call sites was deleted in\na scratch copy of the tree and the suite confirmed RED before this was written down.\n\n### enrol refusals: which are terminal and which are not\n`enroll_refused` wrote a journal row and no state entry, so the same contact was refused on every run\nforever — 39 of the last 40 rows on Kim's live activity page were the identical sentence, hourly, for\ntwo days, and at ~24-30 rows a day the 2,000-row journal cap evicts all real history in about two\nmonths. `enrolmentBar`'s branch already had this right and said why: *the terminal entry, NOT the tag,\nis what stops this refusal repeating every run.* The same reasoning was not applied one line up.\n\nThe split is on whether the refusal can stop being true on its own:\n* **already a customer — TERMINAL, as `done_not_enrolled`.** Rule 4 hard-exits a customer on the\n first pass anyway, so enrolling them could only ever produce an immediate exit.\n NOT `done_customer`, which was the first attempt and was wrong: `api.ts:157` computes the WON tile\n as `byStatus.done_booked + byStatus.done_customer`, off the saved state. Somebody who was ALREADY a\n customer before the path touched them would have been added to the one number the client judges the\n system by — a sale this engine had nothing to do with, appearing on her page as one it won. A new\n terminal status says what actually happened instead, is counted in neither ACTIVE nor WON, and\n api.ts degrades safely on an unknown status (it renders a true sentence and reports the missing\n label back to us in `unlabelledStatuses`). It also cannot be resurrected by a re-tag, which is\n correct: a customer is not a lead. The residual cost is stated plainly — if Kim ever needs to\n nurture a lapsed customer she tagged while they were still a customer, a tag will not do it.\n The alternative was leaving them stateless and journalling once, like the live booking, and that\n was rejected because a permanent candidate jams the enrolment SURGE guard: 40 of them sitting in\n `rawCandidates` on every run exceeds the threshold of 25 and holds enrolment for everybody, forever.\n* **live booking already exists — TRANSIENT.** The booking may be cancelled tomorrow, and then they\n SHOULD enrol. So it must keep being re-evaluated, and it must NOT get a state entry — any state\n entry at all removes the contact from the candidate filter, which is the very bug being fixed. The\n repetition is stopped at the journal instead, by `refusedBefore`. The log line still prints every\n run (it is per-run output, not the 2,000-row history).\n\n### the dead letter that could never come back\nThe candidate filter was `!tags.includes(TAG_ENROLLED) && !state[c.id]`. A dead-lettered contact sits\nin state untouched — the per-contact loop `continue`s on any terminal status — so `lastCheckedAt`\nnever moves and `pruneState` only drops it after 60 days. Kim removing the tag, fixing the number and\nre-tagging produced zero candidates, which is exactly what the dead-letter task told her to do. Fixed\nby `reEnrollable` (reachability.ts), which is deliberately narrow twice over: only the two dead-letter\nstatuses, and only when the contact now has an email address or a phone number. A contact who is still\nunreachable is not a candidate at all — nothing was fixed, so re-admitting them would re-refuse them\nevery run, which is the journal-eating defect above wearing a different hat. `done_send_failed` cannot\nbe verified that way (a bad number looks exactly like a good one), so it is re-admitted with a fresh\nattempt budget; re-enrolment applies TAG_ENROLLED, and that is what stops it repeating.\n\n### the paused STOP\nThe lightweight paused-reply pass pinned `conversationCheckFailed: true` and never set\n`optOutRequested`, so a paused contact who later texted STOP was never detected: no DND write, and\nthey were released 14 days later as `done_hard_exit` for the wrong reason. Rule 1b outranks rule 5, so\nsetting `optOutRequested` on that pass reaches the hard exit while `conversationCheckFailed` still\nguarantees no send can happen on it. It costs one conversation read on a population that is small by\ndefinition. `honourOptOut` is called on that path too — the DND write is the whole point, and it is\nwhat silences Chloe, Ava and the 165 workflows as well.\n\n### From `cron()`'s Node/tsx shim\nVal.town/Deno provides a global `Deno`; this file is normally only ever loaded there. No Deno runtime\nwas available in the build/test session, so the local harness imports this exact file under Node.\nThe shim defines a minimal stand-in ONLY when `Deno` does not already exist. Under real val.town\nexecution `Deno` is already defined, the `if` is false, and the block never runs — zero effect on\ndeployed behaviour.\n\n### From `getReplyStatus()`, the unreadCount arm (R21)\nChloe, Ava and 165 workflows all send. A customer replies, an automated outbound lands seconds later,\nthe direction field flips, and the engine reads 'no reply'. `unreadCount` is the second signal:\noutbound does NOT clear it, so an unread thread means somebody wrote in and nobody looked — which must\nblock a send whatever the newest message was.\n\n### From `decideAction()`'s preamble\nPure function: no network, no side effects. Every rule is evaluated in order for every call — \"first\nmatch wins\" per spec, so a later rule never overrides an earlier one, and the SAME order runs for every\ncontact on every pass regardless of their current status. This is what the whole safety story rests on.\n\n\n=====FILE engine/REGISTER-AUG5.md =====\n# REGISTER ADDENDUM - fleet verification, late 5 Aug (ET)\n26-agent fleet (20 sonnet verify, 4 opus adversarial, 1 opus judge, ~62 min, 642 tool calls) against live data.\n\nCONFIRMED CLEAN: Thomas timeline (every timestamp), Kristina record (all five facts), census=1 Kristina,\nred flag x5 all DND, no x4 with two non-DND, follow-up 0, 40 distinct tags (full 5,562-contact walk),\nold puppy workflow still published (cutover premise), Tresa state (tags [phone], Pup Talk Aug 6 3:40,\nFTD booked), conversations 5,534 (message says five and a half thousand), 3 go-live blockers match page.\n\nFINDINGS AND RESOLUTIONS:\n1. Three source=workflow SMS hit Thomas AFTER the 6:30 PM removal (8:00, 8:05, 9:05 PM ET). Verified by\n hand: they are the BOOKED-path confirmations for his real Aug 15 session (confirmed + spots-held +\n details), triggered by his opportunity moving to booked at 8:00 PM. Correct message type for a booked\n customer; the chase type stayed stopped. Sent message's \"Nothing new will go to him\" is literally\n false as a result; bridge note corrects it.\n2. Adversarial sweep found 76 chase texts + 24 voicemails to 27 other contacts since 14 Apr. Checked the\n booked ones by hand: Luis Colon booked Jul 13, zero chase. Destinee Patterson chased 30 May while\n UNBOOKED (funnel's intended target), booked 4 Aug - the funnel converting, not the defect. Conclusion\n of the sent message stands as scoped: Thomas is the only person chased AFTER booking. Stronger\n evidence method than the calendar-sample cited in the message; noted here.\n3. \"That calendar holds three bookings in all\" was stale by one at send: Tresa booked 6:35 PM, message\n sent 7:54 PM. Materially harmless (the fourth is Tresa, whose story the message tells). Logged.\n4. \"Practice mode... sent nothing to anyone\": engine made one SMS API call on 5 Aug 12:40 PM ET to the\n ZZTEST dummy (unroutable, failed). True for real people; wording tightened in future copy. ENGINE\n HARDENING QUEUED: add TEST_MODE guard at the sendSms call site (safety currently via contact scoping).\n5. \"Computed fresh each year\" (Thanksgiving) describes the deposit plan not yet built; present tense ran\n ahead of reality again. Building the reader includes the fourth-Thursday computation.\n6. Red flag DND nuance: 4 of 5 silenced by the workflow from clean state; the fifth (no-name record) had\n SMS-blocked themselves 20 Jul, workflow extended it to all channels 4 Aug. Message's claim literally true.\n7. Chase funnel \"Free Training Day abandoned booking\" remains PUBLISHED. Fix proposed to Kim in the sent\n message; her call, not taken unilaterally.\n8. Disk reverted to the Aug 4 snapshot a third time mid-fleet; twelve slices reported artifacts missing.\n Kim's copies live on Upwork (hash-verified before send) and everything regenerates from the val bundle\n (v203/204). Local file absence is an environment artifact, not a delivery failure.\n\n","createdAt",["D",1789560810658],"branchVersion","branchId","551774fb-a850-4c9d-94a1-d3509ddcf1b0","id","1bfa6e81-74e1-4c6c-ab32-118304a4ffff","dogsspot_puppy_path",["D",1785429259053],"deletedAt","legacyEnvVars",false,"privacy","public","httpPrivacy","description","Puppy path nurture engine v1.2 — The Dogs Spot","imageUrl","d26e64e6-cd39-4be1-b5b4-1de11cc555f8","pinnedFileId","ad633fec-8e73-11f1-b800-1607ee4eb77e","pinPreview","pinMigrated","screenshotVersion","likeCount",0,"orgId","019f56fd-bd59-724f-8163-80ffcf8235dd","tursoName","1bfa6e8174e14c6cab32118304a4ffff","tursoHostname","1bfa6e8174e14c6cab32118304a4ffff-val-town.aws-us-east-2.turso.io","tursoMeasuredAt",["D",1789519842404],"pinned","userPerm","r","valPerm","blobPerm","rw","emailPerm","sqlitePerm","projectPerm","telemetryPerm","user",{"_98":97,"_106":102},"org",{"_98":97,"_99":100,"_101":102,"_18":54,"_103":104,"_105":47},"branch",{"_13":87,"_32":88,"_41":40,"_89":42,"_90":-5,"_91":-5,"_92":-5,"_93":-5,"_94":-5,"_95":43,"_96":97},"isOwned",1280,"main","projectId","forkedBranchId","forkedBranchVersion","forkedProjectPrivacy","forkedProjectId","forkedProjectOrgId","projectName","userHandle","amir5","handle","displayName","Amir","avatar","https://lh3.googleusercontent.com/a/ACg8ocILk3bwhcvrzozUWm7gxlKoBm7ZGtsgIkesW3ysOOsJ1rSQuA=s96-c","tier","free","canRestrictVals","profileImageUrl","branchName","","adoptOrgId",{"_41":42,"_32":43,"_36":1257,"_45":-5,"_46":47,"_48":49,"_50":49,"_51":52,"_53":-5,"_18":54,"_55":56,"_57":25,"_58":-5,"_59":-5,"_60":61,"_62":63,"_64":65,"_66":67,"_68":1258,"_70":-5,"_71":72,"_73":72,"_74":75,"_76":75,"_77":75,"_78":72,"_79":72,"_80":1259,"_82":1260,"_84":1261,"_86":47},"tree",[896,897,898,899,900,901,902,903,904,905,906,907,908,909,910,911,912,913,914,915,916,917,918,919,920,921,922,923,924,925,926,927,928,929,930,931,932,933,934,935,936,937,938,939,940,941,942,943,944,945,946,947,948,949,950,951,952,953,954,955,956,957,958,959,960,961,962,963,964,965,966,967,968,969,970,971,972,973,974,975,976,977,978,979,980,981,982,983,984,985],"files",[896,897,898,899,900,901,902,903,904,905,906,907,908,909,910,911,912,913,914,915,916,917,918,919,920,921,922,923,924,925,926,927,928,929,930,931,932,933,934,935,936,937,938,939,940,941,942,943,944,945,946,947,948,949,950,951,952,953,954,955,956,957,958,959,960,961,962,963,964,965,966,967,968,969,970,971,972,973,974,975,976,977,978,979,980,981,982,983,984,985],"counts",{"_886":61,"_887":278,"_888":61,"_889":890,"_891":892},"contents",[129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218],"upstreamProject","upstreamBranch","emptyEnvVars","flags",[],"hasHttpFiles","grants","orgs","customDomains",{},{"_41":879,"_32":880,"_30":881,"_222":-5,"_39":40,"_38":882,"_224":25,"_36":883,"_13":61,"_33":20,"_34":884,"_24":47,"_229":-5,"_27":885},{"_41":872,"_32":873,"_30":874,"_222":-5,"_39":40,"_38":875,"_224":25,"_36":876,"_13":253,"_33":227,"_34":877,"_24":47,"_229":-5,"_27":878},{"_41":865,"_32":866,"_30":867,"_222":-5,"_39":40,"_38":868,"_224":25,"_36":869,"_13":270,"_33":20,"_34":870,"_24":47,"_229":-5,"_27":871},{"_41":858,"_32":859,"_30":860,"_222":-5,"_39":40,"_38":861,"_224":25,"_36":862,"_13":61,"_33":20,"_34":863,"_24":47,"_229":-5,"_27":864},{"_41":850,"_32":851,"_30":852,"_222":-5,"_39":40,"_38":853,"_224":47,"_36":854,"_13":855,"_33":20,"_34":856,"_24":47,"_229":-5,"_27":857},{"_41":842,"_32":843,"_30":844,"_222":-5,"_39":40,"_38":845,"_224":47,"_36":846,"_13":847,"_33":20,"_34":848,"_24":47,"_229":-5,"_27":849},{"_41":834,"_32":835,"_30":836,"_222":-5,"_39":40,"_38":837,"_224":47,"_36":838,"_13":839,"_33":20,"_34":840,"_24":47,"_229":-5,"_27":841},{"_41":826,"_32":827,"_30":828,"_222":-5,"_39":40,"_38":829,"_224":47,"_36":830,"_13":831,"_33":20,"_34":832,"_24":47,"_229":-5,"_27":833},{"_41":818,"_32":819,"_30":820,"_222":-5,"_39":40,"_38":821,"_224":47,"_36":822,"_13":823,"_33":20,"_34":824,"_24":47,"_229":-5,"_27":825},{"_41":811,"_32":812,"_30":813,"_222":-5,"_39":40,"_38":814,"_224":47,"_36":815,"_13":396,"_33":20,"_34":816,"_24":47,"_229":-5,"_27":817},{"_41":803,"_32":804,"_30":805,"_222":-5,"_39":40,"_38":806,"_224":47,"_36":807,"_13":808,"_33":20,"_34":809,"_24":47,"_229":-5,"_27":810},{"_41":796,"_32":797,"_30":798,"_222":-5,"_39":40,"_38":799,"_224":47,"_36":800,"_13":505,"_33":20,"_34":801,"_24":47,"_229":-5,"_27":802},{"_41":789,"_32":790,"_30":791,"_222":-5,"_39":40,"_38":792,"_224":47,"_36":793,"_13":359,"_33":20,"_34":794,"_24":47,"_229":-5,"_27":795},{"_41":782,"_32":783,"_30":784,"_222":-5,"_39":40,"_38":785,"_224":47,"_36":786,"_13":764,"_33":20,"_34":787,"_24":47,"_229":-5,"_27":788},{"_41":774,"_32":775,"_30":776,"_222":-5,"_39":40,"_38":777,"_224":47,"_36":778,"_13":779,"_33":20,"_34":780,"_24":47,"_229":-5,"_27":781},{"_41":767,"_32":768,"_30":769,"_222":-5,"_39":40,"_38":770,"_224":47,"_36":771,"_13":301,"_33":20,"_34":772,"_24":47,"_229":-5,"_27":773},{"_41":759,"_32":760,"_30":761,"_222":-5,"_39":40,"_38":762,"_224":47,"_36":763,"_13":764,"_33":20,"_34":765,"_24":47,"_229":-5,"_27":766},{"_41":752,"_32":753,"_30":754,"_222":-5,"_39":40,"_38":755,"_224":47,"_36":756,"_13":301,"_33":20,"_34":757,"_24":47,"_229":-5,"_27":758},{"_41":745,"_32":746,"_30":747,"_222":-5,"_39":40,"_38":748,"_224":47,"_36":749,"_13":671,"_33":20,"_34":750,"_24":47,"_229":-5,"_27":751},{"_41":738,"_32":739,"_30":740,"_222":-5,"_39":40,"_38":741,"_224":47,"_36":742,"_13":330,"_33":20,"_34":743,"_24":47,"_229":-5,"_27":744},{"_41":731,"_32":732,"_30":733,"_222":-5,"_39":40,"_38":734,"_224":47,"_36":735,"_13":330,"_33":20,"_34":736,"_24":47,"_229":-5,"_27":737},{"_41":724,"_32":725,"_30":726,"_222":-5,"_39":40,"_38":727,"_224":47,"_36":728,"_13":330,"_33":20,"_34":729,"_24":47,"_229":-5,"_27":730},{"_41":717,"_32":718,"_30":719,"_222":-5,"_39":40,"_38":720,"_224":47,"_36":721,"_13":330,"_33":20,"_34":722,"_24":47,"_229":-5,"_27":723},{"_41":710,"_32":711,"_30":712,"_222":-5,"_39":40,"_38":713,"_224":47,"_36":714,"_13":671,"_33":20,"_34":715,"_24":47,"_229":-5,"_27":716},{"_41":703,"_32":704,"_30":705,"_222":-5,"_39":40,"_38":706,"_224":47,"_36":707,"_13":330,"_33":20,"_34":708,"_24":47,"_229":-5,"_27":709},{"_41":695,"_32":696,"_30":697,"_222":-5,"_39":40,"_38":698,"_224":47,"_36":699,"_13":700,"_33":20,"_34":701,"_24":47,"_229":-5,"_27":702},{"_41":688,"_32":689,"_30":690,"_222":-5,"_39":40,"_38":691,"_224":47,"_36":692,"_13":330,"_33":20,"_34":693,"_24":47,"_229":-5,"_27":694},{"_41":681,"_32":682,"_30":683,"_222":-5,"_39":40,"_38":684,"_224":47,"_36":685,"_13":330,"_33":20,"_34":686,"_24":47,"_229":-5,"_27":687},{"_41":674,"_32":675,"_30":676,"_222":-5,"_39":40,"_38":677,"_224":47,"_36":678,"_13":330,"_33":20,"_34":679,"_24":47,"_229":-5,"_27":680},{"_41":666,"_32":667,"_30":668,"_222":-5,"_39":40,"_38":669,"_224":47,"_36":670,"_13":671,"_33":20,"_34":672,"_24":47,"_229":-5,"_27":673},{"_41":659,"_32":660,"_30":661,"_222":-5,"_39":40,"_38":662,"_224":47,"_36":663,"_13":330,"_33":20,"_34":664,"_24":47,"_229":-5,"_27":665},{"_41":652,"_32":653,"_30":654,"_222":-5,"_39":40,"_38":655,"_224":47,"_36":656,"_13":330,"_33":20,"_34":657,"_24":47,"_229":-5,"_27":658},{"_41":645,"_32":646,"_30":647,"_222":-5,"_39":40,"_38":648,"_224":47,"_36":649,"_13":262,"_33":20,"_34":650,"_24":47,"_229":-5,"_27":651},{"_41":638,"_32":639,"_30":640,"_222":-5,"_39":40,"_38":641,"_224":47,"_36":642,"_13":262,"_33":20,"_34":643,"_24":47,"_229":-5,"_27":644},{"_41":631,"_32":632,"_30":633,"_222":-5,"_39":40,"_38":634,"_224":47,"_36":635,"_13":236,"_33":20,"_34":636,"_24":47,"_229":-5,"_27":637},{"_41":624,"_32":625,"_30":626,"_222":-5,"_39":40,"_38":627,"_224":47,"_36":628,"_13":236,"_33":20,"_34":629,"_24":47,"_229":-5,"_27":630},{"_41":616,"_32":617,"_30":618,"_222":-5,"_39":40,"_38":619,"_224":47,"_36":620,"_13":621,"_33":20,"_34":622,"_24":47,"_229":-5,"_27":623},{"_41":609,"_32":610,"_30":611,"_222":-5,"_39":40,"_38":612,"_224":47,"_36":613,"_13":253,"_33":20,"_34":614,"_24":47,"_229":-5,"_27":615},{"_41":602,"_32":603,"_30":604,"_222":-5,"_39":40,"_38":605,"_224":47,"_36":606,"_13":61,"_33":20,"_34":607,"_24":47,"_229":-5,"_27":608},{"_41":595,"_32":596,"_30":597,"_222":-5,"_39":40,"_38":598,"_224":47,"_36":599,"_13":61,"_33":20,"_34":600,"_24":47,"_229":-5,"_27":601},{"_41":588,"_32":589,"_30":590,"_222":-5,"_39":40,"_38":591,"_224":47,"_36":592,"_13":61,"_33":20,"_34":593,"_24":47,"_229":-5,"_27":594},{"_41":581,"_32":582,"_30":583,"_222":-5,"_39":40,"_38":584,"_224":47,"_36":585,"_13":61,"_33":20,"_34":586,"_24":47,"_229":-5,"_27":587},{"_41":574,"_32":575,"_30":576,"_222":-5,"_39":40,"_38":577,"_224":47,"_36":578,"_13":61,"_33":20,"_34":579,"_24":47,"_229":-5,"_27":580},{"_41":567,"_32":568,"_30":569,"_222":-5,"_39":40,"_38":570,"_224":47,"_36":571,"_13":61,"_33":20,"_34":572,"_24":47,"_229":-5,"_27":573},{"_41":560,"_32":561,"_30":562,"_222":-5,"_39":40,"_38":563,"_224":47,"_36":564,"_13":61,"_33":20,"_34":565,"_24":47,"_229":-5,"_27":566},{"_41":553,"_32":554,"_30":555,"_222":-5,"_39":40,"_38":556,"_224":47,"_36":557,"_13":527,"_33":20,"_34":558,"_24":47,"_229":-5,"_27":559},{"_41":545,"_32":546,"_30":547,"_222":-5,"_39":40,"_38":548,"_224":47,"_36":549,"_13":550,"_33":20,"_34":551,"_24":47,"_229":-5,"_27":552},{"_41":537,"_32":538,"_30":539,"_222":-5,"_39":40,"_38":540,"_224":47,"_36":541,"_13":542,"_33":20,"_34":543,"_24":47,"_229":-5,"_27":544},{"_41":530,"_32":531,"_30":532,"_222":-5,"_39":40,"_38":533,"_224":47,"_36":534,"_13":470,"_33":20,"_34":535,"_24":47,"_229":-5,"_27":536},{"_41":522,"_32":523,"_30":524,"_222":-5,"_39":40,"_38":525,"_224":47,"_36":526,"_13":527,"_33":20,"_34":528,"_24":47,"_229":-5,"_27":529},{"_41":515,"_32":516,"_30":517,"_222":-5,"_39":40,"_38":518,"_224":25,"_36":519,"_13":61,"_33":227,"_34":520,"_24":47,"_229":-5,"_27":521},{"_41":508,"_32":509,"_30":510,"_222":-5,"_39":40,"_38":511,"_224":25,"_36":512,"_13":253,"_33":245,"_34":513,"_24":47,"_229":-5,"_27":514},{"_41":501,"_32":502,"_30":56,"_222":-5,"_39":40,"_38":503,"_224":25,"_36":504,"_13":505,"_33":245,"_34":506,"_24":47,"_229":-5,"_27":507},{"_41":494,"_32":495,"_30":496,"_222":-5,"_39":40,"_38":497,"_224":25,"_36":498,"_13":61,"_33":227,"_34":499,"_24":47,"_229":-5,"_27":500},{"_41":487,"_32":488,"_30":489,"_222":-5,"_39":40,"_38":490,"_224":25,"_36":491,"_13":262,"_33":227,"_34":492,"_24":47,"_229":-5,"_27":493},{"_41":480,"_32":481,"_30":482,"_222":-5,"_39":40,"_38":483,"_224":25,"_36":484,"_13":278,"_33":227,"_34":485,"_24":47,"_229":-5,"_27":486},{"_41":473,"_32":474,"_30":475,"_222":-5,"_39":40,"_38":476,"_224":25,"_36":477,"_13":61,"_33":227,"_34":478,"_24":47,"_229":-5,"_27":479},{"_41":465,"_32":466,"_30":467,"_222":-5,"_39":40,"_38":468,"_224":25,"_36":469,"_13":470,"_33":245,"_34":471,"_24":47,"_229":-5,"_27":472},{"_41":457,"_32":458,"_30":459,"_222":-5,"_39":40,"_38":460,"_224":25,"_36":461,"_13":462,"_33":227,"_34":463,"_24":47,"_229":-5,"_27":464},{"_41":450,"_32":451,"_30":452,"_222":-5,"_39":40,"_38":453,"_224":25,"_36":454,"_13":236,"_33":254,"_34":455,"_24":47,"_229":-5,"_27":456},{"_41":442,"_32":443,"_30":444,"_222":-5,"_39":40,"_38":445,"_224":25,"_36":446,"_13":447,"_33":245,"_34":448,"_24":47,"_229":-5,"_27":449},{"_41":435,"_32":436,"_30":437,"_222":-5,"_39":40,"_38":438,"_224":25,"_36":439,"_13":61,"_33":227,"_34":440,"_24":47,"_229":-5,"_27":441},{"_41":427,"_32":428,"_30":429,"_222":-5,"_39":40,"_38":430,"_224":25,"_36":431,"_13":432,"_33":227,"_34":433,"_24":47,"_229":-5,"_27":434},{"_41":420,"_32":421,"_30":422,"_222":-5,"_39":40,"_38":423,"_224":25,"_36":424,"_13":330,"_33":245,"_34":425,"_24":47,"_229":-5,"_27":426},{"_41":413,"_32":414,"_30":415,"_222":-5,"_39":40,"_38":416,"_224":25,"_36":417,"_13":301,"_33":227,"_34":418,"_24":47,"_229":-5,"_27":419},{"_41":406,"_32":407,"_30":408,"_222":-5,"_39":40,"_38":409,"_224":25,"_36":410,"_13":301,"_33":245,"_34":411,"_24":47,"_229":-5,"_27":412},{"_41":399,"_32":400,"_30":401,"_222":-5,"_39":40,"_38":402,"_224":25,"_36":403,"_13":244,"_33":245,"_34":404,"_24":47,"_229":-5,"_27":405},{"_41":391,"_32":392,"_30":393,"_222":-5,"_39":40,"_38":394,"_224":25,"_36":395,"_13":396,"_33":227,"_34":397,"_24":47,"_229":-5,"_27":398},{"_41":384,"_32":385,"_30":386,"_222":-5,"_39":40,"_38":387,"_224":25,"_36":388,"_13":253,"_33":227,"_34":389,"_24":47,"_229":-5,"_27":390},{"_41":376,"_32":377,"_30":378,"_222":-5,"_39":40,"_38":379,"_224":25,"_36":380,"_13":381,"_33":254,"_34":382,"_24":47,"_229":-5,"_27":383},{"_41":369,"_32":370,"_30":371,"_222":-5,"_39":40,"_38":372,"_224":25,"_36":373,"_13":253,"_33":227,"_34":374,"_24":47,"_229":-5,"_27":375},{"_41":362,"_32":363,"_30":364,"_222":-5,"_39":40,"_38":365,"_224":25,"_36":366,"_13":278,"_33":227,"_34":367,"_24":47,"_229":-5,"_27":368},{"_41":354,"_32":355,"_30":356,"_222":-5,"_39":40,"_38":357,"_224":25,"_36":358,"_13":359,"_33":245,"_34":360,"_24":47,"_229":-5,"_27":361},{"_41":347,"_32":348,"_30":349,"_222":-5,"_39":40,"_38":350,"_224":25,"_36":351,"_13":278,"_33":227,"_34":352,"_24":47,"_229":-5,"_27":353},{"_41":340,"_32":341,"_30":342,"_222":-5,"_39":40,"_38":343,"_224":25,"_36":344,"_13":278,"_33":227,"_34":345,"_24":47,"_229":-5,"_27":346},{"_41":333,"_32":334,"_30":335,"_222":-5,"_39":40,"_38":336,"_224":25,"_36":337,"_13":244,"_33":227,"_34":338,"_24":47,"_229":-5,"_27":339},{"_41":325,"_32":326,"_30":327,"_222":-5,"_39":40,"_38":328,"_224":25,"_36":329,"_13":330,"_33":227,"_34":331,"_24":47,"_229":-5,"_27":332},{"_41":318,"_32":319,"_30":320,"_222":-5,"_39":40,"_38":321,"_224":25,"_36":322,"_13":244,"_33":227,"_34":323,"_24":47,"_229":-5,"_27":324},{"_41":311,"_32":312,"_30":313,"_222":-5,"_39":40,"_38":314,"_224":25,"_36":315,"_13":278,"_33":227,"_34":316,"_24":47,"_229":-5,"_27":317},{"_41":304,"_32":305,"_30":306,"_222":-5,"_39":40,"_38":307,"_224":25,"_36":308,"_13":61,"_33":227,"_34":309,"_24":47,"_229":-5,"_27":310},{"_41":296,"_32":297,"_30":298,"_222":-5,"_39":40,"_38":299,"_224":25,"_36":300,"_13":301,"_33":227,"_34":302,"_24":47,"_229":-5,"_27":303},{"_41":288,"_32":289,"_30":290,"_222":-5,"_39":40,"_38":291,"_224":25,"_36":292,"_13":293,"_33":245,"_34":294,"_24":47,"_229":-5,"_27":295},{"_41":281,"_32":282,"_30":283,"_222":-5,"_39":40,"_38":284,"_224":25,"_36":285,"_13":253,"_33":245,"_34":286,"_24":47,"_229":-5,"_27":287},{"_41":273,"_32":274,"_30":275,"_222":-5,"_39":40,"_38":276,"_224":25,"_36":277,"_13":278,"_33":227,"_34":279,"_24":47,"_229":-5,"_27":280},{"_41":265,"_32":266,"_30":267,"_222":-5,"_39":40,"_38":268,"_224":25,"_36":269,"_13":270,"_33":227,"_34":271,"_24":47,"_229":-5,"_27":272},{"_41":257,"_32":258,"_30":259,"_222":-5,"_39":40,"_38":260,"_224":25,"_36":261,"_13":262,"_33":245,"_34":263,"_24":47,"_229":-5,"_27":264},{"_41":248,"_32":249,"_30":250,"_222":-5,"_39":40,"_38":251,"_224":25,"_36":252,"_13":253,"_33":254,"_34":255,"_24":47,"_229":-5,"_27":256},{"_41":239,"_32":240,"_30":241,"_222":-5,"_39":40,"_38":242,"_224":25,"_36":243,"_13":244,"_33":245,"_34":246,"_24":47,"_229":-5,"_27":247},{"_41":231,"_32":232,"_30":233,"_222":-5,"_39":40,"_38":234,"_224":25,"_36":235,"_13":236,"_33":227,"_34":237,"_24":47,"_229":-5,"_27":238},{"_41":219,"_32":220,"_30":221,"_222":-5,"_39":40,"_38":223,"_224":25,"_36":225,"_13":226,"_33":227,"_34":228,"_24":47,"_229":-5,"_27":230},"07bbc883-3657-42ce-a700-629b0024a8cb","worklog.ts","facd3ee8-9028-11f1-8d98-1607ee4eb77e","parentId",1117,"latest",["D",1786812154376],39,"script","// THE WORK LOG — what changed, what broke, what got fixed. v1.0, 4 Aug 2026.\n//\n// WHY: Kim's dashboard answers \"is it working\" from live data. It cannot answer \"what have you\n// actually been doing\" or \"did something break last week\" from live data, because those are\n// events, not states. This file is the event trail: append-only, plain English, dated.\n//\n// THE RULE: every entry describes something that DEMONSTRABLY happened, with the evidence\n// alongside it. No entry is written for work that was merely intended. If a claim here cannot\n// be checked, it does not go here. Kim reads this; it is the receipts column of the retainer.\n//\n// TWO SOURCES:\n// 1. SEEDED (below): work done by hand, each line traceable to a verification run.\n// 2. AUTOMATIC: the watchdog appends \"broke\"/\"recovered\" pairs to the `tds_worklog` blob, so\n// an outage at 3am and its recovery both appear without anyone remembering to write them.\n\nexport type WorkEntry = {\n at: string; // ISO date (day precision is fine; this is a human timeline)\n // v1.2. A reader noticed that \"Fixed: this page used to state a number nobody measured\" (mine)\n // and \"Fixed: your website was charging half the deposit\" (hers, worth thousands) wore the same\n // label in the same colour, so my errors were hiding among her wins. `mine` is now its own kind\n // and its own word. Her words: \"Separate the two columns and I'll trust the page more, not less.\"\n kind: \"fixed\" | \"built\" | \"found\" | \"broke\" | \"recovered\" | \"changed\" | \"mine\";\n what: string; // one plain sentence, Kim's vocabulary\n evidence?: string; // how it was checked. Optional only for \"broke\" (the alarm IS the evidence)\n};\n\n// Seeded history. Everything below was verified on the date shown; the evidence column names\n// the check. Newest first is handled by the renderer, so this list stays chronological.\nexport const SEEDED: WorkEntry[] = [\n {\n at: \"2026-07-30\",\n kind: \"built\",\n what: \"The puppy follow-up system was built and switched into practice mode, where it does everything except actually send.\",\n evidence: \"It has been running on its own since, writing down every decision it makes. Its first practice run is still on file.\",\n },\n {\n at: \"2026-08-02\",\n kind: \"built\",\n what: \"Candace's welcome email was written and sent so she could start on the phones with the full picture.\",\n evidence: \"Sent 2 August; it is in the sent folder.\",\n },\n {\n at: \"2026-08-02\",\n kind: \"found\",\n what: \"Your website was charging a $250 Bootcamp deposit instead of $500. It was hidden inside the booking form's own settings, which is why nobody could find it.\",\n evidence: \"Fixed and published; the whole live site was then searched for '$250' and it appears nowhere.\",\n },\n {\n at: \"2026-08-02\",\n kind: \"found\",\n what: \"There are 17 Bootcamp bookings on record, from 19 December to 25 July, every one of them taken while the deposit was set to $250. What is not yet known is which of them actually paid one, and that means matching each booking against the payment records.\",\n evidence: \"Counted from your own booking records. An earlier version of this note asked you for a payment permission to finish the job; that was wrong and it is corrected here, because you had already granted it and it has been working since 1 August. Matching the bookings to the payments is work rather than a blocker, and it has not been done yet.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"fixed\",\n what: \"29 people who had texted STOP were never marked do-not-contact in the CRM, so they could still have been messaged.\",\n evidence: \"All 29 marked, then all 29 read back one at a time through the CRM's own records on 4 August. 29 of 29 confirmed, none missed.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"mine\",\n what: \"Three of the people who had texted STOP were on a call list I had already sent to your front desk. That was my mistake. The list was pulled and rebuilt the same day, but whether anyone had already called those three is not something I can see from here, and it is worth asking the desk.\",\n evidence: \"The rebuilt list has every STOP and every gate arrival removed, with a second tab naming exactly who came off it and why. The three names are in that tab, so the desk can be asked about those three specifically.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"changed\",\n what: \"The puppy follow-up messages were updated with your notes: the toy advice now explains the why, and the Pup Talk asks came down from six to four.\",\n evidence: \"The PDF you signed off was generated straight from the live system, not from a draft.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"built\",\n what: \"The slow track you asked for is built: weekly for a month, then every two weeks for six months, then monthly. No sales asks anywhere on it.\",\n evidence: \"29 messages, all written out in the PDF for your sign-off. Nothing sends until you say go.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"mine\",\n what: \"The follow-up system was running slightly older wording than the version you approved. It now runs exactly what you read.\",\n evidence: \"Compared the live wording against the wording you approved, character by character; they now match.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"fixed\",\n what: \"A security review found that text typed by a customer into their own name could end up treated as code inside an email we send, rather than as words. Nobody had done it, and it cannot happen now. Two other holes were found and closed in the same review, one of them in the key that protects the page you are reading.\",\n evidence: \"It came out of an adversarial review alongside two other security findings, and each of the three now has its own automatic check, and those checks are run before anything goes anywhere near your account. For this one that means names holding dollar signs, angle brackets, quotes and stray markup. The old page key was checked afterwards and is dead.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"built\",\n // [was: \"...looks over the whole setup ON A TIMER and raises an alarm...\". Every word about\n // what it checks was verified and still stands. The two words about the timer were not, and\n // on 5 August the timer turned out never to have fired. Kim has read this line. It is\n // corrected here rather than deleted, and the 5 August entry above carries the current state.]\n what: \"A second, separate system now looks over the whole setup and raises an alarm if anything stops working, including if somebody else quietly changes one of your CRM automations.\",\n evidence: \"Run live and watched end to end. It takes a fingerprint of your CRM automations each time it looks, so a change to any one of them shows up as a change rather than as silence. What was NOT checked at the time was whether it starts itself on a schedule. It does not; see 5 August.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"found\",\n what: \"Your CRM still has an old puppy follow-up automation switched on. If our new one went live alongside it, new inquiries would get two sets of messages from you on the same day.\",\n evidence: \"Read all 165 automations in your account. Switching ours on and that one off has to happen together, and it needs your say-so.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"found\",\n what: \"Your CRM records where nearly every inquiry came from, but not in the column it shows you. The column you can see is blank for four out of five people; the record underneath places all of them.\",\n evidence: \"Checked across a full week of inquiries: the column you can see named about one in five of them, the record underneath named every single one. That is where the Facebook and Instagram numbers above come from, and they are recounted every time you open this page.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"mine\",\n what: \"This page used to tell you the follow-up system checks in every 15 minutes. Nobody had ever measured that, and it was not true. It now times itself and reports the rhythm it actually keeps.\",\n evidence: \"The page was saying 'last checked 26 minutes ago' and 'it runs every 15 minutes' at the same time, which cannot both be right. It now measures the gaps between runs and reports what it sees.\",\n },\n {\n at: \"2026-08-01\",\n kind: \"mine\",\n what: \"I sent you a draft of the follow-up messages as though it were the finished thing, and you spent an evening reading the wrong version. That was mine, and the replacement was generated from the live system so it could not happen the same way twice.\",\n evidence: \"Every write-up you have had since is generated from the running system rather than typed, so what you read is what would send.\",\n },\n {\n at: \"2026-08-02\",\n kind: \"mine\",\n what: \"I gave you a missed-calls figure that was too high, because it was counting people arriving at the gate as well as people calling. You spotted it before I did.\",\n evidence: \"Recounted with gate arrivals excluded, and the same exclusion now runs on every list that comes out of here.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"mine\",\n what: \"I told you a list had been deleted and then left the old one sitting in your Drive for a day. Two versions of the same list is exactly the confusion I was trying to save you from.\",\n evidence: \"The old one is in the trash and the folder was checked afterwards; only one version exists.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"mine\",\n what: \"You asked me something at 8:20 that morning and my reply at 8:27 answered everything except that. Answered since.\",\n evidence: \"Both messages re-read against each other so the gap could be found rather than assumed.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"found\",\n what: \"Once it was measured, the follow-up system turned out to be running about hourly and the watchdog slower still, rather than four times an hour as this page used to claim. Nothing is harmed by that, because the messages are scheduled by the day, but it was worth knowing rather than assuming.\",\n evidence: \"Both were watched without being touched, then run by hand to confirm the code itself was healthy. Both ran cleanly. Do not read the rhythm off this line: the health card above measures the gaps between actual runs and prints what it currently observes, which is the only figure either of us should trust.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"mine\",\n what: \"The count of new customers on this page was reading low. It was looking at only the most recent slice of your records, which missed anyone who first got in touch a while ago and only became a customer this week.\",\n evidence: \"The whole Customer list is now read every time rather than the first slice of it, in about a second. For the last seven days that changed the figure from 2 to 5.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"found\",\n what: \"The second system that checks the first one was set to look once a day, not once an hour. It has been changed to hourly. Nothing was broken; it was just looking far less often than the things it watches can go wrong.\",\n evidence: \"Read off its own settings screen: it said once every 1 days, and its last run had been 13 hours earlier. The follow-up system runs on the hour, so a problem starting just after the checker looked could have sat unnoticed until the next day. It now runs hourly, which matches what it is checking. Everything it looks at was still being looked at throughout.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"mine\",\n what: \"This page told you the checker runs itself about every 95 minutes. That came from the times Amir had started it by hand, so it was a real measurement of the wrong thing. I then went further and wrote that its timer was not firing at all. That was wrong twice over: it was firing, and the only reason my new counter showed nothing was that the counter itself was broken.\",\n evidence: \"The two kinds of run are recorded separately now, and both were watched working before this was written: a scheduled run recorded as scheduled, a hand-started one as by hand. The page no longer guesses at causes either. It reports what it has and has not seen and leaves the diagnosing to a person, which is what I should have done before writing that sentence the first time.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"mine\",\n what: \"Two of our systems were describing the same pile of unmatched counter sales with different figures. One said 35 sales worth $23,463.99, the other said 40 worth $28,035.99.\",\n evidence: \"The payment records were counted again from scratch, a third time and by a different method: 40 is correct. The lower figure came from skipping some sales and from subtracting two things that were not the same kind of thing. Both systems now read the same single count, so they cannot disagree again.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"found\",\n what: \"On your missing call transcripts, a correction of ours. This page said earlier that day that transcription had never been switched on. That was wrong: a call from that morning was opened and its full written transcript was watched rendering. Transcription works, at least sometimes, so the real question is which calls are missing theirs.\",\n evidence: \"The wrong version was reasoned from the reading connection, which never carries transcripts, and that gap was mistaken for the transcripts not existing. The corrected question is on the list above: one example from Kim of a call that should have a transcript and does not is the fastest way to pin down the pattern.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"built\",\n what: \"The missing third step is built. Something now works out which of your inquiries is about a puppy, and it runs alongside everything else so you can see what it would do before it does anything.\",\n evidence: \"It has applied nothing and it cannot: the part that decides has no way to change anything in your account, which is checked automatically. Its first run over your most recent contacts is on the question list above, with its own numbers. A full pass over 1,200 of your records is written up separately for Amir to check line by line.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"mine\",\n what: \"My first attempt at spotting a puppy inquiry would have signed up three people who should not have been: a man asking to buy a puppy, a woman rehoming her older dogs, and a dog described as three years and four months old that got read as four months.\",\n evidence: \"Each of those three is now a rule, each rule has a test, and each test has a check that breaks the rule on purpose and demands the test notice. None of them reached anybody, because nothing has been switched on.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"found\",\n what: \"One of your knowledge bases was edited at around half past ten the night before, and nothing was keeping an eye on it. If that was you, everything is fine and this is just us noticing.\",\n evidence: \"The consolidated one, which is what Chloe answers customers from. Nothing on our side touched it. Until the following morning we were watching your 165 automations for changes but not the documents that decide what your business actually says, which was a gap.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"built\",\n what: \"Your knowledge bases are now watched the same way your automations are. If one of them changes, it gets written down with what moved and when, whoever did it.\",\n evidence: \"Running live. It cannot read the wording inside the documents, only that something changed and which one, so it will not police your writing. The part that spots a change is tested on its own, including the case that matters most: a document edited in place, where nothing is added and nothing is removed.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"mine\",\n what: \"The counter I built to prove the checker keeps its own time was itself broken, and it made a healthy system look dead. It recorded nothing for scheduled runs, so the page reported none had happened while they were happening every hour.\",\n evidence: \"Found by opening the running record rather than trusting my own counter: the scheduled runs were there, one line away from where I was looking. Both kinds of run have now been watched being recorded correctly, one of each, before this was written down.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"fixed\",\n what: \"The two contact records for Kristina were merged into one, exactly as you asked. The phone number that survived is the one she actually rang from, the accidental do-not-disturb is off, her Meet and Greet is untouched, and the typo number is gone.\",\n evidence: \"Her inbound call that morning proves which number is real, so that one was kept. The duplicate had also been dropped into the no-sale and tips nurtures, which would have messaged a person who has an appointment booked on Monday; those did not carry over, and one click puts them back if wanted.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"built\",\n what: \"The first two real puppy inquiries are marked and waiting: Walle's owner, whose Pup Talk was that afternoon, and Kristina, who was marked that morning. Nothing sends to either of them while practice mode is on, and the system deliberately stays quiet for anyone with a call still on the calendar.\",\n evidence: \"Both are visible in the count on this page, which reads your records live. The one switch that remains is the practice-mode switch, and that gets thrown deliberately, not quietly.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"changed\",\n what: \"Walle's owner came off the puppy track before it ever sent her anything, and that is the agreed rule working: she booked. Her Free Training Day is on the calendar for Friday morning, her Pup Talk moved to Thursday afternoon, and during those changes the puppy mark came off her record. One inquiry is marked and waiting now, Kristina.\",\n evidence: \"Read live from her record on the evening of 5 August: the Friday booking is on the calendar, the mark is off, and the count on this page reflects whatever is true when you open it. If she should get the puppy messages after her visit anyway, putting the mark back is one click.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"found\",\n what: \"The tag red flag turns out to be wired to a workflow that came with your system: anyone who gets that tag is switched to do-not-disturb. It was put on five people this week, and all five are on do-not-disturb right now, which means nothing will message them.\",\n evidence: \"Each of the five records was opened and read live on the evening of 5 August, and every one shows do-not-disturb on. They are listed by name in the tag report. Taking the tag off does not switch do-not-disturb back off on its own.\",\n },\n {\n at: \"2026-08-07\",\n kind: \"mine\",\n what: \"Two customers could have dropped off your deposit list without anything looking wrong. You have two boarding calendars because a customer can be on either one, and the list is both of them put together. If one calendar failed to answer — a bad connection is enough, and there was no retry — the shorter list was saved over the full one with a fresh timestamp. Anyone who only appears on the calendar that failed was not marked unknown. They were simply gone.\",\n evidence: \"Reproduced end to end before it was fixed: a run reading one of the two calendars dropped a real customer and was still accepted for saving. It now refuses to replace a saved list with one that saw fewer calendars, so the page goes visibly older instead of quietly shorter. A calendar you actually delete still saves normally, and the first run of all still saves even if a calendar is down, because a partial list with a warning on it beats no list.\",\n },\n {\n at: \"2026-08-07\",\n kind: \"mine\",\n what: \"Where two of your bookings sat on the same day, which one the deposit counted against was decided by the order the bookings happened to come back in. Nothing was ever double counted, but a row could move between 'Payment on file' and 'Worth a look' from one hour to the next with nothing changing on your account. The oldest payment now settles the oldest stay, every time.\",\n evidence: \"Found by shuffling the same customer's bookings and payments 841,000 times and comparing the answers. It also fixed a second case: two deposits paid weeks apart, where spending the newer one first left the later stay looking unpaid when it had been paid all along.\",\n },\n {\n at: \"2026-08-07\",\n kind: \"mine\",\n what: \"The deposit page said a missing deposit might have been paid by cash. Your money page lists four ways to pay and cash is not one of them, so that was sending you to look somewhere that does not exist. It names Venmo, Zelle and cheque now, which are the three your card system genuinely cannot see.\",\n evidence: \"Checked against your own money page, which lists Card, Venmo, Zelle and Cheque and nothing else.\",\n },\n {\n at: \"2026-08-08\",\n kind: \"mine\",\n what: \"Friday's report said 120 of your 149 new people had no source recorded and none came from Facebook. That was wrong, and it was wrong because it read the one box in your CRM that is usually empty instead of the ad-tracking record that sits on every one of them. The truth: 117 of the 149 came from Facebook and 10 more from Instagram, and most carry the exact ad that brought them in. A corrected report is owed and coming.\",\n evidence: \"Re-pulled twice on 9 August by two people working separately, from two different doors into your CRM, and the two answers matched to the digit: 117 Facebook, 10 Instagram, none without a tracking record.\",\n },\n {\n at: \"2026-08-08\",\n kind: \"built\",\n what: \"The Friday report went over: what the ads cost, what came in, and where the money side still cannot be answered from your CRM. One line in it was wrong and was corrected the same night, and that correction is the entry above.\",\n evidence: \"Sent on Upwork Friday 11:46 PM with the five page report attached at 12:03. Both are in the thread.\",\n },\n {\n at: \"2026-08-09\",\n kind: \"built\",\n what: \"Facebook finally lets this page read your ad spend. The permission that was missing since the connection was first built is granted, so the advertising card below now shows real dollars from Facebook's own records every time the page loads, instead of saying it is not allowed to look.\",\n evidence: \"Watched working today: the page read $671.72 of spend and 159 started conversations for the last 7 full days, straight from the ad platform, minutes after the permission went on.\",\n },\n {\n at: \"2026-08-09\",\n kind: \"changed\",\n what: \"Your Wednesday answers are in the copy. Message two now opens on the welcome instead of 'I got your message'. Nothing says 'pitch' anymore, it just says what a Pup Talk is. The 'I won't chase you' lines are gone and the 'call any time' lines stay. 'Getting on' reads 'going'. The July and August notes carry the water warning for hot days, and August mentions school going back.\",\n evidence: \"Each change is pinned by its own automated check, so the wording cannot quietly drift back. The two write-ups you have were regenerated from the changed copy today.\",\n },\n {\n at: \"2026-08-09\",\n kind: \"found\",\n what: \"You asked Thursday for two calendars, a Free Training Day pick up and a second Pup Talk calendar for Candace, both by Tuesday. Then Friday evening you and Kristian agreed nothing changes in calendars or workflows until his handover is checked and written down. Those two collide, so the calendars wait for your word rather than being built into a freeze you asked for.\",\n evidence: \"Both are in writing: your Thursday messages on Upwork, and the Friday emails where the freeze was agreed.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"built\",\n what: \"The deposit list keeps itself up to date on its own now. It checked itself at 21:49 that evening with nobody asking it to, and it will do that every hour.\",\n evidence: \"Watched, not assumed. It refreshed by itself at 20:49 and again at 21:49 on 6 August, and the page records which schedule did it so there is no guessing. If a refresh ever fails, the page says how long ago it last managed one and warns you before you act on a name that might be a day old.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"mine\",\n what: \"I had the deposit check charging $50 a stay. Your own money page says $50 per dog, and it was sitting in the handover pack the whole time. Jeffrey Musselwhite has three dogs in over Thanksgiving: that is $150, and one $50 payment would have marked the whole stay settled and taken him off your list.\",\n evidence: \"Fixed and checked against your live account at 20:31 on 6 August. His row now reads $150.00, three dogs at $50. It settles on one payment for the full amount, or on one $50 payment per dog, and on nothing else.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"mine\",\n what: \"The deposit page was telling you a missing deposit might have been paid in cash or over the phone. Your website takes Venmo, Zelle and cheques as well, and none of those reach the card system either. It now names all three, because knowing where else to look is the difference between a ten-second check and a phone call.\",\n evidence: \"Taken from your own money page: card is the only route that matches itself to a customer record automatically. Venmo, Zelle to your email address, and cheques by post all land somewhere this cannot see.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"built\",\n what: \"The holiday deposit check you asked for is on your page. It reads both boarding calendars for Thanksgiving week and 20 December to 2 January, puts one customer's dogs on one line, leaves out your regular weekly bookings and anything cancelled, and shows which stays have a card payment on file. Right now that is two stays, both worth a look.\",\n evidence: \"It ran against your live account at 15:42 on 6 August and the list came back in under three seconds. Jeffrey Musselwhite's three dogs on 25 November show as one stay, not three, and Enzo's standing Friday slot is left out even though it lands inside every holiday window. It will never say somebody has not paid: a deposit handed over in cash or taken on the phone does not reach the card system, so this is a shortlist to look at.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"found\",\n what: \"Your card payments do reach your CRM after all, in two different shapes, and one of them was invisible to me until that morning. Some land as a plain payment line; others land as a till payment matched to a card payment later. I had only been reading the first kind.\",\n evidence: \"Both shapes are sitting on the same customer's record right now with the same $35 on them and two different reference numbers. If somebody's only record had been the second kind, the deposit check would have shown them as having nothing on file. It reads both now, and where the same money appears twice it is counted once rather than doubled.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"mine\",\n what: \"Twice today I had the deposit check guessing which card payment was the deposit, and twice it was wrong in the direction that costs you money. The first version treated any payment between the booking and the stay as the deposit, so a customer's $355 training package marked their $50 as settled. The second only looked at the ten days around the booking, which then missed a real $50 paid eight days later.\",\n evidence: \"It has stopped guessing. A stay is only marked settled by a card payment for exactly $50. Everything else on the account near that stay is listed with its date and amount and left for you to judge, which is the two-second version of what you were doing by hand. A wrong 'worth a look' costs you a glance. A wrong 'settled' costs you fifty dollars and you never find out.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"built\",\n what: \"The deposit list now knows how long a stay actually is, by reading your pick-up calendars as well as your drop-off ones. Jeffrey's three dogs show as 25 to 28 November rather than a single day, and anybody who drops off before a holiday and stays through it now appears at all.\",\n evidence: \"A drop-off booking in your system is a ten minute slot, so on its own it cannot say how long a dog stays. Checked against your live calendars on 6 August: Ghost and Chewy drop off on the 25th and are collected on the 28th, and only the pick-up calendar says so. If a pick-up calendar does not answer, the page says so rather than quietly showing a shorter list.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"mine\",\n what: \"The first time the deposit check ran for real it was about to tell you your card payments had stopped working, on the strength of two customers with nothing on file. Two quiet customers is a normal week, not an outage. I had written the warning to fire whenever nobody at all had a payment, without asking how many people that was.\",\n evidence: \"Caught by watching the first live run at 15:41 on 6 August rather than by reading the code. It now needs at least five customers checked before it will suggest anything is wrong with the payment feed, and the second run at 15:42 gave you the plain list instead of the warning.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"mine\",\n what: \"I told you the customer chased after booking was the only one it had ever happened to. That was wrong, and I said it with more confidence than my checking deserved. Four people were chased after they had already booked, going back to April: Brianna Badger, Janiya Williams, Michelle Burkard and Thomas.\",\n evidence: \"The first answer came from looking at two people with upcoming bookings. The real one comes from every Free Training Day booking you have ever taken, 80 of them across 69 people, each checked against their own messages. Three of the four came to their session anyway. Michelle's first booking was cancelled after her chase and she rebooked five days later, which is an order of events rather than a proven cause.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"found\",\n what: \"Your missing call transcripts, with one thing I got ahead of myself on. No transcript exists on any call older than about three months, and since then almost everything with speech on it has been written down. I told you that was the date transcription got switched on. I cannot actually tell that from here.\",\n evidence: \"207 calls were opened one at a time, everything inside your hundred most recently active conversations, and each was asked directly for its transcript and its recording. Before 11 May: 45 calls, none transcribed, though 38 of them still play their audio. From 11 May: 162 calls, 127 transcribed. Of the 35 without, 31 were nobody answering and 2 failed to connect. In that sample one call was recorded and never written down, on 4 August at 11:09 in the morning. The honest part: the oldest transcript we can find is 87 days old, which is either the day it was switched on or the age at which transcripts get deleted. Those look identical from here. If they expire, you are losing a month of call history every month, so it matters. One query in a week settles it: if the oldest surviving transcript has moved forward, they expire. That check is now on the list.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"built\",\n what: \"While practice mode is on, the parts that actually send a text or an email now refuse anyone except the single test record, and they refuse from a standing start rather than after being told who is safe.\",\n evidence: \"The refusal sits inside the sending functions themselves, so it holds even if something upstream enrolled the wrong person by mistake. It is switched on and running now. There is a test that proves it, and a second check that deletes the guard on purpose and demands that test go red.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"fixed\",\n what: \"A customer who had already booked his Free Training Day got chased by an older funnel to book one, two texts, a voicemail and another text, because that funnel only counts bookings made through its own page and cannot see the calendar. He was taken out of it at half past six that evening.\",\n evidence: \"His record shows no active workflows since the removal, checked after a full page reload. At the time this was written I had checked the two other people with upcoming bookings and found them clean. That was too small a check to carry the sentence it was carrying, and the entry above from 6 August corrects it: four people have been chased after booking, not one. The follow-up system on this page had nothing to do with it: practice mode was on all day and it sent nothing, checked live the same evening.\",\n },\n // THE GO-LIVE. Written 14 Aug 2026, dated to the day it happened. The 5 August entry above,\n // which says nothing sends while practice mode is on, is left exactly as it was: it was true on\n // 5 August and a work log that edits its own past is not a work log. This is its successor.\n {\n at: \"2026-08-11\",\n kind: \"changed\",\n what: \"The puppy follow-up system came out of practice mode and went live on the evening of 11 August, with your written go-ahead that day, and it has been sending to real people ever since. Two people joined it that evening and both have since had the first two messages. The 5 August note saying nothing sends to anybody while practice mode is on was true on 5 August; this is where it stopped being true.\",\n evidence: \"Open your control panel and the banner across the top says the word LIVE where it used to say PRACTICE MODE. It reads that from the system's own record every time the page loads, so it is not a note somebody typed and forgot. Both of those two people joined at 5:25 in the afternoon on 11 August, Georgia time. To see the messages rather than take my word for it, open either of them in Conversations in your CRM: the texts are sitting in the thread with the date and time on each one.\",\n },\n {\n at: \"2026-08-14\",\n kind: \"mine\",\n what: \"For three days after it went live, this page kept telling you it had not been switched on. Four things on it said so: the question card asking when we should do the switch-on together, the line under the wording question saying it still does not send, the line under the domain question saying texting can still go live on its own, and the line at the very top saying three questions were holding up go-live. All four were written before 11 August and not one of them was rewritten when the day came. They are corrected now, and what actually happened is the 11 August entry.\",\n evidence: \"The system's own record has read live rather than practice since 11 August, and the last message to each of those two people went out on 12 August, so the page was disagreeing with the machine it was describing for three days in writing to you. The four sentences are named above rather than quietly swapped out, because you should be able to hold what you read earlier in the week against what this page says now. Nothing was sent or held back because of the wording; what it cost you was three days of not being able to trust the page.\",\n },\n {\n at: \"2026-08-14\",\n kind: \"mine\",\n what: \"Your control panel could tell you the follow-up system was not running when it was running perfectly. It used to expect a check four times an hour, so any gap past an hour turned the top of that page red and told you to call Amir. The system actually checks about once an hour, and the ordinary gap between checks runs a few minutes either side of that, so the red could appear for a minute or two and clear itself with nothing wrong.\",\n evidence: \"Measured from the system's own list of when it last checked itself, which your control panel already shows: over the most recent 39 gaps the longest was 64 minutes, and four of them ran past the point where the old warning would have fired, for about five minutes in total. It now waits for two checks to be missed before it says anything, and the sentence it prints says once an hour rather than the old wrong number.\",\n },\n // 14 AUGUST, SECOND PASS. Everything below was found by reading the live control panel line by\n // line and holding each sentence against the code that decides it. Four of them were instructions\n // to Kim that would not have worked, and those are the ones that matter: a wrong number on a page\n // is embarrassing, but an instruction that does nothing costs her an afternoon and her trust.\n {\n at: \"2026-08-14\",\n kind: \"mine\",\n what: \"The tile on your control panel that counts people the system could not reach told you to fix their details in your CRM. Doing that would have changed nothing. Once the system had given up on somebody, nothing you could do put them back on the follow-up: they were locked out for 60 days no matter what you fixed. The way back in now works, and the tile tells you the three steps in the order that works.\",\n evidence: \"The tile reads zero today, so nobody has been left stuck by this. It was found by reading the enrolment code rather than by waiting for it to bite: the check that decides who may join skipped anybody the system already had a record of, and that record is exactly what it writes when it gives up. Amir has since changed the engine so that fixing the record and re-tagging really does bring somebody back, and there is an automated check that breaks on purpose if that stops being true. The order matters and the tile now says so: put a phone number or an email address on the record first, then take the tag off, because doing it the other way round looks like nothing happened.\",\n },\n {\n at: \"2026-08-14\",\n kind: \"mine\",\n what: \"The same tile also told you it never resets. It does reset: the system clears somebody out 60 days after it stopped trying to reach them, and the count comes down then. It now says that instead.\",\n evidence: \"The 60 days is in the housekeeping step the system runs at the end of every check, and there is an automated check that fails if that step is ever removed. What the old sentence was reaching for is still true and still said: unlike the Problems today tile beside it, this one does not go back to zero at midnight.\",\n },\n {\n at: \"2026-08-14\",\n kind: \"mine\",\n what: \"The instruction on your control panel for taking one person off every track was wrong in two ways. It said switching on Do Not Disturb takes them off everything, permanently, within about an hour. Your CRM has three Do Not Disturb switches on a contact, not one: a main one, and separate ones for texts and for emails. Only the main one stops everything, and the other two stop just the thing they name, so switching off texts would have left the emails running. The hour was wrong too: the system does not look at somebody again until their next message is due, which can be up to a day.\",\n evidence: \"Your own contact records are the reason this was worth correcting rather than a hypothetical: several of them carry the texts-only switch turned on while the main switch is off, which is the exact combination the old sentence got wrong. Nobody was messaged in the gap, and nobody could have been, because the only moment the system would send to a person is the same moment it re-reads their switches, so this cost you nothing and was still not true. Both points are now spelled out on the page, including which switch is the one that stops everything.\",\n },\n {\n at: \"2026-08-14\",\n kind: \"mine\",\n what: \"Your list of the last things the system did had been taken over by one line repeating. 39 of the 40 rows were the same sentence, once an hour for two days: one person who already has a booking, being passed over again on every check. Everything else the system had done was pushed off the end of the page where you could not see it. Repeats are now folded into a single row that says how many times and over what period, and the page states the sum so you can check nothing was dropped.\",\n evidence: \"You can see this for yourself against what the page looked like on 13 August: the same table now shows the repeat once, with its count, and the note under it says how many rows and how many folded repeats add up to how many entries. Amir has separately stopped the system writing the same line over and over in the first place, so the list fills up with real history from here. The list also now shows times in Georgia time; before this it printed them four hours ahead, so a message sent at five in the afternoon read as nine at night.\",\n },\n {\n at: \"2026-08-14\",\n kind: \"changed\",\n what: \"The shouting is gone from your control panel. Every heading on it was being forced into capitals, and the banner said RUNNING NORMALLY, so you asked us to stop. Headings and labels are in ordinary sentence case now.\",\n evidence: \"It was one line of styling turning all of the headings into capitals rather than anything typed that way, which is why it was consistent and why fixing it fixed all of them at once. The two words spelled FAILED in the middle of a sentence were typed, and those are corrected separately.\",\n },\n {\n at: \"2026-08-14\",\n kind: \"fixed\",\n what: \"Your status page was one failed read away from telling you the follow-up was still in practice mode. It would only have shown while nobody was partway through the sequence, which is why it had not happened yet, and it was the same false sentence you were shown from 11 to 14 August arriving by a different route. The page can now say it does not know, and says that instead of guessing.\",\n evidence: \"It was found by reading the page's own logic rather than by it happening to you: the box that names practice or live was already careful, but the paragraph two lines under it was reading a different record and defaulting to practice when that record did not answer. Both now depend on the same check. There is an automated test that puts the page in exactly that state and demands it say it could not tell, and a second check that removes the fix on purpose and requires the first one to go red.\",\n },\n];\n\nexport function mergeLog(seeded: WorkEntry[], live: WorkEntry[] | null | undefined): WorkEntry[] {\n const all = [...seeded, ...(Array.isArray(live) ? live : [])];\n const seen = new Set();\n const out: WorkEntry[] = [];\n for (const e of all) {\n if (!e || typeof e.at !== \"string\" || typeof e.what !== \"string\" || !e.what.trim()) continue;\n // v1.1 (review #6): dedupe on the FULL sentence. A 60-character prefix collapsed two\n // different outages on the same day into one row, so the second incident never reached Kim.\n const key = `${e.at}|${e.kind}|${e.what}|${e.evidence ?? \"\"}`;\n if (seen.has(key)) continue;\n seen.add(key);\n out.push(e);\n }\n // newest first. Within one day the LATEST-added entry leads, so a broke/recovered pair on the\n // same date reads \"back to normal\" above \"broke\", which is the order a human wants to see.\n return out\n .map((e, i) => ({ e, i }))\n .sort((a, b) => (a.e.at === b.e.at ? b.i - a.i : (b.e.at > a.e.at ? 1 : -1)))\n .map((x) => x.e);\n}\n\nexport const KIND_LABEL: Record = {\n mine: \"My mistake\",\n fixed: \"Fixed\",\n built: \"Built\",\n found: \"Found\",\n broke: \"Broke\",\n recovered: \"Back to normal\",\n changed: \"Changed\",\n};\n","label",[220],"5124a7e0-2efc-42c2-8068-dc5528c65154","watch.ts","ff74119a-9822-11f1-b353-1607ee4eb77e",1230,["D",1787226707632],4,"// THE EARLY WARNING MONITOR. v1.0, 12 Aug 2026. Rebuilt 14 Aug 2026 from tests/watch.test.mjs.\n//\n// WHAT THIS IS FOR. On 19 February 2026 this account's CRM stopped recording payment amounts.\n// Bookings carried on arriving at full volume; the dollars written against them went to zero.\n// Nothing failed, so nothing errored, so nothing alerted, and every count on every page stayed\n// healthy. It ran for five months and cost a five-figure sum before a human happened to look.\n//\n// THE RULE THAT FOLLOWS FROM THAT (LESSONS #12): an absence raises no error, so something has to\n// watch the place where a thing used to be. Volume and value are watched TOGETHER, because either\n// one on its own reads as an ordinary business having an ordinary month.\n//\n// FIVE CHECKS, EACH MEASURED AGAINST THE SOURCE'S OWN HISTORY rather than against a number\n// somebody typed:\n// 1. silenceFindings a source that normally produces records has produced none for\n// longer than its own normal quiet spell.\n// 2. matchRatioFindings payments still arriving, the matched share collapsing against its\n// own recent baseline.\n// 3. revenueChannelFindings activity continuing while the money against it goes to zero. This\n// is the February shape, and it is the reason the file exists.\n// 4. bridgeFindings the Square link erroring now, or its journal no longer growing.\n// 5. backwardsFindings a figure that can only ever grow has gone backwards, which usually\n// means a source was swapped, truncated, or read from somewhere else.\n//\n// THREE DESIGN RULES THIS FILE IS BUILT AROUND, each of them paid for:\n//\n// A CHECK THAT INSPECTED ZERO ITEMS RAISES A FINDING ABOUT ITSELF (LESSONS #2). This project has\n// already shipped an audit that scanned zero files and reported all clear. On a monitor that is\n// worse than useless: \"nothing wrong\" and \"nothing looked at\" render identically on the page, and\n// the second one reads as reassurance. So every check returns the size of what it read, every\n// check that read nothing says so in an urgent finding, and blindSpots() is the backstop that\n// refuses to let a silent zero through.\n//\n// A BASELINE BELOW A MINIMUM POPULATION SAYS \"CANNOT JUDGE\" OUT LOUD (LESSONS #13). Replayed\n// against the real history as it stood on 15 March 2026 the revenue check fired and produced\n// \"47 bookings were recorded, which is the same as usual or more, and the money came to $50.00.\n// Over the 6 periods before it the usual figures were 2 bookings and $550.00.\" The arithmetic was\n// right and the sentence was nonsense, because the baseline was this account's first weeks in the\n// CRM. A sentence that reads as a glitch spends the credibility the real alarm will need, so a\n// thin baseline is declared unjudgeable rather than either accusing or passing.\n//\n// EVERY SENTENCE IS GENERATED FROM THE VALUES IT DESCRIBES (engine/facts.ts, header). Nothing in\n// here types a figure alongside the number it is meant to describe. Change an input and the words\n// move with it, or the two can silently disagree, which is how every wrong claim in this project\n// got out.\n//\n// CLIENT COPY RULES, enforced mechanically by copyProblems() over the generated report: no dashes\n// used as punctuation, and never the name of a service this business does not offer.\n//\n// READ ONLY. Nothing in this file fetches, writes, deploys or schedules anything. It is handed\n// data by scripts/watch-run.mjs and hands back a report.\n\n// ---------------------------------------------------------------------------------------------\n// THE SHAPES\n// ---------------------------------------------------------------------------------------------\n\n/** urgent: look today. attention: look this week. note: the monitor talking about itself. */\nexport type Severity = \"urgent\" | \"attention\" | \"note\";\n\nexport type Finding = {\n check: string; // which check raised it, so the report can group them\n severity: Severity;\n sentence: string; // plain words, generated from `numbers`, safe to send\n numbers: Record; // the figures the sentence was built from\n checkFirst: string; // the first thing to open, in her words not mine\n};\n\nexport type CheckResult = {\n check: string;\n title: string; // how the check is named in the report\n inspected: number; // HOW MUCH IT READ. Zero is a finding, never a pass.\n inspectedLabel: string; // what those items are, for the sentence that reports it\n measured: Record; // the workings, kept so a queried figure can be traced\n findings: Finding[];\n};\n\nexport type WatchReport = {\n generatedAt: string;\n headline: string;\n inspected: number;\n checks: CheckResult[];\n findings: Finding[];\n};\n\nexport type Stream = { name: string; timestamps: unknown; whereToLook?: string };\nexport type RatioPoint = { label?: string; endMs?: number; total: number; matched: number };\nexport type RevenuePeriod = { label?: string; endMs?: number; activity: number; dollars: number };\nexport type Snapshot = { at?: string; counters?: Record };\n\nexport type WatchInput = {\n nowMs?: unknown;\n streams?: unknown;\n ratio?: { subject?: string; points?: unknown } | null;\n revenue?: { subject?: string; periods?: unknown } | null;\n journal?: unknown;\n snapshots?: unknown;\n counterLabels?: Record | null;\n};\n\nconst HOUR = 3_600_000;\n\n// ---------------------------------------------------------------------------------------------\n// THE CONSTANTS, and why each one is the number it is. Every one of these is a judgement about\n// how loud this thing should be, so each is named, exported and testable rather than buried at a\n// call site where nobody can find it to argue with it.\n// ---------------------------------------------------------------------------------------------\n\n/** Below this many records a source has no rhythm worth quoting, and saying so is the honest move. */\nexport const MIN_RECORDS_FOR_RHYTHM = 5;\n\n/**\n * Only the most recent gaps are measured. A source that changes pace has to be able to\n * re-baseline: the payment feed moved from weekly invoicing to daily card takings in June, and a\n * rhythm averaged over all of history would still be judging today against a habit it dropped.\n */\nexport const MAX_GAPS_CONSIDERED = 30;\n\n/**\n * THE QUIET SPELL, not the longest outage. Read against the MAXIMUM gap in history, one bad\n * fortnight silently raises the bar past which any future outage would be reported: the next one\n * has to beat a record before anybody hears about it. The 90th percentile says \"longer than\n * almost every quiet spell this source normally has\" and cannot be dragged by a single hole.\n */\nexport const QUIET_QUANTILE = 0.9;\nexport const QUIET_MULTIPLE = 1.5; // half again past its own worst ordinary silence\nexport const NORMAL_MULTIPLE = 3; // or three times its ordinary gap, whichever is longer\n\n/**\n * THE OVERNIGHT FLOOR. New contact records arrive about every 25 minutes during the day and stop\n * at night. Judged on gaps alone that source is \"silent for twenty times its normal gap\" at 3am\n * every single night, and a report that cries wolf every morning is a report nobody opens on the\n * morning it is right. 26 hours clears a night, a weekend morning and a public holiday opening.\n */\nexport const MIN_EXPECT_HOURS = 26;\n\n/** Twice past the point where it became out of character is today's problem, not this week's. */\nexport const URGENT_MULTIPLE = 2;\n\n/** A collapse is a third of the baseline share gone AND ten points of it in absolute terms. */\nexport const RATIO_RELATIVE_FALL = 0.33;\nexport const RATIO_ABSOLUTE_FALL = 0.1;\n/** Half the baseline share gone is not a wobble, it is a fault, and it is today's problem. */\nexport const RATIO_URGENT_RELATIVE_FALL = 0.5;\n/** A verdict on two payments is not a verdict. Below this the check says so instead. */\nexport const RATIO_MIN_LATEST = 5;\n\n/** Four fifths of the usual money gone. A half is a trading question; this is a plumbing one. */\nexport const REVENUE_DOLLAR_FALL = 0.8;\n/** ...while at least half the usual amount of work still arrived. Both halves, or it is a slow month. */\nexport const REVENUE_ACTIVITY_HELD = 0.5;\n/** LESSONS #13. A baseline of two records a period cannot carry an accusation. */\nexport const REVENUE_MIN_BASELINE_ACTIVITY = 5;\n/** Fewer periods than this and there is no \"usual\" to compare the latest one against. */\nexport const REVENUE_MIN_PERIODS = 4;\n\n/**\n * The bridge is judged on its RECENT rows only. This journal holds 265 failures from three bad\n * days in July that were found and fixed. A check that fires on any error ever recorded is red\n * forever, and a permanently red check is a switched off one.\n */\nexport const BRIDGE_RECENT_ROWS = 100;\nexport const BRIDGE_ERROR_SHARE_URGENT = 0.2;\n\n// ---------------------------------------------------------------------------------------------\n// SAYING THINGS. Every one of these turns a value into words. Nothing below ever types a figure\n// beside the number it describes, which is the whole of engine/facts.ts in one rule.\n// ---------------------------------------------------------------------------------------------\n\nconst MONTH_NAMES = [\"January\", \"February\", \"March\", \"April\", \"May\", \"June\",\n \"July\", \"August\", \"September\", \"October\", \"November\", \"December\"];\n\n/** A duration in words that fit its size: minutes for an hour, hours for a day, days beyond that. */\nexport function sayGap(hours: unknown): string {\n const h = Number(hours);\n if (!Number.isFinite(h)) return \"an unknown length of time\";\n if (h <= 1) return `${Math.round(h * 60)} minutes`;\n if (h < 48) return `${Math.round(h)} hours`;\n const days = Math.round(h / 24);\n if (days < 60) return `${days} days`;\n // Past two months \"97 days\" stops meaning anything to a reader, so the months are said too.\n // Both figures, never the months alone: the day count is the one that can be checked.\n const months = Math.round(days / 30.44);\n return `${days} days, which is about ${months} months`;\n}\n\n/** A date a person can read, in UTC so a replay of a past morning says the same thing every time. */\nexport function sayDate(ms: unknown): string {\n const t = Number(ms);\n if (!Number.isFinite(t)) return \"a date this could not read\";\n const d = new Date(t);\n if (Number.isNaN(d.getTime())) return \"a date this could not read\";\n return `${d.getUTCDate()} ${MONTH_NAMES[d.getUTCMonth()]} ${d.getUTCFullYear()}`;\n}\n\n/** Money, always to the cent and always with its thousands separators. */\nexport function money(n: unknown): string {\n const v = Number(n);\n if (!Number.isFinite(v)) return \"an amount this could not read\";\n const [whole, frac] = Math.abs(v).toFixed(2).split(\".\");\n return `${v < 0 ? \"minus \" : \"\"}$${whole.replace(/\\B(?=(\\d{3})+(?!\\d))/g, \",\")}.${frac}`;\n}\n\nconst WORDS = [\"no\", \"one\", \"two\", \"three\", \"four\", \"five\", \"six\", \"seven\", \"eight\", \"nine\", \"ten\"];\nconst countWord = (n: number) => WORDS[n] ?? String(n);\nconst capitalise = (s: string) => s.replace(/^./, (c) => c.toUpperCase());\nconst plural = (n: number, one: string, many: string) => (n === 1 ? one : many);\nconst commas = (n: number) => Number(n ?? 0).toLocaleString(\"en-US\");\nconst percent = (x: number) => `${Math.round(x * 100)}%`;\n\n/** The subject as a bare noun: \"your bookings\" is what she calls them, \"bookings\" is what counts them. */\nconst unitOf = (subject: string) => String(subject ?? \"records\").replace(/^(your|the)\\s+/i, \"\");\n\n// ---------------------------------------------------------------------------------------------\n// THE MEASUREMENT. A rhythm read off the source itself.\n//\n// Everything else in this file rests on this function, so it is worth saying what it deliberately\n// does NOT do. It does not take a threshold. It does not know what kind of source it is looking\n// at. It reads the gaps between the things that actually arrived and reports how long this source\n// normally goes quiet for. A monitor built on typed thresholds is a monitor that is wrong for\n// every source but the one somebody had in mind when they typed it.\n// ---------------------------------------------------------------------------------------------\n\nexport type Rhythm = {\n records: number; // how many readable timestamps went into this\n gapsUsed: number; // how many gaps the figures below were measured from\n normalGapH: number; // the median gap: what \"usually\" means for this source\n quietGapH: number; // its ordinary worst quiet spell, at the 90th percentile\n longestGapH: number; // the worst hole in the history it was given, reported and NOT used\n expectByH: number; // past this it is out of character for this source\n};\n\n/** Every readable timestamp in a list, as milliseconds, oldest first. Unreadable ones are dropped. */\nexport function readTimes(list: unknown): number[] {\n if (!Array.isArray(list)) return [];\n const out: number[] = [];\n for (const v of list) {\n // A number is already milliseconds; anything else has to survive Date.parse to count.\n const t = typeof v === \"number\" ? v : Date.parse(String(v ?? \"\"));\n if (Number.isFinite(t)) out.push(t as number);\n }\n // SORTED, ALWAYS. The live feed comes back newest first, fixtures come back oldest first, and a\n // jittered series is in neither order. Measuring gaps off an unsorted list produces negative\n // gaps and a median that means nothing.\n return out.sort((a, b) => a - b);\n}\n\n/**\n * The rhythm of a source, or null when there is not enough of it to have one.\n *\n * Null is a real answer here, not a failure: it is what makes \"there is not enough history to\n * judge this\" sayable out loud instead of being rounded to either an alarm or an all clear.\n */\nexport function rhythmOf(list: unknown): Rhythm | null {\n const times = readTimes(list);\n if (times.length < MIN_RECORDS_FOR_RHYTHM) return null;\n const allGaps: number[] = [];\n for (let i = 1; i < times.length; i++) allGaps.push((times[i] - times[i - 1]) / HOUR);\n if (!allGaps.length) return null;\n // RECENT HISTORY ONLY, so a source that changes pace re-baselines instead of being judged\n // forever against a habit it has dropped.\n const gaps = allGaps.slice(-MAX_GAPS_CONSIDERED);\n const normalGapH = quantile(gaps, 0.5) as number;\n const quietGapH = quantile(gaps, QUIET_QUANTILE) as number;\n // The longest gap is REPORTED so it can be looked at, and deliberately not used as the\n // yardstick. See QUIET_QUANTILE above for what happens when it is.\n const longestGapH = Math.max(...allGaps);\n const expectByH = Math.max(quietGapH * QUIET_MULTIPLE, normalGapH * NORMAL_MULTIPLE, MIN_EXPECT_HOURS);\n return { records: times.length, gapsUsed: gaps.length, normalGapH, quietGapH, longestGapH, expectByH };\n}\n\n/** The value at a quantile, interpolated. Null on an empty list, never a confident zero. */\nexport function quantile(values: number[], q: number): number | null {\n if (!Array.isArray(values) || !values.length) return null;\n const a = [...values].sort((x, y) => x - y);\n const pos = (a.length - 1) * q;\n const lo = Math.floor(pos);\n const hi = Math.ceil(pos);\n if (lo === hi) return a[lo];\n return a[lo] + (a[hi] - a[lo]) * (pos - lo);\n}\n\n/** urgent once it is twice past the point where it stopped being in character, attention before. */\nconst escalate = (ageH: number, expectByH: number): Severity =>\n (ageH >= expectByH * URGENT_MULTIPLE ? \"urgent\" : \"attention\");\n\n// ---------------------------------------------------------------------------------------------\n// A CHECK THAT READ NOTHING.\n//\n// This is the single most important function in the file, which is why it is this near the top.\n// Every check routes its empty case through it, so there is exactly one place where \"I inspected\n// nothing\" is turned into words, and exactly one place to break in order to prove the whole\n// arrangement still works (tests/negative-controls.mjs does exactly that).\n// ---------------------------------------------------------------------------------------------\nexport function blindCheck(check: string, title: string, inspectedLabel: string, why: string, checkFirst: string): CheckResult {\n return {\n check,\n title,\n inspected: 0,\n inspectedLabel,\n measured: { inspected: 0 },\n // SEVERITY STAYS \"urgent\" AND SIX TESTS HOLD IT THERE (W10, W19, W26, W31, W37, W42). A check\n // that read nothing must never be quiet. What was wrong was not the severity, it was the\n // HEADLINE: it counted blind spots as business problems and said \"two things need you to look at\n // today\" when both were unwired checks. That is fixed in headlineFor and in the section split\n // below, which separate \"a check found a fault\" from \"a check could not look\" WITHOUT making the\n // second one quiet. Relabelling this to \"note\" was tried on 16 Aug and the tests rejected it,\n // correctly: it is the guarantee, not the wording.\n findings: [{ check, severity: \"urgent\", sentence: why, numbers: { inspected: 0 }, checkFirst }],\n };\n}\n\n/**\n * THE BACKSTOP. Any check that inspected nothing and said nothing about it. This should always be\n * empty, because every check above routes its empty case through blindCheck. It is here because\n * \"should always be empty\" is exactly the kind of claim that quietly stops being true, and\n * scripts/watch-run.mjs refuses to write a report while this returns anything.\n */\nexport function blindSpots(checks: unknown): CheckResult[] {\n return (Array.isArray(checks) ? checks : []).filter((c) => c && c.inspected === 0 && (!c.findings || c.findings.length === 0));\n}\n\n/**\n * A finding is blind only when its owning check inspected no evidence. `finding.numbers` is\n * explanatory working supplied by the check and is deliberately not an authority boundary.\n */\nexport function isBlindFindingForChecks(finding: unknown, checks: unknown): finding is Finding {\n if (!finding || typeof finding !== \"object\" || Array.isArray(finding) || !Array.isArray(checks)) return false;\n const ownerName = (finding as { check?: unknown }).check;\n if (typeof ownerName !== \"string\") return false;\n return checks.some((candidate) =>\n !!candidate && typeof candidate === \"object\" && !Array.isArray(candidate) &&\n (candidate as { check?: unknown }).check === ownerName &&\n (candidate as { inspected?: unknown }).inspected === 0);\n}\n\n// ---------------------------------------------------------------------------------------------\n// CHECK 1: SILENCE WHERE THERE SHOULD BE NOISE. This is the 19 February check.\n//\n// A source that normally produces records has produced none for longer than it normally goes\n// quiet. Every source is judged against its own rhythm: the payment feed against the payment\n// feed's habits, the fortnightly form payments against the fortnightly form payments'. Judging\n// them all by one clock is how the fortnightly source becomes a false alarm every fortnight.\n// ---------------------------------------------------------------------------------------------\n\nconst SILENCE = \"silence\";\nconst SILENCE_TITLE = \"Sources that have gone quiet\";\nconst SILENCE_LABEL = \"timestamps\";\n\nexport function silenceFindings(streams: unknown, nowMs: unknown): CheckResult {\n const now = Number(nowMs);\n const list = (Array.isArray(streams) ? streams : []) as Stream[];\n const prepared = list.map((s) => ({\n name: String(s?.name ?? \"a source with no name\"),\n whereToLook: typeof s?.whereToLook === \"string\" ? s.whereToLook : null,\n times: readTimes(s?.timestamps),\n }));\n const inspected = prepared.reduce((a, s) => a + s.times.length, 0);\n\n if (!Number.isFinite(now) || inspected === 0) {\n return blindCheck(SILENCE, SILENCE_TITLE, SILENCE_LABEL,\n `This check read nothing at all, so it cannot tell you whether anything has stopped arriving. ` +\n `A check that inspects nothing is a blind spot, not a clean result, and it is being reported as one.`,\n `Check that the connection to your CRM is still working, then run this again. Until it reads something, ` +\n `treat the sources it was meant to watch as unwatched rather than healthy.`);\n }\n\n const findings: Finding[] = [];\n const perSource: Record[] = [];\n\n for (const s of prepared) {\n const r = rhythmOf(s.times);\n if (r === null) {\n // NOT A SILENT PASS. A source nothing can be measured on is a source nothing is watching,\n // and she should be told that in the same breath as she is told everything else is fine.\n findings.push({\n check: SILENCE,\n severity: \"note\",\n sentence:\n `There is not enough history for ${s.name} to say what normal looks like: ${s.times.length} ` +\n `${plural(s.times.length, \"record\", \"records\")}, where this needs ${MIN_RECORDS_FOR_RHYTHM} before it can ` +\n `measure a rhythm. Nothing is watching this source yet, which is worth knowing rather than reading as a clean result.`,\n numbers: { source: s.name, records: s.times.length, needed: MIN_RECORDS_FOR_RHYTHM },\n checkFirst:\n `Nothing to do today. Once ${MIN_RECORDS_FOR_RHYTHM} records have arrived here this will start ` +\n `watching it on its own, and until then treat it as unwatched.`,\n });\n perSource.push({ source: s.name, records: s.times.length, rhythm: \"not enough history\" });\n continue;\n }\n const lastMs = s.times[s.times.length - 1];\n const ageH = (now - lastMs) / HOUR;\n perSource.push({\n source: s.name,\n records: r.records,\n normalGapH: Math.round(r.normalGapH * 10) / 10,\n quietGapH: Math.round(r.quietGapH * 10) / 10,\n expectByH: Math.round(r.expectByH * 10) / 10,\n quietForHours: Math.round(ageH * 10) / 10,\n });\n if (ageH <= r.expectByH) continue;\n const severity = escalate(ageH, r.expectByH);\n // THE FIRST MOVE. A stream that knows where its own answer lives brings its own sentence:\n // scripts/watch-run.mjs hands the payment feed one, because that is the stream whose silence\n // means what February meant. Everything else gets this, which is the same move generalised.\n const checkFirst = s.whereToLook ??\n `Open the Square app and compare what it has taken since ${sayDate(lastMs)} against what your CRM shows for ` +\n `${s.name}. If Square has money the CRM does not, sales are being rung up in a way that never reaches a customer record.`;\n findings.push({\n check: SILENCE,\n severity,\n sentence:\n `Nothing has come through from ${s.name} for ${sayGap(ageH)}. The last one was on ${sayDate(lastMs)}. ` +\n `Before that this source produced something every ${sayGap(r.normalGapH)} on average, and the longest it ` +\n `normally stays quiet is ${sayGap(r.quietGapH)}, so this is well outside its own habits rather than outside ` +\n `a figure somebody chose.`,\n numbers: {\n source: s.name,\n lastRecordAt: new Date(lastMs).toISOString(),\n quietForHours: Math.round(ageH * 10) / 10,\n normalGapHours: Math.round(r.normalGapH * 10) / 10,\n quietGapHours: Math.round(r.quietGapH * 10) / 10,\n outOfCharacterAfterHours: Math.round(r.expectByH * 10) / 10,\n recordsMeasured: r.records,\n },\n checkFirst,\n });\n }\n\n return {\n check: SILENCE,\n title: SILENCE_TITLE,\n inspected,\n inspectedLabel: SILENCE_LABEL,\n measured: { sources: prepared.length, timestamps: inspected, perSource },\n findings,\n };\n}\n\n// ---------------------------------------------------------------------------------------------\n// CHECK 2: A RATIO COLLAPSE. Payments still arrive; the share of them reaching a customer record\n// falls away against its own recent baseline.\n//\n// THE TRAP THIS CHECK HAS TO AVOID, and the reason W17 exists: nought matched out of nought\n// arriving is not nought percent matching. Calling it a collapse raises a second alarm for one\n// fault and names the wrong cause, sending her to look at the matcher when the payments never\n// arrived at all.\n// ---------------------------------------------------------------------------------------------\n\nconst RATIO = \"match-ratio\";\nconst RATIO_TITLE = \"Payments reaching a customer record\";\nconst RATIO_LABEL = \"payments\";\n\nexport function matchRatioFindings(points: unknown, subject: unknown): CheckResult {\n const what = String(subject ?? \"payments\");\n const list = (Array.isArray(points) ? points : []) as RatioPoint[];\n const clean = list.map((p) => ({\n label: String(p?.label ?? \"a window\"),\n endMs: Number(p?.endMs),\n total: Math.max(0, Number(p?.total) || 0),\n matched: Math.max(0, Number(p?.matched) || 0),\n }));\n const inspected = clean.reduce((a, p) => a + p.total, 0);\n\n if (inspected === 0) {\n return blindCheck(RATIO, RATIO_TITLE, RATIO_LABEL,\n `This check read no ${what} at all, so it cannot tell you whether they are still reaching a customer record. ` +\n `A check that inspects nothing is a blind spot, not a clean result, and it is being reported as one.`,\n `Check that the Square link is still running and still writing to its own log, then run this again.`);\n }\n\n const latest = clean[clean.length - 1];\n const base = clean.slice(0, -1);\n const baseTotal = base.reduce((a, p) => a + p.total, 0);\n const baseMatched = base.reduce((a, p) => a + p.matched, 0);\n const measured: Record = {\n windows: clean.length,\n payments: inspected,\n latestTotal: latest.total,\n latestMatched: latest.matched,\n baselineTotal: baseTotal,\n baselineMatched: baseMatched,\n };\n const result = (findings: Finding[]): CheckResult =>\n ({ check: RATIO, title: RATIO_TITLE, inspected, inspectedLabel: RATIO_LABEL, measured, findings });\n\n if (baseTotal === 0) {\n return result([{\n check: RATIO,\n severity: \"note\",\n sentence:\n `There is no earlier run of ${what} to compare the latest ${commas(latest.total)} against, so this cannot ` +\n `judge whether the share reaching a customer record has moved. It will be able to from the next run on.`,\n numbers: { subject: what, latestTotal: latest.total, baselineTotal: baseTotal, windows: clean.length },\n checkFirst: `Nothing to do today. This needs one more period of history before it can say anything useful here.`,\n }]);\n }\n\n if (latest.total === 0) {\n // AN ABSENCE, DESCRIBED AS AN ABSENCE. Never as a collapse to nought percent.\n return result([{\n check: RATIO,\n severity: \"note\",\n sentence:\n `No ${what} arrived at all in the latest window, so there is nothing to work out a share from. ` +\n `That is a different problem from the ones this check watches for, and the list of sources that have gone ` +\n `quiet is where it will show up.`,\n numbers: { subject: what, latestTotal: 0, baselineTotal: baseTotal, windows: clean.length },\n checkFirst:\n `Look at the sources that have gone quiet, further up. If nothing there names ${what}, open the Square app ` +\n `and check whether any sale has been taken at all in the last week.`,\n }]);\n }\n\n if (latest.total < RATIO_MIN_LATEST) {\n // LESSONS #13, in its other shape. A verdict on two payments is not a verdict.\n return result([{\n check: RATIO,\n severity: \"note\",\n sentence:\n `Only ${commas(latest.total)} ${plural(latest.total, \"payment\", \"payments\")} arrived in the latest window, ` +\n `which is too few to judge a matching rate on. This needs at least ${RATIO_MIN_LATEST} before it will call ` +\n `a fall in the share reaching a customer record, because a wrong alarm here spends the attention a real one will need.`,\n numbers: { subject: what, latestTotal: latest.total, needed: RATIO_MIN_LATEST, baselineTotal: baseTotal },\n checkFirst: `Nothing to do today. This will judge the share again as soon as a normal week's worth of payments has arrived.`,\n }]);\n }\n\n const baseShare = baseMatched / baseTotal;\n const latestShare = latest.matched / latest.total;\n const relativeFall = baseShare > 0 ? (baseShare - latestShare) / baseShare : 0;\n const absoluteFall = baseShare - latestShare;\n const fires = relativeFall >= RATIO_RELATIVE_FALL && absoluteFall >= RATIO_ABSOLUTE_FALL;\n measured.baselineSharePercent = Math.round(baseShare * 100);\n measured.latestSharePercent = Math.round(latestShare * 100);\n if (!fires) return result([]);\n\n const latestUnmatched = latest.total - latest.matched;\n return result([{\n check: RATIO,\n severity: relativeFall >= RATIO_URGENT_RELATIVE_FALL ? \"urgent\" : \"attention\",\n sentence:\n `${capitalise(what)} are still arriving, and the share of them reaching a customer record has fallen from ` +\n `${percent(baseShare)} to ${percent(latestShare)}. In the latest window ${commas(latestUnmatched)} of ` +\n `${commas(latest.total)} reached nobody at all. The money is still being taken; it is the record of who paid it ` +\n `that is going missing.`,\n numbers: {\n subject: what,\n latestTotal: latest.total,\n latestMatched: latest.matched,\n latestUnmatched,\n latestSharePercent: Math.round(latestShare * 100),\n baselineSharePercent: Math.round(baseShare * 100),\n baselineTotal: baseTotal,\n windowsCompared: clean.length,\n },\n checkFirst:\n `Open the Square link's own log and look at the most recent entries for a sale that did not find a customer. ` +\n `The weekly exception report lists every one of them by name and amount, and that is the list to work from.`,\n }]);\n}\n\n// ---------------------------------------------------------------------------------------------\n// CHECK 3: A REVENUE CHANNEL GOING QUIET WHILE THE ACTIVITY CONTINUES. THE FEBRUARY SHAPE.\n//\n// This is the one the whole file exists for. Six ordinary periods of about 45 bookings and about\n// $7,000 taken, then a period in which the same number of bookings arrived and not one dollar was\n// recorded against them. The live account did exactly that: 48 payment records and $7,386.50 in\n// February, then 37 records and $0.00 in March, 21 and $0.00 in April, 18 and $0.00 in May.\n//\n// BOTH HALVES OR NOTHING. Money down and work down together is a slow month, which she can\n// already see out of the window, and raising it would be inventing an alarm about business\n// conditions. Money down while the work held is a plumbing fault, and she cannot see that at all.\n// ---------------------------------------------------------------------------------------------\n\nconst REVENUE = \"revenue-quiet\";\nconst REVENUE_TITLE = \"Money recorded against the work\";\nconst REVENUE_LABEL = \"records of activity\";\n\nexport function revenueChannelFindings(periods: unknown, subject: unknown): CheckResult {\n const what = String(subject ?? \"your bookings\");\n const unit = unitOf(what);\n const list = (Array.isArray(periods) ? periods : []) as RevenuePeriod[];\n const clean = list.map((p) => ({\n label: String(p?.label ?? \"a period\"),\n endMs: Number(p?.endMs),\n activity: Math.max(0, Number(p?.activity) || 0),\n dollars: Math.max(0, Number(p?.dollars) || 0),\n }));\n const inspected = clean.reduce((a, p) => a + p.activity, 0);\n\n if (inspected === 0) {\n return blindCheck(REVENUE, REVENUE_TITLE, REVENUE_LABEL,\n `This check read no record of any work at all, so it cannot tell you whether the money against it is being ` +\n `written down. A check that inspects nothing is a blind spot, not a clean result, and it is being reported as one.`,\n `Check that the connection to your CRM is still working, then run this again. This is the check that would ` +\n `have caught the five month gap, so it reading nothing matters more than most.`);\n }\n\n const latest = clean[clean.length - 1];\n const base = clean.slice(0, -1);\n const measured: Record = {\n periods: clean.length,\n recordsOfActivity: inspected,\n latestActivity: latest.activity,\n latestDollars: latest.dollars,\n };\n const result = (findings: Finding[]): CheckResult =>\n ({ check: REVENUE, title: REVENUE_TITLE, inspected, inspectedLabel: REVENUE_LABEL, measured, findings });\n\n if (clean.length < REVENUE_MIN_PERIODS) {\n return result([{\n check: REVENUE,\n severity: \"note\",\n sentence:\n `There are only ${clean.length} periods of history for ${what}, and this needs ${REVENUE_MIN_PERIODS} before ` +\n `it can say what a normal period looks like. It cannot judge the latest one yet, and guessing would be worse ` +\n `than saying so.`,\n numbers: { subject: what, periods: clean.length, needed: REVENUE_MIN_PERIODS },\n checkFirst: `Nothing to do today. This will start judging as soon as there are ${REVENUE_MIN_PERIODS} periods to read.`,\n }]);\n }\n\n // THE BASELINE IS A MEDIAN, not an average. One freak month with a $4,000 boarding block in it\n // drags an average up and makes every ordinary month afterwards look like a collapse.\n const baseActivity = quantile(base.map((p) => p.activity), 0.5) as number;\n const baseDollars = Math.round((quantile(base.map((p) => p.dollars), 0.5) as number) * 100) / 100;\n measured.usualActivity = Math.round(baseActivity);\n // Keep the exact median as validation evidence. The rounded value is client-facing, but it is\n // not precise enough to prove the 50% activity-held boundary on its own.\n measured.baselineActivity = baseActivity;\n measured.usualDollars = baseDollars;\n\n if (baseActivity < REVENUE_MIN_BASELINE_ACTIVITY) {\n // LESSONS #13, the sentence that reads as a glitch. Right arithmetic, no denominator.\n return result([{\n check: REVENUE,\n severity: \"note\",\n sentence:\n `Over the ${base.length} periods before the latest one, ${what} ran at about ${Math.round(baseActivity)} ` +\n `${unit} a period, which is too little to say what a normal period looks like. This cannot judge the latest ` +\n `period against a baseline that thin, and it would rather tell you so than put a figure in front of you that ` +\n `reads as a glitch.`,\n numbers: {\n subject: what,\n usualActivity: Math.round(baseActivity),\n needed: REVENUE_MIN_BASELINE_ACTIVITY,\n latestActivity: latest.activity,\n latestDollars: latest.dollars,\n periods: clean.length,\n },\n checkFirst:\n `Nothing to do today. Once this channel has run at ${REVENUE_MIN_BASELINE_ACTIVITY} or more records a period ` +\n `for a few periods, this will start judging it properly.`,\n }]);\n }\n\n if (!(baseDollars > 0)) {\n // THE HONEST LIMIT OF THIS CHECK, said out loud rather than left to be discovered. Once every\n // period in view is already at zero there is nothing left to fall from, and silence here would\n // read as a clean bill of health for the exact fault this check was built for.\n return result([{\n check: REVENUE,\n severity: \"note\",\n sentence:\n `Over the ${base.length} periods before the latest one, no money at all was recorded against ${what}, so there ` +\n `is no normal level for this one to have fallen from. This cannot judge whether anything is wrong here: a fault ` +\n `that has run long enough to become the baseline stops looking like a fall. Take this as the monitor saying it ` +\n `is blind on this channel, not as an all clear.`,\n numbers: {\n subject: what,\n usualDollars: baseDollars,\n latestActivity: latest.activity,\n latestDollars: latest.dollars,\n periods: clean.length,\n },\n checkFirst:\n `Open the Square app and total what it has taken over the last few months, then compare that with what your ` +\n `CRM shows for the same months. If Square has money the CRM does not, the two have been disconnected for ` +\n `longer than this report can see.`,\n }]);\n }\n\n const dollarFall = 1 - latest.dollars / baseDollars;\n const activityHeld = latest.activity >= baseActivity * REVENUE_ACTIVITY_HELD;\n measured.dollarFallPercent = Math.round(dollarFall * 100);\n measured.activityHeld = activityHeld;\n\n if (dollarFall < REVENUE_DOLLAR_FALL || !activityHeld) {\n return result([]);\n }\n\n const usualActivity = Math.round(baseActivity);\n const shareOfMoneyMissing = Math.round(dollarFall * 100);\n const heldPhrase = latest.activity >= baseActivity\n ? \"as many as usual or more\"\n : `${Math.round((latest.activity / baseActivity) * 100)}% of the usual number`;\n const sentence =\n `In the latest period ${commas(latest.activity)} ${unit} were recorded, which is ${heldPhrase}, ` +\n `and the money recorded against them came to ${money(latest.dollars)}. ` +\n `Over the ${base.length} periods before it the usual figures were ${commas(usualActivity)} ${unit} and ` +\n `${money(baseDollars)}. The work carried on and ${shareOfMoneyMissing}% of the money that normally comes with it ` +\n `was never written down, which means it is being taken somewhere your CRM never hears about.`;\n\n return result([{\n check: REVENUE,\n severity: \"urgent\",\n sentence,\n numbers: {\n subject: what,\n latestActivity: latest.activity,\n latestDollars: latest.dollars,\n usualActivity,\n usualDollars: baseDollars,\n shareOfMoneyMissing,\n periodsCompared: clean.length,\n },\n checkFirst:\n `Open the Square app and total what it has taken over the same period. If Square shows sales your CRM does not, ` +\n `sales are being rung up in a way that never reaches a customer record, which is exactly what happened after ` +\n `19 February 2026.`,\n }]);\n}\n\n// ---------------------------------------------------------------------------------------------\n// CHECK 4: THE BRIDGE ITSELF. The Square link either erroring right now, or no longer writing\n// anything down at all.\n//\n// TWO FAULTS, TWO SENTENCES. \"It is failing\" and \"it has stopped\" are different problems with\n// different first moves, and collapsing them into one alarm sends her to the wrong place.\n// ---------------------------------------------------------------------------------------------\n\nconst BRIDGE = \"bridge\";\nconst BRIDGE_TITLE = \"The Square link\";\nconst BRIDGE_LABEL = \"journal rows\";\n\nconst isErrorRow = (r: any) =>\n String(r?.kind ?? \"\").toUpperCase() === \"ERROR\" || (typeof r?.error === \"string\" && r.error.length > 0);\n\nexport function bridgeFindings(rows: unknown, nowMs: unknown): CheckResult {\n const now = Number(nowMs);\n const list = Array.isArray(rows) ? rows : [];\n const inspected = list.length;\n\n if (!Number.isFinite(now) || inspected === 0) {\n return blindCheck(BRIDGE, BRIDGE_TITLE, BRIDGE_LABEL,\n `The Square link's own log came back with nothing in it that could be read, so this cannot tell you whether ` +\n `the link is working. A check that inspects nothing is a blind spot, not a clean result, and an unreadable log ` +\n `is the loudest thing in this report rather than the quietest.`,\n `Open the Square link's own page and check it answers at all. If it does and the log is genuinely empty, ` +\n `every sale taken since it last wrote something down is unaccounted for.`);\n }\n\n // Rows with a readable date, oldest first. The rest are counted and reported, never guessed at.\n const stamped = (list as any[])\n .map((r) => ({ row: r, ms: Date.parse(String(r?.ts ?? \"\")) }))\n .filter((x) => Number.isFinite(x.ms))\n .sort((a, b) => a.ms - b.ms);\n\n const measured: Record = {\n rows: inspected,\n rowsWithATimestamp: stamped.length,\n };\n const result = (findings: Finding[]): CheckResult =>\n ({ check: BRIDGE, title: BRIDGE_TITLE, inspected, inspectedLabel: BRIDGE_LABEL, measured, findings });\n\n if (stamped.length === 0) {\n return result([{\n check: BRIDGE,\n severity: \"urgent\",\n sentence:\n `The Square link's log has ${commas(inspected)} ${plural(inspected, \"entry\", \"entries\")} in it and not one of ` +\n `them carries a date this can read. Without dates there is no way to tell a link that stopped last night from ` +\n `one that stopped in March, so this is being raised rather than passed over.`,\n numbers: { rows: inspected, rowsWithATimestamp: 0 },\n checkFirst:\n `Open the Square link's own log and look at the newest few entries. If they carry no time against them, the ` +\n `link is writing in a shape this report cannot read and that needs fixing before any of it can be believed.`,\n }]);\n }\n\n // ONLY THE RECENT ROWS. See BRIDGE_RECENT_ROWS: a check that fires on any error ever recorded is\n // red forever, and 265 failures from three fixed days in July would keep it that way.\n const recent = stamped.slice(-BRIDGE_RECENT_ROWS);\n const recentSet = new Set(recent);\n const errorsInRecentRows = recent.filter((x) => isErrorRow(x.row)).length;\n const errorsBeforeThat = stamped.filter((x) => !recentSet.has(x) && isErrorRow(x.row)).length;\n const errorShare = recent.length ? errorsInRecentRows / recent.length : 0;\n measured.recentRows = recent.length;\n measured.errorsInRecentRows = errorsInRecentRows;\n measured.errorsBeforeThat = errorsBeforeThat;\n\n const findings: Finding[] = [];\n\n if (errorsInRecentRows > 0) {\n findings.push({\n check: BRIDGE,\n severity: errorShare >= BRIDGE_ERROR_SHARE_URGENT ? \"urgent\" : \"attention\",\n sentence:\n `The Square link is failing as it runs. ${commas(errorsInRecentRows)} of its last ${commas(recent.length)} ` +\n `entries are failures, which is ${percent(errorShare)} of them. Every one of those is a sale that reached ` +\n `Square and did not reach a customer record in your CRM.`,\n numbers: {\n errorsInRecentRows,\n recentRows: recent.length,\n errorSharePercent: Math.round(errorShare * 100),\n errorsBeforeThat,\n },\n checkFirst:\n `The weekly exception report lists every sale that did not reach a customer record, by name and amount. ` +\n `Work from that list rather than from the log itself, and send me the report if the same name keeps appearing.`,\n });\n }\n\n const r = rhythmOf(stamped.map((x) => x.ms));\n const lastMs = stamped[stamped.length - 1].ms;\n const ageH = (now - lastMs) / HOUR;\n measured.quietForHours = Math.round(ageH * 10) / 10;\n if (r === null) {\n findings.push({\n check: BRIDGE,\n severity: \"note\",\n sentence:\n `The Square link's log holds only ${commas(stamped.length)} dated ${plural(stamped.length, \"entry\", \"entries\")}, ` +\n `which is too little for this to know how often it normally writes something. It cannot yet tell a quiet link ` +\n `from a stopped one.`,\n numbers: { rowsWithATimestamp: stamped.length, needed: MIN_RECORDS_FOR_RHYTHM },\n checkFirst: `Nothing to do today. This will be able to judge the link once its log has a little more history in it.`,\n });\n } else {\n measured.expectByH = Math.round(r.expectByH * 10) / 10;\n if (ageH > r.expectByH) {\n findings.push({\n check: BRIDGE,\n severity: escalate(ageH, r.expectByH),\n sentence:\n `The Square link has written nothing down for ${sayGap(ageH)}. The last thing it recorded was on ` +\n `${sayDate(lastMs)}. It normally writes something every ${sayGap(r.normalGapH)}, so it has not simply gone ` +\n `quiet, it has stopped. Anything taken in Square since then has not reached your CRM.`,\n numbers: {\n quietForHours: Math.round(ageH * 10) / 10,\n lastRowAt: new Date(lastMs).toISOString(),\n normalGapHours: Math.round(r.normalGapH * 10) / 10,\n outOfCharacterAfterHours: Math.round(r.expectByH * 10) / 10,\n rowsWithATimestamp: stamped.length,\n },\n checkFirst:\n `Open the Square link's own page and check it answers. If it does, take one card payment in Square and see ` +\n `whether it appears against a customer in your CRM within a few minutes.`,\n });\n }\n }\n\n return result(findings);\n}\n\n// ---------------------------------------------------------------------------------------------\n// CHECK 5: A FIGURE THAT SHOULD ONLY EVER GROW HAS GONE BACKWARDS.\n//\n// Lifetime totals only go up. When one comes back smaller, the reading is being taken from\n// somewhere else: a source was swapped, a query was cut at a date, a page walk stopped early. Each\n// of those has produced a wrong number in front of this client already, and each was invisible at\n// the time because the smaller figure was perfectly plausible on its own.\n//\n// A FIGURE THAT STOPS BEING REPORTED IS THE SAME DISEASE. It hides exactly what a fall hides, and\n// it looks like nothing at all on a page that only prints what it has.\n// ---------------------------------------------------------------------------------------------\n\nconst BACKWARDS = \"backwards\";\nconst BACKWARDS_TITLE = \"Running totals that should only grow\";\nconst BACKWARDS_LABEL = \"running totals\";\n\nexport function backwardsFindings(snapshots: unknown, labels: unknown): CheckResult {\n const named = (labels ?? {}) as Record;\n const nameOf = (key: string) => String(named?.[key] ?? key);\n const list = (Array.isArray(snapshots) ? snapshots : []) as Snapshot[];\n\n if (list.length === 0) {\n return blindCheck(BACKWARDS, BACKWARDS_TITLE, BACKWARDS_LABEL,\n `This check has no readings of your running totals at all, so it cannot tell whether any of them has gone ` +\n `backwards. A check that inspects nothing is a blind spot, not a clean result, and it is being reported as one.`,\n `Check that the file this keeps its earlier readings in still exists and can be read. Until it can, a total ` +\n `that shrinks will pass unnoticed.`);\n }\n\n const previous = list[list.length - 2];\n const current = list[list.length - 1];\n\n if (list.length < 2) {\n // A FIRST RUN IS NOT A CLEAN RUN. It compared nothing, so it says it compared nothing. This is\n // a note rather than an alarm because there is nothing wrong here, but it is still a finding,\n // because \"nothing to compare\" printed as blank space reads as \"everything checks out\".\n return {\n check: BACKWARDS,\n title: BACKWARDS_TITLE,\n inspected: 0,\n inspectedLabel: BACKWARDS_LABEL,\n measured: { readings: list.length, compared: 0 },\n findings: [{\n check: BACKWARDS,\n severity: \"note\",\n sentence:\n `This is the first time these running totals have been written down, so there is nothing yet to compare ` +\n `them against. That is not a clean result, it is an empty one, and from the next run on any figure that ` +\n `goes backwards will be named here.`,\n numbers: { readings: list.length, compared: 0 },\n checkFirst: `Nothing to do today. Run this again tomorrow and it will have something to compare against.`,\n }],\n };\n }\n\n const prevCounters = (previous?.counters ?? {}) as Record;\n const curCounters = (current?.counters ?? {}) as Record;\n const keys = [...new Set([...Object.keys(prevCounters), ...Object.keys(curCounters)])];\n const inspected = keys.length;\n const prevAt = Date.parse(String(previous?.at ?? \"\"));\n\n if (inspected === 0) {\n return blindCheck(BACKWARDS, BACKWARDS_TITLE, BACKWARDS_LABEL,\n `The last two readings of your running totals carry no figures at all, so there was nothing to compare. ` +\n `A check that inspects nothing is a blind spot, not a clean result, and it is being reported as one.`,\n `Check that the file this keeps its earlier readings in has not been emptied or overwritten.`);\n }\n\n const findings: Finding[] = [];\n for (const key of keys) {\n const before = Number(prevCounters[key]);\n const after = curCounters[key] === undefined || curCounters[key] === null ? null : Number(curCounters[key]);\n if (!Number.isFinite(before)) continue; // nothing to fall FROM: not a finding, just no history\n if (after === null || !Number.isFinite(after as number)) {\n findings.push({\n check: BACKWARDS,\n severity: \"attention\",\n sentence:\n `${nameOf(key)} was being reported and now is not. It read ${commas(before)} on ${sayDate(prevAt)} and the ` +\n `latest reading does not carry it at all. A figure that stops being reported hides exactly what a figure ` +\n `going backwards hides, so it is raised the same way.`,\n numbers: { counter: key, label: nameOf(key), previous: before, current: null, previousAt: previous?.at ?? null },\n checkFirst:\n `Check whether whatever produces this figure answered at all on the last run. A reading that failed and a ` +\n `reading of nought look the same on a page and mean opposite things.`,\n });\n continue;\n }\n if ((after as number) >= before) continue;\n const fell = before - (after as number);\n findings.push({\n check: BACKWARDS,\n severity: \"urgent\",\n sentence:\n `${nameOf(key)} has gone backwards. It read ${commas(before)} on ${sayDate(prevAt)} and reads ` +\n `${commas(after as number)} now, a fall of ${commas(fell)}. Figures like this only ever go up, so a fall means ` +\n `it is being read from somewhere different: a source swapped, a list cut short, or a page walk that stopped ` +\n `early and reported what it had as the whole.`,\n numbers: {\n counter: key,\n label: nameOf(key),\n previous: before,\n current: after,\n fell,\n previousAt: previous?.at ?? null,\n currentAt: current?.at ?? null,\n },\n checkFirst:\n `Do not act on any figure derived from this one until it is explained. Send me this report and I will read ` +\n `the same total straight from the system that owns it.`,\n });\n }\n\n return {\n check: BACKWARDS,\n title: BACKWARDS_TITLE,\n inspected,\n inspectedLabel: BACKWARDS_LABEL,\n measured: { readings: list.length, compared: inspected, comparedAgainst: previous?.at ?? null },\n findings,\n };\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE BUCKETING. Dates cut into windows, which is arithmetic and therefore testable.\n//\n// A RECORD WITH NO READABLE DATE IS NEVER INVENTED INTO A WINDOW. Dropping it understates a\n// window; guessing at it corrupts the baseline every later judgement is made against.\n// ---------------------------------------------------------------------------------------------\n\n/** Payments the bridge saw, cut into equal windows ending now, oldest window first. */\nexport function ratioBuckets(seen: unknown, nowMs: unknown, windowDays: number, windows: number): RatioPoint[] {\n const now = Number(nowMs);\n const spanMs = Math.max(1, Number(windowDays) || 1) * 24 * HOUR;\n const n = Math.max(1, Math.floor(Number(windows) || 1));\n const points = Array.from({ length: n }, (_, i) => {\n const endMs = now - (n - 1 - i) * spanMs;\n return { label: `the ${windowDays} days to ${sayDate(endMs)}`, endMs, total: 0, matched: 0 };\n });\n if (!Number.isFinite(now)) return points;\n for (const p of (Array.isArray(seen) ? seen : []) as any[]) {\n const at = Number(p?.atMs);\n if (!Number.isFinite(at)) continue;\n const back = Math.floor((now - at) / spanMs);\n if (back < 0 || back >= n) continue;\n const point = points[n - 1 - back];\n point.total += 1;\n if (p?.matched === true) point.matched += 1;\n }\n return points;\n}\n\n/** Records of work and the money against them, summed into equal windows, oldest window first. */\nexport function revenuePeriods(records: unknown, nowMs: unknown, windowDays: number, windows: number): RevenuePeriod[] {\n const now = Number(nowMs);\n const spanMs = Math.max(1, Number(windowDays) || 1) * 24 * HOUR;\n const n = Math.max(1, Math.floor(Number(windows) || 1));\n const periods = Array.from({ length: n }, (_, i) => {\n const endMs = now - (n - 1 - i) * spanMs;\n return { label: `the ${windowDays} days to ${sayDate(endMs)}`, endMs, activity: 0, dollars: 0 };\n });\n if (!Number.isFinite(now)) return periods;\n for (const rec of (Array.isArray(records) ? records : []) as any[]) {\n const at = Number(rec?.atMs);\n if (!Number.isFinite(at)) continue;\n const back = Math.floor((now - at) / spanMs);\n if (back < 0 || back >= n) continue;\n const period = periods[n - 1 - back];\n period.activity += 1;\n period.dollars += Number(rec?.dollars) || 0;\n }\n // Rounded to the cent at the end, not per addition: summing floats and rounding once is the only\n // version whose total matches what the CRM itself reports.\n for (const p of periods) p.dollars = Math.round(p.dollars * 100) / 100;\n return periods;\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE WHOLE RUN.\n// ---------------------------------------------------------------------------------------------\n\nexport function runWatch(input: WatchInput): WatchReport {\n // A RUN THAT WAS NEVER TOLD THE TIME JUDGES NOTHING.\n //\n // The dangerous shape this refuses: a replay with a mistyped date silently reporting on today,\n // under a heading naming the date it was asked about, with every figure wrong and nothing in the\n // document able to see it. Inventing a clock here would be the one mistake this whole file could\n // make that nobody downstream could catch.\n const now = input?.nowMs;\n if (!Number.isFinite(now)) {\n return {\n generatedAt: \"not known\",\n headline: \"This check could not run, because it was not told what the time is.\",\n inspected: 0,\n checks: [],\n findings: [{\n check: \"clock\",\n severity: \"urgent\",\n sentence:\n `This run was not told what the time is, so it has judged nothing at all. Every figure in this report is ` +\n `measured against a moment, and inventing one would have produced a page of confident numbers about the ` +\n `wrong day. Nothing here is an all clear.`,\n numbers: { nowMs: String(now), inspected: 0 },\n checkFirst:\n `Run this again with the date it is meant to judge. If this was a replay of a past morning, check the date ` +\n `that was typed for it.`,\n }],\n };\n }\n const at = now as number;\n\n const checks: CheckResult[] = [\n silenceFindings(input?.streams, at),\n matchRatioFindings(input?.ratio?.points, input?.ratio?.subject ?? \"payments\"),\n revenueChannelFindings(input?.revenue?.periods, input?.revenue?.subject ?? \"your bookings\"),\n bridgeFindings(input?.journal, at),\n backwardsFindings(input?.snapshots, input?.counterLabels ?? {}),\n ];\n\n const inspected = checks.reduce((a, c) => a + (c.inspected ?? 0), 0);\n // MOST SEVERE FIRST, so the first thing she reads is the worst thing. A stable sort inside a\n // severity band keeps the checks in the order they ran, which is the order the report explains.\n const rank: Record = { urgent: 0, attention: 1, note: 2 };\n const findings = checks\n .flatMap((c) => c.findings.map((f) => ({ ...f, check: f.check ?? c.check })))\n .map((f, i) => ({ f, i }))\n .sort((a, b) => ((rank[a.f.severity] ?? 3) - (rank[b.f.severity] ?? 3)) || (a.i - b.i))\n .map((x) => x.f);\n\n return {\n generatedAt: new Date(at).toISOString(),\n headline: headlineFor(findings, checks, inspected),\n inspected,\n checks,\n findings,\n };\n}\n\n/**\n * The one line at the top. It leads with what has to happen today, and it never says a reassuring\n * thing about a run that could not see anything: \"nothing wrong\" and \"nothing looked at\" have to\n * be different sentences or the second one does the damage of the first.\n */\nexport function headlineFor(findings: Finding[], checks: CheckResult[], inspected: number): string {\n // A finding from a check that read NOTHING is a blind spot, never a problem with the business.\n // The owning check is the authority; a free-form number inside the finding cannot change class.\n const isBlind = (finding: Finding) => isBlindFindingForChecks(finding, checks);\n const n = (s: Severity) => findings.filter((f) => f.severity === s && !isBlind(f)).length;\n const urgent = n(\"urgent\");\n const attention = n(\"attention\");\n const notes = findings.filter((f) => f.severity === \"note\" || isBlind(f)).length;\n if (urgent) {\n return `${capitalise(countWord(urgent))} ${plural(urgent, \"thing needs\", \"things need\")} you to look at today` +\n `${attention ? `, and ${countWord(attention)} more ${plural(attention, \"is\", \"are\")} worth a look this week` : \"\"}.`;\n }\n if (attention) {\n return `${capitalise(countWord(attention))} ${plural(attention, \"thing is\", \"things are\")} worth a look this week.`;\n }\n if (notes) {\n // W42: when NOTHING could be read, \"nothing looks wrong\" is a reassuring sentence about a run\n // that judged nothing. Lead with the blindness instead. Only say the reassuring half when at\n // least one check actually read something and came back clean.\n const readSomething = checks.filter((c) => Number(c?.inspected) > 0).length;\n if (!readSomething) {\n return `Nothing could be checked. ${capitalise(countWord(notes))} ` +\n `${plural(notes, \"check\", \"checks\")} read no data at all, so this run judges nothing either way.`;\n }\n return `Nothing looks wrong in what could be checked, and ${countWord(notes)} ` +\n `${plural(notes, \"thing\", \"things\")} this monitor cannot see yet.`;\n }\n return `Nothing looks wrong. ${capitalise(countWord(checks.length))} checks ran and read ` +\n `${commas(inspected)} records between them.`;\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE COPY SHE READS.\n//\n// TWO RULES, ENFORCED MECHANICALLY, and they run over the GENERATED report rather than over any\n// source file, because the sentences are built at run time and a rule that only reads source\n// cannot see them.\n// ---------------------------------------------------------------------------------------------\n\n/** One entry per rule broken, so an em dash and a spaced hyphen in one page are one problem, not two. */\nexport function copyProblems(text: unknown): string[] {\n const s = String(text ?? \"\");\n const out: string[] = [];\n // The name of a service this business does not offer. She asked for it never to appear.\n if (/\\bday\\s?care\\b/i.test(s)) out.push(\"names a service this business does not offer\");\n // A dash used as punctuation, in any of its forms. Hyphens INSIDE words are fine and common:\n // \"well known\" hyphenated, a phone number, a field name. Only a dash standing alone counts.\n if (/(^|\\s)[-–—](\\s|$)|[–—]/.test(s)) out.push(\"uses a dash as punctuation\");\n return out;\n}\n\n/**\n * THE ENGINE'S OWN VIEW of the report: every finding, the figures behind it, and what every check\n * read including the checks that found nothing.\n *\n * WHY THE CHECKS THAT FOUND NOTHING ARE PRINTED. A report that prints only problems gives the\n * reader no way to tell \"checked and clean\" from \"checked nothing\", and that exact confusion is\n * what let February run for five months.\n *\n * This is the workings, not the page for the owner. scripts/watch-run.mjs renders her page from\n * the same report object and keeps this one in the repo, so a queried figure can still be traced.\n */\nexport function watchReportMarkdown(report: WatchReport, title: unknown): string {\n const heading = String(title ?? \"Early warning check\");\n const findings = Array.isArray(report?.findings) ? report.findings : [];\n const checks = Array.isArray(report?.checks) ? report.checks : [];\n // v1.1 (16 Aug) — THE SPLIT IS \"DID IT READ ANYTHING\", NOT SEVERITY ALONE. A blind check keeps\n // severity \"urgent\" (six tests hold that, and it must never go quiet), but it is not a fault in\n // the business and it must not be filed as one. Before this, the report opened \"Two things need\n // you to look at today\" when both were checks that had never been wired up — the exact shape of\n // failure this page exists to prevent, pointed inward.\n const readNothing = (finding: Finding) => isBlindFindingForChecks(finding, checks);\n const loud = findings.filter((f) => f.severity !== \"note\" && !readNothing(f));\n const notes = findings.filter((f) => f.severity === \"note\" || readNothing(f));\n const band: Record = {\n urgent: \"Look at this today\",\n attention: \"Worth a look this week\",\n note: \"The monitor talking about itself\",\n };\n const figures = (o: Record) =>\n Object.entries(o ?? {})\n .filter(([, v]) => v !== undefined && (typeof v !== \"object\" || v === null))\n .map(([k, v]) => `${k}: ${v === null ? \"not known\" : String(v)}`)\n .join(\", \");\n\n const out: string[] = [];\n out.push(`# ${heading}`);\n out.push(\"\");\n out.push(report?.headline ?? \"\");\n out.push(\"\");\n out.push(`Read at ${report?.generatedAt ?? \"not known\"}. ${commas(report?.inspected ?? 0)} records inspected across ${checks.length} checks.`);\n out.push(\"\");\n\n const say = (f: Finding) => {\n out.push(`### ${band[f.severity] ?? f.severity}. ${f.check}`);\n out.push(\"\");\n out.push(f.sentence);\n out.push(\"\");\n const fig = figures(f.numbers);\n if (fig) { out.push(`The figures behind that: ${fig}`); out.push(\"\"); }\n if (f.checkFirst) { out.push(`Check first: ${f.checkFirst}`); out.push(\"\"); }\n };\n\n if (loud.length) {\n out.push(`## What needs your attention`);\n out.push(\"\");\n for (const f of loud) say(f);\n }\n if (notes.length) {\n out.push(`## What this monitor cannot see yet`);\n out.push(\"\");\n out.push(\n `These are not problems with the business. They are the monitor saying where it is unable to judge anything, ` +\n `which is worth knowing rather than reading as a clean result.`);\n out.push(\"\");\n for (const f of notes) say(f);\n }\n\n out.push(`## What every check read, including the ones that found nothing`);\n out.push(\"\");\n for (const c of checks) {\n out.push(`${c.title}: read ${commas(c.inspected ?? 0)} ${c.inspectedLabel}, and raised ` +\n `${commas(c.findings?.length ?? 0)} ${plural(c.findings?.length ?? 0, \"finding\", \"findings\")}.`);\n const fig = figures(c.measured);\n if (fig) out.push(`The figures behind that: ${fig}`);\n out.push(\"\");\n }\n\n const blind = blindSpots(checks);\n out.push(`## Whether this report can be believed`);\n out.push(\"\");\n out.push(blind.length\n ? `${capitalise(countWord(blind.length))} ${plural(blind.length, \"check\", \"checks\")} inspected nothing and said ` +\n `nothing about it, which means this report is not watching what it claims to. Do not read it as a clean result.`\n : `Every check above reported the size of what it read, and every check that read nothing said so in its own ` +\n `finding rather than passing silently. A check that inspects nothing is a blind spot, not an all clear, and ` +\n `that is the one rule this whole report rests on.`);\n out.push(\"\");\n\n return out.join(\"\\n\").replace(/\\n{3,}/g, \"\\n\\n\");\n}\n",[232],"5c3e5160-8a18-4ca4-9b52-47c0de7c9b06","watch-view.ts","d0159a5c-98c4-11f1-99c3-1607ee4eb77e",1232,["D",1787226716573],3,"http","// READING THE EARLY-WARNING MONITOR. v1.1, 18 Aug 2026.\n//\n// The scheduled monitor writes one receipt blob. This endpoint leads with receipt health so a\n// stale, degraded, failed, or never-successful monitor cannot look like a clean business result.\n\nimport { watchReportMarkdown } from \"./watch.ts\";\nimport {\n WATCH_BLOB,\n reportFindingSeverity,\n validateWatchBlob,\n validatedWatchFindingSummary,\n type ReportFindingSeverity,\n type WatchFindingSummary,\n} from \"./watch-cron.ts\";\n\nconst STALE_HOURS = 36;\nconst COVERAGE =\n \"Runs automatically: CRM revenue against activity, silence on CRM payments and new contacts, \" +\n \"running totals, Square match ratio, and bridge-journal health. Square checks run only when the \" +\n \"credentialled bridge journal validates; missing CRM contact or bridge evidence marks the run \" +\n \"degraded and names the blind checks instead of reporting full health.\";\n\nasync function sha256Hex(s: string): Promise {\n const b = await crypto.subtle.digest(\"SHA-256\", new TextEncoder().encode(s));\n return [...new Uint8Array(b)].map((x) => x.toString(16).padStart(2, \"0\")).join(\"\");\n}\n\nasync function authorised(k: string): Promise {\n const configured = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\");\n if (!k || !configured || !/^[0-9a-f]{64}$/i.test(configured)) return false;\n const got = await sha256Hex(k);\n const want = configured.toLowerCase();\n if (got.length !== want.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ want.charCodeAt(i);\n return d === 0;\n}\n\nfunction invalidView(state: \"invalid\" | \"unreadable\", what: string, reason: string): any {\n return {\n ok: false,\n state,\n what,\n health: {\n reportAgeHours: null,\n stale: true,\n hasSuccessfulReport: false,\n lastRunOk: false,\n persistedLastRunOk: false,\n degraded: true,\n sourceDegraded: true,\n findingSeverity: \"none\",\n actionableFindingSeverity: \"none\",\n blind: false,\n blindFindingCount: 0,\n actionableFindingCount: 0,\n lastRunAt: null,\n lastRunError: reason,\n coverage: COVERAGE,\n schemaError: reason,\n },\n inspected: null,\n report: null,\n snapshots: [],\n };\n}\n\n/** Pure receipt classification, shared by the endpoint and executable tests. */\nexport function watchViewData(stored: unknown, nowMs = Date.now(), readError = \"\"): any {\n if (readError) {\n return invalidView(\n \"unreadable\",\n \"The stored early-warning receipt could not be read. This is not a first run or an all clear.\",\n readError,\n );\n }\n if (stored == null) {\n return {\n ok: false,\n state: \"never-run\",\n what: \"The early-warning monitor has not attempted a run yet.\",\n };\n }\n\n if (!Number.isFinite(nowMs)) {\n return invalidView(\"invalid\", \"The monitor receipt cannot be judged because the current clock is invalid.\",\n \"current time is invalid\");\n }\n let validated: ReturnType;\n try {\n validated = validateWatchBlob(stored, nowMs);\n stored = validated;\n } catch (error) {\n return invalidView(\n \"invalid\",\n \"The stored monitor receipt is malformed or future-dated and cannot be trusted.\",\n error instanceof Error ? error.message : \"stored receipt validation failed\",\n );\n }\n const emptySummary = (): WatchFindingSummary => ({\n findings: [], blind: [], actionable: [], severity: \"none\", actionableSeverity: \"none\",\n });\n const successful = validated.hasSuccessfulReport;\n const findingSummary = successful ? validatedWatchFindingSummary(validated.report) : emptySummary();\n const findingSeverity: ReportFindingSeverity = successful\n ? reportFindingSeverity(validated.report)\n : \"urgent\";\n const actionableFindingSeverity = findingSummary.actionableSeverity;\n const hasActionableFinding = findingSummary.actionable.length > 0;\n const hasBlindFinding = findingSummary.blind.length > 0;\n\n const reportMs = Date.parse(validated.report.generatedAt);\n const ageHours = (nowMs - reportMs) / 3_600_000;\n const stale = ageHours > STALE_HOURS;\n const persistedLastRunOk = validated.lastRun.ok;\n const sourceDegraded = validated.lastRun.degraded === true;\n const lastRunError = validated.lastRun.error;\n // Severity is authoritative even for a receipt written by the pre-repair cron with ok:true.\n // Keep that raw bit for diagnostics, but never expose it as effective health in JSON or prose.\n const lastRunOk = persistedLastRunOk && !sourceDegraded && !hasActionableFinding && !hasBlindFinding;\n const attemptFailed = !persistedLastRunOk && !sourceDegraded && !!lastRunError;\n const hasSuccessfulReport = successful;\n\n let state: \"not-yet-successful\" | \"degraded\" | \"urgent\" | \"failed\" | \"stale\" | \"healthy\";\n if (!hasSuccessfulReport) state = \"not-yet-successful\";\n else if (sourceDegraded) state = \"degraded\";\n else if (attemptFailed) state = \"failed\";\n else if (stale) state = \"stale\";\n else if (actionableFindingSeverity === \"urgent\") state = \"urgent\";\n else if (actionableFindingSeverity === \"attention\") state = \"degraded\";\n else if (hasBlindFinding) state = \"degraded\";\n else if (!lastRunOk) state = \"failed\";\n else state = \"healthy\";\n\n const what = state === \"not-yet-successful\"\n ? \"The early-warning monitor has not completed a successful run. Its failure is shown below.\"\n : state === \"degraded\"\n ? sourceDegraded\n ? \"The latest report contains usable evidence, but one or more monitoring sources could not be read.\" +\n (hasActionableFinding ? ` The available evidence also contains ${actionableFindingSeverity} findings.` : \"\")\n : hasActionableFinding\n ? \"The latest report contains findings that need attention. All configured evidence sources were read.\"\n : \"The latest report cannot judge one or more checks because they inspected no evidence. This is not a business alert or an all clear.\"\n : state === \"urgent\"\n ? \"The latest report contains urgent findings that need action. All configured evidence sources were read.\"\n : state === \"failed\"\n ? \"The latest attempt failed. The last completed report is retained below.\"\n : state === \"stale\"\n ? \"The latest completed report is stale; the monitor may have stopped.\" +\n (hasActionableFinding ? ` Its retained report contains ${actionableFindingSeverity} findings.` :\n hasBlindFinding ? \" Its retained report also contains checks that inspected no evidence.\" : \"\")\n : \"The latest automatic monitor run completed with all configured evidence sources.\";\n\n return {\n ok: state === \"healthy\",\n state,\n what,\n builtAt: validated.builtAt,\n health: {\n reportAgeHours: +ageHours.toFixed(1),\n stale,\n hasSuccessfulReport,\n lastRunOk,\n persistedLastRunOk,\n degraded: sourceDegraded,\n sourceDegraded,\n findingSeverity,\n actionableFindingSeverity,\n blind: hasBlindFinding,\n blindFindingCount: findingSummary.blind.length,\n actionableFindingCount: findingSummary.actionable.length,\n lastRunAt: validated.lastRun.at,\n lastRunError: lastRunError || null,\n coverage: COVERAGE,\n },\n inspected: validated.inspected,\n report: validated.report,\n snapshots: validated.snapshots,\n };\n}\n\n/** Render only detached, classified view data. The original blob value never crosses this API. */\nexport function watchViewText(data: any): string {\n if ([\"never-run\", \"invalid\", \"unreadable\"].includes(String(data?.state))) {\n const detail = data?.health?.schemaError ? `\\nReason: ${data.health.schemaError}\\n` : \"\\n\";\n return `${data?.what ?? \"The stored monitor receipt is unavailable.\"}${detail}`;\n }\n\n const h = data.health;\n const age = h.reportAgeHours === null ? \"an unreadable age\" : `${h.reportAgeHours}h ago`;\n const runLabel = data.state === \"not-yet-successful\" ? \"NOT YET SUCCESSFUL\"\n : data.state === \"urgent\" ? \"URGENT FINDINGS\"\n : data.state === \"degraded\" ? (h.sourceDegraded ? \"DEGRADED\" : h.blind ? \"CANNOT TELL\" : \"ATTENTION\")\n : data.state === \"failed\" ? \"FAILED\"\n : data.state === \"stale\" ? \"STALE\"\n : \"succeeded\";\n const inspected = data.inspected;\n const report = data.report;\n const head = [\n data.what,\n `Report generated ${report?.generatedAt ?? \"at an unreadable time\"} (${age})` +\n `; receipt stored ${data.builtAt ?? \"at an unreadable time\"}` +\n `${h.stale ? \" ***STALE OR UNREADABLE***\" : \"\"}`,\n `Last run ${runLabel}${h.lastRunError ? `: ${h.lastRunError}` : \"\"} at ${h.lastRunAt ?? \"an unreadable time\"}`,\n `Inspected ${inspected?.transactions ?? 0} payment records across ${inspected?.pages ?? 0} page(s)` +\n (inspected?.truncated ? \" — TRUNCATED\" : \"\"),\n h.coverage,\n \"\",\n ].join(\"\\n\");\n\n const reportText = report && Array.isArray(report.findings)\n ? watchReportMarkdown(report, \"The Dogs Spot — early warning\")\n : \"The stored monitor report is malformed and cannot be rendered.\\n\";\n return head + reportText;\n}\n\nexport default async function (req: Request): Promise {\n const u = new URL(req.url);\n if (!(await authorised(u.searchParams.get(\"k\") ?? \"\"))) return new Response(\"Not found\", { status: 404 });\n\n let stored: unknown = null;\n let readError = \"\";\n try {\n const { blob } = await import(\"https://esm.town/v/std/blob\");\n stored = await blob.getJSON(WATCH_BLOB);\n } catch {\n readError = \"watch receipt storage read failed\";\n }\n\n const data = watchViewData(stored, Date.now(), readError);\n if (u.searchParams.get(\"f\") === \"json\") return Response.json(data, { status: 200 });\n return new Response(watchViewText(data), {\n headers: { \"Content-Type\": \"text/plain; charset=utf-8\" },\n });\n}\n",[240],"81b0edc8-3573-4196-8a6a-bb34c5b3b4ab","watch-cron.ts","cfa8812e-98c4-11f1-9f38-1607ee4eb77e",1231,["D",1787226711931],2,"interval","\nimport {\n headlineFor,\n isBlindFindingForChecks,\n REVENUE_ACTIVITY_HELD,\n REVENUE_DOLLAR_FALL,\n REVENUE_MIN_BASELINE_ACTIVITY,\n REVENUE_MIN_PERIODS,\n revenueChannelFindings,\n runWatch,\n ratioBuckets,\n revenuePeriods,\n type Finding,\n type WatchReport,\n} from \"./watch.ts\";\nimport { paymentLedger } from \"./facts.ts\";\nimport { fetchPayments, MIN_REAL_PAYMENT, toPayment } from \"./payments-source.ts\";\n\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst PAYMENT_PATH = \"/payments/transactions\";\nconst CONTACT_PATH = \"/contacts/\";\nconst CONTACT_PAGE_SIZE = \"100\";\nconst CONTACT_QUERY_KEYS = new Set([\"locationId\", \"limit\", \"startAfter\", \"startAfterId\"]);\nexport const BRIDGE_URL = \"https://amir5--41ace24c7e2111f18c9d1607ee4eb77e.web.val.run\";\nconst UA =\n \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0 Safari/537.36\";\nconst DAY = 86_400_000;\nconst PAYMENT_CURRENCY = \"USD\";\nconst PAYMENT_AMOUNT_UNIT = \"major\";\nconst KNOWN_PAYMENT_STATUSES = new Set([\"succeeded\", \"failed\", \"pending\"]);\nconst CRM_REQUEST_TIMEOUT_MS = 15_000;\nconst BRIDGE_REQUEST_TIMEOUT_MS = 15_000;\n\nexport const WATCH_BLOB = \"watch_report\";\nexport const REVENUE_WINDOW_DAYS = 28;\nexport const REVENUE_WINDOWS = 7;\nexport const RATIO_WINDOW_DAYS = 7;\nexport const RATIO_WINDOWS = 6;\nexport const MONITORING_HORIZON_DAYS = REVENUE_WINDOW_DAYS * REVENUE_WINDOWS;\nexport const MAX_SNAPSHOTS = MONITORING_HORIZON_DAYS + 2;\nexport const REAL_MONEY = MIN_REAL_PAYMENT;\nexport const PAGE_CAP = 40;\nexport const BRIDGE_JOURNAL_CAP = 1_500;\nexport const MAX_TRANSACTION_DROP_SHARE = 0.10;\nexport const OVERALL_BUDGET_MS = 45_000;\n\nexport const LIFETIME_COUNTER_KEYS = [\n \"crmPaymentRecords\",\n \"crmPaymentDollarsLifetime\",\n] as const;\ntype LifetimeCounterKey = typeof LIFETIME_COUNTER_KEYS[number];\ntype LifetimeCounters = Record;\ntype Snapshot = { at: string; counters: LifetimeCounters };\ntype ResponseLike = { ok: boolean; status: number; json: () => Promise };\ntype RequestFn = (url: string, init?: RequestInit) => Promise;\ntype BlobLike = {\n getJSON: (key: string) => Promise;\n setJSON: (key: string, value: unknown) => Promise;\n};\n\nexport type ReportFindingSeverity = \"urgent\" | \"attention\" | \"note\" | \"none\";\n\nexport type WatchFindingSummary = {\n findings: Finding[];\n blind: Finding[];\n actionable: Finding[];\n severity: ReportFindingSeverity;\n actionableSeverity: ReportFindingSeverity;\n};\n\nexport type WatchInspected = {\n transactions: number;\n expectedTransactions: number;\n pages: number;\n truncated: boolean;\n validTransactionTimestamps: number;\n paymentStatuses: { succeeded: number; failed: number; pending: number };\n currency: \"USD\";\n amountUnit: \"major\";\n zeroOrTest: number;\n unknownSourceTypes: string[];\n contacts: number;\n contactPages: number;\n bridgeJournalRows: number;\n bridgePayments: number;\n bridgeAtCapacity: boolean;\n bridgeHorizonComplete: boolean;\n};\n\nexport type WatchBlob = {\n report: WatchReport;\n builtAt: string;\n hasSuccessfulReport: boolean;\n inspected: WatchInspected;\n lastRun: {\n at: string;\n ok: boolean;\n degraded?: boolean;\n findingSeverity?: ReportFindingSeverity;\n ms: number;\n error: string;\n };\n snapshots: Snapshot[];\n highWater?: Snapshot;\n};\n\nexport type BridgeEvidence = {\n journal: any[];\n payments: number;\n journalRows: number;\n atCapacity: boolean;\n horizonComplete: boolean;\n oldestAt: string;\n ratio: { subject: string; points: ReturnType };\n};\n\nexport type BridgeReadOptions = {\n admin?: string;\n bridgeUrl?: string;\n request?: RequestFn;\n timeoutMs?: number;\n};\n\nexport type TransactionEvidence = {\n rows: { atMs: number; dollars: number }[];\n count: number;\n expected: number;\n pages: number;\n truncated: false;\n validTimestamps: number;\n statuses: { succeeded: number; failed: number; pending: number };\n currency: \"USD\";\n amountUnit: \"major\";\n zeroOrTest: number;\n unknownSourceTypes: string[];\n};\n\nexport type ContactEvidence = { timestamps: number[]; rows: number; pages: number };\n\nexport type ScheduledWatchDeps = {\n blob?: BlobLike;\n env?: (name: string) => string | undefined;\n request?: RequestFn;\n now?: () => number;\n wallNow?: () => number;\n log?: (line: string) => void;\n runWatchFn?: typeof runWatch;\n};\n\nexport type ScheduledWatchResult = { published: boolean; degraded: boolean; error: string };\n\nconst envValue = (name: string): string | undefined => {\n try {\n return typeof Deno !== \"undefined\" ? Deno.env.get(name) : undefined;\n } catch {\n return undefined;\n }\n};\n\nconst errorText = (value: unknown): string => value instanceof Error ? value.message : String(value);\n\nexport function redactSecrets(value: unknown, known: string[] = []): string {\n let text = errorText(value);\n for (const secret of known.filter((x) => typeof x === \"string\" && x.length >= 4)) {\n text = text.split(secret).join(\"[REDACTED]\");\n }\n return text\n .replace(/Bearer\\s+[^\\s,;]+/gi, \"Bearer [REDACTED]\")\n .replace(/([?&](?:admin|token|api[_-]?key|secret)=)[^&\\s]+/gi, \"$1[REDACTED]\")\n .replace(/\\b((?:admin|token|api[_-]?key|secret)\\s*[:=]\\s*)[^\\s,;]+/gi, \"$1[REDACTED]\")\n .replace(/\\b(?:pit-|ghl_|admin_)[A-Za-z0-9._~-]{12,}/g, \"[REDACTED]\")\n .slice(0, 240);\n}\n\nfunction assertCrmUrl(raw: string, allowedPaths = new Set([PAYMENT_PATH, CONTACT_PATH])): URL {\n let target: URL;\n try {\n target = new URL(raw, GHL);\n } catch {\n throw new Error(\"CRM URL is invalid\");\n }\n if (target.protocol !== \"https:\" || target.origin !== GHL || target.username || target.password) {\n throw new Error(\"refusing a URL outside the CRM origin\");\n }\n if (!allowedPaths.has(target.pathname)) throw new Error(\"refusing an undocumented CRM endpoint\");\n return target;\n}\n\nfunction assertContactPageUrl(raw: string, continuation: boolean): URL {\n const target = assertCrmUrl(raw, new Set([CONTACT_PATH]));\n if (target.hash) throw new Error(\"contact pagination URL contains an unsafe fragment\");\n\n for (const key of target.searchParams.keys()) {\n if (!CONTACT_QUERY_KEYS.has(key)) {\n throw new Error(`contact pagination URL uses an unexpected query route: ${key || \"(empty)\"}`);\n }\n }\n const one = (key: string): string => {\n const values = target.searchParams.getAll(key);\n if (values.length !== 1) {\n throw new Error(`contact pagination URL must contain exactly one ${key}`);\n }\n return values[0];\n };\n\n const locationId = one(\"locationId\");\n if (!/^[A-Za-z0-9]{20}$/.test(locationId)) {\n throw new Error(\"contact pagination URL contains an unsafe locationId\");\n }\n if (locationId !== LOC) {\n throw new Error(\"contact pagination URL is not pinned to the Dogs Spot locationId\");\n }\n if (one(\"limit\") !== CONTACT_PAGE_SIZE) {\n throw new Error(`contact pagination URL changed the requested limit from ${CONTACT_PAGE_SIZE}`);\n }\n\n const startAfter = target.searchParams.getAll(\"startAfter\");\n const startAfterId = target.searchParams.getAll(\"startAfterId\");\n if (!continuation) {\n if (startAfter.length || startAfterId.length) {\n throw new Error(\"initial contact query unexpectedly contains a pagination cursor\");\n }\n return target;\n }\n if (startAfter.length !== 1 || startAfterId.length !== 1) {\n throw new Error(\"contact pagination URL must contain one complete cursor pair\");\n }\n if (!/^\\d{1,20}$/.test(startAfter[0]) || !/^[A-Za-z0-9_-]{1,128}$/.test(startAfterId[0])) {\n throw new Error(\"contact pagination URL contains an unsafe cursor\");\n }\n return target;\n}\n\nfunction bridgeTarget(configured: string): URL {\n let url: URL;\n try {\n url = new URL(configured || BRIDGE_URL);\n if (url.protocol !== \"https:\") throw new Error(\"HTTPS is required\");\n } catch {\n throw new Error(\"bridge journal unavailable: BRIDGE_URL is invalid\");\n }\n const allowed = new URL(BRIDGE_URL);\n if (url.origin !== allowed.origin || url.hostname !== allowed.hostname ||\n url.pathname !== allowed.pathname || url.username || url.password) {\n throw new Error(\"bridge journal unavailable: URL is outside the exact allowed origin\");\n }\n url.search = \"\";\n url.hash = \"\";\n return url;\n}\n\nexport async function readBridgeEvidence(\n nowMs: number,\n options: BridgeReadOptions = {},\n): Promise {\n if (!Number.isFinite(nowMs)) throw new Error(\"bridge journal unavailable: current time is invalid\");\n const admin = (options.admin ?? envValue(\"BRIDGE_ADMIN\") ?? \"\").trim();\n if (!admin) throw new Error(\"bridge journal unavailable: BRIDGE_ADMIN is not configured\");\n\n const configuredUrl = (options.bridgeUrl ?? envValue(\"BRIDGE_URL\") ?? \"\").trim();\n const url = bridgeTarget(configuredUrl);\n url.searchParams.set(\"dump\", \"1\");\n url.searchParams.set(\"admin\", admin);\n\n const timeoutMs = options.timeoutMs ?? BRIDGE_REQUEST_TIMEOUT_MS;\n if (!Number.isFinite(timeoutMs) || timeoutMs <= 0) throw new Error(\"bridge journal request budget is exhausted\");\n let response: ResponseLike;\n try {\n response = await (options.request ?? fetch)(url.toString(), {\n method: \"GET\",\n redirect: \"manual\",\n signal: AbortSignal.timeout(Math.max(1, Math.floor(timeoutMs))),\n }) as ResponseLike;\n } catch {\n throw new Error(\"bridge journal request failed\");\n }\n if (response.status >= 300 && response.status < 400) {\n throw new Error(`bridge journal refused redirect HTTP ${response.status}`);\n }\n if (!response.ok) throw new Error(`bridge journal request failed with HTTP ${response.status}`);\n\n let journal: unknown;\n try {\n journal = await response.json();\n } catch {\n throw new Error(\"bridge journal response was not valid JSON\");\n }\n if (!Array.isArray(journal)) throw new Error(\"bridge journal response was not an array\");\n if (journal.length === 0) {\n throw new Error(\"bridge journal returned zero rows; refusing to publish a zero-data watch report\");\n }\n if (journal.length > BRIDGE_JOURNAL_CAP) {\n throw new Error(`bridge journal exceeded its known ${BRIDGE_JOURNAL_CAP}-row cap`);\n }\n\n const times = journal.map((row, i) => {\n if (!row || typeof row !== \"object\" || Array.isArray(row)) {\n throw new Error(`bridge journal row ${i + 1} is malformed`);\n }\n const at = Date.parse(typeof row.ts === \"string\" ? row.ts : \"\");\n if (!Number.isFinite(at)) throw new Error(`bridge journal row ${i + 1} has an invalid timestamp`);\n if (at > nowMs + 5 * 60_000) throw new Error(`bridge journal row ${i + 1} has a future timestamp`);\n return at;\n });\n\n const ledger = paymentLedger(journal);\n if (ledger.length === 0) {\n throw new Error(\"bridge journal contained no Square payment records; refusing to publish a zero match ratio\");\n }\n if (ledger.some((row) => !Number.isFinite(row.atMs))) {\n throw new Error(\"bridge journal contains a Square payment with no readable timestamp\");\n }\n\n const oldestMs = Math.min(...times);\n const ratioStart = nowMs - RATIO_WINDOW_DAYS * RATIO_WINDOWS * DAY;\n const atCapacity = journal.length === BRIDGE_JOURNAL_CAP;\n const horizonComplete = !atCapacity || oldestMs <= ratioStart;\n if (!horizonComplete) {\n throw new Error(\"bridge journal history is truncated inside the match-ratio horizon\");\n }\n\n return {\n journal,\n payments: ledger.length,\n journalRows: journal.length,\n atCapacity,\n horizonComplete,\n oldestAt: new Date(oldestMs).toISOString(),\n ratio: {\n subject: \"Square payments\",\n points: ratioBuckets(ledger, nowMs, RATIO_WINDOW_DAYS, RATIO_WINDOWS),\n },\n };\n}\n\nexport async function readTransactions(\n get: (url: string) => Promise,\n nowMs = Date.now(),\n options: { pageSize?: number; pageCap?: number } = {},\n): Promise {\n const rawRows: any[] = [];\n const source = await fetchPayments(async (url) => {\n const body = await get(url);\n if (isRecord(body) && Array.isArray(body.data)) rawRows.push(...body.data);\n return body;\n }, {\n locationId: LOC,\n pageSize: options.pageSize,\n pageCap: options.pageCap ?? PAGE_CAP,\n now: nowMs,\n });\n\n const count = source.source.totalCount;\n if (count === 0) throw new Error(\"payment source returned zero transactions; refusing to publish\");\n if (rawRows.length !== count) throw new Error(`payment source read ${rawRows.length} of ${count}`);\n\n const statuses = { succeeded: 0, failed: 0, pending: 0 };\n let zeroOrTest = 0;\n const rows = rawRows.map((raw) => {\n const payment = toPayment(raw);\n if (!KNOWN_PAYMENT_STATUSES.has(payment.status)) {\n throw new Error(`unknown payment status for ${payment.id}: refusing to convert it to zero dollars`);\n }\n if (payment.status === \"succeeded\") statuses.succeeded++;\n else if (payment.status === \"failed\") statuses.failed++;\n else statuses.pending++;\n\n const statedCurrency = raw.currency ?? raw.currencyCode;\n if (statedCurrency != null &&\n (typeof statedCurrency !== \"string\" || statedCurrency.trim().toUpperCase() !== PAYMENT_CURRENCY)) {\n throw new Error(`payment ${payment.id} has an unsupported currency`);\n }\n if (!payment.at) throw new Error(`payment ${payment.id} has no createdAt timestamp`);\n const atMs = Date.parse(payment.at);\n if (!Number.isFinite(atMs)) throw new Error(`payment ${payment.id} has an invalid timestamp`);\n\n const isRevenue = payment.status === \"succeeded\" && payment.amount >= REAL_MONEY;\n if (payment.status === \"succeeded\" && !isRevenue) zeroOrTest++;\n return { atMs, dollars: isRevenue ? payment.amount : 0 };\n });\n\n return {\n rows,\n count,\n expected: source.source.totalCount,\n pages: source.source.pages,\n truncated: false,\n validTimestamps: rows.length,\n statuses,\n currency: PAYMENT_CURRENCY,\n amountUnit: PAYMENT_AMOUNT_UNIT,\n zeroOrTest,\n unknownSourceTypes: source.unknownTypes,\n };\n}\n\nexport async function readContactTimes(\n get: (url: string) => Promise,\n pageLimit = 3,\n nowMs = Date.now(),\n): Promise {\n if (!Number.isInteger(pageLimit) || pageLimit < 1 || pageLimit > 10) {\n throw new Error(\"invalid contact page limit\");\n }\n if (!Number.isFinite(nowMs)) throw new Error(\"contact source current time is invalid\");\n const timestamps: number[] = [];\n const seenUrls = new Set();\n let pages = 0;\n let url: URL | null = assertContactPageUrl(\n `${GHL}${CONTACT_PATH}?locationId=${LOC}&limit=${CONTACT_PAGE_SIZE}`,\n false,\n );\n while (url && pages < pageLimit) {\n const target = url;\n if (seenUrls.has(target.toString())) throw new Error(\"contact pagination repeated a page URL\");\n seenUrls.add(target.toString());\n\n const page = await get(target.toString());\n if (!isRecord(page)) {\n throw new Error(`contact page ${pages + 1} is malformed`);\n }\n if (!Array.isArray(page.contacts)) throw new Error(`contact page ${pages + 1} has no contacts array`);\n if (!isRecord(page.meta)) {\n throw new Error(`contact page ${pages + 1} has no metadata object`);\n }\n if (page.contacts.length > 100) throw new Error(`contact page ${pages + 1} exceeds its requested limit`);\n if (page.meta.nextPageUrl != null &&\n (typeof page.meta.nextPageUrl !== \"string\" || !page.meta.nextPageUrl.trim())) {\n throw new Error(`contact page ${pages + 1} has an invalid nextPageUrl`);\n }\n\n for (const contact of page.contacts) {\n if (!contact || typeof contact !== \"object\" || Array.isArray(contact)) {\n throw new Error(`contact page ${pages + 1} contains a malformed row`);\n }\n const at = Date.parse(String(contact.dateAdded ?? \"\"));\n if (!Number.isFinite(at)) throw new Error(\"contact row has an invalid dateAdded timestamp\");\n if (at > nowMs) throw new Error(\"contact row has a future dateAdded timestamp\");\n if (timestamps.length && at > timestamps[timestamps.length - 1]) {\n throw new Error(\"contact pages are not pinned newest-first\");\n }\n timestamps.push(at);\n }\n pages++;\n\n const next = page.meta.nextPageUrl ?? null;\n url = next ? assertContactPageUrl(next, true) : null;\n }\n if (timestamps.length === 0) throw new Error(\"contact source returned zero timestamps\");\n return { timestamps, rows: timestamps.length, pages };\n}\n\nconst CANONICAL_UTC_TIME = /^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}\\.\\d{3}Z$/;\nconst MAX_REPORT_PERSIST_LAG_MS = 5 * 60_000;\n\nconst isRecord = (value: unknown): value is Record => {\n try {\n return !!value && typeof value === \"object\" && !Array.isArray(value) &&\n Object.getPrototypeOf(value) === Object.prototype;\n } catch {\n return false;\n }\n};\n\nconst isNormalObjectDataDescriptor = (descriptor: PropertyDescriptor | undefined): boolean =>\n descriptor !== undefined && Object.prototype.hasOwnProperty.call(descriptor, \"value\") &&\n descriptor.enumerable === true && descriptor.writable === true && descriptor.configurable === true;\n\nfunction hasExactKeys(\n value: Record,\n required: readonly string[],\n optional: readonly string[] = [],\n): boolean {\n try {\n const allowed = new Set([...required, ...optional]);\n const keys = Reflect.ownKeys(value);\n return required.every((key) => keys.includes(key)) &&\n keys.every((key) => typeof key === \"string\" && allowed.has(key) &&\n isNormalObjectDataDescriptor(Object.getOwnPropertyDescriptor(value, key)));\n } catch {\n return false;\n }\n}\n\nfunction hasExactDataKeys(\n value: Record,\n required: readonly string[],\n optional: readonly string[] = [],\n): boolean {\n return hasExactKeys(value, required, optional);\n}\n\nfunction isExactArray(value: unknown): value is unknown[] {\n try {\n if (!Array.isArray(value) || Object.getPrototypeOf(value) !== Array.prototype) return false;\n const keys = Reflect.ownKeys(value);\n const lengthDescriptor = Object.getOwnPropertyDescriptor(value, \"length\");\n if (!lengthDescriptor || !Object.prototype.hasOwnProperty.call(lengthDescriptor, \"value\") ||\n typeof lengthDescriptor.value !== \"number\" || !Number.isSafeInteger(lengthDescriptor.value) ||\n lengthDescriptor.value < 0 || lengthDescriptor.enumerable !== false ||\n lengthDescriptor.writable !== true || lengthDescriptor.configurable !== false) return false;\n const length = lengthDescriptor.value;\n if (keys.length !== length + 1 || !keys.includes(\"length\")) return false;\n for (let i = 0; i < length; i++) {\n const key = String(i);\n if (!keys.includes(key) ||\n !isNormalObjectDataDescriptor(Object.getOwnPropertyDescriptor(value, key))) return false;\n }\n return keys.every((key) => key === \"length\" ||\n (typeof key === \"string\" && /^(?:0|[1-9]\\d*)$/.test(key) && Number(key) < length));\n } catch {\n return false;\n }\n}\n\nfunction isExactDataArray(value: unknown): value is unknown[] {\n return isExactArray(value);\n}\n\nfunction detachedExactData(\n value: unknown,\n fail: SchemaFailure,\n path: string,\n active: Set

Of the ${ptReadable ? pt.booked : \"unknown\"} Pup Talks: showed / no-show / never marked either way	${ptReadable ? `${pt.showed} / ${pt.noshow} / ${Math.max(0, pt.booked - pt.showed - pt.noshow)}` : \"Unknown\"}
Canceled (not counted above)	${ptReadable ? pt.cancelled : \"Unknown\"}
Show rate	${ptReadable ? `${pt.showed} of ${pt.booked} booked${pt.booked >= 5 ? ` (${pct(pt.showed, pt.booked)})` : \"\"}${Math.max(0, pt.booked - pt.showed - pt.noshow) > 0 && pt.showed + pt.noshow >= 5 ? `; of the ${pt.showed + pt.noshow} actually marked, ${pct(pt.showed, pt.showed + pt.noshow)}` : \"\"}` : \"Unknown\"}
Free Training Day booked / showed	${ftdReadable ? `${ftd.booked} / ${ftd.showed}${ftd.booked === 0 ? \" (none scheduled this week)\" : \"\"}` : \"Unknown\"}
Meta connection error	${esc(metaErr)}

Stage	People
${esc(STATUS_LABEL[s.k])}	${s.n}
Total in a sequence	${sum}

Segment	Count	Share	What can be done
Has an email	${c.emailable}	${pct(c.emailable, d.total)}	Address inventory only; not permission to release.
Email + consent snapshot clear	${c.releaseReady ?? 0}	${pct(c.releaseReady ?? 0, d.total)}	The only rows allowed into the dry-run batch plan.
Email, consent unknown	${c.consentUnknown ?? c.emailable}	${pct(c.consentUnknown ?? c.emailable, d.total)}	Held until each full contact DND snapshot is read.
Email blocked / DND	${c.emailBlocked ?? 0}	${pct(c.emailBlocked ?? 0, d.total)}	Excluded from the release.
Phone only	${c.phoneOnly}	${pct(c.phoneOnly, d.total)}	SMS — held until numbers are validated. Stale numbers get a business flagged by carriers.
Neither	${c.unreachable}	${pct(c.unreachable, d.total)}	Nothing by email or text. Reachable only inside Messenger, within Meta's window.
Excluded	${c.excluded}	${pct(c.excluded, d.total)}	Already customers, already on a path, flagged spam, or duplicates.

Campaign	Spent	Conversations	Cost each
Kims New Except4Ads#2	$180.64	47	$3.84
APRIL 10th Fresh February Leads - Copy	$170.89	44	$3.88
Email CSV AI Campaign	$116.49	22	$5.30
Training Tips-Messenger Leads-6/26	$86.96	14	$6.21
Free Training Day Website 6/19	$0.00	0	off
Total	$554.98	127	$4.37

Measure	This week	How it is worked out
Cost per click	$2.05	$164.00 divided by 80 clicks
Cost per conversion	$41.00	$164.00 divided by 4 conversions
Click through rate	8.25%	80 clicks divided by 970 impressions
Your share of available searches	32%	Google's figure, up from 29%
Rover's share of the same searches	24%	Google's figure, up from 22%

Channel	Messages in	Notes
Facebook	538	72% of everything that came in
Phone	71	120 calls in total, 24 unanswered
Text	71
Instagram	46
Email	4

Figure	Value	Source and method
Facebook spend	$554.98	Ads Manager, account 938090411743620, 31 Jul to 5 Aug, sum of the four live campaigns
Facebook conversations	127	Same view, sum of the Results column
Facebook cost per conversation	$4.37	554.98 divided by 127
Facebook consistency check	4 of 4	Each campaign's spend divided by its results matches Meta's own cost per result to the cent
Google spend, clicks, impressions, conversions	$164, 80, 970, 4	Google Ads overview, account 942-544-7945, 31 Jul to 6 Aug
New contacts, this week and last	175 and 197	CRM contact search on date added, converted to New York time before bucketing, two independent pulls agreed
Appointments	55 and 64	All 29 calendars queried one at a time, 197 raw events, bucketed on start time
Messages in and out	748 and 1,143	660 conversations pulled in full, 15,488 messages, system audit entries excluded
Calls	120, 96 answered	Call type messages, answered means completed
Opportunities won, all time	0	All 5,768 opportunities paginated: 5,594 open, 174 lost, 0 won, 0 abandoned. This is the pipeline view only, not a statement about money received
Payment records in the CRM	232 and 195	Transactions and orders. Three transactions fall inside this week, which is being checked before any return figure is quoted
Contacts with no source, 31 Jul to 5 Aug	120 of 149	Source field on each new contact record

Where the money went	Amount	How this page gets it
Facebook and Instagram3 August to 9 August 2026	$676.94	Read straight from the ad platform every time your card page loads. Read three times today, at 3:06 pm, 3:15 pm and 3:16 pm, and it said the same figure each time.
Google31 July to 6 August 2026	$164.00	Typed by hand. This is the figure in the message sent to you on 7 August. Google puts its own numbers behind a developer token, which Google quotes at about five business days. Google joins this page the same way Facebook has once that token lands, and until then every Google figure you see anywhere is one a person typed.

In the seven days 3 August to 9 August	Count
New people in your CRM	168
Of those, arrived through Facebook or Instagram	139
New cards on your Initial Lead Pipeline	166
Pup Talk appointments on your calendar	20
Of those, showed up	15
Cards that moved into your Customer column	2

Program price on the record	Records	Value
$3,295.00	39	$128,505.00
$2,395.00	11	$26,345.00
$3,795.00	3	$11,385.00
All valued records	53	$166,235.00

What happens to it	Payments	Value
Places itself. One booking open, so the money goes straight on it.	15	$7,880.00
Waits for one of your team to pick. More than one booking open.	0	$0.00
Booking already carries a value, so it is left exactly as it is.	15	$8,237.00
Stays where it is, and it is two separate causes. 3 worth $480.00 carry no name on the record. 3 worth $967.00 name a real customer whose booking sits on another board.	6	$1,447.00
All completed payments	36	$17,564.00

Read from the system itself at 3:12 pm today	Reading
Practice mode	On
Messages to real customers, all time	0
Records it is tracking	1
Practice messages produced	5
Version, and its last pass	1.7.1, 3:11 pm

Program price on the record	Records	Value
$3,295	39	$128,505.00
$2,395	11	$26,345.00
$3,795	3	$11,385.00
All valued records	53	$166,235.00

What happens to it	Payments	Value
Places itself. One booking open, so the money goes straight on it.	15	$7,880.00
Needs one of your team to pick. More than one booking open.	0	$0.00
Already has a value on the booking, so it is left alone.	15	$8,237.00
Cannot be placed, and it is two different problems. Three arrived against a record with no name on it at all. The other three name a real customer who has no card in your Customer column to put the money on.	6	$1,447.00
All completed payments	36	$17,564.00

Route	Payments	What it carries
Invoice raised in the CRM, paid by card	56	Arrives already attached to the customer. This is most of your real revenue.
Order form and manual charges	12	Same, attached to the customer.
Counter sale in Square with no name taken	8	Files against one nameless record. Nothing can ever place these.

What it finds	What it does
One open booking	Writes the amount on. No person involved.
More than one open booking	Puts it on an exception list for your team to pick. It never guesses.
No name on the payment	Reported separately as unplaceable. Never guessed at.
Booking already has a price on it	Left exactly as it is. It never overwrites anybody's number.

Outcome	Payments	Value
Places itself. One booking open.	15	$7,880.00
Goes to the exception list for your team to pick.	0	$0.00
Booking already priced, so left alone.	15	$8,237.00
Cannot be placed, reported separately.	6	$1,447.00
All completed payments	36	$17,564.00

Task	Who	How often
Take a name at the counter when somebody pays without one.	Front desk	Only fixes future payments, not past ones. Eight so far have no name.
Pick the right booking when a customer has more than one open.	Whoever you nominate	Zero times today. The list is empty.
Moving cards into Customer	Nobody	Already automated. Noted, and thank you for the correction.
Anything else	Nobody	The rest is automatic.

${esc(ch.name)}

Where your leads come from, and what goes back

Overall status

What this page deliberately does not claim

Did the ad leads actually land?

Did the ad leads actually land?

Did the ad leads actually land?

Some numbers could not be read

What last week's report said

What last week's report said

The Dogs Spot, the week in numbers

What happened, in words DRAFT until Amir reviews

New inquiries, last eight weeks

Where this week's inquiries came from

Why there is no revenue figure

Appendix, the fine print

This week's raw counts

How every number is computed

Nurture path registry

Holiday deposits

Holiday deposits

Holiday deposits

Holiday deposits

The Dogs Spot

Waiting on you

From first contact to paying customer

Is everything working?

Where the last 7 days of inquiries came from

Which ads they answered

New inquiries, week by week

What the advertising cost

What we have been doing

One thing worth fixing in the CRM

The follow-up system, in detail

What needs doing today

The Dogs Spot, Nurture Control Panel

Right now

Where those people are

Stop everything

${d.journalTotal <= entriesShown && groups.length <= RECENT_ROWS ? \"Everything it has done so far\" : \"What it has been doing\"}

Something went wrong in the last 24 hours

The dormant list — what is actually in it

Who can actually be contacted

How old it really is

The release plan

Nurture path registry

The Dogs Spot

Waiting on you

From first contact to paying customer

Is everything working?

Where the last 7 days of inquiries came from

Which ads they answered

New inquiries, week by week

What the advertising cost

What we have been doing

One thing worth fixing in the CRM

The follow-up system, in detail

The Dogs Spot, week of 31 July to 6 August 2026

The thing worth two minutes

Facebook

Where the money went

Google

Your CRM

Where the 175 came from

The 175, since you asked what it counts

The gap between what the ads claim and what your CRM received

Appendix, every number and where it came from

What you spent, and what came back

1. What you spent, and what it brought

What your Square money is doing

What your bookings carry today

2. Where your people came from

3. What happened to those people

4. What your follow up system is doing

Your review pipeline, on one page for the first time

Where your money is, and what is missing

The money Square has sent across

The gap, in one sentence

What your bookings currently carry

What happens the moment the amount gets written

Diff · v1234