@sireai/optimus 0.1.29 → 0.1.31

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/dist/cli/self-update.js +1 -1
  2. package/dist/config/load-config.js +1 -1
  3. package/package.json +1 -1
  4. package/task-harnesses/bugfix/CONSTRAINTS.md +3 -0
package/dist/cli/self-update.js CHANGED
@@ -115,7 +115,7 @@ function resolveEffectiveSelfUpdateConfig(config) {
115
115
  return config?.selfUpdate ?? {
116
116
  enabled: true,
117
117
  mode: "prompt",
118
- checkIntervalHours: 24,
118
+ checkIntervalHours: 12,
119
119
  startupCommands: ["start", "submit"]
120
120
  };
121
121
  }
package/dist/config/load-config.js CHANGED
@@ -98,7 +98,7 @@ const DEFAULT_CONFIG = {
98
98
  selfUpdate: {
99
99
  enabled: true,
100
100
  mode: "prompt",
101
- checkIntervalHours: 24,
101
+ checkIntervalHours: 12,
102
102
  startupCommands: ["start", "submit"]
103
103
  }
104
104
  };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sireai/optimus",
3
- "version": "0.1.29",
3
+ "version": "0.1.31",
4
4
  "description": "Optimus Codex-native background task runtime and harness scaffolding.",
5
5
  "repository": {
6
6
  "type": "git",
package/task-harnesses/bugfix/CONSTRAINTS.md CHANGED
@@ -8,6 +8,9 @@
8
8
 
9
9
  ## Patch rules
10
10
  - Change code only after reasoning through module boundaries, call chains, state flow, and upstream/downstream impact.
11
+ - Do not modify code that is not directly relevant to the reported problem. If wider edits are required, keep a direct causal link to the fix.
12
+ - Prefer clear, robust, maintainable fixes. Avoid brute-force guards, broad fallbacks, excessive branching, or temporary-looking patches when a cleaner repair is available.
13
+ - After the problem is fully solved, keep the patch to the minimum necessary change set to reduce behavioral drift and side-effect risk.
11
14
  - Do not ship a local symptom fix that breaks surrounding behavior.
12
15
  - Important code changes must include useful comments about intent, key decisions, boundary handling, or risk. Do not add comments that only restate obvious behavior.
13
16
  - If code changed, describe what changed, why, affected scope, and validation.