Set up Cloud dev environment + add AGENTS.md notes

[muratmuzaffer]

Summary

Sets up the BisiCab monorepo development environment for Cursor Cloud agents and documents durable, non-obvious run/test caveats in a new AGENTS.md.

No application code was changed. The only committed change is the new AGENTS.md.

What was set up

• Installed root workspace deps (npm install, Node 22, npm respects .npmrc legacy-peer-deps=true).
• Built + tested the shared package (npm run build:shared, npm test --workspace @bisicab/shared → 9/9 pass).
• Verified static checks via npm run typecheck (all 4 workspaces pass).
• Ran the shifts Next.js app (:3001) and the admin Next.js app (:3000) in dev mode.
• Installed Docker + Supabase CLI for the Supabase-dependent apps (not part of the startup update script).

Verified working

Workspace	Lint/Static	Test	Build/Run
packages/shared	npm run typecheck	npm test --workspace @bisicab/shared (9/9)	npm run build:shared
apps/shifts	npm run typecheck	—	npm run shifts (:3001) — full hello-world demo
apps/admin	npm run typecheck	—	npm run admin (:3000) — boots, serves /login
apps/mobile	npm run typecheck	—	native build only (not runnable in Cloud VM)

Hello-world demo (shifts app)

Logged into /yonetim, imported CSV shift data, published the August 2026 schedule, and confirmed it renders on the home page calendar.

Known blocker (pre-existing, not fixed here)

A clean local supabase start/db reset fails at supabase/migrations/0007_admin_no_shift.sql: it sets end_reason = 'shift_end' on public.shifts (type shift_end_reason), but shift_end is never added to that enum (migration 0004 only adds auto_21h to it, and adds shift_end to a different enum assignment_release_reason). Until 0007 is fixed, the local Supabase stack can't initialize, so admin login and the mobile backend can't be exercised end-to-end locally. Details in AGENTS.md.

Update script

npm install (minimal, idempotent).