Skip to content

monitor: backfill tick-history warnings corpus to closed vocabulary (571 spellings → ~17 conditions) #3922

Description

@tomerweller

Follow-up from #3791 plan (deferred scope item 6a).

#3791 canonicalizes the per-tick artifact writers and enforces a closed warnings/actions vocabulary on append. It deliberately does NOT touch the ~3,000-row historical tick-history.jsonl runtime corpus under ~/data/$MONITOR_SESSION_ID/.

Per amendment 2 (comment on #3791): ~1,043 warning-carrying rows hold 571 distinct spellings (81.8% hapax) for ~17 real conditions, and amendment 2 §2 proved the writer fix alone leaves these historical rows unaggregatable. This issue covers the one-time migration.

Scope

  • Build the 571→17 lookup table (hand-mapped once; amendment 2 §6.5 notes it is small enough to do by hand).
  • One-time migration script (operates on ~/data runtime files, not repo state) that rewrites or sidecars historical rows to the canonical schema + closed vocabulary, promoting embedded measurements (low-disk 90%) to typed fields.
  • Decide rewrite-in-place vs. .normalized.jsonl sidecar.

Why separate from #3791

Operational data migration of ~/data runtime files, not repo code a unit test can cover. Separable and non-blocking for the writer fix.

Parent: #3791.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions