@acedatacloud/skills 2026.806.0 → 2026.806.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@acedatacloud/skills",
-  "version": "2026.806.0",
+  "version": "2026.806.1",
   "description": "Agent Skills for AceDataCloud AI services — music, image, video generation, LLM chat, web search. Compatible with Claude Code, GitHub Copilot, Gemini CLI, OpenAI Codex, and 30+ AI coding agents.",
   "keywords": [
     "agent-skills",

package/skills/xiaohongshu/references/publish.md

@@ -36,13 +36,13 @@ After every navigation, upload, tab switch, modal open/close, or submission, the
 3. The page opens on `上传视频` by default. Select mode by exact visible tab text — `上传图文`, `上传视频`, or `写长文` — by observing the tab strip and clicking the returned ref. Verify the selected mode after clicking; the upload area text changes (`拖拽视频到此或点击上传` for video, an image dropzone for `上传图文`).
 4. If the tab click reports success but the mode does not change, an onboarding popover is covering the tab strip. Press `Escape`, re-observe, and click again. If it still does not change, stop and ask the user to dismiss the overlay in the visible tab — never try to delete page nodes.
 5. Upload one approved resource at a time and wait until the visible preview count reaches the submitted count before the next resource (up to 60 seconds per image). Re-observe between images: the file input's ref changes after the first upload. For video, wait until processing completes and Publish becomes enabled, up to 10 minutes. If resource resolution is unavailable, wait for the user to select local media and verify the same preview/processing state.
-6. Fill the image/video title using the visible title textbox (recognition hints: placeholder containing `填写标题`, then the single visible title input fallback). Titles are capped at 20 full-width-equivalent characters; a visible `n/20` counter turning over the limit is authoritative, so shorten and re-confirm rather than submitting a truncated title. Fill body in the visible rich-text editor (`输入正文描述` placeholder). Use `browser.fill` for replacement, or `browser.click` followed by `browser.type` for rich text. Read immediately after each field; stop if the exact normalized value is not visible.
+6. Fill the image/video title using the visible title textbox (recognition hints: placeholder containing `填写标题`, then the single visible title input fallback). Titles are capped at 20 full-width-equivalent characters; a visible `n/20` counter turning over the limit is authoritative, so shorten and re-confirm rather than submitting a truncated title. Fill body in the visible rich-text editor (`输入正文描述` placeholder). Use `browser.fill` for replacement, or `browser.click` followed by `browser.type` for rich text. Read immediately after each field and compare the complete title/body with the normalized preview. If a write fails or the content differs, do not append more keystrokes: replace the whole field, read it again, and obtain renewed confirmation for any changed preview. Never publish duplicated, missing, or extra text.
 7. Limit tags to the first 10 confirmed tags. Insert them one at a time, close any topic suggestion popover by focusing the title, and verify visible chips/text before continuing.
 8. Configure options one at a time and verify each exact state: schedule (1 hour–14 days), visibility (`公开可见`, `仅自己可见`, `仅互关好友可见`), originality, and products. If originality was requested but cannot be confirmed, abort rather than publishing non-original. Bind a product only when the exact intended product is visibly selected; never accept a first fuzzy match silently.
 9. For long article: choose `写长文` → `新的创作`; fill `输入标题` textarea and the body editor; click `一键排版`; enumerate visible template names; select the confirmed template and verify its selected state; click `下一步`; then fill the separate publish-page description editor.
 10. Before the final action, read or screenshot again and compare media count, title, full body, tags, options, products, and schedule with the confirmed preview. Stop on mismatch.
-11. Locate Publish through two page generations: the visible enabled publish widget first, then the visible legacy red Publish button. Reject `submit-disabled=true`, `disabled`, `aria-disabled=true`, or disabled styling. Click exactly once after the final confirmed chat preview.
-12. Follow [reconciliation](./reconciliation.md). Immediate success requires leaving `/publish/publish` or a visible success destination within 15 seconds. Remaining on the form is not success. Return the canonical note URL when visible.
+11. After the confirmed preview, run a fresh `browser.find` for `role=button`, `name=发布`. The current declarative creator widget is exposed through that semantic contract even though its page element is custom. Inspect the returned ref and reject `submit-disabled=true`, `disabled`, `aria-disabled=true`, or disabled styling. Click that fresh ref exactly once; do not substitute another visible control when Publish is missing.
+12. Follow [reconciliation](./reconciliation.md). Immediate success requires `/publish/success`, `published=true`, or a newly added same-title entry/note ID in note management. A changed draft count, returning to the initial publish page, or click completion alone is not success. Return the canonical note URL when visible.
 
 Never mix image/video media unless the visible current UI explicitly supports it. Bind products only when the account visibly exposes the feature and the exact selected products appear in the final preview.