mecord-connect 1.0.0 → 2.0.0

package/DISCLOSURE

@@ -1,47 +1,47 @@
-MECORD CONNECT — DUAL-USE CONTENT DISCLOSURE
-
-Package: mecord-connect
-Publisher: Kinthala Samuel Sampath Kumar
-Contact: support@splcart.in
-
-Purpose
-
-mecord-connect is the Windows runtime used to pair a user-authorized computer with Mecord Connect for legitimate development and computer-automation workflows initiated through ChatGPT.
-
-Why this package is declared dual-use
-
-The package contains security-relevant remote-management capabilities because it can:
-- connect a local runtime to an authenticated remote relay;
-- inspect and modify files within locally authorized project roots;
-- expose bounded Git/project operations;
-- run locally trusted project commands subject to policy and approval controls;
-- interact with browser/UI automation capabilities that are available to the private local runtime but are not broadly exposed by the public plugin.
-
-These capabilities can be useful for legitimate development, administration, automation, support, and security work, but similar capabilities could be misused if operated without authorization. For that reason the package declares:
-
-  "contentPolicy": {
-    "class": "dual-use"
-  }
-
-Intended legitimate use
-
-The Runtime is intended only for computers, accounts, repositories, websites, data, and services the user owns or is authorized to control.
-
-Safeguards
-
-Mecord Connect is designed to reduce misuse through multiple independent controls, including:
-- authenticated OAuth access to the hosted MCP service;
-- explicit device pairing and signed device identity;
-- locally enforced capability policy and authorized filesystem roots;
-- approval requirements for risk-bearing operations;
-- restricted public plugin tooling rather than unrestricted terminal/browser/UIA exposure;
-- credential/restricted-data guards and minimized public responses;
-- fail-closed relay/session behavior;
-- ambient credential stripping in the npm launcher;
-- immutable source/payload binding, integrity hashes, and Windows-native helper self-tests.
-
-The package is not intended to provide stealth, persistence, credential theft, malware delivery, access-control bypass, or unauthorized surveillance.
-
-Security and abuse reports
-
-Report suspected abuse or security issues privately to support@splcart.in. Do not send live passwords, access tokens, private keys, recovery credentials, or other active secrets.
+MECORD CONNECT — DUAL-USE CONTENT DISCLOSURE
+
+Package: mecord-connect
+Publisher: Kinthala Samuel Sampath Kumar
+Contact: support@splcart.in
+
+Purpose
+
+mecord-connect is the Windows runtime used to pair a user-authorized computer with Mecord Connect for legitimate development and computer-automation workflows initiated through ChatGPT.
+
+Why this package is declared dual-use
+
+The package contains security-relevant remote-management capabilities because it can:
+- connect a local runtime to an authenticated remote relay;
+- inspect and modify files within locally authorized project roots;
+- expose bounded Git/project operations;
+- run locally trusted project commands subject to policy and approval controls;
+- interact with browser/UI automation capabilities that are available to the private local runtime but are not broadly exposed by the public plugin.
+
+These capabilities can be useful for legitimate development, administration, automation, support, and security work, but similar capabilities could be misused if operated without authorization. For that reason the package declares:
+
+  "contentPolicy": {
+    "class": "dual-use"
+  }
+
+Intended legitimate use
+
+The Runtime is intended only for computers, accounts, repositories, websites, data, and services the user owns or is authorized to control.
+
+Safeguards
+
+Mecord Connect is designed to reduce misuse through multiple independent controls, including:
+- authenticated OAuth access to the hosted MCP service;
+- explicit device pairing and signed device identity;
+- locally enforced capability policy and authorized filesystem roots;
+- approval requirements for risk-bearing operations;
+- restricted public plugin tooling rather than unrestricted terminal/browser/UIA exposure;
+- credential/restricted-data guards and minimized public responses;
+- fail-closed relay/session behavior;
+- ambient credential stripping in the npm launcher;
+- immutable source/payload binding, integrity hashes, and Windows-native helper self-tests.
+
+The package is not intended to provide stealth, persistence, credential theft, malware delivery, access-control bypass, or unauthorized surveillance.
+
+Security and abuse reports
+
+Report suspected abuse or security issues privately to support@splcart.in. Do not send live passwords, access tokens, private keys, recovery credentials, or other active secrets.

package/LICENSE

