whynot-control/workplans
tegwick cadbe22d9e
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
fix(workplans): re-key WHYNOT-WP strays onto WNCTL-WP
WHYNOT-WP belongs to whynot-design (26 ids vs 6 here), ruled by Bernd. The two
repos were cross-blocking in the hub: whynot-design could not claim
whynot-wp-0001 because this repo held it, and this repo could not claim
whynot-wp-0002 because whynot-design held that.

WNCTL-WP is newly registered to this repository. Numbers carry over unchanged
since nothing here used the new prefix. Both files declare repo: whynot-control,
so this is the repo's own work, not inherited template residue.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 14:15:09 +02:00
..
WNCTL-WP-0001-statehub-bootstrap.md fix(workplans): re-key WHYNOT-WP strays onto WNCTL-WP 2026-08-28 14:15:09 +02:00
WNCTL-WP-0002-beta-signal-intake.md fix(workplans): re-key WHYNOT-WP strays onto WNCTL-WP 2026-08-28 14:15:09 +02:00