robot_lab-audit 0.2.6

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 1172ca1cc991073953bedbf72f533175c7436852d201e6645ed65d75d7117807
+  data.tar.gz: 87aff3fc9ae887a2e774571305e07a6f95ae1837ce1145179cfd6862c90406a9
+SHA512:
+  metadata.gz: b377176b95d73963e9cda9bc83a985abaf863a0a8478d0c6ee82b67be49e012e28c77bfe5fba0ac6f6ab58dfea648b8182844bcb9797c93a8c4dab5c3e58ed16
+  data.tar.gz: 9b79363dba9c3d3cf7e5982cc097f9e429e89a0ec262e25af65b45a998d62b05449f10a0ae19a195bc566857fa7956e886c8d95db1565cb5b4d9620d684a2a17

data/.envrc

@@ -0,0 +1,3 @@
+source_up
+export RR=`pwd`
+export BUNDLE_GEMFILE=Gemfile

data/.github/workflows/deploy-github-pages.yml

@@ -0,0 +1,52 @@
+name: Deploy Documentation to GitHub Pages
+on:
+  push:
+    branches:
+      - main
+      - develop
+    paths:
+      - "docs/**"
+      - "mkdocs.yml"
+      - ".github/workflows/deploy-github-pages.yml"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pages: write
+  id-token: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: 3.x
+
+      - name: Install dependencies
+        run: |
+          pip install mkdocs
+          pip install mkdocs-material
+          pip install mkdocs-macros-plugin
+          pip install mike
+
+      - name: Configure Git
+        run: |
+          git config --local user.email "action@github.com"
+          git config --local user.name "GitHub Action"
+
+      - name: Build MkDocs site
+        run: mkdocs build
+
+      - name: Deploy to GitHub Pages
+        uses: peaceiris/actions-gh-pages@v4
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          publish_dir: ./site
+          keep_files: true

data/.loki

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+# robot_lab-audit — SQLite-backed execution audit log via the Hook system.
+
+import_up "repo_dev.loki"
+
+class Tasks
+  @@gem_name ||= "robot_lab-audit".freeze
+
+  header "robot_lab-audit v#{gem_version} — execution audit log"
+end

data/.quality/reek_baseline.txt

@@ -0,0 +1,2 @@
+3	lib/robot_lab/audit/event_log.rb
+2	lib/robot_lab/audit/hook.rb

data/.rubocop.yml

@@ -0,0 +1 @@
+inherit_from: ../.rubocop-base.yml

data/CHANGELOG.md

@@ -0,0 +1,37 @@
+# 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]
+
+### Added
+- `.loki` Asgard task file: `test`, `rubocop`, `rubocop_fix`, `flog`, `flay`, `quality`, `build`, `install`, `release`, and `console` tasks via the Asgard task runner
+- `flay_check` Rake task: structural code duplication gate (mass threshold 50); integrated into the `quality` Rake task
+- `flay`, `flog`, `rubocop`, and `racc` gems added to development dependencies (`rubocop` was previously absent; `racc` required explicitly for Ruby 4.0 which dropped it from default gems)
+- `test_output.txt`, `flay_output.txt`, `flog_output.txt`, and `rubocop_output.txt` added to `.gitignore`
+
+### Changed
+- `test/test_helper.rb`: test output redirected to `test_output.txt` via `$stdout` reassignment; `TerminalSummaryReporter` prints a single PASS/FAIL summary line to the terminal
+- `Rakefile`: `rubocop` and `rubocop_fix` tasks removed (now owned by Asgard); `flay_check` integrated into the `quality` gate
+
+## [0.1.0] - 2026-05-28
+
+### Added
+
+- `RobotLab::Audit::EventLog` — SQLite-backed append-only log with two tables:
+  `network_runs` (one row per `Network#run`) and `audit_events` (one row per robot
+  invocation or tool call). Query helpers: `network_runs`, `events_for(run_id)`,
+  `recent_errors`.
+- `RobotLab::Audit::Hook` — `RobotLab::Hook` subclass that captures lifecycle events
+  via `before/after_network_run`, `before/after_run`, and `before/after_tool_call`.
+  Uses thread-local storage to correlate all events within a single network run under
+  one `run_id`. Records wall-clock timestamps and duration in milliseconds for each
+  event.
+- `RobotLab::Audit.enable(db_path:)` — one-call setup that creates the `EventLog`,
+  assigns it to the hook, and registers the hook globally with `RobotLab.on`.
+
+[Unreleased]: https://github.com/MadBomber/robot_lab-audit/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/MadBomber/robot_lab-audit/releases/tag/v0.1.0

