build(trial): preserve deployed source for knowledge refresh

This commit is contained in:
鲨鱼辣椒 committed 2026-10-13 14:29:33 +08:00
1 parent 8e0e52f30e
commit 2d4e44f4a0
42 files changed
+2321 -283

No files matched your search

@@ -8,7 +8,7 @@
- Worktree: /Users/chillishark/Makelore 麦洛/.codex-worktrees/makelore/20261013-chat-knowledge-import-explain-ec03b792
- Base commit: c634425cc669f1da66e725649a386bf09661a70c
- Owner: codex
- Status: Ready for Integration
- Status: Planning
## Scope
@@ -19,7 +19,7 @@
- User initially requested explanation; the latest explicit instruction authorizes removing chat-file import and retaining computer upload. This supersedes the previous feature's approved chat-import entry.
- Earlier steering placed creation beneath computer upload; the latest explicit layout supersedes that button order: the left creation card contains only the new-library entry/form; owned-library browsing and creation do not bind a library to the Agent. Binding remains an explicit bottom selection, and its 100-library limit does not block management or creation. Delete the old instruction paragraph and 「添加到我的知识库」 label.
- Keep real files/chats/libraries, runtime, Main/backend APIs and old recovery records. No actual imports, deletion of user data, app update, main integration or push. Own only removal-related UI/copy/style/tests and this record.
- Keep real files/chats/libraries, Main/backend APIs and old recovery records. The user's latest instruction explicitly authorizes updating the current temporary application; it supersedes the earlier no-update constraint. No actual imports, deletion of user data, main integration or push. Preserve current deployed homepage/recovery/chat and byte-identical Main by assembling only committed current product changes before the knowledge Renderer overlay.
## Outcome
@@ -62,3 +62,12 @@
- Restructure owned-library UI into a top two-column creation/management row and a bottom binding card. Remove creation injection from the document list and automatic bindings on create/browse; preserve pending operations and permission-loss state.
- Update README and focused tests. Independently verify creation/browsing with full binding selection and verify 375px/1440px geometry, upload/status, explicit selection/save/reopen.
- Run focused knowledge suites, typecheck, scoped lint, build and headless fixture; inspect screenshots and independent source review, verify task document boundaries and commit the source handoff.
## Temporary Application Follow-up
- Concurrent Gate: bundled start resumed this same task successfully; status exactly matches feature/task/branch/absolute worktree/base. All peer Scope/Intent/Promotion records read-only. Required project context is retained and startup/positioning/current-state rechecked. Canonical current-state is historical integration context, not the deployed runtime authority.
- Planning Gate: Passed for isolated assembly and staging. Active 「首页更新」 chat is correcting its homepage/account/settings UI and owns concurrent work for the same temporary runtime. Keep its dirty source read-only; bind to the latest committed/verified deployed source and fresh exact current pointer. An active chat need not finish all future steering; serialize actual refresh via inspector exclusivity and pointer/asset identity guards, and rebase if the pointer advances. Unknown legacy scope has no concrete dependency.
- User explicitly authorizes updating the existing trial with finished knowledge source 8e0e52f. Current observed Main is 7c51bb4 / PID9968 / port58003; current Renderer/effective source initially a9fa221 over the home-position overlay. Keep profile/standard login, stable file URL and route, current accepted homepage/recovery/chat, and foreground continuity. No account action, save/discard, real upload/Agent creation/chat, cloud deployment or credential read during verification.
- Plan: assemble the finished knowledge delta over the latest committed deployed product in this owned worktree, keeping canonical/peer task docs read-only. Verify relevant combined source tests/typecheck/lint/build and full Main/resources/package byte equality; prepare a task-owned immutable snapshot with rollback and bound predecessor proof. Activate only after the homepage update settles and a fresh saved/quiet-state check passes; verify actual knowledge layout and original route/session/assets/focus, retaining all rollback artifacts.
- Assembly implemented over deployed a9fa221: imported its committed product/test changes, preserving only this task's knowledge source/README delta. Actual product blobs differ in exactly the four knowledge source/styles files and removed attachment picker; Electron/shared/resources/package/lock match deployed source. Knowledge fixture keeps a9's normalizePath portability fixes; page regression keeps its create/recovery cases and this task's removed old heading click. Independent read-only source review confirms complete current create/journal/onSettled/CloudRecovery/chat DTO/history/stream/message-rendering chains retained.
- Combined verification before staging: 10 focused unit files / 224 tests passed; typecheck and full build passed; 38 changed source/test ESLint files have no errors and retain two existing CloudChat warnings. Knowledge fixture 5/5 passed in 18.2s, including 375/768/1024/1440 geometry and explicit binding/upload-to-ready/save-reopen. All 66 non-Renderer artifacts exactly match immutable running Main/resources/package. The first set comparison detected two unreferenced leftover chunks from this worktree's earlier build; verified that no current JS references them and removed only those generated files, then repeated the strict exact-set comparison successfully.