fix: align cross-editor symbol identities

Author: andrebrait

README.md

@@ -60,7 +60,7 @@ Context normally adds formatting without replacing a symbol's identity color:
 - A reassigned variable or parameter gains an underline but keeps its foreground.
 - Static members are italic; instance members are not.
 - Inspection results add their underline, wave, border, or background over the existing syntax colors.
-- Read-only and other contextual distinctions may use bold or italic where the editor exposes them reliably.
+- Constancy does not change variable or field formatting.
 
 A captured Java variable is a useful boundary case. A method parameter is blue in the enclosing method, but IntelliJ presents its use inside a lambda as a neutral field-like capture. Its semantic role has changed: the generated lambda object effectively carries that value as state.
 

docs/releases/1.3.2.md

@@ -0,0 +1,24 @@
+# Invariant 1.3.2
+
+This release aligns JavaScript and JSON symbol identities across the IntelliJ and
+Visual Studio Code themes.
+
+## IntelliJ
+
+- JavaScript local and global variables now use the warm-neutral variable color
+  instead of inherited Darcula and Islands colors.
+- Resolved JavaScript instance methods now use function green instead of
+  parameter-like blue.
+- Each JavaScript key resets to its exact fallback declared by IntelliJ. Missing
+  libraries may still prevent the IDE from identifying imported types or member
+  methods semantically.
+
+## Visual Studio Code
+
+- JSON, JSON with Comments, and JSON Lines property names now use the neutral
+  variable/property color instead of type cyan.
+- Read-only semantic tokens no longer become bold, so local `const` and `let`
+  variables keep the same identity styling.
+
+The JetBrains ZIP and Visual Studio Code VSIX are attached to this release. Vim
+and Neovim package managers can install the `invariant-v1.3.2` tag directly.

docs/research/intellij-language-color-inheritance.md

@@ -119,6 +119,15 @@ backgrounds.
 
 For Python, type annotations fall back to `DEFAULT_IDENTIFIER` and are left to do so, which is why a type hint reads as neutral text. Python 3.12 type parameters fall back to `DEFAULT_PARAMETER` rather than Java's `TYPE_PARAMETER_NAME_ATTRIBUTES`, so they are pinned to the type-parameter orange explicitly. The plugin's remaining syntax, function, class, parameter, local-variable, decorator, and punctuation keys already fall back to the corresponding Language Defaults.
 
+JavaScript's bundled Darcula fragment overrides `JS.LOCAL_VARIABLE`,
+`JS.GLOBAL_VARIABLE`, and `JS.INSTANCE_MEMBER_FUNCTION`. IntelliJ source declares their
+fallbacks as `DEFAULT_LOCAL_VARIABLE`, `DEFAULT_GLOBAL_VARIABLE`, and
+`DEFAULT_INSTANCE_METHOD`, respectively. Invariant resets each key with that exact declared
+`baseAttributes` value, clearing the parent override without trying to redirect inheritance.
+Locals and globals therefore render warm neutral, while resolved instance methods render green.
+When a reference cannot resolve because its library is missing, the JavaScript highlighter may
+guess a variable or member category instead; a color scheme cannot recover the missing identity.
+
 Known debt: pale blue `#bed6ff` carries two meanings. It marks signature-only methods
 (`ABSTRACT_METHOD_ATTRIBUTES`, `INHERITED_METHOD_ATTRIBUTES`) and also runtime built-ins
 (`PY.BUILTIN_NAME`, `BASH.EXTERNAL_COMMAND`, `CSS.FUNCTION`), and the Visual Studio Code and

jetbrains/build.gradle.kts

@@ -5,7 +5,7 @@ plugins {
 }
 
 group = "com.github.andrebrait"
