feat(swift-ios): mark Dev and Test builds in the home title

[saphid]

1. Observed problem and reproduction

Install Dev, Test, and ordinary SwiftUI builds, then open Home. Before this change, the environments button always read T3 Code, so Home did not distinguish Dev from Test.

2. Cause

The SwiftUI client had no explicit build-channel presentation model. Inferring a channel from bundle identifiers would couple upstream UI to one fork and could mislabel unknown builds.

3. Change and ownership boundary

T3_BUILD_CHANNEL supplied by an xcodebuild argument or local xcconfig expands into the generic T3BuildChannel Info.plist value. Supported values render T3 Code Dev in the existing number token or T3 Code Test in the existing keyword token. The environments button uses the same title in its accessibility label.

The change stays at the SwiftUI Home presentation boundary. It adds one small value model, updates the existing environments button, expands one plist value, documents the setting, and adds focused tests. It does not add a project default or forward this contributor-owned overlay through install-device.sh.

4. Intentionally unchanged

Missing, empty, unexpanded, upstream, and unknown declarations preserve the ordinary T3 Code title. Offline and reconnecting environment status titles remain higher priority.

Bundle identifiers, installed app names, signing and publication workflows, server behavior, providers, contracts, connection modes, web, desktop, and React Native mobile are unchanged. No adjacent cleanup is included.

5. Affected surfaces

• Client and entry point: SwiftUI mobile, Home environments button only.
• Platform: iOS and iPadOS presentation code.
• Accessibility: T3 Code Dev. Manage environments, T3 Code Test. Manage environments, or the unchanged ordinary label.
• Covered declarations: dev, test, upstream, missing, empty, whitespace, unexpanded, mixed-case, and unknown values.

6. Validation on current head

Head 0bb6321643348ddba4efa68bd385c03961544398 targets 22b22f1463b83963d851bd0574a36a20f224a28d on t3code/rebuild-mobile-app-swift.

• PersonalBuildChannelTests: 7 executed, 7 passed, 0 failed.
• xcrun swiftc -parse apps/swift-ios/Features/Workspace/PersonalBuildChannel.swift apps/swift-ios/Features/Workspace/WorkspaceView.swift: exit 0.
• plutil -lint apps/swift-ios/Resources/Info.plist: exit 0, OK.
• git diff --check against the target: exit 0.
• Fresh ordinary, Dev, and Test simulator builds each embed the current head in T3GitCommit and pass codesign --verify --deep --strict.
• The three preserved app variants have the same T3Code.debug.dylib SHA-256, 6f0d7897114811bf685add8fdb7a496fbb96deddb817046b7b74626756af64e2. Only the declared build channel differs.
• Integrated proof ran on the leased iPhone 16 Pro simulator with iOS 26.5 against a disposable loopback environment. Dark and light semantic snapshots matched every visible title and accessibility label.
• The dark and light video packets each contain three real project-filter taps. Packet validation passed all three actions and sealed the clean and annotated derivatives.
• Direct read-only Claude Opus 5 high review of the frozen final diff exited 0 with no actionable findings.

An earlier focused-test attempt hit ENOSPC before any test ran. The retained retry on the same suite passed 7/7 after disposable build data was cleared.

7. Risks and limitations

• The marker depends on the external build or signing overlay supplying T3_BUILD_CHANNEL. Ordinary upstream builds intentionally supply nothing and stay unmarked.
• Unknown values intentionally fall back to the ordinary title.
• The title is the changed behavior. The videos tap the unchanged project filter to prove the screen is live and to bind each state to the repository timeline workflow.
• No unrelated SwiftUI flow was retested.

8. UI evidence

All media below comes from fresh builds of current head 0bb632164. The fixture contains one sanitized project and no threads. Dark mode is first, tight title crops are primary, and full-window context is collapsed.

Dark mode

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean dark-mode MP4 | Annotated dark-mode MP4

Full-window context, dark mode

Ordinary

Dev

Test

Light mode evidence

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean light-mode MP4 | Annotated light-mode MP4

Full-window context, light mode

Ordinary

Dev

Test

This section supersedes the earlier screenshot-only proof in the PR conversation.

9. Owning issue and target

Owning work item: saphid/t3code-personal#121. Authorized proof batch: saphid/t3code-personal#150. This PR targets t3code/rebuild-mobile-app-swift.

Vouched handoff checklist

1. Pass. One observable Home-title behavior, five related files.
2. Pass. The problem, cause, change, and non-goals match current head.
3. Pass. The existing Home button, plist expansion, and design tokens are reused.
4. Pass. Affected and unchanged clients, platforms, contracts, providers, and connections are named.
5. Pass. The focused native suite passed 7/7.
6. Pass. Parse, plist, diff, exact-head build, and strict signature checks passed.
7. Pass. Ordinary, Dev, and Test runtime states were exercised on a leased simulator.
8. Pass. Dark-first tight crops, collapsed full-window context, collapsed light evidence, and GIFs are embedded above; clean and annotated MP4s are linked above.
9. Pass. Risks, the recovered ENOSPC attempt, and untested paths are stated plainly.
10. Pass. The branch contains no unrelated cleanup or PR-only media files.
11. Pass. The description and proof match 0bb632164; the final independent review inspected that commit.
12. Pass. Scope, proof, and expected behavior are ready for maintainer review.

Overall handoff: PASS, ready for maintainer review.

Checklist

• This PR is small and focused
• I explained what changed and why
• I embedded dark-first, phone-readable current-head screenshots with full-window and light context collapsed
• I embedded current-head comparison and action GIFs and linked clean and annotated MP4s
• I verified every anonymous screenshot and GIF URL renders in the live PR body, and every MP4 URL downloads byte-identically with byte-range support

Implementation: GPT-5.6 Sol high in the Codex harness. Independent review: Claude Opus 5 high, read-only, exit 0, no actionable findings.

Upstream delivery

Delivery: direct
Validated against Theo commit: c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0
Depends on: none
Merge order: this PR only
Validation status: none of this PR's five changed paths overlaps Theo's new commit; a merge-tree simulation against the live target exited 0. Current head 0bb6321643348ddba4efa68bd385c03961544398 has green required CI, 7/7 focused native tests, exact-head signed Simulator proof, a successful direct Claude Opus 5 high review with no actionable findings, successful CodeRabbit/Cursor/Macroscope correctness reviews, and no unresolved threads. All 20 linked proof assets returned HTTP 206 byte ranges on 2026-09-01.
Dark mode evidence: yes
Clean screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/dev-dark-tight.png
Annotated screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-action.gif
Clean video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-clean.mp4
Annotated video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-annotated.mp4

