Summary
`ensureInspectorWorkflows()` in `internal/app/screen_inspector.go` checks whether workflows are empty but then calls `refreshInspectorWorkflows()` unconditionally regardless of the result, making the isEmpty check meaningless. This likely causes unnecessary re-fetches on every call.
Details
- Current logic: check if empty → call refresh anyway
- The isEmpty guard was presumably intended to short-circuit the refresh when workflows are already loaded
- As written, the guard is dead code and the function always refreshes
Checklist
References
- `internal/app/screen_inspector.go:53-59`
Raised from senior code review (2026-05-12).
Summary
`ensureInspectorWorkflows()` in `internal/app/screen_inspector.go` checks whether workflows are empty but then calls `refreshInspectorWorkflows()` unconditionally regardless of the result, making the isEmpty check meaningless. This likely causes unnecessary re-fetches on every call.
Details
Checklist
References
Raised from senior code review (2026-05-12).