@tera-system/core 0.2.15 → 0.2.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/MANIFEST.json +5 -5
- package/README.md +3 -3
- package/RELEASES.md +318 -308
- package/agents/application-blueprint.md +4 -4
- package/agents/domain-expert-agent.md +3 -3
- package/agents/domain-research-agent.md +4 -4
- package/agents/engineering-agent-typescript.md +1 -1
- package/agents/production-erp-expert.md +2 -2
- package/agents/red-team-agent.md +1 -1
- package/agents/tera-client-engagement.md +1 -1
- package/agents/tera-system-evolution.md +2 -1
- package/agents/tera.md +1 -0
- package/core/tera-system/AGENT_ACTIVATION_MATRIX.md +275 -277
- package/core/tera-system/AGENT_DEPENDENCY_MAP.md +2 -2
- package/core/tera-system/AGENT_PERMISSION_MODEL.md +39 -26
- package/core/tera-system/TERA_DISTRIBUTION_POLICY.md +2 -2
- package/core/tera-system/TERA_PROJECT_DECISION.md +14 -12
- package/core/tera-system/TOOLING_AND_MCP_POLICY.md +1 -1
- package/core/tera-system/TeraCapabilityMap.md +327 -0
- package/core/tera-system/TeraHelperAgents.md +13 -10
- package/core/tera-system/TeraPolicyMap.md +2 -1
- package/core/tera-system/TeraPreExecutionGate.md +1 -1
- package/core/tera-system/TeraPreparationDocumentationGovernance.md +1 -1
- package/core/tera-system/TeraSubAgents.md +312 -868
- package/core/tera-system/TeraTokenPolicy.md +1 -1
- package/core/tera-system/design-system/DESIGN_SOURCE_PROTOCOL.md +2 -2
- package/core/tera-system/design-system/FIGMA_INTEGRATION.md +3 -3
- package/core/tera-system/design-system/UI_ACCEPTANCE_GATE.md +1 -1
- package/core/tera-system/engineering-governance/ENGINEERING_AGENT_RESPONSIBILITIES.md +4 -2
- package/core/tera-system/engineering-governance/ENGINEERING_REVIEW_CHECKLIST.md +1 -1
- package/core/tera-system/engineering-governance/QUALITY_GATE_THRESHOLDS.md +1 -1
- package/core/tera-system/profiles/PROFILES_INDEX.md +2 -0
- package/core/tera-system/runtime/TERA_RUNTIME_CHECKLISTS.md +3 -3
- package/core/tera-system/runtime/TERA_RUNTIME_PROTOCOLS_CLIENT.md +2 -2
- package/core/tera-system/runtime/TERA_RUNTIME_PROTOCOLS_CORE.md +5 -5
- package/core/tera-system/runtime/TERA_SOLUTION_PREPARATION_PROTOCOL.md +1 -1
- package/core/tera-system/runtime/TERA_SOLUTION_PREPARATION_TEMPLATES.md +4 -4
- package/package.json +1 -1
|
@@ -68,7 +68,7 @@ TERA_ACTIVE_CONTEXT.md (if exists) + Task Context + الملفات المحدد
|
|
|
68
68
|
|---|---|---|
|
|
69
69
|
| **Light** | مهام بسيطة، قراءة ملف واحد، كتابة محدودة | تنسيق، توثيق، مهام روتينية |
|
|
70
70
|
| **Medium** | تحليل وتصميم، قراءة 2-4 ملفات | معظم مهام التحضير والتحليل |
|
|
71
|
-
| **Strong** | مراجعة شاملة، أمان، قرارات معمارية | SecurityAgent، مراجعات الجودة، مراجعة الامتثال |
|
|
71
|
+
| **Strong** | مراجعة شاملة، أمان، قرارات معمارية | SecurityAgent (الدرع)، مراجعات الجودة، مراجعة الامتثال |
|
|
72
72
|
|
|
73
73
|
**قاعدة:** لا يُسمح لأي عميل فرعي باستخدام Strong Token Budget إلا بتفويض صريح من Tera.
|
|
74
74
|
|
|
@@ -29,8 +29,8 @@ No UI Implementation without project-preparation/28_UI_UX_GUIDELINES.md when vis
|
|
|
29
29
|
| Phase | Design Responsibility |
|
|
30
30
|
|---|---|
|
|
31
31
|
| Phase 1 | Collect preferences, screenshots, brand colors, references, RTL/LTR needs — owned by مُهندس (SCP-2026-07-28-118) |
|
|
32
|
-
| Phase 3 | Decide whether `28_UI_UX_GUIDELINES.md`, design-source files, or
|
|
33
|
-
| Phase 4 | Generate/activate
|
|
32
|
+
| Phase 3 | Decide whether `28_UI_UX_GUIDELINES.md`, design-source files, or ui-designer are required — owned by مُهندس |
|
|
33
|
+
| Phase 4 | Generate/activate ui-designer only when design governance is needed now — owned by مُهندس |
|
|
34
34
|
| Phase 5 | Block frontend TASK-COD generation until Design Source Decision exists |
|
|
35
35
|
| Phase 6 | EngineeringAgent follows `28_UI_UX_GUIDELINES.md` and UI Acceptance Gate |
|
|
36
36
|
|
|
@@ -32,7 +32,7 @@ Client provides Figma file / link / structured exports
|
|
|
32
32
|
↓
|
|
33
33
|
Tera records Design Source Mode = FIGMA_DESIGN_FILE
|
|
34
34
|
↓
|
|
35
|
-
|
|
35
|
+
ui-designer analyzes the Figma source:
|
|
36
36
|
- Extracts colors, typography, spacing
|
|
37
37
|
- Maps frames/pages to project screens
|
|
38
38
|
- Documents component variants and states
|
|
@@ -118,9 +118,9 @@ FIGMA_DESIGN_FILE
|
|
|
118
118
|
- بعد التحليل أعطني ملخصًا بما تم اعتماده، وما هي Design Gaps قبل بدء تنفيذ الواجهة.
|
|
119
119
|
```
|
|
120
120
|
|
|
121
|
-
##
|
|
121
|
+
## ui-designer Responsibilities
|
|
122
122
|
|
|
123
|
-
When `FIGMA_DESIGN_FILE` is active,
|
|
123
|
+
When `FIGMA_DESIGN_FILE` is active, ui-designer must:
|
|
124
124
|
|
|
125
125
|
1. Reference the Figma file in `project-preparation/design-source/`.
|
|
126
126
|
2. Extract all available design tokens (colors, typography, spacing).
|
|
@@ -31,7 +31,9 @@ Tera must:
|
|
|
31
31
|
|
|
32
32
|
---
|
|
33
33
|
|
|
34
|
-
## 3.
|
|
34
|
+
## 3. Solution Architecture (Preparation Role — مملوكة لـ application-blueprint)
|
|
35
|
+
|
|
36
|
+
> **SCP-2026-09-04-001:** ليست عميلاً ثابتاً — تُنفَّذ ضمن مسؤولية `application-blueprint` (مهندس الحل) أو عبر `tera-software-designer` لمهام معمارية محددة.
|
|
35
37
|
|
|
36
38
|
Must focus on:
|
|
37
39
|
|
|
@@ -142,7 +144,7 @@ QA must focus on:
|
|
|
142
144
|
- workflow/status transition correctness;
|
|
143
145
|
- whether missing tests create acceptance risk.
|
|
144
146
|
|
|
145
|
-
QA does not replace SecurityAgent for specialized security review.
|
|
147
|
+
QA does not replace SecurityAgent (الدرع) for specialized security review.
|
|
146
148
|
|
|
147
149
|
---
|
|
148
150
|
|
|
@@ -63,7 +63,7 @@ Review only the relevant areas. Do not expand a small review into a full audit u
|
|
|
63
63
|
- [ ] Backend/API/service validation exists for important inputs.
|
|
64
64
|
- [ ] Error format and messages follow project conventions.
|
|
65
65
|
- [ ] Permissions are enforced beyond UI hiding when security matters.
|
|
66
|
-
- [ ] Security-sensitive changes are escalated to SecurityAgent or Tera as required.
|
|
66
|
+
- [ ] Security-sensitive changes are escalated to SecurityAgent (الدرع) or Tera as required.
|
|
67
67
|
|
|
68
68
|
---
|
|
69
69
|
|
|
@@ -32,7 +32,7 @@ Severity depends on impact, context, confidence, evidence quality, and whether t
|
|
|
32
32
|
| Duplication percentage | Static analyzer report only; otherwise call it suspected duplication |
|
|
33
33
|
| Coverage | QA report or coverage artifact only |
|
|
34
34
|
| Flaky tests | QA/CI history only |
|
|
35
|
-
| Vulnerable dependency | SecurityAgent report, dependency scanner, or authoritative advisory |
|
|
35
|
+
| Vulnerable dependency | SecurityAgent (الدرع) report, dependency scanner, or authoritative advisory |
|
|
36
36
|
| Dependency freshness | Not a finding by itself; require vulnerability, EOL, incompatibility, or unused dependency |
|
|
37
37
|
| Technical Debt Ratio | Tool report only |
|
|
38
38
|
| CBO/coupling metric | Analyzer or explicit dependency evidence |
|
|
@@ -47,6 +47,8 @@ If the stack is still unclear, do not activate a final profile yet.
|
|
|
47
47
|
| `dotnet-wpf-sqlite` | C# (.NET 8) + WPF + CommunityToolkit.Mvvm + SQLite | ✅ **Approved** | WPF Desktop — معتمد من Majed (مشروع تجريبي سابق) |
|
|
48
48
|
| `phaser-react-node` | Phaser 3 + React + Node.js + TypeScript + PostgreSQL + Zustand + TanStack Query + Zod + Vite + Vitest | ✅ **Approved** | Web Game 2D — معتمد من Majed (2026-07-29) |
|
|
49
49
|
| `react-pwa` | React 18 + Vite + TypeScript + Tailwind CSS (RTL) + Zustand + idb (IndexedDB) + Fuse.js + vite-plugin-pwa | ✅ **Approved — Active** | PWA محلي عربي (Offline Standalone) — فعّل Majed (2026-08-01, PREP-D-016) |
|
|
50
|
+
| `flutter-mobile` | Flutter + Dart | Available | موبايل — يُحمَّل عند تصنيف المنتج موبايل (MVP_DEFINITION_PROTOCOL + MOBILE_UI_UX_STANDARDS) — (SCP-2026-09-04-003) |
|
|
51
|
+
| `dotnet-razorpages-adonet` | .NET Razor Pages + ADO.NET | Available | تطبيقات أعمال داخلية + تكامل بيانات — (SCP-2026-09-04-003) |
|
|
50
52
|
|
|
51
53
|
## Placeholder Candidates
|
|
52
54
|
|
|
@@ -36,14 +36,14 @@ When the user provides a project idea and technical information:
|
|
|
36
36
|
- Determine creation order and dependencies.
|
|
37
37
|
- Assign each file to the appropriate sub-agent.
|
|
38
38
|
- Identify user approval points.
|
|
39
|
-
- If UI exists, decide whether `28_UI_UX_GUIDELINES.md`, `project-preparation/design-source/`, or `
|
|
39
|
+
- If UI exists, decide whether `28_UI_UX_GUIDELINES.md`, `project-preparation/design-source/`, or `ui-designer` are required.
|
|
40
40
|
4. **No file creation. No agent generation.**
|
|
41
41
|
5. Present the plan for user approval.
|
|
42
42
|
|
|
43
43
|
### Phase 4: Sub-Agent Generation & Preparation Delegation
|
|
44
44
|
1. Verify `PREPARATION_PLAN.md` is approved. If not → do not start Phase 4.
|
|
45
45
|
2. Determine which preparation agents are needed now from the plan.
|
|
46
|
-
- Include `
|
|
46
|
+
- Include `ui-designer` when visual design tokens/component rules must be prepared now.
|
|
47
47
|
3. For each agent, check status: **Use Existing** / **Specialize** / **Generate**.
|
|
48
48
|
4. If generating: create draft in `generated-agents/opencode/` using `AGENT_GENERATION_TEMPLATE.md`.
|
|
49
49
|
5. For each agent, set:
|
|
@@ -340,7 +340,7 @@ Decide security sensitivity before delegation.
|
|
|
340
340
|
|
|
341
341
|
| Level | Meaning | Default Action |
|
|
342
342
|
|---|---|---|
|
|
343
|
-
| Low | UI-only, text/layout, no Auth/API/Server Actions/Data Mutations | `SecurityAgent` not needed by default; only required if Tera identifies a real security gap |
|
|
343
|
+
| Low | UI-only, text/layout, no Auth/API/Server Actions/Data Mutations | `SecurityAgent (الدرع)` not needed by default; only required if Tera identifies a real security gap |
|
|
344
344
|
| Medium | Standard Server Actions, CRUD with requireAdmin, Data Mutations within existing permissions | Tera explicitly decides: required / optional but skipped / not needed |
|
|
345
345
|
| High | Auth flow, JWT, cookies, sessions, passwords, secrets, config, middleware, permissions model, public API endpoints | `SecurityAgent` is default; cannot skip without strong documented reason |
|
|
346
346
|
|
|
@@ -211,7 +211,7 @@ Exit criteria before Build Mode:
|
|
|
211
211
|
|
|
212
212
|
## 15. Handoff Readiness Gate
|
|
213
213
|
|
|
214
|
-
Purpose: Determine when a phase or task group is ready for using `
|
|
214
|
+
Purpose: Determine when a phase or task group is ready for using `Preparation Role: Documentation & Handover (يملكه tera.md)`.
|
|
215
215
|
|
|
216
216
|
Important: `Handoff Readiness Gate` is not required for normal internal task handbacks. It is only for evaluating phase readiness, Release readiness, or formal documentation/delivery packages.
|
|
217
217
|
|
|
@@ -230,7 +230,7 @@ Important: `Handoff Readiness Gate` is not required for normal internal task han
|
|
|
230
230
|
3. No blocking Issues remain open.
|
|
231
231
|
|
|
232
232
|
If any Must Pass item fails:
|
|
233
|
-
- Do not run `
|
|
233
|
+
- Do not run `Preparation Role: Documentation & Handover (يملكه tera.md)` for final delivery.
|
|
234
234
|
- May only run it for an internal draft if Tera decides so and documents the reason.
|
|
235
235
|
|
|
236
236
|
### Should Pass
|
|
@@ -265,7 +265,7 @@ After execution:
|
|
|
265
265
|
2. Record the handback event in `project-control/PROJECT_ACTIVITY_LOG.md`.
|
|
266
266
|
3. Run Post-Execution Review Gate against actual files, packages, commands, and side effects.
|
|
267
267
|
4. Check for secrets in outputs. If a real secret appears anywhere, the gate cannot pass.
|
|
268
|
-
5. Decide whether independent review is needed from `SecurityAgent`, `qa-agent`, or `ProjectControlAgent`.
|
|
268
|
+
5. Decide whether independent review is needed from `SecurityAgent (الدرع)`, `qa-agent`, or `ProjectControlAgent`.
|
|
269
269
|
6. Decide final status: Accept, Needs Fix, Block, Defer, or Close.
|
|
270
270
|
7. Update task status, registry, activity log, project state, issues, and decisions as needed.
|
|
271
271
|
8. Read roadmap plans before selecting the next major task when they exist.
|
|
@@ -386,7 +386,7 @@ Phase 7 output sizing:
|
|
|
386
386
|
Allowed helper agents:
|
|
387
387
|
|
|
388
388
|
- `qa-agent`: Final QA / Smoke / Regression / Acceptance.
|
|
389
|
-
- `
|
|
389
|
+
- `Preparation Role: Documentation & Handover (يملكه tera.md)`: Release Notes / Handover Package / Closure Report.
|
|
390
390
|
- `DevOpsAgent`: Deployment Readiness when needed.
|
|
391
391
|
- `SecurityAgent`: Security closure when needed.
|
|
392
392
|
- Tera: final closure decision.
|
|
@@ -412,10 +412,10 @@ Phase 7 finds blocker
|
|
|
412
412
|
| Updates project-control records, closes/creates Issues, adds Decisions, modifies PROJECT_STATE.md / TERA_ACTIVE_CONTEXT.md, or involves multiple agents | `ProjectControlAgent` |
|
|
413
413
|
| Touches Auth, JWT, Cookies, Middleware, Proxy, API Routes, Server Actions, Permissions, Role checks, Data Mutations, Secrets, or Config | Determine Security Sensitivity Level before delegation |
|
|
414
414
|
| Contains UI, Workflow, main-screen behavior, or important acceptance criteria | Run `qa-agent` |
|
|
415
|
-
| Creates or changes UI visual styling, design tokens, layout rules, or component styles | Use `
|
|
415
|
+
| Creates or changes UI visual styling, design tokens, layout rules, or component styles | Use `ui-designer` during preparation/planning when rules are not already clear; require `UI_ACCEPTANCE_GATE` after implementation |
|
|
416
416
|
| Comes after 3-5 tasks, phase end, before release, or with quality drift / debt / duplication signals | Run `QualityReviewCoordinatorAgent` |
|
|
417
417
|
| Phase closes, major batch ends, MVP acceptance, or roadmap drift suspected | Run `PlanComplianceReviewAgent` |
|
|
418
|
-
| Phase is stable and needs internal handoff / release / user / run documentation | Run Handoff Readiness Gate, then run `
|
|
418
|
+
| Phase is stable and needs internal handoff / release / user / run documentation | Run Handoff Readiness Gate, then run `Preparation Role: Documentation & Handover (يملكه tera.md)` |
|
|
419
419
|
|
|
420
420
|
Rules:
|
|
421
421
|
|
|
@@ -467,7 +467,7 @@ Helper agent authority limits:
|
|
|
467
467
|
- `QualityReviewCoordinatorAgent`: coordinates review scope and consolidates findings. Does not decide task/issue/deferred status. Does not write code or change designs.
|
|
468
468
|
- `PlanComplianceReviewAgent`: reviews roadmap compliance. Does not open tasks/issues/decisions. Does not change status.
|
|
469
469
|
- `qa-agent`: task/screen/workflow acceptance checks. Does not replace periodic quality review.
|
|
470
|
-
- `
|
|
470
|
+
- `Preparation Role: Documentation & Handover (يملكه tera.md)`: prepares documentation only after Handoff Readiness Gate. Does not decide final acceptance.
|
|
471
471
|
|
|
472
472
|
### 5.1 Design Governance Runtime Protocol
|
|
473
473
|
|
|
@@ -209,7 +209,7 @@ Majed → Tera
|
|
|
209
209
|
| الفئة | العملاء | الصلاحية |
|
|
210
210
|
|-------|---------|----------|
|
|
211
211
|
| بحث وتحليل | DomainResearchAgent, DomainExpertAgent, ProductionERPExpert | مسموح — مخرجات `[Research Hint]` |
|
|
212
|
-
| تحضير |
|
|
212
|
+
| تحضير | **Preparation Roles** (RequirementsScope, BusinessWorkflow, DataDesign, UIUXStructure, SolutionArchitecture) — مملوكة لـ `application-blueprint` نفسه + helper agents | مسموح عبر `TASK-PREP-*` |
|
|
213
213
|
| تخطيط اختبارات | qa-agent Planning Mode | مسموح — لا Execution Mode |
|
|
214
214
|
| تصميم بصري | ui-designer Preparation Design Mode | مسموح — وثائق فقط، ممنوع كود |
|
|
215
215
|
| Coding Agents | engineering-agent, engineering-agent-dotnet | ❌ ممنوع |
|
|
@@ -66,7 +66,7 @@
|
|
|
66
66
|
## 8. Required Preparation Files
|
|
67
67
|
| الملف | التصنيف | العميل المتوقع |
|
|
68
68
|
|---|---|---|
|
|
69
|
-
| 01_PROJECT_BRIEF.md | Required |
|
|
69
|
+
| 01_PROJECT_BRIEF.md | Required | application-blueprint (Preparation Role) |
|
|
70
70
|
| ... | ... | ... |
|
|
71
71
|
|
|
72
72
|
## 9. Suggested Sub-Agents
|
|
@@ -113,8 +113,8 @@ Reference: `TERA_PROJECT_DECISION.md`
|
|
|
113
113
|
## 2. Required Preparation Files
|
|
114
114
|
| File | Required | Reason | Owner Agent | Order |
|
|
115
115
|
|---|---|---|---|---|
|
|
116
|
-
| 01_PROJECT_BRIEF.md | Required | Core understanding |
|
|
117
|
-
| 02_SCOPE_AND_BOUNDARIES.md | Required | Scope discipline |
|
|
116
|
+
| 01_PROJECT_BRIEF.md | Required | Core understanding | application-blueprint (Preparation Role) | 1 |
|
|
117
|
+
| 02_SCOPE_AND_BOUNDARIES.md | Required | Scope discipline | application-blueprint (Preparation Role) | 2 |
|
|
118
118
|
| ... | ... | ... | ... | ... |
|
|
119
119
|
|
|
120
120
|
Classification Key:
|
|
@@ -173,7 +173,7 @@ Reference: `PREPARATION_PLAN.md`
|
|
|
173
173
|
## 2. Agents Needed Now
|
|
174
174
|
| Agent | Reason | Status | Assigned Files |
|
|
175
175
|
|---|---|---|---|
|
|
176
|
-
|
|
|
176
|
+
| application-blueprint (Preparation Role) | Core scope | Generate / Existing / Specialize | 01, 02, 03, 04 |
|
|
177
177
|
|
|
178
178
|
## 3. Agents Not Needed Now
|
|
179
179
|
| Agent | Reason | Defer Until |
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tera-system/core",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.16",
|
|
4
4
|
"description": "Tera System OpenCode Plugin ط£آ¢أ¢â€ڑآ¬أ¢â‚¬â€Œ governance core, 20 agents, 11 commands, distribution tools (personal edition)",
|
|
5
5
|
"license": "SEE LICENSE IN LICENSE.md",
|
|
6
6
|
"type": "module",
|