sarj/naming/capability-token Use kebab-case capabilities
Capabilities use one lowercase ASCII kebab-case token.
error
Examples
capability = 'request.signing'capability = 'request-signing'Why it matters
One canonical token derives stable paths without ecosystem-specific ambiguity.
How detection works
A capability is not one lowercase ASCII kebab-case token.
What is inspected
- declared component capability
How to fix it
Choose one lowercase ASCII kebab-case capability token.
- Keep distribution, import, and runtime aliases separate from this identity.
Verify
- Run repo-lint again and confirm the rule passes.