@cad0p/pi-steering 0.1.0 → 0.2.0

package/src/plugins/git/cwd-extensions.ts

@@ -82,8 +82,8 @@
  */
 
 import * as path from "node:path";
-import type { Word } from "unbash";
 import { isStaticallyResolvable, type Modifier } from "@cad0p/unbash-walker";
+import type { Word } from "unbash";
 
 /** Regex matched against each `git`-command argument token. */
 const GIT_DIR_RE = /^--git-dir=(.+)$/;

package/src/schema.ts

@@ -1631,8 +1631,8 @@ export interface SteeringConfig {
    * specify its own. Defaults to `true` (fail-closed - overrides
    * must be explicit opt-in per rule).
    *
-   * Walk-up merge: inner layer wins when specified; missing layer
-   * leaves the running value alone.
+   * Layer merge: inner (project) layer wins when specified; missing
+   * layer leaves the running value alone.
    *
    * `buildConfig` preserves `undefined` in the merged output so
    * downstream evaluators can distinguish "user didn't specify" from
@@ -1698,7 +1698,7 @@ export interface SteeringConfig {
    * to distinguish shape at a glance from the past-participle
    * {@link disabledRules} / {@link disabledPlugins} lists.
    *
-   * Walk-up merge: inner layer wins when specified.
+   * Layer merge: inner (project) layer wins when specified.
    */
   disableDefaults?: boolean;
 
@@ -1714,7 +1714,7 @@ export interface SteeringConfig {
    * (e.g. tracker name collision, reserved name violation) — the
    * engine cannot operate safely with those issues present.
    *
-   * Walk-up merge: inner layer wins when specified, identical to
+   * Layer merge: inner (project) layer wins when specified, identical to
    * {@link disableDefaults}.
    *
    * Prior art: Rollup's `failAfterWarnings`, Maven's `failOnWarning`.

package/src/testing/index.ts

@@ -12,9 +12,9 @@
  *
  *   - {@link loadHarness}         — build an evaluator + dispatcher
  *                                    pair from a static
- *                                    {@link SteeringConfig}. No walk-up
- *                                    loading — tests pass explicit
- *                                    config.
+ *                                    {@link SteeringConfig}. No
+ *                                    filesystem discovery — tests
+ *                                    pass explicit config.
  *   - {@link mockContext}         — build a {@link PredicateContext}
  *                                    for unit-testing predicate
  *                                    handlers in isolation.
@@ -246,16 +246,16 @@ export interface LoadHarnessOptions {
 /**
  * Build an evaluator + observer dispatcher pair from a static
  * {@link SteeringConfig}. Tests drive rules through the same pipeline
- * production uses, without needing a pi runtime stub or walk-up
- * loading.
+ * production uses, without filesystem discovery.
  */
 export function loadHarness(options: LoadHarnessOptions): Harness {
   const inputConfig = options.config;
   const includeDefaults = options.includeDefaults ?? false;
 
   // Run the same merge that production does (single layer here, since
-  // loadHarness operates on an in-memory config rather than a walk-up
-  // chain). The shared helper short-circuits between buildConfig and
+  // loadHarness operates on an in-memory config rather than a
+  // filesystem discovery chain). The shared helper short-circuits
+  // between buildConfig and
   // resolvePlugins on error-class merge diagnostics so a
   // `tracker-name-collision` flagged by `buildConfig` is not also
   // re-flagged by `resolvePlugins`. The diagnostics surface within-