chesterton 0.1.1__tar.gz

chesterton-0.1.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Blueangelman36
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

chesterton-0.1.1/PKG-INFO

@@ -0,0 +1,80 @@
+Metadata-Version: 2.4
+Name: chesterton
+Version: 0.1.1
+Summary: Remember why code exists, and speak up before it's removed.
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/Blueangelman36/chesterton
+Project-URL: Repository, https://github.com/Blueangelman36/chesterton
+Project-URL: Issues, https://github.com/Blueangelman36/chesterton/issues
+Keywords: git,hooks,pre-commit,code-review,documentation,refactoring
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Version Control :: Git
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# chesterton
+
+*Don't take down a fence until you know why it was put up.*
+
+`fence` remembers **why** code exists, and speaks up when a commit is about to delete it.
+
+Some of the most painful bugs start the same way: someone removes a strange-looking retry loop,
+a `sleep(50)`, or an `if` that "can't happen", and it turns out it could. The person who wrote it
+knew why. That reason lived in a closed pull request, a chat thread, or their head, and none of
+those are open when the next person edits the file.
+
+Notes are pinned to statements in the syntax tree rather than to line numbers, so they follow the
+code through reformatting, identifier renames, and moves between files.
+
+```bash
+pip install chesterton
+cd your-project
+fence init
+fence add src/client.py:42 -m "Vendor API returns 200 on auth failure; the error is in the body."
+```
+
+Later, when someone deletes that check:
+
+```text
+$ git commit -m "Simplify fetch"
+[REMOVED] 1559744b  src/client.py:42  in Client.fetch
+    why: Vendor API returns 200 on auth failure; the error is in the body.
+    was: if resp.json().get("error") == "unauthorized":
+
+fence: 1 note(s) checked: 1 REMOVED
+  reason no longer applies?    fence retire <id> -m "what changed"
+  code lives somewhere new?    fence reanchor <id> <file>:<line>
+  commit anyway?               git commit --no-verify
+```
+
+Renaming or moving that code instead blocks nothing — the note follows it.
+
+## For coding agents
+
+```bash
+fence why src/client.py --json    # before changing code you did not write
+fence check --json                # what a blocked commit is objecting to
+fence init --agents               # write the instructions where agents will find them
+```
+
+## Status
+
+A prototype of the core loop: anchoring plus the hook. **Python source only** — the design is not
+Python-specific, and a tree-sitter implementation for other languages is in progress. Measured
+against requests, flask, pytest, django and a slice of the standard library (3,613 files): no
+false alarms, and every deliberate deletion caught.
+
+No dependencies. Python 3.11+. <!-- asof:python-version --> MIT licensed.
+
+Full documentation, the note format specification, and the conformance suite live in the
+repository.

chesterton-0.1.1/README.md

@@ -0,0 +1,56 @@
+# chesterton
+
+*Don't take down a fence until you know why it was put up.*
+
+`fence` remembers **why** code exists, and speaks up when a commit is about to delete it.
+
+Some of the most painful bugs start the same way: someone removes a strange-looking retry loop,
+a `sleep(50)`, or an `if` that "can't happen", and it turns out it could. The person who wrote it
+knew why. That reason lived in a closed pull request, a chat thread, or their head, and none of
+those are open when the next person edits the file.
+
+Notes are pinned to statements in the syntax tree rather than to line numbers, so they follow the
+code through reformatting, identifier renames, and moves between files.
+
+```bash
+pip install chesterton
+cd your-project
+fence init
+fence add src/client.py:42 -m "Vendor API returns 200 on auth failure; the error is in the body."
+```
+
+Later, when someone deletes that check:
+
+```text
+$ git commit -m "Simplify fetch"
+[REMOVED] 1559744b  src/client.py:42  in Client.fetch
+    why: Vendor API returns 200 on auth failure; the error is in the body.
+    was: if resp.json().get("error") == "unauthorized":
+
+fence: 1 note(s) checked: 1 REMOVED
+  reason no longer applies?    fence retire <id> -m "what changed"
+  code lives somewhere new?    fence reanchor <id> <file>:<line>
+  commit anyway?               git commit --no-verify
+```
+
+Renaming or moving that code instead blocks nothing — the note follows it.
+
+## For coding agents
+
+```bash
+fence why src/client.py --json    # before changing code you did not write
+fence check --json                # what a blocked commit is objecting to
+fence init --agents               # write the instructions where agents will find them
+```
+
+## Status
+
+A prototype of the core loop: anchoring plus the hook. **Python source only** — the design is not
+Python-specific, and a tree-sitter implementation for other languages is in progress. Measured
+against requests, flask, pytest, django and a slice of the standard library (3,613 files): no
+false alarms, and every deliberate deletion caught.
+
+No dependencies. Python 3.11+. <!-- asof:python-version --> MIT licensed.
+
+Full documentation, the note format specification, and the conformance suite live in the
+repository.

