keystonectl 0.1.0__tar.gz

keystonectl-0.1.0/.gitignore

@@ -0,0 +1,23 @@
+internal/
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+venv/
+dist/
+build/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+.coverage.*
+htmlcov/
+*.log
+e2e-*.jsonl
+e2e-diagnostics/
+.env
+.env.*
+!.env.example
+.DS_Store
+.idea/
+.vscode/

keystonectl-0.1.0/CHANGELOG.md

@@ -0,0 +1,44 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-10-14
+
+### Added
+
+- Chat skill in `skills/keystonectl/` for installing, upgrading, and removing services.
+- Guide for service authors: `docs/packaging-a-service.md`.
+- CLI skeleton: `init`, `lint`, `check`, `plan`/`apply`, lock file, catalog sources, JSON output.
+- Resource binding for `s3/v1` and `postgres/v1` with probes.
+- Published on PyPI as `keystonectl`; tags `vX.Y.Z` publish through trusted publishing.
+- Public paths: loopback port, nginx vhost, certificate lifecycle, and `service remove`, `upgrade`, `rollback`, `eject`, and `adopt`.
+- Release gate verifies that the default catalog ref exists.
+- `SECURITY.md`.
+- Unexpected errors are reported as `internal_error` in JSON.
+
+### Changed
+
+- catalog spec explains tag versus commit pinning.
+- ADR 0005 and generation.md describe `check` as reporting, `apply` and `upgrade` as stopping.
+- Error hints no longer mention a `--local` flag; `package_ambiguous` names the `source/name` form with an example.
+- README links are absolute for PyPI.
+- ADR 0001 lists the core internals keystonectl depends on.
+- `docs/packaging-a-service.md`: the file-mcp example no longer calls the published image digest a placeholder; it now points authors at copying their own registry's digest.
+- Corrected five docs that had drifted from the code: resource binding question reuse (`docs/resources.md`), Postgres provider promises (`docs/spec/resources/postgres-v1.md`), the keystone-deploy `mcp/` layout example (`docs/spec/deployment-layout.md`), the public DNS check (`docs/public-paths.md`), and `keystone-resources` cross-package reachability (`docs/spec/service-package.md`, `docs/packaging-a-service.md`).
+- ADR 0004 no longer mentions a `--local` flag.
+- `tag_not_found` names the source, the ref, and the URL.
+- e2e: vm profile requires --keystonectl until 0.1.0 is on PyPI; certbot re-issue checked by serial.
+- Skill handles `recommended_policy` from `bundle install`.
+- Taking over an nginx site asks every time and restores every disabled site on remove.
+- e2e pins keystone-deploy at the release/catalog commit that drops the managed-mode text from `.env.example`.
+
+### Fixed
+
+- test: consumer secret comparison after a failed probe
+- State-changing commands hold the lock for their whole run; a second process gets `busy`.
+- Catalog and package fetches no longer fail with EXDEV when /tmp is a different file system.
+- Fetching into a deployment root that has never run `init` now creates `.keystonectl/` itself with mode 700 and the promised `.gitignore`, instead of leaving it with a default, wider mode.

keystonectl-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 Alexey Klochkov
+
+   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.

keystonectl-0.1.0/PKG-INFO

