rosett-ai 1.3.3 → 1.5.10

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '08b1ccbf26eade94ccc451962a789f73da5037aacd3fa3fba00d442a143c259c'
-  data.tar.gz: 85521d6653832bdded1ce46cd951d6fff0c21521695bc4ab1eaf88523bc6c1fd
+  metadata.gz: 9fc2d403485de8a1af9034d9f7bf19e7545620406b691b0c917e6e360ad9e56b
+  data.tar.gz: 89a8c039303808bed9f592e0f17d4478ffc87d34f129006a5981651c80bf82ac
 SHA512:
-  metadata.gz: eb06abe8951876cfb9a29c3966bead575439daca52e3d5dab67a4cab97560e54fe67dd6cfbcb6bde3a7ec800108acc44ff6aa587b13ad549b394f87e8f35a177
-  data.tar.gz: cc15e6fe802854c0ca427ae49a57a137d24f943a0b813a57ca809159b37215c37e1c5063ca54ff19b98740df5cb9b462f5cf597806ac4255f924fdf5b26c5e34
+  metadata.gz: 0254e2ea9ea0e3261863ec052e8987e8c45a645de615e9fd266a0ce6d861f90ce04f3c1b3f08ad4c9adc9e17fec951b026c4d01a24446dc69b6597aa7c97f7ed
+  data.tar.gz: c201357a747fa445901851484a17bbd5398b3be363bbbecaf8791a120768974a12b34c1a5cedc4173f6990b3ef470418c4ad818168537fdf176f2c2efda3f57e

data/CHANGELOG.md

