create-vasvibe 1.2.0 → 2.1.0

package/template/agent/workflows/security.md

@@ -0,0 +1,107 @@
+**ACT AS:** Application Security Expert.
+**CONTEXT:** Bekerja di **dua fase**: (1) Fase **Perencanaan** lewat **Mode S** untuk menetapkan standar keamanan sebagai acuan; (2) Fase **Hardening** (per-release) lewat **Mode A/B/C/D** untuk audit & fix. Berbeda dari QA Agent (static code quality review) — agent ini fokus pada attack surface, eksploitabilitas, dan OWASP Top 10. Gunakan skill `penetration-testing` untuk panduan metodologi.
+
+**INSTRUCTION STEPS:**
+
+Pilih mode sesuai instruksi:
+
+---
+
+### Mode S: Security Standards (Fase Perencanaan)
+1. **Load Context:** Baca `project_overview.md` (terutama Constraints & Compliance) dan domain proyek.
+2. **Define Standards:** Gunakan template `schemas/security-standards.template.md`. Tetapkan:
+   - Auth & authorization model (mechanism, password policy, token TTL, RBAC)
+   - Data protection (encryption in transit/at rest, PII, secrets management)
+   - Input validation & output encoding standards
+   - Security headers, CORS, rate limiting
+   - Compliance requirements (GDPR/UU PDP/PCI-DSS jika relevan)
+   - **Security Acceptance Criteria** — checklist yang harus lulus sebelum release
+3. **Output:** Tulis `state/knowledge_base/security/security-standards.md`.
+4. **Handoff:** Beri tahu Orchestrator standar siap — semua engineer wajib mengikutinya, dan kamu akan memverifikasinya di Hardening.
+
+---
+
+### Mode A: Threat Modeling
+1. **Load Context:** Baca `project_overview.md` dan spesifikasi yang relevan di `specifications/`.
+2. **Architecture Review:** Identifikasi entry points, data flows, dan trust boundaries dari codebase.
+3. **Threat Identification (STRIDE):**
+   - **S**poofing — identity palsu (auth bypass, token forgery)
+   - **T**ampering — manipulasi data (request injection, parameter pollution)
+   - **R**epudiation — aksi yang tidak bisa diaudit (missing logs)
+   - **I**nformation Disclosure — data bocor (verbose error, PII exposure)
+   - **D**enial of Service — resource exhaustion (no rate limit, unbounded query)
+   - **E**levation of Privilege — akses melampaui izin (IDOR, broken authz)
+4. **Attack Surface Map:** Dokumentasikan semua endpoint, mekanisme autentikasi, dan data stores.
+5. **Output:** Tulis hasil ke `task/[TASK-ID]/security_threat_model.md`.
+
+---
+
+### Mode B: Vulnerability Scan
+1. **Load Context:** Baca codebase yang relevan dan `project_overview.md`.
+2. **OWASP Top 10 Review:**
+   - A01: Broken Access Control — cek authorization di setiap endpoint
+   - A02: Cryptographic Failures — cek hashing password, enkripsi data sensitif
+   - A03: Injection — SQL, XSS, Command injection di semua input
+   - A04: Insecure Design — validasi business logic dan alur autentikasi
+   - A05: Security Misconfiguration — cek CORS, HTTP headers, error messages
+   - A06: Vulnerable Components — dependency yang outdated atau ada CVE
+   - A07: Auth & Session Failures — JWT validation, session expiry, brute force protection
+   - A08: Software & Data Integrity Failures — unsigned data, insecure deserialization
+   - A09: Logging & Monitoring Failures — apakah security events di-log?
+   - A10: SSRF — external URL fetching tanpa validasi
+3. **Secrets Scan:** Cari hardcoded credentials, API keys, atau secrets di source code.
+4. **Dependency Scan:** Jalankan `npm audit` (atau `pip audit`, `bundle audit`, dll sesuai tech stack) dan catat hasilnya.
+5. **Output:** Tulis ke `task/[TASK-ID]/security_report.md` menggunakan template `schemas/security_report.template.md`.
+
+---
+
+### Mode C: Security Fix
+1. **Read Report:** Baca `task/[TASK-ID]/security_report.md` yang sudah ada.
+2. **Repo Management:**
+   > 📎 **BACA DAN IKUTI** `agent/workflows/_shared/git-branch-management.md` — pastikan bekerja di branch yang benar sebelum menulis fix.
+3. **Prioritize:** Tangani temuan CRITICAL dan HIGH terlebih dahulu.
+4. **Implement Fix:**
+   - Input validation & sanitization
+   - Parameterized queries (SQL injection prevention)
+   - Output encoding (XSS prevention)
+   - Security headers (CSP, HSTS, X-Frame-Options)
+   - Dependency upgrades untuk packages yang vulnerable
+5. **Verify Fix:** Pastikan fix tidak break fungsionalitas existing. Jalankan unit test jika tersedia.
+6. **Log Fix:** Append ke `task/[TASK-ID]/security_report.md` di section `## Fixes Applied`.
+7. **Update Status:** Tulis `state/agent_handoff.json` dengan status dan temuan utama.
+
+---
+
+### Mode D: Pre-release Audit
+1. **Scope:** Fokus hanya pada kode yang berubah sejak release terakhir (gunakan `git diff` dengan tag release sebelumnya).
+2. **Quick OWASP Check:** Jalankan Mode B dengan scope terbatas pada perubahan tersebut.
+3. **Secrets Verification:** Final check — tidak ada credentials yang ter-commit.
+4. **Dependency Final Check:** `npm audit --audit-level=high`
+5. **Output:** Append hasil ke `task/[RELEASE-VERSION]/security_report.md`.
+
+---
+
+**CRITICAL RULES:**
+- JANGAN pernah commit atau push credential yang ditemukan — segera report ke human untuk ditangani.
+- Gunakan skill `penetration-testing` untuk panduan metodologi detail dan tooling.
+- Severity: **CRITICAL** (eksploitasi langsung) > **HIGH** (butuh kondisi tertentu) > **MEDIUM** (mitigasi ada) > **LOW** (minor) > **INFO** (best practice).
+- SELALU buat atau update `security_report.md` di akhir setiap mode.
+- Jika menemukan CRITICAL: BERHENTI dan laporkan ke human sebelum lanjut.
+
+**INPUT SAYA:**
+"[Mode S/A/B/C/D]: [scope atau target — misal: 'Mode S: tetapkan standar', 'Mode D: v2.0.0']"
+
+## Work Depth
+> 📎 Baca level aktif di `project_overview.md` → `WORK_DEPTH`. Detail: `agent/workflows/_shared/work-depth.md`
+
+| Level | Behavior |
+|-------|----------|
+| **fast** | Skip — Security tidak dipanggil pada mode fast |
+| **standard** | Mode S di Perencanaan (opsional); Mode D di `/release` (Hardening) |
+| **deep** | Mode S wajib di Perencanaan; Mode A+B+C+D penuh di Hardening per-release |
+
+## Change Management
+> 📎 **BACA DAN IKUTI** `agent/workflows/_shared/change-management.md` — perubahan standar keamanan WAJIB di-ADR dan notify semua engineer.
+
+## State Management
+> 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`

package/template/agent/workflows/sysarch.md

@@ -294,5 +294,8 @@ Specs:
 | **standard** | Arsitektur lengkap + capacity planning |
 | **deep** | + Disaster recovery plan, multi-region consideration, security architecture review |
 
+## Change Management
+> 📎 **BACA DAN IKUTI** `agent/workflows/_shared/change-management.md` — setiap perubahan dari user WAJIB ditulis ke dokumen acuan terkait + notify agen hilir. No silent changes.
+
 ## State Management
 > 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`

package/template/agent/workflows/tester.md

@@ -93,5 +93,8 @@
 | **standard** | Full E2E test suite sesuai spec |
 | **deep** | + Edge cases, negative tests, performance assertion dasar |
 
+## Change Management
+> 📎 **BACA DAN IKUTI** `agent/workflows/_shared/change-management.md` — setiap perubahan dari user WAJIB ditulis ke dokumen acuan terkait + notify agen hilir. No silent changes.
+
 ## State Management
 > 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`

package/template/agent/workflows/ux-designer.md

@@ -0,0 +1,45 @@
+**ACT AS:** UX/UI Designer.
+**CONTEXT:** Fase Perencanaan (Planning). Merancang design system dan UX proyek: prinsip desain, color palette, tipografi, spacing, spec komponen, dan pola interaksi. Output kamu adalah **acuan** yang diikuti Frontend Engineer. Berbeda dari Frontend Engineer — kamu merancang (design-time), bukan meng-implementasi kode.
+
+**ACUAN INPUT:**
+- `project_overview.md` — bagian "UI/UX Guidelines & Design System" dan "Visual Vibe"
+- `specifications/` — alur fitur yang butuh UI
+
+**INSTRUCTION STEPS:**
+1.  **Load Context:** Baca `project_overview.md`, terutama Visual Vibe, target audience, dan UI guidelines yang sudah diisi Initiator.
+2.  **Validate:** Jika Visual Vibe / brand direction belum jelas, BERHENTI dan tanyakan ke human (warna brand, mood, referensi).
+3.  **Use Skill:** **CRITICAL** — gunakan skill `ui-ux-pro-max` untuk memilih style, palette, font pairing, dan pola UX yang sesuai dengan jenis produk.
+4.  **Directory Check:** Cek/Buat `state/knowledge_base/design-system/`.
+5.  **Build Design System:** Gunakan template `schemas/design-system.template.md`. Hasilkan `state/knowledge_base/design-system/design-system.md` mencakup:
+    - **Design Principles** (3-5)
+    - **Color Palette** (token + hex + usage)
+    - **Typography** (role, font, size, weight)
+    - **Spacing & Layout** (scale, breakpoints, container)
+    - **Component Specs** (variants & states untuk Button, Input, Card, Modal, Navbar, Table)
+    - **Interaction & Motion** (durasi, easing, feedback states)
+    - **Accessibility** (kontras, focus, keyboard, ARIA)
+6.  **Wireframe (opsional, deep):** Untuk alur kompleks, sertakan wireframe teks/ASCII atau deskripsi layout per screen.
+7.  **Human Review Loop:** Minta human review. Revisi sesuai feedback, update Revision History.
+8.  **Finalize:** Tandai `Approved`. Beri tahu Orchestrator design system siap dipakai Frontend Engineer.
+
+**PRINSIP:**
+- Design system adalah satu sumber kebenaran visual — Frontend tidak boleh mengarang di luar ini.
+- Konsisten > kreatif berlebihan. Setiap token punya alasan.
+
+**INPUT SAYA:**
+"Rancang design system untuk [proyek]."
+
+## Work Depth
+> 📎 Baca level aktif di `project_overview.md` → `WORK_DEPTH`. Detail: `agent/workflows/_shared/work-depth.md`
+
+| Level | Behavior |
+|-------|----------|
+| **fast** | Palette + tipografi + token dasar, komponen inti saja |
+| **standard** | Full design system: semua komponen kunci + states + motion |
+| **deep** | + Wireframe per screen, a11y spec lengkap, dark mode, responsive detail, design tokens export |
+
+## Change Management
+> 📎 **BACA DAN IKUTI** `agent/workflows/_shared/change-management.md` — perubahan design system WAJIB di-update di acuan dan notify Frontend Engineer.
+
+## State Management
+> 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`

package/template/schemas/adr.template.md

@@ -0,0 +1,36 @@
+# ADR-[NNN]: [Judul Keputusan Singkat]
+
+**Status:** `Proposed` / `Accepted` / `Superseded by ADR-XXX` / `Deprecated`
+**Date:** [YYYY-MM-DD]
+**Author Agent:** [agen yang membuat]
+**Phase:** [Planning / Implementation / Testing / Hardening]
+
+---
+
+## Context
+
+[Apa situasi/masalah yang memicu keputusan ini? Kalau perubahan diminta user, sebutkan permintaannya.]
+
+## Decision
+
+[Keputusan yang diambil — jelas dan ringkas.]
+
+## Alternatives Considered
+
+| Opsi | Pro | Kontra | Dipilih? |
+|------|-----|--------|----------|
+| [Opsi A] | | | ✅ / ❌ |
+| [Opsi B] | | | ✅ / ❌ |
+
+## Consequences
+
+- **Positif:** [keuntungan]
+- **Negatif / Trade-off:** [biaya, risiko, utang teknis]
+- **Dokumen acuan yang ikut berubah:** [daftar file yang di-update karena keputusan ini]
+- **Agen yang perlu tahu:** [Backend / Frontend / Tester / dll]
+
+## Revision History
+
+| Timestamp | Agen | Perubahan |
+|-----------|------|-----------|
+| [YYYY-MM-DD HH:MM] | [agen] | ADR dibuat |

package/template/schemas/data-model.template.md

@@ -0,0 +1,57 @@
+# DATA MODEL — [Project Name]
+
+**Owner Agent:** Data Architect
+**Date:** [YYYY-MM-DD HH:MM]
+**Phase:** Planning
+**Status:** `Draft` / `Approved`
+
+> Acuan resmi struktur data proyek. Backend Engineer WAJIB mengikuti ini. Perubahan harus lewat `_shared/change-management.md`.
+
+---
+
+## 1. Entity Overview
+
+[Daftar entity utama dan deskripsi singkat perannya.]
+
+## 2. Entity Relationship Diagram (ERD)
+
+```
+[Diagram teks / mermaid. Contoh:
+User ||--o{ Booking : places
+Booking }o--|| Tour : references
+]
+```
+
+## 3. Schema Detail
+
+### [Entity: User]
+| Field | Type | Constraints | Notes |
+|-------|------|-------------|-------|
+| id | UUID | PK | |
+| email | string | unique, not null | |
+| password_hash | string | not null | bcrypt, JANGAN simpan plaintext |
+| created_at | timestamp | default now | |
+
+*(Ulangi per entity)*
+
+## 4. Indexes & Performance
+
+- [Index yang dibutuhkan untuk query berat — misal: `idx_booking_user_id`]
+
+## 5. Data Governance
+
+- **PII fields:** [daftar field sensitif — email, phone, dll]
+- **Retention:** [berapa lama data disimpan]
+- **Encryption at rest:** [field mana yang dienkripsi]
+- **Audit:** [tabel mana yang butuh audit log]
+
+## 6. Migration Strategy
+
+- [Tooling migrasi — Prisma Migrate, TypeORM, Alembic, dll]
+- [Strategi seed data]
+
+## Revision History
+
+| Timestamp | Agen | Perubahan |
+|-----------|------|-----------|
+| [YYYY-MM-DD HH:MM] | Data Architect | Initial data model |

package/template/schemas/design-system.template.md

@@ -0,0 +1,63 @@
+# DESIGN SYSTEM — [Project Name]
+
+**Owner Agent:** UX Designer
+**Date:** [YYYY-MM-DD HH:MM]
+**Phase:** Planning
+**Status:** `Draft` / `Approved`
+
+> Acuan resmi UI/UX proyek. Frontend Engineer WAJIB mengikuti ini. Perubahan harus lewat `_shared/change-management.md`.
+
+---
+
+## 1. Design Principles
+
+[3-5 prinsip — misal: "Mobile-first", "Aksesibilitas WCAG AA", "Minimalis, fokus konten"]
+
+## 2. Color Palette
+
+| Token | Value (Hex) | Usage |
+|-------|-------------|-------|
+| primary | #____ | tombol utama, link |
+| secondary | #____ | aksen |
+| background | #____ | latar |
+| surface | #____ | card, panel |
+| text-primary | #____ | teks utama |
+| error / success / warning | #____ | state |
+
+## 3. Typography
+
+| Role | Font | Size | Weight |
+|------|------|------|--------|
+| Heading 1 | [font] | | |
+| Body | [font] | | |
+| Caption | [font] | | |
+
+## 4. Spacing & Layout
+
+- **Scale:** [4px base / 8px grid / dll]
+- **Breakpoints:** mobile < 640, tablet 640–1024, desktop > 1024
+- **Container max-width:** [px]
+
+## 5. Component Specs
+
+### [Component: Button]
+- **Variants:** primary, secondary, ghost, destructive
+- **States:** default, hover, active, disabled, loading
+- **Radius / shadow:** [nilai]
+
+*(Ulangi untuk komponen kunci: Input, Card, Modal, Navbar, Table)*
+
+## 6. Interaction & Motion
+
+- **Animasi:** [durasi, easing — misal 200ms ease-out]
+- **Feedback:** loading state, empty state, error state
+
+## 7. Accessibility
+
+- Kontras minimum, focus ring, keyboard nav, ARIA labels
+
+## Revision History
+
+| Timestamp | Agen | Perubahan |
+|-----------|------|-----------|
+| [YYYY-MM-DD HH:MM] | UX Designer | Initial design system |

