issue-boundary-evidence 0.1.2__tar.gz

issue_boundary_evidence-0.1.2/LICENSE

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

issue_boundary_evidence-0.1.2/PKG-INFO

@@ -0,0 +1,144 @@
+Metadata-Version: 2.4
+Name: issue-boundary-evidence
+Version: 0.1.2
+Summary: Read-only, deterministic boundary evidence extraction for public GitHub issues
+Author: Issue Boundary Evidence contributors
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/LaimaWu/issue-boundary-evidence
+Project-URL: Issues, https://github.com/LaimaWu/issue-boundary-evidence/issues
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# Issue Boundary Evidence
+
+A small read-only CLI for OSS maintainers that extracts traceable dependency, upstream, runtime, and version-history evidence from public GitHub Issues.
+
+## Why
+
+Some issues are not hard because the code change is difficult. They are hard because the maintainer first has to determine:
+
+- which package, plugin, runtime, or external system is involved;
+- whether behavior changed across versions;
+- whether investigation belongs upstream;
+- what evidence is still missing.
+
+Issue Boundary Evidence collects those clues without changing the issue or claiming to decide the root cause.
+
+## What it does
+
+Given one public GitHub Issue URL, the CLI reads the title, body, all comments, and a small number of explicitly referenced same-repository issues or pull requests. It produces a Markdown report with:
+
+- environment, package, ABI, and version facts;
+- dependency, plugin, runtime, and upstream boundary candidates;
+- version and regression clues;
+- contextual same-repository commit-history clues;
+- external repository/service domains found in CI or infrastructure context;
+- related GitHub evidence;
+- explicit evidence gaps;
+- source URL, source kind, location, and excerpt for every evidence item.
+
+Each item is typed as `fact`, `strong_clue`, or `weak_clue`. These labels measure evidence strength; they are not final root-cause or bug-owner decisions.
+
+## What it does not do
+
+It does not comment, label, close, or otherwise modify GitHub Issues. It does not run issue code, follow arbitrary downloads, clone linked repositories, fix bugs, use an LLM/API, or replace maintainer judgment.
+
+## Requirements
+
+- Python 3.10 or newer
+- Network access to public `api.github.com`
+- Optional `GITHUB_TOKEN` for a higher GitHub read-only API rate limit
+
+There are no runtime package dependencies.
+
+## Install from the v0.1.2 GitHub release
+
+Install the wheel attached to the v0.1.2 GitHub release:
+
+```bash
+python -m pip install https://github.com/LaimaWu/issue-boundary-evidence/releases/download/v0.1.2/issue_boundary_evidence-0.1.2-py3-none-any.whl
+```
+
+## PyPI installation pending
+
+PyPI publication is not live yet. After the first Trusted Publishing run succeeds, the package will be installable with:
+
+```bash
+python -m pip install issue-boundary-evidence
+```
+
+Until then, use the GitHub release wheel or the contributor installation below.
+
+## Contributor install
+
+From the repository root:
+
+```bash
+python3 -m venv .venv
+. .venv/bin/activate
+python -m pip install -e .
+```
+
+## Run
+
+Print a report:
+
+```bash
+issue-boundary-evidence https://github.com/OWNER/REPO/issues/123
+```
+
+Write it to a file:
+
+```bash
+issue-boundary-evidence https://github.com/OWNER/REPO/issues/123 --output report.md
+```
+
+Run without installing:
+
+```bash
+PYTHONPATH=src python -m issue_boundary_evidence.cli https://github.com/OWNER/REPO/issues/123
+```
+
+## Test
+
+```bash
+PYTHONPATH=src python -m unittest discover -s tests -v
+```
+
+The unit tests use local fixtures and do not require network access.
+
+## Examples
+
+Generated reports are in [`examples/`](examples/):
+
+- `pandas-58927.md`
+- `pytest-12430.md`
+- `numpy-26622.md`
+
+The complete frozen ten-issue precision-pass run is stored in [`eval_outputs/`](eval_outputs/). These are raw CLI reports for human retrospective scoring; the project does not assign its own GO/REVISE/STOP score.
+
+## Retrieval boundary
+
+The CLI uses only GitHub's public, read-only REST endpoints. It fetches all comments on the requested issue. It retrieves up to five same-repository issues or pull requests only when the issue or comments explicitly link them or use contextual wording such as `see #123`, `PR #123`, or `fixed by #123`. Bare numbers and references inside code fences are not retrieved. Contextual commit SHAs are linked without fetching their diffs. Non-GitHub service URLs can identify an infrastructure boundary, but the CLI records their domains without requesting them.
+
+Version-like values are extracted deterministically, then the report prioritizes versions tied to the current repository, complete Python/runtime tokens, boundary language, compatibility, regression, or release/fix prose. Markdown-linked patch versions are supported. This avoids presenting every compiler, package-name substring, or toolchain value in a large environment dump as equally important.
+
+Packaging tools such as `pip`, `setuptools`, and `wheel` are promoted only when their version or behavior directly affects the investigation—for example, selecting the correct ABI wheel. Generic install commands, CI logs, and package lists are not sufficient. Quoted copies of identical regression sentences are collapsed while retaining their source links.
+
+## Security
+
+All issue content is untrusted text. The tool never evaluates or executes issue bodies, comments, code blocks, commands, or reporter-provided scripts. HTTP methods are limited to `GET`; no GitHub write operations exist in the client.
+
+## Validation
+
+This is an experimental deterministic maintainer tool. The repository includes a frozen retrospective evaluation set built from historical pandas, pytest, and NumPy issues where maintainers later discussed dependency, runtime, upstream, infrastructure, or version-history boundaries. Raw generated reports are stored in [`eval_outputs/`](eval_outputs/). This evaluation is intended to expose strengths and failure modes; it is not a claim of universal accuracy.
+
+## Current status
+
+Experimental deterministic CLI. See [`EVAL_NOTES.md`](EVAL_NOTES.md) for the retrospective evaluation procedure.
+
+## License
+
+Apache-2.0.

