@monosmith/plugin-sdk 2.0.0-beta.12 → 2.0.0-beta.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@monosmith/plugin-sdk",
-  "version": "2.0.0-beta.12",
+  "version": "2.0.0-beta.13",
   "description": "The TypeScript SDK for writing smith plugins: the protocol's types, the serve loop, a test host, the conformance checks, templating and key-order-keeping JSON editing. No runtime dependencies.",
   "license": "MIT",
   "type": "module",

package/protocol/protocol-schema.contract.js

@@ -1307,15 +1307,28 @@ export const protocolSchema = {
             ]
         },
         "Finding": {
-            "description": "Finding is one check. Every failed finding names its remedy.",
+            "description": "Finding is one check. Every failed finding names its problem and its remedy.",
             "type": "object",
             "properties": {
                 "check": {
-                    "type": "string"
+                    "type": "string",
+                    "description": "Check is the rule, stated as it should hold (\"golangci-lint is 2.15.0, as in CI\"). A passing finding is listed by it."
                 },
                 "ok": {
                     "type": "boolean"
                 },
+                "problem": {
+                    "type": "string",
+                    "description": "Problem is what is wrong, in one line (\"golangci-lint is 2.14.0, CI uses 2.15.0\"). A failed finding is listed by it; one without it is listed by its Check."
+                },
+                "project": {
+                    "type": "string",
+                    "description": "Project is the project the finding is about, as the workspace names it (\"web\"); empty for a finding about the workspace itself. The host files a finding under its project, so the Check, Problem and Detail need not name it."
+                },
+                "area": {
+                    "type": "string",
+                    "description": "Area is the part of the workspace a workspace-wide finding is about, in one lowercase word: \"toolchain\", \"ci\", \"lint\", \"dependencies\", \"release\", \"git\" or \"config\". A finding with a Project has none."
+                },
                 "detail": {
                     "type": "string"
                 },

package/protocol/protocol-types.contract.d.ts

@@ -602,10 +602,31 @@ export interface FileEdit {
     content?: string;
     delete?: boolean;
 }
-/** Finding is one check. Every failed finding names its remedy. */
+/** Finding is one check. Every failed finding names its problem and its remedy. */
 export interface Finding {
+    /**
+     * Check is the rule, stated as it should hold ("golangci-lint is 2.15.0, as in CI"). A passing
+     * finding is listed by it.
+     */
     check: string;
     ok: boolean;
+    /**
+     * Problem is what is wrong, in one line ("golangci-lint is 2.14.0, CI uses 2.15.0"). A failed
+     * finding is listed by it; one without it is listed by its Check.
+     */
+    problem?: string;
+    /**
+     * Project is the project the finding is about, as the workspace names it ("web"); empty for a
+     * finding about the workspace itself. The host files a finding under its project, so the Check,
+     * Problem and Detail need not name it.
+     */
+    project?: string;
+    /**
+     * Area is the part of the workspace a workspace-wide finding is about, in one lowercase word:
+     * "toolchain", "ci", "lint", "dependencies", "release", "git" or "config". A finding with a
+     * Project has none.
+     */
+    area?: string;
     detail?: string;
     remedy?: string;
     /** Warning true reports a problem without failing doctor. */

package/scaffold/index.d.ts

@@ -1,3 +1,3 @@
 export { scaffoldProject } from './scaffold-project.use-case.ts';
 export type { ScaffoldOptions } from './scaffold-project.use-case.ts';
-export { scaffoldData } from './scaffold-data.mapper.ts';
+export { scaffoldData } from './template-fields.mapper.ts';

package/scaffold/index.js

@@ -1,2 +1,2 @@
 export { scaffoldProject } from './scaffold-project.use-case.js';
-export { scaffoldData } from './scaffold-data.mapper.js';
+export { scaffoldData } from './template-fields.mapper.js';

package/scaffold/scaffold-project.use-case.js

@@ -1,5 +1,5 @@
 import { writeTemplates } from '../templating/index.js';
-import { scaffoldData } from './scaffold-data.mapper.js';
+import { scaffoldData } from './template-fields.mapper.js';
 /**
  * The answer to `generate` for a scaffold: renders the templates into the new
  * project, never overwriting a file, and reports what it wrote. A language