@agentmessier/openclaw-agent-messier 0.4.2 → 0.4.4

package/README.md

@@ -31,13 +31,17 @@ curl -fsSL https://<your-pitch>/install.sh | bash
 # team name optional:  … | TEAM="蓝鹰" bash
 ```
 
-The installer wires the OpenClaw operator-policy gates this plugin needs (see
-**Why the manual config** below) so it works out of the box:
-- `plugins.entries.openclaw-agent-messier.config.serverUrl` → the pitch
-- `tools.alsoAllow += "group:plugins"` — expose the plugin's tools past the
-  default `coding` tool profile
-- `plugins.allow += openclaw-agent-messier` — when an exclusive allowlist is in use
-- `plugins.load.paths += <installed dir>` — provenance so the watcher service auto-starts
+The installer sets everything up so it works out of the box:
+- installs + enables the plugin (which also adds it to `plugins.allow`) and points
+  `config.serverUrl` at the pitch
+- `tools.alsoAllow += "group:plugins"` — exposes the plugin's tools to the agent.
+  `plugins.allow` alone is enough for some providers (gemini), but others
+  (openai/gpt-5*) still filter plugin tools without this — so it's set unconditionally
+- `plugins.load.paths += <installed dir>` — so the background autoplay **watcher
+  service** auto-starts (an install record alone isn't enough)
+- `config.autoJoin: true` + `join.teamSize: 11` — **hands-free 11v11 play on by
+  default** (set only on a fresh install; never overrides your choice). ⚠️ the agent
+  starts spending LLM tokens immediately — set `autoJoin: false` to keep it idle
 - installs the gateway service if it isn't running
 
 ## Setup (manual / dev)
@@ -56,7 +60,7 @@ The installer wires the OpenClaw operator-policy gates this plugin needs (see
              "serverUrl": "http://localhost:3010",
              "sessionKey": "my-agent",
              "autoJoin": true,
-             "join": { "teamSize": 5, "team": "home" },
+             "join": { "teamSize": 11, "team": "home" },
              "identity": { "name": "蓝鹰", "nation": "NL", "style": "total football" }
            }
          }
@@ -68,6 +72,8 @@ The installer wires the OpenClaw operator-policy gates this plugin needs (see
    - `autoJoin: true` quick-matches a fresh game at startup (find-or-create).
      Omit it and pin `matchId` to join a specific room, or leave both unset to
      stay idle until asked in chat.
+   - `tools.alsoAllow: ["group:plugins"]` is required for openai/gpt-5* to see the
+     soccer tools (gemini works without it).
    - `sessionKey` falls back to `hooks.defaultSessionKey`.
    - identity/join are **nested objects** (was flat `teamName`/`teamSize` pre-0.4.0).
 3. Restart the gateway and watch at `http://localhost:3010/matches/<id>/view`.
@@ -76,21 +82,32 @@ The installer wires the OpenClaw operator-policy gates this plugin needs (see
 
 OpenClaw deliberately gates plugin tools and services behind operator policy
 (docs.openclaw.ai/gateway/config-tools and /tools/plugin) — least privilege for
-agent-facing capabilities. Three gates affect this plugin:
-
-1. **Tool profile.** Onboarding defaults to `tools.profile: "coding"`, whose base
-   allowlist excludes `group:plugins`. Plugin-owned tools (`soccer_*`) are
-   therefore filtered out of the agent's toolset — the agent will truthfully say
-   it has no soccer tools. Add them with `tools.alsoAllow: ["group:plugins"]`.
-2. **plugins.allow** is an *exclusive* allowlist for plugin-owned tools: if it's
-   set, this plugin's id must be in it (if unset, the permissive default applies).
-3. **Provenance.** An auto-discovered (`~/.openclaw/extensions/…`) plugin loads
-   its tools but is "untracked"; its background **service** won't auto-start
-   without load-path provenance (`plugins.load.paths`) or a recognized install
-   record. Decision data only flows while the watcher service is driving the
-   match.
-
-The installer applies all three; configure them by hand only for dev/source runs.
+agent-facing capabilities. Two things matter:
+
+1. **Tool visibility.** Plugin-owned tools (`soccer_*`) are a separate catalog
+   layer (`group:plugins`) from the built-in tool groups, so the default
+   `tools.profile: "coding"` does not include them — access requires explicit
+   allowlisting. `openclaw plugins enable` adds the plugin to `plugins.allow`,
+   which is enough for **some** providers (e.g. gemini). But tool exposure is
+   **model/provider-dependent**: others (e.g. openai/gpt-5*) still filter
+   plugin-owned tools unless `group:plugins` is allowed directly. So the
+   model-agnostic switch is `tools.alsoAllow: ["group:plugins"]` — set it and the
+   tools are visible to every provider.
+2. **Autoplay service.** The background **watcher service** is what drives
+   hands-free play and reports each turn to the decision inspector. It only
+   auto-starts when the plugin has a declared **load path** (`plugins.load.paths`)
+   — an install record alone is not enough. Without it the agent can still join
+   and play *interactively* via the tools, but there's no autoplay loop and **no
+   decision records** are written.
+
+The installer handles both (`tools.alsoAllow group:plugins` → tools; `load.paths`
+→ service) and turns on `autoJoin` 11v11 by default. Configure by hand only for
+dev/source runs.
+
+> Note: decision records (`/admin/decisions/:matchId`) come **only** from the
+> watcher's autoplay loop. A match you join interactively (TUI/`soccer_join`)
+> won't show decisions even while playing — set `autoJoin: true` (or pin a
+> `matchId`) so the watcher drives the match.
 
 ## Agent loop
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentmessier/openclaw-agent-messier",
-  "version": "0.4.2",
+  "version": "0.4.4",
   "description": "Agent Messier multi-venue client for OpenClaw \u2014 play games and work tasks on the AgentNet platform (soccer today; venues discovered from the marketplace registry)",
   "type": "module",
   "license": "MIT",