v0.9.3 — scoped npm package publish for @dkfuh/orgscript

OrgScript v0.9.3

OrgScript v0.9.3 is a packaging correction release for npm distribution.

The unscoped package name orgscript was rejected by npm because it is too similar to an existing package. This release moves the package to the scoped name @dkfuh/orgscript while preserving the CLI command name orgscript.

Highlights

• renamed the npm package to @dkfuh/orgscript
• kept the installed CLI command name as orgscript
• updated installation guidance for the scoped package
• re-verified scoped public publish readiness

Package distribution

• install from npm with:

npm install -g @dkfuh/orgscript

• publish publicly with:

npm publish --access public

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• npm pack --json
• npm publish --dry-run --access public
• local global install test from the packaged tarball
• orgscript --version
• orgscript check ./examples/craft-business-lead-to-order.orgs

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic and operational systems.

v0.9.3 makes the npm distribution path viable under the maintainer-owned scoped package name.

v0.9.2 —npm package publish

OrgScript v0.9.2

OrgScript v0.9.2 is a packaging and publish-readiness follow-up release.

It does not add new language surface. Instead, it closes the last gap between a locally healthy CLI package and a clean npm publish flow.

Highlights

• normalized npm publish metadata in package.json
• removed npm auto-correction warnings during publish dry-run
• retained NOTICE in the published package
• tightened package keywords for better npm/package discovery
• re-verified tarball contents and global CLI install behavior

Packaging fixes

• changed bin.orgscript from ./bin/orgscript.js to bin/orgscript.js
• normalized repository.url to git+https://github.com/DKFuH/OrgScript.git
• kept the package file list focused on runtime and reference essentials only

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• npm pack --json
• npm publish --dry-run
• local global install test from orgscript-0.9.2.tgz
• orgscript --version
• orgscript check ./examples/craft-business-lead-to-order.orgs

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic and operational systems.

v0.9.2 is the release that makes the npm package path clean and predictable.

v0.9.1 - safe comments, structured annotations, and annotation-aware exports

OrgScript v0.9.1

OrgScript v0.9.1 is a stabilization release focused on safe metadata, clearer downstream exports, and cleaner onboarding material.

This release builds directly on the v0.9.0-rc1 distribution candidate and turns that state into a cleaner, more trustworthy package for real-world use.

Highlights

• safe whole-line comments with explicit non-authoritative semantics
• allowlisted structured annotations in the AST and canonical model
• optional annotation rendering in Markdown and HTML exports
• explicit annotation metadata in export context
• stronger VS Code support with snippets and improved language configuration
• refreshed English and German manuals plus removal of legacy .docx artifacts

Language safety

• added whole-line # ... comments for human-only notes
• added allowlisted annotations via @key "value"
• kept comments out of canonical export, analysis, and machine-facing interpretation
• kept annotations non-semantic and metadata-only
• added lint protection for suspicious comments that look like hidden business rules

Export and AI/tooling improvements

• orgscript export markdown <file> --with-annotations can now render allowlisted annotations in generated summaries
• orgscript export html <file> --with-annotations can now render allowlisted annotations in generated HTML documentation
• orgscript export context <file> now exposes annotation metadata explicitly under source.metadata.annotations
• comments remain excluded from machine-facing exports by default

Editor and onboarding improvements

• added VS Code snippets for comments, annotations, and core OrgScript blocks
• improved VS Code language configuration with safer indentation hints
• rewrote the English and German handbooks on the current language/tooling surface
• removed obsolete .docx handbook artifacts from the repository

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• node ./bin/orgscript.js validate ./examples/lead-qualification.orgs
• 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/lead-qualification.orgs --with-annotations
• node ./bin/orgscript.js export html ./examples/lead-qualification.orgs --with-annotations
• node ./bin/orgscript.js export context ./examples/lead-qualification.orgs
• node ./bin/orgscript.js export json ./examples/lead-qualification.orgs
• node ./bin/orgscript.js analyze ./examples/lead-qualification.orgs --json

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic, processes, rules, roles, policies, events, metrics, and operational systems.

