Add reproducible session export bundles for bug reports and contributor debugging #44
Description
Summary
When something goes wrong in OAgent, maintainers currently have to reconstruct the state from screenshots, logs, and partial descriptions. The app already persists rich session metadata, tool-call history, and environment-sensitive runtime details. A reproducible export bundle would let users attach a sanitized session package for debugging without sharing their whole workspace.
Proposed scope
The bundle should focus on reproducibility, not full archival. It should capture enough information to help maintainers replay or inspect what happened: session metadata, provider/runtime settings, message history, tool-call summaries, and relevant logs, while explicitly excluding secrets and raw private project files.
Acceptance Criteria
- Add a user-facing export action for a single session or support incident.
- Bundle enough metadata to reproduce runtime context without copying arbitrary workspace contents.
- Exclude secrets, API keys, auth tokens, and raw file contents unless the user explicitly opts in.
- Produce an artifact that is easy to attach to a GitHub issue or discussion.
- Document the format and any privacy boundaries clearly in the UI or support docs.