@diagrammo/dgmo 0.47.0 → 0.48.1

package/src/pert/diagnostics.ts

@@ -1,110 +0,0 @@
-import type { DiagnosticSpec } from '../diagnostics';
-
-// ============================================================
-// PERT chart diagnostics
-// ============================================================
-//
-// Additive metadata catalog for the PERT parser's coded diagnostics.
-// The parser (`src/pert/parser.ts`) still owns emission — these codes are
-// passed as inline string literals to `makeDgmoError(line, msg, severity,
-// code)` via the local `error()`/`warn()` helpers. This file re-declares
-// each code's canonical wording, severity, and a triggering example so the
-// catalog stays discoverable without changing the parser.
-//
-// Every `severity` below reflects the RUNTIME value actually passed to
-// makeDgmoError at the emit site (via `error()` → 'error' / `warn()` →
-// 'warning'), verified against `src/pert/parser.ts`. All PERT codes'
-// runtime severities agree with their `E_`/`W_` prefix.
-
-/** Keyed specs — referenced by the parser's `emit()` call sites. */
-export const PERT_DX = {
-  BOTH_ANCHORS: {
-    code: 'E_PERT_BOTH_ANCHORS',
-    severity: 'error', // Runtime: error() @ parser.ts ~1508
-    chartType: 'pert',
-    title: 'Both start-date and end-date set',
-    // Message interpolates an optional `priorRef` suffix referencing the
-    // first anchor's kind + line. Builder tolerates `{}` (suffix omitted).
-    message: (p) => {
-      const kind = p.firstAnchorKey;
-      const line = p.firstAnchorLine;
-      const priorRef =
-        kind && line
-          ? ` Conflicts with \`${String(kind)}\` declared on line ${String(line)}.`
-          : '';
-      return `Specify \`start-date\` or \`end-date\`, not both. Use one anchor — both directives are discarded; re-author one to recover.${priorRef}`;
-    },
-    hint: 'Pick a single anchor: either `start-date` (forward) or `end-date` (backward).',
-    example: 'pert\nstart-date 2026-06-01\nend-date 2026-09-15\nA 1 2 3\n',
-  },
-  END_DATE_NOW: {
-    code: 'E_PERT_END_DATE_NOW',
-    severity: 'error', // Runtime: error() @ parser.ts ~1530
-    chartType: 'pert',
-    title: '`end-date now` not allowed',
-    message:
-      '`end-date` requires an explicit YYYY-MM-DD; `now` is only valid for `start-date`.',
-    hint: 'Give `end-date` a literal date, or use `start-date now` if you want today.',
-    example: 'pert\nend-date now\nA 1 2 3\n',
-  },
-  INVALID_DATE: {
-    code: 'E_PERT_INVALID_DATE',
-    severity: 'error', // Runtime: error() @ parser.ts ~1519 and ~1545
-    chartType: 'pert',
-    title: 'Invalid anchor date',
-    // Emitted from TWO sites with different wording:
-    //  (a) empty value @ ~1519:  "`${key}` requires a full date (YYYY-MM-DD), got '${value}'."
-    //  (b) unparseable  @ ~1545:  "Invalid date '${trimmed}' for ${key}. Expected YYYY-MM-DD."
-    // The builder reproduces BOTH: pass `empty: true` + `value`/`key` for
-    // variant (a); pass `trimmed`/`key` for variant (b). The `{}` default
-    // shows variant (b)'s representative wording.
-    message: (p) => {
-      const key = p.key ?? 'start-date';
-      if (p.empty) {
-        return `\`${String(key)}\` requires a full date (YYYY-MM-DD), got '${String(p.value ?? '')}'.`;
-      }
-      const date = p.trimmed ?? p.value;
-      return date
-        ? `Invalid date '${String(date)}' for ${String(key)}. Expected YYYY-MM-DD.`
-        : `Invalid date for ${String(key)}. Expected YYYY-MM-DD.`;
-    },
-    hint: 'Use a calendar-valid ISO date, e.g. `2026-06-01` (dashes, not slashes).',
-    example: 'pert\nstart-date 2026-13-99\nA 1 2 3\n',
-  },
-  NEAR_DIRECTIVE: {
-    code: 'E_PERT_NEAR_DIRECTIVE',
-    severity: 'error', // Runtime: error() @ parser.ts ~938
-    chartType: 'pert',
-    title: 'Near-miss directive typo',
-    // Interpolates the mistyped head + the suggested canonical directive.
-    message: (p) => {
-      const head = p.head ?? 'start';
-      const canonical = p.canonical ?? 'start-date';
-      return `Unknown directive '${String(head)}'. Did you mean '${String(canonical)}'?`;
-    },
-    hint: 'Use the full directive name (`start-date`, `end-date`, `default-confidence`, `time-unit`).',
-    example: 'pert\nstart 2026-06-01\nA 1 2 3\n',
-  },
-  BD_WITH_ANCHOR: {
-    code: 'W_PERT_BD_WITH_ANCHOR',
-    severity: 'warning', // Runtime: warn() @ parser.ts ~1024
-    chartType: 'pert',
-    title: 'Business days with date anchor',
-    message:
-      '`bd` (business days) is treated as calendar days when `start-date`/`end-date` is set. For business-day scheduling with weekend/holiday awareness, use Gantt.',
-    hint: 'Drop the date anchor, or switch to Gantt for weekend/holiday-aware scheduling.',
-    example: 'pert\ntime-unit bd\nstart-date 2026-06-01\nA 1 2 3\n',
-  },
-  SUBDAY_WITH_ANCHOR: {
-    code: 'W_PERT_SUBDAY_WITH_ANCHOR',
-    severity: 'warning', // Runtime: warn() @ parser.ts ~1030
-    chartType: 'pert',
-    title: 'Sub-day time-unit with date anchor',
-    message:
-      "Date display rounds to whole days; sub-day `time-unit` ('h'/'min') will lose precision when `start-date`/`end-date` is set. For honest output use `time-unit d`.",
-    hint: 'Use `time-unit d` when anchoring to dates, or remove the anchor.',
-    example: 'pert\ntime-unit h\nstart-date 2026-06-01\nA 1 2 3\n',
-  },
-} satisfies Record<string, DiagnosticSpec>;
-
-export const PERT_DIAGNOSTICS: DiagnosticSpec[] = Object.values(PERT_DX);

