glitch-toolkit 0.1.0__tar.gz

glitch_toolkit-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 [yyyy] [name of copyright owner]
+
+   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.

glitch_toolkit-0.1.0/MANIFEST.in

@@ -0,0 +1,17 @@
+# What the sdist carries beyond what setuptools works out for itself.
+#
+# The default heuristics found tests/test_*.py and missed tests/run_all.py,
+# which is the one command the README tells a reader to run. An sdist whose
+# tests cannot be run with the documented command is an sdist that cannot be
+# checked by the person most likely to want to check it: a packager building
+# from source rather than installing a wheel.
+graft tests
+include LICENSE
+include NOTICE
+include README.md
+
+# Never ship build output or caches, whatever is lying around locally.
+global-exclude __pycache__
+global-exclude *.py[cod]
+prune build
+prune dist

glitch_toolkit-0.1.0/NOTICE

@@ -0,0 +1,22 @@
+glitch — bounded autonomy for agents working in a repository
+Copyright 2026 Duwayne Jefferson
+
+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.
+
+---
+
+This package was extracted on 2026-09-08 from the companion toolkit of the book
+"Building Your Store Or Your SaaS With Claude". The practices it checks are
+described there. The book itself is NOT covered by this licence, and neither is
+anything else in the repository this package was extracted from: see the LICENSE
+file at that repository's root, which grants nothing outside this directory.

glitch_toolkit-0.1.0/PKG-INFO

