patchrail 0.1.1__tar.gz → 0.2.0__tar.gz

{patchrail-0.1.1 → patchrail-0.2.0}/.gitignore

@@ -1,4 +1,5 @@
 .venv/
+.DS_Store
 .pkg-smoke/
 .patchrail-release-smoke/
 __pycache__/

patchrail-0.2.0/CHANGELOG.md

@@ -0,0 +1,83 @@
+# Changelog
+
+## 0.2.0 - 2026-07-07
+
+### Removed
+
+- Removed the commercial `Guide:` link that `ci explain` appended to text and
+  Markdown reports, and the matching guide URL outputs from the GitHub Action.
+  Reports now end after the classification; per-class remediation write-ups
+  live in-repo under `docs/fix/`.
+- Removed commercial product links and campaign-tagged URLs from the README,
+  docs, and the PyPI project URL list.
+- Removed the distribution and web-metrics tooling (`ci share-links` and the
+  web metrics commands and store). PatchRail no longer ships link-tracking or
+  distribution helpers.
+
+### Changed
+
+- `funded-issues` is now explicitly labeled experimental. Discovery commands
+  default to safe-only filtering, and risky entries require an explicit
+  `--include-risky` flag.
+- Rewrote the README around the open-source CI triage workflow: quickstart
+  with real classifier output, honest feature table, local-first safety
+  section, and the fixture contribution path.
+
+### Added
+
+- Added `node_script_missing` CI classification so npm/pnpm/yarn jobs that
+  call a missing package script are separated from dependency-install failures
+  and routed to a workflow/script repair path.
+- Added a permanent source-level blocklist to the funded-issues tracker:
+  owners manually verified as fake-bounty sources are dropped at the
+  `merge_into_store` choke point (counted as `blocked` in the merge summary)
+  and `purge_blocklisted_entries` removes any legacy entries; `track` runs the
+  purge on every merge so existing stores self-heal.
+- Added `funded-issues import-algora-board`, an offline parser for a locally
+  saved Algora organization bounty-board page. It extracts the funder-stated
+  USD amount, GitHub issue reference, posting age, and declared claim count
+  per bounty, and can merge the scored records into a tracker store. No
+  network access is performed.
+- Added read-only competition and payout-vs-effort scoring signals plus the
+  `funded-issues competition` and `funded-issues payout-effort` batch
+  commands, all derived from public metadata observations with no claims,
+  comments, or maintainer contact.
+- Added an offline owner-level `source_noise` heuristic and
+  `funded-issues apply-recheck`, a local-file-only command that transitions
+  tracker entries to closed / stale / active from recheck observations.
+- Added .NET/NuGet/C# and xUnit fixture coverage for `dotnet restore`,
+  `dotnet build`, and `dotnet test` failure modes, growing the public CI
+  fixture zoo to 153 cases.
+
+## 0.1.1 - 2026-06-12
+
+- `ci explain` now ends text and Markdown reports with a `Guide:` link to the
+  matching getpatchrail.com `/fix` remediation page; unknown or unpublished
+  failure classes fall back to the `/fix` index without a network call.
+- Added `funded-issues fresh`, a local read-only radar over the tracker store
+  that surfaces recently posted or recently labeled funded issues for fast
+  solver-side triage.
+- Added `pre_commit_hook_failure` CI classification so pre-commit hook output is
+  recognized directly while the CLI still avoids linking to a missing `/fix`
+  page until that guide exists.
+
+## 0.1.0 - 2026-06-02
+
+- Initial public CI Janitor snapshot.
+- Added `patchrail ci explain` and `patchrail ci classify`.
+- Added local Markdown, JSON, and text reports.
+- Added Apache-2.0 license and safety/ethics documentation.
+- Added fixture-backed tests, local benchmark command, and GitHub Actions CI.
+- Expanded the initial CI fixture zoo to 101 sanitized synthetic examples across
+  Python, Node, TypeScript, Go, Rust, and GitHub Actions failure modes.
+- Added a read-only GitHub Actions triage artifact workflow.
+- Added the experimental local Agent Control Plane queue with SQLite-backed
+  work items, approval states, audit export, CI result import, and proposal
+  records.
+- Added the experimental read-only `funded-issues` CLI over local metadata,
+  with safe-only filtering and explicit anti-abuse blocked actions.
+- Added permission-only adopter reporting and a public metrics tracker for
+  pilot outcomes, adoption signals, and open-source program evidence gaps.
+- Added release-prep evidence docs, package smoke checks, and manual publish
+  gates. Release tags, PyPI publishing, GitHub Releases, and public
+  announcements remain maintainer actions.

