Skip to content

feat(harmonization): add passive status evidence catalog - #386

Open
bearmug wants to merge 2 commits into
mainfrom
feat/issue-385-phase4
Open

feat(harmonization): add passive status evidence catalog#386
bearmug wants to merge 2 commits into
mainfrom
feat/issue-385-phase4

Conversation

@bearmug

@bearmug bearmug commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add passive Advisor and Context Broker FeatureStatusV1 adapters alongside the existing Router/Orchestration adapters
  • add an ordered bundle status catalog with explicit failure isolation and no lifecycle/control authority
  • harden status validation against raw/prohibited strings, unknown fields, prototype/cycle/size abuse, and malformed adapter inputs
  • record the Context Broker's effective backend/degraded state rather than configured environment text
  • add deterministic synthetic status-report generation and documentation

Closes #385

Safety and scope

This is read-only introspection/reporting. It preserves feature ownership, command names, defaults, registration order, routing, worker authority, and lifecycle behavior. It does not create or migrate state, upload telemetry, change policy, select models, dispatch workers, or expose prompts, transcripts, payloads, paths, secrets, or user content.

The checked-in status report uses synthetic fixtures and is a schema/process check, not a production spend, quality, usage, or savings claim.

Validation

  • npm run check — passed; 68 package tests and 28 scripts gated
  • npm test — 68 files / 754 tests passed; existing weak-label research warnings remain non-fatal
  • npm run harmonization:status -- --output <tmp> — passed
  • repeated status report generation — byte-for-byte deterministic
  • focused adapter/catalog/privacy tests — passed
  • Codex review findings were addressed: effective backend reporting, bounded status strings/diagnostics, malformed Advisor mode handling, prototype-safe validation, and URL-safe CLI entrypoint detection

@bearmug

bearmug commented Jul 19, 2026

Copy link
Copy Markdown
Contributor Author

Review-loop update: fixed fail-closed status validation, bounded diagnostic structures, malformed Advisor mode handling, effective Context Broker backend/degraded reporting, URL-safe CLI entrypoint detection, and degraded-backend health classification. Final CI passes; local full suite reports 754 passing tests with the existing weak-label research warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Harmonization phase 4: collect passive representative evidence via FeatureStatusV1

1 participant