Best possible solution:

Land the iOS license screen once maintainers confirm the intended third-party acknowledgement scope and required checks finish cleanly.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a feature PR rather than a bug report. Source inspection shows current main lacks the route and the PR adds the new loader, Settings row, destination, resources, and tests.

Is this the best way to solve the issue?

Yes, with one maintainer check: using a small SwiftUI route plus a resource-backed text-file loader is a maintainable fit for the existing Settings architecture. The remaining question is whether the initial license list is the complete intended release scope.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 4440226d52c2.

Label changes:

• add P3: This is a low-risk user-facing iOS settings/compliance feature with limited runtime blast radius.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The PR has the protected maintainer label, so the external contributor proof gate is not applied; the body reports focused xcodebuild and Maestro validation, though the local screenshot path is not publicly inspectable.

Label justifications:

• P3: This is a low-risk user-facing iOS settings/compliance feature with limited runtime blast radius.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The PR has the protected maintainer label, so the external contributor proof gate is not applied; the body reports focused xcodebuild and Maestro validation, though the local screenshot path is not publicly inspectable.

PR surface:

Docs +14, Other +342. Total +356 across 11 files.

What I checked:

• Current main lacks the requested screen: Current SettingsRoute has no .licenses case and current Settings rows end at About, so the central feature is not already implemented on main. (apps/ios/Sources/Design/SettingsProTabSupport.swift:6, 4440226d52c2)
• PR adds the route and destination: The PR adds the Licenses row, routes .licenses to licensesDestination, and renders document rows with navigation to detail views. (apps/ios/Sources/Design/SettingsProTabSections.swift:171, 1cff0c52481f)
• PR adds resource-backed license loading: LicenseDocumentLoader discovers regular UTF-8 .txt files under Licenses, derives display titles from filenames, skips hidden/non-text/empty files, and sorts by title. (apps/ios/Sources/Design/LicenseDocuments.swift:14, 1cff0c52481f)
• PR bundles the license folder as app resources: The XcodeGen spec adds Resources/Licenses as a folder resource for the iOS app target, matching the loader's Bundle.main.resourceURL/Licenses lookup. (apps/ios/project.yml:63, 1cff0c52481f)
• Dependency license text checked: The added ElevenLabsKit and WebRTC license files match the upstream license files for steipete/ElevenLabsKit tag 0.1.1 and stasel/WebRTC tag 147.0.0. (apps/ios/Resources/Licenses/ElevenLabsKit.txt:1, 1cff0c52481f)
• Validation context: Live PR status showed the PR is mergeable with many relevant checks already successful, including native-i18n, ios-build, macos-swift, dependency/security guards, and iOS dead-code scan; a few broad CI shards were still running during review. (1cff0c52481f)

Likely related people:

• steipete: Recently modernized the iOS Settings design and iOS project configuration that this PR extends. (role: recent area contributor; confidence: high; commits: 313560d5b98e, 8502ef6c598b; files: apps/ios/Sources/Design/SettingsProTabSections.swift, apps/ios/project.yml)
• joshavant: Has prior merged work on iOS Settings, notification UX, App Store/release configuration, and the project file, beyond authoring this PR. (role: recent iOS settings and release contributor; confidence: high; commits: 0bd2aa8ee057, 1168ac2fcd2b, d4f666874f3a; files: apps/ios/Sources/Design/SettingsProTabSupport.swift, apps/ios/Sources/Design/SettingsProTabSections.swift, apps/ios/project.yml)
• Solvely-Colin: Helped introduce and evolve the Pro iOS Settings/app surfaces that the new screen plugs into. (role: feature history owner; confidence: medium; commits: f6e51ff99af4, bf89552e6783; files: apps/ios/Sources/Design/SettingsProTab.swift, apps/ios/Sources/Design/SettingsProTabSections.swift, apps/ios/Tests/SwiftUIRenderSmokeTests.swift)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.