@jtalk22/slack-mcp 1.2.2 → 1.2.4

package/README.md

@@ -32,18 +32,19 @@
   <a href="https://github.com/jtalk22/slack-mcp-server/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/jtalk22/slack-mcp-server/ci.yml?label=build" alt="Build Status"></a>
   <a href="https://smithery.ai/server/jtalk22/slack-mcp-server"><img src="https://img.shields.io/badge/Smithery-Registry-4A154B" alt="Smithery"></a>
   <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT"></a>
-  <a href="https://github.com/sponsors/jtalk22"><img src="https://img.shields.io/badge/Sponsor-♡-ea4aaa?logo=github" alt="Sponsor"></a>
 </p>
 
 ---
 
+> Free local-first path: install with `npx -y @jtalk22/slack-mcp`, run on your own machine, and keep full control of session tokens.
+
 ### Why This Exists
 
 I built this because I was working with someone to help me manage a complex workload, and we kept hitting walls. They needed context from my messages—"what did X say about Y?"—and standard app/OAuth flows were too constrained for that workflow.
 
 Screenshotting messages is not a workflow.
 
-This server bridges the gap. It creates a secure, local bridge between Claude and your Slack web session. It gives your AI the same access **you** already have in the browser—search history, summarize threads, find that thing someone sent you three weeks ago—without fighting the platform.
+This server bridges the gap. It creates a secure, local bridge between Claude and your Slack web session. It gives your MCP client the same access **you** already have in the browser—search history, summarize threads, and retrieve prior context—without fighting the platform.
 
 ![Slack MCP Server Web UI](docs/images/demo-main.png)
 
@@ -100,15 +101,34 @@ Instead of authenticating as a bot, this server leverages your existing Chrome s
 
 **Runtime:** Node.js 20+
 
-### 2-Minute Verify
+### 30-Second Compatibility Check
 
 ```bash
 npx -y @jtalk22/slack-mcp --version
+npx -y @jtalk22/slack-mcp --doctor
 npx -y @jtalk22/slack-mcp --setup
-npx -y @jtalk22/slack-mcp --status
 ```
 
-If `--status` returns valid workspace/user info, your install path is working.
+Expected:
+- `--version` prints `slack-mcp-server v1.2.x`
+- `--doctor` returns one clear next action with exit code:
+  - `0` ready
+  - `1` missing credentials
+  - `2` invalid/expired credentials
+  - `3` connectivity/runtime issue
+- `--setup` launches the interactive wizard
+
+Command reference: [docs/HN-LAUNCH.md](docs/HN-LAUNCH.md)
+
+### Known Working Clients
+
+- Claude Desktop (macOS/Windows/Linux)
+- Claude Code CLI
+- Local browser mode (`web`)
+- Hosted Node runtime (`http`)
+- Cloudflare Worker / Smithery transport
+
+Compatibility matrix: [docs/COMPATIBILITY.md](docs/COMPATIBILITY.md)
 
 ### Option A: npm (Recommended)
 
@@ -130,6 +150,21 @@ npm install
 docker pull ghcr.io/jtalk22/slack-mcp-server:latest
 ```
 
+### Install Sanity (Clean Temp Directory)
+
+```bash
+tmpdir="$(mktemp -d)"
+cd "$tmpdir"
+npx -y @jtalk22/slack-mcp --version
+npx -y @jtalk22/slack-mcp --help
+npx -y @jtalk22/slack-mcp --status
+```
+
+Expected:
+- `--version` and `--help` exit `0`
+- `--status` exits non-zero until credentials are configured
+- `--status` is read-only and never attempts Chrome extraction
+
 ---
 
 ## Configuration
@@ -300,7 +335,7 @@ npm run web
 
 ```
 ════════════════════════════════════════════════════════════
-  Slack Web API Server v1.2.2
+  Slack Web API Server v1.2.4
 ════════════════════════════════════════════════════════════
 
   Dashboard: http://localhost:3000/?key=smcp_xxxxxxxxxxxx
@@ -321,14 +356,36 @@ Just click the link - no copy-paste needed. The key is saved to your browser and
 
 ## Operations Guides
 
