Create or update a Jira project without key clashes

**Objective:** Create the Jira project `{project-name}` with key `{project-key}`, or update it if it already exists, setting its lead to `{lead}` and its description to `{description}`.

**Step 1: Does it already exist**

Call `jira-get-project` with project-key set to {project-key}, then again with name.contains set to {project-name}. This decides which branch you take, and a create with a key that is already in use will fail.

**Step 2: Resolve the lead**

If {lead} was given, call `jira-get-user` with name.contains set to it, or email if it looks like an address, and take user-account-id. If several match, list them and stop. If none match, stop rather than creating the project with no lead.

**Step 3: Confirm the branch and the values**

State plainly whether you are creating or updating, and show the name, key, project type, lead and description. Ask for confirmation. Do not proceed without it.

**Step 4a: Create**

If Step 1 found nothing, call `jira-add-project` ONCE with name, key, project-type set to {project-type} (default software), description, and lead-account-id where resolved. Do not pass category-id, no tool on this server returns a category id.

**Step 4b: Update**

If Step 1 found an existing project, call `jira-update-project` ONCE with id set to its project-id, and only the fields that are actually changing. Do not resend a field that already holds the same value. The key and the project type cannot be changed this way.

**Step 5: Confirm**

Call `jira-get-project` with project-key set to {project-key} and report the stored name, key, lead, project-type and number-of-issues.

**Rules & Guidelines:**

* Exactly one write call, either `jira-add-project` or `jira-update-project`, never both, and only after the Step 3 confirmation.
* Do NOT create issues in the new project as a side effect. `jira-add-issue` is out of scope here.
* If the key exists but the name differs, stop and ask which one is correct rather than renaming someone else's project.

**Validation:**

* A project key must be short and uppercase. If {project-key} does not look like one, ask for it again and stop.
* If {project-type} is supplied and is not a type Jira accepts, such as software or business, ask for it again and stop.