rubocop-osc7501 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 1f5fd674d7fc499061d87cf01bdcfda1e06e9e688e73db0404c129a24eaf0247
+  data.tar.gz: 501bfb77a215116462ad6e92a3355fafa385194946f62573fb9f7e016b8e8118
+SHA512:
+  metadata.gz: fe527b0575c7c819d68bb917ef61c801746b6bcce236bd3851096482341edcb51303b719633fd542cfa9b2d68307de6a569df3cfde87a16bc629db47450792e7
+  data.tar.gz: 618859b3fe899e1c7e1465be5ef4357059eddbcb1952d8e13b7fd1ad048c0f2c9a4451fe22a2d732a0d41a89d251ff531e5d7c84a619a325f580652a0c47df58

data/ACCESSIBILITY.md

@@ -0,0 +1,30 @@
+# Accessibility
+
+Read RuboCop output without relying on terminal status indicators. RuboCop keeps
+ordinary formatter output and errors available as text.
+
+## Plain text output
+
+Disable status reporting and preselect an ordinary formatter:
+
+```sh
+RUBOCOP_OSC7501=off bundle exec rubocop --require rubocop/osc7501 --format progress
+```
+
+`RUBOCOP_OSC7501=off` bypasses eager formatter construction. By default RuboCop
+sends records only to a TTY with a terminal other than `dumb`.
+`RUBOCOP_OSC7501=force` overrides both checks.
+
+## Environments and limits
+
+Terminal status requires an OSC 7501-capable terminal. The gem checks for a TTY
+and honors `TERM=dumb` but does not detect OSC support. Your terminal controls
+display and announcements. I have not tested status display with screen readers,
+and live Rex or tmux presentation has not been verified.
+
+## Report a barrier
+
+Open an [issue](https://github.com/cosgroveb/rubocop-osc7501/issues) describing
+what you tried, what prevented you, and what would help. Include terminal,
+operating system, and assistive technology versions when relevant. You do not
+need to disclose a disability or medical information.

data/CHANGELOG.md

@@ -0,0 +1,11 @@
+# Changelog
+
+## Unreleased
+
+## 0.1.0 - 2026-11-13
+
+- Add opt-in OSC 7501 reporting for RuboCop ([60239fa](https://github.com/cosgroveb/rubocop-osc7501/commit/60239faa66d79897525a96f66d4f988d22b00a41))
+- Fix hosted compatibility test environments ([e2923a9](https://github.com/cosgroveb/rubocop-osc7501/commit/e2923a9c97a501b0636ec9dac9778f59e2354d46))
+- Preserve Bundler load path in legacy checks ([47e351d](https://github.com/cosgroveb/rubocop-osc7501/commit/47e351d5aed51ce90bc295af593f6fb856bb1f50))
+- Trace legacy compatibility child startup ([33546a1](https://github.com/cosgroveb/rubocop-osc7501/commit/33546a108bbe7ed16e1e44195ce9dcf047437b39))
+- Use loaded Bundler path in legacy checks ([d211604](https://github.com/cosgroveb/rubocop-osc7501/commit/d21160489066c54f4a7d2745060cfb87d98fe339))

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,68 @@
+# Code of conduct
+
+Everyone who participates in good faith is welcome in rubocop-osc7501. Treat
+people with respect, regardless of race, ethnicity, caste, color, age, physical
+characteristics, neurodiversity, disability, sex, gender identity or expression,
+sexual orientation, language, philosophy, religion, national or social origin,
+income, education, or other status.
+
+## Working together
+
+Respect the project's purpose and other people's time. Discuss ideas without
+attacking people. Make room for different viewpoints and experiences. Give and
+accept constructive feedback. Account for differences in language, culture,
+and communication when interpreting what someone says.
+
+Take responsibility for what you submit, including code, reports, and comments
+produced with AI assistance. Review it before sharing, make sure you understand
+it, and respond to questions and corrections. Respect the time others spend
+reviewing your work. Take responsibility for repairing harm you cause.
+
+Do not:
+
+- Harass people, ignore a request to stop, or violate stated boundaries.
+- Make personal attacks, discriminate, or stereotype people by identity.
+- Make unwanted sexual comments or advances.
+- Share or use someone's private information without permission.
+- Threaten, encourage, or cause violence or other harm.
+- Impersonate someone or evade moderation with another identity.
+- Contribute someone else's work without credit.
+- Post unrelated advertising or present harmful content without appropriate
+  context and care.
+
+Threatening or encouraging these behaviors also violates this policy. Other
+behavior that threatens the community's well-being may warrant moderation.
+Disagreement alone is not a conduct violation.
+
+## Reporting and enforcement
+
+Report concerns privately to Brian Cosgrove at
+[cosgroveb@gmail.com](mailto:cosgroveb@gmail.com). Include what happened and any
+relevant links or messages. Do not post private reports in public issues.
+
+I review and investigate reports, hear from the people involved as needed, and
+prioritize safety and confidentiality. I share report details only as needed
+to investigate and respond. I handle enforcement privately and discuss any
+public resolution with the people involved. I respond as availability permits,
+without a guaranteed deadline.
+
+Depending on severity and repetition, I may issue a warning, remove content,
+restrict participation, or impose a temporary or permanent ban. Serious
+violations may lead to an immediate ban. Where continued participation is
+appropriate, I explain what needs to change and any conditions for returning.
+These rules apply to maintainers as well as other participants.
+
+## Scope
+
+This policy covers project spaces and anyone officially representing the
+project elsewhere, including through project accounts or at events.
+
+## Attribution
+
+Adapted from [Contributor Covenant 3.0](https://www.contributor-covenant.org/version/3/0/code_of_conduct/),
+stewarded by the Organization for Ethical Source. This adaptation shortens the
+wording and uses a maintainer-led reporting and enforcement process.
+
+This document is licensed under
+[CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
+The software remains licensed under [Apache License 2.0](LICENSE).

data/CONTRIBUTING.md

@@ -0,0 +1,126 @@
+# Contributing
+
+Follow the [code of conduct](CODE_OF_CONDUCT.md). Report vulnerabilities through
+the private channel in [SECURITY.md](SECURITY.md).
+
+AI-assisted contributions are welcome. Verify claims in code and reports, state
+what you tested, and take responsibility for what you submit.
+
+Use MRI Ruby 3.4 or newer for development tooling. Install actionlint 1.7.12 on
+your PATH, then run:
+
+```sh
+bundle install
+bundle exec rake
+```
+
+`rake` runs RuboCop with rubocop-rspec, bundler-audit, actionlint, inline RBS
+checks, specs, and an isolated installed-gem smoke test. Run `bundle exec rake
+lint`, `audit`, `workflows`, `types`, `spec`, `package` or `smoke` separately.
+Dependency auditing uses the ignored lockfile from `bundle install`.
+
+Keep runtime dependencies limited to RuboCop. Cover lifecycle behavior with
+real subprocesses and fake native boundaries. Specs run in random order and
+report their seed. Reproduce an ordering failure with `bundle exec rspec --seed
+<seed> --bisect`.
+
+`rake types` checks annotation coverage across authored Ruby files, generates
+inline RBS, and uses Steep for implementations in `lib/` and `script/`. Specs
+and build configuration receive annotation and signature validation, not
+implementation checking. Generated signatures live in ignored `tmp/` during
+development and inside the built gem under `sig/`, never in the source tree.
+`sig/dependencies.rbs` declares the private RuboCop and RubyGems boundaries that
+bundled signatures lack.
+
+The smoke task installs the built gem and RuboCop's dependency closure in a
+temporary gem home, then checks clean and offending inspections without loading
+companion gems. Modern CI lanes build the canonical package and verify its
+generated runtime signatures. The `pure-rubocop` lane builds a source artifact
+in isolation to check the runtime-only dependency closure without development
+gems.
+
+## Runtime compatibility
+
+The gem targets MRI Ruby 2.1 or newer and RuboCop 0.52.0 or newer. Use
+`Gemfile.compat` and `RUBOCOP_VERSION` to select the runtime pair:
+
+```sh
+export BUNDLE_GEMFILE=Gemfile.compat
+export RUBOCOP_VERSION=0.52.0
+bundle install
+bundle exec ruby script/compat.rb
+```
+
+On Ruby 2.1 install Bundler 1.17.3 first. The compatibility harness checks
+done, error and idle outcomes, first Ctrl-C, output and stderr parity, silent
+modes, File `--out` finalization and idempotent hooks against the actual
+selected executable. It exits nonzero on any failed assertion. Do not treat a
+smoke-only lane as full behavior coverage.
+
+Executed pairs are listed in the README. Remove `Gemfile.compat.lock` before
+changing RuboCop versions and keep it out of commits. Supporting an older
+runtime does not extend its upstream security maintenance.
+
+## Release
+
+Release reviewed commits on remote `main`:
+
+```sh
+gh workflow run release.yml --ref main -f version=NEW_VERSION
+```
+
+Use a stable `major.minor.patch` version without a `v` prefix. The workflow
+captures `main`, updates `VERSION`, builds changelog notes from non-merge
+subjects since the previous tag, tests the exact prepared commit, then pushes
+the commit and tag atomically. Publication resumes an existing tag instead of
+releasing newer commits.
+
+Before the first publication, configure a RubyGems pending Trusted Publisher
+for owner `cosgroveb`, repository `rubocop-osc7501`, workflow `release.yml`.
+Store a write-enabled repository deploy key as `RELEASE_DEPLOY_KEY`. The publish
+job uses OIDC for RubyGems and the workflow token for the GitHub Release.
+
+Update user-visible behavior documentation and write commit subjects that
+describe the change, because release notes use them. Do not maintain
+`Unreleased` entries by hand.
+
+## Live terminal check
+
+Encoded-frame specs do not prove display or notifications. Check these cases
+manually in Rex or tmux against a built gem before making a display claim:
+
+1. Create `sample.rb` with a clean file and `slow_cop.rb` with a slow cop:
+
+   ```ruby
+   # frozen_string_literal: true
+
+   module RuboCop
+     module Cop
+       module Manual
+         class Slow < Base
+           def on_send(_node)
+             200.times { sleep 0.1 }
+           end
+         end
+       end
+     end
+   end
+   ```
+
+2. Run the slow inspection and confirm working status is visible during the
+   cop delay, then `done` on exit 0:
+
+   ```sh
+   RUBOCOP_OSC7501=force bundle exec rubocop --no-server \
+     --require rubocop/osc7501 --require ./slow_cop.rb \
+     --format progress --format RuboCop::OSC7501::Formatter sample.rb
+   ```
+
+3. Add an offense and repeat without the slow cop. Confirm `error` accompanies
+   exit 1 and the ordinary offense output remains readable.
+4. Start the slow command again and press Ctrl-C once. Confirm `idle` is shown
+   and the process exits nonzero without a second record.
+5. Repeat with `RUBOCOP_OSC7501=off` and confirm no status is shown.
+
+Live Rex and tmux acceptance was not run on 2026-11-13. Record the terminal,
+tmux and gem versions when someone performs it.

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 [yyyy] [name of copyright owner]
+
+   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/README.md

@@ -0,0 +1,155 @@
+# rubocop-osc7501
+
+Report finite direct RuboCop inspections through OSC 7501 terminal status while
+preserving ordinary formatter output and exit behavior.
+
+Requires MRI Ruby 2.1 or newer and RuboCop 0.52.0 or newer. The runtime
+dependency is RuboCop only.
+
+## Install
+
+```ruby
+# Gemfile
+gem 'rubocop-osc7501', require: false
+```
+
+Run `bundle install`.
+
+## Use
+
+Select the formatter alongside the ordinary formatter you already use:
+
+```sh
+bundle exec rubocop --require rubocop/osc7501 \
+  --format progress --format RuboCop::OSC7501::Formatter
+```
+
+On RuboCop versions with the server, add `--no-server` for the supported
+direct-process path:
+
+```sh
+bundle exec rubocop --no-server --require rubocop/osc7501 \
+  --format progress --format RuboCop::OSC7501::Formatter
+```
+
+Selecting only the OSC formatter deliberately requests no ordinary diagnostics.
+
+Equivalent project arguments preserve your formatter selection:
+
+```text
+--require rubocop/osc7501
+--format progress
+--format RuboCop::OSC7501::Formatter
+```
+
+`examples/.rubocop` is a RuboCop argument file, not YAML. It contains the
+`--require` and formatter arguments above. Copy it beside `.rubocop.yml` when
+every invocation from that directory should select both formatters. Do not add
+these arguments to a shared configuration when other users do not have the gem.
+
+Requiring `rubocop/osc7501` registers the formatter and installs inert hooks.
+Without formatter selection, or with reporting off, an inspection produces no
+records.
+
+## Output controls
+
+| Setting | Behavior |
+| --- | --- |
+| `RUBOCOP_OSC7501=auto` | Default. Report when the selected formatter output is a TTY and `TERM` is not `dumb`. |
+| `RUBOCOP_OSC7501=force` | Report even to redirected output or a file. |
+| `RUBOCOP_OSC7501=off` | Disable reporting and bypass eager formatter construction. |
+| any other value | Raise `ArgumentError` for a selected inspection. |
+
+RuboCop assigns each formatter its own output. Existing `--out` destinations
+remain attached to their original formatter. When reporting is enabled and that
+output is a File, the adapter writes through its own duplicate so the final
+record survives RuboCop closing the original. It closes only that duplicate.
+
+## What is reported
+
+One root record per supported invocation has `app=rubocop`, `title=RuboCop`, no
+identity and no numeric progress. The first frame appears before target
+discovery and old parallel cache warming. Results use an aggregate message such
+as `3/10 file results, 7 reported offenses`. The adapter does not claim a
+current filename or recompute RuboCop's failure threshold.
+
+File-result updates are throttled to one per 0.1 seconds on a monotonic clock.
+Initial and final records bypass the throttle. Counts reflect delivered
+formatter callbacks and their displayed offenses.
+
+Normal return with status 0 reports `done`. A nonzero status reports `error`.
+A captured runner abort reports `idle`, so the first Ctrl-C does not appear as a
+lint failure. An escaping `Interrupt` or successful `SystemExit` reports
+`idle`. An unsuccessful `SystemExit` or other escaping exception reports
+`error`. The exception identity and exit status stay unchanged. The formatter's
+`finished` callback never publishes a terminal result.
+
+## Boundaries
+
+Supported: finite direct CLI inspections, including autocorrection, fail-level,
+fail-fast, parallel runs, multiple formatters, and `--out` files. Help,
+version, show-cops, docs/explain, LSP, MCP, initialization, target listing and
+automatic configuration generation produce no records. Embedded `Runner` calls
+without a CLI invocation are outside scope.
+
+Server, editor and watch sessions are not supported in the first release. Auto
+mode naturally stays silent when output is redirected, and force is a detection
+override rather than a server claim. The adapter never reopens `/dev/tty`,
+installs a signal handler, or adds an `at_exit` hook. A second Ctrl-C using
+immediate exit, `SIGKILL`, and other forced termination can leave the last record
+in place.
+
+Earlier formatter construction is intentional: the adapter builds the
+configured native formatter set before discovery so reporting starts early.
+This can open configured output files before a target discovery failure. A
+formatter set that returns successfully has its still-open File outputs closed
+during cleanup. If construction fails partway, native partial allocations are
+left as RuboCop made them, adapter-owned duplicates are closed, and the primary
+exception is preserved. The adapter does not reconstruct the native set.
+
+Concurrent independent top-level invocations can overwrite the same terminal
+root record, as with the sibling gems. No terminal, display, dismissal or
+notification guarantee follows from encoded frames. Live Rex and tmux
+acceptance has not been verified.
+
+Messages are bounded to 2048 decoded UTF-8 bytes after ANSI, control and
+whitespace sanitization. Terminal formatting is removed. Writer I/O failures
+disable reporting without closing borrowed streams or replacing the command's
+result.
+
+## Compatibility
+
+The candidate floor is MRI Ruby 2.1 and RuboCop 0.52.0, derived from
+`CLI#execute_runners`, `Runner#aborting?` and the formatter API. No upper bound
+is claimed.
+
+Executed acceptance on 2026-11-13:
+
+| Ruby | RuboCop | Result |
+| --- | --- | --- |
+| 2.1.10 | 0.52.0 | compatibility harness passed |
+| 2.1.10 | 0.57.2 | compatibility harness passed |
+| 2.6.5 | 1.50.0 | compatibility harness passed |
+| 3.4.12 | 1.80.0 | compatibility harness passed |
+| 3.4.12 | 1.92.2 | specs and compatibility harness passed |
+| 3.4.12 | 0.52.0 | not supported: RuboCop fails before inspection on Psych `safe_load` arity |
+
+Ruby 2.4 with RuboCop 1.0.0 was not available on the implementation machine.
+Ruby 3.4 with RuboCop 0.52.0 installs after adding current standard-library
+gems, then fails inside RuboCop before inspection with `Psych.safe_load` arity
+(`given 5, expected 1`). That pair is not supported. macOS hosted checks and
+the remaining CI matrix were not run locally. An unavailable runtime is a
+verification limit, not evidence of compatibility. Other Ruby engines are
+unverified.
+
+## Development
+
+```sh
+bundle install
+bundle exec rake
+```
+
+The default task runs RuboCop, bundler-audit, actionlint, inline RBS checks,
+specs, and installed-gem smoke tests. `bundle exec rspec` runs specs alone.
+See [CONTRIBUTING.md](CONTRIBUTING.md) for compatibility lanes, typing and
+release setup. Report vulnerabilities through [SECURITY.md](SECURITY.md).

data/SECURITY.md

@@ -0,0 +1,18 @@
+# Security policy
+
+## Supported versions
+
+I provide security fixes for the latest released version of rubocop-osc7501.
+Upgrade before checking whether a problem still occurs. Older releases do not
+receive security backports.
+
+## Report a vulnerability
+
+Use [GitHub private vulnerability reporting](https://github.com/cosgroveb/rubocop-osc7501/security/advisories/new).
+Do not disclose vulnerabilities in public issues or pull requests.
+
+Include the affected gem, Ruby, RuboCop and terminal versions, reproduction
+steps, and impact. Remove credentials and unrelated private data. I coordinate
+fix and disclosure timing with the reporter and cannot guarantee deadlines.
+
+For ordinary bugs, use the [issue tracker](https://github.com/cosgroveb/rubocop-osc7501/issues).

data/examples/.rubocop

@@ -0,0 +1,6 @@
+--require
+rubocop/osc7501
+--format
+progress
+--format
+RuboCop::OSC7501::Formatter

data/lib/rubocop/osc7501/formatter.rb

@@ -0,0 +1,47 @@
+# frozen_string_literal: true
+# rbs_inline: enabled
+
+require 'rubocop/formatter/base_formatter'
+require_relative 'lifecycle'
+require_relative 'writer'
+
+module RuboCop
+  module OSC7501
+    # Native RuboCop formatter selected alongside ordinary output. It only
+    # observes callbacks; the private lifecycle owns election and outcomes.
+    class Formatter < RuboCop::Formatter::BaseFormatter
+      # @rbs @invocation: Lifecycle::Invocation?
+      # @rbs @writer: Writer?
+
+      #: (untyped output, ?untyped options) -> void
+      def initialize(output, options = {})
+        super
+        @invocation = Lifecycle.current
+        @writer = nil
+        invocation = @invocation
+        return unless invocation
+        # v1 selection is the documented Formatter class only, so subclasses cannot win election.
+        return unless self.class.equal?(Formatter)
+        return if invocation.reporter
+
+        writer = Writer.new(output, mode: invocation.mode)
+        @writer = writer
+        invocation.add_formatter(self, writer)
+      end
+
+      #: (untyped files) -> nil
+      def started(files)
+        invocation = @invocation
+        invocation.started(self, files.length) if invocation
+        nil
+      end
+
+      #: (untyped file, untyped offenses) -> nil
+      def file_finished(_file, offenses)
+        invocation = @invocation
+        invocation.file_finished(self, offenses) if invocation
+        nil
+      end
+    end
+  end
+end