[dizys]

T3's native project browser and clone flow start in the home directory even when the image's repositories live under T3_WORKSPACE. Seed the existing addProjectBaseDirectory preference before the server and provider integration start, so GitHub and Git URL clones initially target the workspace.

Existing custom preferences and explicit clone destinations take precedence. Later preference changes, including clearing the field, survive restarts. A changed T3_WORKSPACE follows only the image-owned default. Existing projects stay where they are; malformed settings/ownership records are preserved. The scratch development console now uses the same initialization, and the image smoke suite asserts the stored native preference.

T3’s New project action continues to use $T3CODE_HOME/projects. This PR covers the native folder browser and clone flows.

Validation:

• 62 focused defaults/runtime/provider integration tests passed; the 13 default-preference tests also passed after the final ownership-validation adjustment. Shell and JavaScript syntax checks and git diff --check passed.
• Used the real 0.1.3-nightly.20261024.3617 in a disposable home. Cloned octocat/Hello-World into its configured workspace, then cloned again to an explicit alternate directory; checked both Git remotes and files on disk.
• Also checked the clone picker against the bundled stable 0.1.2 runtime. Captured that native picker before/after, in dark mode and at 390px. The screenshot repository name is synthetic; no create/clone request was sent for it.
• Docker is unavailable locally; image builds and smoke checks run in CI. Validation used disposable homes.

Before	Workspace default

Dark and phone