publishport-opencli 1.0.1 → 1.0.2

package/skills/opencli-browser/SKILL.md

@@ -1,21 +1,21 @@
 ---
 name: opencli-browser
-description: Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing adapters — see opencli-adapter-author for that.
-allowed-tools: Bash(opencli:*), Read, Edit, Write
+description: Use when an agent needs to drive a real Chrome window via ppcli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing adapters — see opencli-adapter-author for that.
+allowed-tools: Bash(ppcli:*), Read, Edit, Write
 ---
 
 # opencli-browser
 
 The first reader of this CLI is an agent, not a human. Every subcommand returns a structured envelope that tells you exactly what matched, how confident the match is, and what to do if it didn't. Lean on those envelopes — do not guess.
 
-This skill is for **driving a live browser** to accomplish an agent task. If you are building a reusable adapter under `~/.opencli/clis/<site>/` use `opencli-adapter-author` instead.
+This skill is for **driving a live browser** to accomplish an agent task. If you are building a reusable adapter under `~/.ppcli/clis/<site>/` use `opencli-adapter-author` instead.
 
 ---
 
 ## Prerequisites
 
 ```bash
-opencli doctor
+ppcli doctor
 ```
 
 Until `doctor` is green, nothing else will work. Typical failures: Chrome not running, extension not installed, debug port blocked by 1Password / other extensions. The doctor output tells you which.
@@ -24,27 +24,27 @@ Until `doctor` is green, nothing else will work. Typical failures: Chrome not ru
 
 ## Session lifecycle
 
-- `opencli browser *` commands require a `<session>` positional immediately after `browser`. Use the same session name for a multi-step flow; use a different name to isolate parallel browser work.
-- Use a stable session name for any multi-command or human-paced browser workflow. Example: `opencli browser fb-yaya-warmup open https://example.com`, then reuse `opencli browser fb-yaya-warmup state`, `extract`, `click`, etc.
-- Owned browser sessions keep a tab lease alive between calls. Release it with `opencli browser <session> close` or let the idle timeout expire.
-- `opencli browser <session> bind` binds the Chrome tab you already have open to that session. Use this for logged-in pages, SSO flows, or pages you manually positioned before handing control to the agent.
-- `--window foreground|background` (or `OPENCLI_WINDOW=foreground|background`) chooses whether OpenCLI creates/focuses a foreground browser window or uses a background browser window for owned sessions.
+- `ppcli browser *` commands require a `<session>` positional immediately after `browser`. Use the same session name for a multi-step flow; use a different name to isolate parallel browser work.
+- Use a stable session name for any multi-command or human-paced browser workflow. Example: `ppcli browser fb-yaya-warmup open https://example.com`, then reuse `ppcli browser fb-yaya-warmup state`, `extract`, `click`, etc.
+- Owned browser sessions keep a tab lease alive between calls. Release it with `ppcli browser <session> close` or let the idle timeout expire.
+- `ppcli browser <session> bind` binds the Chrome tab you already have open to that session. Use this for logged-in pages, SSO flows, or pages you manually positioned before handing control to the agent.
+- `--window foreground|background` (or `OPENCLI_WINDOW=foreground|background`) chooses whether ppcli creates/focuses a foreground browser window or uses a background browser window for owned sessions.
 
 ### Bind Tab
 
 ```bash
-opencli browser gmail bind
-opencli browser gmail state
-opencli browser gmail click "Search"
-opencli browser gmail network
-opencli browser gmail unbind
+ppcli browser gmail bind
+ppcli browser gmail state
+ppcli browser gmail click "Search"
+ppcli browser gmail network
+ppcli browser gmail unbind
 ```
 
-Binding never owns the user window and never closes the user tab. It fails closed if the tab is closed or becomes non-debuggable. Re-run `opencli browser <session> bind` when you switch to a different real tab.
+Binding never owns the user window and never closes the user tab. It fails closed if the tab is closed or becomes non-debuggable. Re-run `ppcli browser <session> bind` when you switch to a different real tab.
 
-Navigation is allowed on bound sessions because the session now represents explicit agent ownership of that tab. Tab mutation (`tab new`, `tab select`, `tab close`) is still blocked for bound sessions. Use an owned session when you want OpenCLI to manage tab lifecycle.
+Navigation is allowed on bound sessions because the session now represents explicit agent ownership of that tab. Tab mutation (`tab new`, `tab select`, `tab close`) is still blocked for bound sessions. Use an owned session when you want ppcli to manage tab lifecycle.
 
