Admin: guardrail-flag log + announcement send history - #92
Merged
Ravikxx merged 1 commit intoAug 24, 2026
Merged
Conversation
… admin Fresco 1.3's real-time output guardrail (judgeFlagged) fired with zero visibility into how often or why — this logs every verdict (SAFE and FLAG alike) to a new guardrail_flags table and exposes it at GET /admin/guardrail-flags, so false positives are spottable. Also records recipient_count/send_status/send_error on the announcements table from the /webhook/announce send, and exposes it via GET /admin/announcement-history — closes the exact blind spot that let a GitHub Actions run report "success" while the announcement email silently never queued. Also includes the already-verified Fresco 1.3 admin controls from earlier this session: usage boost / bulk usage reset, and model health / kill switch endpoints. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Ravikxx
added a commit
that referenced
this pull request
Aug 24, 2026
* feat: Remote phone-control pairing (RemoteRelay) + account/sandbox restructure * feat: publish remote-pairing (RemoteRelay) + account/sandbox restructure and worker renames (Lumen->Fresco, Veil->Glyph) * fix: close remote-relay sockets when the pairing TTL expires /remote/ws checked expires_at only at connection admission — once a socket was let through, RemoteRelay held it open and kept forwarding indefinitely, so a paired phone kept live remote-control access past the pairing's expiry. Threads expires_at through to the DO and uses a storage alarm (not setTimeout, which wouldn't survive DO eviction) to close both sockets at the deadline. Flagged by CodeRabbit on PR #90. * Add guardrail-flag observability log and announcement send-history to admin (#92) Fresco 1.3's real-time output guardrail (judgeFlagged) fired with zero visibility into how often or why — this logs every verdict (SAFE and FLAG alike) to a new guardrail_flags table and exposes it at GET /admin/guardrail-flags, so false positives are spottable. Also records recipient_count/send_status/send_error on the announcements table from the /webhook/announce send, and exposes it via GET /admin/announcement-history — closes the exact blind spot that let a GitHub Actions run report "success" while the announcement email silently never queued. Also includes the already-verified Fresco 1.3 admin controls from earlier this session: usage boost / bulk usage reset, and model health / kill switch endpoints. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
guardrail_flagstable +GET /admin/guardrail-flags: logs every Fresco 1.3 output-guardrail verdict (SAFE and FLAG), giving admin visibility into fire rate and false positives (previously logged nowhere).recipient_count/send_status/send_errorcolumns onannouncements+GET /admin/announcement-history: records whether an announcement email actually sent and to how many recipients, closing the blind spot behind a recent incident where a GitHub Actions run reported success but the email silently never queued.fresco13-upstream.jsrouting module.Base branch note: targets
feat/remote-pairing(#90), notmaster— this code was built on top of that branch's fresco/glyph file rename (lumen-upstream.js→fresco-upstream.jsetc.), which hasn't landed onmasteryet. A first attempt based onmasterfailed CI withERR_MODULE_NOT_FOUNDfor exactly that reason.Test plan
node --checkon all changed filesnpm test(only the 3 pre-existing unrelateddesktop-auth.test.mjsfailures, confirmed unrelated to this change)node:sqlitesmoke tests for all 4 new/changed migrations🤖 Generated with Claude Code