docs: document OMNIGENT_FEATURES release feature flags

[omnigent-ci]

Documentation update for omnigent-ai/omnigent#4775 — feat(server): add deployment-wide release feature flags

Changes documented

• app/docs/deploy/feature-flags/page.mdx — new page documenting deployment-wide release features: the OMNIGENT_FEATURES env var, default-off behavior, unknown-key startup failure, the usage_page and harness_install keys (with review-by-release 0.11.0), the removed OMNIGENT_HARNESS_INSTALL_ENABLED var + migration hint, the GET /v1/info features map, the web-app reload requirement, per-platform enablement (Docker/Kubernetes/Railway/Render/Databricks --features), and rollout/rollback steps.
• components/DocsSidebarFull.js — added a "Release Features" entry (/docs/deploy/feature-flags) to the Collaboration section, next to the other deploy pages.

Manual review needed

• app/docs/deploy/feature-flags placement — I filed the new page under the "Collaboration" sidebar section (which already groups the deploy/shared-server pages). A reviewer may prefer it under "Reference" alongside "Usage Telemetry"; either is defensible.
• app/docs/interact/web-ui — the PR gates the web Usage page and sidebar navigation behind usage_page. If any interface/web-ui doc shows or references a Usage page as always-present, it may now need a "release-feature-gated" note. I did not find such a reference (grep for "Usage"//v1/info hit only the harnesses page, unrelated), so I made no edit — worth a human confirming no screenshot or nav description implies Usage is always visible.

---

Source PR: omnigent-ai/omnigent#4775 · merged by @fanzeyi
_{Drafted automatically by the doc-sync workflow. Review for accuracy before merging.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
omnigent-site	Ready	Preview	Aug 14, 2026 6:01pm