bug(tui): a locally created project is written to <path>/datatug/datatug-project.json but read from <path>/datatug-project.json, so it cannot be opened

Inizia da createLocalProject in apps/datatugapp/datatugui/dtproject/create_project_screen.go e confronta la gestione dei percorsi con LoadProjectFile in pkg/storage/filestore/store_loader.go. Controlla project_creator_test.go per verificare la struttura prevista al livello radice. Il lavoro è completato quando un progetto creato localmente può essere aperto e writer e reader concordano sulla posizione del file di progetto.

What happens

A project created locally from the TUI cannot be opened afterwards: the create flow writes the project file one directory deeper than the reader looks for it, so opening the project it just created fails with ErrProjectDoesNotExist.

Trigger

Writer — createLocalProject in apps/datatugapp/datatugui/dtproject/create_project_screen.go puts the file inside a datatug subdirectory:

datatugDir := filepath.Join(projectPath, "datatug")
// ...
configFilePath := filepath.Join(datatugDir, storage.ProjectSummaryFileName)

giving <projectPath>/datatug/datatug-project.json.

Reader — the same flow then calls openProject, which builds a store on projectRef.Path (that same projectPath):

store := filestore.NewProjectStore(projectRef.ID, projectRef.Path)

and datatug-core's filestore.LoadProjectFile joins the file name straight onto that path, with no datatug segment (pkg/storage/filestore/store_loader.go):

func LoadProjectFile(projPath string) (v datatug.ProjectFile, err error) {
	fileName := path.Join(projPath, storage.ProjectSummaryFileName)

So the reader opens <projectPath>/datatug-project.json and nothing is there.

Core is consistent with its reader, not with this writer: filestore's own saver writes saveJSONFile(s.projectPath, storage.ProjectSummaryFileName, projFile), and dtprojcreator.CreateProjectFiles writes it at the project root too — core's project_creator_test.go asserts expectedPath := path.Join(projPath, storage.ProjectSummaryFileName). The TUI's extra datatug directory is the odd one out.

Expected

createLocalProject should write datatug-project.json at the project root, the one place every reader in core looks — or, if the datatug subdirectory is deliberate, projectRef.Path should point at it so the two agree. They must not disagree silently.

Worth deciding at the same time whether the now-empty datatug directory should still be created at all.

Notes

Found in review of #259, which changed the directory this file is written into (it is now named after the project id rather than the title) but not the layout below it — the mismatch predates that PR and is not fixed there. Sibling pre-existing defects on the neighbouring GitHub create path: #260, #261, #262.