docs: establish governed public repository surface

[seonghobae]

Outcome

Serialize the public repository surface behind the canonical #321 → #352 documentation stack without dropping the one material #353 delta that is not already represented there.

Exact source / repaired ancestry

• current base: docs/registry-readme-links@5cdbd57ab66c39c92c921cf3c88897938a6c61cb (docs: make README links registry-safe #352)
• current head: ef804b40a6d5be3b44b412dc7fd6b81c04cc763d
• the current head is an ordinary two-parent merge: predecessor docs: establish governed public repository surface #353 head 074f672c57750965c70b32299d1ec6e211592f7a + canonical docs: make README links registry-safe #352 head 5cdbd57ab66c39c92c921cf3c88897938a6c61cb; no force update or destructive rebase was used
• relative to docs: make README links registry-safe #352, the effective delta is now exactly one file: docs/index.md
• README is inherited unchanged from docs: make README links registry-safe #352, so the previous wrong-base collision is removed
• current PR is Draft, open, and mergeable

Effective delta

The canonical #321/#352 docs/index.md already contains the richer code-current responsibility, security, recovery, release, and DeepWiki navigation contract. The former #353 replacement document is therefore not replayed over it. The retained delta is only Markdown front matter:

• title: pg-llm-batch
• a provider-neutral description covering PostgreSQL token accounting, bounded batch assembly, and durable batch lifecycle

The old README badge-only delta is not duplicated because the canonical public index already carries the exact DeepWiki badge/link; keeping a second decorative copy would add no distinct product contract.

Responsibility boundary

pg-llm-batch owns PostgreSQL-authoritative token accounting, bounded JSONL batch assembly, durable standalone and tenant-qualified lifecycle state, and the provider-neutral batch boundary. Contextual Orchestrator retains provider/model discovery and routing. Embedding hosts retain authentication, tenant authorization, retention policy, telemetry configuration, and caller-owned transaction authority.

The source does not claim distributed exactly-once delivery, immutable release, deployed service, or live Pages publication.

Verification

Exact current head ef804b40a6d5be3b44b412dc7fd6b81c04cc763d has independently reacquired repository-local GREEN after the ordinary restack:

• CI 35480442238: SUCCESS;
• Release Acceptance 35480442226: SUCCESS;
• fresh formal reviews: none;
• fresh inline review threads: none.

The parent #352 exact 5cdbd57ab66c39c92c921cf3c88897938a6c61cb is likewise repository-local GREEN on CI 35477695148 and Release Acceptance 35477695138. Parent/predecessor evidence did not transfer; both exact heads completed their own generations. Absence of review is not approval.

Keep Draft until the parent stack and protected integration/governance prerequisites settle. GitHub Pages publication is not complete until the eventual protected source is actually published and the live endpoint/rendered source are verified. No bypass, self-approval, force push, release claim, source-neutral wake commit, blind rerun, or predecessor evidence transfer.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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]

2026-09-20 exact-head public-surface evidence

• head 074f672c57750965c70b32299d1ec6e211592f7a; protected base main@5913c4bad79d6bc29d7cc1c624abb7db2ea6a77c
• ahead 2 / behind 0; merge base equals protected main
• exactly README.md and docs/index.md
• blobs: README 87a33cd5eeb9fd9a4bceb0f9b7685cee6b870696; overview 0355ccd4efc6b490e2328a4ef6280f561f03ff9f
• exact readback: one linked DeepWiki badge, valid front matter, canonical navigation, and explicit provider-routing/identity/tenant/transaction/release boundaries
• lifecycle: Draft; mergeable=true; unresolved threads=0; APPROVED reviews=0
• exact-head Security 35472707127, CI 35472707126, CodeQL PR 35472707140, SAST Semgrep 35472707133, Release Acceptance 35472707148: all queued

Central desired state is at ContextualWisdomLab/.github#2110 head 6690e56aec7a5568c96ee3d2ef44dae719936ed8. This does not publish from the Draft head or establish a release. Protected-main integration, settings reconciliation, deployment, HTTP 200, and rendered-source verification remain required.

[seonghobae]

Fresh canonical-owner review found a real single-writer / wrong-base repair finding on this Draft; this is not a reason to close it.

Exact #353 074f672c57750965c70b32299d1ec6e211592f7a is based directly on protected main@5913c4bad79d6bc29d7cc1c624abb7db2ea6a77c and changes only README.md + docs/index.md. Those two paths already have active canonical ownership in the serialized public-documentation stack: #321 owns README.md + docs/index.md on #323, and #352 is the current README-side child of #321. #321 exact d5057439... is repository-local GREEN; #352 exact b08218d2... remains the current child awaiting its own exact-head acceptance.

The delta here contains useful material — the README DeepWiki badge plus a front-matter/public-overview candidate — but the current main-based tree cannot be integrated independently without discarding or overwriting the materially richer #321/#352 public contract (driver/commercial status, SecretStore boundary, health disclosure boundary, tenant/RLS/recovery limitations, and existing-volume extension-retirement wording).

Freeze source movement on this lane for now. Repair must preserve the valid #353 delta by ordinary/non-force serialization behind the canonical public-doc stack or a successor that completely inherits its valid content/contract/evidence; do not force-push/rebase, weaken tests, or close merely to reduce PR count. A retarget alone is insufficient unless the resulting tree is first reconciled losslessly with #321/#352. Reacquire exact-head evidence after that reconciliation; this main-based generation's queued checks do not transfer.

[seonghobae]

Fresh owner update: canonical public-doc child #352 has moved ordinary-forward to exact 5cdbd57ab66c39c92c921cf3c88897938a6c61cb after repairing its real stale-test CI failure. #352 remains based on #321 and is now 15 ahead / 0 behind exact #321; its effective relative surface is README.md, tests/test_readme_registry_links.py, and tests/test_count_tokens_stdin_documentation.py.

This does not change the earlier repair finding here: this PR still starts from protected main and still writes both README.md and docs/index.md, which are canonical #321/#352 public-surface ownership. Do not merge this main-based tree standalone and do not overwrite the stronger current README/docs contracts to preserve only the badge/overview delta. Keep Draft/frozen until the current #352 exact-head evidence settles, then serialize the valid #353 delta behind the canonical stack ordinary/non-force or transfer it losslessly to a successor. No close is requested.