docs: 说明老师读取预算与工具分页限制

.project-docs/30-worklog/tasks/20260926-teacher-read-expired-087d82f7.md

@@ -45,6 +45,8 @@
 
 ## Verification
 
+- Follow-up explanation (2026-09-27): same-task check/start/status match Identity and feature ownership; 119 peer records readable, prior semantic scope/context reused without a new conflict. Planning Gate Passed for bounded read-only analysis. Rechecked cloud-runner rounds and Yuxi read_round/MAX_READ_ROUNDS: the cap is six result batches per question, not six files or UI activity rows. One batch increments before local execution, even when its result is an error. directory() lists one level; read tools default to 60 lines (maximum 100) and 2400 UTF-8 bytes. excerptTeacherText removes the middle of oversized results. These supported mechanisms can require more sequential discovery/partial-content reads; local history still lacks parameters, so their contribution to this exact question is unproven. Proposed improvement is more useful directory/continuous-page results plus a suitable explicit budget and final answer; no budget/tool behavior changed or new design accepted in this explanatory turn. No tests rerun because only source facts/documentation changed.
+
 - Follow-up red: pnpm exec vitest run tests/unit/coding-teacher-cloud.test.ts -t "one .* local read|pending tool as failed" --maxWorkers=1 failed all three cases before the fix. A successful local read produced before:file failed and after:file completed, reproducing the screenshot.
 - Follow-up green: coding-teacher-cloud.test.ts and teacher-cloud-activity.test.ts: 47 passed. Success and genuine local read failure each retain one call; bare tool errors await the question outcome; terminal failure still closes pending tools. pnpm run typecheck and pnpm run build:vite passed (existing Browserslist/chunk/import warnings). No new E2E fixture was added: existing layout fixture replaces Host API and cannot reach Main cloud-runner continuation; the regression exercises the actual runner and file service with deterministic cloud events. No installed acceptance, live provider call or source deployment performed.