[frdomovic]

What and why

Calimero core 1.0 removed /admin-api, /jsonrpc, relays, delegated execution and mero-auth. Clients now talk to attested cluster nodes over the sealed channel and sign in with passkeys. This PR moves the iOS Mero Models app onto swift-sdk's 1.0 port. Android, the web app/ and logic/ are untouched.

• SDK pin: swift-sdk is pinned to 6c5f1167d1e586f556f59c326de5f51d034e80dd, the head of feat/calimero-1.0 (swift-sdk#85). The pin is set in project.yml and ModelsCore/Package.swift. The pin moves to the merge commit once swift-sdk#85 lands.
• Sign-in:
  • It uses a passkey on the studio's cluster (MeroAppSession.signIn()), with "Create an account" for signUp(name:). The session lives in the Keychain and is refreshed at launch.
  • "Choose your cluster" / "Change" takes a node URL and a Development cluster switch, which sets allowMock for merod local. On such a node the app keeps a soft passkey and creates the account on first sign-in.
  • The cluster can also be set in project.yml with MeroNodeURL, MeroNodes and MeroAllowMock. The wallet, Cloud-manager and registry keys are gone.
• Vocabulary: studios are organizations and scenes are app instances, either org-wide or in a team. Code comments and the ids under "About this scene" use the 1.0 words.
• Invitations:
  • Links keep the same URL and the {invitation, namespaceId, contextId} keys.
  • The payload is now swift-sdk's OrgInvitation: invitation is the inv_… token string. A pre-1.0 signed invitation is refused.
  • Joining redeems the token with POST /invites/{token}/redeem.
• Blobs: meshes and textures are read with MeroAppBackend.getBlob (/apps/{app}/blobs) instead of the removed client.admin.
• Approvals:
  • A new "Needs your approval" section on the studios list shows the pending node releases and app upgrades that are the account's to decide, for its own apps and for each studio.
  • "Review" opens the node's consent page in the system browser (MeroAppSession.requestConsent), which returns to mero-models://consent.
  • The logic is ApprovalsModel in ModelsCore.
• Errors: the typed 1.0 errors read as words, including ReleaseDeadlineError, NotFound, LoginRequired, WrongNode, UnavailableError and AppError.
• Docs: the mobile README's iOS parts describe the pin and the 1.0 flow.

Verification

• swift test --package-path ModelsCore on macOS: 21 tests pass. They run on InMemoryAppBackend and cover the invite-link round trip, approvals built from node-shaped reports, the consent flow, and the error text.
• xcodegen generate, then xcodebuild build -destination 'generic/platform=iOS' CODE_SIGNING_ALLOWED=NO: BUILD SUCCEEDED, with no warnings in app sources.
• No simulator was used, and nothing ran against a live cluster or end to end.

Gaps

• Associated Domain: passkeys on a real cluster need the webcredentials:<rp-id> Associated Domain. The cluster's rp-id isn't known yet, so it isn't set. The README notes it.
• Android and web interop: the Android app still speaks 0.x, and so does the web studio until mero-react is ported. Until then, links minted on iOS don't open there, and the reverse.
• Demo mode: the app has no demo mode, so there was nothing to keep.

🤖 Generated with Claude Code