@@ -1,64 +1,64 @@
-MECORD CONNECT RUNTIME LICENSE AGREEMENT
-
-Copyright (c) 2026 Kinthala Samuel Sampath Kumar. All rights reserved.
-
-This Mecord Connect Runtime License Agreement ("Agreement") governs your use of the software distributed as the mecord-connect package, including its bundled runtime payload, launchers, native helpers, updates, and accompanying documentation (collectively, the "Runtime").
-
-Licensor
-Kinthala Samuel Sampath Kumar
-Akkayapalem, Visakhapatnam, Andhra Pradesh, India
-Support contact: support@splcart.in
-
-1. License Grant
-
-Subject to this Agreement, the Licensor grants you a limited, non-exclusive, revocable, non-transferable, non-sublicensable license to install and use the Runtime on computers and accounts that you own or are authorized to control, solely for legitimate use with Mecord Connect and its supported local-development workflows.
-
-2. Permitted Use
-
-You may:
-- install and run the Runtime on authorized Windows computers;
-- use it to connect an authorized computer to Mecord Connect;
-- use functionality exposed through the Runtime only within the authorization, safety, approval, and access-control boundaries provided by Mecord Connect and the local Runtime;
-- make a reasonable backup copy solely for your own permitted use where applicable law allows.
-
-3. Restrictions
-
-Unless applicable law expressly requires otherwise, you may not:
-- redistribute, sell, sublicense, rent, lease, host, mirror, or republish the Runtime or a modified copy;
-- remove or alter copyright, license, safety, provenance, or security notices;
-- reverse engineer, decompile, disassemble, or attempt to derive source code from compiled components except to the limited extent such restriction is prohibited by applicable law;
-- bypass, disable, tamper with, or circumvent pairing, authentication, local approvals, capability policy, authorized-root restrictions, credential protections, rate limits, security checks, or other safeguards;
-- use the Runtime to access computers, accounts, data, services, repositories, or networks without authorization;
-- use the Runtime to distribute malware, steal credentials, evade access controls, interfere with systems, or violate applicable law or third-party rights.
-
-4. Ownership
-
-The Runtime is licensed, not sold. The Licensor and applicable contributors retain all right, title, and interest in and to the Runtime and all associated intellectual-property rights, except for third-party components governed by their own licenses.
-
-5. Hosted Services and Third Parties
-
-The Runtime may connect to Mecord Connect hosted services and third-party services. Access to those services may be subject to separate terms, privacy notices, availability limits, provider rules, and charges. This Agreement does not grant rights in third-party software or services.
-
-6. Updates and Changes
-
-The Licensor may update, replace, suspend, or discontinue the Runtime or related hosted functionality. Updated versions may require acceptance of updated terms where permitted by law.
-
-7. Termination
-
-This Agreement terminates automatically if you materially breach it. Upon termination, you must stop using and delete copies of the Runtime, except where retention is required by law. Provisions that by their nature should survive termination, including ownership, restrictions, disclaimers, liability limits, and governing law, survive.
-
-8. Disclaimer
-
-TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE RUNTIME IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR UNINTERRUPTED OR ERROR-FREE OPERATION. NOTHING IN THIS AGREEMENT EXCLUDES WARRANTIES OR RIGHTS THAT CANNOT LEGALLY BE EXCLUDED.
-
-9. Limitation of Liability
-
-TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSOR WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, OR FOR LOSS OF PROFITS, REVENUE, DATA, BUSINESS, OR GOODWILL ARISING FROM OR RELATED TO THE RUNTIME. NOTHING IN THIS AGREEMENT LIMITS LIABILITY THAT CANNOT LEGALLY BE LIMITED.
-
-10. Governing Law and Jurisdiction
-
-This Agreement is governed by the laws of India. Subject to mandatory consumer-protection and jurisdiction rules that cannot be waived, disputes relating to this Agreement are subject to the competent courts at Visakhapatnam, Andhra Pradesh, India.
-
-11. Contact
-
-Questions about this Agreement may be sent to support@splcart.in.
+MECORD CONNECT RUNTIME LICENSE AGREEMENT
+
+Copyright (c) 2026 Kinthala Samuel Sampath Kumar. All rights reserved.
+
+This Mecord Connect Runtime License Agreement ("Agreement") governs your use of the software distributed as the mecord-connect package, including its bundled runtime payload, launchers, native helpers, updates, and accompanying documentation (collectively, the "Runtime").
+
+Licensor
+Kinthala Samuel Sampath Kumar
+Akkayapalem, Visakhapatnam, Andhra Pradesh, India
+Support contact: support@splcart.in
+
+1. License Grant
+
+Subject to this Agreement, the Licensor grants you a limited, non-exclusive, revocable, non-transferable, non-sublicensable license to install and use the Runtime on computers and accounts that you own or are authorized to control, solely for legitimate use with Mecord Connect and its supported local-development workflows.
+
+2. Permitted Use
+
+You may:
+- install and run the Runtime on authorized Windows computers;
+- use it to connect an authorized computer to Mecord Connect;
+- use functionality exposed through the Runtime only within the authorization, safety, approval, and access-control boundaries provided by Mecord Connect and the local Runtime;
+- make a reasonable backup copy solely for your own permitted use where applicable law allows.
+
+3. Restrictions
+
+Unless applicable law expressly requires otherwise, you may not:
+- redistribute, sell, sublicense, rent, lease, host, mirror, or republish the Runtime or a modified copy;
+- remove or alter copyright, license, safety, provenance, or security notices;
+- reverse engineer, decompile, disassemble, or attempt to derive source code from compiled components except to the limited extent such restriction is prohibited by applicable law;
+- bypass, disable, tamper with, or circumvent pairing, authentication, local approvals, capability policy, authorized-root restrictions, credential protections, rate limits, security checks, or other safeguards;
+- use the Runtime to access computers, accounts, data, services, repositories, or networks without authorization;
+- use the Runtime to distribute malware, steal credentials, evade access controls, interfere with systems, or violate applicable law or third-party rights.
+
+4. Ownership
+
+The Runtime is licensed, not sold. The Licensor and applicable contributors retain all right, title, and interest in and to the Runtime and all associated intellectual-property rights, except for third-party components governed by their own licenses.
+
+5. Hosted Services and Third Parties
+
+The Runtime may connect to Mecord Connect hosted services and third-party services. Access to those services may be subject to separate terms, privacy notices, availability limits, provider rules, and charges. This Agreement does not grant rights in third-party software or services.
+
+6. Updates and Changes
+
+The Licensor may update, replace, suspend, or discontinue the Runtime or related hosted functionality. Updated versions may require acceptance of updated terms where permitted by law.
+
+7. Termination
+
+This Agreement terminates automatically if you materially breach it. Upon termination, you must stop using and delete copies of the Runtime, except where retention is required by law. Provisions that by their nature should survive termination, including ownership, restrictions, disclaimers, liability limits, and governing law, survive.
+
+8. Disclaimer
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE RUNTIME IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR UNINTERRUPTED OR ERROR-FREE OPERATION. NOTHING IN THIS AGREEMENT EXCLUDES WARRANTIES OR RIGHTS THAT CANNOT LEGALLY BE EXCLUDED.
+
+9. Limitation of Liability
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSOR WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, OR FOR LOSS OF PROFITS, REVENUE, DATA, BUSINESS, OR GOODWILL ARISING FROM OR RELATED TO THE RUNTIME. NOTHING IN THIS AGREEMENT LIMITS LIABILITY THAT CANNOT LEGALLY BE LIMITED.
+
+10. Governing Law and Jurisdiction
+
+This Agreement is governed by the laws of India. Subject to mandatory consumer-protection and jurisdiction rules that cannot be waived, disputes relating to this Agreement are subject to the competent courts at Visakhapatnam, Andhra Pradesh, India.
+
+11. Contact
+
+Questions about this Agreement may be sent to support@splcart.in.

