chore: record pre-existing uncommitted repository state

Snapshot of the in-flight state that already existed, identically, in both
this worktree and the main checkout before this session began: the initial
HTTP Client platform implementation (previously untracked), the redis-lab
removal, and the JPA / object-storage / notification integration work.

Kept separate from this session's HTTP Client review response, which lands
in the following commit, so the two bodies of work stay reviewable apart.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/runbooks/redis-capability-incident.md

@@ -176,6 +176,13 @@ Sentinel은 asynchronous replication의 zero-data-loss나 strong consistency를
 `min-replicas-to-write`, lag bound, replica acknowledgement가 설정돼도 acknowledgement 결과가
 불명확한 mutation은 여전히 `INDETERMINATE`다.
 
+`min-replicas-to-write 1` + `min-replicas-max-lag 1`은 선택이 아니라 **필수**다. 미설정 시
+promotion 중 교체된 구 primary가 계속 `+OK`를 반환하고 그 write는 resync에서 폐기된다. 7.4
+레인 실측: 승격 후 강등까지 11초, 그 사이 **2,086건이 acknowledge된 뒤 소실**, 실패한 명령은
+1건. 클라이언트는 이를 감지할 수단이 없다 — 서버가 응답했으므로 driver·SDK·호출자 모두
+정상 성공으로 기록한다. 설정 후 동일 promotion에서 소실 1건, 나머지 2,020건은 `NOREPLICAS`로
+명시 거부됐다. 근거: `docs/redis/operations.md`, `LiveRedisSentinelPromotionTest`.
+
 ### Disposable Multipass k3s qualification safety
 
 qualification lab은 host k3s incident 조치 도구가 아니다. VM exact allowlist는

docs/runbooks/template.md

@@ -39,4 +39,6 @@ status: <stub|active>
 > **Note**: This is the canonical runbook template.
 > Copy this file, rename it to match the `runbook://area/scenario` pattern (→ `area-scenario.md`),
 > fill in the frontmatter fields, replace section bodies with operational content,
-> then set `status: active` and remove from `STUB_ALLOWLIST` in `RunbookCoverageContractTest`.
+> then set `status: active`. `LEGACY_STUB_DEBT` in `RunbookCoverageContractTest` is temporary
+> containment for existing debt only; do not add a new stub there. Complete the runbook or adopt
+> the future owned, expiring debt ledger.