Prepare Notarius v0.8.1 source release

.woodpecker/release.yml

@@ -1,3 +1,4 @@
+# Advisory validation after source publication, never a release-completion gate.
 when:
   - event: tag
 
@@ -5,29 +6,4 @@ steps:
   - name: validate-release
     image: golang:1.25.5
     commands:
-      - |
-        set -eu
-
-        version="$CI_COMMIT_TAG"
-        release_note="docs/releases/$version.md"
-
-        if ! printf '%s\n' "$version" | grep -E -x 'v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)' >/dev/null; then
-          printf '%s\n' "invalid release tag: $version" >&2
-          exit 1
-        fi
-        if [ ! -s "$release_note" ]; then
-          printf '%s\n' "missing release note: $release_note" >&2
-          exit 1
-        fi
-        if ! grep -F -x "# Notarius $version" "$release_note" >/dev/null; then
-          printf '%s\n' "release note heading does not match $version" >&2
-          exit 1
-        fi
-        for heading in '## Summary' '## Compatibility' '## Upgrade' '## Changes'; do
-          if ! grep -F -x "$heading" "$release_note" >/dev/null; then
-            printf '%s\n' "release note is missing heading: $heading" >&2
-            exit 1
-          fi
-        done
-
-        ./scripts/check-release-source.sh "$version"
+      - ./scripts/check-release-source.sh "$CI_COMMIT_TAG"

AGENTS.md

@@ -1,7 +1,6 @@
-Please review `docs/development.md` for initial orientation in this repository
-and follow its task-specific reading guide.
+Start with `docs/development.md` for orientation and use its policy reading guide
+to select the policies applicable to the task. Do not read the entire suite by
+default.
 
-For every planning and implementation task, follow the
-[`Implementation Discipline`](docs/policy/architecture.md#implementation-discipline):
-keep machinery proportionate, do not invent restrictions, and do not elevate
-incidental implementation details into repository policy.
+Read and follow `docs/policy/agents.md` before recommending, planning, or
+implementing repository changes.

COPYRIGHT

@@ -0,0 +1,23 @@
+Notarius
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: GPL-3.0-or-later
+
+Notarius 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.
+
+The GNU General Public License version 3 is provided in LICENSE.
+
+Policy material copied or adapted from Standard Repository Policies remains
+licensed under CC-BY-SA-4.0. See docs/oss/attribution.md for the affected
+portions, upstream credit, and license links.
+
+Notarius 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.
+
+Third-party code and assets are subject to their respective license terms.

LICENSE

@@ -1,232 +1,674 @@
-GNU GENERAL PUBLIC LICENSE
-Version 3, 29 June 2007
-
-Copyright © 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.
-
-     go-application-template
-     Copyright (C) 2026  eric
-
-     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/>.
+                    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:
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
 
-     go-application-template  Copyright (C) 2026  eric
-     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.
+    <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”.
+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/>.
+  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/philosophy/why-not-lgpl.html>.
+  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

@@ -60,3 +60,7 @@ Releases](docs/release.md).
 - [Developer guide](docs/development.md) — contributor orientation and
   validation guidance.
 - [Future work](docs/roadmap/future.md) — unimplemented ideas and priorities.
+
+Notarius is licensed under the [GPL v3.0 or later](COPYRIGHT).
+
+[Open Source attribution notices](docs/oss/attribution.md) are available.

docs/cli.md

@@ -12,8 +12,8 @@ defined in [Operations](operations.md).
 notarius help
 notarius --version
 notarius run <pipeline-id> --input path/to/source.json [--json] [flags]
-notarius config validate [--config path/to/config.yml] [--config-profile name] [--pipeline pipeline-id] [--only lane-a,lane-b]
-notarius pipelines list [--config path/to/config.yml] [--config-profile name] [--json]
+notarius config validate [--config path/to/config.yml] [--config-overlay name] [--pipeline pipeline-id] [--only lane-a,lane-b]
+notarius pipelines list [--config path/to/config.yml] [--config-overlay name] [--json]
 ~~~
 
 Running Notarius without arguments, or with **help**, **--help**, or **-h**,
@@ -42,7 +42,7 @@ pipeline ID and **--input** are required.
 | Flag | Meaning |
 | --- | --- |
 | **--config path** | Use this configuration file. When omitted, configuration discovery applies; see [Configuration](config.md). |
-| **--config-profile name** | Select a ConfigKit configuration overlay. Empty and **default** select the composed base configuration. |
+| **--config-overlay name** | Select a ConfigKit configuration overlay. Empty and **default** select the composed base configuration. |
 | **--input path** | Source input file to process. Required. |
 | **--output-dir path** | Override the configured output root for this run. |
 | **--json** | Write the successful run-result receipt as JSON to standard output. |
@@ -155,7 +155,7 @@ OPENROUTER_API_KEY=your-api-key \
 ## config validate
 
 ~~~
-notarius config validate [--config path/to/config.yml] [--config-profile name] [--pipeline pipeline-id] [--only lane-a,lane-b]
+notarius config validate [--config path/to/config.yml] [--config-overlay name] [--pipeline pipeline-id] [--only lane-a,lane-b]
 ~~~
 
 This command loads and validates the selected composed configuration. With **--pipeline**, it also
@@ -184,7 +184,7 @@ validation; it cannot run a provider-backed pipeline.
 ## config effective
 
 ~~~
-notarius config effective [--config path/to/config.yml] [--config-profile name]
+notarius config effective [--config path/to/config.yml] [--config-overlay name]
 ~~~
 
 This command writes the selected composed configuration as deterministic,
@@ -194,19 +194,19 @@ pipeline, prepare modules, materialize references, or contact a provider.
 ## config explain
 
 ~~~
-notarius config explain [--config path/to/config.yml] [--config-profile name] <json-pointer>
+notarius config explain [--config path/to/config.yml] [--config-overlay name] <json-pointer>
 ~~~
 
 This command writes ConfigKit's redacted, human-readable explanation for one
 canonical JSON Pointer. Supply `""` explicitly to explain the root. A malformed
 pointer is a syntax error; a well-formed unknown path is a command failure.
-The explanation can describe a value displaced by a selected profile. Standard
+The explanation can describe a value displaced by a selected overlay. Standard
 output contains only the explanation.
 
 ## pipelines list
 
 ~~~
-notarius pipelines list [--config path/to/config.yml] [--config-profile name] [--json]
+notarius pipelines list [--config path/to/config.yml] [--config-overlay name] [--json]
 ~~~
 
 This command lists configured pipeline IDs in sorted order. By default, it
@@ -225,7 +225,7 @@ errors are written to standard error.
 
 Configuration load errors include ConfigKit's field diagnostics and source
 coordinates, followed by a source-ID legend identifying the acquired files or
-source labels. This includes imported files and the selected configuration profile.
+source labels. This includes imported files and the selected configuration overlay.
 
 For **run --json**, actionable process warnings remain on standard error and standard output is a
 machine-readable success result only. Syntax and runtime diagnostics remain on

docs/config.md

@@ -20,12 +20,13 @@ For configuration values, precedence is:
 
 1. built-in defaults;
 2. composed YAML sources, including imports;
-3. the selected ConfigKit profile; and
+3. the selected ConfigKit overlay; and
 4. explicitly supplied configuration-valued run flags.
 
-`--config-profile` selects a ConfigKit overlay from `profiles/<name>.yml`
+`--config-overlay` selects a ConfigKit overlay from `overlays/<name>.yml`
 beneath the selected configuration root. Empty and `default` select no overlay.
-Configuration profiles are distinct from PromptKit LLM profiles selected by
+`profiles/<name>.yml` is not a fallback location, and `--config-profile` is no
+longer accepted. Configuration overlays are distinct from PromptKit LLM profiles selected by
 `llm_profile` or `--llm-profile`. The retired operational environment variables
 have no effect; `NOTARIUS_CONFIG` remains a source-discovery input.
 