+- [Docs Index](docs/INDEX.md) - One-click index for setup, API, troubleshooting, deployment, and support docs
 - [Deployment Modes](docs/DEPLOYMENT-MODES.md) - Choose the right operating model (`stdio`, `web`, hosted HTTP, Smithery/Worker)
 - [Use Case Recipes](docs/USE_CASE_RECIPES.md) - 12 copy/paste prompts mapped to current tool contracts
 - [Support Boundaries](docs/SUPPORT-BOUNDARIES.md) - Scope, response targets, and solo-maintainer capacity limits
+- [Release Health](docs/RELEASE-HEALTH.md) - Track setup reliability and support-load targets through this release cycle
 
 If you're evaluating team rollout, start with [Deployment Modes](docs/DEPLOYMENT-MODES.md) before exposing remote endpoints.
 
 ---
 
+## Getting Help Fast
+
+1. Run:
+   ```bash
+   npx -y @jtalk22/slack-mcp --version
+   npx -y @jtalk22/slack-mcp --doctor
+   ```
+2. If setup fails, run:
+   ```bash
+   npx -y @jtalk22/slack-mcp --setup
+   ```
+3. Open an issue with full environment details:
+   - [Bug Report Template](.github/ISSUE_TEMPLATE/bug_report.md)
+   - [Deployment Intake Template](.github/ISSUE_TEMPLATE/deployment-intake.md)
+4. Check scope and response targets:
+   - [Support Boundaries](docs/SUPPORT-BOUNDARIES.md)
+   - [Troubleshooting Guide](docs/TROUBLESHOOTING.md)
+
+---
+
 ## Troubleshooting
 
 ### Tokens Expired
@@ -337,6 +394,9 @@ If you're evaluating team rollout, start with [Deployment Modes](docs/DEPLOYMENT
 slack_refresh_tokens  # In Claude
 # Or: npm run tokens:auto
 