package/README.md

@@ -1,44 +1,46 @@
-# mecord-connect
-
-One-command Windows runtime for connecting a user-authorized computer to Mecord Connect in ChatGPT.
-
-```powershell
-npx mecord-connect@latest remote
-```
-
-Requires Windows x64 with a supported Node.js line: 22.14+, 24.x, or 26.x. Git features additionally require Git 2.45 or newer; older or missing Git disables only the Git capabilities while the rest of the Mecord Connect runtime remains available.
-
-The command does **not** install an MSIX and does **not** start a local MCP server. It verifies the package's runtime manifest, starts the existing hardened local policy/runtime agent, and connects that agent to the pinned production relay at `wss://operator.splcart.in/device`. ChatGPT talks to the hosted MCP edge.
-
-On first use the runtime prints a one-time device pairing code. Claim that code from Mecord Connect in the authenticated ChatGPT connection. The resulting short-lived relay credential is protected for the current Windows user with DPAPI and is rotated by the existing relay-session authority.
-
-By default the current directory is the authorized filesystem/project root. To authorize another folder explicitly:
-
-```powershell
-npx mecord-connect@latest remote --root C:\path\to\project
-```
-
-Use `--no-browser` to disable automatic launch of Mecord Connect's managed-browser capability. Generic terminal execution remains disabled by default; project commands continue to use the existing policy/approval boundary.
-
-Before starting a session you can verify the package payload and all three Windows-native security helpers:
-
-```powershell
-npx mecord-connect@latest doctor
-```
-
-`doctor` verifies every packaged runtime file against SHA-256/size metadata, exercises the DPAPI and Windows path-lease self-tests, and performs a protocol health check against the UI Automation sidecar. It does not start the relay connection.
-
-## Security model
-
-The npm launcher deliberately rebuilds the child environment from a small desktop allowlist. npm/GitHub/cloud tokens, `.npmrc` pointers, `NODE_OPTIONS`, caller-supplied Mecord Connect relay variables, and other ambient credentials are not inherited by the long-running runtime. The public package pins its relay/result authority to `operator.splcart.in`; callers cannot redirect a paired device by setting environment variables.
-
-The runtime payload is produced from the canonical repository sources at publication time, and includes the native DPAPI, UI Automation, and Windows path-lease helpers compiled in the Windows release workflow. The payload manifest records the exact Git commit and hashes every shipped file.
-
-## Support and policies
-
-- Support: https://operator.splcart.in/support
-- Privacy: https://operator.splcart.in/privacy
-- Terms: https://operator.splcart.in/terms
-- License: proprietary Mecord Connect Runtime License in `LICENSE`
-- Dual-use disclosure: `DISCLOSURE`
-- Issues: https://github.com/sampathkumar-co/Operator-runtime/issues
+# mecord-connect
+
+One-command Windows runtime for connecting a user-authorized computer to Mecord Connect in ChatGPT.
+
+```powershell
+npx mecord-connect@latest remote
+```
+
+Requires Windows x64 with a supported Node.js line: 22.14+, 24.x, or 26.x. Git features additionally require Git 2.45 or newer; older or missing Git disables only the Git capabilities while the rest of the Mecord Connect runtime remains available.
+
+The command does **not** install an MSIX and does **not** start a local MCP server. It verifies the package's runtime manifest, starts the existing hardened local policy/runtime agent, and connects that agent to the pinned production relay at `wss://operator.splcart.in/device`. ChatGPT talks to the hosted MCP edge.
+
+On first use, when human authorization is actually required, the runtime prints the short-lived secure Mecord pairing link **and automatically opens it in the default Windows browser**. Confirm the device in your Mecord account; ChatGPT does not receive a public device-claim tool. The resulting relay credential is protected for the current Windows user with DPAPI. Future `mecord-connect remote` runs reuse the protected device identity/session path and normally reconnect without opening the browser; pairing reappears only after credential loss, revocation, account/device trust change, or another enrollment requirement.
+
+By default the current directory is the authorized filesystem/project root. To authorize another folder explicitly:
+
+```powershell
+npx mecord-connect@latest remote --root C:\path\to\project
+```
+
+Use `--no-browser` to disable automatic launch of Mecord Connect's managed-browser capability. Generic terminal execution remains disabled by default; project commands continue to use the existing policy/approval boundary.
+
+When ChatGPT requests an action that requires local approval, Mecord opens a **local Windows approval card** showing the action, risk and target with **Deny**, **Approve Once**, and **Allow Session**. `Allow Session` is memory-only, bound to the same account/device authority generation plus the current authorized roots/capability scope, expires after 8 hours or 60 minutes idle, and disappears when the runtime exits. It suppresses repeated external/system/destructive prompts inside that scope but never bypasses root scoping, capability allowlists, emergency stop, path safety, restricted-data filtering, or provider-specific allowlists. ChatGPT never receives the recovery authority and cannot approve its own request. The terminal remains a fallback with `approve`, `session`, `deny`, `session-status`, and `revoke-session`.
+
+Before starting a session you can verify the package payload and all three Windows-native security helpers:
+
+```powershell
+npx mecord-connect@latest doctor
+```
+
+`doctor` verifies every packaged runtime file against SHA-256/size metadata, exercises the DPAPI and Windows path-lease self-tests, and performs a protocol health check against the UI Automation sidecar. It does not start the relay connection.
+
+## Security model
+
+The npm launcher deliberately rebuilds the child environment from a small desktop allowlist. npm/GitHub/cloud tokens, `.npmrc` pointers, `NODE_OPTIONS`, caller-supplied Mecord Connect relay variables, and other ambient credentials are not inherited by the long-running runtime. The public package pins its relay/result authority to `operator.splcart.in`; callers cannot redirect a paired device by setting environment variables.
+
+The runtime payload is produced from the canonical repository sources at publication time, and includes the native DPAPI, UI Automation, and Windows path-lease helpers compiled in the Windows release workflow. The payload manifest records the exact Git commit and hashes every shipped file.
+
+## Support and policies
+
+- Support: https://operator.splcart.in/support
+- Privacy: https://operator.splcart.in/privacy
+- Terms: https://operator.splcart.in/terms
+- License: proprietary Mecord Connect Runtime License in `LICENSE`
+- Dual-use disclosure: `DISCLOSURE`
+- Issues: https://github.com/sampathkumar-co/Operator-runtime/issues

