From 88da76f7f19d5a8c38623eef2fa081d6ed3c4705 Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 4 Sep 2026 23:36:43 +0200 Subject: [PATCH] docs(workplan): close Forgejo package migration Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43 --- workplans/WHYNOT-WP-0004-forgejo-npm-migration.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/workplans/WHYNOT-WP-0004-forgejo-npm-migration.md b/workplans/WHYNOT-WP-0004-forgejo-npm-migration.md index fa25970..798a283 100644 --- a/workplans/WHYNOT-WP-0004-forgejo-npm-migration.md +++ b/workplans/WHYNOT-WP-0004-forgejo-npm-migration.md @@ -4,7 +4,7 @@ type: workplan title: "Move @whynot/design publication to Forgejo Packages" domain: infotech repo: whynot-design -status: active +status: finished owner: codex topic_slug: forgejo-npm-migration created: "2026-09-04" @@ -28,7 +28,7 @@ release contents before any credentialed write. This work promotes routed intake ```task id: WHYNOT-WP-0004-T02 -status: progress +status: done priority: high ``` @@ -53,3 +53,9 @@ Prepared `@whynot/design@0.4.2` on 2026-09-04. The package dry-run contains 105 files with IR `designVersion` 0.4.2; all five Playwright visual tests pass. The changelog gate correctly reports no *post-release* `[Unreleased]` entry after the 0.4.2 section was cut. + +Published and exact-integrity verified on Forgejo on 2026-09-04. The dedicated +publish lane's OpenBao read is healthy but its stored token could not complete +the Forgejo write, so the plan-authorized `forgejo-admin-api-token` lane was used +as a one-time contained recovery path. Dedicated-token rotation remains live in +`WARDEN-WP-0037`; no credential value was printed or persisted.