@lentystyle/core 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,13 @@
+# Changelog
+
+## 0.1.0 - 2026-05-28
+
+- CSS variables, class and pseudo selectors are now usable as variables.
+- Object and array variables are now available.
+- `@for`, `@if`, `elseif`, `else`, and `@fun` functions were added.
+- Improvements for `${}` expressions and calculations were added.
+- `@import` processing flow improvements.
+- Improvements for `?` dynamic and `?!` initial Observed selectors were added.
+- Debug, lazy, performance, worker, and map options for `data-luis` were added.
+- Security `guard` layer improvements were added.
+- Guard and browser runtime security checks are connected to a shared guard runtime adapter for URL, source, and script policy decisions.

package/CHANGELOG.tr.md

@@ -0,0 +1,13 @@
+# Değişiklik Geçmişi
+
+## 0.1.0 - 2026-05-28
+
+- CSS değişkenler, class ve pseudo seçiciler değişken olarka kullanılabiler duruma getirildi.
+- Obje ve array değişkenler kullanılabilir duruma getirildi.
+- `@for`, `@if`,`elseif`, `else`, `@fun` fonksiyonları eklendi.
+- `${...}` ifadeleri ve hesaplamalar için geliştirmeler eklendi.
+- `@import` işleme akışı geliştirmeleri.
+- `?` dynamic ve `?!` initial Observed seçiciler için geliştirmeler eklendi.
+- `data-luis` için debug, lazy, performance, worker, map seçenekleri eklendi.
+- Güvenlik için `guard` katmanı geliştirmeleri eklendi.
+- Guard  ve browser runtime güvenlik kontrolleri URL, kaynak ve script policy kararlarında ortak guard runtime adapterına bağlandı.

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,42 @@
+# LentyStyle Code of Conduct
+
+Thank you for taking the time to be part of the LentyStyle ecosystem. This document explains the communication and behavior rules expected in LentyStyle community spaces.
+
+---
+
+## Code of Conduct
+
+When communicating with each other or with the project team, and when contributing to the project, please follow these rules.
+
+The purpose of this community is to improve the application and solve problems. Communication should be respectful, honest, and constructive.
+
+- Do not use disrespectful, offensive, accusatory, or suggestive language about another person's religion, language, race, political views, country, opinions, color, age, gender, or physical characteristics. Avoid personal attacks and attacks against any group or community.
+- Use respectful and constructive language.
+- Be open to different opinions, perspectives, and experiences. Do not belittle ideas.
+- Community spaces should be used to improve the applications. Please do not use them for unrelated topics or personal conversations.
+- Keep technical discussions focused.
+- Do not share your own or anyone else's personal information.
+- Do not impersonate another person.
+- Do not use this community as a promotion space for unrelated products, services, or projects.
+
+Even when community members try to act in good faith, disagreements may happen. Not every disagreement is a rule violation. Please try to resolve issues constructively instead of escalating them.
+
+Community managers may not be able to monitor every message. If you notice something inappropriate, report it to the community managers instead of escalating the discussion.
+
+Unconstructive, aggressive, disrespectful, or inappropriate words and actions are not accepted. When needed, prefer apologizing or correcting the mistake.
+
+If these rules are not followed, or if inappropriate behavior continues, restrictions, temporary bans, or permanent bans may be applied.
+
+## Closed Source and Project Materials
+
+Some packages may be distributed as closed source or as compiled artifacts.
+
+In community spaces, it is not appropriate to request, share, redistribute, or disclose non-public source code, internal tools, private repository information, or unpublished technical details.
+
+For questions about licenses, usage scope, or source code access, please contact the project maintainers.
+
+---
+
+## Thank You
+
+Every contribution — large or small — helps strengthen the LentyStyle ecosystem.

package/CODE_OF_CONDUCT.tr.md

