bug(dtgithub): projectCreator never receives repoOwner, repoName or branch, so every GitHub call targets an empty repo

Start in pkg/dtgithub/github_repo_projects_store.go by reading NewRepoProjectsStore, GithubRepoProjectsStore.CreateNewProject, and newProjectCreator. Trace the parsed owner, repository, and branch into projectCreator, then verify the GitHub calls no longer use empty values and that the resulting repository, ref, README title, and errors use those inputs.

What happens

Every GitHub API call projectCreator makes is addressed to an empty owner and an empty repository name, and it always works on the branch "".

Trigger

newProjectCreator populates only two of the six fields (pkg/dtgithub/github_repo_projects_store.go):

func newProjectCreator(ghClient *github.Client, report datatug.StatusReporter) (creator *projectCreator) {
	return &projectCreator{
		client: ghClient,
		report: report,
	}
}

repoOwner, repoName, repo and branch are left at their zero values, and nothing assigns them afterwards. Meanwhile GithubRepoProjectsStore.CreateNewProject parses exactly those first two out of its projectID and then throws them away:

repoOwner, repoName, projectDir := ids[0], ids[1], path.Join(ids[2:]...)
_, _, _ = repoOwner, repoName, title

So createRepo calls c.client.Repositories.Get(ctx, "", ""), CreateProject asks for the ref heads/ on ""/"", addDatatugSectionToRootReadmeFile writes # as a README title, and the error messages report failed to create GitHub repository '/'.

branch is a second, separate loss: NewRepoProjectsStore defaults it to "main" and stores it on GithubRepoProjectsStore, but the creator it builds never receives it.

Expected

newProjectCreator should take the owner, repo and branch the store already parsed and hold them, so the parsed values are actually used.

Notes

Found while adapting the CLI to datatug-core v0.39.0's caller-supplied project id (#259) and deliberately not fixed there — it is a pre-existing gap in an unfinished code path, not a consequence of the id change. In practice the panic in the sibling issue fires first, so this is only reachable once that is fixed.