@vived/app 6.6.0 → 6.7.1

package/dist/cjs/TestUtils/setupFeatureForTesting.js

@@ -1,60 +0,0 @@
-"use strict";
-/**
- * setupFeatureForTesting.ts
- *
- * The feature-context test harness for this Feature Library.
- *
- * This package has no app-level domain (no `makeDomain`, no single repo), so there is no
- * global "make the domain" harness. The unit of test context is a **Feature** (or a small
- * cluster of Features), wired the way a Slide App wires it — through each Feature's
- * `FeatureFactory` (the current standard), using the same phased orchestration production
- * uses. See `CLAUDE.md` and `docs/agents/domain.md`.
- *
- * Use this for **wiring / lifecycle** tests — proving that a Feature, once really wired,
- * behaves end-to-end (e.g. a Challenge submits its result when the student leaves the slide).
- * For pure **logic** tests of a single UC or PM, a hand-wired `makeAppObjectRepo()` rig with
- * the collaborators mocked at the boundary is lighter and still preferred — see
- * `src/ObjectPick/UseCases/TrySubmitObjectPickUC.test.ts` as the reference.
- *
- * @example
- *   // LabelDrop's submit path depends on Challenge (for `selectedChallenge`) and the
- *   // Dispatcher (the Host boundary). List dependencies first, exactly as a Slide App would.
- *   const { appObjects } = setupFeatureForTesting([
- *     makeDispatcherFeatureFactory,
- *     makeChallengeFeatureFactory,
- *     makeLabelDropFeatureFactory,
- *   ]);
- *   // Then act through a Controller / navigation seam and assert through an Adapter VM or a
- *   // dispatcher mock registered before setup.
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.setupFeatureForTesting = setupFeatureForTesting;
-const core_1 = require("@vived/core");
-/**
- * Wire one or more Features into a fresh repo for a feature-context test.
- *
- * @param featureFactories The `make<Feature>FeatureFactory` functions to wire, in the order a
- *   Slide App would compose them — a Feature whose `finalSetup` depends on another Feature's
- *   entities must be listed *after* that Feature.
- * @param seed Optional callback run *before* the factories are constructed. Use it to stand up
- *   the boundary singletons a Feature reads at construction time (many Feature UCs resolve
- *   siblings via `getCachedSingleton`, which THROWS when absent — e.g. `BaseAppState`,
- *   `ChallengeEntity`). Seed real entities or their Mocks here instead of pulling every
- *   dependency Feature's factory into the cluster.
- * @returns `{ appObjects }` — resolve Controllers and Adapters from it to act and assert.
- */
-function setupFeatureForTesting(featureFactories, seed) {
-    const appObjects = (0, core_1.makeAppObjectRepo)();
-    // The DomainFactoryRepo must exist before the factories are constructed: each
-    // FeatureFactory auto-registers with it in its constructor.
-    const factoryRepo = (0, core_1.makeDomainFactoryRepo)(appObjects);
-    // Stand up boundary singletons the Features read at construction time.
-    if (seed)
-        seed(appObjects);
-    featureFactories.forEach((makeFactory) => makeFactory(appObjects));
-    // Run the same phased orchestration as production — all setupEntities, then all setupUCs,
-    // then all setupPMs, then all finalSetup — so cross-Feature dependencies resolve correctly.
-    factoryRepo.setupDomain();
-    return { appObjects };
-}
-//# sourceMappingURL=setupFeatureForTesting.js.map