-Bound sessions have no OpenCLI idle-close timer; the binding lasts until `unbind`, tab close, window close, or daemon restart.
+Bound sessions have no ppcli idle-close timer; the binding lasts until `unbind`, tab close, window close, or daemon restart.
 
 ---
 
@@ -60,7 +60,7 @@ Bound sessions have no OpenCLI idle-close timer; the binding lasts until `unbind
 ## Critical rules
 
 1. **Always inspect before you act.** Run `state` or `find` first. Never hard-code a ref or selector from memory across sessions — indices are per-snapshot.
-2. **Prefer site adapters before raw browser driving.** If `opencli <site> <command>` already covers the task, use that adapter command first (`opencli facebook notifications`, `opencli reddit read`, etc.). Use `opencli browser ...` only for gaps, debugging, or one-off UI flows the adapter does not expose.
+2. **Prefer site adapters before raw browser driving.** If `ppcli <site> <command>` already covers the task, use that adapter command first (`ppcli facebook notifications`, `ppcli reddit read`, etc.). Use `ppcli browser ...` only for gaps, debugging, or one-off UI flows the adapter does not expose.
 3. **Prefer numeric ref over CSS once you have it.** Numeric refs survive mild DOM shifts because the CLI fingerprints each tagged element. A CSS selector written by hand will break the first time the site re-renders.
 4. **Read `match_level` after every write.** `exact` = all good. `stable` = the element is the same but some soft attrs drifted — your action still applied. `reidentified` = the original ref was gone and the CLI found a unique replacement; double-check you hit the right element.
 5. **Use the `compound` field for form controls.** Do not regex-guess a date format, do not `state` twice to get the full `<select>` options list. The compound envelope has the format string, full option list up to 50, `options_total` for overflow, and `accept`/`multiple` for `<input type=file>`.
@@ -187,9 +187,9 @@ Error envelope always includes `error.code` and `error.message`. Target errors (
 4. 看回读的 `after`：验证码消失 / URL 跳转 = 成功；仍在且 prompt 变了 = 认错刷新了要重来；仍在且 prompt 没变 = 可能漏点，补点。
 
 ```bash
-opencli browser pub captcha --scale 4            # 存 crop 裁剪图 + 返回 prompt
+ppcli browser pub captcha --scale 4            # 存 crop 裁剪图 + 返回 prompt
 # —— 你读 crop 图：prompt="铃却挂"（另有干扰字别点），读出三个字在图里的比例 ——
-opencli browser pub captcha-click --crop --in ".js-mocaptcha-img" "0.24,0.17 0.69,0.38 0.82,0.36"
+ppcli browser pub captcha-click --crop --in ".js-mocaptcha-img" "0.24,0.17 0.69,0.38 0.82,0.36"
 ```
 
 提醒：验证码识别靠视觉，扭曲字**可能认错**（尤其岩石/云等低对比背景、生僻复杂字）——背景太乱认不清就点刷新按钮换一张（`.js-mocaptcha-refresh` 之类，刷新不提交、无害，多数会换到干净背景）。别短时间反复猛试同一账号（会抬高风控/被判异常），一两次不过就退回让用户手动点。
@@ -213,7 +213,7 @@ state, elapsedMs}` on success and a JSON error envelope on timeout/failure.
 
 ### Extract
 
-- **`web read --url <url>`** — One-shot Markdown reader for arbitrary pages. It expands relevant same-origin iframes by default, so old iframe-shell sites work better than with a top-document-only scrape. Use `--frames all-same-origin` when completeness matters more than Markdown noise. For AJAX shell pages use `opencli web read --url <url> --wait-for "<selector>" --wait-until networkidle --diagnose`; diagnostics show frame URLs, empty containers, and API-like XHRs. If the value you need is table/API data, switch to `browser network` or a dedicated adapter instead of relying on Markdown.
+- **`web read --url <url>`** — One-shot Markdown reader for arbitrary pages. It expands relevant same-origin iframes by default, so old iframe-shell sites work better than with a top-document-only scrape. Use `--frames all-same-origin` when completeness matters more than Markdown noise. For AJAX shell pages use `ppcli web read --url <url> --wait-for "<selector>" --wait-until networkidle --diagnose`; diagnostics show frame URLs, empty containers, and API-like XHRs. If the value you need is table/API data, switch to `browser network` or a dedicated adapter instead of relying on Markdown.
 - **`browser eval <js> [--frame N]`** — Run an expression in the page (or in a cross-origin frame via `--frame`). Wrap in an IIFE and return JSON. Read-only: no `document.forms[0].submit()`, no clicks, no navigations. If the result is a string, stdout is the raw string; otherwise it's JSON.
 - **`browser extract [--selector <css>] [--chunk-size N] [--start N]`** — Markdown extraction of long-form content with a continuation cursor. Returns `{url, title, selector, total_chars, chunk_size, start, end, next_start_char, content}`. Loop on `next_start_char` until it is `null`. Auto-scopes to `<main>`/`<article>`/`<body>` if you don't pass `--selector`.
 
