ci: enable UCI AI review and assist workflows

[alexander-sei]

What is the purpose of the change?

Adds CI automation (no documentation content changes). Ports sei-protocol/sei-chain#3651 — "Enable UCI AI review and assist" — to the docs repo so the same shared AI review/assist pipeline runs here.

Describe the changes to the documentation

Two new GitHub Actions workflows, each a thin caller of a sei-protocol/uci reusable workflow pinned to v0.0.12 (258d2c3216d54872b33ac07430d23c847fc239ca):

• .github/workflows/ai-assist.yml — AI Assistant, triggered on issue_comment, pull_request_review_comment, and pull_request_review. Gated to the sei-protocol/sei-core team.
• .github/workflows/ai-review.yml — AI Review, triggered on pull_request (opened, ready_for_review, synchronize, reopened).

Faithful to the source PR, with one deliberate deviation: enable-cursor stays false, but its inline comment is reworded to drop the sei-chain-specific claim that Cursor Bugbot is "currently enabled on repo" (unverified for this repo).

Notes

• allowed-team carries over unchanged. @sei-protocol/sei-core is the default owner in this repo's CODEOWNERS, so the same team gate applies.
• Verified both reusable workflows exist at the pinned ref and that v0.0.12 is the latest UCI release.
• Secrets dependency: both use secrets: inherit, so the pipeline relies on org-level secrets (API key / OIDC role) being available to sei-docs. If UCI was configured org-wide at sei-protocol this works as-is; if it was scoped per-repo on sei-chain, an org admin may need to grant sei-docs access.
• Scoped to just these two workflow files; unrelated in-progress changes in the working tree were intentionally excluded.

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
CI-only workflow wrappers with no application or docs content changes; operational risk is limited to inherited secrets and automated PR/issue comments from the UCI pipeline.

Overview
Adds two GitHub Actions entrypoints that delegate to shared sei-protocol/uci reusable workflows pinned at v0.0.12 (258d2c3216d54872b33ac07430d23c847fc239ca).

ai-assist.yml runs on issue/PR review comments and submitted PR reviews, with allowed-team: sei-protocol/sei-core and permissions to read contents and write issues/PRs plus id-token.

ai-review.yml runs on PR open, ready-for-review, sync, and reopen events, with enable-cursor: false to avoid overlapping with Cursor Bugbot if enabled. Both workflows use secrets: inherit for org-level UCI credentials.

^{Reviewed by Cursor Bugbot for commit 9f6f434. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
sei-docs	🟢 Ready	View Preview	Jul 12, 2026, 10:02 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[github-actions]

Adds two thin caller workflows (ai-assist.yml, ai-review.yml) that delegate to sei-protocol/uci reusable workflows pinned by full commit SHA. The change is clean and follows CI best practices (SHA-pinned refs, scoped permissions); only minor, non-blocking observations apply.

Findings: 0 blocking | 6 non-blocking | 0 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• REVIEW_GUIDELINES.md was empty/missing, so no repo-specific review standards were applied.
• The OpenAI Codex second-opinion file (codex-review.md) was empty — that pass produced no output.
• The Cursor second-opinion file (cursor-review.md) was empty — that pass produced no output.
• Both workflows use secrets: inherit together with id-token: write, and ai-assist.yml triggers on externally-controllable events (issue_comment, pull_request_review_comment). Access is gated to sei-protocol/sei-core via allowed-team, so this relies on the reusable workflow correctly enforcing that gate before using secrets/OIDC — worth confirming the upstream UCI workflow performs the team check before any privileged step.
• The PR description notes both workflows depend on org-level secrets (API key / OIDC role) being available to sei-docs; if UCI was scoped per-repo rather than org-wide, an admin may need to grant access for these to function.
• Consider adding concurrency groups to ai-review.yml so rapid synchronize pushes cancel superseded runs and avoid redundant/duplicate reviews (optional optimization).