chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-06-27:
  - update .custodian-brief.md for whynot-design

.custodian-brief.md

@@ -2,17 +2,21 @@
 # Custodian Brief — whynot-design
 
 **Domain:** infotech  
-**Last synced:** 2026-06-27 12:29 UTC  
+**Last synced:** 2026-06-27 13:17 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
+### Ad hoc fixes — 2026-06-27
+Progress: 1/1 done  |  workstream_id: `4945ead3-d54b-438f-963a-2fd687c472d4`
+
 ### Downstream consumption: versioned IR releases + consumer drift-check
 Progress: 1/9 done  |  workstream_id: `41fed928-f44a-48f4-9870-120310fbf071`
 
 **Open tasks:**
+- ! Publish to the Gitea npm registry  `dbd3a2e6`
+  *(wait: Config + docs + packaging done (private:false, publishConfig, lit→peerDep, repository.url, .npmrc, PUBLISHING.md, ir/ in files+exports; npm pack --dry-run validated). Remaining: actual `npm publish` + `npm i` install-verify — blocked on a Gitea NPM_AUTH_TOKEN (operator/OpenBao-owned; warden route CLI not available here) and an explicit outward-publish go-ahead (publish is immutable).)*
 - ! Showcase as visual catalog (depends on WP-0002 T11)  `a0886a4f`
-- · Publish to the Gitea npm registry  `dbd3a2e6`
 - · Generate ir/manifest.json  `aaa6d20f`
 - · Define the consumer sync-point  `fe077343`
 - · Build the `drift` CLI  `db7fcac0`