Clean up deprecated files, reorganize docs, fix filelock CVE

[Copilot]

Repository housekeeping: remove obsolete monorepo artifacts after workspace migration, consolidate documentation, and patch filelock TOCTOU vulnerability.

Changes

• Removed deprecated files

  • README.old.md, Dockerfile.old - leftover from pre-workspace structure
  • src/ directory - monorepo code superseded by packages/ workspace
  • requirements.txt - autogenerated file superseded by uv.lock

• Documentation reorganization

  • Created docs/ directory with lowercase naming: implementation-summary.md, package-structure.md
  • Updated internal references to new paths

• Security patch

  • Pinned filelock>=3.20.1 in pyproject.toml (CVE fix for symlink attack during lock creation)
  • Updated uv.lock: 3.18.0 → 3.20.1

• Configuration cleanup

  • Removed src = ["src"] from ruff config
  • Removed obsolete known-first-party imports
  • Removed requirements-txt-fixer and uv-export pre-commit hooks

Original prompt

---

This section details on the original issue you should resolve

<issue_title>house keeping</issue_title>
<issue_description>The repository needs some house keeping:

• unused files that should be deleted: README.old.md, Dockerfile.old and all the files within src/ as the original monorepo has been split in a uv workspace
• implementation_summary.md and PACKAGE_STRUCTURE.md should be maintained as docs in a docs/ folder, with lowercase naming and easy to read for both human engineers as well as AI coding assistants
• filelock should be forced with version >=3.20.1 . It is a sub-dependecy of other stuff, but currently raising the moderate security concern: filelock has a TOCTOU race condition which allows symlink attacks during lock file creation </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes house keeping #13

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[DiTo97]

@copilot works great. Is requirements.txt still used? Otherwise, I'd remove it, would be one more thing to maintain.

[Copilot]

@copilot works great. Is requirements.txt still used? Otherwise, I'd remove it, would be one more thing to maintain.

You're correct—requirements.txt was no longer used. It was being autogenerated by the uv-export pre-commit hook, but since the project uses uv with pyproject.toml and uv.lock, and the Dockerfile uses uv sync directly, it was redundant.

Removed in c3a2fc4 along with the requirements-txt-fixer and uv-export pre-commit hooks.

[DiTo97]

LGTM