[pournasserian]

Closes #2625

What

Follow-ups from the independent review of #2594 (F-DSK, #2422). No scoping leak was found; these close the test gaps and tighten what agents are told.

• Tool descriptions. get_desk_counts, list_desk_queue and get_change_set_review say an agent sees only the change sets it opened, so a count of 0 doesn't read as an empty desk.
• get_change_set_review reads the set and its moves again when the last move disagrees with the set's state, up to three times. A decision that commits between the two reads no longer gives an answer that disagrees with itself.
• ChangeSetMoves.StateAfter names the state each move leaves a set in. The review tool uses it, and a test ties it to the directory.
• ConnectedAgent.AnotherAgentAsync connects a second agent to the same host for tests.

Why

• Read again rather than derive the state from the moves. The rejection reason lives on the set, not in the move event, so only a fresh read of both gives a consistent answer.

Tests

On SQLite and PostgreSQL:

• Another agent's sets are not counted, listed or readable over MCP, while that agent sees its own. This exercises the credential-id half of the OpenedBy filter.

• Every queue through list_desk_queue:

  • recently_published lists newest first and leaves out a set published eight days earlier.
  • reverted lists the reverted set.
  • stale_facts pages two and then one of three, with the total on both pages.
  • The counts match.

• No tool call appends an event, get_change_set_review included.

• Every move the directory makes appends exactly one known move, and StateAfter names the state the move left. The set goes through:

  • open, submit, checks failed, reopen, submit and awaiting review;
  • approve and publish;
  • a published revert, which reverts the original;
  • a rejection.

  All nine move names are seen.

dotnet build -warnaserror, the unit and bUnit suite and the desk, desk tools and queue tests on SQLite and PostgreSQL pass locally. No new package and no new project reference.

Checklist

• Linked to an issue a maintainer has confirmed
• Targets v2
• Tests or docs updated where behaviour changed
• No tool-generated co-author trailers or footers