docs: record consultation integration checkpoint and registry blocker

.project-docs/30-worklog/tasks/20260923-merge-yuxi-teachers-ml-9d623c5f.md

@@ -8,7 +8,7 @@
 - Worktree: D:\Datas\OthersProjects\makelore
 - Base commit: 1f2ad3fb3a71b8b35fabb5b319cd3b54b4c2ebbe
 - Owner: codex
-- Status: Ready for Integration
+- Status: Blocked
 
 ## Scope
 
@@ -42,3 +42,18 @@
 ## Promotion Candidates
 
 - Applied the accepted source promotion candidates in integration mode. User confirmation already covers native Yuxi teachers, local read tools and student billing; no unresolved product decision remains.
+
+## 2026-09-24 Consultation Follow-up Integration
+
+- User requests merging the completed context-budget and server-agent unification follow-ups; explicitly declines the additional Yuxi tool explanation UI. Continue this Yuxi-teacher integration in its existing primary ownership. Current main starts at eb3dc85a2f0ed8457b7f24684c2da3ab192c2e46; exact source is 8a157be4f62d073744164318e02185aebeaadc09, including budget source 248776d8550d67de7ce30802a9f827d432c42a99 / product de72b1cd945df373d09402a1cf3a0e9b34832f03.
+- Project Context Loaded: official check/start/status passed with unchanged Identity, primary main ownership and exclusive integration lock. Read entry/planning gate, memory index, own and both source records, positioning, teacher ADR/decision index, system/module/data-flow, business rules/glossary/success criteria, current state, evidence/reflection/commitment/stale indexes. Compared all 110 owners with the prior source gate: only this integrator and the completed unification source changed; those records reread. Historical placeholder peer scopes remain unknown/read-only, with no concrete dependency. No new owners or conflicting decisions.
+- Main owns local access/history; Yuxi/Works own published personas and student billing. The user's explicit removal of fixed teacher/friend categories supersedes earlier fixed personas. Existing cloud contracts, version pins, scoped reads and generic structured discussion remain. Positioning templates are supplemented by README/AGENTS/verified code; old consultation statements are updated only for this accepted scope.
+- Planning and Integration Gates Passed. Plan: fast-forward the verified source, reconcile accepted canonical consultation/budget facts, prove source ancestry and product equality, run official documentation checks, commit and complete. Preserve all three previously adopted foreign documents byte-for-byte and exclude them from commits; source records stay read-only. No subagents, extra Yuxi UI, cloud changes, paid provider calls, push, packaging or deployment.
+
+### Follow-up Outcome And Verification
+
+- Fast-forwarded main from eb3dc85 to 8a157be without conflicts. Both completed source tips are ancestors; no product or test implementation was changed during integration. Exact source code comparison passes. README corrects one remaining old teacher/friend entry description. Canonical decisions, architecture, rules, glossary, evidence and integrated snapshot now state the user-approved server-agent and budget behavior. Source records are unchanged.
+- Reuse exact source verification: unification covers 323 relevant unit cases, standard typecheck, scoped lint, production build, 2 Electron interactions and 13 layouts; budget source covers 289 relevant cases. Expanded Main remains 66 baseline diagnostics with no additions. No new production/provider/installed-app validation is claimed. Whitespace check and referenced source-document existence pass. Three pre-existing untracked documents remain unchanged and excluded from this checkpoint.
+- Documentation completion is BLOCKED, not passed: the resumed integrator's original 1f2ad3f base predates later cross-machine main integration. Official check_doc_drift attributes six existing historical task records in that prior first-parent range to this task. All six predate this follow-up and are identical to eb3dc85. Five name source branches not retained locally; one records main, so the unchanged-source import rule cannot prove it. Neither source records nor the official checker are rewritten to suppress this result.
+- Retain this as an incomplete integration checkpoint. Proposed recovery requires explicit human approval: release this primary ownership with official release --force (required only because the three known foreign documents remain untracked), start a fresh integration task at the current committed main with --adopt-existing for exactly those unchanged documents, then run its full gates to close this merge. This records the true new integration boundary without changing old task bases, branch history or user files. No cleanup, reset, stash or automatic force release.
+- Both just-integrated managed source worktrees remain retained pending the separate cleanup decision after documentation closure: 20260924-teacher-context-budget-3a9e6c81 and 20260924-cloud-consultation-agents-82a6cd19. Branches and all source commits must remain preserved.