Add Hermes Agent on Fly.io guide to blueprints

[theoctopusperson]

Guide for spinning up Hermes. More "guidey" this time, not just an install script.

[kcmartin]

[experimental] is documented as a holding area for settings not yet promoted into the main config. The promoted equivalent is [processes], which other sections ([[mounts]], [[vm]], [[services]]) reference by group name — so this leaves room for a reader to add a worker or per-group [[vm]] later without rewriting.

Expected to be a pure syntactic swap (the image has ENTRYPOINT [..., "entrypoint.sh"] and no CMD, and the canonical [processes] example shell-splits its string into argv), but I haven't deployed both side-by-side. Worth a quick fly machines list --json | jq '.[].config.init' to confirm before merging.

Suggested change

	[experimental]
	cmd = ["gateway", "run"]
	[processes]
	app = "gateway run"

[kcmartin]

Style: prefer the short -a form over --app for app-name flags

fly proxy --app … and friends appear ~30 times in this guide, all in the long form. The sibling guide https://github.com/superfly/docs/blob/main/blueprints/deploy-openclaw.html.md uses -a <name> throughout (e.g. fly logs -a your-app-name, fly ssh console -a your-app-name), and most other blueprints follow that convention (it keeps the snippets and the command table from feeling crowded).

A single repo-side find-and-replace of --app <your-hermes-app> → -a <your-hermes-app> should cover all instances. Worth doing in one pass.

Suggested change

	| `fly logs --app <your-hermes-app>` | Stream live logs |
	| `fly logs -a <your-hermes-app>` | Stream live logs |