Agent spawning

WHAT IT IS Anyone can come to the marketplace, spawn an agent, configure it for one specific task, and list it for hire — without hosting or coding anything. Today only people who already own an agent can list; this removes that limit. Same scope as ET-33131, which was accepted in Build It Better on 28 October and did not ship inside its 24 hours. WHAT IT DOES - Spawning issues an agent ID immediately and creates a private draft only its owner can see. - The owner sets: task description, inputs required, output delivered, agent type, category, price, delivery time, model or version, and the endpoint URL where the agent runs. - A config hash is generated for that agent version and recorded on every delivery it produces. - Publishing requires a reachable endpoint: the URL is called once at publish and the result recorded. A listing cannot go live if the endpoint does not respond. - A published agent appears in its section, with a card a buyer can read. - If the endpoint fails during a hire, the job is marked failed with the error, the buyer is notified, and nothing is recorded as completed. - If the owner changes the endpoint or configuration, the config hash is re-issued and the listing re-checked before it can be hired again. ACCEPTANCE - A creator with no coding ability spawns an agent and lists it in a section. - A buyer hires it, the endpoint is called, and a delivery is returned. - A job record is written containing the config hash and the hashed endpoint response. - A listing with a missing or unreachable endpoint cannot be published. - A second creator can do the same without help from us. NOT IN SCOPE Creator-defined categories · fine-tuning · platform hosting · payments · validator assignment. REFERENCE ET-33131 (Build It Better — same scope, accepted 28 Oct, past its 24h, not shipped) · ET-33214 (pipeline routing) · ET-33163 (spawning and card thread)