Lemon串口监控 v0.1.1

Lemon串口监控 0.1.1 发布说明 / Lemon Serial Monitor 0.1.1 Release Notes

简体中文 | English

简体中文

0.1.1 是相对 0.1.0 的维护与发布完整性更新，重点是许可证分发、双语公开文档和版本一致性；它不是新增捕获能力、界面功能或 AI 功能的版本。

本版变化

• 根目录 MIT 许可证 是规范许可证文本。个人和企业都可以免费使用，也允许商业使用和盈利、修改、合并、发布、再分发、再许可和销售副本；复制或分发本软件或其实质部分时，必须保留 Copyright (c) 2026 qingningmneg 版权声明和 MIT 许可声明。
• 安装目录现在包含 docs\LICENSE.txt。安装包同时保留 Inno Setup 简体中文翻译的第三方来源与许可证说明；第三方译文只帮助理解，不取代对应的规范许可证原文。
• 公开 Release 增加独立的 LICENSE.txt，成为第六个公开文件；安装前即可阅读完整 MIT 条款。
• README、安装、构建、安全、发现与下载说明已同步为等价的中英文内容，并继续使用稳定的安装包下载名称。
• 产品版本、Windows 文件版本、安装器、安装、卸载、构建和发布校验器已对齐到产品版本 0.1.1；Windows 文件版本保持 0.1.1.0。

发布文件

每个 0.1.1 公开发布目录只包含以下六个普通文件：

1. LemonSerialMonitor-Setup-x64.exe
2. LemonSerialMonitor-User-Manual-zh-CN.pdf
3. RELEASE-NOTES.md
4. BUILD-INFO.json
5. LICENSE.txt
6. SHA256SUMS.txt

SHA256SUMS.txt 只列出并校验除清单自身以外的另外五个文件。下载后应先核对同一版本的清单，再运行安装程序。

安装与安全

0.1.1 仍使用本地测试证书，不是微软 WHQL、Attestation 或生产签名。发布文件没有微软生产信任链，也没有 RFC 3161 公共时间戳；本地测试签名不能替代正式发布签名。

安装程序会核对载荷、证书和哈希，在明确征得同意后导入公钥证书，并在需要时启用 TESTSIGNING。系统策略变化和 Ports 类过滤器加载可能要求重启。软件不会关闭安全启动；安全启动开启或组织策略禁止 TESTSIGNING 时，安装会停止。

0.1.1 不在已有新式安装上执行原地覆盖，也不要直接覆盖正在运行的服务、已加载的驱动或受保护安装记录。

功能边界

• 监控是被动、只读的：桌面程序和 AI 客户端不打开被监控 COM 端口，内核过滤驱动只复制已经发生的读写和受支持控制事件。
• 软件不提供主动发送、注入、修改、阻断或重放串口数据的能力。
• CLI 和 MCP 仅通过受保护的本机接口工作，按页读取持久化捕获事件；不监听 HTTP/TCP，也不提供任意文件访问。

验证证据边界

0.1.0 是现有 Windows 11 实机和 Windows Server 自动化/契约验证的历史基线。0.1.1 没有新增物理串口设备验收、Windows Server 内核驱动端到端验收或完整安装验收，也不构成通用兼容性、真实硬件认证或生产签名声明。

Windows Server 2022/2025 的历史证据仅包括 GitHub 托管桌面 runner 的平台识别、托管测试和安装契约检查，没有装载内核驱动；Server Core 只有组件布局契约测试，Server 2019 自托管任务未执行。重要环境仍应先在同版本测试机完成驱动安装、重启、捕获、AI 和卸载全流程验证。

更新与卸载

从旧版本更新时，先停止监控并导出或备份需要保留的数据，再使用旧版本卸载程序执行完整卸载；按提示重启并等待清理完成后，安装 0.1.1。不要原地覆盖旧版本。

完整卸载会永久删除本软件的会话、导出、设置、日志、缓存和 AI 状态，以及软件拥有的服务、驱动、过滤器、证书和程序文件。需要保留的数据必须先复制到软件管理目录之外。

