죽은 링크 전수 감사 — 서버가 내보내는 모든 주소 출처: https://hyeonworks.com — 2026-09-04 실행 스크립트: evidence/audit/link-audit.py (재실행하면 같은 방식으로 다시 검사한다) 이 감사가 필요한 이유: 주소는 서버가 게시할 때 만들어 DB 에 저장한 문자열이라 화면 코드 어디에도 흔적이 없다. 저장소 안의 to=/href= 리터럴만 훑는 감사로는 잡히지 않는다 — 실제로 결정 링크가 그렇게 숨어 있었다(§9.2). $ python3 evidence/audit/link-audit.py ====================================================================== 200 /cases/bff-session-csrf-responsibility 200 /cases/collection-fetch-join-in-memory-paging 200 /cases/eager-toone-nplus1-without-access 200 /cases/fetch-join-multibag-and-row-explosion 200 /cases/identity-header-trust 200 /cases/spa-browser-credential-boundary 200 /cases/split-custody-access-token 200 /concepts/idp-brokering 200 /projects/backend-clean-architecture 200 /projects/keycloak-patterns 200 /projects/keycloak-patterns/decisions#bff-owns-token-when-browser-must-not 200 /projects/liner-n-plus-1 200 /questions/bff-session-authorized-client-store 200 /questions/edge-authorization-scope 200 /questions/refresh-rotation-replica-contention 200 /questions/server-session-pattern-multi-instance 200 /references/authorization-code-endpoint-credential-movement 200 /references/bff-authentication-design-criteria 200 /references/external-idp-federation-application-boundary 200 /references/forward-auth-identity-header-trust 200 /references/oauth-oidc-pattern-selection-criteria 200 /references/oauth-token-application-session-boundary 200 /references/public-confidential-client-boundary 200 /releases/0.1.0 200 /releases/0.2.0 200 /releases/0.3.0 200 /topics/jpa-feed-query-performance 200 /topics/jpa-feed-query-performance/derived-query 200 /topics/jpa-feed-query-performance/fetch-join 200 /topics/jpa-feed-query-performance/fetch-join-paging 200 /topics/oauth-oidc-auth-boundary 200 /topics/oauth-oidc-auth-boundary/bff 200 /topics/oauth-oidc-auth-boundary/forward-auth 200 /topics/oauth-oidc-auth-boundary/mediator 200 /topics/oauth-oidc-auth-boundary/spa 검사한 주소 35개 죽은 링크 없음 종료코드: 0