sigrix-launcher 0.1.0__tar.gz

sigrix_launcher-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/

sigrix_launcher-0.1.0/CHANGELOG.md

@@ -0,0 +1,22 @@
+# Changelog
+
+All notable changes to this project are recorded here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the versioning is
+described in `VERSIONING.md`.
+
+## [Unreleased]
+
+## [0.1.0] — 2026-09-23
+
+First release, reading package format `1`.
+
+### Added
+
+- `sigrix-launcher run <seller>/<listing-id>`: check the purchase, fetch and
+  verify the package, install it into an environment of its own and start the
+  seller's server on stdio. Arguments after the identifier go to the server.
+- A cache per listing: each version started, and the last purchase answer
+  (with a fingerprint of the token), so a start offline inside the grace period
+  uses the version installed last.
+- The Postern reference runner's client code, copied in, for the purchase check
+  and the verified download.

sigrix_launcher-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Sigrix
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

sigrix_launcher-0.1.0/NOTICE

@@ -0,0 +1,15 @@
+sigrix-launcher
+Copyright 2026 Sigrix
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+src/sigrix_launcher/_postern/ is a copy of the Postern reference runner's
+client code (the entitlement check, the verified download and the transport
+they share), under the same licence. It is changed upstream and copied here,
+never edited in place.
+
+Trademarks. "Sigrix" and the Sigrix logo are trademarks of Sigrix. The Apache
+License does not grant permission to use them. The name of this repository and
+package identifies the marketplace the launcher fetches from; it does not imply
+endorsement of a derivative work. A fork or a derived launcher must not present
+itself as Sigrix or as published by Sigrix.

sigrix_launcher-0.1.0/PKG-INFO

