@demlik/tea 0.13.0 → 0.14.0

package/dist/chart/report/index.d.ts

@@ -1,117 +0,0 @@
-import { WalkCounts } from '../index.js';
-export { edgeKey } from '../index.js';
-import { a as ImportedChart, L as LogEntry, b as LaneStatus, I as ImportedLane, W as WorkflowImportOptions } from '../../fold-BJPdjc9w.js';
-export { c as ImportedEdge, d as ImportedNode, e as ImportedPhase, f as LeafStates, g as PhaseStand, P as PhaseStanding, T as TaskState, h as TimelineStep, U as UnreplayableLogError, i as WorkflowImportError, j as bareEvent, k as chartFromWorkflow, l as chartFromWorkflowText, m as deriveLaneStatus, n as endPolarityOf, o as eventAlphabet, p as foldLane, q as initialOf, r as initialStates, s as laneTerminalReached, t as originOf, u as parseEventsJsonl, v as parseHistoryJson, w as parseStatusJson, x as phaseStandings, y as statesOf, z as stepTask, A as timeline, B as trippedTasks, C as walkedEdgeKey } from '../../fold-BJPdjc9w.js';
-import '../../core-Co0LWkIA.js';
-import 'zod';
-import '../../graph-B3L5e0N1.js';
-
-interface DrawOptions {
-    /** The state the task is in right now — lit. */
-    readonly current?: string;
-    /** Edges the log actually walked, keyed `${from}|${event}|${to}`. */
-    readonly walked?: WalkCounts;
-}
-/**
- * One task's region as a mermaid `stateDiagram-v2` block, with the current node
- * lit, the walked edges marked and the two endings drawn apart.
- *
- * `polarity` is always on: a lane's whole point is that `shipped` and `frozen`
- * are not the same ending, and a report that painted them alike would be lying
- * in the place a reader looks first. It is an OPTION on the renderer rather
- * than a default because a chart drawing is something a reviewer approves —
- * see `ChartMermaidOptions.polarity`.
- */
-declare function drawTask(chart: ImportedChart, opts?: DrawOptions): string;
-/**
- * The edges a log walked, counted — the input `drawTask` marks from.
- *
- * Reads each step's DECLARED `edge` rather than recomputing one from
- * `from`/`event`/`to`: a resume edge is drawn to its fallback and walked to
- * wherever `was` pointed, so the observed target names an edge the drawing does
- * not have. `TimelineStep.edge` is the edge that actually fired.
- */
-declare function walkedEdges(steps: readonly {
-    readonly edge: string;
-}[]): WalkCounts;
-
-/** The lane the report is about. `workflow` is the PARSED document, or an import. */
-interface LaneReportInput {
-    /** `workflow.json`, parsed — or an already-imported lane, reused as is. */
-    readonly workflow: unknown;
-    readonly entries: readonly LogEntry[];
-    /**
-     * `lane status`'s answer.
-     *
-     * OPTIONAL, and that is the whole shape of the two input paths: a caller
-     * shelling out to `fabrika` hands over the CLI's own derivation and the
-     * report never second-guesses it; a caller holding only the two files omits
-     * it and the same derivation runs here.
-     */
-    readonly status?: LaneStatus;
-    /** Heading for the block. Defaults to the document's `id`. */
-    readonly title?: string;
-}
-interface LaneReport {
-    readonly markdown: string;
-}
-/**
- * What this task is waiting on — or `null` at a final.
- *
- * DERIVED, entirely: the events this state routes, grouped by the origin each
- * one DECLARES, in declaration order. Nothing here knows a state name, an event
- * name or a job title, so a consumer that renames half its states changes this
- * output correctly and a consumer with a completely different cast is served by
- * the same function.
- *
- * The degradation is the point of the second half. Provenance is not in
- * `workflow.json` — it is stated at the import boundary or not at all — so a
- * chart imported without it must say what it actually knows, which is WHICH
- * EVENTS the state accepts. It never says who sends them.
- */
-declare function waitingOn(chart: ImportedChart, state: string): string | null;
-/**
- * A lane, as one markdown block.
- *
- * The diagram half is behind {@link drawTask}, which is a translation onto
- * `chartMermaid` — the package's one chart renderer.
- */
-declare function laneReport(input: LaneReportInput): LaneReport;
-
-/** Everything a report needs, however it was obtained. */
-interface LaneSource {
-    readonly workflow: ImportedLane;
-    readonly entries: readonly LogEntry[];
-    /** Present only on the CLI path — the driver's own answer, not ours. */
-    readonly status?: LaneStatus;
-}
-/**
- * PATH 1 — the two files.
- *
- * @param workflowJson the bytes of `<lane>/workflow.json`
- * @param eventsJsonl  the bytes of `<lane>/events.jsonl` (`""` for a fresh lane)
- * @param options      {@link WorkflowImportOptions} — carried straight through
- *                     to the importer, which is the one place it is read.
- */
-declare function laneFromFiles(workflowJson: string, eventsJsonl: string, options?: WorkflowImportOptions): LaneSource;
-/**
- * PATH 2 — the CLI's stdout.
- *
- *     const dir  = ".fabrika/lanes/5842";
- *     const src  = laneFromCli(
- *       readFileSync(`${dir}/workflow.json`, "utf8"),
- *       execFileSync("fabrika", ["lane", "status",  "--lane", "5842"], { encoding: "utf8" }),
- *       execFileSync("fabrika", ["lane", "history", "--lane", "5842"], { encoding: "utf8" }),
- *     );
- *     console.log(laneReport(reportInput(src)).markdown);
- *
- * @param workflowJson the bytes of `<lane>/workflow.json`
- * @param statusStdout `fabrika lane status`'s stdout — `JSON.stringify(status, null, 2)`
- * @param historyStdout `fabrika lane history`'s stdout — the log as a JSON array
- * @param options {@link WorkflowImportOptions} — the same seam as path 1's.
- */
-declare function laneFromCli(workflowJson: string, statusStdout: string, historyStdout: string, options?: WorkflowImportOptions): LaneSource;
-/** A `LaneSource` as the report's input. One line, so neither path spells it. */
-declare function reportInput(source: LaneSource, title?: string): LaneReportInput;
-
-export { type DrawOptions, ImportedChart, ImportedLane, type LaneReport, type LaneReportInput, type LaneSource, LaneStatus, LogEntry, WalkCounts, WorkflowImportOptions, drawTask, laneFromCli, laneFromFiles, laneReport, reportInput, waitingOn, walkedEdges };

