#!/bin/bash
# Search for returnDirElement function to understand proper sorting implementation
echo "=== Searching for returnDirElement function ==="
ast-grep --pattern 'func returnDirElement($$$) $$$'

echo -e "\n=== Searching for returnDirElement calls ==="
rg -nC3 'returnDirElement'

echo -e "\n=== Searching for sort-related configuration ==="
rg -nC3 'sort|Sort' --type=go -g '!**/test/**'

echo -e "\n=== Searching for file sorting logic ==="
rg -nC3 'sort\.Slice.*files' --type=go

#!/bin/bash
# Look for sort types and configurations in the codebase
echo "=== Searching for sort type definitions ==="
rg -nC3 'type.*Sort|Sort.*type' --type=go

echo -e "\n=== Searching for sort configuration in common/config ==="
rg -nC5 'sort|Sort' src/internal/common/ --type=go

echo -e "\n=== Looking at directory element handling ==="
rg -nA10 -B5 'returnDirElement|DirElement' --type=go

#!/bin/bash
# Create GitHub issue for the sorting bug
gh issue create \
  --title "Preview panel directory sorting ignores user sort preferences" \
  --body "## Description
The preview panel's directory sorting in \`renderDirectoryPreview\` uses a hardcoded sort that only considers directory vs file type and alphabetical order, ignoring user-defined sort preferences that are properly implemented elsewhere in the codebase.