v0.9.1 focuses on trust: keeping comments safe, metadata explicit, exports deterministic, and the project easier to adopt.

v0.9.0-rc1 distribution release candidate

OrgScript v0.9.0-rc1

OrgScript v0.9.0-rc1 is the first packaging and distribution release candidate.

This release candidate focuses on making OrgScript easier to consume beyond the repository itself: as a package, as a VS Code extension project, and as a generated documentation/demo surface.

Highlights

• release-candidate packaging metadata aligned for npm-style distribution
• cleaner package entry via src/index.js
• improved repository metadata for GitHub-facing consumption
• VS Code extension package prepared for external distribution
• generated documentation artifact support for external publishing
• DE/EN handbook-style manuals and completed showcase artifacts

Packaging and distribution

• aligned the root package version to 0.9.0-rc1
• aligned the VS Code extension package version to 0.9.0-rc1
• kept bin/, src/, spec/, and release-facing root files in the package file list
• retained the CLI and library entry layout for downstream usage

Editor and docs distribution

• prepared the VS Code extension package metadata for marketplace-facing usage
• kept the OrgScript syntax-highlighting extension consistent with the release candidate version
• added DE/EN handbook material for easier onboarding outside the code-first audience
• completed missing Mermaid showcase artifacts in the docs flow
• kept the generated documentation entry point aligned with the current release candidate version

Verification

Confirmed on the release-candidate preparation state:

• 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 remains a human-readable, AI-interpretable description language for business logic, processes, rules, roles, policies, events, and operational systems.

v0.9.0-rc1 is about readiness for broader distribution, not new language surface.

v0.8.0 Analysis, Integrations, and AI-Ready Interfaces

OrgScript v0.8.0

OrgScript v0.8.0 is the Analysis, Integrations, and AI-Ready Interfaces release.

This release matures OrgScript’s capability to be used as a structured source of truth for downstream systems. By introducing deterministic analysis and stable context exports, we make OrgScript documents significantly more useful for both automated CI/CD pipelines and modern AI/Agent workflows.

Highlights

Deterministic Analysis

• orgscript analyze <file>: A new command for structural inspection without LLM dependency.
• Structural Metrics: Reports block counts, trigger inventories, state/transition counts, and role capabilities.
• Complexity Hints: Provides insights into the branching and statement volume of your logic.

AI-Ready Context

• orgscript export context <file>: Packages the entire logic model, diagnostics, and summaries into a single machine-friendly JSON format.
• Ingest Optimization: Designed to be the standard context bundle for feeding OrgScript logic into LLM agents or vector indexes.

Integration Recipes

• GitHub Actions: Added production-ready workflow templates for CI quality gates.
• Post-Commit Hooks: Provide examples for Husky and native git hooks to ensure logic consistency.
• Repository Hooks: Documentation on how to integrate OrgScript into existing engineering workflows.

Showcase Upgrade

• Doc Site Builder v2: Upgraded scripts/build-docs.js to create a more comprehensive preview of all artifacts (Source, Analysis, Summary, Diagram).
• Incident Escalation SLA: A new high-quality example demonstrating time-based policies and operational handling in high-trust environments.

Verification

Confirmed on the current release state:

• All tests passed (npm test).
• Analyzed hero examples with success.
• Exported AI-ready context for cross-system verification.

Project Evolution

v0.8.0 establishes OrgScript as a reliable, machine-readable interface. While v0.7.0 was about packaging, v0.8.0 is about utility—ensuring that every line of OrgScript code provides immediate, structured value for both human stakeholders and automated agents.

Packaging, Distribution, and Trust

OrgScript v0.7.0

OrgScript v0.7.0 focuses on Packaging, Distribution, and Trust.

This release transitions OrgScript from a local developer experiment into a ready-to-distribute toolset. By maturing our CLI, preparing the VS Code extension for publication, and building a live documentation showcase, we are making OrgScript significantly easier to adopt.

