65 lines
6.9 KiB
Markdown
65 lines
6.9 KiB
Markdown
# Task: Back up and revert extension update iteration
|
|
|
|
## Identity
|
|
|
|
- Task ID: 20260903-backup-revert-extension-update-c71a4e92
|
|
- Mode: Integration
|
|
- Branch: codex/20260903-finalize-extension-update-a6c4e192-finalize-extension-update
|
|
- Worktree: /Users/inmanx/Documents/lwltAPI-finalize-extension-update-a6c4e192
|
|
- Base commit: b2e33e2e5d29138891eabc93969cf24907492dfe
|
|
- Owner: codex
|
|
- Status: Integrated and pushed
|
|
|
|
## Scope
|
|
|
|
- Preserve the complete extension-update iteration currently at remote `main` commit `b2e33e2` on a dedicated remote backup branch before changing `main`.
|
|
- Revert the central-service automatic-update orchestration carried by merge `3224758` through normal history-preserving commits, while retaining the released Chrome extension `0.5.167`, its adaptive ERP readiness behavior, dormant idle/reload safety protocol, synchronized mappings, tests, ZIP, archive, and release manifest.
|
|
- Preserve the source and integration task records as historical evidence, mark accepted decision `EXT-001` as reverted, and reconcile canonical project memory to the restored active architecture.
|
|
- Run the complete repository, release, document, test, and build gates, then advance remote `main` with a normal non-force push.
|
|
|
|
## Intent And Constraints
|
|
|
|
- The user explicitly requested a branch backup followed by rollback of this plugin-update iteration. This supplies the required human decision to reverse accepted architecture and product behavior.
|
|
- The exact backup ref is `codex/backup-extension-update-20260903-b2e33e2`; it must resolve remotely to `b2e33e2e5d29138891eabc93969cf24907492dfe` before the rollback continues.
|
|
- The user's correction establishes the intended boundary: extension `0.5.167` remains current. Remove the central OSS/ECS Cloud Assistant service implementation, account/host UI, dependencies, configuration and migration 019, but keep the exact published `0.5.167` plugin bytes and the `0.5.166` adaptive ERP entry readiness they contain. Required database migration remains 018.
|
|
- Do not create a second payload under version `0.5.167`. Restore the exact source and ZIP from merge `3224758`, SHA-256 `6822ec660097a8889da8ea4fa22d4091467aa022067bff3bee2ac5406864b679`; the plugin-side update messages remain dormant because the current platform/server does not trigger them.
|
|
- Use `git revert`, not a force push or history rewrite. Keep prior task records and the reverted ADR so the decision trail remains auditable and recoverable from the backup branch.
|
|
- The local `main` checkout is owned by task `20260902-migrate-restart-confirmed-4f8c2a71` and contains its untracked task record. Do not alter, adopt, stash, reset, or clean that worktree.
|
|
- Do not deploy, restart, migrate a database, access ERP, publish to OSS, invoke Cloud Assistant, reload Chrome, mutate live tasks, or inspect secrets.
|
|
|
|
## Outcome
|
|
|
|
- Remote backup branch `codex/backup-extension-update-20260903-b2e33e2` was created first and independently verified at exact commit `b2e33e2e5d29138891eabc93969cf24907492dfe`.
|
|
- The first rollback commit `81a0cda` was too broad: it restored extension `0.5.165` together with the service baseline. After the user clarified that the plugin must remain `0.5.167`, this task resumed to correct that scope without rewriting either commit or remote history.
|
|
- Restored the exact extension `0.5.167` source/package from merge `3224758`, including adaptive list-entry readiness and its dormant idle/reload safety handlers; synchronized the platform minimum version, mappings, business/release documentation, focused tests, archived prior releases, and `dist/release-manifest.json`.
|
|
- 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`.
|
|
- 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
|
|
|
|
- `git ls-remote --heads origin refs/heads/codex/backup-extension-update-20260903-b2e33e2`: returned exact commit `b2e33e2e5d29138891eabc93969cf24907492dfe`.
|
|
- `npm ci --no-audit --no-fund`: completed from the restored lockfile.
|
|
- `node --run check:repo`: 10/10 passed, including exact release-set hashes and extension ZIP/source equality.
|
|
- `node --run check`: passed.
|
|
- `node --run test:control-plane`: 162/162 passed.
|
|
- `node --run test:legacy`: 270/270 passed, including adaptive entry readiness and dormant `0.5.167` plugin idle/reload safety coverage.
|
|
- `node --run build`: passed.
|
|
- `node --check` passed for extension `background.js`, `business-bridge.js`, and `inpage.js`.
|
|
- `unzip -t dist/ltjt-order-assistant-0.5.167.zip`: passed; SHA-256 is `6822ec660097a8889da8ea4fa22d4091467aa022067bff3bee2ac5406864b679` and equals both the release manifest and the package at merge `3224758`.
|
|
- Exact path comparisons against `3224758` passed for the extension source, current/archived release packages, release manifest, lifecycle/plan mappings, and shared-plan business contract.
|
|
- 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.
|
|
- Post-push fetch and `git ls-remote` returned remote `main` at `fe1cc2cddc29e4dead81e53c16d31bb71493602d` and the backup branch at exact commit `b2e33e2e5d29138891eabc93969cf24907492dfe`.
|
|
|
|
## Follow-ups
|
|
|
|
- The full server-side automatic-update implementation remains available on the named backup branch. The active `0.5.167` plugin continues to use the existing manual publication/loading workflow unless a future explicit decision revives server orchestration.
|
|
|
|
## Promotion Candidates
|
|
|
|
- None recorded.
|