Task: Refine teacher guidance around intent progress and productive detail

Identity

Refine the shared teacher behavior prompt and synchronize the readable prompt and product consensus outside the repository.
Preserve the existing context compiler, cloud/local request paths, discussion schema and component lifecycle.

User approved capability development as the main purpose, with actual project progress and student intent selecting this turn's entry and guidance.
Continue productive detail exploration; when prerequisites are missing, discussion repeats without evidence, or a choice is ready to test, connect to the wider goal and offer a next thinking step without forcing it.
Keep the prompt concise. No fixed stages, turn limits, mandatory questioning, demonstrations, project execution, app restart, real model requests, or remote publication.
Planning and ownership gates passed for main at the recorded base. Peer task scopes were reviewed; no semantic conflict with this prompt-only refinement. Earlier external integration notes predate the merged Yuxi runtime and will be labelled as historical.

Amend the shared behavior prompt without changing runtime or component contracts.
Synchronize the readable copy and approved consensus; clarify the external handoff note's historical scope.
Run existing teacher guidance/context/protocol checks, standard typecheck, changed-file lint and production compile; review the diff and complete this task record.

Updated the actual shared prompt: capability development is the main purpose; project progress and student intent select the turn's entry and guidance. Stage judgments adapt to new information and do not impose a workflow.
Productive detail exploration continues. Missing prerequisites, repeated comparison without new information, or readiness to try a choice prompt a concise connection to the wider goal and an optional relationship review or small validation. Student choice remains explicit; no fixed turn cutoff.
Component suggestions consider intent, information relationships and current tool state. Existing lifecycle, candidate/confirmation boundaries, no-demonstration and no-execution rules remain intact.
Synchronized README and the external readable prompt/product consensus; labelled the old external handoff description as historical after its earlier Yuxi integration.
Condensed wording to keep existing local read-tool budget compatibility. Final body: 1,273 characters / 3,743 UTF-8 bytes, a net increase of 98 characters. These are text sizes, not measured model tokens.
No runtime/lifecycle code, cloud definition, real student conversation or app process was changed.
Resumed on 2026-09-24 solely to commit the verified prompt, README and this task record for the requesting workspace-style task (thread 01a0cc32-40cf-7503-983e-ca70eb688599). HEAD and runtime edits were unchanged since verification; no restart, interface change or remote push is included.

Passed: 218 tests across teacher-guidance, coding-teacher, teacher-discussion, teacher-discussion-state and coding-teacher-cloud suites.
Passed: standard corepack pnpm run typecheck, changed-file ESLint, corepack pnpm run build:vite, and git diff --check.
Verified exact equality of the readable prompt and source template body, including documented character count.
Confirmed the production Main output contains the updated teaching baseline; reviewed final diff against the recorded base and found only the intended prompt/README/task-record changes.
Independent text-only review passed: adaptive stages and optional, reasoned refocusing preserve student choice and productive interest exploration.
The initial longer draft exceeded the existing 8,000-input local-model fixture after tool schema/result reserves; condensed the prompt and reran all five suites successfully without increasing budgets or changing tests.
Checks cover compilation, prompt loading, budgeting and existing protocol behavior; no live-model pedagogical evaluation was performed.

Real-model teaching quality can be evaluated separately with representative student discussions; the current checks do not establish that outcome.

Target: canonical teacher behavior/domain rules. Proposal: capability development is primary; current project evidence and student intent choose the entry; continue meaningful detail and offer broader relationships or validation when prerequisites/evidence warrant. Evidence: the user's explicit approval in this turn and the shared prompt/README changes. Future impact: applies consistently across ordinary advice, guided help and proactive teacher turns. Semantic conflicts: none with current dynamic component state; existing timer/confirmation gaps are outside scope. Human confirmation: already supplied for this behavior; canonical publication remains an integration-mode task.