@@ -0,0 +1,167 @@
+Metadata-Version: 2.5
+Name: keystonectl
+Version: 0.1.0
+Summary: Install and check services behind a Keystone MCP gateway: package lint, deployment check, plan/apply
+Project-URL: Homepage, https://github.com/keystone-codes/keystonectl
+Project-URL: Repository, https://github.com/keystone-codes/keystonectl
+Project-URL: Issues, https://github.com/keystone-codes/keystonectl/issues
+Project-URL: Changelog, https://github.com/keystone-codes/keystonectl/blob/main/CHANGELOG.md
+Project-URL: Documentation, https://github.com/keystone-codes/keystonectl/tree/main/docs
+Author: Keystone Codes
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: docker-compose,gateway,installer,keystone,mcp
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: System Administrators
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: System :: Installation/Setup
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: boto3>=1.34
+Requires-Dist: httpx>=0.27
+Requires-Dist: jsonschema>=4.18
+Requires-Dist: packaging>=24
+Requires-Dist: psycopg[binary]>=3.2
+Requires-Dist: pyyaml>=6
+Description-Content-Type: text/markdown
+
+# keystonectl
+
+keystonectl installs MCP services behind a Keystone MCP gateway from a catalog, checks service
+packages and deployments, and gives agents a plan/apply interface.
+
+- **Service manifest** — authors and operators share one package description (`keystone-service.yaml`).
+- **Check before run** — `lint` and `check` validate packages and layout without starting containers.
+- **Generate and lifecycle** — `init`, `service plan`/`apply`, lock file, and compose fragments for the gateway.
+
+keystonectl does **not** install keystone-mcp itself and does **not** edit RBAC policy files.
+
+## What keystonectl writes
+
+`service apply` writes the package compose fragment, env files, `docker-compose.packages.yml` (the second `-f`), the upstream registry, the catalog snapshot, and the gateway names in `.env`. It does not edit `packages/<name>.override.yml` or the operator's `docker-compose.yml`. See [docs/generation.md](https://github.com/keystone-codes/keystonectl/blob/main/docs/generation.md).
+
+## Install
+
+Preferred:
+
+```bash
+uv tool install keystonectl
+```
+
+Alternatives:
+
+```bash
+pipx install keystonectl
+uvx keystonectl --version
+```
+
+## Quick start
+
+```bash
+keystonectl init --adopt <deployment-dir>
+keystonectl --root <deployment-dir> catalog list
+keystonectl --root <deployment-dir> bundle install minimal
+keystonectl --root <deployment-dir> service status
+```
+
+Without `sources.yaml` the default catalog `keystone-codes` is used at tag `v1.0.0`.
+
+Every command, its questions, and its error ids are in [docs/commands.md](https://github.com/keystone-codes/keystonectl/blob/main/docs/commands.md).
+
+A service you run yourself is not a package. `keystonectl service add-remote` records its URL, namespace, and filters, and writes a mode 600 handoff file for the team that runs it. keystonectl does not generate compose for that service.
+
+## Run from a checkout
+
+```bash
+uv run keystonectl --version
+uv run keystonectl init <directory>
+uv run keystonectl init --adopt <directory>
+uv run keystonectl lint <manifest-or-directory>
+uv run keystonectl --root <directory> check
+uv run keystonectl --root <directory> catalog list
+uv run keystonectl --root <directory> service plan <package>
+uv run keystonectl --root <directory> service apply <package>
+```
+
+`service install` is another name for `service apply`. `package lint` is another name for `lint`.
+
+## Install through chat
+
+Agents install services by following [`skills/keystonectl/`](https://github.com/keystone-codes/keystonectl/blob/main/skills/keystonectl/SKILL.md). Copy that directory into the agent's skills directory on the host where keystone-mcp runs. The skill ships in the repository, not in the wheel: copy `skills/keystonectl/` from a checkout or a release archive.
+
+The agent runs `keystonectl` with `--json`, asks one question at a time, and takes a secret only as a path to a mode 600 file. It does not run Docker, edit compose files, or edit the RBAC policy. Recommended roles are handed to the `keystone-policy-admin` skill from keystone-mcp 0.5.0, which applies them after an administrator confirms, also for bundles. Without that skill, the agent shows the same `{role, allow}` list and the policy path for the administrator to apply.
+
+## JSON
+
+Pass `--json` for one JSON document on stdout. The document matches `src/keystonectl/schemas/output.schema.json`.
+`--json` does not prompt. Secrets read during the run are replaced with `***`.
+
+Exit codes are the same for text and JSON:
+
+| Code | Meaning |
+|---|---|
+| 0 | Done. Warnings are allowed. |
+| 1 | The command was used incorrectly. |
+| 2 | An answer is missing. Nothing was changed. |
+| 3 | A rule failed, or something outside keystonectl failed. `retryable` is true only for this code. |
+
+## Answers
+
+Non-secret answers can be given with `--set KEY=VALUE` or the environment.
+The name of a per-service answer is `KEYSTONE_SETUP_SERVICE_<PKG>_<SUFFIX>`,
+with the package name in upper case and `-` turned into `_`.
+A secret is only a path to a mode 600 file. The variable name ends in `_FILE`.
+`--set` refuses secret variables.
+
+Lookup order: `--set`, the environment, the answer stored in the lock, then the manifest default.
+
+## Files
+
+| Path | Role |
+|---|---|
+| `services.lock.yaml` | What is installed. Not committed. |
+| `sources.yaml` | Catalog sources. Absent means the default keystone-codes catalog. |
+| `keystonectl/upstreams.yaml` | Upstream registry read by keystone-mcp. |
+| `keystonectl/catalog-snapshot.yaml` | Catalog snapshot read by keystone-mcp. |
+| `.keystonectl/` | Cache of catalogs and packages. |
+
+Start the stack with both compose files, for example:
+
+```bash
+docker compose -f docker-compose.yml -f docker-compose.packages.yml up -d
+```
+
+`init --adopt` prints that command. Without the second file, keystone-mcp does not see the registry, the snapshot, or the service network.
+
+## Documentation
+
+- Packaging your own service: [docs/packaging-a-service.md](https://github.com/keystone-codes/keystonectl/blob/main/docs/packaging-a-service.md)
+- [Service package spec](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/service-package.md)
+- [Catalog spec](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/catalog.md)
+- [S3 resource interface](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/resources/s3-v1.md)
+- [Postgres resource interface](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/resources/postgres-v1.md)
+- [Deployment layout](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/deployment-layout.md)
+- [Architecture decisions](https://github.com/keystone-codes/keystonectl/blob/main/docs/adr/README.md)
+- [CLI reference](https://github.com/keystone-codes/keystonectl/blob/main/docs/cli.md)
+- [Environment variables](https://github.com/keystone-codes/keystonectl/blob/main/docs/resources.md)
+
+Why things are the way they are: [ADR 0006](https://github.com/keystone-codes/keystonectl/blob/main/docs/adr/0006-keystonectl-is-a-separate-product.md).
+
+## Verification
+
+`scripts/e2e.sh` runs the release checks against a real keystone-mcp: the open example and the keystone-deploy MCP layout. Flags, scenarios, and how to read the JSONL report are in [scripts/e2e/README.md](https://github.com/keystone-codes/keystonectl/blob/main/scripts/e2e/README.md). The manual VM and stand protocol, with an empty result column until someone runs it, is [docs/release-checklist.md](https://github.com/keystone-codes/keystonectl/blob/main/docs/release-checklist.md).
+
+## Compatibility
+
+The `keystonectl` version is independent of keystone-mcp. Service packages declare supported
+keystone-mcp versions in `compat.keystone_mcp`; `keystonectl check` validates them against your
+deployment.
+
+## License
+
+Apache-2.0 — see [LICENSE](https://github.com/keystone-codes/keystonectl/blob/main/LICENSE).

keystonectl-0.1.0/README.md

@@ -0,0 +1,135 @@
+# keystonectl
+
+keystonectl installs MCP services behind a Keystone MCP gateway from a catalog, checks service
+packages and deployments, and gives agents a plan/apply interface.
+
+- **Service manifest** — authors and operators share one package description (`keystone-service.yaml`).
+- **Check before run** — `lint` and `check` validate packages and layout without starting containers.
+- **Generate and lifecycle** — `init`, `service plan`/`apply`, lock file, and compose fragments for the gateway.
+
+keystonectl does **not** install keystone-mcp itself and does **not** edit RBAC policy files.
+
+## What keystonectl writes
+
+`service apply` writes the package compose fragment, env files, `docker-compose.packages.yml` (the second `-f`), the upstream registry, the catalog snapshot, and the gateway names in `.env`. It does not edit `packages/<name>.override.yml` or the operator's `docker-compose.yml`. See [docs/generation.md](https://github.com/keystone-codes/keystonectl/blob/main/docs/generation.md).
+
+## Install
+
+Preferred:
+
+```bash
+uv tool install keystonectl
+```
+
+Alternatives:
+
+```bash
+pipx install keystonectl
+uvx keystonectl --version
+```
+
+## Quick start
+
+```bash
+keystonectl init --adopt <deployment-dir>
+keystonectl --root <deployment-dir> catalog list
+keystonectl --root <deployment-dir> bundle install minimal
+keystonectl --root <deployment-dir> service status
+```
+
+Without `sources.yaml` the default catalog `keystone-codes` is used at tag `v1.0.0`.
+
+Every command, its questions, and its error ids are in [docs/commands.md](https://github.com/keystone-codes/keystonectl/blob/main/docs/commands.md).
+
+A service you run yourself is not a package. `keystonectl service add-remote` records its URL, namespace, and filters, and writes a mode 600 handoff file for the team that runs it. keystonectl does not generate compose for that service.
+
+## Run from a checkout
+
+```bash
+uv run keystonectl --version
+uv run keystonectl init <directory>
+uv run keystonectl init --adopt <directory>
+uv run keystonectl lint <manifest-or-directory>
+uv run keystonectl --root <directory> check
+uv run keystonectl --root <directory> catalog list
+uv run keystonectl --root <directory> service plan <package>
+uv run keystonectl --root <directory> service apply <package>
+```
+
+`service install` is another name for `service apply`. `package lint` is another name for `lint`.
+
+## Install through chat
+
+Agents install services by following [`skills/keystonectl/`](https://github.com/keystone-codes/keystonectl/blob/main/skills/keystonectl/SKILL.md). Copy that directory into the agent's skills directory on the host where keystone-mcp runs. The skill ships in the repository, not in the wheel: copy `skills/keystonectl/` from a checkout or a release archive.
+
+The agent runs `keystonectl` with `--json`, asks one question at a time, and takes a secret only as a path to a mode 600 file. It does not run Docker, edit compose files, or edit the RBAC policy. Recommended roles are handed to the `keystone-policy-admin` skill from keystone-mcp 0.5.0, which applies them after an administrator confirms, also for bundles. Without that skill, the agent shows the same `{role, allow}` list and the policy path for the administrator to apply.
+
+## JSON
+
+Pass `--json` for one JSON document on stdout. The document matches `src/keystonectl/schemas/output.schema.json`.
+`--json` does not prompt. Secrets read during the run are replaced with `***`.
+
+Exit codes are the same for text and JSON:
+
+| Code | Meaning |
+|---|---|
+| 0 | Done. Warnings are allowed. |
+| 1 | The command was used incorrectly. |
+| 2 | An answer is missing. Nothing was changed. |
+| 3 | A rule failed, or something outside keystonectl failed. `retryable` is true only for this code. |
+
+## Answers
+
+Non-secret answers can be given with `--set KEY=VALUE` or the environment.
+The name of a per-service answer is `KEYSTONE_SETUP_SERVICE_<PKG>_<SUFFIX>`,
+with the package name in upper case and `-` turned into `_`.
+A secret is only a path to a mode 600 file. The variable name ends in `_FILE`.
+`--set` refuses secret variables.
+
+Lookup order: `--set`, the environment, the answer stored in the lock, then the manifest default.
+
+## Files
+
+| Path | Role |
+|---|---|
+| `services.lock.yaml` | What is installed. Not committed. |
+| `sources.yaml` | Catalog sources. Absent means the default keystone-codes catalog. |
+| `keystonectl/upstreams.yaml` | Upstream registry read by keystone-mcp. |
+| `keystonectl/catalog-snapshot.yaml` | Catalog snapshot read by keystone-mcp. |
+| `.keystonectl/` | Cache of catalogs and packages. |
+
+Start the stack with both compose files, for example:
+
+```bash
+docker compose -f docker-compose.yml -f docker-compose.packages.yml up -d
+```
+
+`init --adopt` prints that command. Without the second file, keystone-mcp does not see the registry, the snapshot, or the service network.
+
+## Documentation
+
+- Packaging your own service: [docs/packaging-a-service.md](https://github.com/keystone-codes/keystonectl/blob/main/docs/packaging-a-service.md)
+- [Service package spec](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/service-package.md)
+- [Catalog spec](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/catalog.md)
+- [S3 resource interface](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/resources/s3-v1.md)
+- [Postgres resource interface](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/resources/postgres-v1.md)
+- [Deployment layout](https://github.com/keystone-codes/keystonectl/blob/main/docs/spec/deployment-layout.md)
+- [Architecture decisions](https://github.com/keystone-codes/keystonectl/blob/main/docs/adr/README.md)
+- [CLI reference](https://github.com/keystone-codes/keystonectl/blob/main/docs/cli.md)
+- [Environment variables](https://github.com/keystone-codes/keystonectl/blob/main/docs/resources.md)
+
+Why things are the way they are: [ADR 0006](https://github.com/keystone-codes/keystonectl/blob/main/docs/adr/0006-keystonectl-is-a-separate-product.md).
+
+## Verification
+
+`scripts/e2e.sh` runs the release checks against a real keystone-mcp: the open example and the keystone-deploy MCP layout. Flags, scenarios, and how to read the JSONL report are in [scripts/e2e/README.md](https://github.com/keystone-codes/keystonectl/blob/main/scripts/e2e/README.md). The manual VM and stand protocol, with an empty result column until someone runs it, is [docs/release-checklist.md](https://github.com/keystone-codes/keystonectl/blob/main/docs/release-checklist.md).
+
+## Compatibility
+
+The `keystonectl` version is independent of keystone-mcp. Service packages declare supported
+keystone-mcp versions in `compat.keystone_mcp`; `keystonectl check` validates them against your
+deployment.
+
+## License
+
+Apache-2.0 — see [LICENSE](https://github.com/keystone-codes/keystonectl/blob/main/LICENSE).

keystonectl-0.1.0/pyproject.toml

@@ -0,0 +1,77 @@
+[project]
+name = "keystonectl"
+version = "0.1.0"
+description = "Install and check services behind a Keystone MCP gateway: package lint, deployment check, plan/apply"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+authors = [{ name = "Keystone Codes" }]
+keywords = ["mcp", "keystone", "installer", "docker-compose", "gateway"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: System Administrators",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: System :: Installation/Setup",
+    "Typing :: Typed",
+]
+dependencies = [
+    "pyyaml>=6",
+    "jsonschema>=4.18",
+    "boto3>=1.34",
+    "httpx>=0.27",
+    "psycopg[binary]>=3.2",
+    "packaging>=24",
+]
+
+[project.scripts]
+keystonectl = "keystonectl.cli:main"
+
+[project.urls]
+Homepage = "https://github.com/keystone-codes/keystonectl"
+Repository = "https://github.com/keystone-codes/keystonectl"
+Issues = "https://github.com/keystone-codes/keystonectl/issues"
+Changelog = "https://github.com/keystone-codes/keystonectl/blob/main/CHANGELOG.md"
+Documentation = "https://github.com/keystone-codes/keystonectl/tree/main/docs"
+
+[dependency-groups]
+dev = [
+    "pytest>=8",
+    "ruff",
+    "pyyaml>=6",
+]
+
+
+[build-system]
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/keystonectl"]
+
+[tool.hatch.build.targets.wheel.force-include]
+"src/keystonectl/nginx/service.conf.template" = "keystonectl/nginx/service.conf.template"
+"src/keystonectl/nginx/service-https.conf.template" = "keystonectl/nginx/service-https.conf.template"
+
+[tool.hatch.build.targets.sdist]
+only-include = ["src/keystonectl", "README.md", "LICENSE", "CHANGELOG.md", "pyproject.toml"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py311"
+
+[tool.ruff.lint.per-file-ignores]
+"src/keystonectl/resources/*_probe.py" = ["BLE001", "S110"]
+"tests/support/fake_pg.py" = ["PYI034", "PYI036"]
+
+[tool.pytest.ini_options]
+pythonpath = ["."]
+testpaths = ["tests"]
+markers = [
+    "integration: needs Docker",
+]

keystonectl-0.1.0/src/keystonectl/__init__.py

@@ -0,0 +1,3 @@
+"""Install and check services behind a Keystone MCP gateway."""
+
+__version__ = "0.1.0"

keystonectl-0.1.0/src/keystonectl/__main__.py

@@ -0,0 +1,8 @@
+"""python -m keystonectl"""
+
+import sys
+
+from keystonectl.cli import main
+
+if __name__ == "__main__":
+    sys.exit(main())