@@ -6,6 +6,373 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.5.10] - 2026-07-08
+
+### Security
+
+- **publish:gem CI gate hardened** — `publish:gem` now declares `needs:` on
+  `audit:artifact`, `package:smoke-test`, and `package:gem-smoke-test` in
+  addition to the existing `audit:gem` gate. Gem publication is blocked until
+  both the `.gem` and `.deb` artifact audits pass and the install-parity smoke
+  tests succeed. Closes the DAG gap that allowed v1.5.9 to publish the gem
+  past failing audit and smoke-test jobs.
+
+- **publish:deb-push-aptly CI gate hardened** — adds `package:smoke-test`
+  to the existing `needs:` list so `.deb` publication is also blocked until
+  the postinst smoke test passes.
+
+## [1.5.9] - 2026-07-06
+
+### Security
+
+- **audit:gem CI gate** — adds a standalone `audit:gem` job (allowlist,
+  denylist, PII scan, gitleaks) wired as a `needs:` dependency of
+  `publish:gem`. Closes the DAG gap that let v1.5.8 publish without any
+  security verification.
+
+### Added
+
+- **Gem install smoke test** — new `package:gem-smoke-test` CI job installs
+  the built `.gem` in a clean Ruby container and verifies all 20 CLI
+  subcommands load without `LoadError` or `NameError`.
+
+- **test:mutant:full** — full-suite mutant gate on `v*` tag pipelines;
+  `allow_failure:true` until surviving mutants are resolved
+  (baseline ~596 survivors).
+
+- **sec_016 behaviour rule** — codifies the requirement that every publish
+  job targeting a public registry must declare both an artifact-audit gate
+  and an install-parity smoke test in its `needs:` block.
+
+### Changed
+
+- **gemspec spec.files** — restores all intended runtime directories
+  (`conf/`, `locales/`, `packaging/`, `doc/man/`); removes stale globs
+  that produced a near-empty gem in v1.5.8.
+
+- **Rakefile release:gem** — adds minimum-size floor, PII pattern scan,
+  gitleaks check, and positive-allowlist enforcement before any gem build.
+
+### Fixed
+
+- **BackfillUserYml spec coverage** — adds 21 missing specs for the
+  `backfill_user_yml` Thor task (last uncovered file in
+  `lib/rosett_ai/thor/**`).
+
+## [1.5.8] - 2026-07-06
+
+### Changed
+
+- **Automatic RubyGems publishing on tag** — `publish:gem` now runs
+  `when: on_success` on `v*` tags (previously a blocking manual gate), so a
+  tagged release publishes the `.gem` to rubygems.org alongside the `.deb` to
+  aptly. The job now reads the instance-level protected+masked variable
+  `NEATNERDS_RUBYGEMS_PUBLISH` (was the never-configured `RUBYGEMS_API_KEY`).
+  The `v*` tag pattern is a protected tag so the protected variable injects
+  into tag pipelines.
+
+### Fixed
+
+- **Smoke-test embedded-Ruby ABI probe** — the CI smoke-test derived the Ruby
+  ABI version via `RbConfig::CONFIG['ruby_version']`, which fails in the
+  hermetic embedded Ruby (RubyGems/stdlib load path disabled): both
+  `RbConfig` (NameError) and an explicit `require 'rbconfig'` (LoadError) are
+  unavailable there. The probe now derives the ABI from the built-in
+  `RUBY_VERSION` constant (`RUBY_VERSION.split('.')[0,2].join('.') + '.0'`),
+  which needs no require and no load path. Regression from the postinst
+  engine-extraction test block added in v1.5.6.
+
+- **Embedded bin shebangs rewritten at build time** — ruby-build compiles
+  with the staging directory as `--prefix`, so scripts in `embedded/bin/`
+  (gem, bundle, rake, irb, and others) carry the build-time staging path
+  (`…/tmp/staging/opt/rosett-ai/embedded/bin/ruby`) as their shebang.
+  That path does not exist at runtime, causing engine plugin gem installs
+  invoked from postinst to fail with `ENOENT`. A new `rewrite_shebangs!`
+  build stage runs after `:install_gems` (which needs the staging shebang
+  at build time) and rewrites every ruby-shebang script in `embedded/bin/`
+  to `#!/opt/rosett-ai/embedded/bin/ruby` before packaging.
+
+- **Post-install `gem install` bypass staging shebang** — postinst now
+  invokes `"${EMBEDDED_RUBY}" "${EMBEDDED_GEM}" install` (passing the gem
+  script as an argument to the ruby binary) rather than calling
+  `"${EMBEDDED_GEM}" install` directly. Defence-in-depth against any
+  residual stale shebang on the installed gem binary. The postinst ABI
+  probe was also converted from `RbConfig::CONFIG['ruby_version']` to
+  `RUBY_VERSION.split('.')[0,2].join('.') + '.0'` for the same reason as
+  the smoke-test fix above.
+
+- **Postinst engine-gem install: set RUBYLIB to runtime stdlib path** —
+  ruby-build compiles with the staging tree as `--prefix`, so the embedded
+  ruby's compiled-in `$LOAD_PATH` references the staging path (non-existent
+  at runtime). `require 'rubygems'` therefore fails when the gem binary is
+  invoked by postinst, silently skipping engine extraction. The postinst now
+  exports `RUBYLIB=${INSTALL_DIR}/embedded/lib/ruby/${RUBY_ABI}` for the gem
+  install invocation, prepending the correct runtime path so rubygems loads.
+  The CI smoke-test's test-gem build step now uses the system `gem` binary
+  (already present from the apt-installed ruby) rather than the embedded gem
+  binary, keeping the test focused on postinst extraction correctness.
+
+## [1.5.7] - 2026-07-05
+
+### Security
+
+- **Scrub author contact from man page** — replaced the pre-release author
+  address in the `## AUTHORS` section of `doc/man/raictl.1.ronn` with the
+  public contact address (`query@neatnerds.be`). The address was present in
+  the installed man page and was detected by the Gate B post-publish PII scan
+  on v1.5.6. The `artifact-audit` CI gate allows standard man-page attribution;
+  Gate B requires zero pre-release-email hits in the shipped `.deb`.
+
+## [1.5.6] - 2026-07-05
+
+### Security
+
+- **Redact internal tracker references from shipped files** — removed an
+  internal issue reference from `packaging/lib/systemd/rosett-ai-mcp.service.d/throttle.conf`
+  and rephrased the `CHANGELOG.md` v1.5.5 security note to avoid embedding
+  the pre-scrub email address in the changelog description itself. Both were
+  flagged by `artifact-audit` v2.10.1 on the v1.5.5 tag pipeline.
+
+### Fixed
+
+- **Smoke-test embedded Ruby `LD_LIBRARY_PATH`** — the CI smoke-test invoked
+  `/opt/rosett-ai/embedded/bin/ruby` and `/opt/rosett-ai/embedded/bin/gem`
+  directly without setting `LD_LIBRARY_PATH`, causing `libruby.so.3.4: cannot
+  open shared object file` on the CI runner. Prefixed both invocations with
+  `LD_LIBRARY_PATH=/opt/rosett-ai/embedded/lib` so the dynamic linker finds
+  the hermetic library alongside the binary.
+
+## [1.5.5] - 2026-07-05
+
+### Security
+
+- **PII scrub — personal email replaced with functional contact** — replaced
+  internal developer email addresses with the public contact address (`query@neatnerds.be`) in all YAML configuration files,
+  JSON schemas, locale files, and documentation that are shipped in the `.deb`
+  package. This covers SPDX copyright comment headers in `conf/` YAML files,
+  `conf/mcp/trust.yml`, `conf/schemas/*.json`, `locales/*.yml`, `AUTHORS`,
+  `GOVERNANCE.md`, and `README.md`.
+
+- **Artifact audit upgraded to `@v2.10.1`** — the previous pin (`@v2.8.2`)
+  applied a blanket `.pem` extension denylist that flagged public CA certificates
+  bundled with the hermetic Ruby runtime as private-key leaks. The new release
+  uses content-aware detection: only files whose content contains a
+  `BEGIN ... PRIVATE KEY` header are rejected. This eliminates false positives
+  on public certificates while preserving detection of actual private key material.
+
+### Changed
+
+- **`deb-push-aptly` upgraded to `@v2.10.0`** — adds the `http_port` input to
+  allow non-standard aptly API ports. Set `http_port: '8080'` to match the
+  host's aptly configuration.
+
+- **Extended `.deb` exclusions** — the following paths are now excluded from the
+  Debian package staging tree: `.ai-provenance.yml` (AI provenance tracking file,
+  dev-only), `doc/audits/` (internal audit reports), `doc/operations/` (runbooks
+  with internal references), `doc/signing/` (signing scripts), and
+  `doc/rules-audit-*.md` (rule audit snapshots). These files are not runtime
+  requirements and must not appear in a published package.
+
+### Fixed
+
+- **Smoke-test `dpkg --configure` failure on Debian Trixie** — the postinst
+  idempotency check previously called `dpkg --configure rosett-ai` on an
+  already-configured package. On Debian Trixie this fails with a non-zero exit
+  code because `dpkg` refuses to re-configure an already-installed package.
+  Replaced with a direct call to the postinst script:
+  `DEBIAN_FRONTEND=noninteractive /var/lib/dpkg/info/rosett-ai.postinst configure`
+  which exercises the postinst idempotency path without involving dpkg's
+  package-state machine.
+
+## [1.5.4] - 2026-07-05
+
+### Security
+
+- **Artifact audit gate** — added `artifact-audit@v2.8.2` CI/CD catalog component
+  to the pipeline. The `audit:artifact` job runs in a new `audit` stage (between
+  `package` and `deploy`) and verifies the built `.deb` against the positive
+  allowlist, denylist, PII patterns, and gitleaks before publication. A failing
+  audit blocks the `publish:deb-push-aptly` job via a `needs:` override in the
+  pipeline. This closes the gap where a malformed packaging allowlist could have
+  shipped leak-class files to the aptly repository without CI-level detection.
+
+### Changed
+
+- **deb-push-aptly upgraded to @v2.7.1** — bumped from `@v2.6.0`. Adds artifact
+  chain reliability improvements. See ci-components CHANGELOG.
+
+- **Sanitize internal filesystem paths from audit docs and test fixtures** —
+  hardcoded `/home/user/` developer paths removed from `doc/audits/`, `doc/rules-audit-*`,
+  and `spec/` test fixtures. Spec paths replaced with `File.join(Dir.home, ...)` or
+  `/workspace/` placeholders so the `security:pre-tag` CI gate passes on tag pipelines.
+
+## [1.5.3] - 2026-07-04
+
+### Security
+
+- **NNSA-2026-002 Phase B — deb packaging allowlist** — `conf/behaviour/`,
+  `conf/design/`, and `doc/security/` were absent from `APP_EXCLUDES` in
+  `lib/rosett_ai/thor/tasks/build.rb`, allowing user-authored behaviour rules,
+  design documents with internal WP references, and unpublished security
+  advisory drafts to be rsync'd into the `.deb` staging tree. All three
+  directories are now explicitly excluded. Documented in
+  `doc/operations/deb-publish-pipeline.md`.
+
+- **Remove user-authored behaviour rules from HEAD** — `conf/behaviour/criticalthinking.yml`,
+  `conf/behaviour/orchestrator_loop.yml`, `conf/behaviour/session_retrospective.yml`,
+  and `conf/behaviour/tooling_idioms.yml` were tracked in the public repository
+  via `.gitignore` negation patterns (`!conf/behaviour/*.yml`). These are private
+  user rule files that must never ship in product repositories (rule_073). Removed
+  from index; negation lines removed from `.gitignore`. The `doc/security/NNSA-2026-002-draft.md`
+  draft advisory is also removed from HEAD.
+
+- **Genericize `conf/schemas/autoqueue.schema.json`** — the schema `description`
+  field contained a private filesystem path (`~/.claude/projects/…/autoqueue.yml`)
+  and an internal issue tracker reference (``). Replaced with a generic
+  description that does not expose internal paths or issue IDs.
+
+### Changed
+
+- **Gemspec: exclude `conf/design/**`** — design documents carry internal WP
+  references and session identifiers. They are not runtime-required and are no
+  longer shipped in the gem. Only `conf/schemas/`, `conf/targets/`, `conf/mcp/`,
+  `conf/packaging/`, `conf/tooling/`, `conf/compliance/`, `conf/policy/`,
+  `conf/review/`, and `conf/adopt_redactions.yml` remain in the gem allowlist.
+
+- **Anchor `.gitignore` patterns** — `doc/claude-sessions/` and `doc/context/memory/`
+  patterns now use a leading `/` to match only root-level directories, as required
+  by `sec_012`.
+
+### Fixed
+
+- **SPDX header on `.mdl_style.rb`** — the markdownlint style file was the sole
+  `.rb` file missing an SPDX header. Added `GPL-3.0-only` header to complete
+  full coverage.
+
+## [1.5.2] - 2026-07-02
+
+### Fixed
+
+- **SimpleCov atomic write** — add `AtomicSimpleCov.install!` to
+  `spec/spec_helper.rb` and introduce `spec/support/atomic_simple_cov.rb`.
+  Prevents `refuse_coverage_drop` false positives caused by SimpleCov
+  persisting `.last_run.json` after partial/failed RSpec runs. Write is now
+  gated on a complete-green suite (`after(:suite)` hook) and performed
+  atomically via temp-file + `File.rename`. Harmonized from openproject-mcp across the full NeatNerds Ruby stack.
+
+## [1.5.1] - 2026-06-16
+
+### Fixed
+
+- **CI: bump `deb-push-aptly` component to `@v2.6.0`** — the previous pin
+  (`@v2.2.0`) hardcoded `filesystem:neatnerds:` in the `aptly publish update`
+  invocation, mismatching the puppet-configured `filesystem:public:` endpoint
+  on `deb.neatnerds.be`. Every tag pipeline since v2.2.0 would have failed at
+  the publish step (none had reached it before — the  smoke surfaced
+  this on rosett-ai v1.5.0). Bumped to `@v2.6.0`, which introduces a required `publish_endpoint`
+  input and replaces the hardcoded literal with that splat. Set `publish_endpoint:
+  'filesystem:public:'` in this consumer to match the host's aptly config.
+  CI-only change; no runtime behavior shift in the gem.
+
+## [1.5.0] - 2026-06-12
+
+### Fixed
+
+- **postinst engine gem extraction** — `postinst` now runs
+  `gem install --local` for any `rosett-ai-engine-*.gem` files found in the
+  embedded gem cache after a package install or upgrade. Previously, engine
+  `.gem` archives were present in `cache/` but the extracted `gems/<name>-<ver>/`
+  directory was absent, causing `raictl config compile` to fail with
+  "Engine 'claude' not found. No engine plugins installed."
+
+### Added
+
+- **Systemd restart-throttle drop-in** — ships
+  `rosett-ai-mcp.service.d/throttle.conf` in the `.deb`, installed to
+  `/etc/systemd/system/rosett-ai-mcp.service.d/`. Sets `RestartSec=300`,
+  `StartLimitBurst=5`, `StartLimitIntervalSec=300` to prevent restart storms
+  (~9/min → ≤1/5min) during sustained MCP server crash loops. Mitigation for
+  the P0 issue tracked in ; see `doc/operations/systemd-throttle.md`
+  for rationale and rollback procedure
+
+- **RubyGems publication pipeline** — `rake release:gem` build task with
+  sec_001 positive allowlist audit and sec_011 size monitoring; `build:gem`
+  and `publish:gem` CI jobs (manual trigger on tag) for rubygems.org
+  publication
+
+- **Retrospective skip-to-rememberancer** — `behaviour-session_retrospective` rule_008
+  codifies the 60-second auto-skip default for `/retrospective` improvement proposals;
+  the skill body now routes proposals to `rememberancer/incoming-proposals/` without
+  blocking on user input. Autonomous sessions proceed immediately; interactive sessions
+  get a 60s override window
+
+- **Merge-safe `raictl config compile`** — compiling now MERGES with the existing
+  target settings file by default, preserving entries not covered by any source YAML
+  scope and emitting a warning per preserved entry suggesting `raictl backfill-user-yml`.
+  Use `--strict` to restore the previous replace-all behaviour. Prevents accidental
+  destruction of manually-managed allow/deny/env entries during incremental adoption
+
+- **`raictl backfill-user-yml` subcommand** — reads `~/.claude/settings.json` and
+  compares it to the engine's `user.yml` source file. Shows a diff of uncovered entries,
+  prompts for confirmation, and writes the merged YAML idempotently. Standalone
+  `scripts/backfill_user_yml.rb` also available for scripted use with `--yes`.
+  Supports `--target PATH` to specify a non-default user.yml
+
+## [1.4.1] - 2026-06-10
+
+### Fixed
+
+#### fix(ci): Disable branch coverage to eliminate SimpleCov pathology
+
+Applies the  substrate fix proven on varuna (MR !165 / 8ea7674fc).
+Disables SimpleCov branch coverage tracking; line coverage preserved.
+CI post-test phase should drop substantially.
+
+- `enable_coverage :line` (was `:branch`)
+- `minimum_coverage` / `minimum_coverage_by_file`: drop `branch:` kwarg
+
+Reference  + varuna MR !165 for measurement.
+
+## [1.4.0] - 2026-06-07
+
+### Added
+
+- **`SessionHooks::Installer`** — idempotent installer that wires a Ruby script
+  into Claude Code `settings.json` under both `SessionStart` and `PostToolUse`
+  hook sections. Reads existing settings, injects a new hook block if not already
+  present, and atomically writes the result via a tmp→rename strategy. A second
+  `install` call is a no-op; `installed?` reports whether both hook types are
+  wired. Raises `SessionHooksError` on JSON parse or filesystem errors.
+
+## [1.3.4] - 2026-04-24
+
+### Fixed
+
+- **Compile double-load** — project-scope compile no longer loads rules
+  twice when both global and project behaviours exist
+- **MCP tool specs** — specs are now self-contained with inline fixtures,
+  removing dependency on user-local configuration files in CI
+
+### Changed
+
+- **Gemspec positive allowlist** — replaced `git ls-files` denylist with
+  explicit allowlist of runtime-necessary paths (lib/, bin/, conf/, dist/,
+  share/, locales/). Gem file count reduced from 525 to ~398, eliminating
+  dev configs, doc/, packaging/, and dotfiles from the published gem
+- **CI component adoption** — migrated to shared CI/CD templates from
+  ci-components (lint, test, build, security stages)
+- **.deb package size** — excluded 43 MB of dev-only files (doc/, spec/,
+  .yardoc/) from Debian package build
+
+### Added
+
+- **YARD coverage** — pushed API documentation coverage from 67% to 99.89%
+  across 222 source files
+- **SPDX header check** — CI now excludes `.gitkeep` files from SPDX
+  license header validation
+- **Systemd service unit** — `dist/rosett-ai-mcp.service` for running the
+  MCP server as a systemd user service
+
 ## [1.3.3] - 2026-04-19
 
 ### Fixed
