path-terminal-init 0.2.3 → 0.2.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "path-terminal-init",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "description": "One-line setup for the Path Terminal SDK integration assistant — connects the user's AI agent to the Path MCP server and installs the per-OS integration recipe (iOS, Android, Windows). The single source of truth for the bootstrap CLI and the recipes.",
   "bin": {
     "path-terminal-init": "dist/cli.js"

package/rules/android/path-integration-android.mdc

@@ -248,6 +248,32 @@ Call `validate_integration` with platform='android' on your code before finalisi
 
 ---
 
+### Step 3.5 — Compile the changes (check the environment first)
+
+Confirm your code compiles against the SDK's **real** API — this catches wrong method
+names / signatures the examples can't guarantee. But **probe the build toolchain first**,
+and treat a missing one as an environment limitation to advise on, **never as a failure**:
+
+1. Probe (non-fatal — just checking):
+   - `command -v java && java -version` — a JDK 17+ on PATH?
+   - `echo "$ANDROID_HOME"`, `ls ~/Library/Android/sdk 2>/dev/null`, or an Android Studio
+     install — is the Android SDK available?
+
+2. **Toolchain present** → run `./gradlew assembleDebug` (or `compileDebugKotlin` for speed).
+   Fix any real API mismatches, then continue to Step 4.
+
+3. **Toolchain absent** → the integration code is complete; you simply can't compile *here*.
+   Do **not** report this as an error or a failed install. Instead:
+   - Check `command -v brew`. If Homebrew is available, **offer** (don't assume) to install the
+     toolchain — `brew install openjdk@21` plus the Android command-line tools — explaining
+     what it does and that it's optional.
+   - If Homebrew is absent, or the developer would rather not, tell them plainly:
+     *"The integration code is done — I can't compile in this environment. Open the project in
+     Android Studio and build; paste back any errors and I'll fix them."* Then summarise every
+     file you changed so they can review and build with confidence.
+
+Frame a missing build toolchain as **"here's how to verify"**, never as a failure of the work.
+
 ### Step 4 — Verify it works end to end
 
 1. Confirm the Application/MainActivity injects `PathTerminalAdapter` (not the old adapter).

package/rules/ios/path-integration.mdc

@@ -311,6 +311,22 @@ If `PathPaymentTerminalAdapter.swift` does not exist, create it:
 
 ---
 
+### Step 3.5 — Build to catch API mismatches (check the environment first)
+
+Confirm your Swift compiles against the SDK's **real** API. **Probe the toolchain first**, and
+treat a missing one as an environment limitation to advise on, **never as a failure:**
+
+1. `xcodebuild -version` — is Xcode (or its command-line tools) available?
+2. **Present** → you may run a build (e.g. `xcodebuild -scheme <App> -destination 'generic/platform=iOS' build`)
+   to surface Swift errors, then fix real API mismatches. (Full runtime verification is the
+   developer's step below — it needs Xcode + a device/simulator.)
+3. **Absent** → the integration code is complete; you just can't build *here*. Do **not** report a
+   failure. Tell the developer plainly: *"The code is done — open the project in Xcode and build;
+   paste back any errors and I'll fix them,"* and summarise every file you changed. (Xcode installs
+   from the App Store, not a package manager — don't offer to install it.)
+
+Frame a missing build toolchain as **"here's how to verify"**, never as a failure of the work.
+
 ### Step 4 — Verify it works end to end
 
 1. Confirm the app entry point injects `PathPaymentTerminalAdapter()`.

package/rules/windows-10/path-integration-windows10.mdc

@@ -180,6 +180,21 @@ Confirm the transaction methods map correctly:
 
 ---
 
+### Step 3.5 — Build to catch API mismatches (check the environment first)
+
+Confirm your C# compiles against the SDK's **real** API. **Probe the toolchain first**, and
+treat a missing one as an environment limitation to advise on, **never as a failure:**
+
+1. `dotnet --version` — is the .NET SDK / MSBuild available? (net48 builds need it.)
+2. **Present** → run `dotnet build src\Path.Epos.TestHarness.Wpf\Path.Epos.TestHarness.Wpf.csproj`,
+   fix any real API mismatches, then continue to Step 4.
+3. **Absent** → the code is complete; you just can't build *here*. Do **not** report a failure.
+   If a package manager is present, **offer** to install the .NET SDK (`winget install Microsoft.DotNet.SDK.8`
+   or `choco install dotnet-sdk`); otherwise tell the developer: *"The code is done — build in Visual
+   Studio or with `dotnet build` and paste back any errors,"* and summarise the files you changed.
+
+Frame a missing build toolchain as **"here's how to verify"**, never as a failure of the work.
+
 ### Step 4 — Verify it works end to end
 
 1. Confirm the app composes the Path-backed service, not `OCPayTerminalAdapter`.

package/rules/windows-11/path-integration-windows11.mdc

@@ -174,6 +174,21 @@ Confirm the transaction methods map correctly:
 
 ---
 
+### Step 3.5 — Build to catch API mismatches (check the environment first)
+
+Confirm your C# compiles against the SDK's **real** API. **Probe the toolchain first**, and
+treat a missing one as an environment limitation to advise on, **never as a failure:**
+
+1. `dotnet --version` — is the .NET 10 SDK available?
+2. **Present** → run `dotnet build Path.Epos.TestHarness.sln -c Debug`, fix any real API
+   mismatches, then continue to Step 4.
+3. **Absent** → the code is complete; you just can't build *here*. Do **not** report a failure.
+   If a package manager is present, **offer** to install the .NET 10 SDK (`winget install Microsoft.DotNet.SDK.10`);
+   otherwise tell the developer: *"The code is done — build in Visual Studio or with `dotnet build`
+   and paste back any errors,"* and summarise the files you changed.
+
+Frame a missing build toolchain as **"here's how to verify"**, never as a failure of the work.
+
 ### Step 4 — Verify it works end to end
 
 1. Confirm the app root composes the Path-backed manager, not `OCPayTerminalAdapter`.