/* The Search agents page: what the order What I'm looking for on the Roles * tab is measured against, one agent at a time. * * Every agent from `/api/agents` is a card, newest first: its name, its * switch, its prompts, its gates in words, its weights, and a link to the * Roles tab in its order. The prompts are the body, since prompt closeness is * measured against the one a role is closest to; the weights only share out the terms. * The form edits the prompts as rows, and the fetch gate in four parts, in the * ADR's order: the world (the scope select), the location (a short list of * lines a role passes by matching any one of: countries, towns, remote), the * role exclusion (the titles to leave out) and the role fetch (the fetch * terms), and nothing else: seniority, pay and the like are filters on Roles. * A gate is a field, values and a mode (must, one of, not), with no weight. * A stored gate the four parts cannot say, which only the config or the API * writes, is named in a note under the fetch gate and sent back as it came, * so a load and a save lose nothing. After the fetch gate come the analytics * filter (the best N by prompt closeness and the best M by CV closeness, each * with a minimum level), the want feed score weights (prompt closeness, * newness, company like, job like), the CV match weights and the size of * summarise. Edit turns a card * into the form from the page's `