feat(workflows): thin-link Day's Priorities + auto-sync after triage

In daily-prep, Day's Priorities entries are now thin links to todo.org tasks rather than copies of their content. The substance — descriptions, drafts, research, sub-tasks, STALLED asks, recommended-approach blocks — lives in the matching todo.org task that Phase 3 creates or updates. Completed-today entries still convert to dated log headings as the day's record. Phase 3's Linear action-item step also gets a comment-as-child-header pattern: paste the @mention or comment inline rather than referencing it, so the reply can be drafted in the prep doc.

In triage-intake, mbsync -a now runs at the end of every triage by default — no more "ask before syncing" — and a Synced line in the summary records the run.

1 files changed, 3 insertions, 2 deletions

diff --git a/.ai/workflows/triage-intake.org b/.ai/workflows/triage-intake.org
index a0657b5..36f9530 100644
--- a/.ai/workflows/triage-intake.org
+++ b/.ai/workflows/triage-intake.org
@@ -89,7 +89,7 @@ All three mail accounts are synced to local Maildirs and =mu=-indexed: =~/.mail/
        <path-1> <path-2> ...
    #+end_src
    *Always pass explicit paths.* Never call =mark-read= with no positional args — the bare default is "mark every unread message across every configured INBOX maildir on the machine," which happens to be the same set here but becomes a footgun the moment a project's extension narrows the scope. =--reindex= re-runs =mu index= so the local index reflects the new flags. =--dry-run= previews without modifying.
-3. Flag changes land on disk; =mbsync= propagates them to the servers on its next run. If the user wants the servers updated immediately, run =mbsync -a= after — but don't auto-sync; ask first (matches =summarize-emails.org='s "ask before syncing").
+3. Flag changes land on disk. *Always run =mbsync -a= at the end of a triage-intake* so the read flags propagate to the servers before the workflow closes — don't leave them queued for the next sync, and don't ask first (Craig's standing instruction, 2026-05-12). The "conflicting changes (N,M)" notices mbsync prints when both sides touched flags are normal — it resolves them. (This overrides the older "ask before syncing" posture inherited from =summarize-emails.org=.)
 4. Trash obvious junk separately and *only with user approval* — never trash without an explicit go-ahead.
 
 *** Slack — every conversation surfaced
@@ -107,7 +107,8 @@ One concise summary back to the user:
 - *What moved (by source)* — one line per change worth knowing.
 - *Actionable* — numbered, with the proposed next step per item.
 - *Cleared* — total count of emails (across the three accounts) and Slack conversations marked read.
-- *Pending decisions* — anything needing user input before action (draft replies awaiting approval, ambiguous routing, =mbsync= sync offer, etc.).
+- *Pending decisions* — anything needing user input before action (draft replies awaiting approval, ambiguous routing, etc.).
+- *Synced* — confirm =mbsync -a= ran and note any non-trivial output.
 
 * Principles