jonsoc 1.1.50 → 1.1.51

package/AGENTS.md

@@ -0,0 +1,27 @@
+# jonsoc agent guidelines
+
+## Build/Test Commands
+
+- **Install**: `bun install`
+- **Run**: `bun run --conditions=browser ./src/index.ts`
+- **Typecheck**: `bun run typecheck` (npm run typecheck)
+- **Test**: `bun test` (runs all tests)
+- **Single test**: `bun test test/tool/tool.test.ts` (specific test file)
+
+## Code Style
+
+- **Runtime**: Bun with TypeScript ESM modules
+- **Imports**: Use relative imports for local modules, named imports preferred
+- **Types**: Zod schemas for validation, TypeScript interfaces for structure
+- **Naming**: camelCase for variables/functions, PascalCase for classes/namespaces
+- **Error handling**: Use Result patterns, avoid throwing exceptions in tools
+- **File structure**: Namespace-based organization (e.g., `Tool.define()`, `Session.create()`)
+
+## Architecture
+
+- **Tools**: Implement `Tool.Info` interface with `execute()` method
+- **Context**: Pass `sessionID` in tool context, use `App.provide()` for DI
+- **Validation**: All inputs validated with Zod schemas
+- **Logging**: Use `Log.create({ service: "name" })` pattern
+- **Storage**: Use `Storage` namespace for persistence
+- **API Client**: The TypeScript TUI (built with SolidJS + OpenTUI) communicates with the JonsOC server using `@jonsoc/sdk`. When adding/modifying server endpoints in `packages/jonsoc/src/server/server.ts`, run `./script/generate.ts` to regenerate the SDK and related files.

package/Dockerfile

@@ -0,0 +1,18 @@
+FROM alpine AS base
+
+# Disable the runtime transpiler cache by default inside Docker containers.
+# On ephemeral containers, the cache is not useful
+ARG BUN_RUNTIME_TRANSPILER_CACHE_PATH=0
+ENV BUN_RUNTIME_TRANSPILER_CACHE_PATH=${BUN_RUNTIME_TRANSPILER_CACHE_PATH}
+RUN apk add libgcc libstdc++ ripgrep
+
+FROM base AS build-amd64
+COPY dist/opencode-linux-x64-baseline-musl/bin/opencode /usr/local/bin/opencode
+
+FROM base AS build-arm64
+COPY dist/opencode-linux-arm64-musl/bin/opencode /usr/local/bin/opencode
+
+ARG TARGETARCH
+FROM build-${TARGETARCH}
+RUN opencode --version
+ENTRYPOINT ["opencode"]

package/PUBLISHING_GUIDE.md

@@ -0,0 +1,151 @@
+# Publishing jonsOC to npm
+
+This guide explains how to publish jonsOC as a global npm package that users can install with `bun add -g jonsoc` or `npm install -g jonsoc`.
+
+## Changes Made
+
+1. **Removed `"private": true`** from `package.json` to allow publishing
+2. **Updated package name** in publish script from "jonsoc" to "jonsoc"
+3. **Added npm metadata** (description, keywords, repository, etc.) for better discoverability
+4. **Updated README** with installation and usage instructions
+
+## How It Works
+
+jonsOC uses a multi-package distribution strategy (similar to esbuild, Parcel, etc.):
+
+1. **Main package (`jonsoc`)**: Contains the wrapper script that users install
+2. **Platform-specific packages**: Compiled binaries for each platform:
+   - `jonsoc-linux-x64`
+   - `jonsoc-darwin-arm64`
+   - `jonsoc-windows-x64`
+
+When users install `jonsoc`, npm automatically installs the correct platform-specific binary as an optional dependency.
+
+## Prerequisites
+
+Before publishing, make sure you:
+
+1. **Have an npm account**: Sign up at https://www.npmjs.com
+2. **Are logged in to npm**:
+   ```bash
+   npm login
+   ```
+3. **Check package name availability**:
+   ```bash
+   npm view jonsoc
+   ```
+   If the package exists and isn't yours, you'll need to choose a different name.
+
+## Publishing Steps
+
+### 1. Build all platform binaries
+
+```bash
+cd packages/jonsoc
+bun run build
+```
+
+This creates compiled binaries for all supported platforms in the `dist/` directory.
+
+### 2. Test locally (optional but recommended)
+
+Build for your current platform only:
+
+```bash
+bun run build -- --single
+```
+
+Test the binary:
+
+```bash
+./dist/jonsoc-<your-platform>-<your-arch>/bin/jonsoc --version
+```
+
+### 3. Publish to npm
+
+```bash
+bun run script/publish.ts
+```
+
+This will:
+
+- Publish all platform-specific packages
+- Publish the main `jonsoc` package
+- Create GitHub release archives (if configured)
+
+### 4. Test the published package
+
+```bash
+# In a different directory
+bun add -g jonsoc
+
+# Verify installation
+jonsoc --version
+jonsoc --help
+```
+
+## Version Management
+
+The version is managed in `@jonsoc/script` package. To publish a new version:
+
+1. Update the version in the script package
+2. Run the build and publish commands
+
+## Troubleshooting
+
+### Package name already taken
+
+If `jonsoc` is already taken on npm, you have a few options:
+
+1. **Use a scoped package**: Change to `@your-username/jonsoc`
+2. **Choose a different name**: e.g., `jonsoc-cli`, `jonsoc-dev`, etc.
+3. **Contact the current owner** if the package is abandoned
+
+To use a scoped package, update the `name` field in `package.json`:
+
+```json
+{
+  "name": "@your-username/jonsoc"
+}
+```
+
+### Authentication errors
+
+If you get authentication errors:
+
+```bash
+npm whoami  # Check if logged in
+npm login   # Login if needed
+```
+
+### Platform binary issues
+
+If a specific platform binary fails to build:
+
+```bash
+# Build only current platform for testing
+bun run build -- --single
+
+# Skip npm install during build
+bun run build -- --skip-install
+```
+
+## Publishing Updates
+
+When publishing updates:
+
+1. Update version in script package
+2. Run `bun run build`
+3. Run `bun run script/publish.ts`
+
+The publish script automatically:
+
+- Tags releases based on the channel (stable, preview, etc.)
+- Creates platform-specific packages
+- Updates the main package
+
+## Notes
+
+- The publish script uses `--access public` to ensure packages are publicly available
+- Platform-specific binaries are automatically selected during installation based on OS and architecture
+- The bin wrapper (`bin/jonsoc`) handles finding and executing the correct binary

package/README.md

@@ -0,0 +1,58 @@
+# jonsOC
+
+AI-powered development tool for modern coding workflows.
+
+## Installation
+
+Install globally using bun:
+
+```bash
+bun add -g jonsoc
+```
+
+Or with npm:
+
+```bash
+npm install -g jonsoc
+```
+
+## Usage
+
+Once installed, you can use jonsOC from anywhere:
+
+```bash
+jonsoc --help
+```
+
+## Development
+
+To install dependencies:
+
+```bash
+bun install
+```
+
+To run locally:
+
+```bash
+bun run dev
+```
+
+To build for all platforms:
+
+```bash
+bun run build
+```
+
+## Publishing
+
+To build and publish to npm:
+
+```bash
+bun run build
+bun run script/publish.ts
+```
+
+## License
+
+MIT