Clarify PR workflow limitations in comment response

[Copilot]

User requested opening a new PR to apply linting fixes from review comments, but the agent cannot create new PRs from within the current PR context.

Changes

• Added reply to comment #3468467125 clarifying that new PRs cannot be opened
• Offered alternative: apply linting fixes directly to current branch
• Listed specific fixes available: type annotations, hardcoded constants, import sorting, union syntax, import placement, and logger usage

Context

The review thread identified 6 linting issues across multiple files that can be auto-fixed with ruff check --fix or addressed manually. Rather than opening a new PR (which is outside the agent's capabilities), these can be applied directly to this branch.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Neiland85]

Closing this PR. After the 2025 refactor, these changes are fully superseded and incompatible with the new system design.

Keeping it open offers no benefit and only adds unnecessary clutter to the repository.

[Neiland85]

Closing this PR. The changes no longer align with the updated architecture and dependency model introduced in the December 2025 refactor.

This contribution is now obsolete and would add noise rather than value to the current codebase.

[Neiland85]

Closing this PR. It is now outdated after the full system refactor completed in December 2025.

The project has been unified under a new architecture, updated dependencies, and a consistent configuration model.

Keeping this PR open would introduce inconsistencies and no longer provides technical value.

[Neiland85]

This PR has been overtaken by the 2025 architecture refactor.
Closing it with respect, but it is no longer part of the living codebase.

[Neiland85]

This PR has been overtaken by the 2025 architecture refactor.
Closing it with respect, but it is no longer part of the living codebase.

[Neiland85]

Closing this PR. After the 2025 refactor, these changes are fully superseded and incompatible with the new system design.

Keeping it open offers no benefit and only adds unnecessary clutter to the repository.

[Neiland85]

Closing this PR. The changes no longer align with the updated architecture and dependency model introduced in the December 2025 refactor.

This contribution is now obsolete and would add noise rather than value to the current codebase.