chore: promote analytics dashboard fix to production#315
Merged
heybeaux merged 5 commits intoJul 2, 2026
Conversation
…estion and trust reports Introduce a first-class delegation ledger that unifies how tasks pass between agents and how trust is earned from evidence rather than prose. - schema: DelegationEvent (append-only lifecycle/AOP-Sonder log), DelegationValidation (Lattice StateContract + validation evidence), DelegationReceipt (Receipts proof-of-work + integrity status) - migration incl. RLS policies + engram_app grants - DelegationLedgerService: event recording, Lattice validation ingestion, receipt attach w/ SHA-256 payload integrity check, evidence-based trust signals, per-task and per-agent trust reports - lifecycle hooks: contract/task create+status changes emit events - API: /v1/delegation/events, /contracts/:id/validations, /tasks/:id/receipts, /tasks/:id/trust-report, /trust-reports/:agentId - tests: 8 suites / 57 tests (ledger, controller, lifecycle, trust rules)
…alytics-to-production-20260702
|
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: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Contributor
✅ Recall Benchmark ResultsFull outputCommit: 27e7f6f |
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
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
stagingtoproductionafter the analytics date_trunc grouping fix landed in PR fix: repair analytics date_trunc grouping #313478bc75Why
Authenticated production dashboard QA still shows
/analyticsreturning 500s from:GET /v1/analytics/summaryGET /v1/analytics/timelineGET /v1/analytics/breakdown/typeGET /v1/analytics/breakdown/layer?includeTrend=trueProduction is still at
11bb548and contains the old repeatedGROUP BY date_trunc(${intervalLiteral}, created_at)SQL. Staging is at478bc75and contains PR #313's bucket-subquery fix.Verification
/sessionsload passed,/ensemble/driftAnalyze passed,/analyticsstill fails with four 500s.Safety
Normal protected promotion PR; do not bypass required reviews/checks.