perfgate 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 100020429feb022487b41383ee3fdab69d2274a07851a33ac205c05120e24199
+  data.tar.gz: 889de864cd8145a014665eafeb9311f4a358358b0b61da85f380361210cf4ff6
+SHA512:
+  metadata.gz: a1f83f58d455a7ee3705b7696ba67617d6ddb3f96d8c9ee871223b4fc9fc4c825997d8add9f33670fcbdab52055a394c3d4b9f4746d844a02e9dcdc9f178cf01
+  data.tar.gz: 3e5e768960362b02652201712d61656132bfa70c9f78d7ad5c560cba5ad8b4bae9338d4bf9b07a2543cbdaa65ab873a43d7fc37fb685aec8ba52818a6e2d0a70

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,25 @@
+AllCops:
+  TargetRubyVersion: 3.1
+  NewCops: enable
+  # Exploratory Milestone 0 spikes are throwaway scripts, not held to the
+  # same design/style bar as the gem itself.
+  Exclude:
+    - "spikes/**/*"
+
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Layout/LineLength:
+  Max: 120
+
+# RSpec example groups naturally group many small `it` blocks together;
+# the default limit is tuned for regular method bodies, not spec files.
+Metrics/BlockLength:
+  Exclude:
+    - "spec/**/*"
+    - "*.gemspec"

data/CHANGELOG.md

@@ -0,0 +1,18 @@
+## [Unreleased]
+
+## [0.1.0] - 2026-08-26
+
+- Core execution engine: CLI, configuration loader, RSpec discovery
+  via `perfgate: true` metadata, `Perfgate.measure`, process-isolated
+  warmup/samples, and a filesystem result bundle.
+- Rails metrics: SQL query count/duration, allocations, and GC
+  diagnostics, correctly isolated to the measurement block.
+- Comparison and policy: execution fingerprints, a compatibility
+  engine, Mann-Whitney statistics, practical thresholds, PASS/WARN/FAIL
+  decisions with CI exit codes, and regression-injection test coverage.
+- CI experience: deterministic diagnostics, console and Markdown
+  reports, `perfgate run --compare/--format` for a single-step CI
+  comparison, portable `perfgate-run-<run-id>.tar.gz` archives, and a
+  documented GitHub Actions workflow.
+- Release readiness: security policy, contribution guide,
+  compatibility matrix, and telemetry specification.

data/CONTRIBUTING.md

@@ -0,0 +1,73 @@
+# Contributing to Baseline
+
+Thanks for considering a contribution. Baseline is early and the scope
+is deliberately narrow -- see
+[baseline_oss_mvp_technical_spec_and_roadmap.md](../baseline_oss_mvp_technical_spec_and_roadmap.md)
+for the authoritative product and technical specification. If you're
+proposing something not covered there, please open an issue to discuss
+scope before sending a large pull request.
+
+## Development setup
+
+```bash
+git clone <your fork>
+cd baseline
+bin/setup
+```
+
+This installs dependencies via Bundler. `bin/console` gives you an
+interactive prompt with the gem loaded.
+
+## Running the checks
+
+```bash
+bundle exec rspec     # unit tests
+bundle exec rubocop   # style and complexity checks
+```
+
+Both must pass before a pull request will be merged; `rake` (no
+arguments) runs both.
+
+## Coding conventions
+
+- This project has a firm house rule: when RuboCop flags a file for
+  length or complexity (`Metrics/MethodLength`, `Metrics/ClassLength`,
+  `Metrics/ModuleLength`, etc.), **extract a smaller method or a new
+  collaborator class/module** rather than raising the limit in
+  `.rubocop.yml`. Several modules in `lib/baseline/comparison/` and
+  `lib/baseline/cli/` exist specifically because of this rule -- follow
+  that pattern.
+- Favor small, single-purpose classes and modules over large ones.
+  Keep public interfaces documented with a short module/class comment
+  explaining the "why", not just the "what".
+- New behavior should ship with unit tests. Regression-injection style
+  tests (seed a known regression, assert Baseline detects it) are
+  especially valuable for comparison/policy logic.
+- Don't add a new runtime dependency without discussing it first --
+  the spec favors using Ruby/Rails standard library and already-present
+  gems (e.g. `rubygems/package` and `zlib` for archives) over adding
+  new ones.
+
+## Commit and PR style
+
+- Write commit messages and PR descriptions the way you'd want to read
+  them in `git log`: an imperative-mood subject line, and a body that
+  explains *why* when it's not obvious from the diff.
+- Keep pull requests scoped to one milestone or one deliverable where
+  possible; it makes review much faster.
+- Reference the relevant spec section (e.g. "spec 20.3") in the PR
+  description when implementing a specific documented behavior.
+
+## Reporting bugs
+
+Open a GitHub issue with:
+
+- Baseline version, Ruby version, Rails version, RSpec version;
+- your `baseline.yml` (redacted if needed);
+- the command you ran and its full output;
+- what you expected vs. what happened.
+
+## Reporting security issues
+
+Please don't file security vulnerabilities as public issues -- see
+[SECURITY.md](SECURITY.md) instead.

