docs: integrate removed project reopening fix

This commit is contained in:
2026-09-21 15:46:31 +08:00
parent 6aa30a57b4
commit b5907e895c
3 changed files with 53 additions and 0 deletions

View File

@@ -0,0 +1,43 @@
# Task: Integrate removed project folder reopening into main
## Identity
- Task ID: 20260921-merge-readd-project-c82e9b
- Mode: Integration
- Branch: main
- Worktree: D:\Datas\OthersProjects\makelore
- Base commit: 576edb2720c00c317b931ea8d33076efae1a0925
- Owner: codex
- Status: Ready for Integration
## Scope
- Integrate completed source `6aa30a57b4dfd3af669db6e7f9a90175a9bdcbb7` into local main and promote the removed-project folder reopening rule.
## Intent And Constraints
- User explicitly confirmed releasing completed owner `20260921-merge-disabled-model-2209f56a` and adopting the three original untracked records unchanged. Official release/start/status passed; this task owns main and the exclusive integration lock.
- Concurrent Task Gate and Planning Gate Passed. Reread entry/own/source records and current domain/integrated state; reuse this conversation's same-base memory index, positioning, decision index, ADR-008, architecture, success criteria and relevant evidence/reflection/commitment context. Re-read 150 peer Scope/Intent/Promotion records and compared them with the preceding assessment; only the source task is newly ready. Historical placeholders remain unknown/read-only with no concrete conflicting dependency.
- Plan: fast-forward the exact completed source, promote compatible domain/current-state facts, verify product/source-record identity and documentation boundaries, then commit and complete this integration. Reuse the verified source tests if integration needs no product edits.
- Preserve original project identities/configurations, Agents, Conversations and disk files. Source records are read-only. No subagents, remote push, packaging, installation or deployment.
## Outcome
- Fast-forwarded local main from `576edb2720c00c317b931ea8d33076efae1a0925` to `6aa30a57b4dfd3af669db6e7f9a90175a9bdcbb7` without conflicts. Product and source task record are unchanged from the verified source result.
- Promoted ordinary direct-folder reopening, preserved disk data/identity, invalid-config rejection and unchanged child-directory/explicit-bind conflict rules to business-rules and current-state. These extend the existing ADR-008 configuration ownership without reversing any accepted decision.
- Original untracked documents `20260901-package-122-c5e8.md`, `20260901-package-123-d7f3.md` and `20260902-client-hang-diagnosis-a47c9e2b.md` remain unchanged and outside the integration commit.
## Verification
- Source branch/HEAD, committed Ready for Integration record and clean source worktree verified; the actual main branch contains its latest result through a direct fast-forward. `git diff --exit-code 6aa30a5 HEAD` passed immediately after merge.
- Reused exact-source results because this integration changes only canonical documentation: 43 focused unit tests, 2 real Electron project-identity flows, standard typecheck, scoped ESLint and all Vite production targets passed. Extra strict Main-service compilation has the same single TS2322 at line 215 as the original baseline, with no new diagnostic.
- Task-aware documentation drift validates unchanged source-record import provenance, canonical write ownership and unchanged adopted foreign records. Diff checks cover unintended content/whitespace changes. No full unrelated suite, installed-package or native macOS/Linux certification is claimed.
## Follow-ups
- Source cleanup awaiting explicit confirmation: task `20260921-readd-project-8f4a2c`, managed worktree `D:\Datas\OthersProjects\.codex-worktrees\makelore\20260921-readd-project-8f4a2c`, branch `codex/20260921-readd-project-8f4a2c-readd-project`. Retain it unless approved; removal preserves the branch and commits while deleting the checkout and ignored build/dependency files.
- A rebuilt client is still needed to deliver this local main fix to installed users. No push, package, installation or deployment performed.
## Promotion Candidates
- Source proposal accepted and promoted to business-rules/current-state under the user's merge authorization. No remaining semantic conflict or promotion candidate.