fix(deployment): align evaluator metadata with v4

[proerror77]

Closes #410

Change contract

Align the Aliyun continuous CEX research Job annotations and operator verification text with purged-walk-forward-v4.

Out of scope

• Alpha-harness evaluator or research logic.
• Polymarket behavior.
• Collector deployment or live runtime cutover.

Dependency / merge order

• Depends on CEX: evaluate an admitted Binance replay with purged post-cost walk-forward #401 / PR CEX: evaluate admitted replay with post-cost walk-forward #409, merged at 6875725.
• Merge after CEX: evaluate admitted replay with post-cost walk-forward #409. No stacked PR dependency remains.

Focused validation

• No purged-walk-forward-v3 reference remains under deployment/aliyun/research.
• Exactly two Job annotations and one README verification reference report purged-walk-forward-v4.
• The changed Job example parses as YAML.
• git diff --check passes.
• Standards review: clean.
• Specification review: clean.
• Production Image And Kubernetes Contract: pending PR CI.

Rollout / rollback impact

Documentation and example metadata only; no live deployment mutation. Revert this PR if the v4 evaluator contract is rolled back.

[coderabbitai]

Warning

Review limit reached

@proerror77, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 15 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e888cb96-c333-4d9b-92fb-e7cb49420b24

📥 Commits

Reviewing files that changed from the base of the PR and between 6875725 and 48a3b18.

📒 Files selected for processing (2)

• deployment/aliyun/research/README.md
• deployment/aliyun/research/k8s/alpha-mission-job.example.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/cex-evaluator-metadata-v4-410

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}