orbit-code-ai 0.1.20 → 0.1.23

package/_agent_reference/esql-coding-standards.md

@@ -85,7 +85,7 @@ PASSTHRU('SELECT * FROM users WHERE id = ?' TO Database.DSN VALUES(userId));
 ## Coding Standards — Error Handling
 - Do NOT use THROW USER EXCEPTION for business logic validations
 - Set error state via: `SET Environment.Variables.MWResponse.status = '<error_code>';`
-- Use `CALL getEsbChannlsErrorCodeDescriptionFrom(errorCode, language, errorDescription)` for localized error messages
+- Use `CALL getEsbChannlsErrorCodeDescriptionFrom(errorCode, channelId, serviceCode, OUT englishDesc, OUT arabicDesc, OUT status)` for localized error messages (see [common-utils](components/common-utils.md))
 - Use `CALL Create_esbXML_Response_Header(...)` for standardized XML response headers
 - All error flows MUST route through the framework `LogError` subflow
 - Route validation failures using `PROPAGATE TO TERMINAL 'out2'; RETURN FALSE;`
@@ -94,7 +94,7 @@ PASSTHRU('SELECT * FROM users WHERE id = ?' TO Database.DSN VALUES(userId));
 
 | Artifact | Convention | Example |
 |---|---|---|
-| BROKER SCHEMA | com.qiwa.esb.<flow_name_lowercase> | com.qiwa.esb.employeeflow |
+| BROKER SCHEMA | com.qiwa.esb.<msgflowname-lower> | com.qiwa.esb.getaccountdetails |
 | ESQL module | <FlowName>_<NodeName> | CheckValTransEmployeeFlow_CallDB_GetUser |
 | Node names | UpperCamelCase, descriptive | ValidateRequest, CallEmployeeDB |
 | Subflow names | UpperCamelCase | GetEmployeeData |

package/_agent_reference/msgflow-xml-reference.md