issue_boundary_evidence-0.1.2/README.md

@@ -0,0 +1,131 @@
+# Issue Boundary Evidence
+
+A small read-only CLI for OSS maintainers that extracts traceable dependency, upstream, runtime, and version-history evidence from public GitHub Issues.
+
+## Why
+
+Some issues are not hard because the code change is difficult. They are hard because the maintainer first has to determine:
+
+- which package, plugin, runtime, or external system is involved;
+- whether behavior changed across versions;
+- whether investigation belongs upstream;
+- what evidence is still missing.
+
+Issue Boundary Evidence collects those clues without changing the issue or claiming to decide the root cause.
+
+## What it does
+
+Given one public GitHub Issue URL, the CLI reads the title, body, all comments, and a small number of explicitly referenced same-repository issues or pull requests. It produces a Markdown report with:
+
+- environment, package, ABI, and version facts;
+- dependency, plugin, runtime, and upstream boundary candidates;
+- version and regression clues;
+- contextual same-repository commit-history clues;
+- external repository/service domains found in CI or infrastructure context;
+- related GitHub evidence;
+- explicit evidence gaps;
+- source URL, source kind, location, and excerpt for every evidence item.
+
+Each item is typed as `fact`, `strong_clue`, or `weak_clue`. These labels measure evidence strength; they are not final root-cause or bug-owner decisions.
+
+## What it does not do
+
+It does not comment, label, close, or otherwise modify GitHub Issues. It does not run issue code, follow arbitrary downloads, clone linked repositories, fix bugs, use an LLM/API, or replace maintainer judgment.
+
+## Requirements
+
+- Python 3.10 or newer
+- Network access to public `api.github.com`
+- Optional `GITHUB_TOKEN` for a higher GitHub read-only API rate limit
+
+There are no runtime package dependencies.
+
+## Install from the v0.1.2 GitHub release
+
+Install the wheel attached to the v0.1.2 GitHub release:
+
+```bash
+python -m pip install https://github.com/LaimaWu/issue-boundary-evidence/releases/download/v0.1.2/issue_boundary_evidence-0.1.2-py3-none-any.whl
+```
+
+## PyPI installation pending
+
+PyPI publication is not live yet. After the first Trusted Publishing run succeeds, the package will be installable with:
+
+```bash
+python -m pip install issue-boundary-evidence
+```
+
+Until then, use the GitHub release wheel or the contributor installation below.
+
+## Contributor install
+
+From the repository root:
+
+```bash
+python3 -m venv .venv
+. .venv/bin/activate
+python -m pip install -e .
+```
+
+## Run
+
+Print a report:
+
+```bash
+issue-boundary-evidence https://github.com/OWNER/REPO/issues/123
+```
+
+Write it to a file:
+
+```bash
+issue-boundary-evidence https://github.com/OWNER/REPO/issues/123 --output report.md
+```
+
+Run without installing:
+
+```bash
+PYTHONPATH=src python -m issue_boundary_evidence.cli https://github.com/OWNER/REPO/issues/123
+```
+
+## Test
+
+```bash
+PYTHONPATH=src python -m unittest discover -s tests -v
+```
+
+The unit tests use local fixtures and do not require network access.
+
+## Examples
+
+Generated reports are in [`examples/`](examples/):
+
+- `pandas-58927.md`
+- `pytest-12430.md`
+- `numpy-26622.md`
+
+The complete frozen ten-issue precision-pass run is stored in [`eval_outputs/`](eval_outputs/). These are raw CLI reports for human retrospective scoring; the project does not assign its own GO/REVISE/STOP score.
+
+## Retrieval boundary
+
+The CLI uses only GitHub's public, read-only REST endpoints. It fetches all comments on the requested issue. It retrieves up to five same-repository issues or pull requests only when the issue or comments explicitly link them or use contextual wording such as `see #123`, `PR #123`, or `fixed by #123`. Bare numbers and references inside code fences are not retrieved. Contextual commit SHAs are linked without fetching their diffs. Non-GitHub service URLs can identify an infrastructure boundary, but the CLI records their domains without requesting them.
+
+Version-like values are extracted deterministically, then the report prioritizes versions tied to the current repository, complete Python/runtime tokens, boundary language, compatibility, regression, or release/fix prose. Markdown-linked patch versions are supported. This avoids presenting every compiler, package-name substring, or toolchain value in a large environment dump as equally important.
+
+Packaging tools such as `pip`, `setuptools`, and `wheel` are promoted only when their version or behavior directly affects the investigation—for example, selecting the correct ABI wheel. Generic install commands, CI logs, and package lists are not sufficient. Quoted copies of identical regression sentences are collapsed while retaining their source links.
+
+## Security
+
+All issue content is untrusted text. The tool never evaluates or executes issue bodies, comments, code blocks, commands, or reporter-provided scripts. HTTP methods are limited to `GET`; no GitHub write operations exist in the client.
+
+## Validation
+
+This is an experimental deterministic maintainer tool. The repository includes a frozen retrospective evaluation set built from historical pandas, pytest, and NumPy issues where maintainers later discussed dependency, runtime, upstream, infrastructure, or version-history boundaries. Raw generated reports are stored in [`eval_outputs/`](eval_outputs/). This evaluation is intended to expose strengths and failure modes; it is not a claim of universal accuracy.
+
+## Current status
+
+Experimental deterministic CLI. See [`EVAL_NOTES.md`](EVAL_NOTES.md) for the retrospective evaluation procedure.
+
+## License
+
+Apache-2.0.

