@inflexa-ai/harness 0.45.0 → 0.46.0

package/dist/contracts/data-profile.d.ts

@@ -30,14 +30,14 @@ export declare const DATA_PROFILE_RUN_LITERAL: "data-profile";
  */
 export type DataProfileSubjectSource = "metadata" | "document" | "filename" | "user-context" | "inferred";
 /** The subject organism, with its provenance and the profiler's confidence in it. */
-export interface DataProfileOrganism {
+export type DataProfileOrganism = {
     scientificName: string;
     /** NCBI Taxonomy ID as a string, e.g. `"9606"`. */
     taxonId: string;
     source: DataProfileSubjectSource;
     confidence: "high" | "medium" | "low";
     notes?: string;
-}
+};
 /**
  * One profiled file's persisted record.
  *
@@ -45,7 +45,7 @@ export interface DataProfileOrganism {
  * them is optional on read, because a snapshot written before the record was widened
  * carries only the pair.
  */
-export interface DataProfileFile {
+export type DataProfileFile = {
     path: string;
     description: string;
     /** Semantic data type (count-matrix, variants, clinical-metadata, document, …). */
@@ -60,14 +60,14 @@ export interface DataProfileFile {
     warnings?: string[];
     /** Flat, identity-establishing facts (sparsity, delimiter, normalizationState, …). */
     metrics?: Record<string, string | number | boolean>;
-}
+};
 /**
  * Dataset-wide quality findings, on rows of the era that recorded them. Superseded by
  * `caveats`, which is agent-authored prose and nothing else.
  */
-export interface DataProfileQualityAssessment {
+export type DataProfileQualityAssessment = {
     concerns: string[];
-}
+};
 /**
  * One repeating set of files — the dataset's structure, as opposed to its contents.
  *
@@ -76,7 +76,7 @@ export interface DataProfileQualityAssessment {
  * the files are the same sort of thing. A singleton is a kind of `count` 1, so a
  * two-file analysis is two kinds and needs no special case.
  */
-export interface DataProfileKind {
+export type DataProfileKind = {
     name: string;
     /** What ONE member represents. The grouping decision, stated apart from the description. */
     memberRepresents: string;
@@ -87,18 +87,18 @@ export interface DataProfileKind {
     format?: string;
     /** Labels of the `axes` that vary across this set's members. */
     axisLabels?: string[];
-}
+};
 /**
  * What varies across a kind's members — the experimental design, as far as it is
  * observable. The scan reports that a filename position varies and which values it
  * takes; what the variation IS is the agent's label.
  */
-export interface DataProfileAxis {
+export type DataProfileAxis = {
     label: string;
     cardinality: number;
     exampleValues?: string[];
     description?: string;
-}
+};
 /**
  * A varying position in a group's display template, as the scan observed it.
  *
@@ -107,7 +107,7 @@ export interface DataProfileAxis {
  * it. The id is scan-scoped — it names the slot within the scan that produced this
  * profile, and a dimension's slot observation refers to it.
  */
-export interface DataProfileGroupSlot {
+export type DataProfileGroupSlot = {
     id: string;
     location: "directory" | "name";
     index: number;
@@ -116,12 +116,12 @@ export interface DataProfileGroupSlot {
     sampleValues: string[];
     /** The slot this one repeats — one token in both a directory segment and the stem is ONE identity. */
     sameAsSlot?: string;
-}
+};
 /** A member the agent wrote about individually. Never exhaustive — that is the filesystem's job. */
-export interface DataProfileMemberAnnotation {
+export type DataProfileMemberAnnotation = {
     path: string;
     note: string;
-}
+};
 /**
  * Companion coverage across a group, computed per member.
  *
@@ -129,7 +129,7 @@ export interface DataProfileMemberAnnotation {
  * average hides the one member whose index is missing, and that is the member a
  * downstream step fails on.
  */
-export interface DataProfileCompanionCompleteness {
+export type DataProfileCompanionCompleteness = {
     expectedCompanions: string[];
     completeMembers: number;
     incompleteMembers: number;
@@ -137,7 +137,7 @@ export interface DataProfileCompanionCompleteness {
         path: string;
         missingCompanions: string[];
     }[];
-}
+};
 /**
  * One declared group — a claim about MEANING, resolved to a membership.
  *
@@ -146,7 +146,7 @@ export interface DataProfileCompanionCompleteness {
  * `displayPattern` is the scanner's own template and is display-only: no agent authored
  * it, and nothing computes membership from it.
  */
-export interface DataProfileGroup {
+export type DataProfileGroup = {
     /** Stable within the profile, derived from the group's name. */
     id: string;
     name: string;
@@ -176,12 +176,12 @@ export interface DataProfileGroup {
     completeness?: DataProfileCompanionCompleteness;
     /** True for the swept residue — files no operation claimed. Visible by construction. */
     unclassified?: boolean;
-}
+};
 /** A measurement that was actually performed. Absent means unchecked, never "no overlap". */
-export interface DataProfileChecked {
+export type DataProfileChecked = {
     matched: number;
     of: number;
-}
+};
 /**
  * Where a slot observation points, in terms that survive the scan that produced it.
  *
@@ -191,10 +191,10 @@ export interface DataProfileChecked {
  * resolves strands the profile rather than rebinding to whatever now sits at that
  * position.
  */
-export interface DataProfileSlotBinding {
+export type DataProfileSlotBinding = {
     template: string;
     slotIndex: number;
-}
+};
 /**
  * One evidenced sighting of a dimension.
  *
@@ -248,7 +248,7 @@ export type DataProfileObservation = {
  * There is no canonical cardinality: observations that disagree both stand, and
  * `reconciliations` carries the delta. A renderer shows the numbers side by side.
  */
-export interface DataProfileDimension {
+export type DataProfileDimension = {
     label: string;
     category: string;
     categoryLabel?: string;
@@ -266,9 +266,9 @@ export interface DataProfileDimension {
     };
     /** Why the dataset deviates from the category's default treatment. */
     treatmentReason?: string;
-}
+};
 /** What the agent found when it looked for one of the standard dimensions. */
-export interface DataProfileProbeReport {
+export type DataProfileProbeReport = {
     probe: string;
     outcome: "found" | "not-found" | "found-but-constant" | "attested";
     dimension?: string;
@@ -278,9 +278,9 @@ export interface DataProfileProbeReport {
     evidence?: string;
     citation?: string;
     path?: string;
-}
+};
 /** Files the scan removed before structure was observed, with why. */
-export interface DataProfileQuarantine {
+export type DataProfileQuarantine = {
     count: number;
     totalBytes: number;
     reasons: {
@@ -288,7 +288,7 @@ export interface DataProfileQuarantine {
         count: number;
     }[];
     sample: string[];
-}
+};
 /**
  * The census, derived rather than declared.
  *
@@ -296,7 +296,7 @@ export interface DataProfileQuarantine {
  * Quarantined files are accounted separately, with their reasons. That the numbers sum
  * is what turns "how much did the profile cover" from a question into a fact.
  */
-export interface DataProfilePartition {
+export type DataProfilePartition = {
     scannedFiles: number;
     keptFiles: number;
     keptMembers: number;
@@ -315,7 +315,7 @@ export interface DataProfilePartition {
     };
     /** True when the walk stopped at its file ceiling, so the census covers part of the tree. */
     scanTruncated?: boolean;
-}
+};
 /**
  * One operation, keyed to the scanner TEMPLATES it addressed rather than the menu ids.
  *
@@ -328,7 +328,7 @@ export interface DataProfilePartition {
  * an unchanged tree re-absorbs as partial and wakes the agent to re-judge what it already
  * judged.
  */
-export interface DataProfileRecipeStep {
+export type DataProfileRecipeStep = {
     op: "use" | "split" | "merge" | "group" | "unclassified";
     /** The templates this step addressed. Empty for an explicit path grouping. */
     templates: string[];
@@ -343,7 +343,7 @@ export interface DataProfileRecipeStep {
     /** True when `paths` holds a prefix of the step's membership rather than all of it. */
     pathsTruncated?: boolean;
     groupIds: string[];
-}
+};
 /**
  * The record of WHICH files a profile covered and of the bytes behind them.
  *
@@ -352,10 +352,10 @@ export interface DataProfileRecipeStep {
  * content hashes deliberately: a content hash means a full read of every input. Two
  * inputs with the same byte length and mtime therefore give the same digest.
  */
-export interface DataProfileInputSignature {
+export type DataProfileInputSignature = {
     count: number;
     digest: string;
-}
+};
 /**
  * How much of the scanned tree the profile's kinds describe.
  *
@@ -365,12 +365,12 @@ export interface DataProfileInputSignature {
  * one that classified all of them, so it read as complete and fresh. Coverage does NOT by
  * itself drive a re-profile, because some input sets legitimately resist classification.
  */
-export interface DataProfileCoverage {
+export type DataProfileCoverage = {
     matched: number;
     unmatched: number;
     total: number;
     unmatchedSample?: string[];
-}
+};
 /**
  * The profile snapshot stored in `cortex_analysis_state.data_profile_result`.
  *
@@ -391,7 +391,7 @@ export interface DataProfileCoverage {
  * field: optionality is the compatibility mechanism, and a discriminator would be a
  * second mechanism answering the same question.
  */
-export interface DataProfileResult {
+export type DataProfileResult = {
     summary: string;
     /** The resolved groups the tree partitions into, `unclassified` included. */
     groups?: DataProfileGroup[];
@@ -436,6 +436,6 @@ export interface DataProfileResult {
     experimentalDesign?: string;
     /** Dataset-wide findings, on a snapshot of the era that recorded them. Superseded by `caveats`. */
     qualityAssessment?: DataProfileQualityAssessment;
-}
+};
 /** The profile's lifecycle, as the ledger records it. */
 export type DataProfileLifecycleStatus = "pending" | "running" | "completed" | "failed";

package/dist/contracts/index.d.ts

@@ -2,15 +2,15 @@ export { ORGAN_SYSTEMS, OrganSystemSchema, ORGAN_SYSTEM_LABELS, organSystemLabel
 export type { OrganSystem } from "./organ-system.js";
 export { SEVERITIES, SeveritySchema } from "./severity.js";
 export type { Severity } from "./severity.js";
-export type { PlanStep, PresentationContent, PresentationPart, PlanPart, RunCardPart, PlanApprovalPart, FileReferenceEntry, FileReferencePart, AskPart, RunStartedPart, StepStatus, DagStepState, PlanGraphStep, DagStatePart, StepPhase, StepActivityPart, ActivityEntryPart, SubAgentActivityEntry, SubAgentActivityPart, FileTreeEntry, StepFileTreePart, StepOutputFile, StepOutputPart, StepSummaryPart, StepUsagePart, StepBlockedPart, FindingReference, SynthesizedFinding, BiologicalTheme, RunSynthesisPart, SynthesisPhase, SynthesisProgressPart, RunCompletedFinding, RunCompletedPart, RunFailedPart, ChildSessionStartedPart, ReportRenderedPart, CompactionPart, ChatPart, } from "./chat-parts.js";
-export type { EventSource, TextDeltaEvent, IterationEvent, ToolStartedEvent, ToolFinishedEvent, FinishEvent, ChatErrorEvent, ChatEvent, ChatFrame, ChatPartFrame, } from "./chat-events.js";
+export type { PlanStep, PresentationContent, PresentationPart, PlanPart, RunCardPart, PlanApprovalPart, FileReferenceEntry, FileReferencePart, AskPart, RunStartedPart, StepStatus, DagStepState, PlanGraphStep, DagStatePart, StepPhase, StepActivityPart, ActivityEntryPart, SubAgentActivityEntry, SubAgentActivityPart, FileTreeEntry, StepFileTreePart, StepOutputFile, StepOutputPart, StepSummaryPart, StepUsagePart, StepBlockedPart, FindingReference, SynthesizedFinding, BiologicalTheme, RunSynthesisPart, SynthesisPhase, SynthesisProgressPart, RunCompletedFinding, RunCompletedPart, RunFailedPart, ChildSessionStartedPart, ReportRenderedPart, CompactionPart, PauseCause, WorkKind, PausePart, ModelRetryPart, ChatPart, KnownChatPart, } from "./chat-parts.js";
+export type { EventSource, TextDeltaEvent, IterationEvent, ToolStartedEvent, ToolFinishedEvent, FinishEvent, ChatErrorEvent, MessageStartEvent, ChatEvent, ChatFrame, ChatPartFrame, } from "./chat-events.js";
 export type { TokenUsageRollup } from "./usage.js";
 export { DATA_PROFILE_RUN_LITERAL } from "./data-profile.js";
 export type { DataProfileAxis, DataProfileChecked, DataProfileCompanionCompleteness, DataProfileCoverage, DataProfileDimension, DataProfileFile, DataProfileGroup, DataProfileGroupSlot, DataProfileInputSignature, DataProfileKind, DataProfileLifecycleStatus, DataProfileMemberAnnotation, DataProfileObservation, DataProfileOrganism, DataProfilePartition, DataProfileProbeReport, DataProfileQualityAssessment, DataProfileQuarantine, DataProfileRecipeStep, DataProfileResult, DataProfileSubjectSource, } from "./data-profile.js";
 export { DIMENSION_CATEGORIES, DIMENSION_CATEGORY_IDS, DIMENSION_PROBE_IDS, DIMENSION_PROBES, GROUP_CATEGORIES, GROUP_CATEGORY_IDS, GROUP_ROLE_IDS, GROUP_ROLES, PROBE_OUTCOME_IDS, dimensionCategoryEntry, dimensionScope, groupCategoryEntry, } from "./profile-vocabulary.js";
 export type { DimensionCategory, DimensionCategoryEntry, DimensionProbe, DimensionProbeEntry, DimensionScope, DimensionTreatment, GroupCategory, GroupCategoryEntry, GroupRole, GroupRoleEntry, ProbeOutcome, } from "./profile-vocabulary.js";
 export type { TextPart, ToolCallPart, MessagePart, ChatMessage } from "./message.js";
-export { toChatFrame, applyChatFrame, checkChatPart } from "./chat-frame.js";
+export { toChatFrame, applyChatFrame, checkChatPart, isKnownPartFrame } from "./chat-frame.js";
 export type { TurnTerminal, ApplyFrameResult, ChatPartCheck } from "./chat-frame.js";
 export { createSubAgentActivityTracker, SUBAGENT_ACTIVITY_MAX_ENTRIES } from "./subagent-activity.js";
 export type { SubAgentActivityTracker } from "./subagent-activity.js";

package/dist/contracts/index.js

@@ -2,7 +2,7 @@ export { ORGAN_SYSTEMS, OrganSystemSchema, ORGAN_SYSTEM_LABELS, organSystemLabel
 export { SEVERITIES, SeveritySchema } from "./severity.js";
 export { DATA_PROFILE_RUN_LITERAL } from "./data-profile.js";
 export { DIMENSION_CATEGORIES, DIMENSION_CATEGORY_IDS, DIMENSION_PROBE_IDS, DIMENSION_PROBES, GROUP_CATEGORIES, GROUP_CATEGORY_IDS, GROUP_ROLE_IDS, GROUP_ROLES, PROBE_OUTCOME_IDS, dimensionCategoryEntry, dimensionScope, groupCategoryEntry, } from "./profile-vocabulary.js";
-export { toChatFrame, applyChatFrame, checkChatPart } from "./chat-frame.js";
+export { toChatFrame, applyChatFrame, checkChatPart, isKnownPartFrame } from "./chat-frame.js";
 export { createSubAgentActivityTracker, SUBAGENT_ACTIVITY_MAX_ENTRIES } from "./subagent-activity.js";
 export { PART_REGISTRY, isTransient, isReconciling, isSidebarPart } from "./part-registry.js";
 export { AnalogyCoverageSchema, AnalogyReportSchema, AnalogyReportErrorSchema, AnalogicalReasonerOutputSchema } from "./analogy-report.js";

package/dist/contracts/message.d.ts

@@ -10,10 +10,10 @@ import type { ToolCallDetail, ToolCallOutcome } from "./chat-events.js";
 import type { ChatPart } from "./chat-parts.js";
 import type { TokenUsageRollup } from "./usage.js";
 /** A plain assistant/user text run. */
-export interface TextPart {
+export type TextPart = {
     type: "text";
     text: string;
-}
+};
 /**
  * A tool call observed during the turn (or replayed from history).
  *
@@ -27,7 +27,7 @@ export interface TextPart {
  * switch on this single field and be told by the compiler when it misses a case,
  * rather than each host inventing what "no outcome" means and disagreeing.
  */
-export interface ToolCallPart {
+export type ToolCallPart = {
     type: "tool-call";
     toolCallId: string;
     toolName: string;
@@ -40,11 +40,11 @@ export interface ToolCallPart {
     detail?: ToolCallDetail;
     /** The time in milliseconds around the dispatch of the call, from `tool-finished`. Absent when no measurement was taken. */
     durationMs?: number;
-}
+};
 /** The discriminated union of every part the chat path can carry. */
 export type MessagePart = TextPart | ToolCallPart | ChatPart;
 /** A single chat message — user, assistant, or system. */
-export interface ChatMessage {
+export type ChatMessage = {
     id: string;
     role: "user" | "assistant" | "system";
     parts: MessagePart[];
@@ -91,4 +91,4 @@ export interface ChatMessage {
      * backs the message — a live surface builds one before anything is written.
      */
     createdAt?: string;
-}
+};

package/dist/contracts/organ-system.d.ts

@@ -17,24 +17,24 @@
 import { z } from "zod";
 export declare const ORGAN_SYSTEMS: readonly ["cardiac", "vascular", "hepatic", "renal", "cns", "pns", "gi", "pancreas", "endocrine_thyroid", "metabolic", "hematologic", "immune", "respiratory", "reproductive", "musculoskeletal", "dermatologic", "ocular", "oncology"];
 export declare const OrganSystemSchema: z.ZodEnum<{
+    cardiac: "cardiac";
+    cns: "cns";
+    dermatologic: "dermatologic";
+    endocrine_thyroid: "endocrine_thyroid";
+    gi: "gi";
     hematologic: "hematologic";
-    metabolic: "metabolic";
-    immune: "immune";
     hepatic: "hepatic";
+    immune: "immune";
+    metabolic: "metabolic";
     musculoskeletal: "musculoskeletal";
-    cns: "cns";
+    ocular: "ocular";
+    oncology: "oncology";
+    pancreas: "pancreas";
+    pns: "pns";
     renal: "renal";
     reproductive: "reproductive";
     respiratory: "respiratory";
-    cardiac: "cardiac";
     vascular: "vascular";
-    pns: "pns";
-    gi: "gi";
-    pancreas: "pancreas";
-    endocrine_thyroid: "endocrine_thyroid";
-    dermatologic: "dermatologic";
-    ocular: "ocular";
-    oncology: "oncology";
 }>;
 export type OrganSystem = (typeof ORGAN_SYSTEMS)[number];
 /**

package/dist/contracts/part-registry.d.ts

@@ -1,8 +1,8 @@
-import type { ChatPart } from "./chat-parts.js";
-export type ChatPartType = ChatPart["type"];
+import type { KnownChatPart } from "./chat-parts.js";
+export type ChatPartType = KnownChatPart["type"];
 export type PartEmitter = "workflow" | "conversation";
 export type PartConsumer = "sidebar" | "conversation";
-export interface PartDescriptor {
+export type PartDescriptor = {
     /** Which layer emits this part. */
     emitter: PartEmitter;
     /** Which UI surface consumes this part. */
@@ -11,8 +11,9 @@ export interface PartDescriptor {
     transient: boolean;
     /** If true, multiple emissions share the same id — latest wins. */
     reconciling: boolean;
-}
+};
 export declare const PART_REGISTRY: Record<ChatPartType, PartDescriptor>;
 export declare function isTransient(type: ChatPartType): boolean;
+export declare function isKnownPartType(type: string): type is ChatPartType;
 export declare function isReconciling(type: ChatPartType): boolean;
 export declare function isSidebarPart(type: ChatPartType): boolean;

package/dist/contracts/part-registry.js

@@ -22,10 +22,15 @@ export const PART_REGISTRY = {
     "data-child-session-started": { emitter: "conversation", consumer: "conversation", transient: false, reconciling: false },
     "data-report-rendered": { emitter: "conversation", consumer: "conversation", transient: false, reconciling: false },
     "data-compaction": { emitter: "conversation", consumer: "conversation", transient: true, reconciling: true },
+    "data-pause": { emitter: "workflow", consumer: "conversation", transient: false, reconciling: true },
+    "data-model-retry": { emitter: "conversation", consumer: "conversation", transient: true, reconciling: true },
 };
 export function isTransient(type) {
     return PART_REGISTRY[type].transient;
 }
+export function isKnownPartType(type) {
+    return Object.hasOwn(PART_REGISTRY, type);
+}
 export function isReconciling(type) {
     return PART_REGISTRY[type].reconciling;
 }

package/dist/contracts/profile-vocabulary.d.ts

@@ -9,7 +9,7 @@
  * It lives in `contracts/` because the persisted profile carries these ids: a consumer
  * rendering a stored group needs the category's meaning without importing the ledger,
  * the schema module, or zod. Hosts do not extend it — the package owns the catalogue and
- * versions it with the harness.
+ * versions it with the harness. Each import from outside `contracts/` is a type import.
  *
  * Every category carries its nearest neighbour and the rule that separates them, because
  * a category list without one is a list of labels an author picks by vibe. Every
@@ -19,10 +19,10 @@
  */
 export declare const GROUP_ROLE_IDS: readonly ["data", "metadata", "index", "documentation", "reference"];
 export type GroupRole = (typeof GROUP_ROLE_IDS)[number];
-export interface GroupRoleEntry {
+export type GroupRoleEntry = {
     readonly id: GroupRole;
     readonly definition: string;
-}
+};
 /**
  * Companions (`.bai`/`.tbi`/per-file `.md5`) take no role — they attach to members. A
  * checksum or inventory file spanning MANY members is not a companion but a member of
@@ -32,12 +32,12 @@ export interface GroupRoleEntry {
 export declare const GROUP_ROLES: readonly GroupRoleEntry[];
 export declare const GROUP_CATEGORY_IDS: readonly ["sequencing-reads", "alignment", "variant-calls", "copy-number", "structural-variants", "association-results", "regions-signal", "expression-matrix", "single-cell-matrix", "methylation", "proteomics", "metabolomics", "cytometry", "chemical-structures", "imaging", "clinical-table", "sample-annotation", "code", "document", "manifest", "reference-data", "other"];
 export type GroupCategory = (typeof GROUP_CATEGORY_IDS)[number];
-export interface GroupCategoryEntry {
+export type GroupCategoryEntry = {
     readonly id: GroupCategory;
     readonly definition: string;
     /** The nearest neighbour and the rule that separates them. */
     readonly note: string;
-}
+};
 /**
  * Coarse on purpose — a free `subtype` refines below the category. Content beats shape:
  * a beta-value matrix is methylation whatever its layout, and a MAF is variant-calls
@@ -54,14 +54,14 @@ export type DimensionScope = "biological" | "technical";
  * slot, possibly bound to a dimension.
  */
 export type DimensionTreatment = "split" | "dimension";
-export interface DimensionCategoryEntry {
+export type DimensionCategoryEntry = {
     readonly id: DimensionCategory;
     readonly scope: DimensionScope;
     readonly definition: string;
     readonly defaultTreatment: DimensionTreatment;
     /** Why the default reads the way it does, and the nearest neighbour it is not. */
     readonly note: string;
-}
+};
 export declare const DIMENSION_CATEGORIES: readonly DimensionCategoryEntry[];
 export declare const DIMENSION_PROBE_IDS: readonly ["subject", "sample", "cohort-arm", "timepoint", "batch"];
 export type DimensionProbe = (typeof DIMENSION_PROBE_IDS)[number];
@@ -74,11 +74,11 @@ export type DimensionProbe = (typeof DIMENSION_PROBE_IDS)[number];
  */
 export declare const PROBE_OUTCOME_IDS: readonly ["found", "not-found", "found-but-constant", "attested"];
 export type ProbeOutcome = (typeof PROBE_OUTCOME_IDS)[number];
-export interface DimensionProbeEntry {
+export type DimensionProbeEntry = {
     readonly id: DimensionProbe;
     /** Where a `found` typically comes from. */
     readonly guidance: string;
-}
+};
 /**
  * The only dimensions the agent actively looks for. The searchable set is bounded and
  * named: files in metadata- or documentation-role groups plus clinical-table and
@@ -100,4 +100,5 @@ export declare function dimensionCategoryEntry(id: DimensionCategory): Dimension
  * a biological thing that varies and has no category is still biological, and pinning
  * every `other` to technical would misfile it. Undeclared, it defaults to technical.
  */
-export declare function dimensionScope(id: DimensionCategory, declared?: DimensionScope): DimensionScope;
+/** A replay can carry a category a retired vocabulary served; the lookup below settles the miss as `technical`. */
+export declare function dimensionScope(id: DimensionCategory | (string & {}), declared?: DimensionScope): DimensionScope;

package/dist/contracts/profile-vocabulary.js

@@ -9,7 +9,7 @@
  * It lives in `contracts/` because the persisted profile carries these ids: a consumer
  * rendering a stored group needs the category's meaning without importing the ledger,
  * the schema module, or zod. Hosts do not extend it — the package owns the catalogue and
- * versions it with the harness.
+ * versions it with the harness. Each import from outside `contracts/` is a type import.
  *
  * Every category carries its nearest neighbour and the rule that separates them, because
  * a category list without one is a list of labels an author picks by vibe. Every
@@ -429,10 +429,16 @@ export const DIMENSION_PROBES = [
 const GROUP_CATEGORY_BY_ID = new Map(GROUP_CATEGORIES.map((entry) => [entry.id, entry]));
 const DIMENSION_CATEGORY_BY_ID = new Map(DIMENSION_CATEGORIES.map((entry) => [entry.id, entry]));
 export function groupCategoryEntry(id) {
-    return GROUP_CATEGORY_BY_ID.get(id);
+    const entry = GROUP_CATEGORY_BY_ID.get(id);
+    if (entry === undefined)
+        throw new Error(`the group category entry "${id}" is absent`);
+    return entry;
 }
 export function dimensionCategoryEntry(id) {
-    return DIMENSION_CATEGORY_BY_ID.get(id);
+    const entry = DIMENSION_CATEGORY_BY_ID.get(id);
+    if (entry === undefined)
+        throw new Error(`the dimension category entry "${id}" is absent`);
+    return entry;
 }
 /**
  * The scope a dimension takes.
@@ -442,6 +448,7 @@ export function dimensionCategoryEntry(id) {
  * a biological thing that varies and has no category is still biological, and pinning
  * every `other` to technical would misfile it. Undeclared, it defaults to technical.
  */
+/** A replay can carry a category a retired vocabulary served; the lookup below settles the miss as `technical`. */
 export function dimensionScope(id, declared) {
     if (id === "other")
         return declared ?? "technical";