docs: add SRE root cause accuracy evaluator page - #852
Conversation
docs(command-center): add overview video to the Agent Command Center page
docs(command-center): autoplay overview video on #watch links
Dev to main, 26th June, 2026
Dev to main, 1st July, 2026
Dev to main, 6th July, 2026
Dev to main, 10th July, 2026
Dev to main, 16th July, 2026
Dev to main, 16th July, 2026
Dev to main, 16th July, 2026
Dev to main, 16th July, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Wipe the fictional v1.0.0–v2.0.0 entries so the page starts empty, ready for the first real automated release below the insert marker. Drop the now unused Callout import. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Add escapeMdx() and apply it to bullet lines in mapped sections and
breaking-changes lines so <, { and } in release notes can't break the MDX
build. Add a test covering the escaping and a lockstep comment tying
SECTION_MAP to release-please-config.json.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…angelog The sync was pointed at src/pages/changelog.mdx — orphan scaffold with no navigation links. The real, actively maintained surface is src/pages/docs/release-notes.mdx (weekly product-voice entries). Transform now emits that page's exact format (styled wrapper + Features / Bugs/Improvements / Breaking Changes subsections, Bug Fixes + Performance merged into the existing Bugs/Improvements bucket) and inserts new versions on top of the existing entries. Orphan changelog.mdx deleted. Tests: 5/5. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner decision: this PR no longer touches the changelog page at all — neither deletion nor placeholder wipe. It is restored byte-identical to main. The release-notes sync is unaffected (targets docs/release-notes.mdx). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ci(changelog): sync docs changelog from platform releases
…UB_TOKEN The org forbids GitHub Actions from creating PRs with GITHUB_TOKEN; App installation tokens are exempt (release bot App already installed on this repo). Mint a scoped token and use it for both the branch push and gh pr create — consistent with how future-agi opens its release PRs, and avoids relaxing the org-wide setting. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…c-app-token ci(changelog): open release-notes PR with App token (not GITHUB_TOKEN)
Dev to main, 10th Aug, 2026
Dev to main, 13th August, 2026
Dev to main, 14th Aug, 2026
Dev to main, 14th August, 2026
Dev to main, 14th Aug, 2026
Dev to main, 17th August, 2026
Dev to main, 17th August, 2026
Dev to main, 18th Aug, 2026
Dev to main, 19th Aug, 2026
…2026-07-to-08 docs(release-notes): add weeks of Jul 22 to Aug 10, 2026
Dev to main, 25th Aug, 2026
Dev to main, 27th Aug, 2026
Dev to main, 7th Sep, 2026
|
Hello @NivedhN160, |
|
Thanks @khushalsonawat — you're right. There is no Root Cause Accuracy evaluator in the monorepo yet. I don't have a monorepo PR open for it. Happy to open one that adds SRERootCauseAccuracy under futureagi/agentic_eval/core_evals/fi_evals/ and register it in eval_type.py, then keep this docs PR in sync (or close this and reopen after the evaluator merges). Should I open the monorepo issue/PR first, or is there an internal design you want aligned before implementation? |
|
@NivedhN160, |
|
Understood — thanks for clarifying. Built-in templates are internal-only. I'll close this PR. For the root-cause use case I'll use a custom eval via the guide you linked instead of proposing a new built-in. |
Adds documentation page for SRE root cause accuracy evaluator.