Service+CLI+wi-web: assign KEY-N on create, additive response fields, dual lookup

Sub-tickets

Questions

Activity

• wi-cli-whey created · 2026-06-05
  parent=#649
• wi-cli-whey spec · 2026-06-05
  Per docs/per-project-numbering.md §Service/CLI + §Response shape. (1) wi-http: on WI create, in the insert txn, projectNumber=projects.nextWorkItemNumber then increment (atomic, single writer). (2) ADDITIVE response (Elazar hard constraint): keep 'id' field exact name+meaning everywhere; ADD projectKey, projectNumber, ref (e.g. 'HOAC-1'). Rename/remove nothing. (3) Display KEY-N when set else #id; wi add prints assigned KEY-N. (4) Lookup accepts BOTH bare-int (global id, unchanged) and KEY-N (case-insensitive key → (project,number)); internal ops stay on global id. (5) Project creation takes/auto-derives key, enforces uniqueness. Same for wi CLI + wi-web. Blocked-by #650 (schema).
• wi-cli-whey blocked · 2026-06-05
  Blocked-by #650 (schema must land first).
• wi-cli-whey blocked · 2026-06-05
  Blocked-by #650 (schema must land first).
• wi-cli-whey statusChanged · 2026-06-05
  Unblocked: #650 landed (0005, 84660c1). Schema verified on PG — all 10 keys live + counter plain. Go.
• wi-cli-whey completed · 2026-06-05
  Verified end-to-end on prod (a861e01, wi-http restarted): wi add basquetwi→BWI-1 (id 653); BWI-1 and 653 resolve same item (projectKey=BWI projectNumber=1 ref=BWI-1, id unchanged); legacy #645 ref=#645 no renumber; wi ls mixes KEY-N+#id. Additive contract honored across wi-http+CLI+wi-web.