English

Version 0.1.1 is a maintenance and release-integrity update relative to 0.1.0. It focuses on license distribution, equivalent bilingual public documentation, and version consistency; it is not a release of new capture, UI, or AI features.

What Changed

• The root MIT License is the canonical license text. Individuals and companies may use the software free of charge, including for commercial and for-profit purposes, and may modify, merge, publish, redistribute, sublicense, and sell copies. Any copy or substantial portion of the software must retain the Copyright (c) 2026 qingningmneg copyright notice and the MIT license notice.
• The installed files now include docs\LICENSE.txt. Setup also retains the third-party source and license notice for the Inno Setup Simplified Chinese translation; a third-party translation helps with understanding but does not replace the corresponding canonical license text.
• The public Release adds a separate LICENSE.txt as its sixth public file, so the complete MIT terms can be read before installation.
• The README, installation, build, security, discovery, and download copy is now equivalent in Chinese and English, while retaining the stable installer download name.
• The product version, Windows file version, installer, installation, uninstall, build, and release verifier are aligned to product version 0.1.1; the Windows file version remains 0.1.1.0.

Release Assets

Each 0.1.1 public release directory contains exactly these six ordinary files:

1. LemonSerialMonitor-Setup-x64.exe
2. LemonSerialMonitor-User-Manual-zh-CN.pdf
3. RELEASE-NOTES.md
4. BUILD-INFO.json
5. LICENSE.txt
6. SHA256SUMS.txt

SHA256SUMS.txt lists and verifies only the other five files, excluding the manifest itself. Verify the same-version manifest before running Setup.

Installation and Security

Version 0.1.1 still uses a local test certificate, not Microsoft WHQL, Attestation, or production signing. The release files have no Microsoft production trust chain and no RFC 3161 public timestamp; local test signing is not a substitute for production release signing.

Setup verifies the payload, certificate, and hashes, imports the public certificate after explicit consent, and enables TESTSIGNING when required. Changes to system policy and loading the Ports class filter may require a restart. The software does not disable Secure Boot; installation stops when Secure Boot is enabled or organizational policy prohibits TESTSIGNING.

Version 0.1.1 does not perform an in-place overwrite of an existing modern installation. Do not directly overwrite a running service, loaded driver, or protected installation record.

Functional Boundaries

• Monitoring is passive and read-only: the desktop application and AI client do not open the monitored COM port, and the kernel filter driver only copies read, write, and supported control events that have already occurred.
• The software does not provide active sending, injection, modification, blocking, or replay of serial data.
• The CLI and MCP work only through protected local interfaces and read persisted capture events through pagination. They do not listen on HTTP/TCP or provide arbitrary file access.

Evidence Boundary

Version 0.1.0 is the historical baseline for the existing physical Windows 11 and automated/contract Windows Server validation. Version 0.1.1 adds no new physical serial-device acceptance, Windows Server kernel-driver end-to-end acceptance, or full installation acceptance, and makes no universal-compatibility, hardware-certification, or production-signing claim.

The historical Windows Server 2022/2025 evidence covers only platform detection, managed tests, and installation-contract checks on GitHub-hosted desktop runners; it did not load the kernel driver. Server Core received component-layout contract tests only, and the Server 2019 self-hosted job was not run. Important environments must still validate driver installation, restart, capture, AI, and uninstall end to end on a test machine running the same version.

Upgrade and Uninstall

To update from an older version, stop monitoring and export or back up the data you need to keep, then perform a full uninstall with the old version's uninstaller. Restart when prompted and wait for cleanup to finish before installing 0.1.1. Do not overwrite the old version in place.

Full uninstall permanently deletes this software's sessions, exports, settings, logs, caches, and AI state, along with the services, driver, filter, certificates, and program files owned by the software. First copy any data that must be retained outside the software-managed directories.

Lemon串口监控 / Lemon Serial Monitor v0.1.0

Lemon串口监控 0.1.0 发布说明

这是第一个可安装版本，面向个人测试和硬件/软件联调。

本版提供