package/dist/cjs/TestUtils/setupFeatureForTesting.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"setupFeatureForTesting.js","sourceRoot":"","sources":["../../../src/TestUtils/setupFeatureForTesting.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;;AA2BH,wDAoBC;AA7CD,sCAKqB;AAOrB;;;;;;;;;;;;GAYG;AACH,SAAgB,sBAAsB,CACpC,gBAAkE,EAClE,IAA0C;IAE1C,MAAM,UAAU,GAAG,IAAA,wBAAiB,GAAE,CAAC;IAEvC,8EAA8E;IAC9E,4DAA4D;IAC5D,MAAM,WAAW,GAAG,IAAA,4BAAqB,EAAC,UAAU,CAAC,CAAC;IAEtD,uEAAuE;IACvE,IAAI,IAAI;QAAE,IAAI,CAAC,UAAU,CAAC,CAAC;IAE3B,gBAAgB,CAAC,OAAO,CAAC,CAAC,WAAW,EAAE,EAAE,CAAC,WAAW,CAAC,UAAU,CAAC,CAAC,CAAC;IAEnE,0FAA0F;IAC1F,4FAA4F;IAC5F,WAAW,CAAC,WAAW,EAAE,CAAC;IAE1B,OAAO,EAAE,UAAU,EAAE,CAAC;AACxB,CAAC","sourcesContent":["/**\r\n * setupFeatureForTesting.ts\r\n *\r\n * The feature-context test harness for this Feature Library.\r\n *\r\n * This package has no app-level domain (no `makeDomain`, no single repo), so there is no\r\n * global \"make the domain\" harness. The unit of test context is a **Feature** (or a small\r\n * cluster of Features), wired the way a Slide App wires it — through each Feature's\r\n * `FeatureFactory` (the current standard), using the same phased orchestration production\r\n * uses. See `CLAUDE.md` and `docs/agents/domain.md`.\r\n *\r\n * Use this for **wiring / lifecycle** tests — proving that a Feature, once really wired,\r\n * behaves end-to-end (e.g. a Challenge submits its result when the student leaves the slide).\r\n * For pure **logic** tests of a single UC or PM, a hand-wired `makeAppObjectRepo()` rig with\r\n * the collaborators mocked at the boundary is lighter and still preferred — see\r\n * `src/ObjectPick/UseCases/TrySubmitObjectPickUC.test.ts` as the reference.\r\n *\r\n * @example\r\n *   // LabelDrop's submit path depends on Challenge (for `selectedChallenge`) and the\r\n *   // Dispatcher (the Host boundary). List dependencies first, exactly as a Slide App would.\r\n *   const { appObjects } = setupFeatureForTesting([\r\n *     makeDispatcherFeatureFactory,\r\n *     makeChallengeFeatureFactory,\r\n *     makeLabelDropFeatureFactory,\r\n *   ]);\r\n *   // Then act through a Controller / navigation seam and assert through an Adapter VM or a\r\n *   // dispatcher mock registered before setup.\r\n */\r\n\r\nimport {\r\n  AppObjectRepo,\r\n  DomainFactory,\r\n  makeAppObjectRepo,\r\n  makeDomainFactoryRepo,\r\n} from \"@vived/core\";\r\n\r\nexport interface FeatureTestContext {\r\n  /** The live repo, wired through the given FeatureFactories exactly as production does. */\r\n  appObjects: AppObjectRepo;\r\n}\r\n\r\n/**\r\n * Wire one or more Features into a fresh repo for a feature-context test.\r\n *\r\n * @param featureFactories The `make<Feature>FeatureFactory` functions to wire, in the order a\r\n *   Slide App would compose them — a Feature whose `finalSetup` depends on another Feature's\r\n *   entities must be listed *after* that Feature.\r\n * @param seed Optional callback run *before* the factories are constructed. Use it to stand up\r\n *   the boundary singletons a Feature reads at construction time (many Feature UCs resolve\r\n *   siblings via `getCachedSingleton`, which THROWS when absent — e.g. `BaseAppState`,\r\n *   `ChallengeEntity`). Seed real entities or their Mocks here instead of pulling every\r\n *   dependency Feature's factory into the cluster.\r\n * @returns `{ appObjects }` — resolve Controllers and Adapters from it to act and assert.\r\n */\r\nexport function setupFeatureForTesting(\r\n  featureFactories: ((appObjects: AppObjectRepo) => DomainFactory)[],\r\n  seed?: (appObjects: AppObjectRepo) => void,\r\n): FeatureTestContext {\r\n  const appObjects = makeAppObjectRepo();\r\n\r\n  // The DomainFactoryRepo must exist before the factories are constructed: each\r\n  // FeatureFactory auto-registers with it in its constructor.\r\n  const factoryRepo = makeDomainFactoryRepo(appObjects);\r\n\r\n  // Stand up boundary singletons the Features read at construction time.\r\n  if (seed) seed(appObjects);\r\n\r\n  featureFactories.forEach((makeFactory) => makeFactory(appObjects));\r\n\r\n  // Run the same phased orchestration as production — all setupEntities, then all setupUCs,\r\n  // then all setupPMs, then all finalSetup — so cross-Feature dependencies resolve correctly.\r\n  factoryRepo.setupDomain();\r\n\r\n  return { appObjects };\r\n}\r\n"]}

package/dist/esm/FramedScreen/Factories/setupStandardFramedScreen.test.js

