Update README to reflect current project state

- Fix authToken naming (was accessToken)
- Update routing docs to path-based routes
- Replace generic deployment options with Clever Cloud + CI
- Add testing section
- Fix GraphQL URL and webhook payload URL

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: hubyrod

README.md

@@ -46,36 +46,33 @@ const config: SkiphooksConfig = {
   },
   slashwork: {
     graphqlUrl: process.env.SLASHWORK_GRAPHQL_URL!,
-    accessToken: process.env.SLASHWORK_ACCESS_TOKEN!,
+    authToken: process.env.SLASHWORK_AUTH_TOKEN!,
   },
   routes: {
-    pull_request: { groupId: "group-abc-123" },
-    issues:       { groupId: "group-abc-123" },
-    push:         { groupId: "group-def-456" },
-    release:      { groupId: "group-ghi-789" },
+    "my-project": { groupId: "group-abc-123" },
+    "releases":   { groupId: "group-def-456" },
   },
 };
 
 export default config;
 ```
 
 - **Secrets** stay in `.env` and are referenced via `process.env`.
-- **Routes** map each GitHub event type to a Slashwork group. Only configure the events you want — unconfigured events are silently ignored.
+- **Routes** are path-based — each route name becomes a `/github/<name>` endpoint. Only configured routes are active — requests to unknown routes return 404.
 
 ## Slashwork Configuration
 
 See the [Slashwork Developer docs](https://slashwork.com/developer) for full details.
 
 1. Create a **stream** (or use an existing one) where notifications will be posted.
-2. Create an **application** with a dedicated access token — this goes in `SLASHWORK_ACCESS_TOKEN`.
+2. Create an **application** with a dedicated auth token — this goes in `SLASHWORK_AUTH_TOKEN`.
 3. Find the **group ID** of your target stream(s) from their URLs — these go in `config.ts` routes.
-4. Set `SLASHWORK_GRAPHQL_URL` to `https://<your-instance>.slashwork.com/graphql`.
-5. You can test queries interactively at `https://<your-instance>.slashwork.com/graphiql`.
+4. Set `SLASHWORK_GRAPHQL_URL` to `https://<your-instance>.slashwork.com/api/graphql`.
 
 ## GitHub Webhook Setup
 
 1. Go to your repo (or org) **Settings → Webhooks → Add webhook**.
-2. **Payload URL:** `https://<your-server>/github-webhook`
+2. **Payload URL:** `https://<your-server>/github/<route-name>` (matching a route in `config.ts`)
 3. **Content type:** `application/json`
 4. **Secret:** Same value as your `GITHUB_WEBHOOK_SECRET` env var.
 5. **Events:** Select the events you want (Pull requests, Issues, Pushes, Releases).
@@ -94,28 +91,24 @@ bun run dev
 bun run start
 ```
 
-## Deployment
-
-### Railway
+## Testing
 
-Railway supports Bun natively. Push your repo, set the env vars in the dashboard, and set the start command to `bun src/index.ts`.
-
-### Render
+```sh
+bun test
+```
 
-Create a new Web Service with Bun runtime and configure the env vars in the dashboard.
+## Deployment
 
-### Fly.io
+Deployed to [Clever Cloud](https://clever-cloud.com) via GitHub Actions. Every push to `main` runs typecheck and tests, then deploys automatically on success.
 
-```sh
-fly launch
-fly secrets set SLASHWORK_GRAPHQL_URL=... SLASHWORK_ACCESS_TOKEN=... GITHUB_WEBHOOK_SECRET=...
-fly deploy
-```
+**Required GitHub secrets** (Settings > Secrets and variables > Actions):
+- `CLEVER_TOKEN`
+- `CLEVER_SECRET`
 
 ## Troubleshooting
 
 - **Signature mismatch (401):** Ensure `GITHUB_WEBHOOK_SECRET` matches exactly between GitHub and your `.env`. Check for trailing whitespace.
 - **Posts not appearing:** Verify group IDs in `config.ts` point to valid streams. Check server logs for GraphQL errors.
-- **Token issues:** Ensure `SLASHWORK_ACCESS_TOKEN` has write permissions to the target groups.
+- **Token issues:** Ensure `SLASHWORK_AUTH_TOKEN` has write permissions to the target groups.
 - **No events received:** Confirm the webhook is active in GitHub (Settings → Webhooks) and the desired events are selected.
-- **Event ignored:** Check that the event type has a route in `config.ts` and the action is one of the supported actions listed above.
+- **Event ignored:** Check that the route exists in `config.ts` and the action is one of the supported actions listed above.