docs: tighten the gt guides and the cli wiring

The workflow example had no trigger, so Gitea would reject it as written.
The guides now merge the small account sections and point users at the
nightly builds they describe. Comments and READMEs no longer mention the
dropped reference generator or list the runner as the only hand written
sidebar product, and the sidebar lookup drops a key the fallback covers.

Co-Authored-By: Claude (Opus 5.5) <[email protected]>

cli-docs/ci.md

@@ -21,8 +21,12 @@ Gitea does not allow secret names that start with `GITEA_`, so store the token a
 example, `GT_TOKEN`:
 
 ```yaml
+on:
+  push:
+    branches: [main]
+
 jobs:
-  deploy:
+  staging:
     runs-on: ubuntu-latest
     env:
       GITEA_TOKEN: ${{ secrets.GT_TOKEN }}
@@ -33,4 +37,4 @@ jobs:
       - run: gt workflow run deploy.yml --ref main --field env=staging --no-input
 ```
 
-`gt run watch` and `gt pr checks --watch` wait for runs and checks and fail when they do.
+`gt run watch` and `gt pr checks --watch` wait for runs and checks and fail when one fails.