OKF Explorer v0.6.3

OKF Explorer v0.6.3 corrects large-corpus record presentation without changing
producer data or weakening legacy bundle compatibility.

Highlights

• Reader overview metrics now prefer a producer's declared counts.records
  before the legacy counts.datasets fallback.
• The unloaded Timeline heading applies the same distinction, so dataset
  groupings are not labelled as records.
• Zero remains a valid declared count, and older bundles that publish only a
  dataset count retain their established fallback.
• Cross-browser tests use genuinely divergent counts and cover Reader,
  Timeline and the legacy fallback.

Verification

• Merged through PR #91
  as c6c8ccd9daaab7600ce8261d0eca587acabf917b; its Git tree is
  76a7215da9592207c8769a0db437113ef80810cf and is identical to the fully
  tested branch head.
• Annotated tag object 3ccddb8a40ca509a4219623b55fd8409341a6111
  peels to that exact merge.
• Exact-head CI run
  31548806154
  passed every selected gate: 342 Vitest checks, 78 Node contract checks, 356
  Python checks and the full Chrome, Firefox and WebKit terminal suite.
• The final 30 targeted large-corpus browser cases passed across all three
  engines. Heritage evidence also passed 100/100 governed questions at or
  above 80, with a 92.7 average, and all three local journeys.
• Deterministic application tree:
  03b482117351213a1eecb405e8542365bd7693b55e58b46ace85921c5a975e53;
  build-manifest SHA-256:
  681498b253d1c1aba7749d8fc942bdc74a5fc412c897ab9bc13e0369ac558652;
  deterministic Site candidate tree:
  80903987badc77f24b93ac305f1f8ccf4cf88c89d6b229df2b56b15b163853cf.

Deployment and public verification

• Pages run
  31549668889
  deployed the exact merge successfully.
• A fresh, service-worker-blocked Chromium session loaded the published HM Land
  Registry v0.3.0 descriptor and rendered 2,203 records, 2,203 official
  sources and 22,267 relationships. Timeline also rendered 2,203 records,
  rather than the 14 dataset groupings.
• The governed exact boundary search result was present, and the separate
  semantic deep link rendered 15 relationships including translation of
  through the runtime manifest, governed route locator and relationship shard,
  without adjacency fallback. Console and network checks were clean.
• The scoped public receipt SHA-256 is
  3511e132a6b3b6d8348f750e977addbccacd5b0b16ba610a2b7c7102b95ce53c;
  its verifier SHA-256 is
  6fcf8f80f213f4a5d5b0ac827a118733bf800136fbe9163b617c7ba0cc98aa66.

No manually attached runtime-evidence asset is required for this source and
presentation-correction release.