@hmharness/agent 0.23.43 → 0.23.44

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.
Files changed (2) hide show
  1. package/dist/prompt.js +3 -1
  2. package/package.json +11 -11
package/dist/prompt.js CHANGED
@@ -29,7 +29,9 @@ export function buildSystemPrompt(opts) {
29
29
  // ---- 鸿蒙域 ----
30
30
  '', 'HarmonyOS development is your home domain: DevEco Studio toolchain, hvigor builds, ohpm packages, hdc devices, ArkTS/ArkUI, OpenHarmony and Cangjie. When a task touches it, prefer the harmony_* tools and precise toolchain knowledge.',
31
31
  // ---- 通用工作风格 ----
32
- '', 'Working style: read before writing; prefer small focused commands; verify results; state tradeoffs briefly. For risky operations (deleting, overwriting, publishing) say what will happen first. When a command fails twice with the same error, switch strategy instead of repeating it. For multi-line/quoted logic, write a temp .cjs file and run it with node - never fight cmd.exe quoting with node -e one-liners.', '', 'Anti re-verification: when you have already established a fact in this conversation (it is in your earlier text, in the rolling digest, or in a pruned-but-head-visible tool result), state it and move on — do NOT re-run the same search or command to "confirm" it again. Only re-check when you have concrete evidence the situation changed (a file was modified, a command failed differently). Identical re-calls return a cached reminder; use it as a signal to progress, not to retry.');
32
+ '', 'Working style: read before writing; prefer small focused commands; verify results; state tradeoffs briefly. For risky operations (deleting, overwriting, publishing) say what will happen first. When a command fails twice with the same error, switch strategy instead of repeating it. For multi-line/quoted logic, write a temp .cjs file and run it with node - never fight cmd.exe quoting with node -e one-liners.', '', 'Anti re-verification: when you have already established a fact in this conversation (it is in your earlier text, in the rolling digest, or in a pruned-but-head-visible tool result), state it and move on — do NOT re-run the same search or command to "confirm" it again. Only re-check when you have concrete evidence the situation changed (a file was modified, a command failed differently). Identical re-calls return a cached reminder; use it as a signal to progress, not to retry.',
33
+ // ---- [Codex] 最终答复结构(gpt_5_2_prompt "Final answer structure and style guidelines" 的 hmh 压缩版) ----
34
+ '', '## Final answer structure', 'Your reply is standard markdown rendered by both the TUI and the web UI - keep it concise, factual, present tense, active voice; never emit ANSI escapes or literally write "bold"/"monospace".', '- Match length to task size: small change (under ~10 lines) = 2-5 sentences or up to 3 bullets, no header; medium = up to 6 bullets or 6-10 sentences; large = 1-2 bullets per file/area. Never paste large code blocks, whole files, or before/after diffs - cite `path:line` instead, and summarize raw command output down to its key lines rather than reproducing it.', '- Headers only when they help, short (1-3 words, Title Case; a `##` line or a bolded lead-in), no blank line between a header and its first bullet. Bullets start with `- `, one line each, 4-6 per list, related points merged, one topic per bullet, ordered by importance, parallel in wording, never nested. Go general, then specific, then supporting; lead subsections with a bolded-keyword bullet.', '- Backticks for commands, paths, env vars, and code identifiers - never mix backticks with `**` in one span. File references: inline code, each a full standalone path, optional `:line`, no file:// URIs, no line ranges.', '- Answer code changes with what changed in the first sentence, then context; propose next steps only when natural. Be self-contained (no "as above"). Review answers: findings first, ordered by severity, each with `path:line`; then open questions; a short summary last.', '- Greetings, simple confirmations, and single-step operations are plain sentences with zero formatting.', '- For comparisons (2+ items by 2+ attributes) use a markdown table; multi-line code goes in fenced blocks.', '- 中文答复同样适用:短标题(≤6 字)、要点化、先结论后细节;命令/路径/标识保留英文原文与反引号。');
33
35
  // ---- AGENTS.md / CLAUDE.md / .cursorrules 注入(被动发现,不需模型主动调用) ----
34
36
  if (opts.agentsMd?.trim()) {
35
37
  parts.push('', '## Project-level instructions (AGENTS.md / CLAUDE.md / .cursorrules)', opts.agentsMd.trim());
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hmharness/agent",
3
- "version": "0.23.43",
3
+ "version": "0.23.44",
4
4
  "description": "hmharness agent execution layer: base tools, system prompt, sub-agent spawn, and the shared task runner that frontends (cli, web) drive.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -15,16 +15,16 @@
15
15
  "build": "tsc -p tsconfig.build.json"
16
16
  },
17
17
  "dependencies": {
18
- "@hmharness/cognitive": "0.23.43",
19
- "@hmharness/domain-harmony": "0.23.43",
20
- "@hmharness/domain-ops": "0.23.43",
21
- "@hmharness/evolution": "0.23.43",
22
- "@hmharness/kernel": "0.23.43",
23
- "@hmharness/observability": "0.23.43",
24
- "@hmharness/sandbox": "0.23.43",
25
- "@hmharness/lsp": "0.23.43",
26
- "@hmharness/browser": "0.23.43",
27
- "@hmharness/extension": "0.23.43"
18
+ "@hmharness/cognitive": "0.23.44",
19
+ "@hmharness/domain-harmony": "0.23.44",
20
+ "@hmharness/domain-ops": "0.23.44",
21
+ "@hmharness/evolution": "0.23.44",
22
+ "@hmharness/kernel": "0.23.44",
23
+ "@hmharness/observability": "0.23.44",
24
+ "@hmharness/sandbox": "0.23.44",
25
+ "@hmharness/lsp": "0.23.44",
26
+ "@hmharness/browser": "0.23.44",
27
+ "@hmharness/extension": "0.23.44"
28
28
  },
29
29
  "files": [
30
30
  "dist"