docs: record extension rollback correction

This commit is contained in:
inman
2026-09-03 17:33:27 +08:00
parent fe1cc2cddc
commit f4664997a8
2 changed files with 4 additions and 4 deletions

View File

@@ -4,7 +4,7 @@ This file is the integrated default-branch snapshot. Feature tasks record progre
## Integrated Through
- Rollback/correction task `20260903-backup-revert-extension-update-c71a4e92` preserved the complete former `0.5.167`/migration-019 stack at remote branch `codex/backup-extension-update-20260903-b2e33e2`, removed the central private-OSS/ECS automatic-update service architecture without rewriting history, and retained the exact Chrome extension `0.5.167` source/package on the active main line with migration 018.
- Correction commit `fe1cc2cddc29e4dead81e53c16d31bb71493602d` from integration task `20260903-backup-revert-extension-update-c71a4e92` preserved the complete former `0.5.167`/migration-019 stack at remote branch `codex/backup-extension-update-20260903-b2e33e2`, removed the central private-OSS/ECS automatic-update service architecture without rewriting history, and retained the exact Chrome extension `0.5.167` source/package on the active main line with migration 018.
- Merge commit `3224758` and integration task `20260903-finalize-extension-update-a6c4e192` remain historical records of the full-stack extension-update design. Only the plugin `0.5.167` release, adaptive entry readiness, and dormant plugin-side idle/reload safeguards remain active; the server orchestration is preserved on the backup branch only.
- Commit `c4c469f4441d744627af2d34abe693b6783e833c` for the independently advanced remote deployment/extension line.
- Commit `cd45ce17d0fcd25f7fa89ab9f8a391d3e904ecdf` for WeChat attachment correlation and privacy-safe server diagnostics.

View File

@@ -8,7 +8,7 @@
- Worktree: /Users/inmanx/Documents/lwltAPI-finalize-extension-update-a6c4e192
- Base commit: b2e33e2e5d29138891eabc93969cf24907492dfe
- Owner: codex
- Status: Correction verified; push pending
- Status: Integrated and pushed
## Scope
@@ -35,7 +35,7 @@
- Kept required schema migration `018_agentbus_account_workers`; migration 019, central OSS/ECS update orchestration, update endpoints/poller, account-to-ECS fields/UI, Alibaba SDK dependencies and production update configuration remain removed from the main-line result.
- Marked `EXT-001` as Reverted and reconciled the decision index, system overview, data flow, current state, task history, evidence index, and rollout commitment.
- Created rollback commit `81a0cdac8ea4be867ab43d0a84ffa547d159223d`. After a fresh fetch proved `origin/main` was still exactly `b2e33e2` and an ancestor of the rollback commit, a normal non-force push advanced remote `main` to `81a0cda`.
- Prepared a forward correction that retains the exact `0.5.167` plugin release while leaving the central updater rollback intact; commit and non-force push are pending.
- Created forward correction commit `fe1cc2cddc29e4dead81e53c16d31bb71493602d`, retaining the exact `0.5.167` plugin release while leaving the central updater rollback intact. After a fresh fetch proved `origin/main` was still exactly `95a0d06` and an ancestor of the correction, a normal non-force push advanced remote `main` to `fe1cc2c`.
- No production deployment, service restart, database migration, OSS publication, ECS command, Chrome reload, ERP access, live task mutation, history rewrite, or secret access occurred.
## Verification
@@ -53,7 +53,7 @@
- Exact path comparisons against pre-updater baseline `f52d9d7` passed for the control plane, dependency manifests, production environment example, and platform HTML/styles. Platform JavaScript differs only by the required extension version `0.5.167`.
- Explicit architecture checks returned required migration `018_agentbus_account_workers` and confirmed migration 019, `extension-updates.ts`, update endpoints/poller, account-to-ECS fields/UI, Alibaba SDK dependencies, and production updater configuration are absent.
- `check_project_docs.py`, `check_doc_drift.py --task-id 20260903-backup-revert-extension-update-c71a4e92`, and `git diff --check`: passed before commit.
- The initial rollback push was verified with remote `main` at `81a0cdac8ea4be867ab43d0a84ffa547d159223d`; final correction push verification remains pending. The remote backup branch remains at exact commit `b2e33e2e5d29138891eabc93969cf24907492dfe`.
- Post-push fetch and `git ls-remote` returned remote `main` at `fe1cc2cddc29e4dead81e53c16d31bb71493602d` and the backup branch at exact commit `b2e33e2e5d29138891eabc93969cf24907492dfe`.
## Follow-ups