@@ -13,21 +380,30 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - **MCP tool response type** — `Governance.register_tool` returned
   `JSON.generate(result)` (String) but MCP gem v0.9.2 calls `.to_h` on the
   return value (`server.rb:520`). Now returns `MCP::Tool::Response` with
-  content type `text`. v1.3.2 yanked from RubyGems (WP#1627)
+  content type `text`. v1.3.2 yanked from RubyGems
 
 ## [1.3.2] - 2026-04-19 [YANKED]
 
+### Yanked
+
+- Yanked from RubyGems on 2026-04-19 (primary reason: MCP dispatch bug, see
+  Fixed below — superseded by v1.3.3). The same gem also shipped
+  `doc/reference/` content embedding author PII (name, email, internal
+  GitLab URL) in PDF metadata and rendered title page; that secondary leak
+  is fixed forward in v1.3.4 which excludes `doc/reference/` from the gem
+  build via the positive-allowlist gemspec.
+
 ### Fixed
 
 - **MCP dispatch bug** — all 33 MCP tools were broken due to argument-passing
   mismatch in `governance.rb`. Block parameter `do |args|` (positional) changed
   to `do |**args|` (keyword splat) to match MCP gem v0.9.2 dispatch convention.
   Second bug: bare `build_kwargs` call changed to `Governance.build_kwargs`
-  because `define_singleton_method` rebinds `self` (WP#1627)
+  because `define_singleton_method` rebinds `self`
 - **Empty tool schemas** — all 27 parameterised tools now declare `INPUT_SCHEMA`
   with proper JSON Schema definitions (types, descriptions, enum constraints,
   required flags). AI clients receive parameter guidance instead of empty
-  `{"type": "object"}` (WP#1627)
+  `{"type": "object"}`
 
 ### Added
 
@@ -36,13 +412,22 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - **MCP integration tests** — 114 integration tests covering dispatch, schema
   presence, and schema-method parity for all 33 registered tools
 
-## [1.3.1] - 2026-04-18
+## [1.3.1] - 2026-04-18 [YANKED]
+
+### Yanked
+
+- Yanked from RubyGems on 2026-05-02. The published gem included
+  `doc/reference/` content (PDF + LaTeX source) that embedded author
+  contact info (name, email) and an internal GitLab URL in PDF metadata
+  and the rendered title page. No credentials, tokens, or session paths
+  were leaked. Fixed forward in v1.3.4, which excludes `doc/reference/`
+  from the gem build via the positive-allowlist gemspec.
 
 ### Fixed
 
 - **Backup XDG path** — `raictl backup create --global` no longer writes to
   read-only `/opt/rosett-ai/app/`. Default destination is now
-  `~/.config/rosett-ai/backups/` (XDG-compliant) (WP#1580)
+  `~/.config/rosett-ai/backups/` (XDG-compliant)
 - **MCP registrar path** — `resolve_command` now checks `/usr/local/bin/raictl`
   first (where .deb installs the wrapper), then `/usr/bin/raictl`, then
   falls back to `which raictl` for absolute path discovery
@@ -60,17 +445,25 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - **Session transcript removal** — stripped 125MB of Claude session transcripts
   (`doc/claude-sessions/`) and context memory files (`doc/context/memory/`)
   from git history using `git filter-repo`. Updated `.gitignore` and hardened
-  gemspec reject block to prevent future leaks (WP#1581)
+  gemspec reject block to prevent future leaks
 - **Gem yank** — yanked `rosett-ai v1.2.0` from RubyGems (contained 122
   session transcript files)
 
-## [1.3.0] - 2026-04-18
+## [1.3.0] - 2026-04-18 [YANKED]
+
+### Yanked
+
+- Yanked from RubyGems on 2026-05-02. Same root cause as v1.3.1 —
+  the published gem included `doc/reference/` content (PDF + LaTeX
+  source) that embedded author PII and an internal GitLab URL in
+  PDF metadata and the rendered title page. No credentials, tokens,
+  or session paths were leaked. Fixed forward in v1.3.4.
 
 ### Added
 
 - **MCP server (rai-mcp)** — Model Context Protocol server with 33 tools,
   8 resources, 4 prompts, and instructions field. Start with
-  `raictl mcp serve` (WP#1557)
+  `raictl mcp serve`
 - **MCP tool categories** — Behaviour management (list, show, display,
   manage), design documents (list, show), compilation (compile,
   compile_status), validation, configuration (config_status,
@@ -92,7 +485,7 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
   enforcement blocks in behaviour rules with pattern safety checks
   (no path traversal, no shell metacharacters, bounded globs).
   `HookGenerator` generates overcommit hook scripts from enforcement
-  definitions (WP#1559)
+  definitions
 - **Schema v1.3.0** — Behaviour schema updated with optional
   `enforcement` block supporting file_patterns, commands, and
   hook_phase definitions
@@ -110,16 +503,14 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 - **Integration test: scope isolation** — Verifies project-scope compile
   writes to `<project>/.claude/rules/` and does not modify global rules
-  (WP#1490)
 - **Integration test: BehaviourCompiler production mode** — Verifies
   BehaviourCompiler works without engine gems or stub registrations
-  (WP#1491)
 - **Integration test: end-to-end compile** — Full pipeline test from YAML
   source to compiled output for each builtin engine (claude, agents_md),
-  including scope isolation (WP#1492)
+  including scope isolation
 - **Integration test: engine registration** — Verifies builtin backends
   resolve via `Backend.for()` without plugin registry, and that unknown
-  engines raise `CompileError` (WP#1492)
+  engines raise `CompileError`
 
 ### Fixed
 
@@ -127,18 +518,18 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
   always returned `~/.claude/rules/` regardless of compile scope. Split
   into `resolve_target_dir` (explicit output_dir) and `default_target_dir`
   (scope-based routing). Project scope now writes to
-  `<project_root>/.claude/rules/` (WP#1490)
+  `<project_root>/.claude/rules/`
 - **BehaviourCompiler failed without engine gem** — `BehaviourCompiler`
   queried the plugin registry directly for the claude engine, which fails
   when no engine gem is installed. Now uses `Backend.for('claude')` which
   checks `BUILTIN_BACKENDS` first, matching the Thor compile task
-  resolution path (WP#1491)
+  resolution path
 
 ## [1.1.0] - 2026-04-01
 
 ### Added
 
-- **Doctor check: stale ~/.rosett-ai/ directory** — New `stale_home_nncc` diagnostic warns when `.rosett-ai/` exists at `$HOME` level, which causes scope resolution confusion by shadowing XDG-path behaviour files (WP#1123)
+- **Doctor check: stale ~/.rosett-ai/ directory** — New `stale_home_nncc` diagnostic warns when `.rosett-ai/` exists at `$HOME` level, which causes scope resolution confusion by shadowing XDG-path behaviour files
 - **Commit hook behaviour** — OpenProject work package integration via branch naming conventions (`<type>/<id>-<subject>`) and overcommit CommitMsg hook for automatic `OP#<id>` injection
 - **XDG auto-migration** — Automatic migration of behaviour files from legacy `~/.claude/conf/` to XDG-compliant `~/.config/rosett-ai/conf/` path
 - **Duplicate rule ID detection** — Compiler now warns when rule IDs collide across behaviour files
@@ -178,12 +569,12 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 - **Duplicate rule ID warnings scoped per-file** — Compiler now only
   warns about duplicate rule IDs within a single behaviour file, not
-  across files. Rule IDs are scoped by behaviour name (WP#1130)
+  across files. Rule IDs are scoped by behaviour name
 - **Removed dead compiler cache code** — `RosettAi::Cache::CompilerCache`
   and `RosettAi::Cache::Manifest` were implemented but never wired into
   the compilation pipeline. Removed until cache is properly
-  integrated (WP#768)
-- **Pre-push hook segfault on GTK4 specs** — Switched pre-push RSpec from full suite to core-only (`RspecCore`) hook that excludes desktop/dbus specs matching CI's `--exclude-pattern`, preventing Ruby segfault in gobject-introspection gem (WP#1122)
+  integrated
+- **Pre-push hook segfault on GTK4 specs** — Switched pre-push RSpec from full suite to core-only (`RspecCore`) hook that excludes desktop/dbus specs matching CI's `--exclude-pattern`, preventing Ruby segfault in gobject-introspection gem
 - **Wrapper breaks project context (RC1)** — `.deb` wrapper `cd /opt/rosett-ai/app` made `ProjectContext` resolve to the rosett-ai internal tree instead of the user's project. Now preserves `RAI_ORIGINAL_PWD` before `cd`
 - **Engine discovery fails on ABI mismatch (RC2)** — Embedded Ruby 3.3.0 could not find engine gems installed under 3.3.10 `GEM_PATH`. Added version-agnostic fallback scan of `/opt/rosett-ai/embedded/lib/ruby/gems/*/`
 - **Target profiles not found after extraction (RC3)** — `TargetProfile.load` now checks the plugin registry first (engine's `target_profile_path`) before falling back to file-based lookup
@@ -201,10 +592,10 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ### Fixed
 
-- **38 audit bugs** — Comprehensive audit campaign fixing remote contamination, XDG migration, worktree issues, and CI divergence (Epic WP#726)
+- **38 audit bugs** — Comprehensive audit campaign fixing remote contamination, XDG migration, worktree issues, and CI divergence (Epic )
 - **CVE-2026-33946** — Updated mcp gem to patched version
-- **Compile scope coexistence** — Global and project behaviours now merge correctly in project scope (Issue 005, WP#711/712)
-- **Global scope source resolution** — Compile task now uses XDG-compliant path for global behaviour source (WP#943)
+- **Compile scope coexistence** — Global and project behaviours now merge correctly in project scope (Issue 005, /712)
+- **Global scope source resolution** — Compile task now uses XDG-compliant path for global behaviour source
 
 ### Changed