chesterton-0.1.1/chesterton.egg-info/PKG-INFO

@@ -0,0 +1,80 @@
+Metadata-Version: 2.4
+Name: chesterton
+Version: 0.1.1
+Summary: Remember why code exists, and speak up before it's removed.
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/Blueangelman36/chesterton
+Project-URL: Repository, https://github.com/Blueangelman36/chesterton
+Project-URL: Issues, https://github.com/Blueangelman36/chesterton/issues
+Keywords: git,hooks,pre-commit,code-review,documentation,refactoring
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Version Control :: Git
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# chesterton
+
+*Don't take down a fence until you know why it was put up.*
+
+`fence` remembers **why** code exists, and speaks up when a commit is about to delete it.
+
+Some of the most painful bugs start the same way: someone removes a strange-looking retry loop,
+a `sleep(50)`, or an `if` that "can't happen", and it turns out it could. The person who wrote it
+knew why. That reason lived in a closed pull request, a chat thread, or their head, and none of
+those are open when the next person edits the file.
+
+Notes are pinned to statements in the syntax tree rather than to line numbers, so they follow the
+code through reformatting, identifier renames, and moves between files.
+
+```bash
+pip install chesterton
+cd your-project
+fence init
+fence add src/client.py:42 -m "Vendor API returns 200 on auth failure; the error is in the body."
+```
+
+Later, when someone deletes that check:
+
+```text
+$ git commit -m "Simplify fetch"
+[REMOVED] 1559744b  src/client.py:42  in Client.fetch
+    why: Vendor API returns 200 on auth failure; the error is in the body.
+    was: if resp.json().get("error") == "unauthorized":
+
+fence: 1 note(s) checked: 1 REMOVED
+  reason no longer applies?    fence retire <id> -m "what changed"
+  code lives somewhere new?    fence reanchor <id> <file>:<line>
+  commit anyway?               git commit --no-verify
+```
+
+Renaming or moving that code instead blocks nothing — the note follows it.
+
+## For coding agents
+
+```bash
+fence why src/client.py --json    # before changing code you did not write
+fence check --json                # what a blocked commit is objecting to
+fence init --agents               # write the instructions where agents will find them
+```
+
+## Status
+
+A prototype of the core loop: anchoring plus the hook. **Python source only** — the design is not
+Python-specific, and a tree-sitter implementation for other languages is in progress. Measured
+against requests, flask, pytest, django and a slice of the standard library (3,613 files): no
+false alarms, and every deliberate deletion caught.
+
+No dependencies. Python 3.11+. <!-- asof:python-version --> MIT licensed.
+
+Full documentation, the note format specification, and the conformance suite live in the
+repository.

chesterton-0.1.1/chesterton.egg-info/SOURCES.txt

@@ -0,0 +1,23 @@
+LICENSE
+README.md
+pyproject.toml
+chesterton.egg-info/PKG-INFO
+chesterton.egg-info/SOURCES.txt
+chesterton.egg-info/dependency_links.txt
+chesterton.egg-info/entry_points.txt
+chesterton.egg-info/top_level.txt
+fence/__init__.py
+fence/__main__.py
+fence/anchor.py
+fence/cache.py
+fence/cli.py
+fence/gitutil.py
+fence/store.py
+fence/suggest.py
+tests/test_anchor.py
+tests/test_cache.py
+tests/test_cli.py
+tests/test_conformance.py
+tests/test_golden.py
+tests/test_pr_comment.py
+tests/test_suggest.py

chesterton-0.1.1/chesterton.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

chesterton-0.1.1/chesterton.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+fence = fence.cli:main

chesterton-0.1.1/chesterton.egg-info/top_level.txt

@@ -0,0 +1 @@
+fence

chesterton-0.1.1/fence/__init__.py

@@ -0,0 +1,7 @@
+"""Remember why code exists, and speak up before it's removed."""
+
+__version__ = "0.1.1"
+
+
+class FenceError(Exception):
+    """A problem worth showing the user as-is, without a traceback."""

chesterton-0.1.1/fence/__main__.py

@@ -0,0 +1,3 @@
+from fence.cli import main
+
+raise SystemExit(main())