docs(baseline): converge protected retention hardening

[seonghobae]

Finding

Fresh protected main@65e8bb7acd34d334d811fae3eee8918de258900d includes the normal #642–#650 retained-memory hardening lineage, but docs/product-technical-gap-baseline.md still carried the older dated protected observation and protected-history list from before that lineage. The moving commercial baseline was therefore behind protected source.

Reality RED

Test-only exact 2708391336414bf155f83f9bd526b2c22dd2e598 added an executable documentation-authority regression while leaving canonical documentation unchanged. Hosted application CI 34642789714 checked out that exact head, passed exact checkout, package/toolchain, live-base, lockfile, install and release typecheck, then failed at release tests. Later release gates were skipped, so this is the intended documentation RED rather than an infrastructure failure.

Causal repair

Baseline repair dd5b38d869f2d527caa74867f52567a08f9938da records the dated protected main@65e8bb7acd34d334d811fae3eee8918de258900d, extends protected history through merged #640–#650 exact source identities, and classifies #641–#650 as a common bounded retained-memory/stream-fragmentation hardening lineage. It explicitly keeps immutable release, deployed heap/p95, provider/model routing, foreign outbound/quarantine authority and production outcome evidence separate.

A review of the new regression then found one case-sensitive fixture mismatch: the documentation intentionally begins the sentence with Stream fragmentation, while the test expected lowercase stream fragmentation. Current exact d635a7d6df6a1a8579e9f71eb03d0071e5831725 fixes only that assertion wording; documentation semantics are unchanged.

All required hosted gates must be terminal GREEN on this current exact before Ready/merge; predecessor workflow results will not be reused.

Owner boundary

This is documentation-authority convergence only. No production source, provider routing, credential authority, foreign domain truth, quarantine/security/outbound authority, release, deployment or production KPI semantics change.

Summary by CodeRabbit

• 문서

  • 보호된 소스 및 권위 기준선에 최신 관찰 정보와 병합된 변경 내역을 반영했습니다.
  • 메모리 보강 변경 사항과 고정 용량 버퍼, 점진적 소비 및 청크 크기 검증에 대한 공통 기준을 문서화했습니다.

• 테스트

  • 관련 병합 변경의 정확한 커밋 정보와 필수 문구가 문서에 포함되는지 검증합니다.
  • 성능을 입증한다고 과장하는 표현이 추가되지 않도록 검증합니다.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 4b439079-3a38-4636-a377-2626161863c4

📥 Commits

Reviewing files that changed from the base of the PR and between 65e8bb7 and d635a7d.

📒 Files selected for processing (2)

• docs/product-technical-gap-baseline.md
• test/documentation-retention-hardening-current.test.ts

---

📝 Walkthrough

Walkthrough

보호된 기술 기준선에 PR #639~#650의 병합 이력과 bounded retained-memory hardening 규칙을 추가합니다. 테스트는 정확한 커밋 해시와 필수 문구를 확인하고, 프로덕션 성능을 증명한다는 문구를 차단합니다.

Changes

기술 기준선 갱신

Layer / File(s)	Summary
기준선 갱신 및 회귀 검증 docs/product-technical-gap-baseline.md, test/documentation-retention-hardening-current.test.ts	보호된 관찰 기준과 PR #639#650의 정확한 커밋 해시를 갱신합니다. PR #641#650의 bounded retained-memory hardening 불변식과 배포 heap/p95 증거의 분리 원칙을 추가합니다. 테스트는 해시와 필수 문구를 확인하고, #650 proves production performance 문구가 없음을 검증합니다.

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

Change: Other

✨ 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 docs/retention-hardening-baseline-20260912

---

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]

Current-head review at d635a7d6df6a1a8579e9f71eb03d0071e5831725: the patch is documentation-authority convergence only, preserves Noema/foreign-owner boundaries, keeps production heap/p95 and immutable-release evidence separate, and the executable regression matches the updated protected history through #650. All four hosted gates on this exact head are terminal SUCCESS; no inline threads are open. No additional source/test/documentation finding remains on this exact.