Stability and CI: DRY playback flow, tests, and Raycast-ready checks

.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+      - master
+
+jobs:
+  validate:
+    runs-on: macos-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Lint
+        run: npm run lint
+
+      - name: Test
+        run: npm run test
+
+      - name: Verify assets
+        run: npm run verify:assets
+
+      - name: Verify dependencies
+        run: npm run verify:deps
+
+      - name: Build
+        run: npm run build

CHANGELOG.md

@@ -1,3 +1,12 @@
 # crickets Changelog
 
+## [Stability and CI hardening] - {PR_MERGE_DATE}
+
+- Refactor command runtime flow to use deterministic bundled asset resolution.
+- Add explicit failure handling for missing/unreadable sound assets.
+- Remove unused runtime dependencies to keep the extension lightweight.
+- Add minimal automated tests for path resolution and command behavior.
+- Add CI workflow for lint, test, verification, and build checks.
+- Refresh README with current command behavior and requirements.
+
 ## [Initial Version] - {PR_MERGE_DATE}

README.md

@@ -1,3 +1,28 @@
-# crickets
+# Crickets
 
-Plays a Crickets sound for use in weird situations where you need to quickly play a crickets sound
+Play a quick cricket chirp sound effect from Raycast.
+
+## Features
+
+- Single `no-view` command for instant playback
+- Bundled audio asset (`assets/crickets.mp3`) for deterministic behavior
+- Fast failure feedback when playback cannot start
+- macOS-only support (uses `afplay`)
+
+## Command
+
+- `Crickets`: plays the bundled cricket sound and shows a HUD confirmation
+
+## Requirements
+
+- Raycast
+- macOS
+
+## Development
+
+```bash
+npm install
+npm run check
+```
+
+`npm run check` runs linting, tests, asset/dependency verification, and a production build to stay aligned with Raycast publication checks.