+# Package setup wizard
+npx -y @jtalk22/slack-mcp --setup
+
 # Linux/Windows: Manual update
 # Edit ~/.slack-mcp-tokens.json with fresh values
 ```
@@ -352,6 +412,7 @@ This caches DM channel IDs for 24 hours.
 - Chrome must be **running** (not minimized to Dock)
 - Slack tab must be open at `app.slack.com`
 - You must be logged in
+- In Chrome menu, enable `View > Developer > Allow JavaScript from Apple Events`
 
 ### Claude Desktop Not Seeing Tools
 1. Verify JSON syntax in config file
@@ -407,7 +468,7 @@ slack-mcp-server/
 
 PRs welcome. Run `node --check` on modified files before submitting.
 
-If you find this project useful, consider [sponsoring](https://github.com/sponsors/jtalk22) or starring the repo.
+If you find this project useful, consider starring the repo.
 
 ---
 

package/docs/API.md

@@ -11,7 +11,9 @@ Check if Slack tokens are valid.
 **Returns:**
 ```json
 {
-  "status": "OK",
+  "status": "ok",
+  "code": "ok",
+  "message": "Slack auth valid",
   "user": "james",
   "team": "Rêvasser",
   "token_source": "environment",
@@ -30,12 +32,15 @@ Get detailed token health, age, and cache statistics.
 **Returns:**
 ```json
 {
+  "status": "healthy",
+  "code": "ok",
+  "message": "Token is healthy",
+  "next_action": null,
   "token": {
     "status": "healthy",
     "age_hours": 2.5,
     "source": "file",
-    "updated_at": "2026-01-08T12:00:00Z",
-    "message": "Token is healthy"
+    "updated_at": "2026-01-08T12:00:00Z"
   },
   "auto_refresh": {
     "enabled": true,
@@ -62,7 +67,9 @@ Force refresh tokens from Chrome.
 **Returns:**
 ```json
 {
-  "status": "SUCCESS",
+  "status": "ok",
+  "code": "refreshed",
+  "message": "Tokens refreshed from Chrome.",
   "user": "james",
   "team": "Rêvasser"
 }

package/docs/COMMUNICATION-STYLE.md

@@ -9,6 +9,7 @@ Use this guide for release notes, issue replies, and changelog entries.
 3. Do not include co-author trailers from tooling.
 4. State exact versions and commands when relevant.
 5. Avoid speculative claims.
+6. Release titles use `vX.Y.Z — <concrete operational outcome>`.
 
 ## Issue Reply Template
 
@@ -18,12 +19,18 @@ Thanks for reporting this.
 Status: fixed in `<version>`.
 
 Included:
-- `<change 1>`
-- `<change 2>`
+- `<fix 1>`
+- `<fix 2>`
+
+Verify:
+- `npx -y @jtalk22/slack-mcp --version`
+- `npx -y @jtalk22/slack-mcp --status`
 
 Install/update:
 - `npx -y @jtalk22/slack-mcp`
 - `npm i -g @jtalk22/slack-mcp@<version>`
+
+If it still reproduces, reply with OS, Node version, runtime mode (`stdio|web|http|worker`), and exact error output.
 ```
 
 ## Release Notes Template
@@ -31,17 +38,18 @@ Install/update:
 ````md
 ## <version> — <short title>
 
-### Fixed
+### Improved
 - <item>
 - <item>
 
-### Runtime / Security
-- <item>
+### Compatibility
+- No API/tool schema changes.
 
 ### Verify
 ```bash
-<command>
-<command>
+npx -y @jtalk22/slack-mcp --version
+npx -y @jtalk22/slack-mcp --setup
+npx -y @jtalk22/slack-mcp --status
 ```
 ````
 

package/docs/COMPATIBILITY.md

@@ -0,0 +1,19 @@
+# Compatibility Matrix
+
+Use this matrix to choose a known working client/runtime path before rollout.
+
+| Client | Mode | Token path | Status | Quick verify command |
+|---|---|---|---|---|
+| Claude Desktop (macOS) | `stdio` | `~/.slack-mcp-tokens.json` via `--setup` auto-extract | Supported | `npx -y @jtalk22/slack-mcp --setup && npx -y @jtalk22/slack-mcp --status` |
+| Claude Desktop (Windows) | `stdio` | `env` (`SLACK_TOKEN`, `SLACK_COOKIE`) in config | Supported | `npx -y @jtalk22/slack-mcp --status` |
+| Claude Desktop (Linux) | `stdio` | `env` or token file via guided setup | Supported | `npx -y @jtalk22/slack-mcp --status` |
+| Claude Code CLI | `stdio` | `~/.slack-mcp-tokens.json` or `env` | Supported | `npx -y @jtalk22/slack-mcp --version && npx -y @jtalk22/slack-mcp --status` |
+| Local Browser UI | `web` | token file or `env` | Supported | `npx -y @jtalk22/slack-mcp web` |
+| Hosted Node Runtime | `http` | `env` in host runtime | Supported with operator controls | `node src/server-http.js` then `curl -s http://localhost:8080/health` |
+| Cloudflare Worker / Smithery transport | `worker` | runtime env/query handoff per deployment config | Supported with deployment validation | `wrangler deploy --config workers/wrangler.toml` and verify `/health` |
+
+## Notes
+
+1. Runtime baseline is Node 20+.
+2. `--doctor` is the fastest first check when setup status is unknown.
+3. For hosted/team deployment, use [DEPLOYMENT-MODES.md](DEPLOYMENT-MODES.md) before production rollout.

package/docs/HN-LAUNCH.md

@@ -0,0 +1,63 @@
+# HN Launch Kit
+
+Use this file as copy/paste launch material with minimal edits.
+
+## Title Options
+
+- `Show HN: Slack MCP Server (session-based Slack access for Claude)`
+- `Show HN: Slack MCP Server (local-first Slack context for Claude)`
+- `Show HN: Slack MCP Server (Slack MCP for local and hosted runtimes)`
+
+## Launch Post Template
+
+```md
+Built a session-based Slack MCP server so Claude can use the same access already available in your Slack web session.
+
+Current scope:
+- DM/channel/thread reads
+- workspace search
+- message sends and user lookups
+- local web mode when MCP is unavailable
+
+Verify:
+- `npx -y @jtalk22/slack-mcp --version`
+- `npx -y @jtalk22/slack-mcp --status`
+- `npx -y @jtalk22/slack-mcp --setup`
+
+Repo: https://github.com/jtalk22/slack-mcp-server
+npm: https://www.npmjs.com/package/@jtalk22/slack-mcp
+```
+
+## First Comment Draft
+
+```md
+Notes up front:
+- Local-first usage is fully supported.
+- Tokens are Slack session credentials and are stored locally by default.
+- macOS supports automatic Chrome extraction; Linux/Windows use guided manual setup.
+- Current docs include deployment modes, support boundaries, and troubleshooting.
+
+If install fails, include OS, Node version, runtime mode (`stdio|web|http|worker`), and exact error output.
+```
+
+## FAQ
+
+### Is this using Slack app OAuth scopes?
+No. It uses existing signed-in session permissions.
+
+### What about token expiry?
+Session tokens expire. `--setup` refreshes credentials, and macOS supports automatic extraction from Chrome.
+
+### Is hosted deployment required?
+No. The default path is local/self-hosted first. Deployment docs describe hosted tradeoffs.
+
+### Is this suitable for production teams?
+Treat as operator-managed infrastructure and validate against your own security and compliance requirements.
+
+## Install Check Block
+
+```bash
+npx -y @jtalk22/slack-mcp --version
+npx -y @jtalk22/slack-mcp --status
+npx -y @jtalk22/slack-mcp --setup
+```

package/docs/INDEX.md

@@ -0,0 +1,31 @@
+# Documentation Index
+
+Start here for setup, compatibility checks, operations, and support.
+
+## Core
+
+- [Setup Guide](SETUP.md)
+- [Compatibility Matrix](COMPATIBILITY.md)
+- [API Reference](API.md)
+- [Web API Reference](WEB-API.md)
+- [Troubleshooting](TROUBLESHOOTING.md)
+
+## Operations
+
+- [Deployment Modes](DEPLOYMENT-MODES.md)
+- [Use Case Recipes](USE_CASE_RECIPES.md)
+- [Support Boundaries](SUPPORT-BOUNDARIES.md)
+
+## Launch and Communication
+
+- [HN Launch Kit](HN-LAUNCH.md)
+- [Communication Style](COMMUNICATION-STYLE.md)
+- [Release Health Guide](RELEASE-HEALTH.md)
+- [Latest Release Health Snapshot](release-health/latest.md)
+- [Changelog](../CHANGELOG.md)
+
+## Issue Intake
+
+- [Bug Report Template](../.github/ISSUE_TEMPLATE/bug_report.md)
+- [Feature Request Template](../.github/ISSUE_TEMPLATE/feature_request.md)
+- [Deployment Intake Template](../.github/ISSUE_TEMPLATE/deployment-intake.md)

package/docs/RELEASE-HEALTH.md

@@ -0,0 +1,66 @@
+# Release Health Tracking
+
+Use this to track installation reliability and operational load during the current release cycle.
+
+## One-command snapshot
+
+```bash
+node scripts/collect-release-health.js
+```
+
+Outputs:
+- `docs/release-health/latest.md`
+- `docs/release-health/YYYY-MM-DD.md`
+- `docs/release-health/automation-delta.md` (when delta script is run)
+
+24-hour loop artifacts:
+- `docs/release-health/24h-start.md`
+- `docs/release-health/24h-end.md`
+- `docs/release-health/24h-delta.md`
+
+## What it captures automatically
+
+- npm downloads (last week, last month)
+- npm latest version
+- GitHub stars, forks, open issues
+- GitHub 14-day traffic views/clones (owner token required via `gh auth`)
+- Count of `deployment-intake` issues
+
+## 14-day targets
+
+- weekly downloads: `>= 180`
+- qualified deployment-intake submissions: `>= 2`
+- support load: `<= 2 hours/week`
+
+## Manual fields to track alongside snapshots
+
+- Weekly support minutes spent.
+- Deployment-intake quality (clear use case, owner, timeline).
+- Traffic source notes (search, referrals, docs traffic).
+- External \"first run succeeded\" confirmations (issues/discussions).
+
+## Recommended cadence
+
+- Days 1-7: daily snapshot
+- Days 8-14: every 2-3 days
+
+## Automated cadence (low-touch)
+
+- Workflow: `.github/workflows/release-health.yml`
+- Triggers:
+  - scheduled at `07:15` and `19:15` UTC
+  - manual `workflow_dispatch`
+- Outputs per run:
+  - workflow summary with current snapshot and baseline delta
+  - artifacts: `docs/release-health/latest.md`, `docs/release-health/automation-delta.md`
+
+## Local delta command
+
+If you want to compare two explicit snapshots locally:
+
+```bash
+node scripts/build-release-health-delta.js \
+  --before docs/release-health/24h-start.md \
+  --after docs/release-health/24h-end.md \
+  --out docs/release-health/24h-delta.md
+```

package/docs/SETUP.md

@@ -23,6 +23,25 @@ cd ~/slack-mcp-server
 npm install
 ```
 
+### 2.5 Verify Install Path in a Clean Directory
+
+```bash
+tmpdir="$(mktemp -d)"
+cd "$tmpdir"
+npx -y @jtalk22/slack-mcp --version
+npx -y @jtalk22/slack-mcp --help
+npx -y @jtalk22/slack-mcp --doctor
+```
+
+Expected:
+- `--version` and `--help` succeed.
+- `--doctor` exits with one clear status:
+  - `0` ready
+  - `1` missing credentials
+  - `2` invalid/expired credentials
+  - `3` connectivity/runtime issue
+- `--status` is read-only and never performs Chrome extraction.
+
 ### 3. Get Slack Tokens
 
 **Option A: Setup Wizard (recommended)**
@@ -120,11 +139,11 @@ You should see your username and team name.
 
 ### "No credentials found"
 
-Run `npx -y @jtalk22/slack-mcp --setup` with Slack open in Chrome, or `npm run tokens:refresh` to enter manually.
+Run `npx -y @jtalk22/slack-mcp --doctor` to confirm diagnostic code, then `npx -y @jtalk22/slack-mcp --setup` with Slack open in Chrome.
 
 ### "invalid_auth" Error
 
-Tokens have expired. Open Slack in Chrome and use `slack_refresh_tokens` in Claude Code.
+Tokens have expired. Run `npx -y @jtalk22/slack-mcp --doctor` and follow the suggested next action.
 
 ### MCP Server Not Loading
 
@@ -138,3 +157,4 @@ Make sure:
 - Chrome is running (not just in dock)
 - You have a Slack tab open (not the desktop app)
 - You're logged into Slack in that tab
+- In Chrome menu, enable `View > Developer > Allow JavaScript from Apple Events`

package/docs/TROUBLESHOOTING.md

@@ -4,6 +4,31 @@ Common issues and their solutions.
 
 ---
 
+## Install Flow Sanity Check
+
+If first-run setup is failing, validate command resolution in a clean directory:
+
+```bash
+tmpdir="$(mktemp -d)"
+cd "$tmpdir"
+npx -y @jtalk22/slack-mcp --version
+npx -y @jtalk22/slack-mcp --help
+npx -y @jtalk22/slack-mcp --doctor
+```
+
+Expected:
+- `--version` and `--help` exit `0`
+- `--doctor` exits with one of:
+  - `0` ready
+  - `1` missing credentials
+  - `2` invalid/expired credentials
+  - `3` connectivity/runtime issue
+- `--status` is read-only and never attempts Chrome extraction.
+
+If `--version` fails here, the issue is install/runtime path, not Slack credentials.
+
+---
+
 ## DMs Not Showing Up
 
 **Symptom:** `slack_list_conversations` returns channels but no DMs.
@@ -57,10 +82,13 @@ slack_refresh_tokens
 # Option 2: Package setup wizard
 npx -y @jtalk22/slack-mcp --setup
 
-# Option 3: Repo CLI
+# Option 3: Diagnostics check
+npx -y @jtalk22/slack-mcp --doctor
+
+# Option 4: Repo CLI
 npm run tokens:auto
 
-# Option 4: Manual
+# Option 5: Manual
 npm run tokens:refresh
 ```
 
@@ -185,7 +213,8 @@ tail -50 ~/Library/Logs/Claude/mcp-server-slack.log
 1. Google Chrome must be running (not just in Dock)
 2. Have a Slack tab open at `app.slack.com` (not desktop app)
 3. Be logged into Slack in that tab
-4. Grant accessibility permissions to Terminal/Claude
+4. In Chrome menu, enable `View > Developer > Allow JavaScript from Apple Events`
+5. Grant accessibility permissions to Terminal/Claude
 
 **Check permissions:**
 System Preferences → Privacy & Security → Accessibility → Ensure Terminal is enabled

package/docs/WEB-API.md

@@ -99,7 +99,9 @@ curl -H "Authorization: Bearer $API_KEY" http://localhost:3000/health
 **Response:**
 ```json
 {
-  "status": "OK",
+  "status": "ok",
+  "code": "ok",
+  "message": "Slack auth valid",
   "user": "james",
   "team": "Rêvasser"
 }
@@ -107,6 +109,15 @@ curl -H "Authorization: Bearer $API_KEY" http://localhost:3000/health
 
 ---
 
+### GET /token-status
+Read-only token diagnostics (age/health/cache stats). This endpoint does not trigger Chrome extraction.
+
+```bash
+curl -H "Authorization: Bearer $API_KEY" http://localhost:3000/token-status
+```
+
+---
+
 ### POST /refresh
 Force token refresh from Chrome.
 

package/docs/release-health/2026-02-25.md

@@ -0,0 +1,33 @@
+# Release Health Snapshot
+
+- Generated: 2026-02-25T06:14:12.948Z
+- Repo: `jtalk22/slack-mcp-server`
+- Package: `@jtalk22/slack-mcp`
+
+## Install Signals
+
+- npm downloads (last week): 139
+- npm downloads (last month): 632
+- npm latest version: 1.2.3
+
+## GitHub Reach
+
+- stars: 13
+- forks: 8
+- open issues: 0
+- 14d views: 497
+- 14d unique visitors: 259
+- 14d clones: 118
+- 14d unique cloners: 67
+- deployment-intake submissions (all-time): 1
+
+## 14-Day Reliability Targets (v1.2.3 Cycle)
+
+- weekly downloads: >= 180
+- qualified deployment-intake submissions: >= 2
+- maintainer support load: <= 2 hours/week
+
+## Notes
+
+- Update this snapshot daily during the first week, then every 2-3 days.
+- Track deployment-intake quality and support load manually in issue notes.

package/docs/release-health/2026-02-26.md

@@ -0,0 +1,33 @@
+# Release Health Snapshot
+
+- Generated: 2026-02-26T09:32:53.328Z
+- Repo: `jtalk22/slack-mcp-server`
+- Package: `@jtalk22/slack-mcp`
+
+## Install Signals
+
+- npm downloads (last week): 532
+- npm downloads (last month): 1011
+- npm latest version: 1.2.3
+
+## GitHub Reach
+
+- stars: 13
+- forks: 8
+- open issues: 0
+- 14d views: 498
+- 14d unique visitors: 263
+- 14d clones: 338
+- 14d unique cloners: 113
+- deployment-intake submissions (all-time): 1
+
+## 14-Day Reliability Targets (v1.2.3 Cycle)
+
+- weekly downloads: >= 180
+- qualified deployment-intake submissions: >= 2
+- maintainer support load: <= 2 hours/week
+
+## Notes
+
+- Update this snapshot daily during active release windows, then weekly.
+- Track deployment-intake quality and support load manually in issue notes.

package/docs/release-health/24h-delta.md

@@ -0,0 +1,21 @@
+# 24-Hour Release Health Delta
+
+- Window start snapshot: docs/release-health/24h-start.md
+- Window end snapshot: docs/release-health/24h-end.md
+
+| Metric | Start | End | Delta |
+|---|---:|---:|---:|
+| npm downloads (last week) | 532 | 532 | 0 |
+| npm downloads (last month) | 1011 | 1011 | 0 |
+| stars | 13 | 13 | 0 |
+| forks | 8 | 8 | 0 |
+| open issues | 0 | 0 | 0 |
+| 14d views | 498 | 498 | 0 |
+| 14d unique visitors | 263 | 263 | 0 |
+| 14d clones | 338 | 338 | 0 |
+| 14d unique cloners | 113 | 113 | 0 |
+| deployment-intake submissions (all-time) | 1 | 1 | 0 |
+
+## Qualitative Signal
+
+- External "first run succeeded" confirmations (issues/discussions): track manually in cycle notes.

package/docs/release-health/24h-end.md

@@ -0,0 +1,33 @@
+# Release Health Snapshot
+
+- Generated: 2026-02-26T09:32:53.328Z
+- Repo: `jtalk22/slack-mcp-server`
+- Package: `@jtalk22/slack-mcp`
+
+## Install Signals
+
+- npm downloads (last week): 532
+- npm downloads (last month): 1011
+- npm latest version: 1.2.3
+
+## GitHub Reach
+
+- stars: 13
+- forks: 8
+- open issues: 0
+- 14d views: 498
+- 14d unique visitors: 263
+- 14d clones: 338
+- 14d unique cloners: 113
+- deployment-intake submissions (all-time): 1
+
+## 14-Day Reliability Targets (v1.2.3 Cycle)
+
+- weekly downloads: >= 180
+- qualified deployment-intake submissions: >= 2
+- maintainer support load: <= 2 hours/week
+
+## Notes
+
+- Update this snapshot daily during active release windows, then weekly.
+- Track deployment-intake quality and support load manually in issue notes.