data/CLAUDE.md

@@ -0,0 +1,60 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## What This Gem Does
+
+`robot_lab-audit` is a SQLite-backed execution audit log for RobotLab. It hooks into the `RobotLab::Hook` system to record every network run, robot invocation, and tool call with timestamps and duration — enabling post-mortem analysis without changing application code.
+
+## Commands
+
+```bash
+bundle exec rake test        # Run full test suite
+ruby -Ilib:test test/<file>  # Run a single test file
+
+bin/console                  # IRB session with gem loaded
+```
+
+## Enabling
+
+```ruby
+require 'robot_lab'
+require 'robot_lab/audit'
+
+RobotLab::Audit.enable(db_path: "~/.robot_lab/audit.db")
+# All subsequent network and robot runs are recorded automatically
+```
+
+`enable` is idempotent — it wires the hook globally once and is safe to call at boot.
+
+## Architecture
+
+All source lives under `lib/robot_lab/audit/`.
+
+**`Audit`** (`audit.rb`) — Entry point module. `Audit.enable(db_path:)` creates the `EventLog` and registers the `Hook` via `RobotLab.on`. Requires `robot_lab` to be loaded first.
+
+**`EventLog`** (`audit/event_log.rb`) — SQLite wrapper. Creates two tables on first open:
+- `network_runs` — one row per `Network#run` call: `run_id`, `network_name`, `input`, `result`, `error_class`, `error_message`, `started_at`, `finished_at`, `duration_ms`
+- `audit_events` — one row per robot run or tool call: same fields plus `event_type` (`"robot_run"` or `"tool_call"`), `robot_name`, `tool_name`
+
+Public query methods: `network_runs(limit:)`, `events_for(run_id)`, `recent_errors(limit:)`.
+
+**`Hook`** (`audit/hook.rb`) — Subclass of `RobotLab::Hook` with `namespace = :audit`. Uses `Thread.current` keyed locals to track `run_id` and `started_at` across the before/after pairs:
+- `before_network_run` / `after_network_run` — writes the `network_runs` row
+- `before_run` / `after_run` — writes a `"robot_run"` audit event
+- `before_tool_call` / `after_tool_call` — writes a `"tool_call"` audit event
+
+All timestamps are UTC ISO 8601 with millisecond precision.
+
+## Key Constraints
+
+- `robot_lab` must be loaded before `robot_lab/audit` — the Hook subclass requires `RobotLab::Hook` to exist.
+- `EventLog` is not thread-safe by itself; SQLite handles concurrent writes via its own locking.
+- `safe_json` on the hook silently falls back to `inspect` for non-serializable values — do not rely on JSON structure for complex tool arguments.
+- Run IDs are UUIDs stored in `Thread.current` — not propagated across Fibers or Ractors.
+
+## Testing
+
+- Minitest with SimpleCov (branch coverage tracked, no minimum threshold enforced yet)
+- Tests use `Tmpdir` for isolated SQLite databases — never write to a shared file in tests
+- Coverage baseline: ~47% line / ~3% branch — test suite is thin relative to implementation

data/COMMITS.md

