docs(ai): close evaluated RAG routing rollout

[kl3inIT]

Summary

• make the evaluated production split durable: Answer gpt-5.6-sol, Keyword gpt-5.6-luna/none, Graph gpt-5.4-mini
• preserve reasoning route values in the shared-ZM export
• archive the completed RAG routing and Graph route increments and reconcile roadmap/specs/runbook

Verification

• production Compose config resolves the approved route values
• test-export-team-dev-config.sh
• pnpm check:docs
• pnpm release:check
• ZM runtime, queue, memory-limit, Prometheus, Loki, Grafana, and Alloy inspection

Summary by CodeRabbit

• Configuration

  • Updated production AI model defaults for answer generation, keyword planning, and graph extraction.
  • Enabled configurable reasoning-effort settings, including no reasoning for keyword planning.
  • Improved environment configuration guidance for official and compatible AI gateways.

• Documentation

  • Documented the verified production model routes and reasoning settings.

• Development Tools

  • Development configuration exports now include AI reasoning-effort settings.
  • Added validation for exporting configured and empty reasoning values.

[coderabbitai]

Warning

Review limit reached

@kl3inIT, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a6339034-12de-4a83-a94b-d378b1857d65

📥 Commits

Reviewing files that changed from the base of the PR and between fdb5e6e and 6bebec0.

📒 Files selected for processing (1)

• .tegami/evaluated-rag-production-routes.md

📝 Walkthrough

Walkthrough

The change updates production OpenAI model routing, enables reasoning-effort configuration, and exports the related variables to development configuration payloads. Tests verify populated and empty reasoning-effort values.

Changes

OpenAI routing configuration

Layer / File(s)	Summary
Production routing defaults ARCHITECTURE.md, infrastructure/deployment/compose.production.yaml, infrastructure/deployment/production.env.example	Documents and configures gpt-5.6-luna for keyword processing. Enables reasoning-effort support and sets keyword reasoning effort to none.
Development configuration export infrastructure/deployment/scripts/export-team-dev-config.sh, infrastructure/deployment/scripts/test-export-team-dev-config.sh	Exports general, keyword, and graph extraction reasoning-effort variables. Tests verify their values, including an empty value.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• kl3inIT/OrgMemory#272: Updates production defaults and export handling for OpenAI reasoning-effort routing.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the completion of the evaluated RAG routing rollout, which matches the primary purpose of the changes.
Description check	✅ Passed	The description includes relevant summary and verification details, but it omits the required Documentation impact section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/rag-workload-routing-luna-closeout

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Tegami

This repository uses Tegami to manage releases. When your changes affect published packages, add a changelog file under .tegami/ before merging.

Create a changelog → · Changelog format

Release preview

Package	Bump	Version
orgmemory	minor	0.1.1 → 0.2.0

Changelogs in this PR

Changelog	Title
evaluated-rag-production-routes.md	Improvements

Run pnpm run tegami locally to create a changelog interactively.

_{Managed by Tegami.}