Part 1 — the ledger + remnants interlude (master-dispatched, owner ruling 2026-09-23: nothing configures the graph beyond chat models): - The embedding ledger surface is gone: readEmbeddings/writeEmbeddings ports, the EmbeddingsLedger contract, EMBEDDINGS_FILE (config, store impls, graphRevision source list), and graph-deletion's vector-pruning step. On-disk data files stay untouched (inert history). - The extraction embedder seam dies wholesale: ExtractionPipelineDeps drops the embedder dep (chat-handler + backfill/import-notes stubs go with it), the 'embedding' phase leaves ExtractionPhase, the usage capture/persist helpers die, and stages.embedding leaves ExtractionRunUsage (historical records keep their shape — reads are lenient). Extraction is two stages again, like the local-embedder era. - Consumer-less remnants: latestQuizOutcomes + QUIZ_EVENT_KINDS, clusterContentId, matchClusterLabelings + Community + ClusterLabeling, the readClusterLabels/appendClusterLabel port seams + store impls + LEDGER_FILES.clusterLabels. NamingRunUsage/readNamingRuns STAY (standing ruling — the cost pill renders historical naming spend); clusterHue + MIN_CLUSTER_SIZE stay (live). - The 'labeler' role dies: BACKGROUND_MODEL_ROLES, ROLE_SLOT, ModelRole, the catalog pin projections, and the UI roster strings. RolePins keys shrink with the union. The notes birth fallback (owner-approved 2026-09-23, surfaced by the interlude's live smoke: production notes imports create provenance-EMPTY nodes (importNotes passes messages: null — the file's anchor is the mapping line), so the provenance-only birth rule left every imported file unclustered and invisible to the prober's session list, against the locked file-birth ruling. A provenance-empty node now births under its FIRST mapping line's chatId (ledger order); only notes-born nodes ever hit the fallback (chat nodes always carry provenance; a re-encountered node's link-append re-opens the provenance rule). Deletion-safe: mapping lines of deleted chats are stripped alongside their provenance. Live-verified on port 3004: a fresh notes import clusters under its src_ id with the file path as the label, end to end with no embedder. 845/845 tests, typecheck/lint/build green. EOF )
27 lines
1.1 KiB
TypeScript
27 lines
1.1 KiB
TypeScript
/**
|
|
* Cluster presentation-rule tests. Wave 7 killed the semantic detection
|
|
* AND the LLM label matcher (birth-session clusters, session-name labels —
|
|
* core/session-clusters.ts has its own suite); what remains pinned here
|
|
* is the render threshold and the hull-color spread the UI leans on.
|
|
*/
|
|
import { strict as assert } from "node:assert";
|
|
import { describe, test } from "node:test";
|
|
import { MIN_CLUSTER_SIZE } from "../src/core/clusters.ts";
|
|
import { clusterHue } from "../components/cluster-geometry.ts";
|
|
|
|
describe("MIN_CLUSTER_SIZE", () => {
|
|
test("is 3 (the render threshold — below this, no hull)", () => {
|
|
assert.equal(MIN_CLUSTER_SIZE, 3);
|
|
});
|
|
});
|
|
|
|
describe("clusterHue", () => {
|
|
test("is stable per id and spreads", () => {
|
|
// Same id → same hue, always; different ids → usually different hues.
|
|
assert.equal(clusterHue("cluster-a"), clusterHue("cluster-a"));
|
|
const hues = new Set<number>();
|
|
for (let i = 0; i < 40; i++) hues.add(clusterHue(`cluster-${i}`));
|
|
assert.ok(hues.size > 20, `expected spread, got ${hues.size} distinct hues for 40 ids`);
|
|
for (const h of hues) assert.ok(h >= 0 && h < 360);
|
|
});
|
|
}); |