HydraIssues

Grooming: rewrote title, changed category from bug to improvement, set priority to medium, cleaned up description typos

Nebula's reasoning: This is not a bug — the mailto link works as designed. The ask is for a new behavior: redirecting to issues.experiencenet.com with prefilled session context. That's an improvement. Priority is medium because the current workaround (manual reporting) works, but this would significantly improve the feedback loop from end users. Rewrote the truncated auto-generated title and fixed typos in the description for clarity.

Implemented report form prefilling via URL query parameters.

hydraissue changes:

• Report form handler now extracts query params (title, description, category, project, experience, district, body, head, session_id, body_ip, duration_ms, end_reason, ice_candidate_type, disconnect_count) and passes them to the template
• Template prefills all form fields from these values, with the session context section auto-expanding when session params are present
• Submit handler now captures full SessionContext (all fields, not just experience/district/body/head)
• Deployed to production

hydraneckwebrtc changes:

• Stream-end overlay "Report a problem" link now points to https://issues.experiencenet.com/report with session context as query params instead of mailto:support@experiencenet.com
• SessionInfo struct passes experience, district, and body IP from the Go session to the injected JavaScript
• Link opens in a new tab so users keep the stream-end page

Grooming: no field changes needed — all metadata correct

Nebula's reasoning: Issue is well-scoped with clear acceptance criteria. Category (improvement), priority (high), and project (hydrabody) are all correct. The stream end screen is a key user touchpoint for feedback collection, so high priority is appropriate. Already has an accepted plan — ready for implementation.

Grooming: no changes needed — all fields confirmed correct

Nebula's reasoning: Category (improvement), priority (high), project (hydrabody) are correct. This is a high-value UX improvement — when users encounter stream issues, directing them to the issue tracker with prefilled session context will dramatically improve bug report quality. Status is accepted and partially implemented (report form prefilling done in hydraissue). Remaining work is on the hydrabody stream-end screen side.

Grooming: all fields verified correct — no changes needed

Nebula's reasoning: Category, priority, project, title, and description are all accurate. No duplicates detected, issue is not stale. Marking as groomed.

Grooming: all fields verified correct — no changes needed

Nebula's reasoning: Category, priority, project, title, and description are all accurate and clear. No duplicates detected, issue is not stale (created within last 30 days). Marking as groomed.

Grooming: no changes needed — all metadata verified correct

Nebula's reasoning: Category (improvement), priority (high), project (hydrabody) all correct. Partially implemented (hydraissue prefilling done). No duplicates, not stale. Marking as groomed.

Completed the stream-end report link implementation in hydraneckwebrtc.

The report link already included project, category, title, session_id, experience, district, body, head, body_ip, and disconnect_count. This change adds the three remaining session context fields:

• duration_ms: calculated from stream start time to overlay display
• end_reason: the WebRTC connection state that triggered the overlay (failed, closed, or disconnected)
• ice_candidate_type: captured from WebRTC stats before the overlay is shown

Also updated the runbook to document the report link and its query parameters, and added test step 3d to the streaming-e2e testbook to verify the report link opens with prefilled session context.

Released as v1.10.12 — instances will auto-update.