@@ -0,0 +1,196 @@
+---
+url: https://www.conventionalcommits.org/en/v1.0.0/
+title: Conventional Commits
+description: A specification for adding human and machine readable meaning to commit messages
+access_date: 2025-07-31T20:51:29.000Z
+current_date: 2025-07-31T20:51:29.601Z
+---
+
+# Conventional Commits
+
+A specification for adding human and machine readable meaning to commit messages
+
+ Quick Summary Full Specification Contribute
+
+# Conventional Commits 1.0.0
+
+## Summary
+
+The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages.
+
+The commit message should be structured as follows:
+
+---
+
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+
+```
+
+---
+
+The commit contains the following structural elements, to communicate intent to the consumers of your library:
+
+1. **fix:** a commit of the _type_ `fix` patches a bug in your codebase (this correlates with `PATCH` in Semantic Versioning).
+2. **feat:** a commit of the _type_ `feat` introduces a new feature to the codebase (this correlates with `MINOR` in Semantic Versioning).
+3. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with `MAJOR` in Semantic Versioning). A BREAKING CHANGE can be part of commits of any _type_.
+4. _types_ other than `fix:` and `feat:` are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends `build:`, `chore:`,`ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others.
+5. _footers_ other than `BREAKING CHANGE: <description>` may be provided and follow a convention similar to git trailer format.
+
+Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., `feat(parser): add ability to parse arrays`.
+
+## Examples
+
+### Commit message with description and breaking change footer
+
+```
+feat: allow provided config object to extend other configs
+
+BREAKING CHANGE: `extends` key in config file is now used for extending other config files
+
+```
+
+### Commit message with `!` to draw attention to breaking change
+
+```
+feat!: send an email to the customer when a product is shipped
+
+```
+
+### Commit message with scope and `!` to draw attention to breaking change
+
+```
+feat(api)!: send an email to the customer when a product is shipped
+
+```
+
+### Commit message with both `!` and BREAKING CHANGE footer
+
+```
+chore!: drop support for Node 6
+
+BREAKING CHANGE: use JavaScript features not available in Node 6.
+
+```
+
+### Commit message with no body
+
+```
+docs: correct spelling of CHANGELOG
+
+```
+
+### Commit message with scope
+
+```
+feat(lang): add Polish language
+
+```
+
+### Commit message with multi-paragraph body and multiple footers
+
+```
+fix: prevent racing of requests
+
+Introduce a request id and a reference to latest request. Dismiss
+incoming responses other than from latest request.
+
+Remove timeouts which were used to mitigate the racing issue but are
+obsolete now.
+
+Reviewed-by: Z
+Refs: #123
+
+```
+
+## Specification
+
+The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
+
+1. Commits MUST be prefixed with a type, which consists of a noun, `feat`, `fix`, etc., followed by the OPTIONAL scope, OPTIONAL `!`, and REQUIRED terminal colon and space.
+2. The type `feat` MUST be used when a commit adds a new feature to your application or library.
+3. The type `fix` MUST be used when a commit represents a bug fix for your application.
+4. A scope MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., `fix(parser):`
+5. A description MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes, e.g., _fix: array parsing issue when multiple spaces were contained in string_.
+6. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.
+7. A commit body is free-form and MAY consist of any number of newline separated paragraphs.
+8. One or more footers MAY be provided one blank line after the body. Each footer MUST consist of a word token, followed by either a `:<space>` or `<space>#` separator, followed by a string value (this is inspired by the git trailer convention).
+9. A footer’s token MUST use `-` in place of whitespace characters, e.g., `Acked-by` (this helps differentiate the footer section from a multi-paragraph body). An exception is made for `BREAKING CHANGE`, which MAY also be used as a token.
+10. A footer’s value MAY contain spaces and newlines, and parsing MUST terminate when the next valid footer token/separator pair is observed.
+11. Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the footer.
+12. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g.,_BREAKING CHANGE: environment variables now take precedence over config files_.
+13. If included in the type/scope prefix, breaking changes MUST be indicated by a`!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change.
+14. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., _docs: update ref docs._
+15. The units of information that make up Conventional Commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase.
+16. BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.
+
+## Why Use Conventional Commits
+
+* Automatically generating CHANGELOGs.
+* Automatically determining a semantic version bump (based on the types of commits landed).
+* Communicating the nature of changes to teammates, the public, and other stakeholders.
+* Triggering build and publish processes.
+* Making it easier for people to contribute to your projects, by allowing them to explore a more structured commit history.
+
+## FAQ
+
+### How should I deal with commit messages in the initial development phase?
+
+We recommend that you proceed as if you’ve already released the product. Typically _somebody_, even if it’s your fellow software developers, is using your software. They’ll want to know what’s fixed, what breaks etc.
+
+### Are the types in the commit title uppercase or lowercase?
+
+Any casing may be used, but it’s best to be consistent.
+
+### What do I do if the commit conforms to more than one of the commit types?
+
+Go back and make multiple commits whenever possible. Part of the benefit of Conventional Commits is its ability to drive us to make more organized commits and PRs.
+
+### Doesn’t this discourage rapid development and fast iteration?
+
+It discourages moving fast in a disorganized way. It helps you be able to move fast long term across multiple projects with varied contributors.
+
+### Might Conventional Commits lead developers to limit the type of commits they make because they’ll be thinking in the types provided?
+
+Conventional Commits encourages us to make more of certain types of commits such as fixes. Other than that, the flexibility of Conventional Commits allows your team to come up with their own types and change those types over time.
+
+### How does this relate to SemVer?
+
+`fix` type commits should be translated to `PATCH` releases. `feat` type commits should be translated to `MINOR` releases. Commits with `BREAKING CHANGE` in the commits, regardless of type, should be translated to `MAJOR` releases.
+
+### How should I version my extensions to the Conventional Commits Specification, e.g. `@jameswomack/conventional-commit-spec`?
+
+We recommend using SemVer to release your own extensions to this specification (and encourage you to make these extensions!)
+
+### What do I do if I accidentally use the wrong commit type?
+
+#### When you used a type that’s of the spec but not the correct type, e.g. `fix` instead of `feat`
+
+Prior to merging or releasing the mistake, we recommend using `git rebase -i` to edit the commit history. After release, the cleanup will be different according to what tools and processes you use.
+
+#### When you used a type _not_ of the spec, e.g. `feet` instead of `feat`
+
+In a worst case scenario, it’s not the end of the world if a commit lands that does not meet the Conventional Commits specification. It simply means that commit will be missed by tools that are based on the spec.
+
+### Do all my contributors need to use the Conventional Commits specification?
+
+No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they’re merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
+
+### How does Conventional Commits handle revert commits?
+
+Reverting code can be complicated: are you reverting multiple commits? if you revert a feature, should the next release instead be a patch?
+
+Conventional Commits does not make an explicit effort to define revert behavior. Instead we leave it to tooling authors to use the flexibility of _types_ and _footers_ to develop their logic for handling reverts.
+
+One recommendation is to use the `revert` type, and a footer that references the commit SHAs that are being reverted:
+
+```
+revert: let us never again speak of the noodle incident
+
+Refs: 676104e, a215868
+
+```

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026 Dewayne VanHoozer
+
+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.

data/README.md

@@ -0,0 +1,141 @@
+# robot_lab-audit
+
+A [RobotLab](https://github.com/MadBomber/robot_lab) extension gem that writes a
+structured execution audit log to SQLite. Every network run, robot invocation, and
+tool call is recorded as a row — timestamps, inputs, outputs, errors, and duration —
+so you can query what happened after the fact.
+
+Plugs into RobotLab's `Hook` system. Zero changes to your robots or networks; opt in
+by calling `RobotLab::Audit.enable`.
+
+## Installation
+
+Add to your Gemfile:
+
+```ruby
+gem "robot_lab-audit"
+```
+
+Or install directly:
+
+```bash
+gem install robot_lab-audit
+```
+
+## Usage
+
+```ruby
+require "robot_lab"
+require "robot_lab/audit"
+
+RobotLab::Audit.enable(db_path: "~/.robot_lab/audit.db")
+
+# All network runs and robot runs from here on are logged automatically.
+network = RobotLab.create_network(...)
+network.run(message: "do something")
+```
+
+The database file and any missing parent directories are created automatically.
+
+### What gets logged
+
+| Table | One row per | Key columns |
+|-------|-------------|-------------|
+| `network_runs` | `Network#run` call | `run_id`, `network_name`, `input`, `result`, `error_*`, `started_at`, `finished_at`, `duration_ms` |
+| `audit_events` | `Robot#run` or `Tool#call` | `run_id`, `event_type`, `robot_name`, `tool_name`, `input`, `output`, `error_*`, `started_at`, `finished_at`, `duration_ms` |
+
+`event_type` is `"robot_run"` or `"tool_call"`. All input/output values are JSON.
+Timestamps are ISO 8601 with millisecond precision.
+
+All events within a single `Network#run` share the same `run_id`, so you can
+reconstruct the full execution trace for any network run.
+
+Standalone `Robot#run` calls (outside a network) are also recorded; their `run_id`
+column will be `nil`.
+
+### Querying the log
+
+`EventLog` provides three convenience methods:
+
+```ruby
+log = RobotLab::Audit::Hook.event_log
+
+log.network_runs(limit: 100)       # recent network runs, newest first
+log.events_for("some-run-id")      # all events for one run, ordered by time
+log.recent_errors(limit: 50)       # events where error_class is not null
+```
+
+Each method returns an array of hashes keyed by column name.
+
+You can also query the SQLite database directly with any SQL tool:
+
+```bash
+sqlite3 ~/.robot_lab/audit.db \
+  "SELECT event_type, robot_name, tool_name, duration_ms, error_class
+   FROM audit_events
+   WHERE run_id = 'some-run-id'
+   ORDER BY started_at;"
+```
+
+### Scoping to a robot or network
+
+`RobotLab::Audit.enable` registers the hook globally. To limit logging to a specific
+robot or network, register the hook directly on that object instead:
+
+```ruby
+RobotLab::Audit::Hook.event_log = RobotLab::Audit::EventLog.new(db_path: "audit.db")
+
+robot.on(RobotLab::Audit::Hook)
+# or
+network.on(RobotLab::Audit::Hook)
+```
+
+## Schema
+
+```sql
+CREATE TABLE network_runs (
+  id            INTEGER PRIMARY KEY AUTOINCREMENT,
+  run_id        TEXT    NOT NULL UNIQUE,
+  network_name  TEXT,
+  input         TEXT,
+  result        TEXT,
+  error_class   TEXT,
+  error_message TEXT,
+  started_at    TEXT    NOT NULL,
+  finished_at   TEXT,
+  duration_ms   REAL
+);
+
+CREATE TABLE audit_events (
+  id            INTEGER PRIMARY KEY AUTOINCREMENT,
+  run_id        TEXT,
+  event_type    TEXT NOT NULL,
+  robot_name    TEXT,
+  tool_name     TEXT,
+  input         TEXT,
+  output        TEXT,
+  error_class   TEXT,
+  error_message TEXT,
+  started_at    TEXT NOT NULL,
+  finished_at   TEXT,
+  duration_ms   REAL
+);
+```
+
+## Development
+
+```bash
+bundle install
+bundle exec rake test       # run tests
+bundle exec rake            # default: test
+bin/console                 # IRB with gem loaded
+```
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at
+https://github.com/MadBomber/robot_lab-audit.
+
+## License
+
+MIT. See [LICENSE.txt](LICENSE.txt).

