chore(release): prepare v0.4.0 metadata

Author: DKFuH

CHANGELOG.md

@@ -6,6 +6,8 @@ The format is based on Keep a Changelog, and this project follows Semantic Versi
 
 ## [Unreleased]
 
+## [0.4.0] - 2026-03-29
+
 - Added `orgscript format <file> --check` for canonical formatting checks without rewriting files.
 - Added `npm run format:check:all` and integrated formatting checks into CI.
 - Added `orgscript check <file>` as the combined quality command for validation, linting, and formatting checks.

docs/releases/v0.4.0.md

@@ -0,0 +1,65 @@
+# OrgScript v0.4.0
+
+OrgScript v0.4.0 is the first developer-experience release.
+
+This release moves the project from a stable language/tooling core toward a more usable day-to-day workflow with combined quality checks, documented machine-readable diagnostics, visible downstream exports, and the first usable editor integration.
+
+## Highlights
+
+- canonical formatting checks via `format --check`
+- one-command quality verification via `check`
+- stable diagnostics with documented codes and JSON output
+- Markdown summary export
+- Mermaid demos for process and stateflow visualization
+- canonical language spec, governance notes, and usage guides
+- first usable VS Code syntax-highlighting extension for `.orgs`
+
+## CLI and DX
+
+- Added `orgscript format <file> --check`
+- Added `orgscript format <file> --check --json`
+- Added `orgscript check <file>`
+- Added `orgscript check <file> --json`
+- Added `npm run check:all`
+- Integrated canonical formatting checks into CI
+- Unified CLI diagnostics across `validate`, `lint`, `check`, and `format --check`
+- Introduced stable diagnostic code namespaces for `cli`, `syntax`, `semantic`, `lint`, and `format`
+
+## Exports and visible outputs
+
+- Added `orgscript export markdown <file>` for deterministic Markdown summaries
+- Added Mermaid demo artifacts and generation flow
+- Kept Mermaid export available for `process` and `stateflow`
+- Extended demo material under `docs/demos`
+
+## Language maturity
+
+- Added the canonical `spec/language-spec.md`
+- Added governance guidance and authoring guides for humans and AI
+- Expanded the diagnostics contract in `spec/diagnostics.md`
+- Kept CI and golden snapshots green on the combined quality path
+
+## Editor support
+
+- Upgraded the VS Code OrgScript extension from a scaffold to a usable first TextMate-based syntax-highlighting integration
+- Registered `.orgs` files as `OrgScript`
+- Highlighted top-level blocks, statements, section keywords, strings, booleans, numbers, operators, and dotted references
+- Documented local testing in `editors/vscode/README.md`
+
+## Verification
+
+Verified with:
+
+- `npm test`
+- `npm run check:all`
+- `node ./bin/orgscript.js check ./examples/craft-business-lead-to-order.orgs`
+- `node ./bin/orgscript.js check ./examples/craft-business-lead-to-order.orgs --json`
+- `node ./bin/orgscript.js export markdown ./examples/order-approval.orgs`
+- `node ./bin/orgscript.js export mermaid ./examples/order-approval.orgs`
+
+## Project status
+
+OrgScript is not a programming language.
+It is a human-readable, AI-interpretable description language for business logic, processes, rules, roles, policies, events, and operational systems.
+
+v0.4.0 is the first release where OrgScript feels usable not only as a language implementation, but also as a contributor-facing tooling project.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "orgscript",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "A human-readable, AI-friendly description language for business logic and operational systems.",
   "license": "Apache-2.0",
   "private": true,