profile: no create command; unknown --profile fails as Session not found

[ankitranjan7]

Summary

webcmd profile is list / rename / use. There is no create. Agents guess profile create, get "Did you mean rename?", then pass a new --profile <name> into session create / browser run and get Session not found — not "profile does not exist."

Isolation scored 2.0/5 because the agent fell through onto the already-connected __audit_nope__ profile and wrote both customers there.

What the eval actually did (v0.7.4, profile-separation)

The task asked for two named identities (personal-run-…, work-run-…).

1. webcmd profile create personal-run-… → unknown command / Did you mean rename?
2. webcmd --profile personal-run-… session create then browser run → Session not found; IDs never appeared in session list
3. webcmd profile use personal-run-… → ARGUMENT; valid names were yesterday's leftover aliases plus default / work / __audit_nope__
4. Wrote both customers' portalPreference into __audit_nope__ sessions, then closed pre-existing sessions they did not create
5. Eventually isolated default vs work — not the requested names — and still failed tenant-clean

profile list -f json now works (#338). That did not give the agent a way to make a profile.

Why they did that

Profiles are cookie jars. The skill says so. The noun profile plus session create teaches "create a profile, then a session." The CLI can only rename an existing Cloak context to an alias. Nothing in --help says that. The failure mode for a never-created profile is the session error, so the agent concludes sessions are broken and starts closing whatever session list shows — including other tasks' sessions.

Fix

1. webcmd profile create <alias> — provision a Cloak context and assign the alias. Idempotent if the alias already exists.
2. webcmd --profile <unknown> session create must fail with PROFILE_NOT_FOUND and enumerate profile list plus profile create <name>, not Session not found.
3. profile --help should list create next to list / rename / use.

Check

webcmd profile create eval-a
webcmd --profile eval-a session create   # succeeds
webcmd --profile does-not-exist session create
# PROFILE_NOT_FOUND, names profile create / profile list

[ankitranjan7]

Implemented in #381

• webcmd profile create <alias> provisions a Cloak alias (idempotent).
• webcmd --profile <unknown> session create fails with PROFILE_NOT_FOUND and names profile create / profile list.

Tests: src/browser/profile.test.ts, src/cli.test.ts (creates a session under a newly created profile, rejects an unknown --profile on session create with PROFILE_NOT_FOUND).

[beubax]

This is a good addition. Make sure that the agent knows about this via the skills too.