openclaw plugins enable oc-path

```

## Why use it

OpenClaw state is spread across human-edited markdown, commented JSONC config,

and append-only JSONL logs. Shell scripts, hooks, and agents often need one

small value from those files: a frontmatter key, a plugin setting, a log record

field, or a bullet item under a named section.

`openclaw path` gives those callers a stable address instead of a one-off grep,

regex, or parser for each file kind. The same `oc://` path can be validated,

resolved, searched, dry-run, and written from the terminal, which makes narrow

automation easier to review and safer to replay. It is especially useful when

you want to update one leaf while preserving the rest of the file's comments,

line endings, and surrounding formatting.

## Subcommands

| Subcommand | Purpose |

deterministic substrate so byte-fidelity round-trips and the redaction

sentinel guard apply uniformly across kinds.

## Why enable it

Enable `oc-path` when you want scripts, hooks, or local agent tooling to point

at a precise piece of workspace state without inventing a parser for each file

shape. A single `oc://` address can name a markdown frontmatter key, a section

item, a JSONC config leaf, or a JSONL event field.

That matters for maintainer workflows where the change should be small,

auditable, and repeatable: inspect one value, find matching records, dry-run a

write, then apply only that leaf while leaving comments, line endings, and

nearby formatting alone. Keeping this as an opt-in plugin gives power users the

addressing substrate without putting parser dependencies or CLI surface into

core for installs that never need it.

## Where it runs

The plugin runs **in-process inside the `openclaw` CLI** on the host where you