[milestone Milestone 5 ] Horizontal scaling for trace ingestion — partition AEP records by `user_id`/`s...

[telleroutlook]

🤖 Auto-filed from milestone doc bullet.

Repo: WasmAgent/trace-pipeline
Milestone: Milestone 5 — Production Trace Pipeline at Scale
Bullet:

Horizontal scaling for trace ingestion — partition AEP records by user_id/subject_id shards, implement concurrent validation workers, and add backpressure-aware queueing (Redis/RabbitMQ) to handle burst traffic from multiple agent instances.

Relevant code context (from worktree)

new (does not exist yet): user_id`/`subject_id
new (does not exist yet): Redis/RabbitMQ
contains 'trace': scripts/export-schemas.py
contains 'trace': scripts/train_dpo.py
contains 'trace': scripts/train_sft.py

Implementation note: Files marked "new (does not exist yet)" must be created from scratch. verify-first should return PROCEED (not NOT_YET) — there is no prerequisite blocking this work.

Acceptance criteria

• Command pip install -e . && python -m pytest passes
• The specific work described in the bullet above is implemented in the smallest number of files required.
• No unrelated files touched (git status --short output limited to the intended change).

Notes for the implementer

This issue was auto-created by SweepMilestoneBulletToIssue. The bullet text is verbatim
from the milestone doc. If ambiguous or too large for a single implement cycle,
verify-first should return NEEDS_SPLIT with sub-issue proposals or NEEDS_HUMAN with the blocker.

---

Filed automatically.

[telleroutlook]

Verify-first found this issue is already implemented at evomerge/ingestion_scaling.py:1. Closing without spawning implementation work.