@@ -0,0 +1,41 @@
+# LentyStyle Davranış Kuralları
+
+LentyStyle ekosistemi için zaman ayırdığınız için teşekkürler. Bu belge, LentyStyle topluluk alanlarında beklenen iletişim ve davranış kurallarını açıklar.
+
+---
+
+## Davranış Kuralları
+
+Topluluk içinde birbiriniz ile veya bizimle iletişim kurarken, katkıda bulunmak istediğinizde aşağıdaki kurallara uymanızı önemle rica ediyoruz.
+Topluluğun amacı ve bir araya gelme sebebimiz var olan uygulamayı daha iyi hale getirmek, sorunları çözmek olmalı. Birbirimizle iletişim kurarken nazik ve dürüst davranalım.
+
+- İletişim kurarken karşınızdakinin din, dil, ırk, siyasi tercih, ülke, fikir, renk, yaş, cinsiyet, fiziksel özelliklerine yönelik herhangi bir saygısızlık/itham/ima edici dil kesinlikle kabul edilmeyecektir. Kişisel veya bir topluluğa/gruba karşı saldırılardan kaçının.
+- Birbirimize karşı saygılı ve yapıcı dil kullanalım.
+- Farklı görüşlere, bakış açılarına ve deneyimlere açık olun, fikirleri küçümsemeyin.
+- Buradaki topluluk alanları, uygulamaları geliştirmek amacıyla kullanılmalıdır. Uygulama dışındaki farklı konulardaki başlıklar, kişisel sohbetleriniz için lütfen burayı kullanmayın.
+- Teknik tartışmalarda odağı koruyun.
+- Kendinize veya başkasına ait herhangi bir kişisel bilgiyi burada paylaşmayın.
+- Kendi hesabınızdan başkası gibi davranmayın.
+- Bu topluluğu başka bir şeyin tanıtım alanı olarak kullanmayın.
+
+Topluluk üyeleri daha iyisi için ellerinden geleni yapsalar bile aralarında gerilimler/sorunlar yaşanabilir. Her anlaşmazlık kuralları ihlali anlamına gelmeyebilir. Sorunları, anlaşmazlıkları büyütmek yerine yapıcı olmaya özen gösterin.
+
+Topluluk yöneticileri her mesajı takip edemeyebilir. Uygun olmadığını düşündüğünüz durumları tartışmayı büyütmek yerine topluluk yöneticilerine iletin.
+
+Yapıcı olmayan, saldırgan, saygısız ve uygun olmayan her türlü söz/eylem kabul edilmeyecektir. Gerektiğinde özür dileme veya hatayı telafi etme yöntemini tercih edelim.
+
+Kurallara uyulmaması, kurallara uymayan eylemlere devam edilmesinde ısrar edilmesi kısıtlamalar, geçici veya kalıcı yasaklarla karşı karşıya kalmanıza sebep olabilir.
+
+## Kapalı Kaynak ve Proje Materyalleri
+
+Bazı paketler kapalı kaynak veya derlenmiş artifaktlar olarak dağıtılabilir.
+
+Topluluk alanlarında, kamuya açık olmayan kaynak kodun, iç araçların, özel repository bilgilerinin veya yayımlanmamış teknik detayların paylaşılması ya da talep edilmesi uygun değildir.
+
+Lisans, kullanım kapsamı veya kaynak kod erişimi ile ilgili sorular için proje yöneticileriyle iletişime geçebilirsiniz.
+
+---
+
+## Teşekkürler
+
+Her katkı — büyük ya da küçük — LentyStyle ekosistemini güçlendirir.

package/CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing to LentyStyle
+
+Thank you for taking the time to contribute to the LentyStyle ecosystem. This document explains how to contribute and what is expected.
+
+---
+
+## Source Code Access
+
+This package is currently distributed as closed source or as compiled artifacts. For this reason, direct source-level contributions are not accepted at this stage.
+
+You can still contribute by reporting bugs, sharing reproducible examples, suggesting improvements, improving documentation, reporting security issues through the appropriate private channel, and helping make the project more reliable and easier to use.
+
+For license details, see `LICENSE.md`.
+
+---
+
+## Opening Issues
+
+**For bug reports:**
+
+- Include the package and version you are using.
+- Share a minimal example that reproduces the issue.
+- Explain the expected behavior and the actual behavior.
+- Include your browser or Node.js version.
+- If you are able to share it, include a link to the project or page where the issue occurs.
+- Briefly explain how the issue appeared, if relevant.
+
+**For questions:**
+
+Use GitHub Discussions instead of opening an issue.
+
+---
+
+## Code of Conduct
+
+Everyone who contributes to this project is expected to follow the rules in `CODE_OF_CONDUCT.md`.
+
+Communication in the community should be respectful, constructive, and polite. If you notice inappropriate behavior, please report it to the project maintainers instead of escalating the discussion.
+
+---
+
+## Contact
+
+- **General questions:** GitHub Discussions
+- **Bug reports:** GitHub Issues
+- **License questions, collaboration, and partnerships:** hello@lentystyle.com
+- **Security reports and other issues:** support@lentystyle.com
+
+---
+
+## Thank You
+
+Every contribution — large or small — helps strengthen the LentyStyle ecosystem.

