vibe64 0.1.39 → 0.1.41

package/docs/colleague-usage/github-work.md

@@ -1,6 +1,6 @@
 # Review, Save and work with GitHub
 
-Source edits in a session, saving a project version and publishing an application
+Source edits in a session, saving a project version and deploying an application
 are separate operations. A different session has its own worktree. Check which
 project, session and branch you are using before saving or creating a pull request.
 
@@ -11,7 +11,7 @@ session's tab. Managed Vibe64 Git saves a version;
 GitHub workflows use your repository permissions and the project's direct-push or
 pull-request policy. **Update this session (rebase)** reconciles newer saved project
 work when offered; Save does not silently perform that update for you. A failed or
-uncertain publication needs a state check before another request.
+uncertain push needs a state check before another request.
 
 Whenever Save or Update reports a problem, its activity panel offers **Fix it with
 AI**, which opens a temporary repair chat with the exact error and asks it to
@@ -36,7 +36,7 @@ repair it. Ask the coding agent to reconcile the existing selected component as
 the error directs, preserving the project's authored setup and output sections.
 This does not require installing dependencies or preparing the database. Review
 the repair, then use **Save** again. The failed preflight leaves your source and
-published version unchanged. Colleague can explain this recovery; the coding
+saved version unchanged. Colleague can explain this recovery; the coding
 agent performs the source repair. These steps apply on desktop and mobile.
 
 If assistant naming is unavailable, Save uses a checkpoint-based version name
@@ -49,8 +49,8 @@ If a push loses its response, Vibe64 checks the exact prepared commit on the
 remote before treating it as failed. If the remote cannot be read, restore access
 and inspect the session's work again. Recovery uses the original Save operation
 and Git evidence, including after an editor restart, without another push. A
-failed local update after publication uses the same recovery. If Git confirms
-that nothing was published, the original rejection remains visible or an
+failed local update after a push uses the same recovery. If Git confirms
+that nothing was pushed, the original rejection remains visible or an
 uncertain attempt becomes explicitly retryable. Colleague can inspect work and
 explain that result; a new Save still requires your instruction.
 
@@ -80,7 +80,7 @@ coding work to finish, then:
    further repair is needed; cancelling leaves the files unchanged.
 3. Select **I've resolved these conflicts — apply Update** to acknowledge the
    repair and run Update. This works even when no repair chat exists or its AI
-   was stopped or failed. It does not Save, push or publish the work.
+   was stopped or failed. It does not Save or push the work.
 
 On phones, reveal chat to reach the Update error or repair tab; the file review
 and confirmation are the same as on desktop. The controls wait while an assistant
@@ -110,7 +110,7 @@ On mobile, reveal the project and choose the corresponding **Dashboard section**
 Creating a pull request uses the same connected-work checks as Main Save. Save
 connected work first, merge its submitted revisions in the receiving projects,
 and Update those connected sessions to the accepted source before creating the
-pull request. Changed source or revoked receiving access stops publication;
+pull request. Changed source or revoked receiving access stops the push;
 creating a pull request does not bypass those checks.
 
 Colleague can explain these workflows, open their views, inspect bounded saved-work
@@ -120,4 +120,4 @@ repository itself. Tell it the intended branch, issue or PR when ambiguous. A
 question such as “How do I create a PR?” makes no commit, push or external write.
 An accepted offer or direct request still needs any unresolved inputs and the
 native review/permission rules. Its report must distinguish requested, saved,
-published and unknown outcomes, and disclose unverified external results.
+pushed and unknown outcomes, and disclose unverified external results.

package/docs/colleague-usage/health-checks.md

@@ -1,26 +1,59 @@
 # Check that this installation is ready (Health)
 
