@qvac/skills 0.1.0 → 0.1.1

package/README.md

@@ -1,15 +1,13 @@
-# qvac-skills
+# @qvac/skills
 
-Skills for the QV.AC app.
+Skills for QV.AC.
 
-A skill is a directory under `skills/` holding a `SKILL.md` — YAML front matter
-plus a `metadata` JSON block the harness parses into a catalog entry — and
-whatever it needs beside it: `references/*.md`, `scripts/*.py`,
-`*.applescript`, `cli.schema.json`.
+A skill is a directory under `skills/` with a `SKILL.md` in it, plus whatever
+else it needs alongside — reference notes, scripts, a schema. The `SKILL.md`
+front matter is what the harness reads to build its catalog.
 
-This package ships that tree **and** a content-addressed bundle of it, so a
-consumer without a filesystem (a Bare worklet) gets the same bytes as one that
-reads `node_modules` directly.
+The package ships the tree itself and a bundled copy of it, so consumers that
+can't read a filesystem still get the same bytes.
 
 ## Entry points
 
@@ -20,29 +18,22 @@ reads `node_modules` directly.
 | `@qvac/skills/hash`     | `SKILLS_HASH` alone                      | no                 |
 | `@qvac/skills/skills/*` | a single file by path                    | no                 |
 
-Every entry loads under Node and Bare alike, but `skillsDir` only points at
-something real where this package was installed to disk. A Bare worklet ships no
-`node_modules`, so it imports `./bundled` and materializes a tree instead.
+All of them work on Node and Bare. `skillsDir` only points at anything real
+where the package was installed to disk, though — a Bare worklet ships no
+`node_modules`, so it imports `./bundled` and writes the tree out itself.
 
-`bundled.js` and `hash.js` are generated from `skills/` by `scripts/build.mjs`
-on `prepack`. They are gitignored: the published artifact is always built from
-the tree beside it, so the bundle and the tree cannot disagree.
-
-`SKILLS_HASH` is sha256 over the sorted `path\0content\0` stream, truncated to
-16 hex chars. It is the content address consumers key a materialized directory
-on, so it must match `hashBundledSkills` in the harness byte for byte.
-
-## Release
+`SKILLS_HASH` is a sha256 over the sorted `path\0content\0` stream, truncated
+to 16 hex chars. Consumers key a materialized directory on it, so it has to
+match `hashBundledSkills` in the harness byte for byte.
 
-Bump `version`, tag `v<version>`, push the tag. `.github/workflows/publish.yml`
-publishes to npmjs through OIDC trusted publishing, so there is no token to
-rotate.
+## Development
 
-```
-npm version patch && git push --follow-tags
+```sh
+npm test     # node + bare
+npm run lint
 ```
 
-Consumers pin a version; nothing resolves a moving ref.
+`bundled.js` and `hash.js` are generated from `skills/` by `scripts/build.mjs`
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qvac/skills",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Skills for the QV.AC app — the SKILL.md tree plus a content-addressed bundle of it.",
   "type": "module",
   "main": "index.js",