docs(research): repo health assessment + upstream csapi-go-v2 issue catalog

Honest assessment of strict-parsing migration work to date:
- What is genuinely improving (portability, OGC 23-001 conformance,
  empirical schema documented, helper infrastructure validated).
- What is NOT improving (metadata loss on the wire, no automated tests,
  copy-paste mechanical pattern, inline workaround comments).
- Comprehensive catalog of 4 P1/P2 upstream csapi-go-v2 defects + 2
  informational items, each with reproducer, current workaround, and
  expiry condition:
    #1 P1 procedure SML asymmetric typo (c2ab201 incomplete)
    #2 P1 system SML rejects characteristics/capabilities
    #3 P2 system SML returns 500 on typeOf
    #4 P2 datastream rejects SWE Time referenceTime
    #5 P3 datastream rejects top-level uid
    #6 informational deployment parent@link encoding

Recommendations: extract sml_builders helper, add contract tests, file
upstream issues, track metadata loss explicitly, choose OSH posture.

Author: Sam-Bolling