docs: Compare a hint of the orchestrator with the Out of scope section of the issue in the prompt of an agent (#308)

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

Author: codeguru42

docs/dev/pick-the-tickets.md

@@ -156,6 +156,7 @@ When the ticket comes back to the current milestone, the orchestrator starts a n
 The orchestrator writes the prompt of each agent.
 
 - The prompt of an agent gives only the context of its ticket. The context is the issue key, the milestones that are off limits for the agent, the landing order (see ["Land the work"](land-the-work.md#land-the-work)), for a stacked ticket, its parent (see [the stacked-ticket rule](#the-stacked-ticket-rule)), the quota slot and whether the agent has a job (see ["Quota"](quota.md#quota)), the folder of the agent for its files (see the folder bullet of ["Limits"](limits.md#limits)), and the hints for its first refine.
+- A hint of the orchestrator can resolve a conflict. Before the orchestrator gives such a hint, it compares the hint with the Out of scope section of the issue. If the Out of scope section excludes what the hint asks for, the orchestrator does not give the hint. Then the agent reports the conflict under the fifth case of [the stop rule](plan-review.md#the-stop-rule), and the user decides. On #301, a hint asked the plan to extend another hint of the page, but the Out of scope section excluded "A change of other hints".
 - When the orchestrator starts an agent, the orchestrator names the session of the agent after the issue key of its ticket. The orchestrator sets the session name with the `name` option of the Agent tool, for example `name: "codeguru42-tasker-108"`.
   - The list of the options of the Agent tool does not show `name`, but the tool accepts it. The `description` option is not the session name. The M7 orchestrator tested `name` on 2026-10-15. An Agent call with `name: "codeguru42-tasker-nametest"` started the agent with no error. A SendMessage with `to: "codeguru42-tasker-nametest"` reached that agent, and the agent answered. The report of the agent came back from `codeguru42-tasker-nametest`.
   - The session name has the form `<owner>-<repo>-<number>`, for example `codeguru42-tasker-108` for `codeguru42/tasker#108`. The Agent tool refuses a name that does not match `^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$` (tested on 2026-10-14). The issue key itself does not match. The Docs orchestrator tested this on 2026-10-15. An Agent call with `name: "codeguru42/tasker#143"` failed before the agent started, with the error `name must start with a letter or digit and contain only letters, digits, underscores, or hyphens (max 64 chars)`. This error gives the same rule as the pattern. No later session tests the issue key as a name again.