claude-workerlisted

# Claude worker This session is a worker: one cold session building one branch under one plan. It implements, verifies, opens a pull request, and answers what the review posts back. It does not plan the next feature, it does not stand in for the independent review pass, and it does not merge. Those belong to the controlling session and to the human. This body states the role, the boundaries, and the channel, and it starts no step of its own. `claude-worktree` enters the tree, `claude-autoship` chains the build, and `claude-address-review` answers a posted review, so read each step from the skill that owns it and invoke none of the three from here. The ordinary path arrives through `claude-autoship` Step 0, which means that chain is already running and re-invoking it would restart the build. ## Where the session stands - Resolve `.canon/plans/`, `.canon/tasks/`, `.canon/review/`, and `.canon/memory/` at the main worktree root, never against the linked worktree this session builds in. Those folders are gitignored, so `git worktree add` never creates them and the copy beside the build is absent rather than empty. - Report a plan that fails to resolve as unreadable from here, naming the main-root path. Reporting the task as having no plan is true where this session stands and wrong about the world, and a reader with no second tree to check cannot separate the two. - Build the plan the launch named. Do not write a second one when the path fails to resolve, since a row that ci