craftar 0.22.0 → 0.22.1

package/README.md

@@ -313,6 +313,14 @@ Later: `service` ingredients with compose fragments (`craftar services up`); `do
 
 ## Upgrading
 
+### to 0.22.1
+
+- **A file the schema refuses is reported on one line, and never with a value it holds.** `invalid <file>: <key>: <what was expected>; <key>: …` replaces zod's JSON list of issues, which quoted the refused value — so a credential written where one of a fixed set of words is expected reached the terminal. A key is still named, as a path (`overrides.sections.<key>`) or as an unrecognized key, and so is the *type* received (`Expected string, received number`) — never the value. It holds for a Forge file, `craftar.yaml` (merged with `craftar.local.yaml`), the registry (`invalid <file>: …`), a `forge unify --plan` file (`<file>: <key>: …`, with no `invalid`), and the refusals of `import` and `drift promote` (`does not fit the ingredient schema: …`, `does not load (…)`), `forge unify` (`the edit no longer loads: …`), and `add recipe`, `remove recipe` and `import --write-config` (`it no longer loads: …`).
+- **A `craftar.lock` or a registry that does not read is named, and nothing of it is quoted.** `craftar.lock is not valid JSON` and `craftar.lock is not a valid lock: <key>: …` replace the raw parser and zod messages; a registry that is not valid JSON reads `cannot read <file>: not valid JSON`. `declares schema <n>, which this craftar does not read` prints the schema only when it is a whole number, and `(not a whole number)` otherwise.
+- **`craftar doctor`**: the `config`, `lock` and `registry` messages carry the same text — `<what> (<key>: <what was expected>, and N more)` keeps its shape, without `received '<value>'`; `craftar.lock is not valid JSON` no longer ends with the parser's message in parentheses.
+- **No exit code and no `--json` key changes**; the text of an error string inside `--json` follows the new wording — among them `doctor --json` `checks[].message`; the `warnings` of `workspaces --json`, `targets --json`, `forge unify --json` and `drift promote --json`; `forge impact --json` `error`; `impact[].error` of `forge unify --json` and `impact.workspaces[].error` of `drift promote --json`; and `forge unify --json` `recipes.kept[].reason`.
+- **No byte change**: no emitter and no lock changed. No workspace sees `update`.
+
 ### to 0.22.0
 
 - **New commands `craftar drift show`, `craftar drift discard` and `craftar drift promote`**: list hand-edited files, discard their edits, or carry one into the Forge. `drift show --json` and `drift promote --json` are new tooling contracts. The `sync` skip lines for `drift` and `orphan-drift` were reworded (prose, not a contract).

package/dist/cli.js

@@ -33,6 +33,7 @@ import { localKeys, readLocalFile } from "./core/workspace-yaml.js";
 import { HUNK_CLASSES, INGREDIENT_TYPES, UnifyPlanSchema } from "./schema/index.js";
 import { EXAMPLE_SETTINGS } from "./emitters/shared.js";
 import { YamlSyntaxError, parseYamlText } from "./core/yaml-read.js";
+import { errorText } from "./core/schema-fault.js";
 process.stdout.on("error", (e) => { if (e.code === "EPIPE")
     process.exit(0); });
 /**
@@ -42,7 +43,7 @@ process.stdout.on("error", (e) => { if (e.code === "EPIPE")
  */
 const DIFF_EXIT_CODE_FETCH_MODE = "sync";
 const program = new Command();
-program.name("craftar").description("Craft, sync and convert AI-coding workspace harnesses.").version("0.22.0");
+program.name("craftar").description("Craft, sync and convert AI-coding workspace harnesses.").version("0.22.1");
 const SAVE_PLAN_GATE = { what: "plan", who: "unify", outside: "save plans outside the Forge", never: "unify never overwrites" };
 const REPORT_GATE = { what: "report", who: "import", outside: "write the report outside the Forge", never: "import never overwrites" };
 program
@@ -1522,13 +1523,13 @@ forge
             parsed = parseYamlText(o.plan, await fs.readFile(o.plan, "utf8"));
         }
         catch (e) {
-            fail(e instanceof YamlSyntaxError ? e.message : `${o.plan}: ${e instanceof Error ? e.message : String(e)}`);
+            fail(e instanceof YamlSyntaxError ? e.message : `${o.plan}: ${errorText(e)}`);
         }
         try {
             loadedPlan = UnifyPlanSchema.parse(parsed);
         }
         catch (e) {
-            fail(`${o.plan}: ${e instanceof Error ? e.message : String(e)}`);
+            fail(`${o.plan}: ${errorText(e)}`);
         }
         // The plan must be for this exact invocation (Ruling 23) — checked before staleness, so a
         // right-ingredient-wrong-profile plan is named for what it is rather than misdiagnosed as
@@ -1994,7 +1995,7 @@ cache
     else
         printPrune(result);
 });
-program.parseAsync().catch((e) => fail(e instanceof Error ? e.message : String(e)));
+program.parseAsync().catch((e) => fail(errorText(e)));
 /* ---------------------------------------------------------------- helpers */
 /** The network rule of a command, `--offline`, and `$CRAFTAR_HOME` (spec 13 §4.1, §6.3). */
 function load(o, mode) {
@@ -2328,7 +2329,7 @@ function unheldMessage(command, root, unheld) {
  * git tracks, `clean` for files unify created (checkout refuses a path git does not know).
  */
 function lateFailure(e, root, journal, command = "unify") {
-    const msg = e instanceof Error ? e.message : String(e);
+    const msg = errorText(e);
     if (journal.length === 0)
         return msg;
     const rel = (abs) => path.relative(root, abs).split(path.sep).join("/");