klayout-klink 0.1.0__tar.gz

klayout_klink-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 klinkdev2026
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

klayout_klink-0.1.0/PKG-INFO

@@ -0,0 +1,416 @@
+Metadata-Version: 2.4
+Name: klayout-klink
+Version: 0.1.0
+Summary: AI-native control plane for KLayout — thin RPC bridge + modular external workers
+Author: klink developers
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/klinkdev2026/klayout-klink
+Project-URL: Repository, https://github.com/klinkdev2026/klayout-klink
+Project-URL: Issues, https://github.com/klinkdev2026/klayout-klink/issues
+Keywords: klayout,eda,gds,rpc,ipc
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering :: Electronic Design Automation (EDA)
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: klink-boxmaze-rs<0.2,>=0.1
+Requires-Dist: klink-trackmaze-rs<0.2,>=0.1
+Provides-Extra: photonics
+Requires-Dist: gdsfactory<10,>=9.40; extra == "photonics"
+Dynamic: license-file
+
+# klink
+
+<p align="right">
+  <a href="./README.md">English</a> | <a href="./README.zh-CN.md">中文</a>
+</p>
+
+klink is an AI-native control plane for [KLayout](https://www.klayout.de/).
+It turns a running KLayout GUI into a scriptable layout kernel that can be
+controlled from external Python processes, MCP clients, and AI agents.
+
+The project is split into three layers:
+
+- `klink`: the external Python client, MCP bridge, routing/domain logic, and
+  agent-facing workflows.
+- `klink_plugin`: a thin KLayout-side RPC plugin that exposes selected `pya`
+  and GUI operations.
+- `examples_klink/public`, `tests/public`, and `docs/public`: examples,
+  validation, and release documentation.
+
+The core Python package pulls in no third-party runtime libraries — its only
+declared dependency is klink's own Rust acceleration kernel, shipped as a
+prebuilt wheel. Virtual environments, caches, build outputs, and local test
+artifacts are intentionally not part of a clean release.
+
+## What It Does
+
+- Controls KLayout over local TCP RPC, with batch methods sized for generated
+  layouts (thousands of shapes/instances/PCells per call).
+- Reads layout, cell, layer, shape, view, selection, and method metadata.
+- Creates and edits shapes, text, cells, instances, PCells, Ports, and Anchors.
+- Routes: tapered/steiner/damped/channel backends over Port/Anchor markers,
+  plus a detailed-router → live LVS flow for custom-device circuits.
+- Exposes KLayout operations as MCP tools through `klink-mcp`, navigable with
+  `klink.find_tools`; runs controlled `pya` snippets as the escape hatch.
+- Remembers what you SEND: selections sent from the KLayout toolbar become
+  durable ids an agent can resolve ("this area", "the one I just sent").
+- Drives many KLayout sessions from one bridge and moves geometry between
+  them with a dry-run-then-commit transfer.
+- Records a working session — manual edits and RPC edits — into a replayable
+  Python script (plus a standalone `pya` variant).
+- Supports gdsfactory-oriented workflows, including Port markers, component
+  placement, routing, and klive-compatible `c.show()` display.
+- Keeps the KLayout plugin thin while heavier logic runs in external Python.
+
+## Repository Layout
+
+```text
+klink/                  Python client, MCP bridge, and core logic
+klink_plugin/           KLayout salt plugin
+examples_klink/public/  Public, open-box-runnable example gallery
+tests/public/           Public test suite (no KLayout required)
+docs/public/            Release documentation
+rust/                   Rust acceleration crate (klink_boxmaze)
+pyproject.toml          Python packaging configuration
+README.md               English README
+README.zh-CN.md         Chinese README
+CLAUDE.md               Claude Code operating rules and project context
+LICENSE                 Apache-2.0 license
+THIRD_PARTY_NOTICES.md  Third-party notices
+```
+
+## Requirements
+
+- **KLayout** — the layout editor klink controls; for everything live this is
+  the core prerequisite. Install the standard desktop build from
+  <https://www.klayout.de/build.html>. klink is developed and tested against
+  KLayout 0.30.x; any recent official desktop build (whose macro environment
+  provides the `pya` Qt bindings) should work. Purely offline workflows (the
+  public test suite and the offline demos) run without it.
+- Python 3.10 or newer (the bundled Rust kernel targets CPython 3.10–3.13).
+- Optional: Claude Code or another MCP client.
+- Optional: gdsfactory, the `klayout` Python package, NumPy/OpenCV, or detector
+  dependencies depending on the workflow.
+
+## Install Python Package
+
+For normal use, install the published package from PyPI:
+
+```powershell
+python -m pip install klayout-klink
+```
+
+`pip install klayout-klink` installs klink **and its Rust acceleration kernel**
+(`klink-boxmaze-rs`) — klink's own code, shipped as a pre-built wheel for
+Linux / macOS / Windows on CPython 3.10–3.13. You get the fast path
+automatically; nothing else to do.
+
+> **On a platform with no pre-built kernel wheel** (an unusual OS / arch /
+> Python), pip falls back to building the kernel from source, which needs a
+> Rust toolchain (rustup). If you don't have one — or want the lightest possible
+> install — use `pip install klayout-klink --no-deps` for the **pure-Python core
+> only**: everything still works (the kernel has a pure-Python fallback), just
+> slower on large place-and-route jobs.
+
+**Third-party** scientific libraries (klayout, gdsfactory, numpy, …) are **not**
+bundled — install the ones a feature needs yourself, into the same interpreter:
+
+```powershell
+python -m pip install klayout                          # offline DB / LVS extraction
+python -m pip install gdsfactory                       # silicon-photonics routing
+python -m pip install numpy opencv-python-headless     # nanodevice flake
+python -m pip install scipy scikit-learn scikit-image  # flake detectors
+```
+
+When a feature needs a library that is missing, klink returns an error naming
+the exact `pip install` command — you do not have to know these in advance.
+
+### From source (development only)
+
+Use an editable install (`-e`) only when you are working on klink itself — it
+points the package at your working tree so source edits take effect immediately.
+Normal users do not need this.
+
+Windows PowerShell:
+
+```powershell
+git clone <repo-url> klink
+cd klink
+py -3.11 -m venv .venv
+.\.venv\Scripts\Activate.ps1
+python -m pip install -U pip
+python -m pip install -e .
+```
+
+Linux / macOS:
+
+```bash
+git clone <repo-url> klink
+cd klink
+python3 -m venv .venv
+source .venv/bin/activate
+python -m pip install -U pip
+python -m pip install -e .
+```
+
+## Install KLayout Plugin
+
+Prerequisite: KLayout itself must be installed first — get the desktop build
+for your OS from <https://www.klayout.de/build.html>.
+
+`klink_plugin` is a KLayout salt package. Once installed, KLayout autoruns
+`pymacros/klink.lym` and starts:
+
+- klink RPC on `127.0.0.1:8765`. If the port is busy, it tries the next ports up
+  to `8799`.
+- a klive-compatible server on `127.0.0.1:8082` for gdsfactory-style `c.show()`
+  workflows.
+
+Windows:
+
+```powershell
+cd path\to\klink
+New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\KLayout\salt" | Out-Null
+Copy-Item -Path ".\klink_plugin" -Destination "$env:USERPROFILE\KLayout\salt\" -Recurse -Force
+```
+
+Linux / macOS:
+
+```bash
+cd /path/to/klink
+mkdir -p ~/.klayout/salt
+cp -R klink_plugin ~/.klayout/salt/
+```
+
+Either way the plugin ends up at `<KLayout salt dir>/klink_plugin/` (the folder
+that contains `grain.xml`).
+
+Restart KLayout after copying the plugin. Each KLayout window runs its own
+klink session: it binds the first free port in `8765`–`8799` and registers as
+session `klayout-<port>`, so with several windows open there is one listener
+per window (`8765`, `8766`, …). A successful startup prints:
+
+```text
+[klink.server] listening on 127.0.0.1:8765
+```
+
+When upgrading an old plugin copy, close KLayout, remove the old
+`salt/klink_plugin` directory, copy the new `klink_plugin` folder, then restart
+KLayout.
+
+## Smoke Test
+
+Start KLayout with the plugin loaded, then connect directly from Python:
+
+```python
+from klink import KLinkClient
+
+with KLinkClient() as c:
+    print(c.ping(nonce=42))
+    print(c.layout_info(verbosity="summary"))
+```
+
+If KLayout is listening on a non-default port:
+
+```python
+from klink import KLinkClient
+
+with KLinkClient(port=8766) as c:
+    print(c.ping())
+```
+
+For a first end-to-end result with no external geometry, run one of the public
+demos (see [`docs/public/demos.md`](docs/public/demos.md)):
+
+```bash
+python -m examples_klink.public.demos.ebl_wraparound      # fully offline
+```
+
+## Claude Code / MCP
+
+After installing the Python package, `klink-mcp` is available as a command-line
+entry point.
+
+Install the agent skills and project memory files:
+
+```powershell
+cd path\to\klink
+klink-mcp --setup .
+```
+
+This installs or updates:
+
+```text
+.claude/skills/klayout/SKILL.md
+.claude/skills/klayout-gdsfactory/SKILL.md
+CLAUDE.md
+```
+
+Register the MCP server with Claude Code:
+
+```powershell
+claude mcp add klayout -- python -m klink.mcp --profile read,write,verify,escape --session-id project-klink
+```
+
+Common profiles:
+
+| Profile | Purpose |
+| --- | --- |
+| `read` | Read-only exploration: layout, cell, layer, shape, view, and selection queries. |
+| `write` | Editing tools: create cells, layers, shapes, instances, PCells, and undo records. |
+| `verify` | DRC / LVS verification tools. |
+| `escape` | Escape-hatch tools such as `exec.python`. |
+| `all` | Expose everything. |
+
+Profiles can be combined:
+
+```powershell
+python -m klink.mcp --profile read,write,verify,escape
+```
+
+Optional libraries must be installed into the same Python environment that
+runs `klink.mcp`. For example, if gdsfactory tools report missing dependencies,
+install gdsfactory into that same environment:
+
+```powershell
+python -m pip install gdsfactory
+```
+
+Use the MCP `klink.status` tool to inspect the active interpreter, detected
+capabilities, and KLayout connection state.
+
+## Tests
+
+The public test suite is pure-Python and does not require KLayout:
+
+```powershell
+python -m pytest -q tests/public
+```
+
+Integration tests (routing, LVS, recorder) need a live KLayout with the
+`klink_plugin` loaded and are exercised in the development repository.
+
+## Publishing to PyPI (maintainers)
+
+One tag publishes TWO PyPI projects: `klayout-klink` (pure-Python core) and
+`klink-boxmaze-rs` (the Rust kernel, platform wheels for Linux/macOS/Windows ×
+CPython 3.10–3.13). The KLayout plugin is shipped separately as a salt package
+and is not on PyPI. Publishing is done by CI (`.github/workflows/release.yml`),
+not by hand — it builds everything, gates on a 16-combo `pip install` smoke
+test, then uploads via PyPI Trusted Publishing:
+
+```powershell
+git tag v0.1.0            # version must match klink/_meta.py + rust/klink_boxmaze/pyproject.toml
+git push origin v0.1.0    # triggers the Release workflow
+```
+
+One-time setup: on pypi.org add a *pending publisher* (GitHub) for each of the
+two project names, pointing at this repo and `release.yml`.
+
+After publishing, users install with `pip install klayout-klink` — no clone and
+no `-e`. The editable (`-e`) install is only for developing klink itself.
+
+## Troubleshooting
+
+### Connecting from Python fails
+
+Check that:
+
+- KLayout is running.
+- `klink_plugin` was copied into the KLayout salt directory.
+- KLayout was restarted after plugin installation.
+- Port `8765` is available, or use the actual session port such as `8766`.
+- Firewall or security software is not blocking localhost TCP.
+
+### MCP tools exist but return KLayout connection errors
+
+The MCP server is running, but KLayout is not reachable. Start KLayout with the
+plugin loaded, then call `klink.reconnect` or restart the MCP client. Use
+`klink.status` to inspect the last connection error.
+
+### gdsfactory or detector tools report missing dependencies
+
+Install the missing library in the same environment used by the script or MCP
+server (the error names the exact one):
+
+```powershell
+python -m pip install gdsfactory
+python -m pip install scipy scikit-learn scikit-image
+```
+
+### PowerShell blocks `.venv` activation
+
+Allow script execution for the current PowerShell process:
+
+```powershell
+Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
+.\.venv\Scripts\Activate.ps1
+```
+
+## Further Reading
+
+- [`docs/public/getting-started.md`](docs/public/getting-started.md): install, configure, and first result.
+- [`docs/public/architecture.md`](docs/public/architecture.md): the three tiers and the control path.
+- [`docs/public/demos.md`](docs/public/demos.md): the demos and what each requires.
+- [`docs/public/control-plane.md`](docs/public/control-plane.md): the typed RPC surface, the MCP tool catalogue, batch authoring.
+- [`docs/public/interactive-workflows.md`](docs/public/interactive-workflows.md): SEND selection memory, multi-session transfer, the recorder.
+- [`CLAUDE.md`](CLAUDE.md): Claude Code operating rules and project context.
+- [`klink/mcp/README.md`](klink/mcp/README.md): MCP bridge details.
+
+## Contributing
+
+Contributions are welcome. A few project-specific rules keep klink coherent:
+
+- **Process purity.** `klink/` is pure mechanism and holds zero process data
+  (no hardcoded layers, devices, DRC numbers, ports, or PDK instances). Process
+  facts live in an example or user `pdk.py` and are passed explicitly into the
+  APIs. Do not add process constants to `klink/`.
+- **One intention = one call.** New agent-facing tools use one call per user
+  intention, errors that instruct (carry a `next_action`), validate-before-mutate,
+  and state persisted on disk.
+- **Tests must pass.** Run the public suite before sending a change:
+  `python -m pytest -q tests/public`. Routing/LVS changes count as done only on
+  a live KLayout LVS `match=True`.
+- **Byte-frozen router.** `klink/routing/backends/flexdr/` and the crate under
+  `rust/` are byte-parity baselines — the Rust kernel is a speed-only port of
+  the pure-Python reference. Do not alter them casually.
+- **Preflight.** `python -m klink.doctor` checks your interpreter, the plugin
+  connection, and the client/plugin version handshake.
+
+Open an issue or a pull request describing the change and how you verified it.
+Contributions are accepted under the project's Apache-2.0 license.
+
+Want to contribute a PR, discuss a larger change, or co-develop a feature?
+Reach the maintainers at **klinkdev2026@163.com** (or open a GitHub issue).
+
+## Acknowledgements
+
+klink builds on and borrows from excellent open-source work:
+
+- **[KLayout](https://www.klayout.de/)** — the layout editor and `pya`/`db` APIs
+  klink drives and embeds into.
+- **[OpenROAD](https://github.com/The-OpenROAD-Project/OpenROAD)** (BSD-3-Clause)
+  — klink's routing engine contains faithful ports and concept adaptations of
+  OpenROAD's detailed router `drt` (FlexDR / FlexPA / FlexGC) and global
+  router `grt` (FastRoute).
+- **[gdsfactory](https://github.com/gdsfactory/gdsfactory)** — the photonic
+  component and `route_bundle` backend behind the silicon-photonics workflows.
+- **[klive](https://github.com/gdsfactory/klive)** (MIT) — the display protocol
+  that klink's plugin reimplements on port 8082 so gdsfactory-style
+  `Component.show()` works unchanged.
+- **[KlayoutClaw](https://github.com/caidish/KlayoutClaw)** (MIT) — nanodevice
+  flake-detection priors and morphological mask helpers.
+- **[Klayout-Router](https://github.com/Legendrexial/Klayout-Router)** (MIT) —
+  the EBL auto-patching idea behind the writefield patch generator.
+
+Formal third-party copyright and license texts are in
+[`THIRD_PARTY_NOTICES.md`](THIRD_PARTY_NOTICES.md).
+
+## License
+
+Apache-2.0. See `LICENSE`. Third-party components retain their own licenses; see
+`THIRD_PARTY_NOTICES.md`.