chore(metadata): record public-surface label taxonomy wave 3

[seonghobae]

Outcome

Record evidence-backed repository issue/PR semantic types in the organization-owned label taxonomy so live classifications remain idempotent rather than one-off mutations.

The current branch doctoring record covers 175 active evidence-backed targets: a reconciled 47-target operating baseline plus 128 reviewed wave-3 targets. The central taxonomy owns the managed primary semantic labels (feature -> enhancement, bug -> bug, documentation -> documentation); richer repository-local priority, workflow-status, security, maintenance, architecture, component, and type: maintenance labels remain outside that managed semantic set.

Successor / stale-target reconciliation

The active inventory follows current canonical writers instead of retaining stale issue identities merely to keep counts stable. Existing branch history records successor carryover including codec-carver#514 → codec-carver#516, g7#2 → g7#3, merged psychometrics-commons#442 → current psychometrics-commons#434, superseded scopeweave#650 → scopeweave#651, and complete carryover for retired contextual-orchestrator#1003 and accounting-information-platform#45 into already-recorded canonical targets.

The current taxonomy blob is 2af5f823dea1e463edc38a4bf80295ace6831f2e. Current head additionally integrates the live-read assignments for pg-erd-cloud#1100, .github#2037/#2039, naruon#1603/#1604/#1605/#1606/#1607/#1608/#1609, appguardrail#1182/#1183, litellm-patched-proxy#5, 9drive#4, ConceptWeave#40, noema#560, and quarantine-sandbox-runtime#99/#100; tests intentionally pin exact inventory/blob identity, and the operator records must move atomically with any assignment change. Fresh traversal has added coordination on this PR for newly classified targets such as naruon#1541, learning-record-store#6, ContextualWisdomLab.github.io#204, pg-erd-cloud#1061, naruon#1500, html4tree#590, contextual-orchestrator#1028, naruon#1539, and pingora-gateway#17; those are live repository classifications but are not claimed as integrated taxonomy entries until this branch's config/test/doctoring set is updated together.

Exact authority — 2026-09-27

GitHub reports this PR open, Draft, and mechanically mergeable. Current exact head is 04f8d5135065498dce50b2150e4fa986e70ac60f.

The stale-base repair was performed without force-push. RED commit d8e7521de73035e81590f15db84636d2313da6f8 proves that repository names containing .. or ending in . were accepted. Two-parent merge 04f8d5135065498dce50b2150e4fa986e70ac60f preserves that test and current protected main@e6334e229581a918e2f22de18733b76fa65d7e71; its tree is 056d79a255439ec68aad299902b058e3111a0c6c. The main-side stricter repository-name validation and branch-side bounded ThreadPoolExecutor reconciliation are both present.

Fresh compare is ahead 63 / behind 0 with protected main as the merge base and exactly eight changed files. A detached checkout of the exact remote head passed all 19 label reconciliation/taxonomy tests, Python compilation, taxonomy --validate-only, and git diff --check.

Exact-head Repository Metadata Reconcile 36271689379, CodeQL PR 36271689369, SAST Semgrep 36271689346, Security Scan 36271689383, and Python Security 36271689343 are queued. The Reviews API still contains a CHANGES_REQUESTED verdict and has zero independent approvals; all inline threads are resolved. Draft status remains correct and this PR must not merge until current-head Checks and review admission settle.

The branch currently carries 63 commits and eight changed files. Continue preserving the single writer: live classification increments recorded in PR comments are not integrated until config, exact inventory tests/fixtures, and operator records move atomically on this branch.

Governance / concurrency

This branch is independent of Draft metadata desired-state PR #1639, which owns repository descriptions/topics/Pages intent. No branch protection, repository settings, Pages settings, secrets, review rules, or leaf repository source is changed here.

The recorded classifications do not make Draft work Ready, unblock blocked work, transfer merge authority, or waive exact-head checks/reviews. A source assignment is not live convergence evidence until repository labels are re-read after protected integration.

Summary by CodeRabbit