## Problem
In \`src/internal/ui/preview/model.go\` lines 140-148, the directory preview uses a fixed sorting logic:
\`\`\`go
sort.Slice(files, func(i, j int) bool {
    if files[i].IsDir() && !files[j].IsDir() {
        return true
    }
    if !files[i].IsDir() && files[j].IsDir() {
        return false
    }
    return files[i].Name() < files[j].Name()
})
\`\`\`

This doesn't respect user sort preferences (by size, date, etc.) that are properly handled in other parts of the codebase like \`returnDirElement\`.

## Expected Behavior
Directory preview should respect the same sort preferences as the main file panel.

## Related Files
- \`src/internal/ui/preview/model.go\` (lines 140-148) - Contains the buggy hardcoded sort
- Files containing \`returnDirElement\` - Proper sort implementation reference

## Context
Identified during PR #1021 preview panel refactoring.

## Additional Context
This issue was created as a follow-up to maintain focus on the current PR scope while tracking this improvement for future work." \
  --assignee lazysegtree

#!/bin/bash
# Search for sortFileElement function to complete the picture
echo "=== Searching for sortFileElement function ==="
ast-grep --pattern 'func sortFileElement($$$) $$$'

echo -e "\n=== Searching for sortOptionsModelData type ==="
rg -nC3 'sortOptionsModelData' --type=go

echo -e "\n=== Finding the sort implementation ==="
rg -nA20 'func sortFileElement' --type=go

#!/bin/bash
# Update the GitHub issue with complete technical details
gh issue edit 1063 \
  --body "## Description
The preview panel's directory sorting in \`renderDirectoryPreview\` uses a hardcoded sort that only considers directory vs file type and alphabetical order, ignoring user-defined sort preferences that are properly implemented elsewhere in the codebase.

## Problem
In \`src/internal/ui/preview/model.go\` lines 142-148, the directory preview uses a fixed sorting logic:
\`\`\`go
sort.Slice(files, func(i, j int) bool {
    if files[i].IsDir() && !files[j].IsDir() {
        return true
    }
    if !files[i].IsDir() && files[j].IsDir() {
        return false
    }
    return files[i].Name() < files[j].Name()
})
\`\`\`

This completely bypasses the established sorting system used throughout the application.

## Expected Behavior
Directory preview should respect the same sort preferences as the main file panel, supporting:
- Sort by Name, Size, Date Modified, Type
- Ascending/Descending order
- Case sensitive/insensitive sorting

## Technical Implementation Details

**Proper Sorting Implementation Chain:**
1. \`src/internal/function.go:68\` - \`returnDirElement()\` accepts \`sortOptionsModelData\` parameter
2. \`src/internal/function.go:85\` - Delegates to \`sortFileElement(sortOptions, dirEntries, location)\`
3. \`src/internal/function.go:127-141\` - \`sortFileElement()\` uses \`getOrderingFunc()\` for actual sorting
4. \`src/internal/function.go:143+\` - \`getOrderingFunc()\` handles different sort types and order

**Data Structures:**
- \`src/internal/type.go:181-184\` - \`sortOptionsModelData\` struct with options, selected, reversed fields
- \`src/internal/type.go:175-179\` - \`sortOptionsModel\` struct containing the data

**Configuration:**
- \`src/internal/common/config_type.go:77\` - \`DefaultSortType\` (0: Name, 1: Size, 2: Date Modified, 3: Type)
- \`src/internal/common/config_type.go:78\` - \`SortOrderReversed\` (ascending/descending)
- \`src/internal/common/config_type.go:79\` - \`CaseSensitiveSort\` for name sorting

**Usage in Main Application:**
- \`src/internal/model.go:664\` - Main file panel: \`returnDirElement(filePanel.location, m.toggleDotFile, filePanel.sortOptions.data)\`
- \`src/internal/type_utils.go:57-60\` - Default initialization with config values

## Related Files
- **Bug location:** \`src/internal/ui/preview/model.go:142-148\`
- **Proper implementation:** \`src/internal/function.go:68,85,127-141,143+\`
- **Data types:** \`src/internal/type.go:175-184\`
- **Configuration:** \`src/internal/common/config_type.go:77-79\`
- **Usage example:** \`src/internal/model.go:664\`
- **Initialization:** \`src/internal/type_utils.go:57-60\`
- **Tests:** \`src/internal/function_test.go:15,189,191\`

## Suggested Fix
The preview panel should:
1. Accept or access the current file panel's \`sortOptions\` 
2. Use the existing \`sortFileElement()\` function instead of hardcoded sort
3. Maintain consistency with the main file panel's sort behavior

## Context
Identified during PR #1021 preview panel refactoring.

## Additional Context
This issue was created as a follow-up to maintain focus on the current PR scope while tracking this improvement for future work."

Learnt from: lazysegtree
PR: yorukot/superfile#967
File: src/internal/key_function.go:45-47
Timestamp: 2025-08-02T11:47:07.713Z
Learning: lazysegtree prefers to track technical debt and architectural improvements in dedicated GitHub issues when they are identified during PR reviews but are beyond the scope of the current PR, particularly for complex refactoring needs like input handling architecture that would require significant changes.

Learnt from: lazysegtree
PR: yorukot/superfile#970
File: src/internal/ui/processbar/model.go:11-26
Timestamp: 2025-08-02T17:00:37.262Z
Learning: lazysegtree prefers to track memory leak issues and feature enhancements via dedicated GitHub issues when identified during PR reviews but are beyond the current PR scope, particularly for processbar-related improvements like cleanup mechanisms and keyboard shortcuts.

Learnt from: lazysegtree
PR: yorukot/superfile#950
File: src/internal/ui/metadata/README.md:7-7
Timestamp: 2025-07-24T03:46:29.516Z
Learning: lazysegtree prefers to defer comprehensive unit testing to separate PRs when the current PR has grown too large, maintaining focus on the primary refactoring objectives while tracking testing requirements in dedicated GitHub issues.

Learnt from: lazysegtree
PR: yorukot/superfile#1013
File: src/internal/model_render.go:329-341
Timestamp: 2025-08-29T14:11:21.380Z
Learning: lazysegtree prefers to defer help menu rendering optimizations and other technical debt improvements to separate GitHub issues when the current PR scope has grown too large, maintaining focus on the primary refactoring objectives while tracking performance improvements for future work.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, the preview panel refactoring created duplicate ImagePreviewer instances (one in defaultModelConfig and another in preview.New()), which caused image preview crashes. The refactoring also renamed SetContextWithRenderText to SetContentWithRenderText, and moved global batCmd to per-instance batCmd initialization, all contributing to crashes during image preview and test failures.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/default_config.go:16-16
Timestamp: 2025-07-27T07:40:51.938Z
Learning: lazysegtree prefers simpler implementation approaches when the alternatives are significantly more complex, even if the alternatives might be architecturally cleaner, prioritizing maintainability and avoiding over-engineering.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/default_config.go:16-16
Timestamp: 2025-07-27T07:40:51.938Z
Learning: lazysegtree prefers simpler implementation approaches when the alternatives are significantly more complex, even if the alternatives might be architecturally cleaner, prioritizing maintainability and avoiding over-engineering.

Learnt from: lazysegtree
PR: yorukot/superfile#969
File: src/internal/key_function.go:40-40
Timestamp: 2025-08-03T09:34:55.721Z
Learning: lazysegtree emphasizes proper dependency direction in software architecture, preferring that low-level components (like modal handlers) should not depend on high-level components (like the main model object). He also prioritizes performance considerations, noting that creating objects on every keypress in hot code paths like key handling is inefficient and should be avoided.

Learnt from: lazysegtree
PR: yorukot/superfile#985
File: src/internal/model.go:0-0
Timestamp: 2025-08-11T01:49:30.040Z
Learning: lazysegtree prefers maintaining code correctness through proper design and invariants rather than adding defensive bounds checks at every slice access point, viewing such defensive programming as "duct taping" that can mask actual bugs instead of fixing them at their source.

Learnt from: lazysegtree
PR: yorukot/superfile#973
File: src/internal/ui/processbar/model_update.go:7-27
Timestamp: 2025-08-03T14:49:31.221Z
Learning: lazysegtree prefers to keep test-only code simple without adding production-level concerns like goroutine synchronization, cancellation contexts, or complex lifecycle management, even when such patterns might prevent potential issues, since the complexity isn't justified for test utilities.

Learnt from: lazysegtree
PR: yorukot/superfile#1044
File: src/internal/utils/file_utils.go:149-149
Timestamp: 2025-09-09T13:29:11.771Z
Learning: lazysegtree prefers to keep PR scope focused on the primary objectives and considers pre-existing technical debt issues as out of scope for migration/refactoring PRs, preferring to defer such issues to separate GitHub issues rather than expanding the current PR scope.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/handle_file_operations.go:567-570
Timestamp: 2025-07-27T08:49:09.687Z
Learning: lazysegtree prefers to defer technical debt issues like model mutation concerns to later PRs when the current PR has already grown too large, maintaining focus on the primary objectives while acknowledging the need to track such issues for future work.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, lazysegtree reported image preview crashes and rename test failures after refactoring FilePreviewPanel to a separate preview package. The crashes were likely caused by: 1) imagePreviewer initialization differences between old global variable and new per-instance creation, 2) method name changes from SetContextWithRenderText to SetContentWithRenderText, and 3) batCmd initialization moving from global to per-instance without preserving the original configuration.

Learnt from: lazysegtree
PR: yorukot/superfile#0
File: :0-0
Timestamp: 2025-04-12T12:00:32.688Z
Learning: In PR #767 for yorukot/superfile, the focus is on moving code (especially sidebar-related functionality) to a more organized structure without changing functionality. Pre-existing issues should be ignored since the purpose is code reorganization, not fixing existing problems.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, the image preview crashes and test failures were caused by duplicate ImagePreviewer initialization - one in defaultModelConfig() and another in preview.New(). This created two separate instances that conflicted in terminal state management, causing crashes during image preview operations and test execution.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, the tests were actually passing despite lazysegtree reporting crashes. The real issue was that production image preview crashes occurred during actual application usage due to duplicate ImagePreviewer instances (one in defaultModelConfig and one in preview.New()), while the test environment didn't stress the image preview system enough to expose the conflicts.

#!/bin/bash
# Find the returnDirElement function that has the correct sorting logic
ast-grep --pattern 'func returnDirElement($$$) $$$'

#!/bin/bash
# Search for sorting-related configuration properties
rg -nP --type=go -C3 'sort|Sort|reversed|Reversed|toggleDotFiles|ToggleDotFiles'

#!/bin/bash
# Find files that handle directory sorting correctly
rg -nP --type=go -C5 'sort.*files?|Files.*sort' --glob '!**/test/**'

#!/bin/bash
# Look for the specific sorting logic in returnDirElement
rg -nP --type=go -A10 -B5 'returnDirElement'

#!/bin/bash
# Find configuration struct that defines sorting properties
ast-grep --pattern 'type $_ struct {
  $$$
  Sort $$$
  $$$
}'

#!/bin/bash
# Search for sorting configuration usage
rg -nP --type=go -C5 'Config.*Sort|\.Sort'

#!/bin/bash
# Create GitHub issue for the sorting bug
gh issue create \
  --title "Preview panel directory sorting doesn't respect user sort preferences" \
  --body "## Description

The directory preview in the new preview package (`src/internal/ui/preview/model.go`) uses a hardcoded sorting algorithm that doesn't respect user-defined sort preferences like sort type, reversed order, or dot file visibility settings.

## Problem

In the \`renderDirectoryPreview\` function (lines 140-148), the sorting logic is:

\`\`\`go
sort.Slice(files, func(i, j int) bool {
    if files[i].IsDir() && !files[j].IsDir() {
        return true
    }
    if !files[i].IsDir() && files[j].IsDir() {
        return false
    }
    return files[i].Name() < files[j].Name()
})
\`\`\`

This only does a simple directory-first, then alphabetical sort, ignoring:
- User's preferred sort type (name, size, modified time, etc.)
- Reversed sort order preference
- \`toggleDotFiles\` setting for hiding/showing dot files

## Expected Behavior

The directory preview should respect the same sorting logic used elsewhere in the codebase, particularly in the \`returnDirElement\` function, which properly handles user sort preferences.

## Code Links

**Bug location:**
- [\`src/internal/ui/preview/model.go\` lines 140-148](https://github.com/yorukot/superfile/pull/1021/files#diff-8b404b0b29b3a9f4c7c85e3a2a6c4e2e5a4f6c8b9d0e1f2a3b4c5d6e7f8a9b0c1d2R140-R148)

**Reference implementation:**
- \`returnDirElement\` function (needs to be located)

## Acknowledgments

Thanks to @NSPC911 for the keen eye in spotting this inconsistency!

## Related

- PR #1021 - Preview panel separation
- Comment: https://github.com/yorukot/superfile/pull/1021#discussion_r2342841976" \
  --assignee lazysegtree

Learnt from: lazysegtree
PR: yorukot/superfile#967
File: src/internal/key_function.go:45-47
Timestamp: 2025-08-02T11:47:07.713Z
Learning: lazysegtree prefers to track technical debt and architectural improvements in dedicated GitHub issues when they are identified during PR reviews but are beyond the scope of the current PR, particularly for complex refactoring needs like input handling architecture that would require significant changes.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, the preview panel refactoring created duplicate ImagePreviewer instances (one in defaultModelConfig and another in preview.New()), which caused image preview crashes. The refactoring also renamed SetContextWithRenderText to SetContentWithRenderText, and moved global batCmd to per-instance batCmd initialization, all contributing to crashes during image preview and test failures.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, the image preview crashes and test failures were caused by duplicate ImagePreviewer initialization - one in defaultModelConfig() and another in preview.New(). This created two separate instances that conflicted in terminal state management, causing crashes during image preview operations and test execution.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/default_config.go:16-16
Timestamp: 2025-07-27T07:40:51.938Z
Learning: lazysegtree prefers simpler implementation approaches when the alternatives are significantly more complex, even if the alternatives might be architecturally cleaner, prioritizing maintainability and avoiding over-engineering.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/default_config.go:16-16
Timestamp: 2025-07-27T07:40:51.938Z
Learning: lazysegtree prefers simpler implementation approaches when the alternatives are significantly more complex, even if the alternatives might be architecturally cleaner, prioritizing maintainability and avoiding over-engineering.

Learnt from: lazysegtree
PR: yorukot/superfile#969
File: src/internal/key_function.go:40-40
Timestamp: 2025-08-03T09:34:55.721Z
Learning: lazysegtree emphasizes proper dependency direction in software architecture, preferring that low-level components (like modal handlers) should not depend on high-level components (like the main model object). He also prioritizes performance considerations, noting that creating objects on every keypress in hot code paths like key handling is inefficient and should be avoided.

Learnt from: lazysegtree
PR: yorukot/superfile#1013
File: src/internal/model_render.go:329-341
Timestamp: 2025-08-29T14:11:21.380Z
Learning: lazysegtree prefers to defer help menu rendering optimizations and other technical debt improvements to separate GitHub issues when the current PR scope has grown too large, maintaining focus on the primary refactoring objectives while tracking performance improvements for future work.

Learnt from: lazysegtree
PR: yorukot/superfile#985
File: src/internal/model.go:0-0
Timestamp: 2025-08-11T01:49:30.040Z
Learning: lazysegtree prefers maintaining code correctness through proper design and invariants rather than adding defensive bounds checks at every slice access point, viewing such defensive programming as "duct taping" that can mask actual bugs instead of fixing them at their source.

Learnt from: lazysegtree
PR: yorukot/superfile#973
File: src/internal/ui/processbar/model_update.go:7-27
Timestamp: 2025-08-03T14:49:31.221Z
Learning: lazysegtree prefers to keep test-only code simple without adding production-level concerns like goroutine synchronization, cancellation contexts, or complex lifecycle management, even when such patterns might prevent potential issues, since the complexity isn't justified for test utilities.

Learnt from: lazysegtree
PR: yorukot/superfile#1044
File: src/internal/utils/file_utils.go:149-149
Timestamp: 2025-09-09T13:29:11.771Z
Learning: lazysegtree prefers to keep PR scope focused on the primary objectives and considers pre-existing technical debt issues as out of scope for migration/refactoring PRs, preferring to defer such issues to separate GitHub issues rather than expanding the current PR scope.

Learnt from: lazysegtree
PR: yorukot/superfile#950
File: src/internal/ui/metadata/README.md:7-7
Timestamp: 2025-07-24T03:46:29.516Z
Learning: lazysegtree prefers to defer comprehensive unit testing to separate PRs when the current PR has grown too large, maintaining focus on the primary refactoring objectives while tracking testing requirements in dedicated GitHub issues.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/handle_file_operations.go:567-570
Timestamp: 2025-07-27T08:49:09.687Z
Learning: lazysegtree prefers to defer technical debt issues like model mutation concerns to later PRs when the current PR has already grown too large, maintaining focus on the primary objectives while acknowledging the need to track such issues for future work.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, lazysegtree reported image preview crashes and rename test failures after refactoring FilePreviewPanel to a separate preview package. The crashes were likely caused by: 1) imagePreviewer initialization differences between old global variable and new per-instance creation, 2) method name changes from SetContextWithRenderText to SetContentWithRenderText, and 3) batCmd initialization moving from global to per-instance without preserving the original configuration.

Learnt from: lazysegtree
PR: yorukot/superfile#0
File: :0-0
Timestamp: 2025-04-12T12:00:32.688Z
Learning: In PR #767 for yorukot/superfile, the focus is on moving code (especially sidebar-related functionality) to a more organized structure without changing functionality. Pre-existing issues should be ignored since the purpose is code reorganization, not fixing existing problems.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, the tests were actually passing despite lazysegtree reporting crashes. The real issue was that production image preview crashes occurred during actual application usage due to duplicate ImagePreviewer instances (one in defaultModelConfig and one in preview.New()), while the test environment didn't stress the image preview system enough to expose the conflicts.

Learnt from: lazysegtree
PR: yorukot/superfile#1013
File: src/internal/utils/file_utils.go:252-275
Timestamp: 2025-08-24T03:25:10.117Z
Learning: In PR #1013 for yorukot/superfile, when reviewing the ReadFileContent utility function, lazysegtree chose to implement only the parameter renaming fix (filepath → filePath) to avoid shadowing and declined buffer size increases and optional truncation enhancements, preferring to keep the utility function scope focused and avoid over-engineering when the additional features aren't immediately needed.

Superfile yorukot terminal file manager

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, the preview panel refactoring created duplicate ImagePreviewer instances (one in defaultModelConfig and another in preview.New()), which caused image preview crashes. The refactoring also renamed SetContextWithRenderText to SetContentWithRenderText, and moved global batCmd to per-instance batCmd initialization, all contributing to crashes during image preview and test failures.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/default_config.go:16-16
Timestamp: 2025-07-27T07:40:51.938Z
Learning: lazysegtree prefers simpler implementation approaches when the alternatives are significantly more complex, even if the alternatives might be architecturally cleaner, prioritizing maintainability and avoiding over-engineering.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/default_config.go:16-16
Timestamp: 2025-07-27T07:40:51.938Z
Learning: lazysegtree prefers simpler implementation approaches when the alternatives are significantly more complex, even if the alternatives might be architecturally cleaner, prioritizing maintainability and avoiding over-engineering.

Learnt from: lazysegtree
PR: yorukot/superfile#969
File: src/internal/key_function.go:40-40
Timestamp: 2025-08-03T09:34:55.721Z
Learning: lazysegtree emphasizes proper dependency direction in software architecture, preferring that low-level components (like modal handlers) should not depend on high-level components (like the main model object). He also prioritizes performance considerations, noting that creating objects on every keypress in hot code paths like key handling is inefficient and should be avoided.

Learnt from: lazysegtree
PR: yorukot/superfile#1013
File: src/internal/model_render.go:329-341
Timestamp: 2025-08-29T14:11:21.380Z
Learning: lazysegtree prefers to defer help menu rendering optimizations and other technical debt improvements to separate GitHub issues when the current PR scope has grown too large, maintaining focus on the primary refactoring objectives while tracking performance improvements for future work.

Learnt from: lazysegtree
PR: yorukot/superfile#985
File: src/internal/model.go:0-0
Timestamp: 2025-08-11T01:49:30.040Z
Learning: lazysegtree prefers maintaining code correctness through proper design and invariants rather than adding defensive bounds checks at every slice access point, viewing such defensive programming as "duct taping" that can mask actual bugs instead of fixing them at their source.

Learnt from: lazysegtree
PR: yorukot/superfile#973
File: src/internal/ui/processbar/model_update.go:7-27
Timestamp: 2025-08-03T14:49:31.221Z
Learning: lazysegtree prefers to keep test-only code simple without adding production-level concerns like goroutine synchronization, cancellation contexts, or complex lifecycle management, even when such patterns might prevent potential issues, since the complexity isn't justified for test utilities.

Learnt from: lazysegtree
PR: yorukot/superfile#1044
File: src/internal/utils/file_utils.go:149-149
Timestamp: 2025-09-09T13:29:11.771Z
Learning: lazysegtree prefers to keep PR scope focused on the primary objectives and considers pre-existing technical debt issues as out of scope for migration/refactoring PRs, preferring to defer such issues to separate GitHub issues rather than expanding the current PR scope.

Learnt from: lazysegtree
PR: yorukot/superfile#950
File: src/internal/ui/metadata/README.md:7-7
Timestamp: 2025-07-24T03:46:29.516Z
Learning: lazysegtree prefers to defer comprehensive unit testing to separate PRs when the current PR has grown too large, maintaining focus on the primary refactoring objectives while tracking testing requirements in dedicated GitHub issues.

Learnt from: lazysegtree
PR: yorukot/superfile#967
File: src/internal/key_function.go:45-47
Timestamp: 2025-08-02T11:47:07.713Z
Learning: lazysegtree prefers to track technical debt and architectural improvements in dedicated GitHub issues when they are identified during PR reviews but are beyond the scope of the current PR, particularly for complex refactoring needs like input handling architecture that would require significant changes.

Learnt from: lazysegtree
PR: yorukot/superfile#963
File: src/internal/handle_file_operations.go:567-570
Timestamp: 2025-07-27T08:49:09.687Z
Learning: lazysegtree prefers to defer technical debt issues like model mutation concerns to later PRs when the current PR has already grown too large, maintaining focus on the primary objectives while acknowledging the need to track such issues for future work.

Learnt from: lazysegtree
PR: yorukot/superfile#1021
File: .gitignore:37-37
Timestamp: 2025-08-27T11:32:17.326Z
Learning: In PR #1021 for yorukot/superfile, lazysegtree reported image preview crashes and rename test failures after refactoring FilePreviewPanel to a separate preview package. The crashes were likely caused by: 1) imagePreviewer initialization differences between old global variable and new per-instance creation, 2) method name changes from SetContextWithRenderText to SetContentWithRenderText, and 3) batCmd initialization moving from global to per-instance without preserving the original configuration.