-version = providers.environmentVariable("PLUGIN_VERSION").orElse("1.3.1").get()
+version = providers.environmentVariable("PLUGIN_VERSION").orElse("1.3.2").get()
 
 repositories {
     mavenCentral()

jetbrains/invariant.icls

@@ -826,17 +826,9 @@
         <option name="FOREGROUND" value="9c9cff" />
       </value>
     </option>
-    <option name="JS.INSTANCE_MEMBER_FUNCTION">
-      <value>
-        <option name="FOREGROUND" value="56a8f5" />
-      </value>
-    </option>
-    <option name="JS.GLOBAL_VARIABLE">
-      <value>
-        <option name="FOREGROUND" value="c77dba" />
-        <option name="FONT_TYPE" value="2" />
-      </value>
-    </option>
+    <option name="JS.INSTANCE_MEMBER_FUNCTION" baseAttributes="DEFAULT_INSTANCE_METHOD" />
+    <option name="JS.GLOBAL_VARIABLE" baseAttributes="DEFAULT_GLOBAL_VARIABLE" />
+    <option name="JS.LOCAL_VARIABLE" baseAttributes="DEFAULT_LOCAL_VARIABLE" />
     <option name="JS.GLOBAL_FUNCTION" baseAttributes="DEFAULT_FUNCTION_DECLARATION" />
     <option name="KOTLIN_COLON">
       <value>

jetbrains/src/main/resources/META-INF/plugin.xml

@@ -6,14 +6,14 @@
   <description><![CDATA[
     <p>Invariant is a semantic dark editor color scheme based on Monokai.</p>
     <p>Color identifies what a symbol is; formatting shows how it is being used. Common code stays relatively quiet, while types, parameters, methods, reserved names, annotations, and comments remain easy to find.</p>
-    <p>The scheme provides explicit coverage for Java, Kotlin, Python, CSS, and shell scripts, with Language Defaults for other supported languages.</p>
+    <p>The scheme provides explicit coverage for Java, Kotlin, JavaScript, Python, CSS, and shell scripts, with Language Defaults for other supported languages.</p>
   ]]></description>
 
   <change-notes><![CDATA[
-    <p>Fixes the plugin so its color scheme appears in the IDE.</p>
+    <p>Aligns JavaScript semantic colors with Invariant's cross-editor identity model.</p>
     <ul>
-      <li>Invariant named Islands Dark as its parent scheme. That scheme is contributed by a plugin and is absent unless the Islands UI is active, so the IDE discarded Invariant on load and it never appeared under Settings | Editor | Color Scheme.</li>
-      <li>The scheme now inherits from Darcula and defines every color and attribute it previously inherited, so its appearance is unchanged.</li>
+      <li>Local and global variables now use the neutral variable color instead of inherited Darcula and Islands colors.</li>
+      <li>Resolved instance methods now use function green instead of parameter-like blue.</li>
     </ul>
   ]]></change-notes>
 

scripts/check.mjs

@@ -28,11 +28,21 @@ const functionScopes = theme.tokenColors.find(rule => rule.name === 'Functions a
 assert.ok(!functionScopes.includes('meta.function-call'));
 assert.ok(functionScopes.includes('meta.function-call.generic.python'));
 assert.equal(theme.semanticTokenColors.variable, theme.semanticTokenColors.property);
+const propertyRule = theme.tokenColors.find(rule => rule.name === 'Variables and properties');
+assert.equal(propertyRule.settings.foreground, theme.semanticTokenColors.property);
+for (const scope of [
+  'support.type.property-name.json',
+  'support.type.property-name.json.comments',
+  'support.type.property-name.json.lines'
+]) {
+  assert.ok(propertyRule.scope.includes(scope));
+}
 assert.equal(theme.semanticTokenColors.parameter, '#79abff');
 assert.deepEqual(theme.semanticTokenColors.selfParameter, { foreground: '#ff007f', bold: true });
 assert.deepEqual(theme.semanticTokenColors.clsParameter, { foreground: '#ff007f', bold: true });
 assert.deepEqual(theme.semanticTokenColors['*.modification'], { underline: true });
 assert.deepEqual(theme.semanticTokenColors['*.static'], { italic: true });
+assert.ok(!Object.hasOwn(theme.semanticTokenColors, '*.readonly'));
 assert.equal(theme.tokenColors.find(rule => rule.name === 'Comments').settings.foreground, '#ffffff');
 assert.deepEqual(theme.tokenColors.find(rule => rule.name === 'Python self and cls').settings, {
   foreground: '#ff007f',
@@ -138,6 +148,9 @@ for (const pythonModule of ['namespace:python', 'module:python']) {
     ['DEFAULT_INSTANCE_METHOD', 'DEFAULT_FUNCTION_DECLARATION'],
     ['DEFAULT_LABEL', 'DEFAULT_IDENTIFIER'],
     ['DEFAULT_LOCAL_VARIABLE', 'DEFAULT_IDENTIFIER'],
+    ['JS.GLOBAL_VARIABLE', 'DEFAULT_GLOBAL_VARIABLE'],
+    ['JS.INSTANCE_MEMBER_FUNCTION', 'DEFAULT_INSTANCE_METHOD'],
+    ['JS.LOCAL_VARIABLE', 'DEFAULT_LOCAL_VARIABLE'],
     ['PY.ANNOTATION', 'DEFAULT_IDENTIFIER'],
     ['PY.STRING.B', 'DEFAULT_STRING'],
     ['STATIC_METHOD_ATTRIBUTES', 'DEFAULT_STATIC_METHOD'],

vscode/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 1.3.2
+
+- JSON, JSON with Comments, and JSON Lines property names now use the neutral variable/property color instead of type cyan, matching IntelliJ's field styling.
+- Read-only semantic tokens no longer become bold, so a local `const` keeps the same variable styling as a local `let`.
+
 ## 1.3.1
 
 - The JetBrains plugin now installs a color scheme the IDE can actually load. It named Islands Dark as its parent scheme, which is contributed by a plugin and is absent unless the Islands UI is active, so IntelliJ discarded the scheme on load and Invariant never appeared under Settings | Editor | Color Scheme. The scheme now inherits from Darcula and spells out every color and attribute it had been inheriting, leaving its appearance unchanged.

vscode/invariant-color-theme.json

@@ -432,6 +432,9 @@
       "scope": [
         "variable",
         "meta.object-literal.key",
+        "support.type.property-name.json",
+        "support.type.property-name.json.comments",
+        "support.type.property-name.json.lines",
         "support.variable"
       ],
       "settings": {
@@ -636,9 +639,6 @@
       "foreground": "#ff007f",
       "bold": true
     },
-    "*.readonly": {
-      "bold": true
-    },
     "*.modification": {
       "underline": true
     },

vscode/package.json

@@ -2,7 +2,7 @@
   "name": "invariant-colors",
   "displayName": "Invariant",
   "description": "A semantic dark editor theme based on Monokai, where color identifies what a symbol is and formatting shows how it is used.",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "publisher": "andrebrait",
   "license": "EPL-2.0",
   "repository": {