• 새 기능

  • 저장소 라벨 분류 체계에 다양한 저장소·이슈 매핑을 추가하고 일부 기존 매핑을 최신화했습니다.
  • 라벨 분류 체계의 Wave 3 운영 문서를 추가했습니다.
  • 독립적인 라벨 대상 처리를 병렬화해 조정 작업을 빠르게 완료하도록 개선했습니다.

• 문서

  • 라벨 대상 운영 기록과 후속 조정 기준을 최신 상태로 갱신했습니다.

• 테스트

  • 병렬 처리, 라벨 분류 데이터 무결성, 워크플로 트리거 경로 검증을 추가·강화했습니다.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

📝 Walkthrough

Walkthrough

저장소 라벨 taxonomy와 운영 기록에 대상 매핑을 추가·수정했습니다. 라벨 reconciliation은 병렬 실행과 일괄 오류 출력을 사용합니다. 워크플로 트리거와 taxonomy 검증 테스트도 갱신했습니다.

Changes

저장소 라벨 reconciliation

Layer / File(s)	Summary
Taxonomy 및 운영 기록 갱신 config/repository-label-taxonomy.json, docs/doctoring/repository-label-taxonomy-wave-3.md, docs/doctoring/repository-public-surface-reconciliation.md	저장소와 이슈의 라벨 유형 매핑을 추가·수정했습니다. wave-3 대상과 successor reconciliation 운영 기록을 갱신했습니다.
병렬 reconciliation 실행 scripts/ci/reconcile_repository_labels.py, tests/test_repository_label_reconciliation.py	assignment 처리를 최대 8개 worker로 병렬화했습니다. 실패를 수집한 뒤 한 번에 출력합니다. 동시 실행 테스트를 추가했습니다.
워크플로 트리거 및 taxonomy 검증 .github/workflows/repository-metadata-reconcile.yml, tests/test_repository_label_taxonomy.py, tests/test_repository_label_taxonomy_workflow_trigger.py	운영 기록과 워크플로 테스트 파일을 pull request 경로에 추가했습니다. taxonomy blob, 중복 assignment, 유형 유효성, 운영 기록 결합을 검증합니다.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: 🟡 Moderate · up to cc2cf

This change expands centrally reconciled labels and parallelizes their application, but it currently assigns an incorrect semantic label to disksage#315, records an inaccurate wave-3 inventory, and can cause nondeterministic test failures. Correct these issues before merging.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 10 functions across 4 files. (4 skipped: 4…
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 PR의 주요 변경 사항인 public-surface label taxonomy wave 3 기록을 정확하고 간결하게 설명합니다.

✨ 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/label-taxonomy-public-surface-wave-3

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[seonghobae]

Fresh organization traversal found three additional evidence-backed semantic-type targets that are not in the current 61-target exact assignment set and should be folded into this same taxonomy lane (or its direct successor after re-reading the current head), rather than opened as a competing manifest writer:

• ContextualWisdomLab/disksage#315 → documentation (product-first README / PRD / public Pages source; the PR is currently repo-locally status: blocked because four substantive irreversible-purge safety findings remain).
• ContextualWisdomLab/macos_utility_packs#4 → documentation (public README/DeepWiki/docs landing surface; live repository description is already concise, while topics and Pages remain unset).
• ContextualWisdomLab/wardnet#144 → bug as the semantic primary type (the Kubernetes manifest-path repair is causal; documentation remains a useful repository-local affected-surface label).

Also corrected repository-local workflow status where fresh evidence showed a real prerequisite/control-plane blocker rather than mere review wait: disksage#315, accounting-information-platform#37, learning-record-store#1, and learning-management-platform#1 now carry status: blocked with stale status: needs-review removed. These status/priority labels should remain outside this PR's centrally managed semantic-type set, consistent with its current boundary.

When extending the exact assignment list, update the exact-set test and operating-record count together; do not weaken exact matching or transfer queued/predecessor evidence.

[seonghobae]

