@cruxy/cli 1.10.0 → 1.11.0

package/dist/config/schema.js

@@ -391,13 +391,47 @@ export const JobsConfigSchema = z
      */
     maxJobs: z.number().int().positive().default(5),
     /**
-     * How many of a job's most-recent log lines are retained in its ring buffer
-     * for `cruxy logs <id>`. Bounded so a chatty job can't grow memory without
-     * limit; older lines roll off oldest-first. Default 1000.
+     * How many of a job's most-recent log lines are retained in its IN-MEMORY
+     * ring buffer, which is what `/logs <id>` and the Tasks view read while the
+     * session is alive. Bounded so a chatty job can't grow memory without
+     * limit; older lines roll off oldest-first and `/logs` says how many.
+     * Default 1000.
+     *
+     * This is no longer the only copy: {@link logFileLines} bounds the
+     * persisted one, which `cruxy logs <id>` reads back after the fact.
      */
     logBufferLines: z.number().int().positive().default(1000),
+    /**
+     * How many lines of a job's output are written to its file under
+     * `~/.cruxy/projects/<project>/subagents/` (#172 item 1). Past this the log
+     * records one honest `truncated` marker and stops; the job runs on.
+     *
+     * WHY A SECOND, LARGER BOUND rather than reusing {@link logBufferLines}.
+     * The file exists precisely to remove the ring buffer's drop-on-overflow,
+     * so a file bounded at the buffer's size would persist the same truncated
+     * tail and buy nothing — which is why this is FLOORED at `logBufferLines`
+     * rather than allowed to sink below it (see the refinement below).
+     *
+     * WHY IT IS BOUNDED AT ALL. `sessions.retention` bounds how many session-
+     * shaped things the tree keeps; nothing bounds how big ONE of them gets,
+     * and a background job is the first writer here that can produce unbounded
+     * output unattended — it runs a full agent loop off screen, and a job stuck
+     * in a tool-call loop emits lines for as long as its budget lasts with
+     * nobody watching. Streaming that to disk uncapped is the second unbounded
+     * writer under `~/.cruxy` that #257 exists to prevent.
+     *
+     * 20000 is 20x the in-memory buffer: roughly 2 MB for a worst-case job, and
+     * the sweep drops a `done` job's log at the next start, so the steady-state
+     * cost of the default is near zero.
+     */
+    logFileLines: z.number().int().positive().default(20000),
 })
-    .strict();
+    .strict()
+    .refine((j) => j.logFileLines >= j.logBufferLines, {
+    message: "jobs.logFileLines must be at least jobs.logBufferLines — the persisted log " +
+        "exists to remove the ring buffer's drop-on-overflow, and a file that kept " +
+        "fewer lines than memory would make persisting strictly worse than not persisting",
+});
 /**
  * Sandbox / container execution (C.16): defense-in-depth beneath the U.3 gate.
  * When enabled, `run_command` and `run_tests` execute inside an isolated,
@@ -461,17 +495,25 @@ export const HooksConfigSchema = z
 /**
  * Multi-model routing (C.30): map declared task classes to tiers so mechanical
  * work runs on a cheap tier and hard reasoning on a strong one. Fully opt-in —
- * with an empty `map` and no `default`, every task class routes to the session's
- * single tier and behavior is unchanged (routing stays inert until configured).
- * Only tier names appear here; upstream model names never do (U.8). Keys are the
- * fixed {@link TASK_CLASSES}, so a mistyped class is rejected at config load.
+ * with an empty `map` and no `default` the whole table is inert and nothing
+ * about a session changes. Only tier names appear here; upstream model names
+ * never do (U.8). Keys are the fixed {@link TASK_CLASSES}, so a mistyped class
+ * is rejected at config load.
+ *
+ * A PARTIAL TABLE STAYS PARTIAL. Writing `map` without `default` routes exactly
+ * the classes named and leaves every other one to the gateway (`auto`) — it does
+ * not pin them to some tier chosen on your behalf. The exception is a
+ * `model.model` that names a tier: that is a session-wide model choice, and the
+ * unnamed classes inherit it rather than being handed back to the gateway.
  */
 export const RoutingConfigSchema = z
     .object({
-    /** Tier for any task class not in `map`. Unset → the tier implied by
-     * `model.model` (a real tier, or the auto-fallback tier). */
+    /** Tier for any task class not in `map`. Unset → the tier `model.model`
+     * names, if it names one; otherwise the class is not routed here at all and
+     * goes out as `auto` for the gateway to route. */
     default: z.enum(MODEL_TIERS).optional(),
-    /** Per-task-class tier overrides; anything omitted takes `default`. */
+    /** Per-task-class tier overrides; anything omitted takes `default`, or
+     * `auto` when there is no `default` to take. */
     map: z.record(z.enum(TASK_CLASSES), z.enum(MODEL_TIERS)).default({}),
 })
     .strict();

package/dist/errors/constructors.js

@@ -109,14 +109,47 @@ export function configParse(path, underlying) {
         meta: { path },
     });
 }
