shuadouyin 0.3.2 → 0.3.3

package/.dy-build-commit

@@ -1 +1 @@
-ab12c5892c78af42d44e52d70980c742fdd40484
+9dfa8e6e905ba375b63fc90c7da17e95a6be4be8

package/dist/operations/navigation.js

@@ -42,7 +42,24 @@ export async function navigate(session, url, kind, signal) {
             ? state.page_kind === "search"
             : // The route commits before the profile renders, so the URL alone would let
                 // the caller read a page whose header has not appeared yet.
-                !!state.url?.includes("/user/") && state.page_kind === "profile", signal);
+                !!state.url?.includes("/user/") && state.page_kind === "profile", signal).catch((error) => {
+        // A profile that redirects elsewhere is a real answer, not a changed selector:
+        // Douyin sends restricted or unavailable accounts to the search page. Saying
+        // "the page did not reach the expected state" hides which of the two happened
+        // and sends the caller looking for a broken selector.
+        // Only when the page actually went somewhere else. A profile that simply took
+        // too long is a different answer, and calling it "not found" would send the
+        // caller looking for a restricted account that is fine.
+        if (kind === "profile" && error instanceof CliError && error.code === "selector_changed") {
+            const landed = String(error.details?.url ?? "");
+            if (landed && !landed.includes("/user/"))
+                throw new CliError("not_found", "This profile redirected elsewhere", {
+                    hint: "Douyin sent this account somewhere other than its profile: it may be restricted, deleted, or require a fresh login. Run dy auth status, or open one of their works with dy video open.",
+                    details: { requested: url, landed },
+                });
+        }
+        throw error;
+    });
 }
 // The recommended feed lives at https://www.douyin.com/?recommend=1, but a
 // plain load of that URL can land on the 精选 page instead, and the feed there

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "shuadouyin",
-	"version": "0.3.2",
+	"version": "0.3.3",
 	"packageManager": "pnpm@10.34.7",
 	"description": "Browse Douyin with a persistent bot persona and a memory of its own",
 	"type": "module",

package/skills/dy/SKILL.md

@@ -199,6 +199,38 @@ dy guide                        # 这份文档的完整内容
 
 `references/commands.md` 是按意图索引的全部命令地图。其余文件讲的是流程和判断，冲突时以命令行为为准。
 
+## 做事的时候一直在说话
+
+刷十条、看五条、评三条，这种活要跑几分钟。跑的时候**一条一条说**，别憋到最后一起报。
+
+原因很简单：用户在等。他不知道你在干什么，就只能看着屏幕不动。中途说一句「第 3 条是拆蟹教程，评论区在吵该不该用工具」，他就知道这事在推进，也能及时叫停——你要是刷到第 8 条才发现方向不对，已经浪费了七条。
+
+**每做完一个可描述的动作就报一句：**
+
+```
+看第 1 条：南浔弹唱《暧昧》，评论区在接歌词，中位 8 字
+看第 2 条：拆蟹教程 4 分钟，三帧是完整流程，14.6 万赞
+第 2 条评了：「大家争的是快慢，我看的是拆的过程本身好看」
+第 3 条划过了，内容是纯广告
+```
+
+**不要这样：**
+
+```
+✗ 好的，我来刷一下（然后 5 分钟没声，最后一次性贴 12 条结果）
+✗ 正在处理第 1/12 条……正在处理第 2/12 条……（这是在刷进度条，不是在说话）
+```
+
+**判断一条值不值得说**：这条读完你有没有新的判断？有就说，没有就跳到下一条。流水账和沉默一样没用。
+
+**长任务开始前先说一句要做什么、大概几步**，用户好在跑偏时叫停：
+
+```
+我去翻 8 条，挑 2 条有意思的看，可能评 1 条。
+```
+
+写操作（评论、私信）尤其要边说边做，因为 `dispatching` 之后不可逆——发之前那句「我要评这条：……」是用户最后的干预机会。
+
 ## 硬规则
 
 这几条在哪个参考文件里都成立：