Release v0.9.0: The Deterministic Telemetry

v0.9.0 establishes deterministic telemetry as a release-level engineering contract across core, action, and docs.

1) Flat-Cost DQS Shift

The quality score now treats every active suppression as a uniform debt signal:

• one suppression equals one score-point deduction;
• suppression debt is always visible in the final score;
• governance thresholds are evaluated independently from debt accumulation.

This closes long-standing ambiguity between enforcement outcomes and score telemetry.

2) BaseAdapter Legacy Method Removal

v0.9.0 finalizes adapter contract simplification by removing legacy dual-method surfaces in favor of a single route-information path.

Migration focus:

• remove legacy adapter method surfaces from custom implementations;
• keep routing semantics deterministic at a single integration boundary;
• reduce divergence between link resolution and classification behavior.

3) Native Freshness Gate via --check-stamp

Telemetry is now enforced through a native freshness command:

• zenzic score --check-stamp verifies badge freshness deterministically;
• freshness checks are config-aware through declared stamp targets;
• CI and local pre-push gates share the same telemetry contract.

4) Landing/Topology (LSM) Restructuring

The release also introduces landing and topology realignment in the LSM layer:

• narrative and route surfaces are aligned to the new telemetry model;
• release communication is split between historical archives and active manifests;
• topology-facing docs now follow the same deterministic signal boundaries used by runtime governance.

Outcome

v0.9.0 turns telemetry from a side-channel metric into a deterministic release surface: inspectable, reproducible, and enforceable in every gate stage.