docs: an Example Plugins page, both languages
The wiki had no catalogue of the example plugins — grepping every page
for `wasm-plugin` returned nothing at all. There are now five of them
across three WIT worlds with five different grant sets, and the only way
to learn what any one did was to open its source.
Adds Example-Plugins / Example-Plugins-zh: what each plugin is for, its
tools, commands and event subscriptions, the grants it needs mapped to
the host imports it actually calls, its world, and its make target. Plus
which one to start from, since "the skeleton to copy" and "the one you
would install" are different plugins and the names do not say so.
Every cell was read out of the sources at nanopi `8dd8ae9` rather than
remembered, which caught two things worth stating on the page:
- `wasm-plugin-minimal` does NOT need `allow_fs`, though its source
declares `host-fs-read` — the declaration is behind
`#[allow(dead_code)]`, LTO drops the unused import, and it is absent
from the built world. The page says to check the component with
`wasm-tools component wit` rather than trust the source, because the
source can over-declare.
- `host-notify` needs no grant at all; it is bounded by a rate limit
rather than a gate, and the host owns the attribution prefix.
Also states plainly that shell hooks are the other half rather than the
lesser option — veto and never-missing-an-event are things only a hook
can do, and plugin event delivery is drop-on-busy — so readers do not
reach for a plugin to build an audit log.
The -zh half additionally covers building behind a restricted network
(cargo mirror, and checking `wasm32-wasip1` in the sysroot rather than
trusting `rustup target list`), following this wiki's split: the Chinese
pages carry that, the English ones never mention it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Dev
committed
Sep 9, 2026