StoneCypher / jssm / d9a755bf0d1ca31ed2250a938facbd8d2bd840de

100%

master: 100%

Pull #973

github

docs(specs): design the highlightjs-fsl repository

Researched against the live highlightjs org (66 repos), the official
3rd-party contribution guide, and eight exemplar grammars.

Key findings:

- No grammar is published under @highlightjs; all are unscoped and owned
  by their individual authors. `highlightjs-fsl` is unclaimed and needs
  no org membership. The scoped form was considered and rejected: it
  would be the only scoped package of ~60.
- The upstream repo is EMPTY (zero branches), so the first content must
  arrive by direct push; a PR is impossible. John has push+maintain but
  not admin, so CI secrets need an org owner.
- Only five conventions are actually invariant across the eight surveyed
  repos. The documented forms (src/languages/, default.txt, .expect.txt,
  export default) are followed inconsistently in the wild, and
  nonconformance fails SILENTLY -- highlightjs-luau ships both
  .expect.txt and .expected.txt in one directory and nobody noticed,
  because no grammar repo runs its language tests in CI.
- The fence syntax is not a dialect; it lives entirely in the Markdown
  info string. One grammar, aliases ['fsl', 'jssm'].
- The grammar source belongs in this monorepo (derived from the same
  token vocabulary as the TextMate builder), but the package and repo do
  not: dist/ is built by highlight.js's own tooling, and monorepo
  version lockstep would put highlightjs-fsl@6.x beside apex@1.66.

Claude-Session: https://claude.ai/code/session_01EBLDd3nmRPcpC2weqD2TD3

3869 of 3869 branches covered (100.0%)

Branch coverage included in aggregate %.

6361 of 6361 relevant lines covered (100.0%)

33378.9 hits per line