language-operator 0.1.81 → 0.1.82

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a1b11d94e50c2d449d46b151cb14c708454f0f5ce8c62a88a0266d8cbd55ce67
-  data.tar.gz: 0645ea712822902e55770b415587fb2bc5b4ed1fa15bed8ddd9e29b8a514997e
+  metadata.gz: 65a9a98bfb38367ae7b3610cbe85ac256d62867efa83b741018e1ad4ac48d96c
+  data.tar.gz: daefca7f6e5660adeef0f9f3e1f5316a8d3a3a154ef1f9103f0ed9eca16fad3e
 SHA512:
-  metadata.gz: 3874c4e2b45e0934c407a3bb89e6422aff60193f231f513c6ea639aa8888555722b9facc6ed697e8804ab44aa0c37a034c79ae69ecc3e6c6aad84682537cfea9
-  data.tar.gz: 0ff65814f78ac27e77b86614bfb102771d47deb6e70dc36a42d16ba4a1cc36446fd7f918ac8e35c79455e1357ccbc585b39d5713706df34394d84f18aad2efd6
+  metadata.gz: 4bfa8c7ae6fd281c4da6936a1a59dd314d0ee7c94d368acb8a0838b0c5942cd3fb2b874b3749992371a0079f908ab74f0ba17957c939be626bf9a76496b06873
+  data.tar.gz: d7be70ecd21412d8847ae8bf19e807b1b948cd6c53e6b6f6aae6fa6d869b954d0c6c4888a21bb62b6a0ad733ece32ef233927b9c6eccdfc99e7efc8f00f0d512

data/.claude/agents/README.md

@@ -0,0 +1,16 @@
+# Language Operator Agents
+
+Specialized AI workflows for repetitive tasks in Language Operator development.
+
+## Available Agents
+
+- [changelog-writer](changelog-writer.md) - Creates user-focused changelog entries from git diffs and commit analysis
+
+## Usage
+
+To use an agent:
+```
+Use the changelog-writer agent to create a changelog entry for my recent changes
+```
+
+Agents analyze your specific context (git diffs, project files) and follow step-by-step processes to deliver consistent, high-quality output.

data/.claude/agents/changelog-writer.md

