SDBL: virtual table colouring is structural, not lexical

Virtual-table names like 'Остатки' / 'СрезПоследних' / 'Обороты' double
as legitimate query aliases — code like
`КАК Остатки … ВЫБРАТЬ Остатки.Количество` is normal SDBL. The previous
global VtKw specializer painted every such reference in the
className/Namespace yellow even when the user clearly meant an alias,
which is exactly what bsl-parser sidesteps with its DOT_MODE lexer state.

Replaced the lexer-level recognition with a structural MdoRef rule:

  MdoRef { MdoKw (!mdoTail Dot Identifier)* }

The dotted tail is greedy (the !mdoTail precedence biases shift over
reduce) so 'РегистрНакопления.ТоварыНаСкладах.Остатки' parses as a
single MdoRef with two tail components. The styleTags now colours
'MdoRef/Identifier' as className — that's the only place where
'Остатки' lights up yellow now. Aliases and field-access references
stay plain variableName.

Side cleanup:
- Removed the VtKw term from the SDBL specializer table, terms file
  and Parameter/sdblName alternative.
- Removed the corresponding 'VtKw → t.className' styleTag entry.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: nixel2007

src/index.ts

@@ -103,12 +103,16 @@ export const sdblLanguage = sdblParser.configure({
       FuncKw: t.function(t.keyword),
       // Built-in type names (Булево/Число/Строка used in CAST etc.).
       TypeKw: t.typeName,
-      // Metadata-object roots (Справочник/Документ/РегистрСведений/…). The
-      // bsl-language-server tags these as Namespace at the LSP level.
+      // Metadata-object roots (Справочник/Документ/РегистрСведений/…).
+      // bsl-language-server tags them as Namespace at the LSP level.
       MdoKw: t.namespace,
-      // Virtual table suffixes (.Остатки, .СрезПоследних, .Обороты). Tagged
-      // as className so themes can distinguish them from base metadata.
-      VtKw: t.className,
+      // Identifier components inside an MdoRef path become Class — the
+      // table name (`Контрагенты` in `Справочник.Контрагенты`) and the
+      // optional virtual-table suffix (`Остатки` in
+      // `РегистрНакопления.ТоварыНаСкладах.Остатки`) both qualify. Outside
+      // of MdoRef the same words stay as plain variableName so query
+      // aliases like `КАК Остатки` don't get the metadata-class colour.
+      "MdoRef/Identifier": t.className,
       // Field accessors (ТочкаМаршрута, ROUTEPOINT) — propertyName tier.
       FieldKw: t.propertyName,
       // Literals.
@@ -126,7 +130,7 @@ export const sdblLanguage = sdblParser.configure({
       // tag so the parameter renders as one visual block. We enumerate the
       // keyword categories because @lezer/highlight resolves at the leaf
       // level and the global FuncKw / StmtKw / etc. tags would otherwise win.
-      "Parameter/Ampersand Parameter/Identifier Parameter/StmtKw Parameter/OpKw Parameter/FuncKw Parameter/TypeKw Parameter/MdoKw Parameter/VtKw Parameter/FieldKw Parameter/BoolLit Parameter/NullLit Parameter/UndefinedLit": t.special(t.variableName),
+      "Parameter/Ampersand Parameter/Identifier Parameter/StmtKw Parameter/OpKw Parameter/FuncKw Parameter/TypeKw Parameter/MdoKw Parameter/FieldKw Parameter/BoolLit Parameter/NullLit Parameter/UndefinedLit": t.special(t.variableName),
       // Punctuation
       "LParen RParen": t.paren,
       // `{...}` configuration blocks — tag the whole group as t.meta so a

src/sdbl-tokens.ts

@@ -8,7 +8,7 @@
 // SDBLLexer.g4`.
 
 import {
-  StmtKw, OpKw, FuncKw, TypeKw, MdoKw, VtKw, FieldKw,
+  StmtKw, OpKw, FuncKw, TypeKw, MdoKw, FieldKw,
   BoolLit, NullLit, UndefinedLit
 } from "./sdbl.grammar.terms"
 
@@ -166,27 +166,20 @@ const MDO_WORDS = [
   "externaldatasource", "внешнийисточникданных"
 ]
 
-// Virtual table suffixes that appear after the metadata-object name:
-// e.g. `РегистрНакопления.Товары.Остатки`, `РегистрСведений.Курсы.СрезПоследних`.
-const VT_WORDS = [
-  "balance", "остатки",
-  "balanceandturnovers", "остаткииобороты",
-  "boundaries", "границы",
-  "drcrturnovers", "оборотыдткт",
-  "extdimensions", "субконто",
-  "recordswithextdimensions", "движенияссубконто",
-  "scheduledata", "данныеграфика",
-  "slicefirst", "срезпервых",
-  "slicelast", "срезпоследних",
-  "taskbyperformer", "задачипоисполнителю",
-  "turnovers", "обороты",
-  "actualactionperiod", "фактическийпериоддействия",
-  "table", "таблица",
-  "cube", "куб",
-  "dimensiontable", "таблицаизмерения"
-]
+// Virtual-table suffixes are NOT globally specialized. Words like "Остатки",
+// "Обороты", "СрезПоследних" double as legitimate query aliases (e.g.
+// `ВЫБРАТЬ Остатки.Количество ИЗ ... КАК Остатки`), and globally tagging
+// them as VtKw paints those alias references yellow even when the user
+// never intended a metadata-object reference. ANTLR's BSL parser side-steps
+// this with a lexer DOT_MODE that only recognises BALANCE_VT etc. right
+// after a dot inside a metadata path; we cannot replicate that mode purely
+// at the specializer level, so we let the structural MdoRef rule in the
+// grammar collect them as ordinary Identifiers and rely on contextual
+// styleTags (MdoRef/Identifier → className) to colour them when they sit
+// at the tail of a metadata path.
 
-// Special field accessors (route points etc.).
+// Special field accessors (route points etc.). These are unambiguous —
+// `ТочкаМаршрута` doesn't double as an alias name in real queries.
 const FIELD_WORDS = [
   "routepoint", "точкамаршрута", "точки"
 ]
@@ -197,7 +190,6 @@ for (const w of OP_WORDS) MAP[w] = OpKw
 for (const w of FUNC_WORDS) MAP[w] = FuncKw
 for (const w of TYPE_WORDS) MAP[w] = TypeKw
 for (const w of MDO_WORDS) MAP[w] = MdoKw
-for (const w of VT_WORDS) MAP[w] = VtKw
 for (const w of FIELD_WORDS) MAP[w] = FieldKw
 
 // Literals

src/sdbl.grammar

@@ -22,8 +22,7 @@ fragment {
   OpKw |
   FuncKw |
   TypeKw |
-  MdoKw |
-  VtKw |
+  MdoRef |
   FieldKw |
   BoolLit |
   NullLit |
@@ -40,6 +39,18 @@ fragment {
   Punct
 }
 
+// Metadata-object reference path: `Справочник.Контрагенты`,
+// `РегистрНакопления.ТоварыНаСкладах.Остатки`, etc. Only inside this
+// structure do the trailing identifier components mean "table name" and
+// "virtual table" — at the lexer level we keep them as plain Identifier
+// so they don't get the namespace/class colour in other positions
+// (e.g. an alias `Остатки` defined via `КАК Остатки`).
+//
+// `!mdoTail` biases the parser to shift each `Dot Identifier` into the
+// current MdoRef rather than reduce early (which would leak the dot into
+// a sibling Punct(Dot) and split the path).
+MdoRef { MdoKw (!mdoTail Dot Identifier)* }
+
 ParenGroup { LParen fragment* RParen }
 
 // `{...}` blocks in SDBL carry data-composition-system parameters that the
@@ -57,7 +68,7 @@ BraceGroup { LBrace fragment* RBrace }
 // stops being recognised.
 Parameter { Ampersand sdblName }
 sdblName {
-  Identifier | StmtKw | OpKw | FuncKw | TypeKw | MdoKw | VtKw | FieldKw |
+  Identifier | StmtKw | OpKw | FuncKw | TypeKw | MdoKw | FieldKw |
   BoolLit | NullLit | UndefinedLit
 }
 
@@ -68,6 +79,12 @@ Punct { Comma | Semicolon | Colon | Dot | Hash }
 
 // ---- Skipping ----
 
+@precedence {
+  // Used by MdoRef to prefer extending the path with another `Dot
+  // Identifier` over reducing the MdoRef early.
+  mdoTail @left
+}
+
 @skip { space | LineComment }
 
 // ---- Tokens ----
@@ -138,7 +155,6 @@ Punct { Comma | Semicolon | Colon | Dot | Hash }
   FuncKw,
   TypeKw,
   MdoKw,
-  VtKw,
   FieldKw,
   BoolLit,
   NullLit,

src/sdbl.grammar.terms.d.ts

@@ -6,7 +6,6 @@ export const OpKw: number
 export const FuncKw: number
 export const TypeKw: number
 export const MdoKw: number
-export const VtKw: number
 export const FieldKw: number
 export const BoolLit: number
 export const NullLit: number