wangxuming/LWLT-AIBOT
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: keep extension 0.5.167 after updater rollback

Browse Source
This commit is contained in:
inman committed 2026-09-03 17:31:48 +08:00
1 parent 95a0d06fde
commit fe1cc2cddc
27 files changed
+389 -51
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

.project-docs/10-decisions/EXT-001-central-service-host-extension-updates.md
+2 -2
View File
@@ -10,9 +10,9 @@ Reverted
## Reversal
On 2026-09-03 the user explicitly directed that this iteration be backed up and removed from the main branch. The exact integrated state at commit `b2e33e2e5d29138891eabc93969cf24907492dfe` is preserved on remote branch `codex/backup-extension-update-20260903-b2e33e2`; active `main` restores the pre-iteration extension `0.5.165` and migration 018 baseline through a normal revert of merge `3224758`.
On 2026-09-03 the user explicitly directed that this iteration be backed up and its server-side automatic-update architecture removed from the main branch, then clarified that the Chrome plugin itself must remain at `0.5.167`. The exact full-stack state at commit `b2e33e2e5d29138891eabc93969cf24907492dfe` is preserved on remote branch `codex/backup-extension-update-20260903-b2e33e2`; active `main` keeps the exact `0.5.167` plugin source/package but restores the control plane to migration 018 with no private-OSS/ECS update orchestration.
This ADR is retained only as historical design context and no longer governs the active architecture. The reverted code was never deployed, migration 019 was not applied, no OSS extension release was published, and no Cloud Assistant or Chrome reload action was performed by these repository tasks.
This ADR is retained only as historical server-architecture context and no longer governs the active control plane. Plugin-side idle proof and guarded reload handlers remain as dormant `0.5.167` capabilities with no current server/platform trigger. The reverted server code was never deployed, migration 019 was not applied, no OSS extension release was published, and no Cloud Assistant or Chrome reload action was performed by these repository tasks.
## Context
.project-docs/10-decisions/decision-index.md
+1 -1
View File
@@ -19,7 +19,7 @@
|---|---|---|---|
| DOC-LEGACY-001 | Root `task_plan.md`, `findings.md`, and `progress.md` were the active project-memory system. | DOC-001 | 2026-08-28 |
| AUTH-001 (partial) | Organization-wide ERP FIFO and archive-only operator removal. | AUTH-002 | 2026-09-03 |
| EXT-001 | Central-service private-OSS and ECS Cloud Assistant orchestration for shared unpacked-extension updates. | Reverted by explicit user decision; exact implementation preserved on `codex/backup-extension-update-20260903-b2e33e2`. | 2026-09-03 |
| EXT-001 | Central-service private-OSS and ECS Cloud Assistant orchestration for shared unpacked-extension updates. | Server architecture reverted by explicit user decision; exact full implementation is preserved on `codex/backup-extension-update-20260903-b2e33e2`, while plugin `0.5.167` remains current. | 2026-09-03 |
## Decision Criteria