package/src/pert/index.ts

@@ -1,43 +0,0 @@
-// ============================================================
-// PERT subpath entry — minimal surface for Web Workers
-// ============================================================
-//
-// `import { simulateCanonical } from '@diagrammo/dgmo/pert'` resolves
-// to a tree-shaken bundle that contains only the simulator + types,
-// not the full d3/echarts/jsdom dependency chain. Use this entry from
-// Web Workers so they don't ship the entire renderer to the worker
-// thread.
-//
-// All public types are re-exported so workers can typecheck against
-// `ResolvedPert`, `MonteCarloResult`, etc. without pulling in the
-// main `@diagrammo/dgmo` entry.
-
-export {
-  mulberry32,
-  sampleBetaPert,
-  simulateCanonical,
-  simulateFast,
-  buildSimulationContext,
-} from './monte-carlo';
-
-export type { ExpandedActivity, SimulateOptions } from './monte-carlo';
-
-export type {
-  MonteCarloResult,
-  ParsedPert,
-  PertActivity,
-  PertEdge,
-  PertGroup,
-  PertExpandedActivity,
-  PertMilestone,
-  PertOptions,
-  PertDirection,
-  ResolvedActivity,
-  ResolvedGroup,
-  ResolvedPert,
-  NodeDetail,
-  PertLayoutNode,
-  PertLayoutEdge,
-  PertLayoutGroup,
-  LayoutResult,
-} from './types';

package/src/pert/internal.ts