@@ -228,7 +228,7 @@ browser network --raw                  # full bodies inline — large; use spari
 browser network --ttl <ms>             # cache TTL (default 24h)
 ```
 
-List entries look like `{key, method, status, url, ct, size, shape, body_truncated?}`. Detail envelope is `{key, url, method, status, ct, size, shape, body, body_truncated?, body_full_size?, body_truncation_reason}`. Cache lives in `~/.opencli/cache/browser-network/` so you can re-inspect without re-triggering the request.
+List entries look like `{key, method, status, url, ct, size, shape, body_truncated?}`. Detail envelope is `{key, url, method, status, ct, size, shape, body, body_truncated?, body_full_size?, body_truncation_reason}`. Cache lives in `~/.ppcli/cache/browser-network/` so you can re-inspect without re-triggering the request.
 
 Default output keeps JSON/XML/plain-text and JS-like API responses, then drops obvious static assets and telemetry by URL. If an expected endpoint is missing, run `browser network --all` once and check whether an unusual content type or URL filter hid it.
 
@@ -331,9 +331,9 @@ Rule of thumb: **one `state` per page transition, one `find` per follow-up query
 **Good — one shell, live session:**
 
 ```bash
-opencli browser hn open "https://news.ycombinator.com" \
-  && opencli browser hn state \
-  && opencli browser hn click 3
+ppcli browser hn open "https://news.ycombinator.com" \
+  && ppcli browser hn state \
+  && ppcli browser hn click 3
 ```
 
 **Bad — each line is a fresh shell, refs from call 1 are already forgotten when call 2 runs.** (Only a problem if you rely on shell-scoped state; browser refs themselves persist in-page, but interleaving unrelated shells invites races.) Prefer `&&` when the steps are meant to be atomic.
@@ -347,24 +347,24 @@ opencli browser hn open "https://news.ycombinator.com" \
 ### Fill a login form
 
 ```bash
-opencli browser login open "https://example.com/login"
-opencli browser login state                          # find [N] for email, password, submit
-opencli browser login type 4 "me@example.com"
-opencli browser login type 5 "hunter2"
-opencli browser login get value 4                    # verify (autocomplete can eat chars)
-opencli browser login click 6                        # submit
-opencli browser login wait selector "[data-testid=account-menu]" --timeout 15000
-opencli browser login state                          # fresh refs on the logged-in page
+ppcli browser login open "https://example.com/login"
+ppcli browser login state                          # find [N] for email, password, submit
+ppcli browser login type 4 "me@example.com"
+ppcli browser login type 5 "hunter2"
+ppcli browser login get value 4                    # verify (autocomplete can eat chars)
+ppcli browser login click 6                        # submit
+ppcli browser login wait selector "[data-testid=account-menu]" --timeout 15000
+ppcli browser login state                          # fresh refs on the logged-in page
 ```
 
 ### Pick from a long dropdown
 
 ```bash
-opencli browser form state                          # sidebar shows [12] <select name=country>
-opencli browser form find --css "select[name=country]"
+ppcli browser form state                          # sidebar shows [12] <select name=country>
+ppcli browser form find --css "select[name=country]"
 # the compound.options_total is 137, but compound.current is "" — unselected.
-opencli browser form select 12 "Uruguay"
-opencli browser form get value 12                   # { value: "uy", match_level: "exact" }
+ppcli browser form select 12 "Uruguay"
+ppcli browser form get value 12                   # { value: "uy", match_level: "exact" }
 ```
 
 ### Pick from a custom React dropdown
@@ -373,13 +373,13 @@ Use this for Radix, shadcn, Material UI, Mercury-style category fields, and
 other controls that are not native `<select>`.
 
 ```bash
-opencli browser mercury state                          # find category trigger ref
+ppcli browser mercury state                          # find category trigger ref
 # If the trigger/option is not clear, use AX:
-opencli browser mercury state --source ax              # look for combobox/button/listbox/option names
-opencli browser mercury click 7                        # click category trigger
-opencli browser mercury state --source ax              # fresh refs after the portal/listbox opens
-opencli browser mercury click 12                       # click option
-opencli browser mercury get text 7                     # verify visible selected label
+ppcli browser mercury state --source ax              # look for combobox/button/listbox/option names
+ppcli browser mercury click 7                        # click category trigger
+ppcli browser mercury state --source ax              # fresh refs after the portal/listbox opens
+ppcli browser mercury click 12                       # click option
+ppcli browser mercury get text 7                     # verify visible selected label
 ```
 
 Do not use `browser select` on these widgets. `browser select` is only for
@@ -392,7 +392,7 @@ When deciding whether AX refs are better for a page, collect metrics without
 sharing page contents:
 
 ```bash
-opencli browser compare state --compare-sources
+ppcli browser compare state --compare-sources
 ```
 
 Report `sources.dom.refs`, `sources.ax.refs`, `frame_sections`,
@@ -402,28 +402,28 @@ arguing that AX should become the default on a site.
 ### Scrape a list via network instead of DOM
 
 ```bash
-opencli browser hn open "https://news.ycombinator.com"
-opencli browser hn network --filter "title,score"
+ppcli browser hn open "https://news.ycombinator.com"
+ppcli browser hn network --filter "title,score"
 # -> find the /topstories entry, note its key
-opencli browser hn network --detail topstories-a1b2
+ppcli browser hn network --detail topstories-a1b2
 ```
 
 ### Read a long article in chunks
 
 ```bash
-opencli browser article open "https://blog.example.com/long-post"
-opencli browser article extract --chunk-size 8000
+ppcli browser article open "https://blog.example.com/long-post"
+ppcli browser article extract --chunk-size 8000
 # -> content + next_start_char: 8000
-opencli browser article extract --start 8000 --chunk-size 8000
+ppcli browser article extract --start 8000 --chunk-size 8000
 # ...until next_start_char is null
 ```
 
 ### Cross-origin iframe
 
 ```bash
-opencli browser checkout frames
+ppcli browser checkout frames
 # -> [{"index": 0, "url": "https://checkout.stripe.com/...", ...}]
-opencli browser checkout eval "(() => document.querySelector('input[name=cardnumber]')?.value)()" --frame 0
+ppcli browser checkout eval "(() => document.querySelector('input[name=cardnumber]')?.value)()" --frame 0
 ```
 
 `browser state --source ax` may omit cross-origin iframe contents or fail to
@@ -449,20 +449,20 @@ normal DOM `state`, or navigate/bind directly to the iframe URL when possible.
 
 | symptom | fix |
 |---------|-----|
-| `opencli doctor` red: "Browser not connected" | Start Chrome with `--remote-debugging-port=9222`, or install the extension from the [Chrome Web Store](https://chromewebstore.google.com/detail/opencli/ildkmabpimmkaediidaifkhjpohdnifk). |
+| `ppcli doctor` red: "Browser not connected" | Start Chrome with `--remote-debugging-port=9222`, or install the extension from the [Chrome Web Store](https://chromewebstore.google.com/detail/opencli/ildkmabpimmkaediidaifkhjpohdnifk). |
 | `attach failed: chrome-extension://...` | Disable 1Password / other CDP-hungry extensions temporarily. |
 | `selector_not_found` right after `state` | Page mutated. `wait selector "..."` then retry. |
 | `stale_ref` across every command | You are reusing refs from a prior page. Re-`state`. |
 | `click` succeeds but nothing happens | The element is probably a decorative wrapper stealing clicks from the real target. `find --css "..."` with a narrower selector and retry on the inner element. |
 | `type` appears to finish but value is wrong | Autocomplete, masked input, or React controlled re-render. Verify with `get value`. Add `keys Enter` or re-type. |
 | Giant `get html` output | Pass `--selector` + `--as json --depth 3 --children-max 20 --text-max 200`. |
-| Network cache seems stale | Bump `--ttl` down, or let it expire. The cache lives at `~/.opencli/cache/browser-network/`. |
+| Network cache seems stale | Bump `--ttl` down, or let it expire. The cache lives at `~/.ppcli/cache/browser-network/`. |
 
 ---
 
 ## See also
 
-- `opencli-adapter-author` — turning what you just figured out into a reusable `~/.opencli/clis/<site>/<command>.js`.
+- `opencli-adapter-author` — turning what you just figured out into a reusable `~/.ppcli/clis/<site>/<command>.js`.
 - `opencli-browser-sitemap` — consuming site sitemap context while driving a browser task.
 - `opencli-sitemap-author` — creating or updating sitemap knowledge when you discover a durable path or stale entry.
 - `opencli-autofix` — when an existing adapter breaks, this skill walks you through `--trace retain-on-failure` evidence and filing a fix.

