@ai-matrx/content-ir-react 0.5.1 → 0.7.0

package/dist/index.d.cts

@@ -482,10 +482,16 @@ type GenericFallbackReason =
  | "generic-row"
 /**
  * The envelope carries a kind-preserved RAW: the payload identified a
- * registered kind but its value failed the schema (or the schema never
- * arrived before the region closed). The instance is BROKEN, not
- * component-less — the repair is fixing the payload/schema, and the generic
- * floor must acknowledge the kind and surface the recorded problems.
+ * registered kind and its value FAILED a check — a schema violation, an
+ * array-item kind mismatch, a duplicate key, a contradicted speculation.
+ * The instance is BROKEN, not component-less — the repair is fixing the
+ * payload or the schema, and the generic floor must acknowledge the kind and
+ * surface the recorded problems.
+ *
+ * NOT this: a kind whose schema was never available (`kindState:
+ * "unverified"`). Nothing checked that value, so calling it broken is a
+ * false accusation — it routes to its component. The two were one state
+ * until 2026-08-29 and conflating them was a platform-wide outage.
  */
  | "broken-instance"
 /**
@@ -701,6 +707,23 @@ declare function isRecordValue(value: unknown): value is Record<string, unknown>
  * decision order; requires the resolver warm tier for db rows (see the warm
  * tick in {@link KindInstanceRender}).
  */
+/**
+ * Is there a render path for this kind that is NOT the generic key/value floor?
+ *
+ * 🚨 READ THIS BEFORE USING IT AS A HEALTH SIGNAL. It answers a narrow
+ * question — "will a direct-object render mount something other than the
+ * generic view?" — and it is the right question for the fallback decision it
+ * was written for. It is the WRONG question for "does this kind work".
+ *
+ * It cannot see any of: whether the kind's schema loads, whether a streamed
+ * payload is recognized from text, or what `applyIrKindRoute` returns for a
+ * real envelope. On 2026-08-29 every one of ~221 kinds that had stopped
+ * rendering in chat still answered `true` here, because their component rows
+ * were fine — the recognition step ahead of the component was not.
+ *
+ * For "does this kind work", run the render paths
+ * (`features/content-ir/render-paths`) and read the route's actual answer.
+ */
 declare function kindIsRoutable(kind: string, host: ContentIrHost): boolean;
 interface KindInstanceRenderProps {
     kind: string;

package/dist/index.d.ts

@@ -482,10 +482,16 @@ type GenericFallbackReason =
  | "generic-row"
 /**
  * The envelope carries a kind-preserved RAW: the payload identified a
- * registered kind but its value failed the schema (or the schema never
- * arrived before the region closed). The instance is BROKEN, not
- * component-less — the repair is fixing the payload/schema, and the generic
- * floor must acknowledge the kind and surface the recorded problems.
+ * registered kind and its value FAILED a check — a schema violation, an
+ * array-item kind mismatch, a duplicate key, a contradicted speculation.
+ * The instance is BROKEN, not component-less — the repair is fixing the
+ * payload or the schema, and the generic floor must acknowledge the kind and
+ * surface the recorded problems.
+ *
+ * NOT this: a kind whose schema was never available (`kindState:
+ * "unverified"`). Nothing checked that value, so calling it broken is a
+ * false accusation — it routes to its component. The two were one state
+ * until 2026-08-29 and conflating them was a platform-wide outage.
  */
  | "broken-instance"
 /**
@@ -701,6 +707,23 @@ declare function isRecordValue(value: unknown): value is Record<string, unknown>
  * decision order; requires the resolver warm tier for db rows (see the warm
  * tick in {@link KindInstanceRender}).
  */
+/**
+ * Is there a render path for this kind that is NOT the generic key/value floor?
+ *
+ * 🚨 READ THIS BEFORE USING IT AS A HEALTH SIGNAL. It answers a narrow
+ * question — "will a direct-object render mount something other than the
+ * generic view?" — and it is the right question for the fallback decision it
+ * was written for. It is the WRONG question for "does this kind work".
+ *
+ * It cannot see any of: whether the kind's schema loads, whether a streamed
+ * payload is recognized from text, or what `applyIrKindRoute` returns for a
+ * real envelope. On 2026-08-29 every one of ~221 kinds that had stopped
+ * rendering in chat still answered `true` here, because their component rows
+ * were fine — the recognition step ahead of the component was not.
+ *
+ * For "does this kind work", run the render paths
+ * (`features/content-ir/render-paths`) and read the route's actual answer.
+ */
 declare function kindIsRoutable(kind: string, host: ContentIrHost): boolean;
 interface KindInstanceRenderProps {
     kind: string;

package/dist/index.js

@@ -567,9 +567,9 @@ function isRecordValue(value) {
 }
 function kindIsRoutable(kind, host) {
   if (host.kinds.getDefinition(kind)?.legacyBlockType) return true;
-  return Boolean(
-    host.components.resolve(kind, host.platform, "output")?.isActive
-  );
+  const resolution = host.components.resolve(kind, host.platform, "output");
+  if (!resolution?.isActive) return false;
+  return resolution.componentKey !== GENERIC_STRUCTURED_COMPONENT_KEY;
 }
 function KindInstanceRender({
   kind,