# Changelog

## Score

- CAI 58 → 60 (+1.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.3) — scores are not directly comparable.

## Lenses

- Code Health 58 → 55 (-2.9)
- Architecture 92 → 75 (-17.7)
- Maturity 73 → 71 (-2.1)
- Readiness 52 → 55 (+2.9)
- Security 63 → 67 (+4.5)
- Performance 70 → 100 (+30.3)

## Resolved (26)

- Dormant codebase
- Duplicated block (12 lines × 2) (runtime/Dart/lib/src/interval_set.dart)
- Duplicated block (12 lines × 2) (runtime/Go/antlr/v4/semantic_context.go)
- Duplicated block (15 lines × 2) (runtime/Go/antlr/v4/jcollect.go)
- Duplicated block (22 lines × 2) (runtime/Go/antlr/v4/parser_atn_simulator.go)
- Duplicated block (7 lines × 2) (runtime/Swift/Sources/Antlr4/atn/ActionTransition.swift)
- Excessive and confusingly similar overloads for string representation. `toStringTree` has 3 overloads with different parameter types (Parser, List<String?>, None). `toString` has 2 overloads (Recognizer, List<String>). This creates a high cognitive load for users trying to get a debug string. Specifically, `toStringTree()` vs `toStringTree([String]?)` vs `toStringTree(Parser)` are very similar in intent (debugging tree structure) but differ in how they resolve symbol names. Similarly, `toString(Recognizer)` vs `toString([String])` are ambiguous.
- High secret: WD-SECRET-0005 (runtime/JavaScript/package-lock.json)
- Inconsistent naming convention for text accessors compared to other stream types. While `ANTLRInputStream` and `BufferedTokenStream` use `getText(Interval)` or similar explicit range-based methods, `Lexer` uses simple `getText()` and `setText()` which implies getting/setting the *current* token's text or internal buffer state without explicit context. This is a minor domain difference (Lexer state vs Stream content), but the lack of `getCharIndex`/`setCharIndex` symmetry with `getLine`/`setLine` is also notable. However, the most glaring inconsistency is between `Lexer.getText()` and `ANTLRInputStream.getText(Interval)`. `Lexer.getText()` likely returns the text of the *current* token being built, whereas `ANTLRInputStream` returns text from a range. This is a semantic difference, not a naming redundancy.
- Inconsistent naming for string-to-ID lookup operations. `Parser` uses `getRuleIndex` to map a rule name string to an integer ID, while `Recognizer` uses `getTokenType` to map a token name string to an integer ID. While the return types are both `Int`, the method names suggest different domains (Rule vs Token). A more consistent pattern would be `getRuleIndex` vs `getTokenTypeIndex` or `getTokenType` vs `getRuleIndex` -> `getRuleIndex` vs `getTokenType` is acceptable if the domain is distinct, but `Recognizer` is the base class. `Parser` inherits from `Recognizer`. It is confusing that `Parser` overrides/defines `getRuleIndex` while the base `Recognizer` defines `getTokenType`. A user might expect `getRuleIndex` to be on `Recognizer` or `getTokenType` to be on `Parser` if they were symmetric. However, since Rules and Tokens are distinct concepts, this is likely intentional.
- Low XML-doc coverage: Antlr4 (runtime/CSharp/src/Antlr4.csproj)
- Low cohesion: Parser (LCOM4 6) (runtime/CSharp/src/Parser.cs)
- Most significant orphaned file (runtime/CSharp/src/Atn/ATNDeserializer.cs)
- Most significant orphaned file (runtime/CSharp/src/Atn/ParserATNSimulator.cs)
- Off-boarding risk: anonymized user #1
- Orphaned file (runtime/CSharp/src/Atn/DecisionInfo.cs)
- Orphaned file (runtime/CSharp/src/Atn/LL1Analyzer.cs)
- Orphaned file (runtime/CSharp/src/Atn/LexerATNConfig.cs)
- Orphaned file (runtime/CSharp/src/Atn/LexerATNSimulator.cs)
- Orphaned file (runtime/CSharp/src/Atn/ParseInfo.cs)
- …and 6 more

## New (223)

- Concentrated knowledge decay
- Documentation: no build, run or usage example (runtime/JavaScript/README.md)
- Duplicated block (12 lines × 2) (runtime/Dart/lib/src/interval_set.dart)
- Duplicated block (12 lines × 2) (runtime/Go/antlr/v4/semantic_context.go)
- Duplicated block (7 lines × 2) (runtime/Swift/Sources/Antlr4/atn/ActionTransition.swift)
- Edited copies of one member (3 members, 10+ corresponding lines) (runtime/Go/antlr/v4/parser_atn_simulator.go)
- Edited copies of one member (3 members, 12+ corresponding lines) (runtime/Swift/Sources/Antlr4/DiagnosticErrorListener.swift)
- Edited copies of one member (3 members, 12+ corresponding lines) (runtime/Swift/Sources/Antlr4/misc/BitSet.swift)
- Edited copies of one member (3 members, 17+ corresponding lines) (runtime/Go/antlr/v4/jcollect.go)
- Edited copies of one member (3 members, 21+ corresponding lines) (runtime/Java/src/org/antlr/v4/runtime/CodePointCharStream.java)
- Edited copies of one member (3 members, 25+ corresponding lines) (tool/src/org/antlr/v4/automata/LexerATNFactory.java)
- Edited copies of one member (3 members, 27+ corresponding lines) (runtime/Go/antlr/v4/jcollect.go)
- Edited copies of one member (3 members, 34+ corresponding lines) (runtime/Go/antlr/v4/jcollect.go)
- Edited copies of one member (3 members, 35+ corresponding lines) (runtime/Swift/Sources/Antlr4/misc/BitSet.swift)
- Edited copies of one member (3 members, 41+ corresponding lines) (runtime/CSharp/src/Atn/ParserATNSimulator.cs)
- Edited copies of one member (3 members, 6+ corresponding lines) (runtime/Java/src/org/antlr/v4/runtime/atn/LexerChannelAction.java)
- Edited copies of one member (3 members, 6+ corresponding lines) (runtime/Swift/Sources/Antlr4/atn/AmbiguityInfo.swift)
- Edited copies of one member (3 members, 7+ corresponding lines) (runtime/CSharp/src/DiagnosticErrorListener.cs)
- Edited copies of one member (3 members, 7+ corresponding lines) (runtime/Swift/Sources/Antlr4/atn/ParserATNSimulator.swift)
- Edited copies of one member (3 members, 8+ corresponding lines) (runtime/Java/src/org/antlr/v4/runtime/atn/ParserATNSimulator.java)
- …and 203 more

## Changes since last survey

- 1 commits — 1 feature/other, 0 fixes

## By area

- runtime-testsuite/test — 1 commit

## Notable commits

- change: Pin typescript@5 and ts-node@10 in TypeScript runtime tests

## Architecture

- Unchanged — 0 containers · 3 contexts · 2 edges