package/CONTRIBUTING.tr.md

@@ -0,0 +1,50 @@
+# LentyStyle'a Katkıda Bulunma
+
+LentyStyle ekosistemi için zaman ayırdığınız için teşekkürler. Bu belge katkı sürecini ve beklentileri açıklamaktadır.
+
+---
+## Kaynak Kod Erişimi
+
+Bu paket şu aşamada kapalı kaynak veya derlenmiş artifaktlar olarak dağıtılmaktadır. Bu nedenle doğrudan kaynak kod seviyesinde katkı kabul edilmemektedir.
+
+Yine de hata bildirimi, yeniden üretilebilir örnek, iyileştirme önerisi, dokümantasyon katkısı ve güvenlik bildirimi ile projeye katkıda bulunabilirsiniz.
+
+Lisans detayları için `LICENSE.TR.md` dosyasını inceleyebilirsiniz.
+
+---
+
+## Issue Açma Kuralları
+
+**Hata raporu için:**
+- Hangi paketi ve versiyonu kullandığınızı belirtin
+- Hatayı yeniden oluşturmak için minimum örnek paylaşın
+- Beklenen ve gerçekleşen davranışı açıklayın
+- Tarayıcı/Node.js versiyonunu ekleyin
+- Paylaşmanızda herhangi bir sakınca yoksa çalışmayı yaptığınız linki paylaşabilirsiniz.
+- Varsa durumun nasıl ortaya çıktığını kısaca açıklayın.
+
+**Soru sormak için:**
+Issue açmak yerine GitHub Discussions kullanın.
+
+---
+
+## Davranış Kuralları
+
+Bu projeye katkıda bulunan herkesin `CODE_OF_CONDUCT.TR.md` dosyasında belirtilen davranış kurallarına uyması beklenir.
+
+Topluluk içinde nazik, yapıcı ve saygılı iletişim esastır. Uygun olmadığını düşündüğünüz durumları tartışmayı büyütmeden proje yöneticilerine iletebilirsiniz.
+
+---
+
+## İletişim
+
+- **Genel sorular:** GitHub Discussions
+- **Bug raporları:** GitHub Issues
+- **Lisans soruları, işbirliği ve ortaklık:** hello@lentystyle.com
+- **Güvenlik, hata bildirimleri ve diğer konular:** support@lentystyle.com
+
+---
+
+## Teşekkürler
+
+Her katkı — büyük ya da küçük — LentyStyle ekosistemini güçlendirir.

package/LICENSE.md