-**Dashboard → Health** (the **Studio Health** page) runs this installation's readiness checks and shows each
-one as passing or needing attention, with what was expected and what was observed. Use **Refresh**
-to run them again after fixing something. On a phone, open Dashboard, then choose
-**Health** from the section menu.
-
-| Check | Group | What a failure means |
-| --- | --- | --- |
-| Workspace services | Studio | The Vibe64 installation or its project list cannot be read. |
-| Tools | Runtime | Shown only when Vibe64 uses the programs installed on this computer (**Using your installed tools**). Always passes; it reminds you to install and update them yourself. |
-| AI connection | Credentials | No AI provider is connected; open **Account settings → AI Accounts**. |
-| Node.js, Git, GitHub CLI, ripgrep, Genesis | Runtime | That program is missing or the wrong version on this machine; install it with the system's normal installer. With your installed tools, Node.js must match the major version Vibe64 declares (shown in the check). |
-| Claude Code, Codex, opencode | AI tools | With your installed tools: that AI tool isn't installed on this computer, or it didn't start. A missing tool shows its official install command; each is needed only for the AI that uses it. Where the host provides pinned versions, a single **Codex CLI** check (Runtime) replaces these. |
-| Playwright runtime, Playwright browser (Pinned browser where the host provides pinned versions) | Browser | Only automated browser tests need these; other work is unaffected. With your installed tools, the check shows Playwright's own message, for example **Playwright is not installed on this computer**; install Playwright, then run `playwright install chromium`. |
+**Dashboard → Health** (the **Studio Health** page) shows what this computer has
+and what Vibe64 needs from it. Use **Refresh** to run the checks again after fixing
+something. On a phone, open Dashboard, then choose **Health** from the section menu.
+
+The top line says **Vibe64 has what it needs.** or how many needed things are
+missing, and how many optional extras aren't set up. Only **Needed** checks count.
+
+**Needed** (Vibe64 can't work without these):
+
+| Check | What a failure means |
+| --- | --- |
+| Node.js | Node.js is missing or not the major version Vibe64 needs (shown in the row). The row shows the install command. |
+| Git | Git is missing or didn't start. |
+| An AI tool | None of Claude Code, Codex or opencode runs on this computer. One is enough. **Set up your AI** opens AI setup. |
+| AI connection | No AI is connected yet. **Set up your AI** opens AI setup (shown on the first AI row that needs it). |
+| Vibe64, Genesis | Vibe64's own parts can't be read. This is not something a project setting fixes. |
+
+**Optional** (nice to have; nothing depends on them): GitHub CLI, ripgrep, the AI
+tools you don't use, **Your name in Git** and the Playwright browser for automated
+browser checks. **Your name in Git** comes first when it needs you; an extra that
+simply isn't installed folds to one line, "Not installed", with **How to install**
+to open its install command.
+
+A tool counts as there only when it actually runs: Vibe64 starts it and asks for
+its version (a few seconds at most), using the same `PATH` your projects use. A file
+that exists but doesn't start shows as **didn't start**. A ready tool shows its
+version and where it was found, so a wrong pick is easy to spot.
+
+A missing tool shows one sentence, the install command for this computer (Debian,
+Ubuntu or WSL; macOS with Homebrew; otherwise mise) with a copy button, **Check
+again** and **Other ways**. For Node.js, Git, GitHub CLI, ripgrep, languages and
+build tools, **Other ways** opens this computer's setup guide
+([Linux](set-up-linux.md), with Fedora and Arch lines, or [macOS](set-up-macos.md));
+for AI tools and the Playwright browser it opens the tool's own page. Commands that need `sudo` say: "You'll be asked for
+your computer password. Nothing shows while you type." **Check again** spins, then
+either turns the row green or says "Still not found. Did the command finish
+without errors?" No restart is needed.
+
+**Your name in Git** is a warning, never a failure: Git has no name and email for
+you yet, so commits are saved with a stand-in name ending in “via Vibe64”. The row
+shows the two `git config --global` lines, with a copy button.
+
+Where the host provides pinned versions, every check is needed and the rows keep
+the host's own wording; no install commands appear.
 
 GitHub sign-in is not a Health check. **Account settings → GitHub** shows the
 **GitHub Connection** card: **Connection ready** means Vibe64 can use GitHub.
 That card also holds **Git user.name**, **Git user.email** and **Save Git identity**.
+Connecting GitHub fills in your Git name and email only when Git has none; it
+never replaces ones you already set.
 
-A missing AI tool also appears in **Account settings → AI Accounts** and in AI onboarding,
-with a **Copy** button for the install command and **Check again**. When Vibe64 starts, it
-also prints one line for each AI tool it can't find.
+When Vibe64 starts in a terminal with no AI tool at all, it prints one plain
+message there with the Claude Code install command. It says nothing when one AI
+tool is installed.
 
 Health only reads. It never installs software, signs in or repairs anything, and
 a pass is not proof that a particular project builds.
@@ -28,8 +61,9 @@ a pass is not proof that a particular project builds.
 ## Ask Colleague
 
 Ask Colleague "check my setup" (or similar). Colleague runs the same Health checks
-and tells you which ones fail and what to do next for your system. It can open
-**Account settings** for you. Installing programs, signing in to GitHub or an AI
+and tells you which ones fail and what to do next for your system. It can also
+check single tools on request (“is Ruby installed?”), explain each step of the
+setup guides, and open **Account settings** for you. Installing programs, signing in to GitHub or an AI
 provider, and entering keys are things you do yourself; never paste a key or
 password into chat. Long command output stays on the Health page; Colleague sees a
 short summary of each check.

package/docs/colleague-usage/incoming-changes.md

@@ -45,18 +45,18 @@ AI**. The existing Temporary AI chat starts with Senior in this receiving sessio
 its Senior model and account must be available. It uses the working session
 currently selected in the receiving project and receives the exact reviewed
 commits and conflicting paths. It repairs those
-working files without committing, rebasing or publishing. You can also repair
+working files without committing, rebasing or pushing. You can also repair
 them manually. Preserve unrelated work and inspect both sides' intended behavior.
 
 When repair finishes, return to **Incoming changes → Review resolved conflicts**.
 This displays the proposed merge using the repaired conflicting files and the
 ordinary merge result for every other authored file, with regenerated Genesis
 maps included in the diff. Do not hand-edit generated maps. If regeneration
-fails, the merge stops without publishing or changing your session files.
+fails, the merge stops without pushing or changing your session files.
 Unrelated local changes are excluded.
 Review that diff, then explicitly choose **Merge into <target> → Merge contribution**.
 Vibe64 rechecks the candidate, receiving worktree/index/HEAD and both remote heads.
-Changed inputs require another review. AI completion alone never publishes or
+Changed inputs require another review. AI completion alone never pushes or
 proves a merge. The merge preserves both parents; local files, staged changes and
 the contribution branch remain available. Use ordinary Update to reconcile the
 receiving session afterwards.

package/docs/colleague-usage/integrations.md

@@ -5,7 +5,7 @@ application, separate from the AI accounts used to write its code. On mobile,
 reveal the project and use **Dashboard section**; scroll the selected integration's
 detail to its configuration and **Application connection** controls.
 
-1. Select **Development**, or **Production** when the host provides a published
+1. Select **Development**, or **Production** when the host provides a deployed
    application. Production uses its reviewed release and does not require a
    development session; its configuration is read-only.
 2. Select a configured integration, or use **Search integrations** and **Add**
@@ -14,7 +14,9 @@ detail to its configuration and **Application connection** controls.
    integration preselects no model: choose one in **AI model**, then enter its
    key reference (for example `env:APP_AI_API_KEY`) before **Save configuration**.
 3. Enter credentials through the indicated Env flow. Use the exact variable names
-   shown by that provider; do not put secrets into a conversation.
+   shown by that provider; do not put secrets into a conversation. When the host
+   offers saved values, the credential step can link one instead of entering a
+   value.
 4. Use **Check connection** or the displayed connect action. If consent is pending,
    select **Continue with provider** and finish the provider's own browser flow.
 5. Return and check connection status. A callback or successful transport alone
@@ -59,4 +61,4 @@ or credentials. If you have an unsaved Integrations draft, an outside change mar
 the form as changed elsewhere and preserves your draft; deliberately discard and
 reload or reconcile it before saving. A source operation can temporarily block
 saving; retry explicitly once it finishes. Saving configuration alone does not
-connect a provider, run the app, perform a session Save or publish the project.
+connect a provider, run the app, perform a session Save or deploy the project.

package/docs/colleague-usage/learning-course-catalogue.md

@@ -47,7 +47,7 @@ installs nothing new for that topic and enables nothing.
 Any signed-in person can install official catalogue courses. The catalogue
 location is fixed by the server, so the page can only install the courses it
 lists. Courses from other sources remain an owner/operator task (see
-[Author a lesson and publish its source](lesson-authoring.md)).
+[Author a lesson and save its source](lesson-authoring.md)).
 
 ### Preview courses
 