@@ -1,29 +0,0 @@
-import { makeAppObjectRepo } from "@vived/core";
-import { setupStandardFramedScreen } from "./setupStandardFramedScreen";
-describe("setupStandardFramedScreen", () => {
-    it("Defaults to adding the StandardLayoutUC", () => {
-        const appObjects = makeAppObjectRepo();
-        const ao = setupStandardFramedScreen(appObjects);
-        expect(ao.hasComponent("StandardLayoutUC")).toBe(true);
-    });
-    it("Does not add the StandardLayoutUC if the option is set to true", () => {
-        const appObjects = makeAppObjectRepo();
-        const ao = setupStandardFramedScreen(appObjects, {
-            dontSetupLayoutHook: true,
-        });
-        expect(ao.hasComponent("StandardLayoutUC")).toBe(false);
-    });
-    it("Adds the StandardLayoutUC if the option is set to false", () => {
-        const appObjects = makeAppObjectRepo();
-        const ao = setupStandardFramedScreen(appObjects, {
-            dontSetupLayoutHook: false,
-        });
-        expect(ao.hasComponent("StandardLayoutUC")).toBe(true);
-    });
-    it("Adds the StandardLayoutUC if the option is not set", () => {
-        const appObjects = makeAppObjectRepo();
-        const ao = setupStandardFramedScreen(appObjects, {});
-        expect(ao.hasComponent("StandardLayoutUC")).toBe(true);
-    });
-});
-//# sourceMappingURL=setupStandardFramedScreen.test.js.map

package/dist/esm/FramedScreen/Factories/setupStandardFramedScreen.test.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"setupStandardFramedScreen.test.js","sourceRoot":"","sources":["../../../../src/FramedScreen/Factories/setupStandardFramedScreen.test.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAChD,OAAO,EAAE,yBAAyB,EAAE,MAAM,6BAA6B,CAAC;AAExE,QAAQ,CAAC,2BAA2B,EAAE,GAAG,EAAE;IACzC,EAAE,CAAC,yCAAyC,EAAE,GAAG,EAAE;QACjD,MAAM,UAAU,GAAG,iBAAiB,EAAE,CAAC;QAEvC,MAAM,EAAE,GAAG,yBAAyB,CAAC,UAAU,CAAC,CAAC;QAEjD,MAAM,CAAC,EAAE,CAAC,YAAY,CAAC,kBAAkB,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IACzD,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,gEAAgE,EAAE,GAAG,EAAE;QACxE,MAAM,UAAU,GAAG,iBAAiB,EAAE,CAAC;QAEvC,MAAM,EAAE,GAAG,yBAAyB,CAAC,UAAU,EAAE;YAC/C,mBAAmB,EAAE,IAAI;SAC1B,CAAC,CAAC;QAEH,MAAM,CAAC,EAAE,CAAC,YAAY,CAAC,kBAAkB,CAAC,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;IAC1D,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,yDAAyD,EAAE,GAAG,EAAE;QACjE,MAAM,UAAU,GAAG,iBAAiB,EAAE,CAAC;QAEvC,MAAM,EAAE,GAAG,yBAAyB,CAAC,UAAU,EAAE;YAC/C,mBAAmB,EAAE,KAAK;SAC3B,CAAC,CAAC;QAEH,MAAM,CAAC,EAAE,CAAC,YAAY,CAAC,kBAAkB,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IACzD,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,oDAAoD,EAAE,GAAG,EAAE;QAC5D,MAAM,UAAU,GAAG,iBAAiB,EAAE,CAAC;QAEvC,MAAM,EAAE,GAAG,yBAAyB,CAAC,UAAU,EAAE,EAAE,CAAC,CAAC;QAErD,MAAM,CAAC,EAAE,CAAC,YAAY,CAAC,kBAAkB,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IACzD,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC","sourcesContent":["import { makeAppObjectRepo } from \"@vived/core\";\r\nimport { setupStandardFramedScreen } from \"./setupStandardFramedScreen\";\r\n\r\ndescribe(\"setupStandardFramedScreen\", () => {\r\n  it(\"Defaults to adding the StandardLayoutUC\", () => {\r\n    const appObjects = makeAppObjectRepo();\r\n\r\n    const ao = setupStandardFramedScreen(appObjects);\r\n\r\n    expect(ao.hasComponent(\"StandardLayoutUC\")).toBe(true);\r\n  });\r\n\r\n  it(\"Does not add the StandardLayoutUC if the option is set to true\", () => {\r\n    const appObjects = makeAppObjectRepo();\r\n\r\n    const ao = setupStandardFramedScreen(appObjects, {\r\n      dontSetupLayoutHook: true,\r\n    });\r\n\r\n    expect(ao.hasComponent(\"StandardLayoutUC\")).toBe(false);\r\n  });\r\n\r\n  it(\"Adds the StandardLayoutUC if the option is set to false\", () => {\r\n    const appObjects = makeAppObjectRepo();\r\n\r\n    const ao = setupStandardFramedScreen(appObjects, {\r\n      dontSetupLayoutHook: false,\r\n    });\r\n\r\n    expect(ao.hasComponent(\"StandardLayoutUC\")).toBe(true);\r\n  });\r\n\r\n  it(\"Adds the StandardLayoutUC if the option is not set\", () => {\r\n    const appObjects = makeAppObjectRepo();\r\n\r\n    const ao = setupStandardFramedScreen(appObjects, {});\r\n\r\n    expect(ao.hasComponent(\"StandardLayoutUC\")).toBe(true);\r\n  });\r\n});\r\n"]}