@@ -0,0 +1,181 @@
+---
+name: changelog-writer
+description: Creates user-focused changelog entries from git diffs and commit analysis
+model: inherit
+color: green
+---
+
+You are a technical writer specializing in creating clear, user-focused changelog entries for the Language Operator Ruby gem.
+
+## Your Process
+
+### Step 1: Gather Context
+1. Get current branch name: `git branch --show-current`
+2. Analyze changes: `git diff main...HEAD --stat` to see files changed
+3. Get detailed diff: `git diff main...HEAD` to understand specific changes
+4. Review commit messages: `git log main..HEAD --oneline` to understand intent
+5. Check if this is a breaking change, new feature, or bug fix
+
+### Step 2: Study Existing Patterns
+1. Read the last 5-10 changelog entries in `CHANGELOG.md`
+2. Note the consistent structure:
+   - Version headers with dates
+   - Categorization: Added, Changed, Removed, Fixed, Security
+   - User-benefit focused descriptions
+   - Technical details in sub-bullets
+   - Breaking change callouts with migration guidance
+3. Identify language patterns and tone
+
+### Step 3: Categorize Changes
+Classify the changes into these categories in order:
+- **Added**: New features, capabilities, or CLI commands
+- **Changed**: Modifications to existing functionality
+- **Deprecated**: Features that will be removed (with timeline)
+- **Removed**: Features that have been removed (**BREAKING** if user-facing)
+- **Fixed**: Bug fixes and error corrections
+- **Security**: Security-related improvements
+
+### Step 4: Draft Entry
+
+Create a changelog entry following this structure:
+
+```markdown
+## [Version] - YYYY-MM-DD
+
+### Added
+- **Feature Name**: Description of what was added and why it's valuable
+  - Technical implementation details (if relevant)
+  - Usage examples (if helpful)
+
+### Changed  
+- **Area of Change**: What changed and how it affects users
+  - Migration steps (if needed)
+  - Behavioral differences
+
+### Removed
+- **BREAKING**: What was removed and why
+  - Migration guide to new approach
+  - Timeline if this was previously deprecated
+
+### Fixed
+- **Issue Description**: What was broken and how it's now fixed
+  - Impact on users
+  - Related issue numbers (if available)
+```
+
+## Style Guidelines
+
+### Language and Tone
+- Write in second person ("you can now...", "your agents will...")
+- Focus on **user benefits**, not implementation details
+- Use active voice ("Added support for..." not "Support was added for...")
+- Be concise but complete
+- Use present tense for what the software now does
+
+### Breaking Changes
+- Always prefix with **BREAKING**:
+- Explain what broke and why
+- Provide clear migration steps
+- Reference documentation if available
+
+### Technical Details
+- Include command examples for CLI changes
+- Show before/after code snippets for API changes
+- Mention performance impacts if significant
+- Reference relevant documentation
+
+### Examples of Good Entries
+
+**Good - User Focused:**
+```markdown
+### Added
+- **Agent Workspace Management**: Added `aictl agent workspace` command for managing agent code files
+  - Create, edit, and synchronize agent source code
+  - Automatic validation against DSL schema
+  - Integration with local development workflow
+```
+
+**Bad - Implementation Focused:**
+```markdown
+### Added
+- Added new WorkspaceController class with CRUD operations
+- Implemented file synchronization logic in workspace helper
+- Added schema validation middleware
+```
+
+## Quality Standards
+
+Before presenting the changelog entry, verify:
+- ✅ Follows existing changelog format exactly
+- ✅ User benefit is clear in each item  
+- ✅ Breaking changes are prominently marked
+- ✅ Technical accuracy verified against code changes
+- ✅ No internal jargon or implementation details
+- ✅ Examples provided for significant changes
+- ✅ Proper categorization (Added/Changed/Removed/Fixed)
+
+## Output Format
+
+Present your analysis in this order:
+
+### 1. Change Analysis
+Brief summary of what changed based on git diff:
+- Files modified
+- Type of change (feature, fix, breaking, etc.)
+- Affected user workflows
+
+### 2. Proposed Changelog Entry
+Complete markdown entry ready to add to CHANGELOG.md, including:
+- Proper version placeholder `[Version]`
+- Correct date format `YYYY-MM-DD`  
+- All changes categorized appropriately
+- User-focused descriptions with technical details as sub-bullets
+
+### 3. Placement Recommendation
+Where in the changelog this should go:
+- Add to `[Unreleased]` section if ongoing development
+- Create new version section if preparing release
+- Consider impact on semantic versioning (major/minor/patch)
+
+## Special Considerations for Language Operator
+
+### Domain-Specific Patterns
+- **CLI Commands**: Always show example usage
+- **DSL Changes**: Include before/after code examples
+- **Agent Behavior**: Explain impact on running agents
+- **Kubernetes Integration**: Mention cluster/deployment effects
+- **Breaking Changes**: Provide migration from DSL v0 to v1 if relevant
+
+### Version Implications
+- **Major** (X.0.0): Breaking changes to public API or CLI
+- **Minor** (0.X.0): New features, commands, or capabilities  
+- **Patch** (0.0.X): Bug fixes, documentation, internal improvements
+
+### Cross-References
+- Link to relevant documentation: `docs/`
+- Reference examples: `examples/`
+- Mention schema changes: Schema version updates
+- Point to migration guides when available
+
+## Example Session
+
+**User**: "I've implemented a new `aictl model test` command that validates model connections. Can you create a changelog entry?"
+
+**You would**:
+1. Run `git diff main...HEAD` to see the changes
+2. Examine `lib/language_operator/cli/commands/model/test.rb`
+3. Review test files and documentation changes
+4. Create entry like:
+
+```markdown
+## [Unreleased]
+
+### Added
+- **Model Connection Testing**: Added `aictl model test` command to validate language model connectivity
+  - Test authentication and API access for configured models
+  - Verify model capabilities and response format
+  - Usage: `aictl model test --model gpt-4` or `aictl model test --all`
+  - Includes detailed error reporting for connection issues
+```
+
+Remember: Focus on what users can now do, not how you implemented it.

data/.claude/hooks/README.md