package/skills/opencli-browser-sitemap/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: opencli-browser-sitemap
-description: Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live browser state.
-allowed-tools: Bash(opencli:*), Read, Edit, Write, Grep
+description: Use when driving a website with ppcli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live browser state.
+allowed-tools: Bash(ppcli:*), Read, Edit, Write, Grep
 ---
 
 # opencli-browser-sitemap
 
-Use this skill when `opencli browser open` or `opencli browser analyze` reports `sitemap.available: true`, or when the user asks you to use a site's sitemap.
+Use this skill when `ppcli browser open` or `ppcli browser analyze` reports `sitemap.available: true`, or when the user asks you to use a site's sitemap.
 
 The sitemap is **prior knowledge**, not ground truth. It should reduce blind clicking, but it must never override the live browser state.
 
@@ -14,13 +14,13 @@ The sitemap is **prior knowledge**, not ground truth. It should reduce blind cli
 
 ## Consumption Loop
 
-1. Run or reuse `opencli browser <session> state` to know the current page.
+1. Run or reuse `ppcli browser <session> state` to know the current page.
 2. Read only the smallest relevant sitemap files:
    - `SITE.md` for site-level orientation.
    - One matching `pages/<page-id>.md` for current state.
    - One matching `workflows/<task-id>.md` for the user goal.
    - `pitfalls.md` only when blocked or warned by the workflow.
-3. Prefer the workflow's **Best path**. If it names an adapter such as `opencli twitter post`, use that before raw browser actions.
+3. Prefer the workflow's **Best path**. If it names an adapter such as `ppcli twitter post`, use that before raw browser actions.
 4. If the adapter is unavailable or fails, use the **Fallback path** browser workflow.
 5. After each navigation or state-changing action, refresh `state` and compare the workflow's `state_signature`.
 6. If reality disagrees, trust reality, continue probing, and write a local stale note or draft patch.
@@ -33,7 +33,7 @@ The sitemap is **prior knowledge**, not ground truth. It should reduce blind cli
 Read local overlay first, then global seed:
 
 ```text
-~/.opencli/sites/<site>/sitemap/    # local overlay
+~/.ppcli/sites/<site>/sitemap/    # local overlay
 sitemaps/<site>/                    # repo seed (top-level)
 ```
 
@@ -75,7 +75,7 @@ Do not edit global seed files unless the task is explicitly a sitemap-authoring
 
 When an adapter fails and the sitemap action or workflow tells you to update adapter health:
 
-1. Find the local workflow file under `~/.opencli/sites/<site>/sitemap/workflows/` whose `Best path` references the adapter command.
+1. Find the local workflow file under `~/.ppcli/sites/<site>/sitemap/workflows/` whose `Best path` references the adapter command.
 2. If no local workflow exists, copy the matching global workflow into the local overlay first; never edit the global seed directly during browser task execution.
 3. Set `adapter_health: suspect` or `broken` as directed.
 4. Add a short stale note with observed error, current URL, and timestamp.

package/skills/opencli-sitemap-author/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: opencli-sitemap-author
-description: Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
-allowed-tools: Bash(opencli:*), Read, Edit, Write, Grep
+description: Use when creating or maintaining ppcli site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
+allowed-tools: Bash(ppcli:*), Read, Edit, Write, Grep
 ---
 
 # opencli-sitemap-author
 
-You are authoring a **task execution graph for agents**, not an SEO sitemap. The artifact should help an agent using `opencli browser` decide where it is, what path to take next, which OpenCLI adapter to prefer, and how to recover when the page disagrees with memory.
+You are authoring a **task execution graph for agents**, not an SEO sitemap. The artifact should help an agent using `ppcli browser` decide where it is, what path to take next, which ppcli adapter to prefer, and how to recover when the page disagrees with memory.
 
 Keep the sitemap small and verified. Do not crawl a whole site. Capture only task-relevant paths that you actually observed.
 
@@ -17,7 +17,7 @@ Keep the sitemap small and verified. Do not crawl a whole site. Capture only tas
 Two layers:
 
 - **Global seed**: `sitemaps/<site>/` (top-level)
-- **Local overlay**: `~/.opencli/sites/<site>/sitemap/`
+- **Local overlay**: `~/.ppcli/sites/<site>/sitemap/`
 
 Local overlay wins by stable id. Write new discoveries to local first. Promote to global only after review.
 
