@tera-system/core 0.1.0

package/core/tera-system/profiles/dotnet-razorpages-adonet.md

@@ -0,0 +1,137 @@
+# Technology Profile: dotnet-razorpages-adonet
+
+## 1. Profile Identity
+
+- Profile ID: `dotnet-razorpages-adonet`
+- Language: C#
+- Framework: ASP.NET Core Razor Pages (.NET 8 LTS)
+- Database: SQL Server (destination) + Oracle (source, read-only via ODP.NET)
+- ORM: ADO.NET SqlBulkCopy (data loading), Entity Framework Core (config + logs only)
+- Package Manager / CLI: dotnet CLI, NuGet
+- UI Library: Syncfusion (Blazor/Razor components via TagHelpers or JS interop)
+- Default Project Type: Internal business application with data integration
+
+## 2. Applicability
+
+Use this profile when:
+- The approved architecture uses ASP.NET Core Razor Pages (not Blazor Server/WebAssembly)
+- The application needs to connect to Oracle as a data source (read-only)
+- Data is loaded into SQL Server via ADO.NET SqlBulkCopy for performance
+- EF Core is used only for application-level configuration and logging
+- The application is deployed on IIS (local or on-premise)
+
+This profile covers:
+- ASP.NET Core Razor Pages (server-rendered, not SPA)
+- Oracle.ManagedDataAccess (ODP.NET) for Oracle connectivity
+- ADO.NET SqlBulkCopy for high-performance data transfer
+- EF Core for config/logs tables only
+- Syncfusion components for dashboard/report UI
+- IIS hosting model
+
+## 3. Default Execution Order
+
+1. Scaffold the .NET solution structure (API project + Razor Pages project).
+2. Add only the required base packages (ODP.NET, EF Core, Syncfusion license key).
+3. Create config/logs database schema (EF Core entities + migrations).
+4. Build Oracle connection and data extraction layer (ODP.NET).
+5. Build SQL Server data loading layer (SqlBulkCopy).
+6. Build Sync Engine (full refresh + incremental-ready architecture).
+7. Build Sync Logs and monitoring.
+8. Build Dashboard layout and rendering (Razor Pages + Syncfusion).
+9. Build Drill Down and navigation.
+10. Build Admin Panel (Card CRUD + config).
+11. Integrate Sync Status display in Dashboard.
+12. IIS deployment configuration.
+
+## 4. First Task Rule
+
+Safe first task:
+
+```text
+Scaffold .NET 8 solution structure with two projects:
+  WarehouseDashboard.Api     (Console / Worker Service for sync engine)
+  WarehouseDashboard.Web      (ASP.NET Core Razor Pages)
++ Add base packages: Oracle.ManagedDataAccess.Core, Microsoft.Data.SqlClient,
+  Microsoft.EntityFrameworkCore.SqlServer, Syncfusion.Blazor (for license)
++ Verify solution builds cleanly
+```
+
+**Do NOT** in the first task:
+- Add EF Core entities
+- Add migrations or database update
+- Add Oracle connection logic
+- Add any business logic
+- Add any UI rendering
+- Add authentication/authorization
+
+## 5. Scaffold Rules
+
+- Use `dotnet new razor` for the Web project, `dotnet new console` or `dotnet new webapi` for the API project.
+- Solution file should be at root with two project references.
+- Keep the first task limited to project structure and minimum approved packages.
+- Syncfusion license key is set via `Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense()` in `Program.cs`.
+- IIS hosting: configure `appsettings.json` with `"Urls": "http://localhost:5000"` as default, configurable via IIS.
+
+## 6. ORM / Database Rules
+
+**Entity Framework Core (Config + Logs only):**
+- Used exclusively for `WarehouseDashboardDbContext` with Config entities (CardConfig, DataSourceConfig, etc.) and Log entities (SyncLog, ErrorLog, etc.).
+- `dotnet ef migrations add` belongs to a separate migration task.
+- `dotnet ef database update` is forbidden unless the task is explicitly a database apply task.
+- Do not use EF Core for Oracle data entities or bulk operations.
+
+**ADO.NET / SqlBulkCopy (Data Loading):**
+- Used for all Oracle-to-SQL Server data transfer.
+- SqlBulkCopy belongs to a dedicated data-loading task.
+- Oracle connection is via `Oracle.ManagedDataAccess.Client.OracleConnection`.
+- Full Refresh = DELETE all rows + SqlBulkCopy.WriteToServer in single transaction.
+- Incremental Sync ready architecture = track LastSyncTimestamp, support Upsert pattern.
+
+**Oracle (Read-Only Source):**
+- ODP.NET connections are read-only by convention.
+- Oracle table details are deferred — client provides during execution.
+- Oracle Managed Data Access (NuGet: Oracle.ManagedDataAccess.Core).
+
+## 7. CLI Side Effects
+
+- `dotnet new razor` creates Razor Pages boilerplate files.
+- `dotnet new console` creates console app boilerplate.
+- `dotnet add package` modifies `.csproj`.
+- `dotnet ef migrations add` creates migration files.
+- `dotnet ef database update` changes database state.
+- `dotnet build` / `dotnet publish` produce output files.
+
+## 8. Forbidden Defaults
+
+Do not add by default in the first implementation task:
+
+- EF Core entities or DbContext
+- Migrations or database update
+- Oracle connection logic
+- SyncEngine logic
+- Dashboard UI
+- Admin Panel
+- Authentication/Authorization
+- Custom UI styling beyond Syncfusion defaults
+- Repository layer without clear need
+- SignalR or real-time features
+- Background services (unless explicitly delegated)
+
+## 9. Pre-Execution Gate Additions
+
+- Confirm scaffold task does not silently add Identity, EF migrations, or extra hosting layers.
+- Confirm ODP.NET is isolated from EF Core DbContext (separate concerns).
+- Confirm SqlBulkCopy tasks are not combined with Oracle extraction tasks unless the task explicitly combines them with approval.
+- Confirm database update commands are isolated in dedicated tasks.
+- Confirm Syncfusion license key is registered before any component usage.
+- Confirm IIS hosting model is configured correctly (no Kestrel-only assumptions).
+
+## 10. Acceptance Criteria Patterns
+
+- .NET 8 solution builds cleanly with both projects.
+- Required packages are installed and version-compatible.
+- Solution can be published for IIS deployment (`dotnet publish -c Release`).
+- Oracle connection can be established (tested in dedicated task).
+- SQL Server config/logs schema can be created (tested in dedicated task).
+- No unapproved packages, entities, migrations, or auth were added.
+- No unapproved database changes were applied.

