Applications can construct native PromptKit request and prepared-report values
in ckprompt callbacks. An application upgrading from the selected v0.21.0
dependency can have positional literals for exported structs whose fields
changed in v0.22.0 or v0.23.0. Those literals can fail compilation after the
dependency upgrade. The local release note and consumer guide omit the needed
migration action, and the linked patch-release guidance omits the intervening
minor-release changes.
A scratch consumer containing a positional `promptkit.PreparedRun` literal
compiled successfully using the pre-adoption module selections at `d107b12`.
The identical source failed with the candidate selections, reporting shifted
field types and too few literal values. `PreparedRun` gained `ParentRunID` as
its first field. Upstream's v0.22.0 and v0.23.0 notes explicitly describe the
exported struct additions and the switch to keyed literals. [PromptKit v0.22.0 compatibility](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/74066167942fcf6f70c112359995739ec9789fa6/docs/releases/v0.22.0.md#efficiency-and-compatibility)
and [PromptKit v0.23.0 upgrade guidance](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/74066167942fcf6f70c112359995739ec9789fa6/docs/releases/v0.23.0.md#compatibility-and-upgrade).
### Expected behavior and remediation
Upgrade guidance should cover the full v0.21.0 → v0.23.1 dependency change.
Add a concise conditional instruction in the ckprompt release note for consumers
using positional literals of affected native structs to migrate those literals
to keyed fields. Link the intervening upstream compatibility guidance. Add a
short pointer from the consumer guide where it introduces the prepared candidate
and native request ownership, keeping upstream type details with PromptKit.
Validate the revised links and wording against the selected source. This
remediation consists of documentation changes. Existing runtime behavior and
regression coverage already satisfy the reviewed adoption paths.