vibe64 0.1.32 → 0.1.34

package/node_modules/@local/vibe64-genesis/src/server/promptContext.js

@@ -1,150 +1,169 @@
 import { createRequire as __vibe64CreateRequire } from 'node:module';const require=__vibe64CreateRequire(import.meta.url);
-import{readFile as y}from"node:fs/promises";import p from"node:path";var x=Object.freeze(["main","temporary"]),m=Object.
-freeze(["managedDatabaseRefresh","managedEnvironment","managedGit","managedPreview"]),k=64*1024,E=Object.freeze(["When u\
+import{readFile as y}from"node:fs/promises";import p from"node:path";var k=Object.freeze(["main","temporary"]),m=Object.
+freeze(["managedDatabaseRefresh","managedEnvironment","managedGit","managedPreview"]),E=64*1024,x=Object.freeze(["When u\
 ser input is necessary, ask no more than three concise, high-impact questions at once.","Put multiple questions on separ\
-ate lines as `[1] Question`, `[2] Question`, and so on.","For a small fixed set of useful choices, finish with `Possible\
- answers:` and a short bullet list; the user may always type a different answer."]),T=Object.freeze(["The Vibe64-managed\
- preview is the canonical application server; do not start a duplicate server on another port.","Use `vibe64-helper prev\
-iew status`, `screenshot`, `logs`, and `browser eval` for rendered inspection. Pass Playwright code to `vibe64-helper pr\
-eview browser eval` on stdin.","For interactive navigation, use the proxy URL from `vibe64-helper preview inspect-url` o\
-r status `currentPage.url` / `endpoints.browser.url`. Inside browser eval, use `await page.goto(new URL('/your-path', pr\
-eview.url).href)`. The direct application endpoint under diagnostics bypasses Preview identity and is not a browser-navi\
-gation URL.","Use the managed preview browser for interactive browsing. Use `vibe64-helper playwright` only for an exist\
-ing configured project suite, and report a platform or project-test blocker rather than installing another browser or ch\
-anging its dependencies.","For browser evidence, batch related actions and assertions and return only the needed values.\
- Inspect relevant locators or page regions; use screenshots at meaningful visual checkpoints or failures instead of afte\
-r every click. Reuse the managed browser when test isolation permits. Preserve required viewport, identity and security \
-checks; use existing automated cases for repeat verification.","For browser tests that write or reset data, inspect `vib\
-e64-helper preview targets --json` and the project's `genesis/stack.md` Outputs. Run `vibe64-helper playwright --target \
-<declared-test-target> test <suite arguments>` or `vibe64-helper playwright --target <declared-test-target> npm-run <scr\
-ipt>`. Vibe64 starts that web target, waits for readiness, uses its declared application identity, and restores the prev\
-ious Preview when the command finishes or is cancelled; report restoration failures.","A target name is not proof of tes\
-t isolation. Before running a destructive suite, the application must verify the server's actual test database and suppr\
-ess real email, invoices, payments, and other external effects. Keep managed Env unchanged. The test launcher and its pr\
-eview-identity command must use the same database. When the project declares BROWSER_TEST_DB_NAME, use it for reusable b\
-rowser fixtures, separate from disposable TEST_DB_NAME. Never spoof safety checks by changing DB_NAME only in the test r\
-unner.","If no suitable test target exists, add one through the project's existing Outputs contract and application-owne\
-d test scripts within the user's authorized scope. Keep normal Preview as the default. Validate the exact disposable dat\
-abase before resetting it, prepare fixtures before reporting readiness, and make Playwright use PLAYWRIGHT_BASE_URL with\
-out starting another server. If the required test resources or external-effect controls are missing, report that specifi\
-c blocker. Use `vibe64-helper preview ensure --target <id> --wait --json` only for deliberate interactive target selecti\
-on; it leaves that target selected until changed.","Keep routine browser startup incremental: reuse the isolated test sc\
-hema, apply only pending migrations, and reset fixture data deterministically. Do not drop and rebuild the database or r\
-un a production frontend build for every focused browser check. Keep fresh-schema migration checks separate, and batch r\
-elated cases into one suite invocation. If startup is slow, measure migrations, fixtures, and server startup before retr\
-ying or extending deadlines.","Keep test output small: select the relevant file and cases, capture stdout and stderr to \
-local artifacts, and preserve the command's exit status. Return counts, duration, failed case names, a short actionable \
-error, and artifact paths. Read only relevant failure excerpts; do not dump passing assertions, full JSON/TAP reports, r\
-equest logs, traces, or screenshots into context. Keep startup, resource and Preview-restoration errors even when tests \
-pass. If the wrapper appends diagnostics after JSON, parse the JSON object and retain the trailing diagnostics separatel\
-y. Wait on the existing run; do not rerun to recover output or repeatedly print unchanged logs. When a command returns a\
-n execution/session identifier, use its existing wait operation with about a 30-second wait window where supported: for \
-an empty command poll, set yield_time_ms: 30000. Reserve shorter waits for interactive input or a specific immediate che\
-ck. Do not alternate brief waits with commands that reread empty or unchanged logs; inspect status or failure excerpts w\
-hen there is new output, a changed state, or a specific blocker to diagnose.","Run related browser tests in one managed \
-suite command: Preview switches once for the entire batch and restores once afterward, not between tests or workers. Man\
-aged suites and live Preview browser actions are sequential: do not run `vibe64-helper preview browser` actions, Preview\
- ensure/restart, or target changes while a suite is active or restoring. Wait on the original command, including cleanup\
- and restoration; if it runs in the background, wait on that same execution before starting a live browser check. Read-o\
-nly status and logs remain available during the suite. After completion, confirm `vibe64-helper playwright status` has n\
-o active run and `vibe64-helper preview status` reports the restored Preview ready before live inspection. To stop a sui\
-te, read `vibe64-helper playwright status`, then run `vibe64-helper playwright cancel <run-id>`. Cancellation waits for \
-managed process cleanup and Preview restoration. Retry that same cancellation if cleanup needs attention. Do not kill in\
-dividual test or Preview PIDs or change internal locks. Launcher exit alone does not prove the managed test stopped. Rec\
-heck live status before reporting a blocker; do not repeat an earlier busy response as current evidence.","If a managed \
-command reports kernel task denials or a resource incident, retain its diagnostic and incident ID when reporting the blo\
-cker. Ask the platform operator to inspect that resource evidence before retrying; do not increase test timeouts or weak\
-en assertions to work around a process/thread limit. A generic browser timeout without resource evidence does not establ\
-ish a platform cause.","Describe only rendered browser evidence; if managed preview is unavailable, report that blocker \
-instead of starting a replacement."]),I=Object.freeze(["Each managed shell command receives current development Env from\
- Vibe64, including existing declared resource bindings. Use those variables in ordinary application commands; do not bui\
-ld environment injection or copy managed credentials into source. Resource provisioning and application migrations remai\
-n separate preparation steps.","Use `vibe64-helper env status [development|production|all]` to inspect configured key na\
-mes without revealing values.","Pipe an available value to `vibe64-helper env set <development|production> <KEY> [--secr\
-et]`; never put values in arguments, logs, or repository files. Use empty stdin only when the user requested an empty va\
-lue.","Keep development and production values separate. Never invent credentials, copy a value between scopes without ex\
-plicit direction, or edit Vibe64 runtime/session storage.","After an Env mutation, report only the affected scope and ke\
-y names, never their values, and claim success only when the command succeeded.","When declared, TEST_DB_NAME is the exa\
-ct disposable integration database and BROWSER_TEST_DB_NAME is a separate reusable browser-fixture database whose migrat\
-ion ledger survives routine runs. Follow the application\u2019s declared test resources; never reset DB_NAME, share these tes\
-t identities, or invent a database name."]);function u(e=""){return String(e??"").trim()}function l(e,t){if(!e||typeof e!=
-"object"||Array.isArray(e))throw new TypeError(`${t} must be an object.`);return e}function i(e,t,s){let r=new Set(t),a=Object.
-keys(e).filter(c=>!r.has(c));if(a.length>0)throw new TypeError(`${s} contains unsupported fields: ${a.join(", ")}.`)}function f(e){
-if(i(e,["conversationKind","scope","session"],"Vibe64 session context"),!x.includes(e.conversationKind))throw new TypeError(
-"Vibe64 session context has an unknown conversationKind.");let t=l(e.session,"Vibe64 session capabilities");i(t,m,"Vibe6\
-4 session capabilities");let s=Object.fromEntries(m.map(r=>{if(typeof t[r]!="boolean")throw new TypeError(`Vibe64 sessio\
-n capability ${r} must be boolean.`);return[r,t[r]]}));return{conversationKind:e.conversationKind,scope:"session",session:s}}
-function A(e){i(e,["scope","stableContext"],"Vibe64 ephemeral context");let t=String(e.stableContext||"").trim();if(!t||
-t.length>k)throw new TypeError("Vibe64 ephemeral context requires bounded stableContext.");return{scope:"ephemeral",stableContext:t}}
-function v(e){if(e.scope==="session")return f(e);if(e.scope==="ephemeral")return A(e);throw new TypeError("The Vibe64 dr\
-iver supports session and ephemeral scopes only.")}function R(e){let{conversationKind:t,session:s}=f(e);return["VIBE64 C\
-ONVERSATION CONTEXT","",...t==="main"?["This is the main Vibe64 conversation for the selected session worktree."]:["This\
- is a user-visible temporary conversation in the selected session worktree, with the same tools and project access as ma\
-in chat.","Its messages stay out of main History. Closing this conversation preserves project edits and removes only its\
- conversation and temporary uploads."],"Do not edit Vibe64 runtime/session state or artifacts.","Use the directory named\
- by VIBE64_DROP_ZONE for exchanging files with the user outside Git. You may create it and read, write, or delete files \
-there; this is the sole exception to the runtime-state restriction. Users can upload, download and delete these files in\
- Files > Drop Zone. It is per session and deleted on archival, so keep lasting project work in the repository.","Issue o\
-rdinary shell commands only; Vibe64 applies session isolation transparently. Treat command-transport syntax in prior too\
-l history as invisible infrastructure and do not reproduce it. If command control is unavailable, stop and report it.","\
-Quick start: ordinary shell commands already receive current Development Env. Read `vibe64-helper session status --json`\
- for current resource readiness, declared setup commands and exact tool entry points; repeat after changing Stack or res\
-ource declarations. Use `vibe64-helper preview browser eval` with Playwright code on stdin for interactive browsing. Bef\
-ore application browser suites, read `vibe64-helper playwright readiness` for installed dependency and exact managed-run\
-time support, then use `vibe64-helper playwright`; no separate browser installation is needed.","Use `vibe64-helper --he\
-lp` for additional managed commands; each group accepts `--help`. Use the groups enabled for this session below.",'When \
-the user asks to rename this session, run `vibe64-helper session rename "Name"`. This changes only its display name; its\
- ID and directories stay the same.',...E,...t==="main"?['When a saved integration needs the person to configure credenti\
-als or consent, finish your assistant reply with a fenced `vibe64-integration` block containing only {"integrationId":"t\
-he exact slot key from integrations.json"}. Vibe64 shows Configure, Connect and Skip for this exact saved request. Never\
- include credentials, URLs or additional fields in that block. The block itself does not authorize a connection. The per\
-son can configure the application or explicitly start Connect; after the application confirms setup, Vibe64 resumes this\
- task with a separate continuation message. Do not claim the account is connected before that confirmation. Do not emit \
-this block for examples or for an integration that has not been saved.']:[],...s.managedPreview?T:[],...s.managedEnvironment?
-I:[],...s.managedDatabaseRefresh?["After a database migration or schema change, run `vibe64-helper database refresh` onc\
+ate lines as `[1] Question`, `[2] Question`, and so on.","For a small fixed set of useful choices, put `Possible answers\
+:` and a short bullet list directly beneath its own question, before the next one; never collect several questions' answ\
+ers into one trailing list.","Each bullet is one distinct, complete answer: Yes and No are separate bullets; never join \
+alternatives with a slash or `or`. Omit the list for free-text answers. The user may always type a different answer.",`E\
+xample:
+[1] Which density?
+Possible answers:
+- Compact
+- Comfortable
+[2] Tell the main agent before changes?
+Possible answers:
+- Yes, tell main first
+- No, proceed independently`]),I=Object.freeze(["The Vibe64-managed preview is the canonical application server; never s\
+tart a duplicate or replacement server. If it is unavailable, report that blocker. Describe only rendered browser eviden\
+ce.","When adopting an authenticated app, or when its login blocks Preview inspection, inspect identity support/names wi\
+th `vibe64-helper preview status`; prefer `vibe64-helper preview browser identity <configured-name>` to requesting passw\
+ords. If unconfigured, ask which existing accounts (email/login/user ID) represent admin and other required roles, and t\
+he default. Reuse prior answers; wait for their choices before configuring access. Never infer admin rights from names o\
+r the Vibe64 viewer.","Offer the application-owned `vibe64.preview-identity.command.v1` adapter in Outputs Preview ident\
+ity, and guide named selectors through Dashboard > App access > Managed app access. Use existing sessions/permissions, r\
+eject 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 deferred/declined, explain access remains unconfigured and continue indepen\
+dent 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 session's application and managed browser, not chat or source. S\
+tatus reports the saved stopped choice. 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 t\
+ests restore the prior stopped choice.","For interactive navigation, use the proxy URL from `vibe64-helper preview inspe\
+ct-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 under diagnostics bypasses Preview identity and is not a bro\
+wser-navigation URL.","Use the managed preview browser for interactive browsing and `vibe64-helper playwright` only for \
+an existing configured project suite; report a platform or project-test blocker rather than installing another browser o\
+r changing its dependencies.","For browser evidence, batch related actions and assertions, return only needed values and\
+ inspect relevant locators or regions; screenshot at meaningful visual checkpoints or failures, not after every click. R\
+euse the managed browser when test isolation permits. Preserve required viewport, identity and security checks; use exis\
+ting automated cases for repeat verification.","For browser tests that write or reset data, inspect `vibe64-helper previ\
+ew targets --json` and the project's `genesis/stack.md` Outputs. Run `vibe64-helper playwright --target <declared-test-t\
+arget> test <suite arguments>` or `vibe64-helper playwright --target <declared-test-target> npm-run <script>`. Vibe64 st\
+arts that web target, waits for readiness, uses its declared application identity, and restores the previous Preview whe\
+n the command finishes or is cancelled; report restoration failures.","A target name is not proof of test isolation. Bef\
+ore 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 c\
+ommand must use the same database. Use a declared BROWSER_TEST_DB_NAME for reusable browser fixtures, separate from disp\
+osable TEST_DB_NAME. Never spoof safety checks by changing DB_NAME only in the test runner.","If no suitable test target\
+ exists, add one through the project's existing Outputs contract and application-owned test scripts within authorized sc\
+ope, keeping normal Preview as default. Validate the exact disposable database before resetting it, prepare fixtures bef\
+ore reporting readiness, and make Playwright use PLAYWRIGHT_BASE_URL without starting another server. If the required te\
+st resources or external-effect controls are missing, report that specific blocker. Use `vibe64-helper preview ensure --\
+target <id> --wait --json` only to deliberately select an interactive target; it stays selected until changed.","Keep ro\
+utine browser startup incremental: reuse the isolated test schema, apply only pending migrations, and reset fixture data\
+ deterministically. Do not drop and rebuild the database or run a production frontend build for every focused browser ch\
+eck. Keep fresh-schema migration checks separate. If startup is slow, measure migrations, fixtures, and server startup b\
+efore retrying or extending deadlines.","Keep test output small: run relevant files/cases, save stdout/stderr to local a\
+rtifacts and preserve exit status. Report counts, duration, failed cases, actionable errors and artifact paths. Read onl\
+y needed failure excerpts, not full passing/JSON/TAP/request/trace/image output. Retain startup, resource and Preview-re\
+storation errors even if tests pass, and trailing wrapper diagnostics separately from JSON. Do not rerun for output or r\
+eread unchanged logs; inspect on new output, changed state or a concrete blocker.","Batch related browser tests in one m\
+anaged suite (one Preview switch and restore). Suites and live Preview actions are sequential: no browser actions, ensur\
+e/restart or target changes during a suite or restoration. Wait on the original execution, including background runs, th\
+rough cleanup/restoration (empty polls: yield_time_ms: 30000 where supported; shorter only for interactive input or an i\
+mmediate check); read-only status/logs stay available. Before live inspection, confirm `vibe64-helper playwright status`\
+ has no active run and `vibe64-helper preview status` is ready on the restored target. To stop, read suite status then r\
+un `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 curr\
+ent status before reporting a busy blocker.","If a managed command reports kernel task denials or a resource incident, r\
+etain its diagnostic and incident ID when reporting the blocker. Ask the platform operator to inspect that resource evid\
+ence before retrying; do not increase test timeouts or weaken assertions to work around a process/thread limit. A generi\
+c browser timeout without resource evidence does not establish a platform cause."]),T=Object.freeze(["Each managed shell\
+ command receives current development Env from Vibe64, including declared resource bindings; use them in ordinary comman\
+ds. Do not build environment injection or copy managed credentials into source. Resource provisioning and application mi\
+grations remain separate preparation steps.","Use `vibe64-helper env status [development|production|all]` to inspect con\
+figured key names without 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 request\
+ed an empty value.","Keep development and production values separate. Never invent credentials, copy a value between sco\
+pes without explicit direction, or edit Vibe64 runtime/session storage.","After an Env mutation, report only the affecte\
+d scope and key names, never their values, and claim success only when the command succeeded.","When declared, TEST_DB_N\
+AME is the exact disposable integration database and BROWSER_TEST_DB_NAME is a separate reusable browser-fixture databas\
+e whose migration ledger survives routine runs. Follow the application\u2019s declared test resources; never reset DB_NAME, s\
+hare these test identities, or invent a database name."]);function u(e=""){return String(e??"").trim()}function l(e,s){if(!e||
+typeof e!="object"||Array.isArray(e))throw new TypeError(`${s} must be an object.`);return e}function o(e,s,r){let t=new Set(
+s),i=Object.keys(e).filter(c=>!t.has(c));if(i.length>0)throw new TypeError(`${r} contains unsupported fields: ${i.join("\
+, ")}.`)}function f(e){if(o(e,["conversationKind","scope","session","hostGuidance"],"Vibe64 session context"),e.hostGuidance!==
+void 0&&(typeof e.hostGuidance!="string"||Buffer.byteLength(e.hostGuidance,"utf8")>1024))throw new TypeError("Vibe64 hos\
+t guidance must be bounded text supplied by the host.");if(!k.includes(e.conversationKind))throw new TypeError("Vibe64 s\
+ession context has an unknown conversationKind.");let s=l(e.session,"Vibe64 session capabilities");o(s,m,"Vibe64 session\
+ capabilities");let r=Object.fromEntries(m.map(t=>{if(typeof s[t]!="boolean")throw new TypeError(`Vibe64 session capabil\
+ity ${t} must be boolean.`);return[t,s[t]]}));return{conversationKind:e.conversationKind,scope:"session",...e.hostGuidance?
+{hostGuidance:e.hostGuidance}:{},session:r}}function S(e){o(e,["scope","stableContext"],"Vibe64 ephemeral context");let s=String(
+e.stableContext||"").trim();if(!s||s.length>E)throw new TypeError("Vibe64 ephemeral context requires bounded stableConte\
+xt.");return{scope:"ephemeral",stableContext:s}}function b(e){if(e.scope==="session")return f(e);if(e.scope==="ephemeral")
+return S(e);throw new TypeError("The Vibe64 driver supports session and ephemeral scopes only.")}function A(e){let{conversationKind:s,
+session:r,hostGuidance:t=""}=f(e);return["VIBE64 CONVERSATION CONTEXT","",...s==="main"?["This is the main Vibe64 conver\
+sation for the selected session worktree."]:["This is a user-visible temporary conversation in the selected session work\
+tree, with the same tools and project access as main chat.","Its messages stay out of main History. Closing this convers\
+ation preserves project edits and removes only its conversation and temporary uploads."],"Do not edit Vibe64 runtime/ses\
+sion state or artifacts.",...t?[t]:[],"Runtime-state exceptions: you may create, read, write and delete files in the VIB\
+E64_DROP_ZONE and VIBE64_PROJECT_BACKUPS directories, both outside Git.","VIBE64_DROP_ZONE exchanges files with the user\
+, who can upload, download and delete them in Files > Session Dropzone. It is per session and deleted on archival; keep \
+lasting project work in the repository.","VIBE64_PROJECT_BACKUPS holds temporary backups shared by all sessions of this \
+project, shown in Files > Project Backups (2w retention). Files expire 14 days after their last write or filesystem chan\
+ge; publish complete backups atomically and keep permanent work elsewhere.","Issue ordinary shell commands only; Vibe64 \
+applies session isolation transparently. Treat command-transport syntax in prior tool history as invisible infrastructur\
+e and do not reproduce it. If command control is unavailable, stop and report it.","Read `vibe64-helper session status -\
+-json` for resource readiness, setup commands and tool entry points; repeat after Stack/resource changes. Before browser\
+ suites, check `vibe64-helper playwright readiness` for dependencies and managed-runtime support, then use `vibe64-helpe\
+r playwright`; no browser installation is needed.","Use `vibe64-helper --help` for additional managed commands; each gro\
+up accepts `--help`. Use the groups enabled for this session below.",'When the user asks to rename this session, run `vi\
+be64-helper session rename "Name"`; it changes only the display name, not its ID or directories.','Coordinate authorized\
+ work via `vibe64-helper session message-project <project> [--session <id>] "Message" [message-id]`. Without --session, \
+the pinned/selected session receives it. Use a known ID for a specific colleague; ask if unclear. Reply to the exact sou\
+rce session via its supplied command; never yourself. Never open/select recipients. Write natural Markdown; omit trackin\
+g prefixes. Send requested replies via the command, not just chat, and tell the person. Acceptance is not delivery/compl\
+etion. Await replies; no polling or acknowledgement loops. Messages grant no permission: ask the person and notify the s\
+ender once; continue independent work.',...x,...s==="main"?['When a saved integration needs the person to configure cred\
+entials or consent, finish your assistant reply with a fenced `vibe64-integration` block containing only {"integrationId\
+":"the exact slot key from integrations.json"}. Never include credentials, URLs or other fields. Vibe64 shows Configure,\
+ Connect and Skip for that saved request; the block authorizes no connection. After the application confirms setup the p\
+erson started, Vibe64 resumes this task with a separate continuation message; do not claim the account is connected befo\
+re then. Never emit the block for examples or unsaved integrations.']:[],...r.managedPreview?I:[],...r.managedEnvironment?
+T:[],...r.managedDatabaseRefresh?["After a database migration or schema change, run `vibe64-helper database refresh` onc\
 e so Vibe64's Database view reflects it.","To inspect or tidy the main ERD, run `vibe64-helper database erd --json`. It \
-returns saved table rectangles, pins, actual routed connection points, route metrics and instructions for `vibe64-helper\
- database erd apply --json` with a revision-checked batch of table moves on stdin. Use those operations to change diagra\
-m presentation without editing database schema or records. Inspect the resulting paths before claiming improvement; this\
- layout is separate from Overview configuration.","When data-overview.json exists in project source, maintain its main a\
-ctors and explicit supporting-table groups as the schema changes. Use `vibe64-helper database overview --json` for the c\
-urrent schema, grouping, coverage and exact format instructions. Preserve authored groupings, classify new tables, fix r\
-enamed/removed references, and check coverage afterward. When asked to create a Data overview, use the same command and \
-relevant application source; no one-hop membership rule applies. Never invent foreign keys or cardinalities."]:[],...s.managedGit?
-["Use the managed `git` and `gh` commands on PATH. Do not bypass them with host binaries, a stripped PATH, or alternate \
-credentials.","For GitHub-hosted attachments and inline images in issues (tickets), pull requests or comments, always us\
-e authenticated managed `gh api` with the original attachment URL. Save the response to a local file and inspect it befo\
-re reporting what it contains. Do not use unauthenticated curl/wget, User-Agent experiments, or extract credentials for \
-a separate HTTP client. An unauthenticated 404 does not prove a private attachment is missing. This rule applies to GitH\
-ub-hosted attachments, not arbitrary external links.","After changing GitHub issues, comments, labels or pull requests, \
-run `vibe64-helper github refresh` once so Vibe64's Issues/PR view reflects it.","When linking an issue in this project'\
-s repository, run `vibe64-helper github issue-link <number>` and use its returned Vibe64 path exactly as the primary Mar\
-kdown link destination, including the /app prefix. Ordinary links to Vibe64 pages navigate in-app without reloading, whe\
-ther root-relative or full URLs on the current origin. You may include the GitHub URL as a secondary link. Do not guess \
-the project slug or host; issues in other repositories keep their GitHub links.","Report authentication or transport fai\
-lures directly; do not inspect credentials or invent another login path.","When a managed Git/GitHub command fails, tell\
- the user which requested action failed, which earlier work is confirmed complete, what remains undone or unconfirmed, a\
-nd the next safe action. Retain the reported failure stage, execution budget and execution reference when provided; do n\
-ot expose credentials or dump raw output unnecessarily.","A timeout or transport failure does not establish invalid auth\
-entication, exhausted AI quota, a GitHub outage or a suspension problem. Separate recorded facts from hypotheses; say th\
-e cause is unknown when it is unproven. Recommend reconnection only when the reported error explicitly calls for it.","I\
-f the diagnostic says commandSubmitted=false, the requested Git/GitHub action was not attempted. After an execution time\
-out, lost response or unreadable response, its effects remain unconfirmed: use a read-only check of the affected Git/Git\
-Hub state before repeating any write. Never claim that a comment was posted or not posted, or that a push succeeded or f\
-ailed, solely from those errors. If verification is unavailable, report the outcome as unknown and stop; do not repeat t\
-he write or claim it was safely rolled back."]:[]].join(`
-`)}function N(e={}){let t=l(e,"Vibe64 driver input"),s=v(t);return s.scope==="session"?R(s):s.stableContext}async function D(e={},{
-readRegistry:t=y,workdir:s=""}={}){let r=l(e,"Vibe64 host resolver request");if(i(r,["data","providerSessionId","parentS\
-essionIds","scope"],"Vibe64 host resolver request"),!["session","turn"].includes(r.scope))throw new TypeError("The Vibe6\
-4 host resolver scope must be session or turn.");if(r.scope==="turn")return null;let a=l(r.data,"Vibe64 host resolver da\
-ta");i(a,["registryPath"],"Vibe64 host resolver data");let c=u(a.registryPath);if(!p.isAbsolute(c))throw new TypeError("\
-Vibe64 host resolver data requires an absolute registryPath.");let h=JSON.parse(await t(c,"utf8"));if(!Array.isArray(h?.
-sessions))throw new TypeError("The conversation ownership registry is invalid.");let b=h.sessions,g=u(r.providerSessionId);
-if(r.parentSessionIds!==void 0&&(!Array.isArray(r.parentSessionIds)||r.parentSessionIds.length>32||r.parentSessionIds.some(
-n=>typeof n!="string"||!n.trim())))throw new TypeError("Invalid native conversation ancestry.");let d=[g,...r.parentSessionIds||
-[]].filter(Boolean).map(n=>b.find(w=>u(w?.upstreamSessionId)===n)).find(Boolean),o=d?.promptContext;if(!o)return null;if(s&&
-d.workdir&&p.resolve(s)!==p.resolve(d.workdir))throw new Error("The managed conversation belongs to a different project \
-directory.");if(o.scope==="learning"){if(i(o,["scope","instructions"],"Vibe64 learning context"),d.conversation?.nativeTools!==
-!1)throw new TypeError("Learning instructions require the restricted native conversation binding.");let n=o.instructions;
+returns table rectangles, pins, routed connection points, route metrics and instructions for `vibe64-helper database erd\
+ apply --json`, which takes a revision-checked batch of table moves on stdin and changes only diagram presentation, not \
+schema, records or Overview configuration. Inspect the resulting paths before claiming improvement.","When project sourc\
+e has data-overview.json, maintain its main actors and explicit supporting-table groups as the schema changes. Use `vibe\
+64-helper database overview --json` for the current schema, grouping, coverage and exact format instructions. Preserve a\
+uthored groupings, classify new tables, fix renamed/removed references, and check coverage afterward. When asked to crea\
+te a Data overview, use the same command and relevant application source; no one-hop membership rule applies. Never inve\
+nt foreign keys or cardinalities."]:[],...r.managedGit?["Use the managed `git` and `gh` commands on PATH. Do not bypass \
+them with host binaries, a stripped PATH, or alternate credentials.","For GitHub-hosted attachments and inline images in\
+ issues (tickets), pull requests or comments, always use authenticated managed `gh api` with the original attachment URL\
+. Save the response to a local file and inspect it before reporting what it contains. Do not use unauthenticated curl/wg\
+et, User-Agent experiments, or extract credentials for a separate HTTP client. An unauthenticated 404 does not prove a p\
+rivate attachment is missing.","After changing GitHub issues, comments, labels or pull requests, run `vibe64-helper gith\
+ub refresh` once so Vibe64's Issues/PR view reflects it.","When linking an issue in this project's repository, run `vibe\
+64-helper github issue-link <number>` and use its returned Vibe64 path exactly as the primary Markdown link destination,\
+ including the /app prefix. Root-relative or same-origin Vibe64 links navigate in-app without reloading. You may include\
+ the GitHub URL as a secondary link. Do not guess the project slug or host; issues in other repositories keep their GitH\
+ub links.","Report authentication or transport failures directly; do not inspect credentials or invent another login pat\
+h.","When a managed Git/GitHub command fails, tell the user which requested action failed, which earlier work is confirm\
+ed complete, what remains undone or unconfirmed, and the next safe action. Retain the reported failure stage, execution \
+budget and execution reference when provided; do not expose credentials or dump raw output unnecessarily.","A timeout or\
+ transport failure does not establish invalid authentication, exhausted AI quota, a GitHub outage or a suspension proble\
+m. Separate recorded facts from hypotheses; say the cause is unknown when it is unproven. Recommend reconnection only wh\
+en the reported error explicitly calls for it.","If the diagnostic says commandSubmitted=false, the requested Git/GitHub\
+ action was not attempted. After an execution timeout, lost response or unreadable response, its effects remain unconfir\
+med: use a read-only check of the affected Git/GitHub state before repeating any write. Never claim that a comment was p\
+osted or not posted, or that a push succeeded or failed, solely from those errors. If verification is unavailable, repor\
+t the outcome as unknown and stop; do not repeat the write or claim it was safely rolled back."]:[]].join(`
+`)}function N(e={}){let s=l(e,"Vibe64 driver input"),r=b(s);return r.scope==="session"?A(r):r.stableContext}async function j(e={},{
+readRegistry:s=y,workdir:r=""}={}){let t=l(e,"Vibe64 host resolver request");if(o(t,["data","providerSessionId","parentS\
+essionIds","scope"],"Vibe64 host resolver request"),!["session","turn"].includes(t.scope))throw new TypeError("The Vibe6\
+4 host resolver scope must be session or turn.");if(t.scope==="turn")return null;let i=l(t.data,"Vibe64 host resolver da\
+ta");o(i,["registryPath"],"Vibe64 host resolver data");let c=u(i.registryPath);if(!p.isAbsolute(c))throw new TypeError("\
+Vibe64 host resolver data requires an absolute registryPath.");let h=JSON.parse(await s(c,"utf8"));if(!Array.isArray(h?.
+sessions))throw new TypeError("The conversation ownership registry is invalid.");let g=h.sessions,v=u(t.providerSessionId);
+if(t.parentSessionIds!==void 0&&(!Array.isArray(t.parentSessionIds)||t.parentSessionIds.length>32||t.parentSessionIds.some(
+n=>typeof n!="string"||!n.trim())))throw new TypeError("Invalid native conversation ancestry.");let d=[v,...t.parentSessionIds||
+[]].filter(Boolean).map(n=>g.find(w=>u(w?.upstreamSessionId)===n)).find(Boolean),a=d?.promptContext;if(!a)return null;if(r&&
+d.workdir&&p.resolve(r)!==p.resolve(d.workdir))throw new Error("The managed conversation belongs to a different project \
+directory.");if(a.scope==="learning"){if(o(a,["scope","instructions"],"Vibe64 learning context"),d.conversation?.nativeTools!==
+!1)throw new TypeError("Learning instructions require the restricted native conversation binding.");let n=a.instructions;
 if(typeof n!="string"||!n.trim()||Buffer.byteLength(n)>128*1024)throw new TypeError("Learning native context requires bo\
-unded nonempty teaching instructions.");return{scope:"learning",instructions:n}}return v(o)}export{k as VIBE64_EPHEMERAL_CONTEXT_MAX_CHARACTERS,N as vibe64Driver,D as vibe64DriverInputFromRegistry};
+unded nonempty teaching instructions.");return{scope:"learning",instructions:n}}return b(a)}export{E as VIBE64_EPHEMERAL_CONTEXT_MAX_CHARACTERS,N as vibe64Driver,j as vibe64DriverInputFromRegistry};

package/node_modules/@local/vibe64-runtime/src/server/agentSessionCommandHook.js

@@ -1,10 +1,10 @@
 import { createRequire as __vibe64CreateRequire } from 'node:module';const require=__vibe64CreateRequire(import.meta.url);
-import c from"node:process";var r=2*1024*1024,u="VIBE64_WRAPPER";async function a(){let o=[],t=0;for await(let i of c.stdin){
-if(t+=i.length,t>r)throw new Error("Agent shell hook input is too large.");o.push(i)}let n=JSON.parse(Buffer.concat(o).toString(
-"utf8")||"{}");return n&&typeof n=="object"&&!Array.isArray(n)?n:{}}function p(o=""){let t=`'${o.replaceAll("'",`'"'"'`)}\
-'`;return{hookSpecificOutput:{hookEventName:"PreToolUse",permissionDecision:"allow",updatedInput:{command:`"$${u}" ${t}`}}}}
-function l(o=""){return{hookSpecificOutput:{hookEventName:"PreToolUse",permissionDecision:"deny",permissionDecisionReason:o||
-"Vibe64 could not bind this shell command to its session."}}}var s=await a(),e=s?.tool_input?.command;if(s.hook_event_name===
-"PreToolUse"&&s.tool_name==="Bash"){let o=typeof e=="string"&&e?p(e):l("Vibe64 rejected a shell command without valid co\
-mmand text.");c.stdout.write(`${JSON.stringify(o)}
+import c from"node:process";var r=2*1024*1024,u="VIBE64_WRAPPER";async function a(){let o=[],n=0;for await(let s of c.stdin){
+if(n+=s.length,n>r)throw new Error("Agent shell hook input is too large.");o.push(s)}let t=JSON.parse(Buffer.concat(o).toString(
+"utf8")||"{}");return t&&typeof t=="object"&&!Array.isArray(t)?t:{}}function p(o){let{command:n}=o,t=`'${n.replaceAll("'",
+`'"'"'`)}'`;return{hookSpecificOutput:{hookEventName:"PreToolUse",permissionDecision:"allow",updatedInput:{...o,command:`\
+"$${u}" ${t}`}}}}function m(o=""){return{hookSpecificOutput:{hookEventName:"PreToolUse",permissionDecision:"deny",permissionDecisionReason:o||
+"Vibe64 could not bind this shell command to its session."}}}var e=await a(),i=e?.tool_input?.command;if(e.hook_event_name===
+"PreToolUse"&&e.tool_name==="Bash"){let o=typeof i=="string"&&i?p(e.tool_input):m("Vibe64 rejected a shell command witho\
+ut valid command text.");c.stdout.write(`${JSON.stringify(o)}
 `)}