docs(ui): stop describing workers-ai as the live default reviewer

[JSONbored]

Summary

• Follow-up to refactor(ai): remove legacy workers-ai framing from live review features #3270/docs(ai): reword stale workers-ai-only comments across the review stack #3274. The AI review settings panel subtitle (apps/gittensory-ui/src/components/site/app-panels/ai-review-settings.tsx) said "Free Cloudflare Workers AI by default... Consensus blocking always uses the free models", and the AI summaries docs page (apps/gittensory-ui/src/routes/docs.ai-summaries.tsx) told operators they configure "one fixed Cloudflare Workers AI model (WORKERS_AI_SUMMARY_MODEL)". Workers AI has no live binding anywhere today — hosted or self-host (see CONVERGENCE_RUNBOOK.md).
• Reworded both to describe the operator's configured default reviewer generically instead of naming Workers AI specifically, and added a cross-link from the AI summaries docs page to the existing /docs/self-hosting-ai-providers page, which already accurately documents the real Codex/Claude Code/Ollama/OpenAI-compatible/Anthropic options.
• Copy-only change; no logic touched. The AiProvider = "anthropic" | "openai" selector in the settings panel is intentionally scoped to the separate hosted BYOK feature and was left as-is.

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• No issue linked — copy-only follow-up to refactor(ai): remove legacy workers-ai framing from live review features #3270, self-evident in scope.

Validation

• git diff --check
• npm run actionlint (via npm run test:ci)
• npm run typecheck
• npm run test:coverage — apps/** is not measured by Codecov; full suite green (8807 passed)
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:test — 64 passed, including the existing ai-review-settings.test.tsx suite (had to reword my first draft of the subtitle copy since "operator-configured" collided with an existing getByText(/configured/) assertion elsewhere on the panel)
• npm run ui:build
• npm audit --audit-level=moderate — 0 vulnerabilities
• Ran the full npm run test:ci gate locally — green

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests. — N/A
• API/OpenAPI/MCP behavior is updated and tested where needed. — N/A, no API/OpenAPI/MCP changes.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks. — text-only copy change, no data-fetching behavior touched.
• Visible UI changes include a UI Evidence section with hosted screenshots. — Verified both changes live in a local browser preview (the docs page render and the settings-panel unit test's rendered DOM), but could not produce a GitHub-hosted image URL to embed here (no gh command uploads an arbitrary attachment, and committing screenshots to the repo is against house rules). Happy to attach via a follow-up comment if there's a preferred upload path.
• Public docs/changelogs are updated where needed. — N/A, no changelog edit.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	649f81a	Commit Preview URL Branch Preview URL	Jul 05 2026, 12:28 AM

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-05 00:27:16 UTC}

2 files · 1 AI reviewer · 1 blocker · readiness 93/100 · CI green · clean

⏸️ Suggested Action - Manual Review

• Maintainer test expectations unmet — Add or update tests, or attach passing validation output that satisfies the maintainer's test expectations.

Review summary
This is a focused copy-only correction that removes stale Workers AI-specific wording from the AI settings panel and AI summaries docs. The added TanStack Link is imported in the changed file and CI has already verified the UI build/typecheck path. I do not see a reachable correctness defect in the visible diff.

Nits — 3 non-blocking

• nit: apps/gittensory-ui/src/components/site/app-panels/ai-review-settings.tsx:181 says "default reviewer" twice, and the singular phrasing can blur the existing consensus wording immediately below; use "configured reviewer pipeline" or "configured reviewers" if the implementation is not strictly one reviewer for every mode.
• apps/gittensory-ui/src/components/site/app-panels/ai-review-settings.tsx:181: consider tightening the subtitle to avoid repeating "default reviewer", for example: "Uses the operator's configured reviewer by default. Bring your own Anthropic/OpenAI key for a frontier-quality advisory write-up — your key, your provider account. Consensus blocking uses the configured reviewer pipeline and only applies to confirmed contributors."
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.

Concerns raised — review before merging

• Maintainer test expectations unmet — Add or update tests, or attach passing validation output that satisfies the maintainer's test expectations.

Signal	Result	Evidence
Code review	❌ 1 blocker	1 reviewer
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 56 registered-repo PR(s), 46 merged, 429 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 56 PR(s), 429 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 56 PR(s), 429 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• No action.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review