rosett-ai 1.3.3 → 1.5.10

data/QUICKSTART.md

@@ -1,73 +0,0 @@
-# Quick Start
-
-Get from zero to your first compiled rules in 5 minutes.
-
-## 1. Install
-
-```bash
-sudo dpkg -i nncc_1.0.0-1_amd64.deb
-sudo apt-get install -f   # resolve dependencies
-```
-
-## 2. Initialize
-
-```bash
-# Set up global ~/.claude/ structure
-rai init --global
-
-# (Optional) Set up project-local structure
-rai init --local
-```
-
-## 3. Create a behaviour rule
-
-```bash
-rai behaviour manage add my_first_rule
-```
-
-Edit the created file at `conf/behaviour/my_first_rule.yml`:
-
-```yaml
-name: my_first_rule
-description: My first rai behaviour rule
-version: 1.0.0
-author: your_name
-created_at: "2026-01-01"
-modified_at: "2026-01-01"
-modified_by: your_name
-sensitive: false
-used_in: []
-rules:
-  - id: rule_001
-    description: Always explain your reasoning before making changes
-    priority: 50
-    enabled: true
-```
-
-## 4. Compile
-
-```bash
-# Preview what would change
-rai compile --simulate --verbose
-
-# Compile rules to ~/.claude/rules/
-rai compile --verbose
-```
-
-## 5. Verify
-
-```bash
-# Check the generated files
-ls ~/.claude/rules/
-
-# Validate everything is consistent
-rai validate
-```
-
-## Next Steps
-
-- `rai compile --engine generic` to compile for non-Claude tools
-- `rai design list` to explore design documents
-- `rai adopt --verbose` to analyze your existing rules
-- `man raictl` for the full manual
-- See [INSTALL.md](INSTALL.md) for detailed installation options

data/Rakefile