@@ -51,10 +51,10 @@ Phase 2 cron audit 按 token count 不按 byte count（CJK 中文 token-per-char
 ## Authoring Loop
 
 1. **Load existing memory**: read local overlay first, then global seed if present.
-2. **Verify reality**: use `opencli browser <session> state`, `find`, `network`, and `analyze`; browser state is truth. If you just completed an `opencli-adapter-author` session for this site, start from the retained browse trace under `~/.opencli/sites/<site>/traces/` as seed evidence instead of re-discovering the path from zero.
+2. **Verify reality**: use `ppcli browser <session> state`, `find`, `network`, and `analyze`; browser state is truth. If you just completed an `opencli-adapter-author` session for this site, start from the retained browse trace under `~/.ppcli/sites/<site>/traces/` as seed evidence instead of re-discovering the path from zero.
 3. **Record only durable structure**: page purpose, stable anchors, state signature, actions, workflows, API references, pitfalls.
 4. **Use stable ids**: page/action/workflow ids should survive URL params, locale text drift, and minor layout changes.
-5. **Write local draft**: update `~/.opencli/sites/<site>/sitemap/...` unless explicitly promoting to repo.
+5. **Write local draft**: update `~/.ppcli/sites/<site>/sitemap/...` unless explicitly promoting to repo.
 6. **Mark stale on conflict**: if existing sitemap disagrees with current browser state, trust browser state and mark the item stale rather than forcing the old path.
 
 ---
@@ -70,7 +70,7 @@ do: <agent action, adapter command, or semantic browser command>
 post: <URL / state / output that proves success>
 fail: <failure signal 1> | <signal 2>
 recover: <fallback instruction>; adapter_health_update: <adapter> -> suspect
-evidence: opencli browser <cmd> or trace:<path>
+evidence: ppcli browser <cmd> or trace:<path>
 ```
 
 Use this compact form by default. Use the longer Markdown form from `references/sitemap-schema.md` only when an action genuinely needs long explanation. `verified_at` and `source` are inherited from file frontmatter; do not repeat them per action.
@@ -106,7 +106,7 @@ Each workflow should answer:
 
 - **Goal**: user-facing task this workflow solves.
 - **State signature**: minimal observable checkpoint for resume after sleep/compaction.
-- **Best path**: prefer existing `opencli <site> <command>` adapter if it covers the goal.
+- **Best path**: prefer existing `ppcli <site> <command>` adapter if it covers the goal.
 - **Fallback path**: browser workflow if the adapter is missing or failing.
 - **Avoid**: tempting paths that waste turns, trigger modals, or rely on unstable selectors.
 - **Stale markers**: last verified date and known layout/API drift signals.
@@ -119,8 +119,8 @@ Fallback path 第一行声明触发条件 + adapter_health_update directive，
 
 ```yaml
 on_adapter_fail:
-  - adapter_health_update: opencli twitter post -> suspect
-  - opencli browser state (verify current page)
+  - adapter_health_update: ppcli twitter post -> suspect
+  - ppcli browser state (verify current page)
   - if not on /home: goto /home
   - action:open_compose in pages/home.md
   - ...
@@ -152,7 +152,7 @@ on_adapter_fail:
 - Do not document bypasses for CAPTCHA, WAF, access control, rate limits, or paid gates.
 - Do not store brittle snapshot indices like `[17]` as durable targets. Store semantic anchors and recovery instructions.
 - Do not describe unverified paths as facts. Use `draft` or `stale` labels.
-- Drafts go inside `sitemap/draft-<topic>.md`, not `~/.opencli/sites/<site>/sitemap.draft.md` at the parent level — the latter is invisible to `opencli browser` sitemap availability detection.
+- Drafts go inside `sitemap/draft-<topic>.md`, not `~/.ppcli/sites/<site>/sitemap.draft.md` at the parent level — the latter is invisible to `ppcli browser` sitemap availability detection.
 
 ---
 

package/skills/opencli-sitemap-author/references/sitemap-schema.md

@@ -215,7 +215,7 @@ Create a new public post on this site with text content.
 - success: post visible on author's timeline within 5s
 
 ## Best path
-adapter: opencli twitter post
+adapter: ppcli twitter post
 adapter_health: healthy        # healthy | suspect | broken
 preconditions:
   - logged_in
