A top-level comment and its replies can be resolved by whoever can
change the ticket (CommentThreadResolvedEvent), with an optional
conclusion added as a reply marked as a decision, so it shows above the
ticket. A settled conversation folds to one line (topic, who settled it
and the conclusion) and can be unfolded or reopened; the header counts
the open ones, and finishing the ticket with one open asks first.
«Ana está escribiendo…» shows in the conversation being answered, at
once: a `typing` mutation publishes to a Redis channel per ticket
(`typing` subscription), never stored. In replies, Enter sends and
Shift+Enter breaks the line, except inside lists and code.
API: resolveThread / PUT-DELETE /api/comments/{id}/resolution, Comment
.resolved/resolvedBy/resolvedAt, typing mutation and subscription. MCP:
resolve_thread.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
web-tracker-presenters
Pantallas del tracker con @pi/ui.
- Import:
@task-stream/web/tracker/presenters - Capa:
presenters· Tags:scope:web-tracker,type:presenters
Contenido
- Rutas
trackerRoutes: inicio (proyectos + «Mi trabajo»,pages/my-work.ts), tablero kanban (drag & drop), ticket, releases, seguimiento, estadísticas, actividad, miembros y configuración (con visibilidad y borrado), más «Explorar» (pages/explore.page.ts). Solo la portada exige sesión. ui/:IssueCardComponent,AvatarsComponent,GoToComponent(«Ir a… WEB-12»),ProjectCardComponent,SeriesChartComponent(gráficas SVG de líneas y áreas apiladas) ycopy.ts(textos y tonos; estados, tipos y áreas salen delWorkflowdel proyecto).
Comandos
npx nx lint web-tracker-presenters
Reglas de dependencia entre capas: Arquitectura.