[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: ca7d1bf3-a4ae-4855-9312-9a5f68d86cb7

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

---

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new configuration-controlled Dev/Test marker to the user-facing Home title while leaving ordinary builds and other runtime flows unchanged. The behavior is small and tested, but its core integration changes an existing shared WorkspaceView, so the bounded additive exception does not fully apply.

^{You can add or adjust custom eligibility rules. Learn more.}

[saphid]

Evidence refreshed on current head

The earlier 69523545 snapshot is superseded. Current-head proof for 0bb6321643348ddba4efa68bd385c03961544398 is now in the PR description: dark-first tight Ordinary/Dev/Test crops, comparison and action GIFs, collapsed full-window and light-mode context, plus clean and annotated MP4s.

Permanent public media: https://github.com/saphid/t3code/releases/tag/pr-7453-evidence-0bb632164-20260830

Dismissing prior approval to re-evaluate 983164b

[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 983164b024afda7537266604694c0bd7de0a1864. Configure here.}

Dismissing prior approval to re-evaluate 3bcdfec

Dismissing prior approval to re-evaluate 6737462

[saphid]

@t3dotgg Ready for human review. This is classified direct against live SwiftUI target c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0: none of the five changed paths overlaps Theo's new commit, and the merge-tree simulation is clean. Head 0bb632164 has green required CI, 7/7 focused native tests, signed exact-head Simulator proof, no unresolved review threads, and successful CodeRabbit, Cursor, Macroscope correctness, and direct Claude Opus 5 high reviews. All 20 proof assets are reachable; the PR body now records the delivery block and exact media.

[saphid]

1. Observed problem and reproduction

Install Dev, Test, and ordinary SwiftUI builds, then open Home. Before this change, the environments button always read T3 Code, so Home did not distinguish Dev from Test.

2. Cause

The SwiftUI client had no explicit build-channel presentation model. Inferring a channel from bundle identifiers would couple upstream UI to one fork and could mislabel unknown builds.

3. Change and ownership boundary

T3_BUILD_CHANNEL supplied by an xcodebuild argument or local xcconfig expands into the generic T3BuildChannel Info.plist value. Supported values render T3 Code Dev in the existing number token or T3 Code Test in the existing keyword token. The environments button uses the same title in its accessibility label.

The change stays at the SwiftUI Home presentation boundary. It adds one small value model, updates the existing environments button, expands one plist value, documents the setting, and adds focused tests. It does not add a project default or forward this contributor-owned overlay through install-device.sh.

4. Intentionally unchanged

Missing, empty, unexpanded, upstream, and unknown declarations preserve the ordinary T3 Code title. Offline and reconnecting environment status titles remain higher priority.

Bundle identifiers, installed app names, signing and publication workflows, server behavior, providers, contracts, connection modes, web, desktop, and React Native mobile are unchanged. No adjacent cleanup is included.

5. Affected surfaces

• Client and entry point: SwiftUI mobile, Home environments button only.
• Platform: iOS and iPadOS presentation code.
• Accessibility: T3 Code Dev. Manage environments, T3 Code Test. Manage environments, or the unchanged ordinary label.
• Covered declarations: dev, test, upstream, missing, empty, whitespace, unexpanded, mixed-case, and unknown values.

6. Validation on current head

Head 0bb6321643348ddba4efa68bd385c03961544398 targets 22b22f1463b83963d851bd0574a36a20f224a28d on t3code/rebuild-mobile-app-swift.

• PersonalBuildChannelTests: 7 executed, 7 passed, 0 failed.
• xcrun swiftc -parse apps/swift-ios/Features/Workspace/PersonalBuildChannel.swift apps/swift-ios/Features/Workspace/WorkspaceView.swift: exit 0.
• plutil -lint apps/swift-ios/Resources/Info.plist: exit 0, OK.
• git diff --check against the target: exit 0.
• Fresh ordinary, Dev, and Test simulator builds each embed the current head in T3GitCommit and pass codesign --verify --deep --strict.
• The three preserved app variants have the same T3Code.debug.dylib SHA-256, 6f0d7897114811bf685add8fdb7a496fbb96deddb817046b7b74626756af64e2. Only the declared build channel differs.
• Integrated proof ran on the leased iPhone 16 Pro simulator with iOS 26.5 against a disposable loopback environment. Dark and light semantic snapshots matched every visible title and accessibility label.
• The dark and light video packets each contain three real project-filter taps. Packet validation passed all three actions and sealed the clean and annotated derivatives.
• Direct read-only Claude Opus 5 high review of the frozen final diff exited 0 with no actionable findings.

An earlier focused-test attempt hit ENOSPC before any test ran. The retained retry on the same suite passed 7/7 after disposable build data was cleared.

7. Risks and limitations

• The marker depends on the external build or signing overlay supplying T3_BUILD_CHANNEL. Ordinary upstream builds intentionally supply nothing and stay unmarked.
• Unknown values intentionally fall back to the ordinary title.
• The title is the changed behavior. The videos tap the unchanged project filter to prove the screen is live and to bind each state to the repository timeline workflow.
• No unrelated SwiftUI flow was retested.

8. UI evidence

All media below comes from fresh builds of current head 0bb632164. The fixture contains one sanitized project and no threads. Dark mode is first, tight title crops are primary, and full-window context is collapsed.

Dark mode

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean dark-mode MP4 | Annotated dark-mode MP4

Full-window context, dark mode

Ordinary

Dev

Test

Light mode evidence

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean light-mode MP4 | Annotated light-mode MP4

Full-window context, light mode

Ordinary

Dev

Test

This section supersedes the earlier screenshot-only proof in the PR conversation.

9. Owning issue and target

Owning work item: saphid/t3code-personal#121. Authorized proof batch: saphid/t3code-personal#150. This PR targets t3code/rebuild-mobile-app-swift.

Vouched handoff checklist

1. Pass. One observable Home-title behavior, five related files.
2. Pass. The problem, cause, change, and non-goals match current head.
3. Pass. The existing Home button, plist expansion, and design tokens are reused.
4. Pass. Affected and unchanged clients, platforms, contracts, providers, and connections are named.
5. Pass. The focused native suite passed 7/7.
6. Pass. Parse, plist, diff, exact-head build, and strict signature checks passed.
7. Pass. Ordinary, Dev, and Test runtime states were exercised on a leased simulator.
8. Pass. Dark-first tight crops, collapsed full-window context, collapsed light evidence, and GIFs are embedded above; clean and annotated MP4s are linked above.
9. Pass. Risks, the recovered ENOSPC attempt, and untested paths are stated plainly.
10. Pass. The branch contains no unrelated cleanup or PR-only media files.
11. Pass. The description and proof match 0bb632164; the final independent review inspected that commit.
12. Pass. Scope, proof, and expected behavior are ready for maintainer review.

Overall handoff: PASS, ready for maintainer review.

Checklist

• This PR is small and focused
• I explained what changed and why
• I embedded dark-first, phone-readable current-head screenshots with full-window and light context collapsed
• I embedded current-head comparison and action GIFs and linked clean and annotated MP4s
• I verified every anonymous screenshot and GIF URL renders in the live PR body, and every MP4 URL downloads byte-identically with byte-range support

Implementation: GPT-5.6 Sol high in the Codex harness. Independent review: Claude Opus 5 high, read-only, exit 0, no actionable findings.

Upstream delivery

Delivery: direct
Validated against Theo commit: c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0
Depends on: none
Merge order: this PR only
Validation status: none of this PR's five changed paths overlaps Theo's new commit; a merge-tree simulation against the live target exited 0. Current head 0bb6321643348ddba4efa68bd385c03961544398 has green required CI, 7/7 focused native tests, exact-head signed Simulator proof, a successful direct Claude Opus 5 high review with no actionable findings, successful CodeRabbit/Cursor/Macroscope correctness reviews, and no unresolved threads. All 20 linked proof assets returned HTTP 206 byte ranges on 2026-09-01.
Dark mode evidence: yes
Clean screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/dev-dark-tight.png
Annotated screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-action.gif
Clean video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-clean.mp4
Annotated video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-annotated.mp4

[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: ca7d1bf3-a4ae-4855-9312-9a5f68d86cb7

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

---

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new configuration-controlled Dev/Test marker to the user-facing Home title while leaving ordinary builds and other runtime flows unchanged. The behavior is small and tested, but its core integration changes an existing shared WorkspaceView, so the bounded additive exception does not fully apply.

^{You can add or adjust custom eligibility rules. Learn more.}

[saphid]

Evidence refreshed on current head

The earlier 69523545 snapshot is superseded. Current-head proof for 0bb6321643348ddba4efa68bd385c03961544398 is now in the PR description: dark-first tight Ordinary/Dev/Test crops, comparison and action GIFs, collapsed full-window and light-mode context, plus clean and annotated MP4s.

Permanent public media: https://github.com/saphid/t3code/releases/tag/pr-7453-evidence-0bb632164-20260830

Dismissing prior approval to re-evaluate 983164b

[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 983164b024afda7537266604694c0bd7de0a1864. Configure here.}

Dismissing prior approval to re-evaluate 3bcdfec

Dismissing prior approval to re-evaluate 6737462

[saphid]

@t3dotgg Ready for human review. This is classified direct against live SwiftUI target c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0: none of the five changed paths overlaps Theo's new commit, and the merge-tree simulation is clean. Head 0bb632164 has green required CI, 7/7 focused native tests, signed exact-head Simulator proof, no unresolved review threads, and successful CodeRabbit, Cursor, Macroscope correctness, and direct Claude Opus 5 high reviews. All 20 proof assets are reachable; the PR body now records the delivery block and exact media.

[saphid]

1. Observed problem and reproduction

Install Dev, Test, and ordinary SwiftUI builds, then open Home. Before this change, the environments button always read T3 Code, so Home did not distinguish Dev from Test.

2. Cause

The SwiftUI client had no explicit build-channel presentation model. Inferring a channel from bundle identifiers would couple upstream UI to one fork and could mislabel unknown builds.

3. Change and ownership boundary

T3_BUILD_CHANNEL supplied by an xcodebuild argument or local xcconfig expands into the generic T3BuildChannel Info.plist value. Supported values render T3 Code Dev in the existing number token or T3 Code Test in the existing keyword token. The environments button uses the same title in its accessibility label.

The change stays at the SwiftUI Home presentation boundary. It adds one small value model, updates the existing environments button, expands one plist value, documents the setting, and adds focused tests. It does not add a project default or forward this contributor-owned overlay through install-device.sh.

4. Intentionally unchanged

Missing, empty, unexpanded, upstream, and unknown declarations preserve the ordinary T3 Code title. Offline and reconnecting environment status titles remain higher priority.

Bundle identifiers, installed app names, signing and publication workflows, server behavior, providers, contracts, connection modes, web, desktop, and React Native mobile are unchanged. No adjacent cleanup is included.

5. Affected surfaces

• Client and entry point: SwiftUI mobile, Home environments button only.
• Platform: iOS and iPadOS presentation code.
• Accessibility: T3 Code Dev. Manage environments, T3 Code Test. Manage environments, or the unchanged ordinary label.
• Covered declarations: dev, test, upstream, missing, empty, whitespace, unexpanded, mixed-case, and unknown values.

6. Validation on current head

Head 0bb6321643348ddba4efa68bd385c03961544398 targets 22b22f1463b83963d851bd0574a36a20f224a28d on t3code/rebuild-mobile-app-swift.

• PersonalBuildChannelTests: 7 executed, 7 passed, 0 failed.
• xcrun swiftc -parse apps/swift-ios/Features/Workspace/PersonalBuildChannel.swift apps/swift-ios/Features/Workspace/WorkspaceView.swift: exit 0.
• plutil -lint apps/swift-ios/Resources/Info.plist: exit 0, OK.
• git diff --check against the target: exit 0.
• Fresh ordinary, Dev, and Test simulator builds each embed the current head in T3GitCommit and pass codesign --verify --deep --strict.
• The three preserved app variants have the same T3Code.debug.dylib SHA-256, 6f0d7897114811bf685add8fdb7a496fbb96deddb817046b7b74626756af64e2. Only the declared build channel differs.
• Integrated proof ran on the leased iPhone 16 Pro simulator with iOS 26.5 against a disposable loopback environment. Dark and light semantic snapshots matched every visible title and accessibility label.
• The dark and light video packets each contain three real project-filter taps. Packet validation passed all three actions and sealed the clean and annotated derivatives.
• Direct read-only Claude Opus 5 high review of the frozen final diff exited 0 with no actionable findings.

An earlier focused-test attempt hit ENOSPC before any test ran. The retained retry on the same suite passed 7/7 after disposable build data was cleared.

7. Risks and limitations

• The marker depends on the external build or signing overlay supplying T3_BUILD_CHANNEL. Ordinary upstream builds intentionally supply nothing and stay unmarked.
• Unknown values intentionally fall back to the ordinary title.
• The title is the changed behavior. The videos tap the unchanged project filter to prove the screen is live and to bind each state to the repository timeline workflow.
• No unrelated SwiftUI flow was retested.

8. UI evidence

All media below comes from fresh builds of current head 0bb632164. The fixture contains one sanitized project and no threads. Dark mode is first, tight title crops are primary, and full-window context is collapsed.

Dark mode

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean dark-mode MP4 | Annotated dark-mode MP4

Full-window context, dark mode

Ordinary

Dev

Test

Light mode evidence

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean light-mode MP4 | Annotated light-mode MP4

Full-window context, light mode

Ordinary

Dev

Test

This section supersedes the earlier screenshot-only proof in the PR conversation.

9. Owning issue and target

Owning work item: saphid/t3code-personal#121. Authorized proof batch: saphid/t3code-personal#150. This PR targets t3code/rebuild-mobile-app-swift.

Vouched handoff checklist

1. Pass. One observable Home-title behavior, five related files.
2. Pass. The problem, cause, change, and non-goals match current head.
3. Pass. The existing Home button, plist expansion, and design tokens are reused.
4. Pass. Affected and unchanged clients, platforms, contracts, providers, and connections are named.
5. Pass. The focused native suite passed 7/7.
6. Pass. Parse, plist, diff, exact-head build, and strict signature checks passed.
7. Pass. Ordinary, Dev, and Test runtime states were exercised on a leased simulator.
8. Pass. Dark-first tight crops, collapsed full-window context, collapsed light evidence, and GIFs are embedded above; clean and annotated MP4s are linked above.
9. Pass. Risks, the recovered ENOSPC attempt, and untested paths are stated plainly.
10. Pass. The branch contains no unrelated cleanup or PR-only media files.
11. Pass. The description and proof match 0bb632164; the final independent review inspected that commit.
12. Pass. Scope, proof, and expected behavior are ready for maintainer review.

Overall handoff: PASS, ready for maintainer review.

Checklist

• This PR is small and focused
• I explained what changed and why
• I embedded dark-first, phone-readable current-head screenshots with full-window and light context collapsed
• I embedded current-head comparison and action GIFs and linked clean and annotated MP4s
• I verified every anonymous screenshot and GIF URL renders in the live PR body, and every MP4 URL downloads byte-identically with byte-range support

Implementation: GPT-5.6 Sol high in the Codex harness. Independent review: Claude Opus 5 high, read-only, exit 0, no actionable findings.

Upstream delivery

Delivery: direct
Validated against Theo commit: c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0
Depends on: none
Merge order: this PR only
Validation status: none of this PR's five changed paths overlaps Theo's new commit; a merge-tree simulation against the live target exited 0. Current head 0bb6321643348ddba4efa68bd385c03961544398 has green required CI, 7/7 focused native tests, exact-head signed Simulator proof, a successful direct Claude Opus 5 high review with no actionable findings, successful CodeRabbit/Cursor/Macroscope correctness reviews, and no unresolved threads. All 20 linked proof assets returned HTTP 206 byte ranges on 2026-09-01.
Dark mode evidence: yes
Clean screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/dev-dark-tight.png
Annotated screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-action.gif
Clean video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-clean.mp4
Annotated video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-annotated.mp4

[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: ca7d1bf3-a4ae-4855-9312-9a5f68d86cb7

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

---

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new configuration-controlled Dev/Test marker to the user-facing Home title while leaving ordinary builds and other runtime flows unchanged. The behavior is small and tested, but its core integration changes an existing shared WorkspaceView, so the bounded additive exception does not fully apply.

^{You can add or adjust custom eligibility rules. Learn more.}

[saphid]

Evidence refreshed on current head

The earlier 69523545 snapshot is superseded. Current-head proof for 0bb6321643348ddba4efa68bd385c03961544398 is now in the PR description: dark-first tight Ordinary/Dev/Test crops, comparison and action GIFs, collapsed full-window and light-mode context, plus clean and annotated MP4s.

Permanent public media: https://github.com/saphid/t3code/releases/tag/pr-7453-evidence-0bb632164-20260830

Dismissing prior approval to re-evaluate 983164b

[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 983164b024afda7537266604694c0bd7de0a1864. Configure here.}

Dismissing prior approval to re-evaluate 3bcdfec

Dismissing prior approval to re-evaluate 6737462

[saphid]

@t3dotgg Ready for human review. This is classified direct against live SwiftUI target c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0: none of the five changed paths overlaps Theo's new commit, and the merge-tree simulation is clean. Head 0bb632164 has green required CI, 7/7 focused native tests, signed exact-head Simulator proof, no unresolved review threads, and successful CodeRabbit, Cursor, Macroscope correctness, and direct Claude Opus 5 high reviews. All 20 proof assets are reachable; the PR body now records the delivery block and exact media.

[saphid]

1. Observed problem and reproduction

Install Dev, Test, and ordinary SwiftUI builds, then open Home. Before this change, the environments button always read T3 Code, so Home did not distinguish Dev from Test.

2. Cause

The SwiftUI client had no explicit build-channel presentation model. Inferring a channel from bundle identifiers would couple upstream UI to one fork and could mislabel unknown builds.

3. Change and ownership boundary

T3_BUILD_CHANNEL supplied by an xcodebuild argument or local xcconfig expands into the generic T3BuildChannel Info.plist value. Supported values render T3 Code Dev in the existing number token or T3 Code Test in the existing keyword token. The environments button uses the same title in its accessibility label.

The change stays at the SwiftUI Home presentation boundary. It adds one small value model, updates the existing environments button, expands one plist value, documents the setting, and adds focused tests. It does not add a project default or forward this contributor-owned overlay through install-device.sh.

4. Intentionally unchanged

Missing, empty, unexpanded, upstream, and unknown declarations preserve the ordinary T3 Code title. Offline and reconnecting environment status titles remain higher priority.

Bundle identifiers, installed app names, signing and publication workflows, server behavior, providers, contracts, connection modes, web, desktop, and React Native mobile are unchanged. No adjacent cleanup is included.

5. Affected surfaces

• Client and entry point: SwiftUI mobile, Home environments button only.
• Platform: iOS and iPadOS presentation code.
• Accessibility: T3 Code Dev. Manage environments, T3 Code Test. Manage environments, or the unchanged ordinary label.
• Covered declarations: dev, test, upstream, missing, empty, whitespace, unexpanded, mixed-case, and unknown values.

6. Validation on current head

Head 0bb6321643348ddba4efa68bd385c03961544398 targets 22b22f1463b83963d851bd0574a36a20f224a28d on t3code/rebuild-mobile-app-swift.

• PersonalBuildChannelTests: 7 executed, 7 passed, 0 failed.
• xcrun swiftc -parse apps/swift-ios/Features/Workspace/PersonalBuildChannel.swift apps/swift-ios/Features/Workspace/WorkspaceView.swift: exit 0.
• plutil -lint apps/swift-ios/Resources/Info.plist: exit 0, OK.
• git diff --check against the target: exit 0.
• Fresh ordinary, Dev, and Test simulator builds each embed the current head in T3GitCommit and pass codesign --verify --deep --strict.
• The three preserved app variants have the same T3Code.debug.dylib SHA-256, 6f0d7897114811bf685add8fdb7a496fbb96deddb817046b7b74626756af64e2. Only the declared build channel differs.
• Integrated proof ran on the leased iPhone 16 Pro simulator with iOS 26.5 against a disposable loopback environment. Dark and light semantic snapshots matched every visible title and accessibility label.
• The dark and light video packets each contain three real project-filter taps. Packet validation passed all three actions and sealed the clean and annotated derivatives.
• Direct read-only Claude Opus 5 high review of the frozen final diff exited 0 with no actionable findings.

An earlier focused-test attempt hit ENOSPC before any test ran. The retained retry on the same suite passed 7/7 after disposable build data was cleared.

7. Risks and limitations

• The marker depends on the external build or signing overlay supplying T3_BUILD_CHANNEL. Ordinary upstream builds intentionally supply nothing and stay unmarked.
• Unknown values intentionally fall back to the ordinary title.
• The title is the changed behavior. The videos tap the unchanged project filter to prove the screen is live and to bind each state to the repository timeline workflow.
• No unrelated SwiftUI flow was retested.

8. UI evidence

All media below comes from fresh builds of current head 0bb632164. The fixture contains one sanitized project and no threads. Dark mode is first, tight title crops are primary, and full-window context is collapsed.

Dark mode

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean dark-mode MP4 | Annotated dark-mode MP4

Full-window context, dark mode

Ordinary

Dev

Test

Light mode evidence

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean light-mode MP4 | Annotated light-mode MP4

Full-window context, light mode

Ordinary

Dev

Test

This section supersedes the earlier screenshot-only proof in the PR conversation.

9. Owning issue and target

Owning work item: saphid/t3code-personal#121. Authorized proof batch: saphid/t3code-personal#150. This PR targets t3code/rebuild-mobile-app-swift.

Vouched handoff checklist

1. Pass. One observable Home-title behavior, five related files.
2. Pass. The problem, cause, change, and non-goals match current head.
3. Pass. The existing Home button, plist expansion, and design tokens are reused.
4. Pass. Affected and unchanged clients, platforms, contracts, providers, and connections are named.
5. Pass. The focused native suite passed 7/7.
6. Pass. Parse, plist, diff, exact-head build, and strict signature checks passed.
7. Pass. Ordinary, Dev, and Test runtime states were exercised on a leased simulator.
8. Pass. Dark-first tight crops, collapsed full-window context, collapsed light evidence, and GIFs are embedded above; clean and annotated MP4s are linked above.
9. Pass. Risks, the recovered ENOSPC attempt, and untested paths are stated plainly.
10. Pass. The branch contains no unrelated cleanup or PR-only media files.
11. Pass. The description and proof match 0bb632164; the final independent review inspected that commit.
12. Pass. Scope, proof, and expected behavior are ready for maintainer review.

Overall handoff: PASS, ready for maintainer review.

Checklist

• This PR is small and focused
• I explained what changed and why
• I embedded dark-first, phone-readable current-head screenshots with full-window and light context collapsed
• I embedded current-head comparison and action GIFs and linked clean and annotated MP4s
• I verified every anonymous screenshot and GIF URL renders in the live PR body, and every MP4 URL downloads byte-identically with byte-range support

Implementation: GPT-5.6 Sol high in the Codex harness. Independent review: Claude Opus 5 high, read-only, exit 0, no actionable findings.

Upstream delivery

Delivery: direct
Validated against Theo commit: c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0
Depends on: none
Merge order: this PR only
Validation status: none of this PR's five changed paths overlaps Theo's new commit; a merge-tree simulation against the live target exited 0. Current head 0bb6321643348ddba4efa68bd385c03961544398 has green required CI, 7/7 focused native tests, exact-head signed Simulator proof, a successful direct Claude Opus 5 high review with no actionable findings, successful CodeRabbit/Cursor/Macroscope correctness reviews, and no unresolved threads. All 20 linked proof assets returned HTTP 206 byte ranges on 2026-09-01.
Dark mode evidence: yes
Clean screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/dev-dark-tight.png
Annotated screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-action.gif
Clean video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-clean.mp4
Annotated video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-annotated.mp4

[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: ca7d1bf3-a4ae-4855-9312-9a5f68d86cb7

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

---

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new configuration-controlled Dev/Test marker to the user-facing Home title while leaving ordinary builds and other runtime flows unchanged. The behavior is small and tested, but its core integration changes an existing shared WorkspaceView, so the bounded additive exception does not fully apply.

^{You can add or adjust custom eligibility rules. Learn more.}

[saphid]

Evidence refreshed on current head

The earlier 69523545 snapshot is superseded. Current-head proof for 0bb6321643348ddba4efa68bd385c03961544398 is now in the PR description: dark-first tight Ordinary/Dev/Test crops, comparison and action GIFs, collapsed full-window and light-mode context, plus clean and annotated MP4s.

Permanent public media: https://github.com/saphid/t3code/releases/tag/pr-7453-evidence-0bb632164-20260830

Dismissing prior approval to re-evaluate 983164b

[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 983164b024afda7537266604694c0bd7de0a1864. Configure here.}

Dismissing prior approval to re-evaluate 3bcdfec

Dismissing prior approval to re-evaluate 6737462

[saphid]

@t3dotgg Ready for human review. This is classified direct against live SwiftUI target c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0: none of the five changed paths overlaps Theo's new commit, and the merge-tree simulation is clean. Head 0bb632164 has green required CI, 7/7 focused native tests, signed exact-head Simulator proof, no unresolved review threads, and successful CodeRabbit, Cursor, Macroscope correctness, and direct Claude Opus 5 high reviews. All 20 proof assets are reachable; the PR body now records the delivery block and exact media.

[saphid]

1. Observed problem and reproduction

Install Dev, Test, and ordinary SwiftUI builds, then open Home. Before this change, the environments button always read T3 Code, so Home did not distinguish Dev from Test.

2. Cause

The SwiftUI client had no explicit build-channel presentation model. Inferring a channel from bundle identifiers would couple upstream UI to one fork and could mislabel unknown builds.

3. Change and ownership boundary

T3_BUILD_CHANNEL supplied by an xcodebuild argument or local xcconfig expands into the generic T3BuildChannel Info.plist value. Supported values render T3 Code Dev in the existing number token or T3 Code Test in the existing keyword token. The environments button uses the same title in its accessibility label.

The change stays at the SwiftUI Home presentation boundary. It adds one small value model, updates the existing environments button, expands one plist value, documents the setting, and adds focused tests. It does not add a project default or forward this contributor-owned overlay through install-device.sh.

4. Intentionally unchanged

Missing, empty, unexpanded, upstream, and unknown declarations preserve the ordinary T3 Code title. Offline and reconnecting environment status titles remain higher priority.

Bundle identifiers, installed app names, signing and publication workflows, server behavior, providers, contracts, connection modes, web, desktop, and React Native mobile are unchanged. No adjacent cleanup is included.

5. Affected surfaces

• Client and entry point: SwiftUI mobile, Home environments button only.
• Platform: iOS and iPadOS presentation code.
• Accessibility: T3 Code Dev. Manage environments, T3 Code Test. Manage environments, or the unchanged ordinary label.
• Covered declarations: dev, test, upstream, missing, empty, whitespace, unexpanded, mixed-case, and unknown values.

6. Validation on current head

Head 0bb6321643348ddba4efa68bd385c03961544398 targets 22b22f1463b83963d851bd0574a36a20f224a28d on t3code/rebuild-mobile-app-swift.

• PersonalBuildChannelTests: 7 executed, 7 passed, 0 failed.
• xcrun swiftc -parse apps/swift-ios/Features/Workspace/PersonalBuildChannel.swift apps/swift-ios/Features/Workspace/WorkspaceView.swift: exit 0.
• plutil -lint apps/swift-ios/Resources/Info.plist: exit 0, OK.
• git diff --check against the target: exit 0.
• Fresh ordinary, Dev, and Test simulator builds each embed the current head in T3GitCommit and pass codesign --verify --deep --strict.
• The three preserved app variants have the same T3Code.debug.dylib SHA-256, 6f0d7897114811bf685add8fdb7a496fbb96deddb817046b7b74626756af64e2. Only the declared build channel differs.
• Integrated proof ran on the leased iPhone 16 Pro simulator with iOS 26.5 against a disposable loopback environment. Dark and light semantic snapshots matched every visible title and accessibility label.
• The dark and light video packets each contain three real project-filter taps. Packet validation passed all three actions and sealed the clean and annotated derivatives.
• Direct read-only Claude Opus 5 high review of the frozen final diff exited 0 with no actionable findings.

An earlier focused-test attempt hit ENOSPC before any test ran. The retained retry on the same suite passed 7/7 after disposable build data was cleared.

7. Risks and limitations

• The marker depends on the external build or signing overlay supplying T3_BUILD_CHANNEL. Ordinary upstream builds intentionally supply nothing and stay unmarked.
• Unknown values intentionally fall back to the ordinary title.
• The title is the changed behavior. The videos tap the unchanged project filter to prove the screen is live and to bind each state to the repository timeline workflow.
• No unrelated SwiftUI flow was retested.

8. UI evidence

All media below comes from fresh builds of current head 0bb632164. The fixture contains one sanitized project and no threads. Dark mode is first, tight title crops are primary, and full-window context is collapsed.

Dark mode

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean dark-mode MP4 | Annotated dark-mode MP4

Full-window context, dark mode

Ordinary

Dev

Test

Light mode evidence

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean light-mode MP4 | Annotated light-mode MP4

Full-window context, light mode

Ordinary

Dev

Test

This section supersedes the earlier screenshot-only proof in the PR conversation.

9. Owning issue and target

Owning work item: saphid/t3code-personal#121. Authorized proof batch: saphid/t3code-personal#150. This PR targets t3code/rebuild-mobile-app-swift.

Vouched handoff checklist

1. Pass. One observable Home-title behavior, five related files.
2. Pass. The problem, cause, change, and non-goals match current head.
3. Pass. The existing Home button, plist expansion, and design tokens are reused.
4. Pass. Affected and unchanged clients, platforms, contracts, providers, and connections are named.
5. Pass. The focused native suite passed 7/7.
6. Pass. Parse, plist, diff, exact-head build, and strict signature checks passed.
7. Pass. Ordinary, Dev, and Test runtime states were exercised on a leased simulator.
8. Pass. Dark-first tight crops, collapsed full-window context, collapsed light evidence, and GIFs are embedded above; clean and annotated MP4s are linked above.
9. Pass. Risks, the recovered ENOSPC attempt, and untested paths are stated plainly.
10. Pass. The branch contains no unrelated cleanup or PR-only media files.
11. Pass. The description and proof match 0bb632164; the final independent review inspected that commit.
12. Pass. Scope, proof, and expected behavior are ready for maintainer review.

Overall handoff: PASS, ready for maintainer review.

Checklist

• This PR is small and focused
• I explained what changed and why
• I embedded dark-first, phone-readable current-head screenshots with full-window and light context collapsed
• I embedded current-head comparison and action GIFs and linked clean and annotated MP4s
• I verified every anonymous screenshot and GIF URL renders in the live PR body, and every MP4 URL downloads byte-identically with byte-range support

Implementation: GPT-5.6 Sol high in the Codex harness. Independent review: Claude Opus 5 high, read-only, exit 0, no actionable findings.

Upstream delivery

Delivery: direct
Validated against Theo commit: c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0
Depends on: none
Merge order: this PR only
Validation status: none of this PR's five changed paths overlaps Theo's new commit; a merge-tree simulation against the live target exited 0. Current head 0bb6321643348ddba4efa68bd385c03961544398 has green required CI, 7/7 focused native tests, exact-head signed Simulator proof, a successful direct Claude Opus 5 high review with no actionable findings, successful CodeRabbit/Cursor/Macroscope correctness reviews, and no unresolved threads. All 20 linked proof assets returned HTTP 206 byte ranges on 2026-09-01.
Dark mode evidence: yes
Clean screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/dev-dark-tight.png
Annotated screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-action.gif
Clean video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-clean.mp4
Annotated video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-annotated.mp4

[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: ca7d1bf3-a4ae-4855-9312-9a5f68d86cb7

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

---

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new configuration-controlled Dev/Test marker to the user-facing Home title while leaving ordinary builds and other runtime flows unchanged. The behavior is small and tested, but its core integration changes an existing shared WorkspaceView, so the bounded additive exception does not fully apply.

^{You can add or adjust custom eligibility rules. Learn more.}

[saphid]

Evidence refreshed on current head

The earlier 69523545 snapshot is superseded. Current-head proof for 0bb6321643348ddba4efa68bd385c03961544398 is now in the PR description: dark-first tight Ordinary/Dev/Test crops, comparison and action GIFs, collapsed full-window and light-mode context, plus clean and annotated MP4s.

Permanent public media: https://github.com/saphid/t3code/releases/tag/pr-7453-evidence-0bb632164-20260830

Dismissing prior approval to re-evaluate 983164b

[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 983164b024afda7537266604694c0bd7de0a1864. Configure here.}

Dismissing prior approval to re-evaluate 3bcdfec

Dismissing prior approval to re-evaluate 6737462

[saphid]

@t3dotgg Ready for human review. This is classified direct against live SwiftUI target c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0: none of the five changed paths overlaps Theo's new commit, and the merge-tree simulation is clean. Head 0bb632164 has green required CI, 7/7 focused native tests, signed exact-head Simulator proof, no unresolved review threads, and successful CodeRabbit, Cursor, Macroscope correctness, and direct Claude Opus 5 high reviews. All 20 proof assets are reachable; the PR body now records the delivery block and exact media.

[saphid]

1. Observed problem and reproduction

Install Dev, Test, and ordinary SwiftUI builds, then open Home. Before this change, the environments button always read T3 Code, so Home did not distinguish Dev from Test.

2. Cause

The SwiftUI client had no explicit build-channel presentation model. Inferring a channel from bundle identifiers would couple upstream UI to one fork and could mislabel unknown builds.

3. Change and ownership boundary

T3_BUILD_CHANNEL supplied by an xcodebuild argument or local xcconfig expands into the generic T3BuildChannel Info.plist value. Supported values render T3 Code Dev in the existing number token or T3 Code Test in the existing keyword token. The environments button uses the same title in its accessibility label.

The change stays at the SwiftUI Home presentation boundary. It adds one small value model, updates the existing environments button, expands one plist value, documents the setting, and adds focused tests. It does not add a project default or forward this contributor-owned overlay through install-device.sh.

4. Intentionally unchanged

Missing, empty, unexpanded, upstream, and unknown declarations preserve the ordinary T3 Code title. Offline and reconnecting environment status titles remain higher priority.

Bundle identifiers, installed app names, signing and publication workflows, server behavior, providers, contracts, connection modes, web, desktop, and React Native mobile are unchanged. No adjacent cleanup is included.

5. Affected surfaces

• Client and entry point: SwiftUI mobile, Home environments button only.
• Platform: iOS and iPadOS presentation code.
• Accessibility: T3 Code Dev. Manage environments, T3 Code Test. Manage environments, or the unchanged ordinary label.
• Covered declarations: dev, test, upstream, missing, empty, whitespace, unexpanded, mixed-case, and unknown values.

6. Validation on current head

Head 0bb6321643348ddba4efa68bd385c03961544398 targets 22b22f1463b83963d851bd0574a36a20f224a28d on t3code/rebuild-mobile-app-swift.

• PersonalBuildChannelTests: 7 executed, 7 passed, 0 failed.
• xcrun swiftc -parse apps/swift-ios/Features/Workspace/PersonalBuildChannel.swift apps/swift-ios/Features/Workspace/WorkspaceView.swift: exit 0.
• plutil -lint apps/swift-ios/Resources/Info.plist: exit 0, OK.
• git diff --check against the target: exit 0.
• Fresh ordinary, Dev, and Test simulator builds each embed the current head in T3GitCommit and pass codesign --verify --deep --strict.
• The three preserved app variants have the same T3Code.debug.dylib SHA-256, 6f0d7897114811bf685add8fdb7a496fbb96deddb817046b7b74626756af64e2. Only the declared build channel differs.
• Integrated proof ran on the leased iPhone 16 Pro simulator with iOS 26.5 against a disposable loopback environment. Dark and light semantic snapshots matched every visible title and accessibility label.
• The dark and light video packets each contain three real project-filter taps. Packet validation passed all three actions and sealed the clean and annotated derivatives.
• Direct read-only Claude Opus 5 high review of the frozen final diff exited 0 with no actionable findings.

An earlier focused-test attempt hit ENOSPC before any test ran. The retained retry on the same suite passed 7/7 after disposable build data was cleared.

7. Risks and limitations

• The marker depends on the external build or signing overlay supplying T3_BUILD_CHANNEL. Ordinary upstream builds intentionally supply nothing and stay unmarked.
• Unknown values intentionally fall back to the ordinary title.
• The title is the changed behavior. The videos tap the unchanged project filter to prove the screen is live and to bind each state to the repository timeline workflow.
• No unrelated SwiftUI flow was retested.

8. UI evidence

All media below comes from fresh builds of current head 0bb632164. The fixture contains one sanitized project and no threads. Dark mode is first, tight title crops are primary, and full-window context is collapsed.

Dark mode

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean dark-mode MP4 | Annotated dark-mode MP4

Full-window context, dark mode

Ordinary

Dev

Test

Light mode evidence

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean light-mode MP4 | Annotated light-mode MP4

Full-window context, light mode

Ordinary

Dev

Test

This section supersedes the earlier screenshot-only proof in the PR conversation.

9. Owning issue and target

Owning work item: saphid/t3code-personal#121. Authorized proof batch: saphid/t3code-personal#150. This PR targets t3code/rebuild-mobile-app-swift.

Vouched handoff checklist

1. Pass. One observable Home-title behavior, five related files.
2. Pass. The problem, cause, change, and non-goals match current head.
3. Pass. The existing Home button, plist expansion, and design tokens are reused.
4. Pass. Affected and unchanged clients, platforms, contracts, providers, and connections are named.
5. Pass. The focused native suite passed 7/7.
6. Pass. Parse, plist, diff, exact-head build, and strict signature checks passed.
7. Pass. Ordinary, Dev, and Test runtime states were exercised on a leased simulator.
8. Pass. Dark-first tight crops, collapsed full-window context, collapsed light evidence, and GIFs are embedded above; clean and annotated MP4s are linked above.
9. Pass. Risks, the recovered ENOSPC attempt, and untested paths are stated plainly.
10. Pass. The branch contains no unrelated cleanup or PR-only media files.
11. Pass. The description and proof match 0bb632164; the final independent review inspected that commit.
12. Pass. Scope, proof, and expected behavior are ready for maintainer review.

Overall handoff: PASS, ready for maintainer review.

Checklist

• This PR is small and focused
• I explained what changed and why
• I embedded dark-first, phone-readable current-head screenshots with full-window and light context collapsed
• I embedded current-head comparison and action GIFs and linked clean and annotated MP4s
• I verified every anonymous screenshot and GIF URL renders in the live PR body, and every MP4 URL downloads byte-identically with byte-range support

Implementation: GPT-5.6 Sol high in the Codex harness. Independent review: Claude Opus 5 high, read-only, exit 0, no actionable findings.

Upstream delivery

Delivery: direct
Validated against Theo commit: c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0
Depends on: none
Merge order: this PR only
Validation status: none of this PR's five changed paths overlaps Theo's new commit; a merge-tree simulation against the live target exited 0. Current head 0bb6321643348ddba4efa68bd385c03961544398 has green required CI, 7/7 focused native tests, exact-head signed Simulator proof, a successful direct Claude Opus 5 high review with no actionable findings, successful CodeRabbit/Cursor/Macroscope correctness reviews, and no unresolved threads. All 20 linked proof assets returned HTTP 206 byte ranges on 2026-09-01.
Dark mode evidence: yes
Clean screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/dev-dark-tight.png
Annotated screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-action.gif
Clean video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-clean.mp4
Annotated video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-annotated.mp4

[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: ca7d1bf3-a4ae-4855-9312-9a5f68d86cb7

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

---

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new configuration-controlled Dev/Test marker to the user-facing Home title while leaving ordinary builds and other runtime flows unchanged. The behavior is small and tested, but its core integration changes an existing shared WorkspaceView, so the bounded additive exception does not fully apply.

^{You can add or adjust custom eligibility rules. Learn more.}

[saphid]

Evidence refreshed on current head

The earlier 69523545 snapshot is superseded. Current-head proof for 0bb6321643348ddba4efa68bd385c03961544398 is now in the PR description: dark-first tight Ordinary/Dev/Test crops, comparison and action GIFs, collapsed full-window and light-mode context, plus clean and annotated MP4s.

Permanent public media: https://github.com/saphid/t3code/releases/tag/pr-7453-evidence-0bb632164-20260830

Dismissing prior approval to re-evaluate 983164b

[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 983164b024afda7537266604694c0bd7de0a1864. Configure here.}

Dismissing prior approval to re-evaluate 3bcdfec

Dismissing prior approval to re-evaluate 6737462

[saphid]

@t3dotgg Ready for human review. This is classified direct against live SwiftUI target c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0: none of the five changed paths overlaps Theo's new commit, and the merge-tree simulation is clean. Head 0bb632164 has green required CI, 7/7 focused native tests, signed exact-head Simulator proof, no unresolved review threads, and successful CodeRabbit, Cursor, Macroscope correctness, and direct Claude Opus 5 high reviews. All 20 proof assets are reachable; the PR body now records the delivery block and exact media.

[saphid]

1. Observed problem and reproduction

Install Dev, Test, and ordinary SwiftUI builds, then open Home. Before this change, the environments button always read T3 Code, so Home did not distinguish Dev from Test.

2. Cause

The SwiftUI client had no explicit build-channel presentation model. Inferring a channel from bundle identifiers would couple upstream UI to one fork and could mislabel unknown builds.

3. Change and ownership boundary

T3_BUILD_CHANNEL supplied by an xcodebuild argument or local xcconfig expands into the generic T3BuildChannel Info.plist value. Supported values render T3 Code Dev in the existing number token or T3 Code Test in the existing keyword token. The environments button uses the same title in its accessibility label.

The change stays at the SwiftUI Home presentation boundary. It adds one small value model, updates the existing environments button, expands one plist value, documents the setting, and adds focused tests. It does not add a project default or forward this contributor-owned overlay through install-device.sh.

4. Intentionally unchanged

Missing, empty, unexpanded, upstream, and unknown declarations preserve the ordinary T3 Code title. Offline and reconnecting environment status titles remain higher priority.

Bundle identifiers, installed app names, signing and publication workflows, server behavior, providers, contracts, connection modes, web, desktop, and React Native mobile are unchanged. No adjacent cleanup is included.

5. Affected surfaces

• Client and entry point: SwiftUI mobile, Home environments button only.
• Platform: iOS and iPadOS presentation code.
• Accessibility: T3 Code Dev. Manage environments, T3 Code Test. Manage environments, or the unchanged ordinary label.
• Covered declarations: dev, test, upstream, missing, empty, whitespace, unexpanded, mixed-case, and unknown values.

6. Validation on current head

Head 0bb6321643348ddba4efa68bd385c03961544398 targets 22b22f1463b83963d851bd0574a36a20f224a28d on t3code/rebuild-mobile-app-swift.

• PersonalBuildChannelTests: 7 executed, 7 passed, 0 failed.
• xcrun swiftc -parse apps/swift-ios/Features/Workspace/PersonalBuildChannel.swift apps/swift-ios/Features/Workspace/WorkspaceView.swift: exit 0.
• plutil -lint apps/swift-ios/Resources/Info.plist: exit 0, OK.
• git diff --check against the target: exit 0.
• Fresh ordinary, Dev, and Test simulator builds each embed the current head in T3GitCommit and pass codesign --verify --deep --strict.
• The three preserved app variants have the same T3Code.debug.dylib SHA-256, 6f0d7897114811bf685add8fdb7a496fbb96deddb817046b7b74626756af64e2. Only the declared build channel differs.
• Integrated proof ran on the leased iPhone 16 Pro simulator with iOS 26.5 against a disposable loopback environment. Dark and light semantic snapshots matched every visible title and accessibility label.
• The dark and light video packets each contain three real project-filter taps. Packet validation passed all three actions and sealed the clean and annotated derivatives.
• Direct read-only Claude Opus 5 high review of the frozen final diff exited 0 with no actionable findings.

An earlier focused-test attempt hit ENOSPC before any test ran. The retained retry on the same suite passed 7/7 after disposable build data was cleared.

7. Risks and limitations

• The marker depends on the external build or signing overlay supplying T3_BUILD_CHANNEL. Ordinary upstream builds intentionally supply nothing and stay unmarked.
• Unknown values intentionally fall back to the ordinary title.
• The title is the changed behavior. The videos tap the unchanged project filter to prove the screen is live and to bind each state to the repository timeline workflow.
• No unrelated SwiftUI flow was retested.

8. UI evidence

All media below comes from fresh builds of current head 0bb632164. The fixture contains one sanitized project and no threads. Dark mode is first, tight title crops are primary, and full-window context is collapsed.

Dark mode

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean dark-mode MP4 | Annotated dark-mode MP4

Full-window context, dark mode

Ordinary

Dev

Test

Light mode evidence

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean light-mode MP4 | Annotated light-mode MP4

Full-window context, light mode

Ordinary

Dev

Test

This section supersedes the earlier screenshot-only proof in the PR conversation.

9. Owning issue and target

Owning work item: saphid/t3code-personal#121. Authorized proof batch: saphid/t3code-personal#150. This PR targets t3code/rebuild-mobile-app-swift.

Vouched handoff checklist

1. Pass. One observable Home-title behavior, five related files.
2. Pass. The problem, cause, change, and non-goals match current head.
3. Pass. The existing Home button, plist expansion, and design tokens are reused.
4. Pass. Affected and unchanged clients, platforms, contracts, providers, and connections are named.
5. Pass. The focused native suite passed 7/7.
6. Pass. Parse, plist, diff, exact-head build, and strict signature checks passed.
7. Pass. Ordinary, Dev, and Test runtime states were exercised on a leased simulator.
8. Pass. Dark-first tight crops, collapsed full-window context, collapsed light evidence, and GIFs are embedded above; clean and annotated MP4s are linked above.
9. Pass. Risks, the recovered ENOSPC attempt, and untested paths are stated plainly.
10. Pass. The branch contains no unrelated cleanup or PR-only media files.
11. Pass. The description and proof match 0bb632164; the final independent review inspected that commit.
12. Pass. Scope, proof, and expected behavior are ready for maintainer review.

Overall handoff: PASS, ready for maintainer review.

Checklist

• This PR is small and focused
• I explained what changed and why
• I embedded dark-first, phone-readable current-head screenshots with full-window and light context collapsed
• I embedded current-head comparison and action GIFs and linked clean and annotated MP4s
• I verified every anonymous screenshot and GIF URL renders in the live PR body, and every MP4 URL downloads byte-identically with byte-range support

Implementation: GPT-5.6 Sol high in the Codex harness. Independent review: Claude Opus 5 high, read-only, exit 0, no actionable findings.

Upstream delivery

Delivery: direct
Validated against Theo commit: c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0
Depends on: none
Merge order: this PR only
Validation status: none of this PR's five changed paths overlaps Theo's new commit; a merge-tree simulation against the live target exited 0. Current head 0bb6321643348ddba4efa68bd385c03961544398 has green required CI, 7/7 focused native tests, exact-head signed Simulator proof, a successful direct Claude Opus 5 high review with no actionable findings, successful CodeRabbit/Cursor/Macroscope correctness reviews, and no unresolved threads. All 20 linked proof assets returned HTTP 206 byte ranges on 2026-09-01.
Dark mode evidence: yes
Clean screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/dev-dark-tight.png
Annotated screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-action.gif
Clean video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-clean.mp4
Annotated video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-annotated.mp4

[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: ca7d1bf3-a4ae-4855-9312-9a5f68d86cb7

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

---

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new configuration-controlled Dev/Test marker to the user-facing Home title while leaving ordinary builds and other runtime flows unchanged. The behavior is small and tested, but its core integration changes an existing shared WorkspaceView, so the bounded additive exception does not fully apply.

^{You can add or adjust custom eligibility rules. Learn more.}

[saphid]

Evidence refreshed on current head

The earlier 69523545 snapshot is superseded. Current-head proof for 0bb6321643348ddba4efa68bd385c03961544398 is now in the PR description: dark-first tight Ordinary/Dev/Test crops, comparison and action GIFs, collapsed full-window and light-mode context, plus clean and annotated MP4s.

Permanent public media: https://github.com/saphid/t3code/releases/tag/pr-7453-evidence-0bb632164-20260830

Dismissing prior approval to re-evaluate 983164b

[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 983164b024afda7537266604694c0bd7de0a1864. Configure here.}

Dismissing prior approval to re-evaluate 3bcdfec

Dismissing prior approval to re-evaluate 6737462

[saphid]

@t3dotgg Ready for human review. This is classified direct against live SwiftUI target c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0: none of the five changed paths overlaps Theo's new commit, and the merge-tree simulation is clean. Head 0bb632164 has green required CI, 7/7 focused native tests, signed exact-head Simulator proof, no unresolved review threads, and successful CodeRabbit, Cursor, Macroscope correctness, and direct Claude Opus 5 high reviews. All 20 proof assets are reachable; the PR body now records the delivery block and exact media.

[saphid]

1. Observed problem and reproduction

Install Dev, Test, and ordinary SwiftUI builds, then open Home. Before this change, the environments button always read T3 Code, so Home did not distinguish Dev from Test.

2. Cause

The SwiftUI client had no explicit build-channel presentation model. Inferring a channel from bundle identifiers would couple upstream UI to one fork and could mislabel unknown builds.

3. Change and ownership boundary

T3_BUILD_CHANNEL supplied by an xcodebuild argument or local xcconfig expands into the generic T3BuildChannel Info.plist value. Supported values render T3 Code Dev in the existing number token or T3 Code Test in the existing keyword token. The environments button uses the same title in its accessibility label.

The change stays at the SwiftUI Home presentation boundary. It adds one small value model, updates the existing environments button, expands one plist value, documents the setting, and adds focused tests. It does not add a project default or forward this contributor-owned overlay through install-device.sh.

4. Intentionally unchanged

Missing, empty, unexpanded, upstream, and unknown declarations preserve the ordinary T3 Code title. Offline and reconnecting environment status titles remain higher priority.

Bundle identifiers, installed app names, signing and publication workflows, server behavior, providers, contracts, connection modes, web, desktop, and React Native mobile are unchanged. No adjacent cleanup is included.

5. Affected surfaces

• Client and entry point: SwiftUI mobile, Home environments button only.
• Platform: iOS and iPadOS presentation code.
• Accessibility: T3 Code Dev. Manage environments, T3 Code Test. Manage environments, or the unchanged ordinary label.
• Covered declarations: dev, test, upstream, missing, empty, whitespace, unexpanded, mixed-case, and unknown values.

6. Validation on current head

Head 0bb6321643348ddba4efa68bd385c03961544398 targets 22b22f1463b83963d851bd0574a36a20f224a28d on t3code/rebuild-mobile-app-swift.

• PersonalBuildChannelTests: 7 executed, 7 passed, 0 failed.
• xcrun swiftc -parse apps/swift-ios/Features/Workspace/PersonalBuildChannel.swift apps/swift-ios/Features/Workspace/WorkspaceView.swift: exit 0.
• plutil -lint apps/swift-ios/Resources/Info.plist: exit 0, OK.
• git diff --check against the target: exit 0.
• Fresh ordinary, Dev, and Test simulator builds each embed the current head in T3GitCommit and pass codesign --verify --deep --strict.
• The three preserved app variants have the same T3Code.debug.dylib SHA-256, 6f0d7897114811bf685add8fdb7a496fbb96deddb817046b7b74626756af64e2. Only the declared build channel differs.
• Integrated proof ran on the leased iPhone 16 Pro simulator with iOS 26.5 against a disposable loopback environment. Dark and light semantic snapshots matched every visible title and accessibility label.
• The dark and light video packets each contain three real project-filter taps. Packet validation passed all three actions and sealed the clean and annotated derivatives.
• Direct read-only Claude Opus 5 high review of the frozen final diff exited 0 with no actionable findings.

An earlier focused-test attempt hit ENOSPC before any test ran. The retained retry on the same suite passed 7/7 after disposable build data was cleared.

7. Risks and limitations

• The marker depends on the external build or signing overlay supplying T3_BUILD_CHANNEL. Ordinary upstream builds intentionally supply nothing and stay unmarked.
• Unknown values intentionally fall back to the ordinary title.
• The title is the changed behavior. The videos tap the unchanged project filter to prove the screen is live and to bind each state to the repository timeline workflow.
• No unrelated SwiftUI flow was retested.

8. UI evidence

All media below comes from fresh builds of current head 0bb632164. The fixture contains one sanitized project and no threads. Dark mode is first, tight title crops are primary, and full-window context is collapsed.

Dark mode

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean dark-mode MP4 | Annotated dark-mode MP4

Full-window context, dark mode

Ordinary

Dev

Test

Light mode evidence

Before, unmarked ordinary build

After, Dev build

After, Test build

Ordinary, Dev, and Test comparison

Live action sequence

Clean light-mode MP4 | Annotated light-mode MP4

Full-window context, light mode

Ordinary

Dev

Test

This section supersedes the earlier screenshot-only proof in the PR conversation.

9. Owning issue and target

Owning work item: saphid/t3code-personal#121. Authorized proof batch: saphid/t3code-personal#150. This PR targets t3code/rebuild-mobile-app-swift.

Vouched handoff checklist

1. Pass. One observable Home-title behavior, five related files.
2. Pass. The problem, cause, change, and non-goals match current head.
3. Pass. The existing Home button, plist expansion, and design tokens are reused.
4. Pass. Affected and unchanged clients, platforms, contracts, providers, and connections are named.
5. Pass. The focused native suite passed 7/7.
6. Pass. Parse, plist, diff, exact-head build, and strict signature checks passed.
7. Pass. Ordinary, Dev, and Test runtime states were exercised on a leased simulator.
8. Pass. Dark-first tight crops, collapsed full-window context, collapsed light evidence, and GIFs are embedded above; clean and annotated MP4s are linked above.
9. Pass. Risks, the recovered ENOSPC attempt, and untested paths are stated plainly.
10. Pass. The branch contains no unrelated cleanup or PR-only media files.
11. Pass. The description and proof match 0bb632164; the final independent review inspected that commit.
12. Pass. Scope, proof, and expected behavior are ready for maintainer review.

Overall handoff: PASS, ready for maintainer review.

Checklist

• This PR is small and focused
• I explained what changed and why
• I embedded dark-first, phone-readable current-head screenshots with full-window and light context collapsed
• I embedded current-head comparison and action GIFs and linked clean and annotated MP4s
• I verified every anonymous screenshot and GIF URL renders in the live PR body, and every MP4 URL downloads byte-identically with byte-range support

Implementation: GPT-5.6 Sol high in the Codex harness. Independent review: Claude Opus 5 high, read-only, exit 0, no actionable findings.

Upstream delivery

Delivery: direct
Validated against Theo commit: c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0
Depends on: none
Merge order: this PR only
Validation status: none of this PR's five changed paths overlaps Theo's new commit; a merge-tree simulation against the live target exited 0. Current head 0bb6321643348ddba4efa68bd385c03961544398 has green required CI, 7/7 focused native tests, exact-head signed Simulator proof, a successful direct Claude Opus 5 high review with no actionable findings, successful CodeRabbit/Cursor/Macroscope correctness reviews, and no unresolved threads. All 20 linked proof assets returned HTTP 206 byte ranges on 2026-09-01.
Dark mode evidence: yes
Clean screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/dev-dark-tight.png
Annotated screenshot: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-action.gif
Clean video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-clean.mp4
Annotated video: https://github.com/saphid/t3code/releases/download/pr-7453-evidence-0bb632164-20260830/channel-identity-dark-annotated.mp4

[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: ca7d1bf3-a4ae-4855-9312-9a5f68d86cb7

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

---

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new configuration-controlled Dev/Test marker to the user-facing Home title while leaving ordinary builds and other runtime flows unchanged. The behavior is small and tested, but its core integration changes an existing shared WorkspaceView, so the bounded additive exception does not fully apply.

^{You can add or adjust custom eligibility rules. Learn more.}

[saphid]

Evidence refreshed on current head

The earlier 69523545 snapshot is superseded. Current-head proof for 0bb6321643348ddba4efa68bd385c03961544398 is now in the PR description: dark-first tight Ordinary/Dev/Test crops, comparison and action GIFs, collapsed full-window and light-mode context, plus clean and annotated MP4s.

Permanent public media: https://github.com/saphid/t3code/releases/tag/pr-7453-evidence-0bb632164-20260830

Dismissing prior approval to re-evaluate 983164b

[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 983164b024afda7537266604694c0bd7de0a1864. Configure here.}

Dismissing prior approval to re-evaluate 3bcdfec

Dismissing prior approval to re-evaluate 6737462

[saphid]

@t3dotgg Ready for human review. This is classified direct against live SwiftUI target c49bcc5d8a56324eb0ad9cf1b19d5dcc6ca0caa0: none of the five changed paths overlaps Theo's new commit, and the merge-tree simulation is clean. Head 0bb632164 has green required CI, 7/7 focused native tests, signed exact-head Simulator proof, no unresolved review threads, and successful CodeRabbit, Cursor, Macroscope correctness, and direct Claude Opus 5 high reviews. All 20 proof assets are reachable; the PR body now records the delivery block and exact media.