@pie-players/pie-section-player 0.3.73 → 0.3.75

package/dist/components/item-shell-element.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/components/shared/shell-registration.d.ts

@@ -1,55 +0,0 @@
-/**
- * Registration dispatch for the item and passage shells.
- *
- * Registration is a statement of fact to the runtime, and the runtime takes it
- * literally: a `pie-register` makes the toolkit unregister and re-register the
- * content's accessibility catalogs, re-run `sectionEngine.register`, and
- * re-notify the section controller. Both shells used to dispatch it from the
- * same effect that attached their listeners, with `pie-unregister` in that
- * effect's cleanup — so every re-run announced a teardown and a rebuild of state
- * that had not moved, and between the two the content had no catalogs at all.
- *
- * Those effects re-run on prop changes, and a shell's props are re-applied
- * whenever its parent card's template updates. That made the dispatch the far
- * half of a cycle: a reader that re-renders in response to a catalog change
- * re-applies a shell's props, which re-registers, which changes catalogs again.
- * It shipped once at roughly a thousand rounds per item, ending in Svelte
- * abandoning the update at its depth limit with the DOM half-applied — and every
- * assertion about the rendered output passed while it was happening, because the
- * elements were all present.
- *
- * So the dispatcher keeps the last identity it announced and says nothing when
- * the next one matches.
- */
-export type ShellRegistrationIdentity = {
-    kind: "item" | "passage";
-    host: HTMLElement;
-    itemId: string;
-    canonicalItemId: string;
-    contentKind: string;
-    item: unknown;
-};
-export type ShellRegistrationDispatcher = {
-    /**
-     * Announce `identity` if it says anything new, and retire the live
-     * registration when there is nothing left to describe — a shell without a host
-     * or an id no longer stands for content, and leaving its registration behind
-     * would strand it in the runtime.
-     *
-     * Never dispatches `pie-unregister` before a re-register: both registration
-     * paths in the toolkit are keyed by element and replace what is there, so the
-     * unregister only ever created the gap.
-     */
-    sync: (identity: ShellRegistrationIdentity | null) => void;
-    /**
-     * Retire the live registration, replaying the identity it was made under
-     * rather than whatever the props say now — by the time a registration is
-     * retired the props may already describe its replacement, and unregistering
-     * under the new identity would leave the old one live.
-     *
-     * Belongs in a teardown that runs on teardown only. Attaching it to an effect
-     * that re-runs on prop changes is what made the churn.
-     */
-    retire: () => void;
-};
-export declare function createShellRegistrationDispatcher(): ShellRegistrationDispatcher;

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

@@ -1,17 +0,0 @@
-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";
-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 = {
-    version: 1;
-    layout: SectionPlayerLayoutName;
-    props: readonly SectionPlayerLayoutPropName[];
-    recommendedBasicProps: readonly SectionPlayerBasicPropName[];
-    advancedEscapeHatchProps: readonly SectionPlayerAdvancedPropName[];
-    events: readonly SectionPlayerPublicEventName[];
-    commands: readonly SectionPlayerLayoutCommandName[];
-    capabilities: readonly SectionPlayerLayoutCapability[];
-};

package/dist/contracts/layout-parity-metadata.d.ts

@@ -1,4 +0,0 @@
-import { SectionPlayerLayoutContract } from './layout-contract.js';
-export declare const SPLITPANE_LAYOUT_CONTRACT: SectionPlayerLayoutContract;
-export declare const VERTICAL_LAYOUT_CONTRACT: SectionPlayerLayoutContract;
-export declare const TABBED_LAYOUT_CONTRACT: SectionPlayerLayoutContract;

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

