feat(workflows): daily-prep carries execution links and join links

A Day's Priorities entry now carries the URL the task is done through (payment portal, doc, PR, form), not just the thin link to its todo.org home. When that URL is missing from the todo.org body, the prep build finds it and adds it to both. Meeting lines in Meetings / Work Blocks get an org link to the join URL from the calendar event's conference data, so joining is one click from the prep doc.

Both rules came out of working the 2026-06-10 prep doc, where paying an invoice meant a Gmail dig for the payment URL first.

1 files changed, 16 insertions, 1 deletions

diff --git a/claude-templates/.ai/workflows/daily-prep.org b/claude-templates/.ai/workflows/daily-prep.org
index 327e519..abf70a4 100644
--- a/claude-templates/.ai/workflows/daily-prep.org
+++ b/claude-templates/.ai/workflows/daily-prep.org
@@ -102,6 +102,8 @@ Each actionable entry under =* Day's Priorities= is a *pointer to a todo.org tas
 
 All the substance — descriptions, drafted messages, research findings, sub-tasks, =VERIFY= asks, recommended-approach blocks — lives in the matching =todo.org= task, created or updated by Phase 3. If a todo.org task doesn't exist yet, create one (with the conventional priority cookie / Linear ID in the heading) and link to it. This keeps everything in one place (todo.org), so the prep doc never accretes content that then has to be transferred back.
 
+*The execution link rides with the entry (2026-06-10 rule).* The thin link covers the task's *home*, not the way to *do* it. When a priorities entry is actionable through a URL — a payment portal, a doc to read, a PR, a form — the entry body carries that link directly. If the link isn't already in the todo.org task body, the prep build hunts it down (the source email, the Slack thread) and adds it to BOTH the todo.org body (durable home) and the prep entry. The failure mode this prevents: "Pay NOLA Sewerage & Water Board invoice" linked to todo.org but not to the InvoiceCloud payment URL, so doing the task meant a Gmail dig first.
+
 Exceptions that stay in the prep doc as content (not links):
 - *Completed-today entries* — once a task is done, its heading becomes a dated log entry (=** YYYY-MM-DD Day @ HH:MM ...=, see [[file:../../.claude/...][feedback_done_tasks_become_dated_log_headings]] — i.e. the dated-heading rule) and stays in the prep doc as the day's record. If the work also has a durable todo.org home, the dated entry links to it.
 - The =* Standup Briefs=, =* Heads-up=, =* Upcoming Deadlines=, and =* [Next day]'s Anchor Tasks= sections — those are prep-doc-native and don't map to todo.org tasks.
@@ -275,7 +277,7 @@ The engine (3b) and sub-step 3a's =:reactive:= pull have populated =todo.org= wi
 <one line on why today>
 #+end_example
 
-Items that don't fit today stay in =todo.org= and resurface on a future prep via 3a's =:reactive:= pull. Don't duplicate task bodies into the prep doc; the thin link is the whole entry (2026-05-12 rule).
+Items that don't fit today stay in =todo.org= and resurface on a future prep via 3a's =:reactive:= pull. Don't duplicate task bodies into the prep doc; the thin link is the whole entry (2026-05-12 rule). One exception to the no-content rule: a URL the task is *done through* (payment portal, doc, PR, form) goes in the entry body per the execution-link rule above — and into the todo.org body if it isn't there yet.
 
 *** Sub-step 3d: Urgency re-sort
 
@@ -295,6 +297,16 @@ Take the per-source marks from the engine's synthesis (its Phase C reports per-p
 
 Once priorities are confirmed, block time on the calendar to accomplish them. Phase 4 also writes the prep doc's =* Meetings / Work Blocks= section — a single chronological list interleaving meetings with focused-work blocks, top to bottom in time order.
 
