@am_shork/attest 0.8.0 → 0.9.1

package/dist/core/validator.js

@@ -28,6 +28,7 @@ export function uncoveredIssues(registry, plan) {
 }
 /**
  * Static structural validation (design §5.3). Emits ERROR-level issues for:
+ * - empty-spec: the root declares no requirements at all
  * - orphan-test: a scenario covers an unknown requirement id
  * - uncovered-requirement: a requirement has no scenario
  * - unbound-param: a statement placeholder has no matching param
@@ -47,6 +48,27 @@ export function uncoveredIssues(registry, plan) {
 export function validateStructure(registry, plan, unreadable = []) {
     const issues = [];
     const knownIds = new Set(Object.keys(registry));
+    // empty-spec: nothing under this root declares intent, so no finding below is
+    // about a requirement — and the report has no line saying why. It is stated
+    // first because everything else this function can emit against an empty
+    // registry is fallout from it: every scenario in the project is an orphan, and
+    // the diagnosis after 135 of them is a diagnosis nobody reaches.
+    //
+    // Guarded on `unreadable`, which is the same withdrawal the orphan advice
+    // makes below and for the same reason. "Point attest at the directory holding
+    // your *.reqs.ts files" is right for a root that has none, and **wrong** for
+    // one whose registry is sitting right there and failed to load: the files were
+    // found, the fix is the load error already in the report, and following the
+    // hint would move a working path. A registry that could not be read is not an
+    // absent one, and the two take different repairs.
+    if (knownIds.size === 0 && unreadable.length === 0) {
+        issues.push({
+            level: 'ERROR',
+            code: 'empty-spec',
+            message: `No requirements found under this root, so there is no intent here to attest. ` +
+                `Point attest at the directory holding your *.reqs.ts files, or add one.`,
+        });
+    }
     // orphan-test: covers a requirement that does not exist.
     //
     // "Add it to the registry, or fix the id" is the right advice for an id that

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@am_shork/attest",
-  "version": "0.8.0",
+  "version": "0.9.1",
   "description": "TDD-native spec framework: tests are the source of truth for verification, ID-bound requirements the source of truth for intent.",
   "type": "module",
   "engines": {
@@ -25,7 +25,8 @@
     "./define": {
       "types": "./dist/core/registry.d.ts",
       "default": "./dist/core/registry.js"
-    }
+    },
+    "./package.json": "./package.json"
   },
   "files": [
     "dist",