path-terminal-init 0.2.6 → 0.2.7

package/README.md

@@ -9,6 +9,12 @@ a real Verifone terminal — guided by the recipe and the MCP server's tools.
 **This repo is the single source of truth** for both the bootstrap CLI and the recipes.
 `Path-mcp-server` serves them (`/rules`, `/init.js`) from here — there are no duplicate copies.
 
+> **Tuning the install process?** It's a *pair* of repos, not just this one:
+> - **`Path-terminal-init`** (here) — the **recipes/rules** (`rules/**/*.mdc`) the agent follows + the CLI. Changes reach partners only after **`npm publish`** (version bump + 2FA).
+> - **`Path-mcp-server`** — the **code examples** the agent pulls (`get_code_example`) + MCP prompts/tools. Changes go live only after a **deploy to the box** (mcp.path2ai.tech).
+>
+> A single behaviour change usually touches **both** (the rule says *what*, the MCP example gives the *code*) — tune one without the other and they drift. Then **update the Terminal Bible** (§12 Distribution & releases) so the docs stay current. Distribution/versioning specifics per platform live in the SDK repos.
+
 ## Layout
 
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "path-terminal-init",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "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/ios/path-integration.mdc

@@ -24,11 +24,14 @@ You have access to the Path MCP server at mcp.path2ai.tech:
 > **Check whether the Swift Package is installed before doing anything else.**
 > Run:
 > ```
-> grep -c "path-terminal-sdk\|PathTerminalSDK" $(find . -maxdepth 2 -name "project.pbxproj" ! -path "*/DerivedData/*" | head -1)
+> find . -name "project.pbxproj" ! -path "*/DerivedData/*" ! -path "*/Pods/*" ! -path "*/.build/*" ! -path "*/SourcePackages/*" -exec grep -l "path-terminal-sdk\|PathTerminalSDK" {} +
 > ```
-> - **Count > 0** — package is already in the project. Do not mention SPM or
+> (Searches the project at **any** depth — the app's `.xcodeproj` is often nested
+> a folder or two below the repo root — so the check can't miss it. Prints the
+> project file if the package is present, nothing if it is not.)
+> - **Prints a path** — package is already in the project. Do not mention SPM or
 >   package installation anywhere in your output. Proceed directly to Step 1.
-> - **Count = 0** — package is not yet added. Tell the developer to add it:
+> - **Prints nothing** — package is not yet added. Tell the developer to add it:
 >   1. Open Xcode → **File → Add Package Dependencies…**
 >   2. Enter URL: `https://github.com/keyman12/path-terminal-sdk`
 >   3. In the **Add to Target** sheet, tick **all four** products:
@@ -231,10 +234,10 @@ sale/refund flow on it — it is fire-and-forget branding, not part of a transac
 Before triggering the first build, run:
 
 ```
-grep -c "PBXFrameworksBuildPhase" $(find . -maxdepth 2 -name "project.pbxproj" ! -path "*/DerivedData/*" | head -1)
+find . -name "project.pbxproj" ! -path "*/DerivedData/*" ! -path "*/Pods/*" ! -path "*/.build/*" ! -path "*/SourcePackages/*" -exec grep -l "PBXFrameworksBuildPhase" {} +
 ```
 
-If the count is **0**, the Frameworks build phase is missing and the build will
+If this prints **nothing**, the Frameworks build phase is missing and the build will
 fail with `Undefined symbol` linker errors for PathTerminalSDK / PathEmulatorAdapter
 / PathCoreModels. Fix it now — do not wait for the build to fail.
 
@@ -242,7 +245,7 @@ fail with `Undefined symbol` linker errors for PathTerminalSDK / PathEmulatorAda
 
 1. Find the four package product UUIDs from the target's `packageProductDependencies`:
    ```
-   grep -A 8 "packageProductDependencies" $(find . -maxdepth 2 -name "project.pbxproj" ! -path "*/DerivedData/*" | head -1)
+   find . -name "project.pbxproj" ! -path "*/DerivedData/*" ! -path "*/Pods/*" ! -path "*/.build/*" ! -path "*/SourcePackages/*" -exec grep -A 8 "packageProductDependencies" {} +
    ```
    You will see something like:
    ```