chore(release): finalize v0.8.0 - analysis, integrations, and AI-ready interfaces

Author: DKFuH

CHANGELOG.md

@@ -6,6 +6,15 @@ The format is based on Keep a Changelog, and this project follows Semantic Versi
 
 ## [Unreleased]
 
+## [0.8.0] - 2026-03-29
+
+- Introduced `orgscript analyze <file>` for deterministic structural analysis (block counts, metrics, and complexity hints).
+- Added `orgscript export context <file>` to package logic for AI-ready workflows (Bundled model, analysis, and summaries).
+- Published integration recipes for GitHub Actions and pre-commit hooks under `docs/integrations/`.
+- Upgraded documentation site builder to highlight the "Source-to-Docs" flow and unified artifacts.
+- Expanded the showcase with a high-quality "Incident Escalation" trust case.
+- Stabilized CLI output for analysis and context exports.
+
 ## [0.7.0] - 2026-03-29
 
 - Enhanced CLI for professional distribution: added `--version` and improved help text.

ROADMAP.md

@@ -62,6 +62,15 @@ Theme: **Packaging, Distribution, and Trust**
 - **Documentation Site**: Automated static documentation on GitHub Pages.
 - **Trust & Showcase**: Complex business logic scenarios and integration examples.
 
+## v0.8 (Completed)
+
+Theme: **Analysis, Integrations, and AI-Ready Interfaces**
+
+- **Deterministic Analysis**: New `orgscript analyze` command for structural metrics.
+- **AI-Ready Context**: Stable context export format for LLM workflows.
+- **Tooling Hooks**: Recipes for CI/CD and pre-commit integrations.
+- **Docs site upgrade**: Improved site-site navigation and showcase grouping.
+
 ## Later
 
 - Ecosystem integrations

docs/integrations/github-actions.md

@@ -0,0 +1,57 @@
+# Integration: GitHub Actions
+
+You can use OrgScript in your CI pipeline to ensure all logic models in your repository remain valid, lint-clean, and canonically formatted.
+
+## Basic Validation Workflow
+
+Create a file named `.github/workflows/orgscript-check.yml`:
+
+```yaml
+name: OrgScript Logic Check
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          
+      - name: Install OrgScript
+        run: npm install -g orgscript
+        
+      - name: Run OrgScript Check
+        run: |
+          # Check all .orgs files in the repository
+          find . -name "*.orgs" -exec orgscript check {} +
+```
+
+## AI Search/Index Ingest Workflow
+
+To feed your organization's logic into an LLM or vector database periodically:
+
+```yaml
+  index-logic:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install OrgScript
+        run: npm install -g orgscript
+      - name: Generate AI Context
+        run: |
+          mkdir -p logic-context
+          for file in $(find examples -name "*.orgs"); do
+            name=$(basename "$file" .orgs)
+            orgscript export context "$file" > "logic-context/${name}.json"
+          done
+      # Then upload logic-context as artifact or push to your index
+```

docs/integrations/pre-commit.md

