datas-world/chatgpt-saved-session-to-markdown

AI Summary: This issue requests the creation of a `copilot-instructions.md` file to provide clear guidelines for Copilot usage. The document should emphasize that Copilot's work is not complete until `pre-commit` checks pass, strictly forbid weakening checks without approval, mandate deep root-cause analysis for test failures, and prefer COTS software with hyperlinked standards.

AI Summary: The current CI/CD pipeline runs linting, type checking, and tests sequentially within a single matrix job. This issue proposes refactoring the pipeline to separate these tasks. Linting and type checking, handled by `pre-commit`, should run in a dedicated job on the latest Python version (at least `3.13`), while tests should run across all supported Python versions (`3.12`, `3.13`) using a matrix job. Both the `pre-commit` and test jobs should execute in parallel.

AI Summary: The issue requests a change in the heading structure for generated Markdown. Currently, the Markdown starts with a third-level heading, but it should be revised to use a first-level heading for the dialogue name and a second-level heading to identify the speaker (user/assistant).

AI Summary: Tests are currently failing, and the root cause is unclear, potentially stemming from recent parallel changes in either the implementation or the tests themselves. The task involves diagnosing and fixing these failures professionally, adhering to best practices, and avoiding temporary workarounds. Additionally, there's a suggestion to migrate to a Commercial Off-the-Shelf test framework if feasible during this process.

AI Summary: The issue requests that all log messages which are specifically related to a file should include the full path of that file within the log output. This aims to provide clearer context for file-related operations in the logs.

AI Summary: A GitHub workflow is requested to automatically create future version milestones (e.g., 2.0.0, 1.3.0, 1.2.4 for version 1.2.3). This workflow should trigger manually, on tag creation, or on release/package upload, calculate potential next semantic versions, and then create corresponding GitHub issue milestones if they don't already exist.