muesli-hq Muesli Dev Build Lanes
Overview
Use this skill to build and reason about local Muesli dev apps across multiple worktrees without overwriting app bundles, sharing support data, or accidentally requiring iCloud/APNs entitlements.
Core Workflow
- Read
AGENTS.mdfirst for current scratch-path and lane policy. - Inspect
scripts/dev-test.sh,scripts/build_native_app.sh, andscripts/muesli_spm_cache.shbefore changing build behavior. - Preserve default
./scripts/dev-test.shbehavior unless explicitly changing the default dev app. - Prefer fixed lanes
A,B, andC; do not create arbitrary branch-named bundle IDs unless the user explicitly accepts repeated macOS permission prompts. - Do not delete app support data or reset TCC permissions unless explicitly asked.
Lane Mapping
Default dev app:
App: /Applications/MuesliDev.app
Bundle ID: com.muesli.dev
Support: ~/Library/Application Support/MuesliDev
Fixed lanes:
A -> MuesliDevA, com.muesli.dev.a, process MuesliDevA, ~/Library/Application Support/MuesliDevA
B -> MuesliDevB, com.muesli.dev.b, process MuesliDevB, ~/Library/Application Support/MuesliDevB
C -> MuesliDevC, com.muesli.dev.c, process MuesliDevC, ~/Library/Application Support/MuesliDevC
Entitlement Modes
Use local-only entitlements when testing non-sync features:
./scripts/dev-test.sh --lane A --local-only
Named lanes default to local-only entitlements. This uses scripts/MuesliLocalOnly.entitlements and clears provisioning/APNs env for the build.
Use cloud entitlements only when iCloud/APNs behavior is under test and the bundle ID has a matching Apple Developer profile:
MUESLI_PROVISIONING_PROFILE="/path/to/profile.provisionprofile" \
MUESLI_SIGN_IDENTITY="Apple Development: Name (TEAMID)" \
MUESLI_CODESIGN_TIMESTAMP=none \
./scripts/dev-test.sh --lane A --cloud-entitlements
Plain ./scripts/dev-test.sh keeps the existing cloud-entitlement-capable MuesliDev behavior.
Build Cache Rules
Use the shared SwiftPM scratch path resolver. For direct SwiftPM commands, pass --scratch-path yourself. Never run concurrent worktrees into the same scratch path.
If /Volumes/MuesliBuildCache/muesli-spm is mounted, prefer it. Otherwise scripts fall back to ~/Library/Caches/muesli-spm.