@@ -0,0 +1,114 @@
+Metadata-Version: 2.5
+Name: sigrix-launcher
+Version: 0.1.0
+Summary: Start a Sigrix-delivered MCP server you bought from the MCP client you already use: checks the purchase, fetches and verifies the package, installs it and hands over stdio.
+Project-URL: Homepage, https://github.com/sigrix-io/sigrix-launcher
+Project-URL: Issues, https://github.com/sigrix-io/sigrix-launcher/issues
+Project-URL: Changelog, https://github.com/sigrix-io/sigrix-launcher/blob/main/CHANGELOG.md
+Author: Sigrix
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: claude-code,mcp,model-context-protocol,postern,sigrix
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# sigrix-launcher
+
+Start an MCP server you bought on [Sigrix](https://sigrix.io) from the client you already use — Claude Code, Claude Desktop, Cursor, or any MCP client that starts a server over stdio.
+
+Some Sigrix listings are delivered by Sigrix rather than installed from a public registry: the seller's server is a package only its buyers can download. This launcher is what your client starts for one. On every start it:
+
+1. asks Sigrix whether your token owns the listing;
+2. downloads the seller's package and verifies it before anything is written;
+3. installs it into an environment of its own, once per version;
+4. starts the seller's server on its own stdio, so your client talks to the server directly.
+
+It speaks [Postern](https://github.com/sigrix-io/postern), the open protocol for checking a purchase and fetching what was bought, using the protocol's reference client code.
+
+## Configure your client
+
+The listing's page shows this with its identifier filled in, once you own it — copy it from there. `<seller>/<listing-id>` below is that identifier, and `YOUR_SIGRIX_TOKEN` is where your token goes.
+
+**Claude Code**
+
+```sh
+claude mcp add modelwatch -e SIGRIX_TOKEN=YOUR_SIGRIX_TOKEN -- uvx sigrix-launcher run <seller>/<listing-id>
+```
+
+**Claude Desktop** (`claude_desktop_config.json`) and **Cursor** (`.cursor/mcp.json`)
+
+```json
+{
+  "mcpServers": {
+    "modelwatch": {
+      "command": "uvx",
+      "args": [
+        "sigrix-launcher",
+        "run",
+        "<seller>/<listing-id>"
+      ],
+      "env": {
+        "SIGRIX_TOKEN": "YOUR_SIGRIX_TOKEN"
+      }
+    }
+  }
+}
+```
+
+`uvx` comes with [uv](https://pypi.org/project/uv/). `pipx run sigrix-launcher run <seller>/<listing-id>` works as well. Python 3.11 or newer.
+
+Arguments after the identifier are passed to the seller's server: `... run <seller>/<listing-id> -- --verbose`. Any other variable in the `env` block (an API key the listing asks for, say) reaches the server as it is.
+
+## Your token
+
+`SIGRIX_TOKEN` is a runner token for this listing: create one under **Runner tokens** on your Sigrix account's plugins page, <https://sigrix.io/account/plugins>, one for each machine. It covers this one listing, and revoking it there stops this configuration and nothing else. The plugin feed token on the same page works too and covers everything you bought, but regenerating it replaces it everywhere at once.
+
+The launcher sends it only in the `Authorization` header of its two requests to Sigrix, never writes it to disk, and starts the seller's server without it — nor any other `SIGRIX_` or `POSTERN_` variable.
+
+## When it does not start
+
+It prints one sentence on stderr saying why and exits; your client shows it in the server's log.
+
+- **Not owned.** The token has not bought this listing, the purchase was refunded, or the token has since been regenerated. Sigrix answers all three the same way on purpose, so the message names all three. Nothing is downloaded.
+- **Offline.** If Sigrix confirmed your purchase within its grace period (a day, for Sigrix) and a version is already installed here, that version starts. Otherwise the launcher asks you to reconnect.
+- **Nothing to install yet.** The seller's newest version may still be waiting for Sigrix's review, or a version may have been withdrawn. A withdrawn version is not started from the cache either.
+- **Withdrawn listing.** Buyers of a listing its seller withdrew keep access for a year; after that, the message gives the date it ended.
+
+A refund takes effect at the next start: the purchase is checked when the server starts, not while it runs.
+
+## What it keeps on your machine
+
+Everything is under one folder: `~/.cache/sigrix-launcher` on Linux, `~/Library/Caches/sigrix-launcher` on macOS, `%LOCALAPPDATA%\sigrix-launcher` on Windows. `SIGRIX_LAUNCHER_HOME` moves it. For each listing: every version you have started, each in its own environment, and Sigrix's last answer about your purchase, stored with a fingerprint of the token rather than the token. Delete the folder whenever you like; the next start downloads again.
+
+## Variables
+
+| Variable | |
+| --- | --- |
+| `SIGRIX_TOKEN` | Required. A runner token for this listing, from the plugins page. |
+| `SIGRIX_LAUNCHER_HOME` | Optional. Where installed versions are kept. |
+| `POSTERN_DISTRIBUTOR` | Optional; defaults to `https://sigrix.io`. For testing against another distributor. Plain `http://` is accepted only to a loopback address. |
+
+## Development
+
+```sh
+pip install -e ".[dev]"
+ruff check . && ruff format --check . && pytest
+```
+
+The tests run a distributor on loopback and, for one of them, install a real wheel and talk to the started server over a real pipe. `src/sigrix_launcher/_postern/` is a copy of the Postern reference runner's client code; change it upstream, never here.
+
+## Licence
+
+Apache-2.0. The Sigrix name and logo are not covered by the licence — see `NOTICE`.

sigrix_launcher-0.1.0/README.md

@@ -0,0 +1,88 @@
+# sigrix-launcher
+
+Start an MCP server you bought on [Sigrix](https://sigrix.io) from the client you already use — Claude Code, Claude Desktop, Cursor, or any MCP client that starts a server over stdio.
+
+Some Sigrix listings are delivered by Sigrix rather than installed from a public registry: the seller's server is a package only its buyers can download. This launcher is what your client starts for one. On every start it:
+
+1. asks Sigrix whether your token owns the listing;
+2. downloads the seller's package and verifies it before anything is written;
+3. installs it into an environment of its own, once per version;
+4. starts the seller's server on its own stdio, so your client talks to the server directly.
+
+It speaks [Postern](https://github.com/sigrix-io/postern), the open protocol for checking a purchase and fetching what was bought, using the protocol's reference client code.
+
+## Configure your client
+
+The listing's page shows this with its identifier filled in, once you own it — copy it from there. `<seller>/<listing-id>` below is that identifier, and `YOUR_SIGRIX_TOKEN` is where your token goes.
+
+**Claude Code**
+
+```sh
+claude mcp add modelwatch -e SIGRIX_TOKEN=YOUR_SIGRIX_TOKEN -- uvx sigrix-launcher run <seller>/<listing-id>
+```
+
+**Claude Desktop** (`claude_desktop_config.json`) and **Cursor** (`.cursor/mcp.json`)
+
+```json
+{
+  "mcpServers": {
+    "modelwatch": {
+      "command": "uvx",
+      "args": [
+        "sigrix-launcher",
+        "run",
+        "<seller>/<listing-id>"
+      ],
+      "env": {
+        "SIGRIX_TOKEN": "YOUR_SIGRIX_TOKEN"
+      }
+    }
+  }
+}
+```
+
+`uvx` comes with [uv](https://pypi.org/project/uv/). `pipx run sigrix-launcher run <seller>/<listing-id>` works as well. Python 3.11 or newer.
+
+Arguments after the identifier are passed to the seller's server: `... run <seller>/<listing-id> -- --verbose`. Any other variable in the `env` block (an API key the listing asks for, say) reaches the server as it is.
+
+## Your token
+
+`SIGRIX_TOKEN` is a runner token for this listing: create one under **Runner tokens** on your Sigrix account's plugins page, <https://sigrix.io/account/plugins>, one for each machine. It covers this one listing, and revoking it there stops this configuration and nothing else. The plugin feed token on the same page works too and covers everything you bought, but regenerating it replaces it everywhere at once.
+
+The launcher sends it only in the `Authorization` header of its two requests to Sigrix, never writes it to disk, and starts the seller's server without it — nor any other `SIGRIX_` or `POSTERN_` variable.
+
+## When it does not start
+
+It prints one sentence on stderr saying why and exits; your client shows it in the server's log.
+
+- **Not owned.** The token has not bought this listing, the purchase was refunded, or the token has since been regenerated. Sigrix answers all three the same way on purpose, so the message names all three. Nothing is downloaded.
+- **Offline.** If Sigrix confirmed your purchase within its grace period (a day, for Sigrix) and a version is already installed here, that version starts. Otherwise the launcher asks you to reconnect.
+- **Nothing to install yet.** The seller's newest version may still be waiting for Sigrix's review, or a version may have been withdrawn. A withdrawn version is not started from the cache either.
+- **Withdrawn listing.** Buyers of a listing its seller withdrew keep access for a year; after that, the message gives the date it ended.
+
+A refund takes effect at the next start: the purchase is checked when the server starts, not while it runs.
+
+## What it keeps on your machine
+
+Everything is under one folder: `~/.cache/sigrix-launcher` on Linux, `~/Library/Caches/sigrix-launcher` on macOS, `%LOCALAPPDATA%\sigrix-launcher` on Windows. `SIGRIX_LAUNCHER_HOME` moves it. For each listing: every version you have started, each in its own environment, and Sigrix's last answer about your purchase, stored with a fingerprint of the token rather than the token. Delete the folder whenever you like; the next start downloads again.
+
+## Variables
+
+| Variable | |
+| --- | --- |
+| `SIGRIX_TOKEN` | Required. A runner token for this listing, from the plugins page. |
+| `SIGRIX_LAUNCHER_HOME` | Optional. Where installed versions are kept. |
+| `POSTERN_DISTRIBUTOR` | Optional; defaults to `https://sigrix.io`. For testing against another distributor. Plain `http://` is accepted only to a loopback address. |
+
+## Development
+
+```sh
+pip install -e ".[dev]"
+ruff check . && ruff format --check . && pytest
+```
+
+The tests run a distributor on loopback and, for one of them, install a real wheel and talk to the started server over a real pipe. `src/sigrix_launcher/_postern/` is a copy of the Postern reference runner's client code; change it upstream, never here.
+
+## Licence
+
+Apache-2.0. The Sigrix name and logo are not covered by the licence — see `NOTICE`.

sigrix_launcher-0.1.0/pyproject.toml

@@ -0,0 +1,67 @@
+[build-system]
+requires = ["hatchling>=1.25"]
+build-backend = "hatchling.build"
+
+[project]
+name = "sigrix-launcher"
+version = "0.1.0"
+description = "Start a Sigrix-delivered MCP server you bought from the MCP client you already use: checks the purchase, fetches and verifies the package, installs it and hands over stdio."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+requires-python = ">=3.11"
+authors = [{ name = "Sigrix" }]
+keywords = ["mcp", "model-context-protocol", "sigrix", "postern", "claude-code"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: End Users/Desktop",
+    "License :: OSI Approved :: Apache Software License",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+]
+# Standard library only, like the runner code it carries: the launcher is
+# started by `uvx` on every client start, and nothing here needs more.
+dependencies = []
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8",
+    "ruff>=0.6",
+]
+
+[project.scripts]
+sigrix-launcher = "sigrix_launcher.cli:main"
+
+[project.urls]
+Homepage = "https://github.com/sigrix-io/sigrix-launcher"
+Issues = "https://github.com/sigrix-io/sigrix-launcher/issues"
+Changelog = "https://github.com/sigrix-io/sigrix-launcher/blob/main/CHANGELOG.md"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/sigrix_launcher"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src/sigrix_launcher", "tests", "README.md", "LICENSE", "NOTICE", "CHANGELOG.md"]
+
+[tool.ruff]
+line-length = 120
+target-version = "py311"
+# Vendored from the Postern reference runner and linted there; a change to it
+# belongs upstream, never here (see the header of each file).
+extend-exclude = ["src/sigrix_launcher/_postern"]
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "B", "UP", "S"]
+ignore = ["E501"]
+
+[tool.ruff.lint.per-file-ignores]
+# S105 and S108 are the fixtures' fake token and fake cache path, which
+# name nothing real.
+"tests/*" = ["S101", "S105", "S108", "S603", "S607"]
+"src/sigrix_launcher/installer.py" = ["S603"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

sigrix_launcher-0.1.0/src/sigrix_launcher/__init__.py

@@ -0,0 +1,43 @@
+"""Start a Sigrix-delivered MCP server you bought, from the MCP client you already use.
+
+What happens on every start, in order:
+
+1. **The purchase is checked.** ``SIGRIX_TOKEN`` is presented to the
+   distributor's entitlement check, through the Postern runner's own client
+   (``_postern/entitlement.py``): its declared staleness window, its grace
+   when the distributor cannot be reached, and a ``404`` as a final answer.
+2. **The package is fetched and verified.** The seller's wheel and its
+   manifest arrive as one zip, held in memory until its ``Repr-Digest``
+   agrees, then checked again against the checksum in the manifest. Nothing
+   is written before both agree, and a version already installed is reused.
+3. **It is installed into an environment of its own** — one per version,
+   under the launcher's cache — with ``uv`` when it is on the path and
+   ``venv`` and ``pip`` otherwise.
+4. **The seller's server is started on this process's stdio**, with the
+   launcher's own variables removed from its environment.
+
+The launcher writes nothing to stdout: that stream is the MCP connection. It
+never writes the token anywhere; its cache holds a fingerprint of it, so a
+rotated token is a new question rather than an old answer.
+"""
+
+__version__ = "0.1.0"
+
+#: The file beside the wheel in a served package, and the only two values of it
+#: this launcher can read. A newer format is refused by name rather than guessed
+#: at — upgrading the launcher is the fix, and the message says so.
+MANIFEST_FILENAME = "sigrix-package.json"
+MANIFEST_KIND = "sigrix-mcp-package"
+SUPPORTED_MANIFEST_FORMAT = 1
+
+#: How the launcher names itself on the entitlement check, so the distributor
+#: can tell a package launched on a buyer's machine from a runner bundle.
+DELIVERY_MODE = "connector-local"
+
+__all__ = [
+    "DELIVERY_MODE",
+    "MANIFEST_FILENAME",
+    "MANIFEST_KIND",
+    "SUPPORTED_MANIFEST_FORMAT",
+    "__version__",
+]

sigrix_launcher-0.1.0/src/sigrix_launcher/__main__.py

@@ -0,0 +1,6 @@
+"""``python -m sigrix_launcher`` — the same command as the ``sigrix-launcher`` script."""
+
+from sigrix_launcher.cli import main
+
+if __name__ == "__main__":
+    raise SystemExit(main())

sigrix_launcher-0.1.0/src/sigrix_launcher/_postern/__init__.py

@@ -0,0 +1,63 @@
+# Vendored from the Postern reference runner's `sigrix_runtime.postern` package.
+# Do not edit this copy: a change belongs upstream, and is re-vendored from there.
+"""Postern v0 for a Sigrix listing bundle — the reference implementation.
+
+Postern (``sigrix-io/postern``) is the open execution and entitlement
+protocol for packaged AI agents: four verbs over local HTTP —
+``describe`` / ``run`` / ``stream`` / ``status`` — and one entitlement flow.
+This package serves them for the bundle it is started inside::
+
+    python -m sigrix_runtime.postern
+
+It is also what the ``sigrix/runner`` image runs as its entrypoint. Those
+are two deployment shapes of one codebase rather than two implementations;
+if they ever diverge, that is the bug.
+
+**Nothing here is a second execution path.** ``run`` and ``stream`` reach
+the agent through ``sigrix_runtime.execution``, which is the same function
+``python main.py "…"`` calls. A crew's kickoff inputs are a contract
+spanning several files, and a server that built its own ``crew.kickoff``
+would be one more place for it to drift.
+
+**Zero dependencies beyond the standard library.** The bundle's
+``requirements.txt`` is something a buyer installs on their own machine,
+and four routes on loopback do not justify adding a web framework and its
+tree to it. ``http.server`` serves them; ``http.client`` makes the one
+outbound call this protocol defines.
+
+Layout:
+
+``errors``       the specification's error envelope, as exceptions
+``describe``     the agent's contract: shipped by the distributor, or derived
+``transport``    the one outbound connection, and SPEC 7's rule on it
+``entitlement``  the distributor client and the state machine of SPEC 5.7
+``pull``         bundle retrieval (SPEC 5.6), which is the image's boot step
+``execution``    the run engine — a subprocess per run, so a timeout is real
+``server``       the HTTP surface: routing, CORS, and the SSE framing
+"""
+
+from __future__ import annotations
+
+# The specification version every payload carries. The ``/postern/v0/``
+# path prefix is deliberately coarser than this (SPEC 5.3, VERSIONING.md):
+# the prefix moves only on a breaking revision, and this field is the only
+# sanctioned way to know exactly what you are talking to.
+POSTERN_VERSION = "0.1"
+
+# SPEC 3. This runner implements all four verbs, so it reports Level 3.
+# ``stream`` emits no ``delta`` — see ``server`` for why that is conformant
+# rather than a shortfall.
+CONFORMANCE_LEVEL = 3
+
+PATH_PREFIX = "/postern/v0"
+
+DEFAULT_PORT = 8787
+DEFAULT_HOST = "127.0.0.1"
+
+__all__ = [
+    "CONFORMANCE_LEVEL",
+    "DEFAULT_HOST",
+    "DEFAULT_PORT",
+    "PATH_PREFIX",
+    "POSTERN_VERSION",
+]