@petercjl/codex-own 0.6.4 → 0.6.5

package/skills/codex-own/SKILL.md

@@ -42,6 +42,14 @@ Tools own their npm prefix/cache and pip cache; no user/system PATH, shell profi
 
 ## Recovery and boundaries
 
+For installation failures, read `doctor --json` and `repair plan`. Doctor reports the actual bootstrap Node executable/version/architecture, lock owner, and inactive staging inventory. Node 22+ is checked before loading the manager; on Windows, a `.cmd` shim may select a different Node than PATH. Prefer invoking the selected supported Node with the npm CLI and installed `bin/codex-own.mjs` explicitly when multiple runtimes exist.
+
+With authorization to reclaim failed installation staging and recover a dead lock, use `repair run --yes`. It preserves current applications, live data, content caches and rollback snapshots. Live/unknown lock owners, active applications, recovery locks and incomplete transactions require inspection; never delete their files to force continuation. Run doctor again, then return to main-line install/update. A copied application candidate is reclaimable only with a matching ownership receipt; unknown next directories stay intact.
+
+Extraction reads Unicode entry names directly from TAR/PAX/gzip/ZIP bytes, checks entry types, file sizes and SHA256, and retries missing or changed entries at most three times. UNPACK_INCOMPLETE/UNPACK_FAILED report missing samples and staging location; persistent security-software interception needs investigation rather than repeated retries or disabling protection. Each installation cleans its own staging on success/failure; occupied files remain reported for explicit recovery. Verified content blocks remain reusable.
+
+Default stdout remains JSON and progress remains stderr for integrations. For an interactive Windows terminal use `--progress stdout` with UTF-8 console settings; `--quiet` suppresses progress. `--json` cannot be combined with stdout progress. Use the process exit status and final result, rather than text color, for success. Runtime selection receipts retain at most 20 verified backups; immutable tool versions stay preserved.
+
 For Windows Agent shell diagnosis, inspect `doctor.agentShell`: verified system Git Bash is preferred for general task commands, PowerShell remains available for Windows-specific operations, and missing/unusable Bash reports a fallback reason. `desktopAdapterBundled` distinguishes a capable desktop from an upgraded manager with an older desktop. The desktop adds this execution policy to new, resumed and forked Agent sessions while preserving existing developer instructions and the private Node/npm/Python environment. Integrated-terminal settings are independent; verify the actual tool call's explicit `shell` and command result. The Windows host context may still say PowerShell. An explicit user shell choice takes precedence. Never replay a failed command in a different shell without checking its side effects.
 
 Component binding contract 2 requires a bridge desktop with embedded updater contract 2 and tool environment contract 1. Manager releases pin exact immutable artifacts, so their version numbers may differ. A manager-only release is not a desktop update; a tool-only update retains the desktop and uses new paths after restart. Legacy pre-bridge clients may need one CLI upgrade. INCOMPATIBLE_BINDING preserves the installed components; inspect the published binding and compatibility instead of forcing a version match.