docs: record verified knowledge trial update

.project-docs/30-worklog/tasks/20261013-chat-knowledge-import-explain-ec03b792.md

@@ -8,7 +8,7 @@
 - Worktree: /Users/chillishark/Makelore 麦洛/.codex-worktrees/makelore/20261013-chat-knowledge-import-explain-ec03b792
 - Base commit: c634425cc669f1da66e725649a386bf09661a70c
 - Owner: codex
-- Status: Planning
+- Status: Ready for Integration
 
 ## Scope
 
@@ -28,7 +28,7 @@
 - New-library creation now says 「创建知识库」 and opens the created library for management without changing Agent draft bindings. Browsing also leaves bindings untouched; bottom selection explicitly binds. Its 100-library limit no longer blocks browsing, uploading or creating.
 - Independent review found that using creation-form visibility to place a shared error could show an upload error in the creation card. Errors now follow the operation source, with a regression covering right-side upload failure while the left creation form is open.
 - Preserved automatic document processing, status polling, pagination, original-operation retries, replacement/deletion, permission-loss pending state, own/shared library distinctions and explicit save/apply of selection.
-- Main/shared/backend import contracts and recovery handling remain for existing pending operations. No real files/chats/libraries were imported, moved or deleted; current app/runtime was not refreshed.
+- Main/shared/backend import contracts and recovery handling remain for existing pending operations. No real files/chats/libraries were imported, moved or deleted. The user later explicitly authorized the temporary application update; its verified activation is recorded below.
 
 ## Verification
 
@@ -42,7 +42,7 @@
 
 ## Follow-ups
 
-- Source handoff is ready for later integration/application update. The knowledge-workspace source record and current trial remain unchanged; no main integration, push or app update occurred.
+- Source and current temporary application update are complete. Primary main, remote and peer/canonical task records are unchanged; no merge/push or cloud deployment occurred. Real cloud file ingestion remains outside this UI update's acceptance scope.
 
 ## Promotion Candidates
 
@@ -71,3 +71,7 @@
 - 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.
+- Source frozen clean as 2d4e44f4a023fc649d9064d4413284fbeb962d59. Task-owned immutable stage `/Users/chillishark/Makelore 麦洛/.trial-runtime/knowledge-layout-20261013-ec03b792` binds exact predecessor a9fa221, its current-pointer SHA and manifest/assets, original Main proof, task helper hashes and rollback snapshot. Root independently checked both helpers and `prepare.py --verify`. A marker cleanup omission on held/preserved exits was fixed before activation; rebind evidence preserves the old/new helper hashes without changing artifacts or pointer.
+- First activation held at preflight: route `#/cloud-agents?view=mine`, unsent input and beforeunload protection were true; no unsaved configuration, background lease or trusted interaction. Pointer/compat/Main were unchanged and Inspector was closed. User then explicitly answered 「允许清除这些输入并刷新」. Added a one-run authorization flag for existing inputs and beforeunload, retaining dialog, pending-file, running-work, lease and fresh-user-interaction guards. Electron's pinned declaration confirms the one-time will-prevent-unload handler permits only this authorized reload; no business-data deletion or cloud cancellation occurs. Separate authorization/helper rebind receipt retained.
+- Final activation succeeded: current Renderer/effective source is 2d4e44f, Main remains 7c51bb4 / PID9968 / port58003, immutable current-stage and predecessor artifacts retained. Actual loaded JS/CSS match the new snapshot; same stable file URL, current route, profile, login, foreground PID1353 and closed Inspector verified. Application did not restore the cleared local input. `prepare.py --verify` independently reports active-verified.
+- Root performed an additional read-only DOM probe: authenticated My Agents list settled with five cards, mounted app, original hash, no login form or visible alert, unchanged foreground and same Main. No names, credentials or input text were read/recorded, no account/Agent/file operation occurred. The original list does not display knowledge configuration; no forced navigation was made. Knowledge layout evidence is the tested source/fixtures at four widths and exact actual loaded Renderer assets, distinct from a live cloud knowledge ingestion test. Durable receipts are overlay-manifest.json, verification-receipt.json, live-dom-probe-receipt.json and retained preflight/helper-authorization evidence.