ts-strictcli: release v0.40.1

Autogenerated: true
Claude-Code-Session-Id: b90b8375-6d62-457f-b66f-4bf9e7557d8e

Author: smm-h

.rlsbl-monorepo/releasables/ts-strictcli/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 # Changelog
 
+## 0.40.1
+
+A member-spelled choice's member flag can declare a short, closing the gap that made converting a group of flags into a member-spelled selector drop every short they had.
+
+<details>
+<summary>Context</summary>
+
+The framework already promised this: §24.4 says a short declared on a member is an ordinary flag short, the refusal for a short on the selector itself says "declare the short on a member", and the short-claim table, the help renderer and the two sibling-scope short guards already read a member's short. Only Go could produce one. The short now goes on the declaration each member shape puts its electing flag on -- choice({value: {carrier, help, short}}) for a payload-carrying member, choice({help, short}) for a payload-less one -- and declaring it anywhere else is a compile error where the type system can see it and a registration error where it cannot.
+
+</details>
+
+### Fixes
+
+- [ts-strictcli] **A member-spelled choice's member flag can declare a short.** `choice({value: {carrier, help, short}})` declares a payload-carrying member's short and `choice({help, short})` a payload-less one's, so converting an at-most-one group of flags into a member-spelled selector no longer drops every short those flags had. The short elects at every door argv supports, renders beside its member in `--help`, publishes on the payload's schema entry, and is claimed against every simultaneously live scope.
+
 ## 0.40.0
 
 The declaration-regime release: mandatory presence declarations, scoped selectors replacing mutex groups, real-JSON-Schema value fragments (schema v2), the co-occurrence constraint system, and the update-command construct.

.rlsbl-monorepo/releasables/ts-strictcli/version

@@ -1 +1 @@
-0.40.0
+0.40.1

CHANGELOG.md

@@ -2070,6 +2070,21 @@ Deployed Go binaries that use strictcli's check system previously panicked when
 
 # ts-strictcli
 
+## 0.40.1
+
+A member-spelled choice's member flag can declare a short, closing the gap that made converting a group of flags into a member-spelled selector drop every short they had.
+
+<details>
+<summary>Context</summary>
+
+The framework already promised this: §24.4 says a short declared on a member is an ordinary flag short, the refusal for a short on the selector itself says "declare the short on a member", and the short-claim table, the help renderer and the two sibling-scope short guards already read a member's short. Only Go could produce one. The short now goes on the declaration each member shape puts its electing flag on -- choice({value: {carrier, help, short}}) for a payload-carrying member, choice({help, short}) for a payload-less one -- and declaring it anywhere else is a compile error where the type system can see it and a registration error where it cannot.
+
+</details>
+
+### Fixes
+
+- [ts-strictcli] **A member-spelled choice's member flag can declare a short.** `choice({value: {carrier, help, short}})` declares a payload-carrying member's short and `choice({help, short})` a payload-less one's, so converting an at-most-one group of flags into a member-spelled selector no longer drops every short those flags had. The short elects at every door argv supports, renders beside its member in `--help`, publishes on the payload's schema entry, and is claimed against every simultaneously live scope.
+
 ## 0.40.0
 
 The declaration-regime release: mandatory presence declarations, scoped selectors replacing mutex groups, real-JSON-Schema value fragments (schema v2), the co-occurrence constraint system, and the update-command construct.

typescript/package-lock.json

@@ -1,6 +1,6 @@
 {
 	"name": "strictcli",
-	"version": "0.40.0",
+	"version": "0.40.1",
 	"type": "module",
 	"description": "TS-native strict CLI framework - declare everything, infer nothing",
 	"engines": {