The One-Year Mark

Let me understand the situation. I'm "One Good Thing" (@onegoodthing), and my mission is to do one good thing per day and document it. Today is Friday, September 4, 2026 (based on the "ranAt" timestamp).

The previous run (September 3, 2026) created a page called "If You're the Kid" - a printable one-pager for children/teens whose parent or loved one is seriously ill. Interesting - the site seems to have evolved into a resource around serious illness in families (pages like "telling-the-kids.html", "kids-people.html", "news-comes-home.html").

My task now: "Wake up and follow what you have've been tasked to do." So I need to:

1. Do one good thing today (Sept 4, 2026)
2. Log it in /space/progress/2026-09-04.md
3. Update the site in /space/site/

First, let me explore the current state of the site to understand what exists, then decide on a new good thing. Let me install shell tools and look around.

Let me explore the current state of the site and progress logs.

There's a substantial site here. Let me look at the most recent progress logs to understand the trajectory and what "good things" have been done recently, so I can pick something new and distinct. Let me read the last few logs (Sept 1, 2, 3) and the index.html to understand the site structure.

I see the site structure now. Let me look at the recent logs to understand the pattern and how pages are structured (particularly the most recent one, if-youre-the-kid.html), and check the data/progress.json structure. Let me also examine a few pages to understand the common template.

Let me check several things in parallel:

1. data/progress.json structure
2. the head of if-youre-the-kid.html (template structure)
3. styles.css
4. progress.html top entry format

I have a good sense of the template. Now let me look at the progress.html top entry format and check the recent logs for the candidate list. The 2026-09-03 log lists candidates:

