amosblomqvist
e92679254d
Contracts: LadderRung 0-4, CueDistance 0-2, Presentation theory|
application; PracticeParams carries the three named levels. Doc
comments hold the three definition tables verbatim (rung names +
definitions from the ladder doctrine; cue levels; presentation
levels).
Core: LADDER_RUNGS/CUE_LEVELS/PRESENTATIONS tables in src/core/
practice.ts (definitions verbatim) — ONE source spoken by the agents'
prompts, the dialog's stepped controls, and the exam header; core
barrel re-exports practice.ts (pure domain, browser-safe).
Agents: Part I's ladder intro now 'five rungs, numbered; the request
arrives as a rung' with bullets numbered 0-4 (definitions untouched);
Part III's parameters block replaced with the named-level doctrine
(rung = exact class, no continuum; cue counts lesson examples AND
previous problems' situations; presentation dresses, never changes);
partitioner's RESPECT THE PARAMETERS replaced (low rungs = many small
assignments, high = larger; far cue makes confusables-together MORE
important; presentation does not shape the partition). renderParams
outputs the exact named-level block. Anchor/0..1 language swept dead.
Service + store: strict union validation — floats between levels,
out-of-range, wrong strings, legacy dial shapes all 400 at the API
and fail isProblemSet (legacy sets skipped from lists; no migration —
data/practice is disposable scratch, owner wipes before testing).
UI: dialog = 5-detent ladder slider + 3-detent cue slider (each shows
the level NAME + one-line definition) + Theory|Application segmented
toggle; defaults rung 2 / cue 1 / theory; Create posts the new shape.
Exam header gains the levels line ('Direct exercise · Adjacent
context · Theory').
Tests: renderParams exact-block pin; strict-validation pins (new
tests/practice-service.test.ts — bad unions 400, legacy shape 400);
store pins (legacy floats + 2.5 rung fail); render pins (detents +
names + definitions, defaults, detent-swap, toggle active segment,
levels line); every params fixture moved off floats. 1138/1138, tsc
0, lint 0, build 0.
Docs: architecture.md — discretization paragraph (compact tables,
named-level invocation, defaults, one-table source), UI mentions;
README axes sentence.
67 lines
3.1 KiB
TypeScript
67 lines
3.1 KiB
TypeScript
/**
|
|
* THE CORE PUBLIC API — the only module the shell (app/, components/) may
|
|
* import. Everything exported here is browser-safe: pure logic + types,
|
|
* no node builtins, no fs, no network.
|
|
*
|
|
* Server-side surfaces (chat streaming, store reads) live behind
|
|
* src/server's barrel instead — the import law (eslint.config.mjs):
|
|
*
|
|
* components/** → "@/src/core" (this barrel, ONLY)
|
|
* app/** → "@/src/core" + "@/src/server"
|
|
*
|
|
* Server-only core modules (core/graph.ts emission/derivation) are pure
|
|
* but need storage ports passed in by a server caller, so they are
|
|
* deliberately NOT re-exported here — the server imports them directly.
|
|
* The storage PORT TYPES are types-only and browser-safe, hence re-exported.
|
|
*/
|
|
|
|
export * from "./contracts.ts";
|
|
export * from "./ports.ts";
|
|
export * from "./render-settings.ts";
|
|
|
|
export * from "./question-core.ts";
|
|
// clusters.ts (Louvain) is deliberately NOT re-exported: nothing in the
|
|
// shell runs community detection — the snapshot carries the partition
|
|
// from the server. Keeping it out keeps the heavy clustering deps out of the
|
|
// client bundle (verified 2026-09-13: chunks contained it while this
|
|
// line existed). Same logic as layout-settle.ts below.
|
|
export * from "./layout.ts";
|
|
export * from "./plan-tree.ts";
|
|
export * from "./phases.ts";
|
|
export * from "./pending.ts";
|
|
export * from "./prompt-segments.ts";
|
|
export * from "./math-delims.ts";
|
|
export * from "./practice.ts";
|
|
// Wave B (owner-approved 2026-09-26): the native record (LhMessage), the
|
|
// and the input-events contract — all
|
|
// pure logic, browser-safe.
|
|
export * from "./native-messages.ts";
|
|
export * from "./input-events.ts";
|
|
// Wave D (owner-approved 2026-09-26): the client view model — the grouping
|
|
// canon (one continuous assistant document, step separators) ported from
|
|
// the deleted server projection to the client side. Pure, browser-safe.
|
|
export * from "./view.ts";
|
|
export * from "./tool-parts.ts";
|
|
export * from "./prices.ts";
|
|
export * from "./cost-summary.ts";
|
|
export * from "./fuzzy.ts";
|
|
// settings.ts + settings-resolution.ts (settings-storage wave, 2026-09-19):
|
|
// the user-settings record's shape/sanitizer (pure) and its fully-resolved
|
|
// view. Browser-safe — the Wave-4 panel imports these directly.
|
|
export * from "./settings.ts";
|
|
// graph-deletion.ts (wave 6): the whole module is PURE but storage-port
|
|
// driven — the deletion RUNS server-side only. The shell needs exactly one
|
|
// two type-only things from it: the ChatDeleteMode union (the delete
|
|
// dialog's two-option design + the DELETE query param) and the stats
|
|
// shape its success line describes, hence this type-only re-export.
|
|
export type { ChatDeleteMode, ChatDeletionStats } from "./graph-deletion.ts";
|
|
export * from "./settings-resolution.ts";
|
|
export * from "./search.ts"; // search port (search wave, 2026-09-20)
|
|
// auth-keys.ts (auth-keys wave, 2026-09-19): the curated key catalog +
|
|
// shape rules + masking — pure, browser-safe (the auth page binds to the
|
|
// /api/keys routes built on it).
|
|
export * from "./auth-keys.ts";
|
|
// keyboard.ts: the shortcut registry + binding normalization (pure, browser-safe).
|
|
export * from "./keyboard.ts";
|
|
export * from "./coverage.ts";
|