@romanilyin/canonicalpath 2026.5.18-2

package/LICENSE.md

@@ -0,0 +1,331 @@
+# Stinger Royalty-Free EULA 1.0 — English convenience translation
+
+**SPDX-License-Identifier:** `LicenseRef-Stinger-Royalty-Free-EULA-1.0`  
+**License version:** 1.0  
+**Effective date:** 2026-05-14  
+**Licensor:** ROMAN ILYIN  
+**Canonical licensor repository namespace:** `https://github.com/romanilyin/*`  
+**Copyright:** Copyright © 2026 ROMAN ILYIN. All rights reserved except as expressly granted in this EULA.
+
+**Language priority:** the Russian-language text of `Stinger Royalty-Free EULA 1.0` is the primary and controlling version. This English text is provided only as a convenience translation. If the Russian and English versions conflict, differ, or are interpreted differently, the Russian version controls.
+
+## Non-binding summary
+
+This summary is provided for convenience only. It is not a substitute for the full terms below.
+
+You may use, copy, modify, and include the Asset in personal, internal, open, or commercial End Products, royalty-free. You may sell, license, publish, distribute, provide access to, and otherwise monetize End Products that use the Asset. You may create and distribute MCP Extensions and MCP Command Sets for your own assets, tools, games, applications, services, workflows, asset packages, client deliverables, and internal pipelines, including commercial End Products, when they are not standalone resale, standalone commercialization, or competing repackaging of the Asset. You must preserve attribution and the Canonical Repository notice. You may not sell, resell, sublicense, rent, lease, monetize, or otherwise commercially exploit the Asset or any Derivative Asset as a standalone asset, package, plugin, library, SDK, template, tool, module, gateway, MCP gateway, MCP module, command pack, extension framework, source package, binary package, or substantially similar product. The Asset is provided as-is, without warranty, support obligation, indemnity, or liability to the maximum extent permitted by law.
+
+This EULA is intended to be source-available and royalty-free for End Products. It is not intended to be an OSI-approved open source license because it restricts standalone resale and standalone commercialization of the Asset and Derivative Assets.
+
+## 1. Agreement and acceptance
+
+1.1. This Stinger Royalty-Free EULA 1.0 (the “EULA”) is a legal agreement between ROMAN ILYIN (the “Licensor”) and any person or entity that downloads, installs, copies, accesses, modifies, distributes, integrates, embeds, publishes, sells, provides access to, or otherwise uses the Asset (“you” or “Licensee”).
+
+1.2. By downloading, installing, copying, accessing, modifying, distributing, integrating, embedding, publishing, selling, providing access to, or otherwise using the Asset, you accept this EULA. If you do not accept this EULA, you must not use the Asset.
+
+1.3. The Asset is licensed, not sold. The Licensor retains all rights, title, and interest in and to the Asset except for the rights expressly granted in this EULA.
+
+1.4. All rights not expressly granted in this EULA are reserved by the Licensor.
+
+1.5. This EULA applies to the Asset identified as licensed under this EULA in the applicable Project Notice, repository metadata, package metadata, README, NOTICE file, LICENSE file, or other accompanying notice.
+
+## 2. Definitions
+
+2.1. “Asset” or “Licensed Material” means the software, source code, object code, binaries, scripts, packages, Unity packages, editor tools, runtime tools, libraries, modules, MCP gateway components, MCP modules, MCP command definitions, MCP resources, MCP prompts, schemas, adapters, manifests, configuration files, documentation, samples, examples, templates, media, and other materials distributed by the Licensor under this EULA and identified in the applicable Project Notice.
+
+2.2. “Project Notice” means the NOTICE file, README, package metadata, repository metadata, source header, or other accompanying notice that identifies the Project name, Canonical Repository, attribution text, and copyright notice for a specific Asset.
+
+2.3. “Project” means the Asset identified in the applicable Project Notice.
+
+2.4. “Canonical Repository” means the original repository or canonical source location identified by the Licensor in the applicable Project Notice. If no more specific Canonical Repository is provided, the Canonical Repository is the official Licensor-controlled repository from which the Asset was distributed under `https://github.com/romanilyin/*`.
+
+2.5. “End Product” means a game, application, digital media work, software product, asset package, content package, tool, service, workflow, client deliverable, internal toolchain, build pipeline, or other product that:
+
+(a) contains substantial original content, code, functionality, workflow, creative expression, or commercial value beyond the Asset;
+
+(b) uses the Asset only as an integrated, embedded, bundled, referenced, or supporting component;
+
+(c) has a primary purpose, function, and value that is not the standalone use, display, distribution, resale, replacement, or commercialization of the Asset or a Derivative Asset; and
+
+(d) does not make the Asset or a Derivative Asset available to recipients as a separately usable standalone asset, package, plugin, library, SDK, template, tool, module, gateway, MCP gateway, MCP module, command pack, extension framework, source package, binary package, or substantially similar product, except as expressly allowed by this EULA.
+
+2.6. A software library, SDK, plugin, Unity package, MCP extension, developer tool, editor tool, asset package, or content package can be an End Product only if it provides substantial original functionality or content and the Asset is not the primary source of its value.
+
+2.7. A third-party asset package can be an End Product when it consists primarily of your own original asset, content, code, tool, workflow, or functionality, and the Asset or an MCP Extension is included only to support, automate, integrate, document, control, configure, or improve that third-party asset package.
+
+2.8. “Derivative Asset” means any modification, adaptation, translation, port, fork, wrapper, repackaging, renamed version, reformatted version, converted version, extended version, compiled version, source-available version, binary version, or other derivative work based on the Asset, excluding an End Product that satisfies Section 2.5.
+
+2.9. “Standalone Asset Distribution” means distributing, publishing, uploading, selling, licensing, sublicensing, renting, leasing, lending, making available, or otherwise providing the Asset or a Derivative Asset separately from an End Product, or in a form where the Asset or Derivative Asset is the main item being obtained.
+
+2.10. “Standalone Commercialization” means any sale, resale, paid licensing, sublicensing, paid download, paid access, paid subscription, marketplace listing for a fee, commercial hosting, paid support plan, paid service, advertising-funded distribution, bundling for commercial consideration, or other monetization where the primary commercial value is access to, use of, support for, or distribution of the Asset or a Derivative Asset as such.
+
+2.11. “Marketplace” means any marketplace, store, package registry, source marketplace, asset marketplace, plugin marketplace, template marketplace, SDK marketplace, extension marketplace, model/tool registry, package index, or similar service, including but not limited to the Unity Asset Store, Unreal Marketplace/Fab, OpenUPM, npm, NuGet, PyPI, GitHub Releases, GitHub Marketplace, Gumroad, itch.io, or similar platforms.
+
+2.12. “MCP” means the Model Context Protocol or any compatible protocol, runtime, gateway, command interface, or automation interface used to expose tools, commands, prompts, resources, schemas, adapters, or workflows to an AI assistant, developer tool, editor, game engine, or automation system.
+
+2.13. “MCP Extension” means an extension, module, adapter, integration, command pack, manifest, schema package, prompt package, handler, bridge, tool definition, resource definition, configuration, or similar component that interoperates with MCP or with the Asset’s MCP gateway, MCP modules, MCP APIs, or MCP extension points.
+
+2.14. “MCP Command Set” means a set of MCP commands, prompts, resources, schemas, metadata, handlers, mappings, or configuration intended to operate with MCP, an MCP Extension, the Asset, or the Stinger MCP Gateway.
+
+2.15. “Embedded” means included in, bundled with, referenced by, required by, integrated into, or otherwise used as part of an End Product in a manner consistent with the End Product’s purpose. Embedded use may include source code, scripts, package manifests, command definitions, schemas, configuration files, or binary files when reasonably necessary for the End Product to build, run, interoperate, be maintained, or be distributed. Embedded use does not permit Standalone Asset Distribution or Standalone Commercialization.
+
+2.16. “Attribution Notice” means the notice required by Section 8 and specified in the applicable Project Notice.
+
+## 3. License grant
+
+3.1. Subject to your compliance with this EULA, the Licensor grants you a worldwide, non-exclusive, royalty-free, revocable only upon breach, copyright license to:
+
+(a) download, install, access, and use the Asset;
+
+(b) copy the Asset for development, evaluation, backup, archival, testing, build, continuous integration, deployment, and internal operational purposes;
+
+(c) modify, adapt, translate, port, extend, and create Derivative Assets;
+
+(d) integrate and Embed the Asset or Derivative Assets into End Products;
+
+(e) distribute the Asset or Derivative Assets only as Embedded components of End Products, subject to this EULA;
+
+(f) sell, license, publish, distribute, provide access to, and otherwise monetize End Products that use the Asset or Derivative Assets, without paying royalties to the Licensor;
+
+(g) permit your employees, contractors, consultants, agents, affiliates, build systems, and service providers to use the Asset solely on your behalf and solely for activities permitted by this EULA; and
+
+(h) permit end users of your End Product to use the Embedded Asset solely as part of the End Product and not separately.
+
+3.2. The license granted in Section 3.1 does not grant any ownership rights in the Asset. You own your original code, content, assets, command logic, project files, products, outputs, and modifications, subject to the Licensor’s retained rights in the Asset and any copied or derivative portions of the Asset.
+
+3.3. You may license your End Product under your own terms, including commercial or proprietary terms, provided that your terms do not grant recipients any rights to the Asset or any Derivative Asset beyond the rights granted by this EULA.
+
+3.4. You may provide paid professional services, consulting, integration, customization, training, or support for End Products that use the Asset, provided that you do not use those services to conduct Standalone Commercialization of the Asset or a Derivative Asset.
+
+## 4. Commercial End Products
+
+4.1. You may use the Asset in commercial End Products without paying royalties, revenue share, subscription fees, seat fees, usage fees, or other compensation to the Licensor.
+
+4.2. Commercial End Products may include games, applications, Unity projects, Unity asset packages, developer tools, editor tools, internal pipelines, build systems, client deliverables, SaaS products, services, SDKs, plugins, content packages, and MCP-enabled workflows, provided that they satisfy the definition of End Product in Section 2.5.
+
+4.3. The fact that an End Product is sold, licensed, monetized, used in commerce, used internally by a company, delivered to a client, or distributed through a Marketplace does not by itself violate this EULA.
+
+4.4. The restriction is not against commercial use. The restriction is against Standalone Asset Distribution and Standalone Commercialization of the Asset or a Derivative Asset.
+
+## 5. MCP Extension and MCP Command Set permission
+
+5.1. Subject to your compliance with this EULA, you may create, use, copy, modify, distribute, sell, license, publish, and monetize MCP Extensions and MCP Command Sets as part of End Products, including commercial End Products.
+
+5.2. You may create MCP Extensions and MCP Command Sets for your own assets, games, applications, tools, services, workflows, asset packages, content packages, client deliverables, and internal pipelines, and you may use them with the Asset, with the Stinger MCP Gateway, or with a compatible MCP gateway.
+
+5.3. You may include an MCP Extension or MCP Command Set in a third-party asset package or other End Product when the extension or command set primarily supports, automates, controls, configures, documents, integrates, validates, tests, or improves your own original asset, tool, workflow, service, or product.
+
+5.4. Examples of permitted MCP-related use include:
+
+(a) building a custom MCP Command Set for your own Unity asset and including it in that asset package so users can operate your asset through the Stinger MCP Gateway;
+
+(b) selling a Unity asset package that contains your own substantial original asset and includes a Stinger-compatible MCP Extension only to automate, configure, test, validate, or control that asset;
+
+(c) including MCP commands in a commercial game-development workflow, build pipeline, editor tool, internal toolchain, or client deliverable;
+
+(d) writing your own MCP adapter that interoperates with the Asset, provided that the adapter is not a disguised repackaging, replacement, fork, or standalone commercialization of the Asset; and
+
+(e) distributing an End Product that includes command definitions, schemas, handlers, or configuration files reasonably necessary to operate the End Product through MCP.
+
+5.5. MCP compatibility alone does not make your own original MCP Extension, MCP Command Set, asset, tool, service, or product a Derivative Asset. Portions that copy, include, adapt, or derive from the Asset remain subject to this EULA.
+
+5.6. You may not sell, resell, license, sublicense, rent, lease, publish, distribute for commercial consideration, provide paid access to, monetize, or otherwise commercially exploit a modified Stinger MCP Gateway, Stinger MCP module, Stinger MCP command-pack infrastructure, or Derivative Asset as a standalone paid package, standalone paid command pack, standalone paid MCP gateway, standalone paid MCP module, standalone paid extension framework, or competing product.
+
+5.7. You may not use an MCP Extension, MCP Command Set, or compatibility layer to avoid the restrictions of this EULA. Changing command names, schemas, manifests, UI labels, namespaces, package layout, or adding thin wrappers or minor features does not turn a Derivative Asset into an End Product.
+
+## 6. Free standalone forks and non-commercial redistribution
+
+6.1. You may distribute the Asset or a Derivative Asset as a standalone public or private fork only if all of the following conditions are met:
+
+(a) the distribution is free of charge;
+
+(b) the distribution is not used for Standalone Commercialization;
+
+(c) the distribution does not require payment, subscription, paid account, paid membership, paid support plan, paid access, advertising interaction, commercial bundle purchase, or other commercial consideration to access, download, use, modify, or redistribute;
+
+(d) all copyright, license, attribution, trademark, proprietary, disclaimer, and Canonical Repository notices are retained;
+
+(e) the Attribution Notice and Canonical Repository are included in a reasonably prominent location such as README, LICENSE, NOTICE, package metadata, documentation, or an equivalent location;
+
+(f) modified versions are clearly marked as modified, unofficial, and not endorsed, sponsored, approved, certified, maintained, or supported by the Licensor;
+
+(g) the distribution does not use the Licensor’s names, logos, project names, trademarks, service marks, or branding except for attribution and truthful compatibility statements; and
+
+(h) the distribution does not violate any other restriction in this EULA.
+
+6.2. Voluntary donations are allowed only if they are not required for access, licensing, features, downloads, source access, binary access, support, updates, or distribution of the Asset or Derivative Asset, and only if they do not imply Licensor endorsement.
+
+6.3. You may maintain private internal forks, private mirrors, and private modifications for your own development, CI, backup, archival, security, or operational purposes, including within your organization or with contractors working on your behalf, provided that all users remain bound by this EULA.
+
+## 7. Restrictions
+
+7.1. You may not sell, resell, license, sublicense, rent, lease, lend, publish, distribute for commercial consideration, provide paid access to, monetize, or otherwise commercially exploit the Asset or any Derivative Asset as a standalone asset, package, plugin, library, SDK, template, tool, module, gateway, MCP gateway, MCP module, command pack, extension framework, source package, binary package, or substantially similar product.
+
+7.2. You may not upload, list, publish, or distribute the Asset or any Derivative Asset on a Marketplace as a paid product, paid package, paid extension, paid asset, paid template, paid SDK, paid tool, paid module, paid command pack, paid gateway, or paid source/binary package.
+
+7.3. You may not create or distribute a product whose primary purpose or value is to provide substantially the same functionality, files, commands, API, module structure, package structure, source, binary, user interface, documentation, examples, or developer-facing value as the Asset, unless the product is distributed for free in compliance with Section 6.
+
+7.4. You may not use minor changes to avoid this EULA. Changing names, namespaces, package names, file layout, package metadata, build format, UI styling, comments, documentation, command labels, command schemas, manifests, or adding thin wrappers or minor features does not make a Derivative Asset into an End Product.
+
+7.5. You may not remove, obscure, or alter any copyright notice, license notice, Attribution Notice, Canonical Repository notice, trademark notice, proprietary notice, or disclaimer included with the Asset.
+
+7.6. You may not state or imply that the Licensor endorses, sponsors, approves, certifies, maintains, supports, or is affiliated with your product, fork, MCP Extension, MCP Command Set, service, marketplace listing, company, repository, or project, unless the Licensor has expressly authorized it in writing.
+
+7.7. You may not use the Licensor’s names, logos, project names, repository names, trademarks, service marks, or branding except as required for attribution or as reasonably necessary for truthful compatibility statements.
+
+7.8. You may not apply a different license to the Asset or any Derivative Asset that permits Standalone Commercialization or removes the attribution, notice, warranty, liability, support, termination, dispute, or reserved-rights provisions of this EULA.
+
+7.9. You may not describe the Asset or any Derivative Asset as MIT-licensed, Apache-licensed, public domain, OSI-approved open source, or otherwise licensed under terms that permit Standalone Commercialization, unless the Licensor has separately released that specific material under those terms.
+
+7.10. You may not use the Asset in violation of applicable law, regulation, export control, sanctions rule, court order, third-party right, or platform rule.
+
+7.11. You may not use the Asset in life-critical, safety-critical, medical, aviation, nuclear, emergency-response, weapons-control, autonomous-vehicle-control, or other high-risk systems where failure of the Asset could reasonably lead to death, personal injury, severe property damage, or severe environmental damage, unless you independently validate the Asset for that use and assume all resulting risk and liability.
+
+## 8. Attribution and notice requirements
+
+8.1. Any distribution of the Asset, a Derivative Asset, or an End Product containing the Asset must retain the applicable copyright notices, license notices, disclaimers, Canonical Repository notice, and Attribution Notice.
+
+8.2. For developer-facing distributions, including source distributions, repositories, packages, Unity packages, UPM packages, MCP Extensions, MCP Command Sets, SDKs, tools, templates, asset packages, content packages, and plugin packages, the Attribution Notice must be included in a reasonably prominent location such as README, LICENSE, NOTICE, THIRD_PARTY_NOTICES, package metadata, documentation, or an equivalent location.
+
+8.3. For compiled, embedded, runtime-only, or end-user-facing End Products, the Attribution Notice may be included in documentation, credits, acknowledgements, an about screen, a license screen, third-party notices, package metadata, or another location where third-party notices are customarily placed. This EULA does not require a splash screen, main-menu credit, advertising placement, or prominent UI notice unless your End Product already has a customary place for third-party notices.
+
+8.4. The required Attribution Notice is the notice specified in the applicable Project Notice. If the Project Notice is missing or incomplete, the Asset must not be distributed in developer-facing form until a Project Notice is added that identifies the Project name, Canonical Repository, copyright notice, and required attribution text.
+
+8.5. Modified standalone forks, free forks, and Derivative Assets must also include:
+
+```text
+This is an unofficial modified version. It is not endorsed, sponsored,
+approved, certified, maintained, or supported by ROMAN ILYIN.
+```
+
+8.6. If the Asset includes a NOTICE file, you must retain it. You may add your own notices for your own original work, but you may not remove or obscure the Licensor’s notices.
+
+8.7. If practical, package metadata and source headers should identify this EULA using:
+
+```text
+LicenseRef-Stinger-Royalty-Free-EULA-1.0
+```
+
+## 9. End-user rights in End Products
+
+9.1. You may distribute End Products under your own end-user license, terms of service, commercial agreement, or marketplace terms.
+
+9.2. Your end users may use the Embedded Asset only as part of the End Product. They do not receive any right from you to extract, copy, modify, publish, sell, resell, redistribute, sublicense, rent, lease, lend, monetize, or otherwise use the Asset or a Derivative Asset separately from the End Product.
+
+9.3. You must not grant your end users rights to the Asset that exceed the rights granted by this EULA.
+
+9.4. You are solely responsible for your End Product, your distribution, your customers, your support promises, your warranties, your compliance obligations, your data practices, your marketplace obligations, and your commercial activities.
+
+## 10. Outputs and generated materials
+
+10.1. Subject to this EULA, the Licensor claims no ownership in your End Products, your original assets, your original code, your original command logic, your original MCP Command Sets, your original MCP Extensions, your content, your project files, your services, your workflows, your outputs, or your client deliverables merely because they were created using, integrated with, or operated through the Asset.
+
+10.2. Logs, reports, metrics, generated files, command outputs, build outputs, configuration outputs, analysis outputs, and other outputs generated by use of the Asset belong to you, unless and only to the extent they contain copied portions of the Asset or third-party material.
+
+10.3. Portions of MCP Extensions, MCP Command Sets, generated files, templates, or outputs that copy, include, adapt, or derive from the Asset remain subject to this EULA.
+
+## 11. Third-party materials and other licenses
+
+11.1. Some files, dependencies, examples, libraries, packages, tools, or components included with or used by the Asset may be governed by separate third-party licenses.
+
+11.2. This EULA does not override third-party license terms. If there is a conflict between this EULA and a third-party license, the third-party license controls only for the third-party material to which it applies.
+
+11.3. Material that the Licensor has expressly released under another license is governed by that other license for that material only. This EULA does not revoke rights already granted by a separate license for separate material or earlier versions.
+
+11.4. You are responsible for complying with all applicable third-party licenses, platform terms, marketplace terms, and dependency licenses in your End Products and distributions.
+
+## 12. Patents
+
+12.1. Subject to your compliance with this EULA, the Licensor grants you a non-exclusive, worldwide, royalty-free patent license under patent claims owned or controlled by the Licensor that are necessarily infringed by using the Asset as provided by the Licensor, solely to the extent necessary to exercise the rights granted by this EULA.
+
+12.2. If you initiate a patent claim alleging that the Asset, or use of the Asset as permitted by this EULA, infringes a patent, then any patent license granted to you under this EULA terminates as of the date the claim is filed.
+
+12.3. No patent license is granted for your modifications, combinations, End Products, third-party materials, or uses outside the scope of this EULA.
+
+## 13. No support, maintenance, updates, or availability obligation
+
+13.1. The Licensor has no obligation to provide support, maintenance, updates, upgrades, bug fixes, security fixes, compatibility fixes, documentation, training, hosting, distribution, or continued availability for the Asset.
+
+13.2. Any support, maintenance, update, or other service provided by the Licensor is provided at the Licensor’s sole discretion and does not create any ongoing obligation unless stated in a separate written agreement signed by the Licensor.
+
+13.3. The Licensor may change, suspend, remove, archive, make private, discontinue, or stop distributing any repository, release, binary, package, branch, tag, documentation, support channel, or service at any time.
+
+## 14. Disclaimer of warranties
+
+14.1. To the maximum extent permitted by applicable law, the Asset is provided “as is,” “as available,” and “with all faults,” without warranties, representations, guarantees, or conditions of any kind, whether express, implied, statutory, or otherwise.
+
+14.2. The Licensor specifically disclaims all warranties, representations, guarantees, and conditions, including but not limited to merchantability, fitness for a particular purpose, title, non-infringement, accuracy, completeness, availability, compatibility, performance, security, error-free operation, uninterrupted operation, absence of harmful components, and suitability for production, commercial, regulated, safety-critical, or high-risk use.
+
+14.3. You are solely responsible for evaluating, testing, validating, securing, configuring, integrating, deploying, maintaining, and using the Asset and any End Product.
+
+## 15. Limitation of liability
+
+15.1. To the maximum extent permitted by applicable law, the Licensor will not be liable to you or any third party for any direct, indirect, incidental, special, consequential, exemplary, punitive, enhanced, reliance, cover, lost-profit, lost-revenue, lost-savings, lost-data, lost-goodwill, business-interruption, procurement-of-substitute-goods-or-services, security, privacy, compliance, regulatory, reputational, or other damages, losses, costs, expenses, penalties, claims, or liabilities arising from or relating to the Asset, this EULA, any End Product, or any use or inability to use the Asset, even if advised of the possibility of such damages and even if any remedy fails of its essential purpose.
+
+15.2. To the maximum extent permitted by applicable law, the Licensor will not be liable for any claim arising from or relating to your modifications, integrations, distributions, commercial activities, customer relationships, warranties, representations, support promises, marketplace listings, professional services, security practices, data practices, or End Products.
+
+15.3. If liability cannot be fully excluded, the Licensor’s total liability will be limited to the minimum amount permitted by applicable law.
+
+## 16. No indemnity by Licensor; Licensee responsibility
+
+16.1. The Licensor does not provide any indemnity, defense obligation, hold-harmless obligation, reimbursement obligation, or insurance coverage for the Asset, this EULA, your use of the Asset, or your End Product.
+
+16.2. You are solely responsible for any claims, damages, losses, liabilities, costs, expenses, settlements, penalties, customer disputes, platform disputes, marketplace disputes, and legal obligations arising from or relating to your End Product, your distribution, your commercial activities, your modifications, your misuse of the Asset, or your breach of this EULA.
+
+16.3. To the maximum extent permitted by applicable law, you agree to defend, indemnify, and hold harmless the Licensor from and against third-party claims arising from your End Product, your distribution, your commercial activities, your modifications, your misuse of the Asset, or your breach of this EULA.
+
+## 17. Termination
+
+17.1. The rights granted under this EULA terminate automatically if you breach this EULA.
+
+17.2. Upon termination, you must stop using, copying, modifying, distributing, publishing, selling, licensing, providing access to, and otherwise exploiting the Asset and any Derivative Asset, except as otherwise expressly permitted in writing by the Licensor.
+
+17.3. Termination does not require prior notice, but the Licensor may provide notice at the Licensor’s discretion.
+
+17.4. The Licensor may reinstate your rights if you cure the breach and the Licensor expressly agrees to reinstatement in writing.
+
+17.5. Sections that by their nature should survive termination survive termination, including ownership, restrictions, attribution, third-party materials, disclaimer of warranties, limitation of liability, no indemnity by Licensor, Licensee responsibility, dispute provisions, and miscellaneous provisions.
+
+17.6. Termination of your rights does not automatically terminate rights validly granted to end users of compliant End Products distributed before termination, provided that those end users continue to use the Embedded Asset only as part of those compliant End Products and not separately.
+
+## 18. Disputes and Licensor-selected forum
+
+18.1. To the maximum extent permitted by applicable law, any dispute, claim, action, proceeding, enforcement action, or controversy arising from or relating to this EULA, the Asset, a Derivative Asset, an End Product, or any use or distribution of the Asset will be governed by the law, jurisdiction, venue, forum, and procedural method selected by the Licensor in the Licensor’s sole discretion at the time the dispute, claim, action, proceeding, enforcement action, or controversy arises or is filed.
+
+18.2. To the maximum extent permitted by applicable law, you consent to the Licensor’s selected law, jurisdiction, venue, forum, and procedural method, and you waive any objection based on inconvenience, lack of connection, conflict of laws, or similar grounds.
+
+18.3. Nothing in this Section limits the Licensor’s right to seek injunctive, equitable, interim, emergency, or protective relief in any available forum to prevent or stop unauthorized use, Standalone Commercialization, infringement, breach, removal of attribution, misuse of branding, or other violation of this EULA.
+
+18.4. If any part of this Section is found unenforceable, invalid, or limited by mandatory law, the remaining parts of this EULA remain in effect to the maximum extent permitted by applicable law.
+
+## 19. License versions and separate permissions
+
+19.1. The Licensor may publish updated versions of this EULA. A Project Notice may specify a version of this EULA that applies to a specific Asset.
+
+19.2. Unless a Project Notice expressly states “or later,” your rights are governed by the specific version of this EULA identified for the Asset.
+
+19.3. The Licensor may grant separate written permissions, waivers, commercial licenses, marketplace permissions, support agreements, dual licenses, or exceptions. Any such permission applies only to the person or entity, Asset, version, scope, and period expressly stated in writing by the Licensor.
+
+19.4. This EULA does not revoke rights validly granted for earlier versions of the Asset under a different license. Earlier versions remain governed by the license terms that applied to those earlier versions.
+
+## 20. Miscellaneous
+
+20.1. If any provision of this EULA is held invalid, illegal, or unenforceable, the remaining provisions remain in full force and effect to the maximum extent permitted by applicable law.
+
+20.2. The failure of the Licensor to enforce any provision of this EULA does not waive the right to enforce that provision or any other provision later.
+
+20.3. You may not assign or transfer this EULA or your rights under it except as part of a transfer of a compliant End Product and only to the extent the transferee agrees to comply with this EULA.
+
+20.4. This EULA does not create a partnership, joint venture, agency, employment relationship, franchise, or fiduciary relationship between you and the Licensor.
+
+20.5. Headings are for convenience only and do not affect interpretation.
+
+20.6. In case of conflict between this EULA and a Project Notice, the Project Notice controls only for project-specific identification data such as Project name, Canonical Repository, copyright notice, attribution text, and additional project-specific notices. This EULA controls all license terms unless the Licensor expressly states otherwise in writing.
+
+20.7. This EULA is the entire agreement between you and the Licensor regarding the Asset, except for separate written agreements signed by the Licensor or other license terms expressly applied by the Licensor to specific material.
+
+## 21. Permission to copy this license text
+
+21.1. Permission is granted to copy and redistribute exact, unmodified copies of this EULA text solely for the purpose of identifying, preserving, referencing, or complying with the license terms for materials distributed by ROMAN ILYIN under this EULA.
+
+21.2. You may not publish a modified license text under the name “Stinger Royalty-Free EULA,” “Stinger Royalty-Free EULA 1.0,” or a confusingly similar name without express written permission from the Licensor.