feat(ios): show debug build distance from base

[saphid]

What changed

• Shows a compact Debug-only build badge on the native SwiftUI workspace home bar.
• Includes build/commit identity plus ahead/behind counts against an explicit base ref or public upstream default branch.
• Links only public GitHub commits and degrades cleanly when distance metadata is unavailable.
• Leaves Release/TestFlight, signing, bundle identities, and private hosts unchanged.

Fixes #5786.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at e55c7ffd1.
Reviewed head: 8e9e51c380acc74050db09d8d36b75869d5f7312.

UI evidence

Before:

Rebased feature evidence — build 5789, one ahead and zero behind (the follow-up changes only base-ref discovery):

Additional fallbacks:

Badge-to-commit interaction video

Verification

• T3CodeTests/DebugBuildMetadataTests: 4 passed, 0 failed.
• Full native gate: 222 tests in 28 suites passed.
• bash -n apps/swift-ios/Scripts/install-device.sh: passed.
• plutil -lint apps/swift-ios/Resources/Info.plist: OK.
• Debug and Release verify-only bundle identity checks: passed.
• Exact-head integrated iOS run exposed one semantic badge target describing build, commit, base ref, 1 ahead, and 0 behind.
• git diff --check: passed; rebase preserved the feature patch exactly.
• GPT-5.6 Sol high reviewed the feature and Cursor follow-up: no actionable findings; judged minimally scoped, Debug-isolated, and privacy-safe.
• Direct Claude Opus 5 high attempt exited 1 with HTTP 429 before review; no Claude findings are claimed.
• Prior MacroScope Git-scope finding is resolved. Cursor's upstream/HEAD finding is fixed with a verified local upstream/main fallback before origin/HEAD; an isolated Git fixture resolved upstream/main when the fork default pointed elsewhere. Current-head CI and review bots completed without further findings.

Checklist

• Small and focused
• Before/after and materially different UI states
• Interaction video
• Focused, script/plist/bundle, full native, and exact-head simulator checks
• No personal signing, identity, private-host, or Release changes
• Current fixed-head CI/MacroScope complete

Built with GPT-5.6 Sol in the Codex harness.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cc2ffcc4-6d17-42bc-a771-5318cf976c84

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 888296e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved 8e9e51c

This PR adds a debug-only badge showing git commit info and distance from base branch. All Swift code is wrapped in #if DEBUG and shell script changes only run for Debug configuration, so production builds are completely unaffected. The change is well-scoped and includes tests.

^{You can customize Macroscope's approvability policy. Learn more.}

Dismissing prior approval to re-evaluate 8e9e51c

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 8e9e51c; focused/full native, script, bundle, and integrated evidence are in the PR body. Current-head CI and MacroScope are green, and all review threads are resolved.

[saphid]

Dependency-safe rebuild is complete and preserved at saphid/swiftui-debug-distance-integration-stack (5230a96b4). Do not update this Theo-targeted PR yet: the tested head composes three still-open foundations in required order—#5790 versions → #5970 monotonic build/install → #5972 shared Debug chrome/predicate. Updating now would duplicate all three diffs.

The eventual unique PR commit is 5230a96b4 (9 files, +312/-2): truthful Debug source + owner-branch distance in Settings/About, no second Home badge, no second version formatter, no second Debug detector, and metadata appended to #5970’s build settings. It never silently compares against upstream/main; missing/shallow/no-upstream states stay honest. Release has no T3Git fields or rows.

Verification on exact integration stack: resolver shell suite; monotonic shell suite; focused Swift 4/4; full native 234 tests/31 suites; Debug build/run and semantic Settings proof; Release build with normal name/version and empty Debug metadata; git diff --check clean. Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:10014/debug-settings-about.mp4

Conflict classification: stale history/code plus feature-placement overlap (old second Home badge conflicts with #5972 visual ownership). Landing plan: merge #5790, #5970, #5972; rebase only 5230a96b4 onto refreshed Theo; then force-with-lease this PR. Opus review unavailable at confirmed 429 quota boundary; no verdict claimed.

[macroscopeapp]

🟡 Medium Scripts/install-device.sh:82

The dirty-status check runs git status --porcelain -- . scoped to the app directory, so modifications to tracked files outside apps/swift-ios (e.g. ../mobile/modules/t3-terminal/Vendor/libghostty/GhosttyKit.xcframework) are not detected. The build badge then reports a clean commit and enables a commit link even though the installed binary includes uncommitted changes from outside that path. Consider checking the full working tree (drop the -- . pathspec) so any dirty tracked input marks the commit as -dirty.

Suggested change

	[[ -n "$(git -C "${APP_DIR}" status --porcelain -- . 2>/dev/null)" ]]; then
	[[ -n "$(git -C "${APP_DIR}" status --porcelain 2>/dev/null)" ]]; then

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/swift-ios/Scripts/install-device.sh around line 82:

The dirty-status check runs `git status --porcelain -- .` scoped to the app directory, so modifications to tracked files outside `apps/swift-ios` (e.g. `../mobile/modules/t3-terminal/Vendor/libghostty/GhosttyKit.xcframework`) are not detected. The build badge then reports a clean commit and enables a commit link even though the installed binary includes uncommitted changes from outside that path. Consider checking the full working tree (drop the `-- .` pathspec) so any dirty tracked input marks the commit as `-dirty`.

[macroscopeapp]

🟠 High Scripts/install-device.sh:107

git fetch --quiet upstream runs unconditionally on every Debug install, so when the upstream remote requires interactive SSH authentication or the network stalls, the script hangs before xcodebuild ever starts. The fetch is unnecessary when T3_SWIFT_BASE_REF already resolves to a local commit, and git fetch has no timeout or non-interactive SSH settings. Consider skipping the fetch when the base ref is already resolvable locally, or guard it with a timeout and GIT_SSH_COMMAND set to BatchMode=yes.

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/swift-ios/Scripts/install-device.sh around line 107:

`git fetch --quiet upstream` runs unconditionally on every Debug install, so when the `upstream` remote requires interactive SSH authentication or the network stalls, the script hangs before `xcodebuild` ever starts. The fetch is unnecessary when `T3_SWIFT_BASE_REF` already resolves to a local commit, and `git fetch` has no timeout or non-interactive SSH settings. Consider skipping the fetch when the base ref is already resolvable locally, or guard it with a timeout and `GIT_SSH_COMMAND` set to `BatchMode=yes`.

[saphid]

Exact final-head simulator proof (811a2a7): the Debug badge remains legible at phone width and exposes the full build/base-distance accessibility label.

Focused DebugBuildMetadataTests (5/5) and shell syntax passed. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.