path-terminal-init 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md ADDED
@@ -0,0 +1,67 @@
1
+ # path-terminal-init
2
+
3
+ One-line setup for the **Path Terminal SDK integration assistant**. It connects the
4
+ user's AI coding agent (Claude Code or Cursor) to the Path MCP help server and installs
5
+ the right **per-OS integration recipe** into their EPOS project. The agent then wires the
6
+ Path SDK in — a backend switcher for the emulator (Wi-Fi/IP by default, or Bluetooth) and
7
+ a real Verifone terminal — guided by the recipe and the MCP server's tools.
8
+
9
+ **This repo is the single source of truth** for both the bootstrap CLI and the recipes.
10
+ `Path-mcp-server` serves them (`/rules`, `/init.js`) from here — there are no duplicate copies.
11
+
12
+ ## Layout
13
+
14
+ ```
15
+ src/cli.ts the bootstrap program
16
+ rules/
17
+ ios/path-integration.mdc iOS (Swift / SPM)
18
+ android/path-integration-android.mdc Android (Kotlin / Gradle)
19
+ windows-11/path-integration-windows11.mdc Windows 11 (WinUI 3 / .NET 10)
20
+ windows-10/path-integration-windows10.mdc Windows 10 (WPF / .NET Framework 4.8)
21
+ build.mjs builds dist/cli.js + dist/init.js
22
+ ```
23
+
24
+ ## How a customer runs it
25
+
26
+ **Android (nothing to install but Node) — fetched from the help server:**
27
+ ```bash
28
+ node <(curl -s https://mcp.path2ai.tech/init.js) --agent claude
29
+ ```
30
+
31
+ **iOS — once published to npm:**
32
+ ```bash
33
+ npx path-terminal-init
34
+ ```
35
+ Until then, from a checkout:
36
+ ```bash
37
+ node /path/to/Path-terminal-init/dist/cli.js
38
+ ```
39
+
40
+ The CLI writes a `.mcp.json` (connecting the agent to `https://mcp.path2ai.tech`), adds the
41
+ SDK dependency, and drops the matching recipe into `.cursor/rules/` and/or `CLAUDE.md`.
42
+
43
+ ## Develop locally
44
+
45
+ ```bash
46
+ npm install
47
+ npm run build # → dist/cli.js (installable) + dist/init.js (standalone bundle)
48
+ npm run typecheck
49
+ node dist/cli.js --help
50
+ ```
51
+
52
+ ## Two artifacts, one source
53
+
54
+ - `dist/cli.js` — the installable CLI. Reads recipes from the local `rules/<os>/` folder.
55
+ - `dist/init.js` — a self-contained bundle for the `curl … | node` one-liner. It runs with
56
+ no local `rules/` folder, so it fetches the recipe from the server's `/rules` endpoint.
57
+
58
+ `Path-mcp-server` serves `dist/init.js` at `/init.js` and the `rules/` files at `/rules*`.
59
+ Its deploy copies them from this repo, so the server is never a stale duplicate.
60
+
61
+ ## Publish to npm (for `npx path-terminal-init`)
62
+
63
+ ```bash
64
+ npm login
65
+ npm publish --access public
66
+ npm view path-terminal-init version
67
+ ```