data/Rakefile

@@ -0,0 +1,132 @@
+# frozen_string_literal: true
+
+require 'bundler/gem_tasks'
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'test'
+  t.libs << 'lib'
+  t.test_files = FileList['test/**/*_test.rb', 'test/**/test_*.rb'].exclude('**/*_helper.rb')
+  t.verbose = true
+  t.ruby_opts << '-rtest_helper'
+end
+
+task default: :test
+
+desc 'Run tests with verbose output'
+task :test_verbose do
+  ENV['TESTOPTS'] = '--verbose'
+  Rake::Task[:test].invoke
+end
+
+desc 'Run a single test file'
+task :test_file, [:file] do |_t, args|
+  ruby "test/#{args[:file]}"
+end
+
+desc 'Check code complexity with Flog (warn >=20, fail >=50)'
+task :flog_check do
+  require 'flog'
+
+  method_warn = 20.0
+  method_fail = 50.0
+
+  flogger = Flog.new(all: true)
+  flogger.flog(*Dir.glob('lib/**/*.rb'))
+
+  warnings = []
+  failures = []
+
+  flogger.each_by_score do |method, score|
+    next if method.end_with?('#none')
+
+    if score > method_fail
+      failures << "#{format('%.1f', score)}: #{method}"
+    elsif score > method_warn
+      warnings << "#{format('%.1f', score)}: #{method}"
+    end
+  end
+
+  unless warnings.empty?
+    puts "\nFlog warnings (#{method_warn}–#{method_fail}) — target for future refactoring:"
+    warnings.each { |v| puts "  #{v}" }
+  end
+
+  if failures.empty?
+    puts "\nFlog: no methods exceed the failure threshold (>=#{method_fail})"
+  else
+    puts "\nFlog failures (>=#{method_fail}) — must be refactored:"
+    failures.each { |v| puts "  #{v}" }
+    abort "\nFlog quality gate failed: #{failures.size} method(s) exceed #{method_fail}"
+  end
+end
+
+desc 'Check for structural code duplication with Flay (mass >= 50)'
+task :flay_check do
+  require 'flay'
+
+  mass_threshold = 50
+
+  flay = Flay.new({ mass: mass_threshold, diff: false, verbose: false, summary: false, timeout: 60 })
+  flay.process(*Dir.glob('lib/**/*.rb'))
+  flay.analyze
+
+  if flay.hashes.empty?
+    puts "\nFlay: no structural duplication detected (mass >= #{mass_threshold})"
+  else
+    puts "\nFlay found structural duplication (mass >= #{mass_threshold}):"
+    flay.report
+    abort "\nFlay quality gate failed: #{flay.hashes.length} pattern(s) detected"
+  end
+end
+
+desc 'Run all quality checks: tests (with coverage), RuboCop, Flog, and Flay'
+task :quality do
+  gates = [
+    ['Tests + Coverage', 'bundle exec rake test'],
+    ['RuboCop',          'bundle exec rubocop'],
+    ['Flog Complexity',  'bundle exec rake flog_check'],
+    ['Flay Duplication', 'bundle exec rake flay_check']
+  ]
+
+  results = gates.map do |label, command|
+    puts "\n#{'=' * 60}"
+    puts "Quality Gate: #{label}"
+    puts '=' * 60
+    [label, system(command) ? :pass : :fail]
+  end
+
+  green = ->(s) { "\e[32m#{s}\e[0m" }
+  red   = ->(s) { "\e[31m#{s}\e[0m" }
+  width = results.map { |label, _| label.length }.max
+
+  puts "\n#{'=' * 60}"
+  puts 'Quality Gate Summary'
+  puts '=' * 60
+  results.each do |label, status|
+    badge = status == :pass ? green.call('PASS') : red.call('FAIL')
+    puts "  [#{badge}] #{label.ljust(width)}"
+  end
+  puts '-' * 60
+
+  passed = results.count { |_, s| s == :pass }
+  failed = results.count { |_, s| s == :fail }
+  tally  = "#{passed} passed, #{failed} failed"
+  puts "  #{failed.zero? ? green.call(tally) : red.call(tally)}"
+  puts '=' * 60
+
+  abort "\n#{red.call('Quality gate failed.')}" unless failed.zero?
+  puts "\n#{green.call('All quality gates passed.')}"
+end
+
+namespace :docs do
+  desc 'Build MkDocs documentation'
+  task :build do
+    sh 'mkdocs build'
+  end
+
+  desc 'Serve MkDocs documentation locally on http://localhost:8000'
+  task :serve do
+    sh 'mkdocs serve'
+  end
+end