@@ -0,0 +1,43 @@
+# Language Operator Hooks
+
+Event-driven automation for Claude Code in Language Operator development.
+
+## Available Hooks
+
+- [skill-activation-prompt](skill-activation-prompt.ts) - Automatically suggests relevant skills based on user prompts
+
+## Setup
+
+The hooks are pre-configured and should work automatically. If you encounter issues:
+
+```bash
+cd .claude/hooks
+npm install
+chmod +x *.sh
+```
+
+## How It Works
+
+When you submit a prompt to Claude, the `UserPromptSubmit` hook runs and:
+
+1. Analyzes your prompt for keywords and intent patterns
+2. Matches against skill trigger rules in `../skills/skill-rules.json`
+3. Displays recommendations like:
+
+```
+🎯 SKILL ACTIVATION CHECK
+📚 RECOMMENDED SKILLS:
+  → ruby-gem-development - Ruby gem development patterns
+  → thor-cli-development - CLI development patterns
+
+💡 ACTION: Consider using the Skill tool to activate relevant skills
+```
+
+## Testing
+
+To test the hook manually:
+
+```bash
+cd .claude/hooks
+echo '{"prompt": "create a gem feature", "cwd": ".", "session_id": "test", "transcript_path": "", "permission_mode": "ask"}' | npx tsx skill-activation-prompt.ts
+```

data/.claude/hooks/node_modules/.bin/esbuild

@@ -0,0 +1 @@
+../esbuild/bin/esbuild

data/.claude/hooks/node_modules/.bin/tsc

@@ -0,0 +1 @@
+../typescript/bin/tsc

data/.claude/hooks/node_modules/.bin/tsserver

@@ -0,0 +1 @@
+../typescript/bin/tsserver

data/.claude/hooks/node_modules/.bin/tsx

@@ -0,0 +1 @@
+../tsx/dist/cli.mjs

data/.claude/hooks/node_modules/.package-lock.json

@@ -0,0 +1,136 @@
+{
+  "name": "hooks",
+  "version": "1.0.0",
+  "lockfileVersion": 3,
+  "requires": true,
+  "packages": {
+    "node_modules/@esbuild/linux-x64": {
+      "version": "0.27.2",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.27.2.tgz",
+      "integrity": "sha512-uwp2Tip5aPmH+NRUwTcfLb+W32WXjpFejTIOWZFw/v7/KnpCDKG66u4DLcurQpiYTiYwQ9B7KOeMJvLCu/OvbA==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@types/node": {
+      "version": "25.0.3",
+      "resolved": "https://registry.npmjs.org/@types/node/-/node-25.0.3.tgz",
+      "integrity": "sha512-W609buLVRVmeW693xKfzHeIV6nJGGz98uCPfeXI1ELMLXVeKYZ9m15fAMSaUPBHYLGFsVRcMmSCksQOrZV9BYA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "undici-types": "~7.16.0"
+      }
+    },
+    "node_modules/esbuild": {
+      "version": "0.27.2",
+      "resolved": "https://registry.npmjs.org/esbuild/-/esbuild-0.27.2.tgz",
+      "integrity": "sha512-HyNQImnsOC7X9PMNaCIeAm4ISCQXs5a5YasTXVliKv4uuBo1dKrG0A+uQS8M5eXjVMnLg3WgXaKvprHlFJQffw==",
+      "hasInstallScript": true,
+      "license": "MIT",
+      "bin": {
+        "esbuild": "bin/esbuild"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "optionalDependencies": {
+        "@esbuild/aix-ppc64": "0.27.2",
+        "@esbuild/android-arm": "0.27.2",
+        "@esbuild/android-arm64": "0.27.2",
+        "@esbuild/android-x64": "0.27.2",
+        "@esbuild/darwin-arm64": "0.27.2",
+        "@esbuild/darwin-x64": "0.27.2",
+        "@esbuild/freebsd-arm64": "0.27.2",
+        "@esbuild/freebsd-x64": "0.27.2",
+        "@esbuild/linux-arm": "0.27.2",
+        "@esbuild/linux-arm64": "0.27.2",
+        "@esbuild/linux-ia32": "0.27.2",
+        "@esbuild/linux-loong64": "0.27.2",
+        "@esbuild/linux-mips64el": "0.27.2",
+        "@esbuild/linux-ppc64": "0.27.2",
+        "@esbuild/linux-riscv64": "0.27.2",
+        "@esbuild/linux-s390x": "0.27.2",
+        "@esbuild/linux-x64": "0.27.2",
+        "@esbuild/netbsd-arm64": "0.27.2",
+        "@esbuild/netbsd-x64": "0.27.2",
+        "@esbuild/openbsd-arm64": "0.27.2",
+        "@esbuild/openbsd-x64": "0.27.2",
+        "@esbuild/openharmony-arm64": "0.27.2",
+        "@esbuild/sunos-x64": "0.27.2",
+        "@esbuild/win32-arm64": "0.27.2",
+        "@esbuild/win32-ia32": "0.27.2",
+        "@esbuild/win32-x64": "0.27.2"
+      }
+    },
+    "node_modules/get-tsconfig": {
+      "version": "4.13.0",
+      "resolved": "https://registry.npmjs.org/get-tsconfig/-/get-tsconfig-4.13.0.tgz",
+      "integrity": "sha512-1VKTZJCwBrvbd+Wn3AOgQP/2Av+TfTCOlE4AcRJE72W1ksZXbAx8PPBR9RzgTeSPzlPMHrbANMH3LbltH73wxQ==",
+      "license": "MIT",
+      "dependencies": {
+        "resolve-pkg-maps": "^1.0.0"
+      },
+      "funding": {
+        "url": "https://github.com/privatenumber/get-tsconfig?sponsor=1"
+      }
+    },
+    "node_modules/resolve-pkg-maps": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/resolve-pkg-maps/-/resolve-pkg-maps-1.0.0.tgz",
+      "integrity": "sha512-seS2Tj26TBVOC2NIc2rOe2y2ZO7efxITtLZcGSOnHHNOQ7CkiUBfw0Iw2ck6xkIhPwLhKNLS8BO+hEpngQlqzw==",
+      "license": "MIT",
+      "funding": {
+        "url": "https://github.com/privatenumber/resolve-pkg-maps?sponsor=1"
+      }
+    },
+    "node_modules/tsx": {
+      "version": "4.21.0",
+      "resolved": "https://registry.npmjs.org/tsx/-/tsx-4.21.0.tgz",
+      "integrity": "sha512-5C1sg4USs1lfG0GFb2RLXsdpXqBSEhAaA/0kPL01wxzpMqLILNxIxIOKiILz+cdg/pLnOUxFYOR5yhHU666wbw==",
+      "license": "MIT",
+      "dependencies": {
+        "esbuild": "~0.27.0",
+        "get-tsconfig": "^4.7.5"
+      },
+      "bin": {
+        "tsx": "dist/cli.mjs"
+      },
+      "engines": {
+        "node": ">=18.0.0"
+      },
+      "optionalDependencies": {
+        "fsevents": "~2.3.3"
+      }
+    },
+    "node_modules/typescript": {
+      "version": "5.9.3",
+      "resolved": "https://registry.npmjs.org/typescript/-/typescript-5.9.3.tgz",
+      "integrity": "sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "bin": {
+        "tsc": "bin/tsc",
+        "tsserver": "bin/tsserver"
+      },
+      "engines": {
+        "node": ">=14.17"
+      }
+    },
+    "node_modules/undici-types": {
+      "version": "7.16.0",
+      "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-7.16.0.tgz",
+      "integrity": "sha512-Zz+aZWSj8LE6zoxD+xrjh4VfkIG8Ya6LvYkZqtUQGJPZjYl53ypCaUwWqo7eI0x66KBGeRo+mlBEkMSeSZ38Nw==",
+      "dev": true,
+      "license": "MIT"
+    }
+  }
+}

