@ai-matrx/records 0.72.12 → 0.72.23

package/dist/{validate-QtFxMmJc.d.ts → types-Ba11aOEO.d.ts}

@@ -334,45 +334,4 @@ interface UseCaseSummary {
     rowCount: number;
 }
 
-/**
- * Every word a `parityType` may be: the parity types, every kind the declaration door
- * publishes (`custom.field_kinds()` — entity_reference, signature, long_text …, which a
- * lane-8 template needs for S4 and e-sign), their behaviours, the synonyms.
- */
-declare const RESOLVABLE_FIELD_TYPE_WORDS: readonly string[];
-/**
- * The minimum a seeded business needs before a screen looks like it is working
- * rather than like a fixture. Below this, a screenshot shows an empty state.
- *
- * It was 8 until a real dataset argued with it: a whole-house renovation has SIX
- * ROOMS, and demanding eight would have meant inventing two rooms that do not
- * exist — which is the exact failure this whole library is against. Six rooms on
- * a board is a working project, not an empty screen. So the floor is what a
- * screen genuinely needs, and the suite keeps the stronger check where it
- * belongs: at least 20 rows across the whole use case.
- */
-declare const MIN_ROWS_IN_PRIMARY_TABLE = 5;
-/** A refusal: what is wrong, where, and what to do. */
-interface UseCaseProblem {
-    /** Dotted path into the use case: "tables[1].fields[3].choices". */
-    at: string;
-    /** The sentence. Always says what to do, never only what is wrong. */
-    says: string;
-}
-interface UseCaseVerdict {
-    ok: boolean;
-    problems: UseCaseProblem[];
-}
-/**
- * Check one use case. Returns every problem rather than the first, because a
- * crew fixing a dataset wants the whole list in one pass.
- */
-declare function validateUseCase(useCase: UseCase): UseCaseVerdict;
-/**
- * Validate, and throw with every problem listed. This is what a seeder calls
- * before it writes anything to a live organization — a half-valid dataset is
- * worse than none, because it produces a screen that looks like it worked.
- */
-declare function assertUseCase(useCase: UseCase): void;
-
-export { type BusinessIdentity as B, type FormAudience as F, MIN_ROWS_IN_PRIMARY_TABLE as M, type NotificationChannel as N, type PostalAddress as P, RESOLVABLE_FIELD_TYPE_WORDS as R, type UseCase as U, type UseCaseSummary as a, type UseCaseDashboardQuestion as b, type UseCaseDocumentTemplate as c, type UseCaseField as d, type UseCaseForm as e, type UseCaseFormField as f, type UseCaseMergeField as g, type UseCaseNotificationRule as h, type UseCaseNotificationTrigger as i, type UseCasePipeline as j, type UseCasePipelineStage as k, type UseCaseProblem as l, type UseCaseProvenance as m, type UseCaseRelationship as n, type UseCaseRow as o, type UseCaseTable as p, type UseCaseVerdict as q, assertUseCase as r, validateUseCase as v };
+export type { BusinessIdentity as B, FormAudience as F, NotificationChannel as N, PostalAddress as P, UseCase as U, UseCaseTable as a, UseCaseField as b, UseCaseRow as c, UseCaseForm as d, UseCaseFormField as e, UseCaseNotificationTrigger as f, UseCaseProvenance as g, UseCaseSummary as h, UseCaseDashboardQuestion as i, UseCaseDocumentTemplate as j, UseCaseMergeField as k, UseCaseNotificationRule as l, UseCasePipeline as m, UseCasePipelineStage as n, UseCaseRelationship as o };

package/dist/{validate-DUSrx-9E.d.cts → types-BtEKp3ot.d.cts}

@@ -334,45 +334,4 @@ interface UseCaseSummary {
     rowCount: number;
 }
 
-/**
- * Every word a `parityType` may be: the parity types, every kind the declaration door
- * publishes (`custom.field_kinds()` — entity_reference, signature, long_text …, which a
- * lane-8 template needs for S4 and e-sign), their behaviours, the synonyms.
- */
-declare const RESOLVABLE_FIELD_TYPE_WORDS: readonly string[];
-/**
- * The minimum a seeded business needs before a screen looks like it is working
- * rather than like a fixture. Below this, a screenshot shows an empty state.
- *
- * It was 8 until a real dataset argued with it: a whole-house renovation has SIX
- * ROOMS, and demanding eight would have meant inventing two rooms that do not
- * exist — which is the exact failure this whole library is against. Six rooms on
- * a board is a working project, not an empty screen. So the floor is what a
- * screen genuinely needs, and the suite keeps the stronger check where it
- * belongs: at least 20 rows across the whole use case.
- */
-declare const MIN_ROWS_IN_PRIMARY_TABLE = 5;
-/** A refusal: what is wrong, where, and what to do. */
-interface UseCaseProblem {
-    /** Dotted path into the use case: "tables[1].fields[3].choices". */
-    at: string;
-    /** The sentence. Always says what to do, never only what is wrong. */
-    says: string;
-}
-interface UseCaseVerdict {
-    ok: boolean;
-    problems: UseCaseProblem[];
-}
-/**
- * Check one use case. Returns every problem rather than the first, because a
- * crew fixing a dataset wants the whole list in one pass.
- */
-declare function validateUseCase(useCase: UseCase): UseCaseVerdict;
-/**
- * Validate, and throw with every problem listed. This is what a seeder calls
- * before it writes anything to a live organization — a half-valid dataset is
- * worse than none, because it produces a screen that looks like it worked.
- */
-declare function assertUseCase(useCase: UseCase): void;
-
-export { type BusinessIdentity as B, type FormAudience as F, MIN_ROWS_IN_PRIMARY_TABLE as M, type NotificationChannel as N, type PostalAddress as P, RESOLVABLE_FIELD_TYPE_WORDS as R, type UseCase as U, type UseCaseSummary as a, type UseCaseDashboardQuestion as b, type UseCaseDocumentTemplate as c, type UseCaseField as d, type UseCaseForm as e, type UseCaseFormField as f, type UseCaseMergeField as g, type UseCaseNotificationRule as h, type UseCaseNotificationTrigger as i, type UseCasePipeline as j, type UseCasePipelineStage as k, type UseCaseProblem as l, type UseCaseProvenance as m, type UseCaseRelationship as n, type UseCaseRow as o, type UseCaseTable as p, type UseCaseVerdict as q, assertUseCase as r, validateUseCase as v };
+export type { BusinessIdentity as B, FormAudience as F, NotificationChannel as N, PostalAddress as P, UseCase as U, UseCaseTable as a, UseCaseField as b, UseCaseRow as c, UseCaseForm as d, UseCaseFormField as e, UseCaseNotificationTrigger as f, UseCaseProvenance as g, UseCaseSummary as h, UseCaseDashboardQuestion as i, UseCaseDocumentTemplate as j, UseCaseMergeField as k, UseCaseNotificationRule as l, UseCasePipeline as m, UseCasePipelineStage as n, UseCaseRelationship as o };