ci(ios): source-only validation - #861
Draft
pascalandr wants to merge 1 commit into
Draft
pascalandr wants to merge 1 commit into
pascalandr wants to merge 1 commit into
Conversation
Layer an explicitly source-only Linux PR/manual workflow over the Android companion foundation. Validate locked launcher dependencies, source contracts, bundle, Tauri ABI provenance and pure Rust authority policy with immutable actions and read-only permissions; do not generate Apple projects, compile native iOS, sign or export. Document the exact stopped experimentation state for Shantur: component/object compilation is not application linking or executed FFI, Array-derived pointer lifetimes remain unqualified, runtime and confinement gates remain open and the exhausted Apple transport path must not be retried. Require a supported owned Mac/device and separately approved unsigned validation contract before further native work; warn that the current distribution script is not a default validation command. Keep private environment-bound diagnostics out of the public handoff, preserve native evidence and call out server exposure/dependency and store minimum-functionality limits. Normalize workflow-test CRLF reads and link the handoff from the README. Latest integration passes20/20 source tests without JDK skip, typecheck and ABI142/13 verification; GitHub source results remain separate from native readiness.
pascalandr
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked source/handoff PR
Depends on Android foundation #860; base is
feat/android-companion-ci, notdev, so this PR contains only the iOS preparation delta. Retarget after the foundation is integrated. Both PRs remain drafts: neither certifies mobile delivery.IOS_HANDOFF.mdfor Shantur, linked from README, with stopped attempts, actual achieved state, unresolved gates and next supported Mac/iPhone checklist. No automatic assignment or notification.Honest state
The stacked head also passed Android source + debug APK CI: run 37446119356, with short-lived artifact 11403981660. This is Android regression/build evidence, never an iOS native build. Existing desktop draft-only jobs are skipped, not validated by these mobile checks.
The foundation's Android source + debug APK CI passed, with a hash-verified short-lived test artifact. This does not qualify Android on device or iOS natively.
GitHub SOURCE CI passed: run 37446119417, head
c4ea5895c7678718de3b7d205ef4b5a38aecfea9. This is Linux source/policy validation, not a native iOS build.Local latest-dev source integration passed 20/20 JS tests without JDK skip, mobile typecheck, launcher build/browser, pure Rust policy 4/4 and ABI verification 142 upstream files / 13 guard inputs. GitHub execution is separate evidence, never proof of an iOS application.
Historical ARM64-device/Intel-simulator Swift component objects are not a linked
.app, IPA or executed Rust↔Swift FFI. Array-derived pointer lifetimes, boundary IDs/ownership, exact simulator runtime, native Swift/linker confinement and WKWebView/device behavior remain unqualified. Local native iOS experimentation is stopped, and no further Mac/VM/SSH, exhausted Apple transport, sandbox broadening or diagnostic attempts are authorized here.Shantur can review sources/CI first, then agree a supported owned Mac/device builder and unsigned non-distribution validation contract with fresh approval. The current
ios:buildrequestsapp-store-connectexport and is explicitly not a default validation command. Signing, accounts, provisioning and store submission require separate operator authorization; App Review 4.2 acceptance is not guaranteed.Private environment-bound probes, caches/crashes and transport receipts remain preserved outside publication. An involuntary rustup toolchain installation during earlier Windows source preparation is disclosed; no cleanup or native test replay was performed. No mobile/store readiness is claimed.