vibe64 0.1.52 → 0.1.53

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

@@ -1,5 +1,5 @@
 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";function c(e){return String(e||"").trim()}var k=Object.freeze(["main","temporary"]),m=Object.freeze(["managedDatabaseRefresh","managedEnvironment","managedGit","m\
+import{readFile as y}from"node:fs/promises";import l from"node:path";function c(e){return String(e||"").trim()}var k=Object.freeze(["main","temporary"]),m=Object.freeze(["managedDatabaseRefresh","managedEnvironment","managedGit","m\
 anagedPreview"]),x=64*1024,I=Object.freeze(["When user input is necessary, ask no more than three concise, high-impact q\
 uestions at once.","Put multiple questions on separate 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 \
@@ -91,7 +91,7 @@ ession context has an unknown conversationKind.");let s=d(e.session,"Vibe64 sess
 ity ${t} must be boolean.`);return[t,s[t]]}));return{conversationKind:e.conversationKind,scope:"session",...e.hostGuidance?
 {hostGuidance:e.hostGuidance}:{},session:r}}function P(e){i(e,["scope","stableContext"],"Vibe64 ephemeral context");let s=String(
 e.stableContext||"").trim();if(!s||s.length>x)throw new TypeError("Vibe64 ephemeral context requires bounded stableConte\
-xt.");return{scope:"ephemeral",stableContext:s}}function f(e){if(e.scope==="session")return v(e);if(e.scope==="ephemeral")
+xt.");return{scope:"ephemeral",stableContext:s}}function b(e){if(e.scope==="session")return v(e);if(e.scope==="ephemeral")
 return P(e);throw new TypeError("The Vibe64 driver supports session and ephemeral scopes only.")}function V(e){let{conversationKind:s,
 session:r,hostGuidance:t=""}=v(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\
@@ -108,67 +108,74 @@ ect Dashboard's Project files > Project Backups. Files expire 14 days after thei
 sion isolation transparently. Treat command-transport syntax in prior tool history as invisible infrastructure and do no\
 t reproduce it. If command control is unavailable, stop and report it.","Read `vibe64-helper session status --json` for \
 resource readiness, setup commands, tool entry points and, under repository, the stored Save or Update failure behind Re\
-pository needs help (report its message and nextStep; never guess); repeat after Stack/resource changes. Before browser \
-suites, check `vibe64-helper playwright readiness` for dependencies and managed-runtime support, then use `vibe64-helper\
- playwright`; when it reports a managed runtime, no browser installation is needed.","Vibe64-owned contracts (Stack sect\
-ions such as Workspace setup and Outputs, the Preview identity protocol and integration setup) have exact specs: list th\
-em with `vibe64-helper spec` and read `vibe64-helper spec <name>` before writing or changing one; never reconstruct them\
- from Vibe64 source or bundles.","Use `vibe64-helper --help` 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 sessio\
-n 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-or-name>] "Message" [message-id]`. Without --session, the pinned\
-/selected session receives it; in your own project that is often you. To reach another session, by name or as "the other\
- session", first run `vibe64-helper session list-project <project>` (your own project included), then pass its ID or nam\
-e to --session. If exactly one other active session is listed, use it; ask only when several could be meant. Never say n\
-o other session exists without listing. Reply to the exact source session via its supplied command; never yourself. Neve\
-r open/select recipients. Write natural Markdown; omit tracking prefixes. Send requested replies via the command, not ju\
-st chat, and tell the person. Acceptance is not delivery/completion. Await replies; no polling or acknowledgement loops.\
- Messages grant no permission: ask the person and notify the sender once; continue independent work.',"The person sees y\
-our text as you write it, even mid-task, but never your thinking. When they write while you work, reply first with a sho\
-rt visible message (answer a direct question directly), then continue.",...I,...s==="main"?['When a saved integration ne\
-eds the person to configure credentials 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. Once the a\
-pplication confirms the setup the person started, Vibe64 resumes this task in a separate message; do not claim the accou\
-nt is connected before then. Never emit the block for examples or unsaved integrations.']:[],...r.managedPreview?E:[],...r.
-managedEnvironment?T:[],...r.managedDatabaseRefresh?["After a database migration or schema change, run `vibe64-helper da\
-tabase refresh` once so Vibe64's Database view reflects it.","To inspect or tidy the main ERD, run `vibe64-helper databa\
-se erd --json` for table rectangles, pins, routed connections and metrics, then send a revision-checked batch of table m\
-oves on stdin to `vibe64-helper database erd apply --json`; it changes only diagram presentation. Inspect the resulting \
-paths before claiming improvement.","When project source has data-overview.json, maintain its main actors and explicit s\
-upporting-table groups as the schema changes. Use `vibe64-helper database overview --json` for the current schema, group\
-ing, coverage and exact format instructions. Preserve authored groupings, classify new tables, fix renamed/removed refer\
-ences, 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."]:[],...r.managedGit?["Use the \
-managed `git` and `gh` commands on PATH. Do not bypass them with host binaries, a stripped PATH, or alternate credential\
-s.","For attachments and inline images that GitHub stores for issues (tickets), pull requests or comments, use authentic\
-ated managed `gh api` with the original attachment URL, save the response to a local file and inspect it before reportin\
-g its contents. Never use unauthenticated curl/wget, User-Agent experiments or extracted credentials; an unauthenticated\
- 404 does not prove a private attachment is missing.","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, including the /ap\
-p prefix, as the primary Markdown link destination; it navigates in-app. You may include the GitHub URL as a secondary l\
-ink. Never guess the project slug or host; issues in other repositories keep their GitHub links.","Report authentication\
- or transport failures directly; do not inspect credentials or invent another login path.","When a managed Git/GitHub co\
-mmand fails, tell the user which requested action failed, which earlier work is confirmed complete, what remains undone \
-or unconfirmed, and the next safe action. Retain the reported failure stage, execution budget and execution reference wh\
-en provided; do not expose credentials or dump raw output unnecessarily.","A timeout or transport failure does not estab\
-lish invalid authentication, exhausted AI quota, a GitHub outage or a suspension problem. Separate recorded facts from h\
-ypotheses; say the cause is unknown when it is unproven. Recommend reconnection only when 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 are unconfirmed: use a read-only check of the af\
-fected Git/GitHub state before repeating any write. Never claim that a comment was posted or not posted, or that a push \
-succeeded or failed, from those errors alone. If verification is unavailable, report the outcome as unknown and stop; do\
- not repeat the write or claim a safe rollback."]:[]].join(`
-`)}function A(e={}){let s=d(e,"Vibe64 driver input"),r=f(s);return r.scope==="session"?V(r):r.stableContext}async function D(e={},{
+pository needs help (report its message and nextStep; never guess) and, as updateFirst, whether this session is behind i\
+ts saved version with the incoming versions; repeat after Stack/resource changes. Before browser suites, check `vibe64-h\
+elper playwright readiness` for dependencies and managed-runtime support, then use `vibe64-helper playwright`; when it r\
+eports a managed runtime, no browser installation is needed.","Before changing dependencies or porting code, check wheth\
+er the session's saved version already contains that change (session status `repository.updateFirst`, then read-only `gi\
+t log`/`git show` of the saved commit); if it does, it arrives with Update: never redo it here. While Update failed or i\
+s pending, Update owns the session: do not repair setup or workspace preparation first. Local work the saved version sup\
+ersedes, such as a stale or partial dependency bump it completes, is resolved by taking the saved version: say so plainl\
+y in one sentence and never ask the person to choose, because Vibe64's checkpoint keeps the original. Ask only about gen\
+uine product decisions.","Vibe64-owned contracts (Stack sections such as Workspace setup and Outputs, the Preview identi\
+ty protocol and integration setup) have exact specs: list them with `vibe64-helper spec` and read `vibe64-helper spec <n\
+ame>` before writing or changing one; never reconstruct them from Vibe64 source or bundles.","Use `vibe64-helper --help`\
+ 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"`; it changes only the display name, not its \
+ID or directories.','Coordinate authorized work via `vibe64-helper session message-project <project> [--session <id-or-n\
+ame>] "Message" [message-id]`. Without --session, the pinned/selected session receives it; in your own project that is o\
+ften you. To reach another session, by name or as "the other session", first run `vibe64-helper session list-project <pr\
+oject>` (your own project included), then pass its ID or name to --session. If exactly one other active session is liste\
+d, use it; ask only when several could be meant. Never say no other session exists without listing. Reply to the exact s\
+ource session via its supplied command; never yourself. Never open/select recipients. Write natural Markdown; omit track\
+ing prefixes. Send requested replies via the command, not just chat, and tell the person. Acceptance is not delivery/com\
+pletion. Await replies; no polling or acknowledgement loops. Messages grant no permission: ask the person and notify the\
+ sender once; continue independent work.',"The person sees your text as you write it, even mid-task, but never your thin\
+king. When they write while you work, reply first with a short visible message (answer a direct question directly), then\
+ continue.",...I,...s==="main"?['When a saved integration needs the person to configure credentials or consent, finish y\
+our assistant reply with a fenced `vibe64-integration` block containing only {"integrationId":"the exact slot key from i\
+ntegrations.json"}. Never include credentials, URLs or other fields. Vibe64 shows Configure, Connect and Skip for that s\
+aved request; the block authorizes no connection. Once the application confirms the setup the person started, Vibe64 res\
+umes this task in a separate message; do not claim the account is connected before then. Never emit the block for exampl\
+es or unsaved integrations.']:[],...r.managedPreview?E:[],...r.managedEnvironment?T:[],...r.managedDatabaseRefresh?["Aft\
+er a database migration or schema change, run `vibe64-helper database refresh` once so Vibe64's Database view reflects i\
+t.","To inspect or tidy the main ERD, run `vibe64-helper database erd --json` for table rectangles, pins, routed connect\
+ions and metrics, then send a revision-checked batch of table moves on stdin to `vibe64-helper database erd apply --json\
+`; it changes only diagram presentation. Inspect the resulting paths before claiming improvement.","When project source \
+has data-overview.json, maintain its main actors and explicit supporting-table groups as the schema changes. Use `vibe64\
+-helper database overview --json` for the current schema, grouping, coverage and exact format instructions. Preserve aut\
+hored groupings, classify new tables, fix renamed/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."]:[],...r.managedGit?["Use the managed `git` and `gh` commands on PATH. Do not bypass th\
+em with host binaries, a stripped PATH, or alternate credentials.","For attachments and inline images that GitHub stores\
+ for issues (tickets), pull requests or comments, use authenticated managed `gh api` with the original attachment URL, s\
+ave the response to a local file and inspect it before reporting its contents. Never use unauthenticated curl/wget, User\
+-Agent experiments or extracted credentials; an unauthenticated 404 does not prove a private attachment is missing.","Af\
+ter changing GitHub issues, comments, labels or pull requests, run `vibe64-helper github refresh` once so Vibe64's Issue\
+s/PR view reflects it.","When linking an issue in this project's repository, run `vibe64-helper github issue-link <numbe\
+r>` and use its returned Vibe64 path exactly, including the /app prefix, as the primary Markdown link destination; it na\
+vigates in-app. You may include the GitHub URL as a secondary link. Never guess the project slug or host; issues in othe\
+r repositories keep their GitHub links.","Report authentication or transport failures directly; do not inspect credentia\
+ls 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, and the next safe action. Retain the repo\
+rted 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 problem. Separate recorded facts from hypotheses; say the cause is unknown when it is unproven. \
+Recommend reconnection only when the reported error explicitly calls for it.","If the diagnostic says commandSubmitted=f\
+alse, the requested Git/GitHub action was not attempted. After an execution timeout, lost response or unreadable respons\
+e, its effects are unconfirmed: use a read-only check of the affected Git/GitHub state before repeating any write. Never\
+ claim that a comment was posted or not posted, or that a push succeeded or failed, from those errors alone. If verifica\
+tion is unavailable, report the outcome as unknown and stop; do not repeat the write or claim a safe rollback."]:[]].join(
+`
+`)}function O(e={}){let s=d(e,"Vibe64 driver input"),r=b(s);return r.scope==="session"?V(r):r.stableContext}async function D(e={},{
 readRegistry:s=y,workdir:r=""}={}){let t=d(e,"Vibe64 host resolver request");if(i(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 n=d(t.data,"Vibe64 host resolver da\
-ta");i(n,["registryPath"],"Vibe64 host resolver data");let o=c(n.registryPath);if(!p.isAbsolute(o))throw new TypeError("\
+ta");i(n,["registryPath"],"Vibe64 host resolver data");let o=c(n.registryPath);if(!l.isAbsolute(o))throw new TypeError("\
 Vibe64 host resolver data requires an absolute registryPath.");let h=JSON.parse(await s(o,"utf8"));if(!Array.isArray(h?.
-sessions))throw new TypeError("The conversation ownership registry is invalid.");let b=h.sessions,g=c(t.providerSessionId);
+sessions))throw new TypeError("The conversation ownership registry is invalid.");let f=h.sessions,g=c(t.providerSessionId);
 if(t.parentSessionIds!==void 0&&(!Array.isArray(t.parentSessionIds)||t.parentSessionIds.length>32||t.parentSessionIds.some(
-a=>typeof a!="string"||!a.trim())))throw new TypeError("Invalid native conversation ancestry.");let l=[g,...t.parentSessionIds||
-[]].filter(Boolean).map(a=>b.find(w=>c(w?.upstreamSessionId)===a)).find(Boolean),u=l?.promptContext;if(!u)return null;if(r&&
-l.workdir&&p.resolve(r)!==p.resolve(l.workdir))throw new Error("The managed conversation belongs to a different project \
-directory.");return f(u)}export{A as vibe64Driver,D as vibe64DriverInputFromRegistry};
+a=>typeof a!="string"||!a.trim())))throw new TypeError("Invalid native conversation ancestry.");let p=[g,...t.parentSessionIds||
+[]].filter(Boolean).map(a=>f.find(w=>c(w?.upstreamSessionId)===a)).find(Boolean),u=p?.promptContext;if(!u)return null;if(r&&
+p.workdir&&l.resolve(r)!==l.resolve(p.workdir))throw new Error("The managed conversation belongs to a different project \
+directory.");return b(u)}export{O as vibe64Driver,D as vibe64DriverInputFromRegistry};