[Railly]

Why now

A fix merged in November 2024 never reached anyone. #68 by @peguimasid made local variables readable in Vercel 2024 Dark, and it has been sitting in main for fifteen months while the published extension still ships the broken color.

Verified by downloading the published .vsix and comparing it against HEAD:

	variable.other.local
Published today, 39,731 installs	#171717, nearly black on a dark background
main	#EDEDED

Publishing has been manual, which is exactly how this happens.

What was broken

The generators reported success on failure. Writes inside forEach were never awaited and neither entry point had an error handler, so a failed write still exited 0. Verified by injecting a failing write: it exited 0 before, and exits 1 now.

The iTerm2 generator had never run. xmlbuilder was imported but never declared, so the step crashed every time and the crash was swallowed by the bug above. It runs now and reproduces the four committed .itermcolors files byte for byte.

vsce and ovsx were never declared, so the publish scripts only worked if they happened to be installed globally.

The package was 7 MB. .vscodeignore excluded almost nothing, so every publish carried screenshots/, src/, demos/, and node_modules/. vsce also refused to package at all, because demos/.env tripped its secret check. Both fixed by the ignore list; it is 57 KB now, a 99% reduction. The README is unaffected since every image it references is a remote URL.

C++ colors, reworked from #71

Credit to @helloAmulya for the diagnosis and the color choices, which this keeps verbatim. Two things blocked that PR:

1. It did not compile. The comment.cpp block was missing its closing braces: TS1136 on line 852. The CI in this PR would have caught it on day one.
2. It carried +724/-320 in Material, because running the build regenerates the five themes tinte owns and reverts them to their pre-tinte state. That is a property of this repo, not a mistake by the author.

Scoped to the generator-owned themes, it is 126 purely additive lines across Classic, Light, and Vercel, zero deletions.

Closes #70.

CI, closing #2

Open since December 2022.

ci.yml on every PR: typecheck, regenerate, drift gate, package, and upload the .vsix as an artifact so a theme change can be installed and looked at before merging.

release.yml on a v* tag: same checks, publish to both registries, cut a GitHub release with the .vsix attached. The tag must match package.json or the job fails.

The drift gate deliberately covers only the five themes this repo's generator owns. Material and the four Flexoki variants come from tinte and are not reproducible from src/, so gating them would fail every run and pressure someone into reverting tinte to make CI green.

Verification

Check	Result
npm run generate end to end	exit 0, both generators
Generator exits 1 on a real failure	verified by injection
iTerm2 output vs committed	byte identical
Typecheck	exit 0
Drift gate, tampered file	exit 1
Drift gate, clean tree	exit 0
Package size	7 MB to 57 KB
All 10 declared themes present and parse	yes
@peguimasid's fix present in the package	#EDEDED
Themes owned by tinte	untouched

Before merging

release.yml needs two repository secrets, neither of which exists yet:

• VSCE_PAT, an Azure DevOps token, Marketplace scope Manage. The old one is likely expired since the last publish was fifteen months ago.
• OVSX_PAT, from open-vsx.org. The RaillyHugo namespace is alive, so this only needs a new token, not a new namespace.

Tag v1.4.1 once those are set.