Record completion of the Promptkit migration
This commit is contained in:
@@ -2,7 +2,28 @@
|
|||||||
|
|
||||||
## Status
|
## Status
|
||||||
|
|
||||||
Ready for implementation.
|
Complete as of 2026-07-28.
|
||||||
|
|
||||||
|
## Completion Summary
|
||||||
|
|
||||||
|
Promptkit's annotated `v0.1.0` tag remains published at commit
|
||||||
|
`9e68a2bbf779545995270c47842048a3bc6c85dc`. 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)
|
||||||
|
succeeded with release notes matching the checked-in source, exactly the Linux
|
||||||
|
`amd64` and `arm64` binaries, and verified SHA-256 checksums.
|
||||||
|
|
||||||
|
Fresh remote module resolution and independent repository validation passed
|
||||||
|
without sibling-repository state. The downloaded `amd64` binary completed an
|
||||||
|
offline render; its existing command interface treated `--help` as an unknown
|
||||||
|
command and printed usage. The `arm64` binary could not be executed on the
|
||||||
|
`amd64` host, so its checksum, format, and target architecture were verified.
|
||||||
|
Notarius at commit `de046a8f13e227676d79c3aa3b685b049902038d`
|
||||||
|
remains migrated and verified, and no other downstream Go consumer was
|
||||||
|
identified. All three repositories were clean and synchronized after
|
||||||
|
validation.
|
||||||
|
|
||||||
This plan implements the target state and policy decisions in
|
This plan implements the target state and policy decisions in
|
||||||
[Step 9](step9.md). Execute the stages in order. A later stage may begin only
|
[Step 9](step9.md). Execute the stages in order. A later stage may begin only
|
||||||
|
|||||||
@@ -2,8 +2,9 @@
|
|||||||
|
|
||||||
## Status
|
## Status
|
||||||
|
|
||||||
Accepted plan. Steps 1 through 8 are complete. Step 9 remains proposed and is
|
Complete as of 2026-07-28. All nine steps and the overall Promptkit migration
|
||||||
not yet implemented.
|
are complete. The final release and validation evidence is recorded in
|
||||||
|
[Step 9](step9.md).
|
||||||
|
|
||||||
## Objective
|
## Objective
|
||||||
|
|
||||||
@@ -315,6 +316,13 @@ Complete the coordinated project transition:
|
|||||||
documentation has distinct and accurate ownership, and the migration status of
|
documentation has distinct and accurate ownership, and the migration status of
|
||||||
all identified downstream consumers is recorded.
|
all identified downstream consumers is recorded.
|
||||||
|
|
||||||
|
**Gate status:** Complete as of 2026-07-28. Promptkit `v0.1.0` remains
|
||||||
|
published from commit `9e68a2bbf779545995270c47842048a3bc6c85dc`.
|
||||||
|
Scriptorium `v0.12.0` was published from independently validated commit
|
||||||
|
`2f42bdde3957563cb9b7a1e27fdd4ab2516f621a` with the intended hosted release
|
||||||
|
notes, Linux `amd64` and `arm64` binaries, and SHA-256 checksums. Notarius, the
|
||||||
|
only identified downstream Go consumer, remains migrated and verified.
|
||||||
|
|
||||||
## Cross-Cutting Constraints
|
## Cross-Cutting Constraints
|
||||||
|
|
||||||
- Preserve the invariant that execution orchestration remains narrow and
|
- Preserve the invariant that execution orchestration remains narrow and
|
||||||
|
|||||||
@@ -2,9 +2,35 @@
|
|||||||
|
|
||||||
## Status
|
## Status
|
||||||
|
|
||||||
Proposed. Steps 1 through 8 of the
|
Complete as of 2026-07-28. All steps of the
|
||||||
[migration roadmap](migration.md) are complete. This is the final migration
|
[migration roadmap](migration.md) are complete.
|
||||||
gate.
|
|
||||||
|
## 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
|
## Purpose
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user