Polish VS Code syntax highlighting scopes

[Copilot]

The initial TextMate grammar lumped the transition arrow and comparison operators into a single scope, and highlighted dotted references as a monolithic token — making it hard for themes to apply meaningful colour distinctions.

Grammar (syntaxes/orgscript.tmLanguage.json)

• Operators split by semantics:

  • -> → keyword.operator.arrow.orgscript (state transition arrow, not a comparator)
  • =, !=, <, <=, >, >= → keyword.operator.comparison.orgscript

• Dotted references split into object + property:

  • lead → variable.other.object.orgscript
  • .status → variable.other.property.orgscript

  Before: lead.status was a single variable.other.property token.
  After: object and property halves are independently scopeable by themes.

{
  "match": "\\b([A-Za-z_][A-Za-z0-9_-]*)((?:\\.[A-Za-z_][A-Za-z0-9_-]*)+)\\b",
  "captures": {
    "1": { "name": "variable.other.object.orgscript" },
    "2": { "name": "variable.other.property.orgscript" }
  }
}

Docs (editors/vscode/README.md)

Added a Local Testing section: F5 → Extension Development Host, then use Developer: Inspect Editor Tokens and Scopes to verify scopes. Points to examples/lead-qualification.orgs as the canonical test file.

[DKFuH]

Looks good overall.\n\nNotes\n- Thanks for splitting the operator scopes (arrow vs comparison) and the dotted reference captures.\n- I added a tiny doc tweak so local testing points to the correct examples path when the workspace is editors/vscode.\n\nNo blocking issues.