Lead project scoping with name-based workflow; ID header is the direct-API detail

Per review: don't steer users to hunt for and paste an opaque project ID.
Scope by name via the CLI --project flag or an SDK client (both resolve the
name to the ID); the raw X-Kernel-Project-Id header (ID-only) is documented as
the underlying mechanism for direct REST callers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: IlyaasK

info/projects.mdx

@@ -25,7 +25,7 @@ A project must also be empty before it can be deleted — archive or remove its
 
 ## Scoping Requests to a Project
 
-Pass the `X-Kernel-Project-Id` header — a project ID — on any API request to scope it to a specific project. The header takes the project's ID, not its name; the CLI's `--project` flag and the SDKs resolve names to IDs for you. Without the header (and without a project-scoped API key), requests act on your organization's **default project**: reads return the default project's resources, and writes create resources in it.
+Scope a request to a project **by name** with the CLI's `--project <name>` flag or by setting the project on an SDK client — both look the name up and send the project's ID for you, so you never handle the raw ID. When calling the REST API directly, send that ID yourself in the `X-Kernel-Project-Id` header (the header takes a project ID, not a name). Without it (and without a project-scoped API key), requests act on your organization's **default project**: reads return the default project's resources, and writes create resources in it.
 
 ```bash
 curl https://api.onkernel.com/browsers \