relore 0.3.17__tar.gz

relore-0.3.17/LICENSE

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

relore-0.3.17/PKG-INFO

@@ -0,0 +1,125 @@
+Metadata-Version: 2.4
+Name: relore
+Version: 0.3.17
+Summary: GitHub project memory: index a repository's issue/PR history and serve it to agents and humans
+Author-email: The Hugging Face Team <transformers@huggingface.co>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/huggingface/relore
+Project-URL: Repository, https://github.com/huggingface/relore
+Project-URL: Documentation, https://github.com/huggingface/relore/tree/main/docs
+Project-URL: Issues, https://github.com/huggingface/relore/issues
+Project-URL: Changelog, https://github.com/huggingface/relore/blob/main/CHANGELOG.md
+Keywords: github,issues,search,agents,project-memory
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx>=0.27
+Provides-Extra: server
+Requires-Dist: SQLAlchemy>=2.0; extra == "server"
+Requires-Dist: fastapi>=0.110; extra == "server"
+Requires-Dist: uvicorn>=0.29; extra == "server"
+Requires-Dist: pydantic>=2.6; extra == "server"
+Provides-Extra: postgres
+Requires-Dist: relore[server]; extra == "postgres"
+Requires-Dist: psycopg[binary]>=3.1; extra == "postgres"
+Provides-Extra: code
+Requires-Dist: tree-sitter>=0.21; extra == "code"
+Provides-Extra: python
+Requires-Dist: relore[code]; extra == "python"
+Requires-Dist: tree-sitter-python>=0.21; extra == "python"
+Provides-Extra: dev
+Requires-Dist: relore[postgres,python]; extra == "dev"
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: ruff>=0.5; extra == "dev"
+Dynamic: license-file
+
+# relore — GitHub project memory
+
+**Every codebase has lore. Ask it, then check it against the code.**
+
+<img src="docs/relore.png" alt="logo" width="200">
+
+`relore` indexes a repository's complete issue and pull-request history and keeps a working
+clone beside it, both served over one HTTP API. Three questions, in the order an agent hits
+them:
+
+**1. Is somebody already doing this?** `inflight <issue>` — every open claimant, its state
+and its author, in one hop. The most expensive thing an agent does is patch something that
+is already in review.
+
+**2. Why is it like this?** Why a fallback cannot be removed, which approach was tried and
+rejected, what a maintainer made the last five contributors change — none of it is in the
+codebase. `thread`, `why PATH:LINE` and `search` return it at comment level with who said
+it attached, so `--trust authoritative` keeps only what someone with write access settled
+and machine authors are excluded by default. `search --symbol GemmaRotaryEmbedding` asks
+what has been *said* about a function — a question `grep` cannot answer.
+
+**3. Is that still true?** `grep`, `symbol` and `copies` run against that clone at HEAD,
+server-side, no checkout on your side. A three-year-old review is a claim about code that
+has moved since.
+
+![Relore connects project history with current code to answer an agent's three questions.](docs/relore-diag.png)
+
+Threads tell you what people decided; the code verbs tell you whether it was true. A
+[contributor claim] confirmed by `grep` is stronger evidence than either alone — the
+argument for this over a search box.
+
+Six agents have run it cold on the same `transformers` bug, one per release, on `--help`
+alone and with no memory of the runs before. They filed 39 issues against the tool; most
+are fixed, each run checking the last one's from the outside.
+[#8](https://github.com/huggingface/relore/issues/8) is the record.
+
+## Get started
+
+- [Deploy the service](docs/operations.md).
+- [Use relore](docs/cli.md).
+
+## What you get
+
+| | |
+| --- | --- |
+| **Comment-level results** | the matching document with its author, trust tier, age and URL — not a thread number to go re-read |
+| **Exact signals** | errors, files, symbols, test ids, shas, extracted at ingest and repeatable as filters |
+| **Trust tiers** | maintainer / contributor / bot, as a filter rather than a weight |
+| **Schema to join on** | "which threads touched this file", and a bug and its merged fix as one record — `search --file` under-returns the newest PRs touching a path until [#48](https://github.com/huggingface/relore/issues/48) lands |
+| **The code, server-side** | `why PATH:LINE`, `grep`, `copies`, `symbol`, and `defs`/`refs` with `--repo`, against a working clone the daemon keeps |
+| **Throughput** | every query is a Postgres query and makes no GitHub request; ten agents in parallel cost the same as one |
+
+The trade is freshness: each thread records its last indexing visit; later GitHub changes
+are unknown. Collector poll times do not guarantee freshness for every thread.
+[Why not GitHub search](docs/why-not-github-search.md) has the measurements.
+
+Running the daemon needs a Postgres and a GitHub token with `issues:read` +
+`pull_requests:read` — never write. `deploy/` has a Helm chart and the scripts that are its
+interface; setup is in [`docs/operations.md`](docs/operations.md).
+
+## Docs
+
+- [`docs/how-search-works.md`](docs/how-search-works.md) — what kind of index this is
+  (lexical and ranked, no embeddings), and what it is better and worse at than `grep`.
+- [`docs/cli.md`](docs/cli.md) — worked queries, and the empty results that are not faults.
+- [`docs/why-not-github-search.md`](docs/why-not-github-search.md) — the comparison.
+- [`docs/architecture.md`](docs/architecture.md) — what is indexed, what is deliberately
+  not, the symbol lens, and language plugins.
+- [`docs/agents.md`](docs/agents.md) — wiring it into a harness (not to be confused with
+  `AGENTS.md` below, which is the contributor contract for this repository).
+- [`docs/ranking.md`](docs/ranking.md) — the scoring model and what the benchmark says.
+- [`docs/operations.md`](docs/operations.md) — backfill, poll, clones, tokens, serving.
+- [`docs/security.md`](docs/security.md) — the properties and how each is enforced.
+- [`docs/release.md`](docs/release.md) — release branches, tags, and PyPI publishing.
+- [`CHANGELOG.md`](CHANGELOG.md) — notable changes by release.
+- [`docs/prior-art.md`](docs/prior-art.md) — related work, and what was borrowed.
+- [`AGENTS.md`](AGENTS.md) — the operating contract: the invariants with tests behind them.
+
+## License
+
+[Apache-2.0](LICENSE).

relore-0.3.17/README.md

@@ -0,0 +1,81 @@
+# relore — GitHub project memory
+
+**Every codebase has lore. Ask it, then check it against the code.**
+
+<img src="docs/relore.png" alt="logo" width="200">
+
+`relore` indexes a repository's complete issue and pull-request history and keeps a working
+clone beside it, both served over one HTTP API. Three questions, in the order an agent hits
+them:
+
+**1. Is somebody already doing this?** `inflight <issue>` — every open claimant, its state
+and its author, in one hop. The most expensive thing an agent does is patch something that
+is already in review.
+
+**2. Why is it like this?** Why a fallback cannot be removed, which approach was tried and
+rejected, what a maintainer made the last five contributors change — none of it is in the
+codebase. `thread`, `why PATH:LINE` and `search` return it at comment level with who said
+it attached, so `--trust authoritative` keeps only what someone with write access settled
+and machine authors are excluded by default. `search --symbol GemmaRotaryEmbedding` asks
+what has been *said* about a function — a question `grep` cannot answer.
+
+**3. Is that still true?** `grep`, `symbol` and `copies` run against that clone at HEAD,
+server-side, no checkout on your side. A three-year-old review is a claim about code that
+has moved since.
+
+![Relore connects project history with current code to answer an agent's three questions.](docs/relore-diag.png)
+
+Threads tell you what people decided; the code verbs tell you whether it was true. A
+[contributor claim] confirmed by `grep` is stronger evidence than either alone — the
+argument for this over a search box.
+
+Six agents have run it cold on the same `transformers` bug, one per release, on `--help`
+alone and with no memory of the runs before. They filed 39 issues against the tool; most
+are fixed, each run checking the last one's from the outside.
+[#8](https://github.com/huggingface/relore/issues/8) is the record.
+
+## Get started
+
+- [Deploy the service](docs/operations.md).
+- [Use relore](docs/cli.md).
+
+## What you get
+
+| | |
+| --- | --- |
+| **Comment-level results** | the matching document with its author, trust tier, age and URL — not a thread number to go re-read |
+| **Exact signals** | errors, files, symbols, test ids, shas, extracted at ingest and repeatable as filters |
+| **Trust tiers** | maintainer / contributor / bot, as a filter rather than a weight |
+| **Schema to join on** | "which threads touched this file", and a bug and its merged fix as one record — `search --file` under-returns the newest PRs touching a path until [#48](https://github.com/huggingface/relore/issues/48) lands |
+| **The code, server-side** | `why PATH:LINE`, `grep`, `copies`, `symbol`, and `defs`/`refs` with `--repo`, against a working clone the daemon keeps |
+| **Throughput** | every query is a Postgres query and makes no GitHub request; ten agents in parallel cost the same as one |
+
+The trade is freshness: each thread records its last indexing visit; later GitHub changes
+are unknown. Collector poll times do not guarantee freshness for every thread.
+[Why not GitHub search](docs/why-not-github-search.md) has the measurements.
+
+Running the daemon needs a Postgres and a GitHub token with `issues:read` +
+`pull_requests:read` — never write. `deploy/` has a Helm chart and the scripts that are its
+interface; setup is in [`docs/operations.md`](docs/operations.md).
+
+## Docs
+
+- [`docs/how-search-works.md`](docs/how-search-works.md) — what kind of index this is
+  (lexical and ranked, no embeddings), and what it is better and worse at than `grep`.
+- [`docs/cli.md`](docs/cli.md) — worked queries, and the empty results that are not faults.
+- [`docs/why-not-github-search.md`](docs/why-not-github-search.md) — the comparison.
+- [`docs/architecture.md`](docs/architecture.md) — what is indexed, what is deliberately
+  not, the symbol lens, and language plugins.
+- [`docs/agents.md`](docs/agents.md) — wiring it into a harness (not to be confused with
+  `AGENTS.md` below, which is the contributor contract for this repository).
+- [`docs/ranking.md`](docs/ranking.md) — the scoring model and what the benchmark says.
+- [`docs/operations.md`](docs/operations.md) — backfill, poll, clones, tokens, serving.
+- [`docs/security.md`](docs/security.md) — the properties and how each is enforced.
+- [`docs/release.md`](docs/release.md) — release branches, tags, and PyPI publishing.
+- [`CHANGELOG.md`](CHANGELOG.md) — notable changes by release.
+- [`docs/prior-art.md`](docs/prior-art.md) — related work, and what was borrowed.
+- [`AGENTS.md`](AGENTS.md) — the operating contract: the invariants with tests behind them.
+
+## License
+
+[Apache-2.0](LICENSE).

relore-0.3.17/pyproject.toml

@@ -0,0 +1,78 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "relore"
+# Read from relore/__init__.py: the client and the daemon refuse to talk across a version
+# difference (relore/wire.py), so two places to write it is one place to get it wrong.
+dynamic = ["version"]
+description = "GitHub project memory: index a repository's issue/PR history and serve it to agents and humans"
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "The Hugging Face Team", email = "transformers@huggingface.co" }]
+keywords = ["github", "issues", "search", "agents", "project-memory"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development",
+]
+
+# The base install is the CLIENT. It must stay small enough to `pip install` inside a
+# constrained agent sandbox: no database driver, no parser, no ML stack.
+# See AGENTS.md, "The four invariants".
+dependencies = ["httpx>=0.27"]
+
+[project.optional-dependencies]
+# The daemon. Never a base dependency -- see the build plan section 2.
+# SQLAlchemy Core (not the ORM) owns the portable half of the schema; SQLite needs no
+# driver, so `[server]` alone runs on a dev laptop and in the test suite.
+server = ["SQLAlchemy>=2.0", "fastapi>=0.110", "uvicorn>=0.29", "pydantic>=2.6"]
+# Production. SQLite is for tests and laptops only -- see AGENTS.md.
+postgres = ["relore[server]", "psycopg[binary]>=3.1"]
+# The code-lens engine. Ships no grammars.
+code = ["tree-sitter>=0.21"]
+# One extra per language. Adding a language must not touch core.
+python = ["relore[code]", "tree-sitter-python>=0.21"]
+dev = ["relore[postgres,python]", "pytest>=8", "ruff>=0.5"]
+
+[project.scripts]
+relore = "relore.cli:main"
+# Through the shim, not straight at `relore.daemon:main`: the base install registers this
+# script and does NOT carry the daemon's dependencies, so the import has to be guarded or
+# a client-only install answers `relored --help` with a ModuleNotFoundError traceback.
+relored = "relore.entrypoints:relored"
+
+[project.urls]
+Homepage = "https://github.com/huggingface/relore"
+Repository = "https://github.com/huggingface/relore"
+Documentation = "https://github.com/huggingface/relore/tree/main/docs"
+Issues = "https://github.com/huggingface/relore/issues"
+Changelog = "https://github.com/huggingface/relore/blob/main/CHANGELOG.md"
+
+[project.entry-points."relore.languages"]
+python = "relore.code.providers.python:PythonProvider"
+
+[tool.setuptools.dynamic]
+version = { attr = "relore.__version__" }
+
+[tool.setuptools.packages.find]
+include = ["relore*"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py310"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B", "SIM"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

relore-0.3.17/relore/__init__.py

@@ -0,0 +1,12 @@
+"""relore -- GitHub project memory."""
+
+#: The one place the version is written. ``pyproject.toml`` reads it from here, so the
+#: distribution, ``relore --version``, ``relored --version``, the ``/api/v1/status``
+#: payload and the wire handshake (:mod:`relore.wire`) can never disagree.
+#:
+#: The minor is the milestone the build plan considers complete; the patch is every
+#: release inside it. **Bump it in the same commit as any change a client can see** --
+#: a wire payload, a renderer, a CLI flag -- because the client and the daemon must run
+#: the same version to talk at all (:mod:`relore.wire`), which makes this string the
+#: compatibility contract rather than a label.
+__version__ = "0.3.17"