coulomb/whynot-design
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

docs(workplan): close Forgejo package migration
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43
This commit is contained in:
tegwick 2026-09-04 23:36:43 +02:00
parent 65247c9320
commit 88da76f7f1
1 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/WHYNOT-WP-0004-forgejo-npm-migration.md
View file

@ -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.