docs: accept central extension update architecture
This commit is contained in:
@@ -9,6 +9,7 @@ Track future-facing memory: promised follow-ups, unfinished loops, timed checks,
|
||||
| 2026-08-28 | Resolve AgentBus OSS attachment rejection caused by private/reserved local DNS answers. | User scheduled integration and confirmed the environment is trusted internal networking | Integration task `20260831-integrate-server-diagnostics-8b42c6d1` | Completed in repository | Deploy/restart and run one live internal attachment verification only under separate authorization. |
|
||||
| 2026-09-02 | Roll out and stage-test AgentBus account workers, account-scoped queues, and force deletion. | Explicit authorization for database backup/migration, service restart, extension reload, account/channel configuration, staging traffic, and disposable task mutation | Future authorized rollout task | Pending authorization | Apply migration 018 and extension `0.5.165`; verify two employee accounts/cloud PCs, ERP identity mismatch, same-account worker conflict/FIFO, cross-account independence, 90-second failover, administrator executable-feed isolation, manual/AgentBus routing, and waiting/active force-delete cleanup. |
|
||||
| 2026-09-02 | Verify the integrated native product-search execution path. | Explicit authorization for extension reload and a guarded ERP preflight/retry | Future authorized rollout task | Pending authorization | Load extension `0.5.165`, confirm the runtime handshake, then verify deterministic product selection and normal write gates without automatically retrying the earlier failed task. |
|
||||
| 2026-09-03 | Bootstrap and canary the central extension-update channel. | Authorized production maintenance window with database backup, migration, service restart, per-profile Chrome access, restricted RAM/OSS configuration, exact ECS mappings, and a disposable higher extension version | Server operator plus future authorized rollout task | Pending rollout | Deploy with updates disabled; apply migration 019; load shared-directory bootstrap `0.5.167` in every profile; verify heartbeats; configure ECS mappings and least privilege; then enable and observe one host through waiting, running, deployed, reload, and verified before fleet rollout. |
|
||||
|
||||
## Use
|
||||
|
||||
|
||||
Reference in New Issue
Block a user