chore(linter): declare_oxc_lint! accept docs from a const

[Sysix]

Updates the declare_oxc_lint! proc-macro parser/codegen to support sourcing rule documentation from a shared constant (via a docs = path::TO_CONST option) in addition to inline doc comments.

[Sysix]

• refactor(linter): move expect-expect rule to shared and create own rule for vitest #18630
• refactor(linter): move consistent-test-it rule to shared and crate own rule for vitest #18605
• refactor(linter): move valid-title rule to shared and crate own rule for vitest #18467
• chore(linter): declare_oxc_lint! accept docs from a const #18603 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull request overview

Updates the declare_oxc_lint! proc-macro parser/codegen to support sourcing rule documentation from a shared constant (via a docs = path::TO_CONST option) in addition to inline doc comments.

Changes:

• Introduces a DocumentationSource enum to represent inline docs vs. a referenced constant path.
• Extends macro argument parsing with a docs = ... option and improves unknown-key handling by returning syn::Error instead of panicking.
• Adjusts generated RuleMeta::documentation() to emit docs based on the selected documentation source.

---

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

[Sysix]

@camc314 any thoughts about this solution? Would wait for your approval before restacking and continue the work

[camc314]

Yeah this approach looks good - I think the name "shared" might be a little to ambiguous - maybe we want something to indicate that it's shared between the two vitest/jest plugins?

[codspeed-hq]

Merging this PR will not alter performance

✅ 4 untouched benchmarks
⏩ 52 skipped benchmarks¹

---

_{Comparing 01-26-chore_linter_declare_oxc_lint_accept_docs_from_a_const (330758b) with main (5c104ff)²}

Footnotes

1. 52 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (b82d37c) during the generation of this report, so 5c104ff was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[Sysix]

I think the name "shared" might be a little to ambiguous

The goal is to share other plugins rule like no-negated-condition and unicorn/no-negated-condition.
https://github.com/oxc-project/oxlint-migrate/blob/main/scripts/constants.ts#L17

They have only one different default option.

Updated the branch, checking for the others PRs (broken because of conflicts)

[Sysix]

@camc314 After a test migration of a project, I found #18975 which would help us to split the logic for valid-expect with (second?) configuration.
Would love to see a movement here :)