Show name clashes on proposed coworkers and skills, and let skill reads see loaded skills

[davidmckayv]

Problem

When a Bot that holds bot-creator or skill-creator proposes a coworker or a skill:

• A coworker named like one already on the roster is offered as "Create Researcher", never "Create Researcher, again" with the clash warning.
• A skill whose slug would replace an existing skill is offered as "Create /weekly-summary", never "Replace /weekly-summary" with whose skill it overwrites.
• list_skills tells the Bot "No skills exist here yet. Any slug is free." while skills exist, and read_skill / list_skill_tools answer from the same empty list.

Cause

The same one #777 fixed in the sign-in card. CopilotKit's useFrontendTool (and useHumanInTheLoop, which calls it) registers a tool when its name, available or deps change, and keeps that renderer and handler. Both tools turn on in the render where the Bot's grant arrives, which is also the render that first asks for the roster and the skills, so the kept card and handlers closed over the empty lists from before those queries loaded, and never saw them.

Fix

• bot-tools.tsx: the save_bot card is now a module-level component that reads the roster with its own useQuery(agentListQueryOptions()) and owns its useMutation. The three read tools already fetch at call time (lib/agents/answers.ts).
• skill-tools.tsx: the save_skill card is a module-level component reading the plugins page and the current user with its own queries. list_skills, read_skill and list_skill_tools fetch at call time with ensureQueryData, as the coworker reads do.

Module scope also keeps the card's identity stable, which is what the old useMemo was for.

How tested

app/tests/authoring-tool-cards.test.tsx uses the real CopilotKitProvider and the real hooks, with no SDK mocks and no mock.module. It captures the renderer and handlers the SDK actually kept, lets the roster and skills arrive after the grant (the order a first visit sees), then draws the card and calls the handlers. On main, all three fail:

Unable to find an element with the text: Create Researcher, again.
(fail) a proposed coworker named like an existing one says so
Unable to find an element with the text: Replace /weekly-summary.
(fail) a proposed skill that would overwrite an existing one says so
Expected to contain: "/weekly-summary — Weekly summary (yours)"
Received: "No skills exist here yet. Any slug is free."
(fail) the skill reads tell the Bot about skills that loaded after the tools turned on

With the fix all three pass. Lint, format, typecheck, the app suite (1294 pass) and bun run build are green locally. The file runs in the CI tests job via bun run test:ci.

Suspected but not bugs

• gallery-tools.tsx refusals: the kept renderer does read a stale map, but nothing visible depends on it. The handler sets the refusal and returns NOT_SHOWN + title + reason in the same step, and the renderer's stored-result branch decodes exactly that reason into the same RefusedCard. The map can only be read before the result exists, and before that the handler has not refused yet. isHeld is passed as available, so it re-registers. Left alone.
• createAgent / saveSkill: stale objects, but mutateAsync is the persisted MutationObserver's mutate, so a kept copy still creates against current state. They moved into the cards anyway as part of the restructure.