Greptile Summary

This PR adds passive message:received hook emission for mention-skipped group messages in both Telegram and Signal, controlled by a new ingest?: boolean flag on group/topic config objects. The schema, types, and Telegram implementation are clean and consistent with how other group policies (e.g. requireMention) are resolved. One logic issue was found in the Signal path.

• Config surface (src/config/group-policy.ts, types.signal.ts, types.telegram.ts, zod-schema.providers-core.ts): ingest?: boolean added correctly to all relevant types and Zod schemas with JSDoc comments.
• Telegram (bot-message-context.body.ts, bot-message-context.ts): Hook dispatch uses topicConfig?.ingest ?? groupConfig?.ingest — the nullish-coalescing correctly gives topic-level config priority over group-level config, matching how requireMention resolution works elsewhere.
• Signal (event-handler.ts): The ingest check uses groupConfig?.ingest === true || defaultConfig?.ingest === true. This || means a specific group with ingest: false cannot override a wildcard * entry with ingest: true, which is inconsistent with Telegram's ?? semantics and with how requireMention priority is resolved. A group-specific opt-out would be silently ignored.
• Tests: New focused test files cover the happy path for both channels. The Telegram test references anthropic/claude-opus-4-5 as a placeholder model string where project guidelines prefer sonnet-4.6.

Confidence Score: 3/5

Mostly safe, but the Signal ingest precedence bug means a group-specific ingest: false can be overridden by the wildcard ingest: true, producing unintended hook emissions.

The Telegram and schema changes are clean. The Signal implementation has a logic bug in how group-specific vs. wildcard config precedence is handled — it uses || where ?? is needed. While not a crash, this silently breaks explicit per-group opt-outs if a wildcard default is also set.

extensions/signal/src/monitor/event-handler.ts — the ingest condition on lines 733-736 needs the || replaced with nullish-coalescing to match Telegram semantics and the rest of the policy resolution pattern.

This is a comment left during a code review.
Path: extensions/signal/src/monitor/event-handler.ts
Line: 733-736

Comment:
**Group-specific `ingest: false` cannot override wildcard `ingest: true`**

The `||` condition means: if the specific group has `ingest: false` but the wildcard `*` entry has `ingest: true`, the hook still fires — the group-specific opt-out is silently ignored.

For example:
```yaml
channels:
  signal:
    groups:
      "group-abc":
        requireMention: true
        ingest: false   # explicit opt-out for this group
      "*":
        requireMention: true
        ingest: true    # default for other groups
```

With the current code `false === true || true === true` evaluates to `true` and the hook fires for `group-abc`.

The Telegram counterpart correctly uses `??` (nullish-coalescing) to give the specific group config priority over the wildcard, and `resolveChannelGroupRequireMention` in `group-policy.ts` applies the same precedence rule for `requireMention`. The ingest flag should follow the same pattern:

```suggestion
      if (
        (signalGroupPolicy.groupConfig?.ingest ?? signalGroupPolicy.defaultConfig?.ingest) === true
      ) {
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/telegram/src/bot-message-context.silent-ingest.test.ts
Line: 51-53

Comment:
**Test model constant doesn't match project preference**

The project guidelines (CLAUDE.md) ask to prefer `sonnet-4.6` for example Anthropic model constants in tests. This placeholder uses `anthropic/claude-opus-4-5`.

```suggestion
          model: "anthropic/sonnet-4.6",
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(channels): emit passive hooks for me..." | Re-trigger Greptile}

Landed.

Commits:

• Landing commit: 69571b6
• Merge commit: 251fa72