package/dist/chart/report/index.js

@@ -1,32 +0,0 @@
-import { parseEventsJsonl, chartFromWorkflowText, parseStatusJson, parseHistoryJson } from '../../chunk-NR7BU22N.js';
-export { UnreplayableLogError, WorkflowImportError, bareEvent, chartFromWorkflow, chartFromWorkflowText, deriveLaneStatus, drawTask, endPolarityOf, eventAlphabet, foldLane, initialOf, initialStates, laneReport, laneTerminalReached, originOf, parseEventsJsonl, parseHistoryJson, parseStatusJson, phaseStandings, statesOf, stepTask, timeline, trippedTasks, waitingOn, walkedEdgeKey, walkedEdges } from '../../chunk-NR7BU22N.js';
-export { edgeKey } from '../../chunk-YWIKDKHY.js';
-import '../../chunk-UOC2PL46.js';
-import '../../chunk-OOYD44JI.js';
-
-// src/chart/report/sources.ts
-function laneFromFiles(workflowJson, eventsJsonl, options = {}) {
-  return {
-    workflow: chartFromWorkflowText(workflowJson, options),
-    entries: parseEventsJsonl(eventsJsonl)
-  };
-}
-function laneFromCli(workflowJson, statusStdout, historyStdout, options = {}) {
-  return {
-    workflow: chartFromWorkflowText(workflowJson, options),
-    entries: parseHistoryJson(historyStdout),
-    status: parseStatusJson(statusStdout)
-  };
-}
-function reportInput(source, title) {
-  return {
-    workflow: source.workflow,
-    entries: source.entries,
-    ...source.status === void 0 ? {} : { status: source.status },
-    ...title === void 0 ? {} : { title }
-  };
-}
-
-export { laneFromCli, laneFromFiles, reportInput };
-//# sourceMappingURL=index.js.map
-//# sourceMappingURL=index.js.map