@@ -1,200 +0,0 @@
-# frozen_string_literal: true
-
-# SPDX-License-Identifier: GPL-3.0-only
-# Copyright (C) 2026 Hugo Antonio Sepulveda Manriquez / NeatNerds
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-require 'rubocop/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-RuboCop::RakeTask.new
-
-desc 'Run reek smell detector'
-task :reek do
-  sh 'bundle', 'exec', 'reek', 'lib/rosett_ai.rb', 'lib/rosett_ai/'
-end
-
-desc 'Check dependency licenses for GPL-3.0 compatibility'
-task :licenses do
-  sh 'bundle', 'exec', 'license_finder'
-end
-
-desc 'Detect potentially uncalled methods'
-task :debride do
-  sh 'bundle', 'exec', 'debride', '-w', '.debride_whitelist', 'lib/'
-end
-
-desc 'Audit dependencies for known vulnerabilities'
-task :bundler_audit do
-  sh 'bundle', 'exec', 'bundler-audit', 'check', '--update'
-end
-
-desc 'Detect structural code duplication'
-task :flay do
-  sh 'bundle', 'exec', 'flay', '--mass', '16', 'lib/'
-end
-
-desc 'Run all quality gates'
-task quality: [:spec, :rubocop, :reek, :licenses, :debride, :bundler_audit, :fasterer, :flay]
-
-task default: :quality
-
-namespace :docs do
-  desc 'Update all documentation'
-  task :update do
-    require_relative 'lib/rosett_ai'
-    RosettAi::Thor::Tasks::Documentation.new.update
-  end
-
-  desc 'Check documentation status'
-  task :status do
-    require_relative 'lib/rosett_ai'
-    RosettAi::Thor::Tasks::Documentation.new.status
-  end
-end
-
-namespace :man do
-  desc 'Build man pages from ronn source'
-  task :build do
-    require 'ronn'
-    source = File.expand_path('doc/man/rai.1.ronn', __dir__)
-    output_dir = File.expand_path('man/man1', __dir__)
-    FileUtils.mkdir_p(output_dir)
-
-    doc = Ronn::Document.new(source)
-    File.write(File.join(output_dir, 'rai.1'), doc.to_roff)
-    puts 'Generated man/man1/rai.1'
-  end
-end
-
-begin
-  require 'yard'
-  YARD::Rake::YardocTask.new(:yard) do |t|
-    t.files = ['lib/**/*.rb']
-    t.options = ['--output-dir', 'doc/api', '--markup', 'markdown', '--no-private']
-  end
-rescue LoadError
-  desc 'Generate YARD documentation (yard gem not installed)'
-  task(:yard) { warn 'yard gem is not installed. Run: gem install yard' }
-end
-
-desc 'Generate CHANGELOG.md from conventional commits (requires git-cliff)'
-task :changelog do
-  unless system('which git-cliff > /dev/null 2>&1')
-    warn 'git-cliff is not installed. See: https://git-cliff.org/docs/installation'
-    exit 1
-  end
-  system('git-cliff', '--config', 'cliff.toml', '--output', 'CHANGELOG.md') || exit(1)
-  puts 'Generated CHANGELOG.md'
-end
-
-desc 'Run fasterer performance suggestions'
-task :fasterer do
-  require 'fasterer/cli'
-  Fasterer::CLI.execute
-rescue LoadError
-  warn 'fasterer gem is not installed. Run: gem install fasterer'
-end
-
-namespace :behaviour do
-  desc 'Validate all behaviour files'
-  task :validate do
-    require_relative 'lib/rosett_ai'
-    RosettAi::Thor::Tasks::Behaviour.new.validate
-  end
-
-  desc 'List all behaviour files'
-  task :list do
-    require_relative 'lib/rosett_ai'
-    RosettAi::Thor::Tasks::Behaviour.new.list
-  end
-end
-
-namespace :build do
-  desc 'Build core .deb package (variant: core, gtk4, qt6)'
-  task :package, [:variant] do |_t, args|
-    require_relative 'lib/rosett_ai'
-    # Trigger Zeitwerk autoload of Build (which defines BuildPackage)
-    RosettAi::Thor::Tasks::Build # rubocop:disable Lint/Void
-    opts = build_package_opts(args)
-    RosettAi::Thor::Tasks::BuildPackage.new([], opts).invoke(:create)
-  end
-
-  desc 'Build engine plugin .deb package'
-  task :engine do
-    require_relative 'lib/rosett_ai'
-    RosettAi::Thor::Tasks::Build # rubocop:disable Lint/Void
-    RosettAi::Thor::Tasks::BuildEngine.new.invoke(:create)
-  end
-end
-
-# Build option flags from Rake args and environment variables.
-# Usage:
-#   rake build:package                          # defaults
-#   rake build:package[gtk4]                    # variant only
-#   rake build:package VERBOSE=1 CLEAN=1        # flags via env
-#   rake build:package[gtk4] VERBOSE=1 CLEAN=1  # both
-def build_package_opts(args)
-  opts = {}
-  opts[:variant] = args[:variant] if args[:variant]
-  opts[:verbose] = true if ENV['VERBOSE']
-  opts[:clean] = true if ENV['CLEAN']
-  opts[:ruby_version] = ENV['RUBY_VERSION'] if ENV['RUBY_VERSION']
-  opts[:architecture] = ENV['ARCHITECTURE'] if ENV['ARCHITECTURE']
-  opts[:output_dir] = ENV['OUTPUT_DIR'] if ENV['OUTPUT_DIR']
-  opts[:build_iteration] = ENV['BUILD_ITERATION'].to_i if ENV['BUILD_ITERATION']
-  opts
-end
-
-namespace :release do
-  desc 'Prepare release (level: major, minor, patch)'
-  task :prepare, [:level] do |_t, args|
-    require_relative 'lib/rosett_ai'
-    RosettAi::Thor::Tasks::Release.new.invoke(:prepare, [args[:level] || 'patch'])
-  end
-
-  desc 'Create annotated git tag from current VERSION'
-  task :tag do
-    require_relative 'lib/rosett_ai'
-    RosettAi::Thor::Tasks::Release.new.invoke(:tag)
-  end
-
-  desc 'Show release status (version, last tag, unreleased commits)'
-  task :status do
-    require_relative 'lib/rosett_ai'
-    RosettAi::Thor::Tasks::Release.new.invoke(:status)
-  end
-end
-
-namespace :readme do
-  desc 'Update README version, test count, and engine count from live sources'
-  task :update do
-    require_relative 'lib/rosett_ai/version'
-    require 'json'
-
-    readme_path = File.expand_path('README.md', __dir__)
-    content = File.read(readme_path)
-
-    # Version from constant
-    version = RosettAi::VERSION
-    content.gsub!(%r{<!-- rai:version -->.*?<!-- /rai:version -->},
-                  "<!-- rai:version -->#{version}<!-- /rai:version -->")
-
-    # Test count via rspec --dry-run (COVERAGE=false suppresses SimpleCov noise in stdout)
-    env = { 'COVERAGE' => 'false' }
-    json_output = IO.popen(env, ['bundle', 'exec', 'rspec', '--dry-run', '--format', 'json'],
-                           err: File::NULL, &:read)
-    test_count = JSON.parse(json_output).dig('summary', 'example_count')
-    content.gsub!(%r{<!-- rai:tests -->.*?<!-- /rai:tests -->},
-                  "<!-- rai:tests -->#{test_count} RSpec specs<!-- /rai:tests -->")
-
-    # Engine count from target profiles
-    engine_count = Dir[File.expand_path('conf/targets/*.yml', __dir__)].size
-    content.gsub!(%r{<!-- rai:engines -->\d+<!-- /rai:engines -->},
-                  "<!-- rai:engines -->#{engine_count}<!-- /rai:engines -->")
-
-    File.write(readme_path, content)
-    puts "README.md updated: v#{version}, #{test_count} specs, #{engine_count} engines"
-  end
-end

