active_module 0.6.1 → 0.6.2

data/vendor/bundle/ruby/4.0.0/gems/mcp-0.8.0/AGENTS.md

@@ -1,107 +0,0 @@
-# AGENTS.md
-
-## Project overview
-
-This is the official Ruby SDK for the Model Context Protocol (MCP), implementing both server and client functionality for JSON-RPC 2.0 based communication between LLM applications and context providers.
-
-## Dev environment setup
-
-- Ruby 3.2.0+ required to run the full test suite, including all Sorbet-related features
-- Run `bundle install` to install dependencies
-- Dependencies: `json-schema` >= 4.1 - Schema validation
-
-## Build and test commands
-
-- `bundle install` - Install dependencies
-- `rake test` - Run all tests
-- `rake rubocop` - Run linter
-- `rake` - Run tests and linting (default task)
-- `ruby -I lib -I test test/path/to/specific_test.rb` - Run single test file
-- `gem build mcp.gemspec` - Build the gem
-
-## Testing instructions
-
-- Test files are in `test/` directory with `_test.rb` suffix
-- Run full test suite with `rake test`
-- Run individual tests with `ruby -I lib -I test test/path/to/file_test.rb`
-- Tests should pass before submitting PRs
-
-## Code style guidelines
-
-- Follow RuboCop rules (run `rake rubocop`)
-- Use frozen string literals
-- Follow Ruby community conventions
-- Keep dependencies minimal
-
-## Commit message conventions
-
-- Use conventional commit format when possible
-- Include clear, descriptive commit messages
-- Releases are triggered by updating version in `lib/mcp/version.rb` and merging to main
-
-## Release process
-
-- Follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format in CHANGELOG.md
-- Update CHANGELOG.md before cutting releases
-- Use git history and PR merge commits to construct changelog entries
-- Format entries as: "Terse description of the change (#nnn)"
-- Keep entries in flat list format (no nesting)
-- Git tags mark commits that cut new releases
-- Exclude maintenance PRs that don't concern end users
-- Check upstream remote for PRs if available
-
-## Architecture overview
-
-### Core Components
-
-**MCP::Server** (`lib/mcp/server.rb`):
-
-- Main server class handling JSON-RPC requests
-- Implements MCP protocol methods: initialize, ping, tools/list, tools/call, prompts/list, prompts/get, resources/list, resources/read
-- Supports custom method registration via `define_custom_method`
-- Handles instrumentation, exception reporting, and notifications
-- Uses JsonRpcHandler for request processing
-
-**MCP::Client** (`lib/mcp/client.rb`):
-
-- Client interface for communicating with MCP servers
-- Transport-agnostic design with pluggable transport layers
-- Supports tool listing and invocation
-
-**Transport Layer**:
-
-- `MCP::Server::Transports::StdioTransport` - Command-line stdio transport
-- `MCP::Server::Transports::StreamableHttpTransport` - HTTP with streaming support
-- `MCP::Client::HTTP` - HTTP client transport (requires faraday gem)
-
-**Protocol Components**:
-
-- `MCP::Tool` - Tool definition with input/output schemas and annotations
-- `MCP::Prompt` - Prompt templates with argument validation
-- `MCP::Resource` - Resource registration and retrieval
-- `MCP::Configuration` - Global configuration with exception reporting and instrumentation
-
-### Key Patterns
-
-**Three Ways to Define Components**:
-
-1. Class inheritance (e.g., `class MyTool < MCP::Tool`)
-2. Define methods (e.g., `MCP::Tool.define(name: "my_tool") { ... }`)
-3. Server registration (e.g., `server.define_tool(name: "my_tool") { ... }`)
-
-**Schema Validation**:
-
-- Tools support input_schema and output_schema for JSON Schema validation
-- Protocol version 2025-03-26+ supports tool annotations (destructive_hint, idempotent_hint, etc.)
-- Validation is configurable via `configuration.validate_tool_call_arguments`
-
-**Context Passing**:
-
-- `server_context` hash passed through tool/prompt calls for request-specific data
-- Methods can accept `server_context:` keyword argument for accessing context
-
-### Integration patterns
-
-- **Rails controllers**: Use `server.handle_json(request.body.read)` for HTTP endpoints
-- **Command-line tools**: Use `StdioTransport.new(server).open` for CLI applications
-- **HTTP services**: Use `StreamableHttpTransport` for web-based servers

