Assess the admin-site issues — separate pilot-relevant model work from court-facing admin UI

[mitch-mitchel]

What needs to change?

Nine issues describe the court-facing admin site (#733, #734, #735, #737, #738, #739, #740, #741, #742). The admin site is not a September pilot deliverable, but some of the models and underlying work beneath those issues may be. Assess each and split it.

First read, to be confirmed or overturned by the pass:

#	Title	First read
#734	Create court config library	Underlying — overlaps the library YAMLs work
#738	Topic flow field groups + field endpoints for interview builder	Mixed — field groups are model work, endpoints are admin API
#740	Admin site: forms and PDF field mapping	Mixed — PDF field mapping is the AcroForm fill path (#535), which is pilot-gating
#741	Add topic flow library	Underlying — overlaps the seed/import work
#742	User facing topic flow page	Not admin at all — user-facing
#733	Contacts and resources on the settings tab	Admin UI
#735	Editable topics on the Knowledge Base tab	Admin UI
#737	Admin site topic flow editor	Admin UI
#739	Admin site links and deadlines editor	Admin UI

Excluded: #736, which is PR #786 and already in flight.

Why?

These nine predate the current AI timeline and describe an admin-first approach it doesn't follow. Closing them wholesale would discard model work the pilot may need; milestoning them wholesale would pull a court-facing admin site into a September scope that doesn't include it. Neither is right, so the split has to be assessed rather than assumed.

Definition of done (optional)

• Each of the nine is classified: pilot-relevant underlying work, admin UI (post-pilot), or superseded
• Pilot-relevant work is extracted into issues on the September Pilot milestone, or folded into an existing epic
• Admin-UI-only issues stay open, out of the milestone, labeled so they read as a post-pilot cluster
• Superseded issues are closed by their owner
• Overlaps with the library/seed work (Create court config library #734, Add topic flow library #741) and the user-facing topic flow page (User facing topic flow page #742) are resolved so the same work isn't filed twice