Commit 40a87bb4aba1

@@ -27,6 +27,10 @@ The tool encodes a GTD split — two modes:
 summary yourself. Never scrape the colorized TTY output (ANSI codes, truncated
 `...` summaries, no full URLs).
 
+**Render GitHub items as `owner/repo#number`** (e.g. `tektoncd/pipeline#10372`,
+not `pipeline#10372`). Join the `repo` field (already `owner/repo`) with
+`number`. This full form is click/jump-recognized by Emacs (embark) and kitty.
+
 ## Mode A — Inbox / Process
 
 `daily-plan inbox --json` returns:
@@ -54,15 +58,30 @@ summary yourself. Never scrape the colorized TTY output (ANSI codes, truncated
 ## Mode B — Plan my day
 
 `daily-plan show --json` returns:
-- `agenda[]` — today's org agenda `{state, heading}`
+- `agenda[]` — today's org agenda (scheduled/deadlined today) `{state, heading}`
+- `deadlines[]` — org items with a DEADLINE in the next 7 days
+  `{state, heading, deadline, scheduled}`. `scheduled: false` means it is NOT
+  yet on the agenda — a candidate to slip.
 - `jira_in_progress[]`, `jira_backlog[]` — `{key, summary, status, priority, url}`
 - `github_issues[]`, `github_assigned_prs[]`, `github_reviews[]`, `github_prs[]` — GitHub items `{repo, number, title, author, created_at, url}`
 
 **Produce a prioritized plan grouped as:**
-- **Do today** — org agenda + Jira In Progress/Code Review (sort by priority, then staleness)
-- **Review** — `github_reviews` (PRs awaiting your review)
-- **In flight** — your open PRs (`github_prs`), assigned PRs (`github_assigned_prs`)
-- **Waiting / backlog** — Jira To Do (`jira_backlog`), assigned issues (`github_issues`)
+- **Do today** — org agenda + Jira In Progress/Code Review (sort by priority, then
+  staleness). Always render the org agenda as a **bulleted list, one item per
+  line** — never a dot/`·`-separated run-on line.
+- **Deadlines to watch** — from `deadlines[]` where `scheduled == false`, sorted
+  by `deadline` ascending. Flag `deadline <= today` as overdue/due-now. These are
+  the items most likely to slip because they aren't scheduled.
+- **Review requests** — `github_reviews` (others explicitly requested your
+  review). Show up to ~10, security/CVE PRs first, then oldest `created_at` first.
+- **Assigned to you** — `github_assigned_prs` (PRs you're the assignee/owner of,
+  i.e. you're on the hook even without an explicit review request). Show these
+  as a distinct group from review requests, oldest first.
+- **Your open PRs** — `github_prs`. Surface ~5–10 and sort **oldest
+  `created_at` first**: stale PRs are the ones that need a nudge, not the fresh
+  ones. Note age (e.g. "opened 2026-02-17").
+- **Waiting / backlog** — Jira To Do (`jira_backlog`), assigned issues
+  (`github_issues`, oldest first).
 
 Use the real `url` fields so every item is a working link.