@kynver-app/openclaw-agent-os 0.1.47 → 0.1.48

package/dist/index.js

@@ -1183,7 +1183,7 @@ function buildAgentOsContinuityGuidanceContext(config) {
     "- Landing tasks are merge-only. Do not edit files, rebase, resolve conflicts, change package versions, or perform implementation work from a landing lane.",
     "- For chat-visible PR check polling, prefer `node scripts/agent-os-pr-checks-soft.mjs <pr-number-or-url> --repo <owner/repo>` over raw `gh pr checks`. Raw `gh pr checks` exits nonzero for pending checks and creates false failed-tool alerts in Telegram; the soft wrapper exits nonzero only for real failed checks unless `--fail-on-pending` is explicitly requested.",
     "- For repo text search, do not pass a single filename (e.g. `package.json`) as ripgrep's path argument \u2014 that is a file, not a directory. Search from the repo root with a glob (`rg -g package.json <pattern> .`) or use `node scripts/agent-os-repo-search.mjs normalize -- '<command>'` before exec. Exclude scopes like `!node_modules` are not valid path arguments \u2014 use `-g '!node_modules/**'` (trailing `/**` required). Ripgrep exit 1 means no matches, not a tool failure. Searching only `package.json` for `agent-os-land-pr` should use `node scripts/agent-os-land-pr.mjs <pr-url>` directly.",
-    "- Land PRs only through the repo's narrow landing wrapper: `node scripts/agent-os-land-pr.mjs <pr-number-or-url>`. The wrapper performs live GitHub readiness checks, squash-merges exactly that PR, deletes the branch, and verifies merged state.",
+    "- Land PRs only through the repo's narrow landing wrapper: `node scripts/agent-os-land-pr.mjs <pr-number-or-url>`. For routine sweeps/watchdogs where a PR may still be pending, use `node scripts/agent-os-land-pr.mjs <pr-number-or-url> --skip-not-ready` so pending checks/UNSTABLE merge state return structured `skipped` JSON instead of a failed tool call. The wrapper performs live GitHub readiness checks, squash-merges exactly that PR, deletes the branch, and verifies merged state.",
     "- If the wrapper rejects a PR as draft, conflicted, non-green, pending checks, or missing an exact PR target, mark the landing task blocked with the exact reason instead of improvising a merge path.",
     "- Do not land unmanaged PRs. A PR must carry a hard AgentTask reference in the PR body and the AgentTask must carry `prUrl`; if either side is missing, block it as unmanaged and repair the link before merge.",
     "- Any PR update sent to Telegram, AgentOS events, or Command Center summaries must include a direct PR link and a plain-English purpose, not just a PR number, task id, branch, or terse title."