fix: hand the model the configured repos and tag only the reporters

[cgaravitoq]

Summary

• 76bb168 feat: offer the configured repos as the tool's repo enum
• b522749 fix: keep Bloop and every other bot out of the reporters
• HEAD: b522749

The wave-end E2E on staging measured two defects in one flow: "delega este bug al conductor del Mac" made the model call delegate_to_conductor with repo "Mac", and the approval message read "Reporters: <@owner> <@Bloop>".

repo is now v.picklist(config.repos) instead of v.string(), which Flue renders for the model as a JSON-schema enum, and the tool description names the same repos. With a single configured repo the request still has to name it: the enum has one value and there is no default. The code-level refusal of an unconfigured repo stays.

readRawSlackThread (packages/core/src/read.ts) now marks every message that carries a bot_id or whose user is the bot's own user id, read from the auth.test answer it already makes. Only non-bot messages feed the reporters, so Bloop and any other bot in the thread are no longer tagged. The stored and dispatched raw thread keeps every message in the {ts, author, text, permalink} shape the Task contract pins.

Verify

Gates, on b522749, after bun install --frozen-lockfile:

• bun run format:check, bun run lint, bun run typecheck: clean
• bun test: 361 pass, 0 fail (17 files)
• bun run knip: clean
• bun run deploy:dry: uploads the staging Worker dry-run
• bun audit --ignore=GHSA-vfj7-8cjw-p6xm: no vulnerabilities
• bun run verify: same sequence, green

Each new test fails on 9039b05 with only the source changes reverted:

• the tool offers exactly the configured repos as the repo the model must name: expect(received).toEqual(expected) with - ["example", "right-hand"] against + undefined (the base input had no .options), and v.parse accepts "Mac" on the base.
• reporters leave out Bloop's own replies and every bot message: expect(stored?.task.reporters).toEqual(["U2", "U1"]) received ["U2", "U1", "UBOT", "UBUILDER"]; the fixture's bot messages carry both a bot_id and a user id, which is the shape Slack sends for a bot reply and the only shape the base filter let through. A bot_id-only message was already dropped by the base user-id filter.

CI: the verify job passed on b522749, 361 tests, in https://github.com/cgaravitoq/agentic-slack/actions/runs/37644245884

Not covered

• The live re-run on staging of the wave-end E2E: the conductor runs it after the pin.