Clean up TinaCMS collection schema overlap (blocks editor upgrade)

[adamjohnwright]

Problem

Starting tinacms dev prints 320 "file in multiple collections" warnings (see https://tina.io/docs/errors/file-in-mutpliple-collections/). On tinacms 3.4 these are warnings; on 3.8 the dev server hangs on init and ng serve is never spawned, leaving port 4200 dead (Apache then returns 502 on beta).

Example overlap from the logs:

content/content/reactome-research-spotlight/226-label-free-mass-spectrometry-proteomics-reveals-different-pathways-modulated-in-thp-1-cells-infected-with-therapeutic-failure-and-drug-resistance-leishmania-infantum-clinical-isolates.mdx Found in multiple collections: content, reactome_research_spotlights.

The content collection (path content/content) currently shadows the reactome_research_spotlights collection (path content/content/reactome-research-spotlight). Similar overlaps likely exist for other nested collections.

Fix

In projects/website-angular/tina/config.ts, add match.exclude patterns on each parent collection so files under a sub-collection's path don't also match the parent. Each file should belong to exactly one collection.

Why it matters

• Prerequisite for any future tinacms upgrade (verified during 2026-05-20 session: bumping to tinacms@3.8.1 + @tinacms/cli@2.3.1 hung indefinitely on init; reverting to 3.4.1 restored service).
• A working upgrade path is the most plausible route to fixing the side-panel resize bug tracked in TinaCMS display issues #81.