Contributors

Use these contributor guides when changing Glade itself. User setup stays in the guide. Runtime coverage, release proof, plugin runtime work, and glade-tools work live here.

Glade stays the product front door. Keep parsing, indexing, semantic checks, the VM, the test runner, SOQL, DML, storage, schema, server runtime, and product CLI commands in this repository.

Keep heavy maintenance work in first-party tools and plugins. That includes compatibility fixtures, capability catalogs, dashboards, surface ledgers, open-source corpus scans, Salesforce docs inventories, and generated maintenance reports.

Before changing source

Read AGENTS.md and AI contributor setup. Inspect the current branch, commit, and working tree; preserve unrelated owner changes. Use Go from go.mod and CGO_ENABLED=1 for declaration parsing. Choose the focused validation for the changed surface before a broad release gate.

Maintainer paths

Extend runtime supportWrite the failing fixture or product test first, then patch the runtime.glade-toolsUse the first-party toolkit for ledgers, captures, and plugin artifacts.Plugin runtimeKeep plugins executable, manifest-driven, and outside the base runtime.Release runbookRun one proof command before product, plugin, and docs release work.Develop the editor extensionPackage and validate the bundled VSIX from the checked extension source.