@kin-tio/cli 0.6.0

package/.env.example

@@ -0,0 +1,46 @@
+# `kintio setup` installs this template as <instance>/.env with mode 0600.
+# Relative file paths resolve from that instance directory.
+PORT=8888
+# Fill all four WECOM values only when the WeChat KF channel is enabled.
+# Leave them empty for an existing-account iLink-only deployment.
+WECOM_CALLBACK_TOKEN=
+WECOM_ENCODING_AES_KEY=
+
+WECOM_CORP_ID=
+WECOM_KF_SECRET=
+
+# Codex is denied for every conversation user until IDs are explicitly allowlisted.
+# Use a comma-separated list such as wm_user_a,wm_user_b.
+# Wildcards are rejected; every entry must be an explicit external_userid.
+WECOM_ALLOWED_USER_IDS=
+
+# Optional self-authorization. Disabled while the trigger is empty.
+# An unauthorized user must send the exact trigger as consecutive messages.
+WECOM_AUTH_TRIGGER=
+WECOM_AUTH_TRIGGER_COUNT=3
+WECOM_AUTH_CONFIRMATION=Code accepted. You can continue the conversation.
+
+# Optional runtime settings.
+# WECOM_RECEIVE_ID defaults to WECOM_CORP_ID.
+# KINTIO_DB_FILE=./data/kintio.sqlite
+# Legacy TALKFERRY_DB_FILE, HARNESS_DB_FILE, and WECOM_DB_FILE aliases remain supported.
+# WECOM_API_TIMEOUT_MS=10000
+# WECOM_MCP_OBSERVE_MS=5000
+# SHUTDOWN_TIMEOUT_MS=10000
+
+# Optional Weixin iLink channel. Generate a 32-byte base64url key and keep it in
+# the deployment secret store; Bot and context tokens are encrypted with it.
+ILINK_ENABLED=false
+# Prefer a deployment-secret value. If omitted, the service creates a private
+# 0600 key file beside SQLite; never register that key with a chat Agent.
+# ILINK_STORAGE_KEY=replace_with_43_character_base64url_key
+# ILINK_STORAGE_KEY_FILE=./data/ilink-storage.key
+# ILINK_BASE_URL=https://ilinkai.weixin.qq.com/
+# ILINK_API_TIMEOUT_MS=15000
+# ILINK_LONG_POLL_TIMEOUT_MS=35000
+# ILINK_MAX_ACCOUNTS=20
+
+# Codex CLI app-server uses the existing local Codex login.
+CODEX_ENABLED=true
+# CODEX_IMAGE_TMP_DIR=./data/codex-input
+# CODEX_WORKING_DIRECTORY=./codex-workspace

package/CHANGELOG.md

