tillerhand 3.48.1 → 3.49.1

package/kit/templates/addons/tr/docs/legal/turkiye.md

@@ -1,80 +1,80 @@
-# Türkiye Paketi
+# Turkey Pack
 
-> `tr` ekiyle gelir (`--addons tr`). Türkiye'de satış yapan veya Türk kullanıcısı olan ürün için.
-> **Hukuki görüş değildir.** Her madde birincil kaynağa bağlı ve kontrol tarihli; mevzuat değişir. Yayından önce bir avukata veya mali müşavire danış.
-> Kullanmadan önce kaynakları `source-research` ile yeniden aç; değişen varsa bu dosyayı güncelle ve tarihi değiştir.
-> `/findings-legal` ve `/findings-business` bu dosyayı okur.
+> Comes with the `tr` add-on (`--addons tr`). For a product that sells in Turkey or has Turkish users.
+> **Not legal advice.** Every item links to a primary source and has a check date; legislation changes. Ask a lawyer or an accountant before launch.
+> Before use, reopen the sources with `source-research`; if something changed, update this file and change the date.
+> `/findings-legal` and `/findings-business` read this file.
 
-## 1. KVKK: yurt dışına aktarım
+## 1. KVKK: transfer abroad
 
-Kontrol: 2026-10-25. Kaynak: [6698 sayılı KVKK, m.9](https://www.mevzuat.gov.tr/MevzuatMetin/1.5.6698.pdf) (7499 sayılı Kanunla değişik, 2/3/2024)
+Checked: 2026-10-25. Source: [Law no. 6698 (KVKK), art. 9](https://www.mevzuat.gov.tr/MevzuatMetin/1.5.6698.pdf) (as amended by Law no. 7499, 2/3/2024)
 
-Yurt dışındaki bir servise kişisel veri gitmesi aktarımdır: AI sağlayıcısı (istem metninde kullanıcı verisi), barındırma ve veritabanı bölgesi, e-posta, analitik, hata takibi. Sıra:
+Personal data going to a service abroad is a transfer: AI provider (user data in the prompt text), hosting and database region, email, analytics, error tracking. Order:
 
-1. **Yeterlilik kararı** var mı (m.9/1-3)? Kurul verir, Resmî Gazete'de yayımlanır. Varsa m.5 veya m.6'daki bir şartla aktarılabilir.
-2. Yoksa **uygun güvence** (m.9/4): Kurul'un ilan ettiği **standart sözleşme**, onaylı bağlayıcı şirket kuralları, Kurul izinli taahhütname veya (kamu kurumları arasında) Kurul izinli anlaşma. Burada da m.5 veya m.6'daki bir şart gerekir ve ilgili kişinin o ülkede haklarını kullanabilmesi şarttır.
-   - **Standart sözleşme imzalandıktan sonra 5 iş günü içinde Kuruma bildirilir** (m.9/5).
-3. İkisi de yoksa sadece **arızi** (tekrarlanmayan) hallerde (m.9/6): bilgilendirilmiş açık rıza, sözleşmenin ifası için zorunluluk ve maddede sayılan diğer haller. Sürekli çalışan bir AI veya barındırma servisi "arızi" değildir.
+1. Is there an **adequacy decision** (art. 9/1-3)? The Personal Data Protection Board (KVKK Board) issues it; it is published in the Official Gazette. If there is one, transfer is allowed under a condition in art. 5 or art. 6.
+2. If not, **appropriate safeguards** (art. 9/4): the **standard contract** announced by the Board, approved binding corporate rules, an undertaking permitted by the Board or (between public bodies) an agreement permitted by the Board. A condition in art. 5 or art. 6 is still required here, and the data subject must be able to exercise their rights in that country.
+   - **After the standard contract is signed, notify the Personal Data Protection Authority (KVKK Authority) within 5 business days** (art. 9/5).
+3. If neither exists, only in **incidental** (non-repeated) cases (art. 9/6): informed explicit consent, necessity for performing a contract and the other cases listed in the article. An AI or hosting service that runs continuously is not "incidental".
 
-Projede yapılacaklar:
-- [ ] `docs/operations/accounts.md`'deki her dış servis için: veri hangi ülkede, aktarım dayanağı ne (yeterlilik / standart sözleşme / yok)?
-- [ ] Standart sözleşme gerekiyorsa sağlayıcıyla imzalandı ve 5 iş günü içinde Kuruma bildirildi; tarih `accounts.md` → Not sütununda.
-- [ ] Aydınlatma metni (`docs/legal/privacy-kvkk.md`) yurt dışına aktarımı, alıcı grubunu ve amacını söylüyor (m.10).
-- [ ] AI istemine gerekmeyen kişisel veri gitmiyor (veri en aza indirme); mümkünse kimlik bilgisi maskeleniyor.
+Project to-do:
+- [ ] For each external service in `docs/operations/accounts.md`: which country is the data in, what is the transfer basis (adequacy / standard contract / none)?
+- [ ] If a standard contract is needed, it is signed with the provider and notified to the Authority within 5 business days; the date is in `accounts.md` → Note column.
+- [ ] The privacy notice (`docs/legal/privacy-kvkk.md`) states the transfer abroad, the recipient group and the purpose (art. 10).
+- [ ] No unneeded personal data goes into the AI prompt (data minimization); identity data is masked where possible.
 
-## 2. e-Fatura ve e-Arşiv Fatura
+## 2. e-Fatura and e-Arşiv Fatura
 
-Kontrol: 2026-10-25. Kaynak: [509 Sıra No.lu VUK Genel Tebliği, güncel hali](https://cdn.gib.gov.tr/api/gibportal-file/file/getFile?objectKey=MEVZUAT_TEBLIGLER%2FUNIVERSAL%2F2026%2FMEVZUAT_TEBLIGLER_2026_VukTeb509_Guncel.pdf) (GİB, 589 Sıra No.lu Tebliğ değişiklikleri işlenmiş) · [e-Belge](https://ebelge.gib.gov.tr/)
+Checked: 2026-10-25. Source: [General Communiqué on the Tax Procedure Law no. 509 (VUK General Communiqué No. 509), current version](https://cdn.gib.gov.tr/api/gibportal-file/file/getFile?objectKey=MEVZUAT_TEBLIGLER%2FUNIVERSAL%2F2026%2FMEVZUAT_TEBLIGLER_2026_VukTeb509_Guncel.pdf) (GİB, with the amendments of Communiqué no. 589 applied) · [e-Belge](https://ebelge.gib.gov.tr/)
 
-- **e-Fatura zorunluluğu** (IV.1.4): 2022 veya sonraki hesap dönemlerinde brüt satış hasılatı **3 milyon TL** ve üzeri olanlar. Kendi sitesinde veya başka elektronik ortamda mal/hizmet satanlar, aracı hizmet sağlayıcılar ve internet ilan/reklam aracıları için eşik **500 bin TL**. Eşiği aşan, izleyen yılın yedinci ayının başına kadar geçer (IV.1.5).
-- **e-Arşiv**: e-Fatura'ya dahil olan e-Arşiv'e de geçer (IV.2.4.1). e-Arşiv'e dahil olmayanların faturaları 1/1/2026'dan itibaren tutarından bağımsız olarak e-Arşiv Fatura olarak (GİB portalı veya özel entegratör üzerinden) düzenlenir. Basit usul ve işletme hesabı esasında bu tarih 1/1/2027'dir (IV.2.4.3).
-- **İnternet satışı faturası** (IV.2.4.5): Fatura elektronik ortamda iletilir. Üzerinde "Bu satış internet üzerinden yapılmıştır." ifadesi, satışın yapıldığı web adresi, ödeme şekli ve tarihi, gönderen kargo bilgisi, gönderim tarihi ve iade bölümü yer alır.
+- **e-Fatura obligation** (IV.1.4): those whose gross sales revenue was **3 million TL** or more in accounting periods of 2022 or later. For those selling goods/services on their own site or in another electronic medium, intermediary service providers and internet listing/advertising intermediaries, the threshold is **500 thousand TL**. Those who exceed the threshold switch by the start of the seventh month of the following year (IV.1.5).
+- **e-Arşiv**: those in e-Fatura also switch to e-Arşiv (IV.2.4.1). Invoices of those not in e-Arşiv are issued as e-Arşiv Fatura (through the GİB portal or a private integrator) from 1/1/2026, regardless of amount. For the simplified procedure and the business account basis this date is 1/1/2027 (IV.2.4.3).
+- **Internet sales invoice** (IV.2.4.5): The invoice is delivered electronically. It carries the statement "Bu satış internet üzerinden yapılmıştır.", the web address where the sale was made, the payment method and date, the shipping carrier's information, the shipping date and a return section.
 
-Projede yapılacaklar:
-- [ ] Fatura kesme yöntemi seçildi: GİB portalı (elle, küçük hacim) veya özel entegratör API'si (otomatik). Seçim `docs/decisions/log.md`'de.
-- [ ] Ödeme başarılı olunca fatura akışı tetikleniyor; fatura kesilemezse sipariş kaybolmuyor (yeniden deneme kuyruğu).
-- [ ] Mali müşavir eşik ve yöntem için onay verdi.
+Project to-do:
+- [ ] Invoicing method chosen: GİB portal (manual, small volume) or a private integrator API (automatic). The choice is in `docs/decisions/log.md`.
+- [ ] The invoice flow is triggered when payment succeeds; if the invoice cannot be issued, the order is not lost (retry queue).
+- [ ] The accountant approved the threshold and the method.
 
-## 3. Ödeme bildirimleri (iyzico, PayTR)
+## 3. Payment notifications (iyzico, PayTR)
 
-Kontrol: 2026-10-25. Kaynaklar: [iyzico webhook](https://docs.iyzico.com/en/advanced/webhook) · [iyzico Retrieve Payment](https://docs.iyzico.com/en/advanced/retrieve-payment) · [iyzico CF Retrieve](https://docs.iyzico.com/en/payment-methods/checkoutform/cf-implementation/cf-retrieve) · [iyzico live / sandbox](https://docs.iyzico.com/en/getting-started/preliminaries/live-vs-sandbox) · [PayTR iFrame API 2. adım](https://dev.paytr.com/en/iframe-api/iframe-api-2-adim) (sayfalarda tarih yok)
+Checked: 2026-10-25. Sources: [iyzico webhook](https://docs.iyzico.com/en/advanced/webhook) · [iyzico Retrieve Payment](https://docs.iyzico.com/en/advanced/retrieve-payment) · [iyzico CF Retrieve](https://docs.iyzico.com/en/payment-methods/checkoutform/cf-implementation/cf-retrieve) · [iyzico live / sandbox](https://docs.iyzico.com/en/getting-started/preliminaries/live-vs-sandbox) · [PayTR iFrame API step 2](https://dev.paytr.com/en/iframe-api/iframe-api-2-adim) (the pages have no date)
 
-Ödeme sonucu tarayıcı yönlendirmesine değil, sağlayıcının sunucudan gönderdiği bildirime göre işlenir. Bildirim imzası doğrulanmadan sipariş onaylanmaz. Kod hazır:
-- web-saas: `src/lib/payments/webhook-signature.ts` → `verifyIyzico`, `verifyPaytr`; saldırgan testi `tests/security/payment-webhook.mjs` (CI: `payment-webhook` iş akışı; yerelde Node 22.18 veya üstü)
-- backend: `app/shared/payments.py` → `verify_iyzico`, `verify_paytr`; saldırgan testi `tests/security/test_payment_webhook.py`
-- mobil: ödeme bildirimi sunucuya gelir; backend şablonunu veya Supabase Edge Function'ı kullan. Kartı uygulama içinde alma; sağlayıcının ödeme sayfasına yönlendir.
+A payment result is processed from the notification the provider sends from its server, not from the browser redirect. An order is not confirmed before the notification signature is verified. The code is ready:
+- web-saas: `src/lib/payments/webhook-signature.ts` → `verifyIyzico`, `verifyPaytr`; adversarial test `tests/security/payment-webhook.mjs` (CI: `payment-webhook` workflow; locally Node 22.18 or later)
+- backend: `app/shared/payments.py` → `verify_iyzico`, `verify_paytr`; adversarial test `tests/security/test_payment_webhook.py`
+- mobile: the payment notification comes to the server; use the backend template or a Supabase Edge Function. Do not take the card inside the app; redirect to the provider's payment page.
 
-Akış:
-1. Sandbox hesabı aç (iyzico: sandbox-merchant.iyzipay.com, API `https://sandbox-api.iyzipay.com`; PayTR: mağaza panelinde test modu). Anahtarlar `.env.example`'daki adlarla **sadece sunucuda**; değerleri sen girersin.
-2. Ödeme başlatma sunucuda yapılır; tutar ve sipariş numarası istemciden değil veritabanındaki siparişten alınır. iyzico'da her ödemeye sipariş numarasını `conversationId` olarak ver: imza bu alanı da kapsar, boşsa doğrulama reddeder.
-3. Bildirim ucu (route) önce imzayı doğrular. `false` dönerse 4xx dön ve logla; isteğin gövdesini loglama (kişisel veri).
-   - iyzico: `X-IYZ-SIGNATURE-V3` başlığı. İmza özelliği hesapta açık olmalı (iyzico'dan istenir). Abonelik bildirimleri bu kodun kapsamında değil.
-   - PayTR: POST'taki `hash` alanı; yanıt düz metin `OK`, oturum kontrolü yok. Alanları form gövdesinden metin olarak al; `total_amount`'u sayıya çevirip geri yazma (imza bozulur).
-4. **Geçerli imza, ödemenin başarılı olduğu demek değildir.** Başarısız ödeme de imzalı gelir. Sadece sonuç başarılıysa siparişi onayla: PayTR `status` = `success`, iyzico `status` = `SUCCESS` ve `iyziEventType` beklediğin tür. Diğerlerinde onaylama, sağlayıcıya yine başarı yanıtı dön.
-5. Tutarı ve para birimini siparişle karşılaştır:
-   - PayTR: bildirimdeki `total_amount` (kuruş: 34,56 TL → 3456).
-   - iyzico: bildirimde tutar yok. Sunucudan sorgula: checkout formunda `token` ile CF Retrieve, diğerlerinde `paymentId` ile Retrieve Payment. Dönen `paymentStatus`, `paidPrice`, `currency` ve `conversationId` siparişle aynı olmalı.
-6. **Tekrar gelen bildirim** (sağlayıcı yeniden dener, saldırgan eski bildirimi yeniden gönderebilir; iyzico imzasında zaman damgası yok): siparişi tek bir atomik güncellemeyle onayla (`UPDATE … SET durum='odendi' WHERE id=… AND durum='bekliyor'`) veya ödeme kimliğine (`merchant_oid` / `paymentId`) benzersiz kısıt koy. Önce okuyup sonra yazma; iki eşzamanlı bildirim ikisi de geçer. Tekrar gelene de başarı yanıtı dön.
-7. Ödeme özelliği bayrak arkasında yayınlanır (`docs/operations/feature-flags.md`); canlıya almadan önce `/findings-security`.
+Flow:
+1. Open a sandbox account (iyzico: sandbox-merchant.iyzipay.com, API `https://sandbox-api.iyzipay.com`; PayTR: test mode in the merchant panel). Keys use the names in `.env.example` and live **on the server only**; you enter the values.
+2. Payment is started on the server; the amount and order number come from the order in the database, not from the client. In iyzico, give the order number as `conversationId` on every payment: the signature covers this field too, and verification rejects it if empty.
+3. The notification endpoint (route) verifies the signature first. If it returns `false`, return 4xx and log; do not log the request body (personal data).
+   - iyzico: `X-IYZ-SIGNATURE-V3` header. The signature feature must be on in the account (request it from iyzico). Subscription notifications are outside the scope of this code.
+   - PayTR: the `hash` field in the POST; the response is plain text `OK`, no session check. Take the fields from the form body as text; do not convert `total_amount` to a number and write it back (this breaks the signature).
+4. **A valid signature does not mean the payment succeeded.** A failed payment also arrives signed. Confirm the order only if the result is a success: PayTR `status` = `success`, iyzico `status` = `SUCCESS` and `iyziEventType` the type you expect. In the other cases do not confirm; still return a success response to the provider.
+5. Compare the amount and currency with the order:
+   - PayTR: `total_amount` in the notification (kuruş: 34.56 TL → 3456).
+   - iyzico: the notification has no amount. Query the server: CF Retrieve with `token` for the checkout form, Retrieve Payment with `paymentId` for the others. The returned `paymentStatus`, `paidPrice`, `currency` and `conversationId` must match the order.
+6. **A repeated notification** (the provider retries, an attacker can resend an old notification; the iyzico signature has no timestamp): confirm the order with a single atomic update (`UPDATE … SET status='paid' WHERE id=… AND status='pending'`) or put a unique constraint on the payment id (`merchant_oid` / `paymentId`). Do not read first and write after; two concurrent notifications would both pass. Return a success response to the repeated one too.
+7. The payment feature ships behind a flag (`docs/operations/feature-flags.md`); run `/findings-security` before going live.
 
-- [ ] İmza saldırgan testi yeşil (imzasız ve değiştirilmiş bildirim reddediliyor).
-- [ ] Bildirim ucu testinde: başarısız ödeme bildirimi siparişi onaylamıyor; aynı bildirim iki kez (ve eşzamanlı) gelince sipariş bir kez işleniyor; tutarı farklı ödeme onaylanmıyor. Bu testler projenin kendi rotası için yazılır.
-- [ ] Prod anahtarları sadece barındırma panelinde; sandbox ve prod ayrı.
+- [ ] The signature adversarial test is green (unsigned and altered notifications are rejected).
+- [ ] The notification endpoint test shows: a failed-payment notification does not confirm the order; when the same notification arrives twice (and concurrently), the order is processed once; a payment with a different amount is not confirmed. These tests are written for the project's own route.
+- [ ] Prod keys are only in the hosting panel; sandbox and prod are separate.
 
-## 4. Türkçe metin: İ/ı
+## 4. Turkish text: İ/ı
 
-`"I".toLowerCase()` → `"i"`, ama Türkçede `"ı"`. `"i".toUpperCase()` → `"I"`, Türkçede `"İ"`. Varsayılan sıralama `ç, ğ, ı, ö, ş, ü` harflerini alfabenin sonuna atar. Arama, sıralama, büyük harfe çevirme ve e-posta karşılaştırması yapan her özelliğin testine şu durumları ekle:
+`"I".toLowerCase()` → `"i"`, but in Turkish it is `"ı"`. `"i".toUpperCase()` → `"I"`, in Turkish it is `"İ"`. The default sort puts the letters `ç, ğ, ı, ö, ş, ü` at the end of the alphabet. Add these cases to the tests of every feature that does search, sorting, uppercasing and email comparison:
 
 ```js
-// Türkçe görünen metin: dil açıkça verilir
+// Text shown as Turkish: the language is given explicitly
 expect('ISPARTA'.toLocaleLowerCase('tr')).toBe('ısparta');
 expect('istanbul'.toLocaleUpperCase('tr')).toBe('İSTANBUL');
 expect(['Zeynep', 'Çağla', 'Ali', 'Ömer'].sort(new Intl.Collator('tr').compare)).toEqual(['Ali', 'Çağla', 'Ömer', 'Zeynep']);
-// Büyük/küçük harf duyarsız arama: "İstanbul" araması "istanbul"u bulur
+// Case-insensitive search: searching "İstanbul" finds "istanbul"
 expect(new Intl.Collator('tr', { sensitivity: 'base' }).compare('İstanbul', 'istanbul')).toBe(0);
-// Makine metni (e-posta, kod, URL, anahtar): dile bağlı çevirme yok
-expect('INFO@ORNEK.COM'.toLowerCase()).toBe('info@ornek.com');
+// Machine text (email, code, URL, key): no language-dependent conversion
+expect('INFO@EXAMPLE.COM'.toLowerCase()).toBe('info@example.com');
 ```
 
-- [ ] Kullanıcıya görünen metinde `toLocaleLowerCase('tr')` / `Intl.Collator('tr')`; e-posta, kullanıcı adı ve kod gibi makine metninde dile bağlı olmayan `toLowerCase()`.
-- [ ] Veritabanı sıralaması: Postgres'te Türkçe collation (ör. ICU `tr-TR-x-icu`) veya sıralama uygulamada.
+- [ ] In text shown to the user use `toLocaleLowerCase('tr')` / `Intl.Collator('tr')`; in machine text such as email, username and code use the language-independent `toLowerCase()`.
+- [ ] Database sorting: a Turkish collation in Postgres (e.g. ICU `tr-TR-x-icu`) or sorting in the application.

package/kit/templates/addons/tr/types/backend/.env.example.append

@@ -1,7 +1,7 @@
-# Türkiye eki: ödeme sağlayıcısı (sadece sunucu; kullanmadığını silebilirsin). Ayrıntı: docs/legal/turkiye.md
+# Turkey add-on: payment provider (server only; you can delete the one you do not use). Details: docs/legal/turkiye.md
 IYZICO_API_KEY=
 IYZICO_SECRET_KEY=
-IYZICO_BASE_URL=https://sandbox-api.iyzipay.com   # canlı: https://api.iyzipay.com
+IYZICO_BASE_URL=https://sandbox-api.iyzipay.com   # live: https://api.iyzipay.com
 PAYTR_MERCHANT_ID=
 PAYTR_MERCHANT_KEY=
 PAYTR_MERCHANT_SALT=

package/kit/templates/addons/tr/types/backend/app/shared/payments.py

@@ -1,7 +1,7 @@
 """Payment provider notification signatures (iyzico, PayTR).
 
 Verify before reading anything else from the request; an unverified notification is rejected.
-Steps and sources: docs/legal/turkiye.md -> "Ödeme bildirimleri".
+Steps and sources: docs/legal/turkiye.md -> "Payment notifications".
 Sources (checked 2026-10-25): docs.iyzico.com/en/advanced/webhook · dev.paytr.com/en/iframe-api/iframe-api-2-adim
 """
 

package/kit/templates/addons/tr/types/backend/tests/security/test_payment_webhook.py

@@ -19,14 +19,14 @@ SALT = "test-merchant-salt"
 DIRECT = {
     "iyziEventType": "API_AUTH",
     "paymentId": "22416750",
-    "paymentConversationId": "siparis-42",
+    "paymentConversationId": "order-42",
     "status": "SUCCESS",
 }
 CHECKOUT = {
     "iyziEventType": "CHECKOUT_FORM_AUTH",
     "iyziPaymentId": "22416751",
     "token": "tok-abc",
-    "paymentConversationId": "siparis-43",
+    "paymentConversationId": "order-43",
     "status": "SUCCESS",
 }
 PAYTR = {"merchant_oid": "SIP42", "status": "success", "total_amount": "3456"}
@@ -66,7 +66,7 @@ class IyzicoTest(unittest.TestCase):
         self.assertFalse(verify_iyzico({**DIRECT, "status": "FAILURE"}, sig, SECRET))
         self.assertFalse(
             verify_iyzico(
-                {**DIRECT, "paymentConversationId": "siparis-99"}, sig, SECRET
+                {**DIRECT, "paymentConversationId": "order-99"}, sig, SECRET
             )
         )
         self.assertFalse(

package/kit/templates/addons/tr/types/web-saas/.env.example.append

@@ -1,7 +1,7 @@
-# Türkiye eki: ödeme sağlayıcısı (sadece sunucu; kullanmadığını silebilirsin). Ayrıntı: docs/legal/turkiye.md
+# Turkey add-on: payment provider (server only; you can delete the one you do not use). Details: docs/legal/turkiye.md
 IYZICO_API_KEY=
 IYZICO_SECRET_KEY=
-IYZICO_BASE_URL=https://sandbox-api.iyzipay.com   # canlı: https://api.iyzipay.com
+IYZICO_BASE_URL=https://sandbox-api.iyzipay.com   # live: https://api.iyzipay.com
 PAYTR_MERCHANT_ID=
 PAYTR_MERCHANT_KEY=
 PAYTR_MERCHANT_SALT=

package/kit/templates/addons/tr/types/web-saas/.github/workflows/payment-webhook.yml

@@ -1,5 +1,5 @@
-# Ödeme bildirimi imza saldırgan testi (tr eki). Sahte anahtarlarla çalışır; sır gerekmez.
-# Kırmızıysa merge etme: sahte veya değiştirilmiş ödeme bildirimi kabul ediliyor olabilir.
+# Payment notification signature adversarial test (tr add-on). Runs with fake keys; no secret needed.
+# If red, do not merge: a fake or altered payment notification may be accepted.
 name: payment-webhook
 
 on:
@@ -18,5 +18,5 @@ jobs:
       - uses: actions/setup-node@v7
         with:
           node-version: 22
-      # Node 22.18+ .ts modülünü doğrudan çalıştırır; bağımlılık kurulumu gerekmez
+      # Node 22.18+ runs a .ts module directly; no dependency install needed
       - run: node --test tests/security/payment-webhook.mjs

package/kit/templates/addons/tr/types/web-saas/src/lib/payments/webhook-signature.ts

@@ -1,5 +1,5 @@
 // Payment provider notification signatures (iyzico, PayTR). Verify before reading anything else from the request;
-// an unverified notification is rejected. Steps and sources: docs/legal/turkiye.md → "Ödeme bildirimleri".
+// an unverified notification is rejected. Steps and sources: docs/legal/turkiye.md → "Payment notifications".
 // Sources (checked 2026-10-25): docs.iyzico.com/en/advanced/webhook · dev.paytr.com/en/iframe-api/iframe-api-2-adim
 import { createHmac, timingSafeEqual } from 'node:crypto';
 

package/kit/templates/addons/tr/types/web-saas/tests/security/payment-webhook.mjs

@@ -17,8 +17,8 @@ const iyzicoSign = (b, secret = SECRET) => {
 };
 const paytrSign = (f, key = KEY, salt = SALT) => createHmac('sha256', key).update(f.merchant_oid + salt + f.status + f.total_amount).digest('base64');
 
-const direct = { iyziEventType: 'API_AUTH', paymentId: '22416750', paymentConversationId: 'siparis-42', status: 'SUCCESS' };
-const checkout = { iyziEventType: 'CHECKOUT_FORM_AUTH', iyziPaymentId: '22416751', token: 'tok-abc', paymentConversationId: 'siparis-43', status: 'SUCCESS' };
+const direct = { iyziEventType: 'API_AUTH', paymentId: '22416750', paymentConversationId: 'order-42', status: 'SUCCESS' };
+const checkout = { iyziEventType: 'CHECKOUT_FORM_AUTH', iyziPaymentId: '22416751', token: 'tok-abc', paymentConversationId: 'order-43', status: 'SUCCESS' };
 const paytr = { merchant_oid: 'SIP42', status: 'success', total_amount: '3456' };
 
 test('iyzico: a correctly signed notification is accepted (direct and checkout form)', () => {
@@ -30,7 +30,7 @@ test('iyzico: a correctly signed notification is accepted (direct and checkout f
 });
 
 test('iyzico: a payment id rounded by JSON.parse (above 2^53) is rejected', () => {
-  const body = JSON.parse('{"iyziEventType":"CHECKOUT_FORM_AUTH","iyziPaymentId":9007199254740993,"token":"tok-abc","paymentConversationId":"siparis-43","status":"SUCCESS"}');
+  const body = JSON.parse('{"iyziEventType":"CHECKOUT_FORM_AUTH","iyziPaymentId":9007199254740993,"token":"tok-abc","paymentConversationId":"order-43","status":"SUCCESS"}');
   const sent = { ...body, iyziPaymentId: '9007199254740993' };
   assert.equal(verifyIyzico(body, iyzicoSign(sent), SECRET), false);
   assert.equal(verifyIyzico(body, iyzicoSign(body), SECRET), false, 'even when signed over the rounded value');
@@ -39,7 +39,7 @@ test('iyzico: a payment id rounded by JSON.parse (above 2^53) is rejected', () =
 test('iyzico: forged, altered or unsigned notifications are rejected', () => {
   const sig = iyzicoSign(direct);
   assert.equal(verifyIyzico({ ...direct, status: 'FAILURE' }, sig, SECRET), false, 'status changed after signing');
-  assert.equal(verifyIyzico({ ...direct, paymentConversationId: 'siparis-99' }, sig, SECRET), false, 'order switched');
+  assert.equal(verifyIyzico({ ...direct, paymentConversationId: 'order-99' }, sig, SECRET), false, 'order switched');
   assert.equal(verifyIyzico(direct, iyzicoSign(direct, 'attacker-key'), SECRET), false, 'signed with another key');
   assert.equal(verifyIyzico(direct, undefined, SECRET), false, 'no header');
   assert.equal(verifyIyzico(direct, '', SECRET), false, 'empty header');

package/kit/templates/backend/.github/dependabot.yml

@@ -6,7 +6,7 @@ updates:
     schedule:
       interval: weekly
     groups:
-      kucuk-guncellemeler:
+      minor-updates:
         update-types: [minor, patch]
     ignore:
       - dependency-name: "*"

package/kit/templates/backend/.github/workflows/live-monitoring.yml

@@ -3,7 +3,7 @@
 # It also raises an alarm if the /health response takes longer than LIVE_MAX_SECONDS (Variables, default 2) seconds.
 # If something breaks it opens an issue labeled "live-monitoring" (it does not open a new one if one is already open).
 # To enable:
-#   1. Settings > Variables > LIVE_URL = https://api.alanadin.com
+#   1. Settings > Variables > LIVE_URL = https://api.example.com
 #   2. Critical endpoint tests (that delete no data, limited to a test account): as pytest under tests/live/
 #   3. If needed, Settings > Secrets > LIVE_TEST_TOKEN (a test account with restricted rights in prod)
 name: Live monitoring

package/kit/templates/backend/docs/architecture/stack.md

@@ -41,7 +41,7 @@
 | Error tracking | Sentry | |
 | Cron monitoring | Healthchecks.io (dead man's switch) | Alarm if a job does not run |
 
-## Commands (commands)
+## Commands
 
 ```bash
 uv sync                                  # install dependencies
@@ -68,7 +68,7 @@ app/
 │       ├── router.py           # HTTP endpoints (thin)
 │       ├── service.py          # business logic
 │       ├── repository.py       # database access
-│       ├── models.py           # SQLAlchemy modelleri
+│       ├── models.py           # SQLAlchemy models
 │       ├── schemas.py          # Pydantic input/output schemas
 │       ├── dependencies.py
 │       └── exceptions.py
@@ -76,7 +76,7 @@ app/
 └── jobs/                       # scheduled and background jobs (idempotent)
 alembic/                        # migration'lar
 tests/
-├── <feature>/                   # tests by feature (test_AC_01_1_... kabul testleri dahil)
+├── <feature>/                   # tests by feature (test_AC_01_1_... acceptance tests included)
 └── live/                       # live monitoring tests
 Dockerfile  pyproject.toml  uv.lock
 ```

package/kit/templates/mobile/.github/dependabot.yml

@@ -7,7 +7,7 @@ updates:
     schedule:
       interval: weekly
     groups:
-      kucuk-guncellemeler:
+      minor-updates:
         update-types: [minor, patch]
     ignore:
       - dependency-name: "expo"

package/kit/templates/mobile/.github/workflows/ci.yml

@@ -66,8 +66,8 @@ jobs:
         if: hashFiles('supabase/config.toml') != ''
         run: |
           # Only the needed keys are taken; the output is not run as a shell command
-          anahtarlar=$(npx -y supabase@2.120.0 status -o env | grep -E '^(API_URL|ANON_KEY|SERVICE_ROLE_KEY|DB_URL|PUBLISHABLE_KEY|SECRET_KEY)=')
-          while IFS="=" read -r ad deger; do deger="${deger%\"}"; export "$ad=${deger#\"}"; done <<< "$anahtarlar"
+          keys=$(npx -y supabase@2.120.0 status -o env | grep -E '^(API_URL|ANON_KEY|SERVICE_ROLE_KEY|DB_URL|PUBLISHABLE_KEY|SECRET_KEY)=')
+          while IFS="=" read -r name value; do value="${value%\"}"; export "$name=${value#\"}"; done <<< "$keys"
           node --test tests/security/rls.mjs
 
   semgrep:

package/kit/templates/mobile/docs/architecture/stack.md

@@ -36,14 +36,14 @@
 | Error tracking | Sentry (`@sentry/react-native`) | |
 | Test | Jest + React Native Testing Library, Maestro (e2e) | |
 
-## Commands (commands)
+## Commands
 
 ```bash
 npx expo start                          # development
 npx expo lint
 npx tsc --noEmit
 npm run test                            # jest
-npx expo install [paket]                # add a package (picks the SDK-compatible version, not npm install)
+npx expo install [package]              # add a package (picks the SDK-compatible version, not npm install)
 npx expo-doctor                         # dependency compatibility check
 eas build --profile preview --platform all     # test build
 eas build --profile production --platform all  # store build
@@ -72,7 +72,7 @@ src/
 │       ├── types.ts
 │       └── index.ts
 ├── components/                 # shared components: Button, TextField, Screen, EmptyState...
-├── hooks/                      # shared hooks (useBayrak etc.)
+├── hooks/                      # shared hooks (useFlag etc.)
 ├── lib/                        # supabase, sentry, secure storage, analytics clients
 ├── theme/                      # design tokens (from DESIGN.md)
 ├── config/                     # environment variables, constants
@@ -124,7 +124,7 @@ maestro test .maestro/ --format junit --output test-results/junit-e2e.xml
 
 **Feature flags** (`docs/operations/feature-flags.md`): It must be possible to turn a feature off without a store update. The app reads the flag remotely at launch and caches the last known value; with no network, the safe default (off) is used:
 - PostHog feature flags or Firebase Remote Config; or a Supabase `feature_flags` table.
-- Reading goes through a single hook: `hooks/useBayrak.ts`. Features that take payments, use AI or send notifications are not released without a flag.
+- Reading goes through a single hook: `hooks/useFlag.ts`. Features that take payments, use AI or send notifications are not released without a flag.
 
 ## Common AI mistakes (watch for these)
 

package/kit/templates/mobile/docs/architecture/structure.md

@@ -22,7 +22,7 @@ src/
 │       ├── types.ts
 │       └── index.ts
 ├── components/                 # shared components: Button, TextField, Screen, EmptyState...
-├── hooks/                      # shared hooks (useBayrak etc.)
+├── hooks/                      # shared hooks (useFlag etc.)
 ├── lib/                        # supabase, sentry, secure storage, analytics clients
 ├── theme/                      # design tokens (from DESIGN.md)
 ├── config/                     # environment variables, constants

package/kit/templates/mobile/docs/design/design-guide.md

@@ -8,7 +8,7 @@
 > Decisions are made with `/design` using **visual previews** (`docs/workflow/decision-protocol.md` §5). If a new color, size or component
 > is needed, it is asked as a decision first, then added to DESIGN.md. No raw colors or arbitrary sizes in code.
 
-## 1. Chosen direction (Chosen direction)
+## 1. Chosen direction
 
 | Area | Choice | Skill | Preview | Date |
 |---|---|---|---|---|

package/kit/templates/web-saas/.github/dependabot.yml

@@ -7,7 +7,7 @@ updates:
     schedule:
       interval: weekly
     groups:
-      kucuk-guncellemeler:
+      minor-updates:
         update-types: [minor, patch]
     ignore:
       - dependency-name: "*"

package/kit/templates/web-saas/.github/workflows/ci.yml

@@ -82,8 +82,8 @@ jobs:
         if: hashFiles('supabase/config.toml') != ''
         run: |
           # Only the needed keys are taken; the output is not run as a shell command
-          anahtarlar=$(npx -y supabase@2.120.0 status -o env | grep -E '^(API_URL|ANON_KEY|SERVICE_ROLE_KEY|DB_URL|PUBLISHABLE_KEY|SECRET_KEY)=')
-          while IFS="=" read -r ad deger; do deger="${deger%\"}"; export "$ad=${deger#\"}"; done <<< "$anahtarlar"
+          keys=$(npx -y supabase@2.120.0 status -o env | grep -E '^(API_URL|ANON_KEY|SERVICE_ROLE_KEY|DB_URL|PUBLISHABLE_KEY|SECRET_KEY)=')
+          while IFS="=" read -r name value; do value="${value%\"}"; export "$name=${value#\"}"; done <<< "$keys"
           node --test tests/security/rls.mjs
 
   semgrep:

package/kit/templates/web-saas/.github/workflows/live-monitoring.yml

@@ -2,7 +2,7 @@
 # Why 3 hours: GitHub Free gives 2,000 Actions minutes a month in a private repo; an hourly run (~3 min) would cost ~2,160 min (docs.github.com, 2026-10-25).
 # If something breaks it opens an issue labeled "live-monitoring" (it does not open a new one if one is already open).
 # To enable:
-#   1. Settings > Variables > LIVE_URL = https://alanadin.com
+#   1. Settings > Variables > LIVE_URL = https://example.com
 #   2. Create a separate test account with restricted rights in prod: Settings > Secrets > LIVE_TEST_EMAIL, LIVE_TEST_PASSWORD
 #   3. Write the tests under tests/live/*.spec.ts (flows that delete no data, limited to the test account). smoke.spec.ts comes ready:
 #      does the home page open, is it within LIVE_MAX_MS (Variables, default 3000), are there errors in the console.

package/kit/templates/web-saas/docs/architecture/stack.md

@@ -19,7 +19,7 @@
 | 8 | Email | **Resend** (recommended: developer friendly, React email templates; free plan gives 3,000 emails per month, 100 per day (source: https://resend.com/pricing, 2026-10-26)) · Postmark (very high deliverability) · Amazon SES (cheapest, hard to set up) |
 | 9 | Analytics | **Plausible** (cookieless, KVKK friendly; no free plan, starts at 9 dollars per month, 30-day trial (source: https://plausible.io/docs/billing, 2026-10-26)) · PostHog (product analytics, funnels, feature flags) · Umami (self-host, free) · None |
 | 10 | Error tracking | **Sentry** (recommended) · Highlight / Better Stack |
-| 11 | Language support | **Turkish only** (recommended for the MVP) · Turkish + English (next-intl; setting it up from the start is cheaper than adding it later) |
+| 11 | Language support | **One language: the users' language** (recommended for the MVP) · Two or more languages (next-intl; setting it up from the start is cheaper than adding it later) |
 | 12 | Test | **Vitest + Playwright** (recommended) · Playwright only (little logic, mostly UI) |
 
 ## Chosen technologies
@@ -41,7 +41,7 @@
 | Analytics | Plausible / PostHog | Watch cookie consent |
 | Test | Vitest (unit), Playwright (e2e) | |
 
-## Commands (commands)
+## Commands
 
 ```bash
 npm run dev            # development
@@ -98,7 +98,7 @@ supabase/migrations/            # database changes ONLY here
 - Every new table has RLS on, a written policy, and an entry in the `tests/security/rls.mjs` → `TABLES` list (the `rls` job in CI turns red on an unregistered table).
 - On every page, think about `loading.tsx` / empty state / `error.tsx`.
 - Images with `next/image`, links with `next/link`.
-- Texts are in Turkish; format date/money with `Intl` and `tr-TR`.
+- Texts are in the UI language (`docs/product/glossary.md`); format date/money with `Intl` and that locale.
 - Before UI work, read `DESIGN.md` and `docs/design/design-guide.md`; do not go outside the tokens and rules. If a new design decision is needed, use `/design`.
 
 ## Verification (evidence before a task is done)
@@ -152,7 +152,7 @@ npx vitest run --reporter=default --reporter=junit --outputFile.junit=test-resul
 
 - [ ] Vercel prod environment variables entered (Preview and Production separate)
 - [ ] Supabase prod project is separate; prod domain and redirect URLs in Auth → URL Configuration
-- [ ] Supabase email templates in Turkish and a custom SMTP (the default SMTP limit is very low)
+- [ ] Supabase email templates in the UI language and a custom SMTP (the default SMTP limit is very low)
 - [ ] Payment: live keys, live webhook endpoint and signing secret
 - [ ] SEO: `metadata` (title, description), Open Graph image, `sitemap.ts`, `robots.ts`, favicon
 - [ ] Lighthouse (mobile): Performance ≥ 90, Accessibility ≥ 90, SEO ≥ 90

package/kit/templates/web-saas/docs/design/design-guide.md

@@ -8,7 +8,7 @@
 > Decisions are made with `/design` using **visual previews** (`docs/workflow/decision-protocol.md` §5). If a new color, size or component
 > is needed, it is asked as a decision first, then added to DESIGN.md. No raw colors or arbitrary sizes in code.
 
-## 1. Chosen direction (Chosen direction)
+## 1. Chosen direction
 
 | Area | Choice | Skill | Preview | Date |
 |---|---|---|---|---|

package/kit/tools/antigravity/.agents/hooks.json

@@ -1,10 +1,10 @@
 {
-  "kit-oturum": {
+  "kit-session": {
     "SessionStart": [
       { "type": "command", "command": "node .claude/hooks/session-start.mjs" }
     ]
   },
-  "kit-dosya-korumalari": {
+  "kit-file-guards": {
     "PreToolUse": [
       {
         "matcher": "write_to_file|replace_file_content|multi_replace_file_content",
@@ -17,7 +17,7 @@
       }
     ]
   },
-  "kit-duzenleme-turu": {
+  "kit-edit-rounds": {
     "PostToolUse": [
       {
         "matcher": "write_to_file|replace_file_content|multi_replace_file_content",
@@ -30,7 +30,7 @@
       { "type": "command", "command": "node .claude/hooks/edit-rounds.mjs --inject" }
     ]
   },
-  "kit-okuma-korumasi": {
+  "kit-read-guard": {
     "PreToolUse": [
       {
         "matcher": "*",
@@ -40,7 +40,7 @@
       }
     ]
   },
-  "kit-komut-korumalari": {
+  "kit-command-guards": {
     "PreToolUse": [
       {
         "matcher": "run_command",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tillerhand",
-  "version": "3.48.1",
+  "version": "3.49.1",
   "description": "Vibe coding kit for Claude Code, Codex and Antigravity: rules, commands, guards and project templates.",
   "license": "MIT",
   "type": "module",