@@ -0,0 +1,281 @@
+# Luis License 1.0 (EN)
+
+Copyright (c) 2025 LentyStyle. All rights reserved.
+
+---
+
+## 1. Purpose
+
+This software may be used as a software system, library, tool, engine, or software component that processes certain sources, definitions, configurations, files, or inputs and produces output.
+
+The purpose of this license is to:
+
+- allow developers to use this software freely in personal, commercial, and project-based use cases,
+- support the growth of the ecosystem around the software,
+- protect commercial use of the software at the platform, service, builder, white-label, and infrastructure level.
+
+This license is not an open source license. The source code of the Covered Software is not publicly available at this stage. The software may be distributed only through compiled artifacts, binary files, packaged outputs, or similar distribution files.
+
+---
+
+## 2. Covered Software
+
+This license applies to all software components that include this license file (the “Covered Software”).
+
+This license applies only to the version of the relevant software with which it is published and remains fixed for that version. Later versions may be published under different license terms.
+
+In this version, the Covered Software may be provided only as compiled artifacts, binary files, bundle files, type definition files, packaged distribution files, and similar outputs.
+
+Components that are not expressly covered by this license or that are published under a different license are outside the scope of this license.
+
+---
+
+## 3. Free Use
+
+The following use cases are free of charge.
+
+### ✓ Personal projects
+
+Use in hobby, learning, experimental, and open source projects is permitted.
+
+Publishing a project as open source does not remove the restrictions imposed by this license on platform, service, builder, editor, white-label, infrastructure, or commercial productization use cases.
+
+### ✓ Commercial projects
+
+Use is permitted in your own websites, web applications, internal tools, product interfaces, or individual projects developed for your clients.
+
+This permission does not grant the right to offer the Covered Software’s processing, compilation, runtime, server-side generation, pre-generated output, theme generation, or output generation capability to others as a service, platform, or product feature.
+
+### ✓ Agency and freelance work
+
+Developing websites, web applications, corporate sites, e-commerce sites, panels, or custom software for clients is permitted. Each client engagement is treated as a separate project.
+
+An agency or developer may use the Covered Software as its own development tool. However, it may not offer the Covered Software’s processing capability as a service to multiple clients or end users through a centralized infrastructure.
+
+### ✓ Self-hosted CMS, theme, and plugin use
+
+Use of the Covered Software in self-hosted CMS, theme, plugin, module, or similar distributions is free of charge; however, such use is limited to producing the relevant installation’s own content, own interface, or own theme.
+
+A commercial license is required in the following cases:
+
+- multiple users creating sites, stores, landing pages, application interfaces, or content pages through the same centralized infrastructure,
+- users processing, compiling, or converting their own sources, files, configurations, or inputs into output on your infrastructure,
+- offering the Covered Software as a hosting, site-builder, no-code, low-code, design tool, editor, export engine, or white-label service capability.
+
+### ✓ Desktop and mobile applications
+
+You may use the Covered Software in your own desktop and mobile applications developed with Electron, Tauri, WebView, or similar technologies to create your application’s own interface or functional output. Browser bundles, binary files, or compiled distribution files may be distributed inside the packaged application.
+
+This permission does not grant the right to offer the Covered Software’s source writing, editing, processing, compilation, preview, export, conversion, or output generation capability to end users as a product feature. Such builder, editor, design tool, code generator, design-to-code, or export products require a commercial license under Section 4.
+
+### ✓ Themes, UI kits, and templates
+
+Theme, UI kit, dashboard, component set, and template works that are sold as ready-made products to end users, where the Covered Software is only one of multiple tools, are free of charge. Sales through digital marketplaces are included in this scope.
+
+These products must not directly expose the Covered Software’s processing capability to end users. If the Covered Software’s runtime, compiler, server-side generation, pre-generated output, export, or processing flow becomes available to users, such use requires a commercial license under Section 4.
+
+### ✓ Custom integrations
+
+You may write custom build, server-side generation, pre-generated output, adapter, or integration code for your own project or for an individual client project.
+
+Public distribution of these integrations does not grant the right to repackage, hide, proxy, white-label, or offer as a service the Covered Software itself, its runtime components, compilation capabilities, or processing capabilities that require a commercial license.
+
+### ✓ Artificial intelligence and code assistants
+
+Generating code, source files, configurations, or output through artificial intelligence tools or code assistants, and running them in your own environment, is permitted. The fact that an artificial intelligence system knows or uses the syntax, format, or usage style of the Covered Software does not by itself create a restriction under this license.
+
+This permission does not grant the right to offer source generation, source conversion, output generation, theme generation, design-to-code, code export, or generation of output compatible with the Covered Software to others as a product, platform, service, plugin, or commercial feature.
+
+> Core principle: In these scenarios, the Covered Software is your development tool; it is not offered to end users as a separate processing, compilation, output generation, or platform capability.
+
+---
+
+## 4. Uses Requiring a Commercial License
+
+A commercial license is required in the following cases.
+
+### 4.1 Use as a Service
+
+The following uses require a commercial license:
+
+- tools where users upload source files, configurations, inputs, or content and receive output, manifests, server-side output, pre-generated artifacts, theme output, or any other output in return,
+- services that process user-owned sources through an API, web tool, CLI service, cloud job, worker, build service, or automated pipeline,
+- systems that offer the Covered Software’s compile, transform, runtime, server-side rendering, pre-rendering, snapshot, build-time generation, or similar processing capability to others as a service.
+
+Local or internal automated build processes used for your own project are not covered by this section.
+
+### 4.2 Platform, SaaS, and Site Builder Use
+
+The following uses require a commercial license:
+
+- SaaS, PaaS, site builder, no-code, or low-code platforms where users create their own sites, stores, landing pages, application interfaces, or content pages,
+- systems where the Covered Software runs in the background but is presented to end users as the platform’s own built-in style, theme, output, processing, or UI engine,
+- services that provide source compilation, runtime processing, server-side generation, pre-generated output, theme generation, or output for multiple clients or end users through centralized infrastructure,
+- marketing the Covered Software as another product’s own engine by hiding the Covered Software’s name, license, or technical presence.
+
+Individual client projects, agency work, self-hosted CMS installations, and uses made solely to create your own product’s interface or your own internal output are not covered by this section.
+
+### 4.3 Hosting and Automated Processing
+
+The following uses require a commercial license:
+
+- hosting users’ source files or project sources on your infrastructure,
+- automatically processing, compiling, or converting user-owned sources into output on your infrastructure,
+- producing source, output, manifests, server-side output, or pre-generated artifacts on your infrastructure from user-owned HTML, components, prompts, designs, content, configurations, or other inputs,
+- running server-side generation, pre-generated output, runtime processing, or security/guard operations through centralized infrastructure that serves multiple users.
+
+Automated compilation and processing workflows used for your own projects, internal tools, or individual client projects are not covered by this section.
+
+### 4.4 Design Tool, Builder, Editor, and Code Generation Products
+
+The following uses require a commercial license:
+
+- products where users generate source, output, manifests, server-side output, pre-generated artifacts, or theme output from designs, prompts, images, components, HTML, configurations, or any other source,
+- design tools, AI design-to-code products, no-code/low-code builders, output builders, theme editors, UI editors, code generation tools, and export tools,
+- systems that offer the Covered Software’s syntax, format, or compilation/runtime capability as the product’s output format, export option, theme engine, styling infrastructure, processing engine, or code generation target,
+- commercial tools that allow users to write, edit, compile, process, preview, export, or generate output from sources.
+
+This restriction applies regardless of whether the tool is offered as a web, desktop, mobile, plugin, API, CLI, agent, or automation product.
+
+Using artificial intelligence or a code assistant in your own project to generate code, source files, or configurations is not covered by this section. The restriction applies when this capability is offered to others as a product, platform, service, or commercial feature.
+
+### 4.5 Platform-Level UI or Output Systems
+
+The following uses require a commercial license:
+
+- UI, theme, style, output, or content generation systems that depend on the Covered Software’s runtime, compiler, server-side generation, or pre-generated output and serve multiple users,
+- dynamic UI engines, output engines, or theme generation systems used inside SaaS, PaaS, hosted CMS, site builder, or similar platforms,
+- theme, style, layout, content, output, or UI generation systems built on top of the Covered Software and offered to multiple users, clients, or tenants.
+
+Using the Covered Software in your own product’s fixed or internal interface, or in your own internal output generation process, is not covered by this section.
+
+### 4.6 White-label, Rebranding, and Competing Engine Use
+
+The following uses require a commercial license or are prohibited without written permission:
+
+- repackaging the Covered Software under a different name, brand, or product,
+- presenting the Covered Software as a product’s own internally developed style engine, theme engine, compiler, runtime, processing engine, output engine, or UI engine,
+- hiding the Covered Software’s name, license, or technical presence from end users,
+- using the outputs, APIs, runtime components, or distribution files of the covered packages to develop a competing compiler, runtime, styling engine, processing engine, output engine, or compatible alternative engine,
+- developing commercial products that generate output compatible with the Covered Software, aim to replace the Covered Software, or substitute the Covered Software’s ecosystem.
+
+Individual projects, agency projects, self-hosted uses, or ready-made theme/template distributions that clearly disclose the use of the Covered Software are not considered within this section. However, the commercial license requirements in Section 4 continue to apply to platform, SaaS, builder, service, multi-user system, or productized export/engine uses.
+
+---
+
+## 5. Core Principle
+
+> If you use the Covered Software in your own project: free of charge.
+>
+> If you develop an individual project for your client: free of charge.
+>
+> If you create and sell a theme, UI kit, or template and do not offer the Covered Software’s processing capability as a service: free of charge.
+>
+> If you offer the Covered Software’s processing capability to others as an engine, builder, SaaS, export format, compiler, runtime, server-side rendering, pre-rendering, theme engine, processing engine, or platform infrastructure: a commercial license is required.
+>
+> If you market the Covered Software as an engine developed by your own product: written permission or a commercial license is required.
+
+If you are unsure whether your use case requires a commercial license, permission or commercial license terms should be clarified through the software owner’s official communication channels.
+
+---
+
+## 6. Usage Examples (For Information Only)
+
+This section is not an interpretation of the license text. It is included to clarify common scenarios.
+
+### Examples of permitted free use
+
+✓ Developing your own e-commerce site with the Covered Software.
+
+✓ Building a corporate website for a client.
+
+✓ Developing a product’s own interface with the Covered Software.
+
+✓ Producing only the relevant site’s theme or interface inside a self-hosted CMS installation.
+
+✓ Preparing a dashboard theme that includes source files and selling it on a digital marketplace; the buyer uses the theme in their own project, and you do not offer the Covered Software’s processing capability as a service.
+
+✓ Using the Covered Software in your desktop or mobile application’s own interface.
+
+✓ Generating code, source files, or configurations with artificial intelligence or a code assistant and running them in your own environment.
+
+✓ Writing custom build, server-side generation, pre-generated output, or adapter integration for your own project.
+
+### Examples requiring a commercial license
+
+✗ Creating a web tool, API, or service where users upload source files and receive output, manifests, server-side output, or pre-generated artifacts.
+
+✗ Running the Covered Software in the background inside a platform where users create their own sites, stores, landing pages, or application interfaces.
+
+✗ Developing a product where users receive source, output, or theme output from designs, prompts, components, or images.
+
+✗ Developing a commercial builder, editor, design tool, code generation tool, or plugin that lets users write, edit, compile, preview, or export sources.
+
+✗ Hosting users’ source files on your infrastructure and automatically running server-side generation, pre-generated output, runtime processing, or compilation.
+
+✗ Packaging the Covered Software under another name and presenting it as your own compiler, runtime, theme engine, processing engine, output engine, or UI engine.
+
+---
+
+## 7. Restrictions
+
+The following are prohibited:
+
+- modifying the source code of the covered packages, decompiling, reverse engineering, or attempting to reconstruct them,
+- using the Covered Software’s compiled outputs, binary files, bundle files, type definition files, runtime components, public APIs, or distributed packages to create another processing, compilation, runtime, styling engine, output engine, or compatible alternative system,
+- removing or modifying copyright notices, license files, or attribution metadata,
+- transferring or sublicensing the rights granted under this license to any third party,
+- using the name, logo, or trademarks of the Covered Software without written permission in a way that implies endorsement of your product or service,
+- using the Covered Software for any use requiring a commercial license under Section 4 without obtaining a written commercial license.
+
+---
+
+## 8. Redistribution
+
+You may redistribute compiled artifacts, binary files, bundle files, type definition files, packaged distribution files, and similar outputs as part of your own product or package, provided that:
+
+- this license file is included without modification,
+- the redistribution does not constitute a platform, service, builder, white-label, competing engine, or other use requiring a commercial license as defined in Section 4,
+- the files are not modified, hidden, renamed and presented as a different engine, or packaged in a way that conceals the technical presence of the Covered Software.
+
+Redistribution does not create any right to sublicense the Covered Software. End users may use the Covered Software only under the terms of this license.
+
+---
+
+## 9. Source Code Release and Open Luis License
+
+At the initial stage, the Covered Software may be published only as compiled artifacts, binary files, bundle files, type definition files, packaged distribution files, and similar outputs.
+
+The software owner will make the source code of the Covered Software publicly available under the Open Luis License no later than 2 years after the first public release date. This date may only be moved earlier; it may not be delayed. A delay is permitted only due to legal, security, or infrastructure requirements outside the reasonable control of the software owner.
+
+The Open Luis License may allow inspection of the source code, use for learning purposes, contribution, and use within the scope permitted by that license.
+
+Making the source code available does not automatically remove the Covered Software’s restrictions on platform, SaaS, builder, editor, design tool, code generator, white-label, hosted service, export engine, competing engine, or multi-user use. Such uses may still require a separate commercial license under the Open Luis License.
+
+A transition to MIT, Apache-2.0, or similar unrestricted open source licenses applies only to software components and versions that are expressly published under those licenses by the software owner.
+
+Some helper components, tools, editor integrations, documentation parts, or independent modules may be published under different licenses. Those components are governed by their own license terms and are outside the scope of this license.
+
+---
+
+## 10. No Warranty
+
+This software is provided “as is”, without any express or implied warranty, including but not limited to warranties of merchantability, fitness for a particular purpose, or non-infringement.
+
+In no event shall the author or copyright holders be liable for any claim, damages, or other liability arising from the software or the use of the software, whether in contract, tort, or otherwise.
+
+The user acknowledges that they use this software based on their own risk assessment. The software owner does not warrant that the software will be secure, uninterrupted, or error-free.
+
+---
+
+## 11. Termination
+
+If you violate any term of this license, your rights automatically terminate. Upon termination, you must immediately stop using and distributing the Covered Software.
+
+Termination does not waive or limit the software owner’s other rights arising from the violation, commercial license claims, or legal remedies.
+
+---
+
+## 12. Contact
+
+For commercial license requests, partnership programs, or questions about permitted use, the software owner’s official communication channels should be used.