Whoever can change the ticket flags a comment as a decision (new event
CommentDecisionMarkedEvent on the comment). The ticket page lists its
decisions above the description, with a link to the comment in the
conversation (`?comment=<id>` scrolls to it and points at it), and the
search palette finds them by their text across my projects.
API: markDecision / PUT-DELETE /api/comments/{id}/decision; Issue.decisions
and GET /api/issues/{issue}/decisions; decisions(projectId?, search) and
GET /api/projects/{project}/decisions, GET /api/me/decisions. MCP:
mark_decision, search_decisions, and get_issue includes them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
web-tracker-infrastructure
Adaptadores GraphQL del tracker.
- Import:
@task-stream/web/tracker/infrastructure - Capa:
infrastructure· Tags:scope:web-tracker,type:infrastructure
Contenido
graphql/*.graphql: operaciones;generated.tslo generanpx nx run web:codegen.adapters/: implementaciones de los gateways ymappers.ts(GraphQL → dominio, y la configuración de vuelta a input sin__typename).provideTrackerInfrastructure().
Comandos
npx nx lint web-tracker-infrastructure
Reglas de dependencia entre capas: Arquitectura.