Sync audited public release boundary

CONTRIBUTING.md

@@ -4,6 +4,8 @@ Open a focused issue or pull request. Repository-owned content is licensed under
 
 The inbound model is the normal same-license model: contributors retain copyright and intentionally submitted contributions are licensed under Apache-2.0. This project does not require a CLA, DCO sign-off, real name, or private contact information.
 
+Contributors must have the rights needed to submit their code, documentation, data, geometry, images, and other assets and to provide them under the project's license.
+
 Contributions must:
 
 - keep solver integrations optional, lazy, API-first, and vendor-neutral at the agent layer;

DISCLAIMER.md

@@ -2,4 +2,4 @@
 
 This software is provided for research, education, and automation prototyping. Engineering models require independent verification by qualified practitioners. No result should be used for safety-critical, regulatory, or production decisions without appropriate validation.
 
-This is an independent project and is not affiliated with, endorsed by, certified by, or supported by Ansys, Inc. Product names identify interoperability targets only. Ansys software must be obtained separately, users must follow the terms and license category applicable to their intended use, and this repository does not redistribute proprietary binaries. Apache-2.0 applies only to repository-owned content and does not grant rights to Ansys software, documentation, examples, trademarks, or proprietary formats.
+This is an independent project and is not affiliated with, endorsed by, certified by, or supported by Ansys, Inc. Product names identify interoperability targets only. Ansys software must be obtained separately. License types are not interchangeable, and users must follow the terms governing their intended use. Apache-2.0 applies only to contributor-held rights; it grants no rights in Ansys software, documentation, trademarks, official/vendor assets, solver-derived rights, or other third-party materials. Solver-derived numbers and project-rendered figures are published only as validation evidence, without implying Ansys approval or legal clearance.

README.md

@@ -131,8 +131,8 @@ python tools/check_links.py
 
 This is an independent community project. It is not affiliated with, endorsed by, certified by, or supported by Ansys, Inc. Ansys software and an appropriate license must be obtained separately and used under their applicable terms. The repository does not distribute Ansys software, proprietary solver databases, vendor documentation, logos, or trade dress.
 
-Original repository-owned code, documentation, and fixtures are licensed under the [Apache License 2.0](LICENSE). That license does not license Ansys software, documentation, examples, trademarks, or proprietary formats. Student licenses are limited to educational use and exclude commercial use and competitive analysis. Engineering results require independent review by qualified practitioners.
+The [Apache License 2.0](LICENSE) applies only to rights held by project contributors. It grants no rights in Ansys software, documentation, trademarks, official/vendor assets, or other third-party materials. Solver-derived numbers and project-rendered figures are published as validation evidence without claiming that Ansys licensed them under Apache-2.0. Ansys license types are not interchangeable; users must lawfully obtain the software and license appropriate to their intended use. Engineering results require independent review by qualified practitioners.
 
 Read [Ansys usage and compliance](docs/ANSYS_USAGE_AND_COMPLIANCE.md), the full [disclaimer](DISCLAIMER.md), and [third-party notices](THIRD_PARTY_NOTICES.md).
 
-Ansys, Mechanical, Fluent, AEDT, Maxwell, HFSS, Rocky, System Coupling, SpaceClaim, and PyAnsys are trademarks or registered trademarks of Ansys, Inc. or its subsidiaries in the United States or other countries. All trademarks remain the property of their respective owners.
+Ansys and its product names are marks of Ansys, Inc. or its subsidiaries and are used only to identify interoperability targets. Other names may be marks of their respective owners.

README.zh-CN.md

@@ -131,8 +131,8 @@ python tools/check_links.py
 
 本项目是独立社区项目，与 Ansys, Inc. 不存在隶属、背书、认证或官方支持关系。Ansys 软件和适用许可证必须另行取得，并按相应条款使用。仓库不分发 Ansys 软件、专有求解器数据库、厂商文档、标志或商业外观。
 
-仓库原创代码、文档和 fixtures 采用 [Apache License 2.0](LICENSE)。该许可证不许可 Ansys 软件、文档、示例、商标或专有格式。Student 许可证限教育用途，不适用于商业用途或竞争分析。工程结果必须由具备相应资质的专业人员独立复核。
+[Apache License 2.0](LICENSE) 仅适用于项目贡献者持有的权利；它不授予 Ansys 软件、文档、商标、官方/厂商资产或其他第三方材料的权利。solver-derived 数值和项目渲染图仅作为验证证据发布，不声称 Ansys 已将其按 Apache-2.0 许可。Ansys 的许可证类型不能相互替代；用户必须为预期用途合法取得相应软件与许可证。工程结果必须由具备相应资质的专业人员独立复核。
 
 请阅读 [Ansys 使用与合规](docs/ANSYS_USAGE_AND_COMPLIANCE.md)、完整[免责声明](DISCLAIMER.md)与[第三方声明](THIRD_PARTY_NOTICES.md)。
 
-Ansys、Mechanical、Fluent、AEDT、Maxwell、HFSS、Rocky、System Coupling、SpaceClaim 与 PyAnsys 是 Ansys, Inc. 或其子公司在美国或其他国家/地区的商标或注册商标，相关权利归各自所有者所有。
+Ansys 及其产品名称是 Ansys, Inc. 或其子公司的标识，本项目仅用它们指明互操作目标；其他名称可能是各自权利人的标识。

SECURITY.md

@@ -1,5 +1,5 @@
 # Security policy
 
-Do not open a public issue for a vulnerability involving credentials, license infrastructure, command injection, unsafe executable discovery, network transfer, or artifact handling. After publication, use the repository's GitHub **Report a vulnerability** private-reporting form. If that feature is not enabled, wait for the maintainer to configure a private channel; do not disclose exploitable details publicly and do not guess an email address.
+Do not open a public issue for a vulnerability involving credentials, license infrastructure, command injection, unsafe executable discovery, network transfer, or artifact handling. Use GitHub's **Report a vulnerability** form only if it is visibly available for the repository. Repository files cannot prove that private vulnerability reporting is enabled. If no private channel is displayed, ask the maintainer to configure one without disclosing exploitable details publicly and do not guess an email address.
 
 Include the affected revision, impact, minimal reproduction steps, and a proposed mitigation when possible. Never attach license files, tokens, private paths, hostnames, private addresses, proprietary solver inputs/outputs, or confidential models. Product vulnerabilities in Ansys software itself must be reported through Ansys's applicable official process, not this independent repository.