4 Commits

Include renames

Author	SHA1	Message	Date
4 people	e2f41eb60e	docs(openclaw): switch to canonical env-var-reference apiKey + olp-claude rename + /models menu-only note (#64) ... Three corrections to PR #63 surfaced via live Telegram bot bring-up on Mac mini -> PI231 OLP: 1. headers.Authorization workaround does NOT work for openai-shape model ids. PI231 audit log showed key_id=__anonymous__ for every gpt-* model sent via olp-codex despite headers.Authorization being set. Canonical OpenClaw pattern is apiKey: dollar-brace VAR brace env-var reference (per docs.openclaw.ai). Verified end-to-end: this attributes both olp-claude/* and olp-codex/* traffic to the bot owner key. Root cause: two unresolved upstream openclaw bugs: - #41157 (Gemini openai-completions Authorization not sent) - #1669 (Ollama provider ignores apiKey) 2. claude-local renamed to olp-claude for naming symmetry with olp-codex. 3. /models is menu-only in OpenClaw. Typing /models olp-codex/gpt-5.5 does NOT directly switch -- only opens the picker. Changes: - Two-modes table: client-mode Auth row now recommends env-var-ref apiKey - Mode B: NEW step walks through env var setup per OS - Provider JSON examples use VAR ref pattern (no more headers.Authorization) - Gotchas rewritten with three failure modes documented - New gotcha for /models menu-only semantics - Troubleshooting table: updated 401 row + new rows for anonymous attribution + menu-only Authority: Live reproduction on Mac mini OpenClaw v2026.5.22 + PI231 OLP v0.5.1. PI231 audit log verification. OpenClaw issues #41157, #1669, #29095. Co-authored-by: dtzp555 <dtzp555@gmail.com> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-27 16:57:46 +10:00
4 people	5d60a0599f	docs(openclaw): expand integration guide — server-co-located vs client-mode + codex-via-OLP recipe (#63) ... The previous version of docs/integrations/openclaw.md assumed loopback OpenClaw+OLP co-located on the same host. Two real gaps: 1. **Client-mode (OpenClaw on a different machine than OLP) is the common family-deployment shape**, and the loopback config recipe doesn't work there. Specifically: - apiKey field is silently overridden by OpenClaw's service-managed env (`OPENCLAW_SERVICE_MANAGED_ENV_KEYS=DEEPSEEK_API_KEY,OPENAI_API_KEY`). The OpenClaw gateway clobbers `process.env.OPENAI_API_KEY` with whatever ChatGPT key it's been authed against, so when an openai-completions provider falls back to env-var auth, the wrong token gets sent and OLP rejects with 401. - The escape hatch is `headers.Authorization: Bearer olp_...` in the provider config, which beats the env fallback because OpenClaw merges `providerConfig.headers` at request-build time (sanitizeModelHeaders → outgoing request). 2. **codex / OpenAI models via OLP routing wasn't documented at all.** OpenClaw's stock `openai-codex` provider talks to ChatGPT directly (bypasses OLP, no audit, no per-key tracking). To get gpt-5.5 / gpt-5.3-codex etc. routed through OLP for per-key observability, you have to register a custom `olp-openai` provider — recipe now included. Changes to docs/integrations/openclaw.md: - Restructured into Mode A (server-co-located) vs Mode B (client-mode) with explicit "pick yours" table up top. - Mode B fully written out — proxyUrl with server IP, headers.Authorization override, claude-local provider listed with the three Claude IDs that OLP's /v1/models actually exposes. - New § "Using codex / OpenAI models through OLP" with olp-openai provider recipe + agents.defaults.models alias examples + warning about why NOT to use OpenClaw's stock openai-codex provider. - New § Gotchas covering: OPENCLAW_SERVICE_MANAGED_ENV_KEYS clobber, default-agent-model points-at-removed-provider, /new doesn't reset model selection, the openclaw.extensions schema-drift (was already there). - New § Troubleshooting table mapping symptoms → root causes → fixes. Discovered live on Mac mini 2026-05-27 during PI231-as-server topology bring-up. The "apiKey shadowed by env" finding required reading OpenClaw source (`/opt/homebrew/lib/node_modules/openclaw/dist/...`) to confirm the `providerConfig.headers` precedence. Verified end-to-end: Telegram bot now routes free-text through claude-local → PI231 OLP → claude spawn → reply; and `/models olp-openai/gpt-5.5` switches to codex via OLP with per-key audit visible on dashboard. Co-authored-by: dtzp555 <dtzp555@gmail.com> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-27 16:10:55 +10:00
4 people	ea0392f744	fix(olp-plugin): add openclaw.extensions field for modern OpenClaw v2026.5+ install (#62) ... Discovered 2026-05-27 while bringing up Mac mini as OpenClaw client of PI231 OLP server: `openclaw plugins install ./olp-plugin/` fails with package.json missing openclaw.extensions; update the plugin package to include openclaw.extensions (for example ["./dist/index.js"]) OpenClaw v2026.5.22 enforces a stricter plugin-manifest validation than earlier revisions. The olp-plugin/package.json still used the legacy schema (`type: "plugin"` + `pluginManifest`) without the new `extensions: [./index.js]` field that modern OpenClaw requires for the gateway plugin-discovery loop. Workaround until this fix lands: manually `cp -R olp-plugin ~/.openclaw/extensions/olp` (symlink also works per docs Option B). Changes: - olp-plugin/package.json: added `extensions: ["./index.js"]` to the openclaw block. Keeps legacy fields (`type`, `id`, `pluginManifest`) for backwards compat with pre-2026.5 OpenClaw revisions; the modern loader only reads `extensions`. - docs/integrations/openclaw.md: - § 3 Configure: rewrote example to show the modern `plugins.allow` + `plugins.entries.olp.{enabled, config}` schema. The previous shape (`plugins.olp.{proxyUrl, apiKey}` at top level) doesn't match what OpenClaw actually picks up. - § Known issues: added a paragraph documenting the `openclaw.extensions` schema-drift event + recovery path (pull latest OLP, or symlink fallback). Verified post-fix: `openclaw plugins install ./olp-plugin/` succeeds on Mac mini OpenClaw v2026.5.22. Authority: - Reproduced live on Mac mini 2026-05-27 during PI231-as-server topology bring-up - OpenClaw stock plugin format (sample: `/opt/homebrew/lib/node_modules/ openclaw/dist/extensions/anthropic/package.json` uses `extensions: ["./index.js"]`) Co-authored-by: dtzp555 <dtzp555@gmail.com> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-27 14:29:35 +10:00
4 people	53afea47ca	feat+test+docs: D71+D72+D73 — olp-plugin/ (OpenClaw /olp Telegram+Discord) + docs/integrations/*.md + README cross-refs (#44) ... Final Phase 4 substantive D-day group. 3 D-days bundled per Iron Rule 11 IDR (plugin consumes existing endpoints; integration docs reference plugin + olp CLI + olp-connect together; README index links all). After this PR merges, Phase 4 has shipped all 5 D-day groups (D60 charter + port / D61-D63 SSE heartbeat+ring+/status / D64-D67 olp CLI+doctor / D68-D70 olp-connect+anonymous-key+ADR0011 / D71-D73 plugin+docs). The v0.4.0 close PR is maintainer-triggered per CLAUDE.md release_kit overlay. ## D71 — olp-plugin/ (OpenClaw gateway plugin) Port OCP ocp-plugin/index.js (311 lines) → OLP olp-plugin/index.js (482 lines) as the /olp Telegram+Discord slash command, but MINUS mutations (no /olp keys keygen, no /olp keys revoke, no /olp restart, no /olp logs — all of these require SSH out of chat for security). Plugin shape: - olp-plugin/index.js — registers /olp command via OpenClaw api.registerCommand - olp-plugin/openclaw.plugin.json — manifest, apiKey REQUIRED, proxyUrl default http://127.0.0.1:4567 (matches D60) - olp-plugin/package.json — minimal: name/version/type:module + OpenClaw discovery block - olp-plugin/README.md — install + configure + use docs; documents the "no mutations from chat" security stance and the dedicated-bot-key pattern (don't share maintainer's personal key with the bot) Subcommand parity with olp CLI (D64-D67): - /olp status → GET /v0/management/status (owner-only) - /olp health → GET /health (public-ok) - /olp usage → GET /v0/management/dashboard-data (owner-only) - /olp models → GET /v1/models (public-ok) - /olp cache → GET /cache/stats (owner-only) - /olp providers → local cross-ref (public-ok) - /olp chain show [<model>] → local (public-ok, advisory if no FS access — defer to ssh + olp chain show) - /olp doctor → informational (HTTP doctor endpoint deferred; advisory to ssh + olp doctor for live use) - /olp help → usage text Port resolution: OLP_PROXY_URL env → OLP_PORT env → plugin config proxyUrl → http://127.0.0.1:4567. Output: Telegram/Discord monospace code block with status icons (🟢🟡🔴). Long responses truncated for the 4096-char message limit. No npm deps. OpenClaw provides Telegram/Discord transport; plugin uses fetch + node builtins only. ## D72 — docs/integrations/*.md (6 IDE pages + index) Per the Phase 4 brainstorm prior-art survey + ADR 0010 § Out-of-scope posture for Claude Code: - continue.md ✅ — config.yaml (NOT config.json); apiBase; requestOptions.headers - cline.md ✅ — "OpenAI Compatible" provider; Cline #7128 base-URL UI bug warning - cursor.md ⚠️ — known base-URL fragility; only enable models OLP serves - aider.md ✅ — OPENAI_API_BASE env + openai/ prefix; .env support - claude-code.md ❌ — explicitly NOT supported per ADR 0010 § /v1/messages defer rationale; recommended alternative: Cline + OLP - openclaw.md ✅ — install olp-plugin via CLI or symlink; configure apiKey; restart gateway Each ~60-120 lines: status / quick setup / known issues / OLP-specific notes / test-it command. docs/integrations/README.md is the index. ## D73 — README cross-references - New § "IDE Setup" links to docs/integrations/README.md - New § "Telegram / Discord Usage" — install + configure + restart + use - Quick Start mentions olp-connect <ip> as family-onboarding command - package.json `files` field extended to include olp-plugin/ so the published tarball ships the plugin ## Test count 672 → 696 (+24 D71-D73 tests in Suite 35: helpers / formatters / dispatch / error paths). All 696 pass locally. ## Scope discipline - server.mjs UNTOUCHED (plugin consumes EXISTING endpoints) - No new npm deps (no Telegram or Discord SDK — OpenClaw provides transport) - No /v1/messages (out of Phase 4 per ADR 0010) - No CHANGELOG / package.json version bump (Phase 4 close handles versioning; only package.json `files` extended for olp-plugin/ publication) ## Implementor flagged for reviewer 1. /olp doctor returns SSH advisory (no HTTP doctor endpoint yet). When future phase exposes /v0/management/doctor, swap advisory branch for real fetchJSON + fmtDoctor (already implemented + tested). 2. /olp providers + chain show have no FS access (plugin runs in OpenClaw gateway process); registry read via lazy-imported models-registry.json from repo root. For live enabled-state visibility users still need /olp status (owner-tier) or ssh + olp providers / olp chain show. 3. No live-server wire test in Suite 35 — existing Suites 31/32 already cover the integration path against the same endpoints; mock-fetch in Suite 35 is sufficient signal for the plugin layer. ## Authority - ADR 0010 § Phase 4 D-day plan D71-D73 line - OCP ocp-plugin/index.js (port reference) - ADR 0010 § Out-of-Phase-4-scope (claude-code.md ❌ rationale) - 2026-05-26 brainstorm (Top OCP inheritance candidates + prior-art survey IDE-specific quirks for cline/cursor/continue docs) Co-authored-by: dtzp555 <dtzp555@gmail.com> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-26 09:35:23 +10:00