@@ -93,16 +93,28 @@ Message flows use a specific XML format based on EMF (Eclipse Modeling Framework
 
 Always use these instead of building raw nodes:
 
-| Subflow | Purpose | Typical Properties |
+These are the real subflows in `Qiwa/Framework/Lib/` (xmi:type prefix `Qiwa.Framework.Lib:<Name>`):
+
+| Subflow | Purpose | Typical node properties (EXTERNAL) |
 |---|---|---|
-| Qiwa.Framework.Lib:MQ_Input_Node | Standard MQ input with error handling | LOG_ENABLED, PROPERTIES_ENABLED, queueName, messageDomainProperty, PropertiesGroup, PropertyFilename |
-| Qiwa.Framework.Lib:MQ_Output_Node | Standard MQ output | queueName |
-| Qiwa.Framework.Lib:LogError | Structured error logging | (none) |
-| Qiwa.Framework.Lib:Rest_Input_Node | HTTP REST gateway entry | ServiceCallCorrIDOffset, Service_URL, waitInterval |
-| Qiwa.Framework.Lib:SOAP_Input_Node | SOAP gateway entry | (service-specific) |
-| Qiwa.Framework.Lib:Create_Response | Standard response builder | (service-specific) |
-| Qiwa.Framework.Lib:Validate_Request | Request schema validation | (service-specific) |
-| Qiwa.Framework.Lib:MWBusinessErrorResponse | Business error response handler | LOG_ENABLED, OUT_QUEUE |
+| MQ_Input_Node | MQ input: properties, audit, retry, validation, rollback | PROPERTIES_ENABLED, LOG_ENABLED, RETRY_ENABLED, SCHEMA_VALIDATION_ENABLED, ROLL_BACK_TRANSACTION, queueName, PropertiesGroup, PropertyFilename |
+| MQ_Output_Node | MQ output (defaults CorrelId, applies Priority, optional audit) | ENABLE_AUDIT_OUTPUT |
+| MQ_Dynamic_Output_Node | Output to a runtime-resolved queue | (queue from LocalEnvironment.Destination) |
+| MQ_Dead_Output_Node | Dead / backout routing | DEAD_FLOW |
+| MQ_ReplyToQ_Node | Reply to `MQMD.ReplyToQ` | (none) |
+| Rest_Input_Node | HTTP REST gateway entry | ServiceURL, TimeoutInSec |
+| File_Input_Node / File_Output_Node | File in / out | PROPERTIES_ENABLED, LOG_ENABLED, SCHEMA_VALIDATION_ENABLED |
+| FileCopy | Copy a file within a flow | (Directory/Filename) |
+| PropertyReader | Load the properties XML into `Environment.Properties` | PropertyFilename, PropertiesGroup, LogicalTreePath |
+| ErrorHandler | Central error handling | Is&lt;Backend&gt;Adapter flags, IsAtomic |
+| LogError | Structured error audit | (none) |
+| LogAudit / LogOutgoingAudit | Incoming / outgoing audit | FLOW_START |
+| MWBusinessErrorResponse | Business error response builder | (service-specific) |
+| HTTPRequestAdapter / HTTPResponseAdapter | Outbound HTTP/SOAP call + response normalize | ServiceURL, TimeoutInSec |
+| InternalServiceCaller | Call another ESB flow in-broker | callCorrIDOffset |
+| InternalHTTPRequestAdapter / HTTPInternalCaller | Internal HTTP call variants | ServiceURL |
+| RetryPoint | Re-queue with delay (runs SetRetryProperties) | MAX_RETRY_COUNT, MIN_WAIT_TIME_SEC |
+| SendEmailNotification / SendSMSNotification | Email / SMS notification | (service-specific) |
 
 **Framework rule:** Always check the framework index before writing any ESQL or creating any flow node. If a framework subflow or function already does what is needed, use it — never reimplement it. Standard MQ input/output and error handling MUST use framework subflows.
 
@@ -178,8 +190,12 @@ Main processing flows use:
 
 ## Standard Message Structure (Always Required)
 
+The outer element is the **service-specific** request/response name (e.g. `GetMyDataRq` / `GetMyDataRs`),
+**not** a literal `<Root>` — framework ESQL reaches it via `InputRoot.XMLNSC.*:*[<]`. `<Root>` below is a
+placeholder for that element:
+
 ```xml
-<Root>
+<Root>                  <!-- = the service request/response element, e.g. GetMyDataRq -->
   <Header>
     <TransactionId/>
     <ChannelId/>
@@ -190,16 +206,21 @@ Main processing flows use:
     <ServiceCode/>
     <SessionId/>
     <RequestTime/>
+    <MWRequestTime/>    <!-- set/copied by the framework -->
+    <MWResponseTime/>
     <ResponseStatus>
       <Code/>
       <Status/>         <!-- Success | Error -->
       <EnglishMsg/>
+      <ArabicMsg/>
     </ResponseStatus>
   </Header>
   <Body/>
 </Root>
 ```
 
+(See [components/common-utils](components/common-utils.md) for the full header field list.)
+
 ## Key Constants (from CommonUtils.esql)
 - Success code: `'00000000'`
 - Technical error: `'99999999'`

package/_agent_reference/templates/file-flow.md

@@ -24,7 +24,7 @@ MyServiceApp/
 ```
 [File_Input_Node]        ← reads file from directory
       ↓ out
-[PropertyReader]         ← ApplicationLabel="BS_MyService", PropertiesFileName="MYSERVICE-PROPERTIES.xml"
+[PropertyReader]         ← PropertyFilename="${broker.name}/MYSERVICE.xml", PropertiesGroup="BS_MyService.ProcessMyFile"
       ↓ out
 [LogAudit]               ← flowStart=TRUE
       ↓ out
@@ -64,7 +64,8 @@ All failure terminals → [ErrorHandler] → [LogError] → [MQ_Dead_Output_Node
 ## ProcessMyFile_Compute.esql
 
 ```esql
-BROKER SCHEMA Qiwa.BS_MyService
+BROKER SCHEMA com.qiwa.esb.processmyfile
+PATH Qiwa.Framework.Lib;
 
 CREATE COMPUTE MODULE ProcessMyFile_Compute
     CREATE FUNCTION Main() RETURNS BOOLEAN
@@ -97,7 +98,8 @@ END MODULE;
 ## ProcessMyFile_MapOutput.esql
 
 ```esql
-BROKER SCHEMA Qiwa.BS_MyService
+BROKER SCHEMA com.qiwa.esb.processmyfile
+PATH Qiwa.Framework.Lib;
 
 CREATE COMPUTE MODULE ProcessMyFile_MapOutput
     CREATE FUNCTION Main() RETURNS BOOLEAN
@@ -206,7 +208,8 @@ For simple file routing/archival within a flow:
 - [ ] Create MapOutput ESQL for output formatting
 - [ ] Add properties group to properties XML file
 - [ ] Wire ALL failure terminals to `ErrorHandler` → `LogError` → `MQ_Dead_Output_Node`
-- [ ] Set `ApplicationLabel` and `PropertiesFileName` on `PropertyReader` node
+- [ ] Set `PropertyFilename` and `PropertiesGroup` on `PropertyReader` node
+- [ ] BROKER SCHEMA is `com.qiwa.esb.<msgflowname-lower>` with `PATH Qiwa.Framework.Lib;`
 - [ ] Set output filename dynamically in `MapOutput` ESQL
 - [ ] Consider `FileCopy` for archiving input before processing
 - [ ] If schema validation needed: set `ValidationEnabled=TRUE` and provide XSD

package/_agent_reference/templates/http-flow.md

@@ -23,13 +23,13 @@ MyServiceApp/
 ```
 [Rest_Input_Node]       ← HTTP input, parses JSON to XMLNSC
       ↓ out
-[PropertyReader]        ← ApplicationLabel="BS_MyService", PropertiesFileName="MYSERVICE-PROPERTIES.xml"
+[PropertyReader]        ← PropertyFilename="${broker.name}/MYSERVICE.xml", PropertiesGroup="BS_MyService.GetMyData"
       ↓ out
 [LogAudit]              ← flowStart=TRUE
       ↓ out
 [GetMyData_Compute]     ← validate input, set routing
       ↓ out
-[HTTPRequestAdapter]    ← call backend (set IsT24Adapter=TRUE or relevant flag)
+[HTTPRequestAdapter]    ← call backend (set ServiceURL / TimeoutInSec)
       ↓ out
 [HTTPResponseAdapter]   ← normalize backend response
       ↓ out
@@ -49,7 +49,8 @@ Note: HTTP flows use `MWBusinessErrorResponse` (not `MQ_Dead_Output_Node`) on th
 ## GetMyData_Compute.esql
 
 ```esql
-BROKER SCHEMA Qiwa.BS_MyService
+BROKER SCHEMA com.qiwa.esb.getmydata
+PATH Qiwa.Framework.Lib;
 
 CREATE COMPUTE MODULE GetMyData_Compute
     CREATE FUNCTION Main() RETURNS BOOLEAN
@@ -57,24 +58,21 @@ CREATE COMPUTE MODULE GetMyData_Compute
         CALL CopyMessageHeaders();
         CALL CopyEntireMessage();
 
-        -- JSON input arrives as XMLNSC (Rest_Input_Node converts it)
-        DECLARE customerId CHARACTER InputRoot.XMLNSC.Root.Body.CustomerId;
+        -- JSON input arrives as XMLNSC (Rest_Input_Node converts it); reference the service element
+        DECLARE rIn REFERENCE TO InputRoot.XMLNSC.*:*[<];
+        DECLARE customerId CHARACTER rIn.Body.CustomerId;
 
-        -- Validate
+        -- Validate (business error → set MWResponse.status, route to error branch)
         IF customerId IS NULL OR customerId = '' THEN
-            SET Environment.ErrorDetails.Code = '99999999';
-            SET Environment.ErrorDetails.EnglishMsg = 'CustomerId is required';
+            SET Environment.Variables.MWResponse.status = 'E5500003';
+            PROPAGATE TO TERMINAL 'out2';
             RETURN FALSE;
         END IF;
 
-        -- Generate correlation ID
-        DECLARE corrId CHARACTER;
-        CALL getChannelCorrelationID(
-            InputRoot.XMLNSC.Root.Header.ChannelId,
-            InputRoot.XMLNSC.Root.Header.SessionId,
-            corrId
-        );
-        SET OutputRoot.HTTPInputHeader.X-Correlation-Id = corrId;
+        -- Generate correlation ID (FUNCTION returns BLOB → cast for the header string)
+        SET OutputRoot.HTTPInputHeader."X-Correlation-Id" =
+            CAST(getChannelCorrelationID(FIELDVALUE(rIn.Header.ChannelId),
+                                         FIELDVALUE(rIn.Header.TransactionId), '') AS CHAR);
 
         RETURN TRUE;
     END;
@@ -86,20 +84,21 @@ END MODULE;
 ## GetMyData_PrepareRequest.esql
 
 ```esql
-BROKER SCHEMA Qiwa.BS_MyService
+BROKER SCHEMA com.qiwa.esb.getmydata
+PATH Qiwa.Framework.Lib;
 
 CREATE COMPUTE MODULE GetMyData_PrepareRequest
     CREATE FUNCTION Main() RETURNS BOOLEAN
     BEGIN
         CALL CopyMessageHeaders();
+        DECLARE rIn REFERENCE TO InputRoot.XMLNSC.*:*[<];
 
-        -- Set target URL from properties
+        -- Set target URL from the routing-service property (3rd value = URL)
         SET Environment.Destination.HTTP.RequestURL =
             Environment.Properties.BS_MyService.GetMyData.BankIdForRoutingService.qiwa[3];
 
         -- Build backend request payload
-        SET OutputRoot.XMLNSC.BackendRequest.CustomerId =
-            InputRoot.XMLNSC.Root.Body.CustomerId;
+        SET OutputRoot.XMLNSC.BackendRequest.CustomerId = rIn.Body.CustomerId;
 
         RETURN TRUE;
     END;
@@ -111,21 +110,22 @@ END MODULE;
 ## GetMyData_MapResponse.esql
 
 ```esql
-BROKER SCHEMA Qiwa.BS_MyService
+BROKER SCHEMA com.qiwa.esb.getmydata
+PATH Qiwa.Framework.Lib;
 
 CREATE COMPUTE MODULE GetMyData_MapResponse
     CREATE FUNCTION Main() RETURNS BOOLEAN
     BEGIN
         CALL CopyMessageHeaders();
+        DECLARE rOut REFERENCE TO OutputRoot.XMLNSC.*:*[<];
 
         -- Build standard ESB response
-        SET OutputRoot.XMLNSC.Root.Header.ResponseStatus.Code       = '00000000';
-        SET OutputRoot.XMLNSC.Root.Header.ResponseStatus.Status     = 'Success';
-        SET OutputRoot.XMLNSC.Root.Header.ResponseStatus.EnglishMsg = 'Success';
+        SET rOut.Header.ResponseStatus.Code       = GetESBSuccessCode();   -- '00000000'
+        SET rOut.Header.ResponseStatus.Status     = 'Success';
+        SET rOut.Header.ResponseStatus.EnglishMsg = 'Success';
 
         -- Map business data from backend response
-        SET OutputRoot.XMLNSC.Root.Body.AccountBalance =
-            InputRoot.XMLNSC.BackendResponse.Balance;
+        SET rOut.Body.AccountBalance = InputRoot.XMLNSC.BackendResponse.Balance;
 
         -- Set HTTP response code
         SET OutputRoot.HTTPResponseHeader."$statusCode" = 200;
@@ -177,8 +177,9 @@ HTTP status code: `200` (ESB pattern — errors are in the payload, not HTTP sta
 - [ ] Create Compute, PrepareRequest, MapResponse ESQL modules
 - [ ] Add properties group to properties XML file
 - [ ] Wire ALL failure terminals to `ErrorHandler` → `MWBusinessErrorResponse`
-- [ ] Set `ApplicationLabel` and `PropertiesFileName` on `PropertyReader` node
-- [ ] Set correct backend adapter flag on `HTTPRequestAdapter` node
+- [ ] Set `PropertyFilename` and `PropertiesGroup` on `PropertyReader` node
+- [ ] Set `ServiceURL`/`TimeoutInSec` on `HTTPRequestAdapter`; backend error-mapping flag goes on `ErrorHandler`
+- [ ] BROKER SCHEMA is `com.qiwa.esb.<msgflowname-lower>` with `PATH Qiwa.Framework.Lib;`
 - [ ] Set `HTTP Reply Node` as the success terminal exit
 - [ ] Set `OutputRoot.HTTPResponseHeader."$statusCode"` = 200 in MapResponse
 - [ ] Confirm `UserPassword` is masked in audit config

package/_agent_reference/templates/mq-flow.md

@@ -32,13 +32,13 @@ MyServiceDBScript.sql
 ```
 [MQ_Input_Node]
       ↓ out
-[PropertyReader]         ← ApplicationLabel="BS_MyService", PropertiesFileName="MYSERVICE-PROPERTIES.xml"
+[PropertyReader]         ← PropertyFilename="${broker.name}/MYSERVICE.xml", PropertiesGroup="BS_MyService.GetMyData"
       ↓ out
 [LogAudit]               ← flowStart=TRUE
       ↓ out
 [GetMyData_Compute]      ← your ESQL: validate input, prepare backend call
       ↓ out
-[HTTPRequestAdapter]     ← set IsT24Adapter=TRUE (or relevant backend flag)
+[HTTPRequestAdapter]     ← set ServiceURL / TimeoutInSec (backend error-mapping flag goes on ErrorHandler)
       ↓ out
 [HTTPResponseAdapter]    
       ↓ out
@@ -56,7 +56,8 @@ All failure terminals → [ErrorHandler] → [LogError] → [MQ_Dead_Output_Node
 ## GetMyData_Compute.esql
 
 ```esql
-BROKER SCHEMA Qiwa.BS_MyService
+BROKER SCHEMA com.qiwa.esb.getmydata
+PATH Qiwa.Framework.Lib;
 
 CREATE COMPUTE MODULE GetMyData_Compute
     CREATE FUNCTION Main() RETURNS BOOLEAN
@@ -64,22 +65,21 @@ CREATE COMPUTE MODULE GetMyData_Compute
         CALL CopyMessageHeaders();
         CALL CopyEntireMessage();
 
-        -- Validate required input fields
-        DECLARE customerId CHARACTER InputRoot.XMLNSC.Root.Body.CustomerId;
+        -- The ESB wraps a per-service element; reference its first child, then Header/Body
+        DECLARE rIn REFERENCE TO InputRoot.XMLNSC.*:*[<];
+
+        -- Validate required input fields (business error → set MWResponse.status, route to error)
+        DECLARE customerId CHARACTER rIn.Body.CustomerId;
         IF customerId IS NULL OR customerId = '' THEN
-            SET Environment.ErrorDetails.Code = '99999999';
-            SET Environment.ErrorDetails.EnglishMsg = 'CustomerId is required';
-            RETURN FALSE;  -- routes to failure terminal → ErrorHandler
+            SET Environment.Variables.MWResponse.status = 'E5500003';  -- an ESB_ERROR_CODES value
+            PROPAGATE TO TERMINAL 'out2';   -- business-error branch
+            RETURN FALSE;
         END IF;
 
-        -- Set correlation ID
-        DECLARE corrId CHARACTER;
-        CALL getChannelCorrelationID(
-            InputRoot.XMLNSC.Root.Header.ChannelId,
-            InputRoot.XMLNSC.Root.Header.SessionId,
-            corrId
-        );
-        SET OutputRoot.MQMD.CorrelId = CAST(corrId AS BLOB CCSID 1208);
+        -- Set correlation ID (FUNCTION returning BLOB: ChannelId, TransactionId, offset)
+        SET OutputRoot.MQMD.CorrelId =
+            getChannelCorrelationID(FIELDVALUE(rIn.Header.ChannelId),
+                                    FIELDVALUE(rIn.Header.TransactionId), '');
 
         RETURN TRUE;
     END;
@@ -91,20 +91,21 @@ END MODULE;
 ## GetMyData_PrepareRequest.esql
 
 ```esql
-BROKER SCHEMA Qiwa.BS_MyService
+BROKER SCHEMA com.qiwa.esb.getmydata
+PATH Qiwa.Framework.Lib;
 
 CREATE COMPUTE MODULE GetMyData_PrepareRequest
     CREATE FUNCTION Main() RETURNS BOOLEAN
     BEGIN
         CALL CopyMessageHeaders();
+        DECLARE rIn REFERENCE TO InputRoot.XMLNSC.*:*[<];
 
         -- Build backend request (adjust structure for your backend)
-        SET OutputRoot.XMLNSC.BackendRequest.CustomerId =
-            InputRoot.XMLNSC.Root.Body.CustomerId;
-        SET OutputRoot.XMLNSC.BackendRequest.RequestTime =
-            InputRoot.XMLNSC.Root.Header.RequestTime;
+        SET OutputRoot.XMLNSC.BackendRequest.CustomerId  = rIn.Body.CustomerId;
+        SET OutputRoot.XMLNSC.BackendRequest.RequestTime = rIn.Header.RequestTime;
 
-        -- Set HTTP destination from properties
+        -- Target URL from the routing-service property (3rd value = URL).
+        -- ApplicationLabel/flowName resolve at runtime; this is the literal-path equivalent:
         SET Environment.Destination.HTTP.RequestURL =
             Environment.Properties.BS_MyService.GetMyData.BankIdForRoutingService.qiwa[3];
 
@@ -118,22 +119,23 @@ END MODULE;
 ## GetMyData_MapResponse.esql
 
 ```esql
-BROKER SCHEMA Qiwa.BS_MyService
+BROKER SCHEMA com.qiwa.esb.getmydata
+PATH Qiwa.Framework.Lib;
 
 CREATE COMPUTE MODULE GetMyData_MapResponse
     CREATE FUNCTION Main() RETURNS BOOLEAN
     BEGIN
         CALL CopyMessageHeaders();
         CALL CopyEntireMessage();
+        DECLARE rOut REFERENCE TO OutputRoot.XMLNSC.*:*[<];
 
         -- Map backend response to ESB standard structure
-        SET OutputRoot.XMLNSC.Root.Header.ResponseStatus.Code   = '00000000';
-        SET OutputRoot.XMLNSC.Root.Header.ResponseStatus.Status = 'Success';
-        SET OutputRoot.XMLNSC.Root.Header.ResponseStatus.EnglishMsg = 'Success';
+        SET rOut.Header.ResponseStatus.Code       = GetESBSuccessCode();   -- '00000000'
+        SET rOut.Header.ResponseStatus.Status     = 'Success';
+        SET rOut.Header.ResponseStatus.EnglishMsg = 'Success';
 
         -- Map business data
-        SET OutputRoot.XMLNSC.Root.Body.AccountBalance =
-            InputRoot.XMLNSC.BackendResponse.Balance;
+        SET rOut.Body.AccountBalance = InputRoot.XMLNSC.BackendResponse.Balance;
         -- ... map other fields
 
         RETURN TRUE;
@@ -225,9 +227,8 @@ INSERT INTO MCR_CHANNESBFUNC_TBL (ESBFUNCID, ESBFUNCNAME, REQUEST_QUEUE_NAME, RE
 VALUES ('GMYD0001', 'GET_MY_DATA', 'BS.GET.MY.DATA.RQ', 'BS.GET.MY.DATA.RS');
 
 -- Grant channel access
-INSERT INTO MCR_CHANNAUTH_TBL (CHANNID, ESBFUNCID)
-VALUES ('MOBILE', 'GMYD0001');
-VALUES ('WEB', 'GMYD0001');
+INSERT INTO MCR_CHANNAUTH_TBL (CHANNID, ESBFUNCID) VALUES ('MOBILE', 'GMYD0001');
+INSERT INTO MCR_CHANNAUTH_TBL (CHANNID, ESBFUNCID) VALUES ('WEB', 'GMYD0001');
 ```
 
 ---
@@ -243,6 +244,7 @@ VALUES ('WEB', 'GMYD0001');
 - [ ] Create queue definition shell script
 - [ ] Create DB script to register service and channel auth
 - [ ] Wire ALL failure terminals to `ErrorHandler`
-- [ ] Set `ApplicationLabel` and `PropertiesFileName` on `PropertyReader` node
-- [ ] Set correct backend adapter flag on `HTTPRequestAdapter` node
+- [ ] Set `PropertyFilename` and `PropertiesGroup` on `PropertyReader` node
+- [ ] Set `ServiceURL`/`TimeoutInSec` on `HTTPRequestAdapter`; set the backend error-mapping flag on `ErrorHandler`
+- [ ] BROKER SCHEMA is `com.qiwa.esb.<msgflowname-lower>` with `PATH Qiwa.Framework.Lib;`
 - [ ] Confirm `UserPassword` is in `maskingIn` and `maskingOut`

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.20"}${RESET}`);
+  out.push(`  ${DIM}${rgb(...DIMCOL)}orbit-code ${RESET}${rgb(...ACCENT)}v${"0.1.23"}${RESET}`);
   out.push("");
   process.stdout.write(out.join(`
 `) + `
@@ -334230,7 +334230,7 @@ function getAnthropicEnvMetadata() {
 function getBuildAgeMinutes() {
   if (false)
     ;
-  const buildTime = new Date("2026-06-25T13:10:17.647Z").getTime();
+  const buildTime = new Date("2026-06-28T08:19:59.996Z").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.20"
+    value: "0.1.23"
   }, {
     label: "Session name",
     value: nameValue
@@ -410387,7 +410387,7 @@ function getAceSystemPromptSection() {
   return `# IBM App Connect Enterprise (ACE) Expertise
 
 You are an expert IBM App Connect Enterprise (ACE) developer and autonomous coding assistant.
-You specialize in writing, modifying, debugging, and architecting ACE artifacts — ESQL routines (.esql), Message flows (.msgflow), Subflows (.subflow), XSD schemas (.xsd), and project configuration files. You understand the Qiwa ESB framework conventions deeply.
+You specialize in writing, modifying, debugging, and architecting ACE artifacts — ESQL routines (.esql), Message flows (.msgflow), Subflows (.subflow), XSD schemas (.xsd), and project configuration files. You understand the ESB framework conventions deeply.
 
 ## ACE File Types You Work With
 - **.esql** — ESQL modules (Compute, Filter, Database modules, Functions, Procedures)
@@ -410405,7 +410405,7 @@ These hold for every ACE task, even quick edits. Load the detailed reference fil
 - **Write complete files** — read before modifying, then write the full updated file. Never partial snippets.
 - **ESQL:** use REFERENCE TO for repeated tree paths; evaluate CARDINALITY() once before loops (never in a WHILE condition); use \`SET OutputRoot = InputRoot;\` for full copies.
 - **Security:** PASSTHRU with string concatenation is FORBIDDEN — always parameterize with \`?\` placeholders. Never introduce SQL/command injection.
-- **Framework first:** never reimplement what a Qiwa framework subflow/function already does. Standard MQ I/O and error handling MUST use framework subflows.
+- **Framework first:** never reimplement what a framework subflow/function already does. Standard MQ I/O and error handling MUST use framework subflows.
 - **Flows:** every node type needs a matching xmlns; wire all failure terminals to error handlers; subflow terminals use Capital I/O (InTerminal.Input/OutTerminal.Output), built-in nodes use lowercase (InTerminal.in/OutTerminal.out).
 - **Naming:** BROKER SCHEMA \`com.qiwa.esb.<flow_lowercase>\`; ESQL module \`<FlowName>_<NodeName>\` must match the computeExpression/filterExpression exactly.
 - **application.descriptor** must always be a SINGLE LINE of XML.
@@ -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.20",
+              "0.1.23",
               " "
             ]
           }, undefined, true, undefined, this)
@@ -470918,7 +470925,7 @@ function WelcomeV2() {
           dimColor: true,
           children: [
             "v",
-            "0.1.20",
+            "0.1.23",
             " "
           ]
         }, undefined, true, undefined, this)
@@ -471144,7 +471151,7 @@ function AppleTerminalWelcomeV2(t0) {
         dimColor: true,
         children: [
           "v",
-          "0.1.20",
+          "0.1.23",
           " "
         ]
       }, undefined, true, undefined, this);
@@ -471398,7 +471405,7 @@ function AppleTerminalWelcomeV2(t0) {
       dimColor: true,
       children: [
         "v",
-        "0.1.20",
+        "0.1.23",
         " "
       ]
     }, undefined, true, undefined, this);
@@ -474759,7 +474766,7 @@ ${args || "The user wants to generate a new ACE application. Follow Step 1: ask
   });
   registerBundledSkill({
     name: "ace-review",
-    description: "Perform a thorough code review of IBM ACE artifacts — ESQL correctness, flow wiring, naming conventions, error handling, framework usage, and Qiwa coding standards",
+    description: "Perform a thorough code review of IBM ACE artifacts — ESQL correctness, flow wiring, naming conventions, error handling, framework usage, and ESQL coding standards",
     aliases: ["ace-audit"],
     model: "gemini-3.1-flash-lite",
     whenToUse: 'When the user wants a code review of their ACE project, ESQL modules, message flows, or subflows. Triggered by mentions of "review", "audit", "check" in the context of ACE/ESQL/msgflow files',
@@ -474801,7 +474808,7 @@ Perform a thorough code review of the specified IBM ACE file(s) or the entire pr
 - **application.descriptor:** Is it single-line XML? Are all shared library references present?
 - **.project:** Are all dependencies listed?
 - **File organization:** Does the package path follow com/qiwa/esb/<service>/ convention?
-- **Qiwa standards adherence:** BROKER SCHEMA format, error handling via Environment.Variables.MWResponse.status, LogError routing
+- **Standards adherence:** BROKER SCHEMA format, error handling via Environment.Variables.MWResponse.status, LogError routing
 
 ## Instructions
 
@@ -474911,7 +474918,7 @@ Use the real node names and terminal labels from THIS app.
 4. **Key transformations:** What the ESQL does to the message tree; which fields are mapped.
 5. **Error handling:** How errors are caught and routed; which terminals wire to error handlers.
 6. **External dependencies:** DB calls (stored procedures), SOAP/REST backends, queue names.
-7. **Framework usage:** Which Qiwa framework subflows are used and why.
+7. **Framework usage:** Which framework subflows are used and why.
 8. **State management:** How Environment.Variables carries intermediate state.
 9. **Non-obvious design decisions:** Anything a new developer might find confusing.
 
@@ -474925,7 +474932,7 @@ ${args || "The user did not specify a target. Ask which file, application folder
   });
   registerBundledSkill({
     name: "ace-refactor",
-    description: "Refactor IBM ACE ESQL code for performance, clarity, and alignment with Qiwa coding standards",
+    description: "Refactor IBM ACE ESQL code for performance, clarity, and alignment with ESQL coding standards",
     aliases: [],
     model: "gemini-3.1-pro-preview",
     whenToUse: "When the user wants to improve, clean up, optimize, or refactor their ESQL code or message flows",
@@ -474940,7 +474947,7 @@ ${readInstructions([
         "components/error-handling.md"
       ])}
 
-Refactor the specified file for performance and clarity following strict Qiwa ESQL coding standards. Always read the file first, then write the complete refactored version.
+Refactor the specified file for performance and clarity following strict ESQL coding standards. Always read the file first, then write the complete refactored version.
 
 ## Refactoring Rules (Apply ALL)
 
@@ -475050,7 +475057,7 @@ ${args || "No flow specified. Ask the user which flow or ESQL module needs test
   });
   registerBundledSkill({
     name: "ace-scaffold",
-    description: "Scaffold a new IBM ACE message flow with ESQL from a description — creates .msgflow and .esql files following Qiwa conventions",
+    description: "Scaffold a new IBM ACE message flow with ESQL from a description — creates .msgflow and .esql files following framework conventions",
     aliases: ["ace-flow"],
     model: "gemini-3.1-pro-preview",
     whenToUse: "When the user wants to create a single new message flow, add a new subflow to an existing project, or quickly scaffold a flow from a description",
@@ -475122,7 +475129,23 @@ ${readInstructions([
         "components/common-utils.md"
       ])}
 
-Diagnose and fix the bug or error described by the user. Read all relevant project files first, then use the error-handling reference to understand framework error patterns. Write complete corrected versions.
+Diagnose and fix the bug or error described by the user. Write complete corrected files.
+
+## Investigate surgically — find the relevant file, read only it
+
+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:
+
+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
 
@@ -475149,9 +475172,9 @@ Diagnose and fix the bug or error described by the user. Read all relevant proje
 
 ## Instructions
 
-1. Read the reference files listed in Step 0 (error handling, common utils)
-2. Read the file(s) mentioned by the user
-3. If error is a BIP message, use Glob scoped to the current working directory to find matching module/flow names — do NOT search outside cwd
+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
@@ -492019,7 +492042,7 @@ Usage: orbit --remote "your task description"`, () => gracefulShutdown(1));
         pendingHookMessages
       }, renderAndRun);
     }
