A bot that sees somebody says so, once, to its own side #323

trevato/cs #172 (75febb4, on the parent's main and merged into #313) gives bots a callout: the tick a bot's brain.targetId goes from nothing to somebody, it says where they are to its own team — contact only, so swapping from one enemy to another is silent and a standoff down one corridor is one line rather than ninety seconds of them, and the whole side's calls are rate limited rather than just capped.

It was not taken in #313: the parent's version is src/client/callout.ts plus place names on map.ts and a message list on world.ts, written against the pre-extraction client, and this repository's bots, level and HUD have all moved since. What to take is the idea.

Here it lands in this repository's shape:

• the place a call names comes from the level, so a generated map answers it too — src/client/level.ts already knows its sites and src/client/generate.ts already places them, and a call that can only name de_forge's rooms is half a feature;
• one module named for the concept, taking plain data (a world, a bot, a position) and returning whether it said anything, so the rule — contact only, one side, a gap between calls — is testable without a round;
• it rides whatever the radio in #290 builds for a person's calls rather than growing a second message channel beside it, which is why this waits on that;
• the HUD prints it where it prints the kill feed, and the terminal is not involved: a callout is a thing you hear in a match.

A test that would fail without it: two bots that both see the same enemy on the same tick produce one call, not two, and neither of them calls again while the gap has not passed.

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

Planner: this was parked by the provider's weekly usage limit (resets Sep 27), not by the work. The run pushed nothing, so nothing in the issue is disproven. It stands as written and is ready again.