@pie-players/pie-assessment-toolkit 0.3.74 → 1.0.0-beta.0

package/dist/tools/internal.js

@@ -1,39 +0,0 @@
-/**
- * Registration-authoring surface.
- *
- * What a package outside this one needs to write a `ToolRegistration`: the
- * registration types, the context predicates a tool answers `isVisibleInContext`
- * with, scoped-id and element-creation helpers, the toolbar button/overlay
- * helpers, the provider contract a registration's descriptor creates, and the
- * TTS provider.
- *
- * A separate entry point rather than additions to `.` for the same reason
- * `runtime/internal` and `policy/internal` exist: this is a surface for sibling
- * packages in this repo, not a contract offered to hosts. Widening `.` with two
- * dozen registration-authoring helpers would make every one of them something a
- * host could reasonably expect us to keep.
- *
- * It exists because the packaged registrations moved out to the composition layer
- * (`@pie-players/pie-default-tool-loaders`) so core stops naming capabilities.
- * A host writing its own capability package imports from here too, which is the
- * point — the mechanism is the same one our own registrations use.
- */
-export { resolveToolProviderId, 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";
-export { createToolElement, resolveToolTag, toToolIdFromTag, } from "./tool-tag-map.js";
-// Toolbar button/overlay wiring shared by every toolbar-toggle registration.
-export { applyOverlaySurface, createScopedVisibilityBinding, syncButtonAndOverlayVisibility, } from "./registrations/toolbar-registration-helpers.js";
-// The TTS provider stays here because it is written against the `pie-tts`
-// contract package, which the toolkit's own `TTSService` also depends on.
-export { 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/utils/logger.d.ts

@@ -1,6 +0,0 @@
-export type Logger = (...args: unknown[]) => void;
-/**
- * Minimal logger helper (replacement for PIEOneer’s internal debug logger).
- * We intentionally keep this lightweight and browser-safe.
- */
-export declare function createLogger(namespace: string): Logger;

package/dist/utils/logger.js

@@ -1,10 +0,0 @@
-/**
- * Minimal logger helper (replacement for PIEOneer’s internal debug logger).
- * We intentionally keep this lightweight and browser-safe.
- */
-export function createLogger(namespace) {
-    return (...args) => {
-        // eslint-disable-next-line no-console
-        console.debug(`[${namespace}]`, ...args);
-    };
-}