Messages can be tagged as coming from a Slack ping, but nothing in this build creates one.
A Slack-ping message origin is plumbed through display and queueing with no code path producing it.
What's wrong with this entry?
A new message origin kind for Slack pings is wired through message display, prompt queueing, system-reminder wrapping and harness tag neutralisation, with its own equality check over channel, thread, message, Slack user, sender name and permalink. No code path in this build produces an origin of this kind.
- A Slack origin field is passed from the inbound bridge payload into the origin classifier, which currently ignores the argument
- The classifier's two Slack observation checks are hard-coded to return false
slack-ping
Strings lifted out of the shipped bundle, so the claim above can be checked against them.