[Yash990-bit]

Summary

Previously, token-format only checked raw string literals passed as the first argument to new Token(...). Token IDs declared via template literals, constants, or type-aware identifiers were skipped.

This PR updates token-format to use resolveStaticString and getTypeServices:

• Statically validates template literals (e.g. new Token(`${PKG}:ISymbol`) and new Token(`${PKG}:kebab-case`))
• Statically validates constants and identifiers
• Adds type-aware resolution support when type services are available
• Updates rule documentation and adds unit test cases

Resolve #161

[Copilot]

🟢 Approval recommended

The focused changes reuse established utilities and include regression coverage, with no blocking issues identified; tests were not executed.

No open issues 🎉

What changed in this PR

Extends token-format beyond raw string literals using existing static-string and type-resolution utilities, addressing #161.

Changes:

• Validates resolvable templates, constants, and string-literal-typed expressions.
• Adds static and type-aware test cases.
• Documents the expanded support.

File	Description
website/​docs/​rules/​token-format.md	Documents supported token ID expressions.
tests/​jupyter-token-format.test.ts	Adds template, constant, and type-aware coverage.
src/​rules/​token-format.ts	Uses shared resolution utilities and skips spread arguments.

_{Review effort: Balanced}

[Darshan808]

I see this is in draft, but gave few feedbacks.

[Yash990-bit]

Hi @Darshan808 when you get a chance, could you please take a look at this PR?

[Darshan808]

Thanks