luckytri 1.0.0 → 1.0.2

package/public/guide.en.html

@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width,initial-scale=1" />
-    <title>LuckyTri v1.0.0 · Getting Started</title>
+    <title>LuckyTri v1.0.2 · Getting Started</title>
     <style>
       * {
         box-sizing: border-box;
@@ -269,7 +269,7 @@
   <body>
     <header>
       <div>
-        <b>LuckyTri · Handbook</b><small>TIME · MEMORY · CHOICE / v1.0.0</small>
+        <b>LuckyTri · Handbook</b><small>TIME · MEMORY · CHOICE / v1.0.2</small>
       </div>
       <nav>
         <a href="/#setup">Back to the studio</a
@@ -281,7 +281,8 @@
     <div class="layout">
       <nav class="toc" aria-label="Guide contents">
         <p>CONTENTS</p>
-        <a href="#step-1">1. Start</a><a href="#step-2">2. Local tokens</a
+        <a href="#step-1">1. Start</a
+        ><a href="#step-2">2. Set your management password</a
         ><a href="#step-3">3. Try it in simulation mode first</a
         ><a href="#step-4">4. Connect a model</a
         ><a href="#step-5">5. Connect QQ</a
@@ -320,17 +321,11 @@ luckytri
           WebUI. The experimental-SQLite notice does not mean the start failed.
         </p>
         <p>
-          Use <code>luckytri paths</code> to find <code>.env</code>, open it in
-          a local editor and enter <code>ADMIN_TOKEN</code> in the studio.
-          <code>luckytri --no-browser</code> launches without opening a browser,
-          <code>luckytri start</code> runs in the foreground, and
-          <code>luckytri stop</code> stops the service. Update with
-          <code>luckytri stop</code>,
-          <code>npm install -g luckytri@latest</code>, then
-          <code>luckytri</code>. Your configuration and data stay intact.
-          Default directories are listed in the
-          <a href="../../README.en.md#configuration-data-and-privacy">README</a
-          >.
+          Set a password in the studio on your first visit. Use
+          <code>luckytri --no-browser</code>, <code>luckytri start</code> and
+          <code>luckytri stop</code> for background, foreground and stop. Update
+          with stop, <code>npm install -g luckytri@latest</code>, then launch;
+          password, configuration and data stay intact.
         </p>
         <p>
           For source development, run <code>npm install</code>,
@@ -451,80 +446,17 @@ luckytri
           mind. On a phone the navigation sits at the bottom and the other
           entries are under &quot;More&quot;.
         </p>
-        <h2 id="step-2">2. Local tokens</h2>
+        <h2 id="step-2">2. Set your management password</h2>
         <p>
-          Configuration is created on first launch. You can also initialize in
-          advance:
+          On the first visit, choose and confirm a password of at least 8
+          characters. Use it to sign in later; no environment-file token is
+          needed. Browser sessions are remembered, and updates or reinstalls
+          preserve the password.
         </p>
-        <pre><code class="language-powershell">luckytri setup
-luckytri paths
-</code></pre>
-        <p>
-          When there is no <code>.env</code>, setup writes an admin token and an
-          OneBot connection token. An existing <code>.env</code> is kept as it
-          is.
-        </p>
-        <pre><code class="language-dotenv">HOST=127.0.0.1
-PORT=3210
-ADMIN_TOKEN=
-ONEBOT_TOKEN=
-LLM_API_KEY=
-</code></pre>
-        <table>
-          <thead>
-            <tr>
-              <th>Field</th>
-              <th>Purpose</th>
-            </tr>
-          </thead>
-          <tbody>
-            <tr>
-              <td><code>ADMIN_TOKEN</code></td>
-              <td>
-                Opens LuckyTri and calls the HTTP API; the stop command uses it
-                too
-              </td>
-            </tr>
-            <tr>
-              <td><code>ONEBOT_TOKEN</code></td>
-              <td>
-                The OneBot 11 connector uses it for
-                <code>/onebot/v11/ws</code> (only needed for OneBot)
-              </td>
-            </tr>
-            <tr>
-              <td><code>LLM_API_KEY</code></td>
-              <td>
-                Optional; when set it takes precedence over the model key saved
-                in LuckyTri
-              </td>
-            </tr>
-            <tr>
-              <td><code>LUCKYTRI_CHANNEL</code></td>
-              <td>
-                Optional; <code>onebot</code> or <code>qqbot</code>. When set,
-                the connection method cannot be changed in the interface
-              </td>
-            </tr>
-            <tr>
-              <td><code>QQBOT_APP_ID</code> / <code>QQBOT_APP_SECRET</code></td>
-              <td>
-                Optional; credentials of the QQ official bot, they take
-                precedence over what is saved in the interface
-              </td>
-            </tr>
-            <tr>
-              <td><code>HOST</code> / <code>PORT</code></td>
-              <td>Listen address and port; keep the defaults for local use</td>
-            </tr>
-          </tbody>
-        </table>
         <p>
-          The first time the page loads data it asks for
-          <code>ADMIN_TOKEN</code>. The token stays in the current tab only.
-          Restart after changing <code>.env</code>. Never give
-          <code>ADMIN_TOKEN</code> to the QQ connector, and do not treat
-          <code>ONEBOT_TOKEN</code> as the studio password.
+          Change the password or sign out under System → Run switches. Only a
+          salted verification digest is stored. Existing environment
+          configuration and model keys remain intact.
         </p>
         <h2 id="step-3">3. Try it in simulation mode first</h2>
         <p>Simulation mode is on by default, so nothing is sent to QQ.</p>
@@ -632,8 +564,8 @@ LLM_API_KEY=
         </p>
         <ol>
           <li>
-            Set <code>ONEBOT_TOKEN</code> in the local <code>.env</code> and
-            restart LuckyTri.
+            Local clients need no separate token. Keep an existing client
+            address and QQ sign-in.
           </li>
           <li>
             In the connector&#39;s own network settings add an OneBot 11 reverse
@@ -658,7 +590,10 @@ LLM_API_KEY=
             </tr>
             <tr>
               <td>Token</td>
-              <td><code>ONEBOT_TOKEN</code> from <code>.env</code></td>
+              <td>
+                Not needed locally; remote clients can use the management
+                password or an existing token
+              </td>
             </tr>
             <tr>
               <td>Message format</td>
@@ -677,11 +612,9 @@ LLM_API_KEY=
           </li>
         </ol>
         <p>
-          <code>3210</code> is LuckyTri&#39;s port. When the connector and
-          LuckyTri are on different machines or in containers,
-          <code>127.0.0.1</code> points at each own environment: replace it with
-          LuckyTri&#39;s real address and configure
-          <code>ADMIN_TOKEN</code> first.
+          In a container or another computer, localhost refers to that
+          environment. Use the reachable LuckyTri address for remote access, set
+          the password locally first, and use HTTPS for remote studio access.
         </p>
         <h3>Option two: QQ official bot</h3>
         <p>
@@ -926,6 +859,46 @@ npm start
           and restores it into a brand new file; see
           <code>docs/en/recovery.md</code>.
         </p>
+        <h3>Import and export from the studio</h3>
+        <p>
+          &quot;System → Data and backups&quot; provides &quot;Export data
+          package&quot; and &quot;Choose import file&quot;. A
+          <code>.luckytri</code> package contains chats, memories,
+          relationships, personal state, diaries, tasks, work versions,
+          knowledge text and settings stored in the database, including saved
+          credentials. Management passwords and login sessions are not migrated.
+          Plugin programs, original knowledge files and the local
+          <code>.env</code> are outside the package. Export uses a consistent
+          snapshot while the instance continues running and streams large
+          downloads.
+        </p>
+        <p>
+          Imports accept <code>.luckytri</code> packages and existing
+          <code>.db</code> / SQLite backups. The default upload limit is 10 GiB;
+          adjust <code>DATA_TRANSFER_MAX_GB</code> (1–100) in <code>.env</code>.
+          Uploads are checked for package SHA-256, database integrity,
+          references and supported structures. Older versions are upgraded only
+          in staging. The preview shows the name, version and record counts
+          before current data changes, so it can be cancelled.
+        </p>
+        <p>
+          Confirming &quot;Import and restart&quot; stops the instance, retains
+          a complete <code>luckytri-before-import-*.db</code> snapshot, replaces
+          the data and restarts automatically. The local management password,
+          current logins, QQ connection settings and backup cleanup rules are
+          preserved. Automatic replies are turned off and plugin execution
+          grants reset. Review connections, models and tasks before enabling
+          replies; reinstall plugins or review their permissions. Import
+          replaces the whole database rather than merging records. Pre-import
+          snapshots can be managed manually and are excluded from scheduled
+          full-backup cleanup.
+        </p>
+        <p>
+          The server removes the export copy after download. Cancelled, expired
+          and interrupted staging files are reclaimed; unused previews expire
+          after one hour. Failed imports retain or restore the original database
+          rather than starting with a partial file.
+        </p>
         <h2 id="step-9">9. Troubleshooting</h2>
         <table>
           <thead>
@@ -949,17 +922,17 @@ npm start
               </td>
             </tr>
             <tr>
-              <td>Wrong token</td>
+              <td>Incorrect password</td>
               <td>
-                Use <code>ADMIN_TOKEN</code>; restart after editing
-                <code>.env</code>
+                Sign in with your management password; change it under System →
+                Run switches
               </td>
             </tr>
             <tr>
               <td>OneBot not connected</td>
               <td>
-                Is the connector logged in; do the URL, port, path and
-                <code>ONEBOT_TOKEN</code> all match
+                Check sign-in, enabled reverse client, address, port and path;
+                local clients need no token
               </td>
             </tr>
             <tr>
@@ -1047,7 +1020,7 @@ npm start
     </div>
     <footer>
       LuckyTri · so that experience and choice stay coherent. This guide matches
-      the v1.0.0 interface.
+      the v1.0.2 interface.
     </footer>
   </body>
 </html>

package/public/guide.html

@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width,initial-scale=1" />
-    <title>LuckyTri v1.0.0 · 使用教程</title>
+    <title>LuckyTri v1.0.2 · 使用教程</title>
     <style>
       * {
         box-sizing: border-box;
@@ -269,7 +269,7 @@
   <body>
     <header>
       <div>
-        <b>LuckyTri · 上手手册</b><small>TIME · MEMORY · CHOICE / v1.0.0</small>
+        <b>LuckyTri · 上手手册</b><small>TIME · MEMORY · CHOICE / v1.0.2</small>
       </div>
       <nav>
         <a href="/#setup">返回管理台</a
@@ -283,7 +283,7 @@
     <div class="layout">
       <nav class="toc" aria-label="教程目录">
         <p>CONTENTS</p>
-        <a href="#step-1">1. 启动</a><a href="#step-2">2. 本机令牌</a
+        <a href="#step-1">1. 启动</a><a href="#step-2">2. 设置管理密码</a
         ><a href="#step-3">3. 先在模拟模式试聊</a
         ><a href="#step-4">4. 连接模型</a><a href="#step-5">5. 连接 QQ</a
         ><a href="#step-6">6. 让 TA 参与会话</a
@@ -315,21 +315,13 @@ luckytri
           实验性提示不表示启动失败，以能否打开 LuckyTri 为准。
         </p>
         <p>
-          运行 <code>luckytri paths</code> 查看本机
-          <code>.env</code>，在本机编辑器中取得
-          <code>ADMIN_TOKEN</code> 并填入管理台。<code
-            >luckytri --no-browser</code
-          >
+          首次进入管理台时设置一个密码即可。<code>luckytri --no-browser</code>
           只后台启动，<code>luckytri start</code> 前台运行，<code
             >luckytri stop</code
           >
           停止服务。更新使用 <code>luckytri stop</code> →
           <code>npm install -g luckytri@latest</code> →
-          <code>luckytri</code>，配置与数据会保留；默认目录见
-          <a
-            href="../../README.md#%E9%85%8D%E7%BD%AE%E6%95%B0%E6%8D%AE%E4%B8%8E%E9%9A%90%E7%A7%81"
-            >README</a
-          >。
+          <code>luckytri</code>，密码、配置与数据会保留。
         </p>
         <p>
           从源码开发时，在仓库中执行 <code>npm install</code>、<code
@@ -430,66 +422,16 @@ luckytri
           戳一下会回应一句，按住是摸摸头，双击或点「聊聊」打开试聊；这些只是界面动画，不会改变
           TA 的心智。手机上导航在底部，其余入口在「更多」里。
         </p>
-        <h2 id="step-2">2. 本机令牌</h2>
-        <p>首次启动已生成配置；也可以提前初始化：</p>
-        <pre><code class="language-powershell">luckytri setup
-luckytri paths
-</code></pre>
+        <h2 id="step-2">2. 设置管理密码</h2>
         <p>
-          没有 <code>.env</code> 时，setup 会写入管理令牌和 OneBot
-          连接令牌。已有 <code>.env</code> 会原样保留。
+          首次打开管理台时设置一个至少 8
+          个字符的密码，确认后进入。以后用同一个密码登录，不需要打开
+          <code>.env</code>
+          查找管理令牌。浏览器登录状态会保留；更新和重装不会重置密码。
         </p>
-        <pre><code class="language-dotenv">HOST=127.0.0.1
-PORT=3210
-ADMIN_TOKEN=
-ONEBOT_TOKEN=
-LLM_API_KEY=
-</code></pre>
-        <table>
-          <thead>
-            <tr>
-              <th>字段</th>
-              <th>用途</th>
-            </tr>
-          </thead>
-          <tbody>
-            <tr>
-              <td><code>ADMIN_TOKEN</code></td>
-              <td>打开 LuckyTri 和调用 HTTP API；停止命令也会使用</td>
-            </tr>
-            <tr>
-              <td><code>ONEBOT_TOKEN</code></td>
-              <td>
-                OneBot 11 接入端连接 <code>/onebot/v11/ws</code>（只用 OneBot
-                方式时需要）
-              </td>
-            </tr>
-            <tr>
-              <td><code>LLM_API_KEY</code></td>
-              <td>可选；非空时优先于 LuckyTri 里保存的模型密钥</td>
-            </tr>
-            <tr>
-              <td><code>LUCKYTRI_CHANNEL</code></td>
-              <td>
-                可选；<code>onebot</code> 或
-                <code>qqbot</code>。设置后在界面里不能更改连接方式
-              </td>
-            </tr>
-            <tr>
-              <td><code>QQBOT_APP_ID</code> / <code>QQBOT_APP_SECRET</code></td>
-              <td>可选；QQ 官方机器人的凭据，优先于界面里保存的</td>
-            </tr>
-            <tr>
-              <td><code>HOST</code> / <code>PORT</code></td>
-              <td>监听地址和端口；本机使用保持默认</td>
-            </tr>
-          </tbody>
-        </table>
         <p>
-          页面第一次取数据时会弹出窗口要求输入
-          <code>ADMIN_TOKEN</code>。令牌只留在当前标签页。修改
-          <code>.env</code> 后必须重启。不要把 <code>ADMIN_TOKEN</code> 填给 QQ
-          接入端，也不要把 <code>ONEBOT_TOKEN</code> 当成管理台密码。
+          在「系统 →
+          运行开关」可以修改密码或退出登录。密码只以加盐校验摘要保存，现有环境配置和模型密钥保留。
         </p>
         <h2 id="step-3">3. 先在模拟模式试聊</h2>
         <p>默认开启模拟模式，消息不会发到 QQ。</p>
@@ -571,10 +513,7 @@ LLM_API_KEY=
           接口，接入端需要你自行准备和管理。
         </p>
         <ol>
-          <li>
-            在本机 <code>.env</code> 中设置
-            <code>ONEBOT_TOKEN</code>，修改后重启 LuckyTri。
-          </li>
+          <li>本机连接无需单独令牌，保留已有的接入地址和 QQ 登录。</li>
           <li>
             在接入端自己的网络设置里添加 OneBot 11 反向 WebSocket 客户端：
           </li>
@@ -597,7 +536,7 @@ LLM_API_KEY=
             </tr>
             <tr>
               <td>Token</td>
-              <td><code>.env</code> 里的 <code>ONEBOT_TOKEN</code></td>
+              <td>本机无需填写；远程可使用管理密码，旧远程令牌仍兼容</td>
             </tr>
             <tr>
               <td>消息格式</td>
@@ -616,10 +555,9 @@ LLM_API_KEY=
           </li>
         </ol>
         <p>
-          这里的 <code>3210</code> 是 LuckyTri 的端口。接入端和 LuckyTri
-          不在同一台机器或放在容器里时，<code>127.0.0.1</code>
-          指向各自环境，需要改成 LuckyTri 的实际地址，并先配置
-          <code>ADMIN_TOKEN</code>。
+          容器或另一台电脑中的 <code>127.0.0.1</code> 指向自身。远程接入使用
+          LuckyTri 的可达地址，并先在本机设置管理密码；对外提供管理台时使用
+          HTTPS。
         </p>
         <h3>方式二：QQ 官方机器人</h3>
         <p>
@@ -793,6 +731,29 @@ npm start
           <code>npm run recovery</code> 校验并恢复到一个全新的文件，见
           <code>docs/zh/recovery.md</code>。
         </p>
+        <h3>从管理台导入与导出</h3>
+        <p>
+          「系统 → 数据与备份」提供「导出数据包」和「选择导入文件」。导出的
+          <code>.luckytri</code>
+          文件包含数据库内的聊天、记忆、关系、个人状态、日记、待办、作品版本、知识文本和设置，也包含保存在设置中的密钥。管理密码和登录会话不随数据包迁移；插件程序、知识库原始文件及本机
+          <code>.env</code>
+          不在其中。导出读取一致快照，实例可以继续运行，大文件通过流式传输下载。
+        </p>
+        <p>
+          导入支持 <code>.luckytri</code> 数据包及已有 <code>.db</code> / SQLite
+          备份。默认单个文件最多 10 GiB，可用 <code>.env</code> 中的
+          <code>DATA_TRANSFER_MAX_GB</code>（1–100）调整。上传后先校验数据包
+          SHA-256、数据库完整性、引用和结构，旧版本只在暂存副本上升级，界面会显示姓名、版本和记录数量。此时尚未改变当前数据，可以取消。
+        </p>
+        <p>
+          确认「导入并重启」后，程序停止实例，保留一份完整的
+          <code>luckytri-before-import-*.db</code>
+          快照，再替换数据并自动重启。本机管理密码、当前登录、QQ
+          连接配置和备份整理规则保留。导入后的自动回复关闭，插件执行权限重置；检查连接、模型和待办后可重新开启，插件需重新安装或确认权限。导入是替换整份数据，不与当前记录合并；原有快照可在备份列表手动管理，定时清理完整备份不会删除它。
+        </p>
+        <p>
+          下载完成后删除服务器导出副本；取消、失效或中断的暂存文件会回收，未使用的预览默认一小时失效。导入失败时保留或恢复原数据，不会把不完整的文件交给实例运行。
+        </p>
         <h2 id="step-9">9. 常见问题</h2>
         <table>
           <thead>
@@ -811,16 +772,13 @@ npm start
               <td>先 <code>npm run stop</code>，不要结束所有 node 进程</td>
             </tr>
             <tr>
-              <td>令牌错误</td>
-              <td>
-                使用 <code>ADMIN_TOKEN</code>；改 <code>.env</code> 后重启
-              </td>
+              <td>密码错误</td>
+              <td>使用首次设置的管理密码；可在系统运行开关中修改</td>
             </tr>
             <tr>
               <td>OneBot 未连接</td>
               <td>
-                接入端是否登录，URL、端口、路径和
-                <code>ONEBOT_TOKEN</code> 是否一致
+                确认接入端已登录、反向客户端启用、地址端口路径一致；本机无需额外令牌
               </td>
             </tr>
             <tr>
@@ -888,6 +846,6 @@ npm start
         <p>不要把 API 密钥、<code>.env</code> 或私聊原文发到公开位置。</p>
       </article>
     </div>
-    <footer>LuckyTri · 让经历和选择彼此连贯。教程与 v1.0.0 界面同步。</footer>
+    <footer>LuckyTri · 让经历和选择彼此连贯。教程与 v1.0.2 界面同步。</footer>
   </body>
 </html>

package/public/tutorial.en.md

@@ -16,7 +16,7 @@ luckytri
 
 LuckyTri starts in the background and opens <http://127.0.0.1:3210>, creating local configuration on the first run. The package includes the built WebUI. The experimental-SQLite notice does not mean the start failed.
 
-Use `luckytri paths` to find `.env`, open it in a local editor and enter `ADMIN_TOKEN` in the studio. `luckytri --no-browser` launches without opening a browser, `luckytri start` runs in the foreground, and `luckytri stop` stops the service. Update with `luckytri stop`, `npm install -g luckytri@latest`, then `luckytri`. Your configuration and data stay intact. Default directories are listed in the [README](../../README.en.md#configuration-data-and-privacy).
+Set a password in the studio on your first visit. Use `luckytri --no-browser`, `luckytri start` and `luckytri stop` for background, foreground and stop. Update with stop, `npm install -g luckytri@latest`, then launch; password, configuration and data stay intact.
 
 For source development, run `npm install`, `npm run setup`, `npm run build` and `npm start` in the checkout. Later examples using `npm run setup/stop/backup/recovery/plugin` apply to source checkouts; global users use the corresponding `luckytri setup/stop/backup/recovery/plugin` commands.
 
@@ -39,35 +39,11 @@ LuckyTri is "TA's little world". The left navigation has three groups and ten en
 
 The colors, sky and motion follow TA's mood and rhythm: warm when she is happy, grey-blue when she is low, night once she is asleep. At the bottom left you can pin one theme or turn on "Reduce motion". The small TA at the bottom right answers a poke, a long press is a head-pat, and a double click or "Chat" opens the trial chat. These are interface animations only and never change her mind. On a phone the navigation sits at the bottom and the other entries are under "More".
 
-## 2. Local tokens
+## 2. Set your management password
 
-Configuration is created on first launch. You can also initialize in advance:
+On the first visit, choose and confirm a password of at least 8 characters. Use it to sign in later; no environment-file token is needed. Browser sessions are remembered, and updates or reinstalls preserve the password.
 
-```powershell
-luckytri setup
-luckytri paths
-```
-
-When there is no `.env`, setup writes an admin token and an OneBot connection token. An existing `.env` is kept as it is.
-
-```dotenv
-HOST=127.0.0.1
-PORT=3210
-ADMIN_TOKEN=
-ONEBOT_TOKEN=
-LLM_API_KEY=
-```
-
-| Field                               | Purpose                                                                                                |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------ |
-| `ADMIN_TOKEN`                       | Opens LuckyTri and calls the HTTP API; the stop command uses it too                                    |
-| `ONEBOT_TOKEN`                      | The OneBot 11 connector uses it for `/onebot/v11/ws` (only needed for OneBot)                          |
-| `LLM_API_KEY`                       | Optional; when set it takes precedence over the model key saved in LuckyTri                            |
-| `LUCKYTRI_CHANNEL`                  | Optional; `onebot` or `qqbot`. When set, the connection method cannot be changed in the interface      |
-| `QQBOT_APP_ID` / `QQBOT_APP_SECRET` | Optional; credentials of the QQ official bot, they take precedence over what is saved in the interface |
-| `HOST` / `PORT`                     | Listen address and port; keep the defaults for local use                                               |
-
-The first time the page loads data it asks for `ADMIN_TOKEN`. The token stays in the current tab only. Restart after changing `.env`. Never give `ADMIN_TOKEN` to the QQ connector, and do not treat `ONEBOT_TOKEN` as the studio password.
+Change the password or sign out under System → Run switches. Only a salted verification digest is stored. Existing environment configuration and model keys remain intact.
 
 ## 3. Try it in simulation mode first
 
@@ -111,20 +87,20 @@ Open "System → Connect QQ". There are two options at the top: **OneBot 11** an
 
 LuckyTri only implements the reverse-WebSocket side of OneBot 11. You prepare and manage the connector yourself.
 
-1. Set `ONEBOT_TOKEN` in the local `.env` and restart LuckyTri.
+1. Local clients need no separate token. Keep an existing client address and QQ sign-in.
 2. In the connector's own network settings add an OneBot 11 reverse WebSocket client:
 
-| Item           | Value on this machine               |
-| -------------- | ----------------------------------- |
-| Protocol       | OneBot 11                           |
-| WebSocket URL  | `ws://127.0.0.1:3210/onebot/v11/ws` |
-| Token          | `ONEBOT_TOKEN` from `.env`          |
-| Message format | array                               |
-| Enabled        | on, then save                       |
+| Item           | Value on this machine                                                                   |
+| -------------- | --------------------------------------------------------------------------------------- |
+| Protocol       | OneBot 11                                                                               |
+| WebSocket URL  | `ws://127.0.0.1:3210/onebot/v11/ws`                                                     |
+| Token          | Not needed locally; remote clients can use the management password or an existing token |
+| Message format | array                                                                                   |
+| Enabled        | on, then save                                                                           |
 
 3. Log in to QQ in the connector. The account must already be in the target group; LuckyTri does not store QQ passwords.
 
-`3210` is LuckyTri's port. When the connector and LuckyTri are on different machines or in containers, `127.0.0.1` points at each own environment: replace it with LuckyTri's real address and configure `ADMIN_TOKEN` first.
+In a container or another computer, localhost refers to that environment. Use the reachable LuckyTri address for remote access, set the password locally first, and use HTTPS for remote studio access.
 
 ### Option two: QQ official bot
 
@@ -192,14 +168,24 @@ Cleanup verifies a retained automatic backup of this instance from the last 72 h
 
 To restore, stop the service, move the current `data/friend.db` and its `-wal` and `-shm` files away, then copy the chosen backup to `data/friend.db`. When `DB_PATH` is set, work on that path. Never keep an old WAL file next to a restored database. The safer way is `npm run recovery`, which verifies a backup and restores it into a brand new file; see `docs/en/recovery.md`.
 
+### Import and export from the studio
+
+"System → Data and backups" provides "Export data package" and "Choose import file". A `.luckytri` package contains chats, memories, relationships, personal state, diaries, tasks, work versions, knowledge text and settings stored in the database, including saved credentials. Management passwords and login sessions are not migrated. Plugin programs, original knowledge files and the local `.env` are outside the package. Export uses a consistent snapshot while the instance continues running and streams large downloads.
+
+Imports accept `.luckytri` packages and existing `.db` / SQLite backups. The default upload limit is 10 GiB; adjust `DATA_TRANSFER_MAX_GB` (1–100) in `.env`. Uploads are checked for package SHA-256, database integrity, references and supported structures. Older versions are upgraded only in staging. The preview shows the name, version and record counts before current data changes, so it can be cancelled.
+
+Confirming "Import and restart" stops the instance, retains a complete `luckytri-before-import-*.db` snapshot, replaces the data and restarts automatically. The local management password, current logins, QQ connection settings and backup cleanup rules are preserved. Automatic replies are turned off and plugin execution grants reset. Review connections, models and tasks before enabling replies; reinstall plugins or review their permissions. Import replaces the whole database rather than merging records. Pre-import snapshots can be managed manually and are excluded from scheduled full-backup cleanup.
+
+The server removes the export copy after download. Cancelled, expired and interrupted staging files are reclaimed; unused previews expire after one hour. Failed imports retain or restore the original database rather than starting with a partial file.
+
 ## 9. Troubleshooting
 
 | Symptom                           | Check first                                                                                                                              |
 | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
 | The page does not open            | Is Node running, and is the address `127.0.0.1:3210`                                                                                     |
 | Port already in use               | Run `npm run stop` first; do not kill every node process                                                                                 |
-| Wrong token                       | Use `ADMIN_TOKEN`; restart after editing `.env`                                                                                          |
-| OneBot not connected              | Is the connector logged in; do the URL, port, path and `ONEBOT_TOKEN` all match                                                          |
+| Incorrect password                | Sign in with your management password; change it under System → Run switches                                                             |
+| OneBot not connected              | Check sign-in, enabled reverse client, address, port and path; local clients need no token                                               |
 | Official bot not connected        | Are the AppID and AppSecret right, are group and one-to-one messages enabled for the bot, can the network reach the QQ Open Platform     |
 | Official bot only gets @ messages | Enable "receive all messages" on the Open Platform; this is a platform permission, not a LuckyTri limit                                  |
 | Connected but no sessions         | Send one more new message in QQ; with OneBot also check the message format is array                                                      |