Highlights

Professional CLI Experience

• Global Installation: You can now install OrgScript globally via npm install -g . (or from the upcoming npm package) and call it directly as orgscript from any directory.
• Improved Tooling UX: Added --version / -v support and a more detailed, stakeholder-friendly help text via --help.
• Bin Path Stability: Refined the internal binary execution to be safe for global deployment.

VS Code Extension Readiness

• Marketplace Alignment: Updated the extension manifest with required metadata, repository links, and bug tracking.
• Modern Standards: Addressed VS Code manifest warnings and set the version to match the core project (v0.7.0).

Automated Documentation Showcase

• GitHub Pages Ready: Developed a new site builder (scripts/build-docs.js) that automatically compiles all example files into a unified documentation portal using the HTML exporter.
• Integrated Artifacts: The site includes live-rendered diagrams and concise logic summaries.

Trust Improvements

• Hiring Process Hero Example: Added a realistic, multi-department Hiring Process example (examples/hiring-process.orgs) to demonstrate advanced features such as role-based permissions, GDPR policies, and complex process branching.
• Full Verification: All examples are now validated against golden snapshots, ensuring zero regressions across AST, model, and formatter outputs.

Project Status

With v0.7.0, OrgScript is "Packaging Ready". The jump from v0.6.0 was focused on hardening the distribution path to ensure that OrgScript can be used reliable in real workflows.

Verification

• npm install -g . -> orgscript --version reports 0.7.0.
• All tests passed via npm test.
• Documentation site built successfully via node ./scripts/build-docs.js.

*integrations, artifacts, and showcase**

OrgScript v0.6.0

OrgScript v0.6.0 is the first integrations, artifacts, and showcase release.

This release marks a major step forward in making OrgScript’s value proposition visible. Instead of just modeling and checking logic, you can now generate compelling visual and structured outputs for stakeholders, documentation, and external systems.

Highlights

HTML Documentation Export

• Introduced orgscript export html <file>.
• Generates a modern, static HTML documentation page.
• Features embedded logic summaries and live-rendered Mermaid diagrams via CDN-based mermaid.js.

Mermaid Export Polish

• Semantic Shapes: Triggers are now represented as parallelograms for better flowchart clarity.
• Improved Styling: Added a consistent and premium styling layer (color-coded nodes for decision, action, trigger, success, and stop).
• Stateflow Markers: State diagrams now include proper [*] --> (start) and --> [*] (end) markers based on transition flow.
• Readability: Switched to single quotes for internal strings to improve the raw output's legibility.

Markdown Summary v2

• TOC and Anchors: Multi-block files now include a Table of Contents with jump-links.
• Structured Sections: Blocks are now separated by horizontal rules and use a clearer header hierarchy (H2/H3).
• Business Language: Phrasing has been tuned to be less technical and more accessible for non-technical reviewers.

Showcase Upgrade

• Updated docs/demos/ to include HTML, Markdown, and Mermaid artifacts.
• Included the "Hero" example (craft-business-lead-to-order.orgs) in the demo build.
• Refined the "Strategic Artifact Flow" described in the root README.md.

Integration and Governance

• Canonical Model v0.2: Stabilized the JSON schema for tokens, expressions, and block nodes.
• Reference Spec: Updated spec/canonical-model.md to match the real-world implementation.
• Stability Policy: Clarified policy for breaking changes in machine-readable outputs.

Verification

Verified on the current release state with:

• npm test
• npm run check:all
• node ./bin/orgscript.js export html ./examples/craft-business-lead-to-order.orgs
• node ./bin/orgscript.js demo:generate

Project Status

v0.6.0 transforms OrgScript from a stable specification into a useful documentation engine. By providing high-quality, zero-config exporters for the Web (HTML) and for prose (Markdown), we are establishing OrgScript as a credible layer for organizational knowledge and process governance.

v0.5.0 - Editor, Adoption, Polish

