@esp-vision/device-cli 0.0.0-stage → 0.1.1

package/DEVICE_CORE_NOTICE.md

@@ -0,0 +1,32 @@
+ESP-VISION Device Core
+Copyright 2026 Espressif Systems (Shanghai) CO LTD
+
+The package as a whole and ESP-VISION contributions are distributed under
+the Apache License, Version 2.0. See LICENSE.
+
+The following notices are retained from the Device Core source migrated
+from ESP-VISION-IDE for previously MIT-licensed and upstream-derived portions.
+Third-party dependencies retain their respective licenses.
+
+MIT License
+
+Copyright (c) 2026 ESP-VISION-IDE contributors
+Copyright (c) 2024 Volodymyr Shymanskyy
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

package/README.md

@@ -1,3 +1,62 @@
-# Temporary Holding Version
+# ESP-VISION Device CLI
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+`@esp-vision/device-cli` installs the `esp-vision-device` command for device discovery, inspection, configuration, control, firmware updates, Python execution, device file operations, JPEG capture, sequential batch plans, and bounded event watches. It is an optional host interface backed by the same `@esp-vision/device-core` package used by ESP-VISION clients.
+
+Requires Node.js 22 or newer. Serial access requires Python with `pyserial`; firmware flashing requires Python `esptool==5.6.0`. LAN discovery uses the bundled multicast-DNS client. Check the selected interpreter with `PYTHON --version` and `PYTHON -c "import serial"`; install pyserial there with `PYTHON -m pip install pyserial` (replace `PYTHON` with that executable). Windows Python Launcher users can use `--python py` and `py -m pip install pyserial`. A failed serial setup gets a bounded environment diagnosis after connection cleanup; successful connections, TCP operations, help, and offline firmware checks do not start it. Busy/access-denied errors keep their port-specific guidance; an unknown adapter failure is not proof of missing Python or pyserial.
+
+Run `esp-vision-device --help` for the command reference, or `esp-vision-device --help --json` for the versioned machine-readable command, output, and limit capabilities envelope.
+
+## Python execution
+
+Choose exactly one input: `--source CODE` for inline code, `--file LOCAL.py` for a local source file, or `--path DEVICE.py` for a file already on the device. `--timeout MS` must be a positive integer and cancels a waiting execution when it expires. `--max-output-chars` bounds captured Python output.
+
+The default `--completion wait` waits for completion and returns bounded output metadata. `--completion start` requires `--path` and acknowledges after the device VM enters its runner. Omit `--timeout` with `start`; it is an execution deadline for `wait` only. This does not confirm that the application initialized successfully or completed. The CLI then releases the connection and exits; it does not keep watching or resume the script.
+
+During foreground `python` execution and Python steps in a batch, `python.output`, `python.log`, and `python.state` events stream as NDJSON on stderr while the command is still running. Python text is capped by `--max-output-chars` (16,384 by default); a single event with `truncated: true` marks the limit. The stdout JSON summary contains metadata, not a duplicate of streamed output. For live Python output, use `--completion wait`.
+
+## Runtime state and connection behavior
+
+A targeted `inspect`, `configure`, firmware check, `capture`, `watch`, or native `files write` acquires the device without probing the friendly REPL, so these operations do not send Ctrl-C to a running application. `inspect --probe` actively checks discovered ports using the same passive connection. Python execution, REPL-backed `files list/read/remove/mkdir`, `control`, firmware updates, and batches use the normal REPL connection probe; these commands can send Ctrl-C.
+
+The `runtime.scriptRunning` and `runtime.run` fields describe work tracked by the current SDK session. A fresh CLI process cannot use them to determine whether a detached program started earlier is still running on the device. `runtime.vmReady` means the VM is ready; it does not mean the VM is idle.
+
+## Device files and capture
+
+For a continuous app, finish directory operations and uploads before starting it, then take passive captures while it runs. Stop it with `control --action stop` before reading progress files. `--mode soft|hard` applies only to `control --action reset`; it is not a stop option. A REPL-backed read can interrupt the app and trigger LCD cleanup, so a subsequent `DISPLAY_NOT_READY` does not by itself establish a firmware failure. Use increasing application frame counters across captures to verify liveness; a fresh connection's session-local execution state cannot establish global idleness.
+
+`files list`, `files read`, `files write`, `files remove`, and `files mkdir` operate on device paths. `files read DEVICE_PATH --output LOCAL_FILE` writes binary content to a local file. `files write DEVICE_PATH --file LOCAL_FILE` sends local bytes to the device. Reads are capped at 16 MiB by default; `--max-bytes` can lower that limit.
+
+`capture camera|screen --output LOCAL.jpg` writes one JPEG and returns its path, byte count, source, MIME type, and capture metadata. Images are never embedded as base64 in JSON output. The `source` field identifies the requested source; it does not certify whether annotations are present. `camera` observes the application's latest camera frame, not the LCD image. Application drawing depends on firmware publication behavior; firmware advertising `debug.capture_frame.observed.v1` supplies an independent copy made at acquisition, before later drawing, without triggering a new acquisition. `screen` captures the current LCD framebuffer, including drawing rendered there; use it to verify LCD overlays and UI. It requires an initialized display, and camera/display dimensions may differ. Neither source starts the application or initializes the sensor/display for you.
+
+## Bounded event watch
+
+`watch --duration MS --port PATH` or `watch --duration MS --tcp HOST[:PORT]` keeps one device connection open for the requested duration (1 ms to 1 hour). It passively observes Python output, device logs, state changes, and diagnostics available to the currently acquired session as NDJSON on stderr, then releases the connection and returns a JSON summary. EV-MUX pins Python stdout to the session that started the program, so a new watch cannot reattach to stdout from a detached `--completion start` run. Use foreground `--completion wait` when live Python output is needed. To check a detached app, use captures or have the app write progress artifacts that can be read later. SIGINT and SIGTERM cancel the watch and still release ownership. A lost device connection is reported as a command failure; the CLI does not reconnect or launch a script.
+
+## Batch plan
+
+`batch PLAN.json --port PATH` or `batch PLAN.json --tcp HOST[:PORT]` validates the complete plan before connecting, then runs each operation in order over one connection. Local `file` and `output` paths are relative to the plan file. The first failed operation stops the plan; the report contains completed operations and the failure. The device is disconnected in all cases.
+
+```json
+{
+  "schemaVersion": 1,
+  "operations": [
+    { "op": "python", "source": "print('hello')" },
+    { "op": "files.list", "path": "/" },
+    { "op": "files.read", "path": "/boot.py", "output": "./boot.py" },
+    { "op": "files.write", "path": "/backup.bin", "file": "./backup.bin" },
+    { "op": "files.remove", "path": "/old.bin" },
+    { "op": "files.mkdir", "path": "/data", "recursive": true },
+    { "op": "capture", "source": "camera", "output": "./frame.jpg", "quality": 80 }
+  ]
+}
+```
+
+## Output and cancellation
+
+`--json` writes exactly one JSON envelope to stdout with `schemaVersion: 1`. A success uses `{ "schemaVersion": 1, "ok": true, "command": "...", "result": ... }`. A failure uses `{ "schemaVersion": 1, "ok": false, "command": "...", "error": { "code": "...", "message": "..." } }`; cleanup failures appear separately as `cleanupError`. Batch failures include `completed` and `failed` entries. Binary data is written to files, never embedded in the envelope.
+
+Status, Python output, firmware phases, cancellation, errors, and duration are NDJSON events on stderr. SIGINT exits with code 130, SIGTERM with 143, argument/plan errors with 2, other failures with 1, and success with 0. Busy or uncertain operations are never retried automatically.
+
+Inspect JSON output uses the same versioned envelope as other commands. Human-readable inspect output remains a terminal table.
+
+Device paths such as `/models` stay absolute device paths on Windows. Git Bash/MSYS may rewrite them; use PowerShell or prefix the individual command with `MSYS2_ARG_CONV_EXCL="*"`, supplying local paths in Windows form. Quoting the device path alone does not prevent conversion. Invalid device paths now fail before connecting, with a shell hint for Windows host paths.

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,135 @@
+# Third-party notices
+
+The CLI bundle includes the following third-party packages. Their original license files are in `licenses/`.
+
+| Package | Version | License | License file |
+| --- | --- | --- | --- |
+| @leichtgewicht/ip-codec | 2.0.5 | MIT | `leichtgewicht__ip-codec-LICENSE` |
+| ansi-regex | 6.4.0 | MIT | `ansi-regex-license` |
+| dns-packet | 5.6.1 | MIT | `dns-packet-LICENSE` |
+| emoji-regex | 10.6.0 | MIT | `emoji-regex-LICENSE-MIT.txt` |
+| get-east-asian-width | 1.7.0 | MIT | `get-east-asian-width-license` |
+| multicast-dns | 7.2.5 | MIT | `multicast-dns-LICENSE` |
+| smol-toml | 1.9.1 | BSD-3-Clause | `smol-toml-LICENSE` |
+| string-width | 7.2.0 | MIT | `string-width-license` |
+| strip-ansi | 7.2.0 | MIT | `strip-ansi-license` |
+| thunky | 1.1.0 | MIT | `thunky-LICENSE` |
+
+## Preserved source license comments
+
+Original copyright and SPDX comments from bundled source files are reproduced below. Recognized legal comments also remain inline in `dist/device-cli.mjs`.
+
+### Source notice 1
+
+Bundled from: `node_modules/@esp-vision/device-core/src/evrepl.js`
+
+```text
+/*
+ * SPDX-FileCopyrightText: 2026 ESP-VISION-IDE
+ * SPDX-License-Identifier: Apache-2.0
+ *
+ * Framed friendly-REPL client over EV-MUX repl channels.
+ *
+ * With boot-default EV-MUX firmware there is no raw REPL bootstrap: the
+ * device speaks frames from power-on, and the friendly REPL is reachable
+ * through repl.stdin / repl.stdout frames. This module executes Python
+ * snippets over that channel and resolves their stdout, so device info,
+ * the file tree and all filesystem operations (read/write/create/delete)
+ * run framed, with no raw REPL access anywhere.
+ */
+```
+
+### Source notice 2
+
+Bundled from: `node_modules/@esp-vision/device-core/src/device_session.js`
+
+```text
+/*
+ * SPDX-FileCopyrightText: 2026 ESP-VISION-IDE
+ * SPDX-License-Identifier: Apache-2.0
+ *
+ * UI-independent EV-MUX device interpreter. Both the browser IDE and agent
+ * integrations construct this class with the same EvMuxParser/EvRepl
+ * implementations, so protocol negotiation and firmware operations cannot
+ * drift between the two entry points.
+ */
+```
+
+### Source notice 3
+
+Bundled from: `node_modules/@esp-vision/device-core/src/evmux.js`
+
+```text
+/*
+ * SPDX-FileCopyrightText: 2026 ESP-VISION-IDE
+ * SPDX-License-Identifier: Apache-2.0
+ */
+```
+
+### Source notice 4
+
+Bundled from: `node_modules/@esp-vision/device-core/src/device.js`, `node_modules/@esp-vision/device-core/src/device_operations.js`, `node_modules/@esp-vision/device-core/src/firmware_updates.js`
+
+```text
+/* SPDX-FileCopyrightText: 2026 ESP-VISION-IDE
+ * SPDX-License-Identifier: Apache-2.0
+ */
+```
+
+### Source notice 5
+
+Bundled from: `node_modules/smol-toml/dist/date.js`, `node_modules/smol-toml/dist/error.js`, `node_modules/smol-toml/dist/extract.js`, `node_modules/smol-toml/dist/index.js`, `node_modules/smol-toml/dist/parse.js`, `node_modules/smol-toml/dist/primitive.js`, `node_modules/smol-toml/dist/stringify.js`, `node_modules/smol-toml/dist/struct.js`, `node_modules/smol-toml/dist/util.js`
+
+```text
+/*!
+ * Copyright (c) Squirrel Chat et al., All rights reserved.
+ * SPDX-License-Identifier: BSD-3-Clause
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright notice, this
+ *    list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright notice,
+ *    this list of conditions and the following disclaimer in the
+ *    documentation and/or other materials provided with the distribution.
+ * 3. Neither the name of the copyright holder nor the names of its contributors
+ *    may be used to endorse or promote products derived from this software without
+ *    specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+ * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+ * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+```
+
+### Source notice 6
+
+Bundled from: `node_modules/@esp-vision/device-core/src/firmware_feed.js`, `node_modules/@esp-vision/device-core/src/firmware_flash.js`, `node_modules/@esp-vision/device-core/src/index.js`, `node_modules/@esp-vision/device-core/src/network_discovery.js`, `node_modules/@esp-vision/device-core/src/network_discovery_node.js`, `node_modules/@esp-vision/device-core/src/node_inventory.js`, `node_modules/@esp-vision/device-core/src/node_rom.js`, `node_modules/@esp-vision/device-core/src/node_transport.js`, `src/cli.js`
+
+```text
+// SPDX-FileCopyrightText: 2026 ESP-VISION-IDE
+```
+
+### Source notice 7
+
+Bundled from: `node_modules/@esp-vision/device-core/src/firmware_io.js`, `node_modules/@esp-vision/device-core/src/firmware_release.js`, `node_modules/@esp-vision/device-core/src/node.js`, `src/serial_diagnostics.js`
+
+```text
+// SPDX-FileCopyrightText: 2026 Espressif Systems (Shanghai) CO LTD
+```
+
+### Source notice 8
+
+Bundled from: `node_modules/@esp-vision/device-core/src/device_files.js`, `node_modules/@esp-vision/device-core/src/device_python.js`, `node_modules/@esp-vision/device-core/src/firmware_feed.js`, `node_modules/@esp-vision/device-core/src/firmware_flash.js`, `node_modules/@esp-vision/device-core/src/firmware_io.js`, `node_modules/@esp-vision/device-core/src/firmware_release.js`, `node_modules/@esp-vision/device-core/src/index.js`, `node_modules/@esp-vision/device-core/src/network_discovery.js`, `node_modules/@esp-vision/device-core/src/network_discovery_node.js`, `node_modules/@esp-vision/device-core/src/node.js`, `node_modules/@esp-vision/device-core/src/node_inventory.js`, `node_modules/@esp-vision/device-core/src/node_rom.js`, `node_modules/@esp-vision/device-core/src/node_transport.js`, `src/cli.js`, `src/serial_diagnostics.js`
+
+```text
+// SPDX-License-Identifier: Apache-2.0
+```