@pie-players/pie-assessment-toolkit 0.3.64 → 0.3.65

package/dist/services/ToolkitCoordinator.js

@@ -25,7 +25,7 @@ import { TTSService } from "./TTSService.js";
 import { BrowserTTSProvider } from "./tts/browser-provider.js";
 import { buildRuntimeTTSConfig, resolveTTSBackend, resolveTTSRuntimeSettings, } from "./tts-runtime-config.js";
 import { ToolProviderRegistry } from "./tool-providers/index.js";
-import { createPackagedToolRegistry } from "./createDefaultToolRegistry.js";
+import { ToolRegistry } from "./ToolRegistry.js";
 import { ToolPolicyEngine, } from "../policy/engine.js";
 import { resolveDefaultPnpEnforcement } from "../policy/internal.js";
 const isPlainRecord = (value) => !!value && typeof value === "object" && !Array.isArray(value);
@@ -190,7 +190,13 @@ export class ToolkitCoordinator {
     boundCurrentItemRef = null;
     static resolveConfig(config) {
         const strictness = normalizeToolConfigStrictness(config.toolConfigStrictness);
-        const toolRegistry = config.toolRegistry ?? createPackagedToolRegistry();
+        // An empty registry when the host supplies none. This package no longer
+        // holds the packaged capability set, so there is nothing to fall back to —
+        // a host that wants stock tools passes a registry from
+        // `@pie-players/pie-default-tool-loaders`. Tool-id validation is skipped
+        // against an empty registry (with a diagnostic saying so) rather than
+        // rejecting every configured id.
+        const toolRegistry = config.toolRegistry ?? new ToolRegistry();
         const normalized = config.deferToolConfigValidation === true
             ? normalizeToolsConfig(config.tools)
             : normalizeAndValidateToolsConfig(config.tools, {
@@ -232,8 +238,7 @@ export class ToolkitCoordinator {
         const resolvedConfig = ToolkitCoordinator.resolveConfig(config);
         this.assessmentId = resolvedConfig.assessmentId;
         this.config = resolvedConfig;
-        this.toolRegistry =
-            resolvedConfig.toolRegistry ?? createPackagedToolRegistry();
+        this.toolRegistry = resolvedConfig.toolRegistry ?? new ToolRegistry();
         this.installToolContextResolvers(resolvedConfig.toolContextResolvers);
         this.hooks = resolvedConfig.hooks ?? {};
         this.lazyInit = config.lazyInit === true;
@@ -1268,13 +1273,16 @@ export class ToolkitCoordinator {
                 if (canUseEventTarget) {
                     synth.removeEventListener("voiceschanged", onVoicesChanged);
                 }
-                else if (assignedHandler && synth.onvoiceschanged === onVoicesChanged) {
+                else if (assignedHandler &&
+                    synth.onvoiceschanged === onVoicesChanged) {
                     synth.onvoiceschanged = previousHandler;
                 }
                 resolve();
             };
             const onVoicesChanged = (event) => {
-                if (!canUseEventTarget && typeof previousHandler === "function" && event) {
+                if (!canUseEventTarget &&
+                    typeof previousHandler === "function" &&
+                    event) {
                     previousHandler.call(synth, event);
                 }
                 finish();
@@ -1371,6 +1379,15 @@ export class ToolkitCoordinator {
         if (toolId === "tts") {
             throw new Error(`Tool id "tts" is no longer supported. Use "textToSpeech".`);
         }
+        // An empty registry means the host supplied none, not that every id is
+        // wrong. There is nothing to check an id against, and throwing turns a
+        // host's every tool-config call into an exception — including the calls
+        // this coordinator's own default-provider block provokes, which is how a
+        // host that passes no registry ended up unable to read its own config.
+        // `normalizeAndValidateToolsConfig` already reports the missing registry
+        // once, as `tools.registryUnavailable`; a second report per call is noise.
+        if (this.toolRegistry.getAllToolIds().length === 0)
+            return;
         if (!this.toolRegistry.get(toolId)) {
             throw new Error(`Unknown tool id "${toolId}".`);
         }

package/dist/services/createDefaultToolRegistry.d.ts

@@ -1,86 +1,53 @@
 /**
- * Default Tool Registry Factory
+ * Tool Registry Factory
  *
- * Creates a ToolRegistry pre-populated with all PIE framework tools.
- * Integrators can use this as a starting point and customize as needed.
+ * Creates an empty `ToolRegistry` and installs whatever component overrides and
+ * lazy module loaders the caller supplies.
+ *
+ * It registers nothing by itself, deliberately. Eleven concrete registrations
+ * used to live in this package, which made the policy and registry core know
+ * every capability by name and left a host unable to contribute one without a PR
+ * against this package. The packaged set now lives in the composition layer:
+ * `createPackagedToolRegistry` from `@pie-players/pie-default-tool-loaders`.
  */
+import type { ToolRegistration, ToolModuleLoader } from "./ToolRegistry.js";
 import { ToolRegistry } from "./ToolRegistry.js";
-import type { ToolRegistration } from "./ToolRegistry.js";
-import type { ToolModuleLoader } from "./ToolRegistry.js";
-import { type ToolComponentFactory, type ToolComponentFactoryMap, type ToolTagMap } from "../tools/tool-tag-map.js";
-import { DEFAULT_TOOL_PLACEMENT, PACKAGED_TOOL_PLACEMENT, SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT } from "./tool-config-defaults.js";
+import type { ToolComponentFactory, ToolComponentFactoryMap, ToolTagMap } from "../tools/tool-tag-map.js";
+import { DEFAULT_TOOL_PLACEMENT } from "./tool-config-defaults.js";
 export interface DefaultToolRegistryOptions {
     /**
-     * Override default tool registrations by toolId.
-     * This is the highest-precedence extension point.
+     * Registrations to register, keyed by toolId. Nothing is registered when this
+     * is absent.
      */
-    overrides?: Partial<Record<string, ToolRegistration>>;
+    registrations?: Partial<Record<string, ToolRegistration>>;
     /**
-     * Override default component tag mapping used by built-in registrations.
+     * Element tag mapping for the registrations being installed. There is no
+     * built-in default: a tag map names capabilities, so it belongs to whoever
+     * decides which capabilities exist.
      */
     toolTagMap?: Partial<ToolTagMap>;
     /**
-     * Override component factory globally (all tools) or per tool.
+     * Override component creation globally (all tools) or per tool.
      */
     toolComponentFactory?: ToolComponentFactory;
     toolComponentFactories?: Partial<ToolComponentFactoryMap>;
     /**
      * Optional lazy module loaders keyed by toolId.
-     * Hosts can inject default loaders from an external package.
      */
     toolModuleLoaders?: Partial<Record<string, ToolModuleLoader>>;
-    /**
-     * Register packaged PIE tools by default.
-     *
-     * @default false
-     */
-    includePackagedTools?: boolean;
-    /**
-     * Restrict registration to specific packaged tool IDs.
-     * Ignored when includePackagedTools is false.
-     */
-    toolIds?: string[];
 }
 /**
  * Create a tool registry.
  *
- * By default, this creates an empty registry so hosts can explicitly opt in.
- * For convenience, pass { includePackagedTools: true } to register all packaged tools,
- * or use createPackagedToolRegistry().
- *
- * @returns ToolRegistry with all default tools
+ * @returns an empty `ToolRegistry` unless `registrations` is supplied
  */
 export declare function createDefaultToolRegistry(options?: DefaultToolRegistryOptions): ToolRegistry;
-export interface RegisterPackagedToolsOptions {
-    toolIds?: string[];
-    applyOverrides?: (registration: ToolRegistration) => ToolRegistration;
-}
 /**
- * Register packaged PIE tools onto an existing registry.
- */
-export declare function registerPackagedTools(registry: ToolRegistry, options?: RegisterPackagedToolsOptions): void;
-/**
- * Convenience factory that registers all packaged PIE tools.
- */
-export declare function createPackagedToolRegistry(options?: Omit<DefaultToolRegistryOptions, "includePackagedTools">): ToolRegistry;
-/**
- * Default tool placement configuration
+ * Placement configuration with every level empty.
  *
- * Defines which tools appear at which levels by default.
- * Integrators can override this configuration.
- *
- * Categories:
- * - Global tools: theme (assessment/section level)
- * - Context-smart: calculator, graph, periodicTable (item/element, auto-detect)
- * - Reading aids: textToSpeech, lineReader, annotationToolbar (where text exists)
- * - Interaction-specific: answerEliminator (choice questions), highlighter (text)
- * - Measurement: ruler, protractor (element level, diagram/geometry)
+ * The only placement default this package can hold: a populated one would name
+ * capabilities. `PACKAGED_TOOL_PLACEMENT` and
+ * `SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT` are in
+ * `@pie-players/pie-default-tool-loaders`.
  */
 export { DEFAULT_TOOL_PLACEMENT };
-export { PACKAGED_TOOL_PLACEMENT };
-export { SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT };
-/**
- * Tool priority order for rendering
- * Tools will be rendered in this order when multiple tools are visible
- */
-export declare const DEFAULT_TOOL_ORDER: readonly ["theme", "calculator", "textToSpeech", "lineReader", "annotationToolbar", "highlighter", "answerEliminator", "ruler", "protractor", "graph", "periodicTable"];

package/dist/services/createDefaultToolRegistry.js

@@ -1,125 +1,45 @@
 /**
- * Default Tool Registry Factory
+ * Tool Registry Factory
  *
- * Creates a ToolRegistry pre-populated with all PIE framework tools.
- * Integrators can use this as a starting point and customize as needed.
+ * Creates an empty `ToolRegistry` and installs whatever component overrides and
+ * lazy module loaders the caller supplies.
+ *
+ * It registers nothing by itself, deliberately. Eleven concrete registrations
+ * used to live in this package, which made the policy and registry core know
+ * every capability by name and left a host unable to contribute one without a PR
+ * against this package. The packaged set now lives in the composition layer:
+ * `createPackagedToolRegistry` from `@pie-players/pie-default-tool-loaders`.
  */
 import { ToolRegistry } from "./ToolRegistry.js";
-import { calculatorToolRegistration } from "../tools/registrations/calculator.js";
-import { ttsToolRegistration } from "../tools/registrations/tts.js";
-import { rulerToolRegistration, protractorToolRegistration, } from "../tools/registrations/measurement-tools.js";
-import { answerEliminatorToolRegistration, highlighterToolRegistration, } from "../tools/registrations/interaction-tools.js";
-import { lineReaderToolRegistration, themeToolRegistration, annotationToolbarRegistration, } from "../tools/registrations/accessibility-tools.js";
-import { graphToolRegistration, periodicTableToolRegistration, } from "../tools/registrations/subject-specific-tools.js";
-import { DEFAULT_TOOL_TAG_MAP, } from "../tools/tool-tag-map.js";
-import { DEFAULT_TOOL_PLACEMENT, PACKAGED_TOOL_PLACEMENT, SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT, } from "./tool-config-defaults.js";
-const PACKAGED_TOOL_REGISTRATIONS = [
-    calculatorToolRegistration,
-    ttsToolRegistration,
-    rulerToolRegistration,
-    protractorToolRegistration,
-    answerEliminatorToolRegistration,
-    highlighterToolRegistration,
-    lineReaderToolRegistration,
-    themeToolRegistration,
-    annotationToolbarRegistration,
-    graphToolRegistration,
-    periodicTableToolRegistration,
-];
+import { DEFAULT_TOOL_PLACEMENT } from "./tool-config-defaults.js";
 /**
  * Create a tool registry.
  *
- * By default, this creates an empty registry so hosts can explicitly opt in.
- * For convenience, pass { includePackagedTools: true } to register all packaged tools,
- * or use createPackagedToolRegistry().
- *
- * @returns ToolRegistry with all default tools
+ * @returns an empty `ToolRegistry` unless `registrations` is supplied
  */
 export function createDefaultToolRegistry(options = {}) {
     const registry = new ToolRegistry();
-    const componentConfig = {
-        toolTagMap: {
-            ...DEFAULT_TOOL_TAG_MAP,
-            ...(options.toolTagMap || {}),
-        },
-        toolComponentFactory: options.toolComponentFactory,
-        toolComponentFactories: options.toolComponentFactories,
-    };
-    const applyOverrides = (registration) => options.overrides?.[registration.toolId] || registration;
-    if (options.includePackagedTools) {
-        registerPackagedTools(registry, {
-            toolIds: options.toolIds,
-            applyOverrides,
-        });
+    for (const registration of Object.values(options.registrations ?? {})) {
+        if (registration)
+            registry.register(registration);
     }
     if (options.toolModuleLoaders &&
         Object.keys(options.toolModuleLoaders).length > 0) {
         registry.setToolModuleLoaders(options.toolModuleLoaders);
     }
-    registry.setComponentOverrides(componentConfig);
-    return registry;
-}
-/**
- * Register packaged PIE tools onto an existing registry.
- */
-export function registerPackagedTools(registry, options = {}) {
-    const selectedToolIds = options.toolIds && options.toolIds.length > 0
-        ? new Set(options.toolIds)
-        : null;
-    const applyOverrides = options.applyOverrides ||
-        ((registration) => registration);
-    for (const registration of PACKAGED_TOOL_REGISTRATIONS) {
-        if (selectedToolIds && !selectedToolIds.has(registration.toolId)) {
-            continue;
-        }
-        registry.register(applyOverrides(registration));
-    }
-}
-/**
- * Convenience factory that registers all packaged PIE tools.
- */
-export function createPackagedToolRegistry(options = {}) {
-    return createDefaultToolRegistry({
-        ...options,
-        includePackagedTools: true,
+    registry.setComponentOverrides({
+        toolTagMap: options.toolTagMap,
+        toolComponentFactory: options.toolComponentFactory,
+        toolComponentFactories: options.toolComponentFactories,
     });
+    return registry;
 }
 /**
- * Default tool placement configuration
- *
- * Defines which tools appear at which levels by default.
- * Integrators can override this configuration.
+ * Placement configuration with every level empty.
  *
- * Categories:
- * - Global tools: theme (assessment/section level)
- * - Context-smart: calculator, graph, periodicTable (item/element, auto-detect)
- * - Reading aids: textToSpeech, lineReader, annotationToolbar (where text exists)
- * - Interaction-specific: answerEliminator (choice questions), highlighter (text)
- * - Measurement: ruler, protractor (element level, diagram/geometry)
+ * The only placement default this package can hold: a populated one would name
+ * capabilities. `PACKAGED_TOOL_PLACEMENT` and
+ * `SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT` are in
+ * `@pie-players/pie-default-tool-loaders`.
  */
 export { DEFAULT_TOOL_PLACEMENT };
-export { PACKAGED_TOOL_PLACEMENT };
-export { SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT };
-/**
- * Tool priority order for rendering
- * Tools will be rendered in this order when multiple tools are visible
- */
-export const DEFAULT_TOOL_ORDER = [
-    // Global accessibility first
-    "theme",
-    // Common tools
-    "calculator",
-    "textToSpeech",
-    // Reading aids
-    "lineReader",
-    "annotationToolbar",
-    "highlighter",
-    // Interaction tools
-    "answerEliminator",
-    // Measurement tools
-    "ruler",
-    "protractor",
-    // Subject-specific
-    "graph",
-    "periodicTable",
-];

package/dist/services/defaultPersonalNeedsProfile.d.ts

@@ -1,19 +1,21 @@
 import type { PersonalNeedsProfile } from "@pie-players/pie-players-shared/types";
 /**
- * PNP support ids that must never enter the computed default profile, however
- * they reach the registry.
+ * An empty personal-needs profile: nothing granted, nothing prohibited, nothing
+ * activated at init.
  *
- * `computeDefaultSupports()` derives the fallback profile from every registered
- * tool's `pnpSupportIds`, which is right for universal features — a highlighter
- * or a zoom control should be there for every student by default. It is wrong
- * for an **accommodation**: signing requires a documented need (IEP / 504), so
- * granting it to every host that does not supply its own profile would invert
- * the eligibility tier. Registry membership is about being policy-addressable,
- * not about who may enable it.
+ * The core ships no populated default on purpose. It once derived one from every
+ * registered tool's `pnpSupportIds`, which read *registry membership* as
+ * *eligibility tier* — registration means "policy-addressable", not "universal,
+ * on by default" — so an accommodation-tier capability was granted to every
+ * student of every host that supplied no profile. The remedy at the time was a
+ * compile-time list of ids to exclude, which a host could not extend for its own
+ * accommodation.
  *
- * Excluded here rather than by declining to register, so the guarantee holds
- * even if a signing tool is later registered for some other reason.
+ * Which capabilities a deployment grants by default is a property of the
+ * program, not of this package: TTS is a universal feature in one program and a
+ * documented accommodation in another. That belongs in policy configuration
+ * alongside the district and test-administration levels. A named preset of
+ * today's universal set ships as data from
+ * `@pie-players/pie-default-tool-loaders`, for hosts that want it.
  */
-export declare const ACCOMMODATION_ONLY_SUPPORT_IDS: readonly string[];
-export declare const DEFAULT_PERSONAL_NEEDS_PROFILE: PersonalNeedsProfile;
-export declare function createDefaultPersonalNeedsProfile(): PersonalNeedsProfile;
+export declare function createEmptyPersonalNeedsProfile(): PersonalNeedsProfile;

package/dist/services/defaultPersonalNeedsProfile.js

@@ -1,46 +1,25 @@
-import { createPackagedToolRegistry } from "./createDefaultToolRegistry.js";
 /**
- * PNP support ids that must never enter the computed default profile, however
- * they reach the registry.
+ * An empty personal-needs profile: nothing granted, nothing prohibited, nothing
+ * activated at init.
  *
- * `computeDefaultSupports()` derives the fallback profile from every registered
- * tool's `pnpSupportIds`, which is right for universal features — a highlighter
- * or a zoom control should be there for every student by default. It is wrong
- * for an **accommodation**: signing requires a documented need (IEP / 504), so
- * granting it to every host that does not supply its own profile would invert
- * the eligibility tier. Registry membership is about being policy-addressable,
- * not about who may enable it.
+ * The core ships no populated default on purpose. It once derived one from every
+ * registered tool's `pnpSupportIds`, which read *registry membership* as
+ * *eligibility tier* — registration means "policy-addressable", not "universal,
+ * on by default" — so an accommodation-tier capability was granted to every
+ * student of every host that supplied no profile. The remedy at the time was a
+ * compile-time list of ids to exclude, which a host could not extend for its own
+ * accommodation.
  *
- * Excluded here rather than by declining to register, so the guarantee holds
- * even if a signing tool is later registered for some other reason.
+ * Which capabilities a deployment grants by default is a property of the
+ * program, not of this package: TTS is a universal feature in one program and a
+ * documented accommodation in another. That belongs in policy configuration
+ * alongside the district and test-administration levels. A named preset of
+ * today's universal set ships as data from
+ * `@pie-players/pie-default-tool-loaders`, for hosts that want it.
  */
-export const ACCOMMODATION_ONLY_SUPPORT_IDS = [
-    // QTI 3.0 / AfA `signLanguage`. Signed alternates are rendered by
-    // section-player's per-item media region, gated on this id.
-    "signLanguage",
-];
-function computeDefaultSupports() {
-    const registry = createPackagedToolRegistry();
-    const supports = new Set();
-    const excluded = new Set(ACCOMMODATION_ONLY_SUPPORT_IDS);
-    for (const tool of registry.getAllTools()) {
-        for (const supportId of tool.pnpSupportIds || []) {
-            if (excluded.has(supportId))
-                continue;
-            supports.add(supportId);
-        }
-    }
-    return [...supports].sort();
-}
-const DEFAULT_SUPPORTS = computeDefaultSupports();
-export const DEFAULT_PERSONAL_NEEDS_PROFILE = {
-    supports: [...DEFAULT_SUPPORTS],
-    prohibitedSupports: [],
-    activateAtInit: [],
-};
-export function createDefaultPersonalNeedsProfile() {
+export function createEmptyPersonalNeedsProfile() {
     return {
-        supports: [...DEFAULT_SUPPORTS],
+        supports: [],
         prohibitedSupports: [],
         activateAtInit: [],
     };

package/dist/services/pnp-standard-features.d.ts

@@ -167,7 +167,7 @@ export declare const QTI_STANDARD_ACCESS_FEATURES: {
 /**
  * Flat list of all standard access features for validation
  */
-export declare const ALL_STANDARD_ACCESS_FEATURES: ("transcript" | "braille" | "textToSpeech" | "graph" | "periodicTable" | "calculator" | "answerEliminator" | "ruler" | "protractor" | "graphingCalculator" | "readAloud" | "strikethrough" | "answerMasking" | "readingMask" | "readingGuide" | "readingRuler" | "highContrastDisplay" | "colorContrast" | "invertColors" | "highlighting" | "annotations" | "signLanguage" | "magnification" | "screenMagnifier" | "zoomable" | "highContrastAudio" | "displayTransformability" | "largePrint" | "fontEnlargement" | "resizeText" | "alternativeText" | "longDescription" | "describedMath" | "tactileGraphic" | "tactileObject" | "audioDescription" | "humanVoice" | "syntheticVoice" | "speechRate" | "speechVolume" | "voicePitch" | "captions" | "closedCaptions" | "openCaptions" | "subtitles" | "audioControl" | "noBackgroundAudio" | "keyboardControl" | "mouseControl" | "touchControl" | "voiceControl" | "switchControl" | "eyeGazeControl" | "singleSwitchAccess" | "stickyKeys" | "keyboardShortcuts" | "timingControl" | "unlimitedTime" | "extendedTime" | "pauseControl" | "simplifiedLanguage" | "reducedComplexity" | "structuralNavigation" | "tableOfContents" | "reducedDistraction" | "noFlashing" | "pauseAnimation" | "bookmarking" | "guidedNavigation" | "thesaurus" | "spellingAssistance" | "grammarAssistance" | "lineSpacing" | "wordSpacing" | "letterSpacing" | "fontFamily" | "wordHighlighting" | "lineHighlighting" | "focusIndicator" | "printableResource" | "nemeth" | "refreshableBraille" | "index" | "pageNavigation" | "skipContent" | "breadcrumbs" | "searchable" | "fullTextSearch" | "multilingualText" | "translatedText" | "glossary" | "signLanguageInterpretation" | "visualLanguage" | "formulaSheet" | "itemGlossary" | "tutorialAvailable")[];
+export declare const ALL_STANDARD_ACCESS_FEATURES: ("transcript" | "braille" | "textToSpeech" | "calculator" | "strikethrough" | "answerEliminator" | "magnification" | "screenMagnifier" | "zoomable" | "highContrastDisplay" | "highContrastAudio" | "colorContrast" | "invertColors" | "displayTransformability" | "largePrint" | "fontEnlargement" | "resizeText" | "alternativeText" | "longDescription" | "describedMath" | "tactileGraphic" | "tactileObject" | "audioDescription" | "readAloud" | "humanVoice" | "syntheticVoice" | "speechRate" | "speechVolume" | "voicePitch" | "captions" | "closedCaptions" | "openCaptions" | "signLanguage" | "subtitles" | "audioControl" | "noBackgroundAudio" | "keyboardControl" | "mouseControl" | "touchControl" | "voiceControl" | "switchControl" | "eyeGazeControl" | "singleSwitchAccess" | "stickyKeys" | "keyboardShortcuts" | "timingControl" | "unlimitedTime" | "extendedTime" | "pauseControl" | "simplifiedLanguage" | "reducedComplexity" | "structuralNavigation" | "tableOfContents" | "reducedDistraction" | "noFlashing" | "pauseAnimation" | "annotations" | "bookmarking" | "highlighting" | "guidedNavigation" | "thesaurus" | "spellingAssistance" | "grammarAssistance" | "lineSpacing" | "wordSpacing" | "letterSpacing" | "fontFamily" | "readingMask" | "readingGuide" | "readingRuler" | "wordHighlighting" | "lineHighlighting" | "focusIndicator" | "printableResource" | "nemeth" | "refreshableBraille" | "index" | "pageNavigation" | "skipContent" | "breadcrumbs" | "searchable" | "fullTextSearch" | "multilingualText" | "translatedText" | "glossary" | "signLanguageInterpretation" | "visualLanguage" | "protractor" | "ruler" | "graph" | "graphingCalculator" | "periodicTable" | "formulaSheet" | "answerMasking" | "itemGlossary" | "tutorialAvailable")[];
 /**
  * Example PNP configurations for common accessibility needs
  * These are NOT official profiles but illustrative examples showing

package/dist/services/tool-config-defaults.d.ts

@@ -1,3 +1,10 @@
+/**
+ * Placement defaults this package can hold.
+ *
+ * Only the empty one. `PACKAGED_TOOL_PLACEMENT` and
+ * `SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT` name capabilities, so they moved to
+ * the composition layer (`@pie-players/pie-default-tool-loaders`).
+ */
 export declare const DEFAULT_TOOL_PLACEMENT: {
     readonly assessment: readonly [];
     readonly section: readonly [];
@@ -6,26 +13,3 @@ export declare const DEFAULT_TOOL_PLACEMENT: {
     readonly rubric: readonly [];
     readonly element: readonly [];
 };
-/**
- * Complete placement preset for hosts that want to enable all packaged tools.
- * Prefer explicit host configuration over implicit defaults.
- */
-export declare const PACKAGED_TOOL_PLACEMENT: {
-    readonly assessment: readonly ["theme"];
-    readonly section: readonly ["theme"];
-    readonly item: readonly ["textToSpeech", "highlighter", "annotationToolbar", "graph", "periodicTable"];
-    readonly passage: readonly ["textToSpeech", "highlighter", "annotationToolbar", "lineReader"];
-    readonly rubric: readonly ["textToSpeech", "highlighter", "annotationToolbar", "lineReader"];
-    readonly element: readonly ["calculator", "answerEliminator", "textToSpeech", "ruler", "protractor", "highlighter", "annotationToolbar", "graph", "periodicTable"];
-};
-/**
- * Opt-in section-player placement preset for hosts that want to expose every
- * packaged tool once at its normal assessment surface. This is not exhaustive:
- * `supportedLevels` still defines where tools can run, and hosts can still
- * choose different placement for custom UX.
- */
-export declare const SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT: {
-    section: string[];
-    item: string[];
-    passage: string[];
-};

package/dist/services/tool-config-defaults.js

@@ -1,3 +1,10 @@
+/**
+ * Placement defaults this package can hold.
+ *
+ * Only the empty one. `PACKAGED_TOOL_PLACEMENT` and
+ * `SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT` name capabilities, so they moved to
+ * the composition layer (`@pie-players/pie-default-tool-loaders`).
+ */
 export const DEFAULT_TOOL_PLACEMENT = {
     assessment: [],
     section: [],
@@ -6,49 +13,3 @@ export const DEFAULT_TOOL_PLACEMENT = {
     rubric: [],
     element: [],
 };
-/**
- * Complete placement preset for hosts that want to enable all packaged tools.
- * Prefer explicit host configuration over implicit defaults.
- */
-export const PACKAGED_TOOL_PLACEMENT = {
-    assessment: ["theme"],
-    section: ["theme"],
-    item: [
-        "textToSpeech",
-        "highlighter",
-        "annotationToolbar",
-        "graph",
-        "periodicTable",
-    ],
-    passage: ["textToSpeech", "highlighter", "annotationToolbar", "lineReader"],
-    rubric: ["textToSpeech", "highlighter", "annotationToolbar", "lineReader"],
-    element: [
-        "calculator",
-        "answerEliminator",
-        "textToSpeech",
-        "ruler",
-        "protractor",
-        "highlighter",
-        "annotationToolbar",
-        "graph",
-        "periodicTable",
-    ],
-};
-/**
- * Opt-in section-player placement preset for hosts that want to expose every
- * packaged tool once at its normal assessment surface. This is not exhaustive:
- * `supportedLevels` still defines where tools can run, and hosts can still
- * choose different placement for custom UX.
- */
-export const SECTION_PLAYER_PREFERRED_TOOL_PLACEMENT = {
-    section: [
-        "theme",
-        "graph",
-        "periodicTable",
-        "lineReader",
-        "ruler",
-        "protractor",
-    ],
-    item: ["calculator", "textToSpeech", "answerEliminator", "annotationToolbar"],
-    passage: ["textToSpeech", "annotationToolbar"],
-};

package/dist/services/tool-config-validation.d.ts

@@ -4,7 +4,7 @@ import type { ToolRegistry } from "./ToolRegistry.js";
 export type ToolConfigStrictness = "off" | "warn" | "error";
 export type ToolConfigDiagnosticSeverity = "warning" | "error";
 export interface ToolConfigDiagnostic {
-    code: "tools.unknownToolId" | "tools.unsupportedLevel" | "tools.unknownProviderKey" | "tools.removedProviderKey" | "tools.providerSanitizeFailed" | "tools.providerValidateFailed" | "tools.invalidProviderValidation";
+    code: "tools.unknownToolId" | "tools.unsupportedLevel" | "tools.unplaceableActivation" | "tools.registryUnavailable" | "tools.unknownProviderKey" | "tools.removedProviderKey" | "tools.providerSanitizeFailed" | "tools.providerValidateFailed" | "tools.invalidProviderValidation";
     severity: ToolConfigDiagnosticSeverity;
     path: string;
     message: string;

package/dist/services/tool-config-validation.js

@@ -1,6 +1,5 @@
 import { normalizeToolsConfig, } from "./tools-config-normalizer.js";
 import { frameworkErrorFromToolConfigDiagnostics, frameworkErrorFromUnknown, } from "./framework-error.js";
-import { createPackagedToolRegistry } from "./createDefaultToolRegistry.js";
 export function frameworkErrorFromToolConfigValidation(args) {
     if (Array.isArray(args.diagnostics) && args.diagnostics.length > 0) {
         return frameworkErrorFromToolConfigDiagnostics({
@@ -120,6 +119,20 @@ function collectPlacementDiagnostics(config, toolMap, diagnostics) {
                 }));
                 continue;
             }
+            if (tool.activation === "region") {
+                // A region capability has no toolbar button, so placing it names a
+                // surface that will never render it. Reported at the placement rather
+                // than at render time, where the symptom is an absent accommodation and
+                // no error.
+                diagnostics.push(createDiagnostic({
+                    code: "tools.unplaceableActivation",
+                    severity: "error",
+                    path: `placement.${level}`,
+                    message: `Tool "${toolId}" renders into a host surface (activation "region") and cannot be placed on the ${level} toolbar. Remove it from placement.${level}; its availability comes from policy plus its content dependency.`,
+                    toolId,
+                }));
+                continue;
+            }
             const supportsLevel = tool.supportedLevels.includes(level);
             // Leniency policy: section-capable tools are tolerated in item placement.
             // This avoids strict failures for common host config patterns while still
@@ -204,9 +217,27 @@ function throwValidationError(diagnostics, source) {
 export function normalizeAndValidateToolsConfig(input, options = {}) {
     const strictness = normalizeToolConfigStrictness(options.strictness);
     const source = options.source ?? "tools";
-    const registryTools = getRegistryToolMap(options.toolRegistry ?? createPackagedToolRegistry());
+    const registryTools = getRegistryToolMap(options.toolRegistry);
     const normalized = normalizeToolsConfig(input);
     const diagnostics = [];
+    // Tool-id and provider checks need a registry to check against, and every
+    // collector below returns early without one. Say so: this package no longer
+    // falls back to a packaged registry, so a caller that used to get id
+    // validation for free now gets none, and a silent downgrade from "your ids are
+    // valid" to "nobody looked" is the kind of change that surfaces as a typo
+    // reaching a learner.
+    const hasConfiguredTools = Object.values(normalized.placement).some((ids) => ids.length > 0) ||
+        Object.keys(normalized.providers).length > 0 ||
+        (normalized.policy.allowed?.length ?? 0) > 0 ||
+        (normalized.policy.blocked?.length ?? 0) > 0;
+    if (registryTools.size === 0 && hasConfiguredTools) {
+        diagnostics.push(createDiagnostic({
+            code: "tools.registryUnavailable",
+            severity: "warning",
+            path: "tools",
+            message: 'No tool registry was supplied, so tool ids, placement levels and provider config were not validated. Pass `toolRegistry` — for the packaged capability set, `createPackagedToolRegistry()` from "@pie-players/pie-default-tool-loaders".',
+        }));
+    }
     const hasRemovedTtsKey = Object.hasOwn(normalized.providers, "tts");
     const nextProviders = {
         ...(normalized.providers || {}),
@@ -233,8 +264,17 @@ export function normalizeAndValidateToolsConfig(input, options = {}) {
     if (strictness === "warn") {
         emitWarnings(diagnostics, source);
     }
-    if (strictness === "error" && diagnostics.length > 0) {
-        throwValidationError(diagnostics, source);
+    // Severity decides what `strictness: "error"` rejects. Every diagnostic this
+    // function raised was `"error"` until `tools.registryUnavailable`, which
+    // reports that validation could not run rather than that the config is wrong —
+    // throwing on it would turn "no registry supplied" from a host's existing,
+    // working setup into a construction failure.
+    const blocking = diagnostics.filter((entry) => entry.severity === "error");
+    if (strictness === "error" && blocking.length > 0) {
+        throwValidationError(blocking, source);
+    }
+    if (strictness === "error" && blocking.length === 0) {
+        emitWarnings(diagnostics, source);
     }
     return {
         config: nextConfig,