data/.claude/hooks/node_modules/@esbuild/linux-x64/README.md

@@ -0,0 +1,3 @@
+# esbuild
+
+This is the Linux 64-bit binary for esbuild, a JavaScript bundler and minifier. See https://github.com/evanw/esbuild for details.

data/.claude/hooks/node_modules/@esbuild/linux-x64/package.json

@@ -0,0 +1,20 @@
+{
+  "name": "@esbuild/linux-x64",
+  "version": "0.27.2",
+  "description": "The Linux 64-bit binary for esbuild, a JavaScript bundler.",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/evanw/esbuild.git"
+  },
+  "license": "MIT",
+  "preferUnplugged": true,
+  "engines": {
+    "node": ">=18"
+  },
+  "os": [
+    "linux"
+  ],
+  "cpu": [
+    "x64"
+  ]
+}

data/.claude/hooks/node_modules/@types/node/LICENSE

@@ -0,0 +1,21 @@
+    MIT License
+
+    Copyright (c) Microsoft Corporation.
+
+    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

data/.claude/hooks/node_modules/@types/node/README.md

@@ -0,0 +1,15 @@
+# Installation
+> `npm install --save @types/node`
+
+# Summary
+This package contains type definitions for node (https://nodejs.org/).
+
+# Details
+Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node.
+
+### Additional Details
+ * Last updated: Tue, 16 Dec 2025 21:35:18 GMT
+ * Dependencies: [undici-types](https://npmjs.com/package/undici-types)
+
+# Credits
+These definitions were written by [Microsoft TypeScript](https://github.com/Microsoft), [Alberto Schiabel](https://github.com/jkomyno), [Andrew Makarov](https://github.com/r3nya), [Benjamin Toueg](https://github.com/btoueg), [David Junger](https://github.com/touffy), [Mohsen Azimi](https://github.com/mohsen1), [Nikita Galkin](https://github.com/galkin), [Sebastian Silbermann](https://github.com/eps1lon), [Wilco Bakker](https://github.com/WilcoBakker), [Marcin Kopacz](https://github.com/chyzwar), [Trivikram Kamat](https://github.com/trivikr), [Junxiao Shi](https://github.com/yoursunny), [Ilia Baryshnikov](https://github.com/qwelias), [ExE Boss](https://github.com/ExE-Boss), [Piotr Błażejewicz](https://github.com/peterblazejewicz), [Anna Henningsen](https://github.com/addaleax), [Victor Perin](https://github.com/victorperin), [NodeJS Contributors](https://github.com/NodeJS), [Linus Unnebäck](https://github.com/LinusU), [wafuwafu13](https://github.com/wafuwafu13), [Matteo Collina](https://github.com/mcollina), [Dmitry Semigradsky](https://github.com/Semigradsky), [René](https://github.com/Renegade334), and [Yagiz Nizipli](https://github.com/anonrig).

data/.claude/hooks/node_modules/@types/node/assert/strict.d.ts

@@ -0,0 +1,105 @@
+/**
+ * In strict assertion mode, non-strict methods behave like their corresponding
+ * strict methods. For example, `assert.deepEqual()` will behave like
+ * `assert.deepStrictEqual()`.
+ *
+ * In strict assertion mode, error messages for objects display a diff. In legacy
+ * assertion mode, error messages for objects display the objects, often truncated.
+ *
+ * To use strict assertion mode:
+ *
+ * ```js
+ * import { strict as assert } from 'node:assert';
+ * ```
+ *
+ * ```js
+ * import assert from 'node:assert/strict';
+ * ```
+ *
+ * Example error diff:
+ *
+ * ```js
+ * import { strict as assert } from 'node:assert';
+ *
+ * assert.deepEqual([[[1, 2, 3]], 4, 5], [[[1, 2, '3']], 4, 5]);
+ * // AssertionError: Expected inputs to be strictly deep-equal:
+ * // + actual - expected ... Lines skipped
+ * //
+ * //   [
+ * //     [
+ * // ...
+ * //       2,
+ * // +     3
+ * // -     '3'
+ * //     ],
+ * // ...
+ * //     5
+ * //   ]
+ * ```
+ *
+ * To deactivate the colors, use the `NO_COLOR` or `NODE_DISABLE_COLORS`
+ * environment variables. This will also deactivate the colors in the REPL. For
+ * more on color support in terminal environments, read the tty
+ * [`getColorDepth()`](https://nodejs.org/docs/latest-v25.x/api/tty.html#writestreamgetcolordepthenv) documentation.
+ * @since v15.0.0
+ * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/assert/strict.js)
+ */
+declare module "node:assert/strict" {
+    import {
+        Assert,
+        AssertionError,
+        AssertionErrorOptions,
+        AssertOptions,
+        AssertPredicate,
+        AssertStrict,
+        deepStrictEqual,
+        doesNotMatch,
+        doesNotReject,
+        doesNotThrow,
+        fail,
+        ifError,
+        match,
+        notDeepStrictEqual,
+        notStrictEqual,
+        ok,
+        partialDeepStrictEqual,
+        rejects,
+        strictEqual,
+        throws,
+    } from "node:assert";
+    function strict(value: unknown, message?: string | Error): asserts value;
+    namespace strict {
+        export {
+            Assert,
+            AssertionError,
+            AssertionErrorOptions,
+            AssertOptions,
+            AssertPredicate,
+            AssertStrict,
+            deepStrictEqual,
+            deepStrictEqual as deepEqual,
+            doesNotMatch,
+            doesNotReject,
+            doesNotThrow,
+            fail,
+            ifError,
+            match,
+            notDeepStrictEqual,
+            notDeepStrictEqual as notDeepEqual,
+            notStrictEqual,
+            notStrictEqual as notEqual,
+            ok,
+            partialDeepStrictEqual,
+            rejects,
+            strict,
+            strictEqual,
+            strictEqual as equal,
+            throws,
+        };
+    }
+    export = strict;
+}
+declare module "assert/strict" {
+    import strict = require("node:assert/strict");
+    export = strict;
+}