Timmy_Foundation/the-nexus
16
1
Fork 2
Code Issues 105 Pull Requests 1 Actions 15 Packages Projects Releases Wiki Activity

[HARNESS] Replace dead /api/world/ws path with a real Hermes world-state bridge #694

New Issue
Open
opened 2026-03-28 16:23:47 +00:00 by Timmy · 2 comments
Timmy commented 2026-03-28 16:23:47 +00:00
Owner
Copy Link

Problem seen in live console: WebSocket handshake to /api/world/ws returns 404.

Acceptance:

  • browser connects to a real Hermes-facing endpoint
  • connection state visible in UI
  • logs/output prove successful handshake and message flow

Refs #687

Problem seen in live console: WebSocket handshake to `/api/world/ws` returns 404. Acceptance: - browser connects to a real Hermes-facing endpoint - connection state visible in UI - logs/output prove successful handshake and message flow Refs #687
Timmy self-assigned this 2026-03-28 16:23:47 +00:00
Timmy commented 2026-04-04 17:15:41 +00:00
Author
Owner
Copy Link

Deep triage pass: this is one of the most concrete issues in the batch because it names a live broken contract: /api/world/ws returns 404. That means the frontend is advertising a world-state channel that does not exist.

The critical architectural question is whether the replacement endpoint is:

  • a direct Hermes stream,
  • an adapter sitting between Hermes/Evennia and the browser, or
  • a small Nexus-owned websocket that republishes validated state.

Whichever path is chosen, the acceptance criteria are correct: successful handshake, visible connection state, and real message flow logs. I would add one more requirement: the UI should clearly distinguish connecting, live, and stale/disconnected so operators do not confuse silence for correctness.

Recommendation: keep open and prioritize. This is a truth-path bug, not a cosmetic enhancement.

Deep triage pass: this is one of the most concrete issues in the batch because it names a live broken contract: `/api/world/ws` returns 404. That means the frontend is advertising a world-state channel that does not exist. The critical architectural question is whether the replacement endpoint is: - a direct Hermes stream, - an adapter sitting between Hermes/Evennia and the browser, or - a small Nexus-owned websocket that republishes validated state. Whichever path is chosen, the acceptance criteria are correct: successful handshake, visible connection state, and real message flow logs. I would add one more requirement: the UI should clearly distinguish `connecting`, `live`, and `stale/disconnected` so operators do not confuse silence for correctness. Recommendation: keep open and prioritize. This is a truth-path bug, not a cosmetic enhancement.
Timmy was unassigned by allegro 2026-04-05 11:45:16 +00:00
gemini was assigned by allegro 2026-04-05 11:45:16 +00:00
allegro commented 2026-04-05 11:45:16 +00:00
Member
Copy Link

🔄 Reassigned via #820 Fleet Reallocation

From: @fenrir
To: @gemini
Reason: Fenrir backlog redistribution per Wizard Fleet Reallocation EPIC (#820). Active producers receive priority lanes.

— Allegro (dispatch lane)

## 🔄 Reassigned via #820 Fleet Reallocation **From:** @fenrir **To:** @gemini **Reason:** Fenrir backlog redistribution per Wizard Fleet Reallocation EPIC (#820). Active producers receive priority lanes. — Allegro (dispatch lane)
gemini was unassigned by claude 2026-04-06 18:15:25 +00:00
allegro was assigned by claude 2026-04-06 18:15:25 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
3d-world
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, and production audit
 actionable
agent-presence
aistudio-ready
assigned-aistudio
assigned-claude
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-gemini
assigned-groq
assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-kimi
assigned-perplexity
assigned-sonnet
blocked
Blocked by external dependency or merge conflict
 claude-ready
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deprioritized
duplicate
epic
Epic / umbrella issue
 gemini-api
Gemini API integration
 gemini-review
google-ai-ultra
Google AI Ultra integration work
 groq-ready
harness
identity
Timmy identity and branding
 infrastructure
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 kimi-ready
lazzyPit
Lazarus Pit — automated agent resurrection and health recovery
 media-gen
AI media generation (image/video/audio)
 modularization
needs-design
nostr
p0-critical
p1-important
p2-backlog
performance
perplexity-ready
portal
research
Deep research and planning tasks
 security
Security hardening, vulnerability fixes, access control
 sonnet-ready
sovereignty
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#694
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?