@pablotech/akesi 0.1.32 → 0.1.34

package/dates.ts

@@ -27,7 +27,7 @@ export function formatDay(iso: string | undefined | null): string {
   return `${MONTHS[Number(m) - 1]} ${Number(d)}, ${y}`;
 }
 
-// M107 — a type="date" input fires `change` on every keystroke inside an already-plausible year
+// A type="date" input fires `change` on every keystroke inside an already-plausible year
 // segment, zero-padded (e.g. typing just "2" of "2026" reports "0002-08-15") — not only once the
 // full year is typed. A plain truthiness/length check on `value` fires on that first padded digit.
 // Require a 4-digit year that isn't itself a padding artifact (<1000) before treating it as done.

package/finding-assemble.ts

@@ -22,7 +22,7 @@ export interface FindingAIResponse {
   };
   /** Leaf-owned: absent from a core response, present on an older stored finding. */
   studyResults?: { study: string; result: string; group: string }[];
-  // M92 — no `noteId`/label field here: a note has no short verbatim-echoable label like Study's
+  // No `noteId`/label field here: a note has no short verbatim-echoable label like Study's
   // `focus`, so entries are paired back to `factors.noteEntries` by array position, not content.
   // See assembleFinding's `meta.noteIds` (the caller supplies the parallel id array).
   /** Leaf-owned: absent from a core response, present on an older stored finding. */
