Refactor code structure for improved readability and maintainability

README.md

@@ -26,6 +26,14 @@ This repository now ships only the web application. It does not bundle Supabase,
 
 See `docs/04-supabase-kurulumu.md` for the expected Supabase-side resources.
 
+For a fresh Supabase project, run the one-shot setup SQL:
+
+```bash
+psql "postgresql://postgres:[PASSWORD]@[HOST]:5432/postgres" -v ON_ERROR_STOP=1 -f supabase/setup.sql
+```
+
+You can also paste the full contents of `supabase/setup.sql` into Supabase SQL Editor and run it once.
+
 ## Environment Variables
 
 Copy `.env.example` to `.env.local` for local development, or add the same values in Vercel, Coolify, Dokploy, or your hosting provider.

docs/04-supabase-kurulumu.md

@@ -22,6 +22,49 @@ Kurulumda genel yaklaşım şu:
 
 Repo içinde `supabase/` ve `docs/database/` klasörleri tutulmaya devam eder. Bunları deployment sırasında otomatik çalıştıran bir script yoktur. Bu dosyalar benim SQL kayıtlarım, migration notlarım ve schema geçmişim olarak durur.
 
+## Tek Seferlik Kurulum SQL'i
+
+Yeni bir Supabase projesini Neta için hazırlamanın en kolay yolu `supabase/setup.sql` dosyasını çalıştırmak. Bu dosya `supabase/schema.sql` ve `supabase/migrations/0002..0011` arasındaki migration dosyalarının tek dosyada birleştirilmiş hâlidir.
+
+Demo seed verisi bu dosyaya dahil değildir. Production kurulumda örnek veri istemediğim için seed ayrı tutulur.
+
+### Supabase SQL Editor ile
+
+Supabase panelinde şu bölümü açın:
+
+```txt
+SQL Editor -> New query
+```
+
+Sonra `supabase/setup.sql` dosyasının tamamını kopyalayıp tek seferde çalıştırın.
+
+Bu işlem şunları kurar:
+
+- Tablolar.
+- Foreign key ve check constraint'leri.
+- Index'ler.
+- Trigger ve function'lar.
+- RLS policy'leri.
+- Storage bucket kayıtları ve storage policy'leri.
+
+### Terminalden Tek Komut ile
+
+Supabase connection string'iniz varsa aynı kurulumu tek `psql` komutuyla da çalıştırabilirsiniz:
+
+```bash
+psql "postgresql://postgres:[PASSWORD]@[HOST]:5432/postgres" -v ON_ERROR_STOP=1 -f supabase/setup.sql
+```
+
+Supabase hosted projelerde connection string'i şuradan alabilirsiniz:
+
+```txt
+Project Settings -> Database -> Connection string
+```
+
+Şifre, host ve port bilgilerini kendi projenize göre değiştirmelisiniz.
+
+Bu komut başarılı bittikten sonra Supabase tarafı Neta uygulamasına hazır hâle gelir.
+
 ## Gerekli Tablolar
 
 Neta şu public tabloları bekler:
@@ -104,7 +147,21 @@ Bu yüzden `SUPABASE_SERVICE_ROLE_KEY` zorunludur. Bu key asla browser'a gönder
 
 ## SQL Dosyaları Nasıl Kullanılmalı?
 
-Bu repodaki SQL dosyalarını otomatik migration sistemi gibi düşünmüyorum. Bunlar benim migration geçmişimi ve Supabase tarafında beklenen yapıyı belgeleyen kaynaklar.
+Yeni kurulum için en pratik dosya:
+
+```txt
+supabase/setup.sql
+```
+
+Bu dosya tek seferde çalıştırılacak kurulum dosyasıdır.
+
+Parçalı dosyalar ise migration geçmişini ve geliştirme sürecini belgelemek için korunur:
+
+```txt
+supabase/schema.sql
+supabase/migrations/
+docs/database/
+```
 
 Yeni bir kurulum yaparken en güvenilir kaynak, çalışan Supabase projesinden aldığınız güncel SQL çıktısıdır. Supabase panelindeki "copy as SQL" çıktısı bu yüzden önemlidir.
 

docs/06-vercel-deploy.md

@@ -19,6 +19,12 @@ Deploy'dan önce hazır olması gerekenler:
 - Supabase tabloları, policy'leri, function'ları ve storage bucket'ları.
 - Environment variable değerleri.
 
