[Muhtasim-Munif-Fahim]

Summary

Three lint findings were the only ones without a fixHint, so lint and check showed the message with no suggestion of what to change. Each one now has a short, concrete hint in the style of the neighbouring rules:

• invalid_composition_variables_declaration, when an entry is not an object (packages/lint/src/rules/composition.ts): shows the shape of a valid entry, {"id":"title","type":"string","label":"Title","default":"Hello"}.
• invalid_composition_variables_declaration, when an entry is missing or has an invalid id/type/label/default: names the entry index and shows the same example shape.
• css_parse_error (packages/lint/src/rules/core.ts): points at the reported line and the usual causes (an unclosed brace, quote or comment, or a missing semicolon).

Messages, codes and severities are unchanged.

Closes #5392

Verification

• The existing tests for these codes now assert the hint is present, and there is a new test for the "entry is not an object" branch. Without the source change, those 4 tests fail.
• bun run --cwd packages/lint test: 20 files, 908 tests passed.
• oxfmt --check and oxlint on packages/lint/src/rules/ are clean, and tsc --noEmit passes in packages/lint.

AI assistance was used to help write the patch and run tests; I reviewed the change.

[jrusso1020]

Approving at 73d4fb36. Thanks!

It adds a fixHint to all three findings from #5392, the two invalid_composition_variables_declaration branches and css_parse_error, and changes nothing else.

• I checked the CSS hint's causes against PostCSS on malformed CSS: an unclosed brace, quote or comment, and a missing semicolon all fail to parse there.
• The rule tests pass, and the full lint suite passes 908/908. With the source change reverted, 4 of the new assertions fail.
• Merges cleanly with main.

Small optional follow-up: the existing "checks a declaration on the composition root too" test doesn't assert the fixHint yet. The issue's acceptance criteria ask for that, so it's worth one more line.

— Rames

[jrusso1020]

Thanks for this! It's approved and CI is green, but main only accepts signed commits, and your commit 73d4fb36 isn't signed, so it can't merge yet.

Quickest fix with an SSH key you already use for GitHub:

git config --global gpg.format ssh
git config --global user.signingkey ~/.ssh/id_ed25519.pub   # your public key
git config --global commit.gpgsign true
git commit --amend --no-edit -S
git push --force-with-lease

Also add that same key to GitHub as a Signing key (Settings → SSH and GPG keys → New SSH key → Key type: Signing key), and make sure the commit's email is a verified email on your account. Docs: Signing commits and Telling Git about your signing key.

Once the commit shows Verified, we'll re-approve and merge.

— Rames

[miguel-heygen]

Checked at fdf8d59. The three hints land where the findings are raised (composition.ts for both variables-entry branches, core.ts for css_parse_error), and each is pinned by a test that reads the hint.

I ran src/rules/composition.test.ts and src/rules/core.test.ts: 358 passed. With composition.ts and core.ts put back to the merge base, 4 of them fail, so the tests guard the change.

Verdict: APPROVE
Reasoning: small, scoped to the issue, tests fail without the change, CI green.