From 7724a8720c856019b706cfbe5e387f014f8089e7 Mon Sep 17 00:00:00 2001 From: DongHyeonka Date: Tue, 18 Aug 2026 02:05:29 +0900 Subject: [PATCH] fix: account for TECH_LOG_STUDIO_SESSION in the auth profile registry pin Task 3's contract contribution legitimately registered a TECH_LOG_STUDIO_SESSION auth profile, growing INSTALLED_REST_AUTH_PROFILES from 2 to 3 entries. The exact-key-set regression test at contract-registry-immutability.test.ts:91 correctly caught the drift; test:unit was left off Task 3's verification list, so it went unnoticed until Task 5 ran the full suite. Updates the expected key list rather than weakening the assertion, so it keeps forcing a reviewer to confirm any future registry change was intended. --- tests/unit/contract-registry-immutability.test.ts | 1 + 1 file changed, 1 insertion(+) diff --git a/tests/unit/contract-registry-immutability.test.ts b/tests/unit/contract-registry-immutability.test.ts index f62746c..cc47844 100644 --- a/tests/unit/contract-registry-immutability.test.ts +++ b/tests/unit/contract-registry-immutability.test.ts @@ -91,6 +91,7 @@ describe("LIVE-02 installed REST auth profile registry", () => { expect([...registry.keys()].sort()).toEqual([ "ANONYMOUS", "REFERENCE_EXTERNAL_BEARER", + "TECH_LOG_STUDIO_SESSION", ]); expect([...registry.entries()].length).toBe(registry.size); expect([...registry.values()].length).toBe(registry.size);