vibe64 0.1.39 → 0.1.41

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

@@ -8,7 +8,7 @@ restart or delete it.
 
 ## One lesson in progress
 
-Starting a lesson (**Courses**, then **Start**) begins one run of it, called an
+Starting a lesson (**Courses**, then **Start lesson**) begins one run of it, called an
 attempt. The attempt owns:
 
 - its step results,
@@ -19,7 +19,10 @@ attempt. The attempt owns:
 You have at most one lesson in progress. It stays in progress until you finish,
 restart or delete it. Switching to Develop, or opening another page, only
 pauses it: its project, results and conversation are all kept, for as long as
-you like. Press **L** to come back to it.
+you like. Press **L** to come back to it. Like any project, a practice project
+left without activity for about 30 minutes is closed by idle cleanup: its
+Preview and assistant stop, while its files, results and conversation stay.
+Coming back to the lesson opens it again; start Preview again if you need it.
 
 If you start a different lesson while one is in progress, Vibe64 asks once
 whether to archive the current lesson first. Confirming archives it (see
@@ -66,6 +69,14 @@ A practice project is a complete project. Its chat, **Preview**, **Dashboard**
 and sessions work as in any project. The session that lesson preparation
 creates in it is an ordinary session.
 
+Which AI the practice project's chat uses depends on who you are. The workspace
+owner's lessons (and yours on Vibe64 on your own computer) run on the owner's
+main AI, as in any project. A team member's lesson runs on the team setup's
+Workspace-use models and their messages are sent straight away, without the
+owner's approval: the composer reads "Message your lesson's AI — *model* (team
+AI)". A personal plan is never used for a team member's lesson; see
+**Lessons** in [Team AI access](team-ai-access.md).
+
 ## In progress and Archived
 
 In Learn mode, **Courses** (on the lesson step bar, or in the project menu beside **L**) has an **In progress** list and an
@@ -76,7 +87,7 @@ lesson…** or **Loading archived lessons…** instead of staying blank.
 practice project's name (or **No practice project**). Without one it says
 **No lesson in progress. Start one from Courses.** The row has three buttons:
 
-- **Open** closes Courses and opens the lesson in the **Lesson** tab of its
+- **Open** closes Courses and opens the lesson (its **Lesson** toggle on) over its
   practice project (or, for a lesson without one, of the page with no project
   selected).
 - **Restart** turns into **Archive and restart**; press that to archive this
@@ -110,7 +121,7 @@ projects.
 ## Finishing a lesson
 
 When every required step has passed, the lesson's **Lesson finished** screen,
-in the page's **Lesson** tab, finishes it: the lesson counts as completed for good, and the attempt is
+in the page's **Lesson** sheet, finishes it: the lesson counts as completed for good, and the attempt is
 archived as one bundle (its record, practice project and conversation). The
 screen then offers **Next lesson** and **Back to courses**. **Start lesson** on
 the course page starts a new attempt with a fresh project, teacher and results; the

package/docs/colleague-usage/learning-teacher-guide.md

@@ -10,8 +10,13 @@ lesson's own caption. You then click it yourself.
 - The rest of the screen dims slightly, and a ring with a gentle ripple sits on
   one real tab, Dashboard section or button. A caption points at it; a thin bar
   on the caption shows the time left.
+- The caption sits beside the control when there is room (right, else left),
+  otherwise below or above it. It stays off the yellow lesson step bar whenever
+  another place fits, so the step text stays readable; on a narrow phone screen
+  it may have to cover part of the bar. The caption is slightly see-through and
+  clicks pass through it to whatever is underneath.
 - The ring is on the next step from where you are. On **Preview**, a path to the
-  ERD rings the **Dashboard** tab; once you are in **Dashboard → Database**, it
+  ERD rings the **Dash** (Dashboard) tab; once you are in **Dashboard → Database**, it
   rings the **ERD** button. When you are already at the place (for example
   Preview or **Dashboard → Files** is open), the ring goes around that open
   pane, with the caption inside its top edge when the pane fills the screen.
@@ -29,7 +34,7 @@ section the project does not show cannot be ringed.
 
 ## On a phone
 
-A phone shows the chat or one pane at a time, so the Preview/Dashboard tabs and
+A phone shows the chat or one pane at a time, so the Preview/Dash tabs and
 the Dashboard menu are hidden. Colleague's full-screen chat minimises itself
 first so the ring is visible. Then:
 
@@ -67,8 +72,9 @@ passes a lesson step. When a lesson asks you to find a place, click it yourself.
 
 ## Opening your lesson
 
-Colleague can show your current lesson step in the Learn page's **Lesson** tab,
+Colleague can show your current lesson step in the Learn page's **Lesson** pane
+(turning the **Lesson** toggle on),
 and open the **Courses** catalogue or close it so you can see the app, without
 ending the lesson. While the lesson is going, the **Step N/M** button in
-Colleague's header shows the current step in the Lesson tab (on a phone,
+Colleague's header shows the current step in the Lesson pane (on a phone,
 Colleague's chat minimises so the step is visible).

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

@@ -24,14 +24,18 @@ each, and the one you see always follows the mode:
   keep being followed while you are in Learn; their updates wait in Develop's
   conversation until you return. **Start fresh** and **Previous conversations**
   work within the conversation you are in.
-- In Learn, Colleague does not create assignments or watches; in Develop it does
-  not teach, read lessons or your teacher notes.
+- In Learn, Colleague does not create assignments, and it watches only your
+  lesson's practice project: ask "tell me when the agent answers" or, where
+  your Vibe64 can watch it, "tell me when my app is live". The watch only
+  reports; the step's own check still decides the step, and the watch ends with
+  the lesson attempt (finish, restart or delete). In Develop it does not teach,
+  read lessons or your teacher notes.
 
 ## Colleague as your teacher
 
 In Learn mode, **Courses** (on the lesson step bar, or in the project menu beside **L**) is the catalogue
 where you choose and start lessons; your current lesson is read on the Learn
-page itself, in its **Lesson** tab beside Colleague (see `learning-environment`).
+page itself, in its **Lesson** sheet beside Colleague (the **Lesson** toggle) (see `learning-environment`).
 You can read lessons yourself without AI. Choose **Teach me** on a lesson step,
 or ask Colleague about your lesson, and Colleague teaches the current step.
 **Teach me** opens Colleague beside the step and sends "Teach me this step.";
@@ -47,12 +51,12 @@ passes the step for you:
   arrive in pages; Colleague reads every page before claiming a step's text is
   missing.
 - It points at, or with "show me" opens, the real Vibe64 places the step uses,
-  replays the step's diagram, can show your current step in the **Lesson** tab,
+  replays the step's diagram, can show your current step in the **Lesson** sheet (turning the toggle on),
   and can open **Courses** or close it so you see the app. Courses keeps its
   place while closed.
 - In Learn mode with a lesson in progress, Colleague's header shows a small
   yellow **Step N/M** button (a check once the step passed). Pressing it shows
-  that step in the page's **Lesson** tab (see `learning-environment`); on a
+  that step in the page's **Lesson** sheet (see `learning-environment`); on a
   phone Colleague's full-screen chat also minimises so the step is visible, and
   its avatar button brings Colleague back. It appears on the desktop panel, the
   phone's full-screen chat and during voice chat. Develop shows no step button.
@@ -66,7 +70,7 @@ passes the step for you:
 On a phone, Colleague's full-screen chat minimises itself when it opens Courses,
 shows a lesson step or rings a control, so you can see it; reopen Colleague with
 its avatar button. **Teach me** on a phone opens Colleague's full-screen chat
-over the Lesson tab, which stays underneath.
+over the Lesson pane, which stays underneath.
 
 ## Colleague never judges
 
@@ -83,8 +87,8 @@ A step passes only through your own action in the lesson:
   now**; a response check first needs your own press of the App's control in this
   lesson's Preview.
 - **Review check**: the step shows its rubric, what your finished work must
-  show. Only your own **Check my work** asks your own AI (your Helper route in
-  **AI Accounts → Model routing**) to review your practice work against it;
+  show. Only your own **Check my work** asks your own AI (your **Explain &
+  check** model in **AI Accounts → Models**) to review your practice work against it;
   Colleague never runs a review for you. A review answers **Passed** (final) or
   **Not yet** with a comment and a hint. While the coding agent is still
   working it says "Wait until the agent finishes"; with nothing changed yet it

package/docs/colleague-usage/lesson-authoring.md

@@ -1,7 +1,7 @@
-# Author a lesson and publish its source
+# Author a lesson and save its source
 
 Ask Colleague to coordinate a coding agent, review the lesson in the same session,
-and publish its source through the existing Save or pull-request workflow.
+and save its source through the existing Save or pull-request workflow.
 Colleague can operate those controls when requested; it does not edit files or
 run a shell itself. Git publication, pinned course material and installation are
 separate results. The current Getting started course has four step-based lessons
@@ -32,7 +32,7 @@ text needs a new immutable topic/course pin, keeping earlier learners’ version
 
 For example: “In this lesson-authoring project and session, improve the introduction's
 wording, keep its step IDs, checks and App/diagram contracts, validate and bundle it,
-arrange a review, then publish the source as a draft PR. Do not install or enable it.”
+arrange a review, then save the source as a draft PR. Do not install or enable it.”
 This is an example instruction, never authority to execute it without the person's
 actual request. A how-to question makes no edits, assignment or external write.
 
@@ -58,21 +58,21 @@ it does not mean published or installed. A preview can be published as preview
 source when requested. Pedagogical trial, real exercise and animation acceptance
 remain explicit requirements before claiming a reviewed course release.
 
-## Publish through the native repository workflow
+## Save through the native repository workflow
 
 After coding settles, inspect **Changes** and the exact repository/branch
 reported by the session. **Save** captures ALL current work, not selected files.
 A managed Vibe64 Git Save updates its canonical project; a GitHub Save pushes to
 the reviewed repository branch. Colleague can request native Save after an explicit
-Save/publication instruction and passes its unchanged destination review. It
+Save instruction and passes its unchanged destination review. It
 cannot bypass active-agent, stale-source, account or required-PR rules, or discard
-unrelated work to make publication pass. An ambiguous target stays unresolved.
+unrelated work to make Save pass. An ambiguous target stays unresolved.
 On mobile, reveal the project and use its Dashboard section chooser for Changes
 or Pull requests. The same native Save/PR permissions and review apply.
 
 For a required or requested PR workflow, Colleague can use the existing PR creation
 operation with the reviewed destination and requested title/body; draft is the
-default. PR creation saves and publishes the session's work. An already bound PR
+default. PR creation saves and pushes the session's work. An already bound PR
 is returned rather than silently edited. **Pull requests** shows actual remote
 source/base commits, checks and review blockers. Marking a draft ready or merging
 requires the person's corresponding instruction and the original fresh review;
@@ -80,10 +80,10 @@ creating a PR does not authorise merge. Use only a repository-enabled merge meth
 covered by that instruction. Save, PR creation or merge never deploys Vibe64.
 
 After success, report the actual saved destination or returned PR and current
-remote status. A coding agent's “pushed” message is not publication proof. After
+remote status. A coding agent's “pushed” message is not proof that Save pushed. After
 an uncertain result, inspect the original operation/PR before a deliberate retry;
-`published_needs_reconcile` means publication happened and local reconciliation
-still needs recovery. Do not republish automatically. Existing **Update this
+`published_needs_reconcile` means the push happened and local reconciliation
+still needs recovery. Do not push again automatically. Existing **Update this
 session (rebase)** and coding-agent conflict repair apply only when requested.
 
 ## Validate, bundle and pin
@@ -189,8 +189,8 @@ own snapshots, and for disabling a release.
 In supported hosted installations, ask Colleague to admit your exact clean
 committed snapshot from the authorized authoring session. Then open Learning with
 **L**; on its **Courses** tab the **Author trial** card shows the snapshot's lesson
-and release, and **Resume author trial** opens it in the ordinary lesson reader, the page's **Lesson** tab. This saved trial has isolated progress; it is not an
-enabled learner course. Ordinary **Start** still requires a published lesson in
+and release, and **Resume author trial** opens it in the ordinary lesson reader, the page's **Lesson** sheet. This saved trial has isolated progress; it is not an
+enabled learner course. Ordinary **Start lesson** still requires a published lesson in
 an enabled release. Local validation/bundling alone admits no trial. Do not change
 a draft's status to bypass that guard or report a trial as published progress.
 
@@ -198,7 +198,7 @@ Internal snapshot acquisition also retains the authoring session's normal
 source protections: AI work, pending review or cleanup, and Workspace setup
 must finish before its committed content can be captured. A closing, renewing
 or unavailable source is refused. The saved trial control captures no source,
-automatically stops no work and does not publish the source.
+automatically stops no work and does not save or push the source.
 
 A workspace operator can now provision approved local lesson content through the
 terminal commands documented in [Local operator provisioning](../training-content.md#local-operator-provisioning).

package/docs/colleague-usage/lesson-step-bar.md

@@ -1,31 +1,44 @@
 # The lesson step bar
 
 The yellow lesson step bar above the project page plays the current lesson
-step: its position, beats, **Step** and **Courses**. The rest of
+step: its position, beats, **Back** and **Next**, and **Courses**. The rest of
 Learn mode is in [The Learning environment](learning-environment.md).
 
 In Learn mode, while your lesson is loaded, a yellow bar above the project page
-names the lesson and shows **Step N of M** with the step's title and status.
-**Previous step** and **Next step** (arrow buttons) move through the steps.
-**Step** (the ≡ button) opens the whole current step right under the bar, in
-place, with everything the Lesson tab offers for it: its text, diagram and
-**Play**, **Done**, **Mark as done**, its question or **Check now**, **Show me**,
-**Teach me** and **Previous step**/**Next step**. It covers the top of the page
-(at most about two thirds of the screen, scrolling inside); **Step** again or
-Escape closes it, and **Show me** closes it so the place it shows is in view.
-This tab remembers whether it is open. To read the step in the page's
-**Lesson** tab, select that tab (see [The Lesson tab](learning-environment.md#the-lesson-tab));
-the bar has no separate Open button. **Courses**, at its right end (a book icon
-on a phone), opens the Courses overlay to choose another lesson. The bar is
-always shown in full; it cannot be collapsed or hidden. On a phone the lesson
-name is hidden.
+names the lesson and shows **Step N of M** (this step's number among all the
+lesson's steps) with the step's title and status.
+
+**Moving through the lesson.** One labelled pair of buttons, with the same
+names for screen readers and the keyboard:
+
+- **Back** goes back one part of this step, or into the previous step from its
+  first part. It is greyed out at the very start of the lesson.
+- The forward button says exactly what it does: **Next** while this step has
+  more parts, **Next step** on its last part (and on a step without parts),
+  and **Finish** on the last step once every required step is done (it shows
+  the **Lesson finished** screen). On the last step before that there is no
+  forward button. There is no second **Next step** button.
+
+On a practice project the **Lesson** toggle is in the header beside **Preview**
+| **Dash** (see [The Lesson pane](learning-environment.md#the-lesson-pane)); on
+Management and other screens outside any project it is on the bar, between
+the forward button and **Courses**. Press it to show the lesson (it turns
+yellow with its switch on); press it again to hide it. On a lesson without a
+practice project the lesson is already the whole page, so there is no toggle.
+
+Away from the lesson's practice project (for example on Management), the bar
+also offers **Open practice project**, which goes back to that project's
+editor. **Courses**, at its right end (a book icon on a phone), opens the
+Courses overlay to choose another lesson. The bar is always shown in full; it
+cannot be collapsed or hidden. On a phone the lesson name is hidden.
 
 ### Steps with beats
 
 Some steps walk you through the real page from the bar itself, one short line
 (a *beat*) at a time, while the lesson stays where it is. The bar then shows
-the lesson name, **N/M** (the step) and a dot per beat (the filled dot is the
-current one), then the beat's line:
+the lesson name, **Step N of M** and a dot per beat, the parts of this step
+(the filled dot is the current one; hovering the dots says, for example,
+**This step: part 2 of 4**), then the beat's line:
 
 - A *show* line rings the place it names (for example the **Preview** tab or the
   coding chat) and moves on by itself after a few seconds; a thin line under
@@ -50,8 +63,8 @@ current one), then the beat's line:
   it opens the place (or the file), reveals and focuses the coding chat, opens
   Courses or Colleague (without asking it anything), reloads the Preview, or
   sends the line's quoted prompt as your next message in the practice
-  project's Main chat. That message shows a **Sent by the lesson** chip under
-  it. On a **Save** line it only points at **Save**: saving stays yours. On a
+  project's Main chat (for a team member, on the team AI, with no owner
+  approval). That message shows a **Sent by the lesson** chip under it. On a **Save** line it only points at **Save**: saving stays yours. On a
   line about waiting for the agent, pressing the App's button, minimising
   Colleague or pressing **L** there is no Do it for me (for **L** it shows
   where the button is). If it cannot be done here (for example the chat cannot take a
@@ -62,25 +75,25 @@ current one), then the beat's line:
   **Set up your AI**; see `learning-mode-ui`.
 - On a step you would finish with **Done**, doing every *do* line of it marks
   the step done by itself.
-- **Back** and **Next** (arrows) move one beat, and into the previous or next
-  step at either end.
+- **Back** and **Next** move one beat; on the step's last beat the forward
+  button reads **Next step** and goes into the next step.
 - After the last beat the bar shows the step's own control: **Done**, **Mark as
   done**, **Check my work** (an automatic check, or a review; a check that does
-  not pass says why under the line) or **Answer in Step** for a question, which opens the
-  step under the bar. When the step has passed it shows **Next step**. **I'm stuck**
+  not pass says why under the line) or **Answer in Lesson** for a question, which shows the
+  step in the Lesson pane, beside a quieter **Next step**. **I'm stuck**
   (on a *do* line, and after the last beat of a step that **Check my work**
-  decides, until the step passes; also in **Step** beside **Teach me**) opens
+  decides, until the step passes; also in the Lesson pane beside **Teach me**) opens
   Colleague and asks it for help with this step (see `learning-with-colleague`).
   On a phone a *do* line keeps only **Do it for me** on the bar; **I'm stuck**
-  is then in **Step**.
+  is then in the Lesson pane.
   A step never moves on by itself.
-- **Show me** on such a step (in the bar's step or the Lesson tab) plays its
+- **Show me** on such a step (in the Lesson pane) plays its
   beats again from the first one.
 
 **Check my work on a reviewed step.** Some steps are checked by a review of
-your work: the bar's line (and the step under **Step**) shows what the review
-looks for. **Check my work** uses your own AI (the Lesson review route in AI
-Accounts → Model routing) to look at the changes in your practice project
+your work: the bar's line (and the step in the Lesson pane) shows what the review
+looks for. **Check my work** uses your own AI (the **Explain & check** model in
+AI Accounts → Models) to look at the changes in your practice project
 (and, when the step says so, your coding chat); the line says **Checking your
 work with your AI…** for up to about a minute, without a Cancel. **Passed ✓**
 with the reviewer's comment passes the step for good. **Not yet:** says what
@@ -92,7 +105,8 @@ why, nothing is recorded, and you can press **Check again**. Colleague never
 runs a review or passes a step for you.
 
 This tab remembers the beat and the pause; another tab or device starts the
-step at its first beat. On a phone the bar has two lines: the position and arrows above,
-the beat's line and its one button below; **Step** and **Courses** show only
-their icons, and the open step fills the width. A step without beats shows its title
-and status as before, and **Show me** when it can point at a place.
+step at its first beat. On a phone the bar has three tidy rows: the position
+with the icon buttons (**Courses**, **Open practice project** and, off a
+project, **Lesson**), then the beat's line and its one button, then **Back**
+at the left and the forward button at the right. A step without beats shows
+its title and status as before, and **Show me** when it can point at a place.

package/docs/colleague-usage/main-chat-approvals.md

@@ -0,0 +1,150 @@
+# Main chat messages that wait for the owner's approval
+
+A project's Main chat always runs on the workspace owner's AI. When a team
+member writes in Main chat, the message does not reach the assistant straight
+away: it waits in **Messages for approval** until the owner approves, edits or
+declines it. The owner's own messages are sent as usual and never wait.
+
+Temporary chats, Colleague and the other assistants a member uses run on that
+member's own team setup; only Main chat waits for approval.
+
+A team member's own lesson is the exception. A practice project is private to
+its learner, so its Main chat runs on the team setup and the member's messages
+(and the lesson's **Do it for me** prompts) are sent straight away, with no
+approval. The composer then reads "Message your lesson's AI — *model* (team
+AI)". See **Lessons** in [Team AI access](team-ai-access.md). The owner's own
+lessons are unchanged. Messages sent by
+another session (project messages) are not person requests and never wait.
+
+## Send a message as a team member
+
+1. Open the project's coding session. Main chat shows the hint
+   "Main chat runs on {owner}'s AI. {owner} approves each message." and the
+   placeholder "Message main chat — {owner} approves before it's sent".
+2. Type the message and choose **Send for approval**. The button keeps that
+   label while the assistant is working; members have no separate Steer button.
+3. A card appears directly above the composer: **You** with the time, the line
+   "Waiting for {owner} to approve", the message and a **Waiting** chip.
+
+Messages for approval are text only: the member composer has no attachment
+button. A request that carries attachments is refused with "Messages for
+approval are text only. Remove the attachments and send again."
+
+You can have up to 5 messages waiting in one session. A sixth is refused with
+"You have 5 messages waiting. Wait for {owner} to review them, or withdraw one."
+
+If the assistant was working when you sent the message, the card adds: "Sent
+while the assistant was working. It joins the current turn if it's still running
+when {owner} approves." Otherwise the approved message starts a new request.
+
+### Change or withdraw a waiting message
+
+- **Edit** replaces the text with a box. Change it and choose **Save**, or
+  **Cancel** to keep the original. An empty text is refused with "Write a
+  message, or withdraw it."
+- **Withdraw** removes the message from the queue. It stays as the one-line row
+  "Withdrawn by you".
+
+Only the sender can edit or withdraw, and only while the message is waiting.
+If the owner has already decided, the change fails with "This message was
+already sent." (or declined or withdrawn); if it is being sent, with "This
+message is being sent."
+
+### What you see after the owner decides
+
+While the chat is open you get a snackbar: "{owner} approved and sent your
+message" or "{owner} declined your message". The card becomes a one-line row:
+
+- **Sent by {owner} · time**, with "· Edited by {owner}" when the owner changed
+  the text first, and **Show in chat**, which scrolls the conversation to the
+  delivered message.
+- **Declined by {owner} · time**, with the owner's note quoted underneath when
+  they wrote one.
+
+Under each row is the start of the message on one line. On a declined or
+withdrawn row, select it to show the whole text, to copy, rework and send it
+again.
+
+The delivered message appears in Main chat as an ordinary user message with the
+line "{sender} · approved by {owner}" under its text. The assistant's reply is
+visible to everyone with access to the project.
+
+Decided rows stay for 24 hours; at most three show at once and the rest are
+behind **Show earlier (n)**.
+
+## Review messages as the owner
+
+New messages announce themselves in several places:
+
+- In any open tab where you have that project's Main chat open, a snackbar
+  "{sender} sent a message for your approval in {project}" with **Review**,
+  which selects the session and scrolls to the waiting messages.
+- A **{n} waiting** chip in the Main chat header; choose it to reveal the queue.
+- The browser tab title starts with "({n}) " while any messages wait.
+- Project lists that support it show a **{n} waiting** badge on the project.
+
+Each waiting card shows "{sender} wants to send · time", the message and these
+actions:
+
+- **Approve & send** sends the message unchanged.
+- **Edit then send** opens a box with the message. Change it and choose **Send**,
+  or **Cancel**. The sender sees "Edited by {owner}" on the Sent row.
+- **Decline** opens "Add a note for {sender} (optional)", up to 500 characters.
+  Choose **Decline** to confirm, or **Cancel**.
+
+While your approval is being delivered the chip reads **Sending…** and the
+buttons are disabled. The owner cannot edit or withdraw a member's message other than by
+approving it with edited text.
+
+### How an approved message is delivered
+
+Approving sends the message exactly as if you had sent it yourself, on your AI:
+
+- No turn running: it starts a new request (in Auto, the Router classifies it).
+- A turn is running that accepts guidance (including Auto working or an active
+  goal): it joins that turn as guidance.
+- A turn is running that cannot take guidance, a delivery is uncertain, or
+  recovery is in progress: the send fails, the message goes back to **Waiting**
+  and the card shows "Couldn't send: {error} Try again." Choose
+  **Approve & send** again when the turn finishes.
+
+If a page reload interrupts a send, the card may stay on **Sending…** with
+**Send again**. Sending again reuses the same delivery, so the message is never
+delivered twice. Its text can't be edited while it is sending; an edited text
+is always a new delivery.
+
+If the sender edited the message after you opened it, your action fails with
+"{sender} changed this message. Review it again." Read the new text and decide
+again.
+
+## Other team members
+
+Members who did not send a message see the same cards, headed "{sender}", with
+"Waiting for {owner} to approve" and no actions.
+
+## Phone
+
+On a phone the queue collapses to a bar above the composer, "{n} messages
+waiting for approval" (or "Messages for approval" when only decided rows
+remain). Tap it to open the **Messages for approval** sheet with the same cards;
+buttons stack full width and Edit or Decline open inside the sheet. Close the
+sheet with its close button or by tapping outside it.
+
+## What Colleague can do
+
+Colleague can explain all of this. When a team member asks Colleague to send a
+message to Main chat, it goes through the same queue and waits for the owner;
+Colleague must say so rather than claim it was delivered. In the member's own
+lesson there is no queue: the message is sent to the lesson's team AI. Approving, editing,
+declining and withdrawing are human-only: Colleague cannot do them, so it should
+point the person to the buttons above.
+
+## Errors
+
+| Message | Meaning |
+|---|---|
+| Only the workspace owner can approve messages. | A member tried to approve or decline. |
+| Only {sender} can change this message. | Someone else tried to edit or withdraw it. |
+| {sender} changed this message. Review it again. | The text changed since you looked. |
+| This message was already sent. / declined. / withdrawn. | It has been decided. |
+| This message is being sent. | Delivery is in progress; wait for it. |

package/docs/colleague-usage/preview-browser-checks.md

@@ -49,7 +49,11 @@ matching managed runtime. A version error is a test-runtime blocker; interactive
 checks can use the existing managed Preview browser. Report the exact required
 version to the platform operator instead of installing a separate browser.
 On a computer without managed browser runtimes, the agent runs the project's own
-Playwright (`npx playwright test`). If that browser is missing, the agent reports
+Playwright (`npx playwright test`). Interactive Preview checks (screenshot, eval)
+use the project's own Playwright, or else the `playwright` command installed on
+this computer, so a project in another language needs no Playwright package. If
+neither exists, the agent asks you to install Playwright on the computer rather
+than adding it to a non-Node.js project. If that browser is missing, the agent reports
 it and asks you before running `npx playwright install chromium`; installing it
 is your decision.
 

package/docs/colleague-usage/preview-starting-application.md

@@ -3,7 +3,7 @@
 This continues [Previewing a web application](preview.md).
 
 In an empty project's **Preview**, choose **Use this starter** on the desired
-Basic, Database, or Accounts app. On mobile, open **Show project** first. Import
+starter, such as Basic app, App with no users, but a database, or App with users. On mobile, open **Show project** first. Import
 adds source to this session; review it and use **Save** to keep it in the project.
 Setup and running the app are separate operations.
 
@@ -19,6 +19,15 @@ apply one. After you choose a starter and accept its offer or directly request
 it, Colleague can use the existing onboarding action and recheck the result.
 A successful import does not mean dependencies are prepared or Preview is running.
 
+When a starter needs a resource such as its database, Preview waits for it and
+says so instead of starting. Where the host supplies that resource (hosted
+Vibe64's managed databases), Preview says "Vibe64 is still setting up this
+app's database" until workspace setup finishes; press **Check again** then.
+Where you supply it, Preview names the variables to set, for example "set
+DB_DATABASE in Env (in Dash, under Development)": open **Dash → Env**, choose
+**Development**, add the value (see [Development Env](development-env.md)) and
+press **Check again**.
+
 For recurring **Preview could not load an application resource** errors, enable
 Preview diagnostics in the affected Studio browser before reproducing: add
 `vibe64_preview_debug=1` to the page URL, or set

package/docs/colleague-usage/project-language-tools.md

@@ -20,7 +20,16 @@ onboarding does not offer PostgreSQL variants yet (for example
 `django-postgresql`); it offers the MySQL or SQLite variant instead.
 
 If **Preparing workspace** fails, expand its output, correct the reported cause
-and choose **Retry**. If Preview cannot start, use **Show run output**. On mobile,
+and choose **Retry**. On your own computer, the panel also lists the tools that
+step uses: each one that runs shows its version and where it was found; one that
+is missing or didn't start shows one sentence, the install command for this
+computer with a copy button, **Check again** and **Other ways**. Language
+runtimes install with mise (`mise use -g ruby@3.4`, `mise use -g python@3.13`,
+`mise use -g java@temurin-25`), which needs no administrator password; build
+tools and libraries for native packages (`cpp`) use `sudo apt install …` on
+Debian/Ubuntu or `brew install …` on macOS. **Other ways** opens the setup
+guide for this computer ([Linux](set-up-linux.md), including Fedora and Arch,
+or [macOS](set-up-macos.md)), which also explains adding mise to your shell. Coming back to the tab checks again. If Preview cannot start, use **Show run output**. On mobile,
 open **Show project** first. A missing runtime needs installation by the host
 administrator; changing the declaration to `shell` does not supply the missing
 tool. Standalone users install/configure the missing tool in their own environment
@@ -31,6 +40,11 @@ interpreter installed does not prove that the project consumes the selected
 library: the project's declared verification must demonstrate that. Normal
 release inputs and unrelated sessions keep their own source selection.
 
+When a runtime is missing, the coding agent stops and says which one, pointing
+to the tool row's command. It never runs `sudo` and never installs a runtime into
+the project folder (for example with `mise use` without `-g`).
+
 Colleague can explain preparation errors and offer its supported status/retry
-actions. These instructions do not give it shell access or permission to install
+actions. On your own computer it can also check whether a named tool runs now,
+for example after you ran an install command. These instructions do not give it shell access or permission to install
 host software. The coding agent can repair project commands after being asked.

package/docs/colleague-usage/project-settings.md

@@ -19,7 +19,7 @@ Gradle, NuGet (.NET) or custom; it is independent of the relationship.
 Custom requires a Preparation script path relative to this project, with its
 runtime declared in Stack. Every other type disables and clears the script; the
 project's own declared Verify command, not Vibe64, treats that source.
-Use **Save connected projects** for the list; ordinary project Save publishes
+Use **Save connected projects** for the list; ordinary project Save pushes
 that source edit. See **Configure connected projects** for access and recovery.
 
 Hosted repository settings can also specify whether GitHub Save permits direct

package/docs/colleague-usage/project-setup.md

@@ -34,8 +34,9 @@ which should be the default. Supply an email, login or user ID, not a password.
 The agent should reuse answers you already gave and wait for your choices.
 Choosing a name such as “admin” does not grant that account administrator rights.
 
-The coding agent can implement the application's Preview identity adapter after
-you accept that work. It can also save the named accounts you give or confirm
+An application with login accounts gets a Preview identity adapter by
+default: when it is missing, the coding agent sets it up as part of the work
+rather than asking first. It can also save the named accounts you give or confirm
 (for example `admin` and `user` with their emails) and then verify each in Preview;
 it never creates accounts or changes roles for this. To configure them yourself,
 open **Dashboard > App access** and use **Managed app access > Add identity**. Enter **Name**, **App identifier**
@@ -55,15 +56,24 @@ work. Public applications and non-web projects do not need preview accounts.
 ## New project
 
 1. Open the project and create or select its coding session. At **What would you
-   like to build with?**, review the available starter cards. The installed JSKIT
-   starters include **JSKIT · Public app** (no accounts or database) and
-   **JSKIT · Accounts and database** (sign-up, login and MySQL persistence).
-   Available starters depend on the installation; do not assume an absent card exists.
+   like to build with?**, review the available starter cards, grouped by
+   technology. The official catalogue lists JSKIT first: **JSKIT · Basic app**
+   (no accounts or database), **JSKIT · App with no users, but a database** (MySQL) and
+   **JSKIT · App with users** (sign-up, login and MySQL). Then one **Basic app**
+   each for Django, Rails, Spring Boot, Express and Next.js: a small notes form
+   saved to SQLite (MySQL/MariaDB for Spring Boot), with ready tests. Only the
+   Rails starter has sign-in, with a seeded development account
+   (`developer@example.com` / `developer`); for the others, ask the agent to add
+   accounts. Available starters depend on the installation; do not assume an
+   absent card exists.
 2. Choose **Use this starter →** on the intended card only when it matches the
    product you want. Preparation adds it to this session; use the session's
    **Save** control to keep the work in the project. A failed application reports
    its error and preserves existing work.
-3. Alternatively, choose **Start through conversation** to open Temporary AI for
+3. You can also describe the app directly in the session's main chat. In an
+   empty folder that was never set up, the coding agent first initializes Genesis,
+   then proposes a Blueprint and the matching Stack components for your answer.
+4. Alternatively, choose **Start through conversation** to open Temporary AI for
    project creation. Discuss what you want, who uses it and its first useful
    outcome before choosing technology. If no starters are configured, this
    conversation route is still offered when a coding assistant is available.