Files
scriptorium/docs/roadmap/implementation.md

3.4 KiB

Step 6 Implementation Completion Record

Status

Completed on 2026-07-28.

This record closes Migration Step 6: Extract And Stabilize Promptkit. It replaces the temporary implementation checklist now that every extraction, documentation, validation, and publication gate has passed.

Recorded Commits And Release

  • Scriptorium extraction source: c7263ab2a8e58f7fb97280082d327a820c7cece7
  • Accepted Promptkit release commit: 9e68a2bbf779545995270c47842048a3bc6c85dc
  • Published annotated Promptkit tag: v0.1.0
  • Verified remote tag object: b4495c2b294967049bb363f20d5607b1f2a36f49

All Promptkit extraction commits use plain-English messages and remain in the Promptkit repository. Scriptorium received no framework implementation or dependency change during this work.

Completed Work

Promptkit received and characterized:

  • the application-neutral domain, defaults, and file-catalog foundation;
  • prompt and profile sources, the embedded built-in catalog, and rendering;
  • ordinary artifact reading and output validation;
  • the provider-neutral model-client boundary and OpenAI-compatible client;
  • preparation and execution orchestration;
  • the supported root facade, values, extension points, error mapping, copying, and redacted formatting;
  • recursive dependency-boundary protection;
  • framework contract fixtures and deterministic offline tests;
  • canonical consumer, format, integration, internal, development, testing, architecture, and release documentation; and
  • a maintained offline Prepare example.

Application configuration, CLI and HTTP adapters, transport policy, restricted artifact access, deployment behavior, and executable concerns remained in Scriptorium.

Validation Evidence

The exact Promptkit release commit passed from a fresh detached checkout with GOWORK=off:

  • module tidiness, ordinary tests, race-enabled tests, vet, and build;
  • the maintained offline example;
  • Go formatting, whitespace, and clean-tree checks;
  • module and package identity checks;
  • absence of Scriptorium module and package dependencies;
  • absence of workspaces and replacements;
  • the recursive architecture guard;
  • public Go inventory and sentinel-error comparison;
  • all maintained local links;
  • exact comparison of all 24 built-in assets with the source snapshot; and
  • preservation of GPLv3 and Promptkit-specific project notices.

Before publication, unchanged Scriptorium independently passed all tests, vet, the cmd/scriptorium build, and whitespace checks with no Promptkit dependency or replacement.

Promptkit's main branch was published before tagging. The annotated v0.1.0 tag was inspected, pushed, and remotely verified to resolve to the accepted commit. A clean temporary consumer module then downloaded exactly v0.1.0, built and ran a minimal root-package program, and verified its module graph without a local replacement.

No binary or hosting-provider-specific release artifact was created.

Migration Handoff

Scriptorium remains deliberately unchanged at its pre-cutover application boundary. Migration Step 7 is the next authorized work: adopt the tagged Promptkit module and remove the duplicated framework while retaining Scriptorium-owned executable and transport behavior.

The Step 6 completion record owns the completed result and retained boundary. The main migration roadmap owns all later work.