feat(mobile): bootstrap native iOS and Android app shells

[tataihono]

Background

mobile/ios and mobile/android exist but are scaffold-level and not yet fully runnable as native app shells.
We need a stable foundation before data integration and CI build gates.

Expected outcome

Both native apps have compile-ready shells with clear local build commands and minimal startup screens, establishing a reliable baseline for follow-on GraphQL and CI work.

Acceptance criteria

• iOS has a buildable app target/scheme (not package-only) with a minimal startup screen.
• Android has complete app entry wiring (manifest/activity/resources) and a minimal startup screen.
• Local debug build commands are documented and verified for both platforms.
• Scope stays platform-native (SwiftUI + Kotlin/Compose) with no shared business logic.

Possible solution(s)

1. iOS: create app target/workspace and wire a minimal SwiftUI app entrypoint.
2. Android: complete app module runtime wiring and verify assembleDebug.

References

• mobile/README.md
• mobile/ios/README.md
• mobile/android/README.md
• mobile/ios/Package.swift
• mobile/android/app/build.gradle.kts

[Ur-imazing]

Execution plan (agent 80-bootstrap-native-app-shells)

• Branch: feat/80-bootstrap-native-app-shells from main
• Android: Added AndroidManifest.xml, MainActivity (Compose), Theme.kt, res/values, buildFeatures { compose = true } in app/build.gradle.kts. Local build: ./gradlew assembleDebug
• iOS: Hand-crafted App/ForgeMobileApp.xcodeproj with app target, local Swift package dependency on ForgeMobile, @main entry in ForgeAppEntry.swift, shared scheme ForgeMobileApp. Local build: open project in Xcode or xcodebuild -scheme ForgeMobileApp -destination 'platform=iOS Simulator,name=iPhone 16' build from mobile/ios/App
• Docs: mobile/README.md, mobile/ios/README.md, mobile/android/README.md updated with local build commands
• PR: feat(mobile): bootstrap native iOS and Android app shells #87