package/dist/esm/StateMachine/Controller/clickRestoreScene.js

@@ -1,11 +0,0 @@
-import { StateMachineEntity } from "../Entities";
-export function clickRestoreScene(appObjects) {
-    const entity = StateMachineEntity.get(appObjects);
-    if (entity) {
-        entity.restoreLastState();
-    }
-    else {
-        appObjects.submitError("clickRestoreScene", "Unable to find StateMachineEntity");
-    }
-}
-//# sourceMappingURL=clickRestoreScene.js.map

package/dist/esm/StateMachine/Controller/clickRestoreScene.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"clickRestoreScene.js","sourceRoot":"","sources":["../../../../src/StateMachine/Controller/clickRestoreScene.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,kBAAkB,EAAE,MAAM,aAAa,CAAC;AAEjD,MAAM,UAAU,iBAAiB,CAAC,UAAyB;IACzD,MAAM,MAAM,GAAG,kBAAkB,CAAC,GAAG,CAAC,UAAU,CAAC,CAAC;IAClD,IAAI,MAAM,EAAE,CAAC;QACX,MAAM,CAAC,gBAAgB,EAAE,CAAC;IAC5B,CAAC;SAAM,CAAC;QACN,UAAU,CAAC,WAAW,CACpB,mBAAmB,EACnB,mCAAmC,CACpC,CAAC;IACJ,CAAC;AACH,CAAC","sourcesContent":["import { AppObjectRepo } from \"@vived/core\";\nimport { StateMachineEntity } from \"../Entities\";\n\nexport function clickRestoreScene(appObjects: AppObjectRepo) {\n  const entity = StateMachineEntity.get(appObjects);\n  if (entity) {\n    entity.restoreLastState();\n  } else {\n    appObjects.submitError(\n      \"clickRestoreScene\",\n      \"Unable to find StateMachineEntity\",\n    );\n  }\n}\n"]}

package/dist/esm/StateMachine/Controller/clickRestoreScene.test.js

@@ -1,24 +0,0 @@
-import { makeAppObjectRepo } from "@vived/core";
-import { makeMockStateMachine } from "../Mocks";
-import { clickRestoreScene } from "./clickRestoreScene";
-function makeTestRig() {
-    const appObjects = makeAppObjectRepo();
-    const stateMachine = makeMockStateMachine(appObjects);
-    return { appObjects, stateMachine };
-}
-describe("Click Restore Scene", () => {
-    it("Calls restore on the entity", () => {
-        const { appObjects, stateMachine } = makeTestRig();
-        stateMachine.restoreLastState = jest.fn();
-        clickRestoreScene(appObjects);
-        expect(stateMachine.restoreLastState).toHaveBeenCalled();
-    });
-    it("Logs an error if the state machine cannot be found", () => {
-        const appObjects = makeAppObjectRepo();
-        appObjects.submitWarning = jest.fn();
-        appObjects.submitError = jest.fn();
-        clickRestoreScene(appObjects);
-        expect(appObjects.submitError).toHaveBeenCalled();
-    });
-});
-//# sourceMappingURL=clickRestoreScene.test.js.map

