opencode-pilot 0.1.0

package/.devcontainer/devcontainer.json

@@ -0,0 +1,16 @@
+{
+  "name": "opencode-pilot",
+  "image": "mcr.microsoft.com/devcontainers/javascript-node:22",
+  "features": {
+    "ghcr.io/devcontainers/features/git:1": {},
+    "ghcr.io/devcontainers/features/github-cli:1": {}
+  },
+  "postCreateCommand": "sudo apt-get update && sudo apt-get install -y bats ripgrep && npm install -g opencode-ai@latest",
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "dbaeumer.vscode-eslint"
+      ]
+    }
+  }
+}

package/.github/workflows/ci.yml

@@ -0,0 +1,67 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+permissions:
+  contents: write
+  id-token: write  # Enable OIDC for npm trusted publishing
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Verify JavaScript syntax
+        run: |
+          for file in plugin/*.js; do
+            echo "Checking $file..."
+            node --check "$file"
+          done
+
+      - name: Run unit tests
+        run: npm test
+      
+      # Note: Bash integration tests removed pending conversion to JS (see #63)
+      # The JS unit tests in test/unit/ provide coverage for core functionality
+
+  release:
+    needs: test
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+    runs-on: ubuntu-latest
+    outputs:
+      new_release_published: ${{ steps.semantic.outputs.new_release_published }}
+      new_release_version: ${{ steps.semantic.outputs.new_release_version }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+
+      - name: Install Node.js dependencies
+        run: npm install
+
+      - name: Run semantic-release
+        id: semantic
+        uses: cycjimmy/semantic-release-action@v4
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_CONFIG_PROVENANCE: true

package/.releaserc.cjs

@@ -0,0 +1,28 @@
+module.exports = {
+  branches: [
+    'main'
+  ],
+  
+  plugins: [
+    // Analyze commits to determine release type
+    '@semantic-release/commit-analyzer',
+    
+    // Generate release notes
+    '@semantic-release/release-notes-generator',
+    
+    // Update version in package.json and publish to npm with provenance
+    ['@semantic-release/npm', { provenance: true }],
+    
+    // Commit the version changes
+    [
+      '@semantic-release/git',
+      {
+        assets: ['package.json', 'package-lock.json'],
+        message: 'chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}'
+      }
+    ],
+    
+    // Create GitHub release
+    '@semantic-release/github'
+  ]
+};

package/AGENTS.md

@@ -0,0 +1,71 @@
+# Agent Instructions
+
+## Pre-Commit: Documentation Check
+
+Before committing changes, verify documentation is updated to reflect code changes:
+
+1. **README.md** - Update if changes affect:
+   - Configuration options (config.yaml keys)
+   - CLI commands (`opencode-pilot <command>`)
+   - Notification types or behavior
+   - Installation or setup steps
+   - Service management
+   - Sources or polling behavior
+
+2. **CONTRIBUTING.md** - Update if changes affect:
+   - Development setup or workflow
+   - Test commands or patterns
+   - Plugin architecture
+
+## Post-PR: Release and Upgrade Workflow
+
+After a PR is merged to main, follow this workflow to upgrade the local installation:
+
+### 1. Watch CI Run
+
+Watch the CI workflow until it completes (creates release via semantic-release and publishes to npm):
+
+```bash
+gh run watch -R athal7/opencode-pilot
+```
+
+### 2. Verify Release Created
+
+Confirm the new release was published:
+
+```bash
+gh release list -R athal7/opencode-pilot -L 1
+npm view opencode-pilot version
+```
+
+### 3. Restart OpenCode
+
+OpenCode auto-updates npm plugins. Simply restart any running OpenCode sessions to get the latest version.
+
+### 4. Restart Service
+
+If the callback service is running, restart it:
+
+```bash
+# Stop current service (Ctrl+C) and restart
+npx opencode-pilot start
+```
+
+### 5. Verify Upgrade
+
+```bash
+npx opencode-pilot status
+```
+
+## Configuration
+
+Config file: `~/.config/opencode-pilot/config.yaml`
+
+Configuration has three sections:
+- `notifications` - ntfy settings (topic, server, callback, etc.)
+- `repos` - per-repository settings (use YAML anchors to share config)
+- `sources` - polling sources with generic MCP tool references
+
+Template files: `~/.config/opencode-pilot/templates/*.md`
+
+See [examples/config.yaml](examples/config.yaml) for a complete example.

package/CONTRIBUTING.md

@@ -0,0 +1,102 @@
+# Contributing to opencode-ntfy
+
+Thanks for your interest in contributing!
+
+## Development Setup
+
+1. Clone the repository:
+   ```bash
+   git clone https://github.com/athal7/opencode-ntfy.git
+   cd opencode-ntfy
+   ```
+
+2. Install the plugin locally for testing:
+   ```bash
+   ./install.sh
+   ```
+
+3. Set required environment variables:
+   ```bash
+   export NTFY_TOPIC=your-test-topic
+   ```
+
+## Running Tests
+
+Run the full test suite:
+```bash
+./test/run_tests.bash
+```
+
+The test suite includes:
+- **File structure tests** - Verify all plugin files exist
+- **Syntax validation** - Run `node --check` on all JS files
+- **Export structure tests** - Verify expected functions are exported
+- **Integration tests** - Test plugin loads in OpenCode without hanging (requires opencode CLI)
+
+## Writing Tests
+
+Tests live in `test/` using bash test helpers from `test_helper.bash`.
+
+Example test:
+```bash
+test_my_feature() {
+  # Use assertions from test_helper.bash
+  assert_file_exists "$PLUGIN_DIR/myfile.js"
+  assert_contains "$output" "expected string"
+}
+
+# Register and run
+run_test "my_feature" "test_my_feature"
+```
+
+For JavaScript unit tests, use Node.js inline:
+```bash
+test_function_works() {
+  node --input-type=module -e "
+    import { myFunction } from '../plugin/module.js';
+    if (myFunction() !== 'expected') throw new Error('Failed');
+    console.log('PASS');
+  " || return 1
+}
+```
+
+## Code Style
+
+- Use ES modules (`import`/`export`)
+- Use `async`/`await` for async operations
+- Log with `[opencode-ntfy]` prefix
+- Handle errors gracefully (log, don't crash OpenCode)
+- No external dependencies (use Node.js built-ins only)
+
+## Plugin Architecture
+
+```
+plugin/
+├── index.js      # Main entry point, event handlers
+├── notifier.js   # ntfy HTTP client
+├── callback.js   # HTTP callback server for interactive responses
+├── hostname.js   # Callback host discovery (Tailscale, env, localhost)
+└── nonces.js     # Single-use nonces for callback authentication
+```
+
+## Submitting Changes
+
+1. Create a feature branch: `git checkout -b my-feature`
+2. Make your changes
+3. Run tests: `./test/run_tests.bash`
+4. Commit with a clear message following conventional commits:
+   - `feat(#1): add idle notifications`
+   - `fix(#3): handle network timeout`
+5. Push and open a pull request
+
+## Releasing
+
+Releases are automated via GitHub Actions. To create a release:
+
+1. Tag the commit: `git tag v1.0.0`
+2. Push the tag: `git push origin v1.0.0`
+
+The release workflow will:
+1. Run tests
+2. Create a tarball
+3. Create a GitHub release with release notes

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Andrew Thal
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,72 @@
+# opencode-pilot
+
+Automation layer for [OpenCode](https://github.com/sst/opencode) - notifications and workflow orchestration.
+
+> **Note**: This is a community project and is not built by or affiliated with the OpenCode team.
+
+## Features
+
+- **Idle notifications** - Get notified when OpenCode has been waiting for input
+- **Error alerts** - Stay informed when something needs attention
+- **Polling automation** - Automatically start sessions from GitHub issues, Linear tickets, etc.
+
+## Installation
+
+Add the plugin to your `~/.config/opencode/opencode.json`:
+
+```json
+{
+  "plugin": ["opencode-pilot"]
+}
+```
+
+OpenCode auto-installs npm plugins on startup.
+
+## Quick Start
+
+1. **Create config** - Copy [examples/config.yaml](examples/config.yaml) to `~/.config/opencode-pilot/config.yaml` and customize
+
+2. **Start the service** (in a separate terminal):
+
+   ```bash
+   npx opencode-pilot start
+   ```
+
+3. **Run OpenCode** - notifications will be sent to your ntfy topic!
+
+## Configuration
+
+See [examples/config.yaml](examples/config.yaml) for a complete example with all options.
+
+### Key Sections
+
+- **`notifications`** - ntfy settings (topic, server, idle/error settings)
+- **`repos`** - Repository paths and settings (use YAML anchors to share config)
+- **`sources`** - What to poll (GitHub issues, Linear tickets, etc.)
+- **`tools`** - Field mappings to normalize different MCP APIs
+
+### Prompt Templates
+
+Create prompt templates as markdown files in `~/.config/opencode-pilot/templates/`. Templates support placeholders like `{title}`, `{body}`, `{number}`, `{html_url}`, etc.
+
+## Service Management
+
+```bash
+npx opencode-pilot start              # Start the service (foreground)
+npx opencode-pilot status             # Check status
+npx opencode-pilot test-source NAME   # Test a source
+```
+
+## Troubleshooting
+
+1. Check ntfy topic: `curl -d "test" ntfy.sh/your-topic`
+2. Verify config: `npx opencode-pilot config`
+3. Enable debug logging: set `notifications.debug: true` in config
+
+## Related
+
+- [opencode-devcontainers](https://github.com/athal7/opencode-devcontainers) - Run multiple devcontainer instances for OpenCode
+
+## License
+
+MIT