data/vendor/bundle/ruby/4.0.0/gems/mcp-0.8.0/CHANGELOG.md

@@ -1,168 +0,0 @@
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [Unreleased]
-
-## [0.8.0] - 2026-03-03
-
-### Added
-
-- `Content::EmbeddedResource` class for embedded resource content type (#244)
-- `Content::Audio` class for audio content type (#243)
-- `$ref` support in `Tool::Schema` for protocol version 2025-11-25 (#242)
-- MCP conformance test suite (#248)
-
-### Fixed
-
-- Handle `Errno::ECONNRESET` in SSE stream operations (#249)
-- Fix default handler return values to comply with MCP spec (#247)
-- Fix `Prompt#validate_arguments!` crash when arguments are `nil` (#246)
-- Return 202 Accepted for SSE responses per MCP spec (#245)
-- Fix `Content::Image#to_h` to return `mimeType` (camelCase) per MCP spec (#241)
-
-## [0.7.1] - 2026-02-21
-
-### Fixed
-
-- Fix `Resource::Contents#to_h` to use correct property names per MCP spec (#235)
-- Return JSON-RPC protocol errors for unknown tool calls (#231)
-- Fix `logging/setLevel` to return empty hash per MCP specification (#230)
-
-## [0.7.0] - 2026-02-14
-
-### Added
-
-- `logging` support (#103)
-- Protocol version negotiation to server initialization (#223)
-- Tool arguments to instrumentation data (#218)
-- Client info to instrumentation callback (#221)
-- `resource_templates` to `MCP::Client` (#225)
-
-### Changed
-
-- Extract `MCP::Annotations` into a dedicated file (#224)
-
-### Fixed
-
-- `Resource::Embedded` not setting `@resource` in `initialize` (#220)
-
-## [0.6.0] - 2026-01-16
-
-### Changed
-
-- Update licensing to Apache 2.0 for new contributions (#213)
-
-### Fixed
-
-- Omit `icons` from responses when empty or nil to reduce context window usage (#212)
-
-## [0.5.0] - 2026-01-11
-
-### Added
-
-- Protocol specification version "2025-11-25" support (#184)
-- `icons` parameter support (#205)
-- `websiteUrl` parameter in `serverInfo` (#188)
-- `description` parameter in `serverInfo` (#201)
-- `additionalProperties` support for schema validation (#198)
-- "Draft" protocol version to supported versions (#179)
-- `stateless` mode for high availability (#101)
-- Exception messages for tool call errors (#194)
-- Elicitation skeleton (#178)
-- `prompts/list` and `prompts/get` support to client (#163)
-- Accept header validation for HTTP client transport (#207)
-- Ruby 2.7 - Ruby 3.1 support (#206)
-
-### Changed
-
-- Make tool names stricter (#204)
-
-### Fixed
-
-- Symlink path comparison in schema validation (#193)
-- Duplicate tool names across namespaces now raise an error (#199)
-- Tool error handling to follow MCP spec (#165)
-- XSS vulnerability in json_rpc_handler (#175)
-
-## [0.4.0] - 2025-10-15
-
-### Added
-
-- Client resources support with `resources/list` and `resources/read` methods (#160)
-- `_meta` field support for Tool schema (#124)
-- `_meta` field support for Prompt
-- `title` field support for prompt arguments
-- `call_tool_raw` method to client for accessing full tool responses (#149)
-- Structured content support in tool responses (#147)
-- AGENTS.md development guidance documentation (#134)
-- Dependabot configuration for automated dependency updates (#138)
-
-### Changed
-
-- Set default `content` to empty array instead of `nil` (#150)
-- Improved prompt spec compliance (#153)
-- Allow output schema to be array of objects (#144)
-- Return 202 response code for accepted JSON-RPC notifications (#114)
-- Added validation to `MCP::Configuration` setters (#145)
-- Updated metaschema URI format for cross-OS compatibility
-
-### Fixed
-
-- Client tools functionality and test coverage (#166)
-- Client resources test for empty responses (#162)
-- Documentation typos and incorrect examples (#157, #146)
-- Removed redundant transport requires (#154)
-- Cleaned up unused block parameters and magic comments
-
-## [0.3.0] - 2025-09-14
-
-### Added
-
-- Tool output schema support with comprehensive validation (#122)
-- HTTP client transport layer for MCP clients (#28)
-- Tool annotations validation for protocol compatibility (#122)
-- Server instructions support (#87)
-- Title support in server info (#119)
-- Default values for tool annotation hints (#118)
-- Notifications/initialized method implementation (#84)
-
-### Changed
-
-- Make default protocol version the latest specification version (#83)
-- Protocol version validation to ensure valid values (#80)
-- Improved tool handling for tools with no arguments (#85, #86)
-- Better error handling and response API (#109)
-
-### Fixed
-
-- JSON-RPC notification format in Streamable HTTP transport (#91)
-- Errors when title is not specified (#126)
-- Tools with missing arguments handling (#86)
-- Namespacing issues in README examples (#89)
-
-## [0.2.0] - 2025-07-15
-
-### Added
-
-- Custom methods support via `define_custom_method` (#75)
-- Streamable HTTP transport implementation (#33)
-- Tool argument validation against schemas (#43)
-
-### Changed
-
-- Server context is now optional for Tools and Prompts (#54)
-- Improved capability handling and removed automatic capability determination (#61, #63)
-- Refactored architecture in preparation for client support (#27)
-
-### Fixed
-
-- Input schema validation for schemas without required fields (#73)
-- Error handling when sending notifications (#70)
-
-## [0.1.0] - 2025-05-30
-
-Initial release in collaboration with Shopify

data/vendor/bundle/ruby/4.0.0/gems/mcp-0.8.0/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at topher.bullock@shopify.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/vendor/bundle/ruby/4.0.0/gems/mcp-0.8.0/Gemfile

@@ -1,29 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-# Specify runtime dependencies in the gemspec
-gemspec
-
-# Specify development dependencies below
-gem "rubocop-minitest", require: false
-gem "rubocop-rake", require: false
-gem "rubocop-shopify", ">= 2.18", require: false if RUBY_VERSION >= "3.1"
-
-gem "puma", ">= 5.0.0"
-gem "rackup", ">= 2.1.0"
-
-gem "activesupport"
-# Fix io-console install error when Ruby 3.0.
-gem "debug" if RUBY_VERSION >= "3.1"
-gem "rake", "~> 13.0"
-gem "sorbet-static-and-runtime" if RUBY_VERSION >= "3.0"
-gem "yard", "~> 0.9"
-gem "yard-sorbet", "~> 0.9" if RUBY_VERSION >= "3.1"
-
-group :test do
-  gem "faraday", ">= 2.0"
-  gem "minitest", "~> 5.1", require: false
-  gem "mocha"
-  gem "webmock"
-end

data/vendor/bundle/ruby/4.0.0/gems/mcp-0.8.0/LICENSE

@@ -1,216 +0,0 @@
-The MCP project is undergoing a licensing transition from the MIT License to the Apache License, Version 2.0 ("Apache-2.0"). All new code and specification contributions to the project are licensed under Apache-2.0. Documentation contributions (excluding specifications) are licensed under CC-BY-4.0.
-
-Contributions for which relicensing consent has been obtained are licensed under Apache-2.0. Contributions made by authors who originally licensed their work under the MIT License and who have not yet granted explicit permission to relicense remain licensed under the MIT License.
-
-No rights beyond those granted by the applicable original license are conveyed for such contributions.
-
----
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to the Licensor for inclusion in the Work by the copyright
-      owner or by an individual or Legal Entity authorized to submit on behalf
-      of the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
----
-
-MIT License
-
-Copyright (c) 2024-2025 Model Context Protocol a Series of LF Projects, LLC.
-
-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.
-
----
-
-Creative Commons Attribution 4.0 International (CC-BY-4.0)
-
-Documentation in this project (excluding specifications) is licensed under
-CC-BY-4.0. See https://creativecommons.org/licenses/by/4.0/legalcode for
-the full license text.