fix: move-codex-session skill should state which processes block a move #134
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/move-codex-session-skill-refusals"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #132 from two of its review findings (incomplete refusal list, process-tree wording).
The skill listed some of the script's refusals as if the list were complete. It also said the destination home may be open anywhere in the invoking process tree, but the script allows only itself and its ancestors there, so a process the invoking Codex started still blocks the move.
The skill now states the two home-activity requirements a caller can act on before running the script, and leaves every other refusal to the script's error message. The refusal list and the process-tree wording predate #132.
move-codex-sessionskill should state which processes block a movemove-codex-sessionshould handle Codex 0.160.1 and large native homes #132move-codex-sessionshould handle Codex 0.160.1 and large native homes #132Review
01M4H3YWH68W76A0XM92XBCS33— headc36631d9c2108d7ab07043e1f2946f15b8906d17Review — j4k-oss/agent-skills @
fefbeff71eScope: diff against base tree
40154724b696Status: dispatched — coverage complete (3/3 slots terminal)
Facts: current review-wide projection
Computed under:
Findings (0)
No findings survived.
Reviewed:
Other claims
01M4H429X9XV96F56BXDBQ5EMZlow — The process-availability instructions omit the script's own lock helpersCoverage
Coverage pass: 01M4H3ZD1M7D4XR9AJDDMYKXJT
Accounting: complete
Slot health: healthy
226a1ae2afc36631d9c2