package/dist/esm/StateMachine/Controller/clickRestoreScene.test.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"clickRestoreScene.test.js","sourceRoot":"","sources":["../../../../src/StateMachine/Controller/clickRestoreScene.test.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAChD,OAAO,EAAE,oBAAoB,EAAE,MAAM,UAAU,CAAC;AAChD,OAAO,EAAE,iBAAiB,EAAE,MAAM,qBAAqB,CAAC;AAExD,SAAS,WAAW;IAClB,MAAM,UAAU,GAAG,iBAAiB,EAAE,CAAC;IACvC,MAAM,YAAY,GAAG,oBAAoB,CAAC,UAAU,CAAC,CAAC;IAEtD,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,CAAC;AACtC,CAAC;AAED,QAAQ,CAAC,qBAAqB,EAAE,GAAG,EAAE;IACnC,EAAE,CAAC,6BAA6B,EAAE,GAAG,EAAE;QACrC,MAAM,EAAE,UAAU,EAAE,YAAY,EAAE,GAAG,WAAW,EAAE,CAAC;QAEnD,YAAY,CAAC,gBAAgB,GAAG,IAAI,CAAC,EAAE,EAAE,CAAC;QAC1C,iBAAiB,CAAC,UAAU,CAAC,CAAC;QAE9B,MAAM,CAAC,YAAY,CAAC,gBAAgB,CAAC,CAAC,gBAAgB,EAAE,CAAC;IAC3D,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,oDAAoD,EAAE,GAAG,EAAE;QAC5D,MAAM,UAAU,GAAG,iBAAiB,EAAE,CAAC;QAEvC,UAAU,CAAC,aAAa,GAAG,IAAI,CAAC,EAAE,EAAE,CAAC;QACrC,UAAU,CAAC,WAAW,GAAG,IAAI,CAAC,EAAE,EAAE,CAAC;QAEnC,iBAAiB,CAAC,UAAU,CAAC,CAAC;QAC9B,MAAM,CAAC,UAAU,CAAC,WAAW,CAAC,CAAC,gBAAgB,EAAE,CAAC;IACpD,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC","sourcesContent":["import { makeAppObjectRepo } from \"@vived/core\";\nimport { makeMockStateMachine } from \"../Mocks\";\nimport { clickRestoreScene } from \"./clickRestoreScene\";\n\nfunction makeTestRig() {\n  const appObjects = makeAppObjectRepo();\n  const stateMachine = makeMockStateMachine(appObjects);\n\n  return { appObjects, stateMachine };\n}\n\ndescribe(\"Click Restore Scene\", () => {\n  it(\"Calls restore on the entity\", () => {\n    const { appObjects, stateMachine } = makeTestRig();\n\n    stateMachine.restoreLastState = jest.fn();\n    clickRestoreScene(appObjects);\n\n    expect(stateMachine.restoreLastState).toHaveBeenCalled();\n  });\n\n  it(\"Logs an error if the state machine cannot be found\", () => {\n    const appObjects = makeAppObjectRepo();\n\n    appObjects.submitWarning = jest.fn();\n    appObjects.submitError = jest.fn();\n\n    clickRestoreScene(appObjects);\n    expect(appObjects.submitError).toHaveBeenCalled();\n  });\n});\n"]}

package/dist/esm/TestUtils/index.js

@@ -1,2 +0,0 @@
-export * from "./setupFeatureForTesting";
-//# sourceMappingURL=index.js.map

package/dist/esm/TestUtils/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/TestUtils/index.ts"],"names":[],"mappings":"AAAA,cAAc,0BAA0B,CAAC","sourcesContent":["export * from \"./setupFeatureForTesting\";\r\n"]}

package/dist/esm/TestUtils/setupFeatureForTesting.js