Fresh organization-label reconciliation found three additional evidence-backed documentation targets that are not yet present in this branch's exact assignment inventory: ContextualWisdomLab/fast-mlsirm#1519, ContextualWisdomLab/governance-risk-compliance#60, and ContextualWisdomLab/naruon#1527. Their live PR labels have been normalized to type: docs in the current pass; GRC #60 also now carries priority: medium and status: draft because its PR body explicitly requires Draft-only handling. Please fold these three targets into config/repository-label-taxonomy.json, the exact-assignment test, and the wave-3 operating record on this existing writer rather than creating a competing taxonomy PR. Existing branch targets reconciled live in the same pass include CalendarWeave #1, RankWeave #40, EgressWeave #190, appguardrail #1077, life-os #211, Orgmetra #160, j-planner #2, learning-{management-platform,content-studio,record-store} #1, mhtml-etl-gateway #44/#56, saju-caldav #42, DiagramWeave #33, kaefa #81, wardnet #130, enterprise-architecture-core #18/#37, pg-erd-cloud #1040, scopeweave #625, and metering-billing-platform #157. Preserve each repository-local priority/status/security/component label; this central lane should continue to own only the primary semantic type mapping.

[seonghobae]

One desired-state correction from the same pass: ContextualWisdomLab/disksage#315 should be bug, not documentation, as its current branch contains substantive fail-closed containment for an unsafe irreversible cache-trash purge plus a release-verifier defect repair; the documentation/PRD work is secondary. I normalized the live primary semantic label to type: bug while preserving documentation, priority: medium, and status: blocked. Please change the #315 assignment in the existing exact taxonomy/test/operating-record writer rather than adding type: docs back.

[seonghobae]

A second primary-type correction: ContextualWisdomLab/fast-mlsirm#1717 should be bug, not documentation. Although it owns the README/Pages entry, its current exact branch also repairs repository runner selectors, executable acquisition-release orchestration/provenance contracts, and fail-closed source-tree sealing under a fix(ci) lane. I normalized the live primary semantic label to type: bug and preserved documentation, priority: high, and status: needs-review. Please update the exact taxonomy assignment/test/operating record accordingly.

[seonghobae]

2026-09-20 follow-up classification increment

• TEPP#620 → bug, priority: high
• TEPP#621 → bug, priority: high
• TEPP#622 → bug, priority: high
• Orgmetra Fail closed when OpenCode approval review is not published #421/Extend OpenCode approval wait for peer checks #422 were directly re-read and already retained bug, priority: high; no mutation was needed.

Direct mutation responses/readback returned exactly the canonical semantic and priority pairs. Preserve this increment atomically with the preceding desired-state handoff.

[seonghobae]

2026-09-20 classification desired-state increment

Direct readback after mutation:

• ContextualWisdomLab/fast-mlsirm#2046 → enhancement, priority: high
• ContextualWisdomLab/fast-mlsirm#2047 → enhancement, priority: high
• ContextualWisdomLab/LineageWeave#908 retained documentation, priority: medium, status: blocked; conflicting legacy alias type: docs removed

Please carry these exact repository/record desired states in the canonical taxonomy reconciler.

[seonghobae]

2026-09-20 follow-up classification desired-state increment

• ContextualWisdomLab/fast-mlsirm#2051 → bug, priority: high

Direct readback confirms the canonical pair. This is a numerical reliability defect in the active one-way ICC owner lane, not a new feature classification.

[seonghobae]

2026-09-20 classification desired-state increment

• ContextualWisdomLab/enterprise-architecture-core#51 → documentation, priority: medium

Direct readback confirms the canonical pair. The PR owns only the repository-facing README and Pages source prerequisite.

[seonghobae]

2026-09-20 classification desired-state increment (direct API readback)

Newly created open records since the preceding metadata pass were normalized with exactly one canonical semantic label and one canonical priority label:

• bug: 14
• enhancement: 10
• maintenance: 2
• priority: critical: 5
• priority: high: 10
• priority: medium: 11

The 26 repaired records span accounting-information-platform, newsdom-api, fast-mlsirm, argos, pg-erd-cloud, clearfolio, seedream_evasepic, naruon, .github, contextual-orchestrator, free-router, html4tree, and appguardrail. Security/runtime authority defects were classified as bug/high or bug/critical from their stated impact; bounded performance/UX additions as enhancement/medium; provenance-adoption chores as maintenance/medium; scientific acceptance and missing evidence contracts as bug/high or enhancement/high according to whether the record repairs an invalid existing claim or adds a new source-faithful acceptance surface.

