Post-P8 / Server Interop: `checkHasConnectedSystems` uses draft-era conformance URIs not declared by spec-conformant servers (csapi-go interop blocker)

[Sam-Bolling]

[Sam-Bolling]

Closing summary

Implemented and folded into PR #136 (commit effaa78 on OS4CSAPI/ogc-client:clean-pr) without growing the PR's commit count — Phase 8's single squashed commit was amended in place via cherry-pick + commit --amend.

Acceptance criteria

• checkHasConnectedSystems(csgoConformance) returns true (live 2026-04-29 fixture)
• checkHasConnectedSystems(oshConformance) returns true (regression — declares non-spec /conf/core)
• checkHasConnectedSystems(featuresOnlyConformance) returns false
• All existing info.spec.ts and endpoint.spec.ts tests pass (35 ogc-api suites, 1495 tests on both phase-8 and clean-pr)
• Strict-mode discovery in OS4CSAPI/ogc-csapi-explorer@0d188d3 will now succeed against csapi-go (no library change required there)
• docs/research/requirements/csapi-conformance-capabilities.md no longer contains ogcapi-connected-systems- (64 replacements on phase-8)
• docs/research/references.md includes new "Conformance Class Identifiers — Canonical Form" subsection

Commits

• OS4CSAPI/ogc-client-CSAPI_2:phase-8 c323e06 — atomic fix with full doc edits (audit trail)
• OS4CSAPI/ogc-client:clean-pr effaa78 — folded into the single Phase 8 commit (PR D-1: Resolve SystemTypeUris name collision between model.ts and constants.ts #136 head)

Investigation outcome (per request)

• Bug 1 (code): info.ts was authored against draft URIs (/conf/core, /conf/dynamic-data) that don't appear in OGC 23-001/23-002, our own csapi-conformance-capabilities.md, or the bundled OpenAPI YAMLs. Process gap, not a reference-doc gap.
• Bug 2 (docs): csapi-conformance-capabilities.md used ogcapi-connected-systems- (with hyphen) in 64 places; canonical form is ogcapi-connectedsystems- (no hyphen). Fixed.
• Reference doc updated with verification fingerprint (live conformance from csapi-go and OSH, captured 2026-04-29).