The insights reading grows (GraphQL insights(since:), REST ?since=, MCP): - planned releases with a likely (p50) and safe (p85) finish date from a Monte Carlo over the last six weeks of finished work, one after another, and a verdict against their target; - with `since` (the viewer's last visit, kept in the browser): tickets created, finished and sent back from QA, and their mentions; - each person's open points against what they closed per sprint lately; - open tickets without estimate, area or assignee, or untouched for 90 days, each count opening the list filtered (new noEstimate, noArea and updatedBefore filters). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
api-tracker-infrastructure
Adaptadores de salida del tracker.
- Import:
@task-stream/api/tracker/infrastructure - Capa:
infrastructure· Tags:scope:api-tracker,type:infrastructure
Contenido
postgres/: lookups de escritura (project_keys,issue_sequences,release_names),ReleaseIssuesRepositoryyTrackerStreamsRepository(consultan el event store: tickets y releases de un proyecto, comentarios y enlaces de un ticket).mongo/: esquemas del read model (incluida la línea temporalissue_timeline), repositoriosFind*yUpsertMaterialized*(upsert idempotente por versión) yStatusCategoryBackfill(al arrancar, rellena la categoría del estado en los tickets proyectados antes de existir).realtime/:RedisChangeFeed(canales de Redis pub/sub por proyecto, ticket y usuario).identity/:IdentityUserDirectory, capa anticorrupción hacia el contexto de identidad.
Comandos
npx nx lint api-tracker-infrastructure
npx nx test api-tracker-infrastructure # Jest
Reglas de dependencia entre capas: Arquitectura.