Trace a desktop app's Export feature from its packaged bytecode, with no source code

# Trace how one feature of a desktop app works, from its packaged files only The `*.pyz` file in this folder is a small desktop app, built only for this test, shipped the way it would reach a user: a zipped Python application containing compiled bytecode (`.pyc`) and no source code. It runs on the Python 3.13 installed here. `data/project.json` is a project the user has open, and `settings.ini` is their settings file. You may unpack, disassemble, import and run the app's code however you like, but don't modify the `.pyz`. There is no display, so the window itself won't open. Trace what happens when the user picks File > Export... in the app's window and write `out/trace.json`: - `call_chain`: List the call chain from the menu handler behind File > Export... down to the function that calls `open()` to write the export. Use qualified names, `<package>.<module>.<Class>.<method>` for methods and `<package>.<module>.<function>` for plain functions, in call order, starting with the handler; each entry calls the next. - `output_path`: Give the full path of the finished export file (after any temporary file is renamed) for this project and settings when the user's home directory is `/home/user` and today is 2026-10-21. - `delimiter` and `header`: Give the field delimiter and the header labels in order. `header` is a list of strings. Write `out/predicted_export.txt` with exactly the bytes the export would write for this project and these settings on 2026-10-21 (same line endings, no extra trailing newline). ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.