package/template/schemas/requirements.template.md

@@ -0,0 +1,64 @@
+# REQUIREMENTS — [Project Name]
+
+**Owner Agent:** Discovery
+**Date:** [YYYY-MM-DD HH:MM]
+**Phase:** Planning (hulu)
+**Status:** `Gathering` / `Approved`
+
+> Hasil requirement gathering dengan human. Acuan paling hulu — menjadi input Initiator untuk `project_overview.md`. Perubahan lewat `_shared/change-management.md`.
+
+---
+
+## 1. Problem & Goals
+- **Masalah:** [masalah yang diselesaikan]
+- **Kenapa sekarang:** [urgensi/konteks]
+- **Definisi sukses (metrik):** [bagaimana tahu ini berhasil]
+
+## 2. Users & Personas
+| Persona | Konteks / Pain | Kebutuhan utama |
+|---------|----------------|-----------------|
+| [Admin] | | |
+| [End user] | | |
+
+## 3. Scope
+- **Must-have:** [fitur wajib]
+- **Nice-to-have:** [fitur opsional]
+- **Out of scope (eksplisit):** [yang TIDAK dikerjakan]
+
+## 4. Key Features & Flows
+- [Alur/fitur utama 1]
+- [Alur/fitur utama 2]
+
+## 5. Non-Functional Requirements
+- **Skala/Beban:** [perkiraan user, transaksi]
+- **Performa:** [target response time, dll]
+- **Security & Compliance:** [GDPR / UU PDP / PCI-DSS / dll]
+- **Availability:** [uptime target jika ada]
+- **Budget:** [jika relevan]
+
+## 6. Constraints
+- **Tech preferences:** [stack yang diinginkan/dihindari]
+- **Sistem existing:** [yang harus diintegrasikan]
+- **Timeline & tim:** [deadline, ukuran tim]
+
+## 7. Data & Integrations
+- **Data sensitif:** [PII, finansial, dll]
+- **Integrasi pihak ketiga:** [payment, auth, notifikasi, dll]
+
+## 8. Assumptions
+- [Asumsi 1 — perlu diverifikasi]
+- [Asumsi 2]
+
+## 9. Open Questions
+- [ ] [Pertanyaan yang belum terjawab 1]
+- [ ] [Pertanyaan 2]
+
+## 10. Risks
+| Risiko | Dampak | Mitigasi awal |
+|--------|--------|---------------|
+| | | |
+
+## Revision History
+| Timestamp | Agen | Perubahan |
+|-----------|------|-----------|
+| [YYYY-MM-DD HH:MM] | Discovery | Initial requirements gathered |

package/template/schemas/security-standards.template.md

@@ -0,0 +1,58 @@
+# SECURITY STANDARDS — [Project Name]
+
+**Owner Agent:** Security Expert (Mode Standards)
+**Date:** [YYYY-MM-DD HH:MM]
+**Phase:** Planning
+**Status:** `Draft` / `Approved`
+
+> Acuan standar keamanan proyek yang ditetapkan di awal. Semua engineer WAJIB mengikuti. Diverifikasi ulang oleh Security di fase Hardening. Perubahan lewat `_shared/change-management.md`.
+
+---
+
+## 1. Authentication & Authorization
+
+- **Auth mechanism:** [JWT / session / OAuth2 — pilih dan jelaskan]
+- **Password policy:** [hashing algo (bcrypt/argon2), min length, complexity]
+- **Token expiry:** [access token TTL, refresh token strategy]
+- **Authorization model:** [RBAC / ABAC — daftar role dan permission]
+
+## 2. Data Protection
+
+- **Encryption in transit:** TLS 1.2+ wajib
+- **Encryption at rest:** [field/tabel yang dienkripsi]
+- **PII handling:** [masking, minimization]
+- **Secrets management:** semua via env var, JANGAN hardcode; daftarkan di `.env.example`
+
+## 3. Input Validation & Output Encoding
+
+- Validasi semua input di server-side
+- Parameterized queries (anti SQL injection)
+- Output encoding (anti XSS)
+
+## 4. Security Headers & Config
+
+- CSP, HSTS, X-Frame-Options, X-Content-Type-Options
+- CORS policy: [origin yang diizinkan]
+- Rate limiting: [batas per endpoint sensitif]
+
+## 5. Compliance Requirements
+
+- [GDPR / UU PDP / PCI-DSS — jika relevan]
+
+## 6. Threat Model Summary
+
+[Threat utama yang diantisipasi sejak desain — referensi ke STRIDE jika sudah ada threat model.]
+
+## 7. Security Acceptance Criteria
+
+Checklist yang harus lulus sebelum release (diverifikasi Security di Hardening):
+- [ ] Tidak ada hardcoded secret
+- [ ] Semua endpoint ter-proteksi authz
+- [ ] Dependency bebas CVE critical/high
+- [ ] OWASP Top 10 ter-review
+
+## Revision History
+
+| Timestamp | Agen | Perubahan |
+|-----------|------|-----------|
+| [YYYY-MM-DD HH:MM] | Security | Initial security standards |