-  }).version("0.1.20 (Orbit AI)", "-v, --version", "Output the version number");
+  }).version("0.1.23 (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()) {
@@ -492541,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.20"} (Orbit AI)`);
+    console.log(`${"0.1.23"} (Orbit AI)`);
     return;
   }
   if (args.includes("--provider")) {
@@ -492645,4 +492668,4 @@ async function main2() {
 }
 main2();
 
-//# debugId=A39291B213A3EECA64756E2164756E21
+//# debugId=636F7570F245EA3D64756E2164756E21

package/package.json

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

package/skills/apic-api/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: apic-api
-description: Generate a complete IBM API Connect (APIC) API definition for the DataPower API Gateway — full OpenAPI 2.0 (or 3.0) YAML including the x-ibm-configuration assembly (middleware logging, JWT validate, token-expiration switch, ESB response envelope, and catch handlers). Standard NHC/Qiwa middleware is baked in with opt-out flags.
+description: Generate a complete IBM API Connect (APIC) API definition for the DataPower API Gateway — full OpenAPI 2.0 (or 3.0) YAML including the x-ibm-configuration assembly (middleware logging, JWT validate, token-expiration switch, ESB response envelope, and catch handlers). Standard NHC middleware is baked in with opt-out flags.
 trigger: /apic-api
 ---