Point YAML ledger explicit-key cases at the specific issue, not the list

Three YAML cases (block scalar as an explicit key, anchor in `?`-key position, bare
`?` multi-line sequence key) cited RedCMD/YAML-Syntax-Highlighter#1 — but that is the
cross-ecosystem aggregator issue LIST, not a specific issue. Retarget them to
#12 ("YAML issues"), RedCMD's multi-item report against
Monogram where the anchor and explicit-multiline-key repros are filed verbatim and
the block-scalar-as-key sits in the same explicit-key scope. The six ecosystem cases
keep their specific upstream cites (tmbundle / atom / vscode). No verdict change
(YAML still 9/9 vs official 8/9).

Author: johnsoncodehk

README.md

@@ -195,7 +195,7 @@ _Each hand-written **official** grammar vs Monogram's **derived** one, on the bu
 #### YAML
 | issue | Monogram | official |
 |---|:--:|:--:|
-| [RedCMD/YAML-Syntax-Highlighter#1](https://github.com/RedCMD/YAML-Syntax-Highlighter/issues/1) — a block scalar used AS an explicit key is scoped as a key name | ✓ | · |
+| [johnsoncodehk/monogram#12](https://github.com/johnsoncodehk/monogram/issues/12) — a block scalar used AS an explicit key is scoped as a key name | ✓ | · |
 
 <details><summary>… and 8 more both grammars already handle (✓ / ✓)</summary>
 
@@ -205,8 +205,8 @@ _Each hand-written **official** grammar vs Monogram's **derived** one, on the bu
 | [atom/language-yaml#114](https://github.com/atom/language-yaml/issues/114) — a `#` in a block-scalar body is content, not a comment | ✓ | ✓ |
 | [tmbundle#38](https://github.com/textmate/yaml.tmbundle/issues/38) — a block scalar with leading/internal EMPTY lines stays one string region | ✓ | ✓ |
 | [tmbundle#18](https://github.com/textmate/yaml.tmbundle/issues/18) — JSON-ish punctuation (`{`/`}`) and a tab indicator inside a block scalar stay content | ✓ | ✓ |
-| [RedCMD/YAML-Syntax-Highlighter#1](https://github.com/RedCMD/YAML-Syntax-Highlighter/issues/1) — an anchor `&a` in explicit-key (`?`) position is still an anchor | ✓ | ✓ |
-| [RedCMD/YAML-Syntax-Highlighter#1](https://github.com/RedCMD/YAML-Syntax-Highlighter/issues/1) — a bare `?` opening an explicit multi-line sequence key is the map-key indicator | ✓ | ✓ |
+| [johnsoncodehk/monogram#12](https://github.com/johnsoncodehk/monogram/issues/12) — an anchor `&a` in explicit-key (`?`) position is still an anchor | ✓ | ✓ |
+| [johnsoncodehk/monogram#12](https://github.com/johnsoncodehk/monogram/issues/12) — a bare `?` opening an explicit multi-line sequence key is the map-key indicator | ✓ | ✓ |
 | [atom/language-yaml#119](https://github.com/atom/language-yaml/issues/119) — an escape inside a double-quoted KEY is highlighted | ✓ | ✓ |
 | [tmbundle#39](https://github.com/textmate/yaml.tmbundle/issues/39) — a plain scalar resolving to `null` is lexically a string that resolves to a constant | ✓ | ✓ |
 

test/yaml-issue-cases.ts

@@ -2,10 +2,12 @@
 // side effects on import). The "official" YAML grammar is the MAINTAINED RedCMD/YAML-Syntax-
 // Highlighter (microsoft/vscode#232244 switched VS Code off the dead textmate/yaml.tmbundle to it),
 // so YAML's baseline is a maintained competitor — most of these it ALSO solves. Each id cites the
-// underlying upstream tracker; the canonical aggregator is RedCMD/YAML-Syntax-Highlighter#1
-// ("Pre-existing grammar issues"), which links the VS Code / textmate-yaml.tmbundle / atom-language-
-// yaml issues. The original report against Monogram was johnsoncodehk/monogram#12, since superseded
-// by RedCMD's organized #1. Shared by the README cross-language ✓ table (test/issue-table.ts).
+// most specific tracker: the ecosystem bugs filed against the official/upstream grammars (VS Code /
+// textmate-yaml.tmbundle / atom-language-yaml), and johnsoncodehk/monogram#12 ("YAML issues",
+// RedCMD's multi-item report against Monogram) for the explicit-key behaviors that have no single
+// dedicated upstream issue. RedCMD/YAML-Syntax-Highlighter#1 ("Pre-existing grammar issues") is the
+// broader cross-ecosystem aggregator that links the upstream issues. Shared by the README
+// cross-language ✓ table (test/issue-table.ts).
 //
 // Each snippet is VALID YAML; the question is whether the grammar scopes the marked span correctly.
 // Same predicate shape as html-issue-cases.ts: {id, title, src, at, nth?, want:(scope)=>boolean}.
@@ -37,11 +39,11 @@ export const cases: YamlCase[] = [
     at: '}', want: isBlockScalar },                                                  // the `}` is literal block-scalar content, not punctuation — and the indicator follows a TAB (tmbundle#18: `{ }` inside literal style breaks highlighting; #17 is the sibling colon case)
 
   // ── explicit-key (`?`) constructs ──
-  { id: 'RedCMD/YAML-Syntax-Highlighter#1', title: 'an anchor `&a` in explicit-key (`?`) position is still an anchor', src: '? &a a\n: &b b\n: *a\n',
+  { id: 'johnsoncodehk/monogram#12', title: 'an anchor `&a` in explicit-key (`?`) position is still an anchor', src: '? &a a\n: &b b\n: *a\n',
     at: '&a', want: isAnchor },                                                      // `&a` after the explicit-key `?` is an anchor (entity.name.type.anchor / variable.other.anchor), not bare source — the original monogram#12 multi-item repro
-  { id: 'RedCMD/YAML-Syntax-Highlighter#1', title: 'a bare `?` opening an explicit multi-line sequence key is the map-key indicator', src: '?\n- a\n- b\n:\n- c\n- d\n',
+  { id: 'johnsoncodehk/monogram#12', title: 'a bare `?` opening an explicit multi-line sequence key is the map-key indicator', src: '?\n- a\n- b\n:\n- c\n- d\n',
     at: '?', want: isMapKeyPunct },                                                  // the lone `?` (its value is the multi-line block sequence below) is punctuation.definition.map.key.yaml — both grammars handle the explicit complex-key form
-  { id: 'RedCMD/YAML-Syntax-Highlighter#1', title: 'a block scalar used AS an explicit key is scoped as a key name', src: '? |\n  block key\n: v\n',
+  { id: 'johnsoncodehk/monogram#12', title: 'a block scalar used AS an explicit key is scoped as a key name', src: '? |\n  block key\n: v\n',
     at: 'block key', want: isTag },                                                  // MONOGRAM-ONLY ✓: Monogram scopes the block-scalar explicit key as a key NAME (entity.name.tag.yaml); the official leaves it string.unquoted.block (it has no entity.name.tag) → only-Monogram
 
   // ── quoted KEYS carry their escapes / plain scalars carry a string ancestor ──