@pie-players/pie-assessment-toolkit 0.3.67 → 0.3.69

package/dist/tools/internal.d.ts

@@ -20,9 +20,15 @@
  */
 export type { HostedToolContext, HostedToolSize, ResolvedToolContext, ToolActivation, ToolContentDependency, ToolContentDependencyContext, ToolModuleLoader, ToolProviderDescriptor, ToolRegistration, ToolRenderElement, ToolSingletonScope, ToolSurfaceRenderContext, ToolSurfaceRenderResult, ToolSurfaceServices, ToolToolbarButtonDefinition, ToolToolbarRenderResult, ToolWindowShellConfig, ToolbarContext, } from "../services/ToolRegistry.js";
 export { ToolRegistry } from "../services/ToolRegistry.js";
+export { resolveToolRegistrationName } from "../services/ToolRegistry.js";
 export type { CatalogOwnerCard, CatalogOwnerSnapshot, } from "../services/AccessibilityCatalogResolver.js";
+export type { ToolSelectionAction, ToolSelectionContext, } from "../services/selection-action.js";
+export type { ToolOpenRequest, ToolRequestTarget, } from "../services/tool-request.js";
+export { resolveFallbackToolIcon, TOOL_FALLBACK_ICONS, } from "../services/tool-icons.js";
 export type { ContentCapabilityPhase, ContentCapabilityPolicy, ResolveContentCapabilitiesArgs, ResolvedContentCapability, } from "./content-capability-resolution.js";
 export { resolveContentCapabilities } from "./content-capability-resolution.js";
+export type { ToolSurfaceHost, ToolSurfaceHostInput, ToolSurfaceHostOptions, ToolSurfaceHostSnapshot, ToolSurfaceScope, } from "./tool-surface-host.js";
+export { createToolSurfaceHost } from "./tool-surface-host.js";
 export type { ToolContext, ToolLevel } from "../services/tool-context.js";
 export { hasChoiceInteraction, hasMathContent, hasReadableText, hasScienceContent, } from "../services/tool-context.js";
 export { createScopedToolId } from "../services/tool-instance-id.js";
