[Bug] buzz-cli @mentions resolve to zero p tags (WITHDRAWN - incorrect report, superseded by #3015)

[Czaruno]

Withdrawn. This report was wrong and I am retracting it.

I filed it believing my @shadow-buzz mentions were going out with zero p tags. They were not. Checking the relay's event store afterwards, every one of those messages carried the correct p tag:

13:22:33  p:390480...  'shadow-claudedesktop here, joined by cla...'
13:28:47  p:390480...  '@shadow-buzz my previous message was sen...'

The mentions resolved and tagged correctly the whole time. What actually happened is that the agent was configured to reply only to its owner, so it ignored them. That is a configuration issue on my side, not a CLI bug. I misread the CLI output, assumed a tagging failure, and reasoned from there.

Both root causes I posted are therefore wrong: the original "sender is not a channel member" claim, and the "mentioned party is not a channel member" correction I posted after that. Neither explains what I actually saw, and the thing I actually saw was not a bug.

One real observation survived the cleanup: when an @name genuinely does not resolve, the CLI says nothing and exits 0. I have filed that on its own, scoped to what I can reproduce, in #3015.

Apologies for the noise.

[Czaruno]

Correcting myself: the trigger in the original filing was wrong. I attributed it to the sender not being a channel member. Leaving the channel and re-sending still produced the p tag, so that is not it.

The real trigger is the mentioned party's membership in the target channel. Same agent, same name, same casing: resolves in a channel it has joined, silently resolves to nothing in a channel it has not. resolve_content_mentions builds its name map from that channel's kind 39002 list only.

Title and body updated. The silent-failure behavior and the code path I pointed at are unchanged.

[Czaruno]

Withdrawing this. The premise was wrong: the mentions were tagged correctly and the agent was ignoring them due to an owner-only reply setting. Body replaced with a retraction. The one reproducible piece, silent failure when an @name does not resolve, is now #3015.