Anomalyzer v0.3.0

Anomalyzer 0.3.0 — distinct events at the same original time

Schema 1.1 adds the optional event-identity-v1 contract for comparable event-index
measurements. DatasetV11.event_ids retain distinct same-time calls without
jitter, aggregation or lost values. Repeated logical IDs are rejected, including
identical retry deliveries; callers own trustworthy identity and upstream deduplication.

• Default data_policy.event_order="timestamp" sorts time/ID for layout only.
  Whole timestamp cohorts finish training/calibration before a later timestamp
  uses the reference. Tied observations keep point and explicit range evidence,
  break change comparisons, and cannot create sequence-pattern continuity.
• Optional event_order="trusted_sequence" requires aligned unique integer
  event_sequence ordinals consistent with nondecreasing original times. This
  is a caller assertion of order, not independence, causation or elapsed cadence.
• SampleRevision.event_id addresses a correction to one existing event at its
  original time. Availability/as-of selection is deterministic. Case and evidence
  IDs use logical identity; relevant changes create a new case revision. Cases,
  point episodes and rule findings can overlap and are not alert counts.
• Assessments/cases expose event_id; quality samples preserve original time,
  original input index, initial value and selected revision provenance. MCP
  get_evidence.source_samples makes distinct same-time calls inspectable.
• Exact identified relationships require matching logical identities and order
  contracts. Lineage exposes source event IDs and original timestamp strings.
  Unordered tied events cannot feed a lagged relationship.
• README chapters 23–24 continue the existing numbered progression with six
  reproducible fixtures and two rendered charts. Source tests cover schemas,
  Python, CLI, MCP, prefix/as-of/corrections and bounded result growth. Installed
  artifact checks and the offline Linux x86_64/Python 3.12 consumer exercise IDs.
• The standalone Linux benchmark includes 1,344 distinct calls with four per
  timestamp. Its result sizes and warm timings are mechanics checks, not measured
  production capacity, accuracy, memory consumption or cold-start cost.
• Release staging retries reads after draft creation to tolerate GitHub's draft
  index delay without creating or overwriting another release.

Calendar grids and legacy unique-time event inputs keep their existing numerical
semantics; schema 1.0 remains unchanged. Upgrade strict schema-1.1 readers/producers
together for the added fields. The package remains alpha, supports Python 3.11–3.13,
and is distributed as an immutable GitHub wheel/sdist with hash-pinned dependencies.

Limits: the engine cannot authenticate event IDs/order, detect aliases, maintain
a durable retry/arrival ledger, infer independence, or finalize an open same-time
cohort. Adding a newly available member/correction can revise later references;
explicit availability preserves earlier as-of snapshots. Event-index calendar
aggregation, multi-seasonality and business incident/notification policy remain
outside this contract. This release does not change or deploy UsageTap Guard.

See docs/sparse-data.md, README chapters 23–24 and docs/releases/README.md for
the exact API, replay boundaries, examples and Linux build-time installation.

Anomalyzer 0.3.0 — local Python analysis library.

Source revision: ea6e0dd157d8fc59c35382f1711240a15b8a9acd.

Wheel and source distribution tested on Python 3.11–3.13; Linux/Python 3.12 Lambda consumer verified offline. See SHA256SUMS and release-manifest.json for artifact identities.

Release and consumption guide.