@objectstack/lint 17.2.0 → 17.4.0

package/dist/{runtime-cV-l_vtC.d.cts → runtime-S3OZQDZV.d.cts}

@@ -70,6 +70,15 @@ type AuthoringRuleTier = 'gating' | 'advisory';
  * `os validate`'s verdict to give), so it runs BOTH tiers on the normalized
  * stack. Every rule here is written to tolerate that — it is what `os lint`
  * already did for the reference-integrity suite and the security linter.
+ * Since #16095 the `parsed` tier under `os lint` is that same normalized stack
+ * with its inline `handler` callables LOWERED to a metadata `body` (the
+ * `lowerCallables` pass `os build` runs before its parse) — still unparsed,
+ * still the same input, but carrying the `body.source` the `hook-body-*` /
+ * `hook-api-update-readonly-*` family opens on. Without it the family judged
+ * only hooks authored with an explicit `body`, which the reference app never
+ * writes (39 of 39 hooks are `handler` functions), while `os build` judged
+ * them all along. `normalized`-tier rules keep the un-lowered input on every
+ * command, so a rule that reads a live function value belongs there.
  *
  * ## What `normalized` does NOT buy, measured (#6073)
  *
@@ -189,8 +198,10 @@ interface AuthoringRuleRun extends AuthoringRuleContext {
     /** `normalizeStackInput` output — pre-Zod-parse. Always required. */
     normalized: AnyRec$1;
     /**
-     * Post-Zod-parse stack. Omitted by `os lint`, which does not parse; `parsed`
-     * rules then read `normalized` (see `AuthoringRuleInputTier`).
+     * Post-Zod-parse stack. `os lint`, which does not parse, hands this the
+     * normalized stack with its inline callables lowered to metadata bodies
+     * (#16095, see `AuthoringRuleInputTier`); omitted, `parsed` rules read
+     * `normalized`.
      */
     parsed?: AnyRec$1;
 }
@@ -276,6 +287,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 {
     /**
@@ -324,6 +342,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-cV-l_vtC.d.ts → runtime-S3OZQDZV.d.ts}

@@ -70,6 +70,15 @@ type AuthoringRuleTier = 'gating' | 'advisory';
  * `os validate`'s verdict to give), so it runs BOTH tiers on the normalized
  * stack. Every rule here is written to tolerate that — it is what `os lint`
  * already did for the reference-integrity suite and the security linter.
+ * Since #16095 the `parsed` tier under `os lint` is that same normalized stack
+ * with its inline `handler` callables LOWERED to a metadata `body` (the
+ * `lowerCallables` pass `os build` runs before its parse) — still unparsed,
+ * still the same input, but carrying the `body.source` the `hook-body-*` /
+ * `hook-api-update-readonly-*` family opens on. Without it the family judged
+ * only hooks authored with an explicit `body`, which the reference app never
+ * writes (39 of 39 hooks are `handler` functions), while `os build` judged
+ * them all along. `normalized`-tier rules keep the un-lowered input on every
+ * command, so a rule that reads a live function value belongs there.
  *
  * ## What `normalized` does NOT buy, measured (#6073)
  *
@@ -189,8 +198,10 @@ interface AuthoringRuleRun extends AuthoringRuleContext {
     /** `normalizeStackInput` output — pre-Zod-parse. Always required. */
     normalized: AnyRec$1;
     /**
-     * Post-Zod-parse stack. Omitted by `os lint`, which does not parse; `parsed`
-     * rules then read `normalized` (see `AuthoringRuleInputTier`).
+     * Post-Zod-parse stack. `os lint`, which does not parse, hands this the
+     * normalized stack with its inline callables lowered to metadata bodies
+     * (#16095, see `AuthoringRuleInputTier`); omitted, `parsed` rules read
+     * `normalized`.
      */
     parsed?: AnyRec$1;
 }
@@ -276,6 +287,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 {
     /**
@@ -324,6 +342,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.