rosett-ai 1.3.3

data/doc/decisions/009-core-only-v1-release.md

@@ -0,0 +1,60 @@
+# ADR-009: Core-Only v1.0.0 Release
+
+## Status
+
+Accepted (2026-03-04)
+
+## Context
+
+raictl v1.0.0 includes 10 engines, D-Bus service, GTK4 desktop app, and all
+supporting infrastructure. The gemspec declares `ruby-dbus` (~> 0.24) and
+`i3ipc` (~> 0.3) as runtime dependencies, but these are only used by the
+desktop and D-Bus modules:
+
+- `ruby-dbus`: `lib/rosett_ai/dbus/`, `lib/rosett_ai/desktop/dbus_client.rb`
+- `i3ipc`: `lib/rosett_ai/dbus/focus_adapters/i3_adapter.rb`
+
+These gems pull in native extensions and system library dependencies
+(`libgirepository1.0-dev` for GObject introspection) that are irrelevant
+for users who only want the CLI compiler. Installing rosett-ai on a headless
+CI runner or server should not require D-Bus development libraries.
+
+The `adwaita` gem (GTK4 desktop UI) is already in a separate `:desktop`
+Bundler group in the Gemfile and excluded from CI. But `ruby-dbus` and
+`i3ipc` are in the gemspec itself, making them mandatory for all installs.
+
+## Decision
+
+Release v1.0.0 as **core-only**:
+
+1. Move `ruby-dbus` and `i3ipc` from `rosett-ai.gemspec` to the `:desktop`
+   group in `Gemfile` (with `require: false`).
+2. Add `loader.ignore` calls in `lib/rosett_ai.rb` to prevent Zeitwerk from
+   autoloading `rosett-ai/dbus` and `rosett-ai/desktop` when `ruby-dbus` is
+   unavailable.
+3. Desktop CLI commands (`dbus start/stop`, `desktop gtk4`) print a
+   clear error message directing users to the `rosett-ai-gtk4` package.
+4. The `.deb` package (`nncc_1.0.0-1_amd64.deb`) ships as core-only.
+   Desktop features will be available via a separate `rosett-ai-gtk4` package.
+
+## Consequences
+
+### Positive
+
+- Core rosett-ai installs cleanly on headless systems (CI, servers, containers)
+- No native extension compilation required for core functionality
+- Cleaner dependency tree for the core `.deb` package
+- Desktop components can evolve on their own release cadence
+
+### Negative
+
+- Users who previously ran `gem install rosett-ai` and used D-Bus features
+  will need to install `rosett-ai-gtk4` separately (no v0.x release exists,
+  so no actual migration impact)
+- Two packages to maintain instead of one
+
+### Neutral
+
+- All 10 engines remain in core (they have no desktop dependencies)
+- Desktop specs are excluded from core-only test runs but remain in
+  the full test suite

data/doc/decisions/010-engine-debian-packaging.md

