@pie-players/pie-tool-sign-language 0.3.50 → 0.3.66

package/README.md

@@ -37,12 +37,15 @@ placement: `activation: "region"` means there is no button to press, so a
 `tools.placement` entry naming this capability is reported as unplaceable rather
 than silently doing nothing.
 
-**Content** — the item carries a matching `sign-language` catalog card. QTI
+**Content** — the item or passage carries a matching `sign-language` catalog card. QTI
 approximates AfA's DRD in-band: the presence of the card *is* the resource
 declaration. This half is `requiresAuthoredContent.resolve`, and it is why a
-learner with the accommodation still sees nothing on the vast majority of items.
+learner with the accommodation still sees nothing on content that has no signed
+alternate. The catalog resolver supplies an immutable owner snapshot after it
+has applied entity/extracted/model traversal and registration precedence; this
+package owns only card validation and sign-language matching.
 
-A signed alternate reaches an item one way only: as a catalog card, authored or
+A signed alternate reaches content one way only: as a catalog card, authored or
 written by an importer. There is no path that lifts a signing video out of item
 markup at render time — one was implemented and removed, because it had no
 producer and failed in the wrong direction, leaving the video in visible content
@@ -50,12 +53,11 @@ for every learner when the markup could not be parsed.
 
 ## No cross-sign-language substitution
 
-ASL, BSL and LSF are not interchangeable. The catalog resolver's last fallback
-rung matches any card of the requested type regardless of language, which helps
-for spoken audio and harms here: handing an ASL learner a BSL recording is worse
-than handing them nothing. `resolveSignLanguageAlternate` therefore accepts a
-card reached by that rung only when its language matches, or when the card
-asserts no language at all.
+ASL, BSL and LSF are not interchangeable. Handing an ASL learner a BSL recording
+is worse than handing them nothing. `resolveSignLanguageAlternate` scans the
+owner snapshot for an exact requested-language match first, then permits an
+unlabelled card as the only fallback. A card labelled with another sign language
+is never substituted.
 
 ## The element
 

package/dist/index.d.ts

@@ -1,5 +1,5 @@
 export { CONTENT_MEDIA_SURFACE, SIGN_LANGUAGE_ELEMENT_TAG, signLanguageRegistration, } from './src/sign-language-registration.js';
 export type { SignLanguageMedia } from './src/sign-language-cards.js';
 export { AMERICAN_SIGN_LANGUAGE, describeSignLanguage, isSignLanguageCard, matchesRequestedSignLanguage, resolveSignLanguageMedia, SIGN_LANGUAGE_CATALOG_TYPE, } from './src/sign-language-cards.js';
-export type { ResolvedSignLanguageAlternate, SignLanguageCatalogRef, SignLanguageLookupArgs, } from './src/sign-language-content.js';
-export { collectSignLanguageCatalogRefs, resolveRequestedSignLanguage, resolveSignLanguageAlternate, resolveSignLanguageContent, SIGN_LANGUAGE_FEATURE_ID, } from './src/sign-language-content.js';
+export type { ResolvedSignLanguageAlternate, SignLanguageLookupArgs, } from './src/sign-language-content.js';
+export { resolveRequestedSignLanguage, resolveSignLanguageAlternate, resolveSignLanguageContent, SIGN_LANGUAGE_FEATURE_ID, } from './src/sign-language-content.js';

package/dist/src/sign-language-content.d.ts

@@ -1,54 +1,22 @@
-import { CatalogOwnerContext, AccessibilityCatalogResolverApi, ToolContentDependencyContext } from '@pie-players/pie-assessment-toolkit';
-import { ItemEntity } from '@pie-players/pie-players-shared/types';
+import { CatalogOwnerSnapshot, ToolContentDependencyContext } from '@pie-players/pie-assessment-toolkit/tools/internal';
 import { SignLanguageMedia } from './sign-language-cards.js';
 /** QTI 3.0 / AfA support id gating signed alternates. */
 export declare const SIGN_LANGUAGE_FEATURE_ID = "signLanguage";
-/** A catalog on this item that carries at least one sign-language card. */
-export interface SignLanguageCatalogRef {
-    catalogId: string;
-    /** Set when the catalog is owned by one model rather than the item root. */
-    modelId?: string;
-}
 export interface ResolvedSignLanguageAlternate extends SignLanguageMedia {
     catalogId: string;
 }
-/**
- * Collect the catalog identifiers on an item that carry signing cards.
- *
- * The region resolves through the catalog resolver, but the resolver is keyed by
- * identifier within an owner scope — something has to say *which* identifiers
- * this item put in play, and whether each belongs to the item or to one model.
- * That is the same walk the runtime does when it registers an item's catalogs,
- * so it is borrowed rather than repeated: a ref can only name a scope
- * registration actually files under. Only the "does this catalog carry signing"
- * filter is ours.
- *
- * The owner identity here is a placeholder: the assessment and section ids are
- * not known at extraction time and are supplied by the caller at lookup time
- * (see `resolveSignLanguageAlternate`). Nothing but `modelId` is read from the
- * walk's contexts.
- */
-export declare function collectSignLanguageCatalogRefs(item: ItemEntity | null | undefined): SignLanguageCatalogRef[];
 export interface SignLanguageLookupArgs {
-    resolver: AccessibilityCatalogResolverApi;
-    refs: SignLanguageCatalogRef[];
-    /** Owner context for the item, without `modelId` — added per ref. */
-    ownerContext: CatalogOwnerContext;
+    catalogs: CatalogOwnerSnapshot;
     /** Sign language the learner is entitled to, ISO 639-3. */
     requestedSignLang?: string;
 }
 /**
  * Resolve the signed alternate to show for an item, or `null`.
  *
- * Priority, language fallback and owner scoping are the resolver's job and are
- * not re-implemented here. What *is* enforced here is the one deliberate
- * departure from the resolver's default behaviour: **no cross-sign-language
- * substitution.** The resolver's last fallback rung matches any card of the
- * requested type regardless of language, which for spoken content is helpful
- * and for signing is not — handing an ASL learner a BSL recording is worse than
- * handing them nothing. So a card the resolver returns by that rung is accepted
- * only if its language actually matches, or if the card asserts no language at
- * all.
+ * Owner scope, item/passage/model traversal and registration order are already
+ * represented by the snapshot. What remains capability-specific is the strict
+ * **no cross-sign-language substitution** rule: handing an ASL learner a BSL
+ * recording is worse than handing them nothing.
  *
  * MVP takes the first resolvable card: sample content is one recording per item.
  * The refs stay per-node capable for when choice-level docking lands.
@@ -66,8 +34,8 @@ export declare function resolveRequestedSignLanguage(parameters: unknown): strin
  * The registration's `requiresAuthoredContent` implementation: the whole
  * content half behind the one call the host makes.
  *
- * The host supplies the item, the resolver and the owner scope, and learns only
- * whether there is something to render. It never sees a catalog type, a card
- * shape or a sign-language code.
+ * The host supplies one owner snapshot and learns only whether there is
+ * something to render. It never sees a catalog type, card shape, entity walk or
+ * sign-language code.
  */
 export declare function resolveSignLanguageContent(context: ToolContentDependencyContext): ResolvedSignLanguageAlternate | null;