#18791: docs: add FogClaw plugin docs for official OpenClaw listing

## Summary This PR submits FogClaw for official OpenClaw plugin intake by adding its plugin documentation and providing reproducible validation evidence for the already-merged `@openclaw/fogclaw` package. The PR does **not** introduce new runtime behavior changes; plugin logic and scanning/redaction implementation already merged in `DataFog/fogclaw` on main. ## What changed - Add docs page: `docs/plugins/fogclaw.md` - install command: `openclaw plugins install @openclaw/fogclaw` - plugin behavior, tools, and config highlights - manifest/extension identity details (`@openclaw/fogclaw`, `id: fogclaw`, `extensions: ["./dist/index.js"]`) ## Scope boundary - No code changes to scanner/redaction logic. - No changes to GLiNER model loading/regex behavior. - No changes to `src/index.ts`, tests, or package runtime code. - Evidence collection only, plus plugin-facing documentation. ## Why this matters FogClaw provides a stable, opt-in privacy guardrail plugin for OpenClaw and now needs upstream documentation/visibility so it can be discovered and installed through standard OpenClaw plugin flows. ## Security impact - New permissions/capabilities? **No** (documentation-only PR) - Secrets/tokens handling changed? **No** - New/changed network calls? **No** - Command/tool execution surface changed? **No** - Data access scope changed? **No** - If any `Yes`, explain risk + mitigation: **Not applicable** ## Evidence (reproducible) Run from a clean checkout of the upstream-merged plugin state: ```bash npm test pnpm build npm run test:plugin-smoke npm pkg get openclaw node - <<'NODE' import plugin from './dist/index.js'; console.log(`${typeof plugin.register === 'function'} ${plugin.id} ${plugin.name}`); NODE ``` Observed outputs: - `npm test`: **pass** (`101` tests, `0` failures) - `pnpm build`: **pass** - `npm run test:plugin-smoke`: **pass** (`3` tests) - `npm pkg get openclaw`: returns: ```json { "extensions": [ "./dist/index.js" ] } ``` - Node import smoke: ```text true fogclaw FogClaw ``` Example command for installability path under the docs: ```bash openclaw plugins install @openclaw/fogclaw ``` (Installability note: package identity is set to `@openclaw/fogclaw` in manifest/package metadata; package manager/registry behavior should be validated by maintainers as part of release/publish steps.) ## Repro + verification - Environment - OS: macOS / Linux - Runtime: Node 22+ - Model/provider: none required - Relevant config: none required - Steps 1. Validate plugin tests/coverage and smoke checks above. 2. Confirm `package.json#openclaw.extensions` and manifest consistency. 3. Confirm this PR only adds `docs/plugins/fogclaw.md`. - Expected - Deterministic green checks for test/build/import evidence. - PR provides concrete package identity and installation guidance. - Actual - As expected (above). ## Risks and mitigations - Risk: package discoverability relies on upstream maintainer-controlled publish cadence. - Mitigation: PR is scoped to documentation and explicit manifest identity so maintainers can pair it with release/publish actions. ## Human verification - Verified commands and outputs above. - Edge checks performed: `npm pkg get openclaw` and runtime import smoke from `dist/index.js`. - What not verified: end-to-end OpenClaw publish+install from remote registry (outside this repository scope).