@@ -55,10 +55,10 @@ A **Preview** course can be installed so that it is ready, and the row says
 **Preview course: it can be installed; until it is released, only the workspace
 owner can try its lessons from Courses.** Its installed card keeps the
 **Preview course** chip. The workspace owner (on local Vibe64, you) sees
-**Try preview**, which starts the lesson exactly like **Start**; everyone else
+the ordinary **Start lesson** button, which starts the lesson as usual; everyone else
 sees the course with the note **Preview — the workspace owner can try it; it
 becomes startable when released** and no start button. Installing does not change
-this; once the course is released, everyone gets **Start**.
+this; once the course is released, everyone gets **Start lesson**.
 
 ## Updating a course
 

package/docs/colleague-usage/learning-environment.md

@@ -8,14 +8,11 @@ exactly the page you last had open in the other mode, also after a reload.
 ## Where the L button is
 
 - Home and project pages: the first button at the left of the header.
-- Hosted management pages (Projects, Users, AI Accounts and the other
-  management screens): the first control in the header, after the menu button.
 - It is the same size as the other header icon buttons (40px on a phone) and
   the first keyboard stop in the header; Enter or Space presses it.
 - Tooltips: **Switch to Learn** in Develop, **Back to Develop (your projects)**
   in Learn, where the L is solid yellow.
