Console: Organization Threads section (list + detail)

[rowan-stein]

User request

Implement Console feature: Organization → Threads section where an org admin can list and view threads.

Source of truth: agynio/architecture/product/console/console.md → Threads.

Requirements (from spec):

• Read-only view of all threads in an org.
• Access:
  • Organization owners
  • Cluster admins (must be granted via OpenFGA model, not hardcoded checks)
• Org Threads list:
  • Columns: truncated ID, participants (@nicknames), message count, status (active/archived), created date
  • Default sort: newest-first
  • Cursor pagination with “Load more”
• Thread detail:
  • Participants
  • Paginated messages newest-first
  • Sender @nickname, timestamp, body
  • Attachments as named download links (no mutation)

Decision: No backfill required for pre-existing threads that lack organization_id.

---

Specification (implementation notes from research)

This feature requires coordinated changes across services/repos.

1) Authorization model (agynio/authorization)

• Add organization.can_view_threads computed relation:
  • can_view_threads = owner OR admin from cluster
• Update terraform/model.fga.yaml tests:
  • org owner → can_view_threads = true
  • org member → can_view_threads = false
  • cluster admin → can_view_threads = true

2) Ensure … from cluster works for new orgs (agynio/organizations)

• On CreateOrganization, write structural tuple:
  • cluster:global#cluster@organization:<orgId>
• Update rollback logic to delete both tuples when needed.
• Update ListAccessibleOrganizations to be model-driven but include cluster admins:
  • union results of ListObjects(relation=member) and ListObjects(relation=can_add_member).

3) Threads org-scoping + APIs (agynio/threads + agynio/api + agynio/gateway)

• DB:
  • Add threads.organization_id (nullable for historical rows; required/populated for new threads)
  • Add threads.message_count (maintained counter; initialized at 0 for new threads)
• ThreadsService:
  • Require/derive org ID on CreateThread and persist to threads.organization_id
  • Increment message_count on SendMessage
  • Add RPCs:
    • ListOrganizationThreads(organization_id, page_size, page_token, [status])
    • GetThread(thread_id)
  • Add newest-first message pagination support:
    • add explicit order param on GetMessagesRequest (keep existing default to avoid breaking clients)
• Authorization enforcement (Threads service):
  • ListOrganizationThreads / GetThread must require OpenFGA Check(can_view_threads, organization:<orgId>).

4) Console UI (agynio/console-app)

• Routes:
  • /organizations/:id/threads (list)
  • /organizations/:id/threads/:threadId (detail)
• Add Threads nav item under Organization (after Members, before Monitoring).
• Cursor pagination with “Load more”.
• Attachments:
  • FilesGateway.GetFileMetadata for name
  • FilesGateway.GetDownloadUrl on click
• Participant nickname display:
  • Best-effort resolution via existing Users/Agents APIs; expose AppsService.GetAppProfile via Gateway if needed.
  • Fallback to truncated IDs when nickname cannot be resolved.

5) Tests

• Authorization model tests.
• Threads service tests:
  • org-scoped list/detail + pagination + authz
  • message pagination newest-first
• Console: Playwright e2e list→detail→pagination.

---

Acceptance criteria

• Org owner can navigate to Org → Threads, see a paginated list, open a thread, and load more messages.
• Cluster admin can do the same, with permissions coming from OpenFGA (no hardcoded cluster-admin checks in services).
• Threads list is org-scoped; pre-existing threads without organization_id do not appear.
• Messages can be paged newest-first per spec.

[rowan-stein]

Update (2026-04-19): rename legacy tenants org-service name to organizations

New requirement: the Organizations service should be called organizations (not tenants) everywhere.

Current state (why CI/e2e had to reference tenants)

Inventory from Emerson:

• bootstrap (agynio/bootstrap/stacks/platform/main.tf)
  • Deploys the organizations chart with fullnameOverride = \"tenants\" and ArgoCD app name tenants.
  • Configures gateway to dial organizationsGrpcTarget = \"tenants:50051\".
• agents-orchestrator: devspace + e2e defaults use tenants:50051.
• llm-proxy: devspace + e2e defaults use tenants:50051.

Proposed safe migration (keeps CI and environments stable)

1. Add temporary compatibility so both organizations:50051 and tenants:50051 resolve (K8s Service alias).
2. Update bootstrap to deploy the org service as organizations and point gateway at organizations:50051.
3. Update all callers/devspace/e2e defaults to use organizations:50051.
4. Remove legacy tenants alias after a deprecation window.

Recommendation

Defer renaming DB resources (tenants-db, db/user names) to a separate migration (higher risk; not required for this feature).

[rowan-stein]

New requirement (2026-04-19): add an Argos/Playwright screenshot for the thread detail view (thread messages list) as part of PR #68.