project-root inference in your code-health workflow

Hi! I'm the author of [pyscn](https://github.com/ludo-technologies/pyscn). I came across this repo and noticed you're running it in your weekly code-health workflow. Thanks for using it.

I also read the comment in `code-health.yml` about pyscn inferring the wrong project root and silently resolving only part of the imports, which inflates the score. That's a real problem on my side and I'd like to fix it rather than have you work around it. If you remember what the wrong root looked like (or a run where the sanity check fired), I'd appreciate the details. Same for having to run `analyze` twice to get both JSON and HTML; that should be a single invocation.

Separately, there's a GitHub App that runs the same analysis on a schedule and posts the reports for you, in case it saves some upkeep:
https://github.com/apps/polyscan-app

If anything else comes up, feel free to let me know.

Esamina il commento e l’invocazione attuale in code-health.yml, quindi raccogli i dettagli errati sulla radice del progetto oppure un’esecuzione in cui è stato attivato il sanity check. Il risultato richiesto è che pyscn risolva correttamente l’intero progetto e produca sia JSON sia HTML da una singola invocazione di analyze, ma la posizione e l’ambito dell’implementazione non sono stati identificati.

Scritto dal modello di indicizzazione a partire dal testo della issue.