• Windows x64 串口类上层过滤驱动
• LocalSystem 捕获与会话服务
• WPF 列表、Dump、终端界面
• 多端口选择、开始、暂停、继续、停止和确认清空
• HEX/文本查找与八种复制格式
• CSV、TXT、RAW 桌面导出
• JSON、JSONL、CSV、TXT、RAW AI 导出
• 本机 JSON CLI 和标准 MCP stdio 接口
• 图形化安装、旧手工安装迁移、失败回滚与完整卸载
• Windows 10/11 和 Windows Server 2019/2022/2025 平台分流

安装特别说明

驱动使用本地测试证书，不是微软正式生产签名。安装程序会明确征得同意后导入公钥证书，并在需要时启用 TESTSIGNING。安全启动开启时不会安装。系统策略变化和 Ports 类过滤器加载可能要求重启。

安装文件有本地测试签名，但没有微软信任链，也没有 RFC 3161 公共时间戳。第一次运行时测试证书尚未导入，Windows 仍可能显示 SmartScreen 或“未知发布者”。只从本项目 Release 下载并核对 SHA256SUMS.txt。

已知边界

• 桌面界面以实时事件为主，不负责把历史会话重新加载回三个视图；历史分页读取由 AI/命令行接口提供。
• 桌面导出为 CSV、TXT、RAW；JSON/JSONL 使用 AI 接口。
• 单事件捕获上限为 4096 字节，长事件会标记截断。
• 列表和终端有可见容量上限；持久化会话与 AI 完整性字段是长时间分析的主要依据。
• 当前没有主动发送、注入、重放、协议模拟、Modbus 解码或任意文件访问。
• 测试签名版本不适合不能关闭安全启动或禁止 TESTSIGNING 的组织设备。
• 0.1.0 不在已有新式安装上执行原地覆盖；更新前先导出或备份数据，完整卸载旧版本，按提示重启后再安装新版本。
• 没有接入串口设备时，后台服务仍会正常运行；刷新后端口列表为空、驱动暂不可用属于正常状态。

验证范围

• Windows 11 专业版 x64（构建 26100）：当前代码候选已完成图形安装、重启、后台服务自动启动、桌面连接、JSON CLI 和 MCP；候选验证链还完成了前一候选的完整卸载以及当前代码候选的干净安装。无物理串口设备的冷启动中，后台服务保持 Running，启动后的服务控制管理器和 .NET 运行时日志没有本软件服务失败事件。
• 无设备接口实测：status --json、ports --json、schema --json、sessions list --json 均成功；MCP 完成协议初始化，列出 11 个工具和 4 个资源，并实际调用状态和端口工具。当前端口返回空数组是因为验收时没有接入实体串口。
• 真实串口证据：前一候选版本在同机物理设备联调中记录 3653 个事件，界面与服务丢失计数为 0；AI 分页读取覆盖全部 3653 个事件，完整性结果未发现驱动丢弃、服务丢弃或序号缺口。当前代码候选因设备不在场，没有再次做热插拔和持续捕获。
• 自动化门禁：615 项托管测试、919 项 PowerShell 安装安全测试、5 组原生 C/C++ 测试、内核协议编译、WDK Release 驱动构建与代码分析（0 条诊断）、INF 验证和公开名称审计。
• Windows Server 2022/2025 已在 GitHub 托管桌面 runner 完成平台识别、托管测试和安装契约检查，但没有装载内核驱动。Server Core 只有组件布局契约测试；Server 2019 自托管任务未执行。本次没有任何 Server 实机或虚拟机的驱动安装、重启、捕获、AI、卸载端到端验收，因此 2019/2022/2025 桌面体验与 Server Core 都只是兼容目标，不代表已完成真实硬件认证。

卸载

完整卸载会删除本软件的服务、驱动、过滤器、证书、程序和全部本机数据。先把需要保留的导出复制到软件目录之外。被占用的驱动或文件会在重启后继续清理并核验。

---

Lemon Serial Monitor 0.1.0 Release Notes