package/bin/operator.mjs

@@ -1,10 +1,10 @@
-#!/usr/bin/env node
-import { main } from '../src/cli.mjs';
-
-try {
-  await main(process.argv.slice(2));
-} catch (error) {
-  const message = error instanceof Error ? error.message : String(error);
-  console.error(`[mecord-connect] ${message}`);
-  process.exitCode = 1;
-}
+#!/usr/bin/env node
+import { main } from '../src/cli.mjs';
+
+try {
+  await main(process.argv.slice(2));
+} catch (error) {
+  const message = error instanceof Error ? error.message : String(error);
+  console.error(`[mecord-connect] ${message}`);
+  process.exitCode = 1;
+}

package/package.json

@@ -1,58 +1,58 @@
-{
-  "name": "mecord-connect",
-  "version": "1.0.0",
-  "description": "Secure one-command Mecord Connect runtime for connecting ChatGPT to a user-authorized Windows computer.",
-  "type": "module",
-  "bin": {
-    "mecord-connect": "bin/operator.mjs"
-  },
-  "files": [
-    "bin",
-    "src",
-    "runtime",
-    "README.md",
-    "DISCLOSURE",
-    "LICENSE"
-  ],
-  "engines": {
-    "node": ">=22.14.0 <23 || >=24.0.0 <25 || >=26.0.0 <27"
-  },
-  "os": [
-    "win32"
-  ],
-  "cpu": [
-    "x64"
-  ],
-  "publishConfig": {
-    "access": "public"
-  },
-  "license": "SEE LICENSE IN LICENSE",
-  "scripts": {
-    "build:runtime": "node ./scripts/build-runtime-payload.mjs",
-    "prepublishOnly": "node ./src/publish-check.mjs"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/sampathkumar-co/Operator-runtime.git"
-  },
-  "homepage": "https://operator.splcart.in",
-  "keywords": [
-    "mecord-connect",
-    "chatgpt",
-    "mcp",
-    "windows",
-    "automation",
-    "developer-tools"
-  ],
-  "bugs": {
-    "url": "https://github.com/sampathkumar-co/Operator-runtime/issues",
-    "email": "support@splcart.in"
-  },
-  "contentPolicy": {
-    "class": "dual-use"
-  },
-  "author": {
-    "name": "Kinthala Samuel Sampath Kumar",
-    "email": "support@splcart.in"
-  }
-}
+{
+  "name": "mecord-connect",
+  "version": "2.0.0",
+  "description": "Secure one-command Mecord Connect runtime for connecting ChatGPT to a user-authorized Windows computer.",
+  "type": "module",
+  "bin": {
+    "mecord-connect": "bin/operator.mjs"
+  },
+  "files": [
+    "bin",
+    "src",
+    "runtime",
+    "README.md",
+    "DISCLOSURE",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=22.14.0 <23 || >=24.0.0 <25 || >=26.0.0 <27"
+  },
+  "os": [
+    "win32"
+  ],
+  "cpu": [
+    "x64"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "license": "SEE LICENSE IN LICENSE",
+  "scripts": {
+    "build:runtime": "node ./scripts/build-runtime-payload.mjs",
+    "prepublishOnly": "node ./src/publish-check.mjs"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/sampathkumar-co/Operator-runtime.git"
+  },
+  "homepage": "https://operator.splcart.in",
+  "keywords": [
+    "mecord-connect",
+    "chatgpt",
+    "mcp",
+    "windows",
+    "automation",
+    "developer-tools"
+  ],
+  "bugs": {
+    "url": "https://github.com/sampathkumar-co/Operator-runtime/issues",
+    "email": "support@splcart.in"
+  },
+  "contentPolicy": {
+    "class": "dual-use"
+  },
+  "author": {
+    "name": "Kinthala Samuel Sampath Kumar",
+    "email": "support@splcart.in"
+  }
+}