-- It appears only for a signed-in person. Hosted Vibe64 shows it after the
-  account prerequisites are complete.
+- It appears only for a signed-in person.
 
 ## Learn mode
 
@@ -29,13 +26,12 @@ which opens the Courses overlay, and your lesson's practice project.
 You have at most one lesson in progress. In Learn mode you are in your learning
 space only (see [Practice projects](learning-practice-projects.md)):
 
-- The lesson's practice project is the one project you can open. Hosted
-  project lists are empty. Opening any other project (for example from a saved
+- The lesson's practice project is the one project you can open. Opening any other project (for example from a saved
   address) takes you to the practice project with the note "You're in Learn
   mode. Press L to go back to your projects."
 - With no lesson in progress the page shows **No project selected** (below).
-  A lesson without a practice project shows the lesson
-  itself on that page (see [The Lesson tab](#the-lesson-tab)).
+  A studio lesson (one taught outside any project, with no practice project)
+  shows the lesson itself on that page (see [The Lesson pane](#the-lesson-pane)).
 - Nothing inside the lesson's practice project is limited: Preview, Files,
   Database, coding chats and Colleague all work. Account settings and AI
   Accounts stay available, so you can connect an AI during a lesson.
@@ -61,43 +57,59 @@ In Learn mode, while your lesson is loaded, a yellow bar above the project page
 names the lesson and plays its current step, beat by beat. How it works is in
 [The lesson step bar](lesson-step-bar.md).
 
-## The Lesson tab
+## The Lesson pane
 
-In Learn mode the current lesson is read on the project page itself, beside
+In Learn mode the current lesson is read on the page itself, beside
 Colleague, your teacher. The **Lesson** pane is the one place a lesson is read:
 the step list, the current step with its text, diagram, question or check,
 **Show me** and **Teach me** (see [Reading a lesson](#reading-a-lesson)), and
 the lesson's **Lesson finished** screen. Starting, continuing or resuming a
-lesson from Courses and Colleague's **Step N/M** button both open it here, at the step you were reading.
-
-- **On the lesson's practice project** the project switches read **Preview**,
-  **Dashboard** and **Lesson**. Select **Lesson** to read the lesson; Preview
-  keeps running behind it, so its App is still there when you select
-  **Preview** again. The address ends in `?pane=lesson`, so a reload, or
-  **L** back to Learn, returns to the Lesson tab.
+lesson from Courses and Colleague's **Step N/M** button both open it, at the step you were reading.
+
+The lesson is an on/off toggle of its own, separate from **Preview** and
+**Dash**:
+
+- **On the lesson's practice project** the header shows the **Preview** |
+  **Dash** switch and, after a thin divider, the **Lesson** toggle: a pill with
+  a school icon and a small switch. Off, it is outlined and its switch is to
+  the left (tooltip **Show lesson**). Press it and it turns solid Learning
+  yellow with its switch to the right and a check (tooltip **Hide lesson**):
+  the lesson now covers whichever of **Preview** or **Dash** was selected, as
+  a yellow sheet with **Lesson** and a **Hide lesson** button at its top.
+- **Pressing Lesson again hides the lesson.** So does **Hide lesson** on the
+  sheet, or choosing **Preview** or **Dash** (that one then shows). What it
+  covered is exactly as you left it: Preview is not reloaded and keeps its
+  App's page, and Dash keeps its section. **Preview** or **Dash** stays
+  selected in the switch while the lesson covers it.
+- The address carries the toggle as `?lesson=1`, apart from the pane, so a
+  reload, or **L** back to Learn, shows the lesson again over the same pane.
+- **On Management and other screens outside any project** (a studio lesson)
+  the toggle is on the lesson step bar. The lesson then lies over the right
+  side of the page (all of it on a phone) without moving or narrowing the
+  page underneath; it stays shown as you move between that page's tabs until
+  you hide it.
 - **On a lesson without a practice project** there is no
-  coding session, so there is no chat column and no pane switches: the Lesson
+  coding session, so there is no chat column and no toggle: the Lesson
   pane fills the page.
 - The reader lays itself out by the width it has: in a narrow pane (on a
   phone, or beside the chat column and an open Colleague) the step list becomes
   a row of numbered circles at the top (a tick for a passed step); the step
   text scrolls below them. When there are more circles than fit, the row
-  scrolls sideways and follows the current step as you press **Next step** or
-  **Previous step**, or reopen the lesson, so the step you are reading always
-  stays in view.
+  scrolls sideways and follows the current step as you move through the
+  lesson, so the step you are reading always stays in view.
 - Your reading place (step and scroll position) is saved for your account. A
   reload in the same tab returns to it; in another browser the lesson opens at
   the step you last read.
 - On a phone (and other narrow screens up to 980px wide) the page shows one
-  side at a time: the chat or the project pane. The next-pane button at the top
-  goes from **Lesson** to **Preview** to **Dashboard** and back to **Lesson**,
-  showing the next pane's name; without a practice project there is only the
-  Lesson pane, so the button is not shown.
+  side at a time: the chat or the project. The next-pane button at the top
+  goes from **Preview** to **Dash** and back, showing the next pane's name
+  (from under the lesson it hides the lesson too). The **Lesson** toggle is
+  beside it; turning it on shows the project side with the lesson over it.
 
 ## No project selected and `/app`
 
 `/app/learning` is Learn mode's page with no project selected: the usual
-project page with the chat column, the **Preview** and **Dashboard** switches
+project page with the chat column, the **Preview** and **Dash** switches
 (on a phone, the single switch button) and **Account settings**. The Dashboard
 still lists its sections, without opening them, and there is no **+** for
 sessions. It is used in two cases:
@@ -109,16 +121,22 @@ sessions. It is used in two cases:
   is in the chat column, which a phone shows first; on a desktop the chat
   column says your teacher will chat there once a lesson starts. The
   Dashboard says **No lesson in progress** with the same button.
-- **A lesson without a practice project**. The page shows
+- **A studio lesson**, taught outside any project. The page shows
   the lesson in its Lesson pane, with no chat column, and a **Dashboard**
   switch whose page says **No project selected** (see
-  [The Lesson tab](#the-lesson-tab)). **L** only switches mode.
+  [The Lesson pane](#the-lesson-pane)). **L** only switches mode.
+
+**Take the tour**, in the account menu, starts the course's orientation lesson,
+**Welcome to Vibe64**: a short studio lesson on the screens around you (your
+AI, Colleague, **L**). It starts like any other lesson: it switches you to
+Learn, the lesson already in progress just opens, and another lesson in
+progress asks **Archive your lesson in progress?** first. With no installed
+course naming one that you may start, Courses opens instead. The end of first-time AI setup offers the same tour once.
 
 A local Vibe64 has no Projects page. Its `/` and `/app` addresses open Develop's
 place, the project Vibe64 was started in, or in Learn mode Learn's place (the
 lesson's practice project, or no project selected). `/app` does this without
 reloading the page. If no project was started, it says so with **Try again**.
-On hosted Vibe64 `/app` is the Projects page.
 
 An old `?mode=learning` address from the retired Learning mode opens the ordinary
 project page.
@@ -128,13 +146,17 @@ project page.
 **Courses** on the lesson step bar, or in the project menu beside **L**, opens
 the Courses overlay above the page: the
 catalogue where you choose, start and manage lessons. It fills the screen, with
-a **Courses** tab, an **In progress** tab and an **Archived** tab, and a close
-button (×, **Close Courses**) at the right. A lesson is not read here: opening
+a **Courses** tab, an **In progress** tab and an **Archived** tab, and at the
+right a blue **Continue lesson** button (while a lesson is in progress) and
+a **Back** button. A lesson is not read here: opening
 one closes Courses and shows it in the page's
-[Lesson tab](#the-lesson-tab).
+[Lesson pane](#the-lesson-pane).
 
-- Press × or Escape to close it. The page you were on, and Colleague, are
-  visible again.
+- Press **Back** or Escape to close Courses. The page you were on (the
+  editor, Management or any other page), and Colleague, are visible again,
+  exactly as you left them.
+- Press **Continue lesson** to go on with your lesson where it runs: for a
+  project lesson its practice project, with the lesson shown.
 - Press **Courses** again to come back to the same tab.
 - A reload of the page leaves Courses closed; this tab remembers which Courses
   tab you were on for the next time you press **Courses**. In another browser it
@@ -147,23 +169,22 @@ and the tab row scrolls sideways when it does not fit.
 
 **Courses** shows course cards with progress, course pages, the **Course
 catalogue** and, for the workspace owner, **New course**; see
-[Choosing lessons and courses](learning-mode-ui.md).
+[Choosing lessons and courses](learning-mode-ui.md). A course lists only the
+lessons you can take on this Vibe64: a lesson about screens this installation
+doesn't have is simply not there.
 
-- **Start**, **Start next lesson**, **Start lesson** or **Try preview** start
-  the lesson, close Courses and open it in the Lesson tab of its practice
+- **Start lesson** or **Start next lesson** start
+  the lesson, close Courses and open it in the Lesson pane of its practice
   project (or, without one, of the no-project page). No chat is created. Starting a lesson while a different one is in progress first asks
   **Archive your lesson in progress?**: **Archive and start** or **Keep it**.
-- **Continue lesson** opens your lesson in progress in the Lesson tab.
+- **Continue lesson** opens your lesson in progress in the Lesson pane.
 - If a start was not confirmed, **Retry lesson start** repeats the same request.
 - Without AI set up, a lesson waits for it: see `learning-mode-ui`.
-- On hosted Vibe64 the workspace owner also sees **Author trial** with
-  **Resume author trial**, which opens the admitted draft snapshot in the
-  Lesson tab (see the hosted author-trial guide).
 
 ## In progress and Archived
 
 **In progress** shows your one lesson in progress with its practice project and
-**Open** (which opens it in the Lesson tab), **Restart** and **Delete**. **Archived** lists the lessons you
+**Open** (which opens it in the Lesson pane), **Restart** and **Delete**. **Archived** lists the lessons you
 finished or archived, each with **Delete**. Deleting asks once more (**Delete
 for good**); see [Practice projects](learning-practice-projects.md).
 
@@ -219,7 +240,7 @@ also has:
 - **Automatic check**: a step about an App interaction says "This step is
   checked automatically when you do it in your practice project", for example
   by pressing a button in its Preview. For a button step, read the step in
-  the Lesson tab, then select **Preview** (**Show me** does this) and press the
+  the Lesson pane, then select **Preview** (**Show me** does this) and press the
   App's button yourself in the practice project's visible Preview. Your press
   counts only for the lesson step Learning currently shows, in that lesson's
   own practice session, while Courses is not covering the app; the
@@ -254,17 +275,17 @@ also has:
   The ring stays for a few seconds, also on a phone while the practice
   project's page is still loading, and clears when you tap or click anywhere.
   Click the control yourself. If the place is not
-  available on the current page, the step comes back in the Lesson tab with the
+  available on the current page, the step comes back in the Lesson pane with the
   reason; open your practice project and try again.
 - **Teach me**: opens Colleague beside the step and sends it the message
-  "Teach me this step." for you. The step stays on screen in the Lesson tab;
+  "Teach me this step." for you. The step stays on screen in the Lesson pane;
   Colleague answers in its conversation. On a phone Colleague's full-screen chat opens over the step.
   If Colleague is not connected yet, an error says so; press **Teach me** again.
   If no AI is connected yet, nothing is sent:
   Colleague opens and says **Colleague cannot teach this step yet: it has no
   usable AI model, so nothing was sent.** with **Open AI Accounts**. Connect an
-  AI there, then press **Teach me** again; no Model routing step is needed,
-  because Colleague saves the recommended routing for a connected AI itself.
+  AI there, then press **Teach me** again; no Models step is needed,
+  because Colleague saves the recommended models for a connected AI itself.
   The message disappears as soon as an AI is usable.
 - **Lesson notes** (when the lesson has them) and **Previous step** /
   **Next step**.
@@ -277,8 +298,8 @@ correct answers of a question.
 
 ## Lesson finished
 
-When your own step result (in the Lesson tab, or an automatic check from your
-Preview press) completes the last required step, the Lesson tab opens on the
+When your own step result (in the Lesson pane, or an automatic check from your
+Preview press) completes the last required step, the Lesson pane opens on the
 **Lesson finished** screen: a check mark,
 **LESSON FINISHED**, the lesson title and "You completed every required step: X
 of Y steps passed." It finishes the lesson for you ("Finishing the lesson…"):
@@ -289,7 +310,7 @@ to try again. You don't need an AI for this. Then choose:
 
 - **Next lesson: <title>** starts the next unfinished lesson of the same course
   (when there is one).
-- **Back to courses** opens the Courses overlay; the Lesson tab goes away, since
+- **Back to courses** opens the Courses overlay; the Lesson pane goes away, since
   no lesson is in progress.
 
 ## The current step in Colleague
@@ -300,14 +321,14 @@ during voice chat) shows a small yellow **Step N/M** button with a school icon,
 or a check once that step has passed. Its tooltip is **Current lesson step:
 <step title>**. It is hidden while Colleague is minimised.
 
-Press it to see the current step in the page's **Lesson** tab (above), at that
+Press it to see the current step in the page's **Lesson** pane (above), at that
 step, with Colleague still open beside it on a desktop. On a phone Colleague's
-full-screen chat minimises so the Lesson tab is visible; its avatar button
-brings Colleague back. The step bar, the Lesson tab, Courses and Colleague share
+full-screen chat minimises so the Lesson pane is visible; its avatar button
+brings Colleague back. The step bar, the Lesson pane, Courses and Colleague share
 one lesson state, so they and other tabs stay in step.
 
 On a phone, when Colleague shows a lesson step for you its full-screen chat
-minimises and the Lesson tab shows that step. When Colleague opens Courses for
+minimises and the Lesson pane shows that step. When Colleague opens Courses for
 you, closing Courses (× or Escape) returns you to Colleague's chat, not the page
 behind it. **Show me** still shows the app.
 
@@ -325,8 +346,9 @@ attempt.
 
 ## What Colleague can do
 
-Colleague can explain these controls, show your current step in the Lesson tab,
-open or close the Courses overlay, point at the L button, and teach a step when you press **Teach me** or
+Colleague can explain these controls, show your current step in the Lesson pane,
+open or close the Courses overlay, point at or open a real place (the L button,
+a Dashboard section, your account menu and more), and teach a step when you press **Teach me** or
 ask. In Learn mode it opens and works only in the lesson's practice project;
 when you ask for another project it says you're in Learn mode and that **L**
 goes back to your projects. It switches mode, restarts or archives a lesson

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

@@ -4,7 +4,7 @@ The **L** button switches between **Develop** (your own projects) and
 **Learn** (lessons); see [The Learning environment (L)](learning-environment.md).
 In Learn mode the app bar turns yellow, and **Courses** (at the right of the
 lesson step bar, or in the project menu beside **L**) opens the Courses overlay, the catalogue where
-lessons are chosen; a lesson itself is read in the page's **Lesson** tab. This
+lessons are chosen; a lesson itself is read in the page's **Lesson** sheet (the **Lesson** toggle). This
 guide describes the overlay's **Courses** tab. Its **In progress** and
 **Archived** tabs are described in
 [Practice projects](learning-practice-projects.md).
@@ -17,7 +17,15 @@ its dots mirror the course's lessons, ticked when complete), a chip saying
 whether it is **Enabled**, a **Preview course** or **Disabled for new lessons**
 (plus **Lesson in progress** 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.
+and the next lesson. The banner counts the courses and lessons on the cards
+shown (an older release an update replaced is not counted).
+
+An installed lesson this version of Vibe64 cannot teach (for example it names a
+screen this Vibe64 no longer has) is left out of its course, and the card and
+course page say "One lesson is not shown because this version of Vibe64 can't
+teach it: <title>". The rest of the course works as usual. **Update** the
+course when Courses offers an update; starting that lesson is refused with the
+same reason.
 
 A lesson is complete when every required step has passed in your saved progress
 (required assessments, for a lesson in the earlier format). Only required
@@ -26,7 +34,7 @@ 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 lesson** reopens your lesson in progress when it belongs
-to that course. Otherwise **Start** starts the course's first published lesson
+to that course. Otherwise **Start lesson** starts the course's first published lesson
 that is not yet complete. **View course** opens the course page: a header with
 the cover and a ring of lessons complete, an **Up next** card, then its topics
 in order, each with its lessons, their title and code and a status of
@@ -39,9 +47,10 @@ project. **Back to courses** returns to the list. On a phone the cards stack in
 one column and the course page scrolls in the same pane.
 
 The lesson card above the course cards is headed "Lesson in progress · code"
-with the lesson title and, once reported, a ring of required steps passed with
-"N of M required steps passed. This lesson is complete." or "Continue the
-remaining steps." **Continue lesson** opens that exact attempt. Disabled,
+with the lesson title and, once reported, a ring reading **N of M required done**, and
+"N of M required steps done. This lesson is complete." or "Continue the
+remaining steps." It counts only the required steps, so it can differ from
+the step bar's **Step N of M**, which counts every step. **Continue lesson** opens that exact attempt. Disabled,
 unavailable, loading and error states are shown on the same page. **Refresh
 courses** rereads installed courses, progress and the course catalogue; after a
 step result is saved, Courses refreshes that lesson's progress by itself. If
@@ -53,19 +62,22 @@ official catalogue's topics and courses with **Install**; 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 opens on the Learn page (at `/app/learning`) with no project
+A studio lesson (taught outside any project) opens on the Learn page (at `/app/learning`) with no project
 selected: the lesson's own **Lesson** pane fills the page beside Colleague,
 with no pane switches, no chat column and no sessions (see the shared guide's
-*The Lesson tab*). Your own projects stay hidden until you
+*The Lesson pane*). Your own projects stay hidden until you
 press **L** to go back to Develop. Its steps say which real screens it uses.
 
 ## Starting, continuing, archiving and finishing
 
-While a start is in progress, Courses says **Starting the selected lesson and
-preparing its practice project. The lesson opens when this finishes.** Every
-start button stays disabled until the request settles. As soon as the start is
-confirmed, Courses closes by itself and the lesson opens in the **Lesson** tab
-of its practice project; you do not need **Continue lesson**. A practice project's Workspace setup can
+While a start is in progress, the button you pressed reads **Starting lesson…**
+with a spinner, and the same course card (or course page) says **Starting your
+lesson: Creating your practice project. This can take a while; the lesson opens
+by itself when it is ready.** Other start buttons stay disabled until the
+request settles. If the start fails, the card says **The lesson did not start**
+with the reason. As soon as the start is
+confirmed, Courses closes by itself and the lesson opens (its **Lesson** toggle on)
+over its practice project; you do not need **Continue lesson**. A practice project's Workspace setup can
 continue afterwards and the lesson becomes ready when setup succeeds (see
 [Practice projects](learning-practice-projects.md)). **Starting lessons is
 unavailable in this installation** appears only when the installation cannot
@@ -93,8 +105,8 @@ in progress, and **L** returns to it. When every required step has passed, the
 (see [The Learning environment (L)](learning-environment.md)).
 
 Starting or continuing a lesson, or **Open** under **In progress**, closes
-Courses and opens the lesson in the **Lesson** tab of its practice project; its
-**Preview** and **Dashboard** tabs are beside it. Setup repair there is ordinary project work
+Courses and opens the lesson over its practice project, with the **Lesson**
+toggle on beside the **Preview** | **Dash** switch; press it again to hide the lesson. Setup repair there is ordinary project work
 (ask that session's agent or use Workspace setup recovery); it is not a learner
 answer or a passed step.
 
@@ -125,12 +137,12 @@ disable-course` (see `docs/training-content.md`) and create another one.
 ## Preview courses
 
 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
+owner (on local Vibe64, you) sees the ordinary **Start lesson** and **Start next
+lesson** buttons beside the **Preview course** chip, on desktop and phone; they
+start an ordinary saved lesson. 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**.
+Once released, everyone gets **Start lesson**.
 
 ## What Colleague can do