feat(metrics): read the privacy-safe health snapshot without jq (#19) #92

Merged

rockachopa merged 2 commits from timmy/19-metrics-operator-report into main

2026-11-02 12:07:00 +00:00

Author	SHA1	Message	Date
Timmy	e08b537866	feat(metrics): render the operator health snapshot as a report (#19 ) Quality gates / quality (pull_request) Waiting to run Details The counters had an endpoint and no way to read them without jq. Adds a pure formatter plus a CLI that prints the app, queue, and model boundaries. The formatter is a function of the snapshot and the three frozen vocabularies, so a caller-supplied failure label cannot reach the terminal: unknown classes are simply not printed. Refusal paths are explicit — 404 means the route is off because no token is configured, 403 means the token was rejected — and the token is never echoed in the report or an error line. RED: tests/model-metrics-report-format.test.js failed with ERR_MODULE_NOT_FOUND before src/model-metrics-report.js existed; the refusal-path test failed with a generic 'answered 404' before the 404 branch was written. Tests: npm test 298/298, npm run test:metrics-report 8/8, syntax and diff gates clean, real-Chromium ui acceptance green with the privacy disclosure visible.	2026-11-02 10:56:16 +00:00
timmy	3e2253a052	wip(#19 ): privacy-safe model metrics in progress — preserved snapshot before nightly release Local work in progress, not reviewed and not part of any PR. Committed only so the nightly release can build from a clean main without discarding it.	2026-11-01 12:02:43 +00:00

Author

SHA1

Message

Date

Timmy

e08b537866

feat(metrics): render the operator health snapshot as a report (#19 )

Quality gates / quality (pull_request) Waiting to run

Details

The counters had an endpoint and no way to read them without jq. Adds a pure
formatter plus a CLI that prints the app, queue, and model boundaries.

The formatter is a function of the snapshot and the three frozen vocabularies,
so a caller-supplied failure label cannot reach the terminal: unknown classes
are simply not printed. Refusal paths are explicit — 404 means the route is off
because no token is configured, 403 means the token was rejected — and the token
is never echoed in the report or an error line.

RED: tests/model-metrics-report-format.test.js failed with ERR_MODULE_NOT_FOUND
before src/model-metrics-report.js existed; the refusal-path test failed with a
generic 'answered 404' before the 404 branch was written.

Tests: npm test 298/298, npm run test:metrics-report 8/8, syntax and diff gates
clean, real-Chromium ui acceptance green with the privacy disclosure visible.

2026-11-02 10:56:16 +00:00

timmy

3e2253a052

wip(#19 ): privacy-safe model metrics in progress — preserved snapshot before nightly release

Local work in progress, not reviewed and not part of any PR. Committed only so the
nightly release can build from a clean main without discarding it.

2026-11-01 12:02:43 +00:00