SILVER/NODEDC_PLATFORM
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

feat(ai-workspace): support SEO codex provider bridge

Browse Source
This commit is contained in:
Codex
2026-07-03 08:43:37 +03:00
parent 1aceabee44
commit a7c6c34c82
26 changed files with 1649 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/AI_WORKSPACE_CONFIG_CONTRACT.md
+29
View File
@@ -27,6 +27,18 @@ Do not mix these classes. A URL reachable from the Mac browser is not automatica
- The deployed AI Hub is allowed only as transport. Launcher, Engine, Ops, Authentik, task manager, and downstream app calls must stay local.
- The remote worker must not call product apps directly. Assistant actions must route back through the local AI Workspace Assistant.
`local-seo/deployed-hub-control-plane`:
- SEO frontend: `http://127.0.0.1:5177`
- SEO backend: `http://127.0.0.1:4100`
- SEO AI Workspace profile: `deployed-hub`
- SEO backend Assistant-compatible control-plane URL: `SEO_AI_WORKSPACE_CONTROL_URL=https://ai-hub.nodedc.ru`
- SEO backend control-plane token: `SEO_AI_WORKSPACE_CONTROL_TOKEN`, accepted by the public Hub server-side API.
- Worker-facing Hub: `wss://ai-hub.nodedc.ru/api/ai-workspace/hub`
- Public Hub exposes only token-gated Assistant control-plane proxy endpoints required by SEO model-provider setup, probe, thread dispatch, and message polling.
- Public Hub must proxy those calls to internal Platform Assistant with server-side internal token. Browser clients and remote workers must not receive the Hub internal token or Assistant token.
- This profile is for local SEO development against the deployed AI Workspace service plane. It is not the same as `local`, and it must not silently fall back to localhost or product app URLs.
`synology/prod-public`:
- Browser Launcher: `https://hub.nodedc.ru`
@@ -57,6 +69,23 @@ New apps must join AI Workspace through app manifests/config/adapters:
Do not add app-specific address logic to the agent installer, Engine, Ops, or Platform Assistant runtime flow.
### NDC SEO Mode
`seo-mode` is a first-class AI Workspace surface, not `global`.
Local SEO testing should keep SEO app/backend on fixed local ports while using the configured AI Workspace transport/profile:
- SEO frontend: `http://127.0.0.1:5177`
- SEO backend: `http://127.0.0.1:4100`
- SEO model-provider surface: `seo-mode`
- SEO model task mode: `seo-model-task`
- Worker-facing transport: public AI Hub relay when selected by profile, normally `wss://ai-hub.nodedc.ru/api/ai-workspace/hub`
- SEO task payload: sanitized `seo-model-task` contract only
The SEO backend must select profiles through env/config, not code edits. Local and deploy-host may use different Assistant URLs, executor ids, setup commands, model defaults, and app grants, but the request contract stays the same.
Remote Codex for SEO must not receive Wordstat/Yandex credentials, product app tokens, unrestricted repo access, rewrite/apply actions, or destructive actions. Wordstat/SERP collection remains SEO-backend-owned.
## Verification
Before changing worker, Assistant, Hub, or app adapter routing, run: