[cvince]

Adds capy project create|delete|restore. Each one asks the human before it acts: in a terminal with a prompt, and for an agent with an elicitation the agent puts to the human.

What changes

New capy project command group. capy project create, capy project delete and capy project restore replace capy org delete-project and capy org restore-project, which never shipped in a release. capy projects still lists projects, and capy org projects --deleted still lists deleted ones. capy org now only switches organization.

capy project create [name] --branch <name> --protected yes|no (new).

• It creates the project and its first branch. In a terminal it asks for the name, the first branch ("What should its first branch be called?", with what a Capy branch is) and whether the branch is protected (yes/no, default no). Anything passed as a flag is not asked again.
• In agent mode it creates nothing until it has all three. It exits 3 with a form elicitation holding only the missing fields (PROJECT_NAME_REQUIRED, BRANCH_NAME_REQUIRED or BRANCH_PROTECTION_REQUIRED), and the rerun command to run with the answers.
• It refuses a name a live project already has, and it never suggests one. If the project is created but its branch is not, it exits with BRANCH_CREATE_FAILED and still returns the project.
• Owners and admins only. It does not link the current folder. --dry-run checks the values and creates nothing.

capy project delete <name-or-id>.

• Without --yes, an agent gets CONFIRMATION_REQUIRED (exit 3) with a confirm elicitation and changes nothing.
• The elicitation shows the org, the project, its branches, every variable name with its branches, and live deploy tokens. It carries names and ids only, never a value.
• --force deletes despite live deploy tokens.

capy project restore <name-or-id>. Asks the same way: a yes/no prompt in a terminal, or a confirm elicitation for an agent. --dry-run names the project that would come back and restores nothing.

A name shared by several projects. Delete and restore ask which one. A terminal shows an arrow list. An agent gets PROJECT_AMBIGUOUS (exit 3) with a pick-one elicitation, whose options are each project's name, variable count and creation time ("created 3 days ago", once the service returns created_at). A name that matches nothing is refused with PROJECT_NOT_FOUND, and nothing is sent.

Agent mode is --json, --non-tty, or no terminal. It applies to all three commands. The elicitation and code come back as JSON with --json; without it, the refusal is a message on stderr with the same exit code. In agent mode they never open a prompt, including the organization picker. With no organization in the folder and several to choose from, they exit 3 with ORG_SELECTION_REQUIRED.

Agent instructions (the AGENTS.md block and capy help --json):

• When a result carries an elicitation, put its display table in the reply, then ask with the agent's question tool, one question per field. Ask in chat only when there is no question tool.
• Never pass --yes on its own.
• To create or delete a project, run the command and let its elicitation ask.
• PROJECT_DELETED means stop and point the human at capy project restore <id>. This concerns the folder's own project only, never a delete or restore asked for by name.
• Before writing, check capy info --json. Stop on a browser sign-in. Look up a secret with capy secrets --json --name NAME.

capy agents writes both AGENTS.md and CLAUDE.md.

capy info --json reports project.state: live, deleted or unknown.

New codes:

• Create: PROJECT_NAME_REQUIRED, PROJECT_NAME_INVALID, PROJECT_NAME_EXISTS, BRANCH_NAME_REQUIRED, BRANCH_NAME_INVALID, BRANCH_PROTECTION_REQUIRED, BRANCH_PROTECTION_INVALID, BRANCH_CREATE_FAILED
• All three commands: ORG_SELECTION_REQUIRED

Checks

• Typecheck is clean, and the full suite passes (3,194 tests).
• In a test VM signed in to prod, fresh agent sessions had only the folder's AGENTS.md and CLAUDE.md, with no memory. In each run the agent ran the new command itself and let its elicitation ask, and it never tried --yes:
  • create: capy project create --json, and capy project create billing-api --branch staging --json, which then asked only the protected question
  • delete, with both the confirm and the pick-one elicitations
  • create again with the name of a deleted project
• In the same VM the delete and restore round trip ran against prod. A delete went through only after a human yes. capy info --json then reported state: "deleted", and bare capy refused with the restore command.

All new user-facing wording is marked COPY-FLAG for review.