@@ -673,7 +673,7 @@ export function assembleFinding(
     inputsHash: string;
     nodeHashes: Record<string, string>;
     generatedBy: ClientFinding["generatedBy"];
-    // M92 — the ordered ids of the Note entries the prompt presented (populatedNoteEntries), zipped
+    // The ordered ids of the Note entries the prompt presented (populatedNoteEntries), zipped
     // positionally against parsed.noteResults since a note has no label the LLM could echo back.
     noteIds: string[];
     // 06/Gap A — injected rather than looked up here, so this module carries no dependency on

package/marker-deltas.ts

@@ -1,9 +1,10 @@
-// Cross-study deltas (W2). The single source of truth for "what changed" — shared
+// Cross-study deltas. The single source of truth for "what changed" — shared
 // by a host's chart/print surfaces and by the Finding prompt builder here, so the change
 // shown on screen and the change the model reasons over can never disagree.
 //
-// Grouping is by stored marker name, which is canonical post-W1c (imaging-catalog),
-// so a metric is one series. `fromComparison` rows (W1b) are real datapoints here; a
+// Grouping is by stored marker name, which is canonical once imaging-catalog markers are
+// stored the same way as lab markers, so a metric is one series. `fromComparison` rows are
+// real datapoints here; a
 // directly-measured reading at the same marker|date already won at ingest.
 
 import type { Client, MarkerResult } from "./types";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pablotech/akesi",
-  "version": "0.1.32",
+  "version": "0.1.34",
   "description": "Schema-constrained clinical reasoning over lab and marker data, where every constraint stated to the model in prose is re-enforced in code on the response.",
   "repository": {
     "type": "git",

package/pinned-queries.ts

@@ -61,7 +61,7 @@ export function pinnedQueries(client: Client): PinnedQuery[] {
     if (t) out.push({ section, label: clip(t) });
   };
 
-  // M74 reversed, on the owner's instruction (2026-08-20): a ratio name used to be barred from the
+  // On the owner's instruction (2026-08-20): a ratio name used to be barred from the
   // prompt outright. As an area of query it is safe and useful — "look at the TG/HDL ratio" is a
   // topic, not a reading — and the block below is explicit that it is not data.
   for (const name of client.pinnedRatios ?? []) push("Marker ratios", name);

package/report-merge.ts

@@ -297,7 +297,7 @@ export interface SourceEditPatch {
   date: string;
 }
 
-// M66 P3 — patch ONE source and its linked DiseaseEntry rows (by position, in sourceId order) in
+// Patch ONE source and its linked DiseaseEntry rows (by position, in sourceId order) in
 // one mutation, keyed by sourceId — the patch counterpart to removeSource's drop. `diseasePatches`
 // must line up 1:1 with diseasesForSource(sourceId)'s current order; a short/mismatched array is
 // ignored past its own length (no add/remove of diagnoses here). Raw values in — normalizeClientDraft

package/treatment-bucket.ts

@@ -12,7 +12,7 @@ import { formatDay } from "./dates";
 
 export type Bucket = "past" | "ongoing" | "planned";
 
-// M102 Phase 1 — the display label for a bucket badge (Treatment's Ungrouped view, which
+// The display label for a bucket badge (Treatment's Ungrouped view, which
 // otherwise concatenates all three buckets with no other visual distinction).
 export const BUCKET_LABEL: Record<Bucket, string> = { ongoing: "Ongoing", planned: "Planned", past: "Past" };
 
@@ -73,7 +73,7 @@ export function collapseByName(items: TreatmentItem[]): TreatmentItem[] {
       id: latest.id,
       name: latest.name,
       dose: latest.dose,
-      // M104 — carry the structured dose fields through too, same "latest row wins" rule as `dose`
+      // Carry the structured dose fields through too, same "latest row wins" rule as `dose`
       // itself; formatDose() prefers these over `dose`, so dropping them here would silently blank
       // out any collapsed-view display for a titration step entered through the new Amount/Unit form.
       doseAmount: latest.doseAmount,
@@ -110,16 +110,16 @@ export interface NamedTreatmentGroup {
   rows: TreatmentItem[];
 }
 
-// M108 — primary group order: Planned drugs first, then Ongoing, then Past — recency of use. A
+// Primary group order: Planned drugs first, then Ongoing, then Past — recency of use. A
 // group's bucket is its NEWEST row's (rows[0], already sorted descending below), so a drug
 // currently mid-titration reads as Ongoing even if an older row of the same drug once looked
-// Planned. M109 — within one bucket, groups sort alphabetically (secondary key), not entry order.
+// Planned. Within one bucket, groups sort alphabetically (secondary key), not entry order.
 const GROUP_BUCKET_ORDER: Record<Bucket, number> = { planned: 0, ongoing: 1, past: 2 };
 
-// M103 — the Medicine audit view's grouping: every raw row for a drug together, unlike
+// The Medicine audit view's grouping: every raw row for a drug together, unlike
 // collapseByName which discards all but one representative row per name.
 //
-// M105 — rows sorted newest-first (start descending): the table must always read newest-to-oldest,
+// Rows sorted newest-first (start descending): the table must always read newest-to-oldest,
 // top to bottom. dateGaps() below is written against this same descending order.
 export function groupByName(items: TreatmentItem[], today: string): NamedTreatmentGroup[] {
   const byName = new Map<string, TreatmentItem[]>();
@@ -140,31 +140,31 @@ export function groupByName(items: TreatmentItem[], today: string): NamedTreatme
 
 export type DateGapVerdict = "ok" | "gap" | "overlap";
 
-// M104 — whole-day distance between two full YYYY-MM-DD dates (nextStart - end), or null if
+// Whole-day distance between two full YYYY-MM-DD dates (nextStart - end), or null if
 // either isn't full day precision (legacy month/year-only can't do calendar-day arithmetic).
 function daysBetween(a: string, b: string): number | null {
   if (!/^\d{4}-\d{2}-\d{2}$/.test(a) || !/^\d{4}-\d{2}-\d{2}$/.test(b)) return null;
   return Math.round((Date.parse(b) - Date.parse(a)) / 86400000);
 }
 
-// M103 — one verdict per consecutive pair in an already-sorted `rows` (see groupByName), comparing
+// One verdict per consecutive pair in an already-sorted `rows` (see groupByName), comparing
 // the OLDER row's end against the NEWER row's start: no end (still ongoing) or an unknown start
 // can't be judged, so those read "ok" rather than a false positive. Length is rows.length - 1.
 //
-// M104 — a titration step ending 2026-06-30 with the next starting 2026-07-01 is back-to-back
+// A titration step ending 2026-06-30 with the next starting 2026-07-01 is back-to-back
 // coverage, not a gap: prefer day-precision arithmetic (0 or 1 day apart both read "ok") over the
 // cmp() prefix comparison, which only recognized an exact same-day handoff as contiguous. Falls
 // back to cmp() when either date isn't full day precision.
 //
-// M105 — `rows` is newest-first (groupByName sorts descending), so for the pair at (i, i+1), i+1
+// `rows` is newest-first (groupByName sorts descending), so for the pair at (i, i+1), i+1
 // is the OLDER row and i is the NEWER one — verdict[i] describes the gap/overlap between them.
 //
-// M106 — symmetric with the gap side: a 1-day overlap (the newer row starts the day before the
+// Symmetric with the gap side: a 1-day overlap (the newer row starts the day before the
 // older one's recorded end — a rounding/entry-day wobble, not a real double-dosing period) also
 // reads "ok". Only a 2+ day overlap is worth flagging. This only applies to the day-precision
 // branch — the cmp() fallback (month/year-only dates) has no day-scale magnitude to be lenient about.
 //
-// M110 — an AM row and a PM row covering the same dates aren't double-dosing, they're a twice-daily
+// An AM row and a PM row covering the same dates aren't double-dosing, they're a twice-daily
 // split — only downgrades a would-be "overlap" (a real gap between an AM and a PM step is still a
 // gap; this isn't a blanket "ignore timing" exemption).
 function splitByTiming(a: TreatmentItem, b: TreatmentItem): boolean {
@@ -198,7 +198,7 @@ export function dateGaps(rows: TreatmentItem[]): DateGapVerdict[] {
 // The verbatim label a PLANNED treatment presents to the Finding (Patient Plan Action, treatmentGroups
 // patient ref, planAssessmentRows key) — its name plus dose when present. Must be identical everywhere
 // the ref is matched (finding-generate input block, finding-assemble expected set, treatment-groups resolve).
-// M104 — the display string for a dose: structured amount/unit/frequency when the record has been
+// The display string for a dose: structured amount/unit/frequency when the record has been
 // entered/edited through the new form, reproducing the pre-existing "6mg/week" convention so
 // treatmentLabel()'s output (and everything matched against it) doesn't change shape; falls back to
 // the legacy free-text `dose` string for anything a host has not yet migrated.

package/treatment-infer.ts

@@ -1,4 +1,4 @@
-// M54/4 — treatment add-flow intake: read what the user actually has about a product — photos of a
+// Treatment add-flow intake: read what the user actually has about a product — photos of a
 // bottle/package/label, or the product sheet as pasted text — and propose a record. Pure of
 // Node/process/env, mirroring report-extract.ts's shape. The Anthropic client is INJECTED and the
 // model is a required arg (no default), so this module never touches process.env or the config.

package/types.ts

@@ -128,7 +128,7 @@ export interface TreatmentItem {
   id: string;
   pinned?: boolean;
   name: string;
-  // M104 — superseded by doseAmount/doseUnit/doseFrequency (below) for anything entered through the
+  // Superseded by doseAmount/doseUnit/doseFrequency (below) for anything entered through the
   // edit form; kept as the display/matching fallback for un-migrated records (see formatDose() in
   // treatment-bucket.ts, and whatever one-time conversion a host runs).
   dose?: string;
@@ -429,15 +429,15 @@ export interface ClientFinding {
   // findings without it still render (StudyResults falls back to a flat list).
   studyResults?: { study: string; result: string; group?: string }[];
   // One inference per populated Note row (factors.noteEntries); keyed by `noteId` rather than a
-  // label (M92 — unlike Study's short hand-picked `focus` labels, a note's `text` is unbounded
-  // free prose, unreliable for the LLM to echo back verbatim for pairing).
+  // label — unlike Study's short hand-picked `focus` labels, a note's `text` is unbounded
+  // free prose, unreliable for the LLM to echo back verbatim for pairing.
   noteResults?: { noteId: string; result: string; group?: string }[];
-  // M94/M97 §C — one inference per known allergy (factors.allergies) / family history entry
+  // One inference per known allergy (factors.allergies) / family history entry
   // (factors.familyHistory), keyed by id like noteResults, paired by array position (no natural
   // unique label to echo back).
   allergyResults?: { allergyId: string; result: string; group?: string }[];
   familyResults?: { familyId: string; result: string; group?: string }[];
-  // M102 — mirrors allergyResults/familyResults exactly, for Reports diagnoses (factors.diseases),
+  // Mirrors allergyResults/familyResults exactly, for Reports diagnoses (factors.diseases),
   // which previously had no AI-paired leaf at all.
   diseaseResults?: { diseaseId: string; result: string; group?: string }[];
   disease: { group: string; finding: string }[];

package/unit-systems.ts

@@ -36,7 +36,7 @@ const IMPERIAL_TO_METRIC: Record<string, { unit: string; factor: number }> = {
   "in³": { unit: "cm³", factor: 16.387064 },
 };
 
-// M93 — markers where the metric unit IS the US-prevailing clinical convention, so the
+// Markers where the metric unit IS the US-prevailing clinical convention, so the
 // generic PHYSICAL_TO_IMPERIAL unit-keyed table must NOT convert them (e.g. visceral adipose
 // tissue mass is reported in grams in US practice too, never ounces/lb — the owner's example,
 // extended here to the sibling DEXA body-composition markers sharing the same convention).
@@ -49,7 +49,7 @@ export const PHYSICAL_NO_CONVERT = new Set<string>([
   "Subcutaneous adipose tissue area",
 ]);
 
-// M93 — cosmetic unit-STRING variants for the same physical unit, straight from different lab
+// Cosmetic unit-STRING variants for the same physical unit, straight from different lab
 // source formats (values stay as-reported per the module doc above; only the DISPLAYED label is
 // canonicalized, never the stored data). eGFR renders identically regardless of which lab
 // formatted its unit string.
@@ -61,7 +61,7 @@ export function canonicalUnit(unit: string): string {
   return UNIT_ALIAS[unit] ?? unit;
 }
 
-// M93 — compound clinical units that are, on research, reported identically in US and SI/
+// Compound clinical units that are, on research, reported identically in US and SI/
 // international practice — no US-customary form exists in routine use, so no conversion ever
 // applies regardless of marker. NEEDS VERIFICATION against a clinical reference before treating
 // as final; each entry's marker(s) are noted so a reviewer can check the specific convention.
@@ -84,7 +84,7 @@ export interface AnalyteRule {
 }
 export const ANALYTE: Record<string, AnalyteRule> = {
   // Lipid/glucose panel — mirrors the in-repo ingest table (parsers/healthmatters.ts
-  // NORMALIZE, in production since W1); 1/k equals that table's factor (cross-checked by test).
+  // NORMALIZE); 1/k equals that table's factor (cross-checked by test).
   Glucose: { us: "mg/dL", si: "mmol/L", k: 1 / 18.02 }, // glucose MW 180.16
   "Estimated Average Glucose (eAG)": { us: "mg/dL", si: "mmol/L", k: 1 / 18.02 },
   "Total Cholesterol": { us: "mg/dL", si: "mmol/L", k: 1 / 38.67 }, // chol MW 386.65
@@ -133,7 +133,7 @@ export const ANALYTE: Record<string, AnalyteRule> = {
   // Monovalent electrolytes: mEq/L (US) and mmol/L (SI) are numerically identical (valence 1).
   "Potassium, Serum (Kalium)": { us: "mEq/L", si: "mmol/L", k: 1 },
   "Sodium, Serum (Natrium)": { us: "mEq/L", si: "mmol/L", k: 1 },
-  // M93 — urine albumin/creatinine ratio: US commonly reports mg/g creatinine; UK/Canada/
+  // Urine albumin/creatinine ratio: US commonly reports mg/g creatinine; UK/Canada/
   // Australia and KDIGO's international staging table use mg/mmol creatinine. Factor derived
   // from creatinine MW 113.12 g/mol (1 g creatinine = 8.84 mmol, so mg/mmol = mg/g × 0.1131).
   // NEEDS VERIFICATION against a clinical reference before relying on this — flagged per the
@@ -144,7 +144,7 @@ export const ANALYTE: Record<string, AnalyteRule> = {
 
 // The units that genuinely differ US↔SI, or need an explicit verified-non-convertible decision —
 // used by the coverage gate to flag any (marker, unit) pair carrying one of these WITHOUT a rule
-// (so a gap can never be silent). M93 extended this beyond molar-concentration units to the
+// (so a gap can never be silent) — extended beyond molar-concentration units to the
 // compound/physical units researched above.
 export const CONVERTIBLE_UNIT_CLASS = new Set([
   "mg/dL", "ng/dL", "pg/mL", "µg/dL", "ug/dL", "mcg/dL", "ng/mL",