Skip to content

fix: centralize TUI runtime logs - #63

Merged
shaohaozhi286 merged 2 commits into
masterfrom
fix/centralize-tui-logs
Sep 19, 2026
Merged

shaohaozhi286 merged 2 commits into
masterfrom
fix/centralize-tui-logs

Conversation

@LIUXIN557

Copy link
Copy Markdown
Collaborator

Summary

  • route TUI runtime logs to the effective ACECode data directory with daily rotation
  • route FTXUI input tracing to a separate centralized daily log and update the FTXUI submodule reference
  • keep TUI and Desktop feedback surface logs isolated while retaining daemon and recent upgrade diagnostics

Verification

  • configured Windows Debug build with the ests vcpkg feature
  • rebuilt FTXUI overlay at port version 7 and built �cecode plus �cecode_unit_tests
  • ran focused logger and feedback tests
  • verified the rebuilt FTXUI library contains the centralized trace-path contract and no legacy relative �cecode.log string
  • ran git diff --check

Manual follow-up

  • perform the documented trace-enabled interactive worktree check: mouse or selection events should write ui-input-trace-YYYY-MM-DD.log in the data directory and must not modify a worktree �cecode.log.

@shaohaozhi286
shaohaozhi286 merged commit 70f6d6b into master Sep 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants