eric/scriptorium
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 9 Wiki Activity

Complete Promptkit adoption handoff and verification record

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-26 15:56:31 +00:00
parent aca50de9bf
commit e177d7c71d
2 changed files with 42 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/roadmap/upgrade-kit.md
View File

@@ -2,7 +2,10 @@
## Status And Intent
Accepted feature direction, recorded on 2026-09-26; implementation is pending.
Accepted feature direction, recorded on 2026-09-26. Implementation is complete
to the pre-release boundary; version selection, release-candidate validation,
and publication remain separate release preparation. The baseline descriptions
below record the state when this roadmap was written, not current behavior.
Upgrade directly from Promptkit v0.9.0 to v0.11.0, including the intervening
v0.10.0 catalog transition. This document defines the desired end state and
the changes from the current baseline. The [implementation plan](implementation.md)
@@ -259,11 +262,12 @@ boundaries.
of the new public identities and context outcomes.
- The licensing/distribution approach is resolved before upgraded binary
distribution, and any required materials are included in the chosen workflow.
- Affected contracts, examples, migration guidance, and release notes match
- Affected current contracts, examples, and migration guidance match
implemented behavior. Relevant tests remain offline and credential-free,
and normal development and release validation pass.
and normal development validation passes. Release-candidate validation and
the version-matched note remain release preparation.
Concrete interface decisions and the remaining distribution question are recorded
in the [implementation plan](implementation.md). They do not expand the product
into conversations, follow-up messages, application-owned semantic retry loops,
prepared-handle coordination, or multi-step workflows.
Concrete interface decisions and the selected distribution approach are recorded
in the completed [implementation plan](implementation.md). They do not expand
the product into conversations, follow-up messages, application-owned semantic
retry loops, prepared-handle coordination, or multi-step workflows.