vibe64 0.1.32 → 0.1.34

package/docs/colleague-usage/learning-mode-ui.md

@@ -1,29 +1,168 @@
 # Choosing lessons and Learning conversations
 
-Use the yellow **L** plate in the app header to switch between Working and
-Learning. Its pressed state and highlighted header indicate Learning. On the
+Use the **L** button at the left of the app header to switch between Working and
+Learning. It is the same size as the other header icon buttons. While Learning
+is on it is a full yellow L (pressed, tooltip **Leave Learning mode**) and the
+header is tinted; in Working it is an outlined, untoggled L (tooltip **Enter
+Learning mode**). It is the first keyboard stop in the header: Enter or Space
+switches mode. In a lesson with saved practice projects, the **Practice
+project** menu sits beside it in place of Working's project switcher; on a phone
+it shrinks to its ▾ arrow. On the
 projectless app page, Working shows the original project picker; Learning shows
-installed lessons without asking you to invent or choose a project. In a project
+installed courses without asking you to invent or choose a project; its header
+reads **Courses**. In a project
 view, the same control changes the existing session panel's purpose filter.
 
-The **Lessons** pane shows the installed course release, lesson title and code,
-and the authenticated person's saved progress. Choose **Start** for an available
-lesson or **Resume** for the exact saved attempt. Disabled, unavailable, loading
-and error states are shown by the original lesson picker. Choosing a release is
-not permission to install or enable it. Refresh rereads catalogue and progress.
-A course labelled **Preview course** is not available through ordinary Start,
-even when its individual lessons are published. It needs an authorized author
-trial or a released, enabled course; changing views does not bypass that rule.
+The **Courses** pane (called **Lessons** in earlier releases) opens with a
+**Courses** banner (with **Refresh courses**) and a list of course cards. Each card
+has decorative cover art (the same for a course every time; its dots mirror that
+course's lessons, ticked when complete), a chip saying whether it is **Enabled**,
+a **Preview course** or **Disabled for new lessons** (plus **Saved lesson** or
+**Course complete** when true), the title, its ID and release, topic and lesson
+counts, "N of M lessons complete" with a progress ring, and the next lesson. A lesson counts as complete when all of its required
+assessments are passed in your saved progress; only required lessons are counted,
+unless a course has none. Progress is read from what is already saved; opening a
+course grades nothing. A lesson passed in one course counts in every course that
+contains the same lesson.
+
+On a card, **Continue** reopens your saved lesson when it belongs to that course;
+it is the same request as **Resume saved lesson**. Otherwise **Start** starts the
+course's first published lesson that is not yet complete. **View course** opens
+the course page: a header with the course cover and a ring showing lessons complete,
+an **Up next** card, then a path of its topics in order, each with its lessons, their title and code
+and a status of **Completed** (green tick), **In progress** (yellow; an open attempt or some passes) or
+**Not started** (numbered). The **Up next** card has one main action, **Continue** or **Start next
+lesson** (with the next lesson named beside it), and each available lesson has a **Start lesson** button
+if you want a different one. **Back to courses** returns to
+the list. While you have a saved active lesson, Start buttons stay disabled:
+continue it, or end it first. There is no End button; ask Colleague to end the
+lesson (see [Lesson history and resume](learning-history.md)). On a phone the cards stack in one column and the
+course page scrolls in the same pane.
+
+Choose **Resume saved lesson** on the saved lesson card (above the course cards,
+headed "Saved lesson · code" with the lesson title and, once reported, a ring of
+required assessments passed) for the exact saved attempt. Disabled,
+unavailable, loading and error states are shown on the same page. **Refresh
+courses** rereads installed courses, progress and the course catalogue.
+
+Below the course cards, **Course catalogue → Install a course** lists the
+official catalogue's topics and their courses with **Install** buttons; an
+installed course with a newer release shows **Update available** and **Update**.
+See [Installing and updating Learning courses](learning-course-catalogue.md). A lesson without a practice project, such as local
+Vibe64's Lesson 0 **Set yourself up**, opens only its Learning conversation; that
+lesson uses [Dashboard → Health](health-checks.md).
+Returning from Working to Learning rereads saved lessons and any admitted author trial; a newly admitted trial does not require reloading the page.
+If Resume reports that the saved exercise is busy preparing or finishing a command, wait for that operation to settle and retry the same attempt. Do not create a replacement.
+
+### Creating a custom course
+
+The workspace owner sees a dashed **New course** tile after the course cards (on
+local Vibe64 you are the owner). Enter a **Course name**, tick whole topics under **Installed
+topics**, put them in learning order with **Up** and **Down** under **Topic
+order**, then choose **Create course**; **Cancel** closes the form without
+changes. The new course opens straight away and stays in the list for everyone in
+this installation. Only topics from enabled, released courses are offered. The
+course is pinned to those exact installed topic releases, so it never changes
+lesson content, and saved progress is shared with the original course.
+
+If creation fails, the message appears at the top of the pane: a name that is
+already used (choose another name), a catalogue that changed meanwhile (use
+**Refresh courses**, then try again), a topic that is no longer available, or the
+16 course-release limit. Other people cannot create courses; on hosted Vibe64
+only the workspace owner can. Colleague can create a custom course when the owner
+asks for it with a name and topics. A custom course cannot be renamed or edited;
+the owner can disable it with `vibe64 training disable-course` (see
+`docs/training-content.md`) and create another one.
+
+A **Preview course** is for the workspace owner to review before release. The
+owner (on local Vibe64, you) sees **Try preview** instead of **Start**, **Start
+next lesson** and **Start lesson**, on desktop and phone; it starts an ordinary
+saved lesson exactly like Start. Others see **Preview — the workspace owner can
+try it; it becomes startable when released** and no start button, and the server
+refuses their start. Drafts and disabled courses stay unavailable to everyone.
+Once released, everyone gets **Start**.
+
+Practice commands and their Git operations stay with the saved lesson until they
+finish. If a command is still finishing, wait before ending the lesson. Ending a
+lesson stops its lesson conversation's running work, as **Stop** does, and keeps
+the conversation, practice project and history; it does not archive or delete
+anything. After cancellation or an end, an old command cannot restart work. An
+ended lesson cannot be resumed; ask Colleague to continue it in a fresh exercise
+(see [Lesson history and resume](learning-history.md)).
+
+When Learning first creates its teacher session, it uses the first available AI
+workflow shown by the normal session picker, then checks your current Junior
+model and account access. It does not assume OpenCode is configured. You can
+change the teacher's AI through the normal chat model controls afterward. If no
+workflow is available, connect/configure one in **AI Accounts → Model routing**,
+then resume the same saved lesson or author trial; do not start a replacement.
+
+The Main teacher uses the saved lesson's exact instructions with Codex, Claude
+or OpenCode. In a practice project those instructions accompany the project's
+normal development guidance; switching AI does not turn the lesson into an
+ordinary coding task. The teacher should give the declared learner task and wait
+for your own answer or action. It must not ask you to reconstruct the installed
+lesson, invent an observation or count its own demonstration as your pass.
 
 After a confirmed active Start or Resume, the existing Main conversation is
 opened and selected only if its loaded row matches your learner and attempt.
-The teacher chat stays visible throughout Learning, including after opening a
-lesson or reloading the page. On desktop, Lessons/App/Presentation appear beside
-it. On phones and tablets, chat occupies the upper part of the workspace and
-Lessons/App/Presentation the lower part; each keeps its own scrollable area.
-Use the existing **Lessons**, **App** or **Presentation** tabs in that supporting
-pane without hiding Main. Learning has no chat-collapse or pane-swipe control.
-Returning to Working restores its previous chat-collapse choice. Both modes use
+Learning uses the same header as Working: the session row on the left, the
+collapse-chat arrow, the **Preview** | **Dashboard** tab group and, while
+Preview is shown, the same Preview toolbar (address, reload, pause, copy and
+status). Learning adds exactly one thing: a graduation-cap option at the end of
+that same tab group (**Preview** | **Dashboard** | 🎓, tooltip "Learning:
+courses and lesson"). Selecting the graduation-cap button beside Preview and
+Dashboard shows the Learning panes (**Courses**, **Check my code**, the lesson
+and its history); Preview and Dashboard then appear unselected, exactly as one
+option of three. Selecting **Preview** or **Dashboard** deselects the cap. The
+collapse-chat arrow hides or shows the teacher chat exactly as it hides or shows
+the Working chat. In a practice lesson, **Dashboard** is the ordinary Dashboard for the
+lesson's practice project and lesson session, showing every section that works
+inside a lesson:
+
+- Project sections: **Git log**, **Env**, **Session History** and **Health**.
+- Session tools: **Session info**, **Current changes**, **Files**, **Database**
+  and **Architecture**.
+
+Each one reads and changes only this lesson's practice project and session,
+never your Working project. **Database** shows the practice app's ERD, tables
+and data, editable like any project's database (see
+[Browse a project's Database](database.md)). An app without a database shows
+"The session Stack does not declare a supported database." **Files** is the
+source editor for the practice project; see
+[Answering a code question in a lesson](learning-code-questions.md).
+**Env** shows and edits this lesson session's user values; **Reveal** for a
+secret is not offered. **Git log** and **Current changes** are read-only: their
+**Check for updates**, update and **Review changes** (save) buttons are not
+shown, because a lesson is never saved, updated or published. **Session
+History** lists only this lesson's archived lesson sessions. **Architecture**
+can analyse the practice project; its **Ask** assistant is off (ask your lesson
+teacher instead). The **Database** Copilot is off too.
+
+A lesson's Dashboard does not show **Project settings**, **Integrations**,
+**App access**, **Incoming changes**, **Issues/PR** or **AI Terminal**. These
+change or reach outside the practice project, and the AI Terminal would type
+straight into the teacher's agent. Opening one of their addresses directly in a
+lesson shows **Env** instead. Moving between Dashboard sections keeps Learning
+on. Switching between Preview, Dashboard and Learning keeps Learning mode on and
+retains the same selected teacher session; it does not switch to your last
+Working session. The graduation-cap **Learning** option shows the **Courses** | **Presentation**
+switch. Returning to it keeps the selected Courses or
+Presentation content visible without requiring another click. A supervised
+project opens on its Preview by default. On reopening, the practice project waits for the
+assistant's initial connection check to settle before opening the saved practice
+runtime. It still opens if that check reports an unavailable or failed AI;
+repairing the AI connection is separate from using the practice Preview.
+A source-less lesson disables **Preview** and **Dashboard** (their tooltip says
+the lesson has no project workspace) and keeps the graduation cap selected,
+instead of showing a remembered Working project. On phones and tablets Learning
+behaves like Working: the teacher chat and the right-hand pane are shown one at
+a time; the arrow button or a horizontal swipe switches between them, and the
+header's next-pane button (shown while the right-hand pane is open) steps through
+**Dashboard**, **Learning** and **Preview**. On the projectless **Courses** page,
+which has no right-hand project pane, chat and lessons are stacked instead.
+
+Working and Learning share one chat-collapse choice. Both modes use
 one retained session panel, so switching modes does not delete drafts or stop
 already admitted background work. A project that is still loading or failed
 keeps its original Working readiness gate while retaining the hidden panel.
@@ -33,48 +172,25 @@ original project through the usual access checks before showing it as ready.
 This does not restart stopped Working agents or outputs. Explicit project Close
 or deletion still leaves the project view; a missing runtime or revoked access
 is not treated as ordinary inactivity.
-The original Preview host offers **Lessons**, **App** when this session actually
-has a source-backed application, and **Presentation** after a declared diagram
-has been opened. A declared diagram can open from Lessons; hidden App controls do not remain
-interactive. Switching these views retains the App and diagram instances
-and the lesson picker within that host. Hidden diagrams pause; returning does
-not replay their motion or count as a completed lesson. If sound is off, use the
-presentation's **Continue** only after its explanation is ready. A supported
-narrated diagram waits for its confirmed final explanation and actual sound and
-motion completion. Hiding or stopping it does not count as completed teaching.
-If its cue receipt was not confirmed, read the current status before continuing;
-do not assume the explanation or motion succeeded.
-When Main opens a lesson diagram, keep that same browser open until its operation
-is confirmed. Main opens it in that lesson's **Presentation** pane; opening the
-Colleague drawer is not required. If the browser did not acknowledge navigation,
-keep the initiating conversation open and check its current status before
-requesting another operation. If Main already finished with that failure, its
-message remains saved; read its result and your saved lesson progress before
-asking it to continue. Do not resend that completed message to recover navigation.
-Stop or a replacement Learning conversation retires its old
-explanation; an old confirmation cannot complete a new one.
-Wait for Main to confirm that the diagram is ready before continuing its
-illustrated steps.
 
 The selected Learning conversation prepares the configured agent through the same
 Main readiness flow as Working. Preparation retains that saved conversation and
 checks your current access; it does not send your draft or begin teaching. An
 ended or inaccessible attempt cannot start agent preparation.
 
-Source-less Learning conversations show Lessons and omit App. A supported declared
-diagram can use the same Presentation player only in your exact saved lesson
-conversation; an empty picker or unavailable diagram cannot open it. This does
-not give the lesson repository, Save or Temporary AI/workspace access. A saved
-checkpoint does not mean a presentation is currently open. After a completed
-command or pause, the player saves its semantic state and labels. Reopening the
-same attempt restores its last confirmed state without replaying sound or motion.
-**Retry diagram checkpoint** retains an unconfirmed save identity; after a
-revision conflict, **Save current diagram** captures fresh state. Keep the player
-open until confirmation. Practice lesson diagrams save to that same lesson and
-Main conversation. A changed account, attempt or conversation retires its old
-handle; an error never grants a pass.
-
-If Start is unconfirmed, **Retry lesson start** keeps its original request
+While a start is in progress, the Courses pane says **Starting the selected
+lesson and preparing its practice project. Its teacher conversation opens when
+this finishes.** Every **Start**, **Start next lesson** and **Start lesson**
+button stays disabled until the request settles; the teacher conversation then
+opens by itself. A practice project's Workspace setup can continue afterwards;
+the lesson becomes ready by itself when setup succeeds, so you do not need
+**Resume saved lesson** after a normal start (see
+[Practice projects in standalone lessons](learning-practice-projects.md)). This
+looks the same on desktop and phone. **Starting lessons is unavailable in this
+installation** appears only when the installation cannot start lessons.
+
+If Start is unconfirmed, the pane says **The last lesson start was not confirmed**
+and a **Retry lesson start** button appears above it. It keeps its original request
 identity, lesson and revision. Do not substitute a different lesson request.
 An ended replay is history; it does not select a different current attempt. If
 opening the saved conversation is unconfirmed, the exact Start retry or Resume
@@ -90,37 +206,23 @@ Private provider key entry remains a human-only step. A diagram belongs to its
 original signed-in learner and Main conversation; changing accounts retires its
 display and pending reads rather than transferring it to the next person.
 
-To request teaching, open the exact saved Learning Main conversation and ask
-“Teach me this lesson.” Starting or resuming the lesson does not itself send that
-request. Main can use the lesson's declared diagrams in that same browser;
-Colleague remains available for general help and workspace supervision. Text
-teaching does not require voice, and private key entry remains your action.
-
-For a narrated diagram, keep the initiating browser and exact lesson conversation
-open until its operation is confirmed. Its explanation waits until Main has
-finished that turn. Stopping or interrupting an unfinished explanation prevents
-it from playing later when you ask a new question. With sound off, use
-**Continue** only after the explanation is ready. A visible diagram or saved
-state does not itself mean narration, motion or an assessment succeeded.
-
-Main confirms a diagram explanation from that turn's finished response before
-enabling **Continue**. Keep the same lesson and conversation open while it
-finishes. A stopped explanation or a response from a different turn cannot
-confirm the old diagram; read Main's current result before asking it to continue.
-The response may appear before **Continue** becomes ready; wait for its
-confirmation instead of resending that finished reply.
-
-If an operation is unconfirmed, read its current status before requesting a
-repeat. A reload or changed lesson/account cannot reuse an old cue confirmation.
-Switching the compact screen between chat and Preview retains the same active
-lesson; selecting a different session or account retires its old presentation.
-
-While a lesson’s narrated visual explanation awaits its final response, optional
-thinking and interim speech stay silent too. Your speech preferences remain saved;
-fresh confirmed replies use the same voice controls. This does not hide chat text.
-
-After Main finishes a Learning turn, **Lessons** refreshes the saved progress
+An exercise's Main coding assistant can perform an explicitly requested setup
+repair in that same practice session. Its commands recheck the saved lesson each
+time, including after the opening request has finished. If the assistant starts a
+command before **Send** finishes saving its receipt, that command waits for the
+same send to finish, then checks the lesson again. **Stop** cancels a waiting
+command. A failed send does not allow its waiting command to proceed. Ending the lesson prevents
+new commands; retained status remains readable. If Workspace setup failed, inspect
+the concrete diagnostic before **Retry**; a repair or successful setup is not a
+learner answer or passed assessment. Colleague can explain and coordinate this
+recovery but has no source-editing or shell access.
+
+After Main finishes a Learning turn, **Courses** refreshes the saved progress
 for that same lesson. An owner’s author trial remains separate from ordinary
-lesson progress. If updates were disconnected, use **Refresh lessons** to read
+lesson progress. If updates were disconnected, use **Refresh courses** to read
 the current saved results before choosing Start or Resume. The saved checkpoint
 question may already have been assessed; it is not a new unanswered question.
+
+Related topics: [Answering a code question in a lesson](learning-code-questions.md),
+[Watching a lesson step by step](learning-lesson-watch.md) and
+[Lesson diagrams and voice](learning-diagrams-and-voice.md).

package/docs/colleague-usage/learning-native-session.md

@@ -1,6 +1,6 @@
 # Main lesson conversations
 
-Use the yellow **L** plate and the existing **Lessons** pane to Start or Resume
+Use the yellow **L** plate and the existing **Courses** pane to Start or Resume
 your saved lesson attempt. The same left Main conversation is the intended
 teacher; Colleague remains available for general application assistance. See
 [Choosing lessons and Learning conversations](learning-mode-ui.md) for the
@@ -123,10 +123,11 @@ for that access read; this does not retain permission for a later request. A cha
 lesson pin or installed exercise remains an error, and historical reading does
 not permit new practice work. A confirmed preparation refusal before admission keeps the
 message failed; after preparation is ready, use its **Retry** once to send the same
-saved request. If delivery is unconfirmed, use **Check delivery**; an unknown result
-is not permission to resend. If setup has finished but the lesson still shows
-preparing, use **Resume** for that saved lesson to confirm its preparation; do not
-start a replacement or change its pin.
+saved request. If delivery is unconfirmed, use **Retry**; an unknown result
+is not permission to resend. The lesson normally becomes ready by itself when
+setup finishes. If setup has finished but the lesson still shows preparing, use
+**Resume saved lesson** (or **Continue** on its course) to confirm its
+preparation; do not start a replacement or change its pin.
 If preparation reports
 missing source, retain the attempt and resolve that failure before continuing;
 a conversation alone cannot replace the workspace. Existing conversations and
@@ -151,14 +152,15 @@ installation's supported connection/replacement recovery.
 
 ## A prepared practice lesson
 
-Start or Resume the saved lesson in **Lessons**, then select its Learning
-conversation in the same session list. Ask Main to teach that lesson. The
+Start or resume the saved lesson in **Courses**. Its Learning conversation opens
+by itself once the request is confirmed; otherwise select it in the same session
+list. Ask Main to teach that lesson. The
 conversation belongs to the lesson’s prepared workspace; changing the visible
 Working project does not move it. Keep the existing attempt and history if its
 source is unavailable, and ask the owner to restore that saved workspace.
 
 Main can use a declared lesson diagram in **Presentation** when the installation
-supports it. **Lessons** returns to the picker; **Presentation** returns to the same
+supports it. **Courses** returns to the Courses pane; **Presentation** returns to the same
 diagram. A confirmed diagram state is retained separately from an assessment pass.
 On a phone, use the existing conversation and Preview view controls to switch
 between the teacher and diagram.
@@ -174,7 +176,7 @@ console is read-only. On a phone, closing its full-screen log returns to the
 underlying view.
 
 The App remains attached to this lesson's saved workspace when you select another
-Working project. **Lessons** returns to the picker and **Presentation** returns
+Working project. **Courses** returns to the Courses pane and **Presentation** returns
 to the lesson diagram. A visible app or successful Run does not by itself confirm
 a practical or pass an assessment; follow Main's actual practical instructions.
 
@@ -186,7 +188,7 @@ Save, manual command terminals or Workspace setup retry. Do not substitute a
 Working conversation to bypass the refusal. Colleague can explain the controls
 and help you recover; Main remains the lesson teacher.
 
-The App setup view retains the same lesson presentation handle and saved lesson identity. Switching between App, Lessons and Presentation does not switch to a working project. A changed account or saved lesson target retires that view; open the current Learning session again.
+The App setup view retains the same lesson presentation handle and saved lesson identity. Switching between App, Courses and Presentation does not switch to a working project. A changed account or saved lesson target retires that view; open the current Learning session again.
 
 An accepted Claude teacher request keeps its own saved lesson, conversation and
 account while its answer continues, including after the Send request returns.

package/docs/colleague-usage/learning-practical-exercises.md

@@ -0,0 +1,71 @@
+# Practise workspace controls and the application
+
+For the workspace exercise, keep the same question open while you use the
+controls yourself: open the project selector and choose the lesson's exercise
+(the already selected project also counts), reveal its Main coding conversation
+with the session tab or **Show chat**, then choose **Preview**. A different session
+or temporary review conversation does not count; use its **Main chat** button
+first. Wait for each view to finish opening.
+Colleague can explain these steps, but its own navigation is a demonstration,
+not evidence that you performed them.
+For a question that asks you to change code, edit in **Dashboard → Files** and
+press **Check my code** in the graduation-cap **Learning** option; see
+[Answering a code question in a lesson](learning-code-questions.md).
+
+Keep one delivered challenge and its question reference across all three steps.
+The Main teacher may explain one substep at a time, but must not prepare a new question
+between project selection, revealing its Main chat and Preview selection:
+that replaces the challenge and resets its observation collection. On a phone,
+receive the task before minimising Colleague; return after the steps and explain
+what you did before assessment. The supported Main practical owner must acknowledge the actual accepted steps
+and coach the next move; ordinary Colleague chat is not a grading path.
+These collecting facts are not a completed observation or pass. Only the final
+native step supplies `trainingPractical` for assessment.
+
+For the return exercise, **Minimize conversation**, use the workspace, then
+restore Colleague with its launcher. On phones, **Show project** / **Show chat**
+toggle workspace / Main, not Colleague. Desktop drawer and phone full-screen retain
+the session, speech, draft and exercise. Restore Colleague's actual body; another
+assistant's voice panel does not count.
+
+Native observation binds your clicked control and settled view to the delivered
+question; it has no pass button. Unsupported observation leaves the practical
+incomplete. If unconfirmed, repeat the step once ready; the workspace action was
+not undone. Reload or question replacement may require repeating an unfinished
+sequence. Separate verified assessment uses the pinned rubric and your explanation.
+
+Observation retries retain the original gesture acknowledgement/step count;
+conflicting details are rejected. Completion is an observation, not a pass.
+After server restart repeat the sequence; workspace actions were not undone.
+The question itself stays open across a restart or reload, so you repeat its
+steps (or press **Check my code** again) without asking for a new question.
+Demonstration/substantial help remains teacher-origin, not independent evidence.
+
+Practical assessment requires both your native exercise receipt and accepted
+explanation, never Main's substitute description. Demonstrations and failed
+declared checks cannot earn a pass. Retry reads the saved result; another submission
+cannot reuse the observation. Assessment is not a learner grading button or proof
+of lesson completion.
+
+### Trying the real application
+
+For the application practical, show **App preview**, press the application's
+**Ask the server** button yourself, and read its greeting and request reference.
+If the diagram is showing, switch back to App preview first. On a phone,
+minimise Colleague so the real App is visible. Tell the Main teacher in ordinary words
+what you pressed and what replied; a verified request alone does not replace
+this explanation.
+
+The lesson checks the visible App frame and real server response. Diagrams,
+demonstrations, readiness signals and background responses are insufficient.
+If App was hidden, the question changed or observation was unconfirmed, show the
+same exercise and press again. After server restart, use **Reload preview** before
+pressing. Original App/Preview controls remain; Colleague gets no source or screenshots.
+
+Colleague can read the completed observation's exact identity through its normal
+context query, then evaluate it with your accepted explanation. Missing or stale
+observations require repeating the native task. A check reporting a verified
+interaction is not itself a rubric pass, and demonstrated steps remain labelled
+as demonstrated.
+
+An assessment error does not prove a Helper setup problem. Keep the attempt and question; inspect the actual cause. After admission recovery, give a fresh answer to the current question; old messages stay unchanged.

package/docs/colleague-usage/learning-practical-gestures.md

@@ -4,7 +4,7 @@ Main is the teacher in the selected saved lesson conversation. Colleague remains
 
 ## Choose the saved practice project and chat
 
-Turn on **Learning mode** with the yellow L. Start or resume the lesson through Lessons, then use **Practice project** to choose its already prepared saved workspace. This menu lists saved practice targets available to your current learner; it does not install or create another project. A source-less introductory lesson has no practice project entry.
+Turn on **Learning mode** with the **L** button at the left of the header (full yellow while Learning is on). Start or resume the lesson through Courses, then use **Practice project** to choose its already prepared saved workspace. This menu lists saved practice targets available to your current learner; it does not install or create another project. A source-less introductory lesson has no practice project entry.
 
 Follow Main's current practical question. Choose the requested practice project yourself, then choose its saved Main session. Main stays visible in Learning mode. Press **App** in Preview when the question asks for the running application. These person clicks retain the selected saved lesson target. Automatic selection after Start or Resume does not count as an independent project-choice step. Answer Main after the actions; do not submit an explanation to Colleague instead. If you reload the page or return to a loaded lesson, wait for the current question and saved workspace to be ready, then carry out all its steps in that browser before sending your explanation.
 
@@ -22,6 +22,23 @@ Do not start a fresh Colleague conversation midway through this question. If Col
 
 A practical observation can fail while your workspace action remains applied. Repeat that step when the saved session and Preview are ready; do not assume the action was undone. If the learner, lesson target, frame or question changed, return to the intended saved lesson and follow Main's current question. A synthetic click, automatic navigation or an old reply is not practical evidence.
 
+If you started polling from Colleague's eye button, the same trusted named click
+can also update that watch after the workspace settles. The watch update and the
+native practical receipt are separate: a watch notification is never practical
+evidence, and a watch-delivery failure does not undo or invalidate a confirmed
+native practical receipt. Colleague-performed navigation is labelled as a
+demonstration. Pause or Stop polling independently of Main's current question.
+When a watched step is confirmed—or its settle/response fails explicitly—the
+watch may notify the same Main teacher after any current learner turn finishes.
+Main can acknowledge meaningful progress or offer one bounded hint, but that
+application update is not your answer or practical evidence. Repeating the same
+unchanged step does not create repeated hints, and inactivity creates none.
+The eye dialog and Colleague's start/read/pause/resume/stop requests control this
+same watch. Its timestamps describe freshness, and its saved assessment outcome
+is the only displayed result that can support lesson completion. Stop never stops
+the app or Main. Actions inside the app that do not cross a declared exercise
+response or named Vibe64 control cannot be observed by this polling mode.
+
 The teacher must genuinely finish delivering the question before practical observations can be accepted. A short preparation reply is not the question. Wait for Main’s full question even when it appears as a later reply in the same request. The original server checks the saved lesson pin, native delivery, declared check and your explanation; these controls do not mark a pass themselves. An unavailable exercise or teacher operation must be reported as unavailable instead of granting credit.
 
 Main grades your actual explanation alongside the server's description of your completed practical actions. The Helper checks both against the saved lesson rubric; it cannot perform missing steps for you. A saved **needs-review** result grants no pass. Ask Main about the missing evidence and use a fresh independent question when reassessment is appropriate; retrying a completed submission does not grade it again.

package/docs/colleague-usage/learning-practice-projects.md

@@ -1,14 +1,18 @@
 # Practice projects in standalone lessons
 
-Some lessons need a practice application. Use the existing lesson **Start** or
-**Resume** control. If the installation reports that exercise preparation is
+Some lessons need a practice application. In Learning → **Courses**, use
+**Start**, **Start next lesson** or **Start lesson** for a new lesson, or
+**Continue**/**Resume saved lesson** for your saved one (see
+[Choosing lessons and Learning conversations](learning-mode-ui.md)). If the installation reports that exercise preparation is
 unavailable, keep the saved attempt and ask the owner to provide preparation
 support before retrying. That refusal means preparation did not start.
 
 Supported preparation uses the exercise bundled with your saved lesson and keeps
 its reserved practice project and session when you resume. Workspace setup may
-continue after the start request finishes. Pending or failed setup needs its
-existing recovery; it does not mean Preview is running or a practical has passed.
+continue after the start request finishes. When that setup run succeeds, the
+lesson becomes ready on its own; you do not need to press **Resume saved lesson**
+first. Failed setup needs its existing recovery, then **Resume saved lesson**;
+setup success does not mean Preview is running or a practical has passed.
 Standalone setup uses the installation's actual resources; it does not create a
 hosted development database by default.
 
@@ -17,10 +21,57 @@ storage intact and ask the owner to inspect the reported error. An unrelated
 Working project cannot replace this saved attempt's practice project.
 
 Colleague can explain the error and use supported lesson controls when asked.
+
+In a practice lesson, **Preview** shows the practice app as soon as it
+reports ready, including after the app starts while you are on the **Learning**
+pane. **Stop preview** stops the practice app cleanly and keeps it stopped, even
+after a reload, until you choose **Restart preview**. Switching between
+**Preview**, **Dashboard** and the graduation-cap **Learning** option keeps the same running app without reloading it.
 Standalone exercise conversations in Learning, their Preview and practical
 assessment are still being integrated; prepared source alone does not make that
 complete flow available.
 
+A local installation normally serves only the project you selected. It also
+opens your own active lesson's practice project by its address (for example
+when Colleague navigates there or you open **Account settings** from it): the
+page, **Preview** and **Dashboard** load the same way as on a hosted workspace.
+That address gives viewing and Preview control only; start new coding work from
+the lesson in **Learning**. The lesson's own conversation stays in **Learning**:
+the project's ordinary (Working) session list and settings do not show it. Another person's practice project, or a practice
+address with no saved lesson behind it, still reports "Local editor mode only
+serves the selected project."
+
+## Instructing your teacher-agent
+
+In a lesson with a practice project, the teacher in the lesson's conversation is
+also your Vibe64 agent for that project, as in normal Vibe64. Ask it to make a
+change and it does the work in the practice project. It also teaches you to
+instruct it well: say the goal, where the change belongs, and how you will check
+it. Then check the result yourself in the real interface: **Preview**, and in the
+lesson **Dashboard** the **Files**, **Current changes**, **Git log**,
+**Architecture**, **Env** and **Database** → **ERD** views. These are the ordinary
+Dashboard sections, limited to this practice project and lesson session; see
+[Choosing lessons and Learning conversations](learning-mode-ui.md) for which
+sections a lesson shows.
+
+Work the teacher does for you is a demonstration. It never counts as your
+practical evidence, and the teacher does not do a graded task for you before you
+try it. When a lesson is about instructing the agent, your own explanation or
+instruction is what is assessed.
+
+While a code question is open, the teacher will not edit that question's files,
+even if you ask; any agent edit there voids the attempt and **Check my code**
+then reports that an independent attempt is needed. Make those edits yourself in
+the lesson Dashboard's **Files** tool. The teacher also never deploys, publishes,
+pushes to real remotes, changes Git remotes, or touches other projects or folders
+outside this practice project. Lesson 0 and other lessons without a practice
+project keep a conversation-only teacher that does no project work.
+
+A lesson you started before Learning moved onto the real Vibe64 app picks up
+the current teacher instructions with your next message. Its earlier replies may
+still say **Workspace** or **Code tab**; those are the old names for the header's
+**Preview** | **Dashboard** options and the Dashboard's **Files** section.
+
 Opening supported practice teaching retains the reserved initial conversation,
 source and history. An ownership or lesson-binding error needs owner inspection;
 do not create a replacement or switch it to an unrelated Working project. An

package/docs/colleague-usage/learning-session-creation.md

@@ -33,10 +33,10 @@ attempt. They do not change the working project or indicate that a different
 lesson has completed. If updates stop, check this same saved conversation before
 retrying a message; a refresh is not permission to send the message again.
 
-These action and storage prerequisites do not yet expose a complete lesson picker
-or Main teacher in every installation. They do not establish successful question
-delivery, assessment, speech or presentation. Use the installation's supported
-controls; an internal operation name is not a visible button.
+Start and resume lessons from Learning → **Courses**; see
+[Choosing lessons and Learning conversations](learning-mode-ui.md). Opening a
+conversation does not establish successful question delivery, assessment, speech
+or presentation. An internal operation name is not a visible button.
 
 
 ## Local editor availability
@@ -75,7 +75,7 @@ failed. The read addition alone does not establish that every installation has
 completed its visible Learning filter or teacher controls.
 
 
-## Main chat transport: integration prerequisite
+## Main chat transport
 
 A supported Learning Main chat uses your actual saved attempt and authorized
 conversation, including its original Send, steering, Stop and goal behavior.
@@ -89,7 +89,7 @@ Learning chat updates belong to the exact attempt. Updates for another lesson or
 working project cannot enable its access, change activity or refresh its goal.
 If updates or access are unavailable, check the same saved attempt before
 retrying; refresh never proves failure or authorizes repeating a message. The
-same transport applies on desktop and mobile. Its prepared client integration
-does not yet prove the visible Main launcher, actual teaching, speech or visuals.
+same transport applies on desktop and mobile. An open chat alone does not prove
+actual teaching, speech or visuals.
 Colleague can explain the supported controls and offer the original actions; an
 offer does not authorize a new lesson or reset progress.