data-ingestors HEAD has drifted from the CLI's pin (canary)

[github-actions]

Canary run: https://github.com/tracebloc/cli/actions/runs/29723726647

pin (scripts/.data-ingestors-ref)	8f89aece1e0c249a28644eb6cdec47b7572bbec6
data-ingestors develop HEAD	4d606bcd82df065b422a703ec8010429b4f7992b
goldens check vs HEAD	in sync
pin reachable from HEAD	true

Mirrored validator source files changed between pin and HEAD (may include verdict-neutral changes with no corpus case yet — the di#365 class):

tracebloc_ingestor/database.py
tracebloc_ingestor/ingestors/base.py
tracebloc_ingestor/modalities/validators.py
tracebloc_ingestor/validators/label_constant_within_group_validator.py
tracebloc_ingestor/validators/mask_id_validator.py
tracebloc_ingestor/validators/per_group_time_ordered_validator.py
tracebloc_ingestor/validators/sequence_group_validator.py

Playbook (pin-bump doctrine, backend#1009 / cli#286 shape): bump scripts/.data-ingestors-ref to the new HEAD, run scripts/sync-schema.sh + scripts/sync-validator-goldens.sh, adopt/audit the intervening upstream changes in the internal/push mirror, and ship the regenerated goldens in the same PR.

Advisory only — this canary never blocks CI. Close this issue when the pin bump lands.

[LukasWodka]

Benign drift notice — goldens are in sync and the pin is reachable from HEAD. To stop the canary recurring, bump scripts/.data-ingestors-ref to the current data-ingestors develop HEAD (can open that PR separately).