@@ -1,57 +0,0 @@
-/**
- * setupFeatureForTesting.ts
- *
- * The feature-context test harness for this Feature Library.
- *
- * This package has no app-level domain (no `makeDomain`, no single repo), so there is no
- * global "make the domain" harness. The unit of test context is a **Feature** (or a small
- * cluster of Features), wired the way a Slide App wires it — through each Feature's
- * `FeatureFactory` (the current standard), using the same phased orchestration production
- * uses. See `CLAUDE.md` and `docs/agents/domain.md`.
- *
- * Use this for **wiring / lifecycle** tests — proving that a Feature, once really wired,
- * behaves end-to-end (e.g. a Challenge submits its result when the student leaves the slide).
- * For pure **logic** tests of a single UC or PM, a hand-wired `makeAppObjectRepo()` rig with
- * the collaborators mocked at the boundary is lighter and still preferred — see
- * `src/ObjectPick/UseCases/TrySubmitObjectPickUC.test.ts` as the reference.
- *
- * @example
- *   // LabelDrop's submit path depends on Challenge (for `selectedChallenge`) and the
- *   // Dispatcher (the Host boundary). List dependencies first, exactly as a Slide App would.
- *   const { appObjects } = setupFeatureForTesting([
- *     makeDispatcherFeatureFactory,
- *     makeChallengeFeatureFactory,
- *     makeLabelDropFeatureFactory,
- *   ]);
- *   // Then act through a Controller / navigation seam and assert through an Adapter VM or a
- *   // dispatcher mock registered before setup.
- */
-import { makeAppObjectRepo, makeDomainFactoryRepo, } from "@vived/core";
-/**
- * Wire one or more Features into a fresh repo for a feature-context test.
- *
- * @param featureFactories The `make<Feature>FeatureFactory` functions to wire, in the order a
- *   Slide App would compose them — a Feature whose `finalSetup` depends on another Feature's
- *   entities must be listed *after* that Feature.
- * @param seed Optional callback run *before* the factories are constructed. Use it to stand up
- *   the boundary singletons a Feature reads at construction time (many Feature UCs resolve
- *   siblings via `getCachedSingleton`, which THROWS when absent — e.g. `BaseAppState`,
- *   `ChallengeEntity`). Seed real entities or their Mocks here instead of pulling every
- *   dependency Feature's factory into the cluster.
- * @returns `{ appObjects }` — resolve Controllers and Adapters from it to act and assert.
- */
-export function setupFeatureForTesting(featureFactories, seed) {
-    const appObjects = makeAppObjectRepo();
-    // The DomainFactoryRepo must exist before the factories are constructed: each
-    // FeatureFactory auto-registers with it in its constructor.
-    const factoryRepo = makeDomainFactoryRepo(appObjects);
-    // Stand up boundary singletons the Features read at construction time.
-    if (seed)
-        seed(appObjects);
-    featureFactories.forEach((makeFactory) => makeFactory(appObjects));
-    // Run the same phased orchestration as production — all setupEntities, then all setupUCs,
-    // then all setupPMs, then all finalSetup — so cross-Feature dependencies resolve correctly.
-    factoryRepo.setupDomain();
-    return { appObjects };
-}
-//# sourceMappingURL=setupFeatureForTesting.js.map

