feat: gts-kit 0.3.0

README.md

@@ -8,6 +8,8 @@ A three-headed application for validating and viewing the [GTS](https://github.c
 
 This project is aimed at exploring and using GTS schemas and instances across platforms.
 
+The repository is conformant with gts-spec v0.13.4.
+
 ![GTS Viewer](./docs/gts-viewer.png)
 
 ## Quick Start

apps/electron/CHANGELOG.md

@@ -0,0 +1,47 @@
+# Changelog
+
+All notable changes to the GTS Electron app will be documented in this file.
+
+## [Unreleased]
+
+## [0.3.0] - 2026-09-18
+
+### Changed
+- Rebased validation on `gts-ts` v0.7.0 for additional checks
+
+### Fixed
+- Reject schema-less `$id` instances
+- Prune annotation-only GTS reference branches and skip ID-less YAML containers
+- Enforce strict RFC 3339 for date/time formats
+
+## [0.2.6] - 2026-09-07
+
+_Released alongside the rest of the suite._
+
+## [0.2.5] - 2026-09-06
+
+_Released alongside the rest of the suite._
+
+## [0.2.4] - 2026-09-06
+
+### Added
+- YAML file format support
+
+### Changed
+- Rebased schema validation on `gts-ts`
+- Aligned schema handling with GTS spec v0.7
+
+## [0.2.1] - 2025-10-22
+
+_Released alongside the rest of the suite._
+
+## [0.2.0] - 2025-10-19
+
+### Fixed
+- Fixed errors on Electron start
+- Moved the primary web server port to 7805 and the DB server to 7806 for npm/docker
+
+## [0.1.0] - 2025-10-16
+
+### Added
+- Initial release of the GTS Electron viewer

apps/electron/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gts-viewer/electron",
-  "version": "0.2.6",
+  "version": "0.3.0",
   "description": "GTS Viewer Electron Application",
   "main": "dist/main/main.js",
   "scripts": {

apps/server/CHANGELOG.md

@@ -0,0 +1,48 @@
+# Changelog
+
+All notable changes to the GTS server will be documented in this file.
+
+## [Unreleased]
+
+## [0.3.0] - 2026-09-18
+
+### Changed
+- Rebased validation on `gts-ts` v0.7.0 for additional checks
+
+### Fixed
+- Reject schema-less `$id` instances
+- Prune annotation-only GTS reference branches and skip ID-less YAML containers
+- Enforce strict RFC 3339 for date/time formats
+
+## [0.2.6] - 2026-09-07
+
+_Released alongside the rest of the suite._
+
+## [0.2.5] - 2026-09-06
+
+_Released alongside the rest of the suite._
+
+## [0.2.4] - 2026-09-06
+
+### Added
+- YAML file format support
+
+### Changed
+- Rebased schema validation on `gts-ts`
+
+## [0.2.1] - 2025-10-22
+
+_Released alongside the rest of the suite._
+
+## [0.2.0] - 2025-10-19
+
+### Changed
+- Switched from `better-sqlite3` to `sql.js` (no native compilation required)
+
+### Fixed
+- Moved the primary web server port to 7805 and the DB server to 7806 for npm/docker
+
+## [0.1.0] - 2025-10-16
+
+### Added
+- Initial release of the GTS server

apps/server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gts/server",
-  "version": "0.2.6",
+  "version": "0.3.0",
   "private": true,
   "type": "module",
   "main": "./dist/index.js",

apps/vscode-extension/CHANGELOG.md

@@ -2,36 +2,123 @@
 
 All notable changes to the GTS Viewer extension will be documented in this file.
 
-## [1.0.0] - 2025-10-08
+## [Unreleased]
+
+## [0.3.0] - 2026-09-18
 
 ### Added
-- **Context Menu Integration**: Right-click `.json` and `.gts` files to preview layouts
-- **Visual Layout Viewer**: Interactive diagram showing JSON schemas and instances
-- **Layout Persistence**: Save and load custom layouts from workspace `.gts-viewer/` folder
-- **Dual Panel View**: File opens in editor (left) with preview panel (right)
-- **Welcome Message**: First-time user guidance
-- **Auto-detection**: Automatic file validation for supported formats
+- GTS activity-bar panel with a file explorer to browse discovered GTS files and see an at-a-glance problem count
+- Refresh button in the GTS panel to rescan the workspace file explorer
+- YAML annotation support, including inline GTS entity definitions declared in YAML config files
+- Drag-and-drop of discovered GTS files, including multi-file drag into chat
+- Automatic revalidation of dependent entities when a file changes, across all apps
+- File watching inside symlinked directories
 
-### Features
-- Support for `.json` and `.gts` file types
-- RepoLayoutStorage integration for team-shared layouts
-- Version control friendly layout storage
-- Error handling with user-friendly messages
-- Webview-based rendering for rich visual experience
+### Changed
+- Rebased validation on `gts-ts` v0.7.0 for additional checks, and updated to gts-spec v0.13.4
+- Renamed all `gts.*` commands to `gts-kit.*`
+- Updated the Marketplace category and tags
+- Enabled Node typings for the extension
+- Improved the default message shown while the GTS file scanner is running
 
-### Commands
-- `GTS: Preview Layout` - Open selected file in visual viewer
-- `GTS: Open Viewer` - Show usage instructions
+### Fixed
+- GTS scanner now starts on extension startup
+- Discovered GTS files stay synchronized, with reduced file-tree flicker and deduplicated symlinked scans
+- Explorer file scans are no longer synchronous, avoiding UI stalls on large repos
+- Invalid files stay marked red after a preview tab closes
+- Inherited schema validation failures are now surfaced
+- Invalid GTS chain segments cascade correctly, and reference errors resolve to their own array item
+- GTS ID segments are classified structurally via core gts-ts
+- Strict RFC 3339 enforcement for date/time formats
+- Schema-less `$id` instances are rejected; annotation-only GTS reference branches and ID-less YAML containers are skipped
+- Duplicate entity suggestions removed
+- Stale files invalidated after parse errors
 
-### Context Menu Locations
-- Explorer context menu (right-click files)
-- Editor title context menu
+## [0.2.6] - 2026-09-07
 
-## [Unreleased]
+### Fixed
+- Malformed `gts://` schema IDs now surface correctly everywhere instead of failing silently
+- Gray chip shown for unresolved GTS IDs in schema examples
+- Compact web UI layout for the VS Code webview; validation errors now wrap properly
+- `GTS: Open Viewer` now opens the currently selected file
+
+### Added
+- Diagnostics shown when the web server isn't running
+- A progress bar for large repo scans
+
+## [0.2.5] - 2026-09-06
+
+### Changed
+- Renamed extension identifier to `gts-kit` (the `gts` name was already taken on the VS Code Marketplace)
+- Reduced packaged extension size
+
+## [0.2.4] - 2026-09-06
+
+### Fixed
+- Rebased schema validation on `gts-ts`
+- Invalid JSON is now rejected during editor validation
+- Removed duplicated validation errors in the GTS viewer
+- Consistent YAML parsing across shared registry and editor validation
+
+### Added
+- All/errors/valid entities selector in the GTS viewer
+
+## [0.2.3] - 2026-08-31
+
+### Added
+- Scoped background validation for unopened GTS files
+- GTS brand logo as extension and activity bar icon
+- Enforced `gts://` URI prefix rules for JSON Schema fields
+
+### Fixed
+- Two-phase prioritized file scan with `.gitignore` exclusion for better performance
+- Persisted GTS registry to reduce editor open latency
+- Removed redundant margins around GTS string annotations in the editor
+- Consistent segment gap width across GTS segment styles
+
+## [0.2.2] - 2026-08-31
 
-### Planned
-- Multi-file comparison view
-- Layout templates
-- Export to image/SVG
-- Search and filter capabilities
-- Enhanced keyboard shortcuts
+### Added
+- YAML file format support
+- Schema examples preview feature
+- NOTICE file with copyright and license information
+
+### Changed
+- Aligned schema handling with GTS spec v0.7
+- Prioritize the GTS ID (`id`, `gtsId`, etc.) over the `type` field for schema resolution
+- Disabled GTS reference validation for `/examples` in schemas
+
+### Fixed
+- Slow GTS color annotations on file open
+- Popup GTS error display position
+- Restored VS Code editor inline validation
+- Removed redundant file link in the web viewer
+
+## [0.2.1] - 2025-10-22
+
+### Added
+- Open the file containing a GTS node directly from the VS Code editor
+
+### Changed
+- Cumulative visual style polish for the web view and VS Code
+- Neutral file link color (blue was reserved for "schema" elsewhere)
+
+### Fixed
+- Color annotations for broken GTS IDs
+- GTS replacement when clicking an auto-suggestion popup
+- Rescan JSON files on edits even when the web viewer isn't active
+
+## [0.2.0] - 2025-10-19
+
+### Added
+- Inline JSON/JSONC/GTS file validation inside the VS Code editor
+- Colored GTS ID validation and suggestions in the editor
+- Support for `.jsonc` and `.gts` file extensions
+
+### Changed
+- Switched from `better-sqlite3` to `sql.js` (no native compilation required)
+
+## [0.1.0] - 2025-10-16
+
+### Added
+- Initial release of the GTS Viewer VS Code extension

apps/vscode-extension/README.md

@@ -111,9 +111,14 @@ See the full [GTS Specification](https://github.com/globaltypesystem/gts-spec) f
 
 - **`.json`** — Standard JSON (schemas and instances)
 - **`.jsonc`** — JSON with Comments (single-line, multi-line, trailing commas)
-- **`.yaml` / `.yml`** — YAML files parsed and treated identically to JSON
+- **`.yaml` / `.yml`** — YAML files parsed and treated like JSON, **plus** inline GTS definitions (see below)
 - **`.gts`** — GTS-specific files
 
+#### Supported GTS Entity Definitions
+
+- **JSON / JSONC / `.gts`** — a document must be either a **single entity** or a **top-level array of entities**. GTS IDs anywhere else are treated as *references*.
+- **YAML** — everything above, **plus** inline definitions: a config file may *define* GTS types/instances under any nested `entities:` array (e.g. a service's `types-registry.config.entities` seed block), even deep inside otherwise-non-GTS config. Each element is registered by its `$id` as a real definition, so it is not flagged as an unresolved reference.
+
 ### Validation
 
 The extension validates GTS files automatically as you open, edit, and save them.

apps/vscode-extension/build.mjs

@@ -1,6 +1,29 @@
 import * as esbuild from 'esbuild'
 import { promises as fs } from 'fs'
 import path from 'path'
+import { createRequire } from 'module'
+
+const require = createRequire(import.meta.url)
+
+/**
+ * gts-ts compiles schema patterns with re2-wasm, which loads its `re2.wasm`
+ * binary from the directory of the running script. Bundled, that is `dist/`,
+ * so the binary must sit next to `dist/extension.js` or the extension throws
+ * on load. Resolved through gts-ts so it's the exact copy gts-ts depends on.
+ *
+ * @type {esbuild.Plugin}
+ */
+const copyRe2WasmPlugin = {
+  name: 'copy-re2-wasm',
+  setup(build) {
+    build.onEnd(async result => {
+      if (result.errors.length > 0) return
+      const gtsTsDir = path.dirname(require.resolve('@globaltypesystem/gts-ts/package.json', { paths: ['../../packages/shared'] }))
+      const re2Dir = path.dirname(require.resolve('re2-wasm/package.json', { paths: [gtsTsDir] }))
+      await fs.copyFile(path.join(re2Dir, 'build', 'wasm', 're2.wasm'), path.join('dist', 're2.wasm'))
+    })
+  },
+}
 
 const production = process.argv.includes('--production')
 const watch = process.argv.includes('--watch')
@@ -41,6 +64,7 @@ async function main() {
     mainFields: ['module', 'main'],
     plugins: [
       esbuildProblemMatcherPlugin,
+      copyRe2WasmPlugin,
     ],
   })