fix(data): self-consistency corrections for 261 tablet/watch records

[Seungpyo1007]

Summary

A fresh self-consistency pass over data/tablet/ and data/watch/ (following #301) surfaced 261 records where the device's RAM size had been mixed into storage_options_gb. In each case the polluting value equals the record's own �ariant.memory.ram_gb (and the top-level
am_gb) and is strictly smaller than every real storage tier in the same list — tiers that are independently confirmed by the record's own �ariant.memory.storage_gb. A 1-2 GB entry cannot be a storage capacity for these devices, so it is the RAM size leaking into the storage list.

Every correction is derived solely from fields already present in the same record — no external sources, no invented values. Ambiguous cases (e.g. records carrying two RAM tiers in the list, or where the low value could plausibly be a real storage size) were left untouched.

• 259 tablet records + 2 watch records
• Each change is a single-line removal (0 additions / 1 deletion) of the RAM value from \storage_options_gb\

Example

\iconia-tab-a100:
am_gb\ = 1, \�ariant.memory\ = { ram_gb: 1, storage_gb: 16 }, but \storage_options_gb\ was [1, 16]. The \1\ is the RAM size, not a storage tier → [16].

Tested

• \python -m app.validate\ → passed
• \integrity_check.py --strict\ (TechEngine, against this worktree) → exit 0, no hard anomalies, structural section clean, no tablet/watch flags
• Mandatory dump refresh (\python -m app.dump, fresh scratch DB, \TECHAPI_DATA_DIR\ → this worktree) committed last; scoped to the 261 tablet/watch detail files that map 1:1 to the data edits (pre-existing unrelated dump drift excluded).

Closes #296