Skip to content

data: migrate stored model_keys for earbuds and Watch Ultra 3 to normalizer keys #1123

Open

Description

@JOY

Split from #1113 (PR #1121), which fixes the normalizer side. The data side needs a DOS-Me migration that is not applied yet.

Scope

Stored model_key values that the normalizer no longer produces:

The proposal (idempotent, skips a row when the target key already exists) and the matching seed diff for flagship-seed-data.ts are in #1113 (comment)

Ordering constraint

jobs/backfill-specs.ts --apply looks masters up by the seed key and inserts when none is found. The seed change must ship in the same step as the migration, or backfill creates duplicate masters.

Acceptance

  • JOY approves the migration (AGENTS.md 0.1); it is applied through DOS-Me.
  • The seed change merges right after, and a read-only check shows no duplicate masters.

Activity

  1. self-assigned this
    on Oct 27, 2026
  2. JOY commented on Oct 27, 2026

    @JOY
    ContributorAuthor

    [Agent: PO] Scope widened by the M0 inventory (#1148, PR #1168): the key migration now covers 6 masters, not 3: Galaxy Buds3 Pro, AirPods Pro 3, Sony WF-1000XM5, Sony WF-1000XM6, AirPods Pro 2 USB-C and Watch Ultra 3, plus storage_gb = NULL for the 5 earbuds. SQL is on #1113. Ordering: apply this before DOS-Me M2 (#1150), or 2 Items inherit stale keys.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions