Record completion of the Promptkit migration

This commit is contained in:
2026-07-28 20:03:11 +00:00
parent 2f42bdde39
commit 1f08a1a94c
3 changed files with 61 additions and 6 deletions

View File

@@ -2,9 +2,35 @@
## Status
Proposed. Steps 1 through 8 of the
[migration roadmap](migration.md) are complete. This is the final migration
gate.
Complete as of 2026-07-28. All steps of the
[migration roadmap](migration.md) are complete.
## Completion Record
- Promptkit's annotated `v0.1.0` tag remains published at commit
`9e68a2bbf779545995270c47842048a3bc6c85dc`; its independent documented
validation and fresh remote module resolution passed.
- Scriptorium's annotated `v0.12.0` tag object
`734632371773bb7620ce9f18e79ae179a2a2b44b` resolves to independently
validated commit `2f42bdde3957563cb9b7a1e27fdd4ab2516f621a`.
- The
[hosted release](https://gitea.maximumdirect.net/eric/scriptorium/releases/tag/v0.12.0)
completed successfully with the checked-in release notes, exactly the Linux
`amd64` and `arm64` binaries, and `SHA256SUMS`. Both checksums and binary
architectures were verified.
- Fresh remote module queries resolved both release tags to their expected
commits and confirmed that Scriptorium selects Promptkit `v0.1.0`, without a
workspace, replacement, vendored sibling source, or local module cache.
- The downloaded Linux `amd64` binary completed an offline render smoke test.
Its existing command interface has no `--help` command, so that invocation
returned the expected unknown-command usage response. The Linux `arm64`
binary was not executed on the `amd64` validation host; its checksum, format,
and target architecture were verified.
- Notarius at commit `de046a8f13e227676d79c3aa3b685b049902038d`
remains migrated to Promptkit and passed its full test suite. No other
downstream consumer of the former Scriptorium Go package was identified.
- Promptkit, Scriptorium, and Notarius were clean and synchronized with their
remote main branches after validation.
## Purpose