Question: sanctioned validation path for custom ContextContract agent

Request: sanctioned validation path for ContextContract agent

I am testing a local ContextContract controller with STATE-Bench.

Current status:

• A custom BaseAgent loads in the public checkout.
• A direct no-score run_task() smoke works on two shopping tasks.
• I am not claiming an official score or external validation.
• The official CLI path is blocked locally by STATE_BENCH_EVAL_ENDPOINT.

Question:

What is the clean sanctioned path from adapter compatibility to valid STATE-Bench evidence?

Useful answers would be:

1. how to access/configure the locked eval endpoint,
2. whether a deterministic no-score smoke can count as nonofficial adapter evidence,
3. whether this belongs in Main Track or Agent Learning Track.

I want to avoid private simulator hacks or protocol-unsafe claims.

Start with the public BaseAgent adapter and the official CLI path, then trace where STATE_BENCH_EVAL_ENDPOINT is required. Review the existing no-score run_task smoke and the benchmark track definitions. Done means documenting the sanctioned endpoint configuration, the status of nonofficial smoke evidence, and the appropriate track.