@@ -297,7 +297,7 @@ source: local
 ```
 
 **Required per entry**:
-- `endpoint_id` — 必须存在于同站 `~/.opencli/sites/<site>/endpoints.json`
+- `endpoint_id` — 必须存在于同站 `~/.ppcli/sites/<site>/endpoints.json`
 - `triggers_on_pages` — array of `page_id`
 - `triggered_by_actions` — array of `action:<stable-id>`
 - `contract_strength` — `stable | visible-ui | internal-unstable`，定义见 `strategy-selection.md`
@@ -350,7 +350,7 @@ verified_at: 2026-06-01
 
 #### Scope（避免 sitemap 变杂物间）
 
-`pitfalls.md` 只放 **task-executor 级**坑 — 跑命令 / 操作页面会撞到的坑。**adapter-internal 实现坑**（queryId 解析 / envelope unwrap / bigint id / 字段 silent rename）放在 `~/.opencli/sites/<site>/notes.md`，不进 sitemap。
+`pitfalls.md` 只放 **task-executor 级**坑 — 跑命令 / 操作页面会撞到的坑。**adapter-internal 实现坑**（queryId 解析 / envelope unwrap / bigint id / 字段 silent rename）放在 `~/.ppcli/sites/<site>/notes.md`，不进 sitemap。
 
 判断标准：
 
@@ -407,7 +407,7 @@ State signature:                          # OPTIONAL — for multi-step internal
   dom_anchor: <a11y role+name OR semantic selector>
 
 Evidence:
-- observed_with: opencli browser <session> <command>
+- observed_with: ppcli browser <session> <command>
 - trace: <path to trace artifact, optional>
 ```
 
@@ -420,7 +420,7 @@ do: <agent action, adapter or semantic browser command>
 post: <URL / state / output that proves success>
 fail: <failure signal 1> | <signal 2> | <signal 3>
 recover: <fallback instruction>; adapter_health_update: <adapter> -> suspect
-evidence: opencli browser <cmd>
+evidence: ppcli browser <cmd>
 ```
 
 字段分隔符约定（避免 ambiguity）：
@@ -428,8 +428,8 @@ evidence: opencli browser <cmd>
 | 符号 | 用途 | 例 |
 |---|---|---|
 | `\|` | 多 failure signal 平级枚举（"任一发生即视为失败"）| `fail: button_not_found \| /flow/login redirect` |
-| `\|\|` | 多 do path / recovery path **fallback priority**（"前者失败试后者"）| `do: opencli twitter like <url> \|\| click [data-testid="like"]` |
-| `;` | 多 recovery 指令 **sequential**（"逐条执行"）| `recover: adapter_health_update: opencli twitter like -> suspect; dom_click within card scope` |
+| `\|\|` | 多 do path / recovery path **fallback priority**（"前者失败试后者"）| `do: ppcli twitter like <url> \|\| click [data-testid="like"]` |
+| `;` | 多 recovery 指令 **sequential**（"逐条执行"）| `recover: adapter_health_update: ppcli twitter like -> suspect; dom_click within card scope` |
 
 字段语义完全等价 Form A，**推荐 Form B**，密集站避免 verbose markdown 把 page 撑爆。
 
@@ -445,8 +445,8 @@ evidence: opencli browser <cmd>
 - 一般是 page state（"on /home"）+ auth state（"logged_in"）+ UI state（"compose dialog not yet open"）
 
 **Do**：实际操作。优先级：
-1. 已有 adapter 命令（`opencli twitter post`）
-2. semantic browser command（`opencli browser click "Post" button`）
+1. 已有 adapter 命令（`ppcli twitter post`）
+2. semantic browser command（`ppcli browser click "Post" button`）
 3. 显式 selector（最后选项，写 stable anchor 不是裸 CSS）
 
 **Postconditions**：成功观察信号。必须具体 — "page changed" 不算，"URL is /compose AND textarea is focused" 才算。
@@ -486,11 +486,11 @@ evidence: opencli browser <cmd>
 ```yaml
 ### action:like_tweet
 pre: card visible AND (tweet_url known OR card permalink anchor extractable)
-do: opencli twitter like <tweet-url> || click [data-testid="like"] (within card scope)
+do: ppcli twitter like <tweet-url> || click [data-testid="like"] (within card scope)
 post: testid 翻转 like -> unlike，icon 红色
 fail: testid 不变 | 弹 login modal