Fresh direct readback over all 27 records created at or after 2026-09-19T21:00:00Z (including already-canonical enterprise-architecture-core#51) reports semantic missing=0, priority missing=0, semantic conflicts=0, priority conflicts=0. This comment is the atomic desired-state handoff; search-index zero-state alone must not replace direct-record reconciliation.

[seonghobae]

2026-09-20 taxonomy increment: new EmbedRelay#5 was direct-read back with exactly documentation / priority: medium. It owns only the protected-source README DeepWiki badge and docs/index.md; central desired-state reconciliation remains in .github#2110. Preserve this pair in the atomic label desired state.

[seonghobae]

2026-09-20 taxonomy increment: new pg-llm-batch#353 was direct-read back with exactly documentation / priority: medium. It owns only the protected-source DeepWiki badge and docs/index.md; central desired-state reconciliation remains in .github#2110. Preserve this pair in the atomic label desired state.

[seonghobae]

2026-09-20 direct classification increment:

• accounting-information-platform#65 → enhancement / priority: high
• fast-mlsirm#2055 → bug / priority: high
• free-router#64 → maintenance / priority: medium (preserved dependency/javascript facets)
• newsdom-api#905 → enhancement / priority: medium
• argos#666 → bug / priority: high
• newsdom-api#904 → bug / priority: high
• argos#665 → enhancement / priority: medium
• inkspan#416 → documentation / priority: medium

Direct post-mutation readback found exactly one canonical semantic label and exactly one priority label on every new record. Please carry this increment into the atomic desired-state taxonomy/reconciliation successor; search-index zero-state is not accepted as proof.

[seonghobae]

Additional 2026-09-20 classification increment: pg-llm-batch#354 → bug / priority: medium. Direct readback confirms exactly one semantic and one priority label. Carry this record into the atomic taxonomy desired-state successor.

[seonghobae]

Classification alias repair: appguardrail#1077 retained conflicting legacy type: docs beside canonical documentation. Removed only the alias; direct readback preserves documentation / priority: medium / status: needs-review. Carry this normalization into the atomic taxonomy successor.

[seonghobae]

2026-09-20 classification increment: fast-mlsirm#2056 and #2057 → enhancement / priority: high. Direct mutation readback returned exactly one canonical semantic and one priority label on both. Carry this increment into the atomic taxonomy successor.

[seonghobae]

Taxonomy desired-state increment — 2026-09-20

Direct readback classified newly created fast-mlsirm#2058 as exactly bug / priority: high.

Evidence: the issue describes represented nonzero within-cluster dispersion being squared to binary64 zero, producing a falsely stronger scientific claim (within_variance == 0, icc == 1). This is a causal numerical correctness defect with high product/scientific impact, while the bounded fail-closed owner repair and ordinary protected release path remain available.

Please carry this exact repository/record/semantic/priority tuple into the atomic taxonomy desired-state successor.

[seonghobae]

Taxonomy desired-state increment — 2026-09-20

Direct readback classified three newly created fast-mlsirm scientific correctness records:

• #2059 → bug / priority: high
• #2060 → bug / priority: high
• #2061 → bug / priority: high

Each record concerns an exact-zero or binary64 underflow/cancellation condition that can produce a scientifically incorrect reliability claim. The causal Rust owner path remains available, so high severity is appropriate without elevating to critical. Please carry these exact record/semantic/priority tuples into the atomic taxonomy desired-state successor.

[seonghobae]

2026-09-26 incremental taxonomy drift handoff

• ContextualWisdomLab/linux-cluster-ops#346 → enhancement / priority: medium
• rationale: the existing redaction behavior remains correct; this record requests a bounded performance optimization to replace overly broad cheap admission substrings with complete token prefixes
• direct post-write readback: exactly one semantic label and one priority label; no alias/conflict observed

This is a newly created open-record increment for the canonical desired-state classifier; no closure or implementation claim.

[seonghobae]

2026-09-27 classification normalization handoff: aFIPC#261 had overlapping semantic labels type: docs and documentation. Removed only the alias type: docs; direct readback preserves exactly documentation / priority: medium / status: draft. Source head and lifecycle are unchanged.

[seonghobae]

2026-09-27 classification increment: mightyETL#149 normalized from duplicate semantic labels documentation + type: docs to the canonical single semantic label documentation, preserving priority: medium, status: draft, and scope: commercial-readiness. Direct readback confirms the alias is absent. Desired-state taxonomy should preserve this normalization.

[seonghobae]

2026-09-27 classification increment: life-os#211 normalized from duplicate semantic labels documentation + type: docs to the canonical single semantic label documentation, preserving priority: medium / status: draft. Direct readback confirms the alias is absent.

[seonghobae]

2026-09-27 metadata desired-state handoff: ContextualWisdomLab.github.io is now enrolled in #2110 at exact head 027287d043d94b522236829b0f13631dc2498d66. Existing taxonomy ownership for merged ContextualWisdomLab.github.io#203 remains canonical; no label delta was required. Live repository classification is preserved as organization homepage / GitHub Pages rather than product runtime, with source and HTTP publication verified byte-identical.

[seonghobae]

2026-09-27 classification handoff: the special .github control-plane repository is enrolled in #2110 at exact head e9b723f4b246c0dd24cb94a6b5720650702155aa as topics-only desired state. Its live description and automation/ci-cd/github-profile/ops/org-profile/security topics already converge; root DeepWiki badge and Pages are absent, so no source/publication claim or label delta was manufactured.

[seonghobae]

2026-09-27 stale-base reconciliation evidence

• RED: d8e7521de73035e81590f15db84636d2313da6f8 adds contract cases for Repo..Name and Repo.; the predecessor implementation failed because neither raised TaxonomyError.
• Protected base re-fetched: main@e6334e229581a918e2f22de18733b76fa65d7e71.
• Non-force two-parent merge: 04f8d5135065498dce50b2150e4fa986e70ac60f.
  • parents: RED head first, protected main second
  • exact tree: 056d79a255439ec68aad299902b058e3111a0c6c
  • main-side fail-closed repository-name regex and branch-side bounded ThreadPoolExecutor are both retained
• Fresh compare: ahead 63 / behind 0; merge base is current protected main; exactly eight intended files; GitHub reports mergeable.
• Detached exact-remote-head verification:
  • six focused test modules: 19 passed
  • python -m py_compile scripts/ci/reconcile_repository_labels.py: exit 0
  • taxonomy --validate-only: exit 0
  • git diff --check: exit 0
  • worktree clean
• Exact-head hosted gates were materialized and are queued:
  • Repository Metadata Reconcile 36271689379
  • CodeQL PR 36271689369
  • SAST Semgrep 36271689346
  • Security Scan 36271689383
  • Python Security 36271689343
• PR remains Draft: independent approvals 0; Reviews API retains CHANGES_REQUESTED; unresolved inline threads 0.

No merge or live protected-branch taxonomy convergence is claimed.

Classification direct readback: removed legacy type: maintenance; the PR now has exactly one semantic label (maintenance), one priority (priority: medium), and workflow status status: needs-review.

[seonghobae]

Taxonomy desired-state handoff — 2026-09-27

Fresh direct readback normalized korean-writing-skills#4 to exactly one semantic and one priority label:

• enhancement
• priority: high

Lifecycle evidence is preserved separately as status: draft. Exact source head is 048d39fa55e6042f0128c489162270f8089ec298; no alias semantic label remains. Please retain this record in the idempotent central taxonomy successor.

[seonghobae]

Desired-state taxonomy increment: ContextualWisdomLab/cwl-telemetry#1 is normalized to exactly enhancement / priority: high / status: draft. Its canonical metadata owner entry is proposed in ContextualWisdomLab/.github#2110@666c295f3934b42ff3ef1ed1f42fdb07d4d222fe. book-to-skill was excluded from CWL owner reconciliation because its README, release badges, sponsor, install path, and product links consistently identify virgiliojr94/book-to-skill as the upstream owner; no CWL ownership claim was invented.

[seonghobae]

2026-09-27 taxonomy increment (direct readback; corrected after concurrent Ready-admission reconciliation):

• ContextualWisdomLab/Orgmetra#160 → documentation / priority: medium / status: needs-review
  • removed legacy semantic alias type: docs and stale lifecycle alias status: draft; source head remains 2ba616abf95cf3c6c4da0527cf8d5b8e7dc6435a.
• ContextualWisdomLab/fast-mlsirm#2192 → bug / priority: high
  • accepted q_nuisance=481 can propagate nonfinite quadrature output.
• ContextualWisdomLab/fast-mlsirm#2191 → bug / priority: high / status: needs-review
  • exact head 382528cec967fc8f011819068d885a3a72fd9e5b is one commit ahead / zero behind stacked base 6a2fa9a827f9f975952c7c800dfc98086ff0a733, changing only the implementation and regression test; current CI and CodeQL are queued, approvals 0.

Ready denotes current-head review admission only. No queued check is treated as GREEN and no merge readiness or protected-branch publication is asserted.

[seonghobae]

2026-09-27 taxonomy increment (direct readback):

• ContextualWisdomLab/learning-management-platform#2 → bug / priority: high
  • removed conflicting legacy alias type: bug.
• ContextualWisdomLab/appguardrail#1099 → enhancement / priority: high
  • removed conflicting legacy alias type: feature.
• ContextualWisdomLab/.github#2356 → maintenance / priority: high / status: blocked
  • preserved area: ci-cd and area: security; removed legacy type: feature and mutually competing status: triaged.
• ContextualWisdomLab/late-life-anxiety-reanalysis#157 → documentation / priority: medium
  • classification follows the repository's citation/source-audit owner boundary and matches sibling Use workflow token for scheduler reads #179.

No issue was closed and no source/body was rewritten. Please preserve these exact assignments in canonical desired-state reconciliation.

[seonghobae]

2026-09-27 live taxonomy/exact-head handoff:

• cwl-telemetry#1: Ready admission now matches enhancement / priority: high / status: needs-review; exact head remains 833419c97da08ff9e1942bb75041a42ed0c3c322. Fresh local full suite is 23 passed, while hosted Telemetry contract/CodeQL remain pending and Semgrep/Security Scan remain queued. The stale status: draft alias and stale failure narrative were removed; no merge or release claim.
• fast-mlsirm#2191: current exact head 8c2f48f299fffbf8c0bb6016b3bd003e915510e9, stacked base 6a2fa9a827f9f975952c7c800dfc98086ff0a733, ahead 2 / behind 0, same two changed files, labels bug / priority: high / status: needs-review. CI is pending and CodeQL queued; approvals 0.
• fast-mlsirm#2192: remains bug / priority: high; issue and PR evidence now reference the new exact head and distinguish prior-head 44-test evidence from current hosted queues.

This handoff records desired-state drift only. It does not mark queued/pending gates GREEN or authorize protected integration.

[seonghobae]

2026-09-27 신규 open PR classification reconciliation:

• late-life-anxiety-reanalysis#287: bug / priority: high / status: draft
• late-life-anxiety-reanalysis#284: documentation / priority: high / status: draft
• xtrmLLMBatchPython#351: enhancement / priority: medium / status: needs-review
• xtrmLLMBatchPython#350: bug / priority: high / status: needs-review
• html4tree#803: bug / priority: medium / status: needs-review
• html4tree#802: enhancement / priority: medium / status: needs-review
• html4tree#801: bug / priority: high / status: needs-review
• .github#2405: bug / priority: high / status: draft / area: ci-cd / area: security
• naruon#1796, pg-erd-cloud#1227, pg-erd-cloud#1226, argos#707, appguardrail#1333: bug / priority: high / status: draft

Classification follows each current Draft/Ready state and the repository-facing change boundary. No source, base, review state, or PR lifecycle mutation was made; no predecessor was closed.