bmc-cross-sync-propagation
Orchestrates propagation, PROJECT-STATE updates, and local vs production verification for Calculadora BMC (https://calculadora-bmc.vercel.app): Vite localhost:5173, API localhost:3001, npm run smoke:p
SKILL.md.cursor/skills/bmc-cross-sync-propagation/SKILL.md
GitHubBMC Cross-Sync Propagation — Calculadora BMC (local + Vercel)
Runbook to keep this repo’s Calculadora stack aligned: team state, §4 propagation, local parity with production, without copying other skills in full.
Product scope (required)
| Environment | What | Canonical |
|---|---|---|
| Remote (frontend) | Vercel | https://calculadora-bmc.vercel.app |
| Remote (API) | Cloud Run service panelin-calc |
Public base from npm run smoke:prod / env (PUBLIC_BASE_URL, BMC_API_BASE, SMOKE_BASE_URL) — do not hardcode URLs in prose that drift |
| Local | Same monorepo | http://localhost:5173 (Vite), http://localhost:3001 (API, /health, /api/*) |
Not the primary focus: BMC Dashboard standalone or sibling repos. If §4 mentions them, treat as “docs/equipment in this repo” or optional sibling sync only.
When to use
- After changes under
src/,server/, OpenAPI, capabilities manifest, ML/Shopify integration, MATRIZ/pricing flows. - User says: sync calculadora, local and prod aligned, verify Vercel + API, smoke prod, cross sync for Panelin calc.
Delegate — do not duplicate
| Need | Follow |
|---|---|
| PROJECT-STATE, §4 table, full team | bmc-project-team-sync, docs/team/PROJECT-TEAM-FULL-COVERAGE.md |
| Deploy Vercel + Cloud Run, pre-deploy checklist | bmc-calculadora-deploy-from-cursor |
Optional mirror to bmc-dashboard-2.0 / bmc-development-team |
bmc-repo-sync-agent only if paths exist (PROJECT-STATE, BMC_DASHBOARD_2_REPO, BMC_DEVELOPMENT_TEAM_REPO) |
Large docs/ hygiene |
bmc-docs-and-repos-organizer |
| npm commands reference | Root AGENTS.md |
Phases (suggested order)
A — Inventory
Identify what changed: git diff, user list, or Cambios recientes in docs/team/PROJECT-STATE.md.
B — Propagation (§4)
Map each change to the matching row in §4 of PROJECT-TEAM-FULL-COVERAGE.md (API, integrations, OpenAPI/GPT, Sheets/MATRIZ when it affects the calculadora). Update PROJECT-STATE: Cambios recientes and Pendientes per §5.2 of that doc.
C — Contract / capabilities (conditional)
If server/routes/, server/agentCapabilitiesManifest.js, or OpenAPI artifacts changed:
- Run
npm run test:contractswith API on 3001 (seeAGENTS.md). - Run
npm run capabilities:snapshotwhen the public capabilities doc must match the manifest.
D — Local verification
- If stack not up:
npm run start:apiand Vite dev (ornpm run dev:fullper project norms); confirmGET http://localhost:3001/healthand app on 5173. - For
src/changes: prefernpm run gate:local:full(lint → test → build), or at minimum whatAGENTS.mdrequires before commit.
E — Remote verification
- Run
npm run smoke:prod(optional skips documented inAGENTS.md, e.g.SMOKE_SKIP_MATRIZ). - Confirms public health, calculadora-facing API behavior, and critical endpoints (e.g. MATRIZ CSV) against production base URL used by the script.
Deploy is out of scope unless the user asks; point to bmc-calculadora-deploy-from-cursor for full deploy + smoke after release.
F — Docs sweep (conditional)
Only if the change was a large documentation restructure: bmc-docs-and-repos-organizer.
G — Sibling repo sync (optional)
Only if the change must be mirrored and sibling paths are configured. Otherwise state N/A — Calculadora BMC focus in the summary.
H — Full team run (conditional)
Follow bmc-project-team-sync and docs/team/INVOQUE-FULL-TEAM.md when:
- User explicitly requests full team / “Invoque full team” / equipo completo, or
- Change spans multiple critical areas (e.g. Sheets schema + API + calculadora UI) with blocking pendientes, or
- Propagation cannot close without orchestrated handoffs.
Otherwise prefer this lighter pipeline over a full run.
Expected output
Deliver a short Markdown summary for the user:
- What changed (inventory).
- Which §4 rows applied and pending owners.
- What was updated in
PROJECT-STATE. - Local: gate/build/health results (or “skipped — reason”).
- Remote:
smoke:prodoutcome (or “skipped — reason”). - Whether deploy was done or only verification.
- Whether full team is recommended and why.
- Sibling repo sync: done / N/A.
Anti-duplication
Keep this file as the index. For step-by-step deploy, OAuth gates, or orchestrator step order, read the linked skills and team docs instead of pasting them here.