data/SECURITY.md

@@ -1,114 +0,0 @@
-# Security Policy
-
-## Scope
-
-This policy covers the following NeatNerds open-source projects:
-
-- **Rosett-AI** (raictl) --- the core CLI and compiler
-- **rosett-ai-engine-\*** --- all official engine adapter gems
-- **auditor-mcp** --- InSpec MCP server
-- **openvox-mcp** --- OpenVox MCP server
-- **neatspec** --- Compliance-as-a-Service wrapper
-
-Third-party forks and community plugins are outside this scope unless
-they ship under the `neatnerds` GitLab namespace.
-
-## Supported Versions
-
-| Version | Supported |
-|---------|-----------|
-| Latest release | Yes |
-| Previous minor | Security fixes only |
-| Older | No |
-
-Only the latest tagged release and the immediately preceding minor
-release receive security patches. If you are running an older version,
-please upgrade before reporting.
-
-## Reporting a Vulnerability
-
-**Do not open a public issue for security vulnerabilities.**
-
-### Email (primary channel --- no account required)
-
-Send an email to **security@neatnerds.be** with:
-
-1. Affected project and version
-2. Description of the vulnerability
-3. Steps to reproduce (proof-of-concept if possible)
-4. Impact assessment (what an attacker could achieve)
-
-Email is the primary reporting channel. It requires no account, no
-registration, and no prior relationship with the project. Anyone who
-discovers a vulnerability can report it immediately.
-
-You may optionally encrypt your report using the PGP key for
-`security@neatnerds.be`, available on
-[keys.openpgp.org](https://keys.openpgp.org). Search for the email
-address to retrieve the public key.
-
-### GitLab Confidential Issue (alternative --- requires account)
-
-If you already have an account on our self-hosted GitLab instance
-(`gitlab.neatnerds.be`), you may open a **confidential** issue on
-the affected project's repository instead. Mark it confidential
-before submitting and use the `Security` issue template.
-
-This channel is mainly useful for existing contributors and
-community members who already have access. If you do not have an
-account, use the email channel above --- do not create an account
-solely to report a vulnerability.
-
-## Response Timeline
-
-| Stage | Target |
-|-------|--------|
-| Acknowledgement | 48 hours |
-| Initial assessment | 7 calendar days |
-| Fix or mitigation | 90 calendar days |
-
-If we cannot meet a target, we will communicate the revised timeline
-in the acknowledgement or assessment response.
-
-## Disclosure Policy
-
-We follow **coordinated disclosure**:
-
-1. The reporter and maintainers agree on a disclosure date (default:
-   90 days after the initial report).
-2. A fix is developed and tested in a private branch.
-3. The fix is released, and a security advisory is published on
-   the same day.
-4. The reporter is credited in the advisory (unless they request
-   anonymity).
-
-We will never disclose a vulnerability before a fix is available
-unless active exploitation is detected in the wild.
-
-## Credit
-
-We gratefully acknowledge security researchers who report
-vulnerabilities responsibly. Unless you request otherwise, your name
-(or handle) and a link to your profile will appear in the security
-advisory and the CHANGELOG entry for the fix.
-
-## Security Advisories
-
-| ID | Date | Severity | Summary |
-|----|------|----------|---------|
-| [NNSA-2026-001](https://gitlab.neatnerds.be/foss/rosett-ai/rosett-ai/-/issues/2) | 2026-04-18 | Medium | Session data included in v1.2.0 gem package. Yanked. Fixed in v1.3.0+. |
-
-## Security Best Practices for Contributors
-
-All contributions must follow these rules (enforced by CI and
-overcommit hooks):
-
-- Use `YAML.safe_load` exclusively --- never `YAML.load`
-- Use array-form `system()` calls --- never string interpolation
-  in shell commands
-- Write files only to whitelisted directories
-- Set 0600 permissions on any file containing secrets
-- Never log secrets or credentials
-- Validate all external input before use
-- Include `# SPDX-License-Identifier: GPL-3.0-only` in every
-  Ruby source file

data/cliff.toml

@@ -1,52 +0,0 @@
-# git-cliff configuration for NeatNerds Code Companion
-# Generates Keep a Changelog 1.1.0 formatted CHANGELOG from conventional commits.
-#
-# Reference: https://git-cliff.org/docs/configuration
-
-[changelog]
-header = """
-# Changelog
-
-All notable changes to the NeatNerds Code Companion (nncc) are documented in this file.
-
-Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).\n
-"""
-
-body = """
-{% if version %}\
-    ## [{{ version | trim_start_matches(pat="v") }}] - {{ timestamp | date(format="%Y-%m-%d") }}
-{% else %}\
-    ## [Unreleased]
-{% endif %}\
-{% for group, commits in commits | group_by(attribute="group") %}
-    ### {{ group | striptags | trim | upper_first }}
-    {% for commit in commits %}
-        - {% if commit.scope %}**{{ commit.scope }}:** {% endif %}\
-            {{ commit.message | split(pat=":") | last | trim | upper_first }}\
-    {% endfor %}
-{% endfor -%}
-"""
-
-footer = ""
-trim = true
-
-[git]
-conventional_commits = true
-filter_unconventional = false
-split_commits = false
-protect_breaking_commits = false
-filter_commits = false
-tag_pattern = "v[0-9].*"
-sort_commits = "oldest"
-commit_parsers = [
-  { message = "^feat", group = "<!-- 0 -->Added" },
-  { message = "^fix", group = "<!-- 1 -->Fixed" },
-  { message = "^refactor", group = "<!-- 2 -->Changed" },
-  { message = "^perf", group = "<!-- 2 -->Changed" },
-  { message = "^docs", group = "<!-- 3 -->Documentation" },
-  { message = "^chore\\(release\\)", skip = true },
-  { message = "^chore", group = "<!-- 4 -->Other" },
-  { message = "^ci", group = "<!-- 4 -->Other" },
-  { message = "^test", group = "<!-- 5 -->Other" },
-  { body = ".*", group = "<!-- 6 -->Other" },
-]

data/conf/design/aaif_alignment.yml

@@ -1,181 +0,0 @@
----
-name: aaif_alignment
-domain: core
-version: 0.1.0
-status: implemented
-priority: 2
-author: hugo
-created_at: "2026-02-24"
-modified_at: "2026-03-16"
-modified_by: claude
-depends_on:
-  - security
-  - architecture
-  - compiler
-  - mcp_integration
-  - error_handling
-#
-intent: |
-  Position rosett-ai as a standards-compliant tool within the Agentic AI Foundation (AAIF)
-  ecosystem by implementing AAIF-governed protocols and compilation targets.
-
-  The AAIF (Linux Foundation, Dec 2025) governs three founding projects:
-  - MCP (Anthropic) — protocol for AI-tool integration
-  - AGENTS.md (OpenAI) — vendor-neutral project instruction files
-  - goose (Block) — open-source AI agent framework
-
-  raictl fills a gap none of these projects address: structured, validated, versioned,
-  auditable configuration management for AI agent workflows. This document defines
-  how rosett-ai integrates with the AAIF ecosystem without losing its core value proposition.
-
-  Key alignments:
-  1. AGENTS.md as a compilation target (alongside CLAUDE.md and generic)
-  2. MCP as the integration protocol (see mcp_integration.yml)
-  3. Vendor-neutral multi-agent support (Claude, Goose, Cursor, Copilot, etc.)
-  4. Potential AAIF project contribution pathway
-
-  AAIF contribution pathway:
-  - Recommended: modular extraction (rosett-ai-mcp as Apache-2.0, core stays GPL-3.0)
-  - Timeline: build MCP integration first, extract after validation, pitch at MCP Dev Summit NYC (April 2-3, 2026)
-  - License tension: AAIF projects use Apache-2.0/MIT; GPL-3.0 is copyleft outlier
-  - Open-core model survives relicensing (content packs are data, not derivative works)
-
-  This design document is part of the AAIF Alignment epic (P2).
-#
-constraints:
-  - AGENTS.md compilation must produce valid, idiomatic Markdown (no YAML frontmatter unless spec adds it)
-  - AGENTS.md output must be readable by all 21+ compatible tools listed on agents.md
-  - Multi-target compilation must not degrade existing CLAUDE.md output quality
-  - Vendor-neutral features must not break Claude Code specific features
-  - AAIF spec tracking must be explicit — pin to known spec versions, not "latest"
-  - No AAIF-specific code paths that circumvent security constraints from security.yml
-  - No code may be contributed to AAIF without a documented license compatibility assessment
-  - AGENTS.md files must be compilable from the same YAML sources as CLAUDE.md
-  - Goose .goosehints format support is optional — only add if demand exists
-  - Any AAIF governance participation must be documented in project decisions log
-#
-acceptance_criteria:
-  - 'bin/raictl compile --engine agents_md produces valid AGENTS.md file'
-  - AGENTS.md output includes all enabled behaviours, properly sectioned by domain
-  - AGENTS.md output is tested against at least 3 tools (manual verification with Claude Code, Goose, Cursor)
-  - Compiler target registry includes agents_md alongside claude, generic, and model-specific targets
-  - Design documents reference AAIF spec versions explicitly (MCP 2025-03-26, AGENTS.md v0.1.0)
-  - Multi-agent configuration support documented with examples for Claude Code, Goose, and generic agents
-  - AAIF ecosystem positioning documented in project README or CONTRIBUTING.md
-  - Compilation lockfile tracks AGENTS.md output alongside existing targets
-  - conf/targets/agents_md.yml target profile exists with format-specific compilation rules
-  - Modular extraction plan documented for Rosett-AI-mcp (Apache-2.0) contribution pathway
-  - License compatibility matrix maintained for AAIF contribution scenarios
-  - AAIF governance participation options documented (Silver member vs project donation)
-  - Compliance differentiator (CRA/NIS2/DORA) integrated into MCP admin capabilities
-#
-examples:
-  - scenario: "User compiles behaviours to AGENTS.md format"
-    expected: |
-      $ bin/raictl compile --engine agents_md --verbose
-      Compiling 12 behaviours to AGENTS.md format...
-      Output: AGENTS.md (project root)
-      Sections: Project Overview, Build & Test, Code Style, Security, Testing
-      Format: Standard Markdown with ## headings per domain
-    not: "Output contains YAML, JSON Schema references, or rosett-ai-internal metadata"
-  - scenario: "User compiles for multiple targets simultaneously"
-    expected: |
-      $ bin/raictl compile --engine claude --engine agents_md
-      Compiling to ~/.claude/rules/ (claude target)
-      Compiling to ./AGENTS.md (agents_md target)
-      Both outputs reflect the same source behaviours with format-appropriate rendering.
-    not: "One target's compilation affects the other's output"
-  - scenario: "User wants to use rosett-ai with Goose instead of Claude Code"
-    expected: |
-      $ bin/raictl compile --engine agents_md
-      Creates AGENTS.md file. Goose reads it as hints (alongside .goosehints).
-      User can also configure rosett-ai as an MCP server in Goose's config.yaml.
-    not: "User must maintain separate configuration for each AI agent"
-  - scenario: "AAIF updates the MCP spec from 2025-03-26 to a newer revision"
-    expected: |
-      raictl tracks spec version in conf/targets/ and mcp_integration design doc.
-      Maintainer reviews changelog, updates pinned version, runs compatibility tests.
-      Release notes document spec version bump.
-    not: "rosett-ai silently breaks on spec change or auto-adopts unreviewed spec versions"
-  - scenario: "Preparing rosett-ai-mcp for AAIF contribution"
-    expected: |
-      1. MCP integration built and tested within rosett-ai (GPL-3.0)
-      2. MCP admin module extracted as rosett-ai-mcp (relicensed Apache-2.0)
-      3. rosett-ai-mcp has own repo, CI, tests, README, GOVERNANCE.md
-      4. Pitched at MCP Dev Summit NYC (April 2-3, 2026)
-      5. If accepted: project hosted under AAIF, copyright to LF Projects, LLC
-      Core rosett-ai remains GPL-3.0 with open-core content model intact.
-    not: "Full rosett-ai donated, GPL-3.0 abandoned, open-core model compromised"
-  - scenario: "AAIF contribution not accepted, continuing independently"
-    expected: |
-      raictl continues as independent project using AAIF standards (MCP, AGENTS.md).
-      Optional: join as Silver member for ecosystem participation without project donation.
-      MCP integration and AGENTS.md compilation still provide value regardless.
-    not: "Project abandoned because AAIF didn't accept it"
-  - scenario: "Evaluating license options for AAIF contribution"
-    expected: |
-      Options evaluated:
-      1. Relicense to Apache-2.0 (content model survives, copyleft lost)
-      2. Dual-license GPL-3.0 + Apache-2.0 (complex but preserves both)
-      3. Extract MCP only as Apache-2.0 (recommended — clean separation)
-      4. Participate as member without donation (keep full control)
-      Decision documented in project decisions log with rationale.
-    not: "License changed without evaluating impact on open-core model"
-  - scenario: "User asks about AAIF compliance status"
-    expected: |
-      $ bin/raictl status --aaif
-      AAIF Alignment Status:
-        MCP Server: enabled (spec 2025-03-26, mcp gem 0.7.1)
-        AGENTS.md: supported (compiled target)
-        CLAUDE.md: supported (compiled target, primary)
-        Goose hints: not supported (planned)
-    not: "No visibility into AAIF ecosystem alignment"
-#
-anti_patterns:
-  - Treating AGENTS.md as a structured format (it is deliberately unstructured Markdown)
-  - Adding AAIF-specific fields to the core behaviour YAML schema (keep source format neutral)
-  - Coupling compilation logic to a single AAIF project (MCP, AGENTS.md, goose are independent)
-  - Auto-updating to new AAIF spec versions without maintainer review
-  - Claiming AAIF compliance or endorsement without actual contribution/acceptance
-  - Ignoring AGENTS.md security concerns (hidden Unicode injection, prompt injection via Markdown)
-  - Duplicating behaviour content across targets instead of compiling from single source
-  - Assuming AGENTS.md will gain a formal schema (design for current unstructured format)
-  - Donating full rosett-ai to AAIF without extracting MCP component first (loses GPL-3.0 protection)
-  - Relicensing core rosett-ai to Apache-2.0 without evaluating open-core model impact
-  - Claiming AAIF membership or endorsement before formal acceptance
-  - Pitching "AI agent config compiler" without the MCP admin angle (too narrow for AAIF)
-  - Ignoring the compliance differentiator (CRA/NIS2/DORA) — this is the strongest enterprise pitch
-#
-gui_notes: |
-  Document interactions (cross-references):
-
-  1. mcp_integration.yml: MCP is the integration protocol. AAIF alignment
-     governs the strategic positioning; MCP integration handles the technical
-     implementation.
-
-  2. compiler.yml: AGENTS.md is a compilation target alongside CLAUDE.md
-     and generic. Target profile: conf/targets/agents_md.yml.
-
-  3. security.yml: AGENTS.md output must not contain hidden Unicode injection
-     or prompt injection patterns.
-
-  4. licensing_system.yml: license compatibility assessment for AAIF
-     contribution (Apache-2.0 vs GPL-3.0 tension).
-
-  5. comply.yml: CRA/NIS2/DORA compliance is the enterprise differentiator
-     for AAIF pitch.
-
-  6. error_handling.yml: exit codes and structured errors for compilation
-     targets.
-#
-preferences:
-  language: ruby
-  patterns:
-    - "Compiler target pattern (AGENTS.md as target)"
-    - "Adapter pattern for format-specific rendering"
-    - "Strategy pattern for multi-target compilation"
-  testing: rspec with AGENTS.md output validation, multi-target compilation
-    tests, and spec version pinning verification
-  gems:
-    - json_schemer
-    - thor