norn-cli 1.1.0

package/CHANGELOG.md

@@ -0,0 +1,556 @@
+# Change Log
+
+All notable changes to the "Norn" extension will be documented in this file.
+
+## [1.1.0] - 2026-02-01
+
+### Added
+- **Test Sequences**: Mark sequences as tests with `test sequence Name` syntax
+  - Only `test sequence` blocks run from CLI; plain `sequence` blocks are helpers
+  - Use helpers for shared setup/utility sequences called by tests
+  - Example: `test sequence AuthFlow` runs from CLI, `sequence SetupUser` is a helper
+
+- **Directory Discovery**: Run all test sequences in a directory tree
+  - `npx norn tests/` recursively finds and runs all `.norn` files
+  - Aggregates results across all files with combined summary
+  - Only `test sequence` blocks are executed
+
+- **Output Directory**: Save reports to a custom location with timestamped filenames
+  - `--output-dir ./reports` saves results to specified directory
+  - Auto-generates timestamped filenames: `tests-2026-02-01-120000-results.xml`
+  - Works with `--junit` and `--html` reporters
+
+- **Secret Variables**: Mark sensitive environment variables with `secret` keyword
+  - Syntax: `secret apiKey = my-secret-key` in `.nornenv` files
+  - Values automatically redacted as `***` in all CLI output
+  - Prevents accidental exposure of tokens, passwords, API keys
+
+- **Human-Readable CLI Output**: Colorized, formatted output for terminal
+  - Pass/fail indicators with colors and Unicode symbols
+  - Assertion results with expected vs actual values
+  - Request/response details in verbose mode
+
+- **JUnit Reporter**: Generate XML reports for CI/CD pipelines
+  - `--junit` flag outputs JUnit-compatible XML
+  - Compatible with GitHub Actions, Jenkins, Azure DevOps
+  - Includes test names, durations, failure messages
+
+- **HTML Reporter**: Generate visual HTML reports
+  - `--html` flag outputs styled HTML report
+  - Expandable sections for requests, responses, assertions
+  - Easy sharing and archiving of test results
+
+### Fixed
+- **Print Statement Variable Resolution**: `{{$1.status}}` now resolves correctly in print statements
+  - Response references (`$1`, `$2`, etc.) are now stored in runtime variables
+  - Works in both print statements and variable assignments
+
+## [1.0.26] - 2026-01-31
+
+### Added
+- **Sequence Tags**: Tag sequences with `@smoke`, `@team(CustomerExp)` for filtering in CI/CD
+  - Simple tags: `@smoke @regression` before `sequence` declaration
+  - Key-value tags: `@team(CustomerExp)`, `@priority(high)`, `@jira(NORN-123)`
+  - Multiple tags on same line or separate lines
+  - Case-insensitive tag matching
+
+- **CLI Tag Filtering**: Filter sequences by tags when running from command line
+  - `--tag smoke` - AND logic (can repeat: `--tag smoke --tag auth`)
+  - `--tags smoke,regression` - OR logic (comma-separated)
+  - Key-value matching: `--tag team(CustomerExp)`
+  - Nested sequences silently skipped when tag filter is active and they don't match
+
+- **Tag IntelliSense**: Type `@` to see existing tags from workspace
+  - Auto-completes simple tags and key-value tags
+  - Suggests common tags: `smoke`, `regression`, `wip`, `skip`, `team`, `priority`
+
+- **Tag Diagnostics**: Warning when tags are placed incorrectly (not before `sequence`)
+
+### Changed
+- **Regression Test Runner**: `run-all.sh` now supports `--tag` and `--tags` options
+  - Example: `./run-all.sh --tag smoke` runs only smoke-tagged sequences
+
+## [1.0.25] - 2026-01-28
+
+### Added
+- **Capture Named Request Response**: `var response = run NamedRequest` now works
+  - Previously only `run NamedRequest` (without capture) worked
+  - Now you can capture the full HTTP response including `status`, `body`, and `headers`
+  - Example: `var resp = run GetSingleTodo` then `assert resp.status == 200`
+
+## [1.0.24] - 2026-01-27
+
+### Changed
+- **Single Return Values**: Single returns now pass the raw value, not a wrapped object
+  - `return myValue` → caller receives the value directly (e.g., `"level-3-data"`)
+  - `return a, b` → caller receives `{a: valueA, b: valueB}` object
+  - This matches intuitive behavior: "return the value" means pass the value itself
+  - Example: `var result = run GetEmail` where `GetEmail` does `return email` → `result` is the email string
+
+### Fixed
+- **Regression Tests**: Updated test expectations to match correct single-return behavior
+  - Tests now correctly assert raw values instead of accessing `.property` on single returns
+
+## [1.0.23] - 2026-01-26
+
+### Fixed
+- **Sequence Return Value Consistency**: Single and multiple return statements now behave identically
+  - Fixed `assert result.value == "data"` failing with "Variable not defined" for single returns
+  - All return values are now wrapped in a JSON object, so `result.myValue` works consistently
+
+- **API Endpoint Request Bodies**: POST/PUT/PATCH with endpoint syntax now includes the body
+  - Fixed `POST HttpBinPost Json` followed by `{"test": "data"}` sending empty body
+  - Body lines after endpoint requests are now correctly extracted and sent
+
+- **Variable Quote Stripping**: Quoted string values are now stored without quotes
+  - Fixed `var url = "https://example.com"` being used as `"https://example.com"/path`
+  - Quotes are stripped during variable extraction for cleaner substitution
+
+## [1.0.22] - 2026-01-26
+
+### Fixed
+- **Standalone API Requests**: `GET GetPetById(1)` now works outside of sequences
+  - Fixed "Invalid URL" error when clicking CodeLens on API endpoint requests
+  - API detection now correctly skips blank lines, comments, and import lines
+
+## [1.0.21] - 2026-01-25
+
+### Fixed
+- **Script Variable Capture**: `var id = run powershell "script.ps1"` now correctly captures and parses JSON output
+  - Script output is automatically parsed as JSON when valid, enabling `id[0].property` access
+  - Fixed detection to not confuse `run powershell` with `run SequenceName`
+
+- **Sequence Return Values**: `return id[0].id` now correctly returns nested values
+  - Fixed path parsing for array and property access in return statements
+  - Return values preserve their type (number, object, etc.) instead of being stringified
+
+- **Sub-sequence API Endpoints**: API endpoints now work correctly in sub-sequences
+  - Fixed `GET GetUser(id)` not resolving when called from `run Get_200(id)`
+  - API definitions are now properly passed to nested sequence calls
+
+## [1.0.20] - 2026-01-25
+
+### Added
+- **Swagger/OpenAPI Import**: Import endpoints from OpenAPI specifications in `.nornapi` files
+  - Add `swagger https://api.example.com/swagger.json` to your `.nornapi` file
+  - Click "Import Endpoints" CodeLens button to fetch and parse the spec
+  - Select which sections to import (All, or specific tags like pet/store/user)
+  - Customize the base URL for generated endpoints
+  - Supports OpenAPI 2.0 (Swagger) and OpenAPI 3.x specifications
+  - Generates clean endpoint definitions: `EndpointName: METHOD /path`
+
+## [1.0.19] - 2026-01-25
+
+### Improved
+- **Simplified IntelliSense**: Completions now insert just the keyword without extra placeholders
+  - HTTP methods insert `GET ` instead of `GET https://` with snippet
+  - `var`, `run`, `assert` insert just the keyword for natural typing
+  - Endpoint completions insert just the name, letting you add `()` manually
+
+- **Better Syntax Highlighting for JSON Bodies**: Full JSON coloring in request bodies
+  - Property keys highlighted as property names
+  - String values highlighted as strings
+  - Numbers highlighted as numbers
+  - Variable references `{{var}}` highlighted inside strings
+  - Works with or without blank line between headers and body
+
+- **Print Statement Syntax Highlighting**: Distinct colors for different elements
+  - Quoted strings show string color
+  - Variables show variable color
+  - `+` operator highlighted
+
+- **Variable Assignment Highlighting**: Better coloring for `var x = value`
+  - Variable paths like `result[0].id` highlighted as variables (not strings)
+
+### Added
+- **Missing Concatenation Diagnostics**: Red squiggly when `+` is missing between values in print
+  - `print "Result: " result` shows error between string and variable
+  - Suggests adding `+` operator
+
+- **Missing Parameter Diagnostics**: Red squiggly when calling sequence without required parameters
+  - `run Teardown` shows error if `Teardown(sessionId)` requires a parameter
+  - Shows required parameter names in error message
+
+### Fixed
+- Auto-closing parentheses now works - typing `(` inserts `)`
+- IntelliSense triggers when typing inside parentheses
+
+## [1.0.18] - 2026-01-24
+
+### Added
+- **Variable Request Capture**: Capture HTTP responses into variables for stable assertions
+  - Syntax: `var user = GET {{baseUrl}}/users/1` or `var user = GET GetUser(1) Json`
+  - Access response properties: `user.body.username`, `user.status`, `user.headers`
+  - Eliminates need for fragile `$1`, `$2` references that break when requests change
+  - Full support for named endpoints with header groups
+
+- **IntelliSense for Variable Request Capture**
+  - HTTP methods (GET, POST, etc.) shown after `var x = `
+  - Endpoint suggestions from `.nornapi` files after method
+  - Header group suggestions after endpoint (Auth, Json, etc.)
+  - Response property completions for captured variables (`user.body.`, `user.headers.`)
+
+- **Diagnostics for Variable Request Capture**
+  - Red squiggly for undefined endpoints in `var x = GET UnknownEndpoint`
+  - Red squiggly for undefined header groups in `var x = GET GetUser(1) InvalidGroup`
+
+- **Syntax Highlighting for Variable Request Capture**
+  - Endpoint name styled as function
+  - Parameters styled appropriately
+  - Header groups styled in green (matching other header group references)
+
+## [1.0.17] - 2026-01-24
+
+### Added
+- **API Definition Files (.nornapi)**: New file format for defining reusable API configurations
+  - Define header groups with `headers GroupName` / `end headers`
+  - Define endpoint templates with `endpoints /path` / `end endpoints`
+  - Import into .norn files with `import "./api.nornapi"`
+  - IntelliSense support for .nornapi keywords and common headers
+  - Custom file icon for .nornapi files
+
+- **Enhanced Sequence Request Display**: Request steps in sequences now show full details
+  - URL display with method badge (color-coded by HTTP method)
+  - Tabs for Body, Headers, and Cookies (same as single request view)
+  - Copy button for response body
+  - JSON syntax highlighting in response body
+
+- **File Icons**: Custom icons for Norn file types
+  - `.nornapi` files show network connection icon
+  - `.nornenv` files show globe icon
+
+### Fixed
+- Comments no longer show diagnostic errors for undefined variables
+- Lines starting with `#` or `//` are properly skipped during variable validation
+
+## [1.0.16] - 2026-01-24
+
+### Added
+- **Sequence Parameters**: Sequences can now accept parameters with optional default values
+  - Declare parameters: `sequence Login(username, password = "secret123")`
+  - Call with positional args: `run Login("admin", "mypass")`
+  - Call with named args: `run Login(password: "pass", username: "user")`
+  - Parameters with defaults are optional
+  - Required parameters must come before optional ones
+
+- **Sequence Return Values**: Sequences can return multiple values
+  - Return statement: `return token, userId`
+  - Capture in caller: `var result = run Login("admin")`
+  - Access fields: `{{result.token}}`, `{{result.userId}}`
+
+- **IntelliSense for Return Fields**: Property completions for sequence return values
+  - Type `{{result.` to see available fields from the sequence's return statement
+  - Works for sequences in the same file and imported files
+
+- **CLI Print Support**: Print statements now display in CLI output with `[print]` prefix
+
+### Fixed
+- Sequence parameters no longer show as undefined variables in diagnostics
+- CodeLens "Run Sequence" now shows for sequences where all parameters have defaults
+
+### Examples
+
+```norn
+sequence CreateUser(name, role = "user", active = "true")
+    print Creating {{name}} with role {{role}}
+    POST {{baseUrl}}/users
+    Content-Type: application/json
+    {"name": "{{name}}", "role": "{{role}}", "active": {{active}}}
+    
+    var id = $1.body.id
+    return id, name, role
+end sequence
+
+sequence TestUsers
+    # Positional args
+    var admin = run CreateUser("Admin", "admin", "true")
+    print Admin ID: {{admin.id}}
+    
+    # Named args (any order)
+    var guest = run CreateUser(role: "guest", name: "Guest")
+    print Guest ID: {{guest.id}}
+    
+    # Use defaults
+    run CreateUser("DefaultUser")
+end sequence
+```
+
+## [1.0.15] - 2026-01-24
+
+### Added
+- **Sequence Composition**: Sequences can now call other sequences with `run SequenceName`
+  - Enables modular test design with reusable setup/teardown patterns
+  - Variables set in called sequences are available to the caller
+  - Sequences can be nested to any depth
+  - Circular references are detected and reported as errors
+  - Sub-sequences shown in collapsible groups in the response panel
+
+- **File Imports**: Import named requests and sequences from other files
+  - `import "./common.norn"` - import from relative path
+  - Nested imports supported (imported files can import other files)
+  - Circular imports detected and reported
+  - Variables resolved at import time (baked in), not exported
+  - `.nornenv` environment variables shared across all files
+
+- **Response Panel Improvements**:
+  - Steps start collapsed by default for cleaner view
+  - "Expand All" / "Collapse All" button in sequence header
+  - Sub-sequence calls shown in collapsible groups with 📦 icon
+  - Failed sub-sequences show error styling
+
+### Examples
+
+```norn
+# common.norn - shared utilities
+var baseUrl = https://api.example.com
+
+[AuthRequest]
+POST {{baseUrl}}/auth/login
+Content-Type: application/json
+{"username": "admin", "password": "secret"}
+
+sequence SharedSetup
+    run AuthRequest
+    var token = $1.body.accessToken
+end sequence
+```
+
+```norn
+# main-test.norn
+import "./common.norn"
+
+sequence MyTests
+    run SharedSetup
+    
+    GET {{baseUrl}}/users/me
+    Authorization: Bearer {{token}}
+    assert $1.status == 200
+end sequence
+```
+
+## [1.0.14] - 2026-01-23
+
+### Added
+- **Variable expression assignment**: Assign variables from expressions without `{{}}`
+  - `var id = data.users[0].id` - extract from JSON variable
+  - `var name = "John"` - quoted string literals
+  - `var count = 123` - numeric literals
+  - `var active = true` - boolean literals
+- **PowerShell output parsing**: Automatic parsing of PowerShell table/list output to JSON
+  - Table format with headers and `---` separators
+  - List format with `Key : Value` pairs
+  - ANSI escape code stripping for clean output
+- **Improved syntax highlighting**: Different colors for value types in variable assignments
+  - Quoted strings, numbers, booleans, variable references, URLs
+- **IntelliSense for variable assignments**: After `var x = `, shows:
+  - Defined variables with their values
+  - Keywords: `true`, `false`, `null`
+  - Run commands
+- **Diagnostic for invalid assignments**: Red squiggly for:
+  - Unquoted strings with spaces: `var x = hello world`
+  - Undefined variable references: `var x = unknownVar`
+
+### Examples
+
+```norn
+sequence DataExtraction
+    # Load JSON data
+    var config = run readJson ./config.json
+    
+    # Extract values directly (no {{}} needed)
+    var userId = config.users[0].id
+    var userName = config.users[0].name
+    
+    # Use string literals with interpolation
+    var greeting = "Hello {{userName}}"
+    
+    # PowerShell scripts now auto-parse to JSON
+    var dbResult = run powershell ./query.ps1
+    var recordId = dbResult.Id
+    
+    print Result | User {{userId}}: {{userName}}
+end sequence
+```
+
+## [1.0.13] - 2026-01-22
+
+### Added
+- **`wait` command**: Pause execution for a specified duration
+  - Formats: `wait 2s`, `wait 500ms`, `wait 1.5 seconds`
+  - Useful for testing async operations or rate-limited APIs
+- **`if` statements**: Conditional execution of steps based on response data
+  - Use any assertion operator: `if $1.status == 200 ... end if`
+  - Supports nesting: multiple if blocks can be nested
+  - Skipped steps are not executed when condition is false
+- **`isType` assertion**: Type checking for response values
+  - Supported types: `number`, `string`, `boolean`, `array`, `object`, `null`
+  - Example: `assert $1.body.id isType number`
+  - Example: `assert $1.body.tags isType array`
+- **CLI improvements**:
+  - `--env` / `-e`: Select environment from `.nornenv`
+  - `--request` / `-r`: Run a specific named request
+  - `--timeout` / `-t`: Request timeout in seconds
+  - `--verbose` now shows response headers
+
+### Examples
+
+```norn
+sequence ConditionalExample
+    GET {{baseUrl}}/users/1
+    
+    # Type assertions
+    assert $1.body.id isType number
+    assert $1.body.name isType string
+    assert $1.body.roles isType array
+    
+    # Conditional execution
+    if $1.status == 200
+        print Success | User found
+        
+        # Wait before next request (rate limiting)
+        wait 1s
+        
+        GET {{baseUrl}}/users/1/profile
+        assert $2.status == 200
+    end if
+    
+    if $1.status == 404
+        print Not Found | User does not exist
+    end if
+end sequence
+```
+
+## [1.0.12] - 2026-01-22
+
+### Added
+- **JSON file reading**: Load JSON files into variables with `var config = run readJson ./path/to/file.json`
+  - Access nested properties: `{{config.database.host}}`, `{{config.users[0].name}}`
+  - Modify properties inline: `config.apiKey = {{newKey}}`
+- **IntelliSense for `run` commands**: Typing `run` and selecting it automatically triggers IntelliSense showing available options:
+  - Script types: `bash`, `powershell`, `js`, `readJson`
+  - Named requests defined in the file
+- **Method icons**: Script type completions now show method icons for better visual distinction
+- **Smart IntelliSense triggers**: Space after `run` automatically shows available options
+
+### Changed
+- **Simplified completions**: Removed snippet placeholders from `run` command completions - now inserts plain text for cleaner experience
+- **Refactored completion logic**: `run` command completions now share logic between standalone `run` and `var x = run` contexts
+
+## [1.0.11] - 2026-01-21
+
+### Added
+- **Assertions**: New `assert` command for validating HTTP responses in sequences
+  - Operators: `==`, `!=`, `>`, `>=`, `<`, `<=`, `contains`, `startsWith`, `endsWith`, `matches`, `exists`, `!exists`
+  - Assert on status: `assert $1.status == 200`
+  - Assert on body: `assert $1.body.userId == 1`
+  - Assert on headers: `assert $1.headers.Content-Type contains "application/json"`
+  - Assert duration: `assert $1.duration < 5000`
+  - Custom failure messages: `assert $1.body.id == 999 | "Expected different ID"`
+- **IntelliSense for response properties**: After typing `$1.`, shows completions for `status`, `statusText`, `headers`, `body`, `duration`
+- **Assertion syntax highlighting**: `assert` commands now have proper syntax coloring
+
+### Changed
+- **BREAKING**: Response body access now requires explicit `body.` prefix
+  - Before: `$1.userId` or `$1[0].title`
+  - After: `$1.body.userId` or `$1.body[0].title`
+  - This makes it clearer what you're accessing (status vs headers vs body)
+
+## [1.0.10] - 2026-01-20
+
+### Fixed
+- **PowerShell 7 support**: Now prefers `pwsh` (PowerShell 7+) over `powershell` (Windows PowerShell 5.1) for script execution. PowerShell 7 has newer SqlClient drivers that support additional connection string options like `HostNameInCertificate`. Falls back to Windows PowerShell if pwsh is not installed.
+
+## [1.0.9] - 2026-01-20
+
+### Added
+- **Streaming sequence results**: Sequence steps now appear in the response panel as they complete, providing real-time feedback during long-running sequences
+- **Variable assignment IntelliSense**: After typing `var x = run `, IntelliSense now shows available script types (bash, powershell, js) AND named requests to run
+- **Named request capture syntax**: Support for `var result = run MyRequest` to capture a named request's response into a variable
+
+### Fixed
+- **`run` keyword highlighting**: The `run` keyword is now properly highlighted while typing, before completing the full command
+- **Partial command highlighting**: `var x = run` and `var x = run bash` now highlight correctly while still typing
+- **IntelliSense after `run `**: Typing `run ` (with trailing space) now properly triggers IntelliSense suggestions
+- **Sequence re-run cleanup**: Running a sequence again now properly clears previous results instead of appending to them
+
+## [1.0.8] - 2026-01-19
+
+### Added
+- **Add env file**: When no `.nornenv` file exists, CodeLens shows "**+ Add env file**" - clicking it creates a template file with common variables and dev/prod environments ready to customize
+
+### Fixed
+- **Parser fix**: Body extraction now stops at request boundaries (`[SomeName]`, `sequence`, HTTP methods). Previously `[SomeName]` after URL-encoded params was incorrectly included in the body.
+
+## [1.0.7] - 2026-01-19
+
+### Fixed
+- **Syntax highlighting**: Proper stateful parsing - headers before blank line get header color, body params after blank line get parameter color (like the parser does)
+
+## [1.0.6] - 2026-01-19
+
+### Fixed
+- **URL-encoded body support**: Now supports `key: value` format (colon) in addition to `key=value` for form data
+- **Syntax highlighting**: Body parameters now have distinct highlighting from headers (different color for `username:` vs `Content-Type:`)
+
+## [1.0.5] - 2026-01-19
+
+### Fixed
+- **Fixed**: File icon resolution 
+- **Fixed header/body parsing**: Parser now uses blank line to separate headers from body (standard HTTP convention). This fixes 400 errors when URL-encoded form data params like `username: value` were incorrectly parsed as headers.
+
+## [1.0.4] - 2026-01-19
+
+### Added
+- **Named Requests**: Define reusable requests with `[RequestName]` and call them with `run RequestName` in sequences
+- **Environment Support**: Create `.nornenv` file with environment-specific variables
+  - Common variables available in all environments
+  - Switch environments via status bar or CodeLens
+  - Environment variables shown in IntelliSense with source indicator
+- **URL-encoded Form Data**: Support for `application/x-www-form-urlencoded` with multi-line format
+- **Environment Selector in CodeLens**: Click `env: dev` next to Send Request to switch environments
+
+### Changed
+- Changed language ID from `http` to `norn` to avoid conflicts with other extensions
+- Improved syntax highlighting for `[RequestName]` declarations and `run` commands
+
+### Fixed
+- Diagnostics now respect environment variables (no false "undefined variable" errors)
+- Diagnostics refresh when switching environments
+- Named request names now enforce no-spaces rule with error highlighting
+
+## [1.0.3] - 2026-01-18
+
+- Fix 'sequence' not being recognized as a keyword
+- Fixed an issue where if the name was of the sequence had a '-' it will be highlighted incorrectly 
+
+## [1.0.2] - 2026-01-18
+
+### Added
+- Capture entire response body with `var data = $1`
+- Capture array elements with `var item = $1[0]`
+- Extended evaluation period to 30 days
+
+### Fixed
+- Array index capture syntax now works correctly (`$1[0].field`)
+
+## [1.0.1] - 2026-01-18
+
+### Fixed
+- Improved file icon resolution (128x128)
+- Updated license badge in README
+
+## [1.0.0] - 2025-01-15
+
+### Added
+- **HTTP Requests**: Send GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS requests
+- **Variables**: Define with `var name = value`, reference with `{{name}}`
+- **Sequences**: Chain multiple requests with `sequence Name` / `end sequence`
+- **Response Capture**: Capture values from responses with `$N.path` syntax
+- **Script Execution**: Run bash, PowerShell, or JavaScript scripts with `run` command
+- **Print Statements**: Debug output with `print Message` or `print Title | Body`
+- **Cookie Support**: Automatic cookie jar with persistence across requests
+- **Syntax Highlighting**: Full highlighting for HTTP methods, headers, JSON bodies
+- **IntelliSense**: Autocomplete for methods, headers, variables, and keywords
+- **Diagnostics**: Error highlighting for undefined variables
+- **CLI Tool**: Run requests from terminal with JSON output for CI/CD pipelines
+- **Response Panel**: Webview with formatted JSON and execution results

