GareArc 058fa95517 feat: expose enterprise_enabled and gate the community edition tip on it ...

The sandbox isolation caveat was suppressed by inspecting license.status,
which answers a different question: a lapsed enterprise licence would start
showing a community edition warning that still does not apply, because sandbox
isolation is a property of how the deployment was built, not of billing state.

ENTERPRISE_ENABLED already drives branding, webapp auth and the plugin manager
in get_system_features, but was never surfaced, leaving the frontend to infer
the edition from side effects. Expose it alongside rbac_enabled and read it
directly, which drops the license status set entirely.

2026-07-21 01:34:28 -07:00

..

account-profile

chore: migrate linting to vp lint with ESLint fallback (#38834)

2026-07-13 06:41:53 +00:00

agent-v2

feat: expose enterprise_enabled and gate the community edition tip on it

2026-07-21 01:34:28 -07:00

deployments

test(web): align test state boundaries (#39239)

2026-07-20 06:06:17 +00:00

system-features

feat: expose enterprise_enabled and gate the community edition tip on it

2026-07-21 01:34:28 -07:00

tag-management

test(web): align test state boundaries (#39239)

2026-07-20 06:06:17 +00:00