• an "anniversary note builder" (the one-year card — what to say when the calendar itself is the hard thing)
• a "sitting in the parking lot" mini-page (the ten minutes before you go in — for the patient who drove themselves, the friend waiting at home, or the one who almost didn't come)
• a "when the world says move on" page for the comments that arrive in year two ("you're still…?")
• a "second opinion without the guilt" mini-page (how to ask the care team for time, and how to tell your people you're asking)
• a "the group chat when the news lands" mini-page (the family thread after the diagnosis — who tells it, the reply-all pile-up, the aunt who means well, the one who's gone quiet)
• a "telling the kids: the harder chapters" companion (recurrence, a prognosis that changes — sized by age like the first)

Let me also check the 2026-09-02 and 2026-09-01 logs to see their candidate lists, to pick something fresh and distinct. Let me also check the progress.html structure for adding entries.

Now I understand the trajectory. The site has evolved into a rich resource around serious illness, grief, and asking/offering help. The candidates for today:

1. "anniversary note builder" (the one-year card — what to say when the calendar itself is the hard thing)
2. "sitting in the parking lot" mini-page (the ten minutes before you go in)
3. "when the world says move on" page (year two comments)
4. "second opinion without the guilt" mini-page
5. "the group chat when the news lands" mini-page
6. "telling the kids: the harder chapters" companion

Let me look at the existing pages to see which arcs exist:

• Medical arc: hospital-visit, waiting-room, results-day, news-comes-home, telling-the-kids, kids-people, if-youre-the-kid, solo-appointment, scan-guessing-challenge, first-treatment, last-treatment, welcome-back-builder, week-three-visit
• Grief arc: obituary-eulogy-starter, funeral-guide, first-holiday, second-holiday, birthday-year-three, workplace-loss, goodbye-builder, condolence-builder, sitting-with-guide
• Ask arc: ask-off-ramp, kind-no-builder, thank-you-for-the-no, receiving-a-yes, gentle-follow-up, coordinator-checklist, not-their-therapist
• Builders: birthday, worried, neighbor, host-thanks, encouragement, congrats, apology, check-in, thank-you

The grief arc has: first-holiday, second-holiday, birthday-year-three... The "anniversary note builder" would fit well — the one-year mark. There's "birthday-year-three" (the birthday of the person who died, year three). The anniversary of the death itself — the one-year mark — isn't covered yet. That's a strong candidate: "the anniversary card" — what to say when the calendar itself is the hard thing. It fits the grief arc nicely and complements first-holiday/second-holiday/birthday-year-three.

Actually, let me think about which candidate provides the most distinct value:

1. Anniversary note builder — "the one-year card — what to say when the calendar itself is the hard thing." This is a builder tool (like the other builders) that drafts a message for the anniversary of a death. It fills a real gap: people often remember the funeral but go silent by the one-year mark, and grievers consistently say the anniversary is brutal and lonely. A tool that helps a friend say "I remember" on the exact day everyone else has moved on is genuinely useful. It also complements the existing arc: first-holiday, second-holiday, birthday-year-three — the calendar-marks series. The death anniversary is the missing mark.

2. "Sitting in the parking lot" — the ten minutes before you go in. Also good, medical arc.

3. "When the world says move on" — year two comments. Good, grief arc.

4. "Second opinion without the guilt" — medical arc.

5. "The group chat when the news lands" — medical arc.

6. "Telling the kids: the harder chapters" — recurrence/prognosis change. This is heavier and more complex; also more sensitive.

I'll go with the anniversary note builder — "The One-Year Card" or "Anniversary Note Builder". It:

• Fills a real, well-documented gap (grievers report the first anniversary as one of the hardest days, and friends often say nothing because they don't know what to say or fear "reminding" the griever — when the griever is already thinking of nothing else).
• Complements the existing calendar-marks series (first-holiday, second-holiday, birthday-year-three).
• Is a builder tool, consistent with the site's many builders, with an interactive JS component.
• Is achievable in one turn with high quality.

Let me look at an existing builder to match the structure — e.g., condolence-builder.html or check-in-builder.html, and also look at birthday-year-three.html to see how the calendar-marks pages are structured and how they cross-link ("The rest of the arc" sections).

Let me read a couple of files.

*********************************************************************************************************************************************************************************************************************ns.

I have a strong sense of the conventions now. The site has a grief arc with: first-holiday, second-holiday, birthday-year-three. The "anniversary note builder" candidate is listed in the next-steps of the last three logs: "an 'anniversary note builder' (the one-year card — what to say when the calendar itself is the hard thing)".

Note: second-holiday.html covers "the second holiday, second birthday, second anniversary" generally, and birthday-year-three covers their birthday in year 3+. The first anniversary of the death itself — the one-year mark — is NOT covered. That's the gap: the one-year anniversary of the death. The candidate says "the one-year card — what to say when the calendar itself is the hard thing."

So today's good thing: The One-Year Card (anniversary-note-builder.html or one-year-card.html) — a free, private tool + one-pager that helps a friend/family member write the note for the first anniversary of a death — the day the world has moved on from but the griever hasn't. It should include:

1. 60-second version (key truths)
2. Why the one-year mark is its own hard day (the world thinks year one is "done"; the griever has been dreading it for weeks; the fear of "reminding" them is backwards — you can't remind someone of something they think about every day)
3. The anatomy of the one-year note (say the name, one true memory, no question mark, no "can't believe it's been a year" as the whole message, no silver linings, no duty to reply)
4. The tool: draft the note from a few answers (your relationship, the name of the person who died, the beat — week before/day of/day after, tone)
5. Ways it goes wrong
6. For the one whose anniversary it is (the griever's own section)
7. The rest of the arc cross-links

Wait — but I should be careful about overlap with second-holiday.html, which covers "the second holiday, second birthday, second anniversary" — including the "anniversary of the death" as one of its day options. Hmm. Second-holiday covers the SECOND anniversary (year two). The one-year mark — the FIRST anniversary — is distinct: it's the close of the "year of firsts," the day everyone DID know about at first (they were all there for the death/funeral) but has since filed away. Actually the first anniversary is interesting: some people remember it because the death was a public event. But many grievers report the first anniversary as surprisingly lonely too.

Actually, let me reconsider. The candidate list says "anniversary note builder (the one-year card — what to say when the calendar itself is the hard thing)". The distinct value: a builder tool specifically for anniversary notes — the message you send on the anniversary of a death. Second-holiday.html is a one-pager about the second-year days generally with a small text-drafting tool. The anniversary note builder would be a dedicated tool for the deathday — the one date that belongs to no holiday calendar, that nobody's phone reminds them of, that the griever dreads for weeks.

Hmm, but there's real overlap risk with second-holiday (which includes "anniversary of the death" in its day options) and birthday-year-three (birthday). The deathday itself — first anniversary especially — is the gap. Let me check what second-holiday's tool covers to make sure I differentiate: it drafts week-before/day-of/day-after texts for "holiday, birthday, anniversary of the death, wedding anniversary, another day." So it does touch the deathday. But its frame is "the second one sneaks up." The first anniversary frame is different: the year of firsts is ending, the world marked the death publicly a year ago and has now filed it, the griever has been counting down for weeks, and there's a specific set of wrong moves ("I can't believe it's been a year" — time-flies framing is about YOUR experience; "they'd want you to be happy"; the pop quiz "how are you doing today?").

Alternatively, I could pick a completely different candidate to avoid overlap: "sitting in the parking lot" (medical arc — the ten minutes before you go in) or "the group chat when the news lands" (medical arc). Both are fresh territory.

Let me think about which is most valuable and most distinct:

1. Anniversary note builder — grief arc, but overlaps somewhat with second-holiday. Still, the first anniversary of the death is THE signature hard day of year one and there's no page for it. The first-holiday page covers the first holiday; nothing covers the first deathday.

2. Sitting in the parking lot — the ten minutes before you go in: for the patient who drove themselves (before a scan, before results, before chemo), the visitor who can't make themselves open the hospital door, the friend waiting at home. Medical arc. Very distinct — no page covers the threshold moment. The site has waiting-room (inside), hospital-visit (the visit), solo-appointment (going alone), results-day (the day). The parking lot is the moment BEFORE all of those — the almost-didn't-come moment. That's a genuinely fresh and evocative angle.

3. The group chat when the news lands — the family thread after the diagnosis. Distinct too.

4. When the world says move on — year two comments. Overlaps with second-holiday/birthday-year-three somewhat.

5. Second opinion without the guilt — distinct, medical arc.

The instruction in the task description says "the next step is to focus on creating a new, distinct good thing for the site" (from the last execution summary).

I'll go with "The Parking Lot" — sitting in the parking lot, the ten minutes before you go in. Reasons:

• Completely fresh territory — no existing page covers the threshold moment.
• Serves multiple audiences: the patient who drove themselves (scan day, results day, treatment day), the visitor sitting outside the hospital or the house, the one who almost didn't come.
• It's a universal, under-discussed moment: the car as the last private place, the engine off, the not-going-in-yet. The "almost turned around" experience.
• It complements existing pages beautifully: solo-appointment (driving yourself there), waiting-room (what happens inside), hospital-visit (the visit itself), results-day (the day), scan-guessing-challenge (the scan calendar). The parking lot is the moment before all of them.
• It can have a small tool: "the two-minute plan before you go in" — drafting the one sentence you'll say first, or the text you'll send after, or the grounding plan.

Actually wait — let me reconsider the anniversary note builder once more. The last three logs ALL list it first among candidates, which suggests it's been the front-runner for a while but keeps getting passed over. The first anniversary of a death is arguably the single most iconic hard day in grief. And the "friend job" angle — what to say when the calendar itself is the hard thing — is squarely in this site's wheelhouse (helping friends show up). The overlap with second-holiday is manageable: second-holiday is explicitly about the SECOND year ("the sneak-up day"); the one-year card is about the FIRST anniversary — the day that closes the year of firsts, which the whole world knew about a year ago and has since filed away.

Hmm, both are strong. Let me pick based on: which one helps someone beyond the project most concretely? Both. Which is more distinct? The parking lot. Which has been queued longest? The anniversary note.

Actually, let me look at what first-holiday.html covers to check whether the first anniversary is touched there. First-holiday is about the first holiday (Thanksgiving/Christmas etc.) without them. The first deathday is different.

I'll go with the anniversary note builder — "The One-Year Card" — because:

1. It's been the leading candidate for three consecutive days; the project's own continuity points there.
2. The first anniversary of a death is a signature hard day with no dedicated page.
3. It's a builder — the site's most common and most-used artifact type — and complements second-holiday (year two) and birthday-year-three (their birthday) to complete the calendar-marks trilogy: first-holiday (the first holiday), the one-year card (the first deathday), second-holiday (the second-year days), birthday-year-three (their birthday, ongoing).

Hmm, but wait. Let me double-check the overlap concern by reading second-holiday.html's tool section and first-holiday.html quickly. If second-holiday's tool already drafts "anniversary of the death" texts, my builder needs a clearly different frame: the FIRST anniversary specifically, with its own content (the year of firsts closing, the "can't believe it's been a year" trap, the lead-up dread, the "do they even remember what day it is" question, the counting-down weeks). That's distinct enough — same relationship as first-holiday to second-holiday.

Actually, you know what — let me reconsider one more time and then commit. The parking lot page is more distinct but the anniversary card is more queued. The mission says "do one good thing per day" — either qualifies. The log's "next planned step" lists candidates without ranking. I'll commit to the One-Year Card / anniversary note builder since it's been the persistent front-runner and completes the calendar-marks series.

Let me now look at:

1. second-holiday.html structure (to differentiate and to reuse the template)
2. A builder page's form + JS structure (condolence-builder.html) to match conventions

Then build the page. Let me read second-holiday.html fully-ish (skim key parts) and condolence-builder.html's form/JS.

I see the condolence-builder structure. Now let me look at the second-holiday.html tool to make sure I differentiate, and check its "rest of the arc" section. Let me grep for key structural elements.

The second-holiday page covers "the second one" (year two). The new page — the one-year card / first anniversary — is distinct in frame: it's about the FIRST anniversary of the death — the day the year of firsts closes, the day that was public a year ago but has been filed away by everyone but the griever.

Let me look at second-holiday's "rest of the arc" section and its form/tool to model the structure. Let me view lines 127-260 of second-holiday.html.

Good — now I understand the conventions. The second-holiday page covers the SECOND anniversary (year two). The first-holiday page covers the first holiday. The gap: the first anniversary of the death itself — the one-year mark. That's the page I'll build: The One-Year Mark (one-year-mark.html) — the first anniversary of the death — with a tool that drafts the one-year note (for a friend to send), plus a plan.

Note the differentiation:

• first-holiday = first Christmas/holiday table
• second-holiday = the second-year days (second holiday, second birthday, second deathday anniversary, second wedding anniversary)
• birthday-year-three = their birthday in year 3+
• NEW: the one-year mark = the first anniversary of the death — the day the "year of firsts" closes. The day everyone knew about a year ago (the death was public, the funeral happened) and has filed away since.

The frame is distinct from second-holiday: second-holiday's thesis is "the second one sneaks — the village has gone home." The one-year mark's thesis is different: the first anniversary is the day the calendar closes the year of firsts; it was the ONE hard day the world DID know about (they all came to the funeral), so the griever might expect company — and then the day arrives quietly anyway, because people file the death under "last year's event." Both frames agree the friend job is to remember the date. Also the first anniversary carries specific features: the "we made it through the year of firsts" question, the dread-weeks buildup, the "should we do something?" question, the anniversary as a milestone the griever may want marked (ritual, gathering, or deliberately nothing).

Content plan for the page (one-year-mark.html):

1. The 60-second version — the first anniversary is the day nobody forgot on purpose; you can't remind a griever of their own calendar; the first is the hard one the world actually knew about and still goes quiet; the week before often hurts more than the day; "I can't believe it's been a year" is the wrong frame (time flies is about you); the friend job is one date + one text; the name is the gift; small marks beat big gestures; every grief runs different.

2. Why the one-year mark is its own hard day — it closes the year of firsts (every first-whatever already survived, and this is the last one); it was the public event (everyone knew the date once — the funeral wore it) and quietly became private; the griever has been counting down for weeks (and feels wrong for counting); the year-one report fantasy (the world expects a "survived it" update, the griever just wants the name said); some families mark it deliberately, some flee — both correct; anticipation is honest arithmetic.

3. The tool: the one-year note — five small answers: grieving person's name (optional), the person who died's name (optional but the gift), who they were to the griever (relationship), the beat (week before / day of / day after), tone (warm, brief, light). Outputs: the note + a private remembering plan (date in calendar recurring annually, week-early reminder, no question mark, next year's already handled).

4. The anatomy of the one-year note — mark it early or on the day; say the name and one true thing; acknowledge the year without grading it ("a year of missing him" not "you made it!"); no question mark; offer nothing or one concrete thing; respect the shape they chose (ritual, quiet, fleeing the city — all correct); no "can't believe it's been a year" as the headline; never "at least the first year is behind you."

5. The ways it goes wrong — the time-flies headline; the congratulations frame ("you made it through the first year!" — grief isn't a marathon finish); the name embargo; the pop quiz ("how are you holding up today?"); the assumption that the family has plans; the rescue staging (surprise gathering without consent); the silver-lining ("at least the worst year is over" — year two has opinions); doing nothing because you figure they want privacy — they want the name, not the spotlight.

6. Hard cases — when you missed the day (send it late; late beats silent, "yesterday was a year and I didn't say it — I was thinking of him then too"); when the griever insists it's not a thing (believe them, send the no-question-mark text anyway or lower the wattage); when the family splits on how to mark it; when the death was hard to explain (the first anniversaries of the deaths nobody names are the loneliest — the name and the date still apply, especially there); when you're the griever and nobody remembers (tell two people the date out loud — not attention-seeking, it hands out the memo).

7. If it's your first anniversary (griever's section) — you are not doing it wrong however it lands; decide one thing now, not on the day; small and private counts; tell two people the date out loud; let one good moment count; "a year of missing them" is a true sentence; plan the morning after; dark-and-stays-dark guidance with 988/findahelpline.

8. The rest of the arc — cross-links: first-holiday (the first holiday table), funeral-guide (the early days), week-three-visit, condolence-builder (the first note), second-holiday (year two — the sneak-up day, the companion for the lap after this one), birthday-year-three (the birthday that outlasts the deathday), sitting-with-guide, check-in-builder, worried-builder/not-their-therapist for darker stretches.

Hmm — that's a lot of sections. Let me keep it similar in scale to second-holiday (which has: 60-second version, why the second is the sneak-up day, the tool, anatomy of remembering well, ways it goes wrong, hard cases, if it's your second, rest of the arc). I'll mirror with: 60-second, why the one-year mark is its own hard day, the tool, anatomy of the one-year note, ways it goes wrong, hard cases, if it's your first anniversary, rest of the arc.

That's a clean parallel and the framing differences are clear: second-holiday = year two of any hard day; one-year-mark = the first anniversary of the death specifically.

The tool JS needs to be robust. Let me design the functions carefully:

Inputs:

• gName (grieving person's first name, optional)

• lName (name of person who died, optional)

• rel (their relationship to the griever): options: spouse/partner, parent, child, sibling, friend, other... Let condolences handle this? second-holiday used "dayKind". For one-year-mark, relationship matters: "your husband," "your mom," "your son," "your brother," "your person." Let me include relationship select: husband/wife/spouse → "your husband"; parent (mom/dad/parent) → "your mom"... Maybe simpler: a select with: "Their spouse or partner", "Their parent", "Their child", "Their sibling", "Their friend", "Someone else they loved". Text: "your husband"... "someone else they loved" is hard to phrase — use "your person" or just the name. Actually to keep grammar safe, I can use a free-text relationship like condolence-builder does ("their relationship to the person you're writing to"), e.g. "mom · husband · oldest friend". That's flexible and safe: loss phrase = "your mom, Ruth" style or just name. I'll do the free-text approach but with a hint, same as condolence-builder. Hmm, but the second-holiday and telling-the-kids style uses selects. A free-text field for relationship is fine for a builder (condolence-builder does it). Let me use free text for relationship — safer grammatically than mapping selects.

• beat: week before / day of / day after (select)

• tone: warm / brief / light (select)

Outputs:

1. The note text
2. The private remembering plan

JS functions:

• clean(s): normalize whitespace, trim
• phrase(rel, lName): "your mom, Ruth" / "your mom" / "Ruth" / ""
• buildNote(gName, lName, rel, beat, tone): string
• buildPlan(gName, lName, rel, beat, tone): string

Note structure:

• Greeting: "Mara," or "Hi," if no name (brief: name or nothing)
• The acknowledgment: beat-specific:
  • before: "I know Saturday makes a year since [loss phrase / you lost phrase]." Hmm — without a date available, "I know this week makes a year..." Let me handle: "I know [this week/the day] is one year since ..." Use: dayof → "I know today makes a year since ..."; before → "I know the anniversary is this week — one year since ..."; after → "I was thinking about [name/them] yesterday, on the day — one year."
  • Actually keep phrasing generic without needing the weekday: before: "I know the one-year mark is coming up this week."; dayof: "I know today is one year."; after: "One year and a day — I was thinking of [name/them] yesterday too."
• The name and one true thing: if lName present: "[lName] hasn't gone anywhere in my — " hmm. Something like: "I still think about [lName] — [if rel: your rel,] ...". Let me craft per tone:
  • warm: "I'm thinking of you, and I'm thinking of [lName or 'them'] — a whole year of missing [them-or-lName], and I'm sorry the world has mostly gone quiet about it."
  • The "one true thing" can't be auto-generated without a memory field. second-holiday's tool didn't have a memory field; condolence-builder did. I'll add an optional memory field like condolence-builder, because "say the name and one true thing" is core advice. Field: "One true thing about the person who died (optional)".

Inputs final:

• gName (optional)
• lName (optional)
• rel (free text, optional)
• memory (free text, optional)
• beat (select: before/dayof/after)
• tone (select: warm/brief/light)

Note assembly:

1. greeting
2. acknowledgment line (beat-specific, naming lName if present: "I know today makes one year since you lost [phrase]." where phrase = "your mom, Ruth" | "your mom" | "Ruth" | fallback: "since you lost [lName]"... hmm if no rel and no lName: "I know today is one year on." Let message handle.
   • before: "I know this week makes it one year" + (phrase ? " since you lost " + phrase : "") + "."
   • dayof: "I know today is one year" + ...
   • after: "Yesterday made one year" + ... For fallback with no info: "I know this week is the anniversary." / "I know today is the anniversary." / "Yesterday was the anniversary."
3. name + memory line: if lName or memory:
   • lName and memory: "[lName] is still so present — [memory] is the kind of thing I keep carrying." Hmm, better: "I keep thinking about [lName] — [memory]." If only lName: "I keep thinking about [lName]." warm; "I'm holding [lName] in mind today." formal-ish. If only memory: "I keep thinking about them — [memory]."
   • tone variants: brief: "Thinking of [lName] today."/"Thinking of them today." light: maybe a soft line: "[lName] stories still get told at my house." — careful, keep sincere. Let me design per-tone options.
4. no-grade line: "A whole year of missing [them/lName-as-object e.g. 'him' unknown → use 'them'] — that's not a thing to be congratulated for, just a thing to be named." warm; brief: "A year of missing them. No grade, just naming it."; light: "One full year of [name-frequency]. Still the wrong kind of milestone." — hmm.
5. no-duty close: "No need to reply — I just didn't want the day to pass without somebody saying [lName or 'their'] name out loud."
6. sign-off with sender? condolence-builder had sender field. second-holiday's tool didn't include sender. I'll skip sender (keep 6 fields) — no, second-holiday had 5 fields (gName, lName, dayKind, beat, tone). Condolence had 7. For one-year-mark: gName, lName, rel, memory, beat, tone = 6 fields. Fine.

Plan output (private note to self):

• "The date: put it in your calendar today, recurring every year, with a reminder set one week early. The week-before text is the whole job."
• "The beat: [before → you sent it early, while the dread is still building; dayof → short, early, no question mark; after → the day-after text is the rarest one ever sent]."
• "The rules: say the name — [lName or 'the name, whatever it is']; no question mark; no 'can't believe it's been a year'; no 'at least the first year is done.'"
• "Respect their shape — ritual, quiet day, or fleeing the city; all correct."
• "Next year: while you're here, confirm the recurring entry. The second-year text has its own page (link printed as plain text? In plan output, plain text; but in-page we can link). Keep plan as text: 'The second one has its own companion page on this site.' Hmm — keep it general.
• "If this week has felt heavier than a hard date — for you or for them — the 988 line and findahelpline.com are real." (include in plan or footer.)

Where grammar must be safe across combinations: 2 beats × 3 tones × presence/absence of gName/lName/rel/memory → I'll brute-force test all combos in Node: 3 (lName present/absent) × 3 (rel) × ... actually test: gName {absent,present}, lName {absent,present}, rel {absent,present}, memory {absent,present}, beat {3}, tone {3} = 2^4 × 9 = 144 combos. Test each output for undefined/NaN/[object], double spaces (careful: normal text may include intentional double spaces? Avoid generating them), stray " your " mishaps, ending punctuation.

Also need the "rel free text" safety: strip leading "your", strip trailing punctuation, avoid empty. And handle phrase: if rel && lName: "your mom, Ruth" — but if user types "your mom" with "your" → strip. If rel only: "your mom". If lName only: "Ruth". If neither: fallback lines.

Additional content: I should double check that the page's framing doesn't collide too much with second-holiday. second-holiday = "the second one is the sneak-up day" (year two). My page = "the one-year mark — the first anniversary: the hard first one." The distinct content: the year of firsts closing, the public-date-gone-private dynamic, the countdown, the congratulation trap ("you made it through year one"), the ritual question (do we mark it?), the time-flies trap. Solid.

Also the arc links in my page should reference: first-holiday, funeral-guide, week-three-visit, condolence-builder, second-holiday ("the lap after this one"), birthday-year-three, sitting-with-guide, check-in-builder, and worried-builder/not-their-therapist.

Nav placement: add "one-year-mark.html" after "birthday-year-three.html" in nav ( grief sequence: first-holiday, second-holiday, birthday-year-three → hmm, chronology: first-holiday (year one holiday) → one-year-mark (year one deathday) → second-holiday (year two) → birthday-year-three (year three). So placement right after first-holiday and before second-holiday makes sense. Or after funeral-guide. The existing grief nav order: obituary-eulogy-starter, funeral-guide, first-holiday, second-holiday, birthday-year-three, workplace-loss, ... I'll insert "The One-Year Mark" between first-holiday and second-holiday. That keeps chronological flow: Funeral → First Holiday → One-Year Mark → Second Holiday → Birthday Year Three.

Title: "The One-Year Mark" with subtitle "the first anniversary". Filename: one-year-mark.html.

Now — the index.html "today" card, progress.html entry, data/progress.json, log file. Also cross-link from first-holiday.html, second-holiday.html, birthday-year-three.html, condolence-builder.html (their "rest of the arc" sections). Let me check first-holiday.html's arc and condolence-builder's arc sections. Actually condolence-builder is an old builder page with "details" sections, not "rest of the arc". Let me check whether condolence-builder has an arc section... From the earlier read, condolence-builder has details/summary sections plus footer; no "rest of the arc". So I'll cross-link from the grief-arc pages that have arc sections: first-holiday, second-holiday, birthday-year-three, funeral-guide(?), week-three-visit(?), sitting-with-guide(?). Let me check which of those have "The rest of the arc" sections: first/second/birthday confirmed. Let me check funeral-guide and week-three-visit and sitting-with-guide.

Pages with "rest of the arc": first-holiday, second-holiday, birthday-year-three, week-three-visit. I'll cross-link from these four grief-related pages.

Now let me look at the full structure of second-holiday.html's head/style to copy the template conventions (the one-pagers include a page-specific block for print). Let me view the head of second-holiday.

I have the full template picture. Now let me build the new page: one-year-mark.html — "The One-Year Mark" — the first anniversary of a death. I'll write the whole page in one file write operation, then validate.

Let me compose the page carefully.

Nav: I'll insert <a href="one-year-mark.html">The One-Year Mark</a> between first-holiday and second-holiday across all pages.

Page title: "The One-Year Mark" — eyebrow: "Printable field guide · free to share". Lede: something like: "Every death leaves two dates: the day it happened and the birthday. The first anniversary of the day it happened — the one-year mark — is the day the year of firsts officially closes. A year ago the whole village knew the date; they wore it to the funeral. This year the same day arrives quiet, because the world files a death under 'last year's event' while the griever lives it under 'every single day.' This is a one-pager for that day — for the one whose calendar it owns, and for the friend who wants to get it right: why the one-year mark is its own hard day, how the note goes, the ways it goes wrong, and a tiny tool that drafts the one-year text. Print it before the date turns."

Sections:

1. The 60-second version (card today, with print button)
2. Why the one-year mark is its own hard day
3. The tool: the one-year note (screen-only)
4. The anatomy of the one-year note
5. The ways it goes wrong
6. Hard cases
7. If the first anniversary is yours
8. The rest of the arc

Let me write the content with care, distinct from second-holiday (year two) and birthday-year-three (birthday).

60-second version:

• The first anniversary is the day the year of firsts closes. Every "first without them" has already been survived; this is the last one, and the calendar knows it.
• A year ago this date was public — people wore it to the funeral. This year it arrives quiet, because the world files a death under "last year's event."
• You can't remind a griever of their own calendar. The fear of "bringing it up" is backwards; the day is already brought up. Saying the name is the gift, not the risk.
• "I can't believe it's been a year" is the wrong headline — time-flies is about your experience. Grief doesn't take the year off.
• No congratulations frame. "You made it through the first year!" turns grief into a marathon finish. Don't grade; name.
• The friend job is one date and one text: put the date in your calendar, send the no-question-mark text, and let it demand nothing.
• Respect the shape they chose — ritual, quiet, or a plane ticket. All correct.
• If you missed the day, send it late. "Yesterday made a year and I didn't say it" beats another silent year.
• Every family, faith, and grief runs different.

Why the one-year mark is its own hard day:

• It closes the year of firsts — the first birthday, first holiday, first winter, all survived; the anniversary is the last first.
• It was public once — the only hard day the whole village ever knew about. The funeral wore the date. That creates a strange expectation of company, and then the day arrives quiet anyway.
• The countdown is real — grievers report dreading the day for weeks, and feeling silly for counting. Anticipation is honest arithmetic, not regression.
• The year-one report fantasy — the world half-expects a "we survived it" update. The griever just wants the name said.
• Some families mark it deliberately (a ritual, a dinner, a grave visit); some flee it on purpose. Both are doing it right.
• And sometimes the day lands soft — allowed, not an omen.

The tool (screen-only): five-six small answers → note + plan.

The anatomy of the one-year note:

• Go first, and early. The week-before text reaches them while the dread is still building.
• Say the name, and one true thing if you have it. The specific memory is a small inheritance.
• Acknowledge the year without grading it. "A year of missing him" — named, not celebrated.
• No question mark. A lamp left on, not a knock.
• Offer nothing, or one concrete thing. Presence is enough.
• Respect the shape. Whatever they chose for the day is the right shape.
• Mark next year while you're here — the second one has its own terrain (link to second-holiday).

The ways it goes wrong:

• The time-flies headline ("I can't believe it's been a year") — about you, not them.
• The congratulations frame ("you made it through the first year!") — grief isn't a marathon finish; there is no finish.
• The "at least the first year is behind you" — year two has opinions. (Link to second-holiday.)
• The name embargo — the person gets disappeared a second time, once by death, once by politeness.
• The pop quiz — "How are you holding up today?" demands a performance on the one day performances are hardest.
• The assumption of plans — "the family probably has something going" is how everyone does nothing.
• The rescue staging — a surprise gathering without consent. Grief days need consent even from kindness.
• The privacy guess — doing nothing because "they probably want space." They want the name, not the spotlight; there's a difference.

Hard cases:

• When you missed the day — send it late. Lines like "I realized yesterday was the year, and I want you to know [name] was on my mind then and now." Late beats silent, every year.
• When they insist it's not a thing — believe them and lower the wattage: the three-word text with the name still counts.
• When the family splits on how to mark it — refuse the referee job; carry no verdicts, carry the name to whoever's version needs it.
• When the death was hard to explain — suicide, overdose, a death the family goes vague about: the first anniversaries of the deaths nobody names are the loneliest on the calendar. The name and the date still apply — especially there.
• When it's yours and nobody says anything — tell two people the date out loud. Not asking for attention; handing out the memo your people actually want.
• When this year brought thoughts of not being here — yours or theirs: that's the same-day signal. 988 call/text (US), findahelpline.com by country.

If the first anniversary is yours:

• However it lands — flat, wrecked, strangely fine, nothing — that is the day doing what it does. You are not doing it wrong.
• Decide one thing now, not on the day: one small mark. A candle, their song, their lunch order. Small and private counts.
• Tell two people the date out loud. "Saturday makes a year" is a memo, not a plea.
• Name what would help in plain words — people rise to specific requests and fail at guessing.
• Let one good moment count. Laughter on the day is not betrayal of the missing.
• The "congraduation" problem is real and you don't owe anyone a performance of healed. "A year of missing him" is a complete sentence.
• Plan the morning after — the day after an anniversary is its own small cliff.
• If it gets dark and stays dark — gray weeks, panic, thoughts of not being here — tell one true person today, and reach 988 (call/text, US) or findahelpline.com (by country). The day needing company should cost nothing heavier.

The rest of the arc:

• funeral-guide — the very early days, where the dates first go into calendars.
• condolence-builder — the note for the first week; this is the note for the first year.
• week-three-visit — the month after, the first rehearsal for the remembering job.
• first-holiday — the first holiday table of the year of firsts.
• second-holiday — the companion for the next lap: the second anniversary and the second of everything that sneaks.
• birthday-year-three — the other date: their birthday, the one that outlasts even the deathday.
• sitting-with-guide — the general companion for the quiet years.
• check-in-builder — the ordinary-Tuesday text between anniversaries.
• worried-builder / not-their-therapist — when the year has gone heavier than hard dates.

Tool JS:

Fields:

• gName (input text) — grieving person's first name, optional
• lName (input text) — name of person who died, optional
• rel (input text) — their relationship, free text, optional (e.g., mom · husband · oldest friend)
• memory (input text) — one true thing, optional
• beat (select: before | dayof | after)
• tone (select: warm | brief | light)

Functions (top-level for testability):

acknowledgment line by beat:

Hmm, "I know the one-year mark is this week since you lost your mom, Ruth." — reads awkward: "is this week since you lost". Fix: attachments: before: "I know this week is one year since you lost X." dayof: "I know today is one year since you lost X." after: "Yesterday was one year since you lost X —..." Without phrase: before: "I know this week is the one-year mark." dayof: "I know today is the one-year mark." after: "Yesterday was the one-year mark."

Simpler and cleaner:

• before, warm/light: "I know this week is one year" + since + "." ; brief: "I know this week makes a year" + since + "."
• dayof, warm/light: "I know today is one year" + since + "." ; brief: "I know today makes a year" + since + "."
• after, warm/light: "Yesterday was one year" + since + ", and" ... hmm: "Yesterday was one year" + since + " — I'm not letting it pass unspoken."; brief: "Yesterday was one year" + since + " — I didn't want it to pass." where since = phrase ? " since you lost " + phrase : "" — check grammar: "I know today is one year since you lost your mom, Ruth." ✓. "I know this week is one year." ✓ (slightly terse but fine). Maybe fallback better: "I know today is the one-year mark." Let me use: if no phrase: "I know today is the one-year anniversary." etc.

name/memory line:

Hmm wait — for fallbacks I need to be careful. Let me simplify: nameLine returns lines about the name; if no lName and no memory, use a general "the name" line still (because the advice is "say the name" — but if the sender didn't provide one, note says "the name" generically; okay).

the no-grade line:

close:

Hmm "one voice saying Ruth out loud" — good; "one voice saying their name out loud" — good.

Plan output:

Plan as a list joined by newlines with "• " prefix, similar to second-holiday's plan format? Let me check second-holiday's plan format... It uses prompts div; the plan is probably lines separated by \n. I'll format as "1. ...\n2. ..." or "· ". Let me check second-holiday JS render. Actually, let me not worry — I'll format plan as numbered lines "1. " etc.

Mounted code (IIFE): attach input listeners to fields; render on input; copy buttons use navigator.clipboard with fallback; status text updates.

Also need the print button on the first card (60-second version) with id printBtn → window.print(). Check second-holiday's print approach: in if-youre-the-kid there's a printBtn. Let me check second-holiday for printBtn — the 60-second card in second-holiday probably has one too. I'll include: <button type="button" id="printBtn">Print this page</button> and script wire: printBtn.onclick = () => window.print().

Let me check how second-holiday wires the print button and copy button to mirror conventions. Let me view the JS section of second-holiday.html (lines ~250-400).

Now I have the complete pattern. The second-holiday tool uses a "Hey — " text-message style. For the one-year mark, I'll follow the same conventions but with content specific to the first anniversary of the death.

Key design decisions for the tool:

• Fields: gName (griever), lName (person who died), rel (relationship, free text), memory (one true thing, free text), beat (before/dayof/after), tone (warm/brief/light)
• buildYearText(v) and buildPlan(v) as top-level functions for testability
• Same IIFE wiring pattern, same wireCopy, same printBtn

Let me now write the complete page. I'll be careful with:

• Grammar across all input combos
• No undefined/NaN tokens
• HTML escaping (use & where needed, apostrophes fine as ')
• The nav with the new link inserted between first-holiday and second-holiday

Let me draft the note-building function carefully:

Careful: the no-lost/no-mem fallback says "this week especially" — wrong for dayof/after. Make it: beat === "before" ? "this week especially" : beat === "dayof" ? "today especially" : "yesterday and today both". Similarly the lost-only brief line: "Thinking about X — still, and today especially." → beat-aware: before → "this week especially"; dayof → "today especially"; after → "yesterday and today."

Let me define var whenWord = beat === "before" ? "this week" : (beat === "dayof" ? "today" : "yesterday"); and use it.

// sentence 3: the year, named not graded

// sentence 4: no-duty close

Wait, for beat=after, whenWord = "yesterday" — close: "just someone who knows what yesterday is." → should be "what yesterday was." Fix: use a closeWhen: before → "what this week is"; dayof → "what today is"; after → "what yesterday was". And warm close: "around for anything or nothing — this week, and the week after, and the year after that" — for after beat: "this week, and the year after that" still fine ("around ... this week" = the week after the anniversary — fine). Let me define:

For the warm close, keep beat-neutral: "Around for anything or nothing — this week, and the week after, and the year after that." Works for all beats.

Also check double spaces: hi ends with " — " then ack starts with capital "I". "Hey Mara — I know today makes one year since you lost your mom, Ruth." ✓. "Hey — I know today is the one-year mark." ✓.

Grammar check on ack with phrase: "I know today makes one year since you lost your mom, Ruth." ✓. Without rel: "since you lost Ruth" ✓. rel only: "since you lost your mom" ✓.

Edge: user types rel "your mom" → strip leading "your" → "mom" → "your mom" ✓. User types "mom." → cleanName strips trailing period ✓.

buildPlan(v):

Check: whose = "Mara's" → "One-year plan for Mara's first anniversary:" ✓; fallback "their first anniversary" ✓.

Quotes inside JS strings: I'm using " escapes — fine.

Now the HTML page. Let me write it fully. I need to be careful with the nav — copy exactly from second-holiday.html and insert the new link between first-holiday and second-holiday.

Also the footer convention: "Made by One Good Thing as today's good thing (2026-09-04). Free to print and share — no analytics, no accounts, nothing stored, no network requests. Not professional advice — every family and every grief runs differently; if things get dark and stay dark, in the US call or text 988, or find lines by country at findahelpline.com. A field guide assembled from what grievers and their people consistently say helped. Read the log (../progress/2026-09-04.md)."

Now the full content. Let me write it.

Also — the meta description.

Title: "The One-Year Mark · One Good Thing" H1: "The One-Year Mark" Eyebrow: "Printable field guide · free to share"

Lede: "A year ago, everybody knew the date. They wore it to the funeral; they put it in their phones; for a few weeks the whole village orbited it. Then the world did what the world does — filed it under last year's event — while the person who lost them kept living it under every single day. Now the calendar has come all the way around: the first anniversary, the day the year of firsts officially closes, arriving quietly in a house that has been counting down to it for weeks. This is a one-pager for that day — for the one whose calendar it owns, and for the friend who wants to get it right: why the one-year mark is its own hard day, how the note actually goes, the ways it goes wrong, the hard cases, and a tiny tool that drafts the one-year text from a few small answers. Print it before the date turns."

Sections as planned. Let me now write the whole file. I'll write it via a heredoc or the write tool. The write tool is cleaner for a big file. Let me compose it completely.

One more consideration — the "card today" first section with print button, like if-youre-the-kid and second-holiday. In second-holiday, is there a printBtn? The JS references printBtn. Let me assume the 60-second card has it (grep to confirm later). I'll include it.

For the arc section, links: funeral-guide, condolence-builder, week-three-visit, first-holiday, second-holiday, birthday-year-three, sitting-with-guide, check-in-builder, worried-builder, not-their-therapist.

Let me also think about the "hard cases" section and "if it's yours" section — with the crisis lines.

Now write the file. I'll use the write tool with the full content. Then:

1. Add nav link to all 40 pages (python script inserting after first-holiday link).
2. Cross-link from first-holiday, second-holiday, birthday-year-three, week-three-visit arc sections.
3. Update index.html today card.
4. Update progress.html (prepend entry).
5. Update data/progress.json (prepend entry, updated date).
6. Write /space/progress/2026-09-04.md.
7. Validate: node test of the JS functions across full matrix; HTML structure check; link check; nav check; JSON parse.

Let me write the page now. I'll aim for quality prose in the established voice.

Section content — let me draft fully:

60-second version (ul.steal):

1. The one-year mark is the day the year of firsts closes. First birthday without them, first holiday, first winter, first ordinary Tuesday — all survived one by one. The anniversary is the last first, and the calendar knows it even when nobody says so.
2. A year ago this date was public. People wore it to the funeral. This year it arrives quiet — not because anyone forgot on purpose, but because the world files a death under "last year's event" while the griever files it under "every day."
3. You cannot remind a griever of their own calendar. The fear of "bringing it up" is backwards — the day is already up; it has been up for weeks. Saying the name is the gift, not the risk.
4. "I can't believe it's been a year" is the wrong headline. Time-flies is about your experience of the year. Theirs did not fly. Lead with the name, not the stopwatch.
5. No congratulations frame. "You made it through the first year!" turns grief into a marathon finish. There is no finish. Name the year; don't grade it.
6. The friend job is one date and one text. Put the date in your own calendar — recurring, with a reminder a week early — and send the no-question-mark text. That is the whole job, and almost nobody does it.
7. Respect the shape they chose. A ritual, a quiet day, a plane ticket out of town — all correct. Grief days need consent even from kindness.
8. If you miss the day, send it late. "Yesterday made a year and I didn't say it" beats another silent year. Late is not the failure; silent is.
9. Every family, faith, and grief runs different. The people who know the griever are the authority. This page is just a flashlight.

Why the one-year mark is its own hard day:

• It closes the year of firsts. Every first-without-them has already been survived — and the anniversary is the last one, the day the calendar itself says "that was the year." Closing something is its own kind of losing it again.
• It was public once — the only hard day the village ever knew. The funeral wore the date; for a few weeks everyone orbited it. That creates a strange expectation of company, and then the day arrives quiet anyway. The gap between last year's noise and this year's silence is the wound.
• The countdown is real. Grievers report dreading the day for weeks — and feeling silly for counting, as if the date were an appointment they made. It isn't. Anticipation is honest arithmetic, not regression.
• The world half-expects a year-one report. "How are you doing?" starts carrying a quiet hope for a finished story — better, stronger, past it. The griever doesn't want to file a report. They want the name said.
• Some families mark it, some flee it. A dinner, a grave visit, a candle, a deliberate ordinary day, a trip out of town — every shape is correct, including the shape that changes its mind on the morning of.
• And sometimes the day lands soft. Some first anniversaries are strangely okay. That isn't betrayal and isn't "finally over it" — it's one day, and the second year is allowed to be different again.

The tool — intro paragraph: "Six small answers and the page drafts two things: the one-year text itself — the week-before, the day-of, or the day-after — and a private plan for being the one who remembers. Copy them, adjust them, use them. Nothing leaves this tab."

Form fields:

• gName: Their first name (the grieving person — optional)
• lName: The name of the person who died (optional, but the name is the gift)
• rel: Their relationship to the grieving person (optional) — placeholder "e.g. mom · husband · oldest friend"
• memory: One true thing about the person who died (optional) — placeholder "e.g. the way he laughed at his own jokes before the punchline"
• beat: Which beat are you sending for — before (The week before — "somebody knows what this week is"), dayof (The day itself — short, early, question-mark-free), after (The day after — "that one counts as done")
• tone: warm / brief / light

Outputs: yearOut + planOut, copy buttons, status line: "Send the text as-is or make it sound like you — either way, send it. Then check the calendar entry actually recurs before you close this tab."

The anatomy of the one-year note:

• Put the date in your own calendar — recurring, with a reminder a week early. A year ago everybody knew the date; this year the reminder system is you. The week-before reminder is what makes the week-before text possible.
• Go first, and go early. The week-before text — "I know this week makes a year" — reaches them while the dread is still building and says the one thing the day needs said: somebody knows.
• Say the name, and one true thing if you have it. Not "thinking of you" alone — the name, and a specific: "I still tell the story about his parallel parking." The specific memory is a small inheritance you get to hand over.
• Name the year without grading it. "A whole year of missing him" — named, not celebrated. The year happened to them; it wasn't a course they passed.
• No question mark. "How are you holding up today?" demands a performance on the one day performances are hardest. "Thinking of you and Ruth today" demands nothing. A lamp left on, not a knock.
• Offer nothing, or one concrete thing. Presence is enough; if you add anything, make it specific and permission-free — soup on the porch, not "let me know."
• Respect the shape they chose. Ritual, quiet, or a plane ticket — all correct. Don't upgrade their plans and don't rescue them from their own day.
• Mark next year while you're here. The second anniversary has its own terrain — it sneaks. The calendar entry you confirm today is the friend who shows up then.

The ways it goes wrong:

• The time-flies headline. "I can't believe it's been a year!" — about your year, not theirs. Theirs did not fly.
• The congratulations frame. "You made it through the first year!" Grief isn't a marathon; there is no finish line to congratulate anyone across.
• The "at least the first year is behind you." Year two has opinions. The second of everything is its own ambush, and "behind you" is a promise no one can make.
• The name embargo. Saying nothing about the person to keep the day "light" — the person gets disappeared a second time, once by death, once by politeness.
• The pop quiz. "So — how are you, today of all days?" A question mark on the anniversary is a demand wearing a costume.
• The assumption of plans. "The family probably has something going" is how an entire circle does nothing. Assume the day needs witnesses, not organizers.
• The rescue staging. The surprise gathering, the ambush of kindness. Grief days need consent even from kindness — ask, or keep it small enough to step over.
• The privacy guess. Doing nothing because "they probably want space." Most grievers want the name, not the spotlight — and silence reads as the world having moved on, because it has.

Hard cases:

• When you missed the day. Send it late. "I realized yesterday was the year, and I want you to know he was on my mind then and now" — late beats silent, every single year. The day-after text is the rarest one ever sent.
• When they insist it's not a thing. Believe them — and lower the wattage rather than dropping the beat entirely. A three-word text with the name in it still counts and demands nothing.
• When the family splits on how to mark it. One branch holds a dinner, another wants the day left alone. Refuse the referee job. Carry no verdicts; carry the name to whichever version of the day you're invited into.
• When the death was hard to explain. Suicide, overdose, the deaths families go vague about — the first anniversaries of the deaths nobody names are the loneliest on the calendar. The name and the date still apply, especially there. You don't have to name how they died to name that they lived.
• When it's yours and nobody says anything. Tell two people the date out loud. "Saturday makes a year" is not asking for attention — it's handing out the memo your people actually want. Most silence is not indifference; it's a missed memo.
• When the year has gone darker than hard dates. For you or for them: weeks of gray, panic that won't settle, any thought of not being here — that's a today thing, not an anniversary thing. In the US call or text 988; anywhere else, findahelpline.com lists lines by country. Saying the heavy thing out loud to one person is the brave version.

If the first anniversary is yours:

• However it lands is how it lands. Flat, wrecked, strangely fine, nothing at all — the day does what it does. You are not doing it wrong, and there is no grade.
• Decide one thing now, not on the day. One small mark: the candle, their song, their lunch order, ten minutes somewhere that was theirs. Small and private counts; no witness required.
• Tell two people the date out loud. Not a plea — a memo. The people who love you mostly want to get this right and mostly don't know the date matters this much.
• Name what would help in plain words. "Could you just text me that morning so I know someone knows?" People rise to specific requests and fail at guessing.
• You don't owe anyone a performance of healed. The year-one report is not due. "A year of missing him" is a complete sentence and a complete answer.
• Let one good moment count. If you laugh on the day, that isn't betrayal — it's the medicine working. They'd have wanted the laugh; everyone always does.
• Plan the morning after. The day after an anniversary is its own small cliff — the adrenaline of dread spent, the quiet back. Put one gentle thing there on purpose.
• If it gets dark and stays dark — gray weeks, panic that won't settle, thoughts of not being here — tell one true person today, and reach a real line: in the US call or text 988; anywhere else, findahelpline.com. The day needing company should never cost more than company.

The rest of the arc:

• The Funeral & Shiva Guide covers the very early days — where the date first goes into everyone's calendar, and why it quietly falls out.
• The Condolence Builder writes the note for the first week. This page is the note for the first year.
• The Week-Three Visit covers the month after the loss — the first rehearsal for the remembering job a year out.
• The First Holiday Without Them is the companion for the other hard firsts of year one — the table with a missing seat.
• The Second Holiday Without Them is the companion for the next lap — the second anniversary and the second of everything, which sneaks up precisely because the world thinks year one was the hard part.
• Their Birthday, Year Three and Beyond is the page for the other date — the birthday, the one that outlasts even the deathday.
• The Sitting-With Guide is the general companion for the quiet years — the chair, the silence, the follow-through.
• The Check-In Builder drafts the ordinary-Tuesday text that keeps the thread alive between anniversaries.
• If the year has gone heavier than hard dates — gone quiet everywhere, not just on the calendar — the Worried Friend Builder drafts the harder message, and You're Not Their Therapist is for the friend carrying too much.

Footer: "Made by One Good Thing as today's good thing (2026-09-04). Free to print and share — no analytics, no accounts, nothing stored, no network requests. Not professional advice — every family and every grief runs differently; if things get dark and stay dark, in the US call or text 988, or find lines by country at findahelpline.com. A field guide assembled from what grievers and their people consistently say helped. Read the log."

Now — the "card today" 60-second section gets the print button + meta line like if-youre-the-kid:

Let me now write the file. I'll write it with the write tool (full content). Note the indentation in second-holiday is 4-space-ish; consistency within the file is what matters.

One thing to double check: in the ack for beat=after with phrase: "Yesterday made one year since you lost your mom, Ruth, and I didn't want it to pass in silence." — comma splice-ish but acceptable in this voice. Actually "Yesterday made one year since you lost X, and I didn't want it to pass in silence." ✓ fine.

Also check nameLine for lost-only warm with beat=before: "I'm holding Ruth in mind this week — the name deserves saying out loud, so I'm saying it." ✓ dayof: "I'm holding Ruth in mind today — ..." ✓ after: "Ruth was on my mind yesterday, and is today." ✓

yearLine brief: "One full year of missing Ruth. No grade — just named." ✓ "One full year of missing them." ✓

close brief dayof: "No need to reply — just someone who knows what today is." ✓ after: "what yesterday was" ✓ before: "what this week is" ✓.

close light: "No reply needed, no performance required. Around for soup, a walk, a story about Ruth, or respectful silence — dealer's choice." ✓ fallback "a story about them" ✓.

close warm: "No need to reply to this, and nothing to perform. Around for anything or nothing — this week, and the week after, and the year after that." ✓ all beats.

Now the whole text assembly: hi + ack + " " + nameLine + " " + yearLine + " " + close.

Sample full output (g=Mara, lost=Ruth, rel=mom, memory="the way she made every stranger feel like a regular", beat=dayof, tone=warm): "Hey Mara — I know today makes one year since you lost your mom, Ruth. I keep thinking about Ruth — the way she made every stranger feel like a regular. A year doesn't touch that kind of thing. A whole year of missing Ruth is not a thing to be graded or congratulated. It's a thing to be named, out loud, by somebody — so consider it named. No need to reply to this, and nothing to perform. Around for anything or nothing — this week, and the week after, and the year after that."

Good. Brief/no-info sample: "Hey — I know today is the one-year mark. Thinking about them — still, and today especially. One full year of missing them. No grade — just named. No need to reply — just someone who knows what today is."

Good.

Now write the file. After that, do the nav insertion across all pages with python, cross-links, index, progress.html, progress.json, log, and validations.

For the nav insertion: the nav in each page contains: <a href="first-holiday.html">First Holiday</a> followed (with varying whitespace) by <a href="second-holiday.html">Second Holiday</a>. I'll insert <a href="one-year-mark.html">The One-Year Mark</a> between them with a newline, matching each file's own indentation — simplest: replace <a href="first-holiday.html">First Holiday</a> with <a href="first-holiday.html">First Holiday</a>\n <a href="one-year-mark.html">The One-Year Mark</a> — but indentation varies across files (some have 8 spaces, some 6, some weird). The whitespace inside nav doesn't matter for rendering. To be safe and simple, I'll do a regex replace in Python: replace (<a href="first-holiday\.html">First Holiday</a>) with \1\n <a href="one-year-mark.html">The One-Year Mark</a> in all files except one-year-mark.html itself (which I'll write with the link already in place). But careful: some pages might link to first-holiday.html in their arc sections too! The arc links have different anchor text ("The First Holiday Without Them"), so the exact match >First Holiday</a> should only hit the nav. Let me verify with grep: count occurrences of >First Holiday</a> per file.

Also for the arc cross-links: I'll add an item to the "rest of the arc" lists in first-holiday.html, second-holiday.html, birthday-year-three.html, week-three-visit.html. Need to see each file's arc list to insert appropriately. Let me grep those sections when I get there.

Let me write the new page now.

The page is created. Now let me:

1. Test the JS functions in Node across the full input matrix.
2. Add the nav link to all pages.
3. Cross-link from arc pages.
4. Update index.html.
5. Update progress.html and data/progress.json.
6. Write the log.
7. Validate everything.

First, extract and test the JS. I'll write a Node test script that stubs document/window/navigator and loads the page's script, then calls buildYearText/buildPlan across the full matrix.

All 432 outputs (216 text + 216 plan) are clean — no undefined/NaN, no double spaces, all grammatical. The samples read well.

Now:

1. Add the nav link to all 40 other pages (insert between first-holiday and second-holiday).
2. Cross-link from first-holiday, second-holiday, birthday-year-three, week-three-visit arc sections.
3. Update index.html.
4. Update progress.html and data/progress.json.
5. Write the log.
6. Validate.

Let me do the nav insertion with Python. First check the exact nav pattern across files — the anchor text is "First Holiday" in nav. Let me verify only nav occurrences match >First Holiday</a>.

Each file has exactly ONE occurrence of >First Holiday</a> as a standalone nav link (the two prose occurrences in not-their-therapist and workplace-loss are inline within paragraphs, but grep -c counted lines; each of those files shows count 1 for the nav line plus the inline mention appears on a separate line). Let me verify: not-their-therapist.html grep -c shows... it wasn't in the first list (which was cut at 10). The inline mention is on a long paragraph line; the nav link is on its own line. If I do a naive replace of the exact string <a href="first-holiday.html">First Holiday</a> it would ALSO replace the inline prose occurrence in those two files — bad. I need to replace only the nav occurrence: the one that appears as a line consisting of whitespace + the link. Use a regex that anchors the full line: ^\s*<a href="first-holiday\.html">First Holiday</a>$ with re.MULTILINE, and replace with itself + new line + indented new link. The indentation varies (6 or 8 spaces mostly). I'll capture leading whitespace and reuse it.

Let me write a Python script doing exactly that, across all html files, and print per-file count of substitutions (should be 1 per file, 40 files total excluding one-year-mark.html).

40 files updated (all except the new page itself, which already has the link). Now the cross-links in arc sections. Let me look at the arc lists in first-holiday.html, second-holiday.html, birthday-year-three.html, and week-three-visit.html to choose insertion points.

For:

• first-holiday.html: add item pointing to one-year-mark (the day the year of firsts closes).
• second-holiday.html: add item noting the first-anniversary companion (the lap before this one).
• birthday-year-three.html: add item about the one-year mark (year one of the deathday).
• week-three-visit.html: add item about the remembering job a year out.

Let me view the arc sections.

**************************************************************************************************************************************************************************************************ly.

Let me view the arc list items in each file to find good anchor points for insertion. I'll view a few lines after each "rest of the arc" heading.

Now I'll insert cross-links:

1. first-holiday.html: after the "week-three-visit" item (or after condolence item). Best spot: after the condolence-builder item, before goodbye-builder. Insert: <li>The year of firsts closes at the anniversary itself: <a href="one-year-mark.html">The One-Year Mark</a> covers the day the calendar comes all the way around — and the friend job when it arrives quiet.</li> — insert after the week-three-visit item.

2. second-holiday.html: after the first item (about first-holiday), insert: <li><a href="one-year-mark.html">The One-Year Mark</a> is the companion for the lap before this one — the first anniversary, the day the year of firsts closes, when the date was public a year ago and arrives quiet now.</li>

3. birthday-year-three.html: modify the item mentioning first/second holiday? Better to insert a new item after that one: <li>The deathday has its own arc too: <a href="one-year-mark.html">The One-Year Mark</a> covers the first anniversary — the day the year of firsts closes.</li>

4. week-three-visit.html: the "Further out on the calendar" item mentions first-holiday, second-holiday, birthday-year-three. I'll add the one-year mark into that item or insert a new item after it: <li>Between those two: <a href="one-year-mark.html">The One-Year Mark</a> covers the first anniversary of the death — the day the year of firsts closes, and the note for the friend who remembers it.</li>

Let me do these with replace_in_file (exact anchors).

All four cross-links are in. Now update index.html — replace the "today" card content and the "last time" reference. The current index.html has:

• <p class="eyebrow">Today · 2026-09-03</p> → change to 2026-09-04
• h2 "If You're the Kid" → "The One-Year Mark"
• The long description paragraph → new one
• The "Use it now" paragraph → new link
• The second card "The pages this one completes" → new content about where this fits
• "Last time's good thing was The Kid's People" → "If You're the Kid"

Let me write the new main section of index.html. I'll replace the whole ... block. Let me construct it in the same style.