chat 4.18.0 → 4.20.0

package/docs/adapters/gchat.mdx

@@ -1,237 +0,0 @@
----
-title: Google Chat
-description: Configure the Google Chat adapter with service account authentication and optional Pub/Sub.
-type: integration
-prerequisites:
-  - /docs/getting-started
----
-
-## Installation
-
-```sh title="Terminal"
-pnpm add @chat-adapter/gchat
-```
-
-## Usage
-
-The adapter auto-detects credentials from `GOOGLE_CHAT_CREDENTIALS` or `GOOGLE_CHAT_USE_ADC` environment variables:
-
-```typescript title="lib/bot.ts" lineNumbers
-import { Chat } from "chat";
-import { createGoogleChatAdapter } from "@chat-adapter/gchat";
-
-const bot = new Chat({
-  userName: "mybot",
-  adapters: {
-    gchat: createGoogleChatAdapter(),
-  },
-});
-
-bot.onNewMention(async (thread, message) => {
-  await thread.post("Hello from Google Chat!");
-});
-```
-
-## Google Chat setup
-
-### 1. Create a GCP project
-
-1. Go to [console.cloud.google.com](https://console.cloud.google.com)
-2. Click the project dropdown then **New Project**
-3. Enter project name and click **Create**
-
-### 2. Enable required APIs
-
-Go to **APIs & Services** then **Library** and enable:
-
-- **Google Chat API**
-- **Google Workspace Events API** (for receiving all messages)
-- **Cloud Pub/Sub API** (for receiving all messages)
-
-### 3. Create a service account
-
-1. Go to **IAM & Admin** then **Service Accounts**
-2. Click **Create Service Account**
-3. Enter name and description
-4. Click **Create and Continue**
-5. Skip the optional steps, click **Done**
-
-### 4. Create service account key
-
-1. Click on your service account
-2. Go to **Keys** tab
-3. Click **Add Key** then **Create new key**
-4. Select **JSON** and click **Create**
-5. Copy the entire JSON content as `GOOGLE_CHAT_CREDENTIALS`
-
-<Callout type="info">
-If your organization has the `iam.disableServiceAccountKeyCreation` constraint enabled, you need to relax it or add an exception for your project in **IAM & Admin** then **Organization Policies**.
-</Callout>
-
-### 5. Configure Google Chat app
-
-1. Go to the [Chat API configuration](https://console.cloud.google.com/apis/api/chat.googleapis.com/hangouts-chat)
-2. Click **Configuration** and fill in:
-   - **App name**: Your bot's display name
-   - **Avatar URL**: URL to your bot's avatar
-   - **Description**: What your bot does
-   - **Interactive features**: Enable **Receive 1:1 messages** and **Join spaces and group conversations**
-   - **Connection settings**: Select **App URL**
-   - **App URL**: `https://your-domain.com/api/webhooks/gchat`
-   - **Visibility**: Choose who can discover your app
-3. Click **Save**
-
-### 6. Add bot to a space
-
-1. Open Google Chat
-2. Create or open a Space
-3. Click the space name then **Manage apps & integrations**
-4. Click **Add apps**, search for your app, and click **Add**
-
-## Pub/Sub for all messages (optional)
-
-By default, Google Chat only sends webhooks for @mentions. To receive all messages in a space, set up Workspace Events with Pub/Sub.
-
-```typescript title="lib/bot.ts" lineNumbers
-createGoogleChatAdapter({
-  pubsubTopic: process.env.GOOGLE_CHAT_PUBSUB_TOPIC,
-  impersonateUser: process.env.GOOGLE_CHAT_IMPERSONATE_USER,
-});
-```
-
-`GOOGLE_CHAT_PUBSUB_TOPIC` and `GOOGLE_CHAT_IMPERSONATE_USER` are also auto-detected from env vars, so you can omit them from config if the env vars are set.
-
-### 1. Create Pub/Sub topic
-
-1. Go to **Pub/Sub** then **Topics**
-2. Click **Create Topic**
-3. Enter topic ID (e.g., `chat-events`)
-4. Uncheck **Add a default subscription**
-5. Click **Create**
-6. Copy the full topic name as `GOOGLE_CHAT_PUBSUB_TOPIC` (format: `projects/your-project-id/topics/chat-events`)
-
-### 2. Grant Chat service account access
-
-1. Go to your Pub/Sub topic
-2. Click **Permissions** tab
-3. Click **Add Principal**
-4. Enter `chat-api-push@system.gserviceaccount.com`
-5. Select role **Pub/Sub Publisher**
-6. Click **Save**
-
-### 3. Create push subscription
-
-1. Go to **Pub/Sub** then **Subscriptions**
-2. Click **Create Subscription**
-3. Select your topic
-4. Set **Delivery type** to Push
-5. Set **Endpoint URL** to `https://your-domain.com/api/webhooks/gchat`
-6. Click **Create**
-
-### 4. Enable domain-wide delegation
-
-Domain-wide delegation is required for creating Workspace Events subscriptions and initiating DMs.
-
-**Step 1 — Enable delegation on the service account:**
-
-1. Go to **IAM & Admin** then **Service Accounts**
-2. Click on your service account
-3. Check **Enable Google Workspace Domain-wide Delegation** and save
-4. Copy the **Client ID** (a numeric ID, not the email)
-
-**Step 2 — Authorize in Google Admin Console:**
-
-1. Go to [Google Admin Console](https://admin.google.com)
-2. Go to **Security** then **Access and data control** then **API controls**
-3. Click **Manage Domain Wide Delegation** then **Add new**
-4. Enter the numeric **Client ID** from Step 1
-5. Add OAuth scopes (comma-separated, on one line):
-   ```
-   https://www.googleapis.com/auth/chat.spaces.readonly,https://www.googleapis.com/auth/chat.messages.readonly,https://www.googleapis.com/auth/chat.spaces,https://www.googleapis.com/auth/chat.spaces.create
-   ```
-6. Click **Authorize**
-
-**Step 3 — Set environment variable:**
-
-Set `GOOGLE_CHAT_IMPERSONATE_USER` to an admin user email in your domain (e.g., `admin@yourdomain.com`).
-
-## Configuration
-
-All options are auto-detected from environment variables when not provided.
-
-| Option | Required | Description |
-|--------|----------|-------------|
-| `credentials` | No* | Service account credentials JSON. Auto-detected from `GOOGLE_CHAT_CREDENTIALS` |
-| `useApplicationDefaultCredentials` | No | Use Application Default Credentials. Auto-detected from `GOOGLE_CHAT_USE_ADC` |
-| `pubsubTopic` | No | Pub/Sub topic for Workspace Events. Auto-detected from `GOOGLE_CHAT_PUBSUB_TOPIC` |
-| `impersonateUser` | No | User email for domain-wide delegation. Auto-detected from `GOOGLE_CHAT_IMPERSONATE_USER` |
-| `auth` | No | Custom auth object (advanced) |
-| `logger` | No | Logger instance (defaults to `ConsoleLogger("info")`) |
-
-*Either `credentials`, `GOOGLE_CHAT_CREDENTIALS` env var, `useApplicationDefaultCredentials`, or `GOOGLE_CHAT_USE_ADC=true` is required.
-
-## Environment variables
-
-```bash title=".env.local"
-GOOGLE_CHAT_CREDENTIALS={"type":"service_account",...}
-
-# Optional: for receiving all messages
-GOOGLE_CHAT_PUBSUB_TOPIC=projects/your-project/topics/chat-events
-GOOGLE_CHAT_IMPERSONATE_USER=admin@yourdomain.com
-```
-
-## Features
-
-| Feature | Supported |
-|---------|-----------|
-| Mentions | Yes |
-| Reactions (add/remove) | Yes (via Workspace Events) |
-| Cards (Google Chat Cards) | Yes |
-| Modals | No |
-| Streaming | Post+Edit fallback |
-| DMs | Yes (requires delegation) |
-| Ephemeral messages | Yes (native) |
-| File uploads | Yes |
-| Typing indicator | No |
-| Message history | Yes |
-
-## Limitations
-
-- **Typing indicators**: Not supported by Google Chat API. `startTyping()` is a no-op.
-- **Adding reactions**: The Google Chat API doesn't support service account (app) authentication for adding reactions. To use `addReaction()` or `removeReaction()`, you need domain-wide delegation with `impersonateUser` configured — but the reaction appears as coming from the impersonated user, not the bot.
-
-### Message history (`fetchMessages`)
-
-Fetching message history requires domain-wide delegation with the `impersonateUser` config option set. The impersonated user must have access to the spaces you want to read from. See the [Pub/Sub setup](#4-enable-domain-wide-delegation) above for configuring delegation and OAuth scopes.
-
-## Troubleshooting
-
-### No webhook received
-
-- Verify the App URL is correct in Google Chat configuration
-- Check that the Chat API is enabled
-- Ensure the service account has the necessary permissions
-
-### Pub/Sub not working
-
-- Verify `chat-api-push@system.gserviceaccount.com` has Pub/Sub Publisher role
-- Check that the push subscription URL is correct
-- Verify domain-wide delegation is configured with correct scopes
-- Check `GOOGLE_CHAT_IMPERSONATE_USER` is a valid admin email
-
-### "Permission denied" for Workspace Events
-
-- Ensure domain-wide delegation is configured
-- Verify the OAuth scopes are exactly as specified
-- Check that the impersonated user has access to the spaces
-
-### "Insufficient Permission" for DMs
-
-- DMs require domain-wide delegation with `chat.spaces` and `chat.spaces.create` scopes
-- Scope changes can take up to 24 hours to propagate
-
-### Button clicks not received
-
-- Verify **Interactive features** is enabled in the Google Chat app configuration
-- Check that the App URL is correctly set and accessible
-- Button clicks go to the same webhook URL as messages

package/docs/adapters/github.mdx

@@ -1,222 +0,0 @@
----
-title: GitHub
-description: Configure the GitHub adapter to respond to @mentions in PR and issue comment threads.
-type: integration
-prerequisites:
-  - /docs/getting-started
----
-
-The GitHub adapter treats issue and pull request comments as messages, and issues/PRs as threads.
-
-## Installation
-
-```sh title="Terminal"
-pnpm add @chat-adapter/github
-```
-
-## Usage
-
-The adapter auto-detects credentials from `GITHUB_TOKEN` (or `GITHUB_APP_ID`/`GITHUB_PRIVATE_KEY`), `GITHUB_WEBHOOK_SECRET`, and `GITHUB_BOT_USERNAME` environment variables:
-
-```typescript title="lib/bot.ts" lineNumbers
-import { Chat } from "chat";
-import { createGitHubAdapter } from "@chat-adapter/github";
-
-const bot = new Chat({
-  userName: "my-bot",
-  adapters: {
-    github: createGitHubAdapter(),
-  },
-});
-
-bot.onNewMention(async (thread, message) => {
-  await thread.post("Hello from GitHub!");
-});
-```
-
-## Authentication
-
-### Option A: Personal Access Token
-
-Best for personal projects, testing, or single-repo bots.
-
-1. Go to [Settings > Developer settings > Personal access tokens](https://github.com/settings/tokens)
-2. Create a new token with `repo` scope
-3. Set `GITHUB_TOKEN` environment variable
-
-```typescript title="lib/bot.ts" lineNumbers
-createGitHubAdapter({
-  token: process.env.GITHUB_TOKEN!,
-});
-```
-
-### Option B: GitHub App (recommended)
-
-Better rate limits, security, and supports multiple installations.
-
-**1. Create the app:**
-
-1. Go to [Settings > Developer settings > GitHub Apps > New GitHub App](https://github.com/settings/apps/new)
-2. Set **Webhook URL** to `https://your-domain.com/api/webhooks/github`
-3. Generate and set a **Webhook secret**
-4. Set permissions:
-   - Repository > Issues: Read & write
-   - Repository > Pull requests: Read & write
-   - Repository > Metadata: Read-only
-5. Subscribe to events: Issue comment, Pull request review comment
-6. Click **Create GitHub App**
-7. Note the **App ID** and click **Generate a private key**
-
-**2. Install the app:**
-
-1. Go to your app's settings then **Install App**
-2. Click **Install** and choose repositories
-3. Note the **Installation ID** from the URL:
-   ```
-   https://github.com/settings/installations/12345678
-                                              ^^^^^^^^
-   ```
-
-**Single-tenant:**
-
-```typescript title="lib/bot.ts" lineNumbers
-createGitHubAdapter({
-  appId: process.env.GITHUB_APP_ID!,
-  privateKey: process.env.GITHUB_PRIVATE_KEY!,
-  installationId: parseInt(process.env.GITHUB_INSTALLATION_ID!),
-});
-```
-
-**Multi-tenant (omit `installationId`):**
-
-```typescript title="lib/bot.ts" lineNumbers
-createGitHubAdapter({
-  appId: process.env.GITHUB_APP_ID!,
-  privateKey: process.env.GITHUB_PRIVATE_KEY!,
-});
-```
-
-The adapter automatically extracts installation IDs from webhooks and caches API clients per-installation.
-
-## Webhook setup
-
-For repository or organization webhooks:
-
-1. Go to repository/org **Settings** then **Webhooks** then **Add webhook**
-2. Set **Payload URL** to `https://your-domain.com/api/webhooks/github`
-3. Set **Content type** to `application/json` (required — the default `application/x-www-form-urlencoded` does not work)
-4. Set **Secret** to match your `webhookSecret`
-5. Select events: Issue comments, Pull request review comments
-
-<Callout type="warn">
-GitHub App webhooks are configured during app creation. Make sure to select `application/json` as the content type.
-</Callout>
-
-## Thread model
-
-GitHub has two types of comment threads:
-
-| Type | Tab | Thread ID format |
-|------|-----|-----------------|
-| PR-level | Conversation | `github:{owner}/{repo}:{prNumber}` |
-| Review comments | Files Changed | `github:{owner}/{repo}:{prNumber}:rc:{commentId}` |
-
-## Reactions
-
-Supports GitHub's reaction emoji:
-
-| SDK emoji | GitHub reaction |
-|-----------|----------------|
-| `thumbs_up` | 👍 (+1) |
-| `thumbs_down` | 👎 (-1) |
-| `laugh` | 😄 |
-| `confused` | 😕 |
-| `heart` | ❤️ |
-| `hooray` | 🎉 |
-| `rocket` | 🚀 |
-| `eyes` | 👀 |
-
-## Configuration
-
-All options are auto-detected from environment variables when not provided.
-
-| Option | Required | Description |
-|--------|----------|-------------|
-| `token` | No* | Personal Access Token. Auto-detected from `GITHUB_TOKEN` |
-| `appId` | No* | GitHub App ID. Auto-detected from `GITHUB_APP_ID` |
-| `privateKey` | No | GitHub App private key (PEM). Auto-detected from `GITHUB_PRIVATE_KEY` |
-| `installationId` | No | Installation ID (omit for multi-tenant). Auto-detected from `GITHUB_INSTALLATION_ID` |
-| `webhookSecret` | No** | Webhook secret. Auto-detected from `GITHUB_WEBHOOK_SECRET` |
-| `userName` | No | Bot username for @mention detection. Auto-detected from `GITHUB_BOT_USERNAME` (default: `"github-bot"`) |
-| `botUserId` | No | Bot's numeric user ID (auto-detected if not provided) |
-| `logger` | No | Logger instance (defaults to `ConsoleLogger("info")`) |
-
-*Either `token`/`GITHUB_TOKEN` or `appId`+`privateKey`/`GITHUB_APP_ID`+`GITHUB_PRIVATE_KEY` is required.
-
-**`webhookSecret` is required — either via config or `GITHUB_WEBHOOK_SECRET` env var.
-
-## Environment variables
-
-```bash title=".env.local"
-# Personal Access Token auth
-GITHUB_TOKEN=ghp_xxxxxxxxxxxx
-
-# OR GitHub App auth
-GITHUB_APP_ID=123456
-GITHUB_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----..."
-GITHUB_INSTALLATION_ID=12345678  # Optional for multi-tenant
-
-# Required
-GITHUB_WEBHOOK_SECRET=your-webhook-secret
-```
-
-## Features
-
-| Feature | Supported |
-|---------|-----------|
-| Mentions | Yes |
-| Reactions (add/remove) | Yes |
-| Cards | GFM Markdown |
-| Modals | No |
-| Streaming | No |
-| DMs | No |
-| File uploads | No |
-| Typing indicator | No |
-| Message history | Yes |
-| Multi-tenant | Yes (GitHub App) |
-
-## Limitations
-
-- **No typing indicators** — GitHub doesn't support typing indicators
-- **No streaming** — Messages posted in full (editing supported for updates)
-- **No DMs** — GitHub doesn't have direct messages
-- **No modals** — GitHub doesn't support interactive modals
-- **Action buttons** — Rendered as text; use link buttons for clickable actions
-
-## Troubleshooting
-
-### "Invalid signature" error
-
-- Verify `GITHUB_WEBHOOK_SECRET` matches your webhook configuration
-- Ensure the request body isn't modified before verification
-
-### "Invalid JSON" error
-
-- Change webhook **Content type** to `application/json`
-
-### Bot not responding to mentions
-
-- Verify webhook events are configured (issue_comment, pull_request_review_comment)
-- Check the webhook URL is correct and accessible
-- Ensure the `userName` config matches your bot's GitHub username
-
-### "Installation ID required" error
-
-- This occurs when making API calls outside webhook context in multi-tenant mode
-- Use a persistent state adapter (Redis) to store installation mappings
-- The first interaction must come from a webhook to establish the mapping
-
-### Rate limiting
-
-- PATs have lower rate limits than GitHub Apps
-- Consider switching to a GitHub App for production use

package/docs/adapters/linear.mdx

@@ -1,206 +0,0 @@
----
-title: Linear
-description: Configure the Linear adapter to respond to @mentions in issue comment threads.
-type: integration
-prerequisites:
-  - /docs/getting-started
----
-
-The Linear adapter treats issue comments as messages and issues as threads.
-
-## Installation
-
-```sh title="Terminal"
-pnpm add @chat-adapter/linear
-```
-
-## Usage
-
-The adapter auto-detects credentials from `LINEAR_API_KEY` (or `LINEAR_CLIENT_ID`/`LINEAR_CLIENT_SECRET`), `LINEAR_WEBHOOK_SECRET`, and `LINEAR_BOT_USERNAME` environment variables:
-
-```typescript title="lib/bot.ts" lineNumbers
-import { Chat } from "chat";
-import { createLinearAdapter } from "@chat-adapter/linear";
-
-const bot = new Chat({
-  userName: "my-bot",
-  adapters: {
-    linear: createLinearAdapter(),
-  },
-});
-
-bot.onNewMention(async (thread, message) => {
-  await thread.post("Hello from Linear!");
-});
-```
-
-## Authentication
-
-### Option A: Personal API key
-
-Best for personal projects, testing, or single-workspace bots. Actions are attributed to you as an individual.
-
-1. Go to [Settings > Security & Access](https://linear.app/settings/account/security)
-2. Under **Personal API keys**, click **Create key**
-3. Select **Only select permissions** and enable Create issues, Create comments
-4. Choose team access
-5. Click **Create** and set `LINEAR_API_KEY`
-
-```typescript title="lib/bot.ts" lineNumbers
-createLinearAdapter({
-  apiKey: process.env.LINEAR_API_KEY!,
-});
-```
-
-### Option B: OAuth application (recommended)
-
-The bot gets its own identity in Linear. The adapter handles token management internally.
-
-1. Go to [Settings > API > Applications](https://linear.app/settings/api/applications/new)
-2. Create an OAuth2 application with your bot's name and icon
-3. **Enable client credentials tokens** in the app settings
-4. Note the **Client ID** and **Client Secret**
-
-```typescript title="lib/bot.ts" lineNumbers
-createLinearAdapter({
-  clientId: process.env.LINEAR_CLIENT_ID!,
-  clientSecret: process.env.LINEAR_CLIENT_SECRET!,
-});
-```
-
-The adapter uses the client credentials grant to obtain tokens automatically. Tokens are valid for 30 days and auto-refresh when expired.
-
-### Making the bot @-mentionable (optional)
-
-To make the bot appear in Linear's `@` mention dropdown as an Agent:
-
-1. In your OAuth app settings, enable **Agent session events** under webhooks
-2. Have a workspace admin install the app with `actor=app` and the `app:mentionable` scope:
-
-```
-https://linear.app/oauth/authorize?
-  client_id=your_client_id&
-  redirect_uri=https://your-domain.com/callback&
-  response_type=code&
-  scope=read,write,comments:create,app:mentionable&
-  actor=app
-```
-
-See the [Linear Agents docs](https://linear.app/developers/agents) for full details.
-
-## Webhook setup
-
-<Callout type="info">
-Webhook management requires workspace admin access. If you don't see the API settings page, ask a workspace admin to create the webhook for you.
-</Callout>
-
-1. Go to **Settings > API** and click **Create webhook**
-2. Fill in:
-   - **Label**: A descriptive name (e.g., "Chat Bot")
-   - **URL**: `https://your-domain.com/api/webhooks/linear`
-3. Copy the **Signing secret** as `LINEAR_WEBHOOK_SECRET`
-4. Under **Data change events**, select:
-   - **Comments** (required)
-   - **Issues** (recommended)
-   - **Emoji reactions** (optional)
-5. Under **Team selection**, choose **All public teams** or a specific team
-6. Click **Create webhook**
-
-## Thread model
-
-Linear has two levels of comment threading:
-
-| Type | Description | Thread ID format |
-|------|-------------|-----------------|
-| Issue-level | Top-level comments on an issue | `linear:{issueId}` |
-| Comment thread | Replies nested under a specific comment | `linear:{issueId}:c:{commentId}` |
-
-When a user writes a comment, the bot replies within the same comment thread.
-
-## Reactions
-
-| SDK emoji | Linear emoji |
-|-----------|-------------|
-| `thumbs_up` | 👍 |
-| `thumbs_down` | 👎 |
-| `heart` | ❤️ |
-| `fire` | 🔥 |
-| `rocket` | 🚀 |
-| `eyes` | 👀 |
-| `sparkles` | ✨ |
-| `wave` | 👋 |
-
-## Configuration
-
-All options are auto-detected from environment variables when not provided.
-
-| Option | Required | Description |
-|--------|----------|-------------|
-| `apiKey` | No* | Personal API key. Auto-detected from `LINEAR_API_KEY` |
-| `clientId` | No* | OAuth app client ID. Auto-detected from `LINEAR_CLIENT_ID` |
-| `clientSecret` | No* | OAuth app client secret. Auto-detected from `LINEAR_CLIENT_SECRET` |
-| `accessToken` | No* | Pre-obtained OAuth access token. Auto-detected from `LINEAR_ACCESS_TOKEN` |
-| `webhookSecret` | No** | Webhook signing secret. Auto-detected from `LINEAR_WEBHOOK_SECRET` |
-| `userName` | No | Bot display name. Auto-detected from `LINEAR_BOT_USERNAME` (default: `"linear-bot"`) |
-| `logger` | No | Logger instance (defaults to `ConsoleLogger("info")`) |
-
-*One of `apiKey`, `clientId`/`clientSecret`, or `accessToken` is required (via config or env vars).
-
-**`webhookSecret` is required — either via config or `LINEAR_WEBHOOK_SECRET` env var.
-
-## Environment variables
-
-```bash title=".env.local"
-# API Key auth
-LINEAR_API_KEY=lin_api_xxxxxxxxxxxx
-
-# OR OAuth app auth
-LINEAR_CLIENT_ID=your-client-id
-LINEAR_CLIENT_SECRET=your-client-secret
-
-# Required
-LINEAR_WEBHOOK_SECRET=your-webhook-secret
-```
-
-## Features
-
-| Feature | Supported |
-|---------|-----------|
-| Mentions | Yes |
-| Reactions (add) | Yes |
-| Cards | Markdown |
-| Modals | No |
-| Streaming | No |
-| DMs | No |
-| File uploads | No |
-| Typing indicator | No |
-| Message history | Yes |
-
-## Limitations
-
-- **No typing indicators** — Linear doesn't support typing indicators
-- **No streaming** — Messages posted in full (editing supported for updates)
-- **No DMs** — Linear doesn't have direct messages
-- **No modals** — Linear doesn't support interactive modals
-- **Action buttons** — Rendered as text; use link buttons for clickable actions
-- **Remove reaction** — Requires reaction ID lookup (not directly supported)
-
-## Troubleshooting
-
-### "Invalid signature" error
-
-- Verify `LINEAR_WEBHOOK_SECRET` matches the secret from your webhook configuration
-- The webhook secret is shown only once at creation — regenerate if lost
-
-### Bot not responding to mentions
-
-- Verify webhook events are configured with **Comments** resource type
-- Check that the webhook URL is correct and accessible
-- Ensure the `userName` config matches how users mention the bot
-- Linear may auto-disable webhooks after repeated failures
-
-### "Webhook expired" error
-
-- Webhook timestamp is too old (> 5 minutes)
-- Usually indicates a delivery delay or clock skew
-- Check that your server time is synchronized

package/docs/adapters/meta.json

@@ -1,13 +0,0 @@
-{
-  "title": "Adapters",
-  "pages": [
-    "index",
-    "slack",
-    "teams",
-    "gchat",
-    "discord",
-    "telegram",
-    "github",
-    "linear"
-  ]
-}