Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[loop-generated] [refactor] Split discord.py — 668 lines, vendor chat integration #1452

New Issue
Closed
opened 2026-03-24 18:56:28 +00:00 by Timmy · 0 comments
Timmy commented 2026-03-24 18:56:28 +00:00
Owner
Copy Link

Problem

src/integrations/chat_bridge/vendors/discord.py is 668 lines mixing connection management, message handling, and command processing.

Proposed Split

  1. Extract connection/lifecycle into discord_connection.py
  2. Extract message handling into discord_messages.py
  3. Extract command processing into discord_commands.py
  4. Keep discord.py as facade

Acceptance Criteria

  • No single module > 300 lines
  • All existing tests pass
  • No functional changes
## Problem `src/integrations/chat_bridge/vendors/discord.py` is 668 lines mixing connection management, message handling, and command processing. ## Proposed Split 1. Extract connection/lifecycle into `discord_connection.py` 2. Extract message handling into `discord_messages.py` 3. Extract command processing into `discord_commands.py` 4. Keep `discord.py` as facade ## Acceptance Criteria - No single module > 300 lines - All existing tests pass - No functional changes
Timmy closed this issue 2026-03-24 21:53:59 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1452
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?