+/**
+ * `--config <path>` named a file that does not exist.
+ *
+ * Loud by construction: the alternative is falling back to discovery or to
+ * defaults, which produces exactly the behaviour the user would have got
+ * without the flag, and so is indistinguishable from success (#289). Raised
+ * only for an EXPLICIT path — a missing global or project config is ordinary.
+ */
+export function configNotFound(path) {
+    return new CruxyError({
+        code: ErrorCode.ConfigNotFound,
+        title: `config file not found: ${path}`,
+        cause: "`--config` named a file that does not exist",
+        nextSteps: [
+            "check the path (it is resolved as given, relative to the current directory)",
+            "omit `--config` to use the discovered project config, or `~/.cruxy/config.json`",
+        ],
+        meta: { path },
+    });
+}
 export function configInvalid(issues, path) {
     return new CruxyError({
         code: ErrorCode.ConfigInvalid,
-        title: "the configuration is invalid",
+        // NAME THE FILE, as `configParse` above already does. The path was carried
+        // in `meta` alone, and the terminal formatter renders title/cause/steps/code
+        // — not meta — so the caller's choice of which file to blame reached nobody
+        // and "correct the reported field(s)" left the user to guess between the
+        // global, project and explicit configs (#289).
+        //
+        // It is the HIGHEST-PRECEDENCE file in effect, not necessarily the one
+        // holding the bad key: the config is a merge, and a resolved value cannot
+        // be traced to a layer from here. Hence "start with" and the pointer to
+        // `config path` — an honest lead, not a claim about which line to edit.
+        title: path
+            ? `the configuration is invalid (${path})`
+            : "the configuration is invalid",
         cause: issues,
         nextSteps: [
             "correct the reported field(s)",
-            "see valid keys with `cruxy config list`",
+            ...(path ? [`start with ${path}, the last file merged`] : []),
+            "see valid keys with `cruxy config list`, or the files in effect with `cruxy config path`",
         ],
         meta: path ? { path } : undefined,
     });

package/dist/errors/types.js

@@ -29,6 +29,11 @@ export const ErrorCode = {
     // config (exit 3)
     ConfigParse: "CRUXY_E_CONFIG_PARSE",
     ConfigInvalid: "CRUXY_E_CONFIG_INVALID",
+    /** A config file named with `--config` does not exist. DISTINCT from
+     * {@link ConfigParse}: nothing was malformed, the file simply is not there,
+     * and the advice is to check the path rather than the JSON. Only an EXPLICIT
+     * path can raise it — a missing global or project file is the normal case. */
+    ConfigNotFound: "CRUXY_E_CONFIG_NOT_FOUND",
     // auth (exit 4)
     AuthMissingKey: "CRUXY_E_AUTH_MISSING_KEY",
     AuthInvalid: "CRUXY_E_AUTH_INVALID",
@@ -311,6 +316,7 @@ const EXIT_CODES = {
     [ErrorCode.RoutingTierUnavailable]: 2,
     [ErrorCode.ConfigParse]: 3,
     [ErrorCode.ConfigInvalid]: 3,
+    [ErrorCode.ConfigNotFound]: 3,
     [ErrorCode.AuthMissingKey]: 4,
     [ErrorCode.AuthInvalid]: 4,
     [ErrorCode.AuthExpired]: 4,

package/dist/jobs/index.js

@@ -1,5 +1,6 @@
 export * from "./types.js";
 export * from "./log-buffer.js";
+export * from "./log-store.js";
 export * from "./log-renderer.js";
 export * from "./approval-queue.js";
 export * from "./manager.js";

package/dist/jobs/log-renderer.js

@@ -18,9 +18,14 @@ const OFFSCREEN_CAPS = {
 };
 /**
  * A {@link StreamRenderer} for a background job (C.28) that captures activity into
- * the job's log buffer and writes NOTHING to any terminal — a job runs
+ * the job's log sink and writes NOTHING to any terminal — a job runs
  * non-interactively, off screen, and its foreground session owns the terminal.
- * `cruxy logs <id>` (a REPL `/logs`) reads back what was captured here.
+ *
+ * What was captured here is read back from two different copies: the in-session
+ * `/logs <id>` and the Tasks view read the ring buffer while the session lives,
+ * and `cruxy logs <id>` reads the persisted file afterwards (#172 item 1).
+ * Everything this renderer emits goes through the one `JobManager.log` sink, so
+ * both copies see exactly the same lines.
  *
  * Assistant text is accumulated and flushed a line at a time on `endSegment`;
  * committed chrome notes and tool-call completions are captured verbatim. The
@@ -94,9 +99,9 @@ export class JobLogRenderer {
         this.planSteps = steps.map((s) => ({ ...s }));
     }
     /**
-     * A job's test run is exactly the kind of outcome `cruxy logs` exists to
-     * show. Plain text, no theme glyphs, matching this log's `[ok]`/`[fail]`
-     * style — and no count this renderer was not given.
+     * A job's test run is exactly the kind of outcome a job log exists to show.
+     * Plain text, no theme glyphs, matching this log's `[ok]`/`[fail]` style —
+     * and no count this renderer was not given.
      */
     testResult(report) {
         const counted = report.total !== undefined