multica-local-run

Starts, debugs, and verifies the local Multica development stack with supervised make dev workflows.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill multica-local-run-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multica-local-run
Source: https://github.com/vovanostm-public/multica/tree/main/docs/wiki/architecture/archived-codex-skills/20260525-190000/multica-local-run
Command: npx skills add https://github.com/vovanostm-public/multica --skill multica-local-run-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Local development stacks fail in confusing ways: stale ports, unsupervised processes, migration guards blocking startup, and schema drift. This Skill provides a canonical runbook for starting, diagnosing, and recovering the Multica local dev environment so you spend time coding instead of fighting infrastructure. ## Core Features & Use Cases - Supervised Startup: Uses make dev as the canonical path with defined port contracts (frontend 3500, backend 3501, postgres 3502, daemon 3503) and health-check verification. - Guarded Migration Recovery: Walks through the 103_drop_legacy_daily_rollups guard failure, including the backfill_task_usage_hourly recovery procedure and correct upgrade ordering. - Failure Diagnosis: Covers port-conflict cleanup, split-state detection (processes running outside make dev supervision), Postgres routing checks, and frontend CPU/memory profiling. - Use Case: Your make dev run fails with listen tcp :3501: bind: address already in use. Follow the Skill to identify the owning process, confirm which checkout owns it, clean up safely, and restart under supervision. ## Quick Start Start the local Multica stack with make dev and verify all health endpoints using this skill's checklist.

Frequently Asked Questions about multica-local-run

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start the Multica local development stack?▼

Run `make dev` from the repo root after confirming Docker is running with `docker info`. Verify startup by curling the backend health on port 3501, frontend health.txt on 3500, daemon health on 3503, and running scripts/dev-stack-status.sh.

How to fix port 3501 already in use error?▼

Find the listener with `lsof -nP -iTCP:3501 -sTCP:LISTEN` and run `bash scripts/stop-dev-stack.sh --quiet`. If the process belongs to another checkout or worktree, stop that owning stack there instead of force-killing it, then retry `make dev`.

Why does migration 103_drop_legacy_daily_rollups fail?▼

The migration guard detects that task_usage_hourly_rollup_state.watermark_at trails the latest task_usage event. Run the backfill with `go run ./cmd/backfill_task_usage_hourly` against the local Postgres on port 3502, then re-run `make dev`.

What does the backend healthy without supervisor warning mean?▼

It means app processes survived outside `make dev`, so watchdog protections are inactive and the checkout is in a split state. Recover by running `make stop` followed by `make dev` to restore supervised startup.

How do I debug frontend CPU or memory spikes in Next.js dev?▼

Run `make dev-profile-next`, then inspect the frontend log under ~/.multica/dev-stack/<checkout-hash>/logs/frontend.log and the last lines of apps/web/.next/dev/trace. Use /health.txt rather than / as the health URL.