patchrail-0.2.0/PKG-INFO

@@ -0,0 +1,214 @@
+Metadata-Version: 2.4
+Name: patchrail
+Version: 0.2.0
+Summary: Local-first maintainer automation for open-source CI triage
+Project-URL: Homepage, https://github.com/patchrail/patchrail
+Project-URL: Documentation, https://github.com/patchrail/patchrail/tree/main/docs
+Project-URL: Changelog, https://github.com/patchrail/patchrail/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/patchrail/patchrail/issues
+Project-URL: GitHub Action, https://github.com/patchrail/ci-triage-action
+Author: Pablo Guillén
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ci,github-actions,maintenance,open-source,triage
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Provides-Extra: dev
+Requires-Dist: build>=1.2; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Requires-Dist: twine>=5.1; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# PatchRail
+
+Local-first CI failure triage for open-source maintainers. Paste a failing CI
+log, get the failure class, the reproduction command, and a suggested fix
+strategy — in seconds, fully offline.
+
+[![PyPI](https://img.shields.io/pypi/v/patchrail)](https://pypi.org/project/patchrail/)
+[![CI](https://github.com/patchrail/patchrail/actions/workflows/ci.yml/badge.svg)](https://github.com/patchrail/patchrail/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+[![Python](https://img.shields.io/pypi/pyversions/patchrail)](https://pypi.org/project/patchrail/)
+
+![patchrail ci explain reading a failed CI log and emitting root cause, confidence, and a reproduce command](docs/assets/ci-explain-demo.gif)
+
+The recording above is real output from the bundled
+`examples/ci-triage/typescript-import-type-drift.log` fixture. No model calls,
+no network, no telemetry: the classifier is a curated rule engine that runs
+entirely on your machine.
+
+## Why maintainers use it
+
+- **33 failure classes** backed by real log signatures — dependency
+  resolution, flaky network, OOM-killed runners, Docker builds, lint,
+  type checks, and test failures across Python, Node, TypeScript, Go, Rust,
+  Java, .NET, Ruby, PHP, and C++.
+- **153 sanitized CI log fixtures** keep the classifier honest: every rule is
+  benchmarked against the public fixture zoo in `examples/ci-triage/` on every
+  test run.
+- **23 secret-redaction patterns** (GitHub/GitLab/npm/PyPI/AWS tokens, private
+  keys, JWTs, emails, home paths) so logs can be shared safely.
+- **Local-first by design**: no network access, no billing, no external model,
+  no telemetry. Nothing leaves the machine.
+- **Markdown for humans, JSON for automation** — pipe the same result into a
+  PR comment or a workflow step.
+
+## Quickstart
+
+PatchRail is published on PyPI:
+
+```bash
+pipx install patchrail
+```
+
+Classify any failed CI log:
+
+```bash
+patchrail ci explain --log failed-ci.log
+```
+
+Or try it on a bundled fixture from a clone of this repo:
+
+```bash
+git clone https://github.com/patchrail/patchrail
+cd patchrail
+patchrail ci explain --log examples/ci-triage/dependency-failure.log --format markdown
+```
+
+Real output:
+
+```markdown
+# PatchRail CI Report
+
+- Root cause: `python_dependency_resolution`
+- Confidence: `0.95`
+- Subsystem: Python dependency installation
+- Reproduce: `python -m pip install -r requirements.txt`
+- Suggested action: Pin or relax the conflicting dependency range, then rerun the same install command and the affected tests.
+
+## Evidence signals
+
+- `Could not find a version that satisfies the requirement`
+- `ResolutionImpossible`
+- `python -m pip install`
+```
+
+It also reads from stdin, so you can pipe a log straight in:
+
+```bash
+tail -n 200 failed-ci.log | patchrail ci explain
+```
+
+Every failure class has a step-by-step remediation write-up in
+[docs/fix/](docs/fix/README.md).
+
+## GitHub Action
+
+Run the same triage on every red CI run with
+[`patchrail/ci-triage-action`](https://github.com/patchrail/ci-triage-action)
+(also on the
+[GitHub Marketplace](https://github.com/marketplace/actions/patchrail-ci-triage)).
+It classifies the log locally on the runner — no PR, no comment, nothing
+leaves the job:
+
+```yaml
+- name: PatchRail CI triage
+  if: failure()
+  uses: patchrail/ci-triage-action@v1
+  with:
+    log-path: test.log
+```
+
+See [examples/ci-triage-action](examples/ci-triage-action/README.md) for the
+report artifact shape.
+
+## Features
+
+| Feature | Status | Notes |
+| --- | --- | --- |
+| CI failure triage (`ci explain`, `ci classify`) | Beta | 33 failure classes for GitHub Actions-style logs and common toolchains |
+| Secret redaction (`redact`, `ci explain --redact`) | Beta | 23 patterns for tokens, keys, emails, and home paths |
+| Reports | Beta | Markdown, JSON, and plain text |
+| Fixture benchmark (`ci benchmark`) | Beta | Scores the classifier against all 153 public fixtures |
+| GitHub Action | Beta | Read-only triage artifact on failed workflows |
+| Local queue / control plane (`queue`) | Experimental | SQLite-backed work items with human approval states |
+| Funded issue discovery (`funded-issues`) | Experimental (read-only) | Safe-only defaults, no claiming or commenting; see [docs/funded-issues-ethics.md](docs/funded-issues-ethics.md) |
+
+## Local-first & safety
+
+PatchRail never phones home. The classifier needs no API key, no GitHub App,
+no repo write permission, and no external model call. Write actions (PRs,
+comments, claims) are out of scope; anything that could become one sits behind
+an explicit human approval state.
+
+Secret redaction is a first-class feature, not an afterthought. Redact a log
+before sharing it anywhere:
+
+```bash
+patchrail redact --log failed.log > failed.redacted.log
+patchrail ci explain --redact --log failed.log
+```
+
+The redaction pass covers GitHub, GitLab, npm, PyPI, AWS, Stripe, Slack,
+Google, Hugging Face, and SendGrid credentials, private key blocks, JWTs,
+bearer tokens, URL-embedded credentials, `*_TOKEN`/`*_SECRET` environment
+assignments, email addresses, and user home paths.
+
+See [ETHICS.md](ETHICS.md), [SECURITY.md](SECURITY.md), and
+[docs/threat-model.md](docs/threat-model.md).
+
+## Roadmap
+
+- **v0.3** — public demo of the local agent control plane: SQLite-backed work
+  queue, approval gates, and audit export.
+- **v0.4** — ethical funded-maintenance workflow: read-only discovery with
+  human-gated follow-up, no automated claiming.
+
+Details in [docs/roadmap.md](docs/roadmap.md).
+
+## Documentation
+
+- [Quickstart](docs/quickstart.md)
+- [Fix guides per failure class](docs/fix/README.md)
+- [CI Failure Zoo](docs/ci-failure-zoo.md)
+- [GitHub Actions CI triage](docs/github-action.md)
+- [Agent Control Plane](docs/agent-control-plane.md)
+- [API reference](docs/api-reference.md)
+- [Threat model](docs/threat-model.md)
+- [Funded issue ethics](docs/funded-issues-ethics.md)
+
+## Contributing
+
+The fastest way in is **adding a CI fixture — it takes about 10 minutes**:
+grab a failed log, redact it, trim it to the smallest excerpt that still shows
+the root cause, and add it with its expected classification under
+`examples/ci-triage/`. The full path is in
+[CONTRIBUTING.md](CONTRIBUTING.md), and the
+[CI failure fixture issue template](.github/ISSUE_TEMPLATE/ci_failure_fixture.md)
+works if you are not ready to open a pull request.
+
+Issues labeled
+[`good first issue`](https://github.com/patchrail/patchrail/labels/good%20first%20issue)
+are scoped for first-time contributors.
+
+Run the checks locally before opening a PR:
+
+```bash
+uv run --extra dev pytest -q
+uv run --extra dev ruff check .
+uv run --extra dev patchrail ci benchmark examples/ci-triage --format json
+```
+
+## License
+
+Apache-2.0.

patchrail-0.2.0/README.md

@@ -0,0 +1,183 @@
+# PatchRail
+
+Local-first CI failure triage for open-source maintainers. Paste a failing CI
+log, get the failure class, the reproduction command, and a suggested fix
+strategy — in seconds, fully offline.
+
+[![PyPI](https://img.shields.io/pypi/v/patchrail)](https://pypi.org/project/patchrail/)
+[![CI](https://github.com/patchrail/patchrail/actions/workflows/ci.yml/badge.svg)](https://github.com/patchrail/patchrail/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+[![Python](https://img.shields.io/pypi/pyversions/patchrail)](https://pypi.org/project/patchrail/)
+
+![patchrail ci explain reading a failed CI log and emitting root cause, confidence, and a reproduce command](docs/assets/ci-explain-demo.gif)
+
+The recording above is real output from the bundled
+`examples/ci-triage/typescript-import-type-drift.log` fixture. No model calls,
+no network, no telemetry: the classifier is a curated rule engine that runs
+entirely on your machine.
+
+## Why maintainers use it
+
+- **33 failure classes** backed by real log signatures — dependency
+  resolution, flaky network, OOM-killed runners, Docker builds, lint,
+  type checks, and test failures across Python, Node, TypeScript, Go, Rust,
+  Java, .NET, Ruby, PHP, and C++.
+- **153 sanitized CI log fixtures** keep the classifier honest: every rule is
+  benchmarked against the public fixture zoo in `examples/ci-triage/` on every
+  test run.
+- **23 secret-redaction patterns** (GitHub/GitLab/npm/PyPI/AWS tokens, private
+  keys, JWTs, emails, home paths) so logs can be shared safely.
+- **Local-first by design**: no network access, no billing, no external model,
+  no telemetry. Nothing leaves the machine.
+- **Markdown for humans, JSON for automation** — pipe the same result into a
+  PR comment or a workflow step.
+
+## Quickstart
+
+PatchRail is published on PyPI:
+
+```bash
+pipx install patchrail
+```
+
+Classify any failed CI log:
+
+```bash
+patchrail ci explain --log failed-ci.log
+```
+
+Or try it on a bundled fixture from a clone of this repo:
+
+```bash
+git clone https://github.com/patchrail/patchrail
+cd patchrail
+patchrail ci explain --log examples/ci-triage/dependency-failure.log --format markdown
+```
+
+Real output:
+
+```markdown
+# PatchRail CI Report
+
+- Root cause: `python_dependency_resolution`
+- Confidence: `0.95`
+- Subsystem: Python dependency installation
+- Reproduce: `python -m pip install -r requirements.txt`
+- Suggested action: Pin or relax the conflicting dependency range, then rerun the same install command and the affected tests.
+
+## Evidence signals
+
+- `Could not find a version that satisfies the requirement`
+- `ResolutionImpossible`
+- `python -m pip install`
+```
+
+It also reads from stdin, so you can pipe a log straight in:
+
+```bash
+tail -n 200 failed-ci.log | patchrail ci explain
+```
+
+Every failure class has a step-by-step remediation write-up in
+[docs/fix/](docs/fix/README.md).
+
+## GitHub Action
+
+Run the same triage on every red CI run with
+[`patchrail/ci-triage-action`](https://github.com/patchrail/ci-triage-action)
+(also on the
+[GitHub Marketplace](https://github.com/marketplace/actions/patchrail-ci-triage)).
+It classifies the log locally on the runner — no PR, no comment, nothing
+leaves the job:
+
+```yaml
+- name: PatchRail CI triage
+  if: failure()
+  uses: patchrail/ci-triage-action@v1
+  with:
+    log-path: test.log
+```
+
+See [examples/ci-triage-action](examples/ci-triage-action/README.md) for the
+report artifact shape.
+
+## Features
+
+| Feature | Status | Notes |
+| --- | --- | --- |
+| CI failure triage (`ci explain`, `ci classify`) | Beta | 33 failure classes for GitHub Actions-style logs and common toolchains |
+| Secret redaction (`redact`, `ci explain --redact`) | Beta | 23 patterns for tokens, keys, emails, and home paths |
+| Reports | Beta | Markdown, JSON, and plain text |
+| Fixture benchmark (`ci benchmark`) | Beta | Scores the classifier against all 153 public fixtures |
+| GitHub Action | Beta | Read-only triage artifact on failed workflows |
+| Local queue / control plane (`queue`) | Experimental | SQLite-backed work items with human approval states |
+| Funded issue discovery (`funded-issues`) | Experimental (read-only) | Safe-only defaults, no claiming or commenting; see [docs/funded-issues-ethics.md](docs/funded-issues-ethics.md) |
+
+## Local-first & safety
+
+PatchRail never phones home. The classifier needs no API key, no GitHub App,
+no repo write permission, and no external model call. Write actions (PRs,
+comments, claims) are out of scope; anything that could become one sits behind
+an explicit human approval state.
+
+Secret redaction is a first-class feature, not an afterthought. Redact a log
+before sharing it anywhere:
+
+```bash
+patchrail redact --log failed.log > failed.redacted.log
+patchrail ci explain --redact --log failed.log
+```
+
+The redaction pass covers GitHub, GitLab, npm, PyPI, AWS, Stripe, Slack,
+Google, Hugging Face, and SendGrid credentials, private key blocks, JWTs,
+bearer tokens, URL-embedded credentials, `*_TOKEN`/`*_SECRET` environment
+assignments, email addresses, and user home paths.
+
+See [ETHICS.md](ETHICS.md), [SECURITY.md](SECURITY.md), and
+[docs/threat-model.md](docs/threat-model.md).
+
+## Roadmap
+
+- **v0.3** — public demo of the local agent control plane: SQLite-backed work
+  queue, approval gates, and audit export.
+- **v0.4** — ethical funded-maintenance workflow: read-only discovery with
+  human-gated follow-up, no automated claiming.
+
+Details in [docs/roadmap.md](docs/roadmap.md).
+
+## Documentation
+
+- [Quickstart](docs/quickstart.md)
+- [Fix guides per failure class](docs/fix/README.md)
+- [CI Failure Zoo](docs/ci-failure-zoo.md)
+- [GitHub Actions CI triage](docs/github-action.md)
+- [Agent Control Plane](docs/agent-control-plane.md)
+- [API reference](docs/api-reference.md)
+- [Threat model](docs/threat-model.md)
+- [Funded issue ethics](docs/funded-issues-ethics.md)
+
+## Contributing
+
+The fastest way in is **adding a CI fixture — it takes about 10 minutes**:
+grab a failed log, redact it, trim it to the smallest excerpt that still shows
+the root cause, and add it with its expected classification under
+`examples/ci-triage/`. The full path is in
+[CONTRIBUTING.md](CONTRIBUTING.md), and the
+[CI failure fixture issue template](.github/ISSUE_TEMPLATE/ci_failure_fixture.md)
+works if you are not ready to open a pull request.
+
+Issues labeled
+[`good first issue`](https://github.com/patchrail/patchrail/labels/good%20first%20issue)
+are scoped for first-time contributors.
+
+Run the checks locally before opening a PR:
+
+```bash
+uv run --extra dev pytest -q
+uv run --extra dev ruff check .
+uv run --extra dev patchrail ci benchmark examples/ci-triage --format json
+```
+
+## License
+
+Apache-2.0.

patchrail-0.2.0/actions/ci-triage/action.yml

@@ -0,0 +1,105 @@
+name: PatchRail CI Triage
+description: Classify a CI log locally and expose PatchRail triage outputs.
+
+inputs:
+  log-path:
+    description: Path to the failed CI log inside the checked-out repository.
+    required: true
+  report-dir:
+    description: Directory where PatchRail writes the markdown and JSON reports.
+    required: false
+    default: patchrail-ci-triage
+  redact:
+    description: Redact secrets, emails, and local home paths before writing reports.
+    required: false
+    default: "true"
+
+outputs:
+  failure-class:
+    description: PatchRail failure class for the CI log.
+    value: ${{ steps.outputs.outputs.failure-class }}
+  failure-slug:
+    description: URL-safe PatchRail failure class slug for labels and artifacts.
+    value: ${{ steps.outputs.outputs.failure-slug }}
+  confidence:
+    description: PatchRail classifier confidence.
+    value: ${{ steps.outputs.outputs.confidence }}
+  json-result:
+    description: Path to the structured PatchRail result JSON.
+    value: ${{ steps.outputs.outputs.json-result }}
+  artifact-name:
+    description: Stable artifact name for uploading the PatchRail triage bundle.
+    value: ${{ steps.outputs.outputs.artifact-name }}
+  markdown-report:
+    description: Path to the maintainer-readable PatchRail report.
+    value: ${{ steps.outputs.outputs.markdown-report }}
+  summary-line:
+    description: One-line PatchRail triage summary for GitHub step summaries.
+    value: ${{ steps.outputs.outputs.summary-line }}
+  redacted-categories:
+    description: Number of local redaction categories found in the CI log.
+    value: ${{ steps.outputs.outputs.redacted-categories }}
+  adoption-key:
+    description: Stable PatchRail adoption evidence key for downstream dashboards.
+    value: ${{ steps.outputs.outputs.adoption-key }}
+  adoption-event-id:
+    description: Stable event id for deduplicating PatchRail workflow evidence.
+    value: ${{ steps.outputs.outputs.adoption-event-id }}
+  adoption-event-json:
+    description: Single-line PatchRail adoption event JSON for workflow evidence ledgers.
+    value: ${{ steps.outputs.outputs.adoption-event-json }}
+  workflow-repository:
+    description: Repository where the PatchRail triage action ran, when available.
+    value: ${{ steps.outputs.outputs.workflow-repository }}
+  workflow-run-url:
+    description: GitHub Actions run URL for the triage execution, when available.
+    value: ${{ steps.outputs.outputs.workflow-run-url }}
+  workflow-run-host:
+    description: Host that executed the triage workflow, for github.com/GHES attribution.
+    value: ${{ steps.outputs.outputs.workflow-run-host }}
+  next-step:
+    description: Minimal next repair step for the detected CI failure.
+    value: ${{ steps.outputs.outputs.next-step }}
+  reproduction-command:
+    description: Local command PatchRail recommends to reproduce the detected failure.
+    value: ${{ steps.outputs.outputs.reproduction-command }}
+
+runs:
+  using: composite
+  steps:
+    - name: Install PatchRail
+      shell: bash
+      run: |
+        set -euo pipefail
+        python -m pip install "$GITHUB_ACTION_PATH/../.."
+
+    - name: Generate PatchRail reports
+      shell: bash
+      run: |
+        set -euo pipefail
+        log_path="${{ inputs.log-path }}"
+        report_dir="${{ inputs.report-dir }}"
+        redact_arg=""
+        if [ "${{ inputs.redact }}" = "true" ]; then
+          redact_arg="--redact"
+        fi
+
+        test -f "$log_path"
+        mkdir -p "$report_dir"
+        patchrail ci classify $redact_arg --log "$log_path" --format json --out "$report_dir/ci-result.json"
+        patchrail ci explain $redact_arg --log "$log_path" --format markdown --out "$report_dir/ci-report.md"
+
+    - name: Export action outputs
+      id: outputs
+      shell: bash
+      run: |
+        set -euo pipefail
+        summary_arg=()
+        if [ -n "${GITHUB_STEP_SUMMARY:-}" ]; then
+          summary_arg=(--summary "$GITHUB_STEP_SUMMARY")
+        fi
+        python "$GITHUB_ACTION_PATH/scripts/ci_triage_action_outputs.py" \
+          --result "${{ inputs.report-dir }}/ci-result.json" \
+          --report "${{ inputs.report-dir }}/ci-report.md" \
+          --output "$GITHUB_OUTPUT" \
+          "${summary_arg[@]}"