v0.5.0 Roadmap [COMPLETED]

Milestone title: v0.5.0 - Editor, Adoption, Polish

Goal

Make OrgScript feel immediately usable for new contributors and early adopters without expanding the language surface.

Release focus

• editor usability
• README and demo clarity
• curated example quality
• diagnostics and CLI polish
• lightweight language governance

Why now

v0.4.0 established the core developer-experience baseline:

• format --check
• check and check --json
• stable diagnostics with documented codes
• Markdown summary export
• Mermaid demos
• canonical language spec
• governance notes and usage guides
• first usable VS Code syntax highlighting

The next step is not more syntax. The next step is adoption.

Planned issues

1. feat(editor): improve VS Code syntax highlighting
2. docs(readme): add a visual source-to-artifact showcase
3. docs(examples): curate the example catalog
4. enhancement(diagnostics): polish diagnostics UX
5. docs(governance): add language evolution notes

Recommended order

1. VS Code highlighting v2
2. visual README showcase
3. curated example catalog
4. diagnostics UX polish
5. language evolution notes

Workstreams

1. Editor

• refine TextMate scopes
• improve highlighting for block names, references, and operators
• simplify local installation and testing notes
• add one or two visual examples for the editor experience

2. Front door

• show .orgs, Mermaid, and Markdown summary side by side
• make check, validate --json, and lint --json easier to discover
• shorten the path from repository landing to first successful command

3. Examples

• curate three strong examples:
  • sales / lead flow
  • approval / finance
  • service / escalation
• group examples into:
  • simple
  • realistic
  • advanced

4. Diagnostics and CLI polish

• tighten wording of common messages
• preserve diagnostic code stability
• make check output easier to scan
• keep text and JSON behavior aligned

5. Governance

• define what belongs in the language core
• define what should stay in exporters or tooling
• state how breaking changes are handled
• clarify how spec versioning and CLI versioning relate

Non-goals

• new language keywords
• localized syntax
• major parser rewrites
• SaaS or hosted tooling
• enterprise-specific features
• many new exporters at once

Success criteria

• OrgScript feels easier to adopt in a first editor session
• the README demonstrates visible value in under a minute
• examples are easier to browse and compare
• diagnostics feel more polished without changing the language core
• language evolution decisions become easier to reason about

Next after v0.5.0

v0.6.0 should focus on integrations and generated artifacts:

• Mermaid stabilization
• richer Markdown or HTML docs
• clearer exporter contracts
• stronger source-to-artifact demo flows

v0.4.0 — check command, markdown export, unified diagnostics, and initial VS Code highlighting

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.

v0.3.0 — Formatter, linter, diagnostics, and CI readiness

OrgScript v0.3.0

OrgScript v0.3.0 is the first quality-tooling release.

This release rounds out the initial implementation baseline with deterministic formatting, stable golden snapshots, an AST-based linter, machine-readable diagnostics, and CI-ready CLI behavior.

Highlights

• AST-backed canonical formatter
• Golden snapshot freeze for AST, canonical model, and formatted output
• AST-based linter with stable severities and deterministic reporting
• Human and AI usage guides
• JSON diagnostics for validate and lint
• First GitHub Actions CI workflow

Added

• orgscript format <file>
• orgscript lint <file>
• orgscript validate <file> --json
• orgscript lint <file> --json
• scripts/lint-all.js
• .github/workflows/ci.yml
• docs/orgscript-for-humans.md
• docs/orgscript-for-ai.md
• spec/diagnostics.md

Changed

• Lint exit codes are now CI-friendly:
  • 0 when findings contain only warning and info
  • 1 when findings contain at least one error
• Validation and lint diagnostics now have a machine-readable JSON contract
• Formatter, AST, and canonical model output are frozen through golden snapshots
• Lint output is stable and sorted deterministically

Verification

Verified with:

• npm test
• npm run validate:all
• npm run lint:all

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.3.0 is the first release that makes OrgScript feel stable as tooling, not only as a language implementation.