@winkjs/composer 0.0.2 → 0.4.1

package/CONTRIBUTING.md

@@ -1,132 +0,0 @@
-# Contributing to Wink Composer
-
-Thank you for taking time to contribute. We are delighted to receive contributions from the community. For `wink-composer` every contribution matters — whether you are reporting a **bug**, posting a **question** or **suggestion**, submitting a **pull request** or updating the **documentation**.
-
-This document will guide you through the contribution process and guidelines.
-
-## Getting Started
-If you spot a bug/issue and the same has not yet been reported, [raise a new issue](https://github.com/winkjs/wink-composer/issues) or consider fixing it and sending a PR. If you have questions and/or suggestions, post them at our [discussions](https://github.com/winkjs/wink-composer/discussions). New features may also be discussed there; eventually you may consider developing the same and sending a PR.
-
-### How to send a PR?
-
-1. Fork the repository from github
-2. Develop your code changes
-4. Capture the logic in comments
-3. Ensure that the API is properly documented
-4. Ensure proper linting
-2. Write test cases to cover each and every change and/or new feature
-2. Review security and performance
-5. Run the entire test suite
-6. Make sure coverage either stays at the current levels or improves; note minimum acceptable level is ≥99.5%
-7. Commit your changes in compliance with commit guidelines
-8. Push to your fork
-9. [Sign the CLA](https://cla-assistant.io/winkjs/wink-composer) if you are contributing for the first time
-
-After completing the above steps, you are ready to submit the pull request.
-
-
-## Code of Conduct
-By contributing, you are expected to uphold [wink’s code of conduct](CODE_OF_CONDUCT.md). In essence, each one of us should:
-
-1. respect fellow contributors, irrespective of their level of experience, race, religion, gender, sexual orientation, and age;
-2. collaborate constructively;
-3. never engage in any form of offense, harassment,  insult, personal attack, provocation and/or use of inappropriate language;
-
-
-
-## Development Guidelines
-Wink-composer is an open-source JavaScript library that aims to simplify the creation of LLM-driven applications.
-
-Do take out some time in understanding the structure of APIs, before attempting any enhancements.
-
-In wink composer, we prefer **functions** and **closures** over objects/classes.
-
-Like artisans, we too need a toolset and process to create beautiful software. The process is orchestrated by Github Actions in accordance with the configuration files present in the repository. The details are outlined below:
-
-
-### Linting
-Well defined linting rules or **coding standards** help us in making code more consistent and avoid bugs. [ESLint](https://eslint.org) enforces these rules automatically. These rules are defined in a configuration file named `.eslintrc.json`, which is located at the root of the repository. These rules cover basic formatting, naming conventions, limits of code complexity, and many more; please refer to the configuration file for further details.
-
-We recommend using a suitable ESLint plugin/add-on for the code editor. Use script **`npm run pretest`** at command line to run linting on the entire code.
-
-
-### Documenting
-We believe that the documentation must not only explain the API but also narrate the story of logic, algorithms and references used. Wink Composer uses the [JSDoc](https://jsdoc.app) standard for API documentation. It is inspired by [Literate-Programming Standards](https://en.wikipedia.org/wiki/Literate_programming) for documenting the logic using [docker](http://jbt.github.io/docker/src/docker.js.html); the **`npm run sourcedocs`** script generates a well formatted code documentation in HTML.
-
-### Testing
-Test cases should cover each and every feature and/or change; use of standard test heuristics such as equivalence partition, boundary values, empty/null value, and decision tree is recommended to write effective test cases.
-
-Wink Composer requires a test coverage of **at least ≥99.5%** and aims for 100%. Any new contribution must maintain the existing test coverage level. We use [Chai](http://chaijs.com/), [Mocha](https://mochajs.org/) and [nyc](https://github.com/istanbuljs/nyc), [Coveralls](https://coveralls.io/) to run tests and determine coverage.
-
-Use script **`npm run test`** at command line to run the entire test suite and obtain test coverage report.
-
-#### Performance Considerations
-It is important to maintain the performance of wink composer, whenever a change is made and/or a new feature is added. We use the [benchmark](https://benchmarkjs.com) package to measure performance.
-
-#### Security Considerations
-Our security review/testing is inspired from the recommendations in [OWASP's NodeJS Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Nodejs_Security_Cheat_Sheet.html) that are applicable to wink-composer —  since it is a library used by developers to create LLM web/mobile/CLI  apps/tools, only Platform Security specific recommendations apply. We follow the  guidelines outlined below:
-
-1. Minimize external dependencies.
-2. Use ESLint as a Static Analysis Security Testing (SAST) tool.
-3. Never use `eval()` function.
-4. Avoid prototype pollution by using objects created via **`Object.create( null )`**.
-5. Perform input validation with defined default behavior.
-6. Use  tools like [regexploit](https://github.com/doyensec/regexploit) to detect potential ReDoS apart from reviewing regexes using  [regex 101](https://regex101.com) on Chrome browser (Latest stable version), Node.js (LTS version).
-
-### Committing
-We follow [commit guidelines](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commits) from Google's [Angular Project](https://angular.io/), whose documentation is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). See important excerpts for quick reference below:
-
-#### Commit Message Format
-Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**:
-
-    <type>(<scope>): <subject>
-    <BLANK LINE>
-    <body>
-    <BLANK LINE>
-    <footer>
-
-The header is **mandatory** and the scope of the header is optional. Any line of the commit message should not be longer than 100 characters!
-
-**Type** should be one of the following:
-
-- `build`: Changes that affect the build system or external dependencies
-- `ci`: Changes to our CI configuration files and scripts
-- `docs`: Documentation only changes
-- `feat`: A new feature
-- `fix`: A bug fix
-- `perf`: A code change that improves performance
-- `refactor`: A code change that neither fixes a bug nor adds a feature
-- `test`: Adding missing tests or correcting existing tests
-- `revert:` When you have to revert to an older commit. Ths subject should be the header of the old  commit and the body should contain `This reverts commit <hash>.` Use the `git revert` command to accomplish this.
-
-**Scope** specifies the  place of the commit change. You can use `*` when the change affects more than a single scope.
-
-**Subject** must contain a crisp description of the change and it must (a) use the imperative, present tense: "change" not "changed" nor "changes", (b) not capitalize the first letter, and (c) not use period (.) at the end.
-
-**Body** just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change.
-
-**Footer** should contain any information about **Breaking Changes** and is also the place to reference [GitHub issues that this commit closes](https://help.github.com/articles/closing-issues-via-commit-messages/). Breaking Changes should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
-
-## Versioning
-Wink Composer follows [semantic versioning](https://semver.org/) for every release.
-
-## Governance
-This section outlines wink-composer’s governance  guidelines:
-1. This is a project of [Graype Systems Private Limited (Graype)](http://graype.in), which is a micro-size company incorporated in India.
-1. The project team consists of 3-core members, including a technical lead.
-1. The project welcomes contributions from the community. For wink-composer every contribution matters — whether it  is [reporting a bug/issue](https://github.com/winkjs/wink-composer/issues), [posting a question/suggestion](https://github.com/winkjs/wink-composer/discussions), submitting a pull request or updating the documentation.
-1. Everyone is entitled to state their opinion and may present their arguments. There is an effort to achieve consensus but in absence of obvious consensus, the technical lead has the final say in decision making. It roughly matches a standard BDFL (Benevolent Dictator For Life) style project.
-1. Wink Composer is licensed under the terms of the MIT license; therefore there are no limitations on forking and developing it further separately.
-1. The technical lead has commit and administrative rights on the project's [organization](https://github.com/winkjs) and [repository](https://github.com/winkjs/wink-composer) at Github. Therefore the technical lead can make changes and accept changes — typically pull requests submitted by others. These changes may include changes to the process and contribution requirements.
-1. [Graype](http://graype.in) offers commercial support and/or services around the project.
-1. The key roles are (a) User — who uses or has used the package; (b) Contributor — who has reported one or more issues, participated in one or more discussions OR sent one or more PRs; (c) Core Team Member as stated above and (d) Technical Lead.
-1. Core team members are Prateek Saxena, Rachna Chakraborty and Sanjaya Kumar Saxena (Technical Lead).
-1. Current opportunities to participate are outlined in the [roadmap](ROADMAP.md).
-1. Every PR must comply with our [development guidelines](CONTRIBUTING.md#development-guidelines) before they can be accepted/merged.
-1. Participation requires adherence to our [code of conduct](CODE_OF_CONDUCT.md).
-
-
-
-## Contributor License Agreement (CLA)
-
-The [CLA](https://gist.github.com/sanjayaksaxena/8b96d3d4f2be6cdc0f28a5839d5a5b2a) is for your protection as well as the protection of [Graype](http://graype.in) and it’s licensees; it does not change your rights to use your own Contributions for any other purpose. Our CLA is a short and easy to understand agreement and can be signed using a simple click-through form.  Please [sign our Contributor License Agreement (CLA)](https://cla-assistant.io/winkjs/wink-composer) before sending pull requests. It's a quick process, we promise!

package/docs/CONTRIBUTING.md

@@ -1,134 +0,0 @@
-# Contributing to Wink Composer
-
-Thank you for taking time to contribute. We are delighted to receive contributions from the community. For `wink-composer` every contribution matters — whether you are reporting a **bug**, posting a **question** or **suggestion**, submitting a **pull request** or updating the **documentation**.
-
-This document will guide you through the contribution process and guidelines.
-
-## Getting Started
-If you spot a bug/issue and the same has not yet been reported, [raise a new issue](https://github.com/winkjs/wink-composer/issues) or consider fixing it and sending a PR. If you have questions and/or suggestions, post them at our [discussions](https://github.com/winkjs/wink-composer/discussions). New features may also be discussed there; eventually you may consider developing the same and sending a PR.
-
-### How to send a PR?
-
-1. Fork the repository from github
-2. Develop your code changes
-4. Capture the logic in comments
-3. Ensure that the API is properly documented
-4. Ensure proper linting
-2. Write test cases to cover each and every change and/or new feature
-2. Review security and performance
-5. Run the entire test suite
-6. Make sure coverage either stays at the current levels or improves; note minimum acceptable level is ≥99.5%
-* [Home](/)
-* [Guide](guide.md)
-7. Commit your changes in compliance with commit guidelines
-8. Push to your fork
-9. [Sign the CLA](https://cla-assistant.io/winkjs/wink-composer) if you are contributing for the first time
-
-After completing the above steps, you are ready to submit the pull request.
-
-
-## Code of Conduct
-By contributing, you are expected to uphold [wink’s code of conduct](CODE_OF_CONDUCT.md). In essence, each one of us should:
-
-1. respect fellow contributors, irrespective of their level of experience, race, religion, gender, sexual orientation, and age;
-2. collaborate constructively;
-3. never engage in any form of offense, harassment,  insult, personal attack, provocation and/or use of inappropriate language;
-
-
-
-## Development Guidelines
-Wink-composer is an open-source JavaScript library that aims to simplify the creation of LLM-driven applications.
-
-Do take out some time in understanding the structure of APIs, before attempting any enhancements.
-
-In wink composer, we prefer **functions** and **closures** over objects/classes.
-
-Like artisans, we too need a toolset and process to create beautiful software. The process is orchestrated by Github Actions in accordance with the configuration files present in the repository. The details are outlined below:
-
-
-### Linting
-Well defined linting rules or **coding standards** help us in making code more consistent and avoid bugs. [ESLint](https://eslint.org) enforces these rules automatically. These rules are defined in a configuration file named `.eslintrc.json`, which is located at the root of the repository. These rules cover basic formatting, naming conventions, limits of code complexity, and many more; please refer to the configuration file for further details.
-
-We recommend using a suitable ESLint plugin/add-on for the code editor. Use script **`npm run pretest`** at command line to run linting on the entire code.
-
-
-### Documenting
-We believe that the documentation must not only explain the API but also narrate the story of logic, algorithms and references used. Wink Composer uses the [JSDoc](https://jsdoc.app) standard for API documentation. It is inspired by [Literate-Programming Standards](https://en.wikipedia.org/wiki/Literate_programming) for documenting the logic using [docker](http://jbt.github.io/docker/src/docker.js.html); the **`npm run sourcedocs`** script generates a well formatted code documentation in HTML.
-
-### Testing
-Test cases should cover each and every feature and/or change; use of standard test heuristics such as equivalence partition, boundary values, empty/null value, and decision tree is recommended to write effective test cases.
-
-Wink Composer requires a test coverage of **at least ≥99.5%** and aims for 100%. Any new contribution must maintain the existing test coverage level. We use [Chai](http://chaijs.com/), [Mocha](https://mochajs.org/) and [nyc](https://github.com/istanbuljs/nyc), [Coveralls](https://coveralls.io/) to run tests and determine coverage.
-
-Use script **`npm run test`** at command line to run the entire test suite and obtain test coverage report.
-
-#### Performance Considerations
-It is important to maintain the performance of wink composer, whenever a change is made and/or a new feature is added. We use the [benchmark](https://benchmarkjs.com) package to measure performance.
-
-#### Security Considerations
-Our security review/testing is inspired from the recommendations in [OWASP's NodeJS Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Nodejs_Security_Cheat_Sheet.html) that are applicable to wink-composer —  since it is a library used by developers to create LLM web/mobile/CLI  apps/tools, only Platform Security specific recommendations apply. We follow the  guidelines outlined below:
-
-1. Minimize external dependencies.
-2. Use ESLint as a Static Analysis Security Testing (SAST) tool.
-3. Never use `eval()` function.
-4. Avoid prototype pollution by using objects created via **`Object.create( null )`**.
-5. Perform input validation with defined default behavior.
-6. Use  tools like [regexploit](https://github.com/doyensec/regexploit) to detect potential ReDoS apart from reviewing regexes using  [regex 101](https://regex101.com) on Chrome browser (Latest stable version), Node.js (LTS version).
-
-### Committing
-We follow [commit guidelines](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commits) from Google's [Angular Project](https://angular.io/), whose documentation is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). See important excerpts for quick reference below:
-
-#### Commit Message Format
-Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**:
-
-    <type>(<scope>): <subject>
-    <BLANK LINE>
-    <body>
-    <BLANK LINE>
-    <footer>
-
-The header is **mandatory** and the scope of the header is optional. Any line of the commit message should not be longer than 100 characters!
-
-**Type** should be one of the following:
-
-- `build`: Changes that affect the build system or external dependencies
-- `ci`: Changes to our CI configuration files and scripts
-- `docs`: Documentation only changes
-- `feat`: A new feature
-- `fix`: A bug fix
-- `perf`: A code change that improves performance
-- `refactor`: A code change that neither fixes a bug nor adds a feature
-- `test`: Adding missing tests or correcting existing tests
-- `revert:` When you have to revert to an older commit. Ths subject should be the header of the old  commit and the body should contain `This reverts commit <hash>.` Use the `git revert` command to accomplish this.
-
-**Scope** specifies the  place of the commit change. You can use `*` when the change affects more than a single scope.
-
-**Subject** must contain a crisp description of the change and it must (a) use the imperative, present tense: "change" not "changed" nor "changes", (b) not capitalize the first letter, and (c) not use period (.) at the end.
-
-**Body** just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change.
-
-**Footer** should contain any information about **Breaking Changes** and is also the place to reference [GitHub issues that this commit closes](https://help.github.com/articles/closing-issues-via-commit-messages/). Breaking Changes should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
-
-## Versioning
-Wink Composer follows [semantic versioning](https://semver.org/) for every release.
-
-## Governance
-This section outlines wink-composer’s governance  guidelines:
-1. This is a project of [Graype Systems Private Limited (Graype)](http://graype.in), which is a micro-size company incorporated in India.
-1. The project team consists of 3-core members, including a technical lead.
-1. The project welcomes contributions from the community. For wink-composer every contribution matters — whether it  is [reporting a bug/issue](https://github.com/winkjs/wink-composer/issues), [posting a question/suggestion](https://github.com/winkjs/wink-composer/discussions), submitting a pull request or updating the documentation.
-1. Everyone is entitled to state their opinion and may present their arguments. There is an effort to achieve consensus but in absence of obvious consensus, the technical lead has the final say in decision making. It roughly matches a standard BDFL (Benevolent Dictator For Life) style project.
-1. Wink Composer is licensed under the terms of the MIT license; therefore there are no limitations on forking and developing it further separately.
-1. The technical lead has commit and administrative rights on the project's [organization](https://github.com/winkjs) and [repository](https://github.com/winkjs/wink-composer) at Github. Therefore the technical lead can make changes and accept changes — typically pull requests submitted by others. These changes may include changes to the process and contribution requirements.
-1. [Graype](http://graype.in) offers commercial support and/or services around the project.
-1. The key roles are (a) User — who uses or has used the package; (b) Contributor — who has reported one or more issues, participated in one or more discussions OR sent one or more PRs; (c) Core Team Member as stated above and (d) Technical Lead.
-1. Core team members are Prateek Saxena, Rachna Chakraborty and Sanjaya Kumar Saxena (Technical Lead).
-1. Current opportunities to participate are outlined in the [roadmap](ROADMAP.md).
-1. Every PR must comply with our [development guidelines](CONTRIBUTING.md#development-guidelines) before they can be accepted/merged.
-1. Participation requires adherence to our [code of conduct](CODE_OF_CONDUCT.md).
-
-
-
-## Contributor License Agreement (CLA)
-
-The [CLA](https://gist.github.com/sanjayaksaxena/8b96d3d4f2be6cdc0f28a5839d5a5b2a) is for your protection as well as the protection of [Graype](http://graype.in) and it’s licensees; it does not change your rights to use your own Contributions for any other purpose. Our CLA is a short and easy to understand agreement and can be signed using a simple click-through form.  Please [sign our Contributor License Agreement (CLA)](https://cla-assistant.io/winkjs/wink-composer) before sending pull requests. It's a quick process, we promise!

package/docs/README.md

@@ -1,132 +0,0 @@
-# wink-composer ♫
-
-### [![Stability](https://img.shields.io/badge/stability-1--experimental-orange.svg)](https://nodejs.org/api/documentation.html#documentation_stability_index)
-
-## ✨ Real-time analytics that sparks joy
-
-[<img align="right" src="https://decisively.github.io/wink-logos/logo-title.png" width="100px" >](http://winkjs.org/)
-
-WinkComposer is an upcoming open-source framework that makes building streaming intelligence playfully simple. Connect intuitive nodes, experiment freely, perfect it in an iteration or two. From edge-ready AI algorithms to built-in resilience, everything you need for production comes standard. No complexity, no black boxes - just the joy of creating exactly what you need.
-
-## Why Composability Matters
-
-**🎯 Create What You Need** — With composability, you're the inventor: Correlate vibration with weather? Done. Detect micro-trends before they become macro? Built. 
-
-**💫 Countless Possibilities** — Dozens of nodes → Endless pipelines. Like few music notes creating captivating symphonies.
-
-**🌱 Evolve Naturally** — Start: `sensor → threshold → alert`. Grow: Add intelligence: `sensor → normalize → smooth → detect → confirm → alert`. Unconstrained by vendor feature lists.
-
-**🔍 Total Transparency** — See which node triggered, what threshold crossed, why it alerted. Every decision is explainable.
-
-## Build Exactly What You Need
-
-Build precise analytics for your unique patterns:
-
-```javascript
-// Detect bearing failure in rotating equipment
-vibration → isolateSignal → extractPeaks → measureIntensity →
-      trackChanges → triggerAlert
-
-// Monitor chemical process quality
-temperature → removeNoise → smoothFast → smoothSlow → findDivergence →
-      detectChange → waitForPersistence
-
-// Find correlated sensor behaviors
-[sensor1, sensor2] → trackCorrelation → compareToNormal → raiseFlag
-
-// Calculate real-time OEE
-machine → trackState → sumTime → countOutput →
-      checkQuality → calculateScore
-```
-
-Each node is simple:
-- `removeNoise`: Median of last few values (removes sensor spikes).
-- `smoothFast`: Average of last 10 values (recent trend).
-- `smoothSlow`: Average of last 100 values (baseline trend).
-- `findDivergence`: Fast trend - slow trend (unusual behavior?).
-- `trackCorrelation`: Smart correlation (learns relationships between sensors)
-
-_Node names and details are illustrative - actual implementations may vary._
-
-Every arrow is a conscious choice. Every node has a purpose. No magic, just simple intuitive math.
-
-
-## Your Analytics Journey
-
-**Start Simple**  
-`sensor → threshold → alert`
-
-**Evolve Naturally**  
-`sensor → validate → normalize → threshold → debounce → alert`
-
-**Scale Intelligently**  
-`sensor → [parallel: statistics | patterns | anomalies] → correlate → decide → act`
-
-Your analytics grow with your understanding, and are never limited by any tool's feature list.
-
-## Designed for the Real World
-
-### Industrial IoT
-From simple threshold monitoring to complex predictive maintenance - compose what fits your equipment, your patterns, your physics. **Move intelligence to the edge** with analytics that run on industrial Raspberry Pis. Works alongside your existing systems to handle your unique requirements.
-
-### Financial Services  
-Build fraud detection you can explain to auditors. Every decision traceable, every threshold justified.
-
-### Smart Infrastructure
-Energy optimization with transparent logic. See why the system made each decision.
-
-## Production-Grade Resilience
-Real streams have noise. Sensors fail. Networks hiccup. WinkComposer handles it all:
-
-- **Node-level fault isolation** - One bad reading doesn't crash your pipeline
-- **Automatic state recovery** - Snapshot and restore without missing a beat
-- **Built-in observability** - Know what's happening in every node, every partition
-- **Adaptive execution** - Maintains responsiveness under varying load
-
-
-## Core Principles
-
-| Principle | What it means |
-|-----------|---------------|
-| **Atomic Operations** | Each node does one thing perfectly |
-| **Pure Functions** | Predictable, testable, composable |
-| **Transparent Logic** | Understand every decision |
-| **Production Ready** | Built for high-throughput streaming with microsecond-scale latency |
-| **AI-Native Intelligence** | From statistical learning nodes to LLM reasoning - intelligence at every level |
-| **Built for Reality** | Node-level fault isolation, automatic recovery, and comprehensive observability |
-
-## What's Coming
-
-### 🎉 **Opening Our Doors in 2025**
-WinkComposer is transitioning to open source development in 2025. Join the [early conversation](https://github.com/winkjs/wink-composer/discussions) and help shape the future of composable streaming analytics. You can even reach out directly at wink@graype.in.
-
-**Together, we're building:**
-
-- **Rich Node Library**: Statistical, filtering, detection, transformation, and control nodes
-- **Edge-Ready Intelligence**: Advanced algorithms like smart correlation, change point detection, and regression inference - AI-like capabilities without heavyweight frameworks
-- **Pipeline Builder**: Define your analytics flows declaratively (visual tools planned)
-- **Edge-Ready Performance**: Process data efficiently, even on resource-constrained devices (**tested on Raspberry Pi**)
-- **Knowledge Graph Integration**: Build digital twins with Neo4j/ArangoDB for contextual intelligence
-- **AI-Native Reasoning**: When patterns emerge, LLMs explain why. When anomalies occur, get actionable recommendations. Open-source models keep intelligence at the edge.
-
-
-## The Vision
-
-Finally, build solutions that fit your exact problems, not the other way around.
-
-Every industry has unique patterns. Every process has specific physics. Every business has particular rules. WinkComposer gives you the building blocks to create exactly what you need.
-
-Domain-specific platforms excel at standard use cases. WinkComposer shines when you need something unique, beyond standard use cases. Standard use cases always included - they're just the beginning of what's possible!
-
-
-
-## About winkJS
-
-WinkComposer joins the winkJS family - production-grade open-source packages for Natural Language Processing, Machine Learning, and Statistical Analysis in JavaScript. Built for reliability with ~100% test coverage.
-
-
-## Copyright & License
-
-**Wink Composer** is copyright 2017-25 [GRAYPE Systems Private Limited](https://graype.in/).
-
-It is licensed under the terms of the MIT License.

package/docs/_coverpage.md

@@ -1,26 +0,0 @@
-
-![logo](_media/wink-logo.png)
-
-# wink-composer <small>♫</small>
-
-**Composable Streaming Intelligence**
-
-<br>
-
-> **🎯 Build exactly what you need, playfully simple**
-
-- ✨ **Real-time Analytics** that Sparks Joy
-- 💫 **Compose from Simple Nodes** — Countless Possibilities
-- 🔍 **Total Transparency** — Every Decision Explainable
-- ⚡ **Edge-Ready Performance** — Runs on Raspberry Pi!
-- 🧠 **Intelligent by Design** — Statistical Learning to LLMs
-- 🚀 **Production Resilient** — Fault isolation, recovery, & observability
-
-<br>
-
-> 🎉 **Transitioning to Open Source in 2025**
-
-
-
-[**Explore on GitHub** →](https://github.com/winkjs/wink-composer)
-[**Read the Docs** →](#docsify)

package/docs/_navbar.md

@@ -1,14 +0,0 @@
-
-* Getting started
-
-  * [Quick start](quickstart.md)
-  * [Writing more pages](more-pages.md)
-  * [Custom navbar](custom-navbar.md)
-  * [Cover page](cover.md)
-
-* Configuration
-  * [Configuration](configuration.md)
-  * [Themes](themes.md)
-  * [Using plugins](plugins.md)
-  * [Markdown configuration](markdown.md)
-  * [Language highlight](language-highlight.md)

package/docs/_sidebar.md

@@ -1,2 +0,0 @@
-* [Home](/)
-* [Contributing](CONTRIBUTING.md)

package/docs/index.html

@@ -1,44 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-  <meta charset="UTF-8">
-  <title>Document</title>
-  <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
-  <meta name="description" content="Composable Streaming Intelligence">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0">
-  <!-- <link rel="stylesheet" href="//cdn.jsdelivr.net/npm/docsify@4/lib/themes/vue.css"> -->
-  <!-- Theme: Simple (light + dark) -->
-  <link rel="stylesheet" media="(prefers-color-scheme: light)" href="https://cdn.jsdelivr.net/npm/docsify-themeable@0/dist/css/theme-simple.css">
-  <link rel="stylesheet" media="(prefers-color-scheme: dark)" href="https://cdn.jsdelivr.net/npm/docsify-themeable@0/dist/css/theme-simple-dark.css">
-
-  <style>
-    :root {
-      --theme-color: #886496;
-      --cover-background-color: #262626;
-      --cover-background-mask-opacity: 0.2;
-      --cover-background-image: none;
-      --cover-blockquote-color: #886496;
-    }
-  </style>
-
-</head>
-<body>
-  <div id="app"></div>
-  <script>
-    window.$docsify = {
-      name: 'wink-composer',
-      repo: 'https://github.com/winkjs/wink-composer',
-      loadSidebar: true,
-      coverpage: true,
-      search: 'auto',
-      loadNavbar: true
-    }
-  </script>
-  <!-- Docsify v4 -->
-  <script src="//cdn.jsdelivr.net/npm/docsify@4"></script>
-  <!-- docsify-themeable -->
-  <script src="https://cdn.jsdelivr.net/npm/docsify-themeable@0/dist/js/docsify-themeable.min.js"></script>
-  <script src="//cdn.jsdelivr.net/npm/docsify/lib/plugins/search.min.js"></script>
-
-</body>
-</html>