package/dist/chart/report/index.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../../../src/chart/report/sources.ts"],"names":[],"mappings":";;;;;;;AAsDO,SAAS,aAAA,CACd,YAAA,EACA,WAAA,EACA,OAAA,GAAiC,EAAC,EACtB;AACZ,EAAA,OAAO;AAAA,IACL,QAAA,EAAU,qBAAA,CAAsB,YAAA,EAAc,OAAO,CAAA;AAAA,IACrD,OAAA,EAAS,iBAAiB,WAAW;AAAA,GACvC;AACF;AAkBO,SAAS,YACd,YAAA,EACA,YAAA,EACA,aAAA,EACA,OAAA,GAAiC,EAAC,EACtB;AACZ,EAAA,OAAO;AAAA,IACL,QAAA,EAAU,qBAAA,CAAsB,YAAA,EAAc,OAAO,CAAA;AAAA,IACrD,OAAA,EAAS,iBAAiB,aAAa,CAAA;AAAA,IACvC,MAAA,EAAQ,gBAAgB,YAAY;AAAA,GACtC;AACF;AAGO,SAAS,WAAA,CACd,QACA,KAAA,EACiB;AACjB,EAAA,OAAO;AAAA,IACL,UAAU,MAAA,CAAO,QAAA;AAAA,IACjB,SAAS,MAAA,CAAO,OAAA;AAAA,IAChB,GAAI,OAAO,MAAA,KAAW,MAAA,GAAY,EAAC,GAAI,EAAE,MAAA,EAAQ,MAAA,CAAO,MAAA,EAAO;AAAA,IAC/D,GAAI,KAAA,KAAU,MAAA,GAAY,EAAC,GAAI,EAAE,KAAA;AAAM,GACzC;AACF","file":"index.js","sourcesContent":["// ═══════════════════════════════════════════════════════════════════════════\n// THE TWO INPUT PATHS.\n//\n// Both produce the same `LaneReportInput`, and both take TEXT rather than doing\n// their own I/O — so this module has no `node:fs` in it, runs in a worker or a\n// Durable Object, and the caller keeps the one decision that is genuinely\n// theirs (which bytes, from where).\n//\n//   THE FILE PATH — `workflow.json` + `events.jsonl` off disk. What a tool\n//   running inside the repo already has: the lane directory is right there.\n//   Status is DERIVED, because there is nothing to be handed.\n//\n//   THE CLI PATH — `fabrika lane status` + `fabrika lane history` stdout, plus\n//   the `workflow.json` bytes. This is the one that matters: it means a\n//   standalone inspector can shell out to `fabrika` and need ZERO phoenix\n//   changes, because both verbs already print JSON on stdout and have done\n//   since they were written. Status here is the CLI's OWN derivation, carried\n//   verbatim — the report reads, it does not re-decide.\n//\n// `workflow.json` is read as a file on BOTH paths, deliberately. `lane print`\n// looks like the CLI answer for topology and is not: it emits, per state, the\n// event NAMES a cell exists for and never the targets, so no edge can be drawn\n// from it. The document is local, gitignored and sitting next to the log.\n// ═══════════════════════════════════════════════════════════════════════════\nimport {\n  type LaneStatus,\n  type LogEntry,\n  parseEventsJsonl,\n  parseHistoryJson,\n  parseStatusJson,\n} from \"./fold\";\nimport type { LaneReportInput } from \"./report\";\nimport {\n  chartFromWorkflowText,\n  type ImportedLane,\n  type WorkflowImportOptions,\n} from \"./workflow\";\n\n/** Everything a report needs, however it was obtained. */\nexport interface LaneSource {\n  readonly workflow: ImportedLane;\n  readonly entries: readonly LogEntry[];\n  /** Present only on the CLI path — the driver's own answer, not ours. */\n  readonly status?: LaneStatus;\n}\n\n/**\n * PATH 1 — the two files.\n *\n * @param workflowJson the bytes of `<lane>/workflow.json`\n * @param eventsJsonl  the bytes of `<lane>/events.jsonl` (`\"\"` for a fresh lane)\n * @param options      {@link WorkflowImportOptions} — carried straight through\n *                     to the importer, which is the one place it is read.\n */\nexport function laneFromFiles(\n  workflowJson: string,\n  eventsJsonl: string,\n  options: WorkflowImportOptions = {},\n): LaneSource {\n  return {\n    workflow: chartFromWorkflowText(workflowJson, options),\n    entries: parseEventsJsonl(eventsJsonl),\n  };\n}\n\n/**\n * PATH 2 — the CLI's stdout.\n *\n *     const dir  = \".fabrika/lanes/5842\";\n *     const src  = laneFromCli(\n *       readFileSync(`${dir}/workflow.json`, \"utf8\"),\n *       execFileSync(\"fabrika\", [\"lane\", \"status\",  \"--lane\", \"5842\"], { encoding: \"utf8\" }),\n *       execFileSync(\"fabrika\", [\"lane\", \"history\", \"--lane\", \"5842\"], { encoding: \"utf8\" }),\n *     );\n *     console.log(laneReport(reportInput(src)).markdown);\n *\n * @param workflowJson the bytes of `<lane>/workflow.json`\n * @param statusStdout `fabrika lane status`'s stdout — `JSON.stringify(status, null, 2)`\n * @param historyStdout `fabrika lane history`'s stdout — the log as a JSON array\n * @param options {@link WorkflowImportOptions} — the same seam as path 1's.\n */\nexport function laneFromCli(\n  workflowJson: string,\n  statusStdout: string,\n  historyStdout: string,\n  options: WorkflowImportOptions = {},\n): LaneSource {\n  return {\n    workflow: chartFromWorkflowText(workflowJson, options),\n    entries: parseHistoryJson(historyStdout),\n    status: parseStatusJson(statusStdout),\n  };\n}\n\n/** A `LaneSource` as the report's input. One line, so neither path spells it. */\nexport function reportInput(\n  source: LaneSource,\n  title?: string,\n): LaneReportInput {\n  return {\n    workflow: source.workflow,\n    entries: source.entries,\n    ...(source.status === undefined ? {} : { status: source.status }),\n    ...(title === undefined ? {} : { title }),\n  };\n}\n"]}

