@fro.bot/systematic 3.26.0 → 3.26.1

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,6 +1,6 @@
1
1
  {
2
2
  "name": "@fro.bot/systematic",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Compound-engineering loops for OpenCode, Pi, and Claude Code",
5
5
  "type": "module",
6
6
  "homepage": "https://fro.bot/systematic",
@@ -103,8 +103,8 @@
103
103
  }
104
104
  },
105
105
  "devDependencies": {
106
- "@biomejs/biome": "2.5.15",
107
- "@earendil-works/pi-coding-agent": "1.3.0",
106
+ "@biomejs/biome": "2.6.2",
107
+ "@earendil-works/pi-coding-agent": "1.4.0",
108
108
  "@opencode-ai/plugin": "1.19.3",
109
109
  "@opencode-ai/sdk": "1.19.3",
110
110
  "@semantic-release/exec": "7.1.0",
@@ -129,7 +129,7 @@
129
129
  "zod": "4.6.7"
130
130
  },
131
131
  "overrides": {
132
- "@earendil-works/pi-ai": "1.3.0",
132
+ "@earendil-works/pi-ai": "1.4.0",
133
133
  "brace-expansion": "^5.0.8",
134
134
  "conventional-changelog-writer": ">=9",
135
135
  "devalue": "^5.9.3",
@@ -19,41 +19,41 @@ required_fields:
19
19
  problem_type:
20
20
  type: enum
21
21
  values:
22
- - build_error # Rails, bundle, compilation errors
23
- - test_failure # Test failures, flaky tests
24
- - runtime_error # Exceptions, crashes during execution
25
- - performance_issue # Slow queries, memory issues, N+1 queries
26
- - database_issue # Migration, query, schema problems
27
- - security_issue # Authentication, authorization, XSS, SQL injection
28
- - ui_bug # Frontend, Stimulus, Turbo issues
29
- - integration_issue # External service, API integration problems
30
- - logic_error # Business logic bugs
22
+ - build_error # Rails, bundle, compilation errors
23
+ - test_failure # Test failures, flaky tests
24
+ - runtime_error # Exceptions, crashes during execution
25
+ - performance_issue # Slow queries, memory issues, N+1 queries
26
+ - database_issue # Migration, query, schema problems
27
+ - security_issue # Authentication, authorization, XSS, SQL injection
28
+ - ui_bug # Frontend, Stimulus, Turbo issues
29
+ - integration_issue # External service, API integration problems
30
+ - logic_error # Business logic bugs
31
31
  - developer_experience # DX issues: workflow, tooling, seed data, dev setup
32
- - workflow_issue # Development process, missing steps, unclear practices
33
- - best_practice # Documenting patterns and practices to follow
34
- - documentation_gap # Missing or inadequate documentation
32
+ - workflow_issue # Development process, missing steps, unclear practices
33
+ - best_practice # Documenting patterns and practices to follow
34
+ - documentation_gap # Missing or inadequate documentation
35
35
  description: "Primary category of the problem"
36
36
 
37
37
  component:
38
38
  type: enum
39
39
  values:
40
- - rails_model # ActiveRecord models
41
- - rails_controller # ActionController
42
- - rails_view # ERB templates, ViewComponent
43
- - service_object # Custom service classes
44
- - background_job # Sidekiq, Active Job
45
- - database # PostgreSQL, migrations, schema
46
- - frontend_stimulus # Stimulus JS controllers
47
- - hotwire_turbo # Turbo Streams, Turbo Drive
48
- - email_processing # Email handling, mailers
49
- - brief_system # Brief generation, summarization
50
- - assistant # AI assistant, prompts
51
- - authentication # Devise, user auth
52
- - payments # Stripe, billing
40
+ - rails_model # ActiveRecord models
41
+ - rails_controller # ActionController
42
+ - rails_view # ERB templates, ViewComponent
43
+ - service_object # Custom service classes
44
+ - background_job # Sidekiq, Active Job
45
+ - database # PostgreSQL, migrations, schema
46
+ - frontend_stimulus # Stimulus JS controllers
47
+ - hotwire_turbo # Turbo Streams, Turbo Drive
48
+ - email_processing # Email handling, mailers
49
+ - brief_system # Brief generation, summarization
50
+ - assistant # AI assistant, prompts
51
+ - authentication # Devise, user auth
52
+ - payments # Stripe, billing
53
53
  - development_workflow # Dev process, seed data, tooling
54
- - testing_framework # Test setup, fixtures, VCR
55
- - documentation # README, guides, inline docs
56
- - tooling # Scripts, generators, CLI tools
54
+ - testing_framework # Test setup, fixtures, VCR
55
+ - documentation # README, guides, inline docs
56
+ - tooling # Scripts, generators, CLI tools
57
57
  description: "CORA component involved"
58
58
 
59
59
  symptoms:
@@ -69,47 +69,47 @@ required_fields:
69
69
  root_cause:
70
70
  type: enum
71
71
  values:
72
- - missing_association # Incorrect Rails associations
73
- - missing_include # Missing eager loading (N+1)
74
- - missing_index # Database performance issue
75
- - wrong_api # Using deprecated/incorrect Rails API
76
- - scope_issue # Incorrect query scope or filtering
77
- - thread_violation # Real-time unsafe operation
78
- - async_timing # Async/background job timing
79
- - memory_leak # Memory leak or excessive allocation
80
- - config_error # Configuration or environment issue
81
- - logic_error # Algorithm/business logic bug
82
- - test_isolation # Test isolation or fixture issue
83
- - missing_validation # Missing model validation
84
- - missing_permission # Authorization check missing
72
+ - missing_association # Incorrect Rails associations
73
+ - missing_include # Missing eager loading (N+1)
74
+ - missing_index # Database performance issue
75
+ - wrong_api # Using deprecated/incorrect Rails API
76
+ - scope_issue # Incorrect query scope or filtering
77
+ - thread_violation # Real-time unsafe operation
78
+ - async_timing # Async/background job timing
79
+ - memory_leak # Memory leak or excessive allocation
80
+ - config_error # Configuration or environment issue
81
+ - logic_error # Algorithm/business logic bug
82
+ - test_isolation # Test isolation or fixture issue
83
+ - missing_validation # Missing model validation
84
+ - missing_permission # Authorization check missing
85
85
  - missing_workflow_step # Skipped or undocumented workflow step
86
86
  - inadequate_documentation # Missing or unclear documentation
87
- - missing_tooling # Lacking helper scripts or automation
88
- - incomplete_setup # Missing seed data, fixtures, or config
87
+ - missing_tooling # Lacking helper scripts or automation
88
+ - incomplete_setup # Missing seed data, fixtures, or config
89
89
  description: "Fundamental cause of the problem"
90
90
 
91
91
  resolution_type:
92
92
  type: enum
93
93
  values:
94
- - code_fix # Fixed by changing source code
95
- - migration # Fixed by database migration
96
- - config_change # Fixed by changing configuration
97
- - test_fix # Fixed by correcting tests
98
- - dependency_update # Fixed by updating gem/dependency
99
- - environment_setup # Fixed by environment configuration
94
+ - code_fix # Fixed by changing source code
95
+ - migration # Fixed by database migration
96
+ - config_change # Fixed by changing configuration
97
+ - test_fix # Fixed by correcting tests
98
+ - dependency_update # Fixed by updating gem/dependency
99
+ - environment_setup # Fixed by environment configuration
100
100
  - workflow_improvement # Improved development workflow or process
101
101
  - documentation_update # Added or updated documentation
102
- - tooling_addition # Added helper script or automation
103
- - seed_data_update # Updated db/seeds.rb or fixtures
102
+ - tooling_addition # Added helper script or automation
103
+ - seed_data_update # Updated db/seeds.rb or fixtures
104
104
  description: "Type of fix applied"
105
105
 
106
106
  severity:
107
107
  type: enum
108
108
  values:
109
- - critical # Blocks production or development (build fails, data loss)
110
- - high # Impairs core functionality (feature broken, security issue)
111
- - medium # Affects specific feature (UI broken, performance impact)
112
- - low # Minor issue or edge case
109
+ - critical # Blocks production or development (build fails, data loss)
110
+ - high # Impairs core functionality (feature broken, security issue)
111
+ - medium # Affects specific feature (UI broken, performance impact)
112
+ - low # Minor issue or edge case
113
113
  description: "Impact severity"
114
114
 
115
115
  optional_fields:
@@ -74,12 +74,13 @@ When the command does not print `saved`, the temp file could not be created or t
74
74
  **Generate the updated title and body** — using the PR URL from DU-2 and the commit range it covers, write an updated PR title and body. The URL preserves repo/PR identity even when invoked from a worktree or subdirectory. If the user provided a focus (e.g., "include the benchmarking results"), incorporate it into the generated content. Write the body to an OS temp file:
75
75
 
76
76
  ```bash
77
- BODY_FILE=$(mktemp /tmp/pr-body-XXXXXX.md)
78
- cat > "$BODY_FILE" << 'EOF'
77
+ BODY_FILE=$(mktemp) && cat > "$BODY_FILE" << 'EOF' && echo "saved $BODY_FILE"
79
78
  <generated body>
80
79
  EOF
81
80
  ```
82
81
 
82
+ When the command does not print `saved` and the path, the temp file could not be created or written. Stop and apply nothing. Tell the user why, remove the old file, and ask how to proceed. Use the printed path as the body file below.
83
+
83
84
  If the PR is not open or the commit range cannot be resolved, report the issue and stop.
84
85
 
85
86
  **Evidence decision:** Preserve any existing `## Demo` or `## Screenshots` block from the current body by default. Carry the `## Demo` section with `mode:carry`, by following Carrying the Demo section: `old=` is the old body file saved above, and `new=` is the body file written above. The carry always runs, and it runs before the compare-and-confirm step. If the user's focus asks to refresh or remove evidence, honor that intent and skip the carry. When the carry ends, remove the old file:
@@ -95,10 +96,10 @@ Do not offer to publish images here. If the user asks to attach local images, ro
95
96
  - If the user provided a focus, confirm it was addressed.
96
97
  - Ask the user to confirm before applying.
97
98
 
98
- If confirmed, apply with the returned title and body file:
99
+ If confirmed, apply with the returned title and body file. `--body-file` makes `gh` read the file as written, so trailing newlines and shell-special characters in the body survive:
99
100
 
100
101
  ```bash
101
- gh pr edit --title "<returned title>" --body "$(cat "<returned body_file>")"
102
+ gh pr edit --title "<returned title>" --body-file "<returned body_file>"
102
103
  ```
103
104
 
104
105
  Report the PR URL.
@@ -233,11 +234,11 @@ When evidence is not possible (docs-only, markdown-only, changelog-only, release
233
234
  - **Title**: conventional-commit format, under 72 characters, describing the value delivered (not the implementation).
234
235
  - **Body**: value-first narrative scaled to the change size. Apply the writing principles, commit classification, sizing, and narrative framing described in this skill. Write the body to an OS temp file:
235
236
  ```bash
236
- BODY_FILE=$(mktemp /tmp/pr-body-XXXXXX.md)
237
- cat > "$BODY_FILE" << 'EOF'
237
+ BODY_FILE=$(mktemp) && cat > "$BODY_FILE" << 'EOF' && echo "saved $BODY_FILE"
238
238
  <generated body>
239
239
  EOF
240
240
  ```
241
+ When the command does not print `saved` and the path, the temp file could not be created or written. Stop, and do not create or edit the PR, because there is no body to apply. Use the printed path as `<body_file>` below.
241
242
  - Splice any captured evidence as a `## Demo` section into the body file before applying. For the file that **Publish local images** returned, append it with the shell and delete it once it is appended, so no SHA is retyped:
242
243
  ```bash
243
244
  printf '\n' >> "<body_file>" && cat "<demo_file>" >> "<body_file>" && rm -f "<demo_file>"
@@ -261,10 +262,10 @@ If the branch diff is empty or the base ref is unresolved, report the issue and
261
262
  Using the title and body file generated in Step 6:
262
263
 
263
264
  ```bash
264
- gh pr create --title "<title>" --body "$(cat "<body_file>")"
265
+ gh pr create --title "<title>" --body-file "<body_file>"
265
266
  ```
266
267
 
267
- Keep the title under 72 characters.
268
+ Keep the title under 72 characters. Pass the body with `--body-file`, never through command substitution, which strips trailing newlines.
268
269
 
269
270
  #### Existing PR (found in Step 3)
270
271
 
@@ -287,7 +288,7 @@ The new commits are already on the PR from Step 5. Report the PR URL, then ask w
287
288
  **Apply.** Only after `status=ok` or `status=absent`. The carry step edits the body file in place, so the apply step is the same:
288
289
 
289
290
  ```bash
290
- gh pr edit --title "<title>" --body "$(cat "<body_file>")"
291
+ gh pr edit --title "<title>" --body-file "<body_file>"
291
292
  ```
292
293
 
293
294
  - If **no** -- skip Step 6 entirely and finish. Do not run evidence capture when the user declined the rewrite.