arenalisted

# Arena Generate independent attempts at one artifact, select a coherent base, adapt compatible strengths, and verify the synthesis. ## Invocation and target Run only after direct explicit invocation or as a bounded phase delegated by another explicitly invoked workflow whose own instructions permit arena delegation and that owns the result. Manual-only metadata does not authorize automatic use for every non-trivial task. Require one concrete artifact, its intended consumer, applicable constraints, and a shared output contract. An artifact may be a design, code change, test set, technical document, query, migration, or another bounded deliverable. Arena is not a way to divide a larger task into different work slices. A complete arena needs at least two completed candidates. One attempt may still be useful, but it is not an arena synthesis. ## Preserve access, privacy, and repository state Keep evidence local by default. Do not send project content to remote sources, new providers, or running environments unless the user requested it and the established privacy boundary permits it. Give each candidate and judge only the minimum relevant context. Do not reproduce credentials, tokens, private keys, cookies, sensitive personal data, or unrelated proprietary content. Use redacted placeholders and report exposures. When a repository is involved: - record its initial state before commands that may generate files; - keep tracked files unchanged unless persistent artifact cr