A project keeps a list of repositories (api, web, admin…), each with its own secret, instead of a single webhook secret. They all call the same URL; the secret that verifies the signature tells which one it was, and every commit, branch or pull request is linked with its repository's name (shown on the ticket and in the MCP). Rotating or removing one leaves the others alone, and what it linked stays. A project that had turned the single webhook on keeps its secret, as a repository named "principal". API: the enable/disable endpoints and mutations give way to adding a repository, rotating its secret and removing it (REST and GraphQL). The web settings card lists the repositories. Docs, Word and PDF updated. 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.