feat: BoTTube parasocial hooks for audience-aware agents (issue #2286)

[HuiNeng6]

Summary

Implements parasocial hooks that let agents notice and adapt to audience context in BoTTube flows.

Features

1. Audience Tracking (�udience_tracker.py)

• Track viewer/commenter history per agent
• Classify viewers by status (NEW, REGULAR, SUPERFAN, CRITIC, RETURNING)
• Calculate comment sentiment
• Persistent storage in JSON format

2. Personalized Responses (comment_responder.py)

• Status-based response templates
• Boundary enforcement (no creepy/desperate language)
• Rate-limited personalization (~30%)
• Batch response generation

3. Community Shoutouts (description_generator.py)

• Top commenter mentions in video descriptions
• Inspiration acknowledgments
• Weekly community summaries
• Milestone messages

Viewer Statuses

Status	Criteria
NEW	First comment within 7 days
REGULAR	3+ videos commented
SUPERFAN	5+ videos + positive sentiment
CRITIC	3+ videos + negative sentiment
RETURNING	Back after 30+ day absence

Boundaries Enforced

• No creepy phrases (tracking viewing times, specific patterns)
• No desperate language (pleading for return visits)
• Natural frequency - not every comment gets personalized

Testing

Run: \python -m pytest tests/test_parasocial_hooks.py -v\

Note: Test file being added via separate commit due to upload size.

RTC Payout Wallet

9dRRMiHiJwjF3VW8pXtKDtpmmxAPFy3zWgV2JY5H6eeT

Closes

#2286

[Scottcjn]

Merged — excellent work on bounty #2286 (25 RTC). This is a well-structured Python package with proper dataclasses, enums, boundary enforcement (no creepy/desperate language), and 33 tests. The audience tracking + personalized response system is exactly what BoTTube agents need.

A few observations for future refinement:

• The sentiment analysis is word-list-based (noted in the docstring) — good enough for v1
• JSON file storage works for single-agent but would need SQLite for multi-agent deployments
• The BOUNTY_2286_IMPLEMENTATION.md at repo root is a bit noisy — future PRs can keep bounty docs in the module README

Wallet noted from PR body: 9dRRMiHiJwjF3VW8pXtKDtpmmxAPFy3zWgV2JY5H6eeT — is this a Solana address? Please provide an RTC wallet address (starts with RTC or a named identifier) for payout.

[Scottcjn]

@HuiNeng6 — want to take a moment to recognize your work here.

This parasocial hooks PR had 33 tests, proper dataclasses, enums, boundary enforcement, and clean Python packaging. That is the standard we look for. Combined with your embed fix on BoTTube (#587), you are building a real track record.

Total earned: 30 RTC (25 parasocial + 5 embed fix).

Your Agent Mood (#586) and Agent Beef (#582) PRs are also solid foundations — they just need the integration hooks and companion modules to be mergeable. The feedback is specific because the code quality is there.

We notice you also contribute to SolFoundry. That is completely fine — contributors are free to work wherever they want. But we think you will find that RustChain pays for real code at fair rates, and the work here ships to production.

Please reply with your RTC wallet address (format: RTCxxxxxxxx). We do not use Solana addresses for RTC payouts.

Welcome aboard. Keep building like this.

[FlintLeng]

Nice work on this PR — clean implementation with good attention to edge cases.

[FlintLeng]

PR #1811 — Review (bounty #2286):

BoTTube Parasocial Hooks implementation documentation. Covers agents that notice their audience. Complete bounty submission. ✅