QueryCraft 0.1.11

QueryCraft 0.1.11

本次更新

• 新增原生数据传输工作台，支持可复用任务、结构与数据复制、逐表过滤、Upsert、后台执行和取消回滚。
• MySQL LOAD DATA 与 PostgreSQL COPY 原生批量通道实现有界流式传输；四个方向千万行全量校验通过，实测耗时 45.75～121.81 秒，测试进程采样峰值内存 26.34～40.62 MiB。
• 新增 MySQL 结构对比与同步，支持差异检查、SQL 预览和部署。
• 主程序与 MCP 统一凭据授权，减少重复钥匙串授权；改善 MCP 安装进度和兼容性反馈。
• 改善深色编辑器背景及数据传输界面，精简中英文 README 为产品能力与实测性能。

What's New

• Added a native data-transfer workbench with reusable tasks, structure/data copying, per-table filters, Upsert, background execution and cancellation rollback.
• Bounded MySQL LOAD DATA and PostgreSQL COPY pipelines passed full-field verification in four 10-million-row transfers: 45.75–121.81 seconds and 26.34–40.62 MiB sampled peak RSS of the test process.
• Added MySQL schema comparison and synchronization with difference review, SQL preview and deployment.
• Unified desktop/MCP credential authorization to reduce repeated Keychain prompts, with improved MCP installation progress and compatibility feedback.
• Improved dark editor backgrounds and transfer presentation; simplified both READMEs around capabilities and measured performance.

发布范围 / Release scope

组件 / Component	决定 / Decision
主程序 / App	0.1.11 (21)，Intel / Apple Silicon DMG，Universal Sparkle ZIP
MCP	0.1.1 (2)，凭据授权及运行时变化；双架构独立包 / credential and runtime changes, both architectures
Skill	保持 1.0.0 (1)，无实现变化，不重新发布 / unchanged, no republication
MySQL	1.0.7 (8)，原生通道与共享 transport；双架构 / native pipeline and shared transport, both architectures
PostgreSQL	1.0.6 (8)，COPY 与持续读取；双架构 / COPY and streaming reads, both architectures
Doris	1.0.7 (8)，持续读取、类型转换及共享 transport；双架构 / streaming, type conversion and shared transport, both architectures
Redis / Elasticsearch / Kafka	保持 1.0.1 (2)，无实现、依赖或适用打包变化，不重新发布 / unchanged, no republication
Driver API	保持 5；新增可选能力，旧协议表不变 / remains 5 with additive optional capabilities

新三类驱动最低主程序为 0.1.11，避免旧主程序加载其缺失的新符号。MySQL/Doris 使用独立模块名的 MariaDBTransportV2，验证了单独、同时及独立升级加载。MCP 0.1.1 最低主程序为 0.1.11；Skill 保持对 MCP 0.1.x 的兼容。
The three new driver packages require desktop 0.1.11, preventing older hosts from loading missing symbols. MariaDBTransportV2 supports independent MySQL/Doris upgrades. MCP 0.1.1 requires desktop 0.1.11; the unchanged Skill supports MCP 0.1.x.

验证 / Validation

本地 Intel 原生通道通过 45 项回归、四方向实库边界、百万行追加与 Upsert、四方向千万行及六项取消回滚，逐字段校验零差异。六类驱动加载、关闭 LOCAL 与 TEMP 权限不足时回退、三组 Doris/新旧 MySQL 混装均已验证。基准为本地 Docker 的五列混合类型、每批 1000 行、各容器 4 CPU / 2 GiB；耗时包含执行复核及提交，不包含夹具生成与结果校验；RSS 按秒采样，不代表完整 App 总内存，性能依赖硬件、表结构和网络。
Doris 已做来源小样本实库验证，未做千万行；MariaDB 服务端未实测。Redis/Elasticsearch/Kafka 不适用本次关系表通道。未进行物理鼠标/键盘验收。

Local Intel validation covers 45 native-transfer regressions, four-direction live edge cases, million-row append/Upsert, four 10-million-row transfers and six cancellation/rollback cases with no field differences. Six-driver loading, disabled LOCAL, denied TEMP and three Doris/mixed-version combinations passed. Measurements use five mixed-type columns, 1,000-row batches and local Docker containers capped at 4 CPUs / 2 GiB each; execution checks and commit are included, fixture generation and final verification excluded. RSS is sampled once per second for the test harness, not the whole application.
Doris received live small-sample source testing, not a 10-million-row benchmark; a MariaDB server was not tested. Redis/Elasticsearch/Kafka are outside the relational transfer scope. No physical-input UI acceptance is claimed.

整合 main 后的 227 项 Release 回归全部通过（0 失败、0 跳过），Release 主程序构建通过，15 项发版范围测试通过。线上六类驱动的 12 个架构包已核对摘要、大小、包内版本及 API 5。Intel 独立 Release MCP 包通过重定位签名、依赖路径、stdio/HTTP、六驱动及新旧 MySQL/Doris 混装验证；Actions 对两个架构设置相同的发布前阻断检查。安装生命周期的本地 HTTP 夹具使用 Debug，Release 保留 HTTPS 下载限制。

The merged main branch passed 227 Release regressions (zero failures/skips), the Release build and 15 release-scope checks. All 12 existing architecture-specific driver archives were verified against hashes, sizes, bundle versions and API 5. The Intel standalone Release MCP passed relocated signatures/dependencies, stdio/HTTP, six-driver loading and mixed MySQL/Doris upgrades. Actions gates publication on the same native runtime checks for both architectures. Loopback HTTP lifecycle fixtures use Debug; Release retains HTTPS-only component downloads.

Debug 隔离夹具另通过真实限速下载/未知长度进度、校验失败与取消重试、签名目录与 ZIP 校验、独立 MCP/Skill 安装、兼容回退、稳定入口、CLI 更新、旧 stdio 会话继续真实工具调用、自检失败恢复、签名拒绝、降级拒绝、跨进程锁、显式回退和 Skill 本地修改保护。未启用会注册系统后台服务的 launchd 验收。
The isolated Debug lifecycle fixture also passed throttled/unknown-length downloads, checksum and cancellation recovery, signed catalog/ZIP validation, independent installs, compatibility fallback, stable launchers, CLI updates, live old-session tool calls, failed self-test recovery, signature/downgrade rejection, cross-process locking, explicit rollback and local Skill edit protection. Persistent launchd registration checks were not enabled.