fix(naming): make runner-assignment evidence semantic - #533
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughGitHub REST 실행·작업 필드를 의미론적 evidence 필드로 변환합니다. 평가기와 CLI 보고서 계약을 Changes러너 할당 evidence 명명 변경
라이선싱 및 권리 증거
제품 문서 및 저장소 안내
Estimated code review effort: 4 (Complex) | ~45 minutes Merge Risk: 🔵 Low · up to The change leaves the repository documenting a GET/HEAD /ready endpoint that returns 404, so operators or integrations using the documented readiness check may receive an incorrect result. The PR is otherwise mergeable with explicit owner awareness and follow-up to align the documentation and runtime behavior. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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. Comment |
Scope
Translate GitHub-owned workflow-run/job REST fields at the read-only adapter boundary into Noema-owned semantic runner-assignment evidence while preserving current-attempt identity, bounded delegated GitHub capability use, stable schema-version-one operator output and acquisition package-byte rights evidence. Central runner capacity, provider routing, quarantine/security verdicts and outbound policy remain outside this PR.
Retained repair lineage
The branch retains the semantic
audit_status/ assignment-check evaluation internally while adapting it back to the established schema-v1 operator report at publication. Earlier review findings around stale nested report fields, missing changelog evidence and acquisition package-metadata integrity were repaired and all corresponding inline threads are resolved. The/readyfinding was reverified as an invalid entrypoint assumption:wrangler.tomlusessrc/runtime-entrypoint.ts, whose GET/HEAD readiness contract is covered by tests.After #546 and #544 reached protected truth, the branch was ordinarily/non-force converged onto
main@71cd0fb6f3cf6ed1b886c8c312bfe96e7613f155. Current exact head is8ced86c7636e3e5d09757459150df53e5329541e; compare is 72 ahead / 0 behind with merge-base exactly the protected head.Exact-head release evidence — 2026-09-06 KST
On unchanged
8ced86c7636e3e5d09757459150df53e5329541e:34006933314— completed / success;34006933327— completed / success under the protected post-fix(reviewer): fail closed on empty CodeGraph semantics #546 reviewer contract;34006933311— completed / success;34006933451— completed / success;No predecessor evidence is substituted. This PR is eligible for normal protected-main promotion at this exact head. Do not self-approve, force-push/destructively rebase, weaken gates or duplicate central/provider/security authority.