Title: Temporarily disable Renovate during Shai-Hulud wave

Summary

Because of the current Shai-Hulud supply-chain wave, we want to temporarily disable Renovate in this repository so that no new automated dependency updates are opened until it’s safe to resume. The change must be:

• Repo-local (doesn’t affect other repos)
• Easily reversible (flip a flag or delete a small config file)

This issue is intended to be implemented by GitHub Copilot via a small configuration change and PR.

Task for Copilot

Goal: Update this repo’s Renovate configuration so that Renovate is disabled via the enabled flag, and clearly document how to turn it back on.

1. Locate the Renovate configuration for this repo

Search for a Renovate config file in this repository. Check, in roughly this order:

• renovate.json
• renovate.json5
• .github/renovate.json
• .github/renovate.json5
• .renovaterc
• .renovaterc.json
• .renovaterc.json5
• package.json (inside a "renovate" section)

Use the first one you find; do not modify multiple configs.

2. If a Renovate config file already exists

Case A: Config is in a dedicated Renovate file
(e.g. renovate.json, .github/renovate.json, .renovaterc*, or renovate.json5)

1. Ensure there is a top-level enabled flag set to false.
   Example (JSONC is allowed in Renovate config files, so comments are OK):

  {
    // SHAI-HULUD FREEZE:
    // Flip this to true or remove this flag when it is safe
    // to re-enable Renovate.
    "enabled": false,

    // ...existing Renovate config...
  }

2. Do not alter any other configuration options.

3. Create a PR

Copilot should:

1. Commit the minimal change described above on a new branch.

2. Open a PR with a title similar to:

chore: temporarily disable Renovate (Shai-Hulud freeze)

3. In the PR description, briefly explain:

   • That Renovate is being disabled due to the Shai-Hulud wave.

   • That re-enabling is as simple as:

     • Setting "enabled": true, or
     • Removing the enabled flag, or
     • Deleting .github/renovate.json if that file was created for this purpose.

Re-enable procedure (for future humans or Copilot)

When the Shai-Hulud danger has passed:

• If we edited an existing config file:

  • Change "enabled": false to "enabled": true, or
  • Remove the enabled property entirely if we want to go back to previous behavior.

• If we created .github/renovate.json with only "enabled": false:

  • Delete .github/renovate.json, or
  • Change "enabled": false to "enabled": true.

Open a small PR with a title like:

chore: re-enable Renovate after Shai-Hulud

Acceptance criteria

• Renovate is disabled in this repository via the enabled: false flag.
• No new Renovate PRs or branches are created once the change is on the default branch.
• The configuration clearly documents how to re-enable Renovate with a single, obvious edit (flip a boolean or delete one file).