data/LICENSE

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

data/NOT_FINALIZED.md

@@ -0,0 +1,70 @@
+# Not Finalized
+
+## CLI commands not yet built
+
+| Command | What it should do | Spec section |
+|---|---|---|
+| `perfgate init` | Scaffold `baselined.yml` with commented defaults and an example workload block | §6.1 |
+| `perfgate doctor` | Pre-flight check: Ruby/Rails version, RSpec integration present, storage path writable, config valid | Phase 2 |
+| `perfgate schema` | Print the canonical JSON Schema for run-result or comparison-result to stdout | Phase 2 |
+| `perfgate report` | Re-render a saved comparison result in any supported format without re-running workloads | Phase 2 |
+
+`init` and `doctor` directly affect first-run experience and are the highest priority.
+
+---
+
+## Memory metric not implemented
+
+`metrics.memory` config key exists and is accepted by the schema validator,
+but the collector is absent. `Instrumentation::REGISTRY` has no `:memory` entry.
+
+File: `lib/baselined/instrumentation.rb:19` — comment says "not yet implemented".
+
+Safe to ship as-is (the config key silently has no effect), but the docs
+(`docs/compatibility.md`) describe it as opt-in and experimental — should either
+implement it or document clearly that it is deferred.
+
+---
+
+## README status note is stale
+
+`README.md` still reads:
+
+> **Status:** Early development. `run` and `compare` are implemented and
+> covered by tests; `init`, `report`, `doctor`, and `schema` are not yet built.
+
+This needs to be updated before publishing — either to reflect what is missing
+or removed once `init`/`doctor` are built.
+
+---
+
+## CI matrix gap
+
+`docs/compatibility.md` lists Ruby 3.2–3.4 and Rails 7.1/7.2/8.0 as supported,
+but the repo's own CI (`github/workflows/main.yml`) only tests Ruby 3.2.2 + SQLite.
+
+No PostgreSQL or MySQL adapter tests. No Rails 7.2/8.0 matrix row.
+
+Not a hard blocker for a first release, but should be noted in the release
+announcement and closed before claiming broad compatibility.
+
+---
+
+## No GitHub remote
+
+The git repo at `baseline/` has commits and no remote.
+`spec.homepage` in the gemspec points to `https://github.com/baseline-oss/perfgate`
+which does not exist yet.
+
+Must push before publishing so RubyGems.org can resolve the source link and
+`spec.files` (`git ls-files`) captures everything correctly.
+
+---
+
+## CHANGELOG not updated for release
+
+The `[Unreleased]` block contains all milestone work but has never been
+promoted to a dated `[0.1.0]` entry. The existing `[0.1.0]` line at the
+bottom just says "Initial release".
+
+Needs a proper dated entry before tagging and pushing.

data/README.md

