vibe64 0.1.40 → 0.1.41

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
@@ -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
@@ -67,8 +76,8 @@ 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 in the **Lesson** tab
-of its practice project; you do not need **Continue lesson**. A practice project's Workspace setup can
+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
@@ -96,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.
 

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

@@ -87,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
@@ -121,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

@@ -72,7 +72,8 @@ 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** pane,
+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 pane (on a phone,

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

@@ -35,7 +35,7 @@ each, and the one you see always follows the mode:
 
 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.";
@@ -51,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.

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

@@ -189,7 +189,7 @@ 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
+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.

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, **Lesson** 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.
-**Lesson** (a school-cap icon), on a lesson with a practice project, shows the
-lesson in the project pane at its current step, with everything for it: its
-text, diagram and **Play**, **Done**, **Mark as done**, its question or **Check
-now**, **Show me**, **Teach me**, **I'm stuck** and **Previous step**/**Next
-step** (see [The Lesson pane](learning-environment.md#the-lesson-pane)). It
-stays pressed while the lesson shows, and the header's **Preview** or **Dash**
-leaves it. On a lesson without a practice project the lesson is already the
-whole page, so the bar has no **Lesson** 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
@@ -62,12 +75,12 @@ 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 Lesson** for a question, which shows the
-  step in the Lesson pane. When the step has passed it shows **Next step**. **I'm stuck**
+  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 the Lesson pane beside **Teach me**) opens
   Colleague and asks it for help with this step (see `learning-with-colleague`).
@@ -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; **Courses** shows only its icon
-and **Lesson** its icon and name. 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/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-setup.md

@@ -58,8 +58,8 @@ work. Public applications and non-web projects do not need preview accounts.
 1. Open the project and create or select its coding session. At **What would you
    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 · Database app** (MySQL, no accounts) and
-   **JSKIT · Accounts app** (sign-up, login and MySQL). Then one **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

package/docs/colleague-usage/publishing.md

@@ -42,7 +42,9 @@ afterwards **Unlock** it for 15 minutes when you add accounts or publish, and
   address, so targets using it keep working with the new token.
 - **Recovery kit**: **Save kit** (or **Manage**) downloads every key as one file under a second
   passphrase; keep both off this computer. **Restore** brings them back on a
-  new computer. The panel says when a key is newer than your last kit.
+  new computer and says how many came back ("Restored 1 key."). When a key is
+  newer than your last kit, the panel reads "Your recovery kit is out of date",
+  says when it was last saved, and offers **Save kit**.
 
 ### Add a target
 

package/docs/colleague-usage/starter-apps.md

@@ -4,9 +4,9 @@ In an empty project's onboarding, starters are grouped by technology. Choose
 the JSKIT starter that matches the app:
 
 - **Basic app**: responsive shell, server/client/browser tests, no database or login.
-- **Database app**: the same shell plus MySQL migrations and isolated database
+- **App with no users, but a database**: the same shell plus MySQL migrations and isolated database
   tests, without accounts.
-- **Accounts app**: sign-up, login, private pages and persisted profiles, plus
+- **App with users**: sign-up, login, private pages and persisted profiles, plus
   account-persistence and browser tests.
 
 For another framework, each of Django, Rails, Spring Boot, Express and Next.js

package/docs/training-content.md

@@ -83,7 +83,7 @@ declare them.
 A v3 `lesson.json` declares `schemaVersion: 3` and everything v2 has, plus
 `stage`: `"project"` for a lesson taught in its practice project (it needs its
 `exercise`), or `"studio"` for one taught on the screens outside any project
-(its Lesson pane docks beside the page). Learn mode opens a lesson where its
+(its Lesson sheet lies over the page while the Lesson toggle is on). Learn mode opens a lesson where its
 stage says.
 
 A step may check a fact: `"check": { "kind": "fact", "fact": "ai-ready" }`,
@@ -200,7 +200,7 @@ One beat per line: `<show|do|check> <target>[ <path>]: <text>`.
   step's `check.rubric` from `lesson.json`, its single source.
 - Places: `preview`, `dashboard`, `database-erd`, `database-data`, `files`,
   `changes`, `git-log`, `session-info`, `architecture`, `learning` (the **L**
-  button), `lesson` (the step bar's **Lesson** button), `chat` (the coding chat), `colleague`,
+  button), `lesson` (the **Lesson** toggle), `chat` (the coding chat), `colleague`,
   `courses`, `lesson-bar` (the bar itself), `save` and `reload-preview`.
   `dashboard` and `lesson-bar` can only be shown.
 - 1–8 beats. Only `lesson`, `lesson-bar`, `courses`, `learning`,

package/node_modules/@jskit-ai/assistant-core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jskit-ai/assistant-core",
-  "version": "0.1.239",
+  "version": "0.1.240",
   "type": "module",
   "exports": {
     "./client": "./src/client/index.js",

package/node_modules/@jskit-ai/assistant-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jskit-ai/assistant-runtime",
-  "version": "0.1.233",
+  "version": "0.1.234",
   "type": "module",
   "exports": {
     "./client": "./src/client/index.js",

package/node_modules/@jskit-ai/assistant-voice/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jskit-ai/assistant-voice",
-  "version": "0.1.40",
+  "version": "0.1.41",
   "type": "module",
   "exports": {
     "./client": "./src/client/index.js",

package/node_modules/@jskit-ai/connectors-catalog/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jskit-ai/connectors-catalog",
-  "version": "0.1.63",
+  "version": "0.1.64",
   "type": "module",
   "exports": {
     "./shared/ai": "./src/shared/ai.js",

package/node_modules/@jskit-ai/realtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jskit-ai/realtime",
-  "version": "0.1.243",
+  "version": "0.1.244",
   "type": "module",
   "exports": {
     "./server/RealtimeProvider": "./src/server/RealtimeProvider.js",

package/node_modules/@local/vibe64-genesis/bin/vibe64-genesis-host-context

@@ -988,86 +988,83 @@ Possible answers:
 start a duplicate or replacement server. If it is unavailable, report that blocker. Describe only rendered browser evide\
 nce.","When adopting an authenticated app, or when its login blocks Preview inspection, inspect identity support/names w\
 ith `vibe64-helper preview status`; prefer `vibe64-helper preview browser identity <configured-name>` to requesting pass\
-words. If unconfigured, ask which existing accounts (email/login/user ID) represent admin and other required roles, and \
-the default. Reuse prior answers; wait for their choices before configuring access. Never infer admin rights from names \
-or the Vibe64 viewer.","A web app with login accounts has an application-owned adapter declared in the Outputs `#### Pre\
-view identity` block (`vibe64-helper spec outputs` and `vibe64-helper spec preview-identity-command`); when it is missin\
-g, set it up from the app framework's own pattern as part of the work instead of merely offering it. Save the named sele\
-ctors the person gives or confirms with `vibe64-helper preview identities save` (`vibe64-helper spec preview-identities`\
-); you may propose them from existing app accounts, then verify each with `vibe64-helper preview browser identity <name>\
-`. Use existing sessions/permissions, reject missing/disabled accounts, and disable the adapter without Vibe64\u2019s per-run\
- enable flag and secret. Do not create users, change roles, reset passwords or weaken production auth for import. Verify\
- the selected account\u2019s actual Preview access; a saved selector is insufficient. If account choices are deferred/decline\
-d, explain access remains unconfigured and continue independent setup work without repeated credential requests. Public/\
-non-web apps need no adapter.","Use `vibe64-helper preview status`, `screenshot`, `logs`, and `browser eval` (Playwright\
- code on stdin) for rendered inspection.","The top Preview toolbar Stop and `vibe64-helper preview stop` stop this sessi\
-on's application and managed browser, not chat or source. Status reports the saved stopped choice. A status read, screen\
-shot, browser inspection, source edit or session reopening is not permission to restart it; use `vibe64-helper preview e\
-nsure --wait` only for a deliberate Start. Scoped browser tests restore the prior stopped choice.","For interactive navi\
-gation, use the proxy URL from `vibe64-helper preview inspect-url` or status `currentPage.url` / `endpoints.browser.url`\
-. Inside browser eval, use `await page.goto(new URL('/your-path', preview.url).href)`. The direct application endpoint u\
-nder diagnostics bypasses Preview identity and is not a browser-navigation URL.","Use the managed preview browser for in\
-teractive browsing and `vibe64-helper playwright` only for an existing configured project suite; report a platform or pr\
-oject-test blocker rather than installing another browser or changing its dependencies.","For browser evidence, batch re\
-lated actions and assertions, return only needed values and inspect relevant locators or regions; screenshot at meaningf\
-ul visual checkpoints or failures, not after every click. Reuse the managed browser when test isolation permits. Preserv\
-e required viewport, identity and security checks; use existing automated cases for repeat verification.","For browser t\
-ests that write or reset data, inspect `vibe64-helper preview targets --json` and the project's `genesis/stack.md` Outpu\
-ts. Run `vibe64-helper playwright --target <declared-test-target> test <suite arguments>` or `vibe64-helper playwright -\
--target <declared-test-target> npm-run <script>`. Vibe64 starts that web target, waits for readiness, uses its declared \
-application identity, and restores the previous Preview when the command finishes or is cancelled; report restoration fa\
-ilures.","A target name is not proof of test isolation. Before running a destructive suite, the application must verify \
-the server's actual test database and suppress real email, invoices, payments, and other external effects. Keep managed \
-Env unchanged. The test launcher and its preview-identity command must use the same database. Follow the application's d\
-eclared test resources and never invent a database name. Never spoof safety checks by changing only the test runner's en\
-vironment.","If no suitable test target exists, add one through the project's existing Outputs contract and application-\
-owned test scripts within authorized scope, keeping normal Preview as default. Validate the exact disposable database be\
-fore resetting it, prepare fixtures before reporting readiness, and make Playwright use the started target's URL, which \
-Vibe64 supplies as PLAYWRIGHT_BASE_URL, without starting another server. If the required test resources or external-effe\
-ct controls are missing, report that specific blocker. Use `vibe64-helper preview ensure --target <id> --wait --json` on\
-ly to deliberately select an interactive target; it stays selected until changed. If browser startup is slow, measure mi\
-grations, fixtures and server startup before retrying or extending deadlines.","Keep test output small: run relevant fil\
-es/cases, save stdout/stderr to local artifacts and preserve exit status. Report counts, duration, failed cases, actiona\
-ble errors and artifact paths. Read only needed failure excerpts, not full passing/JSON/TAP/request/trace/image output. \
-Retain startup, resource and Preview-restoration errors even if tests pass, and trailing wrapper diagnostics separately \
-from JSON. Do not rerun for output or reread unchanged logs; inspect on new output, changed state or a concrete blocker.",
-"Batch related browser tests in one managed suite (one Preview switch and restore). Suites and live Preview actions are \
-sequential: no browser actions, ensure/restart or target changes during a suite or restoration. Wait on the original exe\
-cution, including background runs, through cleanup/restoration (empty polls: yield_time_ms: 30000 where supported; short\
-er only for interactive input or an immediate check); read-only status/logs stay available. Before live inspection, conf\
-irm `vibe64-helper playwright status` has no active run and `vibe64-helper preview status` is ready on the restored targ\
-et. To stop, read suite status then run `vibe64-helper playwright cancel <run-id>`, which waits for cleanup/restoration;\
- retry it if cleanup needs attention. Never kill individual test/Preview PIDs or change locks. Launcher exit alone does \
-not prove tests stopped. Recheck current status before reporting a busy blocker.","If a managed command reports kernel t\
-ask denials or a resource incident, retain its diagnostic and incident ID when reporting the blocker. Ask the platform o\
-perator to inspect that resource evidence before retrying; do not increase test timeouts or weaken assertions to work ar\
-ound a process/thread limit. A generic browser timeout without resource evidence does not establish a platform cause."]),
-C_=Object.freeze(["Each managed shell command receives current development Env from Vibe64, including declared resource \
-bindings; use them in ordinary commands. Do not build environment injection or copy managed credentials into source. Res\
-ource provisioning and application migrations remain separate preparation steps.","Use `vibe64-helper env status [develo\
-pment|production|all]` to inspect configured key names without revealing values.","Pipe an available value to `vibe64-he\
-lper env set <development|production> <KEY> [--secret]`; never put values in arguments, logs, or repository files. Use e\
-mpty stdin only when the user requested an empty value.","When the person refers to a saved key, account or accounts hub\
-, run `vibe64-helper env saved` (names, descriptions and fields, never values) and link the matching field to the variab\
-le the application reads with `vibe64-helper env link <development|production> <KEY> <saved-id> <field-id>` instead of a\
-sking for the value.","Keep development and production values separate. Never invent credentials, copy a value between s\
-copes without explicit direction, or edit Vibe64 runtime/session storage.","After an Env mutation, report only the affec\
-ted scope and key names, never their values, and claim success only when the command succeeded.","Store a secret the app\
-lication needs generated (such as an application key) by generating it with the framework's own generator and piping it \
-to `vibe64-helper env set <scope> <KEY> --secret`. Never write it into a generated `.env` file: Vibe64 regenerates that \
-file from Env."]);function Zr(t=""){return String(t??"").trim()}function en(t,e){if(!t||typeof t!="object"||Array.isArray(
-t))throw new TypeError(`${e} must be an object.`);return t}function rt(t,e,r){let n=new Set(e),o=Object.keys(t).filter(s=>!n.
-has(s));if(o.length>0)throw new TypeError(`${r} contains unsupported fields: ${o.join(", ")}.`)}function qu(t){if(rt(t,[
-"conversationKind","scope","session","hostGuidance"],"Vibe64 session context"),t.hostGuidance!==void 0&&(typeof t.hostGuidance!=
-"string"||Buffer.byteLength(t.hostGuidance,"utf8")>1024))throw new TypeError("Vibe64 host guidance must be bounded text \
-supplied by the host.");if(!$u.includes(t.conversationKind))throw new TypeError("Vibe64 session context has an unknown c\
-onversationKind.");let e=en(t.session,"Vibe64 session capabilities");rt(e,Gs,"Vibe64 session capabilities");let r=Object.
-fromEntries(Gs.map(n=>{if(typeof e[n]!="boolean")throw new TypeError(`Vibe64 session capability ${n} must be boolean.`);
-return[n,e[n]]}));return{conversationKind:t.conversationKind,scope:"session",...t.hostGuidance?{hostGuidance:t.hostGuidance}:
-{},session:r}}function Bu(t){rt(t,["scope","stableContext"],"Vibe64 ephemeral context");let e=String(t.stableContext||"").
-trim();if(!e||e.length>Uu)throw new TypeError("Vibe64 ephemeral context requires bounded stableContext.");return{scope:"\
-ephemeral",stableContext:e}}function Hu(t){if(t.scope==="session")return qu(t);if(t.scope==="ephemeral")return Bu(t);throw new TypeError(
-"The Vibe64 driver supports session and ephemeral scopes only.")}async function Ws(t={},{readRegistry:e=Fu,workdir:r=""}={}){let n=en(t,"Vibe64 host resolver request");if(rt(n,["data","\
+words. If unconfigured, ask which existing accounts (email/login/user ID) represent admin, other required roles and the \
+default; reuse prior answers and wait for their choices before configuring access. Never infer admin rights from names o\
+r the Vibe64 viewer.","A web app with login accounts has an application-owned adapter in the Outputs `#### Preview ident\
+ity` block (`vibe64-helper spec outputs`, `vibe64-helper spec preview-identity-command`); when it is missing, set it up \
+from the app framework's own pattern as part of the work instead of merely offering it. Save selectors the person gives \
+or confirms (you may propose existing app accounts) with `vibe64-helper preview identities save` (`vibe64-helper spec pr\
+eview-identities`), then verify each with `vibe64-helper preview browser identity <name>`; a saved selector alone proves\
+ no access. Use existing sessions/permissions, reject missing/disabled accounts, and disable the adapter without Vibe64\u2019\
+s per-run enable flag and secret. Do not create users, change roles, reset passwords or weaken production auth for impor\
+t. If choices are deferred/declined, say access stays unconfigured and continue independent setup work without repeated \
+credential requests. Public/non-web apps need no adapter.","Use `vibe64-helper preview status`, `screenshot`, `logs`, an\
+d `browser eval` (Playwright code on stdin) for rendered inspection.","The top Preview toolbar Stop and `vibe64-helper p\
+review stop` stop this session's application and managed browser, not chat or source. Status reports the saved stopped c\
+hoice. A status read, screenshot, browser inspection, source edit or session reopening is not permission to restart it; \
+use `vibe64-helper preview ensure --wait` only for a deliberate Start. Scoped browser tests restore the prior stopped ch\
+oice.","For interactive navigation, use the proxy URL from `vibe64-helper preview inspect-url` or status `currentPage.ur\
+l` / `endpoints.browser.url`. Inside browser eval, use `await page.goto(new URL('/your-path', preview.url).href)`. The d\
+irect application endpoint under diagnostics bypasses Preview identity and is not a browser-navigation URL.","Use the ma\
+naged preview browser for interactive browsing and `vibe64-helper playwright` only for an existing configured project su\
+ite; report a platform or project-test blocker rather than installing another browser or changing its dependencies.","Fo\
+r browser evidence, batch related actions and assertions, return only needed values and inspect relevant locators or reg\
+ions; screenshot at meaningful checkpoints or failures, not after every click. Reuse the managed browser when isolation \
+permits, keep required viewport, identity and security checks, and use existing automated cases for repeat verification.",
+"For browser tests that write or reset data, inspect `vibe64-helper preview targets --json` and the project's `genesis/s\
+tack.md` Outputs. Run `vibe64-helper playwright --target <declared-test-target> test <suite arguments>` (or `npm-run <sc\
+ript>` in place of `test`). Vibe64 starts that web target, waits for readiness, uses its declared application identity, \
+and restores the previous Preview when the command finishes or is cancelled; report restoration failures.","A target nam\
+e is not proof of test isolation. Before running a destructive suite, the application must verify the server's actual te\
+st database and suppress real email, invoices, payments, and other external effects. Keep managed Env unchanged. The tes\
+t launcher and its preview-identity command must use the same database. Follow the application's declared test resources\
+ and never invent a database name. Never spoof safety checks by changing only the test runner's environment.","If no sui\
+table test target exists, add one through the project's existing Outputs contract and application-owned test scripts wit\
+hin authorized scope; normal Preview stays the default. Validate the exact disposable database before resetting it, prep\
+are fixtures before reporting readiness, and make Playwright use PLAYWRIGHT_BASE_URL (the started target's URL) without \
+starting another server. If test resources or external-effect controls are missing, report that blocker. `vibe64-helper \
+preview ensure --target <id> --wait --json` deliberately selects an interactive target until changed. If browser startup\
+ is slow, measure migrations, fixtures and server startup before retrying or extending deadlines.","Keep test output sma\
+ll: run relevant files/cases, save stdout/stderr to local artifacts and keep exit status. Report counts, duration, faile\
+d cases, actionable errors and artifact paths, reading only needed failure excerpts. Retain startup, resource and Previe\
+w-restoration errors even if tests pass, and trailing wrapper diagnostics separately from JSON. Do not rerun for output \
+or reread unchanged logs.","Batch related browser tests in one managed suite (one Preview switch and restore). Suites an\
+d live Preview actions are sequential: no browser actions, ensure/restart or target changes during a suite or restoratio\
+n. Wait on the original execution, including background runs, through cleanup/restoration (empty polls: yield_time_ms: 3\
+0000 where supported; shorter only for interactive input); read-only status/logs stay available. Before live inspection,\
+ confirm `vibe64-helper playwright status` shows no active run and `vibe64-helper preview status` is ready on the restor\
+ed target. To stop, run `vibe64-helper playwright cancel <run-id>`, which waits for cleanup/restoration; retry if cleanu\
+p needs attention. Never kill test/Preview PIDs or change locks; launcher exit alone does not prove tests stopped. Reche\
+ck status before reporting a busy blocker.","If a managed command reports kernel task denials or a resource incident, re\
+port the blocker with its diagnostic and incident ID and ask the platform operator to inspect that evidence before retry\
+ing; never raise test timeouts or weaken assertions to work around a process/thread limit. A generic browser timeout wit\
+hout resource evidence does not establish a platform cause."]),C_=Object.freeze(["Each managed shell command receives cu\
+rrent development Env from Vibe64, including declared resource bindings; use them in ordinary commands. Do not build env\
+ironment injection or copy managed credentials into source. Resource provisioning and application migrations remain sepa\
+rate preparation steps.","Use `vibe64-helper env status [development|production|all]` to inspect configured key names wi\
+thout revealing values.","Pipe an available value to `vibe64-helper env set <development|production> <KEY> [--secret]`; \
+never put values in arguments, logs, or repository files. Use empty stdin only when the user requested an empty value.",
+"When the person refers to a saved key, account or accounts hub, run `vibe64-helper env saved` (names, descriptions and \
+fields, never values) and link the matching field to the variable the application reads with `vibe64-helper env link <de\
+velopment|production> <KEY> <saved-id> <field-id>` instead of asking for the value.","Keep development and production va\
+lues separate. Never invent credentials, copy a value between scopes without explicit direction, or edit Vibe64 runtime/\
+session storage.","After an Env mutation, report only the affected scope and key names, never their values, and claim su\
+ccess only when the command succeeded.","Store a secret the application needs generated (such as an application key) by \
+generating it with the framework's own generator and piping it to `vibe64-helper env set <scope> <KEY> --secret`. Never \
+write it into a generated `.env` file: Vibe64 regenerates that file from Env."]);function Zr(t=""){return String(t??"").
+trim()}function en(t,e){if(!t||typeof t!="object"||Array.isArray(t))throw new TypeError(`${e} must be an object.`);return t}
+function rt(t,e,r){let n=new Set(e),o=Object.keys(t).filter(s=>!n.has(s));if(o.length>0)throw new TypeError(`${r} contai\
+ns unsupported fields: ${o.join(", ")}.`)}function qu(t){if(rt(t,["conversationKind","scope","session","hostGuidance"],"\
+Vibe64 session context"),t.hostGuidance!==void 0&&(typeof t.hostGuidance!="string"||Buffer.byteLength(t.hostGuidance,"ut\
+f8")>1024))throw new TypeError("Vibe64 host guidance must be bounded text supplied by the host.");if(!$u.includes(t.conversationKind))
+throw new TypeError("Vibe64 session context has an unknown conversationKind.");let e=en(t.session,"Vibe64 session capabi\
+lities");rt(e,Gs,"Vibe64 session capabilities");let r=Object.fromEntries(Gs.map(n=>{if(typeof e[n]!="boolean")throw new TypeError(
+`Vibe64 session capability ${n} must be boolean.`);return[n,e[n]]}));return{conversationKind:t.conversationKind,scope:"s\
+ession",...t.hostGuidance?{hostGuidance:t.hostGuidance}:{},session:r}}function Bu(t){rt(t,["scope","stableContext"],"Vib\
+e64 ephemeral context");let e=String(t.stableContext||"").trim();if(!e||e.length>Uu)throw new TypeError("Vibe64 ephemera\
+l context requires bounded stableContext.");return{scope:"ephemeral",stableContext:e}}function Hu(t){if(t.scope==="sessi\
+on")return qu(t);if(t.scope==="ephemeral")return Bu(t);throw new TypeError("The Vibe64 driver supports session and ephem\
+eral scopes only.")}async function Ws(t={},{readRegistry:e=Fu,workdir:r=""}={}){let n=en(t,"Vibe64 host resolver request");if(rt(n,["data","\
 providerSessionId","parentSessionIds","scope"],"Vibe64 host resolver request"),!["session","turn"].includes(n.scope))throw new TypeError(
 "The Vibe64 host resolver scope must be session or turn.");if(n.scope==="turn")return null;let o=en(n.data,"Vibe64 host \
 resolver data");rt(o,["registryPath"],"Vibe64 host resolver data");let s=Zr(o.registryPath);if(!Qr.isAbsolute(s))throw new TypeError(