@@ -0,0 +1,46 @@
+# Integration: Pre-commit Hooks
+
+Ensure no invalid or non-canonical OrgScript logic enters your repository.
+
+## Using Husky
+
+If you use [Husky](https://typicode.github.io/husky/) in your project:
+
+1. **Install Husky:**
+   ```bash
+   npm install husky --save-dev
+   npx husky init
+   ```
+
+2. **Add pre-commit hook:**
+   ```bash
+   echo "find . -name '*.orgs' -exec orgscript check {} +" > .husky/pre-commit
+   chmod +x .husky/pre-commit
+   ```
+
+## Using a Shell Script
+
+For a barebones git pre-commit hook, add this to `.git/hooks/pre-commit`:
+
+```bash
+#!/bin/sh
+
+# Staged files (.orgs only)
+STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep ".orgs$")
+
+if [ -z "$STAGED_FILES" ]; then
+    exit 0
+fi
+
+echo "Running OrgScript check on staged files..."
+
+for file in $STAGED_FILES; do
+    orgscript check "$file"
+    if [ $? -ne 0 ]; then
+        echo "OrgScript check failed for $file. Aborting commit."
+        exit 1
+    fi
+done
+
+exit 0
+```

docs/releases/v0.8.0.md

@@ -0,0 +1,36 @@
+# 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.

docs/roadmaps/v0.8.0.md

@@ -0,0 +1,44 @@
+# OrgScript v0.8.0 Roadmap [COMPLETED]
+
+Status: Completed
+Theme: **Analysis, Integrations, and AI-Ready Interfaces**
+
+The goal of v0.8.0 is to make OrgScript easier to inspect, analyze, and integrate into downstream tooling and AI workflows. This release focuses on stable machine-readable outputs and deterministic analysis rather than language expansion.
+
+## Goals
+
+- Introduce a deterministic analysis layer for structural inspection.
+- Provide a stable context export format for AI/Agent ingest.
+- Establish practical integration recipes for CI/CD and repository workflows.
+- Mature the documentation site and showcase value.
+
+## Work Packages
+
+### WP1: Deterministic Analysis Command
+- Implement `orgscript analyze <file>` (and `--json`).
+- Report structural metrics: block counts, triggers, states, transitions, role capabilities.
+- Add "Complexity Hints" based on AST depth and branch counts.
+
+### WP2: AI-Ready Context Export
+- Implement `orgscript export context <file>`.
+- Create a unified context package containing the canonical model, diagnostics, and summaries.
+- Ensure the format is optimized for reliable AI/LLM interpretation.
+
+### WP3: Integration Recipes & Tooling Hooks
+- Create documentation for GitHub Actions integration.
+- Provide pre-commit/pre-push hook examples.
+- Document CI/CD pipeline patterns for OrgScript logic governance.
+
+### WP4: Documentation Site & Showcase Upgrade
+- Refine the generated docs site (`scripts/build-docs.js`).
+- Improve navigation and visual grouping of artifacts (Source vs. Summary vs. Diagram).
+- Highlight hero examples more effectively.
+
+### WP5: Real-World Trust Cases
+- Add high-quality examples: Finance Approval and Incident Escalation.
+- Ensure all showcases exercise multiple OrgScript blocks (`process`, `rule`, `stateflow`).
+
+## Non-Goals
+- Adding new language keywords or block types.
+- Free-form AI text generation or speculative recommendations.
+- SaaS or cloud features.

editors/vscode/package.json

@@ -2,7 +2,7 @@
   "name": "orgscript-vscode",
   "displayName": "OrgScript",
   "description": "Minimal VS Code language support for OrgScript (.orgs) files.",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "publisher": "dkfuh",
   "repository": {
     "type": "git",

examples/incident-escalation.orgs

@@ -0,0 +1,62 @@
+stateflow IncidentLifecycle
+
+  states
+    open
+    triaged
+    investigating
+    mitigated
+    resolved
+    closed
+
+  transitions
+    open -> triaged
+    triaged -> investigating
+    triaged -> mitigated
+    investigating -> mitigated
+    mitigated -> resolved
+    resolved -> closed
+
+role OnCallEngineer
+
+  can
+    triage incident
+    assign responder
+    update status
+    resolve incident
+
+role IncidentManager
+
+  can
+    escalate incident
+    declare major incident
+    notify stakeholders
+
+policy EscalationPolicy
+
+  when incident.severity = "high" and incident.status = "open"
+  then
+    require triage_sla
+    notify on_call_manager with "SLA Warning: High severity incident untriaged"
+
+  when incident.status = "investigating"
+  then
+    require regular_status_updates
+
+process IncidentHandling
+
+  when system.alert_received
+
+  create incident
+  assign incident.severity = "medium"
+  transition incident.status to "open"
+
+  if alert.source = "critical_infrastructure" then
+    assign incident.severity = "high"
+    notify on_call_team with "Critical alert detected"
+
+  if incident.status = "triaged" then
+    assign incident.primary_responder = "on_call_engineer"
+    transition incident.status to "investigating"
+
+  else
+    notify incident_manager with "Incident requiring triage"

package.json

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