feat: add repo automation workflows

docs/configuration.md

@@ -198,6 +198,15 @@ list_ttl_secs = 60
 default_context_window = 8192
 ```
 
+## Repository Automation (GitHub)
+
+The `owlen repo` CLI commands and the matching `:repo` TUI shortcuts can fetch pull requests directly from GitHub. Authentication is driven primarily through environment variables:
+
+- Set `GITHUB_TOKEN` to a personal access token with at least `repo:read` scope. The CLI reads this variable automatically; override it with `--token` or pick a different environment variable with `--token-env NAME`.
+- GitHub Enterprise instances are supported via the `--api-endpoint` flag (for example, `https://github.my-company.com/api/v3`). The same flag is respected when you run `owlen repo review` or when the TUI invokes the automation helpers.
+
+When no token is available, the commands fall back to analysing local diffs only.
+
 Key points to keep in mind:
 
 -   **Base URL normalisation** – Owlen accepts `https://ollama.com`, `https://ollama.com/api`, `https://ollama.com/v1`, and the legacy `https://api.ollama.com`, canonicalising them to the correct HTTPS host. Local deployments get the same treatment for `http://localhost:11434`, `/api`, or `/v1`. You only need to customise `base_url` when the service is proxied elsewhere.

docs/troubleshooting.md

@@ -126,6 +126,12 @@ ollama list
 
 This workaround mirrors what `ollama signin` should do—register the key pair with Ollama Cloud—without waiting for the patched release. Once you upgrade to v0.12.4 or newer, the interactive sign-in command works again.
 
+## Repository Automation Issues
+
+- **401 / authentication errors**: `owlen repo review` needs a GitHub token. Export `GITHUB_TOKEN=<personal access token>` (with at least `repo:read`) before running the command or use `--token <value>`. In the TUI, the same environment variable is read when `:repo review` is executed.
+- **404 responses**: Verify that the `--owner` and `--repo` flags match the full name of the repository (`owner/repo`). A 404 from GitHub for private projects usually means the token lacks access.
+- **Enterprise endpoints**: Supply `--api-endpoint https://github.example.com/api/v3` so the client uses your self-hosted instance instead of `api.github.com`.
+
 ## Performance Tuning
 
 If you are experiencing performance issues, you can try the following: