@vicoa/cli 1.3.11-linux-x64 → 1.3.11-win32-x64

package/bin/_internal/cryptography-46.0.7.dist-info/RECORD

@@ -1,7 +1,7 @@
 cryptography-46.0.7.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
 cryptography-46.0.7.dist-info/METADATA,sha256=zW5_rTueQjaDE9RZqkkUvVnzmJOCgUWgAhn7xhx1z_E,5748
 cryptography-46.0.7.dist-info/RECORD,,
-cryptography-46.0.7.dist-info/WHEEL,sha256=jkxrJemT4jZpYSr-u9xPalWqoow8benNmiXfjKXLlJw,108
+cryptography-46.0.7.dist-info/WHEEL,sha256=8hEf8NzM1FnmM77AjVt5h8nDuYkN3UqZ79LoIAHXeRE,95
 cryptography-46.0.7.dist-info/licenses/LICENSE,sha256=Pgx8CRqUi4JTO6mP18u0BDLW8amsv4X1ki0vmak65rs,197
 cryptography-46.0.7.dist-info/licenses/LICENSE.APACHE,sha256=qsc7MUj20dcRHbyjIJn2jSbGRMaBOuHk8F9leaomY_4,11360
 cryptography-46.0.7.dist-info/licenses/LICENSE.BSD,sha256=YCxMdILeZHndLpeTzaJ15eY9dz2s0eymiSMqtwCPtPs,1532
@@ -30,7 +30,7 @@ cryptography/hazmat/backends/openssl/__pycache__/backend.cpython-312.pyc,,
 cryptography/hazmat/backends/openssl/backend.py,sha256=tV5AxBoFJ2GfA0DMWSY-0TxQJrpQoexzI9R4Kybb--4,10215
 cryptography/hazmat/bindings/__init__.py,sha256=s9oKCQ2ycFdXoERdS1imafueSkBsL9kvbyfghaauZ9Y,180
 cryptography/hazmat/bindings/__pycache__/__init__.cpython-312.pyc,,
-cryptography/hazmat/bindings/_rust.abi3.so,sha256=f8-dHk3kk1Oj6Wn2qVM3eK-aq5PY-x4IrdN1jdLb2gM,12821472
+cryptography/hazmat/bindings/_rust.pyd,sha256=_lxM21US95L7D1s84M2MFIRhSFHVb_XR5yFSE-ueC8o,9121280
 cryptography/hazmat/bindings/_rust/__init__.pyi,sha256=KhqLhXFPArPzzJ7DYO9Fl8FoXB_BagAd_r4Dm_Ze9Xo,1257
 cryptography/hazmat/bindings/_rust/_openssl.pyi,sha256=mpNJLuYLbCVrd5i33FBTmWwL_55Dw7JPkSLlSX9Q7oI,230
 cryptography/hazmat/bindings/_rust/asn1.pyi,sha256=BrGjC8J6nwuS-r3EVcdXJB8ndotfY9mbQYOfpbPG0HA,354

package/bin/_internal/cryptography-46.0.7.dist-info/WHEEL

@@ -1,5 +1,4 @@
 Wheel-Version: 1.0
 Generator: maturin (1.9.4)
 Root-Is-Purelib: false
-Tag: cp311-abi3-manylinux_2_34_x86_64
-
+Tag: cp311-abi3-win_amd64

package/bin/_internal/email_validator-2.3.0.dist-info/RECORD

@@ -1,4 +1,4 @@
-../../../bin/email_validator,sha256=cU72Y3pxP73JTpzLFjJHWWFs5WJCcO2GmJiI6UVE1m4,205
+../../Scripts/email_validator.exe,sha256=dfqTCWW4TfIYrdVDW05rJd4TCxoMjE4EeDFYOCJBvLA,108363
 email_validator-2.3.0.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
 email_validator-2.3.0.dist-info/METADATA,sha256=Kpe4Hu_NhWvICwNG9H-i2AC5pDi_j5IxrgD-kx1cn7w,26006
 email_validator-2.3.0.dist-info/RECORD,,

package/bin/_internal/integrations/cli_wrappers/IMPORTANT_USE_CASES.md

@@ -1,33 +1,33 @@
-# Important Use Cases
-
-This document summarizes important use cases for testing whether the wrapper works.
-
-## Normal messages
-
-1. User message sent from UI should be sent and submitted to terminal 
-2. User message sent from terminal should be displayed in UI.
-3. Agent message from terminal should be displayed in UI.
-4. No duplicate of user or agent messages
-
-## Push Notifications
-
-5. Push notifications should be sent to user when agent completes a task, not while it is running.
-
-## Permission Requests
-
-6. Permission request response options should be properly displayed in UI.
-7. Selecting an option of permission request in UI should be sent to terminal.
-8. Selecting options like "No" of permission request response options, it should be able to send new messages from UI to terminal. 
-
-## Control Messages
-
-e.g. interruption, change permission mode, change model, change agent, etc.  
-
-9. Interrupt the agent from UI while it is busy.
-10. User messages sent while agent is busy should be handled directly, control messages are processed, other messages are send to the terminal directly. 
-11. Permission mode changes in terminal is reflected in UI with a response.
-12. Permission mode changes from UI should be reflected in terminal.
-
-## Close Terminal
-
+# Important Use Cases
+
+This document summarizes important use cases for testing whether the wrapper works.
+
+## Normal messages
+
+1. User message sent from UI should be sent and submitted to terminal 
+2. User message sent from terminal should be displayed in UI.
+3. Agent message from terminal should be displayed in UI.
+4. No duplicate of user or agent messages
+
+## Push Notifications
+
+5. Push notifications should be sent to user when agent completes a task, not while it is running.
+
+## Permission Requests
+
+6. Permission request response options should be properly displayed in UI.
+7. Selecting an option of permission request in UI should be sent to terminal.
+8. Selecting options like "No" of permission request response options, it should be able to send new messages from UI to terminal. 
+
+## Control Messages
+
+e.g. interruption, change permission mode, change model, change agent, etc.  
+
+9. Interrupt the agent from UI while it is busy.
+10. User messages sent while agent is busy should be handled directly, control messages are processed, other messages are send to the terminal directly. 
+11. Permission mode changes in terminal is reflected in UI with a response.
+12. Permission mode changes from UI should be reflected in terminal.
+
+## Close Terminal
+
 13. Closing the terminal should update the session status.

package/bin/_internal/integrations/github/claude-code-action/CLAUDE.md