@@ -1,93 +0,0 @@
-/**
- * Section-player layout-CE public DOM event vocabulary.
- *
- * **Engine routing (M7).** The *stage / loading-complete /
- * framework-error* family is dispatched on the layout CE host by the
- * section runtime engine
- * (`@pie-players/pie-assessment-toolkit/runtime/engine`) — not by an
- * in-CE `$effect` cluster. The kernel attaches the engine to the host
- * (`engine.attachHost({ host, sourceCe, frameworkErrorBus })`), and
- * the engine's DOM-event bridge dispatches `pie-stage-change`,
- * `pie-loading-complete`, and `framework-error`.
- *
- * **Kernel-side Svelte forwards (not engine-routed).** The
- * composition / session / runtime-tier family
- * (`composition-changed`, `session-changed`, `runtime-owned`,
- * `runtime-inherited`) is forwarded by the kernel's Svelte
- * `createEventDispatcher` from `<pie-section-player-base>` events; it
- * does not flow through the engine. This split is intentional: the
- * engine owns lifecycle and error reporting, while composition /
- * 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.**
- * `<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
- * kernel's `handleFrameworkError` listener intercepts that bubbled
- * emit at `<pie-section-player-base>` and calls
- * `event.stopPropagation()`, leaving the engine-bridge emit on the
- * 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
- * layout host does not receive duplicate framework-error events.
- *
- * Lifecycle should be consumed through canonical events:
- *   - `readiness-change` → `pie-stage-change` (the readiness phase
- *     is also reachable via `selectReadiness()` /
- *     `getSnapshot().readiness`).
- *   - `interaction-ready` → `pie-stage-change` filtered on
- *     `detail.stage === "interactive"`.
- *   - `ready` → `pie-loading-complete`.
- *
- * 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`
- * and the `SectionEngineOutput` discriminator in
- * `assessment-toolkit/src/runtime/core/engine-output.ts`.
- */
-export declare const SECTION_PLAYER_PUBLIC_EVENTS: {
-    readonly runtimeOwned: "runtime-owned";
-    readonly runtimeInherited: "runtime-inherited";
-    /**
-     * Engine-routed (M7). Dispatched by
-     * `framework-error-bridge.ts` on the layout CE host whenever the
-     * engine receives a `framework-error` input. See class doc on
-     * `FrameworkErrorBus` for the back-pressure / fan-out semantics.
-     */
-    readonly frameworkError: "framework-error";
-    readonly compositionChanged: "composition-changed";
-    readonly sessionChanged: "session-changed";
-    /**
-     * Engine-routed (M7). One DOM event family carries every stage
-     * transition (`composed` → `engine-ready` → `interactive` →
-     * `disposed`) with the discriminator in `event.detail.stage`.
-     * Dispatched by the engine's `dom-event-bridge.ts` on each
-     * `SectionEngineOutput` of kind `stage-change`. See
-     * `packages/players-shared/src/pie/stages.ts`.
-     */
-    readonly stageChange: "pie-stage-change";
-    /**
-     * Engine-routed (M7). Companion to `stageChange`. Fires once per
-     * cohort when every item in the section has finished loading
-     * (`loadedCount === itemCount`), gated by the engine's
-     * `interactive` state.
-     */
-    readonly loadingComplete: "pie-loading-complete";
-};
-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 preserves the readiness payload shape used by
- * `selectReadiness()`.
- */
-export type SectionPlayerReadinessPhase = "bootstrapping" | "interaction-ready" | "loading" | "ready" | "error";
-export type SectionPlayerReadinessChangeDetail = {
-    phase: SectionPlayerReadinessPhase;
-    interactionReady: boolean;
-    allLoadingComplete: boolean;
-    reason?: string;
-};

package/dist/contracts/stages.d.ts

@@ -1,10 +0,0 @@
-/**
- * Re-export shim for the canonical stage vocabulary.
- *
- * The contract types and tracker primitive live in
- * `@pie-players/pie-players-shared/pie` so both
- * `<pie-section-player-*>` and `<pie-assessment-toolkit>` import the
- * same source of truth (M6 Phase C).
- */
-export { STAGES, applicableStages, stageOrdinal, } from '@pie-players/pie-players-shared/pie';
-export type { LoadingCompleteDetail, Stage, StageChangeDetail, StageSourceCe, StageStatus, } from '@pie-players/pie-players-shared/pie';

package/dist/policies/guards.d.ts

@@ -1,2 +0,0 @@
-import { SectionPlayerPublicEventName } from '../contracts/public-events.js';
-export declare function assertPublicEventName(eventName: string): asserts eventName is SectionPlayerPublicEventName;

package/dist/utils/z-index.d.ts

@@ -1,5 +0,0 @@
-/**
- * Canonical z-index layering is defined in assessment-toolkit.
- * Re-export locally so section-player consumers keep a stable import path.
- */
-export { ZIndexLayer } from '@pie-players/pie-assessment-toolkit';