package/core/tera-system/profiles/dotnet-wpf-sqlite.md

@@ -0,0 +1,159 @@
+# Technology Profile: dotnet-wpf-sqlite
+
+> **✅ معتمد من Majed — جاهز للاستخدام في التنفيذ**
+
+## 1. Profile Identity
+
+- Profile ID: `dotnet-wpf-sqlite`
+- Language: **C# (.NET 8)**
+- Framework: **WPF (Windows Presentation Foundation)** مع **CommunityToolkit.Mvvm**
+- Database: **SQLite**
+- ORM: **Entity Framework Core** (موصى به) أو **Microsoft.Data.Sqlite** (يدوي)
+- Package Manager / CLI: `dotnet CLI` + `NuGet`
+- Default Project Type: **WPF Application** (`dotnet new wpf`)
+- Template: `dotnet new wpf -n <ProjectName>`
+
+## 2. Applicability
+
+يُستخدم هذا البروفايل عندما يكون المشروع:
+- تطبيق **Windows Desktop** (WPF)
+- يعمل **محلياً** (لا سيرفر، لا API)
+- **مستخدم واحد** (أو عدد محدود بصلاحيات بسيطة)
+- مع **SQLite** كقاعدة بيانات
+- مع أو بدون تكامل Outlook
+
+لا يُستخدم لـ:
+- تطبيقات Web
+- تطبيقات Mobile
+- تطبيقات متعددة المستخدمين تحتاج سيرفر
+
+## 3. Default Execution Order
+
+1. Scaffold (إنشاء حل WPF + هيكل المشروع)
+2. إعداد SQLite + Data Layer (Entities + Context + Migrations)
+3. تطبيق طبقة MVVM (Models ← ViewModels ← Services ← Views)
+4. شاشة Login (S1)
+5. شاشة Settings (S2) — الموردين + القطع + التوقيعات + الترويسة
+6. شاشة Quotation Form (S3) — جوهر التطبيق
+7. شاشة Quotation List (S4)
+8. شاشة Reports (S5) — التقارير الأربعة
+9. طباعة + PDF
+10. Outlook Integration (اختياري)
+11. Auto Backup
+12. اختبار + تسليم
+
+## 4. First Task Rule
+
+أول مهمة تنفيذ آمنة:
+
+```text
+TASK-COD-001: Scaffold WPF Project + SQLite Setup
+```
+
+يشمل:
+- `dotnet new wpf` مع هيكل MVVM (Models, ViewModels, Views, Services, Data)
+- إضافة حزمة `CommunityToolkit.Mvvm` و `Microsoft.EntityFrameworkCore.Sqlite`
+- إنشاء ApplicationDbContext + Seed (إن وجد)
+- تطبيق أول Migration
+- التأكد من أن التطبيق يشتغل (Run دون أخطاء)
+
+## 5. Scaffold Rules
+
+```text
+# إنشاء مشروع WPF
+dotnet new wpf -n MyApp -o .\src\MyApp
+
+# إضافة الحزم الأساسية
+dotnet add .\src\MyApp\MyApp.csproj package CommunityToolkit.Mvvm
+dotnet add .\src\MyApp\MyApp.csproj package Microsoft.EntityFrameworkCore.Sqlite
+dotnet add .\src\MyApp\MyApp.csproj package QuestPDF  # للـ PDF
+dotnet add .\src\MyApp\MyApp.csproj package Microsoft.Office.Interop.Outlook
+
+# إنشاء مجلدات الهيكل
+New-Item -ItemType Directory -Path .\src\MyApp\Models, .\src\MyApp\ViewModels, .\src\MyApp\Views, .\src\MyApp\Services, .\src\MyApp\Data
+```
+
+**قيود الـ Scaffold:**
+- لا تنشئ `Views/` افتراضية غير Shutdown
+- لا تعدل `App.xaml` لتغيير StartupUri قبل تجهيز MainWindow
+- لا تنشئ واجهات Login قبل تجهيز منطق المصادقة
+- لا تنشئ أكثر من مشروع واحد في الحل إلا إذا تطلب الأمر
+
+## 6. ORM / Database Rules
+
+- **حدود الـ EF Core Migrations:**
+  - `Add-Migration <name>` لإنشاء migration
+  - `Update-Database` لتطبيقها
+  - لا تحذف migration موجودة
+  - لا تعدل migration يدوياً إلا لتصحيح خطأ محدد
+
+- **Schema:**
+  - كل Entity يكون في `Models/`
+  - DbSet Properties في `Data/AppDbContext.cs`
+   - ConnectionString: `Data Source=MyApp.db` (ملف محلي)
+
+- **Database-side Validation:**
+  - استخدام Data Annotations (`[Required]`, `[MaxLength]`, إلخ)
+  - استخدام Fluent API في `OnModelCreating` للعلاقات
+
+- **SQLite Limits:**
+  - لا تستخدم Stored Procedures (غير مدعومة)
+  - لا تستخدم Types خاصة بـ SQL Server
+  - استخدم `HasColumnType` لضبط الأنواع عند الحاجة
+
+## 7. CLI Side Effects
+
+| الأمر | التأثير الجانبي |
+|:------|:----------------|
+| `dotnet new wpf` | ينشئ ملف `.csproj` + `App.xaml` + `MainWindow.xaml` |
+| `dotnet add package ...` | يعدّل `.csproj` (إضافة PackageReference) |
+| `dotnet build` | لا تأثير جانبي — آمن |
+| `dotnet run` | لا تأثير جانبي — آمن |
+| `Add-Migration` | ينشئ ملف `.cs` في `Migrations/` |
+| `Update-Database` | ينشئ/يعدّل ملف `SQLite.db` في مجلد المشروع |
+| `dotnet publish` | ينشئ مجلد `publish/` بالمخرجات القابلة للتوزيع |
+
+## 8. Forbidden Defaults
+
+ما **يمنع** إنشاؤه افتراضياً بدون طلب صريح:
+
+- ❌ **لا** Views إضافية (غير الـ 5 شاشات المطلوبة)
+- ❌ **لا** Admin Panel/Panel إضافي
+- ❌ **لا** صفحات Settings إضافية
+- ❌ **لا** شاشات Reporting إضافية
+- ❌ **لا** إشعارات النظام
+- ❌ **لا** خلفية سيرفر DB (SQL Server, PostgreSQL)
+- ❌ **لا** Docker
+- ❌ **لا** Unit Tests (للمشاريع الصغيرة جداً — يُضاف إذا طُلب)
+- ❌ **لا** API endpoints
+- ❌ **لا** SignalR أو WebSockets
+
+## 9. Pre-Execution Gate Additions
+
+بالإضافة إلى `TeraPreExecutionGate.md`، تأكد من:
+
+- [ ] ملف `.csproj` لا يحتوي PackageReferences غير ضرورية
+- [ ] WPF لا يستخدم `App.xaml` لتوجيه غير آمن
+- [ ] NuGet packages كلها متوافقة مع .NET 8
+- [ ] ConnectionString لـ SQLite لا تحتوي معلومات حساسة
+- [ ] مجلد `Migrations/` موجود بعد أول مهمة DB
+- [ ] دعم RTL ضمن XAML (FlowDirection)
+
+## 10. Acceptance Criteria Patterns
+
+يقبل الـ Handback إذا:
+
+- ✅ التطبيق يشتغل بـ `dotnet run` بدون أخطاء
+- ✅ الشاشات تعرض بالعربية (RTL)
+- ✅ SQLite يعمل (قراءة/كتابة/تصدير)
+- ✅ الطباعة تنتج وثيقة A4 صالحة
+- ✅ الـ PDF يُفتح بدون أخطاء
+- ✅ Outlook Integration تعمل إذا Outlook مثبت، وإلا Fallback إلى PDF
+- ✅ البحث والتصفية يعملان في الجداول
+- ✅ التطبيق لا يتعطل عند إدخال بيانات ناقصة
+
+---
+
+**إعداد:** TeraAgent (مسودة)
+**تاريخ:** 2026-07-13
+**الحالة:** ✅ **معتمد من Majed** — 2026-07-13

