Verify Solr 10.1 Export includeStoredFields behavior #258

Context

export() exposes the Solr Export API includeStoredFields option, but the current pinned-version evidence covers raw Export response behavior on Solr 8.11.4, 9.11.0, and 10.1.0 without asserting this option's version-specific semantics. The compatibility docs must not imply that exposure in the TypeScript model is runtime certification.

Scope

• Confirm the documented wire parameter and supported semantics against the pinned Solr 10.1 reference/runtime.
• Add an isolated integration assertion using a disposable collection with representative stored/docValues fields, if the server behavior supports it.
• Record version-specific results and any 8.x/9.x differences; do not broaden the claim beyond tested versions.
• If the option is unsupported or behaves differently, document the limitation and adjust types/docs rather than silently claiming support.

Acceptance criteria

• Runtime evidence is recorded for Solr 10.1.0: includeStoredFields=true returns a stored-only field.
• No cross-version claim is made; Solr 8/9 behavior remains unclaimed.
• API coverage, compatibility docs, roadmap, Export guide, and api-inventory.json agree.
• The test uses disposable fields/data and does not change shared fixtures.

Implementation progress (2026-11-04)

• PR test: verify Solr 10.1 Export stored-only fields #261 adds a Solr 10.1-only integration assertion using a disposable stored-only field and a separate docValues sort field.
• The first Solr 10.1 standalone and security integration jobs passed; the remaining CI matrix is still running. Do not mark this issue complete until the full CI run passes and docs/inventory are reconciled.

Completion

• PR test: verify Solr 10.1 Export stored-only fields #263 merged as 9e1d484d6055b6f381b8e1621dd72b0aff2b133c.
• CI run #651 passed all 30 jobs, including the pinned-version matrix.
• Solr 10.1.0-only runtime evidence is recorded; no Solr 8/9 support claim is made.