desk-execution-protocollisted

# Execution protocol This is the only skill on the desk that ends with a signed write to Strike, and only the Execution Trader uses it. The endpoint mechanics live in `strike-orders`, `strike-positions` and `strike-advanced`; signing lives in `strike-auth`. This skill is the discipline around them. ## Inputs - The proposal file `/workspace/trading-desk/proposals/<id>.md` with a Risk Manager PASS and exact ticket fields. - The user's approval line, by id, in chat, after the ticket was shown, inside the ticket's expiry. - The desk computer configured per `strike-setup`: `STRIKE_API_PUBLIC_KEY` and `STRIKE_API_PRIVATE_KEY` available to `scripts/strike_request.py` from the secure secret store, never printed. ## Pre-send checklist Run every item and write the result under `## execution` before sending. Any failure: do not send, name the item, hand back to the Desk Lead. 1. **Ticket integrity.** Id, PASS and approval refer to the same ticket text. If the Desk Lead edited the ticket after the PASS, it goes back to Risk. 2. **Symbol.** The ticket's market, with `status: trading` in `/v2/exchangeInfo`. One symbol vocabulary across both surfaces, so nothing to translate - but a halted market is still a reject. 3. **Account.** `GET /v2/account` and `GET /v2/positions` read this minute. Equity matches what the Risk Manager sized against, within the ticket's tolerance. Nothing unexpected is already open. 4. **Price still valid.** A fresh `/v2/markPrice` read is within the ticket's s