package/dist/esm/TestUtils/setupFeatureForTesting.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"setupFeatureForTesting.js","sourceRoot":"","sources":["../../../src/TestUtils/setupFeatureForTesting.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AAEH,OAAO,EAGL,iBAAiB,EACjB,qBAAqB,GACtB,MAAM,aAAa,CAAC;AAOrB;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,sBAAsB,CACpC,gBAAkE,EAClE,IAA0C;IAE1C,MAAM,UAAU,GAAG,iBAAiB,EAAE,CAAC;IAEvC,8EAA8E;IAC9E,4DAA4D;IAC5D,MAAM,WAAW,GAAG,qBAAqB,CAAC,UAAU,CAAC,CAAC;IAEtD,uEAAuE;IACvE,IAAI,IAAI;QAAE,IAAI,CAAC,UAAU,CAAC,CAAC;IAE3B,gBAAgB,CAAC,OAAO,CAAC,CAAC,WAAW,EAAE,EAAE,CAAC,WAAW,CAAC,UAAU,CAAC,CAAC,CAAC;IAEnE,0FAA0F;IAC1F,4FAA4F;IAC5F,WAAW,CAAC,WAAW,EAAE,CAAC;IAE1B,OAAO,EAAE,UAAU,EAAE,CAAC;AACxB,CAAC","sourcesContent":["/**\r\n * setupFeatureForTesting.ts\r\n *\r\n * The feature-context test harness for this Feature Library.\r\n *\r\n * This package has no app-level domain (no `makeDomain`, no single repo), so there is no\r\n * global \"make the domain\" harness. The unit of test context is a **Feature** (or a small\r\n * cluster of Features), wired the way a Slide App wires it — through each Feature's\r\n * `FeatureFactory` (the current standard), using the same phased orchestration production\r\n * uses. See `CLAUDE.md` and `docs/agents/domain.md`.\r\n *\r\n * Use this for **wiring / lifecycle** tests — proving that a Feature, once really wired,\r\n * behaves end-to-end (e.g. a Challenge submits its result when the student leaves the slide).\r\n * For pure **logic** tests of a single UC or PM, a hand-wired `makeAppObjectRepo()` rig with\r\n * the collaborators mocked at the boundary is lighter and still preferred — see\r\n * `src/ObjectPick/UseCases/TrySubmitObjectPickUC.test.ts` as the reference.\r\n *\r\n * @example\r\n *   // LabelDrop's submit path depends on Challenge (for `selectedChallenge`) and the\r\n *   // Dispatcher (the Host boundary). List dependencies first, exactly as a Slide App would.\r\n *   const { appObjects } = setupFeatureForTesting([\r\n *     makeDispatcherFeatureFactory,\r\n *     makeChallengeFeatureFactory,\r\n *     makeLabelDropFeatureFactory,\r\n *   ]);\r\n *   // Then act through a Controller / navigation seam and assert through an Adapter VM or a\r\n *   // dispatcher mock registered before setup.\r\n */\r\n\r\nimport {\r\n  AppObjectRepo,\r\n  DomainFactory,\r\n  makeAppObjectRepo,\r\n  makeDomainFactoryRepo,\r\n} from \"@vived/core\";\r\n\r\nexport interface FeatureTestContext {\r\n  /** The live repo, wired through the given FeatureFactories exactly as production does. */\r\n  appObjects: AppObjectRepo;\r\n}\r\n\r\n/**\r\n * Wire one or more Features into a fresh repo for a feature-context test.\r\n *\r\n * @param featureFactories The `make<Feature>FeatureFactory` functions to wire, in the order a\r\n *   Slide App would compose them — a Feature whose `finalSetup` depends on another Feature's\r\n *   entities must be listed *after* that Feature.\r\n * @param seed Optional callback run *before* the factories are constructed. Use it to stand up\r\n *   the boundary singletons a Feature reads at construction time (many Feature UCs resolve\r\n *   siblings via `getCachedSingleton`, which THROWS when absent — e.g. `BaseAppState`,\r\n *   `ChallengeEntity`). Seed real entities or their Mocks here instead of pulling every\r\n *   dependency Feature's factory into the cluster.\r\n * @returns `{ appObjects }` — resolve Controllers and Adapters from it to act and assert.\r\n */\r\nexport function setupFeatureForTesting(\r\n  featureFactories: ((appObjects: AppObjectRepo) => DomainFactory)[],\r\n  seed?: (appObjects: AppObjectRepo) => void,\r\n): FeatureTestContext {\r\n  const appObjects = makeAppObjectRepo();\r\n\r\n  // The DomainFactoryRepo must exist before the factories are constructed: each\r\n  // FeatureFactory auto-registers with it in its constructor.\r\n  const factoryRepo = makeDomainFactoryRepo(appObjects);\r\n\r\n  // Stand up boundary singletons the Features read at construction time.\r\n  if (seed) seed(appObjects);\r\n\r\n  featureFactories.forEach((makeFactory) => makeFactory(appObjects));\r\n\r\n  // Run the same phased orchestration as production — all setupEntities, then all setupUCs,\r\n  // then all setupPMs, then all finalSetup — so cross-Feature dependencies resolve correctly.\r\n  factoryRepo.setupDomain();\r\n\r\n  return { appObjects };\r\n}\r\n"]}

package/dist/types/FramedScreen/Factories/setupStandardFramedScreen.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=setupStandardFramedScreen.test.d.ts.map

package/dist/types/FramedScreen/Factories/setupStandardFramedScreen.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"setupStandardFramedScreen.test.d.ts","sourceRoot":"","sources":["../../../../src/FramedScreen/Factories/setupStandardFramedScreen.test.ts"],"names":[],"mappings":""}

package/dist/types/StateMachine/Controller/clickRestoreScene.d.ts

@@ -1,3 +0,0 @@
-import { AppObjectRepo } from "@vived/core";
-export declare function clickRestoreScene(appObjects: AppObjectRepo): void;
-//# sourceMappingURL=clickRestoreScene.d.ts.map

package/dist/types/StateMachine/Controller/clickRestoreScene.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"clickRestoreScene.d.ts","sourceRoot":"","sources":["../../../../src/StateMachine/Controller/clickRestoreScene.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,aAAa,CAAC;AAG5C,wBAAgB,iBAAiB,CAAC,UAAU,EAAE,aAAa,QAU1D"}

package/dist/types/StateMachine/Controller/clickRestoreScene.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=clickRestoreScene.test.d.ts.map

