[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_548":549,"_550":551},"routes/_app.x.$handle.$name",{"_99":98,"_33":45,"_108":89,"_28":109,"_13":14,"_110":-5,"_11":111,"_112":113,"_114":115,"_116":117,"_118":119,"_20":-5,"_120":-5,"_121":-5,"_122":27,"_123":124,"_125":25,"_126":-5,"_127":-5,"_128":129},"routes/_app.x.$handle.$name.branch.$branch.version.$version.diff",{"_11":12,"_13":14,"_15":16,"_17":-5,"_18":-5},"project",{"_43":44,"_33":45,"_38":46,"_47":-5,"_48":27,"_49":50,"_51":50,"_52":53,"_54":-5,"_18":55,"_56":57,"_58":25,"_59":-5,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":68,"_69":70,"_71":-5,"_72":73,"_74":73,"_75":76,"_77":76,"_78":76,"_79":73,"_80":73,"_81":82,"_83":84,"_85":86,"_87":27},"version",295,"changes",[19],"aiChatInfo","userId",{"_20":21,"_22":23,"_24":25,"_26":27,"_28":29,"_30":29},"file",{"_31":32,"_33":29,"_34":20,"_35":37,"_38":39,"_40":14,"_41":42,"_24":27},"previous",{"_31":32,"_33":29,"_34":20,"_35":36},"deleted",true,"deletedHere",false,"path","SOURCE-BUNDLE.part5.txt","latestPath","fileId","11feec3e-919f-11f1-8a41-1607ee4eb77e","name","fileType","content","THE DOGS SPOT — SOURCE BUNDLE (part 5 of 9)\n\nEverything in this project that does not already live on val.town. The engine is NOT here:\nseventeen files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff, verified file by file by\nscripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\n\nRESTORE (needs only node, from an empty folder). Save each part, then run this ON EACH ONE:\n\n node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(process.argv[1],\"utf8\");\n for(const s of b.split(\"\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\n\");\n const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});\n fs.writeFileSync(f,c.replace(/\\n$/,\"\"))}' PART.txt\n\nEach part is complete in itself: whole files only, no reassembly, any order.\n\nThen: node scripts/deploy.mjs --check (pulls nothing, proves the val matches)\n node scripts/build.mjs (needs engine/ back from the val first)\n node tests/run-all.mjs\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (2 of 34 files)\n tests/holiday-deposits.test.mjs 49614 bytes b7f428b6b2f7\n tests/kim-copy.test.mjs 4024 bytes d21c71175c77\n\n================================================================================================\n=====FILE tests/holiday-deposits.test.mjs =====\n// THE HOLIDAY DEPOSIT TRACKER.\n// Every case below is either a real row out of Kim's account on Aug 6 2026 or a near miss of one.\n// The failure this suite exists to prevent is telling Kim that a customer owes her $50 when they\n// do not: that is a message to a real person about money, in her name, and it is unrecoverable.\nimport * as H from \"../build/holiday-deposits.js\";\nimport { readFileSync } from \"node:fs\";\nimport { suite, ok, eq, scoped, codeOnly } from \"./_harness.mjs\";\n\nconst { t, done, header } = suite(\"holiday-deposits\");\n\nconst src = codeOnly(readFileSync(new URL(\"../engine/holiday-deposits.ts\", import.meta.url), \"utf8\"));\n\nheader(\"THE DATES, COMPUTED NOT TYPED\");\n\nt(\"H1 Thanksgiving is the fourth Thursday, worked out for any year\", () => {\n // Kim said \"third Thursday\" in her message and was wrong; we corrected her, so this had\n // better be right. Checked against the real US calendar.\n eq(H.thanksgiving(2026), \"2026-11-26\");\n eq(H.thanksgiving(2027), \"2027-11-25\");\n eq(H.thanksgiving(2028), \"2028-11-23\");\n eq(H.thanksgiving(2025), \"2025-11-27\");\n eq(H.thanksgiving(2030), \"2030-11-28\");\n return scoped(5, \"years\");\n});\n\nt(\"H2 no date is hardcoded anywhere in the module\", () => {\n // The promise made to Kim was that it is computed fresh each year so it cannot drift.\n const hardcoded = src.match(/[\"'`]20\\d\\d-\\d\\d-\\d\\d[\"'`]/g) || [];\n eq(hardcoded, [], \"a literal date is baked into the code, so it will be wrong next year\");\n return scoped(1, \"scan of the module source\");\n});\n\nt(\"H3 the windows bracket the holiday rather than landing on the day\", () => {\n const w = H.holidayWindows(2026);\n eq(w.length, 2);\n ok(w[0].from < \"2026-11-26\" && w[0].to > \"2026-11-26\", \"Thanksgiving is not inside its own window\");\n ok(w[1].from === \"2026-12-20\" && w[1].to === \"2027-01-02\", \"the new year window does not cross into January\");\n return scoped(2, \"windows\");\n});\n\nt(\"H29 on New Year's Day the season is still the one that is happening\", () => {\n // THE ERROR THIS CATCHES: rolling to the next season at midnight on 1 January drops the\n // stays that are physically in her kennels that morning, on the day she most wants the list.\n eq(H.seasonYear(\"2026-08-06\"), 2026);\n eq(H.seasonYear(\"2026-11-25\"), 2026);\n eq(H.seasonYear(\"2026-12-31\"), 2026);\n eq(H.seasonYear(\"2027-01-01\"), 2026, \"New Year's Day jumped forward a season while stays were still running\");\n eq(H.seasonYear(\"2027-01-02\"), 2026);\n eq(H.seasonYear(\"2027-01-03\"), 2027);\n return scoped(6, \"dates across the boundary\");\n});\n\nheader(\"WHO COUNTS AS A HOLIDAY STAY\");\n\n// These are real rows pulled from the Boarding Drop Off calendars on Aug 6 2026.\nconst REAL = [\n // INSIDE the Thanksgiving window on purpose. [was: 2026-11-02, which is outside every window,\n // so H5 passed whether or not the cancellation filter existed. Proved by deleting the filter\n // and watching H5 stay green.]\n { contactId: \"c-test\", title: \" Boarding Dropoff with Help Test\", startTime: \"2026-11-24T09:00:00-05:00\", dateAdded: \"2026-10-01 10:00:00\", appointmentStatus: \"cancelled\", isRecurring: false },\n { contactId: \"c-enzo\", title: \"Daycare Enzo \", startTime: \"2026-11-27T09:00:00-05:00\", dateAdded: \"2026-06-01 10:00:00\", appointmentStatus: \"confirmed\", isRecurring: true },\n { contactId: \"c-muss\", title: \"Achilles — Boarding Drop Off\", startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-07-20 14:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"c-muss\", title: \"Ghost — Boarding Drop Off\", startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-07-20 14:01:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"c-muss\", title: \"Chewy — Boarding Drop Off\", startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-07-20 14:02:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"c-flu\", title: \"Fluffy — Boarding Drop Off\", startTime: \"2027-01-01T09:00:00-05:00\", dateAdded: \"2026-08-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"c-nov\", title: \"Fluffy — Boarding Drop Off\", startTime: \"2026-11-10T09:00:00-05:00\", dateAdded: \"2026-08-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n];\n\nt(\"H4 a recurring weekly slot is never treated as a holiday stay\", () => {\n // THE ERROR THIS CATCHES: \"Daycare Enzo\" is a standing weekly booking that falls inside every\n // holiday window. Without this, Kim is told a regular owes her a deposit, repeatedly.\n const stays = H.groupIntoStays(REAL, H.holidayWindows(2026));\n ok(!stays.some((s) => s.contactId === \"c-enzo\"), \"a recurring booking was counted as a holiday stay\");\n // The Enzo row alone stopped proving this the moment daycare titles were also excluded: it is\n // kept out by EITHER rule, so it could not tell which one was working. Caught by a negative\n // control going red on the wrong test. This row is recurring AND boarding, so only the\n // recurrence filter can keep it out.\n const recurringBoarding = [{ contactId: \"c-weekly\", title: \"Bandit — Boarding Drop Off\",\n startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-01-01 10:00:00\", appointmentStatus: \"confirmed\", isRecurring: true }];\n eq(H.groupIntoStays(recurringBoarding, H.holidayWindows(2026)).length, 0,\n \"a standing weekly BOARDING slot was billed a holiday deposit\");\n return scoped(stays.length + 1, \"stays after filtering\");\n});\n\nt(\"H5 cancelled and test bookings are excluded\", () => {\n const stays = H.groupIntoStays(REAL, H.holidayWindows(2026));\n ok(!stays.some((s) => s.contactId === \"c-test\"), \"a cancelled booking was counted\");\n return scoped(1, \"cancelled booking\");\n});\n\nt(\"H6 three dogs on one day for one customer is ONE stay\", () => {\n // Real: Achilles, Ghost and Chewy all drop off on 25 November for the same person.\n const stays = H.groupIntoStays(REAL, H.holidayWindows(2026));\n const muss = stays.filter((s) => s.contactId === \"c-muss\");\n eq(muss.length, 1, \"one customer's three dogs became three separate deposit questions\");\n eq(muss[0].dogs.sort(), [\"Achilles\", \"Chewy\", \"Ghost\"]);\n eq(muss[0].bookedAt, \"2026-07-20 14:00:00\", \"the earliest booking time should survive, that is when the deposit fell due\");\n return scoped(3, \"dogs in one stay\");\n});\n\nt(\"H7 a booking outside the holiday windows is left alone\", () => {\n const stays = H.groupIntoStays(REAL, H.holidayWindows(2026));\n ok(!stays.some((s) => s.contactId === \"c-nov\"), \"a 10 November stay was pulled into the Thanksgiving window\");\n return scoped(1, \"out-of-window booking\");\n});\n\nt(\"H8 the local day is read off the string, never re-parsed\", () => {\n // A 9am drop-off on 25 Nov in New York must not become 24 Nov or 26 Nov via a timezone shift,\n // because either error moves a booking in or out of the window Kim is chasing.\n eq(H.localDay(\"2026-11-25T09:00:00-05:00\"), \"2026-11-25\");\n eq(H.localDay(\"2026-11-25T23:30:00-05:00\"), \"2026-11-25\");\n eq(H.localDay(\"2026-11-25T00:30:00-05:00\"), \"2026-11-25\");\n eq(H.localDay(null), null);\n eq(H.localDay(\"nonsense\"), null);\n // [was: /Date\\.parse|new Date\$\\s*(e|ev|event)/, which went dead the day localDay grew a branch\n // that legitimately builds a Date from a numeric epoch. It passed only because the parameter\n // happened to be named startTime. The guarantee is about the STRING path, so that is what is\n // asserted: the string branch slices, it never re-parses.]\n const fn = src.slice(src.indexOf(\"export function localDay\"), src.indexOf(\"export function seasonYear\"));\n ok(fn.length > 100, \"localDay was not found in the source, so this check is blind\");\n ok(/startTime\\.slice\\(0, 10\$/.test(fn), \"the string path no longer reads the day off the string\");\n ok(!/Date\\.parse/.test(fn), \"the string path was changed to parse the timestamp, which shifts days across midnight\");\n return scoped(5, \"time strings\");\n});\n\nheader(\"THE MONEY\");\n\nconst NOTES_REAL = [\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $355.00)\", dateAdded: \"2026-08-06T00:47:00.000Z\" },\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\", dateAdded: \"2026-08-06T00:47:01.000Z\" },\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\", dateAdded: \"2026-08-06T00:47:02.000Z\" },\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\", dateAdded: \"2026-08-06T00:47:03.000Z\" },\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\", dateAdded: \"2026-08-06T00:47:04.000Z\" },\n { body: \"--------- AI Call with: Chloe V2 --------- Call Start Time: Mar 14\", dateAdded: \"2026-03-14T13:25:00.000Z\" },\n];\n\nt(\"H9 one payment written five times is counted once\", () => {\n // THE ERROR THIS CATCHES: her real notes hold this payment five times. Summing the bodies\n // would report $1,775 against a $355 payment and mark a deposit as covered many times over.\n const p = H.parseSquarePayments(NOTES_REAL);\n eq(p.length, 1, \"the same payment id was counted more than once\");\n eq(p[0].amount, 355);\n eq(p[0].id, \"tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY\");\n return scoped(NOTES_REAL.length, \"notes read\");\n});\n\nt(\"H10 the contradictory balance figure is never used\", () => {\n // The duplicates disagree with each other: $355.00 then $0.00 four times. Reading the balance\n // would make the answer depend on which duplicate happened to be read last.\n ok(!/balance/i.test(src.replace(/^\\s*\\/\\/.*$/gm, \"\")), \"the module reads the balance figure, which contradicts itself in the real data\");\n return scoped(1, \"scan for balance use\");\n});\n\nt(\"H11 notes that are not payments are ignored\", () => {\n const p = H.parseSquarePayments([{ body: \"Called and left a voicemail\", dateAdded: \"2026-08-01T00:00:00Z\" }]);\n eq(p.length, 0);\n eq(H.parseSquarePayments(null).length, 0);\n eq(H.parseSquarePayments([]).length, 0);\n return scoped(3, \"non-payment inputs\");\n});\n\nt(\"H12 a comma in the amount does not truncate it\", () => {\n const p = H.parseSquarePayments([{ body: \"[Square] +$1,250.00 payment abc123 (balance $0.00)\", dateAdded: \"2026-08-01T00:00:00Z\" }]);\n eq(p[0].amount, 1250, \"$1,250.00 was misread, which would understate what a customer paid\");\n return scoped(1, \"amount\");\n});\n\nheader(\"WHAT KIM IS TOLD\");\n\nconst stay = { contactId: \"c1\", day: \"2026-11-25\", dogs: [\"Achilles\"], bookedAt: \"2026-07-20 14:00:00\", window: \"Thanksgiving\" };\n\nt(\"H13 a failed read is never reported as an outstanding deposit\", () => {\n // THE ERROR THIS CATCHES, and it is the one that would cost Kim a customer: an API hiccup\n // becoming \"this person has not paid\".\n const s = H.statusFor(stay, null);\n eq(s.state, \"could_not_check\");\n ok(!/not paid|owes|outstanding|unpaid/i.test(s.note), \"a failed read was described as non-payment\");\n return scoped(1, \"failed read\");\n});\n\nt(\"H14 a card payment for exactly the deposit is what clears a stay\", () => {\n // THE ONLY EVIDENCE THAT CLEARS ONE. Nothing in her CRM says what a payment was for, and two\n // earlier attempts at inferring it both cost her money, so an exact match on the deposit amount\n // is the only thing treated as an answer. Everything else is shown to her and left to her.\n const s = H.statusFor(stay, [{ amount: 50, id: \"p1\", at: \"2026-07-21T10:00:00Z\", kind: \"direct\" }]);\n eq(s.state, \"seen\");\n ok(/exactly \\$50\\.00/.test(s.note), \"the reason it was cleared is not stated\");\n ok(/Jul 21/.test(s.note), \"the date Kim would recognise is missing\");\n // And a payment of some other size does NOT clear it, however large.\n eq(H.statusFor(stay, [{ amount: 355, id: \"p2\", at: \"2026-07-21T10:00:00Z\", kind: \"direct\" }]).state, \"partial\");\n return scoped(2, \"payments\");\n});\n\nt(\"H15 a payment smaller than the deposit is called partial, not missing\", () => {\n const s = H.statusFor(stay, [{ amount: 20, id: \"p1\", at: \"2026-07-20T10:00:00Z\" }]);\n eq(s.state, \"partial\");\n ok(/\\$20\\.00/.test(s.note), \"the amount actually seen is not shown, so Kim cannot judge it\");\n return scoped(1, \"partial payment\");\n});\n\nt(\"H16 a payment from an unrelated month does not count towards this stay\", () => {\n const s = H.statusFor(stay, [{ amount: 355, id: \"p1\", at: \"2026-01-05T10:00:00Z\" }]);\n eq(s.state, \"none_seen\", \"a payment from ten months earlier was credited against this booking\");\n return scoped(1, \"out-of-window payment\");\n});\n\nt(\"H17 nothing found still says it might have been paid another way\", () => {\n const s = H.statusFor(stay, []);\n eq(s.state, \"none_seen\");\n ok(/cash|over the phone/i.test(s.note), \"the honest limit is missing, so this reads as proof of non-payment\");\n return scoped(1, \"empty result\");\n});\n\nt(\"H18 the word unpaid never reaches Kim\", () => {\n const statuses = [H.statusFor(stay, []), H.statusFor(stay, null), H.statusFor(stay, [{ amount: 20, id: \"p\", at: \"2026-07-20T10:00:00Z\" }])];\n const all = statuses.map((s) => s.note).join(\" \") + \" \" + H.depositSentence(statuses, false);\n ok(!/unpaid/i.test(all), \"the module told Kim someone is unpaid, which it cannot know\");\n ok(!/\\bowes?\\b/i.test(all.replace(/who owe you/i, \"\")), \"the module asserted somebody owes money\");\n return scoped(statuses.length + 1, \"rendered strings\");\n});\n\nt(\"H19 a dead payment feed suppresses the list instead of blaming everyone\", () => {\n // THE ERROR THIS CATCHES: the Square bridge stops, no payments are found for anybody, and the\n // page cheerfully reports that every single holiday customer has not paid.\n ok(H.feedLooksDead([[], [], [], [], [], []]), \"an entirely empty feed was not detected\");\n ok(!H.feedLooksDead([[], [], [], [], [{ amount: 50, id: \"p\", at: null }]]), \"a working feed was called dead\");\n const s = H.depositSentence([H.statusFor(stay, [])], true);\n ok(/payment feed has stopped/i.test(s), \"a dead feed is not explained to Kim\");\n ok(/held back/i.test(s), \"the list is not held back when the feed is dead\");\n return scoped(4, \"feed states\");\n});\n\nt(\"H19b two quiet customers are not evidence that Square has stopped\", () => {\n // FOUND BY WATCHING IT RUN, 6 Aug 15:41Z. Two holiday stays were booked, neither customer had a\n // Square note, and the kill switch fired: Kim would have been shown \"the payment feed has\n // stopped\" on the strength of two people. Two customers with no card payment is a normal week.\n ok(!H.feedLooksDead([[], []]), \"a two-customer sample was treated as proof of an outage\");\n ok(!H.feedLooksDead([[], [], [], []]), \"a four-customer sample was treated as proof of an outage\");\n ok(H.feedLooksDead([[], [], [], [], []]), \"a full sample of silence should still trip the switch\");\n ok(!H.feedLooksDead([]), \"nothing read at all is not evidence of anything\");\n eq(H.MIN_SAMPLE_FOR_DEAD_FEED, 5, \"the floor is not stated as a named number anyone can find\");\n return scoped(5, \"sample sizes\");\n});\n\nt(\"H20 the sentence is generated from the counts, so words and numbers cannot disagree\", () => {\n const many = [H.statusFor(stay, []), H.statusFor(stay, []), H.statusFor(stay, [{ amount: 50, id: \"p\", at: \"2026-07-21T10:00:00Z\", kind: \"direct\" }])];\n const s = H.depositSentence(many, false);\n ok(/3 holiday stays are booked/.test(s), `the count is not stated: ${s}`);\n ok(/1 has a Square payment/.test(s), \"the paid count is not stated\");\n ok(/2 are worth checking/.test(s), \"the check count is not stated\");\n ok(/shortlist/.test(s), \"the honest framing is missing\");\n return scoped(many.length, \"statuses\");\n});\n\nt(\"H21 no holiday bookings at all reads as nothing to do, not as a problem\", () => {\n const s = H.depositSentence([], false);\n ok(/nothing to check/i.test(s), \"an empty list was not explained\");\n ok(!/\\d+ holiday stays are booked/.test(s), \"it announced a count of zero\");\n return scoped(1, \"empty case\");\n});\n\nheader(\"THE SECOND PAYMENT FORMAT, FOUND LIVE ON 6 AUG\");\n\n// Both of these are verbatim rows off David Newman's contact, read live on Aug 6 2026. They are\n// the same amount under two different payment ids, four days apart in note-write time.\nconst NOTES_TWO_FORMATS = [\n { body: \"[Square] +$35.00 payment z3rQRe4iTWZE4AfSdt7fvG0mNd8YY (balance $35.00)\", dateAdded: \"2026-07-31T13:22:29.159Z\" },\n { body: \"[Square] Till payment $35.00 on 2026-07-17. Matched from Square payment 3zu7hAMbwBfEKDsUXyRuw58pztWZY via customer QJXE7X8ZM31TVEQMQS7TTF7974. Backfilled after the Customers-read token was supplied.\", dateAdded: \"2026-07-27T18:02:01.492Z\" },\n];\n\nt(\"H23 the backfill note format is money, not noise\", () => {\n // THE ERROR THIS CATCHES: the first version of the parser only knew the \"+$\" format. A customer\n // whose only Square evidence is a backfill note would have read as no payment found, and gone\n // on the shortlist. Silent, and exactly the wrong direction.\n const p = H.parseSquarePayments([NOTES_TWO_FORMATS[1]]);\n eq(p.length, 1, \"the Till/Matched-from note was not recognised as a payment at all\");\n eq(p[0].amount, 35);\n eq(p[0].id, \"3zu7hAMbwBfEKDsUXyRuw58pztWZY\");\n eq(p[0].kind, \"matched\");\n return scoped(1, \"backfill note\");\n});\n\nt(\"H24 the backfill carries the real payment date, not the day it was written down\", () => {\n // The note was written on 27 July about money taken on Jul 17y. Using the write date would\n // slide a payment out of the window it belongs to.\n const p = H.parseSquarePayments([NOTES_TWO_FORMATS[1]]);\n eq(p[0].at, \"2026-07-17\", \"the note's own write time was used instead of the payment date it states\");\n return scoped(1, \"date\");\n});\n\nt(\"H25 the same $35 under two ids is not counted as $70\", () => {\n // Nothing in the data settles whether this is one payment or two. The two readings disagree\n // about whether a $50 deposit is covered, so the reading that keeps the person ON the list to\n // be checked wins. Counting $70 would quietly drop a real customer off Kim's shortlist.\n const p = H.parseSquarePayments(NOTES_TWO_FORMATS);\n eq(p.length, 2, \"both records should survive parsing; the judgement happens later\");\n const { kept, collapsed } = H.collapseSameMoney(p);\n eq(collapsed, 1);\n eq(kept.reduce((n, x) => n + x.amount, 0), 35, \"$35 seen twice was added up to $70\");\n return scoped(2, \"records\");\n});\n\nt(\"H26 two genuinely separate payments of the same size are still two payments\", () => {\n // The mirror of H25, and the reason the rule is narrow: only a \"Matched from\" reconciliation\n // record collapses. Two direct payments of $35 are $70 and must stay $70.\n const two = [\n { amount: 35, id: \"a\", at: \"2026-07-01\", kind: \"direct\" },\n { amount: 35, id: \"b\", at: \"2026-07-02\", kind: \"direct\" },\n ];\n const { kept, collapsed } = H.collapseSameMoney(two);\n eq(collapsed, 0);\n eq(kept.length, 2, \"two real payments were merged into one\");\n return scoped(2, \"payments\");\n});\n\nt(\"H27 the same $50 under two ids is one deposit, not two payments in Kim's face\", () => {\n // Her live data holds the same money as a direct payment AND as a \"Matched from\" reconciliation\n // record, under two different ids. Listing both would have Kim reading $100 where there is $50.\n const s = H.statusFor(stay, [\n { amount: 50, id: \"a\", at: \"2026-07-21T10:00:00Z\", kind: \"direct\" },\n { amount: 50, id: \"b\", at: \"2026-07-21T10:00:00Z\", kind: \"matched\" },\n ]);\n eq(s.state, \"seen\");\n eq(s.amountSeen, 50, \"the same $50 was counted twice\");\n ok(!/other card payment/i.test(s.note), \"the duplicate record was shown to Kim as a second payment\");\n ok(!/unpaid|owes|not paid/i.test(s.note), \"the softer wording rule still applies to this sentence\");\n // A NON-DEPOSIT PAIR, because the pair above could not fail. [was: only the $50 case, where\n // amountSeen is the constant DEPOSIT and the \"other payments\" list is defined as everything\n // that is NOT $50 — so both assertions held whether or not the collapse ran at all. Deleting\n // the collapse call left all 270 assertions green. Caught by a fourth adversarial read.]\n const live = H.statusFor(stay, [\n { amount: 35, id: \"z3rQ\", at: \"2026-07-31T13:22:29Z\", kind: \"direct\" },\n { amount: 35, id: \"3zu7\", at: \"2026-07-17T00:00:00Z\", kind: \"matched\" },\n ]);\n eq(live.amountSeen, 35, \"the same $35, written by Square in both of its note formats, was counted as $70\");\n ok(/1 card payment is/.test(live.note), `the duplicate was shown to Kim as a second payment: ${live.note}`);\n return scoped(4, \"records\");\n});\n\nt(\"H28 her CRM's two spellings of the status field are both read\", () => {\n // Live on Aug 6: 4 of the 13 events on the Boarding Drop Off calendar carry `appoinmentStatus`\n // alongside the correctly spelled key. They agree today. Reading one is passing by luck.\n ok(H.eligible({ contactId: \"c1\", appointmentStatus: \"confirmed\", appoinmentStatus: \"confirmed\" }));\n ok(!H.eligible({ contactId: \"c1\", appointmentStatus: \"confirmed\", appoinmentStatus: \"cancelled\" }),\n \"a booking cancelled under the misspelled key was still counted, so a cancelled customer gets chased\");\n ok(!H.eligible({ contactId: \"c1\", appointmentStatus: \"cancelled\" }));\n ok(H.eligible({ contactId: \"c1\" }), \"a booking with no status at all should not vanish\");\n return scoped(4, \"status shapes\");\n});\n\nheader(\"WHAT THE ADVERSARIAL PASS FOUND, 6 AUG\");\n\nt(\"H30 every Thanksgiving window is made of dates that exist\", () => {\n // FOUND BY AN ADVERSARIAL READ, not by a failing test. The window edges were decimal arithmetic\n // on the day number, so any year where Thanksgiving is the 28th produced \"Nov 31\": a stay\n // dropping off on 1 December sorted ABOVE it and vanished, and the card printed \"Nov 31\" to Kim.\n let checked = 0;\n for (let y = 2026; y <= 2040; y++) {\n for (const w of H.holidayWindows(y)) {\n for (const d of [w.from, w.to]) {\n const iso = new Date(`${d}T00:00:00Z`).toISOString().slice(0, 10);\n eq(iso, d, `${y}: ${d} is not a real date`);\n checked++;\n }\n }\n const t0 = H.thanksgiving(y);\n const w0 = H.holidayWindows(y)[0];\n ok(w0.from < t0 && w0.to > t0, `${y}: Thanksgiving is not inside its own window`);\n }\n return scoped(checked, \"window edges across 15 years\");\n});\n\nt(\"H31 an appointment time sent as a number is still a day\", () => {\n // Two sibling modules that read this same endpoint already defend against an epoch startTime.\n // Returning null for it dropped EVERY stay and stored \"no holiday stays are booked\" as a fact.\n const d = H.localDay(Date.parse(\"2026-11-25T14:00:00Z\"));\n eq(d, \"2026-11-25\", \"an epoch timestamp was thrown away instead of read\");\n eq(H.localDay(Date.parse(\"2026-11-26T02:00:00Z\")), \"2026-11-25\",\n \"an epoch just after midnight UTC was not read in the business's own timezone\");\n eq(H.localDay(NaN), null);\n return scoped(3, \"numeric times\");\n});\n\nt(\"H32 her CRM's sloppier shapes still exclude the bookings they should\", () => {\n ok(!H.eligible({ contactId: \"c\", appointmentStatus: \"cancelled \" }), \"one trailing space made a cancelled booking chaseable\");\n ok(!H.eligible({ contactId: \"c\", appointmentStatus: \" Cancelled\" }));\n ok(!H.eligible({ contactId: \"c\", isRecurring: \"true\" }), \"a recurring flag sent as a string put a weekly regular on the list\");\n ok(!H.eligible({ contactId: \"c\", deleted: \"true\" }));\n // The ONLY thing keeping the weekly daycare slot off the list used to be its recurrence flag.\n ok(!H.eligible({ contactId: \"c\", title: \"Daycare Enzo \", isRecurring: false }), \"a one-off daycare booking was billed a boarding deposit\");\n ok(H.eligible({ contactId: \"c\", title: \"Achilles — Boarding Drop Off\" }));\n return scoped(6, \"shapes\");\n});\n\nt(\"H33 four ways of writing a payment that all used to read as no payment\", () => {\n const p = (b) => H.parseSquarePayments([{ body: b, dateAdded: \"2026-07-31T00:00:00Z\" }]);\n eq(p(\"[Square] +$25.00 payment aaa (balance $0.00) then [Square] +$35.00 payment bbb (balance $0.00)\").length, 2,\n \"a note holding two payments only counted one of them\");\n eq(p(\"[Square] Till payment $50.00 on 2026-07-17. Matched from Square payment 3zu7hAM\")[0]?.amount, 50,\n \"a backfill note that ends at the payment id lost the whole payment\");\n eq(p(\"[Square] +$50 payment abc\")[0]?.amount, 50, \"a whole-dollar amount was not read as money\");\n eq(p(\"[Square] Till payment $40.00 on 2026-07-01. Matched from Square payment 3zu7abc, via customer X.\")[0]?.id, \"3zu7abc\",\n \"a trailing comma became part of the payment id, so the same payment could be counted twice\");\n return scoped(4, \"note shapes\");\n});\n\nconst stayNov = { contactId: \"c1\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Achilles\"], bookedAt: \"2026-07-20 14:00:00\", window: \"Thanksgiving\" };\n\nt(\"H34 an unrelated payment months before the stay does not clear the deposit\", () => {\n // THE BIGGEST SILENT MISS. The old window ran from the booking to the drop-off, four months\n // wide, and summed everything in it. A customer's $355 training package cleared their deposit,\n // and being cleared means nobody ever looks at them again.\n const s = H.statusFor(stayNov, [{ amount: 355, id: \"pkg\", at: \"2026-08-06T00:47:00Z\", kind: \"direct\" }]);\n ok(s.state !== \"seen\", \"a training package was counted as the deposit and the customer was cleared\");\n ok(/\\$355\\.00 on Aug 6/.test(s.note), `the payment that does exist is hidden from Kim rather than named: ${s.note}`);\n ok(/not for \\$50|none of them for exactly \\$50/.test(s.note), `the note does not say why it was not treated as the deposit: ${s.note}`);\n const s2 = H.statusFor(stayNov, [\n { amount: 30, id: \"a\", at: \"2026-08-01T00:00:00Z\", kind: \"direct\" },\n { amount: 25, id: \"b\", at: \"2026-09-14T00:00:00Z\", kind: \"direct\" },\n ]);\n ok(s2.state !== \"seen\", \"two unrelated payments were added up into a deposit\");\n eq(s2.amountSeen, 55, \"the amounts Kim can see are not reported\");\n // And the real deposit is still recognised.\n eq(H.statusFor(stayNov, [{ amount: 50, id: \"dep\", at: \"2026-07-21T00:00:00Z\", kind: \"direct\" }]).state, \"seen\");\n return scoped(4, \"payment patterns\");\n});\n\nt(\"H35 a booking with no record of when it was made is unknown, not settled\", () => {\n // [was: the search window fell back to the beginning of time, so a payment from 2019 cleared it.]\n const s = H.statusFor({ ...stayNov, bookedAt: null }, [{ amount: 60, id: \"old\", at: \"2019-02-01T00:00:00Z\", kind: \"direct\" }]);\n eq(s.state, \"could_not_check\", \"a payment from years earlier settled a booking whose date we do not know\");\n ok(!/unpaid|owes|has not paid/i.test(s.note));\n return scoped(1, \"booking\");\n});\n\nt(\"H36 a stay that starts before the window but runs through it is a holiday stay\", () => {\n // A holiday boarding business is mostly people who drop off the day BEFORE they travel.\n const w = H.holidayWindows(2026);\n const before = [{ contactId: \"c-x\", title: \"Rex — Boarding Drop Off\", startTime: \"2026-12-19T09:00:00-05:00\",\n endTime: \"2026-12-27T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n const stays = H.groupIntoStays(before, w);\n eq(stays.length, 1, \"a dog boarded across Christmas was invisible because it arrived on the 19th\");\n eq(stays[0].window, \"Christmas and New Year\");\n eq(stays[0].until, \"2026-12-27\");\n // And a stay that ends before the window still does not count.\n const away = [{ ...before[0], startTime: \"2026-12-01T09:00:00-05:00\", endTime: \"2026-12-05T09:00:00-05:00\" }];\n eq(H.groupIntoStays(away, w).length, 0, \"a stay nowhere near a holiday was pulled in\");\n return scoped(4, \"stays\");\n});\n\nt(\"H37 a hyphenated dog name survives\", () => {\n // Kim reads this name before she phones somebody.\n eq(H.dogFromTitle(\"Jean-Luc — Boarding Drop Off\"), \"Jean-Luc\", \"the name was cut at the hyphen inside it\");\n eq(H.dogFromTitle(\"Achilles — Boarding Drop Off\"), \"Achilles\");\n eq(H.dogFromTitle(\"Rex - Boarding Drop Off\"), \"Rex\");\n return scoped(3, \"titles\");\n});\n\nt(\"H38 two payments are never described as one, and never added up into a deposit\", () => {\n const s = H.statusFor(stayNov, [\n { amount: 30, id: \"a\", at: \"2026-07-21T00:00:00Z\", kind: \"direct\" },\n { amount: 40, id: \"b\", at: \"2026-07-22T00:00:00Z\", kind: \"direct\" },\n ]);\n ok(s.state !== \"seen\", \"$30 and $40 were added together into a $50 deposit\");\n ok(/2 card payments are/.test(s.note), `two payments described in the singular: ${s.note}`);\n ok(/\\$30\\.00 on Jul 21/.test(s.note) && /\\$40\\.00 on Jul 22/.test(s.note), \"the two payments are not both shown\");\n return scoped(2, \"payments\");\n});\n\nt(\"H39 the dead-feed sentence does not speak for customers it never read\", () => {\n // [was: \"no Square payment has been recorded against anybody in this period\" while two of the\n // seven had failed to read. The suppressed table meant Kim could not even see which.]\n const st = [\n ...Array.from({ length: 5 }, () => H.statusFor(stayNov, [])),\n H.statusFor(stayNov, null), H.statusFor(stayNov, null),\n ];\n const s = H.depositSentence(st, true);\n ok(/any of the 5 we could check/.test(s), `the sentence claims to cover people it could not read: ${s}`);\n ok(!/against anybody/.test(s));\n return scoped(7, \"stays\");\n});\n\nt(\"H40 a deposit paid days before the booking was entered is put in front of Kim\", () => {\n // A customer phones on Jul 14y and pays $50; Kim enters the booking on the 20th. An exact-amount\n // match inside the search window is the one thing that clears a stay, so this one clears.\n const s = H.statusFor(stayNov, [{ amount: 50, id: \"early\", at: \"2026-07-14T00:00:00Z\", kind: \"direct\" }]);\n eq(s.state, \"seen\", \"a $50 card payment six days before the booking was typed in was not recognised\");\n ok(/Jul 14/.test(s.note), \"the date Kim would recognise is not in the sentence\");\n ok(!/unpaid|owes|has not paid/i.test(s.note));\n // But not one from before the search window: that is a different stay's money.\n ok(H.statusFor(stayNov, [{ amount: 50, id: \"ancient\", at: \"2026-01-14T00:00:00Z\", kind: \"direct\" }]).state !== \"seen\",\n \"a $50 payment six months earlier cleared this stay\");\n return scoped(2, \"payments\");\n});\n\nt(\"H41 the LATEST pick-up ends a stay, so one dog going home early does not delete it\", () => {\n // Her pick-up calendar carries one row per dog: \"Winnie — Boarding Pick Up\", \"Wylie — Boarding\n // Pick Up\", same contact, same day. Taking the earliest meant a family boarding straight through\n // Christmas was computed as a two-day stay in mid-December and dropped out of the window.\n const drops = [{ contactId: \"fam\", title: \"Rex — Boarding Drop Off\", startTime: \"2026-12-15T09:00:00-05:00\",\n dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n const picks = [\n { contactId: \"fam\", title: \"Bella — Boarding Pick Up\", startTime: \"2026-12-17T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"fam\", title: \"Rex — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n ];\n const stays = H.groupIntoStays(drops, H.holidayWindows(2026), picks);\n eq(stays.length, 1, \"a family boarding through Christmas was deleted because one dog went home early\");\n eq(stays[0].until, \"2026-12-27\");\n return scoped(2, \"pick-ups\");\n});\n\nt(\"H42 a stay never reaches forward and takes the next booking's pick-up\", () => {\n // [was: unbounded. A 3-night Thanksgiving stay was rendered \"Nov 25 to Dec 27\", and an ordinary\n // 6 November boarding with a stray later pick-up was dragged into a holiday window and billed\n // a deposit. Her real data has 3 contacts with drop-offs and no pick-ups and 20 the other way.]\n const drops = [\n { contactId: \"two\", title: \"A — Boarding Drop Off\", startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"two\", title: \"A — Boarding Drop Off\", startTime: \"2026-12-20T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n ];\n const picks = [{ contactId: \"two\", title: \"A — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n const stays = H.groupIntoStays(drops, H.holidayWindows(2026), picks);\n const nov = stays.find((x) => x.day === \"2026-11-25\");\n eq(nov.until, \"2026-11-25\", \"the November stay swallowed a pick-up belonging to the December booking\");\n eq(stays.find((x) => x.day === \"2026-12-20\").until, \"2026-12-27\");\n // A case where the length bound alone would NOT save us: two bookings 7 days apart and a\n // pick-up 10 days after the first, well inside MAX_STAY_DAYS. Only the next-booking bound stops\n // the first stay swallowing the second's pick-up.\n const close = H.groupIntoStays(\n [\"20\", \"27\"].map((d) => ({ contactId: \"cl\", title: \"A — Boarding Drop Off\", startTime: `2026-12-${d}T09:00:00-05:00`,\n dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false })),\n H.holidayWindows(2026),\n [{ contactId: \"cl\", title: \"A — Boarding Pick Up\", startTime: \"2026-12-30T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }]);\n eq(close.find((x) => x.day === \"2026-12-20\").until, \"2026-12-20\",\n \"the 20 December stay swallowed a pick-up that belongs to the 27 December booking\");\n eq(close.find((x) => x.day === \"2026-12-27\").until, \"2026-12-30\");\n // A STRAY PICK-UP MUST NOT DRAG AN OUT-OF-SEASON BOARDING INTO A WINDOW. Her account has about\n // twenty contacts with pick-ups and no matching drop-off, so orphan pick-up records are the\n // common case. [was: this asserted the drag HAPPENED — eq(stray.length, 1) — with a follow-up\n // whose first disjunct was false and whose second was true whenever the drag occurred. It was\n // a test pinning the bug its own comment said had been fixed. Caught by a third adversarial\n // read, which applied the correct bound and watched this test go red for it.]\n const stray = H.groupIntoStays(\n [{ contactId: \"s\", title: \"B — Boarding Drop Off\", startTime: \"2026-11-06T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }],\n H.holidayWindows(2026),\n [{ contactId: \"s\", title: \"B — Boarding Pick Up\", startTime: \"2027-02-01T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }]);\n eq(stray.length, 0, \"a 6 November boarding was stretched to February by an orphan pick-up and put on the holiday shortlist\");\n // And a stay of a believable length still pairs.\n const real = H.groupIntoStays(\n [{ contactId: \"r\", title: \"C — Boarding Drop Off\", startTime: \"2026-12-18T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }],\n H.holidayWindows(2026),\n [{ contactId: \"r\", title: \"C — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }]);\n eq(real.length, 1, \"a nine-night Christmas stay was thrown out by the length bound\");\n return scoped(4, \"stays\");\n});\n\nt(\"H43 a cancelled or recurring pick-up is not allowed to end a stay\", () => {\n const drops = [{ contactId: \"c\", title: \"A — Boarding Drop Off\", startTime: \"2026-12-18T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n const bad = [\n { contactId: \"c\", title: \"A — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"cancelled\", isRecurring: false },\n { contactId: \"c\", title: \" Boarding Pickup with David Newman\", startTime: \"2026-12-25T16:30:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: true },\n ];\n eq(H.groupIntoStays(drops, H.holidayWindows(2026), bad).length, 0,\n \"a cancelled or recurring pick-up was used to stretch a stay into a holiday window\");\n const good = [{ contactId: \"c\", title: \"A — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n eq(H.groupIntoStays(drops, H.holidayWindows(2026), good).length, 1);\n return scoped(3, \"pick-ups\");\n});\n\nt(\"H44 a real boarding booking with the word daycare in its title is not thrown away\", () => {\n // Her titles carry free text: \"drop off: Mia and Gemma \", \"Boarding drop off Harry\". A title\n // that says BOTH is a boarding booking with a note on it.\n ok(H.eligible({ contactId: \"c\", title: \"Boarding + daycare drop off with Dan Bonner\" }),\n \"a real boarding stay was excluded because somebody typed daycare in the title\");\n ok(H.eligible({ contactId: \"c\", title: \"Boarding Dropoff (daycare rate) with Gina Wright\" }));\n ok(!H.eligible({ contactId: \"c\", title: \"Daycare Enzo \" }), \"the daycare-only slot should still be excluded\");\n return scoped(3, \"titles\");\n});\n\nt(\"H45 the test-record label does not fire on a real surname\", () => {\n ok(!H.looksLikeTestRecord(\"Sarah Tester\"), \"a customer called Tester was labelled a test record on Kim's screen\");\n ok(!H.looksLikeTestRecord(\"Bob Testa\"));\n ok(!H.looksLikeTestRecord(\"Ann Testerman\"));\n ok(H.looksLikeTestRecord(\"help test\"), \"the record that really is a test was not flagged\");\n ok(H.looksLikeTestRecord(\"ZZTEST PuppyPath-Dummy\"));\n return scoped(5, \"names\");\n});\n\nt(\"H46 the dead-feed sentence never says it checked nobody\", () => {\n const allUnknown = [H.statusFor(stayNov, null), H.statusFor(stayNov, null)];\n const s = H.depositSentence(allUnknown, true);\n ok(!/any of the 0/.test(s), `the sentence reads as broken: ${s}`);\n ok(/none of them could be checked/i.test(s), \"the honest version of this case is missing\");\n return scoped(2, \"stays\");\n});\n\nt(\"H47 the dead-feed switch counts customers, not bookings\", () => {\n // [was: one entry per stay, so a single regular with five holiday drop-offs and a habit of\n // paying cash suppressed the whole card on their own. Her data has one contact with 24.]\n const one = new Map([[\"only-customer\", []]]);\n ok(!H.feedLooksDead(one), \"one customer with no card payment was treated as an outage\");\n const five = new Map([[\"a\", []], [\"b\", []], [\"c\", []], [\"d\", []], [\"e\", []]]);\n ok(H.feedLooksDead(five), \"five customers with no card payment anywhere did not trip the switch\");\n const mixed = new Map([[\"a\", []], [\"b\", []], [\"c\", []], [\"d\", []], [\"e\", [{ amount: 50, id: \"p\", at: null, kind: \"direct\" }]]]);\n ok(!H.feedLooksDead(mixed), \"a working feed was called dead\");\n return scoped(3, \"samples\");\n});\n\nt(\"H48 one $50 deposit settles ONE stay, not every booking that customer has\", () => {\n // THE MOST EXPENSIVE BUG FOUND ALL DAY, and the ordinary case rather than an edge: a regular\n // books Thanksgiving and Christmas in the same phone call and pays one $50 deposit. Both search\n // windows are anchored on the same booking date, so both stays saw the same payment and both\n // went green. Kim was owed $100, $50 arrived, and neither row reached the shortlist.\n const two = [\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" },\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], bookedAt: \"2026-10-01 09:00:00\", window: \"Christmas and New Year\" },\n ];\n const one = [{ amount: 50, id: \"onlyfifty\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" }];\n const out = H.statusesForCustomer(two, one);\n eq(out.filter((s) => s.state === \"seen\").length, 1, \"one $50 payment settled both of this customer's holiday stays\");\n eq(out[0].state, \"seen\", \"the payment should settle the earlier stay\");\n ok(out[1].state !== \"seen\", \"the second stay was settled by money that had already been spent\");\n // Two deposits settle two stays.\n const both = H.statusesForCustomer(two, [...one, { amount: 50, id: \"second\", at: \"2026-10-06T00:00:00Z\", kind: \"direct\" }]);\n eq(both.filter((s) => s.state === \"seen\").length, 2, \"two real $50 deposits did not settle two stays\");\n return scoped(2, \"stays\");\n});\n\nt(\"H49 a payment after the dogs go home does not settle the stay\", () => {\n // The upper edge of the search window. [was: unguarded — it could be stretched to a year\n // without a single test moving, which is how \"any payment ever\" comes back.]\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n eq(H.statusFor(st, [{ amount: 50, id: \"a\", at: \"2026-11-29T00:00:00Z\", kind: \"direct\" }]).state, \"seen\",\n \"a deposit settled the day after pick-up should still count\");\n ok(H.statusFor(st, [{ amount: 50, id: \"b\", at: \"2026-12-15T00:00:00Z\", kind: \"direct\" }]).state !== \"seen\",\n \"a payment weeks after the dogs went home was counted as this stay's deposit\");\n ok(H.statusFor(st, [{ amount: 50, id: \"c\", at: \"2027-06-01T00:00:00Z\", kind: \"direct\" }]).state !== \"seen\",\n \"a payment the following summer was counted as this stay's deposit\");\n return scoped(3, \"payment dates\");\n});\n\nt(\"H50 a lone payment that is not the deposit reads as English\", () => {\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n const n = H.statusFor(st, [{ amount: 100, id: \"a\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" }]).note;\n ok(!/none of them/.test(n), `\"none of them\" about a single payment: ${n}`);\n ok(!/among them/.test(n), `\"among them\" about a single payment: ${n}`);\n ok(/\\$100\\.00 on Oct 5/.test(n), \"the payment is not shown\");\n return scoped(1, \"note\");\n});\n\nt(\"H51 the headline counts every row the table shows as worth a look\", () => {\n // [was: unguarded. Dropping the partial rows from the count gave \"1 is worth checking\" above a\n // table showing two rows both labelled Worth a look.]\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n const mixed = [\n H.statusFor(st, []), // none_seen\n H.statusFor(st, [{ amount: 100, id: \"a\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" }]), // partial\n ];\n const s = H.depositSentence(mixed, false);\n ok(/2 are worth checking/.test(s), `the headline does not count both rows the table shows: ${s}`);\n return scoped(2, \"rows\");\n});\n\nt(\"H52 a deposit Square wrote twice does not settle two different stays\", () => {\n // THE SAME MONEY BUG, RE-ENTERING THROUGH A CRACK. Round three stopped one $50 settling two\n // stays. It came straight back when the payment was a direct+matched pair: the collapse ran\n // inside the per-stay check while the allocator marked only the surviving id as spent, so the\n // folded twin was still on the table for the next stay. Both rows went green quoting two\n // different dates, so it read as two deposits. Kim owed $100, $50 arrived, nothing to chase.\n const two = [\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-09-28 09:00:00\", window: \"Thanksgiving\" },\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], bookedAt: \"2026-09-28 09:00:00\", window: \"Christmas and New Year\" },\n ];\n const twinned = [\n { amount: 50, id: \"z3rQRe4iTWZE4AfSdt7fvG0mNd8YY\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" },\n { amount: 50, id: \"3zu7hAMbwBfEKDsUXyRuw58pztWZY\", at: \"2026-10-01T00:00:00Z\", kind: \"matched\" },\n ];\n const out = H.statusesForCustomer(two, twinned);\n eq(out.filter((s) => s.state === \"seen\").length, 1,\n \"one $50 deposit, written by Square in both of its formats, settled two separate holiday stays\");\n return scoped(2, \"stays\");\n});\n\nt(\"H53 the money goes to the stay that came first, not to whichever way the array arrived\", () => {\n // [was: unpinned. Reversing the allocation order left every assertion green, so the documented\n // rule was a comment rather than a guarantee.]\n const two = [\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], bookedAt: \"2026-09-28 09:00:00\", window: \"Christmas and New Year\" },\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-09-28 09:00:00\", window: \"Thanksgiving\" },\n ];\n const out = H.statusesForCustomer(two, [{ amount: 50, id: \"one\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" }]);\n eq(out[0].stay.day, \"2026-11-25\", \"the stays are not being put in date order before the money is handed out\");\n eq(out[0].state, \"seen\", \"the payment did not go to the earlier stay\");\n ok(out[1].state !== \"seen\");\n return scoped(2, \"stays\");\n});\n\nt(\"H54 the season turns over on her clock, not on Greenwich\", () => {\n // Her business is in New York. Rolling on the UTC date empties the card at 8pm on 2 January,\n // five hours early, with dogs still in the kennels — and the empty result is then stored.\n eq(H.businessDay(\"2027-01-03T01:00:00.000Z\"), \"2027-01-02\", \"8pm on 2 January in New York was read as 3 January\");\n eq(H.seasonYear(H.businessDay(\"2027-01-03T01:00:00.000Z\")), 2026, \"the season rolled over while the New Year stays were still running\");\n eq(H.seasonYear(H.businessDay(\"2027-01-03T13:00:00.000Z\")), 2027, \"the season should have moved on by the afternoon of the 3rd\");\n eq(H.businessDay(\"nonsense\").length, 8);\n return scoped(4, \"moments\");\n});\n\nt(\"H55 money on a settled row is still shown, so Kim can see what else was paid\", () => {\n // [was: unpinned. Deleting the whole sentence left the suite green, and it is Kim's only view\n // of other money on a row that has already been cleared.]\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n const n = H.statusFor(st, [\n { amount: 50, id: \"dep\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" },\n { amount: 240, id: \"inv\", at: \"2026-10-07T00:00:00Z\", kind: \"direct\" },\n ]).note;\n ok(/other card payment/i.test(n), `other money on a cleared row is hidden: ${n}`);\n ok(/\\$240\\.00 on Oct 7/.test(n), \"the amount and date of the other payment are not shown\");\n return scoped(2, \"payments\");\n});\n\nt(\"H56 two settled stays never quote the same payment back to Kim\", () => {\n // The allocator debits one record while the note quotes another, so both rows can cite the same\n // date — which is exactly what \"one payment settled two stays\" looks like on the page, whether\n // or not the underlying count is right. Two backfill records and one direct payment produce it.\n const two = [\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-09-28 09:00:00\", window: \"Thanksgiving\" },\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], bookedAt: \"2026-09-28 09:00:00\", window: \"Christmas and New Year\" },\n ];\n const messy = [\n { amount: 50, id: \"matchedA\", at: \"2026-10-01T00:00:00Z\", kind: \"matched\" },\n { amount: 50, id: \"matchedB\", at: \"2026-10-02T00:00:00Z\", kind: \"matched\" },\n { amount: 50, id: \"directC\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" },\n ];\n const out = H.statusesForCustomer(two, messy);\n const quoted = out.filter((x) => x.state === \"seen\").map((x) => (/on ([A-Z][a-z]{2} \\d+)/.exec(x.note) || [])[1]);\n eq(quoted.length, new Set(quoted).size,\n `two settled stays quote the same payment: ${JSON.stringify(quoted)}`);\n return scoped(out.length, \"stays\");\n});\n\nt(\"H57 two backfill records and one payment are still one deposit\", () => {\n // THE SAME MONEY BUG, ONE LEVEL DOWN AGAIN. The collapse used to be one-for-one: each backfill\n // record consumed one direct payment of the same amount, so with TWO backfills and ONE payment\n // the second backfill survived still sharing an amount with the direct. The per-stay check then\n // folded it a second time — declaring them one payment — while the allocator had only ever\n // spent one id, leaving the other free to settle the next stay. Making the collapse idempotent\n // is what closes it: after one pass, no surviving backfill shares an amount with a payment.\n const messy = [\n { amount: 50, id: \"z3rQ\", at: \"2026-10-07T00:00:00Z\", kind: \"direct\" },\n { amount: 50, id: \"3zu7\", at: \"2026-10-07T00:00:00Z\", kind: \"matched\" },\n { amount: 50, id: \"9kQp\", at: \"2026-10-01T00:00:00Z\", kind: \"matched\" },\n ];\n const once = H.collapseSameMoney(messy);\n const twice = H.collapseSameMoney(once.kept);\n eq(twice.collapsed, 0, \"a second pass still finds something to collapse, so the layers above disagree about how much money there is\");\n eq(once.kept.length, 1);\n const two = [\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], bookedAt: \"2026-09-28 09:00:00\", window: \"Thanksgiving\" },\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], bookedAt: \"2026-09-28 09:00:00\", window: \"Christmas and New Year\" },\n ];\n eq(H.statusesForCustomer(two, messy).filter((x) => x.state === \"seen\").length, 1,\n \"one $50, written once as a payment and twice as a backfill, settled two separate holiday stays\");\n return scoped(3, \"records\");\n});\n\nheader(\"WHAT IT MUST NEVER DO\");\n\nt(\"H22 the module cannot write to the CRM\", () => {\n // Structural, not a promise in a comment. addTag() in this engine is not TEST_MODE guarded and\n // this account has a workflow that turns a tag into do-not-disturb on six channels.\n ok(!/\"POST\"|'POST'|`POST`/.test(src), \"the module contains a POST\");\n ok(!/\"PUT\"|'PUT'|\"PATCH\"|'PATCH'|\"DELETE\"|'DELETE'/.test(src), \"the module contains a write verb\");\n ok(!/addTag|createTask|sendSms|sendEmail|upsert/.test(src), \"the module reaches a function that changes her account\");\n ok(!/fetch\\s*\\(/.test(src), \"the module fetches directly instead of being handed data it can be tested against\");\n return scoped(4, \"structural guarantees\");\n});\n\ndone();\n\n\n=====FILE tests/kim-copy.test.mjs =====\n// KIM'S OWN CORRECTIONS, PINNED. v2.0, 5 Aug 2026.\n// Every rule here is something she asked for in writing on 4 August. They are tests because a copy\n// instruction that lives only in a chat message gets quietly undone by the next edit, and she\n// should never have to ask twice.\nimport * as E from \"../build/engine.js\";\nimport { readFileSync } from \"node:fs\";\nimport { suite, ok, eq, scoped, TRACKS, allMessages, msgText } from \"./_harness.mjs\";\nconst { t, done, header } = suite(\"kim-copy\");\n\nconst all = allMessages(E);\nconst hits = (re) => all.filter((m) => re.test(msgText(m))).map((m) => `${m.track}/${m.id}`);\n\nheader(\"WHAT KIM ASKED FOR\");\n\nt(\"K-a no dog-name placeholder survives anywhere\", () => {\n // \"we haven't always got the name and so if we have a placeholder for the puppies name, it\n // reads weird when there's no puppy in there\" - Kim, 6:32 PM 4 Aug\n eq(hits(/\\{\\{\\s*DOG_NAME\\s*\\}\\}/), []);\n return scoped(all.length, \"messages checked\");\n});\nt(\"K-a2 the person's name is still used, so removing the dog name did not go impersonal\", () => {\n const n = all.filter((m) => /\\{\\{FIRST_NAME\\}\\}/.test(msgText(m))).length;\n ok(n >= all.length * 0.8, `only ${n}/${all.length} greet the person by name`);\n return `${n}/${all.length} greet by name`;\n});\nt(\"K-b daycare appears nowhere: they do not offer it\", () => {\n eq(hits(/day\\s*care/i), []);\n return scoped(all.length, \"messages checked\");\n});\nt(\"K-c American English: potty not toilet, yard not garden\", () => {\n eq(hits(/\\btoilet/i), []); eq(hits(/\\bgarden/i), []);\n ok(hits(/potty/i).length > 0, \"potty training vanished rather than being renamed\");\n return scoped(all.length, \"messages checked\");\n});\nt(\"K-d no British spelling, INCLUDING in render-time constants\", () => {\n const re = /\\b(behaviour|realise|realising|colour|whilst|enquir|apologise|organis|neighbour|favourite|practise\\b|licence\\b|cosy|kerb|aluminium|dialled|theoris)/i;\n eq(hits(re), []);\n // the failure this catches: EMAIL_OPTOUT read \"you enquired with The Dogs Spot\" and was appended\n // to every email at render time, where a scan of the template arrays could never see it\n const src = readFileSync(new URL(\"../engine/puppy_path_v1.1.ts\", import.meta.url), \"utf8\");\n const consts = src.match(/const (SMS_OPTOUT|EMAIL_OPTOUT)[\\s\\S]{0,400}?;/g) || [];\n ok(consts.length >= 2, `expected both opt-out constants, found ${consts.length}`);\n for (const c of consts) ok(!re.test(c), `British spelling in a render-time constant: ${c.slice(0, 90)}`);\n return `${all.length} templates + ${consts.length} appended constants`;\n});\nt(\"K-e the no-show text uses her word, schedule, not sort\", () => {\n const m = all.find((x) => x.id === \"branch_a-1\");\n ok(m, \"branch_a-1 missing\");\n ok(/schedule it/.test(m.bodyTemplate), \"her wording was reverted\");\n ok(!/sort it/.test(m.bodyTemplate), \"'sort it' is back\");\n return \"1 message\";\n});\nt(\"K-f the no-show email is her rewrite, near enough word for word\", () => {\n const m = all.find((x) => x.id === \"branch_a-2\");\n ok(m, \"branch_a-2 missing\");\n const phrases = [\"I noticed we had a Pup Talk scheduled, but we missed each other\", \"I know life gets busy\",\n \"quick, no-pressure call\", \"see whether training with us would be a good fit\",\n \"if we're not the right fit, I'll tell you that too\", \"won't keep bugging you\"];\n for (const p of phrases) ok(m.bodyTemplate.includes(p), `her phrase missing: \"${p}\"`);\n ok(!/daycare/i.test(m.bodyTemplate), \"daycare survived in the very message she rewrote to remove it\");\n return scoped(phrases.length, \"of her phrases verified\");\n});\nt(\"K-g no em-dashes reach a customer\", () => { eq(hits(/—/), []); return scoped(all.length, \"messages checked\"); });\nt(\"K-h no price quoted, grooming never offered\", () => {\n eq(hits(/groom/i), []); eq(hits(/\\$\\d/), []);\n return scoped(all.length, \"messages checked\");\n});\nt(\"K-i 'Pup Talk' everywhere, 'discovery call' nowhere\", () => {\n eq(hits(/discovery call/i), []);\n return scoped(all.length, \"messages checked\");\n});\ndone();\n\n","THE DOGS SPOT — SOURCE BUNDLE (part 5 of 9)\n\nEverything in this project that does not already live on val.town. The engine is NOT here:\nseventeen files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff, verified file by file by\nscripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\n\nRESTORE (needs only node, from an empty folder). Save each part, then run this ON EACH ONE:\n\n node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(process.argv[1],\"utf8\");\n for(const s of b.split(\"\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\n\");\n const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});\n fs.writeFileSync(f,c.replace(/\\n$/,\"\"))}' PART.txt\n\nEach part is complete in itself: whole files only, no reassembly, any order.\n\nThen: node scripts/deploy.mjs --check (pulls nothing, proves the val matches)\n node scripts/build.mjs (needs engine/ back from the val first)\n node tests/run-all.mjs\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (2 of 34 files)\n tests/holiday-deposits.test.mjs 54315 bytes fbf1559d28ec\n tests/kim-copy.test.mjs 4024 bytes d21c71175c77\n\n================================================================================================\n=====FILE tests/holiday-deposits.test.mjs =====\n// THE HOLIDAY DEPOSIT TRACKER.\n// Every case below is either a real row out of Kim's account on Aug 6 2026 or a near miss of one.\n// The failure this suite exists to prevent is telling Kim that a customer owes her $50 when they\n// do not: that is a message to a real person about money, in her name, and it is unrecoverable.\nimport * as H from \"../build/holiday-deposits.js\";\nimport { readFileSync } from \"node:fs\";\nimport { suite, ok, eq, scoped, codeOnly } from \"./_harness.mjs\";\n\nconst { t, done, header } = suite(\"holiday-deposits\");\n\nconst src = codeOnly(readFileSync(new URL(\"../engine/holiday-deposits.ts\", import.meta.url), \"utf8\"));\n\nheader(\"THE DATES, COMPUTED NOT TYPED\");\n\nt(\"H1 Thanksgiving is the fourth Thursday, worked out for any year\", () => {\n // Kim said \"third Thursday\" in her message and was wrong; we corrected her, so this had\n // better be right. Checked against the real US calendar.\n eq(H.thanksgiving(2026), \"2026-11-26\");\n eq(H.thanksgiving(2027), \"2027-11-25\");\n eq(H.thanksgiving(2028), \"2028-11-23\");\n eq(H.thanksgiving(2025), \"2025-11-27\");\n eq(H.thanksgiving(2030), \"2030-11-28\");\n return scoped(5, \"years\");\n});\n\nt(\"H2 no date is hardcoded anywhere in the module\", () => {\n // The promise made to Kim was that it is computed fresh each year so it cannot drift.\n const hardcoded = src.match(/[\"'`]20\\d\\d-\\d\\d-\\d\\d[\"'`]/g) || [];\n eq(hardcoded, [], \"a literal date is baked into the code, so it will be wrong next year\");\n return scoped(1, \"scan of the module source\");\n});\n\nt(\"H3 the windows bracket the holiday rather than landing on the day\", () => {\n const w = H.holidayWindows(2026);\n eq(w.length, 2);\n ok(w[0].from < \"2026-11-26\" && w[0].to > \"2026-11-26\", \"Thanksgiving is not inside its own window\");\n ok(w[1].from === \"2026-12-20\" && w[1].to === \"2027-01-02\", \"the new year window does not cross into January\");\n return scoped(2, \"windows\");\n});\n\nt(\"H29 on New Year's Day the season is still the one that is happening\", () => {\n // THE ERROR THIS CATCHES: rolling to the next season at midnight on 1 January drops the\n // stays that are physically in her kennels that morning, on the day she most wants the list.\n eq(H.seasonYear(\"2026-08-06\"), 2026);\n eq(H.seasonYear(\"2026-11-25\"), 2026);\n eq(H.seasonYear(\"2026-12-31\"), 2026);\n eq(H.seasonYear(\"2027-01-01\"), 2026, \"New Year's Day jumped forward a season while stays were still running\");\n eq(H.seasonYear(\"2027-01-02\"), 2026);\n eq(H.seasonYear(\"2027-01-03\"), 2027);\n return scoped(6, \"dates across the boundary\");\n});\n\nheader(\"WHO COUNTS AS A HOLIDAY STAY\");\n\n// These are real rows pulled from the Boarding Drop Off calendars on Aug 6 2026.\nconst REAL = [\n // INSIDE the Thanksgiving window on purpose. [was: 2026-11-02, which is outside every window,\n // so H5 passed whether or not the cancellation filter existed. Proved by deleting the filter\n // and watching H5 stay green.]\n { contactId: \"c-test\", title: \" Boarding Dropoff with Help Test\", startTime: \"2026-11-24T09:00:00-05:00\", dateAdded: \"2026-10-01 10:00:00\", appointmentStatus: \"cancelled\", isRecurring: false },\n { contactId: \"c-enzo\", title: \"Daycare Enzo \", startTime: \"2026-11-27T09:00:00-05:00\", dateAdded: \"2026-06-01 10:00:00\", appointmentStatus: \"confirmed\", isRecurring: true },\n { contactId: \"c-muss\", title: \"Achilles — Boarding Drop Off\", startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-07-20 14:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"c-muss\", title: \"Ghost — Boarding Drop Off\", startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-07-20 14:01:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"c-muss\", title: \"Chewy — Boarding Drop Off\", startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-07-20 14:02:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"c-flu\", title: \"Fluffy — Boarding Drop Off\", startTime: \"2027-01-01T09:00:00-05:00\", dateAdded: \"2026-08-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"c-nov\", title: \"Fluffy — Boarding Drop Off\", startTime: \"2026-11-10T09:00:00-05:00\", dateAdded: \"2026-08-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n];\n\nt(\"H4 a recurring weekly slot is never treated as a holiday stay\", () => {\n // THE ERROR THIS CATCHES: \"Daycare Enzo\" is a standing weekly booking that falls inside every\n // holiday window. Without this, Kim is told a regular owes her a deposit, repeatedly.\n const stays = H.groupIntoStays(REAL, H.holidayWindows(2026));\n ok(!stays.some((s) => s.contactId === \"c-enzo\"), \"a recurring booking was counted as a holiday stay\");\n // The Enzo row alone stopped proving this the moment daycare titles were also excluded: it is\n // kept out by EITHER rule, so it could not tell which one was working. Caught by a negative\n // control going red on the wrong test. This row is recurring AND boarding, so only the\n // recurrence filter can keep it out.\n const recurringBoarding = [{ contactId: \"c-weekly\", title: \"Bandit — Boarding Drop Off\",\n startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-01-01 10:00:00\", appointmentStatus: \"confirmed\", isRecurring: true }];\n eq(H.groupIntoStays(recurringBoarding, H.holidayWindows(2026)).length, 0,\n \"a standing weekly BOARDING slot was billed a holiday deposit\");\n return scoped(stays.length + 1, \"stays after filtering\");\n});\n\nt(\"H5 cancelled and test bookings are excluded\", () => {\n const stays = H.groupIntoStays(REAL, H.holidayWindows(2026));\n ok(!stays.some((s) => s.contactId === \"c-test\"), \"a cancelled booking was counted\");\n return scoped(1, \"cancelled booking\");\n});\n\nt(\"H6 three dogs on one day for one customer is ONE stay\", () => {\n // Real: Achilles, Ghost and Chewy all drop off on 25 November for the same person.\n const stays = H.groupIntoStays(REAL, H.holidayWindows(2026));\n const muss = stays.filter((s) => s.contactId === \"c-muss\");\n eq(muss.length, 1, \"one customer's three dogs became three separate deposit questions\");\n eq(muss[0].dogs.sort(), [\"Achilles\", \"Chewy\", \"Ghost\"]);\n eq(muss[0].bookedAt, \"2026-07-20 14:00:00\", \"the earliest booking time should survive, that is when the deposit fell due\");\n return scoped(3, \"dogs in one stay\");\n});\n\nt(\"H7 a booking outside the holiday windows is left alone\", () => {\n const stays = H.groupIntoStays(REAL, H.holidayWindows(2026));\n ok(!stays.some((s) => s.contactId === \"c-nov\"), \"a 10 November stay was pulled into the Thanksgiving window\");\n return scoped(1, \"out-of-window booking\");\n});\n\nt(\"H8 the local day is read off the string, never re-parsed\", () => {\n // A 9am drop-off on 25 Nov in New York must not become 24 Nov or 26 Nov via a timezone shift,\n // because either error moves a booking in or out of the window Kim is chasing.\n eq(H.localDay(\"2026-11-25T09:00:00-05:00\"), \"2026-11-25\");\n eq(H.localDay(\"2026-11-25T23:30:00-05:00\"), \"2026-11-25\");\n eq(H.localDay(\"2026-11-25T00:30:00-05:00\"), \"2026-11-25\");\n eq(H.localDay(null), null);\n eq(H.localDay(\"nonsense\"), null);\n // [was: /Date\\.parse|new Date\$\\s*(e|ev|event)/, which went dead the day localDay grew a branch\n // that legitimately builds a Date from a numeric epoch. It passed only because the parameter\n // happened to be named startTime. The guarantee is about the STRING path, so that is what is\n // asserted: the string branch slices, it never re-parses.]\n const fn = src.slice(src.indexOf(\"export function localDay\"), src.indexOf(\"export function seasonYear\"));\n ok(fn.length > 100, \"localDay was not found in the source, so this check is blind\");\n ok(/startTime\\.slice\\(0, 10\$/.test(fn), \"the string path no longer reads the day off the string\");\n ok(!/Date\\.parse/.test(fn), \"the string path was changed to parse the timestamp, which shifts days across midnight\");\n return scoped(5, \"time strings\");\n});\n\nheader(\"THE MONEY\");\n\nconst NOTES_REAL = [\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $355.00)\", dateAdded: \"2026-08-06T00:47:00.000Z\" },\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\", dateAdded: \"2026-08-06T00:47:01.000Z\" },\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\", dateAdded: \"2026-08-06T00:47:02.000Z\" },\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\", dateAdded: \"2026-08-06T00:47:03.000Z\" },\n { body: \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\", dateAdded: \"2026-08-06T00:47:04.000Z\" },\n { body: \"--------- AI Call with: Chloe V2 --------- Call Start Time: Mar 14\", dateAdded: \"2026-03-14T13:25:00.000Z\" },\n];\n\nt(\"H9 one payment written five times is counted once\", () => {\n // THE ERROR THIS CATCHES: her real notes hold this payment five times. Summing the bodies\n // would report $1,775 against a $355 payment and mark a deposit as covered many times over.\n const p = H.parseSquarePayments(NOTES_REAL);\n eq(p.length, 1, \"the same payment id was counted more than once\");\n eq(p[0].amount, 355);\n eq(p[0].id, \"tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY\");\n return scoped(NOTES_REAL.length, \"notes read\");\n});\n\nt(\"H10 the contradictory balance figure is never used\", () => {\n // The duplicates disagree with each other: $355.00 then $0.00 four times. Reading the balance\n // would make the answer depend on which duplicate happened to be read last.\n ok(!/balance/i.test(src.replace(/^\\s*\\/\\/.*$/gm, \"\")), \"the module reads the balance figure, which contradicts itself in the real data\");\n return scoped(1, \"scan for balance use\");\n});\n\nt(\"H11 notes that are not payments are ignored\", () => {\n const p = H.parseSquarePayments([{ body: \"Called and left a voicemail\", dateAdded: \"2026-08-01T00:00:00Z\" }]);\n eq(p.length, 0);\n eq(H.parseSquarePayments(null).length, 0);\n eq(H.parseSquarePayments([]).length, 0);\n return scoped(3, \"non-payment inputs\");\n});\n\nt(\"H12 a comma in the amount does not truncate it\", () => {\n const p = H.parseSquarePayments([{ body: \"[Square] +$1,250.00 payment abc123 (balance $0.00)\", dateAdded: \"2026-08-01T00:00:00Z\" }]);\n eq(p[0].amount, 1250, \"$1,250.00 was misread, which would understate what a customer paid\");\n return scoped(1, \"amount\");\n});\n\nheader(\"WHAT KIM IS TOLD\");\n\nconst stay = { contactId: \"c1\", day: \"2026-11-25\", dogs: [\"Achilles\"], dogCount: 1, bookedAt: \"2026-07-20 14:00:00\", window: \"Thanksgiving\" };\n\nt(\"H13 a failed read is never reported as an outstanding deposit\", () => {\n // THE ERROR THIS CATCHES, and it is the one that would cost Kim a customer: an API hiccup\n // becoming \"this person has not paid\".\n const s = H.statusFor(stay, null);\n eq(s.state, \"could_not_check\");\n ok(!/not paid|owes|outstanding|unpaid/i.test(s.note), \"a failed read was described as non-payment\");\n return scoped(1, \"failed read\");\n});\n\nt(\"H14 a card payment for exactly the deposit is what clears a stay\", () => {\n // THE ONLY EVIDENCE THAT CLEARS ONE. Nothing in her CRM says what a payment was for, and two\n // earlier attempts at inferring it both cost her money, so an exact match on the deposit amount\n // is the only thing treated as an answer. Everything else is shown to her and left to her.\n const s = H.statusFor(stay, [{ amount: 50, id: \"p1\", at: \"2026-07-21T10:00:00Z\", kind: \"direct\" }]);\n eq(s.state, \"seen\");\n ok(/exactly \\$50\\.00/.test(s.note), \"the reason it was cleared is not stated\");\n ok(/Jul 21/.test(s.note), \"the date Kim would recognise is missing\");\n // And a payment of some other size does NOT clear it, however large.\n eq(H.statusFor(stay, [{ amount: 355, id: \"p2\", at: \"2026-07-21T10:00:00Z\", kind: \"direct\" }]).state, \"partial\");\n return scoped(2, \"payments\");\n});\n\nt(\"H15 a payment smaller than the deposit is called partial, not missing\", () => {\n const s = H.statusFor(stay, [{ amount: 20, id: \"p1\", at: \"2026-07-20T10:00:00Z\" }]);\n eq(s.state, \"partial\");\n ok(/\\$20\\.00/.test(s.note), \"the amount actually seen is not shown, so Kim cannot judge it\");\n return scoped(1, \"partial payment\");\n});\n\nt(\"H16 a payment from an unrelated month does not count towards this stay\", () => {\n const s = H.statusFor(stay, [{ amount: 355, id: \"p1\", at: \"2026-01-05T10:00:00Z\" }]);\n eq(s.state, \"none_seen\", \"a payment from ten months earlier was credited against this booking\");\n return scoped(1, \"out-of-window payment\");\n});\n\nt(\"H17 nothing found still says it might have been paid another way\", () => {\n const s = H.statusFor(stay, []);\n eq(s.state, \"none_seen\");\n ok(/cash|over the phone/i.test(s.note), \"the honest limit is missing, so this reads as proof of non-payment\");\n return scoped(1, \"empty result\");\n});\n\nt(\"H18 the word unpaid never reaches Kim\", () => {\n const statuses = [H.statusFor(stay, []), H.statusFor(stay, null), H.statusFor(stay, [{ amount: 20, id: \"p\", at: \"2026-07-20T10:00:00Z\" }])];\n const all = statuses.map((s) => s.note).join(\" \") + \" \" + H.depositSentence(statuses, false);\n ok(!/unpaid/i.test(all), \"the module told Kim someone is unpaid, which it cannot know\");\n ok(!/\\bowes?\\b/i.test(all.replace(/who owe you/i, \"\")), \"the module asserted somebody owes money\");\n return scoped(statuses.length + 1, \"rendered strings\");\n});\n\nt(\"H19 a dead payment feed suppresses the list instead of blaming everyone\", () => {\n // THE ERROR THIS CATCHES: the Square bridge stops, no payments are found for anybody, and the\n // page cheerfully reports that every single holiday customer has not paid.\n ok(H.feedLooksDead([[], [], [], [], [], []]), \"an entirely empty feed was not detected\");\n ok(!H.feedLooksDead([[], [], [], [], [{ amount: 50, id: \"p\", at: null }]]), \"a working feed was called dead\");\n const s = H.depositSentence([H.statusFor(stay, [])], true);\n ok(/payment feed has stopped/i.test(s), \"a dead feed is not explained to Kim\");\n ok(/held back/i.test(s), \"the list is not held back when the feed is dead\");\n return scoped(4, \"feed states\");\n});\n\nt(\"H19b two quiet customers are not evidence that Square has stopped\", () => {\n // FOUND BY WATCHING IT RUN, 6 Aug 15:41Z. Two holiday stays were booked, neither customer had a\n // Square note, and the kill switch fired: Kim would have been shown \"the payment feed has\n // stopped\" on the strength of two people. Two customers with no card payment is a normal week.\n ok(!H.feedLooksDead([[], []]), \"a two-customer sample was treated as proof of an outage\");\n ok(!H.feedLooksDead([[], [], [], []]), \"a four-customer sample was treated as proof of an outage\");\n ok(H.feedLooksDead([[], [], [], [], []]), \"a full sample of silence should still trip the switch\");\n ok(!H.feedLooksDead([]), \"nothing read at all is not evidence of anything\");\n eq(H.MIN_SAMPLE_FOR_DEAD_FEED, 5, \"the floor is not stated as a named number anyone can find\");\n return scoped(5, \"sample sizes\");\n});\n\nt(\"H20 the sentence is generated from the counts, so words and numbers cannot disagree\", () => {\n const many = [H.statusFor(stay, []), H.statusFor(stay, []), H.statusFor(stay, [{ amount: 50, id: \"p\", at: \"2026-07-21T10:00:00Z\", kind: \"direct\" }])];\n const s = H.depositSentence(many, false);\n ok(/3 holiday stays are booked/.test(s), `the count is not stated: ${s}`);\n ok(/1 has a Square payment/.test(s), \"the paid count is not stated\");\n ok(/2 are worth checking/.test(s), \"the check count is not stated\");\n ok(!/\\$50 payment/.test(s), `the headline names a fixed $50 while each row owes $50 per dog: ${s}`);\n ok(/shortlist/.test(s), \"the honest framing is missing\");\n return scoped(many.length, \"statuses\");\n});\n\nt(\"H21 no holiday bookings at all reads as nothing to do, not as a problem\", () => {\n const s = H.depositSentence([], false);\n ok(/nothing to check/i.test(s), \"an empty list was not explained\");\n ok(!/\\d+ holiday stays are booked/.test(s), \"it announced a count of zero\");\n return scoped(1, \"empty case\");\n});\n\nheader(\"THE SECOND PAYMENT FORMAT, FOUND LIVE ON 6 AUG\");\n\n// Both of these are verbatim rows off David Newman's contact, read live on Aug 6 2026. They are\n// the same amount under two different payment ids, four days apart in note-write time.\nconst NOTES_TWO_FORMATS = [\n { body: \"[Square] +$35.00 payment z3rQRe4iTWZE4AfSdt7fvG0mNd8YY (balance $35.00)\", dateAdded: \"2026-07-31T13:22:29.159Z\" },\n { body: \"[Square] Till payment $35.00 on 2026-07-17. Matched from Square payment 3zu7hAMbwBfEKDsUXyRuw58pztWZY via customer QJXE7X8ZM31TVEQMQS7TTF7974. Backfilled after the Customers-read token was supplied.\", dateAdded: \"2026-07-27T18:02:01.492Z\" },\n];\n\nt(\"H23 the backfill note format is money, not noise\", () => {\n // THE ERROR THIS CATCHES: the first version of the parser only knew the \"+$\" format. A customer\n // whose only Square evidence is a backfill note would have read as no payment found, and gone\n // on the shortlist. Silent, and exactly the wrong direction.\n const p = H.parseSquarePayments([NOTES_TWO_FORMATS[1]]);\n eq(p.length, 1, \"the Till/Matched-from note was not recognised as a payment at all\");\n eq(p[0].amount, 35);\n eq(p[0].id, \"3zu7hAMbwBfEKDsUXyRuw58pztWZY\");\n eq(p[0].kind, \"matched\");\n return scoped(1, \"backfill note\");\n});\n\nt(\"H24 the backfill carries the real payment date, not the day it was written down\", () => {\n // The note was written on 27 July about money taken on Jul 17y. Using the write date would\n // slide a payment out of the window it belongs to.\n const p = H.parseSquarePayments([NOTES_TWO_FORMATS[1]]);\n eq(p[0].at, \"2026-07-17\", \"the note's own write time was used instead of the payment date it states\");\n return scoped(1, \"date\");\n});\n\nt(\"H25 the same $35 under two ids is not counted as $70\", () => {\n // Nothing in the data settles whether this is one payment or two. The two readings disagree\n // about whether a $50 deposit is covered, so the reading that keeps the person ON the list to\n // be checked wins. Counting $70 would quietly drop a real customer off Kim's shortlist.\n const p = H.parseSquarePayments(NOTES_TWO_FORMATS);\n eq(p.length, 2, \"both records should survive parsing; the judgement happens later\");\n const { kept, collapsed } = H.collapseSameMoney(p);\n eq(collapsed, 1);\n eq(kept.reduce((n, x) => n + x.amount, 0), 35, \"$35 seen twice was added up to $70\");\n return scoped(2, \"records\");\n});\n\nt(\"H26 two genuinely separate payments of the same size are still two payments\", () => {\n // The mirror of H25, and the reason the rule is narrow: only a \"Matched from\" reconciliation\n // record collapses. Two direct payments of $35 are $70 and must stay $70.\n const two = [\n { amount: 35, id: \"a\", at: \"2026-07-01\", kind: \"direct\" },\n { amount: 35, id: \"b\", at: \"2026-07-02\", kind: \"direct\" },\n ];\n const { kept, collapsed } = H.collapseSameMoney(two);\n eq(collapsed, 0);\n eq(kept.length, 2, \"two real payments were merged into one\");\n return scoped(2, \"payments\");\n});\n\nt(\"H27 the same $50 under two ids is one deposit, not two payments in Kim's face\", () => {\n // Her live data holds the same money as a direct payment AND as a \"Matched from\" reconciliation\n // record, under two different ids. Listing both would have Kim reading $100 where there is $50.\n const s = H.statusFor(stay, [\n { amount: 50, id: \"a\", at: \"2026-07-21T10:00:00Z\", kind: \"direct\" },\n { amount: 50, id: \"b\", at: \"2026-07-21T10:00:00Z\", kind: \"matched\" },\n ]);\n eq(s.state, \"seen\");\n eq(s.amountSeen, 50, \"the same $50 was counted twice\");\n ok(!/other card payment/i.test(s.note), \"the duplicate record was shown to Kim as a second payment\");\n ok(!/unpaid|owes|not paid/i.test(s.note), \"the softer wording rule still applies to this sentence\");\n // A NON-DEPOSIT PAIR, because the pair above could not fail. [was: only the $50 case, where\n // amountSeen is the constant DEPOSIT and the \"other payments\" list is defined as everything\n // that is NOT $50 — so both assertions held whether or not the collapse ran at all. Deleting\n // the collapse call left all 270 assertions green. Caught by a fourth adversarial read.]\n const live = H.statusFor(stay, [\n { amount: 35, id: \"z3rQ\", at: \"2026-07-31T13:22:29Z\", kind: \"direct\" },\n { amount: 35, id: \"3zu7\", at: \"2026-07-17T00:00:00Z\", kind: \"matched\" },\n ]);\n eq(live.amountSeen, 35, \"the same $35, written by Square in both of its note formats, was counted as $70\");\n ok(/1 card payment is/.test(live.note), `the duplicate was shown to Kim as a second payment: ${live.note}`);\n return scoped(4, \"records\");\n});\n\nt(\"H28 her CRM's two spellings of the status field are both read\", () => {\n // Live on Aug 6: 4 of the 13 events on the Boarding Drop Off calendar carry `appoinmentStatus`\n // alongside the correctly spelled key. They agree today. Reading one is passing by luck.\n ok(H.eligible({ contactId: \"c1\", appointmentStatus: \"confirmed\", appoinmentStatus: \"confirmed\" }));\n ok(!H.eligible({ contactId: \"c1\", appointmentStatus: \"confirmed\", appoinmentStatus: \"cancelled\" }),\n \"a booking cancelled under the misspelled key was still counted, so a cancelled customer gets chased\");\n ok(!H.eligible({ contactId: \"c1\", appointmentStatus: \"cancelled\" }));\n ok(H.eligible({ contactId: \"c1\" }), \"a booking with no status at all should not vanish\");\n return scoped(4, \"status shapes\");\n});\n\nheader(\"WHAT THE ADVERSARIAL PASS FOUND, 6 AUG\");\n\nt(\"H30 every Thanksgiving window is made of dates that exist\", () => {\n // FOUND BY AN ADVERSARIAL READ, not by a failing test. The window edges were decimal arithmetic\n // on the day number, so any year where Thanksgiving is the 28th produced \"Nov 31\": a stay\n // dropping off on 1 December sorted ABOVE it and vanished, and the card printed \"Nov 31\" to Kim.\n let checked = 0;\n for (let y = 2026; y <= 2040; y++) {\n for (const w of H.holidayWindows(y)) {\n for (const d of [w.from, w.to]) {\n const iso = new Date(`${d}T00:00:00Z`).toISOString().slice(0, 10);\n eq(iso, d, `${y}: ${d} is not a real date`);\n checked++;\n }\n }\n const t0 = H.thanksgiving(y);\n const w0 = H.holidayWindows(y)[0];\n ok(w0.from < t0 && w0.to > t0, `${y}: Thanksgiving is not inside its own window`);\n }\n return scoped(checked, \"window edges across 15 years\");\n});\n\nt(\"H31 an appointment time sent as a number is still a day\", () => {\n // Two sibling modules that read this same endpoint already defend against an epoch startTime.\n // Returning null for it dropped EVERY stay and stored \"no holiday stays are booked\" as a fact.\n const d = H.localDay(Date.parse(\"2026-11-25T14:00:00Z\"));\n eq(d, \"2026-11-25\", \"an epoch timestamp was thrown away instead of read\");\n eq(H.localDay(Date.parse(\"2026-11-26T02:00:00Z\")), \"2026-11-25\",\n \"an epoch just after midnight UTC was not read in the business's own timezone\");\n eq(H.localDay(NaN), null);\n return scoped(3, \"numeric times\");\n});\n\nt(\"H32 her CRM's sloppier shapes still exclude the bookings they should\", () => {\n ok(!H.eligible({ contactId: \"c\", appointmentStatus: \"cancelled \" }), \"one trailing space made a cancelled booking chaseable\");\n ok(!H.eligible({ contactId: \"c\", appointmentStatus: \" Cancelled\" }));\n ok(!H.eligible({ contactId: \"c\", isRecurring: \"true\" }), \"a recurring flag sent as a string put a weekly regular on the list\");\n ok(!H.eligible({ contactId: \"c\", deleted: \"true\" }));\n // The ONLY thing keeping the weekly daycare slot off the list used to be its recurrence flag.\n ok(!H.eligible({ contactId: \"c\", title: \"Daycare Enzo \", isRecurring: false }), \"a one-off daycare booking was billed a boarding deposit\");\n ok(H.eligible({ contactId: \"c\", title: \"Achilles — Boarding Drop Off\" }));\n return scoped(6, \"shapes\");\n});\n\nt(\"H33 four ways of writing a payment that all used to read as no payment\", () => {\n const p = (b) => H.parseSquarePayments([{ body: b, dateAdded: \"2026-07-31T00:00:00Z\" }]);\n eq(p(\"[Square] +$25.00 payment aaa (balance $0.00) then [Square] +$35.00 payment bbb (balance $0.00)\").length, 2,\n \"a note holding two payments only counted one of them\");\n eq(p(\"[Square] Till payment $50.00 on 2026-07-17. Matched from Square payment 3zu7hAM\")[0]?.amount, 50,\n \"a backfill note that ends at the payment id lost the whole payment\");\n eq(p(\"[Square] +$50 payment abc\")[0]?.amount, 50, \"a whole-dollar amount was not read as money\");\n eq(p(\"[Square] Till payment $40.00 on 2026-07-01. Matched from Square payment 3zu7abc, via customer X.\")[0]?.id, \"3zu7abc\",\n \"a trailing comma became part of the payment id, so the same payment could be counted twice\");\n return scoped(4, \"note shapes\");\n});\n\nconst stayNov = { contactId: \"c1\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Achilles\"], dogCount: 1, bookedAt: \"2026-07-20 14:00:00\", window: \"Thanksgiving\" };\n\nt(\"H34 an unrelated payment months before the stay does not clear the deposit\", () => {\n // THE BIGGEST SILENT MISS. The old window ran from the booking to the drop-off, four months\n // wide, and summed everything in it. A customer's $355 training package cleared their deposit,\n // and being cleared means nobody ever looks at them again.\n const s = H.statusFor(stayNov, [{ amount: 355, id: \"pkg\", at: \"2026-08-06T00:47:00Z\", kind: \"direct\" }]);\n ok(s.state !== \"seen\", \"a training package was counted as the deposit and the customer was cleared\");\n ok(/\\$355\\.00 on Aug 6/.test(s.note), `the payment that does exist is hidden from Kim rather than named: ${s.note}`);\n ok(/nothing on file matches that amount/.test(s.note), `the note does not say why it was not treated as the deposit: ${s.note}`);\n const s2 = H.statusFor(stayNov, [\n { amount: 30, id: \"a\", at: \"2026-08-01T00:00:00Z\", kind: \"direct\" },\n { amount: 25, id: \"b\", at: \"2026-09-14T00:00:00Z\", kind: \"direct\" },\n ]);\n ok(s2.state !== \"seen\", \"two unrelated payments were added up into a deposit\");\n eq(s2.amountSeen, 55, \"the amounts Kim can see are not reported\");\n // And the real deposit is still recognised.\n eq(H.statusFor(stayNov, [{ amount: 50, id: \"dep\", at: \"2026-07-21T00:00:00Z\", kind: \"direct\" }]).state, \"seen\");\n return scoped(4, \"payment patterns\");\n});\n\nt(\"H35 a booking with no record of when it was made is unknown, not settled\", () => {\n // [was: the search window fell back to the beginning of time, so a payment from 2019 cleared it.]\n const s = H.statusFor({ ...stayNov, bookedAt: null }, [{ amount: 60, id: \"old\", at: \"2019-02-01T00:00:00Z\", kind: \"direct\" }]);\n eq(s.state, \"could_not_check\", \"a payment from years earlier settled a booking whose date we do not know\");\n ok(!/unpaid|owes|has not paid/i.test(s.note));\n return scoped(1, \"booking\");\n});\n\nt(\"H36 a stay that starts before the window but runs through it is a holiday stay\", () => {\n // A holiday boarding business is mostly people who drop off the day BEFORE they travel.\n const w = H.holidayWindows(2026);\n const before = [{ contactId: \"c-x\", title: \"Rex — Boarding Drop Off\", startTime: \"2026-12-19T09:00:00-05:00\",\n endTime: \"2026-12-27T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n const stays = H.groupIntoStays(before, w);\n eq(stays.length, 1, \"a dog boarded across Christmas was invisible because it arrived on the 19th\");\n eq(stays[0].window, \"Christmas and New Year\");\n eq(stays[0].until, \"2026-12-27\");\n // And a stay that ends before the window still does not count.\n const away = [{ ...before[0], startTime: \"2026-12-01T09:00:00-05:00\", endTime: \"2026-12-05T09:00:00-05:00\" }];\n eq(H.groupIntoStays(away, w).length, 0, \"a stay nowhere near a holiday was pulled in\");\n return scoped(4, \"stays\");\n});\n\nt(\"H37 a hyphenated dog name survives\", () => {\n // Kim reads this name before she phones somebody.\n eq(H.dogFromTitle(\"Jean-Luc — Boarding Drop Off\"), \"Jean-Luc\", \"the name was cut at the hyphen inside it\");\n eq(H.dogFromTitle(\"Achilles — Boarding Drop Off\"), \"Achilles\");\n eq(H.dogFromTitle(\"Rex - Boarding Drop Off\"), \"Rex\");\n return scoped(3, \"titles\");\n});\n\nt(\"H38 two payments are never described as one, and never added up into a deposit\", () => {\n const s = H.statusFor(stayNov, [\n { amount: 30, id: \"a\", at: \"2026-07-21T00:00:00Z\", kind: \"direct\" },\n { amount: 40, id: \"b\", at: \"2026-07-22T00:00:00Z\", kind: \"direct\" },\n ]);\n ok(s.state !== \"seen\", \"$30 and $40 were added together into a $50 deposit\");\n ok(/2 card payments are/.test(s.note), `two payments described in the singular: ${s.note}`);\n ok(/\\$30\\.00 on Jul 21/.test(s.note) && /\\$40\\.00 on Jul 22/.test(s.note), \"the two payments are not both shown\");\n return scoped(2, \"payments\");\n});\n\nt(\"H39 the dead-feed sentence does not speak for customers it never read\", () => {\n // [was: \"no Square payment has been recorded against anybody in this period\" while two of the\n // seven had failed to read. The suppressed table meant Kim could not even see which.]\n const st = [\n ...Array.from({ length: 5 }, () => H.statusFor(stayNov, [])),\n H.statusFor(stayNov, null), H.statusFor(stayNov, null),\n ];\n const s = H.depositSentence(st, true);\n ok(/any of the 5 we could check/.test(s), `the sentence claims to cover people it could not read: ${s}`);\n ok(!/against anybody/.test(s));\n return scoped(7, \"stays\");\n});\n\nt(\"H40 a deposit paid days before the booking was entered is put in front of Kim\", () => {\n // A customer phones on Jul 14y and pays $50; Kim enters the booking on the 20th. An exact-amount\n // match inside the search window is the one thing that clears a stay, so this one clears.\n const s = H.statusFor(stayNov, [{ amount: 50, id: \"early\", at: \"2026-07-14T00:00:00Z\", kind: \"direct\" }]);\n eq(s.state, \"seen\", \"a $50 card payment six days before the booking was typed in was not recognised\");\n ok(/Jul 14/.test(s.note), \"the date Kim would recognise is not in the sentence\");\n ok(!/unpaid|owes|has not paid/i.test(s.note));\n // But not one from before the search window: that is a different stay's money.\n ok(H.statusFor(stayNov, [{ amount: 50, id: \"ancient\", at: \"2026-01-14T00:00:00Z\", kind: \"direct\" }]).state !== \"seen\",\n \"a $50 payment six months earlier cleared this stay\");\n return scoped(2, \"payments\");\n});\n\nt(\"H41 the LATEST pick-up ends a stay, so one dog going home early does not delete it\", () => {\n // Her pick-up calendar carries one row per dog: \"Winnie — Boarding Pick Up\", \"Wylie — Boarding\n // Pick Up\", same contact, same day. Taking the earliest meant a family boarding straight through\n // Christmas was computed as a two-day stay in mid-December and dropped out of the window.\n const drops = [{ contactId: \"fam\", title: \"Rex — Boarding Drop Off\", startTime: \"2026-12-15T09:00:00-05:00\",\n dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n const picks = [\n { contactId: \"fam\", title: \"Bella — Boarding Pick Up\", startTime: \"2026-12-17T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"fam\", title: \"Rex — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n ];\n const stays = H.groupIntoStays(drops, H.holidayWindows(2026), picks);\n eq(stays.length, 1, \"a family boarding through Christmas was deleted because one dog went home early\");\n eq(stays[0].until, \"2026-12-27\");\n return scoped(2, \"pick-ups\");\n});\n\nt(\"H42 a stay never reaches forward and takes the next booking's pick-up\", () => {\n // [was: unbounded. A 3-night Thanksgiving stay was rendered \"Nov 25 to Dec 27\", and an ordinary\n // 6 November boarding with a stray later pick-up was dragged into a holiday window and billed\n // a deposit. Her real data has 3 contacts with drop-offs and no pick-ups and 20 the other way.]\n const drops = [\n { contactId: \"two\", title: \"A — Boarding Drop Off\", startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n { contactId: \"two\", title: \"A — Boarding Drop Off\", startTime: \"2026-12-20T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false },\n ];\n const picks = [{ contactId: \"two\", title: \"A — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n const stays = H.groupIntoStays(drops, H.holidayWindows(2026), picks);\n const nov = stays.find((x) => x.day === \"2026-11-25\");\n eq(nov.until, \"2026-11-25\", \"the November stay swallowed a pick-up belonging to the December booking\");\n eq(stays.find((x) => x.day === \"2026-12-20\").until, \"2026-12-27\");\n // A case where the length bound alone would NOT save us: two bookings 7 days apart and a\n // pick-up 10 days after the first, well inside MAX_STAY_DAYS. Only the next-booking bound stops\n // the first stay swallowing the second's pick-up.\n const close = H.groupIntoStays(\n [\"20\", \"27\"].map((d) => ({ contactId: \"cl\", title: \"A — Boarding Drop Off\", startTime: `2026-12-${d}T09:00:00-05:00`,\n dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false })),\n H.holidayWindows(2026),\n [{ contactId: \"cl\", title: \"A — Boarding Pick Up\", startTime: \"2026-12-30T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }]);\n eq(close.find((x) => x.day === \"2026-12-20\").until, \"2026-12-20\",\n \"the 20 December stay swallowed a pick-up that belongs to the 27 December booking\");\n eq(close.find((x) => x.day === \"2026-12-27\").until, \"2026-12-30\");\n // A STRAY PICK-UP MUST NOT DRAG AN OUT-OF-SEASON BOARDING INTO A WINDOW. Her account has about\n // twenty contacts with pick-ups and no matching drop-off, so orphan pick-up records are the\n // common case. [was: this asserted the drag HAPPENED — eq(stray.length, 1) — with a follow-up\n // whose first disjunct was false and whose second was true whenever the drag occurred. It was\n // a test pinning the bug its own comment said had been fixed. Caught by a third adversarial\n // read, which applied the correct bound and watched this test go red for it.]\n const stray = H.groupIntoStays(\n [{ contactId: \"s\", title: \"B — Boarding Drop Off\", startTime: \"2026-11-06T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }],\n H.holidayWindows(2026),\n [{ contactId: \"s\", title: \"B — Boarding Pick Up\", startTime: \"2027-02-01T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }]);\n eq(stray.length, 0, \"a 6 November boarding was stretched to February by an orphan pick-up and put on the holiday shortlist\");\n // And a stay of a believable length still pairs.\n const real = H.groupIntoStays(\n [{ contactId: \"r\", title: \"C — Boarding Drop Off\", startTime: \"2026-12-18T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }],\n H.holidayWindows(2026),\n [{ contactId: \"r\", title: \"C — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }]);\n eq(real.length, 1, \"a nine-night Christmas stay was thrown out by the length bound\");\n return scoped(4, \"stays\");\n});\n\nt(\"H43 a cancelled or recurring pick-up is not allowed to end a stay\", () => {\n const drops = [{ contactId: \"c\", title: \"A — Boarding Drop Off\", startTime: \"2026-12-18T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n const bad = [\n { contactId: \"c\", title: \"A — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"cancelled\", isRecurring: false },\n { contactId: \"c\", title: \" Boarding Pickup with David Newman\", startTime: \"2026-12-25T16:30:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: true },\n ];\n eq(H.groupIntoStays(drops, H.holidayWindows(2026), bad).length, 0,\n \"a cancelled or recurring pick-up was used to stretch a stay into a holiday window\");\n const good = [{ contactId: \"c\", title: \"A — Boarding Pick Up\", startTime: \"2026-12-27T09:00:00-05:00\", appointmentStatus: \"confirmed\", isRecurring: false }];\n eq(H.groupIntoStays(drops, H.holidayWindows(2026), good).length, 1);\n return scoped(3, \"pick-ups\");\n});\n\nt(\"H44 a real boarding booking with the word daycare in its title is not thrown away\", () => {\n // Her titles carry free text: \"drop off: Mia and Gemma \", \"Boarding drop off Harry\". A title\n // that says BOTH is a boarding booking with a note on it.\n ok(H.eligible({ contactId: \"c\", title: \"Boarding + daycare drop off with Dan Bonner\" }),\n \"a real boarding stay was excluded because somebody typed daycare in the title\");\n ok(H.eligible({ contactId: \"c\", title: \"Boarding Dropoff (daycare rate) with Gina Wright\" }));\n ok(!H.eligible({ contactId: \"c\", title: \"Daycare Enzo \" }), \"the daycare-only slot should still be excluded\");\n return scoped(3, \"titles\");\n});\n\nt(\"H45 the test-record label does not fire on a real surname\", () => {\n ok(!H.looksLikeTestRecord(\"Sarah Tester\"), \"a customer called Tester was labelled a test record on Kim's screen\");\n ok(!H.looksLikeTestRecord(\"Bob Testa\"));\n ok(!H.looksLikeTestRecord(\"Ann Testerman\"));\n ok(H.looksLikeTestRecord(\"help test\"), \"the record that really is a test was not flagged\");\n ok(H.looksLikeTestRecord(\"ZZTEST PuppyPath-Dummy\"));\n return scoped(5, \"names\");\n});\n\nt(\"H46 the dead-feed sentence never says it checked nobody\", () => {\n const allUnknown = [H.statusFor(stayNov, null), H.statusFor(stayNov, null)];\n const s = H.depositSentence(allUnknown, true);\n ok(!/any of the 0/.test(s), `the sentence reads as broken: ${s}`);\n ok(/none of them could be checked/i.test(s), \"the honest version of this case is missing\");\n return scoped(2, \"stays\");\n});\n\nt(\"H47 the dead-feed switch counts customers, not bookings\", () => {\n // [was: one entry per stay, so a single regular with five holiday drop-offs and a habit of\n // paying cash suppressed the whole card on their own. Her data has one contact with 24.]\n const one = new Map([[\"only-customer\", []]]);\n ok(!H.feedLooksDead(one), \"one customer with no card payment was treated as an outage\");\n const five = new Map([[\"a\", []], [\"b\", []], [\"c\", []], [\"d\", []], [\"e\", []]]);\n ok(H.feedLooksDead(five), \"five customers with no card payment anywhere did not trip the switch\");\n const mixed = new Map([[\"a\", []], [\"b\", []], [\"c\", []], [\"d\", []], [\"e\", [{ amount: 50, id: \"p\", at: null, kind: \"direct\" }]]]);\n ok(!H.feedLooksDead(mixed), \"a working feed was called dead\");\n return scoped(3, \"samples\");\n});\n\nt(\"H48 one $50 deposit settles ONE stay, not every booking that customer has\", () => {\n // THE MOST EXPENSIVE BUG FOUND ALL DAY, and the ordinary case rather than an edge: a regular\n // books Thanksgiving and Christmas in the same phone call and pays one $50 deposit. Both search\n // windows are anchored on the same booking date, so both stays saw the same payment and both\n // went green. Kim was owed $100, $50 arrived, and neither row reached the shortlist.\n const two = [\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" },\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-10-01 09:00:00\", window: \"Christmas and New Year\" },\n ];\n const one = [{ amount: 50, id: \"onlyfifty\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" }];\n const out = H.statusesForCustomer(two, one);\n eq(out.filter((s) => s.state === \"seen\").length, 1, \"one $50 payment settled both of this customer's holiday stays\");\n eq(out[0].state, \"seen\", \"the payment should settle the earlier stay\");\n ok(out[1].state !== \"seen\", \"the second stay was settled by money that had already been spent\");\n // Two deposits settle two stays.\n const both = H.statusesForCustomer(two, [...one, { amount: 50, id: \"second\", at: \"2026-10-06T00:00:00Z\", kind: \"direct\" }]);\n eq(both.filter((s) => s.state === \"seen\").length, 2, \"two real $50 deposits did not settle two stays\");\n return scoped(2, \"stays\");\n});\n\nt(\"H49 a payment after the dogs go home does not settle the stay\", () => {\n // The upper edge of the search window. [was: unguarded — it could be stretched to a year\n // without a single test moving, which is how \"any payment ever\" comes back.]\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n eq(H.statusFor(st, [{ amount: 50, id: \"a\", at: \"2026-11-29T00:00:00Z\", kind: \"direct\" }]).state, \"seen\",\n \"a deposit settled the day after pick-up should still count\");\n ok(H.statusFor(st, [{ amount: 50, id: \"b\", at: \"2026-12-15T00:00:00Z\", kind: \"direct\" }]).state !== \"seen\",\n \"a payment weeks after the dogs went home was counted as this stay's deposit\");\n ok(H.statusFor(st, [{ amount: 50, id: \"c\", at: \"2027-06-01T00:00:00Z\", kind: \"direct\" }]).state !== \"seen\",\n \"a payment the following summer was counted as this stay's deposit\");\n return scoped(3, \"payment dates\");\n});\n\nt(\"H50 a lone payment that is not the deposit reads as English\", () => {\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n const n = H.statusFor(st, [{ amount: 100, id: \"a\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" }]).note;\n ok(!/none of them/.test(n), `\"none of them\" about a single payment: ${n}`);\n ok(!/among them/.test(n), `\"among them\" about a single payment: ${n}`);\n ok(/\\$100\\.00 on Oct 5/.test(n), \"the payment is not shown\");\n return scoped(1, \"note\");\n});\n\nt(\"H51 the headline counts every row the table shows as worth a look\", () => {\n // [was: unguarded. Dropping the partial rows from the count gave \"1 is worth checking\" above a\n // table showing two rows both labelled Worth a look.]\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n const mixed = [\n H.statusFor(st, []), // none_seen\n H.statusFor(st, [{ amount: 100, id: \"a\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" }]), // partial\n ];\n const s = H.depositSentence(mixed, false);\n ok(/2 are worth checking/.test(s), `the headline does not count both rows the table shows: ${s}`);\n return scoped(2, \"rows\");\n});\n\nt(\"H52 a deposit Square wrote twice does not settle two different stays\", () => {\n // THE SAME MONEY BUG, RE-ENTERING THROUGH A CRACK. Round three stopped one $50 settling two\n // stays. It came straight back when the payment was a direct+matched pair: the collapse ran\n // inside the per-stay check while the allocator marked only the surviving id as spent, so the\n // folded twin was still on the table for the next stay. Both rows went green quoting two\n // different dates, so it read as two deposits. Kim owed $100, $50 arrived, nothing to chase.\n const two = [\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-09-28 09:00:00\", window: \"Thanksgiving\" },\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-09-28 09:00:00\", window: \"Christmas and New Year\" },\n ];\n const twinned = [\n { amount: 50, id: \"z3rQRe4iTWZE4AfSdt7fvG0mNd8YY\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" },\n { amount: 50, id: \"3zu7hAMbwBfEKDsUXyRuw58pztWZY\", at: \"2026-10-01T00:00:00Z\", kind: \"matched\" },\n ];\n const out = H.statusesForCustomer(two, twinned);\n eq(out.filter((s) => s.state === \"seen\").length, 1,\n \"one $50 deposit, written by Square in both of its formats, settled two separate holiday stays\");\n return scoped(2, \"stays\");\n});\n\nt(\"H53 the money goes to the stay that came first, not to whichever way the array arrived\", () => {\n // [was: unpinned. Reversing the allocation order left every assertion green, so the documented\n // rule was a comment rather than a guarantee.]\n const two = [\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-09-28 09:00:00\", window: \"Christmas and New Year\" },\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-09-28 09:00:00\", window: \"Thanksgiving\" },\n ];\n const out = H.statusesForCustomer(two, [{ amount: 50, id: \"one\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" }]);\n eq(out[0].stay.day, \"2026-11-25\", \"the stays are not being put in date order before the money is handed out\");\n eq(out[0].state, \"seen\", \"the payment did not go to the earlier stay\");\n ok(out[1].state !== \"seen\");\n return scoped(2, \"stays\");\n});\n\nt(\"H54 the season turns over on her clock, not on Greenwich\", () => {\n // Her business is in New York. Rolling on the UTC date empties the card at 8pm on 2 January,\n // five hours early, with dogs still in the kennels — and the empty result is then stored.\n eq(H.businessDay(\"2027-01-03T01:00:00.000Z\"), \"2027-01-02\", \"8pm on 2 January in New York was read as 3 January\");\n eq(H.seasonYear(H.businessDay(\"2027-01-03T01:00:00.000Z\")), 2026, \"the season rolled over while the New Year stays were still running\");\n eq(H.seasonYear(H.businessDay(\"2027-01-03T13:00:00.000Z\")), 2027, \"the season should have moved on by the afternoon of the 3rd\");\n eq(H.businessDay(\"nonsense\").length, 8);\n return scoped(4, \"moments\");\n});\n\nt(\"H55 money on a settled row is still shown, so Kim can see what else was paid\", () => {\n // [was: unpinned. Deleting the whole sentence left the suite green, and it is Kim's only view\n // of other money on a row that has already been cleared.]\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n const n = H.statusFor(st, [\n { amount: 50, id: \"dep\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" },\n { amount: 240, id: \"inv\", at: \"2026-10-07T00:00:00Z\", kind: \"direct\" },\n ]).note;\n ok(/other card payment/i.test(n), `other money on a cleared row is hidden: ${n}`);\n ok(/\\$240\\.00 on Oct 7/.test(n), \"the amount and date of the other payment are not shown\");\n return scoped(2, \"payments\");\n});\n\nt(\"H56 two settled stays never quote the same payment back to Kim\", () => {\n // The allocator debits one record while the note quotes another, so both rows can cite the same\n // date — which is exactly what \"one payment settled two stays\" looks like on the page, whether\n // or not the underlying count is right. Two backfill records and one direct payment produce it.\n const two = [\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-09-28 09:00:00\", window: \"Thanksgiving\" },\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-09-28 09:00:00\", window: \"Christmas and New Year\" },\n ];\n const messy = [\n { amount: 50, id: \"matchedA\", at: \"2026-10-01T00:00:00Z\", kind: \"matched\" },\n { amount: 50, id: \"matchedB\", at: \"2026-10-02T00:00:00Z\", kind: \"matched\" },\n { amount: 50, id: \"directC\", at: \"2026-10-05T00:00:00Z\", kind: \"direct\" },\n ];\n const out = H.statusesForCustomer(two, messy);\n const quoted = out.filter((x) => x.state === \"seen\").map((x) => (/on ([A-Z][a-z]{2} \\d+)/.exec(x.note) || [])[1]);\n eq(quoted.length, new Set(quoted).size,\n `two settled stays quote the same payment: ${JSON.stringify(quoted)}`);\n return scoped(out.length, \"stays\");\n});\n\nt(\"H57 two backfill records and one payment are still one deposit\", () => {\n // THE SAME MONEY BUG, ONE LEVEL DOWN AGAIN. The collapse used to be one-for-one: each backfill\n // record consumed one direct payment of the same amount, so with TWO backfills and ONE payment\n // the second backfill survived still sharing an amount with the direct. The per-stay check then\n // folded it a second time — declaring them one payment — while the allocator had only ever\n // spent one id, leaving the other free to settle the next stay. Making the collapse idempotent\n // is what closes it: after one pass, no surviving backfill shares an amount with a payment.\n const messy = [\n { amount: 50, id: \"z3rQ\", at: \"2026-10-07T00:00:00Z\", kind: \"direct\" },\n { amount: 50, id: \"3zu7\", at: \"2026-10-07T00:00:00Z\", kind: \"matched\" },\n { amount: 50, id: \"9kQp\", at: \"2026-10-01T00:00:00Z\", kind: \"matched\" },\n ];\n const once = H.collapseSameMoney(messy);\n const twice = H.collapseSameMoney(once.kept);\n eq(twice.collapsed, 0, \"a second pass still finds something to collapse, so the layers above disagree about how much money there is\");\n eq(once.kept.length, 1);\n const two = [\n { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-09-28 09:00:00\", window: \"Thanksgiving\" },\n { contactId: \"c\", day: \"2026-12-22\", until: \"2026-12-27\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-09-28 09:00:00\", window: \"Christmas and New Year\" },\n ];\n eq(H.statusesForCustomer(two, messy).filter((x) => x.state === \"seen\").length, 1,\n \"one $50, written once as a payment and twice as a backfill, settled two separate holiday stays\");\n return scoped(3, \"records\");\n});\n\nt(\"H58 the deposit is $50 PER DOG, which is what her own money page says\", () => {\n // \"Holiday boarding — $50 per dog, non-refundable. Deducted from the total boarding cost at\n // drop-off.\" — Kim's money page, taken from her live website. [was: a flat $50 per stay, with a\n // line on the card asking Kim to tell us if it was per dog. It says so in her own handover pack.\n // Jeffrey Musselwhite's three dogs on 25 November owe $150, and one $50 payment was clearing the\n // whole stay: the silent direction, where somebody who owes $100 more drops off the list.]\n const mk = (n) => ({ contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\",\n dogs: Array.from({ length: n }, (_, i) => `Dog${i}`), dogCount: n, bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" });\n const pay = (a, at, id) => ({ amount: a, id, at, kind: \"direct\" });\n eq(H.depositDue(mk(3)), 150);\n eq(H.depositDue(mk(1)), 50);\n ok(H.statusFor(mk(3), [pay(50, \"2026-10-05T00:00:00Z\", \"a\")]).state !== \"seen\",\n \"one $50 payment settled a three-dog stay that owes $150\");\n eq(H.statusFor(mk(3), [pay(150, \"2026-10-05T00:00:00Z\", \"a\")]).state, \"seen\", \"the full $150 did not settle a three-dog stay\");\n eq(H.statusFor(mk(3), [pay(50, \"2026-10-05T00:00:00Z\", \"a\"), pay(50, \"2026-10-06T00:00:00Z\", \"b\"), pay(50, \"2026-10-07T00:00:00Z\", \"c\")]).state, \"seen\",\n \"three $50 payments, one per dog, did not settle a three-dog stay\");\n ok(H.statusFor(mk(3), [pay(50, \"2026-10-05T00:00:00Z\", \"a\"), pay(50, \"2026-10-06T00:00:00Z\", \"b\")]).state !== \"seen\",\n \"two $50 payments settled a stay that owes three\");\n ok(/\\$150\\.00/.test(H.statusFor(mk(3), []).note), \"the note does not tell Kim what this stay owes\");\n return scoped(7, \"shapes\");\n});\n\nt(\"H59 a dog whose name did not parse is still a dog Kim is owed for\", () => {\n // The count comes from the drop-off ROWS, not from the parsed names. Her titles include\n // \" Boarding Dropoff with Help Test\", which yields no dog name at all.\n const evs = [\"Achilles — Boarding Drop Off\", \" Boarding Dropoff with Someone\", \"Ghost — Boarding Drop Off\"].map((title) => ({\n contactId: \"c\", title, startTime: \"2026-11-25T09:00:00-05:00\", dateAdded: \"2026-10-01 09:00:00\", appointmentStatus: \"confirmed\", isRecurring: false }));\n const st = H.groupIntoStays(evs, H.holidayWindows(2026))[0];\n eq(st.dogCount, 3, \"a booking whose title did not parse was not counted as a dog, so Kim is under-charged\");\n eq(H.depositDue(st), 150);\n ok(st.dogs.length < 3, \"this case is not exercising an unparsed title at all\");\n return scoped(3, \"bookings\");\n});\n\nt(\"H60 Kim is told where else to look, using the routes she actually takes\", () => {\n // Her money page lists Card, Venmo, Zelle and cheque, and says card is \"the only one that\n // matches itself to a customer record automatically\". [was: \"cash or over the phone\", which\n // named neither of the two routes she actually offers.]\n const st = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"Rex\"], dogCount: 1, bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n const n = H.statusFor(st, []).note;\n for (const route of [\"Venmo\", \"Zelle\", \"cheque\"]) ok(new RegExp(route).test(n), `${route} is not named, so Kim does not know to look there`);\n ok(/does not reach the card system/.test(n), \"the reason it is invisible is not explained\");\n ok(!/unpaid|owes|has not paid/i.test(n));\n const s = H.depositSentence([H.statusFor(st, [])], false);\n ok(/Venmo/.test(s) && /Zelle/.test(s), \"the headline still describes the wrong payment routes\");\n return scoped(5, \"routes\");\n});\n\nt(\"H61 the headline never names an amount, because every row owes a different one\", () => {\n // A three-dog stay owes $150. The headline used to say \"we cannot find a $50 payment against\n // it\" directly above it — a number in prose disagreeing with the number in the row beneath.\n const three = { contactId: \"c\", day: \"2026-11-25\", until: \"2026-11-28\", dogs: [\"A\", \"B\", \"C\"], dogCount: 3, bookedAt: \"2026-10-01 09:00:00\", window: \"Thanksgiving\" };\n const st = H.statusFor(three, []);\n const s = H.depositSentence([st], false);\n ok(/\\$150\\.00/.test(st.note), \"the row does not state what it owes\");\n ok(!/\\$50/.test(s), `the headline names $50 above a row that owes $150: ${s}`);\n ok(/worth checking/.test(s), \"the headline stopped saying there is anything to do\");\n return scoped(1, \"row\");\n});\n\nheader(\"WHAT IT MUST NEVER DO\");\n\nt(\"H22 the module cannot write to the CRM\", () => {\n // Structural, not a promise in a comment. addTag() in this engine is not TEST_MODE guarded and\n // this account has a workflow that turns a tag into do-not-disturb on six channels.\n ok(!/\"POST\"|'POST'|`POST`/.test(src), \"the module contains a POST\");\n ok(!/\"PUT\"|'PUT'|\"PATCH\"|'PATCH'|\"DELETE\"|'DELETE'/.test(src), \"the module contains a write verb\");\n ok(!/addTag|createTask|sendSms|sendEmail|upsert/.test(src), \"the module reaches a function that changes her account\");\n ok(!/fetch\\s*\\(/.test(src), \"the module fetches directly instead of being handed data it can be tested against\");\n return scoped(4, \"structural guarantees\");\n});\n\ndone();\n\n\n=====FILE tests/kim-copy.test.mjs =====\n// KIM'S OWN CORRECTIONS, PINNED. v2.0, 5 Aug 2026.\n// Every rule here is something she asked for in writing on 4 August. They are tests because a copy\n// instruction that lives only in a chat message gets quietly undone by the next edit, and she\n// should never have to ask twice.\nimport * as E from \"../build/engine.js\";\nimport { readFileSync } from \"node:fs\";\nimport { suite, ok, eq, scoped, TRACKS, allMessages, msgText } from \"./_harness.mjs\";\nconst { t, done, header } = suite(\"kim-copy\");\n\nconst all = allMessages(E);\nconst hits = (re) => all.filter((m) => re.test(msgText(m))).map((m) => `${m.track}/${m.id}`);\n\nheader(\"WHAT KIM ASKED FOR\");\n\nt(\"K-a no dog-name placeholder survives anywhere\", () => {\n // \"we haven't always got the name and so if we have a placeholder for the puppies name, it\n // reads weird when there's no puppy in there\" - Kim, 6:32 PM 4 Aug\n eq(hits(/\\{\\{\\s*DOG_NAME\\s*\\}\\}/), []);\n return scoped(all.length, \"messages checked\");\n});\nt(\"K-a2 the person's name is still used, so removing the dog name did not go impersonal\", () => {\n const n = all.filter((m) => /\\{\\{FIRST_NAME\\}\\}/.test(msgText(m))).length;\n ok(n >= all.length * 0.8, `only ${n}/${all.length} greet the person by name`);\n return `${n}/${all.length} greet by name`;\n});\nt(\"K-b daycare appears nowhere: they do not offer it\", () => {\n eq(hits(/day\\s*care/i), []);\n return scoped(all.length, \"messages checked\");\n});\nt(\"K-c American English: potty not toilet, yard not garden\", () => {\n eq(hits(/\\btoilet/i), []); eq(hits(/\\bgarden/i), []);\n ok(hits(/potty/i).length > 0, \"potty training vanished rather than being renamed\");\n return scoped(all.length, \"messages checked\");\n});\nt(\"K-d no British spelling, INCLUDING in render-time constants\", () => {\n const re = /\\b(behaviour|realise|realising|colour|whilst|enquir|apologise|organis|neighbour|favourite|practise\\b|licence\\b|cosy|kerb|aluminium|dialled|theoris)/i;\n eq(hits(re), []);\n // the failure this catches: EMAIL_OPTOUT read \"you enquired with The Dogs Spot\" and was appended\n // to every email at render time, where a scan of the template arrays could never see it\n const src = readFileSync(new URL(\"../engine/puppy_path_v1.1.ts\", import.meta.url), \"utf8\");\n const consts = src.match(/const (SMS_OPTOUT|EMAIL_OPTOUT)[\\s\\S]{0,400}?;/g) || [];\n ok(consts.length >= 2, `expected both opt-out constants, found ${consts.length}`);\n for (const c of consts) ok(!re.test(c), `British spelling in a render-time constant: ${c.slice(0, 90)}`);\n return `${all.length} templates + ${consts.length} appended constants`;\n});\nt(\"K-e the no-show text uses her word, schedule, not sort\", () => {\n const m = all.find((x) => x.id === \"branch_a-1\");\n ok(m, \"branch_a-1 missing\");\n ok(/schedule it/.test(m.bodyTemplate), \"her wording was reverted\");\n ok(!/sort it/.test(m.bodyTemplate), \"'sort it' is back\");\n return \"1 message\";\n});\nt(\"K-f the no-show email is her rewrite, near enough word for word\", () => {\n const m = all.find((x) => x.id === \"branch_a-2\");\n ok(m, \"branch_a-2 missing\");\n const phrases = [\"I noticed we had a Pup Talk scheduled, but we missed each other\", \"I know life gets busy\",\n \"quick, no-pressure call\", \"see whether training with us would be a good fit\",\n \"if we're not the right fit, I'll tell you that too\", \"won't keep bugging you\"];\n for (const p of phrases) ok(m.bodyTemplate.includes(p), `her phrase missing: \"${p}\"`);\n ok(!/daycare/i.test(m.bodyTemplate), \"daycare survived in the very message she rewrote to remove it\");\n return scoped(phrases.length, \"of her phrases verified\");\n});\nt(\"K-g no em-dashes reach a customer\", () => { eq(hits(/—/), []); return scoped(all.length, \"messages checked\"); });\nt(\"K-h no price quoted, grooming never offered\", () => {\n eq(hits(/groom/i), []); eq(hits(/\\$\\d/), []);\n return scoped(all.length, \"messages checked\");\n});\nt(\"K-i 'Pup Talk' everywhere, 'discovery call' nowhere\", () => {\n eq(hits(/discovery call/i), []);\n return scoped(all.length, \"messages checked\");\n});\ndone();\n\n","createdAt",["D",1786048353884],"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","pinMigrated","screenshotVersion","likeCount",0,"orgId","019f56fd-bd59-724f-8163-80ffcf8235dd","tursoName","1bfa6e8174e14c6cab32118304a4ffff","tursoHostname","1bfa6e8174e14c6cab32118304a4ffff-val-town.aws-us-east-2.turso.io","tursoMeasuredAt",["D",1789519842404],"pinned","userPerm","r","valPerm","blobPerm","rw","emailPerm","sqlitePerm","projectPerm","telemetryPerm","user",{"_99":98,"_107":103},"org",{"_99":98,"_100":101,"_102":103,"_18":55,"_104":105,"_106":27},"branch",{"_13":88,"_33":89,"_43":42,"_90":44,"_91":-5,"_92":-5,"_93":-5,"_94":-5,"_95":-5,"_96":45,"_97":98},"isOwned",1280,"main","projectId","forkedBranchId","forkedBranchVersion","forkedProjectPrivacy","forkedProjectId","forkedProjectOrgId","projectName","userHandle","amir5","handle","displayName","Amir","avatar","https://lh3.googleusercontent.com/a/ACg8ocILk3bwhcvrzozUWm7gxlKoBm7ZGtsgIkesW3ysOOsJ1rSQuA=s96-c","tier","free","canRestrictVals","profileImageUrl","branchName","","adoptOrgId",{"_43":44,"_33":45,"_38":543,"_47":-5,"_48":27,"_49":50,"_51":50,"_52":53,"_54":-5,"_18":55,"_56":57,"_58":25,"_59":-5,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":68,"_69":544,"_71":-5,"_72":73,"_74":73,"_75":76,"_77":76,"_78":76,"_79":73,"_80":73,"_81":545,"_83":546,"_85":547,"_87":27},"tree",[414,415,416,417,418,419,420,421,422,423,424,425,426,427,428,429,430,431,432,433,434,435,436,437,438,439,440,441,442,443,444,445],"files",[414,415,416,417,418,419,420,421,422,423,424,425,426,427,428,429,430,431,432,433,434,435,436,437,438,439,440,441,442,443,444,445],"counts",{"_404":62,"_405":187,"_406":62,"_407":408,"_409":410},"contents",[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161],"upstreamProject","upstreamBranch","emptyEnvVars","flags",[],"hasHttpFiles","grants","orgs","customDomains",{},{"_43":397,"_33":398,"_31":399,"_165":-5,"_41":42,"_40":400,"_167":27,"_38":401,"_13":225,"_34":20,"_35":402,"_24":27,"_172":-5,"_28":403},{"_43":390,"_33":391,"_31":392,"_165":-5,"_41":42,"_40":393,"_167":25,"_38":394,"_13":62,"_34":20,"_35":395,"_24":27,"_172":-5,"_28":396},{"_43":383,"_33":384,"_31":385,"_165":-5,"_41":42,"_40":386,"_167":27,"_38":387,"_13":185,"_34":20,"_35":388,"_24":27,"_172":-5,"_28":389},{"_43":375,"_33":376,"_31":377,"_165":-5,"_41":42,"_40":378,"_167":27,"_38":379,"_13":380,"_34":20,"_35":381,"_24":27,"_172":-5,"_28":382},{"_43":367,"_33":368,"_31":369,"_165":-5,"_41":42,"_40":370,"_167":27,"_38":371,"_13":372,"_34":20,"_35":373,"_24":27,"_172":-5,"_28":374},{"_43":359,"_33":360,"_31":361,"_165":-5,"_41":42,"_40":362,"_167":27,"_38":363,"_13":364,"_34":20,"_35":365,"_24":27,"_172":-5,"_28":366},{"_43":356,"_33":29,"_31":32,"_165":-5,"_41":42,"_40":14,"_167":27,"_38":357,"_13":241,"_34":20,"_35":37,"_24":27,"_172":-5,"_28":358},{"_43":349,"_33":350,"_31":351,"_165":-5,"_41":42,"_40":352,"_167":27,"_38":353,"_13":273,"_34":20,"_35":354,"_24":27,"_172":-5,"_28":355},{"_43":342,"_33":343,"_31":344,"_165":-5,"_41":42,"_40":345,"_167":27,"_38":346,"_13":233,"_34":20,"_35":347,"_24":27,"_172":-5,"_28":348},{"_43":335,"_33":336,"_31":337,"_165":-5,"_41":42,"_40":338,"_167":27,"_38":339,"_13":187,"_34":20,"_35":340,"_24":27,"_172":-5,"_28":341},{"_43":328,"_33":329,"_31":330,"_165":-5,"_41":42,"_40":331,"_167":27,"_38":332,"_13":62,"_34":20,"_35":333,"_24":27,"_172":-5,"_28":334},{"_43":321,"_33":322,"_31":323,"_165":-5,"_41":42,"_40":324,"_167":27,"_38":325,"_13":187,"_34":188,"_35":326,"_24":27,"_172":-5,"_28":327},{"_43":314,"_33":315,"_31":57,"_165":-5,"_41":42,"_40":316,"_167":27,"_38":317,"_13":318,"_34":188,"_35":319,"_24":27,"_172":-5,"_28":320},{"_43":307,"_33":308,"_31":309,"_165":-5,"_41":42,"_40":310,"_167":25,"_38":311,"_13":241,"_34":170,"_35":312,"_24":27,"_172":-5,"_28":313},{"_43":299,"_33":300,"_31":301,"_165":-5,"_41":42,"_40":302,"_167":27,"_38":303,"_13":304,"_34":188,"_35":305,"_24":27,"_172":-5,"_28":306},{"_43":291,"_33":292,"_31":293,"_165":-5,"_41":42,"_40":294,"_167":27,"_38":295,"_13":296,"_34":170,"_35":297,"_24":27,"_172":-5,"_28":298},{"_43":284,"_33":285,"_31":286,"_165":-5,"_41":42,"_40":287,"_167":27,"_38":288,"_13":187,"_34":250,"_35":289,"_24":27,"_172":-5,"_28":290},{"_43":276,"_33":277,"_31":278,"_165":-5,"_41":42,"_40":279,"_167":27,"_38":280,"_13":281,"_34":188,"_35":282,"_24":27,"_172":-5,"_28":283},{"_43":268,"_33":269,"_31":270,"_165":-5,"_41":42,"_40":271,"_167":27,"_38":272,"_13":273,"_34":170,"_35":274,"_24":27,"_172":-5,"_28":275},{"_43":260,"_33":261,"_31":262,"_165":-5,"_41":42,"_40":263,"_167":27,"_38":264,"_13":265,"_34":170,"_35":266,"_24":27,"_172":-5,"_28":267},{"_43":253,"_33":254,"_31":255,"_165":-5,"_41":42,"_40":256,"_167":25,"_38":257,"_13":233,"_34":170,"_35":258,"_24":27,"_172":-5,"_28":259},{"_43":244,"_33":245,"_31":246,"_165":-5,"_41":42,"_40":247,"_167":27,"_38":248,"_13":249,"_34":250,"_35":251,"_24":27,"_172":-5,"_28":252},{"_43":236,"_33":237,"_31":238,"_165":-5,"_41":42,"_40":239,"_167":27,"_38":240,"_13":241,"_34":188,"_35":242,"_24":27,"_172":-5,"_28":243},{"_43":228,"_33":229,"_31":230,"_165":-5,"_41":42,"_40":231,"_167":27,"_38":232,"_13":233,"_34":170,"_35":234,"_24":27,"_172":-5,"_28":235},{"_43":220,"_33":221,"_31":222,"_165":-5,"_41":42,"_40":223,"_167":27,"_38":224,"_13":225,"_34":170,"_35":226,"_24":27,"_172":-5,"_28":227},{"_43":213,"_33":214,"_31":215,"_165":-5,"_41":42,"_40":216,"_167":27,"_38":217,"_13":62,"_34":170,"_35":218,"_24":27,"_172":-5,"_28":219},{"_43":206,"_33":207,"_31":208,"_165":-5,"_41":42,"_40":209,"_167":25,"_38":210,"_13":62,"_34":170,"_35":211,"_24":27,"_172":-5,"_28":212},{"_43":198,"_33":199,"_31":200,"_165":-5,"_41":42,"_40":201,"_167":27,"_38":202,"_13":203,"_34":170,"_35":204,"_24":27,"_172":-5,"_28":205},{"_43":191,"_33":192,"_31":193,"_165":-5,"_41":42,"_40":194,"_167":27,"_38":195,"_13":179,"_34":188,"_35":196,"_24":27,"_172":-5,"_28":197},{"_43":182,"_33":183,"_31":184,"_165":-5,"_41":42,"_40":185,"_167":27,"_38":186,"_13":187,"_34":188,"_35":189,"_24":27,"_172":-5,"_28":190},{"_43":174,"_33":175,"_31":176,"_165":-5,"_41":42,"_40":177,"_167":27,"_38":178,"_13":179,"_34":170,"_35":180,"_24":27,"_172":-5,"_28":181},{"_43":162,"_33":163,"_31":164,"_165":-5,"_41":42,"_40":166,"_167":27,"_38":168,"_13":169,"_34":170,"_35":171,"_24":27,"_172":-5,"_28":173},"e6ff9890-8d05-4f16-b6f4-d135e3cfee08","worklog.ts","facd3ee8-9028-11f1-8d98-1607ee4eb77e","parentId",258,"latest",["D",1786035263321],31,"script","// THE WORK LOG — what changed, what broke, what got fixed. v1.0, 4 Aug 2026.\n//\n// WHY: Kim's dashboard answers \"is it working\" from live data. It cannot answer \"what have you\n// actually been doing\" or \"did something break last week\" from live data, because those are\n// events, not states. This file is the event trail: append-only, plain English, dated.\n//\n// THE RULE: every entry describes something that DEMONSTRABLY happened, with the evidence\n// alongside it. No entry is written for work that was merely intended. If a claim here cannot\n// be checked, it does not go here. Kim reads this; it is the receipts column of the retainer.\n//\n// TWO SOURCES:\n// 1. SEEDED (below): work done by hand, each line traceable to a verification run.\n// 2. AUTOMATIC: the watchdog appends \"broke\"/\"recovered\" pairs to the `tds_worklog` blob, so\n// an outage at 3am and its recovery both appear without anyone remembering to write them.\n\nexport type WorkEntry = {\n at: string; // ISO date (day precision is fine; this is a human timeline)\n // v1.2. A reader noticed that \"Fixed: this page used to state a number nobody measured\" (mine)\n // and \"Fixed: your website was charging half the deposit\" (hers, worth thousands) wore the same\n // label in the same colour, so my errors were hiding among her wins. `mine` is now its own kind\n // and its own word. Her words: \"Separate the two columns and I'll trust the page more, not less.\"\n kind: \"fixed\" | \"built\" | \"found\" | \"broke\" | \"recovered\" | \"changed\" | \"mine\";\n what: string; // one plain sentence, Kim's vocabulary\n evidence?: string; // how it was checked. Optional only for \"broke\" (the alarm IS the evidence)\n};\n\n// Seeded history. Everything below was verified on the date shown; the evidence column names\n// the check. Newest first is handled by the renderer, so this list stays chronological.\nexport const SEEDED: WorkEntry[] = [\n {\n at: \"2026-07-30\",\n kind: \"built\",\n what: \"The puppy follow-up system was built and switched into practice mode, where it does everything except actually send.\",\n evidence: \"It has been running on its own since, writing down every decision it makes. Its first practice run is still on file.\",\n },\n {\n at: \"2026-08-02\",\n kind: \"built\",\n what: \"Candace's welcome email was written and sent so she could start on the phones with the full picture.\",\n evidence: \"Sent 2 August; it is in the sent folder.\",\n },\n {\n at: \"2026-08-02\",\n kind: \"found\",\n what: \"Your website was charging a $250 Bootcamp deposit instead of $500. It was hidden inside the booking form's own settings, which is why nobody could find it.\",\n evidence: \"Fixed and published; the whole live site was then searched for '$250' and it appears nowhere.\",\n },\n {\n at: \"2026-08-02\",\n kind: \"found\",\n what: \"There are 17 Bootcamp bookings on record, from 19 December to 25 July, every one of them taken while the deposit was set to $250. What is not yet known is which of them actually paid one, and that means matching each booking against the payment records.\",\n evidence: \"Counted from your own booking records. An earlier version of this note asked you for a payment permission to finish the job; that was wrong and it is corrected here, because you had already granted it and it has been working since 1 August. Matching the bookings to the payments is work rather than a blocker, and it has not been done yet.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"fixed\",\n what: \"29 people who had texted STOP were never marked do-not-contact in the CRM, so they could still have been messaged.\",\n evidence: \"All 29 marked, then all 29 read back one at a time through the CRM's own records on 4 August. 29 of 29 confirmed, none missed.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"mine\",\n what: \"Three of the people who had texted STOP were on a call list I had already sent to your front desk. That was my mistake. The list was pulled and rebuilt the same day, but whether anyone had already called those three is not something I can see from here, and it is worth asking the desk.\",\n evidence: \"The rebuilt list has every STOP and every gate arrival removed, with a second tab naming exactly who came off it and why. The three names are in that tab, so the desk can be asked about those three specifically.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"changed\",\n what: \"The puppy follow-up messages were updated with your notes: the toy advice now explains the why, and the Pup Talk asks came down from six to four.\",\n evidence: \"The PDF you signed off was generated straight from the live system, not from a draft.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"built\",\n what: \"The slow track you asked for is built: weekly for a month, then every two weeks for six months, then monthly. No sales asks anywhere on it.\",\n evidence: \"29 messages, all written out in the PDF for your sign-off. Nothing sends until you say go.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"mine\",\n what: \"The follow-up system was running slightly older wording than the version you approved. It now runs exactly what you read.\",\n evidence: \"Compared the live wording against the wording you approved, character by character; they now match.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"fixed\",\n what: \"A security review found that text typed by a customer into their own name could end up treated as code inside an email we send, rather than as words. Nobody had done it, and it cannot happen now. Two other holes were found and closed in the same review, one of them in the key that protects the page you are reading.\",\n evidence: \"It came out of an adversarial review alongside two other security findings, and each of the three now has its own automatic check, and those checks are run before anything goes anywhere near your account. For this one that means names holding dollar signs, angle brackets, quotes and stray markup. The old page key was checked afterwards and is dead.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"built\",\n // [was: \"...looks over the whole setup ON A TIMER and raises an alarm...\". Every word about\n // what it checks was verified and still stands. The two words about the timer were not, and\n // on 5 August the timer turned out never to have fired. Kim has read this line. It is\n // corrected here rather than deleted, and the 5 August entry above carries the current state.]\n what: \"A second, separate system now looks over the whole setup and raises an alarm if anything stops working, including if somebody else quietly changes one of your CRM automations.\",\n evidence: \"Run live and watched end to end. It takes a fingerprint of your CRM automations each time it looks, so a change to any one of them shows up as a change rather than as silence. What was NOT checked at the time was whether it starts itself on a schedule. It does not; see 5 August.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"found\",\n what: \"Your CRM still has an old puppy follow-up automation switched on. If our new one went live alongside it, new inquiries would get two sets of messages from you on the same day.\",\n evidence: \"Read all 165 automations in your account. Switching ours on and that one off has to happen together, and it needs your say-so.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"found\",\n what: \"Your CRM records where nearly every inquiry came from, but not in the column it shows you. The column you can see is blank for four out of five people; the record underneath places all of them.\",\n evidence: \"Checked across a full week of inquiries: the column you can see named about one in five of them, the record underneath named every single one. That is where the Facebook and Instagram numbers above come from, and they are recounted every time you open this page.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"mine\",\n what: \"This page used to tell you the follow-up system checks in every 15 minutes. Nobody had ever measured that, and it was not true. It now times itself and reports the rhythm it actually keeps.\",\n evidence: \"The page was saying 'last checked 26 minutes ago' and 'it runs every 15 minutes' at the same time, which cannot both be right. It now measures the gaps between runs and reports what it sees.\",\n },\n {\n at: \"2026-08-01\",\n kind: \"mine\",\n what: \"I sent you a draft of the follow-up messages as though it were the finished thing, and you spent an evening reading the wrong version. That was mine, and the replacement was generated from the live system so it could not happen the same way twice.\",\n evidence: \"Every write-up you have had since is generated from the running system rather than typed, so what you read is what would send.\",\n },\n {\n at: \"2026-08-02\",\n kind: \"mine\",\n what: \"I gave you a missed-calls figure that was too high, because it was counting people arriving at the gate as well as people calling. You spotted it before I did.\",\n evidence: \"Recounted with gate arrivals excluded, and the same exclusion now runs on every list that comes out of here.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"mine\",\n what: \"I told you a list had been deleted and then left the old one sitting in your Drive for a day. Two versions of the same list is exactly the confusion I was trying to save you from.\",\n evidence: \"The old one is in the trash and the folder was checked afterwards; only one version exists.\",\n },\n {\n at: \"2026-08-03\",\n kind: \"mine\",\n what: \"You asked me something at 8:20 and my reply at 8:27 answered everything except that. Answered since.\",\n evidence: \"Both messages re-read against each other so the gap could be found rather than assumed.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"found\",\n what: \"Once it was measured, the follow-up system turned out to be running about hourly and the watchdog slower still, rather than four times an hour as this page used to claim. Nothing is harmed by that, because the messages are scheduled by the day, but it was worth knowing rather than assuming.\",\n evidence: \"Both were watched without being touched, then run by hand to confirm the code itself was healthy. Both ran cleanly. Do not read the rhythm off this line: the health card above measures the gaps between actual runs and prints what it currently observes, which is the only figure either of us should trust.\",\n },\n {\n at: \"2026-08-04\",\n kind: \"mine\",\n what: \"The count of new customers on this page was reading low. It was looking at only the most recent slice of your records, which missed anyone who first got in touch a while ago and only became a customer this week.\",\n evidence: \"The whole Customer list is now read every time rather than the first slice of it, in about a second. For the last seven days that changed the figure from 2 to 5.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"found\",\n what: \"The second system that checks the first one was set to look once a day, not once an hour. It has been changed to hourly. Nothing was broken; it was just looking far less often than the things it watches can go wrong.\",\n evidence: \"Read off its own settings screen: it said once every 1 days, and its last run had been 13 hours earlier. The follow-up system runs on the hour, so a problem starting just after the checker looked could have sat unnoticed until the next day. It now runs hourly, which matches what it is checking. Everything it looks at was still being looked at throughout.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"mine\",\n what: \"This page told you the checker runs itself about every 95 minutes. That came from the times Amir had started it by hand, so it was a real measurement of the wrong thing. I then went further and wrote that its timer was not firing at all. That was wrong twice over: it was firing, and the only reason my new counter showed nothing was that the counter itself was broken.\",\n evidence: \"The two kinds of run are recorded separately now, and both were watched working before this was written: a scheduled run recorded as scheduled, a hand-started one as by hand. The page no longer guesses at causes either. It reports what it has and has not seen and leaves the diagnosing to a person, which is what I should have done before writing that sentence the first time.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"mine\",\n what: \"Two of our systems were describing the same pile of unmatched counter sales with different figures. One said 35 sales worth $23,463.99, the other said 40 worth $28,035.99.\",\n evidence: \"The payment records were counted again from scratch, a third time and by a different method: 40 is correct. The lower figure came from skipping some sales and from subtracting two things that were not the same kind of thing. Both systems now read the same single count, so they cannot disagree again.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"found\",\n what: \"On your missing call transcripts, a correction of ours. This page said earlier today that transcription had never been switched on. That was wrong: a call from this morning was opened and its full written transcript was watched rendering. Transcription works, at least sometimes, so the real question is which calls are missing theirs.\",\n evidence: \"The wrong version was reasoned from the reading connection, which never carries transcripts, and that gap was mistaken for the transcripts not existing. The corrected question is on the list above: one example from Kim of a call that should have a transcript and does not is the fastest way to pin down the pattern.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"built\",\n what: \"The missing third step is built. Something now works out which of your inquiries is about a puppy, and it runs alongside everything else so you can see what it would do before it does anything.\",\n evidence: \"It has applied nothing and it cannot: the part that decides has no way to change anything in your account, which is checked automatically. Its first run over your most recent contacts is on the question list above, with its own numbers. A full pass over 1,200 of your records is written up separately for Amir to check line by line.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"mine\",\n what: \"My first attempt at spotting a puppy inquiry would have signed up three people who should not have been: a man asking to buy a puppy, a woman rehoming her older dogs, and a dog described as three years and four months old that got read as four months.\",\n evidence: \"Each of those three is now a rule, each rule has a test, and each test has a check that breaks the rule on purpose and demands the test notice. None of them reached anybody, because nothing has been switched on.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"found\",\n what: \"One of your knowledge bases was edited at around half past ten last night, and nothing was keeping an eye on it. If that was you, everything is fine and this is just us noticing.\",\n evidence: \"The consolidated one, which is what Chloe answers customers from. Nothing on our side touched it. Until this morning we were watching your 165 automations for changes but not the documents that decide what your business actually says, which was a gap.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"built\",\n what: \"Your knowledge bases are now watched the same way your automations are. If one of them changes, it gets written down with what moved and when, whoever did it.\",\n evidence: \"Running live. It cannot read the wording inside the documents, only that something changed and which one, so it will not police your writing. The part that spots a change is tested on its own, including the case that matters most: a document edited in place, where nothing is added and nothing is removed.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"mine\",\n what: \"The counter I built to prove the checker keeps its own time was itself broken, and it made a healthy system look dead. It recorded nothing for scheduled runs, so the page reported none had happened while they were happening every hour.\",\n evidence: \"Found by opening the running record rather than trusting my own counter: the scheduled runs were there, one line away from where I was looking. Both kinds of run have now been watched being recorded correctly, one of each, before this was written down.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"fixed\",\n what: \"The two contact records for Kristina were merged into one, exactly as you asked. The phone number that survived is the one she actually rang from, the accidental do-not-disturb is off, her Meet and Greet is untouched, and the typo number is gone.\",\n evidence: \"Her inbound call this morning proves which number is real, so that one was kept. The duplicate had also been dropped into the no-sale and tips nurtures, which would have messaged a person who has an appointment booked on Monday; those did not carry over, and one click puts them back if wanted.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"built\",\n what: \"The first two real puppy inquiries are marked and waiting: Walle's owner, whose Pup Talk is this afternoon, and Kristina, who was marked this morning. Nothing sends to either of them while practice mode is on, and the system deliberately stays quiet for anyone with a call still on the calendar.\",\n evidence: \"Both are visible in the count on this page, which reads your records live. The one switch that remains is the practice-mode switch, and that gets thrown deliberately, not quietly.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"changed\",\n what: \"Walle's owner came off the puppy track before it ever sent her anything, and that is the agreed rule working: she booked. Her Free Training Day is on the calendar for Friday morning, her Pup Talk moved to Thursday afternoon, and during those changes the puppy mark came off her record. One inquiry is marked and waiting now, Kristina.\",\n evidence: \"Read live from her record on the evening of 5 August: the Friday booking is on the calendar, the mark is off, and the count on this page reflects whatever is true when you open it. If she should get the puppy messages after her visit anyway, putting the mark back is one click.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"found\",\n what: \"The tag red flag turns out to be wired to a workflow that came with your system: anyone who gets that tag is switched to do-not-disturb. It was put on five people this week, and all five are on do-not-disturb right now, which means nothing will message them.\",\n evidence: \"Each of the five records was opened and read live on the evening of 5 August, and every one shows do-not-disturb on. They are listed by name in the tag report. Taking the tag off does not switch do-not-disturb back off on its own.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"built\",\n what: \"The holiday deposit check you asked for is on your page. It reads both boarding calendars for Thanksgiving week and 20 December to 2 January, puts one customer's dogs on one line, leaves out your regular weekly bookings and anything cancelled, and shows which stays have a card payment on file. Right now that is two stays, both worth a look.\",\n evidence: \"It ran against your live account at 15:42 on 6 August and the list came back in under three seconds. Jeffrey Musselwhite's three dogs on 25 November show as one stay, not three, and Enzo's standing Friday slot is left out even though it lands inside every holiday window. It will never say somebody has not paid: a deposit handed over in cash or taken on the phone does not reach the card system, so this is a shortlist to look at.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"found\",\n what: \"Your card payments do reach your CRM after all, in two different shapes, and one of them was invisible to me until this morning. Some land as a plain payment line; others land as a till payment matched to a card payment later. I had only been reading the first kind.\",\n evidence: \"Both shapes are sitting on the same customer's record right now with the same $35 on them and two different reference numbers. If somebody's only record had been the second kind, the deposit check would have shown them as having nothing on file. It reads both now, and where the same money appears twice it is counted once rather than doubled.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"mine\",\n what: \"Twice today I had the deposit check guessing which card payment was the deposit, and twice it was wrong in the direction that costs you money. The first version treated any payment between the booking and the stay as the deposit, so a customer's $355 training package marked their $50 as settled. The second only looked at the ten days around the booking, which then missed a real $50 paid eight days later.\",\n evidence: \"It has stopped guessing. A stay is only marked settled by a card payment for exactly $50. Everything else on the account near that stay is listed with its date and amount and left for you to judge, which is the two-second version of what you were doing by hand. A wrong 'worth a look' costs you a glance. A wrong 'settled' costs you fifty dollars and you never find out.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"built\",\n what: \"The deposit list now knows how long a stay actually is, by reading your pick-up calendars as well as your drop-off ones. Jeffrey's three dogs show as 25 to 28 November rather than a single day, and anybody who drops off before a holiday and stays through it now appears at all.\",\n evidence: \"A drop-off booking in your system is a ten minute slot, so on its own it cannot say how long a dog stays. Checked against your live calendars on 6 August: Ghost and Chewy drop off on the 25th and are collected on the 28th, and only the pick-up calendar says so. If a pick-up calendar does not answer, the page says so rather than quietly showing a shorter list.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"mine\",\n what: \"The first time the deposit check ran for real it was about to tell you your card payments had stopped working, on the strength of two customers with nothing on file. Two quiet customers is a normal week, not an outage. I had written the warning to fire whenever nobody at all had a payment, without asking how many people that was.\",\n evidence: \"Caught by watching the first live run at 15:41 on 6 August rather than by reading the code. It now needs at least five customers checked before it will suggest anything is wrong with the payment feed, and the second run at 15:42 gave you the plain list instead of the warning.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"mine\",\n what: \"I told you the customer chased after booking was the only one it had ever happened to. That was wrong, and I said it with more confidence than my checking deserved. Four people were chased after they had already booked, going back to April: Brianna Badger, Janiya Williams, Michelle Burkard and Thomas.\",\n evidence: \"The first answer came from looking at two people with upcoming bookings. The real one comes from every Free Training Day booking you have ever taken, 80 of them across 69 people, each checked against their own messages. Three of the four came to their session anyway. Michelle's first booking was cancelled after her chase and she rebooked five days later, which is an order of events rather than a proven cause.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"found\",\n what: \"Your missing call transcripts, with one thing I got ahead of myself on. No transcript exists on any call older than about three months, and since then almost everything with speech on it has been written down. I told you that was the date transcription got switched on. I cannot actually tell that from here.\",\n evidence: \"207 calls were opened one at a time, everything inside your hundred most recently active conversations, and each was asked directly for its transcript and its recording. Before 11 May: 45 calls, none transcribed, though 38 of them still play their audio. From 11 May: 162 calls, 127 transcribed. Of the 35 without, 31 were nobody answering and 2 failed to connect. In that sample one call was recorded and never written down, on 4 August at 11:09 in the morning. The honest part: the oldest transcript we can find is 87 days old, which is either the day it was switched on or the age at which transcripts get deleted. Those look identical from here. If they expire, you are losing a month of call history every month, so it matters. One query in a week settles it: if the oldest surviving transcript has moved forward, they expire. That check is now on the list.\",\n },\n {\n at: \"2026-08-06\",\n kind: \"built\",\n what: \"While practice mode is on, the parts that actually send a text or an email now refuse anyone except the single test record, and they refuse from a standing start rather than after being told who is safe.\",\n evidence: \"The refusal sits inside the sending functions themselves, so it holds even if something upstream enrolled the wrong person by mistake. It is switched on and running now. There is a test that proves it, and a second check that deletes the guard on purpose and demands that test go red.\",\n },\n {\n at: \"2026-08-05\",\n kind: \"fixed\",\n what: \"A customer who had already booked his Free Training Day got chased by an older funnel to book one, two texts, a voicemail and another text, because that funnel only counts bookings made through its own page and cannot see the calendar. He was taken out of it at half past six this evening.\",\n evidence: \"His record shows no active workflows since the removal, checked after a full page reload. At the time this was written I had checked the two other people with upcoming bookings and found them clean. That was too small a check to carry the sentence it was carrying, and the entry above from 6 August corrects it: four people have been chased after booking, not one. The follow-up system on this page had nothing to do with it: practice mode was on all day and it sent nothing, checked live the same evening.\",\n },\n];\n\nexport function mergeLog(seeded: WorkEntry[], live: WorkEntry[] | null | undefined): WorkEntry[] {\n const all = [...seeded, ...(Array.isArray(live) ? live : [])];\n const seen = new Set();\n const out: WorkEntry[] = [];\n for (const e of all) {\n if (!e || typeof e.at !== \"string\" || typeof e.what !== \"string\" || !e.what.trim()) continue;\n // v1.1 (review #6): dedupe on the FULL sentence. A 60-character prefix collapsed two\n // different outages on the same day into one row, so the second incident never reached Kim.\n const key = `${e.at}|${e.kind}|${e.what}|${e.evidence ?? \"\"}`;\n if (seen.has(key)) continue;\n seen.add(key);\n out.push(e);\n }\n // newest first. Within one day the LATEST-added entry leads, so a broke/recovered pair on the\n // same date reads \"back to normal\" above \"broke\", which is the order a human wants to see.\n return out\n .map((e, i) => ({ e, i }))\n .sort((a, b) => (a.e.at === b.e.at ? b.i - a.i : (b.e.at > a.e.at ? 1 : -1)))\n .map((x) => x.e);\n}\n\nexport const KIND_LABEL: Record = {\n mine: \"My mistake\",\n fixed: \"Fixed\",\n built: \"Built\",\n found: \"Found\",\n broke: \"Broke\",\n recovered: \"Back to normal\",\n changed: \"Changed\",\n};\n","label",[163],"76ccb05b-aa83-4e7f-bb12-5de516cbdfeb","taper-messages.ts","65f1a7b2-900c-11f1-948d-1607ee4eb77e",199,["D",1785973623529],10,"// SLOW TRACK (TAPER) — message copy module. Companion to puppy-messages.ts.\n// Spec is Kim's own, verbatim from her Upwork message 3 Aug 2026, 8:11 PM:\n// \"I'd like something to taper off rather than just drop. Something like a text or email\n// once a week for month then every two weeks for 6 months then every month moving forward.\"\n// Committed shape (confirmed back to her, 8:27 PM): after the 21-day main sequence ends —\n// weekly x4, then fortnightly x13 (~6 months), then monthly indefinitely.\n// HARD RULE, promised to Kim in writing: NO ask attached to any taper message. No booking\n// links, no CTAs, no phone-number pushes — replying to the message itself is the only channel\n// offered. \"The job of that track is that\n// when they finally do need training or boarding, you're the name they already know.\"\n// Same engine rules underneath: reply -> paused for a human; booking -> off the track;\n// STOP -> never contacted again. All enforced engine-side, same as the main sequence.\n\nimport { PHONE_DISPLAY, type MessageTemplate } from \"./puppy-messages.ts\";\n\n// Offsets are hours RELATIVE TO SLOW-TRACK ENTRY (the moment main-8 fires, day 21 absolute).\n// Weekly: rel days 7 / 14 / 21 / 28 = absolute days 28 / 35 / 42 / 49\n// Fortnightly: rel days 42 .. 210 (13 x 14) = absolute days 63 .. 231\n// Monthly: rel day 240 onward, every 30 = absolute day 261 onward, forever\n\nexport const SLOW_WEEKLY: MessageTemplate[] = [\n {\n id: \"slow_w-1\",\n channel: \"email\",\n offsetHours: 168, // rel day 7\n subject: \"The teenage phase is coming (this is normal too)\",\n previewText: \"Somewhere between six and twelve months, trained puppies act untrained. Here's why.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nOne thing I wish more people were warned about: somewhere between six and twelve months, your dog will probably go through a teenage phase. The recall that was working stops working. The chewing comes back. A dog who knew \"sit\" looks at you like they've never heard the word.\n\nThis isn't your training failing, and it isn't the puppy teething back again - that part really does settle, like I said in the early emails. This is adolescence: hormones and a growing brain re-testing every rule, exactly like human teenagers do. Dogs who were doing great at five months often look like a mess at eight, and the owners who don't know it's a phase assume they've done something wrong.\n\nTwo things carry you through it: keep the routines boring and consistent even when they seem pointless, and keep rewarding the behavior you want as if your dog were still tiny. It passes. The dogs who come out of it best are the ones whose people didn't give up on the rules halfway through.\n\n{{STORY:teenage}}\n\nReply anytime - a real person reads these.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_w-2\",\n channel: \"sms\",\n offsetHours: 336, // rel day 14\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim at The Dogs Spot. A tip that saves furniture: rotate your dog's toys - keep most in a closet and swap a few out every couple of days. Old toys become new again, and a dog with something interesting to chew rarely invents their own project. Reply anytime.`,\n },\n {\n id: \"slow_w-3\",\n channel: \"email\",\n offsetHours: 504, // rel day 21\n subject: \"Socialization doesn't stop - it just changes shape\",\n previewText: \"The window closes, but the habit shouldn't.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nWhen your dog was tiny, the job was meeting the world before the socialization window closed. That window does close - but the habit shouldn't. A dog who met the mail carrier calmly at twelve weeks can still decide the mail carrier is suspicious at eight months if the meetings stop.\n\nThe maintenance version is lighter than the puppy version. A different walking route once a week. Ten minutes watching the world go by outside a coffee shop. A calm hello with a steady adult dog now and then. You're just keeping the file open: people, dogs, noises, places, all still no big deal.\n\nThe dogs who stay easy in public are almost never the ones with the most training. They're the ones whose world stayed wide.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_w-4\",\n channel: \"sms\",\n offsetHours: 672, // rel day 28\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. A two-minute recall game that works: someone holds your dog, you walk away looking excited, then call once and celebrate like they won the lottery when they arrive. Dogs repeat what pays.`,\n },\n];\n\nexport const SLOW_FORTNIGHTLY: MessageTemplate[] = [\n {\n id: \"slow_f-1\",\n channel: \"email\",\n offsetHours: 1008, // rel day 42\n subject: \"Teaching your dog that alone is fine\",\n previewText: \"Separation ease is trained, not hoped for.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThe single most underrated skill for a young dog: being alone and being fine about it. It doesn't happen by accident - dogs are social animals, and a dog who is never alone learns that alone is alarming.\n\nBuild it in small doses. Leave for two minutes and come back before any fuss starts, then five, then twenty. Keep departures and returns boring - no big goodbyes, no big reunions. A stuffed chew or a lick mat that only appears when you leave turns your exit into a good sign instead of a bad one.\n\nThe goal isn't a dog who tolerates your absence. It's a dog who hears the keys and thinks \"snack time\", then has a nap.\n\n{{STORY:alone_time}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-2\",\n channel: \"sms\",\n offsetHours: 1344, // rel day 56\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Loose-leash tip: the moment the leash goes tight, stop walking. Move again only when it slackens. Boring, repetitive, and it works better than any gadget - pulling stops paying, so pulling stops. Reply if it stalls.`,\n },\n {\n id: \"slow_f-3\",\n channel: \"email\",\n offsetHours: 1680, // rel day 70\n subject: \"Vet visits without the drama\",\n previewText: \"Five minutes of practice at home changes every appointment for life.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nA dog's opinion of the vet is mostly formed before anything medical ever happens. You can shape it at home, five minutes at a time.\n\nHandle your dog's paws, ears and mouth while they're relaxed - a touch, then a treat, done before they mind. Pop them on a table or a mat, brief and calm, same deal. If you're ever passing your vet's clinic, walk in, let the front desk say hello and hand over a treat, and leave. Visits where nothing happens are what make the real ones manageable.\n\nA dog who's been handled kindly a hundred times at home barely notices an examination. One who's only ever grabbed when something hurts learns the opposite lesson.\n\n{{STORY:vet_visits}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-4\",\n channel: \"sms\",\n offsetHours: 2016, // rel day 84\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim at The Dogs Spot. If your dog goes wild in the evenings - the witching hour is real. It's usually overtiredness, not excess energy. A chew and enforced quiet time settles it faster than another walk. Reply if evenings are still chaos, happy to help.`,\n },\n {\n id: \"slow_f-5\",\n channel: \"email\",\n offsetHours: 2352, // rel day 98\n subject: \"The off switch\",\n previewText: \"The most useful thing a dog can learn isn't a trick.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThe most useful thing your dog can learn isn't a trick - it's an off switch. A dog who can lie on a mat and do nothing while life happens around them gets taken everywhere. A dog who can't gets left at home, which shrinks their world and makes everything harder.\n\nTeach it like anything else. A mat or a bed, a treat for lying on it, then gradually longer stays and gradually more interesting distractions - someone walking past, the doorbell, dinner being eaten. Reward calm, quietly, before they break. Minutes a day, and within a few weeks you have a dog you can take to a restaurant patio.\n\nIt's not glamorous. It changes more about daily life than any other single thing you can train.\n\n{{STORY:settle}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-6\",\n channel: \"sms\",\n offsetHours: 2688, // rel day 112\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Jumping on guests fix: have visitors ignore your dog completely until all four paws are on the floor, then greet warmly. Attention is what they're after. Give it for standing, never for jumping. Consistency from everyone is the whole trick.`,\n },\n {\n id: \"slow_f-7\",\n channel: \"email\",\n offsetHours: 3024, // rel day 126\n subject: \"Dog parks: the honest version\",\n previewText: \"When they help, when they don't, and what to watch.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nDog parks divide opinion, so here's the honest version: they're brilliant for some dogs and genuinely bad for others, and the difference isn't friendliness - it's what happens there.\n\nWatch play, not intentions. Good play has role swaps: chaser becomes chased, wrestler ends up underneath, both dogs keep opting back in. If your dog is always the one being chased, or hiding under benches, or the one doing all the pinning, it isn't play anymore, and every bad visit teaches something you'll later have to untrain.\n\nThe useful test: call your dog out of play now and then, reward, release back. If you can't call them out, the park is training them - just not in the direction you want. A few good dogs beat a big crowd of random ones.\n\n{{STORY:dog_parks}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-8\",\n channel: \"sms\",\n offsetHours: 3360, // rel day 140\n bodyTemplate: `Hi {{FIRST_NAME}}, it's Kim. While I'm thinking about it: feed your dog a few meals in the parked car, engine off, before expecting calm car rides. Cars should predict good things, not just vet trips. Short happy drives to nowhere do the same job. Tell me how it goes, I read these.`,\n },\n {\n id: \"slow_f-9\",\n channel: \"email\",\n offsetHours: 3696, // rel day 154\n subject: \"Boredom looks a lot like bad behavior\",\n previewText: \"Ten minutes of nose work tires a dog more than an hour of fetch.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nMost \"bad behavior\" in young dogs is unemployment. A dog with nothing to do writes their own job description, and it usually involves your baseboards.\n\nThe fix isn't always more exercise - physical exercise builds fitness, and a fitter dog just has more stamina for mischief. Mental work is what actually tires them. Scatter your dog's food in the grass instead of a bowl and let them sniff it out. Hide treats around one room. A snuffle mat, a frozen Kong, a cardboard box with food inside it to be destroyed. Ten minutes of nose work drains more out of a dog than an hour of fetch, because sniffing is thinking.\n\nA tired dog is a good dog, but the right kind of tired is mental. It's also the cheapest training aid there is.\n\n{{STORY:nose_work}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-10\",\n channel: \"sms\",\n offsetHours: 4032, // rel day 168\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Brushing habit worth keeping: one minute after dinner, every day, treat at the end. Daily and brief beats weekly and a wrestle - and you'll spot lumps, ticks and sore spots before they're problems. Reply anytime.`,\n },\n {\n id: \"slow_f-11\",\n channel: \"email\",\n offsetHours: 4368, // rel day 182\n subject: \"Two dogs meeting on leash: what's actually going on\",\n previewText: \"What a tight leash does to friendly dogs, and the walk-along trick.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nA strange thing you'll notice: two perfectly friendly dogs can bristle at each other on leash when the same two would be fine loose. It isn't contrariness. The leash changes the conversation.\n\nDogs read each other sideways - they approach in curves, sniff rears, keep options open. A tight leash forces a head-on approach with no escape route, which in dog language reads as confrontation. The tension travels down the leash too: you tighten up, and your dog decides there must be something to tense about.\n\nWhat helps: keep the leash loose even when it takes nerve, approach in an arc rather than straight on, and if you want two dogs to make friends, walk them side by side in the same direction first and let the sniffing happen on the move. Side by side works. Head-on mostly doesn't.\n\n{{STORY:leash_meetings}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_f-12\",\n channel: \"sms\",\n offsetHours: 4704, // rel day 196\n bodyTemplate: `Hi {{FIRST_NAME}}, it's Kim again. One that surprises people: use part of your dog's daily ration as training treats instead of adding extras on top. Same calories, more practice, no expanding waistline. The dog doesn't know the difference - it all counts as winning.`,\n },\n {\n id: \"slow_f-13\",\n channel: \"email\",\n offsetHours: 5040, // rel day 210\n subject: \"From here on, about once a month\",\n previewText: \"The rhythm changes, the door stays open.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nQuick housekeeping note rather than advice this time: I've been in your inbox every couple of weeks since your dog was small, and from here I'll drop to about once a month - short, seasonal, still a thirty-second read, I promise.\n\nBy now most of the foundations are in: the world stayed wide, alone is fine, the leash is mostly loose, and the teenage phase either happened or is happening and will pass either way.\n\nIf anything ever comes up in between - a behavior that's new, a question that nags - reply to any of these. A real person reads them, always has.\n\nKim\nThe Dogs Spot`,\n },\n];\n\n// Monthly bank — chosen by the CALENDAR MONTH the send lands in (0 = Jan .. 11 = Dec),\n// so the seasonal ones land in season regardless of when the contact entered the track.\n// This is what was promised to Kim: \"seasonal where it fits: settling a dog over the\n// holidays, heat and paws in July, fireworks.\" offsetHours on these entries is ignored\n// by the scheduler (cadence is every 720h from rel day 240); template chosen by month.\nexport const SLOW_MONTHLY_BANK: MessageTemplate[] = [\n {\n id: \"slow_m-jan\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"January: the quiet month is a training month\",\n previewText: \"Short days, big opportunity.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nJanuary is short walks and dark evenings, which makes it a surprisingly good training month. Five minutes of indoor work a day, a settle on the mat or some paw-and-ear handling practice, carries further than one heroic cold-weather hike a week.\n\nGeorgia winters are mild, but a cold snap still ices a morning path now and then - so a quick paw check after those walks is smart.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-feb\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim at The Dogs Spot. Wet-weather boredom builds mischief - a stuffed Kong from the freezer or dinner scattered in a snuffle mat gets you a calm evening. Mental work counts double in February. Reply anytime.`,\n },\n {\n id: \"slow_m-mar\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Spring: the world wakes up, so does the sniffing\",\n previewText: \"Let the nose have its season.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nEverything smells new in spring, and you'll feel it down the leash. Rather than fight it, give sniffing its own time: pick a stretch of the walk where your dog sets the pace and the route, nose down, no agenda. Sniffing is a dog reading the news, and ten minutes of it settles them more than double the distance at a march.\n\nOne more spring thing: tick season opens now. A quick run of the hands after grassy walks catches them early.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-apr\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Spring reminder, same one every year: chocolate is flat-out dangerous for dogs. If there's been an egg hunt anywhere near your yard, a nose will find what the kids missed, sometimes weeks later. Keep the candy high and the vet's number where you can find it.`,\n },\n {\n id: \"slow_m-may\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Before summer: build the water habit\",\n previewText: \"Warm-weather prep is easier before it's hot.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nA little prep now makes summer easier. Get your dog used to drinking on walks - carry water and offer it before they seem thirsty, so it's routine by the time it matters. If a kiddie pool or the sprinkler might feature, introduce them gently now while they're novelty rather than necessity.\n\nAnd as the winter coat blows out, a few minutes of brushing a day now saves your furniture a month of fur. One thing to know before summer: never shave a double-coated breed to cool them down - that coat insulates against heat as well as cold, and they're worse off without it.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-jun\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim at The Dogs Spot. Summer rule of thumb: put the back of your hand on the pavement for seven seconds. Too hot for your hand, too hot for your dog's paws - walk early or late instead. Any summer questions, just reply.`,\n },\n {\n id: \"slow_m-jul\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"July: heat, paws and fireworks\",\n previewText: \"The two summer hazards, and the one that sneaks up.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nJuly's the month I nag about heat. Dogs don't sweat like we do - they cool by panting, which stops working in a hot car in minutes, even parked in shade with windows cracked. Walks move to early morning or late evening, water goes everywhere you go, and pavement gets the seven-second hand test before your dog's paws touch it.\n\nThe one that sneaks up: fireworks around the Fourth. If your dog is nervous of bangs, plan the evening - walk before dark, close curtains, put on some background noise, and let them den up wherever they choose. Comforting a scared dog doesn't reward fear, whatever the old advice said. Sit with them.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-aug\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Late-summer water check: lakes and ponds can grow blue-green algae in August - it's toxic to dogs, sometimes fatal. If the water looks like pea soup or has a scum line, your dog stays out, no exceptions.`,\n },\n {\n id: \"slow_m-sep\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"September: the routine change nobody warns dogs about\",\n previewText: \"Back-to-school hits dogs too.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nSeptember quietly rearranges a dog's whole day: the house empties, walks move, the kids who were constant company vanish for hours. Dogs don't read calendars, so the change lands without warning, and a bit of chewing or barking that starts this month is usually the adjustment talking.\n\nEase it the same way you built alone-time in the first place: short practice absences, something good that only appears when the house empties, and low-key exits. A week of short practice runs saves a month of stress.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-oct\",\n channel: \"sms\",\n offsetHours: 0,\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Halloween heads-up: the doorbell going all evening plus strangers in masks is a lot for most dogs. A chew in a back room with the radio on beats managing the door. And candy, especially sugar-free with xylitol, is dangerous for dogs - keep the bowl high.`,\n },\n {\n id: \"slow_m-nov\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"November: guests, feasts and a dog with opinions\",\n previewText: \"Getting ahead of the holiday chaos.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThe holiday season starts here, and for your dog it mostly means two things: the house fills with people, and the house fills with food at nose height.\n\nThe settle-on-a-mat work comes into its own now - a dog with a place to be, and something to chew there, rides out a busy dinner far better than one loose in the middle of it all. Brief the guests too: no feeding from plates, however charming the eyes. Rich, fatty leftovers are one of the most common reasons dogs see an emergency vet this time of year. The big ones to keep off the floor: onions, grapes and raisins, and any cooked bone.\n\nA walk before guests arrive takes the edge off everything.\n\n{{STORY:holidays}}\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"slow_m-dec\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Settling a dog over the holidays\",\n previewText: \"Trees, tinsel, visitors and routine.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nDecember, quickly, because you're busy: keep your dog's routine as boring as you can manage while everything else changes - same meal times, same walks, same bedtime. Dogs take their stability from routine, and a steady dog copes with a chaotic house far better than the other way around.\n\nTree-wise: chocolate decorations are a vet visit waiting to happen, tinsel and ribbon are surgery if swallowed, and a curious tail plus low ornaments ends how you'd expect. Hang anything precious or edible high.\n\nHowever the season goes, thank you for letting me stay in your inbox this year. Reply anytime - a real person reads these, holidays included.\n\nKim\nThe Dogs Spot`,\n },\n];\n\n// ---- scheduler helpers (pure, testable) ---------------------------------------------------------\n\nexport const SLOW_WEEKLY_COUNT = 4;\nexport const SLOW_FORTNIGHTLY_COUNT = 13;\nexport const SLOW_MONTHLY_START_REL_HOURS = 5760; // rel day 240 (abs day 261)\nexport const SLOW_MONTHLY_INTERVAL_HOURS = 720; // 30 days\n\n// Given how many slow-track messages have already been sent to a contact, return the next\n// one: its template (or, for monthly, the bank + a note to pick by landing month) and its\n// offsetHours relative to slow-track entry. Returns null never — the track is indefinite.\nexport function nextSlowTouch(sentCount: number): {\n phase: \"weekly\" | \"fortnightly\" | \"monthly\";\n template: MessageTemplate | null; // null for monthly — engine picks by landing month\n offsetHours: number;\n} {\n if (sentCount < SLOW_WEEKLY_COUNT) {\n return { phase: \"weekly\", template: SLOW_WEEKLY[sentCount], offsetHours: 168 * (sentCount + 1) };\n }\n const f = sentCount - SLOW_WEEKLY_COUNT;\n if (f < SLOW_FORTNIGHTLY_COUNT) {\n return { phase: \"fortnightly\", template: SLOW_FORTNIGHTLY[f], offsetHours: 672 + 336 * (f + 1) };\n }\n const m = sentCount - SLOW_WEEKLY_COUNT - SLOW_FORTNIGHTLY_COUNT;\n return {\n phase: \"monthly\",\n template: null,\n offsetHours: SLOW_MONTHLY_START_REL_HOURS + SLOW_MONTHLY_INTERVAL_HOURS * m,\n };\n}\n\n// Monthly template for a given send date (calendar-month keyed, so seasonal copy lands in season).\nexport function monthlyTemplateFor(sendDate: Date): MessageTemplate {\n return SLOW_MONTHLY_BANK[sendDate.getMonth()];\n}\n\n// v1.7.1 — same, but never the same message twice in a row. The 30-day grid drifts through the\n// calendar, so two consecutive sends can land in one calendar month (the 1st and the 31st):\n// without this the identical email goes out twice, and December's \"thank you for letting me stay\n// in your inbox this year\" twice in a month reads as a broken robot. If this month's template was\n// the last thing sent, serve next month's instead.\nexport function monthlyTemplateAvoidingRepeat(sendDate: Date, lastSentId: string | null | undefined): MessageTemplate {\n const tpl = SLOW_MONTHLY_BANK[sendDate.getMonth()];\n return lastSentId && tpl.id === lastSentId ? SLOW_MONTHLY_BANK[(sendDate.getMonth() + 1) % 12] : tpl;\n}\n",[175],"36659075-120a-4f67-995b-203ed981f4fa","run.ts","be37b584-8e76-11f1-b9e0-1607ee4eb77e",14,["D",1785678975976],1,"http","// CHECK NOW — manual trigger for the nurture engine. Built 2 Aug 2026.\n//\n// WHY\n// main.ts is a val.town `interval` file. Its schedule is set in val.town's UI and cannot be read or\n// triggered through the API, which left two real problems: (1) nothing could be verified end-to-end\n// on demand — including the kill switch, which is the one control the client must be able to trust;\n// (2) if the schedule ever stalls there is no way to make the system catch up without a human\n// opening val.town. This file closes both. It imports the same cron() the scheduler calls, so there\n// is exactly one code path — a manual run is not a different run.\n//\n// SAFETY\n// Same admin key as the control panel. Every guard inside cron() still applies in full: the kill\n// switch is checked first, TEST_MODE still defaults on, the run lock still prevents overlap with a\n// scheduled tick, and the send ceilings are unchanged. This adds a trigger, never a bypass.\n//\n// ?k= run once, return the run report as JSON\n// ?k=&dry=1 report what the engine WOULD do without invoking it — resolves nothing, just\n// confirms this endpoint is wired and the key is right\n\nimport cron from \"./main.ts\";\n\n// ---- auth ------------------------------------------------------------------------------------\n// v2 (2 Aug, after the adversarial pass): the key is NOT in this file. val.town vals are PUBLIC —\n// proved by fetching this very source with no token — so a literal key here was readable by anyone\n// who found the val, which meant anyone could read Kim's data, stop her system, or trigger a run.\n// Only the SHA-256 digest lives in source now. The digest is useless to a reader and sufficient for\n// a comparison, so publishing the code no longer publishes the secret.\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\n\nasync function sha256Hex(s: string): Promise {\n const b = await crypto.subtle.digest(\"SHA-256\", new TextEncoder().encode(s));\n return [...new Uint8Array(b)].map((x) => x.toString(16).padStart(2, \"0\")).join(\"\");\n}\n\nasync function authorised(k: string): Promise {\n const override = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\");\n const expected = override || KEY_SHA256;\n const got = await sha256Hex(k);\n // Constant-time over equal-length hex digests.\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\n\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n if (!(await authorised(url.searchParams.get(\"k\") || \"\"))) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n if (url.searchParams.get(\"dry\") === \"1\") {\n return new Response(JSON.stringify({ wired: true, note: \"endpoint live; pass without &dry=1 to actually run\" }, null, 2), {\n headers: { \"content-type\": \"application/json\" },\n });\n }\n const startedAt = new Date().toISOString();\n try {\n const report = await cron();\n return new Response(JSON.stringify({ triggeredAt: startedAt, report }, null, 2), {\n headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" },\n });\n } catch (e) {\n return new Response(JSON.stringify({ triggeredAt: startedAt, error: String(e).slice(0, 900) }, null, 2), {\n status: 500,\n headers: { \"content-type\": \"application/json\" },\n });\n }\n}\n",[183],"d4ec88bc-177d-4056-89cd-7ac98c79ed49","report.ts","7a35076a-901f-11f1-8a2e-1607ee4eb77e",70,["D",1785865311684],"// FRIDAY REPORT, HTTP endpoint. Renders the week's numbers live from the CRM, saves a Friday\n// snapshot so next week can reference this week honestly. v1.0, 4 Aug 2026.\n//\n// ROUTES ?k= the report page (most recent complete Fri-Fri week)\n// ?k=&save=1 snapshot this week's numbers + draft commentary\n// (auto-save: first ADMIN view on a Friday ET saves the snapshot if missing)\n//\n// DATA every number from the GHL API at render time, computed in report-logic.ts, formulas\n// printed in the appendix. Ad platform numbers appear the day META_TOKEN / GADS creds\n// exist in the val env; until then those cells say \"not tracked yet\" and nothing is\n// estimated. Reconciliation (platform-claimed leads vs contacts that actually landed)\n// switches on the same day.\ndeclare const Deno: { env: { get(k: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\nimport {\n reportWindows, inWindow, countContacts, sourceBreakdown, countEvents, wonOpps,\n weeklyBuckets, pct, deltaWord, money, draftCommentary, FORMULAS, type ContactLite, type EventLite, type OppLite,\n} from \"./report-logic.ts\";\n\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst PUP_TALK_CAL = \"qHuYJ0NEqzibnoqf5Cw3\";\nconst FTD_CALS = [\"K24xHYRExFJDEGpgSNVB\", \"bLn88LGOYYOZ3NySO1EZ\"]; // Free Dog Training Day + Free Training Day\n// v1.0.1 (review fix #3) — computed PER REQUEST, not at module load: val.town keeps modules\n// warm across the DST changeover, and a stale offset shifts every window an hour and can\n// double-save Thursday's snapshot under Friday's key.\nfunction etOffsetMin(atMs: number): number {\n const fmt = new Intl.DateTimeFormat(\"en-US\", { timeZone: \"America/New_York\", timeZoneName: \"shortOffset\" });\n const part = fmt.formatToParts(new Date(atMs)).find((p) => p.type === \"timeZoneName\")?.value ?? \"GMT-4\";\n const m = part.match(/GMT([+-]\\d+)/);\n return m ? Number(m[1]) * 60 : -240;\n}\n\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\nasync function sha256Hex(s: string): Promise {\n const b = await crypto.subtle.digest(\"SHA-256\", new TextEncoder().encode(s));\n return [...new Uint8Array(b)].map((x) => x.toString(16).padStart(2, \"0\")).join(\"\");\n}\nasync function isAdmin(k: string) {\n return (await sha256Hex(k)) === (Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\") || KEY_SHA256);\n}\nasync function isViewer(k: string) {\n // v1.0.1 (review fix #4) — derived from the GHL token (a real secret held in env/private\n // blob), NOT from the admin digest that sits in this public source. Rotating the CRM token\n // rotates the view links; documented on Amir's list.\n const tok = await token();\n if (!tok) return false;\n return k === \"tds_view_\" + (await sha256Hex(tok + \":view\")).slice(0, 32);\n}\n\nasync function blobMod() { return (await import(\"https://esm.town/v/std/blob\")).blob; }\nasync function token(): Promise {\n const env = Deno.env.get(\"GHL_TOKEN\");\n if (env) return env;\n try { const blob = await blobMod(); return (await blob.getJSON(\"puppy_config\"))?.ghlToken; } catch { return undefined; }\n}\n\nasync function j(path: string, ver: string) {\n const tok = await token();\n const r = await fetch(`${GHL}${path}`, {\n headers: { Authorization: `Bearer ${tok}`, Version: ver, \"User-Agent\": \"curl/8.5.0\" },\n signal: AbortSignal.timeout(25_000),\n });\n if (!r.ok) throw new Error(`GHL ${path.split(\"?\")[0]} -> HTTP ${r.status}`);\n return r.json();\n}\n\n// Contacts newest-first, paginated until older than `floorMs` (bounded pages so a bad response\n// cannot loop forever). Failure THROWS, the section renders the error loudly, never a zero.\nasync function contactsSince(floorMs: number, errorsOut: string[]): Promise {\n const out: ContactLite[] = [];\n let startAfterId: string | undefined;\n let startAfter: number | undefined;\n let reachedFloor = false;\n for (let page = 0; page < 40; page++) {\n const q = new URLSearchParams({ locationId: LOC, limit: \"100\" });\n if (startAfterId && startAfter) { q.set(\"startAfterId\", startAfterId); q.set(\"startAfter\", String(startAfter)); }\n const d = await j(`/contacts/?${q}`, \"2021-07-28\");\n const cs = d?.contacts ?? [];\n if (!cs.length) break;\n for (const c of cs) out.push({ dateAdded: c.dateAdded, source: c.source ?? null, tags: c.tags ?? [] });\n const oldest = Date.parse(cs[cs.length - 1]?.dateAdded ?? \"\");\n const meta = d?.meta ?? {};\n startAfterId = meta.startAfterId; startAfter = meta.startAfter;\n if (Number.isFinite(oldest) && oldest < floorMs) { reachedFloor = true; break; }\n if (!startAfterId) { reachedFloor = true; break; }\n }\n if (!reachedFloor) errorsOut.push(\"Contact history hit the page cap before covering eight weeks; the oldest chart bars may undercount\");\n return out;\n}\n\nasync function eventsFor(calId: string, startMs: number, endMs: number): Promise {\n const d = await j(`/calendars/events?locationId=${LOC}&calendarId=${calId}&startTime=${startMs}&endTime=${endMs}`, \"2021-04-15\");\n return (d?.events ?? []).map((e: any) => ({\n startTime: typeof e.startTime === \"number\" ? e.startTime : Date.parse(e.startTime),\n appointmentStatus: e.appointmentStatus ?? e.appoinmentStatus ?? \"unknown\",\n calendarId: calId,\n }));\n}\n\n// v1.0.1 (review fix #1) — wins are counted by lastStageChangeAt but the search endpoint\n// sorts by createdAt, so a createdAt-floor walk silently drops long-cycle wins (an aged lead\n// created in June, won in August). Wins are a small population: scan them ALL via status=won,\n// no floor break. errorsOut collects a loud note if the page cap is ever hit (fix #8).\n// v1.0.2, PROVEN LIVE 4 Aug 2026: all 5,695 opportunities in this account carry status \"open\".\n// Nobody uses the won/lost flags, so a status=won scan returns zero forever and this report would\n// have printed \"0 closed deals\" every week for the rest of time. The real signal is the pipeline\n// STAGE (Customer / Won-Paid), which the engine's own exit rules already read. Also proven: every\n// such record has monetaryValue 0, so the CRM holds no deal values; the report counts PEOPLE\n// reaching Customer and says plainly that revenue is not recorded.\nconst STAGE_CUSTOMER = \"fd821b4e-bbe6-44de-b754-fa80e4823616\";\nconst STAGE_WON_PAID = \"ae173310-f8b1-4399-acb7-ef1fc03d3697\";\nasync function wonOppsAll(errorsOut: string[]): Promise {\n const out: OppLite[] = [];\n for (let page = 1; page <= 20; page++) {\n const d = await j(`/opportunities/search?location_id=${LOC}&limit=100&page=${page}`, \"2021-07-28\");\n const os = d?.opportunities ?? [];\n if (!os.length) break;\n for (const o of os) {\n if (o.pipelineStageId !== STAGE_CUSTOMER && o.pipelineStageId !== STAGE_WON_PAID) continue;\n out.push({ createdAt: o.createdAt, status: \"won\", monetaryValue: Number(o.monetaryValue) || 0, lastStageChangeAt: o.lastStageChangeAt ?? null });\n }\n if (page === 20 && os.length === 100) errorsOut.push(\"Customer list hit the page cap; totals may be partial\");\n }\n return out;\n}\n\n// Ad platforms, honest stubs. The day the tokens exist, these return numbers; until then null.\nasync function metaSpend(w: { startMs: number; endMs: number }, tzMin: number): Promise<{ spend: number; convs: number } | null> {\n const tok = Deno.env.get(\"META_TOKEN\"), act = Deno.env.get(\"META_AD_ACCOUNT\");\n if (!tok || !act) return null;\n // v1.0.1 (fixes #5, #9) — dates shifted into ET before slicing (UTC slice rolled the window\n // one day long); token in the Authorization header, never the URL; errors sanitized so a\n // network failure can never echo credentials into the page.\n const day = (ms: number) => new Date(ms + tzMin * 60_000).toISOString().slice(0, 10);\n const since = day(w.startMs), until = day(w.endMs - 86_400_000);\n let r: Response;\n try {\n r = await fetch(`https://graph.facebook.com/v21.0/${act}/insights?fields=spend,actions&time_range={\"since\":\"${since}\",\"until\":\"${until}\"}`, {\n headers: { Authorization: `Bearer ${tok}` }, signal: AbortSignal.timeout(20_000),\n });\n } catch { throw new Error(\"Meta API unreachable\"); }\n if (!r.ok) throw new Error(`Meta insights -> HTTP ${r.status}`);\n const d = await r.json();\n const row = d?.data?.[0];\n const convs = Number((row?.actions ?? []).find((a: any) => a.action_type === \"onsite_conversion.total_messaging_connection\" || a.action_type === \"lead\")?.value ?? 0);\n return { spend: Number(row?.spend ?? 0), convs };\n}\n\nconst esc = (s: unknown) => String(s ?? \"\").replace(/[&<>\"']/g, (c) => ({ \"&\": \"&\", \"<\": \"<\", \">\": \">\", '\"': \""\", \"'\": \"'\" }[c] as string));\nconst RAMP = [\"#86b6ef\", \"#3987e5\", \"#256abf\", \"#184f95\", \"#0f3a6e\"];\nconst GOOD = \"#0ca30c\", WARN = \"#fab219\", CRIT = \"#d03b3b\";\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n const k = url.searchParams.get(\"k\") || \"\";\n const admin = await isAdmin(k);\n const viewer = !admin && (await isViewer(k));\n if (!admin && !viewer) return new Response(\"Not found\", { status: 401 });\n\n const nowMs = Date.now();\n const tzMin = etOffsetMin(nowMs);\n const { current, previous } = reportWindows(nowMs, tzMin);\n const errors: string[] = [];\n const chartWeeks = 8;\n const floor = current.endMs - chartWeeks * 7 * 86_400_000;\n\n let contacts: ContactLite[] = [], ptEvents: EventLite[] = [], ftdEvents: EventLite[] = [], opps: OppLite[] = [];\n try { contacts = await contactsSince(floor, errors); } catch (e) { errors.push(`New inquiries could not be read: ${String(e).slice(0, 90)}`); }\n try { ptEvents = await eventsFor(PUP_TALK_CAL, previous.startMs, current.endMs); } catch (e) { errors.push(`Pup Talk calendar could not be read: ${String(e).slice(0, 90)}`); }\n try { for (const c of FTD_CALS) ftdEvents.push(...(await eventsFor(c, previous.startMs, current.endMs))); } catch (e) { errors.push(`Free Training Day calendars could not be read: ${String(e).slice(0, 90)}`); }\n try { opps = await wonOppsAll(errors); } catch (e) { errors.push(`Deals could not be read: ${String(e).slice(0, 90)}`); }\n\n let meta: { spend: number; convs: number } | null = null;\n let metaErr: string | null = null;\n try { meta = await metaSpend(current, tzMin); } catch (e) { metaErr = String(e).slice(0, 90); }\n\n const enq = countContacts(contacts, current), enqPrev = countContacts(contacts, previous);\n const pt = countEvents(ptEvents, current), ptPrev = countEvents(ptEvents, previous);\n const ftd = countEvents(ftdEvents, current);\n const won = wonOpps(opps, current), wonPrev = wonOpps(opps, previous);\n const sourcesAll = sourceBreakdown(contacts, current);\n const sources = sourcesAll.slice(0, 6);\n const buckets = weeklyBuckets(contacts, current.endMs, chartWeeks);\n const maxB = Math.max(1, ...buckets);\n\n // The follow-up system's own status, one honest line (stranger-test finding: the report was\n // silent about the thing the retainer is partly for).\n let engineLine = \"\";\n try {\n const blob2 = await blobMod();\n const st = (await blob2.getJSON(\"puppy_state\")) ?? {};\n const run = (await blob2.getJSON(\"puppy_run_state\")) ?? {};\n const rows: any[] = Object.values(st);\n const activeN = rows.filter((s: any) => [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"].includes(s?.status)).length;\n engineLine = run?.testMode === true\n ? `The automated follow-up system is in practice mode and contacting nobody yet. ${activeN === 1 ? \"One test contact is\" : activeN + \" test contacts are\"} running through the sequence to prove it works.`\n : run?.testMode === false\n ? `The automated follow-up system is LIVE with ${activeN} ${activeN === 1 ? \"person\" : \"people\"} in a sequence.`\n : \"\";\n } catch { engineLine = \"\"; }\n\n const unmarked = Math.max(0, pt.booked - pt.showed - pt.noshow);\n const commentary = draftCommentary({\n enq, enqPrev, ptBooked: pt.booked, ptPrev: ptPrev.booked, ptShowed: pt.showed,\n wonCount: won.count, wonValue: won.value, wonPrevValue: wonPrev.value,\n topSource: sources[0]?.source ?? null, adTracked: !!meta,\n });\n\n // snapshot: label by the window end date (the Friday). Load last week's for the look-back box.\n const weekKey = new Date(current.endMs).toISOString().slice(0, 10);\n const prevKey = new Date(previous.endMs).toISOString().slice(0, 10);\n const blob = await blobMod().catch(() => null);\n let prevSnap: any = null;\n let savedNote = \"\";\n if (blob) {\n prevSnap = await blob.getJSON(`friday_report_${prevKey}`).catch(() => null);\n const existing = await blob.getJSON(`friday_report_${weekKey}`).catch(() => null);\n const isFridayEt = new Date(nowMs + tzMin * 60_000).getUTCDay() === 5;\n const explicitSave = url.searchParams.get(\"save\") === \"1\";\n // v1.0.1 (fixes #2, #7) — never snapshot a week whose reads FAILED (zeros would be quoted\n // as truth forever); explicit save=1 may overwrite a bad snapshot; success claimed only\n // after the write actually resolved.\n if (admin && errors.length === 0 && (explicitSave || (isFridayEt && !existing))) {\n try {\n await blob.setJSON(`friday_report_${weekKey}`, {\n ts: new Date().toISOString(), weekKey,\n numbers: { enq, enqPrev, pt, ftd, won: won, sources },\n commentary,\n });\n savedNote = \"This week's snapshot was saved just now, next week's report will quote it.\";\n } catch { savedNote = \"Snapshot save FAILED, will retry on next view.\"; }\n } else if (admin && errors.length > 0 && (explicitSave || isFridayEt)) {\n savedNote = \"Snapshot NOT saved: some numbers could not be read (see below).\";\n } else if (existing) savedNote = \"Snapshot for this week already saved.\";\n }\n\n const fmtD = (ms: number) => new Date(ms + tzMin * 60_000).toISOString().slice(5, 10).replace(\"-\", \"/\");\n const tile = (label: string, v: string, note: string, accent?: string) =>\n `

${esc(v)}

${esc(label)}

${esc(note)}

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

${b}

${label}

`;\n }).join(\"\");\n\n const srcRows = sources.map((s) => `${esc(s.source)}${s.n}`).join(\"\") || `none this week`;\n\n const adCells = meta\n ? `${tile(\"Ad spend\", money(meta.spend), \"Meta, this week\")}${tile(\"Cost per inquiry\", enq ? money(meta.spend / enq) : \"n/a\", \"spend / inquiries\")}`\n : `${tile(\"Ad spend\", \"not tracked yet\", metaErr ? \"connection problem, see appendix\" : \"shows here once Amir links the ad account\", WARN)}`;\n\n const fbLanded = sourcesAll.filter((s) => /facebook|instagram|meta|messenger/.test(s.source)).reduce((a, s) => a + s.n, 0);\n const unsourced = sourcesAll.find((s) => s.source === \"no source recorded\")?.n ?? 0;\n const recon = meta\n ? `

Did the ad leads actually land?

Meta reports ${meta.convs} conversation${meta.convs === 1 ? \"\" : \"s\"} started this week. In the same window the CRM recorded ${fbLanded} contact${fbLanded === 1 ? \"\" : \"s\"} tagged Facebook/Instagram/Messenger and ${unsourced} with no source recorded. Messenger-created contacts usually arrive unsourced, so the honest comparison is ${meta.convs} claimed against ${fbLanded + unsourced} landed. The gap, if any, is leads that never became reachable contacts, the number worth watching.

`\n : `

Did the ad leads actually land?

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

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

Some numbers could not be read

${esc(e)}

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

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

What last week's report said

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

`\n : `

What last week's report said

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

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

The Dogs Spot, the week in numbers

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

\n\n

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

\n\n

What happened, in words DRAFT until Amir reviews

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

${esc(c)}

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

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

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

${esc(engineLine)}

` : \"\"}

\n\n

New inquiries, last eight weeks

${bars}

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

\n\n

Where this week's inquiries came from

\n${srcRows}

Source	People

\n\n

Why there is no revenue figure

Your deals do not carry a value in the CRM. Every opportunity sits at zero dollars and none are marked won or lost, so no honest revenue number can be produced from it. Counting people who reach the Customer stage is the closest true measure, and that is the tile above. Put a number on each deal and this report can show revenue instead.

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

Appendix, the fine print

This week's raw counts

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

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

How every number is computed

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

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

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

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

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

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

`)\n .join(\"\\n\");\n // Hidden preheader technique so the approved \"preview text\" shows in an inbox list without being\n // visible in the opened email — standard, low-risk, one line.\n const preheader = previewText\n ? `\\n`\n : \"\";\n return preheader + paragraphs;\n}\n\n",[207],"acb44c15-3b84-42e4-8bc6-52df8ab6fdaf","registry-diff.ts","a96cde42-908b-11f1-96ea-1607ee4eb77e",172,["D",1785906494226],"// WHAT CHANGED IN A LIST SOMEBODY ELSE CONTROLS. v1.0, 5 August 2026.\n//\n// The watchdog watches two registries in Kim's CRM that nobody on this project owns: her 165\n// automations, and the eight knowledge bases Chloe answers customers from. Both can be edited by\n// Kim, by Kristian, or by an integration nobody remembers installing, and until v1.6 the knowledge\n// bases were not watched at all. The consolidated one was edited at 02:38 on 5 August and nothing\n// noticed.\n//\n// This is the comparison, on its own, so it can be tested. It lived inline in the watchdog before,\n// where it could only ever be checked by waiting for somebody to change something — which means a\n// check nobody has ever seen go off. Same rule as everywhere else in this project: a check that\n// cannot be shown to fail is not a check.\n//\n// It deliberately knows nothing about workflows or knowledge bases. It takes two maps of\n// id -> description and says what moved.\n\nexport type Registry = Record;\n\nexport type RegistryChange = {\n added: string[];\n removed: string[];\n edited: string[]; // \"old -> new\", so a reader can see what moved without opening anything\n changed: boolean;\n};\n\nexport function registryDiff(prev: Registry | null | undefined, now: Registry | null | undefined): RegistryChange {\n const a = prev && typeof prev === \"object\" ? prev : {};\n const b = now && typeof now === \"object\" ? now : {};\n const prevIds = Object.keys(a);\n const nowIds = Object.keys(b);\n const added = nowIds.filter((i) => !(i in a)).map((i) => b[i]);\n const removed = prevIds.filter((i) => !(i in b)).map((i) => a[i]);\n const edited = nowIds.filter((i) => i in a && a[i] !== b[i]).map((i) => `${a[i]} -> ${b[i]}`);\n return { added, removed, edited, changed: added.length + removed.length + edited.length > 0 };\n}\n\n/**\n * Is this an empty response we should DISTRUST rather than act on?\n *\n * A malformed-but-200 reply that returns an empty list must never overwrite a good baseline, or\n * the next pass fires \"everything was removed\" and the one after that fires \"everything was\n * added\". The watchdog learned this on the workflow registry; the knowledge-base watch inherits it\n * rather than rediscovering it.\n */\nexport function looksLikeAGlitch(nowCount: number, prevCount: number | null | undefined): boolean {\n return nowCount === 0 && (prevCount ?? 0) > 0;\n}\n\n/** The sentence, generated from the change, never written alongside it. */\nexport function registrySentence(c: RegistryChange, what: string): string {\n if (!c.changed) return `Nothing has moved in ${what} since the last look.`;\n const bits: string[] = [];\n if (c.edited.length) bits.push(`Edited: ${c.edited.slice(0, 3).join(\"; \")}.`);\n if (c.added.length) bits.push(`Added: ${c.added.slice(0, 3).join(\"; \")}.`);\n if (c.removed.length) bits.push(`Removed: ${c.removed.slice(0, 3).join(\"; \")}.`);\n const more = c.added.length + c.removed.length + c.edited.length - Math.min(3, c.edited.length) - Math.min(3, c.added.length) - Math.min(3, c.removed.length);\n if (more > 0) bits.push(`${more} more not listed here.`);\n return bits.join(\" \");\n}\n",[214],"3d5538c0-5841-4f98-af81-98e09e3b5887","puppy-messages.ts","cd4b87b0-8c34-11f1-b87e-1607ee4eb77e",99,["D",1785871894236],4,"// PUPPY PATH — message copy module (split from the engine for val.town's 80k/file limit).\n// Copy is VERBATIM from PHASE1-PUPPY-PATH-WRITING-SHEET.md §3 — do not paraphrase here, ever.\ndeclare const Deno: { env: { get(key: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\n\n// ---- v1.3 change, 2 Aug 2026 — booking URL. RETRACTION APPENDED, read the whole block ----------\n// The previous value was:\n// https://api.leadconnectorhq.com/widget/bookings/pbe-discovery-9edbddc3-4b5a-406e-9bc3-7f10cb0d3221\n//\n// WHAT I ORIGINALLY WROTE HERE (and it was wrong): that this id \"does NOT belong to this location\"\n// and was the parent agency's own discovery-call widget.\n//\n// RETRACTED, same day, on better evidence. Re-checking GET /calendars/?locationId=BQHJ19uohldYe3eqA0bl\n// field by field shows `pbe-discovery-9edbddc3-4b5a-406e-9bc3-7f10cb0d3221` is the *widget slug of\n// Kim's own \"Pup Talk Phone Call\" calendar* — the same calendar as qHuYJ0NEqzibnoqf5Cw3. Confirmed\n// independently: https://book.thedogsspotga.com/phone (the page the website's own \"Book your Free\n// Pup Talk\" button leads to) contains BOTH strings. /widget/bookings/ and\n// /widget/booking/ are two URL forms for one object; both return 200 and both land on\n// her calendar. The original link was never broken. I inferred \"not hers\" from the \"pbe\" prefix —\n// which is Pet Biz Experts, the agency that set the account up and therefore named the slug — and\n// stated the inference as a verified finding. That is the error, and it is the kind that matters\n// more than the code change.\n//\n// The current value is kept anyway, for one real reason that survives the retraction: the engine\n// watches PUP_TALK_CALENDAR_ID (qHuYJ0NEqzibnoqf5Cw3) to detect a booking, so using the calendar-id\n// form makes the link a lead clicks and the object the engine watches literally the same string,\n// with no slug indirection to go stale. Secondary: the word \"discovery\" does not appear in it, and\n// Kim asked for \"Pup Talk\" instead.\n//\n// Regression test A1 asserts `!includes(\"pbe-\")`. That assertion is now a style rule, not a\n// correctness rule. Left in place; the comment above is the correction of record.\nexport const REAL_BOOKING_URL =\n \"https://api.leadconnectorhq.com/widget/booking/qHuYJ0NEqzibnoqf5Cw3\";\nexport const SHORT_BOOKING_LINK = Deno.env.get(\"SHORT_BOOKING_LINK\") || REAL_BOOKING_URL;\n\n// Phone number: two live candidates, and the earlier note here (\"zero signals point to 912-823-4382\")\n// is CORRECTED as of 2 Aug 2026. Signals for 912-823-4382 turned out to be strong: it is the meeting\n// location on 73 of 193 Pup Talk appointments, it is the number in the default confirmation text of\n// BOTH booking widgets (\"please call our office at (912) 823-4382\"), and thedogsspotga.com/about-5\n// tells customers to ring it to schedule a training drop-off.\n// Still using 912-348-8726, on a narrower and now-honest basis: it is the number in the website\n// footer on every page and behind the home page \"Call Us\" button, so it is the number a lead who\n// found the site already has. Both are real. Kim must pick one before go-live — flagged on the todo\n// list, not decided quietly.\nexport const PHONE_DISPLAY = Deno.env.get(\"PHONE_DISPLAY\") || \"912-348-8726\";\n\nexport type Channel = \"email\" | \"sms\";\n\nexport type MessageTemplate = {\n id: string;\n channel: Channel;\n offsetHours: number;\n subject?: string; // email only\n previewText?: string; // email only\n bodyTemplate: string;\n};\n\n// ---- message copy (PHASE1-PUPPY-PATH-WRITING-SHEET.md §3, VERBATIM — do not paraphrase) ----------\n// {{FIRST_NAME}} is the ONLY per-contact merge token, resolved at render time by\n// v2.0, 4 Aug 2026. {{DOG_NAME}} was removed from every message in this file and in the taper,\n// on Kim's instruction: \"we haven't always got the name and so if we have a placeholder for the\n// puppies name, it reads weird when there's no puppy in there so I think we should go with having\n// the person's name, but not necessarily the puppies name\". Facebook leads, which are four in\n// five of all inquiries, frequently arrive with no dog name at all. Every sentence that used it\n// was REWRITTEN to read naturally without one, rather than having \"your puppy\" substituted in\n// mechanically, because the mechanical version is exactly what she was objecting to.\n// Also on her instruction, same message: toilet -> potty, garden -> yard, and DAYCARE REMOVED\n// ENTIRELY. They do not offer daycare. That is the same class of error as describing grooming as\n// a service, and it had been sitting in four messages.\n// The old comment, for the record:\n// applyMergeFields(). [phone] / [link] are fixed placeholders per the writing sheet's own §1\n// distinction (Title Case = merge field, lower case = placeholder) — resolved ONCE below via real\n// template-literal interpolation of PHONE_DISPLAY / SHORT_BOOKING_LINK, not per contact.\n// **bold** markdown in messages 3/5/6 is rendered to by bodyToHtml() — that is a formatting\n// transform, not a wording change; the words themselves are untouched.\n\nexport const MAIN_SEQUENCE: MessageTemplate[] = [\n {\n id: \"main-1\",\n channel: \"email\",\n offsetHours: 0,\n subject: \"Getting your puppy off to a good start\",\n previewText: \"A few things that matter more than people expect in these first weeks.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThanks for getting in touch.\n\nWhether you're bringing a puppy home soon, or yours is already running circles around the kitchen, the timing of what happens next matters more than people expect.\n\nA puppy's window for learning that new people, new dogs, new places and new sounds are all safe starts closing earlier than most owners realize - a lot of that learning is done by around four to five months old. Whatever they meet calmly now tends to stay easy for life. Whatever gets missed is harder to fix later. Not impossible, just harder, and it usually takes longer than it would have the first time round.\n\nOver the next few weeks I'll send you a handful of short, practical emails - biting, potty training, recall, that sort of thing. Real advice, not fluff.\n\nIf you'd rather just talk it through now, that's what a Pup Talk is for - a real conversation with our team about how things are going, 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 - welcome. I'll send a few honest, useful puppy emails over the next few weeks. Reply anytime, a real person reads these.`,\n },\n {\n id: \"main-3\",\n channel: \"email\",\n offsetHours: 72, // day 3\n subject: \"Puppy biting: normal, not naughty\",\n previewText: \"What's actually going on when a puppy won't stop mouthing, and what helps.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nIf your puppy has started biting at hands, sleeves, ankles, shoelaces - that's not a behavior problem. It's normal. Puppies explore the world with their mouths the way toddlers explore it with their hands, and it usually gets worse before it gets better, especially once teething starts.\n\nA few things that actually help:\n\n**Redirect, don't just say no.** Keep a toy or a chew within arm's reach of wherever you usually sit, so it's already in your hand before the mouthing starts rather than after. The moment teeth touch skin, swap your hand for the toy. Saying \"no\" tells them to stop; it doesn't tell them what to do instead, and a puppy who is told to stop with nothing to switch to just tries again.\n\n**Watch for the overtired witching hour.** A lot of biting spikes happen when a puppy is overstimulated or short on sleep, not when they're being difficult. A nap often does more than any correction.\n\n**Yelp, don't wrestle.** If it hurts, a short \"ow\" and a pause in play teaches bite inhibition better than pulling your hand away, which can turn into a game.\n\nIt gets better. Most of this settles down significantly by six months, and properly once the adult teeth are in. It feels endless at week two. It isn't.\n\nIf any of that doesn't match what you're seeing, reply and tell me - I read these.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"main-4\",\n channel: \"sms\",\n offsetHours: 144, // day 6\n bodyTemplate: `Hi {{FIRST_NAME}}, Kim here. Quick one - how's the biting and potty training going? Totally normal stage either way. Reply and let me know, happy to help.`,\n },\n {\n id: \"main-5\",\n channel: \"email\",\n offsetHours: 216, // day 9\n subject: \"A realistic potty-training timeline\",\n previewText: \"What actually helps, and why one accident isn't a setback.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nPotty training questions are the ones I get asked about most, usually some version of \"is this normal?\" Almost always, yes.\n\nA young puppy's bladder is small and their control over it is genuinely limited - not a matter of trying harder. As a rough guide, a lot of trainers use \"roughly one hour of control for every month of age\" early on, which is why an eight- or ten-week-old puppy needs to go out far more often than seems reasonable.\n\nWhat tends to work:\n\n**A schedule, not a hope.** Out first thing, after every meal, after every nap, after play, and last thing at night - before you think they need it, not after.\n\n**Same spot, same word.** Consistency does more work than any product. Pick a spot, use a calm word or phrase every time, and reward the second they finish outside, not back indoors where the reward disconnects from the act.\n\n**Supervise or contain.** Accidents mostly happen when a puppy has quiet, unsupervised access to another room. A crate, a pen, or simply keeping them in sight closes that gap.\n\n**No telling off for accidents.** By the time you've found it, they have moved on. Telling them off teaches confusion, not house manners.\n\nMost puppies are largely reliable by four to six months, and fully reliable somewhat later. If yours is well past that and still having accidents daily, that's worth looking at properly rather than pushing through - reply and tell me what's happening.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"main-6\",\n channel: \"email\",\n offsetHours: 312, // day 13\n subject: \"Recall is a habit, not a hope\",\n previewText: `Why \"come\" is worth starting now, even before it matters.`,\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nRecall - getting your puppy to come back reliably - is the one piece of training that keeps a dog safe for the rest of their life. It's also the easiest one to start too late.\n\nThe mistake most people make isn't training it wrong. It's not starting until it's needed - at the park, off lead, with distractions already in the way. By then you're teaching recall and competing for attention at the same time.\n\nStarted early, it's simple:\n\n**Practice where nothing's competing for attention.** Hallway, living room, yard. Say the word once, and make coming back to you the best thing that happens all day - food, praise, a game, whatever they actually want.\n\n**Never call for something unpleasant.** If \"come\" ever means bath time, nail clipping, or the end of a walk, it stops meaning \"good things happen.\" Go get them for that instead.\n\n**Reward every single time, at first.** Not just the good ones. Recall is a habit you're building, not a trick you're testing.\n\nRecall is the one people most often ask me to look at, usually because it worked in the yard and then stopped working everywhere else. If you'd like a hand with it, a Pup Talk is a free twenty-minute call and there's no pitch in it: ${SHORT_BOOKING_LINK}, or call or text ${PHONE_DISPLAY}.\n\nKim\nThe Dogs Spot`,\n },\n {\n id: \"main-7\",\n channel: \"sms\",\n offsetHours: 408, // day 17\n bodyTemplate: `Hi {{FIRST_NAME}}, no pressure at all - if you'd like to talk through training or boarding for your puppy, we're easy to reach. Call or text ${PHONE_DISPLAY}, or book a time here: ${SHORT_BOOKING_LINK}. Kim, The Dogs Spot`,\n },\n {\n id: \"main-8\",\n channel: \"email\",\n offsetHours: 504, // day 21\n subject: \"The last puppy email from me for now\",\n previewText: \"What matters most from the last three weeks, and an open door.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nThis is the last of the every-few-days emails, so a quick summary of everything I've sent: get your puppy meeting the world calmly while that window's open, expect the biting and treat it as normal, keep the potty-training schedule boring and consistent, and start recall before you need it, not after.\n\nNone of that is complicated. Most of it is just easy to talk yourself out of doing consistently when you're tired and there's a puddle on the floor again.\n\nFrom here I'll slow right down - a short note each week for a few weeks, then less and less, only ever the useful kind, and never a sales pitch. If you'd like to talk any of this through properly - what's normal for your puppy specifically, what training or boarding would actually suit your week, what it costs and when it makes sense to start - that's what a Pup Talk is for. It's a conversation, 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 schedule it.`,\n },\n {\n id: \"branch_a-2\",\n channel: \"email\",\n offsetHours: 24, // day +1\n subject: \"Let's find another time\",\n previewText: \"Fifteen minutes, whenever actually suits.\",\n bodyTemplate: `Hi {{FIRST_NAME}},\n\nI noticed we had a Pup Talk scheduled, but we missed each other. No worries at all, I know life gets busy.\n\nIt's a quick, no-pressure call where we'll talk about what's been going on, answer any questions you have, and see whether training with us would be a good fit. And if we're not the right fit, I'll tell you that too.\n\nJust reply with a couple of times that work for you, call or text me at ${PHONE_DISPLAY}, or book a time that's convenient here: ${SHORT_BOOKING_LINK}.\n\nIf I don't hear back, I'll assume now just isn't the right time and won't keep bugging you. Whenever you're ready, just reach out, I'd be happy to help.\n\nKim\nThe Dogs Spot`,\n },\n];\n\nexport const BRANCH_B: MessageTemplate[] = [\n {\n id: \"branch_b-1\",\n channel: \"email\",\n offsetHours: 24, // day +1 after the call\n subject: \"Good talking with you\",\n previewText: \"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, even outside of anything you decide to book.\n\nIf it's not the right time for training or boarding with us, that's completely fine. A lot of people need more than one conversation before it's the right moment, and that's how it should work - nobody should sign up on a call because it felt awkward not to.\n\nIf anything changes, or a question comes up later that we didn't cover, reply here or call or text ${PHONE_DISPLAY}. 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 you're both getting on. If a question's come up since we spoke, reply here anytime. No pressure either way.`,\n },\n];\n\n",[221],"06c38757-da91-45a9-bc23-8a9b0ecafb86","puppy-detect.ts","299fd626-9089-11f1-805a-1607ee4eb77e",164,["D",1785905947813],2,"// WHO IS A PUPPY INQUIRY. v1.0, 5 August 2026.\n//\n// WHY THIS FILE EXISTS. The engine enrolls people carrying the tag `nurture - puppy`. Nothing in\n// Kim's account applies that tag: all 5,544 contacts checked, zero carry it. So go-live is three\n// switches, not two, and this is the third.\n//\n// WHY IT IS NOT A ONE-LINE REGEX. The first thing I tried was matching \"puppy\" or an age in weeks\n// or months against the inquiry summary. Over the 800 most recent contacts it returned 29 people,\n// and reading them showed it was wrong about several in ways that matter:\n//\n// * \"Ken Anderson was looking to purchase a puppy. He inquired whether The Dog's Spot GA offered\n// puppies for sale. The agent clarified that they do not sell.\" He would have received\n// forty-one messages about training a puppy he does not own.\n// * \"Charlie, who is 3 years and 4 months old\" matched on \"4 months old\". The dog is three.\n// * \"Evelyn Carter was seeking good homes for her older dogs\" matched on the word \"new puppy\"\n// later in a sentence about rehoming.\n//\n// A false positive here is not a bad row in a spreadsheet. It is a real person getting nineteen\n// months of messages about a puppy they do not have, in Kim's name.\n//\n// SO THIS FILE NEVER APPLIES A TAG. It classifies, it explains itself in one sentence per person,\n// and it hands the list to a human. `confidence` is the whole point: \"clear\" is defensible on its\n// own, \"probable\" wants a glance, \"unclear\" is a question rather than an answer.\n//\n// It also reports its own blind spot, loudly: the inquiry summary is populated on about half of\n// contacts. Anyone with no summary cannot be classified by this at all, and saying so is part of\n// the output rather than a footnote.\n\nexport type Verdict = {\n contactId: string;\n name: string;\n confidence: \"clear\" | \"probable\" | \"unclear\" | \"no\";\n /** One sentence, in plain English, naming the words that decided it. */\n reason: string;\n /** Months, when a dog's age could be read. null when it could not. */\n ageMonths: number | null;\n matched: string[];\n};\n\nexport type DetectSummary = {\n scanned: number;\n withText: number;\n noText: number;\n clear: number;\n probable: number;\n unclear: number;\n no: number;\n};\n\nconst num = (s: string): number | null => {\n const words: Record = {\n one: 1, two: 2, three: 3, four: 4, five: 5, six: 6, seven: 7, eight: 8,\n nine: 9, ten: 10, eleven: 11, twelve: 12, eighteen: 18,\n };\n const t = s.trim().toLowerCase();\n if (/^\\d+(\\.\\d+)?$/.test(t)) return Number(t);\n return words[t] ?? null;\n};\n\n/**\n * The dog's age in months, or null.\n *\n * The \"3 years and 4 months old\" trap is handled by looking for a YEARS reading first and letting\n * it win. A dog described in years is not a puppy however many months are mentioned afterwards.\n */\nexport function ageInMonths(text: string): number | null {\n const t = text.toLowerCase();\n // YEARS FIRST, AND THEY WIN OUTRIGHT.\n // [was: the years pattern required the word \"old\" straight after it, as in \"3-year-old\". So\n // \"Charlie, who is 3 years and 4 months old\" did not match it — the \"old\" belongs to the\n // months — and fell through to the months branch, which read the dog as 4 months. That is\n // the exact false positive this whole file exists to prevent, and the first version of the\n // file still had it. Caught by its own test, not by reading it.]\n const y = t.match(/(\\d+(?:\\.\\d+)?|one|two|three|four|five|six|seven|eight|nine|ten|eleven|twelve)[\\s-]*(?:year|yr)s?\\b/);\n if (y) {\n const n = num(y[1]);\n if (n != null) {\n const m = t.slice(y.index ?? 0).match(/(?:year|yr)s?[\\s,-]*(?:and\\s*)?(\\d+|one|two|three|four|five|six|seven|eight|nine|ten|eleven)[\\s-]*(?:month|mo)s?\\b/);\n return n * 12 + (m ? (num(m[1]) ?? 0) : 0);\n }\n }\n const mo = t.match(/(\\d+(?:\\.\\d+)?|one|two|three|four|five|six|seven|eight|nine|ten|eleven|twelve|eighteen)(?:\\s*-\\s*\\d+)?[\\s-]*(?:month|mo)s?[\\s-]*old/);\n if (mo) { const n = num(mo[1]); if (n != null) return n; }\n const wk = t.match(/(\\d+(?:\\.\\d+)?|one|two|three|four|five|six|seven|eight|nine|ten|eleven|twelve)(?:\\s*-\\s*\\d+)?[\\s-]*(?:week|wk)s?[\\s-]*old/);\n if (wk) { const n = num(wk[1]); if (n != null) return Math.round((n / 4.345) * 10) / 10; }\n return null;\n}\n\n// Reasons someone is NOT a puppy-training inquiry even though the word appears. Each one is here\n// because a real contact in Kim's account tripped it.\nconst DISQUALIFIERS: Array<[RegExp, string]> = [\n [/\\b(purchase|buy|buying|sell|selling|for sale|breeder|adopt(?:ing)? a)\\b[^.]{0,40}\\bpupp/i,\n \"they were asking to buy a puppy, not to train one\"],\n [/\\bpupp\\w*\\b[^.]{0,40}\\b(for sale|to sell|available to buy)\\b/i,\n \"they were asking to buy a puppy, not to train one\"],\n [/\\b(rehome|rehoming|good homes|find(?:ing)? homes|surrender|give away)\\b/i,\n \"they were rehoming dogs rather than asking about training\"],\n [/\\b(do not sell|don't sell|does not sell|doesn't sell)\\b/i,\n \"the reply on file says Kim does not sell dogs, so this was not a training inquiry\"],\n];\n\nconst PUPPY_WORDS = /\\b(pupp(?:y|ies)|new pup\\b|pup\\b)/i;\n// Kim's puppy sequence is written for a young dog. Past about a year it is the wrong sequence.\nconst PUPPY_MAX_MONTHS = 12;\n\n/** Age in the words a person would use. Nobody says a dog is 1.4 months old. */\nexport function sayAge(months: number): string {\n if (months < 2) { const w = Math.round(months * 4.345); return `${w} week${w === 1 ? \"\" : \"s\"} old`; }\n if (months < 24) { const m = Math.round(months); return `${m} month${m === 1 ? \"\" : \"s\"} old`; }\n const y = Math.round(months / 12);\n return `${y} year${y === 1 ? \"\" : \"s\"} old`;\n}\n\nexport function classify(contactId: string, name: string, text: string): Verdict {\n const clean = (text ?? \"\").replace(/\\s+/g, \" \").trim();\n if (!clean) {\n return { contactId, name, confidence: \"unclear\", ageMonths: null, matched: [],\n reason: \"There is nothing written down about what they asked for, so this cannot be decided from the record.\" };\n }\n\n for (const [re, why] of DISQUALIFIERS) {\n const m = clean.match(re);\n if (m) return { contactId, name, confidence: \"no\", ageMonths: ageInMonths(clean), matched: [m[0].slice(0, 60)], reason: `Not a puppy inquiry: ${why}.` };\n }\n\n const age = ageInMonths(clean);\n const saysPuppy = PUPPY_WORDS.test(clean);\n const matched: string[] = [];\n if (saysPuppy) matched.push((clean.match(PUPPY_WORDS) ?? [\"\"])[0]);\n if (age != null) matched.push(`${age} months old`);\n\n if (age != null && age > PUPPY_MAX_MONTHS) {\n return { contactId, name, confidence: \"no\", ageMonths: age, matched,\n reason: `Not a puppy inquiry: the dog is given as ${sayAge(age)}, which is past the sequence.` };\n }\n if (age != null && saysPuppy) {\n return { contactId, name, confidence: \"clear\", ageMonths: age, matched,\n reason: `Called a puppy and given as ${sayAge(age)}, so both signals agree.` };\n }\n // A very young age settles it on its own. No adult dog is four months old, so the word \"puppy\"\n // adds nothing at this end and demanding it would push obvious cases down to \"probable\".\n if (age != null && age <= 6) {\n return { contactId, name, confidence: \"clear\", ageMonths: age, matched,\n reason: `The dog is given as ${sayAge(age)}, which is a puppy whatever words they used.` };\n }\n if (age != null) {\n return { contactId, name, confidence: \"probable\", ageMonths: age, matched,\n reason: `The dog is given as ${sayAge(age)}, which is inside the sequence, but the word puppy is not used.` };\n }\n if (saysPuppy) {\n return { contactId, name, confidence: \"probable\", ageMonths: null, matched,\n reason: \"They call it a puppy, but no age is written down, so how young is a guess.\" };\n }\n return { contactId, name, confidence: \"no\", ageMonths: null, matched: [],\n reason: \"Nothing in what they wrote points at a puppy.\" };\n}\n\nexport function summarise(vs: Verdict[], scanned: number): DetectSummary {\n const by = (c: Verdict[\"confidence\"]) => vs.filter((v) => v.confidence === c).length;\n const noText = vs.filter((v) => v.matched.length === 0 && v.confidence === \"unclear\").length;\n return { scanned, withText: scanned - noText, noText, clear: by(\"clear\"), probable: by(\"probable\"),\n unclear: by(\"unclear\"), no: by(\"no\") };\n}\n\n/**\n * How old is this reading, in words, or null when it is fresh enough not to mention.\n *\n * A dry pass that stopped running would otherwise keep showing its last numbers as though they\n * were this morning's. The engine runs about hourly, so anything past six hours has missed\n * several turns and is worth saying out loud.\n */\nexport function scanAgeNote(atIso: string | null | undefined, nowMs: number): string | null {\n if (!atIso) return null;\n const ms = nowMs - Date.parse(atIso);\n if (!Number.isFinite(ms) || ms < 0) return null;\n const hours = ms / 3_600_000;\n if (hours < 6) return null;\n if (hours < 48) return `This count was last taken about ${Math.round(hours)} hours ago rather than just now, so treat it as a little out of date.`;\n return `This count was last taken about ${Math.round(hours / 24)} days ago, so it has stopped being kept up and the numbers below are old.`;\n}\n\n/** The sentence for the summary, generated from the counts, never written alongside them. */\nexport function detectSentence(s: DetectSummary | null): string {\n if (!s || !s.scanned) return \"No contacts were read, so there is nothing to report here rather than a zero to trust.\";\n const parts = [\n `${s.scanned.toLocaleString(\"en-US\")} contacts were read. ${s.clear} are clearly a puppy inquiry and ${s.probable} probably are.`,\n ];\n if (s.noText) {\n parts.push(`${s.noText} of them have nothing written down about what they asked for, so they cannot be judged from the record at all, either way.`);\n }\n parts.push(\"Nothing has been tagged. This is a list to look at, not an action taken.\");\n return parts.join(\" \");\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE DRY PASS.\n//\n// This file has NO WAY TO APPLY A TAG and that is structural, not a promise: there is no fetch, no\n// POST and no client in it. Everything here takes contacts in and hands verdicts out. The engine\n// calls it on each run, writes the counts down, and applies nothing. When the tagging is finally\n// armed it will be armed somewhere a human had to go and change, not here.\n//\n// The custom-field ids are Kim's account's. `inquiryText` is deliberately forgiving about the\n// shape of a contact, because it is fed straight from the CRM's JSON.\n// ---------------------------------------------------------------------------------------------\nexport const FIELD_INQUIRY_SUMMARY = \"N8Mw4Mmz5ecesIOrQMWm\";\nexport const FIELD_TRAINING_GOAL = \"4EXdybS2XUAaP6tnlncI\";\n\nexport function inquiryText(contact: unknown): string {\n const cfs = (contact as any)?.customFields;\n if (!Array.isArray(cfs)) return \"\";\n const pick = (id: string) => {\n const f = cfs.find((x: any) => x?.id === id);\n const v = f?.value;\n return typeof v === \"string\" || typeof v === \"number\" ? String(v) : \"\";\n };\n return `${pick(FIELD_INQUIRY_SUMMARY)} ${pick(FIELD_TRAINING_GOAL)}`.trim();\n}\n\nexport function classifyContacts(contacts: unknown): Verdict[] {\n if (!Array.isArray(contacts)) return [];\n return contacts\n .filter((c: any) => c && typeof c.id === \"string\")\n .map((c: any) => classify(c.id, String(c.contactName ?? c.firstName ?? \"(no name)\"), inquiryText(c)));\n}\n\nexport type DryScan = {\n at: string;\n summary: DetectSummary;\n /** Ids only, and only the ones worth a human's time. Never names, never message text. */\n clearIds: string[];\n probableIds: string[];\n /** Always false in this file. Present so the panel can state it rather than assume it. */\n applied: false;\n};\n\nexport function dryScan(contacts: unknown, at: string): DryScan {\n const vs = classifyContacts(contacts);\n return {\n at,\n summary: summarise(vs, vs.length),\n clearIds: vs.filter((v) => v.confidence === \"clear\").map((v) => v.contactId),\n probableIds: vs.filter((v) => v.confidence === \"probable\").map((v) => v.contactId),\n applied: false,\n };\n}\n",[229],"45dd7fb4-4470-47ce-90d9-5b801f8704d0","paths.ts","243d2a8e-8e78-11f1-bbbc-1607ee4eb77e",118,["D",1785876026154],5,"// PATH REGISTRY, the six nurture paths as data, plus the validator that guards them. 2 Aug 2026.\n//\n// WHY\n// The engine was written for one path. Generalising it by rewriting the state machine on a live\n// client system is the kind of refactor that breaks something nobody notices for a week. The\n// cheaper and safer generalisation is to move the *definition* of a path out of code: a path is a\n// tag, a sequence of steps, and a set of exit rules. The engine already treats steps as data\n// (renderStep takes a template); this file makes the whole path a record.\n//\n// RETRACTED, 2 Aug 2026, and the RENDERED SENTENCE corrected 4 Aug: the retraction sat in this\n// comment for two days while the page below carried on printing the claim it retracts. A comment\n// is not a correction. This file used to claim registering paths 2-6 was \"a copy drop, not an\n// engineering job\". That was wrong and it was repeated to the client. The engine does not read this\n// file: puppy_path_v1.1.ts imports MAIN_SEQUENCE/BRANCH_A/BRANCH_B directly from puppy-messages.ts,\n// hardcodes TAG_SOURCE_SIGNAL, and stores Record, one position per contact,\n// not one per path. Dropping steps into a row below would render a green line on this page and send\n// nothing. Path 2 needs the state model, per-path tag mapping, sequence selection and precedence\n// rules built. Days, not an afternoon. This page is a registry and a validator; it is not wiring.\n//\n// THE VALIDATOR IS THE POINT\n// Every path, before it can be registered, has to survive the same checks the test suite runs\n// against the puppy path: no banned wording, no unresolved merge token, SMS inside carrier limits,\n// at least one opt-out line, a booking link that points at a calendar this account actually owns,\n// monotonic timing, and a defined terminal step. A path that fails is refused with reasons rather\n// than half-registered.\n//\n// ?k= the registry: what is defined, what is live, what is missing\n// ?k=&validate=1 run the validator over everything registered\n// ?k=&f=json the same as JSON\n\n// ---- auth ------------------------------------------------------------------------------------\n// v2 (2 Aug, after the adversarial pass): the key is NOT in this file. val.town vals are PUBLIC -\n// proved by fetching this very source with no token, so a literal key here was readable by anyone\n// who found the val, which meant anyone could read Kim's data, stop her system, or trigger a run.\n// Only the SHA-256 digest lives in source now. The digest is useless to a reader and sufficient for\n// a comparison, so publishing the code no longer publishes the secret.\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\n\nasync function sha256Hex(s: string): Promise {\n const b = await crypto.subtle.digest(\"SHA-256\", new TextEncoder().encode(s));\n return [...new Uint8Array(b)].map((x) => x.toString(16).padStart(2, \"0\")).join(\"\");\n}\n\nasync function authorised(k: string): Promise {\n const override = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\");\n const expected = override || KEY_SHA256;\n const got = await sha256Hex(k);\n // Constant-time over equal-length hex digests.\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\n\n// The one calendar this account owns for training consults. Verified live 2 Aug against\n// GET /calendars/?locationId=, \"Pup Talk Phone Call\". Any booking link in any path must contain it.\nconst OWNED_BOOKING_ID = \"qHuYJ0NEqzibnoqf5Cw3\";\nconst OWNED_BOARDING_FORM = \"thedogsspotga.com/boarding-booking-form\";\n\nexport type Step = {\n id: string;\n channel: \"email\" | \"sms\";\n offsetHours: number;\n subject?: string;\n previewText?: string;\n bodyTemplate: string;\n};\n\nexport type PathDef = {\n key: string;\n label: string;\n sourceTag: string; // applying this tag in the CRM is how a human enrols someone\n enrolledTag: string; // minted by the engine on enrolment\n source: \"engine\" | \"ghl\" | \"off\"; // mutual exclusion: never let a val and a GHL workflow both own a path\n channelsAtLaunch: (\"email\" | \"sms\")[];\n steps: Step[];\n notes: string;\n // v1.5, 2 Aug 2026, THE COLLISION MAP, and the most important field in this file.\n // `source` was always a DECLARATION of who owns a path. It was never checked against what the CRM\n // is actually running. Checked properly today via GET /workflows/?locationId= : the location has\n // 165 workflows, 95 of them PUBLISHED, and every one of the six paths below already has published\n // GoHighLevel automation whose name overlaps it. Declaring `source: \"engine\"` does not switch those\n // off. GoHighLevel exposes no endpoint for reading a contact's workflow enrolments\n // (/contacts/{id}/workflow -> 404) so overlap cannot be detected per contact, only per path, by a\n // human reading each workflow. Until a row here is cleared, treat it as live competition for the\n // same customer's inbox. The engine's R27 quiet-period guard is the runtime backstop; this list is\n // the thing that stops us needing it.\n ghlOverlap: { name: string; status: \"published\" | \"draft\"; version: number }[];\n};\n\n// ---- the registry ---------------------------------------------------------------------------------\n// PUPPY is populated from the deployed module so there is exactly one copy of that copy. The other\n// five are declared with everything except their steps: the tag names, the launch channels and the\n// constraints are all decided, so registering them is `steps: [...]` and nothing else.\n\nimport { MAIN_SEQUENCE, BRANCH_A, BRANCH_B } from \"./puppy-messages.ts\";\n\nexport const PATHS: PathDef[] = [\n {\n key: \"puppy\", label: \"Puppy owners\", sourceTag: \"nurture - puppy\", enrolledTag: \"puppy-path-v1\",\n source: \"engine\", channelsAtLaunch: [\"email\", \"sms\"],\n steps: [...MAIN_SEQUENCE, ...BRANCH_A, ...BRANCH_B] as Step[],\n notes: \"Live in the engine. 8 main + 2 no-show + 2 didn't-buy. The template for the other five.\",\n ghlOverlap: [\n { name: \"1. Wait 1 Day: Initial Nurture - Puppy\", status: \"published\", version: 2 },\n { name: \"1. Wait 1 Day: Initial Nurture\", status: \"published\", version: 2 },\n { name: \"Edited - Main New Nurture (New/Updated)\", status: \"published\", version: 4 },\n { name: \"Secondary Nurture Workflow\", status: \"published\", version: 4 },\n { name: \"A. Removed Tag : Initial Lead Nurtures\", status: \"published\", version: 2 },\n { name: \"Secondary Nurture - PUPPY Workflow\", status: \"draft\", version: 5 },\n { name: \"1. Initial Nurture - Facebook\", status: \"draft\", version: 3 },\n { name: \"1. Initial Nurture - Instagram\", status: \"draft\", version: 3 },\n ],\n },\n {\n key: \"behavior\", label: \"Behavior problems\", sourceTag: \"nurture - behavior\", enrolledTag: \"behavior-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\", \"sms\"], steps: [],\n notes: \"Largest real demand signal, 172 asks in the gap log. The day-14 aggression email is the highest-risk message in the whole set and Kim reads it personally before this path is switched on.\",\n ghlOverlap: [\n { name: \"Behavior Quiz Submitted\", status: \"published\", version: 3 },\n { name: \"Dialed In Dog ZJ : Free Training Day Quiz\", status: \"published\", version: 16 },\n { name: \"Quiz -. Pup Talk > Notes\", status: \"published\", version: 4 },\n { name: \"Quiz Score Redirect Logic\", status: \"draft\", version: 6 },\n ],\n },\n {\n key: \"boarding\", label: \"Boarding inquiries\", sourceTag: \"nurture - boarding\", enrolledTag: \"boarding-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\", \"sms\"], steps: [],\n notes: \"The only path allowed to quote prices, and only the boarding ones Kim confirmed. Every mention of hours must carry the appointment-only rule. Booking goes to her website form, never a GHL calendar.\",\n ghlOverlap: [\n { name: \"Boarding Drop-Off - Confirmation + Reminder\", status: \"published\", version: 19 },\n { name: \"Boarding Pick-Up - Confirmation + Reminder\", status: \"published\", version: 25 },\n { name: \"Abandoned Cart - Partial booking\", status: \"published\", version: 5 },\n { name: \"Cancel Boarding - Drop Off\", status: \"published\", version: 3 },\n { name: \"Online Boarding Update > Kennel\", status: \"published\", version: 4 },\n { name: \"Boarding App Webhook\", status: \"published\", version: 18 },\n ],\n },\n {\n key: \"noshow\", label: \"Pup Talk, didn't show\", sourceTag: \"nurture - noshow\", enrolledTag: \"noshow-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\", \"sms\"], steps: [],\n notes: \"Closes a measured hole: 19 no-shows and 8 cancellations across 145 Pup Talk events with nothing following up.\",\n ghlOverlap: [\n { name: \"Cxld/Canceled Pup Talk\", status: \"published\", version: 7 },\n { name: \"Cxld or No Show - Consult Nurture\", status: \"published\", version: 4 },\n { name: \"Free training day no show nurture\", status: \"published\", version: 9 },\n { name: \"Cxld/Canceled Free Training Day\", status: \"published\", version: 4 },\n { name: \"Tag Added 'No Show' > No Show\", status: \"published\", version: 2 },\n { name: \"Tag Added 'No Show DND' > No Show TO PREVENT ANOTHER BOOKING\", status: \"published\", version: 2 },\n { name: \"Free Training Day abandoned booking\", status: \"published\", version: 8 },\n ],\n },\n {\n key: \"didntbuy\", label: \"Pup Talk, didn't buy\", sourceTag: \"nurture - didntbuy\", enrolledTag: \"didntbuy-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\", \"sms\"], steps: [],\n notes: \"82 attended and few converted. Kim's $500 discount decision lives near this path, keep them separate until its wording and its own dry/live toggle exist.\",\n ghlOverlap: [\n { name: \"POST CONSULT - NO SALE NURTURE MESSAGES\", status: \"published\", version: 4 },\n { name: \"Tag added 'No Sale' > No Sale Nurture\", status: \"published\", version: 2 },\n ],\n },\n {\n key: \"aged\", label: \"Dormant inquiries\", sourceTag: \"nurture - aged\", enrolledTag: \"aged-path-v1\",\n source: \"off\", channelsAtLaunch: [\"email\"],\n steps: [],\n notes: \"EMAIL ONLY AT LAUNCH, and the audience is far smaller than the headline: of 3,426 dormant contacts only ~164 have an email address and ~2,655 have neither email nor phone. SMS stays held until numbers are validated, stale numbers get a business flagged by carriers, which would damage every other path.\",\n ghlOverlap: [\n { name: \"Tips Nurture\", status: \"published\", version: 7 },\n { name: \"TIPS FACEBOOK CAMPAIGN - SMS Nurture\", status: \"published\", version: 3 },\n { name: \"Auto Replies > tips campaign\", status: \"published\", version: 10 },\n { name: \"Copy - Tips Ad campaign > Auto Responder\", status: \"published\", version: 11 },\n { name: \"Tips ad campaign > response > phone number\", status: \"published\", version: 10 },\n { name: \"Tips Ad campaign > Auto Responder\", status: \"draft\", version: 19 },\n ],\n },\n];\n\n// ---- the validator --------------------------------------------------------------------------------\n\nconst BANNED = [\n { re: /discovery/i, why: 'Kim banned \"discovery call\", it is \"Pup Talk\"' },\n { re: /grooming/i, why: \"grooming is not a service they offer\" },\n { re: /\\$\\s?\\d/, why: \"a price in a message; boarding prices come from the knowledge base, training prices never\" },\n // Templates legitimately contain {{FIRST_NAME}} and {{DOG_NAME}}, they are resolved per contact at\n // render time, and the engine has fallbacks for both when a contact has neither. Anything ELSE in\n // double braces is a token nobody wired up, which is what actually reaches a customer as literal\n // text. Caught by the first validator run, which flagged all 12 real templates: a check that fails\n // on correct input is worse than no check.\n { re: /\\{\\{(?!\\s*(FIRST_NAME|DOG_NAME)\\s*\\}\\})/, why: \"an unrecognised merge token, only {{FIRST_NAME}} and {{DOG_NAME}} are wired up\" },\n { re: /\\[link\\]|\\[phone\\]|INSERT|TODO|LOREM/i, why: \"a placeholder that never got resolved\" },\n];\n\nexport function validatePath(p: PathDef) {\n const errors: string[] = [], warnings: string[] = [];\n if (!p.steps.length) return { key: p.key, registered: false, ok: false, errors: [\"no steps registered yet\"], warnings: [] };\n\n let sawOptOut = false, sawBooking = false;\n const sms = p.steps.filter((s) => s.channel === \"sms\");\n\n for (const s of p.steps) {\n const text = `${s.subject ?? \"\"}\\n${s.previewText ?? \"\"}\\n${s.bodyTemplate}`;\n for (const b of BANNED) if (b.re.test(text)) errors.push(`${s.id}: ${b.why}`);\n if (/\\bstop\\b/i.test(s.bodyTemplate) || /reply\\s+stop/i.test(s.bodyTemplate)) sawOptOut = true;\n if (s.bodyTemplate.includes(OWNED_BOOKING_ID) || s.bodyTemplate.includes(OWNED_BOARDING_FORM)) sawBooking = true;\n if (/leadconnectorhq\\.com\\/widget\\/bookings?\\//.test(s.bodyTemplate) &&\n !s.bodyTemplate.includes(OWNED_BOOKING_ID)) {\n errors.push(`${s.id}: booking link does not point at a calendar this account owns, this is the exact defect found on 2 Aug`);\n }\n if (s.channel === \"sms\" && s.bodyTemplate.length > 320) errors.push(`${s.id}: SMS ${s.bodyTemplate.length} chars, over the 320 ceiling`);\n if (s.channel === \"email\" && !s.subject) errors.push(`${s.id}: email with no subject line`);\n }\n\n const offsets = p.steps.map((s) => s.offsetHours);\n const mainish = p.steps.filter((s) => s.id.startsWith(\"main\"));\n if (mainish.length > 1) {\n for (let i = 1; i < mainish.length; i++) {\n if (mainish[i].offsetHours <= mainish[i - 1].offsetHours) {\n errors.push(`${mainish[i].id}: timing does not move forward (${mainish[i - 1].offsetHours}h then ${mainish[i].offsetHours}h)`);\n }\n }\n }\n if (Math.max(...offsets) < 24 * 21) warnings.push(`longest step is ${Math.round(Math.max(...offsets) / 24)} days, the client was sold a minimum 30-day journey`);\n if (!sawOptOut && sms.length) warnings.push(\"no opt-out wording found in any SMS\");\n if (!sawBooking) warnings.push(\"no booking link anywhere in this path\");\n if (p.source === \"engine\" && p.channelsAtLaunch.includes(\"sms\") && p.key === \"aged\") {\n errors.push(\"aged path must not launch with SMS until the number list has been validated\");\n }\n\n return { key: p.key, registered: true, ok: errors.length === 0, errors, warnings, steps: p.steps.length, sms: sms.length, email: p.steps.length - sms.length };\n}\n\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n if (!(await authorised(url.searchParams.get(\"k\") || \"\"))) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n const results = PATHS.map(validatePath);\n const payload = {\n at: new Date().toISOString(),\n registered: results.filter((r) => r.registered).length,\n awaitingCopy: results.filter((r) => !r.registered).map((r) => r.key),\n live: PATHS.filter((p) => p.source === \"engine\").map((p) => p.key),\n mutualExclusion: \"each path names exactly one owner, engine, ghl, or off. No path can be run by both.\",\n paths: PATHS.map((p) => ({\n key: p.key, label: p.label, sourceTag: p.sourceTag, enrolledTag: p.enrolledTag,\n source: p.source, channelsAtLaunch: p.channelsAtLaunch, steps: p.steps.length, notes: p.notes,\n validation: results.find((r) => r.key === p.key),\n })),\n };\n if (url.searchParams.get(\"f\") === \"json\" || url.searchParams.get(\"validate\") === \"1\") {\n return new Response(JSON.stringify(payload, null, 2), { headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" } });\n }\n const rows = payload.paths.map((p: any) => {\n const v = p.validation;\n const status = !v.registered ? 'awaiting copy'\n : v.ok ? 'passes every check'\n : `${v.errors.length} problem(s)`;\n return `${p.label}
${p.sourceTag}${p.source}${p.steps || \"-\"}${status}${p.notes}`;\n }).join(\"\");\n return new Response(`Nurture paths\n\n
The six nurture paths
\n
${payload.registered} of ${payload.paths.length} have copy registered. Registering the rest is NOT a copy drop: the engine reads its sequences directly and stores one position per contact, not one per path, so each additional path needs the state model, per-path tag mapping, sequence selection and precedence rules built. Days of work each, not an afternoon. This page is a registry and a validator, not the wiring. Every path is checked against the same rules before it can run.
\n${rows}
Path Owner Steps Validator Constraint that governs it
\n
Owner is the mutual-exclusion switch: engine, ghl, or off. Nothing can be run by two systems at once, that is what put a Facebook script on the website in July.
`,\n { headers: { \"content-type\": \"text/html; charset=utf-8\" } });\n}\n",[237],"3cd3905a-2e0b-4d4e-9a57-c2a848196f9d","main.ts","cdd9f676-8c34-11f1-baf4-1607ee4eb77e",278,["D",1786043003913],18,"interval","// PUPPY PATH ENGINE v1.1 — nurture automation for The Dogs Spot's puppy leads (built 27 Ju\n// (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n\n// ---- Node/tsx compatibility shim, for the local test harness only --------------------------------\n// Val.town/Deno provides a global `Deno`; this file is normally only ever loaded there. No Deno\n// runtime was available in this build/test session, so the local test harness\n// (puppy-path-engine.test.ts) imports this exact file under Node + tsx instead. The lines below define\n// a minimal stand-in ONLY when `Deno` doesn't already exist. Under real val.town execution `Deno` is\n// already defined, the `if` is false, and this block never runs — zero effect on deployed behavior.\ndeclare const Deno: { env: { get(key: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\n\n// Message copy + display constants live in ./puppy-messages.ts (split for val.town's 80k/file cap).\nimport {\n MAIN_SEQUENCE,\n BRANCH_A,\n BRANCH_B,\n PHONE_DISPLAY,\n REAL_BOOKING_URL,\n SHORT_BOOKING_LINK,\n} from \"./puppy-messages.ts\";\nimport type { Channel, MessageTemplate } from \"./puppy-messages.ts\";\n// v1.7 — slow track (taper). Copy+cadence in ./taper-messages.ts; Kim's spec (3 Aug): weekly x4,\n// fortnightly x13, then monthly forever, no asks. Same rails: reply pauses, booking exits, consent.\nimport { nextSlowTouch, monthlyTemplateFor, monthlyTemplateAvoidingRepeat } from \"./taper-messages.ts\";\n// v1.8 — Kim's real stories, one data file, additive slots. Null slots render as nothing.\nimport { resolveStories } from \"./kim-stories.ts\";\nimport { appendRunStamp } from \"./cadence.ts\";\nimport { dryScan } from \"./puppy-detect.ts\";\nimport { resolveDogName, resolveFirstName, applyMergeFields, escHtml, bodyToHtml } from \"./render.ts\";\n\n// ---- reference IDs (spec §2, all verified live this session unless noted) ------------------------\n\nconst GHL = \"https://services.leadconnectorhq.com\";\n// v1.2 — TOKEN RESOLUTION: GHL_TOKEN env var, else private blob `puppy_config`. Blob fallback\n// exists because val.town has no env-var API. Code is public; token never hardcoded. Full note:\n// NOTES-v1.4.md.\nlet TOKEN: string | undefined = Deno.env.get(\"GHL_TOKEN\");\nasync function resolveToken(): Promise {\n if (TOKEN) return TOKEN;\n try {\n const blob = await getBlobModule();\n const cfg = await blob.getJSON(\"puppy_config\").catch(() => null);\n if (cfg?.ghlToken) TOKEN = String(cfg.ghlToken);\n } catch { /* stays undefined; j() will throw a clear auth error */ }\n return TOKEN;\n}\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\nconst MAIN_PIPELINE_ID = \"FXt1UpCVBufbF0v3pfyf\"; // \"1) Initial Lead Pipeline\"\n\nconst STAGE = {\n NEW_LEAD: \"ccb18375-9aa1-40aa-a071-1581ca739533\",\n LEAD_NURTURE: \"00d0f792-38e5-444e-8995-a1be96e77d3b\",\n FREE_TRAINING_DAY: \"43ea02b4-529b-4063-b638-447414d603d2\",\n PUP_TALK: \"379d1dd2-fc18-4720-a840-e8f8ed703bb9\",\n CXLD_PUPTALK_TRAINING_DAY: \"4b5599d3-a5ad-4b8c-8388-4d5507c22fd7\",\n NO_SALE_NURTURE: \"e4511876-0adb-417b-a6be-8460a194f913\",\n DISQUALIFIED: \"38826f17-1d0e-4bac-b53e-349b67c2c79d\",\n NO_SHOW: \"f3f41e5e-edaf-4ef1-8cec-c4cccd4ec5c2\",\n ONBOARDING: \"76c72f7f-56bd-4f44-964d-aa4cbbec7d25\",\n CUSTOMER: \"fd821b4e-bbe6-44de-b754-fa80e4823616\",\n WON_PAID: \"ae173310-f8b1-4399-acb7-ef1fc03d3697\",\n} as const;\n\nconst PUP_TALK_CALENDAR_ID = \"qHuYJ0NEqzibnoqf5Cw3\";\n\n\n// v1.1: env-overridable, and now understood as the HUMAN ENROLLMENT SWITCH, not auto-discovery of a\n// pre-existing population — live check 27 Jul: zero contacts carry it (or any spelling variant), so\n// applying it is how a human puts someone on the path. READ ONLY here, never written by this engine.\nconst TAG_SOURCE_SIGNAL = Deno.env.get(\"TAG_SOURCE_SIGNAL\") || \"nurture - puppy\";\nconst TAG_ENROLLED = \"puppy-path-v1\"; // minted by this engine, applied on enrollment\n\n// v1.1 send-window + surge-hold knobs (see header addendum). Read per call, not once at module load —\n// costs nothing at this call volume and lets the offline harness flip them per test section; under\n// val.town the env is static so behavior is identical either way.\nconst sendWindowStartHour = () => Number(Deno.env.get(\"SEND_WINDOW_START_HOUR\") ?? \"9\");\nconst sendWindowEndHour = () => Number(Deno.env.get(\"SEND_WINDOW_END_HOUR\") ?? \"19\");\nconst smsSundayOk = () => (Deno.env.get(\"SMS_SUNDAY_OK\") ?? \"false\") === \"true\";\nconst enrollSurgeThreshold = () => Number(Deno.env.get(\"ENROLL_SURGE_THRESHOLD\") ?? \"25\");\nconst acknowledgeSurge = () => (Deno.env.get(\"ACKNOWLEDGE_SURGE\") ?? \"false\") === \"true\";\nconst BUSINESS_TZ = \"America/New_York\";\n\n// v1.2 hardening knobs (adversarial-review round, 30 Jul). All env-overridable, read per call.\n// MIN_SEND_GAP_HOURS: floor between two sends to the SAME contact — after an outage, overdue steps\n// space out at 2h apart instead of one per 15-min cron tick (the designed main-1→main-2 gap is\n// exactly 2h, so the default never delays an on-schedule send).\n// MAX_SENDS_PER_RUN / MAX_SENDS_PER_DAY: blast ceilings, mirroring the PupsClub val's precedent.\n// Excess due-sends defer to later runs, identical in spirit to the send-window deferral.\nconst minSendGapHours = () => Number(Deno.env.get(\"MIN_SEND_GAP_HOURS\") ?? \"2\");\nconst maxSendsPerRun = () => Number(Deno.env.get(\"MAX_SENDS_PER_RUN\") ?? \"20\");\nconst maxSendsPerDay = () => Number(Deno.env.get(\"MAX_SENDS_PER_DAY\") ?? \"50\");\n// v1.4 — how often a contact gets a full CRM check even when nothing is due. The floor under\n// due-first filtering: cheap must not become blind.\n// v1.4 — how long a reply can sit unanswered before the engine escalates and releases the contact.\nconst pauseTimeoutDays = () => Number(Deno.env.get(\"PAUSE_TIMEOUT_DAYS\") ?? \"14\");\n// v1.5 R27 — how long the engine stands down after ANY other system messages the contact. 24h is one\n// full business cycle: long enough that a customer never gets our email on the same day as a workflow\n// text, short enough that a 21-day sequence still completes near schedule (a deferred step is never\n// dropped, it waits for the next run).\nconst foreignQuietHours = () => Number(Deno.env.get(\"FOREIGN_QUIET_HOURS\") ?? \"24\");\n// Tolerance when deciding \"was that outbound ours?\" — clock skew between our send and GHL stamping\n// the conversation. Anything inside this window of our own lastSentAt is treated as ours.\nconst OURS_TOLERANCE_MS = 5 * 60 * 1000;\nconst safetySweepHours = () => Number(Deno.env.get(\"SAFETY_SWEEP_HOURS\") ?? \"24\");\nconst RUN_LOCK_TTL_MS = 10 * 60 * 1000; // a run that started >10 min ago is presumed dead\n\nconst sleep = (ms: number) => new Promise((r) => setTimeout(r, ms));\n\n// Rule 8's real signal — NOT CONFIRMED LIVE this session, see gap #2 in the header comment. Left as a\n// clearly-named constant so wiring in the real value later is a one-line change, not a re-guess.\nconst PUP_TALK_DECLINED_TAG = \"TDS-Declined\";\n\nconst HOUR_MS = 3600 * 1000;\nconst DAY_MS = 24 * HOUR_MS;\n\nconst TEST_MODE = (Deno.env.get(\"TEST_MODE\") ?? \"true\") !== \"false\";\n\n// ---- data model (spec §4, verbatim) ---------------------------------------------------------------\n\ntype PuppyStatus =\n | \"main\" | \"awaiting_appt_outcome\" | \"branch_a\" | \"branch_b\" | \"slow_track\"\n | \"paused_reply\" | \"done_booked\" | \"done_customer\" | \"done_hard_exit\"\n | \"done_soft_21d\" | \"done_branch_complete\";\n\n// v1.7 — done_soft_21d stays terminal for LEGACY pre-taper contacts only (no retroactive\n// enrollment). New 21-day completions flow into slow_track instead.\nconst TERMINAL_STATUSES = new Set([\n \"done_booked\", \"done_customer\", \"done_hard_exit\", \"done_soft_21d\", \"done_branch_complete\",\n]);\n\ntype PuppyState = {\n status: PuppyStatus;\n enteredAt: string; // ISO — main sequence start\n lastMainStepSent: number; // 0..8, count of main-sequence messages sent so far\n branchAnchorAt: string | null; // ISO — when branch A/B started\n lastBranchStepSent: number; // 0..2\n pausedForReplyAt: string | null;\n exitReason: string | null; // free text, for humans reading the blob\n lastCheckedAt: string; // ISO, updated every run this contact is touched\n lastSentAt?: string | null; // v1.2 — ISO of the last successful send to this contact (min-gap pacing)\n // v1.4 — R24: monetaryValue was read on every opportunity and thrown away, while the one question\n // the client judges a report by is \"how much revenue did that produce\". Captured at exit.\n exitValue?: number | null; // monetaryValue of the opportunity that ended the sequence\n exitStepsSent?: number | null; // how many messages they had received when they converted\n lastSentStepId?: string | null; // v1.4 — R23: the step ID, so editing copy cannot silently re-point anyone\n // v1.7 — slow track. Optional so pre-v1.7 blobs deserialize untouched; readers default them.\n slowAnchorAt?: string | null; // ISO — when the contact entered the slow track (21-day completion)\n lastSlowStepSent?: number; // count of slow-track messages sent (weekly+fortnightly+monthly)\n};\n\nfunction freshState(enteredAt: string): PuppyState {\n return {\n status: \"main\", enteredAt, lastMainStepSent: 0, branchAnchorAt: null,\n lastBranchStepSent: 0, pausedForReplyAt: null, exitReason: null, lastCheckedAt: enteredAt,\n lastSentAt: null, exitValue: null, exitStepsSent: null, lastSentStepId: null,\n slowAnchorAt: null, lastSlowStepSent: 0,\n };\n}\n\n// ---- pure helpers: timing, merge fields, rendering ------------------------------------------------\n\nfunction isDue(offsetHours: number, anchorIso: string, nowMs: number): boolean {\n return nowMs >= new Date(anchorIso).getTime() + offsetHours * HOUR_MS;\n}\n\n// v1.1 — business-local wall clock for a UTC instant. Intl with an explicit timeZone is deterministic\n// and DST-correct on both Deno and Node; no date library needed for two fields.\nfunction businessLocalParts(nowMs: number): { hour: number; weekday: string } {\n const parts = new Intl.DateTimeFormat(\"en-US\", {\n timeZone: BUSINESS_TZ,\n hour12: false,\n hour: \"2-digit\",\n weekday: \"short\",\n }).formatToParts(new Date(nowMs));\n const get = (t: string) => parts.find((p) => p.type === t)?.value ?? \"\";\n // Intl gives \"24\" for midnight under hour12:false+2-digit in some engines; normalize to 0.\n const hour = Number(get(\"hour\")) % 24;\n return { hour, weekday: get(\"weekday\") };\n}\n\n// v1.1 — send-window gate (header addendum #3). Pure given (nowMs, channel); env knobs are read once\n// at module load. Emails are allowed any day inside the hour window; SMS additionally respects the\n// closed-on-Sundays business identity unless SMS_SUNDAY_OK.\nfunction inSendWindow(channel: Channel, nowMs: number): { ok: boolean; reason: string } {\n const start = sendWindowStartHour();\n const end = sendWindowEndHour();\n const { hour, weekday } = businessLocalParts(nowMs);\n if (hour < start || hour >= end) {\n return { ok: false, reason: `outside ${start}:00–${end}:00 ${BUSINESS_TZ} (local hour ${hour})` };\n }\n if (channel === \"sms\" && weekday === \"Sun\" && !smsSundayOk()) {\n return { ok: false, reason: \"no SMS on Sundays (business closed)\" };\n }\n return { ok: true, reason: \"\" };\n}\n\ntype RenderedMessage =\n | { channel: \"email\"; subject: string; html: string }\n | { channel: \"sms\"; text: string };\n\n// Appended to every rendered message. Kept as constants so the wording is in exactly one place.\nconst SMS_OPTOUT = \"\\n\\nReply STOP to stop these texts.\";\nconst EMAIL_OPTOUT =\n \"\\n\\n---\\nYou're getting this because you inquired with The Dogs Spot. \" +\n \"Reply UNSUBSCRIBE and we'll take you off these emails.\\n\" +\n \"The Dogs Spot, Ellabell, GA\";\n\nfunction renderStep(\n step: MessageTemplate,\n contact: { firstName: string | null | undefined; companyName: string | null | undefined },\n opts: { testMode: boolean },\n): RenderedMessage {\n const prefix = opts.testMode ? \"[TEST] \" : \"\";\n // v1.8 — story slots resolve before merge fields; a null slot leaves no trace.\n const resolvedBody = applyMergeFields(resolveStories(step.bodyTemplate), contact.firstName, contact.companyName);\n\n // ---- v1.4 (2 Aug) — OPT-OUT FURNITURE, appended at render time, never written into the c\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n if (step.channel === \"email\") {\n const resolvedPreview = step.previewText\n ? applyMergeFields(step.previewText, contact.firstName, contact.companyName)\n : undefined;\n return {\n channel: \"email\",\n subject: prefix + applyMergeFields(step.subject ?? \"\", contact.firstName, contact.companyName),\n html: bodyToHtml(resolvedBody + EMAIL_OPTOUT, resolvedPreview),\n };\n }\n return { channel: \"sms\", text: prefix + resolvedBody + SMS_OPTOUT };\n}\n\n// ---- facts / decision types -------------------------------------------------------------------\n\ntype ApptFact = {\n id: string;\n startTime: number; // epoch ms\n endTime: number; // epoch ms\n appointmentStatus: string;\n deleted: boolean;\n};\n\ntype OppFact = {\n id: string;\n pipelineId: string;\n pipelineStageId: string;\n monetaryValue: number;\n status: string;\n};\n\ntype ContactFact = {\n id: string;\n firstName: string;\n companyName: string | null;\n dnd: boolean;\n};\n\ntype Facts = {\n now: number;\n contact: ContactFact;\n opportunities: OppFact[];\n pupTalkAppt: ApptFact | null;\n declinedSignal: boolean;\n hasUnansweredInboundReply: boolean;\n conversationCheckFailed: boolean;\n // v1.5 R27 — epoch ms of the newest outbound message on this contact's thread that this engine did\n // NOT send, or null when there is none / it cannot be told apart from ours. See sendGate.\n foreignOutboundAt: number | null;\n // v1.6 R28 — per-channel consent, read from GHL's dndSettings. true = this channel is opted out.\n channelBlocked: { email: boolean; sms: boolean };\n};\n\ntype Decision =\n | { kind: \"hard_exit\"; status: \"done_hard_exit\" | \"done_customer\" | \"done_booked\"; reason: string }\n | { kind: \"pause_reply\"; isNewPause: boolean }\n | { kind: \"advance_status\"; status: \"awaiting_appt_outcome\" | \"branch_a\" | \"branch_b\" | \"slow_track\"; branchAnchorAt?: string }\n | { kind: \"soft_exit_21d\" }\n | { kind: \"branch_complete\" }\n | { kind: \"send\"; sequence: \"main\" | \"branch_a\" | \"branch_b\" | \"slow\"; stepIndex: number }\n | { kind: \"skip_step\"; sequence: \"main\" | \"branch_a\" | \"branch_b\" | \"slow\"; stepIndex: number; reason: string }\n | { kind: \"skip\"; reason: string };\n\n// v1.7 — slow template for a progression index AT a moment. Weekly/fortnightly fixed by index;\n// monthly picked by the send's calendar month (July=heat, Dec=holidays — as promised to Kim).\n// Shared by decideAction AND the executor so decided and sent templates cannot drift.\nfunction slowTemplateAt(sentCount: number, nowMs: number, lastSentId?: string | null): { tpl: MessageTemplate; offsetHours: number; phase: string } {\n // v1.7.1 — clamp garbage counters (NaN/negative/string blobs) instead of letting an out-of-range\n // index fall through to \"send monthly now\"; monthly fallback only ever fires in the monthly phase.\n const clean = Math.max(0, Math.floor(Number(sentCount)) || 0);\n const n = nextSlowTouch(clean);\n const tpl = n.phase === \"monthly\" ? monthlyTemplateAvoidingRepeat(new Date(nowMs), lastSentId) : n.template!;\n return { tpl, offsetHours: n.offsetHours, phase: n.phase };\n}\n\nfunction pickPrimaryOpportunity(opps: OppFact[]): OppFact | null {\n return opps.find((o) => o.pipelineId === MAIN_PIPELINE_ID) ?? opps[0] ?? null;\n}\n\n// \"Live\" = not cancelled, not invalid, not soft-deleted. Anything else (new / confirmed / showed /\n// noshow) counts as \"they booked\" for rule 6's purposes — the outcome gets sorted out by rules 7/8.\nfunction apptIsLiveBooked(appt: ApptFact | null): boolean {\n if (!appt || appt.deleted) return false;\n return appt.appointmentStatus !== \"cancelled\" && appt.appointmentStatus !== \"invalid\";\n}\n\n// ---- the core state machine (spec §5) ---------------------------------------------------------\n// Pure function: no network, no side effects. Every rule below is evaluated in order for every call —\n// \"first match wins\" per spec, so a later rule never overrides an earlier one, and the SAME order runs\n// for every contact on every pass regardless of their current status. This is what the whole safety\n// story rests on, so it is tested exhaustively — see puppy-path-engine.test.ts.\nfunction decideAction(f: Facts, s: PuppyState): Decision {\n // Rule 1 + 2 — DND / unsubscribed. Top-level `dnd` = full opt-out, hard exit here. Since v1.6\n // (R28) per-channel opt-outs in `dndSettings` are ALSO read — not here, but as f.channelBlocked,\n // which skip-consumes steps on a blocked channel while the other channel carries on. Both layers\n // are live; this rule is the total-stop one.\n if (f.contact.dnd) {\n return { kind: \"hard_exit\", status: \"done_hard_exit\", reason: \"dnd\" };\n }\n\n const primaryOpp = pickPrimaryOpportunity(f.opportunities);\n\n // Rule 3 — Disqualified stage (human override, outranks everything below it).\n if (primaryOpp?.pipelineStageId === STAGE.DISQUALIFIED) {\n return { kind: \"hard_exit\", status: \"done_hard_exit\", reason: \"disqualified\" };\n }\n\n // Rule 4 — became a paying customer. v1.2: scans ALL opportunities, not just primary (fuzz\n // round finding; full note in NOTES-v1.4.md).\n const becameCustomer = f.opportunities.some(\n (o) => o.pipelineStageId === STAGE.CUSTOMER || o.pipelineStageId === STAGE.WON_PAID || o.monetaryValue > 0,\n );\n if (becameCustomer) {\n return { kind: \"hard_exit\", status: \"done_customer\", reason: \"became a customer\" };\n }\n\n // Rule 4b — booked something else entirely (Free Training Day). NOT an explicit numbered r\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n if (primaryOpp?.pipelineStageId === STAGE.FREE_TRAINING_DAY) {\n return { kind: \"hard_exit\", status: \"done_booked\", reason: \"booked Free Training Day — sequence ends per writing sheet §4\" };\n }\n\n // Rule 5 — inbound reply pending, or: couldn't check at all (fail closed — see header gap #1).\n // conversationCheckFailed must be checked BEFORE hasUnansweredInboundReply: an unreadable signal is\n // never treated as \"confirmed no reply,\" because that would let sends continue for someone who may\n // well have replied — exactly the failure this rule exists to prevent.\n if (f.conversationCheckFailed) {\n return { kind: \"skip\", reason: \"conversation check failed (live API scope gap) — not sending until resolved\" };\n }\n if (f.hasUnansweredInboundReply) {\n // \"First match wins\" still applies every run, so this keeps matching (and keeps blocking rule 10)\n // for as long as the reply sits unanswered — but the SIDE EFFECT (timestamping the pause, creating\n // a task) only happens the first time, guarded by isNewPause. Otherwise every run would create a\n // fresh duplicate task for the same unanswered reply.\n return { kind: \"pause_reply\", isNewPause: s.status !== \"paused_reply\" };\n }\n\n // Rule 6 — a live Pup Talk booking -> awaiting_appt_outcome. Scoped to the Pup Talk calendar\n // (branch copy is Pup-Talk-specific; FTD handled by 4b; full note in NOTES-v1.4.md).\n // v1.7.1 — the slow arm requires the appointment to POSTDATE slow entry (mirrors 6b): a stale\n // historical appointment must not yank a taper contact into branch copy.\n if (s.status === \"main\" && apptIsLiveBooked(f.pupTalkAppt)) {\n return { kind: \"advance_status\", status: \"awaiting_appt_outcome\" };\n }\n if (\n s.status === \"slow_track\" && f.pupTalkAppt && apptIsLiveBooked(f.pupTalkAppt) &&\n f.pupTalkAppt.startTime > new Date(s.slowAnchorAt ?? s.enteredAt).getTime()\n ) {\n return { kind: \"advance_status\", status: \"awaiting_appt_outcome\" };\n }\n\n // Rule 6b (v1.2) — REBOOKED while in a branch. Found independently by the adversarial revi\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n if (\n (s.status === \"branch_a\" || s.status === \"branch_b\") &&\n f.pupTalkAppt &&\n apptIsLiveBooked(f.pupTalkAppt) &&\n s.branchAnchorAt &&\n f.pupTalkAppt.startTime > new Date(s.branchAnchorAt).getTime()\n ) {\n return { kind: \"advance_status\", status: \"awaiting_appt_outcome\" };\n }\n\n // Rule 7 — awaiting -> branch_a (missed): time passed, not showed, not cancelled. Funnel-phase\n // cancellations stay parked here on purpose — the \"Cxld Pup Talk\" workflow owns that case\n // (writing sheet §4; full note in NOTES-v1.4.md). Slow-phase cancellations: rule 7s above.\n // v1.7.1 — Rule 7s: a slow-track contact who booked and then CANCELLED goes back on the taper\n // (anchor and counter intact) instead of parking in awaiting_appt_outcome forever. Scoped to\n // contacts with a slow anchor; funnel-phase cancellations still belong to the Cxld workflow.\n if (\n s.status === \"awaiting_appt_outcome\" && s.slowAnchorAt && f.pupTalkAppt &&\n f.pupTalkAppt.appointmentStatus === \"cancelled\"\n ) {\n return { kind: \"advance_status\", status: \"slow_track\" };\n }\n\n if (\n s.status === \"awaiting_appt_outcome\" &&\n f.pupTalkAppt &&\n f.now >= f.pupTalkAppt.endTime &&\n f.pupTalkAppt.appointmentStatus !== \"showed\" &&\n f.pupTalkAppt.appointmentStatus !== \"cancelled\"\n ) {\n return {\n kind: \"advance_status\",\n status: \"branch_a\",\n branchAnchorAt: new Date(f.pupTalkAppt.endTime).toISOString(),\n };\n }\n\n // Rule 8 — awaiting -> branch_b (showed, then declined). declinedSignal NOT CONFIRMED LIVE\n // (header gap #2); branchAnchorAt uses \"now\" per spec's fallback.\n if (\n s.status === \"awaiting_appt_outcome\" &&\n f.pupTalkAppt &&\n f.pupTalkAppt.appointmentStatus === \"showed\" &&\n f.declinedSignal\n ) {\n return { kind: \"advance_status\", status: \"branch_b\", branchAnchorAt: new Date(f.now).toISOString() };\n }\n\n // Rule 9 — 21-day completion. Gated on message 8 having actually SENT, not elapsed time alone\n // (else this outranks rule 10 on the very run msg 8 becomes due and it never sends —\n // NOTES-v1.4.md). Stage never auto-moved; that is Kim's call.\n if (\n s.status === \"main\" &&\n s.lastMainStepSent >= MAIN_SEQUENCE.length &&\n f.now >= new Date(s.enteredAt).getTime() + 21 * DAY_MS\n ) {\n return { kind: \"soft_exit_21d\" };\n }\n\n // Rule 9b — branch exhausted -> done_branch_complete (the type's own terminal; a contact must\n // not sit re-evaluated forever with nothing left to send). NOTES-v1.4.md.\n if (s.status === \"branch_a\" && s.lastBranchStepSent >= BRANCH_A.length) {\n return { kind: \"branch_complete\" };\n }\n if (s.status === \"branch_b\" && s.lastBranchStepSent >= BRANCH_B.length) {\n return { kind: \"branch_complete\" };\n }\n\n // Rule 10 — otherwise, send whatever's next due. v1.1: a due step additionally waits for the send\n // window (inSendWindow). v1.2: and for the per-contact min-gap floor — after an outage, several\n // overdue steps space out ~2h apart instead of one per cron tick. Every deferral leaves state\n // untouched, so a later run simply picks it up.\n const sendGate = (channel: Channel): { ok: boolean; reason: string } => {\n const w = inSendWindow(channel, f.now);\n if (!w.ok) return w;\n if (s.lastSentAt) {\n const gapMs = minSendGapHours() * HOUR_MS;\n const sinceLast = f.now - new Date(s.lastSentAt).getTime();\n // v1.7 — sinceLast >= 0 guard (mirrors R27): a future-dated lastSentAt (clock skew, restored\n // blob) must not freeze the contact until that future date; negative elapsed = ignore the gap.\n if (sinceLast >= 0 && sinceLast < gapMs) {\n return { ok: false, reason: `min send gap (${minSendGapHours()}h) not elapsed — last send ${(sinceLast / HOUR_MS).toFixed(1)}h ago` };\n }\n }\n // R27 (v1.5) — FOREIGN-SENDER QUIET PERIOD: an outbound newer than ours means another system\n // owns this contact right now; stand down. Fails OPEN. Full rationale: NOTES-v1.4.md.\n if (f.foreignOutboundAt != null) {\n const quietMs = foreignQuietHours() * HOUR_MS;\n const since = f.now - f.foreignOutboundAt;\n if (since >= 0 && since < quietMs) {\n return {\n ok: false,\n reason: `another system messaged this contact ${(since / HOUR_MS).toFixed(1)}h ago — quiet period ${foreignQuietHours()}h`,\n };\n }\n }\n return { ok: true, reason: \"\" };\n };\n if (s.status === \"main\" && s.lastMainStepSent < MAIN_SEQUENCE.length) {\n const step = MAIN_SEQUENCE[s.lastMainStepSent];\n if (isDue(step.offsetHours, s.enteredAt, f.now)) {\n const g = sendGate(step.channel);\n if (!g.ok) return { kind: \"skip\", reason: `main #${s.lastMainStepSent + 1} due but deferred: ${g.reason}` };\n if (f.channelBlocked[step.channel]) {\n return { kind: \"skip_step\", sequence: \"main\", stepIndex: s.lastMainStepSent, reason: `opted out of ${step.channel} — step consumed, not sent` };\n }\n return { kind: \"send\", sequence: \"main\", stepIndex: s.lastMainStepSent };\n }\n return { kind: \"skip\", reason: `next main step (#${s.lastMainStepSent + 1}) not due yet` };\n }\n if (s.status === \"branch_a\" && s.lastBranchStepSent < BRANCH_A.length && s.branchAnchorAt) {\n const step = BRANCH_A[s.lastBranchStepSent];\n if (isDue(step.offsetHours, s.branchAnchorAt, f.now)) {\n const g = sendGate(step.channel);\n if (!g.ok) return { kind: \"skip\", reason: `branch A step due but deferred: ${g.reason}` };\n if (f.channelBlocked[step.channel]) {\n return { kind: \"skip_step\", sequence: \"branch_a\", stepIndex: s.lastBranchStepSent, reason: `opted out of ${step.channel} — step consumed, not sent` };\n }\n return { kind: \"send\", sequence: \"branch_a\", stepIndex: s.lastBranchStepSent };\n }\n return { kind: \"skip\", reason: \"next branch A step not due yet\" };\n }\n if (s.status === \"branch_b\" && s.lastBranchStepSent < BRANCH_B.length && s.branchAnchorAt) {\n const step = BRANCH_B[s.lastBranchStepSent];\n if (isDue(step.offsetHours, s.branchAnchorAt, f.now)) {\n const g = sendGate(step.channel);\n if (!g.ok) return { kind: \"skip\", reason: `branch B step due but deferred: ${g.reason}` };\n if (f.channelBlocked[step.channel]) {\n return { kind: \"skip_step\", sequence: \"branch_b\", stepIndex: s.lastBranchStepSent, reason: `opted out of ${step.channel} — step consumed, not sent` };\n }\n return { kind: \"send\", sequence: \"branch_b\", stepIndex: s.lastBranchStepSent };\n }\n return { kind: \"skip\", reason: \"next branch B step not due yet\" };\n }\n\n // v1.7 — Rule 10s: slow track. Indefinite by design, so no exhaustion exit — the exits are the\n // rules above (reply, booking, customer, DND). Anchor falls back to enteredAt if a legacy blob\n // lands here without slowAnchorAt.\n if (s.status === \"slow_track\") {\n const sentCount = Math.max(0, Math.floor(Number(s.lastSlowStepSent)) || 0);\n const anchor = s.slowAnchorAt ?? s.enteredAt;\n const { tpl, offsetHours, phase } = slowTemplateAt(sentCount, f.now, s.lastSentStepId);\n if (isDue(offsetHours, anchor, f.now)) {\n const g = sendGate(tpl.channel);\n if (!g.ok) return { kind: \"skip\", reason: `slow #${sentCount + 1} (${phase}) due but deferred: ${g.reason}` };\n if (f.channelBlocked[tpl.channel]) {\n return { kind: \"skip_step\", sequence: \"slow\", stepIndex: sentCount, reason: `opted out of ${tpl.channel} — slow step consumed, not sent` };\n }\n return { kind: \"send\", sequence: \"slow\", stepIndex: sentCount };\n }\n return { kind: \"skip\", reason: `next slow touch (#${sentCount + 1}, ${phase}) not due yet` };\n }\n\n return { kind: \"skip\", reason: `status ${s.status} has nothing to evaluate` };\n}\n\n// Pure: given a Decision (already known to have succeeded, or to need no IO at all) and the current\n// state, returns the resulting state fields. No IO. This is the ONE place PuppyState transitions are\n// written, used by both cron() (after a successful send/task, or immediately for decisions with no\n// gating IO) and the local test harness (to simulate a full multi-day run without live network calls)\n// — kept as a single function specifically so the tested behavior and the shipped behavior cannot\n// silently drift apart from each other.\nfunction applyDecision(decision: Decision, s: PuppyState, nowIso: string): PuppyState {\n const next: PuppyState = { ...s, lastCheckedAt: nowIso };\n switch (decision.kind) {\n case \"hard_exit\":\n next.status = decision.status;\n next.exitReason = decision.reason;\n return next;\n case \"pause_reply\":\n next.status = \"paused_reply\";\n if (decision.isNewPause) {\n next.pausedForReplyAt = nowIso;\n next.exitReason = \"human reply pending\";\n }\n return next;\n case \"advance_status\":\n next.status = decision.status;\n if (decision.branchAnchorAt) next.branchAnchorAt = decision.branchAnchorAt;\n // v1.2 — entering a branch always starts that branch's 2-message pass from the top. Matters for\n // the rule-6b re-entry paths (branch -> awaiting -> branch again for a NEW appointment): the\n // shared lastBranchStepSent counter would otherwise start a second branch pass mid-sequence\n // (or, worse, route a first branch_b pass to B2 because branch_a had already sent A1). A\n // repeated branch message only ever happens when a genuinely new no-show/decline occurred, so\n // the copy stays contextually true.\n if (decision.status === \"branch_a\" || decision.status === \"branch_b\") next.lastBranchStepSent = 0;\n // v1.7.1 — returning to slow_track (cancelled booking) keeps slowAnchorAt and\n // lastSlowStepSent untouched: the taper resumes where it left off.\n return next;\n case \"soft_exit_21d\":\n // v1.7 — 21-day completion now hands the contact to the slow track (Kim's taper);\n // done_soft_21d remains in the type for legacy blobs only.\n next.status = \"slow_track\";\n next.slowAnchorAt = nowIso;\n next.lastSlowStepSent = 0;\n next.exitReason = \"21-day sequence complete — moved to slow track\";\n return next;\n case \"branch_complete\":\n next.status = \"done_branch_complete\";\n next.exitReason = \"branch sequence complete, no reply\";\n return next;\n case \"send\":\n if (decision.sequence === \"main\") next.lastMainStepSent = s.lastMainStepSent + 1;\n else if (decision.sequence === \"slow\") next.lastSlowStepSent = (s.lastSlowStepSent ?? 0) + 1;\n else next.lastBranchStepSent = s.lastBranchStepSent + 1;\n next.lastSentAt = nowIso; // v1.2 — feeds the min-gap pacing floor\n return next;\n case \"skip_step\":\n // v1.6 R28 — the step is consumed, not deferred. Deferring a step whose channel the contact\n // has opted out of would stall that contact forever on a message that can never legally send.\n // lastSentAt is deliberately NOT set: nothing went out, so nothing should start the pacing clock.\n if (decision.sequence === \"main\") next.lastMainStepSent = s.lastMainStepSent + 1;\n else if (decision.sequence === \"slow\") next.lastSlowStepSent = (s.lastSlowStepSent ?? 0) + 1;\n else next.lastBranchStepSent = s.lastBranchStepSent + 1;\n return next;\n case \"skip\":\n return next;\n }\n}\n\n// ---- IO layer: GHL fetch helper (identical shape to the PupsClub val) -----------------------------\n\nasync function j(url: string, ver: string, init?: RequestInit) {\n const tok = await resolveToken(); // v1.2 — env var, else private puppy_config blob (see header note)\n const r = await fetch(url, {\n ...init,\n headers: {\n Authorization: `Bearer ${tok}`,\n Version: ver,\n \"Content-Type\": \"application/json\",\n ...(init?.headers ?? {}),\n },\n });\n if (!r.ok) throw new Error(`${r.status} ${url.split(\"?\")[0]} ${(await r.text()).slice(0, 200)}`);\n return r.json();\n}\n\n// ---- blob state (dynamic import, see Node/tsx shim note above) ------------------------------------\n\nasync function getBlobModule() {\n // Dynamic (not static like the PupsClub val) so this file's pure logic can be imported under Node +\n // tsx for local testing without resolving esm.town or needing a Deno runtime — under real\n // val.town/Deno execution this resolves identically, just on first call instead of at module load.\n // @ts-expect-error — remote Deno URL specifier; unresolvable (by design) under tsc/Node's module\n // resolution, only ever actually imported at runtime inside a real Deno/val.town environment.\n const mod = await import(\"https://esm.town/v/std/blob\");\n return (mod as any).blob;\n}\n\nasync function loadAllState(): Promise> {\n const blob = await getBlobModule();\n return (await blob.getJSON(\"puppy_state\").catch(() => null)) ?? {};\n}\nasync function saveAllState(state: Record) {\n const blob = await getBlobModule();\n await blob.setJSON(\"puppy_state\", state);\n}\n// v1.8.2. Each run records its own timestamp so the dashboard can report the cadence it OBSERVES\n// rather than one a human typed. See cadence.ts for why, and for the shared shape.\nasync function saveReport(report: any) {\n const blob = await getBlobModule();\n let history: string[] = [];\n try {\n history = appendRunStamp(await blob.getJSON(\"puppy_run_state\").catch(() => null),\n typeof report?.ts === \"string\" ? report.ts : new Date().toISOString());\n } catch { /* bookkeeping is a nicety; never fail a run over it */ }\n await blob.setJSON(\"puppy_run_state\", { ...(report as object), history });\n}\nasync function saveLastError(err: unknown) {\n const blob = await getBlobModule();\n await blob.setJSON(\"puppy_last_error\", err);\n}\n\n// ---- v1.1: journal + summary ----------------------------------------------------------------------\n\ntype JournalRow = { ts: string; contactId: string | null; event: string; detail: string; test?: boolean };\n\n// Appends this run's rows and returns the full merged journal (capped at the newest 2000 rows) so the\n// caller can build the summary from complete history without a second blob read.\nasync function appendJournal(rows: JournalRow[]): Promise {\n const blob = await getBlobModule();\n const existing: JournalRow[] = (await blob.getJSON(\"puppy_journal\").catch(() => null)) ?? [];\n const merged = [...existing, ...rows].slice(-2000);\n if (rows.length) await blob.setJSON(\"puppy_journal\", merged);\n return merged;\n}\n\n// Pure — aggregate the numbers Kim's eventual 30-day report needs. Journal-derived counts\n// (bookedDuringPath, customersDuringPath, sendsByStep) survive state pruning; state-derived counts\n// reflect the current population.\nfunction buildSummary(\n state: Record,\n journal: JournalRow[],\n lastRun: { at: string; testMode: boolean; sent: number; failed: number; enrolled: number },\n) {\n const byStatus: Record = {};\n for (const s of Object.values(state)) byStatus[s.status] = (byStatus[s.status] ?? 0) + 1;\n const sendsByStep: Record = {};\n let bookedDuringPath = 0;\n let customersDuringPath = 0;\n let pausedForHuman = 0;\n let surgeHolds = 0;\n for (const r of journal) {\n if (r.event === \"sent\") sendsByStep[r.detail] = (sendsByStep[r.detail] ?? 0) + 1;\n else if (r.event === \"advance_status\" && r.detail === \"awaiting_appt_outcome\") bookedDuringPath++;\n else if (r.event === \"hard_exit\" && r.detail === \"became a customer\") customersDuringPath++;\n else if (r.event === \"pause_reply\") pausedForHuman++;\n else if (r.event === \"enrollment_surge_hold\") surgeHolds++;\n }\n return {\n at: lastRun.at,\n v: \"1.2\",\n lastRun,\n activeByStatus: byStatus,\n totalTracked: Object.keys(state).length,\n sendsByStep,\n bookedDuringPath,\n customersDuringPath,\n pausedForHuman,\n surgeHolds,\n };\n}\n\nasync function saveSummary(summary: unknown) {\n const blob = await getBlobModule();\n await blob.setJSON(\"puppy_summary\", summary);\n}\n\n// Pure — v1.1 state hygiene: drop terminal entries untouched for 60+ days. History stays in the\n// journal; the puppy-path-v1 tag still prevents re-enrollment of a pruned contact.\nfunction pruneState(state: Record, nowMs: number): { kept: Record; prunedIds: string[] } {\n const kept: Record = {};\n const prunedIds: string[] = [];\n for (const [id, s] of Object.entries(state)) {\n const stale = TERMINAL_STATUSES.has(s.status) && nowMs - new Date(s.lastCheckedAt).getTime() > 60 * DAY_MS;\n if (stale) prunedIds.push(id);\n else kept[id] = s;\n }\n return { kept, prunedIds };\n}\n\n// Pure — v1.1 enrollment gate (header addendum #1/#2). Given this run's un-enrolled tag matches,\n// decide who enrolls. Over-threshold = bulk-tag accident suspected: enroll nobody, hold until a human\n// clears it (ACKNOWLEDGE_SURGE=true) or the candidate count drops back under the threshold.\nfunction selectEnrollable(\n candidates: T[],\n surgeThreshold: number,\n surgeAcknowledged: boolean,\n): { enroll: T[]; surgeHeld: boolean } {\n if (candidates.length > surgeThreshold && !surgeAcknowledged) {\n return { enroll: [], surgeHeld: true };\n }\n return { enroll: candidates, surgeHeld: false };\n}\n\n// ---- IO layer: GHL reads --------------------------------------------------------------------------\n\nasync function getContact(contactId: string): Promise {\n const r = await j(`${GHL}/contacts/${contactId}`, \"2021-07-28\");\n return r.contact;\n}\n\nasync function getOpenOpportunities(contactId: string): Promise {\n const r = await j(`${GHL}/opportunities/search?location_id=${LOC}&contact_id=${contactId}&limit=10`, \"2021-07-28\");\n return (r.opportunities ?? []).map((o: any) => ({\n id: o.id,\n pipelineId: o.pipelineId,\n pipelineStageId: o.pipelineStageId,\n monetaryValue: o.monetaryValue ?? 0,\n status: o.status,\n }));\n}\n\n// ---- v1.3 (2 Aug 2026) — R19: THE ENROLMENT-SCAN QUOTA FIX -----------------------------\n// (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\nconst EXIT_STAGES = [\n \"fd821b4e-bbe6-44de-b754-fa80e4823616\", // Customer\n \"ae173310-f8b1-4399-acb7-ef1fc03d3697\", // Won - Paid\n \"38826f17-1d0e-4bac-b53e-349b67c2c79d\", // Disqualified\n \"43ea02b4-529b-4063-b638-447414d603d2\", // Free Training Day\n];\n\nasync function fetchExitOppIndex(): Promise | null> {\n const index = new Map();\n try {\n for (const stage of EXIT_STAGES) {\n let after: any = null, afterId: any = null, pages = 0;\n while (pages < 12) { // hard ceiling: a runaway page-walk must never be the thing that breaks a run\n let u = `${GHL}/opportunities/search?location_id=${LOC}&pipeline_id=${MAIN_PIPELINE_ID}` +\n `&pipeline_stage_id=${stage}&limit=100`;\n if (after != null) u += `&startAfter=${after}&startAfterId=${afterId}`;\n const r = await j(u, \"2021-07-28\");\n const ops = r.opportunities ?? [];\n if (!ops.length) break;\n for (const o of ops) {\n if (!o.contactId) continue;\n const fact: OppFact = {\n id: o.id,\n pipelineId: o.pipelineId,\n pipelineStageId: o.pipelineStageId,\n monetaryValue: o.monetaryValue ?? 0,\n status: o.status,\n };\n const prev = index.get(o.contactId);\n if (prev) prev.push(fact); else index.set(o.contactId, [fact]);\n }\n pages++;\n after = r.meta?.startAfter; afterId = r.meta?.startAfterId;\n if (!after) break;\n }\n }\n return index;\n } catch {\n // Fail to null, never to an empty map. An empty map would read as \"nobody is a customer\" and\n // could enrol someone who has already bought — the exact mistake this check exists to prevent.\n // Null makes the caller fall back to the per-contact read it used before.\n return null;\n }\n}\n\n// v1.1 (header addendum #5): the Pup Talk calendar's ±90d window holds ~143 events (measured live\n// 27 Jul); fetching it per contact re-downloaded all of them for every active contact every run.\n// Now: one fetch per run, indexed by contactId, latest non-deleted event per contact.\nasync function fetchPupTalkApptIndex(): Promise> {\n const now = Date.now();\n const windowStart = now - 90 * DAY_MS; // look back far enough to still catch a recently-missed appt\n const windowEnd = now + 90 * DAY_MS;\n const r = await j(\n `${GHL}/calendars/events?locationId=${LOC}&calendarId=${PUP_TALK_CALENDAR_ID}&startTime=${windowStart}&endTime=${windowEnd}`,\n \"2021-04-15\",\n );\n const index = new Map();\n for (const e of r.events ?? []) {\n if (!e.contactId || e.deleted) continue;\n const fact: ApptFact = {\n id: e.id,\n startTime: new Date(e.startTime).getTime(),\n endTime: new Date(e.endTime).getTime(),\n appointmentStatus: e.appointmentStatus,\n deleted: !!e.deleted,\n };\n const prev = index.get(e.contactId);\n if (!prev || fact.startTime > prev.startTime) index.set(e.contactId, fact);\n }\n return index;\n}\n\n// ---- v1.6 R28 (2 Aug 2026) — PER-CHANNEL CONSENT ----------------------------------------------\n// Reads GHL's dndSettings, which is keyed BY CHANNEL, instead of only the top-level dnd boolean.\n// Proven against live data: 0 of 100 sampled contacts had dnd===true, 4 carried dndSettings.\n// `status` is consent; `message` is a delivery diagnostic and must NOT be read as consent.\n// Blocks per channel, never a hard exit. Full rationale in NOTES-v1.4.md.\nfunction readChannelConsent(contact: any): { email: boolean; sms: boolean } {\n const ds = contact?.dndSettings;\n const blocked = (key: string): boolean => {\n const entry = ds?.[key];\n if (!entry) return false; // no per-channel record at all = no per-channel opt-out\n const status = String(entry.status ?? \"\").toLowerCase();\n return status !== \"\" && status !== \"active\";\n };\n return {\n // GHL keys these by channel name. SMS and RCS are both text to the recipient, so either one\n // being switched off means we do not text them.\n sms: blocked(\"SMS\") || blocked(\"RCS\"),\n email: blocked(\"Email\"),\n };\n}\n\n// See header gap #1. Fails closed: any error, or a response shape this code doesn't recognize, is\n// reported as conversationCheckFailed=true — never silently treated as \"no reply.\"\nasync function getReplyStatus(\n contactId: string,\n enteredAtIso: string,\n): Promise<{ hasUnansweredInboundReply: boolean; conversationCheckFailed: boolean; lastOutboundAt: number | null }> {\n // v1.5 R27: lastOutboundAt rides along on the SAME request that rule 5 already makes — the collision\n // guard costs zero extra API calls. It is the conversation's own lastMessageDate, returned only when\n // that last message was outbound; the caller decides whether it was ours.\n let lastOutboundAt: number | null = null;\n try {\n const r = await j(`${GHL}/conversations/search?locationId=${LOC}&contactId=${contactId}&limit=1`, \"2021-07-28\");\n const convo = (r.conversations ?? [])[0];\n if (!convo) return { hasUnansweredInboundReply: false, conversationCheckFailed: false, lastOutboundAt };\n {\n const d = convo.lastMessageDirection ?? convo.direction ?? null;\n const ts = convo.lastMessageDate ?? convo.lastMessageDateTime ?? null;\n if (d === \"outbound\" && ts != null) {\n const n = new Date(ts).getTime();\n if (!Number.isNaN(n)) lastOutboundAt = n;\n }\n }\n // Field name NOT independently proven this session (the 401 blocked confirming it) — tryin\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n const direction = convo.lastMessageDirection ?? convo.direction ?? null;\n if (direction !== \"inbound\" && direction !== \"outbound\") {\n return { hasUnansweredInboundReply: false, conversationCheckFailed: true, lastOutboundAt };\n }\n // v1.4 — R21: Chloe, Ava and 165 workflows all send. A customer replies, an automated outbound\n // lands seconds later, the direction field flips, and the engine reads 'no reply'. unreadCount is\n // the second signal: outbound does NOT clear it, so an unread thread means somebody wrote in and\n // nobody looked — which must block a send whatever the newest message was. See NOTES-v1.4.md.\n\n const unread = Number(convo.unreadCount ?? 0);\n if (direction === \"outbound\") {\n if (unread > 0) {\n return { hasUnansweredInboundReply: true, conversationCheckFailed: false, lastOutboundAt };\n }\n return { hasUnansweredInboundReply: false, conversationCheckFailed: false, lastOutboundAt };\n }\n const lastTsRaw = convo.lastMessageDate ?? convo.lastMessageDateTime ?? convo.dateUpdated ?? null;\n const lastTs = lastTsRaw != null ? new Date(lastTsRaw).getTime() : NaN;\n if (!Number.isNaN(lastTs) && lastTs < new Date(enteredAtIso).getTime()) {\n // Pre-enrollment history — EXCEPT if it is still unread, in which case somebody wrote in and\n // nobody has answered them, which outranks how old it is.\n if (Number(convo.unreadCount ?? 0) > 0) return { hasUnansweredInboundReply: true, conversationCheckFailed: false, lastOutboundAt };\n return { hasUnansweredInboundReply: false, conversationCheckFailed: false, lastOutboundAt };\n }\n return { hasUnansweredInboundReply: true, conversationCheckFailed: false, lastOutboundAt };\n } catch {\n return { hasUnansweredInboundReply: false, conversationCheckFailed: true, lastOutboundAt };\n }\n}\n\n// ---- IO layer: GHL writes (all proven live this session, see PUPPY-PATH-TEST-REPORT.md) -----------\n\n// v1.7 hardening (6 Aug): in practice mode the SENDERS THEMSELVES refuse anyone except the one\n// sanctioned test record, so safety no longer rests only on enrollment scoping upstream. Fails\n// closed: until resolveTestDummy() has run and set this, practice mode can send to nobody at all.\nlet SANCTIONED_TEST_CONTACT: string | null = null;\nfunction assertSendAllowed(contactId: string, channel: string) {\n if (TEST_MODE && contactId !== SANCTIONED_TEST_CONTACT) {\n throw new Error(`practice mode: refusing ${channel} to ${contactId}; only the sanctioned test record may be messaged`);\n }\n}\n\nasync function sendSms(contactId: string, text: string) {\n assertSendAllowed(contactId, \"sms\");\n // Proven shape, copied verbatim from the PupsClub val, which sends real SMS in production today.\n return j(`${GHL}/conversations/messages`, \"2021-04-15\", {\n method: \"POST\",\n body: JSON.stringify({ type: \"SMS\", contactId, message: text }),\n });\n}\n\nasync function sendEmail(contactId: string, subject: string, html: string) {\n assertSendAllowed(contactId, \"email\");\n // Body shape verified live this session (27 Jul 2026, against the sanctioned TEST_MODE dummy contact\n // / aizhigitovamir@gmail.com): {\"type\":\"Email\",\"contactId\",\"subject\",\"html\"} on Version 2021-04-15\n // (same API version as the proven SMS call) returned HTTP 201, {\"msg\":\"Email queued successfully.\",\n // \"messageId\":..., \"emailMessageId\":...}. The spec's own best-guess shape worked on the first\n // attempt — nothing needed adjusting.\n return j(`${GHL}/conversations/messages`, \"2021-04-15\", {\n method: \"POST\",\n body: JSON.stringify({ type: \"Email\", contactId, subject, html }),\n });\n}\n\nasync function addTag(contactId: string, tag: string) {\n // POST /contacts/{id}/tags is additive — verified live this session against the dummy contact (an\n // existing tag survived the call, response's tagsAdded confirmed the new one). Deliberately NOT using\n // /contacts/upsert with a tags array for this — upsert's tag merge-vs-replace behavior was never\n // tested and was not worth risking on a real contact's existing tag set.\n return j(`${GHL}/contacts/${contactId}/tags`, \"2021-07-28\", {\n method: \"POST\",\n body: JSON.stringify({ tags: [tag] }),\n });\n}\n\nasync function createTask(contactId: string, title: string, body: string) {\n // Shape verified live this session against the dummy contact (HTTP 201, then confirmed via the\n // proven GET tasks read). assignedTo deliberately omitted rather than sent as JSON null — no\n // confirmed GHL user id for \"the hire\" exists yet in this engine's scope (same open gap\n // BUILD-CHECKLIST-UI.md already flags for its own tasks) — omitting the key tested clean.\n return j(`${GHL}/contacts/${contactId}/tasks`, \"2021-07-28\", {\n method: \"POST\",\n body: JSON.stringify({ title, body, dueDate: new Date().toISOString(), completed: false }),\n });\n}\n\nasync function resolveTestDummy(): Promise<{ id: string; firstName: string; companyName: string | null }> {\n // TEST_MODE's one sanctioned contact (spec §8). +10000000000 is not a working number in any real\n // numbering plan — chosen specifically so an accidental SMS send during testing cannot reach a real\n // person, while still being a syntactically valid phone value GHL will accept on a contact record.\n const up = await j(`${GHL}/contacts/upsert`, \"2021-07-28\", {\n method: \"POST\",\n body: JSON.stringify({\n locationId: LOC,\n firstName: \"ZZTEST\",\n lastName: \"PuppyPath-Dummy\",\n email: \"aizhigitovamir@gmail.com\",\n phone: \"+10000000000\",\n }),\n });\n const c = up.contact;\n SANCTIONED_TEST_CONTACT = c.id;\n return { id: c.id, firstName: c.firstName, companyName: c.companyName ?? null };\n}\n\n// ---- orchestration: cron() (default export — the val.town entry point) ----------------------------\n\nexport default async function cron() {\n const out: any = {\n ok: true,\n v: \"1.7.1\", // slow track + R27/R28, plus the adversarial-review fixes (stale-appt guard, cancel->resume, monthly dedup, dueCheck)\n\n ts: new Date().toISOString(), // v1.2 — lets the watchdog's staleness check actually work\n testMode: TEST_MODE,\n enrolled: 0,\n sent: 0,\n failed: 0,\n skipped: 0,\n log: [] as string[],\n };\n const journal: JournalRow[] = [];\n const jrow = (contactId: string | null, event: string, detail: string) =>\n journal.push({ ts: new Date().toISOString(), contactId, event, detail, ...(TEST_MODE ? { test: true } : {}) });\n\n // v1.2 — best-effort run lock. Blob storage has no compare-and-swap, so this can't be a perfect\n // mutex, but it shrinks the overlap window (manual trigger colliding with the schedule, or a slow\n // run) from \"the whole run\" to milliseconds. A lock older than RUN_LOCK_TTL_MS is a dead run's\n // leftovers and is ignored.\n const blob = await getBlobModule();\n\n // ---- KILL SWITCH (v1.3). Checked first; fails OPEN. Full note in NOTES-v1.4.md.\n try {\n const kill = await blob.getJSON(\"nurture_kill\").catch(() => null);\n if (kill?.stopped) {\n out.ok = true;\n out.killed = true;\n out.log.push(`STOPPED by kill switch (set ${kill.at ?? \"unknown\"}) — no contact examined this tick`);\n await blob.setJSON(\"puppy_run_state\", out).catch(() => {});\n console.log(\"PUPPYPATH\", JSON.stringify(out));\n return out;\n }\n } catch { /* fail open — see note above */ }\n\n const lock = await blob.getJSON(\"puppy_run_lock\").catch(() => null);\n if (lock?.startedAt && Date.now() - new Date(lock.startedAt).getTime() < RUN_LOCK_TTL_MS) {\n out.log.push(`another run appears active (lock from ${lock.startedAt}) — skipping this tick`);\n console.log(\"PUPPYPATH\", JSON.stringify(out));\n return out;\n }\n await blob.setJSON(\"puppy_run_lock\", { startedAt: new Date().toISOString() }).catch(() => {});\n\n try {\n const state = await loadAllState();\n // v1.2 — existing journal loaded up front: the daily send cap counts today's already-journaled\n // live sends, so the ceiling holds across runs, not just within one.\n const priorJournal: JournalRow[] = (await blob.getJSON(\"puppy_journal\").catch(() => null)) ?? [];\n const todayPrefix = new Date().toISOString().slice(0, 10);\n let sentToday = priorJournal.filter(\n (r) => r.event === \"sent\" && r.ts.slice(0, 10) === todayPrefix && !r.test,\n ).length;\n // v1.1 (addendum #5): one calendar fetch per run, shared by enrollment guard + per-contact facts.\n 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 let skippedNotDue = 0; // v1.4 — how many contacts cost zero API calls this run\n\n // v1.9 — THE DRY TAGGING PASS. Runs in BOTH modes on purpose; applies nothing, ever.\n // Full note, including why it was dead for three deploys: NOTES-v1.4.md, \"the dry tagging pass\".\n try {\n const recent = await j(`${GHL}/contacts/?locationId=${LOC}&limit=100`, \"2021-07-28\");\n await blob.setJSON(\"tag_candidates\", dryScan(recent?.contacts ?? [], new Date().toISOString()));\n } catch { /* a dry scan is never worth failing a run over */ }\n\n if (TEST_MODE) {\n // Spec §8: skip real discovery entirely, operate ONLY on the one sanctioned dummy.\n const dummy = await resolveTestDummy();\n contactIds = [dummy.id];\n if (!state[dummy.id]) {\n state[dummy.id] = freshState(new Date().toISOString());\n await addTag(dummy.id, TAG_ENROLLED).catch((e) =>\n out.log.push(`tag failed on dummy: ${String(e).slice(0, 120)}`)\n );\n out.enrolled++;\n out.log.push(`TEST_MODE: enrolled dummy ${dummy.id}`);\n jrow(dummy.id, \"enrolled\", \"test dummy\");\n }\n } else {\n // v1.1 enrollment: the source tag is the HUMAN enrollment switch. Blocks only what makes\n // enrollment WRONG (existing customer, live booking). DND enforced by rule 1 first pass.\n // Surge hold guards bulk tagging — selectEnrollable. Full note: NOTES-v1.4.md.\n const found = await j(`${GHL}/contacts/search`, \"2021-07-28\", {\n method: \"POST\",\n body: JSON.stringify({\n locationId: LOC,\n pageLimit: 100,\n filters: [{ field: \"tags\", operator: \"contains_set\", value: [TAG_SOURCE_SIGNAL] }],\n }),\n });\n // v1.2 — surface pagination truncation instead of silently ignoring candidates beyond page 1\n // (only reachable when a human pushes a >100 bulk batch through with ACKNOWLEDGE_SURGE).\n const totalTagged = found.total ?? (found.contacts ?? []).length;\n if (totalTagged > (found.contacts ?? []).length) {\n out.log.push(\n `WARNING: ${totalTagged} contacts carry '${TAG_SOURCE_SIGNAL}' but only ${(found.contacts ?? []).length} ` +\n `fit one page — the rest enroll on later runs as earlier ones get the puppy-path-v1 tag`,\n );\n }\n const rawCandidates: any[] = (found.contacts ?? []).filter(\n (c: any) => !(c.tags ?? []).includes(TAG_ENROLLED) && !state[c.id],\n );\n const surgeThreshold = enrollSurgeThreshold();\n const { enroll, surgeHeld } = selectEnrollable(rawCandidates, surgeThreshold, acknowledgeSurge());\n if (surgeHeld) {\n out.log.push(\n `ENROLLMENT SURGE HELD: ${rawCandidates.length} un-enrolled '${TAG_SOURCE_SIGNAL}' contacts found in one run ` +\n `(threshold ${surgeThreshold}) — bulk tagging suspected, enrolling NOBODY until a human clears it ` +\n `(remove the bulk tags, or set ACKNOWLEDGE_SURGE=true). Already-enrolled contacts continue normally.`,\n );\n jrow(null, \"enrollment_surge_hold\", `${rawCandidates.length} candidates vs threshold ${surgeThreshold}`);\n }\n // v1.3 / R19 — one indexed read for the whole candidate set instead of one call each.\n const exitOppIndex = enroll.length ? await fetchExitOppIndex() : null;\n if (enroll.length) {\n out.log.push(\n exitOppIndex\n ? `exit-opp index built (${exitOppIndex.size} contacts across ${EXIT_STAGES.length} stages) — ${enroll.length} candidate(s) screened without per-contact calls`\n : `exit-opp index unavailable — falling back to per-contact reads for ${enroll.length} candidate(s)`,\n );\n }\n for (const c of enroll) {\n let opps: OppFact[];\n if (exitOppIndex) {\n opps = exitOppIndex.get(c.id) ?? [];\n } else {\n await sleep(120); // v1.2 — pacing: GHL fails 401/403 (not 429) over 100 req/10s\n opps = await getOpenOpportunities(c.id);\n }\n oppsCache.set(c.id, opps);\n // Across ALL opportunities, not just primary — spec's \"no opportunity showing Customer/Won-Paid\"\n // reading, and the account's own one-opportunity-per-contact rule makes this a cheap superset.\n const alreadyCustomer = opps.some(\n (o) => o.pipelineStageId === STAGE.CUSTOMER || o.pipelineStageId === STAGE.WON_PAID || o.monetaryValue > 0,\n );\n if (alreadyCustomer) {\n out.log.push(`${c.id}: tagged but already a customer — not enrolled`);\n jrow(c.id, \"enroll_refused\", \"already a customer\");\n continue;\n }\n const appt = apptIndex.get(c.id) ?? null;\n if (appt && apptIsLiveBooked(appt)) {\n out.log.push(`${c.id}: tagged but already has a live Pup Talk booking — not enrolled`);\n jrow(c.id, \"enroll_refused\", \"live booking already exists\");\n continue;\n }\n state[c.id] = freshState(new Date().toISOString());\n await addTag(c.id, TAG_ENROLLED).catch((e) => out.log.push(`tag failed on ${c.id}: ${String(e).slice(0, 120)}`));\n out.enrolled++;\n out.log.push(`enrolled ${c.id}`);\n jrow(c.id, \"enrolled\", `via tag '${TAG_SOURCE_SIGNAL}'`);\n }\n contactIds = Object.keys(state);\n }\n\n for (const contactId of contactIds) {\n const s = state[contactId];\n if (!s || TERMINAL_STATUSES.has(s.status)) continue;\n\n // v1.2 — paused_reply contacts get a LIGHTWEIGHT safety pass instead of v1.1's full skip.\n // (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\n if (s.status === \"paused_reply\") {\n // v1.4 — R22: paused_reply was absorbing, so the most engaged leads became the ones nothing\n // happened to. After PAUSE_TIMEOUT_DAYS: raise a SECOND task saying so, then release them.\n // Deliberately does not resume — a person got no answer; the fix is a person. NOTES-v1.4.md.\n\n const pausedSince = s.pausedForReplyAt ? new Date(s.pausedForReplyAt).getTime() : null;\n if (pausedSince && Date.now() - pausedSince > pauseTimeoutDays() * DAY_MS) {\n const days = Math.floor((Date.now() - pausedSince) / DAY_MS);\n try {\n if (!TEST_MODE) {\n await createTask(\n contactId,\n `Still waiting on us — replied ${days} days ago, nobody has answered`,\n `This person replied to a follow-up message ${days} days ago. The sequence stopped for them at the time and raised a task, and that task has not been actioned.\\n\\nOpen Conversations, read what they said, and answer it. They are being taken off the automated follow-up either way — they asked a person a question and they deserve a person's answer.`,\n );\n }\n } catch (e) {\n out.log.push(`${contactId}: pause-timeout task failed: ${String(e).slice(0, 100)}`);\n }\n state[contactId] = {\n ...s,\n status: \"done_hard_exit\",\n exitReason: `paused for ${days} days with no human response — escalated and released`,\n lastCheckedAt: new Date().toISOString(),\n };\n out.log.push(`${contactId}: paused ${days}d with no action — escalated, exited`);\n jrow(contactId, \"pause_timeout\", `${days} days unanswered`);\n continue;\n }\n try {\n await sleep(120);\n const contact = await getContact(contactId);\n if (!contact) continue;\n const opportunities = oppsCache.get(contactId) ?? (await getOpenOpportunities(contactId));\n const facts: Facts = {\n now: Date.now(),\n contact: { id: contactId, firstName: contact.firstName ?? \"\", companyName: contact.companyName ?? null, dnd: !!contact.dnd },\n opportunities,\n pupTalkAppt: apptIndex.get(contactId) ?? null,\n declinedSignal: (contact.tags ?? []).includes(PUP_TALK_DECLINED_TAG),\n hasUnansweredInboundReply: false,\n conversationCheckFailed: true, // pinned: no send can ever pass rule 5 on this pass\n channelBlocked: readChannelConsent(contact),\n foreignOutboundAt: null, // no conversation was fetched on this path; rule 5 blocks sends anyway\n };\n const d = decideAction(facts, s);\n const nowIso = new Date().toISOString();\n if (d.kind === \"hard_exit\") {\n const v = pickPrimaryOpportunity(opportunities)?.monetaryValue ?? 0;\n state[contactId] = { ...applyDecision(d, s, nowIso), exitValue: v, exitStepsSent: s.lastMainStepSent + s.lastBranchStepSent + (s.lastSlowStepSent ?? 0) };\n out.log.push(`${contactId}: paused contact hard-exited -> ${d.status} (${d.reason})`);\n jrow(contactId, \"hard_exit\", `${d.reason}${v ? ` | value ${v}` : \"\"}`);\n } else {\n state[contactId] = { ...s, lastCheckedAt: nowIso };\n }\n } catch (err) {\n out.log.push(`${contactId}: paused-pass FAILED: ${String(err).slice(0, 120)}`);\n }\n continue;\n }\n\n // v1.4 — R19b DUE-FIRST FILTERING: if nothing is due, no send can happen, so ask the CRM\n // nothing about this contact. O(due), not O(enrolled). Full reasoning in NOTES-v1.4.md.\n // Two safety valves: SAFETY_SWEEP_HOURS forces a full check daily regardless; any status this\n // shortcut does not model falls through to the full check. Cheap must not mean blind.\n\n const dueCheck = (() => {\n try {\n if (s.status === \"main\") {\n if (s.lastMainStepSent >= MAIN_SEQUENCE.length) return { due: true, why: \"sequence complete, needs exit evaluation\" };\n const next = MAIN_SEQUENCE[s.lastMainStepSent];\n if (isDue(next.offsetHours, s.enteredAt, Date.now())) return { due: true, why: `main step ${s.lastMainStepSent + 1} due` };\n return { due: false, why: `main step ${s.lastMainStepSent + 1} not due yet` };\n }\n if ((s.status === \"branch_a\" || s.status === \"branch_b\") && s.branchAnchorAt) {\n const seq = s.status === \"branch_a\" ? BRANCH_A : BRANCH_B;\n if (s.lastBranchStepSent >= seq.length) return { due: true, why: \"branch complete, needs exit evaluation\" };\n const next = seq[s.lastBranchStepSent];\n if (isDue(next.offsetHours, s.branchAnchorAt, Date.now())) return { due: true, why: \"branch step due\" };\n return { due: false, why: \"branch step not due yet\" };\n }\n // v1.7.1 — slow_track modelled too: the taper population only grows (non-terminal by\n // design), and without this every taper contact cost a full 3-call CRM check every 15\n // minutes for months of \"not due yet\". The daily safety sweep still catches exits.\n if (s.status === \"slow_track\") {\n const c = Math.max(0, Math.floor(Number(s.lastSlowStepSent)) || 0);\n if (isDue(nextSlowTouch(c).offsetHours, s.slowAnchorAt ?? s.enteredAt, Date.now())) return { due: true, why: `slow touch ${c + 1} due` };\n return { due: false, why: `slow touch ${c + 1} not due yet` };\n }\n return { due: true, why: \"status not modelled by the shortcut — full check\" };\n } catch {\n return { due: true, why: \"due-check threw — full check\" };\n }\n })();\n\n const lastChecked = s.lastCheckedAt ? new Date(s.lastCheckedAt).getTime() : 0;\n const sweepOverdue = Date.now() - lastChecked > safetySweepHours() * HOUR_MS;\n\n if (!dueCheck.due && !sweepOverdue) {\n state[contactId] = { ...s, lastCheckedAt: s.lastCheckedAt };\n out.skipped++;\n skippedNotDue++;\n continue; // zero API calls for this contact this run\n }\n\n try {\n await sleep(120); // v1.2 — pacing between contacts (GHL: 100 req/10s, breach = 401/403 not 429)\n const contact = await getContact(contactId);\n if (!contact) {\n out.log.push(`${contactId}: contact not found, skipping`);\n continue;\n }\n const opportunities = oppsCache.get(contactId) ?? (await getOpenOpportunities(contactId));\n const pupTalkAppt = apptIndex.get(contactId) ?? null;\n const declinedSignal = (contact.tags ?? []).includes(PUP_TALK_DECLINED_TAG);\n const reply = await getReplyStatus(contactId, s.enteredAt);\n\n const facts: Facts = {\n now: Date.now(),\n contact: {\n id: contactId,\n firstName: contact.firstName ?? \"\",\n companyName: contact.companyName ?? null,\n dnd: !!contact.dnd,\n },\n opportunities,\n pupTalkAppt,\n declinedSignal,\n hasUnansweredInboundReply: reply.hasUnansweredInboundReply,\n conversationCheckFailed: reply.conversationCheckFailed,\n // v1.5 R27 — was that last outbound ours or somebody else's? Ours iff it lands within\n // OURS_TOLERANCE_MS of our own recorded send. No lastSentAt yet (nothing sent to this\n // contact) means any outbound on the thread is definitionally foreign.\n channelBlocked: readChannelConsent(contact),\n foreignOutboundAt: (() => {\n const lo = reply.lastOutboundAt;\n if (lo == null) return null;\n if (!s.lastSentAt) return lo;\n const ours = new Date(s.lastSentAt).getTime();\n if (Number.isNaN(ours)) return lo;\n return Math.abs(lo - ours) <= OURS_TOLERANCE_MS ? null : lo;\n })(),\n };\n\n const decision = decideAction(facts, s);\n const nowIso = new Date().toISOString();\n\n switch (decision.kind) {\n case \"hard_exit\": {\n // v1.4 — R24: capture what this exit was worth, at the only moment the number is knowable.\n const exitVal = pickPrimaryOpportunity(opportunities)?.monetaryValue ?? 0;\n const stepsSent = s.lastMainStepSent + s.lastBranchStepSent + (s.lastSlowStepSent ?? 0);\n state[contactId] = {\n ...applyDecision(decision, s, nowIso),\n exitValue: exitVal,\n exitStepsSent: stepsSent,\n };\n out.log.push(`${contactId}: hard exit -> ${decision.status} (${decision.reason})${exitVal ? ` | value ${exitVal}` : \"\"}`);\n jrow(contactId, \"hard_exit\", `${decision.reason}${exitVal ? ` | value ${exitVal} after ${stepsSent} message(s)` : \"\"}`);\n break;\n }\n\n case \"pause_reply\":\n state[contactId] = applyDecision(decision, s, nowIso);\n if (decision.isNewPause) {\n jrow(contactId, \"pause_reply\", \"inbound reply detected — handed to a human\");\n const title = `Reply from ${facts.contact.firstName || \"contact\"} re: puppy path — read and respond personally`;\n try {\n await createTask(\n contactId,\n title,\n \"Auto-created by puppy-path-engine: an inbound reply was detected; the sequence is paused for this contact until a human responds.\",\n );\n out.log.push(`${contactId}: paused (new reply), task created`);\n } catch (e) {\n out.log.push(`${contactId}: paused (new reply), TASK CREATE FAILED: ${String(e).slice(0, 120)}`);\n }\n } else {\n out.log.push(`${contactId}: still paused (reply already flagged, no duplicate task)`);\n }\n break;\n\n case \"advance_status\":\n state[contactId] = applyDecision(decision, s, nowIso);\n out.log.push(`${contactId}: advanced -> ${decision.status}`);\n // \"awaiting_appt_outcome\" here means: they booked a Pup Talk while in the sequence —\n // the attributable event the summary counts as bookedDuringPath.\n jrow(contactId, \"advance_status\", decision.status);\n break;\n\n case \"soft_exit_21d\":\n state[contactId] = applyDecision(decision, s, nowIso);\n try {\n await createTask(\n contactId,\n `Puppy path finished for ${facts.contact.firstName || \"contact\"} — now on the slow track`,\n `Puppy path finished for ${facts.contact.firstName || \"contact\"}, no reply/booking. They are now on the slow track (occasional helpful messages: weekly for a month, then fortnightly, then monthly — no sales asks). Nothing needed unless you want them moved in the pipeline too; the stage was NOT auto-moved — that's Kim's call.`,\n );\n } catch (e) {\n out.log.push(`${contactId}: soft-exit task FAILED: ${String(e).slice(0, 120)}`);\n }\n out.log.push(`${contactId}: 21d complete — moved to slow track (stage NOT moved)`);\n jrow(contactId, \"soft_exit_21d\", \"21-day sequence complete — moved to slow track\");\n break;\n\n case \"branch_complete\":\n state[contactId] = applyDecision(decision, s, nowIso);\n out.log.push(`${contactId}: branch complete`);\n jrow(contactId, \"branch_complete\", s.status);\n break;\n\n case \"send\": {\n // v1.2 — blast ceilings (mirrors the PupsClub val's precedent). A capped send is a pure\n // deferral: state untouched, the step stays due, later runs drain the backlog gradually.\n if (out.sent >= maxSendsPerRun()) {\n out.skipped++;\n out.log.push(`${contactId}: send due but MAX_SENDS_PER_RUN (${maxSendsPerRun()}) reached — deferred`);\n break;\n }\n if (!TEST_MODE && sentToday >= maxSendsPerDay()) {\n out.skipped++;\n out.log.push(`${contactId}: send due but MAX_SENDS_PER_DAY (${maxSendsPerDay()}) reached — deferred to tomorrow`);\n break;\n }\n const step = decision.sequence === \"slow\"\n ? slowTemplateAt(decision.stepIndex, Date.now(), s.lastSentStepId).tpl\n : (decision.sequence === \"main\" ? MAIN_SEQUENCE : decision.sequence === \"branch_a\" ? BRANCH_A : BRANCH_B)[decision.stepIndex];\n // v1.7.1 — consent re-checked against the template actually being sent: a monthly\n // re-resolution at the UTC month boundary can flip template (and channel) between\n // decision and execution; an opted-out channel must win that race.\n if (decision.sequence === \"slow\" && facts.channelBlocked[step.channel]) {\n out.skipped++;\n out.log.push(`${contactId}: slow step resolved to opted-out ${step.channel} at send time — skipped, not consumed`);\n break;\n }\n const rendered = renderStep(\n step,\n { firstName: facts.contact.firstName, companyName: facts.contact.companyName },\n { testMode: TEST_MODE },\n );\n try {\n if (rendered.channel === \"sms\") {\n await sendSms(contactId, rendered.text);\n } else {\n await sendEmail(contactId, rendered.subject, rendered.html);\n }\n // v1.2 — state persisted IMMEDIATELY after each successful send (a mid-run crash\n // must never re-send). Non-send transitions recompute idempotently. NOTES-v1.4.md.\n state[contactId] = applyDecision(decision, s, nowIso);\n await saveAllState(state).catch((e) =>\n out.log.push(`${contactId}: sent OK but state persist failed (will retry at end): ${String(e).slice(0, 100)}`),\n );\n // v1.4 — R23: position is an array index, so inserting a message re-points everyone\n // mid-sequence with no signal. Recording the step ID makes that drift DETECTABLE.\n\n // v1.7 — slow records template id; R23 drift check stays main-only (slow's monthly\n // index-to-id mapping varies by design).\n const seqNow = decision.sequence === \"main\" ? MAIN_SEQUENCE : decision.sequence === \"branch_a\" ? BRANCH_A : decision.sequence === \"branch_b\" ? BRANCH_B : null;\n const sentStepId = decision.sequence === \"slow\" ? step.id : (seqNow?.[decision.stepIndex]?.id ?? null);\n if (s.lastSentStepId && sentStepId && seqNow) {\n const prevIdx = seqNow.findIndex((x) => x.id === s.lastSentStepId);\n if (prevIdx >= 0 && prevIdx !== decision.stepIndex - 1 && decision.sequence === \"main\") {\n out.log.push(`${contactId}: SEQUENCE DRIFT — last sent ${s.lastSentStepId} now sits at index ${prevIdx}, expected ${decision.stepIndex - 1}. The copy has been edited underneath in-flight contacts.`);\n jrow(contactId, \"sequence_drift\", `${s.lastSentStepId} -> index ${prevIdx}`);\n }\n }\n state[contactId] = { ...state[contactId], lastSentStepId: sentStepId };\n out.sent++;\n if (!TEST_MODE) sentToday++;\n out.log.push(`${contactId}: sent ${decision.sequence} step ${decision.stepIndex + 1} (${rendered.channel})`);\n jrow(contactId, \"sent\", `${decision.sequence}#${decision.stepIndex + 1} (${rendered.channel === \"sms\" ? \"text\" : \"email\"})`);\n } catch (e) {\n out.failed++;\n out.log.push(`${contactId}: SEND FAILED ${decision.sequence} step ${decision.stepIndex + 1}: ${String(e).slice(0, 120)}`);\n jrow(contactId, \"send_failed\", `${decision.sequence}#${decision.stepIndex + 1}: ${String(e).slice(0, 80)}`);\n }\n break;\n }\n\n case \"skip_step\":\n // v1.6 R28 — the contact has opted out of this step's channel. The step is consumed so\n // the sequence carries on to the next one it IS allowed to send, rather than stalling.\n // Journalled explicitly: a message that silently never went out is exactly the kind of\n // thing nobody notices until a customer asks why they never heard back.\n state[contactId] = applyDecision(decision, s, nowIso);\n out.skipped++;\n out.log.push(`${contactId}: ${decision.reason}`);\n jrow(contactId, \"skip_step_channel_optout\", decision.reason);\n break;\n\n case \"skip\":\n // Still runs through applyDecision (a no-op on every field except lastCheckedAt) so \"last\n // time this contact was actually looked at\" stays accurate per spec §4's schema comment,\n // even on a run where nothing else changed for them.\n state[contactId] = applyDecision(decision, s, nowIso);\n out.skipped++;\n break;\n }\n } catch (err) {\n out.failed++;\n out.log.push(`${contactId}: FAILED: ${String(err).slice(0, 150)}`);\n // v1.4 — this catch used to write to out.log only, and out.log is not persisted to the\n // journal. So a contact failing here was invisible to the dashboard, which reads the journal.\n // Every failure now leaves a row.\n jrow(contactId, \"contact_failed\", String(err).slice(0, 100));\n }\n }\n\n // v1.1: prune stale terminal entries (their history lives on in the journal), persist everything,\n // then rebuild the aggregate summary from full journal + surviving state.\n out.skippedNotDue = skippedNotDue;\n if (skippedNotDue) out.log.push(`${skippedNotDue} contact(s) not due — zero API calls spent on them`);\n const { kept, prunedIds } = pruneState(state, Date.now());\n for (const id of prunedIds) jrow(id, \"pruned\", \"terminal 60+ days, removed from state (journal retains history)\");\n if (prunedIds.length) out.log.push(`pruned ${prunedIds.length} stale terminal entries`);\n await saveAllState(kept);\n const fullJournal = await appendJournal(journal);\n await saveSummary(\n buildSummary(kept, fullJournal, {\n at: new Date().toISOString(),\n testMode: TEST_MODE,\n sent: out.sent,\n failed: out.failed,\n enrolled: out.enrolled,\n }),\n ).catch((e) => out.log.push(`summary save failed: ${String(e).slice(0, 100)}`));\n await saveReport(out);\n await blob.setJSON(\"puppy_run_lock\", { startedAt: null }).catch(() => {}); // release lock\n // Holiday deposits: once an hour, LAST, fully caught, read-only. Why it hangs off this\n // schedule rather than its own file is in NOTES-v1.4.md under \"deposit refresh\".\n try {\n const dep = await import(\"./deposits.ts\");\n const last: any = await blob.getJSON(dep.ATTEMPT_KEY).catch(() => null);\n if (dep.needsRefresh(last?.at, Date.now())) await dep.runCollection();\n } catch (e) { console.log(\"deposits refresh skipped\", String(e).slice(0, 120)); }\n console.log(\"PUPPYPATH\", JSON.stringify(out));\n return out;\n } catch (err) {\n out.ok = false;\n out.error = String(err);\n await saveLastError({ at: new Date().toISOString(), error: String(err) }).catch(() => {});\n // v1.2 — even on a crashed run, persist whatever state mutations happened before the crash\n // (sends already persisted individually; this catches transitions) and the journal rows.\n await saveReport(out).catch(() => {});\n await appendJournal(journal).catch(() => {});\n await blob.setJSON(\"puppy_run_lock\", { startedAt: null }).catch(() => {});\n console.log(\"PUPPYPATH\", JSON.stringify(out));\n return out;\n }\n}\n\n// ---- booking-link shortener (spec §7) --------------------------------------------------\n// (full note moved to NOTES-v1.4.md when this file hit val.town's 80,000-char ceiling)\nexport async function bookingRedirect(_req: Request): Promise {\n return Response.redirect(REAL_BOOKING_URL, 302);\n}\n\n// ---- exports for the local test harness (puppy-path-engine.test.ts) -------------------------------\n\nexport {\n decideAction,\n applyDecision,\n renderStep,\n resolveDogName,\n resolveFirstName,\n applyMergeFields,\n isDue,\n freshState,\n pickPrimaryOpportunity,\n apptIsLiveBooked,\n bodyToHtml,\n // v1.1 pure additions\n businessLocalParts,\n inSendWindow,\n selectEnrollable,\n buildSummary,\n pruneState,\n MAIN_SEQUENCE,\n BRANCH_A,\n BRANCH_B,\n STAGE,\n MAIN_PIPELINE_ID,\n TAG_ENROLLED,\n TAG_SOURCE_SIGNAL,\n PUP_TALK_DECLINED_TAG,\n PHONE_DISPLAY,\n REAL_BOOKING_URL,\n SHORT_BOOKING_LINK,\n TERMINAL_STATUSES,\n DAY_MS,\n HOUR_MS,\n TEST_MODE,\n // v1.7 — slow track\n slowTemplateAt,\n nextSlowTouch,\n monthlyTemplateFor,\n};\n// v1.8 — story machinery + taper banks re-exported for the offline harness\nexport { STORY_SLOTS, resolveStories, storyFor } from \"./kim-stories.ts\";\nexport { SLOW_WEEKLY, SLOW_FORTNIGHTLY, SLOW_MONTHLY_BANK } from \"./taper-messages.ts\";\nexport type { PuppyState, PuppyStatus, Facts, Decision, ContactFact, OppFact, ApptFact, MessageTemplate, RenderedMessage };\n",[245],"245ad811-33e0-43df-8360-236ebfb6905e","kim-stories.ts","789b1fbc-901e-11f1-980a-1607ee4eb77e",129,["D",1785901696927],"// KIM'S STORIES — the one file that makes the taper personal. v1.8, 4 Aug 2026.\n//\n// THE RULE THIS FILE EXISTS TO ENFORCE: no invented stories, ever. No fictional dogs, no\n// composite customers, no \"a client once told me\". Every `story` below starts as null and stays\n// null until KIM'S OWN WORDS go in. The copy is written to read complete without them — an\n// empty slot renders as nothing, not as a hole.\n//\n// HOW TO FILL ONE IN (the whole procedure, ~5 minutes):\n// 1. Kim answers a question from the Story Capture Sheet (handover/Story-Capture-Sheet.pdf).\n// 2. Paste her answer, lightly tidied but in her words, as the `story` string below.\n// Keep it to 2-4 sentences. First person. No customer surnames without her okay.\n// 3. PUT this one file to the val (same deploy command as always). Nothing else changes.\n// 4. The next send that hits that slot carries her story. Practice mode renders it too,\n// so it can be checked on the panel/journal before anyone real sees it.\n//\n// Slots are ADDITIVE paragraphs: the template holds {{STORY:id}} on its own line; the renderer\n// swaps in the story, or removes the line entirely when null. Both paths are tested.\n\nexport type StorySlot = {\n id: string;\n // The question that gets a usable answer from Kim in 30 seconds — printed on the capture sheet.\n prompt: string;\n // Where it lands, so a human editing this file knows the context without opening the copy file.\n lands: string;\n // Kim's words, or null. Null = the message sends without it and reads complete.\n story: string | null;\n};\n\nexport const STORY_SLOTS: StorySlot[] = [\n {\n id: \"teenage\",\n prompt: \"Name one dog who turned into a teenage terror around 8 months and came good. What did the owner stick with?\",\n lands: \"Slow track week 1 — the adolescence email\",\n story: null,\n },\n {\n id: \"alone_time\",\n prompt: \"Tell me about one dog who couldn't be left alone at first. What actually fixed it?\",\n lands: \"Slow track day 63 — the alone-time email\",\n story: null,\n },\n {\n id: \"vet_visits\",\n prompt: \"Which dog do you know who walks into the vet happy? What did their owner do differently?\",\n lands: \"Slow track day 70 — the vet visits email\",\n story: null,\n },\n {\n id: \"settle\",\n prompt: \"One dog you can picture lying calmly somewhere busy (a patio, a game, a store). How did they get there?\",\n lands: \"Slow track day 119 — the off-switch email\",\n story: null,\n },\n {\n id: \"dog_parks\",\n prompt: \"One thing you've seen go wrong at a dog park that the owner never noticed. What should they have seen?\",\n lands: \"Slow track day 147 — the dog parks email\",\n story: null,\n },\n {\n id: \"nose_work\",\n prompt: \"Name a dog who was 'bad' until they got a job to do. What was the job?\",\n lands: \"Slow track day 175 — the boredom email\",\n story: null,\n },\n {\n id: \"leash_meetings\",\n prompt: \"Which pair of dogs hated each other on leash but got along fine off it, or walking side by side?\",\n lands: \"Slow track day 203 — the leash meetings email\",\n story: null,\n },\n {\n id: \"holidays\",\n prompt: \"What's one thing that happens at the kennel every Thanksgiving or Christmas that owners would never guess?\",\n lands: \"Monthly November — the holiday guests email\",\n story: null,\n },\n];\n\nconst byId = new Map(STORY_SLOTS.map((s) => [s.id, s]));\n\n// Anything SHAPED like a slot token but not a slot we know: an empty id `{{STORY:}}`, a spaced id\n// `{{STORY: a b }}`, the residue a nested token leaves behind after its inner half resolves. None of\n// these is a slot, so none of them is content. They get removed, never shipped.\n// [was: a single pass matching only /\\{\\{STORY:[a-z_]+\\}\\}/, which left `{{STORY:}}` standing\n// after resolving the inner token of `{{STORY:{{STORY:x}}}}`. Caught by tests/stories.test.mjs S5.]\nconst TOKEN_SHAPE = /\\{\\{STORY:[^{}]*\\}\\}/g;\n// Last line of defence: even a half-token fragment must not reach a customer.\nconst TOKEN_FRAGMENT = /\\{\\{STORY:[^}]*\\}{0,2}/g;\n\n// story text, or null. Trims whitespace so a pasted answer can't break the layout.\nexport function storyFor(id: string): string | null {\n const s = byId.get(id)?.story;\n if (!s) return null;\n // A pasted answer can't smuggle a slot token back in (single-pass resolve would ship it raw).\n const t = s.replace(TOKEN_FRAGMENT, \"\").trim();\n return t.length ? t : null;\n}\n\n// Resolve every {{STORY:id}} token in a rendered body. Unknown ids resolve to nothing rather\n// than leaking a token to a customer — and the tests assert every id used in copy exists here.\n//\n// Resolution LOOPS rather than running once. One pass is not enough: a malformed nest only reveals\n// its outer token after the inner one is gone, and a filled story sitting next to a token can shift\n// what the next match sees. The loop is bounded (a pass that changes nothing stops it), so a\n// pathological input costs a few passes rather than hanging.\nexport function resolveStories(text: string): string {\n let out = String(text ?? \"\");\n for (let pass = 0; pass < 8 && out.includes(\"{{STORY:\"); pass++) {\n const before = out;\n out = out.replace(/\\{\\{STORY:([a-z_]+)\\}\\}/g, (_, id) => storyFor(id) ?? \"\");\n out = out.replace(TOKEN_SHAPE, \"\");\n if (out === before) break;\n }\n // Whatever survived the loop is not a slot and is not content.\n out = out.replace(TOKEN_FRAGMENT, \"\");\n return out.replace(/\\n{3,}/g, \"\\n\\n\").trim();\n}\n",[254],"f00b0312-3f9c-4bc1-98bf-a95343478dd2","holiday-deposits.ts","2f043ab0-91ad-11f1-9dc1-1607ee4eb77e",292,["D",1786048291196],12,"// HOLIDAY DEPOSIT TRACKER. v1.0, 6 Aug 2026.\n//\n// WHAT KIM ASKED FOR: she charges a $50 nonrefundable deposit on boarding stays over holidays,\n// and today somebody goes through the bookings by hand to work out who has paid.\n//\n// WHAT THIS CAN AND CANNOT DO, because the difference is the whole honesty of the feature.\n// Square money DOES reach the CRM. It arrives as a note on the contact, like\n// \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\"\n// (verified live on 6 Aug against a real contact). So we can see payments that went through\n// Square. We CANNOT see a deposit handed over in cash or taken over the phone. That means this\n// produces a SHORTLIST TO CHECK, never a list of people who have not paid. The word \"unpaid\"\n// is banned from anything this module renders, and a test enforces that.\n//\n// TWO TRAPS FOUND IN HER REAL DATA, both of which would have made Kim chase the wrong people:\n// 1. The same Square payment is written into the notes FIVE times, and the \"(balance ...)\"\n// figures inside those duplicates contradict each other ($355.00 then $0.00 four times).\n// So: dedupe on the payment id, and never read the balance figure.\n// 2. A recurring weekly slot (\"Daycare Enzo\") lands inside every holiday window. Without a\n// recurring filter Kim would be told a regular customer owes her a holiday deposit eight\n// times over. Recurring bookings are excluded.\n//\n// THIS MODULE WRITES NOTHING. No tag, no custom field, no pipeline stage, no message. That is\n// deliberate and it is tested: addTag() elsewhere in this engine is not TEST_MODE-guarded, and\n// this account contains a workflow (\"Add tag 'red flag' = DND\") which proves a single tag here\n// can silence a real customer on six channels. A read-only report cannot do that.\n\nexport type CalEvent = {\n contactId?: string | null;\n title?: string | null;\n startTime?: string | number | null; // carries its own offset, e.g. \"2026-11-25T09:00:00-05:00\"\n // The pick-up. A stay that starts before a holiday window and runs into it is a holiday stay,\n // and without this the module could only see the drop-off day.\n endTime?: string | number | null;\n dateAdded?: string | null;\n appointmentStatus?: string | null;\n // Her CRM really does return BOTH spellings on the same object: 4 of the 13 events on the\n // Boarding Drop Off calendar carry `appoinmentStatus` alongside the correct one (checked live,\n // 6 Aug 2026). They agree today. Reading only one of them is passing a test by luck.\n appoinmentStatus?: string | null;\n isRecurring?: boolean | null;\n deleted?: boolean | null;\n};\n\n// \"direct\" = \"[Square] +$35.00 payment (balance $x)\" — money arriving\n// \"matched\" = \"[Square] Till payment $35.00 on . Matched from Square payment ...\"\n// — a RECONCILIATION record written by the backfill, carrying its own separate id.\n// Both are real and both are live in her account on the same contact, with the same amount and\n// two different ids. See collapseSameMoney() for why that distinction has to survive parsing.\nexport type Payment = { amount: number; id: string; at: string | null; kind: \"direct\" | \"matched\" };\n\nexport type Stay = {\n contactId: string;\n day: string; // local date of the drop-off, \"YYYY-MM-DD\"\n until: string; // local date of the pick-up; equals `day` when the CRM does not say\n dogs: string[]; // one stay can be several dogs (names, best effort)\n dogCount: number; // how many drop-off rows this stay is, whether or not the names parsed\n bookedAt: string | null;\n window: string; // which holiday it falls in, in Kim's words\n};\n\nexport type StayStatus = {\n stay: Stay;\n state: \"seen\" | \"partial\" | \"none_seen\" | \"could_not_check\";\n amountSeen: number;\n note: string; // the plain-English reason, always populated\n};\n\n/** The fourth Thursday of November. Computed, never typed, so it cannot drift year to year.\n * Kim was told Thanksgiving is handled by working it out fresh each year. This is that. */\nexport function thanksgiving(year: number): string {\n // day 1 of November, then walk to the first Thursday, then add three weeks.\n const first = new Date(Date.UTC(year, 10, 1));\n const dow = first.getUTCDay(); // 0 Sun .. 4 Thu\n const firstThu = 1 + ((4 - dow) + 7) % 7;\n const day = firstThu + 21;\n return `${year}-11-${String(day).padStart(2, \"0\")}`;\n}\n\n/** The windows a deposit applies to, as dates, derived rather than hardcoded.\n * Thanksgiving: the Monday before through the Sunday after.\n * Christmas and New Year: 20 Dec through 2 Jan.\n * If Kim wants different edges these are the only two lines to change. */\nexport function holidayWindows(year: number): { name: string; from: string; to: string }[] {\n const t = thanksgiving(year);\n // [was: String(Number(t.slice(8)) + 3) — decimal arithmetic on the day number. Whenever\n // Thanksgiving falls on the 28th (2030, 2041, ...) that produced \"2030-11-31\", a date that does\n // not exist. Two consequences, both live: a stay dropping off Sunday 1 December sorts ABOVE\n // \"2030-11-31\" in a string compare and vanishes from the window, and the card printed the\n // words \"Thanksgiving (Nov 25 to Nov 31)\" to Kim. Real calendar arithmetic now.]\n return [\n { name: \"Thanksgiving\", from: shiftDays(t, -3), to: shiftDays(t, 3) },\n { name: \"Christmas and New Year\", from: `${year}-12-20`, to: `${year + 1}-01-02` },\n ];\n}\n\n/** The local calendar day of an appointment. startTime carries its own offset, so the first ten\n * characters ARE the local day. Parsing it into a Date and reformatting would shift bookings\n * across midnight into or out of a window, which is how a customer gets chased by mistake.\n *\n * A NUMBER is handled separately and deliberately. Two sibling modules that read this same CRM\n * endpoint already defend against an epoch-millisecond startTime, so the shape is real. Returning\n * null for it would have dropped EVERY stay silently and stored \"no holiday stays are booked\" as\n * a fact, in November, with the kennels full. An epoch has no offset, so it is converted in the\n * business's own timezone rather than in whatever timezone the server happens to be in. */\nexport const BUSINESS_TZ = \"America/New_York\";\nexport function localDay(startTime: string | number | null | undefined): string | null {\n if (typeof startTime === \"number\" && Number.isFinite(startTime)) {\n try {\n const p = new Intl.DateTimeFormat(\"en-CA\", { timeZone: BUSINESS_TZ, year: \"numeric\", month: \"2-digit\", day: \"2-digit\" })\n .format(new Date(startTime));\n return /^\\d{4}-\\d{2}-\\d{2}$/.test(p) ? p : null;\n } catch { return null; }\n }\n if (!startTime || typeof startTime !== \"string\" || startTime.length < 10) return null;\n const d = startTime.slice(0, 10);\n return /^\\d{4}-\\d{2}-\\d{2}$/.test(d) ? d : null;\n}\n\n/** WHICH SEASON ARE WE IN. Passed the local date as \"YYYY-MM-DD\", never reading the clock itself,\n * so this is testable and cannot behave differently on the val than it does here.\n * On 1 January the season that matters is still LAST year's — the New Year window runs to the 2nd,\n * and a page that flips to next Thanksgiving on New Year's Day drops the stays happening that day. */\nexport function businessDay(nowIso: string): string {\n // Her business is in New York. Rolling the season over on the UTC date empties the card at 8pm\n // on 2 January, five hours before the season actually ends, while dogs are still in the kennels\n // — and the empty result then gets stored over the real one.\n try {\n const d = new Date(nowIso);\n if (isNaN(d.getTime())) return String(nowIso).slice(0, 10);\n const p = new Intl.DateTimeFormat(\"en-CA\", { timeZone: BUSINESS_TZ, year: \"numeric\", month: \"2-digit\", day: \"2-digit\" }).format(d);\n return /^\\d{4}-\\d{2}-\\d{2}$/.test(p) ? p : String(nowIso).slice(0, 10);\n } catch { return String(nowIso).slice(0, 10); }\n}\n\nexport function seasonYear(today: string): number {\n const y = Number(today.slice(0, 4));\n const md = today.slice(5, 10);\n return md <= \"01-02\" ? y - 1 : y;\n}\n\nexport function windowFor(day: string | null, windows: { name: string; from: string; to: string }[]): string | null {\n if (!day) return null;\n for (const w of windows) if (day >= w.from && day <= w.to) return w.name;\n return null;\n}\n\n/** A STAY, not a moment. Somebody who drops off on 19 December and collects on 27 December has\n * boarded over Christmas and owes the holiday deposit, but their drop-off day is outside the\n * window. Deciding membership on the drop-off day alone dropped exactly the customers a holiday\n * boarding business has most of: the ones who leave the day before they travel. */\nexport function windowForRange(from: string | null, to: string | null, windows: { name: string; from: string; to: string }[]): string | null {\n if (!from) return null;\n const end = to && to >= from ? to : from;\n for (const w of windows) if (from <= w.to && end >= w.from) return w.name;\n return null;\n}\n\n/** Which bookings count. Cancelled, deleted and recurring are all excluded, and the recurring\n * exclusion is the one that matters most: a standing weekly slot is not a holiday stay. */\nexport function eligible(e: CalEvent): boolean {\n if (!e || truthy(e.deleted)) return false;\n // [was: `e.isRecurring === true`. Her CRM has already been caught shipping the misspelled\n // `appoinmentStatus`, so trusting it to always send a real boolean here is a bet, not a fact.\n // A recurring series returned with isRecurring:\"true\" would have put a weekly daycare regular\n // on the list telling him he owes a boarding deposit.]\n if (truthy(e.isRecurring)) return false;\n // BOTH spellings are read, and either one saying cancelled is enough to drop the booking.\n // The asymmetry is deliberate: dropping a live booking means Kim is not prompted about it and\n // she notices; keeping a cancelled one means she chases a customer who already cancelled, and\n // that one she cannot take back.\n // TRIMMED, because this account demonstrably ships padded strings: \"Daycare Enzo \" and\n // \" Boarding Dropoff with Help Test\" are both real titles out of it. One trailing space on a\n // status was enough to make a cancelled booking eligible.\n const states = [e.appointmentStatus, e.appoinmentStatus].map((s) => String(s ?? \"\").trim().toLowerCase());\n const dead = [\"cancelled\", \"canceled\", \"noshow\", \"no-show\", \"no show\", \"invalid\"];\n if (states.some((s) => dead.includes(s))) return false;\n if (!e.contactId) return false;\n // A DAYCARE slot is not a boarding stay and carries no boarding deposit. Until now the ONLY\n // thing keeping the weekly \"Daycare Enzo\" booking off Kim's list was its recurrence flag; a\n // one-off daycare booking in Christmas week would have been billed a $50 boarding deposit.\n // Narrowed: a title that says BOTH is a boarding booking with a note on it, and excluding\n // \"Boarding + daycare drop off with Dan Bonner\" would lose a real holiday stay.\n const title = String(e.title ?? \"\");\n if (/\\bday\\s?care\\b/i.test(title) && !/\\bboarding\\b/i.test(title)) return false;\n return true;\n}\n\n/** Her CRM's booleans are not reliably booleans. Treats \"true\"/\"TRUE\"/1 the same as true, and\n * anything else, including undefined, as false. */\nfunction truthy(v: unknown): boolean {\n if (v === true || v === 1) return true;\n return typeof v === \"string\" && v.trim().toLowerCase() === \"true\";\n}\n\n/** A dog's name out of \"Achilles — Boarding Drop Off\" style titles, best effort and never fatal. */\nexport function dogFromTitle(title: string | null | undefined): string {\n const t = (title || \"\").trim();\n if (!t) return \"\";\n // [was: split on /[—–-]/, which cut \"Jean-Luc — Boarding Drop Off\" down to \"Jean\". A hyphen\n // inside a name is not a separator; a SPACED hyphen is. Kim reads these names before phoning\n // somebody, so the wrong name here is a wrong conversation.]\n const cut = t.split(/\\s[—–-]\\s|[—–]|\\bBoarding\\b|\\bDrop\\s?off\\b/i)[0];\n return cut.trim().replace(/\\s+with\\s+.*$/i, \"\").trim();\n}\n\n/** WHERE THE END OF A STAY ACTUALLY LIVES. A drop-off appointment in her CRM is a TEN MINUTE\n * slot: \"2026-11-25T12:50 to 2026-11-25T13:00\". Its endTime is the end of the handover, not the\n * end of the boarding. The real length of the stay is on a separate Boarding Pick Up calendar —\n * Ghost and Chewy drop off on 25 November and are collected on the 28th, and only the pick-up\n * calendar says so. Without this, \"did this dog board over Christmas\" could only ever be answered\n * by the drop-off date, and everybody who leaves the day before the holiday starts was invisible.\n * The LATEST eligible pick-up on or after the drop-off wins, bounded by the customer's own next\n * booking and by MAX_STAY_DAYS. */\nexport const MAX_STAY_DAYS = 21;\nexport function attachPickups(stays: Stay[], pickups: CalEvent[]): Stay[] {\n const byContact = new Map();\n for (const p of pickups) {\n if (!eligible(p)) continue;\n const d = localDay(p.startTime);\n if (!d || !p.contactId) continue;\n const list = byContact.get(p.contactId) ?? [];\n list.push(d);\n byContact.set(p.contactId, list);\n }\n for (const list of byContact.values()) list.sort();\n // The customer's OWN next drop-off is the hard upper bound. Without it a stay reaches forward\n // and takes a pick-up belonging to a later booking: a 3-night Thanksgiving stay was rendered\n // \"Nov 25 to Dec 27\", and an ordinary 6 November boarding was dragged into a holiday window and\n // billed a deposit. [was: the EARLIEST pick-up on or after the drop-off, which was wrong the\n // other way — one dog of three going home early cut the stay short and deleted it from the\n // window entirely. Her pick-up calendar really does carry one row per dog.]\n // A stay cannot run forever. Without an upper bound an ORPHAN pick-up — and her account has\n // about twenty contacts with pick-ups and no matching drop-off — drags an out-of-season boarding\n // into a holiday window: a 6 November stay with a stray 1 February pick-up record rendered as\n // \"Nov 6 to Feb 1\" on Kim's shortlist.\n const dropDays = new Map();\n for (const s of stays) {\n const list = dropDays.get(s.contactId) ?? [];\n list.push(s.day);\n dropDays.set(s.contactId, list);\n }\n for (const list of dropDays.values()) list.sort();\n return stays.map((s) => {\n const nextDrop = (dropDays.get(s.contactId) ?? []).find((d) => d > s.day);\n // `<=` on the next drop-off, not `<`: a pick-up on the same day as the customer's next\n // booking is the END of this stay, not part of the next one. With a strict `<`, a customer\n // collecting on 27 December and re-boarding the same day lost their Christmas stay entirely.\n const cands = (byContact.get(s.contactId) ?? []).filter((d) =>\n d >= s.day && d <= shiftDays(s.day, MAX_STAY_DAYS) && (!nextDrop || d <= nextDrop));\n const cand = cands.length ? cands[cands.length - 1] : null;\n return cand && cand > s.until ? { ...s, until: cand } : s;\n });\n}\n\n/** One customer dropping three dogs on the same day is ONE stay and ONE deposit question. */\nexport function groupIntoStays(\n events: CalEvent[],\n windows: { name: string; from: string; to: string }[],\n pickups: CalEvent[] = [],\n): Stay[] {\n const by = new Map();\n for (const e of events) {\n if (!eligible(e)) continue;\n const day = localDay(e.startTime);\n const until = localDay(e.endTime) ?? day;\n if (!day) continue;\n const key = `${e.contactId}|${day}`;\n const dog = dogFromTitle(e.title);\n const existing = by.get(key);\n if (existing) {\n if (dog && !existing.dogs.includes(dog)) existing.dogs.push(dog);\n // COUNTED FROM THE ROWS, not from the names. A title that does not parse still means a dog,\n // and the deposit is charged per dog, so counting parsed names would under-charge.\n existing.dogCount++;\n // the LATEST pick-up across the dogs on this stay\n if (until && until > existing.until) existing.until = until;\n // keep the EARLIEST booking time: that is when the deposit became due\n if (e.dateAdded && (!existing.bookedAt || e.dateAdded < existing.bookedAt)) existing.bookedAt = e.dateAdded;\n } else {\n by.set(key, { contactId: e.contactId!, day, until: until ?? day, dogs: dog ? [dog] : [], dogCount: 1, bookedAt: e.dateAdded ?? null, window: \"\" });\n }\n }\n // Pick-ups are attached BEFORE the window filter, because the whole point is that a stay whose\n // drop-off falls outside a window can still run through it.\n const withEnds = attachPickups([...by.values()], pickups);\n const out: Stay[] = [];\n for (const s of withEnds) {\n const win = windowForRange(s.day, s.until, windows);\n if (win) out.push({ ...s, window: win });\n }\n return out.sort((a, b) => (a.day < b.day ? -1 : a.day > b.day ? 1 : 0));\n}\n\n/** Square payments out of contact notes, DEDUPED BY PAYMENT ID.\n * The same payment appears five times in her real data with contradictory balance figures, so\n * the balance is deliberately not read: only the amount and the payment's own id. */\nexport function parseSquarePayments(notes: { body?: string | null; dateAdded?: string | null }[] | null | undefined): Payment[] {\n const out = new Map();\n // EVERY match in EVERY note, not the first match in each.\n // [was: .exec() on each body, i.e. one payment per note. A note holding two Square lines lost\n // the second one. Every parser gap in this function fails in the same direction — less money\n // seen than was paid — and that direction is the one that puts a paying customer on the list.]\n // The amount tolerates whole dollars (\"+$50 payment\") as well as cents, and the id stops at\n // punctuation so a trailing comma cannot become part of the dedupe key.\n const DIRECT = /\\[Square\\]\\s*\\+?\\$([\\d,]+(?:\\.\\d{2})?)\\s+payment\\s+([A-Za-z0-9_-]+)/gi;\n // Format 2: the reconciliation backfill. It carries the REAL payment date in its own text,\n // which is four days earlier than the note's dateAdded on the live example, so the stated\n // date is used and the note's write time is only the fallback. The trailing punctuation after\n // the id is OPTIONAL: on a note that ENDS at the id the whole payment used to vanish.\n const MATCHED = /\\[Square\\][^[]*?Till payment\\s*\\$([\\d,]+(?:\\.\\d{2})?)\\s*on\\s*(\\d{4}-\\d{2}-\\d{2})[\\s\\S]*?Matched from Square payment\\s+([A-Za-z0-9_-]+)/gi;\n const add = (amount: number, id: string, at: string | null, kind: \"direct\" | \"matched\") => {\n if (!Number.isFinite(amount) || !id) return;\n const prev = out.get(id);\n // keep the earliest sighting of a given payment\n if (!prev || (at && prev.at && at < prev.at)) out.set(id, { amount, id, at, kind });\n else if (!prev.at) out.set(id, { amount, id, at, kind });\n };\n for (const n of notes ?? []) {\n const body = n?.body ?? \"\";\n if (!body) continue;\n for (const m of body.matchAll(MATCHED)) add(Number(m[1].replace(/,/g, \"\")), m[3], m[2], \"matched\");\n for (const m of body.matchAll(DIRECT)) add(Number(m[1].replace(/,/g, \"\")), m[2], n?.dateAdded ?? null, \"direct\");\n }\n return [...out.values()].sort((a, b) => String(a.at).localeCompare(String(b.at)));\n}\n\n/** THE SAME $35, TWICE, UNDER TWO IDS.\n * Live on David Newman's contact right now: \"+$35.00 payment z3rQ...\" and \"Till payment $35.00\n * on 2026-07-17. Matched from Square payment 3zu7...\". Same money or two payments? Nothing in\n * the data settles it, and the two readings disagree about whether a $50 deposit is covered.\n * So the conservative reading wins: a \"Matched from\" record of the same amount as a direct\n * payment is treated as describing that same money. Getting this wrong the other way removes a\n * person from the shortlist, and a person who is not on the shortlist is never looked at. */\n/** A CONTACT THAT LOOKS LIKE SOMEBODY TESTING THE BOOKING FORM. Kim's account holds at least two:\n * a contact literally named \"help test\" with three future boarding bookings, and a tagged\n * \"ZZTEST PuppyPath-Dummy\". This does NOT remove the row — a filter that quietly drops a real\n * customer called Mr Test is worse than a label — it flags it, so Kim knows before she picks up\n * the phone to a stranger about $50. */\nexport function looksLikeTestRecord(name: string | null | undefined): boolean {\n // \"tester\" is deliberately absent: Tester is a real surname, and this label appears on Kim's\n // screen right next to a person's name, immediately before she decides whether to phone them.\n return /\\b(test|testing|dummy|zztest|do not use|ignore)\\b/i.test(String(name ?? \"\"));\n}\n\nexport function collapseSameMoney(payments: Payment[]): { kept: Payment[]; collapsed: number } {\n // IDEMPOTENT, and that is the whole point. [was: one-for-one — each matched record consumed one\n // direct of the same amount, so with TWO matched and ONE direct at $50 the second matched\n // survived, still sharing an amount with the direct. The per-stay check then collapsed it AGAIN\n // and declared them one payment while the allocator had only ever spent one id, leaving the\n // other free to settle the next stay. Two holiday stays settled by one $50, both rows quoting\n // the same date. Collapsing every matched record that shares an amount with any direct makes a\n // second pass a genuine no-op, which is what the layers above assume.]\n const directAmounts = new Set(payments.filter((p) => p.kind === \"direct\").map((p) => p.amount));\n const kept: Payment[] = [];\n let collapsed = 0;\n for (const p of payments) {\n if (p.kind === \"matched\" && directAmounts.has(p.amount)) { collapsed++; continue; }\n kept.push(p);\n }\n return { kept, collapsed };\n}\n\nexport const DEPOSIT = 50;\n\n/** WHAT THIS STAY OWES. Kim's own money page, taken from her live website: \"Holiday boarding —\n * $50 PER DOG, non-refundable. Deducted from the total boarding cost at drop-off.\"\n * [was: a flat $50 per stay, with a line on the card asking Kim to tell us if it was per dog.\n * It is per dog, and it says so in her own handover pack. Jeffrey Musselwhite's three dogs on\n * 25 November owe $150, and a single $50 payment was clearing that whole stay — the silent\n * direction, where somebody who owes $100 more drops off the list and is never looked at.] */\nexport function depositDue(stay: Stay): number {\n return DEPOSIT * Math.max(1, stay.dogCount || stay.dogs.length || 1);\n}\n\n// HOW A PAYMENT IS MATCHED TO A DEPOSIT, and why the answer is \"it mostly is not\".\n//\n// Nothing in her CRM says what a card payment was FOR. Two attempts at guessing have now both\n// been wrong in a way that costs her money:\n// v1 summed every payment between the booking and the drop-off. A $355 training package cleared\n// a $50 deposit, and being cleared means nobody ever looks at that customer again.\n// v2 narrowed it to ten days around the booking and still summed. That missed a real $50 paid\n// eight days later — the page said \"we cannot find a $50 payment\" one line after printing\n// one — and STILL cleared anybody who happened to settle a $240 invoice that same week.\n//\n// So this version stops guessing. It clears a stay on ONE piece of evidence only: a card payment\n// for EXACTLY the deposit amount, in a wide window around the stay. Anything else is shown to Kim\n// with its date and amount and left for her to judge, which takes her about two seconds per row\n// and is the thing she was doing by hand anyway. A wrong \"worth a look\" costs her a glance. A\n// wrong \"settled\" costs her $50 and she never finds out.\n// HOW SHE ACTUALLY GETS PAID, off her own money page: \"Card — at the counter, or through the\n// website's payments page. This is the normal route and THE ONLY ONE THAT MATCHES ITSELF TO A\n// CUSTOMER RECORD AUTOMATICALLY. Venmo — there is a Venmo page on the website. Zelle — sent to an\n// address inside the Zelle app. Cheque — made payable by post.\"\n// [was: \"may still have been paid in cash or over the phone\", which named neither of the two\n// routes she actually offers. Every one of Venmo, Zelle and cheque is invisible here, so naming\n// them is the difference between Kim knowing where to look and Kim assuming non-payment.]\nexport const OTHER_ROUTES = \"A deposit paid by Venmo, Zelle, cheque or cash does not reach the card system, so it will not show here.\";\nexport const NEAR_WINDOW_BEFORE = 30; // a deposit can be taken before the booking is typed in\n\n/** Every card payment close enough to this stay to be worth putting in front of Kim. */\nexport function paymentsNearStay(stay: Stay, payments: Payment[]): Payment[] {\n if (!stay.bookedAt) return [];\n const lo = shiftDays(stay.bookedAt.slice(0, 10), -NEAR_WINDOW_BEFORE);\n const hi = shiftDays(stay.until || stay.day, 1);\n return payments.filter((p) => {\n const d = (p.at || \"\").slice(0, 10);\n return d >= lo && d <= hi;\n });\n}\n\nconst MONTHS = [\"Jan\", \"Feb\", \"Mar\", \"Apr\", \"May\", \"Jun\", \"Jul\", \"Aug\", \"Sep\", \"Oct\", \"Nov\", \"Dec\"];\n/** \"2026-07-21\" -> \"Jul 21\", the same way round as the stay dates on the card. Kim is American and\n * a row that says \"Nov 25 to Nov 28\" beside \"$50.00 on 21 Jul\" makes her read the date twice. */\nexport function prettyDay(iso: string | null | undefined): string {\n const m = /^(\\d{4})-(\\d{2})-(\\d{2})/.exec(String(iso ?? \"\"));\n return m ? `${MONTHS[Number(m[2]) - 1] ?? m[2]} ${Number(m[3])}` : \"\";\n}\nconst listPayments = (ps: Payment[]) =>\n ps.map((p) => `$${p.amount.toFixed(2)} on ${prettyDay(p.at)}`).join(\", \");\n\nexport function shiftDays(day: string, delta: number): string {\n const d = new Date(`${day}T00:00:00Z`);\n if (isNaN(d.getTime())) return day;\n d.setUTCDate(d.getUTCDate() + delta);\n return d.toISOString().slice(0, 10);\n}\n\n/** could_not_check NEVER collapses into none_seen. A failed read must not read as \"she owes\". */\nexport function statusFor(stay: Stay, payments: Payment[] | null): StayStatus {\n if (payments === null) {\n return { stay, state: \"could_not_check\", amountSeen: 0,\n note: \"We could not read this person's payments just now, so this one is unknown. It is not a finding either way.\" };\n }\n // No booking date means no window to search, so there is no honest answer here.\n // [was: the range fell back to the beginning of time, and a payment from 2019 cleared the stay.]\n if (!stay.bookedAt) {\n return { stay, state: \"could_not_check\", amountSeen: 0,\n note: \"This booking has no record of when it was made, so there is no period to check a deposit against. It is not a finding either way.\" };\n }\n const near = collapseSameMoney(paymentsNearStay(stay, payments)).kept;\n // THE ONLY THING THAT CLEARS A STAY: a card payment for exactly the deposit. Everything else\n // gets shown to Kim with its date and left to her, because nothing in the data says what a\n // payment was for and two goes at guessing have both cost her money.\n const due = depositDue(stay);\n const dogs = Math.max(1, stay.dogCount || stay.dogs.length || 1);\n // TWO SHAPES OF EXACT EVIDENCE, and nothing else clears a stay: one payment for the whole\n // amount due, or one $50 payment per dog. Both are exact-amount matches. Summing whatever else\n // is on the account is what cleared a customer on a training package two versions ago.\n const whole = near.filter((p) => p.amount === due);\n const perDog = near.filter((p) => p.amount === DEPOSIT);\n const exact = whole.length ? [whole[0]] : (perDog.length >= dogs ? perDog.slice(0, dogs) : []);\n const rest = near.filter((p) => !exact.includes(p));\n const restNote = rest.length\n ? ` ${rest.length === 1 ? \"There is also 1 other card payment\" : `There are also ${rest.length} other card payments`} on this account around this stay: ${listPayments(rest)}.`\n : \"\";\n if (exact.length) {\n return { stay, state: \"seen\", amountSeen: due,\n note: exact.length === 1\n ? `A card payment for exactly $${due.toFixed(2)} is on file on ${prettyDay(exact[0].at)}, which is the deposit for ${dogs === 1 ? \"1 dog\" : `${dogs} dogs`}.${restNote}`\n : `${exact.length} card payments of $${DEPOSIT}.00 are on file, one per dog, on ${exact.map((p) => prettyDay(p.at)).join(\" and \")}. That is the $${due.toFixed(2)} due for ${dogs} dogs.${restNote}` };\n }\n if (near.length) {\n return { stay, state: \"partial\", amountSeen: near.reduce((n, p) => n + p.amount, 0),\n note: `The deposit on this stay is $${due.toFixed(2)} (${dogs === 1 ? \"1 dog\" : `${dogs} dogs`} at $${DEPOSIT}), and nothing on file matches that amount. ${near.length === 1 ? `1 card payment is on file around it: ${listPayments(near)}. Worth a look to see whether that was the deposit.` : `${near.length} card payments are on file around it: ${listPayments(near)}. Worth a look to see whether the deposit is among them.`}` };\n }\n return { stay, state: \"none_seen\", amountSeen: 0,\n note: `The deposit on this stay is $${due.toFixed(2)} (${dogs === 1 ? \"1 dog\" : `${dogs} dogs`} at $${DEPOSIT}) and no card payment is on file around it at all. ${OTHER_ROUTES}` };\n}\n\n/** ONE PAYMENT, ONE STAY.\n *\n * statusFor answers about a single stay and is handed the customer's whole payment list, so a\n * regular who books Thanksgiving AND Christmas in the same phone call and pays one $50 deposit\n * had BOTH stays marked settled. Kim was owed $100, $50 arrived, and neither row reached the\n * shortlist. That is the exact failure the module says it exists to prevent, and it is the\n * ordinary case rather than an edge — the two windows are six weeks apart and the search window\n * around each booking overlaps almost completely.\n *\n * So the payments are ALLOCATED. Each exact-deposit payment settles at most one stay, earliest\n * drop-off first, and a payment already spent on one stay is invisible to the next. */\nexport function statusesForCustomer(stays: Stay[], payments: Payment[] | null): StayStatus[] {\n const ordered = [...stays].sort((a, b) => a.day.localeCompare(b.day));\n if (payments === null) return ordered.map((s) => statusFor(s, null));\n // COLLAPSED ONCE, HERE, BEFORE ANYTHING IS ALLOCATED.\n // [was: statusFor collapsed internally and the allocator marked only the SURVIVING id as spent,\n // so the folded twin was still visible to the next stay. The same two records were read as one\n // payment when judging a stay and as two when allocating across them, and one $50 deposit that\n // Square had written twice — the exact direct+matched pair live on her account — cleared TWO\n // holiday stays, quoting two different dates so it read as two deposits.]\n const money = collapseSameMoney(payments).kept;\n const spent = new Set();\n return ordered.map((s) => {\n const available = money.filter((p) => !spent.has(p.id));\n const st = statusFor(s, available);\n if (st.state === \"seen\") {\n // EARLIEST DROP-OFF FIRST, and the earliest qualifying payment settles it. Both halves are\n // deliberate and both are pinned by H48: without an order, which stay gets the money is\n // whichever way the array happened to arrive.\n // COMPUTED EXACTLY AS statusFor COMPUTES THE ONE IT QUOTES, so the record Kim reads on the\n // row is the record that gets debited. Since collapseSameMoney is idempotent this second\n // pass is a no-op on already-collapsed money, and there is deliberately no control for it:\n // a control that cannot fail is worse than none. H57 is what guards the idempotency this\n // relies on. [was: paymentsNearStay without the collapse, which diverged from the quote.]\n const claimed = collapseSameMoney(paymentsNearStay(s, available)).kept.find((p) => p.amount === DEPOSIT);\n if (claimed) spent.add(claimed.id);\n }\n return st;\n });\n}\n\n/** The kill switch. If the payment feed itself looks dead, say so instead of telling Kim that\n * every single customer owes her money.\n *\n * MIN_SAMPLE exists because of what happened on the first live run, 6 Aug 15:41Z. Two holiday\n * stays were booked, neither customer had a Square note, and the switch fired: Kim would have\n * been shown \"the payment feed has stopped\" on the strength of two people. Two customers with no\n * Square payment is an ordinary Tuesday, not evidence of an outage. Below the floor the list is\n * shown with its usual caveats, which is the honest reading of a small sample.\n *\n * IT COUNTS CUSTOMERS, NOT BOOKINGS. [was: one entry per stay, so a single regular with five\n * holiday drop-offs and a habit of paying cash cleared the floor on their own and suppressed the\n * whole card. Her real data has one contact with 24 drop-offs. The docstring said \"customers\"\n * and the code counted rows.] */\nexport const MIN_SAMPLE_FOR_DEAD_FEED = 5;\nexport function feedLooksDead(perCustomer: Map | Payment[][], minSample = MIN_SAMPLE_FOR_DEAD_FEED): boolean {\n const lists = perCustomer instanceof Map ? [...perCustomer.values()] : perCustomer;\n return lists.length >= minSample && lists.every((p) => p.length === 0);\n}\n\n/** The sentence Kim reads. Generated from the counts, so the words cannot disagree with them. */\nexport function depositSentence(statuses: StayStatus[], feedDead: boolean): string {\n if (statuses.length === 0) {\n return \"No holiday boarding stays are booked in the deposit windows yet, so there is nothing to check.\";\n }\n const none = statuses.filter((s) => s.state === \"none_seen\").length;\n const partial = statuses.filter((s) => s.state === \"partial\").length;\n const seen = statuses.filter((s) => s.state === \"seen\").length;\n const unknown = statuses.filter((s) => s.state === \"could_not_check\").length;\n if (feedDead) {\n // The old wording claimed \"no Square payment has been recorded against ANYBODY\", which was a\n // claim about people the run had never managed to read. It now says how many it actually read.\n const checked = statuses.length - unknown;\n if (checked <= 0) {\n return `There ${statuses.length === 1 ? \"is 1 holiday stay\" : `are ${statuses.length} holiday stays`} booked, and none of them could be checked just now, so there is nothing to report either way yet.`;\n }\n return `There ${statuses.length === 1 ? \"is 1 holiday stay\" : `are ${statuses.length} holiday stays`} booked, and no card payment shows against ${checked === statuses.length ? \"any of them\" : `any of the ${checked} we could check`}. That pattern usually means the payment feed has stopped rather than that nobody has paid, so the list is being held back until that is checked.`;\n }\n const bits: string[] = [];\n bits.push(`${statuses.length} holiday ${statuses.length === 1 ? \"stay is\" : \"stays are\"} booked.`);\n if (seen) bits.push(`${seen} ${seen === 1 ? \"has a Square payment\" : \"have a Square payment\"} on file.`);\n if (none || partial) {\n const n = none + partial;\n // NO FIXED FIGURE HERE. The deposit is $50 per dog, so the amount due differs per row: the\n // headline said \"we cannot find a $50 payment\" above a three-dog stay that owes $150. Each\n // row states its own amount; the headline states none.\n bits.push(`${n} ${n === 1 ? \"is worth checking\" : \"are worth checking\"}: we cannot find a card payment matching what ${n === 1 ? \"it is\" : \"they are\"} owed.`);\n }\n if (unknown) bits.push(`${unknown} could not be checked just now.`);\n bits.push(`${OTHER_ROUTES} This is a shortlist to look at rather than a list of people who owe you.`);\n return bits.join(\" \");\n}\n",[261],"f695dcb2-f009-450c-a39c-e66915ac7c48","facts.ts","ac8030d4-904a-11f1-a8a4-1607ee4eb77e",144,["D",1785903524091],3,"// ONE SOURCE OF TRUTH PER FACT. v1.0, 4 Aug 2026.\n//\n// THE ROOT CAUSE THIS FILE EXISTS TO KILL:\n// Prose and data were produced separately. Somebody wrote a sentence, something else computed a\n// number, and nothing forced them to agree. Every wrong claim in this project came from that gap:\n// - \"runs every 15 minutes\" beside a timestamp reading 26 minutes ago\n// - \"1,513 records\" that had drifted to 1,514 before a reader saw it\n// - \"35 counter sales totalling $23,463.99\" when the journal holds 40 totalling $28,035.99\n// - \"11 live questions\" in a handover doc while the page rendered 13\n// None of those were typos. Each was a sentence that had no mechanical link to its own subject.\n//\n// THE RULE: a fact is computed once, here, together with the sentence that describes it. Anything\n// that displays it reads from here. If two files can produce the same number independently, one of\n// them is wrong and nobody knows which.\n//\n// EVERY FACT CARRIES ITS PROVENANCE: where it was read and when. `Fact.source` answers \"where did\n// this number come from\" in one hop, which is the test for whether it ships.\n\nexport type Fact = {\n value: T | null; // null means NOT KNOWN, never zero-by-accident\n source: string; // the endpoint or blob it came from, in one hop\n readAt: string; // ISO timestamp of the read that produced it\n note?: string; // anything the reader must know to use it honestly\n};\n\n// Written as function DECLARATIONS rather than generic arrows on purpose.\n// [was: `export const fact = (value: T | null, ...)`. Inside the val that compiles fine, and\n// the dashboard has always rendered correct numbers from it. But esm.town, which is how any\n// OTHER val would import this file, parses a .ts file as .tsx: it read `` as an opening JSX\n// tag and served `export const fact = _jsxs(T, { children: [\"(value: T | null, source...\"] })`\n// — the type signature turned into React children. Anything importing it got garbage that would\n// have thrown at call time, not at import time. The watchdog needs to import this file so that\n// the Square backlog is computed in exactly one place; `function fact(` is unambiguous to\n// both parsers, so it can.]\nexport function fact(value: T | null, source: string, note?: string): Fact {\n return { value, source, readAt: new Date().toISOString(), note };\n}\n\n/** A fact that could not be read. Distinct from a fact whose value is genuinely zero. */\nexport function unknownFact(source: string, note?: string): Fact {\n return { value: null, source, readAt: new Date().toISOString(), note };\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE SQUARE BACKLOG. Previously four numbers typed into a sentence: \"35 counter sales totalling\n// $23,463.99. 14 of the 35 carry enough of a trail; the other 21 arrived with no name.\"\n// An independent re-derivation found 40 / $28,035.99 / 10 / 30. The typed version understated the\n// unlinked money by $4,572 and understated the unresolvable count by 9. It is computed now.\n//\n// The subtlety that makes this worth a function rather than a one-liner: the bridge RE-LOGS the\n// same payment on every retry, so 87 journal rows collapse to 40 distinct payments. Summing rows\n// instead of payments gives $56,369.97, which is double-counting, not a bigger truth.\n// ---------------------------------------------------------------------------------------------\n\nexport type SquareBacklog = {\n payments: number; // distinct payment ids that never matched a contact\n total: number; // their summed value, counting each payment once\n withTrail: number; // carry an email, phone or Square customer id: recoverable with effort\n withTrailTotal: number;\n noTrail: number; // arrived with nothing at all: no permission will ever resolve these\n noTrailTotal: number;\n};\n\nexport function squareBacklog(journal: unknown): SquareBacklog | null {\n if (!Array.isArray(journal)) return null;\n const byPayment = new Map();\n for (const r of journal as any[]) {\n if (r?.kind !== \"NO-MATCH\") continue;\n const m = /payment\\s+(\\S+)/.exec(String(r?.note ?? \"\"));\n if (!m) continue; // an unparseable note is not a payment we can count\n const id = m[1];\n const amt = Number(r?.amount) || 0;\n // any positive identity flag on ANY row for this payment means it is in principle traceable\n const trail = r?.hadEmail === true || r?.hadPhone === true || r?.hadCustomerId === true;\n const prev = byPayment.get(id);\n if (prev) { prev.trail = prev.trail || trail; if (!prev.amt && amt) prev.amt = amt; }\n else byPayment.set(id, { amt, trail });\n }\n const rows = [...byPayment.values()];\n const sum = (f: (x: { amt: number; trail: boolean }) => boolean) =>\n rows.filter(f).reduce((a, x) => a + x.amt, 0);\n return {\n payments: rows.length,\n total: rows.reduce((a, x) => a + x.amt, 0),\n withTrail: rows.filter((x) => x.trail).length,\n withTrailTotal: sum((x) => x.trail),\n noTrail: rows.filter((x) => !x.trail).length,\n noTrailTotal: sum((x) => !x.trail),\n };\n}\n\n// ---------------------------------------------------------------------------------------------\n// SENTENCES ARE GENERATED FROM VALUES, NEVER COMPOSED ALONGSIDE THEM.\n// Each of these takes the fact and returns the words. There is no path by which the words can\n// describe a different number from the one passed in, because there is only one number.\n// ---------------------------------------------------------------------------------------------\n\nconst money = (n: number) => `$${n.toLocaleString(\"en-US\", { minimumFractionDigits: 2, maximumFractionDigits: 2 })}`;\n\nexport function squareSentence(b: SquareBacklog | null): string {\n if (!b || b.payments === 0) {\n return \"We could not read the payment records just now, so there is nothing to report here rather than a zero to trust.\";\n }\n const parts = [\n `${b.payments} counter sales totalling ${money(b.total)} are recorded but not linked to a name.`,\n ];\n if (b.withTrail) {\n parts.push(`${b.withTrail} of them, worth ${money(b.withTrailTotal)}, carry enough of a trail to be matched with effort.`);\n }\n if (b.noTrail) {\n parts.push(`The other ${b.noTrail}, worth ${money(b.noTrailTotal)}, arrived with no name, email or phone attached at all, and nothing will ever resolve those.`);\n }\n parts.push(\"Either way it is old filing rather than missing money.\");\n return parts.join(\" \");\n}\n\n// ---------------------------------------------------------------------------------------------\n// THE PHONE-CALL OMISSION. Two facts sat on the page and were never joined: a channel bucket\n// labelled \"somewhere else\" holding 20 people, and a separate line saying the old source column\n// logged 22 phone calls. An independent cross-tab showed the \"other\" bucket is 20 of 20 phone\n// calls, 100%. The page had the answer twice and printed it as a shrug. Computed now.\n// ---------------------------------------------------------------------------------------------\n\nexport type ContactLike = {\n source?: string | null;\n attribution?: { medium?: string | null } | null;\n dateAdded?: string;\n};\nexport type Win = { startMs: number; endMs: number };\n\n/**\n * What share of the un-named \"other\" medium bucket is explained by phone calls?\n *\n * THE WINDOW IS MANDATORY, and this is not defensive typing. The first version of this function\n * took no window, so it counted every contact ever fetched (nine weeks) and rendered \"all 192 of\n * them are logged as phone calls\" directly beneath a bar that read 20. Same disease, in the code\n * written to cure it: a sentence describing a different population from the chart above it.\n * A caller that cannot supply the window gets null rather than a number from the wrong period.\n */\nexport function otherBucketExplanation(contacts: ContactLike[] | null, w: Win | null): { other: number; phoneInOther: number } | null {\n if (!Array.isArray(contacts) || !contacts.length || !w) return null;\n const inWin = (c: ContactLike) => {\n const t = Date.parse(c.dateAdded ?? \"\");\n return Number.isFinite(t) && t >= w.startMs && t < w.endMs;\n };\n const scoped = contacts.filter(inWin);\n if (!scoped.length) return null;\n const isOther = (c: ContactLike) => /^other$/i.test(String(c.attribution?.medium ?? \"\").trim());\n const isPhone = (c: ContactLike) => /phone/i.test(String(c.source ?? \"\"));\n return {\n other: scoped.filter(isOther).length,\n phoneInOther: scoped.filter((c) => isOther(c) && isPhone(c)).length,\n };\n}\n\nexport function otherBucketSentence(x: { other: number; phoneInOther: number } | null): string {\n if (!x || x.other === 0) return \"\";\n if (x.phoneInOther === 0) {\n return `The ${x.other} filed as \"somewhere else\" carry an arrival record that just says \"other\", and none of them match a logged phone call, so we genuinely cannot place them.`;\n }\n const all = x.phoneInOther === x.other;\n return all\n ? `Worth knowing what \"somewhere else\" actually is: all ${x.other} of them are logged in your CRM as phone calls. Your arrival record has no category for a call, so people who rang you land in that bucket. They are not unknown, they are your callers.`\n : `${x.phoneInOther} of the ${x.other} filed as \"somewhere else\" are logged in your CRM as phone calls. Your arrival record has no category for a call, so callers land in that bucket rather than one of their own.`;\n}\n\n// ---------------------------------------------------------------------------------------------\n// CROSS-ARTIFACT REGISTRY. Any fact that appears in more than one place (page, PDF, ledger, a\n// message to the client) is registered here by name. The consistency test walks this list and\n// fails the build when two artefacts state the same named fact differently. Drift becomes\n// impossible rather than merely unlikely.\n// ---------------------------------------------------------------------------------------------\n\nexport type SharedFact = {\n name: string; // stable id\n pattern: RegExp; // how it appears in prose, capturing the value\n describe: string; // what it is, for the failure message\n};\n\nexport const SHARED_FACTS: SharedFact[] = [\n { name: \"decision_count\", pattern: /(\\d+)\\s+(?:live\\s+)?questions?\\s+(?:on this page\\s+)?(?:are|is)?\\s*wait/i, describe: \"how many questions are waiting on Kim\" },\n { name: \"bootcamp_bookings\", pattern: /(\\d+)\\s+Bootcamp bookings/i, describe: \"Bootcamp bookings on record\" },\n { name: \"bootcamp_ceiling\", pattern: /\\$([\\d,]+)\\s*(?:,|\\.|and|$)/i, describe: \"the Bootcamp exposure ceiling\" },\n { name: \"slow_track_len\", pattern: /(\\d+)\\s+more spread over about\\s+(\\d+)\\s+months/i, describe: \"the slow track length\" },\n { name: \"automations\", pattern: /(?:all\\s+)?(\\d+)\\s+automations/i, describe: \"automations in the account\" },\n];\n\n// ---------------------------------------------------------------------------------------------\n// THE TAG THAT DECIDES WHETHER GO-LIVE REACHES ANYBODY.\n// The engine enrolls on the tag `nurture - puppy`. If nothing applies it, switching the sequence\n// on reaches nobody, and it looks healthy while doing so: the engine reports successful runs with\n// zero enrollments, which is exactly what a working system with no work also looks like.\n//\n// [was: the page said \"1,200 of your most recent contacts were checked and not one carries the\n// tag\". True when it was typed, and a scan size rather than an answer: it left open whether the\n// other four thousand were different. GoHighLevel will filter contacts by tag server-side and\n// return a total, so the real number is one call away. Cross-checked 5 Aug against a full walk of\n// all 5,544 contacts, page by page: \"no sale\" 133, \"tips-nurture\" 155, \"customer\" 1,512, and\n// `nurture - puppy` zero. The filter and the census agree on every one.]\n// ---------------------------------------------------------------------------------------------\nexport type TagCoverage = { tag: string; tagged: number; total: number };\n\nexport function tagCoverageSentence(t: TagCoverage | null): string {\n if (!t || t.total <= 0) {\n return \"We could not read your contact records just now, so this says nothing rather than a zero worth trusting.\";\n }\n if (t.tagged === 0) {\n return `Every one of your ${t.total.toLocaleString(\"en-US\")} contact records was checked just now, and not a single one is marked as a puppy inquiry. Nothing in your account applies that mark, which is why the tagging has to be switched on at the same moment as everything else.`;\n }\n const pct = Math.round((t.tagged / t.total) * 100);\n return `${t.tagged.toLocaleString(\"en-US\")} of your ${t.total.toLocaleString(\"en-US\")} contact records are marked as a puppy inquiry, checked just now, which is ${pct < 1 ? \"under 1\" : pct}% of them. Those are the people the new messages would pick up.`;\n}\n",[269],"5b9a8400-7df2-455c-826a-e8ca9ca51068","deposits.ts","2e97d0d2-91ad-11f1-a57d-1607ee4eb77e",290,["D",1786048130630],9,"// HOLIDAY DEPOSIT COLLECTOR. The only part of this feature that touches her CRM. v1.0, 6 Aug 2026.\n//\n// WHY IT IS A SEPARATE FILE. holiday-deposits.ts holds all the judgement and a test asserts that\n// it contains no fetch() and no write verb at all. That assertion is only worth something if the\n// network code lives somewhere else, so it lives here. This file fetches and stores; it decides\n// nothing. Every decision is made by a function imported from the module that cannot reach the\n// network.\n//\n// WHAT IT DOES, IN ORDER\n// 1. asks both Boarding Drop Off calendars for the events inside this season's deposit windows\n// 2. groups them into stays (one customer, one day, however many dogs)\n// 3. reads each of those customers' notes, which is where Square money lands\n// 4. writes the answer into the `holiday_deposits` blob\n// The dashboard renders that blob and never repeats any of this, so Kim's page stays fast and\n// cannot be broken by a slow CRM.\n//\n// GET ONLY. Every request in here is a GET. There is no code path that tags, messages, moves or\n// updates anybody, and there is no argument that makes one appear.\n//\n// A FAILED READ IS NOT A ZERO. If a customer's notes cannot be read, that customer is recorded as\n// unknown, with the reason, and stays unknown all the way to Kim's screen. The one thing this\n// feature must never do is turn a network hiccup into \"this person has not paid\".\n//\n// ?k= the stored answer, as JSON\n// ?k=&run=1 re-collect from the live CRM, then store and return it\ndeclare const Deno: { env: { get(k: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\nimport {\n holidayWindows, seasonYear, groupIntoStays, parseSquarePayments, statusFor, feedLooksDead,\n depositSentence, paymentsNearStay, statusesForCustomer, shiftDays, businessDay, type CalEvent, type Payment, type StayStatus,\n} from \"./holiday-deposits.ts\";\n\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\n// Both drop-off calendars. One customer appears on BOTH of these in her live data, which is why\n// the union is taken rather than whichever one someone remembers first.\nexport const BOARDING_CALENDARS = [\"wS5N8WN4BbzznaLjEg1N\", \"ZmmjQJszkRMUltfEbumB\"];\n// The matching PICK UP calendars. A drop-off appointment is a ten minute handover slot, so the\n// only place the length of a stay is written down is here. Read on 6 Aug: Ghost and Chewy drop\n// off on 25 Nov and are collected on the 28th, and nothing on the drop-off calendar says that.\nexport const PICKUP_CALENDARS = [\"1FnbK7pQp1ViZWIzX9SR\", \"bN6wWGJa0qKq0QGRg4CC\"];\n// How far past the last window to look for the pick-up that ends a stay running over New Year.\nexport const LOOKAHEAD_DAYS = 30;\nexport const BLOB_KEY = \"holiday_deposits\";\n// How far before the first holiday window to look for bookings. A stay that starts earlier and\n// runs into the window is still a holiday stay; the query filters on drop-off time, so it has to\n// be fetched before it can be judged.\nexport const LOOKBACK_DAYS = 21;\n// The notes endpoint takes NO paging parameters (it 422s on limit and on offset), so the only\n// defence against a silently truncated list is to treat a response at the cap as unreadable.\n// 100 is the usual GHL page size; the largest real list across 60 sampled contacts was 3.\nexport const NOTES_UNPAGEABLE_CAP = 100;\n// How often the list is refreshed off the engine's schedule.\nexport const REFRESH_EVERY_MS = 3_600_000;\n// The ATTEMPT stamp, written on every try. Gating on the stored list instead means a run that\n// legitimately declines to store — no credential, no calendar, everybody unreadable, an empty\n// season held back — leaves the gate open, and the engine then retries every 15 minutes forever\n// against a CRM that is already unwell.\nexport const ATTEMPT_KEY = \"holiday_deposits_attempt\";\n\n/** Is it time to look again? Pure, so the rule can be tested instead of inspected as text.\n * An unreadable or missing stamp opens the gate: never having looked, and not being able to tell\n * when we last looked, both mean look now. A NaN must not close it forever. */\nexport function needsRefresh(lastAttemptAt: string | null | undefined, nowMs: number, everyMs = REFRESH_EVERY_MS): boolean {\n if (!lastAttemptAt) return true;\n const t = Date.parse(String(lastAttemptAt));\n if (!Number.isFinite(t)) return true;\n return nowMs - t > everyMs;\n}\n\n/** Whether a finished collection may replace what is stored. Pure, so all four refusals are\n * testable; they used to be reachable only through the live blob and were checked as regexes. */\nexport function decideStore(out: DepositBlob, prev: DepositBlob | null, force = false): { store: boolean; error?: string } {\n // A collection that could not read a single calendar is NOT stored: overwriting a good answer\n // with an empty one would show Kim \"no holiday stays booked\" the first time her CRM blinked.\n if (out.calendarsRead === 0) return { store: false, error: \"no calendar answered, so the stored list was left alone\" };\n // NOR a collection in which every single row is unknown. The calendars answered, so the guard\n // above lets it through, and the blob would be replaced with a page of \"could not check\" AND a\n // fresh timestamp — the content gets worse while the page claims to have just been updated.\n if (out.rows.length > 0 && out.rows.every((r) => r.state === \"could_not_check\")) {\n return { store: false, error: \"nobody's payments could be read, so the stored list was left alone\" };\n }\n // NOR a run that has gone from a real list to nothing. A renamed calendar answers 200 with an\n // EMPTY events array, which is well formed and passes both guards above; in December that\n // silently replaces her shortlist with \"nothing to check\". A season really can empty out, so\n // this is not permanent: it holds the old list, says why, and the card starts ageing visibly.\n if (!force && out.rows.length === 0 && (prev?.rows?.length ?? 0) > 0) {\n return { store: false, error: `the boarding calendars answered but returned no holiday bookings at all, where the stored list has ${prev!.rows.length}. That is usually a renamed calendar rather than an empty season, so the stored list was left alone. Re-run with force=1 to accept it.` };\n }\n return { store: true };\n}\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\n\nasync function sha256Hex(s: string): Promise {\n const b = await crypto.subtle.digest(\"SHA-256\", new TextEncoder().encode(s));\n return [...new Uint8Array(b)].map((x) => x.toString(16).padStart(2, \"0\")).join(\"\");\n}\nasync function authorised(k: string): Promise {\n const expected = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\") || KEY_SHA256;\n const got = await sha256Hex(k);\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\nasync function blobMod() { return (await import(\"https://esm.town/v/std/blob\")).blob; }\nasync function token(): Promise {\n const env = Deno.env.get(\"GHL_TOKEN\");\n if (env) return env;\n const cfg = await (await blobMod()).getJSON(\"puppy_config\").catch(() => null);\n return (cfg as any)?.ghlToken;\n}\n\n// The single door to the network, and it only knows one verb. Named so that a reader checking\n// \"can this thing write to her account\" gets their answer from the signature.\nasync function getJson(path: string, version: string, tok: string): Promise {\n const r = await fetch(`${GHL}${path}`, {\n method: \"GET\",\n // curl's UA is not decoration: her CRM rejects requests without it.\n headers: { Authorization: `Bearer ${tok}`, Version: version, \"User-Agent\": \"curl/8.5.0\" },\n signal: AbortSignal.timeout(20_000),\n });\n if (!r.ok) throw new Error(`HTTP ${r.status}`);\n return r.json();\n}\n\nexport type DepositRow = {\n contactId: string;\n name: string;\n day: string;\n until: string;\n dogs: string[];\n dogCount: number;\n window: string;\n state: StayStatus[\"state\"];\n amountSeen: number;\n note: string;\n};\nexport type DepositBlob = {\n at: string;\n season: number;\n windows: { name: string; from: string; to: string }[];\n rows: DepositRow[];\n sentence: string;\n feedDead: boolean;\n readFailures: number;\n calendarsRead: number;\n calendarsAsked: number;\n pickupsRead: number;\n pickupsAsked: number;\n};\n\nconst dayMs = (d: string) => Date.parse(`${d}T00:00:00Z`);\n\n/** Every page of a contact's notes, or null if we could not be sure we had them all.\n * Returning a SHORT list would be indistinguishable from a customer with no payments, so a read\n * that cannot be completed returns null and the customer is reported as unknown. */\nasync function allNotes(io: { get: (p: string, v: string) => Promise }, contactId: string): Promise {\n // NO QUERY STRING. [was: `?limit=100&offset=N`, written to fix a truncation worry. This endpoint\n // rejects both: it answers 422 \"property limit should not exist\" to any parameter at all, so\n // every customer became a failed read. It shipped, and both live customers came back \"could not\n // check\" ninety seconds later. It was caught by running it against her account, not by the 250\n // assertions that stayed green — the fixtures answered a URL the real CRM refuses.]\n const d = await io.get(`/contacts/${contactId}/notes`, \"2021-07-28\");\n // A 200 with no notes ARRAY is a response we do not understand, not a customer with no notes.\n if (!Array.isArray(d?.notes)) return null;\n // The endpoint takes no paging parameters, so it returns the lot or it does not. If a response\n // ever comes back at exactly the cap, we cannot tell a full list from a truncated one, and an\n // unknown is the only honest answer. Across 60 sampled contacts on 6 Aug the largest was 3.\n if (d.notes.length >= NOTES_UNPAGEABLE_CAP) return null;\n return d.notes;\n}\n\n/** COLLECT. `io` is injected so the whole thing can be run against fixtures in a test without a\n * network, and so there is exactly one place in this file that can talk to her CRM. */\nexport async function collect(\n io: { get: (path: string, version: string) => Promise },\n todayIso: string,\n): Promise {\n const season = seasonYear(businessDay(todayIso));\n const windows = holidayWindows(season);\n const from = windows[0].from, to = windows[windows.length - 1].to;\n\n // ---- the bookings ----\n const events: CalEvent[] = [];\n let calendarsRead = 0;\n for (const cal of BOARDING_CALENDARS) {\n try {\n // LOOK BACK BEFORE THE WINDOW. A dog dropped off on 19 December and collected on the 27th\n // has boarded over Christmas, but the query filters on the drop-off time, so without this\n // reach-back those bookings are never even fetched. windowForRange decides membership.\n // The SAME range as the pick-ups on purpose. [was: drop-offs stopped at the end of the\n // window while pick-ups reached 30 days past it, so for every stay at the tail of the season\n // the customer's own next booking was never fetched. `nextDrop` came back undefined, the\n // \"hard upper bound\" was structurally blind exactly where it mattered, and a 30 Dec stay\n // swallowed the 15 Jan pick-up of a 10 Jan booking — rendering \"Dec 30 to Jan 15\" and\n // letting a January payment settle the holiday deposit. Out-of-window bookings fetched this\n // way are filtered out by the overlap rule; they are here to be next-drop-off markers.]\n const q = `locationId=${LOC}&calendarId=${cal}&startTime=${dayMs(shiftDays(from, -LOOKBACK_DAYS))}&endTime=${dayMs(shiftDays(to, LOOKAHEAD_DAYS))}`;\n const d = await io.get(`/calendars/events?${q}`, \"2021-04-15\");\n // A 200 that does not carry an events ARRAY is not an empty calendar, it is a response we do\n // not understand. [was: `d?.events ?? []`, which counted a renamed key, a partial payload or\n // a stale calendarId as \"read, and she has no bookings\" — and stored that over a good list.]\n if (!Array.isArray(d?.events)) throw new Error(\"no events array in the response\");\n for (const e of d.events) events.push(e as CalEvent);\n calendarsRead++;\n } catch { /* one calendar down is reported below, never silently treated as \"no bookings\" */ }\n }\n // The pick-ups. A calendar that does not answer here is NOT fatal: without it a stay is judged\n // on its drop-off day alone, which is exactly what the module did before, so the list gets\n // smaller rather than wrong. It is reported all the same.\n const pickups: CalEvent[] = [];\n let pickupsRead = 0;\n for (const cal of PICKUP_CALENDARS) {\n try {\n const q = `locationId=${LOC}&calendarId=${cal}&startTime=${dayMs(shiftDays(from, -LOOKBACK_DAYS))}&endTime=${dayMs(shiftDays(to, LOOKAHEAD_DAYS))}`;\n const d = await io.get(`/calendars/events?${q}`, \"2021-04-15\");\n if (!Array.isArray(d?.events)) throw new Error(\"no events array in the response\");\n for (const e of d.events) pickups.push(e as CalEvent);\n pickupsRead++;\n } catch { /* reported on the card: a stay is then judged on its drop-off day alone */ }\n }\n\n const stays = groupIntoStays(events, windows, pickups);\n\n // ---- the money ----\n const rows: DepositRow[] = [];\n // KEYED BY CUSTOMER. The kill switch's floor is written in customers (\"five people with no card\n // payment\"), so a customer with five holiday drop-offs must count once, not five times.\n const perCustomer = new Map();\n let readFailures = 0;\n\n // BY CUSTOMER, not by stay, so one $50 deposit cannot settle two of the same person's bookings.\n const byCustomer = new Map();\n for (const s of stays) {\n const list = byCustomer.get(s.contactId) ?? [];\n list.push(s);\n byCustomer.set(s.contactId, list);\n }\n\n for (const [contactId, own] of byCustomer) {\n let pays: Payment[] | null = null;\n try {\n const notes = await allNotes(io, contactId);\n // A 200 with no notes ARRAY is a response we do not understand, not a customer with no\n // notes. [was: `d?.notes ?? []`, so a rate-limit soft-fail or a changed response shape\n // rendered as \"No Square payment is on file\" — a confident finding built on nothing.]\n pays = notes === null ? null : parseSquarePayments(notes);\n } catch { pays = null; }\n if (pays === null) readFailures++;\n\n let nm = \"\";\n try {\n const c = await io.get(`/contacts/${contactId}`, \"2021-07-28\");\n const ct = c?.contact ?? c;\n nm = [ct?.firstName, ct?.lastName].filter(Boolean).join(\" \").trim() || ct?.contactName || \"\";\n } catch { nm = \"\"; }\n // A name we could not read is shown as that, not as a blank that reads like a bug.\n const name = nm || \"name not readable\";\n\n // WHAT THE KILL SWITCH IS ALLOWED TO SEE: money in the period this run is judging, for\n // customers we actually searched. A stay with no booking date has NO searchable window, so\n // paymentsNearStay returns a structural empty for it; counting that as \"we looked and saw no\n // money\" let one missing field push the sample over the floor and black out the whole card.\n if (pays !== null && own.some((s) => s.bookedAt)) {\n const near = own.filter((s) => s.bookedAt).flatMap((s) => paymentsNearStay(s, pays!));\n perCustomer.set(contactId, near);\n }\n\n for (const st of statusesForCustomer(own, pays)) {\n rows.push({\n contactId, name, day: st.stay.day, until: st.stay.until, dogs: st.stay.dogs,\n dogCount: st.stay.dogCount, window: st.stay.window, state: st.state, amountSeen: st.amountSeen, note: st.note,\n });\n }\n }\n rows.sort((a, b) => a.day.localeCompare(b.day));\n\n const feedDead = feedLooksDead(perCustomer);\n const statuses: StayStatus[] = rows.map((r) => ({\n stay: { contactId: r.contactId, day: r.day, until: r.until, dogs: r.dogs, bookedAt: null, window: r.window },\n state: r.state, amountSeen: r.amountSeen, note: r.note,\n }));\n\n return {\n at: todayIso, season, windows, rows,\n sentence: depositSentence(statuses, feedDead),\n feedDead, readFailures,\n calendarsRead, calendarsAsked: BOARDING_CALENDARS.length,\n pickupsRead, pickupsAsked: PICKUP_CALENDARS.length,\n };\n}\n\n/** ONE PLACE where a collection is run and stored, so the scheduled run and the manual run cannot\n * drift apart. deposits-cron.ts calls this; so does the endpoint below. */\nexport async function runCollection(force = false): Promise<{ ok: boolean; error?: string; out?: DepositBlob }> {\n const b = await blobMod();\n // Stamped BEFORE the work, so a collection that fails, times out or declines to store still\n // closes the gate for an hour rather than being retried on every tick.\n await b.setJSON(ATTEMPT_KEY, { at: new Date().toISOString() }).catch(() => {});\n const tok = await token();\n if (!tok) return { ok: false, error: \"no CRM credential resolved, so nothing was collected\" };\n const out = await collect({ get: (p, v) => getJson(p, v, tok) }, new Date().toISOString());\n const prev = (await b.getJSON(BLOB_KEY).catch(() => null)) as DepositBlob | null;\n const d = decideStore(out, prev, force);\n if (!d.store) return { ok: false, error: d.error, out };\n await b.setJSON(BLOB_KEY, out);\n return { ok: true, out };\n}\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n if (!(await authorised(url.searchParams.get(\"k\") || \"\"))) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n const json = (o: unknown, status = 200) =>\n new Response(JSON.stringify(o, null, 2), { status, headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" } });\n\n try {\n if (url.searchParams.get(\"run\") !== \"1\") {\n const stored = await (await blobMod()).getJSON(BLOB_KEY).catch(() => null);\n return json(stored ?? { at: null, rows: [], sentence: \"This has not been collected yet.\" });\n }\n const r = await runCollection(url.searchParams.get(\"force\") === \"1\");\n return r.ok ? json(r.out) : json({ error: r.error, ...(r.out ?? {}) }, 503);\n } catch (e) {\n return json({ error: String(e).slice(0, 500) }, 500);\n }\n}\n",[277],"321e09f7-821c-4e77-aabe-b1b3313ce734","deposits-cron.ts","b4eead18-91ad-11f1-b6f8-1607ee4eb77e",248,["D",1786035191302],"// THE HOLIDAY DEPOSIT REFRESH, ON A SCHEDULE. v1.0, 6 Aug 2026.\n//\n// WHY IT IS ITS OWN FILE AND NOT A LINE IN main.ts. main.ts is hard-capped at 80,000 characters\n// and has 679 left. Squeezing this in would mean deleting something that is already load-bearing\n// to make room for something new, on the entry point that runs Kim's follow-up system. A second\n// scheduled file costs nothing and cannot take the engine down with it.\n//\n// IT ONLY READS. Everything it does is inside runCollection(), which reads two calendars and some\n// contact notes and writes one blob. There is no path from here to a message, a tag or a customer.\n//\n// IT NEVER SHOUTS. If the CRM is unreachable this logs and returns. The dashboard already knows\n// how to say \"last checked N hours ago\", so a missed run degrades into a visibly older timestamp\n// rather than into an alarm or, worse, an empty list presented as fact.\nimport { runCollection } from \"./deposits.ts\";\n\nexport default async function (): Promise {\n try {\n const r = await runCollection();\n if (!r.ok) { console.log(`[deposits] not stored: ${r.error}`); return; }\n const o = r.out!;\n const worth = (o.rows ?? []).filter((x) => x.state === \"none_seen\" || x.state === \"partial\").length;\n console.log(`[deposits] ${o.rows.length} stay(s), ${worth} worth checking, ${o.readFailures} unreadable, drop-off calendars ${o.calendarsRead}/${o.calendarsAsked}, pick-up calendars ${o.pickupsRead}/${o.pickupsAsked}`);\n } catch (e) {\n // A scheduled job that throws on val.town shows up as a failed run and pages nobody usefully.\n // The honest outcome of a failed refresh is an older timestamp on the page, which is visible.\n console.log(`[deposits] refresh failed: ${String(e).slice(0, 200)}`);\n }\n}\n",[285],"48486db0-063f-4539-a840-2d0e8a3db960","decisions.ts","13df017c-902f-11f1-8dc5-1607ee4eb77e",223,["D",1786029237007],22,"// WHAT IS WAITING ON KIM. v1.2, 4 Aug 2026.\n//\n// WHY THIS FILE EXISTS: two independent readers were handed the dashboard cold. Both said the\n// same thing without prompting. Kim: \"there is no list of what I'm being asked, no button, no\n// 'Kim: 3 things waiting on you'.\" Candace: \"exactly one requires anything from us, buried\n// fifth-from-top, styled identically to eight items needing nothing, with no owner.\" A page that\n// reports state but never asks for a decision quietly turns the reader into a spectator.\n//\n// THE RULE: an item goes here only when it is genuinely blocked on Kim, it is written in her\n// words, and it says what happens if she says yes AND what happens if she says nothing. No item\n// nags. No item implies she is late. \"Nothing\" is always an acceptable answer, and where that is\n// true the item says so.\n//\n// EVERY ITEM MIRRORS A NUMBERED ROW IN THE COMMITMENTS LEDGER, so the page and the ledger cannot\n// drift apart. The `ref` is that row. If you add one here, add it there in the same commit.\n//\n// v1.2, after the second stranger test. Three findings, all fair:\n// 1. Every item carries `evidence` now. The work log below it sets a standard of proof (\"How we\n// know\" on every line) and this card was exempting itself from that standard while sitting\n// ABOVE it. The reader noticed within one read.\n// 2. No item may hardcode a live number. The old K11 text said \"two of this week's went\n// unmarked\" while the tiles, reading the same account, showed none unmarked in their window.\n// A number typed into prose goes stale the day after it is typed. Live figures arrive through\n// `Ctx` and are rendered by a function, or they are not stated.\n// 3. The $250 Bootcamp cohort is a decision about her customers' money and was sitting twelve\n// rows down in the work log rather than here. \"Wrong things promoted\", exactly.\n\nexport type Ctx = {\n unmarkedPupTalks?: number | null; // appointments with no showed/no-show mark yet, this window\n inquiriesPerWeek?: number | null; // live count, so the volume a YES commits her to is never typed\n // computed by facts.ts from the bridge journal. The typed version of this sentence was wrong in\n // all four of its numbers and understated the money by $4,572.\n squareSentence?: string | null;\n // Live, from a server-side tag filter over the WHOLE contact base. Never a scan size.\n puppyTagSentence?: string | null;\n // What the tagging step WOULD pick up, measured on the engine's last run. Null until it has run\n // one, so the page never implies a dry pass happened when none did.\n tagScanSentence?: string | null;\n};\n\nexport type Decision = {\n ref: string; // ledger row, e.g. \"K8\"\n ask: string; // the question, in Kim's vocabulary, ending in a question mark\n why: string | ((c: Ctx) => string); // what it unblocks or prevents\n // A function when the evidence contains a figure. A number in evidence is still a number,\n // and it drifts exactly like a number in prose does.\n evidence: string | ((c: Ctx) => string);\n ifYes?: string | ((c: Ctx) => string); // what saying yes costs. May depend on live figures.\n ifNothing: string; // what happens if she never answers. Honest, including \"nothing bad\".\n weight: \"blocking\" | \"worth doing\" | \"whenever\";\n liveNow?: boolean; // already affecting real customers today, as opposed to pending\n // v1.5. Three separate readers, independently, came to this page worrying about money and found\n // the only question about money filed last and folded away. Weight measures urgency; this\n // measures whether the reader will go looking for it. Money always shows.\n surface?: boolean;\n /** An extra paragraph computed at render time. Never a place to put a typed figure. */\n extra?: (c: Ctx) => string;\n};\n\n// v1.3, after the third stranger test, which read this file as well as the page. Four findings:\n// 1. The type stated the rule as \"what happens if she says yes AND if she says nothing\" and then\n// implemented only half of it. `ifYes` now exists and is filled wherever a yes has a cost.\n// 2. `weight: \"blocking\"` was applied to two items that do not block. An item carrying a stated\n// default is an answered question; a December deposit does not gate a puppy sequence. The\n// headline counts blockers, so mislabelling one puts a wrong number at the top of the page.\n// 3. The genuine email go-live blocker was in the ledger and NOT here, so a reader answering\n// every card would believe the runway was clear when the email half cannot deliver.\n// 4. The page detected \"already reaching customers\" by regex-matching this file's prose, so a\n// reword would have silently disabled the warning. It is a field now.\n\nexport const DECISIONS: Decision[] = [\n {\n ref: \"K8\",\n ask: \"Can we switch the new follow-up messages on, and switch the old ones off at the same moment?\",\n why: \"Two things have to happen in the same few minutes, not one. Your CRM still has its own puppy follow-up running, so ours going on and that one going off is a single move or new inquiries get two sets of messages from you on the same day. And ours only picks people up when they are tagged as a puppy inquiry, which nothing currently does, so that tagging has to be switched on at the same time or the new messages go live and quietly reach nobody.\",\n evidence: (c: Ctx) =>\n \"All 165 automations were read one by one on 4 August; the one still switched on is named \\\"1. Wait 1 Day: Initial Nurture - Puppy\\\". \" +\n (c.puppyTagSentence ?? \"The mark our system watches for could not be counted just now, so treat the tagging step as unconfirmed rather than done.\"),\n ifYes: (c) =>\n `All three get done together, with you watching: tagging on, ours on, the old one off. From that moment it starts working on ${c.inquiriesPerWeek != null ? `roughly the ${c.inquiriesPerWeek} new inquiries a week you are getting now` : \"your new inquiries as they arrive\"}, and nothing changes for anyone already partway through the old sequence.`,\n ifNothing: \"Nothing breaks. The new messages stay in practice mode and nobody is messaged by them.\",\n weight: \"blocking\",\n extra: (c) => c.tagScanSentence\n ? `On the third of those three switches: the part that works out who counts as a puppy inquiry is now built and running quietly alongside everything else, so you can see what it would do before it does anything. ${c.tagScanSentence} One thing worth your view: a dog of about a year old sits right on the line. Your messages do cover the teenage stage, so they may well belong. That one is yours to call.`\n : \"\",\n },\n {\n ref: \"K1\",\n ask: \"Do the follow-up messages sound like you?\",\n why: \"You have both write-ups in hand. So you know exactly what you are agreeing to: 21 days of messages up front, then 29 more spread over about 19 months, and after that one email a month indefinitely, cycling the same twelve seasonal ones year after year. Anyone can stop all of it at any point with one word. Every text says so in its final line, and the emails get their unsubscribe link from the email system at send time, which practice mode has not yet exercised.\",\n evidence: \"Both write-ups were generated from the live system rather than from a draft, so what you read is exactly what would send.\",\n // v1.4. This read \"roughly 190 new people a week\" while the page counted 186 four inches\n // above it. The volume a YES commits her to is the whole weight of the question, so it is\n // counted at render time or it is not stated as a number at all.\n ifYes: \"The wording is settled and nothing else about it comes back to you. It still does not send until the go-live question above is answered too.\",\n ifNothing: \"Nothing sends. The wording sits exactly as you last read it.\",\n weight: \"blocking\",\n },\n {\n ref: \"K2\",\n ask: \"Which number should customers see, 912-348-8726 or 912-823-4382?\",\n why: \"It goes at the bottom of every message that leaves the system, so it needs to be the one you actually want ringing.\",\n evidence: \"Both numbers are live on your account and both are cleared for texting. On 4 August, only one of them was on your website footer: 912-348-8726.\",\n ifNothing: \"We use 912-348-8726, the one already on your website. This one has a default, so it does not hold anything up; it is here because it is your name on the message.\",\n weight: \"worth doing\",\n },\n {\n ref: \"KB1\",\n ask: \"What do you want done about the Bootcamp deposits taken at $250 instead of $500?\",\n why: \"Your booking form was set to a $250 deposit rather than $500, and it was live until 2 August. There are 17 Bootcamp bookings on record from 19 December onward, every one taken while it was wrong. So the most this can be worth is 17 times $250, which is $4,250, and the least is nothing if none of them paid a deposit at all. The true figure is somewhere between, and finding it means matching those bookings against the payment records.\",\n evidence: \"The wrong figure was found inside the booking form's own settings, corrected and published, and the live site was then searched end to end for '$250' with no hits left. The 17 bookings were counted from your own records. Which of them actually paid a deposit means matching bookings to payments by hand, which is work rather than a blocker: the payment link into your CRM is already live and has been since 1 August.\",\n ifYes: \"We pull the payment list, put a real number on it, and bring it back to you before anybody is contacted. Deciding to look is not deciding to chase.\",\n ifNothing: \"Nothing further goes wrong, because the form is already fixed. Up to $4,250 that was underpaid stays underpaid.\",\n extra: (c) => c.squareSentence ? `Separately, on the same subject of money the records cannot place: ${c.squareSentence}` : \"\",\n weight: \"worth doing\",\n surface: true,\n },\n {\n ref: \"K6\",\n ask: \"Should people who have already booked keep getting the safety tips?\",\n why: \"Right now the follow-ups stop the moment somebody books. Some owners like the tips continuing; some find it odd to still be sold at after they said yes.\",\n evidence: \"Read from the sequence itself: booking is a stop condition on every path, including the slow track.\",\n ifNothing: \"They stop at booking, which is the safer of the two.\",\n weight: \"worth doing\",\n },\n {\n ref: \"K11\",\n ask: \"Can we ask the front desk to mark every Pup Talk showed or no-show?\",\n why: (c) =>\n c.unmarkedPupTalks\n ? `${c.unmarkedPupTalks} of the Pup Talks in the last 7 days ${c.unmarkedPupTalks === 1 ? \"has\" : \"have\"} no mark against ${c.unmarkedPupTalks === 1 ? \"it\" : \"them\"} yet, so the show-up figure on this page is better than the truth by up to that many. It is a ten second job at the desk.`\n : \"When one goes unmarked the show-up figure on this page comes out better than the truth, because an unmarked appointment is not counted as a miss. None are unmarked right now, and keeping it that way is a ten second job at the desk.\",\n evidence: \"Counted live from your calendar each time this page loads, not typed in here.\",\n ifYes: \"Nothing to build. It is a habit at the desk, and the number on this page stops flattering itself.\",\n ifNothing: \"The show-up figure drifts optimistic whenever one is missed, and this page keeps saying so. Nothing else is affected.\",\n weight: \"worth doing\",\n },\n {\n ref: \"K7\",\n ask: \"You have two review-request automations both switched on. Which one do you want to keep?\",\n why: \"You have two review-request workflows switched on at once, with near-identical names. We cannot read a workflow's steps through the interface we have, so we cannot promise you both actually fire, but two published copies is the usual shape of a customer being asked twice, and it is worth ten seconds of your time.\",\n evidence: \"Read from all 165 automations on 4 August: \\\"New Review Request WF\\\" and \\\"Update- New Review Request WF\\\" are both published. What we could NOT do is open either one and read its steps, because that call is not available to us. So this is two live copies, not a confirmed double send.\",\n ifNothing: \"Both stay switched on. If they do both fire, the double ask continues; it is not damaging, it just looks careless.\",\n weight: \"worth doing\",\n liveNow: true,\n },\n {\n ref: \"K12\",\n ask: \"Can we get four small settings added wherever thedogsspotga.com is managed?\",\n why: \"This is the real blocker on the email half. Checked on 4 August, your domain tells the internet that Google and Wix are allowed to send email in your name, and nobody else. If the follow-ups went live today, every email would come from a server your domain does not stand behind, and a lot of them would land in spam or bounce outright. Texting is unaffected: that is verified separately and already works.\",\n evidence: \"Read from your domain's own public records. They list Google and Wix and nothing else. The settings needed are generated by your CRM and are four short lines of text.\",\n ifYes: \"Amir sends the exact four lines and, if you are not sure who looks after your domain, works that out from the records rather than asking you to. Whoever it is pastes them in, it takes about ten minutes, and email can go live alongside texting.\",\n ifNothing: \"Texting can still go live on its own. Email cannot, and this stays the one thing standing in its way.\",\n weight: \"blocking\",\n },\n {\n ref: \"K10\",\n ask: \"Do you want to go through what all this costs against what it brings in?\",\n why: \"Your advertising is running at roughly $675 a week, your CRM is about $200 a month, and there is the retainer on top. This page shows you counts of people, not money, in either direction. It cannot show what you spend because Facebook has not given us permission to read it, and it cannot show what you earned because your CRM does not record a value on a sale. That is Amir's job and it is on his list, not yours.\",\n evidence: \"The ad figure is one week, 24 to 30 July, where the per-campaign spends summed to $674.71 and matched the account total exactly. It was read off the ads screen by eye, not through the connection that is still waiting on Facebook, which is exactly why finishing that connection matters. That is one week checked, not a standing rate. The CRM figure is its published price. Neither is on this page yet, and that is a gap rather than a mystery.\",\n ifYes: \"Half an hour, once Facebook lets us read the spending, with real numbers rather than impressions.\",\n ifNothing: \"The conversation waits. Nothing degrades, but this page keeps showing you what came in and not what it cost.\",\n weight: \"worth doing\",\n surface: true,\n },\n {\n ref: \"K13\",\n ask: \"Can we retire the access key you pasted into the Upwork thread on 31 July?\",\n why: \"It is a working key to your CRM sitting in a chat log. Nothing has gone wrong that we know of, and we have no way to tell whether anybody else has used it, which is exactly why it should not be sitting there. It is simply not where a key should live.\",\n evidence: \"The message was still in the thread on 4 August. Retiring it takes about two minutes on your side and everything carries on working, because a fresh one replaces it.\",\n ifYes: \"Two minutes, and one loose end closed.\",\n ifNothing: \"A working key to your customer list stays in a chat log that other people can be added to. Nothing has gone wrong so far, and nobody can promise it will not.\",\n weight: \"worth doing\",\n liveNow: true,\n },\n {\n ref: \"K14\",\n ask: \"Can we take the holiday boarding deposit automatically instead of by hand?\",\n why: \"You already have a product in your CRM called \\\"Holiday boarding deposit\\\" set at $50, fully configured, and it does not appear on a single order in the payment history we can see. Your boarding bookings go through the form on your website instead, so the CRM never gets the chance to take the money or record that it arrived. That is why somebody is checking by hand.\",\n evidence: \"Read from your own product list: \\\"Holiday boarding deposit\\\" and \\\"New Client Boarding Deposit\\\" both exist at $50, and not one order in your recent payment history references either.\",\n ifYes: \"Two sizes of job, and Amir will lay out both before anything is built: record the deposit against the customer automatically so you get a list rather than a memory, or take it as part of the booking so nobody can complete one without paying.\",\n ifNothing: \"It stays a manual check every holiday season.\",\n weight: \"worth doing\",\n },\n {\n ref: \"K15\",\n ask: \"You have five no-sale and tips follow-up sequences running, plus two auto-responders. Do you want me to go through them for overlap?\",\n why: \"They are all published and live. The one that looked accidental, \\\"Copy - Tips Ad campaign > Auto Responder\\\", you answered on 5 August: the copy is Milton's on purpose, and it answers on Facebook comments as well as in Messenger, so it stays exactly as it is. What is left of this question is smaller: whether Amir reads the five sequences so nobody can end up getting two sets of messages from you on the same afternoon.\",\n evidence: \"Read from all 165 automations on 4 August: seven published and one draft. Five are follow-up sequences; two are auto-responders and call routing, so the real number to review is nearer five. Your 5 August message is the answer of record on the copy workflow.\",\n ifYes: \"Amir reads all of them and tells you which are earning their place, before anything new is built.\",\n ifNothing: \"They keep running as they are, which is now the known-good state you described.\",\n weight: \"worth doing\",\n },\n {\n ref: \"K9\",\n ask: \"Would you tell us a story or two from the kennel?\",\n why: \"There are eight places in the follow-up messages where a real thing that happened to a real dog would land far better than general advice. They are written to read perfectly well empty, and they are empty today, because made up stories are not something we will put in your name.\",\n evidence: \"The eight places are marked in the sequence you have already read. Each one has a fallback line that reads normally with no story in it, which is what is running now.\",\n ifNothing: \"The messages read exactly as you have already seen them, which costs you nothing.\",\n weight: \"whenever\",\n },\n {\n ref: \"K16\",\n ask: \"Do you want the one untranscribed call from 4 August looked at, or is the answer enough?\",\n why: \"Mostly answered on 6 August. No transcript exists on any call older than about three months, and since then almost every call with speech has one. What is not settled is why the old ones have none: either transcription was switched on around 11 May, or transcripts are deleted once they reach about ninety days. Both look the same from here, and the second one would mean you are quietly losing call history every month. One query a week from now tells us which, and it costs nothing.\",\n // [was, twice over: first \"Every call in your account was checked\" (it was 62 of them), then\n // \"the writing-down step has simply never been switched on\". That second claim was inferred\n // from the API showing no transcript on any of the 62 call records, and the inference was\n // wrong: the API simply does not carry transcripts on those records. On 5 August a call from\n // that same morning was opened in the CRM and its transcript was watched rendering, word by\n // word. Transcription is on. The claim below is what has actually been observed.]\n evidence:\n \"Sixty-two of your calls were checked from your most recently active conversations: 54 carry a full audio recording, about two and a quarter hours of it, and the recordings play. The 8 without one were calls nobody answered. Then a call from the morning of 5 August was opened directly in the CRM and its written transcript was watched rendering, and a second call from 4:54 that same afternoon shows its transcript in the CRM as well, so transcription is on and working at least sometimes. What has not been found yet is a call that is missing its transcript, which is why your report matters: one example from you of a call where the transcript used to be there, or should be, pins down the pattern in minutes.\",\n ifYes:\n \"Point at one call where the transcript is missing, or tell us roughly when they disappeared for you, and the comparison between that call and this morning's transcribed one does the rest: same number or different, human or Chloe, long or short, before or after a settings change.\",\n ifNothing:\n \"Nothing breaks. Recording keeps working and at least some calls keep getting transcripts, but the ones that are missing stay a puzzle solved by trial and error instead of by one example from you.\",\n weight: \"worth doing\",\n },\n];\n\nexport const WEIGHT_ORDER: Record = { blocking: 0, \"worth doing\": 1, whenever: 2 };\nexport const WEIGHT_LABEL: Record = {\n blocking: \"Holds up go-live\",\n \"worth doing\": \"Worth doing\",\n whenever: \"Whenever you like\",\n};\nexport function sortedDecisions(ds: Decision[] = DECISIONS): Decision[] {\n return [...ds].sort((a, b) => WEIGHT_ORDER[a.weight] - WEIGHT_ORDER[b.weight]);\n}\nexport const blockingCount = (ds: Decision[] = DECISIONS) => ds.filter((d) => d.weight === \"blocking\").length;\n/** Resolve a `why` that may depend on live figures. */\nexport const whyText = (d: Decision, c: Ctx): string => (typeof d.why === \"function\" ? d.why(c) : d.why);\n/** Same treatment for ifYes: a volume figure must be counted, never typed. */\nexport const ifYesText = (d: Decision, c: Ctx): string | undefined =>\n d.ifYes == null ? undefined : (typeof d.ifYes === \"function\" ? d.ifYes(c) : d.ifYes);\nexport const extraText = (d: Decision, c: Ctx): string => (d.extra ? d.extra(c) : \"\");\n/** Evidence gets the same treatment as why/ifYes: a figure in it is computed, never typed. */\nexport const evidenceText = (d: Decision, c: Ctx): string =>\n typeof d.evidence === \"function\" ? d.evidence(c) : d.evidence;\n",[292],"c4ee8217-b5b6-497c-96bb-e209e25d9b14","dashboard.ts","fb119304-9028-11f1-8278-1607ee4eb77e",289,["D",1786048129517],36,"// THE DOGS SPOT, LIVE DASHBOARD. One page Kim can open any time, from anything. v1.0, 4 Aug 2026.\n//\n// THE PROMISE THIS FILE MAKES: it always renders something true. Every data source is fetched\n// independently, every failure is caught, and the last good answer for each section is cached in\n// a blob. If the CRM is down, the page says \"the CRM did not answer just now, here is what it\n// said 20 minutes ago\" instead of showing a zero or a blank. A dashboard that shows a wrong zero\n// is worse than no dashboard, because it is quietly reassuring.\n//\n// ROUTES ?k= the dashboard\n// ?k=&f=json the same numbers as data\n//\n// AUDIENCE: Kim. Non-technical, on a phone, thirty seconds. No jargon, no acronyms unexplained,\n// no metric that does not connect to her money. Detail lives below the fold for whoever wants it.\ndeclare const Deno: { env: { get(k: string): string | undefined } };\nif (typeof (globalThis as any).Deno === \"undefined\") {\n (globalThis as any).Deno = { env: { get: (k: string) => (globalThis as any).process?.env?.[k] } };\n}\nimport {\n countContacts, sourceBreakdown, channelBreakdown, campaignBreakdown, attributionCoverage,\n countEvents, wonOpps, weeklyBuckets,\n deltaWord, money, type ContactLite, type EventLite, type OppLite,\n} from \"./report-logic.ts\";\nimport { sortedDecisions, blockingCount, whyText, ifYesText, extraText, evidenceText, WEIGHT_LABEL, type Decision, type Ctx } from \"./decisions.ts\";\nimport { SEEDED, mergeLog, KIND_LABEL, type WorkEntry } from \"./worklog.ts\";\nimport { squareBacklog, squareSentence, otherBucketExplanation, otherBucketSentence, tagCoverageSentence, type TagCoverage } from \"./facts.ts\";\nimport { observedCadenceMin, lateness, lateSentence, isHealthy, neverRanItselfSentence } from \"./cadence.ts\";\nimport { detectSentence, scanAgeNote, type DetectSummary } from \"./puppy-detect.ts\";\nimport type { DepositBlob, DepositRow } from \"./deposits.ts\";\nimport { looksLikeTestRecord } from \"./holiday-deposits.ts\";\n\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\n// READ FROM THE SAME PLACE THE ENGINE READS IT. If someone changes the enrollment tag in the val's\n// settings, the page must start counting the new tag, not keep reporting confidently on the old\n// one. Two constants would be two facts, and one of them would be wrong without telling anybody.\nconst ENROLL_TAG = Deno.env.get(\"TAG_SOURCE_SIGNAL\") || \"nurture - puppy\";\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst PUP_TALK_CAL = \"qHuYJ0NEqzibnoqf5Cw3\";\nconst CACHE_KEY = \"dash_cache\";\nconst BRIDGE = \"https://amir5--41ace24c7e2111f18c9d1607ee4eb77e.web.val.run\";\n// read-only journal route; overridable by env so the literal is not the only copy\nconst BRIDGE_ADMIN = \"tds_adm_H6Dn3HYINivzgfJd2zic9YYCi9QUA6Yj4SVF7OrKtDQ\";\n\n// ---- palette: validated with the dataviz validator, both modes, on these exact surfaces ------\n// Categorical slots 1-3 (blue/orange/aqua): ALL CHECKS PASS light and dark. Status steps are the\n// reserved four and always ship with a word beside them, never color alone.\nconst CAT = [\"#2a78d6\", \"#eb6834\", \"#1baf7a\"];\nconst CAT_DARK = [\"#3987e5\", \"#d95926\", \"#199e70\"];\nconst GOOD = \"#0ca30c\", WARN = \"#fab219\", CRIT = \"#d03b3b\";\n\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\nasync function sha256Hex(s: string): Promise {\n const b = await crypto.subtle.digest(\"SHA-256\", new TextEncoder().encode(s));\n return [...new Uint8Array(b)].map((x) => x.toString(16).padStart(2, \"0\")).join(\"\");\n}\nasync function blobMod() { return (await import(\"https://esm.town/v/std/blob\")).blob; }\n// v1.1 (review #2): a failed READ and a genuinely EMPTY value are different facts. Collapsing\n// them made the page say \"0 people waiting on you\" when the truth was \"we could not check\".\ntype Read = { ok: true; v: T | null } | { ok: false; v: null };\nasync function readBlob(k: string): Promise> {\n try { return { ok: true, v: ((await (await blobMod()).getJSON(k)) ?? null) as T | null }; }\n catch { return { ok: false, v: null }; }\n}\nasync function getBlob(k: string): Promise { return (await readBlob(k)).v; }\nasync function token(): Promise {\n return Deno.env.get(\"GHL_TOKEN\") || ((await getBlob<{ ghlToken?: string }>(\"puppy_config\"))?.ghlToken ?? undefined);\n}\nasync function isAdmin(k: string) {\n return (await sha256Hex(k)) === (Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\") || KEY_SHA256);\n}\nasync function isViewer(k: string) {\n const tok = await token();\n return !!tok && k === \"tds_view_\" + (await sha256Hex(tok + \":view\")).slice(0, 32);\n}\n\nasync function j(path: string, ver: string) {\n const tok = await token();\n const r = await fetch(`${GHL}${path}`, {\n headers: { Authorization: `Bearer ${tok}`, Version: ver, \"User-Agent\": \"curl/8.5.0\" },\n signal: AbortSignal.timeout(20_000),\n });\n if (!r.ok) throw new Error(`HTTP ${r.status}`);\n return r.json();\n}\n\nconst ET = () => {\n const p = new Intl.DateTimeFormat(\"en-US\", { timeZone: \"America/New_York\", timeZoneName: \"shortOffset\" })\n .formatToParts(new Date()).find((x) => x.type === \"timeZoneName\")?.value ?? \"GMT-4\";\n const m = p.match(/GMT([+-]\\d+)/);\n return m ? Number(m[1]) * 60 : -240;\n};\n\nasync function contactsSince(floorMs: number, truncated: string[]): Promise {\n const out: ContactLite[] = [];\n let sa: string | undefined, sav: number | undefined;\n let reachedFloor = false;\n for (let page = 0; page < 30; page++) {\n const q = new URLSearchParams({ locationId: LOC, limit: \"100\" });\n if (sa && sav) { q.set(\"startAfterId\", sa); q.set(\"startAfter\", String(sav)); }\n const d = await j(`/contacts/?${q}`, \"2021-07-28\");\n const cs = d?.contacts ?? [];\n if (!cs.length) break;\n for (const c of cs) {\n // The FIRST attribution entry is the one flagged isFirst by the CRM, i.e. how this person\n // arrived, not how they last touched us. Later entries describe return visits.\n const a = (Array.isArray(c.attributions) ? c.attributions : []).find((x: any) => x?.isFirst) ?? c.attributions?.[0] ?? null;\n out.push({\n dateAdded: c.dateAdded, source: c.source ?? null, tags: c.tags ?? [],\n attribution: a ? { medium: a.medium ?? a.utmSessionSource ?? null, campaign: a.utmCampaign ?? null } : null,\n });\n }\n const oldest = Date.parse(cs[cs.length - 1]?.dateAdded ?? \"\");\n sa = d?.meta?.startAfterId; sav = d?.meta?.startAfter;\n if (Number.isFinite(oldest) && oldest < floorMs) { reachedFloor = true; break; }\n if (!sa) { reachedFloor = true; break; }\n }\n if (!reachedFloor) truncated.push(\"the older weeks of the chart\");\n return out;\n}\n\n// Ad platforms. Both are env-gated and honest: no token means \"not connected yet\", never a guess.\nasync function metaWeek(startMs: number, endMs: number, tz: number) {\n const tok = Deno.env.get(\"META_TOKEN\"), act = Deno.env.get(\"META_AD_ACCOUNT\");\n if (!tok || !act) return null;\n const day = (ms: number) => new Date(ms + tz * 60_000).toISOString().slice(0, 10);\n const r = await fetch(\n `https://graph.facebook.com/v21.0/${act}/insights?fields=spend,actions&time_range={\"since\":\"${day(startMs)}\",\"until\":\"${day(endMs - 86_400_000)}\"}`,\n { headers: { Authorization: `Bearer ${tok}` }, signal: AbortSignal.timeout(20_000) },\n ).catch(() => { throw new Error(\"Facebook did not answer\"); });\n if (!r.ok) {\n // A token that exists but has not been granted ad-reading rights is a SETUP state, not a\n // fault, and it must not reach Kim as \"Facebook returned 400\". Meta answers this exact case\n // with code 200 and a message naming ads_management/ads_read. Verified live on 4 Aug against\n // the real token: the system user was created without an app role, so it came out holding\n // only page permissions. Anything else genuinely is an error and says so.\n const body = await r.json().catch(() => null);\n const msg = String(body?.error?.message ?? \"\");\n if (body?.error?.code === 200 || /ads_read|ads_management/.test(msg)) throw new Error(\"PERMISSION\");\n throw new Error(`Facebook returned ${r.status}`);\n }\n const row = (await r.json())?.data?.[0];\n const acts = row?.actions ?? [];\n const conv = Number(acts.find((a: any) => a.action_type === \"onsite_conversion.total_messaging_connection\")?.value\n ?? acts.find((a: any) => a.action_type === \"lead\")?.value ?? 0);\n return { spend: Number(row?.spend ?? 0), conv };\n}\n// PROVEN LIVE 4 Aug 2026: this account has 5,695 opportunities and every single one carries\n// status \"open\", and nobody uses the won/lost flags. Counting `status=won` returns zero forever,\n// which would have rendered \"0 closed deals\" every week regardless of reality. The real signal\n// is the pipeline STAGE (Customer / Won-Paid), which the engine already uses for its exit rules.\n// Separately proven: every one of those records has monetaryValue 0, so the CRM holds no deal\n// values at all. The page therefore reports customer COUNT and says plainly that revenue is not\n// recorded, rather than printing a $0.00 that reads as \"we earned nothing\".\nconst STAGE_CUSTOMER = \"fd821b4e-bbe6-44de-b754-fa80e4823616\";\nconst STAGE_WON_PAID = \"ae173310-f8b1-4399-acb7-ef1fc03d3697\";\n\nasync function googleWeek() {\n const tok = Deno.env.get(\"GADS_TOKEN\");\n if (!tok) return null;\n throw new Error(\"Google Ads connector is coded but has never been run against a live account\");\n}\n\nconst esc = (s: unknown) => String(s ?? \"\").replace(/[&<>\"']/g, (c) => ({ \"&\": \"&\", \"<\": \"<\", \">\": \">\", '\"': \""\", \"'\": \"'\" }[c] as string));\n// The Friday report compares complete Friday-to-Thursday weeks; this page rolls the last 7 days.\n// Saying \"on last week\" here would mean something different from the same phrase there.\nconst vs = (a: number, b: number) => {\n if (a === b) return \"level with the 7 days before\";\n if (b === 0) return \"up from none the 7 days before\";\n const ch = Math.round(((a - b) / b) * 100);\n return `${ch > 0 ? \"up\" : \"down\"} ${Math.abs(ch)}% on the 7 days before`;\n};\nconst MONTHS = [\"Jan\", \"Feb\", \"Mar\", \"Apr\", \"May\", \"Jun\", \"Jul\", \"Aug\", \"Sep\", \"Oct\", \"Nov\", \"Dec\"];\nconst prettyDate = (iso: string) => {\n const m = /^(\\d{4})-(\\d{2})-(\\d{2})/.exec(iso || \"\");\n return m ? `${MONTHS[Number(m[2]) - 1] ?? m[2]} ${Number(m[3])}` : iso;\n};\nconst ago = (iso?: string | null) => {\n if (!iso) return \"never\";\n const m = Math.floor((Date.now() - Date.parse(iso)) / 60000);\n if (!Number.isFinite(m)) return \"unknown\";\n if (m < 1) return \"just now\";\n if (m < 60) return `${m} minute${m === 1 ? \"\" : \"s\"} ago`;\n const h = Math.floor(m / 60);\n if (h < 24) return `${h} hour${h === 1 ? \"\" : \"s\"} ago`;\n const d = Math.floor(h / 24);\n return `${d} day${d === 1 ? \"\" : \"s\"} ago`;\n};\n\n// ---- the holiday deposit card ----------------------------------------------------------------\n// EVERY WORD HERE IS ABOUT SOMEBODY ELSE'S MONEY, so the rules are tighter than anywhere else on\n// this page: it is a list to LOOK AT, never a list of people who owe. Cash and phone deposits do\n// not reach Square, so an absence of a payment is an absence of evidence and is worded that way.\n// A read that failed stays visibly unknown and is never quietly filed under \"nothing found\".\nconst DEP_STATE: Record = {\n seen: { label: \"Payment on file\", color: GOOD },\n partial: { label: \"Worth a look\", color: WARN },\n none_seen: { label: \"Worth a look\", color: WARN },\n could_not_check: { label: \"Could not check\", color: \"#6b7280\" },\n};\nexport function depositCard(dep: DepositBlob | null, readOk: boolean, agoFn: (s?: string | null) => string): string {\n if (!readOk) {\n return `
Holiday deposits
We could not read the deposit list just now. That is a problem reading it, not a finding about anybody. Refreshing in a few minutes normally fixes it.
`;\n }\n if (!dep || !dep.at) {\n return `
Holiday deposits
Nothing collected yet. This fills in the first time the deposit check runs.
`;\n }\n // Worth-a-look first, because that is the only part of this card that is a job to do. Inside each\n // group, soonest drop-off first: the deposit that matters most is the one arriving next.\n const order: Record = { none_seen: 0, partial: 1, could_not_check: 2, seen: 3 };\n const rows = [...(dep.rows ?? [])].sort((a, b) => (order[a.state] - order[b.state]) || a.day.localeCompare(b.day));\n const stayDates = (r: DepositRow) => r.until && r.until > r.day\n ? `${prettyDate(r.day)} to ${prettyDate(r.until)}` : prettyDate(r.day);\n const body = rows.map((r) => `${esc(r.name)}${esc(stayDates(r))}${esc((r.dogs ?? []).join(\", \") || (r.dogCount ? `${r.dogCount} ${r.dogCount === 1 ? \"dog\" : \"dogs\"}, names not recorded` : \"not recorded\"))}\n● ${esc(DEP_STATE[r.state]?.label ?? \"Worth a look\")}\n${esc(r.note)}${looksLikeTestRecord(r.name) ? \" This one looks like somebody testing the booking form rather than a customer, so check who it is before you call.\" : \"\"}`).join(\"\");\n const missed = dep.calendarsAsked && dep.calendarsRead < dep.calendarsAsked\n ? `
Not the whole picture: ${dep.calendarsAsked - dep.calendarsRead} of your ${dep.calendarsAsked} boarding calendars did not answer when this ran, so bookings on ${dep.calendarsAsked - dep.calendarsRead === 1 ? \"it are\" : \"them are\"} missing from the list below.
` : \"\";\n // A pick-up calendar that did not answer is the quiet one: the stays that go missing are exactly\n // the ones that start before a holiday and run into it, and the short list still looks complete.\n const noPickups = (dep.pickupsAsked ?? 0) && (dep.pickupsRead ?? 0) < (dep.pickupsAsked ?? 0)\n ? `
Not the whole picture: ${(dep.pickupsAsked ?? 0) - (dep.pickupsRead ?? 0)} of your ${dep.pickupsAsked} boarding pick-up calendars did not answer, so anyone who dropped off before a holiday and stayed through it may be missing from this list.
` : \"\";\n // COUNTS THE ROWS ON THE TABLE, not the customers behind them. [was: dep.readFailures, which\n // counts customers, so one customer with three holiday stays produced \"1 customer's payments\n // could not be read\" above a table showing three unknown rows and a headline saying 3.]\n const unknownRows = rows.filter((r) => r.state === \"could_not_check\").length;\n const unknowns = unknownRows\n ? `
${unknownRows === 1 ? \"1 stay\" : `${unknownRows} stays`} could not be checked when this ran, so ${unknownRows === 1 ? \"it is\" : \"they are\"} marked unknown rather than guessed at.
` : \"\";\n // EVERY ROW BELOW IS WRITTEN IN THE PRESENT TENSE. If the list is old, saying so at the bottom\n // in small print is not enough: somebody could have paid yesterday and the page would still read\n // \"no Square payment is on file\". Past a day and a half this goes at the TOP, where the reader\n // is before they start acting on names.\n const ageH = (Date.now() - Date.parse(dep.at)) / 3_600_000;\n const stale = Number.isFinite(ageH) && ageH > 36\n ? `
This list was last checked ${esc(agoFn(dep.at))}. Anyone who has paid since then will still show here as not found, so check the date before you act on a name.
` : \"\";\n return `
Holiday deposits
\n
${esc(dep.sentence)}
\n${stale}${missed}${noPickups}${unknowns}\n${dep.feedDead ? \"\" : rows.length ? `${body}
Who Stay Dogs Deposit
` : \"\"}\n
Windows checked: ${(dep.windows ?? []).map((w) => `${esc(w.name)} (${esc(prettyDate(w.from))} to ${esc(prettyDate(w.to))})`).join(\", \")}. $50 per dog, so a three-dog stay is $150. Only a card payment shows up here: Venmo, Zelle, a cheque or cash will not. Daycare, regular weekly bookings and cancellations are left out. Last checked ${esc(agoFn(dep.at))}.
\n
`;\n}\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n const k = url.searchParams.get(\"k\") || \"\";\n const admin = await isAdmin(k);\n if (!admin && !(await isViewer(k))) return new Response(\"Not found\", { status: 401 });\n\n const now = Date.now(), tz = ET();\n const wk = 7 * 86_400_000;\n const cur = { startMs: now - wk, endMs: now, label: \"last 7 days\" };\n const prev = { startMs: now - 2 * wk, endMs: now - wk, label: \"the 7 before\" };\n\n const cacheRead = await readBlob(CACHE_KEY);\n const cache = cacheRead.v ?? {};\n const stale: string[] = []; // sections served from cache, named for the reader\n const truncated: string[] = [];\n\n // v1.1 (review #1): every source runs CONCURRENTLY with its own budget. Sequentially, a merely\n // slow CRM could exceed the platform's request limit and the page would die entirely, which is\n // the one outcome this dashboard exists to prevent. Now the whole fetch phase costs one budget,\n // not the sum of them, and any single source can fail without touching the others.\n const BUDGET = 9_000;\n const budgeted = (p: Promise): Promise =>\n Promise.race([p, new Promise((_, rej) => setTimeout(() => rej(new Error(\"too slow\")), BUDGET))]);\n\n const [cRes, ptRes, oppRes, metaRes, tagRes, sqRes] = await Promise.allSettled([\n budgeted(contactsSince(now - 9 * wk, truncated)),\n budgeted((async () => {\n const d = await j(`/calendars/events?locationId=${LOC}&calendarId=${PUP_TALK_CAL}&startTime=${prev.startMs}&endTime=${now}`, \"2021-04-15\");\n return ((d?.events ?? []) as any[]).map((e: any) => ({\n startTime: typeof e.startTime === \"number\" ? e.startTime : Date.parse(e.startTime),\n appointmentStatus: e.appointmentStatus ?? \"unknown\", calendarId: PUP_TALK_CAL,\n })) as EventLite[];\n })()),\n budgeted((async () => {\n // PROVEN LIVE 4 Aug 2026, and this replaces a capped scan that was quietly wrong.\n //\n // The old version walked six pages of ALL 5,695 opportunities and filtered client side. Two\n // things were wrong with that. It flagged itself truncated, which suppressed the funnel and\n // put an \"at least this many\" caveat on the tile. And it undercounted: it found 2 new\n // customers in the last 7 days when the true figure is 5, because the ones it missed were\n // created long ago and only reached the Customer stage this week, so they sat deep in a list\n // ordered by creation date.\n //\n // Three facts make a complete scan affordable, each verified against the live account:\n // 1. `pipeline_stage_id` IS honoured server side. Customer holds 1,513 records, not 5,695.\n // 2. Pagination is strictly newest-first by createdAt, so page count is knowable up front.\n // 3. meta.total is returned on page 1, so the rest can be fetched at once rather than in\n // series. Sequentially those 16 pages cost 9.4s; in parallel they cost about one.\n // No sort parameter exists (six spellings probed, all 422), which is why the whole stage has\n // to be read: someone can reach Customer this week having been created a year ago.\n const STAGES = [STAGE_CUSTOMER, STAGE_WON_PAID];\n const page = (stage: string, p: number) =>\n j(`/opportunities/search?location_id=${LOC}&limit=100&page=${p}&pipeline_stage_id=${stage}`, \"2021-07-28\");\n const acc: OppLite[] = [];\n let complete = true;\n for (const stage of STAGES) {\n const first = await page(stage, 1);\n const total = Number(first?.meta?.total ?? 0);\n const pages = Math.min(Math.ceil(total / 100) || 1, 40); // 40 pages = 4,000 records, a sane backstop\n if (Math.ceil(total / 100) > 40) complete = false;\n const rest = await Promise.all(\n Array.from({ length: Math.max(0, pages - 1) }, (_, i) => page(stage, i + 2).catch(() => null)),\n );\n for (const d of [first, ...rest]) {\n if (!d) { complete = false; continue; }\n for (const o of d?.opportunities ?? []) {\n // `status` is carried through as the CRM reports it. It used to be overwritten with \"won\" on\n // the way in, which meant the page could not see the field it went on to make claims about.\n acc.push({ createdAt: o.createdAt, status: String(o.status ?? \"open\"), monetaryValue: Number(o.monetaryValue) || 0, lastStageChangeAt: o.lastStageChangeAt ?? null });\n }\n }\n }\n if (!complete) truncated.push(\"customers\");\n return acc;\n })()),\n budgeted(metaWeek(cur.startMs, cur.endMs, tz)),\n // The Square backlog used to be four numbers typed into a sentence, and all four were wrong:\n // it said 35 payments worth $23,463.99 when the journal holds 40 worth $28,035.99, and it\n // never split the money between the recoverable and the unrecoverable. Read live now.\n // THE TAG THAT DECIDES WHETHER GO-LIVE REACHES ANYBODY, counted server side over the whole\n // contact base rather than sampled. Two calls, both filtered, both returning a total.\n // [was: the number 1,200 typed into a decision's evidence — a scan size presented as an\n // answer. Cross-checked 5 Aug: this filter and a full page-by-page walk of all 5,544\n // contacts agree exactly on \"no sale\" (133), \"tips-nurture\" (155) and \"customer\" (1,512).]\n budgeted((async () => {\n const count = async (tag: string | null): Promise => {\n const body: Record = { locationId: LOC, pageLimit: 1 };\n if (tag) body.filters = [{ field: \"tags\", operator: \"contains\", value: tag }];\n const r = await fetch(`${GHL}/contacts/search`, {\n method: \"POST\",\n headers: { Authorization: `Bearer ${await token()}`, Version: \"2021-07-28\", \"User-Agent\": \"curl/8.5.0\", \"Content-Type\": \"application/json\" },\n body: JSON.stringify(body),\n signal: AbortSignal.timeout(8_000),\n });\n if (!r.ok) throw new Error(`contacts/search ${r.status}`);\n return Number((await r.json())?.total ?? 0);\n };\n const [tagged, total] = await Promise.all([count(ENROLL_TAG), count(null)]);\n return { tag: ENROLL_TAG, tagged, total } as TagCoverage;\n })()),\n budgeted((async () => {\n const r = await fetch(`${BRIDGE}?dump=1&admin=${encodeURIComponent(Deno.env.get(\"BRIDGE_ADMIN\") || BRIDGE_ADMIN)}`,\n { signal: AbortSignal.timeout(15_000) });\n if (!r.ok) throw new Error(`bridge ${r.status}`);\n return squareBacklog(await r.json());\n })()),\n ]);\n\n const contacts: ContactLite[] | null = cRes.status === \"fulfilled\" ? cRes.value : null;\n const tagCov: TagCoverage | null = tagRes.status === \"fulfilled\" ? tagRes.value : null;\n const ptEvents: EventLite[] | null = ptRes.status === \"fulfilled\" ? ptRes.value : null;\n const opps: OppLite[] | null = oppRes.status === \"fulfilled\" ? oppRes.value : null;\n const meta = metaRes.status === \"fulfilled\" ? metaRes.value : null;\n const square = sqRes.status === \"fulfilled\" ? sqRes.value : null;\n const metaRaw = metaRes.status === \"rejected\" ? String(metaRes.reason).replace(/^Error:\\s*/, \"\") : null;\n const metaPending = metaRaw === \"PERMISSION\"; // linked, but Facebook has not granted reading yet\n const metaErr = metaPending ? null : (metaRaw ? metaRaw.slice(0, 80) : null);\n\n // computed, or pulled from cache with an honest label\n const C = cache.numbers ?? {};\n const A = cache.ages ?? {}; // per-section ISO stamps: a three-day-old number must not read \"a few minutes ago\"\n const inq = contacts ? countContacts(contacts, cur) : (C.inq ?? null);\n const inqPrev = contacts ? countContacts(contacts, prev) : (C.inqPrev ?? null);\n const srcAll = contacts ? sourceBreakdown(contacts, cur) : (C.srcAll ?? null);\n // PROVEN LIVE 4 Aug 2026: the source column was blank for 154 of 190, while the attribution\n // record placed 190 of 190. The page used to print \"no source recorded: 154\" and then guess in\n // prose that most were Messenger. It now reads the field that actually holds the answer.\n const chan = contacts ? channelBreakdown(contacts, cur) : (C.chan ?? null);\n const camps = contacts ? campaignBreakdown(contacts, cur) : (C.camps ?? null);\n const cover = contacts ? attributionCoverage(contacts, cur) : (C.cover ?? null);\n const buckets = contacts ? weeklyBuckets(contacts, now, 8) : (C.buckets ?? null);\n const pt = ptEvents ? countEvents(ptEvents, cur) : (C.pt ?? null);\n const ptPrev = ptEvents ? countEvents(ptEvents, prev) : (C.ptPrev ?? null);\n // Everything in `opps` is already stage-filtered to Customer/Won-Paid, so the STAGE is the\n // signal; the CRM's own status field is left untouched so the page can report on it honestly.\n const stageWon = (list: OppLite[] | null, w: { startMs: number; endMs: number }) => list\n ? { count: list.filter((o) => { const t = Date.parse(o.lastStageChangeAt || o.createdAt); return Number.isFinite(t) && t >= w.startMs && t < w.endMs; }).length, value: 0 }\n : null;\n const won = opps ? stageWon(opps, cur) : (C.won ?? null);\n // How often a price actually gets written on a deal. The page used to state flatly that every\n // opportunity sat at zero, which a reader disproved from the page's own Bootcamp figures. It is\n // 53 of 1,513, none of them in the last month. Counted here rather than claimed.\n const won2Total = opps ? opps.length : (C.won2Total ?? null);\n const valued = opps ? opps.filter((o) => Number(o.monetaryValue) > 0).length : (C.valued ?? null);\n const valuedTotal = opps ? opps.reduce((a, o) => a + (Number(o.monetaryValue) || 0), 0) : (C.valuedTotal ?? null);\n // \"none at all in the last month\" was typed into the template and would have read true forever,\n // including on the day somebody wrote one. Measured now, from the same records.\n const valuedRecentMs = opps\n ? (opps.filter((o) => Number(o.monetaryValue) > 0)\n .map((o) => Date.parse(o.lastStageChangeAt || o.createdAt)).filter((t) => Number.isFinite(t))\n .reduce((a, b) => Math.max(a, b), 0) || null)\n : (C.valuedRecentMs ?? null);\n const lostCount = opps ? opps.filter((o) => String(o.status).toLowerCase() === \"lost\").length : (C.lostCount ?? null);\n const wonPrev = opps ? stageWon(opps, prev) : (C.wonPrev ?? null);\n const missing: string[] = []; // failed AND no cached value to fall back on\n if (!contacts) (C.inq != null ? stale : missing).push(\"new inquiries\");\n if (!ptEvents) (C.pt ? stale : missing).push(\"Pup Talks\");\n if (!opps) (C.won ? stale : missing).push(\"new customers\");\n\n let googleErr: string | null = null;\n try { await googleWeek(); } catch (e) { googleErr = String(e).replace(/^Error:\\s*/, \"\").slice(0, 90); }\n\n const runR = await readBlob(\"puppy_run_state\"); const run = runR.v;\n const wd = await getBlob(\"wd_public\");\n const killR = await readBlob(\"nurture_kill\"); const kill = killR.v;\n const stateR = await readBlob(\"puppy_state\"); const state = stateR.v ?? {};\n const stateKnown = stateR.ok, runKnown = runR.ok && killR.ok;\n const liveLog = await getBlob(\"tds_worklog\");\n // What the tagging WOULD do, written down by the engine on every run. It applies nothing.\n const tagScan = await getBlob<{ at?: string; summary?: DetectSummary; applied?: boolean }>(\"tag_candidates\");\n // THE HOLIDAY DEPOSIT LIST. Read from the blob the collector writes, never recomputed here: the\n // collection is dozens of CRM calls and Kim's page must not wait for them. A read that FAILS and\n // a list that is genuinely EMPTY are kept apart, because \"no holiday stays booked\" and \"we could\n // not check\" look identical on a screen and only one of them is safe to show in November.\n const depR = await readBlob(\"holiday_deposits\");\n const dep = depR.v;\n const log = mergeLog(SEEDED, liveLog);\n\n const crmSources = [[\"contacts\", !!contacts], [\"appointments\", !!ptEvents], [\"deals\", !!opps]] as const;\n const crmDown = crmSources.filter(([, ok]) => !ok).map(([n]) => n);\n const crmOk = crmDown.length === 0;\n const crmPartial = crmDown.length > 0 && crmDown.length < 3;\n const engineAgeMin = run?.ts ? Math.floor((now - Date.parse(run.ts)) / 60000) : null;\n const engineCadence = observedCadenceMin(run?.history);\n const engineLate = lateness(engineAgeMin, engineCadence);\n const engineOk = isHealthy(engineLate.state) && !kill?.stopped;\n const practice = run?.testMode !== false;\n const wdAgeMin = wd?.ts ? Math.floor((now - Date.parse(wd.ts)) / 60000) : null;\n // SCHEDULED runs only. A rhythm measured over hand-triggered runs is a measurement of the hand.\n // [was: observedCadenceMin(wd?.history), where history mixes both. It produced \"left to itself\n // it runs about every 95 minutes\" out of stamps that were almost entirely me pressing the\n // check-now button, and put that sentence in front of Kim as the watchdog's schedule. The\n // watchdog now records autoHistory separately; older payloads have no such field, and the\n // honest answer for those is \"we cannot tell yet\" rather than the old number.]\n const wdAuto: string[] | null = Array.isArray(wd?.autoHistory) ? wd.autoHistory : null;\n const wdTracksTrigger = wdAuto != null;\n const wdNeverRanItself = wdTracksTrigger && wdAuto.length === 0;\n const wdCadence = wdTracksTrigger ? observedCadenceMin(wdAuto) : null;\n const wdAutoAgeMin = wd?.lastAutoTs ? Math.floor((now - Date.parse(wd.lastAutoTs)) / 60000) : null;\n // Graded on when it last ran ITSELF, not on when it was last poked.\n const wdLate = wdNeverRanItself\n ? { state: \"late\" as const, dueAt: null, lateAt: null }\n : lateness(wdTracksTrigger ? wdAutoAgeMin : wdAgeMin, wdCadence);\n // When did we start being able to tell the difference? The first stamp after the change.\n const wdTrackingSince: string | null = wdTracksTrigger && Array.isArray(wd?.history) && wd.history.length\n ? wd.history[wd.history.length - 1] : null;\n const wdManualSince = wdTracksTrigger && Array.isArray(wd?.history)\n ? wd.history.filter((t: string) => !wdTrackingSince || Date.parse(t) >= Date.parse(wdTrackingSince)).length\n : 0;\n // A watchdog that has not looked recently is not a passing watchdog, whatever its last report\n // said. Grading it purely on the contents of a stale report is how a page ends up putting a\n // green tick beside a system that stopped running an hour ago.\n const wdOk = !!wd && (wd.worst === \"OK\" || wd.worst === \"INFO\") && isHealthy(wdLate.state);\n\n // v1.1 (reviews #3, #8): each section carries its OWN timestamp so staleness is reported per\n // number, and the whole write is skipped when the cache could not be read, so a transient blob\n // hiccup can never erase good history for a section that happens to be failing today.\n if (cacheRead.ok && (contacts || ptEvents || opps)) {\n const nowIso = new Date().toISOString();\n try {\n await (await blobMod()).setJSON(CACHE_KEY, {\n at: nowIso,\n numbers: {\n inq: contacts ? inq : C.inq, inqPrev: contacts ? inqPrev : C.inqPrev,\n srcAll: contacts ? srcAll : C.srcAll, buckets: contacts ? buckets : C.buckets,\n chan: contacts ? chan : C.chan, camps: contacts ? camps : C.camps,\n cover: contacts ? cover : C.cover,\n pt: ptEvents ? pt : C.pt, ptPrev: ptEvents ? ptPrev : C.ptPrev,\n won: opps ? won : C.won, wonPrev: opps ? wonPrev : C.wonPrev,\n won2Total: opps ? won2Total : C.won2Total, valued: opps ? valued : C.valued,\n valuedTotal: opps ? valuedTotal : C.valuedTotal,\n valuedRecentMs: opps ? valuedRecentMs : C.valuedRecentMs, lostCount: opps ? lostCount : C.lostCount,\n },\n ages: {\n inq: contacts ? nowIso : A.inq, pt: ptEvents ? nowIso : A.pt, won: opps ? nowIso : A.won,\n },\n });\n } catch { /* the cache is a nicety; never fail the page over it */ }\n }\n\n if (admin && url.searchParams.get(\"f\") === \"json\") {\n return new Response(JSON.stringify({ inq, inqPrev, pt, won, meta, stale, crmOk, engineOk, practice, wd }, null, 2),\n { headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" } });\n }\n\n // each stale section reports ITS OWN age, not the cache blob's last-write time\n const sectionAge = (label: string) =>\n label === \"new inquiries\" ? (A.inq ?? cache.at) : label === \"Pup Talks\" ? (A.pt ?? cache.at) : (A.won ?? cache.at);\n\n // An appointment nobody has marked is silently counted as \"not a no-show\", which flatters the\n // show-up figure. The page says so, using a number it counts live rather than one typed here.\n const unmarked = pt ? Math.max(0, pt.booked - pt.showed - pt.noshow) : null;\n const otherBucket = contacts ? otherBucketExplanation(contacts as any, cur) : null;\n const ctx: Ctx = {\n unmarkedPupTalks: unmarked,\n inquiriesPerWeek: inq ?? null,\n squareSentence: square ? squareSentence(square) : null,\n // null when the read failed, so the decision says \"unconfirmed\" rather than \"zero\".\n puppyTagSentence: tagCov ? tagCoverageSentence(tagCov) : null,\n // The dry tagging pass. Present only when the engine has actually run one.\n tagScanSentence: tagScan?.summary && tagScan.applied === false\n ? [detectSentence(tagScan.summary), scanAgeNote(tagScan.at, now)].filter(Boolean).join(\" \")\n : null,\n };\n // Both of these used to be typed into the sentence: \"four in five\" (it was 84%) and a claim that\n // the rest \"picked up the phone\" (the arrival record has no phone category at all, so the chart\n // could never show one). Derived now, or not stated.\n const socialShare = chan && inq\n ? Math.round(100 * (chan as any[]).filter((c) => /Facebook|Instagram/i.test(c.source)).reduce((a, c) => a + c.n, 0) / inq)\n : null;\n // No null-coalescing to zero anywhere in this region, deliberately: an unread source list must\n // stay null rather than become a confident zero. A missing phone row and a list we could not read\n // are different facts, and only one of them is safe to print. (The literal pattern is kept out of\n // this comment too, because the test that enforces the rule scans the region as text.)\n const phoneRow = srcAll ? (srcAll as any[]).find((s0) => /phone/i.test(s0.source)) : null;\n const phoneLogged: number | null = srcAll ? (phoneRow ? phoneRow.n : 0) : null;\n const decisions = sortedDecisions();\n const blocking = blockingCount();\n\n // ---- headline verdict ------------------------------------------------------------------\n const problems: string[] = [];\n if (!crmOk) problems.push(\"the CRM is not answering\");\n if (!runKnown) problems.push(\"we could not check whether the follow-up system is running\");\n else if (kill?.stopped) problems.push(\"the follow-up system is stopped\");\n else if (!engineOk) problems.push(\"the follow-up system is running late\");\n if (wd && wd.worst === \"CRITICAL\") problems.push(\"the watchdog found a problem\");\n else if (wd && wdNeverRanItself) problems.push(\"we cannot yet show the watchdog keeping its own time\");\n else if (wd && wdLate.state === \"late\") problems.push(\"the watchdog has not looked recently\");\n const allWell = problems.length === 0;\n // problems[] is built from fixed strings above, but it is still assembled text that reaches the\n // page: escaped at the point of use (the hero line calls esc(verdict)), and kept a plain join\n // here so the escape has exactly one place to live.\n // A row below can wear a warning triangle for being merely overdue, which is not a problem worth\n // alarming Kim about. But the headline may not then say \"everything is running\" as though nothing\n // on the page were marked: the reader can see the triangle, and a headline that ignores it is the\n // same contradiction the stranger test rejected, moved up one level. So the headline names it.\n const liveIssues = decisions.filter((d) => d.liveNow).length;\n const running = [engineLate.state, wd ? wdLate.state : \"ok\"].filter((x) => x === \"due\").length;\n const liveNote = liveIssues ? ` Separately, ${liveIssues === 1 ? \"one question below is marked\" : `${liveIssues} questions below are marked`} HAPPENING NOW: ${liveIssues === 1 ? \"that one is\" : \"those are\"} already affecting customers rather than waiting on go-live.` : \"\";\n const behindNote = running ? ` ${running === 1 ? \"One part of it is\" : `${running} parts of it are`} running a little behind schedule, which happens and sorts itself out.` : \"\";\n const verdict = allWell\n ? (runKnown && practice\n ? `Everything we run is healthy. The follow-up system is in practice mode, so it is not messaging anyone yet, and ${blocking === 0 ? \"nothing is holding that up\" : `${blocking} ${blocking === 1 ? \"thing is\" : \"things are\"} holding up switching it on`}.${liveNote}${behindNote}`\n : `Everything is running normally.${liveNote}${behindNote}`)\n : \"Needs a look: \" + problems.join(\", \") + \".\";\n\n const tile = (label: string, v: string, note: string, accent?: string) =>\n `
${esc(v)}
${esc(label)}
${esc(note)}
`;\n const na = (v: number | null | undefined) => (v == null ? \"n/a\" : String(v));\n\n const checkRow = (ok: boolean, name: string, detail: string) =>\n `
${ok ? \"✓\" : \"⚠\"}
${esc(name)}
${esc(detail)}
`;\n\n // channel chart: top 3 named sources + Other, labeled directly (secondary encoding, per the\n // dataviz rule that a sub-3:1 slot needs visible labels)\n // v1.2 (stranger test): the old build assigned color index 2 to BOTH the third named source\n // and the catch-all roll-up beside it, so two adjacent segments and their two legend swatches\n // were pixel-identical and could not be told apart by looking. A roll-up bucket is not a peer\n // of the named categories anyway; it now takes the recessive gray the dataviz rules reserve for\n // it, which frees all three categorical slots for real, distinguishable channels.\n const chanRows = (chan ?? []).slice(0, 3);\n const chanOther = (chan ?? []).slice(3).reduce((a: number, s: any) => a + s.n, 0);\n const chanTotal = (chan ?? []).reduce((a: number, s: any) => a + s.n, 0) || 1;\n const segs = [\n ...chanRows.map((s: any, i: number) => ({ ...s, fill: `var(--c${i})` })),\n ...(chanOther ? [{ source: \"smaller channels added up\", n: chanOther, fill: \"var(--barq)\" }] : []),\n ];\n const share = (n: number) => `${Math.round((n / chanTotal) * 100)}%`;\n const chanBar = segs.map((s: any) =>\n ``).join(\"\");\n // Every row carries its share as well as its count. A bare 154 is a number; 81% is a decision.\n const chanLegend = segs.map((s: any) =>\n `
${esc(s.source)}${s.n} (${share(s.n)})
`).join(\"\");\n const campTop = (camps ?? []).slice(0, 5);\n const campShown = campTop.reduce((a: number, c: any) => a + c.n, 0);\n const campTotal = (camps ?? []).reduce((a: number, c: any) => a + c.n, 0);\n const campRows = campTop.map((c: any) =>\n `
${esc(c.name)}${c.n}
`).join(\"\");\n\n const maxB = Math.max(1, ...((buckets ?? [1]) as number[]));\n const bars = ((buckets ?? []) as number[]).map((b, i, arr) =>\n `
${b}
`).join(\"\");\n\n const adCard = (name: string, connected: boolean, spend: string, result: string, note: string) =>\n `
${esc(name)}
${connected\n ? `
${esc(spend)}
spent, last 7 days
${esc(result)}
conversations started
`\n : `
${esc(note)}
`}
`;\n\n // Kim's reading order, from her own test: banner, first blocker, the four numbers, gone. The\n // history is the part she cannot act on, so it is the part that folds; the asks stay open.\n const LOG_SHOWN = 6;\n const logRow = (e: WorkEntry) => {\n const col = e.kind === \"broke\" ? CRIT : e.kind === \"mine\" ? WARN : e.kind === \"found\" ? WARN : GOOD;\n return `
${esc(KIND_LABEL[e.kind] ?? e.kind)}
${esc(e.what)}
${e.evidence ? `
How we know: ${esc(e.evidence)}
` : \"\"}
${esc(prettyDate(e.at))}
`;\n };\n const logRows = log.slice(0, LOG_SHOWN).map(logRow).join(\"\");\n const logRest = Math.max(0, log.length - LOG_SHOWN);\n const logRestRows = log.slice(LOG_SHOWN).map(logRow).join(\"\");\n\n // Eight-week direction. The tiles compare one week to the week before, which is noise at this\n // volume: the account's own week-on-week swings run to plus and minus thirty. The trend across\n // the whole chart is the sentence the reader actually wants, and it was the one thing on the\n // page nobody was saying out loud.\n const trendLine = (() => {\n const b = (buckets ?? []) as number[];\n if (b.length < 4) return \"\";\n const firstHalf = b.slice(0, Math.floor(b.length / 2)), lastHalf = b.slice(-Math.floor(b.length / 2));\n const a = firstHalf.reduce((x, y) => x + y, 0) / firstHalf.length;\n const z = lastHalf.reduce((x, y) => x + y, 0) / lastHalf.length;\n if (!a) return \"\";\n const ch = Math.round(((z - a) / a) * 100);\n if (Math.abs(ch) < 10) return `Averaged out, inquiries are running about level across these eight weeks, near ${Math.round(z)} a week.`;\n return `Averaged out, inquiries are ${ch > 0 ? \"up\" : \"down\"} ${Math.abs(ch)}% across these eight weeks: about ${Math.round(a)} a week over the first month, about ${Math.round(z)} a week over the last month.`;\n })();\n\n // The first reader's whole test was ninety seconds in a car park. Answering the second and third\n // readers added items until this card had twelve, which would have pushed every number below the\n // fold and failed her test to satisfy theirs. So the ones that actually hold up go-live are set\n // out in full, and the rest are listed as plain questions behind a fold she opens if she wants.\n // Nothing is hidden: the full text of every one is in the page, one tap away, and the count is\n // stated. It is an ordering decision, not an omission.\n // Numbered, because the page asks thirteen questions and gives her no way to answer them except\n // a message. \"Yes to 1 and 4\" is a reply she can type one-handed at 6am. An unnumbered list is\n // not.\n const numberOf = new Map(decisions.map((d, i) => [d.ref, i + 1]));\n const full = (d: Decision) =>\n `
${d.liveNow ? \"Happening now\" : esc(WEIGHT_LABEL[d.weight])}
` +\n `
${numberOf.get(d.ref)}. ${esc(d.ask)}
${esc(whyText(d, ctx))}
` +\n `
How we know: ${esc(evidenceText(d, ctx))}
` +\n (ifYesText(d, ctx) ? `
If you say yes: ${esc(ifYesText(d, ctx))}
` : \"\") +\n (extraText(d, ctx) ? `
${esc(extraText(d, ctx))}
` : \"\") +\n `
If you say nothing: ${esc(d.ifNothing)}
`;\n // Shown in full: anything that blocks go-live, AND anything already affecting real customers.\n // The first draft of this fold put a live double-messaging issue behind a summary reading \"none\n // of which hold anything up\", one line under a banner announcing it. Blocking and live-now are\n // different reasons to be at the top, and both earn it.\n const upFront = (d: Decision) => d.weight === \"blocking\" || !!d.liveNow || !!d.surface;\n const blockers = decisions.filter(upFront);\n const rest = decisions.filter((d) => !upFront(d));\n const decRows = blockers.map(full).join(\"\")\n + (rest.length\n ? `
${rest.length} more, none of which hold anything up${rest.some((d) => d.liveNow) ? `, though ${rest.filter((d) => d.liveNow).length === 1 ? \"one is\" : `${rest.filter((d) => d.liveNow).length} are`} already running against customers` : \" or affect anybody today\"}
${rest.map(full).join(\"\")}
`\n : \"\");\n\n // THE FUNNEL. Every piece of this was already on the page and the page never put it together.\n // A reader called it \"the whole ballgame\": assembled, it says what share of inquiries becomes a\n // customer. Rendered only when every step read successfully, because a funnel with a hole in it\n // invites exactly the wrong conclusion.\n const funnelReady = inq != null && pt != null && won != null && !truncated.includes(\"customers\");\n const rate = (a: number, b: number) => (b > 0 ? `${(100 * a / b).toFixed(a / b < 0.1 ? 1 : 0)}%` : \"n/a\");\n const funnelRows = funnelReady\n ? [\n { label: \"New inquiries\", n: inq as number, of: null as string | null },\n { label: \"Pup Talks on the calendar\", n: pt!.booked, of: `${rate(pt!.booked, inq as number)} of inquiries` },\n { label: \"Showed up\", n: pt!.showed, of: `${rate(pt!.showed, pt!.booked)} of the ${pt!.booked} that were held${pt!.cancelled ? `, ${rate(pt!.showed, pt!.booked + pt!.cancelled)} of all ${pt!.booked + pt!.cancelled} booked` : \"\"}` },\n { label: \"Became customers\", n: won!.count, of: \"in the same 7 days, but mostly from earlier inquiries\" },\n ]\n : [];\n const funnelMax = Math.max(1, ...funnelRows.map((r) => r.n));\n const funnelHtml = funnelRows.map((r, i) =>\n `
${esc(r.label)}
` +\n `
${i === 3\n ? \"\"\n : ``}
` +\n `
${r.n}${r.of ? ` ${esc(r.of)}` : \"\"}
`).join(\"\");\n\n // The page said \"1 in a sequence: people currently walking through the follow-up messages\".\n // That one record is the sanctioned test dummy (contact mxf92ajJDtsZMHqJxAKv, every one of its\n // sends flagged test:true). Calling a synthetic record a person is the single most misleading\n // thing this page has ever said, so the count of REAL people is derived separately and the copy\n // branches on it rather than on the raw total.\n const isTestRecord = (k: string, v: any) =>\n v?.test === true || v?.isTest === true || /dummy|zztest/i.test(String(v?.name ?? v?.contactName ?? \"\")) || k === TEST_DUMMY_ID;\n const SOURCE_TAG = \"nurture - puppy\";\n const TEST_DUMMY_ID = \"mxf92ajJDtsZMHqJxAKv\";\n const ENROLLED = [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"];\n const realPeople = Object.entries(state).filter(([k, v]: any) =>\n ENROLLED.includes(v?.status) && !isTestRecord(k, v)).length;\n const activeN = Object.values(state).filter((s: any) =>\n [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"].includes(s?.status)).length;\n const pausedN = Object.values(state).filter((s: any) => s?.status === \"paused_reply\").length;\n\n const html = `\n\nThe Dogs Spot dashboard\n
\n\n
The Dogs Spot
\n
This page reads your systems the moment you open it. Refresh any time.
\n\n
${allWell ? \"✓\" : \"⚠\"} ${esc(verdict)}
\n${decisions.length ? `
${decisions.length} question${decisions.length === 1 ? \"\" : \"s\"} on this page ${decisions.length === 1 ? \"is\" : \"are\"} waiting on a word from you, ${blocking} of ${blocking === 1 ? \"which holds\" : \"which hold\"} up go-live. They are the first card below, most pressing first.
` : \"\"}
\n\n
Waiting on you
\n
The first few hold up go-live. The rest can wait as long as you like. Each one says how we know it is real and what happens if you never answer, because for most of them the answer is nothing bad. They are numbered, so a reply saying \"yes to 1 and 3\" is a complete answer. The numbers stay attached to the same questions week to week, so the list below runs out of order once the quieter ones are tucked away. Send it to Amir on Upwork, or say it on the next call.
\n${decRows}\n
\n\n${stale.length || missing.length || truncated.length ? `
Heads up: ${\n stale.length ? `${esc(stale.map((s) => `${s} (last read ${ago(sectionAge(s))})`).join(\", \"))} could not be read at this moment, so ${stale.length === 1 ? \"that number is the last one\" : \"those numbers are the last ones\"} we read successfully. ` : \"\"\n}${missing.length ? `${esc(missing.join(\" and \"))} could not be read and there is no earlier reading to show, so ${missing.length === 1 ? \"it shows\" : \"they show\"} as n/a. ` : \"\"\n}${truncated.length ? `you have enough records that we stopped reading partway through rather than keep you waiting, so ${truncated.length === 1 ? \"the count of\" : \"the counts of\"} ${esc(truncated.join(\" and \"))} ${truncated.length === 1 ? \"is a floor\" : \"are floors\"}, not ${truncated.length === 1 ? \"a total\" : \"totals\"}. The real number is that one or higher, never lower. ` : \"\"\n}Every other number on this page was read fresh just now. Refreshing in a few minutes normally gets the rest.
` : \"\"}\n\n
\n${tile(\"New inquiries\", na(inq), inq != null && inqPrev != null ? `last 7 days, ${vs(inq, inqPrev)}` : \"last 7 days\", undefined)}\n${tile(\"Pup Talks on the calendar\", pt ? String(pt.booked) : \"n/a\", pt && ptPrev ? `held in the last 7 days, ${vs(pt.booked, ptPrev.booked)}` : \"held in the last 7 days\")}\n${tile(\"Showed up\", pt ? String(pt.showed) : \"n/a\", pt ? (() => {\n const un = Math.max(0, pt.booked - pt.showed - pt.noshow);\n const bits = [`of the ${pt.booked} held`];\n if (pt.noshow) bits.push(`${pt.noshow} did not show`);\n // every appointment in the denominator has to be accounted for, or the reader is left doing\n // subtraction on the front tile and finding a number missing\n if (un) bits.push(`${un} ${un === 1 ? \"has\" : \"have\"} not been marked yet, so this figure is flattering by up to ${un}`);\n const tail = pt.cancelled ? ` A further ${pt.cancelled} cancelled ahead of time and ${pt.cancelled === 1 ? \"is\" : \"are\"} not counted in the ${pt.booked}.` : \"\";\n return bits.join(\", \") + \".\" + tail;\n })() : \"last 7 days\")}\n${tile(\"New customers\", won ? String(won.count) : \"n/a\", truncated.includes(\"customers\") ? \"reached the Customer stage. At least this many: see the note above\" : won && wonPrev ? `reached the Customer stage, ${vs(won.count, wonPrev.count)}` : \"reached the Customer stage, last 7 days\", undefined)}\n
\n\n${depositCard(dep, depR.ok, ago)}\n\n${funnelReady ? `
From first contact to paying customer
\n
Four counts over the same 7 days. An inquiry is any new person who reached you and landed in your CRM: a Facebook or Instagram message, a form, the chat box, or a phone call somebody logged.
\n${funnelHtml}\n
Before reading that first gap as bad news: ${socialShare != null ? `${socialShare}% of these inquiries` : \"most of these inquiries\"} arrived as a message on Facebook or Instagram, and a message costs the sender nothing, so plenty were never close to booking. Worth knowing what this cannot tell you: your CRM's arrival record has no category for a phone call at all, so callers are not separated out here. The old source column logged ${esc(String(phoneLogged ?? \"some\"))} phone calls this week, but that column is blank for most people, so neither of us can put a firm number on how many of these actually rang you. The first three rows follow the same people through. The last one does not, and it would be dishonest to draw an arrow to it: somebody who became a customer this week usually first got in touch weeks or months ago, so they are not part of the ${esc(String(inq))} above. Read it as four true counts over the same seven days rather than one conversion rate. The gap between inquiries and Pup Talks is the widest of them, and it is the one worth a conversation.
\n
` : \"\"}\n\n
Is everything working?
\n${checkRow(crmOk, \"Your CRM\", crmOk ? \"Answering normally. This page just read it.\" : crmPartial ? `Answered for some things but not for ${esc(crmDown.join(\" and \"))} just now. If this is still showing in an hour, tell Amir.` : \"Did not answer just now. If this is still showing in an hour, tell Amir.\")}\n${checkRow(engineOk, \"The follow-up system\", kill?.stopped\n ? \"Stopped by the big red button. Nothing is being sent.\"\n : engineAgeMin == null ? \"No check-in recorded yet.\"\n : `Last checked itself ${ago(run?.ts)}. ${lateSentence(engineLate, engineCadence)}`)}\n${checkRow(wdOk, \"The watchdog\", wd\n ? wdNeverRanItself\n ? `${wd.headline} Last look ${ago(wd.ts)}, started by hand. ${neverRanItselfSentence(wdTrackingSince, wdManualSince)}`\n : `${wd.headline} Last look ${ago(wd.ts)}. ${lateSentence(wdLate, wdCadence)}${wdLate.state === \"late\" ? \" Treat that last report as out of date until it looks again.\" : \"\"}`\n : \"No report from the watchdog yet.\")}\n${meta ? checkRow(true, \"Facebook ad spend\", \"Connected and reporting. Your spend is in the advertising section below.\")\n : metaPending ? `
•
Facebook ad spend
Half connected. Your ad account is named here, and Facebook has not yet given us permission to read what you spend on it, so the connection does not work yet. That is one setting on Amir's side, not a fault. It is the only reason this page can show you what came in but not what it cost.
`\n : metaErr ? checkRow(false, \"Facebook ad spend\", `Not reading right now: ${metaErr}`)\n : `
•
Facebook ad spend
Not linked yet, so this page cannot show what you spent. Where your inquiries came from is shown below regardless, because that comes from your own records rather than from Facebook.
`}\n
\n\n
Where the last 7 days of inquiries came from
\n${chan ? `
${chanBar}
${chanLegend}
` : `
Could not read this just now.
`}\n${cover ? `
${cover.known === cover.total ? `Every one of these ${cover.total}` : `${cover.known} of these ${cover.total}`} carries a record of how they arrived, though for some that record just says \"other\", so treat the named channels as the solid part. Worth knowing: the CRM's own \"source\" column is blank for ${esc(String(((srcAll ?? []) as any[]).find((s: any) => s.source === \"no source recorded\")?.n ?? 0))} of these, so any list built off that column will look like you have no idea where your customers come from. You do. It is recorded one field over.
` : \"\"}\n${otherBucket && otherBucketSentence(otherBucket) ? `
${esc(otherBucketSentence(otherBucket))}
` : \"\"}\n${campRows ? `
Which ads they answered
${campRows}
${\n campShown < campTotal\n ? `The ${Math.min(5, (camps ?? []).length)} biggest, covering ${campShown} of the ${campTotal} people who answered a named ad. The remaining ${campTotal - campShown} are spread across ${Math.max(0, (camps ?? []).length - 5)} smaller ones. `\n : `All ${campTotal} people who answered a named ad. `\n}${inq != null && campTotal < inq ? `The other ${inq - campTotal} of your ${inq} inquiries came in without a campaign attached, which is normal for people who message you directly rather than clicking an ad. ` : \"\"}These are the campaign names exactly as they appear in your ad account. Counted from your own records rather than from Facebook, so it stays true whether or not the ad account is linked.
` : \"\"}\n
\n\n
New inquiries, week by week
\n${buckets ? `
${bars}
Eight weeks, oldest on the left. The last bar is the last 7 days.${trendLine ? ` ${esc(trendLine)}` : \"\"}
` : `
Could not read this just now.
`}\n
\n\n${meta || metaErr ? `
What the advertising cost
\n${adCard(\"Facebook and Instagram\", !!meta, meta ? money(meta.spend) : \"\", meta ? String(meta.conv) : \"\", metaErr ? `Not reading right now: ${metaErr}` : \"\")}\n${meta ? `
Spend covers the seven full days up to yesterday, which is the last day the ad platform reports as final. Set against the ${esc(String(inq ?? \"n/a\"))} inquiries above, that is ${meta && inq ? esc(money(meta.spend / inq)) : \"n/a\"} each.
` : \"\"}\n${googleErr ? `
Google: ${esc(googleErr)}
` : \"\"}\n
` : \"\"}\n\n
What we have been doing
\n
Newest first. Each line names how it was checked, so you can pick any one and hold it up against the thing itself. Anything marked \"my mistake\" is one of mine, kept here on purpose rather than quietly fixed.
\n${logRows || `
Nothing recorded yet.
`}\n${logRest ? `
${logRest} older ${logRest === 1 ? \"entry\" : \"entries\"}
${logRestRows}
` : \"\"}\n
\n\n
One thing worth fixing in the CRM
\n
${valued != null && valuedTotal != null && won2Total\n ? `A price gets written on about one deal in ${Math.max(2, Math.round(won2Total / Math.max(1, valued)))}: ${valued} of your ${won2Total} customer records carry one, ${money(valuedTotal)} between them. The most recent was ${valuedRecentMs ? esc(prettyDate(new Date(valuedRecentMs).toISOString()) + \" \" + new Date(valuedRecentMs).getUTCFullYear()) : \"further back than these records reach\"}. So the habit exists and it lapsed.`\n : \"Most of your deals do not carry a value.\"}${lostCount != null ? ` Across all ${won2Total} of those records, ${lostCount === 0 ? \"not one is marked won or lost\" : `${lostCount} ${lostCount === 1 ? \"is\" : \"are\"} marked lost and none at all are marked won`}.` : \"\"} So to be plain about it: this card carries no money in it, in or out, only counts of people. That is why it counts people reaching the Customer stage rather than showing you revenue: a figure built on that few would be worse than no figure at all. Writing the price on each deal as it closes is the single change that would let this page show you what a week was worth.
\n\n
The follow-up system, in detail
\n${runKnown\n ? `
${practice ? \"⚠\" : \"✓\"}
${practice ? \"Practice mode\" : \"Live\"}
${practice ? \"It is doing everything except actually sending. Nobody real is being messaged. It goes live only when you say the word.\" : \"Real messages are going to real people.\"}
`\n : `
⚠
Practice or live: could not check
The system's own record did not answer just now, so this page will not guess. Refresh in a minute.
`}\n${stateKnown\n ? `
0 ? WARN : GOOD}\">${pausedN > 0 ? \"⚠\" : \"✓\"}
${pausedN > 0 ? `${pausedN} person${pausedN === 1 ? \"\" : \"s\"} replied and ${pausedN === 1 ? \"is\" : \"are\"} waiting on you` : \"Nobody is waiting on a reply from you\"}
${pausedN > 0 ? \"The system stepped back the moment they wrote to you. Answer them in your inbox; that is the only job this system ever hands you.\" : \"When somebody replies, the system stops messaging them and they appear here. That is the only job it ever hands you.\"}
\n
${realPeople ? \"✓\" : \"⚠\"}
${realPeople === 0 ? \"Nobody real is in the sequence yet\" : `${realPeople} in a sequence`}
${realPeople === 0\n ? `In practice mode the system runs against ${activeN === 0 ? \"no records at all\" : `${activeN} test record${activeN === 1 ? \"\" : \"s\"} of ours`} and has never sent to or processed one of your actual inquiries. That is deliberate: it is how we prove the machinery works without touching anybody. People join by carrying the tag \"${esc(SOURCE_TAG)}\". A person can put that tag on today, and anyone marked simply waits, untouched, until the switch is thrown. No automation applies the tag yet, so that tagging gets switched on in the same move as go-live.`\n : \"People currently walking through the follow-up messages.\"}
`\n : `
⚠
Who is in the system: could not check
This page will not show you a zero it cannot stand behind. Refresh in a minute.
`}\n
\n\n
Read live ${esc(prettyDate(new Date(now + tz * 60_000).toISOString()) + \" at \" + new Date(now + tz * 60_000).toISOString().slice(11, 16))} Georgia time. The four counts at the top, the funnel, both breakdowns and the week-by-week chart ${stale.length || missing.length || truncated.length ? \"were read from your own systems just now, apart from the ones named at the top\" : \"were read from your own systems just now\"}. The questions and the list of work are written by hand, and each one carries the check that backs it.
\n
`;\n\n return new Response(html, { headers: { \"content-type\": \"text/html; charset=utf-8\", \"cache-control\": \"no-store\" } });\n}\n",[300],"83ca8078-cab9-4f96-b5f5-89120b8838d2","cadence.ts","14aa659c-902f-11f1-8dc5-1607ee4eb77e",178,["D",1785930139649],"// HOW OFTEN DOES IT ACTUALLY RUN. v1.0, 4 Aug 2026.\n//\n// WHY THIS FILE EXISTS: the dashboard told Kim \"the follow-up system runs every 15 minutes\"\n// because a human typed that sentence, not because anything had measured it. A stranger reading\n// the page cold caught it in one pass: the same health row said \"last checked itself 26 minutes\n// ago\" and \"it runs every 15 minutes\", with a green tick beside both. The claim and the evidence\n// were contradicting each other on screen and the claim was winning.\n//\n// The scheduler's interval is not readable through any API (four candidate routes probed on\n// 4 Aug, all 404), so the only honest source of truth is the footprints each system leaves. The\n// engine now records the timestamp of every run; these functions read the gaps between them.\n// Nobody gets to type the cadence any more, which means nobody can get it wrong.\n\n/** Median minutes between consecutive runs, or null when the evidence is too thin to claim one. */\nexport function observedCadenceMin(history: unknown): number | null {\n const ts = (Array.isArray(history) ? history : [])\n .map((x) => Date.parse(String(x))).filter((n) => Number.isFinite(n)).sort((a, b) => a - b);\n if (ts.length < 3) return null;\n const gaps: number[] = [];\n for (let i = 1; i < ts.length; i++) {\n const g = (ts[i] - ts[i - 1]) / 60000;\n // A same-minute duplicate is a double write, not an interval. A multi-day hole is a deploy or\n // an outage, not an interval. Reading either as \"the rhythm\" would let one bad night convince\n // the page that a 15-minute system normally runs daily, and then nothing would ever look late.\n if (g >= 1 && g <= 24 * 60) gaps.push(g);\n }\n if (gaps.length < 2) return null;\n gaps.sort((a, b) => a - b);\n const mid = Math.floor(gaps.length / 2);\n return Math.round(gaps.length % 2 ? gaps[mid] : (gaps[mid - 1] + gaps[mid]) / 2);\n}\n\n/**\n * Late relative to the rhythm the system actually keeps, not to a number somebody hoped for.\n *\n * THREE states, not two, and the middle one is the point. A single missed turn on a system that\n * batches daily messages is not a business problem, so raising an alarm for it would train the\n * reader to ignore alarms, and the day one matters nobody looks. But printing a plain green tick\n * beside a visibly overdue timestamp is what the stranger test caught and refused to accept: the\n * reader could see the gap, and the page was pretending not to. So an overdue-but-not-alarming\n * system gets its own word. The reader is told it is behind, and told that being behind here is\n * ordinary. Nothing is hidden and nothing is dramatised.\n *\n * ok within half a cycle of schedule\n * due past due, one missed turn or so. Says so out loud. Not a fault, not a green tick either.\n * late two and a half cycles behind, floor 30 minutes. This one reaches the headline verdict.\n *\n * With no measured rhythm the thresholds are a flat 60 and 90 minutes, so \"we have not measured\n * it yet\" cannot quietly become infinite patience for a system that has genuinely stopped.\n */\nexport function lateness(ageMin: number | null, cadenceMin: number | null): {\n state: \"ok\" | \"due\" | \"late\" | \"unknown\"; dueAt: number | null; lateAt: number | null;\n} {\n if (ageMin == null) return { state: \"unknown\", dueAt: null, lateAt: null };\n const dueAt = cadenceMin ? cadenceMin * 1.5 : 60;\n const lateAt = cadenceMin ? Math.max(cadenceMin * 2.5, 30) : 90;\n const state = ageMin > lateAt ? \"late\" : ageMin > dueAt ? \"due\" : \"ok\";\n return { state, dueAt, lateAt };\n}\n/** Does this state deserve a tick? Only a system on schedule does. */\nexport const isHealthy = (s: ReturnType[\"state\"]) => s === \"ok\";\n\n/**\n * Append this run's stamp to the trail a system leaves behind, given whatever the previous blob\n * held. Lives here rather than in the engine because main.ts sits against a hard 80,000-character\n * ceiling on the platform, and because the writer and the reader of this trail should agree on its\n * shape by sharing one definition instead of two that drift.\n *\n * Seeds from a pre-history state's own `ts` so the very next run already yields one real gap\n * rather than starting the evidence from nothing. Never appends a duplicate of the last stamp.\n */\nexport const RUN_HISTORY_MAX = 40;\nexport function appendRunStamp(prev: any, ts: string): string[] {\n let h: string[] = Array.isArray(prev?.history) ? prev.history.filter((x: unknown) => typeof x === \"string\") : [];\n if (!h.length && typeof prev?.ts === \"string\") h = [prev.ts];\n if (h[h.length - 1] !== ts) h.push(ts);\n return h.slice(-RUN_HISTORY_MAX);\n}\n\n/**\n * One sentence for the reader, combining the verdict and the yardstick it was measured against.\n *\n * The previous version printed those two separately and produced a flat contradiction that a\n * reader caught at once: \"Its next look is a little overdue\" immediately followed by \"There is not\n * enough history yet to say how often it normally runs.\" You cannot call a thing late and in the\n * same breath say you do not know when it was due. Both sentences were individually true, because\n * an unmeasured system still falls back to a flat one-hour expectation, but nothing on the page\n * said so. Now the yardstick is never separated from the judgement that used it.\n */\nexport function lateSentence(l: ReturnType, cadenceMin: number | null): string {\n const rhythm = cadenceMin == null\n ? \"We have not watched it long enough to know its usual rhythm, so for now we expect it at least once an hour\"\n : `Left to itself it runs about every ${cadenceMin} minute${cadenceMin === 1 ? \"\" : \"s\"}`;\n if (l.state === \"unknown\") return `${rhythm}, and there is no check-in on record to compare against.`;\n if (l.state === \"late\") return `${rhythm}, and it is well past that. If it is still behind in an hour, tell Amir.`;\n if (l.state === \"due\") return `${rhythm}, and it is a little past that now. One late turn is ordinary; several in a row is not.`;\n return `${rhythm}, and it is on time.`;\n}\n/**\n * The sentence for a system that is supposed to run on a schedule and, as far as anything can\n * tell, is not. Kept separate from lateSentence because \"it is a bit late\" and \"it has never\n * started on its own\" are different facts and must not share a phrasing.\n *\n * WHY THIS EXISTS. The watchdog reported a rhythm of \"about every 95 minutes\". That number was\n * computed from its run stamps, honestly, and it was still wrong: nearly every stamp was a human\n * pressing the check-now button. The page was describing my own button presses back to Kim as the\n * watchdog's schedule.\n *\n * IT MUST NOT GUESS WHY.\n * [was: \"Nothing has started it on its own, which means its timer is not firing.\" First half an\n * observation, second half a conclusion, and the conclusion was wrong. I opened the schedule on\n * 5 August and found it set to once every 24 hours, deliberately, a week earlier. The timer was\n * firing perfectly. It was just slower than the window I had been watching, and everything else\n * in the history was a person. I had already written \"the timer has never fired\" into a message\n * and onto Kim's page before I looked. An empty record of scheduled runs means exactly that:\n * report the gap, and let somebody open the settings.]\n *\n * `sinceIso` is when the system started telling scheduled runs apart from manual ones. Saying so\n * matters: an empty record since this morning is not the same claim as \"it has never run\".\n */\nexport function neverRanItselfSentence(sinceIso: string | null, manualCount: number): string {\n const since = sinceIso\n ? `Since ${new Date(sinceIso).toLocaleDateString(\"en-US\", { month: \"long\", day: \"numeric\" })} this system has recorded which of its checks were scheduled and which were started by hand.`\n : \"This system now records which of its checks were scheduled and which were started by hand.\";\n const manual = manualCount > 1\n ? ` ${manualCount} checks have run since then, every one started by hand.`\n : manualCount === 1\n ? \" One check has run since then, and it was started by hand.\"\n : \" Nothing has run since then either way.\";\n return `${since}${manual} Nothing on a schedule has been recorded in that time. Everything it checks is still being checked, because Amir has been running it by hand, but we cannot yet show you it keeping its own time. Nothing else on this page is affected either way.`;\n}\n\n/** Kept for callers that only want the yardstick. */\nexport function cadenceSentence(cadenceMin: number | null): string {\n return cadenceMin == null\n ? \"There is not enough history yet to say how often it normally runs.\"\n : `Left to itself it runs about every ${cadenceMin} minute${cadenceMin === 1 ? \"\" : \"s\"}.`;\n}\n",[308],"bf9883fe-ce8a-4b1a-a33f-f883c67a772d","api.ts",51,["D",1785861568654],11,"// NURTURE CONTROL PANEL, HTTP face of the puppy-path engine. Built 2 Aug 2026.\n//\n// WHY THIS FILE EXISTS\n// The engine (main.ts) keeps everything it knows in val.town blobs. Blobs are reachable only with a\n// blob-scoped API token, which means the only people who could see whether the nurture system was\n// working were people holding a production credential. That is the wrong shape for this client: Kim\n// cancelled her previous supplier for going quiet, and a system whose status is invisible to her is\n// the same failure wearing different clothes.\n//\n// So the engine gets a front door. One URL, one key, no login, no install. It answers three\n// questions in plain language, who is in the system, what happened today, is anything broken, and\n// carries the one control she must always have: STOP.\n//\n// WHAT IT IS NOT\n// Read-mostly by design. The only state it writes is the kill switch. It cannot enrol anyone, send\n// anything, or edit copy. A leaked link is an information disclosure, not a way to message her\n// customers.\n//\n// AUTH\n// ?k=. Constant-time-ish compare, no key echoed back, no data before the check,\n// and the 401 body is byte-identical whether the key is absent or wrong.\n//\n// ROUTES (all GET, all query-param, so a phone bookmark works)\n// ?k=… the dashboard\n// ?k=…&f=json the same numbers as JSON\n// ?k=…&stop=1 kill switch ON , engine halts before it looks at a single contact\n// ?k=…&go=1 kill switch OFF\n//\n// COLOUR\n// Stage colours are a validated 4-step single-hue ordinal ramp (#86b6ef → #3987e5 → #256abf →\n// #184f95); status colours are the reserved good/warning/critical steps and always ship with a word\n// beside them, never colour alone. Both ramps were run through the palette validator in light and\n// dark before this file was written: ordinal ramp ALL CHECKS PASS in both modes.\n\n// ---- auth ------------------------------------------------------------------------------------\n// v2 (2 Aug, after the adversarial pass): the key is NOT in this file. val.town vals are PUBLIC -\n// proved by fetching this very source with no token, so a literal key here was readable by anyone\n// who found the val, which meant anyone could read Kim's data, stop her system, or trigger a run.\n// Only the SHA-256 digest lives in source now. The digest is useless to a reader and sufficient for\n// a comparison, so publishing the code no longer publishes the secret.\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\n\nasync function sha256Hex(s: string): Promise {\n const b = await crypto.subtle.digest(\"SHA-256\", new TextEncoder().encode(s));\n return [...new Uint8Array(b)].map((x) => x.toString(16).padStart(2, \"0\")).join(\"\");\n}\n\nasync function authorised(k: string): Promise {\n const override = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\");\n const expected = override || KEY_SHA256;\n const got = await sha256Hex(k);\n // Constant-time over equal-length hex digests.\n if (got.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < got.length; i++) d |= got.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\n\n// v1.7.1, VIEW-ONLY access. The admin link is also the stop-button link, so anyone Kim forwards\n// it to could halt her follow-up. The view key is DERIVED from the admin digest (deterministic, no\n// second secret to store): it renders the same page minus the stop controls and the JSON/selftest\n// modes. Give Kim and staff the view link; the admin link stays with whoever may press stop.\nasync function viewKey(): Promise {\n // v1.7.2 (review fix), derived from the GHL token (a real secret in env/private blob), not\n // from the admin DIGEST that anyone can read in this public source. Rotating the CRM token\n // rotates the view links, which is the right coupling anyway.\n const tok = Deno.env.get(\"GHL_TOKEN\") || ((await get(\"puppy_config\", null))?.ghlToken ?? \"\");\n if (!tok) return \"tds_view_disabled_no_token_available_x\";\n return \"tds_view_\" + (await sha256Hex(tok + \":view\")).slice(0, 32);\n}\nasync function viewAuthorised(k: string): Promise {\n const expected = await viewKey();\n if (k.length !== expected.length) return false;\n let d = 0;\n for (let i = 0; i < k.length; i++) d |= k.charCodeAt(i) ^ expected.charCodeAt(i);\n return d === 0;\n}\nconst KILL_BLOB = \"nurture_kill\";\nconst BUSINESS_TZ = \"America/New_York\";\n\nasync function blobMod() {\n return (await import(\"https://esm.town/v/std/blob\")).blob;\n}\nasync function get(key: string, fallback: any = null) {\n try {\n const blob = await blobMod();\n const v = await blob.getJSON(key);\n return v ?? fallback;\n } catch {\n return fallback;\n }\n}\n\n\n// Plain-English names for the engine's internal statuses. Kim never sees a snake_case token.\nconst STATUS_LABEL: Record = {\n main: \"In the main sequence\",\n awaiting_appt_outcome: \"Booked, waiting on the Pup Talk\",\n branch_a: \"Missed the Pup Talk, being rebooked\",\n branch_b: \"Had the Pup Talk, hasn't bought yet\",\n slow_track: \"On the slow track, an occasional helpful message\",\n paused_reply: \"Paused, they replied, a human has it\",\n done_booked: \"Booked a Pup Talk\",\n done_customer: \"Became a customer\",\n done_hard_exit: \"Stopped, opted out or disqualified\",\n done_soft_21d: \"Finished the sequence\",\n done_branch_complete: \"Finished the follow-up\",\n};\nconst ACTIVE = [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"];\nconst WON = [\"done_booked\", \"done_customer\"];\n\nfunction esc(s: unknown) {\n return String(s ?? \"\").replace(/[&<>\"']/g, (c) =>\n ({ \"&\": \"&\", \"<\": \"<\", \">\": \">\", '\"': \""\", \"'\": \"'\" }[c] as string)\n );\n}\n\nfunction todayInBusinessTz(): string {\n // en-CA gives YYYY-MM-DD, which is what the journal timestamps slice to.\n return new Intl.DateTimeFormat(\"en-CA\", { timeZone: BUSINESS_TZ }).format(new Date());\n}\n\nasync function collect() {\n const [state, summary, run, journal, lastError, kill] = await Promise.all([\n get(\"puppy_state\", {}),\n get(\"puppy_summary\", null),\n get(\"puppy_run_state\", null),\n get(\"puppy_journal\", []),\n get(\"puppy_last_error\", null),\n get(KILL_BLOB, null),\n ]);\n const wd = await get(\"wd_public\", null); // v1.5, independent watchdog headline\n\n const rows: any[] = Object.entries(state || {}).map(([id, s]: any) => ({ id, ...(s || {}) }));\n const byStatus: Record = {};\n for (const r of rows) byStatus[r.status || \"unknown\"] = (byStatus[r.status || \"unknown\"] || 0) + 1;\n\n const j: any[] = Array.isArray(journal) ? journal : [];\n const today = todayInBusinessTz();\n const todays = j.filter((r) => String(r.ts || \"\").slice(0, 10) === today);\n\n const sentToday = todays.filter((r) => r.event === \"sent\" && !r.test).length;\n const testSentToday = todays.filter((r) => r.event === \"sent\" && r.test).length;\n // v2 fix (adversarial pass): this matched \"failed\"/\"error\" exactly, but the engine journals\n // \"send_failed\", so the error tile could never leave zero and \"RUNNING, with errors today\" was\n // an unreachable state. A dashboard whose alarm cannot fire is worse than no dashboard, because it\n // is actively reassuring. Match any failure-shaped event instead.\n const failedToday = todays.filter((r) => /fail|error/i.test(String(r.event ?? \"\"))).length;\n\n const active = ACTIVE.reduce((n, k) => n + (byStatus[k] || 0), 0);\n const won = WON.reduce((n, k) => n + (byStatus[k] || 0), 0);\n const paused = byStatus[\"paused_reply\"] || 0;\n\n // Staleness is the alarm that matters most: a scheduler that stops firing is exactly the silent\n // failure this client cancels contracts over. 60 min = four missed 15-minute ticks.\n const lastRunTs = run?.ts || null;\n const ageMin = lastRunTs ? Math.floor((Date.now() - new Date(lastRunTs).getTime()) / 60000) : null;\n const stale = ageMin === null || ageMin > 60;\n\n return {\n generatedAt: new Date().toISOString(),\n run: run ?? null,\n contacts: rows.map((r) => ({\n id: r.id,\n status: r.status,\n label: STATUS_LABEL[r.status] || r.status,\n enteredAt: r.enteredAt ?? null,\n lastMainStepSent: r.lastMainStepSent ?? null,\n lastSentAt: r.lastSentAt ?? null,\n })),\n killed: !!kill?.stopped,\n killedAt: kill?.at ?? null,\n testMode: run?.testMode ?? null,\n engineVersion: run?.v ?? null,\n lastRunTs,\n lastRunAgeMin: ageMin,\n stale,\n counts: { total: rows.length, active, won, paused, sentToday, testSentToday, failedToday },\n byStatus,\n lastError: lastError ?? null,\n recent: j.slice(-40).reverse(),\n summary: summary ?? null,\n watchdog: wd ?? null,\n };\n}\n\n// ---- rendering ------------------------------------------------------------------------------------\n\nconst RAMP = [\"#86b6ef\", \"#3987e5\", \"#256abf\", \"#184f95\", \"#0f3a6e\"]; // validated ordinal, light+dark\nconst GOOD = \"#0ca30c\", WARN = \"#fab219\", CRIT = \"#d03b3b\";\n\nfunction tile(label: string, value: string | number, note: string, accent?: string) {\n return `
\n
${esc(value)}
\n
${esc(label)}
\n
${esc(note)}
\n
`;\n}\n\nfunction stageBar(byStatus: Record, total: number) {\n const order = [\"main\", \"awaiting_appt_outcome\", \"branch_a\", \"branch_b\", \"slow_track\"];\n const segs = order\n .map((k, i) => ({ k, n: byStatus[k] || 0, c: RAMP[i] }))\n .filter((s) => s.n > 0);\n const sum = segs.reduce((a, s) => a + s.n, 0);\n if (!sum) {\n return `
Nobody is in a sequence right now. That is expected until the first contact is tagged.
`;\n }\n const bar = segs\n .map((s) => ``)\n .join(\"\");\n const legend = segs\n .map((s) => `
${esc(STATUS_LABEL[s.k])}${s.n}
`)\n .join(\"\");\n return `
${bar}
${legend}
\n \n \n ${segs.map((s) => ``).join(\"\")}\n
The same numbers as a table
Stage People
${esc(STATUS_LABEL[s.k])} ${s.n}
Total in a sequence ${sum}
`;\n}\n\nfunction page(d: any, k: string, opts: { readonly?: boolean } = {}) {\n const c = d.counts;\n const health = d.killed\n ? { c: CRIT, icon: \"■\", t: \"STOPPED\", m: `You stopped the system${d.killedAt ? \" on \" + esc(String(d.killedAt).slice(0, 16).replace(\"T\", \" at \")) : \"\"}. Nothing is being sent.` }\n : d.stale\n ? { c: CRIT, icon: \"⚠\", t: \"NOT RUNNING\", m: d.lastRunTs ? `The last check was ${d.lastRunAgeMin} minutes ago. It should run every 15. Tell Amir.` : \"This has never recorded a run. Tell Amir.\" }\n : c.failedToday > 0\n ? { c: WARN, icon: \"⚠\", t: \"RUNNING, with errors today\", m: `${c.failedToday} message(s) failed today. Details are at the bottom of this page.` }\n : { c: GOOD, icon: \"✓\", t: \"RUNNING NORMALLY\", m: `Last check: ${d.lastRunAgeMin === 1 ? \"1 minute\" : d.lastRunAgeMin + \" minutes\"} ago. It checks roughly every 15 minutes around the clock, and messages only ever go out between 9am and 7pm Georgia time.` };\n\n const mode = d.testMode === true\n ? `
PRACTICE MODE: the system is doing everything except actually sending to your customers. Practice messages go to a dead-end test contact that cannot receive anything, so if you test it yourself you'll get silence, that's the point of practice mode. Keep handling new calls and messages the way you do today; it takes over only when you say the word and this banner turns LIVE.
`\n : d.testMode === false\n ? `
LIVE: real messages are going to real people.
`\n : `
MODE UNKNOWN: no run has reported yet.
`;\n\n // v1.7, Kim's own question (\"how does she know what needs doing today?\") answered on the page\n // itself, permanently. One plain sentence, computed from the same numbers as the tiles.\n const todayMsg = d.killed\n ? \"The system is stopped. Nothing will happen until someone presses Start below.\"\n : c.failedToday > 0\n ? `Look at the problems listed at the bottom of this page, ${c.failedToday} message(s) failed today.`\n : c.paused > 0\n ? `${c.paused === 1 ? \"One person\" : c.paused + \" people\"} replied and ${c.paused === 1 ? \"is\" : \"are\"} waiting on a human. Open Conversations and answer ${c.paused === 1 ? \"them\" : \"each one\"}, that is today's work.`\n : \"Nothing. If the banner above is green and Paused says 0, you can close this page.\";\n const today = `
What needs doing today
${todayMsg}
`;\n\n // Journal rows carry engine-internal names (sent main#3); translate to the words the PDFs use.\n const pretty = (s: string) =>\n s.replace(/\\bmain#(\\d+)/g, \"Touch $1 of the first 21 days\")\n .replace(/\\bslow#(\\d+)/g, \"Slow track message $1\")\n .replace(/\\bbranch_a#(\\d+)/g, \"rebooking note $1\")\n .replace(/\\bbranch_b#(\\d+)/g, \"after-the-call note $1\");\n const EVENT_LABEL: Record = {\n sent: \"message sent\", enrolled: \"joined the sequence\", pause_reply: \"paused, they replied\",\n soft_exit_21d: \"finished the 21 days, moved to slow track\", advance_status: \"moved forward\",\n send_failed: \"message FAILED\", skip_step_channel_optout: \"step skipped, opted out of that channel\",\n branch_complete: \"follow-up finished\", pruned: \"archived\", pause_timeout: \"waited too long, needs a person\",\n enroll_refused: \"not enrolled\", sequence_drift: \"copy changed underneath, check\", contact_failed: \"check FAILED\",\n };\n const rows = (d.recent || [])\n .map((r: any) => `${esc(String(r.ts || \"\").slice(0, 16).replace(\"T\", \" \"))}${esc(EVENT_LABEL[r.event] || r.event)}${r.test ? ' practice' : \"\"}${esc(pretty(String(r.detail || \"\")))}`)\n .join(\"\") || `Nothing recorded yet.`;\n\n return `\n\nThe Dogs Spot, Nurture Control Panel\n
\n
The Dogs Spot, Nurture Control Panel
\n
Everything the follow-up system is doing, on one page. The numbers are read fresh every time this page opens, refresh for the latest.
\n\n
\n
${health.icon}
\n
${health.t}
${health.m}
\n
${mode}
\n\n${today}\n\n${d.watchdog ? `
${esc(d.watchdog.headline)} ●
` : \"\"}\n\n
Right now
\n
\n${tile(\"People being followed up\", c.active, d.testMode === true ? \"right now that is the test dummy, not a real customer\" : \"in a sequence right now\")}\n${tile(\"Booked or became a customer\", c.won, \"the whole point of the system\", c.won > 0 ? GOOD : undefined)}\n${tile(\"Paused: someone replied\", c.paused, \"answer them in the Conversations inbox; the system stays out of it\", c.paused > 0 ? WARN : undefined)}\n${tile(\"Messages sent today\", c.sentToday, c.testSentToday ? `plus ${c.testSentToday} practice` : \"to real people\")}\n${tile(\"Problems today\", c.failedToday, c.failedToday ? \"see the bottom of this page\" : \"none\", c.failedToday ? CRIT : GOOD)}\n
\n\n
Where those people are
${stageBar(d.byStatus || {}, c.total)}${!(d.byStatus || {})[\"slow_track\"] ? `
The slow track (the occasional messages that follow the first 21 days) will appear here once the first person finishes their three weeks. Their first slow-track message goes out a week after that, on day 28.
` : \"\"}
\n\n${opts.readonly ? `
This page is view-only. The stop switch is on the owner's link.
` : `
Stop everything
\n
This halts the follow-up system before it looks at a single person. It takes effect 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. (When it is stopped, a green Start button appears right here.) To take one single person off every track instead: open their contact in GoHighLevel and switch on Do Not Disturb, the system honors that within 15 minutes, permanently.
\n${d.killed\n ? ``\n : ``}\n
`}\n\n
${(d.recent || []).length < 40 ? \"Everything it has done so far\" : \"The last 40 things it did\"}
\n${rows}
When What Detail
\n\n${d.lastError && d.lastError.at && Date.now() - new Date(d.lastError.at).getTime() < 24 * 3600 * 1000 ? `
Something went wrong in the last 24 hours
Technical details for whoever fixes it, if this box is showing, tell Amir and include what is below.
${esc(JSON.stringify(d.lastError).slice(0, 1200))}
` : \"\"}\n\n
System version ${esc(d.engineVersion || \"?\")} · numbers read fresh when this page opened
\n
`;\n}\n\n// ---- live self-test ------------------------------------------------------------------------------\n// Resolves the CRM credential exactly the way the engine does (env var first, then the puppy_config\n// blob) and pings the four endpoints the engine depends on. Reports status codes only, the token is\n// never returned, logged, or echoed. This exists because a stale credential is the failure mode that\n// looks identical to \"quiet\": the scheduler keeps ticking, every read fails, and nothing tells anyone.\nconst GHL = \"https://services.leadconnectorhq.com\";\nconst LOC = \"BQHJ19uohldYe3eqA0bl\";\n\nasync function resolveEngineToken(): Promise<{ token?: string; from: string }> {\n const env = Deno.env.get(\"GHL_TOKEN\");\n if (env) return { token: env, from: \"env GHL_TOKEN\" };\n const cfg = await get(\"puppy_config\", null);\n if (cfg?.ghlToken) return { token: cfg.ghlToken, from: \"puppy_config blob\" };\n return { from: \"NOT FOUND\" };\n}\n\nasync function selfTest() {\n const { token, from } = await resolveEngineToken();\n const checks: any[] = [];\n const probe = async (name: string, url: string, ver: string, why: string) => {\n if (!token) return checks.push({ name, status: null, ok: false, why, note: \"no credential resolved\" });\n try {\n const r = await fetch(url, { headers: { Authorization: `Bearer ${token}`, Version: ver, Accept: \"application/json\" } });\n checks.push({ name, status: r.status, ok: r.status === 200, why });\n } catch (e) {\n checks.push({ name, status: null, ok: false, why, note: String(e).slice(0, 120) });\n }\n };\n await probe(\"read calendar bookings\", `${GHL}/calendars/events?locationId=${LOC}&calendarId=qHuYJ0NEqzibnoqf5Cw3&startTime=${Date.now() - 864e5}&endTime=${Date.now()}`, \"2021-04-15\", \"how it notices someone booked a Pup Talk\");\n await probe(\"read replies\", `${GHL}/conversations/search?locationId=${LOC}&limit=1`, \"2021-04-15\", \"how it pauses when someone writes back\");\n await probe(\"read contacts\", `${GHL}/contacts/?locationId=${LOC}&limit=1`, \"2021-07-28\", \"how it reads names and dog names\");\n await probe(\"read deals\", `${GHL}/opportunities/pipelines?locationId=${LOC}`, \"2021-07-28\", \"how it notices someone became a customer\");\n return { credentialFrom: from, allOk: checks.every((c) => c.ok), checks };\n}\n\nexport default async function (req: Request): Promise {\n const url = new URL(req.url);\n const k = url.searchParams.get(\"k\") || \"\";\n const isAdmin = await authorised(k);\n const isViewer = !isAdmin && (await viewAuthorised(k));\n if (!isAdmin && !isViewer) {\n return new Response(\"Not found\", { status: 401, headers: { \"content-type\": \"text/plain\" } });\n }\n if (isViewer) {\n // view key renders the dashboard only, no stop/go, no JSON, no selftest.\n const d = await collect();\n return new Response(page(d, k, { readonly: true }), {\n headers: { \"content-type\": \"text/html; charset=utf-8\", \"cache-control\": \"no-store\" },\n });\n }\n\n if (url.searchParams.get(\"selftest\") === \"1\") {\n return new Response(JSON.stringify(await selfTest(), null, 2), {\n headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" },\n });\n }\n\n if (url.searchParams.get(\"stop\") === \"1\") {\n const blob = await blobMod();\n await blob.setJSON(KILL_BLOB, { stopped: true, at: new Date().toISOString(), by: \"control-panel\" });\n return Response.redirect(`${url.origin}${url.pathname}?k=${encodeURIComponent(k)}`, 303);\n }\n if (url.searchParams.get(\"go\") === \"1\") {\n const blob = await blobMod();\n await blob.setJSON(KILL_BLOB, { stopped: false, at: new Date().toISOString(), by: \"control-panel\" });\n return Response.redirect(`${url.origin}${url.pathname}?k=${encodeURIComponent(k)}`, 303);\n }\n\n const d = await collect();\n if (url.searchParams.get(\"f\") === \"json\") {\n return new Response(JSON.stringify(d, null, 2), {\n headers: { \"content-type\": \"application/json\", \"cache-control\": \"no-store\" },\n });\n }\n return new Response(page(d, k), {\n headers: { \"content-type\": \"text/html; charset=utf-8\", \"cache-control\": \"no-store\" },\n });\n}\n",[315],"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",[322],"aef5a358-8c75-407f-91e2-b465d635d676","SOURCE-BUNDLE.part9.txt","5cc7c38a-91cc-11f1-86f1-1607ee4eb77e",288,["D",1786044234101],"THE DOGS SPOT — SOURCE BUNDLE (part 9 of 9)\n\nEverything in this project that does not already live on val.town. The engine is NOT here:\nseventeen files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff, verified file by file by\nscripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\n\nRESTORE (needs only node, from an empty folder). Save each part, then run this ON EACH ONE:\n\n node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(process.argv[1],\"utf8\");\n for(const s of b.split(\"\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\n\");\n const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});\n fs.writeFileSync(f,c.replace(/\\n$/,\"\"))}' PART.txt\n\nEach part is complete in itself: whole files only, no reassembly, any order.\n\nThen: node scripts/deploy.mjs --check (pulls nothing, proves the val matches)\n node scripts/build.mjs (needs engine/ back from the val first)\n node tests/run-all.mjs\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (4 of 34 files)\n handover/REPLY-AUG5.txt 10976 bytes 683bd5977a12\n handover/REGISTER-AUG5.md 2927 bytes c8ce4d6aef0d\n handover/AMIR_TODO.md 1488 bytes b7849ef7fbe3\n handover/DEPOSIT-SPEC.md 17603 bytes b1c00353046a\n\n================================================================================================\n=====FILE handover/REPLY-AUG5.txt =====\nKim, the person your funnel was chasing is stopped, answers to everything you asked today below, and one thing I found tonight about the red flag tag that you'll want to see.\n\nThomas first, since that was the HELP. He is out of that workflow as of 6:30 this evening and nothing else is active on his record, checked again after a full reload. Nothing new will go to him.\n\nWhat happened, in order. Your team booked his Free Training Day at 10:24 this morning, right after his Pup Talk, directly on the calendar. A few minutes later the little free training day signup page got a visit and its one question form got submitted, most likely him clicking around after the call. That page's funnel only counts a booking made through the page itself. It cannot see the calendar, so it decided he was interested and unbooked, and chased: two texts at 12:31, a voicemail at 12:41, and another text at 2:41, all grab your spot before it fills. Your screenshots caught three of the four, the 12:41 one was a voicemail drop rather than a text. Candice caught it and rang him at 4:54, which is in his thread too.\n\nTwo things worth knowing about it. First, it was not the new follow-up system. That has been in practice mode all day and has sent nothing to anyone, and I checked it live tonight before writing this. It was one of the workflows that came with your account, called \"Free Training Day abandoned booking\". Second, this is the same blind spot as the deposit: bookings made off to the side are invisible to the automations inside the CRM, and this is what that looks like when it bites. The lasting fix is one exit rule on that funnel, leave anyone who already has a Free Training Day on the calendar, and the same rule on its sibling, the small yes text one that sent the first two messages and had already finished with him by then. I can make that change with you on a call or write it up for whoever you prefer, I didn't want to edit a live workflow of yours tonight without you knowing. I also checked whether it hit anyone else: that calendar holds three bookings in all, and the other two people's threads are clean, so Thomas was the only one it reached.\n\nAnd since it's the same Thomas as this morning, George's owner: after the day he's had I would not put him on any track for now. He's booked in and your people are talking to him, which is better than any sequence.\n\nOn going live for the puppy: you were right about the mechanism, one wording detail aside, and the straight answer on tonight is not yet. The tag is \"nurture - puppy\", not just \"puppy\", and Candice used exactly the right one on Kristina this morning without being told, so it's already in her dropdown. The reason for the not yet: switching on properly is one coordinated move, ours on, the old puppy workflow off, the tagging step on, or somebody ends up with two sets of messages, which is exactly the class of accident Thomas got a taste of today. While practice mode is on, the tag queues people up but nothing sends, to anyone, full stop. And once live, the system stays quiet for anyone with a call still on the calendar until that call has an outcome, so nobody gets messaged over a booking.\n\nWalle's owner, told straight, because her day moved around. I marked her at lunchtime, before what was then her afternoon call. Since then, three things happened on her record: her Pup Talk moved to Thursday at 3:40, the puppy mark came off during the afternoon, and on this evening's call your team booked her Free Training Day for Friday morning. I don't know whose hand took the mark off and I won't guess. But where she has landed matches your own rule, anyone who books comes off the track, so I've left it exactly as it is. If you want her on the puppy messages after her visit, it's one tag to put back. So right now exactly one inquiry is marked and waiting, Kristina, and she's held anyway until her Meet and Greet on Monday resolves.\n\nThe attachment. You didn't miss it, it failed to attach, and that's twice now, which is embarrassing. Both documents are on this message and I've watched them upload this time. The short one is the first three weeks. The long one answers your question about the longer version: it's not a different sequence to choose between, it's the same one continued. The first three weeks run their course and then the taper you designed takes over automatically, once a week for a month, every two weeks for six months, then monthly indefinitely. So \"do the longer one then ease into the slow track\" is exactly what's built, nothing to decide.\n\nKristina's two records are merged, done early this afternoon. The useful detail: the two records had two different phone numbers, one digit apart. Her actual call this morning came from the number ending 4535, which proves that's the real one, so it survived and the typo is gone. The accidental do-not-disturb is off, that got switched on when the second record was created, which is why you saw it and couldn't explain it. Her Meet and Greet on Monday is untouched, her email is on the record, and both conversation histories are in one place. One judgment call I made and want you to know about: the duplicate had also been tagged into the no sale and tips nurtures. She has a booked appointment, so she's not a no sale, and carrying those tags over would have had your tips messages texting someone who's about to come in. I left them off. If you want her in tips anyway it's one click to add back.\n\nThe tag report is attached, rebuilt tonight so it matches your account as of this evening, and it turned up the thing you should actually look at. The tag \"red flag\" is not just a label. A workflow that came with your system switches on do-not-disturb for anyone who gets it. It was put on five people this week, so all five are on do-not-disturb right now and your system will not message them at all. They are listed by name in the file. And they answer your actual question about where these came from: seven people carry them, six from the missed-callers list Candice was working through yesterday and one who came in through Messenger, and every one of the seven records was touched during her calling hours yesterday afternoon. So these read like her outcome notes from working the phones, no for a no, red flag for the ones that felt off. A sensible instinct. She just may not know that red flag also silences people: if any of them were flagged by mistake, taking the tag off is not enough on its own, the do-not-disturb switch needs turning off too. The other odd ones are smaller: \"no\" is on four people and does nothing by itself, though it sits one word away from \"no sale\", which does start a nurture. And a tag called \"follow-up\" was on exactly one person when I built this afternoon's version of the file and is on nobody now. I didn't take it off, so the tidying has already started on your side. One honest limit, stated in the file too: your CRM doesn't record when a tag was applied, only that a record changed, so the file shows records touched since Monday, 167 of them, and what they carry now. On the bigger cleanup, every tag actually in use is in the file, 40 of them tonight. The dropdown also holds tags that are defined but sitting on nobody, and reading that list needs one extra permission on the connection, a two minute change in tonight's task list on my side, and the full unused-tags list follows right behind it. The cleanup itself is short and safe because nothing in use gets touched.\n\nYou're reading the no sale routing correctly. Today everyone lands in no sale-tips unless disqualified. Once we're live, the puppy tag pulls puppies onto the new track and your existing flows keep everyone else. And thank you for the history on the tips ad campaign, that the copy was Milton's and that it answers on Facebook comments as well as Messenger. That changes it from \"looks accidental\" to \"leave it alone\", and I have.\n\nThe deposit, good news: the Stripe advice didn't come from me, and whoever it came from was answering a different question. Nothing in the plan bills anyone through the CRM. Square keeps taking the money exactly as it does now, and what I'll build reads the payments as they land and does the bookkeeping automatically: deposit paid gets marked on the person, and you get one list of holiday bookings that still owe. No Stripe, nothing changes about how customers pay. On dates, one small correction so the automation never misfires: Thanksgiving is the fourth Thursday of November, the 26th this year, and it's computed fresh each year, so that curveball is handled. I'll fold it into the monthly.\n\nThe transcripts, and a correction of mine. Earlier today I told you transcription had never been switched on. That was wrong. Kristina's call from this morning has a full written transcript, I watched it render, and this afternoon's call with Thomas shows one too. So transcription works, at least sometimes, and the real question is which calls are missing theirs. The fastest way to crack it: point me at one call where the transcript should be there and isn't, or tell me roughly when they disappeared for you, and comparing that call against a transcribed one should pin the pattern down quickly. And if nothing comes to mind, just say so, and I'll walk the recorded calls myself tomorrow and bring you the list of which have transcripts and which don't.\n\nCandice's app stalling on messages I'm still on, and I'd rather say that than guess. One thing I can already measure: your account holds five and a half thousand conversations, and loading them one at a time takes long enough that anything doing so would appear to freeze. That's a suspicion about where to look, not an answer yet.\n\nAnd the page link I owed you: https://amir5--fb119304902811f182781607ee4eb77e.web.val.run?k=tds_view_795bafb78a5428f8e6ef481518c274b6\n\nBookmark that. It reads your systems the moment you open it, every count on it comes from your records rather than from anyone's memory, and each question and log line on it names the check that backs it. Tonight is already written on it: Thomas, the red flag finding, and Walle's owner coming off the track. The count of marked puppy inquiries reads your records live each time you open it.\n\nNothing has sent to anybody from the new system, today included. Three things stand between here and fully live, and they are numbered on the page: your word on the wording, the switch-over done as one move so the old puppy workflow cannot double-message anyone, the same class of accident as today's funnel, and four small settings wherever thedogsspotga.com is managed so the emails land in inboxes instead of spam. The first two happen the evening you say the word, and the texts can go live on those two alone. One more honest pointer: on that page, the access key question, the Bootcamp deposit question, and the doubled review-request automations are the three that most deserve your eyes first, and the rest can wait for you.\n\nAmir\n\n\n=====FILE handover/REGISTER-AUG5.md =====\n# REGISTER ADDENDUM - fleet verification, late 5 Aug (ET)\n26-agent fleet (20 sonnet verify, 4 opus adversarial, 1 opus judge, ~62 min, 642 tool calls) against live data.\n\nCONFIRMED CLEAN: Thomas timeline (every timestamp), Kristina record (all five facts), census=1 Kristina,\nred flag x5 all DND, no x4 with two non-DND, follow-up 0, 40 distinct tags (full 5,562-contact walk),\nold puppy workflow still published (cutover premise), Tresa state (tags [phone], Pup Talk Aug 6 3:40,\nFTD booked), conversations 5,534 (message says five and a half thousand), 3 go-live blockers match page.\n\nFINDINGS AND RESOLUTIONS:\n1. Three source=workflow SMS hit Thomas AFTER the 6:30 PM removal (8:00, 8:05, 9:05 PM ET). Verified by\n hand: they are the BOOKED-path confirmations for his real Aug 15 session (confirmed + spots-held +\n details), triggered by his opportunity moving to booked at 8:00 PM. Correct message type for a booked\n customer; the chase type stayed stopped. Sent message's \"Nothing new will go to him\" is literally\n false as a result; bridge note corrects it.\n2. Adversarial sweep found 76 chase texts + 24 voicemails to 27 other contacts since 14 Apr. Checked the\n booked ones by hand: Luis Colon booked Jul 13, zero chase. Destinee Patterson chased 30 May while\n UNBOOKED (funnel's intended target), booked 4 Aug - the funnel converting, not the defect. Conclusion\n of the sent message stands as scoped: Thomas is the only person chased AFTER booking. Stronger\n evidence method than the calendar-sample cited in the message; noted here.\n3. \"That calendar holds three bookings in all\" was stale by one at send: Tresa booked 6:35 PM, message\n sent 7:54 PM. Materially harmless (the fourth is Tresa, whose story the message tells). Logged.\n4. \"Practice mode... sent nothing to anyone\": engine made one SMS API call on 5 Aug 12:40 PM ET to the\n ZZTEST dummy (unroutable, failed). True for real people; wording tightened in future copy. ENGINE\n HARDENING QUEUED: add TEST_MODE guard at the sendSms call site (safety currently via contact scoping).\n5. \"Computed fresh each year\" (Thanksgiving) describes the deposit plan not yet built; present tense ran\n ahead of reality again. Building the reader includes the fourth-Thursday computation.\n6. Red flag DND nuance: 4 of 5 silenced by the workflow from clean state; the fifth (no-name record) had\n SMS-blocked themselves 20 Jul, workflow extended it to all channels 4 Aug. Message's claim literally true.\n7. Chase funnel \"Free Training Day abandoned booking\" remains PUBLISHED. Fix proposed to Kim in the sent\n message; her call, not taken unilaterally.\n8. Disk reverted to the Aug 4 snapshot a third time mid-fleet; twelve slices reported artifacts missing.\n Kim's copies live on Upwork (hash-verified before send) and everything regenerates from the val bundle\n (v203/204). Local file absence is an environment artifact, not a delivery failure.\n\n\n=====FILE handover/AMIR_TODO.md =====\n# AMIR - morning of 6 Aug. 4 things.\n\n## 0. State of play\nThe full reply went to Kim last night (7:54 PM ET, two bubbles, stray \"Boo\" in the middle, all\nthree files attached, every claim fleet-verified afterward). She has not answered yet. The short\nbridge note is drafted and HELD - I do not send it unless you say \"send it\". Three automated\nbooking-confirmation texts went to Thomas at 8-9 PM for his real Aug 15 session (right kind of\nmessage, from the booked-day workflow, not the chase). The chase workflow stays stopped for him.\n\n## 1. One token action in GHL (5 min, fixes the exposed key AND the missing scope)\nPrivate Integrations tab (open in Chrome) > edit the reporting integration > tick the tags-view\nscope > Save > Regenerate token > paste new token into BOTH vals' env tabs (engine + watchdog) >\nopen the dashboard link and confirm the counts load.\n\n## 2. Bridge note - your call\nSend it from your phone or tell me \"send it\". Text is in the chat. It owns the Boo, corrects\n\"nothing new will go to him\" (his booking confirmations went out, the right kind), and points\nher at the red flag finding.\n\n## 3. When Kim says go on the wording\nThe switch-over is one coordinated move done together: TEST_MODE=false, old puppy workflow off,\ntagging on. Never solo.\n\n## 4. Engine hardening queued (do with me, 20 min, not urgent)\nAdd a TEST_MODE guard at the sendSms call site (today safety is contact-scoping to the dummy).\nThen the funnel exit-rule change for Kim if she says yes.\n\n\n=====FILE handover/DEPOSIT-SPEC.md =====\n# HOLIDAY DEPOSIT TRACKER - build spec, 6 Aug\n## The finding that changes everything\nSquare payments ARE in the CRM. They land as contact notes, e.g.\n \"[Square] +$355.00 payment tWYOxuFcG9ZqzF7GTnUPfElf2ZEZY (balance $0.00)\"\nVerified live on contact mmc80rVoE52OKMPQUr7G, 6 Aug 00:47. Every previous conclusion that\n\"the CRM never sees Square money\" came from querying /payments/*, products and custom fields.\nNobody queried /contacts/{id}/notes. So the tracker is buildable, and what Kim was told\n(\"we read those payments and do the bookkeeping\") is accurate.\n\n## Two traps found in the same data\n1. The same payment is written FIVE times, with contradictory balance figures in the duplicates\n ($355.00 then $0.00 x4). Dedupe on the payment id. Never trust the balance figure.\n2. Recurring bookings (a standing weekly slot) fall inside any holiday window and would make\n Kim chase regulars who never owed. Filter isRecurring.\n\n## What it must say to Kim, honestly\nNot \"who still owes\". It cannot be that: a deposit taken in cash or over the phone leaves no\ntrace. It is \"holiday stays where we cannot find a $50 payment\" - a shortlist to check, which\nturns going through every holiday booking by hand into checking these few.\n\n## Build\n- engine/holiday-deposits.ts, called from the interval, rendered by dashboard.ts. GET only.\n Test asserts the source contains no POST/PUT/PATCH.\n- Read drop-off calendars only (pick-up would double count each stay).\n- Per distinct contact: GET /contacts/{id}/notes, parse /^\\[Square\\]\\s*\\+\\$([\\d,]+\\.\\d{2})\\s+payment\\s+(\\S+)/\n- Group into stays by contact + drop-off date. Musselwhite has three dogs on one day: one stay.\n- Status: seen / partial / none_seen / could_not_check. could_not_check NEVER collapses to none_seen.\n- Write NOTHING to the CRM. No tag, no field, no stage. addTag is not TEST_MODE-guarded, and\n \"Add tag 'red flag' = DND\" proves a tag here can silence a contact on six channels.\n- Kill switch: if zero Square notes exist in the period, suppress the list and say the feed\n looks dead, rather than printing \"everyone owes\".\n- The word \"unpaid\" must not appear. Suite asserts it.\n\n## Ask Kim before it goes live\nExact holiday window dates. $50 per stay or per dog. Does she ever take the deposit in cash.\n\n---\n\n# BUILT AND LIVE — 6 August 2026\n\n## What shipped\n| file | on the val | what it is |\n|---|---|---|\n| engine/holiday-deposits.ts | script | all the judgement. No fetch, no write verb, enforced by H22. |\n| engine/deposits.ts | http | the only file that touches the CRM. One GET-only door. |\n| engine/deposits-cron.ts | interval | the scheduled refresh. Separate from main.ts on purpose. |\n| engine/dashboard.ts | http | the card Kim reads, from the stored blob, no CRM call at render. |\n\nBlob key `holiday_deposits`. Endpoint `?k=&run=1` collects and stores; `?k=` reads\nback what is stored.\n\n## Watched working, live\n- 2026-08-06T15:41:28Z — first live collection. 2 stays, 2 calendars read, 0 read failures.\n- 2026-08-06T15:42:56Z — second collection after the kill-switch fix. Correct sentence.\n- 2026-08-06 ~15:44Z — card rendered on the live dashboard, both customers named, no accusation.\n\n## Two things the live data changed\n1. **There is a SECOND Square note format.** `[Square] Till payment $35.00 on . Matched from\n Square payment via customer .` It does not match the `+$` pattern this spec started\n with. A customer whose only record was this shape would have read as \"nothing on file\". Both\n formats are parsed now; where the same amount appears as a direct payment AND as a \"Matched\n from\" record, it is counted ONCE, because over-counting takes a real customer off the shortlist\n and nobody ever looks at them again. H23–H26.\n2. **The kill switch fired on a sample of two.** The first live run was about to tell Kim her\n payment feed had stopped because neither of two customers had a Square note. It now needs at\n least 5 customers checked (`MIN_SAMPLE_FOR_DEAD_FEED`). Found by watching it run, not by\n reading the code. H19b.\n\nAlso: her CRM returns BOTH `appointmentStatus` and the misspelled `appoinmentStatus` — on 4 of 13\nevents. They agree today. Both are read, and either one saying cancelled excludes the booking. H28.\n\n## Tests\n30 assertions in holiday-deposits.test.mjs, 12 in deposits-collect.test.mjs, 9 in dashboard.test.mjs\n(D5.1–D5.9). 19 negative controls prove each of those guarantees can actually go red.\n\n## NOT YET OBSERVED — do not claim this works\n`deposits-cron.ts` is registered on the val as type `interval` and the val accepted a second\ninterval file. **It has not been seen firing on its own.** val.town's API exposes no schedule\nfield, so the only proof is the blob's `at` moving forward without anybody triggering it. Until\nthat has been observed, the list refreshes when the endpoint is hit and the page honestly reports\n\"last checked N hours ago\". Baseline to check against: 2026-08-06T15:42:56.924Z.\n\n## Still to ask Kim\nExact window edges (currently Monday-to-Sunday around Thanksgiving, and 20 Dec to 2 Jan).\n$50 per stay or per dog. Whether she ever takes the deposit in cash — that answer decides whether\nthe \"may have been paid another way\" caveat can ever be dropped.\n\n---\n\n# ROUND TWO — 6 August, afternoon\n\nTwo independent adversarial reads were run against the shipped feature. The first found 19\ndefects, the second found 16 more IN THE FIXES. Everything below is what changed as a result.\nBoth reviewers were given the live data and told to run the built code rather than read it.\n\n## The design change that mattered\n\n**It has stopped guessing which payment is the deposit.** Nothing in the CRM says what a card\npayment was for, and two attempts at inferring it were both wrong in the direction that costs Kim\nmoney:\n\n| version | rule | what it got wrong |\n|---|---|---|\n| v1 | sum every payment between booking and drop-off | a $355 training package cleared a $50 deposit; cleared means nobody ever looks again |\n| v2 | sum payments within 10 days of the booking | missed a real $50 paid 8 days later — the card said \"we cannot find a $50 payment\" one line after printing one — and still cleared anyone who settled a $240 invoice that week |\n| v3 | **a card payment for EXACTLY $50 clears a stay. Nothing else does.** | every other payment near the stay is listed with date and amount for Kim to judge |\n\nA wrong \"worth a look\" costs Kim a glance. A wrong \"settled\" costs her $50 and she never finds out.\n\n## Everything else round two changed\n\n- **Stay length comes from the PICK-UP calendars.** A drop-off booking is a ten minute handover\n slot; its endTime says nothing about the stay. Pairing rule: the LATEST eligible pick-up on or\n after the drop-off and BEFORE that customer's next drop-off. Both bounds were found by failure —\n earliest-wins deleted a family whose first dog went home early, and unbounded made a 3-night\n Thanksgiving stay render as \"Nov 25 to Dec 27\".\n- **The kill switch counts customers, not bookings.** Her account has one contact with 24\n drop-offs; counting rows let one cash-paying regular suppress the whole card.\n- **A pick-up calendar that fails is declared on the card.** It was being written into the blob\n and read by nothing — the quietest possible failure, because the stays that vanish are exactly\n the ones the pick-up calendars exist to find.\n- **The unknown count on the card counts ROWS**, matching the table, not customers.\n- Daycare exclusion narrowed: a title saying both daycare and boarding is a boarding booking.\n- `looksLikeTestRecord` no longer matches \"tester\" — Tester is a real surname and this label sits\n next to a person's name.\n- The dead-feed sentence no longer says \"any of the 0 we could check\".\n\n## Two tests that could not fail, and one control suite that could not run\n\n- **H5** (\"cancelled bookings are excluded\") used a fixture dated 2 November, outside every\n window, so it passed with the cancellation filter deleted. Fixture moved inside the window.\n- **H8**'s structural guard matched a pattern that went stale the day `localDay` grew a legitimate\n numeric branch. It now asserts the specific thing it means: the string path slices, never parses.\n- **negative-controls.mjs was truncated by an edit** — the whole runner was deleted. It then\n printed NOTHING and exited 0, which reads as \"all controls passed\". `run-all.mjs` now runs one\n control as a smoke test and goes RED if the control suite prints no result. Fault-injected and\n confirmed to fire.\n\n## State at 16:53 on 6 August\n\n- 15 suites, 262 assertions, 0 failed.\n- **89 negative controls, 89 passing** — every guarantee above can be made to go red on demand.\n- Live run at 16:53:19Z: 2 stays, both worth a look, 2/2 drop-off and 2/2 pick-up calendars read,\n 0 unreadable customers. Card verified on the live dashboard, no accusation in it.\n\n---\n\n# ROUND THREE — 6 August, 17:00. Verdict was NOT CLEAN.\n\nA third independent read was run with instructions to mutate the code and prove the tests catch\nit. Six mutations, five stayed green. Everything below is what that round changed.\n\n## The one that would have cost Kim money, silently\n\n**One $50 payment settled every holiday stay that customer had.** `statusFor` answers about a\nsingle stay and was handed the customer's whole payment list. A regular who books Thanksgiving\nAND Christmas in the same phone call and pays one deposit had BOTH rows go green. Kim was owed\n$100, $50 arrived, and neither row reached the shortlist. This is the ordinary case, not an edge:\nthe two search windows are both anchored on the same booking date and overlap almost completely.\n\nFixed by `statusesForCustomer()`: payments are ALLOCATED, earliest drop-off first, and a payment\nspent on one stay is invisible to the next. H48, plus a negative control.\n\n## The one that would have taken the whole test suite down\n\n`D5.11`'s fixture carried a hardcoded timestamp and the stale-list banner fires on real elapsed\ntime. **From 8 August the entire 269-assertion regression net would have read RED on the wall\nclock, with no code change.** The fixture is now relative to now. Verified green at +48 hours and\nat +400 days by injecting an offset clock.\n\n## The rest\n\n- **A pick-up on the same day as the next drop-off** (collect one dog, board another, same day)\n deleted the stay it was ending — the busiest stay of the season, silently. Bound is `<=` now.\n- **An orphan pick-up dragged an out-of-season boarding onto the shortlist**: a 6 November stay\n rendered \"Nov 6 to Feb 1\". `MAX_STAY_DAYS = 21` caps the reach. Her account has ~20 contacts\n with pick-ups and no matching drop-off, so orphans are the common case.\n- **H42 was pinning that bug** — it asserted the drag HAPPENED, with a follow-up assertion whose\n first disjunct was false and whose second was true whenever the drag occurred. Rewritten to\n forbid it.\n- **One booking with no `dateAdded` blacked out the whole card**: its structurally-empty payment\n list counted as \"we looked and saw nothing\", pushing the dead-feed sample over the floor.\n- **A run where nobody's payments could be read was stored over yesterday's real shortlist**, with\n a FRESH timestamp — content worse, page claiming to be up to date. Now refused.\n- Grammar: \"1 card payment is on file … none of them … among them\".\n- Four guarantees that no test could break (the search window's upper edge, the per-customer\n sample rule, the amber label on a partial row, and the headline counting partial rows) now have\n tests and controls.\n\n## State at 17:21 on 6 August\n\n- 15 suites, **269 assertions**, 0 failed. Green at +48h and +400d on an injected clock.\n- **98 negative controls, 98 passing.**\n- Live run 17:21:23Z: 2 stays, 2/2 drop-off and 2/2 pick-up calendars, 0 unreadable.\n\n## STILL NOT OBSERVED — do not claim this works\n\n`deposits-cron.ts` is registered on the val as a second `interval` file. It has **not been seen\nfiring on its own**. The blob moved once at 15:44:33Z, six seconds after that file was deployed,\nwhich looks like a deploy-triggered first run rather than a schedule. Between 17:21 and 17:29 it\ndid not move. val.town exposes no schedule field on the API, so the only proof is the stored `at`\nadvancing with nobody triggering it. Until that is seen, treat the list as refreshing when the\nendpoint is hit; the card reports its own age and warns past 36 hours.\n\n---\n\n# ROUNDS FOUR, FIVE AND SIX — 6 August, evening. All three: NOT CLEAN.\n\nThree more independent adversarial reads, each told to mutate the code and prove the tests catch\nit. Between them they ran ~110 mutations. The pattern that matters: **the same money bug came back\nthree times, one layer down each time.**\n\n## The money bug, and the three doors it came back through\n\nThe rule is: one $50 deposit settles ONE stay. A regular books Thanksgiving and Christmas in one\nphone call and pays one deposit; if both rows go green, Kim is owed $100, $50 arrived, and neither\nrow reaches the shortlist. She never finds out.\n\n| round | door it came back through | fix |\n|---|---|---|\n| 3 | `statusFor` was handed the customer's whole payment list per stay | `statusesForCustomer` allocates each payment to one stay, earliest first |\n| 4 | the allocator marked only the SURVIVING id of a direct/backfill twin as spent | collapse once, globally, before allocating |\n| 6 | the collapse was one-for-one, so with two backfills and one payment the survivor was folded AGAIN per stay and never spent | the collapse is now IDEMPOTENT: every backfill sharing an amount with a payment folds, so a second pass is a genuine no-op |\n\nRound 6 found it reachable from Kim's real note text at ~1% of generated contacts. H48, H52, H56,\nH57 and D27 now cover the four layers; each has a negative control.\n\n## Test-integrity defects, which matter more than any single bug\n\n- **`run-all.mjs` never rebuilt.** Behavioural assertions import `build/`, structural ones read\n `engine/`. Deleting the allocation from the source and running the suite WITHOUT rebuilding gave\n \"270 assertions passed, RESULT: GREEN\". The runner now builds first, and a failed build is a RED.\n- **`negative-controls.mjs` was truncated by an edit** — the whole runner deleted. It printed\n nothing and exited 0, which reads as \"all controls passed\". `run-all.mjs` now runs one control\n as a smoke test and goes RED if the control suite prints no result.\n- **The suite would have gone RED on the wall clock on 8 August** — a fixture timestamp against a\n 36-hour staleness banner. Fixtures are relative to now; verified green at +2d, +200d and +2y.\n- **D29 was four vacuous assertions** — regexes over main.ts for \"3600_000\", \"holiday_deposits\",\n \"runCollection()\" and \"catch\". Four different real breakages stayed green, including one that\n made the refresh run on every tick and one that made it never run. The rule is a pure function\n now (`needsRefresh`) and is tested as one.\n- **D12/D26/D28 read the raw file**, so a `[was: ...]` note quoting a deleted guard kept them\n green. They read comment-stripped source now, and what the guards DO is tested behaviourally\n through `decideStore`.\n- **H27 could not fail** (its fixture used the deposit amount, where both assertions hold by\n construction). **H5 could not fail** (fixture outside every window). **H42 asserted the bug its\n own comment said was fixed.** All three rewritten.\n- One control was RETIRED rather than retargeted: idempotency made the fault it injected a no-op,\n so it could no longer fail. A control that cannot fail is worse than no control.\n\n## Other real fixes from these rounds\n\n- Drop-off and pick-up calendars are fetched over the SAME range. They were not, so for every stay\n at the tail of the season the customer's own next booking was never fetched and the \"hard upper\n bound\" was structurally blind: a 30 Dec stay rendered \"Dec 30 to Jan 15\" and a January payment\n settled the holiday deposit.\n- A pick-up on the same day as the next drop-off (collect one dog, board another) deleted the stay\n it was ending.\n- An orphan pick-up dragged an out-of-season boarding onto the shortlist as \"Nov 6 to Feb 1\".\n `MAX_STAY_DAYS = 21`.\n- The refresh gate now keys off an ATTEMPT stamp, not the stored list, so a run that legitimately\n declines to store does not get retried every 15 minutes against a CRM that is already unwell.\n- The season rolls over on New York time, not UTC. It was emptying the card at 8pm on 2 January.\n- `deploy.mjs` reports main.ts in BOTH characters and bytes and gates on the stricter. At one point\n it read 79,815 characters and 80,137 bytes — \"185 to spare\" on one measure, over the line on the\n other.\n- One `$50` payment can no longer be quoted on two different settled rows.\n\n## State at 19:23 on 6 August\n\n- 15 suites, **283 assertions**, 0 failed. Green at +2d, +200d and +2y on an injected clock.\n- **118 negative controls, 118 passing.**\n- Live run 19:03:39Z: 2 stays, 2/2 drop-off and 2/2 pick-up calendars, 0 unreadable, stored.\n Engine healthy after the main.ts change (engineOk true, watchdog INFO).\n\n## The refresh, and what is still not proven\n\n`deposits-cron.ts` has still never been observed firing on its own (checked at 15:44, 17:29, 18:32\nand 19:23 — every movement of the blob was a manual run). So the refresh is now called from\n`main.ts`'s interval, which IS watched keeping time. **That has not been observed firing yet\neither** — the attempt stamp was set at 19:03:39Z and the gate is one hour, so the first\nengine-driven refresh is due after 20:03. Do not claim it works until the stored `at` has moved\nwith nobody triggering it.\n\n",[329],"21436939-beb1-4687-878c-36b5713bb369","SOURCE-BUNDLE.part8.txt","7c8dcd00-91bc-11f1-8e89-1607ee4eb77e",287,["D",1786044233581],"THE DOGS SPOT — SOURCE BUNDLE (part 8 of 9)\n\nEverything in this project that does not already live on val.town. The engine is NOT here:\nseventeen files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff, verified file by file by\nscripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\n\nRESTORE (needs only node, from an empty folder). Save each part, then run this ON EACH ONE:\n\n node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(process.argv[1],\"utf8\");\n for(const s of b.split(\"\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\n\");\n const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});\n fs.writeFileSync(f,c.replace(/\\n$/,\"\"))}' PART.txt\n\nEach part is complete in itself: whole files only, no reassembly, any order.\n\nThen: node scripts/deploy.mjs --check (pulls nothing, proves the val matches)\n node scripts/build.mjs (needs engine/ back from the val first)\n node tests/run-all.mjs\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (5 of 34 files)\n scripts/transcript_census_wide.py 9145 bytes 0f492678e78e\n watchdog/main.ts 36028 bytes 5e6ddce32fd8\n watchdog/run.ts 1285 bytes ce6de4a0e5cf\n handover/PLAN-TO-FINISH.md 13922 bytes 7c1f9736a4c4\n handover/SEND-TO-KIM.txt 6319 bytes 5bdb4888795f\n\n================================================================================================\n=====FILE scripts/transcript_census_wide.py =====\n#!/usr/bin/env python3\n\"\"\"\nWide transcript-coverage census.\nSTRICTLY READ-ONLY: GET requests only.\n\nWalks conversations sorted by recent activity (most recent first),\nfor each conversation collects every TYPE_CALL message, and for each\ncall checks the transcription endpoint and the recording endpoint.\n\nCheckpoints progress to disk continuously so partial results survive\na timeout.\n\"\"\"\nimport json, time, sys, os, re, signal\n\nimport requests\n\nREPO = \"/home/claude/dogsspot\"\nTOK = None\nwith open(os.path.join(REPO, \"tests\", \"aged_audit.py\")) as f:\n txt = f.read()\nm = re.search(r\"pit-[a-f0-9]{8}-[a-f0-9-]*\", txt)\nTOK = m.group(0)\n\nBASE = \"https://services.leadconnectorhq.com\"\nLOC = \"BQHJ19uohldYe3eqA0bl\"\nHDRS_CONV = {\n \"Authorization\": f\"Bearer {TOK}\",\n \"User-Agent\": \"curl/8.5.0\",\n \"Version\": \"2021-04-15\",\n}\n\nSTATE_PATH = os.path.join(REPO, \"logs\", \"transcript-census-wide-state.json\")\nOUT_PATH = os.path.join(REPO, \"logs\", \"transcript-census-wide.json\")\n\nSOFT_DEADLINE_SECONDS = float(sys.argv[1]) if len(sys.argv) > 1 else 500.0\nTARGET_CONVERSATIONS = int(sys.argv[2]) if len(sys.argv) > 2 else 300\n\nSTART = time.time()\n\n\ndef elapsed():\n return time.time() - START\n\n\ndef get(url, params=None, max_retries=4):\n for attempt in range(max_retries):\n try:\n r = requests.get(url, headers=HDRS_CONV, params=params, timeout=30)\n except requests.exceptions.RequestException as e:\n print(f\" ! request exception on {url}: {e}\", flush=True)\n time.sleep(2)\n continue\n if r.status_code == 429:\n print(f\" ! 429 rate-limited on {url}, backing off 5s\", flush=True)\n time.sleep(5)\n continue\n return r\n return r\n\n\ndef load_state():\n if os.path.exists(STATE_PATH):\n with open(STATE_PATH) as f:\n return json.load(f)\n return {\n \"conversations_scanned\": [], # list of {id, contactName, lastMessageDate}\n \"conversations_scanned_ids\": [],\n \"calls\": [], # list of call records\n \"cursor_start_after_date\": None,\n \"conversation_ids_seen\": [],\n \"done_collecting_conversations\": False,\n \"conversations_to_walk\": [], # queue of conversation dicts not yet message-scanned\n \"next_walk_index\": 0,\n \"errors\": [],\n }\n\n\ndef save_state(state):\n tmp = STATE_PATH + \".tmp\"\n with open(tmp, \"w\") as f:\n json.dump(state, f)\n os.replace(tmp, STATE_PATH)\n\n\ndef main():\n state = load_state()\n seen_conv_ids = set(state[\"conversation_ids_seen\"])\n\n # Phase 1: collect conversations sorted by recent activity until we have\n # TARGET_CONVERSATIONS or run out, or hit ~30% of deadline budget.\n collect_deadline = SOFT_DEADLINE_SECONDS * 0.35\n if not state[\"done_collecting_conversations\"]:\n start_after_date = state[\"cursor_start_after_date\"]\n while len(state[\"conversations_to_walk\"]) < TARGET_CONVERSATIONS and elapsed() < collect_deadline:\n params = {\n \"locationId\": LOC,\n \"limit\": 100,\n \"sort\": \"desc\",\n \"sortBy\": \"last_message_date\",\n }\n if start_after_date:\n params[\"startAfterDate\"] = start_after_date\n r = get(f\"{BASE}/conversations/search\", params=params)\n time.sleep(0.3)\n if r is None or r.status_code != 200:\n code = r.status_code if r is not None else \"NO_RESPONSE\"\n print(f\"conversations/search FAILED status={code} body={r.text[:300] if r is not None else ''}\", flush=True)\n state[\"errors\"].append({\"phase\": \"conv_search\", \"status\": code, \"body\": r.text[:300] if r is not None else \"\"})\n break\n data = r.json()\n convs = data.get(\"conversations\", [])\n print(f\"[collect] got {len(convs)} conversations, total queued={len(state['conversations_to_walk'])}, elapsed={elapsed():.0f}s\", flush=True)\n if not convs:\n state[\"done_collecting_conversations\"] = True\n break\n new_count = 0\n for c in convs:\n if c[\"id\"] not in seen_conv_ids:\n seen_conv_ids.add(c[\"id\"])\n state[\"conversations_to_walk\"].append({\n \"id\": c[\"id\"],\n \"contactId\": c.get(\"contactId\"),\n \"contactName\": c.get(\"contactName\") or c.get(\"fullName\"),\n \"lastMessageDate\": c.get(\"lastMessageDate\"),\n \"lastMessageType\": c.get(\"lastMessageType\"),\n })\n new_count += 1\n start_after_date = convs[-1][\"lastMessageDate\"]\n state[\"cursor_start_after_date\"] = start_after_date\n state[\"conversation_ids_seen\"] = list(seen_conv_ids)\n if len(convs) < 100:\n state[\"done_collecting_conversations\"] = True\n break\n save_state(state)\n save_state(state)\n\n print(f\"[collect] DONE collecting: {len(state['conversations_to_walk'])} conversations queued, elapsed={elapsed():.0f}s\", flush=True)\n\n # Phase 2: walk each conversation's messages, find TYPE_CALL, check transcription + recording.\n queue = state[\"conversations_to_walk\"]\n idx = state[\"next_walk_index\"]\n calls = state[\"calls\"]\n scanned = state[\"conversations_scanned\"]\n\n while idx < len(queue) and elapsed() < SOFT_DEADLINE_SECONDS:\n conv = queue[idx]\n conv_id = conv[\"id\"]\n # fetch all messages for this conversation (paginate)\n last_message_id = None\n page_count = 0\n conv_calls_found = 0\n while page_count < 10: # safety cap: 10 pages * 100 = 1000 messages\n params = {\"limit\": 100}\n if last_message_id:\n params[\"lastMessageId\"] = last_message_id\n r = get(f\"{BASE}/conversations/{conv_id}/messages\", params=params)\n time.sleep(0.3)\n page_count += 1\n if r is None or r.status_code != 200:\n code = r.status_code if r is not None else \"NO_RESPONSE\"\n print(f\" ! messages FETCH FAILED conv={conv_id} status={code}\", flush=True)\n state[\"errors\"].append({\"phase\": \"messages\", \"conv\": conv_id, \"status\": code})\n break\n data = r.json()\n mblock = data.get(\"messages\", {})\n msgs = mblock.get(\"messages\", [])\n for msg in msgs:\n if msg.get(\"messageType\") == \"TYPE_CALL\":\n conv_calls_found += 1\n call_id = msg[\"id\"]\n call_record = {\n \"id\": call_id,\n \"conv\": conv_id,\n \"contact\": conv.get(\"contactId\"),\n \"name\": conv.get(\"contactName\"),\n \"at\": msg.get(\"dateAdded\"),\n \"dir\": msg.get(\"direction\"),\n \"status\": (msg.get(\"meta\") or {}).get(\"call\", {}).get(\"status\"),\n \"dur\": (msg.get(\"meta\") or {}).get(\"call\", {}).get(\"duration\"),\n }\n # transcription check\n tr = get(f\"{BASE}/conversations/locations/{LOC}/messages/{call_id}/transcription\")\n time.sleep(0.3)\n call_record[\"transcript\"] = str(tr.status_code) if tr is not None else \"ERR\"\n # recording check\n rec = get(f\"{BASE}/conversations/messages/{call_id}/locations/{LOC}/recording\")\n time.sleep(0.3)\n call_record[\"recording\"] = str(rec.status_code) if rec is not None else \"ERR\"\n calls.append(call_record)\n if not mblock.get(\"nextPage\") or not msgs:\n break\n new_last = mblock.get(\"lastMessageId\")\n if not new_last or new_last == last_message_id:\n break\n last_message_id = new_last\n\n scanned.append({\n \"id\": conv_id,\n \"contactName\": conv.get(\"contactName\"),\n \"lastMessageDate\": conv.get(\"lastMessageDate\"),\n \"calls_found\": conv_calls_found,\n })\n idx += 1\n state[\"next_walk_index\"] = idx\n if idx % 10 == 0:\n print(f\"[walk] {idx}/{len(queue)} conversations scanned, {len(calls)} calls found so far, elapsed={elapsed():.0f}s\", flush=True)\n save_state(state)\n\n save_state(state)\n print(f\"[walk] STOPPED at {idx}/{len(queue)} conversations scanned, {len(calls)} calls found, elapsed={elapsed():.0f}s\", flush=True)\n\n # Write final output summary\n with open(OUT_PATH, \"w\") as f:\n json.dump({\n \"conversations_scanned_count\": len(scanned),\n \"conversations_scanned\": scanned,\n \"calls\": calls,\n \"errors\": state[\"errors\"],\n }, f, indent=1)\n print(f\"Wrote {OUT_PATH}\", flush=True)\n print(f\"DONE_FLAG idx={idx} queue_len={len(queue)} done_collecting={state['done_collecting_conversations']}\", flush=True)\n\n\nif __name__ == \"__main__\":\n main()\n\n\n=====FILE watchdog/main.ts =====\n// dogsspot_watchdog — v1.6 (5 Aug 2026: knowledge-base tamper watch, shared Square figures, scheduled-vs-manual run stamps) / v1.5 (4 Aug 2026: GHL direct health + workflow tamper detection + puppy send-failure scan + panel surfacing via wd_public)\n//\n// WHY THIS EXISTS\n// Three automations run unattended against a live client account: the Pups Club announcer,\n// the reschedule notifier, and the Square/GoHighLevel revenue bridge. Every one of them fails\n// SILENTLY. A dead scheduler, a rotated token, a disabled webhook subscription and a genuinely\n// quiet trading day all look identical from the outside: nothing happens, and nobody finds out\n// until a customer complains or a month of revenue is missing from a report.\n//\n// This val is the supervisor. It reads the state the other three leave behind, applies the\n// checks a human would apply, and emails only when something is actually wrong — plus one\n// all-clear a week so that silence from the watchdog is never itself ambiguous.\n//\n// It is strictly READ-ONLY against the client's GoHighLevel account. It writes nothing but its\n// own digest blob. That is deliberate: a supervisor that can change things is a second thing\n// that can break things.\n\nimport { blob } from \"https://esm.town/v/std/blob\";\nimport { email } from \"https://esm.town/v/std/email\";\n\nconst BRIDGE_URL = \"https://amir5--41ace24c7e2111f18c9d1607ee4eb77e.web.val.run\";\n\nconst DIGEST_KEY = \"wd_digest\";\nconst ALERT_KEY = \"wd_last_alert\";\nconst CHECK_KEY = \"wd_last_check\";\n\n// v1.2 — EMAIL DISCIPLINE, learned the hard way.\n// v1.1 emailed about a createOpp error that was already fixed, simply because the error sat\n// inside a rolling 24-hour window. A monitor that reports history rather than change is a\n// monitor that gets filtered into a folder within a week. Two rules now:\n// 1. Only conditions NEWER than the previous check can raise an alarm.\n// 2. Only CRITICAL reaches the inbox. WARNING and INFO live in the digest, which is always\n// complete and always available — they are for reading on purpose, not for interrupting.\nconst NEW_ERROR_EMAIL_THRESHOLD = 3;\n\n// The two cron vals run every 15 minutes. 90 minutes of silence is ~6 missed cycles: comfortably\n// past a transient platform blip, comfortably short of a day's lost sends.\nconst CRON_STALE_MIN = 90;\n// Square is bursty. A real trading day produces traffic, but a genuinely quiet weekend does not,\n// so 72h avoids crying wolf over a slow Sunday while still catching a disabled subscription.\nconst INBOUND_STALE_H = 72;\nconst ERROR_LOOKBACK_H = 24;\n// Re-send an unchanged alert at most once a day. An alert that repeats hourly is an alert that\n// gets filtered into a folder and never read again.\nconst REALERT_H = 24;\n\ntype Sev = \"CRITICAL\" | \"WARNING\" | \"INFO\";\ninterface Finding {\n sev: Sev;\n system: string;\n what: string;\n why: string;\n}\n\nconst nowMs = Date.now();\nconst ageMin = (iso?: string) => (iso ? (nowMs - Date.parse(iso)) / 60000 : Infinity);\nconst fmtAge = (min: number) =>\n !isFinite(min)\n ? \"never\"\n : min < 60\n ? `${Math.round(min)} min ago`\n : min < 2880\n ? `${(min / 60).toFixed(1)} h ago`\n : `${(min / 1440).toFixed(1)} days ago`;\n\nasync function getBlob(key: string): Promise {\n try {\n return await blob.getJSON(key);\n } catch {\n return null;\n }\n}\n\n/** A cron that stopped firing writes no new state, so staleness is the only honest signal. */\nfunction checkCron(\n name: string,\n state: { ok?: boolean; ts?: string; failed?: number; log?: string[] } | null,\n findings: Finding[],\n) {\n if (!state) {\n findings.push({\n sev: \"CRITICAL\",\n system: name,\n what: \"no state blob at all\",\n why: \"The val has never completed a run, or its state was wiped. It is not doing its job.\",\n });\n return;\n }\n const age = ageMin(state.ts);\n if (!state.ts) {\n findings.push({\n sev: \"INFO\",\n system: name,\n what: \"state has no timestamp yet\",\n why: \"Running a version from before run-timestamps were added. Staleness cannot be checked until it next runs.\",\n });\n } else if (age > CRON_STALE_MIN) {\n findings.push({\n sev: \"CRITICAL\",\n system: name,\n what: `last completed run ${fmtAge(age)}`,\n why: \"Expected every 15 minutes. The scheduler has stopped, or every run is now throwing before it can write state. Sends are being missed right now.\",\n });\n }\n if (state.ok === false) {\n findings.push({\n sev: \"CRITICAL\",\n system: name,\n what: \"last run reported ok:false\",\n why: \"The run completed but knew it had failed. Check the log field in its state blob.\",\n });\n }\n if ((state.failed ?? 0) > 0) {\n findings.push({\n sev: \"WARNING\",\n system: name,\n what: `${state.failed} message(s) failed to send on the last run`,\n why: \"A real customer did not receive a message they should have received. Worth checking who.\",\n });\n }\n}\n\n/** Recent entries in the *_last_error blobs, which the vals write on an unhandled throw. */\nasync function checkErrorBlob(name: string, key: string, findings: Finding[]) {\n const e = await getBlob<{ at?: string; error?: string }>(key);\n if (!e?.at) return;\n const age = ageMin(e.at);\n if (age < ERROR_LOOKBACK_H * 60) {\n findings.push({\n sev: \"WARNING\",\n system: name,\n what: `threw an error ${fmtAge(age)}: ${String(e.error).slice(0, 160)}`,\n why: \"That run did no work. With retries in place this should now be rare — if it repeats, it is not a transient blip.\",\n });\n }\n}\n\n// `trigger` says WHO started this pass. It defaults to \"interval\" because that is how val.town\n// calls the default export: with no arguments. run.ts passes \"manual\" explicitly.\n// [was: no argument at all, so a hand-triggered run and a scheduled one left identical\n// footprints. The dashboard then measured the gaps between those footprints and told Kim\n// \"left to itself it runs about every 95 minutes\" — a sentence about a rhythm, computed from\n// stamps that were mostly me pressing the button. On 4-5 Aug the engine fired on the hour, ten\n// gaps of exactly 60 minutes, while the watchdog fired ZERO times in the same 5h18m window.\n// Its interval is not running, and nothing could say so because nothing knew the difference.]\nexport default async function watchdog(trigger?: unknown) {\n // WHO STARTED THIS PASS, decided by ELIMINATION rather than by trusting the argument.\n // [was: `trigger: \"interval\" | \"manual\" = \"interval\"`, on the assumption that val.town calls\n // the default export with no arguments so the default would apply. It does not: the scheduler\n // passes it something of its own. So `trigger === \"interval\"` was false on every scheduled\n // run, autoHistory stayed empty forever, and the dashboard reported \"nothing on a schedule has\n // been recorded\" while main.ts was firing perfectly and writing to the plain history two lines\n // later. I read that empty list and nearly concluded a second time that the timer was dead.\n // Only run.ts passes the literal string \"manual\"; anything else, including whatever the\n // platform hands us, is a scheduled run.]\n const isManual = trigger === \"manual\";\n const findings: Finding[] = [];\n // v1.5.1 (review fix #12), ONE checkpoint read and ONE scan-start stamp shared by every\n // journal scan, so rows written while this very run executes land in the NEXT window\n // instead of vanishing between two different reads of the checkpoint.\n const scanStartIso = new Date().toISOString();\n const prevCheck = await getBlob<{ ts?: string }>(CHECK_KEY);\n const sinceMsShared = prevCheck?.ts ? Date.parse(prevCheck.ts) : nowMs - ERROR_LOOKBACK_H * 3600_000;\n\n // ---- the two cron vals -------------------------------------------------\n checkCron(\"Pups Club announcer\", await getBlob(\"pups2_state\"), findings);\n checkCron(\"Reschedule notifier\", await getBlob(\"apptn_state\"), findings);\n await checkErrorBlob(\"Pups Club announcer\", \"pups2_last_error\", findings);\n await checkErrorBlob(\"Reschedule notifier\", \"apptn_last_error\", findings);\n\n // ---- Puppy Path engine (added 30 Jul — v1.4; cadence corrected v1.5) ----\n // The engine runs every 15 minutes (not hourly as first noted), so 90 min staleness = six\n // missed ticks. Its run report carries `ts` from engine v1.2+.\n checkCron(\"Puppy Path\", await getBlob(\"puppy_run_state\"), findings);\n await checkErrorBlob(\"Puppy Path\", \"puppy_last_error\", findings);\n const psum = await getBlob<{ surgeHolds?: number }>(\"puppy_summary\");\n if ((psum?.surgeHolds ?? 0) > 0) {\n findings.push({\n sev: \"WARNING\",\n system: \"Puppy Path\",\n what: `enrollment surge hold recorded (${psum!.surgeHolds} total)`,\n why: \"More tagged contacts appeared in one run than the safety threshold allows — bulk tagging suspected. Enrollment is frozen until the extra tags are removed or ACKNOWLEDGE_SURGE=true is set. Check puppy_journal.\",\n });\n }\n\n // ---- cancelled appointments that have not happened yet -----------------\n // Written by the reschedule notifier each run. Every entry is a customer who cancelled and is\n // still queued to be reminded about it, because GoHighLevel does not remove a contact from a\n // reminder workflow when the appointment is cancelled — a contact already on a wait step stays\n // there and the send fires anyway. Until an explicit workflow exit exists, this is the only\n // thing standing between that and a customer having to ask twice.\n const cf = await getBlob<{ ts?: string; n?: number; items?: any[] }>(\"apptn_cancelled_future\");\n if (cf && (cf.n ?? 0) > 0) {\n const soonest = (cf.items ?? [])\n .map((i) => i?.startTime)\n .filter(Boolean)\n .sort()[0];\n findings.push({\n sev: \"WARNING\",\n system: \"Appointments\",\n what: `${cf.n} cancelled appointment(s) still in the future${soonest ? `, soonest ${String(soonest).slice(0, 16).replace(\"T\", \" \")}` : \"\"}`,\n why: \"Each one is a customer who may still be reminded about an appointment they cancelled. Check apptn_cancelled_future for the contact ids.\",\n });\n }\n\n // ---- the bridge is reachable ------------------------------------------\n let bridgeVersion = \"unreachable\";\n try {\n const r = await fetch(BRIDGE_URL, { signal: AbortSignal.timeout(15000) });\n const t = await r.text();\n if (!r.ok) {\n findings.push({\n sev: \"CRITICAL\",\n system: \"Square bridge\",\n what: `health check returned HTTP ${r.status}`,\n why: \"Square is posting payments at an endpoint that is not answering. Revenue attribution is dead while this is true.\",\n });\n } else {\n bridgeVersion = (t.match(/v[\\d.]+/) ?? [\"?\"])[0];\n }\n } catch {\n findings.push({\n sev: \"CRITICAL\",\n system: \"Square bridge\",\n what: \"health check did not respond\",\n why: \"The endpoint Square delivers payments to is down. Every payment arriving now is being lost.\",\n });\n }\n\n // ---- is Square still delivering at all? --------------------------------\n // This is the check that did not exist before, and the one most likely to catch a silent\n // multi-week outage: a webhook subscription that has been disabled looks exactly like a\n // quiet week unless something is counting inbound requests.\n const inbound = await getBlob<{ ts?: string; n?: number }>(\"m2_last_inbound\");\n const inAge = ageMin(inbound?.ts);\n if (!inbound?.ts) {\n findings.push({\n sev: \"INFO\",\n system: \"Square bridge\",\n what: \"no inbound request recorded yet\",\n why: \"Heartbeat tracking was only just added. This clears itself the first time Square posts anything.\",\n });\n } else if (inAge > INBOUND_STALE_H * 60) {\n findings.push({\n sev: \"CRITICAL\",\n system: \"Square bridge\",\n what: `no inbound webhook for ${fmtAge(inAge)}`,\n why: \"Either the business has taken no payments at all, or the Square webhook subscription has been disabled or its URL changed. Check Square's Developer dashboard before assuming it is quiet.\",\n });\n }\n\n // ---- bridge errors, but only ones that are actually NEW -----------------\n // Anything already seen on a previous run is history, not news. This is the specific fix\n // for v1.1 alarming on a createOpp failure that the v3.7 bridge deploy had already resolved.\n const journal = (await getBlob(\"m2_bridge_journal\")) ?? [];\n const fresh = journal.filter((r) => Date.parse(r?.ts ?? 0) > sinceMsShared);\n const newErrs = fresh.filter((r) => r?.kind === \"ERROR\");\n const newNoMatch = fresh.filter((r) => r?.kind === \"NO-MATCH\" || r?.kind === \"REFUND-NO-MATCH\");\n\n if (newErrs.length) {\n findings.push({\n sev: \"WARNING\",\n system: \"Square bridge\",\n what: `${newErrs.length} NEW error(s) since the last check — latest: ${String(newErrs.at(-1)?.error).slice(0, 140)}`,\n why: \"Each one is a payment that did not get attached to a customer record. New errors after a period of quiet usually mean a fix has regressed or an upstream API has changed.\",\n });\n }\n if (newNoMatch.length) {\n findings.push({\n sev: \"INFO\",\n system: \"Square bridge\",\n what: `${newNoMatch.length} new payment(s) arrived with no contact details`,\n why: \"Expected while the Square access token is outstanding. Counted here so the backlog is visible, not because anything is broken.\",\n });\n }\n\n // ---- the POS gap, computed ONCE, in the same place everything else computes it ----------\n // Reported as INFO and never emailed: it is a known, accepted, historic condition.\n //\n // [was: this block did its own dedup and its own arithmetic, and both were wrong.\n // (1) It only counted rows carrying NEITHER an email NOR a phone, which dropped 14 of the 87\n // NO-MATCH rows — payments that are still unattributed — and reported 35 payments worth\n // $23,463.99 against a true 40 worth $28,035.99. Understated by $4,572.\n // (2) It deduped by the note TEXT rather than by payment id.\n // (3) `resolvable` counted journal ROWS and was then subtracted from a PAYMENT count, so the\n // \"21 arrived with no identifying detail\" was 35 payments minus 14 rows: two different\n // units, one subtraction, a number that meant nothing.\n // The dashboard already computed this correctly from engine/facts.ts. Two computations of one\n // fact is how the wrong number reached a client message in the first place, so this one is\n // deleted rather than repaired: the watchdog now reads the same function the page reads.\n // Verified 5 Aug against an independent third derivation of the raw journal in Python:\n // 40 payments, $28,035.99, 10 with a trail worth $4,418.99, 30 without worth $23,617.00.]\n //\n // Imported dynamically and unpinned, on purpose. Unpinned so it always matches what the\n // dashboard is showing Kim; dynamic so that if esm.town is having a moment, the watchdog says\n // it could not read the figure instead of dying or, worse, reporting a stale one.\n const backlog = await (async () => {\n try {\n const m = await import(\"https://esm.town/v/amir5/dogsspot_puppy_path/facts.ts\");\n return { ok: true as const, b: m.squareBacklog(journal), say: m.squareSentence as (x: unknown) => string };\n } catch (e) {\n return { ok: false as const, err: String((e as Error)?.message ?? e).slice(0, 200) };\n }\n })();\n\n if (!backlog.ok) {\n findings.push({\n sev: \"WARNING\",\n system: \"Square bridge\",\n what: \"The counter-sale backlog could not be computed this pass\",\n why: `The shared figures module would not load (${backlog.err}). No number is reported rather than a stale or invented one. One pass failing is a blip; several in a row is worth a look.`,\n });\n } else if (backlog.b && backlog.b.payments > 0) {\n findings.push({\n sev: \"INFO\",\n system: \"Square bridge\",\n // No number in `what`. Every figure lives in one generated sentence below, so there is no\n // second place for one of them to drift.\n what: \"Counter sales are recorded but not linked to a name\",\n why: backlog.say(backlog.b) + \" Historic backlog, not a live defect, and the same figures the dashboard shows.\",\n });\n }\n\n // ---- is the GoHighLevel token still alive? -----------------------------\n // Deliberately inferred rather than tested directly. val.town scopes environment variables\n // per val, so giving this watchdog its own copy of the GoHighLevel token would mean a second\n // place the client's credentials live, for no gain. The two cron vals already authenticate\n // against that account every 15 minutes and record what they got back — so their telemetry\n // IS the token check. A dead token cannot produce a healthy calendar count.\n const pupsS = await getBlob(\"pups2_state\");\n const apptnS = await getBlob(\"apptn_state\");\n const calCount = apptnS?.calendars ?? 0;\n const evCount = (apptnS?.events ?? 0) + (pupsS?.events ?? 0);\n const bothFresh = ageMin(pupsS?.ts) < CRON_STALE_MIN && ageMin(apptnS?.ts) < CRON_STALE_MIN;\n if (bothFresh && calCount === 0 && evCount === 0) {\n findings.push({\n sev: \"CRITICAL\",\n system: \"GoHighLevel access\",\n what: \"both crons ran but read zero calendars and zero appointments\",\n why: \"That combination means authentication, not a quiet week — a quiet week still returns the calendar list. The shared token has almost certainly been revoked or expired. Every automation is down until it is replaced.\",\n });\n }\n // Surface any authentication failure the crons logged against individual calendars. A 401 on\n // one calendar while others succeed is a permissions scope problem, not a dead token, and the\n // two need very different responses.\n for (const [nm, st] of [[\"Pups Club announcer\", pupsS], [\"Reschedule notifier\", apptnS]] as const) {\n const authLog = (st?.log ?? []).filter((l: string) => /\\b40[13]\\b/.test(l));\n if (authLog.length) {\n findings.push({\n sev: \"WARNING\",\n system: nm,\n what: `authentication refused on ${authLog.length} calendar(s): ${String(authLog[0]).slice(0, 120)}`,\n why: \"Other calendars in the same run worked, so this is that calendar's permissions rather than the token itself. Appointments on it are invisible to the automation until it is fixed.\",\n });\n }\n }\n\n // ---- v1.5: puppy engine send failures, NEW ones only --------------------\n // The engine journals send_failed per contact. History is not news (same discipline as the\n // bridge errors above): only rows newer than the previous watchdog pass can raise anything.\n {\n const pj = (await getBlob(\"puppy_journal\")) ?? [];\n const newFails = pj.filter((r) => Date.parse(r?.ts ?? 0) > sinceMsShared && /fail|error/i.test(String(r?.event ?? \"\")));\n if (newFails.length >= 1) {\n findings.push({\n sev: newFails.length >= 3 ? \"CRITICAL\" : \"WARNING\",\n system: \"Puppy Path\",\n what: `${newFails.length} NEW failed action(s) in the engine journal — latest: ${String(newFails.at(-1)?.detail ?? \"\").slice(0, 120)}`,\n why: \"Each row is a message or check that did not complete. The engine retries by design, but new failures after quiet usually mean a credential, a rate limit, or an API change.\",\n });\n }\n }\n\n // Set by the knowledge-base watch below and reported in the digest, so \"it ran and saw eight\"\n // is visible rather than inferred from the absence of an alarm.\n let kbWatch = \"not reached\";\n // ---- v1.5: GoHighLevel reachable + workflow registry tamper check -------\n // Direct read, token from the SAME blob the engine already uses (puppy_config) or env — no\n // new place for credentials to live. Answers two questions nothing else answered: is the CRM\n // API itself up, and did anyone add/remove/publish/unpublish a workflow since the last look.\n // The second matters because a second contractor works in this account: a silently published\n // nurture is exactly how double-sends start.\n try {\n let tok = Deno.env.get(\"GHL_TOKEN\");\n if (!tok) tok = (await getBlob<{ ghlToken?: string }>(\"puppy_config\"))?.ghlToken ?? undefined;\n if (!tok) {\n findings.push({ sev: \"INFO\", system: \"GoHighLevel access\", what: \"no token available to the watchdog\", why: \"Direct reachability and workflow tamper checks skipped. The inferred token check above still runs.\" });\n } else {\n const wr = await fetch(\"https://services.leadconnectorhq.com/workflows/?locationId=BQHJ19uohldYe3eqA0bl\", {\n headers: { Authorization: `Bearer ${tok}`, Version: \"2021-04-15\", \"User-Agent\": \"curl/8.5.0\" },\n signal: AbortSignal.timeout(20000),\n });\n if (!wr.ok) {\n findings.push({\n sev: \"CRITICAL\", system: \"GoHighLevel access\",\n what: `workflow list read returned HTTP ${wr.status}`,\n why: \"The CRM API refused a read that worked before. Token revoked, scope changed, or platform outage — every automation reads this account, so treat as down until confirmed otherwise.\",\n });\n } else {\n const wfs = (await wr.json())?.workflows ?? [];\n const reg = wfs.map((w: any) => [w.id, w.name, w.status, String(w.updatedAt ?? w.dateUpdated ?? \"\")]).sort();\n const enc = new TextEncoder().encode(JSON.stringify(reg));\n const hashBuf = await crypto.subtle.digest(\"SHA-256\", enc);\n const hash = [...new Uint8Array(hashBuf)].map((b) => b.toString(16).padStart(2, \"0\")).join(\"\").slice(0, 16);\n const published = wfs.filter((w: any) => w.status === \"published\").length;\n const prev = await getBlob<{ hash?: string; count?: number; published?: number; names?: Record }>(\"wd_wf_registry\");\n const names: Record = {};\n // v1.5.1 (fix #14), updatedAt travels in the name string so an EDITED-in-place workflow\n // (same name, same status, new content) shows up as a named change, not a blank alarm.\n for (const w of wfs) names[w.id] = `${w.name} [${w.status}] @${String(w.updatedAt ?? w.dateUpdated ?? \"\").slice(0, 16)}`;\n if (wfs.length === 0 && (prev?.count ?? 0) > 0) {\n // v1.5.1 (fix #13), a malformed-but-200 response must not wipe the baseline and fire\n // a bogus \"everything removed\" alarm followed by \"everything added\" on recovery.\n findings.push({ sev: \"WARNING\", system: \"GoHighLevel workflows\", what: \"workflow list came back EMPTY on a 200 response\", why: \"Almost certainly a transient API glitch. The tamper baseline was NOT overwritten; if this repeats across passes, treat it as an outage.\" });\n } else if (prev?.hash && prev.hash !== hash) {\n const prevIds = new Set(Object.keys(prev.names ?? {}));\n const nowIds = new Set(Object.keys(names));\n const added = [...nowIds].filter((i) => !prevIds.has(i)).map((i) => names[i]);\n const removed = [...prevIds].filter((i) => !nowIds.has(i)).map((i) => (prev.names ?? {})[i]);\n const changed = [...nowIds].filter((i) => prevIds.has(i) && (prev.names ?? {})[i] !== names[i]).map((i) => `${(prev.names ?? {})[i]} -> ${names[i]}`);\n findings.push({\n sev: \"CRITICAL\", system: \"GoHighLevel workflows\",\n what: `the workflow registry CHANGED (${prev.count} -> ${wfs.length} workflows, ${prev.published} -> ${published} published). Added: ${added.slice(0, 3).join(\"; \") || \"none\"}. Removed: ${removed.slice(0, 3).join(\"; \") || \"none\"}. Changed: ${changed.slice(0, 3).join(\"; \") || \"none\"}`,\n why: \"Nobody on this project changed workflows. If this was not Kim or Kristian acting deliberately, something is editing the account. A newly PUBLISHED nurture can double-message customers the engine also handles. This alert emails immediately and the change is kept in wd_wf_changes.\",\n });\n // v1.5.1 (fix #10), append-only evidence trail, capped at the newest 20 changes, so\n // the single-blob digest overwrite can never destroy what changed and when.\n const hist = (await getBlob(\"wd_wf_changes\")) ?? [];\n hist.push({ ts: new Date().toISOString(), from: prev.hash, to: hash, added, removed, changed });\n await blob.setJSON(\"wd_wf_changes\", hist.slice(-20)).catch(() => {});\n await blob.setJSON(\"wd_wf_registry\", { ts: new Date().toISOString(), hash, count: wfs.length, published, names });\n } else if (wfs.length > 0 || (prev?.count ?? 0) === 0) {\n await blob.setJSON(\"wd_wf_registry\", { ts: new Date().toISOString(), hash, count: wfs.length, published, names });\n }\n }\n\n // ---- v1.6: the KNOWLEDGE BASES, watched the same way as the workflows ----------------\n // `kbWatch` ends up in the digest snapshot so a human can see, at a glance, that this ran\n // and what it saw. A check whose only evidence is the absence of an alarm is not evidence.\n // WHY. The consolidated knowledge base is what Chloe answers customers from. It carries the\n // rules that cost the client relationship if they slip: no training prices, opening hours\n // never without the appointment-only line, no grooming, \"Pup Talk\" and never \"discovery\n // call\". It was edited at 02:38 on 5 August, by somebody, and nothing noticed. Workflows\n // have been watched since v1.5; the documents that decide what Kim's business SAYS were not.\n //\n // The API gives names, timestamps and a count of what is inside each base, but not the text\n // of the documents. So this cannot check the wording. It can say \"something changed, here,\n // on this date\", which turns a silent edit into a question somebody asks.\n try {\n const kr = await fetch(\"https://services.leadconnectorhq.com/knowledge-base/?locationId=BQHJ19uohldYe3eqA0bl\", {\n headers: { Authorization: `Bearer ${tok}`, Version: \"2021-07-28\", \"User-Agent\": \"curl/8.5.0\" },\n signal: AbortSignal.timeout(12000),\n });\n if (!kr.ok) kbWatch = `http ${kr.status}`;\n else {\n const kbs = (await kr.json())?.data?.knowledgeBases ?? [];\n kbWatch = `read ${kbs.length} knowledge base(s)`;\n const names: Record = {};\n for (const k of kbs) names[k.id] = `${k.name} @${String(k.updatedAt ?? \"\").slice(0, 16)}`;\n const prev = await getBlob<{ names?: Record; count?: number }>(\"wd_kb_registry\");\n // The comparison itself lives in engine/registry-diff.ts and is unit-tested there, so it\n // is not a check that has only ever been seen not firing. Imported unpinned, same as the\n // Square figures, so there is one implementation rather than two that can drift apart.\n const rd = await import(\"https://esm.town/v/amir5/dogsspot_puppy_path/registry-diff.ts\");\n if (rd.looksLikeAGlitch(kbs.length, prev?.count)) {\n findings.push({ sev: \"WARNING\", system: \"GoHighLevel knowledge bases\", what: \"the knowledge base list came back EMPTY on a 200 response\", why: \"Almost certainly a transient API glitch. The baseline was NOT overwritten, so the next good pass will not fire a bogus 'everything came back' alarm.\" });\n } else if (prev?.names) {\n const c = rd.registryDiff(prev.names, names);\n if (c.changed) {\n findings.push({\n sev: \"WARNING\",\n system: \"GoHighLevel knowledge bases\",\n what: \"a knowledge base changed since the last look\",\n why: rd.registrySentence(c, \"her knowledge bases\") +\n \" This is what Chloe answers customers from, so a change here changes what the business says. Worth asking who made it and re-reading the wording rules against it. Not an alarm on its own: Kim edits her own knowledge base and that is exactly as it should be.\",\n });\n const hist = (await getBlob(\"wd_kb_changes\")) ?? [];\n hist.push({ ts: new Date().toISOString(), added: c.added, removed: c.removed, edited: c.edited });\n await blob.setJSON(\"wd_kb_changes\", hist.slice(-20)).catch(() => {});\n }\n await blob.setJSON(\"wd_kb_registry\", { ts: new Date().toISOString(), count: kbs.length, names });\n } else if (kbs.length) {\n await blob.setJSON(\"wd_kb_registry\", { ts: new Date().toISOString(), count: kbs.length, names });\n }\n }\n } catch (e) {\n // NOT SWALLOWED SILENTLY. The dynamic import can fail, the endpoint can move, and a bare\n // catch here would mean the knowledge-base watch was simply not running while everything\n // downstream reported healthy. That is the same shape as the dry tagging pass, which was\n // deployed, hash-verified, green on every test and dead for three deploys because nothing\n // checked that the code had actually executed.\n kbWatch = `failed: ${String((e as Error)?.message ?? e).slice(0, 120)}`;\n findings.push({\n sev: \"WARNING\", system: \"GoHighLevel knowledge bases\",\n what: \"the knowledge-base watch did not run this pass\",\n why: `${kbWatch}. Nothing is broken in Kim's account because of this; it means nobody is watching her knowledge bases until it runs again. Several passes in a row is worth a look.`,\n });\n }\n }\n } catch (e) {\n findings.push({ sev: \"WARNING\", system: \"GoHighLevel access\", what: `direct reachability check failed: ${String(e).slice(0, 100)}`, why: \"Could not confirm the CRM API is up. If the crons are also stale this is an outage; if they are fresh it is likely a transient timeout.\" });\n }\n\n // ---- assemble ----------------------------------------------------------\n const rank: Record = { CRITICAL: 0, WARNING: 1, INFO: 2 };\n findings.sort((a, b) => rank[a.sev] - rank[b.sev]);\n const worst: Sev | \"OK\" = findings.find((f) => f.sev === \"CRITICAL\")\n ? \"CRITICAL\"\n : findings.find((f) => f.sev === \"WARNING\")\n ? \"WARNING\"\n : findings.length\n ? \"INFO\"\n : \"OK\";\n\n const digest = {\n ts: new Date().toISOString(),\n worst,\n bridgeVersion,\n findings,\n snapshot: {\n pups: pupsS,\n apptn: apptnS,\n lastInbound: inbound,\n journalRows: journal.length,\n knowledgeBases: kbWatch,\n },\n };\n await blob.setJSON(DIGEST_KEY, digest);\n\n // v1.5 — one tiny public-facing summary the control panel renders in plain English, so Kim\n // can see that an independent second system is checking the first one. No details here beyond\n // a headline; the digest carries the full findings for whoever investigates.\n // v1.5.2 — the watchdog's own footprints. The dashboard used to grade this system purely on the\n // contents of its last report, so a watchdog that had silently stopped an hour ago still showed\n // a green tick on the strength of a stale \"nothing wrong\". It now reports how punctual the\n // watchdog has actually been, measured from these stamps rather than asserted by anyone.\n let wdHistory: string[] = [];\n let autoHistory: string[] = [];\n try {\n const prevPub = await blob.getJSON(\"wd_public\").catch(() => null);\n wdHistory = Array.isArray(prevPub?.history) ? prevPub.history.filter((x: unknown) => typeof x === \"string\") : [];\n if (!wdHistory.length && typeof prevPub?.ts === \"string\") wdHistory = [prevPub.ts];\n autoHistory = Array.isArray(prevPub?.autoHistory) ? prevPub.autoHistory.filter((x: unknown) => typeof x === \"string\") : [];\n } catch { /* never fail a watchdog run over its own bookkeeping */ }\n if (wdHistory[wdHistory.length - 1] !== digest.ts) wdHistory.push(digest.ts);\n // ONLY a scheduled pass counts towards the rhythm. A cadence measured over button presses is a\n // measurement of the person pressing the button.\n if (!isManual && autoHistory[autoHistory.length - 1] !== digest.ts) autoHistory.push(digest.ts);\n\n await blob.setJSON(\"wd_public\", {\n ts: digest.ts,\n history: wdHistory.slice(-40),\n autoHistory: autoHistory.slice(-40),\n // The last time it ran WITHOUT being asked. Null means it has never run on its own, which is\n // a different and much worse thing than \"it is a bit late\".\n lastAutoTs: autoHistory.length ? autoHistory[autoHistory.length - 1] : null,\n lastTrigger: isManual ? \"manual\" : \"scheduled\",\n worst,\n headline:\n worst === \"OK\"\n ? \"The independent watchdog checked everything and found nothing wrong.\"\n : worst === \"INFO\"\n ? \"The watchdog is running; only informational notes on file, nothing wrong.\"\n : worst === \"WARNING\"\n ? `The watchdog flagged ${findings.filter((f) => f.sev === \"WARNING\").length} thing(s) for Amir to look at. Anything urgent turns this line red and says to call him; this is the level below that.`\n : \"The watchdog found a problem and has alerted Amir. If this stays red for more than an hour, call him.\",\n }).catch(() => {});\n\n // ---- decide whether to actually email ----------------------------------\n // CRITICAL always reaches the inbox. A run of genuinely new bridge errors does too, because\n // a fix regressing is worth interrupting someone for. Everything else waits in the digest.\n const criticals = findings.filter((f) => f.sev === \"CRITICAL\");\n const worthWaking = criticals.length > 0 || newErrs.length >= NEW_ERROR_EMAIL_THRESHOLD;\n\n // v1.5.1 (review fix #11), ages and counts stripped before fingerprinting: \"1.6 h ago\"\n // becoming \"1.8 h ago\" is the same condition, and re-emailing it every pass trains the\n // inbox to ignore the address. REALERT_H still re-sends an unchanged alert daily.\n const stableWhat = (s: string) => s.replace(/\\d+(?:\\.\\d+)?\\s*(?:h|min|minute|hour|day)s?\\b/g, \"N\").replace(/\\d{4}-\\d{2}-\\d{2}[T ][\\d:.]+Z?/g, \"T\").slice(0, 60);\n const fingerprint = worthWaking\n ? criticals.map((f) => `${f.system}:${stableWhat(f.what)}`).join(\"|\") +\n (newErrs.length >= NEW_ERROR_EMAIL_THRESHOLD ? `|errors` : \"\")\n : \"\";\n\n const last = await getBlob<{ fp?: string; ts?: string }>(ALERT_KEY);\n const changed = fingerprint !== (last?.fp ?? \"\");\n const stale = ageMin(last?.ts) > REALERT_H * 60;\n const isMonday = new Date().getUTCDay() === 1;\n\n let sent = false;\n if (fingerprint && (changed || stale)) {\n // CRITICAL and WARNING only in the body. INFO is digest-only by design — a known,\n // accepted condition restated in an alert email is how alerts stop being read.\n const body = findings\n .filter((f) => f.sev !== \"INFO\")\n .map((f) => `[${f.sev}] ${f.system}\\n ${f.what}\\n ${f.why}`)\n .join(\"\\n\\n\");\n await email({\n subject: `Dogs Spot systems — action needed`,\n text: `${body}\\n\\n---\\nChecked ${digest.ts}\\nBridge ${bridgeVersion} · journal ${journal.length} rows\\nOnly conditions newer than the previous check can trigger this email. Warnings and notes that did not meet that bar are in the digest, not here.`,\n });\n await blob.setJSON(ALERT_KEY, { fp: fingerprint, ts: digest.ts });\n sent = true;\n } else if (!fingerprint && isMonday && ageMin(last?.ts) > 6 * 24 * 60) {\n const notes = findings.length\n ? `\\n\\nOpen items, none urgent:\\n` +\n findings.map((f) => ` · ${f.system} — ${f.what}`).join(\"\\n\")\n : \"\";\n await email({\n subject: \"Dogs Spot systems — all clear\",\n text: `Nothing wrong across the announcer, the reschedule notifier and the Square bridge.${notes}\\n\\nChecked ${digest.ts}\\nBridge ${bridgeVersion} · journal ${journal.length} rows\\n\\nWeekly confirmation that the watchdog itself is alive.`,\n });\n await blob.setJSON(ALERT_KEY, { fp: \"\", ts: digest.ts });\n sent = true;\n }\n\n // Stamp the checkpoint LAST, so a crash mid-run does not silently swallow new errors.\n // v1.5.1 (fix #12), the checkpoint is the SCAN START: rows journaled while this run was\n // executing stay newer than the stamp and surface on the next pass instead of vanishing.\n await blob.setJSON(CHECK_KEY, { ts: scanStartIso });\n\n return { ...digest, emailed: sent };\n}\n\n\n=====FILE watchdog/run.ts =====\n// CHECK NOW — manual trigger for the watchdog, mirroring the engine's run.ts pattern.\n// Same admin key as the control panel, digest-only in source, one code path: this imports the\n// exact watchdog() the scheduler calls. Added v1.5 so a deploy can be verified the minute it\n// ships instead of waiting for the next scheduled pass.\nimport watchdog from \"./main.ts\";\n\nconst KEY_SHA256 = \"48cd12465712045f70247da1689eeb198a4ce2d98416d8e52fb844581f044f15\";\nasync function sha256Hex(s: string): Promise {\n const b = await crypto.subtle.digest(\"SHA-256\", new TextEncoder().encode(s));\n return [...new Uint8Array(b)].map((x) => x.toString(16).padStart(2, \"0\")).join(\"\");\n}\nexport default async function (req: Request): Promise {\n const k = new URL(req.url).searchParams.get(\"k\") || \"\";\n const expected = Deno.env.get(\"NURTURE_ADMIN_KEY_SHA256\") || KEY_SHA256;\n if ((await sha256Hex(k)) !== expected) {\n return new Response(\"Not found\", { status: 401 });\n }\n // \"manual\" so this press does not get counted as the watchdog keeping its own schedule.\n const out = await watchdog(\"manual\");\n return new Response(JSON.stringify({ triggeredAt: new Date().toISOString(), result: out ?? \"ran\" }, null, 2), {\n headers: { \"content-type\": \"application/json\" },\n });\n}\n\n\n=====FILE handover/PLAN-TO-FINISH.md =====\n# What is left, in the order it has to happen\n\nUpdated 5 August 2026, 11:50, after a night of work while you were on shift. Everything here is\neither a thing I build or a door you open.\n\n---\n\n## What changed while you were out\n\n**The test suite is back, and bigger than it was.** Deliberately not quoting a number here, because\na number in a document is a number that goes stale: run `node tests/run-all.mjs` and it tells you.\nThe part that matters is `node tests/negative-controls.mjs`. Each control breaks the code on\npurpose, in a temporary copy, and demands a *named* test go red. If the wrong test catches it, or\nnothing does, the control fails. That is the thing we did not have when three fake checks shipped.\nFour of the controls exist because they caught one of my own checks lying.\n\n**It survives a reclaim now.** `handover/SOURCE-BUNDLE.part{1,2,3}.txt` holds every file that is\nnot already on val.town, and the same three parts are stored *on the val* as inert files. The\nrestore command is in the header of each part, and I have actually run it into an empty folder and\ndiffed the result: byte identical, every file. `scripts/build.mjs` and `scripts/deploy.mjs` now\ncarry everything that used to live only in my head, including the two traps that cost time before:\nmain.ts is called `puppy_path_v1.1.ts` locally, and val.town serves you a **cached** copy after a\nwrite, so a verify-by-read straight after a deploy shows the old hash and looks like a failure.\n\n### Four real defects found and fixed\n\n1. **The watchdog was reporting different money from the dashboard.** It said 35 counter sales\n worth $23,463.99. The dashboard said 40 worth $28,035.99. I re-derived it a third time, from\n the raw journal, in Python, without looking at either implementation: **40 is right**. The\n watchdog was skipping any row that carried an email or phone, and it was subtracting a count of\n journal *rows* from a count of *payments* to get its \"unresolvable\" figure. Two different units,\n one subtraction. It now imports the same function the dashboard uses, so they cannot disagree\n again.\n\n2. **The watchdog was set to look once a day. Now hourly. DONE, no longer yours.**\n I wrote in the first version of this file that its timer \"has never fired\". That was wrong, and\n wrong in two separate ways, both of which are worth reading because they are the same mistake\n twice.\n\n Opening the schedule showed **Runs every 1 days** — deliberately, by you, a week ago (val.town\n still has the chat: *\"can you set the watchdog to daily on...\"*). So the timer was firing\n perfectly, once every 24 hours. A problem starting just after it looked could sit unnoticed\n until the next day, while the thing it watches runs hourly. **Changed to hourly. Confirmed on\n the schedule screen: \"Runs every 1 hrs\".**\n\n Then it still reported no scheduled runs, and I nearly concluded a second time that the timer\n was dead. It was not. **The counter I had built that morning was broken.** I had assumed\n val.town calls the scheduled function with no arguments; it passes one of its own, so my\n \"is this a scheduled run\" check was false every single time. The scheduled runs were in the\n plain run record one line from where I was looking. Fixed by deciding it the other way round:\n only the manual endpoint says so, everything else is scheduled. **Both directions have now been\n watched working** — a scheduled run recorded as scheduled, a hand-started one as by hand.\n\n Kim's page reads **\"Everything we run is healthy\"** for the first time.\n\n3. **The page was quoting my button presses back to Kim as the watchdog's schedule.** It said\n \"left to itself it runs about every 95 minutes\". That number was honestly measured off the\n wrong thing. Scheduled and manual runs are recorded separately now, and the page says plainly\n which it is looking at. It is in the work log as my mistake, because it was.\n\n4. **A check passed on my own comment.** `D2b.1` forbade a call, I removed the call, and wrote a\n `[was: ...]` note above it naming the call I had removed. The test matched the note and stayed\n green. Every structural check now reads the file with comments stripped, and there is a control\n that puts the forbidden text *only* inside a comment and demands the test stay green.\n\n### The go-live blocker is no longer blocked, and the third switch is built\n\n**I was wrong that this needed a new scope.** I tested a tag write and a tag delete against my own\ntest contact on the token we already have: both work, HTTP 201 and 200. The `locations/tags.readonly`\nscope only lets me *list* the account's tag vocabulary. It was never in the way.\n\nSo the tagging is built, and it is running now:\n\n- `engine/puppy-detect.ts` decides who counts as a puppy inquiry, from what they wrote when they\n got in touch. It **cannot apply a tag** and that is structural rather than a promise: the file\n contains no fetch, no client, no POST. A test asserts it and a negative control adds a fetch call\n and demands the test go red.\n- The engine calls it once per run, in **both** modes, and writes the counts down. Kim's page shows\n them, with a staleness line if the pass ever stops.\n- A full dry pass over 1,200 contacts is in `handover/Puppy-tagging-candidates.xlsx`: **39 clear,\n 55 probable, 552 not a puppy, 554 with nothing written down to judge by.** Nothing tagged.\n\n**My first version of it would have signed up three people who should not have been.** A man asking\nto *buy* a puppy, a woman *rehoming* her older dogs, and a dog described as \"3 years and 4 months\nold\" read as four months. Each is a rule now, each rule has a test, each test has a control.\n\n**Then my own test caught the years bug still present in the rewrite.** The pattern wanted\n\"3-year-old\"; \"3 years and 4 months old\" puts the word \"old\" after the months, so it fell through\nto the months branch. Fixed and pinned.\n\n**One decision is Kim's, not ours.** A one-year-old dog sits exactly on the boundary and there are\na lot of them. Her slow track covers the teenage stage, so they may well belong. It is on her page.\n\n### Two more findings, late on\n\n**Her knowledge base was edited at 02:38 this morning and nothing was watching it.** That is 22:38\nher time, so it is very likely Kim herself, and if so it is exactly what should happen. But the\nconsolidated knowledge base is what Chloe answers customers from — it carries the no-training-prices\nrule, the appointment-only rule, the no-grooming rule and \"Pup Talk\" — and we have been watching her\n165 automations for changes since 4 August while not watching the documents that decide what her\nbusiness says. The watchdog now watches both. The comparison lives in `engine/registry-diff.ts` with\nits own tests, so it is not another check that has only ever been seen not firing.\n\n**The knowledge base IS readable through the API.** The master handoff says it is UI-only; that is\nwrong, or it has changed. `GET /knowledge-base/?locationId=…` lists all eight, and `GET\n/knowledge-base/{id}` gives names, timestamps and a count of what is inside. The document *text* is\nstill not exposed, so **step 4, the \"discovery call\" wording sweep, still needs the UI** — but we now\nknow exactly what to open: the consolidated base holds 9 items (7 rich text, 1 URL, 1 table).\n\n### Two things that are better than they were\n\n- **The go-live blocker is now counted live.** The page used to say \"1,200 of your most recent\n contacts were checked\". That was a scan size dressed as an answer. GoHighLevel will filter\n contacts by tag server-side, so it now reads **all 5,544** every time the page loads. Zero carry\n the tag. Cross-checked against a full page-by-page walk of the whole contact base: the filter\n and the walk agree exactly on three other tags, so the zero is trustworthy.\n- **The five sequences Kim asked about are reviewed.** `handover/NURTURE-REVIEW-FOR-KIM.md`. They\n are live, they are busy, and the topics collide with ours. Details in that file.\n\n---\n\n## GO-LIVE IS STILL THREE SWITCHES, AND ALL THREE NOW EXIST\n\nOur system enrolls people carrying the tag `nurture - puppy`. **All 5,544 contacts checked, live,\non every page load: zero carry it, and nothing in her account applies it.** Done as two switches it\nwould go live and reach nobody, and it would look like it was working, because the engine would\nreport healthy runs with zero enrollments.\n\nThe third switch is now built and running in dry mode (see above). What is left on it is not code:\n\n1. **Amir reads the candidate list** in `handover/Puppy-tagging-candidates.xlsx` and says whether\n the 39 clear ones look right to him. That is the sanity check on my judgement, not a formality.\n2. **Kim answers the one-year-old question.** It is on her page.\n3. **Arming it** happens on the go-live call, with her watching, alongside the other two switches.\n\nNothing about it is waiting on a scope, a token, or anybody's permission any more.\n\n---\n\n## DOORS I NEED YOU TO OPEN\n\n**1. Meta: give the system user an app role.** Unchanged from before, and still the one that puts\nmoney on the page. Order matters:\n\n- Business Settings, Apps, pick one of her apps, add `dogsspot-reporting` as a user on it\n- *Then* System Users, Generate New Token, tick `ads_read` and `read_insights`\n- *Then* Add Assets, Ad Accounts, tick the account, give View Performance\n- Send me the token and I swap it in val.town in two minutes\n\n**2. GHL token scopes.** Still worth having, but **no longer blocking anything**. Four read-only\nscopes on the integration starting `pit-064237ea`, at Settings, Private Integrations. **Do not\nregenerate the token** — that changes it, which takes the engine offline *and* silently kills Kim's\ndashboard link, because her view key is derived from it.\n\n- `locations.readonly`\n- `locations/customFields.readonly`\n- `locations/tags.readonly`\n- `forms.readonly`\n\n**3. ~~The watchdog's schedule~~ — done, by me, in the val.town UI. Nothing needed from you.**\n\n**4. ~~Chrome cannot be scripted from here~~ — solved.** The AppleScript route does fail with\n\"Chrome is not running\" (that setting is off), but the **extension** route works fine and is what\nyour own master handoff already said to use. I have re-read that note and stopped treating the\nbrowser as blocked. Turning the AppleScript setting on is still worth doing one day, but nothing\nis waiting on it.\n\n**5. Sign into GoHighLevel in Chrome and stay signed in.** The session has expired. Two builds sit\nbehind it: the typing chat agent Kim asked for, and deleting the stale Voice AI widget.\n\n**6. Your retainer figure.** Still the only line item on the page with no number against it.\n\n**7. Nothing else.** Square is granted and working. val.town environment variables are set and\nverified. The Meta ad account id is in place.\n\n---\n\n## WHAT I BUILD, IN ORDER\n\n### Done since the last version of this file\n1. ~~Rebuild the test suite~~ — 11 suites, 151 checks, 30 negative controls.\n2. ~~Store it where a reclaim cannot reach it~~ — three bundle parts, on the val, restore verified\n by actually restoring.\n3. ~~Review the five no-sale sequences~~ — `handover/NURTURE-REVIEW-FOR-KIM.md`.\n\n### Next\n4. ~~The tagging mechanism~~ — built, running in dry mode, 1,200-contact review list delivered.\n What is left on it is Kim's answer on the one-year-old boundary, and Amir's read of the list.\n5. **The go-live drill**, from my own phone, in practice mode: STOP handling, reply-pause, the\n watchdog seeing it, the panel showing it. Watched end to end before anyone real is touched.\n6. **The three switches, together, with Kim watching.** Blocked on her go-live answer, her wording\n sign-off, and the email domain.\n7. **Meta spend**, once door #1 lands.\n8. **Google Ads.** Coded, never run against a live account. Still the least-finished thing I own.\n It gets an account and gets tested, or it comes off the list honestly.\n9. **The deposit automation**, scoped once I have watched a few holiday bookings move.\n10. ~~The missing call transcripts~~ — answered. The recordings are all there (54 of the 62 calls\n checked, about two and a quarter hours of audio; the 8 without are calls nobody answered).\n Transcription is a separate switch at Settings → Phone System → Voice → Call Transcription,\n about 2.4 cents per recorded minute, and it does **not** apply retroactively. It is question 13\n on Kim's page. **Candice's app stalling** is still open: her CRM holds 5,516 conversations and\n the message API takes 0.4 to 2.7 seconds each, so any screen loading them one at a time takes\n over half an hour. That is a hypothesis about somebody else's code, not a finding, and I have\n said so rather than dressing it up.\n11. **The typing chat agent**, blocked on door #5.\n12. **The knowledge-base wording sweep**: confirm \"discovery call\" appears nowhere in the KB.\n13. **Friday reports.** Renders correctly; wants a scheduled snapshot and one send Kim has\n actually received before we call it done.\n\n---\n\n## WHAT I WILL NOT DO\n\n- Contact Kim. Every question goes in the ledger.\n- Take anything out of practice mode without her word and your presence.\n- Invent a story, a testimonial, a customer or an event for the eight empty slots.\n- Type a live number into a document again. Anything countable is counted at render time.\n- Ship a finding I could not stand up. There is one in the nurture review that I dropped for\n exactly that reason, and I said so in the document rather than quietly leaving it out.\n\n---\n\n## HOW THIS ENDS\n\nGo-live is three switches thrown together on a call with Kim watching, after a drill from my own\nphone, with the email domain verified and the tagging built.\n\nThe honest state this morning: the machinery is built, verified live, and now genuinely guarded by\nchecks that have been proven able to fail. Nothing has reached a customer. The gap is three\ndecisions from her and three doors from you.\n\n\n=====FILE handover/SEND-TO-KIM.txt =====\nKim, everything you sent over is in. Taking your notes in order.\n\nThe puppy's name is gone from every message, all forty-one, not just the ones you were reading. You were right, and for a reason I hadn't checked until you said it: I went and counted where your inquiries actually come from, and the large majority arrive as a message on Facebook or Instagram. Those almost never carry a dog's name, so a placeholder for it was always going to sit empty most of the time. The messages don't lean on it now, they use your customer's own name instead, and I rewrote each sentence around it rather than just deleting the word, so nothing reads like it's had a hole punched in it.\n\nYou were spotting a pattern rather than two words, so I treated it as one. Potty training and yard now, and I went back through the rest of the older copy for the same thing and found a few more that read English rather than American. The newer half was already written that way, so it was only the early messages that were off. There is a check on it now, so it stays fixed rather than drifting back the next time I write something.\n\nDaycare is gone completely, and thank you for catching it, because that one was a proper mistake rather than a wording preference. It was in four separate messages offering a service you don't provide. It's the same class of error as if I'd had you offering grooming, and there's now an automatic check that fails the whole build if the word ever reappears anywhere a customer could see it.\n\nBoth of the missed-Pup-Talk messages are your version rather than mine now, near enough word for word. The text says \"just reply and I'll schedule it\". The email is your rewrite in full, including \"I know life gets busy\" and \"won't keep bugging you\". They read better than mine did, particularly the ending.\n\nThe first three weeks are attached, six pages, generated straight out of the running system rather than typed up. Same numbering you've been using, so Touch 4 is the fourth thing a customer receives. There's a longer companion with all forty-one if you ever want it, but you've already signed off the slow track and nothing in it changed, so the short one is the one to read.\n\nOn the no sale and no sale-tips nurtures. I've looked, and the useful thing to know is that you already have these running: five follow-up sequences plus two auto-responders, all published and live in your account right now. So I've deliberately not built ours, because putting another sequence next to five live ones is exactly how somebody ends up getting two sets of messages from you in an afternoon. It's the same trap as the puppy one we already have flagged. What I'd suggest is that I read the five you have and tell you which are earning their place before we build anything new. One thing already looks accidental: a workflow called \"Copy - Tips Ad campaign > Auto Responder\" is published while the original it was copied from sits in draft, which usually means somebody duplicated it to make an edit and published the wrong one.\n\nNow the holiday deposit, which is the most useful question you've asked me this week.\n\nYes, and it's closer than you'd think. You already have a product in your CRM called \"Holiday boarding deposit\" set at fifty dollars, fully configured, and it doesn't appear on a single order in the payment history I can see. Same story with \"New Client Boarding Deposit\". The reason they've never fired is that your boarding bookings go through the form on your website rather than through the CRM, so the CRM never gets the chance to take the money or to write down that it arrived. That's why it lands on somebody to check by hand.\n\nTwo ways to fix it, genuinely different sizes of job. The smaller one keeps the booking exactly where it is and records the deposit against the customer automatically once it's paid, so you get a list you can look at instead of a memory you have to trust. The bigger one moves holiday bookings so the deposit is taken as part of the booking itself, which means nobody can complete one without paying and the chasing disappears rather than getting easier. I'd want to watch how the money moves for a few days before recommending one, and I can, because the payment link into your CRM is already live.\n\nThree corrections of my own, because you should hear them from me.\n\nFirst, I was about to ask you for a Square permission you had already given me. You gave it, it's working, and payments have been flowing through it since the start of the month. I had it wrong in an earlier draft of this message and I'd rather correct it than let it stand.\n\nSecond, your dashboard had been telling you there was one person walking through the follow-up messages. There isn't. That one record is a test contact of mine with my own email on it, and the system has never once looked at a real inquiry. The page says so plainly now. Nothing went to anybody, but it was flattering itself and it shouldn't have been.\n\nThird, and this one matters for go-live. Our system only picks people up when they're tagged as a puppy inquiry, and I checked twelve hundred of your contacts: not one carries that tag, and nothing applies it. So switching ours on and the old one off isn't two moves, it's three. If we'd done the two, we'd have gone live and quietly reached nobody. That's on the list now as part of the go-live question, and it's mine to build rather than anything you need to do.\n\nThe email you sent Kristian is good. It's clearer than my draft was, and the last paragraph does the important work.\n\nTwo things I haven't got answers on yet and I'd rather say so than guess: the missing call transcripts, and Candice's app stopping when it loads messages. I have the screenshot. Both live in parts of the system I want to look at properly rather than guess at, and I'll come back on them specifically.\n\nOne last thing. Rather than keep sending you numbers in messages, there's now a page you can open any time that reads your systems the moment you load it. It shows what came in, what happened to it, what we've been doing and what's waiting on you, and it's numbered so a reply saying \"yes to 1 and 3\" is a complete answer. I'll send you the link separately so it isn't buried in this.\n\nNothing has sent to anybody. Everything stays in practice mode until you say the word.\n\nAmir\n\n",[336],"6282fa96-903e-4048-a2fd-1dfa5ab1b017","SOURCE-BUNDLE.part7.txt","771fe81c-91b7-11f1-b53b-1607ee4eb77e",286,["D",1786044233225],"THE DOGS SPOT — SOURCE BUNDLE (part 7 of 9)\n\nEverything in this project that does not already live on val.town. The engine is NOT here:\nseventeen files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff, verified file by file by\nscripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\n\nRESTORE (needs only node, from an empty folder). Save each part, then run this ON EACH ONE:\n\n node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(process.argv[1],\"utf8\");\n for(const s of b.split(\"\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\n\");\n const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});\n fs.writeFileSync(f,c.replace(/\\n$/,\"\"))}' PART.txt\n\nEach part is complete in itself: whole files only, no reassembly, any order.\n\nThen: node scripts/deploy.mjs --check (pulls nothing, proves the val matches)\n node scripts/build.mjs (needs engine/ back from the val first)\n node tests/run-all.mjs\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (11 of 34 files)\n tests/report-logic.test.mjs 6588 bytes 10479c8a8497\n tests/run-all.mjs 6810 bytes 1bd0ac6d5e59\n tests/slow-track.test.mjs 9404 bytes 0bc57258b304\n tests/sms-length.test.mjs 2793 bytes 4b42ded930a4\n tests/stories.test.mjs 3378 bytes 36c5afe09c12\n tests/taper-test.ts 6922 bytes 3ae9fc044871\n scripts/build.mjs 4893 bytes f21f37e458d0\n scripts/bundle.mjs 7385 bytes 4df1a4ce749c\n scripts/deploy.mjs 10262 bytes 519e5c58693b\n scripts/make-pdfs.mjs 3425 bytes dc204790c10f\n scripts/make_pdf.py 5466 bytes f36bb57eb975\n\n================================================================================================\n=====FILE tests/report-logic.test.mjs =====\n// FRIDAY REPORT LOGIC — offline, with failure injection: empty, garbage, huge, boundary.\nimport * as R from \"../build/report-logic.js\";\nimport { suite, ok, eq, scoped } from \"./_harness.mjs\";\nconst { t, done } = suite(\"report-logic\");\nconst ET = -240;\n\nt(\"R1 run on a Friday: the window is the seven days ending that Friday 00:00 ET\", () => {\n const { current, previous } = R.reportWindows(Date.parse(\"2026-08-07T13:00:00Z\"), ET);\n eq(new Date(current.endMs).toISOString(), \"2026-08-07T04:00:00.000Z\");\n eq((current.endMs - current.startMs) / 86400000, 7);\n eq(current.startMs, previous.endMs, \"windows do not abut\");\n return scoped(3, \"assertions\");\n});\nt(\"R2 run on a Monday: still the most recent complete Fri-to-Fri window\", () => {\n eq(new Date(R.reportWindows(Date.parse(\"2026-08-10T20:00:00Z\"), ET).current.endMs).toISOString(), \"2026-08-07T04:00:00.000Z\");\n return \"1 case\";\n});\nt(\"R3 boundary: an event at window end is EXCLUDED, at start INCLUDED\", () => {\n const w = { startMs: 1000, endMs: 2000, label: \"t\" };\n ok(R.inWindow(1000, w) && !R.inWindow(2000, w) && R.inWindow(1999, w) && !R.inWindow(999, w));\n return scoped(4, \"boundaries\");\n});\nt(\"R4 empty data yields zeros and n/a, never a crash\", () => {\n const w = { startMs: 0, endMs: 10, label: \"t\" };\n eq(R.countContacts([], w), 0);\n eq(R.countEvents([], w), { booked: 0, showed: 0, noshow: 0, cancelled: 0 });\n eq(R.sourceBreakdown([], w), []); eq(R.pct(3, 0), \"n/a\");\n eq(R.weeklyBuckets([], 1000, 8), [0,0,0,0,0,0,0,0]);\n return scoped(5, \"empty cases\");\n});\nt(\"R5 garbage is ignored, never counted\", () => {\n const w = { startMs: 0, endMs: Date.parse(\"2027-01-01\"), label: \"t\" };\n const cs = [{ dateAdded: \"not a date\", source: null, tags: [] }, { dateAdded: \"2026-08-01T00:00:00Z\", source: \" \", tags: [] }];\n eq(R.countContacts(cs, w), 1, \"garbage date counted\");\n eq(R.sourceBreakdown(cs, w), [{ source: \"no source recorded\", n: 1 }], \"blank source not normalised\");\n return scoped(2, \"assertions\");\n});\nt(\"R6 100k contacts computes fast and correctly\", () => {\n const end = Date.parse(\"2026-08-07T04:00:00Z\"); const cs = [];\n for (let i = 0; i < 100_000; i++) cs.push({ dateAdded: new Date(end - (i % 56) * 86400000 - 1).toISOString(), source: \"s\", tags: [] });\n const t0 = Date.now(); const b = R.weeklyBuckets(cs, end, 8); const ms = Date.now() - t0;\n eq(b.reduce((a, x) => a + x, 0), cs.filter((c) => Date.parse(c.dateAdded) >= end - 56 * 86400000).length);\n ok(ms < 2000, `too slow: ${ms}ms`);\n return `100k in ${ms}ms`;\n});\nt(\"R7 cancelled events counted separately, never as booked\", () => {\n const w = { startMs: 0, endMs: 10_000, label: \"t\" };\n eq(R.countEvents([\n { startTime: 5, appointmentStatus: \"confirmed\", calendarId: \"x\" },\n { startTime: 6, appointmentStatus: \"showed\", calendarId: \"x\" },\n { startTime: 7, appointmentStatus: \"cancelled\", calendarId: \"x\" },\n { startTime: 8, appointmentStatus: \"noshow\", calendarId: \"x\" },\n ], w), { booked: 3, showed: 1, noshow: 1, cancelled: 1 });\n return \"4 events\";\n});\nt(\"R8 a show rate is only quoted at n>=5\", () => {\n const c = R.draftCommentary({ enq: 1, enqPrev: 1, ptBooked: 3, ptPrev: 0, ptShowed: 2, wonCount: 0, wonValue: 0, wonPrevValue: 0, topSource: null, adTracked: false });\n ok(!c.join(\" \").includes(\"%\"), \"quoted a rate on n=3\");\n ok(R.draftCommentary({ enq: 1, enqPrev: 1, ptBooked: 10, ptPrev: 0, ptShowed: 7, wonCount: 0, wonValue: 0, wonPrevValue: 0, topSource: null, adTracked: false }).join(\" \").includes(\"70%\"));\n return scoped(2, \"sample sizes\");\n});\nt(\"R9 commentary never invents spend or revenue\", () => {\n const c = R.draftCommentary({ enq: 5, enqPrev: 3, ptBooked: 2, ptPrev: 1, ptShowed: 1, wonCount: 1, wonValue: 500, wonPrevValue: 0, topSource: \"phone call\", adTracked: false });\n ok(c.some((l) => l.includes(\"not tracked yet\")));\n ok(!/\\$/.test(c.join(\" \")), \"quoted a money figure the CRM does not hold\");\n ok(c.some((l) => /reached the Customer stage/.test(l)), \"customers not reported by stage\");\n return scoped(3, \"assertions\");\n});\nt(\"R10 deltaWord edge cases\", () => {\n eq(R.deltaWord(5, 0), \"up from zero last week\"); eq(R.deltaWord(4, 4), \"level with last week\");\n ok(R.deltaWord(2, 4).startsWith(\"down 50%\"));\n return scoped(3, \"cases\");\n});\nt(\"R11 weekly buckets place a contact in the correct week\", () => {\n const end = Date.parse(\"2026-08-07T04:00:00Z\");\n const b = R.weeklyBuckets([{ dateAdded: new Date(end - 3 * 86400000).toISOString(), source: null, tags: [] },\n { dateAdded: new Date(end - (7 * 7 + 3) * 86400000).toISOString(), source: null, tags: [] }], end, 8);\n eq(b[7], 1, \"latest bucket\"); eq(b[0], 1, \"oldest bucket\");\n return scoped(2, \"buckets\");\n});\nt(\"R12 every headline number has a plain-English formula with no field names\", () => {\n const keys = [\"New inquiries\", \"Pup Talks on the calendar\", \"Show rate\", \"New customers\", \"Up or down on last week\", \"Cost per inquiry\", \"Did the ad leads land\"];\n for (const k of keys) ok(R.FORMULAS[k], `missing formula ${k}`);\n ok(!/dateAdded|appointmentStatus|lastStageChangeAt|monetaryValue|startTime/.test(Object.values(R.FORMULAS).join(\" \")), \"code field names leaked\");\n return scoped(keys.length, \"formulas\");\n});\nt(\"R13 attribution reads the field that holds the answer, not the blank column\", () => {\n const w = { startMs: 0, endMs: 2e13, label: \"x\" };\n const cs = [\n { dateAdded: \"2026-08-01T00:00:00Z\", source: null, tags: [], attribution: { medium: \"facebook\", campaign: \"K1\" } },\n { dateAdded: \"2026-08-01T00:00:00Z\", source: null, tags: [], attribution: { medium: \"facebook\", campaign: \"K1\" } },\n { dateAdded: \"2026-08-01T00:00:00Z\", source: \"phone call\", tags: [], attribution: { medium: \"instagram\", campaign: null } },\n { dateAdded: \"2026-08-01T00:00:00Z\", source: null, tags: [] },\n ];\n eq(R.channelBreakdown(cs, w), [{ source: \"Facebook\", n: 2 }, { source: \"Instagram\", n: 1 }, { source: \"not recorded\", n: 1 }]);\n eq(R.campaignBreakdown(cs, w), [{ name: \"K1\", n: 2 }]);\n eq(R.attributionCoverage(cs, w), { known: 3, total: 4 });\n eq(R.sourceBreakdown(cs, w).find((s) => s.source === \"no source recorded\").n, 3, \"the blank column would have called 3 unknown\");\n return scoped(cs.length, \"contacts\");\n});\nt(\"R14 an unanticipated channel is named, never swallowed into 'other'\", () => {\n eq(R.channelBreakdown([{ dateAdded: \"2026-08-01T00:00:00Z\", source: null, tags: [], attribution: { medium: \"tiktok_ads\" } }], { startMs: 0, endMs: 2e13, label: \"x\" }),\n [{ source: \"tiktok ads\", n: 1 }]);\n return \"1 channel\";\n});\ndone();\n\n\n=====FILE tests/run-all.mjs =====\n// THE RUNNER. Discovers every suite in this folder, runs it, and refuses to report green on\n// anything it did not actually observe pass.\n//\n// [was: a shell glob over tests/*.mjs. taper-test.ts sat at 28/29 RED for two days while the glob\n// reported \"all green\", because a .ts file is not a .mjs file. Discovery is by folder listing now,\n// and a file it cannot run is a FAILURE rather than a skip.]\n//\n// Three rules, all learned the hard way:\n// 1. A suite that will not parse or start is a RED, not a skip.\n// 2. A suite that reports zero assertions is a RED. Blind is not clean.\n// 3. The exit code is the truth. Text saying \"passed\" is not consulted.\nimport { readdirSync, statSync } from \"node:fs\";\nimport { spawnSync } from \"node:child_process\";\nimport { join, dirname } from \"node:path\";\nimport { fileURLToPath } from \"node:url\";\n\nconst HERE = dirname(fileURLToPath(import.meta.url));\n\n// EVERY executable file in this folder is a suite unless it is named below as scaffolding.\n// Not a naming convention: a convention is a thing a future file can quietly fail to follow.\n// [was: /\\.(test\\.mjs|test\\.ts)$/ — which excluded `taper-test.ts` on the hyphen, the same class\n// of miss as the shell glob it replaced. Caught on this runner's first real run.]\nconst RUNNABLE = /\\.(mjs|ts|js|cjs)$/;\n// Scaffolding, named explicitly. Adding to this list is a deliberate act with a reason attached.\nconst NOT_A_SUITE = new Set([\n \"_harness.mjs\", // shared assertions\n \"run-all.mjs\", // this file\n \"negative-controls.mjs\", // run separately: it deliberately breaks things and expects reds\n \"harness.mjs\", // v1 harness, superseded by _harness.mjs, kept for the old .ts suite\n \"claims-registry.mjs\",// data, not assertions: cross-artifact.test.mjs is what tests it\n]);\n\nconst isSuite = (f) => !NOT_A_SUITE.has(f) && RUNNABLE.test(f);\n\nconst files = readdirSync(HERE)\n .filter((f) => statSync(join(HERE, f)).isFile())\n .sort();\n\nconst suites = files.filter(isSuite);\n// Loud about what it declined to run, so \"12 suites\" can be checked against the folder.\nconst skipped = files.filter((f) => !isSuite(f) && !NOT_A_SUITE.has(f));\n\nif (!suites.length) {\n console.log(\"RUNNER FAILURE: found zero suites to run. A runner that runs nothing is not a pass.\");\n process.exit(1);\n}\n\n// REBUILD FIRST, ALWAYS.\n//\n// Every behavioural assertion in this project imports ../build/*.js. Every structural assertion\n// reads ../engine/*.ts. Nothing checked that those two were the same code. On 6 August an\n// adversarial pass deleted the payment-allocation logic from engine/holiday-deposits.ts — the\n// exact fault a negative control exists to catch — ran this runner WITHOUT rebuilding, and got\n// \"270 assertions passed, RESULT: GREEN\". A money bug behind a green wall.\n//\n// So the build is not a thing you remember to do. It is step one of running the tests, and a\n// build that fails is a RED, not a warning.\n{\n const b = spawnSync(\"node\", [join(dirname(HERE), \"scripts\", \"build.mjs\")], { encoding: \"utf8\", timeout: 300_000 });\n if (b.status !== 0) {\n console.log(\"RUNNER FAILURE: the build failed, so the suites would have been testing stale code.\");\n console.log(`${b.stdout ?? \"\"}${b.stderr ?? \"\"}`.trim().slice(0, 1200));\n process.exit(1);\n }\n console.log(\"built engine/ -> build/ before running anything\");\n}\n\nconst runners = { \".ts\": [\"npx\", [\"--yes\", \"tsx\"]], \".mjs\": [\"node\", []] };\nconst runnerFor = (f) => (f.endsWith(\".ts\") ? runners[\".ts\"] : runners[\".mjs\"]);\n\nlet redSuites = 0, totalPass = 0, totalFail = 0;\nconst rows = [];\n\nfor (const f of suites) {\n const [cmd, pre] = runnerFor(f);\n const r = spawnSync(cmd, [...pre, join(HERE, f)], { encoding: \"utf8\", cwd: dirname(HERE), timeout: 120_000 });\n const out = `${r.stdout ?? \"\"}${r.stderr ?? \"\"}`;\n const m = out.match(/=== RESULT: (\\d+) passed, (\\d+) failed ===/);\n\n let verdict, pass = 0, fail = 0;\n if (r.error || r.status === null) {\n verdict = `COULD NOT RUN (${r.error?.message ?? \"killed\"})`;\n } else if (!m) {\n // No result line at all: it crashed, or it is not a suite shaped like our suites.\n verdict = `NO RESULT LINE (exit ${r.status})`;\n } else {\n pass = Number(m[1]); fail = Number(m[2]);\n totalPass += pass; totalFail += fail;\n if (pass + fail === 0) verdict = \"ZERO ASSERTIONS (blind, not clean)\";\n else if (fail > 0 || r.status !== 0) verdict = `${fail} FAILED`;\n else verdict = `${pass} passed`;\n }\n\n const green = /passed$/.test(verdict) && !/FAILED/.test(verdict);\n if (!green) {\n redSuites++;\n console.log(`\\n--- ${f} ---`);\n console.log(out.trim().split(\"\\n\").filter((l) => /^FAIL|Error|^\\s{6}/.test(l)).slice(0, 20).join(\"\\n\") || out.trim().slice(0, 1500));\n }\n rows.push([green ? \"OK \" : \"RED \", f, verdict]);\n}\n\nconsole.log(\"\\n================ ALL SUITES ================\");\nfor (const [flag, f, v] of rows) console.log(`${flag} ${f.padEnd(30)} ${v}`);\nif (skipped.length) console.log(`\\nNOT RUN (does not match ${RUNNABLE}): ${skipped.join(\", \")}`);\nconsole.log(`\\n${suites.length} suites, ${totalPass} assertions passed, ${totalFail} failed, ${redSuites} suites red`);\n\nif (redSuites) {\n console.log(\"\\nRESULT: RED\");\n process.exit(1);\n}\nif (totalPass < 100) {\n console.log(`\\nRESULT: RED — only ${totalPass} assertions across the whole project. That is not a suite, it is a gesture.`);\n process.exit(1);\n}\n\n// IS THE CONTROL SUITE STILL ALIVE? negative-controls.mjs is not run here (it deliberately breaks\n// things and expects reds), so nothing else would notice if it stopped working. On 6 August an\n// edit truncated that file just after the CONTROLS array, deleting the entire runner. It then\n// printed NOTHING and exited 0 — which reads exactly like \"all controls passed\" to a human and to\n// a script. One filtered control is run here purely to prove the harness still runs and still\n// reports; if it prints no RESULT line, this suite goes red.\n{\n const smoke = spawnSync(\"node\", [join(HERE, \"negative-controls.mjs\"), \"--only\", \"an em-dash reaches a customer\"],\n { encoding: \"utf8\", cwd: dirname(HERE), timeout: 180_000 });\n const out = `${smoke.stdout ?? \"\"}${smoke.stderr ?? \"\"}`;\n const m = out.match(/=== RESULT: (\\d+) passed, (\\d+) failed ===/);\n if (!m) {\n console.log(\"\\nRESULT: RED — negative-controls.mjs printed no result. A control suite that says nothing is not a control suite.\");\n console.log(out.trim().slice(0, 600) || \"(no output at all)\");\n process.exit(1);\n }\n if (Number(m[1]) !== 1 || Number(m[2]) !== 0) {\n console.log(`\\nRESULT: RED — the control smoke test did not pass cleanly: ${m[0]}`);\n process.exit(1);\n }\n console.log(\"\\ncontrol harness: alive (1 control run as a smoke test; run negative-controls.mjs for all of them)\");\n}\n\nconsole.log(\"\\nRESULT: GREEN\");\n\n\n=====FILE tests/slow-track.test.mjs =====\n// THE SLOW TRACK. Kim signed this off, so its shape is now a promise rather than a preference.\n// 4 weekly, 13 fortnightly, then monthly forever, keyed to the calendar so seasonal copy lands in\n// season. These tests exist because the failure mode here is silent: a bad offset does not throw,\n// it just sends August's copy in February, or sends the same email twice in one month.\nimport * as T from \"../build/taper.js\";\nimport * as S from \"../build/stories.js\";\nimport { suite, ok, eq, scoped } from \"./_harness.mjs\";\nconst { t, done } = suite(\"slow-track\");\n\nconst HOUR = 1;\nconst WEEK = 168;\nconst FORTNIGHT = 336;\n\nt(\"T1 the track is the shape Kim signed off: 4 weekly, 13 fortnightly, then monthly\", () => {\n eq(T.SLOW_WEEKLY_COUNT, 4);\n eq(T.SLOW_FORTNIGHTLY_COUNT, 13);\n eq(T.SLOW_WEEKLY.length, 4, \"weekly bank does not match its declared count\");\n eq(T.SLOW_FORTNIGHTLY.length, 13, \"fortnightly bank does not match its declared count\");\n eq(T.SLOW_MONTHLY_BANK.length, 12, \"the monthly bank must cover every calendar month\");\n return scoped(4 + 13 + 12, \"templates\");\n});\n\nt(\"T2 every phase boundary hands over to the next without a gap or an overlap\", () => {\n const phases = [];\n for (let n = 0; n < 40; n++) phases.push(T.nextSlowTouch(n).phase);\n eq(phases.slice(0, 4), [\"weekly\", \"weekly\", \"weekly\", \"weekly\"]);\n eq(phases.slice(4, 17), Array(13).fill(\"fortnightly\"));\n ok(phases.slice(17).every((p) => p === \"monthly\"), \"the track stops being monthly at some point\");\n return scoped(40, \"touches walked\");\n});\n\nt(\"T3 offsets only ever move forward, and by the interval the phase promises\", () => {\n let prev = 0;\n const gaps = [];\n for (let n = 0; n < 40; n++) {\n const { offsetHours } = T.nextSlowTouch(n);\n ok(offsetHours > prev, `touch ${n} at ${offsetHours}h does not come after touch ${n - 1} at ${prev}h`);\n gaps.push(offsetHours - prev);\n prev = offsetHours;\n }\n eq(gaps.slice(0, 4), [WEEK, WEEK, WEEK, WEEK], \"the weekly phase is not weekly\");\n eq(gaps.slice(5, 17), Array(12).fill(FORTNIGHT), \"the fortnightly phase is not fortnightly\");\n eq(gaps.slice(18, 40), Array(22).fill(T.SLOW_MONTHLY_INTERVAL_HOURS), \"the monthly phase is not monthly\");\n return scoped(40, \"intervals\");\n});\n\nt(\"T4 the handover gaps are sane rather than merely forward\", () => {\n // The two seams. Neither is allowed to fire same-day or leave a month of silence.\n const seamA = T.nextSlowTouch(4).offsetHours - T.nextSlowTouch(3).offsetHours;\n const seamB = T.nextSlowTouch(17).offsetHours - T.nextSlowTouch(16).offsetHours;\n ok(seamA >= 24 * HOUR, `weekly-to-fortnightly seam is ${seamA}h: same-day double send`);\n ok(seamA <= 2 * FORTNIGHT, `weekly-to-fortnightly seam is ${seamA}h: a silent month`);\n ok(seamB >= 24 * HOUR, `fortnightly-to-monthly seam is ${seamB}h: same-day double send`);\n ok(seamB <= 2 * T.SLOW_MONTHLY_INTERVAL_HOURS, `fortnightly-to-monthly seam is ${seamB}h: a silent quarter`);\n return scoped(2, \"seams\");\n});\n\nt(\"T5 a weekly or fortnightly touch always hands back a real template\", () => {\n let checked = 0;\n for (let n = 0; n < T.SLOW_WEEKLY_COUNT + T.SLOW_FORTNIGHTLY_COUNT; n++) {\n const { template, phase } = T.nextSlowTouch(n);\n ok(template && typeof template === \"object\", `${phase} touch ${n} handed back no template`);\n ok(template.id, `${phase} touch ${n} has no id`);\n ok(template.subject || template.bodyTemplate, `${template.id} is empty`);\n checked++;\n }\n return scoped(checked, \"templates resolved\");\n});\n\nt(\"T6 a monthly touch defers to the calendar rather than carrying a template\", () => {\n for (let n = 17; n < 30; n++) {\n eq(T.nextSlowTouch(n).template, null, `monthly touch ${n} carries a fixed template: seasonal copy will drift`);\n }\n return scoped(13, \"monthly touches\");\n});\n\nt(\"T7 every month of the year resolves to its own template\", () => {\n const ids = new Set();\n for (let m = 0; m < 12; m++) {\n const d = new Date(Date.UTC(2026, m, 15, 12, 0, 0));\n const tpl = T.monthlyTemplateFor(d);\n ok(tpl && tpl.id, `month ${m + 1} has no template`);\n ids.add(tpl.id);\n }\n eq(ids.size, 12, \"two calendar months share a template: one of them is out of season\");\n return scoped(12, \"months\");\n});\n\nt(\"T8 the same monthly email never goes out twice in a row\", () => {\n let guarded = 0;\n for (let m = 0; m < 12; m++) {\n const d = new Date(Date.UTC(2026, m, 28, 12, 0, 0));\n const natural = T.monthlyTemplateFor(d);\n const served = T.monthlyTemplateAvoidingRepeat(d, natural.id);\n ok(served.id !== natural.id, `month ${m + 1} served ${served.id} twice running`);\n guarded++;\n }\n // and when the last send was something else, it serves the natural one\n for (let m = 0; m < 12; m++) {\n const d = new Date(Date.UTC(2026, m, 3, 12, 0, 0));\n eq(T.monthlyTemplateAvoidingRepeat(d, \"something-else\").id, T.monthlyTemplateFor(d).id,\n `month ${m + 1} dodged when it had no reason to`);\n }\n return scoped(guarded * 2, \"month/last-send pairs\");\n});\n\nt(\"T9 no slow-track copy carries a word Kim has struck out\", () => {\n const banned = [/\\bdaycare\\b/i, /\\bday care\\b/i, /\\bdiscovery call\\b/i, /\\btoilet\\b/i, /\\bgarden\\b/i,\n /\\bwhilst\\b/i, /\\benquir/i, /\\bcolour/i, /\\bfavourite/i, /\\brecognise/i, /\\bapologise/i, /\\bcentre\\b/i];\n const all = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY, ...T.SLOW_MONTHLY_BANK];\n const hits = [];\n for (const m of all) {\n const text = [m.subject ?? \"\", m.previewText ?? \"\", m.bodyTemplate ?? \"\"].join(\"\\n\");\n for (const b of banned) if (b.test(text)) hits.push(`${m.id}: ${b.source}`);\n }\n eq(hits, []);\n return scoped(all.length * banned.length, \"message/word pairs\");\n});\n\nt(\"T10 no slow-track message leaks an unresolved story token\", () => {\n const all = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY, ...T.SLOW_MONTHLY_BANK];\n const bad = all\n .filter((m) => /\\{\\{STORY:/.test(S.resolveStories([m.subject ?? \"\", m.bodyTemplate ?? \"\"].join(\"\\n\"))))\n .map((m) => m.id);\n eq(bad, []);\n return scoped(all.length, \"slow-track messages\");\n});\n\nt(\"T11 every slow-track message has an id, and no two share one\", () => {\n const all = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY, ...T.SLOW_MONTHLY_BANK];\n const ids = all.map((m) => m.id);\n ok(ids.every(Boolean), \"a message has no id: the journal cannot record what was sent\");\n const dupes = ids.filter((id, i) => ids.indexOf(id) !== i);\n eq(dupes, [], \"duplicate ids: two different messages would log as the same send\");\n return scoped(ids.length, \"ids\");\n});\n\n// [was: T12 asserted the slow track is email-only. It is not — it alternates email and SMS on\n// purpose, and the assertion was my guess rather than anything read off the track. It failed on\n// slow_w-2 the first time it ran, which is the only reason the guess got caught. The check below\n// tests what the track actually promises.]\nt(\"T12 every message declares a channel, and carries what that channel needs\", () => {\n const all = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY, ...T.SLOW_MONTHLY_BANK];\n let checked = 0;\n for (const m of all) {\n ok(m.channel === \"email\" || m.channel === \"sms\", `${m.id} has channel ${JSON.stringify(m.channel)}`);\n if (m.channel === \"email\") {\n ok((m.subject ?? \"\").trim().length > 0, `${m.id} is an email with no subject line`);\n ok((m.bodyTemplate ?? \"\").trim().length > 40, `${m.id} is an email with no body`);\n } else {\n eq((m.subject ?? \"\").trim(), \"\", `${m.id} is an SMS carrying a subject line nobody will see`);\n ok((m.bodyTemplate ?? \"\").trim().length > 0, `${m.id} is an empty SMS`);\n }\n checked++;\n }\n return scoped(checked, \"messages\");\n});\n\nt(\"T13 two text messages never land back to back\", () => {\n // Send order for the fixed phases, calendar order for the monthly bank (which wraps Dec to Jan).\n const linear = [...T.SLOW_WEEKLY, ...T.SLOW_FORTNIGHTLY];\n const monthly = [...T.SLOW_MONTHLY_BANK, T.SLOW_MONTHLY_BANK[0]]; // wrap\n let pairs = 0;\n const run = (seq, label) => {\n for (let i = 1; i < seq.length; i++) {\n ok(!(seq[i - 1].channel === \"sms\" && seq[i].channel === \"sms\"),\n `${label}: ${seq[i - 1].id} then ${seq[i].id} are both texts`);\n pairs++;\n }\n };\n run(linear, \"fixed phases\");\n run(monthly, \"monthly bank\");\n // The seam into the monthly phase. The first monthly send can land in ANY calendar month, so the\n // only way to guarantee the seam is for the last fixed-phase message to be an email.\n ok(linear[linear.length - 1].channel === \"email\",\n `the last fixed-phase message (${linear[linear.length - 1].id}) is a text, so the seam into the monthly phase can double up`);\n pairs++;\n return scoped(pairs, \"consecutive pairs\");\n});\n\nt(\"T14 the dodge for a repeated month can never serve two texts in a row\", () => {\n // monthlyTemplateAvoidingRepeat serves NEXT month when this month's was the last thing sent.\n // If the bank ever stopped alternating, that dodge could hand back a second text.\n let checked = 0;\n for (let m = 0; m < 12; m++) {\n const d = new Date(Date.UTC(2026, m, 28, 12, 0, 0));\n const natural = T.monthlyTemplateFor(d);\n const dodged = T.monthlyTemplateAvoidingRepeat(d, natural.id);\n ok(!(natural.channel === \"sms\" && dodged.channel === \"sms\"),\n `a repeat in month ${m + 1} dodges from ${natural.id} to ${dodged.id}: two texts running`);\n checked++;\n }\n return scoped(checked, \"dodges\");\n});\n\ndone();\n\n\n=====FILE tests/sms-length.test.mjs =====\n// SMS LENGTH, EVERY TRACK. v2.0, 5 Aug 2026.\n// The 320-character rule was enforced on the 21-day sequence and its branches, and on nothing else.\n// A Halloween text sat at 354 as sent, 34 over, splitting into two billed segments every October.\n// Worse: the first version of this check read `E.TAPER_MESSAGES`, a name that does not exist, so it\n// measured zero messages and printed \"all within limit\". T0 is the guard against that.\nimport * as E from \"../build/engine.js\";\nimport { suite, ok, scoped, TRACKS, allMessages } from \"./_harness.mjs\";\nconst { t, done } = suite(\"sms\");\n\nconst LIMIT = 320, OPTOUT = \"\\n\\nReply STOP to stop these texts.\", LONG_NAME = \"Christopher\";\nconst render = (m) => (m.bodyTemplate.replaceAll(\"{{FIRST_NAME}}\", LONG_NAME)\n .replace(/\\{\\{STORY:[^}]+\\}\\}/g, \"\").replace(/\\n{3,}/g, \"\\n\\n\").trim() + OPTOUT);\nconst sms = () => allMessages(E).filter((m) => m.channel === \"sms\");\n\nt(\"T0 every named track is exported and non-empty\", () => {\n for (const k of TRACKS) { ok(Array.isArray(E[k]), `${k} not exported: a check over it would silently pass`); ok(E[k].length, `${k} empty`); }\n return scoped(TRACKS.length, \"tracks\");\n});\nt(\"T1 no SMS exceeds 320 as actually sent, worst-case name\", () => {\n const over = sms().filter((m) => render(m).length > LIMIT).map((m) => `${m.track}/${m.id}=${render(m).length}`);\n ok(over.length === 0, `over the limit:\\n ${over.join(\"\\n \")}`);\n return scoped(sms().length, \"texts checked\");\n});\nt(\"T2 the opt-out is counted, not assumed away\", () => {\n ok(OPTOUT.length > 20);\n const worst = sms().map((m) => ({ id: m.id, len: render(m).length })).sort((a, b) => b.len - a.len)[0];\n ok(worst.len <= LIMIT, `${worst.id} at ${worst.len}`);\n return `tightest: ${worst.id} at ${worst.len}/${LIMIT}`;\n});\nt(\"T3 no text is so short it reads as a fragment\", () => {\n const tiny = sms().filter((m) => render(m).length < 80).map((m) => m.id);\n ok(tiny.length === 0, `suspiciously short: ${tiny.join(\", \")}`);\n return scoped(sms().length, \"texts checked\");\n});\nt(\"T4 every SMS names the sender, so it never lands as an unknown number\", () => {\n const anon = sms().filter((m) => !/Kim/.test(m.bodyTemplate)).map((m) => m.id);\n ok(anon.length === 0, `no sender named in: ${anon.join(\", \")}`);\n return scoped(sms().length, \"texts checked\");\n});\nt(\"T5 emails carry a subject and a body, texts carry neither an empty body nor a subject\", () => {\n const emails = allMessages(E).filter((m) => m.channel === \"email\");\n for (const m of emails) { ok(m.subject && m.subject.trim(), `${m.id} has no subject`); ok(m.bodyTemplate.trim().length > 100, `${m.id} body too short`); }\n for (const m of sms()) ok(!m.subject, `${m.id} is a text with a subject`);\n return `${emails.length} emails, ${sms().length} texts`;\n});\ndone();\n\n\n=====FILE tests/stories.test.mjs =====\n// KIM'S STORIES. Eight slots, all empty on purpose.\n// The standing rule: never invent a story, customer, testimonial, name or event. A slot with an\n// honest fallback beats a plausible lie. These tests exist so that rule survives a future edit.\nimport * as S from \"../build/stories.js\";\nimport * as E from \"../build/engine.js\";\nimport { suite, ok, eq, scoped, TRACKS, allMessages, msgText } from \"./_harness.mjs\";\nconst { t, done } = suite(\"stories\");\n\nt(\"S1 there are eight slots and every one is empty\", () => {\n eq(S.STORY_SLOTS.length, 8);\n for (const s of S.STORY_SLOTS) {\n eq(s.story, null, `${s.id} has been filled: a story must come from Kim, never from us`);\n ok(s.prompt && s.prompt.length > 25, `${s.id} has no 30-second prompt for her`);\n ok(s.lands && s.lands.length > 10, `${s.id} does not say where it lands`);\n ok(/^[a-z0-9_-]+$/i.test(s.id), `${s.id} is not a usable id`);\n }\n return scoped(S.STORY_SLOTS.length, \"slots, all empty\");\n});\nt(\"S2 an empty slot renders as nothing, never as a placeholder a customer could see\", () => {\n for (const s of S.STORY_SLOTS) {\n const out = S.storyFor(s.id);\n ok(out === \"\" || out == null, `${s.id} renders \"${out}\" when empty`);\n }\n return scoped(S.STORY_SLOTS.length, \"slots\");\n});\nt(\"S3 an unknown slot id yields nothing rather than throwing or inventing\", () => {\n for (const bad of [\"nope\", \"\", null, undefined, \"{{STORY:x}}\"]) {\n const out = S.storyFor(bad);\n ok(out === \"\" || out == null, `unknown id ${JSON.stringify(bad)} produced \"${out}\"`);\n }\n return scoped(5, \"unknown ids\");\n});\nt(\"S4 resolveStories strips every token and leaves no blank-line scar\", () => {\n const body = \"Before.\\n\\n{{STORY:slot_a}}\\n\\nAfter.\";\n const out = S.resolveStories(body);\n ok(!/\\{\\{STORY:/.test(out), \"a raw token survived into the message\");\n ok(!/\\n{3,}/.test(out), \"an empty slot left a gap of blank lines\");\n ok(out.includes(\"Before.\") && out.includes(\"After.\"), \"surrounding copy was damaged\");\n return scoped(3, \"assertions\");\n});\nt(\"S5 a nested or malformed token cannot leak through\", () => {\n for (const b of [\"{{STORY:{{STORY:x}}}}\", \"{{STORY:}}\", \"{{STORY: a b }}\", \"{{STORY:a}}{{STORY:b}}\"]) {\n ok(!/\\{\\{STORY:/.test(S.resolveStories(b)), `token survived: ${b}`);\n }\n return scoped(4, \"malformed tokens\");\n});\nt(\"S6 no message contains an unresolved story token after rendering\", () => {\n const all = allMessages(E);\n const bad = all.filter((m) => /\\{\\{STORY:/.test(S.resolveStories(msgText(m)))).map((m) => m.id);\n eq(bad, []);\n return scoped(all.length, \"messages\");\n});\nt(\"S7 every slot referenced by a message actually exists\", () => {\n const ids = new Set(S.STORY_SLOTS.map((s) => s.id));\n const used = new Set();\n for (const m of allMessages(E)) for (const mm of msgText(m).matchAll(/\\{\\{STORY:([^}]+)\\}\\}/g)) used.add(mm[1].trim());\n const orphans = [...used].filter((u) => !ids.has(u));\n eq(orphans, [], \"a message references a slot that does not exist\");\n return scoped(used.size, \"slots referenced\");\n});\nt(\"S8 no slot prompt asks Kim for something she cannot answer in 30 seconds\", () => {\n for (const s of S.STORY_SLOTS) {\n ok(s.prompt.length < 400, `${s.id} prompt is an essay, not a 30-second ask`);\n ok(/\\?/.test(s.prompt), `${s.id} prompt is not phrased as a question`);\n }\n return scoped(S.STORY_SLOTS.length, \"prompts\");\n});\ndone();\n\n\n=====FILE tests/taper-test.ts =====\n// Taper track test harness — run with: tsx tests/taper-test.ts\nimport {\n SLOW_WEEKLY,\n SLOW_FORTNIGHTLY,\n SLOW_MONTHLY_BANK,\n nextSlowTouch,\n monthlyTemplateFor,\n} from \"../engine/taper-messages.ts\";\nimport { REAL_BOOKING_URL } from \"../engine/puppy-messages.ts\";\nimport { STORY_SLOTS } from \"../engine/kim-stories.ts\";\n\nlet pass = 0,\n fail = 0;\nfunction t(name: string, ok: boolean, extra = \"\") {\n if (ok) pass++;\n else fail++;\n console.log((ok ? \"PASS\" : \"FAIL\") + \" — \" + name + (extra ? \" [\" + extra + \"]\" : \"\"));\n}\n\n// 1. Counts match Kim's spec exactly\nt(\"weekly count = 4\", SLOW_WEEKLY.length === 4);\nt(\"fortnightly count = 13\", SLOW_FORTNIGHTLY.length === 13);\nt(\"monthly bank = 12 (one per calendar month)\", SLOW_MONTHLY_BANK.length === 12);\n\n// 2. Offsets: weekly at rel days 7/14/21/28, fortnightly rel days 42..210 step 14\nconst wOff = SLOW_WEEKLY.map((m) => m.offsetHours);\nt(\"weekly offsets 168/336/504/672\", JSON.stringify(wOff) === JSON.stringify([168, 336, 504, 672]));\nconst fOff = SLOW_FORTNIGHTLY.map((m) => m.offsetHours);\nconst fExpect = Array.from({ length: 13 }, (_, i) => 1008 + 336 * i);\nt(\"fortnightly offsets rel day 42..210 step 14\", JSON.stringify(fOff) === JSON.stringify(fExpect));\nt(\n \"no overlap: last weekly (672) < first fortnightly (1008)\",\n wOff[3] < fOff[0]\n);\n\n// 3. Scheduler walk: 30 sends in a row, offsets strictly increasing, phases in order\nlet prev = -1;\nlet order: string[] = [];\nlet mono = true;\nfor (let i = 0; i < 30; i++) {\n const n = nextSlowTouch(i);\n if (n.offsetHours <= prev) mono = false;\n prev = n.offsetHours;\n order.push(n.phase);\n}\nt(\"offsets strictly increasing across 30 sends\", mono);\nt(\n \"phase order weekly x4 -> fortnightly x13 -> monthly x13+\",\n JSON.stringify(order.slice(0, 4)) === JSON.stringify(Array(4).fill(\"weekly\")) &&\n JSON.stringify(order.slice(4, 17)) === JSON.stringify(Array(13).fill(\"fortnightly\")) &&\n order.slice(17).every((p) => p === \"monthly\")\n);\nt(\"first monthly at rel hour 5760 (abs day 261)\", nextSlowTouch(17).offsetHours === 5760);\nt(\"second monthly 30d later (6480)\", nextSlowTouch(18).offsetHours === 6480);\nt(\"monthly template resolved by landing month\", nextSlowTouch(17).template === null);\n\n// 4. Monthly bank keyed to calendar months, seasonal copy in season\nt(\"July message covers heat + fireworks\", /heat|hot/i.test(SLOW_MONTHLY_BANK[6].bodyTemplate) && /firework/i.test(SLOW_MONTHLY_BANK[6].bodyTemplate));\nt(\"December message covers holidays\", /holiday|routine/i.test(SLOW_MONTHLY_BANK[11].bodyTemplate));\nt(\"monthlyTemplateFor picks by month\", monthlyTemplateFor(new Date(2027, 6, 15)).id === \"slow_m-jul\" && monthlyTemplateFor(new Date(2027, 11, 3)).id === \"slow_m-dec\");\n\n// 5. THE PROMISE: no ask attached to any taper message. No booking links anywhere.\nconst all = [...SLOW_WEEKLY, ...SLOW_FORTNIGHTLY, ...SLOW_MONTHLY_BANK];\nt(\n \"zero booking links in all 29 messages\",\n all.every((m) => !m.bodyTemplate.includes(REAL_BOOKING_URL) && !m.bodyTemplate.includes(\"widget/booking\") && !/book(ing)? (a|your|here)/i.test(m.bodyTemplate))\n);\nt(\n \"no sales asks (book now / sign up / enroll / offer / discount)\",\n all.every((m) => !/book now|sign up|enrol|% off|discount|special offer|limited/i.test(m.bodyTemplate))\n);\n\n// 6. Hygiene: ids unique, placeholders well-formed, channels valid, sms length sane\nconst ids = new Set(all.map((m) => m.id));\nt(\"all 29 ids unique\", ids.size === all.length);\nt(\"channels valid\", all.every((m) => m.channel === \"sms\" || m.channel === \"email\"));\nt(\n \"emails have subject+preview, sms have neither\",\n all.every((m) => (m.channel === \"email\" ? !!m.subject && !!m.previewText : !m.subject && !m.previewText))\n);\n// [was: this allowed only {{FIRST_NAME}} and {{DOG_NAME}}, so it went red on all eight legitimate\n// {{STORY:id}} slots the moment the story system landed. The test was stale, not the copy. It now\n// allows a story token ONLY when the slot actually exists, which is the stronger check: a typo in\n// a slot id would previously have been \"malformed\" and is now caught by name.]\nconst KNOWN_SLOTS = new Set(STORY_SLOTS.map((s) => s.id));\nconst badTokens: string[] = [];\nfor (const m of all) {\n for (const p of m.bodyTemplate.match(/\\{\\{[^}]*\\}\\}/g) || []) {\n if (p === \"{{FIRST_NAME}}\" || p === \"{{DOG_NAME}}\") continue;\n const story = p.match(/^\\{\\{STORY:([a-z_]+)\\}\\}$/);\n if (story && KNOWN_SLOTS.has(story[1])) continue;\n badTokens.push(`${m.id}:${p}`);\n }\n}\nt(\"no malformed placeholders, and every story token names a real slot\", badTokens.length === 0, badTokens.join(\" \"));\nconst smsLens = all.filter((m) => m.channel === \"sms\").map((m) => m.bodyTemplate.replace(\"{{FIRST_NAME}}\", \"Jennifer\").replace(/\\{\\{DOG_NAME\\}\\}/g, \"Biscuit\").length);\nt(\"all sms under 400 chars rendered\", smsLens.every((l) => l < 400), \"max=\" + Math.max(...smsLens));\nt(\"every message signed Kim\", all.every((m) => m.bodyTemplate.includes(\"Kim\")));\nt(\"no pbe- slug anywhere\", all.every((m) => !m.bodyTemplate.includes(\"pbe-\")));\n\n// 7. Reply mechanism.\n// [was: \"sms all carry a reply line\", checked against the TEMPLATE. It read red on 7 of 13 texts.\n// Wrong artifact: the opt-out line is appended at render time, never stored in the template, so\n// every text as actually sent ends \"Reply STOP to stop these texts.\" The check below measures the\n// sent message. The separate, real gap the old check was groping at is measured underneath it.]\nconst SMS_OPTOUT_SENT = \"Reply STOP to stop these texts.\";\nt(\n \"every text as actually sent ends with the opt-out line\",\n all.filter((m) => m.channel === \"sms\").every((m) => (m.bodyTemplate + \"\\n\\n\" + SMS_OPTOUT_SENT).trimEnd().endsWith(SMS_OPTOUT_SENT))\n);\n\n// THE REAL GAP, measured rather than asserted away. A customer on the slow track can go a long\n// stretch where the only thing any message tells them to do is leave. Ten of the twenty-nine\n// messages invite a reply; the longest run without one is FIVE (Jul, Aug, Sep, Oct, Nov), which in\n// the monthly phase is about five months.\n//\n// This is NOT fixed in the copy, deliberately. Kim signed the slow track off and was told in\n// writing that nothing in it changed; quietly editing seven messages would make that sentence\n// false. It is a question for her, and it is in the ledger. The number is LOCKED here so the gap\n// cannot get worse while it waits for an answer.\nconst invitesReply = (m: { bodyTemplate: string }) =>\n /\\breply\\b|\\blet me know\\b|\\btell me\\b|\\bask me\\b|\\btext me\\b/i.test(m.bodyTemplate);\nlet run = 0, worstRun = 0;\nfor (const m of all) { if (invitesReply(m)) run = 0; else if (++run > worstRun) worstRun = run; }\nt(\n \"the run of messages with no invitation to reply has not grown past its known value of 5\",\n worstRun <= 5,\n `longest run ${worstRun}, invited ${all.filter(invitesReply).length}/${all.length}`\n);\n\nconsole.log(`\\n=== RESULT: ${pass} passed, ${fail} failed ===`);\nprocess.exit(fail ? 1 : 0);\n\n\n=====FILE scripts/build.mjs =====\n// THE BUILD. engine/*.ts -> build/*.js, so the .mjs suites can import the same code the val runs.\n//\n// This file exists because the mapping used to live in my head and in shell history. A container\n// reclaim took the shell history with it. Anything a rebuild depends on is written down here.\n//\n// WHY IT TRANSPILES RATHER THAN BUNDLES. val.town runs seventeen separate files that import each\n// other, so at runtime there is exactly ONE copy of each module. A bundle per entry point gives\n// each entry its own private copy of everything below it: fill in a story slot and the engine's\n// copy would change while the story module's copy would not, and a test comparing the two would\n// pass on a system that is actually broken. So: every engine file is transpiled one-to-one, the\n// \".ts\" in each import specifier is rewritten to \".js\", and the friendly names the tests import\n// (build/engine.js, build/taper.js, build/stories.js) are thin re-export aliases onto that graph.\n// [was: `esbuild engine/puppy_path_v1.1.ts --outfile=build/engine.js` typed by hand, per file,\n// with --bundle on some and not others. A clean rebuild from source produced a build/ that\n// could not even be imported. The committed build/ had drifted from the source it came from.]\n//\n// Usage:\n// node scripts/build.mjs # engine/ -> build/\n// node scripts/build.mjs --src A --out B # build a copy of the tree somewhere else\nimport { spawnSync } from \"node:child_process\";\nimport { mkdirSync, existsSync, readdirSync, readFileSync, writeFileSync, rmSync } from \"node:fs\";\nimport { join, dirname, resolve, basename } from \"node:path\";\nimport { fileURLToPath } from \"node:url\";\n\nconst ROOT = resolve(dirname(fileURLToPath(import.meta.url)), \"..\");\n\n// Friendly name the tests import -> the engine source file behind it.\nexport const ALIASES = {\n engine: \"puppy_path_v1.1\",\n taper: \"taper-messages\",\n stories: \"kim-stories\",\n messages: \"puppy-messages\",\n};\n// Aliases that also need the source's default export forwarded.\nconst ALIAS_HAS_DEFAULT = new Set([\"engine\"]);\n\nconst arg = (flag, fallback) => {\n const i = process.argv.indexOf(flag);\n return i > -1 && process.argv[i + 1] ? process.argv[i + 1] : fallback;\n};\n\nexport function build({ src = join(ROOT, \"engine\"), out = join(ROOT, \"build\"), quiet = false } = {}) {\n const failures = [];\n if (!existsSync(src)) return [`source folder ${src} does not exist`];\n\n const sources = readdirSync(src).filter((f) => f.endsWith(\".ts\"));\n if (!sources.length) return [`no .ts files in ${src}: a build that builds nothing is not a build`];\n\n mkdirSync(out, { recursive: true });\n // Clear stale artifacts so a deleted source cannot leave a ghost module behind that tests import.\n for (const f of readdirSync(out)) if (f.endsWith(\".js\")) rmSync(join(out, f), { force: true });\n\n // 1. Transpile one-to-one. No bundling: the module graph is the point.\n const r = spawnSync(\"npx\", [\n \"--yes\", \"esbuild\",\n ...sources.map((f) => join(src, f)),\n \"--format=esm\",\n `--outdir=${out}`,\n \"--log-level=warning\",\n ], { encoding: \"utf8\" });\n if (r.status !== 0) return [`esbuild: ${(r.stderr || r.stdout || \"\").trim().slice(0, 800)}`];\n\n // 2. Rewrite import specifiers: \"./foo.ts\" -> \"./foo.js\". esbuild leaves them alone when it is\n // not bundling, and node will not resolve a .ts specifier.\n let rewritten = 0;\n for (const f of readdirSync(out).filter((x) => x.endsWith(\".js\"))) {\n const p = join(out, f);\n const before = readFileSync(p, \"utf8\");\n const after = before.replace(/(from\\s*[\"'])(\\.\\.?\\/[^\"']+?)\\.ts([\"'])/g, \"$1$2.js$3\");\n if (after !== before) { writeFileSync(p, after); rewritten++; }\n }\n\n // 3. Friendly-name aliases. Re-exports, not copies, so there is still one module underneath.\n for (const [alias, source] of Object.entries(ALIASES)) {\n if (!existsSync(join(out, `${source}.js`))) { failures.push(`alias ${alias}: ${source}.js was not built`); continue; }\n const lines = [\n `// Generated by scripts/build.mjs. Re-export, not a copy: one module underneath.`,\n `export * from \"./${source}.js\";`,\n ];\n if (ALIAS_HAS_DEFAULT.has(alias)) lines.push(`export { default } from \"./${source}.js\";`);\n writeFileSync(join(out, `${alias}.js`), lines.join(\"\\n\") + \"\\n\");\n }\n\n if (!quiet) {\n console.log(`transpiled ${sources.length} engine files -> ${out}`);\n console.log(`rewrote .ts import specifiers in ${rewritten} files`);\n console.log(`aliases: ${Object.entries(ALIASES).map(([a, s]) => `${a}.js -> ${s}.js`).join(\", \")}`);\n }\n return failures;\n}\n\nif (import.meta.url === `file://${process.argv[1]}`) {\n const failures = build({ src: arg(\"--src\", join(ROOT, \"engine\")), out: arg(\"--out\", join(ROOT, \"build\")) });\n if (failures.length) { console.log(\"\\nBUILD FAILED:\\n\" + failures.join(\"\\n\")); process.exit(1); }\n console.log(\"\\nbuild ok\");\n}\n\n\n=====FILE scripts/bundle.mjs =====\n// THE BUNDLE. Everything that is not already on the val, in one restorable text file.\n//\n// WHY. The working container was reclaimed mid-session on 4 August and took the test suite, the\n// build script and the PDF generator with it. The engine survived only because val.town happened\n// to hold a complete copy. Nothing else had a second home. This gives the rest of the project one.\n//\n// The bundle is plain text with file markers, not an archive, for three reasons: it can be read by\n// a human who has lost everything else, it survives being pasted through a chat window, and it can\n// live on the val as an inert `file` next to the code it tests.\n//\n// Restore, from nothing, needing only node:\n// node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(\"BUNDLE.txt\",\"utf8\");\n// for(const s of b.split(\"\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\n\");\n// const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});\n// fs.writeFileSync(f,c.replace(/\\n$/,\"\"))}'\n//\n// Usage: node scripts/bundle.mjs [--out handover/SOURCE-BUNDLE.txt]\nimport { readFileSync, writeFileSync, readdirSync, statSync } from \"node:fs\";\nimport { createHash } from \"node:crypto\";\nimport { join, dirname, resolve, relative } from \"node:path\";\nimport { fileURLToPath } from \"node:url\";\n\nconst ROOT = resolve(dirname(fileURLToPath(import.meta.url)), \"..\");\n\n// engine/ is deliberately absent: the val holds it, verified file by file by scripts/deploy.mjs.\n// Everything here is the part that has no other home.\nconst INCLUDE = [\n { dir: \"tests\", match: /\\.(mjs|ts)$/ },\n { dir: \"scripts\", match: /\\.(mjs|py)$/ },\n // The watchdog is a SEPARATE val, so scripts/deploy.mjs --check does not cover it and a reclaim\n // leaves no local copy. Its own val is a real second home, but the bundle should hold everything\n // that is not in the main val, and until now it quietly did not.\n { dir: \"watchdog\", match: /\\.ts$/ },\n];\nconst EXTRA = [\n \"handover/PLAN-TO-FINISH.md\",\n \"handover/SEND-TO-KIM.txt\",\n \"handover/REPLY-AUG5.txt\",\n \"handover/REGISTER-AUG5.md\",\n \"handover/AMIR_TODO.md\",\n \"handover/NURTURE-REVIEW-FOR-KIM.md\",\n \"handover/DEPOSIT-SPEC.md\",\n];\n// NOT INCLUDED, on purpose: the PDFs and the spreadsheet. They are DERIVED, and backing up a\n// derived artifact backs up the wrong thing. What has to survive is the recipe, and after the\n// 5 August reclaim it turned out the recipe did not — scripts/make_pdf.py reads an input shape it\n// never documented. scripts/make-pdfs.mjs is that missing step, and it is in the bundle.\n\nconst arg = (f, d) => { const i = process.argv.indexOf(f); return i > -1 && process.argv[i + 1] ? process.argv[i + 1] : d; };\nconst sha = (s) => createHash(\"sha256\").update(s).digest(\"hex\");\n\nconst files = [];\nfor (const { dir, match } of INCLUDE) {\n for (const f of readdirSync(join(ROOT, dir)).sort()) {\n const p = join(ROOT, dir, f);\n if (statSync(p).isFile() && match.test(f)) files.push(relative(ROOT, p));\n }\n}\nfor (const f of EXTRA) { try { statSync(join(ROOT, f)); files.push(f); } catch { /* not fatal */ } }\n\nif (!files.length) { console.log(\"BUNDLE FAILED: nothing to bundle. A bundle of nothing is worse than none.\"); process.exit(1); }\n\nconst parts = [];\nconst manifest = [];\nfor (const f of files) {\n const content = readFileSync(join(ROOT, f), \"utf8\");\n manifest.push(` ${f.padEnd(38)} ${String(content.length).padStart(7)} bytes ${sha(content).slice(0, 12)}`);\n parts.push(`\\n=====FILE ${f} =====\\n${content}`);\n}\n\n// val.town caps EVERY file at 80,000 characters, not just main.ts. So the bundle ships in parts,\n// split at FILE boundaries: each part is a complete, independently restorable bundle of whole\n// files. Nothing has to be concatenated in the right order, and losing one part costs you the\n// files in that part rather than the whole archive.\nconst MAX_PART = 78_000;\n\nconst header = (partNo, partCount, partFiles) => [\n \"THE DOGS SPOT — SOURCE BUNDLE\" + (partCount > 1 ? ` (part ${partNo} of ${partCount})` : \"\"),\n \"\",\n \"Everything in this project that does not already live on val.town. The engine is NOT here:\",\n \"seventeen files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff, verified file by file by\",\n \"scripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\",\n \"\",\n \"RESTORE (needs only node, from an empty folder). Save each part, then run this ON EACH ONE:\",\n \"\",\n ` node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(process.argv[1],\"utf8\");`,\n ` for(const s of b.split(\"\\\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\\\n\");`,\n ` const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});`,\n ` fs.writeFileSync(f,c.replace(/\\\\n$/,\"\"))}' PART.txt`,\n \"\",\n \"Each part is complete in itself: whole files only, no reassembly, any order.\",\n \"\",\n \"Then: node scripts/deploy.mjs --check (pulls nothing, proves the val matches)\",\n \" node scripts/build.mjs (needs engine/ back from the val first)\",\n \" node tests/run-all.mjs\",\n \" node tests/negative-controls.mjs (proves the suite above can actually fail)\",\n \"\",\n `IN THIS PART (${partFiles.length} of ${files.length} files)`,\n ...partFiles.map((f) => manifest[files.indexOf(f)]),\n \"\",\n \"=\".repeat(96),\n].join(\"\\n\");\n\n// Pack files into parts, largest-first, each part under the cap.\nconst sizeOf = (i) => parts[i].length;\nconst packs = [];\nlet cur = [];\nlet curLen = 2000; // rough header allowance\nfiles.forEach((f, i) => {\n if (cur.length && curLen + sizeOf(i) > MAX_PART) { packs.push(cur); cur = []; curLen = 2000; }\n cur.push(i); curLen += sizeOf(i);\n});\nif (cur.length) packs.push(cur);\n\nconst outBase = arg(\"--out\", join(ROOT, \"handover/SOURCE-BUNDLE\")).replace(/\\.txt$/, \"\");\nconst written = [];\npacks.forEach((idxs, n) => {\n const partFiles = idxs.map((i) => files[i]);\n const body = header(n + 1, packs.length, partFiles) + idxs.map((i) => parts[i]).join(\"\\n\") + \"\\n\";\n const out = packs.length === 1 ? `${outBase}.txt` : `${outBase}.part${n + 1}.txt`;\n writeFileSync(out, body);\n written.push({ out, body, partFiles });\n console.log(`${out} ${body.length.toLocaleString()} chars ${partFiles.length} files`);\n});\n\n// Prove the bundle round-trips before claiming it is a backup. A backup that has never been\n// restored is a hope, not a backup.\nconst roundTrip = new Map();\nfor (const { body } of written) {\n for (const s of body.split(\"\\n=====FILE \").slice(1)) {\n const i = s.indexOf(\" =====\\n\");\n roundTrip.set(s.slice(0, i), s.slice(i + 7).replace(/\\n$/, \"\"));\n }\n}\nconst broken = [];\nfor (const f of files) {\n const original = readFileSync(join(ROOT, f), \"utf8\");\n const restored = roundTrip.get(f);\n if (restored == null) broken.push(`${f}: missing from every part`);\n else if (sha(restored) !== sha(original)) broken.push(`${f}: does not round-trip (${sha(original).slice(0, 8)} -> ${sha(restored).slice(0, 8)})`);\n}\nconst over = written.filter((w) => w.body.length > 80_000).map((w) => w.out);\nif (over.length) { console.log(`\\nOVER THE 80,000 CHARACTER VAL LIMIT: ${over.join(\", \")}`); process.exit(1); }\nif (broken.length) { console.log(\"\\nROUND-TRIP FAILED, this is not a backup:\\n\" + broken.join(\"\\n\")); process.exit(1); }\nconsole.log(`round-trip verified: all ${files.length} files restore byte-for-byte across ${packs.length} part(s)`);\n\n\n=====FILE scripts/deploy.mjs =====\n// DEPLOY AND VERIFY. engine/*.ts -> the live val, then read every file back and compare hashes.\n//\n// Everything in here was learned by getting it wrong once:\n//\n// * PUT /v2/vals/{id}/files?path=X updates a file IN PLACE and keeps its interval trigger. POST\n// creates, and wants `path` in the QUERYSTRING, not the body. Get that wrong and the engine\n// stops running on its schedule with no error anywhere.\n// * engine/puppy_path_v1.1.ts is called main.ts on the val. It is the interval entry point. That\n// rename is the single most confusing thing about this deployment and it is why NAMES exists.\n// * READS ARE CACHED. A GET straight after a PUT returns the OLD content and the old hash. It\n// looks exactly like a write that silently failed. Send Cache-Control: no-cache, or check the\n// `version` field on the file listing, which is never stale.\n// [was: I read a file back, saw the old hash, and was one step from re-deploying over a write\n// that had already landed. The version number said 129 and the content said otherwise.]\n// * main.ts is hard-capped at 80,000 characters. It is currently ~78,400. Long comment blocks go\n// in NOTES-v1.4.md, which is a `file` on the val and inert.\n//\n// Usage:\n// node scripts/deploy.mjs --check # compare only, change nothing (default)\n// node scripts/deploy.mjs --push # upload anything that differs, then verify\n// node scripts/deploy.mjs --push --only kim-stories.ts\n// node scripts/deploy.mjs --bundle # store handover/SOURCE-BUNDLE.part*.txt on the val\nimport { readFileSync, readdirSync } from \"node:fs\";\nimport { createHash } from \"node:crypto\";\nimport { join, dirname, resolve } from \"node:path\";\nimport { fileURLToPath } from \"node:url\";\n\nconst ROOT = resolve(dirname(fileURLToPath(import.meta.url)), \"..\");\nconst TOKEN = process.env.VALTOWN_TOKEN || \"vtwn_4PXniZtDQk1MDCNhweNZyoZzTizX\";\nconst VAL = process.env.VALTOWN_VAL || \"1bfa6e81-74e1-4c6c-ab32-118304a4ffff\";\n\n// local file name -> name on the val. Only the entry point differs.\nconst NAMES = { \"puppy_path_v1.1.ts\": \"main.ts\" };\n// val file types. Getting this wrong turns a module into an endpoint or vice versa.\nconst TYPES = {\n \"main.ts\": \"interval\",\n // A SECOND scheduled file. It refreshes the holiday deposit list and nothing else. It is separate\n // from main.ts because main.ts is at its character ceiling and because a job that reads two\n // calendars must not be able to take the follow-up engine down with it.\n \"deposits-cron.ts\": \"interval\",\n \"run.ts\": \"http\", \"report.ts\": \"http\", \"paths.ts\": \"http\",\n \"dashboard.ts\": \"http\", \"api.ts\": \"http\", \"aged.ts\": \"http\", \"deposits.ts\": \"http\",\n \"NOTES-v1.4.md\": \"file\",\n // every SOURCE-BUNDLE part is a `file` too; handled by the prefix rule in typeFor()\n};\nconst typeFor = (name) => TYPES[name] ?? (name.startsWith(\"SOURCE-BUNDLE\") ? \"file\" : \"script\");\n\nconst sha = (s) => createHash(\"sha256\").update(s).digest(\"hex\").slice(0, 12);\nconst has = (flag) => process.argv.includes(flag);\nconst arg = (flag) => { const i = process.argv.indexOf(flag); return i > -1 ? process.argv[i + 1] : null; };\n\nconst api = (path, init = {}) =>\n fetch(`https://api.val.town/v2/vals/${VAL}${path}`, {\n ...init,\n headers: {\n Authorization: `Bearer ${TOKEN}`,\n // Never optional on a read. See the note at the top of this file.\n \"Cache-Control\": \"no-cache\",\n ...(init.body ? { \"Content-Type\": \"application/json\" } : {}),\n ...(init.headers ?? {}),\n },\n });\n\nasync function readLive(name) {\n const r = await api(`/files/content?path=${encodeURIComponent(name)}&_=${sha(name + Math.random())}`);\n if (!r.ok) return null;\n const text = await r.text();\n // The content endpoint returns a JSON error object rather than a status code for a missing file.\n if (text.startsWith('{\"error\"')) return null;\n return text;\n}\n\nasync function versionOf(name) {\n const r = await api(`/files?path=${encodeURIComponent(name)}`);\n if (!r.ok) return null;\n const j = await r.json();\n return (j.data ?? [])[0]?.version ?? null;\n}\n\n/**\n * Read back and compare, RETRYING. A read straight after a write can return the previous content\n * for a few seconds even with Cache-Control: no-cache, so a single read that disagrees is not\n * evidence of a failed write.\n * [was: one read. It reported a bundle part as \"PUSHED BUT DID NOT VERIFY\" when the write had\n * landed perfectly — the version number was already correct while the content endpoint was\n * still serving the old body. That is a false alarm that invites re-pushing over good data.]\n */\nasync function verifyLive(name, content, tries = 4) {\n for (let i = 0; i < tries; i++) {\n const live = await readLive(name);\n if (live !== null && sha(live) === sha(content)) return { ok: true, live };\n if (i < tries - 1) await new Promise((r) => setTimeout(r, 1500 * (i + 1)));\n }\n return { ok: false, live: await readLive(name) };\n}\n\nasync function push(name, content) {\n const body = JSON.stringify({ content, type: typeFor(name) });\n // PUT UPDATES, POST CREATES. A PUT at a path that does not exist yet returns 404 \"File not\n // found\", which reads like a permissions or naming problem and is neither.\n // [was: PUT only. The first genuinely new engine file since this script was written —\n // puppy-detect.ts — failed to deploy with a 404 and the script had no idea why.]\n let r = await api(`/files?path=${encodeURIComponent(name)}`, { method: \"PUT\", body });\n if (r.status === 404) {\n r = await api(`/files?path=${encodeURIComponent(name)}`, { method: \"POST\", body });\n }\n if (r.ok) return { ok: true, status: r.status };\n return { ok: false, status: r.status, detail: (await r.text()).slice(0, 300) };\n}\n\n// The bundle parts are inert `file` entries on the val: the project's second home, next to the\n// code they describe. Same push-and-verify path as everything else, so they cannot rot silently.\nasync function pushBundle() {\n const dir = join(ROOT, \"handover\");\n const parts = readdirSync(dir).filter((f) => /^SOURCE-BUNDLE.*\\.txt$/.test(f)).sort();\n if (!parts.length) { console.log(\"no bundle parts found. Run: node scripts/bundle.mjs\"); return 1; }\n let bad = 0;\n for (const name of parts) {\n const content = readFileSync(join(dir, name), \"utf8\");\n if (content.length > 80_000) { console.log(`${name} OVER THE 80,000 CHARACTER LIMIT (${content.length.toLocaleString()})`); bad++; continue; }\n const r = await push(name, content);\n if (!r.ok) { console.log(`${name} PUSH FAILED ${r.status}: ${r.detail}`); bad++; continue; }\n const v = await verifyLive(name, content);\n console.log(`${name} ${content.length.toLocaleString()} chars ${v.ok ? `verified (v${await versionOf(name)})` : \"DID NOT VERIFY after 4 reads\"}`);\n if (!v.ok) bad++;\n }\n return bad;\n}\n\n// Branch BEFORE the engine comparison below, which runs at top level.\nif (has(\"--bundle\")) {\n const bad = await pushBundle();\n if (bad) console.log(`\\n${bad} bundle part(s) failed.`);\n process.exit(bad ? 1 : 0);\n}\n\nconst only = arg(\"--only\");\nconst locals = readdirSync(join(ROOT, \"engine\"))\n .filter((f) => f.endsWith(\".ts\") || f.endsWith(\".md\"))\n .map((f) => ({ file: f, name: NAMES[f] ?? f }))\n .filter((x) => !only || x.name === only || x.file === only);\n\nif (!locals.length) { console.log(\"nothing to deploy: engine/ has no source files\"); process.exit(1); }\n\nlet drift = 0, pushed = 0, failed = 0;\nconsole.log(`${has(\"--push\") ? \"PUSH\" : \"CHECK\"} ${locals.length} files val ${VAL}\\n`);\nconsole.log(\"local file val name local live state\");\n\nfor (const { file, name } of locals) {\n const local = readFileSync(join(ROOT, \"engine\", file), \"utf8\");\n let live = await readLive(name);\n let state;\n\n if (live === null) state = \"MISSING ON VAL\";\n else if (sha(live) === sha(local)) state = \"same\";\n else state = \"DIFFERS\";\n\n if (state !== \"same\" && has(\"--push\")) {\n const r = await push(name, local);\n if (!r.ok) { state = `PUSH FAILED ${r.status}: ${r.detail}`; failed++; }\n else {\n // Verify by re-reading, uncached and with retries. A 2xx is not proof.\n const v = await verifyLive(name, local);\n live = v.live;\n if (v.ok) { state = `pushed, verified (v${await versionOf(name)})`; pushed++; }\n else { state = `PUSHED BUT DID NOT VERIFY after 4 reads (live ${live === null ? \"missing\" : sha(live)})`; failed++; }\n }\n } else if (state !== \"same\") drift++;\n\n console.log(`${file.padEnd(26)} ${name.padEnd(21)} ${sha(local).slice(0, 8).padEnd(12)} ${(live === null ? \"-\" : sha(live).slice(0, 8)).padEnd(12)} ${state}`);\n}\n\n// main.ts has a hard ceiling and sits close to it. Say the number every time, not just when it breaks.\nconst mainSrc = readFileSync(join(ROOT, \"engine\", \"puppy_path_v1.1.ts\"), \"utf8\");\nconst mainChars = mainSrc.length;\n// BOTH UNITS. The cap is documented in characters and `.length` counts UTF-16 units, but nothing\n// here has ever confirmed val.town is not counting BYTES — and this file carries em-dashes and\n// curly quotes, so the two numbers differ by hundreds. On 6 Aug main.ts read 79,815 characters and\n// 80,137 bytes at the same moment: \"185 to spare\" on one measure and over the line on the other.\n// The push was accepted, which is evidence the cap is characters, but the stricter number is the\n// one worth watching, so both are printed and the gate uses the worse of the two.\nconst mainBytes = Buffer.byteLength(mainSrc ?? \"\", \"utf8\");\nconst worst = Math.max(mainChars, mainBytes);\nconsole.log(`\\nmain.ts is ${mainChars.toLocaleString()} characters / ${mainBytes.toLocaleString()} bytes against an 80,000 cap (${(80000 - worst).toLocaleString()} to spare on the stricter of the two)`);\nif (worst > 80000) { console.log(\"OVER THE CEILING on at least one measure. Move comments to NOTES-v1.4.md.\"); process.exit(1); }\n\nif (failed) { console.log(`\\n${failed} file(s) failed to deploy or verify.`); process.exit(1); }\nif (has(\"--push\")) console.log(`\\n${pushed} pushed and verified, ${locals.length - pushed} already matching.`);\nelse if (drift) { console.log(`\\n${drift} file(s) differ from the val. Run with --push.`); process.exit(1); }\nelse console.log(\"\\nlive matches local, every file.\");\n\n\n=====FILE scripts/make-pdfs.mjs =====\n// REBUILD THE CLIENT PDFs, end to end, from the live message set.\n//\n// WHY THIS EXISTS. The container was reclaimed twice in two days. The second time, everything\n// restored from the bundle except `handover/TheDogsSpot-First3Weeks.pdf`, and the cross-artifact\n// suite went red because a live fact in the claims registry is that PDF's page count. Binaries are\n// not in the bundle and should not be: they are DERIVED, and a backup of a derived artifact is a\n// backup of the wrong thing.\n//\n// What was actually missing was this file. `scripts/make_pdf.py` reads `/tmp/msgs.json`, in a\n// shape it never documents — an object keyed by track, not the flat array you would naturally\n// write — and that shape lived only in my head. First attempt at regenerating after the reclaim\n// produced `'list' object has no attribute 'get'`.\n//\n// Run: node scripts/make-pdfs.mjs\nimport { writeFileSync, existsSync } from \"node:fs\";\nimport { spawnSync } from \"node:child_process\";\nimport { join, dirname, resolve } from \"node:path\";\nimport { fileURLToPath } from \"node:url\";\n\nconst ROOT = resolve(dirname(fileURLToPath(import.meta.url)), \"..\");\nconst TRACKS = [\"MAIN_SEQUENCE\", \"BRANCH_A\", \"BRANCH_B\", \"SLOW_WEEKLY\", \"SLOW_FORTNIGHTLY\", \"SLOW_MONTHLY_BANK\"];\n\nif (!existsSync(join(ROOT, \"build/engine.js\"))) {\n console.log(\"build/engine.js is missing. Run: node scripts/build.mjs\");\n process.exit(1);\n}\nconst E = await import(join(ROOT, \"build/engine.js\"));\n\n// THE SHAPE make_pdf.py EXPECTS: an object keyed by track name, each value an array of messages.\nconst byTrack = {};\nfor (const k of TRACKS) byTrack[k] = E[k] ?? [];\nconst total = Object.values(byTrack).reduce((a, v) => a + v.length, 0);\nif (!total) { console.log(\"no messages found in build/engine.js: refusing to build an empty PDF\"); process.exit(1); }\nwriteFileSync(\"/tmp/msgs.json\", JSON.stringify(byTrack));\nconsole.log(`${total} messages: ${Object.entries(byTrack).map(([k, v]) => `${k}=${v.length}`).join(\" \")}`);\n\n// The claims registry states these page counts as LIVE facts about the documents Kim was sent, so\n// a rebuild that changes them is a real change and the cross-artifact suite will say so.\nconst EXPECTED = { \"TheDogsSpot-First3Weeks.pdf\": 6, \"TheDogsSpot-AllMessages.pdf\": 14 };\n\nlet bad = 0;\nfor (const [arg, name] of [[\"short\", \"TheDogsSpot-First3Weeks.pdf\"], [null, \"TheDogsSpot-AllMessages.pdf\"]]) {\n const r = spawnSync(\"python3\", [join(ROOT, \"scripts/make_pdf.py\"), ...(arg ? [arg] : [])],\n { encoding: \"utf8\", cwd: ROOT });\n if (r.status !== 0) { console.log(`FAILED ${name}:\\n${(r.stdout + r.stderr).trim().slice(0, 500)}`); bad++; continue; }\n // Page count without a PDF library, the same way the claims registry counts them.\n const buf = (await import(\"node:fs\")).readFileSync(join(ROOT, \"handover\", name)).toString(\"latin1\");\n const pages = (buf.match(/\\/Type\\s*\\/Page[^s]/g) || []).length;\n const want = EXPECTED[name];\n const ok = pages === want;\n if (!ok) bad++;\n console.log(`${ok ? \"ok \" : \"PAGE COUNT CHANGED\"} ${name} ${pages} pages${ok ? \"\" : ` (the message Kim already has says ${want})`}`);\n}\nif (bad) {\n console.log(\"\\nA page count that has moved is not automatically wrong, but Kim was told a number.\");\n console.log(\"Either put the copy back, or update tests/claims-registry.mjs and say so in the next message.\");\n process.exit(1);\n}\nconsole.log(\"\\nboth PDFs rebuilt, page counts match what Kim was told\");\n\n\n=====FILE scripts/make_pdf.py =====\nimport json, re, sys\nfrom reportlab.lib.pagesizes import LETTER\nfrom reportlab.lib.styles import getSampleStyleSheet, ParagraphStyle\nfrom reportlab.lib.units import inch\nfrom reportlab.lib import colors\nfrom reportlab.platypus import SimpleDocTemplate, Paragraph, Spacer, HRFlowable, KeepTogether\nfrom reportlab.lib.enums import TA_LEFT\n\nD = json.load(open('/tmp/msgs.json'))\nSHORT = len(sys.argv) > 1 and sys.argv[1] == \"short\"\nss = getSampleStyleSheet()\nH1 = ParagraphStyle('H1', parent=ss['Title'], fontName='Helvetica-Bold', fontSize=19, leading=23, alignment=TA_LEFT, spaceAfter=3, textColor=colors.HexColor('#111111'))\nSUB = ParagraphStyle('SUB', parent=ss['Normal'], fontSize=10, leading=14, textColor=colors.HexColor('#5a5a5a'), spaceAfter=13)\nH2 = ParagraphStyle('H2', parent=ss['Heading2'], fontName='Helvetica-Bold', fontSize=13, leading=16, spaceBefore=15, spaceAfter=5, textColor=colors.HexColor('#111111'))\nLBL = ParagraphStyle('LBL', parent=ss['Normal'], fontName='Helvetica-Bold', fontSize=9, leading=12, textColor=colors.HexColor('#2a78d6'), spaceAfter=1)\nSUBJ= ParagraphStyle('SUBJ', parent=ss['Normal'], fontName='Helvetica-Bold', fontSize=10.5, leading=14, spaceAfter=3)\nBODY= ParagraphStyle('BODY', parent=ss['Normal'], fontSize=10, leading=14.5, spaceAfter=6)\nNOTE= ParagraphStyle('NOTE', parent=ss['Normal'], fontSize=9, leading=12.5, textColor=colors.HexColor('#5a5a5a'), spaceAfter=9)\n\nesc = lambda t: t.replace('&','&').replace('<','<').replace('>','>')\ndef fmt(t):\n t = esc(t)\n t = re.sub(r'\\{\\{STORY:[^}]+\\}\\}\\s*', '', t)\n t = t.replace('{{FIRST_NAME}}', '[their name]')\n return re.sub(r'\\*\\*(.+?)\\*\\*', r'\\1', t)\nday = lambda m: round(m.get('offsetHours', 0) / 24)\n\nflow = [Paragraph(\"The Dogs Spot: the first three weeks\" if SHORT else \"The Dogs Spot: every follow-up message\", H1),\n Paragraph(\"Every word below was read out of the running system, not retyped from a draft, so what you read is exactly what would send. Everything you sent over is in it: the puppy-name placeholder is gone from every message, the American wording is fixed throughout, the service you do not offer is no longer mentioned anywhere, and both of the missed-Pup-Talk messages are now your rewrite rather than mine. The Touch numbers restart at 1 in each part below.\", SUB),\n HRFlowable(width=\"100%\", thickness=0.6, color=colors.HexColor('#dddddd'), spaceAfter=4)]\n\nSEC = [(\"The first 21 days\",\"MAIN_SEQUENCE\",\"Eight messages over three weeks, counted the way you read them: Touch 1 is the first thing a customer receives. Later parts start their own count again.\"),\n (\"If they book a Pup Talk and do not show\",\"BRANCH_A\",\"Two messages. Both are your rewrite, word for word.\"),\n (\"After a Pup Talk that did not turn into a booking\",\"BRANCH_B\",\"Two messages. No pressure in either.\")]\nif not SHORT:\n SEC += [(\"Then weekly for a month\",\"SLOW_WEEKLY\",\"Four messages. No asks on any of them.\"),\n (\"Then every two weeks for six months\",\"SLOW_FORTNIGHTLY\",\"Thirteen messages.\"),\n (\"Then monthly, indefinitely\",\"SLOW_MONTHLY_BANK\",\"Twelve messages, one a month, seasonal where it fits. These repeat each year.\")]\n\nfor title, key, blurb in SEC:\n flow += [Paragraph(title, H2), Paragraph(blurb, NOTE)]\n for i, m in enumerate(D.get(key, []), 1):\n parts = [Paragraph(f\"TOUCH {i} · {'TEXT MESSAGE' if m['channel']=='sms' else 'EMAIL'} · {'day ' + str(day(m)) if key=='MAIN_SEQUENCE' else ('monthly slot ' + str(i) + ' of 12' if key=='SLOW_MONTHLY_BANK' else '+' + str(day(m)) + ' days')}\", LBL)]\n if m.get('subject'): parts.append(Paragraph(\"Subject: \" + fmt(m['subject']), SUBJ))\n for para in [p for p in re.split(r'\\n\\s*\\n', m['bodyTemplate']) if p.strip()]:\n parts.append(Paragraph(fmt(para).replace('\\n','
'), BODY))\n if m['channel'] == 'sms': parts.append(Paragraph(\"Every text ends with: Reply STOP to stop these texts.\", NOTE))\n parts.append(HRFlowable(width=\"100%\", thickness=0.4, color=colors.HexColor('#eeeeee'), spaceAfter=6))\n flow.append(KeepTogether(parts))\n\nif SHORT:\n flow += [Paragraph(\"What happens after these three weeks\", H2),\n Paragraph(\"The slow track picks up: weekly for a month, then every two weeks for six months, then one a month from there on, cycling the same twelve seasonal ones year after year. That is in the companion document if you want it, and nothing about it changed.\", BODY)]\nflow.append(Paragraph(\"The rules that run underneath all of it\", H2))\nfor line in [\"Anyone who replies comes off the track immediately and gets a person instead.\",\n \"Anyone who books comes off the track.\",\n \"Anyone who texts STOP never hears from the system again, on any track.\",\n \"Nothing sends late at night, and no texts on a Sunday.\",\n \"Nothing has sent to anybody yet. The whole thing is in practice mode until you say the word.\"]:\n flow.append(Paragraph(\"• \" + esc(line), BODY))\n\nout = \"handover/TheDogsSpot-First3Weeks.pdf\" if SHORT else \"handover/TheDogsSpot-AllMessages.pdf\"\nSimpleDocTemplate(out, pagesize=LETTER, leftMargin=0.85*inch, rightMargin=0.85*inch, topMargin=0.7*inch, bottomMargin=0.7*inch,\n title=(\"The Dogs Spot: the first three weeks\" if SHORT else \"The Dogs Spot: every follow-up message\"), author=\"Amir Aizhigitov\").build(flow)\nprint(\"built\", out)\n\n",[343],"9e80942f-9f20-4083-9743-9273e12d7d80","SOURCE-BUNDLE.part6.txt","f58f8f72-91ad-11f1-82b0-1607ee4eb77e",285,["D",1786044232885],"THE DOGS SPOT — SOURCE BUNDLE (part 6 of 9)\n\nEverything in this project that does not already live on val.town. The engine is NOT here:\nseventeen files on val 1bfa6e81-74e1-4c6c-ab32-118304a4ffff, verified file by file by\nscripts/deploy.mjs --check. Restore that with the val, restore this with the snippet below.\n\nRESTORE (needs only node, from an empty folder). Save each part, then run this ON EACH ONE:\n\n node -e 'const fs=require(\"fs\"),p=require(\"path\");const b=fs.readFileSync(process.argv[1],\"utf8\");\n for(const s of b.split(\"\\n=====FILE \").slice(1)){const i=s.indexOf(\" =====\\n\");\n const f=s.slice(0,i),c=s.slice(i+7);fs.mkdirSync(p.dirname(f),{recursive:true});\n fs.writeFileSync(f,c.replace(/\\n$/,\"\"))}' PART.txt\n\nEach part is complete in itself: whole files only, no reassembly, any order.\n\nThen: node scripts/deploy.mjs --check (pulls nothing, proves the val matches)\n node scripts/build.mjs (needs engine/ back from the val first)\n node tests/run-all.mjs\n node tests/negative-controls.mjs (proves the suite above can actually fail)\n\nIN THIS PART (3 of 34 files)\n tests/negative-controls.mjs 62121 bytes 96d74577b0d3\n tests/registry.test.mjs 4947 bytes 9cfa5044cbd0\n tests/render.test.mjs 2941 bytes ea24d897a12f\n\n================================================================================================\n=====FILE tests/negative-controls.mjs =====\n// NEGATIVE CONTROLS. The suite that tests the suite.\n//\n// THE RULE: a check that cannot fail is not a check. This project has already shipped three of\n// them — an audit that matched zero candidates, a spelling check that scanned zero of the strings\n// it claimed to cover, and a cross-artifact check whose whitelist was three words long. All three\n// reported \"all clear\" for days. None of them could ever have gone red.\n//\n// So every control below does the same four things:\n// 1. copies the whole tree somewhere disposable (the real tree is never touched),\n// 2. injects ONE specific fault into the SOURCE,\n// 3. rebuilds and runs the ONE suite that claims to catch it,\n// 4. demands that suite go red ON THE NAMED TEST.\n//\n// Step 4 is the part that matters. \"The suite went red\" is not good enough: a typo in the\n// injection would also make it go red, and then the control would be passing for the wrong reason.\n// A control only passes when the specific test that owns that guarantee is the one that fails.\n//\n// Run: node tests/negative-controls.mjs\nimport { cpSync, rmSync, readFileSync, writeFileSync, mkdtempSync, existsSync } from \"node:fs\";\nimport { spawnSync } from \"node:child_process\";\nimport { join, dirname, resolve } from \"node:path\";\nimport { tmpdir } from \"node:os\";\nimport { fileURLToPath } from \"node:url\";\n\nconst ROOT = resolve(dirname(fileURLToPath(import.meta.url)), \"..\");\n\n// ---------------------------------------------------------------------------------------------\n// THE CONTROLS. Each says: break THIS, and THAT test must be the one that notices.\n// ---------------------------------------------------------------------------------------------\nconst CONTROLS = [\n {\n name: \"a service she does not offer creeps back into a message\",\n file: \"engine/puppy-messages.ts\",\n // A real message body, not a comment. [was: `find: \"Kim\"`, which landed on line 17 of the\n // file header. The test correctly ignored it and the control read as \"the check is blind\".\n // A control that injects a fault the system was never claiming to catch proves nothing.]\n find: \"that's not a behavior problem\",\n replace: \"that's not a behavior problem, and our daycare helps\",\n once: true,\n suite: \"kim-copy.test.mjs\",\n mustFail: \"K-b daycare\",\n },\n {\n name: \"British spelling creeps back into customer copy\",\n file: \"engine/taper-messages.ts\",\n find: \"your dog\",\n replace: \"your favourite dog\",\n once: true,\n suite: \"kim-copy.test.mjs\",\n mustFail: \"K-d no British spelling\",\n },\n {\n name: \"the dog-name placeholder comes back after Kim had it removed\",\n file: \"engine/taper-messages.ts\",\n find: \"your dog\",\n replace: \"{{DOG_NAME}}\",\n once: true,\n suite: \"kim-copy.test.mjs\",\n mustFail: \"K-a no dog-name placeholder\",\n },\n {\n name: \"an em-dash reaches a customer\",\n file: \"engine/taper-messages.ts\",\n find: \"your dog\",\n replace: \"your dog — yes\",\n once: true,\n suite: \"kim-copy.test.mjs\",\n mustFail: \"K-g no em-dashes\",\n },\n {\n name: \"a text message grows past the segment limit\",\n file: \"engine/taper-messages.ts\",\n find: \"Dogs repeat what pays.\",\n replace: \"Dogs repeat what pays. \" + \"Padding that pushes this text well past three hundred and twenty characters so the limit check has something real to catch, because a limit that is never approached is never tested and the first time it matters is the day it silently costs money.\",\n once: true,\n suite: \"sms-length.test.mjs\",\n mustFail: \"T1 no SMS exceeds 320\",\n },\n {\n name: \"somebody writes a story into a slot instead of waiting for Kim\",\n file: \"engine/kim-stories.ts\",\n find: ` lands: \"Slow track week 1 — the adolescence email\",\\n story: null,`,\n replace: ` lands: \"Slow track week 1 — the adolescence email\",\\n story: \"A lab called Buster went through it and came out fine.\",`,\n once: true,\n suite: \"stories.test.mjs\",\n mustFail: \"S1 there are eight slots\",\n },\n {\n name: \"story resolution goes back to a single pass\",\n file: \"engine/kim-stories.ts\",\n // Restores the EXACT implementation that shipped the leak: one pass over well-formed ids and\n // nothing else. [was: only the loop bound was lowered to 1, which changed nothing — the guard\n // is the TOKEN_SHAPE sweep, not the loop. The control passed a fault the code still caught,\n // and would have reported \"the test is blind\" about a test that works.]\n find: ` let out = String(text ?? \"\");`,\n replace: ` return text\\n .replace(/\\\\{\\\\{STORY:([a-z_]+)\\\\}\\\\}/g, (_, id) => storyFor(id) ?? \"\")\\n .replace(/\\\\n{3,}/g, \"\\\\n\\\\n\")\\n .trim();\\n let out = String(text ?? \"\");`,\n suite: \"stories.test.mjs\",\n mustFail: \"S5 a nested or malformed token\",\n },\n {\n name: \"the slow track quietly loses a message\",\n file: \"engine/taper-messages.ts\",\n find: \"export const SLOW_FORTNIGHTLY_COUNT = 13;\",\n replace: \"export const SLOW_FORTNIGHTLY_COUNT = 12;\",\n once: true,\n suite: \"slow-track.test.mjs\",\n mustFail: \"T1 the track is the shape Kim signed off\",\n },\n {\n name: \"two text messages end up back to back\",\n file: \"engine/taper-messages.ts\",\n // [was: `id: \"slow_f-7\", channel: \"sms\"` inserted BEFORE the object's own channel property.\n // A later duplicate key wins in a JS object literal, so the injection was silently undone\n // and the control reported the test as blind. It was the control that was blind.]\n find: `id: \"slow_f-7\",\\n channel: \"email\",`,\n replace: `id: \"slow_f-7\",\\n channel: \"sms\",`,\n once: true,\n suite: \"slow-track.test.mjs\",\n mustFail: \"T13 two text messages never land back to back\",\n },\n {\n name: \"two messages end up sharing an id, so the journal cannot tell them apart\",\n file: \"engine/taper-messages.ts\",\n find: `id: \"slow_f-9\"`,\n replace: `id: \"slow_f-7\"`,\n once: true,\n suite: \"slow-track.test.mjs\",\n mustFail: \"T11 every slow-track message has an id\",\n },\n {\n name: \"a sales ask appears on the track Kim signed off as no-ask\",\n file: \"engine/taper-messages.ts\",\n find: \"Dogs repeat what pays.\",\n replace: \"Dogs repeat what pays. Book now.\",\n once: true,\n suite: \"taper-test.ts\",\n mustFail: \"no sales asks\",\n },\n {\n name: \"a story token names a slot that does not exist\",\n file: \"engine/taper-messages.ts\",\n find: \"{{STORY:vet_visits}}\",\n replace: \"{{STORY:vet_visit}}\",\n once: true,\n suite: \"taper-test.ts\",\n mustFail: \"every story token names a real slot\",\n },\n {\n name: \"a retried payment gets counted once per retry, inflating the backlog\",\n file: \"engine/facts.ts\",\n find: \"const byPayment = new Map\",\n replace: \"const byPayment = new Map0\",\n once: true,\n expectBuildFailure: false,\n suite: \"facts.test.mjs\",\n mustFail: \"F1 a payment logged many times\",\n },\n {\n name: \"a name with no value renders as 'Hi ,'\",\n file: \"engine/render.ts\",\n find: \"export function resolveFirstName\",\n replace: \"export function resolveFirstName_UNUSED\",\n once: true,\n suite: \"render.test.mjs\",\n mustFail: \"M1.1 blank names fall back\",\n },\n // ---------------------------------------------------------- cross-artifact: the check that has\n // been fake three times. Six controls, one per way it could go quietly blind again.\n {\n name: \"a sentence stating a number about her system is added and nothing vouches for it\",\n file: \"handover/SEND-TO-KIM.txt\",\n find: \"Nothing has sent to anybody.\",\n replace: \"Seventeen contacts are in the sequence now. Nothing has sent to anybody.\",\n suite: \"cross-artifact.test.mjs\",\n mustFail: \"X2 every sentence stating a number\",\n },\n {\n name: \"the prose is edited and the registry is left behind (the Square failure, exactly)\",\n file: \"handover/SEND-TO-KIM.txt\",\n find: \"The first three weeks are attached, six pages\",\n replace: \"The first three weeks are attached, seven pages\",\n suite: \"cross-artifact.test.mjs\",\n mustFail: \"X3 every registry entry still points\",\n },\n {\n name: \"a live fact in the prose stops matching what the code computes\",\n file: \"tests/claims-registry.mjs\",\n find: \" stated: 41,\",\n replace: \" stated: 40,\",\n suite: \"cross-artifact.test.mjs\",\n mustFail: \"X5 every LIVE fact\",\n },\n {\n name: \"a pinned fact is dated in the future, so nobody can have read it\",\n file: \"tests/claims-registry.mjs\",\n find: 'source: \"GHL GET /products, location BQHJ19uohldYe3eqA0bl\",\\n readAt: \"2026-08-04\",',\n replace: 'source: \"GHL GET /products, location BQHJ19uohldYe3eqA0bl\",\\n readAt: \"2027-08-04\",',\n suite: \"cross-artifact.test.mjs\",\n mustFail: \"X6 every PINNED fact\",\n },\n {\n name: \"an exemption is downgraded to a shrug\",\n file: \"tests/claims-registry.mjs\",\n find: 'reason: \"\\'One thing\\' introduces a single observation. It counts nothing about her system.\",',\n replace: 'reason: \"n/a\",',\n suite: \"cross-artifact.test.mjs\",\n mustFail: \"X7 every PROSE exemption\",\n },\n {\n name: \"the coverage rule is weakened until it matches nothing\",\n file: \"tests/claims-registry.mjs\",\n find: \"export const HAS_SYSTEM_NOUN = /\",\n replace: \"export const HAS_SYSTEM_NOUN = /__never_matches_anything__/i; const _dead = /\",\n suite: \"cross-artifact.test.mjs\",\n mustFail: \"X9 the coverage rule can still see\",\n },\n {\n name: \"a number that drifts on its own is put into a message that cannot be re-read\",\n file: \"handover/SEND-TO-KIM.txt\",\n find: \"Nothing has sent to anybody.\",\n replace: \"You have 34 opportunities open right now. Nothing has sent to anybody.\",\n suite: \"cross-artifact.test.mjs\",\n mustFail: \"X10 the message that went to Kim\",\n },\n // ------------------------------------------------------- the comment-blindness controls. These\n // exist because a check passed on a `[was: ...]` note explaining the very call it forbade.\n {\n name: \"a forbidden call is put back, and a comment is NOT enough to satisfy the check\",\n file: \"engine/dashboard.ts\",\n find: \"const wdCadence = wdTracksTrigger ? observedCadenceMin(wdAuto) : null;\",\n replace: \"const wdCadence = observedCadenceMin(wd?.history);\",\n suite: \"dashboard.test.mjs\",\n mustFail: \"D2b.1a a rhythm is only ever measured\",\n },\n {\n name: \"the forbidden call appears ONLY inside a comment, and the check must stay green\",\n file: \"engine/dashboard.ts\",\n find: \" const wdAuto: string[] | null =\",\n replace: \" // note: observedCadenceMin(wd?.history) is what this used to be\\n const wdAuto: string[] | null =\",\n suite: \"dashboard.test.mjs\",\n mustFail: null, // INVERTED: this one must NOT go red. See runControl.\n mustStayGreen: true,\n },\n {\n name: \"the comment stripper is neutered, so structural checks read prose again\",\n file: \"tests/_harness.mjs\",\n // Neutered for LINE comments only, so codeOnly's own zero-stripped guard still sees the block\n // comments go and does not throw. [was: `if (false)`, which stripped nothing at all and made\n // codeOnly throw — the control then reported \"it crashed rather than caught anything\", which\n // was true and useless. A control has to break the thing under test, not its smoke alarm.]\n find: 'if (t.startsWith(\"//\") || t.startsWith(\"*\")) { removed++; out.push(\"\"); continue; }',\n replace: 'if (t.startsWith(\"*\")) { removed++; out.push(\"\"); continue; }',\n suite: \"dashboard.test.mjs\",\n mustFail: \"D2b.1a a rhythm is only ever measured\",\n },\n {\n name: \"the watchdog goes back to being graded on when it was last poked\",\n file: \"engine/dashboard.ts\",\n find: \" const wdNeverRanItself = wdTracksTrigger && wdAuto.length === 0;\",\n replace: \" const wdNeverRanItself = false;\",\n suite: \"dashboard.test.mjs\",\n mustFail: \"D2b.1a a rhythm is only ever measured\",\n },\n {\n name: \"the practice-mode send guard is deleted from the email sender\",\n file: \"engine/puppy_path_v1.1.ts\",\n find: ' assertSendAllowed(contactId, \\\"email\\\");\\n',\n replace: \"\",\n suite: \"detect.test.mjs\",\n mustFail: \"G1 both senders open by asserting the send is allowed\",\n // The FIRST message anyone enrolled receives is an email, so the email guard is the one that\n // matters most and it had no control of its own. The sms control below proved only the sms half.\n },\n {\n name: \"the practice-mode send guard is deleted from the sms sender\",\n file: \"engine/puppy_path_v1.1.ts\",\n find: ' assertSendAllowed(contactId, \\\"sms\\\");\\n',\n replace: \"\",\n suite: \"detect.test.mjs\",\n mustFail: \"G1 both senders open by asserting the send is allowed\",\n },\n {\n name: \"a system that has never run on its own gets described as merely late\",\n file: \"engine/cadence.ts\",\n find: \"Nothing on a schedule has been recorded in that time.\",\n replace: \"It runs about every 95 minutes and it is on time.\",\n // [was: it injected over the pre-5-Aug sentence \"Nothing has started it on its own, which\n // means its timer is not firing.\" That text survives only inside a comment now, so the\n // injection edited a comment and the suite rightly stayed green. Retargeted at the sentence\n // the code actually returns today.]\n suite: \"cadence.test.mjs\",\n mustFail: \"C5 a system that has never started itself\",\n },\n {\n name: \"a fresh, unmeasured schedule claim is written into the log Kim reads\",\n file: \"engine/worklog.ts\",\n find: ' {\\n at: \"2026-08-05\",',\n replace: ' {\\n at: \"2026-08-05\",\\n kind: \"built\",\\n what: \"The reminder system now checks your calendar every 15 minutes and sends what is due.\",\\n evidence: \"Built and deployed.\",\\n },\\n {\\n at: \"2026-08-05\",',\n suite: \"dashboard.test.mjs\",\n mustFail: \"D1.6 nothing in the log claims a schedule\",\n },\n {\n name: \"the go-live blocker goes back to quoting a scan size instead of a live count\",\n file: \"engine/decisions.ts\",\n find: \" (c.puppyTagSentence ?? \",\n replace: \" (\\\"Separately, 1,200 of your most recent contacts were checked and not one carries the tag.\\\" ?? \",\n suite: \"dashboard.test.mjs\",\n mustFail: \"D2b.4 no decision hardcodes a live number\",\n },\n {\n name: \"a failed tag read renders as though the tagging had been confirmed\",\n file: \"engine/decisions.ts\",\n find: '\"The mark our system watches for could not be counted just now, so treat the tagging step as unconfirmed rather than done.\"',\n replace: '\"Nothing carries the tag.\"',\n suite: \"dashboard.test.mjs\",\n mustFail: \"D2b.4 no decision hardcodes a live number\",\n },\n {\n name: \"a tag count that could not be read is rendered as a confident zero\",\n file: \"engine/facts.ts\",\n find: 'return \"We could not read your contact records just now, so this says nothing rather than a zero worth trusting.\";',\n replace: 'return \"0 of your contacts are marked as a puppy inquiry.\";',\n suite: \"facts.test.mjs\",\n mustFail: \"F11 the tag sentence counts the WHOLE base\",\n },\n {\n name: \"a 'how we know' line claims a bigger scope than was actually measured\",\n file: \"engine/decisions.ts\",\n find: '\"Sixty-two of your calls were checked from your most recently active conversations: 54',\n replace: '\"Every call in your account was checked on 5 August. Of them, 54',\n // [was: it looked for the K16 evidence text as written on the morning of 5 Aug. K16 was\n // rewritten that evening after the transcript correction, so the injection matched nothing\n // and the control was blind. Retargeted, and the injected sentence is kept number-free so\n // it exercises the date-is-not-a-denominator rule, not the easy case.]\n suite: \"dashboard.test.mjs\",\n mustFail: \"D1.7 no 'how we know' claims a bigger scope\",\n },\n // ------------------------------------------------------------ who gets nineteen months of mail\n {\n name: \"a dog described in years is read as a puppy again (the '3 years and 4 months' trap)\",\n file: \"engine/puppy-detect.ts\",\n find: \"(?:year|yr)s?\\\\b/);\",\n replace: \"(?:year|yr)s?[\\\\s-]*old/);\",\n suite: \"detect.test.mjs\",\n mustFail: \"N1 a dog described in years\",\n },\n {\n name: \"somebody asking to BUY a puppy is treated as a training inquiry\",\n file: \"engine/puppy-detect.ts\",\n find: \"[/\\\\b(purchase|buy|buying|sell|selling|for sale|breeder|adopt(?:ing)? a)\\\\b[^.]{0,40}\\\\bpupp/i,\",\n replace: \"[/\\\\bzzz_never_matches_anything\\\\b/i,\",\n suite: \"detect.test.mjs\",\n mustFail: \"N5 the three real false positives\",\n },\n {\n name: \"a contact with nothing written down is answered 'no' instead of 'unclear'\",\n file: \"engine/puppy-detect.ts\",\n find: 'return { contactId, name, confidence: \"unclear\", ageMonths: null, matched: [],',\n replace: 'return { contactId, name, confidence: \"no\", ageMonths: null, matched: [],',\n suite: \"detect.test.mjs\",\n mustFail: \"N8 an empty record is 'unclear'\",\n },\n {\n name: \"the half of the contact base with nothing written down stops being reported\",\n file: \"engine/puppy-detect.ts\",\n find: \" if (s.noText) {\",\n replace: \" if (false) {\",\n suite: \"detect.test.mjs\",\n mustFail: \"N12 the blind spot is in the output\",\n },\n {\n name: \"the classifier grows the ability to tag somebody\",\n file: \"engine/puppy-detect.ts\",\n find: \"export function inquiryText(contact: unknown): string {\",\n replace: 'async function applyTag(id: string) { await fetch(`https://services.leadconnectorhq.com/contacts/${id}/tags`, { method: \"POST\" }); }\\nexport function inquiryText(contact: unknown): string {',\n suite: \"detect.test.mjs\",\n mustFail: \"N13 the classifier has no way to reach the CRM\",\n },\n {\n name: \"the hourly scan starts storing what people wrote about their dogs\",\n file: \"engine/puppy-detect.ts\",\n find: \" clearIds: vs.filter((v) => v.confidence === \\\"clear\\\").map((v) => v.contactId),\",\n replace: \" clearIds: vs.filter((v) => v.confidence === \\\"clear\\\").map((v) => `${v.contactId} ${v.name} ${v.reason}`),\",\n suite: \"detect.test.mjs\",\n mustFail: \"N15 it carries ids only\",\n },\n {\n name: \"a dry pass that has not run for days keeps showing its old numbers as current\",\n file: \"engine/puppy-detect.ts\",\n find: \" if (hours < 6) return null;\",\n replace: \" return null;\",\n suite: \"detect.test.mjs\",\n mustFail: \"N17 a dry pass that stopped running\",\n },\n {\n name: \"an edit-in-place in her CRM stops being noticed (only adds and removes are)\",\n file: \"engine/registry-diff.ts\",\n find: \" const edited = nowIds.filter((i) => i in a && a[i] !== b[i]).map((i) => `${a[i]} -> ${b[i]}`);\",\n replace: \" const edited: string[] = [];\",\n suite: \"registry.test.mjs\",\n mustFail: \"G1 an edit in place is caught\",\n },\n {\n name: \"an empty API response overwrites a good baseline and fires a false 'everything removed'\",\n file: \"engine/registry-diff.ts\",\n find: \" return nowCount === 0 && (prevCount ?? 0) > 0;\",\n replace: \" return false;\",\n suite: \"registry.test.mjs\",\n mustFail: \"G6 an empty list on a good response\",\n },\n {\n name: \"the change alarm quietly truncates its list without saying how much it dropped\",\n file: \"engine/registry-diff.ts\",\n find: \" if (more > 0) bits.push(`${more} more not listed here.`);\",\n replace: \" if (false) bits.push(``);\",\n suite: \"registry.test.mjs\",\n mustFail: \"G7 the sentence is generated from the change\",\n },\n\n // -------------------------------------------------------------------------------------------\n // THE HOLIDAY DEPOSIT TRACKER. Every one of these faults ends with Kim asking a customer for\n // $50 they already paid, in her name, about money. That is why this module gets eight controls\n // rather than the usual two: the blast radius of a wrong answer here is a lost customer.\n // -------------------------------------------------------------------------------------------\n {\n name: \"a standing weekly booking starts counting as a holiday stay\",\n file: \"engine/holiday-deposits.ts\",\n // Real: \"Daycare Enzo\" is a recurring slot that lands inside EVERY holiday window. Drop this\n // filter and Kim is told a regular customer owes her a holiday deposit, eight times over.\n // [was: `if (e.isRecurring === true)`. Retargeted when the flag check was widened to cope\n // with her CRM sending \"true\" as a string.]\n find: \" if (truthy(e.isRecurring)) return false;\",\n replace: \" if (false) return false;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H4 a recurring weekly slot\",\n },\n {\n name: \"a customer's three dogs become three separate deposit questions\",\n file: \"engine/holiday-deposits.ts\",\n // Real: Achilles, Ghost and Chewy all drop off on 25 Nov for one person. Keying the group by\n // the booking title instead of the customer+day turns one $50 question into three.\n find: \" const key = `${e.contactId}|${day}`;\",\n replace: \" const key = `${e.contactId}|${day}|${e.title}`;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H6 three dogs on one day\",\n },\n {\n name: \"appointment times get parsed into Date objects and shift across midnight\",\n file: \"engine/holiday-deposits.ts\",\n // The plausible-looking \"tidy-up\" that moves a 25 Nov drop-off to the 24th or the 26th, which\n // silently drags bookings in and out of the window Kim is chasing.\n find: \" const d = startTime.slice(0, 10);\",\n replace: \" const d = new Date(startTime).toISOString().slice(0, 10);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H8 the local day is read off the string\",\n },\n {\n name: \"Thanksgiving stops being computed and gets typed in\",\n file: \"engine/holiday-deposits.ts\",\n // Kim was told it is worked out fresh each year so it cannot drift. This is that promise\n // being broken in the most ordinary way: someone hardcodes this year's date.\n find: \" const day = firstThu + 21;\",\n replace: \" const day = 26;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H1 Thanksgiving is the fourth Thursday\",\n },\n {\n name: \"one payment written five times gets counted five times\",\n file: \"engine/holiday-deposits.ts\",\n // Her real notes hold the SAME Square payment five times. Making the key unique per note —\n // which looks like a fix — reports $1,775 against a $355 payment.\n // [was: `find: \" const id = m[2];\"`, which was the single-format parser's line. When the\n // parser was rewritten to handle both live note formats the injection stopped matching, and\n // this control reported itself blind rather than passing on a fault it never applied. That\n // is the harness working: a control that silently stops injecting is the whole failure mode.]\n find: \" for (const m of body.matchAll(DIRECT)) add(Number(m[1].replace(/,/g, \\\"\\\")), m[2], n?.dateAdded ?? null, \\\"direct\\\");\",\n replace: \" for (const m of body.matchAll(DIRECT)) add(Number(m[1].replace(/,/g, \\\"\\\")), m[2] + (n?.dateAdded ?? \\\"\\\"), n?.dateAdded ?? null, \\\"direct\\\");\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H9 one payment written five times\",\n },\n {\n name: \"the balance figure gets read, and the duplicates disagree with each other\",\n file: \"engine/holiday-deposits.ts\",\n // The five duplicates say $355.00 then $0.00 four times. Read the balance and the answer\n // depends on which duplicate happened to be read last.\n // [was: aimed at the single-format parser's `const amount = ...` line, which no longer exists.\n // Retargeted onto the direct-format branch of the two-format parser.]\n find: \" const add = (amount: number, id: string, at: string | null, kind: \\\"direct\\\" | \\\"matched\\\") => {\",\n replace: \" const add = (amount: number, id: string, at: string | null, kind: \\\"direct\\\" | \\\"matched\\\") => {\\n const bal = /balance \\\\$([\\\\d,.]+)/.exec(String(notes?.[0]?.body ?? \\\"\\\"));\\n if (bal) amount = Number(bal[1].replace(/,/g, \\\"\\\"));\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H10 the contradictory balance figure\",\n },\n {\n name: \"an API hiccup becomes 'this person has not paid'\",\n file: \"engine/holiday-deposits.ts\",\n // The single worst thing this module could do. A failed read must stay unknown; collapsing it\n // into none_seen puts a paying customer on the chase list because the network blinked.\n find: ` return { stay, state: \"could_not_check\", amountSeen: 0,`,\n replace: ` return { stay, state: \"none_seen\", amountSeen: 0,`,\n once: true,\n then: {\n find: ` note: \"We could not read this person's payments just now, so this one is unknown. It is not a finding either way.\" };`,\n replace: ` note: \"No Square payment is on file, so this deposit is outstanding.\" };`,\n },\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H13 a failed read is never reported\",\n },\n {\n name: \"the read-only report grows a way to write to her CRM\",\n file: \"engine/holiday-deposits.ts\",\n // addTag() in this engine is not TEST_MODE guarded, and this account holds a workflow that\n // turns one tag into do-not-disturb on six channels. Read-only is structural here, not a\n // promise in a comment.\n find: \"export const DEPOSIT = 50;\",\n replace: \"export const DEPOSIT = 50;\\n\\nexport async function markDepositPaid(contactId: string) {\\n return fetch(`https://services.leadconnectorhq.com/contacts/${contactId}/tags`, { method: \\\"POST\\\" });\\n}\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H22 the module cannot write\",\n },\n {\n name: \"the parser goes back to knowing only one of the two Square note formats\",\n file: \"engine/holiday-deposits.ts\",\n // The version that shipped first. A customer whose only Square evidence is a backfill note\n // reads as \"no payment found\" and goes on the shortlist. Found live on 6 Aug.\n find: \" for (const m of body.matchAll(MATCHED))\",\n replace: \" if (false) for (const m of body.matchAll(MATCHED))\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H23 the backfill note format is money\",\n },\n {\n name: \"the same $35 under two payment ids gets added up to $70\",\n file: \"engine/holiday-deposits.ts\",\n // Over-counting is the quiet failure: it takes a real customer OFF the shortlist, so nobody\n // ever looks at them again.\n // [was: aimed at the one-for-one matcher, which was replaced by an idempotent amount check.]\n find: \" if (p.kind === \\\"matched\\\" && directAmounts.has(p.amount)) { collapsed++; continue; }\",\n replace: \" if (false) { collapsed++; continue; }\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H25 the same $35 under two ids\",\n },\n {\n name: \"only one of her CRM's two spellings of the status field is read\",\n file: \"engine/holiday-deposits.ts\",\n // Her account returns `appoinmentStatus` on 4 of 13 events alongside the correct key. They\n // agree today. The day they do not, a cancelled customer gets chased for a deposit.\n find: \" const states = [e.appointmentStatus, e.appoinmentStatus].map((s) => String(s ?? \\\"\\\").trim().toLowerCase());\",\n replace: \" const states = [e.appointmentStatus].map((s) => String(s ?? \\\"\\\").trim().toLowerCase());\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H28 her CRM's two spellings\",\n },\n\n // ---- the collector: the only part of the deposit feature that touches her CRM ---------------\n {\n name: \"the deposit job reads one boarding calendar instead of both\",\n file: \"engine/deposits.ts\",\n // A real customer has bookings on BOTH. Reading one silently halves the list, and a short\n // list looks exactly like a quiet holiday season.\n find: `export const BOARDING_CALENDARS = [\"wS5N8WN4BbzznaLjEg1N\", \"ZmmjQJszkRMUltfEbumB\"];`,\n replace: `export const BOARDING_CALENDARS = [\"wS5N8WN4BbzznaLjEg1N\"];`,\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D1 both drop-off calendars are asked\",\n },\n {\n name: \"a notes read that fails is recorded as 'no payments found'\",\n file: \"engine/deposits.ts\",\n // One character. It turns every network hiccup into a customer on Kim's chase list.\n find: \" } catch { pays = null; }\",\n replace: \" } catch { pays = []; }\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D6 a notes read that fails\",\n },\n {\n name: \"a CRM outage overwrites last night's real list with an empty one\",\n file: \"engine/deposits.ts\",\n // [was: aimed at the guard while it lived inside the HTTP handler. Extracting runCollection()\n // so the scheduled run and the manual run share one code path moved the line, and this\n // control reported itself blind on the next full pass rather than passing on nothing.]\n find: ` if (out.calendarsRead === 0) return { store: false, error: \"no calendar answered, so the stored list was left alone\" };`,\n replace: ` if (false) return { store: false };`,\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D31 every one of the four storage refusals\",\n },\n\n // ---- the card Kim actually reads -----------------------------------------------------------\n {\n name: \"a customer's name goes onto Kim's page without being escaped\",\n file: \"engine/dashboard.ts\",\n find: \"`${esc(r.name)}\",\n replace: \"`${r.name}\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.7 a customer's name is escaped\",\n },\n {\n name: \"a failed read of the deposit list renders as 'nothing collected yet'\",\n file: \"engine/dashboard.ts\",\n // The two states look almost the same on screen and mean opposite things: one is \"we have not\n // looked\", the other is \"we looked and could not see\". Collapsing them is how a page lies.\n find: \" if (!readOk) {\",\n replace: \" if (false) {\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.1 a failed read of the list\",\n },\n {\n name: \"the deposit list stops putting the jobs to do at the top\",\n file: \"engine/dashboard.ts\",\n find: \" const rows = [...(dep.rows ?? [])].sort((a, b) => (order[a.state] - order[b.state]) || a.day.localeCompare(b.day));\",\n replace: \" const rows = [...(dep.rows ?? [])];\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.3 the jobs to do come first\",\n },\n {\n name: \"the list is 'held back' in words while the names stay on the page\",\n file: \"engine/dashboard.ts\",\n find: \"${dep.feedDead ? \\\"\\\" : rows.length ?\",\n replace: \"${true ? \\\"\\\" : \\\"\\\"}${rows.length ?\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.9 when the payment feed is called dead\",\n },\n {\n name: \"two quiet customers are enough to declare Square broken\",\n file: \"engine/holiday-deposits.ts\",\n // Found by watching the first live run rather than by reading the code: the switch fired on a\n // sample of two and would have told Kim her payment feed had stopped.\n // [was: aimed at the parameter name `allPayments`, which changed when the switch started\n // being handed a per-customer Map instead of an array of arrays.]\n find: \" return lists.length >= minSample && lists.every((p) => p.length === 0);\",\n replace: \" return lists.length > 0 && lists.every((p) => p.length === 0);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H19b two quiet customers\",\n },\n\n // ---- everything the adversarial pass of 6 Aug turned up ------------------------------------\n {\n name: \"the Thanksgiving window goes back to arithmetic on the day number\",\n file: \"engine/holiday-deposits.ts\",\n // Produces \"2030-11-31\", a date that does not exist, and prints it to Kim as \"Nov 31\".\n find: \" { name: \\\"Thanksgiving\\\", from: shiftDays(t, -3), to: shiftDays(t, 3) },\",\n replace: \" { name: \\\"Thanksgiving\\\", from: `${year}-11-${String(Number(t.slice(8)) - 3).padStart(2, \\\"0\\\")}`, to: `${year}-11-${String(Number(t.slice(8)) + 3).padStart(2, \\\"0\\\")}` },\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H30 every Thanksgiving window\",\n },\n {\n name: \"an appointment time sent as a number silently drops every stay\",\n file: \"engine/holiday-deposits.ts\",\n find: \" if (typeof startTime === \\\"number\\\" && Number.isFinite(startTime)) {\",\n replace: \" if (false) {\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H31 an appointment time sent as a number\",\n },\n {\n name: \"one trailing space on a status makes a cancelled booking chaseable\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const states = [e.appointmentStatus, e.appoinmentStatus].map((s) => String(s ?? \\\"\\\").trim().toLowerCase());\",\n replace: \" const states = [e.appointmentStatus, e.appoinmentStatus].map((s) => String(s ?? \\\"\\\").toLowerCase());\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H32 her CRM's sloppier shapes\",\n },\n {\n name: \"the payment parser goes back to one payment per note\",\n file: \"engine/holiday-deposits.ts\",\n find: \" for (const m of body.matchAll(DIRECT)) add(Number(m[1].replace(/,/g, \\\"\\\")), m[2], n?.dateAdded ?? null, \\\"direct\\\");\",\n replace: \" const one = DIRECT.exec(body); DIRECT.lastIndex = 0;\\n if (one) add(Number(one[1].replace(/,/g, \\\"\\\")), one[2], n?.dateAdded ?? null, \\\"direct\\\");\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H33 four ways of writing a payment\",\n },\n {\n name: \"the payments Kim needs in order to judge a row are left off it\",\n file: \"engine/holiday-deposits.ts\",\n // [was: aimed at the deposit-window bounds, which were removed when the module stopped\n // guessing what a payment was for. The half of that guarantee that still lives here is that\n // every payment near the stay is SHOWN, with its date, so Kim can settle a row in a glance.]\n find: \"const listPayments = (ps: Payment[]) =>\",\n replace: \"const listPayments = (ps: Payment[]) => \\\"\\\"; const listPaymentsUnused = (ps: Payment[]) =>\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H34 an unrelated payment months before\",\n },\n {\n name: \"a booking with no date is settled by a payment from years ago\",\n file: \"engine/holiday-deposits.ts\",\n find: \" if (!stay.bookedAt) {\\n return { stay, state: \\\"could_not_check\\\", amountSeen: 0,\",\n replace: \" if (false) {\\n return { stay, state: \\\"could_not_check\\\", amountSeen: 0,\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H35 a booking with no record\",\n },\n {\n name: \"a dog boarded across Christmas is invisible because it arrived on the 19th\",\n file: \"engine/holiday-deposits.ts\",\n // [was: aimed at a line inside the grouping loop. The window decision moved after the loop\n // when pick-ups started being attached before it, and this control reported itself blind.]\n find: \" const win = windowForRange(s.day, s.until, windows);\",\n replace: \" const win = windowFor(s.day, windows);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H36 a stay that starts before the window\",\n },\n {\n name: \"a 200 with no notes list reads as 'no payment found'\",\n file: \"engine/deposits.ts\",\n find: \" pays = notes === null ? null : parseSquarePayments(notes);\",\n replace: \" pays = parseSquarePayments(notes ?? []);\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D13 a 200 with no notes list\",\n },\n {\n name: \"a 200 with no events list counts as a calendar successfully read\",\n file: \"engine/deposits.ts\",\n find: \" if (!Array.isArray(d?.events)) throw new Error(\\\"no events array in the response\\\");\\n for (const e of d.events) events.push(e as CalEvent);\",\n replace: \" for (const e of d?.events ?? []) events.push(e as CalEvent);\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D14 a 200 with no events list\",\n },\n {\n name: \"a query string is sent to the notes endpoint, which rejects every one of them\",\n file: \"engine/deposits.ts\",\n // [was: aimed at a paging loop that never worked. Her CRM 422s on any parameter here, so the\n // loop turned every customer into a failed read. It shipped and was caught live in 90\n // seconds; the control now guards the URL rather than the loop that should never have existed.]\n find: \" const d = await io.get(`/contacts/${contactId}/notes`, \\\"2021-07-28\\\");\",\n replace: \" const d = await io.get(`/contacts/${contactId}/notes?limit=100`, \\\"2021-07-28\\\");\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D15 the notes endpoint is asked exactly\",\n },\n {\n name: \"a notes list at the cap is treated as complete\",\n file: \"engine/deposits.ts\",\n find: \" if (d.notes.length >= NOTES_UNPAGEABLE_CAP) return null;\",\n replace: \" if (false) return null;\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D16 a notes list at the cap\",\n },\n {\n name: \"the dead-feed switch goes back to comparing whole payment histories\",\n file: \"engine/deposits.ts\",\n // Restores the version where any customer with an old Square note kept the switch quiet, so\n // it could only ever fire for people who had never paid by card at all. Inert, and green.\n // [was: `perContact.push(paymentsForStay(...))`, retargeted when the switch moved to a\n // per-customer Map and the window function was renamed.]\n find: \" const near = own.filter((s) => s.bookedAt).flatMap((s) => paymentsNearStay(s, pays!));\",\n replace: \" const near = pays;\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D18 five quiet customers with old payments\",\n },\n {\n name: \"an old deposit list is presented as if it were checked today\",\n file: \"engine/dashboard.ts\",\n // Every row is written in the present tense. A four-day-old list still says \"no Square\n // payment is on file\" about somebody who paid yesterday.\n find: \" const stale = Number.isFinite(ageH) && ageH > 36\",\n replace: \" const stale = false && Number.isFinite(ageH) && ageH > 36\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.11 a list old enough to be wrong\",\n },\n {\n name: \"the length of a stay is read off the ten-minute handover slot instead of the pick-up\",\n file: \"engine/holiday-deposits.ts\",\n // A drop-off appointment runs 12:50 to 13:00. Its endTime is the end of the handover, not the\n // end of the boarding, so judging a stay by it makes everyone who leaves before the holiday\n // starts invisible.\n find: \" const withEnds = attachPickups([...by.values()], pickups);\",\n replace: \" const withEnds = [...by.values()];\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D19 a stay that boards over Christmas\",\n },\n {\n name: \"the pick-up calendars stop being read at all\",\n file: \"engine/deposits.ts\",\n find: `export const PICKUP_CALENDARS = [\"1FnbK7pQp1ViZWIzX9SR\", \"bN6wWGJa0qKq0QGRg4CC\"];`,\n replace: `export const PICKUP_CALENDARS: string[] = [];`,\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D1 both drop-off calendars are asked\",\n },\n {\n name: \"a contact that looks like a test record is presented as a customer to chase\",\n file: \"engine/dashboard.ts\",\n find: \"${looksLikeTestRecord(r.name) ?\",\n replace: \"${false ?\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.13 a booking that looks like somebody testing\",\n },\n {\n name: \"a multi-night stay is shown as a single day\",\n file: \"engine/dashboard.ts\",\n find: \" const stayDates = (r: DepositRow) => r.until && r.until > r.day\",\n replace: \" const stayDates = (r: DepositRow) => false && r.until && r.until > r.day\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.10 a multi-night stay shows both ends\",\n },\n {\n name: \"any payment big enough clears the deposit, whatever it was actually for\",\n file: \"engine/holiday-deposits.ts\",\n // Restores the guess that cost her money twice: a $355 training package or a $240 invoice\n // marks the stay settled and the customer is never looked at again.\n find: \" const exact = near.filter((p) => p.amount === DEPOSIT);\",\n replace: \" const exact = near.filter((p) => p.amount >= DEPOSIT);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H14 a card payment for exactly the deposit\",\n },\n {\n name: \"the earliest pick-up ends a stay, so one dog going home early deletes it\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const cand = cands.length ? cands[cands.length - 1] : null;\",\n replace: \" const cand = cands.length ? cands[0] : null;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H41 the LATEST pick-up ends a stay\",\n },\n {\n name: \"a stay reaches forward and takes the next booking's pick-up\",\n file: \"engine/holiday-deposits.ts\",\n // [was: aimed at the pre-bound filter line. Retargeted onto the next-booking bound itself.]\n find: \" && (!nextDrop || d <= nextDrop));\",\n replace: \");\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H42 a stay never reaches forward\",\n },\n {\n name: \"a cancelled pick-up is allowed to stretch a stay into a holiday window\",\n file: \"engine/holiday-deposits.ts\",\n find: \" for (const p of pickups) {\\n if (!eligible(p)) continue;\",\n replace: \" for (const p of pickups) {\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H43 a cancelled or recurring pick-up\",\n },\n {\n name: \"a real boarding booking is thrown away for having the word daycare in its title\",\n file: \"engine/holiday-deposits.ts\",\n find: \" if (/\\\\bday\\\\s?care\\\\b/i.test(title) && !/\\\\bboarding\\\\b/i.test(title)) return false;\",\n replace: \" if (/\\\\bday\\\\s?care\\\\b/i.test(title)) return false;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H44 a real boarding booking\",\n },\n {\n name: \"a customer whose surname is Tester is labelled a test record on Kim's screen\",\n file: \"engine/holiday-deposits.ts\",\n find: \" return /\\\\b(test|testing|dummy|zztest|do not use|ignore)\\\\b/i.test(String(name ?? \\\"\\\"));\",\n replace: \" return /\\\\b(test|testing|tester|dummy|zztest|do not use|ignore)\\\\b/i.test(String(name ?? \\\"\\\"));\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H45 the test-record label\",\n },\n {\n name: \"the dead-feed sentence goes back to claiming it checked nobody\",\n file: \"engine/holiday-deposits.ts\",\n find: \" if (checked <= 0) {\",\n replace: \" if (false) {\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H46 the dead-feed sentence\",\n },\n {\n name: \"the kill switch counts bookings again, so one regular can suppress the whole card\",\n file: \"engine/deposits.ts\",\n // [was: aimed at the per-stay loop, which became a per-customer loop. The fault it injects\n // now is the same one in the new shape: one sample entry per BOOKING.]\n find: \" perCustomer.set(contactId, near);\",\n replace: \" for (const s of own) perCustomer.set(`${contactId}|${s.day}`, s.bookedAt ? paymentsNearStay(s, pays!) : []);\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D20 one regular with five holiday bookings\",\n },\n {\n name: \"the unknown count on the card counts customers while the table counts rows\",\n file: \"engine/dashboard.ts\",\n find: \" const unknownRows = rows.filter((r) => r.state === \\\"could_not_check\\\").length;\",\n replace: \" const unknownRows = dep.readFailures;\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.14 the unknown count on the card\",\n },\n {\n name: \"a pick-up calendar that did not answer is not mentioned to Kim at all\",\n file: \"engine/dashboard.ts\",\n find: \" const noPickups = (dep.pickupsAsked ?? 0) && (dep.pickupsRead ?? 0) < (dep.pickupsAsked ?? 0)\",\n replace: \" const noPickups = false && (dep.pickupsAsked ?? 0) && (dep.pickupsRead ?? 0) < (dep.pickupsAsked ?? 0)\",\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.15 a pick-up calendar that did not answer\",\n },\n {\n name: \"one $50 payment settles every holiday stay that customer has\",\n file: \"engine/holiday-deposits.ts\",\n // The most expensive bug of the day: a regular books Thanksgiving and Christmas in one call,\n // pays one deposit, and both rows go green. Kim is owed $100 and sees nothing to chase.\n find: \" if (claimed) spent.add(claimed.id);\",\n replace: \" if (claimed) { /* spent nothing */ }\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H48 one $50 deposit settles ONE stay\",\n },\n {\n name: \"the search window stretches past the stay, so any later payment settles it\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const hi = shiftDays(stay.until || stay.day, 1);\",\n replace: \" const hi = shiftDays(stay.until || stay.day, 365);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H49 a payment after the dogs go home\",\n },\n {\n name: \"a stay of any length is accepted, so an orphan pick-up drags a boarding into a holiday\",\n file: \"engine/holiday-deposits.ts\",\n find: \" d >= s.day && d <= shiftDays(s.day, MAX_STAY_DAYS) && (!nextDrop || d <= nextDrop));\",\n replace: \" d >= s.day && (!nextDrop || d <= nextDrop));\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H42 a stay never reaches forward\",\n },\n {\n name: \"a pick-up on the same day as the next booking deletes the stay it ends\",\n file: \"engine/holiday-deposits.ts\",\n find: \"(!nextDrop || d <= nextDrop));\",\n replace: \"(!nextDrop || d < nextDrop));\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D23 collecting one dog and boarding another\",\n },\n {\n name: \"the note about a single payment goes back to plural grammar\",\n file: \"engine/holiday-deposits.ts\",\n find: \" note: near.length === 1\",\n replace: \" note: false\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H50 a lone payment that is not the deposit\",\n },\n {\n name: \"the headline stops counting the rows that have some card activity\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const n = none + partial;\",\n replace: \" const n = none;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H51 the headline counts every row\",\n },\n {\n name: \"a row with card activity but no $50 is coloured green and called settled\",\n file: \"engine/dashboard.ts\",\n find: ' partial: { label: \"Worth a look\", color: WARN },',\n replace: ' partial: { label: \"Payment on file\", color: GOOD },',\n once: true,\n suite: \"dashboard.test.mjs\",\n mustFail: \"D5.16 a row with card activity\",\n },\n {\n name: \"a run where nobody could be read overwrites yesterday's real shortlist\",\n file: \"engine/deposits.ts\",\n find: ' if (out.rows.length > 0 && out.rows.every((r) => r.state === \"could_not_check\")) {',\n replace: \" if (false) {\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D21 a run where nobody's payments\",\n },\n {\n name: \"a booking with no date counts as a customer we checked and saw no money for\",\n file: \"engine/deposits.ts\",\n find: \" if (pays !== null && own.some((s) => s.bookedAt)) {\",\n replace: \" if (pays !== null) {\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D22 a booking with no date\",\n },\n {\n name: \"a deposit Square wrote twice settles two different stays\",\n file: \"engine/holiday-deposits.ts\",\n // The money bug re-entering through the collapse/allocate seam. Restores the version where\n // statusFor collapsed internally and the allocator only ever spent the surviving id.\n find: \" const money = collapseSameMoney(payments).kept;\",\n replace: \" const money = payments;\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H52 a deposit Square wrote twice\",\n },\n {\n name: \"the money goes to whichever stay happens to be first in the array\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const ordered = [...stays].sort((a, b) => a.day.localeCompare(b.day));\",\n replace: \" const ordered = [...stays];\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H53 the money goes to the stay that came first\",\n },\n {\n name: \"the same $35 in both of Square's note formats is read as $70\",\n file: \"engine/holiday-deposits.ts\",\n // [was: not covered at all. H27 used a $50 pair, where amountSeen is the constant DEPOSIT and\n // the other-payments list is defined as everything that is NOT $50, so it could not fail.]\n find: \" const near = collapseSameMoney(paymentsNearStay(stay, payments)).kept;\",\n replace: \" const near = paymentsNearStay(stay, payments);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H27 the same $50 under two ids\",\n },\n {\n name: \"the season rolls over on Greenwich time, five hours early on 2 January\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const p = new Intl.DateTimeFormat(\\\"en-CA\\\", { timeZone: BUSINESS_TZ, year: \\\"numeric\\\", month: \\\"2-digit\\\", day: \\\"2-digit\\\" }).format(d);\\n return /^\\\\d{4}-\\\\d{2}-\\\\d{2}$/.test(p) ? p : String(nowIso).slice(0, 10);\",\n replace: \" return String(nowIso).slice(0, 10);\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H54 the season turns over on her clock\",\n },\n {\n name: \"other money on a settled row stops being shown\",\n file: \"engine/holiday-deposits.ts\",\n find: \" const restNote = rest.length\",\n replace: \" const restNote = false && rest.length\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H55 money on a settled row\",\n },\n {\n name: \"the drop-off query stops at the window edge, blinding the next-booking bound\",\n file: \"engine/deposits.ts\",\n find: \"&endTime=${dayMs(shiftDays(to, LOOKAHEAD_DAYS))}`;\\n const d = await io.get(`/calendars/events?${q}`, \\\"2021-04-15\\\");\\n // A 200 that does not carry an events ARRAY\",\n replace: \"&endTime=${dayMs(to) + 86_399_000}`;\\n const d = await io.get(`/calendars/events?${q}`, \\\"2021-04-15\\\");\\n // A 200 that does not carry an events ARRAY\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D24 the collector asks for the period\",\n },\n {\n name: \"the collector stops looking before the window for stays that run into it\",\n file: \"engine/deposits.ts\",\n find: \"export const LOOKBACK_DAYS = 21;\",\n replace: \"export const LOOKBACK_DAYS = 0;\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D24 the collector asks for the period\",\n },\n {\n name: \"a renamed calendar's empty answer overwrites the real shortlist\",\n file: \"engine/deposits.ts\",\n find: \" if (!force && out.rows.length === 0 && (prev?.rows?.length ?? 0) > 0) {\",\n replace: \" if (false) {\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D26 a season that empties to nothing\",\n },\n {\n name: \"the collector stops allocating per customer and goes back to stay by stay\",\n file: \"engine/deposits.ts\",\n // The whole money bug, back end to end, in one line — and until D27 existed the entire suite\n // stayed green through it because H48 only ever tested the pure function.\n find: \" for (const st of statusesForCustomer(own, pays)) {\",\n replace: \" for (const st of own.map((s0) => statusFor(s0, pays))) {\",\n then: {\n find: \" depositSentence, paymentsNearStay, statusesForCustomer, shiftDays, businessDay,\",\n replace: \" depositSentence, paymentsNearStay, statusesForCustomer, statusFor, shiftDays, businessDay,\",\n },\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D27 the collector really does allocate\",\n },\n {\n name: \"force=1 is quietly disconnected, so an empty season can never be accepted\",\n file: \"engine/deposits.ts\",\n find: ' const r = await runCollection(url.searchParams.get(\"force\") === \"1\");',\n replace: \" const r = await runCollection();\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D28 a genuinely empty season\",\n },\n {\n name: \"the storage guards are deleted but a comment is left quoting them\",\n file: \"engine/deposits.ts\",\n // THE PROSE-MATCHING TRAP, which this project has now shipped four times. A structural check\n // that reads the raw file passes on the author's own explanation of the bug they removed.\n find: ' if (!force && out.rows.length === 0 && (prev?.rows?.length ?? 0) > 0) {',\n replace: ' // [was: if (!force && out.rows.length === 0 && (prev?.rows?.length ?? 0) > 0) { ... }]\\n if (false) {',\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D26 a season that empties to nothing\",\n },\n {\n name: \"the deposit refresh is dropped from the engine's schedule\",\n file: \"engine/puppy_path_v1.1.ts\",\n // The list then only ever refreshes when somebody hits the endpoint by hand, and the page goes\n // quietly stale while still reading in the present tense.\n find: \" if (dep.needsRefresh(last?.at, Date.now())) await dep.runCollection();\",\n replace: \" // refresh removed\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D30 the engine calls that rule\",\n },\n {\n name: \"the gate reads the stored list instead of the attempt stamp, so a sick CRM is retried every tick\",\n file: \"engine/puppy_path_v1.1.ts\",\n find: \" const last: any = await blob.getJSON(dep.ATTEMPT_KEY).catch(() => null);\",\n replace: \" const last: any = await blob.getJSON(\\\"holiday_deposits\\\").catch(() => null);\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D30 the engine calls that rule\",\n },\n {\n name: \"the refresh gate flips, so the list stops refreshing after the first hour\",\n file: \"engine/deposits.ts\",\n find: \" return nowMs - t > everyMs;\",\n replace: \" return nowMs - t < everyMs;\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D29 the refresh gate is a rule\",\n },\n {\n name: \"an unreadable refresh stamp closes the gate forever\",\n file: \"engine/deposits.ts\",\n find: \" if (!Number.isFinite(t)) return true;\",\n replace: \" if (!Number.isFinite(t)) return false;\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D29 the refresh gate is a rule\",\n },\n {\n name: \"the refresh interval is multiplied by a thousand, so it effectively never runs\",\n file: \"engine/deposits.ts\",\n find: \"export const REFRESH_EVERY_MS = 3_600_000;\",\n replace: \"export const REFRESH_EVERY_MS = 3_600_000_000;\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D29 the refresh gate is a rule\",\n },\n {\n name: \"a genuinely empty season can never be accepted, even on purpose\",\n file: \"engine/deposits.ts\",\n find: \" if (!force && out.rows.length === 0 && (prev?.rows?.length ?? 0) > 0) {\",\n replace: \" if (out.rows.length === 0 && (prev?.rows?.length ?? 0) > 0) {\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D31 every one of the four storage refusals\",\n },\n {\n name: \"the very first collection of an empty season is refused, so the card never fills in\",\n file: \"engine/deposits.ts\",\n find: \"(prev?.rows?.length ?? 0) > 0) {\",\n replace: \"(prev?.rows?.length ?? 0) >= 0) {\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D31 every one of the four storage refusals\",\n },\n {\n name: \"the collector reads the season on Greenwich time again\",\n file: \"engine/deposits.ts\",\n find: \" const season = seasonYear(businessDay(todayIso));\",\n replace: \" const season = seasonYear(todayIso.slice(0, 10));\",\n once: true,\n suite: \"deposits-collect.test.mjs\",\n mustFail: \"D32 the collector reads the season\",\n },\n {\n name: \"one matched record of two is left behind, and settles a second stay\",\n file: \"engine/holiday-deposits.ts\",\n // The one-for-one collapse: with two backfill records and one direct payment the survivor\n // still shares an amount with the direct, gets folded AGAIN by the per-stay check, and the\n // allocator never spends it.\n find: \" if (p.kind === \\\"matched\\\" && directAmounts.has(p.amount)) { collapsed++; continue; }\",\n replace: \" if (p.kind === \\\"matched\\\" && directAmounts.has(p.amount)) { directAmounts.delete(p.amount); collapsed++; continue; }\",\n once: true,\n suite: \"holiday-deposits.test.mjs\",\n mustFail: \"H57 two backfill records and one payment\",\n },\n];\n\n// ---------------------------------------------------------------------------------------------\nconst log = (s = \"\") => console.log(s);\nlet pass = 0, fail = 0;\nconst failures = [];\n\nfunction runControl(c, i) {\n const tmp = mkdtempSync(join(tmpdir(), \"nc-\"));\n try {\n // handover/ comes too: the cross-artifact controls patch the documents Kim actually reads,\n // and that suite resolves them relative to its working directory.\n for (const d of [\"engine\", \"tests\", \"handover\"]) cpSync(join(ROOT, d), join(tmp, d), { recursive: true });\n\n const target = join(tmp, c.file);\n if (!existsSync(target)) return bad(c, `the file it patches does not exist: ${c.file}`);\n\n let src = readFileSync(target, \"utf8\");\n const applyOne = (find, replace) => {\n const at = src.indexOf(find);\n if (at === -1) return false;\n src = src.slice(0, at) + replace + src.slice(at + find.length);\n return true;\n };\n // A control whose injection does not apply is a BROKEN CONTROL, not a pass. This is the\n // failure mode that produced three fake checks: the pattern matched nothing and everyone\n // read the green.\n if (!applyOne(c.find, c.replace)) return bad(c, `injection matched NOTHING in ${c.file}: this control is blind`);\n if (c.then && !applyOne(c.then.find, c.then.replace)) return bad(c, `the follow-up injection matched nothing`);\n writeFileSync(target, src);\n\n // Rebuild the patched tree.\n const b = spawnSync(\"node\", [join(ROOT, \"scripts/build.mjs\"), \"--src\", join(tmp, \"engine\"), \"--out\", join(tmp, \"build\")],\n { encoding: \"utf8\", timeout: 180_000 });\n if (b.status !== 0) return bad(c, `the patched tree would not build, so the suite never ran:\\n${(b.stdout + b.stderr).trim().slice(0, 400)}`);\n\n // Run the one suite that owns this guarantee.\n const isTs = c.suite.endsWith(\".ts\");\n const r = spawnSync(isTs ? \"npx\" : \"node\", isTs ? [\"--yes\", \"tsx\", join(tmp, \"tests\", c.suite)] : [join(tmp, \"tests\", c.suite)],\n { encoding: \"utf8\", cwd: tmp, timeout: 180_000 });\n const out = `${r.stdout ?? \"\"}${r.stderr ?? \"\"}`;\n\n // An INVERTED control: the injection is something the check must NOT react to. A structural\n // check that reads code has to stay green when the forbidden text appears only in a comment;\n // if it goes red, it is matching prose and every green it has ever given is worthless.\n if (c.mustStayGreen) {\n if (r.status !== 0) {\n const red = out.split(\"\\n\").filter((l) => l.startsWith(\"FAIL\")).join(\" \").slice(0, 300);\n return bad(c, `the suite went RED on text that appears only inside a comment: it is matching prose, not code.\\n ${red}`);\n }\n pass++;\n log(`PASS control ${i + 1}: ${c.name}`);\n log(` -> ${c.suite} stayed green, so it is reading code rather than comments`);\n return true;\n }\n\n if (r.status === 0) return bad(c, `THE SUITE STAYED GREEN with the fault injected. ${c.suite} cannot catch this.`);\n\n // Red is necessary but not sufficient. The NAMED test must be the one that went red.\n const redLines = out.split(\"\\n\").filter((l) => l.startsWith(\"FAIL\"));\n if (!redLines.length) return bad(c, `the suite exited non-zero but printed no FAIL line: it crashed rather than caught anything.\\n${out.trim().slice(0, 300)}`);\n if (!redLines.some((l) => l.includes(c.mustFail))) {\n return bad(c, `red, but on the wrong test. Expected \"${c.mustFail}\", got:\\n ${redLines.join(\"\\n \").slice(0, 400)}`);\n }\n\n pass++;\n log(`PASS control ${i + 1}: ${c.name}`);\n log(` -> ${c.suite} went red on \"${c.mustFail}\"`);\n return true;\n } finally {\n rmSync(tmp, { recursive: true, force: true });\n }\n}\n\nfunction bad(c, why) {\n fail++;\n failures.push(`${c.name}\\n ${why}`);\n log(`FAIL control: ${c.name}`);\n log(` ${why.split(\"\\n\").join(\"\\n \")}`);\n return false;\n}\n\n// `--only ` runs a subset while iterating on one module. It is DELIBERATELY loud:\n// a filtered green is not a green, and the banner says so on the way in and on the way out, so\n// nobody can paste a partial run into a report and call the suite clean.\nconst onlyIx = process.argv.indexOf(\"--only\");\nconst ONLY = onlyIx > -1 ? process.argv[onlyIx + 1] : null;\nconst SELECTED = ONLY ? CONTROLS.filter((c) => c.name.includes(ONLY) || c.file.includes(ONLY) || c.suite.includes(ONLY)) : CONTROLS;\nif (ONLY && !SELECTED.length) {\n log(`--only \"${ONLY}\" matched none of the ${CONTROLS.length} controls. Refusing to report a green on zero work.`);\n process.exit(1);\n}\n\nif (ONLY) log(`\\n*** FILTERED RUN: ${SELECTED.length} of ${CONTROLS.length} controls (\"${ONLY}\"). THIS IS NOT A FULL PASS. ***`);\nlog(`\\nNEGATIVE CONTROLS — injecting ${SELECTED.length} faults, one at a time.\\n`);\nSELECTED.forEach(runControl);\n\nlog(`\\n=== RESULT: ${pass} passed, ${fail} failed ===`);\nif (ONLY) log(`*** FILTERED RUN: ${CONTROLS.length - SELECTED.length} controls were not run. This does not clear the suite. ***`);\nif (fail) {\n log(`\\n${fail} guarantee(s) are not actually guarded. A green suite means nothing for these:`);\n for (const f of failures) log(` - ${f}`);\n}\nprocess.exit(fail ? 1 : 0);\n\n\n\n=====FILE tests/registry.test.mjs =====\n// WATCHING A LIST SOMEBODY ELSE CONTROLS.\n// The watchdog has watched Kim's 165 automations since 4 August and has never once been seen to\n// fire, because firing requires somebody to change something. That is the definition of a check\n// nobody has verified. The comparison lives on its own now so it can be exercised directly, and\n// every case below is a way the watch could quietly stop working.\nimport * as R from \"../build/registry-diff.js\";\nimport { suite, ok, eq, scoped } from \"./_harness.mjs\";\nconst { t, done } = suite(\"registry\");\n\nconst KB_BEFORE = {\n XOsEp: \"UPDATED - CONSOLIDATED [THE DOGS SPOT] @2026-08-05T02:38\",\n ZkVFb: \"Chloe - Boarding @2026-07-31T12:47\",\n roL2d: \"Ava Knowledgebase @2026-08-03T03:34\",\n};\n\nt(\"G1 an edit in place is caught, which is the case the whole watch exists for\", () => {\n // Same id, same name, new timestamp. Nothing is added and nothing is removed, so a check that\n // only counted entries would see nothing at all — and this is exactly what happened to the\n // consolidated knowledge base at 02:38 on 5 August.\n const after = { ...KB_BEFORE, XOsEp: \"UPDATED - CONSOLIDATED [THE DOGS SPOT] @2026-08-05T09:12\" };\n const c = R.registryDiff(KB_BEFORE, after);\n ok(c.changed, \"an in-place edit was not noticed\");\n eq(c.added, []);\n eq(c.removed, []);\n eq(c.edited.length, 1);\n ok(/02:38 -> .*09:12/.test(c.edited[0]), `the change does not show what moved: ${c.edited[0]}`);\n return scoped(5, \"assertions\");\n});\n\nt(\"G2 additions and removals are told apart, and named\", () => {\n const added = R.registryDiff(KB_BEFORE, { ...KB_BEFORE, newId: \"Brand New KB @2026-08-06T00:00\" });\n eq(added.added, [\"Brand New KB @2026-08-06T00:00\"]);\n eq(added.removed, []);\n const { ZkVFb, ...minusOne } = KB_BEFORE;\n const removed = R.registryDiff(KB_BEFORE, minusOne);\n eq(removed.removed, [\"Chloe - Boarding @2026-07-31T12:47\"]);\n eq(removed.added, []);\n ok(removed.changed && added.changed);\n return scoped(5, \"assertions\");\n});\n\nt(\"G3 an unchanged registry is silent, so the alarm does not cry wolf every pass\", () => {\n const c = R.registryDiff(KB_BEFORE, { ...KB_BEFORE });\n eq(c.changed, false, \"an identical registry reported a change\");\n eq([...c.added, ...c.removed, ...c.edited], []);\n // key ORDER must not matter: the CRM does not promise one\n const shuffled = Object.fromEntries(Object.entries(KB_BEFORE).reverse());\n eq(R.registryDiff(KB_BEFORE, shuffled).changed, false, \"a reordered list reads as a change\");\n return scoped(3, \"assertions\");\n});\n\nt(\"G4 a first run has no baseline and must not report the whole world as new\", () => {\n // The very first pass writes a baseline. If it also alarmed, every deploy would page somebody.\n const c = R.registryDiff(null, KB_BEFORE);\n eq(c.added.length, 3, \"a first run should still be able to describe what it found\");\n eq(c.removed, []);\n eq(c.edited, []);\n // and the watchdog only alarms when prev exists, which is the caller's job — proven in G6\n return scoped(3, \"assertions\");\n});\n\nt(\"G5 garbage in does not throw and does not invent a change\", () => {\n for (const junk of [null, undefined, \"not an object\", 42, []]) {\n const c = R.registryDiff(junk, junk);\n eq(c.changed, false, `${JSON.stringify(junk)} produced a change out of nothing`);\n }\n eq(R.registryDiff(KB_BEFORE, null).removed.length, 3, \"a null 'now' should read as everything gone, for the caller to judge\");\n return scoped(6, \"shapes\");\n});\n\nt(\"G6 an empty list on a good response is treated as a glitch, not as a deletion\", () => {\n // The rule the workflow watch learned the hard way: overwriting a baseline with an empty list\n // fires \"everything removed\" this pass and \"everything added\" the next.\n ok(R.looksLikeAGlitch(0, 8), \"an empty response after a healthy one is being believed\");\n ok(!R.looksLikeAGlitch(0, 0), \"a genuinely empty account is being called a glitch forever\");\n ok(!R.looksLikeAGlitch(8, 8), \"a normal response is being called a glitch\");\n ok(!R.looksLikeAGlitch(3, 8), \"a partial response is being called a glitch: it is a real change\");\n ok(!R.looksLikeAGlitch(0, null), \"a missing baseline is being called a glitch\");\n return scoped(5, \"cases\");\n});\n\nt(\"G7 the sentence is generated from the change and says how much it left out\", () => {\n const many = {};\n for (let i = 0; i < 9; i++) many[`id${i}`] = `Thing ${i} @2026-08-06T00:00`;\n const c = R.registryDiff({}, many);\n const line = R.registrySentence(c, \"her knowledge bases\");\n ok(/Added: Thing 0/.test(line), \"the sentence does not name what changed\");\n ok(/6 more not listed here/.test(line), `the sentence hides how much it truncated: ${line}`);\n const quiet = R.registrySentence(R.registryDiff(KB_BEFORE, KB_BEFORE), \"her automations\");\n ok(/Nothing has moved in her automations/.test(quiet), quiet);\n ok(!/undefined|NaN|\\[object/.test(line + quiet), \"a stray value reached the sentence\");\n return scoped(4, \"assertions\");\n});\n\ndone();\n\n\n=====FILE tests/render.test.mjs =====\n// MESSAGE RENDERING — the escape and merge rules, tested directly.\n// Two of these are regressions from a security review: a name containing $-patterns corrupting the\n// body, and contact-typed text reaching the HTML unescaped. Both shipped once.\nimport * as R from \"../build/render.js\";\nimport { suite, ok, eq, scoped } from \"./_harness.mjs\";\nconst { t, done, header } = suite(\"render\");\n\nheader(\"MERGE FIELDS\");\nt(\"M1.1 blank names fall back rather than rendering 'Hi ,'\", () => {\n eq(R.resolveFirstName(\"\"), \"there\"); eq(R.resolveFirstName(null), \"there\"); eq(R.resolveFirstName(\" \"), \"there\");\n eq(R.applyMergeFields(\"Hi {{FIRST_NAME}}!\", \"\", \"\"), \"Hi there!\");\n return scoped(4, \"cases\");\n});\nt(\"M1.2 a name full of $-patterns cannot corrupt the body\", () => {\n // String.replace treats $&, $', $` and $1 as references. With a string replacement a customer\n // named Bo$$ would have injected fragments of the template into their own message.\n const evils = [\"Bo$$\", \"Re$&\", \"$'\", \"$`\", \"$1$2\", \"A$&B\"];\n for (const e of evils) eq(R.applyMergeFields(\"Hi {{FIRST_NAME}}!\", e, \"\"), `Hi ${e}!`, `name ${e} mangled`);\n return scoped(evils.length, \"hostile names\");\n});\nheader(\"HTML ESCAPING\");\nt(\"M2.1 every dangerous character is escaped\", () => {\n eq(R.escHtml(`', note: \"hi\" }] };\n const h = DASH.depositCard(nasty, true, noAgo);\n ok(!/

Segment	Count	Share	What can be done
Has an email	${c.emailable}	${pct(c.emailable, d.total)}	The email release. This is the real audience.
Phone only	${c.phoneOnly}	${pct(c.phoneOnly, d.total)}	SMS — held until numbers are validated. Stale numbers get a business flagged by carriers.
Neither	${c.unreachable}	${pct(c.unreachable, d.total)}	Nothing by email or text. Reachable only inside Messenger, within Meta's window.
Excluded	${c.excluded}	${pct(c.excluded, d.total)}	Already customers, already on a path, flagged spam, or duplicates.

Diff · v295