tinyhorse 0.1.0__tar.gz

tinyhorse-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.

tinyhorse-0.1.0/PKG-INFO

@@ -0,0 +1,185 @@
+Metadata-Version: 2.4
+Name: tinyhorse
+Version: 0.1.0
+Summary: Git-native project control for local and user-owned infrastructure
+Author: Tiny Horse contributors
+License-Expression: Apache-2.0
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: gdrive
+Requires-Dist: google-auth>=2.0; extra == "gdrive"
+Requires-Dist: google-auth-oauthlib>=1.0; extra == "gdrive"
+Provides-Extra: release
+Requires-Dist: build>=1.2; extra == "release"
+Requires-Dist: twine>=6; extra == "release"
+Dynamic: license-file
+
+# Tiny Horse
+
+Tiny Horse is an open-source, Git-native control layer for projects that should remain usable on local or user-owned infrastructure.
+
+It does **not** replace Git. It wraps standard Git operations with a small, stable interface that humans and agents can inspect without depending on GitHub as the source of truth.
+
+## The storage loop
+
+A Tiny Horse project has one canonical Git bundle on user-controlled storage. The repository contains a `.tinyhorse.toml` locator, not a mutable "current release" pointer. HEAD, refs, tags, timestamps, and history come from Git itself.
+
+```bash
+# Bind an existing repo to a local canonical object.
+tinyhorse init . --storage file:/srv/git/my-project.bundle
+
+# Safe by default: only fast-forwards canonical Git and preserves refs.
+tinyhorse push
+tinyhorse doctor
+
+# Recover on another machine.
+tinyhorse pull file:/srv/git/my-project.bundle ./my-project
+```
+
+## Google Drive login
+
+Install the Drive extra once:
+
+```bash
+python -m pip install 'tinyhorse[gdrive]'
+```
+
+Tiny Horse uses Google's installed-app OAuth flow. It opens the browser, obtains a refresh token, and stores the credential **outside the repository**. You do not copy access tokens into shell variables for normal interactive use.
+
+For development builds, provide a Google OAuth **Desktop app** client JSON once:
+
+```bash
+tinyhorse auth login --client-secrets ~/Downloads/client_secret.json
+```
+
+You can instead set `TINYHORSE_GOOGLE_CLIENT_SECRETS` or place that JSON at `~/.config/tinyhorse/google-client.json`. On first login Tiny Horse remembers the client configuration in its user config directory, so later logins do not need the path again. The resolver also supports a packaged `google-client.json`, allowing a first-party Tiny Horse OAuth client to remove this development-only step without changing project configuration.
+
+```bash
+tinyhorse auth status
+# To force a refresh while checking:
+tinyhorse auth status --refresh
+
+tinyhorse auth logout
+```
+
+Saved refreshable credentials default to `~/.config/tinyhorse/google-drive-credentials.json` (or the platform/config override). The file is written with owner-only permissions where the OS supports them. `TINYHORSE_GOOGLE_DRIVE_TOKEN` is still accepted for CI and other intentionally non-interactive environments.
+
+Then Drive setup no longer requires a folder ID or a `gdrive://` locator:
+
+```bash
+tinyhorse init . --drive
+tinyhorse push
+tinyhorse doctor
+```
+
+`init --drive` looks for one top-level Drive folder with the project name, creates
+it if needed, adopts an existing single `.bundle` inside it when present, and
+otherwise chooses a deterministic bundle filename. The resolved locator is stored
+in `.tinyhorse.toml`; it is implementation detail rather than user input.
+
+Explicit `gdrive://FOLDER_ID/FILENAME` locators remain supported for automation
+and unusual layouts. Fresh-machine recovery no longer requires a locator. After authentication:
+
+```bash
+tinyhorse projects
+tinyhorse clone TULKAS
+```
+
+`projects` discovers top-level Drive project folders that are marked by Tiny Horse
+or contain Git bundles, surfaces empty/ambiguous folders instead of guessing, and
+does not print provider folder/file IDs. `clone PROJECT` requires one exact project
+name, restores the canonical bundle, writes the machine-local binding when needed,
+and verifies that the restored working tree is clean. Explicit `pull LOCATOR`
+remains available for automation and unusual layouts.
+
+The Drive adapter searches for exactly one canonical file with that name in that folder. `push` creates it once and then updates the same Drive object in place. Multiple same-named candidates are treated as an error instead of guessed around. Before replacing an existing object, Tiny Horse downloads and verifies canonical Git, compares its durable refs with the local bundle, and rechecks the provider version immediately before upload. It then reads the object back and verifies the result.
+
+
+## One-command GitHub migration
+
+Once Drive authentication is configured, a GitHub repository can be moved into
+Tiny Horse canonical storage with one command:
+
+```bash
+tinyhorse migrate https://github.com/owner/repository.git
+```
+
+Tiny Horse derives the project and local checkout names from the remote, takes a
+read-only mirror snapshot, materializes every source branch plus tags and Git notes
+in a normal working checkout, auto-provisions the Drive project folder, safely
+publishes the canonical bundle, downloads it again, and verifies that its durable
+Git refs exactly match the source snapshot. The GitHub repository is never pushed
+to, rewritten, deleted, archived, or otherwise modified by migration.
+
+The original remote remains configured locally as `origin`, so it can still be
+used as an optional legacy/read source. Canonical authority is the Tiny Horse
+storage binding. For an exact-history import, the generated `.tinyhorse.toml` is
+kept machine-local via `.git/info/exclude`; migration does not add a setup commit
+or otherwise alter the imported Git history.
+
+Useful overrides are available without changing the safe default:
+
+```bash
+# Pick a different checkout directory or display name.
+tinyhorse migrate https://github.com/owner/repository.git ./repo --project "My Project"
+
+# Use any supported user-controlled storage instead of Drive.
+tinyhorse migrate https://github.com/owner/repository.git --storage file:/srv/git/repository.bundle
+```
+
+If the source already tracks a `.tinyhorse.toml`, migration refuses to replace
+that existing binding implicitly.
+
+## Safe push
+
+Normal `tinyhorse push` is deliberately conservative. Canonical branches may only move forward, canonical tags and other durable refs may not be silently rewritten or deleted, and canonical HEAD may not be replaced by a stale or divergent local history. If another writer changes storage after Tiny Horse's preflight read, the push aborts rather than knowingly overwriting that newer state.
+
+For an intentional history rewrite or ref deletion, use `tinyhorse push --force`. Force bypasses the Git ancestry/ref policy, **not** the storage-version check or readback verification. Remote-tracking refs (`refs/remotes/*`) are treated as caches and are no longer packaged as canonical project state.
+
+## CLI
+
+```bash
+tinyhorse status [PATH]
+tinyhorse init [PATH] (--drive | --storage LOCATOR) [--project NAME]
+tinyhorse push [PATH] [--force]
+tinyhorse pull LOCATOR DESTINATION
+tinyhorse doctor [PATH]
+tinyhorse projects
+tinyhorse clone PROJECT [DESTINATION]
+tinyhorse bundle PATH OUTPUT
+tinyhorse verify-bundle BUNDLE
+tinyhorse migrate REMOTE [DESTINATION] [--drive | --storage LOCATOR] [--project NAME]
+tinyhorse auth login [--client-secrets PATH] [--no-browser]
+tinyhorse auth status [--refresh]
+tinyhorse auth logout
+```
+
+`status`, `migrate`, `push`, `pull`, `doctor`, and the auth commands produce machine-readable JSON where appropriate. `doctor` compares local HEAD to the canonical bundle and reports `in_sync`, `local_ahead`, `local_behind`, or `diverged_or_unrelated`. A refused safe push exits without replacing canonical storage and explains which HEAD, branch, tag, or ref would have been lost.
+
+## Why TULKAS matters
+
+TULKAS is the first proving case. It exposed a practical failure mode: when live Git, old GitHub snapshots, and point-in-time backups sit together, a fresh agent can guess wrong about what is current. Tiny Horse's rule is deliberately mechanical: one canonical Git object, archives elsewhere, and no hand-maintained freshness metadata.
+
+## Package release gate
+
+The repository includes a repeatable package release check and artifact builder:
+
+```bash
+python tools/release.py check
+python tools/release.py build --allow-dev   # development candidate
+```
+
+Tiny Horse is licensed under Apache-2.0. A public release requires a final `X.Y.Z`
+version, a matching `vX.Y.Z` Git tag, and package-index credentials. The build is
+made from committed `HEAD`, verifies wheel/sdist metadata, smoke-installs the wheel
+in a clean virtual environment, and writes SHA-256 hashes. See
+`docs/RELEASING.md`.
+
+
+## Development
+
+```bash
+python -m pip install -e .
+python -m unittest discover -s tests -v
+```