@@ -0,0 +1,66 @@
+# ADR 010: Engine Debian Packaging
+
+| Field    | Value                |
+|----------|----------------------|
+| Status   | Accepted             |
+| Date     | 2026-03-07           |
+| Authors  | Hugo Sepulveda       |
+
+## Context
+
+The rosett-ai core package bundles an embedded Ruby runtime at `/opt/rosett-ai/embedded/`.
+Engine gems (e.g. `rosett-ai-engine-claude`, `rosett-ai-engine-ollama`) are separate
+repositories with their own gemspecs. During development, the core Gemfile
+referenced them via `path: '../rosett-ai-engine-*'`, which:
+
+1. Caused `bundle install --deployment` to fail in the staging tree (the sibling
+   directories don't exist after `rsync` copies the project).
+2. Contradicted the pluggable architecture — engines should be independently
+   installable, not embedded in the core package.
+
+## Decision
+
+Each engine gem is packaged as its own `.deb` (architecture: `all`, since they
+are pure Ruby) that installs into the rosett-ai embedded Ruby's gem directory:
+
+```text
+/opt/rosett-ai/embedded/lib/ruby/gems/3.3.10/
+```
+
+This allows the existing `Gem.find_files('rosett_ai_engine/*/register.rb')` discovery
+mechanism to find engine plugins at runtime without any changes to the core.
+
+### Core Gemfile
+
+The core `Gemfile` no longer references engine gems. A `Gemfile.dev` (gitignored)
+is provided for developers who need cross-repo testing.
+
+### Build Script
+
+A reusable `packaging/build-engine-deb.sh` script in the core repo accepts
+`ENGINE_NAME` and `ENGINE_VERSION` environment variables. Each engine repo
+contains a thin `packaging/build-deb.sh` wrapper that sets these variables and
+delegates to the core script.
+
+### Dependencies
+
+Engine `.deb` packages declare `Depends: rosett-ai (>= 1.0.0)`. Engine-specific
+runtime dependencies (e.g. `anthropic` for rosett-ai-engine-claude) are declared in
+the engine's gemspec as `add_dependency`.
+
+## Consequences
+
+- Users install engines independently: `dpkg -i rosett-ai-engine-claude_1.0.0-1_all.deb`
+- Engine updates don't require rebuilding the core package
+- The core `.deb` is smaller and builds faster (no engine gems bundled)
+- Developers use `BUNDLE_GEMFILE=Gemfile.dev bundle install` for local testing
+- Engine gem dependencies are resolved at gem install time within the engine
+  `.deb` build, not at core build time
+
+## Alternatives Considered
+
+1. **Bundle all engines in core** — rejected: inflates package size, couples
+   release cycles, contradicts pluggable architecture.
+2. **APT repository with engine packages** — deferred: requires infrastructure
+   setup. The current approach produces `.deb` files that can be hosted in any
+   APT repo when ready.

data/doc/decisions/011-context-aware-cli.md

@@ -0,0 +1,71 @@
+# ADR 011: Context-Aware CLI
+
+| Field    | Value                |
+|----------|----------------------|
+| Status   | Accepted             |
+| Date     | 2026-03-08           |
+| Authors  | Hugo Sepulveda       |
+
+## Context
+
+rosett-ai's CLI was "rooted" to its own installation directory. Commands that read
+configuration (design, behaviour, compile, validate) hardcoded
+`RosettAi.root.join('conf', ...)` as the source path, which always resolved to
+rosett-ai's own `conf/` directory regardless of `Dir.pwd`. This made rosett-ai unusable
+as a per-project configuration management tool.
+
+Additionally, commands like `build`, `release`, `dbus`, and `desktop` are
+rosett-ai-internal development commands that clutter help output when invoked from
+any other project.
+
+## Decision
+
+### Project marker: `.rosett-ai/` directory
+
+A new `RosettAi::ProjectContext` class detects project context by walking up from
+`Dir.pwd` looking for a `.rosett-ai/` directory (following the `.git/`, `.vscode/`,
+`.idea/` convention).
+
+Project structure created by `rai init --project`:
+
+```text
+<project>/
+  .rosett-ai/
+    config.yml          # Project marker + config (project_name, default_engine)
+    conf/
+      behaviour/        # Project-specific behaviours
+      design/           # Project-specific design docs
+```
+
+### Path resolution
+
+- `RosettAi.conf_root` returns `.rosett-ai/` when inside a project, `RosettAi.root` otherwise
+- Content directories (design, behaviour, tooling) resolve relative to `conf_root`
+- Schemas always resolve from `RosettAi.root` (they are part of the tool, not the project)
+
+### Command visibility
+
+Internal commands (`build`, `release`, `documentation`, `dbus`, `desktop`) are:
+
+- Hidden from `raictl help` output outside the rosett-ai repository
+- Blocked with a clear error message when invoked directly
+
+Detection uses `ProjectContext#nncc_internal?` which returns true only when the
+detected project root equals `RosettAi.root`.
+
+## Alternatives Considered
+
+1. **`.rosett-ai.yml` file at project root** — Rejected because a hidden directory is
+   cleaner for housing multiple config files and subdirectories without cluttering
+   the project root.
+
+2. **Explicit `--project-dir` flag on every command** — Rejected because it
+   violates the "works like git" principle and creates a poor user experience.
+
+## Consequences
+
+- Users can run `rai init --project` to set up per-project configuration
+- `rai design list` from a project directory shows that project's design docs
+- `rai compile` from a project directory compiles that project's configuration
+- Internal commands remain accessible only from the rosett-ai repository itself
+- Backward compatible: rosett-ai's own repository continues to work unchanged

data/doc/dependency_decisions.yml

@@ -0,0 +1,247 @@
+---
+- - :permit
+  - MIT
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:57:51.797624521 Z
+- - :permit
+  - Apache-2.0
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:57:53.592238092 Z
+- - :permit
+  - Apache 2.0
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:57:55.699515625 Z
+- - :permit
+  - Apache License (2.0)
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:57:57.245428941 Z
+- - :permit
+  - Simplified BSD
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:57:58.814909858 Z
+- - :permit
+  - Simplified BSD, ruby
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:00.504702113 Z
+- - :permit
+  - BSD-2-Clause
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:02.105176116 Z
+- - :permit
+  - BSD-3-Clause
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:03.692853547 Z
+- - :permit
+  - ISC
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:05.306220200 Z
+- - :permit
+  - ruby
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:06.904808287 Z
+- - :permit
+  - GPL-2.0
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:08.496153636 Z
+- - :permit
+  - GPL-2.0-only
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:10.079398510 Z
+- - :permit
+  - GPL-2.0-or-later
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:11.741292936 Z
+- - :permit
+  - GPL-2.0-or-later, ruby
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:13.376744792 Z
+- - :permit
+  - GPL-3.0
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:14.955539712 Z
+- - :permit
+  - GPL-3.0-only
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:16.531696441 Z
+- - :permit
+  - GPL-3.0-or-later
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:18.149338796 Z
+- - :permit
+  - GPLv3
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:19.771117902 Z
+- - :permit
+  - LGPL-2.1
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:21.317632867 Z
+- - :permit
+  - LGPL-2.1-only
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:22.958385745 Z
+- - :permit
+  - LGPL-2.1-or-later
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:24.580793979 Z
+- - :permit
+  - LGPLv2+
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:26.719515734 Z
+- - :permit
+  - LGPL-3.0
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:28.353411296 Z
+- - :permit
+  - LGPL-3.0-only
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:29.972537844 Z
+- - :permit
+  - LGPL-3+
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:31.574701526 Z
+- - :permit
+  - LGPL-3.0+
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:33.196092605 Z
+- - :permit
+  - LGPL-3+, ruby
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:34.827384942 Z
+- - :permit
+  - LGPL-3.0+, ruby
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:36.496811805 Z
+- - :permit
+  - LGPLv3+, ruby
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:38.115625313 Z
+- - :permit
+  - Zlib
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:39.776177141 Z
+- - :permit
+  - 0BSD
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:41.355632019 Z
+- - :permit
+  - Unlicense
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:43.057876881 Z
+- - :permit
+  - Artistic-1.0-Perl, GPL-2.0-or-later, MIT
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:44.637292334 Z
+- - :permit
+  - MIT-like
+  - :who:
+    :why:
+    :versions: []
+    :when: 2026-03-18 19:58:46.185391276 Z
+- - :approve
+  - mutant
+  - :who:
+    :why: Proprietary EULA (Schirp DSO Ltd), dev-only dependency for mutation testing
+    :versions: []
+    :when: 2026-03-18 19:58:57.638272693 Z
+- - :approve
+  - mutant-rspec
+  - :who:
+    :why: Proprietary EULA, dev-only integration for mutation testing
+    :versions: []
+    :when: 2026-03-18 19:58:59.320586322 Z
+- - :approve
+  - stud
+  - :who:
+    :why: Unknown license, transitive dependency of fpm (build-only)
+    :versions: []
+    :when: 2026-03-18 19:59:00.975313332 Z
+- - :approve
+  - native-package-installer
+  - :who:
+    :why: LGPL-3+, GPL-3.0 compatible
+    :versions: []
+    :when: 2026-03-18 19:59:02.646765540 Z
+- - :approve
+  - locale
+  - :who:
+    :why: LGPLv3+ ruby, GPL-3.0 compatible
+    :versions: []
+    :when: 2026-03-18 19:59:04.292348554 Z
+- - :approve
+  - gettext
+  - :who:
+    :why: LGPL-3.0+ ruby, GPL-3.0 compatible
+    :versions: []
+    :when: 2026-03-18 19:59:05.925828383 Z
+- - :approve
+  - pkg-config
+  - :who:
+    :why: LGPLv2+, GPL-3.0 compatible
+    :versions: []
+    :when: 2026-03-18 19:59:07.596953695 Z

data/doc/issues/001-wrapper-missing-environment-variables.md

@@ -0,0 +1,197 @@
+# Issue 001: Wrapper script missing LD_LIBRARY_PATH and RUBYLIB
+
+| Field       | Value                                      |
+|-------------|--------------------------------------------|
+| Severity    | **Critical** (application fails to launch) |
+| Status      | **Resolved**                               |
+| Component   | `packaging/wrapper.sh.template`            |
+| Affects     | All builds (CI and local)                  |
+| Found in    | v1.0.0 (`nncc_1.0.0-1_amd64.deb`)         |
+| Resolved in | v1.1.0                                     |
+
+## Resolution
+
+Wrapper converted to `packaging/wrapper.sh.template` with `@@RUBY_ABI@@` and
+`@@RUBY_ARCH@@` placeholders. The `install_wrapper!` build stage now queries the
+just-compiled embedded Ruby for `RbConfig::CONFIG["ruby_version"]` and
+`RbConfig::CONFIG["arch"]`, substituting them at build time. The template sets
+`LD_LIBRARY_PATH`, `RUBYLIB`, `GEM_HOME`, and `GEM_PATH` with the correct paths,
+eliminating the chicken-and-egg `ruby -e` subprocess call.
+
+## Summary
+
+The runtime wrapper script (`/opt/rosett-ai/bin/raictl`) does not set `LD_LIBRARY_PATH`
+or `RUBYLIB`, causing two cascading failures that prevent the application from
+starting.
+
+## Symptoms
+
+```text
+$ raictl version
+`RubyGems' were not loaded.
+`error_highlight' was not loaded.
+`did_you_mean' was not loaded.
+`syntax_suggest' was not loaded.
+-e:1:in `<main>': uninitialized constant RbConfig (NameError)
+`RubyGems' were not loaded.
+...
+/opt/rosett-ai/app/bin/raictl:10:in `require': cannot load such file -- bundler/setup (LoadError)
+        from /opt/rosett-ai/app/bin/raictl:10:in `<main>'
+```
+
+## Root Cause Analysis
+
+### Failure 1: `libruby.so.3.3` not found
+
+The embedded Ruby binary at `/opt/rosett-ai/embedded/bin/ruby` links against
+`libruby.so.3.3` dynamically. Its ELF `RUNPATH` is set to `/usr/local/lib`
+(see [Issue 002](002-embedded-ruby-wrong-prefix.md) for why), but the actual
+library resides at `/opt/rosett-ai/embedded/lib/libruby.so.3.3`.
+
+**Evidence:**
+
+```text
+$ ldd /opt/rosett-ai/embedded/bin/ruby
+  libruby.so.3.3 => not found
+$ readelf -d /opt/rosett-ai/embedded/bin/ruby | grep RUNPATH
+  0x000000000000001d (RUNPATH)  Library runpath: [/usr/local/lib]
+$ ls /opt/rosett-ai/embedded/lib/libruby.so.3.3
+  /opt/rosett-ai/embedded/lib/libruby.so.3.3 -> libruby.so.3.3.10
+```
+
+The user discovered that `export LD_LIBRARY_PATH=/opt/rosett-ai/embedded/lib/`
+resolves this failure, but a second failure then emerges.
+
+### Failure 2: Ruby standard library not on `$LOAD_PATH`
+
+Even with `LD_LIBRARY_PATH` set, the Ruby binary's compiled-in `$LOAD_PATH`
+points to `/usr/local/lib/ruby/...` instead of `/opt/rosett-ai/embedded/lib/ruby/...`:
+
+```text
+$ LD_LIBRARY_PATH=/opt/rosett-ai/embedded/lib \
+  /opt/rosett-ai/embedded/bin/ruby -e 'puts $LOAD_PATH'
+/usr/local/lib/ruby/site_ruby/3.3.0
+/usr/local/lib/ruby/site_ruby/3.3.0/x86_64-linux
+/usr/local/lib/ruby/site_ruby
+/usr/local/lib/ruby/vendor_ruby/3.3.0
+/usr/local/lib/ruby/vendor_ruby/3.3.0/x86_64-linux
+/usr/local/lib/ruby/vendor_ruby
+/usr/local/lib/ruby/3.3.0
+/usr/local/lib/ruby/3.3.0/x86_64-linux
+```
+
+The actual standard library (including `rbconfig.rb`, `rubygems.rb`,
+`bundler.rb`) exists at `/opt/rosett-ai/embedded/lib/ruby/3.3.0/` but Ruby cannot
+find it. This causes:
+
+- `RbConfig` to be undefined (it requires `rbconfig.rb` from the stdlib)
+- RubyGems, error_highlight, did_you_mean, syntax_suggest all fail to load
+- `bundler/setup` cannot be required
+
+### Failure 3: Chicken-and-egg in GEM_HOME computation (line 11)
+
+The wrapper script runs this **before** the main `exec` call:
+
+```bash
+export GEM_HOME="${INSTALL_DIR}/embedded/lib/ruby/gems/$(${EMBEDDED_BIN}/ruby -e 'puts RbConfig::CONFIG["ruby_program_version"]')"
+```
+
+This subprocess invocation of `ruby` fails first (for the same reasons above),
+which causes the entire wrapper to abort due to `set -e`.
+
+## Proof: All failures resolved with correct environment
+
+Setting `LD_LIBRARY_PATH` and `RUBYLIB` makes the full application work:
+
+```bash
+$ LD_LIBRARY_PATH=/opt/rosett-ai/embedded/lib \
+  RUBYLIB=/opt/rosett-ai/embedded/lib/ruby/3.3.0:/opt/rosett-ai/embedded/lib/ruby/3.3.0/x86_64-linux \
+  GEM_HOME=/opt/rosett-ai/embedded/lib/ruby/gems/3.3.0 \
+  BUNDLE_GEMFILE=/opt/rosett-ai/app/Gemfile \
+  BUNDLE_PATH=/opt/rosett-ai/app/vendor/bundle \
+  BUNDLE_DEPLOYMENT=true \
+  /opt/rosett-ai/embedded/bin/ruby -I/opt/rosett-ai/app/lib /opt/rosett-ai/app/bin/raictl version
+1.0.0
+```
+
+## Proposed Fix
+
+Update `packaging/wrapper.sh` to set the missing environment variables and
+eliminate the chicken-and-egg `ruby` subprocess call:
+
+```bash
+#!/bin/bash
+# Rosett-AI - Runtime wrapper
+# Invoked as /opt/rosett-ai/bin/raictl, symlinked from /usr/local/bin/raictl
+set -e
+
+INSTALL_DIR="/opt/rosett-ai"
+EMBEDDED_DIR="${INSTALL_DIR}/embedded"
+EMBEDDED_BIN="${EMBEDDED_DIR}/bin"
+EMBEDDED_LIB="${EMBEDDED_DIR}/lib"
+APP_DIR="${INSTALL_DIR}/app"
+
+# Ensure the embedded Ruby can find libruby.so
+export LD_LIBRARY_PATH="${EMBEDDED_LIB}${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
+
+# Ensure the embedded Ruby can find its standard library
+export RUBYLIB="${EMBEDDED_LIB}/ruby/3.3.0:${EMBEDDED_LIB}/ruby/3.3.0/x86_64-linux${RUBYLIB:+:$RUBYLIB}"
+
+export PATH="${EMBEDDED_BIN}:${PATH}"
+export GEM_HOME="${EMBEDDED_LIB}/ruby/gems/3.3.0"
+export GEM_PATH="${GEM_HOME}"
+export BUNDLE_GEMFILE="${APP_DIR}/Gemfile"
+export BUNDLE_PATH="${APP_DIR}/vendor/bundle"
+export BUNDLE_DEPLOYMENT="true"
+
+cd "${APP_DIR}"
+exec "${EMBEDDED_BIN}/ruby" -I"${APP_DIR}/lib" "${APP_DIR}/bin/raictl" "$@"
+```
+
+### Key changes
+
+| Change | Rationale |
+|--------|-----------|
+| Add `LD_LIBRARY_PATH` | Ensures dynamic linker finds `libruby.so.3.3` |
+| Add `RUBYLIB` | Overrides compiled-in `$LOAD_PATH` to find stdlib |
+| Hardcode `gems/3.3.0` in `GEM_HOME` | Eliminates failing `ruby -e` subprocess call |
+
+### Trade-off: hardcoded version string
+
+The original wrapper dynamically queried `RbConfig::CONFIG["ruby_program_version"]`
+to avoid hardcoding `gems/3.3.0`. While elegant, this creates a circular
+dependency: Ruby must work before we can query Ruby for its version. Since the
+wrapper is generated at build time (see `install_wrapper!` in `build.rb`),
+the version string can be templated during the build stage instead. See the
+"Templated Wrapper" alternative below.
+
+### Alternative: Templated wrapper (preferred)
+
+Modify `install_wrapper!` in `lib/rosett_ai/thor/tasks/build.rb` to render the
+wrapper from an ERB template with build-time values:
+
+```ruby
+def install_wrapper!
+  template = packaging_dir.join('wrapper.sh.erb')
+  dest = staging_install.join('bin', 'rosett-ai')
+  content = ERB.new(template.read).result_with_hash(
+    ruby_abi_version: '3.3.0',
+    ruby_arch: 'x86_64-linux'
+  )
+  File.write(dest, content)
+  FileUtils.chmod(0o755, dest)
+end
+```
+
+This preserves the "no hardcoded version" design goal while avoiding the
+chicken-and-egg problem.
+
+## Affected Files
+
+- `packaging/wrapper.sh` (or new `packaging/wrapper.sh.erb`)
+- `lib/rosett_ai/thor/tasks/build.rb` (if using templated approach)
+
+## Related Issues
+
+- [002 - Embedded Ruby compiled with wrong prefix](002-embedded-ruby-wrong-prefix.md)
+- [003 - Smoke test installs system Ruby masking failures](003-smoke-test-false-positive.md)