@@ -1,136 +1,136 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Development Tools
-
-- Runtime: Bun 1.2.11
-- TypeScript with strict configuration
-
-## Common Development Tasks
-
-### Available npm/bun scripts from package.json:
-
-```bash
-# Test
-bun test
-
-# Formatting
-bun run format          # Format code with prettier
-bun run format:check    # Check code formatting
-
-# Type checking
-bun run typecheck       # Run TypeScript type checker
-```
-
-## Architecture Overview
-
-This is a GitHub Action that enables Claude to interact with GitHub PRs and issues. The action operates in two main phases:
-
-### Phase 1: Preparation (`src/entrypoints/prepare.ts`)
-
-1. **Authentication Setup**: Establishes GitHub token via OIDC or GitHub App
-2. **Permission Validation**: Verifies actor has write permissions
-3. **Trigger Detection**: Uses mode-specific logic to determine if Claude should respond
-4. **Context Creation**: Prepares GitHub context and initial tracking comment
-
-### Phase 2: Execution (`base-action/`)
-
-The `base-action/` directory contains the core Claude Code execution logic, which serves a dual purpose:
-
-- **Standalone Action**: Published separately as `@anthropic-ai/claude-code-base-action` for direct use
-- **Inner Logic**: Used internally by this GitHub Action after preparation phase completes
-
-Execution steps:
-
-1. **MCP Server Setup**: Installs and configures GitHub MCP server for tool access
-2. **Prompt Generation**: Creates context-rich prompts from GitHub data
-3. **Claude Integration**: Executes via multiple providers (Anthropic API, AWS Bedrock, Google Vertex AI)
-4. **Result Processing**: Updates comments and creates branches/PRs as needed
-
-### Key Architectural Components
-
-#### Mode System (`src/modes/`)
-
-- **Tag Mode** (`tag/`): Responds to `@claude` mentions and issue assignments
-- **Agent Mode** (`agent/`): Direct execution when explicit prompt is provided
-- Extensible registry pattern in `modes/registry.ts`
-
-#### GitHub Integration (`src/github/`)
-
-- **Context Parsing** (`context.ts`): Unified GitHub event handling
-- **Data Fetching** (`data/fetcher.ts`): Retrieves PR/issue data via GraphQL/REST
-- **Data Formatting** (`data/formatter.ts`): Converts GitHub data to Claude-readable format
-- **Branch Operations** (`operations/branch.ts`): Handles branch creation and cleanup
-- **Comment Management** (`operations/comments/`): Creates and updates tracking comments
-
-#### MCP Server Integration (`src/mcp/`)
-
-- **GitHub Actions Server** (`github-actions-server.ts`): Workflow and CI access
-- **GitHub Comment Server** (`github-comment-server.ts`): Comment operations
-- **GitHub File Operations** (`github-file-ops-server.ts`): File system access
-- Auto-installation and configuration in `install-mcp-server.ts`
-
-#### Authentication & Security (`src/github/`)
-
-- **Token Management** (`token.ts`): OIDC token exchange and GitHub App authentication
-- **Permission Validation** (`validation/permissions.ts`): Write access verification
-- **Actor Validation** (`validation/actor.ts`): Human vs bot detection
-
-### Project Structure
-
-```
-src/
-├── entrypoints/           # Action entry points
-│   ├── prepare.ts         # Main preparation logic
-│   ├── update-comment-link.ts  # Post-execution comment updates
-│   └── format-turns.ts    # Claude conversation formatting
-├── github/               # GitHub integration layer
-│   ├── api/              # REST/GraphQL clients
-│   ├── data/             # Data fetching and formatting
-│   ├── operations/       # Branch, comment, git operations
-│   ├── validation/       # Permission and trigger validation
-│   └── utils/            # Image downloading, sanitization
-├── modes/                # Execution modes
-│   ├── tag/              # @claude mention mode
-│   ├── agent/            # Automation mode
-│   └── registry.ts       # Mode selection logic
-├── mcp/                  # MCP server implementations
-├── prepare/              # Preparation orchestration
-└── utils/                # Shared utilities
-```
-
-## Important Implementation Notes
-
-### Authentication Flow
-
-- Uses GitHub OIDC token exchange for secure authentication
-- Supports custom GitHub Apps via `APP_ID` and `APP_PRIVATE_KEY`
-- Falls back to official Claude GitHub App if no custom app provided
-
-### MCP Server Architecture
-
-- Each MCP server has specific GitHub API access patterns
-- Servers are auto-installed in `~/.claude/mcp/github-{type}-server/`
-- Configuration merged with user-provided MCP config via `mcp_config` input
-
-### Mode System Design
-
-- Modes implement `Mode` interface with `shouldTrigger()` and `prepare()` methods
-- Registry validates mode compatibility with GitHub event types
-- Agent mode triggers when explicit prompt is provided
-
-### Comment Threading
-
-- Single tracking comment updated throughout execution
-- Progress indicated via dynamic checkboxes
-- Links to job runs and created branches/PRs
-- Sticky comment option for consolidated PR comments
-
-## Code Conventions
-
-- Use Bun-specific TypeScript configuration with `moduleResolution: "bundler"`
-- Strict TypeScript with `noUnusedLocals` and `noUnusedParameters` enabled
-- Prefer explicit error handling with detailed error messages
-- Use discriminated unions for GitHub context types
-- Implement retry logic for GitHub API operations via `utils/retry.ts`
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Development Tools
+
+- Runtime: Bun 1.2.11
+- TypeScript with strict configuration
+
+## Common Development Tasks
+
+### Available npm/bun scripts from package.json:
+
+```bash
+# Test
+bun test
+
+# Formatting
+bun run format          # Format code with prettier
+bun run format:check    # Check code formatting
+
+# Type checking
+bun run typecheck       # Run TypeScript type checker
+```
+
+## Architecture Overview
+
+This is a GitHub Action that enables Claude to interact with GitHub PRs and issues. The action operates in two main phases:
+
+### Phase 1: Preparation (`src/entrypoints/prepare.ts`)
+
+1. **Authentication Setup**: Establishes GitHub token via OIDC or GitHub App
+2. **Permission Validation**: Verifies actor has write permissions
+3. **Trigger Detection**: Uses mode-specific logic to determine if Claude should respond
+4. **Context Creation**: Prepares GitHub context and initial tracking comment
+
+### Phase 2: Execution (`base-action/`)
+
+The `base-action/` directory contains the core Claude Code execution logic, which serves a dual purpose:
+
+- **Standalone Action**: Published separately as `@anthropic-ai/claude-code-base-action` for direct use
+- **Inner Logic**: Used internally by this GitHub Action after preparation phase completes
+
+Execution steps:
+
+1. **MCP Server Setup**: Installs and configures GitHub MCP server for tool access
+2. **Prompt Generation**: Creates context-rich prompts from GitHub data
+3. **Claude Integration**: Executes via multiple providers (Anthropic API, AWS Bedrock, Google Vertex AI)
+4. **Result Processing**: Updates comments and creates branches/PRs as needed
+
+### Key Architectural Components
+
+#### Mode System (`src/modes/`)
+
+- **Tag Mode** (`tag/`): Responds to `@claude` mentions and issue assignments
+- **Agent Mode** (`agent/`): Direct execution when explicit prompt is provided
+- Extensible registry pattern in `modes/registry.ts`
+
+#### GitHub Integration (`src/github/`)
+
+- **Context Parsing** (`context.ts`): Unified GitHub event handling
+- **Data Fetching** (`data/fetcher.ts`): Retrieves PR/issue data via GraphQL/REST
+- **Data Formatting** (`data/formatter.ts`): Converts GitHub data to Claude-readable format
+- **Branch Operations** (`operations/branch.ts`): Handles branch creation and cleanup
+- **Comment Management** (`operations/comments/`): Creates and updates tracking comments
+
+#### MCP Server Integration (`src/mcp/`)
+
+- **GitHub Actions Server** (`github-actions-server.ts`): Workflow and CI access
+- **GitHub Comment Server** (`github-comment-server.ts`): Comment operations
+- **GitHub File Operations** (`github-file-ops-server.ts`): File system access
+- Auto-installation and configuration in `install-mcp-server.ts`
+
+#### Authentication & Security (`src/github/`)
+
+- **Token Management** (`token.ts`): OIDC token exchange and GitHub App authentication
+- **Permission Validation** (`validation/permissions.ts`): Write access verification
+- **Actor Validation** (`validation/actor.ts`): Human vs bot detection
+
+### Project Structure
+
+```
+src/
+├── entrypoints/           # Action entry points
+│   ├── prepare.ts         # Main preparation logic
+│   ├── update-comment-link.ts  # Post-execution comment updates
+│   └── format-turns.ts    # Claude conversation formatting
+├── github/               # GitHub integration layer
+│   ├── api/              # REST/GraphQL clients
+│   ├── data/             # Data fetching and formatting
+│   ├── operations/       # Branch, comment, git operations
+│   ├── validation/       # Permission and trigger validation
+│   └── utils/            # Image downloading, sanitization
+├── modes/                # Execution modes
+│   ├── tag/              # @claude mention mode
+│   ├── agent/            # Automation mode
+│   └── registry.ts       # Mode selection logic
+├── mcp/                  # MCP server implementations
+├── prepare/              # Preparation orchestration
+└── utils/                # Shared utilities
+```
+
+## Important Implementation Notes
+
+### Authentication Flow
+
+- Uses GitHub OIDC token exchange for secure authentication
+- Supports custom GitHub Apps via `APP_ID` and `APP_PRIVATE_KEY`
+- Falls back to official Claude GitHub App if no custom app provided
+
+### MCP Server Architecture
+
+- Each MCP server has specific GitHub API access patterns
+- Servers are auto-installed in `~/.claude/mcp/github-{type}-server/`
+- Configuration merged with user-provided MCP config via `mcp_config` input
+
+### Mode System Design
+
+- Modes implement `Mode` interface with `shouldTrigger()` and `prepare()` methods
+- Registry validates mode compatibility with GitHub event types
+- Agent mode triggers when explicit prompt is provided
+
+### Comment Threading
+
+- Single tracking comment updated throughout execution
+- Progress indicated via dynamic checkboxes
+- Links to job runs and created branches/PRs
+- Sticky comment option for consolidated PR comments
+
+## Code Conventions
+
+- Use Bun-specific TypeScript configuration with `moduleResolution: "bundler"`
+- Strict TypeScript with `noUnusedLocals` and `noUnusedParameters` enabled
+- Prefer explicit error handling with detailed error messages
+- Use discriminated unions for GitHub context types
+- Implement retry logic for GitHub API operations via `utils/retry.ts`