tinyhorse-0.1.0/README.md

@@ -0,0 +1,168 @@
+# Tiny Horse
+
+Tiny Horse is an open-source, Git-native control layer for projects that should remain usable on local or user-owned infrastructure.
+
+It does **not** replace Git. It wraps standard Git operations with a small, stable interface that humans and agents can inspect without depending on GitHub as the source of truth.
+
+## The storage loop
+
+A Tiny Horse project has one canonical Git bundle on user-controlled storage. The repository contains a `.tinyhorse.toml` locator, not a mutable "current release" pointer. HEAD, refs, tags, timestamps, and history come from Git itself.
+
+```bash
+# Bind an existing repo to a local canonical object.
+tinyhorse init . --storage file:/srv/git/my-project.bundle
+
+# Safe by default: only fast-forwards canonical Git and preserves refs.
+tinyhorse push
+tinyhorse doctor
+
+# Recover on another machine.
+tinyhorse pull file:/srv/git/my-project.bundle ./my-project
+```
+
+## Google Drive login
+
+Install the Drive extra once:
+
+```bash
+python -m pip install 'tinyhorse[gdrive]'
+```
+
+Tiny Horse uses Google's installed-app OAuth flow. It opens the browser, obtains a refresh token, and stores the credential **outside the repository**. You do not copy access tokens into shell variables for normal interactive use.
+
+For development builds, provide a Google OAuth **Desktop app** client JSON once:
+
+```bash
+tinyhorse auth login --client-secrets ~/Downloads/client_secret.json
+```
+
+You can instead set `TINYHORSE_GOOGLE_CLIENT_SECRETS` or place that JSON at `~/.config/tinyhorse/google-client.json`. On first login Tiny Horse remembers the client configuration in its user config directory, so later logins do not need the path again. The resolver also supports a packaged `google-client.json`, allowing a first-party Tiny Horse OAuth client to remove this development-only step without changing project configuration.
+
+```bash
+tinyhorse auth status
+# To force a refresh while checking:
+tinyhorse auth status --refresh
+
+tinyhorse auth logout
+```
+
+Saved refreshable credentials default to `~/.config/tinyhorse/google-drive-credentials.json` (or the platform/config override). The file is written with owner-only permissions where the OS supports them. `TINYHORSE_GOOGLE_DRIVE_TOKEN` is still accepted for CI and other intentionally non-interactive environments.
+
+Then Drive setup no longer requires a folder ID or a `gdrive://` locator:
+
+```bash
+tinyhorse init . --drive
+tinyhorse push
+tinyhorse doctor
+```
+
+`init --drive` looks for one top-level Drive folder with the project name, creates
+it if needed, adopts an existing single `.bundle` inside it when present, and
+otherwise chooses a deterministic bundle filename. The resolved locator is stored
+in `.tinyhorse.toml`; it is implementation detail rather than user input.
+
+Explicit `gdrive://FOLDER_ID/FILENAME` locators remain supported for automation
+and unusual layouts. Fresh-machine recovery no longer requires a locator. After authentication:
+
+```bash
+tinyhorse projects
+tinyhorse clone TULKAS
+```
+
+`projects` discovers top-level Drive project folders that are marked by Tiny Horse
+or contain Git bundles, surfaces empty/ambiguous folders instead of guessing, and
+does not print provider folder/file IDs. `clone PROJECT` requires one exact project
+name, restores the canonical bundle, writes the machine-local binding when needed,
+and verifies that the restored working tree is clean. Explicit `pull LOCATOR`
+remains available for automation and unusual layouts.
+
+The Drive adapter searches for exactly one canonical file with that name in that folder. `push` creates it once and then updates the same Drive object in place. Multiple same-named candidates are treated as an error instead of guessed around. Before replacing an existing object, Tiny Horse downloads and verifies canonical Git, compares its durable refs with the local bundle, and rechecks the provider version immediately before upload. It then reads the object back and verifies the result.
+
+
+## One-command GitHub migration
+
+Once Drive authentication is configured, a GitHub repository can be moved into
+Tiny Horse canonical storage with one command:
+
+```bash
+tinyhorse migrate https://github.com/owner/repository.git
+```
+
+Tiny Horse derives the project and local checkout names from the remote, takes a
+read-only mirror snapshot, materializes every source branch plus tags and Git notes
+in a normal working checkout, auto-provisions the Drive project folder, safely
+publishes the canonical bundle, downloads it again, and verifies that its durable
+Git refs exactly match the source snapshot. The GitHub repository is never pushed
+to, rewritten, deleted, archived, or otherwise modified by migration.
+
+The original remote remains configured locally as `origin`, so it can still be
+used as an optional legacy/read source. Canonical authority is the Tiny Horse
+storage binding. For an exact-history import, the generated `.tinyhorse.toml` is
+kept machine-local via `.git/info/exclude`; migration does not add a setup commit
+or otherwise alter the imported Git history.
+
+Useful overrides are available without changing the safe default:
+
+```bash
+# Pick a different checkout directory or display name.
+tinyhorse migrate https://github.com/owner/repository.git ./repo --project "My Project"
+
+# Use any supported user-controlled storage instead of Drive.
+tinyhorse migrate https://github.com/owner/repository.git --storage file:/srv/git/repository.bundle
+```
+
+If the source already tracks a `.tinyhorse.toml`, migration refuses to replace
+that existing binding implicitly.
+
+## Safe push
+
+Normal `tinyhorse push` is deliberately conservative. Canonical branches may only move forward, canonical tags and other durable refs may not be silently rewritten or deleted, and canonical HEAD may not be replaced by a stale or divergent local history. If another writer changes storage after Tiny Horse's preflight read, the push aborts rather than knowingly overwriting that newer state.
+
+For an intentional history rewrite or ref deletion, use `tinyhorse push --force`. Force bypasses the Git ancestry/ref policy, **not** the storage-version check or readback verification. Remote-tracking refs (`refs/remotes/*`) are treated as caches and are no longer packaged as canonical project state.
+
+## CLI
+
+```bash
+tinyhorse status [PATH]
+tinyhorse init [PATH] (--drive | --storage LOCATOR) [--project NAME]
+tinyhorse push [PATH] [--force]
+tinyhorse pull LOCATOR DESTINATION
+tinyhorse doctor [PATH]
+tinyhorse projects
+tinyhorse clone PROJECT [DESTINATION]
+tinyhorse bundle PATH OUTPUT
+tinyhorse verify-bundle BUNDLE
+tinyhorse migrate REMOTE [DESTINATION] [--drive | --storage LOCATOR] [--project NAME]
+tinyhorse auth login [--client-secrets PATH] [--no-browser]
+tinyhorse auth status [--refresh]
+tinyhorse auth logout
+```
+
+`status`, `migrate`, `push`, `pull`, `doctor`, and the auth commands produce machine-readable JSON where appropriate. `doctor` compares local HEAD to the canonical bundle and reports `in_sync`, `local_ahead`, `local_behind`, or `diverged_or_unrelated`. A refused safe push exits without replacing canonical storage and explains which HEAD, branch, tag, or ref would have been lost.
+
+## Why TULKAS matters
+
+TULKAS is the first proving case. It exposed a practical failure mode: when live Git, old GitHub snapshots, and point-in-time backups sit together, a fresh agent can guess wrong about what is current. Tiny Horse's rule is deliberately mechanical: one canonical Git object, archives elsewhere, and no hand-maintained freshness metadata.
+
+## Package release gate
+
+The repository includes a repeatable package release check and artifact builder:
+
+```bash
+python tools/release.py check
+python tools/release.py build --allow-dev   # development candidate
+```
+
+Tiny Horse is licensed under Apache-2.0. A public release requires a final `X.Y.Z`
+version, a matching `vX.Y.Z` Git tag, and package-index credentials. The build is
+made from committed `HEAD`, verifies wheel/sdist metadata, smoke-installs the wheel
+in a clean virtual environment, and writes SHA-256 hashes. See
+`docs/RELEASING.md`.
+
+
+## Development
+
+```bash
+python -m pip install -e .
+python -m unittest discover -s tests -v
+```

tinyhorse-0.1.0/pyproject.toml

@@ -0,0 +1,30 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "tinyhorse"
+version = "0.1.0"
+description = "Git-native project control for local and user-owned infrastructure"
+readme = "README.md"
+requires-python = ">=3.10"
+authors = [{name = "Tiny Horse contributors"}]
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+dependencies = []
+
+[project.optional-dependencies]
+gdrive = [
+  "google-auth>=2.0",
+  "google-auth-oauthlib>=1.0",
+]
+release = [
+  "build>=1.2",
+  "twine>=6",
+]
+
+[project.scripts]
+tinyhorse = "tinyhorse.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]

tinyhorse-0.1.0/setup.cfg

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

tinyhorse-0.1.0/src/tinyhorse/__init__.py

@@ -0,0 +1,3 @@
+"""Tiny Horse: Git-native project control."""
+
+__version__ = "0.1.0"

tinyhorse-0.1.0/src/tinyhorse/__main__.py

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