From 8f6801d728fe899ad9ac3d52582031c80ac4154e Mon Sep 17 00:00:00 2001 From: ZKDplz <2646995705@qq.com> Date: Thu, 29 Oct 2026 16:24:32 +0800 Subject: [PATCH] docs(contributor): retire completed GH-A05 task Signed-off-by: ZKDplz <2646995705@qq.com> --- docs/development/contributor-tasks-history.md | 1 + docs/development/contributor-tasks.md | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development/contributor-tasks-history.md b/docs/development/contributor-tasks-history.md index 387e6cfe0f..c21f6361d4 100644 --- a/docs/development/contributor-tasks-history.md +++ b/docs/development/contributor-tasks-history.md @@ -16,6 +16,7 @@ names a possible shape; the anchor names the gap. | ID | Area | Task | Validation | | --- | --- | --- | --- | +| GH-A05 | state migration | Landed via [#4915](https://github.com/loopx-project/loopx/pull/4915): added explicit local-state migration with backup and rollback. Ordinary reads and upgrades preserve existing state locations. Issue [#4800](https://github.com/loopx-project/loopx/issues/4800) is closed. | See merged #4915 for the recorded migration/registry tests, DSH package/runtime checks and premerge validation. | | GH-C04 | docs | Landed: #3982 (merged 2026-09-06) synced the public timeline to tagged v0.5.4 evidence and completed the restart-host activation note beside the first-time PyPI install block; the #3301/#3566/#3556 install, ownership, activation-recovery, and extension-doctor alignment landed earlier via #3810. The `docs/release-readiness-v0.5.4` branch is absent from the remote because its work merged, so this row is history rather than an open claim. | `python3 examples/fresh-clone-quickstart-smoke.py`, `python3 examples/loopx-update-smoke.py`, `python3 examples/release/release-readiness-doc-smoke.py`, `python3 examples/release/release-version-contract-smoke.py`, and `loopx check --scan-path docs/product/release-readiness.md --scan-path CONTRIBUTING.md` | | GH-C06 | cli | Landed: #4659 owns `update` registration and dispatch, #4803 owns `goal-channel prepare-operation` and `deliver-operation`, and #4818 owns quota action selection. The public commands remain unchanged, each parent and extracted owner stays below its module budget, and no compatibility wrapper was added. | Command-specific smoke, `python3 examples/cli-command-module-size-ownership-command-modularization-smoke.py`, `python3 regression/cli-command-module-contract.py`, and focused pytest if rules move | | GH-C100 | state | Landed via #4422: the provider-neutral parity fixture drives the shipped file-backed `claim_work` executor through same-target competition, independent-target rebase, exact replay, operation-identity mismatch, and stale-generation rejection. The fixtures remain synthetic and public-safe. | `python3 -m pytest -q tests/control_plane/test_coordination_executor.py tests/control_plane/test_coordination_file_provider.py tests/control_plane/test_coordination_provider_parity.py` and `loopx check --scan-path loopx/control_plane/coordination --scan-path docs/architecture/rfcs/shared-goal-authority-state-provider-v0.md --scan-path docs/development/contributor-tasks.md` | diff --git a/docs/development/contributor-tasks.md b/docs/development/contributor-tasks.md index 73ddcca25f..b47884b69f 100644 --- a/docs/development/contributor-tasks.md +++ b/docs/development/contributor-tasks.md @@ -105,7 +105,6 @@ issue. | GH-A02 | S4/S10 · [#3927](https://github.com/loopx-project/loopx/issues/3927) | A Codex App automation that silently stops delivering scheduled prompts is indistinguishable from a healthy quiet goal; the owner learns days later. Exit: `loopx doctor` or the heartbeat readback reports a missed-delivery window as a typed diagnosis with the last observed tick. | `python3 -m pytest -q tests/test_doctor_installation_scope.py` plus a missed-window fixture; `loopx doctor --deep` readback | Needs design | | GH-A03 | S3 · [#4336](https://github.com/loopx-project/loopx/issues/4336) | Issue #4336 was closed, while [#4397](https://github.com/loopx-project/loopx/pull/4397) remains open with requested changes and [#5162](https://github.com/loopx-project/loopx/pull/5162) closed without merge. Typed progress already owns the runtime rule. Exit: reconcile the closed issue with the current PR review before claiming another regression is required; retain one canonical negative case and upgrade guidance only if that review confirms the gap. | Current `quota should-run` typed/prose regression and the existing PR's focused tests; exact-head review readback | Blocked: closed issue and PR review reconciliation | | GH-A04 | S5 · [#4381](https://github.com/loopx-project/loopx/issues/4381) | Users have to open the dashboard to learn why a task is blocked and what unblocks it; the projection already knows. Exit: the existing blocker projection is delivered through the goal channel / status readback with the recovery action, without a second notifier. | `python3 examples/issue-fix-outcome-projection-smoke.py`, focused status readback smoke | Needs design | -| GH-A05 | S12 · [#4800](https://github.com/loopx-project/loopx/issues/4800) | The explicit `.loopx` migration PR [#4915](https://github.com/loopx-project/loopx/pull/4915) remains open with green CI, requested changes on its exact head, and a conflict with main. Exit: repair the reviewed real-CLI explicit-route regression and merge conflict, revalidate the default/legacy/conflict, migration and rollback contract, then obtain maintainer review and complete issue closeout; ordinary reads must not move existing state. | The existing PR's migration/SSH/registry tests, native Windows junction checks and clean-profile install/update smokes | Claimed | Closed defects that show the lane's shape: #4155 and #4997 (Windows), #4012 (macOS 26.5 app), #3796 / #3867 / #4195 (DSH plugin install), #4051