@@ -0,0 +1,86 @@
+# Perfgate
+
+Perfgate is an open-source, CI-native performance assurance tool for Ruby on
+Rails applications. It converts selected RSpec examples into repeatable
+performance workloads, measures application-level signals (duration, SQL
+activity, allocations, GC), compares a pull request against a compatible
+default-branch baseline, and produces a clear PASS/WARN/FAIL merge-gate
+decision.
+
+> Did this change introduce a material, reproducible performance regression?
+
+## Installation
+
+Add to your Gemfile:
+
+```ruby
+gem "perfgate", group: :test
+```
+
+## Usage
+
+Tag an RSpec example with `perfgate: true` and wrap the part you want
+measured in `Perfgate.measure`:
+
+```ruby
+RSpec.describe "Checkout", type: :request, perfgate: true do
+  it "creates an order" do
+    sign_in(create(:user))
+    cart = create(:cart, :with_line_items)
+
+    Perfgate.measure { post "/checkout", params: { cart_id: cart.id } }
+
+    expect(response).to have_http_status(:created)
+  end
+end
+```
+
+Then run it:
+
+```bash
+bundle exec perfgate run --output .perfgate/current
+bundle exec perfgate compare --baseline .perfgate/main --candidate .perfgate/current
+```
+
+`perfgate run` also accepts `--compare PATH` to run and compare against a
+reference bundle in one step, and `--format markdown` to render a Markdown
+report instead of the console summary. Combined, this is what a CI job needs:
+
+```bash
+bundle exec perfgate run \
+  --output .perfgate/current \
+  --compare .perfgate/reference \
+  --format markdown
+```
+
+This writes a `summary.md` file into `--output` alongside the run bundle, so
+it can be published as a GitHub Actions job summary. See
+[docs/onboarding.md](docs/onboarding.md) for a full walkthrough and
+[examples/rails-rspec-app](examples/rails-rspec-app) for a full example
+workflow, including the artifact download/upload steps that carry a baseline
+result between CI runs.
+
+## Docs
+
+- [Architecture](docs/architecture.md) - layered pipeline, key design decisions, how to add a metric
+- [Onboarding guide](docs/onboarding.md) - first-run walkthrough for an existing Rails/RSpec app
+- [Compatibility matrix](docs/compatibility.md) - supported Ruby, Rails, and database versions
+- [Telemetry contract](docs/telemetry.md) - what is (and is never) collected
+- [Roadmap](ROADMAP.md) - what's done, what's next, what's out of scope
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then,
+run `rake spec` to run the tests. You can also run `bin/console` for an
+interactive prompt that will allow you to experiment.
+
+## Contributing
+
+Bug reports and pull requests are welcome on [GitHub](https://github.com/a11ejandro/perfgate).
+See the contribution guide for scope, principles, and the implementation
+constraints that pull requests are expected to follow.
+
+## License
+
+Perfgate is available as open source under the terms of the
+[Apache License 2.0](LICENSE).

data/ROADMAP.md

@@ -0,0 +1,125 @@
+# Roadmap
+
+This roadmap tracks work toward a public gem release and beyond. Items within
+each phase are roughly prioritized; the order within a phase is not fixed.
+
+Status key: ✅ done · 🚧 in progress · ⬜ not started
+
+---
+
+## Phase 1 — Implemented (MVP core)
+
+✅ `perfgate run` — discovers `:baseline`-tagged RSpec examples, runs warmups
+   + measured samples in subprocess isolation, writes a versioned JSON result bundle
+
+✅ `perfgate compare` — loads two result bundles, validates fingerprint
+   compatibility, produces per-workload PASS/WARN/FAIL/INCOMPARABLE decisions,
+   saves a comparison result, exits with CI-meaningful codes
+
+✅ Instrumentation — wall-clock duration (monotonic), SQL query count and
+   cumulative duration (ActiveSupport::Notifications), Ruby object allocations
+   (GC.stat delta), GC activity
+
+✅ Statistics — Mann-Whitney U with tie correction, extended summary
+   (min/p50/p95/p99/max/count)
+
+✅ Fingerprinting — environment fingerprint (Ruby version, Rails version,
+   platform, dataset version) + per-workload definition hash; compatibility
+   engine that blocks incomparable runs
+
+✅ Regression policy — statistical + practical-floor dual guard; noise-ratio
+   downgrade; deterministic SQL comparison; configurable thresholds
+
+✅ Console and Markdown reporters — table-format console output; GitHub-flavored
+   Markdown for job summaries and PR comments
+
+✅ `baseline run --compare PATH --format markdown` — one-step CI command
+
+✅ Portable archives — `export_archive`/`import_archive` for `.tar.gz` artifact
+   hand-off between CI jobs; path-traversal rejection on import
+
+✅ GitHub Actions example workflow — upload/download artifact pattern for
+   default-branch → PR comparison
+
+✅ Docs — CONTRIBUTING, SECURITY, compatibility matrix, telemetry contract,
+   onboarding guide
+
+---
+
+## Phase 2 — Pre-release polish
+
+⬜ `perfgate init` — scaffold `baseline.yml` with commented defaults and an
+   example workload block; the spec describes it but it is not yet built
+
+⬜ `perfgate doctor` — pre-flight check: Ruby/Rails version, RSpec integration
+   presence, storage directory writability, config validity
+
+⬜ `perfgate schema` — print the canonical JSON Schema for run-result or
+   comparison-result to stdout; useful for tooling integration
+
+⬜ `perfgate report` — re-render a saved comparison result in any supported
+   format without re-running workloads
+
+⬜ Expanded CI matrix — test against Ruby 3.2/3.3/3.4 and
+   Rails 7.1/7.2/8.0 in CI (currently only Ruby 3.2.2 + SQLite)
+
+⬜ PostgreSQL and MySQL smoke tests — verify SQL instrumentation behaves
+   identically across adapters
+
+⬜ RubyGems.org release — cut `v0.1.0`, add gem badge to README, publish
+   to rubygems.org
+
+---
+
+## Phase 3 — Developer experience
+
+⬜ `baseline accept` — mark a known-regression comparison as accepted so the
+   next default-branch run becomes the new reference without manual file moves
+
+⬜ Per-workload threshold overrides in `baseline.yml` — allow tighter or
+   looser thresholds for specific workload IDs
+
+⬜ Memory delta metric (opt-in) — process RSS delta per sample; gated behind
+   `metrics.memory: true` because RSS is noisy on most platforms
+
+⬜ Sidekiq adapter — first-class `Perfgate.measure { MyWorker.drain }` helper
+   that suppresses Sidekiq's own threading and logging noise
+
+⬜ VS Code / RubyMine run-configuration snippets in the example app
+
+⬜ Interactive `baseline run --watch` for local iteration
+
+---
+
+## Phase 4 — Ecosystem and integrations
+
+⬜ GitHub PR comment integration — post or update a comparison summary comment
+   on the PR (requires a GitHub token; strictly opt-in)
+
+⬜ Telemetry (opt-in) — anonymous, privacy-preserving usage data; schema and
+   contract already documented in `docs/telemetry.md`; no data is sent until
+   this is built and the user opts in
+
+⬜ Minitest adapter — extend discovery and execution to work with Minitest
+   test suites
+
+⬜ GitLab CI / Bitbucket Pipelines example workflows
+
+⬜ SARIF output format — machine-readable regression report for GitHub
+   Advanced Security or similar tooling
+
+---
+
+## Out of scope (MVP and foreseeable future)
+
+These are explicitly not on the roadmap for the open-source gem:
+
+- Baseline Cloud / hosted dashboards / long-term history
+- User accounts or billing
+- Multi-repository analytics
+- Production APM or continuous profiling
+- Automatic workload discovery (without explicit `:baseline` tag)
+- Browser / E2E measurement
+- Distributed or concurrency load testing
+- AI-generated diagnoses or automatic code attribution
+- Non-Ruby languages

data/Rakefile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new
+
+task default: %i[spec rubocop]