[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_690":691,"_692":693},"routes/_app.x.$handle.$name",{"_99":98,"_32":44,"_108":89,"_27":109,"_13":14,"_110":-5,"_11":111,"_112":113,"_114":115,"_116":117,"_118":119,"_20":-5,"_120":-5,"_121":-5,"_122":25,"_123":124,"_125":58,"_126":-5,"_127":-5,"_128":129},"routes/_app.x.$handle.$name.branch.$branch.version.$version.diff",{"_11":12,"_13":14,"_15":16,"_17":-5,"_18":-5},"project",{"_42":43,"_32":44,"_37":45,"_46":-5,"_47":25,"_48":49,"_50":49,"_51":52,"_53":-5,"_18":54,"_55":56,"_57":58,"_59":-5,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":68,"_69":70,"_71":-5,"_72":73,"_74":73,"_75":76,"_77":76,"_78":76,"_79":73,"_80":73,"_81":82,"_83":84,"_85":86,"_87":25},"version",693,"changes",[19],"aiChatInfo","userId",{"_20":21,"_22":23,"_24":25,"_26":25,"_27":28,"_29":28},"file",{"_30":31,"_32":28,"_33":20,"_34":36,"_37":38,"_39":14,"_40":41,"_24":25},"previous",{"_30":31,"_32":28,"_33":20,"_34":35},"deleted",false,"deletedHere","path","NOTES-v1.4.md","latestPath","fileId","7fc16eb4-8e83-11f1-bea8-1607ee4eb77e","name","fileType","content","# 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","# 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","createdAt",["D",1786388112214],"branchVersion","branchId","551774fb-a850-4c9d-94a1-d3509ddcf1b0","id","1bfa6e81-74e1-4c6c-ab32-118304a4ffff","dogsspot_puppy_path",["D",1785429259053],"deletedAt","legacyEnvVars","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",true,"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",{"_99":98,"_107":103},"org",{"_99":98,"_100":101,"_102":103,"_18":54,"_104":105,"_106":25},"branch",{"_13":88,"_32":89,"_42":41,"_90":43,"_91":-5,"_92":-5,"_93":-5,"_94":-5,"_95":-5,"_96":44,"_97":98},"isOwned",1233,"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",{"_42":43,"_32":44,"_37":685,"_46":-5,"_47":25,"_48":49,"_50":49,"_51":52,"_53":-5,"_18":54,"_55":56,"_57":58,"_59":-5,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":68,"_69":686,"_71":-5,"_72":73,"_74":73,"_75":76,"_77":76,"_78":76,"_79":73,"_80":73,"_81":687,"_83":688,"_85":689,"_87":25},"tree",[512,513,514,515,516,517,518,519,520,521,522,523,524,525,526,527,528,529,530,531,532,533,534,535,536,537,538,539,540,541,542,543,544,545,546,547,548,549,550,551,552,553,554],"files",[512,513,514,515,516,517,518,519,520,521,522,523,524,525,526,527,528,529,530,531,532,533,534,535,536,537,538,539,540,541,542,543,544,545,546,547,548,549,550,551,552,553,554],"counts",{"_502":62,"_503":198,"_504":62,"_505":506,"_507":508},"contents",[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],"upstreamProject","upstreamBranch","emptyEnvVars","flags",[],"hasHttpFiles","grants","orgs","customDomains",{},{"_42":499,"_32":28,"_30":31,"_176":-5,"_40":41,"_39":14,"_178":25,"_37":500,"_13":444,"_33":20,"_34":36,"_24":25,"_183":-5,"_27":501},{"_42":492,"_32":493,"_30":494,"_176":-5,"_40":41,"_39":495,"_178":58,"_37":496,"_13":62,"_33":20,"_34":497,"_24":25,"_183":-5,"_27":498},{"_42":484,"_32":485,"_30":486,"_176":-5,"_40":41,"_39":487,"_178":25,"_37":488,"_13":489,"_33":20,"_34":490,"_24":25,"_183":-5,"_27":491},{"_42":477,"_32":478,"_30":479,"_176":-5,"_40":41,"_39":480,"_178":25,"_37":481,"_13":274,"_33":20,"_34":482,"_24":25,"_183":-5,"_27":483},{"_42":469,"_32":470,"_30":471,"_176":-5,"_40":41,"_39":472,"_178":25,"_37":473,"_13":474,"_33":20,"_34":475,"_24":25,"_183":-5,"_27":476},{"_42":462,"_32":463,"_30":464,"_176":-5,"_40":41,"_39":465,"_178":25,"_37":466,"_13":290,"_33":20,"_34":467,"_24":25,"_183":-5,"_27":468},{"_42":455,"_32":456,"_30":457,"_176":-5,"_40":41,"_39":458,"_178":25,"_37":459,"_13":207,"_33":20,"_34":460,"_24":25,"_183":-5,"_27":461},{"_42":447,"_32":448,"_30":449,"_176":-5,"_40":41,"_39":450,"_178":25,"_37":451,"_13":452,"_33":20,"_34":453,"_24":25,"_183":-5,"_27":454},{"_42":439,"_32":440,"_30":441,"_176":-5,"_40":41,"_39":442,"_178":25,"_37":443,"_13":444,"_33":20,"_34":445,"_24":25,"_183":-5,"_27":446},{"_42":432,"_32":433,"_30":434,"_176":-5,"_40":41,"_39":435,"_178":25,"_37":436,"_13":298,"_33":20,"_34":437,"_24":25,"_183":-5,"_27":438},{"_42":424,"_32":425,"_30":426,"_176":-5,"_40":41,"_39":427,"_178":25,"_37":428,"_13":429,"_33":20,"_34":430,"_24":25,"_183":-5,"_27":431},{"_42":416,"_32":417,"_30":418,"_176":-5,"_40":41,"_39":419,"_178":25,"_37":420,"_13":421,"_33":20,"_34":422,"_24":25,"_183":-5,"_27":423},{"_42":408,"_32":409,"_30":410,"_176":-5,"_40":41,"_39":411,"_178":25,"_37":412,"_13":413,"_33":20,"_34":414,"_24":25,"_183":-5,"_27":415},{"_42":400,"_32":401,"_30":402,"_176":-5,"_40":41,"_39":403,"_178":25,"_37":404,"_13":405,"_33":20,"_34":406,"_24":25,"_183":-5,"_27":407},{"_42":392,"_32":393,"_30":394,"_176":-5,"_40":41,"_39":395,"_178":25,"_37":396,"_13":397,"_33":20,"_34":398,"_24":25,"_183":-5,"_27":399},{"_42":384,"_32":385,"_30":386,"_176":-5,"_40":41,"_39":387,"_178":25,"_37":388,"_13":389,"_33":20,"_34":390,"_24":25,"_183":-5,"_27":391},{"_42":376,"_32":377,"_30":378,"_176":-5,"_40":41,"_39":379,"_178":25,"_37":380,"_13":381,"_33":20,"_34":382,"_24":25,"_183":-5,"_27":383},{"_42":368,"_32":369,"_30":370,"_176":-5,"_40":41,"_39":371,"_178":25,"_37":372,"_13":373,"_33":20,"_34":374,"_24":25,"_183":-5,"_27":375},{"_42":360,"_32":361,"_30":362,"_176":-5,"_40":41,"_39":363,"_178":25,"_37":364,"_13":365,"_33":20,"_34":366,"_24":25,"_183":-5,"_27":367},{"_42":353,"_32":354,"_30":355,"_176":-5,"_40":41,"_39":356,"_178":25,"_37":357,"_13":198,"_33":199,"_34":358,"_24":25,"_183":-5,"_27":359},{"_42":346,"_32":347,"_30":56,"_176":-5,"_40":41,"_39":348,"_178":25,"_37":349,"_13":350,"_33":199,"_34":351,"_24":25,"_183":-5,"_27":352},{"_42":339,"_32":340,"_30":341,"_176":-5,"_40":41,"_39":342,"_178":58,"_37":343,"_13":237,"_33":181,"_34":344,"_24":25,"_183":-5,"_27":345},{"_42":332,"_32":333,"_30":334,"_176":-5,"_40":41,"_39":335,"_178":58,"_37":336,"_13":62,"_33":181,"_34":337,"_24":25,"_183":-5,"_27":338},{"_42":324,"_32":325,"_30":326,"_176":-5,"_40":41,"_39":327,"_178":25,"_37":328,"_13":329,"_33":199,"_34":330,"_24":25,"_183":-5,"_27":331},{"_42":316,"_32":317,"_30":318,"_176":-5,"_40":41,"_39":319,"_178":25,"_37":320,"_13":321,"_33":181,"_34":322,"_24":25,"_183":-5,"_27":323},{"_42":308,"_32":309,"_30":310,"_176":-5,"_40":41,"_39":311,"_178":58,"_37":312,"_13":313,"_33":275,"_34":314,"_24":25,"_183":-5,"_27":315},{"_42":301,"_32":302,"_30":303,"_176":-5,"_40":41,"_39":304,"_178":25,"_37":305,"_13":196,"_33":199,"_34":306,"_24":25,"_183":-5,"_27":307},{"_42":293,"_32":294,"_30":295,"_176":-5,"_40":41,"_39":296,"_178":25,"_37":297,"_13":298,"_33":181,"_34":299,"_24":25,"_183":-5,"_27":300},{"_42":285,"_32":286,"_30":287,"_176":-5,"_40":41,"_39":288,"_178":25,"_37":289,"_13":290,"_33":181,"_34":291,"_24":25,"_183":-5,"_27":292},{"_42":278,"_32":279,"_30":280,"_176":-5,"_40":41,"_39":281,"_178":58,"_37":282,"_13":245,"_33":181,"_34":283,"_24":25,"_183":-5,"_27":284},{"_42":269,"_32":270,"_30":271,"_176":-5,"_40":41,"_39":272,"_178":25,"_37":273,"_13":274,"_33":275,"_34":276,"_24":25,"_183":-5,"_27":277},{"_42":262,"_32":263,"_30":264,"_176":-5,"_40":41,"_39":265,"_178":25,"_37":266,"_13":198,"_33":181,"_34":267,"_24":25,"_183":-5,"_27":268},{"_42":255,"_32":256,"_30":257,"_176":-5,"_40":41,"_39":258,"_178":25,"_37":259,"_13":237,"_33":199,"_34":260,"_24":25,"_183":-5,"_27":261},{"_42":248,"_32":249,"_30":250,"_176":-5,"_40":41,"_39":251,"_178":25,"_37":252,"_13":62,"_33":181,"_34":253,"_24":25,"_183":-5,"_27":254},{"_42":240,"_32":241,"_30":242,"_176":-5,"_40":41,"_39":243,"_178":25,"_37":244,"_13":245,"_33":181,"_34":246,"_24":25,"_183":-5,"_27":247},{"_42":232,"_32":233,"_30":234,"_176":-5,"_40":41,"_39":235,"_178":25,"_37":236,"_13":237,"_33":181,"_34":238,"_24":25,"_183":-5,"_27":239},{"_42":225,"_32":226,"_30":227,"_176":-5,"_40":41,"_39":228,"_178":25,"_37":229,"_13":62,"_33":181,"_34":230,"_24":25,"_183":-5,"_27":231},{"_42":218,"_32":219,"_30":220,"_176":-5,"_40":41,"_39":221,"_178":58,"_37":222,"_13":62,"_33":181,"_34":223,"_24":25,"_183":-5,"_27":224},{"_42":210,"_32":211,"_30":212,"_176":-5,"_40":41,"_39":213,"_178":58,"_37":214,"_13":215,"_33":181,"_34":216,"_24":25,"_183":-5,"_27":217},{"_42":202,"_32":203,"_30":204,"_176":-5,"_40":41,"_39":205,"_178":25,"_37":206,"_13":207,"_33":199,"_34":208,"_24":25,"_183":-5,"_27":209},{"_42":193,"_32":194,"_30":195,"_176":-5,"_40":41,"_39":196,"_178":25,"_37":197,"_13":198,"_33":199,"_34":200,"_24":25,"_183":-5,"_27":201},{"_42":185,"_32":186,"_30":187,"_176":-5,"_40":41,"_39":188,"_178":58,"_37":189,"_13":190,"_33":181,"_34":191,"_24":25,"_183":-5,"_27":192},{"_42":173,"_32":174,"_30":175,"_176":-5,"_40":41,"_39":177,"_178":25,"_37":179,"_13":180,"_33":181,"_34":182,"_24":25,"_183":-5,"_27":184},"2d3927ed-c0fe-4b16-b9be-86dab3407f82","worklog.ts","facd3ee8-9028-11f1-8d98-1607ee4eb77e","parentId",692,"latest",["D",1786388057191],36,"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];\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",[174],"c195bcad-6c44-41e3-84ec-3a7d93528aa8","taper-messages.ts","65f1a7b2-900c-11f1-948d-1607ee4eb77e",456,["D",1786285581663],11,"// SLOW TRACK (TAPER) — message copy module. Companion to puppy-messages.ts.\n// Spec is Kim's own, verbatim from her Upwork message 3 Aug 2026, 8:11 PM:\n// \"I'd like something to taper off rather than just drop. Something like a text or email\n// once a week for month then every two weeks for 6 months then every month moving forward.\"\n// Committed shape (confirmed back to her, 8:27 PM): after the 21-day main sequence ends —\n// weekly x4, then fortnightly x13 (~6 months), then monthly indefinitely.\n// HARD RULE, promised to Kim in writing: NO ask attached to any taper message. No booking\n// links, no CTAs, no phone-number pushes — replying to the message itself is the only channel\n// offered. \"The job of that track is that\n// when they finally do need training or boarding, you're the name they already know.\"\n// Same engine rules underneath: reply -> paused for a human; booking -> off the track;\n// STOP -> never contacted again. All enforced engine-side, same as the main sequence.\n\nimport { PHONE_DISPLAY, type MessageTemplate } from \"./puppy-messages.ts\";\n\n// Offsets are hours RELATIVE TO SLOW-TRACK ENTRY (the moment main-8 fires, day 21 absolute).\n// Weekly: rel days 7 / 14 / 21 / 28 = absolute days 28 / 35 / 42 / 49\n// Fortnightly: rel days 42 .. 210 (13 x 14) = absolute days 63 .. 231\n// Monthly: rel day 240 onward, every 30 = absolute day 261 onward, forever\n\nexport const SLOW_WEEKLY: MessageTemplate[] = [\n {\n id: \"slow_w-1\",\n channel: \"email\",\n offsetHours: 168, // rel day 7\n subject: \"The teenage phase is coming (this is normal too)\",\n previewText: \"Somewhere between six and twelve months, trained puppies act untrained. Here's why.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nOne thing I wish more people were warned about: somewhere between six and twelve months, your dog will probably go through a teenage phase. The recall that was working stops working. The chewing comes back. A dog who knew \"sit\" looks at you like they've never heard the word.\n\nThis isn't your training failing, and it isn't the puppy teething back again - that part really does settle, like I said in the early emails. This is adolescence: hormones and a growing brain re-testing every rule, exactly like human teenagers do. Dogs who were doing great at five months often look like a mess at eight, and the owners who don't know it's a phase assume they've done something wrong.\n\nTwo things carry you through it: keep the routines boring and consistent even when they seem pointless, and keep rewarding the behavior you want as if your dog were still tiny. It passes. The dogs who come out of it best are the ones whose people didn't give up on the rules halfway through.\n\n{{STORY:teenage}}\n\nReply anytime - a real person reads these.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_w-2\",\n channel: \"sms\",\n offsetHours: 336, // rel day 14\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim at The Dogs Spot. A tip that saves furniture: rotate your dog's toys - keep most in a closet and swap a few out every couple of days. Old toys become new again, and a dog with something interesting to chew rarely invents their own project. Reply anytime.`,\n },\n {\n id: \"slow_w-3\",\n channel: \"email\",\n offsetHours: 504, // rel day 21\n subject: \"Socialization doesn't stop - it just changes shape\",\n previewText: \"The window closes, but the habit shouldn't.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nWhen your dog was tiny, the job was meeting the world before the socialization window closed. That window does close - but the habit shouldn't. A dog who met the mail carrier calmly at twelve weeks can still decide the mail carrier is suspicious at eight months if the meetings stop.\n\nThe maintenance version is lighter than the puppy version. A different walking route once a week. Ten minutes watching the world go by outside a coffee shop. A calm hello with a steady adult dog now and then. You're just keeping the file open: people, dogs, noises, places, all still no big deal.\n\nThe dogs who stay easy in public are almost never the ones with the most training. They're the ones whose world stayed wide.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_w-4\",\n channel: \"sms\",\n offsetHours: 672, // rel day 28\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. A two-minute recall game that works: someone holds your dog, you walk away looking excited, then call once and celebrate like they won the lottery when they arrive. Dogs repeat what pays.`,\n },\n];\n\nexport const SLOW_FORTNIGHTLY: MessageTemplate[] = [\n {\n id: \"slow_f-1\",\n channel: \"email\",\n offsetHours: 1008, // rel day 42\n subject: \"Teaching your dog that alone is fine\",\n previewText: \"Separation ease is trained, not hoped for.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThe single most underrated skill for a young dog: being alone and being fine about it. It doesn't happen by accident - dogs are social animals, and a dog who is never alone learns that alone is alarming.\n\nBuild it in small doses. Leave for two minutes and come back before any fuss starts, then five, then twenty. Keep departures and returns boring - no big goodbyes, no big reunions. A stuffed chew or a lick mat that only appears when you leave turns your exit into a good sign instead of a bad one.\n\nThe goal isn't a dog who tolerates your absence. It's a dog who hears the keys and thinks \"snack time\", then has a nap.\n\n{{STORY:alone_time}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-2\",\n channel: \"sms\",\n offsetHours: 1344, // rel day 56\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Loose-leash tip: the moment the leash goes tight, stop walking. Move again only when it slackens. Boring, repetitive, and it works better than any gadget - pulling stops paying, so pulling stops. Reply if it stalls.`,\n },\n {\n id: \"slow_f-3\",\n channel: \"email\",\n offsetHours: 1680, // rel day 70\n subject: \"Vet visits without the drama\",\n previewText: \"Five minutes of practice at home changes every appointment for life.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nA dog's opinion of the vet is mostly formed before anything medical ever happens. You can shape it at home, five minutes at a time.\n\nHandle your dog's paws, ears and mouth while they're relaxed - a touch, then a treat, done before they mind. Pop them on a table or a mat, brief and calm, same deal. If you're ever passing your vet's clinic, walk in, let the front desk say hello and hand over a treat, and leave. Visits where nothing happens are what make the real ones manageable.\n\nA dog who's been handled kindly a hundred times at home barely notices an examination. One who's only ever grabbed when something hurts learns the opposite lesson.\n\n{{STORY:vet_visits}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-4\",\n channel: \"sms\",\n offsetHours: 2016, // rel day 84\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim at The Dogs Spot. If your dog goes wild in the evenings - the witching hour is real. It's usually overtiredness, not excess energy. A chew and enforced quiet time settles it faster than another walk. Reply if evenings are still chaos, happy to help.`,\n },\n {\n id: \"slow_f-5\",\n channel: \"email\",\n offsetHours: 2352, // rel day 98\n subject: \"The off switch\",\n previewText: \"The most useful thing a dog can learn isn't a trick.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThe most useful thing your dog can learn isn't a trick - it's an off switch. A dog who can lie on a mat and do nothing while life happens around them gets taken everywhere. A dog who can't gets left at home, which shrinks their world and makes everything harder.\n\nTeach it like anything else. A mat or a bed, a treat for lying on it, then gradually longer stays and gradually more interesting distractions - someone walking past, the doorbell, dinner being eaten. Reward calm, quietly, before they break. Minutes a day, and within a few weeks you have a dog you can take to a restaurant patio.\n\nIt's not glamorous. It changes more about daily life than any other single thing you can train.\n\n{{STORY:settle}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-6\",\n channel: \"sms\",\n offsetHours: 2688, // rel day 112\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Jumping on guests fix: have visitors ignore your dog completely until all four paws are on the floor, then greet warmly. Attention is what they're after. Give it for standing, never for jumping. Consistency from everyone is the whole trick.`,\n },\n {\n id: \"slow_f-7\",\n channel: \"email\",\n offsetHours: 3024, // rel day 126\n subject: \"Dog parks: the honest version\",\n previewText: \"When they help, when they don't, and what to watch.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nDog parks divide opinion, so here's the honest version: they're brilliant for some dogs and genuinely bad for others, and the difference isn't friendliness - it's what happens there.\n\nWatch play, not intentions. Good play has role swaps: chaser becomes chased, wrestler ends up underneath, both dogs keep opting back in. If your dog is always the one being chased, or hiding under benches, or the one doing all the pinning, it isn't play anymore, and every bad visit teaches something you'll later have to untrain.\n\nThe useful test: call your dog out of play now and then, reward, release back. If you can't call them out, the park is training them - just not in the direction you want. A few good dogs beat a big crowd of random ones.\n\n{{STORY:dog_parks}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-8\",\n channel: \"sms\",\n offsetHours: 3360, // rel day 140\n bodyTemplate: `Hi {{FIRST_NAME}}, it's Kim. While I'm thinking about it: feed your dog a few meals in the parked car, engine off, before expecting calm car rides. Cars should predict good things, not just vet trips. Short happy drives to nowhere do the same job. Tell me how it goes, I read these.`,\n },\n {\n id: \"slow_f-9\",\n channel: \"email\",\n offsetHours: 3696, // rel day 154\n subject: \"Boredom looks a lot like bad behavior\",\n previewText: \"Ten minutes of nose work tires a dog more than an hour of fetch.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nMost \"bad behavior\" in young dogs is unemployment. A dog with nothing to do writes their own job description, and it usually involves your baseboards.\n\nThe fix isn't always more exercise - physical exercise builds fitness, and a fitter dog just has more stamina for mischief. Mental work is what actually tires them. Scatter your dog's food in the grass instead of a bowl and let them sniff it out. Hide treats around one room. A snuffle mat, a frozen Kong, a cardboard box with food inside it to be destroyed. Ten minutes of nose work drains more out of a dog than an hour of fetch, because sniffing is thinking.\n\nA tired dog is a good dog, but the right kind of tired is mental. It's also the cheapest training aid there is.\n\n{{STORY:nose_work}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-10\",\n channel: \"sms\",\n offsetHours: 4032, // rel day 168\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Brushing habit worth keeping: one minute after dinner, every day, treat at the end. Daily and brief beats weekly and a wrestle - and you'll spot lumps, ticks and sore spots before they're problems. Reply anytime.`,\n },\n {\n id: \"slow_f-11\",\n channel: \"email\",\n offsetHours: 4368, // rel day 182\n subject: \"Two dogs meeting on leash: what's actually going on\",\n previewText: \"What a tight leash does to friendly dogs, and the walk-along trick.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nA strange thing you'll notice: two perfectly friendly dogs can bristle at each other on leash when the same two would be fine loose. It isn't contrariness. The leash changes the conversation.\n\nDogs read each other sideways - they approach in curves, sniff rears, keep options open. A tight leash forces a head-on approach with no escape route, which in dog language reads as confrontation. The tension travels down the leash too: you tighten up, and your dog decides there must be something to tense about.\n\nWhat helps: keep the leash loose even when it takes nerve, approach in an arc rather than straight on, and if you want two dogs to make friends, walk them side by side in the same direction first and let the sniffing happen on the move. Side by side works. Head-on mostly doesn't.\n\n{{STORY:leash_meetings}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-12\",\n channel: \"sms\",\n offsetHours: 4704, // rel day 196\n bodyTemplate: `Hi {{FIRST_NAME}}, it's Kim again. One that surprises people: use part of your dog's daily ration as training treats instead of adding extras on top. Same calories, more practice, no expanding waistline. The dog doesn't know the difference - it all counts as winning.`,\n },\n {\n id: \"slow_f-13\",\n channel: \"email\",\n offsetHours: 5040, // rel day 210\n subject: \"From here on, about once a month\",\n previewText: \"The rhythm changes, the door stays open.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nQuick housekeeping note rather than advice this time: I've been in your inbox every couple of weeks since your dog was small, and from here I'll drop to about once a month - short, seasonal, still a thirty-second read, I promise.\n\nBy now most of the foundations are in: the world stayed wide, alone is fine, the leash is mostly loose, and the teenage phase either happened or is happening and will pass either way.\n\nIf anything ever comes up in between - a behavior that's new, a question that nags - reply to any of these. A real person reads them, always has.\n\nKim\nThe Dogs Spot`,\n },\n];\n\n// Monthly bank — chosen by the CALENDAR MONTH the send lands in (0 = Jan .. 11 = Dec),\n// so the seasonal ones land in season regardless of when the contact entered the track.\n// This is what was promised to Kim: \"seasonal where it fits: settling a dog over the\n// holidays, heat and paws in July, fireworks.\" offsetHours on these entries is ignored\n// by the scheduler (cadence is every 720h from rel day 240); template chosen by month.\n//\n// v1.7.2, 9 Aug 2026 — two additions she asked for 6 Aug, verbatim: \"water intoxication note +\n// kids back to school in August -> July/Aug puppy nurture\" (handover/UPWORK-THREAD-FULL-9AUG.md,\n// 9:07 PM 6 Aug). Water intoxication is now the closing note in July, alongside the heat and\n// fireworks copy she already signed off (both left untouched). Back-to-school is now August's own\n// note rather than September's: Kim's own phrasing places it \"in August\", and school-starting-back\n// is the bigger routine shock than the algae warning that was previously August's only content, so\n// August moved from SMS to email to give both the room they need — a plain factual change (a\n// channel and a word count), not a change to anything she asked for. The algae warning was not\n// removed; nothing she approved was cut, only added to. NOT changed: September, which still carries\n// its own back-to-school note. The two now sit back-to-back with overlapping subject matter — flagged\n// for Kim/Amir rather than silently rewritten, the same way the phone-number choice above was left\n// for a decision rather than guessed at.\nexport const SLOW_MONTHLY_BANK: MessageTemplate[] = [\n {\n id: \"slow_m-jan\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"January: the quiet month is a training month\",\n previewText: \"Short days, big opportunity.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nJanuary is short walks and dark evenings, which makes it a surprisingly good training month. Five minutes of indoor work a day, a settle on the mat or some paw-and-ear handling practice, carries further than one heroic cold-weather hike a week.\n\nGeorgia winters are mild, but a cold snap still ices a morning path now and then - so a quick paw check after those walks is smart.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-feb\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim at The Dogs Spot. Wet-weather boredom builds mischief - a stuffed Kong from the freezer or dinner scattered in a snuffle mat gets you a calm evening. Mental work counts double in February. Reply anytime.`,\n },\n {\n id: \"slow_m-mar\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Spring: the world wakes up, so does the sniffing\",\n previewText: \"Let the nose have its season.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nEverything smells new in spring, and you'll feel it down the leash. Rather than fight it, give sniffing its own time: pick a stretch of the walk where your dog sets the pace and the route, nose down, no agenda. Sniffing is a dog reading the news, and ten minutes of it settles them more than double the distance at a march.\n\nOne more spring thing: tick season opens now. A quick run of the hands after grassy walks catches them early.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-apr\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Spring reminder, same one every year: chocolate is flat-out dangerous for dogs. If there's been an egg hunt anywhere near your yard, a nose will find what the kids missed, sometimes weeks later. Keep the candy high and the vet's number where you can find it.`,\n },\n {\n id: \"slow_m-may\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Before summer: build the water habit\",\n previewText: \"Warm-weather prep is easier before it's hot.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nA little prep now makes summer easier. Get your dog used to drinking on walks - carry water and offer it before they seem thirsty, so it's routine by the time it matters. If a kiddie pool or the sprinkler might feature, introduce them gently now while they're novelty rather than necessity.\n\nAnd as the winter coat blows out, a few minutes of brushing a day now saves your furniture a month of fur. One thing to know before summer: never shave a double-coated breed to cool them down - that coat insulates against heat as well as cold, and they're worse off without it.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-jun\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim at The Dogs Spot. Summer rule of thumb: put the back of your hand on the pavement for seven seconds. Too hot for your hand, too hot for your dog's paws - walk early or late instead. Any summer questions, just reply.`,\n },\n {\n id: \"slow_m-jul\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"July: heat, paws and fireworks\",\n previewText: \"The two summer hazards, and the one that sneaks up.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nJuly's the month I nag about heat. Dogs don't sweat like we do - they cool by panting, which stops working in a hot car in minutes, even parked in shade with windows cracked. Walks move to early morning or late evening, water goes everywhere you go, and pavement gets the seven-second hand test before your dog's paws touch it.\n\nThe one that sneaks up: fireworks around the Fourth. If your dog is nervous of bangs, plan the evening - walk before dark, close curtains, put on some background noise, and let them den up wherever they choose. Comforting a scared dog doesn't reward fear, whatever the old advice said. Sit with them.\n\nOne more worth knowing: a dog who's been fetching from the lake or biting at the hose for a long stretch can swallow more water than their body can handle, and it comes on fast. Water intoxication is rare, but a dog who's wobbly, bloated, or vomiting after a long swim needs a vet call right away, not a wait-and-see.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-aug\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"August: pond safety, and the house about to get quiet\",\n previewText: \"Two things worth knowing before the month's out.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nTwo August things. Lakes and ponds can grow blue-green algae late in the summer - it's toxic to dogs, sometimes fatal. If the water looks like pea soup or has a scum line, your dog stays out, no exceptions.\n\nThe other one sneaks up on dogs more than people expect: school starting back. It rearranges a dog's whole day at once - the house empties out, walks shift earlier or later, and the kids who were around all summer are suddenly gone for hours. A bit of extra chewing or barking this month is usually just the adjustment talking, not a step backward.\n\nEase it in the same way you'd build alone-time from scratch: short practice absences before the real ones start, something good that only shows up when the house empties, and low-key comings and goings. A few practice runs the week before beats a hard first day.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-sep\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"September: the routine change nobody warns dogs about\",\n previewText: \"Back-to-school hits dogs too.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nSeptember quietly rearranges a dog's whole day: the house empties, walks move, the kids who were constant company vanish for hours. Dogs don't read calendars, so the change lands without warning, and a bit of chewing or barking that starts this month is usually the adjustment talking.\n\nEase it the same way you built alone-time in the first place: short practice absences, something good that only appears when the house empties, and low-key exits. A week of short practice runs saves a month of stress.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-oct\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Halloween heads-up: the doorbell going all evening plus strangers in masks is a lot for most dogs. A chew in a back room with the radio on beats managing the door. And candy, especially sugar-free with xylitol, is dangerous for dogs - keep the bowl high.`,\n },\n {\n id: \"slow_m-nov\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"November: guests, feasts and a dog with opinions\",\n previewText: \"Getting ahead of the holiday chaos.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThe holiday season starts here, and for your dog it mostly means two things: the house fills with people, and the house fills with food at nose height.\n\nThe settle-on-a-mat work comes into its own now - a dog with a place to be, and something to chew there, rides out a busy dinner far better than one loose in the middle of it all. Brief the guests too: no feeding from plates, however charming the eyes. Rich, fatty leftovers are one of the most common reasons dogs see an emergency vet this time of year. The big ones to keep off the floor: onions, grapes and raisins, and any cooked bone.\n\nA walk before guests arrive takes the edge off everything.\n\n{{STORY:holidays}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-dec\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Settling a dog over the holidays\",\n previewText: \"Trees, tinsel, visitors and routine.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nDecember, quickly, because you're busy: keep your dog's routine as boring as you can manage while everything else changes - same meal times, same walks, same bedtime. Dogs take their stability from routine, and a steady dog copes with a chaotic house far better than the other way around.\n\nTree-wise: chocolate decorations are a vet visit waiting to happen, tinsel and ribbon are surgery if swallowed, and a curious tail plus low ornaments ends how you'd expect. Hang anything precious or edible high.\n\nHowever the season goes, thank you for letting me stay in your inbox this year. Reply anytime - a real person reads these, holidays included.\n\nKim\nThe Dogs Spot`,\n },\n];\n\n// ---- scheduler helpers (pure, testable) ---------------------------------------------------------\n\nexport const SLOW_WEEKLY_COUNT = 4;\nexport const SLOW_FORTNIGHTLY_COUNT = 13;\nexport const SLOW_MONTHLY_START_REL_HOURS = 5760; // rel day 240 (abs day 261)\nexport const SLOW_MONTHLY_INTERVAL_HOURS = 720; // 30 days\n\n// Given how many slow-track messages have already been sent to a contact, return the next\n// one: its template (or, for monthly, the bank + a note to pick by landing month) and its\n// offsetHours relative to slow-track entry. Returns null never — the track is indefinite.\nexport function nextSlowTouch(sentCount: number): {\n phase: \"weekly\" | \"fortnightly\" | \"monthly\";\n template: MessageTemplate | null; // null for monthly — engine picks by landing month\n offsetHours: number;\n} {\n if (sentCount < SLOW_WEEKLY_COUNT) {\n return { phase: \"weekly\", template: SLOW_WEEKLY[sentCount], offsetHours: 168 * (sentCount + 1) };\n }\n const f = sentCount - SLOW_WEEKLY_COUNT;\n if (f < SLOW_FORTNIGHTLY_COUNT) {\n return { phase: \"fortnightly\", template: SLOW_FORTNIGHTLY[f], offsetHours: 672 + 336 * (f + 1) };\n }\n const m = sentCount - SLOW_WEEKLY_COUNT - SLOW_FORTNIGHTLY_COUNT;\n return {\n phase: \"monthly\",\n template: null,\n offsetHours: SLOW_MONTHLY_START_REL_HOURS + SLOW_MONTHLY_INTERVAL_HOURS * m,\n };\n}\n\n// Monthly template for a given send date (calendar-month keyed, so seasonal copy lands in season).\nexport function monthlyTemplateFor(sendDate: Date): MessageTemplate {\n return SLOW_MONTHLY_BANK[sendDate.getMonth()];\n}\n\n// v1.7.1 — same, but never the same message twice in a row. The 30-day grid drifts through the\n// calendar, so two consecutive sends can land in one calendar month (the 1st and the 31st):\n// without this the identical email goes out twice, and December's \"thank you for letting me stay\n// in your inbox this year\" twice in a month reads as a broken robot. If this month's template was\n// the last thing sent, serve next month's instead.\nexport function monthlyTemplateAvoidingRepeat(sendDate: Date, lastSentId: string | null | undefined): MessageTemplate {\n const tpl = SLOW_MONTHLY_BANK[sendDate.getMonth()];\n return lastSentId && tpl.id === lastSentId ? SLOW_MONTHLY_BANK[(sendDate.getMonth() + 1) % 12] : tpl;\n}\n",[186],"36659075-120a-4f67-995b-203ed981f4fa","run.ts","be37b584-8e76-11f1-b9e0-1607ee4eb77e",14,["D",1785678975976],1,"http","// CHECK NOW — manual trigger for the nurture engine. Built 2 Aug 2026.\n//\n// WHY\n// main.ts is a val.town `interval` file. Its schedule is set in val.town's UI and cannot be read or\n// triggered through the API, which left two real problems: (1) nothing could be verified end-to-end\n// on demand — including the kill switch, which is the one control the client must be able to trust;\n// (2) if the schedule ever stalls there is no way to make the system catch up without a human\n// opening val.town. This file closes both. It imports the same cron() the scheduler calls, so there\n// is exactly one code path — a manual run is not a different run.\n//\n// SAFETY\n// Same admin key as the control panel. Every guard inside cron() still applies in full: the kill\n// switch is checked first, TEST_MODE still defaults on, the run lock still prevents overlap with a\n// scheduled tick, and the send ceilings are unchanged. This adds a trigger, never a bypass.\n//\n// ?k= run once, return the run report as JSON\n// ?k=&dry=1 report what the engine WOULD do without invoking it — resolves nothing, just\n// confirms this endpoint is wired and the key is right\n\nimport cron from \"./main.ts\";\n\n// ---- auth ------------------------------------------------------------------------------------\n// v2 (2 Aug, after the adversarial pass): the key is NOT in this file. val.town vals are PUBLIC —\n// proved by fetching this very source with no token — so a literal key here was readable by anyone\n// who found the val, which meant anyone could read Kim's data, stop her system, or trigger a run.\n// Only the SHA-256 digest lives in source now. The digest is useless to a reader and sufficient for\n// a comparison, so publishing the code no longer publishes the secret.\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\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 override = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\");\n const expected = override || KEY_SHA256;\n const got = await sha256Hex(k);\n // Constant-time over equal-length hex digests.\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\n\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n if (!(await authorised(url.searchParams.get(\"k\") || \"\"))) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n if (url.searchParams.get(\"dry\") === \"1\") {\n return new Response(JSON.stringify({ wired: true, note: \"endpoint live; pass without &dry=1 to actually run\" }, null, 2), {\n headers: { \"content-type\": \"application/json\" },\n });\n }\n const startedAt = new Date().toISOString();\n try {\n const report = await cron();\n return new Response(JSON.stringify({ triggeredAt: startedAt, report }, null, 2), {\n headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" },\n });\n } catch (e) {\n return new Response(JSON.stringify({ triggeredAt: startedAt, error: String(e).slice(0, 900) }, null, 2), {\n status: 500,\n headers: { \"content-type\": \"application/json\" },\n });\n }\n}\n",[194],"3c740e89-e2eb-4d73-8ff3-0290beaf3991","report.ts","7a35076a-901f-11f1-8a2e-1607ee4eb77e",680,["D",1786387503928],13,"// FRIDAY REPORT, HTTP endpoint. Renders the week's numbers live from the CRM, saves a Friday\n// snapshot so next week can reference this week honestly. v1.0, 4 Aug 2026.\n//\n// ROUTES ?k= the report page (most recent complete Fri-Fri week)\n// ?k=&save=1 snapshot this week's numbers + draft commentary\n// (auto-save: first ADMIN view on a Friday ET saves the snapshot if missing)\n//\n// DATA every number from the GHL API at render time, computed in report-logic.ts, formulas\n// printed in the appendix. Ad platform numbers appear the day META_TOKEN / GADS creds\n// exist in the val env; until then those cells say \"not tracked yet\" and nothing is\n// estimated. Reconciliation (platform-claimed leads vs contacts that actually landed)\n// switches on the same day.\ndeclare const Deno: { env: { get(k: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\nimport {\n reportWindows, inWindow, countContacts, sourceBreakdown, channelBreakdown, attributionCoverage,\n facebookLanded, countEvents, wonOpps,\n weeklyBuckets, pct, deltaWord, money, draftCommentary, FORMULAS, type ContactLite, type EventLite, type OppLite,\n} from \"./report-logic.ts\";\n\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst PUP_TALK_CAL = \"qHuYJ0NEqzibnoqf5Cw3\";\nconst FTD_CALS = [\"K24xHYRExFJDEGpgSNVB\", \"bLn88LGOYYOZ3NySO1EZ\"]; // Free Dog Training Day + Free Training Day\n// v1.0.1 (review fix #3) — computed PER REQUEST, not at module load: val.town keeps modules\n// warm across the DST changeover, and a stale offset shifts every window an hour and can\n// double-save Thursday's snapshot under Friday's key.\nfunction etOffsetMin(atMs: number): number {\n const fmt = new Intl.DateTimeFormat(\"en-US\", { timeZone: \"America/New_York\", timeZoneName: \"shortOffset\" });\n const part = fmt.formatToParts(new Date(atMs)).find((p) => p.type === \"timeZoneName\")?.value ?? \"GMT-4\";\n const m = part.match(/GMT([+-]\\d+)/);\n return m ? Number(m[1]) * 60 : -240;\n}\n\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\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}\nasync function isAdmin(k: string) {\n return (await sha256Hex(k)) === (Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\") || KEY_SHA256);\n}\nasync function isViewer(k: string) {\n // v1.0.1 (review fix #4) — derived from the GHL token (a real secret held in env/private\n // blob), NOT from the admin digest that sits in this public source. Rotating the CRM token\n // rotates the view links; documented on Amir's list.\n const tok = await token();\n if (!tok) return false;\n return k === \"tds_view_\" + (await sha256Hex(tok + \":view\")).slice(0, 32);\n}\n\nasync function blobMod() { return (await import(\"https://esm.town/v/std/blob\")).blob; }\nasync function token(): Promise {\n const env = Deno.env.get(\"GHL_TOKEN\");\n if (env) return env;\n try { const blob = await blobMod(); return (await blob.getJSON(\"puppy_config\"))?.ghlToken; } catch { return undefined; }\n}\n\nasync function j(path: string, ver: string) {\n const tok = await token();\n const r = await fetch(`${GHL}${path}`, {\n headers: { Authorization: `Bearer ${tok}`, Version: ver, \"User-Agent\": \"curl/8.5.0\" },\n signal: AbortSignal.timeout(25_000),\n });\n if (!r.ok) throw new Error(`GHL ${path.split(\"?\")[0]} -> HTTP ${r.status}`);\n return r.json();\n}\n\n// Contacts newest-first, paginated until older than `floorMs` (bounded pages so a bad response\n// cannot loop forever). Failure THROWS, the section renders the error loudly, never a zero.\nasync function contactsSince(floorMs: number, errorsOut: string[]): Promise {\n const out: ContactLite[] = [];\n let startAfterId: string | undefined;\n let startAfter: number | undefined;\n let reachedFloor = false;\n for (let page = 0; page < 40; page++) {\n const q = new URLSearchParams({ locationId: LOC, limit: \"100\" });\n if (startAfterId && startAfter) { q.set(\"startAfterId\", startAfterId); q.set(\"startAfter\", String(startAfter)); }\n const d = await j(`/contacts/?${q}`, \"2021-07-28\");\n const cs = d?.contacts ?? [];\n if (!cs.length) break;\n for (const c of cs) {\n // R32: the CRM's own `source` column is null on 78% of contacts and has never once carried\n // \"facebook\". The arrival record is what dashboard.ts has read correctly since 4 Aug.\n const a = (Array.isArray(c.attributions) ? c.attributions : []).find((x: any) => x?.isFirst) ?? c.attributions?.[0] ?? null;\n out.push({\n dateAdded: c.dateAdded, source: c.source ?? null, tags: c.tags ?? [],\n attribution: a ? { medium: a.medium ?? a.utmSessionSource ?? null, campaign: a.utmCampaign ?? null } : null,\n });\n }\n const oldest = Date.parse(cs[cs.length - 1]?.dateAdded ?? \"\");\n const meta = d?.meta ?? {};\n startAfterId = meta.startAfterId; startAfter = meta.startAfter;\n if (Number.isFinite(oldest) && oldest < floorMs) { reachedFloor = true; break; }\n if (!startAfterId) { reachedFloor = true; break; }\n }\n if (!reachedFloor) errorsOut.push(\"Contact history hit the page cap before covering eight weeks; the oldest chart bars may undercount\");\n return out;\n}\n\nasync function eventsFor(calId: string, startMs: number, endMs: number): Promise {\n const d = await j(`/calendars/events?locationId=${LOC}&calendarId=${calId}&startTime=${startMs}&endTime=${endMs}`, \"2021-04-15\");\n return (d?.events ?? []).map((e: any) => ({\n startTime: typeof e.startTime === \"number\" ? e.startTime : Date.parse(e.startTime),\n appointmentStatus: e.appointmentStatus ?? e.appoinmentStatus ?? \"unknown\",\n calendarId: calId,\n }));\n}\n\n// v1.0.1 (review fix #1) — wins are counted by lastStageChangeAt but the search endpoint\n// sorts by createdAt, so a createdAt-floor walk silently drops long-cycle wins (an aged lead\n// created in June, won in August). Wins are a small population: scan them ALL via status=won,\n// no floor break. errorsOut collects a loud note if the page cap is ever hit (fix #8).\n// v1.0.2, PROVEN LIVE 4 Aug 2026: all 5,695 opportunities in this account carry status \"open\".\n// Nobody uses the won/lost flags, so a status=won scan returns zero forever and this report would\n// have printed \"0 closed deals\" every week for the rest of time. The real signal is the pipeline\n// STAGE (Customer / Won-Paid), which the engine's own exit rules already read. Also proven: every\n// such record has monetaryValue 0, so the CRM holds no deal values; the report counts PEOPLE\n// reaching Customer and says plainly that revenue is not recorded.\nconst STAGE_CUSTOMER = \"fd821b4e-bbe6-44de-b754-fa80e4823616\";\nconst STAGE_WON_PAID = \"ae173310-f8b1-4399-acb7-ef1fc03d3697\";\n// FIXED 9 Aug 2026. This used to walk the WHOLE location, page=1..20 at limit=100, and filter\n// down to the two stages afterwards. That reads 2,000 of the roughly 5,800 opportunities this\n// location holds, so it silently missed 1,453 of 1,516 Customer records and 42 of the 53 that\n// carry a dollar value, worth $130,890 of $166,235. It printed \"2 new customers\" for a week that\n// really had 3. The dashboard never had this bug because it queries per stage; this now does the\n// same, which also cuts the request count from 20 pages of everything to ~16 pages of the only\n// two stages that matter.\nasync function wonOppsAll(errorsOut: string[]): Promise {\n const out: OppLite[] = [];\n const pageOf = (stage: string, p: number) =>\n j(`/opportunities/search?location_id=${LOC}&limit=100&page=${p}&pipeline_stage_id=${stage}`, \"2021-07-28\");\n for (const stage of [STAGE_CUSTOMER, STAGE_WON_PAID]) {\n const first = await pageOf(stage, 1);\n const total = Number(first?.meta?.total ?? 0);\n const wanted = Math.ceil(total / 100) || 1;\n const pages = Math.min(wanted, 40); // 4,000 per stage: a backstop, not a working limit\n if (wanted > 40) errorsOut.push(`Customer list hit the page cap on one stage; totals may be partial (${total} records)`);\n const rest = pages > 1\n ? await Promise.all(Array.from({ length: pages - 1 }, (_, i) => pageOf(stage, i + 2)))\n : [];\n for (const d of [first, ...rest]) {\n for (const o of (d?.opportunities ?? [])) {\n out.push({ createdAt: o.createdAt, status: \"won\", monetaryValue: Number(o.monetaryValue) || 0, lastStageChangeAt: o.lastStageChangeAt ?? null });\n }\n }\n }\n return out;\n}\n\n// Ad platforms, honest stubs. The day the tokens exist, these return numbers; until then null.\nasync function metaSpend(w: { startMs: number; endMs: number }, tzMin: number): Promise<{ spend: number; convs: number } | null> {\n const tok = Deno.env.get(\"META_TOKEN\"), act = Deno.env.get(\"META_AD_ACCOUNT\");\n if (!tok || !act) return null;\n // v1.0.1 (fixes #5, #9) — dates shifted into ET before slicing (UTC slice rolled the window\n // one day long); token in the Authorization header, never the URL; errors sanitized so a\n // network failure can never echo credentials into the page.\n const day = (ms: number) => new Date(ms + tzMin * 60_000).toISOString().slice(0, 10);\n const since = day(w.startMs), until = day(w.endMs - 86_400_000);\n let r: Response;\n try {\n r = await fetch(`https://graph.facebook.com/v21.0/${act}/insights?fields=spend,actions&time_range={\"since\":\"${since}\",\"until\":\"${until}\"}`, {\n headers: { Authorization: `Bearer ${tok}` }, signal: AbortSignal.timeout(20_000),\n });\n } catch { throw new Error(\"Meta API unreachable\"); }\n if (!r.ok) throw new Error(`Meta insights -> HTTP ${r.status}`);\n const d = await r.json();\n const row = d?.data?.[0];\n const convs = Number((row?.actions ?? []).find((a: any) => a.action_type === \"onsite_conversion.total_messaging_connection\" || a.action_type === \"lead\")?.value ?? 0);\n return { spend: Number(row?.spend ?? 0), convs };\n}\n\nconst esc = (s: unknown) => String(s ?? \"\").replace(/[&<>\"']/g, (c) => ({ \"&\": \"&\", \"<\": \"<\", \">\": \">\", '\"': \""\", \"'\": \"'\" }[c] as string));\nconst RAMP = [\"#86b6ef\", \"#3987e5\", \"#256abf\", \"#184f95\", \"#0f3a6e\"];\nconst GOOD = \"#0ca30c\", WARN = \"#fab219\", CRIT = \"#d03b3b\";\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n const k = url.searchParams.get(\"k\") || \"\";\n const admin = await isAdmin(k);\n const viewer = !admin && (await isViewer(k));\n if (!admin && !viewer) return new Response(\"Not found\", { status: 401 });\n\n // ?ads=1 (admin only): per-ad Meta spend for a window, straight off the ad platform, as JSON.\n // Exists so cost-per-lead can join platform spend to CRM attribution WITHOUT a number ever\n // being typed. Read only; touches nothing; the formula lives beside the figures downstream.\n if (admin && url.searchParams.get(\"ads\") === \"1\") {\n const tok = Deno.env.get(\"META_TOKEN\"), act = Deno.env.get(\"META_AD_ACCOUNT\");\n if (!tok || !act) return Response.json({ ok: false, why: \"META_TOKEN or META_AD_ACCOUNT not set\" });\n const since = url.searchParams.get(\"since\") || \"\", until = url.searchParams.get(\"until\") || \"\";\n if (!/^\\d{4}-\\d{2}-\\d{2}$/.test(since) || !/^\\d{4}-\\d{2}-\\d{2}$/.test(until)) {\n return Response.json({ ok: false, why: \"since/until must be YYYY-MM-DD\" });\n }\n try {\n const r = await fetch(\n `https://graph.facebook.com/v21.0/${act}/insights?level=ad&fields=ad_id,ad_name,campaign_name,spend,actions&limit=200&time_range={\"since\":\"${since}\",\"until\":\"${until}\"}`,\n { headers: { Authorization: `Bearer ${tok}` }, signal: AbortSignal.timeout(25_000) },\n );\n const body = await r.json();\n if (!r.ok) return Response.json({ ok: false, why: `Facebook returned ${r.status}`, detail: body?.error?.message ?? null });\n const rows = (body?.data ?? []).map((d: any) => ({\n adId: String(d.ad_id ?? \"\"), adName: String(d.ad_name ?? \"\"), campaign: String(d.campaign_name ?? \"\"),\n spend: Number(d.spend ?? 0),\n conv: Number((d.actions ?? []).find((a: any) => a.action_type === \"onsite_conversion.total_messaging_connection\")?.value\n ?? (d.actions ?? []).find((a: any) => a.action_type === \"lead\")?.value ?? 0),\n }));\n return Response.json({ ok: true, since, until, rows, formula: \"cost per lead = spend / CRM contacts whose first-touch utmAdId equals adId, same window\" });\n } catch (e) {\n return Response.json({ ok: false, why: String(e).slice(0, 120) });\n }\n }\n\n const nowMs = Date.now();\n const tzMin = etOffsetMin(nowMs);\n const { current, previous } = reportWindows(nowMs, tzMin);\n const errors: string[] = [];\n const chartWeeks = 8;\n const floor = current.endMs - chartWeeks * 7 * 86_400_000;\n\n let contacts: ContactLite[] = [], ptEvents: EventLite[] = [], ftdEvents: EventLite[] = [], opps: OppLite[] = [];\n try { contacts = await contactsSince(floor, errors); } catch (e) { errors.push(`New inquiries could not be read: ${String(e).slice(0, 90)}`); }\n try { ptEvents = await eventsFor(PUP_TALK_CAL, previous.startMs, current.endMs); } catch (e) { errors.push(`Pup Talk calendar could not be read: ${String(e).slice(0, 90)}`); }\n try { for (const c of FTD_CALS) ftdEvents.push(...(await eventsFor(c, previous.startMs, current.endMs))); } catch (e) { errors.push(`Free Training Day calendars could not be read: ${String(e).slice(0, 90)}`); }\n try { opps = await wonOppsAll(errors); } catch (e) { errors.push(`Deals could not be read: ${String(e).slice(0, 90)}`); }\n\n let meta: { spend: number; convs: number } | null = null;\n let metaErr: string | null = null;\n try { meta = await metaSpend(current, tzMin); } catch (e) { metaErr = String(e).slice(0, 90); }\n\n const enq = countContacts(contacts, current), enqPrev = countContacts(contacts, previous);\n const pt = countEvents(ptEvents, current), ptPrev = countEvents(ptEvents, previous);\n const ftd = countEvents(ftdEvents, current);\n const won = wonOpps(opps, current), wonPrev = wonOpps(opps, previous);\n const sourcesAll = channelBreakdown(contacts, current); // R32: was sourceBreakdown, which showed 'no source recorded' as her largest channel\n const sources = sourcesAll.slice(0, 6);\n const buckets = weeklyBuckets(contacts, current.endMs, chartWeeks);\n const maxB = Math.max(1, ...buckets);\n\n // The follow-up system's own status, one honest line (stranger-test finding: the report was\n // silent about the thing the retainer is partly for).\n let engineLine = \"\";\n try {\n const blob2 = await blobMod();\n const st = (await blob2.getJSON(\"puppy_state\")) ?? {};\n const run = (await blob2.getJSON(\"puppy_run_state\")) ?? {};\n const rows: any[] = Object.values(st);\n const activeN = rows.filter((s: any) => [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"].includes(s?.status)).length;\n engineLine = run?.testMode === true\n ? `The automated follow-up system is in practice mode and contacting nobody yet. ${activeN === 1 ? \"One test contact is\" : activeN + \" test contacts are\"} running through the sequence to prove it works.`\n : run?.testMode === false\n ? `The automated follow-up system is LIVE with ${activeN} ${activeN === 1 ? \"person\" : \"people\"} in a sequence.`\n : \"\";\n } catch { engineLine = \"\"; }\n\n const unmarked = Math.max(0, pt.booked - pt.showed - pt.noshow);\n const commentary = draftCommentary({\n enq, enqPrev, ptBooked: pt.booked, ptPrev: ptPrev.booked, ptShowed: pt.showed,\n wonCount: won.count, wonValue: won.value, wonPrevValue: wonPrev.value,\n topSource: sources[0]?.source ?? null, adTracked: !!meta,\n });\n\n // snapshot: label by the window end date (the Friday). Load last week's for the look-back box.\n const weekKey = new Date(current.endMs).toISOString().slice(0, 10);\n const prevKey = new Date(previous.endMs).toISOString().slice(0, 10);\n const blob = await blobMod().catch(() => null);\n let prevSnap: any = null;\n let savedNote = \"\";\n if (blob) {\n prevSnap = await blob.getJSON(`friday_report_${prevKey}`).catch(() => null);\n const existing = await blob.getJSON(`friday_report_${weekKey}`).catch(() => null);\n const isFridayEt = new Date(nowMs + tzMin * 60_000).getUTCDay() === 5;\n const explicitSave = url.searchParams.get(\"save\") === \"1\";\n // v1.0.1 (fixes #2, #7) — never snapshot a week whose reads FAILED (zeros would be quoted\n // as truth forever); explicit save=1 may overwrite a bad snapshot; success claimed only\n // after the write actually resolved.\n if (admin && errors.length === 0 && (explicitSave || (isFridayEt && !existing))) {\n try {\n await blob.setJSON(`friday_report_${weekKey}`, {\n ts: new Date().toISOString(), weekKey,\n numbers: { enq, enqPrev, pt, ftd, won: won, sources },\n commentary,\n });\n savedNote = \"This week's snapshot was saved just now, next week's report will quote it.\";\n } catch { savedNote = \"Snapshot save FAILED, will retry on next view.\"; }\n } else if (admin && errors.length > 0 && (explicitSave || isFridayEt)) {\n savedNote = \"Snapshot NOT saved: some numbers could not be read (see below).\";\n } else if (existing) savedNote = \"Snapshot for this week already saved.\";\n }\n\n const fmtD = (ms: number) => new Date(ms + tzMin * 60_000).toISOString().slice(5, 10).replace(\"-\", \"/\");\n const tile = (label: string, v: string, note: string, accent?: string) =>\n `

${esc(v)}

${esc(label)}

${esc(note)}

`;\n\n const bars = buckets.map((b, i) => {\n const label = i === chartWeeks - 1 ? \"this wk\" : \"\";\n return `

${b}

${label}

`;\n }).join(\"\");\n\n const srcRows = sources.map((s) => `${esc(s.source)}${s.n}`).join(\"\") || `none this week`;\n\n const adCells = meta\n ? `${tile(\"Ad spend\", money(meta.spend), \"Meta, this week\")}${tile(\"Cost per inquiry\", enq ? money(meta.spend / enq) : \"n/a\", \"spend / inquiries\")}`\n : `${tile(\"Ad spend\", \"not tracked yet\", metaErr ? \"connection problem, see appendix\" : \"shows here once Amir links the ad account\", WARN)}`;\n\n // R32: was counting off `source`, which produced \"the CRM recorded 0 Facebook contacts\" in a week\n // its own attribution recorded 116. `unsourced` is deliberately no longer added in: under\n // attribution the unattributed population is about 1 in 142, not 111, so padding it would be\n // inventing a number. It is reported separately as a data-quality note instead.\n const fbLanded = facebookLanded(contacts, current);\n const cover = attributionCoverage(contacts, current);\n const unattributed = cover.total - cover.known;\n const recon = meta\n ? `

Did the ad leads actually land?

Meta reports ${meta.convs} conversation${meta.convs === 1 ? \"\" : \"s\"} started this week. In the same window ${fbLanded} of the ${cover.total} new contacts in your CRM arrived from Facebook or Instagram, read from the arrival record your CRM keeps on each person. So the comparison is ${meta.convs} claimed against ${fbLanded} landed. The gap, if any, is leads that never became reachable contacts, the number worth watching.${unattributed ? ` ${unattributed} contact${unattributed === 1 ? \"\" : \"s\"} this week arrived with no origin recorded at all and ${unattributed === 1 ? \"is\" : \"are\"} in neither figure.` : \"\"}

`\n : `

Did the ad leads actually land?

Not tracked yet. The day the ad account tokens are connected, this section compares what the platforms claim they delivered against what actually arrived in the CRM.

`;\n\n const errBox = errors.length\n ? `

Some numbers could not be read

${esc(e)}

Missing numbers are shown as errors, never guessed. Refresh in a few minutes; if it persists, tell Amir.

`\n : \"\";\n\n const lastWeekBox = prevSnap\n ? `

What last week's report said

${(prevSnap.commentary ?? []).map((c: string) => esc(c)).join(\" \")}

`\n : `

What last week's report said

No saved report from last week to quote yet. The week-on-week comparisons above are computed fresh from the CRM either way; this box starts quoting the written summary next week.

`;\n\n const html = `\nThe Dogs Spot weekly report, ${esc(fmtD(current.startMs))} to ${esc(fmtD(current.endMs - 86_400_000))}\n

The Dogs Spot, the week in numbers

The week of Friday ${esc(fmtD(current.startMs))} through Thursday ${esc(fmtD(current.endMs - 86_400_000))}. Every figure is read fresh from the CRM when this page opens. ${esc(savedNote)}

\n\n

\n${tile(\"New inquiries\", String(enq), deltaWord(enq, enqPrev), enq > enqPrev ? GOOD : undefined)}\n${tile(\"Pup Talks on the calendar\", String(pt.booked), deltaWord(pt.booked, ptPrev.booked))}\n${tile(\"New customers\", String(won.count), `reached the Customer stage (last week ${wonPrev.count})`, won.count > wonPrev.count ? GOOD : undefined)}\n${adCells}\n

\n\n

What happened, in words DRAFT until Amir reviews

\n${commentary.map((c) => `

${esc(c)}

`).join(\"\")}${unmarked > 0 ? `

${esc(`${unmarked} of the week's Pup Talks ${unmarked === 1 ? \"was\" : \"were\"} never marked showed or no-show in the CRM, so the show rate is fuzzier than it should be. A ten-second tidy after each call fixes that.`)}

` : \"\"}${engineLine ? `

${esc(engineLine)}

` : \"\"}

\n\n

New inquiries, last eight weeks

${bars}

Each bar is one Friday-to-Thursday week; the rightmost is the week above. As a list: ${buckets.join(\", \")}. Across the eight weeks shown, ${buckets.reduce((a, b) => a + b, 0).toLocaleString(\"en-US\")} new people.

\n\n

Where this week's inquiries came from

\n${srcRows}

Source	People

\n\n

Why there is no revenue figure

${(() => {\n const valued = opps.filter((o) => o.monetaryValue > 0);\n const sum = valued.reduce((a, o) => a + o.monetaryValue, 0);\n const money = (n: number) => \"$\" + n.toLocaleString(\"en-US\", { minimumFractionDigits: 2, maximumFractionDigits: 2 });\n // Generated from the same array the tile above counts, so this sentence cannot drift away from\n // the data the way the hand-written one did. It used to read \"every opportunity sits at zero\n // dollars\", which stopped being true and stayed on the page.\n return valued.length === 0\n ? `Not one of your ${opps.length.toLocaleString(\"en-US\")} customer records carries a dollar value, so no honest revenue number can be produced from them.`\n : `${valued.length} of your ${opps.length.toLocaleString(\"en-US\")} customer records carry a dollar value, totaling ${money(sum)}. The other ${(opps.length - valued.length).toLocaleString(\"en-US\")} are empty, which is why this report still cannot tell you what a week earned: the money exists in your payment records, it just never reaches the booking.`;\n})()} Counting people who reach the Customer stage is the closest true measure, and that is the tile above. Put a number on each deal as the deposit is taken and this report can show revenue instead.

\n\n${recon}\n${lastWeekBox}\n${errBox}\n\n

Appendix, the fine print

This week's raw counts

\n\n\n\n\n\n\n${metaErr ? `` : \"\"}\n

Of the ${pt.booked} Pup Talks: showed / no-show / never marked either way	${pt.showed} / ${pt.noshow} / ${Math.max(0, pt.booked - pt.showed - pt.noshow)}
Canceled (not counted above)	${pt.cancelled}
Show rate	${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)}` : \"\"}
Free Training Day booked / showed	${ftd.booked} / ${ftd.showed}${ftd.booked === 0 ? \" (none scheduled this week)\" : \"\"}
Meta connection error	${esc(metaErr)}

How every number is computed

\n${Object.entries(FORMULAS).map(([k, v]) => `

${esc(k)}: ${esc(v)}

`).join(\"\")}\n

Page built ${esc(new Date(nowMs + tzMin * 60_000).toISOString().slice(0, 16).replace(\"T\", \" at \"))} Georgia time.

`;\n\n return new Response(html, { headers: { \"content-type\": \"text/html; charset=utf-8\", \"cache-control\": \"no-store\" } });\n}\n",[203],"a8c78fee-a002-46e1-b932-4f041b4fdd89","report-logic.ts","79e5d064-901f-11f1-a19e-1607ee4eb77e",679,["D",1786387503379],8,"// FRIDAY REPORT, pure computation module. No network, no Deno APIs: everything here is\n// offline-testable, and every number the report shows is produced by a function in this file\n// with its formula written next to it. v1.0, 4 Aug 2026.\n//\n// ACCURACY RULES (the non-negotiables the report was commissioned under):\n// - numbers come from platform APIs upstream of these functions, never typed in\n// - every derived figure's formula is stored beside it (FORMULAS below, rendered in appendix)\n// - anything unverifiable renders as \"not tracked yet\", never a guess\n\n// `attribution` was PROVEN present on 190/190 contacts in the live account on 4 Aug 2026, while\n// the `source` column was blank on 154 of the same 190. The CRM records where a person came from\n// in a place its own source column never reads from. Optional, because every older caller and\n// every test builds a ContactLite without it.\nexport type Attribution = { medium?: string | null; campaign?: string | null };\nexport type ContactLite = { dateAdded: string; source: string | null; tags: string[]; attribution?: Attribution | null };\nexport type EventLite = { startTime: number; appointmentStatus: string; calendarId: string };\nexport type OppLite = { createdAt: string; status: string; monetaryValue: number; lastStageChangeAt?: string | null };\n\nexport type Window = { startMs: number; endMs: number; label: string };\n\n// Reporting week: Friday 00:00 ET back seven days. The report is read Friday morning, so the\n// most recent COMPLETE window is the seven days ending Thursday midnight.\nexport function reportWindows(nowMs: number, tzOffsetMin: number): { current: Window; previous: Window } {\n // tzOffsetMin: minutes to ADD to UTC to get business-local (ET = -240 in summer).\n const local = new Date(nowMs + tzOffsetMin * 60_000);\n const day = local.getUTCDay(); // 0 Sun .. 5 Fri .. 6 Sat, in local terms\n // most recent Friday 00:00 local, strictly in the past or today\n const sinceFri = (day - 5 + 7) % 7;\n const fri = Date.UTC(local.getUTCFullYear(), local.getUTCMonth(), local.getUTCDate() - sinceFri);\n const friUtcMs = fri - tzOffsetMin * 60_000; // back to real UTC instant of local Friday 00:00\n const week = 7 * 86_400_000;\n return {\n current: { startMs: friUtcMs - week, endMs: friUtcMs, label: \"this week\" },\n previous: { startMs: friUtcMs - 2 * week, endMs: friUtcMs - week, label: \"last week\" },\n };\n}\n\nexport function inWindow(iso: string | number, w: Window): boolean {\n const t = typeof iso === \"number\" ? iso : Date.parse(iso);\n return Number.isFinite(t) && t >= w.startMs && t < w.endMs;\n}\n\n// ---- the formulas, stored as data so the appendix can print them verbatim -----------------------\nexport const FORMULAS: Record = {\n \"New inquiries\": \"how many new people landed in the CRM during the seven days, counted by the date the CRM stamped on them\",\n \"Pup Talks on the calendar\": \"how many Pup Talk appointments had a start time inside the seven days, not counting cancelled ones\",\n \"Showed\": \"how many of those the CRM marked as showed up\",\n \"Show rate\": \"showed divided by booked; the percentage is only quoted when at least five were booked, because a rate built on two appointments misleads\",\n \"Free Training Day\": \"the same counting, done against both Free Training Day calendars\",\n \"New customers\": \"people whose deal reached the Customer stage in the CRM during the week, counted in the week they got there, not the week they first got in touch\",\n \"Up or down on last week\": \"this week against the same count for the seven days before it, shown as level, or up or down by a percentage\",\n \"Cost per inquiry\": \"ad spend divided by new inquiries; appears once the ad account is linked, and is never estimated before then\",\n \"Did the ad leads land\": \"what the ad platform claims it delivered, side by side with what actually arrived in the CRM the same week\",\n};\n\nexport function countContacts(cs: ContactLite[], w: Window): number {\n return cs.filter((c) => inWindow(c.dateAdded, w)).length;\n}\n\nexport function sourceBreakdown(cs: ContactLite[], w: Window): Array<{ source: string; n: number }> {\n const m = new Map();\n for (const c of cs.filter((c) => inWindow(c.dateAdded, w))) {\n const s = (c.source || \"no source recorded\").trim().toLowerCase() || \"no source recorded\";\n m.set(s, (m.get(s) ?? 0) + 1);\n }\n return [...m.entries()].map(([source, n]) => ({ source, n })).sort((a, b) => b.n - a.n);\n}\n\nexport function countEvents(evs: EventLite[], w: Window): { booked: number; showed: number; noshow: number; cancelled: number } {\n const live = evs.filter((e) => inWindow(e.startTime, w));\n const ok = live.filter((e) => e.appointmentStatus !== \"cancelled\" && e.appointmentStatus !== \"invalid\");\n return {\n booked: ok.length,\n showed: ok.filter((e) => e.appointmentStatus === \"showed\").length,\n noshow: ok.filter((e) => e.appointmentStatus === \"noshow\" || e.appointmentStatus === \"no-show\").length,\n cancelled: live.length - ok.length,\n };\n}\n\nexport function wonOpps(os: OppLite[], w: Window): { count: number; value: number } {\n const won = os.filter((o) => o.status === \"won\" && inWindow(o.lastStageChangeAt || o.createdAt, w));\n return { count: won.length, value: won.reduce((a, o) => a + (Number(o.monetaryValue) || 0), 0) };\n}\n\n// weekly buckets for the 8-week chart, oldest first\n// The reader-facing name for each raw medium string. Anything not in this map is passed through\n// as itself rather than bucketed into \"other\", so a new channel appears by name instead of\n// silently vanishing into a catch-all nobody investigates.\nconst MEDIUM_LABEL: Record = {\n facebook: \"Facebook\", instagram: \"Instagram\", form: \"a form on your website\",\n chat_widget: \"the chat box on your website\", conversation: \"a direct message\",\n other: \"somewhere else\", email: \"email\", sms: \"text message\", phone: \"phone call\",\n};\nexport function prettyMedium(m: string | null | undefined): string {\n const k = (m || \"\").trim().toLowerCase();\n if (!k) return \"not recorded\";\n return MEDIUM_LABEL[k] ?? k.replace(/_/g, \" \");\n}\n// Where people actually came from, read from the attribution record rather than the source column.\nexport function channelBreakdown(cs: ContactLite[], w: Window): Array<{ source: string; n: number }> {\n const m = new Map();\n for (const c of cs.filter((c) => inWindow(c.dateAdded, w))) {\n const label = prettyMedium(c.attribution?.medium);\n m.set(label, (m.get(label) ?? 0) + 1);\n }\n return [...m.entries()].map(([source, n]) => ({ source, n }))\n .sort((a, b) => (b.n - a.n) || a.source.localeCompare(b.source));\n}\n// Named campaigns. A campaign name is ad-platform text, so it reaches the page as data and must\n// be escaped there like any other untrusted string.\nexport function campaignBreakdown(cs: ContactLite[], w: Window): Array<{ name: string; n: number }> {\n const m = new Map();\n for (const c of cs.filter((c) => inWindow(c.dateAdded, w))) {\n const name = (c.attribution?.campaign || \"\").trim();\n if (!name) continue;\n m.set(name, (m.get(name) ?? 0) + 1);\n }\n return [...m.entries()].map(([name, n]) => ({ name, n }))\n .sort((a, b) => (b.n - a.n) || a.name.localeCompare(b.name));\n}\n// How many of a window's contacts can be placed at all. This is the honest headline for the\n// section: \"we can account for X of Y\", never a bare count of the unexplained.\nexport function attributionCoverage(cs: ContactLite[], w: Window): { known: number; total: number } {\n const inW = cs.filter((c) => inWindow(c.dateAdded, w));\n return { known: inW.filter((c) => (c.attribution?.medium || \"\").trim()).length, total: inW.length };\n}\n\n// R32 (10 Aug 2026). Paid-social arrivals, read from the ARRIVAL RECORD, never from `source`.\n// Case-insensitive on purpose: channelBreakdown returns display labels from prettyMedium\n// (\"Facebook\", \"Instagram\"), so a case-sensitive regex here reproduces the exact bug this replaces.\nexport const PAID_SOCIAL_RE = /facebook|instagram|meta|messenger/i;\nexport function facebookLanded(cs: ContactLite[], w: Window): number {\n return channelBreakdown(cs, w).filter((s) => PAID_SOCIAL_RE.test(s.source)).reduce((a, s) => a + s.n, 0);\n}\n\nexport function weeklyBuckets(cs: ContactLite[], endMs: number, weeks: number): number[] {\n const wMs = 7 * 86_400_000;\n const out = new Array(weeks).fill(0);\n for (const c of cs) {\n const t = Date.parse(c.dateAdded);\n if (!Number.isFinite(t) || t >= endMs || t < endMs - weeks * wMs) continue;\n const idx = weeks - 1 - Math.floor((endMs - 1 - t) / wMs);\n if (idx >= 0 && idx < weeks) out[idx]++;\n }\n return out;\n}\n\nexport function pct(n: number, d: number): string {\n if (!d) return \"n/a\";\n return Math.round((n / d) * 100) + \"%\";\n}\n\nexport function deltaWord(cur: number, prev: number): string {\n if (cur === prev) return \"level with last week\";\n if (prev === 0) return cur > 0 ? \"up from zero last week\" : \"level with last week\";\n const ch = Math.round(((cur - prev) / prev) * 100);\n return ch > 0 ? `up ${ch}% on last week` : `down ${Math.abs(ch)}% on last week`;\n}\n\nexport function money(n: number): string {\n return \"$\" + n.toLocaleString(\"en-US\", { minimumFractionDigits: 2, maximumFractionDigits: 2 });\n}\n\n// ---- draft commentary: rule-based sentences from the computed numbers. Never speculates. --------\n// Marked DRAFT in the page; the human tops and tails before it goes anywhere.\nexport function draftCommentary(f: {\n enq: number; enqPrev: number;\n ptBooked: number; ptPrev: number; ptShowed: number;\n wonCount: number; wonValue: number; wonPrevValue: number;\n topSource: string | null;\n adTracked: boolean;\n}): string[] {\n const lines: string[] = [];\n lines.push(\n `${f.enq} new ${f.enq === 1 ? \"inquiry\" : \"inquiries\"} came in this week, ${deltaWord(f.enq, f.enqPrev)}.` +\n (f.topSource === \"no source recorded\"\n ? ` Most arrived without a source recorded in the CRM, a tracking gap worth closing.`\n : f.topSource\n ? ` The biggest source was ${f.topSource}.`\n : \"\"),\n );\n lines.push(\n `${f.ptBooked} Pup Talk${f.ptBooked === 1 ? \" was\" : \"s were\"} on the calendar (${deltaWord(f.ptBooked, f.ptPrev)})` +\n (f.ptBooked >= 5 ? `, and ${f.ptShowed} of them showed (${pct(f.ptShowed, f.ptBooked)}).` : f.ptBooked > 0 ? `, ${f.ptShowed} showed.` : \".\"),\n );\n // The CRM holds no deal values (proven live: every opportunity is $0 and none are flagged\n // won), so this counts PEOPLE reaching the Customer stage and never implies a revenue figure.\n if (f.wonCount > 0) {\n lines.push(`${f.wonCount} ${f.wonCount === 1 ? \"person\" : \"people\"} reached the Customer stage this week.`);\n } else {\n lines.push(`Nobody reached the Customer stage in the CRM this week.`);\n }\n if (!f.adTracked) {\n lines.push(`Ad spend and cost per lead are not tracked yet, they appear the week the ad platform tokens are connected.`);\n }\n return lines;\n}\n",[211],"ab06b90a-4bea-4ed5-9cfe-9e9ba9cd3552","render.ts","5f8048e8-902f-11f1-8bd3-1607ee4eb77e",77,["D",1785866856515],"// MESSAGE RENDERING. Extracted from main.ts on 4 Aug 2026.\n//\n// WHY IT LIVES HERE: main.ts sits against a hard 80,000-character ceiling on the platform, and\n// these are the most self-contained functions in the file. Pulling them out also means the escape\n// and merge-field rules can be tested directly rather than only through a full engine run, which\n// matters because two of the fixes below came out of a security review, not a feature request.\n\n// Spec: dog name blank on ~70% of sampled contacts; fallback \"your puppy\" per the writing sheet's own\n// proposed default (§6 Q3). Messy-but-present values (multi-dog, junk like \"Money\") are used as-is —\n// that's an intake-form data-quality problem, not something to silently \"clean\" here.\nexport function resolveDogName(companyName: string | null | undefined): string {\n const v = (companyName ?? \"\").trim();\n return v.length > 0 ? v : \"your puppy\";\n}\n\n// Spec only discusses the blank-dog-name case explicitly. Added this small parallel safety net for a\n// blank first name (defensive, beyond spec's literal text) because \"Hi ,\" landing in a live message\n// would look obviously broken — same principle as the dog-name fallback, applied consistently.\nexport function resolveFirstName(firstName: string | null | undefined): string {\n const v = (firstName ?? \"\").trim();\n return v.length > 0 ? v : \"there\";\n}\n\nexport function applyMergeFields(template: string, firstName: string | null | undefined, companyName: string | null | undefined): string {\n // v1.8.1 — function form so $-patterns in names (\"Bo$$\") cannot corrupt the body.\n return template\n .replaceAll(\"{{FIRST_NAME}}\", () => resolveFirstName(firstName))\n .replaceAll(\"{{DOG_NAME}}\", () => resolveDogName(companyName));\n}\n\n// v1.8.1 — contact-typed fields and Kim's stories land in email HTML; escape BEFORE the\n// **bold** transform so markup we generate survives and markup anyone else typed does not.\nexport function escHtml(s: string): string {\n return s.replace(/[&<>\"']/g, (c) => ({ \"&\": \"&\", \"<\": \"<\", \">\": \">\", '\"': \""\", \"'\": \"'\" }[c] as string));\n}\n\nexport function mdBoldToHtml(text: string): string {\n return text.replace(/\\*\\*(.+?)\\*\\*/g, \"$1\");\n}\n\nexport function bodyToHtml(body: string, previewText?: string): string {\n const paragraphs = escHtml(body)\n .trim()\n .split(/\\n\\s*\\n/)\n .map((p) => `

${mdBoldToHtml(p.trim()).replace(/\\n/g, \"
\")}

`)\n .join(\"\\n\");\n // Hidden preheader technique so the approved \"preview text\" shows in an inbox list without being\n // visible in the opened email — standard, low-risk, one line.\n const preheader = previewText\n ? `\\n`\n : \"\";\n return preheader + paragraphs;\n}\n\n",[219],"acb44c15-3b84-42e4-8bc6-52df8ab6fdaf","registry-diff.ts","a96cde42-908b-11f1-96ea-1607ee4eb77e",172,["D",1785906494226],"// WHAT CHANGED IN A LIST SOMEBODY ELSE CONTROLS. v1.0, 5 August 2026.\n//\n// The watchdog watches two registries in Kim's CRM that nobody on this project owns: her 165\n// automations, and the eight knowledge bases Chloe answers customers from. Both can be edited by\n// Kim, by Kristian, or by an integration nobody remembers installing, and until v1.6 the knowledge\n// bases were not watched at all. The consolidated one was edited at 02:38 on 5 August and nothing\n// noticed.\n//\n// This is the comparison, on its own, so it can be tested. It lived inline in the watchdog before,\n// where it could only ever be checked by waiting for somebody to change something — which means a\n// check nobody has ever seen go off. Same rule as everywhere else in this project: a check that\n// cannot be shown to fail is not a check.\n//\n// It deliberately knows nothing about workflows or knowledge bases. It takes two maps of\n// id -> description and says what moved.\n\nexport type Registry = Record;\n\nexport type RegistryChange = {\n added: string[];\n removed: string[];\n edited: string[]; // \"old -> new\", so a reader can see what moved without opening anything\n changed: boolean;\n};\n\nexport function registryDiff(prev: Registry | null | undefined, now: Registry | null | undefined): RegistryChange {\n const a = prev && typeof prev === \"object\" ? prev : {};\n const b = now && typeof now === \"object\" ? now : {};\n const prevIds = Object.keys(a);\n const nowIds = Object.keys(b);\n const added = nowIds.filter((i) => !(i in a)).map((i) => b[i]);\n const removed = prevIds.filter((i) => !(i in b)).map((i) => a[i]);\n const edited = nowIds.filter((i) => i in a && a[i] !== b[i]).map((i) => `${a[i]} -> ${b[i]}`);\n return { added, removed, edited, changed: added.length + removed.length + edited.length > 0 };\n}\n\n/**\n * Is this an empty response we should DISTRUST rather than act on?\n *\n * A malformed-but-200 reply that returns an empty list must never overwrite a good baseline, or\n * the next pass fires \"everything was removed\" and the one after that fires \"everything was\n * added\". The watchdog learned this on the workflow registry; the knowledge-base watch inherits it\n * rather than rediscovering it.\n */\nexport function looksLikeAGlitch(nowCount: number, prevCount: number | null | undefined): boolean {\n return nowCount === 0 && (prevCount ?? 0) > 0;\n}\n\n/** The sentence, generated from the change, never written alongside it. */\nexport function registrySentence(c: RegistryChange, what: string): string {\n if (!c.changed) return `Nothing has moved in ${what} since the last look.`;\n const bits: string[] = [];\n if (c.edited.length) bits.push(`Edited: ${c.edited.slice(0, 3).join(\"; \")}.`);\n if (c.added.length) bits.push(`Added: ${c.added.slice(0, 3).join(\"; \")}.`);\n if (c.removed.length) bits.push(`Removed: ${c.removed.slice(0, 3).join(\"; \")}.`);\n const more = c.added.length + c.removed.length + c.edited.length - Math.min(3, c.edited.length) - Math.min(3, c.added.length) - Math.min(3, c.removed.length);\n if (more > 0) bits.push(`${more} more not listed here.`);\n return bits.join(\" \");\n}\n",[226],"70bf4a4c-1d82-4f81-a6e0-19368d156d63","puppy-messages.ts","cd4b87b0-8c34-11f1-b87e-1607ee4eb77e",455,["D",1786285580501],5,"// PUPPY PATH — message copy module (split from the engine for val.town's 80k/file limit).\n// Copy is VERBATIM from PHASE1-PUPPY-PATH-WRITING-SHEET.md §3 — do not paraphrase here, ever.\ndeclare const Deno: { env: { get(key: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\n\n// ---- v1.3 change, 2 Aug 2026 — booking URL. RETRACTION APPENDED, read the whole block ----------\n// The previous value was:\n// https://api.leadconnectorhq.com/widget/bookings/pbe-discovery-9edbddc3-4b5a-406e-9bc3-7f10cb0d3221\n//\n// WHAT I ORIGINALLY WROTE HERE (and it was wrong): that this id \"does NOT belong to this location\"\n// and was the parent agency's own discovery-call widget.\n//\n// RETRACTED, same day, on better evidence. Re-checking GET /calendars/?locationId=BQHJ19uohldYe3eqA0bl\n// field by field shows `pbe-discovery-9edbddc3-4b5a-406e-9bc3-7f10cb0d3221` is the *widget slug of\n// Kim's own \"Pup Talk Phone Call\" calendar* — the same calendar as qHuYJ0NEqzibnoqf5Cw3. Confirmed\n// independently: https://book.thedogsspotga.com/phone (the page the website's own \"Book your Free\n// Pup Talk\" button leads to) contains BOTH strings. /widget/bookings/ and\n// /widget/booking/ are two URL forms for one object; both return 200 and both land on\n// her calendar. The original link was never broken. I inferred \"not hers\" from the \"pbe\" prefix —\n// which is Pet Biz Experts, the agency that set the account up and therefore named the slug — and\n// stated the inference as a verified finding. That is the error, and it is the kind that matters\n// more than the code change.\n//\n// The current value is kept anyway, for one real reason that survives the retraction: the engine\n// watches PUP_TALK_CALENDAR_ID (qHuYJ0NEqzibnoqf5Cw3) to detect a booking, so using the calendar-id\n// form makes the link a lead clicks and the object the engine watches literally the same string,\n// with no slug indirection to go stale. Secondary: the word \"discovery\" does not appear in it, and\n// Kim asked for \"Pup Talk\" instead.\n//\n// Regression test A1 asserts `!includes(\"pbe-\")`. That assertion is now a style rule, not a\n// correctness rule. Left in place; the comment above is the correction of record.\nexport const REAL_BOOKING_URL =\n \"https://api.leadconnectorhq.com/widget/booking/qHuYJ0NEqzibnoqf5Cw3\";\nexport const SHORT_BOOKING_LINK = Deno.env.get(\"SHORT_BOOKING_LINK\") || REAL_BOOKING_URL;\n\n// Phone number: two live candidates, and the earlier note here (\"zero signals point to 912-823-4382\")\n// is CORRECTED as of 2 Aug 2026. Signals for 912-823-4382 turned out to be strong: it is the meeting\n// location on 73 of 193 Pup Talk appointments, it is the number in the default confirmation text of\n// BOTH booking widgets (\"please call our office at (912) 823-4382\"), and thedogsspotga.com/about-5\n// tells customers to ring it to schedule a training drop-off.\n// Still using 912-348-8726, on a narrower and now-honest basis: it is the number in the website\n// footer on every page and behind the home page \"Call Us\" button, so it is the number a lead who\n// found the site already has. Both are real. Kim must pick one before go-live — flagged on the todo\n// list, not decided quietly.\nexport const PHONE_DISPLAY = Deno.env.get(\"PHONE_DISPLAY\") || \"912-348-8726\";\n\nexport type Channel = \"email\" | \"sms\";\n\nexport type MessageTemplate = {\n id: string;\n channel: Channel;\n offsetHours: number;\n subject?: string; // email only\n previewText?: string; // email only\n bodyTemplate: string;\n};\n\n// ---- message copy (PHASE1-PUPPY-PATH-WRITING-SHEET.md §3, VERBATIM — do not paraphrase) ----------\n// {{FIRST_NAME}} is the ONLY per-contact merge token, resolved at render time by\n// v2.0, 4 Aug 2026. {{DOG_NAME}} was removed from every message in this file and in the taper,\n// on Kim's instruction: \"we haven't always got the name and so if we have a placeholder for the\n// puppies name, it reads weird when there's no puppy in there so I think we should go with having\n// the person's name, but not necessarily the puppies name\". Facebook leads, which are four in\n// five of all inquiries, frequently arrive with no dog name at all. Every sentence that used it\n// was REWRITTEN to read naturally without one, rather than having \"your puppy\" substituted in\n// mechanically, because the mechanical version is exactly what she was objecting to.\n// Also on her instruction, same message: toilet -> potty, garden -> yard, and DAYCARE REMOVED\n// ENTIRELY. They do not offer daycare. That is the same class of error as describing grooming as\n// a service, and it had been sitting in four messages.\n// The old comment, for the record:\n// applyMergeFields(). [phone] / [link] are fixed placeholders per the writing sheet's own §1\n// distinction (Title Case = merge field, lower case = placeholder) — resolved ONCE below via real\n// template-literal interpolation of PHONE_DISPLAY / SHORT_BOOKING_LINK, not per contact.\n// **bold** markdown in messages 3/5/6 is rendered to by bodyToHtml() — that is a formatting\n// transform, not a wording change; the words themselves are untouched.\n//\n// v2.1, 6/7 Aug 2026 — five more of her own corrections (handover/REGISTER-AUG7.md §4), confirmed\n// back to her in writing 7 Aug (handover/MESSAGE-TO-KIM-7-AUG.txt, lines 80-83): main-2 no longer\n// opens \"Got your message\" (opens on the welcome instead); \"pitch\" is gone everywhere a Pup Talk is\n// described, in favour of saying what it IS; branch_a-2 and branch_b-1 lose the \"I won't chase\n// you\"/\"won't keep bugging you\" what-I-won't-do framing while the positive \"reach out\"/\"call or\n// text ... anytime\"/\"door's open\" lines next to them are kept, exactly as she asked; branch_b-2's\n// British \"getting on\" becomes \"going\". Tests: tests/kim-copy.test.mjs, section \"THE 6 AUG\n// FOLLOW-UP\".\n\nexport const MAIN_SEQUENCE: MessageTemplate[] = [\n {\n id: \"main-1\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Getting your puppy off to a good start\",\n previewText: \"A few things that matter more than people expect in these first weeks.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThanks for getting in touch.\n\nWhether you're bringing a puppy home soon, or yours is already running circles around the kitchen, the timing of what happens next matters more than people expect.\n\nA puppy's window for learning that new people, new dogs, new places and new sounds are all safe starts closing earlier than most owners realize - a lot of that learning is done by around four to five months old. Whatever they meet calmly now tends to stay easy for life. Whatever gets missed is harder to fix later. Not impossible, just harder, and it usually takes longer than it would have the first time round.\n\nOver the next few weeks I'll send you a handful of short, practical emails - biting, potty training, recall, that sort of thing. Real advice, not fluff.\n\nIf you'd rather just talk it through now, that's what a Pup Talk is for - a real conversation with our team about how things are going. Reply to this email, call or text us on ${PHONE_DISPLAY}, or grab a time here: ${SHORT_BOOKING_LINK}.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"main-2\",\n channel: \"sms\",\n offsetHours: 2,\n // v2.1, 6/7 Aug — \"Touch 2 loses 'I got your message' and opens on the welcome.\" Kim's own\n // question about the old line: \"What message am I replying to exactly?\" (REGISTER-AUG7.md §4).\n // This can be the first thing a contact hears from her at all, so \"got your message\" did not\n // always make sense; \"welcome\" carries the same warmth without assuming a reply is owed.\n bodyTemplate: `Hi {{FIRST_NAME}}, it's Kim at The Dogs Spot. Welcome! I'll send a few honest, useful puppy emails over the next few weeks. Reply anytime, a real person reads these.`,\n },\n {\n id: \"main-3\",\n channel: \"email\",\n offsetHours: 72, // day 3\n subject: \"Puppy biting: normal, not naughty\",\n previewText: \"What's actually going on when a puppy won't stop mouthing, and what helps.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nIf your puppy has started biting at hands, sleeves, ankles, shoelaces - that's not a behavior problem. It's normal. Puppies explore the world with their mouths the way toddlers explore it with their hands, and it usually gets worse before it gets better, especially once teething starts.\n\nA few things that actually help:\n\n**Redirect, don't just say no.** Keep a toy or a chew within arm's reach of wherever you usually sit, so it's already in your hand before the mouthing starts rather than after. The moment teeth touch skin, swap your hand for the toy. Saying \"no\" tells them to stop; it doesn't tell them what to do instead, and a puppy who is told to stop with nothing to switch to just tries again.\n\n**Watch for the overtired witching hour.** A lot of biting spikes happen when a puppy is overstimulated or short on sleep, not when they're being difficult. A nap often does more than any correction.\n\n**Yelp, don't wrestle.** If it hurts, a short \"ow\" and a pause in play teaches bite inhibition better than pulling your hand away, which can turn into a game.\n\nIt gets better. Most of this settles down significantly by six months, and properly once the adult teeth are in. It feels endless at week two. It isn't.\n\nIf any of that doesn't match what you're seeing, reply and tell me - I read these.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"main-4\",\n channel: \"sms\",\n offsetHours: 144, // day 6\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Quick one - how's the biting and potty training going? Totally normal stage either way. Reply and let me know, happy to help.`,\n },\n {\n id: \"main-5\",\n channel: \"email\",\n offsetHours: 216, // day 9\n subject: \"A realistic potty-training timeline\",\n previewText: \"What actually helps, and why one accident isn't a setback.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nPotty training questions are the ones I get asked about most, usually some version of \"is this normal?\" Almost always, yes.\n\nA young puppy's bladder is small and their control over it is genuinely limited - not a matter of trying harder. As a rough guide, a lot of trainers use \"roughly one hour of control for every month of age\" early on, which is why an eight- or ten-week-old puppy needs to go out far more often than seems reasonable.\n\nWhat tends to work:\n\n**A schedule, not a hope.** Out first thing, after every meal, after every nap, after play, and last thing at night - before you think they need it, not after.\n\n**Same spot, same word.** Consistency does more work than any product. Pick a spot, use a calm word or phrase every time, and reward the second they finish outside, not back indoors where the reward disconnects from the act.\n\n**Supervise or contain.** Accidents mostly happen when a puppy has quiet, unsupervised access to another room. A crate, a pen, or simply keeping them in sight closes that gap.\n\n**No telling off for accidents.** By the time you've found it, they have moved on. Telling them off teaches confusion, not house manners.\n\nMost puppies are largely reliable by four to six months, and fully reliable somewhat later. If yours is well past that and still having accidents daily, that's worth looking at properly rather than pushing through - reply and tell me what's happening.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"main-6\",\n channel: \"email\",\n offsetHours: 312, // day 13\n subject: \"Recall is a habit, not a hope\",\n previewText: `Why \"come\" is worth starting now, even before it matters.`,\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nRecall - getting your puppy to come back reliably - is the one piece of training that keeps a dog safe for the rest of their life. It's also the easiest one to start too late.\n\nThe mistake most people make isn't training it wrong. It's not starting until it's needed - at the park, off lead, with distractions already in the way. By then you're teaching recall and competing for attention at the same time.\n\nStarted early, it's simple:\n\n**Practice where nothing's competing for attention.** Hallway, living room, yard. Say the word once, and make coming back to you the best thing that happens all day - food, praise, a game, whatever they actually want.\n\n**Never call for something unpleasant.** If \"come\" ever means bath time, nail clipping, or the end of a walk, it stops meaning \"good things happen.\" Go get them for that instead.\n\n**Reward every single time, at first.** Not just the good ones. Recall is a habit you're building, not a trick you're testing.\n\nRecall is the one people most often ask me to look at, usually because it worked in the yard and then stopped working everywhere else. If you'd like a hand with it, a Pup Talk is a free twenty-minute call: ${SHORT_BOOKING_LINK}, or call or text ${PHONE_DISPLAY}.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"main-7\",\n channel: \"sms\",\n offsetHours: 408, // day 17\n bodyTemplate: `Hi {{FIRST_NAME}}, no pressure at all - if you'd like to talk through training or boarding for your puppy, we're easy to reach. Call or text ${PHONE_DISPLAY}, or book a time here: ${SHORT_BOOKING_LINK}. Kim, The Dogs Spot`,\n },\n {\n id: \"main-8\",\n channel: \"email\",\n offsetHours: 504, // day 21\n subject: \"The last puppy email from me for now\",\n previewText: \"What matters most from the last three weeks, and an open door.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThis is the last of the every-few-days emails, so a quick summary of everything I've sent: get your puppy meeting the world calmly while that window's open, expect the biting and treat it as normal, keep the potty-training schedule boring and consistent, and start recall before you need it, not after.\n\nNone of that is complicated. Most of it is just easy to talk yourself out of doing consistently when you're tired and there's a puddle on the floor again.\n\nFrom here I'll slow right down - a short note each week for a few weeks, then less and less, only ever the useful kind. If you'd like to talk any of this through properly - what's normal for your puppy specifically, what training or boarding would actually suit your week, what it costs and when it makes sense to start - that's what a Pup Talk is for. It's a conversation. Reply here, call or text ${PHONE_DISPLAY}, or grab a time yourself: ${SHORT_BOOKING_LINK}.\n\nAnd if now just isn't the right time, that's completely fine too. No hard feelings, and the door doesn't close.\n\nKim\nThe Dogs Spot`,\n },\n];\n\nexport const BRANCH_A: MessageTemplate[] = [\n {\n id: \"branch_a-1\",\n channel: \"sms\",\n offsetHours: 2,\n bodyTemplate: `Hi {{FIRST_NAME}}, it's Kim - looks like we missed each other for your Pup Talk. No worries at all, it happens. Want me to find another time? Just reply and I'll schedule it.`,\n },\n {\n id: \"branch_a-2\",\n channel: \"email\",\n offsetHours: 24, // day +1\n subject: \"Let's find another time\",\n previewText: \"Fifteen minutes, whenever actually suits.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nI noticed we had a Pup Talk scheduled, but we missed each other. No worries at all, I know life gets busy.\n\nIt's a quick, no-pressure call where we'll talk about what's been going on, answer any questions you have, and see whether training with us would be a good fit. And if we're not the right fit, I'll tell you that too.\n\nJust reply with a couple of times that work for you, call or text me at ${PHONE_DISPLAY}, or book a time that's convenient here: ${SHORT_BOOKING_LINK}.\n\nIf I don't hear back, I'll assume now just isn't the right time. Whenever you're ready, just reach out, I'd be happy to help.\n\nKim\nThe Dogs Spot`,\n },\n];\n\nexport const BRANCH_B: MessageTemplate[] = [\n {\n id: \"branch_b-1\",\n channel: \"email\",\n offsetHours: 24, // day +1 after the call\n subject: \"Good talking with you\",\n previewText: \"Just a couple of things from our conversation.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThanks for the call. It's genuinely useful for me to hear how things are going, even outside of anything you decide to book.\n\nIf it's not the right time for training or boarding with us, that's completely fine. A lot of people need more than one conversation before it's the right moment, and that's how it should work - nobody should sign up on a call because it felt awkward not to.\n\nIf anything changes, or a question comes up later that we didn't cover, reply here or call or text ${PHONE_DISPLAY} anytime. I'd just rather you knew the door's open than wonder.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"branch_b-2\",\n channel: \"sms\",\n offsetHours: 192, // day +8 after the call\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim again - no news needed, just checking how it's going for you both. If a question's come up since we spoke, reply here anytime. No pressure either way.`,\n },\n];\n\n",[233],"06c38757-da91-45a9-bc23-8a9b0ecafb86","puppy-detect.ts","299fd626-9089-11f1-805a-1607ee4eb77e",164,["D",1785905947813],2,"// WHO IS A PUPPY INQUIRY. v1.0, 5 August 2026.\n//\n// WHY THIS FILE EXISTS. The engine enrolls people carrying the tag `nurture - puppy`. Nothing in\n// Kim's account applies that tag: all 5,544 contacts checked, zero carry it. So go-live is three\n// switches, not two, and this is the third.\n//\n// WHY IT IS NOT A ONE-LINE REGEX. The first thing I tried was matching \"puppy\" or an age in weeks\n// or months against the inquiry summary. Over the 800 most recent contacts it returned 29 people,\n// and reading them showed it was wrong about several in ways that matter:\n//\n// * \"Ken Anderson was looking to purchase a puppy. He inquired whether The Dog's Spot GA offered\n// puppies for sale. The agent clarified that they do not sell.\" He would have received\n// forty-one messages about training a puppy he does not own.\n// * \"Charlie, who is 3 years and 4 months old\" matched on \"4 months old\". The dog is three.\n// * \"Evelyn Carter was seeking good homes for her older dogs\" matched on the word \"new puppy\"\n// later in a sentence about rehoming.\n//\n// A false positive here is not a bad row in a spreadsheet. It is a real person getting nineteen\n// months of messages about a puppy they do not have, in Kim's name.\n//\n// SO THIS FILE NEVER APPLIES A TAG. It classifies, it explains itself in one sentence per person,\n// and it hands the list to a human. `confidence` is the whole point: \"clear\" is defensible on its\n// own, \"probable\" wants a glance, \"unclear\" is a question rather than an answer.\n//\n// It also reports its own blind spot, loudly: the inquiry summary is populated on about half of\n// contacts. Anyone with no summary cannot be classified by this at all, and saying so is part of\n// the output rather than a footnote.\n\nexport type Verdict = {\n contactId: string;\n name: string;\n confidence: \"clear\" | \"probable\" | \"unclear\" | \"no\";\n /** One sentence, in plain English, naming the words that decided it. */\n reason: string;\n /** Months, when a dog's age could be read. null when it could not. */\n ageMonths: number | null;\n matched: string[];\n};\n\nexport type DetectSummary = {\n scanned: number;\n withText: number;\n noText: number;\n clear: number;\n probable: number;\n unclear: number;\n no: number;\n};\n\nconst num = (s: string): number | null => {\n const words: Record = {\n one: 1, two: 2, three: 3, four: 4, five: 5, six: 6, seven: 7, eight: 8,\n nine: 9, ten: 10, eleven: 11, twelve: 12, eighteen: 18,\n };\n const t = s.trim().toLowerCase();\n if (/^\\d+(\\.\\d+)?$/.test(t)) return Number(t);\n return words[t] ?? null;\n};\n\n/**\n * The dog's age in months, or null.\n *\n * The \"3 years and 4 months old\" trap is handled by looking for a YEARS reading first and letting\n * it win. A dog described in years is not a puppy however many months are mentioned afterwards.\n */\nexport function ageInMonths(text: string): number | null {\n const t = text.toLowerCase();\n // YEARS FIRST, AND THEY WIN OUTRIGHT.\n // [was: the years pattern required the word \"old\" straight after it, as in \"3-year-old\". So\n // \"Charlie, who is 3 years and 4 months old\" did not match it — the \"old\" belongs to the\n // months — and fell through to the months branch, which read the dog as 4 months. That is\n // the exact false positive this whole file exists to prevent, and the first version of the\n // file still had it. Caught by its own test, not by reading it.]\n const y = t.match(/(\\d+(?:\\.\\d+)?|one|two|three|four|five|six|seven|eight|nine|ten|eleven|twelve)[\\s-]*(?:year|yr)s?\\b/);\n if (y) {\n const n = num(y[1]);\n if (n != null) {\n const m = t.slice(y.index ?? 0).match(/(?:year|yr)s?[\\s,-]*(?:and\\s*)?(\\d+|one|two|three|four|five|six|seven|eight|nine|ten|eleven)[\\s-]*(?:month|mo)s?\\b/);\n return n * 12 + (m ? (num(m[1]) ?? 0) : 0);\n }\n }\n const mo = t.match(/(\\d+(?:\\.\\d+)?|one|two|three|four|five|six|seven|eight|nine|ten|eleven|twelve|eighteen)(?:\\s*-\\s*\\d+)?[\\s-]*(?:month|mo)s?[\\s-]*old/);\n if (mo) { const n = num(mo[1]); if (n != null) return n; }\n const wk = t.match(/(\\d+(?:\\.\\d+)?|one|two|three|four|five|six|seven|eight|nine|ten|eleven|twelve)(?:\\s*-\\s*\\d+)?[\\s-]*(?:week|wk)s?[\\s-]*old/);\n if (wk) { const n = num(wk[1]); if (n != null) return Math.round((n / 4.345) * 10) / 10; }\n return null;\n}\n\n// Reasons someone is NOT a puppy-training inquiry even though the word appears. Each one is here\n// because a real contact in Kim's account tripped it.\nconst DISQUALIFIERS: Array<[RegExp, string]> = [\n [/\\b(purchase|buy|buying|sell|selling|for sale|breeder|adopt(?:ing)? a)\\b[^.]{0,40}\\bpupp/i,\n \"they were asking to buy a puppy, not to train one\"],\n [/\\bpupp\\w*\\b[^.]{0,40}\\b(for sale|to sell|available to buy)\\b/i,\n \"they were asking to buy a puppy, not to train one\"],\n [/\\b(rehome|rehoming|good homes|find(?:ing)? homes|surrender|give away)\\b/i,\n \"they were rehoming dogs rather than asking about training\"],\n [/\\b(do not sell|don't sell|does not sell|doesn't sell)\\b/i,\n \"the reply on file says Kim does not sell dogs, so this was not a training inquiry\"],\n];\n\nconst PUPPY_WORDS = /\\b(pupp(?:y|ies)|new pup\\b|pup\\b)/i;\n// Kim's puppy sequence is written for a young dog. Past about a year it is the wrong sequence.\nconst PUPPY_MAX_MONTHS = 12;\n\n/** Age in the words a person would use. Nobody says a dog is 1.4 months old. */\nexport function sayAge(months: number): string {\n if (months < 2) { const w = Math.round(months * 4.345); return `${w} week${w === 1 ? \"\" : \"s\"} old`; }\n if (months < 24) { const m = Math.round(months); return `${m} month${m === 1 ? \"\" : \"s\"} old`; }\n const y = Math.round(months / 12);\n return `${y} year${y === 1 ? \"\" : \"s\"} old`;\n}\n\nexport function classify(contactId: string, name: string, text: string): Verdict {\n const clean = (text ?? \"\").replace(/\\s+/g, \" \").trim();\n if (!clean) {\n return { contactId, name, confidence: \"unclear\", ageMonths: null, matched: [],\n reason: \"There is nothing written down about what they asked for, so this cannot be decided from the record.\" };\n }\n\n for (const [re, why] of DISQUALIFIERS) {\n const m = clean.match(re);\n if (m) return { contactId, name, confidence: \"no\", ageMonths: ageInMonths(clean), matched: [m[0].slice(0, 60)], reason: `Not a puppy inquiry: ${why}.` };\n }\n\n const age = ageInMonths(clean);\n const saysPuppy = PUPPY_WORDS.test(clean);\n const matched: string[] = [];\n if (saysPuppy) matched.push((clean.match(PUPPY_WORDS) ?? [\"\"])[0]);\n if (age != null) matched.push(`${age} months old`);\n\n if (age != null && age > PUPPY_MAX_MONTHS) {\n return { contactId, name, confidence: \"no\", ageMonths: age, matched,\n reason: `Not a puppy inquiry: the dog is given as ${sayAge(age)}, which is past the sequence.` };\n }\n if (age != null && saysPuppy) {\n return { contactId, name, confidence: \"clear\", ageMonths: age, matched,\n reason: `Called a puppy and given as ${sayAge(age)}, so both signals agree.` };\n }\n // A very young age settles it on its own. No adult dog is four months old, so the word \"puppy\"\n // adds nothing at this end and demanding it would push obvious cases down to \"probable\".\n if (age != null && age <= 6) {\n return { contactId, name, confidence: \"clear\", ageMonths: age, matched,\n reason: `The dog is given as ${sayAge(age)}, which is a puppy whatever words they used.` };\n }\n if (age != null) {\n return { contactId, name, confidence: \"probable\", ageMonths: age, matched,\n reason: `The dog is given as ${sayAge(age)}, which is inside the sequence, but the word puppy is not used.` };\n }\n if (saysPuppy) {\n return { contactId, name, confidence: \"probable\", ageMonths: null, matched,\n reason: \"They call it a puppy, but no age is written down, so how young is a guess.\" };\n }\n return { contactId, name, confidence: \"no\", ageMonths: null, matched: [],\n reason: \"Nothing in what they wrote points at a puppy.\" };\n}\n\nexport function summarise(vs: Verdict[], scanned: number): DetectSummary {\n const by = (c: Verdict[\"confidence\"]) => vs.filter((v) => v.confidence === c).length;\n const noText = vs.filter((v) => v.matched.length === 0 && v.confidence === \"unclear\").length;\n return { scanned, withText: scanned - noText, noText, clear: by(\"clear\"), probable: by(\"probable\"),\n unclear: by(\"unclear\"), no: by(\"no\") };\n}\n\n/**\n * How old is this reading, in words, or null when it is fresh enough not to mention.\n *\n * A dry pass that stopped running would otherwise keep showing its last numbers as though they\n * were this morning's. The engine runs about hourly, so anything past six hours has missed\n * several turns and is worth saying out loud.\n */\nexport function scanAgeNote(atIso: string | null | undefined, nowMs: number): string | null {\n if (!atIso) return null;\n const ms = nowMs - Date.parse(atIso);\n if (!Number.isFinite(ms) || ms < 0) return null;\n const hours = ms / 3_600_000;\n if (hours < 6) return null;\n if (hours < 48) return `This count was last taken about ${Math.round(hours)} hours ago rather than just now, so treat it as a little out of date.`;\n return `This count was last taken about ${Math.round(hours / 24)} days ago, so it has stopped being kept up and the numbers below are old.`;\n}\n\n/** The sentence for the summary, generated from the counts, never written alongside them. */\nexport function detectSentence(s: DetectSummary | null): string {\n if (!s || !s.scanned) return \"No contacts were read, so there is nothing to report here rather than a zero to trust.\";\n const parts = [\n `${s.scanned.toLocaleString(\"en-US\")} contacts were read. ${s.clear} are clearly a puppy inquiry and ${s.probable} probably are.`,\n ];\n if (s.noText) {\n parts.push(`${s.noText} of them have nothing written down about what they asked for, so they cannot be judged from the record at all, either way.`);\n }\n parts.push(\"Nothing has been tagged. This is a list to look at, not an action taken.\");\n return parts.join(\" \");\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE DRY PASS.\n//\n// This file has NO WAY TO APPLY A TAG and that is structural, not a promise: there is no fetch, no\n// POST and no client in it. Everything here takes contacts in and hands verdicts out. The engine\n// calls it on each run, writes the counts down, and applies nothing. When the tagging is finally\n// armed it will be armed somewhere a human had to go and change, not here.\n//\n// The custom-field ids are Kim's account's. `inquiryText` is deliberately forgiving about the\n// shape of a contact, because it is fed straight from the CRM's JSON.\n// ---------------------------------------------------------------------------------------------\nexport const FIELD_INQUIRY_SUMMARY = \"N8Mw4Mmz5ecesIOrQMWm\";\nexport const FIELD_TRAINING_GOAL = \"4EXdybS2XUAaP6tnlncI\";\n\nexport function inquiryText(contact: unknown): string {\n const cfs = (contact as any)?.customFields;\n if (!Array.isArray(cfs)) return \"\";\n const pick = (id: string) => {\n const f = cfs.find((x: any) => x?.id === id);\n const v = f?.value;\n return typeof v === \"string\" || typeof v === \"number\" ? String(v) : \"\";\n };\n return `${pick(FIELD_INQUIRY_SUMMARY)} ${pick(FIELD_TRAINING_GOAL)}`.trim();\n}\n\nexport function classifyContacts(contacts: unknown): Verdict[] {\n if (!Array.isArray(contacts)) return [];\n return contacts\n .filter((c: any) => c && typeof c.id === \"string\")\n .map((c: any) => classify(c.id, String(c.contactName ?? c.firstName ?? \"(no name)\"), inquiryText(c)));\n}\n\nexport type DryScan = {\n at: string;\n summary: DetectSummary;\n /** Ids only, and only the ones worth a human's time. Never names, never message text. */\n clearIds: string[];\n probableIds: string[];\n /** Always false in this file. Present so the panel can state it rather than assume it. */\n applied: false;\n};\n\nexport function dryScan(contacts: unknown, at: string): DryScan {\n const vs = classifyContacts(contacts);\n return {\n at,\n summary: summarise(vs, vs.length),\n clearIds: vs.filter((v) => v.confidence === \"clear\").map((v) => v.contactId),\n probableIds: vs.filter((v) => v.confidence === \"probable\").map((v) => v.contactId),\n applied: false,\n };\n}\n",[241],"da098612-2e84-4e61-9da5-5300a92cdae9","payments-source.ts","e209084c-94ec-11f1-9ce5-1607ee4eb77e",690,["D",1786388055037],"// SQUARE MONEY AS THE CRM RECORDS IT. New 10 Aug 2026.\n//\n// WHY THIS FILE EXISTS. Until today `money-match.ts` was imported by its own test and by nothing\n// else. There was no call to /payments/transactions anywhere in the repo, so every figure on Kim's\n// money page came from a process that was not in the tree, and the filters below were unwritten\n// rather than misconfigured. This is that missing layer.\n//\n// It is a SEPARATE module on purpose: test MM-h asserts the string `fetch(` never appears in\n// money-match.ts, and that test is worth keeping.\n//\n// The endpoint, and note it rejects `locationId` and wants `altId`:\n// GET /payments/transactions?altId=&altType=location&limit=100&offset=\nimport type { Payment } from \"./money-match.ts\";\n\n// Every source type this location produces, proven live 10 Aug 2026 across all 233 transactions:\n// calendar 158, invoice 61, funnel 11, payment_link 2, manual 1. All 233 carry a contactId.\n// payment_link is IN. Both rows today are failed tests worth $0, but reusable front desk payment\n// links are a live workstream, and a matcher that silently dropped them would report the front\n// desk's first day of takings as zero, with no error, which reads as \"business was quiet\".\nexport const ACCEPTED_SOURCE_TYPES: readonly string[] = Object.freeze([\n \"calendar\", \"invoice\", \"funnel\", \"payment_link\", \"manual\",\n]);\nconst ACCEPTED = new Set(ACCEPTED_SOURCE_TYPES);\n\n// A $0 row is a calendar booking artifact, not money: 171 of 233 live, every one status\n// \"succeeded\". A sub $1 row is a card test: 10 live, $3.05 total, every one pending, belonging to\n// \"emily harris\" and \"automation dogs test\".\n//\n// FILTER ON AMOUNT, NOT ON SOURCE TYPE. Filtering entitySourceType !== \"calendar\" is the near miss:\n// it leaves 13 zero rows standing, which is what invents a phantom payment collision and inflates\n// the booking count. It is also the wrong axis, because invoice/calendar produces both $0 artifacts\n// and real money.\nexport const MIN_REAL_PAYMENT = 1;\nexport const isRealMoney = (p: { amount: number }) => p.amount >= MIN_REAL_PAYMENT;\n\nexport function toPayment(t: any): Payment {\n return {\n id: String(t?._id ?? \"\"),\n amount: Number(t?.amount) || 0,\n status: String(t?.status ?? \"\"),\n contactId: t?.contactId ?? null,\n contactName: t?.contactName ?? null,\n at: t?.createdAt ?? null,\n };\n}\n\nexport type Accepted = { payments: Payment[]; unknownTypes: string[]; dropped: { zeroOrTest: number } };\n\n// An UNRECOGNISED source type is KEPT and REPORTED, never dropped. A new type is a new way money\n// arrives, and dropping it silently is how revenue goes missing without anybody seeing an error.\nexport function acceptPayments(rows: any[]): Accepted {\n const unknown = new Set();\n const kept: Payment[] = [];\n let zeroOrTest = 0;\n for (const t of rows) {\n const st = String(t?.entitySourceType ?? \"\");\n if (st && !ACCEPTED.has(st)) unknown.add(st);\n const p = toPayment(t);\n if (!isRealMoney(p)) { zeroOrTest++; continue; }\n kept.push(p);\n }\n return { payments: kept, unknownTypes: [...unknown].sort(), dropped: { zeroOrTest } };\n}\n",[249],"45dd7fb4-4470-47ce-90d9-5b801f8704d0","paths.ts","243d2a8e-8e78-11f1-bbbc-1607ee4eb77e",118,["D",1785876026154],"// PATH REGISTRY, the six nurture paths as data, plus the validator that guards them. 2 Aug 2026.\n//\n// WHY\n// The engine was written for one path. Generalising it by rewriting the state machine on a live\n// client system is the kind of refactor that breaks something nobody notices for a week. The\n// cheaper and safer generalisation is to move the *definition* of a path out of code: a path is a\n// tag, a sequence of steps, and a set of exit rules. The engine already treats steps as data\n// (renderStep takes a template); this file makes the whole path a record.\n//\n// RETRACTED, 2 Aug 2026, and the RENDERED SENTENCE corrected 4 Aug: the retraction sat in this\n// comment for two days while the page below carried on printing the claim it retracts. A comment\n// is not a correction. This file used to claim registering paths 2-6 was \"a copy drop, not an\n// engineering job\". That was wrong and it was repeated to the client. The engine does not read this\n// file: puppy_path_v1.1.ts imports MAIN_SEQUENCE/BRANCH_A/BRANCH_B directly from puppy-messages.ts,\n// hardcodes TAG_SOURCE_SIGNAL, and stores Record, one position per contact,\n// not one per path. Dropping steps into a row below would render a green line on this page and send\n// nothing. Path 2 needs the state model, per-path tag mapping, sequence selection and precedence\n// rules built. Days, not an afternoon. This page is a registry and a validator; it is not wiring.\n//\n// THE VALIDATOR IS THE POINT\n// Every path, before it can be registered, has to survive the same checks the test suite runs\n// against the puppy path: no banned wording, no unresolved merge token, SMS inside carrier limits,\n// at least one opt-out line, a booking link that points at a calendar this account actually owns,\n// monotonic timing, and a defined terminal step. A path that fails is refused with reasons rather\n// than half-registered.\n//\n// ?k= the registry: what is defined, what is live, what is missing\n// ?k=&validate=1 run the validator over everything registered\n// ?k=&f=json the same as JSON\n\n// ---- auth ------------------------------------------------------------------------------------\n// v2 (2 Aug, after the adversarial pass): the key is NOT in this file. val.town vals are PUBLIC -\n// proved by fetching this very source with no token, so a literal key here was readable by anyone\n// who found the val, which meant anyone could read Kim's data, stop her system, or trigger a run.\n// Only the SHA-256 digest lives in source now. The digest is useless to a reader and sufficient for\n// a comparison, so publishing the code no longer publishes the secret.\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\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 override = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\");\n const expected = override || KEY_SHA256;\n const got = await sha256Hex(k);\n // Constant-time over equal-length hex digests.\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\n\n// The one calendar this account owns for training consults. Verified live 2 Aug against\n// GET /calendars/?locationId=, \"Pup Talk Phone Call\". Any booking link in any path must contain it.\nconst OWNED_BOOKING_ID = \"qHuYJ0NEqzibnoqf5Cw3\";\nconst OWNED_BOARDING_FORM = \"thedogsspotga.com/boarding-booking-form\";\n\nexport type Step = {\n id: string;\n channel: \"email\" | \"sms\";\n offsetHours: number;\n subject?: string;\n previewText?: string;\n bodyTemplate: string;\n};\n\nexport type PathDef = {\n key: string;\n label: string;\n sourceTag: string; // applying this tag in the CRM is how a human enrols someone\n enrolledTag: string; // minted by the engine on enrolment\n source: \"engine\" | \"ghl\" | \"off\"; // mutual exclusion: never let a val and a GHL workflow both own a path\n channelsAtLaunch: (\"email\" | \"sms\")[];\n steps: Step[];\n notes: string;\n // v1.5, 2 Aug 2026, THE COLLISION MAP, and the most important field in this file.\n // `source` was always a DECLARATION of who owns a path. It was never checked against what the CRM\n // is actually running. Checked properly today via GET /workflows/?locationId= : the location has\n // 165 workflows, 95 of them PUBLISHED, and every one of the six paths below already has published\n // GoHighLevel automation whose name overlaps it. Declaring `source: \"engine\"` does not switch those\n // off. GoHighLevel exposes no endpoint for reading a contact's workflow enrolments\n // (/contacts/{id}/workflow -> 404) so overlap cannot be detected per contact, only per path, by a\n // human reading each workflow. Until a row here is cleared, treat it as live competition for the\n // same customer's inbox. The engine's R27 quiet-period guard is the runtime backstop; this list is\n // the thing that stops us needing it.\n ghlOverlap: { name: string; status: \"published\" | \"draft\"; version: number }[];\n};\n\n// ---- the registry ---------------------------------------------------------------------------------\n// PUPPY is populated from the deployed module so there is exactly one copy of that copy. The other\n// five are declared with everything except their steps: the tag names, the launch channels and the\n// constraints are all decided, so registering them is `steps: [...]` and nothing else.\n\nimport { MAIN_SEQUENCE, BRANCH_A, BRANCH_B } from \"./puppy-messages.ts\";\n\nexport const PATHS: PathDef[] = [\n {\n key: \"puppy\", label: \"Puppy owners\", sourceTag: \"nurture - puppy\", enrolledTag: \"puppy-path-v1\",\n source: \"engine\", channelsAtLaunch: [\"email\", \"sms\"],\n steps: [...MAIN_SEQUENCE, ...BRANCH_A, ...BRANCH_B] as Step[],\n notes: \"Live in the engine. 8 main + 2 no-show + 2 didn't-buy. The template for the other five.\",\n ghlOverlap: [\n { name: \"1. Wait 1 Day: Initial Nurture - Puppy\", status: \"published\", version: 2 },\n { name: \"1. Wait 1 Day: Initial Nurture\", status: \"published\", version: 2 },\n { name: \"Edited - Main New Nurture (New/Updated)\", status: \"published\", version: 4 },\n { name: \"Secondary Nurture Workflow\", status: \"published\", version: 4 },\n { name: \"A. Removed Tag : Initial Lead Nurtures\", status: \"published\", version: 2 },\n { name: \"Secondary Nurture - PUPPY Workflow\", status: \"draft\", version: 5 },\n { name: \"1. Initial Nurture - Facebook\", status: \"draft\", version: 3 },\n { name: \"1. Initial Nurture - Instagram\", status: \"draft\", version: 3 },\n ],\n },\n {\n key: \"behavior\", label: \"Behavior problems\", sourceTag: \"nurture - behavior\", enrolledTag: \"behavior-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\", \"sms\"], steps: [],\n notes: \"Largest real demand signal, 172 asks in the gap log. The day-14 aggression email is the highest-risk message in the whole set and Kim reads it personally before this path is switched on.\",\n ghlOverlap: [\n { name: \"Behavior Quiz Submitted\", status: \"published\", version: 3 },\n { name: \"Dialed In Dog ZJ : Free Training Day Quiz\", status: \"published\", version: 16 },\n { name: \"Quiz -. Pup Talk > Notes\", status: \"published\", version: 4 },\n { name: \"Quiz Score Redirect Logic\", status: \"draft\", version: 6 },\n ],\n },\n {\n key: \"boarding\", label: \"Boarding inquiries\", sourceTag: \"nurture - boarding\", enrolledTag: \"boarding-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\", \"sms\"], steps: [],\n notes: \"The only path allowed to quote prices, and only the boarding ones Kim confirmed. Every mention of hours must carry the appointment-only rule. Booking goes to her website form, never a GHL calendar.\",\n ghlOverlap: [\n { name: \"Boarding Drop-Off - Confirmation + Reminder\", status: \"published\", version: 19 },\n { name: \"Boarding Pick-Up - Confirmation + Reminder\", status: \"published\", version: 25 },\n { name: \"Abandoned Cart - Partial booking\", status: \"published\", version: 5 },\n { name: \"Cancel Boarding - Drop Off\", status: \"published\", version: 3 },\n { name: \"Online Boarding Update > Kennel\", status: \"published\", version: 4 },\n { name: \"Boarding App Webhook\", status: \"published\", version: 18 },\n ],\n },\n {\n key: \"noshow\", label: \"Pup Talk, didn't show\", sourceTag: \"nurture - noshow\", enrolledTag: \"noshow-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\", \"sms\"], steps: [],\n notes: \"Closes a measured hole: 19 no-shows and 8 cancellations across 145 Pup Talk events with nothing following up.\",\n ghlOverlap: [\n { name: \"Cxld/Canceled Pup Talk\", status: \"published\", version: 7 },\n { name: \"Cxld or No Show - Consult Nurture\", status: \"published\", version: 4 },\n { name: \"Free training day no show nurture\", status: \"published\", version: 9 },\n { name: \"Cxld/Canceled Free Training Day\", status: \"published\", version: 4 },\n { name: \"Tag Added 'No Show' > No Show\", status: \"published\", version: 2 },\n { name: \"Tag Added 'No Show DND' > No Show TO PREVENT ANOTHER BOOKING\", status: \"published\", version: 2 },\n { name: \"Free Training Day abandoned booking\", status: \"published\", version: 8 },\n ],\n },\n {\n key: \"didntbuy\", label: \"Pup Talk, didn't buy\", sourceTag: \"nurture - didntbuy\", enrolledTag: \"didntbuy-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\", \"sms\"], steps: [],\n notes: \"82 attended and few converted. Kim's $500 discount decision lives near this path, keep them separate until its wording and its own dry/live toggle exist.\",\n ghlOverlap: [\n { name: \"POST CONSULT - NO SALE NURTURE MESSAGES\", status: \"published\", version: 4 },\n { name: \"Tag added 'No Sale' > No Sale Nurture\", status: \"published\", version: 2 },\n ],\n },\n {\n key: \"aged\", label: \"Dormant inquiries\", sourceTag: \"nurture - aged\", enrolledTag: \"aged-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\"],\n steps: [],\n notes: \"EMAIL ONLY AT LAUNCH, and the audience is far smaller than the headline: of 3,426 dormant contacts only ~164 have an email address and ~2,655 have neither email nor phone. SMS stays held until numbers are validated, stale numbers get a business flagged by carriers, which would damage every other path.\",\n ghlOverlap: [\n { name: \"Tips Nurture\", status: \"published\", version: 7 },\n { name: \"TIPS FACEBOOK CAMPAIGN - SMS Nurture\", status: \"published\", version: 3 },\n { name: \"Auto Replies > tips campaign\", status: \"published\", version: 10 },\n { name: \"Copy - Tips Ad campaign > Auto Responder\", status: \"published\", version: 11 },\n { name: \"Tips ad campaign > response > phone number\", status: \"published\", version: 10 },\n { name: \"Tips Ad campaign > Auto Responder\", status: \"draft\", version: 19 },\n ],\n },\n];\n\n// ---- the validator --------------------------------------------------------------------------------\n\nconst BANNED = [\n { re: /discovery/i, why: 'Kim banned \"discovery call\", it is \"Pup Talk\"' },\n { re: /grooming/i, why: \"grooming is not a service they offer\" },\n { re: /\\$\\s?\\d/, why: \"a price in a message; boarding prices come from the knowledge base, training prices never\" },\n // Templates legitimately contain {{FIRST_NAME}} and {{DOG_NAME}}, they are resolved per contact at\n // render time, and the engine has fallbacks for both when a contact has neither. Anything ELSE in\n // double braces is a token nobody wired up, which is what actually reaches a customer as literal\n // text. Caught by the first validator run, which flagged all 12 real templates: a check that fails\n // on correct input is worse than no check.\n { re: /\\{\\{(?!\\s*(FIRST_NAME|DOG_NAME)\\s*\\}\\})/, why: \"an unrecognised merge token, only {{FIRST_NAME}} and {{DOG_NAME}} are wired up\" },\n { re: /\\[link\\]|\\[phone\\]|INSERT|TODO|LOREM/i, why: \"a placeholder that never got resolved\" },\n];\n\nexport function validatePath(p: PathDef) {\n const errors: string[] = [], warnings: string[] = [];\n if (!p.steps.length) return { key: p.key, registered: false, ok: false, errors: [\"no steps registered yet\"], warnings: [] };\n\n let sawOptOut = false, sawBooking = false;\n const sms = p.steps.filter((s) => s.channel === \"sms\");\n\n for (const s of p.steps) {\n const text = `${s.subject ?? \"\"}\\n${s.previewText ?? \"\"}\\n${s.bodyTemplate}`;\n for (const b of BANNED) if (b.re.test(text)) errors.push(`${s.id}: ${b.why}`);\n if (/\\bstop\\b/i.test(s.bodyTemplate) || /reply\\s+stop/i.test(s.bodyTemplate)) sawOptOut = true;\n if (s.bodyTemplate.includes(OWNED_BOOKING_ID) || s.bodyTemplate.includes(OWNED_BOARDING_FORM)) sawBooking = true;\n if (/leadconnectorhq\\.com\\/widget\\/bookings?\\//.test(s.bodyTemplate) &&\n !s.bodyTemplate.includes(OWNED_BOOKING_ID)) {\n errors.push(`${s.id}: booking link does not point at a calendar this account owns, this is the exact defect found on 2 Aug`);\n }\n if (s.channel === \"sms\" && s.bodyTemplate.length > 320) errors.push(`${s.id}: SMS ${s.bodyTemplate.length} chars, over the 320 ceiling`);\n if (s.channel === \"email\" && !s.subject) errors.push(`${s.id}: email with no subject line`);\n }\n\n const offsets = p.steps.map((s) => s.offsetHours);\n const mainish = p.steps.filter((s) => s.id.startsWith(\"main\"));\n if (mainish.length > 1) {\n for (let i = 1; i < mainish.length; i++) {\n if (mainish[i].offsetHours <= mainish[i - 1].offsetHours) {\n errors.push(`${mainish[i].id}: timing does not move forward (${mainish[i - 1].offsetHours}h then ${mainish[i].offsetHours}h)`);\n }\n }\n }\n if (Math.max(...offsets) < 24 * 21) warnings.push(`longest step is ${Math.round(Math.max(...offsets) / 24)} days, the client was sold a minimum 30-day journey`);\n if (!sawOptOut && sms.length) warnings.push(\"no opt-out wording found in any SMS\");\n if (!sawBooking) warnings.push(\"no booking link anywhere in this path\");\n if (p.source === \"engine\" && p.channelsAtLaunch.includes(\"sms\") && p.key === \"aged\") {\n errors.push(\"aged path must not launch with SMS until the number list has been validated\");\n }\n\n return { key: p.key, registered: true, ok: errors.length === 0, errors, warnings, steps: p.steps.length, sms: sms.length, email: p.steps.length - sms.length };\n}\n\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n if (!(await authorised(url.searchParams.get(\"k\") || \"\"))) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n const results = PATHS.map(validatePath);\n const payload = {\n at: new Date().toISOString(),\n registered: results.filter((r) => r.registered).length,\n awaitingCopy: results.filter((r) => !r.registered).map((r) => r.key),\n live: PATHS.filter((p) => p.source === \"engine\").map((p) => p.key),\n mutualExclusion: \"each path names exactly one owner, engine, ghl, or off. No path can be run by both.\",\n paths: PATHS.map((p) => ({\n key: p.key, label: p.label, sourceTag: p.sourceTag, enrolledTag: p.enrolledTag,\n source: p.source, channelsAtLaunch: p.channelsAtLaunch, steps: p.steps.length, notes: p.notes,\n validation: results.find((r) => r.key === p.key),\n })),\n };\n if (url.searchParams.get(\"f\") === \"json\" || url.searchParams.get(\"validate\") === \"1\") {\n return new Response(JSON.stringify(payload, null, 2), { headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" } });\n }\n const rows = payload.paths.map((p: any) => {\n const v = p.validation;\n const status = !v.registered ? 'awaiting copy'\n : v.ok ? 'passes every check'\n : `${v.errors.length} problem(s)`;\n return `${p.label}
${p.sourceTag}${p.source}${p.steps || \"-\"}${status}${p.notes}`;\n }).join(\"\");\n return new Response(`Nurture paths\n\n
The six nurture paths
\n
${payload.registered} of ${payload.paths.length} have copy registered. Registering the rest is NOT a copy drop: the engine reads its sequences directly and stores one position per contact, not one per path, so each additional path needs the state model, per-path tag mapping, sequence selection and precedence rules built. Days of work each, not an afternoon. This page is a registry and a validator, not the wiring. Every path is checked against the same rules before it can run.
\n${rows}
Path Owner Steps Validator Constraint that governs it
\n
Owner is the mutual-exclusion switch: engine, ghl, or off. Nothing can be run by two systems at once, that is what put a Facebook script on the website in July.
`,\n { headers: { \"content-type\": \"text/html; charset=utf-8\" } });\n}\n",[256],"16748399-6362-42ce-b87d-4d48cce38680","money-match.ts","e97430aa-943a-11f1-b975-1607ee4eb77e",689,["D",1786388054033],"// THE MONEY MATCHER. v1.0, 9 Aug 2026.\n//\n// WHAT THIS IS FOR. Kim's question, in her words: \"what are we doing with the money information that\n// comes from square back into the CRM?\" The answer today is: it lands as a note on the customer's\n// file, and nothing ever writes the amount onto the booking. The booking is the only place a report\n// can add money up from, so revenue and ROAS read zero while the money plainly exists.\n//\n// HER RULE, agreed in writing on 9 August at 10:26 PM, verbatim:\n// \"One open opportunity -> automatically assign the payment.\n// Multiple open opportunities -> staff chooses the correct one.\"\n// That is exactly what classify() implements. One card, AUTO. More than one, CHOOSE. None, ORPHAN.\n//\n// WHY THIS SHIPS AS A DRY RUN FIRST, and it is not timidity. Kristian's application also writes\n// opportunities into this same CRM; he confirmed it in writing on 7 August. Until he says whether it\n// writes monetaryValue, two systems would own one field and one would win at random. So this module\n// computes every write it WOULD make, proves the arithmetic, and writes nothing. Flipping it live is\n// one flag, after one sentence from him.\n//\n// NOTHING HERE MUTATES. There is no POST, PUT or PATCH in this file, and a test asserts that.\n\nexport type Payment = {\n id: string;\n amount: number;\n status: string;\n contactId: string | null;\n contactName: string | null;\n at: string | null;\n};\nexport type Opp = {\n id: string;\n contactId: string | null;\n name: string | null;\n monetaryValue: number;\n stage: string;\n createdAt: string | null;\n lastStageChangeAt: string | null;\n};\n\nexport type Verdict = \"AUTO\" | \"CHOOSE\" | \"ORPHAN\" | \"ALREADY_VALUED\";\nexport type Match = {\n payment: Payment;\n verdict: Verdict;\n candidates: Opp[];\n wouldWrite: { oppId: string; value: number } | null;\n why: string;\n};\n\n// A payment only counts as money if it actually completed. Pending and failed are shown to Kim\n// separately and never counted as revenue, because a report that counts a failed card as income is\n// worse than no report.\nexport const COMPLETED = \"succeeded\";\n\n// The point of sale bucket. Square sends counter sales with no customer, and this CRM files them all\n// against one nameless record, so a contactId here does NOT mean a real person was identified.\nexport const isNameless = (p: Payment) =>\n !p.contactName || p.contactName.trim().toLowerCase() === \"unknown\";\n\n// THE ONLY TWO STAGES A PAYMENT MAY EVER BE WRITTEN TO. [Added 10 Aug 2026.]\n// A contact appears on up to eight boards in this location and every empty card looks identical\n// from inside classify(). Proven live: unscoped, $4,020 of $4,685 lands on a card that is not a\n// booking, including $500 onto a Survey Requested card belonging to a customer whose real booking\n// already carries $2,395 and would correctly have been left alone. The exception list also goes\n// from 0 to 10, breaking the promise on Kim's page that nobody has to do anything.\n// Filter HERE, not in the caller: a caller that hands over every board is the normal mistake.\nexport const VALUABLE_STAGES: readonly string[] = Object.freeze([\n \"fd821b4e-bbe6-44de-b754-fa80e4823616\", // 1) Initial Lead Pipeline / Customer\n \"ae173310-f8b1-4399-acb7-ef1fc03d3697\", // 1) Initial Lead Pipeline / Won - Paid\n]);\nconst IN_SCOPE = new Set(VALUABLE_STAGES);\n\nexport function classify(payment: Payment, oppsForContact: Opp[]): Match {\n const inScope = oppsForContact.filter((o) => IN_SCOPE.has(o.stage));\n const open = inScope.filter((o) => o.monetaryValue === 0);\n const valued = inScope.filter((o) => o.monetaryValue > 0);\n\n if (isNameless(payment) || !payment.contactId) {\n return { payment, verdict: \"ORPHAN\", candidates: [], wouldWrite: null,\n why: \"no named customer on the payment, so nothing can be matched to it by any system\" };\n }\n if (inScope.length === 0) {\n return { payment, verdict: \"ORPHAN\", candidates: [], wouldWrite: null,\n why: \"the customer is named but has no booking on the Customer or Won and Paid board to put the money on\" };\n }\n if (open.length === 0 && valued.length > 0) {\n return { payment, verdict: \"ALREADY_VALUED\", candidates: valued, wouldWrite: null,\n why: \"every booking for this customer already carries a value; nothing would be overwritten\" };\n }\n if (open.length === 1) {\n return { payment, verdict: \"AUTO\", candidates: open,\n wouldWrite: { oppId: open[0].id, value: payment.amount },\n why: \"one booking open, so the money goes on it, which is the rule Kim gave\" };\n }\n return { payment, verdict: \"CHOOSE\", candidates: open, wouldWrite: null,\n why: `${open.length} bookings open for this customer, so a person picks; guessing here would invent revenue` };\n}\n\nexport type Write = { oppId: string; value: number; paymentIds: string[] };\n\n// ONE WRITE PER BOOKING, CARRYING THE SUM. [Added 10 Aug 2026.]\n// classify() is per payment because Kim's rule is per payment. The grouping belongs here, in the\n// caller's layer. Without it, a customer who pays twice toward one booking produces two writes to\n// one field and the loser's money vanishes silently. Proven live: Laurie Rubnitz, $120.00 and\n// $90.00, both resolving to opportunity 7yES6q2kajVTQIK6tEx3. Correct value $210.00.\n// The bug self seals: once a wrong value is written the next run sees a non zero field and returns\n// ALREADY_VALUED, so the lost money is unrecoverable without a manual audit.\n// Summing PRESERVES the total, so the $174,115.00 on Kim's page is the correct figure and it is the\n// code that has to catch up with the page.\nexport function planWrites(matches: Match[]): Write[] {\n const byOpp = new Map();\n for (const m of matches) {\n if (m.verdict !== \"AUTO\" || !m.wouldWrite) continue;\n const g = byOpp.get(m.wouldWrite.oppId) ?? { oppId: m.wouldWrite.oppId, amounts: [], paymentIds: [] };\n g.amounts.push(m.wouldWrite.value);\n g.paymentIds.push(m.payment.id);\n byOpp.set(g.oppId, g);\n }\n return [...byOpp.values()].map((g) => ({ oppId: g.oppId, value: sum(g.amounts), paymentIds: g.paymentIds }));\n}\n\nexport type Summary = {\n completed: { count: number; total: number };\n pending: { count: number; total: number };\n failed: { count: number; total: number };\n auto: { count: number; total: number };\n choose: { count: number; total: number };\n orphan: { count: number; total: number };\n alreadyValued: { count: number; total: number };\n coveragePct: number; // of completed money, what this would place on a booking\n valuedNow: { count: number; total: number }; // what the CRM carries today\n valuedAfter: { count: number; total: number }; // what it would carry if the AUTO set were written\n writes: { count: number; total: number }; // ACTUAL write count: one per booking, not per payment\n};\n\nconst sum = (xs: number[]) => Math.round(xs.reduce((a, b) => a + b, 0) * 100) / 100;\n\nexport function summarise(matches: Match[], all: Payment[], valuedToday: Opp[]): Summary {\n const byStatus = (s: string) => all.filter((p) => p.status === s);\n const of = (v: Verdict) => matches.filter((m) => m.verdict === v);\n const amt = (ps: { amount: number }[]) => sum(ps.map((p) => p.amount));\n const pot = (ms: Match[]) => sum(ms.map((m) => m.payment.amount));\n\n const completed = byStatus(COMPLETED);\n const auto = of(\"AUTO\"), choose = of(\"CHOOSE\"), orphan = of(\"ORPHAN\"), av = of(\"ALREADY_VALUED\");\n const writes = planWrites(matches);\n const completedTotal = amt(completed);\n const nowTotal = sum(valuedToday.map((o) => o.monetaryValue));\n\n return {\n completed: { count: completed.length, total: completedTotal },\n pending: { count: byStatus(\"pending\").length, total: amt(byStatus(\"pending\")) },\n failed: { count: byStatus(\"failed\").length, total: amt(byStatus(\"failed\")) },\n auto: { count: auto.length, total: pot(auto) },\n choose: { count: choose.length, total: pot(choose) },\n orphan: { count: orphan.length, total: pot(orphan) },\n alreadyValued: { count: av.length, total: pot(av) },\n // Honesty on the face of it: coverage is what WOULD be placed automatically, out of money that\n // actually completed. Kim is told this number before she ever sees a revenue figure, so a low\n // first month is never a surprise.\n coveragePct: completedTotal > 0 ? Math.round((pot(auto) / completedTotal) * 1000) / 10 : 0,\n valuedNow: { count: valuedToday.length, total: nowTotal },\n // counts BOOKINGS that gain a value, which is the number of writes, not the number of payments\n valuedAfter: { count: valuedToday.length + writes.length, total: sum([nowTotal, pot(auto)]) },\n writes: { count: writes.length, total: sum(writes.map((w) => w.value)) },\n };\n}\n\n// The sentence Kim reads. Generated, never typed, so it cannot drift from the numbers beside it.\nexport function plainEnglish(s: Summary): string {\n const m = (n: number) => \"$\" + n.toLocaleString(\"en-US\", { minimumFractionDigits: 2, maximumFractionDigits: 2 });\n if (s.completed.count === 0) return \"No completed Square payments were found, so there is nothing to place yet.\";\n const parts = [\n `${s.completed.count} Square payments completed, worth ${m(s.completed.total)}.`,\n s.auto.count\n ? `${s.auto.count} of them, worth ${m(s.auto.total)}, belong to a customer with exactly one booking open, so those place themselves.`\n : `None of them belong to a customer with exactly one booking open, so none place themselves yet.`,\n ];\n if (s.choose.count) parts.push(`${s.choose.count}, worth ${m(s.choose.total)}, belong to someone with more than one booking open, so a person picks which one.`);\n if (s.orphan.count) parts.push(`${s.orphan.count}, worth ${m(s.orphan.total)}, arrived with no named customer at all and can never be placed by anything.`);\n if (s.auto.count > s.writes.count) parts.push(`${s.auto.count} payments fill ${s.writes.count} bookings, because some customers paid more than once toward the same booking and those amounts are added together rather than one written over the other.`);\n parts.push(`That would take the money recorded against bookings from ${m(s.valuedNow.total)} to ${m(s.valuedAfter.total)}.`);\n return parts.join(\" \");\n}\n",[263],"1022386a-a434-4b6b-9ff2-617f3ee02113","main.ts","cdd9f676-8c34-11f1-baf4-1607ee4eb77e",691,["D",1786388055916],23,"interval","// PUPPY PATH ENGINE v1.1 — nurture automation for The Dogs Spot's puppy leads (built 27 Ju\n// (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n\n// ---- Node/tsx compatibility shim, for the local test harness only --------------------------------\n// Val.town/Deno provides a global `Deno`; this file is normally only ever loaded there. No Deno\n// runtime was available in this build/test session, so the local test harness\n// (puppy-path-engine.test.ts) imports this exact file under Node + tsx instead. The lines below define\n// a minimal stand-in ONLY when `Deno` doesn't already exist. Under real val.town execution `Deno` is\n// already defined, the `if` is false, and this block never runs — zero effect on deployed behavior.\ndeclare const Deno: { env: { get(key: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\n\n// Message copy + display constants live in ./puppy-messages.ts (split for val.town's 80k/file cap).\nimport {\n MAIN_SEQUENCE,\n BRANCH_A,\n BRANCH_B,\n PHONE_DISPLAY,\n REAL_BOOKING_URL,\n SHORT_BOOKING_LINK,\n} from \"./puppy-messages.ts\";\nimport type { Channel, MessageTemplate } from \"./puppy-messages.ts\";\n// v1.7 — slow track (taper). Copy+cadence in ./taper-messages.ts; Kim's spec (3 Aug): weekly x4,\n// fortnightly x13, then monthly forever, no asks. Same rails: reply pauses, booking exits, consent.\nimport { nextSlowTouch, monthlyTemplateFor, monthlyTemplateAvoidingRepeat } from \"./taper-messages.ts\";\n// v1.8 — Kim's real stories, one data file, additive slots. Null slots render as nothing.\nimport { resolveStories } from \"./kim-stories.ts\";\nimport { appendRunStamp } from \"./cadence.ts\";\nimport { dryScan } from \"./puppy-detect.ts\";\nimport { resolveDogName, resolveFirstName, applyMergeFields, escHtml, bodyToHtml } from \"./render.ts\";\n\n// ---- reference IDs (spec §2, all verified live this session unless noted) ------------------------\n\nconst GHL = \"https://services.leadconnectorhq.com\";\n// v1.2 — TOKEN RESOLUTION: GHL_TOKEN env var, else private blob `puppy_config`. Blob fallback\n// exists because val.town has no env-var API. Code is public; token never hardcoded. Full note:\n// NOTES-v1.4.md.\nlet TOKEN: string | undefined = Deno.env.get(\"GHL_TOKEN\");\nasync function resolveToken(): Promise {\n if (TOKEN) return TOKEN;\n try {\n const blob = await getBlobModule();\n const cfg = await blob.getJSON(\"puppy_config\").catch(() => null);\n if (cfg?.ghlToken) TOKEN = String(cfg.ghlToken);\n } catch { /* stays undefined; j() will throw a clear auth error */ }\n return TOKEN;\n}\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\nconst MAIN_PIPELINE_ID = \"FXt1UpCVBufbF0v3pfyf\"; // \"1) Initial Lead Pipeline\"\n\nconst STAGE = {\n NEW_LEAD: \"ccb18375-9aa1-40aa-a071-1581ca739533\",\n LEAD_NURTURE: \"00d0f792-38e5-444e-8995-a1be96e77d3b\",\n FREE_TRAINING_DAY: \"43ea02b4-529b-4063-b638-447414d603d2\",\n PUP_TALK: \"379d1dd2-fc18-4720-a840-e8f8ed703bb9\",\n CXLD_PUPTALK_TRAINING_DAY: \"4b5599d3-a5ad-4b8c-8388-4d5507c22fd7\",\n NO_SALE_NURTURE: \"e4511876-0adb-417b-a6be-8460a194f913\",\n DISQUALIFIED: \"38826f17-1d0e-4bac-b53e-349b67c2c79d\",\n NO_SHOW: \"f3f41e5e-edaf-4ef1-8cec-c4cccd4ec5c2\",\n ONBOARDING: \"76c72f7f-56bd-4f44-964d-aa4cbbec7d25\",\n CUSTOMER: \"fd821b4e-bbe6-44de-b754-fa80e4823616\",\n WON_PAID: \"ae173310-f8b1-4399-acb7-ef1fc03d3697\",\n} as const;\n\nconst PUP_TALK_CALENDAR_ID = \"qHuYJ0NEqzibnoqf5Cw3\";\n\n\n// v1.1: env-overridable, and now understood as the HUMAN ENROLLMENT SWITCH, not auto-discovery of a\n// pre-existing population — live check 27 Jul: zero contacts carry it (or any spelling variant), so\n// applying it is how a human puts someone on the path. READ ONLY here, never written by this engine.\nconst TAG_SOURCE_SIGNAL = Deno.env.get(\"TAG_SOURCE_SIGNAL\") || \"nurture - puppy\";\nconst TAG_ENROLLED = \"puppy-path-v1\"; // minted by this engine, applied on enrollment\n\n// v1.1 send-window + surge-hold knobs (see header addendum). Read per call, not once at module load —\n// costs nothing at this call volume and lets the offline harness flip them per test section; under\n// val.town the env is static so behavior is identical either way.\nconst sendWindowStartHour = () => Number(Deno.env.get(\"SEND_WINDOW_START_HOUR\") ?? \"9\");\nconst sendWindowEndHour = () => Number(Deno.env.get(\"SEND_WINDOW_END_HOUR\") ?? \"19\");\nconst smsSundayOk = () => (Deno.env.get(\"SMS_SUNDAY_OK\") ?? \"false\") === \"true\";\nconst enrollSurgeThreshold = () => Number(Deno.env.get(\"ENROLL_SURGE_THRESHOLD\") ?? \"25\");\nconst acknowledgeSurge = () => (Deno.env.get(\"ACKNOWLEDGE_SURGE\") ?? \"false\") === \"true\";\nconst BUSINESS_TZ = \"America/New_York\";\n\n// v1.2 hardening knobs (adversarial-review round, 30 Jul). All env-overridable, read per call.\n// MIN_SEND_GAP_HOURS: floor between two sends to the SAME contact — after an outage, overdue steps\n// space out at 2h apart instead of one per 15-min cron tick (the designed main-1→main-2 gap is\n// exactly 2h, so the default never delays an on-schedule send).\n// MAX_SENDS_PER_RUN / MAX_SENDS_PER_DAY: blast ceilings, mirroring the PupsClub val's precedent.\n// Excess due-sends defer to later runs, identical in spirit to the send-window deferral.\nconst minSendGapHours = () => Number(Deno.env.get(\"MIN_SEND_GAP_HOURS\") ?? \"2\");\nconst maxSendsPerRun = () => Number(Deno.env.get(\"MAX_SENDS_PER_RUN\") ?? \"20\");\nconst maxSendsPerDay = () => Number(Deno.env.get(\"MAX_SENDS_PER_DAY\") ?? \"50\");\n// v1.4 — how often a contact gets a full CRM check even when nothing is due. The floor under\n// due-first filtering: cheap must not become blind.\n// v1.4 — how long a reply can sit unanswered before the engine escalates and releases the contact.\nconst pauseTimeoutDays = () => Number(Deno.env.get(\"PAUSE_TIMEOUT_DAYS\") ?? \"14\");\n// v1.5 R27 — how long the engine stands down after ANY other system messages the contact. 24h is one\n// full business cycle: long enough that a customer never gets our email on the same day as a workflow\n// text, short enough that a 21-day sequence still completes near schedule (a deferred step is never\n// dropped, it waits for the next run).\nconst foreignQuietHours = () => Number(Deno.env.get(\"FOREIGN_QUIET_HOURS\") ?? \"24\");\n// Tolerance when deciding \"was that outbound ours?\" — clock skew between our send and GHL stamping\n// the conversation. Anything inside this window of our own lastSentAt is treated as ours.\nconst OURS_TOLERANCE_MS = 5 * 60 * 1000;\nconst safetySweepHours = () => Number(Deno.env.get(\"SAFETY_SWEEP_HOURS\") ?? \"24\");\nconst RUN_LOCK_TTL_MS = 10 * 60 * 1000; // a run that started >10 min ago is presumed dead\n\nconst sleep = (ms: number) => new Promise((r) => setTimeout(r, ms));\n\n// Rule 8's real signal — NOT CONFIRMED LIVE this session, see gap #2 in the header comment. Left as a\n// clearly-named constant so wiring in the real value later is a one-line change, not a re-guess.\nconst PUP_TALK_DECLINED_TAG = \"TDS-Declined\";\n\nconst HOUR_MS = 3600 * 1000;\nconst DAY_MS = 24 * HOUR_MS;\n\nconst TEST_MODE = (Deno.env.get(\"TEST_MODE\") ?? \"true\") !== \"false\";\n\n// ---- data model (spec §4, verbatim) ---------------------------------------------------------------\n\ntype PuppyStatus =\n | \"main\" | \"awaiting_appt_outcome\" | \"branch_a\" | \"branch_b\" | \"slow_track\"\n | \"paused_reply\" | \"done_booked\" | \"done_customer\" | \"done_hard_exit\"\n | \"done_soft_21d\" | \"done_branch_complete\";\n\n// v1.7 — done_soft_21d stays terminal for LEGACY pre-taper contacts only (no retroactive\n// enrollment). New 21-day completions flow into slow_track instead.\nconst TERMINAL_STATUSES = new Set([\n \"done_booked\", \"done_customer\", \"done_hard_exit\", \"done_soft_21d\", \"done_branch_complete\",\n]);\n\ntype PuppyState = {\n status: PuppyStatus;\n enteredAt: string; // ISO — main sequence start\n lastMainStepSent: number; // 0..8, count of main-sequence messages sent so far\n branchAnchorAt: string | null; // ISO — when branch A/B started\n lastBranchStepSent: number; // 0..2\n pausedForReplyAt: string | null;\n exitReason: string | null; // free text, for humans reading the blob\n lastCheckedAt: string; // ISO, updated every run this contact is touched\n lastSentAt?: string | null; // v1.2 — ISO of the last successful send to this contact (min-gap pacing)\n // v1.4 — R24: monetaryValue was read on every opportunity and thrown away, while the one question\n // the client judges a report by is \"how much revenue did that produce\". Captured at exit.\n exitValue?: number | null; // monetaryValue of the opportunity that ended the sequence\n exitStepsSent?: number | null; // how many messages they had received when they converted\n lastSentStepId?: string | null; // v1.4 — R23: the step ID, so editing copy cannot silently re-point anyone\n // v1.7 — slow track. Optional so pre-v1.7 blobs deserialize untouched; readers default them.\n slowAnchorAt?: string | null; // ISO — when the contact entered the slow track (21-day completion)\n lastSlowStepSent?: number; // count of slow-track messages sent (weekly+fortnightly+monthly)\n};\n\nfunction freshState(enteredAt: string): PuppyState {\n return {\n status: \"main\", enteredAt, lastMainStepSent: 0, branchAnchorAt: null,\n lastBranchStepSent: 0, pausedForReplyAt: null, exitReason: null, lastCheckedAt: enteredAt,\n lastSentAt: null, exitValue: null, exitStepsSent: null, lastSentStepId: null,\n slowAnchorAt: null, lastSlowStepSent: 0,\n };\n}\n\n// ---- pure helpers: timing, merge fields, rendering ------------------------------------------------\n\nfunction isDue(offsetHours: number, anchorIso: string, nowMs: number): boolean {\n return nowMs >= new Date(anchorIso).getTime() + offsetHours * HOUR_MS;\n}\n\n// v1.1 — business-local wall clock for a UTC instant. Intl with an explicit timeZone is deterministic\n// and DST-correct on both Deno and Node; no date library needed for two fields.\nfunction businessLocalParts(nowMs: number): { hour: number; weekday: string } {\n const parts = new Intl.DateTimeFormat(\"en-US\", {\n timeZone: BUSINESS_TZ,\n hour12: false,\n hour: \"2-digit\",\n weekday: \"short\",\n }).formatToParts(new Date(nowMs));\n const get = (t: string) => parts.find((p) => p.type === t)?.value ?? \"\";\n // Intl gives \"24\" for midnight under hour12:false+2-digit in some engines; normalize to 0.\n const hour = Number(get(\"hour\")) % 24;\n return { hour, weekday: get(\"weekday\") };\n}\n\n// v1.1 — send-window gate (header addendum #3). Pure given (nowMs, channel); env knobs are read once\n// at module load. Emails are allowed any day inside the hour window; SMS additionally respects the\n// closed-on-Sundays business identity unless SMS_SUNDAY_OK.\nfunction inSendWindow(channel: Channel, nowMs: number): { ok: boolean; reason: string } {\n const start = sendWindowStartHour();\n const end = sendWindowEndHour();\n const { hour, weekday } = businessLocalParts(nowMs);\n if (hour < start || hour >= end) {\n return { ok: false, reason: `outside ${start}:00–${end}:00 ${BUSINESS_TZ} (local hour ${hour})` };\n }\n if (channel === \"sms\" && weekday === \"Sun\" && !smsSundayOk()) {\n return { ok: false, reason: \"no SMS on Sundays (business closed)\" };\n }\n return { ok: true, reason: \"\" };\n}\n\ntype RenderedMessage =\n | { channel: \"email\"; subject: string; html: string }\n | { channel: \"sms\"; text: string };\n\n// Appended to every rendered message. Kept as constants so the wording is in exactly one place.\nconst SMS_OPTOUT = \"\\n\\nReply STOP to stop these texts.\";\nconst EMAIL_OPTOUT =\n \"\\n\\n---\\nYou're getting this because you inquired with The Dogs Spot. \" +\n \"Reply UNSUBSCRIBE and we'll take you off these emails.\\n\" +\n \"The Dogs Spot, Ellabell, GA\";\n\nfunction renderStep(\n step: MessageTemplate,\n contact: { firstName: string | null | undefined; companyName: string | null | undefined },\n opts: { testMode: boolean },\n): RenderedMessage {\n const prefix = opts.testMode ? \"[TEST] \" : \"\";\n // v1.8 — story slots resolve before merge fields; a null slot leaves no trace.\n const resolvedBody = applyMergeFields(resolveStories(step.bodyTemplate), contact.firstName, contact.companyName);\n\n // ---- v1.4 (2 Aug) — OPT-OUT FURNITURE, appended at render time, never written into the c\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n if (step.channel === \"email\") {\n const resolvedPreview = step.previewText\n ? applyMergeFields(step.previewText, contact.firstName, contact.companyName)\n : undefined;\n return {\n channel: \"email\",\n subject: prefix + applyMergeFields(step.subject ?? \"\", contact.firstName, contact.companyName),\n html: bodyToHtml(resolvedBody + EMAIL_OPTOUT, resolvedPreview),\n };\n }\n return { channel: \"sms\", text: prefix + resolvedBody + SMS_OPTOUT };\n}\n\n// ---- facts / decision types -------------------------------------------------------------------\n\ntype ApptFact = {\n id: string;\n startTime: number; // epoch ms\n endTime: number; // epoch ms\n appointmentStatus: string;\n deleted: boolean;\n};\n\ntype OppFact = {\n id: string;\n pipelineId: string;\n pipelineStageId: string;\n monetaryValue: number;\n status: string;\n};\n\ntype ContactFact = {\n id: string;\n firstName: string;\n companyName: string | null;\n dnd: boolean;\n};\n\ntype Facts = {\n now: number;\n contact: ContactFact;\n opportunities: OppFact[];\n pupTalkAppt: ApptFact | null;\n declinedSignal: boolean;\n hasUnansweredInboundReply: boolean;\n conversationCheckFailed: boolean;\n // v1.5 R27 — epoch ms of the newest outbound message on this contact's thread that this engine did\n // NOT send, or null when there is none / it cannot be told apart from ours. See sendGate.\n foreignOutboundAt: number | null;\n // v1.6 R28 — per-channel consent, read from GHL's dndSettings. true = this channel is opted out.\n channelBlocked: { email: boolean; sms: boolean };\n};\n\ntype Decision =\n | { kind: \"hard_exit\"; status: \"done_hard_exit\" | \"done_customer\" | \"done_booked\"; reason: string }\n | { kind: \"pause_reply\"; isNewPause: boolean }\n | { kind: \"advance_status\"; status: \"awaiting_appt_outcome\" | \"branch_a\" | \"branch_b\" | \"slow_track\"; branchAnchorAt?: string }\n | { kind: \"soft_exit_21d\" }\n | { kind: \"branch_complete\" }\n | { kind: \"send\"; sequence: \"main\" | \"branch_a\" | \"branch_b\" | \"slow\"; stepIndex: number }\n | { kind: \"skip_step\"; sequence: \"main\" | \"branch_a\" | \"branch_b\" | \"slow\"; stepIndex: number; reason: string }\n | { kind: \"skip\"; reason: string };\n\n// v1.7 — slow template for a progression index AT a moment. Weekly/fortnightly fixed by index;\n// monthly picked by the send's calendar month (July=heat, Dec=holidays — as promised to Kim).\n// Shared by decideAction AND the executor so decided and sent templates cannot drift.\nfunction slowTemplateAt(sentCount: number, nowMs: number, lastSentId?: string | null): { tpl: MessageTemplate; offsetHours: number; phase: string } {\n // v1.7.1 — clamp garbage counters (NaN/negative/string blobs) instead of letting an out-of-range\n // index fall through to \"send monthly now\"; monthly fallback only ever fires in the monthly phase.\n const clean = Math.max(0, Math.floor(Number(sentCount)) || 0);\n const n = nextSlowTouch(clean);\n const tpl = n.phase === \"monthly\" ? monthlyTemplateAvoidingRepeat(new Date(nowMs), lastSentId) : n.template!;\n return { tpl, offsetHours: n.offsetHours, phase: n.phase };\n}\n\nfunction pickPrimaryOpportunity(opps: OppFact[]): OppFact | null {\n return opps.find((o) => o.pipelineId === MAIN_PIPELINE_ID) ?? opps[0] ?? null;\n}\n\n// \"Live\" = not cancelled, not invalid, not soft-deleted. Anything else (new / confirmed / showed /\n// noshow) counts as \"they booked\" for rule 6's purposes — the outcome gets sorted out by rules 7/8.\nfunction apptIsLiveBooked(appt: ApptFact | null): boolean {\n if (!appt || appt.deleted) return false;\n return appt.appointmentStatus !== \"cancelled\" && appt.appointmentStatus !== \"invalid\";\n}\n\n// ---- the core state machine (spec §5) ---------------------------------------------------------\n// Pure function: no network, no side effects. Every rule below is evaluated in order for every call —\n// \"first match wins\" per spec, so a later rule never overrides an earlier one, and the SAME order runs\n// for every contact on every pass regardless of their current status. This is what the whole safety\n// story rests on, so it is tested exhaustively — see puppy-path-engine.test.ts.\nfunction decideAction(f: Facts, s: PuppyState): Decision {\n // Rule 1 + 2 — DND / unsubscribed. Top-level `dnd` = full opt-out, hard exit here. Since v1.6\n // (R28) per-channel opt-outs in `dndSettings` are ALSO read — not here, but as f.channelBlocked,\n // which skip-consumes steps on a blocked channel while the other channel carries on. Both layers\n // are live; this rule is the total-stop one.\n if (f.contact.dnd) {\n return { kind: \"hard_exit\", status: \"done_hard_exit\", reason: \"dnd\" };\n }\n\n const primaryOpp = pickPrimaryOpportunity(f.opportunities);\n\n // Rule 3 — Disqualified stage (human override, outranks everything below it).\n if (primaryOpp?.pipelineStageId === STAGE.DISQUALIFIED) {\n return { kind: \"hard_exit\", status: \"done_hard_exit\", reason: \"disqualified\" };\n }\n\n // Rule 4 — became a paying customer. v1.2: scans ALL opportunities, not just primary (fuzz\n // round finding; full note in NOTES-v1.4.md).\n const becameCustomer = f.opportunities.some(\n (o) => o.pipelineStageId === STAGE.CUSTOMER || o.pipelineStageId === STAGE.WON_PAID || o.monetaryValue > 0,\n );\n if (becameCustomer) {\n return { kind: \"hard_exit\", status: \"done_customer\", reason: \"became a customer\" };\n }\n\n // Rule 4b — booked something else entirely (Free Training Day). NOT an explicit numbered r\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n if (primaryOpp?.pipelineStageId === STAGE.FREE_TRAINING_DAY) {\n return { kind: \"hard_exit\", status: \"done_booked\", reason: \"booked Free Training Day — sequence ends per writing sheet §4\" };\n }\n\n // Rule 5 — inbound reply pending, or: couldn't check at all (fail closed — see header gap #1).\n // conversationCheckFailed must be checked BEFORE hasUnansweredInboundReply: an unreadable signal is\n // never treated as \"confirmed no reply,\" because that would let sends continue for someone who may\n // well have replied — exactly the failure this rule exists to prevent.\n if (f.conversationCheckFailed) {\n return { kind: \"skip\", reason: \"conversation check failed (live API scope gap) — not sending until resolved\" };\n }\n if (f.hasUnansweredInboundReply) {\n // \"First match wins\" still applies every run, so this keeps matching (and keeps blocking rule 10)\n // for as long as the reply sits unanswered — but the SIDE EFFECT (timestamping the pause, creating\n // a task) only happens the first time, guarded by isNewPause. Otherwise every run would create a\n // fresh duplicate task for the same unanswered reply.\n return { kind: \"pause_reply\", isNewPause: s.status !== \"paused_reply\" };\n }\n\n // Rule 6 — a live Pup Talk booking -> awaiting_appt_outcome. Scoped to the Pup Talk calendar\n // (branch copy is Pup-Talk-specific; FTD handled by 4b; full note in NOTES-v1.4.md).\n // v1.7.1 — the slow arm requires the appointment to POSTDATE slow entry (mirrors 6b): a stale\n // historical appointment must not yank a taper contact into branch copy.\n if (s.status === \"main\" && apptIsLiveBooked(f.pupTalkAppt)) {\n return { kind: \"advance_status\", status: \"awaiting_appt_outcome\" };\n }\n if (\n s.status === \"slow_track\" && f.pupTalkAppt && apptIsLiveBooked(f.pupTalkAppt) &&\n f.pupTalkAppt.startTime > new Date(s.slowAnchorAt ?? s.enteredAt).getTime()\n ) {\n return { kind: \"advance_status\", status: \"awaiting_appt_outcome\" };\n }\n\n // Rule 6b (v1.2) — REBOOKED while in a branch. Found independently by the adversarial revi\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n if (\n (s.status === \"branch_a\" || s.status === \"branch_b\") &&\n f.pupTalkAppt &&\n apptIsLiveBooked(f.pupTalkAppt) &&\n s.branchAnchorAt &&\n f.pupTalkAppt.startTime > new Date(s.branchAnchorAt).getTime()\n ) {\n return { kind: \"advance_status\", status: \"awaiting_appt_outcome\" };\n }\n\n // Rule 7 — awaiting -> branch_a (missed): time passed, not showed, not cancelled. Funnel-phase\n // cancellations stay parked here on purpose — the \"Cxld Pup Talk\" workflow owns that case\n // (writing sheet §4; full note in NOTES-v1.4.md). Slow-phase cancellations: rule 7s above.\n // v1.7.1 — Rule 7s: a slow-track contact who booked and then CANCELLED goes back on the taper\n // (anchor and counter intact) instead of parking in awaiting_appt_outcome forever. Scoped to\n // contacts with a slow anchor; funnel-phase cancellations still belong to the Cxld workflow.\n if (\n s.status === \"awaiting_appt_outcome\" && s.slowAnchorAt && f.pupTalkAppt &&\n f.pupTalkAppt.appointmentStatus === \"cancelled\"\n ) {\n return { kind: \"advance_status\", status: \"slow_track\" };\n }\n\n if (\n s.status === \"awaiting_appt_outcome\" &&\n f.pupTalkAppt &&\n f.now >= f.pupTalkAppt.endTime &&\n f.pupTalkAppt.appointmentStatus !== \"showed\" &&\n f.pupTalkAppt.appointmentStatus !== \"cancelled\"\n ) {\n return {\n kind: \"advance_status\",\n status: \"branch_a\",\n branchAnchorAt: new Date(f.pupTalkAppt.endTime).toISOString(),\n };\n }\n\n // Rule 8 — awaiting -> branch_b (showed, then declined). declinedSignal NOT CONFIRMED LIVE\n // (header gap #2); branchAnchorAt uses \"now\" per spec's fallback.\n if (\n s.status === \"awaiting_appt_outcome\" &&\n f.pupTalkAppt &&\n f.pupTalkAppt.appointmentStatus === \"showed\" &&\n f.declinedSignal\n ) {\n return { kind: \"advance_status\", status: \"branch_b\", branchAnchorAt: new Date(f.now).toISOString() };\n }\n\n // Rule 9 — 21-day completion. Gated on message 8 having actually SENT, not elapsed time alone\n // (else this outranks rule 10 on the very run msg 8 becomes due and it never sends —\n // NOTES-v1.4.md). Stage never auto-moved; that is Kim's call.\n if (\n s.status === \"main\" &&\n s.lastMainStepSent >= MAIN_SEQUENCE.length &&\n f.now >= new Date(s.enteredAt).getTime() + 21 * DAY_MS\n ) {\n return { kind: \"soft_exit_21d\" };\n }\n\n // Rule 9b — branch exhausted -> done_branch_complete (the type's own terminal; a contact must\n // not sit re-evaluated forever with nothing left to send). NOTES-v1.4.md.\n if (s.status === \"branch_a\" && s.lastBranchStepSent >= BRANCH_A.length) {\n return { kind: \"branch_complete\" };\n }\n if (s.status === \"branch_b\" && s.lastBranchStepSent >= BRANCH_B.length) {\n return { kind: \"branch_complete\" };\n }\n\n // Rule 10 — otherwise, send whatever's next due. v1.1: a due step additionally waits for the send\n // window (inSendWindow). v1.2: and for the per-contact min-gap floor — after an outage, several\n // overdue steps space out ~2h apart instead of one per cron tick. Every deferral leaves state\n // untouched, so a later run simply picks it up.\n const sendGate = (channel: Channel): { ok: boolean; reason: string } => {\n const w = inSendWindow(channel, f.now);\n if (!w.ok) return w;\n if (s.lastSentAt) {\n const gapMs = minSendGapHours() * HOUR_MS;\n const sinceLast = f.now - new Date(s.lastSentAt).getTime();\n // v1.7 — sinceLast >= 0 guard (mirrors R27): a future-dated lastSentAt (clock skew, restored\n // blob) must not freeze the contact until that future date; negative elapsed = ignore the gap.\n if (sinceLast >= 0 && sinceLast < gapMs) {\n return { ok: false, reason: `min send gap (${minSendGapHours()}h) not elapsed — last send ${(sinceLast / HOUR_MS).toFixed(1)}h ago` };\n }\n }\n // R27 (v1.5) — FOREIGN-SENDER QUIET PERIOD: an outbound newer than ours means another system\n // owns this contact right now; stand down. Fails OPEN. Full rationale: NOTES-v1.4.md.\n if (f.foreignOutboundAt != null) {\n const quietMs = foreignQuietHours() * HOUR_MS;\n const since = f.now - f.foreignOutboundAt;\n if (since >= 0 && since < quietMs) {\n return {\n ok: false,\n reason: `another system messaged this contact ${(since / HOUR_MS).toFixed(1)}h ago — quiet period ${foreignQuietHours()}h`,\n };\n }\n }\n return { ok: true, reason: \"\" };\n };\n if (s.status === \"main\" && s.lastMainStepSent < MAIN_SEQUENCE.length) {\n const step = MAIN_SEQUENCE[s.lastMainStepSent];\n if (isDue(step.offsetHours, s.enteredAt, f.now)) {\n const g = sendGate(step.channel);\n if (!g.ok) return { kind: \"skip\", reason: `main #${s.lastMainStepSent + 1} due but deferred: ${g.reason}` };\n if (f.channelBlocked[step.channel]) {\n return { kind: \"skip_step\", sequence: \"main\", stepIndex: s.lastMainStepSent, reason: `opted out of ${step.channel} — step consumed, not sent` };\n }\n return { kind: \"send\", sequence: \"main\", stepIndex: s.lastMainStepSent };\n }\n return { kind: \"skip\", reason: `next main step (#${s.lastMainStepSent + 1}) not due yet` };\n }\n if (s.status === \"branch_a\" && s.lastBranchStepSent < BRANCH_A.length && s.branchAnchorAt) {\n const step = BRANCH_A[s.lastBranchStepSent];\n if (isDue(step.offsetHours, s.branchAnchorAt, f.now)) {\n const g = sendGate(step.channel);\n if (!g.ok) return { kind: \"skip\", reason: `branch A step due but deferred: ${g.reason}` };\n if (f.channelBlocked[step.channel]) {\n return { kind: \"skip_step\", sequence: \"branch_a\", stepIndex: s.lastBranchStepSent, reason: `opted out of ${step.channel} — step consumed, not sent` };\n }\n return { kind: \"send\", sequence: \"branch_a\", stepIndex: s.lastBranchStepSent };\n }\n return { kind: \"skip\", reason: \"next branch A step not due yet\" };\n }\n if (s.status === \"branch_b\" && s.lastBranchStepSent < BRANCH_B.length && s.branchAnchorAt) {\n const step = BRANCH_B[s.lastBranchStepSent];\n if (isDue(step.offsetHours, s.branchAnchorAt, f.now)) {\n const g = sendGate(step.channel);\n if (!g.ok) return { kind: \"skip\", reason: `branch B step due but deferred: ${g.reason}` };\n if (f.channelBlocked[step.channel]) {\n return { kind: \"skip_step\", sequence: \"branch_b\", stepIndex: s.lastBranchStepSent, reason: `opted out of ${step.channel} — step consumed, not sent` };\n }\n return { kind: \"send\", sequence: \"branch_b\", stepIndex: s.lastBranchStepSent };\n }\n return { kind: \"skip\", reason: \"next branch B step not due yet\" };\n }\n\n // v1.7 — Rule 10s: slow track. Indefinite by design, so no exhaustion exit — the exits are the\n // rules above (reply, booking, customer, DND). Anchor falls back to enteredAt if a legacy blob\n // lands here without slowAnchorAt.\n if (s.status === \"slow_track\") {\n const sentCount = Math.max(0, Math.floor(Number(s.lastSlowStepSent)) || 0);\n const anchor = s.slowAnchorAt ?? s.enteredAt;\n const { tpl, offsetHours, phase } = slowTemplateAt(sentCount, f.now, s.lastSentStepId);\n if (isDue(offsetHours, anchor, f.now)) {\n const g = sendGate(tpl.channel);\n if (!g.ok) return { kind: \"skip\", reason: `slow #${sentCount + 1} (${phase}) due but deferred: ${g.reason}` };\n if (f.channelBlocked[tpl.channel]) {\n return { kind: \"skip_step\", sequence: \"slow\", stepIndex: sentCount, reason: `opted out of ${tpl.channel} — slow step consumed, not sent` };\n }\n return { kind: \"send\", sequence: \"slow\", stepIndex: sentCount };\n }\n return { kind: \"skip\", reason: `next slow touch (#${sentCount + 1}, ${phase}) not due yet` };\n }\n\n return { kind: \"skip\", reason: `status ${s.status} has nothing to evaluate` };\n}\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.\nfunction applyDecision(decision: Decision, s: PuppyState, nowIso: string): PuppyState {\n const next: PuppyState = { ...s, lastCheckedAt: nowIso };\n switch (decision.kind) {\n case \"hard_exit\":\n next.status = decision.status;\n next.exitReason = decision.reason;\n return next;\n case \"pause_reply\":\n next.status = \"paused_reply\";\n if (decision.isNewPause) {\n next.pausedForReplyAt = nowIso;\n next.exitReason = \"human reply pending\";\n }\n return next;\n case \"advance_status\":\n next.status = decision.status;\n if (decision.branchAnchorAt) next.branchAnchorAt = decision.branchAnchorAt;\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 if (decision.status === \"branch_a\" || decision.status === \"branch_b\") next.lastBranchStepSent = 0;\n // v1.7.1 — returning to slow_track (cancelled booking) keeps slowAnchorAt and\n // lastSlowStepSent untouched: the taper resumes where it left off.\n return next;\n case \"soft_exit_21d\":\n // v1.7 — 21-day completion now hands the contact to the slow track (Kim's taper);\n // done_soft_21d remains in the type for legacy blobs only.\n next.status = \"slow_track\";\n next.slowAnchorAt = nowIso;\n next.lastSlowStepSent = 0;\n next.exitReason = \"21-day sequence complete — moved to slow track\";\n return next;\n case \"branch_complete\":\n next.status = \"done_branch_complete\";\n next.exitReason = \"branch sequence complete, no reply\";\n return next;\n case \"send\":\n if (decision.sequence === \"main\") next.lastMainStepSent = s.lastMainStepSent + 1;\n else if (decision.sequence === \"slow\") next.lastSlowStepSent = (s.lastSlowStepSent ?? 0) + 1;\n else next.lastBranchStepSent = s.lastBranchStepSent + 1;\n next.lastSentAt = nowIso; // v1.2 — feeds the min-gap pacing floor\n return next;\n case \"skip_step\":\n // v1.6 R28 — the step is consumed, not deferred. Deferring a step whose channel the contact\n // has opted out of would stall that contact forever on a message that can never legally send.\n // lastSentAt is deliberately NOT set: nothing went out, so nothing should start the pacing clock.\n if (decision.sequence === \"main\") next.lastMainStepSent = s.lastMainStepSent + 1;\n else if (decision.sequence === \"slow\") next.lastSlowStepSent = (s.lastSlowStepSent ?? 0) + 1;\n else next.lastBranchStepSent = s.lastBranchStepSent + 1;\n return next;\n case \"skip\":\n return next;\n }\n}\n\n// ---- IO layer: GHL fetch helper (identical shape to the PupsClub val) -----------------------------\n\nasync function j(url: string, ver: string, init?: RequestInit) {\n const tok = await resolveToken(); // v1.2 — env var, else private puppy_config blob (see header note)\n const r = await fetch(url, {\n ...init,\n headers: {\n Authorization: `Bearer ${tok}`,\n Version: ver,\n \"Content-Type\": \"application/json\",\n ...(init?.headers ?? {}),\n },\n });\n if (!r.ok) throw new Error(`${r.status} ${url.split(\"?\")[0]} ${(await r.text()).slice(0, 200)}`);\n return r.json();\n}\n\n// ---- blob state (dynamic import, see Node/tsx shim note above) ------------------------------------\n\nasync function getBlobModule() {\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 // @ts-expect-error — remote Deno URL specifier; unresolvable (by design) under tsc/Node's module\n // resolution, only ever actually imported at runtime inside a real Deno/val.town environment.\n const mod = await import(\"https://esm.town/v/std/blob\");\n return (mod as any).blob;\n}\n\nasync function loadAllState(): Promise> {\n const blob = await getBlobModule();\n return (await blob.getJSON(\"puppy_state\").catch(() => null)) ?? {};\n}\nasync function saveAllState(state: Record) {\n const blob = await getBlobModule();\n await blob.setJSON(\"puppy_state\", state);\n}\n// v1.8.2. Each run records its own timestamp so the dashboard can report the cadence it OBSERVES\n// rather than one a human typed. See cadence.ts for why, and for the shared shape.\nasync function saveReport(report: any) {\n const blob = await getBlobModule();\n let history: string[] = [];\n try {\n history = appendRunStamp(await blob.getJSON(\"puppy_run_state\").catch(() => null),\n typeof report?.ts === \"string\" ? report.ts : new Date().toISOString());\n } catch { /* bookkeeping is a nicety; never fail a run over it */ }\n await blob.setJSON(\"puppy_run_state\", { ...(report as object), history });\n}\nasync function saveLastError(err: unknown) {\n const blob = await getBlobModule();\n await blob.setJSON(\"puppy_last_error\", err);\n}\n\n// ---- v1.1: journal + summary ----------------------------------------------------------------------\n\ntype JournalRow = { ts: string; contactId: string | null; event: string; detail: string; test?: boolean };\n\n// Appends this run's rows and returns the full merged journal (capped at the newest 2000 rows) so the\n// caller can build the summary from complete history without a second blob read.\nasync function appendJournal(rows: JournalRow[]): Promise {\n const blob = await getBlobModule();\n const existing: JournalRow[] = (await blob.getJSON(\"puppy_journal\").catch(() => null)) ?? [];\n const merged = [...existing, ...rows].slice(-2000);\n if (rows.length) await blob.setJSON(\"puppy_journal\", merged);\n return merged;\n}\n\n// Pure — aggregate the numbers Kim's eventual 30-day report needs. Journal-derived counts\n// (bookedDuringPath, customersDuringPath, sendsByStep) survive state pruning; state-derived counts\n// reflect the current population.\nfunction buildSummary(\n state: Record,\n journal: JournalRow[],\n lastRun: { at: string; testMode: boolean; sent: number; failed: number; enrolled: number },\n) {\n const byStatus: Record = {};\n for (const s of Object.values(state)) byStatus[s.status] = (byStatus[s.status] ?? 0) + 1;\n const sendsByStep: Record = {};\n let bookedDuringPath = 0;\n let customersDuringPath = 0;\n let pausedForHuman = 0;\n let surgeHolds = 0;\n for (const r of journal) {\n if (r.event === \"sent\") sendsByStep[r.detail] = (sendsByStep[r.detail] ?? 0) + 1;\n else if (r.event === \"advance_status\" && r.detail === \"awaiting_appt_outcome\") bookedDuringPath++;\n else if (r.event === \"hard_exit\" && r.detail === \"became a customer\") customersDuringPath++;\n else if (r.event === \"pause_reply\") pausedForHuman++;\n else if (r.event === \"enrollment_surge_hold\") surgeHolds++;\n }\n return {\n at: lastRun.at,\n v: \"1.2\",\n lastRun,\n activeByStatus: byStatus,\n totalTracked: Object.keys(state).length,\n sendsByStep,\n bookedDuringPath,\n customersDuringPath,\n pausedForHuman,\n surgeHolds,\n };\n}\n\nasync function saveSummary(summary: unknown) {\n const blob = await getBlobModule();\n await blob.setJSON(\"puppy_summary\", summary);\n}\n\n// Pure — v1.1 state hygiene: drop terminal entries untouched for 60+ days. History stays in the\n// journal; the puppy-path-v1 tag still prevents re-enrollment of a pruned contact.\nfunction pruneState(state: Record, nowMs: number): { kept: Record; prunedIds: string[] } {\n const kept: Record = {};\n const prunedIds: string[] = [];\n for (const [id, s] of Object.entries(state)) {\n const stale = TERMINAL_STATUSES.has(s.status) && nowMs - new Date(s.lastCheckedAt).getTime() > 60 * DAY_MS;\n if (stale) prunedIds.push(id);\n else kept[id] = s;\n }\n return { kept, prunedIds };\n}\n\n// Pure — v1.1 enrollment gate (header addendum #1/#2). Given this run's un-enrolled tag matches,\n// decide who enrolls. Over-threshold = bulk-tag accident suspected: enroll nobody, hold until a human\n// clears it (ACKNOWLEDGE_SURGE=true) or the candidate count drops back under the threshold.\nfunction selectEnrollable(\n candidates: T[],\n surgeThreshold: number,\n surgeAcknowledged: boolean,\n): { enroll: T[]; surgeHeld: boolean } {\n if (candidates.length > surgeThreshold && !surgeAcknowledged) {\n return { enroll: [], surgeHeld: true };\n }\n return { enroll: candidates, surgeHeld: false };\n}\n\n// ---- IO layer: GHL reads --------------------------------------------------------------------------\n\nasync function getContact(contactId: string): Promise {\n const r = await j(`${GHL}/contacts/${contactId}`, \"2021-07-28\");\n return r.contact;\n}\n\nasync function getOpenOpportunities(contactId: string): Promise {\n const r = await j(`${GHL}/opportunities/search?location_id=${LOC}&contact_id=${contactId}&limit=10`, \"2021-07-28\");\n return (r.opportunities ?? []).map((o: any) => ({\n id: o.id,\n pipelineId: o.pipelineId,\n pipelineStageId: o.pipelineStageId,\n monetaryValue: o.monetaryValue ?? 0,\n status: o.status,\n }));\n}\n\n// ---- v1.3 (2 Aug 2026) — R19: THE ENROLMENT-SCAN QUOTA FIX -----------------------------\n// (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\nconst EXIT_STAGES = [\n \"fd821b4e-bbe6-44de-b754-fa80e4823616\", // Customer\n \"ae173310-f8b1-4399-acb7-ef1fc03d3697\", // Won - Paid\n \"38826f17-1d0e-4bac-b53e-349b67c2c79d\", // Disqualified\n \"43ea02b4-529b-4063-b638-447414d603d2\", // Free Training Day\n];\n\nasync function fetchExitOppIndex(): Promise | null> {\n const index = new Map();\n try {\n for (const stage of EXIT_STAGES) {\n let after: any = null, afterId: any = null, pages = 0;\n while (pages < 12) { // hard ceiling: a runaway page-walk must never be the thing that breaks a run\n let u = `${GHL}/opportunities/search?location_id=${LOC}&pipeline_id=${MAIN_PIPELINE_ID}` +\n `&pipeline_stage_id=${stage}&limit=100`;\n if (after != null) u += `&startAfter=${after}&startAfterId=${afterId}`;\n const r = await j(u, \"2021-07-28\");\n const ops = r.opportunities ?? [];\n if (!ops.length) break;\n for (const o of ops) {\n if (!o.contactId) continue;\n const fact: OppFact = {\n id: o.id,\n pipelineId: o.pipelineId,\n pipelineStageId: o.pipelineStageId,\n monetaryValue: o.monetaryValue ?? 0,\n status: o.status,\n };\n const prev = index.get(o.contactId);\n if (prev) prev.push(fact); else index.set(o.contactId, [fact]);\n }\n pages++;\n after = r.meta?.startAfter; afterId = r.meta?.startAfterId;\n if (!after) break;\n }\n }\n return index;\n } catch {\n // Fail to null, never to an empty map. An empty map would read as \"nobody is a customer\" and\n // could enrol someone who has already bought — the exact mistake this check exists to prevent.\n // Null makes the caller fall back to the per-contact read it used before.\n return null;\n }\n}\n\n// v1.1 (header addendum #5): the Pup Talk calendar's ±90d window holds ~143 events (measured live\n// 27 Jul); fetching it per contact re-downloaded all of them for every active contact every run.\n// Now: one fetch per run, indexed by contactId, latest non-deleted event per contact.\nasync function fetchPupTalkApptIndex(): Promise> {\n const now = Date.now();\n const windowStart = now - 90 * DAY_MS; // look back far enough to still catch a recently-missed appt\n const windowEnd = now + 90 * DAY_MS;\n const r = await j(\n `${GHL}/calendars/events?locationId=${LOC}&calendarId=${PUP_TALK_CALENDAR_ID}&startTime=${windowStart}&endTime=${windowEnd}`,\n \"2021-04-15\",\n );\n const index = new Map();\n for (const e of r.events ?? []) {\n if (!e.contactId || e.deleted) continue;\n const fact: ApptFact = {\n id: e.id,\n startTime: new Date(e.startTime).getTime(),\n endTime: new Date(e.endTime).getTime(),\n appointmentStatus: e.appointmentStatus,\n deleted: !!e.deleted,\n };\n const prev = index.get(e.contactId);\n if (!prev || fact.startTime > prev.startTime) index.set(e.contactId, fact);\n }\n return index;\n}\n\n// ---- v1.6 R28 (2 Aug 2026) — PER-CHANNEL CONSENT ----------------------------------------------\n// Keyed BY CHANNEL, not the top-level dnd boolean. `status` is consent; `message` is a delivery\n// diagnostic and must NOT be read as consent. Blocks per channel, never a hard exit.\n// R31: `active` = DND ON = BLOCK. `inactive` = free to contact. Was inverted. See NOTES-v1.4.md.\nfunction readChannelConsent(contact: any): { email: boolean; sms: boolean } {\n const ds = contact?.dndSettings;\n const blocked = (key: string): boolean => {\n const entry = ds?.[key];\n if (!entry) return false; // no per-channel record at all = no per-channel opt-out\n const status = String(entry.status ?? \"\").toLowerCase();\n // Allow-list the two states that mean \"go\", so an unrecognised status fails CLOSED.\n return status !== \"\" && status !== \"inactive\";\n };\n return {\n // GHL keys these by channel name. SMS and RCS are both text to the recipient, so either one\n // being switched off means we do not text them.\n sms: blocked(\"SMS\") || blocked(\"RCS\"),\n email: blocked(\"Email\"),\n };\n}\n\n// See header gap #1. Fails closed: any error, or a response shape this code doesn't recognize, is\n// reported as conversationCheckFailed=true — never silently treated as \"no reply.\"\nasync function getReplyStatus(\n contactId: string,\n enteredAtIso: string,\n): Promise<{ hasUnansweredInboundReply: boolean; conversationCheckFailed: boolean; lastOutboundAt: number | null }> {\n // v1.5 R27: lastOutboundAt rides along on the SAME request that rule 5 already makes — the collision\n // guard costs zero extra API calls. It is the conversation's own lastMessageDate, returned only when\n // that last message was outbound; the caller decides whether it was ours.\n let lastOutboundAt: number | null = null;\n try {\n const r = await j(`${GHL}/conversations/search?locationId=${LOC}&contactId=${contactId}&limit=1`, \"2021-07-28\");\n const convo = (r.conversations ?? [])[0];\n if (!convo) return { hasUnansweredInboundReply: false, conversationCheckFailed: false, lastOutboundAt };\n {\n const d = convo.lastMessageDirection ?? convo.direction ?? null;\n const ts = convo.lastMessageDate ?? convo.lastMessageDateTime ?? null;\n if (d === \"outbound\" && ts != null) {\n const n = new Date(ts).getTime();\n if (!Number.isNaN(n)) lastOutboundAt = n;\n }\n }\n // Field name NOT independently proven this session (the 401 blocked confirming it) — tryin\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n const direction = convo.lastMessageDirection ?? convo.direction ?? null;\n if (direction !== \"inbound\" && direction !== \"outbound\") {\n return { hasUnansweredInboundReply: false, conversationCheckFailed: true, lastOutboundAt };\n }\n // v1.4 — R21: Chloe, Ava and 165 workflows all send. A customer replies, an automated outbound\n // lands seconds later, the direction field flips, and the engine reads 'no reply'. unreadCount is\n // the second signal: outbound does NOT clear it, so an unread thread means somebody wrote in and\n // nobody looked — which must block a send whatever the newest message was. See NOTES-v1.4.md.\n\n const unread = Number(convo.unreadCount ?? 0);\n if (direction === \"outbound\") {\n if (unread > 0) {\n return { hasUnansweredInboundReply: true, conversationCheckFailed: false, lastOutboundAt };\n }\n return { hasUnansweredInboundReply: false, conversationCheckFailed: false, lastOutboundAt };\n }\n const lastTsRaw = convo.lastMessageDate ?? convo.lastMessageDateTime ?? convo.dateUpdated ?? null;\n const lastTs = lastTsRaw != null ? new Date(lastTsRaw).getTime() : NaN;\n if (!Number.isNaN(lastTs) && lastTs < new Date(enteredAtIso).getTime()) {\n // Pre-enrollment history — EXCEPT if it is still unread, in which case somebody wrote in and\n // nobody has answered them, which outranks how old it is.\n if (Number(convo.unreadCount ?? 0) > 0) return { hasUnansweredInboundReply: true, conversationCheckFailed: false, lastOutboundAt };\n return { hasUnansweredInboundReply: false, conversationCheckFailed: false, lastOutboundAt };\n }\n return { hasUnansweredInboundReply: true, conversationCheckFailed: false, lastOutboundAt };\n } catch {\n return { hasUnansweredInboundReply: false, conversationCheckFailed: true, lastOutboundAt };\n }\n}\n\n// ---- IO layer: GHL writes (all proven live this session, see PUPPY-PATH-TEST-REPORT.md) -----------\n\n// v1.7 hardening (6 Aug): in practice mode the SENDERS THEMSELVES refuse anyone except the one\n// sanctioned test record, so safety no longer rests only on enrollment scoping upstream. Fails\n// closed: until resolveTestDummy() has run and set this, practice mode can send to nobody at all.\nlet SANCTIONED_TEST_CONTACT: string | null = null;\nfunction assertSendAllowed(contactId: string, channel: string) {\n if (TEST_MODE && contactId !== SANCTIONED_TEST_CONTACT) {\n throw new Error(`practice mode: refusing ${channel} to ${contactId}; only the sanctioned test record may be messaged`);\n }\n}\n\nasync function sendSms(contactId: string, text: string) {\n assertSendAllowed(contactId, \"sms\");\n // Proven shape, copied verbatim from the PupsClub val, which sends real SMS in production today.\n return j(`${GHL}/conversations/messages`, \"2021-04-15\", {\n method: \"POST\",\n body: JSON.stringify({ type: \"SMS\", contactId, message: text }),\n });\n}\n\nasync function sendEmail(contactId: string, subject: string, html: string) {\n assertSendAllowed(contactId, \"email\");\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 return j(`${GHL}/conversations/messages`, \"2021-04-15\", {\n method: \"POST\",\n body: JSON.stringify({ type: \"Email\", contactId, subject, html }),\n });\n}\n\nasync function addTag(contactId: string, tag: string) {\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 return j(`${GHL}/contacts/${contactId}/tags`, \"2021-07-28\", {\n method: \"POST\",\n body: JSON.stringify({ tags: [tag] }),\n });\n}\n\nasync function createTask(contactId: string, title: string, body: string) {\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 return j(`${GHL}/contacts/${contactId}/tasks`, \"2021-07-28\", {\n method: \"POST\",\n body: JSON.stringify({ title, body, dueDate: new Date().toISOString(), completed: false }),\n });\n}\n\nasync function resolveTestDummy(): Promise<{ id: string; firstName: string; companyName: string | null }> {\n // TEST_MODE's one sanctioned contact (spec §8). +10000000000 is not a working number in any real\n // numbering plan — chosen specifically so an accidental SMS send during testing cannot reach a real\n // person, while still being a syntactically valid phone value GHL will accept on a contact record.\n const up = await j(`${GHL}/contacts/upsert`, \"2021-07-28\", {\n method: \"POST\",\n body: JSON.stringify({\n locationId: LOC,\n firstName: \"ZZTEST\",\n lastName: \"PuppyPath-Dummy\",\n email: \"aizhigitovamir@gmail.com\",\n phone: \"+10000000000\",\n }),\n });\n const c = up.contact;\n SANCTIONED_TEST_CONTACT = c.id;\n return { id: c.id, firstName: c.firstName, companyName: c.companyName ?? null };\n}\n\n// ---- orchestration: cron() (default export — the val.town entry point) ----------------------------\n\nexport default async function cron() {\n const out: any = {\n ok: true,\n v: \"1.7.1\", // slow track + R27/R28, plus the adversarial-review fixes (stale-appt guard, cancel->resume, monthly dedup, dueCheck)\n\n ts: new Date().toISOString(), // v1.2 — lets the watchdog's staleness check actually work\n testMode: TEST_MODE,\n enrolled: 0,\n sent: 0,\n failed: 0,\n skipped: 0,\n log: [] as string[],\n };\n const journal: JournalRow[] = [];\n const jrow = (contactId: string | null, event: string, detail: string) =>\n journal.push({ ts: new Date().toISOString(), contactId, event, detail, ...(TEST_MODE ? { test: true } : {}) });\n\n // v1.2 — best-effort run lock. Blob storage has no compare-and-swap, so this can't be a perfect\n // mutex, but it shrinks the overlap window (manual trigger colliding with the schedule, or a slow\n // run) from \"the whole run\" to milliseconds. A lock older than RUN_LOCK_TTL_MS is a dead run's\n // leftovers and is ignored.\n const blob = await getBlobModule();\n\n // ---- KILL SWITCH (v1.3). Checked first; fails OPEN. Full note in NOTES-v1.4.md.\n try {\n const kill = await blob.getJSON(\"nurture_kill\").catch(() => null);\n if (kill?.stopped) {\n out.ok = true;\n out.killed = true;\n out.log.push(`STOPPED by kill switch (set ${kill.at ?? \"unknown\"}) — no contact examined this tick`);\n await blob.setJSON(\"puppy_run_state\", out).catch(() => {});\n console.log(\"PUPPYPATH\", JSON.stringify(out));\n return out;\n }\n } catch { /* fail open — see note above */ }\n\n const lock = await blob.getJSON(\"puppy_run_lock\").catch(() => null);\n if (lock?.startedAt && Date.now() - new Date(lock.startedAt).getTime() < RUN_LOCK_TTL_MS) {\n out.log.push(`another run appears active (lock from ${lock.startedAt}) — skipping this tick`);\n console.log(\"PUPPYPATH\", JSON.stringify(out));\n return out;\n }\n await blob.setJSON(\"puppy_run_lock\", { startedAt: new Date().toISOString() }).catch(() => {});\n\n try {\n const state = await loadAllState();\n // v1.2 — existing journal loaded up front: the daily send cap counts today's already-journaled\n // live sends, so the ceiling holds across runs, not just within one.\n const priorJournal: JournalRow[] = (await blob.getJSON(\"puppy_journal\").catch(() => null)) ?? [];\n const todayPrefix = new Date().toISOString().slice(0, 10);\n let sentToday = priorJournal.filter(\n (r) => r.event === \"sent\" && r.ts.slice(0, 10) === todayPrefix && !r.test,\n ).length;\n // v1.1 (addendum #5): one calendar fetch per run, shared by enrollment guard + per-contact facts.\n // WRAPPED 10 Aug 2026. This was bare, and it runs BEFORE the TEST_MODE branch, so one 401 from\n // the calendar endpoint aborted the entire run before a single contact was examined. That has\n // already happened once, stored as lastError on 2026-07-30. An empty index degrades the Pup Talk\n // check; an exception here stops everything.\n let apptIndex: Map;\n try {\n apptIndex = await fetchPupTalkApptIndex();\n } catch (e) {\n apptIndex = new Map();\n out.log.push(`appt index unavailable, continuing without it: ${String((e as Error)?.message ?? e).slice(0, 120)}`);\n }\n let contactIds: string[];\n // v1.2 — opportunities fetched during enrollment eligibility are reused when the same contact is\n // processed later in this run, instead of a redundant second API call.\n const oppsCache = new Map();\n let skippedNotDue = 0; // v1.4 — how many contacts cost zero API calls this run\n\n // v1.9 — THE DRY TAGGING PASS. Runs in BOTH modes on purpose; applies nothing, ever.\n // Full note, including why it was dead for three deploys: NOTES-v1.4.md, \"the dry tagging pass\".\n try {\n const recent = await j(`${GHL}/contacts/?locationId=${LOC}&limit=100`, \"2021-07-28\");\n await blob.setJSON(\"tag_candidates\", dryScan(recent?.contacts ?? [], new Date().toISOString()));\n } catch { /* a dry scan is never worth failing a run over */ }\n\n if (TEST_MODE) {\n // Spec §8: skip real discovery entirely, operate ONLY on the one sanctioned dummy.\n const dummy = await resolveTestDummy();\n contactIds = [dummy.id];\n if (!state[dummy.id]) {\n state[dummy.id] = freshState(new Date().toISOString());\n await addTag(dummy.id, TAG_ENROLLED).catch((e) =>\n out.log.push(`tag failed on dummy: ${String(e).slice(0, 120)}`)\n );\n out.enrolled++;\n out.log.push(`TEST_MODE: enrolled dummy ${dummy.id}`);\n jrow(dummy.id, \"enrolled\", \"test dummy\");\n }\n } else {\n // v1.1 enrollment: the source tag is the HUMAN enrollment switch. Blocks only what makes\n // enrollment WRONG (existing customer, live booking). DND enforced by rule 1 first pass.\n // Surge hold guards bulk tagging — selectEnrollable. Full note: NOTES-v1.4.md.\n const found = await j(`${GHL}/contacts/search`, \"2021-07-28\", {\n method: \"POST\",\n body: JSON.stringify({\n locationId: LOC,\n pageLimit: 100,\n filters: [{ field: \"tags\", operator: \"contains_set\", value: [TAG_SOURCE_SIGNAL] }],\n }),\n });\n // v1.2 — surface pagination truncation instead of silently ignoring candidates beyond page 1\n // (only reachable when a human pushes a >100 bulk batch through with ACKNOWLEDGE_SURGE).\n const totalTagged = found.total ?? (found.contacts ?? []).length;\n if (totalTagged > (found.contacts ?? []).length) {\n out.log.push(\n `WARNING: ${totalTagged} contacts carry '${TAG_SOURCE_SIGNAL}' but only ${(found.contacts ?? []).length} ` +\n `fit one page — the rest enroll on later runs as earlier ones get the puppy-path-v1 tag`,\n );\n }\n const rawCandidates: any[] = (found.contacts ?? []).filter(\n (c: any) => !(c.tags ?? []).includes(TAG_ENROLLED) && !state[c.id],\n );\n const surgeThreshold = enrollSurgeThreshold();\n const { enroll, surgeHeld } = selectEnrollable(rawCandidates, surgeThreshold, acknowledgeSurge());\n if (surgeHeld) {\n out.log.push(\n `ENROLLMENT SURGE HELD: ${rawCandidates.length} un-enrolled '${TAG_SOURCE_SIGNAL}' contacts found in one run ` +\n `(threshold ${surgeThreshold}) — bulk tagging suspected, enrolling NOBODY until a human clears it ` +\n `(remove the bulk tags, or set ACKNOWLEDGE_SURGE=true). Already-enrolled contacts continue normally.`,\n );\n jrow(null, \"enrollment_surge_hold\", `${rawCandidates.length} candidates vs threshold ${surgeThreshold}`);\n }\n // v1.3 / R19 — one indexed read for the whole candidate set instead of one call each.\n const exitOppIndex = enroll.length ? await fetchExitOppIndex() : null;\n if (enroll.length) {\n out.log.push(\n exitOppIndex\n ? `exit-opp index built (${exitOppIndex.size} contacts across ${EXIT_STAGES.length} stages) — ${enroll.length} candidate(s) screened without per-contact calls`\n : `exit-opp index unavailable — falling back to per-contact reads for ${enroll.length} candidate(s)`,\n );\n }\n for (const c of enroll) {\n let opps: OppFact[];\n if (exitOppIndex) {\n opps = exitOppIndex.get(c.id) ?? [];\n } else {\n await sleep(120); // v1.2 — pacing: GHL fails 401/403 (not 429) over 100 req/10s\n opps = await getOpenOpportunities(c.id);\n }\n oppsCache.set(c.id, opps);\n // Across ALL opportunities, not just primary — spec's \"no opportunity showing Customer/Won-Paid\"\n // reading, and the account's own one-opportunity-per-contact rule makes this a cheap superset.\n const alreadyCustomer = opps.some(\n (o) => o.pipelineStageId === STAGE.CUSTOMER || o.pipelineStageId === STAGE.WON_PAID || o.monetaryValue > 0,\n );\n if (alreadyCustomer) {\n out.log.push(`${c.id}: tagged but already a customer — not enrolled`);\n jrow(c.id, \"enroll_refused\", \"already a customer\");\n continue;\n }\n const appt = apptIndex.get(c.id) ?? null;\n if (appt && apptIsLiveBooked(appt)) {\n out.log.push(`${c.id}: tagged but already has a live Pup Talk booking — not enrolled`);\n jrow(c.id, \"enroll_refused\", \"live booking already exists\");\n continue;\n }\n state[c.id] = freshState(new Date().toISOString());\n await addTag(c.id, TAG_ENROLLED).catch((e) => out.log.push(`tag failed on ${c.id}: ${String(e).slice(0, 120)}`));\n out.enrolled++;\n out.log.push(`enrolled ${c.id}`);\n jrow(c.id, \"enrolled\", `via tag '${TAG_SOURCE_SIGNAL}'`);\n }\n contactIds = Object.keys(state);\n }\n\n for (const contactId of contactIds) {\n const s = state[contactId];\n if (!s || TERMINAL_STATUSES.has(s.status)) continue;\n\n // v1.2 — paused_reply contacts get a LIGHTWEIGHT safety pass instead of v1.1's full skip.\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n if (s.status === \"paused_reply\") {\n // v1.4 — R22: paused_reply was absorbing, so the most engaged leads became the ones nothing\n // happened to. After PAUSE_TIMEOUT_DAYS: raise a SECOND task saying so, then release them.\n // Deliberately does not resume — a person got no answer; the fix is a person. NOTES-v1.4.md.\n\n const pausedSince = s.pausedForReplyAt ? new Date(s.pausedForReplyAt).getTime() : null;\n if (pausedSince && Date.now() - pausedSince > pauseTimeoutDays() * DAY_MS) {\n const days = Math.floor((Date.now() - pausedSince) / DAY_MS);\n try {\n if (!TEST_MODE) {\n await createTask(\n contactId,\n `Still waiting on us — replied ${days} days ago, nobody has answered`,\n `This person replied to a follow-up message ${days} days ago. The sequence stopped for them at the time and raised a task, and that task has not been actioned.\\n\\nOpen Conversations, read what they said, and answer it. They are being taken off the automated follow-up either way — they asked a person a question and they deserve a person's answer.`,\n );\n }\n } catch (e) {\n out.log.push(`${contactId}: pause-timeout task failed: ${String(e).slice(0, 100)}`);\n }\n state[contactId] = {\n ...s,\n status: \"done_hard_exit\",\n exitReason: `paused for ${days} days with no human response — escalated and released`,\n lastCheckedAt: new Date().toISOString(),\n };\n out.log.push(`${contactId}: paused ${days}d with no action — escalated, exited`);\n jrow(contactId, \"pause_timeout\", `${days} days unanswered`);\n continue;\n }\n try {\n await sleep(120);\n const contact = await getContact(contactId);\n if (!contact) continue;\n const opportunities = oppsCache.get(contactId) ?? (await getOpenOpportunities(contactId));\n const facts: Facts = {\n now: Date.now(),\n contact: { id: contactId, firstName: contact.firstName ?? \"\", companyName: contact.companyName ?? null, dnd: !!contact.dnd },\n opportunities,\n pupTalkAppt: apptIndex.get(contactId) ?? null,\n declinedSignal: (contact.tags ?? []).includes(PUP_TALK_DECLINED_TAG),\n hasUnansweredInboundReply: false,\n conversationCheckFailed: true, // pinned: no send can ever pass rule 5 on this pass\n channelBlocked: readChannelConsent(contact),\n foreignOutboundAt: null, // no conversation was fetched on this path; rule 5 blocks sends anyway\n };\n const d = decideAction(facts, s);\n const nowIso = new Date().toISOString();\n if (d.kind === \"hard_exit\") {\n const v = pickPrimaryOpportunity(opportunities)?.monetaryValue ?? 0;\n state[contactId] = { ...applyDecision(d, s, nowIso), exitValue: v, exitStepsSent: s.lastMainStepSent + s.lastBranchStepSent + (s.lastSlowStepSent ?? 0) };\n out.log.push(`${contactId}: paused contact hard-exited -> ${d.status} (${d.reason})`);\n jrow(contactId, \"hard_exit\", `${d.reason}${v ? ` | value ${v}` : \"\"}`);\n } else {\n state[contactId] = { ...s, lastCheckedAt: nowIso };\n }\n } catch (err) {\n out.log.push(`${contactId}: paused-pass FAILED: ${String(err).slice(0, 120)}`);\n }\n continue;\n }\n\n // v1.4 — R19b DUE-FIRST FILTERING: if nothing is due, no send can happen, so ask the CRM\n // nothing about this contact. O(due), not O(enrolled). Full reasoning in NOTES-v1.4.md.\n // Two safety valves: SAFETY_SWEEP_HOURS forces a full check daily regardless; any status this\n // shortcut does not model falls through to the full check. Cheap must not mean blind.\n\n const dueCheck = (() => {\n try {\n if (s.status === \"main\") {\n if (s.lastMainStepSent >= MAIN_SEQUENCE.length) return { due: true, why: \"sequence complete, needs exit evaluation\" };\n const next = MAIN_SEQUENCE[s.lastMainStepSent];\n if (isDue(next.offsetHours, s.enteredAt, Date.now())) return { due: true, why: `main step ${s.lastMainStepSent + 1} due` };\n return { due: false, why: `main step ${s.lastMainStepSent + 1} not due yet` };\n }\n if ((s.status === \"branch_a\" || s.status === \"branch_b\") && s.branchAnchorAt) {\n const seq = s.status === \"branch_a\" ? BRANCH_A : BRANCH_B;\n if (s.lastBranchStepSent >= seq.length) return { due: true, why: \"branch complete, needs exit evaluation\" };\n const next = seq[s.lastBranchStepSent];\n if (isDue(next.offsetHours, s.branchAnchorAt, Date.now())) return { due: true, why: \"branch step due\" };\n return { due: false, why: \"branch step not due yet\" };\n }\n // v1.7.1 — slow_track modelled too: the taper population only grows (non-terminal by\n // design), and without this every taper contact cost a full 3-call CRM check every 15\n // minutes for months of \"not due yet\". The daily safety sweep still catches exits.\n if (s.status === \"slow_track\") {\n const c = Math.max(0, Math.floor(Number(s.lastSlowStepSent)) || 0);\n if (isDue(nextSlowTouch(c).offsetHours, s.slowAnchorAt ?? s.enteredAt, Date.now())) return { due: true, why: `slow touch ${c + 1} due` };\n return { due: false, why: `slow touch ${c + 1} not due yet` };\n }\n return { due: true, why: \"status not modelled by the shortcut — full check\" };\n } catch {\n return { due: true, why: \"due-check threw — full check\" };\n }\n })();\n\n const lastChecked = s.lastCheckedAt ? new Date(s.lastCheckedAt).getTime() : 0;\n const sweepOverdue = Date.now() - lastChecked > safetySweepHours() * HOUR_MS;\n\n if (!dueCheck.due && !sweepOverdue) {\n state[contactId] = { ...s, lastCheckedAt: s.lastCheckedAt };\n out.skipped++;\n skippedNotDue++;\n continue; // zero API calls for this contact this run\n }\n\n try {\n await sleep(120); // v1.2 — pacing between contacts (GHL: 100 req/10s, breach = 401/403 not 429)\n const contact = await getContact(contactId);\n if (!contact) {\n out.log.push(`${contactId}: contact not found, skipping`);\n continue;\n }\n const opportunities = oppsCache.get(contactId) ?? (await getOpenOpportunities(contactId));\n const pupTalkAppt = apptIndex.get(contactId) ?? null;\n const declinedSignal = (contact.tags ?? []).includes(PUP_TALK_DECLINED_TAG);\n const reply = await getReplyStatus(contactId, s.enteredAt);\n\n const facts: Facts = {\n now: Date.now(),\n contact: {\n id: contactId,\n firstName: contact.firstName ?? \"\",\n companyName: contact.companyName ?? null,\n dnd: !!contact.dnd,\n },\n opportunities,\n pupTalkAppt,\n declinedSignal,\n hasUnansweredInboundReply: reply.hasUnansweredInboundReply,\n conversationCheckFailed: reply.conversationCheckFailed,\n // v1.5 R27 — was that last outbound ours or somebody else's? Ours iff it lands within\n // OURS_TOLERANCE_MS of our own recorded send. No lastSentAt yet (nothing sent to this\n // contact) means any outbound on the thread is definitionally foreign.\n channelBlocked: readChannelConsent(contact),\n foreignOutboundAt: (() => {\n const lo = reply.lastOutboundAt;\n if (lo == null) return null;\n if (!s.lastSentAt) return lo;\n const ours = new Date(s.lastSentAt).getTime();\n if (Number.isNaN(ours)) return lo;\n return Math.abs(lo - ours) <= OURS_TOLERANCE_MS ? null : lo;\n })(),\n };\n\n const decision = decideAction(facts, s);\n const nowIso = new Date().toISOString();\n\n switch (decision.kind) {\n case \"hard_exit\": {\n // v1.4 — R24: capture what this exit was worth, at the only moment the number is knowable.\n const exitVal = pickPrimaryOpportunity(opportunities)?.monetaryValue ?? 0;\n const stepsSent = s.lastMainStepSent + s.lastBranchStepSent + (s.lastSlowStepSent ?? 0);\n state[contactId] = {\n ...applyDecision(decision, s, nowIso),\n exitValue: exitVal,\n exitStepsSent: stepsSent,\n };\n out.log.push(`${contactId}: hard exit -> ${decision.status} (${decision.reason})${exitVal ? ` | value ${exitVal}` : \"\"}`);\n jrow(contactId, \"hard_exit\", `${decision.reason}${exitVal ? ` | value ${exitVal} after ${stepsSent} message(s)` : \"\"}`);\n break;\n }\n\n case \"pause_reply\":\n state[contactId] = applyDecision(decision, s, nowIso);\n if (decision.isNewPause) {\n jrow(contactId, \"pause_reply\", \"inbound reply detected — handed to a human\");\n const title = `Reply from ${facts.contact.firstName || \"contact\"} re: puppy path — read and respond personally`;\n try {\n await createTask(\n contactId,\n title,\n \"Auto-created by puppy-path-engine: an inbound reply was detected; the sequence is paused for this contact until a human responds.\",\n );\n out.log.push(`${contactId}: paused (new reply), task created`);\n } catch (e) {\n out.log.push(`${contactId}: paused (new reply), TASK CREATE FAILED: ${String(e).slice(0, 120)}`);\n }\n } else {\n out.log.push(`${contactId}: still paused (reply already flagged, no duplicate task)`);\n }\n break;\n\n case \"advance_status\":\n state[contactId] = applyDecision(decision, s, nowIso);\n out.log.push(`${contactId}: advanced -> ${decision.status}`);\n // \"awaiting_appt_outcome\" here means: they booked a Pup Talk while in the sequence —\n // the attributable event the summary counts as bookedDuringPath.\n jrow(contactId, \"advance_status\", decision.status);\n break;\n\n case \"soft_exit_21d\":\n state[contactId] = applyDecision(decision, s, nowIso);\n try {\n await createTask(\n contactId,\n `Puppy path finished for ${facts.contact.firstName || \"contact\"} — now on the slow track`,\n `Puppy path finished for ${facts.contact.firstName || \"contact\"}, no reply/booking. They are now on the slow track (occasional helpful messages: weekly for a month, then fortnightly, then monthly — no sales asks). Nothing needed unless you want them moved in the pipeline too; the stage was NOT auto-moved — that's Kim's call.`,\n );\n } catch (e) {\n out.log.push(`${contactId}: soft-exit task FAILED: ${String(e).slice(0, 120)}`);\n }\n out.log.push(`${contactId}: 21d complete — moved to slow track (stage NOT moved)`);\n jrow(contactId, \"soft_exit_21d\", \"21-day sequence complete — moved to slow track\");\n break;\n\n case \"branch_complete\":\n state[contactId] = applyDecision(decision, s, nowIso);\n out.log.push(`${contactId}: branch complete`);\n jrow(contactId, \"branch_complete\", s.status);\n break;\n\n case \"send\": {\n // v1.2 — blast ceilings (mirrors the PupsClub val's precedent). A capped send is a pure\n // deferral: state untouched, the step stays due, later runs drain the backlog gradually.\n if (out.sent >= maxSendsPerRun()) {\n out.skipped++;\n out.log.push(`${contactId}: send due but MAX_SENDS_PER_RUN (${maxSendsPerRun()}) reached — deferred`);\n break;\n }\n if (!TEST_MODE && sentToday >= maxSendsPerDay()) {\n out.skipped++;\n out.log.push(`${contactId}: send due but MAX_SENDS_PER_DAY (${maxSendsPerDay()}) reached — deferred to tomorrow`);\n break;\n }\n const step = decision.sequence === \"slow\"\n ? slowTemplateAt(decision.stepIndex, Date.now(), s.lastSentStepId).tpl\n : (decision.sequence === \"main\" ? MAIN_SEQUENCE : decision.sequence === \"branch_a\" ? BRANCH_A : BRANCH_B)[decision.stepIndex];\n // v1.7.1 — consent re-checked against the template actually being sent: a monthly\n // re-resolution at the UTC month boundary can flip template (and channel) between\n // decision and execution; an opted-out channel must win that race.\n if (decision.sequence === \"slow\" && facts.channelBlocked[step.channel]) {\n out.skipped++;\n out.log.push(`${contactId}: slow step resolved to opted-out ${step.channel} at send time — skipped, not consumed`);\n break;\n }\n const rendered = renderStep(\n step,\n { firstName: facts.contact.firstName, companyName: facts.contact.companyName },\n { testMode: TEST_MODE },\n );\n try {\n if (rendered.channel === \"sms\") {\n await sendSms(contactId, rendered.text);\n } else {\n await sendEmail(contactId, rendered.subject, rendered.html);\n }\n // v1.2 — state persisted IMMEDIATELY after each successful send (a mid-run crash\n // must never re-send). Non-send transitions recompute idempotently. NOTES-v1.4.md.\n state[contactId] = applyDecision(decision, s, nowIso);\n await saveAllState(state).catch((e) =>\n out.log.push(`${contactId}: sent OK but state persist failed (will retry at end): ${String(e).slice(0, 100)}`),\n );\n // v1.4 — R23: position is an array index, so inserting a message re-points everyone\n // mid-sequence with no signal. Recording the step ID makes that drift DETECTABLE.\n\n // v1.7 — slow records template id; R23 drift check stays main-only (slow's monthly\n // index-to-id mapping varies by design).\n const seqNow = decision.sequence === \"main\" ? MAIN_SEQUENCE : decision.sequence === \"branch_a\" ? BRANCH_A : decision.sequence === \"branch_b\" ? BRANCH_B : null;\n const sentStepId = decision.sequence === \"slow\" ? step.id : (seqNow?.[decision.stepIndex]?.id ?? null);\n if (s.lastSentStepId && sentStepId && seqNow) {\n const prevIdx = seqNow.findIndex((x) => x.id === s.lastSentStepId);\n if (prevIdx >= 0 && prevIdx !== decision.stepIndex - 1 && decision.sequence === \"main\") {\n out.log.push(`${contactId}: SEQUENCE DRIFT — last sent ${s.lastSentStepId} now sits at index ${prevIdx}, expected ${decision.stepIndex - 1}. The copy has been edited underneath in-flight contacts.`);\n jrow(contactId, \"sequence_drift\", `${s.lastSentStepId} -> index ${prevIdx}`);\n }\n }\n state[contactId] = { ...state[contactId], lastSentStepId: sentStepId };\n out.sent++;\n if (!TEST_MODE) sentToday++;\n out.log.push(`${contactId}: sent ${decision.sequence} step ${decision.stepIndex + 1} (${rendered.channel})`);\n jrow(contactId, \"sent\", `${decision.sequence}#${decision.stepIndex + 1} (${rendered.channel === \"sms\" ? \"text\" : \"email\"})`);\n } catch (e) {\n out.failed++;\n out.log.push(`${contactId}: SEND FAILED ${decision.sequence} step ${decision.stepIndex + 1}: ${String(e).slice(0, 120)}`);\n jrow(contactId, \"send_failed\", `${decision.sequence}#${decision.stepIndex + 1}: ${String(e).slice(0, 80)}`);\n }\n break;\n }\n\n case \"skip_step\":\n // v1.6 R28 — the contact has opted out of this step's channel. The step is consumed so\n // the sequence carries on to the next one it IS allowed to send, rather than stalling.\n // Journalled explicitly: a message that silently never went out is exactly the kind of\n // thing nobody notices until a customer asks why they never heard back.\n state[contactId] = applyDecision(decision, s, nowIso);\n out.skipped++;\n out.log.push(`${contactId}: ${decision.reason}`);\n jrow(contactId, \"skip_step_channel_optout\", decision.reason);\n break;\n\n case \"skip\":\n // Still runs through applyDecision (a no-op on every field except lastCheckedAt) so \"last\n // time this contact was actually looked at\" stays accurate per spec §4's schema comment,\n // even on a run where nothing else changed for them.\n state[contactId] = applyDecision(decision, s, nowIso);\n out.skipped++;\n break;\n }\n } catch (err) {\n out.failed++;\n out.log.push(`${contactId}: FAILED: ${String(err).slice(0, 150)}`);\n // v1.4 — this catch used to write to out.log only, and out.log is not persisted to the\n // journal. So a contact failing here was invisible to the dashboard, which reads the journal.\n // Every failure now leaves a row.\n jrow(contactId, \"contact_failed\", String(err).slice(0, 100));\n }\n }\n\n // v1.1: prune stale terminal entries (their history lives on in the journal), persist everything,\n // then rebuild the aggregate summary from full journal + surviving state.\n out.skippedNotDue = skippedNotDue;\n if (skippedNotDue) out.log.push(`${skippedNotDue} contact(s) not due — zero API calls spent on them`);\n const { kept, prunedIds } = pruneState(state, Date.now());\n for (const id of prunedIds) jrow(id, \"pruned\", \"terminal 60+ days, removed from state (journal retains history)\");\n if (prunedIds.length) out.log.push(`pruned ${prunedIds.length} stale terminal entries`);\n await saveAllState(kept);\n const fullJournal = await appendJournal(journal);\n await saveSummary(\n buildSummary(kept, fullJournal, {\n at: new Date().toISOString(),\n testMode: TEST_MODE,\n sent: out.sent,\n failed: out.failed,\n enrolled: out.enrolled,\n }),\n ).catch((e) => out.log.push(`summary save failed: ${String(e).slice(0, 100)}`));\n await saveReport(out);\n await blob.setJSON(\"puppy_run_lock\", { startedAt: null }).catch(() => {}); // release lock\n // Holiday deposits: once an hour, LAST, fully caught, read-only. Why it hangs off this\n // schedule rather than its own file is in NOTES-v1.4.md under \"deposit refresh\".\n try {\n const dep = await import(\"./deposits.ts\");\n await dep.refreshIfDue(() => blob.getJSON(dep.ATTEMPT_KEY) as any, () => dep.runCollection(false, \"engine\"), Date.now());\n } catch (e) { console.log(\"deposits refresh skipped\", String(e).slice(0, 120)); }\n console.log(\"PUPPYPATH\", JSON.stringify(out));\n return out;\n } catch (err) {\n out.ok = false;\n out.error = String(err);\n await saveLastError({ at: new Date().toISOString(), error: String(err) }).catch(() => {});\n // v1.2 — even on a crashed run, persist whatever state mutations happened before the crash\n // (sends already persisted individually; this catches transitions) and the journal rows.\n await saveReport(out).catch(() => {});\n await appendJournal(journal).catch(() => {});\n await blob.setJSON(\"puppy_run_lock\", { startedAt: null }).catch(() => {});\n console.log(\"PUPPYPATH\", JSON.stringify(out));\n return out;\n }\n}\n\n// ---- booking-link shortener (spec §7) --------------------------------------------------\n// (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\nexport async function bookingRedirect(_req: Request): Promise {\n return Response.redirect(REAL_BOOKING_URL, 302);\n}\n\n// ---- exports for the local test harness (puppy-path-engine.test.ts) -------------------------------\n\nexport {\n decideAction,\n applyDecision,\n readChannelConsent, // exported 10 Aug so a test can CALL it, not grep it. See NOTES R31.\n renderStep,\n resolveDogName,\n resolveFirstName,\n applyMergeFields,\n isDue,\n freshState,\n pickPrimaryOpportunity,\n apptIsLiveBooked,\n bodyToHtml,\n // v1.1 pure additions\n businessLocalParts,\n inSendWindow,\n selectEnrollable,\n buildSummary,\n pruneState,\n MAIN_SEQUENCE,\n BRANCH_A,\n BRANCH_B,\n STAGE,\n MAIN_PIPELINE_ID,\n TAG_ENROLLED,\n TAG_SOURCE_SIGNAL,\n PUP_TALK_DECLINED_TAG,\n PHONE_DISPLAY,\n REAL_BOOKING_URL,\n SHORT_BOOKING_LINK,\n TERMINAL_STATUSES,\n DAY_MS,\n HOUR_MS,\n TEST_MODE,\n // v1.7 — slow track\n slowTemplateAt,\n nextSlowTouch,\n monthlyTemplateFor,\n};\n// v1.8 — story machinery + taper banks re-exported for the offline harness\nexport { STORY_SLOTS, resolveStories, storyFor } from \"./kim-stories.ts\";\nexport { SLOW_WEEKLY, SLOW_FORTNIGHTLY, SLOW_MONTHLY_BANK } from \"./taper-messages.ts\";\nexport type { PuppyState, PuppyStatus, Facts, Decision, ContactFact, OppFact, ApptFact, MessageTemplate, RenderedMessage };\n",[270],"245ad811-33e0-43df-8360-236ebfb6905e","kim-stories.ts","789b1fbc-901e-11f1-980a-1607ee4eb77e",129,["D",1785901696927],"// KIM'S STORIES — the one file that makes the taper personal. v1.8, 4 Aug 2026.\n//\n// THE RULE THIS FILE EXISTS TO ENFORCE: no invented stories, ever. No fictional dogs, no\n// composite customers, no \"a client once told me\". Every `story` below starts as null and stays\n// null until KIM'S OWN WORDS go in. The copy is written to read complete without them — an\n// empty slot renders as nothing, not as a hole.\n//\n// HOW TO FILL ONE IN (the whole procedure, ~5 minutes):\n// 1. Kim answers a question from the Story Capture Sheet (handover/Story-Capture-Sheet.pdf).\n// 2. Paste her answer, lightly tidied but in her words, as the `story` string below.\n// Keep it to 2-4 sentences. First person. No customer surnames without her okay.\n// 3. PUT this one file to the val (same deploy command as always). Nothing else changes.\n// 4. The next send that hits that slot carries her story. Practice mode renders it too,\n// so it can be checked on the panel/journal before anyone real sees it.\n//\n// Slots are ADDITIVE paragraphs: the template holds {{STORY:id}} on its own line; the renderer\n// swaps in the story, or removes the line entirely when null. Both paths are tested.\n\nexport type StorySlot = {\n id: string;\n // The question that gets a usable answer from Kim in 30 seconds — printed on the capture sheet.\n prompt: string;\n // Where it lands, so a human editing this file knows the context without opening the copy file.\n lands: string;\n // Kim's words, or null. Null = the message sends without it and reads complete.\n story: string | null;\n};\n\nexport const STORY_SLOTS: StorySlot[] = [\n {\n id: \"teenage\",\n prompt: \"Name one dog who turned into a teenage terror around 8 months and came good. What did the owner stick with?\",\n lands: \"Slow track week 1 — the adolescence email\",\n story: null,\n },\n {\n id: \"alone_time\",\n prompt: \"Tell me about one dog who couldn't be left alone at first. What actually fixed it?\",\n lands: \"Slow track day 63 — the alone-time email\",\n story: null,\n },\n {\n id: \"vet_visits\",\n prompt: \"Which dog do you know who walks into the vet happy? What did their owner do differently?\",\n lands: \"Slow track day 70 — the vet visits email\",\n story: null,\n },\n {\n id: \"settle\",\n prompt: \"One dog you can picture lying calmly somewhere busy (a patio, a game, a store). How did they get there?\",\n lands: \"Slow track day 119 — the off-switch email\",\n story: null,\n },\n {\n id: \"dog_parks\",\n prompt: \"One thing you've seen go wrong at a dog park that the owner never noticed. What should they have seen?\",\n lands: \"Slow track day 147 — the dog parks email\",\n story: null,\n },\n {\n id: \"nose_work\",\n prompt: \"Name a dog who was 'bad' until they got a job to do. What was the job?\",\n lands: \"Slow track day 175 — the boredom email\",\n story: null,\n },\n {\n id: \"leash_meetings\",\n prompt: \"Which pair of dogs hated each other on leash but got along fine off it, or walking side by side?\",\n lands: \"Slow track day 203 — the leash meetings email\",\n story: null,\n },\n {\n id: \"holidays\",\n prompt: \"What's one thing that happens at the kennel every Thanksgiving or Christmas that owners would never guess?\",\n lands: \"Monthly November — the holiday guests email\",\n story: null,\n },\n];\n\nconst byId = new Map(STORY_SLOTS.map((s) => [s.id, s]));\n\n// Anything SHAPED like a slot token but not a slot we know: an empty id `{{STORY:}}`, a spaced id\n// `{{STORY: a b }}`, the residue a nested token leaves behind after its inner half resolves. None of\n// these is a slot, so none of them is content. They get removed, never shipped.\n// [was: a single pass matching only /\\{\\{STORY:[a-z_]+\\}\\}/, which left `{{STORY:}}` standing\n// after resolving the inner token of `{{STORY:{{STORY:x}}}}`. Caught by tests/stories.test.mjs S5.]\nconst TOKEN_SHAPE = /\\{\\{STORY:[^{}]*\\}\\}/g;\n// Last line of defence: even a half-token fragment must not reach a customer.\nconst TOKEN_FRAGMENT = /\\{\\{STORY:[^}]*\\}{0,2}/g;\n\n// story text, or null. Trims whitespace so a pasted answer can't break the layout.\nexport function storyFor(id: string): string | null {\n const s = byId.get(id)?.story;\n if (!s) return null;\n // A pasted answer can't smuggle a slot token back in (single-pass resolve would ship it raw).\n const t = s.replace(TOKEN_FRAGMENT, \"\").trim();\n return t.length ? t : null;\n}\n\n// Resolve every {{STORY:id}} token in a rendered body. Unknown ids resolve to nothing rather\n// than leaking a token to a customer — and the tests assert every id used in copy exists here.\n//\n// Resolution LOOPS rather than running once. One pass is not enough: a malformed nest only reveals\n// its outer token after the inner one is gone, and a filled story sitting next to a token can shift\n// what the next match sees. The loop is bounded (a pass that changes nothing stops it), so a\n// pathological input costs a few passes rather than hanging.\nexport function resolveStories(text: string): string {\n let out = String(text ?? \"\");\n for (let pass = 0; pass < 8 && out.includes(\"{{STORY:\"); pass++) {\n const before = out;\n out = out.replace(/\\{\\{STORY:([a-z_]+)\\}\\}/g, (_, id) => storyFor(id) ?? \"\");\n out = out.replace(TOKEN_SHAPE, \"\");\n if (out === before) break;\n }\n // Whatever survived the loop is not a slot and is not content.\n out = out.replace(TOKEN_FRAGMENT, \"\");\n return out.replace(/\\n{3,}/g, \"\\n\\n\").trim();\n}\n",[279],"5d9872c5-03e7-472a-906d-0efcc23be7b7","holiday-deposits.ts","2f043ab0-91ad-11f1-9dc1-1607ee4eb77e",490,["D",1786309576501],20,"// HOLIDAY DEPOSIT TRACKER. v1.0, 6 Aug 2026.\n//\n// WHAT KIM ASKED FOR: she charges a $50 nonrefundable deposit on boarding stays over holidays,\n// and today somebody goes through the bookings by hand to work out who has paid.\n//\n// WHAT THIS CAN AND CANNOT DO, because the difference is the whole honesty of the feature.\n// Square money DOES reach the CRM. It arrives as a note on the contact, like\n// \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\"\n// (verified live on 6 Aug against a real contact). So we can see payments that went through\n// Square. We CANNOT see a deposit handed over in cash or taken over the phone. That means this\n// produces a SHORTLIST TO CHECK, never a list of people who have not paid. The word \"unpaid\"\n// is banned from anything this module renders, and a test enforces that.\n//\n// TWO TRAPS FOUND IN HER REAL DATA, both of which would have made Kim chase the wrong people:\n// 1. The same Square payment is written into the notes FIVE times, and the \"(balance ...)\"\n// figures inside those duplicates contradict each other ($355.00 then $0.00 four times).\n// So: dedupe on the payment id, and never read the balance figure.\n// 2. A recurring weekly slot (\"Daycare Enzo\") lands inside every holiday window. Without a\n// recurring filter Kim would be told a regular customer owes her a holiday deposit eight\n// times over. Recurring bookings are excluded.\n//\n// THIS MODULE WRITES NOTHING. No tag, no custom field, no pipeline stage, no message. That is\n// deliberate and it is tested: addTag() elsewhere in this engine is not TEST_MODE-guarded, and\n// this account contains a workflow (\"Add tag 'red flag' = DND\") which proves a single tag here\n// can silence a real customer on six channels. A read-only report cannot do that.\n\nexport type CalEvent = {\n contactId?: string | null;\n title?: string | null;\n startTime?: string | number | null; // carries its own offset, e.g. \"2026-11-25T09:00:00-05:00\"\n // The pick-up. A stay that starts before a holiday window and runs into it is a holiday stay,\n // and without this the module could only see the drop-off day.\n endTime?: string | number | null;\n dateAdded?: string | null;\n appointmentStatus?: string | null;\n // Her CRM really does return BOTH spellings on the same object: 4 of the 13 events on the\n // Boarding Drop Off calendar carry `appoinmentStatus` alongside the correct one (checked live,\n // 6 Aug 2026). They agree today. Reading only one of them is passing a test by luck.\n appoinmentStatus?: string | null;\n isRecurring?: boolean | null;\n deleted?: boolean | null;\n};\n\n// \"direct\" = \"[Square] +$35.00 payment (balance $x)\" — money arriving\n// \"matched\" = \"[Square] Till payment $35.00 on . Matched from Square payment ...\"\n// — a RECONCILIATION record written by the backfill, carrying its own separate id.\n// Both are real and both are live in her account on the same contact, with the same amount and\n// two different ids. See collapseSameMoney() for why that distinction has to survive parsing.\nexport type Payment = { amount: number; id: string; at: string | null; kind: \"direct\" | \"matched\" };\n\nexport type Stay = {\n contactId: string;\n day: string; // local date of the drop-off, \"YYYY-MM-DD\"\n until: string; // local date of the pick-up; equals `day` when the CRM does not say\n dogs: string[]; // one stay can be several dogs (names, best effort)\n dogCount: number; // how many drop-off rows this stay is, whether or not the names parsed\n bookedAt: string | null;\n window: string; // which holiday it falls in, in Kim's words\n};\n\nexport type StayStatus = {\n stay: Stay;\n state: \"seen\" | \"partial\" | \"none_seen\" | \"could_not_check\";\n amountSeen: number;\n note: string; // the plain-English reason, always populated\n};\n\n/** The fourth Thursday of November. Computed, never typed, so it cannot drift year to year.\n * Kim was told Thanksgiving is handled by working it out fresh each year. This is that. */\nexport function thanksgiving(year: number): string {\n // day 1 of November, then walk to the first Thursday, then add three weeks.\n const first = new Date(Date.UTC(year, 10, 1));\n const dow = first.getUTCDay(); // 0 Sun .. 4 Thu\n const firstThu = 1 + ((4 - dow) + 7) % 7;\n const day = firstThu + 21;\n return `${year}-11-${String(day).padStart(2, \"0\")}`;\n}\n\n/** The windows a deposit applies to, as dates, derived rather than hardcoded.\n * Thanksgiving: the Monday before through the Sunday after.\n * Christmas and New Year: 20 Dec through 2 Jan.\n * If Kim wants different edges these are the only two lines to change. */\nexport function holidayWindows(year: number): { name: string; from: string; to: string }[] {\n const t = thanksgiving(year);\n // [was: String(Number(t.slice(8)) + 3) — decimal arithmetic on the day number. Whenever\n // Thanksgiving falls on the 28th (2030, 2041, ...) that produced \"2030-11-31\", a date that does\n // not exist. Two consequences, both live: a stay dropping off Sunday 1 December sorts ABOVE\n // \"2030-11-31\" in a string compare and vanishes from the window, and the card printed the\n // words \"Thanksgiving (Nov 25 to Nov 31)\" to Kim. Real calendar arithmetic now.]\n return [\n { name: \"Thanksgiving\", from: shiftDays(t, -3), to: shiftDays(t, 3) },\n { name: \"Christmas and New Year\", from: `${year}-12-20`, to: `${year + 1}-01-02` },\n ];\n}\n\n/** The local calendar day of an appointment. startTime carries its own offset, so the first ten\n * characters ARE the local day. Parsing it into a Date and reformatting would shift bookings\n * across midnight into or out of a window, which is how a customer gets chased by mistake.\n *\n * A NUMBER is handled separately and deliberately. Two sibling modules that read this same CRM\n * endpoint already defend against an epoch-millisecond startTime, so the shape is real. Returning\n * null for it would have dropped EVERY stay silently and stored \"no holiday stays are booked\" as\n * a fact, in November, with the kennels full. An epoch has no offset, so it is converted in the\n * business's own timezone rather than in whatever timezone the server happens to be in. */\nexport const BUSINESS_TZ = \"America/New_York\";\nexport function localDay(startTime: string | number | null | undefined): string | null {\n if (typeof startTime === \"number\" && Number.isFinite(startTime)) {\n try {\n const p = new Intl.DateTimeFormat(\"en-CA\", { timeZone: BUSINESS_TZ, year: \"numeric\", month: \"2-digit\", day: \"2-digit\" })\n .format(new Date(startTime));\n return /^\\d{4}-\\d{2}-\\d{2}$/.test(p) ? p : null;\n } catch { return null; }\n }\n if (!startTime || typeof startTime !== \"string\" || startTime.length < 10) return null;\n // A STRING ENDING IN Z IS UTC, AND ITS FIRST TEN CHARACTERS ARE NOT THE LOCAL DAY.\n //\n // The slice below is right for \"2026-11-25T21:00:00-05:00\", which carries New York's own offset.\n // It is wrong by a whole day for \"2026-11-26T02:00:00Z\", which is the same instant: every evening\n // drop-off from about 7pm Eastern reads as the NEXT calendar day. A stay on 2 January — the last\n // day of the Christmas and New Year window — moves to the 3rd, falls outside `to`, and the\n // customer silently never appears on Kim's shortlist at all. No error, no \"could not check\".\n //\n // Said plainly: this shape has NOT been seen on this endpoint. Every startTime read live on 6 and\n // 7 August carried an explicit offset. But two sibling modules already defend against an epoch\n // number from this same CRM, a Z suffix is unambiguous when it does appear, and converting it in\n // the business's own timezone costs one branch. Handling it is cheap; slicing it is wrong.\n if (/\\dZ$/.test(startTime)) {\n const t = Date.parse(startTime);\n return Number.isFinite(t) ? localDay(t) : null; // through the epoch branch, in BUSINESS_TZ\n }\n const d = startTime.slice(0, 10);\n return /^\\d{4}-\\d{2}-\\d{2}$/.test(d) ? d : null;\n}\n\n/** WHICH SEASON ARE WE IN. Passed the local date as \"YYYY-MM-DD\", never reading the clock itself,\n * so this is testable and cannot behave differently on the val than it does here.\n * On 1 January the season that matters is still LAST year's — the New Year window runs to the 2nd,\n * and a page that flips to next Thanksgiving on New Year's Day drops the stays happening that day. */\nexport function businessDay(nowIso: string): string {\n // Her business is in New York. Rolling the season over on the UTC date empties the card at 8pm\n // on 2 January, five hours before the season actually ends, while dogs are still in the kennels\n // — and the empty result then gets stored over the real one.\n try {\n const d = new Date(nowIso);\n if (isNaN(d.getTime())) return String(nowIso).slice(0, 10);\n const p = new Intl.DateTimeFormat(\"en-CA\", { timeZone: BUSINESS_TZ, year: \"numeric\", month: \"2-digit\", day: \"2-digit\" }).format(d);\n return /^\\d{4}-\\d{2}-\\d{2}$/.test(p) ? p : String(nowIso).slice(0, 10);\n } catch { return String(nowIso).slice(0, 10); }\n}\n\nexport function seasonYear(today: string): number {\n const y = Number(today.slice(0, 4));\n const md = today.slice(5, 10);\n return md <= \"01-02\" ? y - 1 : y;\n}\n\nexport function windowFor(day: string | null, windows: { name: string; from: string; to: string }[]): string | null {\n if (!day) return null;\n for (const w of windows) if (day >= w.from && day <= w.to) return w.name;\n return null;\n}\n\n/** A STAY, not a moment. Somebody who drops off on 19 December and collects on 27 December has\n * boarded over Christmas and owes the holiday deposit, but their drop-off day is outside the\n * window. Deciding membership on the drop-off day alone dropped exactly the customers a holiday\n * boarding business has most of: the ones who leave the day before they travel. */\nexport function windowForRange(from: string | null, to: string | null, windows: { name: string; from: string; to: string }[]): string | null {\n if (!from) return null;\n const end = to && to >= from ? to : from;\n for (const w of windows) if (from <= w.to && end >= w.from) return w.name;\n return null;\n}\n\n/** Which bookings count. Cancelled, deleted and recurring are all excluded, and the recurring\n * exclusion is the one that matters most: a standing weekly slot is not a holiday stay. */\nexport const DEAD_STATUSES = [\"cancelled\", \"canceled\", \"noshow\", \"no-show\", \"no show\", \"invalid\"];\nexport function eligible(e: CalEvent): boolean {\n if (!e || truthy(e.deleted)) return false;\n // [was: `e.isRecurring === true`. Her CRM has already been caught shipping the misspelled\n // `appoinmentStatus`, so trusting it to always send a real boolean here is a bet, not a fact.\n // A recurring series returned with isRecurring:\"true\" would have put a weekly daycare regular\n // on the list telling him he owes a boarding deposit.]\n if (truthy(e.isRecurring)) return false;\n // BOTH spellings are read, and either one saying cancelled is enough to drop the booking.\n // The asymmetry is deliberate: dropping a live booking means Kim is not prompted about it and\n // she notices; keeping a cancelled one means she chases a customer who already cancelled, and\n // that one she cannot take back.\n // TRIMMED, because this account demonstrably ships padded strings: \"Daycare Enzo \" and\n // \" Boarding Dropoff with Help Test\" are both real titles out of it. One trailing space on a\n // status was enough to make a cancelled booking eligible.\n const states = [e.appointmentStatus, e.appoinmentStatus].map((s) => String(s ?? \"\").trim().toLowerCase());\n // EXPORTED so a test can assert the whole list rather than the one spelling somebody thought\n // of. GHL really does emit `noshow` and `invalid`, and the American spelling is one keystroke\n // away. Letting any of them through puts a customer who cancelled on Kim's chase list, which\n // the comment above calls the mistake she cannot take back.\n const dead = DEAD_STATUSES;\n if (states.some((s) => dead.includes(s))) return false;\n if (!e.contactId) return false;\n // A DAYCARE slot is not a boarding stay and carries no boarding deposit. Until now the ONLY\n // thing keeping the weekly \"Daycare Enzo\" booking off Kim's list was its recurrence flag; a\n // one-off daycare booking in Christmas week would have been billed a $50 boarding deposit.\n // Narrowed: a title that says BOTH is a boarding booking with a note on it, and excluding\n // \"Boarding + daycare drop off with Dan Bonner\" would lose a real holiday stay.\n const title = String(e.title ?? \"\");\n if (/\\bday\\s?care\\b/i.test(title) && !/\\bboarding\\b/i.test(title)) return false;\n return true;\n}\n\n/** Her CRM's booleans are not reliably booleans. Treats \"true\"/\"TRUE\"/1 the same as true, and\n * anything else, including undefined, as false. */\nfunction truthy(v: unknown): boolean {\n if (v === true || v === 1) return true;\n return typeof v === \"string\" && v.trim().toLowerCase() === \"true\";\n}\n\n/** A dog's name out of \"Achilles — Boarding Drop Off\" style titles, best effort and never fatal. */\nexport function dogFromTitle(title: string | null | undefined): string {\n const t = (title || \"\").trim();\n if (!t) return \"\";\n // [was: split on /[—–-]/, which cut \"Jean-Luc — Boarding Drop Off\" down to \"Jean\". A hyphen\n // inside a name is not a separator; a SPACED hyphen is. Kim reads these names before phoning\n // somebody, so the wrong name here is a wrong conversation.]\n const cut = t.split(/\\s[—–-]\\s|[—–]|\\bBoarding\\b|\\bDrop\\s?off\\b/i)[0];\n return cut.trim().replace(/\\s+with\\s+.*$/i, \"\").trim();\n}\n\n/** WHERE THE END OF A STAY ACTUALLY LIVES. A drop-off appointment in her CRM is a TEN MINUTE\n * slot: \"2026-11-25T12:50 to 2026-11-25T13:00\". Its endTime is the end of the handover, not the\n * end of the boarding. The real length of the stay is on a separate Boarding Pick Up calendar —\n * Ghost and Chewy drop off on 25 November and are collected on the 28th, and only the pick-up\n * calendar says so. Without this, \"did this dog board over Christmas\" could only ever be answered\n * by the drop-off date, and everybody who leaves the day before the holiday starts was invisible.\n * The LATEST eligible pick-up on or after the drop-off wins, bounded by the customer's own next\n * booking and by MAX_STAY_DAYS. */\nexport const MAX_STAY_DAYS = 21;\nexport function attachPickups(stays: Stay[], pickups: CalEvent[]): Stay[] {\n const byContact = new Map();\n for (const p of pickups) {\n if (!eligible(p)) continue;\n const d = localDay(p.startTime);\n if (!d || !p.contactId) continue;\n const list = byContact.get(p.contactId) ?? [];\n list.push(d);\n byContact.set(p.contactId, list);\n }\n for (const list of byContact.values()) list.sort();\n // The customer's OWN next drop-off is the hard upper bound. Without it a stay reaches forward\n // and takes a pick-up belonging to a later booking: a 3-night Thanksgiving stay was rendered\n // \"Nov 25 to Dec 27\", and an ordinary 6 November boarding was dragged into a holiday window and\n // billed a deposit. [was: the EARLIEST pick-up on or after the drop-off, which was wrong the\n // other way — one dog of three going home early cut the stay short and deleted it from the\n // window entirely. Her pick-up calendar really does carry one row per dog.]\n // A stay cannot run forever. Without an upper bound an ORPHAN pick-up — and her account has\n // about twenty contacts with pick-ups and no matching drop-off — drags an out-of-season boarding\n // into a holiday window: a 6 November stay with a stray 1 February pick-up record rendered as\n // \"Nov 6 to Feb 1\" on Kim's shortlist.\n const dropDays = new Map();\n for (const s of stays) {\n const list = dropDays.get(s.contactId) ?? [];\n list.push(s.day);\n dropDays.set(s.contactId, list);\n }\n for (const list of dropDays.values()) list.sort();\n return stays.map((s) => {\n const nextDrop = (dropDays.get(s.contactId) ?? []).find((d) => d > s.day);\n // `<=` on the next drop-off, not `<`: a pick-up on the same day as the customer's next\n // booking is the END of this stay, not part of the next one. With a strict `<`, a customer\n // collecting on 27 December and re-boarding the same day lost their Christmas stay entirely.\n const cands = (byContact.get(s.contactId) ?? []).filter((d) =>\n d >= s.day && d <= shiftDays(s.day, MAX_STAY_DAYS) && (!nextDrop || d <= nextDrop));\n const cand = cands.length ? cands[cands.length - 1] : null;\n return cand && cand > s.until ? { ...s, until: cand } : s;\n });\n}\n\n/** One customer dropping three dogs on the same day is ONE stay and ONE deposit question. */\nexport function groupIntoStays(\n events: CalEvent[],\n windows: { name: string; from: string; to: string }[],\n pickups: CalEvent[] = [],\n): Stay[] {\n const by = new Map();\n for (const e of events) {\n if (!eligible(e)) continue;\n const day = localDay(e.startTime);\n const until = localDay(e.endTime) ?? day;\n if (!day) continue;\n const key = `${e.contactId}|${day}`;\n const dog = dogFromTitle(e.title);\n const existing = by.get(key);\n if (existing) {\n if (dog && !existing.dogs.includes(dog)) existing.dogs.push(dog);\n // COUNTED FROM THE ROWS, not from the names. A title that does not parse still means a dog,\n // and the deposit is charged per dog, so counting parsed names would under-charge.\n existing.dogCount++;\n // the LATEST pick-up across the dogs on this stay\n if (until && until > existing.until) existing.until = until;\n // keep the EARLIEST booking time: that is when the deposit became due\n if (e.dateAdded && (!existing.bookedAt || e.dateAdded < existing.bookedAt)) existing.bookedAt = e.dateAdded;\n } else {\n by.set(key, { contactId: e.contactId!, day, until: until ?? day, dogs: dog ? [dog] : [], dogCount: 1, bookedAt: e.dateAdded ?? null, window: \"\" });\n }\n }\n // Pick-ups are attached BEFORE the window filter, because the whole point is that a stay whose\n // drop-off falls outside a window can still run through it.\n const withEnds = attachPickups([...by.values()], pickups);\n const out: Stay[] = [];\n for (const s of withEnds) {\n const win = windowForRange(s.day, s.until, windows);\n if (win) out.push({ ...s, window: win });\n }\n return out.sort((a, b) => (a.day < b.day ? -1 : a.day > b.day ? 1 : 0));\n}\n\n/** Square payments out of contact notes, DEDUPED BY PAYMENT ID.\n * The same payment appears five times in her real data with contradictory balance figures, so\n * the balance is deliberately not read: only the amount and the payment's own id. */\nexport function parseSquarePayments(notes: { body?: string | null; dateAdded?: string | null }[] | null | undefined): Payment[] {\n const out = new Map();\n // EVERY match in EVERY note, not the first match in each.\n // [was: .exec() on each body, i.e. one payment per note. A note holding two Square lines lost\n // the second one. Every parser gap in this function fails in the same direction — less money\n // seen than was paid — and that direction is the one that puts a paying customer on the list.]\n // The amount tolerates whole dollars (\"+$50 payment\") as well as cents, and the id stops at\n // punctuation so a trailing comma cannot become part of the dedupe key.\n const DIRECT = /\\[Square\\]\\s*\\+?\\$([\\d,]+(?:\\.\\d{2})?)\\s+payment\\s+([A-Za-z0-9_-]+)/gi;\n // Format 2: the reconciliation backfill. It carries the REAL payment date in its own text,\n // which is four days earlier than the note's dateAdded on the live example, so the stated\n // date is used and the note's write time is only the fallback. The trailing punctuation after\n // the id is OPTIONAL: on a note that ENDS at the id the whole payment used to vanish.\n const MATCHED = /\\[Square\\][^[]*?Till payment\\s*\\$([\\d,]+(?:\\.\\d{2})?)\\s*on\\s*(\\d{4}-\\d{2}-\\d{2})[\\s\\S]*?Matched from Square payment\\s+([A-Za-z0-9_-]+)/gi;\n const add = (amount: number, id: string, at: string | null, kind: \"direct\" | \"matched\") => {\n if (!Number.isFinite(amount) || !id) return;\n const prev = out.get(id);\n // keep the earliest sighting of a given payment\n if (!prev || (at && prev.at && at < prev.at)) out.set(id, { amount, id, at, kind });\n else if (!prev.at) out.set(id, { amount, id, at, kind });\n };\n for (const n of notes ?? []) {\n const body = n?.body ?? \"\";\n if (!body) continue;\n for (const m of body.matchAll(MATCHED)) add(Number(m[1].replace(/,/g, \"\")), m[3], m[2], \"matched\");\n for (const m of body.matchAll(DIRECT)) add(Number(m[1].replace(/,/g, \"\")), m[2], n?.dateAdded ?? null, \"direct\");\n }\n return [...out.values()].sort((a, b) => String(a.at).localeCompare(String(b.at)));\n}\n\n/** THE SAME $35, TWICE, UNDER TWO IDS.\n * Live on David Newman's contact right now: \"+$35.00 payment z3rQ...\" and \"Till payment $35.00\n * on 2026-07-17. Matched from Square payment 3zu7...\". Same money or two payments? Nothing in\n * the data settles it, and the two readings disagree about whether a $50 deposit is covered.\n * So the conservative reading wins: a \"Matched from\" record of the same amount as a direct\n * payment is treated as describing that same money. Getting this wrong the other way removes a\n * person from the shortlist, and a person who is not on the shortlist is never looked at. */\n/** A CONTACT THAT LOOKS LIKE SOMEBODY TESTING THE BOOKING FORM. Kim's account holds at least two:\n * a contact literally named \"help test\" with three future boarding bookings, and a tagged\n * \"ZZTEST PuppyPath-Dummy\". This does NOT remove the row — a filter that quietly drops a real\n * customer called Mr Test is worse than a label — it flags it, so Kim knows before she picks up\n * the phone to a stranger about $50. */\nexport function looksLikeTestRecord(name: string | null | undefined): boolean {\n // \"tester\" is deliberately absent: Tester is a real surname, and this label appears on Kim's\n // screen right next to a person's name, immediately before she decides whether to phone them.\n return /\\b(test|testing|dummy|zztest|do not use|ignore)\\b/i.test(String(name ?? \"\"));\n}\n\n// 21 DAYS, and the number is not a guess. The one real pair on her account is a payment noted on\n// 31 July reconciling a till payment the backfill states was taken on 17 July: 14.6 days, because\n// the parser deliberately uses the backfill's OWN stated payment date rather than the day the note\n// was written. A fortnight would have been too tight for the only case anybody has ever seen, so\n// the bound carries about 40% headroom over it and still refuses to fold across months.\nexport const COLLAPSE_WINDOW_DAYS = 21;\nexport function collapseSameMoney(payments: Payment[]): { kept: Payment[]; collapsed: number } {\n // IDEMPOTENT, and now DATE-BOUNDED. Both properties are load-bearing.\n //\n // Idempotent [round 6]: every backfill record sharing an amount with a payment folds, so a\n // second pass finds nothing. The layers above assume that.\n //\n // Date-bounded [round 9]: a \"Matched from Square payment\" note is a reconciliation of a payment\n // near it in TIME. The one real pair on her account is four days apart; the code was folding on\n // amount alone, across the customer's whole history. $50 is precisely the amount a repeat\n // customer pays more than once in a year, so a November payment and a December till record were\n // being read as one $50 — deleting a real deposit, demoting a settled stay, and then printing\n // \"nothing unspent on file matches that amount\" and \"nothing else is unaccounted for\" about a\n // customer who had paid twice. 2.3% of generated customers. Same false sentence as round 8's\n // bug, a different door.\n //\n // The bias is unchanged and deliberate: folding keeps somebody ON the shortlist, which costs Kim\n // a glance. NOT folding a genuine duplicate would clear somebody who owes, which costs her $50\n // and she never finds out. The bound only stops folding across months, where \"same money\" stops\n // being a plausible reading at all.\n const directs = payments.filter((p) => p.kind === \"direct\");\n const kept: Payment[] = [];\n let collapsed = 0;\n for (const p of payments) {\n if (p.kind === \"matched\" && directs.some((d) => d.amount === p.amount && withinDays(d.at, p.at, COLLAPSE_WINDOW_DAYS))) {\n collapsed++;\n continue;\n }\n kept.push(p);\n }\n return { kept, collapsed };\n}\n\n/** Are two payment dates close enough to be the same money? A missing date on either side counts\n * as close: an undated record is not evidence that they are far apart. */\nexport function withinDays(a: string | null, b: string | null, days: number): boolean {\n const x = Date.parse(String(a ?? \"\")), y = Date.parse(String(b ?? \"\"));\n if (!Number.isFinite(x) || !Number.isFinite(y)) return true;\n return Math.abs(x - y) <= days * 86_400_000;\n}\n\nexport const DEPOSIT = 50;\n\n/** WHAT THIS STAY OWES. Kim's own money page, taken from her live website: \"Holiday boarding —\n * $50 PER DOG, non-refundable. Deducted from the total boarding cost at drop-off.\"\n * [was: a flat $50 per stay, with a line on the card asking Kim to tell us if it was per dog.\n * It is per dog, and it says so in her own handover pack. Jeffrey Musselwhite's three dogs on\n * 25 November owe $150, and a single $50 payment was clearing that whole stay — the silent\n * direction, where somebody who owes $100 more drops off the list and is never looked at.] */\nexport function depositDue(stay: Stay): number {\n return DEPOSIT * dogsOn(stay);\n}\nexport function dogsOn(stay: Stay): number {\n return Math.max(1, stay.dogCount || stay.dogs.length || 1);\n}\n\n/** THE ONE PLACE THAT DECIDES WHICH PAYMENTS SETTLE A STAY. Returns them, or nothing.\n *\n * This exists because the money bug has now come back FOUR times, and every time through the\n * same crack: the rule for \"is this stay settled\" and the rule for \"what did that cost\" lived in\n * two places and drifted apart. The last version cleared a stay on either one payment for the\n * full amount OR one $50 per dog, and then debited a single $50 — so a two-dog stay settled by a\n * $100 payment debited NOTHING, and the same $100 settled the customer's next stay too. Kim owed\n * $200, $100 arrived, neither row reached her shortlist. 29% of generated multi-stay customers\n * hit it.\n *\n * So there is one function. statusFor asks it what settles the stay; the allocator asks it what\n * to spend. They cannot disagree, because it is the same answer. */\nexport function qualifyingPayments(stay: Stay, payments: Payment[]): Payment[] {\n // OLDEST MONEY FIRST, and never in whatever order the array happened to arrive.\n //\n // [was: `near.find(...)` and `perDog.slice(0, dogs)` straight off the caller's array. Two things\n // came out of that, found by a property test over 841,000 shuffles on 7 August:\n // 1. The same customer, the same payments, a different array order, a different answer. There\n // is no meaningful order on this list — it is whatever the notes endpoint returned — so a\n // row could move between \"Payment on file\" and \"Worth a look\" from one hourly run to the\n // next with nothing whatsoever having changed on her account.\n // 2. Worse, it could starve a later stay. Two real $50 payments, both inside the FIRST stay's\n // window, only the later one inside the SECOND stay's window: settle the first stay with the\n // later payment and the second stay has nothing left it can reach, and reads as unpaid.\n // Settle it with the earlier one and both are correctly settled. Oldest-first is the reading\n // that matches how the money was actually spent, and it is stable.\n // Sorted by id as well as date, so two payments stamped the same second cannot swap either.]\n // A payment with no readable date sorts LAST, not first: \"oldest first\" is a claim, and an\n // undated record is not evidence that it is the oldest. DEFENSIVE ONLY, and there is no negative\n // control for it on purpose: paymentsNearStay compares (p.at || \"\").slice(0, 10) against the\n // window, \"\" is below every real date, so an undated payment is filtered out before this line\n // ever sees it. A control that cannot be made to fail is worse than no control. H86 pins the\n // reachable half of that — an undated record never qualifies for a stay at all.\n const when = (p: Payment) => {\n const t = p.at ? Date.parse(p.at) : NaN;\n return Number.isFinite(t) ? t : Number.POSITIVE_INFINITY;\n };\n const near = [...collapseSameMoney(paymentsNearStay(stay, payments)).kept]\n .sort((a, b) => when(a) - when(b) || String(a.id).localeCompare(String(b.id)));\n const due = depositDue(stay);\n const dogs = dogsOn(stay);\n const whole = near.find((p) => p.amount === due);\n if (whole) return [whole];\n const perDog = near.filter((p) => p.amount === DEPOSIT);\n return perDog.length >= dogs ? perDog.slice(0, dogs) : [];\n}\n\n// HOW A PAYMENT IS MATCHED TO A DEPOSIT, and why the answer is \"it mostly is not\".\n//\n// Nothing in her CRM says what a card payment was FOR. Two attempts at guessing have now both\n// been wrong in a way that costs her money:\n// v1 summed every payment between the booking and the drop-off. A $355 training package cleared\n// a $50 deposit, and being cleared means nobody ever looks at that customer again.\n// v2 narrowed it to ten days around the booking and still summed. That missed a real $50 paid\n// eight days later — the page said \"we cannot find a $50 payment\" one line after printing\n// one — and STILL cleared anybody who happened to settle a $240 invoice that same week.\n//\n// So this version stops guessing. It clears a stay on ONE piece of evidence only: a card payment\n// for EXACTLY the deposit amount, in a wide window around the stay. Anything else is shown to Kim\n// with its date and amount and left for her to judge, which takes her about two seconds per row\n// and is the thing she was doing by hand anyway. A wrong \"worth a look\" costs her a glance. A\n// wrong \"settled\" costs her $50 and she never finds out.\n// HOW SHE ACTUALLY GETS PAID, off her own money page: \"Card — at the counter, or through the\n// website's payments page. This is the normal route and THE ONLY ONE THAT MATCHES ITSELF TO A\n// CUSTOMER RECORD AUTOMATICALLY. Venmo — there is a Venmo page on the website. Zelle — sent to an\n// address inside the Zelle app. Cheque — made payable by post.\"\n// [was: \"may still have been paid in cash or over the phone\", which named neither of the two\n// routes she actually offers. Every one of Venmo, Zelle and cheque is invisible here, so naming\n// them is the difference between Kim knowing where to look and Kim assuming non-payment.]\n// CASH IS NOT ONE OF HER ROUTES. [was: \"Venmo, Zelle, cheque or cash\". Her money page lists\n// exactly four ways to pay — Card, Venmo, Zelle and Cheque — and cash appears nowhere on her site\n// or anywhere in the handover pack. The comment directly above this line names the three invisible\n// routes correctly and the string underneath it invented a fourth. True of cash in general,\n// invented as a thing Kim accepts, and the whole point of this sentence is telling her where else\n// to actually look.]\nexport const OTHER_ROUTES = \"A deposit paid by Venmo, Zelle or a cheque does not reach the card system, so it will not show here.\";\n// HER OTHER DEPOSIT. The same money page publishes a $250 non-refundable TRAINING deposit — which\n// is exactly what five dogs owe at $50 each. The per-dog rule widened the set of amounts that can\n// clear a stay from {$50} to {$50, $100, $150, ...}, and $250 is now in it. Nothing in the data\n// says which a $250 payment was for, so the row says so rather than quietly picking one.\nexport const TRAINING_DEPOSIT = 250;\n/** A SINGLE PAYMENT FOR A MULTI-DOG DEPOSIT IS WEAKER EVIDENCE THAN ONE $50 PER DOG, and the\n * per-dog rule quietly widened the amounts that can clear a stay from {$50} to {$50, $100, $150,\n * $200, $250, ...}. Her published boarding rates are $30-$65 a day, so five nights at $30 is $150\n * — a three-dog deposit — and the total is settled at drop-off, inside the search window. $250\n * is her training deposit exactly. Flagging only $250 patched the rarest collision and left the\n * likelier ones silent. Any lump sum above one dog's deposit now says what else it could be. */\nexport function lumpCaveat(due: number): string {\n // The count comes from the amount due, so a four-dog stay is told four and not \"two or three\" —\n // which was $100-$150 of advice printed on a $200 row, contradicting the rule the same row was\n // applying.\n if (due === TRAINING_DEPOSIT) return ` Worth an eye: $${TRAINING_DEPOSIT} is also what a training deposit costs, so this one payment could be either.`;\n if (due > DEPOSIT) return ` Worth an eye: one payment of this size could also be the boarding total rather than the deposit. ${due / DEPOSIT} separate $${DEPOSIT} payments would be clearer.`;\n return \"\";\n}\nexport const NEAR_WINDOW_BEFORE = 30; // a deposit can be taken before the booking is typed in\n\n/** Every card payment close enough to this stay to be worth putting in front of Kim. */\nexport function paymentsNearStay(stay: Stay, payments: Payment[]): Payment[] {\n if (!stay.bookedAt) return [];\n const lo = shiftDays(stay.bookedAt.slice(0, 10), -NEAR_WINDOW_BEFORE);\n const hi = shiftDays(stay.until || stay.day, 1);\n return payments.filter((p) => {\n const d = (p.at || \"\").slice(0, 10);\n return d >= lo && d <= hi;\n });\n}\n\nconst MONTHS = [\"Jan\", \"Feb\", \"Mar\", \"Apr\", \"May\", \"Jun\", \"Jul\", \"Aug\", \"Sep\", \"Oct\", \"Nov\", \"Dec\"];\n/** \"2026-07-21\" -> \"Jul 21\", the same way round as the stay dates on the card. Kim is American and\n * a row that says \"Nov 25 to Nov 28\" beside \"$50.00 on 21 Jul\" makes her read the date twice. */\nexport function prettyDay(iso: string | null | undefined): string {\n const m = /^(\\d{4})-(\\d{2})-(\\d{2})/.exec(String(iso ?? \"\"));\n return m ? `${MONTHS[Number(m[2]) - 1] ?? m[2]} ${Number(m[3])}` : \"\";\n}\n/** \"Oct 5\", \"Oct 5 and Oct 6\", \"Oct 5, Oct 6 and Oct 7\" — never \"a and b and c\". */\n/** \"on Nov 20\" when three dogs were paid for in one visit, rather than \"on Nov 20, Nov 20 and\n * Nov 20\" — which is how a family of three actually pays, at the counter, in one go. */\nexport function sameDayList(days: string[]): string {\n const uniq = [...new Set(days)];\n return uniq.length === 1 ? `on ${uniq[0]}` : `on ${humanList(uniq)}`;\n}\nexport function humanList(items: string[]): string {\n if (items.length <= 1) return items[0] ?? \"\";\n return `${items.slice(0, -1).join(\", \")} and ${items[items.length - 1]}`;\n}\n/** \"$50.00 on Dec 20\" for three taps on the same day, not the same line three times — which is\n * what a four-dog family paying at the counter produced, and reads as a rendering fault. */\nconst listPayments = (ps: Payment[]) => {\n const byAmountAndDay = new Map();\n for (const p of ps) {\n const day = prettyDay(p.at);\n const k = `${p.amount}|${day}`;\n const prev = byAmountAndDay.get(k);\n if (prev) prev.n++;\n else byAmountAndDay.set(k, { amount: p.amount, day, n: 1 });\n }\n return [...byAmountAndDay.values()]\n .map((g) => `${g.n > 1 ? `${g.n} payments of ` : \"\"}$${g.amount.toFixed(2)} on ${g.day}`)\n .join(\", \");\n};\n\nexport function shiftDays(day: string, delta: number): string {\n const d = new Date(`${day}T00:00:00Z`);\n if (isNaN(d.getTime())) return day;\n d.setUTCDate(d.getUTCDate() + delta);\n return d.toISOString().slice(0, 10);\n}\n\n/** could_not_check NEVER collapses into none_seen. A failed read must not read as \"she owes\". */\nexport function statusFor(\n stay: Stay,\n payments: Payment[] | null,\n // WHAT THE ROW SHOWS vs WHAT THE ROW IS SETTLED BY. `payments` is the money still unspent, which\n // is what may settle this stay. `opts.all` is everything on the account, which is what Kim can\n // see in Square. [was: one list for both, so a stay whose money had already been counted against\n // an earlier stay was told \"no card payment is on file around it AT ALL\" — with the payment\n // sitting right there in her window. 7.9% of generated rows. One step from an accusation, and\n // false: she phones, the customer says \"I paid on the 20th\", and they did.]\n opts: { all?: Payment[]; alreadyCounted?: Set } = {},\n): StayStatus {\n if (payments === null) {\n return { stay, state: \"could_not_check\", amountSeen: 0,\n note: \"We could not read this person's payments just now, so this one is unknown. It is not a finding either way.\" };\n }\n // No booking date means no window to search, so there is no honest answer here.\n // [was: the range fell back to the beginning of time, and a payment from 2019 cleared the stay.]\n if (!stay.bookedAt) {\n return { stay, state: \"could_not_check\", amountSeen: 0,\n note: \"This booking has no record of when it was made, so there is no period to check a deposit against. It is not a finding either way.\" };\n }\n const near = collapseSameMoney(paymentsNearStay(stay, opts.all ?? payments)).kept;\n // THE ONLY THING THAT CLEARS A STAY: a card payment for exactly the deposit. Everything else\n // gets shown to Kim with its date and left to her, because nothing in the data says what a\n // payment was for and two goes at guessing have both cost her money.\n const due = depositDue(stay);\n const dogs = dogsOn(stay);\n // TWO SHAPES OF EXACT EVIDENCE, and nothing else clears a stay: one payment for the whole\n // amount due, or one $50 payment per dog. Both are exact-amount matches. Summing whatever else\n // is on the account is what cleared a customer on a training package two versions ago.\n const exact = qualifyingPayments(stay, payments);\n const ids = new Set(exact.map((p) => p.id));\n const rest = near.filter((p) => !ids.has(p.id));\n // Money that IS in this stay's window but has already paid for one of this customer's earlier\n // stays. Naming it is the difference between an honest row and a false one.\n const counted = rest.filter((p) => opts.alreadyCounted?.has(p.id));\n const countedNote = counted.length\n ? ` ${counted.length === 1 ? `A card payment of $${counted[0].amount.toFixed(2)} on ${prettyDay(counted[0].at)} is` : `${counted.length} card payments totaling $${counted.reduce((n, p) => n + p.amount, 0).toFixed(2)} are`} around this stay too, but ${counted.length === 1 ? \"it has\" : \"they have\"} already been counted against ${counted.length === 1 ? \"an earlier stay\" : \"earlier stays\"} of theirs.`\n : \"\";\n const others = rest.filter((p) => !opts.alreadyCounted?.has(p.id));\n const restNote = (others.length\n ? ` ${others.length === 1 ? \"There is also 1 other card payment\" : `There are also ${others.length} other card payments`} on this account around this stay: ${listPayments(others)}.`\n : \"\") + countedNote;\n if (exact.length) {\n // TWO DIFFERENT PAYMENTS CAN SHARE AN AMOUNT AND A DAY, and then the settled one and the\n // left-over one render identically — which makes a correct allocation look exactly like the\n // money bug this module has fought five times. Say how many landed.\n const twinDay = exact.length === 1\n ? near.filter((p) => p.amount === exact[0].amount && prettyDay(p.at) === prettyDay(exact[0].at)).length\n : 1;\n const ofN = twinDay > 1 ? ` (one of ${twinDay} payments of that amount that day)` : \"\";\n return { stay, state: \"seen\", amountSeen: due,\n note: exact.length === 1\n ? `A card payment for exactly $${due.toFixed(2)} is on file on ${prettyDay(exact[0].at)}${ofN}, which is the deposit for ${dogs === 1 ? \"1 dog\" : `${dogs} dogs`}.${lumpCaveat(due)}${restNote}`\n : `${exact.length} card payments of $${DEPOSIT}.00 are on file, one per dog, ${sameDayList(exact.map((p) => prettyDay(p.at)))}. That is the $${due.toFixed(2)} due for ${dogs} dogs.${restNote}` };\n }\n if (near.length) {\n // SPLIT, deliberately. `others` is money Kim could still match to this stay; `counted` is money\n // that is around it but has already paid for one of the same customer's earlier stays. Lumping\n // them together is how a row ends up implying she has been paid twice, or not at all.\n // A PAYMENT CAN BE SHOWN AND NOT COUNTED. `near` is what Kim can see in this stay's window;\n // `exact` is what may settle it. A record whose fold-twin survives OUTSIDE the window is in the\n // first and not the second, and the row then denied a $50 match one clause before printing\n // \"$50.00 on Oct 15\". 1.3% of rows. The module's own header names that exact sentence shape as\n // the v2 bug it fixed, so it cannot be allowed back in a different branch.\n const blocked = others.filter((p) => p.amount === due || p.amount === DEPOSIT);\n const why = blocked.length\n ? `Square records the same money again outside this stay, so ${blocked.length === 1 ? \"it has\" : \"they have\"} not been counted here`\n : \"nothing unspent on file matches that amount\";\n const shown = others.length\n ? `${others.length === 1 ? \"1 card payment is\" : `${others.length} card payments are`} on file around it: ${listPayments(others)}. Worth a look to see whether the deposit is ${others.length === 1 ? \"that one\" : \"among them\"}.`\n : \"Nothing else on this account is unaccounted for around it.\";\n return { stay, state: \"partial\", amountSeen: others.reduce((n, p) => n + p.amount, 0),\n note: `The deposit on this stay is $${due.toFixed(2)} (${dogs === 1 ? \"1 dog\" : `${dogs} dogs`} at $${DEPOSIT}), and ${why}. ${shown}${countedNote}` };\n }\n return { stay, state: \"none_seen\", amountSeen: 0,\n note: `The deposit on this stay is $${due.toFixed(2)} (${dogs === 1 ? \"1 dog\" : `${dogs} dogs`} at $${DEPOSIT}) and no card payment is on file around it at all. ${OTHER_ROUTES}` };\n}\n\n/** ONE PAYMENT, ONE STAY.\n *\n * statusFor answers about a single stay and is handed the customer's whole payment list, so a\n * regular who books Thanksgiving AND Christmas in the same phone call and pays one $50 deposit\n * had BOTH stays marked settled. Kim was owed $100, $50 arrived, and neither row reached the\n * shortlist. That is the exact failure the module says it exists to prevent, and it is the\n * ordinary case rather than an edge — the two windows are six weeks apart and the search window\n * around each booking overlaps almost completely.\n *\n * So the payments are ALLOCATED. Each exact-deposit payment settles at most one stay, earliest\n * drop-off first, and a payment already spent on one stay is invisible to the next. */\nexport function statusesForCustomer(stays: Stay[], payments: Payment[] | null): StayStatus[] {\n // TIE-BROKEN, not just sorted. [was: `a.day.localeCompare(b.day)` alone. JavaScript's sort is\n // stable, so two stays on the SAME DAY stayed in whatever order the caller passed them, and the\n // one that happened to be first took the money. Same customer, same payments, same day, two\n // bookings: which one reads \"Payment on file\" was decided by array order. Found by shuffling\n // the input 464,000 times. The tie-break is the booking date first — the stay she booked\n // earlier is the one an earlier payment belongs to — then fields that identify the stay, so\n // the answer is the same on every run.]\n const key = (s: Stay) => `${s.day}|${s.bookedAt ?? \"\"}|${s.until ?? \"\"}|${dogsOn(s)}|${(s.dogs ?? []).join(\",\")}`;\n const ordered = [...stays].sort((a, b) => a.day.localeCompare(b.day) || key(a).localeCompare(key(b)));\n if (payments === null) return ordered.map((s) => statusFor(s, null));\n // COLLAPSED ONCE, HERE, BEFORE ANYTHING IS ALLOCATED.\n // [was: statusFor collapsed internally and the allocator marked only the SURVIVING id as spent,\n // so the folded twin was still visible to the next stay. The same two records were read as one\n // payment when judging a stay and as two when allocating across them, and one $50 deposit that\n // Square had written twice — the exact direct+matched pair live on her account — cleared TWO\n // holiday stays, quoting two different dates so it read as two deposits.]\n const money = collapseSameMoney(payments).kept;\n const spent = new Set();\n return ordered.map((s) => {\n const available = money.filter((p) => !spent.has(p.id));\n // `all` IS THE RAW LIST, not the globally collapsed one. [was: `all: money`, and the docstring\n // for `all` says \"everything on the account, which is what Kim can see in Square\" — which the\n // collapsed list is not. A till record folded against a payment OUTSIDE this stay's window\n // vanished from the display, and the row printed the banned sentence: a customer who paid BOTH\n // deposits, fourteen days apart, had her Thanksgiving row read \"no card payment is on file\n // around it at all\". Adding a later payment turned a settled stay into \"nothing at all\".\n // statusFor collapses `all` itself, scoped to this stay's own window, which is the only scope\n // where \"same money\" is a reading rather than a guess.]\n const st = statusFor(s, available, { all: payments, alreadyCounted: new Set(spent) });\n if (st.state === \"seen\") {\n // EARLIEST DROP-OFF FIRST, and the earliest qualifying payment settles it. Both halves are\n // deliberate and both are pinned by H48: without an order, which stay gets the money is\n // whichever way the array happened to arrive.\n // COMPUTED EXACTLY AS statusFor COMPUTES THE ONE IT QUOTES, so the record Kim reads on the\n // row is the record that gets debited. Since collapseSameMoney is idempotent this second\n // pass is a no-op on already-collapsed money, and there is deliberately no control for it:\n // a control that cannot fail is worse than none. H57 is what guards the idempotency this\n // relies on. [was: paymentsNearStay without the collapse, which diverged from the quote.]\n // EVERY payment that settled it, not one of them. [was: `.find(p => p.amount === DEPOSIT)`,\n // which debited nothing at all when a multi-dog stay was settled by one lump sum, and one of\n // N when it was settled per dog. Same money, two stays, both green.]\n for (const p of qualifyingPayments(s, available)) spent.add(p.id);\n }\n return st;\n });\n}\n\n/** The kill switch. If the payment feed itself looks dead, say so instead of telling Kim that\n * every single customer owes her money.\n *\n * MIN_SAMPLE exists because of what happened on the first live run, 6 Aug 15:41Z. Two holiday\n * stays were booked, neither customer had a Square note, and the switch fired: Kim would have\n * been shown \"the payment feed has stopped\" on the strength of two people. Two customers with no\n * Square payment is an ordinary Tuesday, not evidence of an outage. Below the floor the list is\n * shown with its usual caveats, which is the honest reading of a small sample.\n *\n * IT COUNTS CUSTOMERS, NOT BOOKINGS. [was: one entry per stay, so a single regular with five\n * holiday drop-offs and a habit of paying cash cleared the floor on their own and suppressed the\n * whole card. Her real data has one contact with 24 drop-offs. The docstring said \"customers\"\n * and the code counted rows.] */\nexport const MIN_SAMPLE_FOR_DEAD_FEED = 5;\nexport function feedLooksDead(perCustomer: Map | Payment[][], minSample = MIN_SAMPLE_FOR_DEAD_FEED): boolean {\n const lists = perCustomer instanceof Map ? [...perCustomer.values()] : perCustomer;\n return lists.length >= minSample && lists.every((p) => p.length === 0);\n}\n\n/** The sentence Kim reads. Generated from the counts, so the words cannot disagree with them. */\n// Takes anything carrying a `state`, not a full StayStatus: the dashboard regenerates this line\n// from the rows it is about to render, so the two cannot disagree, and a DepositRow is not a Stay.\nexport function depositSentence(statuses: readonly { state: StayStatus[\"state\"] }[], feedDead: boolean): string {\n if (statuses.length === 0) {\n return \"No holiday boarding stays are booked in the deposit windows yet, so there is nothing to check.\";\n }\n const none = statuses.filter((s) => s.state === \"none_seen\").length;\n const partial = statuses.filter((s) => s.state === \"partial\").length;\n const seen = statuses.filter((s) => s.state === \"seen\").length;\n const unknown = statuses.filter((s) => s.state === \"could_not_check\").length;\n if (feedDead) {\n // The old wording claimed \"no Square payment has been recorded against ANYBODY\", which was a\n // claim about people the run had never managed to read. It now says how many it actually read.\n const checked = statuses.length - unknown;\n if (checked <= 0) {\n return `There ${statuses.length === 1 ? \"is 1 holiday stay\" : `are ${statuses.length} holiday stays`} booked, and ${statuses.length === 1 ? \"it could not be checked\" : \"none of them could be checked\"} just now, so there is nothing to report either way yet.`;\n }\n return `There ${statuses.length === 1 ? \"is 1 holiday stay\" : `are ${statuses.length} holiday stays`} booked, and no card payment shows against ${checked === statuses.length ? (statuses.length === 1 ? \"it\" : \"any of them\") : (checked === 1 ? \"the one we could check\" : `any of the ${checked} we could check`)}. That pattern usually means the payment feed has stopped rather than that nobody has paid, so the list is being held back until that is checked.`;\n }\n const bits: string[] = [];\n bits.push(`${statuses.length} holiday ${statuses.length === 1 ? \"stay is\" : \"stays are\"} booked.`);\n if (seen) bits.push(`${seen} ${seen === 1 ? \"has a card payment\" : \"have a card payment\"} on file.`);\n if (none || partial) {\n const n = none + partial;\n // NO FIXED FIGURE HERE. The deposit is $50 per dog, so the amount due differs per row: the\n // headline said \"we cannot find a $50 payment\" above a three-dog stay that owes $150. Each\n // row states its own amount; the headline states none.\n // \"the deposit for it\", not \"what is owed on it\". [was: \"owed\", which is the vocabulary of a\n // debt list. The card's own closing sentence exists to say this is not one, and every other\n // string on it was already careful about this. Plainer, and it names the actual figure's name.]\n bits.push(`${n} ${n === 1 ? \"is worth checking\" : \"are worth checking\"}: we cannot find a card payment matching the deposit for ${n === 1 ? \"it\" : \"them\"}.`);\n }\n if (unknown) bits.push(`${unknown} could not be checked just now.`);\n bits.push(`${OTHER_ROUTES} This is a shortlist to look at rather than a list of people who owe you.`);\n return bits.join(\" \");\n}\n",[286],"cf871b7e-27d1-45fc-86d6-2728463eb67f","facts.ts","ac8030d4-904a-11f1-a8a4-1607ee4eb77e",489,["D",1786309575802],6,"// ONE SOURCE OF TRUTH PER FACT. v1.0, 4 Aug 2026.\n//\n// THE ROOT CAUSE THIS FILE EXISTS TO KILL:\n// Prose and data were produced separately. Somebody wrote a sentence, something else computed a\n// number, and nothing forced them to agree. Every wrong claim in this project came from that gap:\n// - \"runs every 15 minutes\" beside a timestamp reading 26 minutes ago\n// - \"1,513 records\" that had drifted to 1,514 before a reader saw it\n// - \"35 counter sales totaling $23,463.99\" when the journal holds 40 totalling $28,035.99\n// - \"11 live questions\" in a handover doc while the page rendered 13\n// None of those were typos. Each was a sentence that had no mechanical link to its own subject.\n//\n// THE RULE: a fact is computed once, here, together with the sentence that describes it. Anything\n// that displays it reads from here. If two files can produce the same number independently, one of\n// them is wrong and nobody knows which.\n//\n// EVERY FACT CARRIES ITS PROVENANCE: where it was read and when. `Fact.source` answers \"where did\n// this number come from\" in one hop, which is the test for whether it ships.\n\nexport type Fact = {\n value: T | null; // null means NOT KNOWN, never zero-by-accident\n source: string; // the endpoint or blob it came from, in one hop\n readAt: string; // ISO timestamp of the read that produced it\n note?: string; // anything the reader must know to use it honestly\n};\n\n// Written as function DECLARATIONS rather than generic arrows on purpose.\n// [was: `export const fact = (value: T | null, ...)`. Inside the val that compiles fine, and\n// the dashboard has always rendered correct numbers from it. But esm.town, which is how any\n// OTHER val would import this file, parses a .ts file as .tsx: it read `` as an opening JSX\n// tag and served `export const fact = _jsxs(T, { children: [\"(value: T | null, source...\"] })`\n// — the type signature turned into React children. Anything importing it got garbage that would\n// have thrown at call time, not at import time. The watchdog needs to import this file so that\n// the Square backlog is computed in exactly one place; `function fact(` is unambiguous to\n// both parsers, so it can.]\nexport function fact(value: T | null, source: string, note?: string): Fact {\n return { value, source, readAt: new Date().toISOString(), note };\n}\n\n/** A fact that could not be read. Distinct from a fact whose value is genuinely zero. */\nexport function unknownFact(source: string, note?: string): Fact {\n return { value: null, source, readAt: new Date().toISOString(), note };\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE SQUARE BACKLOG. Previously four numbers typed into a sentence: \"35 counter sales totaling\n// $23,463.99. 14 of the 35 carry enough of a trail; the other 21 arrived with no name.\"\n// An independent re-derivation found 40 / $28,035.99 / 10 / 30. The typed version understated the\n// unlinked money by $4,572 and understated the unresolvable count by 9. It is computed now.\n//\n// The subtlety that makes this worth a function rather than a one-liner: the bridge RE-LOGS the\n// same payment on every retry, so 87 journal rows collapse to 40 distinct payments. Summing rows\n// instead of payments gives $56,369.97, which is double-counting, not a bigger truth.\n// ---------------------------------------------------------------------------------------------\n\nexport type SquareBacklog = {\n payments: number; // distinct payment ids that never matched a contact\n total: number; // their summed value, counting each payment once\n withTrail: number; // carry an email, phone or Square customer id: recoverable with effort\n withTrailTotal: number;\n noTrail: number; // arrived with nothing at all: no permission will ever resolve these\n noTrailTotal: number;\n};\n\n// FIXED 9 Aug 2026. The loop below used to start `if (r.kind !== \"NO-MATCH\") continue`, which\n// meant the comment about reading \"ANY row for this payment\" was a lie: only NO-MATCH rows were\n// ever seen. A payment that failed to match on the first attempt and matched on a later one was\n// still counted as unmatched forever. That overstated the backlog Kim was shown by $10,884.00\n// across 9 payments: 42 payments / $33,535.99 reported, 33 / $22,651.99 true. She has the wrong\n// figure in writing, so this is a correction owed, not just a cleanup.\n// A payment is only unmatched if NO row anywhere in the journal ties it to a contact.\nconst MATCHED_KINDS = new Set([\"REVENUE-ON-CLIENT-OPP\", \"PAYMENT\", \"CAPI-PURCHASE\", \"INVOICE-LINKED\"]);\nexport function squareBacklog(journal: unknown): SquareBacklog | null {\n if (!Array.isArray(journal)) return null;\n const rowsFor = new Map();\n for (const r of journal as any[]) {\n const m = /payment\\s+(\\S+)/.exec(String(r?.note ?? \"\"));\n if (!m) continue; // an unparseable note is not a payment we can count\n (rowsFor.get(m[1]) ?? rowsFor.set(m[1], []).get(m[1])!).push(r);\n }\n const byPayment = new Map();\n for (const [id, rs] of rowsFor) {\n if (!rs.some((r) => r?.kind === \"NO-MATCH\")) continue; // never failed: not a backlog item\n if (rs.some((r) => MATCHED_KINDS.has(r?.kind) || (typeof r?.contactId === \"string\" && r.contactId.length > 4))) continue; // matched later\n const amt = rs.map((r) => Number(r?.amount) || 0).find((a) => a > 0) ?? 0;\n const trail = rs.some((r) => r?.hadEmail === true || r?.hadPhone === true || r?.hadCustomerId === true);\n byPayment.set(id, { amt, trail });\n }\n const rows = [...byPayment.values()];\n const sum = (f: (x: { amt: number; trail: boolean }) => boolean) =>\n rows.filter(f).reduce((a, x) => a + x.amt, 0);\n return {\n payments: rows.length,\n total: rows.reduce((a, x) => a + x.amt, 0),\n withTrail: rows.filter((x) => x.trail).length,\n withTrailTotal: sum((x) => x.trail),\n noTrail: rows.filter((x) => !x.trail).length,\n noTrailTotal: sum((x) => !x.trail),\n };\n}\n\n// ---------------------------------------------------------------------------------------------\n// SENTENCES ARE GENERATED FROM VALUES, NEVER COMPOSED ALONGSIDE THEM.\n// Each of these takes the fact and returns the words. There is no path by which the words can\n// describe a different number from the one passed in, because there is only one number.\n// ---------------------------------------------------------------------------------------------\n\nconst money = (n: number) => `$${n.toLocaleString(\"en-US\", { minimumFractionDigits: 2, maximumFractionDigits: 2 })}`;\n\nexport function squareSentence(b: SquareBacklog | null): string {\n if (!b || b.payments === 0) {\n return \"We could not read the payment records just now, so there is nothing to report here rather than a zero to trust.\";\n }\n const parts = [\n `${b.payments} counter sales totaling ${money(b.total)} are recorded but not linked to a name.`,\n ];\n if (b.withTrail) {\n parts.push(`${b.withTrail} of them, worth ${money(b.withTrailTotal)}, carry enough of a trail to be matched with effort.`);\n }\n if (b.noTrail) {\n parts.push(`The other ${b.noTrail}, worth ${money(b.noTrailTotal)}, arrived with no name, email or phone attached at all, and nothing will ever resolve those.`);\n }\n parts.push(\"Either way it is old filing rather than missing money.\");\n return parts.join(\" \");\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE PHONE-CALL OMISSION. Two facts sat on the page and were never joined: a channel bucket\n// labelled \"somewhere else\" holding 20 people, and a separate line saying the old source column\n// logged 22 phone calls. An independent cross-tab showed the \"other\" bucket is 20 of 20 phone\n// calls, 100%. The page had the answer twice and printed it as a shrug. Computed now.\n// ---------------------------------------------------------------------------------------------\n\nexport type ContactLike = {\n source?: string | null;\n attribution?: { medium?: string | null } | null;\n dateAdded?: string;\n};\nexport type Win = { startMs: number; endMs: number };\n\n/**\n * What share of the un-named \"other\" medium bucket is explained by phone calls?\n *\n * THE WINDOW IS MANDATORY, and this is not defensive typing. The first version of this function\n * took no window, so it counted every contact ever fetched (nine weeks) and rendered \"all 192 of\n * them are logged as phone calls\" directly beneath a bar that read 20. Same disease, in the code\n * written to cure it: a sentence describing a different population from the chart above it.\n * A caller that cannot supply the window gets null rather than a number from the wrong period.\n */\nexport function otherBucketExplanation(contacts: ContactLike[] | null, w: Win | null): { other: number; phoneInOther: number } | null {\n if (!Array.isArray(contacts) || !contacts.length || !w) return null;\n const inWin = (c: ContactLike) => {\n const t = Date.parse(c.dateAdded ?? \"\");\n return Number.isFinite(t) && t >= w.startMs && t < w.endMs;\n };\n const scoped = contacts.filter(inWin);\n if (!scoped.length) return null;\n const isOther = (c: ContactLike) => /^other$/i.test(String(c.attribution?.medium ?? \"\").trim());\n const isPhone = (c: ContactLike) => /phone/i.test(String(c.source ?? \"\"));\n return {\n other: scoped.filter(isOther).length,\n phoneInOther: scoped.filter((c) => isOther(c) && isPhone(c)).length,\n };\n}\n\nexport function otherBucketSentence(x: { other: number; phoneInOther: number } | null): string {\n if (!x || x.other === 0) return \"\";\n if (x.phoneInOther === 0) {\n return `The ${x.other} filed as \"somewhere else\" carry an arrival record that just says \"other\", and none of them match a logged phone call, so we genuinely cannot place them.`;\n }\n const all = x.phoneInOther === x.other;\n return all\n ? `Worth knowing what \"somewhere else\" actually is: all ${x.other} of them are logged in your CRM as phone calls. Your arrival record has no category for a call, so people who rang you land in that bucket. They are not unknown, they are your callers.`\n : `${x.phoneInOther} of the ${x.other} filed as \"somewhere else\" are logged in your CRM as phone calls. Your arrival record has no category for a call, so callers land in that bucket rather than one of their own.`;\n}\n\n// ---------------------------------------------------------------------------------------------\n// CROSS-ARTIFACT REGISTRY. Any fact that appears in more than one place (page, PDF, ledger, a\n// message to the client) is registered here by name. The consistency test walks this list and\n// fails the build when two artefacts state the same named fact differently. Drift becomes\n// impossible rather than merely unlikely.\n// ---------------------------------------------------------------------------------------------\n\nexport type SharedFact = {\n name: string; // stable id\n pattern: RegExp; // how it appears in prose, capturing the value\n describe: string; // what it is, for the failure message\n};\n\nexport const SHARED_FACTS: SharedFact[] = [\n { name: \"decision_count\", pattern: /(\\d+)\\s+(?:live\\s+)?questions?\\s+(?:on this page\\s+)?(?:are|is)?\\s*wait/i, describe: \"how many questions are waiting on Kim\" },\n { name: \"bootcamp_bookings\", pattern: /(\\d+)\\s+Bootcamp bookings/i, describe: \"Bootcamp bookings on record\" },\n { name: \"bootcamp_ceiling\", pattern: /\\$([\\d,]+)\\s*(?:,|\\.|and|$)/i, describe: \"the Bootcamp exposure ceiling\" },\n { name: \"slow_track_len\", pattern: /(\\d+)\\s+more spread over about\\s+(\\d+)\\s+months/i, describe: \"the slow track length\" },\n { name: \"automations\", pattern: /(?:all\\s+)?(\\d+)\\s+automations/i, describe: \"automations in the account\" },\n];\n\n// ---------------------------------------------------------------------------------------------\n// THE TAG THAT DECIDES WHETHER GO-LIVE REACHES ANYBODY.\n// The engine enrolls on the tag `nurture - puppy`. If nothing applies it, switching the sequence\n// on reaches nobody, and it looks healthy while doing so: the engine reports successful runs with\n// zero enrollments, which is exactly what a working system with no work also looks like.\n//\n// [was: the page said \"1,200 of your most recent contacts were checked and not one carries the\n// tag\". True when it was typed, and a scan size rather than an answer: it left open whether the\n// other four thousand were different. GoHighLevel will filter contacts by tag server-side and\n// return a total, so the real number is one call away. Cross-checked 5 Aug against a full walk of\n// all 5,544 contacts, page by page: \"no sale\" 133, \"tips-nurture\" 155, \"customer\" 1,512, and\n// `nurture - puppy` zero. The filter and the census agree on every one.]\n// ---------------------------------------------------------------------------------------------\nexport type TagCoverage = { tag: string; tagged: number; total: number };\n\nexport function tagCoverageSentence(t: TagCoverage | null): string {\n if (!t || t.total <= 0) {\n return \"We could not read your contact records just now, so this says nothing rather than a zero worth trusting.\";\n }\n if (t.tagged === 0) {\n return `Every one of your ${t.total.toLocaleString(\"en-US\")} contact records was checked just now, and not a single one is marked as a puppy inquiry. Nothing in your account applies that mark, which is why the tagging has to be switched on at the same moment as everything else.`;\n }\n const pct = Math.round((t.tagged / t.total) * 100);\n // [was: \"1 ... are marked ... Those are the people\" — a real reader hit the n=1 case on 9 Aug\n // and the plural read as a glitch on a page that trades on precision. Number agreement is now\n // computed from the count, never assumed.]\n const one = t.tagged === 1;\n return `${t.tagged.toLocaleString(\"en-US\")} of your ${t.total.toLocaleString(\"en-US\")} contact records ${one ? \"is\" : \"are\"} marked as a puppy inquiry, checked just now, which is ${pct < 1 ? \"under 1\" : pct}% of them. ${one ? \"That is the one person\" : \"Those are the people\"} the new messages would pick up.`;\n}\n",[294],"308a6490-dbe9-4d25-aa30-f21963c7b9c7","deposits.ts","2e97d0d2-91ad-11f1-a57d-1607ee4eb77e",386,["D",1786072341597],"// HOLIDAY DEPOSIT COLLECTOR. The only part of this feature that touches her CRM. v1.0, 6 Aug 2026.\n//\n// WHY IT IS A SEPARATE FILE. holiday-deposits.ts holds all the judgement and a test asserts that\n// it contains no fetch() and no write verb at all. That assertion is only worth something if the\n// network code lives somewhere else, so it lives here. This file fetches and stores; it decides\n// nothing. Every decision is made by a function imported from the module that cannot reach the\n// network.\n//\n// WHAT IT DOES, IN ORDER\n// 1. asks both Boarding Drop Off calendars for the events inside this season's deposit windows\n// 2. groups them into stays (one customer, one day, however many dogs)\n// 3. reads each of those customers' notes, which is where Square money lands\n// 4. writes the answer into the `holiday_deposits` blob\n// The dashboard renders that blob and never repeats any of this, so Kim's page stays fast and\n// cannot be broken by a slow CRM.\n//\n// GET ONLY. Every request in here is a GET. There is no code path that tags, messages, moves or\n// updates anybody, and there is no argument that makes one appear.\n//\n// A FAILED READ IS NOT A ZERO. If a customer's notes cannot be read, that customer is recorded as\n// unknown, with the reason, and stays unknown all the way to Kim's screen. The one thing this\n// feature must never do is turn a network hiccup into \"this person has not paid\".\n//\n// ?k= the stored answer, as JSON\n// ?k=&run=1 re-collect from the live CRM, then store and return it\ndeclare const Deno: { env: { get(k: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\nimport {\n holidayWindows, seasonYear, groupIntoStays, parseSquarePayments, statusFor, feedLooksDead,\n depositSentence, paymentsNearStay, statusesForCustomer, shiftDays, businessDay, type CalEvent, type Payment, type StayStatus,\n} from \"./holiday-deposits.ts\";\n\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\n// Both drop-off calendars. One customer appears on BOTH of these in her live data, which is why\n// the union is taken rather than whichever one someone remembers first.\nexport const BOARDING_CALENDARS = [\"wS5N8WN4BbzznaLjEg1N\", \"ZmmjQJszkRMUltfEbumB\"];\n// The matching PICK UP calendars. A drop-off appointment is a ten minute handover slot, so the\n// only place the length of a stay is written down is here. Read on 6 Aug: Ghost and Chewy drop\n// off on 25 Nov and are collected on the 28th, and nothing on the drop-off calendar says that.\nexport const PICKUP_CALENDARS = [\"1FnbK7pQp1ViZWIzX9SR\", \"bN6wWGJa0qKq0QGRg4CC\"];\n// How far past the last window to look for the pick-up that ends a stay running over New Year.\nexport const LOOKAHEAD_DAYS = 30;\nexport const BLOB_KEY = \"holiday_deposits\";\n// How far before the first holiday window to look for bookings. A stay that starts earlier and\n// runs into the window is still a holiday stay; the query filters on drop-off time, so it has to\n// be fetched before it can be judged.\nexport const LOOKBACK_DAYS = 21;\n// The notes endpoint takes NO paging parameters (it 422s on limit and on offset), so the only\n// defence against a silently truncated list is to treat a response at the cap as unreadable.\n// 100 is the usual GHL page size; the largest real list across 60 sampled contacts was 3.\nexport const NOTES_UNPAGEABLE_CAP = 100;\n// How often the list is refreshed off the engine's schedule.\nexport const REFRESH_EVERY_MS = 3_600_000;\n// The ATTEMPT stamp, written on every try. Gating on the stored list instead means a run that\n// legitimately declines to store — no credential, no calendar, everybody unreadable, an empty\n// season held back — leaves the gate open, and the engine then retries every 15 minutes forever\n// against a CRM that is already unwell.\nexport const ATTEMPT_KEY = \"holiday_deposits_attempt\";\n\n/** Is it time to look again? Pure, so the rule can be tested instead of inspected as text.\n * An unreadable or missing stamp opens the gate: never having looked, and not being able to tell\n * when we last looked, both mean look now. A NaN must not close it forever. */\n/** THE WHOLE \"should I collect now\" STEP, in one place, so both schedules run the same code and a\n * test can watch it decide. [was: hand-rolled in main.ts and again in deposits-cron.ts, checked\n * by greps for the word `needsRefresh`. A mutation that called needsRefresh and threw the answer\n * away — collecting from her CRM on every tick — passed all three of those greps.] */\nexport async function refreshIfDue(\n readStamp: () => Promise<{ at?: string } | null>,\n run: () => Promise<{ ok: boolean; error?: string }>,\n nowMs: number,\n): Promise<{ ran: boolean; why: string }> {\n const last = await readStamp().catch(() => null);\n if (!needsRefresh(last?.at, nowMs)) return { ran: false, why: \"not due yet\" };\n const r = await run();\n return { ran: true, why: r.ok ? \"collected\" : `not stored: ${r.error ?? \"unknown\"}` };\n}\n\nexport function needsRefresh(lastAttemptAt: string | null | undefined, nowMs: number, everyMs = REFRESH_EVERY_MS): boolean {\n if (!lastAttemptAt) return true;\n const t = Date.parse(String(lastAttemptAt));\n if (!Number.isFinite(t)) return true;\n return nowMs - t > everyMs;\n}\n\n/** Whether a finished collection may replace what is stored. Pure, so all four refusals are\n * testable; they used to be reachable only through the live blob and were checked as regexes. */\nexport function decideStore(out: DepositBlob, prev: DepositBlob | null, force = false): { store: boolean; error?: string } {\n // A collection that could not read a single calendar is NOT stored: overwriting a good answer\n // with an empty one would show Kim \"no holiday stays booked\" the first time her CRM blinked.\n if (out.calendarsRead === 0) return { store: false, error: \"no calendar answered, so the stored list was left alone\" };\n // NOR a collection in which every single row is unknown. The calendars answered, so the guard\n // above lets it through, and the blob would be replaced with a page of \"could not check\" AND a\n // fresh timestamp — the content gets worse while the page claims to have just been updated.\n if (out.rows.length > 0 && out.rows.every((r) => r.state === \"could_not_check\")) {\n return { store: false, error: \"nobody's payments could be read, so the stored list was left alone\" };\n }\n // NOR a run that has gone from a real list to nothing. A renamed calendar answers 200 with an\n // EMPTY events array, which is well formed and passes both guards above; in December that\n // silently replaces her shortlist with \"nothing to check\". A season really can empty out, so\n // this is not permanent: it holds the old list, says why, and the card starts ageing visibly.\n if (!force && out.rows.length === 0 && (prev?.rows?.length ?? 0) > 0) {\n return { store: false, error: `the boarding calendars answered but returned no holiday bookings at all, where the stored list has ${prev!.rows.length}. That is usually a renamed calendar rather than an empty season, so the stored list was left alone. Re-run with force=1 to accept it.` };\n }\n // NOR A RUN THAT SEES LESS THAN THE STORED ONE DID.\n //\n // This is the hole the three guards above left open, and it is the worst of the four because it\n // is silent. There are two boarding calendars precisely because one customer can appear on\n // either; the row list is their union. If ONE calendar fails — a transient 5xx, a revoked scope,\n // a rename — `calendarsRead` comes back 1 of 2, every guard above passes, and the partial union\n // is written straight over the complete one. The customers who only ever appear on the calendar\n // that failed do not become \"could not check\" rows. Their bookings were never fetched, so they\n // get NO ROW AT ALL: they vanish off Kim's shortlist entirely, under a banner that says one\n // calendar did not answer but cannot say who is missing. There is no retry anywhere in this\n // file, so one blip is enough. Found on 7 August; nothing guarded it.\n //\n // Compared by how many did NOT answer, not by the raw count, so genuinely deleting a calendar\n // (2 asked and read, then 1 asked and read) still stores.\n const missedNow = (out.calendarsAsked - out.calendarsRead) + (out.pickupsAsked - out.pickupsRead);\n const missedBefore = prev ? (prev.calendarsAsked - prev.calendarsRead) + (prev.pickupsAsked - prev.pickupsRead) : 0;\n if (!force && prev && missedNow > missedBefore) {\n return { store: false, error: `this run could not read ${missedNow} calendar(s) where the stored list was missing ${missedBefore}, so it sees fewer bookings than what is already saved. A shorter list with a newer timestamp is worse than the saved one going visibly stale, so the stored list was left alone.` };\n }\n return { store: true };\n}\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\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}\nasync function authorised(k: string): Promise {\n const expected = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\") || KEY_SHA256;\n const got = await sha256Hex(k);\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\nasync function blobMod() { return (await import(\"https://esm.town/v/std/blob\")).blob; }\nasync function token(): Promise {\n const env = Deno.env.get(\"GHL_TOKEN\");\n if (env) return env;\n const cfg = await (await blobMod()).getJSON(\"puppy_config\").catch(() => null);\n return (cfg as any)?.ghlToken;\n}\n\n// The single door to the network, and it only knows one verb. Named so that a reader checking\n// \"can this thing write to her account\" gets their answer from the signature.\nasync function getJson(path: string, version: string, tok: string): Promise {\n const r = await fetch(`${GHL}${path}`, {\n method: \"GET\",\n // curl's UA is not decoration: her CRM rejects requests without it.\n headers: { Authorization: `Bearer ${tok}`, Version: version, \"User-Agent\": \"curl/8.5.0\" },\n signal: AbortSignal.timeout(20_000),\n });\n if (!r.ok) throw new Error(`HTTP ${r.status}`);\n return r.json();\n}\n\nexport type DepositRow = {\n contactId: string;\n name: string;\n day: string;\n until: string;\n dogs: string[];\n dogCount: number;\n window: string;\n state: StayStatus[\"state\"];\n amountSeen: number;\n note: string;\n};\nexport type DepositBlob = {\n at: string;\n season: number;\n windows: { name: string; from: string; to: string }[];\n rows: DepositRow[];\n sentence: string;\n feedDead: boolean;\n readFailures: number;\n calendarsRead: number;\n calendarsAsked: number;\n pickupsRead: number;\n pickupsAsked: number;\n};\n\nconst dayMs = (d: string) => Date.parse(`${d}T00:00:00Z`);\n\n/** Every page of a contact's notes, or null if we could not be sure we had them all.\n * Returning a SHORT list would be indistinguishable from a customer with no payments, so a read\n * that cannot be completed returns null and the customer is reported as unknown. */\nasync function allNotes(io: { get: (p: string, v: string) => Promise }, contactId: string): Promise {\n // NO QUERY STRING. [was: `?limit=100&offset=N`, written to fix a truncation worry. This endpoint\n // rejects both: it answers 422 \"property limit should not exist\" to any parameter at all, so\n // every customer became a failed read. It shipped, and both live customers came back \"could not\n // check\" ninety seconds later. It was caught by running it against her account, not by the 250\n // assertions that stayed green — the fixtures answered a URL the real CRM refuses.]\n const d = await io.get(`/contacts/${contactId}/notes`, \"2021-07-28\");\n // A 200 with no notes ARRAY is a response we do not understand, not a customer with no notes.\n if (!Array.isArray(d?.notes)) return null;\n // The endpoint takes no paging parameters, so it returns the lot or it does not. If a response\n // ever comes back at exactly the cap, we cannot tell a full list from a truncated one, and an\n // unknown is the only honest answer. Across 60 sampled contacts on 6 Aug the largest was 3.\n if (d.notes.length >= NOTES_UNPAGEABLE_CAP) return null;\n return d.notes;\n}\n\n/** COLLECT. `io` is injected so the whole thing can be run against fixtures in a test without a\n * network, and so there is exactly one place in this file that can talk to her CRM. */\nexport async function collect(\n io: { get: (path: string, version: string) => Promise },\n todayIso: string,\n): Promise {\n const season = seasonYear(businessDay(todayIso));\n const windows = holidayWindows(season);\n const from = windows[0].from, to = windows[windows.length - 1].to;\n\n // ---- the bookings ----\n const events: CalEvent[] = [];\n let calendarsRead = 0;\n for (const cal of BOARDING_CALENDARS) {\n try {\n // LOOK BACK BEFORE THE WINDOW. A dog dropped off on 19 December and collected on the 27th\n // has boarded over Christmas, but the query filters on the drop-off time, so without this\n // reach-back those bookings are never even fetched. windowForRange decides membership.\n // The SAME range as the pick-ups on purpose. [was: drop-offs stopped at the end of the\n // window while pick-ups reached 30 days past it, so for every stay at the tail of the season\n // the customer's own next booking was never fetched. `nextDrop` came back undefined, the\n // \"hard upper bound\" was structurally blind exactly where it mattered, and a 30 Dec stay\n // swallowed the 15 Jan pick-up of a 10 Jan booking — rendering \"Dec 30 to Jan 15\" and\n // letting a January payment settle the holiday deposit. Out-of-window bookings fetched this\n // way are filtered out by the overlap rule; they are here to be next-drop-off markers.]\n const q = `locationId=${LOC}&calendarId=${cal}&startTime=${dayMs(shiftDays(from, -LOOKBACK_DAYS))}&endTime=${dayMs(shiftDays(to, LOOKAHEAD_DAYS))}`;\n const d = await io.get(`/calendars/events?${q}`, \"2021-04-15\");\n // A 200 that does not carry an events ARRAY is not an empty calendar, it is a response we do\n // not understand. [was: `d?.events ?? []`, which counted a renamed key, a partial payload or\n // a stale calendarId as \"read, and she has no bookings\" — and stored that over a good list.]\n if (!Array.isArray(d?.events)) throw new Error(\"no events array in the response\");\n for (const e of d.events) events.push(e as CalEvent);\n calendarsRead++;\n } catch { /* one calendar down is reported below, never silently treated as \"no bookings\" */ }\n }\n // The pick-ups. A calendar that does not answer here is NOT fatal: without it a stay is judged\n // on its drop-off day alone, which is exactly what the module did before, so the list gets\n // smaller rather than wrong. It is reported all the same.\n const pickups: CalEvent[] = [];\n let pickupsRead = 0;\n for (const cal of PICKUP_CALENDARS) {\n try {\n const q = `locationId=${LOC}&calendarId=${cal}&startTime=${dayMs(shiftDays(from, -LOOKBACK_DAYS))}&endTime=${dayMs(shiftDays(to, LOOKAHEAD_DAYS))}`;\n const d = await io.get(`/calendars/events?${q}`, \"2021-04-15\");\n if (!Array.isArray(d?.events)) throw new Error(\"no events array in the response\");\n for (const e of d.events) pickups.push(e as CalEvent);\n pickupsRead++;\n } catch { /* reported on the card: a stay is then judged on its drop-off day alone */ }\n }\n\n const stays = groupIntoStays(events, windows, pickups);\n\n // ---- the money ----\n const rows: DepositRow[] = [];\n // KEYED BY CUSTOMER. The kill switch's floor is written in customers (\"five people with no card\n // payment\"), so a customer with five holiday drop-offs must count once, not five times.\n const perCustomer = new Map();\n let readFailures = 0;\n\n // BY CUSTOMER, not by stay, so one $50 deposit cannot settle two of the same person's bookings.\n const byCustomer = new Map();\n for (const s of stays) {\n const list = byCustomer.get(s.contactId) ?? [];\n list.push(s);\n byCustomer.set(s.contactId, list);\n }\n\n for (const [contactId, own] of byCustomer) {\n let pays: Payment[] | null = null;\n try {\n const notes = await allNotes(io, contactId);\n // A 200 with no notes ARRAY is a response we do not understand, not a customer with no\n // notes. [was: `d?.notes ?? []`, so a rate-limit soft-fail or a changed response shape\n // rendered as \"No Square payment is on file\" — a confident finding built on nothing.]\n pays = notes === null ? null : parseSquarePayments(notes);\n } catch { pays = null; }\n if (pays === null) readFailures++;\n\n let nm = \"\";\n try {\n const c = await io.get(`/contacts/${contactId}`, \"2021-07-28\");\n const ct = c?.contact ?? c;\n nm = [ct?.firstName, ct?.lastName].filter(Boolean).join(\" \").trim() || ct?.contactName || \"\";\n } catch { nm = \"\"; }\n // A name we could not read is shown as that, not as a blank that reads like a bug.\n const name = nm || \"name not readable\";\n\n // WHAT THE KILL SWITCH IS ALLOWED TO SEE: money in the period this run is judging, for\n // customers we actually searched. A stay with no booking date has NO searchable window, so\n // paymentsNearStay returns a structural empty for it; counting that as \"we looked and saw no\n // money\" let one missing field push the sample over the floor and black out the whole card.\n if (pays !== null && own.some((s) => s.bookedAt)) {\n const near = own.filter((s) => s.bookedAt).flatMap((s) => paymentsNearStay(s, pays!));\n perCustomer.set(contactId, near);\n }\n\n for (const st of statusesForCustomer(own, pays)) {\n rows.push({\n contactId, name, day: st.stay.day, until: st.stay.until, dogs: st.stay.dogs,\n dogCount: st.stay.dogCount, window: st.stay.window, state: st.state, amountSeen: st.amountSeen, note: st.note,\n });\n }\n }\n rows.sort((a, b) => a.day.localeCompare(b.day));\n\n const feedDead = feedLooksDead(perCustomer);\n const statuses: StayStatus[] = rows.map((r) => ({\n stay: { contactId: r.contactId, day: r.day, until: r.until, dogs: r.dogs, dogCount: r.dogCount, bookedAt: null, window: r.window },\n state: r.state, amountSeen: r.amountSeen, note: r.note,\n }));\n\n return {\n at: todayIso, season, windows, rows,\n sentence: depositSentence(statuses, feedDead),\n feedDead, readFailures,\n calendarsRead, calendarsAsked: BOARDING_CALENDARS.length,\n pickupsRead, pickupsAsked: PICKUP_CALENDARS.length,\n };\n}\n\n/** ONE PLACE where a collection is run and stored, so the scheduled run and the manual run cannot\n * drift apart. deposits-cron.ts calls this; so does the endpoint below. */\nexport async function runCollection(force = false, source = \"unknown\"): Promise<{ ok: boolean; error?: string; out?: DepositBlob }> {\n const b = await blobMod();\n // Stamped BEFORE the work, so a collection that fails, times out or declines to store still\n // closes the gate for an hour rather than being retried on every tick.\n // WITH WHO STARTED IT. Two schedules can reach this — the engine's interval and deposits-cron.ts\n // — plus a person hitting the endpoint. On 6 Aug the list refreshed at 20:49 with nobody\n // triggering it, which was the first autonomous refresh ever observed, and there was no way to\n // tell WHICH schedule did it. \"It works\" and \"which one works\" are different facts.\n await b.setJSON(ATTEMPT_KEY, { at: new Date().toISOString(), source }).catch(() => {});\n const tok = await token();\n if (!tok) return { ok: false, error: \"no CRM credential resolved, so nothing was collected\" };\n const out = await collect({ get: (p, v) => getJson(p, v, tok) }, new Date().toISOString());\n const prev = (await b.getJSON(BLOB_KEY).catch(() => null)) as DepositBlob | null;\n const d = decideStore(out, prev, force);\n if (!d.store) return { ok: false, error: d.error, out };\n await b.setJSON(BLOB_KEY, out);\n return { ok: true, out };\n}\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n if (!(await authorised(url.searchParams.get(\"k\") || \"\"))) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n const json = (o: unknown, status = 200) =>\n new Response(JSON.stringify(o, null, 2), { status, headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" } });\n\n try {\n if (url.searchParams.get(\"run\") !== \"1\") {\n const b = await blobMod();\n const stored = await b.getJSON(BLOB_KEY).catch(() => null);\n // THE ATTEMPT STAMP COMES BACK TOO, and reading it does not write it. Without this, \"the\n // list has not moved\" is ambiguous between \"the schedule never tried\" and \"it tried and\n // declined to store\" — and those need completely different fixes. Every observation of the\n // refresh so far has been unable to tell them apart.\n const attempt: any = await b.getJSON(ATTEMPT_KEY).catch(() => null);\n return json({ ...(stored ?? { at: null, rows: [], sentence: \"This has not been collected yet.\" }),\n lastAttemptAt: attempt?.at ?? null,\n lastAttemptBy: attempt?.source ?? null,\n refreshDueAt: attempt?.at && Number.isFinite(Date.parse(attempt.at))\n ? new Date(Date.parse(attempt.at) + REFRESH_EVERY_MS).toISOString() : null });\n }\n const r = await runCollection(url.searchParams.get(\"force\") === \"1\", \"endpoint\");\n return r.ok ? json(r.out) : json({ error: r.error, ...(r.out ?? {}) }, 503);\n } catch (e) {\n return json({ error: String(e).slice(0, 500) }, 500);\n }\n}\n",[302],"b71c0829-6146-4c4f-82e8-64c1a725c66d","deposits-cron.ts","b4eead18-91ad-11f1-b6f8-1607ee4eb77e",325,["D",1786053100090],4,"// THE HOLIDAY DEPOSIT REFRESH, ON A SCHEDULE. v1.0, 6 Aug 2026.\n//\n// WHY IT IS ITS OWN FILE AND NOT A LINE IN main.ts. main.ts is hard-capped at 80,000 characters\n// and has 679 left. Squeezing this in would mean deleting something that is already load-bearing\n// to make room for something new, on the entry point that runs Kim's follow-up system. A second\n// scheduled file costs nothing and cannot take the engine down with it.\n//\n// IT ONLY READS. Everything it does is inside runCollection(), which reads two calendars and some\n// contact notes and writes one blob. There is no path from here to a message, a tag or a customer.\n//\n// IT NEVER SHOUTS. If the CRM is unreachable this logs and returns. The dashboard already knows\n// how to say \"last checked N hours ago\", so a missed run degrades into a visibly older timestamp\n// rather than into an alarm or, worse, an empty list presented as fact.\nimport { runCollection, refreshIfDue, ATTEMPT_KEY, BLOB_KEY, type DepositBlob, type DepositRow } from \"./deposits.ts\";\n\nexport default async function (): Promise {\n try {\n // THE SAME GATE main.ts USES, through the same function, so the two cannot drift.\n const blob = (await import(\"https://esm.town/v/std/blob\")).blob;\n const g = await refreshIfDue(() => blob.getJSON(ATTEMPT_KEY) as any, () => runCollection(false, \"deposits-cron\"), Date.now());\n if (!g.ran) { console.log(`[deposits] ${g.why}`); return; }\n const o = (await blob.getJSON(BLOB_KEY)) as DepositBlob | null;\n if (!o) { console.log(`[deposits] ${g.why}, and nothing is stored`); return; }\n const worth = (o.rows ?? []).filter((x: DepositRow) => x.state === \"none_seen\" || x.state === \"partial\").length;\n console.log(`[deposits] ${o.rows.length} stay(s), ${worth} worth checking, ${o.readFailures} unreadable, drop-off calendars ${o.calendarsRead}/${o.calendarsAsked}, pick-up calendars ${o.pickupsRead}/${o.pickupsAsked}`);\n } catch (e) {\n // A scheduled job that throws on val.town shows up as a failed run and pages nobody usefully.\n // The honest outcome of a failed refresh is an older timestamp on the page, which is visible.\n console.log(`[deposits] refresh failed: ${String(e).slice(0, 200)}`);\n }\n}\n",[309],"cfeb7f25-ab21-4795-b6c3-3b435b650a7f","decisions.ts","13df017c-902f-11f1-8dc5-1607ee4eb77e",688,["D",1786388052942],25,"// WHAT IS WAITING ON KIM. v1.2, 4 Aug 2026.\n//\n// WHY THIS FILE EXISTS: two independent readers were handed the dashboard cold. Both said the\n// same thing without prompting. Kim: \"there is no list of what I'm being asked, no button, no\n// 'Kim: 3 things waiting on you'.\" Candace: \"exactly one requires anything from us, buried\n// fifth-from-top, styled identically to eight items needing nothing, with no owner.\" A page that\n// reports state but never asks for a decision quietly turns the reader into a spectator.\n//\n// THE RULE: an item goes here only when it is genuinely blocked on Kim, it is written in her\n// words, and it says what happens if she says yes AND what happens if she says nothing. No item\n// nags. No item implies she is late. \"Nothing\" is always an acceptable answer, and where that is\n// true the item says so.\n//\n// EVERY ITEM MIRRORS A NUMBERED ROW IN THE COMMITMENTS LEDGER, so the page and the ledger cannot\n// drift apart. The `ref` is that row. If you add one here, add it there in the same commit.\n//\n// v1.2, after the second stranger test. Three findings, all fair:\n// 1. Every item carries `evidence` now. The work log below it sets a standard of proof (\"How we\n// know\" on every line) and this card was exempting itself from that standard while sitting\n// ABOVE it. The reader noticed within one read.\n// 2. No item may hardcode a live number. The old K11 text said \"two of this week's went\n// unmarked\" while the tiles, reading the same account, showed none unmarked in their window.\n// A number typed into prose goes stale the day after it is typed. Live figures arrive through\n// `Ctx` and are rendered by a function, or they are not stated.\n// 3. The $250 Bootcamp cohort is a decision about her customers' money and was sitting twelve\n// rows down in the work log rather than here. \"Wrong things promoted\", exactly.\n\nexport type Ctx = {\n unmarkedPupTalks?: number | null; // appointments with no showed/no-show mark yet, this window\n inquiriesPerWeek?: number | null; // live count, so the volume a YES commits her to is never typed\n // computed by facts.ts from the bridge journal. The typed version of this sentence was wrong in\n // all four of its numbers and understated the money by $4,572.\n squareSentence?: string | null;\n // Live, from a server-side tag filter over the WHOLE contact base. Never a scan size.\n puppyTagSentence?: string | null;\n // What the tagging step WOULD pick up, measured on the engine's last run. Null until it has run\n // one, so the page never implies a dry pass happened when none did.\n tagScanSentence?: string | null;\n};\n\nexport type Decision = {\n ref: string; // ledger row, e.g. \"K8\"\n ask: string; // the question, in Kim's vocabulary, ending in a question mark\n why: string | ((c: Ctx) => string); // what it unblocks or prevents\n // A function when the evidence contains a figure. A number in evidence is still a number,\n // and it drifts exactly like a number in prose does.\n evidence: string | ((c: Ctx) => string);\n ifYes?: string | ((c: Ctx) => string); // what saying yes costs. May depend on live figures.\n ifNothing: string; // what happens if she never answers. Honest, including \"nothing bad\".\n weight: \"blocking\" | \"worth doing\" | \"whenever\";\n liveNow?: boolean; // already affecting real customers today, as opposed to pending\n // v1.5. Three separate readers, independently, came to this page worrying about money and found\n // the only question about money filed last and folded away. Weight measures urgency; this\n // measures whether the reader will go looking for it. Money always shows.\n surface?: boolean;\n /** An extra paragraph computed at render time. Never a place to put a typed figure. */\n extra?: (c: Ctx) => string;\n};\n\n// v1.3, after the third stranger test, which read this file as well as the page. Four findings:\n// 1. The type stated the rule as \"what happens if she says yes AND if she says nothing\" and then\n// implemented only half of it. `ifYes` now exists and is filled wherever a yes has a cost.\n// 2. `weight: \"blocking\"` was applied to two items that do not block. An item carrying a stated\n// default is an answered question; a December deposit does not gate a puppy sequence. The\n// headline counts blockers, so mislabelling one puts a wrong number at the top of the page.\n// 3. The genuine email go-live blocker was in the ledger and NOT here, so a reader answering\n// every card would believe the runway was clear when the email half cannot deliver.\n// 4. The page detected \"already reaching customers\" by regex-matching this file's prose, so a\n// reword would have silently disabled the warning. It is a field now.\n\nexport const DECISIONS: Decision[] = [\n {\n ref: \"K8\",\n ask: \"When do we do the switch-on together?\",\n why: \"You already answered the yes: on Wednesday evening you wrote \\\"switch on as soon as we've tweaked the follow up messages\\\", and the tweaks you asked for went into the copy on 9 August, every one. You also confirmed the old puppy workflow has never been used and can go off at any time. So the question left is not whether, it is when: three things happen in the same few minutes, with you watching, or new inquiries get two sets of messages from you on the same day. Say a day and a time and it is done in that window.\",\n evidence: (c: Ctx) =>\n \"All 165 automations were read one by one on 4 August; the one still switched on is named \\\"1. Wait 1 Day: Initial Nurture - Puppy\\\". \" +\n (c.puppyTagSentence ?? \"The mark our system watches for could not be counted just now, so treat the tagging step as unconfirmed rather than done.\"),\n ifYes: (c) =>\n `All three get done together, with you watching: tagging on, ours on, the old one off. From that moment it starts working on ${c.inquiriesPerWeek != null ? `roughly the ${c.inquiriesPerWeek} new inquiries a week you are getting now` : \"your new inquiries as they arrive\"}, and nothing changes for anyone already partway through the old sequence.`,\n ifNothing: \"Nothing breaks. The new messages stay in practice mode and nobody is messaged by them.\",\n weight: \"blocking\",\n extra: (c) => c.tagScanSentence\n ? `On the third of those three switches: the part that works out who counts as a puppy inquiry is now built and running quietly alongside everything else, so you can see what it would do before it does anything. ${c.tagScanSentence} One thing worth your view: a dog of about a year old sits right on the line. Your messages do cover the teenage stage, so they may well belong. That one is yours to call.`\n : \"\",\n },\n {\n ref: \"K1\",\n ask: \"The wording changes you asked for are in. Want a fresh read, or is Wednesday's answer the answer?\",\n why: \"On Wednesday you gave the wording its verdict and its corrections in one go: open message two on the welcome, say what a Pup Talk is rather than what it is not, drop the lines about what we will not do, and say \\\"going\\\" not \\\"getting on\\\", plus the hot-day water note and back-to-school for August. Every one of those went into the copy on 9 August and each is now pinned by its own automated check so it cannot drift back. The write-ups you hold were regenerated from the changed copy the same day.\",\n evidence: \"Both write-ups were generated from the live system rather than from a draft, so what you read is exactly what would send. Your Wednesday message is the answer of record; the 9 August regeneration carries your changes.\",\n // v1.4. This read \"roughly 190 new people a week\" while the page counted 186 four inches\n // above it. The volume a YES commits her to is the whole weight of the question, so it is\n // counted at render time or it is not stated as a number at all.\n ifYes: \"Nothing else about the wording comes back to you. It still does not send until the switch-on above is scheduled too.\",\n ifNothing: \"Your Wednesday corrections stand as given and the copy stays exactly as regenerated.\",\n weight: \"blocking\",\n },\n {\n ref: \"K2\",\n ask: \"Which number should customers see, 912-348-8726 or 912-823-4382?\",\n why: \"It goes at the bottom of every message that leaves the system, so it needs to be the one you actually want ringing.\",\n evidence: \"Both numbers are live on your account and both are cleared for texting. On 4 August, only one of them was on your website footer: 912-348-8726.\",\n ifNothing: \"We use 912-348-8726, the one already on your website. This one has a default, so it does not hold anything up; it is here because it is your name on the message.\",\n weight: \"worth doing\",\n },\n {\n ref: \"KB1\",\n ask: \"Bootcamp deposits: you answered this on Wednesday. Anything to add, or is it closed?\",\n why: \"Your Wednesday answer is the answer of record: most people pay the deposit over the phone, the one or two who paid the wrong amount were corrected at drop off, everyone ultimately paid the right price, and the website payment was set up to go to PayPal rather than Square. So the earlier worry on this card, that money might have gone missing while the form said $250, is answered by you: nothing was underpaid. The form itself was fixed to $500 on 2 August and stays fixed.\",\n evidence: \"The wrong figure was found inside the booking form's own settings, corrected and published, and the live site was then searched end to end for '$250' with no hits left. Your Wednesday message about PayPal, the phone payments and nothing being underpaid is the answer of record; the payment matching this card used to ask for is no longer needed unless you want it.\",\n ifYes: \"If you ever want the belt-and-braces version, we match the 17 bookings against the payment records and hand you the list. Deciding to look is not deciding to chase.\",\n ifNothing: \"Closed on your say-so. The form is fixed and your answer stands.\",\n extra: (c) => c.squareSentence ? `Separately, on the same subject of money the records cannot place: ${c.squareSentence}` : \"\",\n weight: \"worth doing\",\n surface: true,\n },\n {\n ref: \"K6\",\n ask: \"Should people who have already booked keep getting the safety tips?\",\n why: \"Right now the follow-ups stop the moment somebody books. Some owners like the tips continuing; some find it odd to still be sold at after they said yes.\",\n evidence: \"Read from the sequence itself: booking is a stop condition on every path, including the slow track.\",\n ifNothing: \"They stop at booking, which is the safer of the two.\",\n weight: \"worth doing\",\n },\n {\n ref: \"K11\",\n ask: \"Can we ask the front desk to mark every Pup Talk showed or no-show?\",\n why: (c) =>\n c.unmarkedPupTalks\n ? `${c.unmarkedPupTalks} of the Pup Talks in the last 7 days ${c.unmarkedPupTalks === 1 ? \"has\" : \"have\"} no mark against ${c.unmarkedPupTalks === 1 ? \"it\" : \"them\"} yet, so the show-up figure on this page is better than the truth by up to that many. It is a ten second job at the desk.`\n : \"When one goes unmarked the show-up figure on this page comes out better than the truth, because an unmarked appointment is not counted as a miss. None are unmarked right now, and keeping it that way is a ten second job at the desk.\",\n evidence: \"Counted live from your calendar each time this page loads, not typed in here.\",\n ifYes: \"Nothing to build. It is a habit at the desk, and the number on this page stops flattering itself.\",\n ifNothing: \"The show-up figure drifts optimistic whenever one is missed, and this page keeps saying so. Nothing else is affected.\",\n weight: \"worth doing\",\n },\n {\n ref: \"K7\",\n ask: \"You have two review-request automations both switched on. Which one do you want to keep?\",\n why: \"You have two review-request workflows switched on at once, with near-identical names. We cannot read a workflow's steps through the interface we have, so we cannot promise you both actually fire, but two published copies is the usual shape of a customer being asked twice, and it is worth ten seconds of your time.\",\n evidence: \"Read from all 165 automations on 4 August: \\\"New Review Request WF\\\" and \\\"Update- New Review Request WF\\\" are both published. What we could NOT do is open either one and read its steps, because that call is not available to us. So this is two live copies, not a confirmed double send.\",\n ifNothing: \"Both stay switched on. If they do both fire, the double ask continues; it is not damaging, it just looks careless.\",\n weight: \"worth doing\",\n liveNow: true,\n },\n {\n ref: \"K12\",\n ask: \"The four domain lines: you said yes on Wednesday and asked for instructions. Ready for them on Upwork today?\",\n why: \"This is the real blocker on the email half, and on Wednesday you answered it: happy to add the four lines, just need to know how and where. Checked on 4 August, your domain tells the internet that Google and Wix are allowed to send email in your name, and nobody else. Until the four lines go in, every follow-up email would come from a server your domain does not stand behind, and a lot of them would land in spam. Texting is unaffected: that is verified separately and already works.\",\n evidence: \"Read from your domain's own public records. They list Google and Wix and nothing else. The settings needed are generated by your CRM and are four short lines of text. Your Wednesday yes is the answer of record; the step-by-step instructions for the Wix screen are written and come to you on Upwork.\",\n ifYes: \"You paste the four lines where the instructions show, it takes about ten minutes, and email can go live alongside texting.\",\n ifNothing: \"Texting can still go live on its own. Email cannot, and this stays the one thing standing in its way.\",\n weight: \"blocking\",\n },\n {\n ref: \"K10\",\n ask: \"Costs against what it brings in: you said go ahead on Wednesday. The spend half now reads live. Want the walkthrough this week?\",\n why: \"You answered on Wednesday: \\\"I absolutely wanna know what all this costs against what it brings in, go ahead.\\\" Since 9 August the spend half is no longer waiting on anybody: Facebook granted the read permission, so the advertising card on this page now shows real dollars from the ad platform every time it loads. What the page still cannot show is the money coming back, because your CRM does not record a value on a sale. Closing that half is Amir's job and it is on his list, not yours.\",\n evidence: \"The spend connection was watched working on 9 August: the page read $671.72 and 159 started conversations for the last 7 full days straight from Facebook. The earning side is nearly blank in your CRM: 53 of your customer records carry a dollar value, $166,235.00 between them, and every one of those was last touched on 30 June, so nothing in the last six weeks has had a value put on it.\",\n ifYes: \"Half an hour together, real spend against real bookings, and the cost-per-lead for each campaign on paper in front of you.\",\n ifNothing: \"The spend keeps showing on this page either way. The what-it-brings-in half waits until the CRM records a value on a sale.\",\n weight: \"worth doing\",\n surface: true,\n },\n {\n ref: \"K13\",\n ask: \"Can we retire the access key you pasted into the Upwork thread on 31 July?\",\n why: \"It is a working key to your CRM sitting in a chat log. Nothing has gone wrong that we know of, and we have no way to tell whether anybody else has used it, which is exactly why it should not be sitting there. It is simply not where a key should live.\",\n evidence: \"The message was still in the thread on 4 August. On Wednesday evening you went to delete the key yourself and said you were not entirely sure it worked. That attempt is on record; what has not happened yet is anyone confirming the old key is actually dead, and until that check runs the honest state is: probably retired, not yet proven.\",\n ifYes: \"Two minutes, and one loose end closed.\",\n ifNothing: \"A working key to your customer list stays in a chat log that other people can be added to. Nothing has gone wrong so far, and nobody can promise it will not.\",\n weight: \"worth doing\",\n liveNow: true,\n },\n {\n ref: \"K14\",\n ask: \"Can we take the holiday boarding deposit automatically instead of by hand?\",\n why: \"You already have a product in your CRM called \\\"Holiday boarding deposit\\\" set at $50, fully configured, and it does not appear on a single order in the payment history we can see. Your boarding bookings go through the form on your website instead, so the CRM never gets the chance to take the money or record that it arrived. That is why somebody is checking by hand.\",\n evidence: \"Read from your own product list: \\\"Holiday boarding deposit\\\" and \\\"New Client Boarding Deposit\\\" both exist at $50, and not one order in your recent payment history references either.\",\n ifYes: \"Two sizes of job, and Amir will lay out both before anything is built: record the deposit against the customer automatically so you get a list rather than a memory, or take it as part of the booking so nobody can complete one without paying.\",\n ifNothing: \"It stays a manual check every holiday season.\",\n weight: \"worth doing\",\n },\n {\n ref: \"K15\",\n ask: \"You have five no-sale and tips follow-up sequences running, plus two auto-responders. Do you want me to go through them for overlap?\",\n why: \"They are all published and live. The one that looked accidental, \\\"Copy - Tips Ad campaign > Auto Responder\\\", you answered on 5 August: the copy is Milton's on purpose, and it answers on Facebook comments as well as in Messenger, so it stays exactly as it is. What is left of this question is smaller: whether Amir reads the five sequences so nobody can end up getting two sets of messages from you on the same afternoon.\",\n evidence: \"Read from all 165 automations on 4 August: seven published and one draft. Five are follow-up sequences; two are auto-responders and call routing, so the real number to review is nearer five. Your 5 August message is the answer of record on the copy workflow.\",\n ifYes: \"Amir reads all of them and tells you which are earning their place, before anything new is built.\",\n ifNothing: \"They keep running as they are, which is now the known-good state you described.\",\n weight: \"worth doing\",\n },\n {\n ref: \"K9\",\n ask: \"Would you tell us a story or two from the kennel?\",\n why: \"There are eight places in the follow-up messages where a real thing that happened to a real dog would land far better than general advice. They are written to read perfectly well empty, and they are empty today, because made up stories are not something we will put in your name.\",\n evidence: \"The eight places are marked in the sequence you have already read. Each one has a fallback line that reads normally with no story in it, which is what is running now.\",\n ifNothing: \"The messages read exactly as you have already seen them, which costs you nothing.\",\n weight: \"whenever\",\n },\n {\n ref: \"K16\",\n ask: \"Do you want the one untranscribed call from 4 August looked at, or is the answer enough?\",\n why: \"Mostly answered on 6 August. No transcript exists on any call older than about three months, and since then almost every call with speech has one. What is not settled is why the old ones have none: either transcription was switched on around 11 May, or transcripts are deleted once they reach about ninety days. Both look the same from here, and the second one would mean you are quietly losing call history every month. One query a week from now tells us which, and it costs nothing.\",\n // [was, twice over: first \"Every call in your account was checked\" (it was 62 of them), then\n // \"the writing-down step has simply never been switched on\". That second claim was inferred\n // from the API showing no transcript on any of the 62 call records, and the inference was\n // wrong: the API simply does not carry transcripts on those records. On 5 August a call from\n // that same morning was opened in the CRM and its transcript was watched rendering, word by\n // word. Transcription is on. The claim below is what has actually been observed.]\n evidence:\n \"Sixty-two of your calls were checked from your most recently active conversations: 54 carry a full audio recording, about two and a quarter hours of it, and the recordings play. The 8 without one were calls nobody answered. Then a call from the morning of 5 August was opened directly in the CRM and its written transcript was watched rendering, and a second call from 4:54 that same afternoon shows its transcript in the CRM as well, so transcription is on and working at least sometimes. What has not been found yet is a call that is missing its transcript, which is why your report matters: one example from you of a call where the transcript used to be there, or should be, pins down the pattern in minutes.\",\n ifYes:\n \"Point at one call where the transcript is missing, or tell us roughly when they disappeared for you, and the comparison between that call and the transcribed one from that morning does the rest: same number or different, human or Chloe, long or short, before or after a settings change.\",\n ifNothing:\n \"Nothing breaks. Recording keeps working and at least some calls keep getting transcripts, but the ones that are missing stay a puzzle solved by trial and error instead of by one example from you.\",\n weight: \"worth doing\",\n },\n];\n\nexport const WEIGHT_ORDER: Record = { blocking: 0, \"worth doing\": 1, whenever: 2 };\nexport const WEIGHT_LABEL: Record = {\n blocking: \"Holds up go-live\",\n \"worth doing\": \"Worth doing\",\n whenever: \"Whenever you like\",\n};\nexport function sortedDecisions(ds: Decision[] = DECISIONS): Decision[] {\n return [...ds].sort((a, b) => WEIGHT_ORDER[a.weight] - WEIGHT_ORDER[b.weight]);\n}\nexport const blockingCount = (ds: Decision[] = DECISIONS) => ds.filter((d) => d.weight === \"blocking\").length;\n/** Resolve a `why` that may depend on live figures. */\nexport const whyText = (d: Decision, c: Ctx): string => (typeof d.why === \"function\" ? d.why(c) : d.why);\n/** Same treatment for ifYes: a volume figure must be counted, never typed. */\nexport const ifYesText = (d: Decision, c: Ctx): string | undefined =>\n d.ifYes == null ? undefined : (typeof d.ifYes === \"function\" ? d.ifYes(c) : d.ifYes);\nexport const extraText = (d: Decision, c: Ctx): string => (d.extra ? d.extra(c) : \"\");\n/** Evidence gets the same treatment as why/ifYes: a figure in it is computed, never typed. */\nexport const evidenceText = (d: Decision, c: Ctx): string =>\n typeof d.evidence === \"function\" ? d.evidence(c) : d.evidence;\n",[317],"74fcc178-d6ce-49e0-bca9-9d629df4d412","dashboard.ts","fb119304-9028-11f1-8278-1607ee4eb77e",385,["D",1786072340622],39,"// THE DOGS SPOT, LIVE DASHBOARD. One page Kim can open any time, from anything. v1.0, 4 Aug 2026.\n//\n// THE PROMISE THIS FILE MAKES: it always renders something true. Every data source is fetched\n// independently, every failure is caught, and the last good answer for each section is cached in\n// a blob. If the CRM is down, the page says \"the CRM did not answer just now, here is what it\n// said 20 minutes ago\" instead of showing a zero or a blank. A dashboard that shows a wrong zero\n// is worse than no dashboard, because it is quietly reassuring.\n//\n// ROUTES ?k= the dashboard\n// ?k=&f=json the same numbers as data\n//\n// AUDIENCE: Kim. Non-technical, on a phone, thirty seconds. No jargon, no acronyms unexplained,\n// no metric that does not connect to her money. Detail lives below the fold for whoever wants it.\ndeclare const Deno: { env: { get(k: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\nimport {\n countContacts, sourceBreakdown, channelBreakdown, campaignBreakdown, attributionCoverage,\n countEvents, wonOpps, weeklyBuckets,\n deltaWord, money, type ContactLite, type EventLite, type OppLite,\n} from \"./report-logic.ts\";\nimport { sortedDecisions, blockingCount, whyText, ifYesText, extraText, evidenceText, WEIGHT_LABEL, type Decision, type Ctx } from \"./decisions.ts\";\nimport { SEEDED, mergeLog, KIND_LABEL, type WorkEntry } from \"./worklog.ts\";\nimport { squareBacklog, squareSentence, otherBucketExplanation, otherBucketSentence, tagCoverageSentence, type TagCoverage } from \"./facts.ts\";\nimport { observedCadenceMin, lateness, lateSentence, isHealthy, neverRanItselfSentence } from \"./cadence.ts\";\nimport { detectSentence, scanAgeNote, type DetectSummary } from \"./puppy-detect.ts\";\nimport type { DepositBlob, DepositRow } from \"./deposits.ts\";\nimport { looksLikeTestRecord, depositSentence, OTHER_ROUTES } from \"./holiday-deposits.ts\";\n\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\n// READ FROM THE SAME PLACE THE ENGINE READS IT. If someone changes the enrollment tag in the val's\n// settings, the page must start counting the new tag, not keep reporting confidently on the old\n// one. Two constants would be two facts, and one of them would be wrong without telling anybody.\nconst ENROLL_TAG = Deno.env.get(\"TAG_SOURCE_SIGNAL\") || \"nurture - puppy\";\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst PUP_TALK_CAL = \"qHuYJ0NEqzibnoqf5Cw3\";\nconst CACHE_KEY = \"dash_cache\";\nconst BRIDGE = \"https://amir5--41ace24c7e2111f18c9d1607ee4eb77e.web.val.run\";\n// read-only journal route; overridable by env so the literal is not the only copy\nconst BRIDGE_ADMIN = \"tds_adm_H6Dn3HYINivzgfJd2zic9YYCi9QUA6Yj4SVF7OrKtDQ\";\n\n// ---- palette: validated with the dataviz validator, both modes, on these exact surfaces ------\n// Categorical slots 1-3 (blue/orange/aqua): ALL CHECKS PASS light and dark. Status steps are the\n// reserved four and always ship with a word beside them, never color alone.\nconst CAT = [\"#2a78d6\", \"#eb6834\", \"#1baf7a\"];\nconst CAT_DARK = [\"#3987e5\", \"#d95926\", \"#199e70\"];\nconst GOOD = \"#0ca30c\", WARN = \"#fab219\", CRIT = \"#d03b3b\";\n\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\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}\nasync function blobMod() { return (await import(\"https://esm.town/v/std/blob\")).blob; }\n// v1.1 (review #2): a failed READ and a genuinely EMPTY value are different facts. Collapsing\n// them made the page say \"0 people waiting on you\" when the truth was \"we could not check\".\ntype Read = { ok: true; v: T | null } | { ok: false; v: null };\nasync function readBlob(k: string): Promise> {\n try { return { ok: true, v: ((await (await blobMod()).getJSON(k)) ?? null) as T | null }; }\n catch { return { ok: false, v: null }; }\n}\nasync function getBlob(k: string): Promise { return (await readBlob(k)).v; }\nasync function token(): Promise {\n return Deno.env.get(\"GHL_TOKEN\") || ((await getBlob<{ ghlToken?: string }>(\"puppy_config\"))?.ghlToken ?? undefined);\n}\nasync function isAdmin(k: string) {\n return (await sha256Hex(k)) === (Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\") || KEY_SHA256);\n}\nasync function isViewer(k: string) {\n const tok = await token();\n return !!tok && k === \"tds_view_\" + (await sha256Hex(tok + \":view\")).slice(0, 32);\n}\n\nasync function j(path: string, ver: string) {\n const tok = await token();\n const r = await fetch(`${GHL}${path}`, {\n headers: { Authorization: `Bearer ${tok}`, Version: ver, \"User-Agent\": \"curl/8.5.0\" },\n signal: AbortSignal.timeout(20_000),\n });\n if (!r.ok) throw new Error(`HTTP ${r.status}`);\n return r.json();\n}\n\nconst ET = () => {\n const p = new Intl.DateTimeFormat(\"en-US\", { timeZone: \"America/New_York\", timeZoneName: \"shortOffset\" })\n .formatToParts(new Date()).find((x) => x.type === \"timeZoneName\")?.value ?? \"GMT-4\";\n const m = p.match(/GMT([+-]\\d+)/);\n return m ? Number(m[1]) * 60 : -240;\n};\n\nasync function contactsSince(floorMs: number, truncated: string[]): Promise {\n const out: ContactLite[] = [];\n let sa: string | undefined, sav: number | undefined;\n let reachedFloor = false;\n for (let page = 0; page < 30; page++) {\n const q = new URLSearchParams({ locationId: LOC, limit: \"100\" });\n if (sa && sav) { q.set(\"startAfterId\", sa); q.set(\"startAfter\", String(sav)); }\n const d = await j(`/contacts/?${q}`, \"2021-07-28\");\n const cs = d?.contacts ?? [];\n if (!cs.length) break;\n for (const c of cs) {\n // The FIRST attribution entry is the one flagged isFirst by the CRM, i.e. how this person\n // arrived, not how they last touched us. Later entries describe return visits.\n const a = (Array.isArray(c.attributions) ? c.attributions : []).find((x: any) => x?.isFirst) ?? c.attributions?.[0] ?? null;\n out.push({\n dateAdded: c.dateAdded, source: c.source ?? null, tags: c.tags ?? [],\n attribution: a ? { medium: a.medium ?? a.utmSessionSource ?? null, campaign: a.utmCampaign ?? null } : null,\n });\n }\n const oldest = Date.parse(cs[cs.length - 1]?.dateAdded ?? \"\");\n sa = d?.meta?.startAfterId; sav = d?.meta?.startAfter;\n if (Number.isFinite(oldest) && oldest < floorMs) { reachedFloor = true; break; }\n if (!sa) { reachedFloor = true; break; }\n }\n if (!reachedFloor) truncated.push(\"the older weeks of the chart\");\n return out;\n}\n\n// Ad platforms. Both are env-gated and honest: no token means \"not connected yet\", never a guess.\nasync function metaWeek(startMs: number, endMs: number, tz: number) {\n const tok = Deno.env.get(\"META_TOKEN\"), act = Deno.env.get(\"META_AD_ACCOUNT\");\n if (!tok || !act) return null;\n const day = (ms: number) => new Date(ms + tz * 60_000).toISOString().slice(0, 10);\n const r = await fetch(\n `https://graph.facebook.com/v21.0/${act}/insights?fields=spend,actions&time_range={\"since\":\"${day(startMs)}\",\"until\":\"${day(endMs - 86_400_000)}\"}`,\n { headers: { Authorization: `Bearer ${tok}` }, signal: AbortSignal.timeout(20_000) },\n ).catch(() => { throw new Error(\"Facebook did not answer\"); });\n if (!r.ok) {\n // A token that exists but has not been granted ad-reading rights is a SETUP state, not a\n // fault, and it must not reach Kim as \"Facebook returned 400\". Meta answers this exact case\n // with code 200 and a message naming ads_management/ads_read. Verified live on 4 Aug against\n // the real token: the system user was created without an app role, so it came out holding\n // only page permissions. Anything else genuinely is an error and says so.\n const body = await r.json().catch(() => null);\n const msg = String(body?.error?.message ?? \"\");\n if (body?.error?.code === 200 || /ads_read|ads_management/.test(msg)) throw new Error(\"PERMISSION\");\n throw new Error(`Facebook returned ${r.status}`);\n }\n const row = (await r.json())?.data?.[0];\n const acts = row?.actions ?? [];\n const conv = Number(acts.find((a: any) => a.action_type === \"onsite_conversion.total_messaging_connection\")?.value\n ?? acts.find((a: any) => a.action_type === \"lead\")?.value ?? 0);\n return { spend: Number(row?.spend ?? 0), conv };\n}\n// PROVEN LIVE 4 Aug 2026: this account has 5,695 opportunities and every single one carries\n// status \"open\", and nobody uses the won/lost flags. Counting `status=won` returns zero forever,\n// which would have rendered \"0 closed deals\" every week regardless of reality. The real signal\n// is the pipeline STAGE (Customer / Won-Paid), which the engine already uses for its exit rules.\n// Separately proven: every one of those records has monetaryValue 0, so the CRM holds no deal\n// values at all. The page therefore reports customer COUNT and says plainly that revenue is not\n// recorded, rather than printing a $0.00 that reads as \"we earned nothing\".\nconst STAGE_CUSTOMER = \"fd821b4e-bbe6-44de-b754-fa80e4823616\";\nconst STAGE_WON_PAID = \"ae173310-f8b1-4399-acb7-ef1fc03d3697\";\n\nasync function googleWeek() {\n const tok = Deno.env.get(\"GADS_TOKEN\");\n if (!tok) return null;\n throw new Error(\"Google Ads connector is coded but has never been run against a live account\");\n}\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\".\nconst text = (s: unknown) => (typeof s === \"string\" ? s : typeof s === \"number\" && Number.isFinite(s) ? String(s) : \"\");\nconst esc = (s: unknown) => text(s).replace(/[\\u202A-\\u202E\\u2066-\\u2069\\u200E\\u200F\\u061C]/g, \"\")\n .replace(/[&<>\"']/g, (c) => ({ \"&\": \"&\", \"<\": \"<\", \">\": \">\", '\"': \""\", \"'\": \"'\" }[c] as string));\n/** For a field typed by a stranger into her public booking form: capped, then escaped. */\nconst MAX_CELL = 120;\nconst escCell = (s: unknown) => {\n const raw = text(s);\n return esc(raw.length > MAX_CELL ? `${raw.slice(0, MAX_CELL)}...` : raw);\n};\n// The Friday report compares complete Friday-to-Thursday weeks; this page rolls the last 7 days.\n// Saying \"on last week\" here would mean something different from the same phrase there.\nconst vs = (a: number, b: number) => {\n if (a === b) return \"level with the 7 days before\";\n if (b === 0) return \"up from none the 7 days before\";\n const ch = Math.round(((a - b) / b) * 100);\n return `${ch > 0 ? \"up\" : \"down\"} ${Math.abs(ch)}% on the 7 days before`;\n};\nconst MONTHS = [\"Jan\", \"Feb\", \"Mar\", \"Apr\", \"May\", \"Jun\", \"Jul\", \"Aug\", \"Sep\", \"Oct\", \"Nov\", \"Dec\"];\nconst prettyDate = (iso: string) => {\n const m = /^(\\d{4})-(\\d{2})-(\\d{2})/.exec(iso || \"\");\n return m ? `${MONTHS[Number(m[2]) - 1] ?? m[2]} ${Number(m[3])}` : iso;\n};\nconst ago = (iso?: string | null) => {\n if (!iso) return \"never\";\n const m = Math.floor((Date.now() - Date.parse(iso)) / 60000);\n if (!Number.isFinite(m)) return \"unknown\";\n if (m < 1) return \"just now\";\n if (m < 60) return `${m} minute${m === 1 ? \"\" : \"s\"} ago`;\n const h = Math.floor(m / 60);\n if (h < 24) return `${h} hour${h === 1 ? \"\" : \"s\"} ago`;\n const d = Math.floor(h / 24);\n return `${d} day${d === 1 ? \"\" : \"s\"} ago`;\n};\n\n// ---- the holiday deposit card ----------------------------------------------------------------\n// EVERY WORD HERE IS ABOUT SOMEBODY ELSE'S MONEY, so the rules are tighter than anywhere else on\n// this page: it is a list to LOOK AT, never a list of people who owe. Cash and phone deposits do\n// not reach Square, so an absence of a payment is an absence of evidence and is worded that way.\n// A read that failed stays visibly unknown and is never quietly filed under \"nothing found\".\nexport const DEP_STATE: Record = {\n seen: { label: \"Payment on file\", color: GOOD },\n partial: { label: \"Worth a look\", color: WARN },\n none_seen: { label: \"Worth a look\", color: WARN },\n could_not_check: { label: \"Could not check\", color: \"#6b7280\" },\n};\n/** The Dogs column has to agree with the money. Her titles do not all carry a dog name — one real\n * one is \" Boarding Dropoff with Help Test\" — so a stay can be charged for three dogs while only\n * two names parsed. Showing the two names alone reads as an overcharge; this says both numbers. */\n// The windows line, built so it cannot render as a dangling \"Windows checked: .\" and cannot throw\n// on a blob whose `windows` is not an array of objects. That line sits outside the rows check, so\n// before this it ran — and crashed the page — even when there was nothing at all to show.\nfunction windowLine(windows: unknown): string {\n const ws = (Array.isArray(windows) ? windows : []).filter((w): w is { name: string; from: string; to: string } => !!w && typeof w === \"object\");\n if (!ws.length) return \"The holiday windows are not recorded on this list, so it cannot say which dates it covered.\";\n return `Windows checked: ${ws.map((w) => `${esc(w.name)} (${esc(prettyDate(w.from))} to ${esc(prettyDate(w.to))})`).join(\", \")}.`;\n}\n\nexport function dogsCell(r: DepositRow): string {\n // Array.isArray, not `?? []`. A `dogs` field that is a bare string — or a number, or an object —\n // reaches `.filter` and throws, and this function is called inside the page's one big template\n // literal with no try/catch anywhere above it, so the whole dashboard 500s on one bad row.\n // Same for a dogCount that is a numeric string (\"1 dogs\") or negative (\"-1 dogs\").\n const names = (Array.isArray(r.dogs) ? r.dogs : []).filter((d) => typeof d === \"string\" && d.trim());\n const asked = Number(r.dogCount);\n const n = Math.max(0, Number.isFinite(asked) ? Math.floor(asked) : 0) || names.length || 0;\n if (!n) return \"not recorded\";\n if (!names.length) return `${n} ${n === 1 ? \"dog\" : \"dogs\"}, names not recorded`;\n if (names.length < n) return `${names.join(\", \")} and ${n - names.length} more (${n} in total)`;\n return names.join(\", \");\n}\n\nexport function depositCard(dep: DepositBlob | null, readOk: boolean, agoFn: (s?: string | null) => string): string {\n if (!readOk) {\n return `
Holiday deposits
We could not read the deposit list just now. That is a problem reading it, not a finding about anybody. Refreshing in a few minutes normally fixes it.
`;\n }\n if (!dep || !dep.at) {\n return `
Holiday deposits
The deposit check has not run yet, so there is nothing to show here. It fills in the first time it runs.
`;\n }\n // A STORED LIST THAT IS NOT A LIST IS A READING PROBLEM, not an empty season. Filtering a\n // malformed `rows` down to [] and carrying on would print \"No holiday boarding stays are booked\",\n // which is the one thing this card must never say on the strength of something it could not read.\n if (dep.rows !== undefined && dep.rows !== null && !Array.isArray(dep.rows)) {\n return `
Holiday deposits
The stored deposit list is not readable, so nothing is shown here rather than a list that might be wrong. That is a problem reading it, not a finding about anybody.
`;\n }\n // NOTHING BELOW TRUSTS THE SHAPE OF THE STORED BLOB.\n //\n // Every one of these guards is a crash reproduced on 7 August against the real function. The card\n // is interpolated into the page's single template literal, and there is no try/catch between here\n // and the HTTP response, so any throw takes down Kim's whole dashboard rather than one card:\n // rows: {} -> \"(dep.rows ?? []) is not iterable\" (spread of a non-iterable)\n // rows: \"x\" -> renders a blank phantom customer the headline then counts\n // two same-state rows, day null -> \"Cannot read properties of null (reading 'localeCompare')\"\n // invisible with one row, because .sort() never calls the\n // comparator on a single element\n // dogs: \"Fido\" -> \".filter is not a function\" (fixed in dogsCell)\n // windows: \"Thanksgiving\" -> \".map is not a function\", and that line runs even with no rows\n const order: Record = { none_seen: 0, partial: 1, could_not_check: 2, seen: 3 };\n const day = (r: DepositRow) => (typeof r.day === \"string\" ? r.day : \"\");\n const rows = (Array.isArray(dep.rows) ? dep.rows : []).filter((r): r is DepositRow => !!r && typeof r === \"object\")\n .slice()\n .sort((a, b) => ((order[a.state] ?? 9) - (order[b.state] ?? 9)) || day(a).localeCompare(day(b)));\n const stayDates = (r: DepositRow) => r.until && day(r) && r.until > r.day\n ? `${prettyDate(r.day)} to ${prettyDate(r.until)}` : day(r) ? prettyDate(r.day) : \"date not recorded\";\n // A row with no readable name is NOT rendered anonymously. deposits.ts already substitutes\n // \"name not readable\" upstream; a blank green \"Payment on file\" row with no name at all is\n // unverifiable — Kim cannot act on it and cannot check it — so this is the second line of that\n // defence rather than a duplicate of it.\n const who = (r: DepositRow) => (typeof r.name === \"string\" && r.name.trim() ? r.name : \"name not readable\");\n // AN UNKNOWN STATE FALLS BACK TO \"could not check\", as one pair.\n // [was: two independent `??` fallbacks, a grey dot and the label \"Worth a look\", which between\n // them produced a combination that exists nowhere in DEP_STATE: grey is reserved for\n // \"Could not check\" and \"Worth a look\" is reserved for the two orange states. A state this code\n // does not recognise is a state it cannot make a claim about, so it says so.]\n const shown = (r: DepositRow) => DEP_STATE[r.state] ?? DEP_STATE.could_not_check;\n const body = rows.map((r) => `${escCell(who(r))}${esc(stayDates(r))}${escCell(dogsCell(r))}\n● ${esc(shown(r).label)}\n${esc(r.note)}${looksLikeTestRecord(who(r)) ? \" This one looks like somebody testing the booking form rather than a customer, so check who it is before you call.\" : \"\"}`).join(\"\");\n const missed = dep.calendarsAsked && dep.calendarsRead < dep.calendarsAsked\n ? `
Not the whole picture: ${dep.calendarsAsked - dep.calendarsRead} of your ${dep.calendarsAsked} boarding calendars did not answer when this ran, so bookings on ${dep.calendarsAsked - dep.calendarsRead === 1 ? \"it are\" : \"them are\"} missing from the list below.
` : \"\";\n // A pick-up calendar that did not answer is the quiet one: the stays that go missing are exactly\n // the ones that start before a holiday and run into it, and the short list still looks complete.\n const noPickups = (dep.pickupsAsked ?? 0) && (dep.pickupsRead ?? 0) < (dep.pickupsAsked ?? 0)\n ? `
Not the whole picture: ${(dep.pickupsAsked ?? 0) - (dep.pickupsRead ?? 0)} of your ${dep.pickupsAsked} boarding pick-up calendars did not answer, so anyone who dropped off before a holiday and stayed through it may be missing from this list.
` : \"\";\n // COUNTS THE ROWS ON THE TABLE, not the customers behind them. [was: dep.readFailures, which\n // counts customers, so one customer with three holiday stays produced \"1 customer's payments\n // could not be read\" above a table showing three unknown rows and a headline saying 3.]\n const unknownRows = rows.filter((r) => r.state === \"could_not_check\").length;\n const unknowns = unknownRows\n ? `
${unknownRows === 1 ? \"1 stay\" : `${unknownRows} stays`} could not be checked when this ran, so ${unknownRows === 1 ? \"it is\" : \"they are\"} marked unknown rather than guessed at.
` : \"\";\n // EVERY ROW BELOW IS WRITTEN IN THE PRESENT TENSE. If the list is old, saying so at the bottom\n // in small print is not enough: somebody could have paid yesterday and the page would still read\n // \"no Square payment is on file\". Past a day and a half this goes at the TOP, where the reader\n // is before they start acting on names.\n const ageH = (Date.now() - Date.parse(dep.at)) / 3_600_000;\n // AN AGE THAT CANNOT BE READ IS NOT AN AGE OF ZERO. [was: `Number.isFinite(ageH) && ageH > 36`\n // alone, so an unparseable `at` made ageH NaN, skipped this banner silently, and a list of\n // completely unknown age looked identical at the top of the card to one checked a minute ago —\n // in the one place this card exists to be honest about.]\n const stale = !Number.isFinite(ageH)\n ? `
There is no readable date on this list, so there is no way to tell how old it is. Treat every row below as possibly out of date and check before you act on a name.
`\n : ageH > 36\n ? `
This list was last checked ${esc(agoFn(dep.at))}. Anyone who has paid since then will still show here as not found, so check the date before you act on a name.
` : \"\";\n // THE HEADLINE IS REGENERATED FROM THE ROWS ON THIS PAGE, never read from the blob.\n //\n // [was: `esc(dep.sentence)`, printed verbatim. The sentence and the rows are written by the same\n // run, so they agree — by convention, enforced nowhere. A stale, hand-edited or half-written\n // blob put \"No holiday boarding stays are booked in the deposit windows yet, so there is nothing\n // to check.\" directly above a table of three named people worth checking. Generating it here\n // from the rows being rendered makes that disagreement impossible rather than unlikely.]\n const sentence = depositSentence(rows.map((r) => ({ state: shown(r) === DEP_STATE.could_not_check ? \"could_not_check\" : r.state })), !!dep.feedDead);\n return `
Holiday deposits
\n
${esc(sentence)}
\n${stale}${missed}${noPickups}${unknowns}\n${dep.feedDead ? \"\" : rows.length ? `${body}
Who Stay Dogs Deposit
` : \"\"}\n
${windowLine(dep.windows)} $50 per dog, so a three-dog stay is $150. ${esc(OTHER_ROUTES)} Only overnight boarding stays are counted here; cancellations and everything else on the calendar are left out. Last checked ${esc(agoFn(dep.at))}.
\n
`;\n}\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n const k = url.searchParams.get(\"k\") || \"\";\n const admin = await isAdmin(k);\n if (!admin && !(await isViewer(k))) return new Response(\"Not found\", { status: 401 });\n\n const now = Date.now(), tz = ET();\n const wk = 7 * 86_400_000;\n const cur = { startMs: now - wk, endMs: now, label: \"last 7 days\" };\n const prev = { startMs: now - 2 * wk, endMs: now - wk, label: \"the 7 before\" };\n\n const cacheRead = await readBlob(CACHE_KEY);\n const cache = cacheRead.v ?? {};\n const stale: string[] = []; // sections served from cache, named for the reader\n const truncated: string[] = [];\n\n // v1.1 (review #1): every source runs CONCURRENTLY with its own budget. Sequentially, a merely\n // slow CRM could exceed the platform's request limit and the page would die entirely, which is\n // the one outcome this dashboard exists to prevent. Now the whole fetch phase costs one budget,\n // not the sum of them, and any single source can fail without touching the others.\n const BUDGET = 9_000;\n const budgeted = (p: Promise): Promise =>\n Promise.race([p, new Promise((_, rej) => setTimeout(() => rej(new Error(\"too slow\")), BUDGET))]);\n\n const [cRes, ptRes, oppRes, metaRes, tagRes, sqRes] = await Promise.allSettled([\n budgeted(contactsSince(now - 9 * wk, truncated)),\n budgeted((async () => {\n const d = await j(`/calendars/events?locationId=${LOC}&calendarId=${PUP_TALK_CAL}&startTime=${prev.startMs}&endTime=${now}`, \"2021-04-15\");\n return ((d?.events ?? []) as any[]).map((e: any) => ({\n startTime: typeof e.startTime === \"number\" ? e.startTime : Date.parse(e.startTime),\n appointmentStatus: e.appointmentStatus ?? \"unknown\", calendarId: PUP_TALK_CAL,\n })) as EventLite[];\n })()),\n budgeted((async () => {\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 const STAGES = [STAGE_CUSTOMER, STAGE_WON_PAID];\n const page = (stage: string, p: number) =>\n j(`/opportunities/search?location_id=${LOC}&limit=100&page=${p}&pipeline_stage_id=${stage}`, \"2021-07-28\");\n const acc: OppLite[] = [];\n let complete = true;\n for (const stage of STAGES) {\n const first = await page(stage, 1);\n const total = Number(first?.meta?.total ?? 0);\n const pages = Math.min(Math.ceil(total / 100) || 1, 40); // 40 pages = 4,000 records, a sane backstop\n if (Math.ceil(total / 100) > 40) complete = false;\n const rest = await Promise.all(\n Array.from({ length: Math.max(0, pages - 1) }, (_, i) => page(stage, i + 2).catch(() => null)),\n );\n for (const d of [first, ...rest]) {\n if (!d) { complete = false; continue; }\n for (const o of d?.opportunities ?? []) {\n // `status` is carried through as the CRM reports it. It used to be overwritten with \"won\" on\n // the way in, which meant the page could not see the field it went on to make claims about.\n acc.push({ createdAt: o.createdAt, status: String(o.status ?? \"open\"), monetaryValue: Number(o.monetaryValue) || 0, lastStageChangeAt: o.lastStageChangeAt ?? null });\n }\n }\n }\n if (!complete) truncated.push(\"customers\");\n return acc;\n })()),\n budgeted(metaWeek(cur.startMs, cur.endMs, tz)),\n // The Square backlog used to be four numbers typed into a sentence, and all four were wrong:\n // it said 35 payments worth $23,463.99 when the journal holds 40 worth $28,035.99, and it\n // never split the money between the recoverable and the unrecoverable. Read live now.\n // THE TAG THAT DECIDES WHETHER GO-LIVE REACHES ANYBODY, counted server side over the whole\n // contact base rather than sampled. Two calls, both filtered, both returning a total.\n // [was: the number 1,200 typed into a decision's evidence — a scan size presented as an\n // answer. Cross-checked 5 Aug: this filter and a full page-by-page walk of all 5,544\n // contacts agree exactly on \"no sale\" (133), \"tips-nurture\" (155) and \"customer\" (1,512).]\n budgeted((async () => {\n const count = async (tag: string | null): Promise => {\n const body: Record = { locationId: LOC, pageLimit: 1 };\n if (tag) body.filters = [{ field: \"tags\", operator: \"contains\", value: tag }];\n const r = await fetch(`${GHL}/contacts/search`, {\n method: \"POST\",\n headers: { Authorization: `Bearer ${await token()}`, Version: \"2021-07-28\", \"User-Agent\": \"curl/8.5.0\", \"Content-Type\": \"application/json\" },\n body: JSON.stringify(body),\n signal: AbortSignal.timeout(8_000),\n });\n if (!r.ok) throw new Error(`contacts/search ${r.status}`);\n return Number((await r.json())?.total ?? 0);\n };\n const [tagged, total] = await Promise.all([count(ENROLL_TAG), count(null)]);\n return { tag: ENROLL_TAG, tagged, total } as TagCoverage;\n })()),\n budgeted((async () => {\n const r = await fetch(`${BRIDGE}?dump=1&admin=${encodeURIComponent(Deno.env.get(\"BRIDGE_ADMIN\") || BRIDGE_ADMIN)}`,\n { signal: AbortSignal.timeout(15_000) });\n if (!r.ok) throw new Error(`bridge ${r.status}`);\n return squareBacklog(await r.json());\n })()),\n ]);\n\n const contacts: ContactLite[] | null = cRes.status === \"fulfilled\" ? cRes.value : null;\n const tagCov: TagCoverage | null = tagRes.status === \"fulfilled\" ? tagRes.value : null;\n const ptEvents: EventLite[] | null = ptRes.status === \"fulfilled\" ? ptRes.value : null;\n const opps: OppLite[] | null = oppRes.status === \"fulfilled\" ? oppRes.value : null;\n const meta = metaRes.status === \"fulfilled\" ? metaRes.value : null;\n const square = sqRes.status === \"fulfilled\" ? sqRes.value : null;\n const metaRaw = metaRes.status === \"rejected\" ? String(metaRes.reason).replace(/^Error:\\s*/, \"\") : null;\n const metaPending = metaRaw === \"PERMISSION\"; // linked, but Facebook has not granted reading yet\n const metaErr = metaPending ? null : (metaRaw ? metaRaw.slice(0, 80) : null);\n\n // computed, or pulled from cache with an honest label\n const C = cache.numbers ?? {};\n const A = cache.ages ?? {}; // per-section ISO stamps: a three-day-old number must not read \"a few minutes ago\"\n const inq = contacts ? countContacts(contacts, cur) : (C.inq ?? null);\n const inqPrev = contacts ? countContacts(contacts, prev) : (C.inqPrev ?? null);\n const srcAll = contacts ? sourceBreakdown(contacts, cur) : (C.srcAll ?? null);\n // PROVEN LIVE 4 Aug 2026: the source column was blank for 154 of 190, while the attribution\n // record placed 190 of 190. The page used to print \"no source recorded: 154\" and then guess in\n // prose that most were Messenger. It now reads the field that actually holds the answer.\n const chan = contacts ? channelBreakdown(contacts, cur) : (C.chan ?? null);\n const camps = contacts ? campaignBreakdown(contacts, cur) : (C.camps ?? null);\n const cover = contacts ? attributionCoverage(contacts, cur) : (C.cover ?? null);\n const buckets = contacts ? weeklyBuckets(contacts, now, 8) : (C.buckets ?? null);\n const pt = ptEvents ? countEvents(ptEvents, cur) : (C.pt ?? null);\n const ptPrev = ptEvents ? countEvents(ptEvents, prev) : (C.ptPrev ?? null);\n // Everything in `opps` is already stage-filtered to Customer/Won-Paid, so the STAGE is the\n // signal; the CRM's own status field is left untouched so the page can report on it honestly.\n const stageWon = (list: OppLite[] | null, w: { startMs: number; endMs: number }) => list\n ? { count: list.filter((o) => { const t = Date.parse(o.lastStageChangeAt || o.createdAt); return Number.isFinite(t) && t >= w.startMs && t < w.endMs; }).length, value: 0 }\n : null;\n const won = opps ? stageWon(opps, cur) : (C.won ?? null);\n // How often a price actually gets written on a deal. The page used to state flatly that every\n // opportunity sat at zero, which a reader disproved from the page's own Bootcamp figures. It is\n // 53 of 1,513, none of them in the last month. Counted here rather than claimed.\n const won2Total = opps ? opps.length : (C.won2Total ?? null);\n const valued = opps ? opps.filter((o) => Number(o.monetaryValue) > 0).length : (C.valued ?? null);\n const valuedTotal = opps ? opps.reduce((a, o) => a + (Number(o.monetaryValue) || 0), 0) : (C.valuedTotal ?? null);\n // \"none at all in the last month\" was typed into the template and would have read true forever,\n // including on the day somebody wrote one. Measured now, from the same records.\n const valuedRecentMs = opps\n ? (opps.filter((o) => Number(o.monetaryValue) > 0)\n .map((o) => Date.parse(o.lastStageChangeAt || o.createdAt)).filter((t) => Number.isFinite(t))\n .reduce((a, b) => Math.max(a, b), 0) || null)\n : (C.valuedRecentMs ?? null);\n const lostCount = opps ? opps.filter((o) => String(o.status).toLowerCase() === \"lost\").length : (C.lostCount ?? null);\n const wonPrev = opps ? stageWon(opps, prev) : (C.wonPrev ?? null);\n const missing: string[] = []; // failed AND no cached value to fall back on\n if (!contacts) (C.inq != null ? stale : missing).push(\"new inquiries\");\n if (!ptEvents) (C.pt ? stale : missing).push(\"Pup Talks\");\n if (!opps) (C.won ? stale : missing).push(\"new customers\");\n\n let googleErr: string | null = null;\n try { await googleWeek(); } catch (e) { googleErr = String(e).replace(/^Error:\\s*/, \"\").slice(0, 90); }\n\n const runR = await readBlob(\"puppy_run_state\"); const run = runR.v;\n const wd = await getBlob(\"wd_public\");\n const killR = await readBlob(\"nurture_kill\"); const kill = killR.v;\n const stateR = await readBlob(\"puppy_state\"); const state = stateR.v ?? {};\n const stateKnown = stateR.ok, runKnown = runR.ok && killR.ok;\n const liveLog = await getBlob(\"tds_worklog\");\n // What the tagging WOULD do, written down by the engine on every run. It applies nothing.\n const tagScan = await getBlob<{ at?: string; summary?: DetectSummary; applied?: boolean }>(\"tag_candidates\");\n // THE HOLIDAY DEPOSIT LIST. Read from the blob the collector writes, never recomputed here: the\n // collection is dozens of CRM calls and Kim's page must not wait for them. A read that FAILS and\n // a list that is genuinely EMPTY are kept apart, because \"no holiday stays booked\" and \"we could\n // not check\" look identical on a screen and only one of them is safe to show in November.\n const depR = await readBlob(\"holiday_deposits\");\n const dep = depR.v;\n const log = mergeLog(SEEDED, liveLog);\n\n const crmSources = [[\"contacts\", !!contacts], [\"appointments\", !!ptEvents], [\"deals\", !!opps]] as const;\n const crmDown = crmSources.filter(([, ok]) => !ok).map(([n]) => n);\n const crmOk = crmDown.length === 0;\n const crmPartial = crmDown.length > 0 && crmDown.length < 3;\n const engineAgeMin = run?.ts ? Math.floor((now - Date.parse(run.ts)) / 60000) : null;\n const engineCadence = observedCadenceMin(run?.history);\n const engineLate = lateness(engineAgeMin, engineCadence);\n const engineOk = isHealthy(engineLate.state) && !kill?.stopped;\n const practice = run?.testMode !== false;\n const wdAgeMin = wd?.ts ? Math.floor((now - Date.parse(wd.ts)) / 60000) : null;\n // SCHEDULED runs only. A rhythm measured over hand-triggered runs is a measurement of the hand.\n // [was: observedCadenceMin(wd?.history), where history mixes both. It produced \"left to itself\n // it runs about every 95 minutes\" out of stamps that were almost entirely me pressing the\n // check-now button, and put that sentence in front of Kim as the watchdog's schedule. The\n // watchdog now records autoHistory separately; older payloads have no such field, and the\n // honest answer for those is \"we cannot tell yet\" rather than the old number.]\n const wdAuto: string[] | null = Array.isArray(wd?.autoHistory) ? wd.autoHistory : null;\n const wdTracksTrigger = wdAuto != null;\n const wdNeverRanItself = wdTracksTrigger && wdAuto.length === 0;\n const wdCadence = wdTracksTrigger ? observedCadenceMin(wdAuto) : null;\n const wdAutoAgeMin = wd?.lastAutoTs ? Math.floor((now - Date.parse(wd.lastAutoTs)) / 60000) : null;\n // Graded on when it last ran ITSELF, not on when it was last poked.\n const wdLate = wdNeverRanItself\n ? { state: \"late\" as const, dueAt: null, lateAt: null }\n : lateness(wdTracksTrigger ? wdAutoAgeMin : wdAgeMin, wdCadence);\n // When did we start being able to tell the difference? The first stamp after the change.\n const wdTrackingSince: string | null = wdTracksTrigger && Array.isArray(wd?.history) && wd.history.length\n ? wd.history[wd.history.length - 1] : null;\n const wdManualSince = wdTracksTrigger && Array.isArray(wd?.history)\n ? wd.history.filter((t: string) => !wdTrackingSince || Date.parse(t) >= Date.parse(wdTrackingSince)).length\n : 0;\n // A watchdog that has not looked recently is not a passing watchdog, whatever its last report\n // said. Grading it purely on the contents of a stale report is how a page ends up putting a\n // green tick beside a system that stopped running an hour ago.\n const wdOk = !!wd && (wd.worst === \"OK\" || wd.worst === \"INFO\") && isHealthy(wdLate.state);\n\n // v1.1 (reviews #3, #8): each section carries its OWN timestamp so staleness is reported per\n // number, and the whole write is skipped when the cache could not be read, so a transient blob\n // hiccup can never erase good history for a section that happens to be failing today.\n if (cacheRead.ok && (contacts || ptEvents || opps)) {\n const nowIso = new Date().toISOString();\n try {\n await (await blobMod()).setJSON(CACHE_KEY, {\n at: nowIso,\n numbers: {\n inq: contacts ? inq : C.inq, inqPrev: contacts ? inqPrev : C.inqPrev,\n srcAll: contacts ? srcAll : C.srcAll, buckets: contacts ? buckets : C.buckets,\n chan: contacts ? chan : C.chan, camps: contacts ? camps : C.camps,\n cover: contacts ? cover : C.cover,\n pt: ptEvents ? pt : C.pt, ptPrev: ptEvents ? ptPrev : C.ptPrev,\n won: opps ? won : C.won, wonPrev: opps ? wonPrev : C.wonPrev,\n won2Total: opps ? won2Total : C.won2Total, valued: opps ? valued : C.valued,\n valuedTotal: opps ? valuedTotal : C.valuedTotal,\n valuedRecentMs: opps ? valuedRecentMs : C.valuedRecentMs, lostCount: opps ? lostCount : C.lostCount,\n },\n ages: {\n inq: contacts ? nowIso : A.inq, pt: ptEvents ? nowIso : A.pt, won: opps ? nowIso : A.won,\n },\n });\n } catch { /* the cache is a nicety; never fail the page over it */ }\n }\n\n if (admin && url.searchParams.get(\"f\") === \"json\") {\n return new Response(JSON.stringify({ inq, inqPrev, pt, won, meta, stale, crmOk, engineOk, practice, wd }, null, 2),\n { headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" } });\n }\n\n // each stale section reports ITS OWN age, not the cache blob's last-write time\n const sectionAge = (label: string) =>\n label === \"new inquiries\" ? (A.inq ?? cache.at) : label === \"Pup Talks\" ? (A.pt ?? cache.at) : (A.won ?? cache.at);\n\n // An appointment nobody has marked is silently counted as \"not a no-show\", which flatters the\n // show-up figure. The page says so, using a number it counts live rather than one typed here.\n const unmarked = pt ? Math.max(0, pt.booked - pt.showed - pt.noshow) : null;\n const otherBucket = contacts ? otherBucketExplanation(contacts as any, cur) : null;\n const ctx: Ctx = {\n unmarkedPupTalks: unmarked,\n inquiriesPerWeek: inq ?? null,\n squareSentence: square ? squareSentence(square) : null,\n // null when the read failed, so the decision says \"unconfirmed\" rather than \"zero\".\n puppyTagSentence: tagCov ? tagCoverageSentence(tagCov) : null,\n // The dry tagging pass. Present only when the engine has actually run one.\n tagScanSentence: tagScan?.summary && tagScan.applied === false\n ? [detectSentence(tagScan.summary), scanAgeNote(tagScan.at, now)].filter(Boolean).join(\" \")\n : null,\n };\n // Both of these used to be typed into the sentence: \"four in five\" (it was 84%) and a claim that\n // the rest \"picked up the phone\" (the arrival record has no phone category at all, so the chart\n // could never show one). Derived now, or not stated.\n const socialShare = chan && inq\n ? Math.round(100 * (chan as any[]).filter((c) => /Facebook|Instagram/i.test(c.source)).reduce((a, c) => a + c.n, 0) / inq)\n : null;\n // No null-coalescing to zero anywhere in this region, deliberately: an unread source list must\n // stay null rather than become a confident zero. A missing phone row and a list we could not read\n // are different facts, and only one of them is safe to print. (The literal pattern is kept out of\n // this comment too, because the test that enforces the rule scans the region as text.)\n const phoneRow = srcAll ? (srcAll as any[]).find((s0) => /phone/i.test(s0.source)) : null;\n const phoneLogged: number | null = srcAll ? (phoneRow ? phoneRow.n : 0) : null;\n const decisions = sortedDecisions();\n const blocking = blockingCount();\n\n // ---- headline verdict ------------------------------------------------------------------\n const problems: string[] = [];\n if (!crmOk) problems.push(\"the CRM is not answering\");\n if (!runKnown) problems.push(\"we could not check whether the follow-up system is running\");\n else if (kill?.stopped) problems.push(\"the follow-up system is stopped\");\n else if (!engineOk) problems.push(\"the follow-up system is running late\");\n if (wd && wd.worst === \"CRITICAL\") problems.push(\"the watchdog found a problem\");\n else if (wd && wdNeverRanItself) problems.push(\"we cannot yet show the watchdog keeping its own time\");\n else if (wd && wdLate.state === \"late\") problems.push(\"the watchdog has not looked recently\");\n const allWell = problems.length === 0;\n // problems[] is built from fixed strings above, but it is still assembled text that reaches the\n // page: escaped at the point of use (the hero line calls esc(verdict)), and kept a plain join\n // here so the escape has exactly one place to live.\n // A row below can wear a warning triangle for being merely overdue, which is not a problem worth\n // alarming Kim about. But the headline may not then say \"everything is running\" as though nothing\n // on the page were marked: the reader can see the triangle, and a headline that ignores it is the\n // same contradiction the stranger test rejected, moved up one level. So the headline names it.\n const liveIssues = decisions.filter((d) => d.liveNow).length;\n const running = [engineLate.state, wd ? wdLate.state : \"ok\"].filter((x) => x === \"due\").length;\n const liveNote = liveIssues ? ` Separately, ${liveIssues === 1 ? \"one question below is marked\" : `${liveIssues} questions below are marked`} HAPPENING NOW: ${liveIssues === 1 ? \"that one is\" : \"those are\"} already affecting customers rather than waiting on go-live.` : \"\";\n const behindNote = running ? ` ${running === 1 ? \"One part of it is\" : `${running} parts of it are`} running a little behind schedule, which happens and sorts itself out.` : \"\";\n const verdict = allWell\n ? (runKnown && practice\n ? `Everything we run is healthy. The follow-up system is in practice mode, so it is not messaging anyone yet, and ${blocking === 0 ? \"nothing is holding that up\" : `${blocking} ${blocking === 1 ? \"thing is\" : \"things are\"} holding up switching it on`}.${liveNote}${behindNote}`\n : `Everything is running normally.${liveNote}${behindNote}`)\n : \"Needs a look: \" + problems.join(\", \") + \".\";\n\n const tile = (label: string, v: string, note: string, accent?: string) =>\n `
${esc(v)}
${esc(label)}
${esc(note)}
`;\n const na = (v: number | null | undefined) => (v == null ? \"n/a\" : String(v));\n\n const checkRow = (ok: boolean, name: string, detail: string) =>\n `
${ok ? \"✓\" : \"⚠\"}
${esc(name)}
${esc(detail)}
`;\n\n // channel chart: top 3 named sources + Other, labeled directly (secondary encoding, per the\n // dataviz rule that a sub-3:1 slot needs visible labels)\n // v1.2 (stranger test): the old build assigned color index 2 to BOTH the third named source\n // and the catch-all roll-up beside it, so two adjacent segments and their two legend swatches\n // were pixel-identical and could not be told apart by looking. A roll-up bucket is not a peer\n // of the named categories anyway; it now takes the recessive gray the dataviz rules reserve for\n // it, which frees all three categorical slots for real, distinguishable channels.\n const chanRows = (chan ?? []).slice(0, 3);\n const chanOther = (chan ?? []).slice(3).reduce((a: number, s: any) => a + s.n, 0);\n const chanTotal = (chan ?? []).reduce((a: number, s: any) => a + s.n, 0) || 1;\n const segs = [\n ...chanRows.map((s: any, i: number) => ({ ...s, fill: `var(--c${i})` })),\n ...(chanOther ? [{ source: \"smaller channels added up\", n: chanOther, fill: \"var(--barq)\" }] : []),\n ];\n const share = (n: number) => `${Math.round((n / chanTotal) * 100)}%`;\n const chanBar = segs.map((s: any) =>\n ``).join(\"\");\n // Every row carries its share as well as its count. A bare 154 is a number; 81% is a decision.\n const chanLegend = segs.map((s: any) =>\n `
${esc(s.source)}${s.n} (${share(s.n)})
`).join(\"\");\n const campTop = (camps ?? []).slice(0, 5);\n const campShown = campTop.reduce((a: number, c: any) => a + c.n, 0);\n const campTotal = (camps ?? []).reduce((a: number, c: any) => a + c.n, 0);\n const campRows = campTop.map((c: any) =>\n `
${esc(c.name)}${c.n}
`).join(\"\");\n\n const maxB = Math.max(1, ...((buckets ?? [1]) as number[]));\n const bars = ((buckets ?? []) as number[]).map((b, i, arr) =>\n `
${b}
`).join(\"\");\n\n const adCard = (name: string, connected: boolean, spend: string, result: string, note: string) =>\n `
${esc(name)}
${connected\n ? `
${esc(spend)}
spent, last 7 days
${esc(result)}
conversations started
`\n : `
${esc(note)}
`}
`;\n\n // Kim's reading order, from her own test: banner, first blocker, the four numbers, gone. The\n // history is the part she cannot act on, so it is the part that folds; the asks stay open.\n const LOG_SHOWN = 6;\n const logRow = (e: WorkEntry) => {\n const col = e.kind === \"broke\" ? CRIT : e.kind === \"mine\" ? WARN : e.kind === \"found\" ? WARN : GOOD;\n return `
${esc(KIND_LABEL[e.kind] ?? e.kind)}
${esc(e.what)}
${e.evidence ? `
How we know: ${esc(e.evidence)}
` : \"\"}
${esc(prettyDate(e.at))}
`;\n };\n const logRows = log.slice(0, LOG_SHOWN).map(logRow).join(\"\");\n const logRest = Math.max(0, log.length - LOG_SHOWN);\n const logRestRows = log.slice(LOG_SHOWN).map(logRow).join(\"\");\n\n // Eight-week direction. The tiles compare one week to the week before, which is noise at this\n // volume: the account's own week-on-week swings run to plus and minus thirty. The trend across\n // the whole chart is the sentence the reader actually wants, and it was the one thing on the\n // page nobody was saying out loud.\n const trendLine = (() => {\n const b = (buckets ?? []) as number[];\n if (b.length < 4) return \"\";\n const firstHalf = b.slice(0, Math.floor(b.length / 2)), lastHalf = b.slice(-Math.floor(b.length / 2));\n const a = firstHalf.reduce((x, y) => x + y, 0) / firstHalf.length;\n const z = lastHalf.reduce((x, y) => x + y, 0) / lastHalf.length;\n if (!a) return \"\";\n const ch = Math.round(((z - a) / a) * 100);\n if (Math.abs(ch) < 10) return `Averaged out, inquiries are running about level across these eight weeks, near ${Math.round(z)} a week.`;\n return `Averaged out, inquiries are ${ch > 0 ? \"up\" : \"down\"} ${Math.abs(ch)}% across these eight weeks: about ${Math.round(a)} a week over the first month, about ${Math.round(z)} a week over the last month.`;\n })();\n\n // The first reader's whole test was ninety seconds in a car park. Answering the second and third\n // readers added items until this card had twelve, which would have pushed every number below the\n // fold and failed her test to satisfy theirs. So the ones that actually hold up go-live are set\n // out in full, and the rest are listed as plain questions behind a fold she opens if she wants.\n // Nothing is hidden: the full text of every one is in the page, one tap away, and the count is\n // stated. It is an ordering decision, not an omission.\n // Numbered, because the page asks thirteen questions and gives her no way to answer them except\n // a message. \"Yes to 1 and 4\" is a reply she can type one-handed at 6am. An unnumbered list is\n // not.\n const numberOf = new Map(decisions.map((d, i) => [d.ref, i + 1]));\n const full = (d: Decision) =>\n `
${d.liveNow ? \"Happening now\" : esc(WEIGHT_LABEL[d.weight])}
` +\n `
${numberOf.get(d.ref)}. ${esc(d.ask)}
${esc(whyText(d, ctx))}
` +\n `
How we know: ${esc(evidenceText(d, ctx))}
` +\n (ifYesText(d, ctx) ? `
If you say yes: ${esc(ifYesText(d, ctx))}
` : \"\") +\n (extraText(d, ctx) ? `
${esc(extraText(d, ctx))}
` : \"\") +\n `
If you say nothing: ${esc(d.ifNothing)}
`;\n // Shown in full: anything that blocks go-live, AND anything already affecting real customers.\n // The first draft of this fold put a live double-messaging issue behind a summary reading \"none\n // of which hold anything up\", one line under a banner announcing it. Blocking and live-now are\n // different reasons to be at the top, and both earn it.\n const upFront = (d: Decision) => d.weight === \"blocking\" || !!d.liveNow || !!d.surface;\n const blockers = decisions.filter(upFront);\n const rest = decisions.filter((d) => !upFront(d));\n const decRows = blockers.map(full).join(\"\")\n + (rest.length\n ? `
${rest.length} more, none of which hold anything up${rest.some((d) => d.liveNow) ? `, though ${rest.filter((d) => d.liveNow).length === 1 ? \"one is\" : `${rest.filter((d) => d.liveNow).length} are`} already running against customers` : \" or affect anybody today\"}
${rest.map(full).join(\"\")}
`\n : \"\");\n\n // THE FUNNEL. Every piece of this was already on the page and the page never put it together.\n // A reader called it \"the whole ballgame\": assembled, it says what share of inquiries becomes a\n // customer. Rendered only when every step read successfully, because a funnel with a hole in it\n // invites exactly the wrong conclusion.\n const funnelReady = inq != null && pt != null && won != null && !truncated.includes(\"customers\");\n const rate = (a: number, b: number) => (b > 0 ? `${(100 * a / b).toFixed(a / b < 0.1 ? 1 : 0)}%` : \"n/a\");\n const funnelRows = funnelReady\n ? [\n { label: \"New inquiries\", n: inq as number, of: null as string | null },\n { label: \"Pup Talks on the calendar\", n: pt!.booked, of: `${rate(pt!.booked, inq as number)} of inquiries` },\n { label: \"Showed up\", n: pt!.showed, of: `${rate(pt!.showed, pt!.booked)} of the ${pt!.booked} that were held${pt!.cancelled ? `, ${rate(pt!.showed, pt!.booked + pt!.cancelled)} of all ${pt!.booked + pt!.cancelled} booked` : \"\"}` },\n { label: \"Became customers\", n: won!.count, of: \"in the same 7 days, but mostly from earlier inquiries\" },\n ]\n : [];\n const funnelMax = Math.max(1, ...funnelRows.map((r) => r.n));\n const funnelHtml = funnelRows.map((r, i) =>\n `
${esc(r.label)}
` +\n `
${i === 3\n ? \"\"\n : ``}
` +\n `
${r.n}${r.of ? ` ${esc(r.of)}` : \"\"}
`).join(\"\");\n\n // The page said \"1 in a sequence: people currently walking through the follow-up messages\".\n // That one record is the sanctioned test dummy (contact mxf92ajJDtsZMHqJxAKv, every one of its\n // sends flagged test:true). Calling a synthetic record a person is the single most misleading\n // thing this page has ever said, so the count of REAL people is derived separately and the copy\n // branches on it rather than on the raw total.\n const isTestRecord = (k: string, v: any) =>\n v?.test === true || v?.isTest === true || /dummy|zztest/i.test(String(v?.name ?? v?.contactName ?? \"\")) || k === TEST_DUMMY_ID;\n const SOURCE_TAG = \"nurture - puppy\";\n const TEST_DUMMY_ID = \"mxf92ajJDtsZMHqJxAKv\";\n const ENROLLED = [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"];\n const realPeople = Object.entries(state).filter(([k, v]: any) =>\n ENROLLED.includes(v?.status) && !isTestRecord(k, v)).length;\n const activeN = Object.values(state).filter((s: any) =>\n [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"].includes(s?.status)).length;\n const pausedN = Object.values(state).filter((s: any) => s?.status === \"paused_reply\").length;\n\n const html = `\n\nThe Dogs Spot dashboard\n
\n\n
The Dogs Spot
\n
This page reads your systems the moment you open it. Refresh any time.
\n\n
${allWell ? \"✓\" : \"⚠\"} ${esc(verdict)}
\n${decisions.length ? `
${decisions.length} question${decisions.length === 1 ? \"\" : \"s\"} on this page ${decisions.length === 1 ? \"is\" : \"are\"} waiting on a word from you, ${blocking} of ${blocking === 1 ? \"which holds\" : \"which hold\"} up go-live. They are the first card below, most pressing first.
` : \"\"}
\n\n
Waiting on you
\n
The first few hold up go-live. The rest can wait as long as you like. Each one says how we know it is real and what happens if you never answer, because for most of them the answer is nothing bad. They are numbered, so a reply saying \"yes to 1 and 3\" is a complete answer. The numbers stay attached to the same questions week to week, so the list below runs out of order once the quieter ones are tucked away. Send it to Amir on Upwork, or say it on the next call.
\n${decRows}\n
\n\n${stale.length || missing.length || truncated.length ? `
Heads up: ${\n stale.length ? `${esc(stale.map((s) => `${s} (last read ${ago(sectionAge(s))})`).join(\", \"))} could not be read at this moment, so ${stale.length === 1 ? \"that number is the last one\" : \"those numbers are the last ones\"} we read successfully. ` : \"\"\n}${missing.length ? `${esc(missing.join(\" and \"))} could not be read and there is no earlier reading to show, so ${missing.length === 1 ? \"it shows\" : \"they show\"} as n/a. ` : \"\"\n}${truncated.length ? `you have enough records that we stopped reading partway through rather than keep you waiting, so ${truncated.length === 1 ? \"the count of\" : \"the counts of\"} ${esc(truncated.join(\" and \"))} ${truncated.length === 1 ? \"is a floor\" : \"are floors\"}, not ${truncated.length === 1 ? \"a total\" : \"totals\"}. The real number is that one or higher, never lower. ` : \"\"\n}Every other number on this page was read fresh just now. Refreshing in a few minutes normally gets the rest.
` : \"\"}\n\n
\n${tile(\"New inquiries\", na(inq), inq != null && inqPrev != null ? `last 7 days, ${vs(inq, inqPrev)}` : \"last 7 days\", undefined)}\n${tile(\"Pup Talks on the calendar\", pt ? String(pt.booked) : \"n/a\", pt && ptPrev ? `held in the last 7 days, ${vs(pt.booked, ptPrev.booked)}` : \"held in the last 7 days\")}\n${tile(\"Showed up\", pt ? String(pt.showed) : \"n/a\", pt ? (() => {\n const un = Math.max(0, pt.booked - pt.showed - pt.noshow);\n const bits = [`of the ${pt.booked} held`];\n if (pt.noshow) bits.push(`${pt.noshow} did not show`);\n // every appointment in the denominator has to be accounted for, or the reader is left doing\n // subtraction on the front tile and finding a number missing\n if (un) bits.push(`${un} ${un === 1 ? \"has\" : \"have\"} not been marked yet, so this figure is flattering by up to ${un}`);\n const tail = pt.cancelled ? ` A further ${pt.cancelled} cancelled ahead of time and ${pt.cancelled === 1 ? \"is\" : \"are\"} not counted in the ${pt.booked}.` : \"\";\n return bits.join(\", \") + \".\" + tail;\n })() : \"last 7 days\")}\n${tile(\"New customers\", won ? String(won.count) : \"n/a\", truncated.includes(\"customers\") ? \"reached the Customer stage. At least this many: see the note above\" : won && wonPrev ? `reached the Customer stage, ${vs(won.count, wonPrev.count)}` : \"reached the Customer stage, last 7 days\", undefined)}\n
\n\n${depositCard(dep, depR.ok, ago)}\n\n${funnelReady ? `
From first contact to paying customer
\n
Four counts over the same 7 days. An inquiry is any new person who reached you and landed in your CRM: a Facebook or Instagram message, a form, the chat box, or a phone call somebody logged.
\n${funnelHtml}\n
Before reading that first gap as bad news: ${socialShare != null ? `${socialShare}% of these inquiries` : \"most of these inquiries\"} arrived as a message on Facebook or Instagram, and a message costs the sender nothing, so plenty were never close to booking. Worth knowing what this cannot tell you: your CRM's arrival record has no category for a phone call at all, so callers are not separated out here. The old source column logged ${esc(String(phoneLogged ?? \"some\"))} phone calls this week, but that column is blank for most people, so neither of us can put a firm number on how many of these actually rang you. The first three rows follow the same people through. The last one does not, and it would be dishonest to draw an arrow to it: somebody who became a customer this week usually first got in touch weeks or months ago, so they are not part of the ${esc(String(inq))} above. Read it as four true counts over the same seven days rather than one conversion rate. The gap between inquiries and Pup Talks is the widest of them, and it is the one worth a conversation.
\n
` : \"\"}\n\n
Is everything working?
\n${checkRow(crmOk, \"Your CRM\", crmOk ? \"Answering normally. This page just read it.\" : crmPartial ? `Answered for some things but not for ${esc(crmDown.join(\" and \"))} just now. If this is still showing in an hour, tell Amir.` : \"Did not answer just now. If this is still showing in an hour, tell Amir.\")}\n${checkRow(engineOk, \"The follow-up system\", kill?.stopped\n ? \"Stopped by the big red button. Nothing is being sent.\"\n : engineAgeMin == null ? \"No check-in recorded yet.\"\n : `Last checked itself ${ago(run?.ts)}. ${lateSentence(engineLate, engineCadence)}`)}\n${checkRow(wdOk, \"The watchdog\", wd\n ? wdNeverRanItself\n ? `${wd.headline} Last look ${ago(wd.ts)}, started by hand. ${neverRanItselfSentence(wdTrackingSince, wdManualSince)}`\n : `${wd.headline} Last look ${ago(wd.ts)}. ${lateSentence(wdLate, wdCadence)}${wdLate.state === \"late\" ? \" Treat that last report as out of date until it looks again.\" : \"\"}`\n : \"No report from the watchdog yet.\")}\n${meta ? checkRow(true, \"Facebook ad spend\", \"Connected and reporting. Your spend is in the advertising section below.\")\n : metaPending ? `
•
Facebook ad spend
Half connected. Your ad account is named here, and Facebook has not yet given us permission to read what you spend on it, so the connection does not work yet. That is one setting on Amir's side, not a fault. It is the only reason this page can show you what came in but not what it cost.
`\n : metaErr ? checkRow(false, \"Facebook ad spend\", `Not reading right now: ${metaErr}`)\n : `
•
Facebook ad spend
Not linked yet, so this page cannot show what you spent. Where your inquiries came from is shown below regardless, because that comes from your own records rather than from Facebook.
`}\n
\n\n
Where the last 7 days of inquiries came from
\n${chan ? `
${chanBar}
${chanLegend}
` : `
Could not read this just now.
`}\n${cover ? `
${cover.known === cover.total ? `Every one of these ${cover.total}` : `${cover.known} of these ${cover.total}`} carries a record of how they arrived, though for some that record just says \"other\", so treat the named channels as the solid part. Worth knowing: the CRM's own \"source\" column is blank for ${esc(String(((srcAll ?? []) as any[]).find((s: any) => s.source === \"no source recorded\")?.n ?? 0))} of these, so any list built off that column will look like you have no idea where your customers come from. You do. It is recorded one field over.
` : \"\"}\n${otherBucket && otherBucketSentence(otherBucket) ? `
${esc(otherBucketSentence(otherBucket))}
` : \"\"}\n${campRows ? `
Which ads they answered
${campRows}
${\n campShown < campTotal\n ? `The ${Math.min(5, (camps ?? []).length)} biggest, covering ${campShown} of the ${campTotal} people who answered a named ad. The remaining ${campTotal - campShown} are spread across ${Math.max(0, (camps ?? []).length - 5)} smaller ones. `\n : `All ${campTotal} people who answered a named ad. `\n}${inq != null && campTotal < inq ? `The other ${inq - campTotal} of your ${inq} inquiries came in without a campaign attached, which is normal for people who message you directly rather than clicking an ad. ` : \"\"}These are the campaign names exactly as they appear in your ad account. Counted from your own records rather than from Facebook, so it stays true whether or not the ad account is linked.
` : \"\"}\n
\n\n
New inquiries, week by week
\n${buckets ? `
${bars}
Eight weeks, oldest on the left. The last bar is the last 7 days.${trendLine ? ` ${esc(trendLine)}` : \"\"}
` : `
Could not read this just now.
`}\n
\n\n${meta || metaErr ? `
What the advertising cost
\n${adCard(\"Facebook and Instagram\", !!meta, meta ? money(meta.spend) : \"\", meta ? String(meta.conv) : \"\", metaErr ? `Not reading right now: ${metaErr}` : \"\")}\n${meta ? `
Spend covers the seven full days up to yesterday, which is the last day the ad platform reports as final. Set against the ${esc(String(inq ?? \"n/a\"))} inquiries above, that is ${meta && inq ? esc(money(meta.spend / inq)) : \"n/a\"} each.
` : \"\"}\n${googleErr ? `
Google: ${esc(googleErr)}
` : \"\"}\n
` : \"\"}\n\n
What we have been doing
\n
Newest first. Each line names how it was checked, so you can pick any one and hold it up against the thing itself. Anything marked \"my mistake\" is one of mine, kept here on purpose rather than quietly fixed.
\n${logRows || `
Nothing recorded yet.
`}\n${logRest ? `
${logRest} older ${logRest === 1 ? \"entry\" : \"entries\"}
${logRestRows}
` : \"\"}\n
\n\n
One thing worth fixing in the CRM
\n
${valued != null && valuedTotal != null && won2Total\n ? `A price gets written on about one deal in ${Math.max(2, Math.round(won2Total / Math.max(1, valued)))}: ${valued} of your ${won2Total} customer records carry one, ${money(valuedTotal)} between them. The most recent was ${valuedRecentMs ? esc(prettyDate(new Date(valuedRecentMs).toISOString()) + \" \" + new Date(valuedRecentMs).getUTCFullYear()) : \"further back than these records reach\"}. So the habit exists and it lapsed.`\n : \"Most of your deals do not carry a value.\"}${lostCount != null ? ` Across all ${won2Total} of those records, ${lostCount === 0 ? \"not one is marked won or lost\" : `${lostCount} ${lostCount === 1 ? \"is\" : \"are\"} marked lost and none at all are marked won`}.` : \"\"} So to be plain about it: this card carries no money in it, in or out, only counts of people. That is why it counts people reaching the Customer stage rather than showing you revenue: a figure built on that few would be worse than no figure at all. Writing the price on each deal as it closes is the single change that would let this page show you what a week was worth.
\n\n
The follow-up system, in detail
\n${runKnown\n ? `
${practice ? \"⚠\" : \"✓\"}
${practice ? \"Practice mode\" : \"Live\"}
${practice ? \"It is doing everything except actually sending. Nobody real is being messaged. It goes live only when you say the word.\" : \"Real messages are going to real people.\"}
`\n : `
⚠
Practice or live: could not check
The system's own record did not answer just now, so this page will not guess. Refresh in a minute.
`}\n${stateKnown\n ? `
0 ? WARN : GOOD}\">${pausedN > 0 ? \"⚠\" : \"✓\"}
${pausedN > 0 ? `${pausedN} person${pausedN === 1 ? \"\" : \"s\"} replied and ${pausedN === 1 ? \"is\" : \"are\"} waiting on you` : \"Nobody is waiting on a reply from you\"}
${pausedN > 0 ? \"The system stepped back the moment they wrote to you. Answer them in your inbox; that is the only job this system ever hands you.\" : \"When somebody replies, the system stops messaging them and they appear here. That is the only job it ever hands you.\"}
\n
${realPeople ? \"✓\" : \"⚠\"}
${realPeople === 0 ? \"Nobody real is in the sequence yet\" : `${realPeople} in a sequence`}
${realPeople === 0\n ? `In practice mode the system runs against ${activeN === 0 ? \"no records at all\" : `${activeN} test record${activeN === 1 ? \"\" : \"s\"} of ours`} and has never sent to or processed one of your actual inquiries. That is deliberate: it is how we prove the machinery works without touching anybody. People join by carrying the tag \"${esc(SOURCE_TAG)}\". A person can put that tag on today, and anyone marked simply waits, untouched, until the switch is thrown. No automation applies the tag yet, so that tagging gets switched on in the same move as go-live.`\n : \"People currently walking through the follow-up messages.\"}
`\n : `
⚠
Who is in the system: could not check
This page will not show you a zero it cannot stand behind. Refresh in a minute.
`}\n
\n\n
Read live ${esc(prettyDate(new Date(now + tz * 60_000).toISOString()) + \" at \" + new Date(now + tz * 60_000).toISOString().slice(11, 16))} Georgia time. The four counts at the top, the funnel, both breakdowns and the week-by-week chart ${stale.length || missing.length || truncated.length ? \"were read from your own systems just now, apart from the ones named at the top\" : \"were read from your own systems just now\"}. The questions and the list of work are written by hand, and each one carries the check that backs it.
\n
`;\n\n return new Response(html, { headers: { \"content-type\": \"text/html; charset=utf-8\", \"cache-control\": \"no-store\" } });\n}\n",[325],"b45f58b5-564d-491b-a9ac-642ffdfcff88","cpl.ts","e52967e0-941c-11f1-8def-1607ee4eb77e",473,["D",1786298724982],"// COST PER LEAD, v1.0, 9 Aug 2026. GHL leads grouped by attributionSource.adId, joined to Meta\n// spend into per-campaign cost per lead. The val orchestrator wires these together and fetches\n// Meta itself; nothing here runs unattended, writes anything, or is a route.\n// WHY attributionSource, not attributions[] (report.ts/dashboard.ts's field): proven live 9 Aug —\n// GET /contacts/ (contactsSince, report.ts:70-92) has attributions[]/utmAdId, no attributionSource;\n// POST /contacts/search has attributionSource.adId directly; both agree on the total, 175 contacts\n// for 31 Jul-6 Aug. Window filter is report-logic.ts's inWindow (report-logic.ts:38-41): same rule\n// as \"New inquiries\".\ndeclare const Deno: { env: { get(k: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\nimport { inWindow, money, type Window } from \"./report-logic.ts\";\nexport type { Window };\n\nexport const LOC = \"BQHJ19uohldYe3eqA0bl\";\nconst GHL = \"https://services.leadconnectorhq.com\";\n\n// ---- 1. GHL PULL, GROUPED BY AD ----\n\nexport type AdCount = { adId: string | null; n: number };\n// Network as an argument, shape of deposits.ts's io.get (deposits.ts:212): tests use a fixture.\nexport type GhlIo = { post: (path: string, version: string, body: unknown) => Promise };\n\nexport async function pullAdCounts(io: GhlIo, w: Window, errorsOut: string[]): Promise {\n const counts = new Map();\n let searchAfter: any;\n let reachedFloor = false;\n for (let page = 0; page < 40; page++) {\n const body: Record = { locationId: LOC, pageLimit: 100 };\n if (searchAfter) body.searchAfter = searchAfter;\n const d = await io.post(\"/contacts/search\", \"2021-07-28\", body);\n const cs = d?.contacts ?? [];\n if (!cs.length) break;\n for (const c of cs) {\n if (!inWindow(c.dateAdded, w)) continue;\n const adId = c?.attributionSource?.adId || null;\n const k = adId ?? \"\";\n counts.set(k, (counts.get(k) ?? 0) + 1);\n }\n const oldest = Date.parse(cs[cs.length - 1]?.dateAdded ?? \"\");\n searchAfter = cs[cs.length - 1]?.searchAfter;\n if (Number.isFinite(oldest) && oldest < w.startMs) { reachedFloor = true; break; }\n if (!searchAfter) { reachedFloor = true; break; }\n }\n // contactsSince's reachedFloor warning (report.ts:90): never silently read as \"no leads\".\n if (!reachedFloor) errorsOut.push(\"Contact pull hit the page cap before covering the window; ad counts may undercount\");\n return [...counts.entries()]\n .map(([k, n]) => ({ adId: k === \"\" ? null : k, n }))\n .sort((a, b) => b.n - a.n || String(a.adId).localeCompare(String(b.adId)));\n}\n\n// A ready io for real use (token resolution stays with the caller).\nexport function liveGhlIo(token: string): GhlIo {\n return {\n post: async (path, version, body) => {\n const r = await fetch(`${GHL}${path}`, {\n method: \"POST\",\n headers: { Authorization: `Bearer ${token}`, Version: version, \"User-Agent\": \"curl/8.5.0\", \"Content-Type\": \"application/json\" },\n body: JSON.stringify(body),\n signal: AbortSignal.timeout(25_000),\n });\n if (!r.ok) throw new Error(`GHL ${path} -> HTTP ${r.status}`);\n return r.json();\n },\n };\n}\n\n// ---- 2. JOIN TO PER-CAMPAIGN COST PER LEAD, pure, no network ----\n\nexport type AdSpend = { campaign: string; spend: number };\nexport type CampaignCPL = {\n campaign: string; leads: number; spend: number; spendStr: string;\n cpl: number | null; cplStr: string;\n formula: string; // spend / leads with real numbers in it (report-logic.ts:52's formula)\n};\n// noAdId: leads with no ad attribution at all. noSpendData: leads on a real adId Meta had no spend row for.\nexport type CPLResult = { campaigns: CampaignCPL[]; noAdId: number; noSpendData: number };\n\nexport function joinCostPerLead(counts: AdCount[], adSpend: Record): CPLResult {\n const byCampaign = new Map();\n const row = (name: string) => byCampaign.get(name) ?? { spend: 0, leads: 0 };\n for (const s of Object.values(adSpend)) {\n const r = row(s.campaign); r.spend += Number(s.spend) || 0; byCampaign.set(s.campaign, r);\n }\n let noAdId = 0, noSpendData = 0;\n for (const { adId, n } of counts) {\n if (!adId) { noAdId += n; continue; }\n const s = adSpend[adId];\n if (!s) { noSpendData += n; continue; }\n const r = row(s.campaign); r.leads += n; byCampaign.set(s.campaign, r);\n }\n const campaigns = [...byCampaign.entries()].map(([campaign, { spend, leads }]) => {\n const cpl = leads > 0 ? spend / leads : null;\n const spendStr = money(spend), cplStr = cpl === null ? \"n/a\" : money(cpl);\n const formula = `${spendStr} / ${leads} lead${leads === 1 ? \"\" : \"s\"} = ${cplStr}`;\n return { campaign, leads, spend, spendStr, cpl, cplStr, formula };\n }).sort((a, b) => b.spend - a.spend || a.campaign.localeCompare(b.campaign));\n return { campaigns, noAdId, noSpendData };\n}\n\n// ---- 3. META AD SPEND, defensive: every failure is a value, never a throw ----\n// A hiccup reads as \"spend not available now\", never crashes the unattended run. Same ET-day\n// slicing + unencoded time_range as report.ts's metaSpend (report.ts:135-141) — matched, not\n// \"improved\": the one Meta call run live so far.\n\nexport type MetaAdRow = { adId: string; adName: string; campaign: string; spend: number };\nexport type MetaResult = { ok: true; rows: MetaAdRow[]; truncated?: string } | { ok: false; why: string };\n\n// Mirrors report.ts:29-34, copied not imported: report.ts is an HTTP entry point, no exports.\nexport function etOffsetMin(atMs: number): number {\n const fmt = new Intl.DateTimeFormat(\"en-US\", { timeZone: \"America/New_York\", timeZoneName: \"shortOffset\" });\n const part = fmt.formatToParts(new Date(atMs)).find((p) => p.type === \"timeZoneName\")?.value ?? \"GMT-4\";\n const m = part.match(/GMT([+-]\\d+)/);\n return m ? Number(m[1]) * 60 : -240;\n}\n\nexport async function fetchMetaAdSpend(w: { startMs: number; endMs: number }, tzOffsetMin: number): Promise {\n const tok = Deno.env.get(\"META_TOKEN\"), act = Deno.env.get(\"META_AD_ACCOUNT\");\n if (!tok) return { ok: false, why: \"META_TOKEN is not set\" };\n if (!act) return { ok: false, why: \"META_AD_ACCOUNT is not set\" };\n const day = (ms: number) => new Date(ms + tzOffsetMin * 60_000).toISOString().slice(0, 10);\n const since = day(w.startMs), until = day(w.endMs - 86_400_000);\n // level=ad, one row per ad; limit=500 covers this account (17 ads seen in one live week).\n const url = `https://graph.facebook.com/v21.0/${act}/insights?level=ad&fields=ad_id,ad_name,campaign_name,spend&time_range={\"since\":\"${since}\",\"until\":\"${until}\"}&limit=500`;\n let r: Response;\n try { r = await fetch(url, { headers: { Authorization: `Bearer ${tok}` }, signal: AbortSignal.timeout(20_000) }); }\n catch (e) { return { ok: false, why: `Meta API unreachable: ${String(e).slice(0, 150)}` }; }\n let body: any;\n try { body = await r.json(); } catch { return { ok: false, why: `Meta insights returned unparseable JSON (HTTP ${r.status})` }; }\n if (!r.ok) return { ok: false, why: `Meta insights error: ${String(body?.error?.message ?? `HTTP ${r.status}`).slice(0, 200)}` };\n const rows: MetaAdRow[] = (body?.data ?? []).map((d: any) => ({\n adId: String(d.ad_id ?? \"\"), adName: String(d.ad_name ?? \"\"), campaign: String(d.campaign_name ?? \"\"), spend: Number(d.spend) || 0,\n }));\n const truncated = typeof body?.paging?.next === \"string\" ? \"more ads exist past this page; spend is partial\" : undefined;\n return { ok: true, rows, truncated };\n}\n\nexport function toAdSpendMap(rows: MetaAdRow[]): Record {\n const m: Record = {};\n for (const r of rows) if (r.adId) m[r.adId] = { campaign: r.campaign, spend: (m[r.adId]?.spend ?? 0) + r.spend };\n return m;\n}\n",[333],"83ca8078-cab9-4f96-b5f5-89120b8838d2","cadence.ts","14aa659c-902f-11f1-8dc5-1607ee4eb77e",178,["D",1785930139649],"// HOW OFTEN DOES IT ACTUALLY RUN. v1.0, 4 Aug 2026.\n//\n// WHY THIS FILE EXISTS: the dashboard told Kim \"the follow-up system runs every 15 minutes\"\n// because a human typed that sentence, not because anything had measured it. A stranger reading\n// the page cold caught it in one pass: the same health row said \"last checked itself 26 minutes\n// ago\" and \"it runs every 15 minutes\", with a green tick beside both. The claim and the evidence\n// were contradicting each other on screen and the claim was winning.\n//\n// The scheduler's interval is not readable through any API (four candidate routes probed on\n// 4 Aug, all 404), so the only honest source of truth is the footprints each system leaves. The\n// engine now records the timestamp of every run; these functions read the gaps between them.\n// Nobody gets to type the cadence any more, which means nobody can get it wrong.\n\n/** Median minutes between consecutive runs, or null when the evidence is too thin to claim one. */\nexport function observedCadenceMin(history: unknown): number | null {\n const ts = (Array.isArray(history) ? history : [])\n .map((x) => Date.parse(String(x))).filter((n) => Number.isFinite(n)).sort((a, b) => a - b);\n if (ts.length < 3) return null;\n const gaps: number[] = [];\n for (let i = 1; i < ts.length; i++) {\n const g = (ts[i] - ts[i - 1]) / 60000;\n // A same-minute duplicate is a double write, not an interval. A multi-day hole is a deploy or\n // an outage, not an interval. Reading either as \"the rhythm\" would let one bad night convince\n // the page that a 15-minute system normally runs daily, and then nothing would ever look late.\n if (g >= 1 && g <= 24 * 60) gaps.push(g);\n }\n if (gaps.length < 2) return null;\n gaps.sort((a, b) => a - b);\n const mid = Math.floor(gaps.length / 2);\n return Math.round(gaps.length % 2 ? gaps[mid] : (gaps[mid - 1] + gaps[mid]) / 2);\n}\n\n/**\n * Late relative to the rhythm the system actually keeps, not to a number somebody hoped for.\n *\n * THREE states, not two, and the middle one is the point. A single missed turn on a system that\n * batches daily messages is not a business problem, so raising an alarm for it would train the\n * reader to ignore alarms, and the day one matters nobody looks. But printing a plain green tick\n * beside a visibly overdue timestamp is what the stranger test caught and refused to accept: the\n * reader could see the gap, and the page was pretending not to. So an overdue-but-not-alarming\n * system gets its own word. The reader is told it is behind, and told that being behind here is\n * ordinary. Nothing is hidden and nothing is dramatised.\n *\n * ok within half a cycle of schedule\n * due past due, one missed turn or so. Says so out loud. Not a fault, not a green tick either.\n * late two and a half cycles behind, floor 30 minutes. This one reaches the headline verdict.\n *\n * With no measured rhythm the thresholds are a flat 60 and 90 minutes, so \"we have not measured\n * it yet\" cannot quietly become infinite patience for a system that has genuinely stopped.\n */\nexport function lateness(ageMin: number | null, cadenceMin: number | null): {\n state: \"ok\" | \"due\" | \"late\" | \"unknown\"; dueAt: number | null; lateAt: number | null;\n} {\n if (ageMin == null) return { state: \"unknown\", dueAt: null, lateAt: null };\n const dueAt = cadenceMin ? cadenceMin * 1.5 : 60;\n const lateAt = cadenceMin ? Math.max(cadenceMin * 2.5, 30) : 90;\n const state = ageMin > lateAt ? \"late\" : ageMin > dueAt ? \"due\" : \"ok\";\n return { state, dueAt, lateAt };\n}\n/** Does this state deserve a tick? Only a system on schedule does. */\nexport const isHealthy = (s: ReturnType[\"state\"]) => s === \"ok\";\n\n/**\n * Append this run's stamp to the trail a system leaves behind, given whatever the previous blob\n * held. Lives here rather than in the engine because main.ts sits against a hard 80,000-character\n * ceiling on the platform, and because the writer and the reader of this trail should agree on its\n * shape by sharing one definition instead of two that drift.\n *\n * Seeds from a pre-history state's own `ts` so the very next run already yields one real gap\n * rather than starting the evidence from nothing. Never appends a duplicate of the last stamp.\n */\nexport const RUN_HISTORY_MAX = 40;\nexport function appendRunStamp(prev: any, ts: string): string[] {\n let h: string[] = Array.isArray(prev?.history) ? prev.history.filter((x: unknown) => typeof x === \"string\") : [];\n if (!h.length && typeof prev?.ts === \"string\") h = [prev.ts];\n if (h[h.length - 1] !== ts) h.push(ts);\n return h.slice(-RUN_HISTORY_MAX);\n}\n\n/**\n * One sentence for the reader, combining the verdict and the yardstick it was measured against.\n *\n * The previous version printed those two separately and produced a flat contradiction that a\n * reader caught at once: \"Its next look is a little overdue\" immediately followed by \"There is not\n * enough history yet to say how often it normally runs.\" You cannot call a thing late and in the\n * same breath say you do not know when it was due. Both sentences were individually true, because\n * an unmeasured system still falls back to a flat one-hour expectation, but nothing on the page\n * said so. Now the yardstick is never separated from the judgement that used it.\n */\nexport function lateSentence(l: ReturnType, cadenceMin: number | null): string {\n const rhythm = cadenceMin == null\n ? \"We have not watched it long enough to know its usual rhythm, so for now we expect it at least once an hour\"\n : `Left to itself it runs about every ${cadenceMin} minute${cadenceMin === 1 ? \"\" : \"s\"}`;\n if (l.state === \"unknown\") return `${rhythm}, and there is no check-in on record to compare against.`;\n if (l.state === \"late\") return `${rhythm}, and it is well past that. If it is still behind in an hour, tell Amir.`;\n if (l.state === \"due\") return `${rhythm}, and it is a little past that now. One late turn is ordinary; several in a row is not.`;\n return `${rhythm}, and it is on time.`;\n}\n/**\n * The sentence for a system that is supposed to run on a schedule and, as far as anything can\n * tell, is not. Kept separate from lateSentence because \"it is a bit late\" and \"it has never\n * started on its own\" are different facts and must not share a phrasing.\n *\n * WHY THIS EXISTS. The watchdog reported a rhythm of \"about every 95 minutes\". That number was\n * computed from its run stamps, honestly, and it was still wrong: nearly every stamp was a human\n * pressing the check-now button. The page was describing my own button presses back to Kim as the\n * watchdog's schedule.\n *\n * IT MUST NOT GUESS WHY.\n * [was: \"Nothing has started it on its own, which means its timer is not firing.\" First half an\n * observation, second half a conclusion, and the conclusion was wrong. I opened the schedule on\n * 5 August and found it set to once every 24 hours, deliberately, a week earlier. The timer was\n * firing perfectly. It was just slower than the window I had been watching, and everything else\n * in the history was a person. I had already written \"the timer has never fired\" into a message\n * and onto Kim's page before I looked. An empty record of scheduled runs means exactly that:\n * report the gap, and let somebody open the settings.]\n *\n * `sinceIso` is when the system started telling scheduled runs apart from manual ones. Saying so\n * matters: an empty record since this morning is not the same claim as \"it has never run\".\n */\nexport function neverRanItselfSentence(sinceIso: string | null, manualCount: number): string {\n const since = sinceIso\n ? `Since ${new Date(sinceIso).toLocaleDateString(\"en-US\", { month: \"long\", day: \"numeric\" })} this system has recorded which of its checks were scheduled and which were started by hand.`\n : \"This system now records which of its checks were scheduled and which were started by hand.\";\n const manual = manualCount > 1\n ? ` ${manualCount} checks have run since then, every one started by hand.`\n : manualCount === 1\n ? \" One check has run since then, and it was started by hand.\"\n : \" Nothing has run since then either way.\";\n return `${since}${manual} Nothing on a schedule has been recorded in that time. Everything it checks is still being checked, because Amir has been running it by hand, but we cannot yet show you it keeping its own time. Nothing else on this page is affected either way.`;\n}\n\n/** Kept for callers that only want the yardstick. */\nexport function cadenceSentence(cadenceMin: number | null): string {\n return cadenceMin == null\n ? \"There is not enough history yet to say how often it normally runs.\"\n : `Left to itself it runs about every ${cadenceMin} minute${cadenceMin === 1 ? \"\" : \"s\"}.`;\n}\n",[340],"ca08c72e-c9f1-44bc-89b4-4fd671499306","api.ts",687,["D",1786388051927],12,"// NURTURE CONTROL PANEL, HTTP face of the puppy-path engine. Built 2 Aug 2026.\n//\n// WHY THIS FILE EXISTS\n// The engine (main.ts) keeps everything it knows in val.town blobs. Blobs are reachable only with a\n// blob-scoped API token, which means the only people who could see whether the nurture system was\n// working were people holding a production credential. That is the wrong shape for this client: Kim\n// cancelled her previous supplier for going quiet, and a system whose status is invisible to her is\n// the same failure wearing different clothes.\n//\n// So the engine gets a front door. One URL, one key, no login, no install. It answers three\n// questions in plain language, who is in the system, what happened today, is anything broken, and\n// carries the one control she must always have: STOP.\n//\n// WHAT IT IS NOT\n// Read-mostly by design. The only state it writes is the kill switch. It cannot enrol anyone, send\n// anything, or edit copy. A leaked link is an information disclosure, not a way to message her\n// customers.\n//\n// AUTH\n// ?k=. Constant-time-ish compare, no key echoed back, no data before the check,\n// and the 401 body is byte-identical whether the key is absent or wrong.\n//\n// ROUTES (all GET, all query-param, so a phone bookmark works)\n// ?k=… the dashboard\n// ?k=…&f=json the same numbers as JSON\n// ?k=…&stop=1 kill switch ON , engine halts before it looks at a single contact\n// ?k=…&go=1 kill switch OFF\n//\n// COLOUR\n// Stage colours are a validated 4-step single-hue ordinal ramp (#86b6ef → #3987e5 → #256abf →\n// #184f95); status colours are the reserved good/warning/critical steps and always ship with a word\n// beside them, never colour alone. Both ramps were run through the palette validator in light and\n// dark before this file was written: ordinal ramp ALL CHECKS PASS in both modes.\n\n// ---- auth ------------------------------------------------------------------------------------\n// v2 (2 Aug, after the adversarial pass): the key is NOT in this file. val.town vals are PUBLIC -\n// proved by fetching this very source with no token, so a literal key here was readable by anyone\n// who found the val, which meant anyone could read Kim's data, stop her system, or trigger a run.\n// Only the SHA-256 digest lives in source now. The digest is useless to a reader and sufficient for\n// a comparison, so publishing the code no longer publishes the secret.\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\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 override = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\");\n const expected = override || KEY_SHA256;\n const got = await sha256Hex(k);\n // Constant-time over equal-length hex digests.\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\n\n// v1.7.1, VIEW-ONLY access. The admin link is also the stop-button link, so anyone Kim forwards\n// it to could halt her follow-up. The view key is DERIVED from the admin digest (deterministic, no\n// second secret to store): it renders the same page minus the stop controls and the JSON/selftest\n// modes. Give Kim and staff the view link; the admin link stays with whoever may press stop.\nasync function viewKey(): Promise {\n // v1.7.2 (review fix), derived from the GHL token (a real secret in env/private blob), not\n // from the admin DIGEST that anyone can read in this public source. Rotating the CRM token\n // rotates the view links, which is the right coupling anyway.\n const tok = Deno.env.get(\"GHL_TOKEN\") || ((await get(\"puppy_config\", null))?.ghlToken ?? \"\");\n if (!tok) return \"tds_view_disabled_no_token_available_x\";\n return \"tds_view_\" + (await sha256Hex(tok + \":view\")).slice(0, 32);\n}\nasync function viewAuthorised(k: string): Promise {\n const expected = await viewKey();\n if (k.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < k.length; i++) d |= k.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\nconst KILL_BLOB = \"nurture_kill\";\nconst BUSINESS_TZ = \"America/New_York\";\n\nasync function blobMod() {\n return (await import(\"https://esm.town/v/std/blob\")).blob;\n}\nasync function get(key: string, fallback: any = null) {\n try {\n const blob = await blobMod();\n const v = await blob.getJSON(key);\n return v ?? fallback;\n } catch {\n return fallback;\n }\n}\n\n\n// Plain-English names for the engine's internal statuses. Kim never sees a snake_case token.\nconst STATUS_LABEL: Record = {\n main: \"In the main sequence\",\n awaiting_appt_outcome: \"Booked, waiting on the Pup Talk\",\n branch_a: \"Missed the Pup Talk, being rebooked\",\n branch_b: \"Had the Pup Talk, hasn't bought yet\",\n slow_track: \"On the slow track, an occasional helpful message\",\n paused_reply: \"Paused, they replied, a human has it\",\n done_booked: \"Booked a Pup Talk\",\n done_customer: \"Became a customer\",\n done_hard_exit: \"Stopped, opted out or disqualified\",\n done_soft_21d: \"Finished the sequence\",\n done_branch_complete: \"Finished the follow-up\",\n};\nconst ACTIVE = [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"];\nconst WON = [\"done_booked\", \"done_customer\"];\n\nfunction esc(s: unknown) {\n return String(s ?? \"\").replace(/[&<>\"']/g, (c) =>\n ({ \"&\": \"&\", \"<\": \"<\", \">\": \">\", '\"': \""\", \"'\": \"'\" }[c] as string)\n );\n}\n\nfunction todayInBusinessTz(): string {\n // en-CA gives YYYY-MM-DD, which is what the journal timestamps slice to.\n return new Intl.DateTimeFormat(\"en-CA\", { timeZone: BUSINESS_TZ }).format(new Date());\n}\n\nasync function collect() {\n const [state, summary, run, journal, lastError, kill] = await Promise.all([\n get(\"puppy_state\", {}),\n get(\"puppy_summary\", null),\n get(\"puppy_run_state\", null),\n get(\"puppy_journal\", []),\n get(\"puppy_last_error\", null),\n get(KILL_BLOB, null),\n ]);\n const wd = await get(\"wd_public\", null); // v1.5, independent watchdog headline\n\n const rows: any[] = Object.entries(state || {}).map(([id, s]: any) => ({ id, ...(s || {}) }));\n const byStatus: Record = {};\n for (const r of rows) byStatus[r.status || \"unknown\"] = (byStatus[r.status || \"unknown\"] || 0) + 1;\n\n const j: any[] = Array.isArray(journal) ? journal : [];\n const today = todayInBusinessTz();\n const todays = j.filter((r) => String(r.ts || \"\").slice(0, 10) === today);\n\n const sentToday = todays.filter((r) => r.event === \"sent\" && !r.test).length;\n const testSentToday = todays.filter((r) => r.event === \"sent\" && r.test).length;\n // v2 fix (adversarial pass): this matched \"failed\"/\"error\" exactly, but the engine journals\n // \"send_failed\", so the error tile could never leave zero and \"RUNNING, with errors today\" was\n // an unreachable state. A dashboard whose alarm cannot fire is worse than no dashboard, because it\n // is actively reassuring. Match any failure-shaped event instead.\n const failedToday = todays.filter((r) => /fail|error/i.test(String(r.event ?? \"\"))).length;\n\n const active = ACTIVE.reduce((n, k) => n + (byStatus[k] || 0), 0);\n const won = WON.reduce((n, k) => n + (byStatus[k] || 0), 0);\n const paused = byStatus[\"paused_reply\"] || 0;\n\n // Staleness is the alarm that matters most: a scheduler that stops firing is exactly the silent\n // failure this client cancels contracts over. 60 min = four missed 15-minute ticks.\n const lastRunTs = run?.ts || null;\n const ageMin = lastRunTs ? Math.floor((Date.now() - new Date(lastRunTs).getTime()) / 60000) : null;\n const stale = ageMin === null || ageMin > 60;\n\n return {\n generatedAt: new Date().toISOString(),\n run: run ?? null,\n contacts: rows.map((r) => ({\n id: r.id,\n status: r.status,\n label: STATUS_LABEL[r.status] || r.status,\n enteredAt: r.enteredAt ?? null,\n lastMainStepSent: r.lastMainStepSent ?? null,\n lastSentAt: r.lastSentAt ?? null,\n })),\n killed: !!kill?.stopped,\n killedAt: kill?.at ?? null,\n testMode: run?.testMode ?? null,\n engineVersion: run?.v ?? null,\n lastRunTs,\n lastRunAgeMin: ageMin,\n stale,\n counts: { total: rows.length, active, won, paused, sentToday, testSentToday, failedToday },\n byStatus,\n lastError: lastError ?? null,\n recent: j.slice(-40).reverse(),\n summary: summary ?? null,\n watchdog: wd ?? null,\n };\n}\n\n// ---- rendering ------------------------------------------------------------------------------------\n\nconst RAMP = [\"#86b6ef\", \"#3987e5\", \"#256abf\", \"#184f95\", \"#0f3a6e\"]; // validated ordinal, light+dark\nconst GOOD = \"#0ca30c\", WARN = \"#fab219\", CRIT = \"#d03b3b\";\n\nfunction tile(label: string, value: string | number, note: string, accent?: string) {\n return `
\n
${esc(value)}
\n
${esc(label)}
\n
${esc(note)}
\n
`;\n}\n\nfunction stageBar(byStatus: Record, total: number) {\n const order = [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"];\n const segs = order\n .map((k, i) => ({ k, n: byStatus[k] || 0, c: RAMP[i] }))\n .filter((s) => s.n > 0);\n const sum = segs.reduce((a, s) => a + s.n, 0);\n if (!sum) {\n return `
Nobody is in a sequence right now. That is expected until the first contact is tagged.
`;\n }\n const bar = segs\n .map((s) => ``)\n .join(\"\");\n const legend = segs\n .map((s) => `
${esc(STATUS_LABEL[s.k])}${s.n}
`)\n .join(\"\");\n return `
${bar}
${legend}
\n \n \n ${segs.map((s) => ``).join(\"\")}\n
The same numbers as a table
Stage People
${esc(STATUS_LABEL[s.k])} ${s.n}
Total in a sequence ${sum}
`;\n}\n\nfunction page(d: any, k: string, opts: { readonly?: boolean } = {}) {\n const c = d.counts;\n const health = d.killed\n ? { c: CRIT, icon: \"■\", t: \"STOPPED\", m: `You stopped the system${d.killedAt ? \" on \" + esc(String(d.killedAt).slice(0, 16).replace(\"T\", \" at \")) : \"\"}. Nothing is being sent.` }\n : d.stale\n ? { c: CRIT, icon: \"⚠\", t: \"NOT RUNNING\", m: d.lastRunTs ? `The last check was ${d.lastRunAgeMin} minutes ago. It should run every 15. Tell Amir.` : \"This has never recorded a run. Tell Amir.\" }\n : c.failedToday > 0\n ? { c: WARN, icon: \"⚠\", t: \"RUNNING, with errors today\", m: `${c.failedToday} message(s) failed today. Details are at the bottom of this page.` }\n : { c: GOOD, icon: \"✓\", t: \"RUNNING NORMALLY\", m: `Last check: ${d.lastRunAgeMin === 1 ? \"1 minute\" : d.lastRunAgeMin + \" minutes\"} ago. It checks about once an hour around the clock, and messages only ever go out between 9am and 7pm Georgia time.` };\n\n const mode = d.testMode === true\n ? `
PRACTICE MODE: the system is doing everything except actually sending to your customers. Practice messages go to a dead-end test contact that cannot receive anything, so if you test it yourself you'll get silence, that's the point of practice mode. Keep handling new calls and messages the way you do today; it takes over only when you say the word and this banner turns LIVE.
`\n : d.testMode === false\n ? `
LIVE: real messages are going to real people.
`\n : `
MODE UNKNOWN: no run has reported yet.
`;\n\n // v1.7, Kim's own question (\"how does she know what needs doing today?\") answered on the page\n // itself, permanently. One plain sentence, computed from the same numbers as the tiles.\n const todayMsg = d.killed\n ? \"The system is stopped. Nothing will happen until someone presses Start below.\"\n : c.failedToday > 0\n ? `Look at the problems listed at the bottom of this page, ${c.failedToday} message(s) failed today.`\n : c.paused > 0\n ? `${c.paused === 1 ? \"One person\" : c.paused + \" people\"} replied and ${c.paused === 1 ? \"is\" : \"are\"} waiting on a human. Open Conversations and answer ${c.paused === 1 ? \"them\" : \"each one\"}, that is today's work.`\n : \"Nothing. If the banner above is green and Paused says 0, you can close this page.\";\n const today = `
What needs doing today
${todayMsg}
`;\n\n // Journal rows carry engine-internal names (sent main#3); translate to the words the PDFs use.\n const pretty = (s: string) =>\n s.replace(/\\bmain#(\\d+)/g, \"Touch $1 of the first 21 days\")\n .replace(/\\bslow#(\\d+)/g, \"Slow track message $1\")\n .replace(/\\bbranch_a#(\\d+)/g, \"rebooking note $1\")\n .replace(/\\bbranch_b#(\\d+)/g, \"after-the-call note $1\");\n const EVENT_LABEL: Record = {\n sent: \"message sent\", enrolled: \"joined the sequence\", pause_reply: \"paused, they replied\",\n soft_exit_21d: \"finished the 21 days, moved to slow track\", advance_status: \"moved forward\",\n send_failed: \"message FAILED\", skip_step_channel_optout: \"step skipped, opted out of that channel\",\n branch_complete: \"follow-up finished\", pruned: \"archived\", pause_timeout: \"waited too long, needs a person\",\n enroll_refused: \"not enrolled\", sequence_drift: \"copy changed underneath, check\", contact_failed: \"check FAILED\",\n };\n const rows = (d.recent || [])\n .map((r: any) => `${esc(String(r.ts || \"\").slice(0, 16).replace(\"T\", \" \"))}${esc(EVENT_LABEL[r.event] || r.event)}${r.test ? ' practice' : \"\"}${esc(pretty(String(r.detail || \"\")))}`)\n .join(\"\") || `Nothing recorded yet.`;\n\n return `\n\nThe Dogs Spot, Nurture Control Panel\n
\n
The Dogs Spot, Nurture Control Panel
\n
Everything the follow-up system is doing, on one page. The numbers are read fresh every time this page opens, refresh for the latest.
\n\n
\n
${health.icon}
\n
${health.t}
${health.m}
\n
${mode}
\n\n${today}\n\n${d.watchdog ? `
${esc(d.watchdog.headline)} ●
` : \"\"}\n\n
Right now
\n
\n${tile(\"People being followed up\", c.active, d.testMode === true ? \"right now that is the test dummy, not a real customer\" : \"in a sequence right now\")}\n${tile(\"Booked or became a customer\", c.won, \"the whole point of the system\", c.won > 0 ? GOOD : undefined)}\n${tile(\"Paused: someone replied\", c.paused, \"answer them in the Conversations inbox; the system stays out of it\", c.paused > 0 ? WARN : undefined)}\n${tile(\"Messages sent today\", c.sentToday, c.testSentToday ? `plus ${c.testSentToday} practice` : \"to real people\")}\n${tile(\"Problems today\", c.failedToday, c.failedToday ? \"see the bottom of this page\" : \"none\", c.failedToday ? CRIT : GOOD)}\n
\n\n
Where those people are
${stageBar(d.byStatus || {}, c.total)}${!(d.byStatus || {})[\"slow_track\"] ? `
The slow track (the occasional messages that follow the first 21 days) will appear here once the first person finishes their three weeks. Their first slow-track message goes out a week after that, on day 28.
` : \"\"}
\n\n${opts.readonly ? `
This page is view-only. The stop switch is on the owner's link.
` : `
Stop everything
\n
This halts the follow-up system before it looks at a single person. It takes effect on the next check, which is within the hour, and needs no one's help. Nothing is deleted, everyone keeps their place and picks up where they left off when you start it again. (When it is stopped, a green Start button appears right here.) To take one single person off every track instead: open their contact in GoHighLevel and switch on Do Not Disturb, the system honors that on its next check, within the hour, permanently.
\n${d.killed\n ? ``\n : ``}\n
`}\n\n
${(d.recent || []).length < 40 ? \"Everything it has done so far\" : \"The last 40 things it did\"}
\n${rows}
When What Detail
\n\n${d.lastError && d.lastError.at && Date.now() - new Date(d.lastError.at).getTime() < 24 * 3600 * 1000 ? `
Something went wrong in the last 24 hours
Technical details for whoever fixes it, if this box is showing, tell Amir and include what is below.
${esc(JSON.stringify(d.lastError).slice(0, 1200))}
` : \"\"}\n\n
System version ${esc(d.engineVersion || \"?\")} · numbers read fresh when this page opened
\n
`;\n}\n\n// ---- live self-test ------------------------------------------------------------------------------\n// Resolves the CRM credential exactly the way the engine does (env var first, then the puppy_config\n// blob) and pings the four endpoints the engine depends on. Reports status codes only, the token is\n// never returned, logged, or echoed. This exists because a stale credential is the failure mode that\n// looks identical to \"quiet\": the scheduler keeps ticking, every read fails, and nothing tells anyone.\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\n\nasync function resolveEngineToken(): Promise<{ token?: string; from: string }> {\n const env = Deno.env.get(\"GHL_TOKEN\");\n if (env) return { token: env, from: \"env GHL_TOKEN\" };\n const cfg = await get(\"puppy_config\", null);\n if (cfg?.ghlToken) return { token: cfg.ghlToken, from: \"puppy_config blob\" };\n return { from: \"NOT FOUND\" };\n}\n\nasync function selfTest() {\n const { token, from } = await resolveEngineToken();\n const checks: any[] = [];\n const probe = async (name: string, url: string, ver: string, why: string) => {\n if (!token) return checks.push({ name, status: null, ok: false, why, note: \"no credential resolved\" });\n try {\n const r = await fetch(url, { headers: { Authorization: `Bearer ${token}`, Version: ver, Accept: \"application/json\" } });\n checks.push({ name, status: r.status, ok: r.status === 200, why });\n } catch (e) {\n checks.push({ name, status: null, ok: false, why, note: String(e).slice(0, 120) });\n }\n };\n await probe(\"read calendar bookings\", `${GHL}/calendars/events?locationId=${LOC}&calendarId=qHuYJ0NEqzibnoqf5Cw3&startTime=${Date.now() - 864e5}&endTime=${Date.now()}`, \"2021-04-15\", \"how it notices someone booked a Pup Talk\");\n await probe(\"read replies\", `${GHL}/conversations/search?locationId=${LOC}&limit=1`, \"2021-04-15\", \"how it pauses when someone writes back\");\n await probe(\"read contacts\", `${GHL}/contacts/?locationId=${LOC}&limit=1`, \"2021-07-28\", \"how it reads names and dog names\");\n await probe(\"read deals\", `${GHL}/opportunities/pipelines?locationId=${LOC}`, \"2021-07-28\", \"how it notices someone became a customer\");\n return { credentialFrom: from, allOk: checks.every((c) => c.ok), checks };\n}\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n const k = url.searchParams.get(\"k\") || \"\";\n const isAdmin = await authorised(k);\n const isViewer = !isAdmin && (await viewAuthorised(k));\n if (!isAdmin && !isViewer) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n if (isViewer) {\n // view key renders the dashboard only, no stop/go, no JSON, no selftest.\n const d = await collect();\n return new Response(page(d, k, { readonly: true }), {\n headers: { \"content-type\": \"text/html; charset=utf-8\", \"cache-control\": \"no-store\" },\n });\n }\n\n if (url.searchParams.get(\"selftest\") === \"1\") {\n return new Response(JSON.stringify(await selfTest(), null, 2), {\n headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" },\n });\n }\n\n if (url.searchParams.get(\"stop\") === \"1\") {\n const blob = await blobMod();\n await blob.setJSON(KILL_BLOB, { stopped: true, at: new Date().toISOString(), by: \"control-panel\" });\n return Response.redirect(`${url.origin}${url.pathname}?k=${encodeURIComponent(k)}`, 303);\n }\n if (url.searchParams.get(\"go\") === \"1\") {\n const blob = await blobMod();\n await blob.setJSON(KILL_BLOB, { stopped: false, at: new Date().toISOString(), by: \"control-panel\" });\n return Response.redirect(`${url.origin}${url.pathname}?k=${encodeURIComponent(k)}`, 303);\n }\n\n const d = await collect();\n if (url.searchParams.get(\"f\") === \"json\") {\n return new Response(JSON.stringify(d, null, 2), {\n headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" },\n });\n }\n return new Response(page(d, k), {\n headers: { \"content-type\": \"text/html; charset=utf-8\", \"cache-control\": \"no-store\" },\n });\n}\n",[347],"51bc55ba-f13d-4265-8a6f-81e07f6b53cf","aged.ts","58225aaa-8e77-11f1-90c9-1607ee4eb77e",15,["D",1785678976395],"// AGED-LIST SEGMENTER AND RELEASE PLANNER — built 2 Aug 2026.\n//\n// WHY THIS EXISTS\n// The plan of record was \"release the 3,206 dormant New Lead contacts by email, a few hundred a\n// week.\" Before building the machine, the audience was measured. It does not exist in the shape the\n// plan assumed:\n//\n// 3,426 opportunities sit in New Lead (not 3,206 — it grows ~12/day)\n// 177 (5.2%) have an email address\n// 766 (22.4%) have a phone number\n// 2,655 (77.5%) have NEITHER — they are Messenger-only contacts and cannot be emailed or texted\n//\n// Verified twice: once from the opportunity payload's embedded contact, then again by re-fetching\n// 25 of the \"no email\" contacts individually with GET /contacts/{id} — 0 of 25 had a hidden email.\n// So the email-only launch reaches 177 people, not three thousand.\n//\n// Age was also assumed wrong. Nothing in the backlog is older than 292 days; the oldest month is\n// October 2025 and only 328 rows are from 2025 at all. Median age is 109 days.\n//\n// This endpoint keeps that truth live rather than frozen in a document: it re-measures on demand,\n// segments the backlog by what can actually be done with each person, and produces the batch plan.\n//\n// WHAT IT WILL NOT DO\n// It never sends. It plans. Releasing anyone is a separate, deliberate act by a human, and the\n// copy for this path has not been approved by the client. `?k=…&plan=1` returns the batch list;\n// there is no endpoint here that hands that list to a sender.\n//\n// QUOTA (this is the R19 fix in miniature)\n// A full walk is 35 paginated calls. That is far too much to do on every 15-minute engine tick, so\n// the result is cached in the `aged_segments` blob with a timestamp and only recomputed when asked\n// or when older than CACHE_TTL. The engine never calls this; it is an operator tool.\n//\n// ?k= segment summary (cached)\n// ?k=&fresh=1 force a re-measure from the live CRM\n// ?k=&plan=1 the batch release plan\n// ?k=&f=json raw JSON of whichever of the above applies\n\n// ---- auth ------------------------------------------------------------------------------------\n// v2 (2 Aug, after the adversarial pass): the key is NOT in this file. val.town vals are PUBLIC —\n// proved by fetching this very source with no token — so a literal key here was readable by anyone\n// who found the val, which meant anyone could read Kim's data, stop her system, or trigger a run.\n// Only the SHA-256 digest lives in source now. The digest is useless to a reader and sufficient for\n// a comparison, so publishing the code no longer publishes the secret.\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\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 override = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\");\n const expected = override || KEY_SHA256;\n const got = await sha256Hex(k);\n // Constant-time over equal-length hex digests.\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\nconst PIPE = \"FXt1UpCVBufbF0v3pfyf\";\nconst NEW_LEAD = \"ccb18375-9aa1-40aa-a071-1581ca739533\";\nconst CACHE_KEY = \"aged_segments\";\nconst CACHE_TTL_MS = 12 * 3600 * 1000;\n\n// Batch policy. Email first, small, watching between batches — a burst to a stale list is how a\n// sending reputation dies, and this list is stale by construction.\nconst BATCH_SIZE = 60;\nconst BATCHES_PER_WEEK = 1;\n\nasync function blobMod() { return (await import(\"https://esm.town/v/std/blob\")).blob; }\n\n\nasync function token(): Promise {\n const env = Deno.env.get(\"GHL_TOKEN\");\n if (env) return env;\n const blob = await blobMod();\n const cfg = await blob.getJSON(\"puppy_config\").catch(() => null);\n return cfg?.ghlToken;\n}\n\nasync function walkNewLead() {\n const t = await token();\n if (!t) throw new Error(\"no CRM credential resolved\");\n const rows: any[] = [];\n let after: any = null, afterId: any = null, pages = 0;\n while (pages < 45) {\n let u = `${GHL}/opportunities/search?location_id=${LOC}&pipeline_id=${PIPE}&pipeline_stage_id=${NEW_LEAD}&limit=100`;\n if (after != null) u += `&startAfter=${after}&startAfterId=${afterId}`;\n const r = await fetch(u, { headers: { Authorization: `Bearer ${t}`, Version: \"2021-07-28\", Accept: \"application/json\" } });\n if (!r.ok) throw new Error(`opportunities/search ${r.status}`);\n const d = await r.json();\n const ops = d.opportunities ?? [];\n if (!ops.length) break;\n rows.push(...ops);\n pages++;\n after = d.meta?.startAfter; afterId = d.meta?.startAfterId;\n if (!after) break;\n }\n return { rows, pages };\n}\n\n// A lead nobody can reach is not a lead. A lead who only ever spoke on Messenger cannot be emailed or\n// texted at all — Meta's 24-hour messaging window closes that door, and pretending otherwise is how a\n// nurture plan produces a number that never arrives.\nfunction segment(rows: any[]) {\n const now = Date.now();\n const seg: Record = { emailable: [], phoneOnly: [], unreachable: [], excluded: [] };\n const ageBuckets: Record = { \"0-30d\": 0, \"31-90d\": 0, \"91-180d\": 0, \"181-365d\": 0, \"365d+\": 0 };\n const years: Record = {};\n const seenEmail = new Set(), seenPhone = new Set();\n let dupes = 0;\n\n for (const o of rows) {\n const c = o.contact ?? {};\n const email = String(c.email ?? \"\").trim().toLowerCase();\n const phone = String(c.phone ?? \"\").trim();\n const tags: string[] = (c.tags ?? []).map((x: string) => String(x).toLowerCase());\n const created = o.createdAt ? new Date(o.createdAt).getTime() : null;\n const ageDays = created ? Math.floor((now - created) / 86400000) : null;\n\n if (created) {\n const y = new Date(created).getUTCFullYear();\n years[y] = (years[y] ?? 0) + 1;\n const a = ageDays!;\n ageBuckets[a <= 30 ? \"0-30d\" : a <= 90 ? \"31-90d\" : a <= 180 ? \"91-180d\" : a <= 365 ? \"181-365d\" : \"365d+\"]++;\n }\n\n const rec = { contactId: o.contactId, name: c.name ?? null, email: email || null, phone: phone || null, ageDays, tags };\n\n // Exclusions come first and are absolute.\n const isSpam = tags.some((t) => t.includes(\"spam\"));\n const isCustomer = tags.includes(\"customer\") || tags.includes(\"subscription_active\");\n const alreadyOnAPath = tags.some((t) => t.startsWith(\"puppy-path\") || t.startsWith(\"path-\") || t.includes(\"nurture\"));\n if (isSpam || isCustomer || alreadyOnAPath) { seg.excluded.push({ ...rec, why: isSpam ? \"flagged spam\" : isCustomer ? \"already a customer\" : \"already on a nurture path\" }); continue; }\n\n // Same person twice is one person. Dedupe on the strongest identifier available.\n const k = email || phone;\n if (k) {\n const set = email ? seenEmail : seenPhone;\n if (set.has(k)) { dupes++; seg.excluded.push({ ...rec, why: \"duplicate of an earlier row\" }); continue; }\n set.add(k);\n }\n\n if (email) seg.emailable.push(rec);\n else if (phone) seg.phoneOnly.push(rec);\n else seg.unreachable.push(rec);\n }\n\n // Oldest first: they have waited longest and are the least likely to remember enquiring, so they\n // are also the batch most worth watching the opt-out rate on.\n seg.emailable.sort((a, b) => (b.ageDays ?? 0) - (a.ageDays ?? 0));\n seg.phoneOnly.sort((a, b) => (b.ageDays ?? 0) - (a.ageDays ?? 0));\n\n return { seg, ageBuckets, years, dupes };\n}\n\nfunction plan(emailable: any[]) {\n const batches: any[] = [];\n for (let i = 0; i < emailable.length; i += BATCH_SIZE) {\n batches.push({\n batch: batches.length + 1,\n weekOffset: batches.length * (1 / BATCHES_PER_WEEK),\n size: emailable.slice(i, i + BATCH_SIZE).length,\n oldestAgeDays: emailable[i]?.ageDays ?? null,\n contactIds: emailable.slice(i, i + BATCH_SIZE).map((r) => r.contactId),\n });\n }\n return batches;\n}\n\nasync function measure(fresh: boolean) {\n const blob = await blobMod();\n if (!fresh) {\n const cached = await blob.getJSON(CACHE_KEY).catch(() => null);\n if (cached?.at && Date.now() - new Date(cached.at).getTime() < CACHE_TTL_MS) return { ...cached, fromCache: true };\n }\n const { rows, pages } = await walkNewLead();\n const { seg, ageBuckets, years, dupes } = segment(rows);\n const out = {\n at: new Date().toISOString(),\n fromCache: false,\n apiCallsUsed: pages,\n total: rows.length,\n counts: {\n emailable: seg.emailable.length,\n phoneOnly: seg.phoneOnly.length,\n unreachable: seg.unreachable.length,\n excluded: seg.excluded.length,\n duplicatesRemoved: dupes,\n },\n ageBuckets, years,\n batchPolicy: { size: BATCH_SIZE, perWeek: BATCHES_PER_WEEK, channel: \"email only\" },\n weeksToClear: Math.ceil(seg.emailable.length / (BATCH_SIZE * BATCHES_PER_WEEK)),\n emailable: seg.emailable,\n phoneOnly: seg.phoneOnly.slice(0, 200),\n excludedSample: seg.excluded.slice(0, 50),\n };\n await blob.setJSON(CACHE_KEY, out).catch(() => {});\n return out;\n}\n\nfunction pct(n: number, d: number) { return d ? `${((n / d) * 100).toFixed(1)}%` : \"0%\"; }\n\nfunction html(d: any) {\n const c = d.counts;\n const rows = (d.batches ?? []).slice(0, 12).map((b: any) =>\n `${b.batch}week +${b.weekOffset}${b.size}${b.oldestAgeDays ?? \"—\"} days`).join(\"\");\n return `Aged list — what is actually there\n\n
The dormant list — what is actually in it
\n
Measured from the live CRM ${d.fromCache ? \"(cached \" + String(d.at).slice(0, 16).replace(\"T\", \" \") + \" UTC)\" : \"just now\"} · ${d.apiCallsUsed ?? \"—\"} API calls
\n
The plan assumed roughly 3,200 people who could be emailed. They cannot.\nOf ${d.total} contacts sitting in New Lead, ${c.emailable} have an email address —\n${pct(c.emailable, d.total)}. ${c.unreachable} (${pct(c.unreachable, d.total)}) have neither an email\nnor a phone number: they only ever spoke through Messenger, and Meta's 24-hour rule closes that door.
\n
Who can actually be contacted
\n\n\n\n\n
Segment Count Share What can be done
Has an email ${c.emailable} ${pct(c.emailable, d.total)} The email release. This is the real audience.
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.
\n
How old it really is
\n${Object.entries(d.ageBuckets || {}).map(([k, v]) => ``).join(\"\")}
Age Count
${k} ${v}
\n
By year created: ${Object.entries(d.years || {}).map(([k, v]) => `${k} ${v}`).join(\" · \")}. Nothing in this list is more than a year old.
\n${rows ? `
The release plan
${rows}
Batch When People Oldest in batch
\n
${d.batchPolicy.size} per batch, ${d.batchPolicy.perWeek} batch per week, email only, oldest first — ${d.weeksToClear} week(s) to work through everyone who can be reached.
` : \"\"}\n
Nothing here sends anything. This page measures and plans. Releasing a batch is a separate deliberate action, and the copy for this path has not been approved yet.
`;\n}\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n if (!(await authorised(url.searchParams.get(\"k\") || \"\"))) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n try {\n const d: any = await measure(url.searchParams.get(\"fresh\") === \"1\");\n if (url.searchParams.get(\"plan\") === \"1\") d.batches = plan(d.emailable ?? []);\n if (url.searchParams.get(\"f\") === \"json\") {\n return new Response(JSON.stringify(d, null, 2), { headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" } });\n }\n if (!d.batches) d.batches = plan(d.emailable ?? []);\n return new Response(html(d), { headers: { \"content-type\": \"text/html; charset=utf-8\", \"cache-control\": \"no-store\" } });\n } catch (e) {\n return new Response(JSON.stringify({ error: String(e).slice(0, 500) }, null, 2), { status: 500, headers: { \"content-type\": \"application/json\" } });\n }\n}\n",[354],"9819cd9e-a633-4046-96bb-ff64f836f9d8","SOURCE-BUNDLE.part9.txt","5cc7c38a-91cc-11f1-86f1-1607ee4eb77e",686,["D",1786387549422],29,"THE DOGS SPOT — SOURCE BUNDLE (part 9 of 17)\n\nEverything in this project that does not already live on val.town. The engine is NOT here:\nthe engine files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff (23 of them on 9 Aug 2026; list the val,\ndo not assume) are verified file by file by\nscripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\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/deploy.mjs --check (pulls nothing, proves the val matches)\n node scripts/build.mjs (needs engine/ back from the val first)\n node tests/run-all.mjs\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (8 of 61 files)\n tests/run-all.mjs 16104 bytes b067deb1fc22\n tests/slow-track.test.mjs 9404 bytes 0bc57258b304\n tests/sms-length.test.mjs 2793 bytes 4b42ded930a4\n tests/stories.test.mjs 3378 bytes 36c5afe09c12\n tests/taper-test.ts 6922 bytes 3ae9fc044871\n scripts/blueprint.py 19291 bytes 804ea6084df6\n scripts/build.mjs 4893 bytes f21f37e458d0\n scripts/bundle.mjs 12289 bytes 9d6744dbca87\n\n================================================================================================\n=====FILE tests/run-all.mjs =====\n// THE RUNNER. Discovers every suite in this folder, runs it, and refuses to report green on\n// anything it did not actually observe pass.\n//\n// [was: a shell glob over tests/*.mjs. taper-test.ts sat at 28/29 RED for two days while the glob\n// reported \"all green\", because a .ts file is not a .mjs file. Discovery is by folder listing now,\n// and a file it cannot run is a FAILURE rather than a skip.]\n//\n// Three rules, all learned the hard way:\n// 1. A suite that will not parse or start is a RED, not a skip.\n// 2. A suite that reports zero assertions is a RED. Blind is not clean.\n// 3. The exit code is the truth. Text saying \"passed\" is not consulted.\nimport { readdirSync, statSync } from \"node:fs\";\nimport { spawnSync } from \"node:child_process\";\nimport { join, dirname } from \"node:path\";\nimport { fileURLToPath } from \"node:url\";\n\nconst HERE = dirname(fileURLToPath(import.meta.url));\n\n// EVERY executable file in this folder is a suite unless it is named below as scaffolding.\n// Not a naming convention: a convention is a thing a future file can quietly fail to follow.\n// [was: /\\.(test\\.mjs|test\\.ts)$/ — which excluded `taper-test.ts` on the hyphen, the same class\n// of miss as the shell glob it replaced. Caught on this runner's first real run.]\nconst RUNNABLE = /\\.(mjs|ts|js|cjs)$/;\n// Scaffolding, named explicitly. Adding to this list is a deliberate act with a reason attached.\nconst NOT_A_SUITE = new Set([\n \"_harness.mjs\", // shared assertions\n \"run-all.mjs\", // this file\n \"negative-controls.mjs\", // run separately: it deliberately breaks things and expects reds\n \"harness.mjs\", // v1 harness, superseded by _harness.mjs, kept for the old .ts suite\n \"claims-registry.mjs\",// data, not assertions: cross-artifact.test.mjs is what tests it\n]);\n\nconst isSuite = (f) => !NOT_A_SUITE.has(f) && RUNNABLE.test(f);\n\nconst files = readdirSync(HERE)\n .filter((f) => statSync(join(HERE, f)).isFile())\n .sort();\n\nconst suites = files.filter(isSuite);\n// Loud about what it declined to run, so \"12 suites\" can be checked against the folder.\nconst skipped = files.filter((f) => !isSuite(f) && !NOT_A_SUITE.has(f));\n\nif (!suites.length) {\n console.log(\"RUNNER FAILURE: found zero suites to run. A runner that runs nothing is not a pass.\");\n process.exit(1);\n}\n\n// REBUILD FIRST, ALWAYS.\n//\n// Every behavioural assertion in this project imports ../build/*.js. Every structural assertion\n// reads ../engine/*.ts. Nothing checked that those two were the same code. On 6 August an\n// adversarial pass deleted the payment-allocation logic from engine/holiday-deposits.ts — the\n// exact fault a negative control exists to catch — ran this runner WITHOUT rebuilding, and got\n// \"270 assertions passed, RESULT: GREEN\". A money bug behind a green wall.\n//\n// So the build is not a thing you remember to do. It is step one of running the tests, and a\n// build that fails is a RED, not a warning.\n{\n const b = spawnSync(\"node\", [join(dirname(HERE), \"scripts\", \"build.mjs\")], { encoding: \"utf8\", timeout: 300_000 });\n if (b.status !== 0) {\n console.log(\"RUNNER FAILURE: the build failed, so the suites would have been testing stale code.\");\n console.log(`${b.stdout ?? \"\"}${b.stderr ?? \"\"}`.trim().slice(0, 1200));\n process.exit(1);\n }\n console.log(\"built engine/ -> build/ before running anything\");\n}\n\n// TYPECHECK, after the build and before the suites. esbuild strips types without checking them,\n// so a field added to a type and missed in two object literals built clean and tested green on\n// 6 August. Found by an adversarial pass, not by anything here.\n{\n const t = spawnSync(\"node\", [join(dirname(HERE), \"scripts\", \"typecheck.mjs\")], { encoding: \"utf8\", timeout: 300_000 });\n const out = `${t.stdout ?? \"\"}${t.stderr ?? \"\"}`.trim();\n console.log(out.split(\"\\n\")[0] ?? \"typecheck: no output\");\n if (t.status !== 0) {\n console.log(\"RUNNER FAILURE: the engine does not typecheck.\");\n console.log(out.slice(0, 1200));\n process.exit(1);\n }\n}\n\nconst runners = { \".ts\": [\"npx\", [\"--yes\", \"tsx\"]], \".mjs\": [\"node\", []] };\nconst runnerFor = (f) => (f.endsWith(\".ts\") ? runners[\".ts\"] : runners[\".mjs\"]);\n\nlet redSuites = 0, totalPass = 0, totalFail = 0;\nconst checksBySuite = {};\nconst assertsBySuite = {};\nconst rows = [];\n\nfor (const f of suites) {\n const [cmd, pre] = runnerFor(f);\n const r = spawnSync(cmd, [...pre, join(HERE, f)], { encoding: \"utf8\", cwd: dirname(HERE), timeout: 120_000 });\n const out = `${r.stdout ?? \"\"}${r.stderr ?? \"\"}`;\n const m = out.match(/=== RESULT: (\\d+) passed, (\\d+) failed(?:, (\\d+) checks)?(?:, (\\d+) assertions)? ===/);\n\n let verdict, pass = 0, fail = 0;\n if (r.error || r.status === null) {\n verdict = `COULD NOT RUN (${r.error?.message ?? \"killed\"})`;\n } else if (!m) {\n // No result line at all: it crashed, or it is not a suite shaped like our suites.\n verdict = `NO RESULT LINE (exit ${r.status})`;\n } else {\n pass = Number(m[1]); fail = Number(m[2]);\n checksBySuite[f] = Number(m[3] ?? 0);\n assertsBySuite[f] = Number(m[4] ?? 0);\n totalPass += pass; totalFail += fail;\n if (pass + fail === 0) verdict = \"ZERO ASSERTIONS (blind, not clean)\";\n else if (fail > 0 || r.status !== 0) verdict = `${fail} FAILED`;\n else verdict = `${pass} passed`;\n }\n\n const green = /passed$/.test(verdict) && !/FAILED/.test(verdict);\n if (!green) {\n redSuites++;\n console.log(`\\n--- ${f} ---`);\n console.log(out.trim().split(\"\\n\").filter((l) => /^FAIL|Error|^\\s{6}/.test(l)).slice(0, 20).join(\"\\n\") || out.trim().slice(0, 1500));\n }\n rows.push([green ? \"OK \" : \"RED \", f, verdict]);\n}\n\nconsole.log(\"\\n================ ALL SUITES ================\");\nfor (const [flag, f, v] of rows) console.log(`${flag} ${f.padEnd(30)} ${v}`);\nif (skipped.length) console.log(`\\nNOT RUN (does not match ${RUNNABLE}): ${skipped.join(\", \")}`);\nconsole.log(`\\n${suites.length} suites, ${totalPass} assertions passed, ${totalFail} failed, ${redSuites} suites red`);\n\nif (redSuites) {\n console.log(\"\\nRESULT: RED\");\n process.exit(1);\n}\n// A SUITE THAT LOSES TESTS MUST GO RED. Deleting the seven assertions that guard the money bug's\n// fourth return took holiday-deposits from 69 to 62 and this runner still printed GREEN: the only\n// floor was a global one, and nothing compared a suite against itself. The floors below are the\n// counts observed passing; raising one is a deliberate act, lowering one is a conversation.\n// [The numbers are not a target. They are a ratchet: tests get added, and a drop means somebody\n// removed a guarantee, which is exactly the move nobody ever announces.]\n// CHECK FLOORS, alongside the test-count floors. A test can pass while inspecting almost nothing;\n// these are the totals each suite reports through scoped(), so hollowing a test out shows up even\n// though the test still says PASS.\nconst CHECK_FLOORS = {\n \"holiday-deposits.test.mjs\": 1544,\n \"deposits-collect.test.mjs\": 136,\n \"dashboard.test.mjs\": 2489,\n};\n// ASSERTION FLOORS. The one count in this project that a test author cannot type: it is\n// incremented inside ok() and eq() themselves. CHECK_FLOORS above is the number a test PASSES to\n// scoped(), and on 7 August that was proved worthless against the failure it was written for —\n// H1's five eq() calls were deleted, `return scoped(5, \"years\")` was left standing, and both the\n// test count and the check count came back byte-identical to the honest run. This floor moves.\nconst ASSERT_FLOORS = {\n \"cadence.test.mjs\": 54,\n \"cross-artifact.test.mjs\": 244,\n \"dashboard.test.mjs\": 891,\n \"deposits-collect.test.mjs\": 155,\n \"detect.test.mjs\": 115,\n \"facts.test.mjs\": 44,\n \"holiday-deposits.test.mjs\": 1594,\n \"kim-copy.test.mjs\": 25,\n \"registry.test.mjs\": 31,\n \"render.test.mjs\": 23,\n \"report-logic.test.mjs\": 38,\n \"slow-track.test.mjs\": 288,\n \"sms-length.test.mjs\": 81,\n \"stories.test.mjs\": 71,\n // taper-test.ts runs on the v1 harness (tests/harness.mjs) and reports no assertion count.\n // Its own hollowing guard lives there instead; see the note in that file.\n};\n// EVERY SUITE HAS A FLOOR. [was: eight of fifteen. The other seven — cadence, facts, registry,\n// render, report-logic, sms-length, stories — were protected only by the global `totalPass < 100`\n// backstop, which had 220 assertions of slack. Deleting five of stories.test.mjs's eight tests\n// dropped the project total from 320 to 315 and printed GREEN.]\nconst FLOORS = {\n \"holiday-deposits.test.mjs\": 88,\n \"deposits-collect.test.mjs\": 38,\n \"dashboard.test.mjs\": 67,\n \"cross-artifact.test.mjs\": 10,\n \"detect.test.mjs\": 19,\n \"kim-copy.test.mjs\": 10,\n \"slow-track.test.mjs\": 14,\n \"taper-test.ts\": 25,\n \"cadence.test.mjs\": 7,\n \"facts.test.mjs\": 11,\n \"registry.test.mjs\": 7,\n \"render.test.mjs\": 8,\n \"report-logic.test.mjs\": 14,\n \"sms-length.test.mjs\": 6,\n \"stories.test.mjs\": 8,\n};\n// A FLOOR ON A SUITE THAT DID NOT RUN GUARDS NOTHING.\n//\n// Every floor above is applied by looking a suite up in `rows`, and `rows` only contains suites\n// discovery actually found. So a suite that vanishes does not fail its floor — it is not there to\n// be measured, and every filter below quietly skips it. Proved three ways on 7 August, each\n// ending in `RESULT: GREEN, exit 0` with a whole suite's coverage gone:\n// delete detect.test.mjs -> 14 suites, GREEN, no mention of it\n// rename it to detect.test.mjs.bak -> GREEN, one passive \"NOT RUN\" line that changes nothing\n// add it to NOT_A_SUITE -> GREEN, and it appears NOWHERE in the output at all\n// This is the same shape as the stale-build hole and the truncated-control-file hole: the runner\n// reporting on work it never did.\n{\n const expected = new Set([...Object.keys(FLOORS), ...Object.keys(CHECK_FLOORS), ...Object.keys(ASSERT_FLOORS)]);\n const missing = [...expected].filter((f) => !rows.some(([, name]) => name === f)).sort();\n if (missing.length) {\n console.log(\"\\nRESULT: RED — a suite that has a floor did not run at all.\");\n console.log(\"It was deleted, renamed out of the runnable pattern, or added to NOT_A_SUITE. A floor\");\n console.log(\"cannot fail a suite that is not there: this is the check that notices it is not there.\");\n for (const f of missing) console.log(` ${f}: has a floor, was never run`);\n process.exit(1);\n }\n console.log(`scaffolding deliberately excluded from discovery (${NOT_A_SUITE.size}): ${[...NOT_A_SUITE].sort().join(\", \")}`);\n}\n{\n const short = rows.filter(([, f]) => FLOORS[f] !== undefined)\n .map(([, f, v]) => [f, Number((v.match(/^(\\d+) passed/) || [])[1] ?? 0)])\n .filter(([f, n]) => n < FLOORS[f]);\n const thin = Object.entries(CHECK_FLOORS)\n .filter(([f, n]) => (checksBySuite[f] ?? 0) < n)\n .map(([f, n]) => [f, checksBySuite[f] ?? 0, n]);\n const hollow = Object.entries(ASSERT_FLOORS)\n .filter(([f, n]) => (assertsBySuite[f] ?? 0) < n)\n .map(([f, n]) => [f, assertsBySuite[f] ?? 0, n]);\n if (hollow.length) {\n console.log(\"\\nRESULT: RED — a suite still passes but is RUNNING FEWER ASSERTIONS than it used to.\");\n console.log(\"This count is incremented inside ok() and eq(), so it is the one number a hollowed-out\");\n console.log(\"test cannot keep steady. If assertions were deliberately merged or removed, move the\");\n console.log(\"floor in run-all.mjs and say why.\");\n for (const [f, n, floor] of hollow) console.log(` ${f}: ${n} assertions ran, floor is ${floor}`);\n process.exit(1);\n }\n if (thin.length) {\n console.log(\"\\nRESULT: RED — a suite still passes but is inspecting LESS than it used to.\");\n console.log(\"A test can be hollowed out to a bare `return scoped(1, ...)` and still say PASS; this is\");\n console.log(\"the total work its checks report. If the drop is deliberate, change the floor and say why.\");\n for (const [f, n, floor] of thin) console.log(` ${f}: ${n} checks now, floor is ${floor}`);\n process.exit(1);\n }\n if (short.length) {\n console.log(\"\\nRESULT: RED — a suite has FEWER assertions than it used to. Guarantees do not\");\n console.log(\"get removed quietly; if this is deliberate, change the floor in run-all.mjs and say why.\");\n for (const [f, n] of short) console.log(` ${f}: ${n} now, floor is ${FLOORS[f]}`);\n process.exit(1);\n }\n}\n\nif (totalPass < 100) {\n console.log(`\\nRESULT: RED — only ${totalPass} assertions across the whole project. That is not a suite, it is a gesture.`);\n process.exit(1);\n}\n\n// THE MONEY GUARDS, RUN EVERY TIME.\n//\n// Two things this replaces. First: negative-controls.mjs is not run here (it deliberately breaks\n// things and expects reds), so nothing would notice if it stopped working — on 6 August an edit\n// truncated that file, deleting the whole runner, and it then printed NOTHING and exited 0, which\n// reads exactly like \"all controls passed\". Second, and worse: a test can be HOLLOWED OUT to a\n// bare `return scoped(3, \"allocations\")` and still print PASS, with the assertion count and the\n// self-reported check count both unchanged. Floors cannot see that. A control can: it injects the\n// fault and demands that named test go red, and a hollow test cannot go red.\n//\n// So the controls guarding the bug that has come back six times run on every single test run.\n// They cost about half a minute. The other ~155 still need `node tests/negative-controls.mjs`.\n//\n// EACH IS PINNED BY FINGERPRINT, NOT BY NAME. The fingerprint is a hash of the fault a control\n// actually injects — file, find, replace, suite and the test it demands go red. [was: the name\n// alone. So the name could be left untouched and the injection underneath it swapped for an\n// unrelated one, and this block kept printing \"7 money guards each proved to still fire\" for a\n// guard that no longer had anything to do with the money bug. Done on 7 August, in one edit, to\n// the control named \"a row is labelled 'Not paid' on Kim's card\" — after which the string\n// \"Not paid\" survived in the control file only inside that name.]\nconst CRITICAL = [\n [\"the allocator debits one $50 while the rule clears on a lump sum\", \"350476142ee4\"],\n [\"one $50 payment settles every holiday stay that customer has\", \"0162bb23668a\"],\n [\"a backfill record from months away is folded into a payment as the same money\", \"563d872d5b35\"],\n [\"a row denies a payment that is sitting in its own window\", \"20b84610424f\"],\n [\"the display list is the collapsed one, so a folded payment vanishes off the row\", \"57e730475b81\"],\n [\"an accusation is added to the note cell, gated on a row state\", \"cd8f1069c9c2\"],\n [\"a row is labelled 'Not paid' on Kim's card\", \"8c99365509f4\"],\n];\n{\n let bad = 0;\n for (const [name, fp] of CRITICAL) {\n const r = spawnSync(\"node\", [join(HERE, \"negative-controls.mjs\"), \"--only\", name],\n { encoding: \"utf8\", cwd: dirname(HERE), timeout: 240_000 });\n const out = `${r.stdout ?? \"\"}${r.stderr ?? \"\"}`;\n const m = out.match(/=== RESULT: (\\d+) passed, (\\d+) failed ===/);\n if (!m) {\n console.log(`\\nRESULT: RED — the control suite printed no result for \"${name}\".`);\n console.log(out.trim().slice(0, 600) || \"(no output at all)\");\n process.exit(1);\n }\n if (Number(m[1]) !== 1 || Number(m[2]) !== 0) {\n console.log(`\\nRESULT: RED — the guard for \"${name}\" no longer fires: ${m[0]}`);\n console.log(out.split(\"\\n\").filter((l) => /^\\s+/.test(l)).slice(0, 6).join(\"\\n\"));\n bad++;\n continue;\n }\n if (!out.includes(`[fp:${fp}]`)) {\n console.log(`\\nRESULT: RED — the control named \"${name}\" passed, but it is not the same control.`);\n console.log(`Expected fingerprint ${fp}; got ${(out.match(/fp:[0-9a-f]+/) || [\"none\"])[0]}. The name was kept`);\n console.log(\"and the fault underneath it changed, so this line has been reporting on the wrong guarantee.\");\n bad++;\n }\n }\n if (bad) {\n console.log(\"\\nA guarantee that cannot be made to fail is not guarded. Fix the test, not the control.\");\n process.exit(1);\n }\n console.log(`\\ncontrol harness: alive, and ${CRITICAL.length} money guards each proved to still fire`);\n}\n\nconsole.log(\"\\nRESULT: GREEN\");\n\n\n=====FILE tests/slow-track.test.mjs =====\n// THE SLOW TRACK. Kim signed this off, so its shape is now a promise rather than a preference.\n// 4 weekly, 13 fortnightly, then monthly forever, keyed to the calendar so seasonal copy lands in\n// season. These tests exist because the failure mode here is silent: a bad offset does not throw,\n// it just sends August's copy in February, or sends the same email twice in one month.\nimport * as T from \"../build/taper.js\";\nimport * as S from \"../build/stories.js\";\nimport { suite, ok, eq, scoped } from \"./_harness.mjs\";\nconst { t, done } = suite(\"slow-track\");\n\nconst HOUR = 1;\nconst WEEK = 168;\nconst FORTNIGHT = 336;\n\nt(\"T1 the track is the shape Kim signed off: 4 weekly, 13 fortnightly, then monthly\", () => {\n eq(T.SLOW_WEEKLY_COUNT, 4);\n eq(T.SLOW_FORTNIGHTLY_COUNT, 13);\n eq(T.SLOW_WEEKLY.length, 4, \"weekly bank does not match its declared count\");\n eq(T.SLOW_FORTNIGHTLY.length, 13, \"fortnightly bank does not match its declared count\");\n eq(T.SLOW_MONTHLY_BANK.length, 12, \"the monthly bank must cover every calendar month\");\n return scoped(4 + 13 + 12, \"templates\");\n});\n\nt(\"T2 every phase boundary hands over to the next without a gap or an overlap\", () => {\n const phases = [];\n for (let n = 0; n < 40; n++) phases.push(T.nextSlowTouch(n).phase);\n eq(phases.slice(0, 4), [\"weekly\", \"weekly\", \"weekly\", \"weekly\"]);\n eq(phases.slice(4, 17), Array(13).fill(\"fortnightly\"));\n ok(phases.slice(17).every((p) => p === \"monthly\"), \"the track stops being monthly at some point\");\n return scoped(40, \"touches walked\");\n});\n\nt(\"T3 offsets only ever move forward, and by the interval the phase promises\", () => {\n let prev = 0;\n const gaps = [];\n for (let n = 0; n < 40; n++) {\n const { offsetHours } = T.nextSlowTouch(n);\n ok(offsetHours > prev, `touch ${n} at ${offsetHours}h does not come after touch ${n - 1} at ${prev}h`);\n gaps.push(offsetHours - prev);\n prev = offsetHours;\n }\n eq(gaps.slice(0, 4), [WEEK, WEEK, WEEK, WEEK], \"the weekly phase is not weekly\");\n eq(gaps.slice(5, 17), Array(12).fill(FORTNIGHT), \"the fortnightly phase is not fortnightly\");\n eq(gaps.slice(18, 40), Array(22).fill(T.SLOW_MONTHLY_INTERVAL_HOURS), \"the monthly phase is not monthly\");\n return scoped(40, \"intervals\");\n});\n\nt(\"T4 the handover gaps are sane rather than merely forward\", () => {\n // The two seams. Neither is allowed to fire same-day or leave a month of silence.\n const seamA = T.nextSlowTouch(4).offsetHours - T.nextSlowTouch(3).offsetHours;\n const seamB = T.nextSlowTouch(17).offsetHours - T.nextSlowTouch(16).offsetHours;\n ok(seamA >= 24 * HOUR, `weekly-to-fortnightly seam is ${seamA}h: same-day double send`);\n ok(seamA <= 2 * FORTNIGHT, `weekly-to-fortnightly seam is ${seamA}h: a silent month`);\n ok(seamB >= 24 * HOUR, `fortnightly-to-monthly seam is ${seamB}h: same-day double send`);\n ok(seamB <= 2 * T.SLOW_MONTHLY_INTERVAL_HOURS, `fortnightly-to-monthly seam is ${seamB}h: a silent quarter`);\n return scoped(2, \"seams\");\n});\n\nt(\"T5 a weekly or fortnightly touch always hands back a real template\", () => {\n let checked = 0;\n for (let n = 0; n < T.SLOW_WEEKLY_COUNT + T.SLOW_FORTNIGHTLY_COUNT; n++) {\n const { template, phase } = T.nextSlowTouch(n);\n ok(template && typeof template === \"object\", `${phase} touch ${n} handed back no template`);\n ok(template.id, `${phase} touch ${n} has no id`);\n ok(template.subject || template.bodyTemplate, `${template.id} is empty`);\n checked++;\n }\n return scoped(checked, \"templates resolved\");\n});\n\nt(\"T6 a monthly touch defers to the calendar rather than carrying a template\", () => {\n for (let n = 17; n < 30; n++) {\n eq(T.nextSlowTouch(n).template, null, `monthly touch ${n} carries a fixed template: seasonal copy will drift`);\n }\n return scoped(13, \"monthly touches\");\n});\n\nt(\"T7 every month of the year resolves to its own template\", () => {\n const ids = new Set();\n for (let m = 0; m < 12; m++) {\n const d = new Date(Date.UTC(2026, m, 15, 12, 0, 0));\n const tpl = T.monthlyTemplateFor(d);\n ok(tpl && tpl.id, `month ${m + 1} has no template`);\n ids.add(tpl.id);\n }\n eq(ids.size, 12, \"two calendar months share a template: one of them is out of season\");\n return scoped(12, \"months\");\n});\n\nt(\"T8 the same monthly email never goes out twice in a row\", () => {\n let guarded = 0;\n for (let m = 0; m < 12; m++) {\n const d = new Date(Date.UTC(2026, m, 28, 12, 0, 0));\n const natural = T.monthlyTemplateFor(d);\n const served = T.monthlyTemplateAvoidingRepeat(d, natural.id);\n ok(served.id !== natural.id, `month ${m + 1} served ${served.id} twice running`);\n guarded++;\n }\n // and when the last send was something else, it serves the natural one\n for (let m = 0; m < 12; m++) {\n const d = new Date(Date.UTC(2026, m, 3, 12, 0, 0));\n eq(T.monthlyTemplateAvoidingRepeat(d, \"something-else\").id, T.monthlyTemplateFor(d).id,\n `month ${m + 1} dodged when it had no reason to`);\n }\n return scoped(guarded * 2, \"month/last-send pairs\");\n});\n\nt(\"T9 no slow-track copy carries a word Kim has struck out\", () => {\n const banned = [/\\bdaycare\\b/i, /\\bday care\\b/i, /\\bdiscovery call\\b/i, /\\btoilet\\b/i, /\\bgarden\\b/i,\n /\\bwhilst\\b/i, /\\benquir/i, /\\bcolour/i, /\\bfavourite/i, /\\brecognise/i, /\\bapologise/i, /\\bcentre\\b/i];\n const all = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY, ...T.SLOW_MONTHLY_BANK];\n const hits = [];\n for (const m of all) {\n const text = [m.subject ?? \"\", m.previewText ?? \"\", m.bodyTemplate ?? \"\"].join(\"\\n\");\n for (const b of banned) if (b.test(text)) hits.push(`${m.id}: ${b.source}`);\n }\n eq(hits, []);\n return scoped(all.length * banned.length, \"message/word pairs\");\n});\n\nt(\"T10 no slow-track message leaks an unresolved story token\", () => {\n const all = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY, ...T.SLOW_MONTHLY_BANK];\n const bad = all\n .filter((m) => /\\{\\{STORY:/.test(S.resolveStories([m.subject ?? \"\", m.bodyTemplate ?? \"\"].join(\"\\n\"))))\n .map((m) => m.id);\n eq(bad, []);\n return scoped(all.length, \"slow-track messages\");\n});\n\nt(\"T11 every slow-track message has an id, and no two share one\", () => {\n const all = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY, ...T.SLOW_MONTHLY_BANK];\n const ids = all.map((m) => m.id);\n ok(ids.every(Boolean), \"a message has no id: the journal cannot record what was sent\");\n const dupes = ids.filter((id, i) => ids.indexOf(id) !== i);\n eq(dupes, [], \"duplicate ids: two different messages would log as the same send\");\n return scoped(ids.length, \"ids\");\n});\n\n// [was: T12 asserted the slow track is email-only. It is not — it alternates email and SMS on\n// purpose, and the assertion was my guess rather than anything read off the track. It failed on\n// slow_w-2 the first time it ran, which is the only reason the guess got caught. The check below\n// tests what the track actually promises.]\nt(\"T12 every message declares a channel, and carries what that channel needs\", () => {\n const all = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY, ...T.SLOW_MONTHLY_BANK];\n let checked = 0;\n for (const m of all) {\n ok(m.channel === \"email\" || m.channel === \"sms\", `${m.id} has channel ${JSON.stringify(m.channel)}`);\n if (m.channel === \"email\") {\n ok((m.subject ?? \"\").trim().length > 0, `${m.id} is an email with no subject line`);\n ok((m.bodyTemplate ?? \"\").trim().length > 40, `${m.id} is an email with no body`);\n } else {\n eq((m.subject ?? \"\").trim(), \"\", `${m.id} is an SMS carrying a subject line nobody will see`);\n ok((m.bodyTemplate ?? \"\").trim().length > 0, `${m.id} is an empty SMS`);\n }\n checked++;\n }\n return scoped(checked, \"messages\");\n});\n\nt(\"T13 two text messages never land back to back\", () => {\n // Send order for the fixed phases, calendar order for the monthly bank (which wraps Dec to Jan).\n const linear = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY];\n const monthly = [...T.SLOW_MONTHLY_BANK, T.SLOW_MONTHLY_BANK[0]]; // wrap\n let pairs = 0;\n const run = (seq, label) => {\n for (let i = 1; i < seq.length; i++) {\n ok(!(seq[i - 1].channel === \"sms\" && seq[i].channel === \"sms\"),\n `${label}: ${seq[i - 1].id} then ${seq[i].id} are both texts`);\n pairs++;\n }\n };\n run(linear, \"fixed phases\");\n run(monthly, \"monthly bank\");\n // The seam into the monthly phase. The first monthly send can land in ANY calendar month, so the\n // only way to guarantee the seam is for the last fixed-phase message to be an email.\n ok(linear[linear.length - 1].channel === \"email\",\n `the last fixed-phase message (${linear[linear.length - 1].id}) is a text, so the seam into the monthly phase can double up`);\n pairs++;\n return scoped(pairs, \"consecutive pairs\");\n});\n\nt(\"T14 the dodge for a repeated month can never serve two texts in a row\", () => {\n // monthlyTemplateAvoidingRepeat serves NEXT month when this month's was the last thing sent.\n // If the bank ever stopped alternating, that dodge could hand back a second text.\n let checked = 0;\n for (let m = 0; m < 12; m++) {\n const d = new Date(Date.UTC(2026, m, 28, 12, 0, 0));\n const natural = T.monthlyTemplateFor(d);\n const dodged = T.monthlyTemplateAvoidingRepeat(d, natural.id);\n ok(!(natural.channel === \"sms\" && dodged.channel === \"sms\"),\n `a repeat in month ${m + 1} dodges from ${natural.id} to ${dodged.id}: two texts running`);\n checked++;\n }\n return scoped(checked, \"dodges\");\n});\n\ndone();\n\n\n=====FILE tests/sms-length.test.mjs =====\n// SMS LENGTH, EVERY TRACK. v2.0, 5 Aug 2026.\n// The 320-character rule was enforced on the 21-day sequence and its branches, and on nothing else.\n// A Halloween text sat at 354 as sent, 34 over, splitting into two billed segments every October.\n// Worse: the first version of this check read `E.TAPER_MESSAGES`, a name that does not exist, so it\n// measured zero messages and printed \"all within limit\". T0 is the guard against that.\nimport * as E from \"../build/engine.js\";\nimport { suite, ok, scoped, TRACKS, allMessages } from \"./_harness.mjs\";\nconst { t, done } = suite(\"sms\");\n\nconst LIMIT = 320, OPTOUT = \"\\n\\nReply STOP to stop these texts.\", LONG_NAME = \"Christopher\";\nconst render = (m) => (m.bodyTemplate.replaceAll(\"{{FIRST_NAME}}\", LONG_NAME)\n .replace(/\\{\\{STORY:[^}]+\\}\\}/g, \"\").replace(/\\n{3,}/g, \"\\n\\n\").trim() + OPTOUT);\nconst sms = () => allMessages(E).filter((m) => m.channel === \"sms\");\n\nt(\"T0 every named track is exported and non-empty\", () => {\n for (const k of TRACKS) { ok(Array.isArray(E[k]), `${k} not exported: a check over it would silently pass`); ok(E[k].length, `${k} empty`); }\n return scoped(TRACKS.length, \"tracks\");\n});\nt(\"T1 no SMS exceeds 320 as actually sent, worst-case name\", () => {\n const over = sms().filter((m) => render(m).length > LIMIT).map((m) => `${m.track}/${m.id}=${render(m).length}`);\n ok(over.length === 0, `over the limit:\\n ${over.join(\"\\n \")}`);\n return scoped(sms().length, \"texts checked\");\n});\nt(\"T2 the opt-out is counted, not assumed away\", () => {\n ok(OPTOUT.length > 20);\n const worst = sms().map((m) => ({ id: m.id, len: render(m).length })).sort((a, b) => b.len - a.len)[0];\n ok(worst.len <= LIMIT, `${worst.id} at ${worst.len}`);\n return `tightest: ${worst.id} at ${worst.len}/${LIMIT}`;\n});\nt(\"T3 no text is so short it reads as a fragment\", () => {\n const tiny = sms().filter((m) => render(m).length < 80).map((m) => m.id);\n ok(tiny.length === 0, `suspiciously short: ${tiny.join(\", \")}`);\n return scoped(sms().length, \"texts checked\");\n});\nt(\"T4 every SMS names the sender, so it never lands as an unknown number\", () => {\n const anon = sms().filter((m) => !/Kim/.test(m.bodyTemplate)).map((m) => m.id);\n ok(anon.length === 0, `no sender named in: ${anon.join(\", \")}`);\n return scoped(sms().length, \"texts checked\");\n});\nt(\"T5 emails carry a subject and a body, texts carry neither an empty body nor a subject\", () => {\n const emails = allMessages(E).filter((m) => m.channel === \"email\");\n for (const m of emails) { ok(m.subject && m.subject.trim(), `${m.id} has no subject`); ok(m.bodyTemplate.trim().length > 100, `${m.id} body too short`); }\n for (const m of sms()) ok(!m.subject, `${m.id} is a text with a subject`);\n return `${emails.length} emails, ${sms().length} texts`;\n});\ndone();\n\n\n=====FILE tests/stories.test.mjs =====\n// KIM'S STORIES. Eight slots, all empty on purpose.\n// The standing rule: never invent a story, customer, testimonial, name or event. A slot with an\n// honest fallback beats a plausible lie. These tests exist so that rule survives a future edit.\nimport * as S from \"../build/stories.js\";\nimport * as E from \"../build/engine.js\";\nimport { suite, ok, eq, scoped, TRACKS, allMessages, msgText } from \"./_harness.mjs\";\nconst { t, done } = suite(\"stories\");\n\nt(\"S1 there are eight slots and every one is empty\", () => {\n eq(S.STORY_SLOTS.length, 8);\n for (const s of S.STORY_SLOTS) {\n eq(s.story, null, `${s.id} has been filled: a story must come from Kim, never from us`);\n ok(s.prompt && s.prompt.length > 25, `${s.id} has no 30-second prompt for her`);\n ok(s.lands && s.lands.length > 10, `${s.id} does not say where it lands`);\n ok(/^[a-z0-9_-]+$/i.test(s.id), `${s.id} is not a usable id`);\n }\n return scoped(S.STORY_SLOTS.length, \"slots, all empty\");\n});\nt(\"S2 an empty slot renders as nothing, never as a placeholder a customer could see\", () => {\n for (const s of S.STORY_SLOTS) {\n const out = S.storyFor(s.id);\n ok(out === \"\" || out == null, `${s.id} renders \"${out}\" when empty`);\n }\n return scoped(S.STORY_SLOTS.length, \"slots\");\n});\nt(\"S3 an unknown slot id yields nothing rather than throwing or inventing\", () => {\n for (const bad of [\"nope\", \"\", null, undefined, \"{{STORY:x}}\"]) {\n const out = S.storyFor(bad);\n ok(out === \"\" || out == null, `unknown id ${JSON.stringify(bad)} produced \"${out}\"`);\n }\n return scoped(5, \"unknown ids\");\n});\nt(\"S4 resolveStories strips every token and leaves no blank-line scar\", () => {\n const body = \"Before.\\n\\n{{STORY:slot_a}}\\n\\nAfter.\";\n const out = S.resolveStories(body);\n ok(!/\\{\\{STORY:/.test(out), \"a raw token survived into the message\");\n ok(!/\\n{3,}/.test(out), \"an empty slot left a gap of blank lines\");\n ok(out.includes(\"Before.\") && out.includes(\"After.\"), \"surrounding copy was damaged\");\n return scoped(3, \"assertions\");\n});\nt(\"S5 a nested or malformed token cannot leak through\", () => {\n for (const b of [\"{{STORY:{{STORY:x}}}}\", \"{{STORY:}}\", \"{{STORY: a b }}\", \"{{STORY:a}}{{STORY:b}}\"]) {\n ok(!/\\{\\{STORY:/.test(S.resolveStories(b)), `token survived: ${b}`);\n }\n return scoped(4, \"malformed tokens\");\n});\nt(\"S6 no message contains an unresolved story token after rendering\", () => {\n const all = allMessages(E);\n const bad = all.filter((m) => /\\{\\{STORY:/.test(S.resolveStories(msgText(m)))).map((m) => m.id);\n eq(bad, []);\n return scoped(all.length, \"messages\");\n});\nt(\"S7 every slot referenced by a message actually exists\", () => {\n const ids = new Set(S.STORY_SLOTS.map((s) => s.id));\n const used = new Set();\n for (const m of allMessages(E)) for (const mm of msgText(m).matchAll(/\\{\\{STORY:([^}]+)\\}\\}/g)) used.add(mm[1].trim());\n const orphans = [...used].filter((u) => !ids.has(u));\n eq(orphans, [], \"a message references a slot that does not exist\");\n return scoped(used.size, \"slots referenced\");\n});\nt(\"S8 no slot prompt asks Kim for something she cannot answer in 30 seconds\", () => {\n for (const s of S.STORY_SLOTS) {\n ok(s.prompt.length < 400, `${s.id} prompt is an essay, not a 30-second ask`);\n ok(/\\?/.test(s.prompt), `${s.id} prompt is not phrased as a question`);\n }\n return scoped(S.STORY_SLOTS.length, \"prompts\");\n});\ndone();\n\n\n=====FILE tests/taper-test.ts =====\n// Taper track test harness — run with: tsx tests/taper-test.ts\nimport {\n SLOW_WEEKLY,\n SLOW_FORTNIGHTLY,\n SLOW_MONTHLY_BANK,\n nextSlowTouch,\n monthlyTemplateFor,\n} from \"../engine/taper-messages.ts\";\nimport { REAL_BOOKING_URL } from \"../engine/puppy-messages.ts\";\nimport { STORY_SLOTS } from \"../engine/kim-stories.ts\";\n\nlet pass = 0,\n fail = 0;\nfunction t(name: string, ok: boolean, extra = \"\") {\n if (ok) pass++;\n else fail++;\n console.log((ok ? \"PASS\" : \"FAIL\") + \" — \" + name + (extra ? \" [\" + extra + \"]\" : \"\"));\n}\n\n// 1. Counts match Kim's spec exactly\nt(\"weekly count = 4\", SLOW_WEEKLY.length === 4);\nt(\"fortnightly count = 13\", SLOW_FORTNIGHTLY.length === 13);\nt(\"monthly bank = 12 (one per calendar month)\", SLOW_MONTHLY_BANK.length === 12);\n\n// 2. Offsets: weekly at rel days 7/14/21/28, fortnightly rel days 42..210 step 14\nconst wOff = SLOW_WEEKLY.map((m) => m.offsetHours);\nt(\"weekly offsets 168/336/504/672\", JSON.stringify(wOff) === JSON.stringify([168, 336, 504, 672]));\nconst fOff = SLOW_FORTNIGHTLY.map((m) => m.offsetHours);\nconst fExpect = Array.from({ length: 13 }, (_, i) => 1008 + 336 * i);\nt(\"fortnightly offsets rel day 42..210 step 14\", JSON.stringify(fOff) === JSON.stringify(fExpect));\nt(\n \"no overlap: last weekly (672) < first fortnightly (1008)\",\n wOff[3] < fOff[0]\n);\n\n// 3. Scheduler walk: 30 sends in a row, offsets strictly increasing, phases in order\nlet prev = -1;\nlet order: string[] = [];\nlet mono = true;\nfor (let i = 0; i < 30; i++) {\n const n = nextSlowTouch(i);\n if (n.offsetHours <= prev) mono = false;\n prev = n.offsetHours;\n order.push(n.phase);\n}\nt(\"offsets strictly increasing across 30 sends\", mono);\nt(\n \"phase order weekly x4 -> fortnightly x13 -> monthly x13+\",\n JSON.stringify(order.slice(0, 4)) === JSON.stringify(Array(4).fill(\"weekly\")) &&\n JSON.stringify(order.slice(4, 17)) === JSON.stringify(Array(13).fill(\"fortnightly\")) &&\n order.slice(17).every((p) => p === \"monthly\")\n);\nt(\"first monthly at rel hour 5760 (abs day 261)\", nextSlowTouch(17).offsetHours === 5760);\nt(\"second monthly 30d later (6480)\", nextSlowTouch(18).offsetHours === 6480);\nt(\"monthly template resolved by landing month\", nextSlowTouch(17).template === null);\n\n// 4. Monthly bank keyed to calendar months, seasonal copy in season\nt(\"July message covers heat + fireworks\", /heat|hot/i.test(SLOW_MONTHLY_BANK[6].bodyTemplate) && /firework/i.test(SLOW_MONTHLY_BANK[6].bodyTemplate));\nt(\"December message covers holidays\", /holiday|routine/i.test(SLOW_MONTHLY_BANK[11].bodyTemplate));\nt(\"monthlyTemplateFor picks by month\", monthlyTemplateFor(new Date(2027, 6, 15)).id === \"slow_m-jul\" && monthlyTemplateFor(new Date(2027, 11, 3)).id === \"slow_m-dec\");\n\n// 5. THE PROMISE: no ask attached to any taper message. No booking links anywhere.\nconst all = [...SLOW_WEEKLY, ...SLOW_FORTNIGHTLY, ...SLOW_MONTHLY_BANK];\nt(\n \"zero booking links in all 29 messages\",\n all.every((m) => !m.bodyTemplate.includes(REAL_BOOKING_URL) && !m.bodyTemplate.includes(\"widget/booking\") && !/book(ing)? (a|your|here)/i.test(m.bodyTemplate))\n);\nt(\n \"no sales asks (book now / sign up / enroll / offer / discount)\",\n all.every((m) => !/book now|sign up|enrol|% off|discount|special offer|limited/i.test(m.bodyTemplate))\n);\n\n// 6. Hygiene: ids unique, placeholders well-formed, channels valid, sms length sane\nconst ids = new Set(all.map((m) => m.id));\nt(\"all 29 ids unique\", ids.size === all.length);\nt(\"channels valid\", all.every((m) => m.channel === \"sms\" || m.channel === \"email\"));\nt(\n \"emails have subject+preview, sms have neither\",\n all.every((m) => (m.channel === \"email\" ? !!m.subject && !!m.previewText : !m.subject && !m.previewText))\n);\n// [was: this allowed only {{FIRST_NAME}} and {{DOG_NAME}}, so it went red on all eight legitimate\n// {{STORY:id}} slots the moment the story system landed. The test was stale, not the copy. It now\n// allows a story token ONLY when the slot actually exists, which is the stronger check: a typo in\n// a slot id would previously have been \"malformed\" and is now caught by name.]\nconst KNOWN_SLOTS = new Set(STORY_SLOTS.map((s) => s.id));\nconst badTokens: string[] = [];\nfor (const m of all) {\n for (const p of m.bodyTemplate.match(/\\{\\{[^}]*\\}\\}/g) || []) {\n if (p === \"{{FIRST_NAME}}\" || p === \"{{DOG_NAME}}\") continue;\n const story = p.match(/^\\{\\{STORY:([a-z_]+)\\}\\}$/);\n if (story && KNOWN_SLOTS.has(story[1])) continue;\n badTokens.push(`${m.id}:${p}`);\n }\n}\nt(\"no malformed placeholders, and every story token names a real slot\", badTokens.length === 0, badTokens.join(\" \"));\nconst smsLens = all.filter((m) => m.channel === \"sms\").map((m) => m.bodyTemplate.replace(\"{{FIRST_NAME}}\", \"Jennifer\").replace(/\\{\\{DOG_NAME\\}\\}/g, \"Biscuit\").length);\nt(\"all sms under 400 chars rendered\", smsLens.every((l) => l < 400), \"max=\" + Math.max(...smsLens));\nt(\"every message signed Kim\", all.every((m) => m.bodyTemplate.includes(\"Kim\")));\nt(\"no pbe- slug anywhere\", all.every((m) => !m.bodyTemplate.includes(\"pbe-\")));\n\n// 7. Reply mechanism.\n// [was: \"sms all carry a reply line\", checked against the TEMPLATE. It read red on 7 of 13 texts.\n// Wrong artifact: the opt-out line is appended at render time, never stored in the template, so\n// every text as actually sent ends \"Reply STOP to stop these texts.\" The check below measures the\n// sent message. The separate, real gap the old check was groping at is measured underneath it.]\nconst SMS_OPTOUT_SENT = \"Reply STOP to stop these texts.\";\nt(\n \"every text as actually sent ends with the opt-out line\",\n all.filter((m) => m.channel === \"sms\").every((m) => (m.bodyTemplate + \"\\n\\n\" + SMS_OPTOUT_SENT).trimEnd().endsWith(SMS_OPTOUT_SENT))\n);\n\n// THE REAL GAP, measured rather than asserted away. A customer on the slow track can go a long\n// stretch where the only thing any message tells them to do is leave. Ten of the twenty-nine\n// messages invite a reply; the longest run without one is FIVE (Jul, Aug, Sep, Oct, Nov), which in\n// the monthly phase is about five months.\n//\n// This is NOT fixed in the copy, deliberately. Kim signed the slow track off and was told in\n// writing that nothing in it changed; quietly editing seven messages would make that sentence\n// false. It is a question for her, and it is in the ledger. The number is LOCKED here so the gap\n// cannot get worse while it waits for an answer.\nconst invitesReply = (m: { bodyTemplate: string }) =>\n /\\breply\\b|\\blet me know\\b|\\btell me\\b|\\bask me\\b|\\btext me\\b/i.test(m.bodyTemplate);\nlet run = 0, worstRun = 0;\nfor (const m of all) { if (invitesReply(m)) run = 0; else if (++run > worstRun) worstRun = run; }\nt(\n \"the run of messages with no invitation to reply has not grown past its known value of 5\",\n worstRun <= 5,\n `longest run ${worstRun}, invited ${all.filter(invitesReply).length}/${all.length}`\n);\n\nconsole.log(`\\n=== RESULT: ${pass} passed, ${fail} failed ===`);\nprocess.exit(fail ? 1 : 0);\n\n\n=====FILE scripts/blueprint.py =====\nfrom reportlab.lib.pagesizes import A4\nfrom reportlab.lib.styles import getSampleStyleSheet, ParagraphStyle\nfrom reportlab.lib.units import mm\nfrom reportlab.lib import colors\nfrom reportlab.platypus import (SimpleDocTemplate, Paragraph, Spacer, Table, TableStyle,\n PageBreak, KeepTogether, HRFlowable)\n\nOUT = \"/mnt/user-data/outputs/CALL-BLUEPRINT-9-Aug.pdf\"\nss = getSampleStyleSheet()\nINK = colors.HexColor(\"#14171a\"); MUT = colors.HexColor(\"#5b6570\")\nACC = colors.HexColor(\"#1c5d99\"); RED = colors.HexColor(\"#b3261e\")\nGRN = colors.HexColor(\"#1a6b3c\"); BG = colors.HexColor(\"#f4f6f8\")\n\nH1 = ParagraphStyle(\"H1\", parent=ss[\"Normal\"], fontName=\"Helvetica-Bold\", fontSize=16, leading=19, textColor=INK, spaceAfter=1)\nSUB = ParagraphStyle(\"SUB\", parent=ss[\"Normal\"], fontName=\"Helvetica\", fontSize=9, leading=12, textColor=MUT, spaceAfter=9)\nS = ParagraphStyle(\"S\", parent=ss[\"Normal\"], fontName=\"Helvetica-Bold\", fontSize=11.5, leading=14, textColor=ACC, spaceBefore=11, spaceAfter=4)\nB = ParagraphStyle(\"B\", parent=ss[\"Normal\"], fontName=\"Helvetica\", fontSize=9.2, leading=12.3, textColor=INK, spaceAfter=3)\nLI = ParagraphStyle(\"LI\", parent=B, leftIndent=11, spaceAfter=2.5)\nQ = ParagraphStyle(\"Q\", parent=B, fontName=\"Helvetica-Bold\", textColor=INK, spaceBefore=5, spaceAfter=1)\nA = ParagraphStyle(\"A\", parent=B, leftIndent=11, textColor=colors.HexColor(\"#20303f\"), spaceAfter=1)\nNOTE= ParagraphStyle(\"NOTE\", parent=B, fontName=\"Helvetica-Oblique\", textColor=MUT, leftIndent=11, spaceAfter=4)\n\nst = []\ndef sec(t): st.append(Paragraph(t, S))\ndef p(t, s=B): st.append(Paragraph(t, s))\ndef bl(items, s=LI):\n for t in items: st.append(Paragraph(\"•\" + t, s))\ndef qa(q, a, note=None):\n blk=[Paragraph(q, Q), Paragraph(a, A)]\n if note: blk.append(Paragraph(note, NOTE))\n st.append(KeepTogether(blk))\nCELL = ParagraphStyle(\"CELL\", parent=ss[\"Normal\"], fontName=\"Helvetica\", fontSize=8.6, leading=11.4, textColor=INK)\nKEY = ParagraphStyle(\"KEY\", parent=CELL, fontName=\"Helvetica-Bold\")\ndef box(rows, widths, head=None):\n rows = [[Paragraph(c, KEY if i == 0 else CELL) for i, c in enumerate(r)] for r in rows]\n data = ([head] if head else []) + rows\n t = Table(data, colWidths=widths)\n style=[(\"FONT\",(0,0),(-1,-1),\"Helvetica\",8.6),(\"VALIGN\",(0,0),(-1,-1),\"TOP\"),\n (\"TEXTCOLOR\",(0,0),(-1,-1),INK),(\"BOTTOMPADDING\",(0,0),(-1,-1),4),(\"TOPPADDING\",(0,0),(-1,-1),4),\n (\"LINEBELOW\",(0,0),(-1,-2),0.4,colors.HexColor(\"#dfe4e9\")),\n (\"FONT\",(0,0),(0,-1),\"Helvetica-Bold\",8.6)]\n if head: style += [(\"FONT\",(0,0),(-1,0),\"Helvetica-Bold\",8),(\"TEXTCOLOR\",(0,0),(-1,0),MUT),\n (\"LINEBELOW\",(0,0),(-1,0),0.8,colors.HexColor(\"#b9c2cb\"))]\n t.setStyle(TableStyle(style)); st.append(t)\n\n# ============================ PAGE 1 ============================\np(\"The Dogs Spot: your blueprint for tonight\", H1)\np(\"Sunday 9 August, 20:00 to 21:00 Oxford time (3:00pm for Kim in Georgia). \"\n \"meet.google.com/kii-bcbi-ihm. Dial in (GB) +44 20 3873 3170 PIN 177 520 765 1562#.\", SUB)\n\nsec(\"The whole thing in five sentences\")\np(\"Kim Hicks owns a dog boarding and training business in Savannah, Georgia. She is paying two \"\n \"separate people. Kristian Moore has spent months building her a custom web application \"\n \"plus Chloe, the AI that answers her phone, and he is many months late. You were hired \"\n \"separately for the marketing side: ad tracking, reporting, and the automatic follow up messages. \"\n \"Tonight is Kristian's final exam, where Kim checks whether what he built actually works before \"\n \"she signs it off and takes ownership. You are in the room because you inherit Chloe and the \"\n \"GoHighLevel side the moment he signs off, so you need to see the condition of what is coming \"\n \"to you.\")\n\nsec(\"Why you specifically are on this call\")\np(\"Kim put it in writing to Kristian on 4 August: \\\"I've also engaged another developer, Amir, \"\n \"who is helping me with the ongoing GoHighLevel ecosystem, tracking, reporting, and future \"\n \"automation work. Since his work will need to integrate with the platform you've built, I'd like \"\n \"him to join the acceptance walkthrough.\\\"\")\np(\"And in her Chloe email on 7 August: \\\"Amir is included for visibility because he will be \"\n \"taking Chloe over once Kristian's handoff has been completed.\\\"\")\np(\"So your job tonight is to receive information, not to give it. You are the incoming owner \"\n \"doing a survey on a house before contracts exchange. Nobody expects you to perform.\")\n\nsec(\"The cast\")\nbox([\n [\"Kim Hicks\", \"The client. Pays you both. Sharp, thorough, writes long. Has spent this week \"\n \"documenting Kristian's failures in forensic detail. Not angry at you.\"],\n [\"Kristian Moore\", \"Moore Cre8ive. Built the app and Chloe. Under pressure. Wants sign off and \"\n \"the 30 day warranty clock started. Has asked, politely, that you touch nothing.\"],\n [\"Chloe\", \"Not a person. The AI voice agent that answers Kim's phones and books appointments. \"\n \"Built inside GoHighLevel. Becomes yours after handover.\"],\n [\"Candice\", \"Kim's new staff member, started around 2 August. The second Pup Talk calendar is for her.\"],\n], [26*mm, 148*mm])\n\nsec(\"What has actually happened since the start of August\")\nbox([\n [\"2 Aug\", \"You welcomed Candice. The Bootcamp deposit on the website was corrected from $250 to $500.\"],\n [\"4 Aug\", \"Kim tells Kristian she has hired you, and asks him five hard questions in advance so the \"\n \"walkthrough is not spent explaining. She refuses to accept the app until she has seen it \"\n \"running in her own accounts.\"],\n [\"6 Aug\", \"Kim sends you a very long message: six wording changes to the follow up messages, a \"\n \"request for tag cleanup, questions about deposits, and her answers to your question cards. \"\n \"She says the old puppy workflow has never been used and can be switched off any time.\"],\n [\"7 Aug\", \"The bad day. Four real customers call in and Chloe mishandles all four. Kim writes the \"\n \"whole thing up and sends it to Kristian, copying you, demanding seven fixes before tonight. \"\n \"Kristian replies with a long defence of what is built. They agree a freeze: you observe, \"\n \"you change nothing in the app, calendars, workflows or Chloe.\"],\n [\"7 Aug\", \"You send the Friday report at 11:46pm. One line in it is wrong.\"],\n [\"8 Aug\", \"You catch it yourself at 7:33am and correct it to her: you had read the wrong field, and \"\n \"her Facebook tracking was working all along.\"],\n [\"9 Aug\", \"Today. Facebook ad permission fixed and watched working. Corrected report rebuilt. Kim \"\n \"answers your question cards and says yes to the three that were holding up go live.\"],\n], [16*mm, 158*mm])\n\nst.append(PageBreak())\n\n# ============================ PAGE 2 ============================\np(\"What the hour will look like\", H1)\np(\"Kristian shares his screen. You share nothing. Roughly: Kristian speaks half, Kim forty percent, you ten.\", SUB)\n\nsec(\"The running order\")\nbox([\n [\"0 to 20 min\", \"Chloe retest. Kristian walks through the seven things Kim caught on Friday and \"\n \"shows they are fixed. Kim will be testing him hard. Say nothing here unless asked.\"],\n [\"20 to 40 min\", \"The app walkthrough. app.thedogsspotga.com, the 21 July build. He demonstrates \"\n \"features against the contract and the ChangeLog. This is the part you need to watch \"\n \"closely, because this is what you inherit.\"],\n [\"40 to 50 min\", \"The punch list. Anything still broken gets written down for correction and retest.\"],\n [\"50 to 60 min\", \"Handover talk. Documentation, operating guide, runbook, credentials, GitHub, \"\n \"Supabase, Railway. This is your slot. Ask your questions here.\"],\n], [22*mm, 152*mm])\n\nsec(\"The seven Chloe faults, so you understand what you are watching\")\np(\"All four calls were the same customer, George Fitzgerald, plus one first time boarder, Monique Burnett.\")\nbl([\n \"Chloe offered training program appointments to a man who just wanted his dog looked after for the day.\",\n \"Four separate times she told a caller \\\"we have assigned one of our team members to get back to you\\\" \"\n \"and no task, text or notification was ever created. Nobody was assigned. Nobody knew.\",\n \"Monique's boarding drop off was created correctly, then her pickup was created as a Pup Talk by \"\n \"mistake, and Chloe told her the stay was confirmed anyway.\",\n \"The staff review task that is supposed to fire for a first time boarder never fired.\",\n \"Chloe must not confirm a stay unless both the drop off and the pickup really exist.\",\n \"Chloe must not say a handoff happened unless it happened.\",\n \"The retry and rollback path described in his own document has to be shown working.\",\n])\np(\"Not his fault, and Kim has said so in writing: Chloe refusing a 9:30am change was a four hour minimum \"\n \"notice rule on the calendar. Kim changed it herself to fifteen minutes.\", NOTE)\n\nsec(\"What Kristian has already claimed in writing, so you can spot a change of story\")\nbl([\n \"The app is live, running the 21 July build, but still deployed in his accounts, not Kim's. \"\n \"Transfer happens after QA.\",\n \"GoHighLevel owns the booking link, the calendars, the appointments and the automations. His app is \"\n \"the customer facing portal on top of that.\",\n \"23 approved calendars, and he states none have been renamed, archived, duplicated or added.\",\n \"His app writes into GoHighLevel: contacts, appointments, opportunities, tags, notes, custom fields, \"\n \"appointment statuses and workflows. Underline that one. It is the same data your reporting reads.\",\n \"Chloe is configured directly in GoHighLevel and is separate from his app's code.\",\n])\n\nst.append(PageBreak())\n\n# ============================ PAGE 3 ============================\np(\"What they will ask you, and exactly what to say\", H1)\np(\"Every answer below is true today. You are not memorising a script, you are being handed the facts.\", SUB)\n\nsec(\"From Kristian\")\nqa(\"\\\"Have you made any changes to the account?\\\"\",\n \"\\\"No. Nothing in the application, the calendar mappings, the workflows or Chloe. My side has been \"\n \"reporting, ad tracking and the follow up messages, which sit separately.\\\"\",\n \"True. The freeze has been kept. Nothing you built touches his configuration.\")\nqa(\"\\\"What access do you have?\\\"\",\n \"\\\"Kim set me up with a private integration key so the reporting can read the account. It reads, it \"\n \"does not reconfigure anything.\\\"\")\nqa(\"\\\"What are you planning to change after handover?\\\"\",\n \"\\\"Nothing until your handover is documented and I have read it. After that I will come back to Kim \"\n \"with a plan rather than start changing things.\\\"\")\n\nsec(\"From Kim\")\nqa(\"\\\"Amir, does this affect your tracking?\\\"\",\n \"\\\"It might. What I need to know is what the app writes into the CRM and when, because my reporting \"\n \"reads the same records. That is one of my questions for tonight.\\\"\")\nqa(\"\\\"Amir, can you fix that?\\\"\",\n \"\\\"I can once it is mine. Tonight it is still Kristian's to correct, and I do not want to touch it \"\n \"while you are still testing his work, or neither of you will know what changed.\\\"\",\n \"This is the single most likely trap. Do not take on Chloe work tonight. It is not yours yet and \"\n \"fixing it would wreck the QA baseline she is trying to establish.\")\nqa(\"\\\"When will my things be done?\\\"\",\n \"\\\"Monday: the list that stopped loading, your domain lines, and the corrected numbers. Tuesday: the \"\n \"review workflows and the message overlap. The tag cleanup, the Free Training Day rebuild and your two \"\n \"calendars all sit inside the freeze, so they go the day after it lifts, and that is partly what tonight \"\n \"decides. The Pups Club unsubscribe I can do either way.\\\"\",\n \"Do not promise Wednesday for the tag cleanup or the Free Training Day rebuild. Both are workflow \"\n \"changes and both are frozen. Putting the delay on the freeze rather than on you is also just true.\")\nqa(\"\\\"What about the two calendars I asked for?\\\"\",\n \"\\\"That is a question for both of you. Creating calendars is exactly what the freeze covers, and \"\n \"Kristian has told you no calendars have been added since his reconciliation. Tell me the freeze does \"\n \"not apply to those two and they are built tomorrow.\\\"\",\n \"Getting this answered in front of both of them is one of your five goals. Half an hour of work is \"\n \"sitting behind a yes.\")\n\nsec(\"If you do not know, say one of these. Never bluff.\")\np(\"Not knowing is completely normal for the person who has not built it. Bluffing is the only thing that \"\n \"would actually damage you tonight.\")\nbl([\n \"\\\"I do not want to guess at that. Let me check it properly and come back to you today.\\\"\",\n \"\\\"That is Kristian's side until handover, so I would rather he answered it than me speculating.\\\"\",\n \"\\\"I have not looked at that yet, so I do not have an answer I would stand behind.\\\"\",\n \"\\\"Can you show me what you are seeing?\\\" — buys you a minute and usually answers the question for you.\",\n \"\\\"Let me write that down and come back to you on it.\\\" Then actually write it down.\",\n])\np(\"If a technical question goes over your head entirely: \\\"Say that back to me in terms of what the \"\n \"customer experiences, and I will tell you whether it touches my side.\\\" That is a senior move, not \"\n \"a dodge, and it works every time.\")\n\nst.append(PageBreak())\np(\"Her open list, and what the freeze blocks\", H1)\np(\"If she asks when things will be done, this is the page. Half of it is waiting on tonight.\", SUB)\nbox([\n [\"The list that stopped loading\", \"She screenshotted her contact list dying mid scroll on 6 Aug, and \"\n \"separately said her page shows times but no dates. Never reproduced. The oldest thing outstanding. \"\n \"Not frozen. Monday.\"],\n [\"The four domain lines\", \"Four DNS records for Wix so her follow up emails send from thedogsspotga.com \"\n \"instead of a shared address. They do not exist yet because no sending domain is set up in her CRM. \"\n \"Not frozen. Monday.\"],\n [\"Free Training Day pick up calendar\", \"Her words: 30 minute appointments, bookable from 3:30pm with the \"\n \"last start at 4:30 so everything finishes by 5pm, with the usual appointment workflows. Twenty minutes \"\n \"of work. FROZEN.\"],\n [\"Second Pup Talk calendar\", \"Her words: a copy of the existing one under a different name, so Candice can \"\n \"book a customer straight onto a trainer's Pup Talk and the team can tell at a glance whose call it is. \"\n \"Ten minutes of work. FROZEN.\"],\n [\"Tag cleanup\", \"Remove tags not in use and ones not attached to a real customer. She also asked to track \"\n \"when a tag is applied, which her CRM does not record, so that half needs building. FROZEN.\"],\n [\"Free Training Day workflow\", \"The one that chased four people who had already booked. She built it \"\n \"herself and is open to a rebuild, with her watching. FROZEN.\"],\n [\"Review workflows\", \"Open both and settle whether her customers are being asked for a review twice. \"\n \"Reading only, not frozen. Tuesday.\"],\n [\"Message overlap\", \"Five no sale and tips sequences plus two auto responders. Confirm nothing double \"\n \"fires. Reading only, not frozen. Tuesday.\"],\n [\"Pups Club unsubscribe\", \"Her words: a way for subscription members to unsubscribe themselves. \"\n \"Doable either way.\"],\n [\"The switch on\", \"Fifteen minutes with her watching. Tagging on, new messages on, old workflow off. \"\n \"Waiting only on her picking a moment.\"],\n], [40*mm, 134*mm])\n\nst.append(PageBreak())\n\n# ============================ PAGE 4 ============================\np(\"What you must come away with\", H1)\np(\"If you get these five, the call was a success regardless of how it goes for Kristian.\", SUB)\n\nsec(\"Your five\")\nbox([\n [\"1\", \"Say the boundary out loud. \\\"Reporting, ads, tracking and the follow up messages are mine \"\n \"and carry on. The app, the calendars, the workflows and Chloe I am not touching until your \"\n \"handover is documented.\\\" Say this early. It makes you the professional in the room.\"],\n [\"2\", \"What does the app write into the CRM, and when? He listed contacts, appointments, \"\n \"opportunities, tags, notes and custom fields. Get the timing, so his writes and mine do not \"\n \"overwrite each other.\"],\n [\"3\", \"Does the app set opportunity value or move pipeline stages? Kim asked you today whether \"\n \"reporting depends on things being marked Won. If his app touches values or stages, your answer \"\n \"to her changes. This one is worth more than it sounds.\"],\n [\"4\", \"What exactly do I receive at handover, and on what date? Documentation, operating guide, \"\n \"runbook, credential sheet, GitHub, Supabase, Railway. Ask for a date, not a stage.\"],\n [\"5\", \"Do the two calendars fall under the freeze? Ask both of them together, get one answer.\"],\n], [8*mm, 166*mm])\n\nsec(\"Do not do these\")\nbl([\n \"Do not offer to fix anything of Chloe's tonight. Not yours yet, and it destroys Kim's clean test.\",\n \"Do not pile on about his failures. Kim is doing that thoroughly and it is her job, not yours. \"\n \"You come out of this better by being the calm one. He may also be the person you have to work with \"\n \"for another month.\",\n \"Do not promise a date for anything you have not scoped. \\\"I will come back to you with a date \"\n \"tomorrow\\\" is a complete answer.\",\n \"Do not raise the access key issue on this call. That is between you and Kim, and not in front \"\n \"of an outgoing contractor.\",\n \"Do not discuss money, yours or his.\",\n])\n\nsec(\"Numbers in your pocket, if you are asked how your side is doing\")\nbox([\n [\"Ad spend\", \"$718.98 last week. Facebook $554.98, Google $164.00.\"],\n [\"Cost per lead\", \"$4.11 overall. Best campaign $4.63, worst $10.87.\"],\n [\"New inquiries\", \"175 last week, down 22 on the week before.\"],\n [\"Facebook tracking\", \"Fixed today. The permission was missing since the connection was first built. \"\n \"The page now reads spend live from Meta.\"],\n [\"Follow up system\", \"Built, tested, running in practice mode. Has never messaged a real customer. \"\n \"Fifteen minutes from live once Kim picks a moment.\"],\n [\"The honest gap\", \"Revenue and ROAS do not work yet, because payment amounts never land on the \"\n \"booking record. That is the next build.\"],\n], [30*mm, 144*mm])\n\nsec(\"Last thing\")\np(\"You have been doing this properly. This week you caught your own mistake before the client did and \"\n \"corrected it inside twelve hours, which is more than the other contractor on this call can say about \"\n \"a four month overrun. Turn up, listen, ask your five, and write things down. That is the entire job \"\n \"tonight.\")\n\nSimpleDocTemplate(OUT, pagesize=A4, leftMargin=18*mm, rightMargin=18*mm, topMargin=14*mm,\n bottomMargin=12*mm, title=\"The Dogs Spot, call blueprint, 9 August\").build(st)\nprint(\"wrote\", OUT)\n\n\n=====FILE scripts/build.mjs =====\n// THE BUILD. engine/*.ts -> build/*.js, so the .mjs suites can import the same code the val runs.\n//\n// This file exists because the mapping used to live in my head and in shell history. A container\n// reclaim took the shell history with it. Anything a rebuild depends on is written down here.\n//\n// WHY IT TRANSPILES RATHER THAN BUNDLES. val.town runs seventeen separate files that import each\n// other, so at runtime there is exactly ONE copy of each module. A bundle per entry point gives\n// each entry its own private copy of everything below it: fill in a story slot and the engine's\n// copy would change while the story module's copy would not, and a test comparing the two would\n// pass on a system that is actually broken. So: every engine file is transpiled one-to-one, the\n// \".ts\" in each import specifier is rewritten to \".js\", and the friendly names the tests import\n// (build/engine.js, build/taper.js, build/stories.js) are thin re-export aliases onto that graph.\n// [was: `esbuild engine/puppy_path_v1.1.ts --outfile=build/engine.js` typed by hand, per file,\n// with --bundle on some and not others. A clean rebuild from source produced a build/ that\n// could not even be imported. The committed build/ had drifted from the source it came from.]\n//\n// Usage:\n// node scripts/build.mjs # engine/ -> build/\n// node scripts/build.mjs --src A --out B # build a copy of the tree somewhere else\nimport { spawnSync } from \"node:child_process\";\nimport { mkdirSync, existsSync, readdirSync, readFileSync, writeFileSync, rmSync } from \"node:fs\";\nimport { join, dirname, resolve, basename } from \"node:path\";\nimport { fileURLToPath } from \"node:url\";\n\nconst ROOT = resolve(dirname(fileURLToPath(import.meta.url)), \"..\");\n\n// Friendly name the tests import -> the engine source file behind it.\nexport const ALIASES = {\n engine: \"puppy_path_v1.1\",\n taper: \"taper-messages\",\n stories: \"kim-stories\",\n messages: \"puppy-messages\",\n};\n// Aliases that also need the source's default export forwarded.\nconst ALIAS_HAS_DEFAULT = new Set([\"engine\"]);\n\nconst arg = (flag, fallback) => {\n const i = process.argv.indexOf(flag);\n return i > -1 && process.argv[i + 1] ? process.argv[i + 1] : fallback;\n};\n\nexport function build({ src = join(ROOT, \"engine\"), out = join(ROOT, \"build\"), quiet = false } = {}) {\n const failures = [];\n if (!existsSync(src)) return [`source folder ${src} does not exist`];\n\n const sources = readdirSync(src).filter((f) => f.endsWith(\".ts\"));\n if (!sources.length) return [`no .ts files in ${src}: a build that builds nothing is not a build`];\n\n mkdirSync(out, { recursive: true });\n // Clear stale artifacts so a deleted source cannot leave a ghost module behind that tests import.\n for (const f of readdirSync(out)) if (f.endsWith(\".js\")) rmSync(join(out, f), { force: true });\n\n // 1. Transpile one-to-one. No bundling: the module graph is the point.\n const r = spawnSync(\"npx\", [\n \"--yes\", \"esbuild\",\n ...sources.map((f) => join(src, f)),\n \"--format=esm\",\n `--outdir=${out}`,\n \"--log-level=warning\",\n ], { encoding: \"utf8\" });\n if (r.status !== 0) return [`esbuild: ${(r.stderr || r.stdout || \"\").trim().slice(0, 800)}`];\n\n // 2. Rewrite import specifiers: \"./foo.ts\" -> \"./foo.js\". esbuild leaves them alone when it is\n // not bundling, and node will not resolve a .ts specifier.\n let rewritten = 0;\n for (const f of readdirSync(out).filter((x) => x.endsWith(\".js\"))) {\n const p = join(out, f);\n const before = readFileSync(p, \"utf8\");\n const after = before.replace(/(from\\s*[\"'])(\\.\\.?\\/[^\"']+?)\\.ts([\"'])/g, \"$1$2.js$3\");\n if (after !== before) { writeFileSync(p, after); rewritten++; }\n }\n\n // 3. Friendly-name aliases. Re-exports, not copies, so there is still one module underneath.\n for (const [alias, source] of Object.entries(ALIASES)) {\n if (!existsSync(join(out, `${source}.js`))) { failures.push(`alias ${alias}: ${source}.js was not built`); continue; }\n const lines = [\n `// Generated by scripts/build.mjs. Re-export, not a copy: one module underneath.`,\n `export * from \"./${source}.js\";`,\n ];\n if (ALIAS_HAS_DEFAULT.has(alias)) lines.push(`export { default } from \"./${source}.js\";`);\n writeFileSync(join(out, `${alias}.js`), lines.join(\"\\n\") + \"\\n\");\n }\n\n if (!quiet) {\n console.log(`transpiled ${sources.length} engine files -> ${out}`);\n console.log(`rewrote .ts import specifiers in ${rewritten} files`);\n console.log(`aliases: ${Object.entries(ALIASES).map(([a, s]) => `${a}.js -> ${s}.js`).join(\", \")}`);\n }\n return failures;\n}\n\nif (import.meta.url === `file://${process.argv[1]}`) {\n const failures = build({ src: arg(\"--src\", join(ROOT, \"engine\")), out: arg(\"--out\", join(ROOT, \"build\")) });\n if (failures.length) { console.log(\"\\nBUILD FAILED:\\n\" + failures.join(\"\\n\")); process.exit(1); }\n console.log(\"\\nbuild ok\");\n}\n\n\n=====FILE scripts/bundle.mjs =====\n// THE BUNDLE. Everything that is not already on the val, in one restorable text file.\n//\n// WHY. The working container was reclaimed mid-session on 4 August and took the test suite, the\n// build script and the PDF generator with it. The engine survived only because val.town happened\n// to hold a complete copy. Nothing else had a second home. This gives the rest of the project one.\n//\n// The bundle is plain text with file markers, not an archive, for three reasons: it can be read by\n// a human who has lost everything else, it survives being pasted through a chat window, and it can\n// live on the val as an inert `file` next to the code it tests.\n//\n// Restore, from nothing, needing only node:\n// node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(\"BUNDLE.txt\",\"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$/,\"\"))}'\n//\n// Usage: node scripts/bundle.mjs [--out handover/SOURCE-BUNDLE.txt]\nimport { readFileSync, writeFileSync, readdirSync, statSync } from \"node:fs\";\nimport { createHash } from \"node:crypto\";\nimport { join, dirname, resolve, relative } from \"node:path\";\nimport { fileURLToPath } from \"node:url\";\n\nconst ROOT = resolve(dirname(fileURLToPath(import.meta.url)), \"..\");\n\n// engine/ is deliberately absent: the val holds it, verified file by file by scripts/deploy.mjs.\n// Everything here is the part that has no other home.\nconst INCLUDE = [\n { dir: \"tests\", match: /\\.(mjs|ts|json)$/ }, // .json since 9 Aug: tests/fixtures/ is source, not pulled data\n { dir: \"scripts\", match: /\\.(mjs|py)$/ },\n // The watchdog is a SEPARATE val, so scripts/deploy.mjs --check does not cover it and a reclaim\n // leaves no local copy. Its own val is a real second home, but the bundle should hold everything\n // that is not in the main val, and until now it quietly did not.\n { dir: \"watchdog\", match: /\\.ts$/ },\n];\nconst EXTRA = [\n // THE RESUME FILE FIRST. It is the only thing that stops the next session starting from scratch,\n // and on 7 August it would have been the single most valuable file to have had in the bundle.\n // AWAITING-AMIR is the ONLY channel for anything needing his approval, and it used to live only\n // in /mnt/user-data/outputs, which does not survive a container reclaim. A pending draft to the\n // client is not a derived artifact; losing it loses the work. Bundled since 9 Aug.\n \"handover/AWAITING-AMIR.md\",\n // HANDOFF.md IS AT THE REPO ROOT AND NOWHERE ELSE. On 9 Aug it briefly existed twice, at the root\n // and in handover/, and the bundle carried the handover/ one. A cold read caught it: the backup\n // held a THREE COMMIT OLD handoff whose §13 told the next session to fetch 13 of the 14 parts.\n // A backup of a stale copy of the recovery instructions is the worst possible failure here.\n // The guard below refuses to write a bundle while a second copy exists.\n \"HANDOFF.md\",\n // QUEUE.md is what §1 tells a new session to open after HANDOFF. It was not in the bundle, so a\n // reclaim destroyed the one file the handoff points at. MINED-*.md are the only receipts behind\n // the commercials in §3, including the Upwork contract number. money-page.html is the SOURCE of\n // Monday's client deliverable, and \"put the generator in the repo\" is useless when the repo is\n // not the durable thing. All four bundled since 9 Aug.\n \"QUEUE.md\",\n \"MINED-OLD-TREES.md\",\n \"MINED-HANDOVER.md\",\n \"reports/money-page.html\",\n \"reports/square-revenue-explainer.html\",\n \"BOARD-10-AUG.md\",\n \"AMIR-DO-THIS.md\",\n \"handover/KIM-MESSAGE-10-AUG-FINAL.txt\",\n \"BUILD-PLAN-10-AGENTS.md\",\n \"handover/RESUME.md\",\n \"handover/REGISTER-AUG7.md\",\n \"handover/SWEEP-7-AUG.md\",\n \"handover/AUTOPILOT.md\",\n \"handover/DRAFTS-WHILE-AWAY.md\",\n \"handover/MESSAGE-TO-KIM-7-AUG.txt\",\n \"reports/Friday-Report-7-Aug-2026.html\",\n \"handover/PLAN-TO-FINISH.md\",\n \"handover/SEND-TO-KIM.txt\",\n \"handover/REPLY-AUG5.txt\",\n \"handover/REGISTER-AUG5.md\",\n \"handover/AMIR_TODO.md\",\n \"handover/NURTURE-REVIEW-FOR-KIM.md\",\n \"handover/DEPOSIT-SPEC.md\",\n];\n// NOT INCLUDED, on purpose: the PDFs and the spreadsheet. They are DERIVED, and backing up a\n// derived artifact backs up the wrong thing. What has to survive is the recipe, and after the\n// 5 August reclaim it turned out the recipe did not — scripts/make_pdf.py reads an input shape it\n// never documented. scripts/make-pdfs.mjs is that missing step, and it is in the bundle.\n\nconst arg = (f, d) => { const i = process.argv.indexOf(f); return i > -1 && process.argv[i + 1] ? process.argv[i + 1] : d; };\nconst sha = (s) => createHash(\"sha256\").update(s).digest(\"hex\");\n\n// RECURSIVE since 9 Aug 2026. This used to read one level only, so tests/fixtures/ was skipped in\n// silence: the fixture the money suite reads was never in the bundle, and a tree restored after the\n// container loss that evening came back RED for a file the bundle had quietly declined to carry.\n// A backup that drops a directory without saying so is worse than one that fails loudly.\nconst files = [];\nconst walk = (abs, match, out) => {\n for (const f of readdirSync(abs).sort()) {\n const p = join(abs, f);\n if (statSync(p).isDirectory()) walk(p, match, out);\n else if (match.test(f)) out.push(relative(ROOT, p));\n }\n};\nfor (const { dir, match } of INCLUDE) walk(join(ROOT, dir), match, files);\nfor (const f of EXTRA) { try { statSync(join(ROOT, f)); files.push(f); } catch { /* not fatal */ } }\n\nif (!files.length) { console.log(\"BUNDLE FAILED: nothing to bundle. A bundle of nothing is worse than none.\"); process.exit(1); }\n\n// ONE HANDOFF, AT THE ROOT. See the note in EXTRA. Two copies means the bundle silently backs up\n// whichever one this list happens to name, and the other is the one being read and edited.\ntry {\n statSync(join(ROOT, \"handover/HANDOFF.md\"));\n console.log(\"BUNDLE FAILED: handover/HANDOFF.md exists. There must be exactly ONE handoff, at the repo root.\");\n console.log(\"On 9 Aug the duplicate meant the backup held a stale handoff that told the next session to fetch 13 of 14 parts.\");\n process.exit(1);\n} catch (e) { if (e?.code !== \"ENOENT\") throw e; }\n// And the thing that must never silently drop out again.\nif (!files.includes(\"HANDOFF.md\")) { console.log(\"BUNDLE FAILED: HANDOFF.md is not in the bundle.\"); process.exit(1); }\n\nconst MAX_PART = 78_000;\n// A SINGLE FILE CAN NOW EXCEED A WHOLE PART. negative-controls.mjs passed 80,000 characters on\n// 6 August — the val's own per-file ceiling — and the packer, which only ever splits BETWEEN\n// files, produced a part the val refused. A backup that cannot be written is not a backup, and\n// this is the file the whole disaster-recovery story rests on. Oversized files are cut into\n// numbered CHUNK records and rejoined on restore, in order.\nconst CHUNK = 60_000;\n\n// A file bigger than CHUNK becomes several records named \"#1\", \"#2\", ... which the\n// restore rejoins in order. Everything else is unchanged, so old parts and new parts read the same.\nconst records = [];\nconst manifest = [];\nfor (const f of files) {\n const content = readFileSync(join(ROOT, f), \"utf8\");\n manifest.push(` ${f.padEnd(38)} ${String(content.length).padStart(7)} bytes ${sha(content).slice(0, 12)}`);\n if (content.length <= CHUNK) { records.push({ name: f, body: content }); continue; }\n const n = Math.ceil(content.length / CHUNK);\n for (let i = 0; i < n; i++) records.push({ name: `${f}#${i + 1}`, body: content.slice(i * CHUNK, (i + 1) * CHUNK) });\n console.log(` (${f} is ${content.length.toLocaleString()} chars, split across ${n} records)`);\n}\nconst parts = records.map((r) => `\\n=====FILE ${r.name} =====\\n${r.body}`);\nconst recNames = records.map((r) => r.name);\n\n// val.town caps EVERY file at 80,000 characters, not just main.ts. So the bundle ships in parts,\n// split at FILE boundaries: each part is a complete, independently restorable bundle of whole\n// files. Nothing has to be concatenated in the right order, and losing one part costs you the\n// files in that part rather than the whole archive.\n\n\nconst header = (partNo, partCount, partFiles) => [\n \"THE DOGS SPOT — SOURCE BUNDLE\" + (partCount > 1 ? ` (part ${partNo} of ${partCount})` : \"\"),\n \"\",\n \"Everything in this project that does not already live on val.town. The engine is NOT here:\",\n \"the engine files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff (23 of them on 9 Aug 2026; list the val,\",\n \"do not assume) are verified file by file by\",\n \"scripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\",\n \"\",\n \"RESTORE (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 \"\",\n \"A record named #1, #2, ... is one FILE cut into pieces: concatenate them in order, then\",\n \"strip one trailing newline from the last. scripts/restore.mjs does this for you.\",\n \"\",\n \"Each part is complete in itself: whole files only, no reassembly, any order.\",\n \"\",\n \"Then: node scripts/deploy.mjs --check (pulls nothing, proves the val matches)\",\n \" node scripts/build.mjs (needs engine/ back from the val first)\",\n \" node tests/run-all.mjs\",\n \" node tests/negative-controls.mjs (proves the suite above can actually fail)\",\n \"\",\n `IN THIS PART (${partFiles.length} of ${files.length} files)`,\n ...partFiles.map((f) => manifest[files.indexOf(f)]),\n \"\",\n \"=\".repeat(96),\n].join(\"\\n\");\n\n// Pack files into parts, largest-first, each part under the cap.\nconst sizeOf = (i) => parts[i].length;\nconst packs = [];\nlet cur = [];\nlet curLen = 2000; // rough header allowance\nrecNames.forEach((f, i) => {\n if (cur.length && curLen + sizeOf(i) > MAX_PART) { packs.push(cur); cur = []; curLen = 2000; }\n cur.push(i); curLen += sizeOf(i);\n});\nif (cur.length) packs.push(cur);\n\nconst outBase = arg(\"--out\", join(ROOT, \"handover/SOURCE-BUNDLE\")).replace(/\\.txt$/, \"\");\nconst written = [];\npacks.forEach((idxs, n) => {\n const partFiles = idxs.map((i) => recNames[i]);\n const body = header(n + 1, packs.length, partFiles) + idxs.map((i) => parts[i]).join(\"\\n\") + \"\\n\";\n const out = packs.length === 1 ? `${outBase}.txt` : `${outBase}.part${n + 1}.txt`;\n writeFileSync(out, body);\n written.push({ out, body, partFiles });\n console.log(`${out} ${body.length.toLocaleString()} chars ${partFiles.length} files`);\n});\n\n// Prove the bundle round-trips before claiming it is a backup. A backup that has never been\n// restored is a hope, not a backup.\nconst roundTrip = new Map();\nfor (const { body } of written) {\n for (const s of body.split(\"\\n=====FILE \").slice(1)) {\n const i = s.indexOf(\" =====\\n\");\n const name = s.slice(0, i);\n const chunk = s.slice(i + 7);\n const m = /^(.*)#(\\d+)$/.exec(name);\n // ONE trailing newline comes from the join between records, whatever the chunk itself ends\n // with, so stripping exactly one recovers the chunk byte-for-byte.\n if (m) roundTrip.set(m[1], (roundTrip.get(m[1]) ?? \"\") + chunk.replace(/\\n$/, \"\"));\n else roundTrip.set(name, chunk.replace(/\\n$/, \"\"));\n }\n}\nconst broken = [];\nfor (const f of files) {\n const original = readFileSync(join(ROOT, f), \"utf8\");\n const restored = roundTrip.get(f);\n if (restored == null) broken.push(`${f}: missing from every part`);\n else if (sha(restored) !== sha(original)) broken.push(`${f}: does not round-trip (${sha(original).slice(0, 8)} -> ${sha(restored).slice(0, 8)})`);\n}\nconst over = written.filter((w) => w.body.length > 80_000).map((w) => w.out);\nif (over.length) { console.log(`\\nOVER THE 80,000 CHARACTER VAL LIMIT: ${over.join(\", \")}`); process.exit(1); }\nif (broken.length) { console.log(\"\\nROUND-TRIP FAILED, this is not a backup:\\n\" + broken.join(\"\\n\")); process.exit(1); }\nconsole.log(`round-trip verified: all ${files.length} files restore byte-for-byte across ${packs.length} part(s)`);\n\n",[361],"ed9b97d7-005d-4723-80e4-dbb4be8d260c","SOURCE-BUNDLE.part8.txt","7c8dcd00-91bc-11f1-8e89-1607ee4eb77e",685,["D",1786387548911],28,"THE DOGS SPOT — SOURCE BUNDLE (part 8 of 17)\n\nEverything in this project that does not already live on val.town. The engine is NOT here:\nthe engine files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff (23 of them on 9 Aug 2026; list the val,\ndo not assume) are verified file by file by\nscripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\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/deploy.mjs --check (pulls nothing, proves the val matches)\n node scripts/build.mjs (needs engine/ back from the val first)\n node tests/run-all.mjs\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (4 of 61 files)\n\n tests/registry.test.mjs 4947 bytes 9cfa5044cbd0\n tests/render.test.mjs 2941 bytes ea24d897a12f\n tests/report-logic.test.mjs 8329 bytes 505cbbf5e568\n\n================================================================================================\n=====FILE tests/negative-controls.mjs#2 =====\n cash or taken over the phone does not reach the card system, so it will not show here.\";',\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H60 Kim is told where else to look\",\n },\n {\n name: \"the card stops saying the deposit is per dog\",\n file: \"engine/dashboard.ts\",\n find: \"$50 per dog, so a three-dog stay is $150.\",\n replace: \"Counted as one $50 deposit per stay.\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.12 the card says the deposit is per dog\",\n },\n {\n name: \"the headline names a flat $50 above rows that owe $50 a dog\",\n file: \"engine/holiday-deposits.ts\",\n find: \"we cannot find a card payment matching the deposit for ${n === 1 ? \\\"it\\\" : \\\"them\\\"}.`);\",\n replace: \"we cannot find a $50.00 card payment for ${n === 1 ? \\\"it\\\" : \\\"them\\\"}.`);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H61 the headline never names an amount\",\n },\n {\n name: \"looking at the deposit list resets the refresh clock\",\n file: \"engine/deposits.ts\",\n // If a check writes the attempt stamp, the check becomes the reason the refresh never fires.\n find: \" const attempt: any = await b.getJSON(ATTEMPT_KEY).catch(() => null);\",\n replace: \" const attempt: any = await b.getJSON(ATTEMPT_KEY).catch(() => null);\\n await b.setJSON(ATTEMPT_KEY, { at: new Date().toISOString() }).catch(() => {});\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D33 reading the list reports when\",\n },\n {\n name: \"the read route stops reporting when the refresh last tried\",\n file: \"engine/deposits.ts\",\n find: \" lastAttemptAt: attempt?.at ?? null,\",\n replace: \" lastAttemptedAt: attempt?.at ?? null,\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D33 reading the list reports when\",\n },\n {\n name: \"the allocator debits one $50 while the rule clears on a lump sum\",\n file: \"engine/holiday-deposits.ts\",\n // The money bug's fourth door: a two-dog stay settled by $100 debited nothing at all, and the\n // same $100 settled the customer's next stay. 29% of generated multi-stay customers hit it.\n find: \" for (const p of qualifyingPayments(s, available)) spent.add(p.id);\",\n replace: \" const c = collapseSameMoney(paymentsNearStay(s, available)).kept.find((p) => p.amount === DEPOSIT);\\n if (c) spent.add(c.id);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H62 one payment cannot settle two multi-dog\",\n },\n {\n name: \"what settles a stay and what gets debited go back to being two different rules\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const exact = qualifyingPayments(stay, payments);\",\n replace: \" const exact = near.filter((p) => p.amount === DEPOSIT).slice(0, dogs);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H58 the deposit is $50 PER DOG\",\n },\n {\n name: \"the dogs charged for are counted from the names again\",\n file: \"engine/holiday-deposits.ts\",\n find: \" return Math.max(1, stay.dogCount || stay.dogs.length || 1);\",\n replace: \" return Math.max(1, stay.dogs.length || 1);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H64 the amount charged and the dogs named\",\n },\n {\n name: \"three payment dates are chained together with ands\",\n file: \"engine/holiday-deposits.ts\",\n find: \" return `${items.slice(0, -1).join(\\\", \\\")} and ${items[items.length - 1]}`;\",\n replace: \" return items.join(\\\" and \\\");\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H65 three dates read as a list\",\n },\n {\n name: \"the headline has Kim owing money to her customers\",\n file: \"engine/holiday-deposits.ts\",\n find: \"we cannot find a card payment matching the deposit for ${n === 1 ? \\\"it\\\" : \\\"them\\\"}.`);\",\n replace: \"we cannot find a card payment matching what ${n === 1 ? \\\"it is\\\" : \\\"they are\\\"} owed.`);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H66 the headline says what is owed\",\n },\n {\n name: \"a $250 payment is read as five holiday deposits with no mention of training\",\n file: \"engine/holiday-deposits.ts\",\n find: \" if (due === TRAINING_DEPOSIT) return ` Worth an eye: $${TRAINING_DEPOSIT} is also what a training deposit costs, so this one payment could be either.`;\",\n replace: \" if (false) return \\\"\\\";\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H67 a $250 deposit is flagged\",\n },\n {\n name: \"the card shows two dog names beside a three-dog charge\",\n file: \"engine/dashboard.ts\",\n find: \" if (names.length < n) return `${names.join(\\\", \\\")} and ${n - names.length} more (${n} in total)`;\",\n replace: \" if (false) return \\\"\\\";\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.17 the Dogs column never contradicts\",\n },\n {\n name: \"the refresh stops recording which schedule started it\",\n file: \"engine/deposits.ts\",\n find: \" await b.setJSON(ATTEMPT_KEY, { at: new Date().toISOString(), source }).catch(() => {});\",\n replace: \" await b.setJSON(ATTEMPT_KEY, { at: new Date().toISOString() }).catch(() => {});\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D34 the refresh records WHICH schedule\",\n },\n {\n name: \"the second scheduled file collects on every tick again\",\n file: \"engine/deposits-cron.ts\",\n // [was: deleting the `if (!g.ran) return`, which stopped being the gate when the gate moved\n // INSIDE refreshIfDue. The fault that matters now is bypassing the shared step entirely.]\n find: \" const g = await refreshIfDue(() => blob.getJSON(ATTEMPT_KEY) as any, () => runCollection(false, \\\"deposits-cron\\\"), Date.now());\",\n replace: \" const g = { ran: true, why: \\\"collected\\\" }; await runCollection(false, \\\"deposits-cron\\\");\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D35 the second scheduled file uses\",\n },\n {\n name: \"the settle rule stops collapsing duplicates, so a backfilled twin can settle a stay\",\n file: \"engine/holiday-deposits.ts\",\n // The OTHER copy of that line, inside qualifyingPayments. Both need guarding: one decides what\n // Kim reads, the other decides what gets spent.\n find: \" const near = [...collapseSameMoney(paymentsNearStay(stay, payments)).kept]\",\n replace: \" const near = [...paymentsNearStay(stay, payments)]\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H68 one $50 written twice\",\n },\n {\n name: \"a row denies a payment that is sitting in its own window\",\n file: \"engine/holiday-deposits.ts\",\n // 7.9% of generated rows said \"no card payment is on file around it at all\" with the payment\n // right there. Kim phones; the customer says \"I paid on the 20th\"; they did.\n find: \" const near = collapseSameMoney(paymentsNearStay(stay, opts.all ?? payments)).kept;\",\n replace: \" const near = collapseSameMoney(paymentsNearStay(stay, payments)).kept;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H69 a row never denies a payment\",\n },\n {\n name: \"money already counted against an earlier stay stops being explained\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const countedNote = counted.length\",\n replace: \" const countedNote = false && counted.length\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H69 a row never denies a payment\",\n },\n {\n name: \"three dogs paid for in one visit print the same date three times\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const uniq = [...new Set(days)];\",\n replace: \" const uniq = days;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H70 three dogs paid for in one visit\",\n },\n {\n name: \"only the $250 collision is flagged, not the likelier ones\",\n file: \"engine/holiday-deposits.ts\",\n find: \" if (due > DEPOSIT) return ` Worth an eye: one payment of this size could also be the boarding total\",\n replace: \" if (false) return ` Worth an eye: one payment of this size could also be the boarding total\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H71 a lump sum for several dogs\",\n },\n {\n name: \"the amount shown against a settled multi-dog stay is one dog's worth\",\n file: \"engine/holiday-deposits.ts\",\n find: \" return { stay, state: \\\"seen\\\", amountSeen: due,\",\n replace: \" return { stay, state: \\\"seen\\\", amountSeen: DEPOSIT,\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H72 the amount shown against a settled stay\",\n },\n {\n name: \"a row is labelled 'Not paid' on Kim's card\",\n file: \"engine/dashboard.ts\",\n // The most natural phrasing of the one thing this feature must never say, and the old ban\n // regex let it straight through.\n find: ' none_seen: { label: \"Worth a look\", color: WARN },',\n replace: ' none_seen: { label: \"Not paid\", color: CRIT },',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.4 the word unpaid\",\n },\n {\n name: \"the sentence saying this is not a list of people who owe her money is dropped\",\n file: \"engine/holiday-deposits.ts\",\n find: \"This is a shortlist to look at rather than a list of people who owe you.`);\",\n replace: \"This is a shortlist.`);\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.4 the word unpaid\",\n },\n {\n name: \"the card writes '1 dogs, names not recorded'\",\n file: \"engine/dashboard.ts\",\n find: ' if (!names.length) return `${n} ${n === 1 ? \"dog\" : \"dogs\"}, names not recorded`;',\n replace: ' if (!names.length) return `${n} dogs, names not recorded`;',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.18 the counts on the card\",\n },\n {\n name: \"a backfill record from months away is folded into a payment as the same money\",\n file: \"engine/holiday-deposits.ts\",\n // The money bug's fifth door: $50 is exactly the amount a repeat customer pays twice in a\n // year, so a November payment and a December till record were read as one, deleting a real\n // deposit and then telling Kim nothing was on file.\n find: \" if (p.kind === \\\"matched\\\" && directs.some((d) => d.amount === p.amount && withinDays(d.at, p.at, COLLAPSE_WINDOW_DAYS))) {\",\n replace: \" if (p.kind === \\\"matched\\\" && directs.some((d) => d.amount === p.amount)) {\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H74 a payment months away\",\n },\n {\n name: \"the date bound tightens past the one real pair on her account\",\n file: \"engine/holiday-deposits.ts\",\n find: \"export const COLLAPSE_WINDOW_DAYS = 21;\",\n replace: \"export const COLLAPSE_WINDOW_DAYS = 7;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H74 a payment months away\",\n },\n {\n name: \"the same payment is printed twice on one row, in contradictory terms\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const others = rest.filter((p) => !opts.alreadyCounted?.has(p.id));\",\n replace: \" const others = rest;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H75 money already counted appears once\",\n },\n {\n name: \"three taps on one day are printed as three identical lines\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const prev = byAmountAndDay.get(k);\",\n replace: \" const prev = undefined; byAmountAndDay.set(`${k}|${p.id}`, { amount: p.amount, day, n: 1 });\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H76 three taps on one day\",\n },\n {\n name: \"a row on Kim's card is relabelled 'No payment received'\",\n file: \"engine/dashboard.ts\",\n // One of four phrasings a ninth review walked straight past the word ban.\n find: ' none_seen: { label: \"Worth a look\", color: WARN },',\n replace: ' none_seen: { label: \"No payment received\", color: CRIT },',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.19 the card can only say\",\n },\n {\n name: \"the card prints a running total of what customers supposedly owe\",\n file: \"engine/dashboard.ts\",\n find: '
${windowLine(dep.windows)}',\n replace: '
These stays are short by $150.00 between them. ${windowLine(dep.windows)}',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.19 the card can only say\",\n },\n {\n name: \"the engine's hourly refresh is wrapped in a condition that never fires\",\n file: \"engine/puppy_path_v1.1.ts\",\n find: \" await dep.refreshIfDue(\",\n replace: \" if (Math.random() < 0) await dep.refreshIfDue(\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D30 the engine calls that rule\",\n },\n {\n name: \"the scheduled file collects a second time, outside the gate\",\n file: \"engine/deposits-cron.ts\",\n find: \" if (!g.ran) { console.log(`[deposits] ${g.why}`); return; }\",\n replace: \" await runCollection(false, \\\"deposits-cron\\\");\\n if (!g.ran) { console.log(`[deposits] ${g.why}`); return; }\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D35 the second scheduled file uses\",\n },\n {\n name: \"the row label is rendered from a ternary instead of the allowed set\",\n file: \"engine/dashboard.ts\",\n // The allow-list pinned the constant and not the page: the render site was free.\n find: \"${esc(shown(r).label)}\",\n replace: '${esc(r.state === \"seen\" ? \"Payment on file\" : \"Worth a look\")}',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.19 the card can only say\",\n },\n {\n name: \"the card grows a column of money nobody vouches for\",\n file: \"engine/dashboard.ts\",\n find: \"WhoStayDogsDeposit\",\n replace: \"WhoStayDogsDepositTo chase\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.19 the card can only say\",\n },\n {\n name: \"the engine's refresh is wrapped in a condition placed before the import\",\n file: \"engine/puppy_path_v1.1.ts\",\n // The exact bypass a tenth review used against the previous, statement-level pin.\n find: \" try {\\n const dep = await import(\\\"./deposits.ts\\\");\",\n replace: \" try {\\n if (Date.now() < 0) {\\n const dep = await import(\\\"./deposits.ts\\\");\",\n then: {\n find: \" } catch (e) { console.log(\\\"deposits refresh skipped\\\", String(e).slice(0, 120)); }\",\n replace: \" } } catch (e) { console.log(\\\"deposits refresh skipped\\\", String(e).slice(0, 120)); }\",\n },\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D30 the engine calls that rule\",\n },\n {\n name: \"the scheduled file aliases the collector and calls it outside the gate\",\n file: \"engine/deposits-cron.ts\",\n find: \" const g = await refreshIfDue(\",\n replace: \" const always = runCollection; await always(false, \\\"deposits-cron\\\");\\n const g = await refreshIfDue(\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D35 the second scheduled file uses\",\n },\n {\n name: \"the scheduled file's gate is handed a reader that is always empty\",\n file: \"engine/deposits-cron.ts\",\n find: \"() => blob.getJSON(ATTEMPT_KEY) as any\",\n replace: \"async () => null\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D35 the second scheduled file uses\",\n },\n {\n name: \"the plural headline goes back to 'what are owed on them'\",\n file: \"engine/holiday-deposits.ts\",\n find: \"we cannot find a card payment matching the deposit for ${n === 1 ? \\\"it\\\" : \\\"them\\\"}.`);\",\n replace: \"we cannot find a card payment matching what are owed on ${n === 1 ? \\\"it\\\" : \\\"them\\\"}.`);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H77 the plural headline is a sentence\",\n },\n {\n name: \"only one spelling of cancelled keeps a booking off the list\",\n file: \"engine/holiday-deposits.ts\",\n find: 'export const DEAD_STATUSES = [\"cancelled\", \"canceled\", \"noshow\", \"no-show\", \"no show\", \"invalid\"];',\n replace: 'export const DEAD_STATUSES = [\"cancelled\"];',\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H78 every way her CRM says a booking is dead\",\n },\n {\n name: \"the collapse bound is hardcoded next to the constant that documents it\",\n file: \"engine/holiday-deposits.ts\",\n find: \"withinDays(d.at, p.at, COLLAPSE_WINDOW_DAYS)\",\n replace: \"withinDays(d.at, p.at, 30)\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H79 the collapse bound is the constant\",\n },\n {\n name: \"two payments of the same size on the same day render identically\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const ofN = twinDay > 1 ? ` (one of ${twinDay} payments of that amount that day)` : \\\"\\\";\",\n replace: \" const ofN = \\\"\\\";\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H80 two payments of the same size\",\n },\n {\n name: \"a generated note tells Kim the customer still owes\",\n file: \"engine/holiday-deposits.ts\",\n // The accusation scan used to read hand-typed fixture notes, so this reached her page green.\n find: \"already been counted against ${counted.length === 1 ? \\\"an earlier stay\\\" : \\\"earlier stays\\\"} of theirs.`\",\n replace: \"already been counted against ${counted.length === 1 ? \\\"an earlier stay\\\" : \\\"earlier stays\\\"} of theirs, so they still owe this one.`\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.4 the word unpaid\",\n },\n {\n name: \"the display list is the collapsed one, so a folded payment vanishes off the row\",\n file: \"engine/holiday-deposits.ts\",\n // A customer who paid BOTH deposits, fourteen days apart, had her Thanksgiving row read\n // \"no card payment is on file around it at all\" — because the till record had been folded\n // against the December card payment and the row was shown the collapsed list.\n find: \" const st = statusFor(s, available, { all: payments, alreadyCounted: new Set(spent) });\",\n replace: \" const st = statusFor(s, available, { all: money, alreadyCounted: new Set(spent) });\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H82 a folded payment still shows on the row\",\n },\n {\n name: \"the card writes prose of its own into a row's note\",\n file: \"engine/dashboard.ts\",\n find: '${esc(r.note)}',\n replace: '${esc(r.note)} Those customers are still to pay.',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.20 the card renders a row\",\n },\n {\n name: \"the longest stay accepted drifts away from the constant that documents it\",\n file: \"engine/holiday-deposits.ts\",\n find: \"d <= shiftDays(s.day, MAX_STAY_DAYS)\",\n replace: \"d <= shiftDays(s.day, 60)\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H81 the longest stay accepted\",\n },\n {\n name: \"the same-day clause stops naming the day\",\n file: \"engine/holiday-deposits.ts\",\n find: \"` (one of ${twinDay} payments of that amount that day)`\",\n replace: \"` (one of ${twinDay} payments of that amount)`\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H80 two payments of the same size\",\n },\n {\n name: \"a row denies a match one clause before printing it\",\n file: \"engine/holiday-deposits.ts\",\n // The v2 bug's exact sentence, back in a different branch. 1.3% of rows.\n find: \" const why = blocked.length\",\n replace: \" const why = false && blocked.length\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H83 a row never denies a match\",\n },\n {\n name: \"the lump-sum advice names a number of payments the rule would refuse\",\n file: \"engine/holiday-deposits.ts\",\n find: \"${due / DEPOSIT} separate $${DEPOSIT} payments would be clearer.`;\",\n replace: \"Two or three separate $${DEPOSIT} payments would be clearer.`;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H84 the advice on a lump sum\",\n },\n {\n name: \"an accusation is added to the note cell, gated on a row state\",\n file: \"engine/dashboard.ts\",\n // The old allow-list only ever rendered `seen` rows, so any conditional was dead in its fixture.\n find: '${esc(r.note)}',\n replace: '${esc(r.note)}${r.state === \"none_seen\" ? \" They have skipped the deposit.\" : \"\"}',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.20 the card renders a row\",\n },\n {\n name: \"an accusation is added to the Who column\",\n file: \"engine/dashboard.ts\",\n find: \"`${escCell(who(r))}\",\n replace: \"`${escCell(who(r))} (owes)\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.20 the card renders a row\",\n },\n {\n name: \"an accusation is added to the Dogs column\",\n file: \"engine/dashboard.ts\",\n find: \"${escCell(dogsCell(r))}\",\n replace: \"${escCell(dogsCell(r))} (unpaid)\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.20 the card renders a row\",\n },\n {\n name: \"the staleness warning is turned into an accusation\",\n file: \"engine/dashboard.ts\",\n find: \"will still show here as not found, so check the date before you act on a name.\",\n replace: \"will still show here as having skipped it, so check the date before you act on a name.\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.20 the card renders a row\",\n },\n {\n name: \"the card synthesises a debt total that coincides with a row's own figure\",\n file: \"engine/dashboard.ts\",\n // The realistic wording, computed the way the card would really compute it — which is exactly\n // the form the old substring check could not see.\n find: '
${windowLine(dep.windows)}',\n replace: '
These stays are still short by $${rows.filter((r) => r.state === \"none_seen\" || r.state === \"partial\").reduce((n, r) => n + 50 * (r.dogCount || 1), 0).toFixed(2)} between them.
${windowLine(dep.windows)}',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.19 the card can only say\",\n },\n {\n name: \"a dog name out of the CRM reaches Kim's page unescaped\",\n file: \"engine/dashboard.ts\",\n find: \"${escCell(dogsCell(r))}\",\n replace: \"${dogsCell(r)}\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.7 a customer's name is escaped\",\n },\n {\n name: \"the footer stops naming the payment routes the card cannot see\",\n file: \"engine/dashboard.ts\",\n find: \"${esc(OTHER_ROUTES)} Only overnight boarding stays are counted here\",\n replace: \"Only overnight boarding stays are counted here\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.12 the card says the deposit is per dog\",\n },\n // ---- ROUND 14, 7 August. Every one of these is a fault that shipped green until this round. ----\n {\n name: \"the page renders an object as [object Object] again\",\n file: \"engine/dashboard.ts\",\n find: 'const text = (s: unknown) => (typeof s === \"string\" ? s : typeof s === \"number\" && Number.isFinite(s) ? String(s) : \"\");',\n replace: 'const text = (s: unknown) => String(s ?? \"\");',\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.21 a malformed stored list\",\n },\n {\n name: \"a bidi override in a customer name reaches the page and reorders the cell\",\n file: \"engine/dashboard.ts\",\n find: '.replace(/[\\\\u202A-\\\\u202E\\\\u2066-\\\\u2069\\\\u200E\\\\u200F\\\\u061C]/g, \"\")',\n replace: \"\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.25 a name typed by a stranger\",\n },\n {\n name: \"a name out of the booking form is rendered with no length cap\",\n file: \"engine/dashboard.ts\",\n find: \" return esc(raw.length > MAX_CELL ? `${raw.slice(0, MAX_CELL)}...` : raw);\",\n replace: \" return esc(raw);\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.25 a name typed by a stranger\",\n },\n {\n name: \"the length cap is put back on esc itself, truncating the card's own sentences\",\n file: \"engine/dashboard.ts\",\n find: \"const esc = (s: unknown) => text(s).replace(\",\n replace: \"const esc = (s: unknown) => text(s).slice(0, 120).replace(\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.4 the word unpaid\",\n },\n {\n name: \"the stored row list is spread without checking it is a list\",\n file: \"engine/dashboard.ts\",\n find: ' const rows = (Array.isArray(dep.rows) ? dep.rows : []).filter((r): r is DepositRow => !!r && typeof r === \"object\")',\n replace: \" const rows = [...(dep.rows ?? [])].filter((r): r is DepositRow => true)\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.21 a malformed stored list\",\n },\n {\n name: \"the row sort reads .day without checking it is a string\",\n file: \"engine/dashboard.ts\",\n find: \"|| day(a).localeCompare(day(b)));\",\n replace: \"|| a.day.localeCompare(b.day));\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.21 a malformed stored list\",\n },\n {\n name: \"the dogs cell filters a field that may not be an array\",\n file: \"engine/dashboard.ts\",\n find: ' const names = (Array.isArray(r.dogs) ? r.dogs : []).filter((d) => typeof d === \"string\" && d.trim());',\n replace: \" const names = ((r.dogs ?? []) as string[]).filter(Boolean);\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.21 a malformed stored list\",\n },\n {\n name: \"the windows line maps a field that may not be an array\",\n file: \"engine/dashboard.ts\",\n find: \" const ws = (Array.isArray(windows) ? windows : [])\",\n replace: \" const ws = ((windows ?? []) as any[])\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.21 a malformed stored list\",\n },\n {\n name: \"a list of unknown age is silently treated as fresh\",\n file: \"engine/dashboard.ts\",\n find: \" const stale = !Number.isFinite(ageH)\",\n replace: \" const stale = false && !Number.isFinite(ageH)\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.23 a list whose age cannot be read\",\n },\n {\n name: \"the headline is read back out of the blob instead of generated from the rows\",\n file: \"engine/dashboard.ts\",\n find: ' const sentence = depositSentence(rows.map((r) => ({ state: shown(r) === DEP_STATE.could_not_check ? \"could_not_check\" : r.state })), !!dep.feedDead);',\n replace: \" const sentence = dep.sentence;\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.22 the headline is generated\",\n },\n {\n name: \"an unreadable state gets a grey dot beside an orange label again\",\n file: \"engine/dashboard.ts\",\n find: \" const shown = (r: DepositRow) => DEP_STATE[r.state] ?? DEP_STATE.could_not_check;\",\n replace: ' const shown = (r: DepositRow) => ({ color: DEP_STATE[r.state]?.color ?? \"#6b7280\", label: DEP_STATE[r.state]?.label ?? \"Worth a look\" });',\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.24 a state this code does not recognise\",\n },\n {\n name: \"a row with no name renders as a blank settled row\",\n file: \"engine/dashboard.ts\",\n find: ' const who = (r: DepositRow) => (typeof r.name === \"string\" && r.name.trim() ? r.name : \"name not readable\");',\n replace: \" const who = (r: DepositRow) => r.name;\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.26 a row with no readable name\",\n },\n {\n name: \"an unreadable stored list is presented as an empty season\",\n file: \"engine/dashboard.ts\",\n find: \" if (dep.rows !== undefined && dep.rows !== null && !Array.isArray(dep.rows)) {\",\n replace: \" if (false) {\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.27 a stored list that is not a list\",\n },\n {\n name: \"the empty card goes back to saying nothing has been collected\",\n file: \"engine/dashboard.ts\",\n find: \"The deposit check has not run yet, so there is nothing to show here.\",\n replace: \"Nothing collected yet.\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.2 nothing collected yet\",\n },\n {\n name: \"a run that read fewer calendars overwrites the complete stored list\",\n file: \"engine/deposits.ts\",\n find: \" if (!force && prev && missedNow > missedBefore) {\",\n replace: \" if (false && !force && prev && missedNow > missedBefore) {\",\n once: true, suite: \"deposits-collect.test.mjs\", mustFail: \"D41 a run that saw fewer calendars\",\n },\n {\n name: \"the attempt stamp is written after the collection instead of before it\",\n file: \"engine/deposits.ts\",\n find: \" await b.setJSON(ATTEMPT_KEY, { at: new Date().toISOString(), source }).catch(() => {});\\n const tok = await token();\",\n replace: \" const tok = await token();\\n await b.setJSON(ATTEMPT_KEY, { at: new Date().toISOString(), source }).catch(() => {});\",\n once: true, suite: \"deposits-collect.test.mjs\", mustFail: \"D43 the refresh gate is claimed\",\n },\n {\n name: \"which payment settles a stay goes back to array order\",\n file: \"engine/holiday-deposits.ts\",\n find: \" .sort((a, b) => when(a) - when(b) || String(a.id).localeCompare(String(b.id)));\",\n replace: \" .slice();\",\n once: true, suite: \"holiday-deposits.test.mjs\", mustFail: \"H86 which payment settles a stay\",\n },\n {\n name: \"two stays on the same day are settled in whatever order they arrived\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const ordered = [...stays].sort((a, b) => a.day.localeCompare(b.day) || key(a).localeCompare(key(b)));\",\n replace: \" const ordered = [...stays].sort((a, b) => a.day.localeCompare(b.day));\",\n once: true, suite: \"holiday-deposits.test.mjs\", mustFail: \"H86 which payment settles a stay\",\n },\n {\n name: \"the deposit note offers cash as a place to look\",\n file: \"engine/holiday-deposits.ts\",\n find: 'export const OTHER_ROUTES = \"A deposit paid by Venmo, Zelle or a cheque does not reach the card system, so it will not show here.\";',\n replace: 'export const OTHER_ROUTES = \"A deposit paid by Venmo, Zelle, cheque or cash does not reach the card system, so it will not show here.\";',\n once: true, suite: \"holiday-deposits.test.mjs\", mustFail: \"H60 Kim is told where else to look\",\n },\n {\n name: \"a UTC drop-off time is sliced instead of converted, moving evening stays a day\",\n file: \"engine/holiday-deposits.ts\",\n find: \" if (/\\\\dZ$/.test(startTime)) {\",\n replace: \" if (false) {\",\n once: true, suite: \"holiday-deposits.test.mjs\", mustFail: \"H8 the local day is read off the string\",\n },\n {\n name: \"the last sighting of a repeated payment wins instead of the first\",\n file: \"engine/holiday-deposits.ts\",\n find: \" if (!prev || (at && prev.at && at < prev.at)) out.set(id, { amount, id, at, kind });\",\n replace: \" if (!prev || (at && prev.at && at > prev.at)) out.set(id, { amount, id, at, kind });\",\n once: true, suite: \"holiday-deposits.test.mjs\", mustFail: \"H85 a payment written into the notes\",\n },\n {\n name: \"the deposit schedules are deployed as plain scripts, so neither ever fires\",\n file: \"scripts/deploy.mjs\",\n find: '\"deposits-cron.ts\": \"interval\"',\n replace: '\"deposits-cron.ts\": \"script\"',\n once: true, suite: \"deposits-collect.test.mjs\", mustFail: \"D42 both schedules are wired\",\n },\n {\n name: \"the cron's refresh call is moved out of the file's own default export\",\n file: \"engine/deposits-cron.ts\",\n find: \"export default async function (): Promise {\",\n replace: \"export default async function (): Promise { return; }\\nasync function unused(): Promise {\",\n once: true, suite: \"deposits-collect.test.mjs\", mustFail: \"D42 both schedules are wired\",\n },\n {\n name: \"an accusation is added to the Stay column\",\n file: \"engine/dashboard.ts\",\n find: \"${esc(stayDates(r))}\",\n replace: '${esc(stayDates(r))}${r.state === \"none_seen\" ? \" (still to pay)\" : \"\"}',\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.20 the card renders a row\",\n },\n {\n name: \"the missed-calendar banner accuses the customers it could not see\",\n file: \"engine/dashboard.ts\",\n find: \"missing from the list below.
` : \\\"\\\";\",\n replace: \"missing from the list below, and those deposits are unpaid.
` : \\\"\\\";\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.4 the word unpaid\",\n },\n {\n name: \"the pick-up banner accuses the customers it could not see\",\n file: \"engine/dashboard.ts\",\n find: \"may be missing from this list.
` : \\\"\\\";\",\n replace: \"may be missing from this list, and those deposits are outstanding.
` : \\\"\\\";\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.4 the word unpaid\",\n },\n {\n name: \"the test-record warning accuses the record it is warning about\",\n file: \"engine/dashboard.ts\",\n find: \"so check who it is before you call.\",\n replace: \"so check who it is before you call. This one has not paid.\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.4 the word unpaid\",\n },\n {\n name: \"the dead-feed sentence contradicts itself and accuses everybody\",\n file: \"engine/holiday-deposits.ts\",\n find: \"so the list is being held back until that is checked.`;\",\n replace: \"so the list is being held back until that is checked. Nobody below has paid a deposit.`;\",\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.4 the word unpaid\",\n },\n {\n name: \"the dot colour is chosen at the render site rather than from the allowed set\",\n file: \"engine/dashboard.ts\",\n find: '',\n replace: '',\n once: true, suite: \"dashboard.test.mjs\", mustFail: \"D5.24b every REAL state\",\n },\n];\n\n// ---------------------------------------------------------------------------------------------\nconst log = (s = \"\") => console.log(s);\n\n// HOW MANY CONTROLS THERE ARE SUPPOSED TO BE. A ratchet, checked before anything runs and\n// regardless of --only.\n//\n// [was: nothing. On 6 August a bad edit truncated this file and deleted the whole runner; it then\n// printed NOTHING and exited 0, which reads exactly like \"all controls passed\". That was fixed by\n// making run-all re-prove seven controls every run. On 7 August an adversarial pass found the\n// same hole one turn down: truncate the ARRAY rather than the runner — cut it to three entries —\n// and the file prints `=== RESULT: 3 passed, 0 failed ===` and exits 0. Not silence this time; a\n// small, plausible, entirely fake green. Fourteen controls sit past the last of run-all's seven\n// critical ones, so a tail truncation there is caught by nothing at all.]\nconst EXPECTED_CONTROL_COUNT = 203;\nif (CONTROLS.length < EXPECTED_CONTROL_COUNT) {\n log(`RUNNER FAILURE: CONTROLS holds ${CONTROLS.length} entries; at least ${EXPECTED_CONTROL_COUNT} are expected.`);\n log(\"Controls have been lost. Refusing to report any result: a short run is not a clean run.\");\n process.exit(1);\n}\n\n// A CONTROL'S FINGERPRINT: the fault it actually injects, not the name somebody typed above it.\n// run-all.mjs re-proves seven money controls on every test run and matched them BY NAME, so\n// leaving the name in place and swapping the find/replace/mustFail underneath it kept the reassuring\n// line \"7 money guards each proved to still fire\" printing for a guard that no longer tested the\n// money bug it is named for. Proved on 7 August. The fingerprint is printed on every pass and\n// pinned in run-all.mjs.\nconst fingerprint = (c) => createHash(\"sha256\").update(JSON.stringify([c.file, c.find, c.replace, c.suite, c.mustFail, !!c.mustStayGreen])).digest(\"hex\").slice(0, 12);\n\n// THE CLEAN TREE MUST BE GREEN BEFORE A FAULT PROVES ANYTHING.\n//\n// A control claims: \"inject this fault, and that named test goes red.\" If the named test was\n// ALREADY red — an unrelated bug, a half-finished edit, a stale build — then the control passes\n// having proved nothing whatsoever about its own injection. Proved on 7 August by pointing a\n// control's `replace` at its own `find` (a byte-identical no-op) alongside one unrelated broken\n// constant: the control passed, on a fault it did not cause and could not have caused.\n//\n// Built once and memoized per suite, so this costs one build and one run per suite for the whole\n// session rather than one per control.\nconst baselines = new Map();\nlet cleanTree = null;\nfunction baselineIsGreen(suite) {\n if (baselines.has(suite)) return baselines.get(suite);\n if (!cleanTree) {\n cleanTree = mkdtempSync(join(tmpdir(), \"nc-clean-\"));\n for (const d of [\"engine\", \"tests\", \"handover\", \"scripts\"]) cpSync(join(ROOT, d), join(cleanTree, d), { recursive: true });\n const b = spawnSync(\"node\", [join(ROOT, \"scripts/build.mjs\"), \"--src\", join(cleanTree, \"engine\"), \"--out\", join(cleanTree, \"build\")],\n { encoding: \"utf8\", timeout: 180_000 });\n if (b.status !== 0) {\n log(\"RUNNER FAILURE: the CLEAN tree will not build. No control can prove anything against it.\");\n log((b.stdout + b.stderr).trim().slice(0, 600));\n process.exit(1);\n }\n }\n const isTs = suite.endsWith(\".ts\");\n const r = spawnSync(isTs ? \"npx\" : \"node\", isTs ? [\"--yes\", \"tsx\", join(cleanTree, \"tests\", suite)] : [join(cleanTree, \"tests\", suite)],\n { encoding: \"utf8\", cwd: cleanTree, timeout: 180_000 });\n const green = r.status === 0;\n baselines.set(suite, green);\n if (!green) {\n const red = `${r.stdout ?? \"\"}${r.stderr ?? \"\"}`.split(\"\\n\").filter((l) => l.startsWith(\"FAIL\")).slice(0, 3).join(\" | \");\n log(`baseline: ${suite} is ALREADY RED before any fault is injected -> ${red.slice(0, 240)}`);\n }\n return green;\n}\n\nlet pass = 0, fail = 0;\nconst failures = [];\n\nfunction runControl(c, i) {\n // Nothing this control does can mean anything if its suite is red to begin with.\n if (!baselineIsGreen(c.suite)) return bad(c, `${c.suite} is RED on the clean tree, so this control would pass for a reason that is not its own fault`);\n const tmp = mkdtempSync(join(tmpdir(), \"nc-\"));\n try {\n // handover/ comes too: the cross-artifact controls patch the documents Kim actually reads,\n // and that suite resolves them relative to its working directory.\n // scripts/ comes too. [was: engine, tests and handover only — so D42, which reads\n // scripts/deploy.mjs to check both schedules are still deployed as val.town intervals, threw\n // in every control's temp tree. Under the new baseline check that shows up honestly as\n // \"deposits-collect.test.mjs is RED on the clean tree\"; before it, four controls would have\n // passed on a suite that was red for a reason that had nothing to do with them.]\n for (const d of [\"engine\", \"tests\", \"handover\", \"scripts\"]) cpSync(join(ROOT, d), join(tmp, d), { recursive: true });\n\n const target = join(tmp, c.file);\n if (!existsSync(target)) return bad(c, `the file it patches does not exist: ${c.file}`);\n\n let src = readFileSync(target, \"utf8\");\n const applyOne = (find, replace) => {\n const at = src.indexOf(find);\n if (at === -1) return false;\n src = src.slice(0, at) + replace + src.slice(at + find.length);\n return true;\n };\n // A control whose injection does not apply is a BROKEN CONTROL, not a pass. This is the\n // failure mode that produced three fake checks: the pattern matched nothing and everyone\n // read the green.\n if (!applyOne(c.find, c.replace)) return bad(c, `injection matched NOTHING in ${c.file}: this control is blind`);\n if (c.then && !applyOne(c.then.find, c.then.replace)) return bad(c, `the follow-up injection matched nothing`);\n writeFileSync(target, src);\n\n // Rebuild the patched tree.\n const b = spawnSync(\"node\", [join(ROOT, \"scripts/build.mjs\"), \"--src\", join(tmp, \"engine\"), \"--out\", join(tmp, \"build\")],\n { encoding: \"utf8\", timeout: 180_000 });\n if (b.status !== 0) return bad(c, `the patched tree would not build, so the suite never ran:\\n${(b.stdout + b.stderr).trim().slice(0, 400)}`);\n\n // Run the one suite that owns this guarantee.\n const isTs = c.suite.endsWith(\".ts\");\n const r = spawnSync(isTs ? \"npx\" : \"node\", isTs ? [\"--yes\", \"tsx\", join(tmp, \"tests\", c.suite)] : [join(tmp, \"tests\", c.suite)],\n { encoding: \"utf8\", cwd: tmp, timeout: 180_000 });\n const out = `${r.stdout ?? \"\"}${r.stderr ?? \"\"}`;\n\n // An INVERTED control: the injection is something the check must NOT react to. A structural\n // check that reads code has to stay green when the forbidden text appears only in a comment;\n // if it goes red, it is matching prose and every green it has ever given is worthless.\n if (c.mustStayGreen) {\n if (r.status !== 0) {\n const red = out.split(\"\\n\").filter((l) => l.startsWith(\"FAIL\")).join(\" \").slice(0, 300);\n return bad(c, `the suite went RED on text that appears only inside a comment: it is matching prose, not code.\\n ${red}`);\n }\n pass++;\n log(`PASS control ${i + 1}: ${c.name}`);\n log(` -> ${c.suite} stayed green, so it is reading code rather than comments [fp:${fingerprint(c)}]`);\n return true;\n }\n\n if (r.status === 0) return bad(c, `THE SUITE STAYED GREEN with the fault injected. ${c.suite} cannot catch this.`);\n\n // Red is necessary but not sufficient. The NAMED test must be the one that went red.\n const redLines = out.split(\"\\n\").filter((l) => l.startsWith(\"FAIL\"));\n if (!redLines.length) return bad(c, `the suite exited non-zero but printed no FAIL line: it crashed rather than caught anything.\\n${out.trim().slice(0, 300)}`);\n if (!redLines.some((l) => l.includes(c.mustFail))) {\n return bad(c, `red, but on the wrong test. Expected \"${c.mustFail}\", got:\\n ${redLines.join(\"\\n \").slice(0, 400)}`);\n }\n\n pass++;\n log(`PASS control ${i + 1}: ${c.name}`);\n log(` -> ${c.suite} went red on \"${c.mustFail}\" [fp:${fingerprint(c)}]`);\n return true;\n } finally {\n rmSync(tmp, { recursive: true, force: true });\n }\n}\n\nfunction bad(c, why) {\n fail++;\n failures.push(`${c.name}\\n ${why}`);\n log(`FAIL control: ${c.name}`);\n log(` ${why.split(\"\\n\").join(\"\\n \")}`);\n return false;\n}\n\n// `--only ` runs a subset while iterating on one module. It is DELIBERATELY loud:\n// a filtered green is not a green, and the banner says so on the way in and on the way out, so\n// nobody can paste a partial run into a report and call the suite clean.\nconst onlyIx = process.argv.indexOf(\"--only\");\nconst ONLY = onlyIx > -1 ? process.argv[onlyIx + 1] : null;\nconst SELECTED = ONLY ? CONTROLS.filter((c) => c.name.includes(ONLY) || c.file.includes(ONLY) || c.suite.includes(ONLY)) : CONTROLS;\nif (ONLY && !SELECTED.length) {\n log(`--only \"${ONLY}\" matched none of the ${CONTROLS.length} controls. Refusing to report a green on zero work.`);\n process.exit(1);\n}\n\nif (ONLY) log(`\\n*** FILTERED RUN: ${SELECTED.length} of ${CONTROLS.length} controls (\"${ONLY}\"). THIS IS NOT A FULL PASS. ***`);\nlog(`\\nNEGATIVE CONTROLS — injecting ${SELECTED.length} faults, one at a time.\\n`);\nSELECTED.forEach(runControl);\n\nlog(`\\n=== RESULT: ${pass} passed, ${fail} failed ===`);\nif (ONLY) log(`*** FILTERED RUN: ${CONTROLS.length - SELECTED.length} controls were not run. This does not clear the suite. ***`);\nif (fail) {\n log(`\\n${fail} guarantee(s) are not actually guarded. A green suite means nothing for these:`);\n for (const f of failures) log(` - ${f}`);\n}\nprocess.exit(fail ? 1 : 0);\n\n\n\n=====FILE tests/registry.test.mjs =====\n// WATCHING A LIST SOMEBODY ELSE CONTROLS.\n// The watchdog has watched Kim's 165 automations since 4 August and has never once been seen to\n// fire, because firing requires somebody to change something. That is the definition of a check\n// nobody has verified. The comparison lives on its own now so it can be exercised directly, and\n// every case below is a way the watch could quietly stop working.\nimport * as R from \"../build/registry-diff.js\";\nimport { suite, ok, eq, scoped } from \"./_harness.mjs\";\nconst { t, done } = suite(\"registry\");\n\nconst KB_BEFORE = {\n XOsEp: \"UPDATED - CONSOLIDATED [THE DOGS SPOT] @2026-08-05T02:38\",\n ZkVFb: \"Chloe - Boarding @2026-07-31T12:47\",\n roL2d: \"Ava Knowledgebase @2026-08-03T03:34\",\n};\n\nt(\"G1 an edit in place is caught, which is the case the whole watch exists for\", () => {\n // Same id, same name, new timestamp. Nothing is added and nothing is removed, so a check that\n // only counted entries would see nothing at all — and this is exactly what happened to the\n // consolidated knowledge base at 02:38 on 5 August.\n const after = { ...KB_BEFORE, XOsEp: \"UPDATED - CONSOLIDATED [THE DOGS SPOT] @2026-08-05T09:12\" };\n const c = R.registryDiff(KB_BEFORE, after);\n ok(c.changed, \"an in-place edit was not noticed\");\n eq(c.added, []);\n eq(c.removed, []);\n eq(c.edited.length, 1);\n ok(/02:38 -> .*09:12/.test(c.edited[0]), `the change does not show what moved: ${c.edited[0]}`);\n return scoped(5, \"assertions\");\n});\n\nt(\"G2 additions and removals are told apart, and named\", () => {\n const added = R.registryDiff(KB_BEFORE, { ...KB_BEFORE, newId: \"Brand New KB @2026-08-06T00:00\" });\n eq(added.added, [\"Brand New KB @2026-08-06T00:00\"]);\n eq(added.removed, []);\n const { ZkVFb, ...minusOne } = KB_BEFORE;\n const removed = R.registryDiff(KB_BEFORE, minusOne);\n eq(removed.removed, [\"Chloe - Boarding @2026-07-31T12:47\"]);\n eq(removed.added, []);\n ok(removed.changed && added.changed);\n return scoped(5, \"assertions\");\n});\n\nt(\"G3 an unchanged registry is silent, so the alarm does not cry wolf every pass\", () => {\n const c = R.registryDiff(KB_BEFORE, { ...KB_BEFORE });\n eq(c.changed, false, \"an identical registry reported a change\");\n eq([...c.added, ...c.removed, ...c.edited], []);\n // key ORDER must not matter: the CRM does not promise one\n const shuffled = Object.fromEntries(Object.entries(KB_BEFORE).reverse());\n eq(R.registryDiff(KB_BEFORE, shuffled).changed, false, \"a reordered list reads as a change\");\n return scoped(3, \"assertions\");\n});\n\nt(\"G4 a first run has no baseline and must not report the whole world as new\", () => {\n // The very first pass writes a baseline. If it also alarmed, every deploy would page somebody.\n const c = R.registryDiff(null, KB_BEFORE);\n eq(c.added.length, 3, \"a first run should still be able to describe what it found\");\n eq(c.removed, []);\n eq(c.edited, []);\n // and the watchdog only alarms when prev exists, which is the caller's job — proven in G6\n return scoped(3, \"assertions\");\n});\n\nt(\"G5 garbage in does not throw and does not invent a change\", () => {\n for (const junk of [null, undefined, \"not an object\", 42, []]) {\n const c = R.registryDiff(junk, junk);\n eq(c.changed, false, `${JSON.stringify(junk)} produced a change out of nothing`);\n }\n eq(R.registryDiff(KB_BEFORE, null).removed.length, 3, \"a null 'now' should read as everything gone, for the caller to judge\");\n return scoped(6, \"shapes\");\n});\n\nt(\"G6 an empty list on a good response is treated as a glitch, not as a deletion\", () => {\n // The rule the workflow watch learned the hard way: overwriting a baseline with an empty list\n // fires \"everything removed\" this pass and \"everything added\" the next.\n ok(R.looksLikeAGlitch(0, 8), \"an empty response after a healthy one is being believed\");\n ok(!R.looksLikeAGlitch(0, 0), \"a genuinely empty account is being called a glitch forever\");\n ok(!R.looksLikeAGlitch(8, 8), \"a normal response is being called a glitch\");\n ok(!R.looksLikeAGlitch(3, 8), \"a partial response is being called a glitch: it is a real change\");\n ok(!R.looksLikeAGlitch(0, null), \"a missing baseline is being called a glitch\");\n return scoped(5, \"cases\");\n});\n\nt(\"G7 the sentence is generated from the change and says how much it left out\", () => {\n const many = {};\n for (let i = 0; i < 9; i++) many[`id${i}`] = `Thing ${i} @2026-08-06T00:00`;\n const c = R.registryDiff({}, many);\n const line = R.registrySentence(c, \"her knowledge bases\");\n ok(/Added: Thing 0/.test(line), \"the sentence does not name what changed\");\n ok(/6 more not listed here/.test(line), `the sentence hides how much it truncated: ${line}`);\n const quiet = R.registrySentence(R.registryDiff(KB_BEFORE, KB_BEFORE), \"her automations\");\n ok(/Nothing has moved in her automations/.test(quiet), quiet);\n ok(!/undefined|NaN|\\[object/.test(line + quiet), \"a stray value reached the sentence\");\n return scoped(4, \"assertions\");\n});\n\ndone();\n\n\n=====FILE tests/render.test.mjs =====\n// MESSAGE RENDERING — the escape and merge rules, tested directly.\n// Two of these are regressions from a security review: a name containing $-patterns corrupting the\n// body, and contact-typed text reaching the HTML unescaped. Both shipped once.\nimport * as R from \"../build/render.js\";\nimport { suite, ok, eq, scoped } from \"./_harness.mjs\";\nconst { t, done, header } = suite(\"render\");\n\nheader(\"MERGE FIELDS\");\nt(\"M1.1 blank names fall back rather than rendering 'Hi ,'\", () => {\n eq(R.resolveFirstName(\"\"), \"there\"); eq(R.resolveFirstName(null), \"there\"); eq(R.resolveFirstName(\" \"), \"there\");\n eq(R.applyMergeFields(\"Hi {{FIRST_NAME}}!\", \"\", \"\"), \"Hi there!\");\n return scoped(4, \"cases\");\n});\nt(\"M1.2 a name full of $-patterns cannot corrupt the body\", () => {\n // String.replace treats $&, $', $` and $1 as references. With a string replacement a customer\n // named Bo$$ would have injected fragments of the template into their own message.\n const evils = [\"Bo$$\", \"Re$&\", \"$'\", \"$`\", \"$1$2\", \"A$&B\"];\n for (const e of evils) eq(R.applyMergeFields(\"Hi {{FIRST_NAME}}!\", e, \"\"), `Hi ${e}!`, `name ${e} mangled`);\n return scoped(evils.length, \"hostile names\");\n});\nheader(\"HTML ESCAPING\");\nt(\"M2.1 every dangerous character is escaped\", () => {\n eq(R.escHtml(`', note: \"hi\" }] };\n const h = DASH.depositCard(nasty, true, noAgo);\n ok(!/

Segment	Count	Share	What can be done
Has an email	${c.emailable}	${pct(c.emailable, d.total)}	The email release. This is the real audience.
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.

Diff · v693