package/template/schemas/security_report.template.md

@@ -0,0 +1,89 @@
+# SECURITY REPORT - [TASK-ID / SCOPE]
+
+**Date:** [YYYY-MM-DD HH:MM]
+**Agent:** Security Expert Agent
+**Scope:** [Deskripsi scope yang diaudit — misal: "Fitur Login & Auth", "Seluruh codebase", "v1.2.0 release"]
+**Mode:** [A: Threat Model / B: Vulnerability Scan / C: Security Fix / D: Pre-release Audit]
+
+---
+
+## Executive Summary
+
+[Ringkasan singkat — apa yang diaudit, berapa temuan, dan rekomendasi utama.]
+
+**Overall Risk Level:** `CRITICAL` / `HIGH` / `MEDIUM` / `LOW` / `CLEAR`
+
+---
+
+## Findings
+
+### CRITICAL
+| # | Vulnerability | Location | Description | Recommendation |
+|---|---------------|----------|-------------|----------------|
+| 1 | | | | |
+
+### HIGH
+| # | Vulnerability | Location | Description | Recommendation |
+|---|---------------|----------|-------------|----------------|
+| 1 | | | | |
+
+### MEDIUM
+| # | Vulnerability | Location | Description | Recommendation |
+|---|---------------|----------|-------------|----------------|
+| 1 | | | | |
+
+### LOW / INFO
+| # | Vulnerability | Location | Description | Recommendation |
+|---|---------------|----------|-------------|----------------|
+| 1 | | | | |
+
+---
+
+## OWASP Top 10 Checklist
+
+- [ ] A01: Broken Access Control
+- [ ] A02: Cryptographic Failures
+- [ ] A03: Injection (SQL, XSS, Command)
+- [ ] A04: Insecure Design
+- [ ] A05: Security Misconfiguration
+- [ ] A06: Vulnerable & Outdated Components
+- [ ] A07: Authentication & Session Failures
+- [ ] A08: Software & Data Integrity Failures
+- [ ] A09: Security Logging & Monitoring Failures
+- [ ] A10: Server-Side Request Forgery (SSRF)
+
+---
+
+## Dependency Scan Results
+
+```
+[Output dari npm audit / pip audit / bundle audit]
+```
+
+**Vulnerable packages found:** [X critical, Y high, Z moderate]
+
+---
+
+## Secrets Scan Results
+
+- [ ] No hardcoded credentials found
+- [ ] No API keys in source code
+- [ ] `.env.example` does not contain real values
+- [ ] `.gitignore` covers all `.env` variants
+
+---
+
+## Fixes Applied
+
+| # | Vulnerability | Fix Description | Files Changed | Timestamp |
+|---|---------------|-----------------|---------------|-----------|
+| 1 | | | | |
+
+---
+
+## Sign-off
+
+- **Status:** `Pending Fix` / `All Clear` / `Conditional Approval`
+- **Remaining Issues:** [Daftar temuan yang belum di-fix dan alasannya — misal: "MEDIUM-1: accepted risk, ditangani di sprint berikutnya"]
+- **Next Action:** [Fix CRITICAL-1 sebelum deploy / Ready for release / dll]
+- **Reviewed By:** [Security Agent + Human approval jika sudah di-review]

package/template/state/knowledge_base/requirements/.gitkeep

@@ -0,0 +1 @@
+# Keep this folder tracked by git