package/dist/types/StateMachine/Controller/clickRestoreScene.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"clickRestoreScene.test.d.ts","sourceRoot":"","sources":["../../../../src/StateMachine/Controller/clickRestoreScene.test.ts"],"names":[],"mappings":""}

package/dist/types/TestUtils/index.d.ts

@@ -1,2 +0,0 @@
-export * from "./setupFeatureForTesting";
-//# sourceMappingURL=index.d.ts.map

package/dist/types/TestUtils/index.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/TestUtils/index.ts"],"names":[],"mappings":"AAAA,cAAc,0BAA0B,CAAC"}

package/dist/types/TestUtils/setupFeatureForTesting.d.ts

@@ -1,48 +0,0 @@
-/**
- * setupFeatureForTesting.ts
- *
- * The feature-context test harness for this Feature Library.
- *
- * This package has no app-level domain (no `makeDomain`, no single repo), so there is no
- * global "make the domain" harness. The unit of test context is a **Feature** (or a small
- * cluster of Features), wired the way a Slide App wires it — through each Feature's
- * `FeatureFactory` (the current standard), using the same phased orchestration production
- * uses. See `CLAUDE.md` and `docs/agents/domain.md`.
- *
- * Use this for **wiring / lifecycle** tests — proving that a Feature, once really wired,
- * behaves end-to-end (e.g. a Challenge submits its result when the student leaves the slide).
- * For pure **logic** tests of a single UC or PM, a hand-wired `makeAppObjectRepo()` rig with
- * the collaborators mocked at the boundary is lighter and still preferred — see
- * `src/ObjectPick/UseCases/TrySubmitObjectPickUC.test.ts` as the reference.
- *
- * @example
- *   // LabelDrop's submit path depends on Challenge (for `selectedChallenge`) and the
- *   // Dispatcher (the Host boundary). List dependencies first, exactly as a Slide App would.
- *   const { appObjects } = setupFeatureForTesting([
- *     makeDispatcherFeatureFactory,
- *     makeChallengeFeatureFactory,
- *     makeLabelDropFeatureFactory,
- *   ]);
- *   // Then act through a Controller / navigation seam and assert through an Adapter VM or a
- *   // dispatcher mock registered before setup.
- */
-import { AppObjectRepo, DomainFactory } from "@vived/core";
-export interface FeatureTestContext {
-    /** The live repo, wired through the given FeatureFactories exactly as production does. */
-    appObjects: AppObjectRepo;
-}
-/**
- * Wire one or more Features into a fresh repo for a feature-context test.
- *
- * @param featureFactories The `make<Feature>FeatureFactory` functions to wire, in the order a
- *   Slide App would compose them — a Feature whose `finalSetup` depends on another Feature's
- *   entities must be listed *after* that Feature.
- * @param seed Optional callback run *before* the factories are constructed. Use it to stand up
- *   the boundary singletons a Feature reads at construction time (many Feature UCs resolve
- *   siblings via `getCachedSingleton`, which THROWS when absent — e.g. `BaseAppState`,
- *   `ChallengeEntity`). Seed real entities or their Mocks here instead of pulling every
- *   dependency Feature's factory into the cluster.
- * @returns `{ appObjects }` — resolve Controllers and Adapters from it to act and assert.
- */
-export declare function setupFeatureForTesting(featureFactories: ((appObjects: AppObjectRepo) => DomainFactory)[], seed?: (appObjects: AppObjectRepo) => void): FeatureTestContext;
-//# sourceMappingURL=setupFeatureForTesting.d.ts.map

package/dist/types/TestUtils/setupFeatureForTesting.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"setupFeatureForTesting.d.ts","sourceRoot":"","sources":["../../../src/TestUtils/setupFeatureForTesting.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AAEH,OAAO,EACL,aAAa,EACb,aAAa,EAGd,MAAM,aAAa,CAAC;AAErB,MAAM,WAAW,kBAAkB;IACjC,0FAA0F;IAC1F,UAAU,EAAE,aAAa,CAAC;CAC3B;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,sBAAsB,CACpC,gBAAgB,EAAE,CAAC,CAAC,UAAU,EAAE,aAAa,KAAK,aAAa,CAAC,EAAE,EAClE,IAAI,CAAC,EAAE,CAAC,UAAU,EAAE,aAAa,KAAK,IAAI,GACzC,kBAAkB,CAiBpB"}