epic(wishlist): tracking issue to break out into multiple issues, close when decomposed to multiple issues

[thewrz]

Decomposed. This wishlist (captured from a user-feedback session) has been broken into tracked issues per its own closing instruction. Each bullet was triaged three ways: already built (use the existing endpoint/tool), non-goal (explicitly out of scope), or new work (a deterministic feature, sometimes also answerable today via an MCP agent query).

Verdict legend: 🟢 already built · 🔵 new deterministic · 🟣 MCP-now + deterministic-later · ⚪ non-goal

Wishlist item	Verdict	Disposition
Related Sections — referenced sections missing from the directory; which, and where called out (§ + ¶ + snippet)	🟢 / 🔵	Detection ships today via the coordination report's dangling_ref (reports source section, reference text, and which libraries could supply the missing section). Paragraph-level locator + snippet (and catching refs without the literal "Section " keyword) → #260
Sections listed under Related Sections but not referenced in the body	🔵	#259 (needs article-role tagging — #258)
Sections referenced in the body but not listed under Related Sections	🔵	#259
Body work implies an unlisted Related Section (e.g. conduit firestopping → 07 84 00)	🟣	Answerable now via an MCP agent (list_sections + search_library); deterministic title-keyword index → #261
Codes/Standards under References but not cited in the body	⚪	Non-goal — you marked this "This is OK." No finding emitted.
Codes/Standards cited in the body but not listed under References	🔵	#259 (standard refs already extracted; needs References-article tagging — #258)
Have all inserted comments been closed? (strike-out OR "Closed" suffix)	🟣	Comment text is already exposed via MCP, so an agent can flag any comment not ending in "Closed" today; deterministic open/closed state + strike-out capture + open-comments report → #262
Create a submittal table for a group of selected specs	🟣	An MCP agent can synthesize a draft register now from the selected specs; deterministic submittal model + register → #263 (needs #258)
Intelligent search ("for these specs, which sections refer to Firestopping 07 84 00?")	🟢	Already built — get_references(direction:'to') (MCP) / GET /projects/{id}/references/inbound?section=07 84 00. Natural-language framing is an MCP usage pattern over existing tools.
Umbrella sections called out in each subordinate section	🔵	#264 (umbrella↔subordinate registry — easy for Div 26/27/28 — + a new coordination finding; ADR required)

Foundation

• feat(ast): semantic article-role tagging — Related Sections / References / Submittals #258 — semantic article-role tagging (Related Sections / References / Submittals). Keystone that unblocks feat(coordination): article↔body reference consistency (Related Sections / References) #259 and feat(api): submittal register/table for a group of selected specs #263; ADR required.

Children

#	Title	Verdict
#258	article-role tagging (keystone)	🔵
#259	article↔body reference consistency (A2/A3/B2)	🔵
#260	missing-section locator (¶ + snippet on dangling_ref)	🔵
#261	implied Related-Section detection (title-keyword)	🟣
#262	comment-closure state + open-comments report	🟣
#263	submittal register/table	🟣
#264	umbrella↔subordinate cross-call-out check	🔵

All seven are on the SpecR project board in Backlog (not yet vetted/sequenced into Ready). Items marked 🟢 / ⚪ need no new issue. Closing this epic — the work now lives in the children above.

---

🤖 Triaged & decomposed by Claude (Opus 4.8).

[thewrz]

Decomposed into #258–#264 (all on the SpecR board in Backlog). Already-built items (intelligent search → get_references/inbound endpoint; missing-section detection → dangling_ref) and the non-goal (standards listed-but-not-cited) are recorded in the issue body. Closing per the epic's own instruction.