v4.6.0

4.6.0 (2026-10-12)

Changed

Research leads now come with a worklist (job-sluice leads followups, leads mark-asked,
leads answer). Three things change on an existing install without you running any of
the new commands:

• Every triage verdict now writes a new frontmatter key, triage_next: the question a
  research verdict asks you to put, or blank. Notes gain the key the next time they are
  judged. A value you type there over several lines is left alone.
• The triage digest gains a standing Research queue: line counting every research lead,
  how many you have marked asked, and how long ago the oldest was first seen. It is
  omitted when there are no research leads.
• Text written into a lead note's ## Job description section (leads add --jd-file,
  the MCP create_lead tool) now has an unclosed code fence closed for it, so a pasted
  posting can no longer turn the rest of the note into code.

No config keys are added. A lead you mark asked is skipped by triage run until you
record the answer; nothing is skipped until you do.

Features

• core: mark a research lead asked and record its answer (#378) (a218a69)
• core: read and write research follow-up answers (#378) (41e8443)
• leads: list research follow-ups, mark them asked and record answers (#378) (b7c9e01)
• mcp: label the follow-up answers section as the user's own notes (#378) (f338d52)
• triage: record each verdict's next action and clear a stale asked stamp (#378) (2a3d958)
• triage: skip leads awaiting a reply and show the judge recorded answers (#378) (b5647d3)

Documentation

• describe the research follow-up worklist (#378) (feaa83c)
• design the research follow-up worklist (#378) (c1c732d)
• fold the second spec review into the follow-up design (#378) (c87263e)
• fold the spec review into the follow-up design (#378) (d599290)
• fold the third spec review into the follow-up design (#378) (0a110a9)
• plan the research follow-up worklist (#378) (7237f3f)