fix(repo-mode): reuse canonical cached project slug (#2212)

[time-attack]

Summary

gstack caches a project’s slug from the first time it’s seen (often the local folder name). If you add a GitHub origin later, gstack-repo-mode used to ignore that cache and invent a new slug from the remote URL. That wrote state into a second “twin” project folder, so history could look split or lost and you’d get duplicate untracked project dirs.

This fix makes gstack-repo-mode reuse the canonical cached slug from gstack-slug. Repos with no remote still return REPO_MODE=unknown. It runs from the git root so the PWD-keyed cache matches.

Fixes #2212

Tests

We built local Git workspaces that mimic real public repos people use with gstack, reproduced the twin-slug bug in each, then verified the fix:

1. facebook/react — local folder react-local-history, cache slug first, then add https://github.com/facebook/react.git as origin. Before: wrote under facebook-react. After: keeps react-local-history and no twin dir.
2. vercel/next.js — same flow with next-local-history → https://github.com/vercel/next.js.git.
3. kubernetes/kubernetes — same flow with kubernetes-local-history → https://github.com/kubernetes/kubernetes.git.

Additional coverage:

• No-origin repo still returns REPO_MODE=unknown and creates no project dir
• Running from a subdirectory still writes under the git-root cached slug
• Unusual origin URLs (spaces/parens) stay sanitized before mkdir

All 6 cases in test/gstack-repo-mode.test.ts pass via bun test test/gstack-repo-mode.test.ts.

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

[time-attack]

@16francej

[marcusLewi]

Unsubscribe

…

On Tue, Jul 14, 2026, 4:36 PM Joshua France ***@***.***> wrote: Merged #2218 <#2218> into main. — Reply to this email directly, view it on GitHub <#2218?email_source=notifications&email_token=BQ7R3F3R7LDU3DSFHVWVAEL5E27ZNA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZZHA4TKMZYHAYTDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#event-27989538811>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQ7R3F6AY7C4SZQIOT3ATUL5E27ZNAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNZZGI3DIMRVHE5US43TOVSTWNBYGU3DANRVGU4DLILWAI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>