eidosmd 0.1.0 → 0.2.0

package/instructions/validating.md

@@ -1,6 +1,6 @@
 ## Validating blueprints
 
-Validation is framework-defined. `eidos check` reads the root's own `_eidos/Framework.yaml` and shapes and enforces those, never a contract of its own.
+Validation is framework-defined. `eidos check` reads the root's own `.eidos/Framework.yaml` and templates and enforces those, never a contract of its own.
 
 ```bash
 eidos check                      # the whole root: framework, layout, every blueprint
@@ -13,8 +13,8 @@ Exit code 0 means no errors; 1 means at least one error (or, with `--strict`, an
 
 ### What the levels mean
 
-- An **error** is wrong on any reading: frontmatter that does not parse, a missing `id` or `title`, an `id` that is not kebab-case or is used twice, a `flavor` the collection does not declare, a link to a file that does not exist, a shape file the framework points at but does not have.
-- A **warning** is a gap the standard says to note and offer, never refuse: a missing or empty property the Schema applies to this collection, a property the Schema does not declare, a work-tracking field, a body section the flavor's shape declares but the blueprint lacks, a section the shape does not know, sections out of the shape's order, a grouping value that does not match its folder, a declared frame nobody has written, a stale `index.md`, a version gap.
+- An **error** is wrong on any reading: frontmatter that does not parse, a missing `id` or `title`, an `id` used twice (its form is free: a slug, a number, a GUID), a `variant` the collection does not declare, a link to a file that does not exist, a template file the framework points at but does not have.
+- A **warning** is a gap the standard says to note and offer, never refuse: a missing or empty property the Properties table applies to this collection (every block of it: the core, yours, a tool's), a property no block declares, a work-tracking field, a body section the variant's template declares but the blueprint lacks, a section the template does not know, sections out of the template's order, a grouping value that does not match its folder, a declared frame nobody has written, a stale index, a version gap, a near-miss the Vocabulary names (`term-near-miss`, with the declared term beside it).
 
 ### Reporting a review
 
@@ -25,9 +25,10 @@ The output is a review the owner acts on. When you report:
 - Offer to add a missing core property with a note on why it exists; never refuse the file.
 - Confirm no work-tracking fields crept in, and that any section describing approach reads as intent, not progress.
 - A version gap is worth one line and an offer to migrate, once per session; then carry on with the framework as it stands.
+- A `term-near-miss` is a suggestion: name the declared term, ask, and leave the word to the owner. Never swap it in.
 
 Do not fix silently. Show the finding, propose the change, and let the owner decide, unless the change is purely mechanical and they have asked for it (regenerating an index, adding a blank property stub).
 
 ### Things `check` cannot judge
 
-Whether the prose is true, whether the scope is right, and whether an open question should be settled are the owner's. `check` tells you the file is well-formed against its framework; it says nothing about whether the thing described is the thing they mean. Read the blueprint with the frames in mind and raise what does not fit.
+Whether the prose is true, whether the scope is right, and whether an open question should be settled are the owner's. `check` tells you the file is well-formed against its framework; it says nothing about whether the product described is the one they mean. Read the blueprint with the frames in mind and raise what does not fit.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eidosmd",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "The Eidos CLI: scaffold, validate, index, and browse a root of Eidos blueprints, and hand any agent the workflow it needs to work in one.",
   "keywords": [
     "eidos",
@@ -25,7 +25,7 @@
   },
   "files": [
     "dist/src",
-    "browser",
+    "browser/dist",
     "instructions",
     "standard",
     "NOTICE"
@@ -33,21 +33,30 @@
   "engines": {
     "node": ">=20"
   },
+  "scripts": {
+    "build": "tsc -p tsconfig.json && vite build browser",
+    "clean": "node -e \"require('node:fs').rmSync('dist', { recursive: true, force: true })\"",
+    "test": "pnpm build && node --test \"dist/test/**/*.test.js\"",
+    "check": "tsc -p tsconfig.json --noEmit && tsc -p browser/tsconfig.json --noEmit",
+    "prepublishOnly": "pnpm clean && pnpm test",
+    "sync-standard": "node scripts/sync-standard.mjs",
+    "build:browser": "vite build browser",
+    "dev:browser": "vite browser"
+  },
   "dependencies": {
     "commander": "^14.0.0",
     "marked": "^18.0.13",
     "yaml": "^2.8.0"
   },
   "devDependencies": {
+    "@preact/preset-vite": "^2.10.6",
     "@types/node": "^22.0.0",
-    "typescript": "^5.9.0"
+    "@types/react": "^19.3.0",
+    "@types/react-dom": "^19.3.0",
+    "html-to-image": "^1.11.13",
+    "preact": "^10.29.8",
+    "typescript": "^5.9.0",
+    "vite": "^8.3.0"
   },
-  "bugs": "https://gitlab.com/the-virtual-panda/eidosmd/-/issues",
-  "scripts": {
-    "build": "tsc -p tsconfig.json",
-    "clean": "node -e \"require('node:fs').rmSync('dist', { recursive: true, force: true })\"",
-    "test": "pnpm build && node --test \"dist/test/**/*.test.js\"",
-    "check": "tsc -p tsconfig.json --noEmit",
-    "sync-standard": "node scripts/sync-standard.mjs"
-  }
-}
+  "bugs": "https://gitlab.com/the-virtual-panda/eidosmd/-/issues"
+}