Unsure what to do about the facade path for moved repos

[MoralCode]

When we detect a repo has moved (301), we create a new dict of repo table data with the repo_path set to None

CollectOSS/collectoss/tasks/github/detect_move/core.py

Line 112 in 115b4ee

'repo_path': None,

This line was last touched in 34d5c7d

We do this without resetting the facade collection state such that it will be cloned fresh next run, which essentially breaks collection/puts facade in a weird state.

[MoralCode]

This is being caught by the coalesce behavior in bulk_insert_dicts:

CollectOSS/collectoss/application/db/lib.py

Line 339 in 115b4ee

setDict[key] = func.coalesce(getattr(stmnt.excluded, key), existing_col)

In our DB all the facade repos with NULL paths also have a description set indicating they ran into a 404 error at some point, so thats a different code path.

All this data predates November 11, 2025 as well. October was the last time the coalesce behavior was touched.

That still leaves open the question of why (or even if) we trying to clear the repo_path when a move is detected.

@IsaacMilarky do you have any historical context on why we are setting repo_path to None here and what the intent was (i.e. should facade be put into a state where it will clone the new repo fresh?