@ours.network/fleet-codex 0.19.0-nightly.9 → 1.0.1

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ours-fleet",
-  "version": "0.19.0-nightly.9",
+  "version": "1.0.1",
   "description": "Spawn, configure, and oversee ours-fleet roles from OpenAI Codex.",
   "author": {
     "name": "Adapt Framework Solutions Ltd",
@@ -9,14 +9,7 @@
   "homepage": "https://github.com/adapt-toolkit/ours-fleet/tree/main/integrations/codex/ours-fleet",
   "repository": "https://github.com/adapt-toolkit/ours-fleet",
   "license": "FSL-1.1-Apache-2.0",
-  "keywords": [
-    "codex",
-    "ours.network",
-    "fleet",
-    "agents",
-    "spawn",
-    "oversight"
-  ],
+  "keywords": ["codex", "ours.network", "fleet", "agents", "spawn", "oversight"],
   "skills": "./skills/",
   "interface": {
     "displayName": "ours.network Fleet",
@@ -24,11 +17,7 @@
     "longDescription": "Create temporary or supervised ours-fleet roles, configure Codex models and permissions, and keep spawned agents healthy from inside Codex.",
     "developerName": "Adapt Framework Solutions Ltd",
     "category": "Productivity",
-    "capabilities": [
-      "Interactive",
-      "Read",
-      "Write"
-    ],
+    "capabilities": ["Interactive", "Read", "Write"],
     "websiteURL": "https://ours.network",
     "defaultPrompt": [
       "Spawn a new Codex fleet agent for this task.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ours.network/fleet-codex",
-  "version": "0.19.0-nightly.9",
+  "version": "1.0.1",
   "description": "Native Codex plugin for spawning, configuring, and overseeing ours-fleet agents.",
   "type": "module",
   "license": "FSL-1.1-Apache-2.0",
@@ -11,32 +11,13 @@
     "url": "git+https://github.com/adapt-toolkit/ours-fleet.git",
     "directory": "integrations/codex/ours-fleet"
   },
-  "keywords": [
-    "codex",
-    "openai",
-    "plugin",
-    "fleet",
-    "agents",
-    "spawn",
-    "oversight",
-    "ours.network"
-  ],
-  "files": [
-    ".codex-plugin",
-    "skills",
-    "bin",
-    "README.md",
-    "LICENSE"
-  ],
+  "keywords": ["codex", "openai", "plugin", "fleet", "agents", "spawn", "oversight", "ours.network"],
+  "files": [".codex-plugin", "skills", "bin", "README.md", "LICENSE"],
   "bin": {
     "ours-fleet-codex-install": "bin/ours-fleet-codex-install.mjs"
   },
-  "engines": {
-    "node": ">=20"
-  },
-  "publishConfig": {
-    "access": "public"
-  },
+  "engines": { "node": ">=20" },
+  "publishConfig": { "access": "public" },
   "scripts": {
     "test": "node --test"
   }

package/skills/spawn-ours-agent/SKILL.md

@@ -54,10 +54,16 @@ What this means in practice, on this harness:
 
 | Neutral intent | Native settings | Meets the floor? |
 | --- | --- | --- |
-| `--approval allow --filesystem workspace` | `approval=never sandbox=workspace-write` | yes |
-| `--approval allow --filesystem read-only` | `approval=never sandbox=read-only` | no — no `write-state`, no `workspace-edit` |
-| `--approval ask` | `approval=on-request` | no — `read-state` only |
-| `--approval deny` | `approval=on-request` | no — `read-state` only |
+| `--approval allow --filesystem workspace` | ACP: `agent-full-access` / `never` / `danger-full-access`; tmux: `never` / `workspace-write` | yes |
+| `--approval allow --filesystem read-only` | ACP: `agent-full-access` / `never` / `danger-full-access`; tmux: `never` / `read-only` | ACP yes; tmux no |
+| `--approval auto` | ACP: `agent` / `on-request` / `workspace-write` | no — `read-state` only |
+| `--approval ask` or legacy `deny` | conservative prompting mode | no — `read-state` only |
+
+Codex ACP mode IDs couple approval and filesystem. Neutral `allow` intentionally
+selects the yolo/`agent-full-access` preset, widening a neutral `workspace` or
+`read-only` filesystem value. Neutral `auto` selects `agent`. An explicit
+`--sandbox` override still wins. Use `--isolation-file` as the outer boundary
+for an ACP role that needs `allow`.
 
 ## 3. Choose permissions from the job, not from a default
 
@@ -77,7 +83,7 @@ user authorizes it, then pick:
   or get the authorization; do not paper over it with a mode that only hides
   the prompt.
 
-Never choose `--filesystem unrestricted`, `--sandbox danger-full-access`, or a
+Never choose an explicit `--filesystem unrestricted`, `--sandbox danger-full-access`, or a
 native `--permission-mode` override without the user asking for it by name and
 understanding what it grants. `harness_options` wins over the neutral block at
 launch, so stating intent in both places and disagreeing is how a role runs on