From 744b4aa36eb3af20cf9328d2fd605f7782943c4e Mon Sep 17 00:00:00 2001 From: tegwick Date: Sat, 10 Oct 2026 12:40:12 +0200 Subject: [PATCH] NK-WP-0048: record key-cape adoption of the derived Forgejo custody path Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 736651@bnt-lap001 Assistant-Session: f6189624-fd64-4109-b53e-f8a59ca8a2d8 --- workplans/NK-WP-0048-security-case-types.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/workplans/NK-WP-0048-security-case-types.md b/workplans/NK-WP-0048-security-case-types.md index 08e0aea..1e28ab0 100644 --- a/workplans/NK-WP-0048-security-case-types.md +++ b/workplans/NK-WP-0048-security-case-types.md @@ -381,6 +381,13 @@ rendered and built (message `1ebddae9`; CCR drafts handed to railiance-platform) so T06 now waits on the platform apply, the mint-secret lane and the attended register-client session. +2026-10-10: key-cape adopted the type's custody path (key-cape ab5cccd, message +`88a4559c`): `docs/forgejo-oidc-client-request.yaml` and KEY-WP-0038-T02 name +`platform/workloads/keycape/forgejo`, field `CLIENT_SECRET`, delivered as +`sso/keycape-forgejo-client` through `external-secrets-keycape-forgejo`, and the +`forgejo/netkingdom-oidc-client` proposal is withdrawn. This matches the type and +the Forgejo example; no change needed here. + ```task id: NK-WP-0048-T07 status: wait