@classytic/labs 0.4.0 → 0.5.0

package/README.md

@@ -35,19 +35,35 @@ npm i @classytic/labs @classytic/stage react react-dom katex lucide-react
 @import '@classytic/labs/styles.css'; /* control-UI kit + lab tokens */
 ```
 
-`styles.css` is the compatibility aggregate: every subject, which is right for a
-gallery and wasteful for a course page. Hosts that know which subjects a page
-shows should import the layers explicitly instead:
+`styles.css` is the compatibility aggregate of two entries, and a host that renders
+labs on only some routes should use them separately, so pages without labs never
+download the lab styles:
 
 ```css
+/* global CSS (your Tailwind entry): the scan for the authoring UI's utilities, no rules */
+@import '@classytic/labs/tailwind.css';
+```
+
+```ts
+// in the code that renders labs (for example your MDX component map)
+import '@classytic/labs/styles/runtime.css';
+```
+
+`styles/runtime.css` is every subject, which is right for a gallery and wasteful for
+a course page. Hosts that know which subjects a page shows can go finer:
+
+```css
+@import '@classytic/labs/tailwind.css'; /* in the Tailwind entry, if you use /blocks */
 @import '@classytic/labs/styles/core.css'; /* tokens, shell, components: always */
 @import '@classytic/labs/styles/figure.css'; /* figure art direction:        always */
 @import '@classytic/labs/styles/domains/math.css'; /* ONE subject */
-@import '@classytic/labs/styles/commerce.css'; /* only on Commerce routes */
+@import '@classytic/labs/styles/domains/geometry.css'; /* + geometry, mensuration, solids */
+@import '@classytic/labs/styles/domains/commerce.css'; /* same contract for Commerce */
 ```
 
 core.css and figure.css are the two always-required layers, then one sheet per
-subject from `styles/domains/`. Use `styles/domains.css` if you genuinely want
+subject from `styles/domains/`. A maths course that also shows geometry,
+mensuration or solid labs imports `domains/geometry.css` beside `domains/math.css`. Use `styles/domains.css` if you genuinely want
 every subject in one import. Per-subject budgets and the full list of sheets are
 in `docs/DESIGN-SYSTEM.md`.
 
@@ -68,8 +84,10 @@ The broader `@classytic/labs/three` entry remains available as a convenience;
 prefer the domain entry when a host only enables one family of 3D lessons.
 
 Community-authored labs using the Activity, pedagogy, and response primitives need only
-`core.css`. Add `domains.css` when rendering the package's built-in domain catalog and
-`commerce.css` only for Commerce experiences. All layers consume shadcn-compatible semantic
+`core.css`. Add `domains.css` when rendering the package's built-in domain catalog and one canonical
+`styles/domains/<subject>.css` entry on a focused course route—including `domains/commerce.css` and
+`domains/exam.css`. Internal feature leaves keep large subjects maintainable without creating a
+second design-system contract. All layers consume shadcn-compatible semantic
 tokens (`--background`, `--foreground`, `--primary`, `--muted`, `--border`, `--ring`) with
 Stage fallbacks; they do not install or override a host theme.
 
@@ -95,6 +113,13 @@ import { CircuitNetworkLab } from '@classytic/labs/circuits';
 <BalanceAlgebraLab coef={2} addend={1} rhs={7} answer={3} />
 ```
 
+### Practical-work labs
+
+- `MetalReactivityBench`: put metals in cold water, steam or dilute acid, watch, then rank them by reactivity.
+- `ScaleReading`: read a burette, measuring cylinder, thermometer, balance, stopwatch or ruler to the right precision, with a parallax eye and the titre.
+- `PaperChromatogram`: run the solvent, measure spots from the baseline, work out Rf, identify an unknown and judge purity. `identify="contains"` (default) ticks every reference in the unknown; `identify="exact"` picks the one reference whose spots match it exactly (which pen wrote the note).
+- `ApparatusBuilder`: drag the parts of a filtration, crystallisation or distillation set-up into place and run it.
+
 ## The lab-template registry (`@classytic/labs/catalog`)
 
 Families are listable/instantiable units — the basis for a lab "marketplace" and the

package/dist/algorithms/GraphAlgorithmLab.d.mts

@@ -1,13 +1,27 @@
-import { AlgorithmGraph } from "./contract.mjs";
+import { AlgorithmGraph, GraphAlgorithmId } from "./contract.mjs";
+import { DfsOrder } from "./graph.mjs";
 //#region src/algorithms/GraphAlgorithmLab.d.ts
+type GraphRepresentation = 'drawing' | 'adj-list' | 'matrix' | 'both';
 interface GraphAlgorithmLabProps {
-  algorithm?: 'bfs' | 'dfs' | 'dijkstra';
+  algorithm?: GraphAlgorithmId;
+  /** A named graph dataset id, e.g. 'city-roads'. An inline `graph` wins over it. */
+  dataset?: string;
   graph?: AlgorithmGraph;
   source?: string;
   target?: string;
+  /** Ask the learner to predict each real choice before it happens (graded). Default true. */
+  predict?: boolean;
+  /** Show the adjacency list and/or matrix beside the drawing, with the scanned row lit. */
+  representation?: GraphRepresentation;
+  /**
+   * DFS only. 'stack' (default) is the iterative version: a node is marked when pushed and the
+   * newest push comes off first. 'recursive' is the textbook version exams trace: a node is marked
+   * on entry, neighbours are tried in alphabetical order and the search backtracks at dead ends.
+   */
+  dfsOrder?: DfsOrder;
   title?: string;
   prompt?: string;
 }
-declare function GraphAlgorithmLab({ algorithm, graph, source, target, title, prompt }: GraphAlgorithmLabProps): import("react").JSX.Element;
+declare function GraphAlgorithmLab({ algorithm, dataset, graph, source, target, predict, representation, dfsOrder, title, prompt }: GraphAlgorithmLabProps): import("react").JSX.Element;
 //#endregion
-export { GraphAlgorithmLab, GraphAlgorithmLabProps };
+export { GraphAlgorithmLab, GraphAlgorithmLabProps, GraphRepresentation };