@metaobjectsdev/sdk 0.23.0 → 0.23.1

package/agent-context/skills/metaobjects-authoring/references/requirements.md

@@ -47,9 +47,15 @@ line: *would this sentence have to change if the code changed but the model did
 is `notes`.
 
 **Hierarchy is nesting, and links live at the bottom.** L1 solution, L2 segment, L3
-service — these never reference the model. **L4** binds an object, **L5** binds a field,
-view or identity. `implementedBy` above L4 is an error. Regrouping *moves* a node; it does
-not edit a parent string.
+service — these never reference the model. **L4** binds a declared top-level node — an
+`object.*` **or a `template.*`** — and **L5** binds a member of one: a field, view,
+validator, identity, or a template's child. `implementedBy` above L4 is an error.
+Regrouping *moves* a node; it does not edit a parent string.
+
+Claim your prompts. A `template.prompt` is a model node realising a capability exactly as
+an entity is, and it is the node whose retirement is hardest to see later — a removed
+prompt leaves no table behind. A prompt estate with no requirement entries is the same
+blind spot this whole mechanism exists to close.
 
 **L1–L3 are levels of abstraction and ownership in the problem domain** — whose need is
 this, and at what altitude — and are NEVER a directory, package, deployable or module.

package/agent-context/skills/metaobjects-verify/references/requirements.md

@@ -35,9 +35,26 @@ mechanism exists to preserve.
 | `@implementedBy` above the L4 link floor | 1 |
 | live `requirement.architectural` claimed by nothing | 1 |
 | `@verifiedBy` naming a test that exists nowhere | 1 |
+| `@verifiedBy` naming a name found only in an **unrecognised** test file | 0 (warning) |
 | `@verifiedBy` naming a test that is **skipped** | 0 (warning) |
 | an entity no requirement claims | 0 (warning) |
 
+## What counts as a test file is YOUR project's call
+
+The scan ships patterns for jest/vitest/bun, JUnit, Maven Failsafe (`*IT`), xUnit/NUnit,
+pytest and Kotlin. Those are a convenience, **not an authority** — a built-in list is a guess
+about your repository, and a wrong guess reports a real test as a broken claim. Declare your
+conventions and they are added to the built-ins:
+
+```ts
+// metaobjects.config.ts
+export default defineConfig({ verify: { testFiles: ["**/*IT.kt", "**/*.feature"] } });
+```
+
+If a named test is missing from the corpus but present in some other source file, `verify`
+warns and names that file rather than failing — an unrecognised convention is the tool's
+ignorance, not your mistake.
+
 ## What a green run does NOT prove
 
 It proves **referential integrity**: statuses parse, levels are in range, links sit at or

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metaobjectsdev/sdk",
-  "version": "0.23.0",
+  "version": "0.23.1",
   "description": "Workspace helpers and agent-docs utilities for MetaObjects projects.",
   "type": "module",
   "main": "./dist/index.js",
@@ -56,7 +56,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@metaobjectsdev/metadata": "0.23.0",
+    "@metaobjectsdev/metadata": "0.23.1",
     "zod": "^3.23.0"
   },
   "devDependencies": {