@oonacode/win32-x64 0.3.298 → 0.3.299

package/oona.exe

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/oona.exe
-size: 114155008 bytes
-sha256: dc8a7f7318a4764e332825ad44d006ebd86c2913f74b4c9f253080737451dcda
+size: 114185216 bytes
+sha256: 43f44e1818b019c25379fcbc4c3f8aa3b133e0b2a5153110ff830280d3e9dfef

package/oonacode-release.json

@@ -1,13 +1,13 @@
 {
     "name":  "oonacode",
-    "version":  "0.3.298",
+    "version":  "0.3.299",
     "channel":  "stable",
     "platform":  "win32",
     "arch":  "x64",
     "mode":  "bun",
     "launcherRuntime":  "bun 1.4.1",
-    "commit":  "9adf07a4",
-    "builtAt":  "2026-11-04T13:17:55.5203625Z",
+    "commit":  "08daf447",
+    "builtAt":  "2026-11-04T15:49:21.8564698Z",
     "engine":  "engine-store",
     "engineVersion":  "0.3.301",
     "siteOrigin":  "https://oonacode.oonak.ai",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oonacode/win32-x64",
-  "version": "0.3.298",
+  "version": "0.3.299",
   "description": "OonaCode native binaries for Windows x64: oona.exe (CLI + headless host service), the pinned oonaclaude.exe engine sidecar, local web UI assets. Installed automatically as an optional dependency of `oonacode`.",
   "license": "UNLICENSED",
   "homepage": "https://oonacode.oonak.ai",

package/registry.json

@@ -746,7 +746,7 @@
           "kind": "other"
         }
       ],
-      "notes": "OPERATOR POOL ONLY (owner, 2026-10-13: \"integrate into oonacode … muse and codex … on the oonacode server in the pool list, all models … implement authentication flow on the server for both … similar to supergrok and codex with translation layer\"). The operator's own Meta Muse Code subscription, signed in from Admin → Providers → Meta Muse by a REAL Muse CLI on the server (`muse login` in a private HOME; packages/gateway/src/muse/*). The credential row is a POINTER; the static api_key a browser sign-in mints is read from Muse's own ~/.config/muse/auth.json per request (there is no refresh token and no expiry). Chats are NOT run through Muse: the engine's Anthropic request is translated to the Responses wire (@oonacode/translate responses-*.ts — the wire muse itself speaks, POST /v1/responses) and sent to api.meta.ai with Muse's identity headers (recorded 2026-10-13 through a loopback recorder). The pool serves the -contributor ids too (owner, 2026-10-13: cheaper; Muse's contributor mode lets Meta use the content for product improvement, accepted for the pool); a request for one carries x-tbh-contributor-mode: 1 like the CLI's, any other model does not. Meta's subscription terms say the credential is for use with Muse Code only; serving other people from it is the owner's call (2026-10-13), as for the Claude, SuperGrok and ChatGPT plans. A user's OWN Muse key is muse-subscription, direct from their PC. The model list is what GET api.meta.ai/muse-code/models answered for the owner's account on 2026-10-13 (muse-image-1.0 is hidden and image-only; the contributor twins are left out). docs/muse-engine.md.",
+      "notes": "OPERATOR POOL ONLY (owner, 2026-10-13: \"integrate into oonacode … muse and codex … on the oonacode server in the pool list, all models … implement authentication flow on the server for both … similar to supergrok and codex with translation layer\"). The operator's own Meta Muse Code subscription, signed in from Admin → Providers → Meta Muse by a REAL Muse CLI on the server (`muse login` in a private HOME; packages/gateway/src/muse/*). The credential row is a POINTER; the static api_key a browser sign-in mints is read from Muse's own ~/.config/muse/auth.json per request (there is no refresh token and no expiry). Chats are NOT run through Muse: the engine's Anthropic request is translated to the Responses wire (@oonacode/translate responses-*.ts — the wire muse itself speaks, POST /v1/responses) and sent to api.meta.ai with Muse's identity headers (recorded 2026-10-13 through a loopback recorder). The pool serves the -contributor ids (owner, 2026-10-13: cheaper; Muse's contributor mode lets Meta use the content for product improvement, accepted for the pool) and, since 2026-11-04, ONLY those four (the standard ids are in the catalogue but not pooled); every request carries x-tbh-contributor-mode like the CLI's: 1 with a -contributor id, 0 with any other (measured on Muse 1.4.14: contributor mode appends -contributor to an id only when Meta's model list holds the twin). Meta's subscription terms say the credential is for use with Muse Code only; serving other people from it is the owner's call (2026-10-13), as for the Claude, SuperGrok and ChatGPT plans. A user's OWN Muse key is muse-subscription, direct from their PC. The model list is what GET api.meta.ai/muse-code/models answered for the owner's account on 2026-10-13 (muse-image-1.0 is hidden and image-only and is not listed here; the four contributor twins are listed below). docs/muse-engine.md (section 11, \"The setup as it stands\").",
       "credentialVariants": [
         {
           "id": "token-plan",