reproduction. Its observed application versions include PromptKit v0.23.0.
The constructor wrapper responsible for that behavior also exists in the
currently selected v0.21.0.
## Upstream changes and integration scope
PromptKit v0.23.1 resolves the constructor wrapping defect at source commit
`74066167942fcf6f70c112359995739ec9789fa6`. The wrapper exposes the original
cause through a single unwrap and recognizes `ErrInvalidConfig` through
`errors.Is`. Typed ConfigKit errors remain reachable through `errors.As`.
Genuine joined causes remain available for classification. The adoption can
therefore use ckconfig's existing classifier. [Upstream constructor](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/74066167942fcf6f70c112359995739ec9789fa6/engine.go)
and [error implementation](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/74066167942fcf6f70c112359995739ec9789fa6/errors.go).
The intervening releases add opt-in conversation capture, continuation,
coordination, execution-group summaries, operation timeouts, and prepared-run
notifications. Applications own engine setup, native request construction, and
execution. Existing native request builders provide the integration point for
application-selected request capabilities. Prepared reports continue to expose
upstream fields through the existing report path. Review those additive shapes
for compatibility during the upgrade. [Upstream consumer guidance](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/74066167942fcf6f70c112359995739ec9789fa6/docs/consumers/pkg-promptkit.md).
Keep the adoption focused on existing CommandKit operator tasks and the
constructor-error fix. Additional CLI capabilities remain subject to the
operator needs recorded in [future work](future.md). Preparation and validation
documentation should describe the upstream operations actually invoked,
including their handling of contexts and request options.