[dizys]

New project still created repositories under $T3CODE_HOME/projects, even after the workspace defaults for browsing and cloning were added. This applies a local native T3 source patch so the client advertises and creates projects in T3_WORKSPACE. T3CODE_PROJECTS_DIR can override that destination; existing projects retain their paths.

• Keep container-specific native changes in this repository's patch registry. Build from an exact upstream release tag, retain its matching client and native assets, and record the source commit, upstream checksum and patch fingerprint.
• Build and test AMD64 and ARM64 before publishing native OCI artifacts in the existing public GHCR package. The image and hourly Stable/Nightly updater consume the same patched distribution. Compilation keeps that tag's checked-in public Connect defaults, with an explicit allowlist and build-generation fingerprint. Compiler tools stay outside the final image.
• Verify anonymous downloads through the index, platform manifest and archive digest/size chain. Keep patched cache variants separate from original binaries, including same-version integration trials, SQLite recovery and device validation.
• Show integration updates explicitly in Updates, retain the exact version/channel during a same-version update, and disable actions while submission waits. Retained error notifications cannot cover confirmation controls.

An image recreate retains an explicitly selected native runtime. Applying its integration goes through the normal update confirmation and trial. The native workflow also supports building exact older pins. The maintenance guide documents this lifecycle and the repository's policy for local T3 patches.

Validation:

• All 942 repository tests pass, plus shell checks, native script syntax, workflow actionlint and the existing static UI audit.
• Compiled Stable 0.1.2 and Nightly 0.1.3-nightly.20261026.3717. Real native API and browser flows create repositories in the workspace, exercise name collisions, preserve existing projects and verify the native Connect JSON command before publishing. Browser checks cover desktop/phone in both themes.
• Real same-version integration trials preserve the original session, environment identity, native version and Connect/relay discovery on both builds. Regression tests cover failed trials, database recovery, pinned versions and patch-cache cleanup.
• Real ORAS publication and discovery pass against an offline OCI layout, including both architectures, checksum rejection, immutable tags and monotonic channel aliases.
• The Updates browser audit passes all 12 layouts across both themes, including long Nightly versions, failed submissions, retries, delayed requests and duplicate-submit guards.

Full Docker image builds and smoke tests run in PR CI; Docker is unavailable in this local container.

Native New project, light	Native New project, dark

Integration update, light	Integration update, dark

Phone verification in both themes

Native New project, light	Native New project, dark

Integration update, light	Integration update, dark