+Supabase tarafını yeni kuruyorsanız önce `supabase/setup.sql` dosyasını Supabase SQL Editor'da tek seferde çalıştırın. Terminal kullanıyorsanız aynı işlem şu komutla yapılabilir:
+
+```bash
+psql "postgresql://postgres:[PASSWORD]@[HOST]:5432/postgres" -v ON_ERROR_STOP=1 -f supabase/setup.sql
+```
+
 Gerekli env değerleri:
 
 ```env

docs/07-coolify-deploy.md

@@ -22,6 +22,14 @@ Coolify deploy için hazır olması gerekenler:
 
 Supabase tarafında tablo, policy, function ve storage bucket'ları hazır olmalıdır.
 
+Yeni bir Supabase projesi hazırlıyorsanız `supabase/setup.sql` dosyasını tek seferde çalıştırabilirsiniz:
+
+```bash
+psql "postgresql://postgres:[PASSWORD]@[HOST]:5432/postgres" -v ON_ERROR_STOP=1 -f supabase/setup.sql
+```
+
+Supabase panelinden ilerlemek isterseniz aynı dosyanın tamamını SQL Editor'a yapıştırıp çalıştırmanız yeterli.
+
 ## Uygulama Oluşturma
 
 Coolify içinde yeni bir application oluştururken:

docs/08-dokploy-deploy.md

@@ -20,6 +20,14 @@ Başlamadan önce şunlar hazır olmalı:
 - Supabase schema ve storage yapısı.
 - Ortam değişkenleri.
 
+Supabase tarafı hazır değilse önce `supabase/setup.sql` dosyasını çalıştırın. Terminalden tek komutla kurmak için:
+
+```bash
+psql "postgresql://postgres:[PASSWORD]@[HOST]:5432/postgres" -v ON_ERROR_STOP=1 -f supabase/setup.sql
+```
+
+SQL Editor kullanıyorsanız `supabase/setup.sql` içeriğini komple yapıştırıp çalıştırabilirsiniz.
+
 ## Dokploy'da Uygulama Oluşturma
 
 Dokploy içinde yeni bir uygulama oluştururken GitHub reposunu seçin. Uygulamayı Node.js/Next.js app olarak yapılandırın.

docs/database/query-order.md

@@ -33,10 +33,10 @@ They must also be documented and registered in this file, but they should only b
 
 ## Applying The Ordered SQL
 
-Use the migration helper from the repository root:
+For a fresh Supabase project, use the one-shot setup file from the repository root:
 
 ```bash
-DATABASE_URL='postgresql://postgres:password@host:5432/postgres' sh ./scripts/apply-migrations.sh
+psql "postgresql://postgres:[PASSWORD]@[HOST]:5432/postgres" -v ON_ERROR_STOP=1 -f supabase/setup.sql
 ```
 
-The helper applies missing queries from `0001` through `0011` in the order listed above and records completed migrations in `neta_internal.schema_migrations`. It uses local `psql` when available, otherwise it runs `psql` through Docker. After migrations, it sends `NOTIFY pgrst, 'reload schema'` so PostgREST can see new RPC functions without a manual restart.
+The setup file applies `0001` through `0011` in the order listed above. It does not include optional seed data. If you are changing the schema later, keep adding ordered files under `supabase/migrations/` and update this table.

supabase/README.md

@@ -2,6 +2,22 @@
 
 This directory stores SQL files for the project's Supabase/PostgreSQL database.
 
+## One-Shot Setup
+
+For a fresh Supabase project, use:
+
+```text
+supabase/setup.sql
+```
+
+You can paste the full file into Supabase SQL Editor and run it once, or run it from the repository root with `psql`:
+
+```bash
+psql "postgresql://postgres:[PASSWORD]@[HOST]:5432/postgres" -v ON_ERROR_STOP=1 -f supabase/setup.sql
+```
+
+The setup file is generated by concatenating `schema.sql` and migrations `0002` through `0011` in the canonical order. Demo seed data is intentionally not included.
+
 ## Current Baseline
 
 - `schema.sql` is the first registered database SQL file.
@@ -42,10 +58,10 @@ Do not overwrite already executed SQL without also creating a new ordered migrat
 
 ## Apply Migrations
 
-From the repository root:
+For a new project, prefer the one-shot setup file:
 
 ```bash
