jorgex-stack 1.0.15 → 1.0.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "jorgex-stack",
3
- "version": "1.0.15",
3
+ "version": "1.0.16",
4
4
  "description": "Harness multi-agente portable: instala la config JorgeX (agentes, skills, hooks, Engram, MCPs) en Claude Code, Codex CLI y OpenCode",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -0,0 +1,12 @@
1
+ <!-- jorgex:programmatic-mode -->
2
+ ## PROGRAMMATIC MODE
3
+
4
+ - This installation is meant for external orchestrators, CI, or scripts.
5
+ - Answer in English.
6
+ - Keep intermediate output compact and direct.
7
+ - Make the final handoff strict and machine-friendly.
8
+ - When a final response is required, emit one strict JSON object only.
9
+ - Any delegation must live in the JSON `delegations[]` array as a string in the form `agent: work — paths — inputs`; do not emit Markdown delegation lines outside JSON.
10
+ - Required keys: `status`, `decision`, `confidence`, `summary`, `risks`, `next_steps`, `delegations`.
11
+ - `status` is one of `done`, `partial`, `blocked`.
12
+ - `risks`, `next_steps`, and `delegations` are arrays of strings.
@@ -0,0 +1,8 @@
1
+ <!-- jorgex:programmatic-mode -->
2
+ ## Programmatic Mode
3
+
4
+ - Use English only.
5
+ - Keep replies compact and direct.
6
+ - Delegations must be strings in the final JSON `delegations[]` array, using `agent: work — paths — inputs`.
7
+ - Do not emit Markdown delegation lines.
8
+ - Use the strict final JSON handoff.
@@ -0,0 +1,43 @@
1
+ {
2
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
3
+ "title": "Programmatic final output",
4
+ "type": "object",
5
+ "additionalProperties": false,
6
+ "required": ["status", "decision", "confidence", "summary", "risks", "next_steps", "delegations"],
7
+ "properties": {
8
+ "status": {
9
+ "type": "string",
10
+ "enum": ["done", "partial", "blocked"]
11
+ },
12
+ "decision": {
13
+ "type": "string"
14
+ },
15
+ "confidence": {
16
+ "type": "number",
17
+ "minimum": 0,
18
+ "maximum": 1
19
+ },
20
+ "summary": {
21
+ "type": "string"
22
+ },
23
+ "risks": {
24
+ "type": "array",
25
+ "items": {
26
+ "type": "string"
27
+ }
28
+ },
29
+ "next_steps": {
30
+ "type": "array",
31
+ "items": {
32
+ "type": "string"
33
+ }
34
+ },
35
+ "delegations": {
36
+ "type": "array",
37
+ "items": {
38
+ "type": "string",
39
+ "pattern": "^[A-Za-z0-9][^:\\n]*: [^—\\n]+ — [^—\\n]+ — [^—\\n]+$"
40
+ }
41
+ }
42
+ }
43
+ }
@@ -0,0 +1,15 @@
1
+ <!-- jorgex:programmatic-mode -->
2
+ ## Programmatic Mode
3
+
4
+ - Use English only.
5
+ - Keep reasoning compact and direct.
6
+ - The final assistant response must be exactly one strict JSON object.
7
+ - Do not wrap the final JSON in Markdown fences or prose.
8
+ - Process the final JSON object's `delegations[]` array; each item must be a string in the form `agent: work — paths — inputs`. Ignore Markdown delegation lines outside JSON.
9
+ - Required keys: `status`, `decision`, `confidence`, `summary`, `risks`, `next_steps`, `delegations`.
10
+ - `status` is one of `done`, `partial`, `blocked` and `decision` is a short string.
11
+ - `confidence` is a number between 0 and 1.
12
+ - `summary` is a short string.
13
+ - `risks`, `next_steps`, and `delegations` are arrays of strings.
14
+
15
+ {{CONCURRENCY_RULE}}
@@ -0,0 +1,12 @@
1
+ <!-- jorgex:programmatic-mode -->
2
+ ## Programmatic Mode
3
+
4
+ - Use English only.
5
+ - Keep replies compact and direct.
6
+ - Avoid long Markdown reports unless the orchestrator asks for them.
7
+ - Return a terse, structured handoff that is easy to parse.
8
+ - Use the strict final JSON handoff.
9
+ - Any delegation must live in the JSON `delegations[]` array as a string in the form `agent: work — paths — inputs`; do not emit Markdown delegation lines outside JSON.
10
+ - Required keys: `status`, `decision`, `confidence`, `summary`, `risks`, `next_steps`, `delegations`.
11
+ - `status` is one of `done`, `partial`, `blocked`.
12
+ - `risks`, `next_steps`, and `delegations` are arrays of strings.