feat(metadata): extend public-surface desired state

[seonghobae]

Outcome

Extends the organization-owned declarative repository metadata manifest to 22 reviewed public surfaces while keeping leaf README/Pages ownership exact and non-duplicative.

The latest cohort includes PolicyWeave, supply-chain-control-plane, learning-management-platform, learning-content-studio, and learning-record-store. Each entry preserves exact repository casing, bounded customer-facing copy, normalized topics, exact DeepWiki intent, and legacy /docs Pages intent without treating branch-only source as live publication.

Source coordination

Leaf repositories remain authoritative for customer-facing source. The central reconciler verifies prerequisites and applies settings; it does not rewrite leaf README copy.

Notable current ownership includes:

• keyverse#103 badge / keyverse#127 Pages source;
• OriginWeave#274 badge + Pages source;
• accounting-information-platform#37 README/badge / #45 Pages source;
• pg-erd-cloud#824 README/badge / #1046 Pages source;
• clearfolio#305 README/badge / #538 Pages source;
• DiagramWeave#34 badge + Pages source;
• semantic-data-portal#72 README/badge / #90 Pages source;
• contextual-orchestrator#994 broader README rewrite while #1003 owns its Pages source;
• mhtml-etl-gateway#56, PolicyWeave#1, supply-chain-control-plane#1, and learning-management-platform#1 each own their reviewed public surface;
• learning-content-studio#1 now owns README, exact badge, Apache-2.0 grant, and docs/index.md; former child [codex] Require OpenCode inline suggested diffs #8 is closed after its complete unique Pages delta was folded into Add Palette journal for profile repo #1;
• learning-record-store#1 now owns README, exact badge, Apache-2.0 grant, and docs/index.md; former child Block OpenCode approval on stale fact evidence #7 is closed after its complete unique Pages delta was folded into Add Palette journal for profile repo #1.

The operational baseline on this branch was updated to match those consolidations rather than leaving closed child PRs recorded as active source owners.

Until branch-only prerequisites reach their protected default branches, reconciliation fails closed only for the affected repository while eligible siblings remain actionable.

Review remediation and control-plane boundary

The manifest contract covers all 22 exact-cased entries and representative normalized topics. Repository-source probing requires a successful Contents API object with type: file; empty responses/directories are not source evidence. The operational baseline remains aligned with the dedicated settings-credential owner path #1625 and the workflow-backed Pages preservation repair already integrated centrally.

Branch-selectable manual dispatch remains intentionally outside the control-plane contract. Live description/topic/Pages convergence is not claimed by this PR itself.

Current exact authority

Current exact branch head after source-owner reconciliation: 8b246d009333452c547862fb4d5bcc360f929471.

The branch changes the declarative desired-state manifest, its contract test, and the public-surface operational baseline. Every predecessor-head check/review is historical after the source-owner update. Protected PR validation must execute on this unchanged head before integration.

Scope

Central metadata desired state, executable validation, and operating evidence only. No leaf runtime, dependency, credential provisioning, ruleset, release, or live repository-setting mutation is performed by this PR. Live descriptions, topics, and Pages remain unclaimed until protected integration, trusted-main apply, and postcondition verification succeed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 9c050d9d-4a26-4e0a-b0eb-b48d7b815095

📥 Commits

Reviewing files that changed from the base of the PR and between 696852e and 5679f4c.

📒 Files selected for processing (3)

• config/repository-metadata.json
• docs/doctoring/repository-public-surface-reconciliation.md
• tests/test_repository_metadata_reconciliation.py

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

16개 저장소의 메타데이터를 추가하고, 공개 surface 조정 문서와 저장소 메타데이터 검증 테스트를 22개 저장소 기준으로 갱신했습니다.

Changes

저장소 메타데이터 확장

