@plurnk/plurnk-schemes 3.3.0 → 3.3.2

package/README.md

@@ -9,7 +9,7 @@ Framework + contract for `@plurnk/plurnk-schemes-*` URI handler packages. Consum
 
 ## Write a scheme
 
-Ship a scheme by publishing a package — **under any scope** (`@acme/whatever`; discovery keys on `plurnk.kind`, not the `@plurnk` scope) — that declares itself and default-exports a `SchemeHandler`. Install it and it lights up; there is no first-party allow-list (scope-agnostic discovery, SPEC §6).
+Ship a scheme by publishing a package — **under any scope** (`@acme/whatever`; discovery keys on `plurnk.kind`, not the `@plurnk` scope) — that declares itself and default-exports a `SchemeHandler`. Install it and it lights up; there is no first-party allow-list (scope-agnostic discovery, {§scheme-discovery}).
 
 ### 1. Declare in `package.json`
 
@@ -60,10 +60,10 @@ them or author COPY/MOVE effect envelopes. A regional `editBatch`
 returns `EditBatchResult` with its typed `EditBatchReceipt`; the engine validates
 and projects it.
 The optional synchronous `attributions(context)` hook may return no, one, or
-many opaque tags for each provider emission attempt ({§extension-attribution}).
+many opaque tags for each provider emission attempt ({§extension-discovery}).
 `implements SchemeHandler` gives compile-time signature checking. The statement
 and path types (`FindStatement`, `SendStatement`, `UrlPath`, etc.) are re-exported
-from this package, so you depend on and peer (`^1`) only
+from this package, so you depend on and peer (`^3.0.0`) only
 `@plurnk/plurnk-schemes`; grammar rides underneath.
 
 ### 3. Declare the manifest — including self-doc
@@ -89,7 +89,7 @@ static manifest: SchemeManifest = {
 };
 ```
 
-- **`documentation`** — the **deep doc** (ops, channels, edge cases) with an exact H2 `Summary`. The consumer materializes it as a pull-able `worker:///_plurnk/plurnk/<name>.md` entry: FIND catalogs the summary and the model READs the body on demand, off the hot path. It is analogous to executor supplemental `details`. **Convention:** keep it in a **`docs/<name>.md`** file (root) and load it at module init with the snippet above — `../` resolves the same from `src/` (test) and `dist/` (built); add `docs/**/*` to `files`. A missing file fails-hard at import.
+- **`documentation`** — the **deep doc** (ops, channels, edge cases) with an exact H2 `Summary`. The consumer materializes it as a pull-able `plurnk:///<name>.md` entry: FIND catalogs the summary and the model READs the body on demand, off the hot path. It is analogous to executor supplemental `details`. **Convention:** keep it in a **`docs/<name>.md`** file (root) and load it at module init with the snippet above — `../` resolves the same from `src/` (test) and `dist/` (built); add `docs/**/*` to `files`. A missing file fails-hard at import.
 - **`glyph`** — optional opaque client display metadata. It is discoverable through the client capability wire and never rendered into model teaching; clients choose fallback, fonts, and theme.
 
 Declare `lineAnchors: true` when stable textual representations should publish
@@ -123,8 +123,8 @@ That's the whole contract: declare, `implements SchemeHandler`, manifest with se
 - `PathMimetype.resolve(pathname, default, mimetypes)` — path-extension mimetype resolver.
 - `Matcher.matchAgainstContent(body, content, mimetype, mimetypes)` - boolean resource selection over `Mimetypes.query` (glob/regex/jsonpath/xpath), returning locator/exact-region `MatchEvidence`.
 - `Results.problem` / `.failure` / `.assert` / `.assertReadResult` / `.assertMatchEvidenceList` / `.attachInstance` / `.isEntry` / `.isProposal` / `.isPassthrough` / `.isErrorStatus` - RFC 9457 result builders, validators, durable-occurrence attachment, and guards.
-- `PacketSections.assertDrafts(value, subject?)` — validates the exact tokenless section-draft list returned by a packet transformer.
-- `SchemeDiscovery.discover({ cwd? })` — scope-agnostic `node_modules` scan for `plurnk.kind:"scheme"` packages (trust-gated, fail-hard on prefix collision); returns descriptors plus canonical static attribution lists for represented packages (SPEC §6, {§extension-attribution}).
+- `PacketSections.assertDrafts(value, subject?)` — validates the exact unweighted section-draft list returned by a packet transformer.
+- `SchemeDiscovery.discover({ cwd? })` — scope-agnostic `node_modules` scan for `plurnk.kind:"scheme"` packages (trust-gated, fail-hard on prefix collision); returns descriptors plus canonical static attribution lists for represented packages ({§scheme-discovery}, {§extension-discovery}).
 
 `SchemeCtx` is the stable semantic API for trusted in-process schemes, not a
 sandbox. The consumer injects its implementation; database layout and private