omp-fabric 1.18.4 → 1.19.0

package/docs/configuration.md

@@ -275,7 +275,9 @@ OMP core calls reject when the native tool reports an error. Successful `bash`,
 
 `fullCodeMode: true` is the default. Fabric takes OMP's native core tools out of the model-facing set and exposes their implementations through `fabric_exec`; `omp.read()` and the other `omp.*` core calls route through the host adapter.
 
-Fabric records which native core tools were active before it takes ownership. Switching to orchestration-only mode or unloading Fabric restores that selection. Fabric applies full-mode ownership only when the session initializes or the mode changes. It never resets an explicitly selected active tool set from input, agent-start, turn-end, or settled lifecycle hooks. The system prompt carries the full-mode execution rule.
+Fabric reaches only the core tools OMP itself has active. A tool disabled in OMP is unavailable through `omp.*` as well: discovery omits it and a call to it fails. `capture.excludeTools` is a different mechanism. It hides a tool from the model and leaves it callable through `omp.*`. Turning a core tool off while full code mode is already active applies to the next session: Fabric has removed that name from the active set, so the change is invisible to it and the tool stays reachable through `omp.*` until the session ends.
+
+Fabric records which native core tools were active before it takes ownership. Switching to orchestration-only mode or unloading Fabric restores that selection. A core tool re-enabled while full code mode is active stays hidden for that session and is not added to the restored selection. Fabric applies full-mode ownership only when the session initializes or the mode changes. It never resets an explicitly selected active tool set from input, agent-start, turn-end, or settled lifecycle hooks. The system prompt carries the full-mode execution rule.
 
 OMP core shows its model-visible skill catalog only while the native `read` tool is active. Full code mode restores the same catalog from OMP's structured skill registry and changes only the loader instruction, so `omp.read` runs inside `fabric_exec`. Native core tools stay hidden. Packaged skills mark cross-document paths with `<skill-dir>`. Fabric replaces that marker inline from OMP's expanded skill `location` or the actual `SKILL.md` read path. It never matches skill names or enumerates directories. Ordinary document reads stay unchanged. When an expanded skill invokes another installed skill, Fabric adds an exact name-to-path resolution hint for that turn, and the delegated `SKILL.md` loads before task work.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omp-fabric",
-  "version": "1.18.4",
+  "version": "1.19.0",
   "description": "A programmable tool and agent runtime for Oh My Pi (OMP)",
   "type": "module",
   "main": "./dist/index.js",