## Related issue
Follow-up to #4673.
## Summary
- Add a typed, default-off release-feature registry driven by one comma-separated `OMNIGENT_FEATURES` environment variable, with strict validation and lifecycle metadata.
- Gate the web Usage route/navigation and page-only report enrichment while preserving the existing `GET /v1/usage` CLI API.
- Migrate web-driven harness installation to the same immutable startup snapshot and wire rollout configuration across Docker, Kubernetes, Render, Railway, and Databricks.
ELI5: the server reads one list of enabled features when it starts, enforces that same list on backend routes, and tells the web app which controls and pages to show.
```text
OMNIGENT_FEATURES
|
v
FeatureFlags snapshot
/ \
backend gates GET /v1/info
|
v
frontend gates
```
## Test Plan
- `uv run pytest tests/server/test_feature_flags.py tests/host/test_local_server.py tests/server/integration/test_utility_endpoints.py tests/server/integration/test_hosts_install_harness.py tests/server/integration/test_hosts_store_credential.py tests/server/routes/test_usage_report.py tests/server/test_openapi_drift.py -q`
- `cd web && pnpm vitest run src/lib/capabilities.test.ts src/lib/harnessSetup.test.ts src/App.test.tsx src/shell/Sidebar.test.tsx`
- `uv run pytest tests/e2e_ui/sessions/test_usage_page_feature.py -q`
- `uv run python scripts/dump_openapi.py --check`
- `pre-commit run --files <changed files>`
- Verified default-off and enabled Usage route/sidebar behavior, strict unknown-feature rejection, legacy CLI usage compatibility, and harness route enforcement.
## Demo
- Default off: the updated visual baselines show the original sidebar without the Usage row.
- Enabled Usage page: https://github.com/user-attachments/assets/8385d4f0-47ad-430f-bf2c-06c35af6c499
## Type of change
- [ ] Bug fix
- [x] Feature
- [x] UI / frontend change
- [ ] Refactor / chore
- [x] Docs
- [ ] Test / CI
- [ ] Breaking change
## Test coverage
- [x] Unit tests added / updated
- [x] Integration tests added / updated
- [x] E2E tests added / updated
- [x] Manual verification completed
- [x] Existing tests cover this change
- [ ] Not applicable
## Coverage notes
Manually reviewed the default-off visual output and verified that the Usage route is absent while the capability is disabled. Targeted backend and frontend tests cover both flag states, capability parsing, startup snapshots, and harness enforcement.
## Changelog
Usage and web-driven harness setup can now be enabled per deployment with `OMNIGENT_FEATURES`.
Signed-off-by: Zeyi (Rice) Fan <zeyi.f@databricks.com>
Now that Omnigent on Databricks (Beta) is GA-track and managed by
Databricks, most Databricks customers should use it rather than
self-deploying the server. Add a recommendation callout to the three
Databricks-facing docs (the integration guide, the deploy menu, and the
Apps bundle README), framing the existing Apps bundle as the
self-managed path for cases the managed service does not cover yet
(region availability, custom YAML policies, BYO provider keys, custom
egress).
Co-authored-by: Isaac
* docs(deploy): add Databricks Apps deployment guide
OSS shipped the `databricks` extra and DatabricksVolumesArtifactStore but
not the deploy guide (deploy/databricks/ is excluded from the internal→OSS
export). Three dangling references pointed at the missing dir
(pyproject.toml psycopg comment + two .gitignore lines).
Add a genericized deploy/databricks/ — deploy.py, build.sh, grant_sp_perms.py,
databricks.yml, src/app.py, src/app.yaml, README.md — with internal infra
scrubbed: public PyPI (honors UV_INDEX_URL), example.databricks.com host, no
influencer target, generic app/profile names. Drops the internal CD-ops
SKILL.md.
Wire it into deploy/README.md (menu row + tree). Fix a self-contradicting
.gitignore line that ignored deploy/databricks/**/*.whl despite the adjacent
comment — it would have broken `bundle deploy` file sync.
Co-authored-by: Isaac
* fix(deploy): address Databricks deploy review comments
- deploy.py: drop dead `backups = {}` reassignment in main()'s finally
(flagged by code-quality bot).
- grant_sp_perms.py: build psycopg connection params as keyword args
instead of interpolating the Lakebase OAuth token into a conninfo
string, so token contents can't be mis-parsed.
- README.md: fix first-time setup ordering — the SP grant requires the
app/SP, which only exist after an initial deploy; make the
deploy → grant → redeploy sequence explicit. Clarify the Lakebase
resource-slug (databricks-postgres) vs SQL dbname (databricks_postgres)
mapping. Document the X-Forwarded-Email / header-auth trust boundary.
Co-authored-by: Isaac
* style(deploy): ruff-format deploy.py
Reflow a help string that fits on one line after shortening the
example app name. No behavior change.
Co-authored-by: Isaac
Zeyi (Rice) Fan