Version continuity: v3.8 was never published — fold forward or archival stub

[styk-tv]

Problem

The site's published narrative documentation sequence currently ends at v3.7. A v3.8 set was never released here, so shipping v3.9.1 next would leave a visible gap in the version history.

Independently of the narrative docs, the v3.8 ontology IRIs are already referenced publicly (see the ontology hosting issue in this milestone) — so the /ontology/v3.8/ set must exist regardless of what happens to v3.8 narrative pages.

Decision to make

• Option 1 — fold forward: record v3.8 on the changelog page as an interim epoch whose changes are documented within the v3.9.1 set; publish no standalone v3.8 pages
• Option 2 — archival stub: publish a minimal docs/v3.8/ entry (version note + changelog) so every version in the sequence has a landing page

Either way, the versioned changelog page must present a continuous v3.7 → v3.8 → v3.9.1 history.

Acceptance

• Decision recorded in this issue
• Changelog page shows a continuous version history through v3.9.1
• No dangling "latest" pointer skips an epoch silently

[styk-tv]

Decision (owner): fold forward — no intermediate versions are published. The version story on the site is: v3.7 is the last full narrative set; v3.8 is the core vocabulary's permanent namespace (now resolvable, see #1); the current protocol epoch is v3.9.1, presented on the landing page with the measured epoch timeline; v3.10 (CKN) is the design direction. The changelog continuity requirement moves into #2 (the v3.9.1 set's changelog page).