orbit-code-ai 0.1.19 → 0.1.22

package/dist/cli.mjs

@@ -83759,7 +83759,7 @@ async function printStartupScreen() {
   const sLen = ` ● ${sL}    Ready — type /help to begin`.length;
   out.push(boxRow(sRow, W2, sLen));
   out.push(`${rgb(...BORDER)}╚${"═".repeat(W2 - 2)}╝${RESET}`);
-  out.push(`  ${DIM}${rgb(...DIMCOL)}orbit-code ${RESET}${rgb(...ACCENT)}v${"0.1.19"}${RESET}`);
+  out.push(`  ${DIM}${rgb(...DIMCOL)}orbit-code ${RESET}${rgb(...ACCENT)}v${"0.1.22"}${RESET}`);
   out.push("");
   process.stdout.write(out.join(`
 `) + `
@@ -334230,7 +334230,7 @@ function getAnthropicEnvMetadata() {
 function getBuildAgeMinutes() {
   if (false)
     ;
-  const buildTime = new Date("2026-06-25T12:29:23.980Z").getTime();
+  const buildTime = new Date("2026-06-28T07:25:11.496Z").getTime();
   if (isNaN(buildTime))
     return;
   return Math.floor((Date.now() - buildTime) / 60000);
@@ -358647,7 +358647,7 @@ function buildPrimarySection() {
   }, undefined, false, undefined, this);
   return [{
     label: "Version",
-    value: "0.1.19"
+    value: "0.1.22"
   }, {
     label: "Session name",
     value: nameValue
@@ -410444,8 +410444,15 @@ The \`_agent_reference\` folder contains the authoritative detailed standards, t
 
 ---
 
+## Code Navigation — Be Surgical (find the relevant file, read only it)
+Work like a precise engineer, not a crawler. Reading unneeded files wastes time and money and dilutes focus — find the file that matters, read it, and stop.
+- **Locate before you read.** Start from a concrete signal: a file/module/flow name, a symbol, an error or BIP code, a field. Use \`Grep\` (for a symbol or string) or \`Glob\` (for a filename), **scoped to the current working directory**, to find the exact file. Do not open files speculatively.
+- **Read only what the search points to**, plus the one or two files it directly references (e.g. a .msgflow's computeExpression → that .esql). Open a file ONLY when you have a concrete reason to.
+- **Never crawl.** Do not bulk-read directories, do not "read all the files first," and never read the shared framework/libraries to understand an application — anything under \`Framework/\`, \`Utils/\`, \`Qiwa/Framework/Lib\`, or \`lib/\` is shared infrastructure. Use the \`_agent_reference\` docs above for framework behavior instead of opening its source.
+- **Narrow, don't widen.** If a search returns many matches, refine the query — don't read them all.
+
 ## General Behavior
-- Always read files before modifying them
+- Always read a file before modifying it (the specific file you will edit — not the whole project)
 - Always write complete file content — never partial snippets
 - When generating a full application, generate every required file — do not stop halfway
 - Prioritize correctness and security. Never introduce SQL injection, command injection, or other vulnerabilities
@@ -470718,7 +470725,7 @@ function WelcomeV2() {
             dimColor: true,
             children: [
               "v",
-              "0.1.19",
+              "0.1.22",
               " "
             ]
           }, undefined, true, undefined, this)
@@ -470918,7 +470925,7 @@ function WelcomeV2() {
           dimColor: true,
           children: [
             "v",
-            "0.1.19",
+            "0.1.22",
             " "
           ]
         }, undefined, true, undefined, this)
@@ -471144,7 +471151,7 @@ function AppleTerminalWelcomeV2(t0) {
         dimColor: true,
         children: [
           "v",
-          "0.1.19",
+          "0.1.22",
           " "
         ]
       }, undefined, true, undefined, this);
@@ -471398,7 +471405,7 @@ function AppleTerminalWelcomeV2(t0) {
       dimColor: true,
       children: [
         "v",
-        "0.1.19",
+        "0.1.22",
         " "
       ]
     }, undefined, true, undefined, this);
@@ -475122,25 +475129,23 @@ ${readInstructions([
         "components/common-utils.md"
       ])}
 
-## How to work — read the real code, in as few steps as possible
+Diagnose and fix the bug or error described by the user. Write complete corrected files.
 
-Accurate diagnosis requires reading the ACTUAL code and choosing the relevant files YOURSELF. Do
-that directly — do NOT delegate gathering to a sub-agent and do NOT work from a summary; a lossy
-digest causes wrong root-cause identification and wrong fixes. Keep cost down by minimizing the
-NUMBER of read steps, not by reading less.
+## Investigate surgically — find the relevant file, read only it
 
-**Step 1 — gather in ONE shot.** Identify the buggy file and its directly-related files in THIS
-application (the \`.msgflow\` that wires a broken \`.esql\`, the \`.esql\` a compute node points at,
-the relevant property \`.xml\`), then read them ALL with a SINGLE \`Bash\` command — e.g. one
-\`cat fileA fileB …\` or \`find <app> … -exec cat\` scoped to the app folder — instead of many
-separate \`Read\` calls. One-file-at-a-time reading re-processes the whole context every step and is
-the main cost driver. **Do NOT read shared libraries or other projects** — anything under
-\`Framework/\`, \`Utils/\`, \`Qiwa/Framework/Lib\`, or \`lib/\` is OUT OF SCOPE; use the
-error-handling/common-utils references above for framework patterns instead.
+Work like a precise debugger, NOT a crawler. Do NOT bulk-read directories or "read all the files" —
+that wastes time and money. Locate the specific file(s) that matter, read those, and stop:
 
-**Step 2 — diagnose and fix.** From the real code you just read, identify the EXACT root cause
-(quote the offending line), explain it in plain language, then apply the minimal correct fix and
-write the full corrected file. Do not rewrite unrelated parts.
+1. Start from the concrete signal in the bug report — a BIP code, an ESQL module name, a flow/node
+   name, a field, or an error string.
+2. Find it with a SCOPED search: \`Grep\` for the symbol/string, or \`Glob\` for the filename,
+   restricted to the current working directory. Let the search point you to the exact file.
+3. Read ONLY the file(s) the search identifies, plus the one or two they directly reference (e.g. a
+   \`.msgflow\`'s computeExpression → that \`.esql\`). Open a file ONLY when you have a concrete reason.
+4. **Never crawl shared infrastructure or unrelated apps** — do not read under \`Framework/\`,
+   \`Utils/\`, \`Qiwa/Framework/Lib\`, \`lib/\`, or other application folders. Use the error-handling
+   and common-utils references above for framework behavior instead of opening library source.
+5. If a search returns many hits, narrow the term — don't read them all.
 
 ## Common ACE Bugs to Check
 
@@ -475167,15 +475172,15 @@ write the full corrected file. Do not rewrite unrelated parts.
 
 ## Instructions
 
-1. Gather the buggy file + directly-related app files in ONE batch read (Step 1) — never bulk-read
-   the framework (\`Framework/\`, \`Utils/\`, \`lib/\`) or other projects.
-2. If the error is a BIP message, Glob within the cwd to find matching module/flow names — never
-   search outside cwd.
-3. Identify the EXACT root cause — quote the problematic line.
-4. Explain the bug in plain language.
-5. Apply the minimal correct fix; write the full corrected file — never partial content.
-6. Do NOT rewrite unrelated parts of the file.
-7. If the user rejects a write, do NOT retry.
+1. From the bug report, pick the concrete signal (BIP code, module/flow name, field, error text)
+2. Locate the file with a cwd-scoped Grep/Glob — never search outside cwd, never crawl the framework
+3. Read ONLY the matched file(s) and any file they directly reference — do not bulk-read
+4. Identify the EXACT root cause — quote the problematic line
+5. Explain the bug in plain language
+6. Apply the minimal correct fix
+7. Write the full corrected file back to disk — never partial content
+8. Do NOT rewrite unrelated parts of the file
+9. If the user rejects a write, do NOT retry
 
 ## User's Bug Report
 
@@ -492037,7 +492042,7 @@ Usage: orbit --remote "your task description"`, () => gracefulShutdown(1));
         pendingHookMessages
       }, renderAndRun);
     }