issue_boundary_evidence-0.1.2/pyproject.toml

@@ -0,0 +1,23 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "issue-boundary-evidence"
+version = "0.1.2"
+description = "Read-only, deterministic boundary evidence extraction for public GitHub issues"
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+authors = [{ name = "Issue Boundary Evidence contributors" }]
+dependencies = []
+
+[project.urls]
+Repository = "https://github.com/LaimaWu/issue-boundary-evidence"
+Issues = "https://github.com/LaimaWu/issue-boundary-evidence/issues"
+
+[project.scripts]
+issue-boundary-evidence = "issue_boundary_evidence.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]

issue_boundary_evidence-0.1.2/setup.cfg

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

issue_boundary_evidence-0.1.2/src/issue_boundary_evidence/__init__.py

@@ -0,0 +1,4 @@
+"""Deterministic, read-only evidence extraction for public GitHub issues."""
+
+__version__ = "0.1.0"
+

issue_boundary_evidence-0.1.2/src/issue_boundary_evidence/cli.py

@@ -0,0 +1,47 @@
+from __future__ import annotations
+
+import argparse
+import sys
+from pathlib import Path
+
+from .github import GitHubError
+from .report import render_report
+from .retrieve import analyze_issue
+
+
+def build_parser() -> argparse.ArgumentParser:
+    parser = argparse.ArgumentParser(
+        prog="issue-boundary-evidence",
+        description="Produce a read-only Markdown boundary-evidence report for a public GitHub issue.",
+    )
+    parser.add_argument("issue_url", help="Public GitHub issue URL")
+    parser.add_argument("-o", "--output", type=Path, help="Write Markdown to this file instead of stdout")
+    parser.add_argument(
+        "--related-limit",
+        type=int,
+        default=5,
+        choices=range(0, 11),
+        metavar="0..10",
+        help="Maximum explicitly referenced same-repository issues/PRs to retrieve (default: 5)",
+    )
+    return parser
+
+
+def main(argv: list[str] | None = None) -> int:
+    args = build_parser().parse_args(argv)
+    try:
+        analysis = analyze_issue(args.issue_url, related_limit=args.related_limit)
+        report = render_report(analysis)
+    except (ValueError, GitHubError) as exc:
+        print(f"error: {exc}", file=sys.stderr)
+        return 2
+    if args.output:
+        args.output.write_text(report, encoding="utf-8")
+    else:
+        print(report)
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())
+