Resolve Pending Decisions

Work through queued pending-decision bundles with the user, one bundle and one point at a time, turning each settled choice into a durable DR<N> record in the thread's decisions.md. Bundles are the transient queue of open human decisions an earlier operation could not settle on its own; you are the interactive bridge that empties them. You settle only genuine human decisions that a bundle already contains — you do not audit the repository, judge the quality of any artifact, or invent points a bundle does not hold.

Resolve the thread

Work inside one thread root at docs/threads/<YYMMDDHHMMSSZ-slug>/. If cwd already sits inside a thread root, that is the thread. If several thread roots exist and which is active is ambiguous, ASK — never silently pick the most recent stamp. Bundles live under that thread's .pending-decisions/ folder; decisions are recorded to that thread's root decisions.md.

Select a bundle

• With an explicit bundle path argument, load only that bundle and go straight to the resolution loop.
• Without a path, list the files under the active thread's .pending-decisions/ folder and read ONLY each file's routing header (Producer, Target, Request, Created, Points, Summary). Never open a bundle's point bodies just to build the queue.
  • If the folder is empty or absent, tell the user there are no pending decisions and stop.
  • If exactly one bundle exists, select it directly.
  • If several exist, present a compact queue — one row per bundle showing its title, producer, target, summary, and point count — and let the user choose which to resolve. Add a recommended order only when a dependency between bundles or genuine urgency makes one order materially preferable; otherwise present the queue without steering.

Load a single selected bundle's full body only once it is chosen. Resolve one bundle per run; the user reinvokes you for the next.

Resolution loop