docs(push): fix stale TargetSize NOTE — no swap, [width, height]

[saadqbal]

Comment-only fix. The TargetSize field NOTE in internal/push/spec.go still described the old #25/[H,W] behavior:

stored [W, H] here, but EMITTED as [height, width] by Build … buildImage does the swap.

That is wrong on both counts now. buildImage emits [TargetSize[0], TargetSize[1]] = [width, height] with no swap — the state #147 (landed via #149) deliberately reverted to. The stale NOTE contradicted the inline comment right next to the emit and risked a future reader "re-fixing" it back to [H,W], which is exactly what failed every non-square dataset in-cluster.

Ground truth (verified against tracebloc/data-ingestors):

• ingest.v1.json: target_size is [width, height], "matches PIL.Image.size and what ImageResolutionValidator expects".
• image_validator.py: img.size is (width, height); compares actual[0]↔expected[0] (width), actual[1]↔expected[1] (height).

Rewrote the NOTE to state stored-and-emitted [width, height], no swap, and warn against re-introducing the swap.

Rolls up under #145/#147 — no new kanban ticket.

---

Note

Low Risk
Comment-only change to field documentation; no executable code or emitted spec behavior is modified.

Overview
Updates the TargetSize field NOTE on SpecArgs in internal/push/spec.go so it matches current behavior and the ingest contract.

The old NOTE claimed values are stored as [W, H] but emitted as [height, width] with a swap in buildImage. That was outdated after #147: buildImage emits [width, height] with no dimension swap, aligned with ingest.v1 and ImageResolutionValidator (PIL img.size order). The revised NOTE documents stored-and-emitted [width, height], references the mistaken [H,W] swap from PR #22 that broke non-square datasets in-cluster, and warns against re-introducing a swap—consistent with the inline comment beside the emit in buildImage.

No runtime or spec-building logic changes—documentation only.

^{Reviewed by Cursor Bugbot for commit f26798a. Bugbot is set up for automated code reviews on this repo. Configure here.}