package/dist/chunk-2YFLOCWX.js

@@ -1,15 +0,0 @@
-// src/subs/from-timeout.ts
-function fromTimeout(msgFn) {
-  return (sub, _ctx, dispatch) => {
-    const handle = setTimeout(() => {
-      dispatch(msgFn(sub));
-    }, sub.delayMs);
-    return () => {
-      clearTimeout(handle);
-    };
-  };
-}
-
-export { fromTimeout };
-//# sourceMappingURL=chunk-2YFLOCWX.js.map
-//# sourceMappingURL=chunk-2YFLOCWX.js.map

package/dist/chunk-2YFLOCWX.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/subs/from-timeout.ts"],"names":[],"mappings":";AAgCO,SAAS,YACd,KAAA,EACiC;AACjC,EAAA,OAAO,CAAC,GAAA,EAAK,IAAA,EAAM,QAAA,KAAa;AAC9B,IAAA,MAAM,MAAA,GAAS,WAAW,MAAM;AAC9B,MAAA,QAAA,CAAS,KAAA,CAAM,GAAG,CAAC,CAAA;AAAA,IACrB,CAAA,EAAG,IAAI,OAAO,CAAA;AACd,IAAA,OAAO,MAAM;AACX,MAAA,YAAA,CAAa,MAAM,CAAA;AAAA,IACrB,CAAA;AAAA,EACF,CAAA;AACF","file":"chunk-2YFLOCWX.js","sourcesContent":["// ---------------------------------------------------------------------------\n// fromTimeout — universal `setTimeout`-shaped Sub factory.\n//\n// Same lifecycle shape as `fromInterval` minus the recurrence: the\n// scheduled callback fires once, the cleanup is `clearTimeout`. Two\n// observable consequences worth pinning explicitly:\n//\n//   1. The Sub stays in the desired set until the caller removes it from\n//      `subscriptions(state)`. The substrate's reconcile pass does NOT\n//      auto-remove a Sub on cleanup — the timer fires, the callback\n//      dispatches its Msg, and if the Sub is still present on the next\n//      transition's desired set, the factory will... NOT re-fire. The\n//      timer handle is captured per-subscribe call; after it fires, the\n//      handle is exhausted. Adding the same Sub a second time (via a new\n//      id) is the only way to re-arm.\n//\n//   2. Cleanup before the timer fires cancels the pending dispatch. This\n//      is the \"cancel on state exit\" pattern: model the timeout as a Sub\n//      whose `subscriptions(state)` returns it only in the state where the\n//      timeout should be armed. When the state changes, the substrate's\n//      reconcile drops the Sub and the factory's cleanup fires before the\n//      timer does.\n//\n// Like `fromInterval`, the delay lives on the Sub (`delayMs`) — same id\n// means same scheduled timeout; changing the delay requires a new id.\n// ---------------------------------------------------------------------------\n\nimport type { Sub } from \"../index\";\nimport type { SubscribeHandler } from \"./types\";\n\ntype TimeoutSubData = { delayMs: number };\n\nexport function fromTimeout<S extends Sub & TimeoutSubData, M>(\n  msgFn: (sub: S) => M,\n): SubscribeHandler<S, M, unknown> {\n  return (sub, _ctx, dispatch) => {\n    const handle = setTimeout(() => {\n      dispatch(msgFn(sub));\n    }, sub.delayMs);\n    return () => {\n      clearTimeout(handle);\n    };\n  };\n}\n"]}