docs: record point wallet worktree cleanup failure

This commit is contained in:
2026-09-22 12:06:25 +08:00
parent 88800f9223
commit 0cf67befb5

View File

@@ -35,7 +35,9 @@
- Fast-forwarded main from 2f82b9f79cf72873d75c17a48853292323aa5df5 to a1cce428afcca9b7e32ef043705a25a4685fbbdd with no conflicts. Product files and the imported source task record are unchanged from that source.
- Promoted the user-confirmed permanent-point policy into current-state, business-rules and decision-index; replaced obsolete membership/reset-card descriptions in system-overview, module-map and data-flow. Recorded actual source provenance under Integrated Through; historical task records remain intact.
- Official drift validation confirms the three adopted foreign task documents remain at their approved original states. They remain untracked and excluded from the integration commit.
- Source worktree remains clean, managed and ready_for_integration, with its latest a1cce42 included in main. Only that just-integrated source is eligible for the required separate cleanup offer; primary and other task worktrees are retained.
- Before cleanup, verified the source worktree was clean, managed and ready_for_integration, with its committed ready record and latest a1cce42 included in main. User then explicitly approved removal of this source worktree; primary and other task worktrees were excluded.
- Resumed this same integration task using official start/status and retained the passed planning context for the bounded cleanup. Confirmed the resolved target was exactly the approved child of D:\Datas\OthersProjects\.codex-worktrees\makelore, then ran official retire from primary. Git returned Directory not empty and the command exited 1. It partially removed the checkout and Git worktree registration, but retained residual files/directories and the node_modules junction. The source's .git marker and on-disk task record are now absent; the skill ownership/reservation state was retained on failure. No manual removal or registry bypass was attempted.
- Source branch still resolves to a1cce428afcca9b7e32ef043705a25a4685fbbdd and remains included in main. Primary tracked files are unchanged; the same three unrelated documents remain untracked. Merge/documentation commit 88800f9 completed before the failed cleanup.
- Local merge only: no push, packaging, installation, deployment, real payment or subagent use.
## Verification
@@ -48,7 +50,7 @@
## Follow-ups
- Source checkout cleanup awaiting explicit confirmation: task 20260922-permanent-points-client-7f4c9a2e at D:\Datas\OthersProjects\.codex-worktrees\makelore\20260922-permanent-points-client-7f4c9a2e, branch codex/20260922-permanent-points-client-7f4c9a2e-permanent-points-client. If approved, use official retire from primary; preserve the branch/commit. Merge/handoff consent does not cover removal. No response keeps the worktree and does not block the completed merge.
- Source cleanup was approved but is blocked after partial Git removal: task 20260922-permanent-points-client-7f4c9a2e at D:\Datas\OthersProjects\.codex-worktrees\makelore\20260922-permanent-points-client-7f4c9a2e, branch codex/20260922-permanent-points-client-7f4c9a2e-permanent-points-client. Residual directory and stale local task registration require a supported recovery path; do not treat this as a clean usable worktree or retry ordinary retire without restoring its prerequisites. Branch/commit are preserved. This failure does not invalidate or block delivery of the completed main merge.
- Before release, deploy matching Works Square permanent-points API / 0094 migration and verify genuine registration, actual payment callbacks and configured desktop payment payload. PostgreSQL upgrade/concurrency and non-Windows packaged acceptance remain release work.
- Track the existing Pi v6/v7 test assertion and Main typecheck baseline independently.