Skip to content

fix(operations): restack scheduler activation evidence after release integration - #244

Merged
seonghobae merged 1 commit into
mainfrom
fix/hourly-scheduler-activation-post-release-v4
Aug 13, 2026
Merged

fix(operations): restack scheduler activation evidence after release integration#244
seonghobae merged 1 commit into
mainfrom
fix/hourly-scheduler-activation-post-release-v4

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Purpose

Clean protected-main successor for stale-base PR #243 after release-evidence integration advanced protected main. This branch starts directly from protected main f272107443389efe5982e18e84a5719a3ed10c05 and reapplies only the five exact scheduler-activation blobs already isolated on #243, without force-push, destructive rebase, stale changelog replay, or predecessor evidence transfer.

Exact source / scope

  • live protected base at construction and PR creation: f272107443389efe5982e18e84a5719a3ed10c05;
  • current exact head: 61e6d8805d9f54b350ccce59f811e0362cd77865;
  • source predecessor: PR fix(operations): restack scheduler activation evidence on latest main #243 exact head 0472aa7c9acbfe233d093b733a28a615a1da9e87;
  • exact preserved blobs:
    • .github/workflows/hourly-commercial-readiness.yml 294debefc27b123dd29156eb703d38cf7d5e76c6;
    • docs/doctoring/hourly-scheduler-activation-feasibility.md f6ac1636309f85925e5c5dd632176f91a241274b;
    • docs/hourly-commercial-readiness-loop.md b0301aa54d8b59d414864af1aaf2a2e2799f7e0b;
    • test/hourly-commercial-readiness-activation.test.ts 4acc8ed9e3458332a20b627c9690ce39b3f525e6;
    • test/workflow-readiness.test.ts 5202f2af4696d900752f03117d9fc9f93454350c;
  • every other path, including the newly protected release-evidence authority work, is inherited byte-for-byte from current protected main.

Operational boundary

The always-running activation preflight remains read-only and emits bounded outcome classes. Credential-bearing Maintainer App work remains separately gated. NO_ACTION_NEEDED remains diagnostic evidence only and cannot satisfy review, merge, release, deployment, licensing/IP, KPI, production, or acquisition authority.

Evidence boundary

No CI, reviewer, scanner, model, review, scheduler, or production evidence transfers from #222, #239, or #243. This exact head must obtain fresh application CI, reviewer CI, and protected-base-eligible central Security Scan evidence against unchanged head and current protected main. Pending, skipped, absent, stale, predecessor, status-only, model-only, cancelled, failed, or rate-limited evidence is non-passing.

Immediately before merge, re-resolve live main/head, re-read live rulesets and central .github Security Scan authority, verify exact checkout SHAs, require every applicable gate to be terminal-success and require zero valid unresolved findings. No independent-approval requirement is invented unless live policy actually requires one.

Supersedes #243 only after this successor has fresh exact-head proof and protected integration.

Summary by CodeRabbit

  • 새로운 기능

    • 시간별 상업적 준비 상태 점검에 읽기 전용 사전 검증 단계를 추가했습니다.
    • 준비 조건을 충족할 때만 변경 작업이 실행되도록 개선했습니다.
    • 검증 결과와 최소화된 증거 자료를 요약 및 아티팩트로 제공합니다.
  • 문서

    • 활성화 조건, 보안 제약, 결과 분류 및 운영 점검 절차를 문서화했습니다.
  • 테스트

    • 사전 검증, 조건부 실행, 증거 생성 및 민감 정보 비공개 동작을 검증하는 테스트를 추가했습니다.

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6240863f-8f07-4d2f-a8cd-cd60464a9596

📥 Commits

Reviewing files that changed from the base of the PR and between f272107 and 61e6d88.

📒 Files selected for processing (5)
  • .github/workflows/hourly-commercial-readiness.yml
  • docs/doctoring/hourly-scheduler-activation-feasibility.md
  • docs/hourly-commercial-readiness-loop.md
  • test/hourly-commercial-readiness-activation.test.ts
  • test/workflow-readiness.test.ts

📝 Walkthrough

Walkthrough

시간별 상용 readiness 워크플로에 읽기 전용 activation_preflight 작업을 추가했습니다. 사전 점검은 활성화 조건과 구성을 평가하고 증거를 생성합니다. maintain 작업은 write_ready == 'true'일 때만 실행됩니다. 관련 문서와 테스트도 갱신했습니다.

Changes

활성화 사전 점검

Layer / File(s) Summary
활성화 계약과 보안 경계
docs/doctoring/hourly-scheduler-activation-feasibility.md
활성화 RCA, 평가 기준, terminal classification, 공개 증거 최소화 규칙과 GitHub 동작 근거를 정의했습니다.
사전 점검 구현과 쓰기 레인 게이트
.github/workflows/hourly-commercial-readiness.yml, test/hourly-commercial-readiness-activation.test.ts, test/workflow-readiness.test.ts
activation_preflight가 읽기 전용 검사를 수행하고 JSON 증거와 Step Summary를 생성합니다. maintainwrite_ready 출력이 true일 때만 실행됩니다. 테스트는 실행 조건, 증거 비공개 처리, Node 24 형식을 검증합니다.
운영 절차와 readiness 기록
docs/hourly-commercial-readiness-loop.md
사전 점검 순서, 분류값, 조건부 Maintainer App 토큰 발급, 감사 산출물 분리와 운영 확인 절차를 문서화했습니다.

Estimated code review effort: 4 (Complex) | ~45 minutes

Mergeability Score: ⚪ Minimal · up to 61e6d

The change is merge-ready after normal checks and review; no actionable merge-blocking risk remains.

Sequence Diagram(s)

sequenceDiagram
  participant Scheduler
  participant activation_preflight
  participant maintain
  participant Maintainer App
  Scheduler->>activation_preflight: 시간별 워크플로 실행
  activation_preflight->>activation_preflight: 저장소, SHA, 활성화 조건 평가
  activation_preflight-->>Scheduler: 증거 파일과 terminal classification 기록
  activation_preflight->>maintain: write_ready 출력 전달
  maintain->>Maintainer App: write_ready가 true이면 토큰 요청
Loading

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed 제목은 릴리스 통합 후 스케줄러 활성화 증거를 재적용한 변경 사항을 정확하고 간결하게 요약합니다.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ 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 fix/hourly-scheduler-activation-post-release-v4

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
seonghobae merged commit 84a1b4c into main Aug 13, 2026
16 checks passed
@seonghobae
seonghobae deleted the fix/hourly-scheduler-activation-post-release-v4 branch August 13, 2026 00:12
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.

1 participant