package/LICENSE

@@ -0,0 +1,94 @@
+End User License Agreement
+
+This End User License Agreement ("Agreement") is a legal contract between you as an individual or business organisation ("you" or "Licensee") and the Norn developer ("Licensor") for the Norn software (all editions), including any associated media, printed materials and electronic documentation (the "Software").
+
+By copying, downloading, accessing, or otherwise using the Software, you agree to be bound by the terms of this Agreement and you warrant and represent that you are authorised to enter into this Agreement on behalf of yourself or your business organisation.
+
+If you do not wish to be bound by the terms of this Agreement, you may not download, install, access or use the Software.
+
+• DEFINITIONS
+
+"Authorized User" means any employee, independent contractor or other temporary worker authorized by Licensee to use the Software while performing duties within the scope of their employment or assignment.
+
+"License Key" means a unique key-code that enables a single Authorized User to use the Software at a time. Only Licensor and/or its representatives are permitted to produce License Keys for the Software.
+
+"Commercial Use" means any use of the Software in connection with a business, including but not limited to: (a) use by an employee or contractor during paid work hours, (b) use to develop, test, or maintain software or services that generate revenue, (c) use within a for-profit organisation, or (d) use in CI/CD pipelines for commercial projects.
+
+"Personal Use" means use by an individual for personal projects, learning, education, or open-source projects that do not generate revenue.
+
+• OWNERSHIP
+
+This Agreement does not convey to you any rights of ownership in the Software. All right, title, benefit and interest in the Software and in any ideas, know-how, and programs which are developed by Licensor in the course of providing any technical services, including any enhancements or modifications made to the Software, shall at all times remain the property of Licensor.
+
+• GRANT OF LICENSE
+
+Upon your acceptance of this Agreement, Licensor grants you a limited, non-transferable, non-assignable, non-exclusive license to install and use the Software on the terms and conditions set forth herein.
+
+• INTENDED USERS OF THE SOFTWARE
+
+The Norn software is licensed to provide functionality to test APIs in Visual Studio Code as an Extension. The Norn CLI can be used locally on the user's computer for Personal Use without a license. A license is required to use the Software for Commercial Use, including use of the Norn CLI in CI/CD build pipelines.
+
+• FREE USE (PERSONAL USE)
+
+You may install and use the Software free of charge for Personal Use, including:
+- Personal projects and experimentation
+- Learning and educational purposes
+- Open-source projects that do not generate revenue
+- Academic research
+
+• COMMERCIAL EVALUATION
+
+Businesses and organisations may evaluate the Software for Commercial Use without a license for a period of thirty (30) days from first use ("Evaluation Period"). The Evaluation Period is:
+- Limited to one (1) evaluation period per organisation
+- Intended for genuine evaluation purposes only
+- Not to be used for production workloads or client projects
+- Not extendable or renewable without written permission from the Licensor
+
+After the Evaluation Period, continued Commercial Use requires a valid license. Abuse of the Evaluation Period, including but not limited to repeated evaluations by the same organisation, rotating users to extend evaluation, or using evaluation for production purposes, constitutes a breach of this Agreement.
+
+• COMMERCIAL USE
+
+A license is required for Commercial Use of the Software after the Evaluation Period. Commercial Use includes but is not limited to:
+- Use within a for-profit company or organisation
+- Use by employees or contractors during paid work
+- Use in CI/CD pipelines for commercial projects
+- Use to develop, test, or maintain revenue-generating software or services
+
+Please contact the Licensor for commercial licensing options.
+
+• RESTRICTIONS ON USE OF THE SOFTWARE
+
+You are NOT permitted to:
+a) Edit, alter, modify, adapt, translate or otherwise change the whole or any part of the Software.
+b) Decompile, disassemble or reverse engineer the Software or attempt to do any such things.
+c) Reproduce, copy, distribute, resell or otherwise use the whole or any part of the Software's code for any commercial purpose.
+d) Disable, modify or hide notifications sent by the Software.
+e) Distribute, resell, or share License Keys.
+f) Misrepresent your use as Personal Use when it constitutes Commercial Use.
+g) Use older versions of the Software to circumvent licensing requirements.
+
+• LIMITED WARRANTY AND DISCLAIMER OF WARRANTY
+
+SOFTWARE IS PROVIDED TO LICENSEE "AS IS" AND WITHOUT WARRANTIES. LICENSOR MAKES NO WARRANTY AS TO ITS USE OR PERFORMANCE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LICENSOR AND ITS AFFILIATES, SUPPLIERS AND RESELLERS DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT, WITH REGARD TO SOFTWARE, AND THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES.
+
+• DISCLAIMER OF DAMAGES
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO LICENSEE UNDER ANY THEORY FOR ANY DAMAGES SUFFERED BY LICENSEE OR ANY USER OF SOFTWARE, OR FOR ANY SPECIAL, INCIDENTAL, INDIRECT, CONSEQUENTIAL, OR SIMILAR DAMAGES (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF REASONABLE CARE, FOR NEGLIGENCE, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF THE USE OR INABILITY TO USE SOFTWARE, OR THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND REGARDLESS OF THE LEGAL OR EQUITABLE THEORY (CONTRACT, TORT OR OTHERWISE) UPON WHICH THE CLAIM IS BASED.
+
+IN ANY CASE, LICENSOR'S ENTIRE LIABILITY UNDER ANY PROVISION OF THIS AGREEMENT WILL BE LIMITED TO THE AMOUNT ACTUALLY PAID BY LICENSEE FOR SOFTWARE UNDER THIS AGREEMENT.
+
+• TERMINATION
+
+This license can be terminated by you at any time. If you choose to terminate the license, you will not be entitled to any refund of the license fee(s) you have paid. Your license may be terminated by Licensor if you fail to comply with the terms of this Agreement within ten (10) days after receipt of written notice of such failure. In the event of termination, you must cease using the Software, destroy all copies of the Software (including copies in storage media) and certify such destruction to Licensor. This requirement applies to all copies in any form, partial or complete. Upon the effective date of any termination, you relinquish all rights granted under this Agreement.
+
+• RELATIONSHIP OF PARTIES
+
+You and Licensor are independent parties. Nothing in this Agreement shall be construed as making you an employee, agent, partner or legal representative of Licensor.
+
+• ENTIRE AGREEMENT
+
+This Agreement and any document expressly referred to in it constitute the whole agreement between you and the Licensor and supersede any previous arrangement understanding or agreement between you and the Licensor, relating to the licensing of the Software.
+
+The parties acknowledge that, in entering into this Agreement (and the documents referred to in it), neither party relies on any statement, representation, assurance or warranty ("Representation") of any person (whether a party to this Agreement or not) other than as expressly set out in this Agreement or those documents.
+
+The parties agree that the only rights and remedies available to each party arising out of or in connection with a Representation shall be for breach of contract as provided in this Agreement.