Adopt PromptKit timeout fix and complete verification

This commit is contained in:
2026-11-19 14:39:10 +00:00
parent 78bcf86619
commit c5e54edaa5
20 changed files with 92 additions and 57 deletions

View File

@@ -7,6 +7,11 @@ repository policies, and [ADR 0004](../adr/0004-definition-boundary.md) and
[ADR 0005](../adr/0005-configkit-boundary.md). Use the pinned upstream
references in the feature roadmap, not either sibling checkout's moving HEAD.
For final verification, the selected PromptKit release is v0.23.3 at commit
`804a4d32b23aa2e7973400bb0a322a7016574c9f`. The maintainer approved this
patch update after v0.23.2 exposed an in-flight HTTP timeout attribution bug;
it supersedes the earlier PromptKit pin below. ConfigKit remains v1.2.1.
Execute these stages in order as one sprint. Intermediate stages may leave
unresolved imports, outdated fixtures, or failing tests that a later stage
explicitly addresses. Do not add shims or split the migration into separately
@@ -339,6 +344,8 @@ scaffolding, or conversation and coordination features.
## Stage 8: Verify the complete cutover
**Status: Complete.**
1. Use the selected Go 1.27.4 toolchain. Finish `GOWORK=off go mod tidy`
after all imports and fixtures are in place and confirm
`GOWORK=off go mod tidy -diff` is empty. Inspect `go list -m all` for

View File

@@ -2,8 +2,12 @@
## Status And Scope
Accepted direction; not yet implemented. Upgrade the existing Scriptorium
product in one native cutover. Use the released PromptKit and ConfigKit APIs
Implemented. The original v0.23.2 target below was superseded for final
verification by PromptKit v0.23.3 at commit
`804a4d32b23aa2e7973400bb0a322a7016574c9f`, with the maintainer's approval,
to correct in-flight HTTP operation-timeout attribution. ConfigKit remains
v1.2.1. This roadmap upgrades the existing Scriptorium product in one native
cutover. Use the released PromptKit and ConfigKit APIs
for framework and configuration mechanisms that they already own. Provide
migration guidance for configuration, definitions, and CLI usage, not a
second application schema, a legacy definition reader, or compatibility