@@ -32,6 +38,6 @@ export { applyOverlaySurface, createScopedVisibilityBinding, syncButtonAndOverla
 export type { ElementToolStateStoreApi, ToolCoordinatorApi, ToolkitCoordinatorApi, TtsServiceApi, } from "../services/interfaces.js";
 export type { ToolPlacementConfig, ToolProviderConfig, } from "../services/tools-config-normalizer.js";
 export type { ToolConfigDiagnostic } from "../services/tool-config-validation.js";
-export { DesmosToolProvider, TTSToolProvider, } from "../services/tool-providers/index.js";
+export { CortexToolProvider, DesmosToolProvider, GeoGebraToolProvider, TTSToolProvider, } from "../services/tool-providers/index.js";
 export type { NormalizedTTSSpeedOption } from "../services/tts-runtime-config.js";
 export { buildRuntimeTTSConfig, normalizeTTSLayoutMode, normalizeTTSSpeedControlOptions, resolveRuntimeProvider, resolveTTSBackend, resolveTTSHostToolbarLayout, resolveTTSLayoutMode, resolveTTSRuntimeSettings, resolveTransportMode, } from "../services/tts-runtime-config.js";

package/dist/tools/internal.js

@@ -19,7 +19,14 @@
  * point — the mechanism is the same one our own registrations use.
  */
 export { ToolRegistry } from "../services/ToolRegistry.js";
+// A registration's own display name in the interface locale. A tool window's
+// title is the registration's name, so the shell needs the same `nameKey`-then-
+// `name` precedence the toolbar uses rather than the raw English field.
+export { resolveToolRegistrationName } from "../services/ToolRegistry.js";
+// So a gateway button and the toolbar button for the same tool draw one icon.
+export { resolveFallbackToolIcon, TOOL_FALLBACK_ICONS, } from "../services/tool-icons.js";
 export { resolveContentCapabilities } from "./content-capability-resolution.js";
+export { createToolSurfaceHost } from "./tool-surface-host.js";
 export { hasChoiceInteraction, hasMathContent, hasReadableText, hasScienceContent, } from "../services/tool-context.js";
 // Scoped tool instance ids, so two placements of one tool do not share state.
 export { createScopedToolId } from "../services/tool-instance-id.js";
@@ -30,5 +37,5 @@ export { applyOverlaySurface, createScopedVisibilityBinding, syncButtonAndOverla
 // stay here rather than moving with the registrations because they are written
 // against the `pie-calculator` and `pie-tts` contract packages, which the
 // toolkit's own `TTSService` and provider registry also depend on.
-export { DesmosToolProvider, TTSToolProvider, } from "../services/tool-providers/index.js";
+export { CortexToolProvider, DesmosToolProvider, GeoGebraToolProvider, TTSToolProvider, } from "../services/tool-providers/index.js";
 export { buildRuntimeTTSConfig, normalizeTTSLayoutMode, normalizeTTSSpeedControlOptions, resolveRuntimeProvider, resolveTTSBackend, resolveTTSHostToolbarLayout, resolveTTSLayoutMode, resolveTTSRuntimeSettings, resolveTransportMode, } from "../services/tts-runtime-config.js";

package/dist/tools/tool-surface-host.d.ts

@@ -0,0 +1,57 @@
+/**
+ * Headless host for capabilities that render into a renderer's surfaces.
+ *
+ * The interface deliberately exposes only current input, a two-boolean snapshot,
+ * and teardown. Discovery, policy/catalog invalidation, content resolution, lazy
+ * loading, DOM reconciliation, error isolation, and registry observation stay
+ * inside this module. Svelte callers are geometry adapters over this seam.
+ *
+ * It lives here rather than in `section-player`, where it was written, because a
+ * second renderer now opens a surface: the annotation toolbar hosts the
+ * capabilities that act on a text selection. Two copies of mount/reconcile/
+ * registry-observation would drift, and the drift would be invisible until one
+ * renderer stopped honouring the grant-AND-content rule. Nothing about the module
+ * was section-shaped — it already imported only from this package — so the move
+ * is a relocation, not a rewrite. The one thing that *was* section-shaped is the
+ * name it reported errors under, which is now {@link ToolSurfaceHostOptions.hostLabel}.
+ */
+import type { CatalogOwnerContext } from "../services/catalog-owner.js";
+import type { ToolRegistry, ToolSurfaceServices } from "../services/ToolRegistry.js";
+export type ToolSurfaceScope = {
+    kind: "content";
+    ownerContext: CatalogOwnerContext;
+} | {
+    kind: "section";
+    assessmentId: string;
+    sectionId: string;
+};
+export interface ToolSurfaceHostInput {
+    anchor: HTMLElement | null;
+    surface: string;
+    registry: ToolRegistry | null;
+    services: ToolSurfaceServices;
+    scope: ToolSurfaceScope;
+}
+export interface ToolSurfaceHostSnapshot {
+    /** At least one capability is eligible, including one still loading. */
+    mountable: boolean;
+    /** At least one capability successfully mounted an element. */
+    occupied: boolean;
+}
+export interface ToolSurfaceHost {
+    update(input: ToolSurfaceHostInput): void;
+    destroy(): void;
+}
+export interface ToolSurfaceHostOptions {
+    /**
+     * Which renderer this host belongs to, for framework-error `source` and console
+     * warnings — `"pie-section-player"`, `"pie-tool-annotation-toolbar"`.
+     *
+     * A warning that named the module but not its renderer would be unactionable
+     * now that two of them mount surfaces: the same `render` failure on the same
+     * `toolId` means different things depending on which surface asked.
+     */
+    hostLabel: string;
+}
+/** Create one lifecycle owner for one host surface anchor. */
+export declare function createToolSurfaceHost(onSnapshot: (snapshot: ToolSurfaceHostSnapshot) => void, options: ToolSurfaceHostOptions): ToolSurfaceHost;