Align the COPYRIGHT and LICENSE documents with the house standard

.gitignore

@@ -1,6 +1,5 @@
 # ---> Codex
 .codex
-AGENTS.md
 
 # ---> Go
 # If you prefer the allow list template instead of the deny list, see community template:
@@ -57,6 +56,8 @@ mono_crash.*
 [Dd]ebugPublic/
 [Rr]elease/
 [Rr]eleases/
+!docs/releases/
+!docs/releases/*.md
 x64/
 x86/
 [Ww][Ii][Nn]32/
@@ -434,4 +435,3 @@ FodyWeavers.xsd
 
 # JetBrains Rider
 *.sln.iml
-

.woodpecker/release.yml

@@ -11,9 +11,16 @@ steps:
         version="$CI_COMMIT_TAG"
         dist="dist"
         pkg="gitea.maximumdirect.net/eric/scriptorium/cmd/scriptorium"
+        notes="docs/releases/$version.md"
+
+        if [ ! -f "$notes" ]; then
+          printf 'release notes not found: %s\n' "$notes" >&2
+          exit 1
+        fi
 
         rm -rf "$dist"
         mkdir -p "$dist"
+        cp "$notes" "$dist/RELEASE_NOTES.md"
 
         build_binary() {
           goos="$1"
@@ -22,16 +29,12 @@ steps:
           output="$dist/scriptorium-$version-$goos-$goarch$suffix"
 
           CGO_ENABLED=0 GOOS="$goos" GOARCH="$goarch" \
-            go build -trimpath -ldflags "-s -w -X gitea.maximumdirect.net/eric/scriptorium/internal/buildinfo.Version=$version" \
+            go build -trimpath -ldflags "-s -w" \
             -o "$output" "$pkg"
         }
 
         build_binary linux amd64 ""
         build_binary linux arm64 ""
-        build_binary darwin amd64 ""
-        build_binary darwin arm64 ""
-        build_binary windows amd64 ".exe"
-        build_binary windows arm64 ".exe"
 
   - name: publish-release
     image: woodpeckerci/plugin-release
@@ -42,6 +45,7 @@ steps:
         from_secret: GITEA_RELEASE_TOKEN
       files:
         - dist/scriptorium-*
+      note: dist/RELEASE_NOTES.md
       checksum: sha256
       checksum-file: SHA256SUMS
       checksum-flatten: true

AGENTS.md

@@ -0,0 +1,4 @@
+Please review `docs/development.md` for initial orientation in this repository and follow its task-specific reading guide.
+
+Review and follow `docs/policy/agents.md` before recommending, planning, or
+implementing changes to this repository.

COPYRIGHT

@@ -0,0 +1,19 @@
+Scriptorium
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: GPL-3.0-or-later
+
+Scriptorium is free software: you can redistribute it and/or modify it
+under the terms of the GNU Lesser General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+The GNU General Public License version 3 is provided in LICENSE.
+
+Scriptorium is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU Lesser General Public License for more details.
+
+Third-party code and assets are subject to their respective license terms.

LICENSE

@@ -1,11 +1,674 @@
-Copyright (c) 2026 eric. 
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
 
-Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
 
-1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+                            Preamble
 
-2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
 
-3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
 
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

README.md

@@ -1,449 +1,57 @@
-# scriptorium
+# Scriptorium
 
-Scriptorium is a generic prompt execution engine.
+Scriptorium is a prompt-execution application with a command-line interface and
+an HTTP service. It prepares prompt requests, runs them against
+OpenAI-compatible model endpoints, and returns generated output with validation
+metadata.
 
-It takes:
-- a prompt definition
-- a selected or default execution profile
-- named input artifacts
-- template variables
-- optional runtime overrides
+The application uses
+[Promptkit v0.11.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/)
+for prompt, profile, schema, preparation, generation, and validation behavior.
+Scriptorium owns executable configuration, CLI and HTTP mapping, process
+behavior, output presentation, and HTTP artifact-containment policy.
 
-It returns:
-- for `run`: generated artifact, validation result, metadata
-- for `render`: prepared/rendered prompt data (no model output)
+## Quickstart
 
-## Prompt vs Profile
+From the repository root:
 
-Scriptorium separates **what** to do (Prompt) from **how** to do it (Profile).
-
-### Prompt Definition
-Defines the task logic and output contract.
-- Task description and version.
-- Message templates (system, user, etc.).
-- Required and optional input artifacts.
-- Output format and validation rules.
-- Repair settings for structured output.
-- Optional `default_profile` for convenience.
-
-### Execution Profile
-Defines the runtime environment and model settings.
-- LLM endpoint (URL).
-- Model name.
-- Generation parameters: `temperature`, `max_tokens`, `top_p`.
-- Runtime settings: `timeout`, `reasoning_effort`.
-- API key source via `api_key_env`.
-
-Callers can explicitly provide a `profile_id` to override the prompt's `default_profile`.
-
-## Precedence
-
-Scriptorium uses two precedence layers:
-
-### Application Configuration Precedence
-
-For application-level adapter settings (for example prompt/profile/schema directories, server address, and render output default), precedence is:
-
-1. **CLI Flags**
-2. **`config.yml`**
-3. **Built-in application defaults**
-
-Application config loading behavior:
-- Default config path: `/etc/scriptorium/config.yml`
-- Override path: `--config <PATH>` (supported by `run`, `render`, and `serve`)
-- If `--config` is provided, the file must exist and be valid.
-- If `--config` is omitted, missing `/etc/scriptorium/config.yml` is allowed.
-
-### Runtime Model Precedence
-
-When resolving runtime model settings, Scriptorium follows this precedence model (highest to lowest):
-
-1. **Runtime Overrides**: Provided via CLI flags or HTTP request `model` object.
-2. **Execution Profile**: Settings defined in the selected profile.
-3. **Application Defaults**: Built-in fallback values.
-
-### Profile Selection Logic
-The engine determines which profile to use in this order:
-1. Explicit `profile_id` (via `--profile` or HTTP request).
-2. The `default_profile` named in the Prompt Definition.
-3. Error: If neither is provided and no default exists.
-
-## API Key Policy
-
-To ensure security, Scriptorium does not support raw API keys in configuration files, CLI arguments, or HTTP requests.
-
-- **`api_key_env`**: Profiles and overrides specify the name of an environment variable (e.g., `SCRIPTORIUM_API_KEY`).
-- **Runtime Resolution**: The value of the environment variable is read directly from the process environment at runtime.
-- **Zero Leakage**: API key values are never included in metadata, logs, or response bodies.
-
-## CLI Usage
-
-Available CLI commands:
-- `scriptorium run`
-- `scriptorium render`
-- `scriptorium serve`
-
-All commands accept `--config <PATH>`.
-
-`prompt_dir` and `profile_dir` may be supplied by CLI flags or `config.yml`:
-- `--prompt-dir` or `config.yml` `prompt_dir`
-- `--profile-dir` or `config.yml` `profile_dir`
-
-`schema_dir` and `serve` `addr` may also be supplied by `config.yml` where applicable:
-- `--schema-dir` or `config.yml` `schema_dir`
-- `--addr` or `config.yml` `server.addr`
-
-### `scriptorium run`
-
-Runs a single prompt execution.
-
-**Required Flags:**
-- `--prompt`: The prompt ID to execute.
-- `--input`: Input mapping `name=path` (repeatable).
-
-**Required Effective Settings:**
-- Prompt directory: `--prompt-dir` or `config.yml` `prompt_dir`
-- Profile directory: `--profile-dir` or `config.yml` `profile_dir`
-
-**Optional Flags:**
-- `--config`: Application config file path. Default discovery path is `/etc/scriptorium/config.yml`.
-- `--prompt-dir`: Override prompt directory from config.
-- `--profile-dir`: Override profile directory from config.
-- `--profile`: Override the prompt's default profile.
-- `--var`: Template variable `name=value` (repeatable).
-- `--out`: Write output to a file instead of stdout.
-- `--llm-base-url`: Override endpoint.
-- `--model`: Override model name.
-- `--api-key-env`: Override API key environment variable name.
-- `--temperature`: Override temperature.
-- `--max-tokens`: Override max tokens.
-- `--top-p`: Override top_p.
-- `--timeout`: Override request timeout (e.g., `30s`, `1m`).
-- `--schema-dir`: Base directory for validation schemas.
-
-**Examples:**
-
-Using `config.yml` for prompt/profile directories:
 ```bash
-scriptorium run \
-  --prompt generic.markdown_summary \
-  --input transcript=./examples/fixtures/transcript.md
-```
-
-Overriding config directories explicitly:
-```bash
-scriptorium run \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --input transcript=./examples/fixtures/transcript.md
-```
-
-Overriding the profile:
-```bash
-scriptorium run \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --profile local-quality \
-  --input transcript=./examples/fixtures/transcript.md
-```
-
-Overriding model and runtime values:
-```bash
-scriptorium run \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --model gpt-4o \
-  --temperature 0.7 \
-  --input transcript=./examples/fixtures/transcript.md
-```
-
-Using a local OpenAI-compatible vLLM endpoint:
-```bash
-scriptorium run \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --llm-base-url http://localhost:8000/v1 \
-  --model meta-llama-3-8b \
-  --input transcript=./examples/fixtures/transcript.md
-```
-
-### `scriptorium render`
-
-Prepares and renders a prompt without calling the LLM.
-
-`render` uses the same prompt/profile/input/variable/runtime override resolution as `run`:
-- Profile selection precedence: `--profile` -> prompt `default_profile` -> error.
-- Runtime precedence: CLI runtime overrides -> selected profile -> built-in defaults.
-
-`render` is useful for debugging:
-- prompt template rendering
-- input mappings
-- selected profile behavior
-- runtime override behavior
-
-`render` does not:
-- call the LLM
-- validate model output
-- perform repair
-- expose resolved API key values
-
-It may include `api_key_env` names where relevant.
-
-**Required Flags:**
-- `--prompt`: The prompt ID to render.
-- `--input`: Input mapping `name=path` (repeatable).
-
-**Required Effective Settings:**
-- Prompt directory: `--prompt-dir` or `config.yml` `prompt_dir`
-- Profile directory: `--profile-dir` or `config.yml` `profile_dir`
-
-**Optional Flags:**
-- `--config`: Application config file path. Default discovery path is `/etc/scriptorium/config.yml`.
-- `--prompt-dir`: Override prompt directory from config.
-- `--profile-dir`: Override profile directory from config.
-- `--profile`: Override the prompt's default profile.
-- `--var`: Template variable `name=value` (repeatable).
-- `--out`: Write output to a file instead of stdout.
-- `--format`: Render output format (`text` or `json`). Default: `text`.
-- `--llm-base-url`: Runtime override for endpoint.
-- `--model`: Runtime override for model name.
-- `--api-key-env`: Runtime override for API key environment variable name.
-- `--temperature`: Runtime override for temperature.
-- `--max-tokens`: Runtime override for max tokens.
-- `--top-p`: Runtime override for top_p.
-- `--timeout`: Runtime override for timeout (e.g., `30s`, `1m`).
-
-**Render Output Formats:**
-- `text`: Human-readable output (default).
-- `json`: Machine-readable structured output.
-
-Render formatting is modular; additional output formats can be added later without changing prepare/run core logic.
-
-**Examples:**
-
-Default text output using `config.yml` directories:
-```bash
-scriptorium render \
-  --prompt generic.markdown_summary \
-  --input transcript=./examples/fixtures/transcript.md
-```
-
-Explicit config path:
-```bash
-scriptorium render \
+go run ./cmd/scriptorium render \
   --config ./examples/config.yml \
   --prompt generic.markdown_summary \
-  --input transcript=./examples/fixtures/transcript.md
-```
-
-Explicit directory overrides:
-```bash
-scriptorium render \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --input transcript=./examples/fixtures/transcript.md
-```
-
-Explicit JSON output:
-```bash
-scriptorium render \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
   --input transcript=./examples/fixtures/transcript.md \
+  --input glossary=./examples/fixtures/glossary.yml \
   --format json
 ```
 
-Using prompt `default_profile` (omit `--profile`):
-```bash
-scriptorium render \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --input transcript=./examples/fixtures/transcript.md
-```
+This renders the prepared prompt and effective runtime settings without calling
+a model. For complete invocation and output behavior, see the
+[CLI reference](docs/cli.md).
 
-Overriding profile selection:
-```bash
-scriptorium render \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --profile local-quality \
-  --input transcript=./examples/fixtures/transcript.md
-```
+## Documentation
 
-Overriding runtime settings:
-```bash
-scriptorium render \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --input transcript=./examples/fixtures/transcript.md \
-  --llm-base-url http://localhost:8000/v1 \
-  --model gpt-4o-mini \
-  --temperature 0.2 \
-  --max-tokens 800 \
-  --top-p 1.0 \
-  --timeout 45s
-```
-
-Writing rendered output to a file:
-```bash
-scriptorium render \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --prompt generic.markdown_summary \
-  --input transcript=./examples/fixtures/transcript.md \
-  --format text \
-  --out ./rendered_prompt.txt
-```
-
-### `scriptorium serve`
-
-Starts the HTTP API.
-
-**Required Effective Settings:**
-- Prompt directory: `--prompt-dir` or `config.yml` `prompt_dir`
-- Profile directory: `--profile-dir` or `config.yml` `profile_dir`
-
-**Optional Flags:**
-- `--config`: Application config file path. Default discovery path is `/etc/scriptorium/config.yml`.
-- `--addr`: Listen address (default `:8080`).
-- `--schema-dir`: Base directory for validation schemas.
-
-**Examples:**
-
-Using `config.yml`:
-```bash
-scriptorium serve
-```
-
-Overriding config for local use:
-```bash
-scriptorium serve \
-  --prompt-dir ./prompts \
-  --profile-dir ./profiles \
-  --addr :9090
-```
-
-## HTTP API
-
-### `POST /v1/runs`
-
-Executes a prompt. No built-in authentication is provided; deploy behind a trusted gateway.
-
-**Request Body:**
-```json
-{
-  "prompt_id": "generic.structured_events",
-  "profile_id": "local-quality",
-  "include_raw_output": false,
-  "inputs": {
-    "transcript": {"type": "file", "uri": "./examples/fixtures/transcript.md"}
-  },
-  "vars": {
-    "session_date": "2026-05-04"
-  },
-  "model": {
-    "endpoint": "http://localhost:8000/v1",
-    "model": "gpt-4o-mini",
-    "temperature": 0.0
-  }
-}
-```
-
-`profile_id` is optional. If omitted, Scriptorium uses the prompt's `default_profile`. If neither is available, the run fails.
-
-**Response:**
-Returns a `200 OK` with the generated artifact, validation results, and metadata including the `prompt_id` and the `selected_profile_id`.
-
-**Validation Failures:**
-If the model output fails validation (e.g., invalid JSON), the API returns `200 OK` with `validation.status = "failed"`.
-
-**Raw Output Exposure:**
-- `raw_model_output` is omitted by default.
-- Set `include_raw_output: true` in the request to include it in the response.
-- Raw output is preserved internally in run results regardless of HTTP exposure.
-
-## Prompt Definition Authoring
-
-Prompts are defined in YAML.
-
-### Canonical Shape
-```yaml
-id: generic.structured_events
-version: "1.0.0"
-description: "Extracts structured events from a transcript"
-default_profile: local-quality
-
-inputs:
-  - name: transcript
-    required: true
-    content_type: text/markdown
-    description: "The raw session transcript"
-  - name: glossary
-    required: false
-    content_type: application/yaml
-    description: "Optional glossary terms"
-
-messages:
-  - role: system
-    content: "You are a helpful assistant."
-  - role: user
-    content_file: messages/extract_events.tmpl
-
-output:
-  format: json
-  validation_mode: json_schema
-  schema_path: structured_events.schema.json
-  repair_attempts: 2
-```
-
-**Key Features:**
-- **Inline vs File**: Use `content` for short prompts or `content_file` for larger templates. Exactly one must be set per message.
-- **Path Resolution**: `content_file` paths are resolved relative to the prompt YAML file.
-- **Inputs**: Mark inputs as `required` to ensure the runner fails early if they are missing.
-- **Input Metadata**: `content_type` is currently descriptive metadata and not enforced yet.
-- **Validation**: Support `none`, `basic`, `json`, and `json_schema`.
-- **Repair**: `repair_attempts` enables bounded retries to fix structured output.
-
-## Execution Profile Authoring
-
-Profiles are defined in YAML.
-
-### Canonical Shape
-```yaml
-id: local-quality
-endpoint: http://localhost:8000/v1
-model: gpt-4o
-temperature: 0.0
-max_tokens: 4096
-top_p: 1.0
-timeout_seconds: 300
-reasoning_effort: high
-api_key_env: SCRIPTORIUM_API_KEY
-```
-
-**Constraints:**
-- **No Raw Keys**: Do not include actual API keys. Only specify the environment variable name in `api_key_env`.
-- **Local Profiles**: For local endpoints that don't require auth, `api_key_env` can be omitted.
+- [CLI reference](docs/cli.md)
+- [Configuration reference](docs/config.md)
+- [Application configuration inspection](docs/cli.md#application-configuration-inspection)
+- [HTTP API reference](docs/api.md)
+- [Operations guide](docs/operations.md)
+- [Consumer integration overview](docs/consumers/api.md)
+- [Migration from the former Go package](docs/consumers/migrating-to-promptkit.md)
+- [Subprocess integration](docs/integrations/subprocess.md)
+- [Architecture policy](docs/policy/architecture.md)
+- [Promptkit framework formats](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md)
+- [Promptkit Go consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md)
 
 ## Examples
 
-- **Prompt Definitions**: `prompts/`
-- **Execution Profiles**: `profiles/`
-- **Schemas**: `schemas/`
-- **Fixtures**: `examples/fixtures/`
+- [Minimal configuration](examples/config.yml) and
+  [complete configuration](examples/config.full.yml), plus a
+  [composed import/overlay example](examples/config.composed.yml)
+- [Prompt definitions](examples/prompts/), [execution profiles](examples/profiles/),
+  [schemas](examples/schemas/), and [synthetic input fixtures](examples/fixtures/)
+- [Render script](examples/render-markdown-summary.sh)
+- [HTTP request](examples/http-run.json)
 
-## Build and Test
+Scriptorium is licensed under the [BSD 3-Clause License](LICENSE).
 
-```bash
-go build -o scriptorium ./cmd/scriptorium
-go test ./...
-```
+[Open Source attribution notices](docs/oss/attribution.md) are available.

architecture.md

@@ -1,483 +0,0 @@
-# Scriptorium Architecture
-
-## 1. Purpose and Non-Goals
-
-Scriptorium is a prompt-definition execution engine.
-
-It accepts named input artifacts, renders prompt templates, calls an LLM, validates output, optionally performs bounded structured-output repair, and returns an artifact with metadata.
-
-Scriptorium also supports rendering/preparing a prompt without calling an LLM. This allows users to inspect the fully rendered prompt messages and effective runtime settings before executing a run.
-
-Scriptorium is not an orchestrator. It must not own transcription, transcript merge/polish steps, notifications, or cross-step workflow control.
-
-For the motivating D&D workflow:
-- Narratio orchestrates.
-- WhisperX transcribes.
-- Seriatim merges transcripts.
-- Audita polishes transcripts.
-- Scriptorium generates final artifacts from prepared inputs.
-
-Core Go code remains generic.
-
-## 2. Current Architecture
-
-Scriptorium uses a ports-and-adapters architecture to decouple the core execution logic from external dependencies.
-
-### Package Responsibilities
-
-- `cmd/scriptorium`: Binary entrypoint for CLI and HTTP server.
-- `internal/domain`: Core domain contracts, including `PromptDefinition`, `ExecutionProfile`, `PreparedRun`, `RunResult`, and related metadata.
-- `internal/usecase`: `Runner` use case logic, including prompt preparation, profile selection, runtime override resolution, full run execution, validation, and bounded repair.
-- `internal/config`: Application-level config model/loader for adapter settings (for example prompt/profile/schema directories, server address, and render format default).
-- `internal/promptdef`: Repository for loading and validating Prompt Definitions from the filesystem.
-- `internal/profile`: Repository for loading Execution Profiles from the filesystem.
-- `internal/artifact`: Input artifact resolution (`inline`, `file`).
-- `internal/prompt`: Template rendering via Go templates.
-- `internal/llm`: Provider-neutral client interface and OpenAI-compatible HTTP adapter.
-- `internal/validate`: Output validation implementation (`none/basic/json/json_schema`).
-- `internal/adapter/cli`: CLI flag parsing, command dispatch, and output handling.
-- `internal/adapter/http`: HTTP request/response mapping.
-- `internal/format` or equivalent: Formatting of prepared/rendered prompt output for CLI or other adapters, if formatting grows beyond simple CLI-local helpers.
-
-Exact package names may evolve, but the architectural boundaries should remain stable.
-
-### Application Configuration
-
-`config.yml` is adapter/application setup, not domain logic.
-
-Application config is intended for application-level settings such as:
-- `prompt_dir`
-- `profile_dir`
-- `schema_dir`
-- `server.addr`
-- `defaults.render_format`
-
-Application config precedence is:
-1. CLI flags
-2. `config.yml`
-3. Built-in application defaults
-
-Runtime model settings are intentionally separate:
-- Execution profiles and runtime overrides continue to own endpoint/model/runtime behavior.
-- `config.yml` does not replace execution profiles.
-
-The core use case (`Runner.Prepare`/`Runner.Run`) does not need to know whether adapter-level settings came from CLI flags or `config.yml`; it receives resolved dependencies and requests from adapters.
-
-## 3. Core Execution Model
-
-Scriptorium has two closely related execution paths:
-
-1. Prepare/render path.
-2. Full run path.
-
-The full run path should reuse the prepare path rather than duplicating its logic.
-
-### 3.1 Prepare / Render Data Flow
-
-The prepare path should be represented in the use case layer, preferably as `Runner.Prepare(ctx, RunRequest)` or an equivalent method.
-
-It executes all pre-LLM work:
-
-1. **Validate Request**: Ensure the request includes a prompt ID and all minimum required fields.
-2. **Load Prompt Definition**: Retrieve the `PromptDefinition` by ID from the prompt repository.
-3. **Select Profile**: Determine the `profile_id` using this precedence:
-   - Explicit `profile_id` in `RunRequest`.
-   - `default_profile` specified in the `PromptDefinition`.
-   - Error if neither is available.
-4. **Load Execution Profile**: Retrieve the `ExecutionProfile` from the profile repository.
-5. **Resolve Runtime Overrides**: Merge settings based on precedence, highest to lowest:
-   - Runtime overrides from CLI flags or HTTP request `model` object.
-   - Execution Profile settings.
-   - Built-in application defaults.
-6. **Resolve Artifacts**: Load all named input artifacts defined in the request.
-7. **Render Prompt**: Apply template variables and input artifacts to the prompt templates.
-8. **Compute Metadata**: Compute hashes, selected profile ID, prompt ID/version, effective runtime settings, input hashes, rendered prompt hash, and timing information as appropriate.
-9. **Return PreparedRun**: Return a `PreparedRun` containing the rendered messages, effective runtime settings, resolved metadata, and input/prompt hashes.
-
-The prepare path must not call the LLM.
-
-The prepare path must not validate model output, because there is no model output.
-
-The prepare path must not perform structured-output repair, because repair only applies after model output exists.
-
-The prepare path should not resolve or expose raw API key values. It may include the selected `api_key_env` name in effective runtime settings or metadata, but never the environment variable value.
-
-### 3.2 Full Run Data Flow
-
-The `Runner.Run(ctx, RunRequest)` flow should reuse the prepare path:
-
-1. **Prepare**: Call the shared prepare flow to load the prompt, select the profile, resolve artifacts, render prompt messages, and compute pre-run metadata.
-2. **Call LLM**: Execute the generation request using the effective runtime settings from the prepared run.
-3. **Build Output Artifact**: Convert the model response into the configured output artifact.
-4. **Validate Output**:
-   - Validate the model output against the prompt definition's output contract.
-   - Validation content failures remain successful run results with `validation.status=failed`.
-   - Validator runtime/config errors are run errors.
-5. **Repair If Configured**:
-   - If structured validation fails and `repair_attempts > 0`, perform bounded repair attempts.
-   - Re-validate after each repair attempt.
-   - Repair loops must remain strictly bounded.
-6. **Return RunResult**: Produce a `RunResult` containing the final artifact, validation status, raw model output, usage information, and metadata.
-
-`Runner.Run` should not duplicate profile selection, artifact resolution, or prompt rendering logic that already exists in `Runner.Prepare`.
-
-## 4. Domain Model
-
-Key domain types:
-
-- `PromptDefinition`: Defines the "what" of the task: templates, inputs, output contract, validation settings, repair settings, and optional `default_profile`.
-- `ExecutionProfile`: Defines the "how" of execution: endpoint, model, generation parameters, timeout, reasoning effort, and `api_key_env`.
-- `RunRequest`: The intent to execute or prepare a prompt, including `prompt_id`, optional `profile_id`, inputs, variables, and optional runtime overrides.
-- `PreparedRun`: The result of the prepare/render phase. Contains rendered messages, effective runtime settings, selected profile ID, prompt metadata, input hashes, prompt hash, and other pre-LLM metadata.
-- `RunResult`: The result of a full run. Contains the generated `Artifact`, `ValidationResult`, raw model output, token usage, and `RunMetadata`.
-- `RunMetadata`: Detailed tracing information, including prompt ID/version, selected profile ID, effective model parameters, usage tokens, hashes, timestamps, validation status, and repair attempts where applicable.
-- `RenderedPrompt`: Provider-neutral rendered prompt structure.
-- `RenderedMessage`: Provider-neutral rendered message with role and content.
-- `ArtifactRef`: A reference to an input artifact, such as `file` or `inline`.
-- `Artifact`: Loaded artifact content with name, content type, body, source URI, size, and hash.
-- `ValidationResult`: Validation status and details for full runs.
-
-`PreparedRun` should be serializable for JSON output and should also be representable in a human-readable text format.
-
-## 5. Interfaces and Adapters
-
-### Primary Ports
-
-- `promptdef.Repository`: Lookup for prompt definitions.
-- `profile.Repository`: Lookup for execution profiles.
-- `artifact.Reader`: Loading of artifact content.
-- `prompt.Renderer`: Template rendering.
-- `llm.Client`: Model generation.
-- `validate.Validator`: Output validation.
-- `format.PreparedRunFormatter` or equivalent: Optional formatting abstraction for rendered/prepared output.
-
-### Current Adapters
-
-- **Repositories**: Filesystem YAML loaders for both prompts and profiles.
-- **Artifact Reader**: Composite reader supporting `file` and `inline`.
-- **Prompt Renderer**: Go templates with a custom `input` helper.
-- **LLM Client**: OpenAI-compatible `/chat/completions` over HTTP.
-- **Validator**: Standard validator supporting `none`, `basic`, `json`, and `json_schema`.
-- **CLI Adapter**: Supports `run`, `render`, and `serve`.
-- **HTTP Adapter**: Supports full run execution through `POST /v1/runs`.
-
-## 6. Public Contracts
-
-### CLI
-
-Scriptorium should expose at least these commands:
-
-- `scriptorium run`: Executes a prompt by preparing it, calling the LLM, validating output, optionally repairing structured output, and returning an artifact.
-- `scriptorium render`: Prepares and renders a prompt without calling the LLM.
-- `scriptorium serve`: Starts the HTTP API using infrastructure-only flags.
-
-### `scriptorium run`
-
-`run` uses flags such as:
-
-- `--prompt-dir`
-- `--profile-dir`
-- `--prompt`
-- `--profile`
-- `--input`
-- `--var`
-- `--out`
-- runtime overrides such as `--model`, `--llm-base-url`, `--temperature`, `--max-tokens`, `--top-p`, `--timeout`, and `--api-key-env` if supported.
-
-`run` should produce the generated artifact as its primary output.
-
-### `scriptorium render`
-
-`render` prepares and renders a prompt without calling an LLM.
-
-It should use the same prompt/profile/input/variable/runtime override flags as `run` where applicable:
-
-- `--prompt-dir`
-- `--profile-dir`
-- `--prompt`
-- `--profile`
-- `--input`
-- `--var`
-- runtime overrides such as `--model`, `--llm-base-url`, `--temperature`, `--max-tokens`, `--top-p`, `--timeout`, and `--api-key-env` if supported.
-- `--format`, with initial support for `text` and `json`.
-
-Default render output format should be `text`.
-
-`render` must not call the LLM.
-
-`render` should show the same rendered messages and effective runtime settings that `run` would use.
-
-`render` should include enough information to debug:
-
-- prompt ID
-- prompt version
-- selected profile ID
-- effective runtime settings
-- input hashes
-- prompt hash
-- rendered messages
-
-`render` must not include resolved API key values.
-
-`render` may include the `api_key_env` name.
-
-### Render Output Formats
-
-Initial render output formats:
-
-- `text`: Human-readable default format.
-- `json`: Machine-readable structured representation of the prepared run.
-
-Additional formats, such as `markdown`, may be added later.
-
-Render output formatting should be modular. Adding a new output format should not require changing the prepare/run core logic.
-
-The output formatting layer should consume a `PreparedRun` and produce bytes or text for the adapter. It should not reload prompts, re-resolve artifacts, re-render templates, call the LLM, or perform validation.
-
-### `scriptorium serve`
-
-`serve` starts the HTTP API.
-
-It should use infrastructure-only flags such as:
-
-- `--addr`
-- `--prompt-dir`
-- `--profile-dir`
-- `--schema-dir`
-
-`serve` should not introduce a server-level model/runtime precedence layer unless explicitly documented and intentionally implemented.
-
-### HTTP API
-
-Current HTTP API:
-
-- `POST /v1/runs`: Accepts `RunRequest` JSON and returns `RunResponse` JSON. No built-in auth.
-
-Request may include runtime overrides under `model` and an `include_raw_output` boolean.
-
-`raw_model_output` is exposed only when explicitly requested with `include_raw_output=true`.
-
-A future HTTP prepare/render endpoint may be added, such as `POST /v1/renders` or `POST /v1/runs/prepare`, but the initial render feature may be CLI-only. If added later, it should call the same usecase-level prepare path as `scriptorium render`.
-
-### YAML Shapes
-
-Prompt YAML includes:
-
-- `id`
-- `version`
-- optional `default_profile`
-- `inputs`
-- `messages`
-- `output`
-
-Inputs support:
-
-- `name`
-- `required`
-- optional `content_type`
-- `description`
-
-Messages require:
-
-- `role`
-- exactly one of `content` or `content_file`
-
-`content_file` resolves relative to the prompt YAML location.
-
-Profile YAML includes:
-
-- `id`
-- `endpoint`
-- `model`
-- generation parameters
-- timeout settings
-- reasoning settings
-- `api_key_env`
-
-Prompt content must not appear in profile YAML.
-
-Model/runtime/API-key settings must not appear in prompt YAML, except that prompt YAML may specify `default_profile`.
-
-## 7. Render Feature Design
-
-The render feature is a first-class use case, not a CLI-only shortcut.
-
-### Goals
-
-The render feature should help users:
-
-- inspect fully rendered prompt messages
-- debug missing inputs
-- verify template variable substitution
-- verify selected profile resolution
-- verify runtime override precedence
-- verify file-backed prompt loading
-- inspect input hashes and prompt hashes
-- prepare for future token budgeting and prompt-size inspection
-
-### Non-Goals
-
-The render feature should not:
-
-- call an LLM
-- validate model output
-- repair structured output
-- resolve or print API key values
-- mutate artifacts
-- save outputs to artifact storage unless a future explicit output option is added
-- become an orchestration step manager
-
-### Usecase Shape
-
-The preferred usecase shape is:
-
-- `Runner.Prepare(ctx, RunRequest) (*PreparedRun, error)`
-- `Runner.Run(ctx, RunRequest) (*RunResult, error)`
-
-`Runner.Run` should call `Runner.Prepare`.
-
-The prepare flow should be the only implementation of:
-
-- prompt loading
-- profile selection
-- runtime override resolution
-- artifact resolution
-- prompt rendering
-- pre-run metadata/hash calculation
-
-### CLI Shape
-
-The preferred command name is `render`.
-
-The command should support:
-
-- `--format text`
-- `--format json`
-
-Default format:
-
-- `text`
-
-Unknown formats should produce a clear error.
-
-Formatting should be centralized through a small formatter registry, strategy, switch, or interface so new formats can be added without modifying usecase logic.
-
-### Text Output Expectations
-
-Text output should be optimized for human inspection.
-
-It should include, at minimum:
-
-- prompt ID and version
-- selected profile ID
-- model name
-- endpoint
-- effective generation settings
-- input hashes
-- rendered prompt hash
-- rendered messages grouped by role
-
-Text output should be readable and deterministic enough for tests.
-
-It should not include raw API key values.
-
-### JSON Output Expectations
-
-JSON output should be a structured representation of `PreparedRun` or a DTO derived from it.
-
-It should include, at minimum:
-
-- prompt ID and version
-- selected profile ID
-- effective runtime settings
-- input hashes
-- rendered prompt hash
-- rendered messages
-
-JSON output should not include raw API key values.
-
-JSON output should remain stable enough to be useful for automation and integration tests.
-
-## 8. Guardrails
-
-- **Separation of Concerns**: Prompt content must not belong in execution profiles; model/API settings must not belong in prompt definitions.
-- **Security**: Raw API keys are unsupported in all configuration and transport layers. Only `api_key_env` is used.
-- **Secret Handling**: Resolved API key values must never appear in rendered output, metadata, logs, HTTP responses, or CLI output.
-- **Path Resolution**: `content_file` paths in prompt definitions resolve relative to the prompt YAML file.
-- **Integrity**: No silent prompt truncation or omission of content.
-- **Reliability**: Repair loops are strictly bounded by `repair_attempts`.
-- **No Orchestration Creep**: Scriptorium prepares and executes a single prompt request. It does not coordinate multi-stage workflows.
-- **Render Reuse**: The full run path must reuse the prepare/render path to avoid divergent behavior.
-- **Formatter Isolation**: Render output formatters must not perform usecase work. They only format a completed `PreparedRun`.
-
-## 9. Testing Strategy
-
-Tests should protect both the run path and the prepare/render path.
-
-### Prepare / Render Tests
-
-Add tests for:
-
-- preparing a prompt with explicit profile selection
-- preparing a prompt using `default_profile`
-- failing when no explicit profile and no `default_profile` exist
-- runtime overrides beating profile values
-- profile values beating application defaults
-- file-backed prompt bodies rendering correctly
-- required inputs failing when missing
-- optional inputs being absent when not referenced
-- unknown input references failing
-- input hashes being included
-- rendered prompt hash being included
-- effective runtime settings being included
-- `api_key_env` name being included where appropriate
-- resolved API key values never appearing in `PreparedRun`
-- prepare path not calling the LLM
-
-### CLI Render Tests
-
-Add tests for:
-
-- `scriptorium render` mapping flags into `RunRequest`
-- default text output
-- explicit `--format text`
-- explicit `--format json`
-- unknown format failure
-- text output includes prompt/profile/messages
-- JSON output includes prompt/profile/messages
-- rendered output never includes resolved API key values
-
-### Run Reuse Tests
-
-Add tests proving:
-
-- `Runner.Run` reuses prepare behavior
-- run and render resolve the same prompt/profile/runtime settings for equivalent inputs
-- run still validates output
-- run still performs bounded repair where configured
-
-### Existing Tests
-
-Continue testing:
-
-- prompt definition loading
-- execution profile loading
-- artifact loading
-- prompt rendering
-- LLM adapter behavior
-- validation behavior
-- HTTP request/response mapping
-
-## 10. Extension Points
-
-Future work should remain grounded in the current architecture:
-
-- **Artifacts**: Add S3 artifact references via a new `artifact.Reader`.
-- **LLM**: Implement additional provider adapters, such as Anthropic or Google.
-- **Execution**: Add token budgeting, streaming generation, and batch execution capabilities.
-- **Prepare/Render**: Add token estimates, prompt-size summaries, or additional render output formats.
-- **Repositories**: Implement database-backed repositories for prompts and profiles.
-- **Profiles**: Support more granular profile versioning and environment-specific profiles.
-- **HTTP**: Add an HTTP prepare/render endpoint if Narratio or another caller needs it.
-
-Future render formats should plug into the formatter layer and should not require changes to the usecase layer.

docs/adr/0001-adopt-canonical-documentation-ownership.md

@@ -0,0 +1,48 @@
+# ADR 0001: Adopt Canonical Documentation Ownership
+
+## Status
+
+Accepted
+
+## Date
+
+2026-07-26
+
+## Context
+
+Scriptorium's documentation grew alongside its CLI, HTTP, public Go, and
+integration interfaces. As a result, several documents repeated mutable
+contracts such as flags, configuration fields, and status behavior. Those
+parallel definitions made it unclear which document to update when behavior
+changed and increased the risk of documentation drift.
+
+## Decision
+
+Assign each documentation topic one canonical owner, as defined in
+[`docs/policy/documentation.md`](../policy/documentation.md). Non-owning
+documents may provide short orientation and links, but do not redefine volatile
+contracts. Current behavior is documented outside `docs/roadmap/`; roadmaps own
+future work, sequencing, and implementation status.
+
+## Alternatives Considered
+
+- Keep broad reference material in several audience-specific documents. This
+  would preserve local convenience but leave conflicting contract definitions
+  likely.
+- Consolidate all documentation into one reference. This would reduce duplicate
+  text but would not serve the distinct needs of users, operators, consumers,
+  and contributors.
+
+## Rationale
+
+Canonical ownership retains audience-specific guidance while making the source
+of truth for each contract discoverable. It also makes documentation changes
+reviewable alongside the implementation change that requires them.
+
+## Consequences
+
+- Changes to behavior must update the canonical owner in the same change.
+- Cross-cutting documentation links to the owner instead of copying its
+  details.
+- Documentation restructuring followed a dedicated implementation roadmap;
+  repository history, not this ADR, records its completion.

docs/adr/0002-split-promptkit-from-scriptorium.md

@@ -0,0 +1,288 @@
+# ADR 0002: Split Promptkit From Scriptorium
+
+## Status
+
+Accepted
+
+## Date
+
+2026-07-26
+
+## Context
+
+Scriptorium currently combines two products in one Go module:
+
+- a reusable prompt-execution framework with a public Go facade; and
+- a runnable application with CLI and HTTP interfaces.
+
+Downstream Go projects increasingly import the framework directly and do not
+use the executable interfaces. Keeping both products in one module couples
+framework releases, dependencies, documentation, and public API evolution to
+application-specific transport concerns.
+
+Promptkit will become the framework project, and Scriptorium will become a slim
+application that consumes it. This ADR records that end-state boundary. It does
+not assert that the split has been implemented; until then, the current
+repository structure and contracts remain authoritative.
+
+## Decision
+
+### Projects And Module Paths
+
+Create a repository named `promptkit` alongside Scriptorium:
+
+| Project | Repository and Go module path | Root Go package |
+| --- | --- | --- |
+| Promptkit | `gitea.maximumdirect.net/eric/promptkit` | `promptkit` |
+| Scriptorium | `gitea.maximumdirect.net/eric/scriptorium` | No reusable root facade after migration |
+
+Promptkit will expose its supported public API from the module root. Its
+implementation packages will remain under `internal/` unless a real consumer
+extension point requires a public type or interface.
+
+Scriptorium will import only Promptkit's supported public packages. It will not
+import Promptkit implementation packages or reproduce Promptkit orchestration.
+
+### Product Responsibilities
+
+Promptkit owns application-neutral framework behavior:
+
+- the engine and its `Prepare` and `Run` workflow;
+- public request, result, profile, option, extension, and error APIs;
+- prompt-definition loading and rendering;
+- profile loading, overlays, and the embedded built-in profile registry;
+- schema loading and output validation;
+- provider-neutral model-client boundaries and the OpenAI-compatible client;
+- artifact types, artifact-reader injection, and general-purpose inline and
+  caller-selected file readers;
+- execution-setting resolution and framework defaults; and
+- framework-level secret redaction and error classification.
+
+Scriptorium owns executable and transport behavior:
+
+- the `scriptorium` process and its `run`, `render`, and `serve` commands;
+- CLI parsing, streams, output files, formatting, exit codes, and process
+  cancellation behavior;
+- application-configuration discovery and CLI-over-configuration precedence;
+- HTTP routing, strict request decoding, DTO mapping, response encoding,
+  status codes, and transport limits;
+- HTTP artifact-root containment and deployment policy;
+- server construction, server defaults, and process logging; and
+- executable release artifacts.
+
+The dependency direction is:
+
+```text
+Scriptorium CLI and HTTP adapters
+                |
+                v
+       Promptkit public API
+                |
+                v
+  injected sources, readers, and model clients
+```
+
+### Current Package Disposition
+
+Implementation may reorganize files during extraction, but each current package
+has this target owner:
+
+| Current package or file group | Target owner | Disposition |
+| --- | --- | --- |
+| Root `scriptorium` facade files and tests | Promptkit | Move and rename the public package to `promptkit`; Scriptorium retains no compatibility facade. |
+| `internal/domain`, `internal/usecase` | Promptkit | Move as internal engine implementation. |
+| `internal/promptdef`, `internal/prompt` | Promptkit | Move as internal prompt loading and rendering. |
+| `internal/profile`, `internal/profile/builtin` | Promptkit | Move with embedded built-in assets and registry tests. |
+| `internal/filecatalog` | Promptkit | Move as source-loading support. |
+| `internal/validate` | Promptkit | Move as schema and output-validation implementation. |
+| `internal/llm` | Promptkit | Move with the OpenAI-compatible integration. |
+| `internal/artifact` | Split | Move general inline/file reading to Promptkit; keep rooted, denied, and byte-limited HTTP file reading in Scriptorium behind a Promptkit reader interface. |
+| `internal/defaults` | Split | Move framework, execution, output-artifact, content-type, and model-client defaults to Promptkit; keep CLI, HTTP, and server defaults in Scriptorium. |
+| `internal/adapter/cli`, `internal/adapter/http` | Scriptorium | Keep and refactor to use Promptkit's public API. |
+| `internal/config` | Scriptorium | Keep application settings, discovery, validation, and CLI precedence. |
+| `internal/format` | Scriptorium | Keep prepared-run presentation, rewritten against Promptkit public values. |
+| `cmd/scriptorium` | Scriptorium | Keep as the process entrypoint. |
+
+Tests move with the behavior they protect. Cross-boundary tests will live with
+the consuming side: Promptkit protects framework contracts, while Scriptorium
+protects adapter mapping, HTTP containment, and executable behavior.
+
+### Public Boundary
+
+Promptkit's initial facade will preserve the useful shape of the current
+Scriptorium Go API where that reduces extraction risk. It will expose only the
+capabilities required by Promptkit consumers and by Scriptorium:
+
+- engine construction, preparation, and execution;
+- public request, result, profile, and error values;
+- prompt, profile, schema, artifact-reader, validator, and model-client source
+  or injection options that have demonstrated consumers; and
+- enough stable error identity for Scriptorium to map CLI and HTTP outcomes.
+
+Promptkit will not export its domain package, runner implementation,
+repositories, adapter DTOs, or general internal constructors merely to
+simplify the move.
+
+Scriptorium's CLI and HTTP adapters will depend on a small consumer-facing
+`Prepare`/`Run` interface where test substitution is needed. That interface
+belongs at the consuming boundary rather than forcing adapter concepts into
+Promptkit.
+
+### Artifact Reading And HTTP Containment
+
+Promptkit will define the artifact-reader extension point used during
+preparation. Its ordinary file reader may read a path deliberately supplied by
+an in-process or CLI caller and does not claim to be a deployment sandbox.
+
+Scriptorium will implement the HTTP-specific reader that:
+
+- denies file references when no artifact root is configured;
+- applies the configured artifact byte limit;
+- enforces Scriptorium's documented lexical root-containment rule; and
+- maps reader failures to Scriptorium HTTP error responses.
+
+Scriptorium will inject that reader through Promptkit's public construction
+boundary. Promptkit will not know about HTTP roots, status codes, request DTOs,
+or deployment policy.
+
+### Configuration And Default Ownership
+
+Configuration ownership follows the behavior configured, not the current file
+location:
+
+| Configuration category | Owner |
+| --- | --- |
+| Application configuration discovery, configuration-file precedence, `prompt_dir`, `profile_dir`, and `schema_dir` | Scriptorium |
+| CLI flags and their mapping to application settings or request overrides | Scriptorium |
+| `server.*`, render-output settings, HTTP byte limits, and server defaults | Scriptorium |
+| Prompt-definition, profile, and output-contract file formats | Promptkit |
+| Prompt/profile source selection, overlays, schema behavior, and built-in profiles | Promptkit |
+| Execution settings, presence-aware request overrides, and execution defaults | Promptkit |
+| Built-in OpenAI-compatible client settings, timeout behavior, and provider wire mapping | Promptkit |
+| HTTP request and response fields, including their mapping to framework values | Scriptorium |
+
+Scriptorium will translate its application settings and external request
+values into Promptkit construction options and requests. When an omitted
+Scriptorium setting means “use the framework default,” Scriptorium will omit
+the override rather than copy Promptkit's numeric default.
+
+### Compatibility And Versioning
+
+This migration is intentionally breaking:
+
+- new Go consumers will import `gitea.maximumdirect.net/eric/promptkit`;
+- Scriptorium will not provide aliases, forwarding wrappers, or deprecated
+  compatibility packages for its former Go facade;
+- existing consumers may remain pinned to the final framework-bearing
+  Scriptorium tag until migrated; and
+- intermediate migration phases need not preserve source compatibility, but
+  each merged phase must be internally buildable and tested.
+
+Promptkit's first release will be `v0.1.0`. During the migration, incompatible
+Promptkit changes may advance its minor version until a stable `v1` contract is
+declared. The first slim Scriptorium release will advance the Scriptorium minor
+version beyond the final framework-bearing release. Normal semantic-versioning
+rules apply independently to both projects after the migration.
+
+Promptkit must be tagged before Scriptorium or another consumer publishes a
+release that depends on it. Release branches must use tagged module
+dependencies, not local replacements or unpublished revisions.
+
+### Local Development And Cross-Repository Coordination
+
+For coordinated local work, place both repositories in a temporary Go
+workspace or use an uncommitted module replacement. `go.work`,
+`go.work.sum`, and local filesystem `replace` directives must not be committed
+to release branches.
+
+Cross-repository changes follow this order:
+
+1. land and tag the required Promptkit capability;
+2. update Scriptorium and other consumers to that tag;
+3. run each repository's own CI and smoke checks; and
+4. release consumers only after the Promptkit tag is available.
+
+Migration coordination must confirm out-of-band repository creation, Promptkit
+tags, and downstream migrations before dependent work proceeds.
+Cross-repository changes are coordinated, not treated as atomic commits.
+
+### Documentation And Maintained Assets
+
+Each repository will maintain its own README, contributor guide, architecture,
+documentation, testing, release, and operations material appropriate to that
+project. Cross-project documents will link to the canonical owner rather than
+copy its contract.
+
+Existing documentation and maintained assets have these target owners:
+
+| Current material | Target owner |
+| --- | --- |
+| Current README and executable quickstart | Scriptorium; Promptkit creates its own framework orientation |
+| Public Go package and Go-consumer guidance | Promptkit |
+| Prompt, profile, schema, execution-setting, and framework credential reference | Promptkit |
+| OpenAI-compatible integration contract and framework internal documents | Promptkit |
+| CLI, HTTP API, subprocess, and Scriptorium operations contracts | Scriptorium |
+| Consumer interface overview | Scriptorium, revised to route Go consumers to Promptkit |
+| Application-configuration discovery, server settings, and adapter internals | Scriptorium |
+| Current internal overview and source documentation | Split into repository-local overviews; Promptkit owns framework sources and Scriptorium owns HTTP containment |
+| This ADR and cross-project migration records | Scriptorium |
+| `examples/go-library` | Promptkit |
+| `examples/config*.yml`, `examples/render-markdown-summary.sh`, and `examples/http-run.json` | Scriptorium |
+| Example prompts, profiles, schemas, and synthetic fixtures used by the executable examples | Scriptorium |
+| Embedded built-in profile assets | Promptkit |
+| Scriptorium release workflow and executable packaging | Scriptorium |
+| Repository-level license, ignore rules, agent guidance, and development policies | Each repository maintains its own applicable copy |
+
+Promptkit will create or retain its own minimal framework examples and test
+fixtures rather than making either repository's tests depend on the other's
+working tree. Scriptorium's framework-format documentation will become a short
+version-appropriate link to Promptkit, while its maintained executable examples
+remain self-contained.
+
+## Alternatives Considered
+
+- Keep the current combined repository and improve package naming. This avoids
+  migration work but retains release and ownership coupling between the
+  framework and executable.
+- Add Promptkit as a wrapper around the Scriptorium public package. This gives
+  consumers a new import path but leaves framework ownership and dependency
+  direction inverted.
+- Extract Promptkit while retaining a Scriptorium compatibility facade. This
+  reduces immediate consumer changes but creates a second public API surface
+  and prolongs duplicate maintenance.
+- Move all artifact reading into Promptkit. This would place HTTP containment,
+  byte limits, and deployment policy in the application-neutral framework.
+- Keep Promptkit and Scriptorium as separate modules in one repository. This
+  separates imports but not repository permissions, release workflows,
+  issue ownership, or independent project evolution.
+
+## Rationale
+
+A separate Promptkit project makes the reusable framework the direct owner of
+the API that downstream Go projects already consume. Keeping Scriptorium as a
+public-API consumer exercises the same boundary as other consumers and prevents
+its adapters from relying on framework internals.
+
+The selected split keeps transport and deployment policy close to the
+Scriptorium interfaces that expose it, while allowing Promptkit to remain
+useful to in-process consumers with different IO and security requirements.
+Explicit package, configuration, documentation, and asset ownership reduces
+ambiguity during extraction and after release.
+
+## Consequences
+
+- All Go consumers of the framework must change their import path.
+- Promptkit and Scriptorium gain independent issue, release, CI, policy, and
+  documentation lifecycles.
+- Scriptorium becomes a real downstream integration test of Promptkit's public
+  facade.
+- Framework changes that affect Scriptorium require tagged, ordered
+  cross-repository coordination.
+- Some current packages, especially artifact reading and defaults, must be
+  separated by responsibility rather than moved intact.
+- Scriptorium's current configuration and documentation references must be
+  split between application and framework owners.
+- Maintainers must inventory and migrate downstream consumers explicitly; no
+  compatibility facade will hide incomplete migration.
+- Until the split is implemented, the current repository structure and
+  contracts remain authoritative.

docs/adr/0003-use-maintainer-run-validation-and-tag-only-releases-for-promptkit.md

@@ -0,0 +1,67 @@
+# ADR 0003: Use Maintainer-Run Validation and Tag-Only Releases for Promptkit
+
+## Status
+
+Accepted
+
+## Date
+
+2026-07-28
+
+## Context
+
+[ADR 0002](0002-split-promptkit-from-scriptorium.md) established Promptkit as
+an independent Go library with its own repository, version history, validation,
+and release coordination. It anticipated independent hosted CI for Promptkit
+alongside Scriptorium's existing executable build and CI policy.
+
+Promptkit is presently a single-maintainer library. It does not produce a
+runnable command, so executable packaging and binary-release automation do not
+apply. Its validation and release model should be explicit before repository
+guidance relies on it.
+
+## Decision
+
+Promptkit will use maintainer-run validation rather than hosted CI at this
+stage. From a clean checkout, the maintainer will run the repository-documented
+test, vet, build, formatting, documentation-link, and repository-hygiene checks
+before changes are accepted and before a release tag is published.
+
+Promptkit releases consist of source commits and semantic Go module tags. The
+project does not release runnable binaries or maintain binary-packaging
+automation.
+
+Scriptorium's executable build, hosted CI, and binary-release policies are
+unaffected. The repository boundary, independent version history, release
+ordering, and other migration decisions accepted by ADR 0002 remain in force.
+Where ADR 0002 anticipated independent hosted CI for Promptkit, this later ADR
+controls Promptkit validation.
+
+## Alternatives Considered
+
+- Add hosted Promptkit CI now. This would provide automated remote enforcement,
+  but its setup and maintenance are not proportionate to the present
+  single-maintainer library and do not replace the maintainer's release
+  responsibility.
+- Require local Git hooks. Hooks can provide fast feedback, but they are
+  machine-local, can be bypassed, and are not a durable substitute for the
+  documented clean-checkout validation procedure.
+
+## Rationale
+
+A documented maintainer-run procedure provides a clear acceptance and release
+gate with little operational overhead for the project's current contribution
+pattern. If maintenance load or contributor patterns change, a later ADR may
+introduce hosted CI without changing Promptkit's library or tag-based release
+model.
+
+## Consequences
+
+- Promptkit repository guidance must define the complete local validation
+  procedure and the checks required before accepting or tagging a change.
+- Release evidence is the maintainer's successful clean-checkout validation,
+  not a hosted CI result.
+- Promptkit releases contain source and semantic Go module tags only.
+- A future move to hosted CI requires a later architectural decision.
+- Scriptorium continues to validate, build, package, and release its executable
+  under its own policies.

docs/adr/0004-definition-boundary.md

@@ -0,0 +1,112 @@
+# Preserve Definition Compatibility And A Simple Execution Model
+
+## Status
+
+Accepted.
+
+## Date
+
+2026-08-29.
+
+## Context
+
+Scriptorium is a user-facing application built on Promptkit. Promptkit is a Go
+library with both declarative framework formats and public APIs intended for
+applications that need to assemble specialized integrations or workflows.
+
+Scriptorium needs a durable rule for deciding which upstream capabilities it
+must support. Treating every new Promptkit public API as an application feature
+would steadily expand Scriptorium into a workflow framework. Selecting an
+arbitrary subset of prompt or profile fields would instead make valid Promptkit
+definitions unexpectedly unusable through Scriptorium.
+
+The intended product is narrower: Scriptorium provides simple executable
+interfaces that select and execute predefined prompts and return their results
+in a consistent, repeatable form. It is not intended to own conversations,
+modify prompts dynamically, coordinate follow-up messages, or manage complex
+multi-step workflows.
+
+## Decision
+
+Scriptorium will aim to support the complete set of features expressible in
+valid Promptkit prompt and profile definitions for the Promptkit version it
+selects. This includes the schema, backend, source, and request plumbing needed
+to prepare and execute those definitions without Scriptorium imposing a
+narrower field-level format contract.
+
+Promptkit remains the canonical parser and validator for its definitions.
+Scriptorium will pass its configured framework sources and mapped request
+values through the supported Promptkit public facade rather than copying
+Promptkit formats, defaults, or validation rules.
+
+Promptkit library features that are not required to use valid prompt or profile
+definitions are considered individually. They may be incorporated when they
+serve Scriptorium's simple execution model and fit its application-owned CLI,
+HTTP, configuration, presentation, security, and process boundaries. A public
+Promptkit declaration does not by itself require a corresponding Scriptorium
+interface.
+
+Each execution request will remain self-contained from the caller's
+perspective. A request must not depend on conversation or workflow state
+retained from a completed request, and Scriptorium will not become a general
+workflow or conversation system. Application-managed prompt modification,
+appended or follow-up message flows, conversation state, prepared-handle
+coordination, multi-step orchestration, and similar higher-level workflows are
+outside its intended scope.
+
+Scriptorium may, and when necessary must, maintain process-scoped operational
+state shared by concurrent requests. This includes the configured Promptkit
+engine and backend registry, capacity admission and queue accounting,
+in-flight request coordination, cancellation, and ordinary server lifecycle
+resources. The state must be scoped so configured backend limits apply across
+all relevant in-flight requests. But this is operational implementation state,
+not durable user workflow or conversation state.
+
+## Alternatives Considered
+
+### Expose Every Promptkit Public Feature
+
+This would make the application surface track the library API closely, but it
+would blur the boundary between a reusable Go library and a simple executable
+consumer. Library-oriented lifecycle, source-construction, extension, and
+workflow primitives would add commands, wire contracts, configuration, and
+state without necessarily improving predefined prompt execution.
+
+### Support A Curated Subset Of Definition Fields
+
+This would keep the application small in the short term, but valid Promptkit
+definitions could fail or behave differently solely because they were invoked
+through Scriptorium. Maintaining a parallel field-level compatibility list
+would also duplicate upstream format ownership and create recurring drift.
+
+### Expand Scriptorium Into A Workflow Service
+
+Scriptorium could own conversations, prompt changes, follow-up messages,
+retries, checkpoints, and multi-step execution. That is a different product
+with durable state, lifecycle, recovery, privacy, and operational requirements
+that are not justified by Scriptorium's current purpose.
+
+## Consequences
+
+- Promptkit upgrades require an audit of the complete prompt and profile format
+  contracts, not only a source-compatibility build.
+- Scriptorium adapters must not add unconditional request requirements that
+  reject a definition Promptkit can validly prepare or execute.
+- Application configuration may need new plumbing, such as custom backend
+  registration, when it is necessary to use a valid profile feature.
+- Definition parsing, validation, precedence, inheritance, defaults, and
+  built-in catalogs remain Promptkit responsibilities.
+- A running HTTP server must share its appropriately scoped Promptkit engine
+  across requests so the engine's backend admission and concurrency limits
+  cannot be bypassed by per-request construction.
+- Process-scoped counters, queues, in-flight request records, cancellation, and
+  lifecycle resources are permitted implementation state. They must be
+  concurrency-safe and do not create a durable resume or conversation
+  contract.
+- Library-only source constructors, injected collaborators, opaque lifecycle
+  handles, and request-composition primitives remain optional Scriptorium
+  features rather than automatic requirements.
+- New application features must be evaluated against the simple,
+  request-independent predefined-prompt execution model.
+- Work that implements this decision remains tracked in roadmaps until it is
+  delivered and incorporated into current-state contracts.

docs/api.md

@@ -0,0 +1,227 @@
+# HTTP API Reference
+
+This is the canonical public HTTP contract for Scriptorium.
+
+## Service And Route
+
+`POST /v1/runs` runs one prompt request and returns generated output,
+validation, and metadata. The service has no built-in authentication or
+authorization; deploy it behind appropriate network and authentication controls.
+
+The service address and HTTP limits are configured as described in the
+[configuration reference](config.md). `serve` invocation is defined in the
+[CLI reference](cli.md).
+
+Requests and responses are JSON objects. Requests are decoded as JSON regardless
+of their `Content-Type`; successful JSON responses use
+`Content-Type: application/json`. There are no query parameters.
+
+## Request Limits
+
+The configured request-body limit includes inline artifact bodies. The artifact
+limit applies to HTTP `file` inputs. The response limit applies to the encoded
+response, including the artifact body, optional raw output, and optional execution report. A limit of zero
+disables that limit.
+
+A request body over its limit returns `413 request_too_large`; an oversized
+file input returns `413 artifact_too_large`; an oversized encoded response
+returns `413 response_too_large`.
+
+## `POST /v1/runs`
+
+### Request Body
+
+The maintained [request example](../examples/http-run.json) is a complete
+copyable shape. At the HTTP adapter boundary, the smallest valid shape is:
+
+```json
+{
+  "prompt_id": "generic.markdown_summary"
+}
+```
+
+| Field | Required | Meaning |
+| --- | --- | --- |
+| `prompt_id` | yes | Non-blank prompt ID. |
+| `prompt_version` | no | Prompt version filter. |
+| `profile_id` | no | Execution-profile ID; otherwise the prompt must set `default_profile`. |
+| `session_id` | no | Optional direct, non-secret session identifier. |
+| `inputs` | no | Optional object mapping input names to references. Promptkit decides whether the selected definition needs them. |
+| `vars` | no | Object mapping template-variable names to strings. |
+| `model` | no | Runtime model-override object. |
+| `include_raw_output` | no | Include `raw_model_output` when true. |
+| `include_execution_report` | no | Include a terminal `execution` report when true and Promptkit supplies a terminal observation. Omitted, `null`, or false leaves reporting off. |
+| `transient_retries` | no | Nonnegative additional transient attempt count for this run. Omitted or `null` inherits the configured engine value and then Promptkit's default; `0` disables additional attempts. |
+| `run_timeout_seconds` | no | Optional signed 64-bit whole-second limit for engine execution. Omitted, `null`, or `0` adds no deadline; positive values shorten the caller context deadline. |
+
+An input reference has a required `type` of `file` or `inline`. A `file`
+reference requires `uri`; an `inline` reference requires `body`.
+
+HTTP file references require a configured artifact root. Relative paths resolve
+within that root. Absolute paths must be lexically within it; traversal outside
+it is rejected with `400 artifact_not_allowed`. This lexical check does not
+resolve symlinks: the operating system follows symlinks inside the root,
+including ones that target outside it. Keep the root narrow and inaccessible to
+untrusted writers.
+
+The optional `model` object accepts `endpoint`, `model`, `temperature`,
+`max_tokens`, `top_p`, `timeout_seconds`, `service_tier`,
+`reasoning_effort`, `api_key_env`, and `extra_params`. Numeric ranges and
+framework credential semantics are defined by the
+[Promptkit format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md).
+Explicit zero values for the numeric fields are overrides; zero
+`timeout_seconds` disables the per-attempt generation deadline only, retaining the
+request context and configured transport cap. The timeout layers are defined in
+the [Promptkit outbound integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/integrations/openai-compatible-chat.md#timeout-and-cancellation).
+Each built-in transient retry gets a fresh generation timeout; the caller's
+request context remains the outer cancellation boundary.
+
+Raw API-key values are not accepted. `api_key` and any other unknown model
+field cause `400 invalid_json`.
+
+`model.reasoning_effort` is an optional JSON string with three states: omission
+inherits the selected profile, a non-empty string replaces its value, and an
+empty string explicitly clears it. JSON `null` is treated as omission.
+
+`session_id` is passed directly to Promptkit. A nonblank value replaces a
+definition-rendered session ID; omission or a blank value lets the definition
+provide one. Promptkit trims direct values and limits them to 256 Unicode code
+points. Session IDs are not credentials and may be included in prepared data,
+results, and provider-facing requests, so use stable non-sensitive identifiers.
+
+### Strict JSON
+
+Request decoding rejects malformed JSON, unknown fields at every request level,
+and trailing JSON tokens with `400 invalid_json`. A blank `prompt_id` returns
+`400 invalid_request`. Omitted or empty `inputs` are passed to Promptkit, which
+reports any definition-required or template-referenced inputs.
+`transient_retries` must be a JSON integer; a wrong type or noninteger number
+returns `400 invalid_json`, while a negative integer returns
+`400 invalid_request` before execution. A request override does not change the
+shared engine setting used by other requests. Promptkit owns eligible statuses,
+retry waits, and the separate transient budget for each repair generation.
+`run_timeout_seconds` must be a JSON int64. A wrong type or int64 overflow
+returns `400 invalid_json`; a negative value or one whose conversion to a Go
+duration would overflow returns `400 invalid_request`. The deadline starts
+immediately before engine execution and excludes body decoding and response
+writing. An earlier caller deadline or cancellation still wins. Synchronous
+work is not guaranteed to stop immediately.
+
+### Success Response
+
+A completed run returns `200 OK`, including when generated content fails its
+validation contract. The response contains:
+
+- `artifact`: `name`, `content_type`, `body`, `size`, `hash`, and
+  optional `uri`;
+- `validation`: `status`, `mode`, `repair_attempts`, `is_valid`, plus
+  optional `errors` and `schema_path`;
+- `metadata`: run, prompt, rendered-prompt, profile, optional backend identity, model, input-hash, usage,
+  timing, validation, and repair-attempt metadata; and
+- optional `raw_model_output` when requested.
+- optional `execution` when requested and a terminal observation exists.
+
+`metadata.model_params` has `endpoint`, `model`, `temperature`,
+`max_tokens`, `top_p`, and `timeout_seconds`, plus optional
+`backend_id`, `service_tier`, `reasoning_effort`, `api_key_env`, and `extra_params`.
+`metadata.usage` always includes `prompt_tokens`, `completion_tokens`,
+`total_tokens`, `cached_tokens`, and `cache_write_tokens`; unavailable
+cache usage is reported as zero.
+
+When Promptkit resolves a direct or definition-rendered session ID,
+`metadata.session_id` contains that effective result value. It is omitted when
+no effective session ID exists.
+
+`metadata.selected_backend_id` and `metadata.model_params.backend_id` report
+the corresponding Promptkit result fields independently when present. Both are
+omitted for an endpoint-only profile; Scriptorium does not infer backend
+identity from an endpoint.
+
+A validation failure has `validation.status: "failed"`, `is_valid: false`,
+and any available diagnostic errors, while still returning the artifact and
+metadata.
+
+### Execution Report
+
+The opt-in `execution` object projects one Promptkit terminal observation. It
+is independent of `metadata.usage`, which retains its existing result-based
+meaning. A terminal event can describe a failed invocation even when no provider
+call was dispatched; if there is no terminal event, `execution` is omitted.
+
+| Field | Meaning |
+| --- | --- |
+| `run_id`, `prompt_id`, `prompt_version`, `profile_id`, `backend_id`, `model` | Terminal identifiers; absent values are omitted. |
+| `outcome` | `success`, `invalid_output`, `error`, or `other` for an unrecognized upstream value. |
+| `failure` | The known terminal failure category, `none`, or `other` for an unrecognized value. |
+| `status_code` | Provider status, omitted when unavailable. |
+| `retries_exhausted` | Boolean independent of the failure category. |
+| `attempts`, `transient_retries`, `repair_calls` | Unsigned terminal aggregate counts. |
+| `duration_ms`, `capacity_wait_ms`, `generation_duration_ms`, `retry_delay_ms` | Terminal observed durations in integer milliseconds; their sum need not equal wall time. |
+| `usage` | Object containing `prompt_tokens`, `completion_tokens`, `total_tokens`, `cached_tokens`, and `cache_write_tokens`. |
+
+Each `usage` count contains `value` (integer), `known` (boolean), and
+`complete` (boolean). Reported zero differs from an unknown count; an
+incomplete total does not establish complete billing. All counts, durations,
+`retries_exhausted`, and `usage` are present even when zero or unknown. The
+recognized failure values are `none`, `canceled`, `deadline`, `transport`,
+`provider_status`, `malformed_response`, `capacity`, `invalid_config`,
+`invalid_request`, `prompt_not_found`, `profile_not_found`, `prompt_load`,
+`profile_load`, `artifact_load`, `prompt_render`, `validation`, `generation`,
+and `other`.
+
+The report excludes content, credentials, URLs, headers, and raw errors, but
+its identifiers can still be sensitive. Apply appropriate access and retention
+controls to responses that include it.
+
+## Error Responses
+
+Errors have this shape:
+
+```json
+{"error":{"code":"invalid_request","message":"prompt_id is required"}}
+```
+
+Messages are concise and do not expose wrapped internal causes.
+For an opted-in failed invocation, the error envelope can also include the
+optional top-level `execution` object described above. Decode and validation
+failures before engine invocation do not have a report. Report-bearing error
+responses are subject to the complete encoded response-size limit; if they
+exceed it, the response is the compact `413 response_too_large` error without
+`execution`. The existing compact error fallback itself is not re-limited.
+
+| Status | Code | Meaning |
+| --- | --- | --- |
+| `400` | `invalid_json` | Malformed JSON, unknown field, or trailing JSON. |
+| `400` | `invalid_request` | Missing or invalid request data or runtime override. |
+| `400` | `profile_required` | No profile ID and no prompt default profile. |
+| `400` | `prompt_load_failed` | Prompt definition failed to load. |
+| `400` | `profile_load_failed` | Profile failed to load. |
+| `400` | `artifact_not_allowed` | HTTP file input is disabled or outside the artifact root. |
+| `400` | `artifact_read_failed` | Input artifact is invalid or cannot be read. |
+| `400` | `prompt_render_failed` | Prompt template rendering failed. |
+| `400` | `api_key_env_missing` | The selected credential environment variable is unset or empty. |
+| `404` | `not_found` | Route does not exist. |
+| `404` | `prompt_not_found` | Prompt ID or version does not exist. |
+| `404` | `profile_not_found` | Profile ID does not exist. |
+| `405` | `method_not_allowed` | The route does not accept the method. |
+| `408` | `request_canceled` | The caller context was canceled during a failed run. |
+| `413` | `request_too_large` | Encoded request exceeds its limit. |
+| `413` | `artifact_too_large` | File input exceeds its limit. |
+| `413` | `response_too_large` | Encoded response exceeds its limit. |
+| `500` | `validation_runtime_failed` | Schema or validator runtime failure. |
+| `500` | `internal_error` | Unclassified server failure. |
+| `502` | `llm_failed` | Outbound model request failed. |
+| `503` | `capacity_exceeded` | The selected model backend has no admission capacity. No retry timing is supplied. |
+| `504` | `deadline_exceeded` | The execution context's deadline expired during a failed run. |
+
+These context outcomes require the execution context to have ended. A provider
+attempt timeout while it remains live retains `502 llm_failed`. A successful
+run remains successful even if cancellation races with response formatting;
+delivery after a client disconnect cannot be guaranteed.
+
+## Retry And Idempotency
+
+Scriptorium provides no idempotency keys, pagination, caching headers, or rate
+limits. Clients may retry transport failures or `5xx` responses only when
+their workflow tolerates another model call: a retry can produce different
+output and incur another provider request.

docs/cli.md

@@ -0,0 +1,304 @@
+# CLI Reference
+
+This is the canonical contract for invoking Scriptorium. Configuration discovery,
+precedence, application source locations, and server settings are defined in the
+[configuration reference](config.md). The [HTTP API reference](api.md) owns
+service request and response behavior.
+
+## Shortest Useful Command
+
+```bash
+go run ./cmd/scriptorium render \
+  --config ./examples/config.yml \
+  --prompt generic.markdown_summary \
+  --input transcript=./examples/fixtures/transcript.md \
+  --input glossary=./examples/fixtures/glossary.yml
+```
+
+`render` prepares a request without calling an LLM.
+
+## Commands
+
+- `scriptorium run`: prepare a prompt, call the configured LLM, and write the
+  generated artifact.
+- `scriptorium render`: prepare a prompt and write prepared-run output.
+- `scriptorium serve`: start the HTTP server.
+- `scriptorium inspect prompt`: inspect one prompt definition without model execution.
+- `scriptorium inspect profile`: inspect one effective profile without model execution.
+- `scriptorium config validate`: validate application configuration without building an engine.
+- `scriptorium config show`: show the resolved application configuration.
+- `scriptorium config sources`: show the ordered configuration sources.
+- `scriptorium config explain`: explain one effective or historical configuration path.
+
+All commands accept `--config <path>` and `--config-overlay <name>` and reject
+positional arguments. `--config-overlay` selects one application configuration
+overlay; it is separate from `--profile`, which selects a Promptkit execution
+profile. See [configuration composition](config.md#explicit-imports-and-selected-overlays)
+for name, root, and no-base behavior. `run`,
+`render`, `serve`, and `inspect prompt` require an effective `prompt_dir`;
+`inspect profile` does not. Supply the directory through the configuration
+contract or a supported `--prompt-dir` flag. Explicit application flags,
+including empty values, override file settings. Configuration load diagnostics
+go to stderr and exit with status 1; successful load warnings are printed once
+before command work.
+
+## `scriptorium run`
+
+```text
+scriptorium run [flags]
+```
+
+Required flags:
+
+| Flag | Meaning |
+| --- | --- |
+| `--prompt <id>` | Prompt ID to execute. |
+
+Optional flags:
+
+| Flag | Meaning |
+| --- | --- |
+| `--config <path>` | Application configuration file. |
+| `--config-overlay <name>` | Selected application configuration overlay. |
+| `--prompt-dir <dir>` | Prompt-definition directory override. |
+| `--profile-dir <dir>` | Custom profile-directory override. |
+| `--schema-dir <dir>` | Schema base-directory override. |
+| `--prompt-version <version>` | Optional prompt-definition version selector. |
+| `--profile <id>` | Execution-profile override. |
+| `--session-id <id>` | Optional direct session identifier. |
+| `--input name=path` | Optional input file mapping; repeat or use comma-separated mappings. |
+| `--var name=value` | Template-variable mapping; repeat or use comma-separated mappings. |
+| `--out <path>` | Write generated content to this file instead of stdout. |
+| `--execution-report <path>` | Write an opt-in terminal execution report as newline-terminated JSON to a separate file. |
+| `--llm-base-url <url>` | Runtime endpoint override. |
+| `--model <name>` | Runtime model override. |
+| `--api-key-env <name>` | Runtime API-key environment-variable name override. |
+| `--temperature <float>` | Runtime temperature override. |
+| `--max-tokens <int>` | Runtime maximum-token override. |
+| `--top-p <float>` | Runtime top-p override. |
+| `--reasoning-effort <value>` | Runtime reasoning-effort override. |
+| `--timeout <duration>` | Runtime timeout override using Go duration syntax. |
+| `--run-timeout <duration>` | Optional whole-run engine deadline using Go duration syntax; zero or omission adds no deadline, negative values are invalid. |
+| `--transient-retries <integer>` | Nonnegative additional transient attempt count for this request; `0` disables additional attempts. |
+
+Deprecated aliases: `--prompt-id` for `--prompt`, and `--profile-id` for
+`--profile`.
+
+Omitted numeric runtime flags preserve the selected effective value; explicit
+zero values override it. `--timeout 0s` disables the per-attempt generation deadline
+only; the caller context and configured transport cap remain active. CLI
+durations are converted to whole seconds by truncation toward zero, so any
+duration whose absolute value is below one second becomes an explicit
+zero-second override. The timeout layers are defined in the
+[Promptkit outbound integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/integrations/openai-compatible-chat.md#timeout-and-cancellation).
+With the built-in client, each transient retry gets a fresh generation timeout;
+this flag does not limit the complete run.
+`--run-timeout` keeps subsecond precision and starts immediately before engine
+execution. It bounds preparation, capacity waits, retry waits, generation, and
+repairs where they honor context. Parsing, engine construction, and output
+writes are outside that interval. A failed run whose execution context reaches
+this deadline exits 1 with a safe deadline diagnostic; a completed invalid
+output still exits 2. It does not promise immediate interruption of synchronous
+work.
+Omitting `--transient-retries` inherits the application setting or Promptkit's
+current default of two additional attempts. The flag overrides only this
+request; it does not alter the configured engine. Structural repair generations
+have separate transient retry budgets.
+
+There is no raw API-key flag. Use `--api-key-env`.
+
+`--prompt-version` is passed directly to Promptkit. When it is omitted, the
+selected prompt ID must have exactly one available version. `--input` is
+optional at the CLI boundary: Promptkit decides whether the selected definition
+requires declared inputs or template-referenced values.
+
+`--session-id` supplies a direct, non-secret session identifier. A nonblank
+value replaces a definition-rendered session ID; an omitted or blank value lets
+the definition supply one. Promptkit trims direct values and limits them to 256
+Unicode code points. Use stable, non-sensitive identifiers because effective
+session IDs may appear in prepared output, run metadata, and provider-facing
+requests.
+
+`--reasoning-effort` is presence-aware: omitting it inherits the selected
+profile value, a nonblank value replaces that value, and
+`--reasoning-effort=` explicitly clears inherited reasoning. Promptkit treats
+nonblank values as provider-specific opaque strings.
+
+### Execution report file
+
+`--execution-report` requires a nonempty path. It is available only for `run`;
+`-` is an ordinary filename. Parent directories are not created. An existing
+file is replaced through ordinary file writing, without rollback or an atomic
+replacement guarantee. Generated content still goes to stdout or `--out`.
+Equal output/report paths, including existing paths that refer to the same
+file, are rejected before execution.
+
+The file is written after engine execution when Promptkit supplies a terminal
+event, including for a failed run or invalid generated output. A failure before
+invocation leaves the report path untouched. If no terminal event is supplied,
+Scriptorium leaves the path untouched and emits a diagnostic; an existing file
+may therefore contain an older report. Artifact output is attempted first on a
+successful run, and report writing is attempted even if artifact writing fails.
+Any output or report write failure exits 1; already-written output is not
+undone. Without a write failure, the actual run keeps its usual exit status.
+
+The [HTTP API reference](api.md#execution-report) defines the shared report
+fields and usage-presence semantics. The file contains that JSON object followed
+by a newline.
+
+The report excludes content, credentials, URLs, headers, and raw errors, but
+its identifiers can still be sensitive. The caller owns file retention and
+access.
+
+## `scriptorium render`
+
+```text
+scriptorium render [flags]
+```
+
+`--prompt <id>` is required. The following optional flags are supported:
+`--config`, `--config-overlay`, `--prompt-dir`, `--profile-dir`, `--schema-dir`, `--prompt-version`, `--profile`,
+`--input`, `--var`, `--out`, `--llm-base-url`,
+`--model`, `--api-key-env`, `--temperature`, `--max-tokens`, `--top-p`,
+`--reasoning-effort`, `--session-id`, `--timeout`, `--transient-retries`, and `--format text|json`. Their meanings match the corresponding
+`run` flags; `--format` selects prepared-run output and otherwise uses
+`defaults.render_format`.
+
+The same deprecated aliases and numeric/timeout behavior as `run` apply.
+The same session and reasoning inheritance, replacement, and clearing behavior
+also applies.
+`render` validates the retry override but does not generate model output or
+include a retry field in prepared output.
+`render` resolves profiles and schemas as part of preparation but
+does not call an LLM.
+
+## `scriptorium serve`
+
+```text
+scriptorium serve [flags]
+```
+
+Optional flags:
+
+| Flag | Meaning |
+| --- | --- |
+| `--config <path>` | Application configuration file. |
+| `--config-overlay <name>` | Selected application configuration overlay. |
+| `--addr <listen-address>` | HTTP listen-address override. |
+| `--prompt-dir <dir>` | Prompt-definition directory override. |
+| `--profile-dir <dir>` | Custom profile-directory override. |
+| `--schema-dir <dir>` | Schema base-directory override. |
+| `--artifact-root <dir>` | Root for HTTP `file` input references. |
+| `--max-request-bytes <n>` | Maximum encoded HTTP request-body bytes; `0` disables the limit. |
+| `--max-artifact-bytes <n>` | Maximum HTTP file-input artifact bytes; `0` disables the limit. |
+| `--max-response-bytes <n>` | Maximum encoded HTTP response bytes; `0` disables the limit. |
+
+`serve` accepts no runtime model override flags. HTTP request fields, response
+schemas, and error codes are defined in the [HTTP API reference](api.md).
+
+## `scriptorium inspect prompt`
+
+```text
+scriptorium inspect prompt --prompt ID [--prompt-version VERSION]
+    [--config PATH] [--config-overlay NAME] [--prompt-dir DIR] [--format text|json] [--out PATH]
+```
+
+`--prompt` is required. Inspection uses normal configuration discovery and a
+`--prompt-dir` override, defaults to text regardless of `defaults.render_format`,
+and writes to stdout unless `--out` is supplied. It loads and normalizes the
+selected definition but does not resolve a profile, load a schema, render a
+template, reserve backend capacity, or call a model.
+
+## `scriptorium inspect profile`
+
+```text
+scriptorium inspect profile --profile ID
+    [--config PATH] [--config-overlay NAME] [--profile-dir DIR] [--format text|json] [--out PATH]
+```
+
+`--profile` is required; built-in profiles need no prompt directory. Inspection
+resolves profile inheritance and backend defaults, but never reads a credential
+value, loads a prompt, reserves capacity, or calls a model. Unset provider
+controls are shown as zero values when Promptkit leaves them unspecified.
+
+## Application configuration inspection
+
+```text
+scriptorium config validate [flags]
+scriptorium config show [flags]
+scriptorium config sources [flags]
+scriptorium config explain --path JSON_POINTER [flags]
+```
+
+Each accepts `--config`, `--config-overlay`, `--prompt-dir`, `--profile-dir`,
+`--schema-dir`, `--addr`, `--artifact-root`, `--max-request-bytes`,
+`--max-artifact-bytes`, and `--max-response-bytes`. These are application
+configuration selectors and overrides; request, credential, backend-editing,
+output-format, and output-file flags are not accepted. Positional arguments
+are rejected.
+
+`validate` writes no success output; status 0 means the application configuration
+loaded and passed its own validation. It does not establish that a prompt
+directory exists, credentials are present, or Promptkit can construct an
+engine. `show` writes ConfigKit's resolved, redacted YAML snapshot. `sources`
+writes one newline-terminated JSON array of source records in load order. Each
+record has `id`, `label`, and `layer`, plus `path` when available; explicit CLI
+overrides appear as synthetic sources. Defaults-only input without overrides
+produces `[]` for `sources`.
+
+`explain` requires an explicitly supplied `--path` in JSON Pointer syntax.
+The empty string selects the root; `/server/addr` selects a field; `~1` and
+`~0` escape `/` and `~` inside mapping keys. Numeric tokens are interpreted
+according to the containing mapping or sequence. Dotted paths, file paths,
+and URL fragments are not accepted. ConfigKit writes a human-readable account
+of the effective value and its chronological default, base, overlay, CLI,
+and normalization history, including removed historical values. This is not a
+JSON schema or a byte-for-byte stable prose format. Unknown and malformed paths
+exit 1 without successful explanation output.
+
+Diagnostics and warnings go to stderr, never into successful stdout. Parse,
+load, output, and diagnostic-write failures exit 1. Ordinary output writes may
+leave partial data on failure. The inspection output can contain paths,
+identifiers, `api_key_env` reference names, and ordinary `extra_params` values,
+including displaced historical values in explanations;
+protect it accordingly. Raw API-key values are not read or emitted by these
+commands.
+
+## Input And Variable Syntax
+
+`--input name=path` maps an input name to a local file; `--var name=value`
+maps a template variable to a string. Both flags can be repeated or contain
+comma-separated mappings. Values may contain `=` after the first separator.
+Empty names and values are rejected.
+
+CLI inputs are file references. HTTP inline inputs are defined by the
+[HTTP API reference](api.md).
+
+## Output And Exit Behavior
+
+- `run` writes generated content to stdout, or to `--out` when supplied, and
+  writes a concise summary to stderr. The summary includes `backend=<id>` when
+  Promptkit selected a backend; endpoint-only profiles omit it.
+- `render` writes prepared-run output to stdout, or to `--out` when supplied,
+  without a success summary. Text output includes `selected_backend_id` after
+  `selected_profile_id` when Promptkit selected one; endpoint-only profiles
+  omit it.
+- `serve` writes startup and server errors to stderr.
+
+Exit statuses:
+
+| Status | Meaning |
+| --- | --- |
+| `0` | Success. |
+| `1` | Parse, configuration, loading, rendering, generation, output-write, or other runtime error. |
+| `2` | `run` generated and wrote output, but validation failed. |
+
+A backend admission rejection is a runtime error and prints `run error: model
+backend capacity is exhausted`. The HTTP capacity response is defined in the
+[HTTP API reference](api.md).
+
+## Workflows And Examples
+
+The [maintained render script](../examples/render-markdown-summary.sh) is a
+copyable render workflow. The [HTTP request example](../examples/http-run.json)
+is for a running `serve` process.

docs/config.md

@@ -0,0 +1,207 @@
+# Configuration Reference
+
+This is the canonical reference for Scriptorium application settings. Prompt,
+profile, schema, execution-setting, built-in profile, and framework credential
+semantics are defined by the
+[Promptkit v0.11.0 format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md).
+For command syntax, see the [CLI reference](cli.md); for HTTP request shapes and
+outcomes, see the [HTTP API reference](api.md).
+
+## Discovery And Precedence
+
+Application settings are resolved in this order:
+
+1. built-in Scriptorium defaults;
+2. a configuration file; then
+3. CLI overrides.
+
+When `--config` is omitted, Scriptorium searches
+`/usr/local/etc/scriptorium/config.yml` and then `/etc/scriptorium/config.yml`.
+If neither exists, it uses built-in defaults. An explicit `--config` path must
+exist and decode successfully.
+
+The maintained [minimal configuration](../examples/config.yml),
+[complete configuration](../examples/config.full.yml), and
+[composed configuration](../examples/config.composed.yml) are copyable examples.
+
+## Application Configuration File
+
+Configuration is decoded by ConfigKit v0.4.0 as strict YAML. Unknown fields,
+empty files, multiple YAML documents, and YAML aliases/anchors are rejected.
+An explicit empty string is a value: it clears a file-provided optional path
+or, for required `prompt_dir`, fails the command's prerequisite. A scalar
+`null` is not an empty string and is rejected for scalar fields; nullable
+fields such as `transient_retries` retain their documented meaning. Raw
+API-key fields are not accepted.
+
+ConfigKit applies defaults, the selected file, then only explicitly supplied
+application CLI flags before validating the result. Paths in the application
+document remain relative to the process working directory, not to the file's
+directory. Load diagnostics are printed safely on stderr; invalid application
+configuration exits with status 1.
+
+### Explicit imports and selected overlays
+
+A file-backed configuration may declare `configkit.imports` with relative
+`path` or `glob` entries. Each entry is explicit; Scriptorium does not scan
+for fragments on its own. ConfigKit composes the selected file and imports by
+conflict, so two fragments cannot define the same field merely to establish
+precedence. A required missing import fails; an entry may use
+`optional: true` to suppress target nonexistence. Imports are resolved from
+the declaring file's canonical directory and remain within the selected
+file's canonical directory by default. Scriptorium does not widen that root.
+
+`--config-overlay NAME` selects one file at `overlays/NAME.yml` below that
+root. The name must use letters, digits, `_`, or `-`; it is not a path. Empty
+and exact lowercase `default` select no overlay. There is no fallback,
+case folding, inherited stack, or automatic selection; a missing selected
+overlay fails. ConfigKit merges mapping fields and replaces other values,
+including sequences and explicit nulls, before applying explicit CLI flags.
+An active overlay needs a selected base file. No-source defaults-only loads
+cannot use imports or an active overlay.
+
+The [composed example](../examples/config.composed.yml) imports two fragments
+and has a selectable [local overlay](../examples/overlays/local.yml). From the
+repository root:
+
+```bash
+go run ./cmd/scriptorium render \
+  --config ./examples/config.composed.yml --config-overlay local \
+  --prompt generic.markdown_summary \
+  --input transcript=./examples/fixtures/transcript.md \
+  --input glossary=./examples/fixtures/glossary.yml
+```
+
+Import and overlay file locations are constrained by ConfigKit;
+*application path values* such as `prompt_dir` remain relative
+to the process working directory even when authored in a fragment or overlay.
+These source constraints are separate from HTTP artifact containment.
+
+| Field | Default | Meaning |
+| --- | --- | --- |
+| `prompt_dir` | unset | Promptkit prompt-definition source directory. `run`, `render`, `serve`, and `inspect prompt` require an effective value. |
+| `profile_dir` | unset | Optional custom Promptkit profile source directory overlaid on Promptkit built-ins. |
+| `schema_dir` | `.` | Promptkit schema source directory for relative schema paths. |
+| `server.addr` | `:8080` | Address used by `serve`. |
+| `server.artifact_root` | unset | Root that enables HTTP `file` input references. |
+| `server.max_request_bytes` | `16777216` | Maximum encoded HTTP request-body bytes; `0` disables the limit. |
+| `server.max_artifact_bytes` | `16777216` | Maximum HTTP file-input artifact bytes; `0` disables the limit. |
+| `server.max_response_bytes` | `16777216` | Maximum encoded HTTP response bytes; `0` disables the limit. |
+| `defaults.render_format` | `text` | Default prepared-run output format: `text` or `json`. |
+| `backends` | unset | Optional mapping of custom Promptkit backend IDs to engine-scoped connection and capacity settings. |
+| `transient_retries` | Promptkit default | Optional nonnegative count of additional built-in transient generation attempts. Omitted or `null` delegates to Promptkit; `0` disables additional attempts. |
+
+The size fields must be zero or greater. The [HTTP API](api.md) defines how
+each limit is enforced and reported. `server.artifact_root` configures an HTTP
+deployment boundary; see [operations](operations.md) for deployment handling.
+
+The `config validate`, `config show`, `config sources`, and `config explain`
+commands inspect this
+application configuration without creating a Promptkit engine. `show` is a
+resolved inspection snapshot, not necessarily a reloadable file. Application
+validation does not check framework sources, backend connectivity, or credential
+availability. `api_key_env` is an environment-variable *name* and remains
+visible in inspection; its environment value is never read by ConfigKit.
+Ordinary backend `extra_params` values also remain visible, so keep secrets out
+of those fields and protect inspection output as potentially sensitive.
+`config explain --path /server/addr` uses JSON Pointer syntax to show the
+selected field's current value and history from defaults, files, overlays,
+explicit CLI overrides, and normalization. `--path ''` selects the root.
+History includes replaced and removed values; `show` presents the final
+resolved snapshot. Neither renderer looks up credential bytes, and neither
+claims to identify arbitrary secrets in unclassified parameter values.
+
+## Custom Backends
+
+Use `backends` when a profile selects an application-defined backend ID:
+
+```yaml
+backends:
+  local-gpu:
+    endpoint: http://localhost:11434/v1
+    api_key_env: LOCAL_GPU_API_KEY
+    extra_params:
+      provider_option: enabled
+    concurrency_limit: 2
+    queue_capacity: 0
+```
+
+Each mapping key is the case-sensitive backend ID. `endpoint` is required;
+`api_key_env`, `extra_params`, `concurrency_limit`, and `queue_capacity` are
+optional. `concurrency_limit: 0` leaves the backend unlimited. Omitting
+`queue_capacity` lets Promptkit use its default for a limited backend, while
+an explicit `queue_capacity: 0` disables queueing.
+
+Configuration strictly owns the YAML shape and rejects unknown fields. Promptkit
+validates backend IDs, endpoints, environment-variable names, extra parameters,
+and capacity relationships when Scriptorium constructs its engine. There are no
+backend command-line overrides. Store only an environment-variable name in
+`api_key_env`; raw API-key fields are not accepted.
+
+## Framework Source Mapping
+
+Scriptorium passes `prompt_dir`, `profile_dir`, and `schema_dir` to Promptkit
+when constructing its engine. Scriptorium does not redefine or independently
+parse those framework file formats.
+
+- Prompt selection, versions, message templates, inputs, output contracts, and
+  session IDs are Promptkit contracts.
+- Profile fields, numeric ranges, execution defaults, overlay precedence,
+  built-in profiles, and credential rules are Promptkit contracts.
+- Schema path behavior and generated-content validation are Promptkit
+  contracts.
+
+See the
+[tagged Promptkit format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md)
+for all of those definitions. The files under
+[`examples/prompts`](../examples/prompts/),
+[`examples/profiles`](../examples/profiles/), and
+[`examples/schemas`](../examples/schemas/) are maintained Scriptorium
+application inputs using that tagged format.
+
+Promptkit supplies the opt-in profile IDs `promptkit-openrouter-standard` and
+`promptkit-openrouter-auto`. They can be selected as a prompt default or request
+profile, and custom profile sources retain precedence. Their effective model
+settings may change with a catalog upgrade; use a complete application-owned
+profile when fixed settings are required. See the tagged format reference for
+the maintained-profile contract.
+
+## Credentials And Outbound Behavior
+
+Scriptorium maps `--api-key-env` and HTTP `model.api_key_env` into Promptkit
+request overrides. Keep secret values in environment variables and store only
+their names in configuration or framework source files. Do not place raw keys
+in configuration, prompts, profiles, CLI arguments, examples, or HTTP
+payloads.
+
+An optional `api_key_env` whose environment value is absent or empty can result
+in an unauthenticated provider request. A profile that declares credentials
+required still fails as an invalid request when no credential source is
+selected, and fails with `ErrAPIKeyEnvMissing` when its selected environment
+source is absent or empty. Scriptorium never reads or emits the environment
+value itself.
+
+Unset optional provider controls are omitted from compatible provider requests.
+A positive Promptkit `repair_attempts` budget can add provider calls, latency,
+token use, and cost; see the tagged format reference for its permitted values
+and validation-mode requirements.
+
+Promptkit's built-in client makes up to two additional attempts for eligible
+transient HTTP statuses by default. The application `transient_retries` setting
+changes that budget for its constructed engine; an explicit `run` request
+override takes precedence. This can increase latency, request count, and cost.
+Each initial or repair generation has its own transient budget; an injected
+client retains its own retry behavior. The tagged integration contract owns
+eligibility and timing.
+
+Promptkit's
+[OpenAI-compatible integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/integrations/openai-compatible-chat.md)
+defines outbound authentication, provider request mapping, transport limits,
+and timeout layering.
+
+## Related References
+
+- [CLI reference](cli.md)
+- [HTTP API reference](api.md)
+- [Operations guide](operations.md)
+- [Promptkit framework formats](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md)

docs/config/config-yml.md

@@ -1,48 +0,0 @@
-# Main `config.yml`
-
-`config.yml` defines application-level defaults used by CLI commands.
-
-By default, Scriptorium looks for `/usr/local/etc/scriptorium/config.yml` and, if not present, then for `/etc/scriptorium/config.yml`. You can also pass `--config PATH`.
-
-## Complete Example
-
-```yaml
-prompt_dir: ./prompts
-profile_dir: ./profiles
-schema_dir: ./schemas
-
-server:
-  addr: :8080
-
-defaults:
-  render_format: text
-```
-
-## Available Options
-
-- `prompt_dir` (optional): Default directory for prompt definition YAML files.
-- `profile_dir` (optional): Default directory for execution profile YAML files.
-- `schema_dir` (optional): Base directory for JSON schema files used by `json_schema` validation.
-
-### `server`
-
-- `addr` (optional): HTTP server listen address for `scriptorium serve`.
-
-### `defaults`
-
-- `render_format` (optional): Default output format for `scriptorium render`.
-- Allowed values: `text`, `json`.
-
-## Precedence
-
-For run/render/serve settings, precedence is:
-
-1. Explicit CLI flags
-2. `config.yml`
-3. Built-in defaults
-
-## Notes and Rules
-
-- Unknown YAML fields fail to load (strict decoding).
-- This file does not accept API keys.
-- `config.yml` sets directory/server defaults only; prompt/profile content remains in their own files.

docs/config/profile-definitions.md

@@ -1,41 +0,0 @@
-# Execution Profile Definitions
-
-Execution Profiles define **how** Scriptorium calls an LLM endpoint.
-
-A profile file is YAML, typically stored under `profiles/`, for example `profiles/local-quality.yaml`.
-
-## Complete Example
-
-```yaml
-id: local-quality
-endpoint: http://localhost:8000/v1
-model: gpt-4.1
-temperature: 0.0
-max_tokens: 1200
-top_p: 1.0
-timeout_seconds: 180
-reasoning_effort: medium
-api_key_env: SCRIPTORIUM_API_KEY
-extra_params:
-  provider: openrouter
-  route: fallback
-```
-
-## Available Options
-
-- `id` (required): Unique profile identifier used by `--profile` or prompt `default_profile`.
-- `endpoint` (required): OpenAI-compatible base URL, usually ending in `/v1`.
-- `model` (required): Model name to request at that endpoint.
-- `temperature` (optional): Sampling temperature. Valid range is `0` to `2`.
-- `max_tokens` (optional): Max completion tokens. Must be `>= 0`.
-- `top_p` (optional): Nucleus sampling parameter. Valid range is `0` to `1`.
-- `timeout_seconds` (optional): Request timeout in seconds. Must be `>= 0`.
-- `reasoning_effort` (optional): Provider/model-specific reasoning level string.
-- `api_key_env` (optional): Environment variable name that holds the API key.
-- `extra_params` (optional): String key/value map for provider-specific parameters.
-
-## Notes and Rules
-
-- Raw API keys are not supported. Do **not** add `api_key` fields.
-- Unknown YAML fields fail to load (strict decoding).
-- If `api_key_env` is set, the environment variable must be present when the run executes.

docs/config/prompt-definitions.md

@@ -1,73 +0,0 @@
-# Prompt Definition Files
-
-Prompt Definitions define **what** Scriptorium should do.
-
-A prompt file is YAML, typically stored under `prompts/`, for example `prompts/generic.structured_events.yaml`.
-
-## Complete Example
-
-```yaml
-id: generic.structured_events
-version: "1.0.0"
-default_profile: local-quality
-description: Extract events from a transcript into structured JSON.
-
-inputs:
-  - name: transcript
-    required: true
-    content_type: text/markdown
-    description: Source transcript
-  - name: glossary
-    required: false
-    content_type: text/yaml
-    description: Optional glossary context
-
-messages:
-  - role: system
-    content: |
-      You are a structured extraction assistant.
-      Return only JSON.
-  - role: user
-    content_file: ./generic.structured_events.user.md
-
-output:
-  format: json
-  validation_mode: json_schema
-  schema_path: structured_events.schema.json
-  repair_attempts: 1
-```
-
-## Available Options
-
-- `id` (required): Prompt identifier used by `--prompt` / `prompt_id`.
-- `version` (required): Prompt version string.
-- `default_profile` (optional): Execution profile ID used when no explicit profile is provided.
-- `description` (optional): Human-readable description.
-
-### `inputs[]`
-
-- `name` (required): Logical input name referenced in templates via `{{input "name"}}`.
-- `required` (optional): If `true`, run fails when input is missing.
-- `content_type` (optional): Metadata only (not enforced yet).
-- `description` (optional): Human-readable input description.
-
-### `messages[]`
-
-- `role` (required): Message role such as `system` or `user`.
-- `content` (optional): Inline Go-template message body.
-- `content_file` (optional): Path to a template file.
-
-Each message must set **exactly one** of `content` or `content_file`.
-
-### `output`
-
-- `format` (required): One of `text`, `markdown`, `json`.
-- `validation_mode` (required): One of `none`, `basic`, `json`, `json_schema`.
-- `schema_path` (required when `validation_mode: json_schema`): Path to JSON Schema file.
-- `repair_attempts` (required): Number of bounded repair retries (`>= 0`).
-
-## Notes and Rules
-
-- Unknown YAML fields fail to load (strict decoding).
-- `content_file` paths are resolved relative to the prompt YAML file.
-- For `json_schema` validation mode, Scriptorium also sends provider-level structured output requests automatically.

docs/config/schema-definitions.md

@@ -1,82 +0,0 @@
-# JSON Schema Definition Files
-
-Schema definition files describe the expected JSON output contract for prompts that use:
-
-- `output.format: json`
-- `output.validation_mode: json_schema`
-
-Schema files are JSON, typically stored under `schemas/`, for example `schemas/structured_events.schema.json`.
-
-## Complete Example
-
-```json
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://example.com/schemas/structured-events.schema.json",
-  "title": "Structured Events",
-  "description": "Expected shape for extracted event output",
-  "type": "object",
-  "properties": {
-    "summary": {
-      "type": "string",
-      "minLength": 1,
-      "description": "High-level session summary"
-    },
-    "events": {
-      "type": "array",
-      "items": {
-        "type": "object",
-        "properties": {
-          "title": { "type": "string" },
-          "type": {
-            "type": "string",
-            "enum": ["discovery", "combat", "social", "travel", "downtime", "other"]
-          },
-          "notes": { "type": "string" }
-        },
-        "required": ["title", "type"],
-        "additionalProperties": false
-      },
-      "minItems": 0
-    }
-  },
-  "required": ["summary", "events"],
-  "additionalProperties": false,
-  "$defs": {
-    "nonEmptyString": {
-      "type": "string",
-      "minLength": 1
-    }
-  }
-}
-```
-
-## Available Options
-
-Scriptorium does not define custom schema keywords. It expects a valid JSON Schema document and passes it to the validator/provider.
-
-Commonly used JSON Schema options include:
-
-- `$schema`: Draft identifier URI.
-- `$id`: Schema identifier URI.
-- `title`: Human-readable schema title.
-- `description`: Human-readable schema description.
-- `type`: Expected JSON type (`object`, `array`, `string`, etc.).
-- `properties`: Object field definitions.
-- `required`: Required object fields.
-- `additionalProperties`: Whether undeclared fields are allowed.
-- `items`: Array item schema.
-- `enum`: Allowed literal values.
-- `const`: Single allowed literal value.
-- `oneOf`, `anyOf`, `allOf`: Composition rules.
-- `minimum`, `maximum`: Numeric bounds.
-- `minLength`, `maxLength`, `pattern`: String constraints.
-- `minItems`, `maxItems`: Array constraints.
-- `$defs`: Reusable local definitions.
-- `$ref`: Reference to another schema/definition.
-
-## Notes and Rules
-
-- Schema path comes from prompt `output.schema_path` and is resolved relative to `schema_dir`.
-- If schema loading fails for `json_schema` mode, the run fails before the LLM request.
-- Keep schemas strict (`additionalProperties: false`) when you want predictable output shape.

docs/consumers/api.md

@@ -0,0 +1,38 @@
+# Consumer Integration Overview
+
+Scriptorium exposes executable interfaces. Choose between a local subprocess
+and the HTTP service according to the boundary your application needs.
+
+| Interface | Use when |
+| --- | --- |
+| CLI subprocess | The consumer needs a synchronous local process boundary or prepared output. |
+| HTTP API | The consumer needs a service boundary or remote access. |
+
+- CLI subprocess: [subprocess integration](../integrations/subprocess.md)
+- HTTP service: [HTTP API reference](../api.md)
+- Application configuration: [configuration reference](../config.md)
+
+Go applications that need an in-process prompt framework should import
+Promptkit directly. The tagged
+[Promptkit Go consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md)
+owns that interface; Scriptorium does not provide a Go library package.
+Consumers arriving from the former Scriptorium Go API should follow the
+[migration guide](migrating-to-promptkit.md).
+
+## Consumer Responsibilities
+
+Consumers are responsible for:
+
+- selecting and deploying prompt, profile, and schema assets;
+- supplying required inputs and template variables;
+- supplying credentials through the chosen interface;
+- protecting rendered prompts and generated artifacts as potentially
+  sensitive;
+- deciding whether validation-failed output is usable; and
+- retrying only when another model call is acceptable.
+
+Scriptorium does not persist run state. A retry can produce different output
+and can incur another provider request. CLI exits belong to the
+[CLI reference](../cli.md), HTTP status behavior belongs to the
+[HTTP API reference](../api.md), and framework semantics belong to
+[Promptkit v0.11.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md).

docs/consumers/migrating-to-promptkit.md

@@ -0,0 +1,109 @@
+# Migrate From Scriptorium To Promptkit
+
+## Supported Migration Boundary
+
+Scriptorium `v0.11.1` at
+`gitea.maximumdirect.net/eric/scriptorium` is the final release that provides
+the former in-process Go framework. Promptkit `v0.11.0` at
+`gitea.maximumdirect.net/eric/promptkit` is the destination for that framework
+API. Scriptorium `v0.12.0` and later provide the CLI and HTTP application only.
+
+There is no Scriptorium compatibility facade, alias package, forwarding
+package, or deprecated wrapper. A consumer that cannot migrate may remain
+pinned to Scriptorium `v0.11.1`, but that framework-bearing line does not
+provide the slim application release.
+
+## Update A Go Consumer
+
+Start from a clean consumer checkout and review the pending diff before
+committing it. Add the published Promptkit module:
+
+```sh
+go get gitea.maximumdirect.net/eric/promptkit@v0.11.0
+```
+
+For an ordinary consumer that imports the former root package under its
+default name, replace the exact import and package qualifier, then format the
+changed Go files:
+
+```sh
+git grep -l \
+  '"gitea.maximumdirect.net/eric/scriptorium"' \
+  -- '*.go' |
+  while IFS= read -r go_file
+  do
+    perl -pi -e \
+      's{"gitea.maximumdirect.net/eric/scriptorium"}{"gitea.maximumdirect.net/eric/promptkit"}g; s{\bscriptorium\.}{promptkit.}g' \
+      "$go_file"
+    gofmt -w "$go_file"
+  done
+```
+
+Inspect the resulting diff. Consumers that used an import alias should retain
+or deliberately rename that alias instead of applying the qualifier
+replacement mechanically.
+
+Remove the now-unused Scriptorium requirement through module tidiness and run
+the consumer's complete tests:
+
+```sh
+go mod tidy
+go test ./...
+```
+
+Confirm that `go.mod` selects Promptkit `v0.11.0` and that no Go file imports
+the former Scriptorium package:
+
+```sh
+test "$(
+  go list -m -f '{{.Path}}@{{.Version}}' \
+    gitea.maximumdirect.net/eric/promptkit
+)" = 'gitea.maximumdirect.net/eric/promptkit@v0.11.0'
+if git grep -n \
+  'gitea.maximumdirect.net/eric/scriptorium' \
+  -- '*.go'
+then
+  printf '%s\n' 'a former Scriptorium Go import remains' >&2
+  exit 1
+fi
+```
+
+## Compatibility And Additions
+
+Promptkit preserves the established engine, request, result, profile,
+source-option, model-client, artifact, validation-value, and public-error
+shapes where practical. Exact declarations and current behavior belong to the
+tagged [Promptkit consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md)
+and Go source.
+
+Promptkit also includes migration-relevant public contracts that were not in
+Scriptorium `v0.11.1`:
+
+- [`WithArtifactReader`](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/engine.go#L169-L174)
+  and the
+  [`ArtifactReader` declaration](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/types.go#L315)
+  provide the artifact-reading extension described by the tagged
+  [extension-interface guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md#extension-interfaces).
+- [`ErrProfileRequired` and `ErrAPIKeyEnvMissing`](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/engine.go#L33-L48)
+  provide the specific identities described by the tagged
+  [error guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md#handle-errors).
+
+Use those tagged owners for exact signatures, wrapping guarantees, and
+extension behavior.
+
+## Verify Consumer Behavior
+
+Source compatibility is only the first check. Exercise the behavior the
+consumer actually relies upon, especially:
+
+- prompt, profile, and schema source selection;
+- direct and environment-based credentials;
+- caller, generation, and transport timeout layering;
+- output validation and validation-failure handling;
+- injected model-client and artifact-reader extensions; and
+- every `errors.Is` branch used for recovery or classification.
+
+Also verify any serialized values, redaction expectations, filesystem policy,
+and provider integration behavior that crosses the consumer's own boundary.
+Promptkit owns the in-process framework contract; Scriptorium owns only its
+executable CLI and HTTP application interfaces.

docs/development.md

@@ -0,0 +1,59 @@
+# Development
+
+This is the contributor entry point for Scriptorium. Scriptorium is an
+application that consumes the public
+[Promptkit v0.11.0 package](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md);
+framework implementation work belongs in Promptkit. Application configuration
+uses ConfigKit v0.4.0; keep Scriptorium's schema and source selection local.
+
+## Initial Orientation
+
+Before recommending, planning, or implementing work:
+
+1. read the [agent policy](policy/agents.md);
+2. inspect the working tree and preserve unrelated changes;
+3. read the [architecture policy](policy/architecture.md);
+4. follow the task-specific contracts and internal documents below; and
+5. inspect the relevant implementation and tests before changing them.
+
+Also read the [documentation policy](policy/documentation.md) before changing
+documentation and the [testing policy](policy/testing.md) before changing
+tests.
+
+## Task-Specific Reading Guide
+
+| Task | Read before changing |
+| --- | --- |
+| Repository orientation or component responsibility | [Internal component overview](internal/overview.md) and [architecture policy](policy/architecture.md) |
+| CLI commands, flags, output, or exit behavior | [CLI contract](cli.md) and [adapter internals](internal/adapters.md) |
+| HTTP routes, DTOs, limits, status mapping, or artifact policy | [HTTP API contract](api.md), [adapter internals](internal/adapters.md), and [source internals](internal/sources.md) |
+| Application configuration or precedence | [Configuration contract](config.md), [adapter internals](internal/adapters.md), [source internals](internal/sources.md), and `internal/config` definition/load tests |
+| Prepared-run presentation | [CLI contract](cli.md), [adapter internals](internal/adapters.md), and `internal/format` |
+| Prompt, profile, schema, generation, or validation semantics | [Promptkit framework formats](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md) and the [Promptkit consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md) |
+| OpenAI-compatible outbound behavior or timeout layering | [Promptkit integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/integrations/openai-compatible-chat.md) |
+| Subprocess behavior | [Subprocess integration](integrations/subprocess.md) and [CLI contract](cli.md) |
+| Runtime operation or recovery | [Operations](operations.md) |
+| Dependencies, copied assets, or attribution | The [OSS policy](policy/oss.md), [component attributions](oss/attribution.md), and [architecture policy](policy/architecture.md) |
+| Release documentation, packaging, or publication | The [release policy](policy/release.md), [OSS policy](policy/oss.md), [release procedure](release.md), [hosted release workflow](../.woodpecker/release.yml), and [architecture policy](policy/architecture.md) |
+| Examples or copyable assets | The owning Scriptorium contract, the relevant [Promptkit format contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md), and the related files under `examples/` |
+| Architecture decisions or future work | The [documentation policy](policy/documentation.md), relevant accepted ADRs, and relevant roadmap documents |
+
+Cross-project changes land and release in Promptkit before Scriptorium adopts
+the tagged version. Do not commit a Go workspace, local replacement, vendored
+Promptkit source, or an import of a Promptkit `internal` package.
+
+## Baseline Validation
+
+For code changes, run:
+
+```bash
+go test ./...
+go test -race ./...
+go vet ./...
+go build ./cmd/scriptorium
+```
+
+Check formatting with `gofmt`, run `git diff --check`, and validate affected
+examples and documentation links. Documentation-only work does not require
+unrelated new tests, but commands and examples changed by documentation must be
+run.

docs/integrations/narratio.md

@@ -1,322 +0,0 @@
-# Narratio -> Scriptorium CLI Integration
-
-## 1. Purpose
-
-This document defines how Narratio should invoke Scriptorium through the **public CLI**.
-
-This is a **subprocess integration contract**, not an internal Go API contract.
-
-## 2. Assumptions
-
-- `scriptorium` is installed and available on `PATH`.
-- Scriptorium is configured with `config.yml`.
-- `config.yml` provides `prompt_dir`, `profile_dir`, and `schema_dir` as needed.
-- Prompt and profile libraries are already deployed for the environment.
-- Narratio provides prepared artifact files (for example polished transcript, glossary, previous recap, campaign notes).
-- Initial integration is synchronous subprocess execution.
-- Narratio remains the orchestrator.
-
-In normal operation, Narratio does not need to pass `--prompt-dir` and `--profile-dir` if they are supplied by Scriptorium config.
-
-Narratio may pass `--config <PATH>` when it must use a non-default Scriptorium config file.
-
-## 3. Core Commands Narratio May Call
-
-Primary commands for subprocess integration:
-
-- `scriptorium run`
-- `scriptorium render`
-
-For production generation, use `scriptorium run`.
-
-`scriptorium render` is for debugging, dry-runs, test assertions, and validating command construction without LLM execution.
-
-Note: `scriptorium serve` and HTTP API exist, but they are not the initial integration path.
-
-## 4. Command Selection Guidance
-
-- Use `run` to generate an output artifact.
-- Use `render` to inspect the prepared prompt and effective settings without calling the LLM.
-- Use `render --format json` when Narratio/tests need structured prepare output.
-
-## 5. Recommended `run` Invocation Shape
-
-Production shape:
-
-```bash
-scriptorium run \
-  --prompt <prompt_id> \
-  --input transcript=<processed-transcript-path> \
-  --out <output-artifact-path>
-```
-
-Common optional additions:
-
-- `--config <path>`: use a specific Scriptorium config file.
-- `--profile <profile_id>`: override prompt default profile.
-- `--var name=value` (repeatable): small metadata values.
-- `--input name=path` (repeatable): additional named artifacts.
-- `--timeout <duration>`: per-run timeout override.
-- Runtime model override flags (`--llm-base-url`, `--model`, etc.) only for exceptional/operator-directed cases.
-
-## 6. Recommended `render` Invocation Shape
-
-Human-readable debug shape:
-
-```bash
-scriptorium render \
-  --prompt <prompt_id> \
-  --input transcript=<processed-transcript-path> \
-  --format text
-```
-
-Structured debug/test shape:
-
-```bash
-scriptorium render \
-  --prompt <prompt_id> \
-  --input transcript=<processed-transcript-path> \
-  --format json \
-  --out <render-debug-path>
-```
-
-`render` does **not** call the LLM, does **not** validate model output, and does **not** perform repair.
-
-## 7. Inputs
-
-- Pass inputs as repeated `--input name=path` flags.
-- `name` must match the Prompt Definition input name.
-- Prefer absolute paths, or paths relative to a working directory controlled by Narratio.
-- Pass Audita output as the primary transcript input.
-- Additional inputs may include glossary, previous recap, campaign notes, event logs, final state maps, or other prompt-specific artifacts.
-- Scriptorium reads input files directly; Narratio does not need to inline file content for CLI use.
-
-## 8. Variables
-
-Use repeated `--var name=value` for small metadata values.
-
-Typical examples:
-
-- `session_date`
-- `session_id`
-- `campaign_name`
-- `previous_session_id`
-- `output_kind`
-
-Large content belongs in input files, not `--var` values.
-
-## 9. Prompt IDs and Output Artifact Types
-
-Narratio should treat prompt IDs as configuration, not hardcoded business logic.
-
-Narratio config may map stage/output names to prompt IDs, for example:
-
-- session recap prompt
-- structured event extraction prompt
-- glossary suggestion prompt
-- player-facing summary prompt
-
-Prompt IDs used by Narratio should come from the deployed Scriptorium prompt library.
-
-## 10. Profiles
-
-- Prompts may declare `default_profile`.
-- Narratio may omit `--profile` to use prompt default profile.
-- Narratio may pass `--profile` to force profile selection.
-- This enables environment/profile selection like `local-fast`, `local-quality`, `frontier`, `batch`, or test profiles.
-- Profile names should generally be Narratio configuration values.
-
-## 11. Runtime Overrides
-
-Supported runtime override flags:
-
-- `--llm-base-url`
-- `--model`
-- `--api-key-env`
-- `--temperature`
-- `--max-tokens`
-- `--top-p`
-- `--timeout`
-
-Guidance:
-
-- Keep normal model/runtime settings in Execution Profiles.
-- Use runtime overrides only for explicit per-run exceptions, tests, or operator overrides.
-- Never pass raw API keys on the command line.
-- `--api-key-env` names an environment variable; Narratio must ensure that variable is set in subprocess environment.
-
-## 12. Config Behavior
-
-- Default config path: `/etc/scriptorium/config.yml`.
-- `--config <PATH>` overrides default path.
-- Missing default config is allowed by Scriptorium.
-- If `--config` is provided explicitly, the file must exist and be valid.
-- CLI flags override `config.yml`.
-- `config.yml` overrides built-in application defaults.
-
-Narratio can either:
-
-- rely on system default config path, or
-- carry an explicit config path and pass `--config`.
-
-## 13. Environment Handling
-
-Subprocess environment recommendations:
-
-- Pass through required API-key environment variables referenced by `api_key_env`.
-- Do not pass raw API keys as CLI arguments.
-- Avoid logging full environment dumps.
-- Capture stdout and stderr separately.
-- Use a controlled working directory.
-- Prefer absolute artifact paths.
-
-## 14. Output Handling
-
-For `scriptorium run`:
-
-- Use `--out` when Narratio needs durable artifact files.
-- Without `--out`, artifact content is written to stdout.
-- Preferred orchestration pattern: always use `--out`, then treat the file as stage output artifact.
-- Capture stderr for diagnostics.
-
-For `scriptorium render`:
-
-- Use `--out` to store render diagnostics.
-- Use `--format json` when tests need to inspect selected profile, effective runtime settings, input hashes, prompt hash, and rendered messages.
-
-## 15. Exit Status and Errors
-
-Current CLI behavior (verified from implementation/tests):
-
-- `0`: success.
-- `1`: runtime/parse/config/load/render/generation/IO error.
-- `2`: run completed but output validation failed (`ValidationFailed`).
-
-Additional details:
-
-- On `run`, output artifact write happens before exit code selection. If validation fails, artifact may still be written and exit code is `2`.
-- `stderr` carries both errors and normal run summary output; non-empty stderr alone does not imply failure.
-- `render` returns `0` on success and `1` on failures.
-
-Narratio should treat non-zero exit codes as failed stage execution, but may record generated artifact paths if a run exited `2` and output file exists.
-
-## 16. Recommended Narratio Integration Pattern
-
-1. Build CLI args from Narratio stage configuration.
-2. Use subprocess context cancellation/timeout.
-3. Pass absolute input paths.
-4. Pass `--out` to a session-scoped artifact path.
-5. Add `--var` metadata values.
-6. Optionally add `--config`.
-7. Optionally add `--profile`.
-8. Ensure required API-key env vars are present.
-9. Run subprocess synchronously.
-10. Capture stdout/stderr separately.
-11. On success, store output artifact path and invocation metadata in stage artifacts.
-12. On failure, store exit code and stderr diagnostics in stage status.
-
-## 17. Suggested Narratio Configuration Shape
-
-Illustrative (not required schema):
-
-```yaml
-scriptorium:
-  config_path: /etc/scriptorium/config.yml
-  stages:
-    session_recap:
-      prompt_id: dnd.session_recap
-      profile_id: local-quality   # optional
-      inputs: [transcript, glossary, previous_recap]
-      vars: [session_id, session_date, campaign_name]
-      output_path_template: artifacts/{session_id}/session_recap.md
-      timeout: 2m
-      render_debug: false
-```
-
-The key idea: map Narratio stage/artifact names to prompt ID, optional profile, expected inputs, and output destination.
-
-## 18. Testing Strategy for Narratio Integration
-
-- Use `scriptorium render --format json` to verify command construction without LLM calls.
-- Use dedicated test prompt/profile libraries for integration tests.
-- Use small fixture transcripts.
-- Verify missing-input failure behavior.
-- Verify prompt `default_profile` behavior.
-- Verify explicit `--profile` override behavior.
-- Verify `--config` behavior (default and explicit).
-- Verify output file creation when `--out` is used.
-- Verify stderr capture on failures.
-- Avoid real API keys in tests.
-
-## 19. Security and Privacy Notes
-
-- Never pass raw API keys on command line.
-- Do not log full rendered prompts by default; transcripts may contain sensitive content.
-- Avoid logging prompt content unless explicit debug mode is enabled.
-- Treat generated artifacts as potentially sensitive.
-- Use session-scoped, access-controlled output paths.
-- `api_key_env` names should come from environment management, not embedded secrets.
-
-## 20. Initial D&D Artifact Generation Examples
-
-These are examples only. Use prompt IDs from the deployed prompt library.
-
-Session recap:
-
-```bash
-scriptorium run \
-  --prompt dnd.session_recap \
-  --input transcript=/work/session-42/transcript.polished.md \
-  --input glossary=/work/session-42/glossary.yml \
-  --out /work/session-42/artifacts/session_recap.md
-```
-
-Structured events:
-
-```bash
-scriptorium run \
-  --prompt dnd.structured_events \
-  --input transcript=/work/session-42/transcript.polished.md \
-  --out /work/session-42/artifacts/structured_events.json
-```
-
-Glossary suggestions:
-
-```bash
-scriptorium run \
-  --prompt dnd.glossary_suggestions \
-  --input transcript=/work/session-42/transcript.polished.md \
-  --input previous_recap=/work/session-41/artifacts/session_recap.md \
-  --out /work/session-42/artifacts/glossary_suggestions.md
-```
-
-Player-facing summary:
-
-```bash
-scriptorium run \
-  --prompt dnd.player_summary \
-  --input transcript=/work/session-42/transcript.polished.md \
-  --input structured_events=/work/session-42/artifacts/structured_events.json \
-  --out /work/session-42/artifacts/player_summary.md
-```
-
-## 21. Non-Goals
-
-Initial Narratio integration should not:
-
-- call Scriptorium internal Go packages
-- use HTTP API as the primary path
-- expect Scriptorium to read S3 refs directly
-- make Scriptorium responsible for Narratio stage state
-- make Scriptorium responsible for notification
-- require Scriptorium to understand D&D workflow semantics beyond prompt definitions
-
-## 22. Future Extension Notes
-
-Possible later extensions:
-
-- HTTP API integration
-- S3 artifact references if Scriptorium adds S3 reader support
-- storing render diagnostics alongside generated artifacts
-- token budgeting/prompt-size checks
-- batch execution if Scriptorium later adds batch support

docs/integrations/subprocess.md

@@ -0,0 +1,63 @@
+# Subprocess Integration
+
+This document covers process-boundary behavior for callers that invoke
+Scriptorium as a child process. Command syntax, flags, output, and exit codes
+are defined by the [CLI reference](../cli.md). Interface selection belongs in
+the [consumer integration overview](../consumers/api.md).
+
+## Process Contract
+
+Use `scriptorium render` when the caller needs prepared output without a model
+call, and `scriptorium run` for generation. Pass an explicit `--config` or
+make the configuration search paths available to the child process; configuration
+discovery, fields, profile selection, and credential mechanisms are defined in
+the [configuration reference](../config.md).
+
+Pass required API-key environment variables through the child environment. Do
+not place raw API keys in arguments. Keep the environment limited to the values
+needed for the selected profile.
+
+For application-only preflight, invoke `scriptorium config validate`; it exits
+0 with empty stdout when the application configuration loads, but does not
+prove that Promptkit sources or credentials are usable. `config show` emits
+resolved YAML and `config sources` emits newline-terminated JSON provenance.
+All three use the same source selection and explicit overrides as execution
+commands and require separate stderr capture for diagnostics. Their output can
+include source paths, identifiers, credential reference names, and ordinary
+backend parameters; treat it as potentially sensitive.
+
+## Streams And Output Ownership
+
+Capture stdout and stderr separately. Stdout contains the requested artifact or
+prepared output unless the caller selects an output file; stderr contains
+summaries, diagnostics, and server messages. The exact destinations and status
+meanings are part of the [CLI reference](../cli.md), not a stable stderr data
+protocol.
+
+When using `--out`, the caller owns the output path, its permissions, and
+cleanup. Treat rendered prompts, generated artifacts, stdout, and stderr as
+potentially sensitive.
+
+For `run`, an optional [execution report file](../cli.md) contains terminal
+metadata separate from generated stdout or `--out`. The caller owns that
+path's permissions and retention. Output and report files are not a
+transaction: one may be written when the other fails, and a preexisting report
+may remain when the invocation has no terminal event. Check the exit status
+and diagnostics rather than assuming a report path contains this run's data.
+
+## Cancellation And Recovery
+
+A CLI invocation performs one synchronous request and creates no durable run
+state. A supervising process that needs cancellation must terminate the child
+process according to its own process-management policy. A later invocation is a
+new request and can make another model call; there is no resume or checkpoint
+protocol.
+
+For `run`, callers may set the [whole-run deadline](../cli.md) to bound the
+engine invocation. It is separate from the per-attempt generation timeout and
+does not include child startup or output writing. A deadline failure exits 1;
+supervisors still own process termination when they need to stop the child
+outside that engine interval.
+
+For deployment, filesystem permissions, and sensitive-artifact handling, see
+the [operations guide](../operations.md).

docs/internal/adapters.md

@@ -0,0 +1,136 @@
+# Adapter Internals
+
+## Purpose
+
+Scriptorium adapters translate executable inputs into Promptkit public requests
+and translate Promptkit results or errors back to CLI or HTTP behavior. They
+own IO and presentation mechanics, not framework decisions.
+
+External contracts are canonical in the [CLI reference](../cli.md) and
+[HTTP API reference](../api.md). Promptkit's public engine contract is
+described by its tagged
+[Go consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md).
+
+## Components And Collaborators
+
+- `cmd/scriptorium` passes process arguments and streams to
+  `internal/adapter/cli`.
+- `internal/adapter/cli` resolves settings through `internal/config`,
+  constructs `promptkit.Engine`, maps CLI values to `promptkit.RunRequest`,
+  and owns output files, summaries, and exit codes.
+- `internal/config` delegates application YAML decoding, default resolution,
+  overrides, and validation ordering to ConfigKit. The CLI supplies only
+  explicitly visited application flags as overrides and renders safe structured
+  load diagnostics on stderr.
+- `internal/adapter/http` strictly decodes request DTOs, maps them to Promptkit
+  public values, calls its adapter-owned `Runner` interface, and maps results
+  and errors to HTTP DTOs.
+- `internal/format` renders `promptkit.PreparedRun` values as deterministic text
+  or JSON.
+- `internal/report` maps Promptkit's terminal execution event to a small
+  application-owned value without invoking the engine or writing output.
+
+## Wiring Flows
+
+### CLI
+
+`run` calls `promptkit.Engine.Run`; `render` calls
+`promptkit.Engine.Prepare`. Both share request mapping for prompt ID/version
+and profile selection, optional file inputs, variables, and presence-aware
+execution overrides. Omitted framework settings remain zero values so Promptkit
+resolves its own defaults and definition-required inputs.
+The application retry setting enters shared engine construction, while a
+run/render flag enters only the mapped request. The server uses the same engine
+setting and retains one backend admission state. Render prepares without
+generation.
+
+`inspect prompt` maps the selected ID and optional version to
+`promptkit.Engine.InspectPrompt`, then formats Scriptorium-owned inspection
+data. It constructs the same configuration-aware engine but does not perform
+preparation or generation.
+
+`inspect profile` maps an explicit profile ID to `Engine.InspectProfile` and
+formats a safe application-owned effective profile view. It intentionally does
+not require prompt, schema, or artifact sources.
+
+The `config` family loads the same application ConfigKit result once and uses
+its validation, effective-output, source, and explanation views directly. It
+does not construct a Promptkit engine. The CLI maps source records into a small
+JSON DTO for `sources`; `show` and `explain` use ConfigKit's own writers.
+
+`serve` constructs Scriptorium's restricted HTTP artifact reader, injects it
+with `promptkit.WithArtifactReader`, passes the engine through the HTTP
+adapter's consumer-owned `Runner` interface, and starts the server.
+
+The command paths assemble the engine from the same resolved prompt, profile,
+and schema directories plus configured custom backends. Each backend is mapped
+to Promptkit's public `Backend` value and registered during engine construction,
+so one constructed server engine retains one immutable backend registry and its
+associated capacity state.
+
+### HTTP
+
+The handler enforces transport limits and strict JSON decoding before mapping
+DTOs into `promptkit.RunRequest`, `promptkit.ArtifactRef`, and
+`promptkit.ExecutionTargetOverride`. On success it reads Promptkit artifact,
+validation, model, usage, and metadata values directly.
+The optional HTTP retry count maps to `RunRequest.TransientRetries` without
+mutating the shared engine. Negative values are rejected before invocation;
+Promptkit controls retries and backend admission for concurrent requests.
+
+Failure mapping uses `errors.Is` against Promptkit's public sentinels and the
+HTTP reader's Scriptorium-owned containment and size errors. Wrapped reader
+errors preserve their identity through Promptkit's artifact-load boundary.
+
+The report collector is per invocation. It ignores nonterminal events and
+copies terminal aggregates once, including usage presence and completeness.
+It retains no history or shared state; adapters decide whether to attach it and
+how to present its snapshot.
+CLI `run` attaches one only when a report path is selected, writes generated
+output first on success, and then writes the terminal snapshot when present.
+Its report path remains untouched for pre-invocation failures or absent
+terminal observations; report and artifact writes are independent.
+HTTP `POST /v1/runs` attaches a separate collector to each invocation only when
+`include_execution_report` is true. Its optional top-level `execution` field
+appears in success or error envelopes only when Promptkit emits a terminal
+event. Pre-invocation adapter errors and absent terminal events leave it out.
+The complete serialized success or report-bearing error response is subject to
+the configured response-size limit; overflow returns the compact 413 error
+without a report. Field meanings are owned by the [API contract](../api.md#execution-report).
+
+## Package-Local Guarantees
+
+- Adapters contain no copied framework types or orchestration.
+- Configuration is resolved before Promptkit engine construction.
+- Explicit numeric overrides preserve presence, including zero.
+- HTTP DTO and error mapping remains stable and transport-owned.
+- Resolved secrets are not serialized or printed.
+- No adapter creates durable run state.
+
+## Verification
+
+Inspect:
+
+- `internal/adapter/cli/run_test.go`
+- `internal/adapter/http/handler_test.go`
+- `internal/adapter/http/artifact_reader_test.go`
+- `internal/format/prepared_run_test.go`
+- `internal/adapter/dependency_test.go`
+
+The adapter tests protect parsing, configuration mapping, output, status
+mapping, restricted artifacts, and representative real Promptkit-engine
+workflows. The dependency test protects the repository boundary.
+
+## Change Recipes
+
+For a CLI or HTTP change:
+
+1. identify the Scriptorium-owned external contract;
+2. map through Promptkit public values without copying framework semantics;
+3. add or update the narrow application-owned test;
+4. update the canonical Scriptorium contract; and
+5. coordinate and tag Promptkit first if a required public capability is
+   genuinely absent.
+
+Update [source internals](sources.md) when application source locations or HTTP
+artifact containment changes.

docs/internal/overview.md

@@ -0,0 +1,19 @@
+# Internal Component Overview
+
+This is the complete inventory of Scriptorium's implemented Go components.
+The [architecture policy](../policy/architecture.md) owns normative boundaries;
+public behavior belongs in the linked contracts.
+
+| Component | Implemented responsibility | References |
+| --- | --- | --- |
+| `cmd/scriptorium` | Process entrypoint that delegates arguments and streams to the CLI adapter. | [CLI contract](../cli.md), [adapter internals](adapters.md) |
+| `internal/adapter/cli` | Parses execution and application-configuration inspection commands, resolves settings, constructs Promptkit engines only for execution/definition inspection, maps requests, and owns process output and exit behavior. | [CLI contract](../cli.md), [adapter internals](adapters.md) |
+| `internal/adapter/http` | Owns routes, DTOs, strict decoding, limits, Promptkit request/result mapping, public error mapping, and restricted HTTP artifact reading. | [HTTP API](../api.md), [adapter internals](adapters.md), [source internals](sources.md) |
+| `internal/config` | Selects application sources, supplies the ConfigKit definition and explicit overrides, and converts resolved settings for runtime use. | [configuration contract](../config.md), [adapter internals](adapters.md) |
+| `internal/defaults` | Holds Scriptorium-owned application and HTTP defaults. | [configuration contract](../config.md) |
+| `internal/format` | Formats Promptkit prepared-run and prompt/profile inspection values for CLI text or JSON output. | [CLI contract](../cli.md), [adapter internals](adapters.md) |
+| `internal/report` | Projects one terminal Promptkit observation into Scriptorium-owned execution metadata. | [adapter internals](adapters.md) |
+
+Framework implementation packages are provided by
+[Promptkit v0.11.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md)
+and are not part of this repository.

docs/internal/sources.md

@@ -0,0 +1,101 @@
+# Source Internals
+
+## Purpose
+
+This document covers Scriptorium-owned source locations and the restricted HTTP
+artifact reader. Prompt, profile, schema, and ordinary artifact semantics are
+owned by the tagged
+[Promptkit format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md).
+
+## Application Source Locations
+
+`internal/config` resolves `prompt_dir`, `profile_dir`, and `schema_dir` from
+Scriptorium defaults, configuration files, and CLI overrides. It also resolves
+the application-owned `backends` mapping into sorted engine settings.
+`internal/adapter/cli` passes the directories into `promptkit.Config` and maps
+each configured backend to Promptkit's public engine registration when
+constructing an engine shared by the command path.
+
+Scriptorium does not search, parse, validate, or overlay framework source files
+itself. Promptkit owns prompt selection, profile built-ins and overlays, schema
+resolution, ordinary file artifacts, and the related error identities.
+
+The [configuration reference](../config.md) owns Scriptorium's source-location
+fields and precedence. Maintained files under `examples/` are application
+inputs that use Promptkit's tagged formats.
+
+## Application Configuration Boundary
+
+`internal/config` contains a ConfigKit-native `Document` definition. Its
+fresh defaults come from Scriptorium's existing default constants; its resolver
+records only actual trimming, path cleaning, and render-format normalization.
+The validator reports application retry, size-limit, and format errors without
+mutating the document or exposing rejected values. Application path values keep
+working-directory-relative meaning. ConfigKit owns strict YAML decoding and
+presence semantics, including dynamic integer values in backend parameters.
+
+The `Load` boundary selects an explicit file, the first existing implicit
+configuration file, or ConfigKit's defaults-only source. Only absence advances
+implicit discovery. One ConfigKit load applies explicit application overrides
+before validation and returns a result containing the resolved document and
+its frozen inspection records. `Settings` converts that document into the
+existing runtime settings with backend IDs sorted; it does not read files or
+apply another merge. File-backed loads enable explicit ConfigKit imports and
+select one named overlay when requested. ConfigKit uses the selected file's
+canonical directory as the source root; the application does not widen it.
+Application path values retain process-working-directory-relative meaning.
+
+Every configuration-loading command uses this boundary. The CLI maps only
+explicitly visited application flags to ConfigKit overrides and prints
+structured load diagnostics before engine construction. The old application
+YAML decoder and merge path have been removed.
+Application `config` inspection reuses the result's frozen effective,
+provenance, and history views without constructing an engine or reloading
+sources. It does not resolve API-key environment values; ordinary backend
+parameters remain visible by the selected inspection policy.
+
+## Restricted HTTP Artifact Reader
+
+`internal/adapter/http` implements `promptkit.ArtifactReader` for HTTP
+requests. The `serve` path injects it with
+`promptkit.WithArtifactReader`, replacing Promptkit's ordinary reader for
+inbound HTTP inputs.
+
+The reader:
+
+- accepts inline references without an artifact root;
+- denies file references when no root is configured;
+- resolves relative paths below the configured root;
+- accepts absolute paths only when they are lexically within that root;
+- rejects lexical traversal outside the root;
+- applies the configured file byte limit, with zero meaning unlimited;
+- preserves content type, body, size, hash, name, and URI metadata; and
+- honors context cancellation.
+
+Containment is lexical and does not resolve symlinks. The operating system
+follows symlinks after the check. The [HTTP API](../api.md) owns observable
+request outcomes, and [operations](../operations.md) owns safe deployment
+permissions and root selection.
+
+Reader errors remain identifiable after Promptkit wraps them as artifact-load
+failures, allowing the HTTP adapter to preserve Scriptorium status and error
+codes.
+
+## Verification And Change Recipe
+
+Inspect:
+
+- `internal/config/document_test.go`
+- `internal/config/load_test.go`
+- `internal/adapter/cli/run_test.go`
+- `internal/adapter/http/artifact_reader_test.go`
+- `internal/adapter/http/handler_test.go`
+
+When changing an application source location or HTTP artifact policy:
+
+1. preserve strict configuration precedence and the Promptkit public boundary;
+2. keep containment and size policy in Scriptorium;
+3. update focused configuration, reader, and handler tests;
+4. update the [configuration](../config.md), [HTTP](../api.md), and
+   [operations](../operations.md) contracts as applicable; and
+5. do not duplicate Promptkit loaders, formats, or ordinary artifact behavior.

docs/operations.md

@@ -0,0 +1,229 @@
+# Operations Guide
+
+## Scope And References
+
+This runbook covers deployment, normal operation, capacity planning, and safe
+recovery for Scriptorium. It does not redefine invocation syntax, configuration
+fields, or HTTP wire behavior.
+
+- [CLI reference](cli.md): commands, output destinations, and exit codes.
+- [Configuration reference](config.md): application settings, source
+  locations, defaults, and credential mapping.
+- [Promptkit framework formats](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md):
+  prompt, profile, schema, execution-setting, and framework credential
+  contracts.
+- [HTTP API reference](api.md): route, request/response schema, status codes,
+  limits, and HTTP artifact access.
+- [Consumer integration overview](consumers/api.md): caller responsibilities.
+
+## Operational Model And State
+
+Scriptorium handles one prompt request for each CLI invocation or HTTP request.
+It has no durable run store, archive, checkpoint, cache, or resume mechanism.
+A failed or interrupted request is recovered by correcting its inputs,
+configuration, or environment and submitting a new request.
+
+Generated artifacts, rendered prompts, model output, and run metadata are
+caller-owned data. Retention, encryption, backup, and deletion are deployment
+responsibilities.
+Optional [CLI execution reports](cli.md) also belong to the caller. They can
+contain sensitive identifiers even though they omit prompt and response bodies.
+Keep report paths separate from generated output and apply the same access and
+retention controls. Output and report writes are not transactional; an older
+report may remain when no terminal observation was produced.
+HTTP callers may also request a [terminal execution report](api.md#execution-report).
+It shares the same identifier sensitivity and should receive response access
+and retention controls. An opted-in report increases the encoded response size;
+an oversized success or report-bearing error becomes the compact 413 response
+without a report.
+
+## Deploy The Filesystem And Process
+
+Provide the process with readable configured Promptkit prompt, profile, and
+schema sources that follow the tagged framework formats. For an HTTP deployment
+that accepts file artifacts, use a dedicated, narrow artifact directory rather
+than a general-purpose or sensitive filesystem tree.
+
+If application configuration uses explicit imports or a selected overlay,
+deploy those files beneath the selected configuration file's canonical
+directory. ConfigKit keeps imported and overlay files within that root;
+Scriptorium does not widen it. Application path values inside those files still
+resolve from the process working directory, so set that directory deliberately
+in the service manager. This configuration-source boundary is distinct from
+the HTTP artifact root and does not constrain prompt or schema directories.
+
+When upgrading existing definitions, review selected profile IDs.
+`deepseek-3-2`, `deepseek-4-flash`, and `deepseek-4-pro` were removed from the
+selected catalog. Choose an available catalog profile, one of Promptkit's
+maintained names, or a complete application-owned profile. New DeepSeek names
+are not aliases for the removed ones; see the
+[v0.10 migration guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.10.0/docs/releases/v0.10.0.md).
+
+Run Scriptorium under an identity that can:
+
+- read only the prompt, profile, schema, and allowed input-artifact paths it
+  needs;
+- read the required credential environment variables without writing them to
+  files or logs; and
+- write only caller-selected output locations when CLI output files are used.
+
+Do not make the HTTP artifact directory writable by untrusted users. The HTTP
+artifact containment behavior is lexical and the operating system follows
+symlinks; account for that when choosing ownership and mount boundaries. See
+the [HTTP API reference](api.md) for the externally observable behavior.
+
+## Supply Credentials And Protect Runtime Data
+
+Set secret values in the process environment and configure only their
+environment-variable names. Do not put raw keys in configuration, prompt or
+profile files, process arguments, HTTP payloads, captured command lines, or
+debug dumps.
+
+Treat stdout, stderr, prepared-run output, generated artifacts, and HTTP
+responses as potentially sensitive. Send service logs to a controlled collector
+and apply the same retention and access rules as for model input and output.
+
+## Run A Normal Workflow
+
+Before changing production inputs, profiles, or schemas:
+
+1. use `config validate`, `config show`, or `config sources` to check the
+   application configuration and its selected sources without constructing an
+   engine; this does not verify prompt files, provider access, or credentials;
+2. confirm the deployed configuration selects the intended sources and model
+   credentials;
+3. use [`render`](cli.md) with the same request inputs and variables to confirm
+   preparation without a model call;
+4. use [`run`](cli.md) for generation; and
+5. retain or discard validation-failed output according to the caller's
+   policy.
+
+Inspection output can include configuration paths, names, and ordinary backend
+parameters. `config explain --path` uses JSON Pointer paths and can show
+displaced historical values as well as the final value. Protect both the
+selected paths and the output, especially when backend parameters contain
+sensitive identifiers; ConfigKit does not infer arbitrary secrets in those
+parameters. Apply
+access and retention controls; the application stores only API-key environment
+reference names, not the resolved credential bytes.
+
+The [maintained render script](../examples/render-markdown-summary.sh) is a
+copyable preflight example. The CLI reference owns its complete invocation and
+exit semantics.
+
+## Expose The HTTP Service
+
+The HTTP service has no built-in authentication or authorization. Place it on a
+trusted network or behind an authenticated reverse proxy, API gateway, or
+equivalent access control. Restrict who can reach it and who can read the
+artifact root.
+
+Use a service manager or supervisor appropriate to the deployment to manage
+process lifetime, restart policy, log capture, and environment injection. The
+[HTTP API reference](api.md) owns client request shapes, status behavior, and
+artifact-access outcomes.
+
+## Plan Capacity And Limits
+
+Capacity is primarily determined by concurrent model calls, input and output
+sizes, schema complexity, provider latency, and network behavior. Size limits
+protect request bodies, HTTP file artifacts, and encoded responses; configure
+them through the [configuration reference](config.md) and rely on the
+[HTTP API reference](api.md) for their response effects.
+
+Configured backend concurrency and queue capacity are enforced per constructed
+Promptkit engine. A `serve` process constructs one engine for its handler, so
+concurrent HTTP requests share that transient admission state. Scriptorium does
+not retain workflow state: capacity is neither durable nor a queue of resumable
+runs. When admission is exhausted, HTTP returns `503 capacity_exceeded` without
+retry timing; callers choose any retry policy that is safe for another model
+call.
+
+Promptkit's built-in client now allows two additional attempts for eligible
+transient provider statuses by default. Account for added calls, latency, and
+cost when planning capacity. Each repair generation has its own transient
+budget, separate from the structural repair count. Configure the engine budget
+with [`transient_retries`](config.md); `run` and `render` accept a request
+override described in the [CLI contract](cli.md), and HTTP callers can select
+one through the [API contract](api.md). Omission inherits the engine
+setting and then Promptkit's default, while explicit zero disables additional
+attempts. Existing generation timeouts apply
+per attempt, while the caller context covers the complete operation. Provider
+`Retry-After` timing can exceed Promptkit's ordinary backoff cap; consult the
+[outbound integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/integrations/openai-compatible-chat.md)
+for details.
+
+CLI `run` can set a [whole-run deadline](cli.md) when total execution time must
+be bounded. The existing generation timeout applies afresh to each attempt and
+does not cap retry waits or the complete invocation. The whole-run interval
+covers the engine call, including capacity waiting and repairs as supported by
+context cancellation; it excludes parsing, engine setup, and output writes.
+HTTP callers can use [`run_timeout_seconds`](api.md) to shorten their request
+context for the same engine interval. The API distinguishes an expired
+execution deadline from caller cancellation and from a provider-attempt
+timeout. A canceled capacity waiter releases its Promptkit admission state.
+
+Before increasing a limit:
+
+1. measure representative input, generated-output, and optional raw-output
+   sizes;
+2. confirm memory, network, and upstream-provider capacity;
+3. retain an upstream request-size and authentication boundary; and
+4. test the intended workload in a non-production environment.
+
+For large local inputs, prefer a controlled file-artifact directory over
+placing arbitrary paths on the service host. Avoid disabling a limit unless an
+equivalent trusted control exists elsewhere.
+
+## Diagnose And Recover
+
+### Preparation Or Configuration Failure
+
+Capture the CLI diagnostic or HTTP error response, then verify the selected
+configuration, prompt ID, profile selection, source readability, and input
+mapping. Use `render` with the same request when it is unclear whether failure
+occurs before model execution. Consult the [CLI reference](cli.md), the
+[configuration reference](config.md), and the [HTTP API reference](api.md) for
+the exact interface contract.
+
+### Credential Or Provider Failure
+
+Confirm that the process environment contains the configured credential name
+without printing the secret. Check endpoint reachability and provider health
+from the process network. If preparation succeeds but generation fails, inspect
+the selected model settings in prepared output and the service's controlled
+logs. Correct the deployment or provider issue, then submit a new request.
+
+### Artifact Or Permission Failure
+
+Verify that the process can read the intended local input. For HTTP file
+artifacts, verify the deployment's artifact root, ownership, path layout, and
+file size. Do not widen filesystem permissions or the allowed root merely to
+make an arbitrary path work; move or copy the required artifact into the
+controlled location instead.
+
+### Validation Failure
+
+A generated-content validation failure is distinct from a runtime failure.
+CLI `run` reports the validation result and error count in its success summary;
+it does not print the individual validation messages. For HTTP, inspect the
+validation object in the response according to the [HTTP API reference](api.md).
+
+Use rendered input and generated output to determine whether prompt instructions,
+the selected model, or the schema needs correction. If schema loading or
+compilation itself fails, correct the source deployment or schema document
+before rerunning.
+
+### HTTP Limit Or Request Failure
+
+Compare the request, artifact, or expected response size with the deployed
+configuration, and validate the request against the [HTTP API reference](api.md).
+Reduce the payload, use an appropriate controlled artifact source, omit
+unneeded raw output, or adjust the deployment limit after capacity review.
+
+## Cleanup And Reruns
+
+Because no run state is retained, cleanup concerns caller-owned output files,
+logs, and artifacts only. Remove or rotate them using the deployment's normal
+retention policy. After a correction, rerun the request from the beginning;
+there is no safe resume point.

docs/oss/attribution.md

@@ -0,0 +1,127 @@
+# Open-Source Attribution
+
+Scriptorium's own terms are in the repository [LICENSE](../../LICENSE).
+The [OSS policy](../policy/oss.md) governs these entries. Dependency versions
+are recorded in [go.mod](../../go.mod) and [go.sum](../../go.sum); source and
+notice links below identify the exact commits for the selected versions.
+
+## Promptkit
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3 companion](licenses/GPL-3.0.txt) |
+[upstream LICENSE](https://gitea.maximumdirect.net/eric/promptkit/src/commit/db05b56166ca2d8650dfaf660e1cf0eed3932e1d/LICENSE)
+
+Source: [Promptkit v0.11.0](https://gitea.maximumdirect.net/eric/promptkit/src/commit/db05b56166ca2d8650dfaf660e1cf0eed3932e1d)
+
+## ConfigKit
+
+Upstream copyright statement: no project-specific statement is present in the
+selected module; the FSF copyright in its license text belongs to that license
+document and is not substituted for a project notice.
+
+SPDX-License-Identifier: LGPL-3.0-only
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3 companion](licenses/GPL-3.0.txt) |
+[upstream LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/e6ced0d3d1194b58e0b3dc8970089471ba175258/LICENSE)
+
+Source: [ConfigKit v0.4.0](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/e6ced0d3d1194b58e0b3dc8970089471ba175258)
+
+## Promptkit OpenRouter Catalog
+
+Upstream copyright statement: no project-specific statement is present in the
+selected module. The linked upstream README records the profile assets'
+Promptkit origin and the copyright holder's deliberate relicensing.
+
+SPDX-License-Identifier: LGPL-3.0-only
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3 companion](licenses/GPL-3.0.txt) |
+[upstream LICENSE](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/f7518043ebdd70b8959506201639903dff0b85ab/LICENSE) |
+[asset licensing notice](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/f7518043ebdd70b8959506201639903dff0b85ab/README.md)
+
+Source: [OpenRouter catalog v2.20260922.1](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/f7518043ebdd70b8959506201639903dff0b85ab)
+
+## Promptkit Rakestrawhome Catalog
+
+Upstream copyright statement: no project-specific statement is present in the
+selected module. The linked upstream README records the profile asset's
+Promptkit origin and the copyright holder's deliberate relicensing.
+
+SPDX-License-Identifier: LGPL-3.0-only
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3 companion](licenses/GPL-3.0.txt) |
+[upstream LICENSE](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/d664696142bf7c2d93db2a6b2e07f3deb55f2226/LICENSE) |
+[asset licensing notice](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/d664696142bf7c2d93db2a6b2e07f3deb55f2226/README.md)
+
+Source: [Rakestrawhome catalog v2.20260922.0](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/d664696142bf7c2d93db2a6b2e07f3deb55f2226)
+
+## jsonschema/v6
+
+Upstream copyright statement: no project-specific statement is present in the
+selected module; no substitute statement is inferred here.
+
+SPDX-License-Identifier: Apache-2.0
+
+License and notices: [Apache 2.0](licenses/Apache-2.0.txt) |
+[upstream LICENSE](https://github.com/santhosh-tekuri/jsonschema/blob/29cbed948d24a04700eb94436416b18a07953b71/LICENSE)
+
+Source: [jsonschema/v6 v6.0.2](https://github.com/santhosh-tekuri/jsonschema/tree/29cbed948d24a04700eb94436416b18a07953b71)
+
+## golang.org/x/text
+
+Copyright (c) 2009 The Go Authors. All rights reserved.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause.txt) |
+[upstream LICENSE](https://go.googlesource.com/text/+/6c97a165dd661335ff7bce6104a008558123c353/LICENSE)
+
+Source: [golang.org/x/text v0.14.0](https://go.googlesource.com/text/+/6c97a165dd661335ff7bce6104a008558123c353)
+
+## gopkg.in/yaml.v3
+
+Copyright (c) 2006-2010 Kirill Simonov
+
+Copyright (c) 2006-2011 Kirill Simonov
+
+Copyright (c) 2011-2019 Canonical Ltd
+
+Copyright 2011-2016 Canonical Ltd.
+
+SPDX-License-Identifier: MIT AND Apache-2.0
+
+The upstream LICENSE assigns MIT to files ported from libyaml and Apache 2.0
+to the remaining files; these are file-specific terms, not alternatives.
+
+License and notices: [MIT](licenses/MIT.txt) |
+[Apache 2.0](licenses/Apache-2.0.txt) |
+[upstream LICENSE](https://github.com/go-yaml/yaml/blob/f6f7691b1fdeb513f56608cd2c32c51f8194bf51/LICENSE) |
+[upstream NOTICE](https://github.com/go-yaml/yaml/blob/f6f7691b1fdeb513f56608cd2c32c51f8194bf51/NOTICE)
+
+Source: [gopkg.in/yaml.v3 v3.0.1](https://github.com/go-yaml/yaml/tree/f6f7691b1fdeb513f56608cd2c32c51f8194bf51)
+
+## go.yaml.in/yaml/v4
+
+Copyright 2006-2010 Kirill Simonov
+
+Copyright 2011-2019 Canonical Ltd
+
+Copyright 2025 The go-yaml Project Contributors
+
+SPDX-License-Identifier: MIT AND Apache-2.0
+
+The upstream NOTICE assigns MIT to files ported from libyaml and Apache 2.0
+to the remaining files; these are file-specific terms, not alternatives.
+
+License and notices: [MIT](licenses/MIT.txt) |
+[Apache 2.0](licenses/Apache-2.0.txt) |
+[upstream LICENSE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/LICENSE) |
+[upstream NOTICE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/NOTICE)
+
+Source: [go.yaml.in/yaml/v4 v4.0.0-rc.6](https://github.com/yaml/go-yaml/tree/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125)

docs/oss/licenses/Apache-2.0.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

docs/oss/licenses/BSD-3-Clause.txt

@@ -0,0 +1,11 @@
+Copyright (c) <year> <owner>. 
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

docs/oss/licenses/GPL-3.0.txt

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

docs/oss/licenses/LGPL-3.0.txt

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

docs/oss/licenses/MIT.txt

@@ -0,0 +1,18 @@
+MIT License
+
+Copyright (c) <year> <copyright holders>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
+associated documentation files (the "Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the
+following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial
+portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
+LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO
+EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
+USE OR OTHER DEALINGS IN THE SOFTWARE.

docs/policy/agents.md

@@ -0,0 +1,77 @@
+# Agent Policy
+
+**Base Policy Version:** 1.1
+
+**Last Updated:** 2026-09-26
+
+## Purpose
+
+Agents working in this repository must read and adhere to the following house rules.
+
+## Implementation Discipline
+
+**KEY PRINCIPLES:** Write the simplest idiomatic code that satisfies the user's
+request. Do not implicitly strengthen requirements, restrictions, or guarantees
+beyond what the user actually requested.
+
+**Keep implementation machinery proportionate.** Use straightforward,
+idiomatic code and introduce only the machinery needed to support the requested
+behavior and flexibility. Optimize for conceptual simplicity and
+maintainability, not for the fewest lines, fewest options, or narrowest product
+surface.
+
+**Do not invent restrictions.** Do not reject, prohibit, constrain, cap,
+harden, or otherwise narrow behavior unless required by the user, an explicit
+repository contract, or an unavoidable correctness constraint. Preserve
+operator and caller choice where policy has not been established. If an
+additional restriction appears advisable, present it as a decision rather than
+silently implementing it.
+
+**Do not invent guarantees.** Do not strengthen public contracts, guarantees,
+or invariants beyond those expressly requested by the user.
+
+**Use the standard library.** For example: in almost every case, the best
+approach to copying files is to use the standard library. Writing custom code to
+implement power-loss protection at the application level, or to guard against
+bad actors with privileged and concurrent access to the host's filesystem,
+is wasteful, unnecessary, and not idiomatic. Stick to the simple, standard, and
+idiomatic approach unless another path is expressly requested by the user.
+
+**An implementation detail is not repository policy.** Tests and documentation
+must not elevate incidental behavior into a durable guarantee or restriction
+unless that behavior was expressly selected as part of the contract.
+
+## Git Commit Policy
+
+By default, create a commit after completing each coherent unit of work, using a
+concise, plain-English message describing what changed. This policy is standing
+authorization to create those local commits; a separate user request is not
+required. An explicit user instruction to leave work uncommitted takes precedence.
+
+A unit of work is a focused, reviewable outcome, including its relevant tests and
+documentation. Do not commit after every intermediate edit or create empty commits.
+Complete the appropriate validation before committing. If work is incomplete or
+validation is blocked, report that state rather than presenting it as completed.
+
+Before committing:
+
+1. Run `git status --short` and review the relevant diff, including any staged
+   changes. Identify changes that predate the current unit of work.
+2. Exclude secrets, local environment files, generated junk, and unrelated changes.
+3. Stage only the files or hunks belonging to the completed unit. Use `git add .`
+   only when every included change belongs to that unit. Do not disturb unrelated
+   staged or unstaged work.
+4. Review `git diff --staged` and run appropriate checks for the change. Do not
+   repeat checks already passed for unchanged content merely to create a commit.
+5. Review `git log --oneline -n 10` and use
+   `git commit -m "<concise plain-English commit message>"`.
+6. Report the commit identifier and any remaining uncommitted work.
+
+If the unit cannot be safely separated from pre-existing work, leave it uncommitted
+and explain the overlap rather than silently including that work. If a commit
+fails, preserve the changes and report the failure; do not bypass hooks.
+
+Default commit authorization does not authorize pushing, publishing, amending,
+resetting, reverting, or rewriting history. Those actions require a separate user
+instruction. Do not use `git commit -a` or `git commit --no-verify` to bypass the
+staging and validation discipline above.

docs/policy/architecture.md

@@ -0,0 +1,157 @@
+# Architecture Policy
+
+**Base Policy Version:** 1.1
+
+**Last Updated:** 2026-09-26
+
+## Purpose And Ownership
+
+This policy defines Scriptorium's purpose, responsibility and dependency
+boundaries, established invariants, and non-goals. Concrete component inventory
+and implementation mechanics belong in [internal documentation](../internal/overview.md);
+public behavior belongs in its canonical contracts.
+
+Adopted constraints govern future development without implying that every
+capability they could govern exists or is planned. Keep proposed structure and
+implementation status in roadmaps, and decision rationale in ADRs. Acceptance
+of a decision is not proof of implementation. Do not turn incidental choices
+into architectural invariants.
+
+## System Shape
+
+Scriptorium is an executable application with four command entry paths: CLI
+`run`, CLI `render`, CLI `inspect`, and the HTTP service started by `serve`.
+The `inspect` command has prompt and profile modes. Scriptorium does not expose
+a reusable root Go package.
+
+The application consumes
+[Promptkit v0.11.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md)
+through its supported root package. Promptkit owns prompt execution,
+preparation, source formats, built-in profiles, model-client behavior, and
+validation. Scriptorium owns application configuration, executable adapters,
+prepared-run and definition-inspection presentation, process behavior, and HTTP
+deployment policy.
+
+Scriptorium also consumes ConfigKit v0.4.0 for application configuration
+decoding, resolution, and validation flow. Scriptorium owns its application
+schema, defaults, normalization, validation rules, source selection, and CLI
+flag mapping; ConfigKit does not own Promptkit framework sources or HTTP
+artifact containment.
+
+The concrete package inventory is maintained in the
+[internal overview](../internal/overview.md).
+
+As established by [ADR 0004](../adr/0004-definition-boundary.md), Scriptorium
+aims to support the complete set of features in valid Promptkit prompt and
+profile definitions for its selected upstream version. Promptkit remains the
+canonical parser and validator. Library-only features are considered
+individually against the simple predefined-prompt execution model.
+
+Maintain adapter boundaries with proportionate, idiomatic code. This approach
+does not require an interface for every type, additional wrappers, or a fixed
+directory tree for integrations that do not exist.
+
+## Dependency Direction
+
+```text
+cmd/scriptorium
+        |
+        v
+CLI and HTTP adapters, configuration, defaults, and formatting
+        |
+        v
+Promptkit (execution) and ConfigKit (application configuration)
+```
+
+- Retained application packages may import Promptkit's root package.
+- They must not import Promptkit `internal` packages.
+- They must not import Promptkit catalog modules directly.
+- They must not import the removed Scriptorium root facade or recreate former
+  framework package families.
+- Adapter-owned interfaces use Promptkit public values when a consumer-side
+  substitution boundary is needed.
+- Scriptorium passes omitted framework settings as zero values so Promptkit
+  applies its own defaults.
+
+The repository architecture guard enforces these import and removal
+invariants.
+
+Cross-project changes land and release in Promptkit before Scriptorium adopts
+the tagged dependency. Do not commit Go workspaces, local replacements,
+vendored Promptkit implementation, or unpublished dependency assumptions.
+
+## Retained Boundaries
+
+- `internal/adapter/cli` owns commands, flags, configuration precedence,
+  process streams, output files, summaries, and exit codes.
+- `internal/adapter/http` owns routes, strict JSON DTOs, size limits, response
+  mapping, status mapping, and the restricted artifact reader.
+- `internal/config` owns discovery and Scriptorium's application definition;
+  ConfigKit owns strict YAML decoding and the load/override pipeline.
+- `internal/defaults` owns Scriptorium application and HTTP defaults only.
+- `internal/format` owns deterministic prepared-run and definition-inspection
+  text and JSON presentation.
+- Promptkit owns framework orchestration and contracts. Its
+  [format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md)
+  and
+  [outbound integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/integrations/openai-compatible-chat.md)
+  are canonical.
+
+## HTTP Artifact Security Boundary
+
+Ordinary CLI file loading is provided by Promptkit. Scriptorium's HTTP adapter
+injects a restricted `promptkit.ArtifactReader` for inbound HTTP requests.
+That reader denies file references without an artifact root, enforces the
+configured byte limit, and applies Scriptorium's lexical root-containment rule.
+The operating system still follows symlinks after the lexical check.
+
+This boundary handles untrusted request references under the documented
+deployment model; it is not a filesystem sandbox. Defending against a
+privileged actor concurrently modifying the host filesystem is outside the
+adopted scope, not a claim that such activity cannot occur. Do not infer
+additional defenses or guarantees from hypothetical threats; raise unsettled
+scope decisions under the [agent policy](agents.md).
+
+The [HTTP API](../api.md) owns observable request outcomes, and
+[operations](../operations.md) owns deployment permissions and root selection.
+
+## State, Errors, And Secrets
+
+Scriptorium has no durable run-state store, checkpoint, cache, or resume
+mechanism. Recovery is a new request after correcting inputs, configuration, or
+environment.
+
+Each request is self-contained from the caller's perspective, without
+conversation or workflow state retained from completed requests. This does
+not mean the process is internally stateless. Shared engines, backend capacity
+and queue accounting, in-flight coordination, cancellation, and server
+lifecycle resources are permitted and must be shared where necessary to
+enforce configured backend limits across concurrent requests. Such state must
+be concurrency-safe and does not create a durable user-workflow contract.
+
+Adapters map Promptkit public error identities into CLI exits or HTTP statuses
+without classifying by message text. Raw API keys are not accepted in
+Scriptorium configuration, CLI arguments, or HTTP payloads, and resolved
+secrets must not be emitted.
+
+## Architectural Invariants
+
+- External YAML and JSON decoding remains strict.
+- CLI and HTTP behavior remains presentation and transport logic rather than
+  framework orchestration.
+- Explicit numeric request overrides preserve presence, including zero.
+- HTTP artifact containment and byte limits remain Scriptorium policy.
+- No application package depends on Promptkit implementation packages.
+
+## Non-Goals
+
+- Do not recreate an in-process Scriptorium framework API or compatibility
+  facade.
+- Do not copy Promptkit types, defaults, built-in profiles, or implementation
+  into Scriptorium.
+- Do not move CLI, inbound HTTP, process, or deployment policy into Promptkit.
+- Do not add durable workflow, archive, or resume behavior.
+- Do not add application-managed prompt modification, follow-up message flows,
+  conversation management, or multi-step workflow orchestration.
+
+Work that is not implemented belongs in `docs/roadmap/`.

docs/policy/documentation.md

@@ -0,0 +1,200 @@
+# Documentation Policy
+
+**Base Policy Version:** 1.4
+
+**Last Updated:** 2026-09-26
+
+## Purpose
+
+This policy assigns each documentation topic to one canonical owner. Its goal is
+to keep this repository's documentation accurate, concise, discoverable, and
+resistant to drift for users, operators, developers, integrators, and LLM
+coding agents.
+
+## Core Rules
+
+### One Canonical Owner
+
+Each authoritative fact belongs in one document. A non-owning document may give
+a short, stable summary for orientation, but it must link to the canonical owner
+instead of repeating volatile details.
+
+Volatile details include commands, flags, configuration fields and defaults,
+module keys, schemas, file names, paths, status codes, retry behavior, and
+runtime guarantees. If readers could reasonably treat a statement as a
+contract, maintain it only in the owning document.
+
+Minimal tested usage examples are allowed outside the owning contract when this
+policy assigns them an orientation or instructional purpose. They must link to
+the canonical contract and must not redefine complete syntax, defaults, or
+semantics.
+
+### Current And Future Behavior
+
+Outside `docs/roadmap/`, documentation describes implemented behavior only.
+Partial features may be described only to their implemented boundary.
+
+Architectural constraints may govern future changes without implying that the
+components or capabilities they would govern already exist. This does not
+permit describing a proposed system structure as implemented.
+
+ADRs may record an accepted architectural decision before implementation, but
+acceptance must not be presented as proof that the behavior exists. The roadmap
+owns implementation status and sequencing until the decision is implemented.
+Current architecture, user, operator,
+integration, and internal documentation are updated when the behavior lands.
+
+### Audience And Detail
+
+Write for the document's stated audience and include only the detail needed for
+its owned topic. User and operator docs should not expose implementation detail.
+Developer docs should link to user-facing and external contracts rather than
+restate them.
+
+### Examples
+
+Complete copyable files belong in `examples/`. Documentation may use the
+smallest illustrative snippet needed to explain its owned topic, but should link
+to maintained examples instead of embedding a second complete copy.
+
+Examples must be valid, secret-free, and tested where practical. Commands and
+configuration used in documentation should match the application.
+
+### Security And Privacy
+
+Documentation and examples must not contain real credentials, private keys,
+private environment dumps, sensitive source material, or private infrastructure
+details unless intentionally public. Document secret-handling mechanisms, not
+secret values.
+
+## Canonical Ownership
+
+| Topic | Canonical owner | Owned content | Content owned elsewhere |
+| --- | --- | --- | --- |
+| Product orientation and minimal end-to-end quickstart | `README.md` | What this project is, why it is useful, one shortest successful invocation, and links onward, including license and attribution navigation. | Complete command reference, configuration reference, operational procedures, implementation detail. |
+| Contributor entry point | `docs/development.md` | Task-oriented reading guide, minimal contributor orientation, baseline validation commands, and links to canonical docs. | Package inventory, architecture rules, subsystem behavior, and detailed change recipes, which belong in the relevant internal component document. |
+| Application architecture policy | `docs/policy/architecture.md` | System shape, normative ownership, dependency direction, architectural boundaries, invariants, safety properties, and non-goals. | Concrete package inventory, implementation mechanics, contributor procedures, decision history, future work. |
+| Agent policy | `docs/policy/agents.md` | Agent implementation discipline, proportionality, idiomatic simplicity, local commit rules, and rules against inventing requirements, restrictions, guarantees, or repository policy. | Application contracts, architecture, testing policy, and contributor procedures. |
+| Documentation organization | `docs/policy/documentation.md` | Documentation ownership, audience boundaries, maintenance rules, and ADR/document lifecycle. | Application architecture or product behavior. |
+| Testing policy | `docs/policy/testing.md` | Test philosophy, risk-based sufficiency, test boundaries, doubles, coverage guidance, regression-test policy, and criteria for adding, rewriting, or deleting tests. | Subsystem behavior, application contracts, subsystem-specific test inventories, and implementation plans. |
+| CLI contract | `docs/cli.md` | Commands, arguments, flags, invocation semantics, and exit codes. | End-to-end operating procedures, configuration field definitions, runtime filesystem layout, module implementation details. |
+| Configuration contract | `docs/config.md` | Application discovery and precedence, source locations, server fields, render default, HTTP limits, and credential mapping. | Promptkit framework formats and defaults, complete example files, CLI syntax, runtime lifecycle, and implementation detail. |
+| Operations | `docs/operations.md` | Runtime workflows, physical filesystem and state layout, output, cache, and debug handling, resume, cleanup, permissions, recovery, and operational limits. | CLI flag syntax, configuration field definitions, logical output schemas, implementation mechanics. |
+| Release policy | `docs/policy/release.md` | Versioning and compatibility, release integrity and immutability, documentation requirements, proportionate gates, publication controls, source completion, and optional verification boundaries. | Repository-specific commands, installation guidance, historical summaries, and CI implementation details. |
+| Release procedure | `docs/release.md` | Maintainer prerequisites, candidate preparation, publication command and guards, asynchronous delivery, optional diagnostics, and failure recovery. | General release requirements, runtime operations, historical announcements, and current application contracts. |
+| Version-specific release notes | `docs/releases/` | Immutable release summaries, compatibility notices, and migration announcements for one published version. | Complete CLI, HTTP, configuration, operations, or dependency contracts. |
+| Open source licensing and attribution policy | `docs/policy/oss.md` | House attribution format, license-text and notice-link conventions, discoverability, maintenance, and handling of concrete exceptions. | Component entries, license texts, release commands, and dependency security review. |
+| Project license | `LICENSE` | The project's own license terms. | Upstream component attribution and dependency license texts. |
+| Upstream component attribution | `docs/oss/attribution.md` | Component names, copyright statements, license identification, and license, notice, and source links. | General attribution policy and complete standard license texts. |
+| Standard dependency license texts | `docs/oss/licenses/` | Complete, verbatim standard license texts shared by attribution entries where applicable. | Project-specific upstream notices, attribution prose, and policy interpretation. |
+| Public HTTP contract | `docs/api.md` | Routes, authentication, media types, request and response schemas, status codes, pagination, caching, idempotency, rate limits, and HTTP retry semantics. | Client walkthroughs, upstream or downstream integration internals, implementation detail. |
+| Consumer guidance | `docs/consumers/` | Choosing between Scriptorium's executable interfaces and understanding consumer responsibilities. | HTTP wire semantics, CLI syntax, Promptkit's Go package, and internal implementation detail. |
+| External and durable integration contracts | `docs/integrations/` | Scriptorium-owned process and executable integration contracts. | Promptkit framework formats and outbound provider protocols, physical runtime placement, internal transformations, CLI syntax, and configuration defaults. |
+| Implemented component inventory | `docs/internal/overview.md` | Current packages and components, their implemented responsibilities, and links to focused internal docs. | Normative architecture, contributor reading policy, external contracts. |
+| Internal component behavior | Other files under `docs/internal/` | Implementation flow, internal collaborators and state transitions, package-local guarantees and failures, and relevant tests. | Global architecture invariants, configuration definitions and defaults, external schemas, operator procedures. |
+| Architectural decision history | `docs/adr/` | Significant decisions, context, alternatives, rationale, consequences, and supersession history. | Current behavior reference, implementation status, task sequencing. |
+| Future work and implementation status | `docs/roadmap/` | Proposed, accepted, deferred, or rejected work; implementation status; sequencing; and task breakdowns. | Implemented behavior reference and architectural decision rationale. |
+| Complete copyable artifacts | `examples/` | Maintained configuration, inputs, and other files intended to be copied or run. | Field-by-field reference, command reference, prose explanation. |
+
+Documents that do not exist are required only when the corresponding interface
+or responsibility exists. Do not create placeholder API, consumer, integration,
+or operations documents for behavior the application does not have.
+
+## Boundary Rules
+
+### Orientation
+
+The README owns product orientation. The developer guide routes contributors.
+Architecture owns normative structure. Internal overview owns the current
+concrete component map. These documents may link to one another but should not
+maintain parallel package or behavior descriptions.
+
+### Commands, Configuration, And Operations
+
+CLI documentation answers how to invoke the application. Configuration
+documentation answers what settings mean. Operations answers what happens to
+runtime state and how to operate or recover the application. When a workflow
+crosses these topics, choose the document that owns the task and link to the
+other contracts.
+
+### Releases
+
+The release policy owns release requirements; the release procedure supplies
+the commands that satisfy them. Release notes are historical summaries, not
+current-state contract owners. The checked-in note at an immutable tag records
+that release; current documentation changes with the behavior it describes.
+Neither a procedure nor a note may weaken policy or defer required updates to
+canonical contracts.
+
+### Open Source Attribution
+
+The [OSS policy](oss.md) defines the House Format and README and release-link
+conventions. Attribution entries own component-specific information. README
+and release documents provide navigation to those canonical materials; the
+release procedure owns URL construction and publication mechanics.
+
+### Contracts And Implementation
+
+Integration and API documents define externally observable shapes and
+semantics. Internal documents explain how this project implements or consumes
+those contracts. Internal docs may name a field, file, or protocol to identify
+a dependency, but must link to its canonical contract for the definition.
+
+### Security Topics
+
+This policy owns what documentation and examples may contain. Architecture owns
+application security invariants. Configuration owns credential-supply
+mechanisms. Operations owns permissions and handling of sensitive runtime
+artifacts. Internal docs own implementation mechanisms only.
+
+## Architecture Decision Records
+
+Use sequentially numbered ADR filenames such as
+`0001-record-architecture-decisions.md`. Follow the lightweight Nygard format:
+
+1. title;
+2. status;
+3. date;
+4. context;
+5. decision;
+6. alternatives considered;
+7. consequences.
+
+Use one of these statuses:
+
+- **Proposed:** the decision is under consideration and may change;
+- **Accepted:** the decision is approved, whether or not implementation is
+  complete;
+- **Rejected:** the proposed decision was considered and not adopted;
+- **Superseded:** a later ADR replaces the accepted decision.
+
+A proposed ADR transitions to accepted or rejected. An accepted ADR transitions
+to superseded only when a later accepted ADR replaces it. An ADR may be created
+as accepted when the decision has already been made.
+
+Treat the decision content of an accepted ADR as immutable. Its status and
+supersession metadata may be updated, but a changed decision requires a new ADR.
+A superseded ADR must link to its replacement, and the replacement must link
+back to the superseded ADR. Rejected architectural alternatives belong in the
+ADR; rejected product ideas belong in the roadmap.
+
+## Maintenance
+
+Every policy document records its underlying template version and local
+last-updated date immediately below the title. Update the date when revising
+local policy; change the base version only when adopting a newer template.
+Do not retain template adoption instructions in the local policy.
+
+When behavior changes, update its canonical owner in the same change. If
+ownership moves, remove the old definition and replace it with a link where
+navigation remains useful.
+
+Before completing documentation work:
+
+- verify affected behavior and examples;
+- check commands, flags, fields, defaults, schemas, and paths against their
+  implementation;
+- keep unimplemented behavior in the roadmap, subject to the ADR exception;
+- remove stale references and validate links;
+- confirm that non-owning documents summarize and link rather than redefine;
+- confirm that no secrets or sensitive private data were added.

docs/policy/oss.md

@@ -0,0 +1,139 @@
+# Open Source Licensing And Attribution Policy
+
+**Base Policy Version:** 1.1
+
+**Last Updated:** 2026-09-26
+
+## Purpose And Scope
+
+This policy establishes a repeatable House Format for open source attribution
+and license notices. It covers upstream components incorporated into or
+distributed with the project, including relevant transitive dependencies and
+copied code or assets. Treatment follows the component's terms and actual use,
+rather than its classification as a direct dependency.
+
+The baseline is a publicly available source repository with releases published
+alongside it. The format is independent of language, forge, and build system.
+It does not require attribution for every development tool, establish license
+compatibility, or resolve obligations beyond attribution and notice handling.
+
+## Canonical Locations
+
+The [documentation policy](documentation.md) assigns ownership:
+
+- `LICENSE` contains the project's own license. Dependency attribution does
+  not relicense the project.
+- `docs/oss/attribution.md` contains the canonical component entries.
+- `docs/oss/licenses/` contains complete, verbatim standard license texts,
+  including companion texts where applicable.
+
+Use recognizable license filenames, such as `Apache-2.0.txt` or `LGPL-3.0.txt`.
+A shared standard text may serve multiple entries. Keep explanations outside
+license texts and preserve distinct versions and exceptions.
+
+## House Format
+
+Each component entry has five fields:
+
+1. **Project name**, normally as the entry heading.
+2. **Upstream copyright statement or statements**, preserving their wording.
+3. **SPDX license identifier or expression**, when applicable.
+4. **License and notice links**, covering the applicable standard texts and
+   upstream project-specific material.
+5. **Source repository link**, identifying the source corresponding to the
+   imported version.
+
+Illustrative Markdown, with placeholders for the actual upstream information:
+
+```markdown
+## Example Library
+
+Copyright <upstream copyright statement>
+
+SPDX-License-Identifier: Apache-2.0
+
+License and notices: [Apache 2.0](licenses/Apache-2.0.txt) | [NOTICE](<upstream NOTICE URL at the imported commit>)
+
+Source: [Example Library](<upstream repository URL at the imported commit>)
+```
+
+These are five fields, not a line limit. Include multiple statements and links
+where needed. Omit the SPDX field when no applicable identifier exists; identify
+nonstandard terms accurately through the linked text. Preserve licensing
+alternatives and exceptions, and record a selected option when relevant. Do not
+invent an identifier or silently resolve an unsettled licensing choice.
+
+## License Texts And Upstream Links
+
+Link standard license texts to their local copies. Link project-specific
+notices to the upstream copies instead of storing them locally. Every upstream
+repository or notice link must identify the exact commit corresponding to the
+imported version, including the selected source revision for copied material.
+Do not use moving branches or version tags as substitutes for that commit.
+
+Classify material by its contents, not its filename. An upstream `LICENSE`,
+`COPYING`, or similar file may contain project-specific notices or exceptions
+in addition to standard wording. Link both the local standard text and the
+commit-specific upstream file when needed. Make companion license texts directly
+reachable from the entry rather than leaving readers to infer their location.
+
+For project-specific license and attribution material, this policy accepts
+direct links to the applicable upstream texts as satisfying reproduction,
+inclusion, or copy requirements. This is the adopted house interpretation.
+Agents must apply it without adding local-copy requirements or seeking repeated
+approval solely because a license uses those terms.
+
+This interpretation concerns notice reproduction. Concrete obligations such as
+marking modified files or supplying corresponding source receive their own
+applicable treatment. Preserve required notices already present in incorporated
+source files; the central attribution entry does not authorize stripping them.
+
+## Discoverability
+
+End the project's README with two friendly statements linking to its actual
+license and the attribution document. For Scriptorium:
+
+```markdown
+Scriptorium is licensed under the [BSD 3-Clause License](LICENSE).
+
+[Open Source attribution notices](docs/oss/attribution.md) are available.
+```
+
+Each new checked-in release document and its hosted download page must end
+with links whose visible text is `LICENSE | ATTRIBUTION`. Use absolute URLs to
+those files at the release's immutable tag or corresponding immutable source
+revision so the links work in both locations. This release navigation is distinct
+from upstream component links, which must use the imported commit.
+
+Reuse the checked-in release document as the hosted release body where supported.
+The release procedure owns concrete URLs and publication mechanics for delivering
+the links through the selected channel. Do not maintain duplicate notice lists.
+These conventions do not by themselves require separate downloadable license
+assets, source bundles, or a different binary package format.
+
+## Maintenance And Exceptions
+
+Update notices in the change that adds, removes, upgrades, copies, or changes
+the distribution of a relevant component. Check the selected source's license
+and notices rather than assuming they are unchanged. Update affected entries,
+commit links, and texts; retain historical versions through Git.
+
+Check affected statements, faithful standard-text copies, and link destinations
+as part of ordinary change review. For a future release tag, check intended file
+paths against the candidate source; the tag need not resolve remotely before
+publication. Do not add publication-time network checks, CI polling, recurring
+legal sign-offs, mandatory scanners, or a full software bill of materials merely
+to implement this policy.
+
+Use the House Format routinely. Raise an exception only for a concrete obligation
+or unresolved rights question it does not address, including any arising from a
+particular distribution channel. Record the issue and selected treatment in the
+adopted policy or affected attribution entry as appropriate. Resolve the issue
+before the affected use or distribution without reopening settled choices.
+Common ownership of projects is neither required nor a blanket exception.
+
+Apply the formatting convention prospectively. Do not rewrite published tags,
+notes, binaries, or checksums to retrofit it. Address actual omissions deliberately
+under the applicable terms and the [release correction policy](release.md#immutability-and-failure-recovery).
+Ordinary attribution maintenance and release links are preparation work, not new
+release approval gates.

docs/policy/release.md

@@ -0,0 +1,213 @@
+# Release Policy
+
+**Base Policy Version:** 1.2
+
+**Last Updated:** 2026-09-26
+
+## Purpose
+
+This policy defines a proportionate workflow for validating and publishing an
+intended source revision under a fresh version. Releases should require little
+routine intervention, avoid repeated work, and preserve published contents.
+
+The repository-specific commands belong in `docs/release.md`. Historical release
+summaries belong in `docs/releases/`. The procedure must agree with the adopted
+policy and link to it rather than introduce additional release requirements.
+
+## Release Model And Completion
+
+A source release identifies one exact committed source revision through an
+immutable version tag and a version-matched, checked-in release note. The
+primary release branch is `main`; the authoritative publication remote is
+`origin`.
+
+A successful push of the intended tag, with its source commit available on the
+authoritative primary branch, completes the release. Publish `main` before
+invoking the publication command; the command requires
+that the remote branch exactly identifies the validated candidate and pushes
+only the selected annotated tag.
+
+Release commands must finish at successful publication. They must not wait for
+or poll CI, require successful CI status, inspect downloadable artifacts, or
+check consumer installation or Go module availability as completion gates.
+A failed or ambiguous push requires resolving the authoritative remote state
+before declaring success or retrying; successful pushes do not require a
+separate remote read-back gate.
+
+Scriptorium publishes Linux binaries and checksums asynchronously from the
+tagged source. The procedure must identify those deliverables and the
+responsibility of their automation. Published deliverables must be traceable
+to that source and identify the same version.
+
+Artifact delivery is a separate status. A successful tag push is not evidence
+that artifacts are available. Delivery failures do not reverse source-release
+success, and optional investigation must not delay release completion.
+
+## Versioning And Compatibility
+
+Stable releases use Semantic Versioning in the form `vMAJOR.MINOR.PATCH`, with
+no leading zeroes. Prereleases are not part of the adopted release channel.
+
+The selected version must be unused locally and on the authoritative remote.
+Do not require queries to every configured remote or publication service.
+A version known to have already been published must not be reused, even if the
+normal guards do not inspect that channel. Adding a distribution channel
+requires a deliberate update to the policy and procedure where needed.
+
+For releases at or after `v1.0.0`:
+
+- a major release may make intentional incompatible changes;
+- a minor release may add backward-compatible behavior; and
+- a patch release may make backward-compatible fixes.
+
+Before `v1.0.0`, a minor release may change a documented public, operational,
+configuration, data, integration, or compatibility contract when the release
+note explains the impact and required consumer action. A patch release must
+not intentionally break those contracts within its minor line.
+
+Additional compatibility promises and deliberate exceptions belong in the
+adopted policy or canonical contract documentation. Release notes explain
+changes; they do not redefine current compatibility contracts.
+
+## Release Documentation And Preparation
+
+Every new release must include `docs/releases/<version>.md` in the tagged
+source tree. Use the complete version tag as the filename and begin with a
+title containing the product name and that exact version.
+
+Include a short summary and any relevant compatibility impact or upgrade
+instructions. Keep the note proportionate to the change. Fixed sections and
+explicit no-action boilerplate are not required. Existing historical notes
+need not be rewritten to adopt this format.
+
+Include the release footer defined by the [OSS policy](oss.md#discoverability)
+in each new release document and preserve it on the hosted download page. The
+release procedure defines the concrete URLs and publication mechanics. Prepare
+these links with the release note; they do not add a network check or approval
+gate.
+
+Keep exact current contracts in their canonical documents and update affected
+documentation with the behavior change. Link to those documents from the note
+where useful. A release note must not substitute for current documentation.
+Use annotated tags with their message derived from the checked-in note rather
+than requiring a separately authored account of the same release.
+
+Version selection, release-note content, and retirement of completed roadmaps
+are preparation responsibilities, not separate human approval gates. Preserve
+planned and deferred work and repair affected links when retiring roadmaps.
+Ordinary change review covers unintended files, credentials, and private data;
+do not repeat it as a release-specific sign-off. Ignored local files are not
+prohibited merely because they exist: they are not included in the tagged source.
+
+## Candidate Validation
+
+Provide one publication command that validates the final committed candidate,
+checks publication state, and publishes the intended refs. A validation-only
+mode or command may be provided for diagnosis, but must not be a required step
+before publication repeats the same checks.
+
+Run the complete deterministic, offline default test suite once for the final
+candidate, following the [testing policy](testing.md), and verify the required
+build targets. Select those targets for the application's actual support
+commitments; native testing on each platform and access to particular hardware
+are not default release prerequisites.
+
+The selected test invocation includes the race detector because the HTTP
+service shares engines and backend capacity state across concurrent requests.
+This single invocation covers both ordinary assertions and race detection.
+Build both declared Linux architectures with the hosted release flags to catch
+cross-compilation and packaging failures; native test hardware for each target
+is not required. Existing architecture tests enforce dependency boundaries.
+
+Retain narrow source guards against committed workspaces, vendor trees, and
+module replacements: these can otherwise make a passing local build depend on
+unpublished or substituted framework code. Disable workspace discovery and
+vendor mode during validation. These guards preserve the established
+cross-project boundary; they do not require exact dependency-version audits or
+module-metadata rewrites at release time.
+
+Additional gates must address a concrete risk that the existing checks do not
+adequately cover. Do not automatically require linting, race testing, module
+hygiene audits, documentation audits, credential scans, example validation, or
+expanded platform matrices solely because they are possible. Retain such
+checks when their distinct protection justifies their cost. A one-time migration
+check must not silently become a permanent release requirement.
+
+Release tests must not require real credentials, mutable application services,
+paid APIs, provider probes, or inference calls. The procedure describes
+dependency preparation separately from offline validation.
+
+Avoid duplicate validation across release phases. Successful checks for the
+same final candidate need not be repeated solely to satisfy another phase;
+any reuse must clearly apply to that exact candidate. Persistent validation
+caches are not required. If the candidate changes, validate the new candidate.
+Cheap publication-state checks may be repeated immediately before pushing
+because local or remote state may have changed during validation.
+
+Automate mechanical guards. Human review gates are strongly disfavored: add one
+only through an explicit project-specific policy decision explaining the
+concrete risk and why ordinary change review or automation is insufficient.
+Do not add routine confirmations for checks the command can perform itself.
+
+## Publication Guards
+
+Automate the checks needed to publish the intended source under a fresh version:
+
+- the version has the adopted format and is unused locally and on the
+  authoritative remote;
+- the worktree and index are clean on the primary release branch;
+- the source being published is the exact candidate that passed validation,
+  including its matching release note;
+- the remote primary branch already identifies that exact candidate; and
+- the tag identifies the validated candidate and only the intended refs are
+  published.
+
+Fetch the authoritative branch and tag state as needed for these checks.
+Do not force branch or tag updates to bypass a failed guard. Publish explicit
+refs rather than all local tags. Do not require CI success, publication-service
+availability checks, or a separate manual confirmation for each guard.
+
+## Immutability And Failure Recovery
+
+Published version tags and published contents are immutable. Do not move,
+overwrite, recreate, or delete a published tag, or replace a published artifact,
+checksum, signature, provenance statement, or release note under that version.
+The checked-in note at the immutable tag is that release's historical record.
+
+If validation fails before publication, correct and commit the candidate and
+rerun the publication command. If a push fails or its outcome is ambiguous,
+inspect the authoritative remote before retrying. Remove an unpublished local
+tag only after confirming it was never published or used by a release channel.
+An unavailable remote leaves publication status unknown; do not overwrite a tag
+to resolve uncertainty.
+
+Transient network, authentication, CI, or consumer-availability failures do not
+by themselves require a new version. Asynchronous delivery may be retried from
+the same immutable tag. Missing artifacts may be published later, provided
+existing published contents are not replaced and the additions remain consistent
+with the tagged source and any already-published checksum manifest. If that
+cannot be achieved, publish a new version.
+
+A defect requiring changes to published source or contents requires a corrected
+commit, a new semantically appropriate version, a matching release note, and
+the release procedure again. Leave the original release intact. A channel's
+yank, deprecation, or advisory mechanism may warn consumers away from a defective
+release without replacing its contents or reusing its version.
+
+## Repository Release Procedure
+
+Maintain `docs/release.md` as a short, executable maintainer runbook. It must
+identify:
+
+1. prerequisites, primary branch, and authoritative remote;
+2. version and release-note preparation;
+3. one publication command with its selected local checks and automated guards;
+4. declared deliverables, required build targets, and automation responsibilities;
+5. the successful-push completion point and separately reported delivery status;
+   and
+6. failure handling, ambiguous-push recovery, and asynchronous delivery retries.
+
+Use copyable commands where practical. Keep optional diagnostics and consumer
+verification clearly optional. The procedure must not turn preparation work,
+ordinary change review, or post-publication investigation into additional
+release gates.

docs/policy/testing.md

@@ -0,0 +1,291 @@
+# Testing Policy
+
+**Base Policy Version:** 1.1
+
+**Last Updated:** 2026-09-26
+
+## Purpose
+
+Our tests exist to make **incorrect changes expensive and correct changes cheap**.
+
+We do not optimize for test count, line coverage, exhaustive isolation, or the fewest possible tests. We optimize for sufficient confidence in important behavior while imposing as little unnecessary friction as possible on future development.
+
+## Every test has a cost
+
+Every test has an immediate and continuing cost: writing, review, execution,
+diagnosis, fixture maintenance, and updates when legitimate behavior changes.
+Tests can also constrain refactoring, duplicate policy, and add failure noise.
+
+A test is warranted only when the confidence it provides justifies these costs.
+Evaluate that tradeoff at two levels:
+
+1. **Per test:** What realistic defect does this test detect, how consequential would that defect be, and is that protection worth the test's lifetime cost?
+2. **Across the suite:** Does this collection provide materially more confidence than a smaller, simpler suite would?
+
+Some friction is intentional. Tests should make dangerous changes—such as breaking compatibility, corrupting data, violating security boundaries, or reintroducing subtle bugs—require deliberate review. They should not make ordinary internal changes needlessly expensive.
+
+The cost of a test is not a reason to omit testing by default. Do not cite maintenance cost abstractly. When omitting a plausible test, be able to state why the protected failure is low-risk, already covered, obvious, reversible, or cheaper to detect elsewhere. For consequential, subtle, or difficult-to-observe behavior, the presumption should favor testing.
+
+## Default testing style
+
+Use a **classical/Detroit-style** approach:
+
+- Test observable behavior, resulting state, contracts, and invariants.
+- Use real internal collaborators when they are fast and deterministic.
+- Use fakes, stubs, or mocks primarily at expensive, nondeterministic, destructive, or external boundaries.
+- Prefer package-level behavioral tests over tests coupled to private helpers or internal call sequences.
+- Treat exact collaborator interactions as testable behavior only when the interaction itself is a requirement.
+
+Examples of appropriate seams include clocks, randomness, subprocesses, remote APIs, object storage, email, and paid LLM calls.
+
+## Test execution requirements
+
+Tests in the default suite must be deterministic, offline, and independent of real credentials. They must not invoke paid APIs or depend on mutable external services. Tests that require live infrastructure must be explicitly opt-in and clearly separated from the default suite.
+
+Control clocks, randomness, environment variables, and other process-global or machine-specific state when they affect behavior. Tests should be safe to run repeatedly and alongside other tests without depending on execution order or state left by an earlier test.
+
+## What deserves tests
+
+To the extent the following features are present in the application, prioritize tests for:
+
+1. Public and package-level contracts.
+2. Domain rules and important invariants.
+3. Boundary conditions and malformed input.
+4. Failure handling, cancellation, retries, recovery, and partial success.
+5. Serialization, schemas, compatibility, and round trips.
+6. Previously observed or plausible regressions.
+7. Representative integration and end-to-end workflows.
+
+A package-level contract is behavior relied upon by another package or major collaborator, not every observable detail of a package implementation.
+
+Choose tests for requested behavior and established contracts. Tests must not
+introduce new restrictions, guarantees, or threat scenarios merely because they
+could be asserted. Follow the [agent policy](agents.md) when deciding whether a
+behavior belongs to the contract; current implementation behavior alone is not
+sufficient authority.
+
+For established behavior involving **data integrity, destructive operations,
+compatibility, security, concurrency, idempotency, or recovery**, favor durable
+tests for realistic failures whose consequences warrant protection. Identify
+the failure and the existing contract it would violate. These categories call
+for attention, not an automatic test inventory or permission to strengthen the
+application's guarantees. Account for protection already provided at other layers.
+
+Do not add tests merely because a function, branch, or line exists. Do not add a test when the same meaningful risk is already adequately protected elsewhere.
+
+## Choose the right test boundary
+
+Test through the narrowest stable boundary that expresses the behavior clearly.
+
+For application configuration, ConfigKit owns exhaustive YAML grammar,
+source traversal, import/overlay composition, provenance, and inspection
+renderer tests. Scriptorium tests its selected definition, source discovery,
+CLI override presence, command prerequisites, runtime conversion, credential
+boundary, and representative execution/inspection workflows with the tagged
+library. Do not copy the upstream parser test matrix into this repository.
+
+This is often the package API, but it may instead be:
+
+- a smaller pure function when dense domain logic is most clearly isolated there;
+- a package-level operation when several internal collaborators jointly produce the behavior; or
+- a larger integration boundary when correctness emerges from interaction with a real dependency.
+
+Do not force all behavior through oversized end-to-end tests. Do not test every private helper merely because it exists. Choose the boundary that gives durable confidence with the least incidental coupling.
+
+## Test behavior, not implementation
+
+A test should protect a decision, contract, or invariant. A test must not memorialize the current implementation.
+
+A test is suspect when its main purpose is to detect that someone:
+
+- changed an internal constant;
+- renamed or split a private helper;
+- reordered equivalent internal operations;
+- changed incidental formatting;
+- replaced one correct algorithm with another; or
+- refactored internal object structure without changing behavior.
+
+Refactoring should normally require no test edits unless the refactored structure is itself part of the contract.
+
+## Expected effects of different changes
+
+Use the following expectations when evaluating test failures and test maintenance:
+
+| Change | Expected effect on tests |
+|---|---|
+| Internal refactor that preserves behavior | Existing tests should normally remain unchanged and continue to pass. |
+| Change to an internal default with no contractual significance | Behavioral tests should normally remain unchanged; tests should derive expectations from configuration or relationships rather than duplicate the old value. |
+| Intentional change to public behavior, policy, schema, or compatibility guarantees | The relevant tests should be reviewed and changed deliberately. |
+| Accidental violation of a contract or invariant | Tests should fail; fix the production code rather than rewriting the tests to accept the defect. |
+
+A test failing is not the same as a test needing to be edited. Many tests may correctly fail because of one production defect. The maintenance smell is a correct internal change that requires unrelated expectation updates throughout the suite.
+
+## Separate mechanism from policy
+
+Configurable thresholds and defaults must not be duplicated throughout the test suite.
+
+For this example, assume the selected contract rejects a request to start more
+processes than a configured limit. Do not encode its production default indirectly:
+
+```go
+// Production default:
+const maxConcurrency = 4
+
+// Brittle test:
+err := startProcesses(5)
+require.Error(t, err)
+```
+
+Instead, test the mechanism relationally:
+
+```go
+const limit = 2
+runner := NewRunner(limit)
+
+require.NoError(t, runner.Start(limit))
+require.ErrorIs(t, runner.Start(limit+1), ErrTooMuchConcurrency)
+```
+
+For this selected contract, the test should prove:
+
+- the configured limit is accepted; and
+- one beyond the configured limit is rejected.
+
+Rejection is not a general requirement for concurrency control. If the selected
+contract queues excess work or limits active workers while accepting larger
+batches, test that behavior instead. Do not add rejection or a configurable
+limit solely to reproduce this example.
+
+The production default should be tested exactly only when its literal value is itself a public, operational, safety, protocol, or compatibility requirement.
+
+Apply the same rule to limits, timeouts, capacities, retry counts, and ranges: test relationships and behavior, not duplicated literals.
+
+For established concurrency limits, distinguish these behaviors where the contract requires them:
+
+1. **Configuration handling:** values are accepted or rejected according to the selected contract.
+2. **Runtime enforcement:** observed peak concurrency never exceeds the configured limit.
+
+Use a test-controlled limit and measure the behavior relative to that limit. Do not merely assert today's default value.
+
+## Avoid semantic duplication across layers
+
+Each behavior should have a clear test owner.
+
+- Configuration tests own application YAML, strict decoding, discovery,
+  precedence, and application defaults.
+- CLI tests own argument mapping, streams, summaries, exit behavior, and
+  representative command workflows.
+- HTTP tests own DTOs, strict decoding, limits, status mapping, and restricted
+  artifact policy.
+- Formatter tests own prepared-run and definition-inspection text and JSON
+  presentation.
+- Architecture tests own dependency direction and removal invariants.
+- Promptkit owns framework parsing, orchestration, validation, profiles, and
+  model-client behavior. Scriptorium's definition compatibility fixtures protect
+  its adapter plumbing without duplicating the upstream format contract.
+
+Higher-level tests should not repeat every lower-level case. A single intentional policy change should not require unrelated edits across many test files.
+
+## Use test doubles deliberately
+
+Choose the least elaborate test double that provides the required control or observation.
+
+As a default:
+
+1. Prefer real collaborators when they are fast and deterministic.
+2. Use small in-memory fakes when realistic stateful behavior is helpful.
+3. Use stubs when a dependency only needs to provide controlled responses.
+4. Use mocks when the interaction itself is contractual.
+
+Mocks are appropriate when the contract includes facts such as:
+
+- a notification is sent exactly once;
+- a transaction is committed only after successful writes;
+- cancellation reaches a subprocess;
+- an expensive API is called no more than once; or
+- a security audit event is emitted.
+
+Do not use mocks merely to isolate every object or reproduce the implementation's call graph.
+
+## Go-specific guidance
+
+Select techniques according to the behavior and risk being tested. The following
+are options, not a checklist that every package or application must satisfy:
+
+- table-driven tests for meaningful behavioral categories and boundaries;
+- `t.TempDir()` for real filesystem behavior;
+- `httptest.Server` for realistic HTTP interactions;
+- fuzz tests when exploring broad input spaces, such as parsers or path handling, adds useful protection beyond representative cases;
+- golden files only when the complete output is intentionally stable;
+- integration tests where correctness depends on component interaction; and
+- a small number of representative end-to-end tests when assembled workflows expose meaningful risks not adequately covered at narrower boundaries.
+
+Avoid exact error-string assertions unless the wording is itself contractual. Prefer `errors.Is`, `errors.As`, typed errors, or structured error fields.
+
+At CLI boundaries, prefer exit classifications, structured output, and the smallest stable semantic fragment needed to identify the error. Do not snapshot complete diagnostic wording unless it is contractual.
+
+Golden-file updates must require an explicit local flag. CI must not update golden files automatically, and reviewers must inspect the semantic diff before accepting an update.
+
+Keep tests readable and direct. Test helpers and fixture frameworks must earn their own maintenance cost; do not build elaborate test infrastructure for small or isolated needs.
+
+## Coverage
+
+Coverage is a diagnostic, not a target.
+
+Use it to find untested critical branches and unexpectedly weak packages. Do not write low-value tests solely to increase a percentage, and do not infer test quality from coverage alone.
+
+Security-sensitive HTTP containment and external mappings may warrant denser
+coverage than straightforward process wiring. Uneven coverage is acceptable
+when it reflects risk.
+
+## Regression tests
+
+A bug fix should normally include a regression test that fails before the fix and passes afterward.
+
+Retain the test when the defect could realistically recur and its consequences justify the ongoing cost. Prefer the narrowest durable test of the violated contract or invariant; do not preserve accidental implementation details from the original bug.
+
+Not every historical bug requires a permanent test. If the underlying design has made recurrence impossible, the test has become redundant, or a stronger invariant test now subsumes it, remove or consolidate it.
+
+## Deleting or rewriting tests
+
+Tests are maintained code, not permanent historical artifacts.
+
+Delete or rewrite a test when its maintenance cost exceeds the confidence it provides.
+
+Strong candidates include tests that:
+
+- require updates after harmless internal changes;
+- directly assert private constants without protecting a real contract;
+- duplicate the same policy across several layers;
+- verify mock choreography rather than outcomes;
+- snapshot large amounts of incidental output;
+- test trivial private helpers already exercised through stable package behavior;
+- protect risks already covered more effectively elsewhere;
+- are flaky, misleading, obsolete, or disproportionately expensive to diagnose; or
+- no longer correspond to a plausible failure mode.
+
+Several brittle tests may encode one genuine requirement. Replace them with one durable behavior-level or invariant test rather than preserving all of them.
+
+## Reviewing a proposed test
+
+Use the following questions when the value, boundary, or durability of a proposed test is not self-evident. Significant test additions should be reviewable against them, but written answers are not required for every routine test.
+
+1. Which requested behavior or established contract does it protect, and what realistic defect would violate it?
+2. How likely and consequential is that defect, and is it already protected elsewhere?
+3. What is the narrowest stable boundary that can test it clearly?
+4. Would a correct internal refactor or a change to an incidental default require test edits?
+5. Does its confidence justify its maintenance, execution, and diagnostic cost, or would a smaller test suffice?
+
+## Definition of sufficient
+
+A test suite is sufficient when:
+
+- important requested behavior and established contracts are protected against realistic, consequential failures;
+- boundaries and component interactions have coverage where they introduce meaningful risks not protected elsewhere;
+- failures provide useful signal rather than redundant noise;
+- legitimate internal changes usually do not require test edits; and
+- additional tests would mostly repeat existing protection or preserve inconsequential implementation details.
+
+Sufficiency is a risk judgment, not a coverage percentage, test count, or required
+mix of testing techniques. Reassess it as the application, its users, and the
+consequences of failure evolve.

docs/release.md

@@ -0,0 +1,143 @@
+# Release Procedure
+
+The [release policy](policy/release.md) owns versioning, compatibility,
+publication completion, and immutability. This runbook supplies Scriptorium's
+commands; release notes under `docs/releases/` are historical summaries. The
+[OSS policy](policy/oss.md#discoverability) owns license and attribution
+discoverability requirements.
+
+## Prepare The Candidate
+
+Use a POSIX shell, Git with a configured tagger identity and access to
+`origin`, and a Go toolchain compatible with `go.mod`. The native host must
+support Go's race detector and have its required C compiler. If Git is
+configured to sign tags, its signing tool and key must be available. Run from the
+repository root. Provision the toolchain and module cache before offline
+validation; when dependencies are not cached:
+
+```sh
+GOWORK=off go mod download
+```
+
+Choose an unused stable version under the release policy. Commit its note as
+`docs/releases/<version>.md`, beginning with a title such as
+`# Scriptorium v0.14.0` (an example, not an instruction to select that version).
+Include a concise summary and relevant compatibility impact or upgrade action.
+End the note with the following footer, replacing `<version>` in both absolute
+URLs with the selected version tag (for example, `v0.14.0`):
+
+```markdown
+[LICENSE](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/<version>/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/<version>/docs/oss/attribution.md)
+```
+
+Check that both URLs name files in the candidate tree at that tag. The tag may
+not resolve online until publication. The checked-in note is copied unchanged
+into the hosted release body by the existing workflow, so do not maintain a
+second footer there.
+Update affected canonical documentation with the change, and retire completed
+roadmap material when appropriate while preserving deferred work and links.
+No extra release-specific review signoff is required.
+
+Finish and commit the intended candidate on `main`, then publish that branch:
+
+```sh
+git -c push.followTags=false push origin refs/heads/main:refs/heads/main
+```
+
+The publication command inspects the configured push endpoint of `origin`,
+not a potentially stale remote-tracking ref. If a separate push URL is
+configured, it is authoritative for both checks and publication. Configure one
+publication URL; multiple push endpoints cannot be validated as one remote.
+
+## Publish
+
+Invoke the single [publication command](../scripts/release.sh), substituting
+the selected version:
+
+```sh
+sh scripts/release.sh v0.14.0
+```
+
+The command validates a clean worktree and index on `main`, an unused local and
+remote version, exact agreement with authoritative remote `main`, and a
+checked-in note whose first-level title contains Scriptorium and the exact
+version. Ignored local files do not make the candidate dirty.
+
+The existing source-boundary guards reject committed workspaces, vendor trees,
+and module replacements. No migration-specific exact Promptkit version audit
+is required.
+
+It then runs the complete suite once with the race detector and builds Linux
+amd64 and arm64 binaries using `CGO_ENABLED=0`, `-trimpath`, and
+`-ldflags '-s -w'`. The native test run uses the host platform and enables cgo.
+Validation disables workspaces, uses read-only module mode, and disables module
+and toolchain downloads. Missing dependencies must be provisioned separately;
+fix the environment and rerun the command. No persistent validation cache is
+maintained by the release tool.
+
+The command rechecks candidate and publication state, creates an annotated tag
+from the committed note, and pushes only that tag's exact object to its explicit
+ref. It does not push branches, follow other tags, force updates, or wait for
+CI. Temporary notes and validation builds are removed on exit. The successful
+summary identifies the source commit and tag object and reports binary
+delivery separately as asynchronous and unverified.
+
+## Asynchronous Binary Delivery
+
+The tag-triggered [hosted workflow](../.woodpecker/release.yml) builds and
+publishes:
+
+- `scriptorium-<version>-linux-amd64`;
+- `scriptorium-<version>-linux-arm64`; and
+- `SHA256SUMS`.
+
+The matching checked-in note supplies the hosted release body. The workflow
+owns image selection, packaging, checksum generation, and upload configuration.
+Its upload step skips existing files and does not overwrite the release.
+Source-publication success does not attest to workflow success or asset
+availability.
+
+Workflow inspection, downloads, checksum verification, and a compatible-host
+smoke test are optional delivery diagnostics. They must not delay or redefine
+source-release completion. No polling or consumer-installation check is part
+of the publication command.
+
+## Failure Recovery
+
+Before tag creation, correct and commit a failed candidate, publish `main`,
+and invoke the publication command again. A changed candidate must pass its
+own validation.
+
+After an unsuccessful push, the command queries the authoritative endpoint.
+If it confirms the exact tag object and candidate, it reports source success.
+Otherwise it exits unsuccessfully and preserves the local tag. It never retries
+a push or deletes a tag automatically. If the endpoint is unavailable, the
+publication status is unknown, not evidence that nothing was published.
+
+For manual diagnosis, select the affected version and compare the local tag
+object and peeled commit with the authoritative remote:
+
+```sh
+release_version=v0.14.0
+release_remote=$(git remote get-url --push origin)
+git rev-parse "refs/tags/$release_version" "refs/tags/$release_version^{commit}"
+git ls-remote "$release_remote" refs/heads/main \
+    "refs/tags/$release_version" "refs/tags/$release_version^{}"
+```
+
+Do not retry while the outcome remains unknown. If the tag exists remotely,
+do not move, recreate, or delete it. If the tag was never published or used by
+any release channel, an explicitly authorized local cleanup may delete only
+that unpublished tag; then rerun the command to validate and publish the
+candidate. The command intentionally rejects an existing local tag rather than
+assuming that a previous process validated it.
+
+For transient delivery failures, inspect what has already been uploaded before
+retrying the same immutable tag. The upload step's skip behavior alone does not
+prove checksum consistency. Add missing assets only if they match the tagged
+source and any already-published manifest, without replacing existing contents.
+Compare rebuilt bytes with published checksums when recovering a partial
+upload; do not assume toolchain changes reproduce identical binaries. If safe
+completion is impossible, or published source, notes, packaging, or artifact
+contents need correction, leave the original release intact and publish a new
+version from a corrected commit.

docs/releases/v0.12.0.md

@@ -0,0 +1,36 @@
+# Scriptorium v0.12.0
+
+## Breaking Project Boundary
+
+Scriptorium is now an executable-only CLI and HTTP application. This is a
+breaking change for Go consumers: the former root Go package is not included,
+and no compatibility facade is provided.
+
+Scriptorium `v0.11.1` was the final framework-bearing release. Former Go
+consumers should follow the
+[migration guide](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.12.0/docs/consumers/migrating-to-promptkit.md)
+and adopt
+[Promptkit `v0.1.0`](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.1.0/docs/consumers/pkg-promptkit.md)
+for in-process prompt preparation and execution.
+
+## Application Interfaces
+
+The Scriptorium command-line and HTTP application interfaces remain. Their
+canonical documentation defines the supported commands, configuration,
+requests, responses, operational behavior, and deployment responsibilities:
+
+- [CLI reference](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.12.0/docs/cli.md)
+- [HTTP API reference](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.12.0/docs/api.md)
+- [Configuration reference](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.12.0/docs/config.md)
+- [Operations guide](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.12.0/docs/operations.md)
+
+## Framework Dependency And Consumers
+
+The released Scriptorium binaries use Promptkit `v0.1.0` as their framework
+dependency. Promptkit owns the reusable engine, source formats, profiles,
+generation boundary, and validation contracts. See the
+[Promptkit Go consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.1.0/docs/consumers/pkg-promptkit.md)
+for that supported API.
+
+All known downstream Go consumers were migrated to Promptkit before this
+release.

docs/releases/v0.13.0.md

@@ -0,0 +1,59 @@
+# Scriptorium v0.13.0
+
+## Promptkit v0.9 Adoption
+
+Scriptorium now uses
+[Promptkit `v0.9.0`](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/)
+and supports the complete Promptkit v0.9 prompt and profile definition format
+through its configured directory sources. This includes prompt versions,
+optional inputs, all supported message roles, cache control, session templates,
+output schemas and repair budgets, profile inheritance, backend selection,
+provider controls, optional credential environment names, and JSON-compatible
+extra parameters.
+
+Promptkit remains the canonical owner of definition parsing and framework
+validation. Scriptorium continues to own its CLI, HTTP, configuration,
+presentation, and deployment contracts.
+
+## Application Features
+
+- `run` and `render` can select an explicit prompt version and can execute
+  prompts that do not declare or reference inputs.
+- CLI and HTTP requests can provide a direct session ID. Reasoning controls can
+  inherit, replace, or explicitly clear the selected profile value.
+- Application configuration can register custom OpenAI-compatible backends
+  with optional credential environment names, extra parameters, concurrency
+  limits, and queue policy.
+- `inspect prompt` and `inspect profile` provide deterministic text or JSON
+  views without invoking a model. Profile inspection does not read credential
+  values or require a prompt definition.
+- Prepared output, CLI summaries, and HTTP metadata report effective backend
+  identity when available.
+- HTTP requests rejected by backend capacity policy return `503` with the
+  stable `capacity_exceeded` code. One server-scoped Promptkit engine enforces
+  those limits across concurrent requests.
+
+See the versioned application contracts for exact behavior:
+
+- [CLI reference](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.13.0/docs/cli.md)
+- [HTTP API reference](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.13.0/docs/api.md)
+- [Configuration reference](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.13.0/docs/config.md)
+- [Operations guide](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.13.0/docs/operations.md)
+- [Promptkit v0.9 format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/docs/formats.md)
+
+## Compatibility And Operations
+
+There are no intentional removals from the v0.12 application interfaces. The
+Promptkit upgrade does enforce its current definition-safety rules, including
+supported message roles, absolute HTTP or HTTPS endpoints, contained content
+and schema paths, bounded repair budgets, and JSON-compatible extra parameters.
+Definitions rejected by these rules must be corrected before use.
+
+Credential values remain outside configuration, definition files, CLI flags,
+and HTTP payloads. Named environment sources are optional unless a selected
+Promptkit profile explicitly requires a key. A positive repair budget permits
+additional provider calls and can increase latency, token use, and cost.
+
+The HTTP service retains only the shared operational state needed for backend
+admission and in-flight request handling. Scriptorium does not retain durable
+conversation, workflow, checkpoint, or resume state.

docs/releases/v0.14.0.md

@@ -0,0 +1,66 @@
+# Scriptorium v0.14.0
+
+This minor release adopts Promptkit v0.11.0 and ConfigKit v0.4.0, adds
+application-configuration inspection, and exposes request retry controls,
+whole-run deadlines, and optional terminal execution reports.
+
+## Configuration migration
+
+Scriptorium now uses ConfigKit for application configuration. This intentionally
+changes accepted input and precedence:
+
+- An existing empty file is invalid; use `{}` for an empty mapping. Explicit
+  empty strings and zeroes replace lower values, while `null` is accepted only
+  for nullable fields. `--config ''` is invalid. An explicitly empty server
+  address reaches the standard HTTP server rather than restoring `:8080`.
+- YAML decoding is stricter: unknown fields, additional documents,
+  anchors/aliases, unsupported scalar forms, and other inputs rejected by
+  ConfigKit now fail. The `configkit` key is reserved, and ConfigKit's source
+  and resource limits apply. Backend parameter integers use its `int64` shape.
+- File-backed configurations can explicitly import path or glob fragments and
+  select one named overlay with `--config-overlay`. These files stay under the
+  selected configuration file's canonical directory. Application path *values*
+  remain relative to the process working directory. Only explicitly supplied
+  application CLI flags override file or overlay settings.
+
+Use `config validate`, `config show`, `config sources`, and `config explain` to
+inspect application settings without creating an engine or contacting a model.
+Validation is not a provider probe or complete Promptkit definition check;
+effective output is not guaranteed reloadable. Inspection keeps ordinary
+`extra_params` values, including historical values, and `api_key_env` reference
+names visible. Keep secrets out of parameters and protect inspection output;
+actual API-key values remain with Promptkit and are never resolved by ConfigKit.
+Request retry overrides and Promptkit credential requirements are separate
+from application configuration.
+
+## Promptkit and execution changes
+
+Promptkit v0.11.0 uses its `/v2` catalogs. The `deepseek-3-2`,
+`deepseek-4-flash`, and `deepseek-4-pro` profile IDs are removed without aliases;
+select an available catalog profile, a maintained Promptkit profile, or a
+complete application-owned profile.
+
+Promptkit's built-in transient retry default is two additional attempts. This
+can increase provider calls, latency, and cost; an application or request
+retry override of zero disables additional attempts. Repair generations have
+their own retry budgets. Generation timeouts apply per attempt. CLI
+`--run-timeout` and HTTP `run_timeout_seconds` add optional whole-run deadlines;
+an expired HTTP execution returns `504 deadline_exceeded`, caller cancellation
+returns `408 request_canceled`, and a live-context provider-attempt failure
+remains a 502 response.
+
+CLI `--execution-report` and HTTP `include_execution_report` expose optional
+terminal reports. Reports are absent when no terminal observation exists, can
+contain sensitive identifiers, and do not replace result usage. CLI report
+writes are separate and nontransactional; HTTP report bytes count toward the
+response-size limit.
+
+For complete behavior, see the
+[CLI](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.14.0/docs/cli.md),
+[configuration](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.14.0/docs/config.md),
+[HTTP API](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.14.0/docs/api.md),
+and [operations](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.14.0/docs/operations.md)
+references. The repository now includes
+[dependency attribution and license texts](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.14.0/docs/oss/attribution.md).
+
+[LICENSE](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.14.0/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/scriptorium/src/tag/v0.14.0/docs/oss/attribution.md)

docs/roadmap/configkit.md

@@ -0,0 +1,231 @@
+# ConfigKit Adoption
+
+## Status And Intent
+
+Implemented feature direction, drafted on 2026-09-26 and delivered through the
+[implementation plan](implementation.md). This roadmap records the target
+behavior and changes from the reviewed baseline; the implementation plan owns
+sequencing, concrete interfaces, and verification evidence.
+
+The user is adopting ConfigKit across an application suite to standardize
+configuration semantics. Scriptorium will make a clean cutover to ConfigKit's
+native conventions, including intentional breaking changes. Preserving the
+legacy loader's behavior is not a goal: there will be no parallel legacy loader,
+compatibility mode, or recreation of the old merging rules.
+
+Alignment applies to application configuration, not to Promptkit-owned prompt,
+profile, or schema definitions. Departures from ConfigKit conventions require an
+application-specific reason or a genuine ownership boundary, not backward
+compatibility alone. The [architecture policy](../policy/architecture.md) and
+[ADR 0004](../adr/0004-definition-boundary.md) remain the scope boundaries.
+
+## Reviewed Baseline (Historical)
+
+Scriptorium consumes Promptkit v0.11.0. Its `internal/config` package uses
+yaml.v3 directly and manually applies defaults, file settings, and CLI overrides.
+It has a parser-specific integer decoder, ignores empty string overrides, and
+treats an empty configuration file as defaults-only input. It has no application
+configuration imports, selected overlays, or provenance/inspection interface.
+The [configuration reference](../config.md), [CLI reference](../cli.md), and
+[source internals](../internal/sources.md) own the current behavior.
+
+The reviewed ConfigKit release is v0.4.0 at commit
+`e6ced0d3d1194b58e0b3dc8970089471ba175258`. Adopt that published release as the
+initial target, rather than a sibling checkout or unpublished replacement.
+Its canonical references are:
+
+- [Configuration contract](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/e6ced0d3d1194b58e0b3dc8970089471ba175258/docs/config.md).
+- [Consumer adoption guide](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/e6ced0d3d1194b58e0b3dc8970089471ba175258/docs/consumers/README.md).
+- [Release notes](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/e6ced0d3d1194b58e0b3dc8970089471ba175258/docs/releases/v0.4.0.md).
+
+ConfigKit requires Go 1.25, within Scriptorium's existing toolchain requirement.
+It selects `go.yaml.in/yaml/v4 v4.0.0-rc.6`. Removing Scriptorium's direct parser
+usage does not remove yaml.v3 from the dependency graph: Promptkit still uses it.
+The initial review passed ConfigKit's default test suite and Scriptorium's
+configuration and CLI tests; that is baseline evidence, not migration validation.
+
+## Target Ownership And Loading Model
+
+| Owner | Responsibility |
+| --- | --- |
+| ConfigKit | Application YAML policy, source acquisition, composition, overlays, typed decoding, explicit override application, provenance, and redacted inspection. |
+| Scriptorium | Source discovery, application schema and defaults, CLI parsing, recorded application normalization, semantic validation, command prerequisites, and runtime conversion. |
+| Promptkit | Framework definition formats, backend semantics, credential lookup, engine defaults, and prompt execution. |
+
+`internal/config` becomes a small application-specific ConfigKit integration,
+not a second general-purpose configuration framework. Execution and inspection
+share one configuration definition and loading pipeline. Defaults, selected base
+and imports, selected overlay, and explicit application CLI overrides participate
+in ConfigKit's lifecycle; resolution and validation follow its upstream rules.
+Normalization that changes inspected values is recorded through its resolver.
+Runtime conversion does not perform a hidden second merge or apply new defaults
+after the inspection snapshot has been created.
+
+Scriptorium retains its application field names and domain meanings unless a
+specific change below requires otherwise. ConfigKit's public root API replaces
+direct YAML decoding and parser-specific hooks. Application defaults remain
+Scriptorium-owned; omitted framework settings still delegate to Promptkit.
+Backend conversion retains deterministic registration and engine-scoped shared
+capacity state. This work does not change the HTTP request contract or move
+configuration loading into each HTTP request.
+
+## Native Configuration Semantics
+
+The target accepts ConfigKit's upstream YAML grammar, schema binding, limits,
+composition, and value-presence rules without a legacy preprocessing layer.
+Migration-visible changes include:
+
+- An existing empty file is invalid; `{}` expresses an empty application mapping.
+  Defaults-only operation with no discovered file uses `NoSource` instead.
+- Explicit empty strings, false values, and zeroes replace defaults. They are
+  not silently treated as omission. Application validation still decides whether
+  a resulting value is meaningful for its field or selected command.
+- Null follows the application's declared nullable types. It is not a universal
+  spelling for omission. Scalars and structs do not accept null merely because
+  the former parser tolerated it.
+- Anchors, aliases, merge keys, explicit tags, additional documents, unsupported
+  scalar spellings, and coercions rejected by ConfigKit are rejected here too.
+- ConfigKit's reserved `configkit` key and resource limits apply, including in
+  dynamic application data. These constraints do not apply to independently
+  loaded Promptkit definitions or HTTP request bodies.
+- Dynamic integers in backend `extra_params` use ConfigKit's `int64`
+  representation. Runtime mapping preserves their supported value semantics
+  rather than reserializing through YAML or demanding the old Go scalar type.
+
+Presence remains meaningful at the framework boundary: omitted/null
+`transient_retries` delegates to Promptkit, while explicit zero disables retries;
+omitted backend queue capacity differs from explicit zero. Application HTTP
+size defaults and zero-as-unlimited behavior remain. No new value ranges or
+backend restrictions are introduced merely to adopt the library.
+
+## Discovery, Imports, Overlays, And Paths
+
+Source discovery remains Scriptorium-owned. The target retains the documented
+explicit `--config` selection and ordered system-location search. An explicitly
+empty config path is invalid rather than an implicit request for a default file.
+If neither implicit candidate exists, loading uses defaults only; a selected
+file that fails loading is not silently replaced with defaults. No implicit
+working-directory configuration search, environment overlay, or directory scan
+is added.
+
+Application configuration supports ConfigKit's explicit path and glob imports.
+Imports compose disjoint definitions; repeated non-mapping definitions are
+conflicts, not last-writer-wins overrides. There is no implicit `conf.d` scan.
+
+An optional `--config-overlay` selects ConfigKit's one named overlay using its
+standard `overlays/<name>.yml` location, naming rules, and merge behavior. No
+overlay is selected by default. Selecting an active overlay without a base
+source follows ConfigKit's rejection of overlays with `NoSource`; Scriptorium
+does not invent a root. Application overlays do not replace `--profile`,
+`profile_dir`, or Promptkit's execution-profile selection.
+
+Use the selected file's canonical directory as ConfigKit's default import and
+overlay root. This root governs configuration source traversal only. Values of
+`prompt_dir`, `profile_dir`, `schema_dir`, and `server.artifact_root` retain
+working-directory-relative interpretation; absolute values remain absolute.
+This is an explicit application path policy, not an upstream requirement or a
+legacy parsing mode. ConfigKit's consumer examples demonstrate alternatives but
+do not mandate source-file-relative application paths. This adoption does not
+extend import containment to application data or alter HTTP artifact containment.
+
+## CLI Overrides And Configuration Inspection
+
+Only flags explicitly supplied by the user become ConfigKit application
+override records. Parser defaults do not overwrite file or overlay settings.
+Explicit empty values are not dropped. The existing invocation-specific prompt,
+profile, input, model, timeout, output, and reporting options remain invocation
+state rather than new application configuration fields. In particular, the
+run/render retry flag remains a request override; it does not mutate the engine's
+application retry setting or backend state.
+
+Expose application configuration validation, effective redacted YAML, source
+provenance, and explanation of an individual configuration path. These are
+included features, not merely library capabilities available for future work.
+They use ConfigKit diagnostics and inspection records from the shared loading
+pipeline, including defaults, imports, overlays, explicit CLI values, and
+recorded normalization. No separate inspection-only interpretation is maintained.
+
+Configuration inspection does not execute prompts, make provider calls, or
+resolve API-key values. Application validation is not a promise that every
+Promptkit backend or definition is valid or that a provider is reachable.
+Command-specific execution prerequisites remain with the relevant command;
+inspection can explain an incomplete application configuration without requiring
+an executable prompt selection. The interface is a CLI configuration command
+family, not a second CLI framework or an HTTP configuration endpoint; the
+implementation plan specifies its concrete commands and mappings.
+
+Safe diagnostics must not restore raw parser errors or configuration values
+that ConfigKit deliberately suppresses. Effective output and explanation use
+the upstream redacted renderers; they are inspection output, not guaranteed
+reloadable configuration. Under the maintainer's selected policy, backend
+`extra_params` are visible in effective output and explanation, including
+historical values. There is no blanket container masking, sensitive-key heuristic,
+or new selective-redaction configuration surface.
+
+## Credential Boundary And Deferred Features
+
+Existing `api_key_env` values remain environment-name strings passed to Promptkit.
+They do not become ConfigKit `Secret` fields. ConfigKit eagerly resolves effective
+typed references and requires nonempty values; that would change Promptkit's
+optional/required and selected-credential behavior. This departure from the
+secret-reference feature is an ownership decision, not compatibility plumbing.
+Raw API-key fields remain unsupported under the existing architecture policy.
+
+API-key values are the only secrets requiring ConfigKit redaction in this
+adoption. The application configuration holds environment-variable names, not
+those values, so inspection neither resolves nor contains the actual keys.
+Reference names remain visible. Do not tag `api_key_env` as secret merely to
+hide its name, add an eager key lookup, or mask unrelated application settings.
+The existing raw-key prohibition and Promptkit boundary provide the protection
+without introducing a redundant credential-bearing configuration field.
+
+Secrets-directory bootstrap and application schema versioning are deferred until
+there is a concrete application need. Their availability in ConfigKit does not
+make them mandatory. Hot reload, runtime resource replacement, remote imports,
+automatic migrations, and general environment-variable overlays are outside
+this adoption. These are scope limits for this feature, not new permanent
+prohibitions on future explicitly requested work.
+
+## Required Changes And Completion Criteria
+
+- Replace manual decoding/default/override machinery with the shared ConfigKit
+  integration and retain only application-specific discovery, rules, and mapping.
+- Support imports and selected overlays across commands that load application
+  configuration, and deliver the configuration inspection capabilities above.
+- Update application configuration types, presence handling, CLI explicit-set
+  mapping, and diagnostics to match the selected native semantics.
+- Update maintained examples and canonical configuration, CLI, operations,
+  architecture, and internal documentation when behavior lands. Upstream generic
+  contracts remain linked rather than copied into a competing specification.
+- Add proportionate integration coverage for the cutover: defaults-only input,
+  explicit values and nulls, imports/conflicts, overlays, CLI precedence,
+  inspection agreement and API-key non-disclosure, visible dynamic backend
+  parameters, unchanged credential ownership, and representative
+  execution/server startup.
+  ConfigKit owns exhaustive parser and composition tests; Scriptorium tests its
+  adoption and application boundaries.
+- Pin the published dependency and maintain ConfigKit and YAML attribution under
+  the [OSS policy](../policy/oss.md), using imported-commit source/notice links
+  and applicable standard and companion license texts.
+- Document migration in a release appropriate for the intentional breaking
+  configuration changes under the [release policy](../policy/release.md).
+  Release selection and publication remain separate preparation work; this
+  roadmap adds no release gate, network probe, or new distribution format.
+
+Completion means one ConfigKit-native application configuration path serves
+execution and inspection, the selected user-facing features work, and migrated
+examples and regression coverage demonstrate the documented semantics. It does
+not require adopting every ConfigKit feature or changing Promptkit definitions.
+
+## Resolved Inspection Policy
+
+On 2026-09-26 the maintainer selected no redaction for `extra_params` and limited
+the relevant secret to the API key. Inspection therefore preserves parameter
+values and environment-reference names, while actual API-key values remain
+outside the application configuration pipeline. Visibility is intentional;
+this is not a promise to detect secrets placed inside arbitrary parameter values.
+
+The delivered `config show` and `config explain` commands use ConfigKit's
+inspection writers without secret tags or a second redaction path. Both
+effective and historical parameter values remain visible; `api_key_env` names
+remain visible while Promptkit alone resolves selected credential values.

docs/roadmap/implementation.md

@@ -0,0 +1,536 @@
+# ConfigKit Adoption Implementation Plan
+
+## Status, Authority, And Historical Plans
+
+Planned on 2026-09-26 against Scriptorium commit
+`43eea5c7c41d2a8134b3dece60f3af5c98b8fd1c`. This document records the
+ordered implementation and its completion evidence. The maintainer resolved
+the inspection-policy question:
+`extra_params` remain visible; only API-key values require secret protection.
+
+The [feature roadmap](configkit.md) owns scope, target behavior, and user intent.
+This plan owns implementation steps and the interface choices needed to execute
+them. Read [development](../development.md) and every policy before work:
+[agents](../policy/agents.md), [architecture](../policy/architecture.md),
+[documentation](../policy/documentation.md), [testing](../policy/testing.md),
+[release](../policy/release.md), and [OSS](../policy/oss.md).
+[ADR 0004](../adr/0004-definition-boundary.md) continues to govern Promptkit's
+definition boundary. Do not rewrite accepted ADR decisions.
+
+This filename previously contained completed Promptkit plans. Older roadmap
+links to this file refer to these historical records, not the ConfigKit stages:
+
+- Completed v0.11 implementation and release handoff:
+  `git show 43eea5c7c41d2a8134b3dece60f3af5c98b8fd1c:docs/roadmap/implementation.md`.
+- Completed v0.9 implementation:
+  `git show e4405966c87c8a7843b340146e90cc1e515bef42:docs/roadmap/implementation.md`.
+
+Those deliveries must not be repeated or lost from upcoming release preparation.
+These Git records are available locally without publishing the recent commits.
+
+## Working Rules And Selected Design
+
+The dependency target is `gitea.maximumdirect.net/eric/ConfigKit v0.4.0`,
+commit `e6ced0d3d1194b58e0b3dc8970089471ba175258`. Use its public root package,
+imported as `configkit`. The roadmap links the exact upstream contracts.
+Do not opportunistically upgrade Promptkit or other dependencies, commit a
+workspace/replacement, or depend on sibling source at runtime.
+
+This is a clean configuration cutover, not a compatibility project. Native
+ConfigKit syntax, presence, nullability, resource limits, and precedence apply.
+Do not add a pre-parser, YAML serialization round trip, alternate merge engine,
+legacy mode, generic provider abstraction, or a new CLI framework.
+
+Keep application source discovery and domain rules in `internal/config`;
+CLI parsing/output stays in `internal/adapter/cli`. Promptkit remains responsible
+for prompt/profile/schema parsing, backend semantics, credentials, and engine
+behavior. Keep one shared server engine and existing HTTP artifact policy.
+No HTTP schema, execution-report, request-timeout, or retry-orchestration change
+is part of this plan.
+
+For every stage:
+
+1. Inspect the working tree and relevant code/tests through the repository's
+   code-discovery guidance. Preserve unrelated changes.
+2. Implement the listed outcome and only supporting refactoring it needs.
+   Internal names below are selected implementation guidance, not public APIs
+   or immutable package-layout contracts.
+3. Update canonical current-state docs when behavior lands. Until Stage 3 the
+   new loader is internal preparation, not an advertised executable feature.
+   Never claim later stages are implemented.
+4. Run focused tests and the development guide's baseline validation for code
+   changes. Tests stay offline, deterministic, and free of real credentials.
+   Reuse existing coverage rather than cloning ConfigKit's parser test matrix.
+5. Format changed Go files, inspect the diff, validate affected docs/examples,
+   record stage status/evidence here, and commit the coherent unit. Do not push,
+   tag, publish, or add new release gates.
+
+### Application Configuration Definition
+
+Use a new `Document` type in `internal/config` for the native configuration
+shape. It replaces the old on-disk `Config` after CLI cutover. Keep the familiar
+YAML field names:
+
+| YAML path | Go shape | Default and selected meaning |
+| --- | --- | --- |
+| `prompt_dir`, `profile_dir` | `string` | Empty; no source configured. |
+| `schema_dir` | `string` | Existing schema-directory default. Empty remains empty at the application boundary; Promptkit owns any subsequent framework default. |
+| `transient_retries` | `*int` | Nil; omitted/null delegates, zero disables additional attempts. |
+| `server` | Non-pointer struct | Its children receive typed defaults; null is invalid. |
+| `server.addr` | `string` | Existing listen-address default when absent; explicit empty is passed unchanged to the standard HTTP server, not replaced with the Scriptorium default. |
+| `server.artifact_root` | `string` | Empty; HTTP file input remains disabled. |
+| Three `server.max_*_bytes` fields | `int64` | Existing defaults; explicit zero disables the respective limit; null is invalid. |
+| `defaults` | Non-pointer struct | Contains `render_format`; null is invalid. |
+| `defaults.render_format` | `string` | Existing text default; resolved value must be text or json. Explicit empty is invalid, not defaulted. |
+| `backends` | `map[string]BackendDocument` | Nil; null is permitted, an empty mapping follows ConfigKit semantics. |
+
+`BackendDocument` keeps `endpoint string`, `api_key_env string`,
+`extra_params map[string]any`, `concurrency_limit int`, and
+`queue_capacity *int`. Scalar nulls are invalid; nullable maps/pointers retain
+native semantics. No catalog IDs or Promptkit fields are added.
+
+The fresh defaults factory reads existing `internal/defaults` and format
+constants, not a duplicated set of literals. Normalization trims surrounding
+whitespace from application directory strings, artifact root, and server
+address; cleans only nonempty application paths; and lowercases/trims
+`defaults.render_format`. Empty paths remain empty: never let
+`filepath.Clean("")` turn disabled/unset into `.`. Record actual changes with
+`configkit.Normalize`, using value-free reasons. Do not normalize backend
+fields or parameter values on Promptkit's behalf.
+
+The read-only validator reports negative application size limits, negative
+nonnull application retries, and invalid render format through
+`Validation.Error` at their field paths. It does not print rejected values.
+Do not call the existing format parser's empty-as-default branch for this field.
+Do not add endpoint, backend ID, credential-presence, directory-existence,
+address-format, or positive-only-capacity checks. Existing Promptkit and
+command-specific validation retains those responsibilities where applicable.
+
+## Stage 1: Add The Dependency And Native Application Definition
+
+**Status: Complete.** The pinned dependency, native definition, focused
+presence/normalization/validation tests, and commit-specific attribution are in
+place. The existing executable loader remains active pending the command cutover.
+
+Primary files: `go.mod`, `go.sum`, new focused files under `internal/config`,
+and `docs/oss/attribution.md`.
+
+1. Add ConfigKit at the selected release. Retain Promptkit v0.11.0 and its
+   selected catalogs. Provision dependencies outside offline test execution.
+   ConfigKit's yaml/v4 release-candidate dependency is the reviewed upstream
+   choice, not an instruction to upgrade its parser independently.
+2. Implement `Document`, `BackendDocument`, the fresh defaults factory,
+   recorded resolver, and read-only validator described above. Keep the old
+   loader operational until Stage 3 so this stage remains independently
+   buildable; this temporary development state is not a shipped compatibility
+   mode or a second user-selectable configuration path.
+3. Test the new definition using real `configkit.Load[Document]` with
+   `Bytes` and `NoSource`. Cover explicit zero/empty/null distinctions,
+   retry/queue nil-versus-zero, safe application validation, and a normalized
+   path whose effective output agrees with the returned value. Include nested
+   unknown fields and a representative dynamic numeric parameter.
+4. Add ConfigKit and yaml/v4 attribution from their selected source material.
+   Resolve the imported yaml/v4 commit from release/module metadata. Preserve
+   actual copyright statements; do not infer a project statement from the
+   FSF license-document copyright. Use applicable SPDX expressions, local
+   standard texts, and commit-pinned upstream license/notice links. Reuse GPL,
+   LGPL, MIT, and Apache texts where applicable, including companion links.
+   Retain yaml.v3 attribution because Promptkit still incorporates it.
+5. Document the internal definition as preparation in the relevant internal
+   guide without claiming the CLI has switched. No current configuration
+   contract changes yet.
+
+Acceptance: the dependency and definition compile, focused tests demonstrate
+native semantics and audited normalization, and attribution follows the OSS
+policy. Existing executable behavior still passes its tests.
+
+## Stage 2: Build Discovery And The Shared Loading Boundary
+
+**Status: Complete.** Ordered source discovery, one ConfigKit load, typed
+diagnostics, and settings conversion are covered by focused file/default and
+override tests. Existing commands still use the old entry point until cutover.
+
+Primary files: `internal/config` and its tests; `docs/internal/sources.md`.
+
+1. Add `LoadOptions` with `Path string`, `Explicit bool`, `Overlay string`,
+   and `Overrides []configkit.Override`, plus
+   `Load(LoadOptions) (*configkit.Result[Document], error)`.
+   Discovery chooses a source; the one ConfigKit call owns actual file reading
+   and decoding. Return the result so consumers retain the frozen inspection
+   snapshot as well as the typed configuration.
+2. With `Explicit=true`, pass the selected path to `configkit.File`;
+   an explicitly empty path is invalid, not implicit discovery or a fallback
+   to the old system filename. Do not silently trim a source filename into a
+   different filename. ConfigKit validates and resolves file sources.
+3. With `Explicit=false`, ignore the option's path value and examine the
+   existing ordered implicit search locations. Only nonexistence permits
+   examining the next candidate. Other stat failures are errors. Select the
+   first existing candidate and let ConfigKit load it. A selected file's later
+   disappearance/read/parse failure does not restart discovery.
+4. If neither implicit candidate exists, use `NoSource`. Initially leave
+   imports disabled and the overlay empty; Stage 4 enables composition.
+   Defaults-only loads still accept explicit application overrides. Never
+   reinterpret an empty file as `NoSource`.
+5. Pass overrides into the ConfigKit call before decoding/validation; do not
+   validate a separately merged lower configuration first. Native parsing and
+   composition failures still follow the upstream lifecycle and are not
+   bypassed by CLI overrides.
+6. Add a small `Settings(Document) AppSettings` conversion for existing
+   executable wiring. It copies resolved fields, maps the already-validated
+   format, and converts the backend map into ID-sorted backend settings.
+   It performs no file IO, normalization, credential lookup, semantic backend
+   checks, or additional defaults. Dynamic values retain their decoded shapes.
+7. Preserve ConfigKit's typed `*LoadError` through wrapping so the CLI can
+   render safe structured diagnostics. Discovery-only errors are concise and
+   quote paths safely; no new public error taxonomy is needed.
+8. Test ordered discovery with temporary paths rather than host system files,
+   explicit missing/empty paths, empty-file rejection versus `{}`,
+   defaults-only loading, source records, override-before-validation behavior,
+   sorted backend conversion, and preservation of zero/nullable values.
+   Remove no existing entry point until all its CLI callers migrate in Stage 3.
+
+Acceptance: real files and defaults-only inputs produce one reusable result,
+runtime conversion agrees with it, and tests do not depend on machine-wide
+configuration or secrets. The old and new internals are temporarily buildable,
+with no new user-visible mode.
+
+## Stage 3: Cut Existing Commands Over And Remove The Legacy Loader
+
+**Status: Complete.** All five command modes use the shared ConfigKit loader;
+the legacy decoder and merge path are removed. CLI and configuration contracts
+now describe native YAML and override behavior. Full test, race, vet, build,
+and diff checks passed.
+
+Primary files: `internal/adapter/cli/run.go`, `inspect.go`,
+`internal/config/config.go`, and associated tests.
+
+1. Route run, render, serve, inspect prompt, and inspect profile through the
+   shared `Load` and `Settings` boundary. Preserve the explicit presence of
+   `--config` in every parser. Centralize the small application-flag mapping
+   rather than reproduce it in each command.
+2. Use `flag.FlagSet.Visit` (or the existing explicit-set helper) to create
+   one `configkit.Override` per explicitly supplied application flag. Use
+   `configkit.Keys`, built-in scalar values, and a safe `Flag` label containing
+   only the flag name. Standard flag parsing's last occurrence supplies the
+   single override; do not emit duplicate records or parser defaults.
+
+   | Flag | Application path | Existing command scope after cutover |
+   | --- | --- | --- |
+   | `--prompt-dir` | `prompt_dir` | run, render, serve, inspect prompt |
+   | `--profile-dir` | `profile_dir` | run, render, serve, inspect profile |
+   | `--schema-dir` | `schema_dir` | run, render, serve |
+   | `--addr` | `server.addr` | serve |
+   | `--artifact-root` | `server.artifact_root` | serve |
+   | `--max-request-bytes` | `server.max_request_bytes` | serve |
+   | `--max-artifact-bytes` | `server.max_artifact_bytes` | serve |
+   | `--max-response-bytes` | `server.max_response_bytes` | serve |
+
+   Register the schema-directory flag on render as well as run/serve so the
+   advertised application path override is consistently usable. This is not a
+   general expansion of runtime/provider flags to other commands.
+3. Keep `--format`, `--out`, request `--transient-retries`, prompt/profile
+   selection, model overrides, timeouts, inputs, variables, and reporting
+   options outside the application configuration tree. In particular,
+   `render --format` overrides that invocation's output format without
+   rewriting `defaults.render_format`; omitted format inherits its resolved
+   application value. Existing invocation-only parsing remains unchanged.
+4. Remove post-load directory trimming/cleaning/defaulting from argument
+   finalizers, including unconditional schema-path cleaning. Keep only
+   invocation-owned transformations such as output-file paths. Explicit
+   empty profile/artifact-root overrides must clear file-provided values;
+   explicit empty prompt directory must reach the existing execution
+   prerequisite rather than revive the lower value.
+5. Keep existing command prerequisites: run/render/serve and prompt inspection
+   need their effective prompt directory as currently required; profile
+   inspection does not acquire a prompt-directory requirement. All commands
+   still perform the common application schema validation. Do not introduce
+   eager filesystem or credential validation for inspection.
+6. Add one CLI diagnostic path using `errors.As` and
+   `configkit.WriteDiagnostics` for load errors. Carry successful load warnings
+   to the command boundary and render them once on stderr before execution or
+   output. Handle diagnostic writer errors as command failures. Do not flatten
+   structured failures into raw parser text or print rejected values.
+   Preserve existing process exit classifications; application/parse/load
+   failures are exit 1, not generated-output validation exit 2.
+7. Remove the old YAML decoder, `strictInteger.UnmarshalYAML`, old on-disk
+   types, `applyConfig`, `ApplyCLIOverrides`, and unused compatibility
+   sentinels/helpers after migrating all callers/tests. Keep only one defaults
+   factory. Remove the direct yaml.v3 import; module tidy may retain yaml.v3
+   as an indirect Promptkit dependency.
+8. Update tests to the deliberate breaking semantics, not the legacy behavior.
+   Protect explicit empty path clearing, scalar-null rejection, unknown fields,
+   rejected empty/multi-document input, one representative YAML policy change,
+   unchanged request-versus-engine retry precedence, absent optional
+   credentials, and command-specific inspection prerequisites.
+9. Update configuration and CLI contracts, source/adapter internals, architecture
+   ownership, and the contributor reading guide for the delivered cutover.
+   Preserve existing application defaults, Promptkit definition support,
+   HTTP containment, shared capacity, and report behavior. Adjust the current
+   CLI claim that every command requires a prompt directory to match actual
+   command-specific requirements.
+
+Acceptance: all existing commands use ConfigKit, no legacy parser or second
+application merge remains, relevant tests pass, and diagnostics and docs describe
+the native breaking behavior. Imports/overlays and new inspection commands are
+not yet advertised.
+
+## Stage 4: Enable Explicit Imports And Selected Configuration Overlays
+
+**Status: Complete.** File-backed loads support explicit imports and one
+selected overlay under the selected file's canonical directory. All five
+existing command modes accept `--config-overlay`; real-file composition and a
+render workflow are tested. The composed example and contracts are updated;
+full test, race, vet, build, and diff checks passed.
+
+Primary files: shared loader, CLI source-selection wiring, configuration and
+CLI tests, maintained configuration examples.
+
+1. Enable `Options.Imports` for file-backed loads. Leave it false for
+   `NoSource`, which rejects imports. Use ConfigKit's default canonical
+   selected-file directory as the root; do not supply a wider filesystem root
+   or add application traversal code.
+2. Wire `LoadOptions.Overlay` into `Options.Overlay`. Register
+   `--config-overlay` on all five existing configuration-loading command
+   modes. Treat the value exactly as an upstream overlay name: no trimming,
+   case folding, extension fallback, path expansion, or local inheritance.
+   Empty and exact lowercase default mean no active overlay under v0.4.0.
+   A requested active overlay without a selected base source fails through
+   ConfigKit; do not manufacture an empty base file or root.
+3. Use native `configkit.imports` directives for explicit paths/globs. The
+   application enables the feature without requiring a second CLI opt-in;
+   absent directives cause no discovery. Retain conflict-based base
+   composition and native overlay replacement/null semantics.
+4. Preserve working-directory-relative application path values even when
+   authored in fragments or overlays. Configuration-source containment is
+   not the HTTP artifact policy and is not applied to prompt/schema paths.
+5. Add focused real-file tests for disjoint backend fragments, an import
+   conflict, overlay replacement, explicit CLI precedence, missing selected
+   overlay, and no-base overlay failure. Verify `--profile` still selects a
+   Promptkit execution profile independently of `--config-overlay`.
+   One real command workflow proves wiring; upstream owns exhaustive glob,
+   symlink, cycle, and parser-limit tests.
+6. Add a small synthetic import/overlay example under `examples/`; preserve
+   a simple single-file quickstart. Update config/CLI contracts and operations
+   guidance for the new features, root selection, and relative-value policy.
+
+Acceptance: supported commands load the same native composition pipeline;
+imports are explicit, overlays remain distinct from execution profiles, and no
+new scanning, remote acquisition, or path policy is introduced.
+
+## Stage 5: Add Application Validation, Effective Output, And Source Inspection
+
+**Status: Complete.** Application-only validation, effective YAML, and ordered
+JSON source inspection use one shared ConfigKit result without an engine. Tests
+cover source composition, CLI provenance, stream failures, and the credential
+reference boundary. Public and internal contracts are updated; full test,
+race, vet, build, and diff checks passed.
+
+Primary files: a focused `internal/adapter/cli/config.go`, shared config
+definition, CLI dispatch/help/tests, and canonical CLI/config documentation.
+
+1. Apply the maintainer's selected inspection policy: no redaction for
+   `extra_params`, including historical values. API-key values are the only
+   relevant secrets, but this schema stores only `api_key_env` reference names.
+   Keep those names visible and never resolve them in the ConfigKit load.
+   Do not add secret tags to the reference name or parameter container, a
+   catch-all secret predicate, sensitive-key guessing, or a selective masking
+   interface. Actual credentials remain with Promptkit; raw API-key fields
+   remain rejected. Use upstream inspection renderers without adding a second
+   value-rendering path or a synthetic credential field.
+2. Add a top-level `config` command family using the existing standard-library
+   flag style. The selected interfaces are:
+
+   | Command | Success stdout |
+   | --- | --- |
+   | `scriptorium config validate [flags]` | Empty; exit status communicates application validation success. |
+   | `scriptorium config show [flags]` | `Result.WriteEffective` redacted YAML. |
+   | `scriptorium config sources [flags]` | One newline-terminated JSON array of source records. |
+   | `scriptorium config explain --path <pointer> [flags]` | Added in Stage 6. |
+
+   These are prospective interface specifications, not commands to execute
+   before their stages are implemented.
+3. All configuration subcommands accept `--config`, `--config-overlay`,
+   and the eight application override flags in Stage 3's table, regardless
+   of which execution command normally uses them. They do not accept request,
+   credential, backend-editing, output-format, or output-file flags. Shell
+   redirection is sufficient for these inspection outputs. No positional
+   arguments are accepted.
+4. Load exactly once through the common loader. Do not construct a Promptkit
+   engine, restricted artifact reader, listener, or client. Missing prompt
+   directories, unselected/absent credentials, and framework backend validity
+   are not additional application-inspection gates. Invalid application
+   types/ranges/format still fail. Validation describes application load
+   validity, not end-to-end executability.
+5. For sources, map `Result.Sources()` to a small local DTO with JSON keys
+   `id`, `label`, `layer` (always present), and `path` (omit when empty).
+   Preserve upstream source order; emit `[]\n` for defaults-only input without
+   overrides. Include synthetic CLI sources where present. Do not marshal
+   opaque ConfigKit implementation objects. The standard JSON encoder escapes
+   control characters; no custom terminal rendering is necessary.
+6. Diagnostics/warnings go only to stderr through the shared diagnostic helper.
+   Successful operations exit 0; parse/load/output/diagnostic-write failures
+   exit 1. No exit 2 meaning is introduced for configuration validation.
+   Ordinary writer failures may leave partial output; do not promise atomic
+   streams or buffering of an entire configuration.
+7. Test defaults-only show/sources, a composed load with CLI provenance,
+   explicit empty clearing, normalized effective values, failed loads producing
+   no successful stdout, and writer failure. Set a synthetic API-key environment
+   variable: effective output must show its reference name, not its value.
+   Repeat with the variable absent to establish that inspection does not require
+   credentials. Assert that ordinary synthetic parameter values remain visible
+   and runtime ExtraParams stay intact; no real environment or provider is used.
+8. Update CLI/config contracts, README navigation, subprocess integration,
+   operations, and internal inventory to describe only these delivered modes.
+   Retain the README's license/attribution ending.
+
+Acceptance: validation, effective output, and source inspection use the same
+resolved configuration as execution, preserve stream separation, and honor the
+selected API-key boundary without masking or changing backend parameter data.
+
+## Stage 6: Add Per-Path Explanation And Verify Credential Boundaries
+
+**Status: Complete.** `config explain` uses required JSON Pointer paths and
+ConfigKit's snapshot renderer, including historical and normalized values.
+Tests cover root, escaped/numeric keys, unknown paths, writer failures, and
+synthetic credential-reference boundaries. Full test, race, vet, build, and
+diff checks passed.
+
+Primary files: configuration command implementation/tests and CLI/config docs.
+
+1. Implement `config explain` with the same selectors and override flags as
+   Stage 5 plus a required, explicitly supplied `--path`. Parse using
+   `configkit.ParsePath`; syntax is JSON Pointer, not dotted notation, a file
+   path, or a URL fragment. Explicit `--path ""` selects the root; an omitted
+   flag is an error. Preserve escaped and numeric mapping-key semantics.
+2. Use the successful shared result's `WriteExplanation`. Explain known
+   effective and historical paths, including removed values. An unknown or
+   malformed path exits 1 with no successful explanation output. Quote
+   user-supplied paths safely if included in application diagnostics.
+   Do not rebuild history, look up environment values, or reload sources.
+3. Keep the upstream human-readable renderer and its redaction semantics rather
+   than inventing a JSON explanation schema or freezing the entire rendered
+   prose as an application guarantee. Writer failures exit 1 and can leave
+   partial output, as with effective output.
+4. Test a value's default/base/overlay/CLI history, recorded normalization,
+   explicit equal-value writes, an escaped backend key, root selection, and
+   an unknown path. Cover a displaced historical backend parameter value:
+   it remains visible, including in a container/root explanation. Use distinct
+   synthetic environment names and key values to verify reference names remain
+   explainable but resolved API-key bytes are absent from all history/output.
+5. Update CLI/config docs and operations guidance with path syntax,
+   historical-value meaning, representation differences, and sensitive
+   identifiers/paths. Do not claim that redaction detects arbitrary secrets
+   outside classified paths.
+
+Acceptance: explain uses the existing snapshot and upstream semantics; its
+history matches the selected inputs and normalization, parameters remain
+visible, and explanation neither resolves nor discloses API-key values.
+
+## Stage 7: Verify Integration, Finish Documentation, And Record Release Handoff
+
+**Status: Complete.** The feature roadmap, command paths, dependency boundary,
+documentation, and attribution were audited. Maintained single-file and
+composed examples passed configuration inspection and no-provider rendering;
+the optional-credential/integer-parameter backend path passed with a local
+provider. The full test, race, vet, build, formatting, link, and diff checks
+passed. Release preparation is recorded below; no tag or publication occurred.
+
+1. Review the feature roadmap against actual code. Confirm all five original
+   command modes and all four new configuration subcommands use one definition
+   and load pipeline. Remove any transitional loader, duplicated defaults,
+   unused compatibility helpers, or post-snapshot configuration mutation.
+   Do not add architecture machinery merely to assert a particular file layout.
+2. Exercise maintained single-file and import/overlay examples through the
+   implemented configuration commands and a no-provider render workflow.
+   Use focused backend integration evidence that dynamic integer parameters
+   reach Promptkit correctly and missing optional credentials retain their
+   established meaning. Use a local HTTP server only where provider serialization
+   must be checked; never a real service or credential.
+3. Retain existing HTTP concurrency, containment, error mapping, retry,
+   timeout, and report tests. Add a representative configuration-to-server
+   wiring test only if existing coverage misses changed settings propagation;
+   do not reproduce all upstream scheduling or HTTP cases.
+4. Run the development baseline on final code: `go test ./...`,
+   `go test -race ./...`, `go vet ./...`, and
+   `go build ./cmd/scriptorium`. Check formatting, affected examples/links,
+   and `git diff --check`. Do not stage the built binary or scratch files.
+   Compare any new standard license text byte-for-byte; preserve upstream
+   whitespace rather than editing license wording to satisfy a style check.
+5. Ensure current configuration, CLI, subprocess, operations, internal docs,
+   contributor routing, and architecture ownership agree. Testing policy
+   should identify ConfigKit as the owner of exhaustive upstream loading tests,
+   while Scriptorium owns application adoption tests. Change policy dates when
+   revising policies, not base versions unless adopting new templates.
+   Keep accepted ADR text and published release notes immutable.
+6. Record the release handoff below and mark only delivered stages complete.
+   Update the feature roadmap's status, including the resolved inspection
+   decision. Preserve deferred work. The next breaking release follows the
+   release policy; version selection, candidate publication validation, release
+   notes at that version, tag creation, and publishing are not this sprint.
+7. Commit the final coherent handoff and report validation evidence, remaining
+   limitations, and any outstanding work without claiming source/binary
+   publication or complete legal compliance.
+
+Acceptance: the ConfigKit-native target is delivered with proportionate
+regression evidence and accurate documentation, and the workspace contains no
+temporary dependency substitutions or uncommitted implementation artifacts.
+
+### Release Handoff To Retain
+
+The upcoming release needs migration guidance for empty files versus `{}`,
+explicit empty values, nullable versus scalar fields, strict YAML/scalars,
+reserved keys and upstream size limits, and the invalid explicit-empty config
+path. Include imports/overlays, application path interpretation, CLI presence,
+inspection command scope, and the selected API-key-only secret policy. Explicit
+empty server address reaches standard HTTP server behavior instead of restoring
+Scriptorium's default; operators should supply their intended listen address.
+
+Keep request retry overrides and Promptkit credential semantics distinct from
+application settings. Explain that configuration validation is not a provider
+probe or complete Promptkit definition validator, and that inspection output
+is not guaranteed reloadable. Include dependency/attribution changes and the
+existing LICENSE | ATTRIBUTION footer. Preserve the still-relevant Promptkit
+v0.11 release handoff identified above when preparing a combined next release.
+
+### Implementation And Release Preparation Record
+
+The ConfigKit v0.4.0 adoption is implemented in committed source. The next
+breaking release still needs version selection, version-matched release notes,
+candidate validation, tagging, and publication under the release policy; none
+has occurred as part of this work. Keep the earlier Promptkit v0.11 handoff
+linked above when preparing a combined release.
+
+The release note should summarize the deliberate configuration migration:
+empty files now fail and `{}` means an empty mapping; explicitly empty strings
+and zero values override lower values; `null` follows declared nullable types;
+strict YAML rejects additional documents, anchors/aliases, unsupported scalar
+forms, and unknown fields; `configkit` is reserved and ConfigKit's source and
+resource limits apply. Explicit `--config ''` is invalid. Imports are opt-in
+per file directive, while `--config-overlay` selects one named overlay under
+the selected file's canonical directory; application path *values* remain
+process-working-directory-relative. Only explicitly supplied application CLI
+flags override configuration. An explicit empty server address is passed to
+the standard HTTP server and does not restore Scriptorium's default.
+
+Document the four application-inspection modes and the selected policy:
+`extra_params`, including history, and `api_key_env` reference names remain
+visible, but actual API-key bytes are never resolved by ConfigKit. Inspection
+output can be sensitive and is not guaranteed reloadable. Application
+validation neither probes a provider nor completely validates Promptkit
+definitions. Keep request retry overrides and Promptkit's credential rules
+separate from application settings. Include the new dependency and attribution
+notices, and retain the existing LICENSE | ATTRIBUTION footer. Deferred
+secrets bootstrap, schema versioning, reload, and remote acquisition remain
+deferred; do not imply source or binary publication has happened.
+
+## Open Questions
+
+None remain for this scope. On 2026-09-26 the maintainer selected no redaction
+for `extra_params` and specified that the API key is the only secret requiring
+ConfigKit redaction. Stages 5–6 implement that decision through visible parameter
+values/reference names and the existing separation of actual credentials from
+application configuration. Do not reopen it or substitute blanket masking.
+
+This does not claim automatic detection of credentials embedded in arbitrary
+strings or provider parameters. The application schema still rejects raw API-key
+fields, and Promptkit remains responsible for resolving named credential sources.

docs/roadmap/policy.md

@@ -0,0 +1,63 @@
+# OSS Policy Adoption
+
+## Status
+
+Completed on 2026-09-26. The upstream template work proposed here is now
+available and adopted locally. This document records the adoption; the
+[OSS policy](../policy/oss.md) is the canonical owner of the ongoing rules.
+
+The adopted baseline is the standard policy repository at commit
+`eea8bcd21a964b395e31971077d7fddb445f2c28`:
+
+- OSS policy base version 1.1;
+- documentation policy base version 1.4; and
+- release policy base version 1.2.
+
+Each affected policy records its base version and local update date. Template
+adoption instructions were removed. Unchanged agent, architecture, and testing
+policies retain their existing versions.
+
+## Adoption Outcome
+
+- [Documentation ownership](../policy/documentation.md) distinguishes the
+  project license, component entries, standard texts, and OSS policy.
+- The [contributor guide](../development.md) routes dependency, copied-asset,
+  attribution, and release-document work to the OSS policy.
+- [Component entries](../oss/attribution.md) cover the six selected direct and
+  transitive Go modules. Source and project-specific notice links identify the
+  imported commits. LGPL entries link directly to both LGPL v3 and GPL v3.
+- Project-specific notices are linked upstream under the adopted house
+  interpretation. YAML's former local LICENSE and NOTICE copies were removed;
+  their history remains in Git. Missing upstream copyright statements are
+  identified in the affected entries rather than fabricated.
+- The five applicable standard texts in `docs/oss/licenses/` match the upstream
+  reference collection byte-for-byte: GPL v3, LGPL v3, Apache 2.0, BSD 3-Clause,
+  and MIT. The reference collection documents their publisher/SPDX provenance.
+  Adoption removed a stray LGPL prefix, restored the complete Apache text,
+  separated the standard BSD text from the Go-specific notice, and added MIT.
+- The [README](../../README.md) ends with friendly project-license and
+  attribution links. The [release policy](../policy/release.md) delegates footer
+  conventions to the OSS policy; the [release procedure](../release.md) retains
+  Scriptorium's immutable-tag URLs and existing hosted-body reuse.
+
+## Preserved Scope
+
+This adoption changes documentation and attribution, not Scriptorium's license,
+dependencies, application architecture, or release machinery. Published notes,
+tags, and assets remain unchanged. Existing source-release completion and
+asynchronous binary-delivery behavior remain intact.
+
+There is no new publication-time network check, approval gate, scanner, source
+bundle, downloadable license asset, or modified-dependency rebuild exercise.
+Concrete exceptions continue to receive the treatment specified by the adopted
+OSS policy; the house format is not a universal legal-sufficiency guarantee.
+
+## Validation
+
+The standard texts were compared against the upstream reference collection.
+The BSD reference intentionally retains its publisher's trailing space in the
+copyright placeholder; it is not reformatted to satisfy a whitespace check.
+Dependency commit references were resolved from Go module origin metadata or
+the selected upstream tag, and affected local links and upstream attribution
+destinations were checked. No runtime code, commands, or executable examples
+changed.

docs/roadmap/promptkit-v0.9.0-adoption.md

@@ -0,0 +1,351 @@
+# Promptkit v0.9.0 Adoption Roadmap
+
+## Status
+
+Complete. This document records the delivered feature scope and targeted end
+state. The completed delivery plan is maintained in
+[implementation.md](implementation.md); current behavior remains defined by
+the canonical application contracts linked below.
+
+The durable product and integration boundary for this work is established by
+[ADR 0004](../adr/0004-definition-boundary.md). This roadmap applies that
+decision to Promptkit v0.9.0 and owns implementation scope and completion
+status.
+
+## Objective
+
+Bring Scriptorium from Promptkit v0.1.0 to v0.9.0 and expose the newer
+framework capabilities that fit Scriptorium's existing CLI, HTTP,
+configuration, presentation, and process boundaries.
+
+Scriptorium must accept the complete Promptkit v0.9.0 feature set expressed by
+directory-backed prompt, profile, and schema definitions. Application adapters
+must not narrow that format contract by requiring request values that the
+selected definition does not require or by omitting selection values needed to
+address a valid definition. Promptkit's tagged
+[framework format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/docs/formats.md)
+remains canonical; Scriptorium must delegate parsing and framework validation
+rather than reproduce those rules.
+
+The completed application will retain Promptkit as the owner of reusable
+prompt execution, source formats, profiles, backend definitions, capacity,
+inspection, generation, and validation. Scriptorium will continue to own
+application configuration, command and HTTP contracts, error and exit mapping,
+output presentation, and deployment policy.
+
+## Targeted End State
+
+When this roadmap is complete:
+
+- Scriptorium pins the released Promptkit v0.9.0 module without a workspace,
+  replacement, vendored source, direct catalog import, or Promptkit internal
+  import.
+- Existing valid CLI, HTTP, configuration, prompt, profile, schema, and render
+  workflows remain supported subject to Promptkit's documented v0.2.0 through
+  v0.9.0 compatibility corrections.
+- Every Promptkit v0.9.0 prompt and profile feature expressible in definitions
+  under Scriptorium's configured directory sources is usable through the
+  executable application, including prompts with no inputs and explicitly
+  selected prompt versions.
+- CLI and HTTP requests can supply a direct non-secret session ID.
+- HTTP requests and a presence-aware CLI flag can inherit, replace, or
+  explicitly clear reasoning effort.
+- Prepared output, CLI run summaries, and HTTP result metadata expose effective
+  backend identity when Promptkit supplies one.
+- HTTP capacity rejection has a stable Scriptorium-owned overload response.
+- Application configuration can register reusable engine-scoped custom
+  backends, including bounded concurrency and queue policy, for selection by
+  Promptkit profiles.
+- CLI users can inspect prompt and profile definitions without supplying
+  placeholder inputs or invoking a model.
+- Scriptorium's contracts and examples point to Promptkit v0.9.0 and accurately
+  describe its current credential, validation-repair, provider-control,
+  message-role, backend, and source-validation semantics.
+
+## Feature Scope
+
+### Complete Prompt And Profile Definition Compatibility
+
+Scriptorium will treat the tagged Promptkit v0.9.0 format contract as one
+indivisible downstream compatibility boundary. This includes prompt identity
+and version selection, optional and required input declarations, message and
+content-file templates, supported roles, cache control, session templates,
+default profiles, output contracts, schemas, and repair budgets. It also
+includes standalone and inherited profiles, built-in and custom backend
+selection, endpoint overrides, execution controls, optional credential
+environment sources, and JSON-compatible extra parameters.
+
+Most of this support is provided by passing configured prompt, profile, and
+schema directories directly to Promptkit. Scriptorium will not independently
+decode these framework definitions or maintain a field-level subset. Two
+current adapter restrictions must be removed so the executable interfaces do
+not reject definitions that Promptkit accepts:
+
+- `run` and `render` will accept an optional prompt-version flag and map it to
+  `promptkit.RunRequest.PromptVersion`; and
+- `run`, `render`, and `POST /v1/runs` will permit omitted or empty input maps.
+  Promptkit will decide whether an input is required by the selected
+  definition or referenced template.
+
+The HTTP API already carries `prompt_version`; its mapping must remain covered
+by adapter tests. CLI and HTTP callers may continue to supply extra inputs,
+subject to their existing file, containment, and size policies. Removing the
+application-level nonempty-input requirement does not weaken Promptkit's
+declared-required-input or template-reference validation.
+
+Profiles that name built-in backend IDs require no application registration.
+Profiles that name other backend IDs become fully usable through the custom
+backend configuration in this roadmap. Profile inheritance and all other
+profile-field resolution remain Promptkit responsibilities.
+
+This compatibility requirement concerns fields and behavior expressed in
+Promptkit YAML definitions. Go-consumer construction alternatives such as
+single-file sources, injected `fs.FS` sources, in-memory profiles, fallback
+profile filesystems, and prepared-execution handles are library-integration
+features and are not required merely to support the complete definition
+format.
+
+### Promptkit v0.9.0 Compatibility Baseline
+
+Required dependency and source changes:
+
+- update `go.mod` and `go.sum` to select Promptkit v0.9.0 and its selected
+  OpenRouter and Rakestrawhome catalog dependencies;
+- change Scriptorium's inbound HTTP reasoning-effort representation to preserve
+  Promptkit's pointer semantics;
+- retain keyed Promptkit public struct literals and confirm no removed
+  `RunRequest.Metadata` use exists;
+- update tagged Promptkit links and version references throughout Scriptorium;
+  and
+- preserve Scriptorium's architecture guard against replacements, workspaces,
+  vendored Promptkit code, former facade packages, and Promptkit internal
+  imports.
+
+Required compatibility review:
+
+- verify application and maintained example endpoints satisfy Promptkit's
+  absolute HTTP/HTTPS endpoint rules;
+- verify prompt content paths, file artifacts, identities, JSON documents, and
+  JSON-compatible extra parameters satisfy the v0.6.0 safety boundaries;
+- verify maintained prompt roles are limited to `developer`, `system`, `user`,
+  and `assistant`;
+- verify every positive repair budget is no greater than three and is paired
+  with `basic`, `json`, or `json_schema` validation;
+- document that positive repair budgets authorize additional provider calls,
+  latency, token use, and cost;
+- document that unset optional provider controls are omitted and that a zero
+  effective value can represent an unspecified provider control unless an
+  explicit request override supplied it; and
+- update credential guidance for Promptkit's optional environment lookup
+  behavior, profile `api_key_env` semantics, and Scriptorium's prohibition on
+  raw API-key inputs.
+
+### Session And Reasoning Request Controls
+
+The CLI `run` and `render` commands will accept a direct session-ID flag and map
+it to `promptkit.RunRequest.SessionID`. The value remains non-secret
+application correlation metadata and is subject to Promptkit's normalization
+and length rules.
+
+The HTTP run request will accept `session_id` and map it through the existing
+strict DTO boundary. Successful HTTP metadata will report the effective
+session ID when present.
+
+The CLI `run` and `render` commands will also accept a presence-aware reasoning
+effort flag. Omission inherits the selected profile, a nonblank value replaces
+it, and an explicitly supplied empty value clears it. The existing HTTP
+`model.reasoning_effort` field will gain the same three-state behavior while
+remaining a JSON string when present.
+
+These additions must not introduce raw direct API-key flags or fields.
+
+### Backend Identity And Capacity Outcomes
+
+Scriptorium presentation will expose `SelectedBackendID` and the effective
+target's `BackendID` without deriving identity from endpoint text. Backend
+identity will be included where applicable in:
+
+- prepared-run text and JSON output;
+- the CLI run summary; and
+- HTTP response metadata and effective model parameters.
+
+Endpoint-only profiles continue to have no backend ID, and empty identities
+must remain distinguishable from registered built-in or custom backends.
+
+The HTTP adapter will classify `promptkit.ErrCapacityExceeded` separately from
+provider generation failures. The target public outcome is HTTP `503` with a
+stable `capacity_exceeded` code and a generic message. Scriptorium will not
+invent retry timing or expose an untrusted diagnostic. CLI capacity rejection
+continues to be a runtime failure, with a clear safe diagnostic and the
+existing runtime-error exit status.
+
+The HTTP server will use one appropriately scoped Promptkit engine across its
+requests so backend admission, active-generation limits, and queue capacity
+apply across concurrent in-flight work. The server may retain the operational
+state needed for those limits and for request cancellation and lifecycle
+management. This does not create durable per-request, conversation, or resume
+state.
+
+Scriptorium will continue to return generic public model-generation failures.
+Promptkit `GenerationError` provider code, type, and message values will not be
+added to the public HTTP response because they are untrusted and potentially
+sensitive.
+
+### Custom Backend Configuration
+
+The strict Scriptorium application configuration will gain an optional custom
+backend collection. Each entry will support the application-owned mapping
+needed to construct a public `promptkit.Backend`:
+
+- backend ID;
+- OpenAI-compatible endpoint;
+- optional API-key environment-variable name;
+- optional JSON-compatible request-wide extra parameters;
+- non-negative concurrency limit; and
+- queue capacity with presence preserved so omission and explicit zero remain
+  different.
+
+Raw API-key values will remain invalid. Unknown fields will remain errors.
+Configured backends will be registered through `promptkit.WithBackend` during
+engine construction and will be immutable and engine-scoped. Promptkit will
+remain the canonical validator for backend IDs, endpoints, reserved request
+parameters, capacity bounds, duplicate or reserved IDs, environment-variable
+names, and JSON-compatible values. Scriptorium will add context appropriate to
+its configuration error boundary without copying those framework rules.
+
+The collection will be configuration-file-owned. This roadmap does not add
+per-backend CLI flags. Existing endpoint-only profiles remain valid, while
+profiles may select configured custom backend IDs through Promptkit's existing
+`backend` field. Promptkit's built-in OpenRouter and Rakestrawhome backends and
+profiles remain available without Scriptorium registration.
+
+The application configuration shape is a `backends` mapping whose keys are the
+backend IDs registered with Promptkit:
+
+```yaml
+backends:
+  local-gpu:
+    endpoint: http://localhost:11434/v1
+    api_key_env: LOCAL_GPU_API_KEY
+    extra_params:
+      provider_option: enabled
+    concurrency_limit: 2
+    queue_capacity: 0
+```
+
+`endpoint` is required for each entry. The other fields are optional. Omitted
+`queue_capacity` uses Promptkit's default queue policy when concurrency is
+bounded, while an explicit zero disables queuing. The configuration contract
+and complete maintained configuration example will document this shape when
+the feature is implemented.
+
+### Prompt And Profile Inspection CLI
+
+Scriptorium will add a CLI inspection command with prompt and profile modes.
+The intended command family is:
+
+- `scriptorium inspect prompt`, backed by `Engine.InspectPrompt`; and
+- `scriptorium inspect profile`, backed by `Engine.InspectProfile`.
+
+Prompt inspection will select an ID and optional version and report the
+normalized prompt identity, opaque prompt hash, declared default profile,
+declared inputs, and normalized output contract. It will not require input
+artifacts, resolve a profile, load a schema, render templates, reserve backend
+capacity, or contact a model.
+
+Profile inspection will select an explicit profile ID and report its resolved
+effective target, backend identity, optional credential source name, and
+whether a later request must provide credential configuration. It will not
+read credential values, load a prompt, reserve capacity, or contact a model.
+
+Inspection will support deterministic Scriptorium-owned text and JSON output
+and normal output-file handling. Scriptorium will define explicit output DTOs
+rather than treating Promptkit inspection structs as stable wire formats.
+Inspection failures will use existing public Promptkit error identities and
+Scriptorium-owned CLI diagnostics and exit behavior.
+
+The prompt form accepts `--prompt`, optional `--prompt-version`, `--config`,
+`--prompt-dir`, `--format text|json`, and `--out`. The profile form accepts
+`--profile`, `--config`, `--profile-dir`, `--format text|json`, and `--out`.
+Both forms reject positional arguments and default to text output independently
+of `defaults.render_format`. Configuration discovery and CLI-over-file source
+precedence match the existing command family. Prompt inspection requires an
+effective prompt directory; profile inspection does not, because Promptkit's
+built-in profiles remain inspectable without one.
+
+## Documentation And Example Changes
+
+Implementation of this roadmap requires coordinated updates to the canonical
+owners of affected behavior:
+
+- `docs/cli.md` for session and reasoning flags, inspection commands, output,
+  prompt-version selection, optional inputs, and exit behavior;
+- `docs/api.md` for `session_id`, effective backend/session metadata, reasoning
+  presence semantics, optional inputs, and the capacity response;
+- `docs/config.md` for custom backend configuration and current Promptkit
+  credential and provider-default semantics;
+- `docs/operations.md` for capacity and custom-backend operational guidance
+  where deployment handling is affected;
+- `docs/internal/adapters.md` and `docs/internal/sources.md` for implemented
+  mapping and engine-assembly behavior;
+- `docs/policy/architecture.md` and `docs/internal/overview.md` only if concrete
+  component responsibilities or durable boundaries change; and
+- maintained examples for valid v0.9.0 prompt/profile formats and custom
+  backend configuration.
+
+Current-state documents must not describe these features as implemented until
+the corresponding code lands.
+
+## Validation And Completion Criteria
+
+The roadmap is complete only when:
+
+- ordinary and race-enabled tests pass against the tagged Promptkit v0.9.0
+  dependency;
+- `go vet ./...` and `go build ./cmd/scriptorium` pass;
+- Go formatting and `git diff --check` pass;
+- the architecture guard passes with no workspace, replacement, vendor tree,
+  former facade, or Promptkit internal import;
+- maintained render, custom-backend, session, reasoning, and inspection
+  examples execute successfully without real credentials or provider calls;
+- CLI tests cover explicit and omitted prompt versions for prompt IDs with one
+  or multiple definitions;
+- CLI and HTTP tests cover prompts with no declared inputs, omitted optional
+  inputs, missing required inputs, and template-referenced inputs;
+- HTTP tests cover omitted, replacement, and clearing reasoning states;
+- CLI and HTTP tests cover session propagation and invalid session handling;
+- presentation tests cover registered and endpoint-only backend identity;
+- HTTP tests cover capacity rejection independently from provider failure;
+- concurrent HTTP tests demonstrate that one server's requests share backend
+  admission and cannot bypass capacity through per-request engine creation;
+- configuration tests cover strict decoding, precedence, queue-capacity
+  presence, invalid backends, and secret-field rejection;
+- inspection tests cover deterministic text and JSON, source selection,
+  output-file handling, safe credential presentation, and public error
+  mapping;
+- all maintained prompt roles and repair budgets are valid under Promptkit
+  v0.9.0; and
+- representative definition fixtures cover inline and file-backed messages,
+  cache control, session templates, every output validation mode, schemas,
+  profile inheritance, built-in and custom backends, execution controls,
+  credential environment names, and extra parameters without Scriptorium
+  independently parsing those fields; and
+- affected documentation links and copyable examples validate successfully.
+
+## Explicit Non-Goals
+
+This roadmap does not include:
+
+- appended request messages in either executable interface;
+- retained or durable prepared-execution handles;
+- HTTP prompt or profile inspection routes;
+- embedded application fallback profiles;
+- single-file, injected `fs.FS`, or in-memory prompt and profile source
+  configuration;
+- request-level output-contract replacement through the executable interfaces;
+- public disclosure of structured provider error details;
+- direct imports or configuration of Promptkit's external catalog modules;
+- raw API-key configuration, CLI flags, or HTTP fields;
+- durable run state, conversations, retries, archives, checkpoints, or resume;
+  or
+- changes to Promptkit itself.

docs/roadmap/remediation.md

@@ -0,0 +1,77 @@
+# Promptkit Upgrade Review Remediation
+
+## Scope And Status
+
+Review baseline: `e177d7c`, covering implementation commits after `5c3b0cf`.
+This document records a resolved test-contract issue; it does not authorize
+unrelated implementation changes. No runtime defect or missing planned feature
+was identified in this review. Release preparation remains separate work.
+
+## R1: Remove The Unrequested Context-Identity Invariant
+
+Priority: P3 (low). Status: Complete.
+
+Original location: `internal/adapter/http/handler_test.go:334–349`,
+`TestHandlerRunTimeoutValidationAndContextMapping`, introduced in `7de2b02`.
+
+The test's `child` field and `(ctx != parent) != tc.child` assertion required
+the exact parent context object for omitted/null/zero timeouts and a distinct
+object for a positive timeout. The requested contract concerns effective
+deadlines and cancellation propagation, not Go interface identity. In
+particular, a harmless derived context that preserves the parent's deadline,
+values, and cancellation would fail the omission cases despite satisfying the
+application contract.
+
+This elevated an incidental implementation choice into a test-enforced
+invariant, contrary to the [agent policy](../policy/agents.md) and
+[testing policy](../policy/testing.md). The current handler's context behavior
+is correct; this is a maintainability issue, not a runtime cancellation bug.
+
+### Required Change
+
+Remove the identity comparison and the identity-only table field. Retain
+behavioral assertions that an earlier parent deadline is not extended and
+parent cancellation reaches execution. For omitted/null/zero values, verify
+that no deadline is introduced when the parent has none. Retain coverage of
+positive deadlines and the distinction between a canceled execution context
+and a provider-attempt timeout while the execution context remains live.
+
+Use the existing runner seam and focused cases; do not introduce a context
+wrapper framework, timer abstraction, new public guarantee, or production
+refactor solely to change this test.
+
+### Completion Criteria
+
+- Tests protect effective deadline/cancellation behavior without requiring
+  context object identity.
+- A semantically equivalent derived context does not fail merely because it
+  is a different object.
+- Existing timeout validation and HTTP outcome coverage remains intact.
+
+### Resolution And Validation
+
+Removed the identity-only table field and context comparisons. The test now
+checks effective deadlines, including omitted/null/zero requests with no
+parent deadline, and explicitly checks that parent cancellation reaches the
+runner. Existing positive-deadline integration tests and live-context
+provider-timeout mapping remain intact. No production code changed.
+
+Focused HTTP timeout tests, `go test ./...`, `go test -race ./...`,
+`go vet ./...`, a native build outside the repository, and `git diff --check`
+all passed after remediation.
+
+## Original Review Verification
+
+- `go test -race -count=1 ./...` passed, including retry, shared-capacity,
+  deadline, report, definition-conformance, and architecture-boundary tests.
+- `go vet ./...` passed.
+- A native `cmd/scriptorium` build passed, with output outside the repository.
+- The selected dependency is Promptkit v0.11.0 with its intended v2 catalogs.
+- Application code, tests, release automation, and historical releases were
+  not changed during this review.
+
+The runtime ownership boundaries remain as intended: Promptkit owns framework
+formats, execution, retries, and backend admission; Scriptorium owns executable
+adapters, application settings, HTTP artifact policy, deadlines, and terminal
+report presentation. No additional runtime restrictions, durable workflow
+state, or extra release compliance gates were identified in the reviewed diff.

docs/roadmap/upgrade-kit.md

@@ -0,0 +1,273 @@
+# Promptkit v0.11 Adoption
+
+## Status And Intent
+
+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)
+owns sequencing, concrete interface choices, verification steps, and unresolved
+implementation decisions.
+
+The target is complete definition compatibility, controllable transient
+retries, an optional whole-run deadline, and modest opt-in execution diagnostics.
+This is a focused adapter and configuration update, not another architecture
+migration. Optional diagnostics are included in the desired feature set.
+“Optional” means callers opt in, not that diagnostics may be silently omitted
+from the completed adoption or appear in default output.
+
+[ADR 0004](../adr/0004-definition-boundary.md) and the
+[architecture policy](../policy/architecture.md) govern scope. Promptkit remains
+the parser, validator, execution engine, and owner of framework defaults.
+Scriptorium remains a simple executable application for independent prompt
+executions, with shared operational state where required for backend limits.
+
+## Baseline And Upstream Changes
+
+Scriptorium currently selects Promptkit v0.9.0 and the v1.0.0 backend catalog
+modules. It already supports CLI execution, rendering, prompt/profile
+inspection, HTTP execution, configured backends, and presence-aware execution
+overrides. It does not expose transient retry settings, a whole-run deadline,
+or execution observers. CLI execution currently supplies a background context.
+
+The upstream review covered the local tagged release v0.11.0 at commit
+`db05b56166ca2d8650dfaf660e1cf0eed3932e1d`. Its canonical references are:
+
+- [v0.10.0 migration guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.10.0/docs/releases/v0.10.0.md);
+- [v0.11.0 release notes](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/releases/v0.11.0.md);
+- [definition formats](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md);
+- [execution and retry integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/integrations/openai-compatible-chat.md);
+- [consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md); and
+- [observation declarations](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/observations.go).
+
+A diagnostic run using a temporary module file compiled Scriptorium against
+v0.11.0. The existing test suite reported one failing profile-inspection case
+that selects the removed `deepseek-4-flash` profile; other packages passed.
+This establishes an initial migration issue, not proof of complete behavioral
+compatibility or coverage of the new capabilities. The diagnostic did not
+change the repository dependency pin.
+
+Neither intervening release adds declarative prompt/profile fields requiring
+new adapter plumbing. The definition-facing changes concern catalog contents
+and resolution precedence. Retry and observer APIs are execution controls;
+their adoption is a deliberate case-by-case choice under ADR 0004.
+
+## Dependency And Definition Compatibility
+
+### Target End State
+
+Scriptorium uses tagged Promptkit v0.11.0 through its supported root package,
+with the catalog versions selected by that release:
+
+- `promptkit-backend-openrouter/v2` v2.20260922.1;
+- `promptkit-backend-rakestrawhome/v2` v2.20260922.0.
+
+Valid definitions for the selected Promptkit version remain usable through
+Scriptorium's existing sources and adapters, subject to its established HTTP
+artifact and deployment boundaries. Rendering and inspection remain offline
+operations that do not generate model output.
+
+The maintained names `promptkit-openrouter-standard` and
+`promptkit-openrouter-auto` work wherever a profile ID is accepted, including
+prompt defaults, explicit selection, inheritance, and profile inspection.
+They are opt-in choices, not new Scriptorium defaults. Ordinary custom-source
+precedence remains intact.
+
+A stable maintained name is not a frozen model/settings selection. External
+catalog entries can change or disappear across upgrades; inheriting from one
+does not create a frozen copy. Complete application-owned profiles remain the
+appropriate choice when an application owns its model and settings.
+
+### Change From Baseline
+
+The module graph and active definition fixtures reflect the released v0.11
+catalogs rather than v0.9's catalogs. The selected catalog removes
+`deepseek-3-2`, `deepseek-4-flash`, and `deepseek-4-pro`; newer DeepSeek names
+are not compatibility aliases. Migration guidance offers an available catalog
+profile, a maintained Promptkit name, or a complete application-owned definition.
+Application-owned examples retain fixed settings where that is their purpose.
+
+Definition conformance and focused resolution coverage protect Scriptorium's
+adapter boundary without duplicating the upstream parser or catalog. Existing
+dependency boundaries also apply to the new `/v2` module paths.
+
+## Controllable Transient Retries
+
+### Target End State
+
+Expose `transient_retries` in application configuration, with a CLI execution
+override and an HTTP request override. Preserve value presence throughout:
+
+| Value | Meaning |
+| --- | --- |
+| Omitted | Inherit the engine setting, ultimately Promptkit's default. |
+| Zero | Disable additional transient attempts. |
+| Positive integer | Permit that many additional transient attempts. |
+| Negative integer | Invalid configuration or request. |
+
+Adopt Promptkit's default of two additional attempts rather than silently
+pinning the previous single-attempt behavior. Users must be able to select zero
+explicitly. Request overrides take precedence over application configuration;
+omission must not accidentally become an explicit zero.
+
+Promptkit alone owns eligible statuses, attempt execution, backoff,
+`Retry-After`, and capacity coordination. Scriptorium adds no outer model retry
+loop. Transient retries and structural repairs have distinct budgets: each
+generation, including each repair generation, receives its transient budget.
+Retries do not imply exactly-once generation or complete billing knowledge.
+
+### Change From Baseline
+
+Application settings reach `promptkit.Config.TransientRetries`, including the
+shared server engine, and request overrides reach
+`promptkit.RunRequest.TransientRetries`. This adds execution controls, not
+prompt/profile schema fields or provider model parameters. Strict decoding and
+presence-aware mapping preserve inheritance and explicit zero. User and
+operations guidance makes the changed default, latency/cost implications, and
+independent repair budget visible. Cancellation and shared backend limits
+remain effective during retrying executions.
+
+## Optional Whole-Run Deadline
+
+### Target End State
+
+Callers can opt into a total execution deadline independently of the existing
+generation timeout. No new default deadline is imposed. Existing timeout
+controls must not silently change meaning: in v0.11.0 they apply per generation
+attempt, whereas a whole-run deadline bounds the overall operation, including
+preparation, capacity waiting, retry delays, attempts, and repairs as supported
+by the upstream context contract.
+
+Expose this choice through CLI execution and HTTP execution. Derive any timeout
+context from the caller's existing context, so a caller cancellation or earlier
+deadline still wins. This is a cancellation boundary, not a guarantee of
+instantaneous interruption of arbitrary callback or filesystem code.
+
+### Change From Baseline
+
+CLI execution can carry a selected deadline instead of always using an
+unbounded background context. HTTP execution can shorten the incoming context
+without losing parent cancellation or changing server lifecycle behavior.
+Total-run duration handling is separate from existing attempt-timeout conversion.
+The interval covers the engine invocation, not adapter parsing, engine creation,
+or output writing. Provider retry timing can exceed local backoff limits;
+per-attempt timeouts do not cap that complete invocation.
+
+## Opt-In Execution Reports
+
+### Target End State
+
+Provide a modest terminal execution report for CLI and HTTP callers who opt
+in. Capture selected metadata through `RunRequest.Observer`, including attempt,
+retry, repair, timing, outcome, and presence-aware usage information. Reports
+should be available for completed successful and failed execution invocations
+when Promptkit supplies terminal observations. Do not invent execution data for
+failures that occur before invocation.
+
+Keep generated CLI content on stdout or the existing output path. Execution
+reports use a separate destination. Ordinary CLI output and HTTP response
+shapes remain unchanged when reporting is not requested.
+
+The report has a Scriptorium-owned schema rather than serializing upstream
+events directly: `ExecutionEvent` has no stable JSON contract. Preserve unknown
+usage versus reported zero, and incomplete versus complete observed totals.
+Existing successful-result usage semantics remain unchanged. A terminal total
+is an aggregate, not another attempt to add to the bill; no report is a billing
+ledger.
+
+### Change From Baseline
+
+Both adapters have opt-in reporting and explicit application-owned report DTOs.
+Per-request collection adds no shared mutable report state, durable storage,
+callback I/O, or event archive. Operational failures can carry reports without
+manufacturing partial `RunResult` values. Default output remains unchanged.
+
+Reports exclude prompt and response bodies, credentials, headers, endpoint URLs,
+provider diagnostic text, and raw errors. Selected identifiers remain potentially
+sensitive even when observations are content-free. Reports are concise terminal
+metadata, not a general telemetry framework, event stream, or durable history.
+
+## Errors And Compatibility
+
+Preserve existing CLI exit classifications and HTTP `502 / llm_failed`
+classification for generation failures. Keep safe public messages rather than
+exposing provider error bodies or parsing diagnostic strings.
+
+Promptkit adds `ErrTransport`, `ErrMalformedResponse`, `ErrRetriesExhausted`, and
+`RetryExhaustedError`. Use their public identities to support optional structured
+failure details in execution diagnostics, including actual attempts where
+available. Retry exhaustion and the final cause are distinct facts; do not lose
+the underlying failure category by flattening them into one label.
+
+Capacity and validation behavior remains intact. Whole-run deadline and caller
+cancellation outcomes are deliberate adapter classifications, distinct from a
+provider-attempt timeout while the caller context is still live. The implementation
+plan owns the exact presentation choices. Existing generation-error codes do
+not need a breaking replacement for this upgrade.
+
+## Licensing And Distribution Review
+
+Promptkit v0.11.0 changes from GPLv3 to LGPL-3.0-or-later. Scriptorium's current
+binary workflow produces statically linked Go executables, and upstream's
+[license summary](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/README.md#license)
+explicitly calls out distribution considerations for that model. Catalog and
+other dependency licenses remain separate.
+
+Before distributing the upgraded binaries, resolve the applicable notices,
+license texts, source availability, and any required materials or permissions
+for recombination with a modified library. Record the chosen distribution
+approach and make any corresponding packaging/documentation changes. This
+roadmap is not a legal determination or a complete compliance checklist.
+
+Do not automatically relicense Scriptorium, assume that library source alone
+settles every distribution requirement, or alter historical release contents.
+Licensing review is a concrete adoption prerequisite, not a new blanket manual
+approval gate for every future release.
+
+## Documentation And Delivery
+
+Current documentation links to the selected v0.11.0 contracts once implemented.
+CLI, HTTP, configuration, and operations documents own their respective new
+behavior; internal docs explain adapter mapping; release notes summarize
+compatibility impact. Historical release notes and ADR decision content remain
+unchanged. Current examples and migration guidance reflect the selected version.
+
+The upgrade merits a minor Scriptorium release, not a compatibility patch,
+with prominent migration guidance for removed profiles, changed retry behavior,
+the explicit single-attempt option, and timeout layering. Any later decision to
+defer part of the target leaves that feature visibly incomplete until delivered.
+
+Use the existing [release policy](../policy/release.md) and
+[runbook](../release.md). This roadmap authorizes no publication. No new ADR is
+needed unless a later decision changes the established product or compatibility
+boundaries.
+
+## Completion Criteria
+
+- The tagged dependency and selected catalog modules are adopted without
+  unsupported imports or local dependency substitutions.
+- Existing definition conformance tests and focused maintained-profile tests
+  pass; removed profile IDs have explicit migration guidance, not silent aliases.
+- Retry settings preserve omission and zero across configuration, CLI, and HTTP;
+  Promptkit remains the sole retry/capacity implementation.
+- Optional total deadlines bound the caller operation without redefining
+  per-attempt timeouts or disabling parent cancellation.
+- Opt-in terminal reports provide safe, isolated, presence-aware execution
+  metadata without changing default output or creating durable workflow state.
+  Any deferred reporting work remains visibly incomplete.
+- Existing error classifications remain compatible, with deliberate handling
+  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 current contracts, examples, and migration guidance match
+  implemented behavior. Relevant tests remain offline and credential-free,
+  and normal development validation passes. Release-candidate validation and
+  the version-matched note remain release preparation.
+
+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.

examples/config-fragments/backend.yml

@@ -0,0 +1,4 @@
+backends:
+  local-gpu:
+    endpoint: http://localhost:11434/v1
+    api_key_env: LOCAL_GPU_API_KEY

examples/config-fragments/sources.yml

@@ -0,0 +1,3 @@
+prompt_dir: ./examples/prompts
+profile_dir: ./examples/profiles
+schema_dir: ./examples/schemas

examples/config.composed.yml

@@ -0,0 +1,8 @@
+# Select from the repository root; application paths remain working-directory-relative.
+configkit:
+  imports:
+    - path: config-fragments/sources.yml
+    - path: config-fragments/backend.yml
+
+server:
+  addr: :8080

examples/config.full.yml

@@ -0,0 +1,22 @@
+prompt_dir: ./examples/prompts
+profile_dir: ./examples/profiles
+schema_dir: ./examples/schemas
+
+backends:
+  local-gpu:
+    endpoint: http://localhost:11434/v1
+    api_key_env: LOCAL_GPU_API_KEY
+    extra_params:
+      provider_option: enabled
+    concurrency_limit: 2
+    queue_capacity: 0
+
+server:
+  addr: 127.0.0.1:8080
+  artifact_root: .
+  max_request_bytes: 16777216
+  max_artifact_bytes: 16777216
+  max_response_bytes: 16777216
+
+defaults:
+  render_format: text

examples/config.yml

@@ -1,9 +1,10 @@
-prompt_dir: ./prompts
-profile_dir: ./profiles
-schema_dir: ./schemas
+prompt_dir: ./examples/prompts
+profile_dir: ./examples/profiles
+schema_dir: ./examples/schemas
 
 server:
   addr: :8080
+  artifact_root: .
 
 defaults:
   render_format: text

examples/http-run.json

@@ -0,0 +1,18 @@
+{
+  "prompt_id": "generic.markdown_summary",
+  "profile_id": "local-fast",
+  "inputs": {
+    "transcript": {
+      "type": "file",
+      "uri": "./examples/fixtures/transcript.md"
+    },
+    "glossary": {
+      "type": "file",
+      "uri": "./examples/fixtures/glossary.yml"
+    }
+  },
+  "vars": {
+    "session_date": "2026-05-04"
+  },
+  "include_raw_output": false
+}

examples/overlays/local.yml

@@ -0,0 +1,4 @@
+defaults:
+  render_format: json
+server:
+  addr: 127.0.0.1:8080

examples/profiles/local-gpu.yml

@@ -0,0 +1,4 @@
+id: local-gpu
+backend: local-gpu
+model: local-model
+reasoning_effort: low

examples/render-markdown-summary.sh

@@ -0,0 +1,13 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+repo_root="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+
+cd "$repo_root"
+
+go run ./cmd/scriptorium render \
+  --config ./examples/config.yml \
+  --prompt generic.markdown_summary \
+  --input transcript=./examples/fixtures/transcript.md \
+  --input glossary=./examples/fixtures/glossary.yml \
+  --format text

examples/render-v0.9-features.sh

@@ -0,0 +1,25 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+repo_root="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+cd "$repo_root"
+
+go run ./cmd/scriptorium render \
+  --config ./examples/config.full.yml \
+  --prompt generic.markdown_summary \
+  --prompt-version 1.0.0 \
+  --profile local-gpu \
+  --session-id example-session \
+  --reasoning-effort= \
+  --input transcript=./examples/fixtures/transcript.md \
+  --input glossary=./examples/fixtures/glossary.yml
+
+go run ./cmd/scriptorium inspect prompt \
+  --config ./examples/config.full.yml \
+  --prompt generic.markdown_summary \
+  --format json
+
+go run ./cmd/scriptorium inspect profile \
+  --config ./examples/config.full.yml \
+  --profile local-gpu \
+  --format json

go.mod

@@ -3,8 +3,15 @@ module gitea.maximumdirect.net/eric/scriptorium
 go 1.25.5
 
 require (
-	github.com/santhosh-tekuri/jsonschema/v6 v6.0.2
-	gopkg.in/yaml.v3 v3.0.1
+	gitea.maximumdirect.net/eric/ConfigKit v0.4.0
+	gitea.maximumdirect.net/eric/promptkit v0.11.0
 )
 
-require golang.org/x/text v0.14.0 // indirect
+require (
+	gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1 // indirect
+	gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0 // indirect
+	github.com/santhosh-tekuri/jsonschema/v6 v6.0.2 // indirect
+	go.yaml.in/yaml/v4 v4.0.0-rc.6 // indirect
+	golang.org/x/text v0.14.0 // indirect
+	gopkg.in/yaml.v3 v3.0.1 // indirect
+)

go.sum

@@ -1,7 +1,17 @@
+gitea.maximumdirect.net/eric/ConfigKit v0.4.0 h1:fo+vKff3zTGeWqJIA38NtT84b6OUP//9ZmBH3lFuKgk=
+gitea.maximumdirect.net/eric/ConfigKit v0.4.0/go.mod h1:tYWpsrbLyu05r8+1MapWp5fN6ZrX9I8hU2xEPedYmYk=
+gitea.maximumdirect.net/eric/promptkit v0.11.0 h1:x7JguOUiInPVXK0GEitjyoRFqqvcuSTjYUvqJ+whtik=
+gitea.maximumdirect.net/eric/promptkit v0.11.0/go.mod h1:0zEBVlJJC+ldDdXazAgybYBXNSe74vwFx5dyOuSos/w=
+gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1 h1:S2/Q/JDE+m8Ca3pDhAjVbfYrdlEhs9blj0STgNopHo0=
+gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1/go.mod h1:a3VBbh9oaGXD6ruxhtwHj+AWW6DY/SSyby1QtMmYSUo=
+gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0 h1:Y0EXc3eh12eKW2NrOviVqdk3oBo6UUjopt1YAa1B3Oc=
+gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0/go.mod h1:mtgD1E0SGm0e/I8Ffhz+AYX7GN7RKUWJXehNFIKHs4Y=
 github.com/dlclark/regexp2 v1.11.0 h1:G/nrcoOa7ZXlpoa/91N3X7mM3r8eIlMBBJZvsz/mxKI=
 github.com/dlclark/regexp2 v1.11.0/go.mod h1:DHkYz0B9wPfa6wondMfaivmHpzrQ3v9q8cnmRbL6yW8=
 github.com/santhosh-tekuri/jsonschema/v6 v6.0.2 h1:KRzFb2m7YtdldCEkzs6KqmJw4nqEVZGK7IN2kJkjTuQ=
 github.com/santhosh-tekuri/jsonschema/v6 v6.0.2/go.mod h1:JXeL+ps8p7/KNMjDQk3TCwPpBy0wYklyWTfbkIzdIFU=
+go.yaml.in/yaml/v4 v4.0.0-rc.6 h1:1h7H1ohdUh93/FyE4YaDa1Zh64K6VVbjF4K6WUxMtH4=
+go.yaml.in/yaml/v4 v4.0.0-rc.6/go.mod h1:aZqd9kCMsGL7AuUv/m/PvWLdg5sjJsZ4oHDEnfPPfY0=
 golang.org/x/text v0.14.0 h1:ScX5w1eTa3QqT8oi6+ziP7dTV1S2+ALU0bI+0zXKWiQ=
 golang.org/x/text v0.14.0/go.mod h1:18ZOQIKpY8NJVqYksKHtTdi31H5itFRjB5/qKTNYzSU=
 gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405 h1:yhCVgyC4o1eVCa2tZl7eS0r+SDo693bJlVdllGtEeKM=

internal/adapter/cli/application_config.go

@@ -0,0 +1,71 @@
+package cli
+
+import (
+	"errors"
+	"flag"
+	"fmt"
+	"io"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	appconfig "gitea.maximumdirect.net/eric/scriptorium/internal/config"
+)
+
+// applicationOverrides keeps explicit application flags separate from invocation state.
+func applicationOverrides(fs *flag.FlagSet) []configkit.Override {
+	var overrides []configkit.Override
+	fs.Visit(func(selected *flag.Flag) {
+		var path configkit.Path
+		switch selected.Name {
+		case "prompt-dir":
+			path = configkit.Keys("prompt_dir")
+		case "profile-dir":
+			path = configkit.Keys("profile_dir")
+		case "schema-dir":
+			path = configkit.Keys("schema_dir")
+		case "addr":
+			path = configkit.Keys("server", "addr")
+		case "artifact-root":
+			path = configkit.Keys("server", "artifact_root")
+		case "max-request-bytes":
+			path = configkit.Keys("server", "max_request_bytes")
+		case "max-artifact-bytes":
+			path = configkit.Keys("server", "max_artifact_bytes")
+		case "max-response-bytes":
+			path = configkit.Keys("server", "max_response_bytes")
+		default:
+			return
+		}
+		overrides = append(overrides, configkit.Override{
+			Path: path, Value: selected.Value.(flag.Getter).Get(), Flag: "--" + selected.Name,
+		})
+	})
+	return overrides
+}
+
+func loadApplicationSettings(configPath, overlay string, explicit bool, overrides []configkit.Override) (appconfig.AppSettings, []configkit.Diagnostic, error) {
+	result, err := appconfig.Load(appconfig.LoadOptions{
+		Path: configPath, Overlay: overlay, Explicit: explicit, Overrides: overrides,
+	})
+	if err != nil {
+		return appconfig.AppSettings{}, nil, err
+	}
+	return appconfig.Settings(result.Config), result.Diagnostics(), nil
+}
+
+func writeApplicationError(output io.Writer, label string, err error) {
+	var loadError *configkit.LoadError
+	if errors.As(err, &loadError) {
+		if writeErr := configkit.WriteDiagnostics(output, loadError.Diagnostics()); writeErr != nil {
+			_, _ = fmt.Fprintf(output, "%s diagnostic write error: %v\n", label, writeErr)
+		}
+		return
+	}
+	_, _ = fmt.Fprintf(output, "%s error: %v\n", label, err)
+}
+
+func writeApplicationWarnings(output io.Writer, diagnostics []configkit.Diagnostic) error {
+	if len(diagnostics) == 0 {
+		return nil
+	}
+	return configkit.WriteDiagnostics(output, diagnostics)
+}

internal/adapter/cli/config.go

@@ -0,0 +1,104 @@
+package cli
+
+import (
+	"encoding/json"
+	"flag"
+	"fmt"
+	"io"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	appconfig "gitea.maximumdirect.net/eric/scriptorium/internal/config"
+)
+
+type configurationSource struct {
+	ID    string          `json:"id"`
+	Label string          `json:"label"`
+	Layer configkit.Layer `json:"layer"`
+	Path  string          `json:"path,omitempty"`
+}
+
+func configCommand(args []string, stdout, stderr io.Writer) int {
+	if len(args) == 0 {
+		fmt.Fprintln(stderr, "config parse error: configuration mode is required")
+		return ExitRuntimeError
+	}
+	mode := args[0]
+	if mode != "validate" && mode != "show" && mode != "sources" && mode != "explain" {
+		fmt.Fprintln(stderr, "config parse error: unknown configuration mode")
+		return ExitRuntimeError
+	}
+
+	fs := flag.NewFlagSet("config "+mode, flag.ContinueOnError)
+	fs.SetOutput(io.Discard)
+	var path, overlay, pointer string
+	registerConfigSelectionFlags(fs, &path, &overlay)
+	registerConfigurationOverrides(fs)
+	if mode == "explain" {
+		fs.StringVar(&pointer, "path", "", "configuration path as a JSON Pointer")
+	}
+	if err := fs.Parse(args[1:]); err != nil {
+		writeApplicationError(stderr, "config parse", err)
+		return ExitRuntimeError
+	}
+	if fs.NArg() != 0 {
+		fmt.Fprintln(stderr, "config parse error: positional arguments are not accepted")
+		return ExitRuntimeError
+	}
+	var explanationPath configkit.Path
+	if mode == "explain" {
+		if !flagWasSet(fs, "path") {
+			fmt.Fprintln(stderr, "config parse error: --path is required")
+			return ExitRuntimeError
+		}
+		var err error
+		explanationPath, err = configkit.ParsePath(pointer)
+		if err != nil {
+			fmt.Fprintln(stderr, "config parse error: --path must be a JSON Pointer")
+			return ExitRuntimeError
+		}
+	}
+
+	result, err := appconfig.Load(appconfig.LoadOptions{
+		Path: path, Explicit: flagWasSet(fs, "config"), Overlay: overlay,
+		Overrides: applicationOverrides(fs),
+	})
+	if err != nil {
+		writeApplicationError(stderr, "config", err)
+		return ExitRuntimeError
+	}
+	if err := writeApplicationWarnings(stderr, result.Diagnostics()); err != nil {
+		return ExitRuntimeError
+	}
+	switch mode {
+	case "validate":
+		return ExitOK
+	case "show":
+		err = result.WriteEffective(stdout)
+	case "sources":
+		sources := make([]configurationSource, 0, len(result.Sources()))
+		for _, source := range result.Sources() {
+			sources = append(sources, configurationSource{
+				ID: source.ID, Label: source.Label, Layer: source.Layer, Path: source.Path,
+			})
+		}
+		err = json.NewEncoder(stdout).Encode(sources)
+	case "explain":
+		err = result.WriteExplanation(stdout, explanationPath)
+	}
+	if err != nil {
+		fmt.Fprintf(stderr, "config output error: %v\n", err)
+		return ExitRuntimeError
+	}
+	return ExitOK
+}
+
+func registerConfigurationOverrides(fs *flag.FlagSet) {
+	fs.String("prompt-dir", "", "prompt-definition directory override")
+	fs.String("profile-dir", "", "profile directory override")
+	fs.String("schema-dir", "", "schema directory override")
+	fs.String("addr", "", "HTTP listen address override")
+	fs.String("artifact-root", "", "HTTP artifact root override")
+	fs.Int64("max-request-bytes", 0, "HTTP request byte limit override")
+	fs.Int64("max-artifact-bytes", 0, "HTTP artifact byte limit override")
+	fs.Int64("max-response-bytes", 0, "HTTP response byte limit override")
+}

internal/adapter/cli/config_test.go

@@ -0,0 +1,207 @@
+package cli
+
+import (
+	"bytes"
+	"encoding/json"
+	"errors"
+	"io"
+	"os"
+	"path/filepath"
+	"strings"
+	"testing"
+
+	appconfig "gitea.maximumdirect.net/eric/scriptorium/internal/config"
+)
+
+func TestConfigCommandsInspectApplicationWithoutEngine(t *testing.T) {
+	path := writeAppConfigFile(t, "{}\n")
+	for _, mode := range []string{"validate", "show", "sources"} {
+		code, stdout, stderr := runCLICommand(t, configCommand, []string{mode, "--config", path})
+		if code != ExitOK || stderr != "" {
+			t.Fatalf("%s failed: code=%d stdout=%q stderr=%q", mode, code, stdout, stderr)
+		}
+		switch mode {
+		case "validate":
+			if stdout != "" {
+				t.Fatalf("validation wrote stdout: %q", stdout)
+			}
+		case "show":
+			if !strings.Contains(stdout, "render_format: text") || !strings.Contains(stdout, "max_request_bytes: 16777216") {
+				t.Fatalf("effective defaults missing: %q", stdout)
+			}
+		case "sources":
+			var sources []configurationSource
+			if err := json.Unmarshal([]byte(stdout), &sources); err != nil || len(sources) != 1 || sources[0].Layer != "base" {
+				t.Fatalf("unexpected source records: %q (%v)", stdout, err)
+			}
+		}
+	}
+}
+
+func TestConfigCommandsExposeComposedSourcesAndResolvedValues(t *testing.T) {
+	dir := t.TempDir()
+	if err := os.MkdirAll(filepath.Join(dir, "overlays"), 0o755); err != nil {
+		t.Fatal(err)
+	}
+	base := filepath.Join(dir, "config.yml")
+	for path, body := range map[string]string{
+		base:                               "configkit:\n  imports:\n    - path: fragment.yml\nprompt_dir: ' ./before/../prompts '\nprofile_dir: ./profiles\n",
+		filepath.Join(dir, "fragment.yml"): "server:\n  addr: :8081\n",
+		filepath.Join(dir, "overlays", "local.yml"): "server:\n  addr: :9090\n",
+	} {
+		if err := os.WriteFile(path, []byte(body), 0o600); err != nil {
+			t.Fatal(err)
+		}
+	}
+	args := []string{"--config", base, "--config-overlay", "local", "--profile-dir=", "--addr", ":7070"}
+	code, stdout, stderr := runCLICommand(t, configCommand, append([]string{"show"}, args...))
+	if code != ExitOK || stderr != "" || !strings.Contains(stdout, "prompt_dir: prompts") || !strings.Contains(stdout, "profile_dir: ''") || !strings.Contains(stdout, "addr: :7070") {
+		t.Fatalf("resolved effective output changed: code=%d out=%q err=%q", code, stdout, stderr)
+	}
+	code, stdout, stderr = runCLICommand(t, configCommand, append([]string{"sources"}, args...))
+	if code != ExitOK || stderr != "" || !strings.HasSuffix(stdout, "\n") {
+		t.Fatalf("source command failed: code=%d out=%q err=%q", code, stdout, stderr)
+	}
+	var sources []configurationSource
+	if err := json.Unmarshal([]byte(stdout), &sources); err != nil || len(sources) != 5 {
+		t.Fatalf("unexpected composed source records: %+v (%v)", sources, err)
+	}
+	for i, layer := range []string{"base", "base", "overlay", "cli", "cli"} {
+		if string(sources[i].Layer) != layer {
+			t.Fatalf("source %d layer = %q, want %q", i, sources[i].Layer, layer)
+		}
+	}
+}
+
+func TestConfigInspectionKeepsReferencesAndOrdinaryParameters(t *testing.T) {
+	const name = "SCRIPTORIUM_CONFIG_TEST_API_KEY"
+	const secret = "synthetic-secret-value-should-not-appear"
+	path := writeAppConfigFile(t, `backends:
+  synthetic:
+    endpoint: http://127.0.0.1:1/v1
+    api_key_env: SCRIPTORIUM_CONFIG_TEST_API_KEY
+    extra_params:
+      visible_parameter: synthetic-ordinary-value
+`)
+	t.Setenv(name, secret)
+	for _, present := range []bool{true, false} {
+		if !present {
+			if err := os.Unsetenv(name); err != nil {
+				t.Fatal(err)
+			}
+		}
+		code, stdout, stderr := runCLICommand(t, configCommand, []string{"show", "--config", path})
+		if code != ExitOK || stderr != "" || !strings.Contains(stdout, name) || !strings.Contains(stdout, "synthetic-ordinary-value") || strings.Contains(stdout, secret) {
+			t.Fatalf("credential boundary changed with present=%t: code=%d out=%q err=%q", present, code, stdout, stderr)
+		}
+	}
+	result, err := appconfig.Load(appconfig.LoadOptions{Path: path, Explicit: true})
+	if err != nil {
+		t.Fatal(err)
+	}
+	settings := appconfig.Settings(result.Config)
+	if len(settings.Backends) != 1 || settings.Backends[0].ExtraParams["visible_parameter"] != "synthetic-ordinary-value" {
+		t.Fatalf("runtime backend parameters changed: %+v", settings.Backends)
+	}
+}
+
+type errorOutputWriter struct{}
+
+func (errorOutputWriter) Write([]byte) (int, error) { return 0, errors.New("output unavailable") }
+
+func TestConfigCommandFailuresDoNotProduceSuccessfulOutput(t *testing.T) {
+	path := writeAppConfigFile(t, "server:\n  max_request_bytes: -1\n")
+	for _, mode := range []string{"validate", "show", "sources"} {
+		code, stdout, stderr := runCLICommand(t, configCommand, []string{mode, "--config", path})
+		if code != ExitRuntimeError || stdout != "" || !strings.Contains(stderr, "validate.error") {
+			t.Fatalf("%s misclassified invalid config: code=%d out=%q err=%q", mode, code, stdout, stderr)
+		}
+	}
+	path = writeAppConfigFile(t, "{}\n")
+	var stderr bytes.Buffer
+	if code := configCommand([]string{"show", "--config", path}, errorOutputWriter{}, &stderr); code != ExitRuntimeError || !strings.Contains(stderr.String(), "output error") {
+		t.Fatalf("writer error not reported: code=%d stderr=%q", code, stderr.String())
+	}
+	if code := configCommand([]string{"sources", "--config", path}, errorOutputWriter{}, io.Discard); code != ExitRuntimeError {
+		t.Fatalf("source writer error returned %d", code)
+	}
+}
+
+func TestConfigExplainUsesResolvedHistoryAndKeepsParametersVisible(t *testing.T) {
+	dir := t.TempDir()
+	if err := os.MkdirAll(filepath.Join(dir, "overlays"), 0o755); err != nil {
+		t.Fatal(err)
+	}
+	base := filepath.Join(dir, "config.yml")
+	for path, body := range map[string]string{
+		base: `prompt_dir: " ./prompts/../prompts "
+server:
+  addr: :8080
+backends:
+  "team/blue~1":
+    endpoint: http://127.0.0.1:1/v1
+    api_key_env: SCRIPTORIUM_EXPLAIN_KEY
+    extra_params:
+      "0": base-parameter
+`,
+		filepath.Join(dir, "overlays", "local.yml"): `server:
+  addr: :9090
+backends:
+  "team/blue~1":
+    extra_params:
+      "0": overlay-parameter
+`,
+	} {
+		if err := os.WriteFile(path, []byte(body), 0o600); err != nil {
+			t.Fatal(err)
+		}
+	}
+	const keyValue = "synthetic-key-bytes-must-not-appear"
+	t.Setenv("SCRIPTORIUM_EXPLAIN_KEY", keyValue)
+	args := []string{"--config", base, "--config-overlay", "local", "--addr", ":9090"}
+	for _, tc := range []struct {
+		pointer string
+		want    []string
+	}{
+		{pointer: "/server/addr", want: []string{":8080", ":9090", "--addr"}},
+		{pointer: "/prompt_dir", want: []string{"normalized application path", "prompts"}},
+		{pointer: "/backends/team~1blue~01/extra_params/0", want: []string{"base-parameter", "overlay-parameter"}},
+		{pointer: "/backends/team~1blue~01/api_key_env", want: []string{"SCRIPTORIUM_EXPLAIN_KEY"}},
+		{pointer: "", want: []string{"base-parameter", "overlay-parameter", "SCRIPTORIUM_EXPLAIN_KEY"}},
+	} {
+		code, stdout, stderr := runCLICommand(t, configCommand, append([]string{"explain", "--path", tc.pointer}, args...))
+		if code != ExitOK || stderr != "" || strings.Contains(stdout, keyValue) {
+			t.Fatalf("explain %q failed or disclosed key: code=%d out=%q err=%q", tc.pointer, code, stdout, stderr)
+		}
+		for _, want := range tc.want {
+			if !strings.Contains(stdout, want) {
+				t.Fatalf("explain %q lacks %q: %q", tc.pointer, want, stdout)
+			}
+		}
+	}
+	if err := os.Unsetenv("SCRIPTORIUM_EXPLAIN_KEY"); err != nil {
+		t.Fatal(err)
+	}
+	code, stdout, stderr := runCLICommand(t, configCommand, append([]string{"explain", "--path", "/backends/team~1blue~01/api_key_env"}, args...))
+	if code != ExitOK || stderr != "" || !strings.Contains(stdout, "SCRIPTORIUM_EXPLAIN_KEY") || strings.Contains(stdout, keyValue) {
+		t.Fatalf("absent credential changed reference explanation: code=%d out=%q err=%q", code, stdout, stderr)
+	}
+}
+
+func TestConfigExplainRejectsUnknownOrMalformedPaths(t *testing.T) {
+	path := writeAppConfigFile(t, "{}\n")
+	for _, args := range [][]string{
+		{"explain", "--config", path},
+		{"explain", "--config", path, "--path", "not-a-pointer"},
+		{"explain", "--config", path, "--path", "/missing"},
+	} {
+		code, stdout, stderr := runCLICommand(t, configCommand, args)
+		if code != ExitRuntimeError || stdout != "" || stderr == "" {
+			t.Fatalf("invalid explanation path accepted: args=%q code=%d out=%q err=%q", args, code, stdout, stderr)
+		}
+	}
+	var stderr bytes.Buffer
+	if code := configCommand([]string{"explain", "--config", path, "--path", ""}, errorOutputWriter{}, &stderr); code != ExitRuntimeError || !strings.Contains(stderr.String(), "output error") {
+		t.Fatalf("explanation writer failure not reported: code=%d err=%q", code, stderr.String())
+	}
+}

internal/adapter/cli/inspect.go

@@ -0,0 +1,212 @@
+package cli
+
+import (
+	"context"
+	"errors"
+	"flag"
+	"fmt"
+	"io"
+	"io/fs"
+	"path/filepath"
+	"strings"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/promptkit"
+	appformat "gitea.maximumdirect.net/eric/scriptorium/internal/format"
+)
+
+type promptInspectionConfig struct {
+	configPath, promptDir, promptID, promptVersion, outputPath string
+	configOverlay                                              string
+	configExplicit                                             bool
+	outputFormat                                               appformat.OutputFormat
+	overrides                                                  []configkit.Override
+	diagnostics                                                []configkit.Diagnostic
+}
+
+type profileInspectionConfig struct {
+	configPath, profileDir, profileID, outputPath string
+	configOverlay                                 string
+	configExplicit                                bool
+	outputFormat                                  appformat.OutputFormat
+	overrides                                     []configkit.Override
+	diagnostics                                   []configkit.Diagnostic
+}
+
+// emptyPromptDefinitionFS satisfies Promptkit's engine-level prompt-source
+// requirement without exposing the caller's working directory. Profile
+// inspection never reads this source.
+type emptyPromptDefinitionFS struct{}
+
+func (emptyPromptDefinitionFS) Open(name string) (fs.File, error) {
+	return nil, &fs.PathError{Op: "open", Path: name, Err: fs.ErrNotExist}
+}
+
+func inspectCommand(args []string, stdout, stderr io.Writer) int {
+	if len(args) == 0 {
+		fmt.Fprintln(stderr, "inspect parse error: inspection mode is required")
+		return ExitRuntimeError
+	}
+	if args[0] == "profile" {
+		return inspectProfileCommand(args[1:], stdout, stderr)
+	}
+	if args[0] != "prompt" {
+		fmt.Fprintln(stderr, "inspect parse error: unknown inspection mode")
+		return ExitRuntimeError
+	}
+	cfg, err := parsePromptInspectionArgs(args[1:])
+	if err != nil {
+		writeApplicationError(stderr, "inspect parse", err)
+		return ExitRuntimeError
+	}
+	settings, err := resolveAppSettingsForPromptInspection(cfg)
+	if err != nil {
+		writeApplicationError(stderr, "inspect", err)
+		return ExitRuntimeError
+	}
+	if err := writeApplicationWarnings(stderr, cfg.diagnostics); err != nil {
+		return ExitRuntimeError
+	}
+	engine, err := newEngine(settings)
+	if err != nil {
+		fmt.Fprintf(stderr, "engine error: %v\n", err)
+		return ExitRuntimeError
+	}
+	inspection, err := engine.InspectPrompt(context.Background(), cfg.promptID, cfg.promptVersion)
+	if err != nil {
+		fmt.Fprintf(stderr, "inspect error: %v\n", err)
+		return ExitRuntimeError
+	}
+	data, err := appformat.FormatPromptInspection(inspection, cfg.outputFormat)
+	if err != nil {
+		fmt.Fprintf(stderr, "inspect error: %v\n", err)
+		return ExitRuntimeError
+	}
+	if err := writeOutput(stdout, cfg.outputPath, data); err != nil {
+		fmt.Fprintf(stderr, "output write error: %v\n", err)
+		return ExitRuntimeError
+	}
+	return ExitOK
+}
+
+func inspectProfileCommand(args []string, stdout, stderr io.Writer) int {
+	cfg, err := parseProfileInspectionArgs(args)
+	if err != nil {
+		writeApplicationError(stderr, "inspect parse", err)
+		return ExitRuntimeError
+	}
+	settings, err := resolveAppSettingsForProfileInspection(cfg)
+	if err != nil {
+		writeApplicationError(stderr, "inspect", err)
+		return ExitRuntimeError
+	}
+	if err := writeApplicationWarnings(stderr, cfg.diagnostics); err != nil {
+		return ExitRuntimeError
+	}
+	engine, err := newEngine(settings, promptkit.WithPromptFS(emptyPromptDefinitionFS{}, "."))
+	if err != nil {
+		fmt.Fprintf(stderr, "engine error: %v\n", err)
+		return ExitRuntimeError
+	}
+	inspection, err := engine.InspectProfile(context.Background(), cfg.profileID)
+	if err != nil {
+		fmt.Fprintf(stderr, "inspect error: %v\n", err)
+		return ExitRuntimeError
+	}
+	data, err := appformat.FormatProfileInspection(inspection, cfg.outputFormat)
+	if err != nil {
+		fmt.Fprintf(stderr, "inspect error: %v\n", err)
+		return ExitRuntimeError
+	}
+	if err := writeOutput(stdout, cfg.outputPath, data); err != nil {
+		fmt.Fprintf(stderr, "output write error: %v\n", err)
+		return ExitRuntimeError
+	}
+	return ExitOK
+}
+
+func parseProfileInspectionArgs(args []string) (*profileInspectionConfig, error) {
+	cfg := &profileInspectionConfig{outputFormat: appformat.DefaultOutputFormat}
+	fs := flag.NewFlagSet("inspect profile", flag.ContinueOnError)
+	fs.SetOutput(io.Discard)
+	registerConfigSelectionFlags(fs, &cfg.configPath, &cfg.configOverlay)
+	fs.StringVar(&cfg.profileDir, "profile-dir", "", "directory containing execution profiles")
+	fs.StringVar(&cfg.profileID, "profile", "", "profile ID to inspect")
+	rawFormat := ""
+	fs.StringVar(&rawFormat, "format", "", "output format: text or json")
+	fs.StringVar(&cfg.outputPath, "out", "", "optional output file path")
+	if err := fs.Parse(args); err != nil {
+		return nil, err
+	}
+	cfg.configExplicit = flagWasSet(fs, "config")
+	cfg.overrides = applicationOverrides(fs)
+	if fs.NArg() > 0 {
+		return nil, fmt.Errorf("unexpected positional args: %v", fs.Args())
+	}
+	if strings.TrimSpace(cfg.profileID) == "" {
+		return nil, errors.New("--profile is required")
+	}
+	format, err := appformat.ParseOutputFormat(rawFormat)
+	if err != nil {
+		return nil, err
+	}
+	cfg.outputFormat = format
+	if cfg.outputPath != "" {
+		cfg.outputPath = filepath.Clean(cfg.outputPath)
+	}
+	return cfg, nil
+}
+
+func resolveAppSettingsForProfileInspection(cfg *profileInspectionConfig) (engineSettings, error) {
+	settings, diagnostics, err := loadApplicationSettings(cfg.configPath, cfg.configOverlay, cfg.configExplicit, cfg.overrides)
+	if err != nil {
+		return engineSettings{}, err
+	}
+	cfg.diagnostics = diagnostics
+	return engineSettings{profileDir: settings.ProfileDir, backends: settings.Backends, transientRetries: settings.TransientRetries}, nil
+}
+
+func parsePromptInspectionArgs(args []string) (*promptInspectionConfig, error) {
+	cfg := &promptInspectionConfig{outputFormat: appformat.DefaultOutputFormat}
+	fs := flag.NewFlagSet("inspect prompt", flag.ContinueOnError)
+	fs.SetOutput(io.Discard)
+	registerConfigSelectionFlags(fs, &cfg.configPath, &cfg.configOverlay)
+	fs.StringVar(&cfg.promptDir, "prompt-dir", "", "directory containing prompt definitions")
+	fs.StringVar(&cfg.promptID, "prompt", "", "prompt ID to inspect")
+	fs.StringVar(&cfg.promptVersion, "prompt-version", "", "optional prompt version")
+	rawFormat := ""
+	fs.StringVar(&rawFormat, "format", "", "output format: text or json")
+	fs.StringVar(&cfg.outputPath, "out", "", "optional output file path")
+	if err := fs.Parse(args); err != nil {
+		return nil, err
+	}
+	cfg.configExplicit = flagWasSet(fs, "config")
+	cfg.overrides = applicationOverrides(fs)
+	if fs.NArg() > 0 {
+		return nil, fmt.Errorf("unexpected positional args: %v", fs.Args())
+	}
+	if strings.TrimSpace(cfg.promptID) == "" {
+		return nil, errors.New("--prompt is required")
+	}
+	format, err := appformat.ParseOutputFormat(rawFormat)
+	if err != nil {
+		return nil, err
+	}
+	cfg.outputFormat = format
+	if cfg.outputPath != "" {
+		cfg.outputPath = filepath.Clean(cfg.outputPath)
+	}
+	return cfg, nil
+}
+
+func resolveAppSettingsForPromptInspection(cfg *promptInspectionConfig) (engineSettings, error) {
+	settings, diagnostics, err := loadApplicationSettings(cfg.configPath, cfg.configOverlay, cfg.configExplicit, cfg.overrides)
+	if err != nil {
+		return engineSettings{}, err
+	}
+	cfg.diagnostics = diagnostics
+	if strings.TrimSpace(settings.PromptDir) == "" {
+		return engineSettings{}, errors.New(errPromptDirRequired)
+	}
+	return engineSettings{promptDir: settings.PromptDir, backends: settings.Backends, transientRetries: settings.TransientRetries}, nil
+}

internal/adapter/cli/run.go

@@ -2,6 +2,7 @@ package cli
 
 import (
 	"context"
+	"encoding/json"
 	"errors"
 	"flag"
 	"fmt"
@@ -12,18 +13,13 @@ import (
 	"strings"
 	"time"
 
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/promptkit"
 	httpadapter "gitea.maximumdirect.net/eric/scriptorium/internal/adapter/http"
-	artifactadapter "gitea.maximumdirect.net/eric/scriptorium/internal/artifact"
 	appconfig "gitea.maximumdirect.net/eric/scriptorium/internal/config"
 	"gitea.maximumdirect.net/eric/scriptorium/internal/defaults"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/domain"
 	renderformat "gitea.maximumdirect.net/eric/scriptorium/internal/format"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/llm"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/profile"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/prompt"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/promptdef"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/usecase"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/validate"
+	executionreport "gitea.maximumdirect.net/eric/scriptorium/internal/report"
 )
 
 const (
@@ -33,38 +29,49 @@ const (
 )
 
 const (
-	errPromptDirRequired  = "prompt directory is required; provide --prompt-dir or config.yml prompt_dir"
-	errProfileDirRequired = "profile directory is required; provide --profile-dir or config.yml profile_dir"
+	errPromptDirRequired = "prompt directory is required; provide --prompt-dir or config.yml prompt_dir"
 )
 
 type runConfig struct {
 	configPath string
 
-	promptDir   string
-	profileDir  string
-	promptID    string
-	profileID   string
-	inputRaw    listFlag
-	varRaw      listFlag
-	outputPath  string
-	llmBaseURL  string
-	apiKeyEnv   string
-	model       string
-	temperature float64
-	maxTokens   int
-	topP        float64
-	schemaDir   string
-	timeout     time.Duration
+	promptDir                  string
+	profileDir                 string
+	promptID                   string
+	promptVersion              string
+	profileID                  string
+	sessionID                  string
+	inputRaw                   listFlag
+	varRaw                     listFlag
+	outputPath                 string
+	executionReportPath        string
+	llmBaseURL                 string
+	apiKeyEnv                  string
+	model                      string
+	temperature                float64
+	maxTokens                  int
+	topP                       float64
+	reasoningEffort            string
+	schemaDir                  string
+	backends                   []appconfig.BackendSettings
+	timeout                    time.Duration
+	runTimeout                 time.Duration
+	transientRetries           int
+	configuredTransientRetries *int
+	diagnostics                []configkit.Diagnostic
+	configOverlay              string
 
 	defaultRenderFormat renderformat.PreparedRunOutputFormat
 
-	llmBaseURLSet  bool
-	apiKeyEnvSet   bool
-	modelSet       bool
-	temperatureSet bool
-	maxTokensSet   bool
-	topPSet        bool
-	timeoutSet     bool
+	llmBaseURLSet       bool
+	apiKeyEnvSet        bool
+	modelSet            bool
+	temperatureSet      bool
+	maxTokensSet        bool
+	topPSet             bool
+	reasoningEffortSet  bool
+	timeoutSet          bool
+	transientRetriesSet bool
 }
 
 type renderConfig struct {
@@ -75,10 +82,33 @@ type renderConfig struct {
 type serveConfig struct {
 	configPath string
 
-	addr       string
-	promptDir  string
-	profileDir string
-	schemaDir  string
+	addr             string
+	promptDir        string
+	profileDir       string
+	schemaDir        string
+	artifactRoot     string
+	maxRequestBytes  int64
+	maxArtifactBytes int64
+	maxResponseBytes int64
+	backends         []appconfig.BackendSettings
+	transientRetries *int
+	diagnostics      []configkit.Diagnostic
+	configOverlay    string
+}
+
+type commonCommandSettings struct {
+	promptDir           string
+	profileDir          string
+	schemaDir           string
+	serverAddr          string
+	artifactRoot        string
+	maxRequestBytes     int64
+	maxArtifactBytes    int64
+	maxResponseBytes    int64
+	defaultRenderFormat renderformat.PreparedRunOutputFormat
+	backends            []appconfig.BackendSettings
+	transientRetries    *int
+	diagnostics         []configkit.Diagnostic
 }
 
 type listFlag []string
@@ -105,6 +135,10 @@ func Run(args []string, stdout, stderr io.Writer) int {
 		return renderCommand(args[1:], stdout, stderr)
 	case "serve":
 		return serveCommand(args[1:], stderr)
+	case "inspect":
+		return inspectCommand(args[1:], stdout, stderr)
+	case "config":
+		return configCommand(args[1:], stdout, stderr)
 	default:
 		fmt.Fprintf(stderr, "unknown command %q\n", args[0])
 		printUsage(stderr)
@@ -115,7 +149,10 @@ func Run(args []string, stdout, stderr io.Writer) int {
 func runCommand(args []string, stdout, stderr io.Writer) int {
 	cfg, err := parseRunArgs(args)
 	if err != nil {
-		fmt.Fprintf(stderr, "run parse error: %v\n", err)
+		writeApplicationError(stderr, "run parse", err)
+		return ExitRuntimeError
+	}
+	if err := writeApplicationWarnings(stderr, cfg.diagnostics); err != nil {
 		return ExitRuntimeError
 	}
 
@@ -125,31 +162,53 @@ func runCommand(args []string, stdout, stderr io.Writer) int {
 		return ExitRuntimeError
 	}
 
-	llmClient, err := llm.NewOpenAICompatibleClient(llm.OpenAICompatibleConfig{
-		Timeout: defaults.LLMRequestTimeoutDefault,
-	})
+	engine, err := newEngine(cfg.engineSettings())
 	if err != nil {
-		fmt.Fprintf(stderr, "llm client error: %v\n", err)
+		fmt.Fprintf(stderr, "engine error: %v\n", err)
 		return ExitRuntimeError
 	}
+	return executeRun(cfg, req, engine.Run, stdout, stderr)
+}
 
-	runner := usecase.NewRunner(
-		promptdef.NewFilesystemRepository(cfg.promptDir),
-		profile.NewFilesystemRepository(cfg.profileDir),
-		artifactadapter.NewCompositeReader(),
-		prompt.NewGoRenderer(),
-		llmClient,
-		validate.NewStandardValidator(cfg.schemaDir),
-	)
-
-	res, runErr := runner.Run(context.Background(), req)
+func executeRun(cfg *runConfig, req promptkit.RunRequest, run func(context.Context, promptkit.RunRequest) (*promptkit.RunResult, error), stdout, stderr io.Writer) int {
+	var collector *executionreport.Collector
+	if cfg.executionReportPath != "" {
+		collector = executionreport.NewCollector()
+		req.Observer = collector.Observe
+	}
+	runContext := context.Background()
+	cancel := func() {}
+	if cfg.runTimeout > 0 {
+		runContext, cancel = context.WithTimeout(runContext, cfg.runTimeout)
+	}
+	res, runErr := run(runContext, req)
+	contextErr := runContext.Err()
+	cancel()
 	if runErr != nil {
-		fmt.Fprintf(stderr, "run error: %v\n", runErr)
-		return ExitRuntimeError
+		if errors.Is(contextErr, context.DeadlineExceeded) {
+			fmt.Fprintln(stderr, "run error: execution deadline exceeded")
+		} else {
+			fmt.Fprintln(stderr, runErrorMessage(runErr))
+		}
 	}
 
-	if err := writeOutput(stdout, cfg.outputPath, res.Artifact.Body); err != nil {
-		fmt.Fprintf(stderr, "output write error: %v\n", err)
+	outputFailed := false
+	if runErr == nil {
+		if err := writeOutput(stdout, cfg.outputPath, res.Artifact.Body); err != nil {
+			fmt.Fprintf(stderr, "output write error: %v\n", err)
+			outputFailed = true
+		}
+	}
+	reportFailed := false
+	if collector != nil {
+		if value := collector.Snapshot(); value == nil {
+			fmt.Fprintln(stderr, "execution report not produced: no terminal observation")
+		} else if err := writeExecutionReport(cfg.executionReportPath, value); err != nil {
+			fmt.Fprintf(stderr, "execution report write error: %v\n", err)
+			reportFailed = true
+		}
+	}
+	if runErr != nil || outputFailed || reportFailed {
 		return ExitRuntimeError
 	}
 
@@ -157,10 +216,21 @@ func runCommand(args []string, stdout, stderr io.Writer) int {
 	return determineExitCode(nil, res)
 }
 
+func writeExecutionReport(path string, value *executionreport.Execution) error {
+	data, err := json.Marshal(value)
+	if err != nil {
+		return err
+	}
+	return os.WriteFile(path, append(data, '\n'), 0644)
+}
+
 func renderCommand(args []string, stdout, stderr io.Writer) int {
 	cfg, err := parseRenderArgs(args)
 	if err != nil {
-		fmt.Fprintf(stderr, "render parse error: %v\n", err)
+		writeApplicationError(stderr, "render parse", err)
+		return ExitRuntimeError
+	}
+	if err := writeApplicationWarnings(stderr, cfg.diagnostics); err != nil {
 		return ExitRuntimeError
 	}
 
@@ -170,16 +240,13 @@ func renderCommand(args []string, stdout, stderr io.Writer) int {
 		return ExitRuntimeError
 	}
 
-	runner := usecase.NewRunner(
-		promptdef.NewFilesystemRepository(cfg.promptDir),
-		profile.NewFilesystemRepository(cfg.profileDir),
-		artifactadapter.NewCompositeReader(),
-		prompt.NewGoRenderer(),
-		nil,
-		validate.NewStandardValidator(cfg.schemaDir),
-	)
+	engine, err := newEngine(cfg.runConfig.engineSettings())
+	if err != nil {
+		fmt.Fprintf(stderr, "engine error: %v\n", err)
+		return ExitRuntimeError
+	}
 
-	prepared, prepErr := runner.Prepare(context.Background(), req)
+	prepared, prepErr := engine.Prepare(context.Background(), req)
 	if prepErr != nil {
 		fmt.Fprintf(stderr, "render error: %v\n", prepErr)
 		return ExitRuntimeError
@@ -201,28 +268,29 @@ func renderCommand(args []string, stdout, stderr io.Writer) int {
 func serveCommand(args []string, stderr io.Writer) int {
 	cfg, err := parseServeArgs(args)
 	if err != nil {
-		fmt.Fprintf(stderr, "serve parse error: %v\n", err)
+		writeApplicationError(stderr, "serve parse", err)
+		return ExitRuntimeError
+	}
+	if err := writeApplicationWarnings(stderr, cfg.diagnostics); err != nil {
 		return ExitRuntimeError
 	}
 
-	llmClient, err := llm.NewOpenAICompatibleClient(llm.OpenAICompatibleConfig{
-		Timeout: defaults.LLMRequestTimeoutDefault,
-	})
+	artifactReader, err := httpadapter.NewRestrictedArtifactReader(cfg.artifactRoot, cfg.maxArtifactBytes)
 	if err != nil {
-		fmt.Fprintf(stderr, "llm client error: %v\n", err)
+		fmt.Fprintf(stderr, "artifact root error: %v\n", err)
 		return ExitRuntimeError
 	}
 
-	runner := usecase.NewRunner(
-		promptdef.NewFilesystemRepository(cfg.promptDir),
-		profile.NewFilesystemRepository(cfg.profileDir),
-		artifactadapter.NewCompositeReader(),
-		prompt.NewGoRenderer(),
-		llmClient,
-		validate.NewStandardValidator(cfg.schemaDir),
-	)
+	engine, err := newEngine(cfg.engineSettings(), promptkit.WithArtifactReader(artifactReader))
+	if err != nil {
+		fmt.Fprintf(stderr, "engine error: %v\n", err)
+		return ExitRuntimeError
+	}
 
-	h := httpadapter.NewHandler(runner)
+	h := httpadapter.NewHandlerWithOptions(engine, httpadapter.HandlerOptions{
+		MaxRequestBytes:  cfg.maxRequestBytes,
+		MaxResponseBytes: cfg.maxResponseBytes,
+	})
 	srv := &http.Server{
 		Addr:              cfg.addr,
 		Handler:           h,
@@ -242,9 +310,11 @@ func parseRunArgs(args []string) (*runConfig, error) {
 	fs := flag.NewFlagSet("run", flag.ContinueOnError)
 	fs.SetOutput(io.Discard)
 
-	registerConfigPathFlag(fs, &cfg.configPath)
+	registerConfigSelectionFlags(fs, &cfg.configPath, &cfg.configOverlay)
 	registerExecutionRequestFlags(fs, cfg)
 	fs.StringVar(&cfg.schemaDir, "schema-dir", "", "base directory for validation schemas")
+	fs.DurationVar(&cfg.runTimeout, "run-timeout", 0, "whole-run execution deadline")
+	fs.StringVar(&cfg.executionReportPath, "execution-report", "", "JSON execution report file path")
 
 	if err := fs.Parse(args); err != nil {
 		return nil, err
@@ -252,11 +322,44 @@ func parseRunArgs(args []string) (*runConfig, error) {
 	if err := finalizeExecutionRequestConfig(fs, cfg); err != nil {
 		return nil, err
 	}
-	cfg.schemaDir = filepath.Clean(cfg.schemaDir)
-
+	if cfg.runTimeout < 0 {
+		return nil, errors.New("--run-timeout must be greater than or equal to 0")
+	}
+	if flagWasSet(fs, "execution-report") {
+		if cfg.executionReportPath == "" {
+			return nil, errors.New("--execution-report requires a nonempty path")
+		}
+		cfg.executionReportPath = filepath.Clean(cfg.executionReportPath)
+		if cfg.outputPath != "" {
+			collision, err := outputPathsCollide(cfg.outputPath, cfg.executionReportPath)
+			if err != nil {
+				return nil, err
+			}
+			if collision {
+				return nil, errors.New("--out and --execution-report select the same file")
+			}
+		}
+	}
 	return cfg, nil
 }
 
+func outputPathsCollide(first, second string) (bool, error) {
+	firstAbs, err := filepath.Abs(first)
+	if err != nil {
+		return false, err
+	}
+	secondAbs, err := filepath.Abs(second)
+	if err != nil {
+		return false, err
+	}
+	if firstAbs == secondAbs {
+		return true, nil
+	}
+	firstInfo, firstErr := os.Stat(firstAbs)
+	secondInfo, secondErr := os.Stat(secondAbs)
+	return firstErr == nil && secondErr == nil && os.SameFile(firstInfo, secondInfo), nil
+}
+
 func parseRenderArgs(args []string) (*renderConfig, error) {
 	cfg := &renderConfig{
 		outputFormat: renderformat.DefaultPreparedRunOutputFormat,
@@ -264,8 +367,9 @@ func parseRenderArgs(args []string) (*renderConfig, error) {
 	fs := flag.NewFlagSet("render", flag.ContinueOnError)
 	fs.SetOutput(io.Discard)
 
-	registerConfigPathFlag(fs, &cfg.configPath)
+	registerConfigSelectionFlags(fs, &cfg.configPath, &cfg.configOverlay)
 	registerExecutionRequestFlags(fs, &cfg.runConfig)
+	fs.StringVar(&cfg.schemaDir, "schema-dir", "", "base directory for validation schemas")
 
 	var rawFormat string
 	fs.StringVar(&rawFormat, "format", "", "render output format (text|json)")
@@ -294,11 +398,15 @@ func parseServeArgs(args []string) (*serveConfig, error) {
 	fs := flag.NewFlagSet("serve", flag.ContinueOnError)
 	fs.SetOutput(io.Discard)
 
-	registerConfigPathFlag(fs, &cfg.configPath)
+	registerConfigSelectionFlags(fs, &cfg.configPath, &cfg.configOverlay)
 	fs.StringVar(&cfg.addr, "addr", "", "HTTP listen address")
 	fs.StringVar(&cfg.promptDir, "prompt-dir", "", "directory containing prompt definition YAML files")
 	fs.StringVar(&cfg.profileDir, "profile-dir", "", "directory containing execution profile YAML files")
 	fs.StringVar(&cfg.schemaDir, "schema-dir", "", "base directory for validation schemas")
+	fs.StringVar(&cfg.artifactRoot, "artifact-root", "", "base directory for HTTP file input artifacts")
+	fs.Int64Var(&cfg.maxRequestBytes, "max-request-bytes", 0, "maximum HTTP request body bytes; 0 disables the limit")
+	fs.Int64Var(&cfg.maxArtifactBytes, "max-artifact-bytes", 0, "maximum HTTP file artifact bytes; 0 disables the limit")
+	fs.Int64Var(&cfg.maxResponseBytes, "max-response-bytes", 0, "maximum HTTP response body bytes; 0 disables the limit")
 
 	if err := fs.Parse(args); err != nil {
 		return nil, err
@@ -307,31 +415,27 @@ func parseServeArgs(args []string) (*serveConfig, error) {
 		return nil, fmt.Errorf("unexpected positional args: %v", fs.Args())
 	}
 
-	settings, err := resolveAppSettings(fs, cfg.configPath, appconfig.CLIOverrides{
-		PromptDir:  cfg.promptDirIfSet(fs),
-		ProfileDir: cfg.profileDirIfSet(fs),
-		SchemaDir:  cfg.schemaDirIfSet(fs),
-		ServerAddr: cfg.addrIfSet(fs),
-	})
+	settings, err := resolveCommonSettings(fs, cfg.configPath, cfg.configOverlay)
 	if err != nil {
 		return nil, err
 	}
 
-	cfg.promptDir = settings.PromptDir
-	cfg.profileDir = settings.ProfileDir
-	cfg.schemaDir = settings.SchemaDir
-	cfg.addr = settings.ServerAddr
+	cfg.promptDir = settings.promptDir
+	cfg.profileDir = settings.profileDir
+	cfg.schemaDir = settings.schemaDir
+	cfg.addr = settings.serverAddr
+	cfg.artifactRoot = settings.artifactRoot
+	cfg.maxRequestBytes = settings.maxRequestBytes
+	cfg.maxArtifactBytes = settings.maxArtifactBytes
+	cfg.maxResponseBytes = settings.maxResponseBytes
+	cfg.backends = settings.backends
+	cfg.transientRetries = settings.transientRetries
+	cfg.diagnostics = settings.diagnostics
 
-	if strings.TrimSpace(cfg.promptDir) == "" {
-		return nil, errors.New(errPromptDirRequired)
-	}
-	if strings.TrimSpace(cfg.profileDir) == "" {
-		return nil, errors.New(errProfileDirRequired)
+	if err := validateRequiredLibraryDirs(cfg.promptDir); err != nil {
+		return nil, err
 	}
 
-	cfg.promptDir = filepath.Clean(cfg.promptDir)
-	cfg.profileDir = filepath.Clean(cfg.profileDir)
-	cfg.schemaDir = filepath.Clean(cfg.schemaDir)
 	return cfg, nil
 }
 
@@ -339,7 +443,9 @@ func registerExecutionRequestFlags(fs *flag.FlagSet, cfg *runConfig) {
 	fs.StringVar(&cfg.promptDir, "prompt-dir", "", "directory containing prompt definition YAML files")
 	fs.StringVar(&cfg.profileDir, "profile-dir", "", "directory containing execution profile YAML files")
 	fs.StringVar(&cfg.promptID, "prompt", "", "prompt ID to run")
+	fs.StringVar(&cfg.promptVersion, "prompt-version", "", "optional prompt definition version")
 	fs.StringVar(&cfg.profileID, "profile", "", "optional execution profile ID; if omitted, prompt default_profile is used")
+	fs.StringVar(&cfg.sessionID, "session-id", "", "optional session ID")
 	fs.Var(&cfg.inputRaw, "input", "input mapping(s): name=path (repeatable, comma-separated)")
 	fs.Var(&cfg.varRaw, "var", "variable mapping(s): name=value (repeatable, comma-separated)")
 	fs.StringVar(&cfg.outputPath, "out", "", "optional output file path")
@@ -349,7 +455,9 @@ func registerExecutionRequestFlags(fs *flag.FlagSet, cfg *runConfig) {
 	fs.Float64Var(&cfg.temperature, "temperature", 0, "optional temperature override")
 	fs.IntVar(&cfg.maxTokens, "max-tokens", 0, "optional max tokens override")
 	fs.Float64Var(&cfg.topP, "top-p", 0, "optional top_p override")
-	fs.DurationVar(&cfg.timeout, "timeout", defaults.LLMRequestTimeoutDefault, "LLM request timeout")
+	fs.StringVar(&cfg.reasoningEffort, "reasoning-effort", "", "optional reasoning effort override")
+	fs.DurationVar(&cfg.timeout, "timeout", 0, "LLM request timeout")
+	fs.IntVar(&cfg.transientRetries, "transient-retries", 0, "additional transient generation attempts")
 	fs.StringVar(&cfg.promptID, "prompt-id", "", "deprecated alias for --prompt")
 	fs.StringVar(&cfg.profileID, "profile-id", "", "deprecated alias for --profile")
 }
@@ -359,34 +467,25 @@ func finalizeExecutionRequestConfig(fs *flag.FlagSet, cfg *runConfig) error {
 		return fmt.Errorf("unexpected positional args: %v", fs.Args())
 	}
 
-	settings, err := resolveAppSettings(fs, cfg.configPath, appconfig.CLIOverrides{
-		PromptDir:  cfg.promptDirIfSet(fs),
-		ProfileDir: cfg.profileDirIfSet(fs),
-		SchemaDir:  cfg.schemaDirIfSet(fs),
-	})
+	settings, err := resolveCommonSettings(fs, cfg.configPath, cfg.configOverlay)
 	if err != nil {
 		return err
 	}
 
-	cfg.promptDir = settings.PromptDir
-	cfg.profileDir = settings.ProfileDir
-	cfg.schemaDir = settings.SchemaDir
-	cfg.defaultRenderFormat = settings.DefaultRenderFormat
+	cfg.promptDir = settings.promptDir
+	cfg.profileDir = settings.profileDir
+	cfg.schemaDir = settings.schemaDir
+	cfg.defaultRenderFormat = settings.defaultRenderFormat
+	cfg.backends = settings.backends
+	cfg.configuredTransientRetries = settings.transientRetries
+	cfg.diagnostics = settings.diagnostics
 
-	if strings.TrimSpace(cfg.promptDir) == "" {
-		return errors.New(errPromptDirRequired)
-	}
-	if strings.TrimSpace(cfg.profileDir) == "" {
-		return errors.New(errProfileDirRequired)
+	if err := validateRequiredLibraryDirs(cfg.promptDir); err != nil {
+		return err
 	}
 	if strings.TrimSpace(cfg.promptID) == "" {
 		return errors.New("--prompt is required")
 	}
-	if len(cfg.inputRaw) == 0 {
-		return errors.New("at least one --input is required")
-	}
-	cfg.promptDir = filepath.Clean(cfg.promptDir)
-	cfg.profileDir = filepath.Clean(cfg.profileDir)
 	if cfg.outputPath != "" {
 		cfg.outputPath = filepath.Clean(cfg.outputPath)
 	}
@@ -396,60 +495,16 @@ func finalizeExecutionRequestConfig(fs *flag.FlagSet, cfg *runConfig) error {
 	cfg.temperatureSet = flagWasSet(fs, "temperature")
 	cfg.maxTokensSet = flagWasSet(fs, "max-tokens")
 	cfg.topPSet = flagWasSet(fs, "top-p")
+	cfg.reasoningEffortSet = flagWasSet(fs, "reasoning-effort")
 	cfg.timeoutSet = flagWasSet(fs, "timeout")
+	cfg.transientRetriesSet = flagWasSet(fs, "transient-retries")
+	if cfg.transientRetriesSet && cfg.transientRetries < 0 {
+		return errors.New("--transient-retries must be greater than or equal to 0")
+	}
 	return nil
 }
 
-func (c *runConfig) promptDirIfSet(fs *flag.FlagSet) string {
-	if flagWasSet(fs, "prompt-dir") {
-		return c.promptDir
-	}
-	return ""
-}
-
-func (c *runConfig) profileDirIfSet(fs *flag.FlagSet) string {
-	if flagWasSet(fs, "profile-dir") {
-		return c.profileDir
-	}
-	return ""
-}
-
-func (c *runConfig) schemaDirIfSet(fs *flag.FlagSet) string {
-	if flagWasSet(fs, "schema-dir") {
-		return c.schemaDir
-	}
-	return ""
-}
-
-func (c *serveConfig) promptDirIfSet(fs *flag.FlagSet) string {
-	if flagWasSet(fs, "prompt-dir") {
-		return c.promptDir
-	}
-	return ""
-}
-
-func (c *serveConfig) profileDirIfSet(fs *flag.FlagSet) string {
-	if flagWasSet(fs, "profile-dir") {
-		return c.profileDir
-	}
-	return ""
-}
-
-func (c *serveConfig) schemaDirIfSet(fs *flag.FlagSet) string {
-	if flagWasSet(fs, "schema-dir") {
-		return c.schemaDir
-	}
-	return ""
-}
-
-func (c *serveConfig) addrIfSet(fs *flag.FlagSet) string {
-	if flagWasSet(fs, "addr") {
-		return c.addr
-	}
-	return ""
-}
-
-func registerConfigPathFlag(fs *flag.FlagSet, target *string) {
+func registerConfigSelectionFlags(fs *flag.FlagSet, target, overlay *string) {
 	fs.StringVar(
 		target,
 		"config",
@@ -460,62 +515,142 @@ func registerConfigPathFlag(fs *flag.FlagSet, target *string) {
 			appconfig.DefaultConfigPath,
 		),
 	)
+	fs.StringVar(overlay, "config-overlay", "", "selected application configuration overlay")
 }
 
-func resolveAppSettings(fs *flag.FlagSet, configPath string, overrides appconfig.CLIOverrides) (appconfig.AppSettings, error) {
-	settings, err := appconfig.LoadConfig(configPath, flagWasSet(fs, "config"))
+func resolveCommonSettings(fs *flag.FlagSet, configPath, overlay string) (commonCommandSettings, error) {
+	settings, diagnostics, err := loadApplicationSettings(configPath, overlay, flagWasSet(fs, "config"), applicationOverrides(fs))
 	if err != nil {
-		return appconfig.AppSettings{}, fmt.Errorf("application config error: %w", err)
+		return commonCommandSettings{}, err
 	}
-
-	merged, err := appconfig.ApplyCLIOverrides(settings, overrides)
-	if err != nil {
-		return appconfig.AppSettings{}, fmt.Errorf("application config error: %w", err)
-	}
-
-	return merged, nil
+	return commonCommandSettings{
+		promptDir:           settings.PromptDir,
+		profileDir:          settings.ProfileDir,
+		schemaDir:           settings.SchemaDir,
+		serverAddr:          settings.ServerAddr,
+		artifactRoot:        settings.ArtifactRoot,
+		maxRequestBytes:     settings.MaxRequestBytes,
+		maxArtifactBytes:    settings.MaxArtifactBytes,
+		maxResponseBytes:    settings.MaxResponseBytes,
+		defaultRenderFormat: settings.DefaultRenderFormat,
+		backends:            settings.Backends,
+		transientRetries:    settings.TransientRetries,
+		diagnostics:         diagnostics,
+	}, nil
 }
 
-func buildRunRequestFromConfig(cfg *runConfig) (domain.RunRequest, error) {
-	inputMappings, err := parseMappings(cfg.inputRaw, false)
+func validateRequiredLibraryDirs(promptDir string) error {
+	if strings.TrimSpace(promptDir) == "" {
+		return errors.New(errPromptDirRequired)
+	}
+	return nil
+}
+
+type engineSettings struct {
+	promptDir        string
+	profileDir       string
+	schemaDir        string
+	backends         []appconfig.BackendSettings
+	transientRetries *int
+}
+
+func (c runConfig) engineSettings() engineSettings {
+	return engineSettings{promptDir: c.promptDir, profileDir: c.profileDir, schemaDir: c.schemaDir, backends: c.backends, transientRetries: c.configuredTransientRetries}
+}
+
+func (c serveConfig) engineSettings() engineSettings {
+	return engineSettings{promptDir: c.promptDir, profileDir: c.profileDir, schemaDir: c.schemaDir, backends: c.backends, transientRetries: c.transientRetries}
+}
+
+func newEngine(settings engineSettings, options ...promptkit.Option) (*promptkit.Engine, error) {
+	engineOptions := make([]promptkit.Option, 0, len(settings.backends)+len(options))
+	for _, configured := range settings.backends {
+		engineOptions = append(engineOptions, promptkit.WithBackend(promptkit.Backend{
+			ID:               configured.ID,
+			Endpoint:         configured.Endpoint,
+			APIKeyEnv:        configured.APIKeyEnv,
+			ExtraParams:      configured.ExtraParams,
+			ConcurrencyLimit: configured.ConcurrencyLimit,
+			QueueCapacity:    configured.QueueCapacity,
+		}))
+	}
+	engineOptions = append(engineOptions, options...)
+	engine, err := promptkit.NewEngine(promptkit.Config{
+		PromptDir:        settings.promptDir,
+		ProfileDir:       settings.profileDir,
+		SchemaDir:        settings.schemaDir,
+		TransientRetries: settings.transientRetries,
+	}, engineOptions...)
 	if err != nil {
-		return domain.RunRequest{}, fmt.Errorf("input parse error: %w", err)
+		return nil, fmt.Errorf("engine initialization from application configuration: %w", err)
+	}
+	return engine, nil
+}
+
+func buildRunRequestFromConfig(cfg *runConfig) (promptkit.RunRequest, error) {
+	var inputMappings map[string]string
+	var err error
+	if len(cfg.inputRaw) > 0 {
+		inputMappings, err = parseMappings(cfg.inputRaw, false)
+		if err != nil {
+			return promptkit.RunRequest{}, fmt.Errorf("input parse error: %w", err)
+		}
 	}
 
 	varMappings := map[string]string{}
 	if len(cfg.varRaw) > 0 {
 		varMappings, err = parseMappings(cfg.varRaw, false)
 		if err != nil {
-			return domain.RunRequest{}, fmt.Errorf("var parse error: %w", err)
+			return promptkit.RunRequest{}, fmt.Errorf("var parse error: %w", err)
 		}
 	}
 
-	inputs := make(map[string]domain.ArtifactRef, len(inputMappings))
-	for name, path := range inputMappings {
-		inputs[name] = domain.ArtifactRef{Type: domain.ArtifactRefFile, URI: path}
+	var inputs map[string]promptkit.ArtifactRef
+	if len(inputMappings) > 0 {
+		inputs = make(map[string]promptkit.ArtifactRef, len(inputMappings))
+		for name, path := range inputMappings {
+			inputs[name] = promptkit.File(path)
+		}
 	}
 
-	var modelOverride *domain.ExecutionTarget
-	if cfg.llmBaseURLSet || cfg.modelSet || cfg.temperatureSet || cfg.maxTokensSet || cfg.topPSet || cfg.apiKeyEnvSet || cfg.timeoutSet {
-		modelOverride = &domain.ExecutionTarget{
-			Endpoint:    cfg.llmBaseURL,
-			Model:       cfg.model,
-			Temperature: cfg.temperature,
-			MaxTokens:   cfg.maxTokens,
-			TopP:        cfg.topP,
-			APIKeyEnv:   cfg.apiKeyEnv,
+	var modelOverride *promptkit.ExecutionTargetOverride
+	if cfg.llmBaseURLSet || cfg.modelSet || cfg.temperatureSet || cfg.maxTokensSet || cfg.topPSet || cfg.reasoningEffortSet || cfg.apiKeyEnvSet || cfg.timeoutSet {
+		modelOverride = &promptkit.ExecutionTargetOverride{
+			Endpoint:  cfg.llmBaseURL,
+			Model:     cfg.model,
+			APIKeyEnv: cfg.apiKeyEnv,
+		}
+		if cfg.temperatureSet {
+			modelOverride.Temperature = &cfg.temperature
+		}
+		if cfg.maxTokensSet {
+			modelOverride.MaxTokens = &cfg.maxTokens
+		}
+		if cfg.topPSet {
+			modelOverride.TopP = &cfg.topP
+		}
+		if cfg.reasoningEffortSet {
+			modelOverride.ReasoningEffort = &cfg.reasoningEffort
 		}
 		if cfg.timeoutSet {
-			modelOverride.TimeoutSeconds = int(cfg.timeout.Seconds())
+			timeoutSeconds := int(cfg.timeout.Seconds())
+			modelOverride.TimeoutSeconds = &timeoutSeconds
 		}
 	}
 
-	return domain.RunRequest{
-		PromptID:  cfg.promptID,
-		ProfileID: cfg.profileID,
-		Inputs:    inputs,
-		Vars:      varMappings,
-		Execution: modelOverride,
+	var transientRetries *int
+	if cfg.transientRetriesSet {
+		transientRetries = &cfg.transientRetries
+	}
+	return promptkit.RunRequest{
+		PromptID:         cfg.promptID,
+		PromptVersion:    cfg.promptVersion,
+		ProfileID:        cfg.profileID,
+		SessionID:        cfg.sessionID,
+		Inputs:           inputs,
+		Vars:             varMappings,
+		Execution:        modelOverride,
+		TransientRetries: transientRetries,
 	}, nil
 }
 
@@ -574,21 +709,21 @@ func writeOutput(stdout io.Writer, outputPath string, body []byte) error {
 	return os.WriteFile(outputPath, body, 0644)
 }
 
-func determineExitCode(runErr error, result *domain.RunResult) int {
+func determineExitCode(runErr error, result *promptkit.RunResult) int {
 	if runErr != nil {
 		return ExitRuntimeError
 	}
-	if result != nil && result.Validation.Status == domain.ValidationFailed {
+	if result != nil && result.Validation.Status == promptkit.ValidationFailed {
 		return ExitValidationFailed
 	}
 	return ExitOK
 }
 
-func printSummary(stderr io.Writer, res *domain.RunResult) {
+func printSummary(stderr io.Writer, res *promptkit.RunResult) {
 	if res == nil {
 		return
 	}
-	fmt.Fprintf(stderr, "prompt=%s@%s selected_profile=%s model=%s validation=%s mode=%s validation_errors=%d prompt_hash=%s inputs=%d usage=%d/%d/%d\n",
+	fmt.Fprintf(stderr, "prompt=%s@%s selected_profile=%s model=%s validation=%s mode=%s validation_errors=%d prompt_hash=%s inputs=%d usage=%d/%d/%d",
 		res.PromptID,
 		res.PromptVersion,
 		res.SelectedProfileID,
@@ -602,11 +737,28 @@ func printSummary(stderr io.Writer, res *domain.RunResult) {
 		res.Usage.CompletionTokens,
 		res.Usage.TotalTokens,
 	)
+	if res.Usage.CachedTokens != 0 || res.Usage.CacheWriteTokens != 0 {
+		fmt.Fprintf(stderr, " cached_tokens=%d cache_write_tokens=%d", res.Usage.CachedTokens, res.Usage.CacheWriteTokens)
+	}
+	if res.SelectedBackendID != "" {
+		fmt.Fprintf(stderr, " backend=%s", res.SelectedBackendID)
+	}
+	fmt.Fprintln(stderr)
+}
+
+func runErrorMessage(err error) string {
+	if errors.Is(err, promptkit.ErrCapacityExceeded) {
+		return "run error: model backend capacity is exhausted"
+	}
+	return fmt.Sprintf("run error: %v", err)
 }
 
 func printUsage(w io.Writer) {
-	fmt.Fprintln(w, "usage: scriptorium <run|render|serve> ...")
-	fmt.Fprintln(w, "  run:   scriptorium run [--config PATH] [--prompt-dir DIR] [--profile-dir DIR] --prompt ID --input name=path [--input ...] [--profile ID] [--llm-base-url URL] [--model NAME] [--api-key-env ENV] [--temperature N] [--max-tokens N] [--top-p N] [--var k=v] [--out path] [--timeout 10m]")
-	fmt.Fprintln(w, "  render: scriptorium render [--config PATH] [--prompt-dir DIR] [--profile-dir DIR] --prompt ID --input name=path [--input ...] [--profile ID] [--llm-base-url URL] [--model NAME] [--api-key-env ENV] [--temperature N] [--max-tokens N] [--top-p N] [--var k=v] [--format text|json] [--out path] [--timeout 10m]")
-	fmt.Fprintf(w, "  serve: scriptorium serve [--config PATH] [--addr %s] [--prompt-dir DIR] [--profile-dir DIR] [--schema-dir DIR]\n", defaults.HTTPAddrDefault)
+	fmt.Fprintln(w, "usage: scriptorium <run|render|serve|inspect|config> ...")
+	fmt.Fprintln(w, "  run:   scriptorium run [--config PATH] [--config-overlay NAME] [--prompt-dir DIR] [--profile-dir DIR] [--schema-dir DIR] --prompt ID [--prompt-version VERSION] [--input name=path] [--profile ID] [--session-id ID] [--llm-base-url URL] [--model NAME] [--api-key-env ENV] [--temperature N] [--max-tokens N] [--top-p N] [--reasoning-effort VALUE] [--var k=v] [--out path] [--execution-report path] [--timeout 10m] [--run-timeout 10m] [--transient-retries N]")
+	fmt.Fprintln(w, "  render: scriptorium render [--config PATH] [--config-overlay NAME] [--prompt-dir DIR] [--profile-dir DIR] [--schema-dir DIR] --prompt ID [--prompt-version VERSION] [--input name=path] [--profile ID] [--session-id ID] [--llm-base-url URL] [--model NAME] [--api-key-env ENV] [--temperature N] [--max-tokens N] [--top-p N] [--reasoning-effort VALUE] [--var k=v] [--format text|json] [--out path] [--timeout 10m] [--transient-retries N]")
+	fmt.Fprintf(w, "  serve: scriptorium serve [--config PATH] [--config-overlay NAME] [--addr %s] [--prompt-dir DIR] [--profile-dir DIR] [--schema-dir DIR] [--artifact-root DIR] [--max-request-bytes N] [--max-artifact-bytes N] [--max-response-bytes N]\n", defaults.HTTPAddrDefault)
+	fmt.Fprintln(w, "  inspect prompt: scriptorium inspect prompt --prompt ID [--prompt-version VERSION] [--config PATH] [--config-overlay NAME] [--prompt-dir DIR] [--format text|json] [--out path]")
+	fmt.Fprintln(w, "  inspect profile: scriptorium inspect profile --profile ID [--config PATH] [--config-overlay NAME] [--profile-dir DIR] [--format text|json] [--out path]")
+	fmt.Fprintln(w, "  config: scriptorium config <validate|show|sources|explain> [--config PATH] [--config-overlay NAME] [application overrides] [--path /pointer for explain]")
 }

internal/adapter/dependency_test.go

@@ -0,0 +1,322 @@
+package adapter_test
+
+import (
+	"fmt"
+	"go/parser"
+	"go/token"
+	"io/fs"
+	"os"
+	"path/filepath"
+	"runtime"
+	"strconv"
+	"strings"
+	"testing"
+)
+
+const (
+	scriptoriumModulePath             = "gitea.maximumdirect.net/eric/scriptorium"
+	promptkitInternalPath             = "gitea.maximumdirect.net/eric/promptkit/internal"
+	promptkitOpenRouterCatalogPath    = "gitea.maximumdirect.net/eric/promptkit-backend-openrouter"
+	promptkitRakestrawhomeCatalogPath = "gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome"
+)
+
+var (
+	removedFrameworkPackageRoots = []string{
+		scriptoriumModulePath + "/internal/artifact",
+		scriptoriumModulePath + "/internal/domain",
+		scriptoriumModulePath + "/internal/filecatalog",
+		scriptoriumModulePath + "/internal/llm",
+		scriptoriumModulePath + "/internal/profile",
+		scriptoriumModulePath + "/internal/prompt",
+		scriptoriumModulePath + "/internal/promptdef",
+		scriptoriumModulePath + "/internal/usecase",
+		scriptoriumModulePath + "/internal/validate",
+	}
+	removedFrameworkDirectories = []string{
+		"internal/artifact",
+		"internal/domain",
+		"internal/filecatalog",
+		"internal/llm",
+		"internal/profile",
+		"internal/prompt",
+		"internal/promptdef",
+		"internal/usecase",
+		"internal/validate",
+	}
+	nonSourceDirectories = map[string]struct{}{
+		".cache":           {},
+		".codebase-memory": {},
+		".git":             {},
+		"build":            {},
+		"coverage":         {},
+		"dist":             {},
+		"node_modules":     {},
+		"out":              {},
+		"testdata":         {},
+		"vendor":           {},
+	}
+)
+
+type forbiddenImport struct {
+	filePath   string
+	importPath string
+}
+
+func TestApplicationBoundary(t *testing.T) {
+	moduleRoot := moduleRootFromTestFile(t)
+
+	violations, err := findForbiddenProductionImports(moduleRoot)
+	if err != nil {
+		t.Fatalf("scan production imports: %v", err)
+	}
+	for _, violation := range violations {
+		t.Errorf("%s imports forbidden package %s", violation.filePath, violation.importPath)
+	}
+
+	assertFrameworkImplementationAbsent(t, moduleRoot)
+}
+
+func TestForbiddenImportScannerDetectsFormerRoot(t *testing.T) {
+	root := t.TempDir()
+	sourcePath := writeGoSource(t, root, "nested/consumer/root.go", scriptoriumModulePath)
+
+	violations, err := findForbiddenProductionImports(root)
+	if err != nil {
+		t.Fatalf("scan source fixture: %v", err)
+	}
+	assertSingleViolation(t, violations, sourcePath, scriptoriumModulePath)
+}
+
+func TestForbiddenImportScannerDetectsFormerFrameworkFamily(t *testing.T) {
+	root := t.TempDir()
+	importPath := scriptoriumModulePath + "/internal/profile/builtin"
+	sourcePath := writeGoSource(t, root, "nested/consumer/profile.go", importPath)
+
+	violations, err := findForbiddenProductionImports(root)
+	if err != nil {
+		t.Fatalf("scan source fixture: %v", err)
+	}
+	assertSingleViolation(t, violations, sourcePath, importPath)
+}
+
+func TestForbiddenImportScannerDetectsPromptkitInternalPackages(t *testing.T) {
+	tests := []struct {
+		name       string
+		importPath string
+	}{
+		{name: "exact internal root", importPath: promptkitInternalPath},
+		{name: "internal descendant", importPath: promptkitInternalPath + "/domain"},
+	}
+
+	for _, tc := range tests {
+		t.Run(tc.name, func(t *testing.T) {
+			root := t.TempDir()
+			sourcePath := writeGoSource(t, root, "nested/consumer/promptkit.go", tc.importPath)
+
+			violations, err := findForbiddenProductionImports(root)
+			if err != nil {
+				t.Fatalf("scan source fixture: %v", err)
+			}
+			assertSingleViolation(t, violations, sourcePath, tc.importPath)
+		})
+	}
+}
+
+func TestForbiddenImportScannerDetectsPromptkitCatalogPackages(t *testing.T) {
+	for _, importPath := range []string{
+		promptkitOpenRouterCatalogPath,
+		promptkitRakestrawhomeCatalogPath,
+	} {
+		t.Run(importPath, func(t *testing.T) {
+			root := t.TempDir()
+			sourcePath := writeGoSource(t, root, "nested/consumer/catalog.go", importPath)
+
+			violations, err := findForbiddenProductionImports(root)
+			if err != nil {
+				t.Fatalf("scan source fixture: %v", err)
+			}
+			assertSingleViolation(t, violations, sourcePath, importPath)
+		})
+	}
+}
+
+func TestForbiddenImportScannerAllowsRetainedApplicationPackages(t *testing.T) {
+	root := t.TempDir()
+	sourcePath := filepath.Join(root, "nested/consumer/application.go")
+	if err := os.MkdirAll(filepath.Dir(sourcePath), 0o755); err != nil {
+		t.Fatalf("create source fixture directory: %v", err)
+	}
+	source := `package consumer
+
+import (
+	_ "gitea.maximumdirect.net/eric/promptkit"
+	_ "gitea.maximumdirect.net/eric/scriptorium/internal/adapter/http"
+	_ "gitea.maximumdirect.net/eric/scriptorium/internal/config"
+	_ "gitea.maximumdirect.net/eric/scriptorium/internal/defaults"
+	_ "gitea.maximumdirect.net/eric/scriptorium/internal/format"
+)
+`
+	if err := os.WriteFile(sourcePath, []byte(source), 0o644); err != nil {
+		t.Fatalf("write source fixture: %v", err)
+	}
+
+	violations, err := findForbiddenProductionImports(root)
+	if err != nil {
+		t.Fatalf("scan source fixture: %v", err)
+	}
+	if len(violations) != 0 {
+		t.Fatalf("expected retained application imports to be allowed, got %#v", violations)
+	}
+}
+
+func findForbiddenProductionImports(root string) ([]forbiddenImport, error) {
+	var violations []forbiddenImport
+	err := filepath.WalkDir(root, func(path string, entry fs.DirEntry, err error) error {
+		if err != nil {
+			return err
+		}
+		if entry.IsDir() {
+			if path != root && shouldSkipSourceDirectory(entry.Name()) {
+				return filepath.SkipDir
+			}
+			return nil
+		}
+		if !strings.HasSuffix(entry.Name(), ".go") || strings.HasSuffix(entry.Name(), "_test.go") {
+			return nil
+		}
+
+		file, err := parser.ParseFile(token.NewFileSet(), path, nil, parser.ImportsOnly)
+		if err != nil {
+			return fmt.Errorf("parse imports in %s: %w", path, err)
+		}
+		for _, imported := range file.Imports {
+			importPath, err := strconv.Unquote(imported.Path.Value)
+			if err != nil {
+				return fmt.Errorf("parse import path in %s: %w", path, err)
+			}
+			if isForbiddenProductionImport(importPath) {
+				violations = append(violations, forbiddenImport{
+					filePath:   path,
+					importPath: importPath,
+				})
+			}
+		}
+		return nil
+	})
+	if err != nil {
+		return nil, fmt.Errorf("walk repository root %s: %w", root, err)
+	}
+	return violations, nil
+}
+
+func shouldSkipSourceDirectory(name string) bool {
+	_, skip := nonSourceDirectories[name]
+	return skip
+}
+
+func isForbiddenProductionImport(importPath string) bool {
+	if importPath == scriptoriumModulePath {
+		return true
+	}
+	if importPath == promptkitInternalPath || strings.HasPrefix(importPath, promptkitInternalPath+"/") {
+		return true
+	}
+	if importPath == promptkitOpenRouterCatalogPath || strings.HasPrefix(importPath, promptkitOpenRouterCatalogPath+"/") {
+		return true
+	}
+	if importPath == promptkitRakestrawhomeCatalogPath || strings.HasPrefix(importPath, promptkitRakestrawhomeCatalogPath+"/") {
+		return true
+	}
+	for _, root := range removedFrameworkPackageRoots {
+		if importPath == root || strings.HasPrefix(importPath, root+"/") {
+			return true
+		}
+	}
+	return false
+}
+
+func moduleRootFromTestFile(t *testing.T) string {
+	t.Helper()
+
+	_, testFile, _, ok := runtime.Caller(0)
+	if !ok {
+		t.Fatal("locate dependency guard source")
+	}
+	root, err := findModuleRoot(filepath.Dir(testFile))
+	if err != nil {
+		t.Fatal(err)
+	}
+	return root
+}
+
+func findModuleRoot(start string) (string, error) {
+	dir, err := filepath.Abs(start)
+	if err != nil {
+		return "", fmt.Errorf("resolve module search path: %w", err)
+	}
+	for {
+		goMod := filepath.Join(dir, "go.mod")
+		if info, err := os.Stat(goMod); err == nil && !info.IsDir() {
+			return dir, nil
+		} else if err != nil && !os.IsNotExist(err) {
+			return "", fmt.Errorf("inspect %s: %w", goMod, err)
+		}
+
+		parent := filepath.Dir(dir)
+		if parent == dir {
+			return "", fmt.Errorf("locate go.mod from %s", start)
+		}
+		dir = parent
+	}
+}
+
+func assertFrameworkImplementationAbsent(t *testing.T, moduleRoot string) {
+	t.Helper()
+
+	entries, err := os.ReadDir(moduleRoot)
+	if err != nil {
+		t.Fatalf("read module root: %v", err)
+	}
+	for _, entry := range entries {
+		if !entry.IsDir() && strings.HasSuffix(entry.Name(), ".go") && !strings.HasSuffix(entry.Name(), "_test.go") {
+			t.Errorf("module root contains production Go file %s", entry.Name())
+		}
+	}
+
+	for _, relativePath := range removedFrameworkDirectories {
+		path := filepath.Join(moduleRoot, filepath.FromSlash(relativePath))
+		if _, err := os.Stat(path); err == nil {
+			t.Errorf("removed framework directory still exists: %s", relativePath)
+		} else if !os.IsNotExist(err) {
+			t.Errorf("inspect removed framework directory %s: %v", relativePath, err)
+		}
+	}
+}
+
+func writeGoSource(t *testing.T, root, relativePath, importPath string) string {
+	t.Helper()
+
+	sourcePath := filepath.Join(root, filepath.FromSlash(relativePath))
+	if err := os.MkdirAll(filepath.Dir(sourcePath), 0o755); err != nil {
+		t.Fatalf("create source fixture directory: %v", err)
+	}
+	source := fmt.Sprintf("package consumer\n\nimport _ %q\n", importPath)
+	if err := os.WriteFile(sourcePath, []byte(source), 0o644); err != nil {
+		t.Fatalf("write source fixture: %v", err)
+	}
+	return sourcePath
+}
+
+func assertSingleViolation(t *testing.T, violations []forbiddenImport, sourcePath, importPath string) {
+	t.Helper()
+
+	if len(violations) != 1 {
+		t.Fatalf("expected one forbidden import, got %#v", violations)
+	}
+	if violations[0].filePath != sourcePath {
+		t.Fatalf("unexpected importing file: %q", violations[0].filePath)
+	}
+	if violations[0].importPath != importPath {
+		t.Fatalf("unexpected forbidden import: %q", violations[0].importPath)
+	}
+}

internal/adapter/http/artifact_reader.go

@@ -0,0 +1,165 @@
+package httpadapter
+
+import (
+	"context"
+	"crypto/sha256"
+	"errors"
+	"fmt"
+	"io"
+	"mime"
+	"os"
+	"path/filepath"
+	"strings"
+
+	"gitea.maximumdirect.net/eric/promptkit"
+)
+
+var (
+	ErrFileNotAllowed  = errors.New("file artifact references are not allowed")
+	ErrFileOutsideRoot = errors.New("file artifact path is outside artifact root")
+	ErrFileTooLarge    = errors.New("file artifact exceeds size limit")
+)
+
+const fallbackArtifactContentType = "text/plain"
+
+// NewRestrictedArtifactReader creates the HTTP artifact reader for a rooted
+// filesystem and optional byte limit. An empty root permits inline artifacts
+// but denies file references; a zero limit permits artifacts of any size.
+func NewRestrictedArtifactReader(root string, maxBytes int64) (promptkit.ArtifactReader, error) {
+	if maxBytes < 0 {
+		return nil, fmt.Errorf("artifact size limit must be greater than or equal to 0")
+	}
+
+	cleanRoot := strings.TrimSpace(root)
+	if cleanRoot == "" {
+		return &restrictedArtifactReader{maxBytes: maxBytes}, nil
+	}
+	absRoot, err := filepath.Abs(filepath.Clean(cleanRoot))
+	if err != nil {
+		return nil, fmt.Errorf("resolve artifact root: %w", err)
+	}
+	return &restrictedArtifactReader{root: absRoot, maxBytes: maxBytes}, nil
+}
+
+type restrictedArtifactReader struct {
+	root     string
+	maxBytes int64
+}
+
+var _ promptkit.ArtifactReader = (*restrictedArtifactReader)(nil)
+
+func (r *restrictedArtifactReader) Read(ctx context.Context, ref promptkit.ArtifactRef) (*promptkit.Artifact, error) {
+	select {
+	case <-ctx.Done():
+		return nil, ctx.Err()
+	default:
+	}
+
+	switch ref.Type {
+	case promptkit.ArtifactRefInline:
+		return readInlineArtifact(ref)
+	case promptkit.ArtifactRefFile:
+		return r.readFileArtifact(ref)
+	default:
+		return nil, fmt.Errorf("unsupported artifact reference type %q", ref.Type)
+	}
+}
+
+func readInlineArtifact(ref promptkit.ArtifactRef) (*promptkit.Artifact, error) {
+	if ref.Body == "" {
+		return nil, errors.New("inline artifact body is required")
+	}
+
+	body := []byte(ref.Body)
+	return &promptkit.Artifact{
+		ContentType: fallbackArtifactContentType,
+		Body:        body,
+		Size:        int64(len(body)),
+		Hash:        artifactHash(body),
+		URI:         ref.URI,
+	}, nil
+}
+
+func (r *restrictedArtifactReader) readFileArtifact(ref promptkit.ArtifactRef) (*promptkit.Artifact, error) {
+	if ref.URI == "" {
+		return nil, errors.New("file artifact path is required")
+	}
+	if r.root == "" {
+		return nil, ErrFileNotAllowed
+	}
+
+	path, err := r.resolveLexicalPath(ref.URI)
+	if err != nil {
+		return nil, err
+	}
+	return readArtifactFile(path, r.maxBytes)
+}
+
+// resolveLexicalPath checks cleaned path containment without resolving symlinks.
+func (r *restrictedArtifactReader) resolveLexicalPath(rawPath string) (string, error) {
+	cleanPath := filepath.Clean(strings.TrimSpace(rawPath))
+	candidate := cleanPath
+	if !filepath.IsAbs(cleanPath) {
+		candidate = filepath.Join(r.root, cleanPath)
+	}
+
+	absCandidate, err := filepath.Abs(candidate)
+	if err != nil {
+		return "", fmt.Errorf("resolve artifact path: %w", err)
+	}
+	absCandidate = filepath.Clean(absCandidate)
+
+	rel, err := filepath.Rel(r.root, absCandidate)
+	if err != nil {
+		return "", fmt.Errorf("compare artifact path to root: %w", err)
+	}
+	if rel == ".." || strings.HasPrefix(rel, ".."+string(filepath.Separator)) || filepath.IsAbs(rel) {
+		return "", ErrFileOutsideRoot
+	}
+	return absCandidate, nil
+}
+
+func readArtifactFile(path string, maxBytes int64) (*promptkit.Artifact, error) {
+	file, err := os.Open(path)
+	if err != nil {
+		return nil, fmt.Errorf("failed to read file %s: %w", path, err)
+	}
+	defer file.Close()
+
+	info, err := file.Stat()
+	if err != nil {
+		return nil, fmt.Errorf("failed to stat file %s: %w", path, err)
+	}
+	if maxBytes > 0 && info.Size() > maxBytes {
+		return nil, ErrFileTooLarge
+	}
+
+	var reader io.Reader = file
+	if maxBytes > 0 {
+		reader = io.LimitReader(file, maxBytes+1)
+	}
+	body, err := io.ReadAll(reader)
+	if err != nil {
+		return nil, fmt.Errorf("failed to read file %s: %w", path, err)
+	}
+	if maxBytes > 0 && int64(len(body)) > maxBytes {
+		return nil, ErrFileTooLarge
+	}
+
+	contentType := mime.TypeByExtension(filepath.Ext(path))
+	if contentType == "" {
+		contentType = fallbackArtifactContentType
+	}
+	return &promptkit.Artifact{
+		Name:        filepath.Base(path),
+		ContentType: contentType,
+		Body:        body,
+		URI:         path,
+		Size:        int64(len(body)),
+		Hash:        artifactHash(body),
+	}, nil
+}
+
+func artifactHash(body []byte) string {
+	return fmt.Sprintf("%x", sha256.Sum256(body))
+}

internal/adapter/http/artifact_reader_test.go

@@ -0,0 +1,185 @@
+package httpadapter
+
+import (
+	"context"
+	"errors"
+	"mime"
+	"os"
+	"path/filepath"
+	"testing"
+
+	"gitea.maximumdirect.net/eric/promptkit"
+)
+
+func TestRestrictedArtifactReaderReadsContainedFiles(t *testing.T) {
+	root := t.TempDir()
+	outside := t.TempDir()
+	inputPath := filepath.Join(root, "input.html")
+	if err := os.WriteFile(inputPath, []byte("allowed"), 0o644); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(root, "input.unknown"), []byte("unknown type"), 0o644); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.Mkdir(filepath.Join(root, "nested"), 0o755); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(outside, "secret.txt"), []byte("denied"), 0o644); err != nil {
+		t.Fatal(err)
+	}
+	expectedContentType := mime.TypeByExtension(filepath.Ext(inputPath))
+	if expectedContentType == "" {
+		t.Fatal("expected built-in HTML content type")
+	}
+
+	reader, err := NewRestrictedArtifactReader(root, 0)
+	if err != nil {
+		t.Fatalf("construct restricted reader: %v", err)
+	}
+
+	for _, ref := range []promptkit.ArtifactRef{
+		{Type: promptkit.ArtifactRefFile, URI: "nested/../input.html"},
+		{Type: promptkit.ArtifactRefFile, URI: inputPath},
+	} {
+		artifact, err := reader.Read(context.Background(), ref)
+		if err != nil {
+			t.Fatalf("read contained path %q: %v", ref.URI, err)
+		}
+		if artifact.Name != "input.html" || artifact.URI != inputPath || artifact.Size != int64(len("allowed")) || string(artifact.Body) != "allowed" {
+			t.Fatalf("unexpected artifact metadata: %#v", artifact)
+		}
+		if artifact.ContentType != expectedContentType {
+			t.Fatalf("unexpected artifact content type: got %q, want %q", artifact.ContentType, expectedContentType)
+		}
+		if artifact.Hash != artifactHash([]byte("allowed")) {
+			t.Fatalf("unexpected artifact hash: %q", artifact.Hash)
+		}
+	}
+
+	artifact, err := reader.Read(context.Background(), promptkit.File("input.unknown"))
+	if err != nil {
+		t.Fatalf("read unknown-extension path: %v", err)
+	}
+	if artifact.ContentType != fallbackArtifactContentType {
+		t.Fatalf("unexpected fallback content type: %q", artifact.ContentType)
+	}
+
+	for _, ref := range []promptkit.ArtifactRef{
+		{Type: promptkit.ArtifactRefFile, URI: filepath.Join("..", filepath.Base(outside), "secret.txt")},
+		{Type: promptkit.ArtifactRefFile, URI: filepath.Join(outside, "secret.txt")},
+	} {
+		_, err := reader.Read(context.Background(), ref)
+		if !errors.Is(err, ErrFileOutsideRoot) {
+			t.Fatalf("expected ErrFileOutsideRoot for %q, got %v", ref.URI, err)
+		}
+	}
+}
+
+func TestRestrictedArtifactReaderFollowsSymlinkAfterLexicalCheck(t *testing.T) {
+	root := t.TempDir()
+	outside := t.TempDir()
+	target := filepath.Join(outside, "linked.txt")
+	if err := os.WriteFile(target, []byte("linked outside root"), 0o644); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.Symlink(target, filepath.Join(root, "linked.txt")); err != nil {
+		t.Skipf("symlink creation unavailable: %v", err)
+	}
+
+	reader, err := NewRestrictedArtifactReader(root, 0)
+	if err != nil {
+		t.Fatalf("construct restricted reader: %v", err)
+	}
+	artifact, err := reader.Read(context.Background(), promptkit.File("linked.txt"))
+	if err != nil {
+		t.Fatalf("read symlink inside root: %v", err)
+	}
+	if string(artifact.Body) != "linked outside root" {
+		t.Fatalf("unexpected symlink artifact body: %q", artifact.Body)
+	}
+}
+
+func TestRestrictedArtifactReaderWithoutRootDeniesFiles(t *testing.T) {
+	reader, err := NewRestrictedArtifactReader("", 0)
+	if err != nil {
+		t.Fatalf("construct rootless reader: %v", err)
+	}
+
+	artifact, err := reader.Read(context.Background(), promptkit.Inline("inline"))
+	if err != nil {
+		t.Fatalf("read inline artifact: %v", err)
+	}
+	if artifact.ContentType != fallbackArtifactContentType || string(artifact.Body) != "inline" || artifact.Hash != artifactHash([]byte("inline")) {
+		t.Fatalf("unexpected inline artifact: %#v", artifact)
+	}
+
+	_, err = reader.Read(context.Background(), promptkit.File("input.txt"))
+	if !errors.Is(err, ErrFileNotAllowed) {
+		t.Fatalf("expected ErrFileNotAllowed, got %v", err)
+	}
+}
+
+func TestRestrictedArtifactReaderEnforcesLimits(t *testing.T) {
+	root := t.TempDir()
+	if err := os.WriteFile(filepath.Join(root, "exact.txt"), []byte("12345"), 0o644); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(root, "large.txt"), []byte("123456"), 0o644); err != nil {
+		t.Fatal(err)
+	}
+
+	reader, err := NewRestrictedArtifactReader(root, 5)
+	if err != nil {
+		t.Fatalf("construct limited reader: %v", err)
+	}
+	artifact, err := reader.Read(context.Background(), promptkit.File("exact.txt"))
+	if err != nil || string(artifact.Body) != "12345" {
+		t.Fatalf("expected exact-limit artifact, got %#v and %v", artifact, err)
+	}
+	_, err = reader.Read(context.Background(), promptkit.File("large.txt"))
+	if !errors.Is(err, ErrFileTooLarge) {
+		t.Fatalf("expected ErrFileTooLarge, got %v", err)
+	}
+
+	unlimited, err := NewRestrictedArtifactReader(root, 0)
+	if err != nil {
+		t.Fatalf("construct unlimited reader: %v", err)
+	}
+	artifact, err = unlimited.Read(context.Background(), promptkit.File("large.txt"))
+	if err != nil || string(artifact.Body) != "123456" {
+		t.Fatalf("expected unlimited artifact, got %#v and %v", artifact, err)
+	}
+
+	if _, err := NewRestrictedArtifactReader(root, -1); err == nil {
+		t.Fatal("expected negative limit to fail")
+	}
+}
+
+func TestRestrictedArtifactReaderRejectsCanceledAndMalformedReferences(t *testing.T) {
+	reader, err := NewRestrictedArtifactReader(t.TempDir(), 0)
+	if err != nil {
+		t.Fatalf("construct reader: %v", err)
+	}
+
+	canceledCtx, cancel := context.WithCancel(context.Background())
+	cancel()
+	for _, ref := range []promptkit.ArtifactRef{
+		promptkit.Inline("input"),
+		promptkit.File("input.txt"),
+	} {
+		_, err := reader.Read(canceledCtx, ref)
+		if !errors.Is(err, context.Canceled) {
+			t.Fatalf("expected cancellation for %#v, got %v", ref, err)
+		}
+	}
+
+	for _, ref := range []promptkit.ArtifactRef{
+		{Type: promptkit.ArtifactRefType("unsupported")},
+		{Type: promptkit.ArtifactRefInline},
+		{Type: promptkit.ArtifactRefFile},
+	} {
+		if _, err := reader.Read(context.Background(), ref); err == nil {
+			t.Fatalf("expected malformed reference %#v to fail", ref)
+		}
+	}
+}

internal/adapter/http/dto.go

@@ -2,16 +2,22 @@ package httpadapter
 
 import (
 	"time"
+
+	executionreport "gitea.maximumdirect.net/eric/scriptorium/internal/report"
 )
 
 type runRequestDTO struct {
-	PromptID         string                   `json:"prompt_id"`
-	PromptVersion    string                   `json:"prompt_version,omitempty"`
-	ProfileID        string                   `json:"profile_id,omitempty"`
-	Inputs           map[string]inputRefDTO   `json:"inputs"`
-	Vars             map[string]string        `json:"vars,omitempty"`
-	Model            *modelOverrideRequestDTO `json:"model,omitempty"`
-	IncludeRawOutput bool                     `json:"include_raw_output,omitempty"`
+	PromptID               string                   `json:"prompt_id"`
+	PromptVersion          string                   `json:"prompt_version,omitempty"`
+	ProfileID              string                   `json:"profile_id,omitempty"`
+	SessionID              string                   `json:"session_id,omitempty"`
+	Inputs                 map[string]inputRefDTO   `json:"inputs"`
+	Vars                   map[string]string        `json:"vars,omitempty"`
+	Model                  *modelOverrideRequestDTO `json:"model,omitempty"`
+	IncludeRawOutput       bool                     `json:"include_raw_output,omitempty"`
+	TransientRetries       *int                     `json:"transient_retries,omitempty"`
+	RunTimeoutSeconds      *int64                   `json:"run_timeout_seconds,omitempty"`
+	IncludeExecutionReport bool                     `json:"include_execution_report,omitempty"`
 }
 
 type inputRefDTO struct {
@@ -21,22 +27,24 @@ type inputRefDTO struct {
 }
 
 type modelOverrideRequestDTO struct {
-	Endpoint        string            `json:"endpoint,omitempty"`
-	Model           string            `json:"model,omitempty"`
-	Temperature     float64           `json:"temperature,omitempty"`
-	MaxTokens       int               `json:"max_tokens,omitempty"`
-	TopP            float64           `json:"top_p,omitempty"`
-	TimeoutSeconds  int               `json:"timeout_seconds,omitempty"`
-	ReasoningEffort string            `json:"reasoning_effort,omitempty"`
-	APIKeyEnv       string            `json:"api_key_env,omitempty"`
-	ExtraParams     map[string]string `json:"extra_params,omitempty"`
+	Endpoint        string         `json:"endpoint,omitempty"`
+	Model           string         `json:"model,omitempty"`
+	Temperature     *float64       `json:"temperature,omitempty"`
+	MaxTokens       *int           `json:"max_tokens,omitempty"`
+	TopP            *float64       `json:"top_p,omitempty"`
+	TimeoutSeconds  *int           `json:"timeout_seconds,omitempty"`
+	ServiceTier     string         `json:"service_tier,omitempty"`
+	ReasoningEffort *string        `json:"reasoning_effort,omitempty"`
+	APIKeyEnv       string         `json:"api_key_env,omitempty"`
+	ExtraParams     map[string]any `json:"extra_params,omitempty"`
 }
 
 type runResponseDTO struct {
-	Artifact       artifactDTO   `json:"artifact"`
-	Validation     validationDTO `json:"validation"`
-	Metadata       metadataDTO   `json:"metadata"`
-	RawModelOutput *string       `json:"raw_model_output,omitempty"`
+	Artifact       artifactDTO                `json:"artifact"`
+	Validation     validationDTO              `json:"validation"`
+	Metadata       metadataDTO                `json:"metadata"`
+	RawModelOutput *string                    `json:"raw_model_output,omitempty"`
+	Execution      *executionreport.Execution `json:"execution,omitempty"`
 }
 
 type artifactDTO struct {
@@ -55,6 +63,8 @@ type metadataDTO struct {
 	PromptHash         string            `json:"prompt_hash"`
 	RenderedPromptHash string            `json:"rendered_prompt_hash"`
 	SelectedProfileID  string            `json:"selected_profile_id"`
+	SelectedBackendID  string            `json:"selected_backend_id,omitempty"`
+	SessionID          string            `json:"session_id,omitempty"`
 	ModelName          string            `json:"model_name"`
 	Endpoint           string            `json:"endpoint"`
 	ModelParams        modelParamsDTO    `json:"model_params"`
@@ -69,21 +79,25 @@ type metadataDTO struct {
 }
 
 type modelParamsDTO struct {
-	Endpoint        string            `json:"endpoint"`
-	Model           string            `json:"model"`
-	Temperature     float64           `json:"temperature"`
-	MaxTokens       int               `json:"max_tokens"`
-	TopP            float64           `json:"top_p"`
-	TimeoutSeconds  int               `json:"timeout_seconds"`
-	ReasoningEffort string            `json:"reasoning_effort,omitempty"`
-	APIKeyEnv       string            `json:"api_key_env,omitempty"`
-	ExtraParams     map[string]string `json:"extra_params,omitempty"`
+	Endpoint        string         `json:"endpoint"`
+	BackendID       string         `json:"backend_id,omitempty"`
+	Model           string         `json:"model"`
+	Temperature     float64        `json:"temperature"`
+	MaxTokens       int            `json:"max_tokens"`
+	TopP            float64        `json:"top_p"`
+	TimeoutSeconds  int            `json:"timeout_seconds"`
+	ServiceTier     string         `json:"service_tier,omitempty"`
+	ReasoningEffort string         `json:"reasoning_effort,omitempty"`
+	APIKeyEnv       string         `json:"api_key_env,omitempty"`
+	ExtraParams     map[string]any `json:"extra_params,omitempty"`
 }
 
 type tokenUsageDTO struct {
 	PromptTokens     int `json:"prompt_tokens"`
 	CompletionTokens int `json:"completion_tokens"`
 	TotalTokens      int `json:"total_tokens"`
+	CachedTokens     int `json:"cached_tokens"`
+	CacheWriteTokens int `json:"cache_write_tokens"`
 }
 
 type validationDTO struct {
@@ -96,7 +110,8 @@ type validationDTO struct {
 }
 
 type errorResponse struct {
-	Error errorBody `json:"error"`
+	Error     errorBody                  `json:"error"`
+	Execution *executionreport.Execution `json:"execution,omitempty"`
 }
 
 type errorBody struct {

internal/adapter/http/handler.go

@@ -4,25 +4,40 @@ import (
 	"context"
 	"encoding/json"
 	"errors"
+	"io"
+	"math"
 	"net/http"
 	"strings"
+	"time"
 
-	"gitea.maximumdirect.net/eric/scriptorium/internal/domain"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/profile"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/promptdef"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/usecase"
+	"gitea.maximumdirect.net/eric/promptkit"
+	"gitea.maximumdirect.net/eric/scriptorium/internal/defaults"
+	executionreport "gitea.maximumdirect.net/eric/scriptorium/internal/report"
 )
 
 type Runner interface {
-	Run(ctx context.Context, req domain.RunRequest) (*domain.RunResult, error)
+	Run(ctx context.Context, req promptkit.RunRequest) (*promptkit.RunResult, error)
 }
 
 type Handler struct {
-	runner Runner
+	runner  Runner
+	options HandlerOptions
+}
+
+type HandlerOptions struct {
+	MaxRequestBytes  int64
+	MaxResponseBytes int64
 }
 
 func NewHandler(runner Runner) *Handler {
-	return &Handler{runner: runner}
+	return NewHandlerWithOptions(runner, HandlerOptions{
+		MaxRequestBytes:  defaults.HTTPMaxRequestBytesDefault,
+		MaxResponseBytes: defaults.HTTPMaxResponseBytesDefault,
+	})
+}
+
+func NewHandlerWithOptions(runner Runner, options HandlerOptions) *Handler {
+	return &Handler{runner: runner, options: options}
 }
 
 func (h *Handler) ServeHTTP(w http.ResponseWriter, r *http.Request) {
@@ -36,9 +51,26 @@ func (h *Handler) ServeHTTP(w http.ResponseWriter, r *http.Request) {
 	}
 
 	var req runRequestDTO
-	dec := json.NewDecoder(r.Body)
+	body := r.Body
+	if h.options.MaxRequestBytes > 0 {
+		body = http.MaxBytesReader(w, r.Body, h.options.MaxRequestBytes)
+	}
+	dec := json.NewDecoder(body)
 	dec.DisallowUnknownFields()
 	if err := dec.Decode(&req); err != nil {
+		if isRequestTooLarge(err) {
+			writeError(w, http.StatusRequestEntityTooLarge, "request_too_large", "request body is too large")
+			return
+		}
+		writeError(w, http.StatusBadRequest, "invalid_json", "invalid JSON request body")
+		return
+	}
+	var trailing any
+	if err := dec.Decode(&trailing); err != io.EOF {
+		if isRequestTooLarge(err) {
+			writeError(w, http.StatusRequestEntityTooLarge, "request_too_large", "request body is too large")
+			return
+		}
 		writeError(w, http.StatusBadRequest, "invalid_json", "invalid JSON request body")
 		return
 	}
@@ -47,46 +79,70 @@ func (h *Handler) ServeHTTP(w http.ResponseWriter, r *http.Request) {
 		writeError(w, http.StatusBadRequest, "invalid_request", "prompt_id is required")
 		return
 	}
-	if len(req.Inputs) == 0 {
-		writeError(w, http.StatusBadRequest, "invalid_request", "inputs is required")
+	if req.TransientRetries != nil && *req.TransientRetries < 0 {
+		writeError(w, http.StatusBadRequest, "invalid_request", "transient_retries must be greater than or equal to 0")
 		return
 	}
-
-	mappedInputs := make(map[string]domain.ArtifactRef, len(req.Inputs))
-	for name, in := range req.Inputs {
-		mappedInputs[name] = domain.ArtifactRef{
-			Type: domain.ArtifactRefType(in.Type),
-			URI:  in.URI,
-			Body: in.Body,
+	if req.RunTimeoutSeconds != nil {
+		if *req.RunTimeoutSeconds < 0 || *req.RunTimeoutSeconds > math.MaxInt64/int64(time.Second) {
+			writeError(w, http.StatusBadRequest, "invalid_request", "run_timeout_seconds is out of range")
+			return
+		}
+	}
+	var mappedInputs map[string]promptkit.ArtifactRef
+	if len(req.Inputs) > 0 {
+		mappedInputs = make(map[string]promptkit.ArtifactRef, len(req.Inputs))
+		for name, in := range req.Inputs {
+			mappedInputs[name] = promptkit.ArtifactRef{
+				Type: promptkit.ArtifactRefType(in.Type),
+				URI:  in.URI,
+				Body: in.Body,
+			}
 		}
 	}
 
-	var model *domain.ExecutionTarget
+	var model *promptkit.ExecutionTargetOverride
 	if req.Model != nil {
-		model = &domain.ExecutionTarget{
-			Endpoint:        req.Model.Endpoint,
-			Model:           req.Model.Model,
-			Temperature:     req.Model.Temperature,
-			MaxTokens:       req.Model.MaxTokens,
-			TopP:            req.Model.TopP,
-			TimeoutSeconds:  req.Model.TimeoutSeconds,
-			ReasoningEffort: req.Model.ReasoningEffort,
-			APIKeyEnv:       req.Model.APIKeyEnv,
-			ExtraParams:     req.Model.ExtraParams,
-		}
+		model = executionTargetOverrideFromModelOverrideDTO(req.Model)
 	}
 
-	res, err := h.runner.Run(r.Context(), domain.RunRequest{
-		PromptID:      req.PromptID,
-		PromptVersion: req.PromptVersion,
-		ProfileID:     req.ProfileID,
-		Inputs:        mappedInputs,
-		Vars:          req.Vars,
-		Execution:     model,
-	})
+	runContext := r.Context()
+	if req.RunTimeoutSeconds != nil && *req.RunTimeoutSeconds > 0 {
+		var cancel context.CancelFunc
+		runContext, cancel = context.WithTimeout(runContext, time.Duration(*req.RunTimeoutSeconds)*time.Second)
+		defer cancel()
+	}
+	mappedRequest := promptkit.RunRequest{
+		PromptID:         req.PromptID,
+		PromptVersion:    req.PromptVersion,
+		ProfileID:        req.ProfileID,
+		SessionID:        req.SessionID,
+		Inputs:           mappedInputs,
+		Vars:             req.Vars,
+		Execution:        model,
+		TransientRetries: req.TransientRetries,
+	}
+	var collector *executionreport.Collector
+	if req.IncludeExecutionReport {
+		collector = executionreport.NewCollector()
+		mappedRequest.Observer = collector.Observe
+	}
+	res, err := h.runner.Run(runContext, mappedRequest)
+	var execution *executionreport.Execution
+	if collector != nil {
+		execution = collector.Snapshot()
+	}
 	if err != nil {
+		switch runContext.Err() {
+		case context.DeadlineExceeded:
+			writeRunFailure(w, http.StatusGatewayTimeout, "deadline_exceeded", "run execution deadline exceeded", execution, h.options.MaxResponseBytes)
+			return
+		case context.Canceled:
+			writeRunFailure(w, http.StatusRequestTimeout, "request_canceled", "run request canceled", execution, h.options.MaxResponseBytes)
+			return
+		}
 		status, code, message := mapRunError(err)
-		writeError(w, status, code, message)
+		writeRunFailure(w, status, code, message, execution, h.options.MaxResponseBytes)
 		return
 	}
 
@@ -107,24 +163,18 @@ func (h *Handler) ServeHTTP(w http.ResponseWriter, r *http.Request) {
 			PromptHash:         res.PromptHash,
 			RenderedPromptHash: res.RenderedPromptHash,
 			SelectedProfileID:  res.SelectedProfileID,
+			SelectedBackendID:  res.SelectedBackendID,
+			SessionID:          res.SessionID,
 			ModelName:          res.ModelName,
 			Endpoint:           res.Endpoint,
-			ModelParams: modelParamsDTO{
-				Endpoint:        res.EffectiveModelParams.Endpoint,
-				Model:           res.EffectiveModelParams.Model,
-				Temperature:     res.EffectiveModelParams.Temperature,
-				MaxTokens:       res.EffectiveModelParams.MaxTokens,
-				TopP:            res.EffectiveModelParams.TopP,
-				TimeoutSeconds:  res.EffectiveModelParams.TimeoutSeconds,
-				ReasoningEffort: res.EffectiveModelParams.ReasoningEffort,
-				APIKeyEnv:       res.EffectiveModelParams.APIKeyEnv,
-				ExtraParams:     res.EffectiveModelParams.ExtraParams,
-			},
-			InputHashes: res.InputHashes,
+			ModelParams:        modelParamsDTOFromExecutionTarget(res.EffectiveModelParams),
+			InputHashes:        res.InputHashes,
 			Usage: tokenUsageDTO{
 				PromptTokens:     res.Usage.PromptTokens,
 				CompletionTokens: res.Usage.CompletionTokens,
 				TotalTokens:      res.Usage.TotalTokens,
+				CachedTokens:     res.Usage.CachedTokens,
+				CacheWriteTokens: res.Usage.CacheWriteTokens,
 			},
 			StartTime:          res.StartTime,
 			EndTime:            res.EndTime,
@@ -133,15 +183,58 @@ func (h *Handler) ServeHTTP(w http.ResponseWriter, r *http.Request) {
 			ValidationStatus:   string(res.Validation.Status),
 			RepairAttemptsUsed: res.Validation.RepairAttempts,
 		},
+		Execution: execution,
 	}
 	if req.IncludeRawOutput {
 		raw := res.RawOutput
 		resp.RawModelOutput = &raw
 	}
-	writeJSON(w, http.StatusOK, resp)
+	writeLimitedJSON(w, http.StatusOK, resp, h.options.MaxResponseBytes)
 }
 
-func mapValidation(v domain.ValidationResult) validationDTO {
+func writeRunFailure(w http.ResponseWriter, status int, code, message string, execution *executionreport.Execution, maxBytes int64) {
+	if execution == nil {
+		writeError(w, status, code, message)
+		return
+	}
+	writeLimitedJSON(w, status, errorResponse{Error: errorBody{Code: code, Message: message}, Execution: execution}, maxBytes)
+}
+
+func executionTargetOverrideFromModelOverrideDTO(dto *modelOverrideRequestDTO) *promptkit.ExecutionTargetOverride {
+	if dto == nil {
+		return nil
+	}
+	return &promptkit.ExecutionTargetOverride{
+		Endpoint:        dto.Endpoint,
+		Model:           dto.Model,
+		Temperature:     dto.Temperature,
+		MaxTokens:       dto.MaxTokens,
+		TopP:            dto.TopP,
+		TimeoutSeconds:  dto.TimeoutSeconds,
+		ServiceTier:     dto.ServiceTier,
+		ReasoningEffort: dto.ReasoningEffort,
+		APIKeyEnv:       dto.APIKeyEnv,
+		ExtraParams:     dto.ExtraParams,
+	}
+}
+
+func modelParamsDTOFromExecutionTarget(target promptkit.ExecutionTarget) modelParamsDTO {
+	return modelParamsDTO{
+		Endpoint:        target.Endpoint,
+		BackendID:       target.BackendID,
+		Model:           target.Model,
+		Temperature:     target.Temperature,
+		MaxTokens:       target.MaxTokens,
+		TopP:            target.TopP,
+		TimeoutSeconds:  target.TimeoutSeconds,
+		ServiceTier:     target.ServiceTier,
+		ReasoningEffort: target.ReasoningEffort,
+		APIKeyEnv:       target.APIKeyEnv,
+		ExtraParams:     target.ExtraParams,
+	}
+}
+
+func mapValidation(v promptkit.ValidationResult) validationDTO {
 	return validationDTO{
 		Status:         string(v.Status),
 		Mode:           string(v.Mode),
@@ -154,29 +247,33 @@ func mapValidation(v domain.ValidationResult) validationDTO {
 
 func mapRunError(err error) (int, string, string) {
 	switch {
-	case errors.Is(err, promptdef.ErrPromptDefinitionNotFound):
+	case errors.Is(err, promptkit.ErrPromptNotFound):
 		return http.StatusNotFound, "prompt_not_found", "prompt definition not found"
-	case errors.Is(err, profile.ErrProfileNotFound):
+	case errors.Is(err, promptkit.ErrProfileNotFound):
 		return http.StatusNotFound, "profile_not_found", "execution profile not found"
-	case errors.Is(err, promptdef.ErrInvalidYAML), errors.Is(err, promptdef.ErrInvalidPromptDefinition):
-		return http.StatusBadRequest, "prompt_load_failed", "failed to load prompt definition"
-	case errors.Is(err, profile.ErrInvalidYAML), errors.Is(err, profile.ErrInvalidProfile):
-		return http.StatusBadRequest, "profile_load_failed", "failed to load execution profile"
-	case errors.Is(err, usecase.ErrInvalidRequest) && strings.Contains(err.Error(), "profile id is required either in request or prompt default_profile"):
+	case errors.Is(err, promptkit.ErrProfileRequired):
 		return http.StatusBadRequest, "profile_required", "profile_id is required when prompt default_profile is not set"
-	case errors.Is(err, usecase.ErrInvalidRequest) && strings.Contains(err.Error(), "api key environment variable"):
+	case errors.Is(err, promptkit.ErrAPIKeyEnvMissing):
 		return http.StatusBadRequest, "api_key_env_missing", "api_key_env is set but the environment variable is missing"
-	case errors.Is(err, usecase.ErrInvalidRequest):
-		return http.StatusBadRequest, "invalid_request", "invalid run request"
-	case errors.Is(err, usecase.ErrProfileLoad):
+	case errors.Is(err, promptkit.ErrPromptLoad):
 		return http.StatusBadRequest, "prompt_load_failed", "failed to load prompt definition"
-	case errors.Is(err, usecase.ErrArtifactLoad):
+	case errors.Is(err, promptkit.ErrProfileLoad):
+		return http.StatusBadRequest, "profile_load_failed", "failed to load execution profile"
+	case errors.Is(err, promptkit.ErrInvalidRequest):
+		return http.StatusBadRequest, "invalid_request", "invalid run request"
+	case errors.Is(err, ErrFileNotAllowed), errors.Is(err, ErrFileOutsideRoot):
+		return http.StatusBadRequest, "artifact_not_allowed", "file input artifact is not allowed"
+	case errors.Is(err, ErrFileTooLarge):
+		return http.StatusRequestEntityTooLarge, "artifact_too_large", "file input artifact is too large"
+	case errors.Is(err, promptkit.ErrArtifactLoad):
 		return http.StatusBadRequest, "artifact_read_failed", "failed to read input artifact"
-	case errors.Is(err, usecase.ErrPromptRender):
+	case errors.Is(err, promptkit.ErrPromptRender):
 		return http.StatusBadRequest, "prompt_render_failed", "failed to render prompt"
-	case errors.Is(err, usecase.ErrLLMGenerate):
+	case errors.Is(err, promptkit.ErrCapacityExceeded):
+		return http.StatusServiceUnavailable, "capacity_exceeded", "model backend capacity is exhausted"
+	case errors.Is(err, promptkit.ErrLLMGenerate), errors.Is(err, promptkit.ErrTransport), errors.Is(err, promptkit.ErrMalformedResponse), errors.Is(err, promptkit.ErrRetriesExhausted):
 		return http.StatusBadGateway, "llm_failed", "model generation request failed"
-	case errors.Is(err, usecase.ErrValidation):
+	case errors.Is(err, promptkit.ErrValidation):
 		return http.StatusInternalServerError, "validation_runtime_failed", "validation runtime failed"
 	default:
 		return http.StatusInternalServerError, "internal_error", "internal server error"
@@ -184,9 +281,23 @@ func mapRunError(err error) (int, string, string) {
 }
 
 func writeJSON(w http.ResponseWriter, status int, v any) {
+	writeLimitedJSON(w, status, v, 0)
+}
+
+func writeLimitedJSON(w http.ResponseWriter, status int, v any, maxBytes int64) {
+	data, err := json.Marshal(v)
+	if err != nil {
+		writeError(w, http.StatusInternalServerError, "internal_error", "internal server error")
+		return
+	}
+	data = append(data, '\n')
+	if maxBytes > 0 && int64(len(data)) > maxBytes {
+		writeError(w, http.StatusRequestEntityTooLarge, "response_too_large", "response body is too large")
+		return
+	}
 	w.Header().Set("Content-Type", "application/json")
 	w.WriteHeader(status)
-	_ = json.NewEncoder(w).Encode(v)
+	_, _ = w.Write(data)
 }
 
 func writeError(w http.ResponseWriter, status int, code, message string) {
@@ -197,3 +308,8 @@ func writeError(w http.ResponseWriter, status int, code, message string) {
 		},
 	})
 }
+
+func isRequestTooLarge(err error) bool {
+	var maxBytesErr *http.MaxBytesError
+	return errors.As(err, &maxBytesErr)
+}

internal/artifact/reader.go

@@ -1,110 +0,0 @@
-package artifact
-
-import (
-	"context"
-	"crypto/sha256"
-	"errors"
-	"fmt"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/defaults"
-	"gitea.maximumdirect.net/eric/scriptorium/internal/domain"
-	"mime"
-	"os"
-	"path/filepath"
-)
-
-var (
-	ErrUnsupportedRefType = errors.New("unsupported artifact reference type")
-	ErrMissingInlineBody  = errors.New("missing body for inline artifact")
-	ErrMissingFilePath    = errors.New("missing file path for file artifact")
-)
-
-// Reader resolves artifact references into actual artifacts.
-type Reader interface {
-	Read(ctx context.Context, ref domain.ArtifactRef) (*domain.Artifact, error)
-}
-
-// CompositeReader routes artifact resolution based on the reference type.
-type CompositeReader struct {
-	inlineReader *inlineReader
-	fileReader   *fileReader
-}
-
-func NewCompositeReader() Reader {
-	return &CompositeReader{
-		inlineReader: &inlineReader{},
-		fileReader:   &fileReader{},
-	}
-}
-
-func (c *CompositeReader) Read(ctx context.Context, ref domain.ArtifactRef) (*domain.Artifact, error) {
-	select {
-	case <-ctx.Done():
-		return nil, ctx.Err()
-	default:
-	}
-
-	switch ref.Type {
-	case domain.ArtifactRefInline:
-		return c.inlineReader.Read(ctx, ref)
-	case domain.ArtifactRefFile:
-		return c.fileReader.Read(ctx, ref)
-	default:
-		return nil, fmt.Errorf("%w: %s", ErrUnsupportedRefType, ref.Type)
-	}
-}
-
-type inlineReader struct{}
-
-func (r *inlineReader) Read(ctx context.Context, ref domain.ArtifactRef) (*domain.Artifact, error) {
-	select {
-	case <-ctx.Done():
-		return nil, ctx.Err()
-	default:
-	}
-
-	if ref.Body == "" {
-		return nil, ErrMissingInlineBody
-	}
-
-	body := []byte(ref.Body)
-	return &domain.Artifact{
-		ContentType: defaults.ContentTypeTextPlain,
-		Body:        body,
-		Size:        int64(len(body)),
-		Hash:        fmt.Sprintf("%x", sha256.Sum256(body)),
-		URI:         ref.URI,
-	}, nil
-}
-
-type fileReader struct{}
-
-func (r *fileReader) Read(ctx context.Context, ref domain.ArtifactRef) (*domain.Artifact, error) {
-	select {
-	case <-ctx.Done():
-		return nil, ctx.Err()
-	default:
-	}
-
-	if ref.URI == "" {
-		return nil, ErrMissingFilePath
-	}
-
-	data, err := os.ReadFile(ref.URI)
-	if err != nil {
-		return nil, fmt.Errorf("failed to read file %s: %w", ref.URI, err)
-	}
-
-	contentType := mime.TypeByExtension(filepath.Ext(ref.URI))
-	if contentType == "" {
-		contentType = defaults.ContentTypeTextPlain
-	}
-
-	return &domain.Artifact{
-		Name:        filepath.Base(ref.URI),
-		ContentType: contentType,
-		Body:        data,
-		URI:         ref.URI,
-		Size:        int64(len(data)),
-		Hash:        fmt.Sprintf("%x", sha256.Sum256(data)),
-	}, nil
-}

internal/artifact/reader_test.go

@@ -1,105 +0,0 @@
-package artifact
-
-import (
-	"context"
-	"errors"
-	"os"
-	"testing"
-
-	"gitea.maximumdirect.net/eric/scriptorium/internal/domain"
-)
-
-func TestCompositeReader_Read(t *testing.T) {
-	reader := NewCompositeReader()
-	ctx := context.Background()
-
-	t.Run("inline artifact", func(t *testing.T) {
-		ref := domain.ArtifactRef{
-			Type: domain.ArtifactRefInline,
-			Body: "hello world",
-		}
-		art, err := reader.Read(ctx, ref)
-		if err != nil {
-			t.Fatalf("unexpected error: %v", err)
-		}
-		if string(art.Body) != "hello world" {
-			t.Errorf("expected 'hello world', got %s", string(art.Body))
-		}
-		if art.ContentType != "text/plain" {
-			t.Errorf("expected text/plain content type, got %q", art.ContentType)
-		}
-		if art.Hash != "b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9" {
-			t.Errorf("unexpected hash: %s", art.Hash)
-		}
-	})
-
-	t.Run("inline artifact missing body", func(t *testing.T) {
-		ref := domain.ArtifactRef{
-			Type: domain.ArtifactRefInline,
-			Body: "",
-		}
-		_, err := reader.Read(ctx, ref)
-		if !errors.Is(err, ErrMissingInlineBody) {
-			t.Errorf("expected ErrMissingInlineBody, got %v", err)
-		}
-	})
-
-	t.Run("unsupported ref type", func(t *testing.T) {
-		ref := domain.ArtifactRef{
-			Type: domain.ArtifactRefS3,
-			URI:  "s3://bucket/key",
-		}
-		_, err := reader.Read(ctx, ref)
-		if !errors.Is(err, ErrUnsupportedRefType) {
-			t.Error("expected error for unsupported type")
-		}
-	})
-}
-
-func TestFileReader_Read(t *testing.T) {
-	content := []byte("test file content")
-	tmpFile, err := os.CreateTemp("", "artifact_test_*.txt")
-	if err != nil {
-		t.Fatal(err)
-	}
-	defer os.Remove(tmpFile.Name())
-
-	if _, err := tmpFile.Write(content); err != nil {
-		t.Fatal(err)
-	}
-	tmpFile.Close()
-
-	reader := NewCompositeReader()
-	ctx := context.Background()
-
-	t.Run("file artifact loading", func(t *testing.T) {
-		ref := domain.ArtifactRef{
-			Type: domain.ArtifactRefFile,
-			URI:  tmpFile.Name(),
-		}
-		art, err := reader.Read(ctx, ref)
-		if err != nil {
-			t.Fatalf("unexpected error: %v", err)
-		}
-		if string(art.Body) != string(content) {
-			t.Errorf("expected %s, got %s", string(content), string(art.Body))
-		}
-		if art.Name == "" {
-			t.Error("expected name to be inferred from filename")
-		}
-		if art.Hash != "60f5237ed4049f0382661ef009d2bc42e48c3ceb3edb6600f7024e7ab3b838f3" {
-			t.Errorf("unexpected hash: %s", art.Hash)
-		}
-	})
-
-	t.Run("missing file path", func(t *testing.T) {
-		ref := domain.ArtifactRef{
-			Type: domain.ArtifactRefFile,
-			URI:  "",
-		}
-		_, err := reader.Read(ctx, ref)
-		if !errors.Is(err, ErrMissingFilePath) {
-			t.Errorf("expected ErrMissingFilePath, got %v", err)
-		}
-	})
-}

internal/config/config.go

@@ -1,193 +0,0 @@
-package config
-
-import (
-	"bytes"
-	"errors"
-	"fmt"
-	"io"
-	"os"
-	"path/filepath"
-	"strings"
-
-	"gitea.maximumdirect.net/eric/scriptorium/internal/defaults"
-	renderformat "gitea.maximumdirect.net/eric/scriptorium/internal/format"
-	"gopkg.in/yaml.v3"
-)
-
-const (
-	DefaultConfigPath      = "/etc/scriptorium/config.yml"
-	DefaultConfigPathLocal = "/usr/local/etc/scriptorium/config.yml"
-)
-
-var defaultConfigSearchPaths = []string{
-	DefaultConfigPathLocal,
-	DefaultConfigPath,
-}
-
-var (
-	ErrConfigNotFound    = errors.New("config file not found")
-	ErrInvalidConfigYAML = errors.New("invalid config YAML")
-	ErrInvalidConfig     = errors.New("invalid config")
-)
-
-// Config is the on-disk YAML shape for application-level settings.
-type Config struct {
-	PromptDir  string         `yaml:"prompt_dir"`
-	ProfileDir string         `yaml:"profile_dir"`
-	SchemaDir  string         `yaml:"schema_dir"`
-	Server     ServerConfig   `yaml:"server"`
-	Defaults   DefaultsConfig `yaml:"defaults"`
-}
-
-type ServerConfig struct {
-	Addr string `yaml:"addr"`
-}
-
-type DefaultsConfig struct {
-	RenderFormat string `yaml:"render_format"`
-}
-
-// AppSettings is the resolved application settings used by adapters.
-type AppSettings struct {
-	PromptDir           string
-	ProfileDir          string
-	SchemaDir           string
-	ServerAddr          string
-	DefaultRenderFormat renderformat.PreparedRunOutputFormat
-}
-
-// CLIOverrides can be applied after config load to enforce precedence.
-type CLIOverrides struct {
-	PromptDir    string
-	ProfileDir   string
-	SchemaDir    string
-	ServerAddr   string
-	RenderFormat string
-}
-
-// BuiltInDefaults returns compile-time application defaults.
-func BuiltInDefaults() AppSettings {
-	return AppSettings{
-		SchemaDir:           defaults.SchemaDirDefault,
-		ServerAddr:          defaults.HTTPAddrDefault,
-		DefaultRenderFormat: renderformat.DefaultPreparedRunOutputFormat,
-	}
-}
-
-// LoadConfig loads and resolves app settings from YAML.
-//
-// If explicit is false and the file does not exist, built-in defaults are returned.
-// If explicit is true, missing file is an error.
-func LoadConfig(path string, explicit bool) (AppSettings, error) {
-	resolved := BuiltInDefaults()
-	configPath := strings.TrimSpace(path)
-	if configPath == "" {
-		if explicit {
-			configPath = DefaultConfigPath
-		} else {
-			for _, candidate := range defaultConfigSearchPaths {
-				if _, err := os.Stat(candidate); err == nil {
-					configPath = candidate
-					break
-				} else if !errors.Is(err, os.ErrNotExist) {
-					return AppSettings{}, fmt.Errorf("failed to stat config file %q: %w", candidate, err)
-				}
-			}
-		}
-	}
-	if configPath == "" {
-		if explicit {
-			return AppSettings{}, fmt.Errorf("%w: %s", ErrConfigNotFound, DefaultConfigPath)
-		}
-		return resolved, nil
-	}
-	configPath = filepath.Clean(configPath)
-
-	raw, err := os.ReadFile(configPath)
-	if err != nil {
-		if errors.Is(err, os.ErrNotExist) {
-			if explicit {
-				return AppSettings{}, fmt.Errorf("%w: %s", ErrConfigNotFound, configPath)
-			}
-			return resolved, nil
-		}
-		return AppSettings{}, fmt.Errorf("failed to read config file %q: %w", configPath, err)
-	}
-
-	cfg, err := decodeConfig(raw)
-	if err != nil {
-		return AppSettings{}, err
-	}
-
-	resolved, err = applyConfig(resolved, cfg)
-	if err != nil {
-		return AppSettings{}, err
-	}
-	return resolved, nil
-}
-
-// ApplyCLIOverrides applies CLI-provided overrides over resolved config settings.
-func ApplyCLIOverrides(base AppSettings, overrides CLIOverrides) (AppSettings, error) {
-	out := base
-
-	if v := strings.TrimSpace(overrides.PromptDir); v != "" {
-		out.PromptDir = filepath.Clean(v)
-	}
-	if v := strings.TrimSpace(overrides.ProfileDir); v != "" {
-		out.ProfileDir = filepath.Clean(v)
-	}
-	if v := strings.TrimSpace(overrides.SchemaDir); v != "" {
-		out.SchemaDir = filepath.Clean(v)
-	}
-	if v := strings.TrimSpace(overrides.ServerAddr); v != "" {
-		out.ServerAddr = v
-	}
-	if rawFormat := strings.TrimSpace(overrides.RenderFormat); rawFormat != "" {
-		parsed, err := renderformat.ParsePreparedRunOutputFormat(rawFormat)
-		if err != nil {
-			return AppSettings{}, fmt.Errorf("%w: defaults.render_format: %v", ErrInvalidConfig, err)
-		}
-		out.DefaultRenderFormat = parsed
-	}
-
-	return out, nil
-}
-
-func decodeConfig(raw []byte) (Config, error) {
-	var cfg Config
-	decoder := yaml.NewDecoder(bytes.NewReader(raw))
-	decoder.KnownFields(true)
-	if err := decoder.Decode(&cfg); err != nil {
-		if errors.Is(err, io.EOF) {
-			return Config{}, nil
-		}
-		return Config{}, fmt.Errorf("%w: %v", ErrInvalidConfigYAML, err)
-	}
-	return cfg, nil
-}
-
-func applyConfig(base AppSettings, cfg Config) (AppSettings, error) {
-	out := base
-
-	if v := strings.TrimSpace(cfg.PromptDir); v != "" {
-		out.PromptDir = filepath.Clean(v)
-	}
-	if v := strings.TrimSpace(cfg.ProfileDir); v != "" {
-		out.ProfileDir = filepath.Clean(v)
-	}
-	if v := strings.TrimSpace(cfg.SchemaDir); v != "" {
-		out.SchemaDir = filepath.Clean(v)
-	}
-	if v := strings.TrimSpace(cfg.Server.Addr); v != "" {
-		out.ServerAddr = v
-	}
-	if rawFormat := strings.TrimSpace(cfg.Defaults.RenderFormat); rawFormat != "" {
-		parsed, err := renderformat.ParsePreparedRunOutputFormat(rawFormat)
-		if err != nil {
-			return AppSettings{}, fmt.Errorf("%w: defaults.render_format: %v", ErrInvalidConfig, err)
-		}
-		out.DefaultRenderFormat = parsed
-	}
-
-	return out, nil
-}

internal/config/config_test.go

@@ -1,236 +0,0 @@
-package config
-
-import (
-	"errors"
-	"os"
-	"path/filepath"
-	"testing"
-
-	renderformat "gitea.maximumdirect.net/eric/scriptorium/internal/format"
-)
-
-func TestLoadConfigMissingImplicitPathUsesBuiltInDefaults(t *testing.T) {
-	tmp := t.TempDir()
-	missing := filepath.Join(tmp, "missing.yml")
-
-	got, err := LoadConfig(missing, false)
-	if err != nil {
-		t.Fatalf("expected no error, got %v", err)
-	}
-
-	want := BuiltInDefaults()
-	if got != want {
-		t.Fatalf("unexpected settings: got=%+v want=%+v", got, want)
-	}
-}
-
-func TestLoadConfigMissingExplicitPathReturnsError(t *testing.T) {
-	tmp := t.TempDir()
-	missing := filepath.Join(tmp, "missing.yml")
-
-	_, err := LoadConfig(missing, true)
-	if err == nil {
-		t.Fatal("expected error for missing explicit config")
-	}
-	if !errors.Is(err, ErrConfigNotFound) {
-		t.Fatalf("expected ErrConfigNotFound, got %v", err)
-	}
-}
-
-func TestLoadConfigInvalidYAMLReturnsError(t *testing.T) {
-	path := writeConfigFile(t, "config.yml", "prompt_dir: [")
-
-	_, err := LoadConfig(path, true)
-	if err == nil {
-		t.Fatal("expected invalid YAML error")
-	}
-	if !errors.Is(err, ErrInvalidConfigYAML) {
-		t.Fatalf("expected ErrInvalidConfigYAML, got %v", err)
-	}
-}
-
-func TestLoadConfigInvalidYAMLImplicitPathReturnsError(t *testing.T) {
-	path := writeConfigFile(t, "config.yml", "prompt_dir: [")
-
-	_, err := LoadConfig(path, false)
-	if err == nil {
-		t.Fatal("expected invalid YAML error")
-	}
-	if !errors.Is(err, ErrInvalidConfigYAML) {
-		t.Fatalf("expected ErrInvalidConfigYAML, got %v", err)
-	}
-}
-
-func TestLoadConfigUnknownFieldReturnsError(t *testing.T) {
-	path := writeConfigFile(t, "config.yml", "unknown_field: true\n")
-
-	_, err := LoadConfig(path, true)
-	if err == nil {
-		t.Fatal("expected unknown field error")
-	}
-	if !errors.Is(err, ErrInvalidConfigYAML) {
-		t.Fatalf("expected ErrInvalidConfigYAML, got %v", err)
-	}
-}
-
-func TestLoadConfigAPIKeyFieldIsRejectedAsUnknown(t *testing.T) {
-	path := writeConfigFile(t, "config.yml", "api_key: secret\n")
-
-	_, err := LoadConfig(path, true)
-	if err == nil {
-		t.Fatal("expected unknown field error for api_key")
-	}
-	if !errors.Is(err, ErrInvalidConfigYAML) {
-		t.Fatalf("expected ErrInvalidConfigYAML, got %v", err)
-	}
-}
-
-func TestLoadConfigValidConfigSetsDirectoriesAndServerAddr(t *testing.T) {
-	path := writeConfigFile(t, "config.yml", `
-prompt_dir: ./prompts
-profile_dir: ./profiles
-schema_dir: ./schemas
-server:
-  addr: 127.0.0.1:9090
-defaults:
-  render_format: json
-`)
-
-	got, err := LoadConfig(path, true)
-	if err != nil {
-		t.Fatalf("expected no error, got %v", err)
-	}
-
-	if got.PromptDir != filepath.Clean("./prompts") {
-		t.Fatalf("unexpected prompt_dir: %q", got.PromptDir)
-	}
-	if got.ProfileDir != filepath.Clean("./profiles") {
-		t.Fatalf("unexpected profile_dir: %q", got.ProfileDir)
-	}
-	if got.SchemaDir != filepath.Clean("./schemas") {
-		t.Fatalf("unexpected schema_dir: %q", got.SchemaDir)
-	}
-	if got.ServerAddr != "127.0.0.1:9090" {
-		t.Fatalf("unexpected server.addr: %q", got.ServerAddr)
-	}
-	if got.DefaultRenderFormat != renderformat.PreparedRunFormatJSON {
-		t.Fatalf("unexpected defaults.render_format: %q", got.DefaultRenderFormat)
-	}
-}
-
-func TestLoadConfigEmptyFileResolvesToBuiltInDefaults(t *testing.T) {
-	path := writeConfigFile(t, "config.yml", "")
-
-	got, err := LoadConfig(path, true)
-	if err != nil {
-		t.Fatalf("expected no error, got %v", err)
-	}
-
-	want := BuiltInDefaults()
-	if got != want {
-		t.Fatalf("unexpected settings: got=%+v want=%+v", got, want)
-	}
-}
-
-func TestLoadConfigImplicitSearchPrefersUsrLocalEtcOverEtc(t *testing.T) {
-	tmp := t.TempDir()
-	localPath := filepath.Join(tmp, "usr-local.yml")
-	etcPath := filepath.Join(tmp, "etc.yml")
-
-	if err := os.WriteFile(localPath, []byte("prompt_dir: ./from-usr-local\n"), 0o644); err != nil {
-		t.Fatal(err)
-	}
-	if err := os.WriteFile(etcPath, []byte("prompt_dir: ./from-etc\n"), 0o644); err != nil {
-		t.Fatal(err)
-	}
-
-	orig := defaultConfigSearchPaths
-	defaultConfigSearchPaths = []string{localPath, etcPath}
-	t.Cleanup(func() { defaultConfigSearchPaths = orig })
-
-	got, err := LoadConfig("", false)
-	if err != nil {
-		t.Fatalf("expected no error, got %v", err)
-	}
-	if got.PromptDir != filepath.Clean("./from-usr-local") {
-		t.Fatalf("expected usr-local config to win, got prompt_dir=%q", got.PromptDir)
-	}
-}
-
-func TestLoadConfigImplicitSearchFallsBackToEtcWhenUsrLocalMissing(t *testing.T) {
-	tmp := t.TempDir()
-	missingLocal := filepath.Join(tmp, "missing-local.yml")
-	etcPath := filepath.Join(tmp, "etc.yml")
-
-	if err := os.WriteFile(etcPath, []byte("prompt_dir: ./from-etc\n"), 0o644); err != nil {
-		t.Fatal(err)
-	}
-
-	orig := defaultConfigSearchPaths
-	defaultConfigSearchPaths = []string{missingLocal, etcPath}
-	t.Cleanup(func() { defaultConfigSearchPaths = orig })
-
-	got, err := LoadConfig("", false)
-	if err != nil {
-		t.Fatalf("expected no error, got %v", err)
-	}
-	if got.PromptDir != filepath.Clean("./from-etc") {
-		t.Fatalf("expected etc fallback config, got prompt_dir=%q", got.PromptDir)
-	}
-}
-
-func TestApplyCLIOverridesAppliesPrecedence(t *testing.T) {
-	base := AppSettings{
-		PromptDir:           "/from/config/prompts",
-		ProfileDir:          "/from/config/profiles",
-		SchemaDir:           "/from/config/schemas",
-		ServerAddr:          ":1234",
-		DefaultRenderFormat: renderformat.PreparedRunFormatJSON,
-	}
-
-	got, err := ApplyCLIOverrides(base, CLIOverrides{
-		PromptDir:    "./prompts-cli",
-		ProfileDir:   "./profiles-cli",
-		SchemaDir:    "./schemas-cli",
-		ServerAddr:   ":8081",
-		RenderFormat: "text",
-	})
-	if err != nil {
-		t.Fatalf("expected no error, got %v", err)
-	}
-
-	if got.PromptDir != filepath.Clean("./prompts-cli") {
-		t.Fatalf("unexpected prompt dir: %q", got.PromptDir)
-	}
-	if got.ProfileDir != filepath.Clean("./profiles-cli") {
-		t.Fatalf("unexpected profile dir: %q", got.ProfileDir)
-	}
-	if got.SchemaDir != filepath.Clean("./schemas-cli") {
-		t.Fatalf("unexpected schema dir: %q", got.SchemaDir)
-	}
-	if got.ServerAddr != ":8081" {
-		t.Fatalf("unexpected server addr: %q", got.ServerAddr)
-	}
-	if got.DefaultRenderFormat != renderformat.PreparedRunFormatText {
-		t.Fatalf("unexpected render format: %q", got.DefaultRenderFormat)
-	}
-}
-
-func TestApplyCLIOverridesInvalidRenderFormatReturnsError(t *testing.T) {
-	_, err := ApplyCLIOverrides(BuiltInDefaults(), CLIOverrides{RenderFormat: "yaml"})
-	if err == nil {
-		t.Fatal("expected invalid render format error")
-	}
-	if !errors.Is(err, ErrInvalidConfig) {
-		t.Fatalf("expected ErrInvalidConfig, got %v", err)
-	}
-}
-
-func writeConfigFile(t *testing.T, name, content string) string {
-	t.Helper()
-	path := filepath.Join(t.TempDir(), name)
-	if err := os.WriteFile(path, []byte(content), 0o644); err != nil {
-		t.Fatalf("failed to write config file: %v", err)
-	}
-	return path
-}

internal/config/document.go

@@ -0,0 +1,109 @@
+package config
+
+import (
+	"path/filepath"
+	"strings"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/scriptorium/internal/defaults"
+	renderformat "gitea.maximumdirect.net/eric/scriptorium/internal/format"
+)
+
+// Document is Scriptorium's ConfigKit-native application configuration shape.
+type Document struct {
+	PromptDir        string                     `yaml:"prompt_dir"`
+	ProfileDir       string                     `yaml:"profile_dir"`
+	SchemaDir        string                     `yaml:"schema_dir"`
+	TransientRetries *int                       `yaml:"transient_retries"`
+	Server           ServerDocument             `yaml:"server"`
+	Defaults         DefaultsDocument           `yaml:"defaults"`
+	Backends         map[string]BackendDocument `yaml:"backends"`
+}
+
+type BackendDocument struct {
+	Endpoint         string         `yaml:"endpoint"`
+	APIKeyEnv        string         `yaml:"api_key_env"`
+	ExtraParams      map[string]any `yaml:"extra_params"`
+	ConcurrencyLimit int            `yaml:"concurrency_limit"`
+	QueueCapacity    *int           `yaml:"queue_capacity"`
+}
+
+type ServerDocument struct {
+	Addr             string `yaml:"addr"`
+	ArtifactRoot     string `yaml:"artifact_root"`
+	MaxRequestBytes  int64  `yaml:"max_request_bytes"`
+	MaxArtifactBytes int64  `yaml:"max_artifact_bytes"`
+	MaxResponseBytes int64  `yaml:"max_response_bytes"`
+}
+
+type DefaultsDocument struct {
+	RenderFormat string `yaml:"render_format"`
+}
+
+func documentDefinition() configkit.Definition[Document] {
+	return configkit.Definition[Document]{
+		Defaults: documentDefaults,
+		Resolve:  resolveDocument,
+		Validate: validateDocument,
+	}
+}
+
+func documentDefaults() Document {
+	return Document{
+		SchemaDir: defaults.SchemaDirDefault,
+		Server: ServerDocument{
+			Addr:             defaults.HTTPAddrDefault,
+			MaxRequestBytes:  defaults.HTTPMaxRequestBytesDefault,
+			MaxArtifactBytes: defaults.HTTPMaxArtifactBytesDefault,
+			MaxResponseBytes: defaults.HTTPMaxResponseBytesDefault,
+		},
+		Defaults: DefaultsDocument{RenderFormat: string(renderformat.DefaultPreparedRunOutputFormat)},
+	}
+}
+
+func resolveDocument(document *Document, resolution *configkit.Resolution) error {
+	normalizePath := func(path configkit.Path, value *string) {
+		cleaned := strings.TrimSpace(*value)
+		if cleaned != "" {
+			cleaned = filepath.Clean(cleaned)
+		}
+		if cleaned != *value {
+			configkit.Normalize(resolution, path, value, cleaned, "normalized application path")
+		}
+	}
+	normalizeString := func(path configkit.Path, value *string, normalized, reason string) {
+		if normalized != *value {
+			configkit.Normalize(resolution, path, value, normalized, reason)
+		}
+	}
+
+	normalizePath(configkit.Keys("prompt_dir"), &document.PromptDir)
+	normalizePath(configkit.Keys("profile_dir"), &document.ProfileDir)
+	normalizePath(configkit.Keys("schema_dir"), &document.SchemaDir)
+	normalizePath(configkit.Keys("server", "artifact_root"), &document.Server.ArtifactRoot)
+	normalizeString(configkit.Keys("server", "addr"), &document.Server.Addr,
+		strings.TrimSpace(document.Server.Addr), "trimmed server address")
+	normalizeString(configkit.Keys("defaults", "render_format"), &document.Defaults.RenderFormat,
+		strings.ToLower(strings.TrimSpace(document.Defaults.RenderFormat)), "normalized render format")
+	return nil
+}
+
+func validateDocument(document *Document, validation *configkit.Validation) {
+	if document.TransientRetries != nil && *document.TransientRetries < 0 {
+		validation.Error(configkit.Keys("transient_retries"), "must be greater than or equal to zero")
+	}
+	if document.Server.MaxRequestBytes < 0 {
+		validation.Error(configkit.Keys("server", "max_request_bytes"), "must be greater than or equal to zero")
+	}
+	if document.Server.MaxArtifactBytes < 0 {
+		validation.Error(configkit.Keys("server", "max_artifact_bytes"), "must be greater than or equal to zero")
+	}
+	if document.Server.MaxResponseBytes < 0 {
+		validation.Error(configkit.Keys("server", "max_response_bytes"), "must be greater than or equal to zero")
+	}
+	switch document.Defaults.RenderFormat {
+	case string(renderformat.OutputFormatText), string(renderformat.OutputFormatJSON):
+	default:
+		validation.Error(configkit.Keys("defaults", "render_format"), "must be text or json")
+	}
+}

internal/config/document_test.go

@@ -0,0 +1,163 @@
+package config
+
+import (
+	"bytes"
+	"errors"
+	"reflect"
+	"strings"
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+func loadDocumentBytes(content string) (*configkit.Result[Document], error) {
+	return configkit.Load(configkit.Bytes("application.yml", []byte(content)), configkit.Options[Document]{
+		Definition: documentDefinition(),
+	})
+}
+
+func TestDocumentDefaultsAndExplicitValues(t *testing.T) {
+	defaultsOnly, err := configkit.Load(configkit.NoSource(), configkit.Options[Document]{Definition: documentDefinition()})
+	if err != nil {
+		t.Fatalf("defaults-only load: %v", err)
+	}
+	if !reflect.DeepEqual(defaultsOnly.Config, documentDefaults()) || len(defaultsOnly.Sources()) != 0 {
+		t.Fatalf("unexpected defaults-only result: %+v sources=%+v", defaultsOnly.Config, defaultsOnly.Sources())
+	}
+
+	result, err := loadDocumentBytes(`prompt_dir: ""
+profile_dir: ""
+schema_dir: ""
+transient_retries: 0
+server:
+  addr: ""
+  artifact_root: ""
+  max_request_bytes: 0
+  max_artifact_bytes: 0
+  max_response_bytes: 0
+defaults:
+  render_format: " JSON "
+backends:
+  local:
+    endpoint: "http://fixture.invalid/v1"
+    queue_capacity: 0
+    extra_params:
+      sample_count: 23
+`)
+	if err != nil {
+		t.Fatalf("explicit-value load: %v", err)
+	}
+	config := result.Config
+	if config.SchemaDir != "" || config.Server.Addr != "" || config.Server.MaxRequestBytes != 0 || config.Server.MaxArtifactBytes != 0 || config.Server.MaxResponseBytes != 0 {
+		t.Fatalf("explicit empty and zero values did not replace defaults: %+v", config)
+	}
+	if config.TransientRetries == nil || *config.TransientRetries != 0 {
+		t.Fatalf("explicit zero retry budget lost: %+v", config.TransientRetries)
+	}
+	if backend := config.Backends["local"]; backend.QueueCapacity == nil || *backend.QueueCapacity != 0 || backend.ExtraParams["sample_count"] != int64(23) {
+		t.Fatalf("backend presence or dynamic integer changed: %+v", backend)
+	}
+	if config.Defaults.RenderFormat != "json" {
+		t.Fatalf("render format normalization failed: %q", config.Defaults.RenderFormat)
+	}
+
+	nullable, err := loadDocumentBytes("transient_retries: null\nbackends:\n  local:\n    queue_capacity: null\n")
+	if err != nil {
+		t.Fatalf("nullable-value load: %v", err)
+	}
+	if nullable.Config.TransientRetries != nil || nullable.Config.Backends["local"].QueueCapacity != nil {
+		t.Fatalf("nullable fields did not remain nil: %+v", nullable.Config)
+	}
+
+	nullBackends, err := loadDocumentBytes("backends: null\n")
+	if err != nil || nullBackends.Config.Backends != nil {
+		t.Fatalf("nullable backend map did not remain nil: %+v error=%v", nullBackends, err)
+	}
+}
+
+func TestDocumentRecordsEffectiveNormalization(t *testing.T) {
+	result, err := loadDocumentBytes(`prompt_dir: "  ./one/../two  "
+profile_dir: "  "
+server:
+  artifact_root: " ./data/../artifacts "
+  addr: "  :9000  "
+defaults:
+  render_format: " JSON "
+`)
+	if err != nil {
+		t.Fatalf("load normalized document: %v", err)
+	}
+	if result.Config.PromptDir != "two" || result.Config.ProfileDir != "" || result.Config.Server.ArtifactRoot != "artifacts" || result.Config.Server.Addr != ":9000" {
+		t.Fatalf("unexpected normalized values: %+v", result.Config)
+	}
+	var effective bytes.Buffer
+	if err := result.WriteEffective(&effective); err != nil {
+		t.Fatalf("write effective configuration: %v", err)
+	}
+	for _, fragment := range []string{"prompt_dir: two", "profile_dir: ''", "artifact_root: artifacts", "addr: :9000", "render_format: json"} {
+		if !strings.Contains(effective.String(), fragment) {
+			t.Fatalf("effective output omitted %q: %s", fragment, effective.String())
+		}
+	}
+	explanation, known := result.Explain(configkit.Keys("prompt_dir"))
+	if !known || explanation.Effective.YAML != "two\n" {
+		t.Fatalf("explanation does not agree with effective value: %+v known=%t", explanation, known)
+	}
+	found := false
+	for _, change := range explanation.History {
+		if change.Origin.Operation == configkit.ChangeNormalization {
+			found = true
+		}
+	}
+	if !found {
+		t.Fatalf("normalization was not recorded: %+v", explanation.History)
+	}
+}
+
+func TestDocumentValidationIsSafeAndPathSpecific(t *testing.T) {
+	for _, tc := range []struct{ name, content, path string }{
+		{"negative retry", "transient_retries: -9173\n", "/transient_retries"},
+		{"negative request limit", "server:\n  max_request_bytes: -9173\n", "/server/max_request_bytes"},
+		{"negative artifact limit", "server:\n  max_artifact_bytes: -9173\n", "/server/max_artifact_bytes"},
+		{"negative response limit", "server:\n  max_response_bytes: -9173\n", "/server/max_response_bytes"},
+		{"empty format", "defaults:\n  render_format: \"\"\n", "/defaults/render_format"},
+		{"unknown format", "defaults:\n  render_format: private-invalid-value\n", "/defaults/render_format"},
+	} {
+		t.Run(tc.name, func(t *testing.T) {
+			_, err := loadDocumentBytes(tc.content)
+			var loadError *configkit.LoadError
+			if !errors.As(err, &loadError) {
+				t.Fatalf("expected typed validation error, got %v", err)
+			}
+			found := false
+			for _, diagnostic := range loadError.Diagnostics() {
+				if diagnostic.Code == configkit.CodeValidateError && diagnostic.Path.String() == tc.path {
+					found = true
+				}
+				if strings.Contains(diagnostic.Message, "9173") || strings.Contains(diagnostic.Message, "private-invalid-value") {
+					t.Fatalf("diagnostic disclosed rejected value: %+v", diagnostic)
+				}
+			}
+			if !found {
+				t.Fatalf("expected validation at %s, got %+v", tc.path, loadError.Diagnostics())
+			}
+		})
+	}
+}
+
+func TestDocumentRejectsNativeShapeErrors(t *testing.T) {
+	for _, content := range []string{
+		"server: null\n",
+		"defaults: null\n",
+		"server:\n  addr: null\n",
+		"server:\n  max_request_bytes: null\n",
+		"defaults:\n  render_format: null\n",
+		"server:\n  unknown_field: 1\n",
+		"backends:\n  local:\n    unknown_field: 1\n",
+	} {
+		_, err := loadDocumentBytes(content)
+		if err == nil {
+			t.Fatalf("unexpected acceptance of %q", content)
+		}
+	}
+}

internal/config/load.go

@@ -0,0 +1,96 @@
+package config
+
+import (
+	"errors"
+	"fmt"
+	"os"
+	"sort"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	renderformat "gitea.maximumdirect.net/eric/scriptorium/internal/format"
+)
+
+// LoadOptions selects one application source and explicit configuration values.
+type LoadOptions struct {
+	Path      string
+	Explicit  bool
+	Overlay   string
+	Overrides []configkit.Override
+}
+
+// Load resolves one ConfigKit document and retains its inspection snapshot.
+func Load(options LoadOptions) (*configkit.Result[Document], error) {
+	var source configkit.Source
+	fileBacked := false
+	if options.Explicit {
+		source = configkit.File(options.Path)
+		fileBacked = true
+	} else {
+		selected := ""
+		for _, candidate := range defaultConfigSearchPaths {
+			if _, err := os.Stat(candidate); err == nil {
+				selected = candidate
+				break
+			} else if !errors.Is(err, os.ErrNotExist) {
+				reason := "filesystem error"
+				if errors.Is(err, os.ErrPermission) {
+					reason = "permission denied"
+				}
+				return nil, fmt.Errorf("cannot inspect configuration path %q: %s", candidate, reason)
+			}
+		}
+		if selected == "" {
+			source = configkit.NoSource()
+		} else {
+			source = configkit.File(selected)
+			fileBacked = true
+		}
+	}
+
+	result, err := configkit.Load(source, configkit.Options[Document]{
+		Definition: documentDefinition(),
+		Imports:    fileBacked,
+		Overlay:    options.Overlay,
+		Overrides:  options.Overrides,
+	})
+	if err != nil {
+		return nil, fmt.Errorf("load application configuration: %w", err)
+	}
+	return result, nil
+}
+
+// Settings converts a validated document without another merge or normalization.
+func Settings(document Document) AppSettings {
+	settings := AppSettings{
+		PromptDir:           document.PromptDir,
+		ProfileDir:          document.ProfileDir,
+		SchemaDir:           document.SchemaDir,
+		ServerAddr:          document.Server.Addr,
+		ArtifactRoot:        document.Server.ArtifactRoot,
+		MaxRequestBytes:     document.Server.MaxRequestBytes,
+		MaxArtifactBytes:    document.Server.MaxArtifactBytes,
+		MaxResponseBytes:    document.Server.MaxResponseBytes,
+		DefaultRenderFormat: renderformat.PreparedRunOutputFormat(document.Defaults.RenderFormat),
+		TransientRetries:    document.TransientRetries,
+	}
+	if document.Backends != nil {
+		ids := make([]string, 0, len(document.Backends))
+		for id := range document.Backends {
+			ids = append(ids, id)
+		}
+		sort.Strings(ids)
+		settings.Backends = make([]BackendSettings, 0, len(ids))
+		for _, id := range ids {
+			backend := document.Backends[id]
+			settings.Backends = append(settings.Backends, BackendSettings{
+				ID:               id,
+				Endpoint:         backend.Endpoint,
+				APIKeyEnv:        backend.APIKeyEnv,
+				ExtraParams:      backend.ExtraParams,
+				ConcurrencyLimit: backend.ConcurrencyLimit,
+				QueueCapacity:    backend.QueueCapacity,
+			})
+		}
+	}
+	return settings
+}

internal/config/load_test.go

@@ -0,0 +1,233 @@
+package config
+
+import (
+	"errors"
+	"os"
+	"path/filepath"
+	"reflect"
+	"strings"
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+func useConfigSearchPaths(t *testing.T, paths ...string) {
+	t.Helper()
+	previous := defaultConfigSearchPaths
+	defaultConfigSearchPaths = paths
+	t.Cleanup(func() { defaultConfigSearchPaths = previous })
+}
+
+func writeApplicationFile(t *testing.T, path, body string) {
+	t.Helper()
+	if err := os.WriteFile(path, []byte(body), 0o600); err != nil {
+		t.Fatal(err)
+	}
+}
+
+func TestLoadSelectsOrderedSourceAndKeepsItsSnapshot(t *testing.T) {
+	dir := t.TempDir()
+	first := filepath.Join(dir, "first.yml")
+	second := filepath.Join(dir, "second.yml")
+	writeApplicationFile(t, first, "prompt_dir: ./first\n")
+	writeApplicationFile(t, second, "prompt_dir: ./second\n")
+	useConfigSearchPaths(t, first, second)
+
+	result, err := Load(LoadOptions{Path: filepath.Join(dir, "ignored.yml")})
+	if err != nil {
+		t.Fatalf("load first implicit source: %v", err)
+	}
+	if result.Config.PromptDir != "first" || len(result.Sources()) != 1 || result.Sources()[0].Path != first {
+		t.Fatalf("unexpected implicit source: config=%+v sources=%+v", result.Config, result.Sources())
+	}
+	writeApplicationFile(t, first, "prompt_dir: ./changed\n")
+	if result.Config.PromptDir != "first" {
+		t.Fatalf("result did not retain resolved snapshot: %+v", result.Config)
+	}
+
+	if err := os.Remove(first); err != nil {
+		t.Fatal(err)
+	}
+	result, err = Load(LoadOptions{})
+	if err != nil || result.Config.PromptDir != "second" || result.Sources()[0].Path != second {
+		t.Fatalf("second implicit source not selected: result=%+v err=%v", result, err)
+	}
+
+	result, err = Load(LoadOptions{Path: first, Explicit: true})
+	if result != nil || err == nil {
+		t.Fatalf("missing explicit source was accepted: result=%+v err=%v", result, err)
+	}
+	var loadError *configkit.LoadError
+	if !errors.As(err, &loadError) {
+		t.Fatalf("typed load error was lost: %v", err)
+	}
+}
+
+func TestLoadRejectsExplicitEmptyAndDistinguishesEmptyFile(t *testing.T) {
+	useConfigSearchPaths(t, filepath.Join(t.TempDir(), "absent.yml"))
+	if _, err := Load(LoadOptions{Explicit: true, Path: ""}); err == nil {
+		t.Fatal("explicit empty path was accepted")
+	} else {
+		var loadError *configkit.LoadError
+		if !errors.As(err, &loadError) {
+			t.Fatalf("expected upstream source diagnostic, got %v", err)
+		}
+	}
+
+	dir := t.TempDir()
+	empty := filepath.Join(dir, "empty.yml")
+	writeApplicationFile(t, empty, "")
+	if _, err := Load(LoadOptions{Path: empty, Explicit: true}); err == nil {
+		t.Fatal("empty file was treated as defaults-only")
+	}
+	writeApplicationFile(t, empty, "{}\n")
+	result, err := Load(LoadOptions{Path: empty, Explicit: true})
+	if err != nil || !reflect.DeepEqual(result.Config, documentDefaults()) {
+		t.Fatalf("empty mapping did not load defaults: result=%+v err=%v", result, err)
+	}
+}
+
+func TestLoadDefaultsOnlyAndOverridesBeforeValidation(t *testing.T) {
+	useConfigSearchPaths(t, filepath.Join(t.TempDir(), "absent.yml"))
+	result, err := Load(LoadOptions{})
+	if err != nil || !reflect.DeepEqual(result.Config, documentDefaults()) || len(result.Sources()) != 0 {
+		t.Fatalf("defaults-only load: result=%+v err=%v", result, err)
+	}
+	var effective strings.Builder
+	if err := result.WriteEffective(&effective); err != nil || !strings.Contains(effective.String(), "render_format: text") || len(result.Sources()) != 0 {
+		t.Fatalf("defaults-only inspection changed: effective=%q err=%v sources=%+v", effective.String(), err, result.Sources())
+	}
+
+	result, err = Load(LoadOptions{Overrides: []configkit.Override{{
+		Path: configkit.Keys("server", "max_request_bytes"), Value: int64(0), Flag: "--max-request-bytes",
+	}}})
+	if err != nil || result.Config.Server.MaxRequestBytes != 0 || len(result.Sources()) != 1 || result.Sources()[0].Layer != configkit.LayerCLI {
+		t.Fatalf("defaults-only override lost: result=%+v err=%v", result, err)
+	}
+
+	path := filepath.Join(t.TempDir(), "invalid.yml")
+	writeApplicationFile(t, path, "defaults:\n  render_format: invalid-choice\n")
+	result, err = Load(LoadOptions{Path: path, Explicit: true, Overrides: []configkit.Override{{
+		Path: configkit.Keys("defaults", "render_format"), Value: "json", Flag: "--render-format",
+	}}})
+	if err != nil || result.Config.Defaults.RenderFormat != "json" {
+		t.Fatalf("override did not precede validation: result=%+v err=%v", result, err)
+	}
+	if len(result.Sources()) != 2 || result.Sources()[0].Layer != configkit.LayerBase || result.Sources()[1].Layer != configkit.LayerCLI {
+		t.Fatalf("source order changed: %+v", result.Sources())
+	}
+	writeApplicationFile(t, path, "defaults: [\n")
+	if _, err := Load(LoadOptions{Path: path, Explicit: true, Overrides: []configkit.Override{{
+		Path: configkit.Keys("defaults", "render_format"), Value: "json", Flag: "--render-format",
+	}}}); err == nil {
+		t.Fatal("override bypassed malformed lower-level YAML")
+	}
+}
+
+func TestSettingsCopiesResolvedValuesAndSortsBackends(t *testing.T) {
+	result, err := loadDocumentBytes(`schema_dir: ""
+transient_retries: 0
+server:
+  addr: ""
+  artifact_root: ""
+  max_request_bytes: 0
+defaults:
+  render_format: json
+backends:
+  zed:
+    endpoint: http://zed.invalid/v1
+    extra_params:
+      count: 4
+  alpha:
+    queue_capacity: 0
+`)
+	if err != nil {
+		t.Fatal(err)
+	}
+	settings := Settings(result.Config)
+	if settings.SchemaDir != "" || settings.ServerAddr != "" || settings.MaxRequestBytes != 0 || settings.DefaultRenderFormat != "json" {
+		t.Fatalf("resolved scalar values changed: %+v", settings)
+	}
+	if settings.TransientRetries == nil || *settings.TransientRetries != 0 {
+		t.Fatalf("retry presence lost: %+v", settings.TransientRetries)
+	}
+	if len(settings.Backends) != 2 || settings.Backends[0].ID != "alpha" || settings.Backends[1].ID != "zed" {
+		t.Fatalf("backend order changed: %+v", settings.Backends)
+	}
+	if settings.Backends[0].QueueCapacity == nil || *settings.Backends[0].QueueCapacity != 0 || settings.Backends[1].QueueCapacity != nil {
+		t.Fatalf("queue presence changed: %+v", settings.Backends)
+	}
+	if value := settings.Backends[1].ExtraParams["count"]; value != int64(4) {
+		t.Fatalf("dynamic number changed shape: %T %v", value, value)
+	}
+
+	if got := Settings(documentDefaults()); got.TransientRetries != nil || got.Backends != nil {
+		t.Fatalf("default nullable values changed: %+v", got)
+	}
+}
+
+func TestLoadDiscoveryErrorQuotesPath(t *testing.T) {
+	dir := t.TempDir()
+	loop := filepath.Join(dir, "loop-\n.yml")
+	if err := os.Symlink(loop, loop); err != nil {
+		t.Skipf("symlink unavailable: %v", err)
+	}
+	useConfigSearchPaths(t, loop)
+	_, err := Load(LoadOptions{})
+	if err == nil || !strings.Contains(err.Error(), `\n`) || strings.Contains(err.Error(), "loop-\n.yml") {
+		t.Fatalf("discovery error did not quote path safely: %v", err)
+	}
+}
+
+func TestLoadComposesExplicitImportsAndSelectedOverlay(t *testing.T) {
+	dir := t.TempDir()
+	if err := os.MkdirAll(filepath.Join(dir, "fragments"), 0o700); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.MkdirAll(filepath.Join(dir, "overlays"), 0o700); err != nil {
+		t.Fatal(err)
+	}
+	base := filepath.Join(dir, "config.yml")
+	writeApplicationFile(t, base, "configkit:\n  imports:\n    - glob: fragments/*.yml\nprompt_dir: ./base-prompts\nserver:\n  addr: :8081\n")
+	writeApplicationFile(t, filepath.Join(dir, "fragments", "a.yml"), "backends:\n  alpha:\n    endpoint: http://alpha.invalid/v1\n")
+	writeApplicationFile(t, filepath.Join(dir, "fragments", "b.yml"), "backends:\n  beta:\n    endpoint: http://beta.invalid/v1\n")
+	writeApplicationFile(t, filepath.Join(dir, "overlays", "local.yml"), "prompt_dir: ./overlay-prompts\nserver:\n  addr: :9090\n")
+
+	result, err := Load(LoadOptions{Path: base, Explicit: true})
+	if err != nil || result.Config.PromptDir != "base-prompts" || len(result.Config.Backends) != 2 || len(result.Sources()) != 3 {
+		t.Fatalf("disjoint imports did not compose: result=%+v err=%v", result, err)
+	}
+	result, err = Load(LoadOptions{Path: base, Explicit: true, Overlay: "local", Overrides: []configkit.Override{{
+		Path: configkit.Keys("server", "addr"), Value: ":7070", Flag: "--addr",
+	}}})
+	if err != nil || result.Config.PromptDir != "overlay-prompts" || result.Config.Server.Addr != ":7070" || len(result.Sources()) != 5 {
+		t.Fatalf("overlay or explicit override changed: result=%+v err=%v", result, err)
+	}
+	if _, err := Load(LoadOptions{Path: base, Explicit: true, Overlay: "missing"}); err == nil {
+		t.Fatal("missing selected overlay accepted")
+	}
+	writeApplicationFile(t, filepath.Join(dir, "fragments", "b.yml"), "backends:\n  alpha:\n    endpoint: http://conflict.invalid/v1\n")
+	if _, err := Load(LoadOptions{Path: base, Explicit: true}); err == nil {
+		t.Fatal("conflicting import accepted")
+	} else {
+		var loadError *configkit.LoadError
+		if !errors.As(err, &loadError) {
+			t.Fatalf("conflict lost structured diagnostic: %v", err)
+		}
+	}
+}
+
+func TestLoadRejectsOverlayWithoutBase(t *testing.T) {
+	useConfigSearchPaths(t, filepath.Join(t.TempDir(), "absent.yml"))
+	if _, err := Load(LoadOptions{Overlay: "local"}); err == nil {
+		t.Fatal("overlay without base accepted")
+	} else {
+		var loadError *configkit.LoadError
+		if !errors.As(err, &loadError) {
+			t.Fatalf("no-base overlay lost structured diagnostic: %v", err)
+		}
+	}
+	if _, err := Load(LoadOptions{Overlay: "default"}); err != nil {
+		t.Fatalf("default must select no overlay: %v", err)
+	}
+}

internal/config/settings.go

@@ -0,0 +1,37 @@
+package config
+
+import renderformat "gitea.maximumdirect.net/eric/scriptorium/internal/format"
+
+const (
+	DefaultConfigPath      = "/etc/scriptorium/config.yml"
+	DefaultConfigPathLocal = "/usr/local/etc/scriptorium/config.yml"
+)
+
+var defaultConfigSearchPaths = []string{
+	DefaultConfigPathLocal,
+	DefaultConfigPath,
+}
+
+// AppSettings holds the validated application values used by executable adapters.
+type AppSettings struct {
+	PromptDir           string
+	ProfileDir          string
+	SchemaDir           string
+	ServerAddr          string
+	ArtifactRoot        string
+	MaxRequestBytes     int64
+	MaxArtifactBytes    int64
+	MaxResponseBytes    int64
+	DefaultRenderFormat renderformat.PreparedRunOutputFormat
+	Backends            []BackendSettings
+	TransientRetries    *int
+}
+
+type BackendSettings struct {
+	ID               string
+	Endpoint         string
+	APIKeyEnv        string
+	ExtraParams      map[string]any
+	ConcurrencyLimit int
+	QueueCapacity    *int
+}

internal/defaults/defaults.go

@@ -1,36 +1,13 @@
 package defaults
 
-import (
-	"time"
-
-	"gitea.maximumdirect.net/eric/scriptorium/internal/domain"
-)
+import "time"
 
 const (
-	HTTPAddrDefault            = ":8080"
-	SchemaDirDefault           = "."
-	OutputArtifactName         = "output"
-	ContentTypeTextPlain       = "text/plain"
-	ContentTypeTextMarkdown    = "text/markdown"
-	ContentTypeApplicationJSON = "application/json"
-	OpenAIChatCompletionsPath  = "/chat/completions"
-
-	ExecutionDefaultTemperature    = 0.0
-	ExecutionDefaultMaxTokens      = 0
-	ExecutionDefaultTopP           = 1.0
-	ExecutionDefaultTimeoutSeconds = 600
+	HTTPAddrDefault             = ":8080"
+	SchemaDirDefault            = "."
+	HTTPMaxRequestBytesDefault  = 16 * 1024 * 1024
+	HTTPMaxArtifactBytesDefault = 16 * 1024 * 1024
+	HTTPMaxResponseBytesDefault = 16 * 1024 * 1024
 )
 
-var (
-	LLMRequestTimeoutDefault     = 10 * time.Minute
-	HTTPReadHeaderTimeoutDefault = 10 * time.Second
-)
-
-func ExecutionTargetDefault() domain.ExecutionTarget {
-	return domain.ExecutionTarget{
-		Temperature:    ExecutionDefaultTemperature,
-		MaxTokens:      ExecutionDefaultMaxTokens,
-		TopP:           ExecutionDefaultTopP,
-		TimeoutSeconds: ExecutionDefaultTimeoutSeconds,
-	}
-}
+var HTTPReadHeaderTimeoutDefault = 10 * time.Second

internal/domain/domain.go

@@ -1,254 +0,0 @@
-package domain
-
-import (
-	"time"
-)
-
-// ArtifactRefType defines how an artifact is referenced.
-type ArtifactRefType string
-
-const (
-	ArtifactRefInline ArtifactRefType = "inline"
-	ArtifactRefFile   ArtifactRefType = "file"
-	ArtifactRefS3     ArtifactRefType = "s3"
-)
-
-// OutputFormat defines the desired format of the generated artifact.
-type OutputFormat string
-
-const (
-	FormatText     OutputFormat = "text"
-	FormatMarkdown OutputFormat = "markdown"
-	FormatJSON     OutputFormat = "json"
-)
-
-// ValidationMode defines how the output should be validated.
-type ValidationMode string
-
-const (
-	ValidationNone       ValidationMode = "none"
-	ValidationBasic      ValidationMode = "basic"
-	ValidationJSON       ValidationMode = "json"
-	ValidationJSONSchema ValidationMode = "json_schema"
-)
-
-// ValidationStatus defines the result of a validation check.
-type ValidationStatus string
-
-const (
-	ValidationPassed  ValidationStatus = "passed"
-	ValidationFailed  ValidationStatus = "failed"
-	ValidationSkipped ValidationStatus = "skipped"
-)
-
-// RunRequest represents a request to generate a single artifact.
-type RunRequest struct {
-	PromptID      string
-	PromptVersion string
-	ProfileID     string
-	Inputs        map[string]ArtifactRef
-	Vars          map[string]string
-	Execution     *ExecutionTarget
-	Validation    *OutputContract
-	Metadata      map[string]string
-}
-
-// RunResult represents the complete result of a prompt execution run.
-type RunResult struct {
-	RunID                string
-	Artifact             Artifact
-	RawOutput            string
-	Validation           ValidationResult
-	PromptID             string
-	PromptVersion        string
-	PromptHash           string
-	RenderedPromptHash   string
-	SelectedProfileID    string
-	ModelName            string
-	Endpoint             string
-	EffectiveModelParams ExecutionTarget
-	InputHashes          map[string]string
-	Usage                TokenUsage
-	StartTime            time.Time
-	EndTime              time.Time
-	Duration             time.Duration
-	Error                error
-}
-
-// PreparedRun contains pre-LLM execution state from the prepare/render phase.
-// It must never include resolved API key values, model output, or validation data.
-type PreparedRun struct {
-	PromptID             string                `json:"prompt_id"`
-	PromptVersion        string                `json:"prompt_version,omitempty"`
-	PromptHash           string                `json:"prompt_hash,omitempty"`
-	SelectedProfileID    string                `json:"selected_profile_id"`
-	EffectiveModelParams ExecutionTarget       `json:"effective_model_params"`
-	OutputContract       OutputContract        `json:"output_contract"`
-	StructuredOutput     *StructuredOutputSpec `json:"structured_output,omitempty"`
-	InputHashes          map[string]string     `json:"input_hashes,omitempty"`
-	RenderedPromptHash   string                `json:"rendered_prompt_hash"`
-	Messages             []RenderedMessage     `json:"messages"`
-	StartTime            time.Time             `json:"start_time,omitempty"`
-	EndTime              time.Time             `json:"end_time,omitempty"`
-	DurationMS           int64                 `json:"duration_ms,omitempty"`
-}
-
-// ArtifactRef represents a reference to an input artifact.
-type ArtifactRef struct {
-	Type ArtifactRefType
-	URI  string
-	Body string // Used for inline
-}
-
-// Artifact represents the actual loaded content of a reference.
-type Artifact struct {
-	Name        string
-	ContentType string
-	Body        []byte
-	URI         string
-	Size        int64
-	Hash        string
-}
-
-// PromptDefinition represents a configured prompt execution definition.
-type PromptDefinition struct {
-	ID             string                  `yaml:"id"`
-	Version        string                  `yaml:"version"`
-	DefaultProfile string                  `yaml:"default_profile"`
-	Description    string                  `yaml:"description"`
-	Inputs         []PromptInput           `yaml:"inputs"`
-	Templates      []PromptMessageTemplate `yaml:"templates"`
-	OutputFormat   OutputFormat            `yaml:"output_format"`
-	Validation     OutputContract          `yaml:"validation"`
-}
-
-// PromptInput describes one named input expected by a prompt definition.
-type PromptInput struct {
-	Name        string `yaml:"name"`
-	Required    bool   `yaml:"required"`
-	ContentType string `yaml:"content_type"`
-	Description string `yaml:"description"`
-}
-
-// PromptMessageTemplate defines a template for a chat message.
-type PromptMessageTemplate struct {
-	Role        string `yaml:"role"`
-	Content     string `yaml:"content"`
-	ContentFile string `yaml:"content_file"`
-}
-
-// ExecutionProfile describes how and where to execute a model.
-type ExecutionProfile struct {
-	ID              string            `yaml:"id"`
-	Endpoint        string            `yaml:"endpoint"`
-	Model           string            `yaml:"model"`
-	Temperature     float64           `yaml:"temperature"`
-	MaxTokens       int               `yaml:"max_tokens"`
-	TopP            float64           `yaml:"top_p"`
-	TimeoutSeconds  int               `yaml:"timeout_seconds"`
-	ReasoningEffort string            `yaml:"reasoning_effort"`
-	APIKeyEnv       string            `yaml:"api_key_env"`
-	ExtraParams     map[string]string `yaml:"extra_params"`
-}
-
-// ExecutionTarget represents effective model runtime settings for a run.
-type ExecutionTarget struct {
-	Endpoint        string            `yaml:"endpoint" json:"endpoint"`
-	Model           string            `yaml:"model" json:"model"`
-	Temperature     float64           `yaml:"temperature" json:"temperature"`
-	MaxTokens       int               `yaml:"max_tokens" json:"max_tokens"`
-	TopP            float64           `yaml:"top_p" json:"top_p"`
-	TimeoutSeconds  int               `yaml:"timeout_seconds" json:"timeout_seconds"`
-	ReasoningEffort string            `yaml:"reasoning_effort" json:"reasoning_effort"`
-	APIKeyEnv       string            `yaml:"api_key_env" json:"api_key_env"`
-	ExtraParams     map[string]string `yaml:"extra_params" json:"extra_params"`
-}
-
-// OutputContract defines the requirements for the output artifact.
-type OutputContract struct {
-	Format         OutputFormat   `yaml:"format"`
-	ValidationMode ValidationMode `yaml:"validation_mode"`
-	SchemaPath     string         `yaml:"schema_path"`
-	RepairAttempts int            `yaml:"repair_attempts"`
-}
-
-// RenderedPrompt represents the prompt after template application.
-type RenderedPrompt struct {
-	Messages []RenderedMessage `json:"messages"`
-}
-
-// RenderedMessage is a single message in a rendered prompt.
-type RenderedMessage struct {
-	Role    string `json:"role"`
-	Content string `json:"content"`
-}
-
-// GenerateRequest is the internal request passed to the LLM client.
-type GenerateRequest struct {
-	Prompt           RenderedPrompt
-	Target           ExecutionTarget
-	StructuredOutput *StructuredOutputSpec
-}
-
-// StructuredOutputType indicates which provider-level output mode is requested.
-type StructuredOutputType string
-
-const (
-	StructuredOutputJSONSchema StructuredOutputType = "json_schema"
-)
-
-// StructuredOutputSpec describes provider-level structured output requirements.
-type StructuredOutputSpec struct {
-	Type       StructuredOutputType      `json:"type"`
-	JSONSchema *StructuredOutputJSONSpec `json:"json_schema,omitempty"`
-}
-
-// StructuredOutputJSONSpec contains json_schema output constraints.
-type StructuredOutputJSONSpec struct {
-	Name   string `json:"name"`
-	Strict bool   `json:"strict"`
-	Schema any    `json:"schema"`
-}
-
-// GenerateResponse is the response received from the LLM client.
-type GenerateResponse struct {
-	Content string
-	Usage   TokenUsage
-}
-
-// TokenUsage tracks token consumption.
-type TokenUsage struct {
-	PromptTokens     int
-	CompletionTokens int
-	TotalTokens      int
-}
-
-// ValidationResult represents the outcome of an output validation.
-type ValidationResult struct {
-	Status         ValidationStatus
-	Mode           ValidationMode
-	Errors         []string
-	SchemaPath     string
-	RepairAttempts int
-	IsValid        bool
-}
-
-// RunMetadata contains auditing information for a run.
-type RunMetadata struct {
-	RunID              string
-	PromptID           string
-	PromptVersion      string
-	PromptHash         string
-	RenderedPromptHash string
-	SelectedProfileID  string
-	InputHashes        map[string]string
-	ModelEndpoint      string
-	ModelName          string
-	Params             ExecutionTarget
-	Timestamp          time.Time
-	Duration           time.Duration
-	Usage              TokenUsage
-	ValidationMode     ValidationMode
-	ValidationStatus   ValidationStatus
-	RepairAttempts     int
-}

internal/domain/prepared_run_test.go

@@ -1,55 +0,0 @@
-package domain
-
-import (
-	"encoding/json"
-	"strings"
-	"testing"
-)
-
-func TestPreparedRunJSONDoesNotIncludeSecretValues(t *testing.T) {
-	const envName = "SCRIPTORIUM_TEST_API_KEY"
-	const secret = "super-secret-value"
-	t.Setenv(envName, secret)
-
-	prepared := PreparedRun{
-		PromptID:          "prompt.id",
-		PromptVersion:     "v1",
-		PromptHash:        "prompt-hash",
-		SelectedProfileID: "local-fast",
-		EffectiveModelParams: ExecutionTarget{
-			Endpoint:  "http://llm/v1",
-			Model:     "gpt-test",
-			APIKeyEnv: envName,
-		},
-		InputHashes:        map[string]string{"transcript": "hash-1"},
-		RenderedPromptHash: "rendered-hash",
-		Messages: []RenderedMessage{
-			{Role: "system", Content: "You are helpful."},
-			{Role: "user", Content: "Summarize this."},
-		},
-	}
-
-	b, err := json.Marshal(prepared)
-	if err != nil {
-		t.Fatalf("marshal failed: %v", err)
-	}
-
-	out := string(b)
-	if strings.Contains(out, secret) {
-		t.Fatalf("prepared run JSON unexpectedly contains secret value: %s", out)
-	}
-	if !strings.Contains(out, `"api_key_env":"`+envName+`"`) {
-		t.Fatalf("prepared run JSON should include api_key_env name: %s", out)
-	}
-
-	var top map[string]any
-	if err := json.Unmarshal(b, &top); err != nil {
-		t.Fatalf("unmarshal failed: %v", err)
-	}
-
-	for _, forbidden := range []string{"raw_output", "validation", "artifact"} {
-		if _, ok := top[forbidden]; ok {
-			t.Fatalf("prepared run JSON should not include %q", forbidden)
-		}
-	}
-}

internal/format/inspection.go

@@ -0,0 +1,122 @@
+package format
+
+import (
+	"bytes"
+	"encoding/json"
+	"errors"
+	"fmt"
+	"strconv"
+
+	"gitea.maximumdirect.net/eric/promptkit"
+)
+
+type PromptInspection struct {
+	PromptID         string                  `json:"prompt_id"`
+	PromptVersion    string                  `json:"prompt_version"`
+	PromptHash       string                  `json:"prompt_hash"`
+	DefaultProfileID string                  `json:"default_profile_id"`
+	Inputs           []PromptInspectionInput `json:"inputs"`
+	OutputContract   OutputContract          `json:"output_contract"`
+}
+
+type PromptInspectionInput struct {
+	Name        string `json:"name"`
+	Required    bool   `json:"required"`
+	ContentType string `json:"content_type"`
+	Description string `json:"description"`
+}
+
+type OutputContract struct {
+	Format         string `json:"format"`
+	ValidationMode string `json:"validation_mode"`
+	SchemaPath     string `json:"schema_path"`
+	RepairAttempts int    `json:"repair_attempts"`
+}
+
+type ProfileInspection struct {
+	ProfileID            string             `json:"profile_id"`
+	EffectiveModelParams ProfileModelParams `json:"effective_model_params"`
+	APIKeyRequired       bool               `json:"api_key_required"`
+}
+
+type ProfileModelParams struct {
+	BackendID       string         `json:"backend_id"`
+	Endpoint        string         `json:"endpoint"`
+	Model           string         `json:"model"`
+	Temperature     float64        `json:"temperature"`
+	MaxTokens       int            `json:"max_tokens"`
+	TopP            float64        `json:"top_p"`
+	TimeoutSeconds  int            `json:"timeout_seconds"`
+	ServiceTier     string         `json:"service_tier"`
+	ReasoningEffort string         `json:"reasoning_effort"`
+	APIKeyEnv       string         `json:"api_key_env"`
+	ExtraParams     map[string]any `json:"extra_params"`
+}
+
+func FormatPromptInspection(value *promptkit.PromptInspection, outputFormat OutputFormat) ([]byte, error) {
+	if value == nil {
+		return nil, errors.New("prompt inspection is nil")
+	}
+	dto := PromptInspection{
+		PromptID: value.PromptID, PromptVersion: value.PromptVersion, PromptHash: value.PromptHash, DefaultProfileID: value.DefaultProfileID,
+		Inputs:         make([]PromptInspectionInput, len(value.Inputs)),
+		OutputContract: OutputContract{Format: string(value.OutputContract.Format), ValidationMode: string(value.OutputContract.ValidationMode), SchemaPath: value.OutputContract.SchemaPath, RepairAttempts: value.OutputContract.RepairAttempts},
+	}
+	for i, input := range value.Inputs {
+		dto.Inputs[i] = PromptInspectionInput{Name: input.Name, Required: input.Required, ContentType: input.ContentType, Description: input.Description}
+	}
+	switch outputFormat {
+	case OutputFormatJSON:
+		data, err := json.MarshalIndent(dto, "", "  ")
+		if err != nil {
+			return nil, err
+		}
+		return append(data, '\n'), nil
+	case OutputFormatText:
+		var b bytes.Buffer
+		fmt.Fprintf(&b, "prompt_id: %s\nprompt_version: %s\nprompt_hash: %s\ndefault_profile_id: %s\ninputs:", dto.PromptID, dto.PromptVersion, dto.PromptHash, dto.DefaultProfileID)
+		if len(dto.Inputs) == 0 {
+			fmt.Fprintln(&b, " []")
+		} else {
+			fmt.Fprintln(&b)
+			for _, input := range dto.Inputs {
+				fmt.Fprintf(&b, "  - name: %s\n    required: %t\n    content_type: %s\n    description: %s\n", input.Name, input.Required, input.ContentType, strconv.Quote(input.Description))
+			}
+		}
+		fmt.Fprintf(&b, "output_contract:\n  format: %s\n  validation_mode: %s\n  schema_path: %s\n  repair_attempts: %d\n", dto.OutputContract.Format, dto.OutputContract.ValidationMode, dto.OutputContract.SchemaPath, dto.OutputContract.RepairAttempts)
+		return b.Bytes(), nil
+	default:
+		return nil, fmt.Errorf("%w: %q", ErrUnknownPreparedRunFormat, outputFormat)
+	}
+}
+
+func FormatProfileInspection(value *promptkit.ProfileInspection, outputFormat OutputFormat) ([]byte, error) {
+	if value == nil {
+		return nil, errors.New("profile inspection is nil")
+	}
+	target := value.EffectiveModelParams
+	params := map[string]any{}
+	for key, item := range target.ExtraParams {
+		params[key] = item
+	}
+	dto := ProfileInspection{ProfileID: value.ProfileID, APIKeyRequired: value.APIKeyRequired, EffectiveModelParams: ProfileModelParams{BackendID: target.BackendID, Endpoint: target.Endpoint, Model: target.Model, Temperature: target.Temperature, MaxTokens: target.MaxTokens, TopP: target.TopP, TimeoutSeconds: target.TimeoutSeconds, ServiceTier: target.ServiceTier, ReasoningEffort: target.ReasoningEffort, APIKeyEnv: target.APIKeyEnv, ExtraParams: params}}
+	switch outputFormat {
+	case OutputFormatJSON:
+		data, err := json.MarshalIndent(dto, "", "  ")
+		if err != nil {
+			return nil, err
+		}
+		return append(data, '\n'), nil
+	case OutputFormatText:
+		var b bytes.Buffer
+		fmt.Fprintf(&b, "profile_id: %s\neffective_model_params:\n  backend_id: %s\n  endpoint: %s\n  model: %s\n  temperature: %g\n  max_tokens: %d\n  top_p: %g\n  timeout_seconds: %d\n  service_tier: %s\n  reasoning_effort: %s\n  api_key_env: %s\n  extra_params: ", dto.ProfileID, dto.EffectiveModelParams.BackendID, dto.EffectiveModelParams.Endpoint, dto.EffectiveModelParams.Model, dto.EffectiveModelParams.Temperature, dto.EffectiveModelParams.MaxTokens, dto.EffectiveModelParams.TopP, dto.EffectiveModelParams.TimeoutSeconds, dto.EffectiveModelParams.ServiceTier, dto.EffectiveModelParams.ReasoningEffort, dto.EffectiveModelParams.APIKeyEnv)
+		paramsJSON, err := json.Marshal(dto.EffectiveModelParams.ExtraParams)
+		if err != nil {
+			return nil, err
+		}
+		fmt.Fprintf(&b, "%s\napi_key_required: %t\n", paramsJSON, dto.APIKeyRequired)
+		return b.Bytes(), nil
+	default:
+		return nil, fmt.Errorf("%w: %q", ErrUnknownPreparedRunFormat, outputFormat)
+	}
+}

internal/format/inspection_test.go

@@ -0,0 +1,124 @@
+package format
+
+import (
+	"encoding/json"
+	"strings"
+	"testing"
+
+	"gitea.maximumdirect.net/eric/promptkit"
+)
+
+func TestFormatPromptInspectionPreservesDeclaredOrderAndEmptyValues(t *testing.T) {
+	value := &promptkit.PromptInspection{PromptID: "p", PromptVersion: "1", PromptHash: "hash", Inputs: []promptkit.PromptInputDefinition{{Name: "first", Required: true, ContentType: "text/plain", Description: "first input"}, {Name: "second"}}, OutputContract: promptkit.OutputContract{Format: "text", ValidationMode: promptkit.ValidationNone}}
+	text, err := FormatPromptInspection(value, OutputFormatText)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if !strings.Contains(string(text), "default_profile_id: \ninputs:\n  - name: first") || strings.Index(string(text), "name: first") > strings.Index(string(text), "name: second") {
+		t.Fatalf("unexpected text inspection: %s", text)
+	}
+	jsonOutput, err := FormatPromptInspection(value, OutputFormatJSON)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if !strings.HasSuffix(string(jsonOutput), "\n") || !strings.Contains(string(jsonOutput), `"default_profile_id": ""`) {
+		t.Fatalf("unexpected json inspection: %s", jsonOutput)
+	}
+}
+
+func TestFormatPromptInspectionRejectsNil(t *testing.T) {
+	if _, err := FormatPromptInspection(nil, OutputFormatText); err == nil {
+		t.Fatal("expected nil inspection error")
+	}
+}
+
+func TestFormatProfileInspectionPreservesSafeEffectiveValues(t *testing.T) {
+	const secret = "sentinel-secret-must-not-appear"
+	t.Setenv("FIXTURE_PROFILE_API_KEY", secret)
+
+	value := &promptkit.ProfileInspection{
+		ProfileID: "custom-derived",
+		EffectiveModelParams: promptkit.ExecutionTarget{
+			BackendID:       "fixture-custom",
+			Endpoint:        "http://127.0.0.1:11434/v1",
+			Model:           "fixture-model",
+			Temperature:     0.25,
+			MaxTokens:       640,
+			TopP:            0.9,
+			TimeoutSeconds:  45,
+			ServiceTier:     "flex",
+			ReasoningEffort: "high",
+			APIKeyEnv:       "FIXTURE_PROFILE_API_KEY",
+			ExtraParams: map[string]any{
+				"zeta":  true,
+				"alpha": map[string]any{"nested": []any{"first", 2.0}},
+			},
+		},
+		APIKeyRequired: true,
+	}
+
+	jsonOutput, err := FormatProfileInspection(value, OutputFormatJSON)
+	if err != nil {
+		t.Fatal(err)
+	}
+	secondJSONOutput, err := FormatProfileInspection(value, OutputFormatJSON)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if string(jsonOutput) != string(secondJSONOutput) || !strings.HasSuffix(string(jsonOutput), "\n") {
+		t.Fatalf("expected deterministic newline-terminated JSON, got %q", jsonOutput)
+	}
+	if strings.Contains(string(jsonOutput), secret) {
+		t.Fatalf("inspection exposed an environment secret: %s", jsonOutput)
+	}
+
+	var decoded ProfileInspection
+	if err := json.Unmarshal(jsonOutput, &decoded); err != nil {
+		t.Fatalf("decode profile inspection: %v", err)
+	}
+	if decoded.ProfileID != "custom-derived" || decoded.EffectiveModelParams.BackendID != "fixture-custom" {
+		t.Fatalf("unexpected profile identity: %+v", decoded)
+	}
+	if decoded.EffectiveModelParams.APIKeyEnv != "FIXTURE_PROFILE_API_KEY" || !decoded.APIKeyRequired {
+		t.Fatalf("unexpected credential metadata: %+v", decoded)
+	}
+	alpha, ok := decoded.EffectiveModelParams.ExtraParams["alpha"].(map[string]any)
+	if !ok || len(alpha["nested"].([]any)) != 2 {
+		t.Fatalf("nested extra parameters were not preserved: %#v", decoded.EffectiveModelParams.ExtraParams)
+	}
+
+	textOutput, err := FormatProfileInspection(value, OutputFormatText)
+	if err != nil {
+		t.Fatal(err)
+	}
+	textValue := string(textOutput)
+	if !strings.Contains(textValue, "backend_id: fixture-custom") ||
+		!strings.Contains(textValue, "api_key_env: FIXTURE_PROFILE_API_KEY") ||
+		!strings.Contains(textValue, `extra_params: {"alpha":{"nested":["first",2]},"zeta":true}`) ||
+		!strings.Contains(textValue, "api_key_required: true") {
+		t.Fatalf("unexpected text inspection: %s", textValue)
+	}
+	if strings.Contains(textValue, secret) {
+		t.Fatalf("text inspection exposed an environment secret: %s", textValue)
+	}
+}
+
+func TestFormatProfileInspectionPreservesEmptyBackendAndRejectsNil(t *testing.T) {
+	output, err := FormatProfileInspection(&promptkit.ProfileInspection{
+		ProfileID: "endpoint-only",
+		EffectiveModelParams: promptkit.ExecutionTarget{
+			Endpoint: "http://127.0.0.1:8000/v1",
+			Model:    "fixture-model",
+		},
+	}, OutputFormatJSON)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if !strings.Contains(string(output), `"backend_id": ""`) ||
+		!strings.Contains(string(output), `"extra_params": {}`) {
+		t.Fatalf("expected explicit empty backend and object extra params, got %s", output)
+	}
+	if _, err := FormatProfileInspection(nil, OutputFormatText); err == nil {
+		t.Fatal("expected nil profile inspection error")
+	}
+}

internal/format/prepared_run.go

@@ -1,4 +1,4 @@
-// Package format formats already-prepared domain data for adapters.
+// Package format formats already-prepared public data for adapters.
 package format
 
 import (
@@ -9,37 +9,52 @@ import (
 	"sort"
 	"strings"
 
-	"gitea.maximumdirect.net/eric/scriptorium/internal/domain"
+	"gitea.maximumdirect.net/eric/promptkit"
 )
 
 var ErrUnknownPreparedRunFormat = errors.New("unknown prepared run format")
 
-// PreparedRunOutputFormat is the output format for prepared render data.
-type PreparedRunOutputFormat string
+// OutputFormat selects an application-owned textual or JSON representation.
+type OutputFormat string
 
 const (
-	PreparedRunFormatText PreparedRunOutputFormat = "text"
-	PreparedRunFormatJSON PreparedRunOutputFormat = "json"
+	OutputFormatText OutputFormat = "text"
+	OutputFormatJSON OutputFormat = "json"
 
-	DefaultPreparedRunOutputFormat PreparedRunOutputFormat = PreparedRunFormatText
+	DefaultOutputFormat OutputFormat = OutputFormatText
+)
+
+// PreparedRunOutputFormat is the output format for prepared render data.
+type PreparedRunOutputFormat = OutputFormat
+
+const (
+	PreparedRunFormatText = OutputFormatText
+	PreparedRunFormatJSON = OutputFormatJSON
+
+	DefaultPreparedRunOutputFormat = DefaultOutputFormat
 )
 
 // PreparedRunFormatter serializes a prepared run without performing use case work.
 type PreparedRunFormatter interface {
-	Format(prepared *domain.PreparedRun) ([]byte, error)
+	Format(prepared *promptkit.PreparedRun) ([]byte, error)
 }
 
 // ParsePreparedRunOutputFormat parses a format name.
 func ParsePreparedRunOutputFormat(raw string) (PreparedRunOutputFormat, error) {
-	switch PreparedRunOutputFormat(strings.ToLower(strings.TrimSpace(raw))) {
+	return ParseOutputFormat(raw)
+}
+
+// ParseOutputFormat parses the shared inspection and prepared-run format names.
+func ParseOutputFormat(raw string) (OutputFormat, error) {
+	switch OutputFormat(strings.ToLower(strings.TrimSpace(raw))) {
 	case "":
-		return DefaultPreparedRunOutputFormat, nil
-	case PreparedRunFormatText:
-		return PreparedRunFormatText, nil
-	case PreparedRunFormatJSON:
-		return PreparedRunFormatJSON, nil
+		return DefaultOutputFormat, nil
+	case OutputFormatText:
+		return OutputFormatText, nil
+	case OutputFormatJSON:
+		return OutputFormatJSON, nil
 	default:
-		return "", fmt.Errorf("%w: %q (supported: %s, %s)", ErrUnknownPreparedRunFormat, raw, PreparedRunFormatText, PreparedRunFormatJSON)
+		return "", fmt.Errorf("%w: %q (supported: %s, %s)", ErrUnknownPreparedRunFormat, raw, OutputFormatText, OutputFormatJSON)
 	}
 }
 
@@ -56,7 +71,7 @@ func FormatterForPreparedRun(outputFormat PreparedRunOutputFormat) (PreparedRunF
 }
 
 // FormatPreparedRun formats a prepared run using the selected format.
-func FormatPreparedRun(prepared *domain.PreparedRun, outputFormat PreparedRunOutputFormat) ([]byte, error) {
+func FormatPreparedRun(prepared *promptkit.PreparedRun, outputFormat PreparedRunOutputFormat) ([]byte, error) {
 	formatter, err := FormatterForPreparedRun(outputFormat)
 	if err != nil {
 		return nil, err
@@ -65,7 +80,7 @@ func FormatPreparedRun(prepared *domain.PreparedRun, outputFormat PreparedRunOut
 }
 
 // FormatPreparedRunByName parses a format name and formats a prepared run.
-func FormatPreparedRunByName(prepared *domain.PreparedRun, rawFormat string) ([]byte, error) {
+func FormatPreparedRunByName(prepared *promptkit.PreparedRun, rawFormat string) ([]byte, error) {
 	outputFormat, err := ParsePreparedRunOutputFormat(rawFormat)
 	if err != nil {
 		return nil, err
@@ -75,7 +90,7 @@ func FormatPreparedRunByName(prepared *domain.PreparedRun, rawFormat string) ([]
 
 type jsonPreparedRunFormatter struct{}
 
-func (jsonPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, error) {
+func (jsonPreparedRunFormatter) Format(prepared *promptkit.PreparedRun) ([]byte, error) {
 	if prepared == nil {
 		return nil, errors.New("prepared run is nil")
 	}
@@ -84,7 +99,7 @@ func (jsonPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, er
 
 type textPreparedRunFormatter struct{}
 
-func (textPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, error) {
+func (textPreparedRunFormatter) Format(prepared *promptkit.PreparedRun) ([]byte, error) {
 	if prepared == nil {
 		return nil, errors.New("prepared run is nil")
 	}
@@ -93,9 +108,15 @@ func (textPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, er
 	fmt.Fprintf(&b, "prompt: %s\n", prepared.PromptID)
 	fmt.Fprintf(&b, "prompt_version: %s\n", prepared.PromptVersion)
 	fmt.Fprintf(&b, "selected_profile_id: %s\n", prepared.SelectedProfileID)
+	if prepared.SelectedBackendID != "" {
+		fmt.Fprintf(&b, "selected_backend_id: %s\n", prepared.SelectedBackendID)
+	}
 	if prepared.PromptHash != "" {
 		fmt.Fprintf(&b, "prompt_hash: %s\n", prepared.PromptHash)
 	}
+	if prepared.SessionID != "" {
+		fmt.Fprintf(&b, "session_id: %s\n", prepared.SessionID)
+	}
 	fmt.Fprintf(&b, "rendered_prompt_hash: %s\n", prepared.RenderedPromptHash)
 
 	target := prepared.EffectiveModelParams
@@ -106,6 +127,9 @@ func (textPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, er
 	fmt.Fprintf(&b, "  max_tokens: %d\n", target.MaxTokens)
 	fmt.Fprintf(&b, "  top_p: %g\n", target.TopP)
 	fmt.Fprintf(&b, "  timeout_seconds: %d\n", target.TimeoutSeconds)
+	if target.ServiceTier != "" {
+		fmt.Fprintf(&b, "  service_tier: %s\n", target.ServiceTier)
+	}
 	if target.ReasoningEffort != "" {
 		fmt.Fprintf(&b, "  reasoning_effort: %s\n", target.ReasoningEffort)
 	}
@@ -120,7 +144,11 @@ func (textPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, er
 		}
 		sort.Strings(keys)
 		for _, k := range keys {
-			fmt.Fprintf(&b, "    %s: %s\n", k, target.ExtraParams[k])
+			renderedValue, err := formatExtraParamTextValue(target.ExtraParams[k])
+			if err != nil {
+				return nil, fmt.Errorf("failed to format extra_params.%s: %w", k, err)
+			}
+			fmt.Fprintf(&b, "    %s: %s\n", k, renderedValue)
 		}
 	}
 
@@ -136,7 +164,7 @@ func (textPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, er
 
 	fmt.Fprintln(&b, "messages:")
 	roleOrder := make([]string, 0)
-	byRole := make(map[string][]domain.RenderedMessage)
+	byRole := make(map[string][]promptkit.RenderedMessage)
 	for _, msg := range prepared.Messages {
 		if _, exists := byRole[msg.Role]; !exists {
 			roleOrder = append(roleOrder, msg.Role)
@@ -148,6 +176,13 @@ func (textPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, er
 		messages := byRole[role]
 		for i, msg := range messages {
 			fmt.Fprintf(&b, "    - message: %d\n", i+1)
+			if msg.CacheControl != nil {
+				fmt.Fprintf(&b, "      cache_control: %s", msg.CacheControl.Type)
+				if msg.CacheControl.TTL != "" {
+					fmt.Fprintf(&b, " ttl=%s", msg.CacheControl.TTL)
+				}
+				fmt.Fprintln(&b)
+			}
 			fmt.Fprintln(&b, "      content: |")
 			content := msg.Content
 			if content == "" {
@@ -162,3 +197,15 @@ func (textPreparedRunFormatter) Format(prepared *domain.PreparedRun) ([]byte, er
 
 	return b.Bytes(), nil
 }
+
+func formatExtraParamTextValue(value any) (string, error) {
+	if s, ok := value.(string); ok {
+		return s, nil
+	}
+
+	b, err := json.Marshal(value)
+	if err != nil {
+		return "", err
+	}
+	return string(b), nil
+}