@pie-players/pie-section-player 0.3.44 → 0.3.45

package/dist/components/shared/section-player-host-runtime.d.ts

@@ -6,10 +6,7 @@ import { ItemEntity } from '@pie-players/pie-players-shared';
  * because of the `DEFAULT_PLAYER_DEFINITIONS` dependency, which
  * side-effect-imports `@pie-players/pie-item-player`.
  *
- * Verbatim absorption of the pre-PR-7 `resolvePlayerRuntime` from
- * `section-player-runtime.ts`; behavior is byte-for-byte identical
- * (the existing `tests/section-player-runtime.test.ts` test suite
- * pins this module's export at PR 7).
+ * Pinned by `tests/section-player-runtime.test.ts`.
  */
 export declare function resolvePlayerRuntime(args: {
     effectiveRuntime: Record<string, unknown>;
@@ -43,13 +40,7 @@ export declare function mapRenderablesToItems(renderables: unknown[]): ItemEntit
  * local `resolvePlayerRuntime` so the toolkit core never imports
  * `DEFAULT_PLAYER_DEFINITIONS`.
  *
- * Pre-PR-7 callers used the legacy
- * `resolveSectionPlayerRuntimeState` from `section-player-runtime.ts`;
- * post-PR-7 the legacy file is deleted and this wrapper is the only
- * orchestrator entry point.
- *
- * Behavior is byte-for-byte identical to the pre-PR-7 implementation
- * (pinned by `tests/section-player-runtime.test.ts`).
+ * Pinned by `tests/section-player-runtime.test.ts`.
  */
 export declare function resolveSectionPlayerRuntimeState(args: RuntimeInputs): {
     effectiveToolsConfig: unknown;

package/dist/contracts/layout-contract.d.ts

@@ -1,8 +1,8 @@
 import { SectionPlayerPublicEventName } from './public-events.js';
 export type SectionPlayerLayoutName = "splitpane" | "vertical" | "tabbed";
 export type SectionPlayerLayoutCapability = "items-pane" | "passages-pane" | "section-toolbar" | "item-toolbar" | "passage-toolbar" | "readiness-events" | "navigation-events";
-export type SectionPlayerBasicPropName = "assessmentId" | "section" | "sectionId" | "attemptId" | "debug" | "showToolbar" | "toolbarPosition" | "narrowLayoutBreakpoint" | "contentMaxWidthNoPassage" | "contentMaxWidthWithPassage" | "splitPaneMinRegionWidth" | "splitPaneInitialPassageWidth" | "splitPaneCollapseStrategy" | "enabledTools";
-export type SectionPlayerAdvancedPropName = "runtime" | "playerType" | "player" | "lazyInit" | "tools" | "accessibility" | "coordinator" | "env" | "iifeBundleHost" | "toolRegistry" | "sectionHostButtons" | "itemHostButtons" | "passageHostButtons" | "policies" | "toolConfigStrictness" | "hooks" | "onFrameworkError" | "onStageChange" | "onLoadingComplete";
+export type SectionPlayerBasicPropName = "assessmentId" | "section" | "sectionId" | "attemptId" | "debug" | "showToolbar" | "toolbarPosition" | "narrowLayoutBreakpoint" | "contentMaxWidthNoPassage" | "contentMaxWidthWithPassage" | "splitPaneMinRegionWidth" | "splitPaneInitialPassageWidth" | "splitPaneCollapseStrategy";
+export type SectionPlayerAdvancedPropName = "runtime" | "iifeBundleHost" | "toolRegistry" | "sectionHostButtons" | "itemHostButtons" | "passageHostButtons" | "policies" | "toolConfigStrictness" | "hooks" | "onFrameworkError" | "onStageChange" | "onLoadingComplete";
 export type SectionPlayerLayoutPropName = SectionPlayerBasicPropName | SectionPlayerAdvancedPropName;
 export type SectionPlayerLayoutCommandName = "getSnapshot" | "selectComposition" | "selectNavigation" | "selectReadiness" | "navigateTo" | "navigateNext" | "navigatePrevious" | "getSectionController" | "waitForSectionController";
 export type SectionPlayerLayoutContract = {

package/dist/contracts/public-events.d.ts

@@ -20,7 +20,7 @@
  * session forwarding stays in section-player because the shape is
  * section-player-specific and the engine has no opinion on it.
  *
- * **`framework-error` single-emit on the layout host (compat sweep).**
+ * **`framework-error` single-emit on the layout host.**
  * `<pie-assessment-toolkit>` nested inside a layout CE still
  * dispatches its own `framework-error` (with `bubbles: true,
  * composed: true`) so direct toolkit consumers keep working. The
@@ -30,13 +30,9 @@
  * layout host as the single canonical DOM surface for
  * section-player consumers. The single-emit contract is pinned by
  * `tests/section-player-framework-error-dual-emit.test.ts`. The
- * previous dual-emit was removed in the broad architecture review
- * compat sweep.
+ * layout host does not receive duplicate framework-error events.
  *
- * **Removed in the broad architecture review compat sweep.** The
- * deprecated readiness aliases (`readiness-change`,
- * `interaction-ready`, `ready`) and their `legacy-event-bridge.ts`
- * are gone. Hosts that previously listened for them migrate to:
+ * Lifecycle should be consumed through canonical events:
  *   - `readiness-change` → `pie-stage-change` (the readiness phase
  *     is also reachable via `selectReadiness()` /
  *     `getSnapshot().readiness`).
@@ -44,10 +40,9 @@
  *     `detail.stage === "interactive"`.
  *   - `ready` → `pie-loading-complete`.
  *
- * The deprecated `section-controller-ready` Svelte/DOM event was
- * also removed. Hosts that previously listened for it migrate to
- * `waitForSectionController(timeoutMs)` / `getSectionController()`
- * on the layout CE, or filter `pie-stage-change` for
+ * Controller readiness is available through
+ * `waitForSectionController(timeoutMs)` / `getSectionController()` on the
+ * layout CE, or by filtering `pie-stage-change` for
  * `detail.stage === "engine-ready"`.
  *
  * Source of truth for the names: `players-shared/src/pie/stages.ts`
@@ -86,10 +81,8 @@ export declare const SECTION_PLAYER_PUBLIC_EVENTS: {
 export type SectionPlayerPublicEventName = (typeof SECTION_PLAYER_PUBLIC_EVENTS)[keyof typeof SECTION_PLAYER_PUBLIC_EVENTS];
 /**
  * Readiness phase reported by the engine's readiness derivation. The
- * type is named after the deprecated `readiness-change` event for
- * backward compatibility with consumers that imported it via the
- * kernel's `selectReadiness()` selector — the *event name* is gone,
- * but the readiness payload itself is still the canonical shape.
+ * type preserves the readiness payload shape used by
+ * `selectReadiness()`.
  */
 export type SectionPlayerReadinessPhase = "bootstrapping" | "interaction-ready" | "loading" | "ready" | "error";
 export type SectionPlayerReadinessChangeDetail = {