@radhya/mach 2.1.1 → 2.1.3

package/docs/frameworks/expo.md

@@ -114,6 +114,10 @@ For iOS store builds, set:
 }
 ```
 
+`"auto"` makes Mach allocate the next scoped Dashboard counter value. You can instead provide an explicit Android positive integer or an iOS value such as `"68"` or `"1.2.3"`; Mach then uses that exact value without incrementing.
+
+Mach applies the resolved value after Expo prebuild, so `app.json` or `app.config.*` cannot silently replace it. The Expo `version` field remains the public marketing version. Mach verifies the packaged IPA/AAB/APK native version before reporting a successful build.
+
 This updates native build numbers only. Apple also requires the marketing version to increase when a released version train is closed. In Expo projects, that is usually `expo.version` in `app.json` or `app.config.*`.
 
 ## Common Commands

package/docs/frameworks/react-native.md

@@ -90,6 +90,8 @@ Mach uses the existing native iOS project. If multiple schemes exist, set the sc
 
 For store builds, upload iOS signing credentials and App Store Connect credentials from the Dashboard or CLI.
 
+`ios.buildNumber: "auto"` allocates the next scoped Dashboard value. An explicit value is used exactly as configured. Mach applies the resolved value to the app and extension targets, then verifies the final IPA before upload.
+
 ## Android Notes
 
 Mach runs Gradle from `android/gradlew` when present. Production builds default to `bundleRelease`; internal builds default to `assembleRelease`; development-client style builds default to `assembleDebug`.
@@ -107,6 +109,8 @@ Set package and version code at the root:
 
 For Google Play submission, upload a Google Play service account credential for the exact package id. Mach-managed versionCode assignment uses the Dashboard counter and does not require a Google Play service key.
 
+An explicit `android.versionCode` is used without incrementing the Dashboard counter. The `"auto"` value enables atomic counter allocation. Mach injects the resolved value at the Gradle variant level (including Groovy or Kotlin DSL projects) and verifies the packaged APK/AAB before upload.
+
 ## Development Builds
 
 Bare React Native does not use Expo development-client behavior. If a profile contains `developmentClient`, Mach ignores Expo-only dev-client environment handling unless `framework` is `expo`.

package/docs/push.md

@@ -22,6 +22,8 @@ The command writes public SDK values to a generated file. It creates a separate
 application-owned callback file for foreground notifications, notification
 taps, registration, permission changes, and errors. Running setup again
 refreshes generated configuration but never overwrites those callbacks.
+If an administrator deleted the server-side push app, running setup again
+detects the stale local key and safely creates or links a replacement.
 
 Expo setup also installs and wires `@radhya/mach/expo-plugin`. The plugin adds
 the APNs entitlement, Android notification permission, Firebase config path,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@radhya/mach",
-  "version": "2.1.1",
+  "version": "2.1.3",
   "description": "Mach CLI: Cloud Build Orchestrator for React Native & Expo",
   "main": "dist/index.js",
   "type": "module",