@@ -79,14 +80,14 @@ umask, setgid inheritance, and default ACLs; see [Operations](operations.md#cach
 
 Every nonempty relative configured destination or reference path resolves from
 the canonical directory of the file that supplies its surviving declaration.
-This includes imported fragments and selected configuration profiles. Built-in
+This includes imported fragments and selected configuration overlays. Built-in
 relative destinations use the selected main configuration file's directory;
 explicit `--output-dir` and `--debug-dir` values use the invocation working
 directory. Absolute values remain unchanged.
 
 The root file can use ConfigKit imports to compose disjoint definitions. Imports
-and selected profiles remain under the configuration root; they do not merge or
-append a pipeline's `steps` sequence. A profile replaces sequences as defined
+and selected overlays remain under the configuration root; they do not merge or
+append a pipeline's `steps` sequence. An overlay replaces sequences as defined
 by ConfigKit, so changing an individual ordered binding requires supplying the
 whole replacement sequence.
 
@@ -101,6 +102,7 @@ version: 5
 promptkit:
   profile_dir: ./profiles
   # profile_file: ./profiles.yml
+  transient_retries: 2
   local_backend:
     endpoint: http://localhost:8000/v1
     concurrency_limit: 2
@@ -110,6 +112,7 @@ promptkit:
 | --- | --- | --- |
 | **profile_dir** | string | Non-empty directory containing profile files. |
 | **profile_file** | string | Non-empty profile file. |
+| **transient_retries** | integer | Non-negative additional built-in HTTP attempts for eligible transient provider failures; defaults to 2. Set 0 to disable these retries. |
 | **local_backend** | object | Optional registration for the conventional PromptKit backend ID **local**. |
 | **local_backend.endpoint** | string | Required when **local_backend** is present; absolute HTTP or HTTPS URL with a host. |
 | **local_backend.concurrency_limit** | integer | Optional non-negative limit; defaults to 0. |
@@ -201,7 +204,7 @@ debug:
 **concurrency.total_llm** must be greater than zero. The only supported
 **concurrency.stage_workers** key is **extract**; its value must be from 1
 through **total_llm**. When omitted, it is recalculated from the effective
-**total_llm** after imports, profile selection, and explicit ConfigKit
+**total_llm** after imports, overlay selection, and explicit ConfigKit
 overrides.
 
 **cache.chunk_plans.mode** accepts **auto**, **bypass**, or **refresh**.
@@ -440,7 +443,7 @@ pipeline, lane, and binding scopes and precedence are defined by the
 replace a configured generated artifact handoff. Required slots must be bound
 after configuration and CLI reference actions are applied. A YAML reference
 path resolves from the file that supplies its surviving declaration, including
-an imported fragment or selected profile. CLI reference paths resolve relative
+an imported fragment or selected overlay. CLI reference paths resolve relative
 to the process working directory.
 
 ### D&D Reference Slots
@@ -601,5 +604,5 @@ Use [config effective](cli.md#config-effective) to write the selected composed
 configuration as deterministic, redacted YAML. Use
 [config explain](cli.md#config-explain) with a canonical JSON Pointer to inspect
 the effective or historical provenance for one path, including a value displaced
-by a selected profile. Neither command resolves a pipeline, prepares modules,
+by a selected overlay. Neither command resolves a pipeline, prepares modules,
 materializes references, or requires provider credentials.

docs/consumers/subprocess.md

@@ -15,10 +15,10 @@ configured lane inventory, and downstream acceptance checklist, see
 Optionally preflight a selected configuration and pipeline before work starts:
 
 ```sh
-notarius config validate --config /path/to/notarius.yml --config-profile production --pipeline pipeline-id
+notarius config validate --config /path/to/notarius.yml --config-overlay production --pipeline pipeline-id
 ```
 
-Omit `--config-profile` when the composed base configuration is the intended
+Omit `--config-overlay` when the composed base configuration is the intended
 selection; it is independent from any `--llm-profile` run override.
 
 Invoke the run with explicit paths and machine-readable output. Capture
@@ -28,7 +28,7 @@ processing the result.
 ```sh
 notarius run pipeline-id \
   --config /path/to/notarius.yml \
-  --config-profile production \
+  --config-overlay production \
   --input /path/to/source.json \
   --output-dir /path/to/output-root \
   --json

docs/development.md

@@ -4,19 +4,41 @@ This is the first-read landing page for people and LLM coding agents working on
 Notarius. It provides a concise repository orientation and routes each kind of
 change to its canonical documentation.
 
-Notarius is a Go CLI for configured structured extraction workflows. Start with
-the [README](../README.md) for product context, [Architecture](policy/architecture.md)
-for system boundaries, and [Internal Overview](internal/overview.md) for the
-implemented component map.
+Notarius is a Go CLI for configured structured extraction workflows. The
+[README](../README.md) provides product context; [Architecture](policy/architecture.md)
+describes system boundaries, and [Internal Overview](internal/overview.md) maps
+implemented components. Read the documents applicable to your task.
+
+Read [Agent Policy](policy/agents.md) before recommending, planning, or
+implementing changes. It owns implementation discipline and local commit rules.
+
+## Policy Reading Guide
+
+| Policy | Read before… |
+| --- | --- |
+| [Policy set provenance](policy/meta.md) | Adopting policies, checking upstream revisions, or updating the adopted policy set. |
+| [Agents](policy/agents.md) | Recommending, planning, or implementing repository changes. |
+| [Architecture](policy/architecture.md) | Planning or changing application code or its structure. |
+| [Testing](policy/testing.md) | Selecting validation for code changes, or adding, changing, removing, or evaluating tests. |
+| [Documentation](policy/documentation.md) | Writing, revising, or reorganizing documentation. |
+| [OSS](policy/oss.md) | Adding or updating dependencies or incorporated third-party material, or changing licensing or attribution. |
+| [Release](policy/release.md) | Preparing or publishing a release, changing release procedures, or making versioning and compatibility decisions. |
+
+- Read applicable policies before making decisions they govern; multiple policies
+  may apply.
+- Select policies using the task triggers above. Follow cross-references to
+  relevant sections when needed to resolve a concrete question.
+- Reuse policies already available in context; reread when changed or no longer
+  available.
+- Expand reading when the task's scope expands.
+- When revising a policy itself, read that policy and any provisions elsewhere
+  affected by the revision.
 
 ## What To Read
 
 | When working on | Read | Why |
 | --- | --- | --- |
 | Finding the package or component that owns current behavior | [Internal Overview](internal/overview.md) | It is the implemented component inventory and routes to focused internals. |
-| Application shape, package boundaries, contracts, dependency direction, runtime guarantees, or safety properties | [Architecture](policy/architecture.md) and relevant [ADRs](adr/) | Architecture defines the intended system and its invariants; ADRs preserve significant decision rationale. |
-| Any documentation addition or revision | [Documentation Policy](policy/documentation.md) | It defines canonical homes, audiences, current-behavior rules, and maintenance requirements. |
-| Adding, changing, reviewing, or deleting tests | [Testing Policy](policy/testing.md) | It defines risk-based sufficiency, durable test boundaries, test-double guidance, and criteria for retaining tests. |
 | CLI composition or command behavior | [CLI Internals](internal/cli.md) and [CLI Reference](cli.md) | The internal guide owns composition and command flow; the reference owns public syntax. |
 | Building a subprocess caller or changing its result protocol | [Subprocess Consumer Guide](consumers/subprocess.md), [Complete D&D Consumer Guide](consumers/dnd-pipeline.md), [Run Result Receipt](integrations/run-result.md), and [CLI Internals](internal/cli.md) | These separate generic caller workflow, the complete D&D workflow, the durable receipt contract, and CLI implementation behavior. |
 | Configuration loading, resolution, or user-visible configuration behavior | [Configuration Internals](internal/configuration.md) and [Configuration](config.md) | The internal guide owns loading and resolution mechanics; the reference owns the configuration contract. |
@@ -25,7 +47,7 @@ implemented component map.
 | LLM clients, prompts, schemas, profiles, or scheduling | [LLM Runtime](internal/llm.md) | It documents the transport boundary and PromptKit integration. |
 | Output, cache, resume, or debug artifacts | [Run State Internals](internal/state.md), [Operations](operations.md), and [Configuration](config.md) | These separate implementation details, operator behavior, and configuration contracts. |
 | External input formats, artifact schemas, or durable output files | [Integration Contracts](integrations/) | Integration documents define external and durable data contracts. |
-| Release preparation, tagging, publication, or verification | [Source Releases](release.md) and [Documentation Policy](policy/documentation.md) | The release procedure owns maintainer guards and immutable-tag recovery; the policy assigns release-note ownership. |
+| Repository-specific release commands or diagnostics | [Source Releases](release.md) | The runbook supplies publication commands and recovery procedures. |
 | Proposed or unimplemented behavior | [Roadmap](roadmap/) | Future work belongs only in roadmap documentation until implemented. |
 
 For an existing subsystem, also inspect its focused tests and the package-local

docs/integrations/pkg-configkit.md

@@ -2,7 +2,7 @@
 
 Notarius uses the public root package
 [`gitea.maximumdirect.net/eric/ConfigKit`](https://gitea.maximumdirect.net/eric/ConfigKit)
-at v0.3.0 for version 5 configuration acquisition, imports, profiles, explicit
+at v0.4.2 for version 5 configuration acquisition, imports, overlays, explicit
 overrides, diagnostics, and safe inspection rendering.
 
 Notarius owns the typed document, domain defaults and validation, runtime
@@ -11,3 +11,8 @@ paths, and command discovery. It uses only ConfigKit's public path, result,
 diagnostic, and resolution-source APIs. Upstream documentation owns general
 ConfigKit semantics; [Configuration](../config.md) owns Notarius's file and
 operator contract.
+
+The v0.4.2 patch updates upstream release tooling and policy/licensing
+documentation without changing configuration behavior or the public API. See
+the canonical [ConfigKit attribution](../oss/attribution.md#configkit) for its
+license and notices.

docs/integrations/pkg-promptkit.md

@@ -1,11 +1,11 @@
 # PromptKit Integration
 
 Notarius pins
-[`gitea.maximumdirect.net/eric/promptkit` v0.9.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0)
+[`gitea.maximumdirect.net/eric/promptkit` v0.11.2](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2)
 as its in-process prompt engine. The upstream
-[Go package consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/docs/consumers/pkg-promptkit.md)
+[Go package consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/docs/consumers/pkg-promptkit.md)
 owns the public engine API, and the upstream
-[format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/docs/formats.md)
+[format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/docs/formats.md)
 owns prompt, profile, and schema file contracts.
 
 ## Supported Boundary
@@ -27,7 +27,7 @@ Notarius relies on the root `promptkit` package to:
   admission exhaustion through `ErrCapacityExceeded`.
 
 The pinned
-[`BackendLocal`, `LocalBackend`, and `WithBackend` API](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/backends.go)
+[`BackendLocal`, `LocalBackend`, and `WithBackend` API](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/backends.go)
 owns the registration and backend-capacity contract.
 
 For one completion, the adapter calls `PrepareExecution`, takes a
@@ -53,7 +53,7 @@ Notarius sends one stable effective session through PromptKit's direct session
 field, which is authoritative for provider session behavior. It also retains
 the same value as the `session_id` prompt variable for maintained prompt
 compatibility. The generated identifier is 76 ASCII characters, within
-PromptKit v0.9.0's 256-code-point session limit. Session IDs are non-secret
+PromptKit's 256-code-point session limit. Session IDs are non-secret
 correlation identifiers and may be exposed to providers and provider
 observability. The CLI contract owns generation and override behavior.
 
@@ -71,7 +71,15 @@ endpoint-only profiles have no such backend limit. The adapter translates
 PromptKit capacity rejection into the provider-neutral Notarius
 `ErrLLMCapacityExceeded` contract. It may include the normalized selected
 backend ID in safe diagnostic context, without exposing PromptKit's capacity
-error type, and leaves retries to the calling pipeline stage.
+error type. PromptKit's built-in client retries eligible transient HTTP failures
+with its v0.11.2 default of two additional attempts per generation; Notarius
+keeps pipeline-stage retries outside that completion boundary.
+
+The adapter projects built-in generation failures as the application-owned
+`LLMGenerationError`, retaining a safe failure kind, HTTP status when present,
+and retry-exhaustion attempt count. Transport, malformed successful envelopes,
+provider statuses, and generic generation failures remain distinct without
+exposing PromptKit error values to Notarius callers.
 
 ## Profile Sources And Compatibility
 
@@ -86,16 +94,16 @@ configuration and deployment workflow are defined in
 [Operations](../operations.md#promptkit-profile-deployment).
 
 PromptKit owns `base_profile` resolution under its
-[pinned format rules](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/docs/formats.md).
+[pinned format rules](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/docs/formats.md).
 Notarius records the selected leaf identity and resolved target without parsing
 or merging inheritance. An unset filesystem `api_key_env` is optional and may
 reach the provider without authorization, which can result in a 401 or 403.
 
-PromptKit v0.9.0 accepts only the `developer`, `system`, `user`, and
+PromptKit accepts only the `developer`, `system`, `user`, and
 `assistant` text-chat roles after normalizing case and surrounding whitespace.
 Maintained Notarius prompt definitions use only `system` and `user`.
 
-For application-owned semantic correction, Notarius uses PromptKit v0.9.0's
+For application-owned semantic correction, Notarius uses PromptKit's
 `RunRequest.AppendedMessages` after the ordinary rendered prompt. It supplies
 exactly two messages in order: the latest validated producer response with
 role `assistant`, then deterministic validation guidance with role `user`.
@@ -112,12 +120,28 @@ and terminal summaries retain only safe counts, digests, identities, and usage;
 complete appended messages remain limited to the explicitly requested detailed
 debug trace.
 
-PromptKit now obtains its maintained OpenRouter and Rakestrawhome backend and
+PromptKit obtains its maintained OpenRouter and Rakestrawhome backend and
 profile catalogs from independently versioned transitive modules. Notarius
 does not import or register either catalog; PromptKit retains catalog source,
 identity, precedence, credential, and capacity ownership.
 
-Notarius supports this boundary against PromptKit v0.9.0. Its fallback source,
+External catalog profile names and settings can change between dependency
+releases, including removal without aliases. Review directly selected IDs and
+inherited `base_profile` values when upgrading. An application-owned alias that
+inherits an external profile does not freeze that profile's settings.
+PromptKit's opt-in `promptkit-openrouter-standard` and
+`promptkit-openrouter-auto` names provide name continuity within its
+selected-and-tested dependency scope, not a fixed model or provider availability
+guarantee. See the upstream
+[catalog compatibility policy](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/docs/policy/release.md#catalog-profile-compatibility).
+
+Use a complete operator-owned profile with explicit backend or endpoint, model,
+and settings when those choices must remain operator-controlled. The embedded
+`dnd-extraction` fallback already follows this model and does not inherit an
+external catalog profile. An upgrade updates Notarius's compiled-in catalog
+checkpoint identity so prior profile-source checkpoints are not reused.
+
+Notarius supports this boundary against PromptKit v0.11.2. Its fallback source,
 prepared-execution, inspection, and typed capacity APIs are used as public
 upstream contracts; other PromptKit APIs or file-format behavior are not
 implicitly supported. A dependency upgrade requires reviewing the adapter,
@@ -146,3 +170,9 @@ profile/configuration contracts against the upstream documentation. Maintained
 production prompts use PromptKit's bounded structural-repair contract; their
 current declaration is one additional repair attempt. Notarius retains the
 transport-neutral boundary and does not expose PromptKit types to modules.
+
+The v0.11.2 patch updates upstream policy and licensing documentation without
+changing runtime APIs, profile settings, or dependency/catalog versions.
+See the canonical [PromptKit attribution](../oss/attribution.md#promptkit),
+[OpenRouter catalog notice](../oss/attribution.md#promptkit-openrouter-catalog),
+and [Rakestrawhome catalog notice](../oss/attribution.md#promptkit-rakestrawhome-catalog).

docs/internal/cli.md

@@ -35,7 +35,7 @@ options before dispatch so that a missing production dependency fails as a
 command error rather than reaching execution.
 
 Commands that need configuration use one shared ConfigKit-backed loader. The
-CLI discovers the file, passes the requested profile and only explicit
+CLI discovers the file, passes the requested overlay and only explicit
 configuration-valued run overrides, and receives a **LoadedConfig**. The
 configured discovery and precedence contract is in
 [Configuration](../config.md), while the loading and resolution mechanics are

docs/internal/configuration.md

@@ -28,7 +28,7 @@ at their respective [CLI](cli.md), [pipeline](pipeline.md), and
 
 ## Loading And Validation
 
-ConfigKit acquires the selected root, imports, optional selected profile, and
+ConfigKit acquires the selected root, imports, optional selected overlay, and
 explicit CLI overrides in precedence order. Its document definition supplies
 typed defaults, source-aware path normalization, and structural validation
 before conversion to the independently owned runtime **Config**. Only
@@ -44,7 +44,9 @@ concurrency settings, malformed bindings and references, invalid retries, and
 invalid pipeline, step, or lane structure. PromptKit local-backend validation
 accepts only an absolute HTTP or HTTPS endpoint with a host and no user
 information, query, or fragment, and rejects a negative local concurrency
-limit. Its errors retain the closest known pipeline, lane, and binding context.
+limit. It also rejects a negative `promptkit.transient_retries` value; decoded
+omission resolves to two, while explicit zero remains a distinct opt-out. Its
+errors retain the closest known pipeline, lane, and binding context.
 It deliberately does not require modules to be registered: that requires a
 catalog and belongs to resolution.
 
@@ -112,13 +114,15 @@ recording arbitrary environment values or provider requests.
 
 ## Invariants To Preserve
 
-- ConfigKit composition applies defaults, imports, an optional profile, and
+- ConfigKit composition applies defaults, imports, an optional overlay, and
   explicit overrides in one direction with retained origin metadata.
 - A configuration is structurally valid before it is resolved, and a resolved
   pipeline is compatible with the supplied catalog before preparation begins.
 - Whitespace-normalized identifiers are unique wherever they identify a
   pipeline, step, lane, worker, or reference slot.
 - Runtime conversion and resolved-pipeline publication return detached data.
+- The resolved PromptKit transient-retry budget is always passed to the shared
+  built-in client; document presence preserves an explicit zero.
 - The resolved digest changes when resolved composition changes and never
   includes itself.
 
@@ -126,7 +130,7 @@ recording arbitrary environment values or provider requests.
 
 - **internal/core/config/document_test.go** and
   **operational_document_test.go** cover ConfigKit document loading,
-  normalization, imports, profiles, and overrides.
+  normalization, imports, overlays, and overrides.
 - **internal/core/config/validation_contract_test.go** covers configuration
   invariants and contextual failures.
 - **internal/core/config/effective_config_contract_test.go** covers defaults,

docs/internal/llm.md

@@ -216,6 +216,19 @@ than output-validation failures. Apart from documented context, capacity, and
 invalid-output categories, provider error values and types do not cross the
 adapter error chain; callers receive only a credential-redacted diagnostic.
 
+`LLMGenerationError` preserves the provider-neutral failure kind (`transport`,
+`provider_status`, `malformed_response`, or generic `generation`) and any HTTP
+status. When PromptKit exhausts an eligible transient-status retry budget, it
+also records that exhaustion and the attempts in that generation. Those fields
+do not include repair generations, and zero attempts means unavailable rather
+than proof that no request was sent.
+
+Every execution that reaches PromptKit returns an optional request-local
+`execution` summary. It contains only terminal aggregate attempts, retry and
+repair counts, durations, outcome and failure classification, status, and
+presence-aware token usage. Preparation failures have no summary; later local
+decode failures retain the upstream terminal summary without changing it.
+
 When PromptKit rejects backend admission before generation, the adapter maps
 `promptkit.ErrCapacityExceeded` to
 `contracts.ErrLLMCapacityExceeded`, retaining prompt context and a redacted
@@ -258,14 +271,18 @@ diagnostics; see
 ## Timeout Ownership
 
 The caller context remains the outer cancellation authority. PromptKit applies
-a positive effective generation timeout as an inner request deadline; an
-explicit zero disables only that generation deadline. The HTTP client timeout
-is a separate transport-wide cap. Notarius forwards the caller context and
-does not install another timeout wrapper around PromptKit.
+a positive effective generation timeout as an inner request deadline for each
+built-in generation attempt; an explicit zero disables only that generation
+deadline. The HTTP client timeout is a separate transport-wide cap. Notarius
+forwards the caller context and does not install another timeout wrapper around
+PromptKit.
 
-The selected PromptKit profile owns generation settings. Notarius binding
-retries remain outside the adapter and repeat the complete module operation
-and validation chain. PromptKit does not add a provider retry loop.
+The selected PromptKit profile owns generation settings. The resolved global
+`promptkit.transient_retries` configuration is passed to the shared PromptKit
+engine and controls additional built-in attempts for eligible transient HTTP
+failures in one generation. It defaults to two; explicit zero disables those
+attempts. Notarius binding retries remain outside the adapter and repeat the
+complete module operation and validation chain.
 Operator-facing behavior is summarized in
 [Operations](../operations.md#operational-limits), and the pinned upstream
 contract is identified in

docs/internal/pipeline.md

@@ -52,7 +52,7 @@ consumers do not repeat profile inheritance or configuration resolution.
 Each LLM request receives its own copy of that resolved value. PromptKit spends
 it only for structural correction inside one completion; the runner's binding
 retry policy remains the separate outer budget for complete stage attempts.
-Configuration resolution supplies the selected profile and catalog; see
+Configuration resolution supplies the selected overlay and catalog; see
 [Configuration Internals](configuration.md).
 
 External reference materialization happens before preparation. The materializer

docs/internal/state.md

@@ -1,5 +1,9 @@
 # Run State Internals
 
+LLM debug response artifacts and their safe per-call references retain an
+optional terminal execution summary when one is available. This metadata is
+diagnostic only and does not change receipts, checkpoints, or aggregate usage.
+
 This document describes the implementation collaborators behind output, cache,
 and debug state. User-visible fields belong in [Configuration](../config.md),
 and physical layout, retention, recovery, reason codes, and cleanup belong in

docs/operations.md

@@ -147,13 +147,32 @@ their exit classes are defined in the [CLI reference](cli.md#output-streams-and-
 
 ## Validation Retries And Terminal Outcomes
 
+When debug recording is enabled, per-call response artifacts include the
+terminal execution summary for retry, repair, timing, and presence-aware usage
+diagnosis. Normal output, receipts, and warnings do not aggregate or publish
+this diagnostic metadata.
+
 Each producer binding has one outer **retries** budget. It covers complete
 producer attempts for operational failures, invalid structured output,
 normalizer fallback retry, and semantic correction. It is independent from
-PromptKit's structural-repair calls inside one completion and from an
-LLM-backed validator's own retry budget. A semantic correction rebuilds the
-ordinary producer request and supplies only the latest rejected model response
-plus aggregated validator guidance; it is not a conversation replay.
+PromptKit's structural-repair calls inside one completion, its configured
+`promptkit.transient_retries` built-in HTTP attempts, and an LLM-backed
+validator's own retry budget. The transient setting defaults to two additional
+attempts for eligible provider statuses; set it explicitly to zero when an
+operator needs one HTTP attempt per generation. A semantic correction rebuilds
+the ordinary producer request and supplies only the latest rejected model
+response plus aggregated validator guidance; it is not a conversation replay.
+
+These budgets multiply only by their declared scopes. With two outer producer
+retries, two transient retries, and one structural repair, a single producer
+can issue up to 18 HTTP attempts: three producer attempts, each with an initial
+generation and one repair generation, each allowing three HTTP attempts. This
+is an illustration, not a total-deadline or exactly-once guarantee. Every
+built-in HTTP attempt has its own generation timeout; caller cancellation
+remains the overall authority and interrupts Retry-After waiting. The shared
+Notarius scheduler keeps its permit through those waits, so retry budgets can
+increase latency and provider cost. Observed usage can remain incomplete when
+providers omit accounting fields.
 
 After the applicable budgets are exhausted, the resolved
 [`validation_policy`](config.md#pipelines) determines the result. Structural
@@ -319,7 +338,7 @@ content. Neither surface is a cache input. Do not treat a debug bundle as safe
 to share merely because its configuration summary is redacted. Invocation
 metadata omits reasoning effort when it is inherited, records the replacement
 value when one is supplied, and records an empty value when inherited reasoning
-was explicitly cleared. It records `config_profile` only when a non-base
+was explicitly cleared. It records `config_overlay` only when a non-base
 configuration overlay was selected.
 
 Notarius never creates debug state without an explicit request and never
@@ -352,7 +371,9 @@ Provider execution settings and the generation timeout come from the selected
 PromptKit profile. The invocation-only **--reasoning-effort** and
 **--clear-reasoning-effort** controls may replace or clear that profile setting
 for all LLM-backed calls in one run without changing the profile. PromptKit
-structural output repair happens within one structured-completion call. Its
+also retries eligible transient HTTP failures with its built-in default
+of two additional attempts per generation. This retry work is separate from
+structural output repair, which happens within one structured-completion call. Its
 effective `structured_output_repair_attempts` limit is resolved from the
 selected binding, then the pipeline, then the prompt declaration; see
 [module bindings](config.md#module-bindings-and-validators). This is distinct
@@ -360,19 +381,20 @@ from Notarius binding **retries**, which rerun the complete module operation
 and validation chain and do not consume or replenish the structural-repair
 limit. The maintained production prompts declare one repair attempt, paid only
 after a structural failure. One structured completion with repair budget **R**
-makes at most **R + 1** serial provider calls. If one stage attempt performs
-**C** structured completions, a binding with **retries: N** has a maximum of
-**(N + 1) * C * (R + 1)** provider calls; LLM-backed validators have their own
-corresponding invocation counts and budgets. This is an upper bound, not a
-promise that every call reaches a provider.
+contains at most **R + 1** serial generations. Each generation can now contain
+more than one provider call when PromptKit retries an eligible transient
+failure. LLM-backed validators have their own corresponding invocation and
+repair budgets. These are bounds on attempted work, not a promise that every
+call reaches a provider.
 
 Timeouts are layered. Caller cancellation is the outer authority. A positive
-effective generation timeout adds an inner request deadline, while zero
-disables only that generation deadline. The HTTP client timeout remains a
-transport-wide cap. Notarius does not add another timeout around PromptKit.
-Repairs are serial within the same caller context, so their worst-case latency
-and cost follow the provider-call bound above; provision run deadlines and
-provider budgets accordingly. Credentials remain optional unless the selected
+effective generation timeout adds an inner request deadline to each built-in
+generation attempt, while zero disables only that generation deadline. The HTTP
+client timeout remains a transport-wide cap. Notarius does not add another
+timeout around PromptKit. Retries and repairs are serial within the same caller
+context, so their worst-case latency and cost can exceed the structural-repair
+bound above; provision run deadlines and provider budgets accordingly.
+Credentials remain optional unless the selected
 PromptKit profile requires one, in which case preparation fails before a
 provider call when its configured credential is unavailable.
 The pinned upstream boundary and profile-format links are in

docs/oss/attribution.md

@@ -0,0 +1,140 @@
+# Open Source Attribution Notices
+
+## Standard Repository Policies
+
+Material: policy documents under `docs/policy/`, adapted for this repository.
+Root `AGENTS.md` and the Policy Reading Guide in `docs/development.md`, copied
+without modification.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+License and notices: [CC BY-SA 4.0](licenses/CC-BY-SA-4.0.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843).
+
+## ConfigKit
+
+Selected module: `gitea.maximumdirect.net/eric/ConfigKit` at `v0.4.2`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL 3.0](licenses/LGPL-3.0.txt) |
+[GPL 3.0](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/67c03690181c5af8dde6be325abac241dae6732f/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/67c03690181c5af8dde6be325abac241dae6732f/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/67c03690181c5af8dde6be325abac241dae6732f).
+
+## PromptKit
+
+Selected module: `gitea.maximumdirect.net/eric/promptkit` at `v0.11.2`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL 3.0](licenses/LGPL-3.0.txt) |
+[GPL 3.0](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit/src/commit/12d6d80024e80c552d122a076c22429bf6f2f6c2/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/promptkit/src/commit/12d6d80024e80c552d122a076c22429bf6f2f6c2/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit/src/commit/12d6d80024e80c552d122a076c22429bf6f2f6c2).
+
+## PromptKit OpenRouter Catalog
+
+Selected module: `gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2` at `v2.20260926.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: MIT
+
+License and notices: [MIT](licenses/MIT.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/4f731d217e0bc39151c010f50fb5912706e7b6b3/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/4f731d217e0bc39151c010f50fb5912706e7b6b3/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/4f731d217e0bc39151c010f50fb5912706e7b6b3).
+
+## PromptKit Rakestrawhome Catalog
+
+Selected module: `gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2` at `v2.20260926.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: MIT
+
+License and notices: [MIT](licenses/MIT.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/48918a3ad39fd99843cda94a86133b1b3881d596/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/48918a3ad39fd99843cda94a86133b1b3881d596/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/48918a3ad39fd99843cda94a86133b1b3881d596).
+
+## jsonschema
+
+Selected module: `github.com/santhosh-tekuri/jsonschema/v6` at `v6.0.2`.
+
+SPDX-License-Identifier: Apache-2.0
+
+License and notices: [Apache 2.0](licenses/Apache-2.0.txt) |
+[LICENSE](https://github.com/santhosh-tekuri/jsonschema/blob/29cbed948d24a04700eb94436416b18a07953b71/LICENSE).
+
+[Source](https://github.com/santhosh-tekuri/jsonschema/commit/29cbed948d24a04700eb94436416b18a07953b71).
+
+## Go text
+
+Selected module: `golang.org/x/text` at `v0.40.0`.
+
+Copyright 2009 The Go Authors.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause.txt) |
+[LICENSE](https://github.com/golang/text/blob/724af9c35838492dcaacc1ac51a8a0187c994c54/LICENSE) |
+[PATENTS](https://github.com/golang/text/blob/724af9c35838492dcaacc1ac51a8a0187c994c54/PATENTS).
+
+[Source](https://github.com/golang/text/commit/724af9c35838492dcaacc1ac51a8a0187c994c54).
+
+## go-yaml v3
+
+Selected module: `gopkg.in/yaml.v3` at `v3.0.1`.
+
+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
+
+License and notices: [MIT](licenses/MIT-Kirill-Simonov.txt) |
+[Apache 2.0](licenses/Apache-2.0.txt) |
+[LICENSE](https://github.com/go-yaml/yaml/blob/f6f7691b1fdeb513f56608cd2c32c51f8194bf51/LICENSE) |
+[NOTICE](https://github.com/go-yaml/yaml/blob/f6f7691b1fdeb513f56608cd2c32c51f8194bf51/NOTICE).
+
+[Source](https://github.com/go-yaml/yaml/commit/f6f7691b1fdeb513f56608cd2c32c51f8194bf51).
+
+## go-yaml v4
+
+Selected module: `go.yaml.in/yaml/v4` at `v4.0.0-rc.6`.
+
+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
+
+License and notices: [MIT](licenses/MIT-Kirill-Simonov.txt) |
+[Apache 2.0](licenses/Apache-2.0.txt) |
+[LICENSE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/LICENSE) |
+[NOTICE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/NOTICE).
+
+[Source](https://github.com/yaml/go-yaml/commit/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,27 @@
+Copyright 2009 The Go Authors.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
+met:
+
+   * Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+   * 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.
+   * Neither the name of Google LLC 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
+OWNER 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/CC-BY-SA-4.0.txt

@@ -0,0 +1,170 @@
+Creative Commons Attribution-ShareAlike 4.0 International
+
+ Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.
+
+Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors.
+
+Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described.
+
+Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public.
+
+Creative Commons Attribution-ShareAlike 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions.
+
+Section 1 – Definitions.
+
+     a.	Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image.
+
+     b.	Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License.
+
+     c.	BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License.
+
+     d.	Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.
+
+     e.	Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements.
+
+     f.	Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material.
+
+     g.	License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike.
+
+     h.	Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License.
+
+     i.	Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.
+
+     j.	Licensor means the individual(s) or entity(ies) granting rights under this Public License.
+
+     k.	Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them.
+
+     l.	Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world.
+
+     m.	You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning.
+
+Section 2 – Scope.
+
+     a.	License grant.
+
+          1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:
+
+               A. reproduce and Share the Licensed Material, in whole or in part; and
+
+               B. produce, reproduce, and Share Adapted Material.
+
+          2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.
+
+          3. Term. The term of this Public License is specified in Section 6(a).
+
+          4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.
+
+          5. Downstream recipients.
+
+               A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License.
+
+               B. Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply.
+
+               C. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material.
+
+          6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i).
+
+     b.	Other rights.
+
+          1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.
+
+          2. Patent and trademark rights are not licensed under this Public License.
+
+          3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties.
+
+Section 3 – License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the following conditions.
+
+     a.	Attribution.
+
+          1. If You Share the Licensed Material (including in modified form), You must:
+
+               A. retain the following if it is supplied by the Licensor with the Licensed Material:
+
+                    i.	identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);
+
+                    ii.	a copyright notice;
+
+                    iii. a notice that refers to this Public License;
+
+                    iv.	a notice that refers to the disclaimer of warranties;
+
+                    v.	a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
+
+               B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and
+
+               C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License.
+
+          2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information.
+
+          3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable.
+
+     b.	ShareAlike.In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply.
+
+          1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.
+
+          2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material.
+
+          3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply.
+
+Section 4 – Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material:
+
+     a.	for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database;
+
+     b.	if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and
+
+     c.	You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database.
+For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights.
+
+Section 5 – Disclaimer of Warranties and Limitation of Liability.
+
+     a.	Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.
+
+     b.	To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
+
+     c.	The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
+
+Section 6 – Term and Termination.
+
+     a.	This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically.
+
+     b.	Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:
+
+          1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or
+
+          2. upon express reinstatement by the Licensor.
+
+     c.	For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License.
+
+     d.	For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License.
+
+     e.	Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
+
+Section 7 – Other Terms and Conditions.
+
+     a.	The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.
+
+     b.	Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License.
+
+Section 8 – Interpretation.
+
+     a.	For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License.
+
+     b.	To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions.
+
+     c.	No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor.
+
+     d.	Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.
+
+Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses.
+
+Creative Commons may be contacted at creativecommons.org.

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-Kirill-Simonov.txt

@@ -0,0 +1,20 @@
+Copyright (c) 2006-2010 Kirill Simonov
+Copyright (c) 2006-2011 Kirill Simonov
+
+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/oss/licenses/MIT.txt

@@ -0,0 +1,18 @@
+MIT License
+
+Copyright (c) 2026 Eric Rakestraw
+
+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,79 @@
+# Agent Policy
+
+**Base Policy Version:** 1.3
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/agents.md
+
+## Purpose
+
+Agents must read and follow these 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, commit each completed, nonempty 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.
+Complete the appropriate validation before committing. If work is incomplete or
+validation is blocked, report that state accurately.
+
+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. Preserve unrelated
+   staged and unstaged work.
+4. Review `git diff --staged` and run appropriate checks for the change. Reuse
+   successful checks for unchanged content.
+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

@@ -1,10 +1,46 @@
-# Architecture
+# Architecture Policy
 
-This document defines the intended high-level architecture of Notarius and the
-invariants that changes must preserve. Implemented component details belong in
-[Internal Overview](../internal/overview.md) and its linked documents. The
-reasoning behind significant architectural choices belongs in
-[ADRs](../adr/).
+**Base Policy Version:** 1.3
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/architecture.md
+
+## Purpose And Ownership
+
+The adopted policy defines the application's purpose and the architectural
+constraints contributors must follow. It owns system boundaries, responsibility
+and dependency rules, established invariants, and explicit non-goals.
+
+Describe the concrete package inventory and implementation mechanics in internal
+documentation. Link to canonical public contracts for their exact behavior and
+to ADRs for decision rationale.
+
+## Architectural Approach
+
+Hexagonal architecture is strongly recommended, including encapsulating external
+integrations and APIs within internal adapters. Keep domain and application
+logic independent of external integration details, and make dependency direction
+clear in the adopted policy.
+
+Implement that separation with proportionate, idiomatic code. Choose interfaces
+and package layout to serve the application's actual boundaries. Use adapters
+for collaborators with external integration responsibilities.
+
+## Adopted Constraints And Implemented Structure
+
+Architectural constraints govern current and future development. Record
+implemented structure accurately, proposals and implementation status in the
+roadmap, and significant decisions and rationale in ADRs. Describe a target
+structure as implemented when its changes land.
+
+Constraints must reflect deliberately selected requirements and decisions.
+Do not promote incidental implementation choices into architectural invariants.
+
+Notarius's fixed pipeline, artifact-family boundaries, and deployment-owned
+cache permissions are established product decisions. The linked ADRs retain
+their rationale; the [internal overview](../internal/overview.md) inventories
+their implementation.
 
 ## System Shape
 
@@ -38,35 +74,7 @@ Notarius is contract-first without being abstraction-heavy. Interfaces and
 extension points should protect demonstrated boundaries. New abstraction is not
 itself an architectural goal.
 
-## Implementation Discipline
-
-Simplify the mechanism, not the user's choices.
-
-**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.
-
-**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. Existing
-explicit contracts remain authoritative; changing or weakening one requires a
-deliberate decision rather than being inferred from this principle.
-
-[ADR-0017](../adr/0017-defer-cache-access-policy-to-deployment.md) illustrates
-these principles. Notarius previously elevated private cache creation modes
-into application policy even though Unix deployments already express access
-policy through directory permissions, process umask, setgid inheritance, and
-default ACLs. The revised design retains application-owned correctness
-boundaries while leaving deployment security policy to the operator.
+Implementation discipline is owned by [Agent Policy](agents.md).
 
 ## Layers And Dependency Direction
 
@@ -307,8 +315,30 @@ LLM provenance to make a run auditable after configuration changes. Manifests
 record identities and bounded validation summaries rather than secret, raw
 model, correction, or large payload content.
 
+## Trust Boundaries And Threat Scope
+
+Where useful, state the trust boundaries and threat scenarios relevant to the
+application's adopted requirements, along with scenarios it explicitly excludes.
+For example, distinguish handling untrusted application input from defending
+against a privileged actor concurrently modifying the host filesystem.
+
+Threat exclusions define the scope of the adopted requirements. Base defenses
+and guarantees on those requirements and raise unsettled scope for a deliberate
+decision under the [agent policy](agents.md).
+
+Keep this discussion proportionate to the application. Configuration,
+operations, and internal documents retain ownership of credential supply,
+runtime handling, and implementation mechanisms under the documentation policy.
+
 ## State, Output, And Safety
 
+Source material and model responses cross application validation boundaries.
+Host access policy belongs to the deployment; hypothetical privileged actors
+concurrently changing the filesystem do not justify new application defenses
+without an explicit decision. This scope statement does not remove the adopted
+correctness boundaries below or claim excluded scenarios cannot occur. Follow
+[Agent Policy](agents.md) when a new threat or guarantee needs a decision.
+
 Notarius exposes three filesystem surfaces with independent roots and
 lifecycle:
 
@@ -364,8 +394,9 @@ best-effort development and compilation environment, while Windows is
 unsupported. Notarius distributes source releases only: an immutable source
 tag and its checked-in release note identify a release. The project does not
 publish executable binaries, archives, installers, container images,
-checksums, signatures, or package-manager entries. Maintainer release commands
-and tag guards belong to [Source Releases](../release.md).
+checksums, signatures, or package-manager entries. [Release Policy](release.md)
+owns publication requirements and completion; maintainer commands and guards
+belong to [Source Releases](../release.md).
 
 ## Architectural Non-Goals
 

docs/policy/documentation.md

@@ -1,9 +1,15 @@
 # Documentation Policy
 
+**Base Policy Version:** 1.11
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/documentation.md
+
 ## Purpose
 
 This policy assigns each documentation topic to one canonical owner. Its goal is
-to keep Notarius documentation accurate, concise, discoverable, and resistant
+to keep this application's documentation accurate, concise, discoverable, and resistant
 to drift for users, operators, developers, integrators, and LLM coding agents.
 
 ## Core Rules
@@ -12,7 +18,7 @@ to drift for users, operators, developers, integrators, and LLM coding agents.
 
 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.
+for volatile details.
 
 Volatile details include commands, flags, configuration fields and defaults,
 module keys, schemas, file names, paths, status codes, retry behavior, and
@@ -24,36 +30,26 @@ contract, maintain it only in the owning document.
 Outside `docs/roadmap/`, documentation describes implemented behavior only.
 Partial features may be described only to their implemented boundary.
 
-ADRs are the narrow exception: an ADR 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.
+Architectural constraints may govern future changes. Describe current structure
+from implemented behavior.
 
-### Implementation Details And Policy
-
-Documentation must distinguish an explicit contract from an incidental
-implementation choice. Do not describe a restriction, guarantee, security
-policy, default, or limit as authoritative merely because the current code
-implements it. Documentation may accurately describe current behavior without
-making it a permanent requirement; distinguish descriptive behavior from
-normative policy. The
-[implementation-discipline rules](architecture.md#implementation-discipline)
-own the criteria for adopting product restrictions and for elevating behavior
-into repository policy.
+ADRs may record an accepted architectural decision before implementation. 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.
+its owned topic. Keep user and operator docs focused on using and operating the
+application. Developer docs should link to user-facing and external contracts
+for their definitions.
 
 ### 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.
+to maintained examples for complete copyable files.
 
 Examples must be valid, secret-free, and tested where practical. Commands and
 configuration used in documentation should match the application.
@@ -69,37 +65,41 @@ secret values.
 
 | Topic | Canonical owner | Owned content | Content owned elsewhere |
 | --- | --- | --- | --- |
-| Product orientation and minimal end-to-end quickstart | `README.md` | What Notarius is, why it is useful, one shortest successful invocation, and links onward. | 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, detailed change recipes. |
-| Current application architecture | `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. |
-| 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` | Discovery and precedence, file schema, fields, defaults, environment overrides, validation rules, and user-selectable module or validator keys. | Complete example files, CLI syntax, runtime state lifecycle, module implementation details. |
-| 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. |
-| Source release procedure | `docs/release.md` | Maintainer release selection, candidate validation, tagging, publication guards, verification, and immutable-tag recovery. | Product installation summary, CLI version semantics, historical release summaries, CI implementation detail. |
-| Release-note history | `docs/releases/` | One checked-in historical summary for each source release made under the procedure. The note at the immutable tag is that release's record. | Current commands, behavior, contracts, and compatibility definitions. |
-| Public HTTP contract, if introduced | `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, if a public package or API is introduced | `docs/consumers/` | Task-oriented use of the public interface, minimal client examples, and consumer responsibilities. | HTTP wire semantics, external protocol contracts, internal implementation detail. |
-| External and durable integration contracts | `docs/integrations/` | External file formats and protocols, upstream and downstream contracts, logical output bundle paths and schemas, media types, and compatibility behavior. | Physical runtime placement and lifecycle, internal transformations, CLI syntax, 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. |
+| Product orientation and minimal end-to-end quickstart | `README.md` | Purpose, value, shortest successful invocation, and navigation, including licensing and attribution. | Complete command reference, configuration reference, operational procedures, implementation detail. |
+| Contributor entry point | `docs/development.md` | Task-oriented reading guide, contributor orientation, baseline validation commands, and canonical links. | Package inventory, architecture rules, subsystem behavior, detailed change recipes. |
+| Application architecture policy | `docs/policy/architecture.md` | System shape, normative ownership, dependency direction, boundaries, invariants, safety properties, and non-goals. | Concrete package inventory, implementation mechanics, contributor procedures, decision history, future work. |
+| Policy-set provenance and upstream navigation | `docs/policy/meta.md` | Policy-set origin, local authority, adoption baselines, and upstream adoption and update links. | Task-specific reading triggers, detailed adoption procedures, and formal attribution notices. |
+| Agent policy | `docs/policy/agents.md` | Proportionate, idiomatic implementation; rules against inventing requirements, restrictions, guarantees, or policy. | Application contracts, architecture, testing policy, and contributor procedures. |
+| Documentation policy | `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 sufficiency, boundaries, doubles, coverage, regressions, and test maintenance. | Subsystem behavior, application contracts, subsystem-specific test inventories, and implementation plans. |
+| Release policy | `docs/policy/release.md` | Versioning, compatibility, release integrity and immutability, release documentation, proportionate gates, publication controls, completion, and required versus optional checks. | Repository-specific commands, product installation guidance, CLI version semantics, historical release summaries, and CI implementation detail. |
+| Open source licensing and attribution policy | `docs/policy/oss.md` | License defaults and author choices, COPYRIGHT and attribution formats, license/notice links, discoverability, maintenance, and concrete exceptions. | Component entries, license texts, release commands, and dependency security review. |
+| Project copyright and license grant | `COPYRIGHT` | Project identity, copyright holders and years, SPDX expression, grant, warranty disclaimer, and third-party statement. | Complete license texts and upstream component attribution. |
+| Project license texts | `LICENSE` | Complete project and incorporated companion license texts, with required project-specific fields. | General licensing policy and upstream component attribution. |
+| Upstream component attribution | `docs/oss/attribution.md` | House Format component entries: identity, material scope and modifications where applicable, copyright, license, required notices, and license, notice, and source links. | General attribution policy, exception reasoning, research narratives, compliance commentary, and complete standard license texts. |
+| Standard dependency license texts | `docs/oss/licenses/` | Complete, verbatim standard license texts shared by applicable entries. | Project-specific upstream notices, attribution prose, and policy interpretation. |
+| Repository-specific release procedure | `docs/release.md` | Maintainer prerequisites, candidate preparation, validation and source-only publication commands and automated guards, optional consumer verification, and recovery. | General release requirements, product installation guidance, historical release summaries, and current compatibility contracts. |
+| CLI contract (if applicable) | `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 (if applicable) | `docs/config.md` | Discovery, precedence, schema, fields, defaults, environment overrides, validation, and selectable module and validator keys. | Complete example files, CLI syntax, runtime state lifecycle, module implementation details. |
+| Operations (if applicable) | `docs/operations.md` | Runtime workflows, physical filesystem and state layout, output, cache and debug handling, resume, cleanup, permissions, recovery, and limits. | CLI flag syntax, configuration field definitions, logical output schemas, implementation mechanics. |
+| Subprocess consumer guidance | `docs/consumers/` | Task-oriented subprocess use, minimal examples, and consumer responsibilities. | CLI invocation semantics, external protocol contracts, internal implementation detail. |
+| Integration contracts for external components (if applicable) | `docs/integrations/` | External formats and protocols, upstream and downstream contracts, logical output paths and schemas, media types, and compatibility. | Physical runtime placement and lifecycle, internal transformations, CLI syntax, configuration defaults. |
+| Inventory of implemented internal packages | `docs/internal/overview.md` | Implemented packages and components, responsibilities, and links to focused internal docs. | Normative architecture, contributor reading policy, external contracts. |
+| Behavior and architecture of internal packages | Other files under `docs/internal/` | Implementation flow, collaborators, state transitions, package-local guarantees and failures, and relevant tests. | Global architecture invariants, configuration definitions and defaults, external schemas, operator procedures. |
+| Architectural decision records | `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. |
+| Release-note history | `docs/releases/` | One checked-in summary per source release under the procedure; the note at its immutable tag is the release record. | Current commands, behavior, contracts, and compatibility definitions. |
+| Complete copyable artifacts | `examples/` | Maintained configuration, inputs, and other copyable or runnable files. | 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.
+Create supporting documents for existing interfaces and responsibilities when
+substantive content is available.
 
 ## 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.
+Link among orientation, architecture, and internal documents; maintain each
+package or behavior description in its canonical owner.
 
 ### Commands, Configuration, And Operations
 
@@ -111,16 +111,23 @@ other contracts.
 
 ### Releases
 
-`docs/release.md` owns the source-release procedure. Release notes are
-historical summaries, not current-state contract owners: the checked-in note at
-an immutable tag records that release, while current canonical documentation
-must change with the behavior it describes. Do not use a release note to defer
-or replace current documentation updates.
+The release policy defines requirements and invariants that every release must
+satisfy. The repository-specific release procedure defines the commands and
+workflow maintainers use to satisfy that policy. Release notes record history
+at immutable tags. Maintain current behavior in its canonical documentation,
+update it with the corresponding behavior changes, and keep release procedures
+consistent with adopted policy.
+
+### Project Licensing And Upstream Attribution
+
+README and release documents link to the canonical licensing and attribution
+materials under the [OSS policy](oss.md). 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 Notarius implements or consumes those
+semantics. Internal documents explain how this application 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.
 

docs/policy/meta.md

@@ -0,0 +1,27 @@
+# Policy Set Provenance
+
+**Base Policy Version:** 1.0
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/meta.md
+
+## Origin And Local Authority
+
+This repository's policy set is adapted from
+[Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy).
+The adopted local policies govern work in this repository. Upstream revisions
+become local policy through deliberate adoption, preserving local decisions.
+Each policy's `Upstream Source` identifies its adopted baseline.
+
+## Adoption And Updates
+
+For policy adoption, upstream revision reviews, and updates, consult the
+[upstream adoption and update guide](https://gitea.maximumdirect.net/eric/policy/src/branch/main/docs/adoption.md).
+That guide and the reference example collection are maintained upstream and
+accessed through links. Keep discovery links pointed at the current upstream
+project and guide; keep adopted-source and example links pinned to commits.
+
+The local [developer guide](../development.md) routes tasks to applicable
+policies. Formal credit and licensing notices for the copied policy material
+belong in the local [attribution document](../oss/attribution.md).

docs/policy/oss.md

@@ -0,0 +1,218 @@
+# Open Source Licensing And Attribution Policy
+
+**Base Policy Version:** 1.8
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/oss.md
+
+## Purpose And Scope
+
+This policy defines project licensing conventions and a repeatable House Format
+for upstream attribution and license notices. It covers the project's own code
+and upstream components incorporated into or distributed with the application
+or library, including relevant transitive dependencies and copied code,
+documentation, or assets.
+Determine treatment from the component's terms and actual use.
+
+Consulting development guidance or using tooling alone does not require an
+attribution entry. Copying or adapting documentation for inclusion in the
+repository is different: preserve its applicable attribution and license terms.
+A material's role as development guidance does not exempt copied documents.
+Apply any express permissions for attribution-free reuse of example formatting.
+
+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 every obligation arising from use or distribution.
+
+## Canonical Locations
+
+The [documentation policy](documentation.md) assigns ownership:
+
+- `COPYRIGHT`: project name, copyright statements, SPDX expression, grant,
+  warranty disclaimer, and third-party statement.
+- `LICENSE` contains the complete, unmodified project license text, including
+  incorporated companion text. Dependency attribution does not relicense the project.
+- `docs/oss/attribution.md`: canonical component entries.
+- `docs/oss/licenses/`: complete, verbatim standard and applicable companion texts.
+
+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.
+
+## Upstream Reference Examples
+
+Use the commit-pinned upstream examples to create actual project notices.
+Retain their links and keep the example collection upstream; keep applicable
+license texts locally as specified above.
+
+## Project Licensing
+
+Notarius's selected application grant is `GPL-3.0-or-later`, recorded in
+[COPYRIGHT](../../COPYRIGHT).
+
+Unless the author specifies otherwise, use **GPL version 3 or later**
+(`GPL-3.0-or-later`) for applications and **LGPL version 3 or later**
+(`LGPL-3.0-or-later`) for libraries. An author's explicit choice takes precedence:
+for example, a one-off script may use MIT. Such a choice requires no exception
+rationale, additional approval, or compensating controls under this policy.
+
+These defaults guide new license selection. Adopting this policy does not
+relicense existing code or override third-party terms. Preserve an existing
+license unless the author deliberately changes it. For mixed-purpose projects,
+follow the author's selected scope rather than inferring different licenses for
+individual packages.
+
+Use the upstream [application COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/application/COPYRIGHT)
+or [library COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/library/COPYRIGHT)
+to create the project’s root `COPYRIGHT` file.
+Use verified project names, contribution years, and copyright holders.
+For another selected license, adapt the grant, SPDX expression, disclaimer, and
+text references together to reflect the author's selected grant.
+
+For GPLv3 projects, copy the complete GPLv3 text into `LICENSE`. For LGPLv3
+projects, place the complete LGPLv3 text followed by the complete GPLv3 text in
+`LICENSE`; the LGPL incorporates the GPL terms. Keep the texts unmodified and
+place project-specific statements in `COPYRIGHT`. For the default grants, the
+grant and SPDX expression in `COPYRIGHT` must expressly identify `or-later`;
+follow the author’s choice if a different grant is selected.
+
+For other licenses, provide their complete text and any required project-specific
+fields; the standard reference collection remains unchanged. Keep `COPYRIGHT`,
+`LICENSE`, SPDX expressions, and README descriptions consistent with the actual
+grant. This convention introduces no blanket requirement for per-file headers;
+preserve notices or add them where the applicable terms require them.
+
+Identify separately licensed documentation or assets in the project grant, with
+links to their attribution and license information. An application's default
+code license does not override the terms of incorporated documentation.
+
+## Upstream Attribution House Format
+
+Begin `docs/oss/attribution.md` with `# Open Source Attribution Notices`,
+followed directly by component entries. These comprise the complete document.
+
+Each entry presents these five fields in order, with blank lines between them:
+
+1. **Project name** as a level-two heading. An optional identification paragraph
+   may follow, such as `Selected module: MODULE at VERSION.` with the module and
+   version in backticks. For copied documentation, a concise `Material:` sentence
+   may identify the affected files and whether they were adapted or copied
+   without modification. A factual qualifier such as `(transitive dependency)`
+   is permitted. Limit optional identification prose to factual component and
+   material scope.
+2. **Upstream copyright statement or statements**, preserving their wording.
+   Put multiple statements in separate paragraphs. Include this field when the
+   selected upstream source supplies an applicable statement; otherwise, omit it.
+3. **SPDX license identifier or expression**, when applicable, using
+   `SPDX-License-Identifier: EXPRESSION`.
+4. **License and notice links**, beginning `License and notices:`, separated
+   by ` | `, and ending with a period. Label local standard texts by license
+   name, such as `MIT` or `Apache 2.0`. Label upstream files by their actual
+   filenames, such as `COPYRIGHT`, `LICENSE`, `NOTICE`, or `PATENTS`.
+5. **Source repository link**, rendered exactly as `[Source](COMMIT_URL).`.
+
+Use the upstream [attribution example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/attribution.md)
+to create the project’s `docs/oss/attribution.md`.
+The example illustrates omitted fields and multiple copyrights and licenses.
+Replace the uppercase placeholders and illustrative URLs with actual component
+information. Local license links are relative to the destination
+`docs/oss/attribution.md`; copy the applicable texts into its `licenses/`
+directory. Do not copy example entries for components the project does not use.
+
+These are five fields, not a line limit. Omit the SPDX field when no applicable
+identifier exists; identify nonstandard terms through the linked text. Preserve
+licensing alternatives and exceptions, and record a selected option when
+relevant through the factual license identification. Do not invent an identifier
+or silently resolve an unsettled licensing choice.
+
+Keep entries factual. Do not add agent-authored explanations of license
+expressions, file-level license scope, research performed, retained source
+notices, or compliance conclusions. Avoid filler such as "none is invented
+here" and embellished link labels such as "upstream LICENSE", "additional
+patent grant", or "at the imported commit". Preserve actual required upstream
+content; this rule excludes editorial additions, not required notices. Policy
+interpretation and exception reasoning belong in the adopted OSS policy or an
+appropriate decision record, not the attribution document.
+
+## License Texts And Upstream Links
+
+Link standard license texts to their local copies. Link project-specific
+notices to their upstream copies. Every upstream repository or notice link must
+identify the exact commit corresponding to the
+imported version, including the selected source revision for copied material.
+
+Classify material according to its contents. 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.
+
+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
+grant in `COPYRIGHT` and the attribution document. For example, for a project
+with the stated license:
+
+```markdown
+PROJECT_NAME is licensed under the [LGPL v3.0 or later](COPYRIGHT).
+
+[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 `COPYRIGHT | 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.
+
+For Notarius, the [release runbook](../release.md) owns the concrete source-only
+publication process and release navigation.
+
+## Maintenance And Exceptions
+
+Update project licensing statements together when the author changes the grant
+or its scope. Update upstream 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 OSS policy or an appropriate decision record. Attribution entries
+contain the resulting factual identification and required material, without
+repeating that reasoning. 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,204 @@
+# Release Policy
+
+**Base Policy Version:** 1.4
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/release.md
+
+## 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` and the authoritative remote is `origin`.
+Tags are lightweight. Publish the candidate to `main` before pushing its tag.
+
+A successful push of the intended tag, with its source commit available on the
+authoritative primary branch, completes the release. Notarius uses
+branch-before-tag publication; it does not require an atomic push.
+
+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.
+
+Notarius publishes source only: no binaries, archives, images, packages,
+checksums, signatures, or Gitea release objects. Tag CI may provide advisory
+validation but publishes no deliverables and is not a completion gate.
+
+## Versioning And Compatibility
+
+Stable releases use Semantic Versioning in the form `vMAJOR.MINOR.PATCH`, with
+no leading zeroes. Notarius does not support prereleases.
+
+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. Choose sections suited to the release and keep the note
+proportionate to the change.
+
+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.
+
+Include the release footer defined by the [OSS policy](oss.md#discoverability)
+in each new release document. The [release procedure](../release.md) defines
+its concrete immutable-tag URLs. Notarius has no hosted download page; preparing
+these links with the note does not add a network check or approval gate.
+
+Do not create retrospective notes for the pre-procedure v0.1.0, v0.2.0, or
+v0.3.0 tags.
+
+Handle version selection, release-note content, and retirement of completed
+roadmaps during preparation. Preserve planned and deferred work and repair
+affected links when retiring roadmaps. Reuse ordinary change review for
+unintended files, credentials, and private data. Scope release-content review
+to 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). For repositories that
+publish builds, 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.
+
+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 may describe 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.
+
+### Notarius Gate Selection
+
+Run the default offline Go suite once and build the native `cmd/notarius` with
+release version injection, checking its `--version` output. The command check
+protects the actual executable entry point and linker-supplied version, which
+package tests alone do not verify. Build products are temporary, not published.
+Use `GOWORK=off` so a sibling checkout cannot substitute for declared dependencies.
+
+Race tests, standalone vet, formatting/whitespace checks, module tidy audits,
+standalone example validation, and Linux/Darwin cross-builds remain useful
+change-specific development checks, not mandatory release gates. Default tests
+already cover maintained examples. Source-only publication does not require a
+binary distribution matrix. No new platform or hardware prerequisites are added.
+
+## 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 branch push advances authoritative `main` to the candidate without
+  discarding remote history, before the tag is published; 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. Advisory CI or optional installation checks
+may be retried against the same immutable tag. Notarius has no asynchronous
+artifact delivery to recover.
+
+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. source-only delivery, required build targets, and automation responsibilities;
+5. the successful-push completion point; and
+6. failure handling and ambiguous-push recovery.
+
+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

@@ -1,39 +1,32 @@
 # Testing Policy
 
+**Base Policy Version:** 1.3
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/testing.md
+
 ## 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.
+We optimize for sufficient confidence in important behavior while minimizing friction on future development.
 
 ## Every test has a cost
 
-Testing is not an unqualified good. Every test imposes both an immediate cost and a continuing lifetime cost.
-
-A test must be:
-
-- written and reviewed;
-- understood by future maintainers and coding agents;
-- executed in local and CI workflows;
-- diagnosed when it fails;
-- updated when legitimate behavior changes;
-- maintained as fixtures, APIs, and dependencies evolve; and
-- removed or rewritten when it becomes redundant, brittle, misleading, or obsolete.
-
-Tests also create cognitive and architectural friction. They can constrain refactoring, duplicate policy, slow feedback loops, add noise to failures, and cause harmless implementation changes to require unrelated edits across the suite.
+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.
-
-Apply this cost-benefit analysis at two levels:
+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?
 
-The preferred test suite is a **lean suite that provides sufficient confidence in the risks that matter, without redundant or low-value tests**. We seek sufficient confidence with the least unnecessary testing friction, not the fewest possible tests.
+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. Keep ordinary internal changes inexpensive.
 
-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.
+Evaluate maintenance cost against the specific failure being protected. 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
 
@@ -55,7 +48,7 @@ Control clocks, randomness, environment variables, and other process-global or m
 
 ## What deserves tests
 
-Prioritize tests for:
+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.
@@ -65,15 +58,27 @@ Prioritize tests for:
 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.
+A package-level contract comprises behavior relied upon by another package or major collaborator.
 
-For behavior involving **data integrity, destructive operations, compatibility, security, concurrency, idempotency, or recovery**, presume that durable tests are required unless the behavior is already credibly protected at another layer.
+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.
+Choose the narrowest stable boundary that expresses the behavior clearly and
+provides durable confidence with minimal incidental coupling.
 
 This is often the package API, but it may instead be:
 
@@ -81,35 +86,15 @@ This is often the package API, but it may instead be:
 - 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—not memorialize the current implementation.
+A test should protect a selected decision, contract, or invariant.
 
-Tests must not create a stronger product contract than the requirement they
-protect. In particular, do not turn an incidental limit, restriction,
-permission choice, validation rule, or implementation default into policy by
-asserting it without an expressly selected contract. Follow the
-[implementation-discipline rules](architecture.md#implementation-discipline)
-when deciding what behavior deserves durable protection.
+A test is suspect when it primarily detects changes to private constants or
+helpers, equivalent operation ordering, incidental formatting, equivalent
+algorithms, or internal structure that preserves behavior.
 
-Before adding or retaining a test, ask:
-
-> What realistic defect would this test catch?
-
-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.
-
-A test can be factually correct and still have negative value. Accurately describing current behavior is not enough; the protected behavior must be important enough to justify the future friction.
+Behavioral tests should normally remain stable through internal refactoring that preserves the contract.
 
 ## Expected effects of different changes
 
@@ -126,12 +111,13 @@ A test failing is not the same as a test needing to be edited. Many tests may co
 
 ## Separate mechanism from policy
 
-Configurable thresholds and defaults must not be duplicated throughout the test suite.
+Derive expectations from test-controlled configuration and relationships.
 
-For example, do not encode an internal concurrency limit indirectly:
+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 policy:
+// Production default:
 const maxConcurrency = 4
 
 // Brittle test:
@@ -149,25 +135,30 @@ require.NoError(t, runner.Start(limit))
 require.ErrorIs(t, runner.Start(limit+1), ErrTooMuchConcurrency)
 ```
 
-The test should prove:
+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.
+Apply the same rule to limits, timeouts, capacities, retry counts, and ranges: test relationships and behavior.
 
-For concurrency limits, test both kinds of behavior when relevant:
+For established concurrency limits, distinguish these behaviors where the contract requires them:
 
-1. **Configuration enforcement:** invalid or excessive requested values are handled correctly.
+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.
+Use a test-controlled limit and measure the behavior relative to that limit.
 
-## Avoid semantic duplication across layers
+## Assign each behavior a test owner
 
-Each behavior should have a clear test owner.
+Where these layers exist, assign ownership as follows:
 
 - Parser tests own parsing cases.
 - Validator tests own validation rules.
@@ -177,9 +168,7 @@ Each behavior should have a clear test owner.
 - CLI tests own argument and configuration mapping.
 - End-to-end tests prove that representative assembled workflows work.
 
-Higher-level tests should not repeat every lower-level case. A single intentional policy change should not require unrelated edits across many test files.
-
-Tests that are individually reasonable may still be collectively redundant. Evaluate the marginal value of each additional test in light of the protection already provided by the rest of the suite.
+Give each layer its distinct responsibility and keep expectation updates localized to the contract being changed.
 
 ## Use test doubles deliberately
 
@@ -200,104 +189,76 @@ Mocks are appropriate when the contract includes facts such as:
 - 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
 
-Use:
+Select techniques by behavior and risk:
 
 - table-driven tests for meaningful behavioral categories and boundaries;
 - `t.TempDir()` for real filesystem behavior;
 - `httptest.Server` for realistic HTTP interactions;
-- fuzz tests for parsers, normalization, path handling, and broad input spaces;
+- 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.
+- 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.
+Prefer `errors.Is`, `errors.As`, typed errors, or structured error fields. Use exact error-wording assertions only when the wording is contractual.
 
-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.
+At CLI boundaries, prefer exit classifications, structured output, and the smallest stable semantic fragment needed to identify the error. Use complete diagnostic snapshots only when the wording 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.
+Keep tests readable and direct. Size test helpers and fixture frameworks to the maintenance benefit they provide.
 
 ## 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.
+Use coverage to locate untested critical branches and unexpectedly weak packages. Evaluate test quality through meaningful behavioral protection and choose coverage according to risk.
 
 Pure domain logic will often warrant higher coverage than CLI wiring or external adapters. Uneven coverage is acceptable when it reflects risk.
 
-Increasing coverage is valuable only when the newly covered behavior protects a meaningful risk at an acceptable cost.
-
 ## 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.
+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.
 
-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.
+Remove or consolidate a test when the underlying design has made recurrence impossible, its protection is redundant, or a stronger invariant test subsumes 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.
+Delete or rewrite tests when maintenance cost exceeds their continuing
+protective value.
 
 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;
+- assert incidental private constants or snapshot large amounts of incidental output;
 - 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;
+- duplicate policy across layers, retest trivial helpers covered by package
+  behavior, or protect risks 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.
-
-Deleting a low-value test can improve the quality of the suite by reducing noise, maintenance burden, and friction around legitimate change.
+Several brittle tests may encode one genuine requirement. Consolidate them into one durable behavior-level or invariant test.
 
 ## 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.
+Use the following questions when a proposed test needs closer evaluation. Significant test additions should be reviewable against them; written answers are optional for routine tests.
 
-1. What realistic defect would it catch?
-2. How likely is that defect?
-3. How consequential would it be?
-4. Is the behavior already protected elsewhere?
-5. At which layer should this behavior be owned?
-6. Does the test assert a durable contract or an incidental implementation detail?
-7. Could the implementation be refactored without changing the behavior and without editing this test?
-8. What should cause this test to fail?
-9. What legitimate changes should not cause this test to fail?
-10. What ongoing maintenance, execution, and diagnostic cost will the test impose?
-11. Is there a smaller or more direct test that protects the same risk?
-
-Do not add the test when its expected lifetime cost exceeds its expected protective value.
-
-When deciding not to test plausible behavior, record or be able to explain why the risk is low, already protected, obvious, reversible, or cheaper to detect elsewhere.
+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 contracts and invariants are protected;
-- meaningful boundaries and failure modes are exercised;
-- realistic and consequential regressions are credibly protected against silent recurrence;
-- behavior involving data integrity, destructive operations, compatibility, security, concurrency, idempotency, and recovery is credibly protected;
-- important external boundaries have realistic integration coverage;
-- representative complete workflows are tested;
-- failures provide useful signal rather than redundant noise;
-- legitimate internal changes usually do not require test edits; and
+- 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, distinct signals;
+- tests usually remain stable through legitimate internal changes; and
 - additional tests would mostly repeat existing protection or preserve inconsequential implementation details.
 
-Sufficiency is a risk judgment, not a coverage percentage or test count. Reassess it as the application, its users, and the consequences of failure evolve.
-
-The governing rule is:
-
-> Test heavily where failure is consequential, subtle, or difficult to detect after the fact. Test lightly where failure is obvious, reversible, and inexpensive—and retain no test whose lifetime cost exceeds the confidence it provides.
+Reassess sufficiency as the application, its users, and the consequences of
+failure evolve.

docs/release.md

@@ -1,164 +1,93 @@
 # Source Releases
 
-This procedure is for maintainers publishing Notarius source releases. A
-release is an immutable lightweight `vMAJOR.MINOR.PATCH` tag on `main` together
-with its checked-in `docs/releases/<tag>.md` note. Tag CI validates that source
-candidate after publication; it does not publish or repair a release.
+This is the executable runbook for [Release Policy](policy/release.md).
+Notarius publishes an immutable lightweight tag and its checked-in release note,
+not binaries or Gitea release objects. Linux is supported; macOS is best-effort
+for development, and Windows is unsupported. `main` on `origin` is authoritative.
 
-Notarius publishes no binaries, archives, checksums, signatures, containers,
-package-manager entries, or Gitea release objects. Windows is not supported.
-Do not create retrospective notes for the pre-procedure `v0.1.0`, `v0.2.0`, or
-`v0.3.0` tags.
+## Prepare
 
-## Select And Describe The Release
+Use Git, a POSIX shell, and Go 1.25.5 or newer. Configure ordinary Git credentials
+for `origin` and private-module access without putting secrets in the repository.
+Prepare dependencies before offline validation where necessary:
 
-Choose an unused stable semantic version in the form `vMAJOR.MINOR.PATCH`.
-Prereleases are not supported. Before `v1.0.0`, a minor release may change a
-documented CLI, configuration, durable artifact, integration, or operating
-contract when its note explains the impact and required operator action. A
-patch release must not intentionally break those documented contracts within
-its minor line.
+```sh
+GOWORK=off GOPRIVATE=gitea.maximumdirect.net go mod download
+```
 
-Create the version-matched note as part of the candidate. Every new note uses
-this structure, with concise, truthful content in each section:
+Choose an unused stable version under the policy's compatibility rules. Add
+`docs/releases/<version>.md`, starting with `# Notarius <version>`, with a concise
+summary and relevant compatibility/upgrade information. No fixed section list is
+required. Update current documentation with behavior changes; retire only
+completed roadmaps and preserve planned/deferred work. Commit the candidate on
+`main` after ordinary change review. There is no separate release sign-off.
+
+End each new release note with this footer, replacing `<version>` with the
+selected tag. Check that `COPYRIGHT`, `LICENSE`, and `docs/oss/attribution.md`
+exist in the candidate source before publication; the future tag need not
+resolve remotely during preparation.
 
 ```markdown
-# Notarius vMAJOR.MINOR.PATCH
-
-This release ...
-
-## Summary
-
-## Compatibility
-
-## Upgrade
-
-## Changes
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/notarius/src/tag/<version>/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/notarius/src/tag/<version>/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/notarius/src/tag/<version>/docs/oss/attribution.md)
 ```
 
-The note is a historical summary. Link to current canonical documentation for
-exact behavior, and update that documentation in the candidate rather than
-using the note as a substitute.
+## Publish
 
-## Prepare The Candidate
-
-Set the selected release version and disable Go workspace use for every
-candidate command:
+Run one command from the repository with the actual selected version:
 
 ```sh
-RELEASE_VERSION=vMAJOR.MINOR.PATCH
-export RELEASE_VERSION GOWORK=off
+./scripts/release.sh vMAJOR.MINOR.PATCH
 ```
 
-Run the shared source-candidate checks from the repository. They cover module
-hygiene, tests, race tests, vet, builds, formatting, whitespace, maintained
-configuration validation, and the Linux and Darwin command-build matrix:
+The command checks version availability on `origin`, branch and worktree state,
+and the matching note. It runs the complete offline default test suite once and
+a native CLI build/version check with `GOWORK=off`. The
+[gate rationale](policy/release.md#notarius-gate-selection) explains the selected
+checks. It then rechecks candidate and publication state, pushes the exact
+candidate to `main` without force, creates a lightweight tag, and pushes only
+that tag. It neither rewrites history nor publishes other local tags.
+
+A successful tag push completes the source release. The command does not wait
+for CI or verify consumer installation/module availability. Tag CI is advisory
+validation only; there are no asynchronous deliverables to await.
+
+## Failure And Recovery
+
+Before publication, correct failed checks, commit any changes, and rerun the
+command. If the candidate changes during validation, validation must run again
+on the new candidate. A failed branch push publishes no tag.
+
+On a failed or ambiguous push, the command queries the affected remote ref. If
+a tag push reports failure but the intended lightweight tag is confirmed on the
+remote, publication succeeded. Otherwise it stops and reports failure or unknown
+status, leaving any local tag intact for inspection. Do not blindly rerun, force
+push, or delete a possibly published tag.
+
+Inspect authoritative state before retrying:
 
 ```sh
-./scripts/check-release-source.sh "$RELEASE_VERSION"
+git ls-remote origin refs/heads/main refs/tags/vMAJOR.MINOR.PATCH
+git rev-parse vMAJOR.MINOR.PATCH
 ```
 
-Before committing, manually follow every changed local Markdown link and
-review the candidate for unintended files, generated output, credentials, or
-other unrelated changes. Commit the release note and all affected current
-documentation, then run the shared checker against that exact candidate. Push
-the candidate commit to `main` only after it succeeds. Record the exact commit
-only after that push:
+If the intended tag exists remotely, leave it immutable. If it is absent and
+you have confirmed that the local tag was never published or used by a release
+channel, remove only that unpublished local tag, then rerun the command. A
+failed remote query is not proof of absence. Network/authentication failures
+alone do not require a new version. A defect requiring changes to published
+source requires a new semantically appropriate version and matching note.
 
-```sh
-RELEASE_COMMIT=$(git rev-parse 'HEAD^{commit}')
-export RELEASE_COMMIT
-```
+## Optional Diagnostics
 
-For private-module installation, configure standard `GOPRIVATE` matching this
-module and ordinary Git authentication for the hosting service before running
-the verification below. The exact authentication mechanism belongs to the
-maintainer environment; never record credentials or environment dumps in a
-release note, command history, or repository file.
+`./scripts/check-release-source.sh <version>` runs validation without publication.
+It is useful for diagnosis, but is not a required preliminary step that must
+repeat the publication command's checks.
 
-## Guard And Publish The Tag
+Race tests, vet, module hygiene, formatting, example checks, and cross-builds may
+be run when relevant to a change; they are not additional release gates. The
+development guide and testing policy govern change-specific verification.
 
-Fetch current remote references, then run this guard without editing the
-candidate. It requires `main`, a clean worktree and index, disabled workspace
-use, a stable release version, the recorded and pushed commit, a matching note,
-and unused local and remote tags:
-
-```sh
-git fetch origin main --tags
-
-if ! printf '%s\n' "$RELEASE_VERSION" |
-  grep -E -x 'v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)' >/dev/null
-then
-  printf '%s\n' "invalid release version: $RELEASE_VERSION" >&2
-  exit 1
-fi
-test "$GOWORK" = off
-test "$(git branch --show-current)" = main
-test -z "$(git status --porcelain)"
-test "$RELEASE_COMMIT" = "$(git rev-parse 'HEAD^{commit}')"
-test "$RELEASE_COMMIT" = "$(git rev-parse 'origin/main^{commit}')"
-test -s "docs/releases/$RELEASE_VERSION.md"
-grep -F -x "# Notarius $RELEASE_VERSION" "docs/releases/$RELEASE_VERSION.md"
-for heading in '## Summary' '## Compatibility' '## Upgrade' '## Changes'; do
-  grep -F -x "$heading" "docs/releases/$RELEASE_VERSION.md"
-done
-if git rev-parse -q --verify "refs/tags/$RELEASE_VERSION" >/dev/null; then
-  printf '%s\n' "local tag already exists: $RELEASE_VERSION" >&2
-  exit 1
-fi
-if git ls-remote --exit-code --tags origin "refs/tags/$RELEASE_VERSION" >/dev/null 2>&1; then
-  printf '%s\n' "remote tag already exists: $RELEASE_VERSION" >&2
-  exit 1
-fi
-```
-
-Create an explicitly lightweight tag against the guarded commit, verify its
-target, and push only that tag ref:
-
-```sh
-git -c tag.gpgSign=false tag "$RELEASE_VERSION" "$RELEASE_COMMIT"
-test "$(git cat-file -t "$RELEASE_VERSION")" = commit
-test "$(git rev-parse "$RELEASE_VERSION^{commit}")" = "$RELEASE_COMMIT"
-git push origin "refs/tags/$RELEASE_VERSION:refs/tags/$RELEASE_VERSION"
-```
-
-Never use `git push --tags`, move a published tag, or delete a published tag.
-
-## Verify The Published Release
-
-Confirm that the remote tag still points at the guarded commit and that the
-note is available from the tagged tree:
-
-```sh
-REMOTE_TAG_COMMIT=$(git ls-remote origin "refs/tags/$RELEASE_VERSION" | awk '{print $1}')
-test "$REMOTE_TAG_COMMIT" = "$RELEASE_COMMIT"
-git show "$RELEASE_VERSION:docs/releases/$RELEASE_VERSION.md" >/dev/null
-```
-
-Verify a fresh source installation and its diagnostic version. The temporary
-directory confines the installed command to this check:
-
-```sh
-release_verification_dir=$(mktemp -d)
-trap 'rm -rf "$release_verification_dir"' 0 HUP INT TERM
-mkdir -p "$release_verification_dir/bin"
-GOWORK=off GOBIN="$release_verification_dir/bin" go install \
-  "gitea.maximumdirect.net/eric/notarius/cmd/notarius@$RELEASE_VERSION"
-test "$("$release_verification_dir/bin/notarius" --version)" = "notarius $RELEASE_VERSION"
-```
-
-An exact fresh checkout and `GOWORK=off go build ./cmd/notarius` is an
-equivalent source verification when local installation policy requires it.
-`notarius --version` is diagnostic only; downstream compatibility remains
-defined by the published receipt and artifact contracts.
-
-## Failure And Correction Policy
-
-If candidate validation fails before publication, fix the candidate on `main`,
-rerun the shared checker, and repeat the guards. An unpublished local tag may
-be deleted after inspection.
-
-If the remote tag or tag CI reveals a defect, leave the published tag intact.
-Fix the defect on `main`, choose a new patch version, write a new matching
-note, and repeat this procedure. Do not weaken tag immutability or add release
-assets as a workaround.
+A fresh source install or exact-tag checkout/build may be used to investigate
+consumer availability after release. Such checks are optional and do not delay
+or reverse release completion. `notarius --version` is diagnostic; subprocess
+compatibility is defined by the receipt and artifact contracts.

docs/releases/v0.7.1.md

@@ -0,0 +1,44 @@
+# Notarius v0.7.1
+
+This release updates the prompt engine and its provider catalogs while retaining
+Notarius's application-owned D&D defaults and subprocess contracts.
+
+## Summary
+
+- Upgrade PromptKit from v0.9.0 to v0.10.0 and adopt its selected provider catalogs.
+- Refresh the profile-source checkpoint identity for the updated catalog.
+- Document profile ownership and upstream catalog compatibility.
+
+## Compatibility
+
+Notarius's CLI, configuration schema, durable artifact formats, and subprocess
+receipt are unchanged. The `dnd-extraction` fallback retains its explicit model
+and settings; the upgrade does not switch it to an upstream default profile.
+
+Upstream catalog selections require review: `deepseek-3-2`, `deepseek-4-flash`,
+and `deepseek-4-pro` are no longer present. Operators selecting or inheriting
+those profiles must supply a complete operator-owned definition or select an
+available profile. `deepseek-flash-latest` and `deepseek-pro-latest` are not
+equivalent aliases and need not preserve previous settings. See the
+[PromptKit integration contract](../integrations/pkg-promptkit.md#profile-sources-and-compatibility).
+
+Existing checkpoints with the previous profile-source identity are not reused.
+Source-keyed chunk plans and existing output artifacts are unaffected.
+
+## Upgrade
+
+Review selected LLM profile IDs and inherited bases before rebuilding from this
+tag. No Notarius configuration migration is required for the maintained examples
+or application-owned D&D defaults. For controlled model settings, use a complete
+[operator profile](../config.md#promptkit-profiles), rather than inheriting a
+volatile catalog entry. Follow the [source release procedure](../release.md)
+for source installation and verification.
+
+## Changes
+
+- PromptKit v0.10.0 preserves the public engine API and adds two opt-in maintained
+  profile names; Notarius continues using its existing adapter and defaults.
+- The dependency graph selects OpenRouter catalog v2.20260922.1 and Rakestrawhome
+  catalog v2.20260922.0.
+- Profile checkpoint fingerprinting and current integration documentation now
+  identify the updated engine.

docs/releases/v0.8.0.md

@@ -0,0 +1,31 @@
+# Notarius v0.8.0
+
+This release upgrades ConfigKit and PromptKit and makes provider retry behavior
+explicit, inspectable, and available in debug diagnostics.
+
+## Compatibility
+
+Configuration selection now uses `--config-overlay` and
+`overlays/<name>.yml`. The retired `--config-profile` flag and
+`profiles/<name>.yml` lookup are no longer accepted. PromptKit LLM profiles are
+unchanged.
+
+`promptkit.transient_retries` defaults to two additional eligible transient
+HTTP attempts per generation. Set it to `0` to disable built-in transient
+retries. Existing pipeline and validator retry settings remain separate.
+
+## Upgrade
+
+Move selected configuration files from `profiles/` to `overlays/` and replace
+every `--config-profile` invocation with `--config-overlay`. Review retry and
+timeout budgets before deployment, especially where providers charge per
+attempt. See [Configuration](../config.md), [Operations](../operations.md), and
+the [PromptKit integration contract](../integrations/pkg-promptkit.md).
+
+## Changes
+
+- Upgrade ConfigKit to v0.4.0 and PromptKit to v0.11.0.
+- Add application-owned generation failure and request-local execution-summary
+  metadata, including retry exhaustion details.
+- Record execution summaries in existing debug response artifacts and safe
+  per-call references.

docs/releases/v0.8.1.md

@@ -0,0 +1,23 @@
+# Notarius v0.8.1
+
+This patch release refreshes ConfigKit and PromptKit and makes the project's
+licensing, policy provenance, and upstream attribution easier to find.
+
+## Changes
+
+- Update ConfigKit to v0.4.2 and PromptKit to v0.11.2. These upstream patches
+  update release tooling and policy or licensing documentation without changing
+  the Notarius integration APIs or configured profile settings.
+- Refresh the PromptKit built-in profile-source checkpoint identity for the
+  selected dependency version. Existing checkpoints with the previous identity
+  are not reused; source-keyed chunk plans and published output are unaffected.
+- Align the repository policies with their pinned upstream source, add canonical
+  third-party attribution, and distinguish the GPL-3.0-or-later application grant
+  from the CC-BY-SA-4.0 terms for copied or adapted policy material. The root
+  GPL license text has been brought into the house-standard form without
+  changing the application grant.
+
+Notarius's CLI, configuration schema, subprocess receipt, and durable artifact
+formats have no intentional changes in this release.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/notarius/src/tag/v0.8.1/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/notarius/src/tag/v0.8.1/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/notarius/src/tag/v0.8.1/docs/oss/attribution.md)

docs/roadmap/archive/implementation.md

@@ -0,0 +1,322 @@
+# Policy Alignment Implementation Plan
+
+## Purpose And Execution Contract
+
+Implement [Standard Repository Policy Alignment](policy.md). That feature
+roadmap owns the target policy choices and justified Notarius exceptions; this
+document owns implementation order. It replaces the completed kit-upgrade plan,
+not the implementation or contracts delivered by that earlier work.
+
+Each numbered stage is one bounded prompt for a gpt-5.6-terra coding agent.
+Complete stages in order. Inspect the worktree before each stage, preserve
+unrelated work, validate the resulting documentation, and commit the coherent
+stage under agent policy. Report changed files, checks, and any concrete blocker.
+Do not push, tag, publish, or retire unrelated roadmaps.
+
+This is a documentation/policy migration. Do not change application code,
+dependency pins, tests, release scripts, runtime contracts, or release gates.
+No production credentials or model calls are needed.
+
+## Fixed Sources And Adoption Rules
+
+Use upstream full commit
+`d84a38ebab26f048cafbe59a2246700c35d29843` throughout.
+Begin with its
+[adoption guide](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/adoption.md).
+Read applicable local policies through `docs/development.md`; when revising a
+policy, also read the upstream counterpart and affected cross-policy provisions.
+Do not reconstruct historical adoption baselines.
+
+Retrieve pinned files through public URLs or `git show` against that exact
+commit in an available checkout. Do not use an unverified sibling working tree
+or silently select newer upstream content. An unavailable source is a concrete
+blocker to copying it accurately, not a reason to invent its text.
+
+For every adopted policy:
+
+- Copy upstream wording verbatim except for required template removal and the
+  agreed, substantive project-specific customizations in the feature roadmap.
+- Retain its upstream Base Policy Version; set Last Updated to the actual date
+  the local document is adopted, not the review date by habit.
+- Add Upstream Source pointing to its own file at the full selected commit:
+  `https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/FILE.md`.
+- Remove the entire Base Policy Template section and perform its instructions.
+  Keep upstream generic rules outside it, including commit-pinned example links.
+- Explain substantive local exceptions briefly where they apply, or retain an
+  existing rationale/ADR link. Do not create an exception registry or preserve
+  stylistic paraphrases merely because they already exist.
+
+Current public project and adoption-guide links are discovery links; they may
+follow main. Source, example, and attribution links stay commit-pinned. Preserve
+accurate preexisting example pins supplied by the selected OSS template.
+Metadata must reflect only documents actually adopted by the current stage.
+The transition may temporarily contain mixed versions without claiming otherwise.
+
+## Stage 1 — Establish Provenance And Copied-Policy Licensing
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Establish the self-contained adoption and licensing foundation.
+One prompt limited to two short policies and their actual notice materials.
+
+**Read:** Selected upstream `docs/policy/meta.md` (1.0),
+`docs/policy/oss.md` (1.8), `COPYRIGHT`,
+`examples/licensing/policy-attribution.md`, and the adoption guide;
+local `COPYRIGHT`, `LICENSE`, and the feature roadmap.
+
+**Files:** Create `docs/policy/meta.md`, `docs/policy/oss.md`,
+`docs/oss/attribution.md`, and
+`docs/oss/licenses/CC-BY-SA-4.0.txt`; update `COPYRIGHT`.
+
+1. Adopt meta and OSS using the fixed-source rules. Keep public discovery URLs
+   in meta and link to the existing local developer guide and new attribution.
+   Point project-specific OSS context to Notarius's grant and release runbook;
+   do not import generic example projects.
+2. Create attribution with `# Open Source Attribution Notices` followed by
+   the canonical policy entry. Replace all three UPSTREAM_COMMIT placeholders.
+   Initially identify the two newly adopted policy files as adapted material.
+   Later stages expand this statement as their material is actually adopted;
+   do not imply that the older five files have already been refreshed.
+3. Copy the complete CC BY-SA 4.0 standard text from the pinned reference asset.
+   Preserve the canonical copyright/SPDX/notices/source arrangement and its
+   modification indication. Do not add research or compliance prose.
+4. Add a distinct scope statement to COPYRIGHT: policy material adapted from
+   Standard Repository Policies remains CC-BY-SA-4.0, with attribution defining
+   the affected material. Keep the existing GPL-3.0-or-later application grant,
+   warranty disclaimer, and third-party statement; leave root LICENSE unchanged.
+5. Do not create placeholder dependency entries. Dependency inventory is assigned
+   to Stages 4–5, and remains tracked here rather than asserted complete.
+
+**Acceptance:** Both policies have correct versions, date, file-specific source
+links, and no template-only section. All new relative links resolve. Attribution
+describes this stage's actual material, and code licensing is unchanged.
+
+**Validation:** Compare copied policy bodies and license text to the pinned
+sources; inspect deliberate substitutions. Run `git diff --check` and review
+the COPYRIGHT diff. No Go tests are needed.
+
+## Stage 2 — Standardize General Policies And Selective Orientation
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Adopt the general rules and their reading workflow. One prompt:
+three largely verbatim policy updates plus small orientation edits.
+
+**Read:** Local agent/testing/documentation policies; pinned upstream versions
+1.3, 1.3, and 1.11 respectively; upstream `agents/AGENTS.md` and the adoption
+guide's Policy Reading Guide; local `AGENTS.md` and `docs/development.md`.
+
+**Files:** Update `docs/policy/agents.md`, `testing.md`,
+`documentation.md`, root `AGENTS.md`, `docs/development.md`, and
+`docs/oss/attribution.md`.
+
+1. Adopt agent and testing substantive wording without local paraphrases.
+   Remove the redundant agent preamble, additional generic contract-preservation
+   prose, and ADR-0017 illustration. Its decision remains in architecture/ADR;
+   this is not permission to change it.
+2. Adopt documentation wording and ownership rows. Customize the consumer row
+   for existing subprocess guidance, not a hypothetical public Go API.
+   Omit the inapplicable HTTP contract row; preserve applicable CLI/config/
+   operations/integration/internal ownership. Remove the local duplicate
+   implementation-details-versus-policy section.
+3. Base root AGENTS.md on upstream `agents/AGENTS.md`, not upstream root
+   AGENTS.md. Preserve applicable existing instructions. Require orientation
+   through the developer guide and agent policy, but not full-suite reading.
+4. Add the adoption guide's seven-row selective Policy Reading Guide and its
+   selection/reuse/scope-expansion rules to docs/development.md. Retain existing
+   subsystem navigation and validation guidance; remove redundant competing
+   policy-trigger rows from the old table rather than creating two authorities.
+5. Expand the attribution material statement to identify the newly refreshed
+   policy files, adapted AGENTS.md, and copied policy-reading-guide portion of
+   docs/development.md. Do not license the unrelated remainder as copied policy.
+   Ensure the COPYRIGHT scope statement covers these identified portions.
+
+**Acceptance:** General rules match upstream, except required documentation
+ownership customization. All seven policy triggers are available; existing
+subsystem links still work. Reading is selective and public discovery is reachable.
+No test changes or stricter testing/commit requirements were introduced.
+
+**Validation:** Diff each policy against its pinned source, inspect AGENTS and
+developer-guide navigation, check attribution scope and relative links, and run
+`git diff --check`. Search affected files for leftover template instructions.
+
+## Stage 3 — Align Architecture And Release Policies Without Contract Changes
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Complete the customized policies and release navigation. One prompt
+focused on preserving existing decisions rather than redesigning them.
+
+**Read:** Local architecture and release policies, docs/release.md, relevant
+linked ADRs; pinned upstream architecture 1.3 and release 1.4. Use
+docs/internal/overview.md and existing canonical contracts only where needed to
+resolve an ownership question.
+
+**Files:** Update `docs/policy/architecture.md`, `docs/policy/release.md`,
+`docs/release.md`, and `docs/oss/attribution.md`.
+
+1. Adopt upstream general architecture ownership/approach guidance. Replace its
+   application-specific template guidance with Notarius's existing decisions.
+   Preserve the feature roadmap's enumerated pipeline, module, assets, domain,
+   identity, validation/retry, scheduling, configuration/provenance, state,
+   secret-handling, permissions, platform, and distribution contracts.
+   Keep existing application-specific sections unless an edit is necessary for
+   the adopted structure; do not turn this into a broad architecture rewrite.
+2. Adopt release wording with narrow project customizations: source only,
+   lightweight tags, main/origin, branch-before-tag, no prereleases, and no
+   hosted/asynchronous deliverables. Keep the native CLI/version check and
+   GOWORK=off rationale. Preserve the historical no-retrospective-notes decision.
+   Retain unchanged generic requirements verbatim.
+3. Add the OSS footer rule for new notes. Update the runbook with a copyable
+   three-link COPYRIGHT | LICENSE | ATTRIBUTION footer using absolute
+   `https://gitea.maximumdirect.net/eric/notarius/src/tag/<version>/...` paths.
+   Explain substitution of the selected release tag and local path checking.
+   Do not require a future tag to resolve or change publication scripts.
+4. Expand policy attribution to the complete adopted docs/policy set, retaining
+   the AGENTS/developer-guide scope from Stage 2 and any relevant adaptation
+   indications. All seven per-document source links now identify this adoption.
+
+**Acceptance:** Existing architecture and release choices are unchanged and their
+local reasons remain clear. Upstream generic wording is used where applicable.
+There are no new gates, platforms, artifacts, retrospective notes, or ADR edits.
+
+**Validation:** Review policy diffs specifically for added/removed requirements,
+check runbook agreement and affected links, and run `git diff --check`.
+Do not run a release/publication command. No runtime tests are warranted.
+
+## Stage 4 — Attribute The Kit Dependencies And Catalogs
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Add the first bounded group of component notices: ConfigKit,
+PromptKit, and their two backend catalogs. One prompt for four related projects.
+
+**Read:** Adopted OSS policy; go.mod/go.sum, resolved build dependency metadata;
+exact selected module COPYRIGHT/LICENSE/NOTICE/attribution files and VCS metadata.
+The reviewed pins are ConfigKit v0.4.1, PromptKit v0.11.1, and both catalog
+modules v2.20260926.0; verify the actual selected versions before writing.
+
+**Files:** Update `docs/oss/attribution.md`; add applicable texts under
+`docs/oss/licenses/`.
+
+1. Use read-only discovery such as `GOWORK=off go list -m -json all`,
+   `GOWORK=off go list -deps ./cmd/notarius`, and selected module contents.
+   Dependency acquisition may populate the module cache but must not change
+   dependency pins or introduce a local replace directive.
+2. Establish each selected version's exact source commit from module/VCS
+   metadata; peel annotated tags to commits. Do not substitute a tag object ID,
+   main-branch head, assumed sibling HEAD, or version tag in attribution URLs.
+3. Add factual House Format entries with supplied copyright statements,
+   applicable SPDX expressions, local standard-text links, required upstream
+   notice links, and exact-commit Source links. Preserve alternatives and
+   exceptions; determine scope from contents rather than filenames.
+4. Include LGPLv3 and its GPLv3 companion for the kit grants, and MIT for the
+   catalogs where confirmed by the pinned sources. Reuse shared local standard
+   texts; leave root project LICENSE unchanged.
+5. Inspect upstream dependency inventories for leads, but do not copy them
+   wholesale or treat them as substitutes for Notarius's own inclusion scope.
+   Hand remaining selected third-party components to Stage 5 through the stage
+   report, not editorial prose in attribution.
+
+**Acceptance:** These four components have verified source/notice links and
+complete applicable local texts. No dependency changes, guessed notices, or
+new distribution obligations were invented.
+
+**Validation:** Check exact revision correspondence, upstream filenames, every
+new local license link, and byte fidelity of standard texts. Run
+`git diff --check`; confirm go.mod/go.sum are unchanged. Report discovery
+commands and evidence; do not add a persistent inventory tool or audit artifact.
+
+## Stage 5 — Complete Attribution And Connect Reader Navigation
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Finish remaining incorporated-component coverage and canonical
+navigation. One prompt for the remaining small dependency set and doc links.
+
+**Read:** Adopted OSS policy, remaining selected module/source notices,
+README.md, integration guides, and repository evidence of copied code/assets.
+Start with jsonschema/v6 v6.0.2, x/text v0.40.0, yaml.v3 v3.0.1, and yaml/v4
+v4.0.0-rc.6, then resolve any additional actual incorporation revealed by
+Stage 4. A go.sum entry alone is not proof of incorporation.
+
+**Files:** Update `docs/oss/attribution.md`, applicable
+`docs/oss/licenses/*`, `README.md`,
+`docs/integrations/pkg-configkit.md`, and
+`docs/integrations/pkg-promptkit.md`.
+
+1. Inspect direct/transitive incorporation and copied material separately.
+   Apply the same exact-revision, factual-entry, and faithful-text rules as
+   Stage 4. Include relevant components, not every tool used in development.
+   Do not add generic entries with unresolved versions or copyrights.
+2. Use the OSS format for omitted copyright/SPDX fields where the source
+   supplies no applicable value. Preserve required project-specific notices.
+   Raise only a concrete unresolved obligation or rights issue; do not seek
+   blanket approval for the already selected linked-notice arrangement.
+3. End README with the prescribed GPL-v3-or-later COPYRIGHT link and the
+   Open Source attribution notices link. Do not imply that every incorporated
+   component or document has the application's license.
+4. Replace competing license/notice paragraphs in both integration guides with
+   concise links to the relevant canonical attribution anchors. Keep dependency
+   pins, behavior, compatibility, and public API links in the guides.
+5. Keep the attribution document to its title and factual component entries.
+   Do not include the inventory research, legal conclusions, or completion logs.
+   Do not copy unused upstream examples or standard licenses.
+
+**Acceptance:** Attribution covers the verified relevant components and copied
+policy material, with only applicable texts. README and integration links point
+to the canonical inventory; no user-visible API or dependency settings change.
+
+**Validation:** Review coverage against resolved dependencies and inspected
+copied-material evidence, validate affected relative/source links and text
+fidelity, and run `git diff --check`. No Go suite, scanner, or SBOM is required
+solely for documentation changes.
+
+## Stage 6 — Verify The Complete Adoption
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Perform the cross-document check and correct scoped documentation
+defects. One prompt; no fresh feature work or automated policy-sync system.
+
+**Read:** The feature roadmap; the seven resulting policies and their pinned
+sources; AGENTS.md, developer guide, COPYRIGHT, README, attribution/license
+materials, release runbook, and affected integration links.
+
+**Work and acceptance:**
+
+1. Compare all seven policies directly against the selected revision. Classify
+   remaining differences as metadata, template removal, required customization,
+   or a feature-roadmap exception. Replace accidental paraphrases with upstream
+   wording. Preserve established local requirements.
+2. Confirm versions 1.3/1.3/1.11/1.3/1.4/1.0/1.8 for agents, architecture,
+   documentation, testing, release, meta, and OSS respectively. Verify each
+   Upstream Source targets its own file and Last Updated reflects actual work.
+3. Confirm discovery links follow public project/main-guide URLs while adopted
+   source, examples, and component attribution remain accurately commit-pinned.
+   Check no placeholder UPSTREAM_COMMIT, template-only section, or local
+   checkout-dependent reference remains in adopted materials.
+4. Check selective policy routing, local authority, canonical documentation
+   ownership, copied-material scope/modification status, unchanged application
+   grant/root LICENSE, and directly reachable license/companion texts.
+5. Verify source-only publication, selected gates, optional diagnostics,
+   release completion, and prospective-only footer guidance still agree.
+   Do not modify historical notes, accepted ADRs, or scripts to satisfy this check.
+6. Review changed-file scope: only intended policy, notice, and supporting
+   documentation files should have changed. Correct in-scope documentation
+   defects, report unresolved concrete issues, and leave unrelated roadmap
+   retirement and release preparation to an explicit later request.
+
+**Validation:** Run `git diff --check`; inspect file/link destinations and
+compare local standard texts with verified sources. A search for
+`Base Policy Template` or `UPSTREAM_COMMIT` in adopted files should be empty;
+do not confuse explanatory roadmap text with an unfilled adopted template.
+No production tests, new test framework, recurring synchronization gate, or
+release execution is needed.
+
+## Open Questions
+
+None at the agreed baseline. Policy choices and exceptions are settled.
+A newly discovered concrete notice/source or rights issue should be reported
+with evidence and viable treatments rather than resolved by inventing a broader
+requirement. That contingency does not authorize reopening settled policies.

docs/roadmap/archive/policy.md

@@ -0,0 +1,252 @@
+# Standard Repository Policy Alignment
+
+## Purpose
+
+Bring Notarius's adopted policies into alignment with Standard Repository
+Policies, using identical upstream language wherever a substantive,
+project-specific decision does not require customization. Preserve Notarius's
+application contracts, operator choices, selected code license, and source-only
+release process.
+
+This roadmap defines the agreed target and update scope. It does not itself
+adopt policies, alter runtime behavior, or authorize a release.
+
+## Selected Upstream Revision And Current Baseline
+
+The agreed review, performed on 2026-09-28, uses full upstream commit
+`d84a38ebab26f048cafbe59a2246700c35d29843` of
+[Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy).
+Follow the [adoption and update guide at that revision](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/adoption.md).
+Use that fixed revision for implementation, not whichever revision is then on
+`main`.
+
+The comparison is between the current Notarius documents and that revision.
+Historical adoption baselines need not be reconstructed or assessed. Introducing
+source metadata records the revision actually incorporated by this update, not
+a claim about previous adoptions.
+
+Notarius currently has five policies, no `meta.md` or `oss.md`, and no
+`docs/oss/` attribution collection. Its current agent entry point and developer
+guide provide orientation but lack the complete selective policy-reading guide.
+The project grant is GPL-3.0-or-later; root `LICENSE` contains the GPLv3 text.
+README licensing navigation and prospective release-footer instructions are
+missing.
+
+Public upstream discovery and attribution are now expressly approved. This
+supersedes the earlier instruction to omit references to the policy source;
+local checkout paths are neither necessary nor appropriate public references.
+
+## Alignment Rules
+
+- Start from the selected upstream wording, not a paraphrase of it. Adopt
+  non-substantive wording changes verbatim.
+- Retain local variations only for substantive, locally significant
+  requirements or decisions. Explain their purpose in the relevant policy
+  section or link to existing rationale; do not add a separate exception registry.
+- Follow each template's adoption instructions and remove its entire
+  `Base Policy Template` section. Replace required project-specific guidance
+  rather than leaving template instructions in an adopted policy.
+- Preserve deliberately selected contracts. Simplifying duplicate wording does
+  not authorize changing architecture, runtime behavior, or release mechanics.
+- Keep local policies authoritative. Upstream changes take effect only through
+  deliberate adoption; no automatic synchronization is introduced.
+
+## Target Policy Set And Justified Customizations
+
+| Local file | Current version | Target version | Required treatment |
+| --- | --- | --- | --- |
+| `docs/policy/agents.md` | 1.1 | 1.3 | Adopt substantive upstream wording verbatim. Remove redundant local preamble and the ADR-0017 illustration; architecture already owns the deployment-permissions decision. No substantive exception is needed. |
+| `docs/policy/architecture.md` | 1.1 | 1.3 | Adopt general purpose, ownership, architectural approach, and constraint-versus-implementation guidance while retaining the application-specific decisions described below. |
+| `docs/policy/testing.md` | 1.1 | 1.3 | Adopt substantive upstream wording verbatim. Existing risk-based testing remains intact; no project-specific exception or test rewrite is needed. |
+| `docs/policy/documentation.md` | 1.3 | 1.11 | Adopt upstream wording and licensing/provenance ownership rows. Customize consumer ownership for subprocess use and omit the inapplicable HTTP-contract row. Remove the duplicate local implementation-details-versus-policy section; agent policy owns that rule. |
+| `docs/policy/release.md` | 1.1 | 1.4 | Adopt upstream wording with the existing source-only choices and selected gates below. Add prospective OSS-footer guidance. |
+| `docs/policy/meta.md` | Absent | 1.0 | Add upstream substantive wording, including public discovery links, local authority, and local attribution navigation. |
+| `docs/policy/oss.md` | Absent | 1.8 | Add upstream substantive wording, commit-pinned example links, and required Notarius context through canonical documents. |
+
+No existing policy remains entirely unchanged: all five need wording and/or
+provenance updates. This does not imply new substantive testing or agent rules.
+
+### Architecture Exceptions
+
+The architecture template expressly requires application-specific content.
+Retain Notarius's fixed stage sequence rather than an arbitrary DAG,
+artifact-family ownership across stages, domain-neutral framework, inward
+dependency direction, external adapter boundaries, and content-only assets
+package. Retain adopted validation/retry, scheduling, identity, evidence,
+configuration, and provenance contracts.
+
+Preserve operator-owned filesystem access policy and the separately adopted
+correctness boundaries, cache/checkpoint eligibility, output/debug lifecycle,
+secret handling, and platform/distribution decisions. These express existing
+product requirements and ADR-backed choices, not stylistic variations.
+Use existing architecture and ADRs as their authority; this migration does not
+authorize strengthening or weakening them.
+
+Keep concrete package inventories and implementation mechanics in their current
+internal-documentation homes. No architecture redesign, new threat model, or
+new abstraction is part of this work.
+
+### Documentation Exceptions
+
+Notarius's consumer interface is primarily a subprocess CLI, not a public Go
+API. Retain `docs/consumers/` ownership for that workflow and its consumer
+responsibilities. Retain integration contracts as the owners of durable receipt
+and artifact shapes. No HTTP service documentation or placeholder API document
+is needed.
+
+Other editorial variations should use upstream language, including the current
+versus future behavior and accepted-ADR rules. Preserve their meaning without
+retaining duplicate local formulations.
+
+### Release Exceptions
+
+Preserve source-only delivery, lightweight tags, `main` on `origin`,
+branch-before-tag publication, and no prereleases. There are no binaries,
+hosted release objects, or asynchronous artifacts to publish or recover.
+Use upstream generic language where applicable, but do not introduce those
+channels or atomic-push requirements.
+
+Retain the native CLI build and injected-version check with `GOWORK=off`:
+it protects the executable entry point and release version, which package tests
+alone do not verify. Preserve its documented rationale and existing optional
+diagnostics. No additional validation gate is warranted.
+
+Retain the decision not to create retrospective notes for v0.1.0, v0.2.0, or
+v0.3.0. Apply new footer formatting prospectively; do not rewrite published
+history to retrofit it.
+
+## Provenance And Selective Reading
+
+Each of the seven policies must retain its actual target `Base Policy Version`,
+set `Last Updated` to its actual local adoption date, and add an
+`Upstream Source` link to its own source file. For example:
+
+```text
+https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/testing.md
+```
+
+Substitute the correct filename for each policy; do not link every header to
+the repository root or adoption guide. Retain provenance through subsequent
+local edits.
+
+Use current public discovery URLs in `meta.md`:
+
+- https://gitea.maximumdirect.net/eric/policy
+- https://gitea.maximumdirect.net/eric/policy/src/branch/main/docs/adoption.md
+
+Discovery links intentionally follow the current project and guide.
+Adopted-source, example, and attribution links identify immutable commits.
+The OSS template already includes commit-pinned example references; retain
+accurate pinned references rather than converting them to branch links.
+
+Adapt upstream `agents/AGENTS.md` into root `AGENTS.md`, preserving applicable
+existing instructions. Direct readers to `docs/development.md`, require agent
+policy before recommending/planning/implementing changes, and explicitly avoid
+reading the whole policy suite by default.
+
+Merge the upstream adoption guide's Policy Reading Guide into
+`docs/development.md`. Include all seven task triggers, especially policy
+updates, dependency/licensing changes, validation selection, and compatibility
+decisions. Preserve focused subsystem navigation without duplicating policy
+triggers across competing tables. Reuse policies already in context, expand
+reading when scope expands, and read affected cross-policy provisions when
+revising a policy.
+
+## Licensing And Attribution Target
+
+### Copied Policy Material
+
+Follow the selected upstream grant and canonical policy-attribution example:
+
+- Create `docs/oss/attribution.md` with the House Format title and insert the
+  Standard Repository Policies entry using the selected full commit for its
+  source, COPYRIGHT, and LICENSE URLs.
+- Identify actual copied/adapted material and modification status. Include
+  `docs/policy/`, the adapted root `AGENTS.md`, and the copied policy-reading
+  guide within `docs/development.md` as applicable. Do not claim unrelated
+  developer documentation was copied or relicense unrelated material.
+- Preserve supplied copyright, license, and disclaimer notices through the
+  specified arrangement; keep the entry factual rather than adding compliance
+  or research commentary.
+- Copy the complete, verbatim `CC-BY-SA-4.0.txt` to `docs/oss/licenses/`.
+- Add the separately licensed policy-material scope to `COPYRIGHT`, pointing
+  to attribution for exact scope and notices. Adapted policy material remains
+  CC-BY-SA-4.0; application code remains GPL-3.0-or-later. Leave root `LICENSE`
+  unchanged.
+
+The upstream licensing-format examples are CC0; using their original formatting
+alone does not require a separate attribution entry. This does not exempt
+copied policy prose from its stated terms.
+
+### Incorporated Dependencies And Assets
+
+Complete the previously planned inventory of relevant direct/transitive
+dependencies and copied code/assets using `go.mod`, resolved build dependencies,
+and exact pinned source contents. Neither direct imports alone nor every
+`go.sum` entry defines the inventory.
+
+Current starting points are ConfigKit v0.4.1, PromptKit v0.11.1, both PromptKit
+backend catalogs v2.20260926.0, jsonschema/v6 v6.0.2, x/text v0.40.0, yaml.v3
+v3.0.1, and yaml/v4 v4.0.0-rc.6. Verify actual incorporation, terms, notices,
+and exact commits; this list is not a pre-approved attribution inventory.
+
+Use the upstream OSS House Format without editorial elaboration. Copy only
+applicable standard and companion license texts, retaining their wording.
+Link component-specific notices and sources at the exact imported commit.
+Apply the upstream house interpretation of linked notices without inventing
+extra local-copy requirements, recurring approvals, or licensing conclusions.
+Handle a concrete uncovered obligation separately if one is discovered.
+
+### Navigation And Canonical Ownership
+
+- End `README.md` with the project-grant and attribution links prescribed by
+  OSS policy, using Notarius's GPL-3.0-or-later grant.
+- Update `docs/release.md` with a copyable prospective
+  `COPYRIGHT | LICENSE | ATTRIBUTION` footer using absolute Notarius URLs at
+  the release tag or corresponding immutable source revision. Check intended
+  local paths before publication; do not require an unpublished tag to resolve.
+- Update `docs/integrations/pkg-configkit.md` and
+  `docs/integrations/pkg-promptkit.md` to link to canonical attribution rather
+  than maintaining competing notice inventories. Keep behavioral/API references
+  in those integration guides.
+
+## Local Materials And Upstream-Only References
+
+Keep the seven adopted policies, adapted agent entry point, project-specific
+developer guide, actual notices, and applicable license texts locally.
+
+Keep the upstream README, root AGENTS.md, contributor guide, adoption guide,
+and example collection upstream. Link to them when appropriate instead of
+copying an additional documentation tree. Do not copy unused license texts,
+example projects, or placeholder documents. Root Notarius `AGENTS.md` is based
+on upstream `agents/AGENTS.md`, not upstream's own contributor instructions.
+
+## Implementation Ownership
+
+[Implementation Plan](implementation.md) owns the ordered work stages and their
+validation. This document owns the target end state, scope, and policy choices.
+
+## Scope Boundaries And Acceptance
+
+- No application code, dependency pins, tests, release scripts, or published
+  history change merely to adopt policy wording.
+- No new ADR, recurring policy-sync job, SBOM, scanner, blanket header sweep,
+  security audit, platform matrix, approval round, or release gate is required.
+- All seven policies use the selected versions and correct file-specific source
+  links, with actual adoption dates and no remaining template-only sections.
+- Non-substantive differences use upstream wording; substantive variations are
+  confined to justified Notarius responsibilities and decisions.
+- Orientation supports selective reading and public upstream discovery without
+  requiring a sibling checkout.
+- Attribution accurately identifies copied material, modifications, selected
+  dependency revisions, notices, and faithful local license texts. Application
+  and policy-material license scopes remain distinct.
+- Canonical navigation works without duplicate notice inventories, nonexistent
+  interface documents, or copied upstream guide/example collections.
+- Validate affected relative and public links, metadata targets, license-text
+  fidelity, and `git diff --check`. Ordinary document review is sufficient;
+  production model runs and new runtime tests are not warranted.
+- Resolve only concrete newly discovered rights or scope issues with the user;
+  do not reopen settled choices through blanket approval requirements.
+
+There are no blocking open design decisions at the agreed review baseline.

docs/roadmap/archive/remediation.md

@@ -0,0 +1,124 @@
+# Kit Upgrade Review Remediation
+
+## Resolution
+
+Completed 2026-09-26. No production changes were needed.
+
+- `internal/framework/llm/promptkit_observation_test.go` now covers retries in
+  both initial and repair generations, aggregate versus legacy accounting,
+  unknown/known-zero/partial usage, retry-wait cancellation, exhausted execution,
+  preparation failure, and overlapping request isolation.
+- `internal/framework/pipeline/debug_execution_test.go` exercises the real
+  scheduled client and debug wrapper together. It verifies returned and persisted
+  summaries for provider errors and cancellation without a body, split debug and
+  fallback content, terminal references, and explicit usage-presence JSON fields.
+- Temporary regression probes confirmed that discarding failed responses in the
+  scheduler and collapsing usage presence into known zero cause the new tests
+  to fail. Those probes were reverted.
+- Focused LLM/pipeline tests, their race-enabled suites, and
+  `GOWORK=off go test ./...` passed. Existing no-debug and redaction coverage was
+  retained. Runtime budgets, scheduler policy, and output contracts are unchanged.
+
+The original finding below is retained as review context.
+
+## Review Scope
+
+Reviewed implementation commits `31b48d2` through `7ac9d94` against
+[the feature roadmap](upgrade-kit.md) and the completed upgrade work recorded
+in those commits.
+The review covered configuration selection/defaults, production client wiring,
+error translation, execution observation, scheduler/debug propagation, current
+documentation, and tests. No production model calls were made.
+
+The implemented architecture is consistent with the intended design: ConfigKit
+v0.4.0 owns composition and overlay provenance behind the configuration boundary;
+PromptKit v0.11.0 owns transient retries and structural repairs behind the LLM
+adapter. Notarius retains stage retry/disposition policy, completion-scoped
+scheduling, application-owned error/observation types, and opt-in debug output.
+No new runtime defect or unrequested restriction was established in this review.
+
+## Finding 1 — Complete The Missing Retry And Observation Verification
+
+**Priority:** Medium. This is a verification gap, not a demonstrated runtime
+failure. Stages 5–7 are marked complete, but their consequential cross-boundary
+acceptance tests were not implemented.
+
+### Evidence And Risk
+
+- `internal/framework/llm/promptkit_client_test.go:58` adds only a successful,
+  single-attempt observation assertion with positive prompt-token usage. It
+  does not exercise absent versus partial/known-zero usage, failed/canceled
+  execution summaries, preparation failure, or concurrent request isolation.
+- `TestPromptKitClientAppliesConfiguredBuiltInTransientRetries` covers basic
+  status recovery, explicit zero, exhaustion, and a noneligible status. It
+  discards the response, so does not protect terminal accounting. There is no
+  combined transient-retry/structural-repair scenario or cancellation while
+  waiting on Retry-After.
+- `internal/framework/llm/scheduled_client.go:40` now preserves a response when
+  the inner call fails. No corresponding test protects that behavior. Returning
+  an empty response again would silently remove precisely the failed-call
+  observations this feature is intended to retain.
+- `internal/framework/pipeline/debug.go:267` and `:277` add execution summaries
+  to response artifacts and call references, plus fallback/content-splitting
+  propagation. Neither the debug nor terminal-debug tests were extended to
+  exercise these fields. Passing existing tests does not prove that failed-call
+  metadata reaches persisted records.
+
+These are Notarius-owned integration risks, not a request to re-test PromptKit's
+backoff algorithm. Losing failed-call observations or misrepresenting incomplete
+usage would be difficult to detect in ordinary successful runs. A focused set
+of behavioral tests is justified under the testing policy.
+
+### Required Remediation
+
+Use existing test assets, local HTTP fixtures, scheduler wrappers, and debug
+recorders. Combine related assertions; no fixed test count or new test framework
+is required.
+
+1. Add an adapter scenario with a transient failure, a structurally invalid
+   completion, and a successful repair. Exercise retries in both generations
+   with small explicit budgets, and assert terminal attempts/retries/repair
+   counts without double-counting. Use controlled usage fields to distinguish
+   known zero, unknown, and partial aggregate usage. Preserve legacy usage
+   semantics independently.
+2. Cover failed and canceled completions, including cancellation during a
+   Retry-After wait. Verify caller cancellation identity, bounded completion,
+   and retained execution metadata. Use signaling and a generous bounded test
+   timeout, not exact sleep durations or jitter assertions. Cover a preparation
+   failure with no execution summary. Add a small concurrent-call check for
+   request-local summary isolation, which race tests alone do not prove.
+3. Exercise an error response through the real scheduled client and existing
+   debug wrapper/recorder seams. Assert that the summary reaches response
+   artifacts and terminal call references even without a provider response
+   body. Cover the content-splitting/fallback path with a representative response.
+   Reuse existing no-debug and redaction tests rather than duplicating their
+   whole inventories. Keep new summary assertions metadata-only.
+
+Retain existing scheduler policy, stage/validator budgets, cancellation
+disposition, warning semantics, and debug opt-in behavior. Do not introduce a
+total deadline, new retry caps, telemetry artifacts, or live API requirements
+to make these tests easier. Fix production code only if these checks reveal a
+violation of the already selected behavior.
+
+**Acceptance:** The added tests fail if failed responses lose their execution
+summary at an adapter/wrapper boundary, usage presence is collapsed into zero,
+or retry/repair totals are double-counted. They pass with the intended behavior
+and provide evidence for the previously unverified stage acceptance criteria.
+
+**Validation:** Run focused LLM/pipeline tests, race-enabled tests for those
+packages, and `GOWORK=off go test ./...`. No production credentials are needed.
+
+## Checks Completed During Review
+
+- `GOWORK=off go test ./...`
+- `GOWORK=off go vet ./...`
+- `GOWORK=off go build ./...`
+- `GOWORK=off go mod tidy -diff`
+- `GOWORK=off go test -race ./internal/framework/llm ./internal/framework/pipeline`
+- CLI configuration validation for the minimal and complete examples, including
+  the complete example with `--config-overlay development`.
+- `git diff --check`
+
+All passed. Existing green tests do not substitute for the missing behavioral
+coverage above. Temporary diagnostic test material used during review was
+removed; no application code was changed.

docs/roadmap/archive/upgrade-kit.md

@@ -0,0 +1,337 @@
+# ConfigKit And PromptKit Upgrades
+
+## Purpose
+
+Adopt ConfigKit v0.4.0 and PromptKit v0.11.0 in one coordinated work set:
+
+- Consistently call ConfigKit's selected configuration layer an **overlay**,
+  distinct from PromptKit LLM profiles.
+- Adopt configurable transient HTTP retries, provider-neutral failure
+  classifications, and execution observations from PromptKit.
+
+Preserve application/framework boundaries and keep the two upgrades as distinct
+implementation workstreams. Neither requires a redesign of pipeline execution.
+
+This feature roadmap records the target state and scope. Its original
+implementation plan was completed and later replaced by a new work plan.
+Neither document authorized release publication.
+
+## Current Baseline
+
+The reviewed baseline is Notarius v0.7.1 (`53d9284`):
+
+- `go.mod` pins ConfigKit v0.3.0 and PromptKit v0.10.0.
+- `internal/core/config/load.go` passes `LoadOptions.Profile` into
+  `configkit.Options[Document].Profile`.
+- `--config-profile` selects `profiles/<name>.yml` beneath the configuration
+  root for `run`, `config validate`, `config effective`, `config explain`, and
+  `pipelines list`.
+- The maintained selected-layer example is
+  `examples/profiles/development.yml`; configuration and CLI tests create
+  equivalent directories and exercise selection and inspection.
+- ConfigKit owns composition and inspection metadata. Notarius owns its
+  version 5 document, defaults, validation, source-relative path resolution,
+  runtime conversion, and CLI discovery.
+
+A dependency-only trial against v0.4.0 fails to compile at `load.go:33` because
+`configkit.Options.Profile` no longer exists. The review found no direct
+Notarius references to `LayerProfile`, `CodeProfile*`, or `LoadSecretsDir`.
+
+An isolated dependency-only trial against PromptKit v0.11.0 passes the complete
+Notarius test suite and `go vet ./...`. That proves baseline compatibility, not
+adoption of the new controls or observations. The current adapter does not
+configure transient retries or attach an execution observer. It classifies
+generation errors broadly and records successful-result usage and structural
+repair counts. The outer scheduler holds a permit for the whole completion.
+
+## Upstream Changes
+
+### ConfigKit v0.4.0
+
+The [ConfigKit v0.4.0 release guide](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.4.0/docs/releases/v0.4.0.md)
+defines four breaking naming changes:
+
+| Surface | Previous | Target |
+| --- | --- | --- |
+| Selection API | `Options.Profile` | `Options.Overlay` |
+| Selected file | `profiles/<name>.yml` | `overlays/<name>.yml` |
+| Provenance layer | `LayerProfile` / `profile` | `LayerOverlay` / `overlay` |
+| Diagnostic identifiers | `CodeProfile*` / `profile.*` | `CodeOverlay*` / `overlay.*` |
+
+There are no legacy aliases or directory fallback. Explicit imports from a
+directory named `profiles` remain valid ordinary imports. Merge rules,
+precedence, lifecycle, source-origin APIs, minimum Go version, and YAML parser
+dependency are unchanged.
+
+The intervening v0.3.1 release makes the opt-in `LoadSecretsDir` API ignore
+dot-prefixed entries. Notarius does not use this API; adding secrets-directory
+bootstrap is outside this work.
+
+### PromptKit v0.11.0
+
+The [PromptKit v0.11.0 release guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/releases/v0.11.0.md)
+introduces additive runtime APIs and one changed default:
+
+- Built-in generation defaults to two additional transient HTTP attempts for
+  statuses 429, 500, 502, 503, and 504. Engine and request controls can override
+  the count, including zero. Injected `LLMClient` implementations are not
+  automatically replayed; a custom HTTP client on the built-in path still is.
+- Backoff is cancellable and honors valid provider `Retry-After` timing.
+  Generation and HTTP timeouts apply per attempt; the caller context bounds
+  the whole operation. Transport failures, malformed responses, other HTTP
+  statuses, and invalid generated content are not transient-retry candidates.
+- `RunRequest.Observer` reports lifecycle metadata, attempts, waits, outcomes,
+  and presence-aware usage, including work before a failed execution. It works
+  with prepared execution; preparation itself emits no execution events.
+- `ErrTransport`, `ErrMalformedResponse`, `ErrRetriesExhausted`, and
+  `RetryExhaustedError` support typed classification without parsing error text.
+- The license changes to LGPL-3.0-or-later. Catalog selections and the minimum
+  Go version are unchanged from v0.10.0.
+
+## Target End State
+
+### Dependency And Ownership
+
+Pin ConfigKit v0.4.0 and PromptKit v0.11.0 and tidy the dependency graph.
+Continue using only ConfigKit's
+public root API behind `internal/core/config`. No compatibility parser,
+application-owned composition engine, or new configuration abstraction is
+needed. PromptKit remains behind `internal/framework/llm`; its types must not
+leak into domain modules or pipeline contracts. Retain the existing prepared
+execution path, profile choices, and D&D model settings.
+
+### Consistent Overlay Selection
+
+- Replace the configuration-selection CLI flag with `--config-overlay` on all
+  commands that currently accept `--config-profile`.
+- Rename application-owned fields, variables, helpers, help text, and test
+  descriptions that specifically represent this selection to overlay terms.
+- Pass the selection through `configkit.Options.Overlay`.
+- Select files only from `overlays/<name>.yml`, following ConfigKit's contract.
+- Preserve empty and `default` selection as the composed base configuration
+  without a selected overlay.
+- Use a clean cutover: no old CLI alias, directory fallback, automatic file
+  moves, or custom migration machinery. Normal unknown-flag handling is
+  sufficient for the retired flag; explain migration in documentation.
+
+This rename is deliberately narrow. Preserve `llm_profile`, `--llm-profile`,
+`promptkit.profile_dir`, `promptkit.profile_file`, `base_profile`, embedded
+`dnd-extraction` profiles, and `examples/llm-profiles/`. Other application
+concepts named `Profile`, including pipeline/runtime types, must not be renamed
+merely because they share the word.
+
+### Preserved Behavior
+
+Retain configuration version 5, with the additive retry setting described below.
+Preserve existing defaults other than the explicitly adopted transient retry policy,
+imports, overlay merge behavior (including sequence replacement), explicit CLI
+override precedence, strict decoding, domain validation, and secret redaction.
+Do not add new restrictions or relax existing explicit contracts as part of the
+rename.
+
+Relative paths continue to resolve from the file supplying the surviving
+declaration, including overlay files. Invocation-relative CLI paths and
+main-file-relative built-in defaults retain their current behavior.
+
+Effective configuration, explanations, and configuration-load diagnostics use
+the new upstream overlay provenance and diagnostic vocabulary. Preserve source
+file labels and actionable error context; do not translate the new metadata
+back into legacy profile terminology.
+
+Pipeline stage order, semantic acceptance, LLM selection, domain artifact
+schemas, and subprocess result receipts remain unchanged. No blanket checkpoint
+invalidation is added merely for the ConfigKit rename. Update the existing
+PromptKit-version identity used by checkpoint fingerprinting with its dependency
+pin, following the current adapter convention; no cache redesign is needed.
+
+### Transient Retry Policy
+
+Expose `promptkit.transient_retries` as a nonnegative integer setting with a
+Notarius default of **2 additional attempts**. Explicit zero disables transient
+retries. Apply the resolved setting to the shared PromptKit engine so modules,
+normalizers, validators, and semantic correction calls receive the same policy.
+Include the effective value in configuration inspection. Do not impose an
+arbitrary application maximum or add per-binding controls in this work set.
+
+Maintain three separate budgets and owners:
+
+| Budget | Owner | Repeated work |
+| --- | --- | --- |
+| Transient retries | PromptKit | The same generation request after eligible HTTP failures |
+| Structural repairs | PromptKit | A corrective generation for invalid structured output |
+| Producer/validator retries | Notarius | The configured stage or validator operation, with semantic feedback where applicable |
+
+Do not silently reduce, repurpose, or remove existing stage/validator budgets.
+Each structural repair generation receives its own transient budget. For a
+single-completion producer, two additional stage attempts, one structural
+repair, and two transient retries permit up to 18 HTTP attempts, excluding any
+separate validator calls. Document this multiplication and the possibility of
+additional cost; retries do not imply exactly-once provider execution.
+
+Preserve caller cancellation throughout generation and waiting. Do not describe
+a profile's generation timeout as a total completion deadline: provider
+`Retry-After` can extend waits beyond local backoff, and each HTTP attempt has
+its own timeout. A new total-deadline configuration surface is outside this
+upgrade; accurately document the current controls and limitations.
+
+Retain Notarius's completion-scoped scheduler permit during upstream backoff.
+PromptKit releases its active backend permit during that wait, but this does
+not release the outer Notarius permit. This remains bounded and correct; do
+not add an attempt-level scheduler redesign.
+
+### Provider-Neutral Failure Diagnostics
+
+Translate the new typed errors into application-owned classifications for
+transport failures and malformed provider responses. Represent transient retry
+exhaustion separately from its underlying failure/status, retaining the actual
+attempt count where available. Preserve existing HTTP-status reporting,
+capacity classification, cancellation, deadline handling, and redaction.
+
+Do not turn a malformed provider envelope into a semantic rejection or confuse
+it with a structurally invalid model response. Do not expose PromptKit error
+types across the adapter boundary or parse prose to recover classifications.
+Existing stage disposition policies continue to decide what happens after a
+completion fails; this work does not redesign those policies.
+
+### Execution Observations
+
+Attach a request-local observer through the existing prepared-execution path.
+Translate selected metadata into Notarius-owned completion/debug summaries:
+
+- dispatched attempt, transient retry, and structural repair-call counts;
+- capacity-wait, generation, retry-delay, and total execution durations;
+- terminal outcome, failure classification, HTTP status, and exhaustion state;
+- observed token counts with explicit known/complete indicators.
+
+Retain available summaries on failed completions, including cancellation, rather
+than discarding them with the absent `RunResult`. Preparation failures have no
+execution observation; do not fabricate one. Keep existing successful-result
+usage fields and their meanings unchanged. Observation totals are separate
+presence-aware metadata, not a second set of tokens to add to existing usage.
+Unknown counts are not known zero; partial totals are not a billing ledger.
+
+Use lightweight per-request accumulation with no unbounded event history or
+asynchronous queue. Callbacks are synchronous: avoid blocking I/O or acquisition
+of scheduler resources inside them, and isolate concurrent requests. Persist
+the projection through the existing opt-in debug path, including safe terminal
+summaries where applicable. Do not serialize upstream event structs directly;
+their JSON layout is not a public contract. Allowlist metadata and preserve
+existing identifier/content handling and redaction boundaries.
+
+Successful transient recovery is ordinary success, not a warning. This work
+does not add routine console messages, change the warning policy, introduce a
+new durable telemetry artifact, or add complete cost accounting.
+
+## Required Changes
+
+### Code And Examples
+
+- Update `go.mod` and `go.sum` and the configuration loader/options boundary.
+- Update CLI selection plumbing in `internal/cli/run.go` and
+  `configkit_commands.go`, including usage, flag parsing, argument classification,
+  explicit empty-value handling, and error paths.
+- Move the maintained example to `examples/overlays/development.yml` and update
+  example discovery and related fixtures. Inspect relative paths when moving
+  files; do not assume all occurrences of `profiles` are configuration overlays.
+- Update affected configuration and CLI tests, particularly document paths,
+  operational defaults, safe inspection, command selection, diagnostic source
+  labels, run contracts, and maintained-example coverage.
+- Add the retry setting through the typed configuration document, defaults,
+  validation, runtime conversion, and CLI client-construction boundary. Update
+  the complete example to demonstrate it without adding unnecessary settings
+  to the minimal example.
+- Update the PromptKit adapter's engine construction, request observation,
+  error conversion, and checkpoint version identity. Extend transport-neutral
+  response/debug contracts only with the application-owned metadata needed.
+- Carry observations through the pipeline debug wrapper and safe terminal
+  reporting without double-counting usage or losing failed-call summaries.
+
+### Documentation
+
+Update current documentation with the implementation, keeping canonical
+ownership under [Documentation Policy](../../policy/documentation.md):
+
+- `docs/cli.md`: new flag on every affected command and matching help behavior.
+- `docs/config.md`: overlay terminology, directory layout, precedence, and the
+  explicit distinction from LLM profiles; transient retry setting and default.
+- `docs/integrations/pkg-configkit.md`: pinned release and supported upstream
+  naming/inspection contract.
+- `docs/internal/configuration.md` and relevant CLI internals: new selection
+  terminology and unchanged boundaries.
+- `docs/consumers/subprocess.md` and any other current callers/examples: updated
+  invocation syntax. Review operations and README references where applicable.
+- `docs/integrations/pkg-promptkit.md`: updated pin, typed errors, observer
+  support, and retry contract. Refresh pinned upstream links, including its
+  relocated release-policy document.
+- `docs/internal/llm.md` and relevant pipeline/debug internals: observation
+  projection, failure handling, scheduler interaction, and separate retry
+  budgets. Remove the obsolete claim that PromptKit has no provider retry loop.
+- `docs/operations.md`: latency/cost implications, timeout limits, opt-in debug
+  evidence, and how to disable transient retries.
+
+Preserve historical release notes and the accepted text of ADR-0018. Its
+ConfigKit ownership decision remains valid; a terminology migration alone does
+not require a new ADR or supersession. Current documentation must not portray
+the old dependency pin as the current supported version.
+
+Record PromptKit's LGPL-3.0-or-later change in the integration documentation and
+eventual release note. Review its notices and distribution implications within
+Notarius's source-only release model. Do not silently relicense Notarius, copy
+upstream release policy into this repository, or introduce binary packaging.
+Any future binary distribution needs its own license-compliance review.
+
+## Operator Migration And Release Impact
+
+This work belongs in the next **minor** Notarius release, not a patch, because
+both the documented selected-file layout and CLI syntax change.
+
+Operators move selected configuration files from `profiles/` to `overlays/`
+and replace `--config-profile` with `--config-overlay` in scripts, service
+definitions, and subprocess callers. Preserve unrelated PromptKit profile
+directories and explicit imports. Review relative paths and explicit imports
+that refer to moved files. No YAML body version migration is required.
+
+The eventual release note must explain this cutover, the newly enabled transient
+retries and zero-value opt-out, and the dependency license change. PromptKit's
+catalogs are unchanged from v0.10.0; this upgrade adds no further profile-name
+migration or change to the D&D model defaults. Release preparation,
+tagging, and publication remain a separately requested task under
+[Source Releases](../../release.md).
+
+## Acceptance And Verification
+
+- Notarius builds against ConfigKit v0.4.0 and PromptKit v0.11.0 without
+  compatibility shims.
+- All five affected commands use the new flag; non-default overlay selection,
+  omitted selection, empty selection, and `default` retain their intended
+  behavior. The old flag is not accepted.
+- Selected overlays load from the new directory. A legacy-only selected file
+  does not silently load; ordinary explicit imports remain supported.
+- Representative tests demonstrate overlay precedence, CLI overrides,
+  declaration-relative paths, redacted inspection, and source-aware failures.
+- Maintained examples validate, including the development overlay. LLM profile
+  loading and defaults remain unaffected.
+- Tests prove the default transient retry policy, explicit zero, configured
+  counts, and negative-value rejection through the relevant configuration and
+  adapter boundaries. Use local HTTP test servers for eligible/noneligible
+  statuses, exhaustion, cancellation, and interaction with structural repair;
+  an injected LLM fake alone does not exercise built-in HTTP retries.
+- Provider-neutral errors preserve underlying status and cancellation identity
+  without leaking credentials or upstream types.
+- Observations are available for success and failure, preserve unknown versus
+  known-zero usage, avoid aggregate double-counting, and stay isolated under
+  concurrent completions. Successful retry recovery emits no warning.
+- Representative scheduler/repair/retry checks preserve bounded execution and
+  cancellation; use existing coverage where it already proves the contract.
+- Current documentation, help text, examples, and tests agree. Searches for old
+  vocabulary are reviewed semantically, excluding intentional historical and
+  LLM-profile references rather than enforcing a blanket text ban.
+- Run focused `go test ./internal/core/config ./internal/cli ./internal/framework/llm ./internal/framework/pipeline`, followed by
+  `go test ./...`, `go vet ./...`, `go build ./...`, `go mod tidy -diff`, and
+  `git diff --check`, with `GOWORK=off`. Run race-enabled tests for the modified
+  adapter, scheduler, and observation integration. Validate both maintained configurations
+  and the complete configuration with `--config-overlay development`.
+
+Use existing behavioral tests where possible, following
+[Testing Policy](../../policy/testing.md). No live model calls or production API
+credentials are needed to validate this migration.

examples/dnd-complete.config.yml

@@ -4,6 +4,7 @@ configkit:
     - path: pipelines/dnd-session.yml
 promptkit:
   profile_file: ./llm-profiles/dnd-extraction.yml
+  transient_retries: 2
 concurrency:
   total_llm: 2
   stage_workers:

go.mod

@@ -3,8 +3,8 @@ module gitea.maximumdirect.net/eric/notarius
 go 1.25.5
 
 require (
-	gitea.maximumdirect.net/eric/ConfigKit v0.3.0
-	gitea.maximumdirect.net/eric/promptkit v0.9.0
+	gitea.maximumdirect.net/eric/ConfigKit v0.4.2
+	gitea.maximumdirect.net/eric/promptkit v0.11.2
 	github.com/santhosh-tekuri/jsonschema/v6 v6.0.2
 	gopkg.in/yaml.v3 v3.0.1 // indirect
 )
@@ -12,7 +12,7 @@ require (
 require golang.org/x/text v0.40.0
 
 require (
-	gitea.maximumdirect.net/eric/promptkit-backend-openrouter v1.0.0 // indirect
-	gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome v1.0.0 // indirect
+	gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260926.0 // indirect
+	gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260926.0 // indirect
 	go.yaml.in/yaml/v4 v4.0.0-rc.6 // indirect
 )

go.sum

@@ -1,11 +1,11 @@
-gitea.maximumdirect.net/eric/ConfigKit v0.3.0 h1:LgXEUjR0KsgwGBznOWa8FJTQ+iElctHtI1via5vKdu4=
-gitea.maximumdirect.net/eric/ConfigKit v0.3.0/go.mod h1:tYWpsrbLyu05r8+1MapWp5fN6ZrX9I8hU2xEPedYmYk=
-gitea.maximumdirect.net/eric/promptkit v0.9.0 h1:IpvDRC8L6xRxQ9hpuyKOmMc5b6MeLTKYyx+h1YAjy08=
-gitea.maximumdirect.net/eric/promptkit v0.9.0/go.mod h1:oMJ/WUJImUtwJ5e+6MAGECPYAErAkOaKel0G+3T/b4E=
-gitea.maximumdirect.net/eric/promptkit-backend-openrouter v1.0.0 h1:lc062euk2qseO//D762i3JaFyulDNML3eQQX7DkYTho=
-gitea.maximumdirect.net/eric/promptkit-backend-openrouter v1.0.0/go.mod h1:AIa7kAu2mfrRQgcspe4L+DW51WqgnALQT60lqkEywJI=
-gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome v1.0.0 h1:j9YY7wsTVjzke2kHH4YAzpU0oUpM+x+nXwl1IeS+2eg=
-gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome v1.0.0/go.mod h1:4RNS+LILDg4JbS4Ts9Lwy1C92wauXJIbeQaalps4Koo=
+gitea.maximumdirect.net/eric/ConfigKit v0.4.2 h1:ZMxmv8pOnLtAx2hFTf8Z+pHKUbR89xErkBhwjr4yK24=
+gitea.maximumdirect.net/eric/ConfigKit v0.4.2/go.mod h1:tYWpsrbLyu05r8+1MapWp5fN6ZrX9I8hU2xEPedYmYk=
+gitea.maximumdirect.net/eric/promptkit v0.11.2 h1:2RqI+KtflvSh7vLQaTAQCmMaFQscEA7EPwPazyvXRoY=
+gitea.maximumdirect.net/eric/promptkit v0.11.2/go.mod h1:onm/FBPUKQ8/NSPwTEk26Ut+dVX2iXcq8vEseB+g/0E=
+gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260926.0 h1:wdab+R+lgMZxzYwhbAuCrW7zdSQ1cW9ovBR6UzLmZR4=
+gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260926.0/go.mod h1:a3VBbh9oaGXD6ruxhtwHj+AWW6DY/SSyby1QtMmYSUo=
+gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260926.0 h1:baCCIB6Ee5t0S4Zc++NTBIPcJEv5UPS6DlSrpZfykwg=
+gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260926.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=

internal/cli/catalog.go

@@ -157,13 +157,15 @@ func buildProductionLLMClient(ctx context.Context, cfg config.Config, profileID
 		return nil, nil, fmt.Errorf("production asset registry must not be nil")
 	}
 	recorder := llm.NewLLMProfileRecorder()
+	transientRetries := cfg.PromptKit.TransientRetries
 	client, err := llm.NewPromptKitClient(llm.PromptKitClientConfig{
-		ProfileDir:      cfg.PromptKit.ProfileDir,
-		ProfileFile:     cfg.PromptKit.ProfileFile,
-		LocalBackend:    mapPromptKitLocalBackend(cfg.PromptKit.LocalBackend),
-		Assets:          assets,
-		Recorder:        recorder,
-		ReasoningEffort: overrides.ReasoningEffort,
+		ProfileDir:       cfg.PromptKit.ProfileDir,
+		ProfileFile:      cfg.PromptKit.ProfileFile,
+		TransientRetries: &transientRetries,
+		LocalBackend:     mapPromptKitLocalBackend(cfg.PromptKit.LocalBackend),
+		Assets:           assets,
+		Recorder:         recorder,
+		ReasoningEffort:  overrides.ReasoningEffort,
 	})
 	if err != nil {
 		return nil, nil, fmt.Errorf("create PromptKit-backed LLM client: %w", err)

internal/cli/configkit_commands.go

@@ -16,7 +16,7 @@ func runConfigEffective(args []string, stdout, stderr io.Writer, opts Options) i
 	fs := flag.NewFlagSet("config effective", flag.ContinueOnError)
 	fs.SetOutput(io.Discard)
 	configPath := fs.String("config", "", "config file path")
-	profile := fs.String("config-profile", "", "configuration profile")
+	overlay := fs.String("config-overlay", "", "configuration overlay")
 	if err := fs.Parse(args); err != nil {
 		fmt.Fprintf(stderr, "notarius: %v\n", err)
 		return 2
@@ -25,7 +25,7 @@ func runConfigEffective(args []string, stdout, stderr io.Writer, opts Options) i
 		fmt.Fprintf(stderr, "notarius: unexpected argument %q\n", fs.Arg(0))
 		return 2
 	}
-	loaded, _, err := loadConfigKit(*configPath, *profile, nil, opts)
+	loaded, _, err := loadConfigKit(*configPath, *overlay, nil, opts)
 	if err != nil {
 		writeConfigLoadError(stderr, err)
 		return 1
@@ -41,7 +41,7 @@ func runConfigExplain(args []string, stdout, stderr io.Writer, opts Options) int
 	fs := flag.NewFlagSet("config explain", flag.ContinueOnError)
 	fs.SetOutput(io.Discard)
 	configPath := fs.String("config", "", "config file path")
-	profile := fs.String("config-profile", "", "configuration profile")
+	overlay := fs.String("config-overlay", "", "configuration overlay")
 	if err := fs.Parse(args); err != nil {
 		fmt.Fprintf(stderr, "notarius: %v\n", err)
 		return 2
@@ -56,7 +56,7 @@ func runConfigExplain(args []string, stdout, stderr io.Writer, opts Options) int
 		fmt.Fprintf(stderr, "notarius: %q is not a canonical JSON Pointer\n", pointer)
 		return 2
 	}
-	loaded, _, err := loadConfigKit(*configPath, *profile, nil, opts)
+	loaded, _, err := loadConfigKit(*configPath, *overlay, nil, opts)
 	if err != nil {
 		writeConfigLoadError(stderr, err)
 		return 1
@@ -72,7 +72,7 @@ func runConfigValidate(args []string, stdout, stderr io.Writer, opts Options) in
 	fs := flag.NewFlagSet("config validate", flag.ContinueOnError)
 	fs.SetOutput(io.Discard)
 	configPath := fs.String("config", "", "config file path")
-	profile := fs.String("config-profile", "", "configuration profile")
+	overlay := fs.String("config-overlay", "", "configuration overlay")
 	pipelineID := fs.String("pipeline", "", "pipeline ID")
 	onlyRaw := fs.String("only", "", "comma-separated artifact lanes")
 	if err := fs.Parse(args); err != nil {
@@ -92,7 +92,7 @@ func runConfigValidate(args []string, stdout, stderr io.Writer, opts Options) in
 		fmt.Fprintf(stderr, "notarius: %v\n", err)
 		return 2
 	}
-	loaded, path, err := loadConfigKit(*configPath, *profile, nil, opts)
+	loaded, path, err := loadConfigKit(*configPath, *overlay, nil, opts)
 	if err != nil {
 		writeConfigLoadError(stderr, err)
 		return 1
@@ -123,7 +123,7 @@ func runPipelinesList(args []string, stdout, stderr io.Writer, opts Options) int
 	fs := flag.NewFlagSet("pipelines list", flag.ContinueOnError)
 	fs.SetOutput(io.Discard)
 	configPath := fs.String("config", "", "config file path")
-	profile := fs.String("config-profile", "", "configuration profile")
+	overlay := fs.String("config-overlay", "", "configuration overlay")
 	jsonOutput := fs.Bool("json", false, "write JSON output")
 	if err := fs.Parse(args); err != nil {
 		fmt.Fprintf(stderr, "notarius: %v\n", err)
@@ -133,7 +133,7 @@ func runPipelinesList(args []string, stdout, stderr io.Writer, opts Options) int
 		fmt.Fprintf(stderr, "notarius: unexpected argument %q\n", fs.Arg(0))
 		return 2
 	}
-	loaded, _, err := loadConfigKit(*configPath, *profile, nil, opts)
+	loaded, _, err := loadConfigKit(*configPath, *overlay, nil, opts)
 	if err != nil {
 		writeConfigLoadError(stderr, err)
 		return 1

internal/cli/configkit_commands_test.go

@@ -14,22 +14,49 @@ import (
 	"gitea.maximumdirect.net/eric/notarius/internal/framework/contracts"
 )
 
-func TestConfigKitReadOnlyCommandsLoadImportsAndProfiles(t *testing.T) {
+func TestConfigKitReadOnlyCommandsLoadImportsAndOverlays(t *testing.T) {
 	t.Parallel()
 	root := t.TempDir()
 	path := filepath.Join(root, "notarius.yml")
 	writeConfigKitFile(t, filepath.Join(root, "fragment.yml"), "pipelines:\n  imported:\n    input: {module: input}\n")
-	writeConfigKitFile(t, filepath.Join(root, "profiles", "development.yml"), "pipelines:\n  profiled:\n    input: {module: input}\n")
+	writeConfigKitFile(t, filepath.Join(root, "overlays", "development.yml"), "pipelines:\n  overlaid:\n    input: {module: input}\n")
 	writeConfigKitFile(t, path, "version: 5\nconfigkit:\n  imports:\n    - path: fragment.yml\npipelines:\n  base:\n    input: {module: input}\n")
 	var stdout, stderr bytes.Buffer
-	if code := RunWithOptions([]string{"pipelines", "list", "--config", path, "--config-profile", "development"}, &stdout, &stderr, commandContractOptions(t)); code != 0 || stdout.String() != "base\nimported\nprofiled\n" {
+	if code := RunWithOptions([]string{"pipelines", "list", "--config", path, "--config-overlay", "development"}, &stdout, &stderr, commandContractOptions(t)); code != 0 || stdout.String() != "base\nimported\noverlaid\n" {
 		t.Fatalf("list = %d, %q, %q", code, stdout.String(), stderr.String())
 	}
 	stdout.Reset()
 	stderr.Reset()
-	if code := RunWithOptions([]string{"config", "validate", "--config", path, "--config-profile", "development"}, &stdout, &stderr, commandContractOptions(t)); code != 0 || !strings.Contains(stdout.String(), "is valid") {
+	if code := RunWithOptions([]string{"config", "validate", "--config", path, "--config-overlay", "development"}, &stdout, &stderr, commandContractOptions(t)); code != 0 || !strings.Contains(stdout.String(), "is valid") {
 		t.Fatalf("validate = %d, %q, %q", code, stdout.String(), stderr.String())
 	}
+	for _, selection := range [][]string{nil, {"--config-overlay", ""}, {"--config-overlay", "default"}} {
+		stdout.Reset()
+		stderr.Reset()
+		args := append([]string{"pipelines", "list", "--config", path}, selection...)
+		if code := RunWithOptions(args, &stdout, &stderr, commandContractOptions(t)); code != 0 || stdout.String() != "base\nimported\n" || stderr.Len() != 0 {
+			t.Fatalf("base list %q = %d, %q, %q", selection, code, stdout.String(), stderr.String())
+		}
+	}
+}
+
+func TestRetiredConfigProfileFlagUsesNormalUnknownFlagBehavior(t *testing.T) {
+	t.Parallel()
+
+	for _, args := range [][]string{
+		{"run", "sample", "--config-profile=development"},
+		{"config", "validate", "--config-profile=development"},
+		{"config", "effective", "--config-profile=development"},
+		{"config", "explain", "--config-profile=development", ""},
+		{"pipelines", "list", "--config-profile=development"},
+	} {
+		t.Run(strings.Join(args[:2], " "), func(t *testing.T) {
+			var stdout, stderr bytes.Buffer
+			if code := RunWithOptions(args, &stdout, &stderr, commandContractOptions(t)); code != 2 || stdout.Len() != 0 || !strings.Contains(stderr.String(), "not defined") {
+				t.Fatalf("args=%q code=%d stdout=%q stderr=%q", args, code, stdout.String(), stderr.String())
+			}
+		})
+	}
 }
 
 func TestConfigKitReadOnlyCommandsRejectVersionFour(t *testing.T) {
@@ -53,8 +80,8 @@ pipelines:
   "0":
     input: {module: input}
 `)
-	writeConfigKitFile(t, filepath.Join(root, "profiles", "development.yml"), "concurrency:\n  total_llm: 3\n")
-	writeConfigKitFile(t, filepath.Join(root, "profiles", "retired.yml"), "pipelines: null\n")
+	writeConfigKitFile(t, filepath.Join(root, "overlays", "development.yml"), "concurrency:\n  total_llm: 3\n")
+	writeConfigKitFile(t, filepath.Join(root, "overlays", "retired.yml"), "pipelines: null\n")
 
 	providerCalled := false
 	opts := commandContractOptions(t)
@@ -64,7 +91,7 @@ pipelines:
 	}
 
 	var stdout, stderr bytes.Buffer
-	if code := RunWithOptions([]string{"config", "effective", "--config", path, "--config-profile", "development"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), "total_llm: 3") || stderr.Len() != 0 {
+	if code := RunWithOptions([]string{"config", "effective", "--config", path, "--config-overlay", "development"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), "total_llm: 3") || stderr.Len() != 0 {
 		t.Fatalf("effective = %d, %q, %q", code, stdout.String(), stderr.String())
 	}
 	if providerCalled {
@@ -73,7 +100,7 @@ pipelines:
 
 	stdout.Reset()
 	stderr.Reset()
-	if code := RunWithOptions([]string{"config", "explain", "--config", path, "--config-profile", "development", "/concurrency/total_llm"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), `path: "/concurrency/total_llm"`) || stderr.Len() != 0 {
+	if code := RunWithOptions([]string{"config", "explain", "--config", path, "--config-overlay", "development", "/concurrency/total_llm"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), `path: "/concurrency/total_llm"`) || stderr.Len() != 0 {
 		t.Fatalf("explain effective = %d, %q, %q", code, stdout.String(), stderr.String())
 	}
 
@@ -85,7 +112,7 @@ pipelines:
 
 	stdout.Reset()
 	stderr.Reset()
-	if code := RunWithOptions([]string{"config", "explain", "--config", path, "--config-profile", "retired", "/pipelines/0"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), `path: "/pipelines/0"`) || stderr.Len() != 0 {
+	if code := RunWithOptions([]string{"config", "explain", "--config", path, "--config-overlay", "retired", "/pipelines/0"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), `path: "/pipelines/0"`) || stderr.Len() != 0 {
 		t.Fatalf("explain removed mapping key = %d, %q, %q", code, stdout.String(), stderr.String())
 	}
 }

internal/cli/configkit_load.go

@@ -10,7 +10,7 @@ import (
 	"gitea.maximumdirect.net/eric/notarius/internal/core/config"
 )
 
-func loadConfigKit(configPath, profile string, overrides []configkit.Override, opts Options) (*config.LoadedConfig, string, error) {
+func loadConfigKit(configPath, overlay string, overrides []configkit.Override, opts Options) (*config.LoadedConfig, string, error) {
 	path, err := discoverConfigPath(configPath, opts)
 	if err != nil {
 		return nil, "", err
@@ -19,7 +19,7 @@ func loadConfigKit(configPath, profile string, overrides []configkit.Override, o
 	if err != nil {
 		return nil, "", fmt.Errorf("determine invocation directory: %w", err)
 	}
-	loaded, err := config.Load(path, config.LoadOptions{Profile: profile, Overrides: overrides, InvocationDirectory: workingDirectory})
+	loaded, err := config.Load(path, config.LoadOptions{Overlay: overlay, Overrides: overrides, InvocationDirectory: workingDirectory})
 	if err != nil {
 		return nil, "", err
 	}
@@ -31,7 +31,7 @@ func writeConfigLoadError(output io.Writer, err error) {
 	if errors.As(err, &loadError) {
 		if writeErr := configkit.WriteDiagnostics(output, loadError.Diagnostics()); writeErr == nil {
 			// ConfigKit's locations contain source IDs. Keep its renderer and
-			// supply the acquired-source legend so imported/profile errors can
+			// supply the acquired-source legend so imported/overlay errors can
 			// be traced to a file. Quoting also escapes terminal controls.
 			for _, source := range loadError.Sources() {
 				label := source.Path

internal/cli/configkit_load_test.go

@@ -13,16 +13,16 @@ import (
 
 func TestConfigLoadDiagnosticsIdentifyComposedSources(t *testing.T) {
 	t.Parallel()
-	for _, profile := range []bool{false, true} {
-		t.Run(strconv.FormatBool(profile), func(t *testing.T) {
+	for _, overlay := range []bool{false, true} {
+		t.Run(strconv.FormatBool(overlay), func(t *testing.T) {
 			root := t.TempDir()
 			main := filepath.Join(root, "config.yml")
 			fragment := filepath.Join(root, "pipeline\n\x1b.yml")
 			args := []string{"config", "validate", "--config", main}
-			if profile {
-				fragment = filepath.Join(root, "profiles", "development.yml")
+			if overlay {
+				fragment = filepath.Join(root, "overlays", "development.yml")
 				writeConfigKitFile(t, main, "version: 5\n")
-				args = append(args, "--config-profile", "development")
+				args = append(args, "--config-overlay", "development")
 			} else {
 				writeConfigKitFile(t, main, "version: 5\nconfigkit:\n  imports:\n    - path: "+strconv.Quote(filepath.Base(fragment))+"\n")
 			}
@@ -43,18 +43,18 @@ func TestConfigLoadDiagnosticsIdentifyComposedSources(t *testing.T) {
 	}
 }
 
-func TestLoadConfigKitUsesDiscoveryProfileAndOverrides(t *testing.T) {
+func TestLoadConfigKitUsesDiscoveryOverlayAndOverrides(t *testing.T) {
 	t.Parallel()
 	root := t.TempDir()
 	path := filepath.Join(root, "notarius.yml")
 	writeConfigKitFile(t, path, "version: 5\npipelines:\n  base:\n    input: {module: input}\n")
-	profiles := filepath.Join(root, "profiles")
-	writeConfigKitFile(t, filepath.Join(profiles, "development.yml"), "pipelines:\n  profiled:\n    input: {module: input}\n")
+	overlays := filepath.Join(root, "overlays")
+	writeConfigKitFile(t, filepath.Join(overlays, "development.yml"), "pipelines:\n  overlaid:\n    input: {module: input}\n")
 	loaded, gotPath, err := loadConfigKit(path, "development", []configkit.Override{{Path: configkit.Keys("output", "directory"), Value: "generated", Flag: "--output"}}, commandContractOptions(t))
 	if err != nil {
 		t.Fatalf("loadConfigKit() error = %v", err)
 	}
-	if gotPath != path || loaded.Config.Pipelines["profiled"].Input.Module != "input" || loaded.Config.Output.Directory == "generated" {
+	if gotPath != path || loaded.Config.Pipelines["overlaid"].Input.Module != "input" || loaded.Config.Output.Directory == "generated" {
 		t.Fatalf("loaded = %#v, path=%q", loaded.Config, gotPath)
 	}
 }

internal/cli/example_contract_test.go

@@ -136,19 +136,19 @@ func TestMaintainedConfigurationExampleSet(t *testing.T) {
 		t.Fatalf("maintained configuration examples = %q, want only the minimal and complete D&D examples", got)
 	}
 
-	profileEntries, err := os.ReadDir(repositoryPath("examples", "profiles"))
+	overlayEntries, err := os.ReadDir(repositoryPath("examples", "overlays"))
 	if err != nil {
 		t.Fatal(err)
 	}
 	names = names[:0]
-	for _, entry := range profileEntries {
+	for _, entry := range overlayEntries {
 		if !entry.IsDir() && strings.HasSuffix(entry.Name(), ".yml") {
 			names = append(names, entry.Name())
 		}
 	}
 	sort.Strings(names)
 	if got := strings.Join(names, ","); got != "development.yml" {
-		t.Fatalf("maintained configuration profiles = %q, want development.yml", got)
+		t.Fatalf("maintained configuration overlays = %q, want development.yml", got)
 	}
 	llmProfiles, err := os.ReadDir(repositoryPath("examples", "llm-profiles"))
 	if err != nil {

internal/cli/production_contract_test.go

@@ -557,11 +557,16 @@ func TestNormalizeOptionsSharesProductionProfileAssetsWithDefaultRuntime(t *test
 func TestProductionLLMClientFactoryUsesConfiguredLocalBackend(t *testing.T) {
 	var providerCalls atomic.Int32
 	server := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
-		providerCalls.Add(1)
+		call := providerCalls.Add(1)
 		if r.URL.Path != "/v1/chat/completions" {
 			t.Errorf("provider path = %q, want /v1/chat/completions", r.URL.Path)
 		}
 		w.Header().Set("Content-Type", "application/json")
+		if call == 1 {
+			w.WriteHeader(http.StatusServiceUnavailable)
+			_, _ = w.Write([]byte(`{"error":{"message":"transient"}}`))
+			return
+		}
 		_, _ = w.Write([]byte(`{
 			"choices": [{"message": {"role": "assistant", "content": "{\"ok\":true}"}}],
 			"usage": {"prompt_tokens": 3, "completion_tokens": 4, "total_tokens": 7}
@@ -596,6 +601,7 @@ output:
 
 	cfg := config.Default()
 	cfg.PromptKit.ProfileFile = profilePath
+	cfg.PromptKit.TransientRetries = 1
 	cfg.PromptKit.LocalBackend = &config.PromptKitLocalBackendConfig{
 		Endpoint:         server.URL + "/v1",
 		ConcurrencyLimit: 2,
@@ -624,8 +630,8 @@ output:
 	if err != nil {
 		t.Fatalf("CompleteStructured() error = %v, want nil", err)
 	}
-	if providerCalls.Load() != 1 {
-		t.Fatalf("provider calls = %d, want 1", providerCalls.Load())
+	if providerCalls.Load() != 2 {
+		t.Fatalf("provider calls = %d, want 2", providerCalls.Load())
 	}
 	provider, ok := client.(contracts.LLMProfileManifestProvider)
 	if !ok {

internal/cli/run.go

@@ -34,10 +34,10 @@ const usage = `Usage:
   notarius help
   notarius --version
   notarius run <pipeline-id> --input path/to/source.json [--json] [flags]
-  notarius config validate --config path/to/config.yml [--config-profile name] [--pipeline pipeline-id] [--only lane-a,lane-b]
-  notarius config effective --config path/to/config.yml [--config-profile name]
-  notarius config explain --config path/to/config.yml [--config-profile name] <json-pointer>
-  notarius pipelines list --config path/to/config.yml [--config-profile name] [--json]
+  notarius config validate --config path/to/config.yml [--config-overlay name] [--pipeline pipeline-id] [--only lane-a,lane-b]
+  notarius config effective --config path/to/config.yml [--config-overlay name]
+  notarius config explain --config path/to/config.yml [--config-overlay name] <json-pointer>
+  notarius pipelines list --config path/to/config.yml [--config-overlay name] [--json]
 `
 
 type Options struct {
@@ -160,7 +160,7 @@ func runPipelineCommand(args []string, stdout, stderr io.Writer, opts Options) i
 	fs := flag.NewFlagSet("run", flag.ContinueOnError)
 	fs.SetOutput(io.Discard)
 	configPath := fs.String("config", "", "config file path")
-	configProfile := fs.String("config-profile", "", "configuration profile")
+	configOverlay := fs.String("config-overlay", "", "configuration overlay")
 	inputPath := fs.String("input", "", "source input file path")
 	onlyRaw := fs.String("only", "", "comma-separated artifact lanes")
 	outputDir := fs.String("output-dir", "", "output directory")
@@ -268,7 +268,7 @@ func runPipelineCommand(args []string, stdout, stderr io.Writer, opts Options) i
 		return 2
 	}
 
-	loaded, loadedConfigPath, err := loadConfigKit(*configPath, *configProfile, runConfigurationOverrides(chunkCache, *outputDir, *debugDir), opts)
+	loaded, loadedConfigPath, err := loadConfigKit(*configPath, *configOverlay, runConfigurationOverrides(chunkCache, *outputDir, *debugDir), opts)
 	if err != nil {
 		writeConfigLoadError(stderr, err)
 		return 1
@@ -331,7 +331,7 @@ func runPipelineCommand(args []string, stdout, stderr io.Writer, opts Options) i
 		InputPath:               strings.TrimSpace(*inputPath),
 		ConfigPath:              loadedConfigPath,
 		ConfigSource:            configSource(*configPath),
-		ConfigProfile:           effectiveConfigProfile(*configProfile),
+		ConfigOverlay:           effectiveConfigOverlay(*configOverlay),
 		OnlyLanes:               append([]string(nil), only...),
 		ChunkCacheOverride:      chunkCache.explicitValue(),
 		ReasoningEffortOverride: runtimeOverrides.ReasoningEffort,
@@ -877,7 +877,7 @@ func reorderRunArgs(args []string) []string {
 
 func runFlagTakesValue(arg string) bool {
 	switch arg {
-	case "--config", "--config-profile", "--input", "--only", "--output-dir", "--debug-dir", "--llm-profile", "--session-id", "--reasoning-effort", "--chunk_cache", "--reference", "--without-reference", "--recompute-step":
+	case "--config", "--config-overlay", "--input", "--only", "--output-dir", "--debug-dir", "--llm-profile", "--session-id", "--reasoning-effort", "--chunk_cache", "--reference", "--without-reference", "--recompute-step":
 		return true
 	default:
 		return false
@@ -963,7 +963,7 @@ func chunkPlanStoreForRun(cfg config.ChunkPlanCacheConfig, opts Options) (pipeli
 
 func validateRunFlagValues(args []string) error {
 	for i, arg := range args {
-		if arg != "--config-profile" && arg != "--session-id" && arg != "--reasoning-effort" {
+		if arg != "--config-overlay" && arg != "--session-id" && arg != "--reasoning-effort" {
 			continue
 		}
 		if i+1 >= len(args) || strings.HasPrefix(args[i+1], "-") {
@@ -973,11 +973,11 @@ func validateRunFlagValues(args []string) error {
 	return nil
 }
 
-func effectiveConfigProfile(profile string) string {
-	if profile == "" || profile == "default" {
+func effectiveConfigOverlay(overlay string) string {
+	if overlay == "" || overlay == "default" {
 		return ""
 	}
-	return profile
+	return overlay
 }
 
 func flagWasProvided(args []string, name string) bool {

internal/cli/run_contract_test.go

@@ -38,8 +38,8 @@ func TestRunControlsRejectSyntaxWithoutAllocatingState(t *testing.T) {
 		{name: "blank debug directory", args: func(roots stateTestRoots) []string {
 			return []string{"run", "sample", "--config", roots.config, "--input", roots.input, "--debug-dir", ""}
 		}},
-		{name: "missing configuration profile", args: func(roots stateTestRoots) []string {
-			return []string{"run", "sample", "--config", roots.config, "--input", roots.input, "--config-profile"}
+		{name: "missing configuration overlay", args: func(roots stateTestRoots) []string {
+			return []string{"run", "sample", "--config", roots.config, "--input", roots.input, "--config-overlay"}
 		}},
 		{name: "debug directory without debug", args: func(roots stateTestRoots) []string {
 			return []string{"run", "sample", "--config", roots.config, "--input", roots.input, "--debug-dir", filepath.Join(filepath.Dir(roots.debug), "requested-debug")}
@@ -247,38 +247,38 @@ func TestRunStateRootsHonorEnvironmentFlagsAndDefaults(t *testing.T) {
 	})
 }
 
-func TestRunAppliesConfigurationProfileAndRecordsSelection(t *testing.T) {
+func TestRunAppliesConfigurationOverlayAndRecordsSelection(t *testing.T) {
 	roots := newStateTestRoots(t)
-	profileDirectory := filepath.Join(filepath.Dir(roots.config), "profiles")
-	profileOutput := filepath.Join(profileDirectory, "profile-output")
-	profileDebug := filepath.Join(profileDirectory, "profile-debug")
-	writeConfigKitFile(t, filepath.Join(profileDirectory, "development.yml"), "output:\n  directory: ./profile-output\ndebug:\n  directory: ./profile-debug\n")
+	overlayDirectory := filepath.Join(filepath.Dir(roots.config), "overlays")
+	overlayOutput := filepath.Join(overlayDirectory, "overlay-output")
+	overlayDebug := filepath.Join(overlayDirectory, "overlay-debug")
+	writeConfigKitFile(t, filepath.Join(overlayDirectory, "development.yml"), "output:\n  directory: ./overlay-output\ndebug:\n  directory: ./overlay-debug\n")
 
 	var stdout, stderr bytes.Buffer
 	code := RunWithOptions([]string{
-		"run", "sample", "--config", roots.config, "--config-profile", "development",
+		"run", "sample", "--config", roots.config, "--config-overlay", "development",
 		"--input", roots.input, "--chunk_cache", "bypass", "--debug",
 	}, &stdout, &stderr, newStateTestHarness().options())
 	if code != 0 || stderr.Len() != 0 {
 		t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout.String(), stderr.String())
 	}
-	assertFile(t, filepath.Join(profileOutput, filepath.Base(onlyChildDir(t, profileOutput)), "result.json"))
-	bundle := onlyChildDir(t, profileDebug)
+	assertFile(t, filepath.Join(overlayOutput, filepath.Base(onlyChildDir(t, overlayOutput)), "result.json"))
+	bundle := onlyChildDir(t, overlayDebug)
 	var invocation debugbundle.Invocation
 	readStateTestSummaryJSON(t, bundle, "invocation.json", &invocation)
-	if invocation.ConfigProfile != "development" {
-		t.Fatalf("config profile = %q, want development", invocation.ConfigProfile)
+	if invocation.ConfigOverlay != "development" {
+		t.Fatalf("config overlay = %q, want development", invocation.ConfigOverlay)
 	}
 }
 
-func TestEffectiveConfigProfileOmitsBaseSelection(t *testing.T) {
-	for _, profile := range []string{"", "default"} {
-		if got := effectiveConfigProfile(profile); got != "" {
-			t.Fatalf("effectiveConfigProfile(%q) = %q, want empty", profile, got)
+func TestEffectiveConfigOverlayOmitsBaseSelection(t *testing.T) {
+	for _, overlay := range []string{"", "default"} {
+		if got := effectiveConfigOverlay(overlay); got != "" {
+			t.Fatalf("effectiveConfigOverlay(%q) = %q, want empty", overlay, got)
 		}
 	}
-	if got := effectiveConfigProfile("development"); got != "development" {
-		t.Fatalf("effectiveConfigProfile(development) = %q", got)
+	if got := effectiveConfigOverlay("development"); got != "development" {
+		t.Fatalf("effectiveConfigOverlay(development) = %q", got)
 	}
 }
 

internal/core/config/config.go

@@ -14,9 +14,10 @@ type Config struct {
 }
 
 type PromptKitConfig struct {
-	ProfileDir   string                       `json:"profile_dir,omitempty"`
-	ProfileFile  string                       `json:"profile_file,omitempty"`
-	LocalBackend *PromptKitLocalBackendConfig `json:"local_backend,omitempty"`
+	ProfileDir       string                       `json:"profile_dir,omitempty"`
+	ProfileFile      string                       `json:"profile_file,omitempty"`
+	TransientRetries int                          `json:"transient_retries"`
+	LocalBackend     *PromptKitLocalBackendConfig `json:"local_backend,omitempty"`
 }
 
 type PromptKitLocalBackendConfig struct {
@@ -29,7 +30,10 @@ type ConcurrencyConfig struct {
 	StageWorkers map[string]int `json:"stage_workers"`
 }
 
-const defaultLLMConcurrency = 16
+const (
+	defaultLLMConcurrency   = 16
+	defaultTransientRetries = 2
+)
 
 type OutputConfig struct {
 	Directory string `json:"directory"`
@@ -55,6 +59,7 @@ type DebugConfig struct {
 
 func Default() Config {
 	return Config{
+		PromptKit: PromptKitConfig{TransientRetries: defaultTransientRetries},
 		Pipelines: map[string]pipeline.PipelineProfile{},
 		Concurrency: ConcurrencyConfig{
 			TotalLLM:     defaultLLMConcurrency,

internal/core/config/document.go

@@ -16,9 +16,10 @@ type Document struct {
 }
 
 type PromptKitDocument struct {
-	ProfileDir   *string                        `yaml:"profile_dir,omitempty"`
-	ProfileFile  *string                        `yaml:"profile_file,omitempty"`
-	LocalBackend *PromptKitLocalBackendDocument `yaml:"local_backend,omitempty"`
+	ProfileDir       *string                        `yaml:"profile_dir,omitempty"`
+	ProfileFile      *string                        `yaml:"profile_file,omitempty"`
+	TransientRetries *int                           `yaml:"transient_retries,omitempty"`
+	LocalBackend     *PromptKitLocalBackendDocument `yaml:"local_backend,omitempty"`
 }
 
 type PromptKitLocalBackendDocument struct {

internal/core/config/document_paths_test.go

@@ -77,27 +77,48 @@ func TestDocumentPathsUseInvocationDirectoryForOverrides(t *testing.T) {
 	}
 }
 
-func TestDocumentPathsUseProfileDeclarationDirectory(t *testing.T) {
+func TestDocumentPathsUseOverlayDeclarationDirectory(t *testing.T) {
 	t.Parallel()
 
 	root := t.TempDir()
-	profiles := filepath.Join(root, "profiles")
-	if err := os.MkdirAll(profiles, 0o700); err != nil {
+	overlays := filepath.Join(root, "overlays")
+	if err := os.MkdirAll(overlays, 0o700); err != nil {
 		t.Fatal(err)
 	}
 	main := filepath.Join(root, "notarius.yml")
 	if err := os.WriteFile(main, []byte("version: 5\n"), 0o600); err != nil {
 		t.Fatal(err)
 	}
-	if err := os.WriteFile(filepath.Join(profiles, "development.yml"), []byte("output: {directory: ./profile-output}\n"), 0o600); err != nil {
+	if err := os.WriteFile(filepath.Join(overlays, "development.yml"), []byte("output: {directory: ./overlay-output}\n"), 0o600); err != nil {
 		t.Fatal(err)
 	}
-	loaded, err := loadConfig(main, LoadOptions{Profile: "development"})
+	loaded, err := loadConfig(main, LoadOptions{Overlay: "development"})
 	if err != nil {
 		t.Fatalf("loadConfig() error = %v", err)
 	}
-	if got := loaded.Config.Output.Directory; got != filepath.Join(profiles, "profile-output") {
-		t.Fatalf("profile directory = %q", got)
+	if got := loaded.Config.Output.Directory; got != filepath.Join(overlays, "overlay-output") {
+		t.Fatalf("overlay directory = %q", got)
+	}
+}
+
+func TestDocumentLoadDoesNotFallBackToLegacyProfileDirectory(t *testing.T) {
+	t.Parallel()
+
+	root := t.TempDir()
+	main := filepath.Join(root, "notarius.yml")
+	if err := os.WriteFile(main, []byte("version: 5\n"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	legacy := filepath.Join(root, "profiles", "development.yml")
+	if err := os.MkdirAll(filepath.Dir(legacy), 0o700); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(legacy, []byte("output: {directory: ./legacy-output}\n"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+
+	if _, err := loadConfig(main, LoadOptions{Overlay: "development"}); err == nil {
+		t.Fatal("loadConfig() error = nil, want missing overlay")
 	}
 }
 

internal/core/config/load.go

@@ -10,7 +10,7 @@ import (
 // boundary. It is intentionally narrow: configuration discovery and CLI flag
 // parsing remain outside this package.
 type LoadOptions struct {
-	Profile             string
+	Overlay             string
 	Overrides           []configkit.Override
 	InvocationDirectory string
 }
@@ -30,7 +30,7 @@ func loadDocumentWithSource(source configkit.Source, options LoadOptions, import
 	return configkit.Load(source, configkit.Options[Document]{
 		Definition: documentDefinition(state),
 		Imports:    imports,
-		Profile:    options.Profile,
+		Overlay:    options.Overlay,
 		Overrides:  options.Overrides,
 	})
 }
@@ -63,6 +63,9 @@ func documentDefinition(state *documentLoadState) configkit.Definition[Document]
 
 func documentDefaults() Document {
 	return Document{
+		PromptKit: &PromptKitDocument{
+			TransientRetries: documentValue(defaultTransientRetries),
+		},
 		Pipelines: map[string]PipelineDocument{},
 		Concurrency: &ConcurrencyDocument{
 			TotalLLM:     documentValue(defaultLLMConcurrency),

internal/core/config/loaded_config.go

@@ -94,6 +94,9 @@ func documentToConfig(document Document) (Config, error) {
 		if document.PromptKit.ProfileFile != nil {
 			config.PromptKit.ProfileFile = *document.PromptKit.ProfileFile
 		}
+		if document.PromptKit.TransientRetries != nil {
+			config.PromptKit.TransientRetries = *document.PromptKit.TransientRetries
+		}
 		if document.PromptKit.LocalBackend != nil {
 			backend := PromptKitLocalBackendConfig{}
 			if document.PromptKit.LocalBackend.Endpoint != nil {

internal/core/config/loaded_config_test.go

@@ -2,6 +2,7 @@ package config
 
 import (
 	"bytes"
+	"strconv"
 	"strings"
 	"testing"
 
@@ -58,6 +59,44 @@ pipelines:
 	}
 }
 
+func TestLoadedConfigResolvesPromptKitTransientRetriesAndRetainsInspection(t *testing.T) {
+	t.Parallel()
+
+	for _, test := range []struct {
+		name     string
+		document string
+		want     int
+	}{
+		{name: "omitted", document: "version: 5\n", want: defaultTransientRetries},
+		{name: "disabled", document: "version: 5\npromptkit:\n  transient_retries: 0\n", want: 0},
+		{name: "configured", document: "version: 5\npromptkit:\n  transient_retries: 5\n", want: 5},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			loaded, err := loadConfigSource(configkit.Bytes("document.yml", []byte(test.document)), LoadOptions{})
+			if err != nil {
+				t.Fatal(err)
+			}
+			if got := loaded.Config.PromptKit.TransientRetries; got != test.want {
+				t.Fatalf("transient retries = %d, want %d", got, test.want)
+			}
+			var effective bytes.Buffer
+			if err := loaded.WriteEffective(&effective); err != nil {
+				t.Fatal(err)
+			}
+			if !strings.Contains(effective.String(), "transient_retries: "+strconv.Itoa(test.want)) {
+				t.Fatalf("effective configuration = %q", effective.String())
+			}
+			var explanation bytes.Buffer
+			if err := loaded.WriteExplanation(&explanation, "/promptkit/transient_retries"); err != nil {
+				t.Fatal(err)
+			}
+			if !strings.Contains(explanation.String(), strconv.Itoa(test.want)) {
+				t.Fatalf("explanation = %q", explanation.String())
+			}
+		})
+	}
+}
+
 func TestLoadedConfigOwnsRuntimeValuesAndKeepsFrozenInspection(t *testing.T) {
 	t.Parallel()
 

internal/core/config/operational_document.go

@@ -167,6 +167,11 @@ func validateDocumentPromptKit(promptKit *PromptKitDocument, validation *configk
 	if err := validatePromptKitProfileSources(profileDir, profileFile); err != nil {
 		validation.Error(configkit.Keys("promptkit"), err.Error())
 	}
+	if promptKit.TransientRetries == nil {
+		validation.Error(configkit.Keys("promptkit", "transient_retries"), "must be an integer")
+	} else if err := validatePromptKitTransientRetries(*promptKit.TransientRetries); err != nil {
+		validation.Error(configkit.Keys("promptkit", "transient_retries"), err.Error())
+	}
 	if promptKit.LocalBackend == nil {
 		return
 	}
@@ -283,6 +288,13 @@ func validatePromptKitLocalBackendConcurrencyLimit(concurrencyLimit int) error {
 	return nil
 }
 
+func validatePromptKitTransientRetries(transientRetries int) error {
+	if transientRetries < 0 {
+		return fmt.Errorf("promptkit.transient_retries must not be negative")
+	}
+	return nil
+}
+
 func validateRequiredPath(name, value string) error {
 	if strings.TrimSpace(value) == "" {
 		return fmt.Errorf("%s must not be empty", name)

internal/core/config/operational_document_test.go

@@ -105,28 +105,28 @@ debug:
 	}
 }
 
-func TestDocumentLoadDerivesWorkersAfterProfileAndCLIOverrides(t *testing.T) {
+func TestDocumentLoadDerivesWorkersAfterOverlayAndCLIOverrides(t *testing.T) {
 	t.Parallel()
 
 	directory := t.TempDir()
 	main := filepath.Join(directory, "config.yml")
-	profiles := filepath.Join(directory, "profiles")
-	if err := os.Mkdir(profiles, 0o755); err != nil {
+	overlays := filepath.Join(directory, "overlays")
+	if err := os.Mkdir(overlays, 0o755); err != nil {
 		t.Fatal(err)
 	}
 	if err := os.WriteFile(main, []byte("version: 5\nconcurrency:\n  total_llm: 4\n"), 0o600); err != nil {
 		t.Fatal(err)
 	}
-	if err := os.WriteFile(filepath.Join(profiles, "development.yml"), []byte("concurrency:\n  total_llm: 3\n"), 0o600); err != nil {
+	if err := os.WriteFile(filepath.Join(overlays, "development.yml"), []byte("concurrency:\n  total_llm: 3\n"), 0o600); err != nil {
 		t.Fatal(err)
 	}
 
-	profiled, err := loadDocument(main, LoadOptions{Profile: "development"})
+	overlaid, err := loadDocument(main, LoadOptions{Overlay: "development"})
 	if err != nil {
 		t.Fatal(err)
 	}
-	if profiled.Config.Concurrency.TotalLLM == nil || *profiled.Config.Concurrency.TotalLLM != 3 || profiled.Config.Concurrency.StageWorkers["extract"] != 3 {
-		t.Fatalf("profiled concurrency = %#v", profiled.Config.Concurrency)
+	if overlaid.Config.Concurrency.TotalLLM == nil || *overlaid.Config.Concurrency.TotalLLM != 3 || overlaid.Config.Concurrency.StageWorkers["extract"] != 3 {
+		t.Fatalf("overlaid concurrency = %#v", overlaid.Config.Concurrency)
 	}
 
 	overridden, err := loadDocument(main, LoadOptions{Overrides: []configkit.Override{{
@@ -138,6 +138,16 @@ func TestDocumentLoadDerivesWorkersAfterProfileAndCLIOverrides(t *testing.T) {
 	if overridden.Config.Concurrency.TotalLLM == nil || *overridden.Config.Concurrency.TotalLLM != 2 || overridden.Config.Concurrency.StageWorkers["extract"] != 2 {
 		t.Fatalf("overridden concurrency = %#v", overridden.Config.Concurrency)
 	}
+
+	overlaidAndOverridden, err := loadDocument(main, LoadOptions{Overlay: "development", Overrides: []configkit.Override{{
+		Path: configkit.Keys("concurrency", "total_llm"), Value: 2, Flag: "--total-llm",
+	}}})
+	if err != nil {
+		t.Fatal(err)
+	}
+	if overlaidAndOverridden.Config.Concurrency.TotalLLM == nil || *overlaidAndOverridden.Config.Concurrency.TotalLLM != 2 || overlaidAndOverridden.Config.Concurrency.StageWorkers["extract"] != 2 {
+		t.Fatalf("overlaid and overridden concurrency = %#v", overlaidAndOverridden.Config.Concurrency)
+	}
 }
 
 func TestDocumentLoadRetainsExplicitWorkerAndRejectsInvalidOperationalValues(t *testing.T) {
@@ -213,6 +223,13 @@ cache:
 	assertDocumentDiagnostic(t, err, configkit.CodeValidateError, "/promptkit/local_backend/endpoint")
 }
 
+func TestDocumentLoadRejectsNegativePromptKitTransientRetries(t *testing.T) {
+	t.Parallel()
+
+	_, err := loadDocumentSource(configkit.Bytes("promptkit.yml", []byte("version: 5\npromptkit:\n  transient_retries: -1\n")), LoadOptions{})
+	assertDocumentDiagnostic(t, err, configkit.CodeValidateError, "/promptkit/transient_retries")
+}
+
 func assertDocumentDiagnostic(t *testing.T, err error, code configkit.Code, path string) {
 	t.Helper()
 	var loadError *configkit.LoadError

internal/core/config/validation.go

@@ -46,6 +46,9 @@ func validatePromptKit(cfg PromptKitConfig) error {
 	if err := validatePromptKitProfileSources(cfg.ProfileDir, cfg.ProfileFile); err != nil {
 		return err
 	}
+	if err := validatePromptKitTransientRetries(cfg.TransientRetries); err != nil {
+		return err
+	}
 	if cfg.LocalBackend == nil {
 		return nil
 	}

internal/core/config/validation_contract_test.go

@@ -89,6 +89,22 @@ func TestValidatePromptKitSourcesAreMutuallyExclusive(t *testing.T) {
 	assertValidationContains(t, cfg, "promptkit profile_dir and profile_file are mutually exclusive")
 }
 
+func TestValidatePromptKitTransientRetries(t *testing.T) {
+	if got := Default().PromptKit.TransientRetries; got != defaultTransientRetries {
+		t.Fatalf("default transient retries = %d, want %d", got, defaultTransientRetries)
+	}
+	for _, retries := range []int{0, 4} {
+		cfg := Default()
+		cfg.PromptKit.TransientRetries = retries
+		if err := cfg.Validate(); err != nil {
+			t.Fatalf("Validate() with transient retries %d error = %v", retries, err)
+		}
+	}
+	negative := Default()
+	negative.PromptKit.TransientRetries = -1
+	assertValidationContains(t, negative, "promptkit.transient_retries must not be negative")
+}
+
 func TestValidatePromptKitLocalBackendEndpoints(t *testing.T) {
 	tests := []struct {
 		name          string

internal/core/debugbundle/summary.go

@@ -39,7 +39,7 @@ type Invocation struct {
 	InputPath               string    `json:"input_path,omitempty"`
 	ConfigPath              string    `json:"config_path,omitempty"`
 	ConfigSource            string    `json:"config_source,omitempty"`
-	ConfigProfile           string    `json:"config_profile,omitempty"`
+	ConfigOverlay           string    `json:"config_overlay,omitempty"`
 	OnlyLanes               []string  `json:"only_lanes,omitempty"`
 	ChunkCacheOverride      string    `json:"chunk_cache_override,omitempty"`
 	ReasoningEffortOverride *string   `json:"reasoning_effort_override,omitempty"`

internal/framework/contracts/contracts.go

@@ -21,15 +21,45 @@ type StructuredCompletionRequest struct {
 }
 
 type StructuredCompletionResponse struct {
-	Content          json.RawMessage   `json:"content"`
-	Provider         string            `json:"provider,omitempty"`
-	Model            string            `json:"model,omitempty"`
-	ProfileID        string            `json:"profile_id,omitempty"`
-	PromptTokens     int               `json:"prompt_tokens,omitempty"`
-	CompletionTokens int               `json:"completion_tokens,omitempty"`
-	TotalTokens      int               `json:"total_tokens,omitempty"`
-	RepairAttempts   int               `json:"repair_attempts,omitempty"`
-	Debug            *LLMDebugMaterial `json:"debug,omitempty"`
+	Content          json.RawMessage      `json:"content"`
+	Provider         string               `json:"provider,omitempty"`
+	Model            string               `json:"model,omitempty"`
+	ProfileID        string               `json:"profile_id,omitempty"`
+	PromptTokens     int                  `json:"prompt_tokens,omitempty"`
+	CompletionTokens int                  `json:"completion_tokens,omitempty"`
+	TotalTokens      int                  `json:"total_tokens,omitempty"`
+	RepairAttempts   int                  `json:"repair_attempts,omitempty"`
+	Debug            *LLMDebugMaterial    `json:"debug,omitempty"`
+	Execution        *LLMExecutionSummary `json:"execution,omitempty"`
+}
+
+type LLMObservedTokenCount struct {
+	Value    int  `json:"value"`
+	Known    bool `json:"known"`
+	Complete bool `json:"complete"`
+}
+
+type LLMObservedTokenUsage struct {
+	PromptTokens     LLMObservedTokenCount `json:"prompt_tokens"`
+	CompletionTokens LLMObservedTokenCount `json:"completion_tokens"`
+	TotalTokens      LLMObservedTokenCount `json:"total_tokens"`
+	CachedTokens     LLMObservedTokenCount `json:"cached_tokens"`
+	CacheWriteTokens LLMObservedTokenCount `json:"cache_write_tokens"`
+}
+
+type LLMExecutionSummary struct {
+	Attempts         uint64                `json:"attempts"`
+	TransientRetries uint64                `json:"transient_retries"`
+	RepairCalls      uint64                `json:"repair_calls"`
+	CapacityWaitMS   int64                 `json:"capacity_wait_ms"`
+	GenerationMS     int64                 `json:"generation_ms"`
+	RetryDelayMS     int64                 `json:"retry_delay_ms"`
+	DurationMS       int64                 `json:"duration_ms"`
+	Outcome          string                `json:"outcome"`
+	FailureKind      string                `json:"failure_kind"`
+	StatusCode       int                   `json:"status_code"`
+	RetriesExhausted bool                  `json:"retries_exhausted"`
+	Usage            LLMObservedTokenUsage `json:"usage"`
 }
 
 type StructuredLLMClient interface {

internal/framework/contracts/errors.go

@@ -13,16 +13,42 @@ var ErrLLMCapacityExceeded = errors.New("LLM capacity exceeded")
 // ErrLLMGeneration identifies a provider generation failure.
 var ErrLLMGeneration = errors.New("LLM generation failed")
 
+type LLMGenerationFailureKind string
+
+const (
+	LLMGenerationFailureGeneration        LLMGenerationFailureKind = "generation"
+	LLMGenerationFailureTransport         LLMGenerationFailureKind = "transport"
+	LLMGenerationFailureProviderStatus    LLMGenerationFailureKind = "provider_status"
+	LLMGenerationFailureMalformedResponse LLMGenerationFailureKind = "malformed_response"
+)
+
+type LLMGenerationMetadata struct {
+	FailureKind      LLMGenerationFailureKind
+	RetriesExhausted bool
+	Attempts         uint64
+}
+
 type LLMGenerationError struct {
-	status     int
-	diagnostic string
+	status      int
+	diagnostic  string
+	failureKind LLMGenerationFailureKind
+	exhausted   bool
+	attempts    uint64
 }
 
 func NewLLMGenerationError(status int, diagnostic string) *LLMGenerationError {
+	return NewLLMGenerationErrorWithMetadata(status, diagnostic, LLMGenerationMetadata{})
+}
+
+func NewLLMGenerationErrorWithMetadata(status int, diagnostic string, metadata LLMGenerationMetadata) *LLMGenerationError {
 	if status < 0 {
 		status = 0
 	}
-	return &LLMGenerationError{status: status, diagnostic: diagnostic}
+	kind := metadata.FailureKind
+	if kind == "" {
+		kind = LLMGenerationFailureGeneration
+	}
+	return &LLMGenerationError{status: status, diagnostic: diagnostic, failureKind: kind, exhausted: metadata.RetriesExhausted, attempts: metadata.Attempts}
 }
 func (e *LLMGenerationError) Error() string {
 	if e == nil || e.diagnostic == "" {
@@ -37,3 +63,21 @@ func (e *LLMGenerationError) StatusCode() int {
 	}
 	return e.status
 }
+
+func (e *LLMGenerationError) FailureKind() LLMGenerationFailureKind {
+	if e == nil || e.failureKind == "" {
+		return LLMGenerationFailureGeneration
+	}
+	return e.failureKind
+}
+
+func (e *LLMGenerationError) RetriesExhausted() bool {
+	return e != nil && e.exhausted
+}
+
+func (e *LLMGenerationError) Attempts() uint64 {
+	if e == nil {
+		return 0
+	}
+	return e.attempts
+}

internal/framework/contracts/errors_test.go

@@ -0,0 +1,22 @@
+package contracts
+
+import (
+	"errors"
+	"testing"
+)
+
+func TestLLMGenerationErrorPreservesApplicationMetadata(t *testing.T) {
+	legacy := NewLLMGenerationError(503, "provider failure")
+	if !errors.Is(legacy, ErrLLMGeneration) || legacy.StatusCode() != 503 || legacy.FailureKind() != LLMGenerationFailureGeneration || legacy.RetriesExhausted() || legacy.Attempts() != 0 {
+		t.Fatalf("legacy generation error = %#v", legacy)
+	}
+
+	err := NewLLMGenerationErrorWithMetadata(429, "provider failure", LLMGenerationMetadata{
+		FailureKind:      LLMGenerationFailureProviderStatus,
+		RetriesExhausted: true,
+		Attempts:         3,
+	})
+	if !errors.Is(err, ErrLLMGeneration) || err.StatusCode() != 429 || err.FailureKind() != LLMGenerationFailureProviderStatus || !err.RetriesExhausted() || err.Attempts() != 3 {
+		t.Fatalf("generation error = %#v", err)
+	}
+}

internal/framework/llm/promptkit_client.go

@@ -26,15 +26,16 @@ type PromptKitLocalBackendConfig struct {
 }
 
 type PromptKitClientConfig struct {
-	ProfileDir      string
-	ProfileFile     string
-	LocalBackend    *PromptKitLocalBackendConfig
-	Assets          *AssetRegistry
-	Timeout         time.Duration
-	HTTPClient      *http.Client
-	EngineOptions   []promptkit.Option
-	Recorder        *LLMProfileRecorder
-	ReasoningEffort *string
+	ProfileDir       string
+	ProfileFile      string
+	TransientRetries *int
+	LocalBackend     *PromptKitLocalBackendConfig
+	Assets           *AssetRegistry
+	Timeout          time.Duration
+	HTTPClient       *http.Client
+	EngineOptions    []promptkit.Option
+	Recorder         *LLMProfileRecorder
+	ReasoningEffort  *string
 }
 
 type PromptKitClient struct {
@@ -79,9 +80,10 @@ func NewPromptKitClient(cfg PromptKitClientConfig) (*PromptKitClient, error) {
 	options = append(options, cfg.EngineOptions...)
 
 	engine, err := promptkit.NewEngine(promptkit.Config{
-		ProfileDir: profileSource.ProfileDir,
-		Timeout:    cfg.Timeout,
-		HTTPClient: cfg.HTTPClient,
+		ProfileDir:       profileSource.ProfileDir,
+		Timeout:          cfg.Timeout,
+		HTTPClient:       cfg.HTTPClient,
+		TransientRetries: cfg.TransientRetries,
 	}, options...)
 	if err != nil {
 		return nil, fmt.Errorf("create PromptKit engine: %w", err)
@@ -128,10 +130,10 @@ func (c *PromptKitClient) CompleteStructured(ctx context.Context, req contracts.
 		return contracts.StructuredCompletionResponse{}, fmt.Errorf("structured completion prompt_id must not be empty")
 	}
 	sessionID := strings.TrimSpace(req.SessionID)
-	var execution *promptkit.ExecutionTargetOverride
+	var targetOverride *promptkit.ExecutionTargetOverride
 	if c.reasoningEffort != nil {
 		reasoningEffort := *c.reasoningEffort
-		execution = &promptkit.ExecutionTargetOverride{
+		targetOverride = &promptkit.ExecutionTargetOverride{
 			ReasoningEffort: &reasoningEffort,
 		}
 	}
@@ -143,9 +145,15 @@ func (c *PromptKitClient) CompleteStructured(ctx context.Context, req contracts.
 		SessionID:        sessionID,
 		Inputs:           promptKitInputs(req.Inputs),
 		Vars:             promptKitVars(req, sessionID),
-		Execution:        execution,
+		Execution:        targetOverride,
 		AppendedMessages: appendedMessages,
 	}
+	var executionSummary *contracts.LLMExecutionSummary
+	runReq.Observer = func(event promptkit.ExecutionEvent) {
+		if event.Kind == promptkit.ExecutionFinished {
+			executionSummary = promptKitExecutionSummary(event)
+		}
+	}
 	if req.StructuredOutputRepairAttempts != nil {
 		inspection, err := c.engine.InspectPrompt(ctx, promptID, strings.TrimSpace(req.PromptVersion))
 		if err != nil {
@@ -170,12 +178,12 @@ func (c *PromptKitClient) CompleteStructured(ctx context.Context, req contracts.
 	result, err := c.engine.RunPrepared(ctx, prepared)
 	if err != nil {
 		if ctxErr := ctx.Err(); ctxErr != nil {
-			return contracts.StructuredCompletionResponse{}, ctxErr
+			return promptKitResponseWithExecution(contracts.StructuredCompletionResponse{}, executionSummary), ctxErr
 		}
 		if errors.Is(err, promptkit.ErrCapacityExceeded) {
 			var capacityErr *promptkit.CapacityError
 			if errors.As(err, &capacityErr) && strings.TrimSpace(capacityErr.BackendID) != "" {
-				return contracts.StructuredCompletionResponse{}, fmt.Errorf(
+				return promptKitResponseWithExecution(contracts.StructuredCompletionResponse{}, executionSummary), fmt.Errorf(
 					"run PromptKit prompt %q on backend %q: %w: %v",
 					promptID,
 					strings.TrimSpace(capacityErr.BackendID),
@@ -183,7 +191,7 @@ func (c *PromptKitClient) CompleteStructured(ctx context.Context, req contracts.
 					redactPromptKitError(err),
 				)
 			}
-			return contracts.StructuredCompletionResponse{}, fmt.Errorf(
+			return promptKitResponseWithExecution(contracts.StructuredCompletionResponse{}, executionSummary), fmt.Errorf(
 				"run PromptKit prompt %q: %w: %v",
 				promptID,
 				contracts.ErrLLMCapacityExceeded,
@@ -192,20 +200,26 @@ func (c *PromptKitClient) CompleteStructured(ctx context.Context, req contracts.
 		}
 		if errors.Is(err, promptkit.ErrLLMGenerate) {
 			var generationErr *promptkit.GenerationError
+			var exhaustedErr *promptkit.RetryExhaustedError
 			status := 0
+			metadata := contracts.LLMGenerationMetadata{FailureKind: promptKitGenerationFailureKind(err)}
+			if errors.As(err, &exhaustedErr) {
+				metadata.RetriesExhausted = true
+				metadata.Attempts = exhaustedErr.Attempts()
+			}
 			response := contracts.StructuredCompletionResponse{Debug: &contracts.LLMDebugMaterial{Prompt: promptKitDebugPrompt(&preparedDetails)}}
 			if errors.As(err, &generationErr) {
 				status = generationErr.StatusCode()
 				response.Debug.Response = promptKitDebugGenerationError(&preparedDetails, generationErr)
 			}
-			return response, contracts.NewLLMGenerationError(status, fmt.Sprintf("run PromptKit prompt %q: %v", promptID, redactPromptKitError(err)))
+			return promptKitResponseWithExecution(response, executionSummary), contracts.NewLLMGenerationErrorWithMetadata(status, fmt.Sprintf("run PromptKit prompt %q: %v", promptID, redactPromptKitError(err)), metadata)
 		}
-		return contracts.StructuredCompletionResponse{}, fmt.Errorf("run PromptKit prompt %q: %v", promptID, redactPromptKitError(err))
+		return promptKitResponseWithExecution(contracts.StructuredCompletionResponse{}, executionSummary), fmt.Errorf("run PromptKit prompt %q: %v", promptID, redactPromptKitError(err))
 	}
 	if result == nil {
-		return contracts.StructuredCompletionResponse{}, fmt.Errorf("run PromptKit prompt %q: %w: empty result", promptID, contracts.ErrInvalidStructuredOutput)
+		return promptKitResponseWithExecution(contracts.StructuredCompletionResponse{}, executionSummary), fmt.Errorf("run PromptKit prompt %q: %w: empty result", promptID, contracts.ErrInvalidStructuredOutput)
 	}
-	response := c.responseFromResult(result, &preparedDetails)
+	response := promptKitResponseWithExecution(c.responseFromResult(result, &preparedDetails), executionSummary)
 	if result.Validation.Status == promptkit.ValidationFailed || !result.Validation.IsValid {
 		return response, fmt.Errorf("run PromptKit prompt %q: %w: validation failed: %s", promptID, contracts.ErrInvalidStructuredOutput, strings.Join(result.Validation.Errors, "; "))
 	}
@@ -218,6 +232,61 @@ func (c *PromptKitClient) CompleteStructured(ctx context.Context, req contracts.
 	return response, nil
 }
 
+func promptKitResponseWithExecution(response contracts.StructuredCompletionResponse, execution *contracts.LLMExecutionSummary) contracts.StructuredCompletionResponse {
+	response.Execution = execution
+	return response
+}
+
+func promptKitExecutionSummary(event promptkit.ExecutionEvent) *contracts.LLMExecutionSummary {
+	count := func(value promptkit.ObservedTokenCount) contracts.LLMObservedTokenCount {
+		return contracts.LLMObservedTokenCount{Value: value.Value, Known: value.Known, Complete: value.Complete}
+	}
+	return &contracts.LLMExecutionSummary{
+		Attempts: event.Attempts, TransientRetries: event.TransientRetries, RepairCalls: event.RepairCalls,
+		CapacityWaitMS: event.CapacityWait.Milliseconds(), GenerationMS: event.GenerationDuration.Milliseconds(), RetryDelayMS: event.RetryDelay.Milliseconds(), DurationMS: event.Duration.Milliseconds(),
+		Outcome: promptKitExecutionOutcome(event.Outcome), FailureKind: promptKitExecutionFailure(event.Failure), StatusCode: event.StatusCode, RetriesExhausted: event.RetriesExhausted,
+		Usage: contracts.LLMObservedTokenUsage{PromptTokens: count(event.Usage.PromptTokens), CompletionTokens: count(event.Usage.CompletionTokens), TotalTokens: count(event.Usage.TotalTokens), CachedTokens: count(event.Usage.CachedTokens), CacheWriteTokens: count(event.Usage.CacheWriteTokens)},
+	}
+}
+
+func promptKitExecutionOutcome(value promptkit.ExecutionOutcome) string {
+	switch value {
+	case promptkit.ExecutionOutcomeSuccess:
+		return "success"
+	case promptkit.ExecutionOutcomeInvalidOutput:
+		return "invalid_output"
+	case promptkit.ExecutionOutcomeError:
+		return "error"
+	default:
+		return "other"
+	}
+}
+
+func promptKitExecutionFailure(value promptkit.ExecutionFailureKind) string {
+	switch value {
+	case promptkit.ExecutionFailureNone:
+		return ""
+	case promptkit.ExecutionFailureCanceled, promptkit.ExecutionFailureDeadline, promptkit.ExecutionFailureTransport, promptkit.ExecutionFailureProviderStatus, promptkit.ExecutionFailureMalformedResponse, promptkit.ExecutionFailureCapacity, promptkit.ExecutionFailureInvalidConfig, promptkit.ExecutionFailureInvalidRequest, promptkit.ExecutionFailurePromptNotFound, promptkit.ExecutionFailureProfileNotFound, promptkit.ExecutionFailurePromptLoad, promptkit.ExecutionFailureProfileLoad, promptkit.ExecutionFailureArtifactLoad, promptkit.ExecutionFailurePromptRender, promptkit.ExecutionFailureValidation, promptkit.ExecutionFailureGeneration:
+		return string(value)
+	default:
+		return "other"
+	}
+}
+
+func promptKitGenerationFailureKind(err error) contracts.LLMGenerationFailureKind {
+	switch {
+	case errors.Is(err, promptkit.ErrTransport):
+		return contracts.LLMGenerationFailureTransport
+	case errors.Is(err, promptkit.ErrMalformedResponse):
+		return contracts.LLMGenerationFailureMalformedResponse
+	}
+	var generationErr *promptkit.GenerationError
+	if errors.As(err, &generationErr) && generationErr.StatusCode() != 0 {
+		return contracts.LLMGenerationFailureProviderStatus
+	}
+	return contracts.LLMGenerationFailureGeneration
+}
+
 func promptKitCorrectionMessages(correction *contracts.SemanticCorrection) ([]promptkit.RenderedMessage, error) {
 	owned, err := contracts.CloneSemanticCorrection(correction)
 	if err != nil {

internal/framework/llm/promptkit_client_test.go

@@ -55,6 +55,10 @@ func TestPromptKitClientMapsPromptRequestAndUnmarshalsOutput(t *testing.T) {
 	if resp.PromptTokens != 11 || resp.CompletionTokens != 7 || resp.TotalTokens != 18 {
 		t.Fatalf("usage = %#v, want mapped token counts", resp)
 	}
+	if resp.Execution == nil || resp.Execution.Outcome != "success" || resp.Execution.Attempts != 1 ||
+		!resp.Execution.Usage.PromptTokens.Known || resp.Execution.Usage.PromptTokens.Value != 11 {
+		t.Fatalf("execution summary = %#v", resp.Execution)
+	}
 	if resp.Debug == nil || resp.Debug.Prompt == nil {
 		t.Fatalf("debug prompt = nil, want prepared prompt material")
 	}
@@ -971,6 +975,83 @@ model: local-model
 	}
 }
 
+func TestPromptKitClientAppliesConfiguredBuiltInTransientRetries(t *testing.T) {
+	for _, test := range []struct {
+		name      string
+		retries   int
+		statuses  []int
+		wantCalls int32
+		wantErr   bool
+	}{
+		{name: "eligible failure then success", retries: 1, statuses: []int{http.StatusServiceUnavailable, http.StatusOK}, wantCalls: 2},
+		{name: "disabled", retries: 0, statuses: []int{http.StatusServiceUnavailable}, wantCalls: 1, wantErr: true},
+		{name: "exhausted", retries: 1, statuses: []int{http.StatusServiceUnavailable, http.StatusServiceUnavailable}, wantCalls: 2, wantErr: true},
+		{name: "noneligible client error", retries: 2, statuses: []int{http.StatusBadRequest}, wantCalls: 1, wantErr: true},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			var calls atomic.Int32
+			server := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
+				index := calls.Add(1) - 1
+				if int(index) >= len(test.statuses) {
+					t.Errorf("unexpected HTTP attempt %d", index+1)
+					w.WriteHeader(http.StatusInternalServerError)
+					return
+				}
+				status := test.statuses[index]
+				w.Header().Set("Content-Type", "application/json")
+				if status != http.StatusOK {
+					w.WriteHeader(status)
+					_, _ = w.Write([]byte(`{"error":{"message":"provider failure"}}`))
+					return
+				}
+				_, _ = w.Write([]byte(`{"choices":[{"message":{"content":"{\"ok\":true}"}}]}`))
+			}))
+			defer server.Close()
+
+			profilePath := filepath.Join(t.TempDir(), "profile.yml")
+			if err := os.WriteFile(profilePath, []byte("id: retry-profile\nendpoint: "+server.URL+"/v1\nmodel: retry-model\n"), 0o600); err != nil {
+				t.Fatal(err)
+			}
+			client, err := NewPromptKitClient(PromptKitClientConfig{
+				Assets:           newTestPromptKitAssets(t),
+				ProfileFile:      profilePath,
+				TransientRetries: &test.retries,
+			})
+			if err != nil {
+				t.Fatal(err)
+			}
+			var out map[string]any
+			_, err = client.CompleteStructured(context.Background(), contracts.StructuredCompletionRequest{
+				PromptID:  "adapter.test",
+				ProfileID: "retry-profile",
+				SessionID: "retry-test",
+				Inputs: contracts.LLMInputSet{
+					"transcript": contracts.NewLLMInputMaterial("transcript", "application/json", []byte(`{"source":true}`), "", ""),
+				},
+			}, &out)
+			if (err != nil) != test.wantErr {
+				t.Fatalf("CompleteStructured() error = %v, want error=%t", err, test.wantErr)
+			}
+			if test.wantErr {
+				var generation *contracts.LLMGenerationError
+				if !errors.As(err, &generation) || generation.FailureKind() != contracts.LLMGenerationFailureProviderStatus {
+					t.Fatalf("generation error = %#v, want provider-status classification", generation)
+				}
+				wantExhausted := test.name == "exhausted"
+				if generation.RetriesExhausted() != wantExhausted {
+					t.Fatalf("retries exhausted = %t, want %t", generation.RetriesExhausted(), wantExhausted)
+				}
+				if wantExhausted && (generation.Attempts() != 2 || generation.StatusCode() != http.StatusServiceUnavailable) {
+					t.Fatalf("exhausted generation = %#v", generation)
+				}
+			}
+			if got := calls.Load(); got != test.wantCalls {
+				t.Fatalf("HTTP calls = %d, want %d", got, test.wantCalls)
+			}
+		})
+	}
+}
+
 func TestLLMProfileRecorderDistinguishesEffectiveTargets(t *testing.T) {
 	recorder := NewLLMProfileRecorder()
 	for _, profile := range []artifacts.LLMProfileManifest{
@@ -1309,6 +1390,51 @@ func TestPromptKitClientForwardsConfiguredTransportTimeout(t *testing.T) {
 	}
 }
 
+func TestPromptKitClientClassifiesBuiltInTransportAndMalformedResponses(t *testing.T) {
+	for _, test := range []struct {
+		name      string
+		kind      contracts.LLMGenerationFailureKind
+		roundTrip func(*http.Request) (*http.Response, error)
+	}{
+		{
+			name: "transport",
+			kind: contracts.LLMGenerationFailureTransport,
+			roundTrip: func(*http.Request) (*http.Response, error) {
+				return nil, errors.New("transport unavailable")
+			},
+		},
+		{
+			name: "malformed response",
+			kind: contracts.LLMGenerationFailureMalformedResponse,
+			roundTrip: func(request *http.Request) (*http.Response, error) {
+				return &http.Response{StatusCode: http.StatusOK, Header: make(http.Header), Body: io.NopCloser(strings.NewReader("not-json")), Request: request}, nil
+			},
+		},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			client, err := NewPromptKitClient(PromptKitClientConfig{
+				Assets:     newTestPromptKitAssets(t),
+				HTTPClient: &http.Client{Transport: roundTripFunc(test.roundTrip)},
+				EngineOptions: []promptkit.Option{promptkit.WithProfiles(promptkit.OpenAICompatibleProfile(promptkit.OpenAICompatibleProfileConfig{
+					ID: "default-profile", Endpoint: "http://promptkit.test/v1", Model: "default-model",
+				}))},
+			})
+			if err != nil {
+				t.Fatal(err)
+			}
+			var out map[string]any
+			_, err = client.CompleteStructured(context.Background(), contracts.StructuredCompletionRequest{
+				PromptID: "adapter.test", SessionID: "failure-kind-test",
+				Inputs: contracts.LLMInputSet{"transcript": contracts.NewLLMInputMaterial("transcript", "application/json", []byte(`{"source":true}`), "", "")},
+			}, &out)
+			var generation *contracts.LLMGenerationError
+			if !errors.As(err, &generation) || generation.FailureKind() != test.kind || generation.RetriesExhausted() || generation.Attempts() != 0 {
+				t.Fatalf("generation error = %#v, want kind %q", generation, test.kind)
+			}
+		})
+	}
+}
+
 func TestPromptKitClientClassifiesEmptyStructuredCompletion(t *testing.T) {
 	client := newTestPromptKitClient(t, &fakePromptKitLLM{allowEmpty: true})
 

internal/framework/llm/promptkit_observation_test.go

@@ -0,0 +1,245 @@
+package llm
+
+import (
+	"context"
+	"encoding/json"
+	"errors"
+	"io"
+	"net/http"
+	"net/http/httptest"
+	"strings"
+	"sync/atomic"
+	"testing"
+	"time"
+
+	"gitea.maximumdirect.net/eric/notarius/internal/framework/contracts"
+	"gitea.maximumdirect.net/eric/promptkit"
+)
+
+func newObservedHTTPClient(t *testing.T, handler http.HandlerFunc, retries int, transport http.RoundTripper) *PromptKitClient {
+	t.Helper()
+	server := httptest.NewServer(handler)
+	t.Cleanup(server.Close)
+	client, err := NewPromptKitClient(PromptKitClientConfig{
+		Assets: newTestPromptKitAssets(t), TransientRetries: &retries,
+		HTTPClient: &http.Client{Transport: transport},
+		EngineOptions: []promptkit.Option{promptkit.WithProfiles(promptkit.OpenAICompatibleProfile(promptkit.OpenAICompatibleProfileConfig{
+			ID: "default-profile", Endpoint: server.URL + "/v1", Model: "test-model",
+		}))},
+	})
+	if err != nil {
+		t.Fatal(err)
+	}
+	return client
+}
+
+func observedRequest() contracts.StructuredCompletionRequest {
+	return contracts.StructuredCompletionRequest{
+		PromptID: "adapter.test", SessionID: "observation-test",
+		Inputs: contracts.LLMInputSet{"transcript": contracts.NewLLMInputMaterial("transcript", "application/json", []byte(`{}`), "", "")},
+	}
+}
+
+func TestPromptKitObservationsComposeTransientRetriesAndRepair(t *testing.T) {
+	var calls atomic.Int32
+	client := newObservedHTTPClient(t, func(w http.ResponseWriter, r *http.Request) {
+		w.Header().Set("Content-Type", "application/json")
+		switch calls.Add(1) {
+		case 1, 3:
+			w.WriteHeader(http.StatusServiceUnavailable)
+			_, _ = io.WriteString(w, `{"error":{"message":"try again"}}`)
+		case 2:
+			_, _ = io.WriteString(w, `{"choices":[{"message":{"content":"{\"bad\":true}"}}],"usage":{"prompt_tokens":3,"completion_tokens":2,"total_tokens":5,"prompt_tokens_details":{"cached_tokens":0}}}`)
+		case 4:
+			_, _ = io.WriteString(w, `{"choices":[{"message":{"content":"{\"ok\":true}"}}],"usage":{"prompt_tokens":7,"completion_tokens":0,"total_tokens":7}}`)
+		default:
+			t.Error("unexpected extra HTTP attempt")
+			w.WriteHeader(http.StatusBadRequest)
+		}
+	}, 1, nil)
+	ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second)
+	defer cancel()
+	req := observedRequest()
+	repairs := 1
+	req.StructuredOutputRepairAttempts = &repairs
+	var out struct{ OK bool }
+	response, err := client.CompleteStructured(ctx, req, &out)
+	if err != nil || !out.OK {
+		t.Fatalf("completion = (%+v, %v), output = %+v", response, err, out)
+	}
+	summary := response.Execution
+	if calls.Load() != 4 || summary == nil || summary.Attempts != 4 || summary.TransientRetries != 2 || summary.RepairCalls != 1 || summary.Outcome != "success" || summary.RetriesExhausted {
+		t.Fatalf("calls = %d, execution = %+v", calls.Load(), summary)
+	}
+	wantUsage := contracts.LLMObservedTokenUsage{
+		PromptTokens:     contracts.LLMObservedTokenCount{Value: 10, Known: true},
+		CompletionTokens: contracts.LLMObservedTokenCount{Value: 2, Known: true},
+		TotalTokens:      contracts.LLMObservedTokenCount{Value: 12, Known: true},
+		CachedTokens:     contracts.LLMObservedTokenCount{Known: true},
+	}
+	// Failed HTTP attempts contribute unknown usage, not known zero. Neither
+	// terminal totals nor legacy result totals should be added a second time.
+	if summary.Usage != wantUsage {
+		t.Fatalf("observed usage = %+v, want %+v", summary.Usage, wantUsage)
+	}
+	if response.PromptTokens != 10 || response.CompletionTokens != 2 || response.TotalTokens != 12 || response.RepairAttempts != 1 {
+		t.Fatalf("legacy result accounting changed: %+v", response)
+	}
+}
+
+type closeSignalingBody struct {
+	io.ReadCloser
+	closed chan<- struct{}
+}
+
+func (b closeSignalingBody) Close() error {
+	err := b.ReadCloser.Close()
+	b.closed <- struct{}{}
+	return err
+}
+
+func TestPromptKitObservationSurvivesCanceledRetryWait(t *testing.T) {
+	consumed := make(chan struct{}, 2)
+	transport := http.DefaultTransport.(*http.Transport).Clone()
+	t.Cleanup(transport.CloseIdleConnections)
+	var calls atomic.Int32
+	client := newObservedHTTPClient(t, func(w http.ResponseWriter, r *http.Request) {
+		calls.Add(1)
+		w.Header().Set("Retry-After", "3600")
+		w.WriteHeader(http.StatusServiceUnavailable)
+		_, _ = io.WriteString(w, `{"error":{"message":"busy"}}`)
+	}, 1, roundTripFunc(func(req *http.Request) (*http.Response, error) {
+		response, err := transport.RoundTrip(req)
+		if err == nil {
+			response.Body = closeSignalingBody{ReadCloser: response.Body, closed: consumed}
+		}
+		return response, err
+	}))
+	ctx, cancel := context.WithCancel(context.Background())
+	defer cancel()
+	type result struct {
+		response contracts.StructuredCompletionResponse
+		err      error
+	}
+	done := make(chan result, 1)
+	go func() {
+		var out map[string]any
+		response, err := client.CompleteStructured(ctx, observedRequest(), &out)
+		done <- result{response, err}
+	}()
+	// The failure has been consumed, so cancellation must interrupt the pending
+	// retry wait rather than depend on another provider response or its timeout.
+	select {
+	case <-consumed:
+	case <-time.After(5 * time.Second):
+		t.Fatal("provider response was not consumed")
+	}
+	cancel()
+	select {
+	case got := <-done:
+		if !errors.Is(got.err, context.Canceled) || got.response.Execution == nil {
+			t.Fatalf("canceled completion = (%+v, %v)", got.response, got.err)
+		}
+		summary := got.response.Execution
+		if summary.Outcome != "error" || summary.FailureKind != "canceled" || summary.Attempts != 1 || summary.RetriesExhausted || calls.Load() != 1 {
+			t.Fatalf("canceled execution = %+v, HTTP calls = %d", summary, calls.Load())
+		}
+	case <-time.After(5 * time.Second):
+		t.Fatal("cancellation did not interrupt retry waiting")
+	}
+}
+
+func TestPromptKitObservationsSeparatePreparationAndExecutionFailure(t *testing.T) {
+	var calls atomic.Int32
+	client := newObservedHTTPClient(t, func(w http.ResponseWriter, r *http.Request) {
+		calls.Add(1)
+		w.WriteHeader(http.StatusServiceUnavailable)
+		_, _ = io.WriteString(w, `{"error":{"message":"busy"}}`)
+	}, 1, nil)
+	ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second)
+	defer cancel()
+	req := observedRequest()
+	req.PromptID = "missing-prompt"
+	var out map[string]any
+	response, err := client.CompleteStructured(ctx, req, &out)
+	if err == nil || response.Execution != nil || calls.Load() != 0 {
+		t.Fatalf("preparation failure = (%+v, %v), calls = %d", response, err, calls.Load())
+	}
+	response, err = client.CompleteStructured(ctx, observedRequest(), &out)
+	var generation *contracts.LLMGenerationError
+	if !errors.As(err, &generation) || response.Execution == nil {
+		t.Fatalf("execution failure = (%+v, %v)", response, err)
+	}
+	summary := response.Execution
+	if summary.Outcome != "error" || summary.FailureKind != "provider_status" || summary.StatusCode != http.StatusServiceUnavailable || !summary.RetriesExhausted || summary.Attempts != 2 || summary.TransientRetries != 1 || calls.Load() != 2 {
+		t.Fatalf("failed execution = %+v, calls = %d", summary, calls.Load())
+	}
+	if summary.Usage != (contracts.LLMObservedTokenUsage{}) {
+		t.Fatalf("failed attempts should have unknown usage: %+v", summary.Usage)
+	}
+}
+
+func TestPromptKitObservationsAreIsolatedAcrossConcurrentCalls(t *testing.T) {
+	arrived := make(chan struct{}, 2)
+	release := make(chan struct{})
+	client := newObservedHTTPClient(t, func(w http.ResponseWriter, r *http.Request) {
+		body, err := io.ReadAll(r.Body)
+		if err != nil {
+			t.Error(err)
+			return
+		}
+		tokens := 11
+		if strings.Contains(string(body), "second-call") {
+			tokens = 22
+		}
+		arrived <- struct{}{}
+		select {
+		case <-release:
+		case <-r.Context().Done():
+			return
+		}
+		_ = json.NewEncoder(w).Encode(map[string]any{
+			"choices": []any{map[string]any{"message": map[string]string{"content": `{"ok":true}`}}},
+			"usage":   map[string]int{"prompt_tokens": tokens, "completion_tokens": 0, "total_tokens": tokens},
+		})
+	}, 0, nil)
+	ctx, cancel := context.WithTimeout(context.Background(), 5*time.Second)
+	defer cancel()
+	type result struct {
+		want     int
+		response contracts.StructuredCompletionResponse
+		err      error
+	}
+	done := make(chan result, 2)
+	for name, tokens := range map[string]int{"first-call": 11, "second-call": 22} {
+		go func() {
+			req := observedRequest()
+			req.Vars = map[string]any{"custom": name}
+			var out map[string]any
+			response, err := client.CompleteStructured(ctx, req, &out)
+			done <- result{tokens, response, err}
+		}()
+	}
+	for i := 0; i < 2; i++ {
+		select {
+		case <-arrived:
+		case <-ctx.Done():
+			t.Fatal("requests did not overlap")
+		}
+	}
+	close(release)
+	for i := 0; i < 2; i++ {
+		select {
+		case got := <-done:
+			summary := got.response.Execution
+			if got.err != nil || summary == nil {
+				t.Fatalf("concurrent completion = (%+v, %v)", got.response, got.err)
+			}
+			if summary.Attempts != 1 || summary.Usage.PromptTokens != (contracts.LLMObservedTokenCount{Value: got.want, Known: true, Complete: true}) || summary.Usage.CompletionTokens != (contracts.LLMObservedTokenCount{Known: true, Complete: true}) || summary.Usage.CachedTokens != (contracts.LLMObservedTokenCount{}) {
+				t.Fatalf("execution for %d tokens = %+v", got.want, summary)
+			}
+		case <-ctx.Done():
+			t.Fatal("concurrent completions did not return")
+		}
+	}
+}

internal/framework/llm/promptkit_profile_fingerprint.go

@@ -17,7 +17,7 @@ const (
 	promptKitLocalBackendMarker          = "notarius:promptkit-local-backend:v1"
 	// The built-in profile catalog is compiled into this pinned PromptKit
 	// release. Update this identity when the dependency is upgraded.
-	promptKitBuiltinProfileCatalogID = "promptkit:v0.9.0:builtin-profiles"
+	promptKitBuiltinProfileCatalogID = "promptkit:v0.11.2:builtin-profiles"
 )
 
 func promptKitProfileFingerprint(profileDir, profileFile, fallbackProfileDigest string) (CheckpointFingerprint, error) {

internal/framework/llm/scheduled_client.go

@@ -38,7 +38,7 @@ func (c *scheduledClient) CompleteStructured(ctx context.Context, req contracts.
 		return callErr
 	})
 	if err != nil {
-		return contracts.StructuredCompletionResponse{}, err
+		return response, err
 	}
 	return response, nil
 }

internal/framework/pipeline/debug.go

@@ -113,13 +113,14 @@ type debugSerializedOutput struct {
 type debugStructuredCompletionRequest = contracts.DebugStructuredCompletionRequest
 
 type debugStructuredCompletionResponse struct {
-	Content          string `json:"content,omitempty"`
-	Provider         string `json:"provider,omitempty"`
-	Model            string `json:"model,omitempty"`
-	ProfileID        string `json:"profile_id,omitempty"`
-	PromptTokens     int    `json:"prompt_tokens,omitempty"`
-	CompletionTokens int    `json:"completion_tokens,omitempty"`
-	TotalTokens      int    `json:"total_tokens,omitempty"`
+	Content          string                         `json:"content,omitempty"`
+	Provider         string                         `json:"provider,omitempty"`
+	Model            string                         `json:"model,omitempty"`
+	ProfileID        string                         `json:"profile_id,omitempty"`
+	PromptTokens     int                            `json:"prompt_tokens,omitempty"`
+	CompletionTokens int                            `json:"completion_tokens,omitempty"`
+	TotalTokens      int                            `json:"total_tokens,omitempty"`
+	Execution        *contracts.LLMExecutionSummary `json:"execution,omitempty"`
 }
 
 type debugLLMPromptArtifact struct {
@@ -133,21 +134,23 @@ type debugLLMResponseArtifact struct {
 	Fallback    *debugStructuredCompletionResponse `json:"fallback,omitempty"`
 	ContentPath string                             `json:"content_path,omitempty"`
 	Error       string                             `json:"error,omitempty"`
+	Execution   *contracts.LLMExecutionSummary     `json:"execution,omitempty"`
 }
 
 type debugLLMCallReference struct {
-	CallID              string `json:"call_id"`
-	PromptPath          string `json:"prompt_path,omitempty"`
-	ResponsePath        string `json:"response_path"`
-	ResponseContentPath string `json:"response_content_path,omitempty"`
-	PromptID            string `json:"prompt_id,omitempty"`
-	ProfileID           string `json:"profile_id,omitempty"`
-	Model               string `json:"model,omitempty"`
-	PromptTokens        int    `json:"prompt_tokens,omitempty"`
-	CompletionTokens    int    `json:"completion_tokens,omitempty"`
-	TotalTokens         int    `json:"total_tokens,omitempty"`
-	RepairAttempts      int    `json:"repair_attempts,omitempty"`
-	Error               bool   `json:"error,omitempty"`
+	CallID              string                         `json:"call_id"`
+	PromptPath          string                         `json:"prompt_path,omitempty"`
+	ResponsePath        string                         `json:"response_path"`
+	ResponseContentPath string                         `json:"response_content_path,omitempty"`
+	PromptID            string                         `json:"prompt_id,omitempty"`
+	ProfileID           string                         `json:"profile_id,omitempty"`
+	Model               string                         `json:"model,omitempty"`
+	PromptTokens        int                            `json:"prompt_tokens,omitempty"`
+	CompletionTokens    int                            `json:"completion_tokens,omitempty"`
+	TotalTokens         int                            `json:"total_tokens,omitempty"`
+	RepairAttempts      int                            `json:"repair_attempts,omitempty"`
+	Error               bool                           `json:"error,omitempty"`
+	Execution           *contracts.LLMExecutionSummary `json:"execution,omitempty"`
 }
 
 type debugValidationOutcome struct {
@@ -267,6 +270,7 @@ func (client *debugLLMClient) CompleteStructured(ctx context.Context, req contra
 			Fallback:    fallbackForArtifact,
 			ContentPath: responseContentPath,
 			Error:       errorText,
+			Execution:   cloneLLMExecutionSummary(response.Execution),
 		},
 		Error: errorText,
 	}))
@@ -283,6 +287,7 @@ func (client *debugLLMClient) CompleteStructured(ctx context.Context, req contra
 		TotalTokens:         response.TotalTokens,
 		RepairAttempts:      response.RepairAttempts,
 		Error:               err != nil,
+		Execution:           cloneLLMExecutionSummary(response.Execution),
 	}
 	if scope := debugLLMScopeFromContext(ctx); scope != nil {
 		scope.record(callRef)
@@ -637,6 +642,7 @@ func debugCompletionResponse(response contracts.StructuredCompletionResponse) de
 		PromptTokens:     response.PromptTokens,
 		CompletionTokens: response.CompletionTokens,
 		TotalTokens:      response.TotalTokens,
+		Execution:        cloneLLMExecutionSummary(response.Execution),
 	}
 }
 
@@ -651,7 +657,8 @@ func debugCompletionFallback(response contracts.StructuredCompletionResponse) *d
 		fallback.ProfileID == "" &&
 		fallback.PromptTokens == 0 &&
 		fallback.CompletionTokens == 0 &&
-		fallback.TotalTokens == 0 {
+		fallback.TotalTokens == 0 &&
+		fallback.Execution == nil {
 		return nil
 	}
 	return &fallback
@@ -696,6 +703,15 @@ func cloneDebugFallbackWithoutContent(fallback *debugStructuredCompletionRespons
 	}
 	clone := *fallback
 	clone.Content = ""
+	clone.Execution = cloneLLMExecutionSummary(fallback.Execution)
+	return &clone
+}
+
+func cloneLLMExecutionSummary(summary *contracts.LLMExecutionSummary) *contracts.LLMExecutionSummary {
+	if summary == nil {
+		return nil
+	}
+	clone := *summary
 	return &clone
 }
 

internal/framework/pipeline/debug_execution_test.go

@@ -0,0 +1,122 @@
+package pipeline
+
+import (
+	"bytes"
+	"context"
+	"encoding/json"
+	"errors"
+	"testing"
+
+	"gitea.maximumdirect.net/eric/notarius/internal/framework/contracts"
+	"gitea.maximumdirect.net/eric/notarius/internal/framework/llm"
+)
+
+type executionDebugClient struct {
+	response contracts.StructuredCompletionResponse
+	err      error
+}
+
+func (c executionDebugClient) CompleteStructured(context.Context, contracts.StructuredCompletionRequest, any) (contracts.StructuredCompletionResponse, error) {
+	return c.response, c.err
+}
+
+func TestScheduledDebugClientPreservesExecutionThroughTerminalRecords(t *testing.T) {
+	providerErr := contracts.NewLLMGenerationError(503, "provider unavailable")
+	const content = `{"ok":true}`
+	for _, test := range []struct {
+		name          string
+		err           error
+		content       string
+		debugResponse bool
+	}{
+		{name: "provider failure without body", err: providerErr},
+		{name: "canceled without body", err: context.Canceled},
+		{name: "split debug response", content: content, debugResponse: true},
+		{name: "split fallback response", content: content},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			want := contracts.LLMExecutionSummary{
+				Attempts: 2, TransientRetries: 1, Outcome: "success",
+				CapacityWaitMS: 1, GenerationMS: 3, RetryDelayMS: 5, DurationMS: 9,
+				Usage: contracts.LLMObservedTokenUsage{
+					PromptTokens:     contracts.LLMObservedTokenCount{Value: 7, Known: true},
+					CompletionTokens: contracts.LLMObservedTokenCount{Known: true},
+				},
+			}
+			if test.err != nil {
+				want.Outcome = "error"
+				want.FailureKind = "provider_status"
+				want.StatusCode = 503
+				want.RetriesExhausted = true
+				if errors.Is(test.err, context.Canceled) {
+					want.FailureKind = "canceled"
+					want.StatusCode = 0
+					want.RetriesExhausted = false
+				}
+			}
+			execution := want
+			response := contracts.StructuredCompletionResponse{Execution: &execution}
+			if test.debugResponse {
+				response.Debug = &contracts.LLMDebugMaterial{Response: &contracts.LLMDebugResponse{Content: test.content}}
+			} else {
+				response.Content = json.RawMessage(test.content)
+			}
+			scheduler, err := llm.NewScheduler(1)
+			if err != nil {
+				t.Fatal(err)
+			}
+			recorder := newCapturedDebugRecorder()
+			client := WithDebugLLMRecording(llm.NewScheduledClient(executionDebugClient{response, test.err}, scheduler), recorder)
+			ctx, scope := withDebugLLMScope(context.Background(), "attempt")
+			got, err := client.CompleteStructured(ctx, contracts.StructuredCompletionRequest{StageName: "extract"}, &struct{}{})
+			if !errors.Is(err, test.err) || got.Execution == nil || *got.Execution != want {
+				t.Fatalf("scheduled debug completion = (%+v, %v), want summary and original error", got, err)
+			}
+			terminal := newAttemptTerminalRecorder(recorder, "attempt/terminal", "extract", scope, debugTimedEnvelope{Stage: "extract"})
+			if err := terminal.record(nil, test.err); !errors.Is(err, test.err) {
+				t.Fatalf("terminal recording error = %v", err)
+			}
+			envelope := recorder.envelope(t, "attempt/response-0001.json")
+			encoded, err := json.Marshal(envelope.Payload)
+			if err != nil {
+				t.Fatal(err)
+			}
+			var artifact debugLLMResponseArtifact
+			if err := json.Unmarshal(encoded, &artifact); err != nil {
+				t.Fatal(err)
+			}
+			if artifact.Execution == nil || *artifact.Execution != want {
+				t.Fatalf("persisted response lost execution summary: %+v", artifact)
+			}
+			if !test.debugResponse && (artifact.Fallback == nil || artifact.Fallback.Execution == nil || *artifact.Fallback.Execution != want) {
+				t.Fatalf("persisted fallback lost execution summary: %+v", artifact.Fallback)
+			}
+			if test.content == "" {
+				if artifact.ContentPath != "" {
+					t.Fatalf("bodyless failure has content path %q", artifact.ContentPath)
+				}
+			} else {
+				var compact bytes.Buffer
+				if artifact.ContentPath == "" || json.Compact(&compact, recorder.bytes[artifact.ContentPath]) != nil || compact.String() != test.content {
+					t.Fatalf("split content not preserved at %q", artifact.ContentPath)
+				}
+				if (artifact.Fallback != nil && artifact.Fallback.Content != "") || (artifact.Response != nil && artifact.Response.Content != "") {
+					t.Fatal("split content remains in response metadata")
+				}
+			}
+			refs := recorder.envelope(t, "attempt/terminal.json").LLMCalls
+			if len(refs) != 1 || refs[0].Execution == nil || *refs[0].Execution != want || refs[0].Error != (test.err != nil) {
+				t.Fatalf("terminal references = %+v", refs)
+			}
+			// Decode the persisted JSON, not just Go defaults: omitted false and
+			// zero fields would erase the presence-aware usage contract.
+			usage := envelope.Payload.(map[string]any)["execution"].(map[string]any)["usage"].(map[string]any)
+			unknown := usage["cached_tokens"].(map[string]any)
+			for _, key := range []string{"value", "known", "complete"} {
+				if _, ok := unknown[key]; !ok {
+					t.Fatalf("unknown token usage omits %q: %+v", key, unknown)
+				}
+			}
+		})
+	}
+}

scripts/check-release-source.sh

@@ -2,85 +2,23 @@
 
 set -eu
 
-fail() {
-	printf '%s\n' "check-release-source: $*" >&2
-	exit 1
-}
-
-if [ "$#" -ne 1 ]; then
-	fail "usage: $0 vMAJOR.MINOR.PATCH"
-fi
-
-release_version=$1
-if ! printf '%s\n' "$release_version" | grep -E -x 'v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)' >/dev/null; then
-	fail "version must be a stable semantic version tag"
-fi
+fail() { printf '%s\n' "check-release-source: $*" >&2; exit 1; }
 
+[ "$#" -eq 1 ] || fail "usage: $0 vMAJOR.MINOR.PATCH"
+version=$1
+printf '%s\n' "$version" | grep -E -x 'v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)' >/dev/null || fail "invalid stable release version"
 script_dir=$(CDPATH= cd "$(dirname "$0")" && pwd)
-repo_root=$(CDPATH= cd "$script_dir/.." && pwd)
-cd "$repo_root"
+cd "$script_dir/.."
+note="docs/releases/$version.md"
+[ -s "$note" ] || fail "missing release note: $note"
+[ "$(head -n 1 "$note")" = "# Notarius $version" ] || fail "release note title does not match version"
 
-temporary_dir=$(mktemp -d "${TMPDIR:-/tmp}/notarius-release-source.XXXXXX") || fail "create temporary directory"
-trap 'rm -rf "$temporary_dir"' 0 HUP INT TERM
+export GOWORK=off
+go test -count=1 ./...
 
-if ! grep -E '^module[[:space:]]+gitea\.maximumdirect\.net/eric/notarius([[:space:]]|$)' go.mod >/dev/null; then
-	fail "go.mod does not declare the expected module path"
-fi
-
-if git ls-files --error-unmatch go.work >/dev/null 2>&1 || git ls-files --error-unmatch go.work.sum >/dev/null 2>&1; then
-	fail "tracked Go workspace files are not allowed"
-fi
-if [ -d vendor ]; then
-	fail "vendor directory is not allowed"
-fi
-if grep -E '^[[:space:]]*replace([[:space:]]|$)' go.mod >/dev/null; then
-	fail "go.mod replace directives are not allowed"
-fi
-
-GOWORK=off go test -count=1 ./...
-GOWORK=off go test -race -count=1 ./...
-GOWORK=off go vet ./...
-GOWORK=off go build ./...
-GOWORK=off go mod tidy -diff
-
-unformatted=$(git ls-files '*.go' | while IFS= read -r go_file; do
-	fmt_output=$(gofmt -l "$go_file")
-	if [ -n "$fmt_output" ]; then
-		printf '%s\n' "$fmt_output"
-	fi
-done)
-if [ -n "$unformatted" ]; then
-	printf '%s\n' "$unformatted" >&2
-	fail "tracked Go files are not gofmt formatted"
-fi
-
-git diff --check
-git diff --cached --check
-
-GOWORK=off go run ./cmd/notarius config validate --config examples/dnd-minimal.config.yml --pipeline dnd-session
-GOWORK=off OPENROUTER_API_KEY=validation-placeholder go run ./cmd/notarius config validate --config examples/dnd-complete.config.yml --pipeline dnd-session
-
-host_os=$(GOWORK=off go env GOOS)
-host_arch=$(GOWORK=off go env GOARCH)
-version_symbol='gitea.maximumdirect.net/eric/notarius/internal/buildinfo.Override'
-
-build_target() {
-	target_os=$1
-	target_arch=$2
-	target_path="$temporary_dir/notarius-$target_os-$target_arch"
-	CGO_ENABLED=0 GOOS="$target_os" GOARCH="$target_arch" GOWORK=off go build -trimpath \
-		-ldflags "-X $version_symbol=$release_version" \
-		-o "$target_path" ./cmd/notarius
-	if [ "$host_os" = "$target_os" ] && [ "$host_arch" = "$target_arch" ]; then
-		"$target_path" --version > "$temporary_dir/version-output"
-		printf 'notarius %s\n' "$release_version" > "$temporary_dir/expected-version-output"
-		if ! cmp -s "$temporary_dir/expected-version-output" "$temporary_dir/version-output"; then
-			fail "version output is incorrect for $target_os/$target_arch"
-		fi
-	fi
-}
-
-build_target linux amd64
-build_target linux arm64
-build_target darwin amd64
-build_target darwin arm64
+# Exercise the actual command and its linker-supplied diagnostic version.
+verification_dir=$(mktemp -d "${TMPDIR:-/tmp}/notarius-release-check.XXXXXX")
+trap 'rm -rf "$verification_dir"' 0 HUP INT TERM
+go build -trimpath -ldflags "-X gitea.maximumdirect.net/eric/notarius/internal/buildinfo.Override=$version" \
+  -o "$verification_dir/notarius" ./cmd/notarius
+[ "$("$verification_dir/notarius" --version)" = "notarius $version" ] || fail "incorrect diagnostic version"

scripts/release.sh

@@ -0,0 +1,56 @@
+#!/bin/sh
+
+set -eu
+
+fail() { printf '%s\n' "release: $*" >&2; exit 1; }
+
+[ "$#" -eq 1 ] || fail "usage: $0 vMAJOR.MINOR.PATCH"
+version=$1
+printf '%s\n' "$version" | grep -E -x 'v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)' >/dev/null || fail "invalid stable release version"
+script_dir=$(CDPATH= cd "$(dirname "$0")" && pwd)
+cd "$script_dir/.."
+export GOWORK=off
+candidate=$(git rev-parse 'HEAD^{commit}')
+
+check_candidate() {
+  [ "$(git branch --show-current)" = main ] || fail "release branch must be main"
+  [ -z "$(git status --porcelain)" ] || fail "worktree and index must be clean"
+  [ "$(git rev-parse 'HEAD^{commit}')" = "$candidate" ] || fail "candidate changed during validation"
+  git cat-file -e "$candidate:docs/releases/$version.md" || fail "release note must be committed"
+}
+
+check_publication() {
+  # Query failure is not proof that the tag is unused.
+  remote_tag=$(git ls-remote --tags origin "refs/tags/$version" "refs/tags/$version^{}") || fail "cannot determine remote tag availability"
+  [ -z "$remote_tag" ] || fail "remote tag already exists: $version"
+  if git show-ref --verify --quiet "refs/tags/$version"; then
+    fail "local tag already exists: $version"
+  fi
+  git fetch --no-tags origin refs/heads/main || fail "cannot fetch authoritative main"
+  remote_main=$(git rev-parse 'FETCH_HEAD^{commit}')
+  git merge-base --is-ancestor "$remote_main" "$candidate" || fail "candidate does not contain authoritative main"
+}
+
+check_candidate
+check_publication
+"$script_dir/check-release-source.sh" "$version"
+check_candidate
+check_publication
+
+if ! git -c push.followTags=false push origin "$candidate:refs/heads/main"; then
+  # Do not publish a tag after a failed branch push, even if the branch arrived.
+  git ls-remote origin refs/heads/main >&2 || fail "branch publication status unknown; inspect origin before retrying"
+  fail "branch push failed; inspect the reported remote state before retrying"
+fi
+
+git -c tag.gpgSign=false tag "$version" "$candidate"
+[ "$(git cat-file -t "$version")" = commit ] || fail "tag is not lightweight"
+[ "$(git rev-parse "$version^{commit}")" = "$candidate" ] || fail "tag target changed"
+if ! git -c push.followTags=false push origin "refs/tags/$version:refs/tags/$version"; then
+  # A connection can fail after the server accepted the tag. Preserve it locally
+  # until authoritative state proves whether publication succeeded.
+  remote_tag=$(git ls-remote --tags origin "refs/tags/$version" "refs/tags/$version^{}") || fail "tag publication status unknown; preserve local tag and inspect origin"
+  expected=$(printf '%s\t%s' "$candidate" "refs/tags/$version")
+  [ "$remote_tag" = "$expected" ] || fail "tag push failed; preserve local tag and inspect origin before retrying"
+fi
+printf 'Released %s at %s\n' "$version" "$candidate"

scripts/release_test.go

@@ -0,0 +1,243 @@
+package scripts
+
+import (
+	"os"
+	"os/exec"
+	"path/filepath"
+	"strings"
+	"testing"
+)
+
+// Keep publication tests offline: real Git repositories exercise ref safety,
+// while a fake Go command represents the expensive candidate validation boundary.
+type releaseFixture struct {
+	t       *testing.T
+	root    string
+	remote  string
+	bin     string
+	log     string
+	initial string
+}
+
+func writeFile(t *testing.T, path, content string, mode os.FileMode) {
+	t.Helper()
+	if err := os.MkdirAll(filepath.Dir(path), 0755); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(path, []byte(content), mode); err != nil {
+		t.Fatal(err)
+	}
+}
+
+func command(t *testing.T, dir string, args ...string) string {
+	t.Helper()
+	cmd := exec.Command(args[0], args[1:]...)
+	cmd.Dir = dir
+	output, err := cmd.CombinedOutput()
+	if err != nil {
+		t.Fatalf("%v: %v\n%s", args, err, output)
+	}
+	return strings.TrimSpace(string(output))
+}
+
+func newReleaseFixture(t *testing.T) *releaseFixture {
+	t.Helper()
+	dir := t.TempDir()
+	f := &releaseFixture{t: t, root: filepath.Join(dir, "work"), remote: filepath.Join(dir, "origin.git"), bin: filepath.Join(dir, "bin"), log: filepath.Join(dir, "validation.log")}
+	command(t, dir, "git", "init", "--bare", f.remote)
+	command(t, dir, "git", "init", "-b", "main", f.root)
+	f.git("config", "user.name", "Release Test")
+	f.git("config", "user.email", "release@example.invalid")
+	f.git("config", "commit.gpgSign", "false")
+	f.git("config", "tag.gpgSign", "false")
+	for _, name := range []string{"release.sh", "check-release-source.sh"} {
+		content, err := os.ReadFile(name)
+		if err != nil {
+			t.Fatal(err)
+		}
+		writeFile(t, filepath.Join(f.root, "scripts", name), string(content), 0755)
+	}
+	writeFile(t, filepath.Join(f.root, ".gitignore"), "vendor/\n", 0644)
+	f.git("add", ".")
+	f.git("commit", "-m", "Initial source")
+	f.git("remote", "add", "origin", f.remote)
+	f.git("push", "origin", "main")
+	f.initial = f.git("rev-parse", "HEAD")
+	writeFile(t, filepath.Join(f.root, "docs/releases/v0.8.0.md"), "# Notarius v0.8.0\n\nA concise note without fixed sections.\n", 0644)
+	f.git("add", ".")
+	f.git("commit", "-m", "Prepare release")
+	writeFile(t, filepath.Join(f.bin, "go"), `#!/bin/sh
+set -eu
+[ "$GOWORK" = off ]
+printf '%s\n' "$1" >> "$RELEASE_TEST_LOG"
+case "$1" in
+test)
+  [ "${RELEASE_TEST_FAIL:-}" != test ] || exit 1
+  if [ "${RELEASE_TEST_CHANGE:-}" = yes ]; then
+    printf 'changed\n' >> docs/releases/v0.8.0.md
+  fi
+  ;;
+build)
+  while [ "$1" != -o ]; do shift; done
+  shift
+  printf '#!/bin/sh\nprintf "notarius v0.8.0\\n"\n' > "$1"
+  chmod +x "$1"
+  ;;
+*) exit 1 ;;
+esac
+`, 0755)
+	return f
+}
+
+func (f *releaseFixture) git(args ...string) string {
+	f.t.Helper()
+	return command(f.t, f.root, append([]string{"git"}, args...)...)
+}
+
+func (f *releaseFixture) run(version string, env ...string) (string, error) {
+	f.t.Helper()
+	cmd := exec.Command("sh", "scripts/release.sh", version)
+	cmd.Dir = f.root
+	cmd.Env = append(os.Environ(), "PATH="+f.bin+string(os.PathListSeparator)+os.Getenv("PATH"), "RELEASE_TEST_LOG="+f.log)
+	cmd.Env = append(cmd.Env, env...)
+	output, err := cmd.CombinedOutput()
+	return string(output), err
+}
+
+func TestReleasePublishesExactCandidateOnce(t *testing.T) {
+	f := newReleaseFixture(t)
+	// Neither ignored local files nor unrelated local tags are release inputs.
+	writeFile(t, filepath.Join(f.root, "vendor/local.txt"), "ignored", 0644)
+	f.git("tag", "unrelated")
+	f.git("tag", "-a", "unrelated-annotated", "-m", "Do not publish")
+	f.git("config", "push.followTags", "true")
+	candidate := f.git("rev-parse", "HEAD")
+	output, err := f.run("v0.8.0")
+	if err != nil {
+		t.Fatalf("release: %v\n%s", err, output)
+	}
+	for _, ref := range []string{"refs/heads/main", "refs/tags/v0.8.0"} {
+		if got := command(t, f.remote, "git", "rev-parse", ref); got != candidate {
+			t.Fatalf("%s = %s, want %s", ref, got, candidate)
+		}
+	}
+	if got := command(t, f.remote, "git", "cat-file", "-t", "v0.8.0"); got != "commit" {
+		t.Fatalf("tag type = %s", got)
+	}
+	if got := f.git("ls-remote", "--tags", "origin", "refs/tags/unrelated*"); got != "" {
+		t.Fatal("published unrelated tag")
+	}
+	log, err := os.ReadFile(f.log)
+	if err != nil || string(log) != "test\nbuild\n" {
+		t.Fatalf("validation was not performed once: %q, %v", log, err)
+	}
+}
+
+func TestReleaseGuardsPreventPublication(t *testing.T) {
+	for _, name := range []string{"invalid_version", "missing_note", "wrong_title", "dirty", "staged", "wrong_branch", "local_tag", "remote_tag", "remote_ahead", "remote_unavailable", "validation_failure", "candidate_changed"} {
+		t.Run(name, func(t *testing.T) {
+			f := newReleaseFixture(t)
+			version := "v0.8.0"
+			var env []string
+			switch name {
+			case "invalid_version":
+				version = "v00.8.0"
+			case "missing_note":
+				version = "v0.8.1"
+			case "wrong_title":
+				writeFile(t, filepath.Join(f.root, "docs/releases/v0.8.0.md"), "# Wrong version\n", 0644)
+				f.git("add", ".")
+				f.git("commit", "-m", "Wrong title")
+			case "dirty", "staged":
+				writeFile(t, filepath.Join(f.root, "dirty.txt"), "dirty", 0644)
+				if name == "staged" {
+					f.git("add", ".")
+				}
+			case "wrong_branch":
+				f.git("checkout", "-b", "other")
+			case "local_tag":
+				f.git("tag", version)
+			case "remote_tag":
+				f.git("push", "origin", f.initial+":refs/tags/"+version)
+			case "remote_ahead":
+				// Publish an independent descendant of the old remote tip.
+				f.git("checkout", "-b", "other", f.initial)
+				f.git("commit", "--allow-empty", "-m", "Other work")
+				f.git("push", "origin", "HEAD:main")
+				f.initial = f.git("rev-parse", "HEAD")
+				f.git("checkout", "main")
+			case "remote_unavailable":
+				f.git("remote", "set-url", "origin", filepath.Join(t.TempDir(), "missing.git"))
+			case "validation_failure":
+				env = []string{"RELEASE_TEST_FAIL=test"}
+			case "candidate_changed":
+				env = []string{"RELEASE_TEST_CHANGE=yes"}
+			}
+			if output, err := f.run(version, env...); err == nil {
+				t.Fatalf("guard allowed publication: %s", output)
+			}
+			if got := command(t, f.remote, "git", "rev-parse", "main"); got != f.initial {
+				t.Fatal("guard advanced remote branch")
+			}
+			if name != "remote_tag" {
+				if got := command(t, f.remote, "git", "tag", "--list"); got != "" {
+					t.Fatalf("guard published tag: %s", got)
+				}
+			}
+		})
+	}
+}
+
+func TestReleasePushFailureRecovery(t *testing.T) {
+	for _, mode := range []string{"branch_rejected", "tag_rejected", "tag_accepted_disconnect", "tag_unknown"} {
+		t.Run(mode, func(t *testing.T) {
+			f := newReleaseFixture(t)
+			if mode == "branch_rejected" || mode == "tag_rejected" {
+				pattern := "refs/heads/main"
+				if mode == "tag_rejected" {
+					pattern = "refs/tags/*"
+				}
+				writeFile(t, filepath.Join(f.remote, "hooks/update"), "#!/bin/sh\ncase \"$1\" in "+pattern+") exit 1;; esac\n", 0755)
+			} else {
+				realGit, err := exec.LookPath("git")
+				if err != nil {
+					t.Fatal(err)
+				}
+				// Simulate a lost acknowledgement, optionally followed by an outage.
+				writeFile(t, filepath.Join(f.bin, "git"), `#!/bin/sh
+set -eu
+if [ "$1" = -c ] && [ "$3" = push ] && [ "$5" = refs/tags/v0.8.0:refs/tags/v0.8.0 ]; then
+  "$RELEASE_TEST_GIT" "$@"
+  touch "$RELEASE_TEST_MARKER"
+  exit 1
+fi
+if [ "$1" = ls-remote ] && [ -e "$RELEASE_TEST_MARKER" ] && [ "$RELEASE_TEST_MODE" = tag_unknown ]; then
+  exit 1
+fi
+exec "$RELEASE_TEST_GIT" "$@"
+`, 0755)
+				output, err := f.run("v0.8.0", "RELEASE_TEST_GIT="+realGit, "RELEASE_TEST_MARKER="+filepath.Join(f.bin, "marker"), "RELEASE_TEST_MODE="+mode)
+				if (err == nil) != (mode == "tag_accepted_disconnect") {
+					t.Fatalf("unexpected outcome: %v\n%s", err, output)
+				}
+				if got := command(t, f.remote, "git", "rev-parse", "v0.8.0"); got != f.git("rev-parse", "HEAD") {
+					t.Fatal("wrong remote tag")
+				}
+				return
+			}
+			if output, err := f.run("v0.8.0"); err == nil {
+				t.Fatalf("rejected push reported success: %s", output)
+			}
+			if got := command(t, f.remote, "git", "tag", "--list"); got != "" {
+				t.Fatal("rejected push published tag")
+			}
+			if mode == "tag_rejected" {
+				if got := f.git("rev-parse", "v0.8.0"); got != f.git("rev-parse", "HEAD") {
+					t.Fatal("unpublished local tag not preserved")
+				}
+			} else if got := f.git("tag", "--list"); got != "" {
+				t.Fatal("created tag after failed branch push")
+			}
+		})
+	}
+}