docs(copy): speak customer actions instead of internals - #123
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (16)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough패킷 검증 지침, HRIS 충돌 안내, People API 오류 응답, 후보자-근로자 전환 문서의 표현을 갱신했습니다. 관련 테스트 기대값과 manifest의 문서 다이제스트도 업데이트했습니다. Changes기록 무결성 안내
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The PR updates customer-facing wording and related assertions while preserving the stated behavior, with all reported checks passing; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 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 |
|
@opencode-agent review Please produce a formal |
|
Lifecycle/mergeability correction: current protected |
Current authority — 2026-09-06
Current exact head is
740cbec81ab43464cc4ae9c7a6f34b523426f9c1. This PR still carries old base snapshotdevelop@9e3e4847510e1e612b48474ba42b177b8ed824df; live protected truth isdevelop@eb9757f8649aaad026a9865508d9aad50c1a7a4f. GitHub currently reports the PR open · Draft · non-mergeable. Earlier wording that called it non-draft and mechanically mergeable was stale and is removed here.The product-copy delta remains valid: customer guidance replaces internal storage/implementation jargon with concrete next actions across candidate-evidence, offer-approval, requisition-review, HRIS-kernel correction/assignment/workforce/organization/resolution messages, People API hire/worker-conflict errors, and the storyboard. Trust semantics remain unchanged: authoritative re-resolution precedes consequential use, human-only approval remains mandatory where the owning flow requires it, and fail-closed behavior is preserved. Published route placeholders, Keyverse, and external-owner adapter names remain where they are real contract truth rather than implementation leakage.
Protected governance correction
The prior body also recorded a
required_approving_review_count = 0target. That is not the live protected rule. Organization ruleset18156473is active on the default branch and currently requires 1 approving review, dismisses stale reviews after a push, requires review-thread resolution, requires extra approval for unattributed changes, permits merge/squash only, and requires the seven central OpenCode / PR scheduler / Security / Strix / SAST / Noema / CodeQL workflows. The exposed OrganizationAdmin bypass is not an ordinary merge path and must not be used to make this lane pass.Historical exact-head evidence
The old-base exact head previously had successful repository-owned evidence but terminal non-passing review evidence, including OpenCode run
33209166811/ job98978056409and Strix run33209166866/ job98980447535. Existing thread closure or historical checks do not transfer across a protected-parent reconciliation, and no qualifying approval may be inferred from COMMENTED reviews.Required repair path
Preserve the customer-action copy delta and its tests, semantically adopt current protected
developwithout force/destructive rebase, preserve #161 canonical workflow ownership, resolve any overlapping source/provenance changes rather than choosing an old tree wholesale, and reseal deterministic artifacts from final bytes where required. Only the reconciled successor may obtain fresh exact-head Foundation/security/review evidence and the live ruleset's qualifying approval.Do not self-approve, use routine administrator bypass, manufacture reviewer identity, transfer predecessor GREEN, weaken or simulate a required workflow, force-push, or simply Close the valid copy delta.