feat: implicit handover on owner reply + sliding TTL

[keiravoss94]

Dependency

Requires hermes-agent commit b1e7628d7 (PR pebble-tech/hermes-agent#1) which adds the opt-in WHATSAPP_FORWARD_OWNER_MESSAGES env var and propagates MessageEvent.metadata[\"whatsapp_from_owner\"] from the WhatsApp bridge. Without that change the metadata flag never appears and the new code paths in this PR are inert.

Why

Two gaps with the existing handover flow:

1. No safety-net activation. Handover was activated only via the agent-callable trigger_handover tool. If the agent missed the cue and the owner stepped in manually, the bot kept replying alongside the owner.
2. TTL was set once at activation and never refreshed. A long owner-driven conversation could time out mid-chat while the owner was still actively replying.

How

Both behaviours hang off the same metadata signal — event.metadata.get(\"whatsapp_from_owner\") — so a profile that doesn't enable the env flag on hermes-agent sees no behaviour change.

state.py: HandoverStore.touch(platform, chat_id, ttl_seconds) -> bool

Single SQL UPDATE that slides expires_at to now + ttl_seconds. Idempotent:

• Returns False on cold rows.
• Returns False on rows with expires_at IS NULL (operator chose no TTL — don't surprise them).
• Returns True and updates otherwise.

rules/handover.py: owner-reply branch with explicit ordering

/takeback + owner-source check        ->  deactivate (existing path, now first)
event.metadata.whatsapp_from_owner    ->  activate-or-extend
existing active handover (customer)   ->  silent ingest (unchanged)

The /takeback branch beats the owner-implicit branch so an owner exiting via the command still wins, even though the same fromMe inbound also carries the metadata flag.

Owner-implicit activation uses reason=\"owner_reply\", activated_by=\"owner_implicit\", and never calls notify_owner — the owner is already in the chat, so a Telegram ping would be noise. On a hot chat the rule just calls touch(...) and silent-ingests the event so the transcript captures it.

Tests

8 new tests in tests/test_rules.py (suite goes 34 → 42 passing):

• touch() no-op on cold and no-TTL rows; slides forward on hot rows.
• Owner inbound activates with activated_by='owner_implicit', no notify.
• Owner inbound on hot chat slides TTL, doesn't overwrite original activated_by, no notify.
• Customer inbound (flag absent) does not touch TTL.
• /takeback with owner flag still deactivates (ordering guard).
• Bot's own outbound (flag absent) is a no-op.

Profile config

After this merges, profiles that want the new behaviour add WHATSAPP_FORWARD_OWNER_MESSAGES=true to their .env. Profiles that don't are unaffected.

[coderabbitai]

Warning

Rate limit exceeded

@keiravoss94 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 25 minutes and 41 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 67d8d407-2a03-4236-ac39-dfc0e5d73b9f

📥 Commits

Reviewing files that changed from the base of the PR and between 04d2391 and 4763c88.

📒 Files selected for processing (3)

• rules/handover.py
• state.py
• tests/test_rules.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/handover-sliding-ttl-and-owner-reply

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}