toga-ai 1.0.143 → 1.0.144

package/knowledge/1.0/apps/library/features/netsuite-suiteql-api-reference.md

@@ -58,12 +58,12 @@ App_Api_Netsuite_Rest::authenticate();   // acquire OAuth2 token once
 - In our usage the client is effectively **read-only**: only `GET` (record fetch) and `POST`
   (SuiteQL) are exercised. `send()` accepts any verb (incl. PATCH/PUT) but we don't write through it.
 
-### The `send()` logging trap (dev laptop)
+### Disabling logging for ad-hoc SuiteQL probes
 
-`App_Api_Netsuite_Rest::send()` auto-authenticates but does **not** call `setLogging(false)`. From a
-dev laptop the API-log DB write then fails and the framework error handler reports a **misleading
-"Could not connect to database 'Vision'"** that masks the real result. Workaround: `authenticate()`
-once, then issue your own `App_ApiTransaction` with logging off:
+`App_Api_Netsuite_Rest::send()` auto-authenticates and logs to the API-log DB by default (it does
+**not** call `setLogging(false)`). That's fine in normal environments; for a one-off **read-only
+probe** you can keep the call out of the API log by authenticating once and issuing your own
+`App_ApiTransaction` with logging off:
 
 ```php
 $url = rtrim(App_Api_Netsuite_Rest::$endpoint, '/') . App_Api_Netsuite_Rest::API_BASE_PATH

package/knowledge/1.0/apps/worker/workflows/onboarding-client-to-netsuite-togasupply-sync.md

@@ -90,7 +90,7 @@ the directory; no `USE`).
   with "Unknown database 'logs_<name>'" if absent.
 - Run the cron in place with `C:\xampp8\php\php.exe` from the `worker/` dir; the autoloader
   walks up to `worker/_` for `__APPROOT__`. `App_Api_Netsuite_Rest::authenticate()` +
-  `App_ApiTransaction->setLogging(false)` is the laptop-safe NetSuite pattern (see
+  `App_ApiTransaction->setLogging(false)` is the read-only SuiteQL probe pattern (see
   `test/@dave/nsq.php`, a read-only SuiteQL runner).
 - Verified behavior: empty window → 0 writes, checkpoint advances (clean no-op); record
   already present → `PUT` update (idempotent, keyed on `c_netsuiteInternalSalesOrderId`, no

package/knowledge/2.0/apps/worker2/features/netsuite-opportunity-sync.md

@@ -145,8 +145,8 @@ Shared helpers: `buildCustomFields()` (the field array, used by both create and
   `Presales Lead Email`, and `Presales Lead` (users field).
 - The ClickUp token comes from `[clickup] token` in the worker2 config (legacy webhook received
   it on the payload; the new contract drops it).
-- Every ClickUp `_ApiRequest` calls `setLogging(self::CLICKUP_API_LOGGING_ENABLED=false)` — the
-  `_ApiRequest` Logs-DB default otherwise surfaces a misleading "connection refused" on dev laptops.
+- Every ClickUp `_ApiRequest` calls `setLogging(self::CLICKUP_API_LOGGING_ENABLED=false)`, so ClickUp
+  traffic is not written to the Logs DB.
 
 ## Data model
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.143",
+  "version": "1.0.144",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",