docs: document AI Workspace Engine entitlement adapter

This commit is contained in:
Codex 2026-06-24 22:03:44 +03:00
parent 7003efa75a
commit e11f9bd7e7
2 changed files with 4 additions and 1 deletions

View File

@ -134,6 +134,9 @@ or app-specific variables:
AI_WORKSPACE_OPS_ENTITLEMENT_URL=https://ops.example/api/ai-workspace/entitlements
AI_WORKSPACE_OPS_ENTITLEMENT_TOKEN=...
AI_WORKSPACE_OPS_ENTITLEMENT_REQUIRED=false
AI_WORKSPACE_ENGINE_ENTITLEMENT_URL=https://engine.example/api/ai-workspace/internal/v1/entitlements
AI_WORKSPACE_ENGINE_ENTITLEMENT_TOKEN=...
AI_WORKSPACE_ENGINE_ENTITLEMENT_REQUIRED=false
```
Adapter request body:

View File

@ -155,7 +155,7 @@ Scenarios:
- Engine user with Ops read grant opens an Ops-targeted run and can read the target card.
- Engine user with Ops write grant creates or updates in the target Ops project.
- Engine user without target Ops grant gets preflight denied and no token.
- Ops-origin run can call Engine-side context once the Engine entitlement adapter exists.
- Ops-origin run can call Engine-side context once `AI_WORKSPACE_ENGINE_ENTITLEMENT_URL` points at Engine `/api/ai-workspace/internal/v1/entitlements`.
- Admin grants a user a new project permission; new AI Workspace run receives it without reinstalling the agent.
- Admin revokes a project permission; new run token loses it and existing source-linked token grants stop resolving through deleted grants.