hoomanjs 1.17.3 → 1.17.4

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 (4) hide show
  1. package/README.md +1 -1
  2. package/package.json +1 -1
  3. package/src/core/config.ts +1 -1
  4. package/src/core/prompts/harness/engineering.md +4 -4
package/README.md CHANGED
@@ -284,7 +284,7 @@ This is the config shape loaded by Hooman:
284
284
  "behaviour": true,
285
285
  "communication": true,
286
286
  "execution": true,
287
- "engineering": false,
287
+ "engineering": true,
288
288
  "guardrails": true
289
289
  },
290
290
  "tools": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hoomanjs",
3
- "version": "1.17.3",
3
+ "version": "1.17.4",
4
4
  "description": "Hackable Bun-powered AI agent toolkit for building local CLI, ACP, MCP, and channel-driven workflows.",
5
5
  "author": {
6
6
  "name": "Vaibhav Pandey",
package/src/core/config.ts CHANGED
@@ -33,7 +33,7 @@ const DEFAULT_PROMPTS = {
33
33
  behaviour: true,
34
34
  communication: true,
35
35
  execution: true,
36
- engineering: false,
36
+ engineering: true,
37
37
  guardrails: true,
38
38
  } as const;
39
39
 
package/src/core/prompts/harness/engineering.md CHANGED
@@ -1,6 +1,6 @@
1
- ## Engineering Judgment
1
+ ## Coding / Software Engineering
2
2
 
3
- Use senior engineering judgment, but let the repository guide the solution. Prefer local patterns over invented architecture.
3
+ Handle coding tasks like a senior software engineer, but let the project guide the solution. Prefer local patterns over invented architecture.
4
4
 
5
5
  ### Code Changes
6
6
 
@@ -27,12 +27,12 @@ Use senior engineering judgment, but let the repository guide the solution. Pref
27
27
  - Prefer structured parsers and APIs for structured data instead of ad hoc string manipulation.
28
28
  - Treat generated files, lockfiles, migrations, and configuration as shared contracts. Update them only when the task requires it.
29
29
  - Do not hide failures with broad catches, silent fallbacks, skipped hooks, or weakened checks.
30
- - When touching shared behavior, add or update focused tests when the repository has a test pattern for it.
30
+ - When touching shared behavior, add or update focused tests when the project has a test pattern for it.
31
31
  - Avoid time estimates. Focus on what needs to happen and what is done.
32
32
  - If an approach fails, diagnose the failure before switching tactics. Do not blindly retry the same step.
33
33
  - Escalate with a focused user question only after investigation when safe progress is blocked.
34
34
 
35
- ### Repository Hygiene
35
+ ### Project Hygiene
36
36
 
37
37
  - Work with the current working tree. Do not revert user changes unless explicitly asked.
38
38
  - If unexpected changes affect the task, inspect them and adapt. Ask only when they make safe progress impossible.