SportMatch project hub

Static project hub for the SportMatch leadership views, development tools, interactive prototype, and shared design assets.

Repository map

• index.html: public Leadership entry point.
• leadership/: WBS, PERT/CPM and Gantt views (each with a v1/v2/v4 switch), plus the changelog. The v4 data is generated by scripts/generate-v4.py from the planning documents and the Linear export under docs/planning/.
• tools/: /tools entry point and its pages, including the Inicio introduction and team platform links.
• prototype/sportmatch/: canonical mobile and desktop prototype.
• assets/: public brand, icon, photo, token, and vendor assets.
• generated/figma/: derived Figma and standalone exports.
• docs/: planning material and references.
• scripts/: local project utilities.
• DESIGN.md: product design-system reference.

Run locally

Serve the repository with the Vercel CLI so root-relative asset paths, iframes, vercel.json routes and the api/ functions (Status, Bugs, Resources) behave exactly as they do in production:

vercel dev --listen 8000

python3 -m http.server 8000 still serves the static pages, but every /api/* call answers 404, so Status shows "No se pudo consultar el estado: HTTP 404".

Then open:

• Leadership: http://localhost:8000/
• Development tools (opens on Inicio): http://localhost:8000/tools/
• Mobile prototype: http://localhost:8000/prototype/sportmatch/mobile.html
• Desktop prototype: http://localhost:8000/prototype/sportmatch/desktop.html

Check local HTML references after moving files:

node scripts/check-static-links.mjs

Sync with Linear

The Gantt shows the Linear issues of each epic, package and deliverable. Refresh that data by hand whenever it matters (there is no automatic sync):

node --env-file=.env.local scripts/sync-linear.mjs          # report + refresh the repo
node --env-file=.env.local scripts/sync-linear.mjs --push    # also write milestones to Linear

Issues map to WBS packages in docs/planning/linear-wbs-map.csv, one row per issue-package pair; the first row of an issue is its main package and decides its milestone. New issues arrive with an empty wbs_id and npm run check fails until they are filled in. Pick the milestone when creating an issue in Linear: the epic comes from there. See docs/planning/plan-linear.md.

Database migrations

Apply the SQL files in db/migrations/ in numeric order to the Neon database. 002_dev_resources.sql creates the dynamic developer-resource directory and idempotently seeds the 75 resources that were previously embedded in the page.

Status history

/status charts uptime by day, week, month and year from the status_checks table (005_status_checks.sql). A cron-job.org job records one row per service every 30 minutes:

• URL: https://<deployment>/api/status-history, method POST
• Header: Authorization: Bearer <STATUS_CRON_SECRET>
• Schedule: every 30 minutes (don't go lower: each probe wakes the Neon computes, and a 5-minute schedule kept them on 24/7 and burned the free CPU hours)

STATUS_CRON_SECRET must be set in the Vercel project; without it the endpoint answers 503 and records nothing.

KPIs

/kpis shows the 10 KPIs that the kpi-report workflow in agents-copilot publishes every day to the course dashboard (lab4-kpis, Supabase), aggregated by day, week or month. api/kpis.js reads them server-side, so the project key never reaches the browser. Set these in the Vercel project, with the same values as the prod environment of agents-copilot; without them the page answers 503:

• KPI_SUPABASE_URL
• KPI_SUPABASE_PUBLISHABLE_KEY
• KPI_PROJECT_KEY (the prod key: each key only reads its own environment)

Source-of-truth rules

• Edit prototype code only under prototype/sportmatch/.
• Treat generated/figma/ as derived output, not source code.
• Add public reusable files under assets/ and use /assets/... URLs.
• Keep planning documents under docs/planning/.
• Keep index.html and tools/index.html stable because Vercel routes point to those entry files.
• Legacy public URLs are preserved as compatibility rewrites in vercel.json.