Fix nine formatters that read field paths the API never returns

[adamjohnwright]

What

Nine tools called their endpoint correctly and reported success, but read fields the Reactome APIs never return. They rendered undefined — or, worse, silently rendered nothing and looked fine.

contentClient.get<T> asserts T, it does not verify it, so nothing caught any of this. The seven analysis tools had no tests at all, which is why the token bug fixed in #21 survived as long as it did.

Crashed or printed "undefined"

Tool	What the API actually returns
search_suggest, search_spellcheck	a bare string[], not {suggestions: []}. Suggest threw on .map; spellcheck guarded the access, so it reported "no suggestions" for every input
entity_component_of	one entry per relationship type with parallel names/stIds/schemaClasses arrays — not Complex objects. Every container printed **undefined** (undefined) [undefined]
participants	a reduced projection keyed on peDbId; no stId, no dbId
static_interactors, psicquic_details	entities lists the molecules queried; interactors hang off each one. Reading score a level too high threw Cannot read properties of undefined (reading 'toFixed')
interactor_summary, psicquic_summary	same envelope, same level error
analysis_found_entities	a mapsTo entry has ids (plural), not identifier

Silently dropped data, with no "undefined" to give it away

• participants never showed external identifiers — the endpoint returns refEntities (an array), never a singular referenceEntity. UniProt accessions are now rendered, which is new capability, not just cosmetics.
• search_facets returned nothing but its heading. Each facet is an object with an available list, so .length was undefined and every section was skipped as falsy.

These two are the reason this PR is bigger than the sweep that started it: grepping rendered output for undefined cannot find a field that was dropped cleanly. Only diffing against the real payload does.

Also

• events_hierarchy defaulted to species "Homo sapiens", which that endpoint answers with HTTP 500; "9606" returns 200. The default made the tool fail every time it was called without an explicit species.
• The four interactor tools shared one envelope and four wrong copies of it. They now share one type and one formatter.

How it was found

Swept every reachable tool against the live services — 48 of 53, once a real analysis token was obtained to unlock the token-gated ones — and diffed rendered output against the actual payloads.

Verification

• npm test: 41 → 57 tests, all passing.
• 15 of the 16 new tests fail against the previous code (verified by stashing src/).
• Every fixture is copied verbatim from the live service, with the endpoint and response recorded in a comment above the type. If a fixture stops matching production, that is a signal to change the formatter — not the fixture.
• Post-fix sweep: no undefined in any rendered output.

Known upstream, not fixed here

/data/orthology/{id}/species/{taxId} returns HTTP 500 for valid-looking input, and /interactors/psicquic/molecule/{resource}/... returns 500 rather than 400 for an unknown resource. Both are Reactome-side; our URLs match the documented routes.

🤖 Generated with Claude Code