session: a worker can stop its own job, and a run's checker is told the work is in its copy

[AbirAbbas]

These two bugs showed up in a default /task run during the fresh-install check of dev 1194d4b8f.

1. A worker could not stop its own job. The bash belt puts jobs, read_document and manual on the wire (Decision 6 of the bash-task-loop design), and the worker's page sends the worker to jobs and read_document. But the one-action envelope refused every call not named bash. A worker's find / had become job 1. The worker called jobs kill and was told jobs was not on this belt, so the walk ran on for the rest of the task.
Now the envelope still allows exactly one call per response, and it refuses only a name the belt does not carry. The page says a job is read and stopped with the jobs tool. A job still running when its task ends was already stopped by the worker seat's close, and a test now proves it.

2. The checker began in the person's checkout. Nothing in a check's opening said where the work was. The only path it held was the footer's working directory, and the project folder's name in that path spells the person's checkout. The checker decoded it (cd /tmp/fxfresh/repo 2>/dev/null || pwd) and read an unrelated diff there. It moved into its own copy only when a write was refused. A check that only reads is never refused, so it could have answered on the wrong tree.
Now the check section says the work is in its working directory, every check and probe runs there, and the person's checkout is not the work.

Manual: how-tasks-run.md gains a section on which folder the checker reads, plus a sentence on stopping jobs. worker-harness.md now says the kept hands are called directly. Both come with probes.

Validation contract

• When a bash-belt worker sends one jobs kill call for a job it started, the call runs, answers job 1 killed, and the job's process group is gone.
• A call naming a tool the belt does not carry is still refused with [not run] no action executed: …. Two calls in one response are still refused.
• Every belt tool the worker page names is one the envelope lets run.
• A job still running when its task ends is gone once the worker's run returns.
• A check's real opening (run.NewBashWorker, a RoleCheck task) says the work is in its working directory and never names the person's checkout.
• The chat belt's jobs tool and the promotion sentence are unchanged.

How it was checked

• The session envelope test and the check-opening test fail on dev and pass here. The end-of-task job test passes on dev as well; it fails if the jobs round in Close is removed.
• make pr-ready: green (see below).
• Hand check: the real binary with every seat on deepseek-v4-flash ($0.014).
  • The worker started sleep 900 in the background, then its trajectory reads jobs kill → job 1 killed and jobs list → killed. No sleep process was left.
  • The checker's first command was cd …/trees/1 (its own copy). Its jobs call was let through.

Follows #1429 / #1485 / #1494 / #1436 review.

🤖 Generated with Claude Code