-DATABASE_URL='postgresql://postgres:password@host:5432/postgres' bash ./scripts/apply-migrations.sh
+psql "postgresql://postgres:[PASSWORD]@[HOST]:5432/postgres" -v ON_ERROR_STOP=1 -f supabase/setup.sql
 ```
 
-The script applies all required schema files in canonical order. It requires either local `psql` or Docker. If `psql` is not installed, it runs `psql` through the `postgres:16-alpine` Docker image.
+The ordered migration files remain as the source history for future schema changes.

supabase/migrations/0004_add_business_os_tables.sql

@@ -70,25 +70,41 @@ alter table public.invoices enable row level security;
 alter table public.subscriptions enable row level security;
 
 -- Proposals RLS
+drop policy if exists "Users can view their own proposals" on public.proposals;
 create policy "Users can view their own proposals" on public.proposals for select using (auth.uid() = user_id);
+drop policy if exists "Users can insert their own proposals" on public.proposals;
 create policy "Users can insert their own proposals" on public.proposals for insert with check (auth.uid() = user_id);
+drop policy if exists "Users can update their own proposals" on public.proposals;
 create policy "Users can update their own proposals" on public.proposals for update using (auth.uid() = user_id);
+drop policy if exists "Users can delete their own proposals" on public.proposals;
 create policy "Users can delete their own proposals" on public.proposals for delete using (auth.uid() = user_id);
 
 -- Contracts RLS
+drop policy if exists "Users can view their own contracts" on public.contracts;
 create policy "Users can view their own contracts" on public.contracts for select using (auth.uid() = user_id);
+drop policy if exists "Users can insert their own contracts" on public.contracts;
 create policy "Users can insert their own contracts" on public.contracts for insert with check (auth.uid() = user_id);
+drop policy if exists "Users can update their own contracts" on public.contracts;
 create policy "Users can update their own contracts" on public.contracts for update using (auth.uid() = user_id);
+drop policy if exists "Users can delete their own contracts" on public.contracts;
 create policy "Users can delete their own contracts" on public.contracts for delete using (auth.uid() = user_id);
 
 -- Invoices RLS
+drop policy if exists "Users can view their own invoices" on public.invoices;
 create policy "Users can view their own invoices" on public.invoices for select using (auth.uid() = user_id);
+drop policy if exists "Users can insert their own invoices" on public.invoices;
 create policy "Users can insert their own invoices" on public.invoices for insert with check (auth.uid() = user_id);
+drop policy if exists "Users can update their own invoices" on public.invoices;
 create policy "Users can update their own invoices" on public.invoices for update using (auth.uid() = user_id);
+drop policy if exists "Users can delete their own invoices" on public.invoices;
 create policy "Users can delete their own invoices" on public.invoices for delete using (auth.uid() = user_id);
 
 -- Subscriptions RLS
+drop policy if exists "Users can view their own subscriptions" on public.subscriptions;
 create policy "Users can view their own subscriptions" on public.subscriptions for select using (auth.uid() = user_id);
+drop policy if exists "Users can insert their own subscriptions" on public.subscriptions;
 create policy "Users can insert their own subscriptions" on public.subscriptions for insert with check (auth.uid() = user_id);
+drop policy if exists "Users can update their own subscriptions" on public.subscriptions;
 create policy "Users can update their own subscriptions" on public.subscriptions for update using (auth.uid() = user_id);
+drop policy if exists "Users can delete their own subscriptions" on public.subscriptions;
 create policy "Users can delete their own subscriptions" on public.subscriptions for delete using (auth.uid() = user_id);

supabase/migrations/0005_add_advanced_crm_tables.sql

@@ -24,7 +24,11 @@ create table if not exists public.client_activities (
 alter table public.client_activities enable row level security;
 
 -- Client Activities RLS
+drop policy if exists "Users can view their own client activities" on public.client_activities;
 create policy "Users can view their own client activities" on public.client_activities for select using (auth.uid() = user_id);
+drop policy if exists "Users can insert their own client activities" on public.client_activities;
 create policy "Users can insert their own client activities" on public.client_activities for insert with check (auth.uid() = user_id);
+drop policy if exists "Users can update their own client activities" on public.client_activities;
 create policy "Users can update their own client activities" on public.client_activities for update using (auth.uid() = user_id);
+drop policy if exists "Users can delete their own client activities" on public.client_activities;
 create policy "Users can delete their own client activities" on public.client_activities for delete using (auth.uid() = user_id);

supabase/migrations/0006_add_pgvector_and_embeddings.sql

@@ -16,9 +16,13 @@ create table if not exists public.document_embeddings (
 -- Enable RLS
 alter table public.document_embeddings enable row level security;
 
+drop policy if exists "Users can view their own embeddings" on public.document_embeddings;
 create policy "Users can view their own embeddings" on public.document_embeddings for select using (auth.uid() = user_id);
+drop policy if exists "Users can insert their own embeddings" on public.document_embeddings;
 create policy "Users can insert their own embeddings" on public.document_embeddings for insert with check (auth.uid() = user_id);
+drop policy if exists "Users can update their own embeddings" on public.document_embeddings;
 create policy "Users can update their own embeddings" on public.document_embeddings for update using (auth.uid() = user_id);
+drop policy if exists "Users can delete their own embeddings" on public.document_embeddings;
 create policy "Users can delete their own embeddings" on public.document_embeddings for delete using (auth.uid() = user_id);
 
 -- Create a function to similarity search for embeddings

supabase/migrations/0007_add_client_portal_tables.sql

@@ -23,6 +23,7 @@ CREATE TABLE IF NOT EXISTS public.project_revisions (
 );
 
 -- Trigger to set updated_at
+DROP TRIGGER IF EXISTS set_project_revisions_updated_at ON public.project_revisions;
 CREATE TRIGGER set_project_revisions_updated_at
 BEFORE UPDATE ON public.project_revisions
 FOR EACH ROW
@@ -35,18 +36,21 @@ ALTER TABLE public.project_revisions ENABLE ROW LEVEL SECURITY;
 
 -- PROFILES
 -- Clients can read their own profile
+DROP POLICY IF EXISTS "Clients can view own profile" ON public.profiles;
 CREATE POLICY "Clients can view own profile"
 ON public.profiles FOR SELECT
 USING (auth.uid() = id);
 
 -- CLIENTS
 -- Clients can read their own client record
+DROP POLICY IF EXISTS "Clients can view own client record" ON public.clients;
 CREATE POLICY "Clients can view own client record"
 ON public.clients FOR SELECT
 USING (client_auth_id = auth.uid());
 
 -- PROJECTS
 -- Clients can view projects where client_id matches their client record
+DROP POLICY IF EXISTS "Clients can view own projects" ON public.projects;
 CREATE POLICY "Clients can view own projects"
 ON public.projects FOR SELECT
 USING (
@@ -57,6 +61,7 @@ USING (
 
 -- TASKS
 -- Clients can view tasks linked to their projects IF is_public_to_client is true
+DROP POLICY IF EXISTS "Clients can view public tasks of their projects" ON public.tasks;
 CREATE POLICY "Clients can view public tasks of their projects"
 ON public.tasks FOR SELECT
 USING (
@@ -70,6 +75,7 @@ USING (
 
 -- PROJECT PLANNING SECTIONS (Milestones, Roadmap, etc.)
 -- Clients can view planning sections of their projects
+DROP POLICY IF EXISTS "Clients can view planning sections of their projects" ON public.project_planning_sections;
 CREATE POLICY "Clients can view planning sections of their projects"
 ON public.project_planning_sections FOR SELECT
 USING (
@@ -82,6 +88,7 @@ USING (
 
 -- PROJECT REVISIONS
 -- Freelancers can manage all revisions for their projects
+DROP POLICY IF EXISTS "Freelancers can manage revisions" ON public.project_revisions;
 CREATE POLICY "Freelancers can manage revisions"
 ON public.project_revisions FOR ALL
 USING (
@@ -91,6 +98,7 @@ USING (
 );
 
 -- Clients can insert revisions for their projects
+DROP POLICY IF EXISTS "Clients can insert revisions" ON public.project_revisions;
 CREATE POLICY "Clients can insert revisions"
 ON public.project_revisions FOR INSERT
 WITH CHECK (
@@ -101,6 +109,7 @@ WITH CHECK (
 );
 
 -- Clients can view their own revisions
+DROP POLICY IF EXISTS "Clients can view own revisions" ON public.project_revisions;
 CREATE POLICY "Clients can view own revisions"
 ON public.project_revisions FOR SELECT
 USING (