package/core/tera-system/profiles/effect-bun-opencode.md

@@ -0,0 +1,109 @@
+# Technology Profile: effect-bun-opencode
+
+> **⚠️ مُلغى (Deprecated) منذ 2026-08-15:** هذا البروفايل كان مرتبطاً بمشروع TeraOpenCode/TeraAi التجريبي الذي أُزيل من المستودع. يحتفظ بمعرفة الـ stack (Effect TS + Bun) كمرجع للاستخدام المستقبلي المحتمل — لا يُفعَّل حالياً.
+
+## 1. Profile Identity
+
+- Profile ID: `effect-bun-opencode`
+- Language: TypeScript
+- Framework: Effect TS / OpenCode-style monorepo architecture
+- Database: Not applicable for current task
+- ORM: Not applicable
+- Package Manager / CLI: Bun
+- Default Project Type: TypeScript monorepo engine / CLI / core package work
+- Status: **Deprecated** — المشروع المصدر (TeraOpenCode/TeraAi) أُزيل من المستودع 2026-08-15
+
+## 2. Applicability
+
+Use this profile for TypeScript monorepo engine work (Effect TS + Bun + OpenCode-style architecture). ملاحظة: كان مرتبطاً بمشروع TeraOpenCode التجريبي (clients/TeraAi) الذي أُزيل من المستودع 2026-08-15 — لا يوجد مسار فعلي حالياً.
+
+This profile is intended for the current Phase 4 Context API prototype and similar engine-integration tasks.
+
+## 3. Default Execution Order
+
+1. Read the approved protocol/design documents.
+2. Identify the smallest package-level integration point.
+3. Add or modify schemas/types before runtime behavior when needed.
+4. Implement the minimal runtime path.
+5. Register only the minimal exported surface required by the task.
+6. Run package-local checks only, not repo-root tests.
+7. Report changed files, commands, and verification results.
+
+## 4. First Task Rule
+
+The safest first implementation task is a narrow, non-state-changing prototype that validates protocol shape and message handling without adding Task API, Approval API, Event Stream, Config Bridge, or persistent platform state.
+
+For Phase 4.2, the first allowed implementation is: Handshake + ContextRequest + ContextResponse over JSON Lines stdio, scoped to a prototype entrypoint or gateway module.
+
+## 5. Scaffold Rules
+
+- Do not scaffold a new application.
+- Do not add a new framework.
+- Do not add runtime dependencies unless explicitly required and approved.
+- Prefer existing repository patterns for TypeScript modules, exports, schemas, and service registration.
+- Keep files close to the relevant package boundary.
+
+## 6. ORM / Database Rules
+
+Not applicable for the current engine gateway prototype.
+
+Forbidden by default:
+- Database schema changes
+- Migrations
+- ORM configuration
+- Persistent task/session storage
+
+## 7. CLI Side Effects
+
+Allowed commands must be package-local and explicitly listed in the task file.
+
+Common allowed verification commands:
+- `bun run typecheck` from the relevant package directory when available
+- package-local tests if a test script exists and is scoped
+
+Forbidden by default unless separately approved:
+- repo-wide destructive cleanup
+- dependency installation
+- publishing
+- migration or database commands
+- force push / amend / reset
+- starting long-running servers unless the task explicitly requires it
+
+## 8. Forbidden Defaults
+
+Do not create by default:
+- Task API
+- Approval API
+- Event Stream
+- REST API
+- Config Bridge
+- persistent platform state
+- new agent files
+- broad refactors
+- unrelated renames
+- new dependencies
+
+## 9. Pre-Execution Gate Additions
+
+Before delegation:
+
+- Confirm `TERA_GATEWAY_PROTOCOL_SPEC.md` version and status.
+- Confirm the task is limited to Context API prototype.
+- Confirm stdout/stderr rules are included in acceptance criteria.
+- Confirm no `.tera-workspace/` writes are allowed.
+- Confirm `read_tera_workspace` remains fallback only and is not removed.
+- Confirm allowed write targets are package-specific.
+- Confirm no Task State changes are introduced.
+
+## 10. Acceptance Criteria Patterns
+
+For the Phase 4.2 Context API prototype:
+
+1. Handshake accepts compatible `contract_version` and rejects incompatible versions.
+2. ContextRequest is accepted only after successful handshake.
+3. ContextResponse uses the same correlation `id` as ContextRequest.
+4. stdout emits protocol JSON Lines only.
+5. stderr is used for diagnostics/logs only.
+6. Oversized context is rejected according to `MESSAGE_TOO_LARGE` behavior.
+7. No Task API, Approval API, Event Stream, Config Bridge, or platform state mutation is added.
+8. Typecheck or scoped verification passes.