v1.14.0

[1.14.0] - 2026-07-20

Fixes

• Projects built with an older engine are now correctly flagged for re-indexing instead of silently going stale, and codegraph status --json exposes a reindexReasons array so scripts can detect a missed update without parsing the prose warning. (#189)
• VBA intrinsic constants such as vbCrLf, vbTab, vbYesNo, and vbExclamation, plus DAO option flags such as dbFailOnError, dbSeeChanges, dbReadOnly, and dbAppendOnly, no longer appear as failed references when they appear as bare identifiers; user-defined symbols that happen to share one of these names still resolve normally. (#188)
• VBA statement-form built-in calls such as MsgBox "…", DoEvents, and Shell "calc.exe" are now classified as runtime calls instead of failing, while user-defined symbols that happen to share a built-in name still resolve normally. (#192)
• VBA array parameters declared with ByRef name() As Type or ByVal name() As Type, including continued declarations, no longer flag indexed accesses inside their procedure as unresolved calls, while same-named genuine calls elsewhere still surface normally. (#190)
• The human-readable codegraph status output no longer reports an index as healthy when a re-index is recommended; the clean-health sentence now reads "No source changes detected" and the re-index hint names the structured reasons, matching the existing JSON contract. (#193)

Documentation

• The seven reference_kind literals that appear in VBA unresolved_refs (unqualified-ident, calls, qualified-call, member-with, property-get, property-set, references) are now documented in one place alongside the declined-runtime semantics and the v1.13.0 noise-ratio benchmarks on the 00_VBA_TOOLKIT_BENCH corpus, so audit scripts can filter actionable "missing callees" without re-reading the resolver source. Reference: docs/vba-reference-kinds.md. (#191)