# React Scheduler — Agent Protocol

This project uses a vendor-neutral agent harness. **The protocol is not in this
file.** It lives at `.agent/instructions.md` so every agent tool follows identical
rules against identical gates.

## Do this now, before anything else

1. `read .agent/instructions.md` — the operating protocol
2. `read .agent/adapters/codestudio.md` — capability bindings for Code Studio
3. `read .agent/project-context.md` — stack, architecture, conventions, boundaries
4. `python .agent/tools/task.py status`
5. `python .agent/tools/harness.py doctor` — first session, and after every pull

## The rule you most need to know

You may narrate, but you may not assert. Any claim a tool can measure is decided
by that tool. `task.py done` refuses to complete a task without passing gate
evidence — that refusal is the harness working correctly.

Also read product-specific AI guidance in `.codestudio/codestudio-instructions.md`
(OpenSpec, Scheduler standards). Harness rules win on evidence and done criteria.

Tier L1 · profile js-react · overlay syncfusion · contract v1.0