+*** Meeting lines carry clickable join links (2026-06-10 rule)
+
+Every meeting line in =* Meetings / Work Blocks= gets an org link to its join URL, pulled from the calendar event's conference data (=conferenceData.entryPoints= in the Phase A MCP output — already fetched, no extra query). Example:
+
+#+begin_example
+- 10:00–11:00 — SWE weekly sprint planning [recurring; Eric] — [[https://us06web.zoom.us/j/...][join Zoom]]
+#+end_example
+
+Craig clicks and joins right from the prep doc instead of digging through the calendar. A meeting with no conference URL (in-person, phone) just omits the link.
+
 *** Quick Tasks (< 5 minutes)
 Tasks like "schedule a meeting with Ryan" or "send a Slack message" should be done during the prep workflow itself, not scheduled separately. Draft the message or create the calendar event on the spot.
 
@@ -611,5 +623,8 @@ Phase 3's inline source scans — sub-steps 3b (email), 3c (mark-read), 3d (Slac
 *** 2026-06-01: Prep docs live in =daily-prep/= with a root =daily-prep.org= symlink — no inbox churn, no archive move
 Craig's call. The prep doc is now *born* in =daily-prep/YYYY-MM-DD-daily-prep.org= and never moves; the dated files accumulate there as both working location and archive. A single stable symlink at the project root — =daily-prep.org= — points at the current day's file, repointed each prep run with =ln -sf=. Replaces the prior model where the doc was born in =inbox/YYYY-MM-DD-daily-prep.org=, yesterday's stayed in =inbox/=, and older docs were =mv='d into the =daily-prep/= archive (old Phase 8). Consumers resolve the root symlink instead of computing a dated filename or searching =inbox/=: the Emacs opener =C-c p d= (=cj/open-project-daily-prep=, repointed from =inbox/today-prep.org= to =daily-prep.org= — handoff filed to the =.emacs.d= project 2026-06-01), next-day Phase 2, and the standup lookback (Phase A step 5, which now globs =daily-prep/= and takes the file before the symlink's target). Touchpoints updated: Phase A step 5 + slim-Phase-A step 2 (lookback), standup-only "Where the brief lands," Phase 8 (rewritten as "Repoint the Current-Day Symlink"). Cross-workflow: =triage-intake.org='s sentinel-anchor fallback dropped its =inbox/= prep-doc path. (=wrap-it-up.org= was left as-is — its =inbox/= references are about =lint-followups.org= routing, not the prep doc, so they stay correct.) Migration is one-time per project: move existing =inbox/*-daily-prep.org= into =daily-prep/= and create the root symlink at the most recent.
 
+*** 2026-06-10: Execution links in priorities + join links on meetings
+Two link rules from working the 2026-06-10 prep doc (Craig's asks, verbatim in the handoff: "when adding tasks to the priorities, you will need to include the relevant link" / "we really need to add links to the meetings so I can click and join right from the daily prep document"). (1) A Day's Priorities entry actioned through a URL carries that URL in the entry body; the thin link to todo.org names the task's home, not the way to do it. If the URL isn't in the todo.org task body yet, the prep build finds it (source email, Slack thread) and adds it to both. Worked example: the NOLA water-bill task linked to todo.org but not the InvoiceCloud payment URL, so doing the task meant a Gmail dig first. (2) Every meeting line in Meetings / Work Blocks carries an org link to its join URL from the calendar event's conference data, so Craig joins from the prep doc. Stated in *Prep Doc Structure* (execution-link rule), sub-step 3c, and the new Phase 4 join-links sub-section.
+
 *** 2026-06-10: Manager Tools prep additions — 5-day look-ahead, daily big-ball, decline gate
 Three additions folded in from the Manager Tools / Career Tools casts on preparing-for-your-day and meeting prep. None adds a new prep-doc section (the fixed-section rule holds — the look-ahead feeds Heads-up / Anchor Tasks). (1) *5-Day Look-Ahead* — Phase A widens the calendar fetch from the prep day to the prep day plus the next 5 days, and a new Phase 1 sub-section scans that forward window for three buckets: meetings that need prep, traps (time-zone mismatch, double-booking, overrun, an unneeded recurring meeting), and focus blocks to protect. A scan-and-flag pass, not full prep. (2) *Daily big-ball* — Phase 3 sub-step 3a item 5 pulls one important-but-not-urgent (Quadrant-2) task per day and slates a ~15-minute chunk, since strategic work only lands when broken into small daily pieces. (3) *Decline gate* — Phase 1 item 5 reframes "what Craig needs" from attending to contributing, and adds a send-regrets gate: a meeting with no objective and no contribution is a decline candidate for Craig's call at review. The look-ahead's meeting-prep references link directly to =meeting-prep.org= (promoted to a template 2026-06-10).