@@ -0,0 +1,152 @@
+Metadata-Version: 2.4
+Name: glitch-toolkit
+Version: 0.1.0
+Summary: Install and verify bounded-autonomy practices in a repository worked on by AI agents
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/AbstractGlitch/glitch-toolkit
+Project-URL: Source, https://github.com/AbstractGlitch/glitch-toolkit
+Project-URL: Issues, https://github.com/AbstractGlitch/glitch-toolkit/issues
+Keywords: claude,agents,guardrails,governance,ci
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Provides-Extra: mcp
+Requires-Dist: mcp>=2.0; extra == "mcp"
+Dynamic: license-file
+
+# glitch
+
+Install the practices from *Building Your Store Or Your SaaS With Claude* into
+your own repository, and check that they still refuse things.
+
+```bash
+glitch install     # put the artifacts in this repository
+glitch status      # what is installed, what is not
+glitch check --all # verify every step
+```
+
+## What it actually checks
+
+A step is not complete because a file is present. Every check does three things
+and reports which of them failed:
+
+1. finds the artifact
+2. runs it, and expects it to work
+3. runs it against a deliberately broken case, and expects it to **refuse**
+
+Without the third, a check passes the moment you copy a file in, whether or not
+that file has any teeth left, and it would be green for every reader forever.
+`tests/test_cli.py` exists to prove the checker fails that case; its `SABOTAGE`
+test installs artifacts that run, exit 0 and refuse nothing.
+
+## What `install` will not do
+
+It will not write your `CLAUDE.md`, `FLEET.md`, `FLOOR.md` or `PLAN.md`. Four of
+the six steps are checked against your own file, because for those four the file
+*is* the work: a rules file that holds, a desk table with one committer, a floor
+measured twice, a plan someone else approved. A command that wrote them would
+turn the path into "you ran an installer". The `FLOOR.md` and `PLAN.md` templates
+ship deliberately unpassable for the same reason.
+
+It will not overwrite. An artifact already in your repo is left alone and
+reported as kept; `--force` is how you say otherwise.
+
+It writes nothing outside the directory you point it at, makes no network calls,
+and has no dependencies outside the standard library.
+
+## Running it without installing it
+
+`cli.py` is one file and stays one file. Copy it into a repository and `status`
+and `check` work with nothing on the path and no install step — that property is
+deliberate and there is a test for the search paths it uses. Only `install`
+needs the rest of the package, and it says so plainly rather than failing oddly.
+
+## The MCP server (read-only)
+
+```bash
+pip install 'glitch-toolkit[mcp]'
+glitch-mcp --repo .
+```
+
+It offers the checks to an agent as three tools — `glitch_status`, `glitch_check`,
+`glitch_ledger_tail` — and appends every question and answer to
+`.claude/toolkit/ledger/ledger.jsonl`.
+
+**It gates nothing.** It cannot pause, block, refuse or intercept any action. It
+has no database connection, no credential and no network call. That is the whole
+first version, on purpose: a server that stands between an agent and a
+production database is serious software, and the honest order is to run
+read-only first, read the ledger, and find out what it *would* have refused
+before giving it the power to refuse. A gate built before that record exists is
+a guess with permissions.
+
+The checks write nothing into your repository. The server breaks that in exactly
+one place — it appends to the ledger — and `--no-ledger` turns off even that, at
+the cost of the only thing worth keeping.
+
+In Claude Code, `.mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "glitch": { "command": "glitch-mcp", "args": ["--repo", "."] }
+  }
+}
+```
+
+### The ledger
+
+Append-only JSONL. Nothing rewrites a line it did not just write; a record that
+is overtaken is superseded by a new one and both stay; a field nobody measured
+is `null` rather than `0`; a half-written last line is skipped and counted, never
+repaired, because repairing it means rewriting the file.
+
+## Tests
+
+```bash
+python tests/run_all.py      # all three suites, 38 tests
+```
+
+The server suite skips cleanly without the `[mcp]` extra and the runner reports
+that as SKIPPED rather than passing, because a green line meaning "we did not
+look" is the exact failure the gate-check practice exists to catch.
+
+## Licence
+
+Apache License 2.0 — see [LICENSE](https://github.com/AbstractGlitch/glitch-toolkit/blob/main/LICENSE)
+and [NOTICE](https://github.com/AbstractGlitch/glitch-toolkit/blob/main/NOTICE). Chosen over MIT for
+the patent grant.
+
+Everything in this repository is under it. Use it commercially, change it,
+redistribute it.
+
+The links above are absolute on purpose: this README is also the package's
+description on PyPI, where a relative link resolves against `pypi.org` and
+returns a 404.
+
+## Where this comes from
+
+This repository is a published mirror. The package is developed inside a private
+monorepo alongside the book *Building Your Store Or Your SaaS With Claude*, whose
+practices it installs and checks, and it is pushed here as a subtree. The book,
+the shop that sells it and the rest of that repository are **not** open source
+and are not here. Nothing is being withheld from this repository that belongs to
+the package.
+
+Issues and pull requests belong here rather than there, because here is the part
+anyone can read.
+
+## Status
+
+Version 0.1.0, the first release. It installs, and the practices it checks are
+the six the book argues for.
+
+What it is not yet: it gates nothing. `glitch-mcp` reports and records and
+cannot block an agent from doing anything. That is deliberate and the reasoning
+is in `mcp_server.py` — a server that stands between an agent and a production
+database should earn its evidence before it earns the power to refuse.

glitch_toolkit-0.1.0/README.md

@@ -0,0 +1,131 @@
+# glitch
+
+Install the practices from *Building Your Store Or Your SaaS With Claude* into
+your own repository, and check that they still refuse things.
+
+```bash
+glitch install     # put the artifacts in this repository
+glitch status      # what is installed, what is not
+glitch check --all # verify every step
+```
+
+## What it actually checks
+
+A step is not complete because a file is present. Every check does three things
+and reports which of them failed:
+
+1. finds the artifact
+2. runs it, and expects it to work
+3. runs it against a deliberately broken case, and expects it to **refuse**
+
+Without the third, a check passes the moment you copy a file in, whether or not
+that file has any teeth left, and it would be green for every reader forever.
+`tests/test_cli.py` exists to prove the checker fails that case; its `SABOTAGE`
+test installs artifacts that run, exit 0 and refuse nothing.
+
+## What `install` will not do
+
+It will not write your `CLAUDE.md`, `FLEET.md`, `FLOOR.md` or `PLAN.md`. Four of
+the six steps are checked against your own file, because for those four the file
+*is* the work: a rules file that holds, a desk table with one committer, a floor
+measured twice, a plan someone else approved. A command that wrote them would
+turn the path into "you ran an installer". The `FLOOR.md` and `PLAN.md` templates
+ship deliberately unpassable for the same reason.
+
+It will not overwrite. An artifact already in your repo is left alone and
+reported as kept; `--force` is how you say otherwise.
+
+It writes nothing outside the directory you point it at, makes no network calls,
+and has no dependencies outside the standard library.
+
+## Running it without installing it
+
+`cli.py` is one file and stays one file. Copy it into a repository and `status`
+and `check` work with nothing on the path and no install step — that property is
+deliberate and there is a test for the search paths it uses. Only `install`
+needs the rest of the package, and it says so plainly rather than failing oddly.
+
+## The MCP server (read-only)
+
+```bash
+pip install 'glitch-toolkit[mcp]'
+glitch-mcp --repo .
+```
+
+It offers the checks to an agent as three tools — `glitch_status`, `glitch_check`,
+`glitch_ledger_tail` — and appends every question and answer to
+`.claude/toolkit/ledger/ledger.jsonl`.
+
+**It gates nothing.** It cannot pause, block, refuse or intercept any action. It
+has no database connection, no credential and no network call. That is the whole
+first version, on purpose: a server that stands between an agent and a
+production database is serious software, and the honest order is to run
+read-only first, read the ledger, and find out what it *would* have refused
+before giving it the power to refuse. A gate built before that record exists is
+a guess with permissions.
+
+The checks write nothing into your repository. The server breaks that in exactly
+one place — it appends to the ledger — and `--no-ledger` turns off even that, at
+the cost of the only thing worth keeping.
+
+In Claude Code, `.mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "glitch": { "command": "glitch-mcp", "args": ["--repo", "."] }
+  }
+}
+```
+
+### The ledger
+
+Append-only JSONL. Nothing rewrites a line it did not just write; a record that
+is overtaken is superseded by a new one and both stay; a field nobody measured
+is `null` rather than `0`; a half-written last line is skipped and counted, never
+repaired, because repairing it means rewriting the file.
+
+## Tests
+
+```bash
+python tests/run_all.py      # all three suites, 38 tests
+```
+
+The server suite skips cleanly without the `[mcp]` extra and the runner reports
+that as SKIPPED rather than passing, because a green line meaning "we did not
+look" is the exact failure the gate-check practice exists to catch.
+
+## Licence
+
+Apache License 2.0 — see [LICENSE](https://github.com/AbstractGlitch/glitch-toolkit/blob/main/LICENSE)
+and [NOTICE](https://github.com/AbstractGlitch/glitch-toolkit/blob/main/NOTICE). Chosen over MIT for
+the patent grant.
+
+Everything in this repository is under it. Use it commercially, change it,
+redistribute it.
+
+The links above are absolute on purpose: this README is also the package's
+description on PyPI, where a relative link resolves against `pypi.org` and
+returns a 404.
+
+## Where this comes from
+
+This repository is a published mirror. The package is developed inside a private
+monorepo alongside the book *Building Your Store Or Your SaaS With Claude*, whose
+practices it installs and checks, and it is pushed here as a subtree. The book,
+the shop that sells it and the rest of that repository are **not** open source
+and are not here. Nothing is being withheld from this repository that belongs to
+the package.
+
+Issues and pull requests belong here rather than there, because here is the part
+anyone can read.
+
+## Status
+
+Version 0.1.0, the first release. It installs, and the practices it checks are
+the six the book argues for.
+
+What it is not yet: it gates nothing. `glitch-mcp` reports and records and
+cannot block an agent from doing anything. That is deliberate and the reasoning
+is in `mcp_server.py` — a server that stands between an agent and a production
+database should earn its evidence before it earns the power to refuse.

glitch_toolkit-0.1.0/pyproject.toml

@@ -0,0 +1,77 @@
+# Packaging for the toolkit checker.
+#
+# Apache-2.0, decided 2026-09-08, chosen over MIT for the patent grant: if the
+# attestation registry this package is a step toward ever means anything, it
+# means it with a patent grant behind it.
+#
+# The `Private :: Do Not Upload` classifier that used to sit in the list below
+# was removed in the same commit that added LICENSE and NOTICE, which is the
+# condition its own comment set for removing it.
+#
+# The name was decided on 2026-09-08 and is no longer a placeholder. README.md is
+# this package's description on PyPI, so what it says about publication is a
+# public claim rather than a note to ourselves: rebuild the dist after editing
+# it, or the index serves the previous version of that claim.
+#
+# setuptools>=77 is not cosmetic. `license = "Apache-2.0"` is the PEP 639 SPDX
+# form, and on setuptools 61 to 76 it is read as the old free-text field and the
+# build fails. Do not lower this bound without changing that line back.
+
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "glitch-toolkit"
+version = "0.1.0"
+description = "Install and verify bounded-autonomy practices in a repository worked on by AI agents"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+requires-python = ">=3.8"
+keywords = ["claude", "agents", "guardrails", "governance", "ci"]
+classifiers = [
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Topic :: Software Development :: Quality Assurance",
+]
+
+# No runtime dependencies, and this is a promise rather than a coincidence.
+# The checker has to run in a stranger's repository on the first day, before
+# they have installed anything. Adding one is a product decision.
+dependencies = []
+
+# The MCP server is the one thing here that needs anything, and it is optional
+# for that reason. `glitch` keeps its promise; `glitch-mcp` asks first and says
+# so plainly when the SDK is absent rather than dying on an ImportError.
+[project.optional-dependencies]
+mcp = ["mcp>=2.0"]
+
+# Where the PyPI sidebar sends people. Without this table there is no Homepage,
+# no Source and no Issues link, which for a package whose success is measured in
+# issues from strangers is a self-inflicted wound.
+#
+# These point at the PUBLIC mirror, not at the private monorepo the package is
+# developed in. A Source link a stranger cannot open is worse than none.
+[project.urls]
+Homepage = "https://github.com/AbstractGlitch/glitch-toolkit"
+Source = "https://github.com/AbstractGlitch/glitch-toolkit"
+Issues = "https://github.com/AbstractGlitch/glitch-toolkit/issues"
+
+[project.scripts]
+glitch = "glitch.cli:main"
+glitch-mcp = "glitch.mcp_server:main"
+
+[tool.setuptools]
+package-dir = {"" = "src"}
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+glitch = [
+    "_assets/scripts/*.py",
+    "_assets/skills/*/SKILL.md",
+    "_assets/templates/*",
+]

glitch_toolkit-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

glitch_toolkit-0.1.0/src/glitch/__init__.py

@@ -0,0 +1,12 @@
+"""Bounded autonomy for agents working in a repository.
+
+Six practices from *Building Your Store Or Your SaaS With Claude*, installed
+into your own project and checked there. The checker's contract is that an
+artifact counts as installed only when it is present, runs, AND still refuses a
+deliberately broken case; anything that merely passes is treated as not wired up.
+
+The command line is the product. Import it if you want to, but nothing in here
+is a stable API yet.
+"""
+
+__version__ = "0.1.0"

glitch_toolkit-0.1.0/src/glitch/__main__.py

@@ -0,0 +1,7 @@
+"""Allow `python -m glitch` alongside the `glitch` console script."""
+import sys
+
+from .cli import main
+
+if __name__ == "__main__":
+    sys.exit(main())