@objectstack/lint 17.1.0 → 17.3.0

package/dist/{runtime-s3X9D9hm.d.cts → runtime-B8F5-Cbg.d.cts}

@@ -35,7 +35,13 @@ interface AuthoringFinding {
     rule: string;
     /** Human-readable location, e.g. `object "leave_request"`. */
     where: string;
-    /** Config path, e.g. `objects[3].sharingModel`. */
+    /**
+     * Config path, e.g. `objects[3].sharingModel`. Positional as RULES emit it;
+     * on the runtime gate's wire surface the top-level collection index of a
+     * collection-resident finding is rewritten to the entry's NAME
+     * (`objects.acme_invoice.sharingModel`) — see `nameKeyFindingPath` in
+     * `runtime-gate.ts` (#10064).
+     */
     path: string;
     /** What is wrong. */
     message: string;
@@ -117,6 +123,19 @@ type AuthoringRuleInputTier = 'normalized' | 'parsed';
 interface AuthoringRuleContext {
     /** ADR-0080 SDUI component manifest, when the project ships one. */
     sduiManifest?: unknown;
+    /**
+     * [#9313] The singular metadata type of the per-write snapshot being judged
+     * — set by the runtime publish gate (`runtime-gate.ts`) on every gated
+     * write, ABSENT on the three CLI commands (`runAuthoringRules` never sets
+     * it). Exists for the one entry that is itself a registry: the
+     * reference-integrity suite dispatches its MEMBERS by this
+     * (`ReferenceIntegrityRule.runtimeTypes`), because the entry-level
+     * `runtimeTypes` can only say which writes reach the suite, not which
+     * members can judge a partial per-write snapshot without inventing
+     * findings. No other rule reads it, and none should without the same
+     * argument.
+     */
+    runtimeWriteType?: string;
 }
 interface AuthoringRule {
     /** The exported function's name — the id the wiring guard asserts on. */
@@ -257,6 +276,13 @@ type AnyRec = Record<string, unknown>;
  * `positions` / `apps` — so those are NOT carried. Widening the snapshot is a
  * one-key edit here plus a `CONTEXT_STACK_KEYS` entry, made when a rule that
  * reads the collection actually crosses the wall, never in advance.
+ *
+ * [#13977] "Derived from this shape" is now the mechanism and not only the
+ * intent: the second half of that edit is DEMANDED by the compiler rather than
+ * remembered. Add a key here and this package stops building until the
+ * collection has its row below — see {@link CONTEXT_STACK_KEYS} for what the
+ * old `satisfies` clause could not ask, and what silently happened when the
+ * row was forgotten.
  */
 interface RuntimeStackContext {
     /**
@@ -305,6 +331,23 @@ interface RuntimeStackContext {
      * for (#4463 D4).
      */
     datasets?: readonly unknown[];
+    /**
+     * The live page declarations (stack key `pages`).
+     *
+     * [#13216] The resolution universe `validateViewPageRefs` resolves a
+     * `type: 'page'` list view's `pageName` against. It is carried for the
+     * reason `datasets` is carried and states first: without it a per-write
+     * `view` snapshot holds NO pages at all, so every legitimate page mount
+     * reads as dangling. The widening is the "one-key edit here plus a
+     * `CONTEXT_STACK_KEYS` entry, made when a rule that reads the collection
+     * actually crosses the wall" this docblock describes — the rule crossed in
+     * the same change, never in advance.
+     *
+     * Carrying it in BOTH differential passes also cancels page-derived findings
+     * for every other write type, so a stored page's pre-existing condition is
+     * not some unrelated write's to answer for (#4463 D4).
+     */
+    pages?: readonly unknown[];
 }
 /**
  * Which package a write belongs to, and what that package is allowed to reach.

package/dist/{runtime-s3X9D9hm.d.ts → runtime-B8F5-Cbg.d.ts}

@@ -35,7 +35,13 @@ interface AuthoringFinding {
     rule: string;
     /** Human-readable location, e.g. `object "leave_request"`. */
     where: string;
-    /** Config path, e.g. `objects[3].sharingModel`. */
+    /**
+     * Config path, e.g. `objects[3].sharingModel`. Positional as RULES emit it;
+     * on the runtime gate's wire surface the top-level collection index of a
+     * collection-resident finding is rewritten to the entry's NAME
+     * (`objects.acme_invoice.sharingModel`) — see `nameKeyFindingPath` in
+     * `runtime-gate.ts` (#10064).
+     */
     path: string;
     /** What is wrong. */
     message: string;
@@ -117,6 +123,19 @@ type AuthoringRuleInputTier = 'normalized' | 'parsed';
 interface AuthoringRuleContext {
     /** ADR-0080 SDUI component manifest, when the project ships one. */
     sduiManifest?: unknown;
+    /**
+     * [#9313] The singular metadata type of the per-write snapshot being judged
+     * — set by the runtime publish gate (`runtime-gate.ts`) on every gated
+     * write, ABSENT on the three CLI commands (`runAuthoringRules` never sets
+     * it). Exists for the one entry that is itself a registry: the
+     * reference-integrity suite dispatches its MEMBERS by this
+     * (`ReferenceIntegrityRule.runtimeTypes`), because the entry-level
+     * `runtimeTypes` can only say which writes reach the suite, not which
+     * members can judge a partial per-write snapshot without inventing
+     * findings. No other rule reads it, and none should without the same
+     * argument.
+     */
+    runtimeWriteType?: string;
 }
 interface AuthoringRule {
     /** The exported function's name — the id the wiring guard asserts on. */
@@ -257,6 +276,13 @@ type AnyRec = Record<string, unknown>;
  * `positions` / `apps` — so those are NOT carried. Widening the snapshot is a
  * one-key edit here plus a `CONTEXT_STACK_KEYS` entry, made when a rule that
  * reads the collection actually crosses the wall, never in advance.
+ *
+ * [#13977] "Derived from this shape" is now the mechanism and not only the
+ * intent: the second half of that edit is DEMANDED by the compiler rather than
+ * remembered. Add a key here and this package stops building until the
+ * collection has its row below — see {@link CONTEXT_STACK_KEYS} for what the
+ * old `satisfies` clause could not ask, and what silently happened when the
+ * row was forgotten.
  */
 interface RuntimeStackContext {
     /**
@@ -305,6 +331,23 @@ interface RuntimeStackContext {
      * for (#4463 D4).
      */
     datasets?: readonly unknown[];
+    /**
+     * The live page declarations (stack key `pages`).
+     *
+     * [#13216] The resolution universe `validateViewPageRefs` resolves a
+     * `type: 'page'` list view's `pageName` against. It is carried for the
+     * reason `datasets` is carried and states first: without it a per-write
+     * `view` snapshot holds NO pages at all, so every legitimate page mount
+     * reads as dangling. The widening is the "one-key edit here plus a
+     * `CONTEXT_STACK_KEYS` entry, made when a rule that reads the collection
+     * actually crosses the wall" this docblock describes — the rule crossed in
+     * the same change, never in advance.
+     *
+     * Carrying it in BOTH differential passes also cancels page-derived findings
+     * for every other write type, so a stored page's pre-existing condition is
+     * not some unrelated write's to answer for (#4463 D4).
+     */
+    pages?: readonly unknown[];
 }
 /**
  * Which package a write belongs to, and what that package is allowed to reach.