chore(renovate): normalize requirements.lock header to equals-form

[stranske]

Renovate's pip-compile manager (enabled fleet-wide via the shared preset, stranske/Workflows#2406) parses the lock header to reconstruct the uv pip compile command and requires every option in equals form (--extra=dev, --output-file=requirements.lock). This repo's lock header was in space form, so Renovate raised a non-fatal Option ... must have equal sign warning and silently skipped the lock — it was never regenerated on dependency bumps.

This rewrites only the header line to equals form; the resolved pins are byte-identical (header-only diff).

Verified with npx renovate@43 --platform=local --dry-run=extract on a sibling repo: before = pip-compile error … must have equal sign (skipped); after = lock extracted, no error.

Part of the fleet pip-compile lock-regen rollout (Workflows #2406 enabled the manager; consumer lock headers were space-form and needed normalizing).

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• requirements.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4242a8f3-0f9e-43b8-8579-43c55d1f111a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/lock-header-equals-form

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[agents-workflows-bot]

Workflow source needed

PR #300 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely.

Please do one of:

• Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
• Check one Workflow Source option in the PR body.
• Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
• Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.

[github-actions]

Workflow state fingerprint for Agents Gate Followups. Do not edit.