@plurnk/plurnk-schemes 1.15.0 → 1.16.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +1 -1
  2. package/SPEC.md +1 -1
  3. package/package.json +4 -4
package/README.md CHANGED
@@ -85,7 +85,7 @@ static manifest: SchemeManifest = {
85
85
  lineAnchors: true, // publish stable line anchors without EDIT
86
86
  textEditScopes: true, // use the standard text-edit capability
87
87
  glyph: "🦊", // optional client-only display marker
88
- example: "## READ0 (foo://thing/42)", // concise hot-path operation example set
88
+ example: "### READ0 (foo://thing/42)", // concise hot-path operation example set
89
89
  documentation, // deep doc from docs/foo.md, pulled through the skills catalog
90
90
  };
91
91
  ```
package/SPEC.md CHANGED
@@ -51,7 +51,7 @@ class Notes {
51
51
  | `textEditScopes?` | `true` declares the shared textual EDIT coordinate and collision contract. For model-writable schemes it implies `lineAnchors`; handlers receive only numeric coordinates and route standard entry mutation through `ctx.entries.operations.editBatch`. |
52
52
  | §manifest-metadata-modifier `metadataModifier?` | `true` declares that the scheme owns the opaque, ordered `{metadata}` modifier. Absent/false rejects it before handler invocation. |
53
53
  | §manifest-capability-traits `traits?` | Unique lowercase capability facts (for example `web` or `interaction`). The scheme declares facts only; the consumer's general capability-policy cascade decides admission. |
54
- | `example?` | The scheme's concise **hot-path** operation example set (e.g. `"## READ0 (foo://thing/42)"`) — renders in the live resource catalogue every turn. One or more complete operations may be separated by blank lines; keep semantics in `documentation`. Omit → not advertised. |
54
+ | `example?` | The scheme's concise **hot-path** operation example set (e.g. `"### READ0 (foo://thing/42)"`) — renders in the live resource catalogue every turn. One or more complete operations may be separated by blank lines; keep semantics in `documentation`. Omit → not advertised. |
55
55
  | `documentation?` | The **deep doc** (semantics / channels / edge cases), with an exact H2 `Summary` for discovery. Consumer materializes it as a pull-able `worker://~/_plurnk/plurnk/<name>.md` entry READ on demand; never hits the hot path. Analogous to executor supplemental `details`. |
56
56
  | §manifest-client-display `glyph?` | Non-empty opaque client presentation glyph. It is projected through {§client-display-capabilities}; omission delegates identity fallback to the client. It never enters model teaching. |
57
57
  | `foldedByDefault?` | Entries land FOLDED, off the ranked manifest surface (READable via address, not poured into the ranked view). For executor-output streams (`<tag>://`) — containment one level up. Absent/false → ranked/first-class. |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@plurnk/plurnk-schemes",
3
- "version": "1.15.0",
3
+ "version": "1.16.1",
4
4
  "description": "Framework + contract for the @plurnk/plurnk-schemes-* URI handler packages.",
5
5
  "keywords": [
6
6
  "plurnk",
@@ -49,10 +49,10 @@
49
49
  "prepack": "npm run build"
50
50
  },
51
51
  "peerDependencies": {
52
- "@plurnk/plurnk-mimetypes": "^1.15.0"
52
+ "@plurnk/plurnk-mimetypes": "^1.16.1"
53
53
  },
54
54
  "dependencies": {
55
- "@plurnk/plurnk-contracts": "1.15.0",
56
- "@plurnk/plurnk-meta": "1.15.0"
55
+ "@plurnk/plurnk-contracts": "1.16.1",
56
+ "@plurnk/plurnk-meta": "1.16.1"
57
57
  }
58
58
  }