Harmonization phase 4: collect passive representative evidence via FeatureStatusV1

[bearmug]

Goal

Build the next passive harmonization slice on top of FeatureStatusV1 and the phase-3 evidence pack so representative, privacy-preserving runtime evidence can be collected without changing behavior.

Scope

• Add a dependency-neutral, read-only status catalog/report path at the existing bundle composition boundary.
• Expose passive FeatureStatusV1 snapshots for the currently supported Router and Orchestration adapters, preserving registration order and feature ownership.
• Add read-only adapters for Advisor and Context Broker where their existing state can be safely summarized; unavailable/disabled states must remain explicit.
• Emit only versioned aggregate/allowlisted observations suitable for later evidence-pack aggregation: feature, health, enabled/mode, authority/provenance, bounded outcome/cost bands, and hashed correlation metadata where needed.
• Keep collection offline/local and deterministic for fixtures; no telemetry upload, raw prompts, transcripts, payloads, paths, secrets, user content, routing changes, policy mutation, worker selection changes, or central lifecycle/controller abstraction.
• Add representative fixture/report tests and documentation describing privacy boundaries, sampling limits, and evidence-gated follow-up decisions.

Acceptance criteria

• Existing command names, defaults, registration order, routing, worker authority, and lifecycle behavior are unchanged.
• Status snapshots are read-only and do not create, migrate, or write feature state.
• Status serialization is versioned and allowlisted; prohibited/raw fields fail closed.
• A local report can be generated from representative fixtures and matches byte-for-byte across repeated runs.
• Tests cover unavailable/disabled/idle/ready/degraded/error mappings, adapter isolation, catalog ordering, privacy rejection, and unchanged existing behavior.
• npm run check, focused tests, and the full test suite pass (apart from documented pre-existing weak-label research warnings).

Non-goals

Do not consolidate Router, Advisor, Orchestration, or Context Broker policy/lifecycle types; do not remove aliases or knobs; do not upload telemetry; do not make evidence-based deletions in this issue.

Depends on #383 and builds on the merged FeatureStatusV1 work from #379/#380.