@link-assistant/hive-mind 1.34.7 → 1.34.8

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @link-assistant/hive-mind
 
+## 1.34.8
+
+### Patch Changes
+
+- c95a472: Add test timeout guidelines to system prompt and case study documentation
+  - Added guidelines for setting reasonable test timeouts in CI/CD pipelines
+  - Created comprehensive case study in docs/case-studies/issue-1197/
+  - Recommendations include: 5-30s for unit tests, 30-60s for E2E tests
+  - Guidelines for job-level workflow timeouts and fail-fast patterns
+
 ## 1.34.7
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@link-assistant/hive-mind",
-  "version": "1.34.7",
+  "version": "1.34.8",
   "description": "AI-powered issue solver and hive mind for collaborative problem solving",
   "main": "src/hive.mjs",
   "type": "module",

package/src/agent.prompts.lib.mjs

@@ -172,6 +172,8 @@ Solution development and testing.
       write unit tests with mocks for easy and quick start.
    - When you test integrations, use existing framework.
    - When you test solution draft, include automated checks in pr.
+   - When you write or modify tests, consider setting reasonable timeouts at test, suite, and CI job levels so failures surface quickly instead of hanging.
+   - When you see repeated test timeout patterns in CI, investigate the root cause rather than increasing timeouts.
    - When issue is unclear, write comment on issue asking questions.
    - When you encounter any problems that you unable to solve yourself, write a comment to the pull request asking for help.
    - When you need human help, use gh pr comment ${prNumber} --body "your message" to comment on existing PR.

package/src/claude.prompts.lib.mjs

@@ -215,6 +215,8 @@ Solution development and testing.
       write unit tests with mocks for easy and quick start.
    - When you test integrations, use existing framework.
    - When you test solution draft, include automated checks in pr.
+   - When you write or modify tests, consider setting reasonable timeouts at test, suite, and CI job levels so failures surface quickly instead of hanging.
+   - When you see repeated test timeout patterns in CI, investigate the root cause rather than increasing timeouts.
    - When issue is unclear, write comment on issue asking questions.
    - When you encounter any problems that you unable to solve yourself (any human feedback or help), write a comment to the pull request asking for help.
    - When you need human help, use gh pr comment ${prNumber} --body "your message" to comment on existing PR.

package/src/codex.prompts.lib.mjs

@@ -181,6 +181,8 @@ Solution development and testing.
       write unit tests with mocks for easy and quick start.
    - When you test integrations, use existing framework.
    - When you test solution draft, include automated checks in pr.
+   - When you write or modify tests, consider setting reasonable timeouts at test, suite, and CI job levels so failures surface quickly instead of hanging.
+   - When you see repeated test timeout patterns in CI, investigate the root cause rather than increasing timeouts.
    - When issue is unclear, write comment on issue asking questions.
    - When you encounter any problems that you unable to solve yourself (any human feedback or help), write a comment to the pull request asking for help.
    - When you need human help, use gh pr comment ${prNumber} --body "your message" to comment on existing PR.

package/src/opencode.prompts.lib.mjs

@@ -175,6 +175,8 @@ Solution development and testing.
       write unit tests with mocks for easy and quick start.
    - When you test integrations, use existing framework.
    - When you test solution draft, include automated checks in pr.
+   - When you write or modify tests, consider setting reasonable timeouts at test, suite, and CI job levels so failures surface quickly instead of hanging.
+   - When you see repeated test timeout patterns in CI, investigate the root cause rather than increasing timeouts.
    - When issue is unclear, write comment on issue asking questions.
    - When you encounter any problems that you unable to solve yourself, write a comment to the pull request asking for help.
    - When you need human help, use gh pr comment ${prNumber} --body "your message" to comment on existing PR.