close-threadlisted

# Close Thread Close one thread, end to end. You gather the thread's material, run every check before the first write, then land the thread's draft ADRs and glossary entries into the project layer and record the thread's outcome on the roadmap entry it answers. The thread folder stays in place: what marks the thread closed is that its drafts and its terms now live in the project layer. Once the checks pass, the writes run without questions. Writing the last record is where you stop — do not stage, commit, or push. ## Inputs Gather all of these before running the checks; everything below works from what you gather here. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the thread's drafts, which land beside them. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - The thread to close — the folder the invocation names, in the shape `<skill_path>/references/formats/thread.md` defines. Everything below is read inside it. - The thread's `seed.md` — why the thread exists and what it set out to reach. When it carries a `Roadmap:` line and an `Entry:` line, they name the roadmap index this thread was opened from and the slug of its entry. - The thread's `spec.md`, when the file exists — the design claims the currency check reads. - The thread's `adr/` ��� the draft records to land, in the shape `<skill_path>/references/formats/adr.md` defines. - The thread's `glossary.md`, when the file exi