Skip to content

ci(release): fail closed on missing license evidence - #240

Closed
seonghobae wants to merge 21 commits into
mainfrom
chore/release-legal-readiness-20260817
Closed

ci(release): fail closed on missing license evidence#240
seonghobae wants to merge 21 commits into
mainfrom
chore/release-legal-readiness-20260817

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Why

Protected main currently has no LICENSE/COPYING file, GitHub reports no detected repository license, and Cargo.toml declares neither license nor license-file. That is an acquisition/release-readiness gap, but this PR must not invent legal terms or claim rights that have not been established.

What

  • Add a deterministic source-distribution legal-readiness checker.
  • Require explicit repository license-file evidence plus Cargo package license metadata before the presence gate reports ready.
  • Reject missing or path-escaping license-file declarations.
  • Emit machine-readable blockers and explicit limitations: this does not select or interpret a license, prove copyright ownership, establish instrument rights, or establish legal sufficiency.
  • Add isolated unit fixtures for fail-closed missing/malformed/path-escape cases and valid explicit-evidence cases.
  • Add a manual, read-only workflow_dispatch preflight. It intentionally fails on the current repository until an authorized owner adds reviewed terms; it does not make every ordinary PR fail while that governance decision is pending.

TDD

  • RED contract: c31a2b454d121d3e187e8955fe6b1eb05d65294c
  • Checker implementation: 4e8878fc8b1bf5acb9283fc4c970862b4df687b5
  • Unit evidence: f2d33cae7cb54e07743d3bbadf6f054f05115cf6
  • GREEN workflow: 10973662ce969303a4b3dc8cee47cc86461bc316

Scope

This PR adds evidence/preflight only. It does not choose a license, change publish = false, publish a crate, certify third-party compatibility, or assert rights to assessment content. Those remain explicit owner/legal-governance inputs.

Do not merge until required checks on the unchanged exact head and qualifying independent non-author review pass.


Open in Devin Review

@cursor

cursor Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 46756092-3bbc-49ac-b973-2e0eadb91d84

📥 Commits

Reviewing files that changed from the base of the PR and between 5544149 and e7d2855.

📒 Files selected for processing (7)
  • .github/workflows/ci.yml
  • .github/workflows/release-legal-readiness.yml
  • scripts/check_release_legal_readiness.py
  • src/session_http.rs
  • tests/session_http_framing.rs
  • tests/test_check_release_legal_readiness.py
  • tests/test_release_legal_readiness.py
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-legal-readiness-20260817

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@seonghobae

Copy link
Copy Markdown
Contributor Author

Hourly loop: exact head 220c6fe3 now includes the refs/heads/main preflight guard. Isolated legal-readiness unittests are GREEN locally (python3 -m unittest tests.test_release_legal_readiness tests.test_check_release_legal_readiness). Repo Runtime CI was rerun on this unchanged SHA after org-queue cancellation. Independent last-push review is still required; this comment is not approval.

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown
⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@seonghobae

Copy link
Copy Markdown
Contributor Author

Live re-verify (2026-08-17)

Exact head c3a34611 is still MERGEABLE against protected main aac99d0b. Required checks on this unchanged head are SUCCESS (Runtime CI, line/branch coverage, rustdoc, security/SAST, SBOM, provenance, noema-review, opencode-review).

Merge is blocked only by the live ruleset: reviewDecision=REVIEW_REQUIRED and there is no qualifying independent non-author last-push approval. I am the PR author (seonghobae) and will not self-approve or use admin bypass.

Requested Copilot review on this exact head. This comment is not approval. Independent last-push review is still required before merge.

@cursor

cursor Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

@coderabbitai review

1 similar comment
@seonghobae

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown
⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@cursor
cursor Bot force-pushed the chore/release-legal-readiness-20260817 branch from 4529c6b to a9f69d8 Compare August 18, 2026 00:07
@cursor
cursor Bot force-pushed the chore/release-legal-readiness-20260817 branch from a9f69d8 to 73e45e6 Compare August 18, 2026 00:26
cursoragent and others added 2 commits August 18, 2026 00:36
…ader

Production line coverage failed because the integration framing client
unwrapped write/shutdown after the listener already fail-closed. Drive
those reader arms through the race-safe helper and tolerate a closed
peer during the public framing contract.

Co-authored-by: Seongho Bae <seonghobae@users.noreply.github.com>

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 0f075706909c3dc36430fd05dddd5dffb4fa2971.

  • Head SHA: 0f075706909c3dc36430fd05dddd5dffb4fa2971

  • Workflow run: 32100400739

  • Workflow attempt: 1

Coverage evidence

Coverage Decision

  • Result: FAIL
  • Test evidence: not proven passing
  • Docstring evidence: not proven passing when configured
  • Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow (2 files)"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (2 files)"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file (2 files)"]
  R2 --> V2["required checks"]
  Evidence --> S3["Test (3 files)"]
  S3 --> I3["regression suite"]
  I3 --> R3["Review risk: Test (3 files)"]
  R3 --> V3["targeted test run"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 0f075706909c3dc36430fd05dddd5dffb4fa2971
  • Workflow run: 32100400739
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 0f075706909c3dc36430fd05dddd5dffb4fa2971.

  • Head SHA: 0f075706909c3dc36430fd05dddd5dffb4fa2971

  • Workflow run: 32100400739

  • Workflow attempt: 1

Coverage evidence

Coverage Decision

  • Result: FAIL
  • Test evidence: not proven passing
  • Docstring evidence: not proven passing when configured
  • Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow (2 files)"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (2 files)"]
  S2 --> I2["repository behavior"]
  I2 --> R2["Review risk: Changed file (2 files)"]
  R2 --> V2["required checks"]
  Evidence --> S3["Test (3 files)"]
  S3 --> I3["regression suite"]
  I3 --> R3["Review risk: Test (3 files)"]
  R3 --> V3["targeted test run"]
Loading

Copy link
Copy Markdown
Contributor Author

@opencode-agent review exact current head 0f075706909c3dc36430fd05dddd5dffb4fa2971. The repository-owned Runtime CI/security/SAST/SBOM/provenance runs on this exact head are green; re-evaluate with the current central review tooling rather than transferring the historical coverage-evidence failure. Preserve the legal-governance boundary: this PR checks explicit evidence presence only and must not invent license terms.

@seonghobae

Copy link
Copy Markdown
Contributor Author

Audited exact head 0f07570: Strix is the only failed check. The check-run annotation contains only Process completed with exit code 1; its output, annotations, and downloadable logs expose no finding or root cause, while Runtime CI/security/SAST/SBOM/provenance are successful. No code change or unchanged-head rerun is justified until actionable Strix evidence appears; the PR remains blocked.

@seonghobae

Copy link
Copy Markdown
Contributor Author

@opencode-agent Please review only the current exact head 0f07570 against protected main 5544149. Current Runtime CI, coverage, SBOM, provenance, SAST, dependency, and coverage-evidence checks pass; the historical Strix check is an unavailable required-workflow run with no actionable output. Do not transfer the superseded coverage-evidence REQUEST_CHANGES to this head; report any current actionable finding against this exact SHA.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants