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

[kimi-task] [feat] Add system_status message producer #681

New Issue
Closed
opened 2026-03-21 03:12:13 +00:00 by kimi · 1 comment
kimi commented 2026-03-21 03:12:13 +00:00
Collaborator
Copy Link

Epic: Matrix Unification

Task

Create produce_system_status() -> dict in src/infrastructure/presence.py that generates
a system_status message for the Matrix. This tells the frontend about system health.

Files

  • src/infrastructure/presence.py — add produce_system_status()
  • tests/unit/test_presence.py — add tests

Acceptance Criteria

  • Returns dict with type="system_status", data={agents_online, visitors, uptime_seconds, thinking_active, memory_count}
  • agents_online: count of agents with status != offline
  • visitors: count from VisitorRegistry
  • uptime_seconds: time since server start
  • thinking_active: bool from thinking engine state
  • memory_count: total memories in vector store
  • tox -e unit passes
  • tox -e lint passes

Context

The Matrix PROTOCOL.md specifies system_status but it was never implemented.
The Matrix style.css has an elaborate status panel (currently dead CSS) that will use this.

## Epic: Matrix Unification ## Task Create `produce_system_status() -> dict` in `src/infrastructure/presence.py` that generates a system_status message for the Matrix. This tells the frontend about system health. ## Files - src/infrastructure/presence.py — add produce_system_status() - tests/unit/test_presence.py — add tests ## Acceptance Criteria - [ ] Returns dict with type="system_status", data={agents_online, visitors, uptime_seconds, thinking_active, memory_count} - [ ] agents_online: count of agents with status != offline - [ ] visitors: count from VisitorRegistry - [ ] uptime_seconds: time since server start - [ ] thinking_active: bool from thinking engine state - [ ] memory_count: total memories in vector store - [ ] tox -e unit passes - [ ] tox -e lint passes ## Context The Matrix PROTOCOL.md specifies system_status but it was never implemented. The Matrix style.css has an elaborate status panel (currently dead CSS) that will use this.
kimi self-assigned this 2026-03-21 03:12:13 +00:00
kimi commented 2026-03-21 15:12:43 +00:00
Author
Collaborator
Copy Link

✅ Task Complete

PR created: #743

What was implemented

produce_system_status() in src/infrastructure/presence.py generates system health messages for the Matrix with:

  • agents_online: Count of agents with status != offline
  • visitors: WebSocket client count
  • uptime_seconds: Server uptime
  • thinking_active: Thinking engine state
  • memory_count: Total memories in vector store

Design highlights

  • Graceful degradation: all data collection wrapped in try/except blocks
  • Never crashes even when dependencies fail
  • Follows existing Matrix protocol patterns

Tests

10 new test cases covering structure, types, error handling, and edge cases.

Verification

  • ✅ tox -e format (clean)
  • ✅ tox -e unit (2574 passed)
  • ✅ tox -e lint (clean)
  • ✅ tox -e pre-push (full CI suite)
## ✅ Task Complete PR created: [#743](http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/743) ### What was implemented **`produce_system_status()`** in `src/infrastructure/presence.py` generates system health messages for the Matrix with: - `agents_online`: Count of agents with status != offline - `visitors`: WebSocket client count - `uptime_seconds`: Server uptime - `thinking_active`: Thinking engine state - `memory_count`: Total memories in vector store ### Design highlights - Graceful degradation: all data collection wrapped in try/except blocks - Never crashes even when dependencies fail - Follows existing Matrix protocol patterns ### Tests 10 new test cases covering structure, types, error handling, and edge cases. ### Verification - ✅ tox -e format (clean) - ✅ tox -e unit (2574 passed) - ✅ tox -e lint (clean) - ✅ tox -e pre-push (full CI suite)
kimi closed this issue 2026-03-21 15:13:02 +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 kimi
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#681
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?