Feat/integrated config edit

[Firstp1ck]

Summary

• Integrated TUI config editor: New modal to view and edit settings from inside the app, with typed schema, validation, persistence, global events, mouse support, footer integration, and UI under src/ui/modals/config_editor.rs / src/events/modals/config_editor.rs / src/state/config_editor.rs.
• Keybind editing hardening: keybinds.conf is fully wired into the integrated editor flow (schema exports, file activation, active-path visibility), with typed key-chord serialization/lookup and same-scope conflict detection to block invalid colliding saves.
• Typed config patching: theme/config/patch.rs and theme/config/schema.rs support structured edits aligned with shipped config examples.
• Update checks: Prefer checkupdates when available; classify failures and stderr; fall back through fakeroot temp-db sync and stale pacman -Qu when appropriate. Optional pacman -Sl index paths are gated on active repo names from the main pacman.conf (EndeavourOS, CachyOS, Artix, BlackArch) via PacmanConfScan::active_repo_names_lower and refactors in src/index/fetch.rs.
• Logging: Periodic update-check INFO lines are deduplicated: summary INFO only when count, authority, strategy, or reason digest changes (or first non-empty reason run); isolated checkupdates execution logs at DEBUG.
• Updates modal UX: Scroll position centers the selected row when possible (clamped at list ends); tests and docs updated for centering behavior.
• Locales: New strings for en-US, de-DE, hu-HU for the config editor and related UI.
• Assets: Images/Config_Editor_v0.8.3.png added for the config editor UI.

Type of change

• feat (new feature)
• fix (bug fix)
• docs (documentation only)
• refactor (no functional change)
• perf (performance)
• test (add/update tests)
• chore (build/infra/CI)
• ui (visual/interaction changes)
• breaking change (incompatible behavior)

Related issues

Closes #

How to test

cargo fmt --all
cargo clippy --all-targets --all-features -- -D warnings
cargo check
cargo test -- --test-threads=1

Manual / integration:

• Run the TUI (RUST_LOG=pacsea=debug cargo run -- with --dry-run where you only need to observe behavior without installs).
• Open the integrated config editor from the documented entry point (footer / keybind as wired in this branch); change a setting, save, restart, and confirm values persist and match config/ schema expectations.
• In keybinds.conf, attempt both a valid keybind edit and a same-scope conflicting keybind edit; confirm valid saves persist and conflicts are rejected with no file write.
• Trigger update checks with and without checkupdates on PATH; confirm authority ordering, reason codes in logs, and that INFO spam is reduced on steady-state repeats.
• Open the updates modal, move selection through the list (start, middle, end), and confirm the selected row stays centered when the viewport allows it.
• Spot-check localized strings if using de-DE or hu-HU.

Screenshots / recordings (if UI changes)

See Images/Config_Editor_v0.8.3.png for the integrated config editor.

Checklist

Code Quality:

• Code compiles locally (cargo check)
• cargo fmt --all ran without changes
• cargo clippy --all-targets --all-features -- -D warnings is clean
• cargo test -- --test-threads=1 passes
• Complexity checks pass for new code (cargo test complexity -- --nocapture)
• All new functions/methods have rustdoc comments (What, Inputs, Output, Details)
• No unwrap() or expect() in non-test code

Testing:

• Added or updated tests where it makes sense
• For bug fixes: created failing tests first, then fixed the issue
• Tests are meaningful and cover the functionality

Documentation:

• Updated README if behavior, options, or keybinds changed (keep high-level, reference wiki)
• Updated relevant wiki pages if needed:
  • How to use Pacsea
  • Configuration
  • Keyboard Shortcuts
• Updated config examples in config/ directory if config keys changed
• For UI changes: included screenshots and updated Images/ if applicable

Compatibility:

• Changes respect --dry-run flag
• Code degrades gracefully if pacman/paru/yay are unavailable
• No breaking changes (or clearly documented if intentional)

Security (CI):

• Ran ./dev/scripts/security-check.sh before opening the PR (local mirror of Security + Lint workflows: rustfmt, clippy, cargo audit, cargo deny check, gitleaks — skipped steps print install hints)
• After adding or updating dependencies: cargo audit and cargo deny check pass (deny.toml); no new high-severity or license issues that would fail GitHub dependency review on this PR
• No secrets or credential-like placeholders that would trip gitleaks (see .gitleaks.toml for allowlisted paths if you must add test fixtures)
• Follows secure coding rules in AGENTS.md / CLAUDE.md (shell quoting, credentials, HTTP, paths) — see dev/SECURITY_REMEDIATION_GUIDE.md for remediation patterns

Other:

• Not a packaging change for AUR (otherwise propose in pacsea-bin or pacsea-git repos)

Notes for reviewers

• Large surface area: config editor crosses state, events, ui, theme, persist, and locales; a skim of modal lifecycle (open/save/cancel) and AppState integration will pay off.
• Update-check path touches workers/updates.rs, index/fetch.rs, and pacman_conf.rs; optional -Sl is now tied to active repo sections—worth validating on installs that only enable a subset of community repos.
• Log dedupe uses digests; confirm debug-level detail is still sufficient for troubleshooting without restoring INFO noise.

Breaking changes

None intended. Config editing goes through the existing theme/settings model; if any default or validation behavior changed, call it out during review.

Additional context

• Branch: feat/integrated-config-edit
• Prior planning doc updates under dev/ (e.g. integrated config editing plan) may accompany this work for historical context.