-  }).version("0.1.19 (Orbit AI)", "-v, --version", "Output the version number");
+  }).version("0.1.22 (Orbit AI)", "-v, --version", "Output the version number");
   program2.option("-w, --worktree [name]", "Create a new git worktree for this session (optionally specify a name)");
   program2.option("--tmux", "Create a tmux session for the worktree (requires --worktree). Uses iTerm2 native panes when available; use --tmux=classic for traditional tmux.");
   if (canUserConfigureAdvisor()) {
@@ -492559,7 +492564,7 @@ if (false) {}
 async function main2() {
   const args = process.argv.slice(2);
   if (args.length === 1 && (args[0] === "--version" || args[0] === "-v" || args[0] === "-V")) {
-    console.log(`${"0.1.19"} (Orbit AI)`);
+    console.log(`${"0.1.22"} (Orbit AI)`);
     return;
   }
   if (args.includes("--provider")) {
@@ -492663,4 +492668,4 @@ async function main2() {
 }
 main2();
 
-//# debugId=54338F400F5338B064756E2164756E21
+//# debugId=464CEC6DB47A292F64756E2164756E21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orbit-code-ai",
-  "version": "0.1.19",
+  "version": "0.1.22",
   "description": "Orbit AI – Your AI-powered IBM ACE coding companion",
   "type": "module",
   "author": "moenawaf",