[EHotwagner]

Refs #4640

Summary

Prepares the independent Telemetry Host 0.9.0 source, so that a Host built from current main can be published. That Host admits passive provider-usage-observation/1 facts with provenance claude-local-transcript/1.

• Published Host 0.8.0 (telemetry-host/v0.8.0 → 74cbd6f0) predates Capture Claude Code native usage through the existing telemetry path #4802. It still has the old check provenance <> "codex-local-rollout/1", so it answers a Claude transcript batch with invalid-request.
• Current store source maps each admitted provenance to its own native identity namespace and refuses everything else. The Host gets this parser through its FS.GG.Telemetry.Store → FS.GG.Coord.Core project references. No Host logic change is needed. Only the independent package coordinates advance, following the Prepare independent Host 0.8 for the facts browser journey #4782 route.

Changes

• Host Version 0.9.0, plus updated release notes and README.
• Release route for 0.8 → 0.9:
  • candidate/publish workflow job names and package paths
  • telemetry_host_successor_execution VERSION/TAG
  • artifact verifier VERSION
  • publisher journal utel-host-rel-15 and intent version
  • read-first gate (VERSION 0.9.0, PREDECESSOR 0.8.0, TAG, JOURNAL)
  • Store14 profile for 0.9.0
• tests/telemetry-host-successor/run.py advances to 0.9.0/journal15. It now also refuses the published 0.7.0 and 0.8.0 manifests as current identities, and the read-gate fixtures use 0.8.0 as the predecessor.
• A new Host-level test, HostPassiveReceiptTests "passive HTTP receipt admits Claude transcript provenance and refuses unknown provenance". Against the real /v1/batches endpoint it checks that:
  • a Claude transcript observation is applied
  • claude-statusline/1 is refused with 400 invalid-request
  • a Codex-namespaced identity carrying Claude provenance is refused with 400 invalid-request
  • the stored fact keeps its provenance and the Claude-namespace identity, with no item
  • Causal check: with the Claude arm removed from the store match, the test fails with invalid-request.
• The passive Host HTTP preflight minimum goes from 4 to 5 in telemetry-host-package.yml and the successor candidate, so the new test is mandatory.
• Registry:
  • telemetry-host version 0.9.0, source only. package-version/package-tag stay 0.8.0.
  • CHANGELOG entry.
  • Regenerated projections: compatibility, architecture, and the publishing-and-deployment release inventory in both roots, plus the driver skill manifest.
• A docs/coordination/telemetry-host-release.md section for the prospective 0.9 source.

Store14 is unchanged

• Since 74cbd6f0, src/FS.GG.Coord.Core/TelemetryStore.fs differs only in the provenance → namespace match.
• src/FS.GG.Coord.Cli/TelemetryStoreApplication.{fs,fsi} is byte-identical: currentSchemaVersion = 14, with the same DDL and passive query.
• The manifest profile stays (14, 14).
• Claude facts use the existing current_ingest_facts/corrections rows.

A Home Store14 workspace can therefore cut over from 0.8 to 0.9 without migration.

Coordinates

These are prospective only. No availability claim is made.

• Predecessor: published 0.8.0
  • release 419394647, target_commitish 74cbd6f0b1b598d48556eb854c4ba6a3c3abda54
  • archive 44273495…5aba89, payload sha256:f0368085…1802ee
  • journal14
  • nuget.org index ends at 0.8.0
• telemetry-host/v0.9.0 tag is absent.
• Authority state/releases lists utel-host-rel-01..14, so rel-15 is unused.

No candidate, preflight, publication or Home adoption is performed or asserted. The publisher stays default-false.

architecture-map: unaffected

🤖 Generated with Claude Code