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

package/README.md

@@ -417,7 +417,11 @@ tools: {
     rubric: []
   },
   providers: {
-    calculator: { authFetcher: async () => ({ apiKey: '...' }) },
+    calculator: {
+      provider: {
+        runtime: { authFetcher: async () => ({ apiKey: '...' }) }
+      }
+    },
     textToSpeech: { enabled: true, backend: 'browser' }
   }
 }
@@ -478,7 +482,9 @@ tools: {
   providers: {
     calculator: {
       enabled: true,
-      authFetcher: async () => { /* ... */ }
+      provider: {
+        runtime: { authFetcher: async () => { /* ... */ } }
+      }
     }
   }
 }
@@ -536,9 +542,13 @@ const coordinator = new ToolkitCoordinator({
     providers: {
       calculator: {
         enabled: true,
-        authFetcher: async () => {
-          const response = await fetch('/api/tools/desmos/auth');
-          return response.json();
+        provider: {
+          runtime: {
+            authFetcher: async () => {
+              const response = await fetch('/api/tools/desmos/auth');
+              return response.json();
+            }
+          }
         }
       },
       textToSpeech: { enabled: true, backend: 'browser' }
@@ -565,14 +575,50 @@ const coordinator = new ToolkitCoordinator({
       passage: ['textToSpeech']
     },
     providers: {
-      calculator: { enabled: true },
+      calculator: {
+        enabled: true,
+        provider: {
+          runtime: { authFetcher: fetchLicensedDesmosApiKey }
+        }
+      },
       textToSpeech: { enabled: true, backend: 'browser' }
     }
   }
 });
 ```
 
-The ToolkitCoordinator handles all internal complexity (service initialization, provider management, state coordination). The only special configuration is `authFetcher` for Desmos calculator (optional - falls back to local calculator if not provided).
+The ToolkitCoordinator handles service initialization, provider management, and
+state coordination. With no calculator provider configuration, the existing
+Desmos implementation remains the default and preserves its legacy unkeyed load.
+That fallback is for client compatibility; it does not grant a Desmos license.
+Licensed deployments can supply `provider.init.apiKey` or
+`provider.runtime.authFetcher`. Runtime key delivery avoids committing the key
+but does not hide it from the browser's Desmos script request.
+
+Select the separate GeoGebra implementation explicitly without changing the
+calculator capability, placement, or item policy:
+
+```typescript
+providers: {
+  calculator: {
+    provider: { id: 'calculator-geogebra' },
+    settings: { showResetIcon: true }
+  }
+}
+```
+
+Select the bundled open-source implementation in the same way. It uses no API
+key or runtime network request and supports basic, scientific, and focused
+graphing modes:
+
+```typescript
+providers: {
+  calculator: {
+    provider: { id: 'calculator-cortex' },
+    settings: { angleMode: 'degree', evaluationTimeLimitMs: 1000 }
+  }
+}
+```
 
 ### Minimal Server-Backed TTS Config
 
@@ -834,7 +880,15 @@ export interface ToolkitCoordinatorConfig {
       };
       calculator?: {
         enabled?: boolean;
-        authFetcher?: () => Promise<Record<string, unknown>>;
+        provider?: {
+          id?: 'calculator-desmos' | 'calculator-geogebra' | 'calculator-cortex';
+          init?: Record<string, unknown>;
+          runtime?: {
+            authFetcher?: () => Promise<Record<string, unknown>>;
+          };
+        };
+        settings?: Record<string, unknown>;
+        restrictedMode?: boolean;
       };
     };
   };
@@ -1026,6 +1080,24 @@ const id = highlightCoordinator.addAnnotation(range, 'yellow');
 highlightCoordinator.removeAnnotation(id);
 ```
 
+Reading highlights resolve through five `component-public` tokens registered in
+`packages/theme/src/token-registry.json`:
+
+| Custom property | Default | Description |
+| --- | --- | --- |
+| `--pie-tts-word-highlight` | `--pie-missing` at 68% | Fill behind the current word |
+| `--pie-tts-sentence-highlight` | `--pie-missing` at 38% | Fill behind the current sentence |
+| `--pie-tts-line-highlight` | `--pie-tts-sentence-highlight` | Fill behind the current line |
+| `--pie-tts-word-underline` | `--pie-text` at 70% | Underline marking the current word |
+| `--pie-tts-word-shadow` | `--pie-text` at 35% | Shadow carrying the word over its fill |
+
+The coordinator derives all five from the active theme's accent, text and
+background — opacities clamped to a legible band, and the underline colour picked
+by background luminance so the cue survives a dark scheme — then writes them
+inline on the document element. Inline styles outrank any author selector, so a
+host override takes `!important` and owns the contrast the derivation was
+maintaining, across every scheme it ships.
+
 ### AccessibilityCatalogResolver
 
 ```typescript

package/dist/components/ItemToolBar.custom-element.js

@@ -1 +1 @@
-import{a}from"./chunks/ItemToolBar-9ymm7pd1.js";import"./chunks/ItemToolBar-38mhtjsq.js";export{a as default};
+import{a}from"./chunks/ItemToolBar-pe5szfyx.js";import"./chunks/ItemToolBar-rd7te9r0.js";export{a as default};