-recover: adapter_health_update: opencli twitter like -> suspect; dom_click within card scope
-evidence: opencli twitter like + opencli browser click
+recover: adapter_health_update: ppcli twitter like -> suspect; dom_click within card scope
+evidence: ppcli twitter like + ppcli browser click
 ```
 
 两层 routing 不冲突：
@@ -561,11 +561,11 @@ sitemap 内部多文件互相引用。引用格式：
 
 agent 发现新路径 / stale 修正 / 半成品流程时写 draft。**draft 必须放在 `sitemap/` 目录内**，命名为 `sitemap/draft-<topic>.md` 或 `sitemap/pages/<page>.draft.md`。
 
-**❌ 不要**放在父目录（如 `~/.opencli/sites/<site>/sitemap.draft.md`） — `opencli browser open` 的 sitemap availability 检测只看 `sitemap/` 目录是否存在。draft 放父目录 → 检测不到 → agent 不会被提醒"有 sitemap" → 你的发现没人用。
+**❌ 不要**放在父目录（如 `~/.ppcli/sites/<site>/sitemap.draft.md`） — `ppcli browser open` 的 sitemap availability 检测只看 `sitemap/` 目录是否存在。draft 放父目录 → 检测不到 → agent 不会被提醒"有 sitemap" → 你的发现没人用。
 
 正确：
 ```
-~/.opencli/sites/twitter/sitemap/
+~/.ppcli/sites/twitter/sitemap/
 ├── SITE.md
 ├── pages/home.md
 └── draft-search-filter.md       ← OK，会被检测到
@@ -573,7 +573,7 @@ agent 发现新路径 / stale 修正 / 半成品流程时写 draft。**draft 必
 
 错误：
 ```
-~/.opencli/sites/twitter/
+~/.ppcli/sites/twitter/
 ├── sitemap.draft.md             ← 检测不到，不会触发 availability
 └── sitemap/                     ← 空 dir → 检测到但内容空
     └── (empty)
@@ -581,7 +581,7 @@ agent 发现新路径 / stale 修正 / 半成品流程时写 draft。**draft 必
 
 ### 5.2 `site-alias.json`（optional, Phase 2）
 
-`opencli browser open` 用 adapter registry 把 hostname → site 映射（如 `news.ycombinator.com → hackernews`）。如果 sitemap 先于 adapter 存在（即一个站还没人写 adapter 但有人写了 sitemap），registry 没数据，sitemap dir 检测不到。
+`ppcli browser open` 用 adapter registry 把 hostname → site 映射（如 `news.ycombinator.com → hackernews`）。如果 sitemap 先于 adapter 存在（即一个站还没人写 adapter 但有人写了 sitemap），registry 没数据，sitemap dir 检测不到。
 
 future fix：sitemap dir 内放 `site-alias.json` 声明它服务的 hostname：
 
@@ -633,7 +633,7 @@ sitemap 是 hint，browser state 是 truth。当冲突时：
 
 ### 7.3 Reality check
 
-- action `Postconditions` 里的 `url_pattern` / `dom_anchor` → 用 `opencli browser` 实跑一遍，验证 anchor 仍可 resolve
+- action `Postconditions` 里的 `url_pattern` / `dom_anchor` → 用 `ppcli browser` 实跑一遍，验证 anchor 仍可 resolve
 - workflow `State signature.url_pattern` → 同上
 
 失败 → 自动倒 `last_verified` 30 天前。
@@ -649,7 +649,7 @@ sitemap 是 hint，browser state 是 truth。当冲突时：
 
 - [`../../opencli-adapter-author/references/strategy-selection.md`](../../opencli-adapter-author/references/strategy-selection.md) — `contract_strength` 和 `auth_strategy` 取值定义
 - [`../../opencli-adapter-author/references/api-discovery.md`](../../opencli-adapter-author/references/api-discovery.md) — `endpoint_id` 怎么发现
-- `~/.opencli/sites/<site>/endpoints.json` — endpoint 的真实 URL/method/params/response
+- `~/.ppcli/sites/<site>/endpoints.json` — endpoint 的真实 URL/method/params/response
 
 ---
 
@@ -657,4 +657,4 @@ sitemap 是 hint，browser state 是 truth。当冲突时：
 
 1. **`state_signature` 用什么 DSL**：现在写 `url_pattern: <regex>` + `dom_anchor: <semantic>`，未来可能需要更结构化（如 JSON path / xpath / a11y tree path）。等 PoC 实践后定
 2. **多语言站 anchor**：现在建议 a11y role + name；不同 locale name 不同。是否一个 anchor 列表多 locale，还是一个 sitemap per locale？PoC 后决
-3. **Validation cron 实现位置**：作为 OpenCLI 内置命令 `opencli sitemap audit`？还是独立 GitHub Action？Phase 2 决
+3. **Validation cron 实现位置**：作为 ppcli 内置命令 `ppcli sitemap audit`？还是独立 GitHub Action？Phase 2 决