@veryfront/ext-yaml 0.1.1227 → 0.1.1229

package/README.md

@@ -13,8 +13,8 @@ Veryfront core owns the `SKILL.md` frontmatter envelope, document limits,
 mapping-root validation, immutable snapshots, and Skill metadata policy. This
 extension receives only the YAML source between the delimiters and returns the
 decoded, untrusted value. Keeping that boundary narrow prevents YAML parser
-details and third-party dependencies from entering core — core may depend on
-the Deno standard library and nothing else, so the parser has to live here.
+details and third-party dependencies from entering core. Core may depend on
+the Deno standard library and nothing else, so the parser must live here.
 
 ## YAML version
 

package/esm/src/adapter.js

@@ -3,8 +3,8 @@ import { createSkillDocumentParserProvider, createYamlParserProvider, } from "ve
 /**
  * The tags a JSON-representable document may carry explicitly. `yaml`'s
  * `Schema.knownTags` fallback resolves YAML 1.1 tags such as `!!binary`,
- * `!!timestamp`, `!!set` and `!!omap` even under the 1.2 core schema, and does
- * so without raising a warning — so the parser options alone cannot express
+ * `!!timestamp`, `!!set` and `!!omap` even under the 1.2 core schema without
+ * raising a warning, so the parser options alone cannot express
  * `@std/yaml`'s JSON schema. Rejecting every other explicit tag does.
  */
 const JSON_SCHEMA_TAGS = new Set([

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@veryfront/ext-yaml",
-  "version": "0.1.1227",
+  "version": "0.1.1229",
   "description": "Veryfront first-party extension package for ext-yaml",
   "keywords": [
     "veryfront",
@@ -50,7 +50,7 @@
     "yaml": "2.9.0"
   },
   "peerDependencies": {
-    "veryfront": "^0.1.1227"
+    "veryfront": "^0.1.1229"
   },
   "type": "module",
   "types": "./esm/src/index.d.ts",