@oh-my-pi/pi-agent-core 17.2.13 → 17.2.15

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,7 +1,7 @@
1
1
  {
2
2
  "type": "module",
3
3
  "name": "@oh-my-pi/pi-agent-core",
4
- "version": "17.2.13",
4
+ "version": "17.2.15",
5
5
  "description": "General-purpose agent with transport abstraction, state management, and attachment support",
6
6
  "homepage": "https://omp.sh",
7
7
  "author": "Can Boluk",
@@ -35,16 +35,16 @@
35
35
  "fmt": "biome format --write ."
36
36
  },
37
37
  "dependencies": {
38
- "@oh-my-pi/pi-ai": "17.2.13",
39
- "@oh-my-pi/pi-catalog": "17.2.13",
40
- "@oh-my-pi/pi-natives": "17.2.13",
41
- "@oh-my-pi/pi-utils": "17.2.13",
42
- "@oh-my-pi/pi-wire": "17.2.13",
43
- "@oh-my-pi/snapcompact": "17.2.13",
38
+ "@oh-my-pi/pi-ai": "17.2.15",
39
+ "@oh-my-pi/pi-catalog": "17.2.15",
40
+ "@oh-my-pi/pi-natives": "17.2.15",
41
+ "@oh-my-pi/pi-utils": "17.2.15",
42
+ "@oh-my-pi/pi-wire": "17.2.15",
43
+ "@oh-my-pi/snapcompact": "17.2.15",
44
44
  "@opentelemetry/api": "^1.9.1"
45
45
  },
46
46
  "devDependencies": {
47
- "@oh-my-pi/omptype": "17.2.13",
47
+ "@oh-my-pi/omptype": "17.2.15",
48
48
  "@opentelemetry/context-async-hooks": "^2.9.0",
49
49
  "@opentelemetry/sdk-trace-base": "^2.9.0",
50
50
  "@types/bun": "^1.3.14"
@@ -1,4 +1,4 @@
1
- The following is a summary of a branch that this conversation came back from:
1
+ Branch-return summary:
2
2
 
3
3
  <summary>
4
4
  {{summary}}
@@ -1,2 +1,2 @@
1
- The user explored a different conversation branch before returning here.
2
- Summary of that exploration:
1
+ User explored another conversation branch, then returned here.
2
+ Exploration summary:
@@ -1,9 +1,3 @@
1
- You MUST summarize what was done in this conversation, written like a pull request description.
2
-
3
- Rules:
4
- - MUST be 2-3 sentences max
5
- - MUST describe the changes made, not the process
6
- - NEVER mention running tests, builds, or other validation steps
7
- - NEVER explain what the user asked for
8
- - MUST write in first person (I added…, I fixed…)
9
- - NEVER ask questions
1
+ Summarize conversation changes as a pull request description.
2
+ MUST 2–3 sentences; first person (`I added…`, `I fixed…`); describe changes, not process.
3
+ NEVER mention tests, builds, or other validation steps; explain user request; ask questions.
@@ -1,4 +1,5 @@
1
- Another language model started to solve this problem and produced a summary of its thinking process. You also have access to the state of the tools that model used. You MUST build on the work already done and NEVER duplicate it. Here is that summary:
1
+ Prior model work/tool state available.
2
+ MUST build on prior work; NEVER duplicate prior work.
2
3
 
3
4
  <summary>
4
5
  {{summary}}
@@ -1,6 +1,6 @@
1
- This is the PREFIX of a turn that was too large to keep. The SUFFIX (recent work) is retained.
1
+ Turn prefix too large; recent-work suffix retained.
2
2
 
3
- You MUST summarize the prefix to provide context for the retained suffix:
3
+ MUST summarize prefix for retained suffix:
4
4
 
5
5
  ## Original Request
6
6
 
@@ -12,6 +12,6 @@ You MUST summarize the prefix to provide context for the retained suffix:
12
12
  ## Context for Suffix
13
13
  - [Information needed to understand the retained recent work]
14
14
 
15
- You MUST output only the structured summary. You NEVER include extra text.
15
+ MUST output only the structured summary; NEVER extra text.
16
16
 
17
- You MUST be concise. You MUST preserve exact file paths, function names, error messages, and relevant tool outputs or command results if they appear. You MUST focus on what's needed to understand the kept suffix.
17
+ MUST concise. MUST preserve exact file paths, function names, error messages, relevant tool outputs, and command results if present. MUST focus on information needed to understand the retained suffix.
@@ -1,15 +1,18 @@
1
- You MUST incorporate the new messages above into the existing handoff summary in <previous-summary> tags, used by another LLM to resume the task.
2
- RULES:
3
- - MUST preserve all information from the previous summary
4
- - MUST add new progress, decisions, and context from new messages
5
- - MUST update Progress: move items from "In Progress" to "Done" when completed
6
- - MUST update "Next Steps" based on what was accomplished
7
- - MUST preserve exact file paths, function names, and error messages
8
- - You MAY remove anything no longer relevant
9
-
10
- IMPORTANT: If the new messages end with an unanswered question or request to the user, you MUST add it to Critical Context (replacing any previous pending question if answered).
11
-
12
- You MUST use this format (omit sections if not applicable):
1
+ Update existing handoff summary in <previous-summary> tags from new messages above for another LLM to resume.
2
+
3
+ MUST:
4
+ - preserve all previous-summary information; add new progress, decisions, context.
5
+ - Progress: move completed "In Progress" items to "Done".
6
+ - update "Next Steps" for completed work.
7
+ - preserve exact file paths, function names, error messages.
8
+ - MAY remove irrelevant content.
9
+ - If new messages end with an unanswered user question/request: add it to Critical Context; replace any previous pending question if answered.
10
+ - output only the structured summary; NEVER extra text.
11
+ - keep sections concise.
12
+ - preserve relevant tool outputs/command results.
13
+ - include mentioned repository state changes (branch, uncommitted changes).
14
+
15
+ Format (omit inapplicable sections):
13
16
 
14
17
  ## Goal
15
18
  [Preserve existing goals; add new ones if task expanded]
@@ -39,7 +42,3 @@ You MUST use this format (omit sections if not applicable):
39
42
 
40
43
  ## Additional Notes
41
44
  [Other important info not fitting above]
42
-
43
- You MUST output only the structured summary; you NEVER include extra text.
44
-
45
- Sections MUST be kept concise. You MUST preserve relevant tool outputs/command results. You MUST include repository state changes (branch, uncommitted changes) if mentioned.
@@ -1 +1 @@
1
- Output exceeded the available model context and was truncated
1
+ Output: exceeded available model context truncated.
@@ -1,3 +1,3 @@
1
- Summarize conversations between users and AI coding assistants. Produce structured summaries in the exact specified format.
1
+ Summarize user–AI coding-assistant conversations in the exact specified structured format.
2
2
 
3
- NEVER continue the conversation. NEVER respond to questions in it. Output ONLY the structured summary.
3
+ NEVER continue the conversation or answer its questions. Output ONLY the structured summary.