|
| 1 | +# OrgScript v0.9.4 |
| 2 | + |
| 3 | +OrgScript v0.9.4 adds a small but meaningful language-core v1 step: a document language metadata header. |
| 4 | + |
| 5 | +This release does not introduce free-form multilingual syntax. The core language remains canonical in English. Instead, OrgScript documents can now declare the intended language of comments, annotations, and generated human-facing context in a strict, parseable way. |
| 6 | + |
| 7 | +## Highlights |
| 8 | + |
| 9 | +- added an optional `orgscript 1` document header |
| 10 | +- added allowlisted document metadata keys: |
| 11 | + - `source-language` |
| 12 | + - `comment-language` |
| 13 | + - `annotation-language` |
| 14 | + - `context-language` |
| 15 | +- kept `source-language` strict in v1: only `en` is allowed |
| 16 | +- carried document metadata into the AST, canonical JSON model, and AI context export |
| 17 | +- added conservative lint findings for obvious language mismatches in comments and annotations |
| 18 | + |
| 19 | +## Why this matters |
| 20 | + |
| 21 | +The new header makes human-authored text safer and clearer in multilingual environments without weakening the OrgScript core. |
| 22 | + |
| 23 | +That helps with: |
| 24 | + |
| 25 | +- reviewability for teams working across multiple human languages |
| 26 | +- safer exporter and AI context behavior |
| 27 | +- clearer authorship expectations for comments and annotations |
| 28 | +- preserving English-first syntax while still declaring document language intent |
| 29 | + |
| 30 | +## Example |
| 31 | + |
| 32 | +```orgscript |
| 33 | +orgscript 1 |
| 34 | +
|
| 35 | +source-language "en" |
| 36 | +comment-language "de" |
| 37 | +annotation-language "de" |
| 38 | +context-language "de" |
| 39 | +``` |
| 40 | + |
| 41 | +This header is non-semantic. It does not change execution behavior, validation meaning, or the canonical interpretation of OrgScript logic. |
| 42 | + |
| 43 | +## Verification |
| 44 | + |
| 45 | +Confirmed on the release preparation state: |
| 46 | + |
| 47 | +- `npm test` |
| 48 | +- `npm run check:all` |
| 49 | +- `node ./bin/orgscript.js validate ./examples/lead-qualification.orgs` |
| 50 | +- `node ./bin/orgscript.js lint ./tests/lint/language-mismatch.orgs --json` |
| 51 | +- `node ./bin/orgscript.js export json ./examples/lead-qualification.orgs` |
| 52 | +- `node ./bin/orgscript.js export context ./examples/lead-qualification.orgs` |
| 53 | +- `node ./bin/orgscript.js analyze ./examples/lead-qualification.orgs --json` |
| 54 | +- `node ./bin/orgscript.js export markdown ./examples/lead-qualification.orgs --with-annotations` |
| 55 | +- `node ./bin/orgscript.js export html ./examples/lead-qualification.orgs --with-annotations` |
| 56 | + |
| 57 | +## Project status |
| 58 | + |
| 59 | +OrgScript remains a human-readable, AI-friendly description language for business logic and operational systems. |
| 60 | + |
| 61 | +v0.9.4 strengthens document contracts and exporter clarity without turning the core language into a multilingual keyword system. |
0 commit comments