This is the first installable release, intended for personal testing and hardware/software integration.

What This Release Provides

• Windows x64 upper filter driver for the serial-port class
• LocalSystem capture and session service
• WPF List, Dump, and Terminal views
• Multi-port selection, Start, Pause, Resume, Stop, and confirmed Clear
• HEX/text search and eight copy formats
• CSV, TXT, and RAW desktop export
• JSON, JSONL, CSV, TXT, and RAW AI export
• Local JSON CLI and standard MCP stdio interface
• Graphical installation, migration from old manual installations, rollback on failure, and full uninstall
• Platform-specific handling for Windows 10/11 and Windows Server 2019/2022/2025

Special Installation Notes

The driver uses a local test certificate, not Microsoft production signing. Setup explicitly obtains consent before importing the public certificate and enables TESTSIGNING when required. It does not install while Secure Boot is enabled. Changes to system policy and loading the Ports class filter may require a restart.

The installation file is locally test-signed but has no Microsoft trust chain and no RFC 3161 public timestamp. On first run, the test certificate has not yet been imported, so Windows may still display SmartScreen or "Unknown publisher." Download only from this project's Release and verify SHA256SUMS.txt.

Known Boundaries

• The desktop UI focuses on live events and does not reload historical sessions into its three views. Historical paginated reads are available through the AI/command-line interface.
• Desktop export supports CSV, TXT, and RAW; use the AI interface for JSON/JSONL.
• The per-event capture limit is 4096 bytes. Longer events are marked as truncated.
• The List and Terminal views have visible capacity limits. Persisted sessions and AI integrity fields are the primary basis for long-running analysis.
• There is currently no active sending, injection, replay, protocol simulation, Modbus decoding, or arbitrary file access.
• This test-signed release is unsuitable for organizational devices on which Secure Boot cannot be disabled or TESTSIGNING is prohibited.
• Version 0.1.0 does not perform an in-place overwrite of an existing modern installation. Before updating, export or back up the data, fully uninstall the old version, restart as prompted, and then install the new version.
• The background service continues to run normally when no serial-port device is connected. An empty port list and a temporarily unavailable driver after refresh are normal in this state.

Validation Scope

• Windows 11 Pro x64 (build 26100): the current code candidate completed graphical installation, restart, automatic background-service startup, desktop connection, JSON CLI, and MCP checks. The candidate validation chain also completed full uninstall of an earlier candidate and a clean installation of the current code candidate. During a cold start with no physical serial-port device, the background service remained Running, and the post-start Service Control Manager and .NET runtime logs contained no failure event for this software's service.
• No-device interface checks: status --json, ports --json, schema --json, and sessions list --json all succeeded. MCP completed protocol initialization, listed 11 tools and 4 resources, and actually called the status and port tools. The current port result is an empty array because no physical serial port was connected during acceptance testing.
• Physical serial-port evidence: during hardware integration of an earlier candidate on the same machine, 3653 events were recorded, with UI and service drop counts of 0. AI pagination covered all 3653 events, and the integrity result found no driver drops, service drops, or sequence gaps. Because the device was not present for the current code candidate, hot-plugging and sustained capture were not repeated.
• Automated gates: 615 managed tests, 919 PowerShell installation safety tests, 5 native C/C++ test groups, kernel protocol compilation, a WDK Release driver build and code analysis (0 diagnostics), INF validation, and a public-name audit.
• Windows Server 2022/2025 hosted GitHub desktop runners completed platform detection, managed tests, and installation-contract checks, but did not load the kernel driver. Server Core received component-layout contract tests only; the Server 2019 self-hosted job was not run. This release received no end-to-end acceptance testing for driver installation, restart, capture, AI, and uninstall on a physical or virtual Server system. The Desktop Experience and Server Core variants of 2019/2022/2025 are therefore compatibility targets, not hardware certification.

Uninstall

Full uninstall deletes this software's service, driver, filter, certificate, programs, and all local data. First copy any exports that must be retained outside the software directory. Cleanup and verification for an in-use driver or file continue after the restart.

---

简体中文 README | English README