mirror of
https://github.com/jackwener/OpenCLI.git
synced 2026-09-14 18:25:42 +08:00
jakevin
dc724262f2
* feat: agent-native retrospective — analyze / verify guards / fixture content checks Post-mortem on slow 1point3acres + 51job adapter sessions, consolidated into one PR. Scope is "reduce uncertainty and catch silent failures" — the two things that sink agent success rate on first-time adapters. Changes: - `browser analyze <url>` — one command returns pattern (A/B/C/D), anti-bot vendor (Aliyun/Cloudflare/Akamai/Geetest), nearest adapter, and a single-sentence recommended_next_step. Replaces the three-step open/wait/network recon loop when it can reach a confident verdict. - `browser wait xhr <regex>` — poll for a specific XHR URL instead of blind `wait time N`, so SPA data-arrival barriers are deterministic. - Fixture `mustNotContain` / `mustBeTruthy` — catch two silent-failure modes `notEmpty` misses: content contamination (sibling DOM bleed) and `|| 0` / `|| false` fallbacks. - `browser verify` post-success site-memory check + `--strict-memory` — verify-green no longer hides the case where `~/.opencli/sites/` was never written back. Memory only materializes if authors write it. - CI: guard that committed `cli-manifest.json` matches a fresh build. Main was already drifted (#1118 left stale ordering + a missing arg); this PR regenerates the manifest and will catch the next drift. Docs (opencli-adapter-author + opencli-autofix skills): - `success-rate-pitfalls.md` — 10 concrete silent-failure scenarios seen in real adapter sessions, each with defense via fixture / adapter patterns. - `autofix` gains discipline rule #6: verify pattern failure means tighten the adapter, never loosen the fixture. - `site-recon.md` leads with `browser analyze`; `api-discovery.md` adds a §0 covering WAF vendor detection and cross-subdomain CORS (the two gotchas that burned the 51job session). - `wait time 3` → `wait time 2`, with `wait xhr` as the robust choice. * fix: make output-dir defaults host-independent in manifest Three adapters (chatgpt/image, gemini/image, instagram/download) baked `path.join(os.homedir(), ...)` into the `default` field of their args. The committed manifest therefore carried my personal `/Users/jakevin/...` paths — which agents running on a different host saw as surprising defaults. The drift guard I just added to CI caught it on the first run. Runtime behavior is unchanged: each adapter still falls back to `path.join(os.homedir(), …)` inside `func` when the kwarg is absent. Only the displayed / registered default becomes a tilde-path. * fix(cli): enforce strict-memory without fixture * fix(browser): harden analyze and xhr guards * fix(browser): fallback to interceptor buffer