Nurture paths

[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_232":233,"_234":235},"routes/_app.x.$handle.$name",{"_97":96,"_31":42,"_106":87,"_26":107,"_13":14,"_108":-5,"_11":109,"_110":111,"_112":113,"_114":115,"_116":117,"_20":-5,"_118":-5,"_119":-5,"_120":24,"_121":122,"_123":56,"_124":-5,"_125":-5,"_126":127},"routes/_app.x.$handle.$name.branch.$branch.version.$version.diff",{"_11":12,"_13":14,"_15":16,"_17":-5,"_18":-5},"project",{"_40":41,"_31":42,"_35":43,"_44":-5,"_45":24,"_46":47,"_48":47,"_49":50,"_51":-5,"_18":52,"_53":54,"_55":56,"_57":-5,"_58":-5,"_59":60,"_61":62,"_63":64,"_65":66,"_67":68,"_69":-5,"_70":71,"_72":71,"_73":74,"_75":74,"_76":74,"_77":71,"_78":71,"_79":80,"_81":82,"_83":84,"_85":24},"version",18,"changes",[19],"aiChatInfo","userId",{"_20":21,"_22":-7,"_23":24,"_25":24,"_26":27,"_28":27},"file",{"_29":30,"_31":27,"_32":20,"_33":34,"_35":36,"_37":14,"_38":39,"_23":24},"previous","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.","createdAt",["D",1785683085978],"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",{"_97":96,"_105":101},"org",{"_97":96,"_98":99,"_100":101,"_18":52,"_102":103,"_104":24},"branch",{"_13":86,"_31":87,"_40":39,"_88":41,"_89":-5,"_90":-5,"_91":-5,"_92":-5,"_93":-5,"_94":42,"_95":96},"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",{"_40":41,"_31":42,"_35":227,"_44":-5,"_45":24,"_46":47,"_48":47,"_49":50,"_51":-5,"_18":52,"_53":54,"_55":56,"_57":-5,"_58":-5,"_59":60,"_61":62,"_63":64,"_65":66,"_67":228,"_69":-5,"_70":71,"_72":71,"_73":74,"_75":74,"_76":74,"_77":71,"_78":71,"_79":229,"_81":230,"_83":231,"_85":24},"tree",[198,199,200,201,202,203,204],"files",[198,199,200,201,202,203,204],"counts",{"_187":60,"_188":142,"_189":60,"_190":191,"_192":193},"contents",[128,129,130,131,132,133,134],"upstreamProject","upstreamBranch","emptyEnvVars","flags",[],"hasHttpFiles","grants","orgs","customDomains",{},{"_40":184,"_31":27,"_29":30,"_138":-5,"_38":39,"_37":14,"_140":24,"_35":185,"_13":60,"_32":20,"_33":34,"_23":24,"_145":-5,"_26":186},{"_40":177,"_31":178,"_29":179,"_138":-5,"_38":39,"_37":180,"_140":24,"_35":181,"_13":142,"_32":143,"_33":182,"_23":24,"_145":-5,"_26":183},{"_40":171,"_31":172,"_29":54,"_138":-5,"_38":39,"_37":173,"_140":24,"_35":174,"_13":160,"_32":143,"_33":175,"_23":24,"_145":-5,"_26":176},{"_40":163,"_31":164,"_29":165,"_138":-5,"_38":39,"_37":166,"_140":24,"_35":167,"_13":150,"_32":168,"_33":169,"_23":24,"_145":-5,"_26":170},{"_40":155,"_31":156,"_29":157,"_138":-5,"_38":39,"_37":158,"_140":24,"_35":159,"_13":160,"_32":143,"_33":161,"_23":24,"_145":-5,"_26":162},{"_40":147,"_31":148,"_29":149,"_138":-5,"_38":39,"_37":150,"_140":24,"_35":151,"_13":142,"_32":152,"_33":153,"_23":24,"_145":-5,"_26":154},{"_40":135,"_31":136,"_29":137,"_138":-5,"_38":39,"_37":139,"_140":24,"_35":141,"_13":142,"_32":143,"_33":144,"_23":24,"_145":-5,"_26":146},"36659075-120a-4f67-995b-203ed981f4fa","run.ts","be37b584-8e76-11f1-b9e0-1607ee4eb77e","parentId",14,"latest",["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","label",[136],"d33235b1-4614-4c5b-975a-131a9f3883d6","puppy-messages.ts","cd4b87b0-8c34-11f1-b87e-1607ee4eb77e",4,["D",1785676173115],"script","// 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 CORRECTION, 2 Aug 2026 — WRONG-CALENDAR DEFECT, FIXED --------------------------------\n// The previous value was:\n// https://api.leadconnectorhq.com/widget/bookings/pbe-discovery-9edbddc3-4b5a-406e-9bc3-7f10cb0d3221\n// That widget returns HTTP 200, which is why it passed the original check — but a 200 only proves a\n// page exists, not that it is HERS. Verified live 2 Aug 2026 against GET /calendars/?locationId=\n// BQHJ19uohldYe3eqA0bl (29 calendars): that id does NOT belong to this location. \"pbe\" is Pet Biz\n// Experts, the parent agency; it is the agency's own discovery-call widget.\n//\n// Three things it would have caused, every one of them customer-visible:\n// 1. Kim's leads would have booked the AGENCY's calendar. She would never have seen the booking.\n// 2. The engine watches PUP_TALK_CALENDAR_ID (qHuYJ0NEqzibnoqf5Cw3, confirmed live as \"Pup Talk\n// Phone Call\") to decide someone has converted. A lead who booked through the old link would\n// never register as booked, so the engine would have kept nurturing a customer who had already\n// said yes — the exact failure the whole exit-rule ladder exists to prevent.\n// 3. The literal string \"discovery\" would have appeared in a customer-facing URL. Kim banned that\n// word by name; it is \"Pup Talk\".\n//\n// The replacement is the same id the engine already trusts for booking detection, so the link a lead\n// clicks and the calendar the engine watches are now provably the same object. Both re-checked live\n// 2 Aug 2026: HTTP 200.\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: genuinely two live candidates found this session, not silently picked — see build\n// report. Using 912-348-8726 because two independent signals agree on it (GHL's default outbound\n// calling line, AND the number published on thedogsspotga.com/contact) and zero signals point to the\n// Business Profile field's alternative (912-823-4382). Worth a one-line confirm from Kim before\n// go-live regardless — flagged, 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}} / {{DOG_NAME}} are per-contact merge tokens, resolved at render time by\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\nexport const MAIN_SEQUENCE: MessageTemplate[] = [\n {\n id: \"main-1\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Getting {{DOG_NAME}} 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 {{DOG_NAME}} is already running circles round 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 realise - a lot of that learning is done by around four to five months old. Whatever {{DOG_NAME}} meets 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, toilet 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 {{DOG_NAME}}, not a sales pitch. 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 bodyTemplate: `Hi {{FIRST_NAME}}, it's Kim at The Dogs Spot. Got your message about {{DOG_NAME}} - 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 {{DOG_NAME}} has started biting at hands, sleeves, ankles, shoelaces - that's not a behaviour 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.** The second teeth touch skin, swap in something they're allowed to bite - a toy, a chew, your sleeve traded for something better. Saying \"no\" tells them to stop; it doesn't tell them what to do instead.\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 you want to talk through what's normal for {{DOG_NAME}}'s age specifically, that's an easy thing to cover in a Pup Talk. Reply here anytime, or call or text ${PHONE_DISPLAY}.\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 toilet training going with {{DOG_NAME}}? 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 toilet-training timeline\",\n previewText: \"What actually helps, and why one accident isn't a setback.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nToilet 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, {{DOG_NAME}} has 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 {{DOG_NAME}} is past that and still struggling, that's worth an actual conversation rather than another article - a Pup Talk is exactly the place for it. Call or text ${PHONE_DISPLAY}, or just reply here.\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 {{DOG_NAME}} 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, garden. Say the word once, and make coming back to you the best thing that happens all day - food, praise, a game, whatever {{DOG_NAME}} actually wants.\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\nThis is one of the things people ask about most in a Pup Talk, because it's an easy one to accidentally undo without realising. If you'd like to talk through where {{DOG_NAME}} is with it, we're easy to reach - ${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 daycare for {{DOG_NAME}}, 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 one of these for a while, so a quick summary of everything I've sent: get {{DOG_NAME}} meeting the world calmly while that window's open, expect the biting and treat it as normal, keep the toilet-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\nI won't keep filling your inbox with puppy emails past this point. If you'd like to talk any of this through properly - what's normal for {{DOG_NAME}} specifically, what training or daycare 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, not a pitch. 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 sort 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\nWe had a Pup Talk booked and the time came and went - completely fine, life gets in the way, and I'd rather rebook than assume anything about it.\n\nIt's a short call, not a big commitment: we talk through {{DOG_NAME}}, what's going on day to day, and whether training or daycare with us would actually help. If it's not the right fit, you'll hear that from me too.\n\nReply here with a couple of times that suit, call or text ${PHONE_DISPLAY}, or pick a slot yourself: ${SHORT_BOOKING_LINK}.\n\nIf I don't hear back, I'll leave it there for now rather than keep chasing - you're welcome to reach out whenever it's a better time.\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: \"No pitch here, 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 with {{DOG_NAME}}, even outside of anything you decide to book.\n\nIf it's not the right time for training or daycare 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}. I'm not going to chase you for an answer. 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 {{DOG_NAME}}'s getting on. If a question's come up since we spoke, reply here anytime. No pressure either way.`,\n },\n];\n\n",[148],"fd1e098a-477d-4654-a6db-c96585677211","paths.ts","243d2a8e-8e78-11f1-bbbc-1607ee4eb77e",16,["D",1785678976840],2,"// 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// Registering paths 2-6 is then a copy drop, not an engineering job — which is exactly the state\n// the project needs to be in, because the copy for those five exists and is approved by nobody yet.\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};\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 },\n {\n key: \"behaviour\", label: \"Behaviour problems\", sourceTag: \"nurture - behaviour\", enrolledTag: \"behaviour-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 },\n {\n key: \"boarding\", label: \"Boarding enquiries\", 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 },\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 },\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 },\n {\n key: \"aged\", label: \"Dormant enquiries\", 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 },\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 a copy drop — the tag, the channels and the constraints are already decided, and 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",[156],"ef5ea1af-2bf1-49c2-902a-7c7655bd56f7","main.ts","cdd9f676-8c34-11f1-baf4-1607ee4eb77e",17,["D",1785678977334],"interval","// PUPPY PATH ENGINE v1.1 — nurture automation for The Dogs Spot's puppy leads (built 27 Jul 2026;\n// v1.1 same evening — see the v1.1 addendum block below for what changed and why)\n//\n// WHY THIS EXISTS AS A VAL, NOT A NATIVE GHL WORKFLOW:\n// GHL's public API cannot create or edit workflow steps — UI-only, no way around it — and the\n// workflow-builder UI itself was tested this session via browser automation and found completely\n// unresponsive (clicks/scroll/keyboard, across multiple tabs and domains — not a one-off glitch).\n// So this is a val.town script driven by the GHL REST API instead, matching this account's own\n// existing idiom. Follows PupsClub-AutoSend-val-v2.1.ts's conventions closely on purpose: same j()\n// fetch helper, same Deno.env.get-driven TEST_MODE-defaults-true pattern, same blob-based state,\n// same wrapped-in-try/catch-writes-a-state-blob-every-run structure, same per-recipient try/catch\n// inside the send loop.\n//\n// HOW IT WORKS:\n// One state blob (puppy_state), keyed by contactId, tracks each enrolled contact's position in\n// either the 8-message main sequence or one of two post-Pup-Talk branches (A: no-show, B: had the\n// call, didn't buy). Each cron run walks every contact currently in that state (plus, outside\n// TEST_MODE, discovers new puppy-tagged leads to enroll) and re-evaluates a FIXED priority list of\n// exit/branch rules (spec §5, rules 1-10 below, plus two additions flagged where they occur) top to\n// bottom — first match wins. Only if nothing else matches does it fall through to \"send whatever's\n// next due.\" Every safety exit (DND, disqualified, became a customer, human reply pending) is\n// checked BEFORE a send is ever considered, every single run, for every contact, regardless of what\n// status they were in a moment ago — that ordering is the whole safety model.\n//\n// HARD SAFETY INVARIANT (non-negotiable — Amir's written promise to Kim: \"nothing gets switched on in\n// the meantime\"):\n// TEST_MODE defaults true. When true, this script never looks at a real contact at all — discovery\n// is skipped outright, and the only contact it ever touches is one fixed dummy resolved via\n// /contacts/upsert (firstName \"ZZTEST\", lastName \"PuppyPath-Dummy\", email aizhigitovamir@gmail.com —\n// Amir's own inbox, safe to actually deliver to). Going live is a deliberate later step someone takes\n// on purpose (flip TEST_MODE=false as an env var) — not something that happens by forgetting a flag.\n//\n// GUARDRAILS:\n// - \"[TEST] \" prefix on every subject line / SMS body while TEST_MODE, so a real send during testing\n// is unmistakable — matches the PupsClub val's own convention exactly. Deliberately kept OUT of the\n// email body itself so the client-approved copy stays byte-for-byte verbatim; the subject prefix\n// alone 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\n// val's \"write state before sending\" choice, because the failure mode being defended against is\n// different here. That script defends against a duplicate blast to many recipients from an\n// overlapping run (one session opening, many people to text). This one processes contacts one at a\n// time in a single sequential loop, so the real risk is a step being marked \"sent\" and then never\n// actually going out because the network call failed. A duplicate nurture message on a rare retry\n// is 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\n// through the SAME order every run, so DND / disqualified / became-a-customer / human-reply always\n// outrank a scheduled send, never the other way round.\n//\n// TWO GENUINE GAPS FOUND WHILE BUILDING THIS, NOT WORKED AROUND, FLAGGED HERE ON PURPOSE:\n// 1. GET /conversations/search — the call rule 5 (inbound-reply detection) needs — returns 401 \"The\n// token is not authorized for this scope\" on this account's current PIT token. Tested directly\n// this session: with and without contactId, on both 2021-07-28 and 2021-04-15 API versions, all\n// four combinations 401 identically. This means reply-pause (arguably the single most\n// safety-critical rule in the whole spec) cannot actually run live with today's credential.\n// getReplyStatus() below fails CLOSED on this — it does not fabricate a \"no reply\" result, it\n// reports conversationCheckFailed=true, and decideAction() treats that as \"do not send anything to\n// this contact this run,\" full stop (see rule 5 below). Practical consequence: AS CURRENTLY\n// CREDENTIALED, this engine cannot send anything at all outside TEST_MODE, because the reply-check\n// always fails closed for every contact — which is an extra, accidental safety margin on top of\n// the TEST_MODE flag, but it is a real gap that needs a broader-scoped PIT token before this is\n// actually USEFUL live, not just safe. Side note: inspect-dummy.sh's own conversations/search call\n// would 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;\n// flagged here since it surfaced while building this.\n// 2. The Pup Talk \"declined / not now\" outcome signal (rule 8) doesn't exist yet as its own thing.\n// Per spec, this should key off the TDS-Declined tag being built for the separate front-desk\n// task-layer project (BUILD-CHECKLIST-UI.md). That tag did not exist as of the 26 Jul build\n// checklist (\"Settings -> Tags has no existing TDS-Bought, TDS-Declined, TDS-Nurture\"). Checked\n// again this session via contacts/search filtered by tag (contains_set operator, confirmed correct\n// via the account's own validation-error message listing valid operators) — zero contacts carry\n// it, but that is a weak signal: a tag can exist in Settings -> Tags with nobody on it yet, and\n// this token cannot read Settings -> Tags directly (401, same scope gap as #1) to check for real.\n// Treated as NOT CONFIRMED LIVE. PUP_TALK_DECLINED_TAG below is a clearly-named constant, not\n// invented behavior — wire the real value in once confirmed rather than guessing.\n//\n// State blobs: puppy_state (per-contact, keyed by contactId) · puppy_run_state (per-run report,\n// mirrors 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//\n// ---- v1.1 (27 Jul 2026, late) — five upgrades from the pre-deploy live review -------------------\n// Live verification against the real account (verify-live-reads.py, read-only) found that the\n// discovery tag \"nurture - puppy\" matches ZERO contacts — no spelling variant matches anyone, and\n// the newest 15 real New Lead contacts carry only \"messenger\"/campaign tags. There is no automatic\n// puppy-vs-adult signal in the account's data model (age lives only in Ava's chat transcripts). So:\n//\n// 1. ENROLLMENT IS HUMAN-GATED, by design not accident: applying the source tag to a contact IS the\n// enrollment action (\"tag them and the system takes over\"). The New-Lead-stage requirement from\n// spec §5's auto-discovery framing is deliberately DROPPED — under human gating the tag is\n// explicit intent, and silently ignoring a deliberately-tagged contact because their opportunity\n// sits 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\n// outcomes that would be WRONG, not merely unusual. Tag is env-overridable (TAG_SOURCE_SIGNAL).\n// 2. ENROLLMENT SURGE HOLD: normal operation is a few tags a day. If one run finds more than\n// ENROLL_SURGE_THRESHOLD (default 25) un-enrolled tag matches, someone bulk-tagged — the run\n// enrolls NOBODY, journals the hold loudly, and keeps holding until a human either removes the\n// bulk tags or sets ACKNOWLEDGE_SURGE=true. Already-enrolled contacts keep processing normally\n// during a hold. This is what protects a live account from a day-one accidental blast.\n// 3. SEND WINDOW: messages only go out 09:00–19:00 America/New_York (env: SEND_WINDOW_START_HOUR /\n// SEND_WINDOW_END_HOUR), and SMS additionally never on Sunday (env SMS_SUNDAY_OK=true to allow;\n// The Dogs Spot is closed Sundays — a business texting on its day off invites replies nobody\n// answers). A due-but-out-of-window message simply waits for the next in-window run; offsets\n// still anchor to enteredAt, so nothing else shifts. Spec line ~222 explicitly accepted the\n// late-night case as a known limitation; this removes it.\n// 4. PAUSED CONTACTS GET A LIGHTWEIGHT PASS (v1.2 revision of v1.1's full skip): spec defines no\n// resume path from paused_reply (a human reply permanently hands the conversation to a human —\n// writing sheet §4's own philosophy). v1.1 skipped paused contacts entirely; the adversarial\n// review showed that also disabled the DND/disqualified/became-customer rules for them, so a\n// paused contact who later bought was never counted or retired. v1.2: paused contacts get a\n// 2-read safety pass (contact + opportunities; reply check pinned failed-closed so a send is\n// structurally impossible) — hard exits still fire, sends never do. Un-pausing is a deliberate\n// human act: set the contact's status back to \"main\" in the puppy_state blob. Do NOT delete the\n// entry — the puppy-path-v1 tag blocks re-discovery, so deletion just orphans them.\n// 5. 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\n// contact every run. Now fetched once per run and indexed by contactId.\n// Plus: puppy_journal (append-only, capped 2000 rows — enrollments, sends, exits, pauses, holds,\n// failures) and puppy_summary (per-status counts, sends by step, exits by reason, booked-during-\n// path, customers-during-path) — the numbers Kim's 30-day report needs, accumulated from day one,\n// readable by the watchdog. State hygiene: terminal entries untouched for 60+ days are pruned from\n// puppy_state (their history stays in puppy_journal; the puppy-path-v1 tag still prevents\n// re-enrollment).\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\n// ---- reference IDs (spec §2, all verified live this session unless noted) ------------------------\n\nconst GHL = \"https://services.leadconnectorhq.com\";\n// v1.2 deploy note — TOKEN RESOLUTION, in order:\n// 1. GHL_TOKEN env var (the proper home; set it in the val's Environment Variables UI), else\n// 2. the PRIVATE blob `puppy_config` ({\"ghlToken\": \"...\"}), written via the val.town API.\n// The blob fallback exists because val.town has no env-var API and this deploy was done fully\n// programmatically. Blobs are account-private; this val's CODE is public, so the token must never\n// be hardcoded here. Once someone pastes GHL_TOKEN into the env UI, delete the puppy_config blob.\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\");\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\"\n | \"paused_reply\" | \"done_booked\" | \"done_customer\" | \"done_hard_exit\"\n | \"done_soft_21d\" | \"done_branch_complete\";\n\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};\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,\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\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.\nfunction 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.\nfunction resolveFirstName(firstName: string | null | undefined): string {\n const v = (firstName ?? \"\").trim();\n return v.length > 0 ? v : \"there\";\n}\n\nfunction applyMergeFields(template: string, firstName: string | null | undefined, companyName: string | null | undefined): string {\n return template\n .replaceAll(\"{{FIRST_NAME}}\", resolveFirstName(firstName))\n .replaceAll(\"{{DOG_NAME}}\", resolveDogName(companyName));\n}\n\nfunction mdBoldToHtml(text: string): string {\n return text.replace(/\\*\\*(.+?)\\*\\*/g, \"$1\");\n}\n\nfunction bodyToHtml(body: string, previewText?: string): string {\n const paragraphs = 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 ? `
${previewText}
\\n`\n : \"\";\n return preheader + paragraphs;\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 enquired 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 const resolvedBody = applyMergeFields(step.bodyTemplate, contact.firstName, contact.companyName);\n\n // ---- v1.4 (2 Aug) — OPT-OUT FURNITURE, appended at render time, never written into the copy ----\n // The adversarial pass checked the shipped templates and found the thing everyone had assumed was\n // there: not one of the five SMS says STOP, and not one of the seven emails carries an unsubscribe\n // line. An earlier risk register claimed opt-out wording was present. It was not. Retracted.\n //\n // This is appended by the renderer rather than edited into puppy-messages.ts on purpose, for three\n // reasons. It keeps the client-approved wording byte-for-byte, so what Kim signs off is what she\n // wrote. It cannot be forgotten on a new path — every message rendered by this engine carries it,\n // including the five paths whose copy has not been written yet. And it is one line to change if the\n // wording ever needs to.\n //\n // The SMS line is deliberately short: at 39 characters it costs a fraction of a segment, and the\n // 320-char ceiling is checked against the FINAL rendered body, furniture included, so a message can\n // never be pushed over the limit by the thing that makes it compliant.\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};\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\"; branchAnchorAt?: string }\n | { kind: \"soft_exit_21d\" }\n | { kind: \"branch_complete\" }\n | { kind: \"send\"; sequence: \"main\" | \"branch_a\" | \"branch_b\"; stepIndex: number }\n | { kind: \"skip\"; reason: string };\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. GHL exposes one top-level `dnd` boolean (proven in\n // inspect-dummy.sh). There is no independently-proven per-channel unsubscribe signal anywhere in\n // this account's existing tooling — a `dndSettings` object was observed present on live contacts\n // during this build, but per spec instruction it is deliberately NOT parsed (unverified schema,\n // nothing else in this account relies on it). So rule 2 collapses into rule 1: the one proven boolean\n // covers SMS STOP and email unsubscribe both, from GHL's side.\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: the stage check now scans ALL opportunities, not just\n // the primary — matches the monetaryValue clause's any-opportunity scope and spec's \"no opportunity\n // showing a Customer/Won-Paid stage\" wording. (Fuzz round proved the old primary-only check let a\n // send through while a secondary opp sat in Customer stage — near-impossible live given the\n // one-opp-per-contact account rule, but the cheap superset removes the asymmetry entirely.)\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 rule in\n // spec §5 (which only names Customer/Won-Paid/monetaryValue for rule 4), but the WRITING SHEET's §4\n // exits are unambiguous: \"If they book anything else... A paid service, a Free Training Day, walking\n // in and booking at the desk - any of it ends this sequence.\" Free Training Day is its own pipeline\n // stage with no monetary value (it's free), so spec's literal rule 4 wording doesn't actually catch\n // it — a real gap between the spec and the writing sheet's own stated intent, not a content\n // disagreement (spec says content loses to the writing sheet, mechanism wins to the spec; this is\n // neither — it's a rule the spec's enumeration simply left out). Resolved here rather than left\n // broken. This also happens to be the only sensible use for the \"done_booked\" terminal status the\n // state type declares but no other rule in §5 ever assigns.\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 — main -> awaiting_appt_outcome once a live Pup Talk booking appears. Scoped to the Pup Talk\n // calendar specifically (spec §2 only supplies that one calendar id, and branch A/B copy is\n // explicitly Pup-Talk-specific — \"we had a Pup Talk booked\" — so routing a Free-Training-Day-only\n // booking through this branch would send Pup Talk copy about an appointment that doesn't exist;\n // Free Training Day is already handled by rule 4b above instead). Spec's rule 6 text says \"a Pup Talk\n // (or other) appointment\" — the \"(or other)\" is acknowledged, not implemented, for that reason.\n if (s.status === \"main\" && apptIsLiveBooked(f.pupTalkAppt)) {\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 review and the\n // fuzz round (concrete trace: contact no-shows -> branch_a -> books a new Pup Talk two weeks out ->\n // v1.1 still sent branch_a-2 \"Let's find another time\" for an appointment they'd already replaced,\n // then went terminal and stopped watching the new appointment entirely). If a live booking exists\n // whose start time is NEWER than the branch anchor (i.e., it's a different, later appointment than\n // the one that put them in the branch), the branch conversation is obsolete: go back to\n // awaiting_appt_outcome and track the new appointment's outcome like any other. Rules 7/8 then\n // re-fire off the NEW appointment — including a second no-show correctly re-entering branch_a with\n // the new anchor.\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_appt_outcome -> branch_a (missed): time passed, not showed, not cancelled.\n // Cancelled-ahead-of-time is explicitly out of scope per the writing sheet §4 (\"doesn't cover a Pup\n // Talk that gets cancelled ahead of time... not folded into this draft\" — a different, existing\n // workflow, \"Cxld/Canceled Pup Talk,\" owns that case). A contact whose appointment gets cancelled\n // here deliberately stays parked in awaiting_appt_outcome rather than this engine inventing\n // unapproved behavior for a case the copy sheet explicitly didn't write for.\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_appt_outcome -> branch_b (showed, then marked declined/not-now). declinedSignal\n // is NOT CONFIRMED LIVE — see header gap #2. branchAnchorAt uses \"now\" per spec's own fallback\n // instruction (\"use 'now' if no better timestamp is available\") since no proven tag-application\n // timestamp exists to use instead.\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 soft exit. Gated on lastMainStepSent having actually reached the end of\n // MAIN_SEQUENCE, not purely on elapsed time. Message 8 is ALSO due at exactly +21 days, and this rule\n // sits ahead of rule 10 in priority order — a pure time-only gate would fire this rule first on the\n // very run message 8 becomes due, and message 8 would never actually send. Spec's own parenthetical\n // (\"i.e. message 8 has been sent and no exit fired\") is the tell that this is meant to be gated on\n // the send having happened, not just on the calendar math. Per spec: flag only, do NOT move the\n // pipeline stage — that decision belongs to a human (Kim's own §6 Q6).\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 sequence exhausted. Not an explicit numbered rule in spec §5, but PuppyState's own\n // type declares done_branch_complete as a real terminal status, and rule 10 has nothing left to send\n // once a branch's last step has gone out. Leaving a contact parked in branch_a/branch_b forever once\n // there is genuinely nothing left to do is inconsistent with that declared type, and would mean this\n // contact gets silently re-evaluated by every future cron run for no reason. Mirrors rule 9's own\n // \"sequence exhausted\" shape.\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 if (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 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 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 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 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 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 return next;\n case \"soft_exit_21d\":\n next.status = \"done_soft_21d\";\n next.exitReason = \"sequence complete, no reply/booking\";\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 next.lastBranchStepSent = s.lastBranchStepSent + 1;\n next.lastSentAt = nowIso; // v1.2 — feeds the min-gap pacing floor\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}\nasync function saveReport(report: unknown) {\n const blob = await getBlobModule();\n await blob.setJSON(\"puppy_run_state\", report);\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// Raised by the adversarial pre-mortem and NOT refuted. The enrolment loop called\n// getOpenOpportunities() once per candidate. With one or two human-tagged candidates that is\n// nothing; the day the dormant backlog is released it is one API call per candidate per run, on top\n// of the walk itself, and GHL answers sustained overload with 401/403 rather than 429 — so the\n// engine would not merely slow down, it would look credential-broken while quietly starving.\n//\n// The fix is the same shape as the calendar index directly below, which already solved this problem\n// once for appointments: fetch the exit-triggering stages ONCE per run and index them by contactId.\n// A candidate absent from the index has no disqualifying opportunity, which is the only question\n// enrolment eligibility actually asks. Cost goes from O(candidates) to O(exit-stage size) — and\n// those stages are small, because the pipeline's own census puts Customer / Won-Paid / Onboarding\n// at zero and Free Training Day and Disqualified in the low hundreds.\n//\n// Deliberately NOT applied to already-enrolled contacts: their per-contact read also has to catch a\n// monetaryValue > 0 opportunity sitting in any stage at all, and that population is bounded by the\n// surge guard, so it was never the blowout. Precision beats a clever sweep here.\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// 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 }> {\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 };\n // Field name NOT independently proven this session (the 401 blocked confirming it) — trying the\n // conventional GHL field defensively. v1.2 tightened two ways after the adversarial round:\n // 1. STRICT direction validation — only the literal strings \"inbound\"/\"outbound\" count as a\n // readable signal. The old `direction == null` check let a falsy-but-not-nullish value (e.g.\n // an empty string on a malformed conversation record) slip through as \"confirmed no reply\" —\n // the exact unrecognized-shape case fail-closed exists to catch.\n // 2. TEMPORAL scoping — an inbound message that predates this contact's enrollment is a historic\n // conversation someone already handled (e.g. a \"do you do daycare?\" text from months ago), not\n // a reply to this sequence. Without this, such contacts would pause permanently before their\n // first message ever sent. If no usable timestamp field exists on the record, we conservatively\n // treat the inbound as blocking (pause) rather than ignoring it. Timestamp field names are\n // best-effort until the scope unblocks and the real shape can be confirmed live.\n const direction = convo.lastMessageDirection ?? convo.direction ?? null;\n if (direction !== \"inbound\" && direction !== \"outbound\") {\n return { hasUnansweredInboundReply: false, conversationCheckFailed: true };\n }\n if (direction === \"outbound\") return { hasUnansweredInboundReply: false, conversationCheckFailed: false };\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 return { hasUnansweredInboundReply: false, conversationCheckFailed: false }; // pre-enrollment history\n }\n return { hasUnansweredInboundReply: true, conversationCheckFailed: false };\n } catch {\n return { hasUnansweredInboundReply: false, conversationCheckFailed: true };\n }\n}\n\n// ---- IO layer: GHL writes (all proven live this session, see PUPPY-PATH-TEST-REPORT.md) -----------\n\nasync function sendSms(contactId: string, text: string) {\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 // 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 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.2\",\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 // ---- v1.3 (2 Aug 2026) — KILL SWITCH -----------------------------------------------------------\n // Checked before the run lock, before state loads, before a single contact is looked at. Kim can\n // set this herself from the control panel (api.ts) with two taps and no help from anyone; it is the\n // one control she must never have to ask for. Deliberately fails OPEN — if the blob read throws,\n // the engine carries on rather than halting on a storage hiccup, because a silent permanent stop\n // would be indistinguishable from the outage this whole system is built to be visible about.\n // Nothing is deleted while stopped: every contact keeps its exact position and resumes from it.\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 const apptIndex = await fetchPupTalkApptIndex();\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\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 (header addendum #1/#2): the source tag is the HUMAN enrollment switch — live\n // check found zero contacts carrying it, so every appearance is a deliberate act. The spec-era\n // New-Lead-stage requirement is dropped (tag = explicit intent); what remains blocking is only\n // what would make enrollment WRONG: already a customer, or a live Pup Talk booking already on\n // the calendar (they don't need a \"book a Pup Talk\" sequence). DND is enforced by rule 1 on\n // their first processing pass, before anything could send. Surge hold protects against bulk\n // tagging — see selectEnrollable.\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 // The adversarial round showed the full skip quietly disabled rules 1/3/4 for paused contacts:\n // someone who replied and later BOUGHT stayed \"paused_reply\" forever, was never counted as a\n // customer, and never aged into pruning. Now: two cheap reads (contact + opportunities), no\n // reply/no-calendar calls, conversationCheckFailed pinned true so rule 5 structurally blocks\n // any send — only the hard-exit rules can fire. Un-pausing for real remains a human act: set\n // the contact's status field back to \"main\" in the puppy_state blob (do NOT delete the entry —\n // the puppy-path-v1 tag blocks re-discovery, so a deleted entry just orphans them; header docs\n // updated accordingly).\n if (s.status === \"paused_reply\") {\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 };\n const d = decideAction(facts, s);\n const nowIso = new Date().toISOString();\n if (d.kind === \"hard_exit\") {\n state[contactId] = applyDecision(d, s, nowIso);\n out.log.push(`${contactId}: paused contact hard-exited -> ${d.status} (${d.reason})`);\n jrow(contactId, \"hard_exit\", d.reason);\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 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 };\n\n const decision = decideAction(facts, s);\n const nowIso = new Date().toISOString();\n\n switch (decision.kind) {\n case \"hard_exit\":\n state[contactId] = applyDecision(decision, s, nowIso);\n out.log.push(`${contactId}: hard exit -> ${decision.status} (${decision.reason})`);\n jrow(contactId, \"hard_exit\", decision.reason);\n break;\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\"} — confirm next stage`,\n `Puppy path finished for ${facts.contact.firstName || \"contact\"}, no reply/booking — confirm whether they should move to Lead Nurture. (Pipeline stage NOT auto-moved — that's Kim's call, spec §5 rule 9 / writing sheet §6 Q6.)`,\n );\n } catch (e) {\n out.log.push(`${contactId}: soft-exit task FAILED: ${String(e).slice(0, 120)}`);\n }\n out.log.push(`${contactId}: soft exit at 21d, flagged (stage NOT moved)`);\n jrow(contactId, \"soft_exit_21d\", \"sequence complete, no reply/booking\");\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 seq = decision.sequence === \"main\" ? MAIN_SEQUENCE : decision.sequence === \"branch_a\" ? BRANCH_A : BRANCH_B;\n const step = seq[decision.stepIndex];\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 // State written AFTER a successful send — and, v1.2, PERSISTED immediately, not just\n // mutated in memory. The adversarial round's top finding: with one save at end-of-run, a\n // mid-run crash (val timeout, OOM, network) forgot every send already made that run and\n // re-sent them all next tick. Sends are the only irreversible action in this system, so\n // each one is durably recorded the moment it happens; a crash now loses at most\n // bookkeeping for non-send transitions, which recompute idempotently next run.\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 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}`);\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\":\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 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 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// Purpose: message copy references one short, stable link; if the real booking URL ever changes, one\n// line changes (REAL_BOOKING_URL above) instead of eight message templates.\n//\n// Deployment note, honestly flagged rather than guessed at: a single val.town val has one default\n// export, which is this file's cron() entry point. Whether val.town's current UI can attach a second,\n// HTTP trigger to a NAMED export (not the default) on the SAME val was not verified this session —\n// VT_TOKEN was unavailable, so nothing could be deployed to check. If it can, wire this function up\n// directly. If not, the fallback is a second, tiny val: two lines, importing REAL_BOOKING_URL from\n// this file and re-exporting a redirect as ITS default export. Either way this is a convenience, not a\n// critical system, exactly as spec §7 frames it — kept deliberately simple.\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 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};\nexport type { PuppyState, PuppyStatus, Facts, Decision, ContactFact, OppFact, ApptFact, MessageTemplate, RenderedMessage };\n",[164],"3d0e877b-92d4-488e-96ac-534bc598f294","api.ts",13,["D",1785678975114],"// 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}\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 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\"];\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\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 };\n}\n\n// ---- rendering ------------------------------------------------------------------------------------\n\nconst RAMP = [\"#86b6ef\", \"#3987e5\", \"#256abf\", \"#184f95\"]; // 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\"];\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) {\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 checked ${d.lastRunAgeMin} minute(s) ago. It checks every 15 minutes, day and night.` };\n\n const mode = d.testMode === true\n ? `
PRACTICE MODE — the system is doing everything except actually sending to your customers. Nothing reaches a real person while this says PRACTICE.
`\n : d.testMode === false\n ? `
LIVE — real messages are going to real people.
`\n : `
MODE UNKNOWN — no run has reported yet.
`;\n\n const rows = (d.recent || [])\n .map((r: any) => `${esc(String(r.ts || \"\").slice(0, 16).replace(\"T\", \" \"))}${esc(r.event)}${r.test ? ' practice' : \"\"}${esc(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. Refresh any time — these numbers are live.
\n\n
\n
${health.icon}
\n
${health.t}
${health.m}
\n
${mode}
\n\n
Right now
\n
\n${tile(\"People being followed up\", c.active, \"in a sequence today\")}\n${tile(\"Booked or bought\", c.won, \"came out the far end\", c.won > 0 ? GOOD : undefined)}\n${tile(\"Paused — someone replied\", c.paused, \"a human needs to answer\", 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)}
\n\n
Stop everything
\n
This halts the follow-up system before it looks at a single person. It takes effect within 15 minutes 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.
\n${d.killed\n ? ``\n : ``}\n
\n\n
The last 40 things it did
\n${rows}
When What Detail
\n\n${d.lastError ? `
Last recorded error
${esc(JSON.stringify(d.lastError).slice(0, 1200))}
` : \"\"}\n\n
Engine ${esc(d.engineVersion || \"?\")} · page built ${esc(d.generatedAt.slice(0, 16).replace(\"T\", \" \"))} UTC · same numbers as data: &f=json
\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 if (!(await authorised(k))) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\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",[172],"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",[178],"f4c07b43-125c-4475-9f3f-9101290a7cbb",["D",1785683085978],[27],"pulls","branches","forks","envVars",{"_194":196,"_197":60},"connections",{"_194":60,"_195":60},"count","unfilledCount",7,"emptyCount",{"_40":184,"_31":27,"_29":30,"_138":-5,"_38":39,"_37":14,"_140":24,"_35":224,"_13":60,"_32":20,"_33":34,"_23":24,"_145":-5,"_206":225,"_26":226},{"_40":177,"_31":178,"_29":179,"_138":-5,"_38":39,"_37":180,"_140":24,"_35":221,"_13":142,"_32":143,"_33":182,"_23":24,"_145":-5,"_206":222,"_26":223},{"_40":171,"_31":172,"_29":54,"_138":-5,"_38":39,"_37":173,"_140":24,"_35":218,"_13":160,"_32":143,"_33":175,"_23":24,"_145":-5,"_206":219,"_26":220},{"_40":163,"_31":164,"_29":165,"_138":-5,"_38":39,"_37":166,"_140":24,"_35":215,"_13":150,"_32":168,"_33":169,"_23":24,"_145":-5,"_206":216,"_26":217},{"_40":155,"_31":156,"_29":157,"_138":-5,"_38":39,"_37":158,"_140":24,"_35":212,"_13":160,"_32":143,"_33":161,"_23":24,"_145":-5,"_206":213,"_26":214},{"_40":147,"_31":148,"_29":149,"_138":-5,"_38":39,"_37":150,"_140":24,"_35":209,"_13":142,"_32":152,"_33":153,"_23":24,"_145":-5,"_206":210,"_26":211},{"_40":135,"_31":136,"_29":137,"_138":-5,"_38":39,"_37":139,"_140":24,"_35":205,"_13":142,"_32":143,"_33":144,"_23":24,"_145":-5,"_206":207,"_26":208},["D",1785678975976],"children",[],[136],["D",1785676173115],[],[148],["D",1785678976840],[],[156],["D",1785678977334],[],[164],["D",1785678975114],[],[172],["D",1785678976395],[],[178],["D",1785683085978],[],[27],["D",1785429259053],["D",1789519842404],{"_97":96,"_105":101},{"_97":96,"_98":99,"_100":101,"_18":52,"_102":103,"_104":24},{"_13":86,"_31":87,"_40":39,"_88":41,"_89":-5,"_90":-5,"_91":-5,"_92":-5,"_93":-5,"_94":42,"_95":96},"ctx",{"_79":-5,"_125":265,"_266":267,"_268":269,"_270":24,"_271":24,"_272":24,"_273":56,"_274":-5,"_275":-7,"_276":-7,"_277":60,"_278":24,"_279":24,"_280":-5,"_281":24,"_282":24,"_283":24,"_284":-5},"ENV",{"_236":237,"_238":239,"_240":87,"_241":242,"_243":244,"_245":246,"_247":248,"_249":250,"_251":252,"_253":254,"_255":256,"_257":258,"_259":260,"_261":262,"_263":264},"REACT_APP_SENTRY_DSN","https://586020d86f05489db63a554690acf1e9@o1398359.ingest.sentry.io/6724499","RENDER_GIT_COMMIT","e87eb04e707cf64e7e532c8e8ec395f209e17f15","RENDER_GIT_BRANCH","POSTHOG_API_TOKEN","phc_nmoyuAkStEZuUp69rYlg1DZgrIt19Gx0Y4Hwf8tGgJP","POSTHOG_API_HOST","https://wart.val.town","WEB_API_TEMPLATE","https://{val}.web.val.run","APP_URL","https://www.val.town","MODULE_URL","https://esm.town","VANITY_WEB_API_TEMPLATE","https://{label}.val.run/","DENOLS_URL","https://lsp.val.town","NODE_ENV","production","CLOUDFLARE_TURNSTILE_SITE_KEY","0x4AAAAAACtaIZJH7s9rBMZ6","GOOGLE_CLIENT_ID","875989696899-jtsqkhlbdv5jrlsk8631p7ipjg3c6o62.apps.googleusercontent.com","STRIPE_PUBLISHABLE_KEY","pk_live_51N2zvWEpZTTLipIkVEwXrUG9AT0yeOOEYxszarZT1jpsZV58Ly6wlg3SltZpHN26CUalOBmUSY7adQRQiSkCZz2500qSXNkf8Y","API_URL","https://api.val.town",[],"preferencesKeybindings","default","preferencesTheme","light","preferencesFixers","preferencesCopilot","preferencesSelectionAi","preferencesCloseBrackets","preferencesChatPanelState","preferencesDprint","preferencesDenofmt","notificationCount","flagDenols","isBusinessOrgMember","businessOrgHandle","isBusinessOrgAdmin","isHigherTownieTier","navCollapsed","currentOrgId"]

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 · v18