[Hackathon] fix(project): validate non-empty and non-whitespace <project-id> across project env commands #385

Verified against (commit SHA or released version)

commit 988c0355bb05631e9c6c1785e443937ff2a88c0e — @testsprite/testsprite-cli 0.14.0

Discord Username / User ID

@npall_805

What does this improvement do?

The project env command group (project env list, project env get, project env create, project env update, project env delete, and project env set-default) accepts a positional <project-id> argument but does not validate that it is non-empty and non-whitespace before proceeding.

When a positional <project-id> argument is empty or whitespace (e.g. testsprite project env list "$PROJECT_ID" or testsprite project env get " " prod when an environment variable is unset or whitespace):

1. Under --dry-run: The CLI immediately prints canned synthetic responses (e.g. sampleEnv, deleted: prod, etc.) and exits 0, providing a false-success indicator on an invalid project identifier.
2. In live mode: The unvalidated empty/whitespace argument is directly interpolated into the REST path (e.g. /projects/%20%20%20/env or /projects//env), sending malformed requests to the backend API rather than failing fast locally with a typed VALIDATION_ERROR (exit 5).

In contrast, sibling commands such as project delete explicitly validate <project-id> up front and throw VALIDATION_ERROR (<project-id> is required and must not be empty or whitespace-only, exit 5).

Details / implementation notes

Proposed Solution:

1. Add requireProjectId(raw: string | undefined): string in src/commands/project-env.ts throwing typed localValidationError('<project-id> is required and must not be empty or whitespace-only', '<project-id>') (exit 5, VALIDATION_ERROR).
2. Call requireProjectId up front in:
   • runEnvList
   • runEnvGet
   • runEnvCreate
   • runEnvUpdate
   • runEnvDelete
   • runEnvSetDefault
3. Add unit test suite in src/commands/project-env.spec.ts asserting that empty and whitespace project IDs consistently reject with code 5 (VALIDATION_ERROR) across all 6 commands in both live and --dry-run modes.

Branch is ready with all tests and formatting verified.

Confirmations

• I have searched existing issues and this is not a duplicate.
• I have provided my Discord identity above for reward coordination.