24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
|
# BUG_REPORT: add-self-improvement-loop
|
||
|
|
|
||
|
|
## Findings
|
||
|
|
|
||
|
|
### Bug 1 (LOW): install.sh loop bootstrap is inside the `else` block
|
||
|
|
|
||
|
|
The loop creation commands are inside the `else` block of `if [ -d "$FRAMEWORK_DIR" ]`, which means they only run on fresh installs. If a user previously installed the framework before this change and runs `install.sh` again, they get "already installed" and the loop is NOT created. This is correct behavior -- `update.sh` handles the existing-user case.
|
||
|
|
|
||
|
|
**Severity:** LOW (by design)
|
||
|
|
**Fix:** None needed.
|
||
|
|
|
||
|
|
### Bug 2 (INFO): No `--project` flag consistency check
|
||
|
|
|
||
|
|
`install.sh` uses `--project "$FRAMEWORK_DIR"` while `update.sh` also uses `--project "$FRAMEWORK_DIR"`. Both are consistent. The `work_source.project` in the template is `"~/.automaton/"` (a string), but `--create-loop` doesn't use `work_source.project` -- it uses the `--project` flag. The runner reads `work_source.project` at tick time. No mismatch because `--project "$FRAMEWORK_DIR"` (which is `$HOME/.automaton`) and `work_source.project: "~/.automaton/"` resolve to the same path.
|
||
|
|
|
||
|
|
**Severity:** INFO (no bug)
|
||
|
|
**Fix:** None needed.
|
||
|
|
|
||
|
|
## Summary
|
||
|
|
|
||
|
|
No correctness bugs found. One LOW (by design) and one INFO.
|
||
|
|
|
||
|
|
**Verdict: CLEAN**
|