@@ -1,252 +0,0 @@
-// ============================================================
-// PERT — internal types
-// ============================================================
-//
-// Not re-exported from the package barrel. Parser/analyzer/renderer
-// share these; consumers should reach for `./types` instead.
-
-import type { Duration, DurationUnit } from '../gantt/types';
-import { formatDateKey, parseGanttDate } from '../utils/duration';
-
-/**
- * A three-point duration estimate. Each component is a parsed
- * `Duration { amount, unit }` so mixed units (`1w 2w 3m`) are
- * preserved; the analyzer normalizes to `options.timeUnit` for
- * arithmetic.
- */
-export interface DurationEstimate {
-  o: Duration;
-  m: Duration;
-  p: Duration;
-  /**
-   * When true, only an M token was given on the source line and the
-   * analyzer must expand O/P from confidence factors. When false, the
-   * user wrote an explicit O M P triple (even when all three values
-   * are equal — zero-variance is a valid, deterministic estimate).
-   */
-  mOnly: boolean;
-}
-
-/** Named confidence level. */
-export type ConfidenceLevel = 'high' | 'medium' | 'low';
-
-/** Resolved O/P heuristic factors. */
-export interface ConfidenceFactors {
-  oFactor: number;
-  pFactor: number;
-}
-
-/** Heuristic defaults (see spec § Heuristic Defaults). */
-export const CONFIDENCE_TABLE: Record<ConfidenceLevel, ConfidenceFactors> = {
-  high: { oFactor: 0.9, pFactor: 1.5 },
-  medium: { oFactor: 0.75, pFactor: 3.0 },
-  low: { oFactor: 0.5, pFactor: 4.0 },
-};
-
-/**
- * Resolve a `confidence` directive value to factor pair.
- * Accepts named levels (`high`/`medium`/`low`) or `O/P` factor pair
- * (`0.6/2.5`). Returns `null` on a malformed value.
- */
-export function resolveConfidence(value: string): ConfidenceFactors | null {
-  const trimmed = value.trim().toLowerCase();
-  if (trimmed in CONFIDENCE_TABLE) {
-    return CONFIDENCE_TABLE[trimmed as ConfidenceLevel];
-  }
-  const factorMatch = trimmed.match(/^(\d+(?:\.\d+)?)\s*\/\s*(\d+(?:\.\d+)?)$/);
-  if (factorMatch) {
-    // In-bounds by regex match: groups 1 and 2 are guaranteed present.
-    const oFactor = parseFloat(factorMatch[1]!);
-    const pFactor = parseFloat(factorMatch[2]!);
-    if (oFactor > 0 && pFactor > 0) return { oFactor, pFactor };
-  }
-  return null;
-}
-
-/**
- * Per-activity layout-overrides shape — the diagrammo-app holds expansion
- * state in its own store and passes overrides to `relayoutPert`.
- */
-export type LayoutOverrides = Record<string, { width: number; height: number }>;
-
-/** Pass 1 raw declaration record. */
-export interface DeclarationSite {
-  /** Original name token (multi-word, pre-alias-strip). */
-  name: string;
-  /** Alias from `as <id>` suffix, or undefined. */
-  alias?: string;
-  /** Raw duration tokens (numeric strings) — empty for TBD. */
-  durationTokens: string[];
-  /** Raw pipe-metadata segment (everything after `|`), or undefined. */
-  pipeMetadata?: string;
-  /** Source line (1-based). */
-  lineNumber: number;
-  /** Pending group id from the enclosing block at the source line. */
-  groupHint?: string;
-}
-
-/** Pass 1 raw reference record. */
-export interface ReferenceSite {
-  /** Source activity id (resolved at edge-creation time). */
-  sourceName: string;
-  sourceLineNumber: number;
-  /** Target name as written. */
-  targetName: string;
-  targetLineNumber: number;
-  /** Dependency type (default FS when no edge label). */
-  type: import('./types').EdgeType;
-  /** Lag duration; null = zero offset. Negative amount = lead. */
-  lag: import('../gantt/types').Duration | null;
-}
-
-// ============================================================
-// Date anchoring helpers
-// ============================================================
-//
-// `start-date` / `end-date` directives let PERT diagrams render
-// real calendar dates instead of numeric day-offsets. These helpers
-// own the host-TZ-invariant arithmetic; reuse them everywhere a date
-// flows through PERT (parser, analyzer, renderer).
-
-/** Time-unit → calendar-day conversion, mirroring analyzer's table. */
-const UNIT_TO_DAYS_LOCAL: Record<DurationUnit, number> = {
-  min: 1 / (60 * 24),
-  h: 1 / 24,
-  d: 1,
-  bd: 1, // PERT has no calendar; bd ≈ d for analytical purposes
-  w: 7,
-  m: 30,
-  q: 90,
-  y: 365,
-  s: 14, // sprint (14 calendar days) — not seconds
-};
-
-export function unitToDays(unit: DurationUnit): number {
-  return UNIT_TO_DAYS_LOCAL[unit];
-}
-
-/** Strict `YYYY-MM-DD` literal — no time component, no other formats. */
-const ISO_DATE_RE = /^\d{4}-\d{2}-\d{2}$/;
-
-/**
- * TZ-safe parse of a `YYYY-MM-DD` string into a local-time `Date`.
- * Rejects:
- *   - shape mismatches (e.g. `2026/06/01`, `2026-6-1`)
- *   - invalid calendar dates (`2026-13-99`, `2026-02-31`)
- * Returns `null` on rejection.
- */
-export function parseLocalISODate(iso: string): Date | null {
-  if (!ISO_DATE_RE.test(iso)) return null;
-  const date = parseGanttDate(iso);
-  // Round-trip check rejects calendar wrap-arounds like 2026-13-99
-  // (which JS happily reinterprets as 2027-01-99 etc.).
-  if (formatDateKey(date) !== iso) return null;
-  return date;
-}
-
-/**
- * Format a `Date` as `YYYY-MM-DD` using local-time getters (NOT
- * `toISOString`, which silently shifts to UTC and produces off-by-one
- * results in non-UTC zones).
- */
-export function formatLocalISODate(date: Date): string {
-  return formatDateKey(date);
-}
-
-/**
- * Add `days` calendar days to an ISO date string, returning a new
- * `YYYY-MM-DD`. Single rounding point at entry, symmetric (round-half-
- * away-from-zero) so forward and backward anchors agree at fractional
- * boundaries. Returns the input unchanged when it fails to parse —
- * upstream validation should have caught that, so this is defensive.
- */
-export function addCalendarDays(iso: string, days: number): string {
-  const start = parseLocalISODate(iso);
-  if (!start) return iso;
-  // Symmetric round-half-away-from-zero. `Math.round` rounds .5
-  // toward +∞, which makes forward (+17.5) and backward (-17.5) of
-  // the same offset disagree.
-  const whole = Math.sign(days) * Math.round(Math.abs(days));
-  const result = new Date(
-    start.getFullYear(),
-    start.getMonth(),
-    start.getDate() + whole,
-    start.getHours(),
-    start.getMinutes()
-  );
-  return formatLocalISODate(result);
-}
-
-// ============================================================
-// Cell value formatters
-// ============================================================
-//
-// Shared by `layout.ts` (for column-width measurement) and
-// `renderer.ts` (for actual cell text). Pure functions; identical
-// inputs → identical outputs so the measured width matches the
-// rendered text exactly.
-
-export function formatDuration(
-  value: number | null,
-  unit: DurationUnit,
-  nullLabel: string | null
-): string {
-  if (value === null) return nullLabel ?? '?';
-  const rounded = Math.round(value * 100) / 100;
-  const display = rounded.toFixed(2).replace(/\.?0+$/, '');
-  return `${display}${unit}`;
-}
-
-/**
- * Format an ES / EF / LS / LF cell. When `projectStart` is set, the
- * numeric offset (in `unit`) becomes a calendar date; otherwise we
- * fall back to the numeric duration label so unanchored diagrams keep
- * their original output byte-for-byte.
- */
-export function formatScheduleValue(
-  value: number | null,
-  projectStart: string | null,
-  unit: DurationUnit,
-  nullLabel: string | null
-): string {
-  if (value === null) return nullLabel ?? '?';
-  if (projectStart === null) return formatDuration(value, unit, nullLabel);
-  return addCalendarDays(projectStart, value * unitToDays(unit));
-}
-
-/**
- * Format a sprint-indexed schedule cell as `S<n>`. The activity's value
- * is in sprint units (offset from `sprint-number`), so display = base +
- * round(value). Fractional sprint offsets are rounded to nearest int —
- * sprints are inherently discrete iteration boundaries.
- */
-export function formatSprintCell(
-  value: number | null,
-  sprintNumber: number,
-  nullLabel: string | null
-): string {
-  if (value === null) return nullLabel ?? '?';
-  const rounded = Math.round(value);
-  return `S${sprintNumber + rounded}`;
-}
-
-/**
- * Format a slack cell. Anchored diagrams normalize slack to calendar
- * days regardless of `time-unit` (per spec C6); unanchored diagrams
- * keep the original behavior.
- */
-export function formatSlackValue(
-  value: number | null,
-  projectStart: string | null,
-  unit: DurationUnit,
-  nullLabel: string | null
-): string {
-  if (value === null) return nullLabel ?? '?';
-  if (projectStart === null) return formatDuration(value, unit, nullLabel);
-  // Convert from `unit` to calendar days so a 3-week slack reads "21d"
-  // instead of "3w" when dates are showing.
-  const days = value * unitToDays(unit);
-  const rounded = Math.round(days * 100) / 100;
-  const display = rounded.toFixed(2).replace(/\.?0+$/, '');
-  return `${display}d`;
-}