Layer / File(s)	Summary
매니페스트 및 검증 테스트 config/repository-metadata.json, tests/test_repository_metadata_reconciliation.py	16개 저장소의 description, topics, deepwiki, pages 메타데이터를 추가했습니다. 저장소명과 필수 토픽 검증 목록 및 문서 인덱스 응답 fixture를 갱신했습니다.
공개 surface 조정 계약 docs/doctoring/repository-public-surface-reconciliation.md	desired-state fleet을 22개 저장소로 확장했습니다. source ownership, Pages 계약, label 처리, 보호된 기본 브랜치 통합 경계를 갱신했습니다.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: 🔵 Low · up to 5679f

The manifest expands centrally managed public metadata and Pages intent from 8 to 22 repositories, increasing the scope of a maintainer-controlled reconciliation run. Existing protections keep the change mergeable, but owners should explicitly acknowledge the broader cross-repository blast radius.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	PR은 #1626의 결정과 일치합니다. 중앙 워크플로에 branch-selected manual dispatch를 추가하지 않았고, 기존 protected default branch 스케줄 경로를 유지합니다. 메타데이터 매니페스트와 관련 검증만 업데이트했습니다.
Out of Scope Changes check	✅ Passed	변경 사항은 저장소 메타데이터, 공개 표면 검증 테스트, reconciliation 문서와 테스트 fixture에 한정됩니다. 모든 변경은 PR 목표와 관련되며, 자격 증명, 워크플로 제어, 런타임 코드 또는 라이브 설정 변경은 없습니다.
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 2 functions across 1 files. (2 skipped: 2 …
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 공개 표면의 메타데이터 desired state를 확장하는 주요 변경 사항을 정확하고 간결하게 설명합니다.

Full details: Docstring Coverage

Explanation

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 2 functions across 1 files. (2 skipped: 2 unsupported.)

✨ 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 metadata/extend-public-surface-desired-state

---

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]

Exact-head follow-up for 15e1a9a80106456b2b0fa3aff29af5b8b15971b5: manifest schema validation succeeds, but Repository Metadata Reconcile run 33533730897 fails in the Run metadata contract tests at repository quality gates step. The branch still has test_metadata_manifest_declares_exact_casing_and_public_surfaces() asserting the manifest key set equals the original eight repositories, while this PR now adds five (keyverse, OriginWeave, accounting-information-platform, pg-erd-cloud, clearfolio). That stale exact-set contract is therefore the deterministic validation root cause. Please extend the expected mapping on this same active manifest lane (with representative required topics for all five) rather than weakening/removing the assertion. I am not pushing onto the branch because it moved concurrently during this run; preserving the active writer avoids clobbering its new two-repository extension. Sibling security checks are otherwise succeeding/continuing.

[seonghobae]

QUEUE_SATURATION_CHICKEN_EGG verified for exact head 8b246d009333452c547862fb4d5bcc360f929471 against protected main@0b724fffcda468127ace1f1ff4ef5d91c73ef071.

Evidence re-fetched immediately before merge decision:

• GitHub reports the PR mechanically mergeable and non-draft, with a three-file desired-state/test/operational-evidence delta.
• Every review thread is resolved; the previously substantive manifest/test and source-owner-reference findings were repaired on successor heads.
• Exact-head CodeRabbit and Devin commit statuses are both success.
• Exact-head Actions inventory contains nine PR workflows and every listed run is still queued: Scorecard PR, SAST Semgrep, Security Scan, Secret Scan, OSV-Scanner PR, CodeQL PR, Python Security, SBOM Generation, and Repository Metadata Reconcile. No exact-head workflow failure is present in that inventory.
• The central .github Actions queue is currently 943 queued runs, so waiting for these nine admission workflows would preserve the control-plane backlog while this reviewed declarative fleet extension remains unable to run from trusted main.

This exception does not treat queued checks as passing and does not transfer predecessor workflow evidence. It uses owner-authorized bypass solely because the unchanged current head has independent current-head review success, no unresolved substantive finding, no conflict, and the remaining admission evidence is blocked by the verified saturated Actions fleet. Merge is pinned to the exact head SHA; any head movement must abort.