Deploy Hub configurations from the CLI (#2955)

* feat(cli): add Hub configuration deploy

Deploy configuration bytes directly to an explicitly targeted Hub project using only caller-supplied origin and organization API key authority.

* refactor(cli): name Hub deploy contracts

* docs(hub): complete deploy CLI guidance

* docs(hub): link deployed API references

* feat(cli): bundle referenced Hub partials

Send exact referenced prompt-partial content alongside YAML so Hub can resolve local includes while inline-only configurations keep the existing request shape.

* fix(cli): match Hub YAML size semantics

Apply the finalized Hub request limit to decoded YAML length and cover multibyte configuration payloads without changing the wire body.

public-docs/hub/quickstart.md

@@ -39,6 +39,8 @@ Open **Projects → New project**. On its **Configuration** tab, pick a reposito
 Add `.paseo/hub.yml` to that repository:
 
 ```yaml
+project: your-project
+
 environments:
   - name: dev
     kind: daemon
@@ -67,7 +69,9 @@ triggers:
               ${{ paseo.prompt }}
 ```
 
-`daemon` is the normalized slug from step 3. `cwd` is a directory on that machine.
+`project` is the project slug from step 4. The deploy CLI reads it as deployment metadata; it does not affect workflow behavior. `daemon` is the normalized slug from step 3. `cwd` is a directory on that machine.
+
+If a prompt uses an `include` block, store the file below `.paseo/partials/`. The deploy CLI bundles only the files referenced by `.paseo/hub.yml`; nested include-looking text inside a partial is not resolved.
 
 ## 6. Push
 
@@ -75,6 +79,16 @@ Push to the default branch. Hub fetches the file at that commit, validates it, a
 
 If the file is invalid, Hub records the failure and keeps the previous revision active.
 
+To deploy the file directly instead, create an organization API key with the `configuration:install` scope, then run:
+
+```sh
+export PASEO_HUB_URL=https://your-hub.example.com
+export PASEO_HUB_API_KEY=paseo_pk_...
+paseo hub deploy
+```
+
+The command reads exactly `.paseo/hub.yml` from the current directory. It does not search parent directories. Use `paseo hub deploy path/to/config.yml` for another file. `-p, --project <slug>` overrides the file's `project` metadata. See [Hub configuration](/docs/hub/configuration#deploy-from-the-cli) for every deploy option and the current authentication limits.
+
 ## 7. Trigger it
 
 Comment `@paseo have a look at this` on an issue in that repository, from the account you listed in `from_users`.