@@ -0,0 +1,95 @@
+# Changelog
+
+This file records important user-visible changes after the first public release.
+
+## Unreleased
+
+## 0.6.0 - 2026-08-31
+
+- Published the global `kintio` command as `@kin-tio/cli` through the public
+  npm Registry and added exact tarball and clean Registry-install verification
+  ([#37](https://github.com/Gkxie/kintio/issues/37)).
+- Disabled persisted Codex Goals and multi-agent tools inside untrusted channel
+  sessions so conversation work cannot outlive its bounded turn or expand into
+  background Agent execution
+  ([#38](https://github.com/Gkxie/kintio/issues/38)).
+- Made `~/.kintio` the single default mutable instance root for global and
+  direct Worker entry points, hardened foreground and daemon-first crash cleanup,
+  and constrained Windows-owned state to the selected Profile instance without
+  restricting the Agent project directory
+  ([#32](https://github.com/Gkxie/kintio/issues/32)).
+- Made one Worker-owned persistence root the only production owner of the raw
+  SQLite connection; Runtime, channels, MCP, and Agent code now consume JS/TS
+  state facades instead of a public database handle
+  ([#29](https://github.com/Gkxie/kintio/issues/29)).
+- Installed and refreshed the managed conversation Skill in the effective
+  configured Agent workspace, so a custom `CODEX_WORKING_DIRECTORY` cannot
+  leave a dangling session-level Skill reference
+  ([#30](https://github.com/Gkxie/kintio/issues/30)).
+- Moved MCP actions off HTTP entirely: Codex now starts true stdio relays backed
+  by a private Unix-domain socket or Windows named pipe, with no MCP TCP port or
+  static URL/Bearer configuration. The Codex adapter continues to inherit host
+  model, provider, reasoning, and search settings
+  ([#21](https://github.com/Gkxie/kintio/issues/21),
+  [#27](https://github.com/Gkxie/kintio/issues/27)).
+- Added macOS, Linux, and Windows lifecycle support with an authenticated native
+  daemon, bounded worker restarts, rotated logs, portable path and temporary-file
+  handling, and a three-system CI matrix
+  ([#19](https://github.com/Gkxie/kintio/issues/19)).
+- Removed duplicate post-merge CI, coverage artifact round trips, redundant
+  registry audits, and brittle repository-policy snapshots; retained the
+  executable security boundaries and made Agent subprocesses inherit the host
+  environment without copying Kintio configuration-file values into it
+  ([#16](https://github.com/Gkxie/kintio/issues/16)).
+- Made iLink activation explicit with `ILINK_ENABLED=true`, fixed an
+  authorization race that could defer an already-authorized message until
+  restart, and stopped opt-in tests and low-level Codex processes from
+  inheriting unrelated deployment credentials
+  ([#14](https://github.com/Gkxie/kintio/issues/14)).
+- Replaced the custom CLA parser and ledger writer with the immutable,
+  SHA-pinned CLA Assistant Lite workflow used by OpenAI Codex, while retaining
+  public signature records in the protected `cla-signatures` branch
+  ([#11](https://github.com/Gkxie/kintio/issues/11)).
+
+## 0.5.0 - 2026-08-30
+
+- Added a global `kintio` command with secure setup, foreground execution, and
+  PM2-backed start, stop, restart, status, and log operations
+  ([#5](https://github.com/Gkxie/kintio/pull/5)).
+- Separated installed program files from instance configuration, SQLite state,
+  temporary media, and the Agent workspace under `~/.kintio` by default.
+- Made an application Supervisor the process composition root; Hono now remains
+  an HTTP callback and MCP channel beside polling and future WebSocket inputs.
+- Rendered optional iLink login invitations as branded QR cards with an explicit
+  five-minute validity notice
+  ([#6](https://github.com/Gkxie/kintio/pull/6)).
+
+## 0.4.1 - 2026-08-30
+
+- Removed wildcard WeChat authorization; `WECOM_ALLOWED_USER_IDS` now accepts
+  explicit `external_userid` values only.
+- Removed the unused `/healthz` endpoint; process state and the Hono startup log
+  remain the supported local liveness signals.
+
+## 0.4.0 - 2026-08-29
+
+- Authorized channel users can assign work to a Codex Agent and receive results
+  in the originating conversation.
+- Added WeChat Customer Service API and independent Weixin iLink Bot
+  conversations.
+- Added text and image input, with text, image, link, mini-program, and location
+  delivery according to each adapter's capabilities.
+- New user instructions steer the active Agent turn instead of receiving stale
+  answers in sequence.
+- SQLite recovery resumes missed and unfinished messages after restart while
+  prioritizing live inbound traffic.
+- Channel identities, Threads, media, and reply windows are isolated, and
+  provider secrets are not exposed to the Agent.
+- Adopted the channel-neutral Kintio identity, English canonical documentation,
+  and one concise Simplified Chinese entry page.
+- Added Hono lifecycle management, PM2 deployment guidance, SQLite durability,
+  and compatibility paths for existing deployments.
+- Added deterministic unit, integration, recovery, and security tests with
+  coverage, TypeScript, dependency, secret, and CodeQL checks.
+- Added repository-native CLA enforcement, contributor accountability,
+  release provenance checks, and an abuse-response runbook.

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

@@ -0,0 +1,150 @@
+<div align="center">
+
+# Kintio
+
+**Connect chat channels to an Agent you control.**
+
+English | [简体中文](https://github.com/Gkxie/kintio/blob/master/README.zh-CN.md)
+
+[![CI](https://github.com/Gkxie/kintio/actions/workflows/ci.yml/badge.svg)](https://github.com/Gkxie/kintio/actions/workflows/ci.yml)
+[![CodeQL](https://github.com/Gkxie/kintio/actions/workflows/codeql.yml/badge.svg)](https://github.com/Gkxie/kintio/actions/workflows/codeql.yml)
+[![Latest release](https://img.shields.io/github/v/release/Gkxie/kintio?display_name=tag)](https://github.com/Gkxie/kintio/releases/latest)
+[![License](https://img.shields.io/github/license/Gkxie/kintio)](https://github.com/Gkxie/kintio/blob/master/LICENSE)
+
+</div>
+
+Deploy Kintio next to an Agent runtime and authorized people can assign work,
+steer an active task, and receive results without leaving their chat app. Kintio
+connects each
+conversation to the Agent while keeping identities, state, and reply capabilities scoped to
+the originating channel. The current runtime uses the Codex CLI session on the deployment
+host.
+
+```text
+Chat: "Investigate this"  -> Kintio starts a task in the Agent on your machine
+Chat: "Focus on the logs" -> Kintio steers that running task
+Agent result              -> Kintio delivers it back to the same chat
+```
+
+## What it provides
+
+- A separate Agent thread for every adapter identity, with no implicit identity or history
+  merging across channels.
+- Steering for active work: a user's follow-up can redirect the current Agent turn instead
+  of waiting behind stale instructions.
+- A durable SQLite inbox, restart recovery, and live-message priority over backlog recovery.
+- One application Supervisor for HTTP callbacks, polling listeners, and future long-lived
+  channel transports; Hono is an adapter rather than the process lifecycle owner.
+- Session-scoped MCP actions that cannot choose another recipient or expose provider
+  credentials, raw user identifiers, or database paths to the Agent.
+- Explicit delivery outcomes: accepted, failed, or uncertain. Uncertain sends are not
+  blindly retried.
+
+One deployment currently shares one Agent runtime login. Conversation state is isolated,
+but Kintio is not yet a multi-tenant platform where each chat user supplies independent
+Agent credentials, quotas, or working directories.
+
+## Current adapters
+
+| Adapter | Inbound | Outbound | Transport | Conversation identity |
+| --- | --- | --- | --- | --- |
+| WeChat KF API | Text and images; other message types become explicit summaries | Text, images, links, Mini Programs, and locations | Public HTTPS callback | `open_kfid + external_userid` |
+| Weixin iLink | Text and images; other message types become explicit summaries | Text and images | Long polling after QR-code binding | `bot_id + user_id` |
+
+Adapter capabilities are enforced per conversation. For example, an image received in one
+conversation can only be referenced by the short-lived MCP session bound to that same
+conversation.
+
+## Quick start
+
+Prerequisites:
+
+- Node.js 24 or later;
+- an installed and authenticated Codex CLI;
+- credentials for at least one supported adapter.
+
+```bash
+npm install --global @kin-tio/cli
+kintio setup
+codex login status
+```
+
+`kintio setup` creates a private instance under `~/.kintio`, installs the bundled Agent
+skill, and writes the channel configuration template. POSIX systems use mode `0600`;
+Windows keeps the instance inside the current user's profile. No adapter is enabled
+by default. Follow the [setup guide](https://github.com/Gkxie/kintio/blob/master/docs/setup.md)
+and edit `~/.kintio/.env` to configure one adapter:
+
+- For WeChat KF API, set its callback token, EncodingAESKey, CorpID, and secret. A temporary
+  `WECOM_AUTH_TRIGGER` can authorize the first user without knowing their
+  `external_userid` in advance.
+- For an existing Weixin iLink binding, set `ILINK_ENABLED=true`. Creating a new binding
+  currently starts from an authorized WeChat KF conversation.
+
+Start Kintio:
+
+```bash
+kintio start
+kintio status
+kintio logs --lines 100
+```
+
+After startup, confirm that `kintio logs` contains `Hono server is listening on port 8888`.
+Complete the callback or binding checks described in the setup guide before sending traffic.
+Use `kintio run` when a foreground process is preferable to the native daemon.
+Existing source-based deployments can keep their current state after the one-time
+process-manager migration described in the setup guide.
+
+Source builds and contributor setup are documented in
+[CONTRIBUTING.md](https://github.com/Gkxie/kintio/blob/master/CONTRIBUTING.md).
+
+## Security boundaries
+
+- `.env`, SQLite databases, downloaded media, and local key files are ignored by Git and
+  must never be force-added.
+- Kintio does not inject messaging-adapter secrets, stable user identifiers, raw media IDs,
+  or database paths into the Agent; host Agent credentials remain host-managed.
+- Codex starts MCP over stdio. Kintio uses only a private Unix-domain socket or
+  Windows named pipe behind that process boundary, never an MCP TCP port or public
+  Hono route; every action still requires a short-lived conversation capability.
+- Project-level Agent capability restrictions are not an operating-system sandbox. Use a
+  dedicated system account and additional isolation appropriate to the Agent's real powers.
+- A provider accepting an outbound request does not prove that a client displayed it;
+  uncertain outcomes remain explicit to avoid duplicate delivery.
+
+See the [security policy](https://github.com/Gkxie/kintio/blob/master/SECURITY.md) for the complete trust boundary and private
+vulnerability-reporting process.
+
+## Documentation and contributing
+
+- [Setup guide](https://github.com/Gkxie/kintio/blob/master/docs/setup.md) — configuration through the first Agent reply.
+- [Architecture](https://github.com/Gkxie/kintio/blob/master/docs/architecture.md) — message flow, module boundaries, identity
+  isolation, and source entry points.
+- [Roadmap](https://github.com/Gkxie/kintio/blob/master/ROADMAP.md) — long-term direction and `0.x` priorities.
+- [Contributing guide](https://github.com/Gkxie/kintio/blob/master/CONTRIBUTING.md) — where to start and how to validate changes.
+- [Maintainer guide](https://github.com/Gkxie/kintio/blob/master/MAINTAINING.md) — issue, pull request, and release operations.
+- [Code of Conduct](https://github.com/Gkxie/kintio/blob/master/CODE_OF_CONDUCT.md), [Changelog](CHANGELOG.md), and
+  [Apache License 2.0](https://github.com/Gkxie/kintio/blob/master/LICENSE).
+
+The default verification entry point is:
+
+```bash
+pnpm test
+```
+
+Tests use temporary SQLite databases and simulated provider and Agent boundaries by
+default. They contact real services only when explicit live-test flags, targets, and
+allowlists are supplied.
+
+## Project status
+
+Kintio is in the `0.x` stage. It currently ships the two adapters listed above while the
+channel, identity, recovery, and Agent-runtime contracts are stabilized for future
+adapters.
+
+The Weixin iLink protocol implementation incorporates work described in
+[THIRD_PARTY_NOTICES](https://github.com/Gkxie/kintio/blob/master/THIRD_PARTY_NOTICES).
+
+Kintio is an independent open-source project. It is not affiliated with, authorized by,
+endorsed by, or an official product of Tencent, WeChat, Weixin, or any other channel
+provider.

package/README.zh-CN.md

@@ -0,0 +1,79 @@
+<div align="center">
+
+# Kintio
+
+**把聊天通道连接到你掌控的 Agent。**
+
+[English](README.md) | 简体中文
+
+</div>
+
+这是本项目唯一的中文入口。详细文档、贡献流程与版本说明统一以英文维护。
+
+把 Kintio 部署在运行 Agent 的机器上，授权用户就能在微信等受支持的聊天入口中直接下达
+任务、补充或改变指令，并在原会话中收到结果。Kintio 负责连接聊天与 Agent，同时隔离不同
+通道的身份、状态和回复能力；当前 Agent Runtime 使用部署主机上已经登录的 Codex CLI。
+
+## 核心能力
+
+- 每个适配器身份使用独立 Agent Thread，不跨通道合并身份或历史。
+- 用户补充指令时可以调整正在执行的任务，避免旧指令排队产生过时回复。
+- SQLite Inbox 支持重启恢复，并优先处理实时消息。
+- 应用 Supervisor 统一管理 HTTP 回调、轮询监听和未来长连接通道；Hono 只是 HTTP 适配器，
+  不是进程生命周期入口。
+- MCP 动作只作用于当前会话，不向 Agent 暴露渠道密钥、原始用户标识或数据库路径。
+- 投递结果明确区分已受理、失败和不确定；结果不确定时不会盲目重发。
+
+目前一套部署共享一份 Agent Runtime 登录态，不是每个聊天用户绑定独立 Agent 凭据、额度和
+工作目录的多租户平台。
+
+## 当前适配器
+
+| 适配器 | 接收 | 发送 | 接入方式 |
+| --- | --- | --- | --- |
+| WeChat KF API | 文字、图片；其他类型转为明确摘要 | 文字、图片、链接、小程序、位置 | 公网 HTTPS 回调 |
+| Weixin iLink | 文字、图片；其他类型转为明确摘要 | 文字、图片 | 扫码绑定后长轮询 |
+
+## 最小启动步骤
+
+需要 Node.js 24+、已安装并登录的 Codex CLI，以及至少一个
+受支持适配器的凭据。
+
+```bash
+npm install --global @kin-tio/cli
+kintio setup
+codex login status
+```
+
+`kintio setup` 会在 `~/.kintio` 创建私有实例目录、安装内置 Agent Skill，并生成渠道配置
+模板 `.env`。macOS/Linux 使用 `0600`，Windows 则限定在当前用户目录的 ACL
+边界内。默认不启用任何适配器；请按英文
+[部署指南](https://github.com/Gkxie/kintio/blob/master/docs/setup.md)配置 WeChat KF API，或为已有 Weixin iLink 绑定设置
+`ILINK_ENABLED=true`。
+
+```bash
+kintio start
+kintio status
+kintio logs --lines 100
+```
+
+启动后应确认 `kintio logs` 包含 `Hono server is listening on port 8888`；投入使用前仍需按
+部署指南完成回调或绑定验证。需要前台进程时使用 `kintio run`；现有源码目录部署可以在完成
+部署指南中的一次性进程管理器迁移后，继续使用原数据库和配置。
+源码构建与贡献者开发环境见英文
+[贡献指南](https://github.com/Gkxie/kintio/blob/master/CONTRIBUTING.md)。
+
+## 英文文档
+
+- [Setup guide](https://github.com/Gkxie/kintio/blob/master/docs/setup.md)：配置到收到第一条 Agent 回复。
+- [Architecture](https://github.com/Gkxie/kintio/blob/master/docs/architecture.md)：消息链路、模块边界与身份隔离。
+- [Roadmap](https://github.com/Gkxie/kintio/blob/master/ROADMAP.md)：长期方向和 `0.x` 优先级。
+- [Contributing guide](https://github.com/Gkxie/kintio/blob/master/CONTRIBUTING.md)：参与方式与验证要求。
+- [Security policy](https://github.com/Gkxie/kintio/blob/master/SECURITY.md)：信任边界与私密漏洞报告。
+- [Changelog](CHANGELOG.md)：用户可观察的版本变化。
+
+Kintio 处于 `0.x` 阶段，使用 [Apache License 2.0](LICENSE)。Weixin iLink 协议实现所涉及的
+第三方归属和许可证见 [THIRD_PARTY_NOTICES](THIRD_PARTY_NOTICES)。
+
+Kintio 是独立开源项目，与腾讯、微信、Weixin 及其他通道提供方不存在隶属、授权、背书
+或官方代表关系。

package/THIRD_PARTY_NOTICES

@@ -0,0 +1,31 @@
+Third-Party Notices
+===================
+
+This project includes protocol definitions adapted from and an independently
+rewritten media flow based on @tencent-weixin/openclaw-weixin 2.4.6:
+https://github.com/Tencent/openclaw-weixin
+
+Tencent is pleased to support the open source community by making
+openclaw-weixin available.
+
+Copyright (C) 2026 Tencent. All rights reserved.
+
+openclaw-weixin is licensed under the MIT License:
+
+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/bin/kintio.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+
+await import('../dist/cli.js');