HydraIssues

Problem

A venue has no way to see its own issues. Today the venue team either asks us, or nothing. That is why the Cloud Seven needs in the Secure Inside hand-over doc (#566) sat in a Google Doc instead of the tracker.

We want: a venue contact logs in, sees the venue, and sees every open issue for that venue.

Depends on #545

#545 already covers the identity half: hydravenues authenticates against iamnim itself, authorization is org membership matched against Venue.OrganizationID, and hydramancer stays the front door with a "My venues" panel. Do not duplicate that work here.

This issue is the second half: once a member is scoped to a venue, show that venue's issues.

Depends on the hydraissue venue filter

hydraissue already stores a venue per issue. SessionContext.Venue is set through the session object on POST /api/v1/issues and through the venue form field on POST /report, and IssueSummary.Venue is carried into the index (internal/store/store.go:590).

What is missing is the read path. Store.List takes only status, category, project and activeOnly, and apiListIssues exposes only those. So there is no way to ask for "issues where venue = cloud-seven". That filter is the prerequisite and is filed separately.

Scope here

1. A "Issues" panel on the venue page in hydravenues, visible to members of the venue's organization.
2. It calls the hydraissue list API filtered by the venue id, and shows open issues with id, title, status, priority and a link to issues.experiencenet.com.
3. A "Report an issue" button that deep-links to the hydraissue /report form with venue=<venue id> pre-filled. The report form already reads venue from the query string (internal/api/handlers_web.go:110), so this works with no hydraissue change.
4. hydravenues needs a hydraissue API token to read the list. The list endpoint requires auth today.

Open question

Whether the venue view should show every issue for the venue, including platform-internal ones, or only issues marked as venue-facing. Cloud Seven's list would today include body, stream and network internals that are not useful to a venue manager. Decide before building the panel. A venue_visible flag on the issue is one option.

Note on venue naming

The tracker already holds inconsistent venue values: Rupelmonde and rupelmonde, cloud-seven and cloud-seven / nerdland. Normalize against the hydravenues venue id before the filter goes live, otherwise the venue feed silently misses issues.