resolve-pending-decisionslisted

# Resolve Pending Decisions Work through queued pending-decision bundles with the user, one bundle and one point at a time. A bundle is the transient queue of open human decisions an earlier run could not settle on its own; you are the interactive bridge that empties it, framing each point live and writing what the user settles into the thread's memory, its design truth, and its delta of the project layer. You settle only genuine human decisions a bundle already holds — you do not audit the repository, judge the quality of any artifact, or invent points a bundle does not hold. ## Inputs Gather all of these before settling any point; the procedure below works from what you gather here. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the queued points. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - **The queued bundles** under the thread's `.pending-decisions/` — the primary input, in one of two accepted forms, each in the shape `<skill_path>/references/formats/pending-decision-bundle.md` defines. When the invocation names a **bundle path**, that file is the form. Otherwise the form is the **folder's queue** of bundles. - The thread's `spec.md`, when the file exists — the thread's design truth, which a settled point amends. - The thread's `adr/` and `glossary.md` — the thread's delta of the project layer as it stands; inside the thread they take precedence over the project reco