Add JSON output method for doctor

[SMillerDev]

Add an option to output the brew doctor results in easily parseable JSON output.

---

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them? Performance claims (e.g. "this is faster") must include Hyperfine benchmarks.
• Have you written new tests (excluding integration tests) for your changes? Here's an example.
• Have you successfully run brew lgtm (style, typechecking and tests) with your changes locally?

---

• AI was used to generate or assist with generating this PR.

---

[MikeMcQuaid]

Great idea but I think this needs a lot of work before we can merge. We need to actually provide structured output from all diagnostics rather than relying on regexes.

[Copilot]

Pull request overview

This PR adds JSON output support to brew doctor, making diagnostic results easier for scripts and tools to consume.

Changes:

• Adds a --json switch to brew doctor.
• Builds and prints a JSON object containing a support tier and findings.
• Adds the generated Sorbet RBI predicate and a basic command spec.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 4 comments.

File	Description
Library/Homebrew/cmd/doctor.rb	Adds JSON output generation for doctor diagnostics.
Library/Homebrew/sorbet/rbi/dsl/homebrew/cmd/doctor.rbi	Adds the json? argument predicate.
Library/Homebrew/test/cmd/doctor_spec.rb	Adds a basic spec for brew doctor --json.

Files not reviewed (1)

• Library/Homebrew/sorbet/rbi/dsl/homebrew/cmd/doctor.rbi: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[SMillerDev]

Fair enough, I'd suggest a structure like this:

• Title
• Issue description
• Tier indicator
• Affects (list of full package names)
• links: (list of URLs)
• Remediation
  • commands (list)
  • text (or empty)

That we can then turn into a string or json object in the output.

[MikeMcQuaid]

@SMillerDev yeh something like that sounds good. Also may want to have things like: affected formulae/casks, relevant URL(s).

[SMillerDev]

Adjusted to include that

[MikeMcQuaid]

@SMillerDev looks good except we need to return the structured data from diagnostics rather than using regex on their string output.

[SMillerDev]

Yeah, fully planning to do that. Just wanted to work out a structure here before I get on reshaping all audit check output 😅

[SMillerDev]

JSON output:

{
  "tier": 1,
  "findings": [
    {
      "title": "Deprecated or disabled formulae",
      "issue": "Some installed formulae are deprecated or disabled.",
      "tier": 1,
      "affects": [
        "php@7.2",
        "mysql@8.0"
      ],
      "links": [],
      "remediation": {
        "commands": [],
        "text": "You should find replacements for the following formulae:\nmysql@8.0\n  php@7.2\n"
      }
    }
  ]
}

[MikeMcQuaid]

Thanks, this is looking good! Will take another look when 🟢 and comments addressed. Happy to discuss more before addressing.