Resumen (3 líneas máx): sbg-portal es un proyecto nuevo (primer commit: 24 jun 2026, dentro del período). Sin backlog de Jira todavía, todo el trabajo del período se reconstruye desde GitHub: 1 PR mergeado a main y 8 commits humanos de Oscar Cortez que scaffoldearon el portal Next.js y le agregaron una sección de Self-reports completa. No hay CI configurado ni releases todavía.
⚠️ Nota de alcance Jira: sbg-portal no tiene tickets propios en Jira todavía. Está mapeado únicamente al épico paraguas SD-1456 "SBG Internal Tools" (compartido con sbg-pm), que existe como placeholder recién creado y sin issues hijos en este período. Esta sección "comprometido vs completado" se reemplaza por "shippeado vía commits/PRs" porque no hay backlog de tickets contra el cual comparar. No se inventó actividad de Jira para este proyecto.
| Comprometido (Jira) | No aplica — sin backlog de tickets (SD-1456 vacío) |
| Shippeado (GitHub) | 1 PR mergeado · 8 commits humanos · 10 commits automáticos de sync |
| Contribuyentes | 1 — Oscar Cortez (oscarcortez) + bot sbg-pm bot (sync automático, no es una persona) |
| Carry-over | N/A — sin backlog de tickets que arrastrar |
| Alcance agregado | N/A — todo el trabajo del período es alcance nuevo (repo creado el 24 jun) |
main) — reorganiza el listado de reportes por área y establece el sidebar base del portal.
0b09f3a, 24 jun) — Next.js 16 + Tailwind v4 + shadcn/ui, static export (para publicar en Cloudflare Pages).
13725f9, 188762e, 1eabf4f, 13b6aaf, a00a79a, 30 jun) — nueva vista del sidebar con tarjetas por persona; el portal pasó a "ser dueño" de los self-reports (servidos desde public/self-reports/) en lugar de solo reflejar HTML sincronizado; se corrigió el link del self-report de Oscar (a00a79a); se migró/reflejó el HTML físico de self-reports automáticamente.
publish: sync PM-brain content from sbg-pm@<sha> (24–30 jun) — el pipeline de publicación que sincroniza contenido generado en sbg-pm hacia este portal está operativo y corriendo repetidamente durante el período.
.github/workflows no existe) y varios commits fueron directo a main sin PR (solo 1 de 8 commits humanos pasó por PR).
main + 10 commits automáticos de sync. 18 commits en total en el historial completo del repo (todo el historial cae dentro de este período, porque el repo se creó el 24 jun).
main sin PR — aceptable en fase de scaffold de un proyecto de 1 dev, pero conviene formalizar el flujo de PR antes de sumar más contribuyentes. (2) No hay CI (lint/build/tests) configurado — riesgo de regresiones silenciosas dado que el sitio es estático y se publica sin gate automático. (3) Sin tickets Jira, no hay trazabilidad de "por qué" se hizo cada cambio más allá del mensaje de commit — vale la pena abrir issues bajo SD-1456 a medida que el portal crezca.
Summary (max 3 lines): sbg-portal is a brand-new project (first commit: Jun 24, 2026, inside this period). With no Jira backlog yet, this period's work is reconstructed entirely from GitHub: 1 PR merged to main and 8 human commits from Oscar Cortez that scaffolded the Next.js portal and shipped a full Self-reports section. No CI is configured yet and no releases have been cut.
⚠️ Jira scope note: sbg-portal has no tickets of its own in Jira yet. It is mapped only to the umbrella epic SD-1456 "SBG Internal Tools" (shared with sbg-pm), a freshly created placeholder with no child issues in this period. The "committed vs done" section below is replaced with "shipped via commits/PRs" since there's no ticket backlog to compare against. No Jira activity was invented for this project.
| Committed (Jira) | N/A — no ticket backlog (SD-1456 is empty) |
| Shipped (GitHub) | 1 merged PR · 8 human commits · 10 automated sync commits |
| Contributors | 1 — Oscar Cortez (oscarcortez) + sbg-pm bot (automated sync, not a person) |
| Carry-over | N/A — no ticket backlog to carry over |
| Scope added | N/A — all work this period is new scope (repo created Jun 24) |
main) — reorganizes the reports listing by area and lays down the portal's base sidebar.
0b09f3a, Jun 24) — Next.js 16 + Tailwind v4 + shadcn/ui, static export (for Cloudflare Pages publishing).
13725f9, 188762e, 1eabf4f, 13b6aaf, a00a79a, Jun 30) — new sidebar space with per-person cards; the portal became the owner of self-reports (served from public/self-reports/) instead of just mirroring synced HTML; fixed Oscar's self-report link (a00a79a); auto-migrated physical self-report HTML files.
publish: sync PM-brain content from sbg-pm@<sha> (Jun 24–30) — the publishing pipeline that syncs sbg-pm-generated content into this portal is live and ran repeatedly through the period.
.github/workflows doesn't exist) and most commits went straight to main without a PR (only 1 of 8 human commits went through review).
main + 10 automated sync commits. 18 commits total in the repo's entire history (the whole history falls inside this period, since the repo was created Jun 24).
main without a PR — acceptable during single-dev scaffolding, but the PR flow should be formalized before more contributors join. (2) No CI (lint/build/tests) is configured — a silent-regression risk given the site is static and ships without an automated gate. (3) With no Jira tickets, there's no "why" trail beyond commit messages — worth opening issues under SD-1456 as the portal grows.
Sources: GitHub
swissbull-group/sbg-portal— PR #1, commits onmain2026-06-22→2026-07-03 (18 total: 8 human by Oscar Cortez, 10 automatedsbg-pm botsync commits), no CI workflows (.github/workflowsabsent), no releases/tags. Jira: no ticket-level source registered for sbg-portal yet — epic SD-1456 ("SBG Internal Tools") confirmed as an empty placeholder per the project registry (projects/sbg-portal.yaml), no child issues this period. No invented data.