Scripts directory

[KonstantinPotekaev]

I’d like to raise a concern about the current state of the scripts directory. There are two possible suggestions to solve it:

1. Please consider renaming the scripts directory to something more specific.

2. Alternatively, configure the packaging so that scripts does not get treated as a top-level library when the package is installed.

Right now, because scripts is installed as a separate top-level package, it conflicts with user projects that also have a scripts/ directory — making it nearly impossible to structure custom projects without import collisions.

This causes a lot of frustration and breaks local development workflows. Please consider making this small change — it would really help the community.