Adopt the updated repository policies

.woodpecker/release.yml

@@ -1,25 +1,51 @@
+matrix:
+  include:
+    - GO_IMAGE: golang:1.27.3-bookworm
+
 when:
   - event: tag
+    ref: refs/tags/v*
 
 steps:
-  - name: build-release-assets
-    image: golang:1.25.5
-    commands:
-      - bash scripts/build-release.sh "$CI_COMMIT_TAG" dist
-
-  - name: publish-release
-    image: woodpeckerci/plugin-release
-    depends_on:
-      - build-release-assets
-    settings:
-      api_key:
+  - name: deliver
+    image: ${GO_IMAGE}
+    environment:
+      RELEASEKIT_GITEA_TOKEN:
         from_secret: GITEA_RELEASE_TOKEN
-      files:
-        - dist/audita-*-linux-amd64
-        - dist/audita-*-linux-arm64
-      checksum: sha256
-      checksum-file: SHA256SUMS
-      checksum-flatten: true
-      file-exists: skip
-      overwrite: false
-      prerelease: false
+    commands:
+      - |
+        set -eu
+        test -n "$${CI_COMMIT_TAG}"
+        test -n "$${CI_COMMIT_SHA}"
+        git check-ref-format "refs/tags/$${CI_COMMIT_TAG}"
+        git fetch origin "refs/tags/$${CI_COMMIT_TAG}:refs/tags/$${CI_COMMIT_TAG}"
+        tag_commit=$(git rev-parse "refs/tags/$${CI_COMMIT_TAG}^{commit}")
+        expected_commit=$(git rev-parse --verify "$${CI_COMMIT_SHA}^{commit}")
+        test "$(printf '%s' "$${tag_commit}" | tr '[:upper:]' '[:lower:]')" = "$${expected_commit}"
+        git checkout --detach "$${tag_commit}"
+        test "$(git rev-parse HEAD | tr '[:upper:]' '[:lower:]')" = "$${expected_commit}"
+        test -z "$(git status --porcelain --untracked-files=all)"
+
+        bootstrap_dir=$(mktemp -d "$${CI_WORKSPACE%/*}/.releasekit-bootstrap.XXXXXX")
+        trap 'rm -rf "$${bootstrap_dir}"' EXIT
+        cp go.mod "$${bootstrap_dir}/releasekit.mod"
+        if [ -f go.sum ]; then
+          cp go.sum "$${bootstrap_dir}/releasekit.sum"
+        else
+          : > "$${bootstrap_dir}/releasekit.sum"
+        fi
+
+        export GOWORK=off
+        export GOTOOLCHAIN=local
+        releasekit_host_os=$(go env GOHOSTOS) || exit $?
+        releasekit_host_arch=$(go env GOHOSTARCH) || exit $?
+        export GOOS="$${releasekit_host_os}" GOARCH="$${releasekit_host_arch}"
+        releasekit_module=go.maximumdirect.net/releasekit
+        go list -mod=mod -modfile="$${bootstrap_dir}/releasekit.mod" -m "$${releasekit_module}"
+        go mod edit -modfile="$${bootstrap_dir}/releasekit.mod" -tool="$${releasekit_module}/cmd/releasekit"
+        go list -mod=mod -modfile="$${bootstrap_dir}/releasekit.mod" -deps "$${releasekit_module}/cmd/releasekit" > /dev/null
+        go tool -modfile="$${bootstrap_dir}/releasekit.mod" "$${releasekit_module}/cmd/releasekit" ci-deliver \
+          --repo "$${CI_WORKSPACE}" \
+          --prepared \
+          --commit "$${expected_commit}" \
+          "$${CI_COMMIT_TAG}"

AGENTS.md

@@ -1,4 +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.
 
-Review and follow `docs/policy/agents.md` before recommending, planning, or implementing any changes to this repository.
+Read and follow `docs/policy/agents.md` before recommending, planning, or
+implementing repository changes.

COPYRIGHT

@@ -0,0 +1,23 @@
+Audita
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: GPL-3.0-or-later
+
+Audita 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.
+
+Audita 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.
+
+Policy documents and guidance adapted from Standard Repository Policies
+remain licensed under CC-BY-SA-4.0. See docs/oss/attribution.md for the
+affected material, upstream credit, and license links.

LICENSE

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

README.md

@@ -1,58 +1,41 @@
 # Audita
 
-Audita polishes transcript JSON using glossary-aware and LLM-backed correction
-modules. It validates proposed corrections and produces corrected text plus
-reports for review and subprocess integration.
+Audita polishes transcript JSON with glossary-aware and LLM-backed correction
+modules. It validates proposed edits and produces corrected text and reports for
+review or subprocess integration.
 
 ## Quickstart
 
-From a checkout, build with Go 1.25.5 or newer:
+Build with Go 1.27.0 or newer:
 
 ```sh
 go build -o ./bin/audita ./cmd/audita
 ```
 
-Processing requires a reachable [compatible LLM endpoint](docs/integrations/openai-compatible-llm.md)
-and access to a model you select. The [minimal config](examples/minimal-config.yml)
-targets an unauthenticated local endpoint; edit its endpoint and
-[local profiles](examples/profiles/) to match your service and models. The
-[service example](examples/production-config.yml) demonstrates a named credential
-reference and a shared backend. Set its referenced environment variable before
-validating it. The [testing overlay](examples/overlays/testing.yml) selects both
-role profiles, but model cost, speed, and quality depend on your provider choices.
-
-Check configuration and profile selection offline:
+Edit the synthetic endpoint and model in [examples/local/prompts.yml](examples/local/prompts.yml)
+for a reachable OpenAI-compatible service. From `examples/local`, run the built
+executable (adjust the executable path if needed):
 
 ```sh
-./bin/audita config validate --config examples/minimal-config.yml
-./bin/audita config print-effective --config examples/minimal-config.yml --view profiles
+../../bin/audita config validate --config config.yml
+../../bin/audita process --config config.yml --output corrected.json transcript.json
 ```
 
-Run the included small input with the minimal config:
-
-```sh
-./bin/audita process examples/tiny-transcript.json \
-  --config examples/minimal-config.yml \
-  --glossary examples/tiny-glossary.yaml \
-  --output corrected.json
-```
-
-This makes LLM requests. Explicit setting flags override the selected file and
-optional overlay; general environment setting overrides are no longer read.
-By default the command writes `errors.yml`, `recoveries.yml`, and `report.md`
-beside `corrected.json`. Use `--reporting=false` to suppress those files, or
-`--debug` to retain detailed run artifacts under the configured debug work
-directory. Model failures affecting some operations can still yield a completed
-transcript with applied corrections; the summary and reports identify them.
-See the [v2 migration guide](docs/migrations/v2.md) for old configurations.
+Processing makes model requests. Reports are written beside the output by default;
+recoverable model errors can appear in a completed run. The [example guide](examples/README.md)
+includes service, overlay, prompt editing, preview, and shared glossary projects.
+See the [v3 migration guide](docs/migrations/v3.md) for the configuration cutover.
 
 ## Documentation
 
-- [CLI reference](docs/cli.md)
-- [Configuration and maintained examples](docs/config.md)
+- [CLI reference](docs/cli.md) and [configuration](docs/config.md)
 - [Operations and artifact lifecycle](docs/operations.md)
 - [Transcript and glossary inputs](docs/integrations/transcript-glossary-files.md)
 - [Output files and report formats](docs/integrations/output-files.md)
 - [Subprocess integration](docs/integrations/subprocess.md)
 - [LLM endpoint contract](docs/integrations/openai-compatible-llm.md)
 - [Contributor guide](docs/development.md)
+
+Audita is licensed under the [GPL v3.0 or later](COPYRIGHT).
+
+[Open Source attribution notices](docs/oss/attribution.md) are available.

cmd/audita/correction_repair_integration_test.go

@@ -0,0 +1,374 @@
+package main
+
+import (
+	"bytes"
+	"context"
+	"encoding/json"
+	"fmt"
+	"net/http"
+	"net/http/httptest"
+	"os"
+	"os/exec"
+	"path/filepath"
+	"reflect"
+	"strings"
+	"sync"
+	"testing"
+	"time"
+
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/reporting"
+)
+
+type repairWireMessage struct {
+	Role    string `json:"role"`
+	Content string `json:"content"`
+}
+type repairWireRequest struct {
+	Messages       []repairWireMessage `json:"messages"`
+	ResponseFormat struct {
+		JSONSchema struct {
+			Schema struct {
+				Properties map[string]any `json:"properties"`
+			} `json:"schema"`
+		} `json:"json_schema"`
+	} `json:"response_format"`
+}
+type correctionProvider struct {
+	mu                   sync.Mutex
+	requests             []repairWireRequest
+	attempts             map[int]int
+	entered              chan struct{}
+	wait                 bool
+	invalidFirstRevision bool
+}
+
+func (p *correctionProvider) ServeHTTP(w http.ResponseWriter, r *http.Request) {
+	var req repairWireRequest
+	if err := json.NewDecoder(r.Body).Decode(&req); err != nil {
+		http.Error(w, "bad request", 400)
+		return
+	}
+	_, repair := req.ResponseFormat.JSONSchema.Schema.Properties["proposal_ref"]
+	_, validation := req.ResponseFormat.JSONSchema.Schema.Properties["validations"]
+	p.mu.Lock()
+	p.requests = append(p.requests, req)
+	p.mu.Unlock()
+	content := `{"corrections":[{"id":1,"original_text":"hello","corrected_text":"Hello","confidence":0.99},{"id":2,"original_text":"second","corrected_text":"Second","confidence":0.1},{"id":3,"original_text":"third","corrected_text":"Third","confidence":0.1}]}`
+	if validation {
+		var indices []int
+		for _, message := range req.Messages {
+			if pos := strings.LastIndex(message.Content, "Corrections to validate:"); pos >= 0 {
+				var items []struct {
+					CorrectionIndex int `json:"correction_index"`
+				}
+				if err := json.Unmarshal([]byte(strings.TrimSpace(message.Content[pos+len("Corrections to validate:"):])), &items); err != nil {
+					http.Error(w, "bad validation", 400)
+					return
+				}
+				for _, item := range items {
+					indices = append(indices, item.CorrectionIndex)
+				}
+			}
+		}
+		var decisions []map[string]any
+		for _, index := range indices {
+			decisions = append(decisions, map[string]any{"correction_index": index, "approved": true, "confidence": 0.99, "reason": "controlled"})
+		}
+		raw, _ := json.Marshal(map[string]any{"validations": decisions})
+		content = string(raw)
+	}
+	if repair {
+		if p.wait {
+			select {
+			case p.entered <- struct{}{}:
+			default:
+			}
+			<-r.Context().Done()
+			return
+		}
+		ref := 2
+		if strings.Contains(req.Messages[len(req.Messages)-1].Content, `"proposal_ref":3`) {
+			ref = 3
+		}
+		p.mu.Lock()
+		p.attempts[ref]++
+		attempt := p.attempts[ref]
+		invalid := p.invalidFirstRevision && attempt == 1
+		p.mu.Unlock()
+		if ref == 3 {
+			http.Error(w, `{"error":{"message":"context too long"}}`, http.StatusBadRequest)
+			return
+		}
+		confidence := 0.1
+		if attempt > 1 {
+			confidence = 0.99
+		}
+		id := 2
+		if invalid {
+			id, confidence = 99, 0.99
+		}
+		content = fmt.Sprintf(`{"proposal_ref":2,"action":"revise","correction":{"id":%d,"original_text":"second","corrected_text":"Second","confidence":%v}}`, id, confidence)
+	}
+	raw, _ := json.Marshal(content)
+	w.Header().Set("Content-Type", "application/json")
+	fmt.Fprintf(w, `{"model":"fixture","choices":[{"message":{"content":%s}}]}`, raw)
+}
+
+func TestSubprocessReportsDefectOnOriginatingRepair(t *testing.T) {
+	for _, tc := range []struct {
+		budget     int
+		outcome    string
+		recoveries int
+	}{{1, "exhausted", 1}, {2, "applied", 2}} {
+		t.Run(tc.outcome, func(t *testing.T) {
+			f, provider := setupCorrectionFixture(t, tc.budget, false, false)
+			provider.mu.Lock()
+			provider.invalidFirstRevision = true
+			provider.mu.Unlock()
+			if code, _, stderr := f.run(t, true); code != 0 {
+				t.Fatalf("code=%d stderr=%s", code, stderr)
+			}
+			doc := f.recoveries(t)
+			if *doc.Summary.ProposalResponses != 1 || *doc.Summary.ProposalResponsesWithFiltering != 0 || len(doc.Recoveries) != tc.recoveries {
+				t.Fatalf("unexpected recoveries: %+v", doc)
+			}
+			first := doc.Recoveries[0]
+			want := []reporting.FilteredProposal{{ProposalIndex: 1, Reason: "invalid_target_segment_id", Count: 1}}
+			if first.Operation != "correction_repair" || !reflect.DeepEqual(first.FilteredProposals, want) || !reflect.DeepEqual(first.Reasons, []string{"proposals_filtered"}) {
+				t.Fatalf("first repair recovery: %+v", first)
+			}
+			if tc.recoveries == 2 && !reflect.DeepEqual(doc.Recoveries[1].Reasons, []string{"correction_revised"}) {
+				t.Fatalf("successful repair recovery: %+v", doc.Recoveries[1])
+			}
+			report, err := os.ReadFile(filepath.Join(f.dir, "report.md"))
+			if err != nil || !strings.Contains(string(report), fmt.Sprintf("| 1 | 1 | 1 | %d | %s |", tc.budget, tc.outcome)) {
+				t.Fatalf("repair outcome: %s %v", report, err)
+			}
+		})
+	}
+}
+func setupCorrectionFixture(t *testing.T, attempts int, replacement, wait bool) (processFixture, *correctionProvider) {
+	t.Helper()
+	f := newProcessFixture(t, "normal", "[grammar]")
+	f.setSegments(t, "hello world", "second text", "third text")
+	provider := &correctionProvider{attempts: map[int]int{}, entered: make(chan struct{}, 1), wait: wait}
+	server := httptest.NewServer(provider)
+	t.Cleanup(server.Close)
+	resources := fmt.Sprintf("profiles:\n  - id: proposal\n    endpoint: %s/v1\n    model: fixture\n  - id: validation\n    endpoint: %s/v1\n    model: fixture\n", server.URL, server.URL)
+	if replacement {
+		resources += "collections:\n  audita:\n    prompts:\n      - id: modules.grammar.repair\n        messages:\n          - role: user\n            content_file: repair.txt\n        output:\n          format: json\n          validation_mode: json_schema\n          schema_path: correction_repair.v1.json\n"
+		if err := os.WriteFile(filepath.Join(f.dir, "repair.txt"), []byte("OVERRIDE {{ .RepairRequestJSON }}"), 0600); err != nil {
+			t.Fatal(err)
+		}
+	}
+	if err := os.WriteFile(filepath.Join(f.dir, "prompts.yml"), []byte(resources), 0600); err != nil {
+		t.Fatal(err)
+	}
+	data, err := os.ReadFile(f.config)
+	if err != nil {
+		t.Fatal(err)
+	}
+	text := strings.Replace(string(data), "correction_repair_attempts: 0", fmt.Sprintf("correction_repair_attempts: %d", attempts), 1)
+	text += "chunking:\n  target_sections: 1\n  min_section_tokens: 1\nnormalization:\n  max_segment_gap: 0\n"
+	if err := os.WriteFile(f.config, []byte(text), 0600); err != nil {
+		t.Fatal(err)
+	}
+	return f, provider
+}
+
+func TestSubprocessCorrectionRepairConversation(t *testing.T) {
+	for _, tc := range []struct {
+		name               string
+		debug, replacement bool
+	}{{"default prompt without debug", false, false}, {"replacement with debug", true, true}} {
+		t.Run(tc.name, func(t *testing.T) {
+			f, provider := setupCorrectionFixture(t, 2, tc.replacement, false)
+			args := []string{"--verbose"}
+			if tc.debug {
+				args = append(args, "--debug")
+			}
+			code, stdout, stderr := f.run(t, true, args...)
+			if code != 0 || stdout != "" {
+				t.Fatalf("code=%d stdout=%s stderr=%s", code, stdout, stderr)
+			}
+			output := f.readTranscript(t, f.output)
+			if len(output.Segments) != 3 || output.Segments[0].Text != "Hello world" || output.Segments[1].Text != "Second text" || output.Segments[2].Text != "third text" {
+				t.Fatalf("transcript: %+v", output)
+			}
+			report, err := os.ReadFile(filepath.Join(f.dir, "report.md"))
+			if err != nil {
+				t.Fatal(err)
+			}
+			for _, fragment := range []string{"## Correction repair", "| 1 | 1 | 1 | 2 | applied |", "| 1 | 1 | 2 | 1 | unavailable |"} {
+				if !strings.Contains(string(report), fragment) {
+					t.Errorf("missing %q in %s", fragment, report)
+				}
+			}
+			doc := f.errors(t)
+			recoveries := f.recoveries(t)
+			if doc.Summary.LLMOperations == nil || *doc.Summary.LLMOperations != 10 || *doc.Summary.CorrectionsApplied != 2 || *doc.Summary.Recoveries != 1 || !reflect.DeepEqual(doc.Summary, recoveries.Summary) || !strings.Contains(stderr, "2 corrections applied; 1 work units with errors; 1 recoveries") {
+				t.Fatalf("counts: errors=%+v recoveries=%+v stderr=%s", doc.Summary, recoveries.Summary, stderr)
+			}
+			if len(doc.Errors) != 1 || len(doc.Errors[0].Failures) != 1 || doc.Errors[0].Failures[0].Operation != "correction_repair" || doc.Errors[0].Failures[0].Reason != "provider_failed" {
+				t.Fatalf("errors: %+v", doc)
+			}
+			provider.mu.Lock()
+			requests := append([]repairWireRequest(nil), provider.requests...)
+			provider.mu.Unlock()
+			var base []repairWireMessage
+			var branches [][]repairWireMessage
+			for _, req := range requests {
+				if _, ok := req.ResponseFormat.JSONSchema.Schema.Properties["corrections"]; ok {
+					base = req.Messages
+				}
+				if _, ok := req.ResponseFormat.JSONSchema.Schema.Properties["proposal_ref"]; ok {
+					branches = append(branches, req.Messages)
+				}
+			}
+			if len(base) != 2 || len(branches) != 3 || len(branches[0]) != 4 || len(branches[1]) != 6 || len(branches[2]) != 4 {
+				t.Fatalf("request lengths base=%d branches=%v", len(base), branches)
+			}
+			for _, messages := range branches {
+				for i := range base {
+					if messages[i] != base[i] {
+						t.Fatalf("changed prefix: %+v", messages)
+					}
+				}
+				if messages[2].Role != "assistant" || !strings.Contains(messages[2].Content, `"corrections"`) {
+					t.Fatalf("missing initial response: %+v", messages)
+				}
+			}
+			if branches[1][3] != branches[0][3] || branches[1][4].Role != "assistant" || strings.Contains(branches[2][3].Content, `"proposal_ref":2`) {
+				t.Fatalf("branch history: %+v", branches)
+			}
+			if tc.replacement && !strings.Contains(branches[0][3].Content, "OVERRIDE") {
+				t.Fatal("replacement not used")
+			}
+			if tc.debug {
+				_, ledger := f.debugArtifacts(t)
+				if len(ledger) != 3 {
+					t.Fatalf("ledger: %+v", ledger)
+				}
+			}
+		})
+	}
+}
+
+func TestSubprocessRepairDisabledAndOutputSelections(t *testing.T) {
+	for _, tc := range []struct {
+		name             string
+		reporting, debug bool
+	}{{"neither", false, false}, {"debug only", false, true}, {"report only", true, false}} {
+		t.Run(tc.name, func(t *testing.T) {
+			f, provider := setupCorrectionFixture(t, 0, false, false)
+			if !tc.reporting {
+				file, err := os.OpenFile(f.config, os.O_APPEND|os.O_WRONLY, 0600)
+				if err != nil {
+					t.Fatal(err)
+				}
+				fmt.Fprintln(file, "reporting:\n  enabled: false")
+				file.Close()
+			}
+			var args []string
+			if tc.debug {
+				args = append(args, "--debug")
+			}
+			code, _, stderr := f.run(t, true, args...)
+			if code != 0 {
+				t.Fatalf("code=%d stderr=%s", code, stderr)
+			}
+			provider.mu.Lock()
+			requests := append([]repairWireRequest(nil), provider.requests...)
+			provider.mu.Unlock()
+			for _, req := range requests {
+				if _, ok := req.ResponseFormat.JSONSchema.Schema.Properties["proposal_ref"]; ok {
+					t.Fatal("repair request with zero budget")
+				}
+			}
+			_, err := os.Stat(filepath.Join(f.dir, "report.md"))
+			if tc.reporting != (err == nil) {
+				t.Fatalf("report selection: %v", err)
+			}
+			if tc.debug {
+				_, ledger := f.debugArtifacts(t)
+				if len(ledger) == 0 {
+					t.Fatal("debug ledger missing")
+				}
+			} else if _, err := os.Stat(filepath.Join(f.dir, "runs")); !os.IsNotExist(err) {
+				t.Fatalf("unexpected debug dir: %v", err)
+			}
+		})
+	}
+}
+
+func TestSubprocessCancellationDuringCorrectionRepair(t *testing.T) {
+	f, provider := setupCorrectionFixture(t, 2, false, true)
+	ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second)
+	defer cancel()
+	args := []string{"-test.run=^TestProcessSubprocessHelper$", "--", "process", f.transcript, "--config", f.config, "--output", f.output, "--debug"}
+	command := exec.CommandContext(ctx, os.Args[0], args...)
+	command.Env = append(os.Environ(), "AUDITA_HELPER_PROCESS=1")
+	var stderr bytes.Buffer
+	command.Stderr = &stderr
+	if err := command.Start(); err != nil {
+		t.Fatal(err)
+	}
+	select {
+	case <-provider.entered:
+	case <-ctx.Done():
+		t.Fatalf("repair not reached: %v", ctx.Err())
+	}
+	if err := command.Process.Signal(os.Interrupt); err != nil {
+		t.Fatal(err)
+	}
+	err := command.Wait()
+	if ctx.Err() != nil || err == nil {
+		t.Fatalf("cancellation: %v ctx=%v stderr=%s", err, ctx.Err(), stderr.String())
+	}
+	if _, err := os.Stat(f.output); !os.IsNotExist(err) {
+		t.Fatalf("transcript published: %v", err)
+	}
+	doc := f.errors(t)
+	if doc.Status != reporting.StatusFailed || len(doc.Errors) == 0 {
+		t.Fatalf("failed report: %+v", doc)
+	}
+	data, err := os.ReadFile(filepath.Join(f.dir, "report.md"))
+	if err != nil || !strings.Contains(string(data), "| 1 | 1 | 1 | 1 | interrupted |") {
+		t.Fatalf("partial report %s %v", data, err)
+	}
+	_, ledger := f.debugArtifacts(t)
+	if len(ledger) == 0 {
+		t.Fatal("partial ledger missing")
+	}
+}
+
+func TestSubprocessRepairWithoutOrdinaryReporting(t *testing.T) {
+	for _, debug := range []bool{false, true} {
+		t.Run(fmt.Sprintf("debug=%t", debug), func(t *testing.T) {
+			f, _ := setupCorrectionFixture(t, 2, false, false)
+			file, err := os.OpenFile(f.config, os.O_APPEND|os.O_WRONLY, 0600)
+			if err != nil {
+				t.Fatal(err)
+			}
+			fmt.Fprintln(file, "reporting:\n  enabled: false")
+			file.Close()
+			args := []string{"--verbose"}
+			if debug {
+				args = append(args, "--debug")
+			}
+			code, _, stderr := f.run(t, true, args...)
+			if code != 0 || !strings.Contains(stderr, "2 corrections applied; 1 work units with errors; 1 recoveries") {
+				t.Fatalf("code=%d stderr=%s", code, stderr)
+			}
+			if _, err := os.Stat(filepath.Join(f.dir, "report.md")); !os.IsNotExist(err) {
+				t.Fatalf("unexpected report: %v", err)
+			}
+			if debug {
+				_, ledger := f.debugArtifacts(t)
+				if len(ledger) != 3 {
+					t.Fatalf("ledger: %+v", ledger)
+				}
+			}
+		})
+	}
+}

cmd/audita/main.go

@@ -6,7 +6,7 @@ import (
 	"os/signal"
 	"syscall"
 
-	"gitea.maximumdirect.net/eric/audita/internal/cli"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/cli"
 )
 
 func main() {

cmd/audita/main_integration_test.go

@@ -19,9 +19,9 @@ import (
 	"testing"
 	"time"
 
-	"gitea.maximumdirect.net/eric/audita/internal/cli"
-	"gitea.maximumdirect.net/eric/audita/internal/core/reporting"
-	"gitea.maximumdirect.net/eric/audita/internal/core/schema"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/cli"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/reporting"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/schema"
 	"gopkg.in/yaml.v3"
 )
 
@@ -122,6 +122,11 @@ func (p *fixtureProvider) serve(w http.ResponseWriter, r *http.Request) {
 		return
 	}
 	content := `{"corrections":[{"id":1,"original_text":"hello world","corrected_text":"Hello world","confidence":0.99}]}`
+	if p.mode == "invalid-credential-echo" {
+		sent := strings.TrimPrefix(r.Header.Get("Authorization"), "Bearer ")
+		raw, _ := json.Marshal(map[string]string{"unexpected": sent + "|" + p.secret})
+		content = string(raw)
+	}
 	if p.mode == "repair-filter-later-failure" && !validation {
 		if proposalCall == 1 {
 			content = `{"wrong":true}`
@@ -231,17 +236,15 @@ func newProcessFixture(t *testing.T, mode, modules string) processFixture {
 	t.Helper()
 	dir := t.TempDir()
 	p := &fixtureProvider{mode: mode, secret: `selected-secret-"\-123`, entered: make(chan struct{}, 1)}
+	if mode == "invalid-credential-echo" {
+		p.secret = "  synthetic-echo-credential\t "
+	}
 	server := httptest.NewServer(http.HandlerFunc(p.serve))
 	t.Cleanup(server.Close)
-	if err := os.Mkdir(filepath.Join(dir, "profiles"), 0700); err != nil {
+	resources := fmt.Sprintf("backends:\n  - id: local\n    endpoint: %s/v1\n    api_key_env: AUDITA_TEST_PROVIDER_KEY\nprofiles:\n  - id: proposal\n    backend: local\n    model: local\n  - id: validation\n    backend: local\n    model: local\n", server.URL)
+	if err := os.WriteFile(filepath.Join(dir, "prompts.yml"), []byte(resources), 0600); err != nil {
 		t.Fatal(err)
 	}
-	for _, id := range []string{"proposal", "validation"} {
-		profile := fmt.Sprintf("id: %s\nbackend: local\nmodel: local\ntimeout_seconds: 5\n", id)
-		if err := os.WriteFile(filepath.Join(dir, "profiles", id+".yaml"), []byte(profile), 0600); err != nil {
-			t.Fatal(err)
-		}
-	}
 	configPath := filepath.Join(dir, "config.yml")
 	repairs := 0
 	if mode == "repair-filter-later-failure" || mode == "invalid-decision-after-repair" {
@@ -250,7 +253,17 @@ func newProcessFixture(t *testing.T, mode, modules string) processFixture {
 	if strings.HasPrefix(mode, "span-") || strings.HasPrefix(mode, "decision-") {
 		repairs = 1
 	}
-	configText := fmt.Sprintf("version: 2\nbackends:\n  local:\n    endpoint: %s/v1\n    credential: AUDITA_TEST_PROVIDER_KEY\nllm:\n  proposal_profile: proposal\n  validation_profile: validation\n  transient_retries: 0\n  repair_attempts: %d\npipeline:\n  modules: %s\ndiagnostics:\n  work_dir: %s\n", server.URL, repairs, modules, filepath.Join(dir, "runs"))
+	var stageList []string
+	for _, name := range strings.Split(strings.Trim(modules, "[]"), ",") {
+		if name = strings.TrimSpace(name); name != "" {
+			stageList = append(stageList, "    - module: "+name)
+		}
+	}
+	pipeline := "  stages: []\n"
+	if len(stageList) != 0 {
+		pipeline = "  stages:\n" + strings.Join(stageList, "\n") + "\n"
+	}
+	configText := fmt.Sprintf("version: 3\nllm:\n  proposal_profile: proposal\n  validation_profile: validation\n  transient_retries: 0\n  correction_repair_attempts: 0\n  repair_attempts: %d\npipeline:\n%sdiagnostics:\n  work_dir: %s\n", repairs, pipeline, filepath.Join(dir, "runs"))
 	if strings.HasPrefix(mode, "span-") || strings.HasPrefix(mode, "decision-") {
 		configText += "validation:\n  max_prompt_tokens: 4096\nchunking:\n  target_sections: 1\n  max_section_tokens: 8192\n  min_section_tokens: 1\nnormalization:\n  max_segment_gap: 0\n"
 	}
@@ -271,7 +284,7 @@ func newProcessFixture(t *testing.T, mode, modules string) processFixture {
 
 func (f processFixture) run(t *testing.T, includeOutput bool, extra ...string) (int, string, string) {
 	t.Helper()
-	args := []string{"-test.run=^TestProcessSubprocessHelper$", "--", "process", f.transcript, "--config", f.config, "--glossary", f.glossary}
+	args := []string{"-test.run=^TestProcessSubprocessHelper$", "--", "process", f.transcript, "--config", f.config}
 	if includeOutput {
 		args = append(args, "--output", f.output)
 	}
@@ -293,6 +306,25 @@ func (f processFixture) run(t *testing.T, includeOutput bool, extra ...string) (
 	return code, stdout.String(), stderr.String()
 }
 
+func (f processFixture) runConfigView(t *testing.T, view string) (int, string, string) {
+	t.Helper()
+	command := exec.Command(os.Args[0], "-test.run=^TestProcessSubprocessHelper$", "--", "config", "print-effective", "--config", f.config, "--view", view)
+	command.Dir = f.dir
+	command.Env = append(os.Environ(), "AUDITA_HELPER_PROCESS=1", "AUDITA_TEST_PROVIDER_KEY="+f.provider.secret)
+	var stdout, stderr bytes.Buffer
+	command.Stdout, command.Stderr = &stdout, &stderr
+	err := command.Run()
+	code := 0
+	if err != nil {
+		if exit, ok := err.(*exec.ExitError); ok {
+			code = exit.ExitCode()
+		} else {
+			t.Fatal(err)
+		}
+	}
+	return code, stdout.String(), stderr.String()
+}
+
 func (f processFixture) errors(t *testing.T) reporting.ErrorsDocument {
 	t.Helper()
 	raw, err := os.ReadFile(filepath.Join(f.dir, "errors.yml"))
@@ -756,7 +788,7 @@ func TestSubprocessRespectsNegativeMeaningReviewOnDeletion(t *testing.T) {
 func TestSubprocessDefaultFileOutputAndReports(t *testing.T) {
 	f := newProcessFixture(t, "normal", "[grammar]")
 	code, stdout, stderr := f.run(t, true)
-	if code != 0 || stdout != "" || !strings.HasPrefix(stderr, "Completed: 1 corrections applied; 0 work units with errors; 0 recoveries.") {
+	if code != 0 || stdout != "" || stderr != "" {
 		t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout, stderr)
 	}
 	output, err := os.ReadFile(f.output)
@@ -788,7 +820,7 @@ func TestSubprocessStdoutAndSelectedReportDirectory(t *testing.T) {
 		t.Fatal(err)
 	}
 	code, stdout, stderr := f.run(t, false, "--report-dir", reports)
-	if code != 0 || !strings.Contains(stdout, "Hello world") || !strings.HasPrefix(stderr, "Completed:") {
+	if code != 0 || !strings.Contains(stdout, "Hello world") || stderr != "" {
 		t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout, stderr)
 	}
 	if _, err := os.Stat(f.output); !os.IsNotExist(err) {
@@ -799,35 +831,82 @@ func TestSubprocessStdoutAndSelectedReportDirectory(t *testing.T) {
 	}
 }
 
+func TestSubprocessUsesIndependentTranscriptReportAndDebugDestinations(t *testing.T) {
+	f := newProcessFixture(t, "normal", "[grammar]")
+	transcriptDir := filepath.Join(f.dir, "transcripts")
+	reportDir := filepath.Join(f.dir, "reports")
+	debugDir := filepath.Join(f.dir, "debug")
+	for _, dir := range []string{transcriptDir, reportDir} {
+		if err := os.Mkdir(dir, 0700); err != nil {
+			t.Fatal(err)
+		}
+	}
+	f.output = filepath.Join(transcriptDir, "corrected.json")
+	code, stdout, stderr := f.run(t, true, "--report-dir", reportDir, "--debug", "--work-dir", debugDir)
+	if code != 0 || stdout != "" || !strings.Contains(stderr, "Completed:") {
+		t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout, stderr)
+	}
+	if output, err := os.ReadFile(f.output); err != nil || !bytes.Contains(output, []byte("Hello world")) {
+		t.Fatalf("transcript: %s %v", output, err)
+	}
+	for _, name := range []string{"errors.yml", "recoveries.yml", "report.md"} {
+		if _, err := os.Stat(filepath.Join(reportDir, name)); err != nil {
+			t.Fatalf("report %s: %v", name, err)
+		}
+		if _, err := os.Stat(filepath.Join(transcriptDir, name)); !os.IsNotExist(err) {
+			t.Fatalf("report %s appeared beside transcript: %v", name, err)
+		}
+	}
+	dirs, err := filepath.Glob(filepath.Join(debugDir, "run-*"))
+	if err != nil || len(dirs) != 1 {
+		t.Fatalf("debug runs: %v %v", dirs, err)
+	}
+	if _, err := os.Stat(filepath.Join(dirs[0], "correction-ledger.json")); err != nil {
+		t.Fatalf("debug capture: %v", err)
+	}
+}
+
 func TestSubprocessReportingAndDebugSelections(t *testing.T) {
 	var expectedOutput, expectedSummary string
 	for _, selection := range []struct{ reporting, debug bool }{
 		{false, false}, {false, true}, {true, false}, {true, true},
 	} {
-		f := newProcessFixture(t, "normal", "[grammar]")
-		extra := []string{"--reporting=false", "--report-dir", filepath.Join(f.dir, "missing")}
+		f := newProcessFixture(t, "repair-filter-later-failure", "[grammar, grammar]")
+
+		reportDir := filepath.Join(f.dir, "missing")
+		extra := []string{"--verbose", "--reporting=false", "--report-dir", reportDir}
 		if selection.reporting {
-			extra = []string{"--reporting=true", "--report-dir", filepath.Join(f.dir, "missing")}
+			reportDir = filepath.Join(f.dir, "selected-reports")
+			if err := os.Mkdir(reportDir, 0700); err != nil {
+				t.Fatal(err)
+			}
+			extra = []string{"--verbose", "--reporting=true", "--report-dir", reportDir}
 		}
 		if selection.debug {
 			extra = append(extra, "--debug")
 		}
 		code, stdout, stderr := f.run(t, true, extra...)
-		if code != 0 || stdout != "" || !strings.HasPrefix(stderr, "Completed:") {
+		if code != 0 || stdout != "" || !strings.Contains(stderr, "1 corrections applied; 1 work units with errors; 1 recoveries") {
 			t.Fatalf("selection=%+v code=%d stdout=%q stderr=%q", selection, code, stdout, stderr)
 		}
 		output, err := os.ReadFile(f.output)
 		if err != nil {
 			t.Fatal(err)
 		}
-		summary := strings.SplitN(stderr, "\n", 2)[0]
+		summary := ""
+		for _, line := range strings.Split(stderr, "\n") {
+			if strings.HasPrefix(line, "Completed:") {
+				summary = line
+				break
+			}
+		}
 		if expectedOutput == "" {
 			expectedOutput, expectedSummary = string(output), summary
 		} else if string(output) != expectedOutput || summary != expectedSummary {
 			t.Fatalf("selection changed processing: %+v summary=%q output=%s", selection, summary, output)
 		}
 		for _, name := range []string{"errors.yml", "recoveries.yml", "report.md"} {
-			_, err := os.Stat(filepath.Join(f.dir, name))
+			_, err := os.Stat(filepath.Join(reportDir, name))
 			if selection.reporting && err != nil || !selection.reporting && !os.IsNotExist(err) {
 				t.Fatalf("selection=%+v report %s: %v", selection, name, err)
 			}
@@ -842,6 +921,7 @@ func TestSubprocessReportingAndDebugSelections(t *testing.T) {
 					t.Fatal(err)
 				}
 			}
+
 		}
 	}
 }
@@ -855,7 +935,7 @@ func boolInt(value bool) int {
 
 func TestSubprocessAllModelFailureStillCompletes(t *testing.T) {
 	f := newProcessFixture(t, "all-model-failure", "[grammar, grammar]")
-	code, stdout, stderr := f.run(t, true)
+	code, stdout, stderr := f.run(t, true, "--verbose")
 	if code != 0 || stdout != "" || !strings.Contains(stderr, "2 work units with errors") {
 		t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout, stderr)
 	}
@@ -872,9 +952,41 @@ func TestSubprocessAllModelFailureStillCompletes(t *testing.T) {
 	}
 }
 
+func TestSubprocessMasksPaddedCredentialInProviderResponse(t *testing.T) {
+	f := newProcessFixture(t, "invalid-credential-echo", "[grammar]")
+	effective := strings.TrimSpace(f.provider.secret)
+	code, stdout, stderr := f.run(t, true, "--debug")
+	if code != 0 || f.provider.callCount() != 1 || !strings.Contains(stderr, "1 work units with errors") {
+		t.Fatalf("code=%d calls=%d stdout=%q stderr=%q", code, f.provider.callCount(), stdout, stderr)
+	}
+	if strings.Contains(stderr, effective) || strings.Contains(stdout, effective) {
+		t.Fatal("credential escaped redaction in command output")
+	}
+	responseCaptured := false
+	err := filepath.WalkDir(f.dir, func(path string, entry os.DirEntry, err error) error {
+		if err != nil || entry.IsDir() {
+			return err
+		}
+		data, err := os.ReadFile(path)
+		if err != nil {
+			return err
+		}
+		if bytes.Contains(data, []byte(effective)) {
+			t.Errorf("credential escaped redaction in %s", entry.Name())
+		}
+		if strings.HasSuffix(entry.Name(), "-response-payload.json") && bytes.Contains(data, []byte("[REDACTED]|[REDACTED]")) {
+			responseCaptured = true
+		}
+		return nil
+	})
+	if err != nil || !responseCaptured {
+		t.Fatalf("missing redacted provider echo: %v", err)
+	}
+}
+
 func TestSubprocessAllValidationFailureStillCompletes(t *testing.T) {
 	f := newProcessFixture(t, "all-validation-failure", "[grammar, grammar]")
-	code, stdout, stderr := f.run(t, true)
+	code, stdout, stderr := f.run(t, true, "--verbose")
 	if code != 0 || stdout != "" || !strings.Contains(stderr, "2 work units with errors") {
 		t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout, stderr)
 	}
@@ -890,7 +1002,7 @@ func TestSubprocessAllValidationFailureStillCompletes(t *testing.T) {
 
 func TestSubprocessRecoveredFilteringSurvivesLaterFailure(t *testing.T) {
 	f := newProcessFixture(t, "repair-filter-later-failure", "[grammar, grammar]")
-	code, _, stderr := f.run(t, true)
+	code, _, stderr := f.run(t, true, "--verbose")
 	if code != 0 || !strings.Contains(stderr, "1 corrections applied; 1 work units with errors; 1 recoveries") {
 		t.Fatalf("code=%d stderr=%q errors=%+v", code, stderr, f.errors(t))
 	}
@@ -920,7 +1032,7 @@ func TestSubprocessRecoveredFilteringSurvivesLaterFailure(t *testing.T) {
 
 func TestSubprocessRepairedInvalidDecisionsRemainAnError(t *testing.T) {
 	f := newProcessFixture(t, "invalid-decision-after-repair", "[grammar]")
-	code, _, stderr := f.run(t, true)
+	code, _, stderr := f.run(t, true, "--verbose")
 	if code != 0 || !strings.Contains(stderr, "0 corrections applied; 1 work units with errors; 0 recoveries") {
 		t.Fatalf("code=%d stderr=%q", code, stderr)
 	}
@@ -938,7 +1050,7 @@ func TestSubprocessCancellationLeavesFailedReportsWithoutTranscript(t *testing.T
 	f := newProcessFixture(t, "wait-cancel", "[grammar, grammar]")
 	ctx, stop := context.WithTimeout(context.Background(), 5*time.Second)
 	defer stop()
-	args := []string{"-test.run=^TestProcessSubprocessHelper$", "--", "process", f.transcript, "--config", f.config, "--glossary", f.glossary, "--output", f.output}
+	args := []string{"-test.run=^TestProcessSubprocessHelper$", "--", "process", f.transcript, "--config", f.config, "--output", f.output}
 	command := exec.CommandContext(ctx, os.Args[0], args...)
 	command.Env = append(os.Environ(), "AUDITA_HELPER_PROCESS=1", "AUDITA_TEST_PROVIDER_KEY="+f.provider.secret)
 	var stderr bytes.Buffer
@@ -968,7 +1080,7 @@ func TestSubprocessCancellationLeavesFailedReportsWithoutTranscript(t *testing.T
 
 func TestSubprocessPartialValidationAndLaterStage(t *testing.T) {
 	f := newProcessFixture(t, "partial-validation", "[grammar, grammar]")
-	code, _, stderr := f.run(t, true)
+	code, _, stderr := f.run(t, true, "--verbose")
 	if code != 0 || !strings.Contains(stderr, "1 corrections applied; 1 work units with errors") {
 		t.Fatalf("code=%d stderr=%q", code, stderr)
 	}
@@ -982,32 +1094,63 @@ func TestSubprocessPartialValidationAndLaterStage(t *testing.T) {
 	}
 }
 
-func TestSubprocessInvalidInputLeavesFailedReports(t *testing.T) {
+func TestSubprocessInvalidInputCreatesNoOutput(t *testing.T) {
 	f := newProcessFixture(t, "normal", "[grammar]")
 	if err := os.WriteFile(f.transcript, []byte("not JSON"), 0600); err != nil {
 		t.Fatal(err)
 	}
 	code, _, _ := f.run(t, true)
-	if code != 1 || f.provider.callCount() != 0 {
+	if code != 2 || f.provider.callCount() != 0 {
 		t.Fatalf("invalid input dispatched: code=%d calls=%d", code, f.provider.callCount())
 	}
-	if document := f.errors(t); document.Status != reporting.StatusFailed || len(document.Errors) != 1 || document.Errors[0].Scope != "run" {
-		t.Fatalf("failed report: %+v", document)
-	}
+
 	if _, err := os.Stat(f.output); !os.IsNotExist(err) {
 		t.Fatalf("failed transcript published: %v", err)
 	}
-	var recoveries reporting.RecoveriesDocument
-	if raw, err := os.ReadFile(filepath.Join(f.dir, "recoveries.yml")); err != nil {
-		t.Fatal(err)
-	} else if err := yaml.Unmarshal(raw, &recoveries); err != nil {
+}
+
+func TestSubprocessMissingInheritanceParentFailsBeforeProviderDispatch(t *testing.T) {
+	f := newProcessFixture(t, "normal", "[grammar]")
+	original, err := os.ReadFile(filepath.Join(f.dir, "prompts.yml"))
+	if err != nil {
 		t.Fatal(err)
 	}
-	if recoveries.Status != reporting.StatusFailed {
-		t.Fatalf("recoveries status: %+v", recoveries)
+	updated := strings.Replace(string(original), "  - id: local\n", "  - id: local\n    extends: {id: missing}\n", 1)
+	if updated == string(original) {
+		t.Fatal("process fixture backend configuration was not found")
 	}
-	if raw, err := os.ReadFile(filepath.Join(f.dir, "report.md")); err != nil || !bytes.Contains(raw, []byte("Status: failed")) {
-		t.Fatalf("Markdown status: %s %v", raw, err)
+	if err := os.WriteFile(filepath.Join(f.dir, "prompts.yml"), []byte(updated), 0600); err != nil {
+		t.Fatal(err)
+	}
+	code, stdout, stderr := f.run(t, true)
+	if code != 2 || stdout != "" || f.provider.callCount() != 0 {
+		t.Fatalf("missing parent handling: code=%d stdout=%q stderr=%q provider calls=%d", code, stdout, stderr, f.provider.callCount())
+	}
+}
+
+func TestSubprocessInvalidInputDoesNotCreateReportsInSelectedDirectory(t *testing.T) {
+	f := newProcessFixture(t, "normal", "[grammar]")
+	if err := os.WriteFile(f.transcript, []byte("not JSON"), 0600); err != nil {
+		t.Fatal(err)
+	}
+	reportDir := filepath.Join(f.dir, "failed-reports")
+	if err := os.Mkdir(reportDir, 0700); err != nil {
+		t.Fatal(err)
+	}
+	code, _, _ := f.run(t, true, "--report-dir", reportDir)
+	if code != 2 || f.provider.callCount() != 0 {
+		t.Fatalf("invalid input dispatched: code=%d calls=%d", code, f.provider.callCount())
+	}
+	for _, name := range []string{"errors.yml", "recoveries.yml", "report.md"} {
+		if _, err := os.Stat(filepath.Join(reportDir, name)); !os.IsNotExist(err) {
+			t.Fatalf("report created before preflight: %s %v", name, err)
+		}
+	}
+	if _, err := os.Stat(filepath.Join(f.dir, "errors.yml")); !os.IsNotExist(err) {
+		t.Fatalf("failed report appeared in default directory: %v", err)
+	}
+	if _, err := os.Stat(f.output); !os.IsNotExist(err) {
+		t.Fatalf("failed transcript published: %v", err)
 	}
 }
 
@@ -1026,7 +1169,7 @@ func TestSubprocessOutputFailureBeforeModelDispatch(t *testing.T) {
 func TestSubprocessOptionalDebugFailureDoesNotChangeOutcome(t *testing.T) {
 	f := newProcessFixture(t, "normal", "[grammar]")
 	code, _, stderr := f.run(t, true, "--debug", "--work-dir", f.transcript)
-	if code != 0 || !strings.HasPrefix(stderr, "Completed: 1 corrections applied") || !strings.Contains(stderr, "debug directory") {
+	if code != 0 || !strings.Contains(stderr, "Completed: 1 corrections applied") || !strings.Contains(stderr, "work directory") {
 		t.Fatalf("optional debug failure changed processing: code=%d stderr=%q", code, stderr)
 	}
 	if _, err := os.Stat(f.output); err != nil {
@@ -1041,7 +1184,7 @@ func TestSubprocessTranscriptPreflightWithoutReporting(t *testing.T) {
 	f := newProcessFixture(t, "normal", "[grammar]")
 	f.output = filepath.Join(f.dir, "missing", "output.json")
 	code, _, stderr := f.run(t, true, "--reporting=false")
-	if code == 0 || f.provider.callCount() != 0 || !strings.Contains(stderr, "transcript output parent") {
+	if code == 0 || f.provider.callCount() != 0 || !strings.Contains(stderr, "prepare transcript output") {
 		t.Fatalf("transcript preflight: code=%d calls=%d stderr=%q", code, f.provider.callCount(), stderr)
 	}
 }
@@ -1100,12 +1243,12 @@ func TestSubprocessPathAnnouncementsAreRedacted(t *testing.T) {
 			selected, unused := "selected-path-secret", "unused-path-secret"
 			f.provider.secret = selected
 			t.Setenv("AUDITA_UNUSED_PATH_KEY", unused)
-			cfg, err := os.ReadFile(f.config)
+			cfg, err := os.ReadFile(filepath.Join(f.dir, "prompts.yml"))
 			if err != nil {
 				t.Fatal(err)
 			}
-			cfg = bytes.Replace(cfg, []byte("backends:\n"), []byte("backends:\n  unused:\n    endpoint: http://unused.invalid/v1\n    credential: AUDITA_UNUSED_PATH_KEY\n"), 1)
-			if err := os.WriteFile(f.config, cfg, 0600); err != nil {
+			cfg = bytes.Replace(cfg, []byte("backends:\n"), []byte("backends:\n  - id: unused\n    endpoint: http://unused.invalid/v1\n    api_key_env: AUDITA_UNUSED_PATH_KEY\n"), 1)
+			if err := os.WriteFile(filepath.Join(f.dir, "prompts.yml"), cfg, 0600); err != nil {
 				t.Fatal(err)
 			}
 			reportDir := filepath.Join(f.dir, unused)
@@ -1120,20 +1263,20 @@ func TestSubprocessPathAnnouncementsAreRedacted(t *testing.T) {
 				}
 			}
 			code, _, stderr := f.run(t, true, "--debug", "--work-dir", debugParent)
-			if (!fail && code != 0) || (fail && code != 1) {
+			if (!fail && code != 0) || (fail && code != 2) {
 				t.Fatalf("code=%d stderr=%q", code, stderr)
 			}
 			if strings.Contains(stderr, selected) || strings.Contains(stderr, unused) {
 				t.Fatalf("credential in stderr: %q", stderr)
 			}
-			if !strings.Contains(stderr, "[REDACTED]") {
+			if !fail && !strings.Contains(stderr, "[REDACTED]") {
 				t.Fatalf("missing redacted announcement: %q", stderr)
 			}
-			if _, err := os.Stat(filepath.Join(reportDir, "report.md")); err != nil {
+			if _, err := os.Stat(filepath.Join(reportDir, "report.md")); !fail && err != nil {
 				t.Fatal(err)
 			}
 			dirs, err := os.ReadDir(debugParent)
-			if err != nil || len(dirs) != 1 {
+			if !fail && (err != nil || len(dirs) != 1) {
 				t.Fatalf("debug location: %v %v", dirs, err)
 			}
 			if !fail {
@@ -1147,7 +1290,7 @@ func TestSubprocessPathAnnouncementsAreRedacted(t *testing.T) {
 
 func TestSubprocessInteractionWriteFailureIsVisibleAndNonfatal(t *testing.T) {
 	f := newProcessFixture(t, "normal", "[grammar]")
-	code, _, baselineSummary := f.run(t, true)
+	code, _, baselineSummary := f.run(t, true, "--verbose")
 	if code != 0 {
 		t.Fatal(baselineSummary)
 	}
@@ -1162,16 +1305,16 @@ func TestSubprocessInteractionWriteFailureIsVisibleAndNonfatal(t *testing.T) {
 			t.Errorf("debug directory: %v %v", dirs, err)
 			return
 		}
-		if err := os.WriteFile(filepath.Join(dirs[0], "grammar"), []byte("block interaction writes"), 0600); err != nil {
+		if err := os.WriteFile(filepath.Join(dirs[0], "grammar_1"), []byte("block interaction writes"), 0600); err != nil {
 			t.Error(err)
 		}
 	}
 	f.provider.mu.Unlock()
 	code, _, stderr := f.run(t, true, "--debug")
-	if code != 0 || !strings.HasPrefix(stderr, strings.SplitN(baselineSummary, "\n", 2)[0]) {
+	if code != 0 || !strings.Contains(stderr, strings.SplitN(baselineSummary, "\n", 2)[0]) {
 		t.Fatalf("changed outcome: %d %q", code, stderr)
 	}
-	if !strings.Contains(stderr, "debug proposal interaction") || !strings.Contains(stderr, "debug validation interaction") {
+	if !strings.Contains(stderr, "proposal interaction") || !strings.Contains(stderr, "validation interaction") {
 		t.Fatalf("missing debug failures: %q", stderr)
 	}
 	output, err := os.ReadFile(f.output)
@@ -1204,7 +1347,7 @@ func TestSubprocessInPlaceTranscript(t *testing.T) {
 				t.Fatal(err)
 			}
 			if invalid {
-				if code != 1 || !bytes.Equal(before, after) {
+				if code != 2 || !bytes.Equal(before, after) {
 					t.Fatalf("failed processing changed input: code=%d %s", code, stderr)
 				}
 			} else if code != 0 || stdout != "" || !bytes.Contains(after, []byte("Hello world")) {
@@ -1218,15 +1361,18 @@ func TestSubprocessProfileSources(t *testing.T) {
 	f := newProcessFixture(t, "success", "[]")
 	// PromptKit uses profile IDs, not filename stems. A report-named profile is
 	// still an input and must not be overwritten during report initialization.
-	loaded := filepath.Join(f.dir, "profiles", "errors.yml")
-	if err := os.Rename(filepath.Join(f.dir, "profiles", "proposal.yaml"), loaded); err != nil {
+	if err := os.Mkdir(filepath.Join(f.dir, "prompts"), 0700); err != nil {
+		t.Fatal(err)
+	}
+	loaded := filepath.Join(f.dir, "prompts", "errors.yml")
+	if err := os.Rename(filepath.Join(f.dir, "prompts.yml"), loaded); err != nil {
 		t.Fatal(err)
 	}
 	before, err := os.ReadFile(loaded)
 	if err != nil {
 		t.Fatal(err)
 	}
-	f.output = filepath.Join(f.dir, "profiles", "proposal.yml")
+	f.output = filepath.Join(f.dir, "prompts", "proposal.yml")
 	code, _, stderr := f.run(t, true, "--reporting=false")
 	if code != 0 {
 		t.Fatalf("unused alternate rejected: %d %s", code, stderr)
@@ -1240,7 +1386,50 @@ func TestSubprocessProfileSources(t *testing.T) {
 	if err != nil {
 		t.Fatal(err)
 	}
-	if code != 2 || !bytes.Equal(before, after) || f.provider.callCount() != 0 {
+	if code != 1 || !bytes.Equal(before, after) || f.provider.callCount() != 0 {
 		t.Fatalf("loaded profile not protected: %d %s", code, stderr)
 	}
+
+	parentDir := filepath.Join(f.dir, "prompts", "catalog")
+	childDir := filepath.Join(f.dir, "prompts", "nested", "child")
+	for _, directory := range []string{parentDir, childDir} {
+		if err := os.MkdirAll(directory, 0700); err != nil {
+			t.Fatal(err)
+		}
+	}
+	parent := filepath.Join(parentDir, "arbitrary-name.yaml")
+	child := filepath.Join(childDir, "override.yaml")
+	resource := filepath.Join(parentDir, "report.md")
+	for path, content := range map[string]string{
+		parent:   "prompts:\n  - id: source\n    messages:\n      - role: user\n        content_file: report.md\n    output:\n      format: text\n      validation_mode: none\n",
+		child:    "prompts:\n  - id: child\n    extends: {id: source}\n",
+		resource: "Captured operator message.\n",
+	} {
+		if err := os.WriteFile(path, []byte(content), 0600); err != nil {
+			t.Fatal(err)
+		}
+	}
+	resourceBefore, err := os.ReadFile(resource)
+	if err != nil {
+		t.Fatal(err)
+	}
+	f.output = resource
+	code, _, stderr = f.run(t, true, "--reporting=false")
+	resourceAfter, err := os.ReadFile(resource)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if code != 1 || !bytes.Equal(resourceBefore, resourceAfter) || f.provider.callCount() != 0 {
+		t.Fatalf("consumed message file not protected as transcript output: %d %s", code, stderr)
+	}
+
+	f.output = filepath.Join(f.dir, "output.json")
+	code, _, stderr = f.run(t, true, "--report-dir", parentDir)
+	resourceAfter, err = os.ReadFile(resource)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if code != 1 || !bytes.Equal(resourceBefore, resourceAfter) || f.provider.callCount() != 0 {
+		t.Fatalf("consumed message file not protected as report output: %d %s", code, stderr)
+	}
 }

docs/adr/0001-releasekit.md

@@ -0,0 +1,45 @@
+# ADR 0001: Adopt ReleaseKit for release management
+
+## Status
+
+Accepted.
+
+## Date
+
+2026-10-07
+
+## Context
+
+Audita maintains custom release scripts, build tooling, delivery configuration,
+and tests for mechanics shared across applications in the same suite.
+[ReleaseKit](https://gitea.maximumdirect.net/eric/ReleaseKit) provides a common implementation and standard workflow for
+those responsibilities.
+
+## Decision
+
+Adopt ReleaseKit for shared release validation, source publication, binary
+builds, version information, and hosted delivery. Audita will follow its standard
+workflow and supply product identity, delivery targets, release notes, and
+necessary product-specific checks.
+
+Better maintainability and less locally owned release-focused code outweigh any
+small advantage from retaining Audita's custom release procedure. Changes to
+that procedure are an accepted consequence of standardization.
+
+## Alternatives considered
+
+Retaining the custom procedure would preserve its exact behavior and local
+control. It would also retain responsibility for duplicated mechanics, tests,
+and maintenance across projects. The shared implementation offers greater
+long-term value.
+
+## Consequences
+
+Audita's release integration becomes smaller, with common mechanics and their
+tests maintained upstream. Audita benefits from shared fixes and takes on
+ReleaseKit dependency maintenance.
+
+Adoption requires updates to release tooling, CI wiring, documentation, and
+runtime version reporting. The [release policy](../policy/release.md) continues
+to govern compatibility and release completion; the
+[release procedure](../release.md) will describe the adopted workflow.

docs/adr/0002-glossary-configuration-and-preflight.md

@@ -0,0 +1,42 @@
+# ADR 0002: Glossary configuration and processing readiness
+
+**Status:** Accepted
+
+**Date:** 2026-11-10
+
+## Context
+
+Operators need to reuse glossary collections across campaigns and select different
+context and protected terms for each ordered correction. Configuration inspection
+must remain useful without a transcript, model credentials, or a populated glossary.
+A processing run must reject an unusable later correction before publishing outputs
+or spending resources on earlier corrections.
+
+## Decision
+
+ConfigKit composes typed, named glossary collections with the application
+configuration. Each pipeline entry selects context and protection independently;
+Audita derives consumer views without changing the resolved configuration. For a
+glossary correction, active recognized spellings are exempt from that entry's
+protection view. Other protected spellings and validators remain effective.
+
+After configuration resolution, Audita preflight checks the whole pipeline and
+coordinates output preparation. It consumes the typed configuration and acquired
+inputs, without reloading configuration or calling a provider. The output session
+owns preparation, cleanup, and publication. See the [configuration](../config.md)
+and [operations](../operations.md) contracts for current behavior.
+
+## Alternatives considered
+
+A separately parsed glossary per invocation would duplicate composition and make
+per-entry selection and provenance harder to express. Requiring nonempty
+collections in configuration validation would prevent inspection and reuse of
+valid empty definitions. Preparing outputs or checking each entry only when it
+runs could leave artifacts or incur model work before finding a later error.
+
+## Consequences
+
+Configuration and runtime views have distinct responsibilities. Inspection can
+show configured selections and origins without presenting derived vocabulary as
+configuration. Preflight and the output session need a clear handoff, and the
+processing pipeline must carry each entry's own effective settings and identity.

docs/adr/0003-module-focus-and-editorial-acceptance.md

@@ -0,0 +1,59 @@
+# ADR 0003: Module focus and editorial acceptance
+
+**Status:** Accepted
+
+**Date:** 2026-11-11
+
+## Context
+
+Audita gives each correction module a focused task. A prompt review suggested
+making that task's scope an acceptance condition, because validators can accept
+minor editorial changes that the proposing module was not asked to make.
+
+The maintainer's practical testing established why this difference is deliberate.
+Models persistently propose minor editorial cleanup when it is clearly warranted
+in the supplied text. Instructions strict enough to suppress that cleanup also
+suppress desirable edits. Enforcing exclusive module scopes would therefore
+trade away useful corrections to achieve a separation that does not serve the
+application's editorial goals.
+
+## Decision
+
+Module scope guides the corrections Audita asks a model to propose. It is not an
+exhaustive boundary on acceptable edits. Minor editorial cleanup is permitted
+across modules and their validators even when the proposal prompt does not
+request it.
+
+Validators must not reject an otherwise acceptable minor editorial change solely
+because it falls outside the originating module's requested focus. Existing
+checks for applicability, protected terms, meaning, and other domain concerns
+continue to apply. This allowance does not guarantee that any particular edit
+passes validation or application, nor does it authorize arbitrary rewriting.
+
+Proposal, validation, and repair instructions may differ to serve their roles.
+Their consistency should be assessed against this distinction, rather than by
+requiring identical lists of allowed edits. Repair feedback should not turn
+module focus into an exclusive acceptance rule.
+
+## Alternatives considered
+
+**Strict module-aware acceptance**, whether implemented in shared validators,
+separate review definitions, or an additional scope check, would make stage
+boundaries easier to describe. It is rejected because the maintainer's testing
+shows that suppressing incidental cleanup also suppresses desirable work.
+
+**Request every kind of cleanup in every module** would align proposal requests
+with the broader acceptance policy, but would dilute the focused tasks. Permitting
+incidental cleanup does not require asking each stage to perform every task.
+
+## Consequences
+
+An edit accepted outside a module's requested focus is not, by itself, a design
+defect. Prompt maintenance and evaluation should preserve useful corrections
+while checking substantive editorial quality. They should not introduce strict
+scope enforcement as an apparent consistency fix.
+
+The [architecture policy](../policy/architecture.md#correction-and-concurrency-invariants)
+records the boundary. Reconsidering this accepted decision requires new evidence
+and explicit supersession under the ADR lifecycle, rather than rediscovering the
+same prompt/validator difference during each review.

docs/adr/README.md

@@ -1,6 +1,15 @@
 # Architectural Decision Records
 
-No ADRs have been recorded here. Use the
+## Accepted
+
+- [ADR 0001: Adopt ReleaseKit for release management](0001-releasekit.md) —
+  accepted 2026-10-07.
+- [ADR 0002: Glossary configuration and processing readiness](0002-glossary-configuration-and-preflight.md) —
+  accepted 2026-11-10.
+- [ADR 0003: Module focus and editorial acceptance](0003-module-focus-and-editorial-acceptance.md) —
+  accepted 2026-11-11.
+
+Use the
 [documentation policy's ADR lifecycle](../policy/documentation.md#architecture-decision-records)
 for significant decisions. Current architecture belongs in the
 [architecture policy](../policy/architecture.md); implementation status belongs in

docs/cli.md

@@ -1,95 +1,45 @@
 # Audita CLI Reference
 
-The shared version-2 configuration parser and offline profile inspection serve
-`process`, `config validate`, and `config print-effective`.
-The [configuration reference](config.md) owns fields, defaults, and validation;
-the [migration guide](migrations/v2.md) maps retired inputs.
+Audita uses CommandKit for routing and the ConfigKit and PromptKit integrations
+for their standard inspection and request commands. Run `audita --help` or
+command-specific `--help` for the installed command inventory. The adopted
+[CommandKit consumer guide](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/f369d6a78253b6e6fcb1e023fb2e9c3af1d20ff0/docs/consumers/guide.md)
+describes the standard command grammar, inspection, comparison, preview,
+validation, smoke tests, and their provider-specific caveats. Help and version
+do not load application or model configuration.
 
-## Commands and help
+## Processing
 
 ```sh
-audita process <transcript.json> --glossary <glossary.yml> [flags]
-audita config validate --config <config.yml> [flags]
-audita config print-effective [flags]
+audita process [flags] transcript.json
 ```
 
-Root invocation, `--help`, `-h`, and command help succeed without loading a config
-file or resolving secrets. Unknown commands and flags return exit code `2`.
-`process` accepts exactly one transcript path, either before the flags or after
-them. With flags first, put the transcript last. Both config commands reject
-positional arguments and process-only flags.
+`--config` selects a main configuration and `--overlay` selects its overlay.
+`--output` writes the transcript to a file; omission selects stdout. The shared
+`--debug` flag enables retained debug artifacts, and `--quiet` suppresses optional
+messages. Quiet processing requires an output file or `/dev/null`. See
+[operations](operations.md) for output and report lifecycle.
 
-All three commands accept `--config <path>` and `--overlay <name>`. `config validate`
-requires an explicit nonempty `--config`; the other commands select the explicit
-file, then `/usr/local/etc/audita/config.yml`, then `/etc/audita/config.yml`.
-Missing system candidates are skipped; inaccessible selected files are errors.
-No file means a configuration error. `AUDITA_CONFIG` is ignored. The selected
-overlay is loaded beside the main file, not used to locate profile files.
+Explicit process flags override root settings only. `--glossaries` and
+`--protected-terms` each accept one JSON array of collection names or `null`;
+`[]` clears the selection. Set pipeline order and per-entry overrides in YAML.
+Other supplied flags cover profiles, output schema, description, reporting,
+chunking, normalization, confidence thresholds, validation budget, and debug
+work directory. `audita process --help` lists the available flags. An omitted flag
+does not contribute an override. [Configuration](config.md) defines their values
+and inheritance.
 
-## Setting overrides
+## Inspection and outcomes
 
-Only flags actually supplied override file or overlay settings. `--modules ''`
-clears the module pipeline, and an explicit numeric zero reaches configuration
-validation. The shared setting flags are:
+The application configuration scope uses ConfigKit's native effective values,
+source evidence, explanation, comparison, and redaction. PromptKit supplies its
+own configuration and resource scopes and request preparation, validation, and
+explicit smoke diagnostics. Inspection does not require a processing-ready
+pipeline or contact a provider. Smoke tests can contact providers and are run
+only on explicit request.
 
-| Setting | Flags |
-| --- | --- |
-| Profile selection | `--proposal-profile`, `--validation-profile` |
-| Pipeline and output | `--modules`, `--output-schema` |
-| Validation budget | `--validation-max-prompt-tokens` |
-| Chunking | `--target-sections`, `--max-section-tokens`, `--min-section-tokens` |
-| Normalization (numeric seconds) | `--normalize-max-segment-gap`, `--normalize-ellipsis-gap`, `--normalize-max-segment-duration`, `--normalize-max-segment-tokens` |
-| Confidence thresholds | `--glossary-confidence-threshold`, `--homophones-confidence-threshold`, `--spoken-word-confidence-threshold`, `--grammar-confidence-threshold` |
-| Context | `--transcript-description` |
-| Reporting | `--reporting[=true\|false]`, `--report-dir DIR` |
-| Debug | `--debug[=true\|false]`, `--work-dir DIR` |
-
-`process` alone accepts `--glossary` (required) and `--output`.
-An omitted or empty output value selects stdout. Nonempty output filenames are
-used literally, including whitespace.
-Reporting defaults to enabled. `--reporting=false` disables all three ordinary
-reports; an explicit false overrides a true file or overlay setting. With file
-output, reports go beside the transcript and `--report-dir` has no effect. With
-stdout output, `--report-dir` selects the report directory, defaulting to the
-invocation working directory. `--debug` separately enables retained detailed
-artifacts under `--work-dir`. Configuration inspection does not create or probe
-these output directories.
-Per-role model, base URL, key, timeout, retry, and concurrency flags have been
-removed. Models and generation controls belong to PromptKit profiles, backend
-credentials and capacity to configuration, and retry/deadline settings to the
-shared LLM section. Legacy configuration environment overrides are ignored.
-
-## Streams and exit status
-
-`config validate` loads settings and both selected PromptKit profiles offline,
-then prints `config is valid` on success. `config print-effective` accepts
-`--view settings|profiles|explain` and defaults to `settings`. Settings writes
-ConfigKit's redacted effective-settings YAML. Profiles writes an Audita-owned
-YAML summary of selected ID, backend, model, sampling controls, per-attempt
-timeout, service tier, and reasoning effort for each role. It omits credentials,
-endpoints, and arbitrary extra provider parameters. Explain writes a YAML
-sequence of field paths, source origins, and recorded derivations without
-resolved setting values. These views share the same settings and profile
-validation path as `process`. Unknown views are usage errors. The effective
-settings YAML is for inspection and is not guaranteed reloadable.
-
-For `process`, `--output` writes the corrected transcript to a file and leaves
-stdout empty on success. Without it, stdout carries transcript JSON only on
-success. Enabled reporting creates `errors.yml`, `recoveries.yml`, and
-`report.md` in the selected directory. Successful stderr begins with
-`Completed: N corrections applied; E work units with errors; R recoveries.`
-Report and debug locations follow only when created. Model-operation failures
-can coexist with a completed run and applied corrections; read the YAML reports
-for details. Debug artifacts are created only with `--debug`. See the
-[report contract](integrations/output-files.md).
-
-Exit codes are `0` for success, `1` for runtime or output failure, and `2` for
-usage or configuration input errors. Invalid settings and profiles return `2`;
-broken embedded assets, caller cancellation, fatal processing, and required
-output failures return `1`. A late report-write failure can follow a published
-transcript; exit status and report status remain authoritative.
-Configuration commands inspect profiles without contacting a provider.
-
-See the [input files](integrations/transcript-glossary-files.md),
-[subprocess contract](integrations/subprocess.md), and
-[artifact lifecycle](operations.md) for their respective details.
+Process stdout contains transcript JSON when no output file is selected. Ordinary
+reports may record recoverable model failures even when processing completes.
+Exit status `0` means success, `1` runtime or output failure, `2` invalid usage
+or input, and native comparison may return `3` for differences. See the
+[output contract](integrations/output-files.md) and [subprocess contract](integrations/subprocess.md).

docs/config.md

@@ -1,88 +1,105 @@
 # Audita Configuration
 
-This reference describes the version-2 configuration loader in `internal/core/config`.
-Use the maintained [local](../examples/minimal-config.yml) and
-[service](../examples/production-config.yml) examples with their PromptKit
-[profiles](../examples/profiles/) and optional [testing overlay](../examples/overlays/testing.yml).
-Choose real models for your endpoint; a testing profile makes no cost or quality
-guarantee. See the [migration guide](migrations/v2.md) for retired inputs.
+Audita uses version 3 application configuration. See the [migration guide](migrations/v3.md)
+and [examples](../examples/) for complete projects. Command syntax is owned by
+[the CLI reference](cli.md).
 
-## Loading and precedence
+## Loading and composition
 
-The application selects one main YAML file: an explicit `--config`, then
-`/usr/local/etc/audita/config.yml` if present, then `/etc/audita/config.yml`
-if present. Missing system candidates are skipped; an explicit missing or empty
-path, inaccessible selected file, or absence of any selected file is an error.
-`config validate` requires an explicit file. ConfigKit loads built-in defaults,
-the selected file, an optional named overlay from `overlays/<name>.yml` beside the
-main file, and only explicitly supplied setting overrides, in that order. Imports
-and secret-directory bootstrap are disabled. Unknown fields and missing, null,
-or non-integer `version: 2` are errors. Version-1 files require migration; no
-compatibility loader or implicit environment configuration remains.
+An explicit `--config` selects one main YAML file. Without it, ConfigKit searches
+the working directory, user configuration directory, and Unix system directories
+for `audita` configuration. If no file is found, built-in defaults apply. An
+explicit invalid selection or failure of a selected file is an error; search does
+not continue after a selected file fails. An omitted version uses the v3 schema;
+a supplied version must be `3`.
 
-Validation runs after overlays, explicit overrides, and derived settings have
-resolved. An override can therefore repair an invalid lower-precedence setting
-when that setting can be decoded. ConfigKit retains field origins and derivations
-for effective-configuration inspection. Its effective YAML redacts resolved
-credentials.
+Operator sources may use ConfigKit imports. The selected main file provides the
+base for an optional `overlays/<name>.yml`, optional `glossary.yml`, and recursive
+`glossary/` YAML files. Without a main source, automatic companion files are not
+loaded from the working directory. ConfigKit composes sources, resolves native
+inheritance, applies explicit overrides, records derived defaults, and validates
+the result. Its [configuration reference](https://forge.maximumdirect.net/base-layer/configkit/src/tag/v1.2.0/docs/config.md)
+owns native composition and provenance semantics.
 
-Profile files are resolved against the selected main file's directory, or may
-use an absolute `profiles_dir`. Both selected profiles must exist and select a
-registered backend. Their effective endpoints must match that backend's endpoint
-after surrounding whitespace and trailing slashes are removed. Profiles cannot
-supply a competing `api_key_env` lookup. The backend credential supplies the
-runtime key when required; inspection makes no provider call. The
-[CLI inspection views](cli.md#streams-and-exit-status) show selected controls and
-field provenance separately from ConfigKit's redacted settings YAML.
+### PromptKit profiles and operator prompts
+
+PromptKit loads its default catalog and Audita's embedded prompts, followed by
+optional `prompts.yml` and recursive `prompts/` YAML files beside the application
+main. Native imports, resource collections, inheritance, and replacement apply.
+Profiles, backends, models, credentials, admission, and provider parameters belong
+to PromptKit configuration; see its [format reference](https://forge.maximumdirect.net/base-layer/promptkit/src/tag/v0.21.0/docs/formats.md).
+The engine captures its sources for an invocation. Edit files and run a new
+invocation to pick up changes. Inspection does not require model credentials.
+
+## Pipeline and glossary selections
+
+`glossary_collections` maps names to collections with an ordered `entries` list.
+Each entry has an `id`, `name`, and `category`; `description`, `aliases`, and
+`plural` provide optional context. Entries are identified within their collection
+by `id`. Root `glossaries` and `protected_terms` select collection names. If root
+protection is omitted, it derives from the root glossary selection.
+
+`pipeline.stages` is an ordered list of `module` records; supported modules are
+`glossary`, `homophones`, `spoken_word`, and `grammar`. The default sequence is
+`glossary`, `homophones`, `glossary`, `spoken_word`, `grammar`. Repeated modules
+run separately; `[]` runs normalization without model processing. An optional
+nonempty, unique `id` identifies a record in evidence. Each record may override
+`glossaries`, `protected_terms`, `confidence_threshold`, and fields under `llm`,
+`validation`, and `context`. Omitted fields inherit their resolved root values.
+Explicit empty lists and null list selections clear a selection.
+
+Each entry receives its selected context and independent protection. Glossary
+correction exempts active recognized spellings from protection for that entry.
+A longer exempt name still takes precedence over a shorter protected spelling
+inside it. A glossary correction must have at least one selected entry at
+processing preflight. Empty definitions and empty protection remain valid
+configuration.
 
 ## Settings
 
-| Field | Default | Rule |
+| Setting | Default | Meaning |
 | --- | --- | --- |
-| `profiles_dir` | `profiles` | Nonempty; profile files are resolved relative to the selected main file. |
-| `backends.<id>.endpoint` | None | Required nonempty endpoint for each backend. At least one backend is required. |
-| `backends.<id>.concurrency` | `1` | Positive finite capacity; shared by both roles using that backend. |
-| `backends.<id>.queue_capacity` | `1024` | Nonnegative; zero disables waiting admission. |
-| `backends.<id>.credential` | Unset | Optional environment-variable secret reference; omission or null means unauthenticated use. |
-| `llm.proposal_profile` | None | Required nonempty profile ID. |
-| `llm.validation_profile` | Final proposal profile | Omission inherits the final proposal selection; explicit empty or null fails. |
-| `llm.transient_retries` | `2` | Nonnegative additional attempts per generation. |
-| `llm.repair_attempts` | `2` | Additional structural repair generations, from zero through three. |
-| `llm.operation_timeout` | `15m` | Positive Go duration string per logical call. |
-| `pipeline.modules` | `[glossary, homophones, glossary, spoken_word, grammar]` | Ordered module keys; repeats are meaningful and an explicit empty list runs no correction modules. |
-| `output.schema` | `bare-segments` | `bare-segments` or `audita-v1`. See [output formats](integrations/output-files.md). |
+| `llm.proposal_profile` | unset | PromptKit profile for proposals; required for processing entries. |
+| `llm.validation_profile` | effective proposal profile | Profile for model validation; null clears a selection before fallback. |
+| `llm.correction_repair_profile` | effective proposal profile | Profile for correction repair; null clears an inherited selection before fallback. |
+| `llm.correction_repair_attempts` | `1` | Nonnegative repair attempts per correction; zero disables correction repair. |
+| `llm.transient_retries` | `2` | Additional transient attempts per generation. |
+| `llm.repair_attempts` | `2` | Structural repairs, from zero through three. |
+| `llm.operation_timeout` | `15m` | Positive duration per logical operation. |
 | `validation.max_prompt_tokens` | `2048` | Positive validation batching budget. |
-| `chunking.target_sections` | Unset | Optional positive target; omission or null selects automatic chunking. |
-| `chunking.max_section_tokens` | `8192` | Positive maximum estimate. |
-| `chunking.min_section_tokens` | `2048` | Positive and no greater than maximum. |
-| `normalization.max_segment_gap` | `4.0` | Nonnegative numeric seconds. |
-| `normalization.ellipsis_gap` | `3.5` | Nonnegative numeric seconds. |
-| `normalization.max_segment_duration` | `60.0` | Positive numeric seconds. |
-| `normalization.max_segment_tokens` | `2048` | Positive token estimate. |
-| `thresholds.glossary`, `.homophones`, `.spoken_word`, `.grammar` | `0.8` each | Confidence thresholds in `[0, 1]`. |
-| `context.description` | Empty | Trimmed prompt context, at most 500 bytes. |
-| `reporting.enabled` | `true` | Write the ordinary three-file report bundle when processing. |
-| `reporting.stdout_dir` | `.` | Report directory for stdout transcript output; ignored for file output or disabled reporting. |
-| `diagnostics.debug` | `false` | Persist detailed debug artifacts when processing. |
-| `diagnostics.work_dir` | `/tmp/audita` | Parent of the retained debug run directory; required only when debug is enabled. |
+| `thresholds.<module>` | `0.8` | Root confidence threshold for each module, in `[0, 1]`. |
+| `context.description` | empty | Prompt context; at most 500 bytes after trimming. |
+| `chunking.target_sections` | unset | Optional positive target. |
+| `chunking.max_section_tokens`, `chunking.min_section_tokens` | `8192`, `2048` | Positive section bounds; minimum must not exceed maximum. |
+| `normalization.max_segment_gap`, `normalization.ellipsis_gap` | `4`, `3.5` | Nonnegative seconds. |
+| `normalization.max_segment_duration`, `normalization.max_segment_tokens` | `60`, `2048` | Positive seconds and token estimate. |
+| `output.schema` | `bare-segments` | Output format; see [output contracts](integrations/output-files.md). |
+| `reporting.enabled`, `reporting.stdout_dir` | `true`, `.` | Ordinary report capture and default directory for stdout output. |
+| `diagnostics.work_dir` | `/tmp/audita` | Parent directory for optional debug capture. |
 
-Module keys select correction modules; validator chains remain built into them.
-The loader preserves module order and repetitions. Normalization time settings
-accept numeric seconds only. The operation timeout uses a duration string.
-`reporting.stdout_dir` must be nonblank only for reporting-enabled stdout runs;
-`diagnostics.work_dir` must be nonblank only with debug enabled. These path
-requirements are checked when choosing process destinations, not during
-configuration inspection.
+For example, an entry can disable correction repair or select another profile:
 
-## Credentials
+```yaml
+llm:
+  proposal_profile: local
+  correction_repair_attempts: 2
+pipeline:
+  stages:
+    - module: grammar
+      llm:
+        correction_repair_profile: review
+    - module: spoken_word
+      llm:
+        correction_repair_attempts: 0
+```
 
-A backend credential is a ConfigKit secret reference containing an environment
-variable name, such as `credential: AUDITA_SERVICE_KEY`. Every reference that
-survives overlay and override resolution must name a set, nonempty variable,
-including credentials on backends unused by the selected roles. A replacement
-reference resolves only the replacement; null removes the reference. General
-`AUDITA_*` and `OPENROUTER_API_KEY` variables have no implicit setting effect.
-Secret values are available to the runtime through the resolved reference, while
-ConfigKit's effective output and provenance contain no resolved secret values.
-
-Current invocation syntax belongs in [CLI](cli.md).
+Processing profiles are selected explicitly; no profile or glossary is selected
+automatically. The validation selection falls back after root and per-entry
+settings are combined. An explicit root correction repair profile is inherited
+by each entry unless overridden or cleared with null; otherwise the entry uses
+its effective proposal profile. The repair profile is checked only when its
+attempt budget is positive. Each correction repair attempt is a logical call
+that can also use the configured transient retries and structural repairs. Null
+does not disable validation. Numeric zero and false
+retain their field meaning, subject to validation. Inspect recorded origins and
+default dependencies using the [native commands](cli.md).

docs/development.md

@@ -7,9 +7,8 @@ Audita is a Go CLI for transcript polishing. Start with the
 ## Before Changing the Repository
 
 Coding agents must read and follow the [agent policy](policy/agents.md) before
-recommending, planning, or implementing changes. Read the
-[architecture policy](policy/architecture.md) for boundaries and invariants,
-then use the task guide below rather than reading every reference indiscriminately.
+recommending, planning, or implementing changes. Use the policy reading guide
+below to select the policies applicable to the task.
 
 Confirm the requested scope and behavior contract, make focused changes in the
 owning component, and update the relevant tests and canonical documentation
@@ -18,9 +17,33 @@ sufficiency; the [documentation policy](policy/documentation.md) governs content
 ownership. Commit discipline and agent Git restrictions are in the
 [agent policy](policy/agents.md#git-commit-policy).
 
+## 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.
+
 ## Baseline Validation
 
-Use Go 1.25.5 or newer. From the repository root:
+Use Go 1.27.0 or newer for source builds. The selected release toolchain is
+documented in the [release procedure](release.md#prerequisites). From the
+repository root:
 
 ```sh
 go build -o ./bin/audita ./cmd/audita

docs/integrations/openai-compatible-llm.md

@@ -1,26 +1,26 @@
 # OpenAI-Compatible LLM Integration
 
-Audita uses the pinned [PromptKit](https://gitea.maximumdirect.net/eric/promptkit)
+Audita uses the pinned [PromptKit](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/171fb11f4e967a1da3af57843c6467954b14ba09)
 built-in OpenAI-compatible transport. PromptKit owns chat-completions wire framing,
 provider envelope parsing, transient retries, per-generation timeouts, and JSON
 Schema repair. A backend's configured base endpoint must support the selected
 profile's model and structured JSON-schema responses; local configuration
 inspection does not contact the provider.
 
-Audita selects a role profile, supplies its registered backend credential, and
-passes the embedded response schema as a complete per-call output contract. It
-prepares each call once, checks that the prepared target still matches the
-inspected backend and endpoint, then executes that same prepared request. A
-profile cannot introduce a separate credential environment lookup. An absent
-backend credential permits an unauthenticated local service.
+Audita selects role profiles independently for each pipeline entry and supplies
+its domain response schema and per-operation budget. PromptKit owns backend and
+credential selection, request preparation, transport, retries, repairs, and
+admission. Audita executes the same prepared handle and retains its own domain
+validation. Profiles may use native endpoint and credential settings; local
+inspection does not resolve a credential value or call the provider.
 
 `llm.transient_retries` counts additional attempts for eligible transient
 failures; explicit zero makes one attempt. `llm.repair_attempts` counts
 additional generations for schema-invalid model output. The operation timeout
 covers preparation, capacity waiting, retries, generation, and repair. Caller
 cancellation or an earlier deadline also applies. See [configuration](../config.md#settings)
-for defaults and [PromptKit's consumer contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md)
-for the pinned protocol and retry details.
+for defaults and the [PromptKit consumer contract](https://forge.maximumdirect.net/base-layer/promptkit/src/tag/v0.21.0/docs/consumers/pkg-promptkit.md)
+for protocol and retry details.
 
 A model operation that exhausts structural repair, a live-parent local operation
 timeout, capacity rejection, transport failure, malformed provider response,
@@ -31,4 +31,4 @@ continue. Caller cancellation, broken assets or configuration, and unknown
 internal failures remain fatal and cancel peers. Audita decodes into domain
 types only after PromptKit validates the JSON. Ordinary reports use safe reason
 codes and counts rather than provider messages. Full request/response content
-is written only with `--debug`; see [operations](../operations.md#diagnostics-directory).
+is written only with `--debug`; see [operations](../operations.md#debug-evidence).

docs/integrations/output-files.md

@@ -5,7 +5,7 @@
 The corrected transcript uses the selected `output.schema`: `bare-segments`
 or `audita-v1`. Its schema and text rules are unchanged by resilience
 reporting. See [configuration](../config.md#settings) for selection and
-[operations](../operations.md#required-output-files) for placement and writes.
+[operations](../operations.md#outputs-and-lifecycle) for placement and writes.
 
 With reporting enabled, Audita produces three ordinary files:
 
@@ -46,9 +46,9 @@ remain in opt-in debug files.
 ## Error and Recovery Records
 
 An `errors` record with `scope: work_unit` identifies zero-based `stage_index`
-and `chunk_index`, module key/instance, initial segment range, applied-correction
+and `chunk_index`, optional `stage_id`, module key/instance, initial segment range, applied-correction
 count, and a `failures` sequence. Each failure identifies the operation
-(`proposal`, `validation`, or `validation_input`), optional validator and
+(`proposal`, `validation`, `validation_input`, or `correction_repair`), optional validator and
 zero-based batch index, safe reason/message, sorted proposal indices when
 known, and execution counts when available. Multiple failed batches in one
 work unit form one error record. `scope: run` instead records phase, safe reason
@@ -59,11 +59,15 @@ For `validation_decisions_invalid`, proposal indices identify only candidates
 whose required decisions were unavailable. Other candidates in the same batch
 may still be approved or rejected normally.
 
-Each recovery identifies its work unit and successful operation, with sorted
+Each recovery identifies its work unit, optional `stage_id`, and successful operation, with sorted
 `reasons`, a safe message, available execution counts, and sorted
 `filtered_proposals` details. One recovery can contain `output_repaired`,
-`service_recovered`, and `proposals_filtered` together. Filtering covers
-defective response proposals; low confidence, protected-term rejection,
+`service_recovered`, `correction_revised`, and `proposals_filtered` together.
+`correction_revised` means a repair yielded a fully validated revision; its
+application outcome is recorded in the Markdown report. Filtering covers
+defective proposals and revisions under their originating operation. Only
+original proposal operations count toward `proposal_responses_with_filtering`.
+Low confidence, protected-term rejection,
 ordinary editorial rejection, and an apply-time conflict caused by an earlier
 accepted correction are not filtering recoveries. Failed operations are errors,
 not recoveries. The initial chunk identity remains stable even if earlier
@@ -79,23 +83,29 @@ is an error even when unexpected indices were also ignored.
 `report.md` includes run ID, status, corrections, work coverage, error and
 recovery totals, input/output paths, and full work-unit error and recovery
 matrices. Rows show every initial chunk with 1-based chunk number and initial
-segment range; columns follow configured module-instance order, including
-repeats. Completed error cells are `0` or `1`; recovery cells are operation
+segment range; columns follow configured pipeline order, including repeated modules. Labels show
+the one-based position and module, plus the operator ID when supplied. Completed error cells are `0` or `1`; recovery cells are operation
 counts. `—` means not started and `n*` means interrupted with n facts recorded.
 An empty stage or chunk set is identified as having no work units. Short reason breakdowns count
 records containing each reason; a recovery can have several reasons, so those
-counts need not sum to the recovery total. The report refers to both YAML
-files. It does not include transcript excerpts or correction lists.
+counts need not sum to the recovery total. When a repair was attempted, a
+Correction repair table lists its stage, chunk,
+original proposal index, semantic attempt count, and final outcome (`applied`,
+`approved_skipped`, `withdrawn`, `rejected`, `exhausted`, `unavailable`, or
+`interrupted`). The report refers to both YAML files. It does not include
+transcript excerpts or correction lists.
 
 ## Debug-Only Files
 
 With `--debug`, `correction-ledger.json` contains proposed candidates and
 their application, rejection, or interruption details. `llm-execution.json`
-holds logical calls and PromptKit execution events; `utilization-diagnostics.json`
-groups backend capacity and timing observations while preserving known and
-complete usage semantics. Interaction request/response artifacts, selected
-profiles, configuration provenance, and input snapshots are also debug-only.
+holds logical calls and PromptKit execution events. Interaction request/response
+artifacts and input snapshots are also debug-only. Records carry zero-based
+`stage_index` and optional `stage_id` where an entry is identified.
 These files are diagnostic evidence, not an alternate ordinary report schema.
+For a repaired proposal, one ledger row preserves the original proposed edit,
+the final applied segment and span when applicable, and repair attempts with
+revision decisions and interaction artifact paths.
 Each candidate-backed ledger entry includes `proposed_corrected_text`, the
 literal replacement span, even when it is `""` for a deletion. Applied entries
 also include `applied_corrected_text`, likewise `""` for an applied deletion.

docs/integrations/subprocess.md

@@ -6,14 +6,17 @@ The [CLI reference](../cli.md) owns command syntax, streams, and exit semantics;
 
 ## Invocation
 
-Use an argument array with the transcript path and required glossary argument,
-following the [process examples](../cli.md#commands-and-help). For machine workflows,
+Use an argument array with the transcript path and configured glossary selections,
+following the [process examples](../cli.md#processing). For machine workflows,
 select an explicit transcript file destination and a configuration path. Reports
-then go beside the transcript. For stdout output, select `--report-dir` or use
-the invocation working directory. Debug is independent and off by default.
-Supplying a configuration path also
-makes file selection predictable; only explicitly referenced credential variables
-are read from the environment.
+go beside the transcript unless an explicit `--report-dir` selects another
+directory. For stdout output, reports use the effective `reporting.stdout_dir`
+(defaulting to the invocation working directory), including a `--report-dir`
+override. A config-file or overlay value for `reporting.stdout_dir` alone does
+not redirect file-output reports. `--work-dir` selects a debug root, while
+`--debug` enables capture; the path flag alone does not.
+Supplying a configuration path also makes file selection predictable; only
+explicitly referenced credential variables are read from the environment.
 
 Resolve the executable deliberately and set the child's working directory so
 relative input/output paths and reported artifact paths have a known base.
@@ -23,18 +26,20 @@ or cancellation in the parent process when needed.
 ## Result Handling
 
 Interpret the exit result according to the
-[CLI output and exit contract](../cli.md#streams-and-exit-status).
+[CLI output and exit contract](../cli.md#inspection-and-outcomes).
 Consume transcript/report data through the
 [output-file contract](output-files.md), and treat stderr as human-readable detail.
-The three reports may be absent after early configuration or destination
-failures. After initialization, failed reports can describe invalid input or
-partial processing. Exit `0` can include recoverable model errors and applied
+Audita loads configuration and parses the input transcript before report
+initialization. Early destination failures can also leave no reports. After
+initialization, failed reports can describe partial processing or output
+failures and use the same report directory as successful runs.
+Exit `0` can include recoverable model errors and applied
 corrections; inspect `errors.yml` and `recoveries.yml` for those outcomes. A
 transcript may have been written before a later required report failure, so
 the file alone does not prove completion.
 
 If processing fails, preserve available evidence and follow
-[operations recovery](../operations.md#failure-inspection-and-recovery).
+[operations recovery](../operations.md#recovery).
 Ordinary reports are independent of optional retained debug evidence. Parent
 cancellation reaches the child through its context; Audita joins workers and
 attempts failed-status report finalization before exiting. Uncatchable
@@ -45,4 +50,4 @@ file nor a debug directory alone establishes successful completion.
 
 - [Transcript and glossary inputs](transcript-glossary-files.md)
 - [LLM endpoint compatibility](openai-compatible-llm.md)
-- [Configuration inspection commands](../cli.md#commands-and-help)
+- [Configuration inspection commands](../cli.md#inspection-and-outcomes)

docs/integrations/transcript-glossary-files.md

@@ -28,23 +28,11 @@ The [tiny transcript](../../examples/tiny-transcript.json) is a complete copyabl
 input. Invalid JSON, unsupported top-level shapes, empty transcripts, invalid field
 types, duplicate supplied IDs, and the validation failures above are rejected.
 
-## Glossary YAML Contract
+## Glossary collections
 
-The top-level object contains a `glossary` list with at least one entry.
-
-| Entry field | Type and validation |
-| --- | --- |
-| `name` | Non-empty string |
-| `category` | Non-empty string |
-| `summary` | Non-empty string |
-| `aliases` | Optional list of non-empty strings |
-| `plural` | Optional string |
-
-The parser checks empty strings without trimming them. Unknown YAML fields are
-ignored by the glossary parser, unlike the stricter
-[configuration-file schema](../config.md#loading-and-precedence).
-
-The [tiny glossary](../../examples/tiny-glossary.yaml) is a complete copyable input.
-Malformed YAML, an empty/missing glossary, invalid shapes, missing required text,
-and empty aliases are rejected. These formats describe input acceptance, not
-additional vocabulary restrictions.
+Glossary definitions are composed as application configuration, including the
+optional companion inputs described by the [configuration reference](../config.md).
+The [local example](../../examples/local/glossary.yml) provides a complete
+collection. Configuration may contain empty collections; processing preflight
+requires every glossary-correction entry to select at least one glossary entry.
+The previous standalone `glossary` file format is not a processing input.

docs/internal/cli-config.md

@@ -9,7 +9,7 @@ CLI wiring, and maintained examples. Definitions of behavior belong to the
 1. Update fields, defaults, loading, and validation in `internal/core/config`.
 2. Update file, selected overlay, credential reference, and CLI mapping as
    applicable. Preserve the precedence defined in the
-   [configuration contract](../config.md#loading-and-precedence), including the
+   [configuration contract](../config.md#loading-and-composition), including the
    distinct validation and effective-config commands.
 3. Update redaction when secrets are involved.
 4. Review configuration tests and related CLI tests for precedence, validation,
@@ -27,23 +27,20 @@ CLI wiring, and maintained examples. Definitions of behavior belong to the
    for the changed behavior.
 4. Update the CLI reference and affected integration guidance.
 
+The `version` route uses ReleaseKit's public `buildinfo.Version()` accessor and
+stays independent of application runtime assembly. Preserve its behavior from
+the [CLI contract](../cli.md) when changing the command; the
+adoption decision is recorded in [ADR 0001](../adr/0001-releasekit.md).
+
 ## Validating Examples
 
 Keep complete copyable files in [examples](../../examples/) and link to them from
 their canonical contract documentation. Keep them valid and secret-free.
-From the repository root, validate the maintained configuration examples:
-
-```sh
-go run ./cmd/audita config validate --config examples/minimal-config.yml
-AUDITA_SERVICE_KEY=synthetic-example go run ./cmd/audita config validate --config examples/production-config.yml
-AUDITA_SERVICE_KEY=synthetic-example go run ./cmd/audita config validate --config examples/production-config.yml --overlay testing
-go run ./cmd/audita config print-effective --config examples/minimal-config.yml --view profiles
-```
-
-Only referenced credentials read environment values; use a controlled synthetic
-value when validating the service example. Check affected CLI examples against the
-parser and use schema tests for maintained transcript/glossary inputs. Example
-validation should not invoke a live LLM merely to check documentation.
+Run the commands in the [example guide](../../examples/README.md) from each
+project's directory. `internal/cli/examples_integration_test.go` exercises the
+maintained projects with a controlled provider, and the preview fixture can be
+prepared without inference. Review automatic companion sources and overlays in
+their actual project directories. Keep service credentials synthetic in tests.
 
 ## Runtime Change Checks
 

docs/internal/diagnostics-reporting.md

@@ -24,36 +24,29 @@ retain their execution counts and never produce a recovery record.
 `internal/core/diagnostics.OutputSession` owns active destination checks,
 transcript preflight, report initialization, regular-file replacement, and direct
 stream publication. Transcript input is protected from early report writes but
-may be the final transcript destination. The LLM runtime records successful reads
-through PromptKit's profile filesystem and supplies those source paths to CLI;
+may be the final transcript destination. The LLM runtime records consumed PromptKit sources and effective host message
+files and supplies those source paths to CLI;
 no second filename-based discovery rule is used.
-CLI composes it after configuration/profile inspection and before reading
-inputs or dispatching model work. It does not create ordinary report parents.
+CLI composes it after configuration, transcript acquisition, and preflight
+readiness and before dispatching model work. It does not create ordinary report parents.
 On a final write error it attempts other enabled reports and one failed-status
 pass; a published transcript is never erased by a later report failure.
 
-Debug is independent. Only `diagnostics.debug` creates a unique retained child
+Debug is independent. The shared `--debug` flag enables a unique retained child
 under `diagnostics.work_dir`. CLI passes empty diagnostics paths and nil writers
-when debug is off. With debug on, source/normalized snapshots, invocation,
-effective settings, origins, profiles, initial chunk summary, correction ledger,
-indexed execution/utilization, and model interactions are written. Runner
-candidate capture includes proposals later rejected or interrupted. Ledger
-mapping uses optional string pointers so an empty proposed replacement is
-serialized for every candidate and an empty applied replacement appears only
-when that candidate applied; see the [public artifact contract](../integrations/output-files.md#debug-only-files).
-Debug write failures reach the CLI through an explicit concurrency-safe diagnostic
-callback and produce redacted stderr messages without aborting processing.
-Completed validator decisions returned with a fatal batch error remain available
-to the debug ledger; they never authorize applying an incompletely validated edit.
-Runner decision records carry the validator's explicit approved, rejected, or
-unavailable disposition into the ledger. Unavailable candidates have a distinct
-top-level ledger disposition, while fatal interruptions remain interrupted when
-no rejection or unavailable decision was returned. Successful validation
-interaction payloads contain the full decoded response, final content, and
-reconciliation outcomes; ignored indices do not become ledger candidates.
-Every debug writer uses all configured backend secrets for redaction, including
-unselected backend credentials and source snapshots. Debug can still contain
-sensitive transcript and prompt content.
+when debug is off. With debug enabled, it captures source and normalized
+snapshots, invocation, effective settings, correction ledger, LLM execution
+observations, and model interactions. Candidate capture includes proposals later
+rejected or interrupted. Repair and revalidation artifacts use section, proposal,
+attempt, validator, and batch coordinates as applicable; their retained content
+is redacted using the selected role credentials. Ledger mapping preserves empty proposed and applied
+replacements and distinguishes unavailable candidates from interrupted work.
+
+A concurrency-safe diagnostic callback reports optional write failures without
+aborting processing. Diagnostic redaction uses credential source metadata; debug
+artifacts can still contain sensitive transcript and prompt content. Execution
+position and optional operator ID are carried separately from generated safe
+artifact path coordinates.
 
 ## Key Tests
 

docs/internal/llm-runtime.md

@@ -1,39 +1,30 @@
 # Audita LLM Runtime
 
-## Client Boundary
+`llm.NewRuntime` assembles one captured PromptKit engine using its default
+catalog, Audita's embedded prompts and schemas, and optional operator sources
+anchored to the recorded application main context. Captured host sources and
+message files are passed to output collision checks. An embedded-only diagnostic
+construction distinguishes shipped asset failures from operator-source failures;
+it never replaces the requested engine.
 
-`llm.NewRuntime` assembles one PromptKit engine for both roles. It loads embedded
-prompt and schema assets, registers application backends, and inspects the
-selected proposal and validation profiles offline. A role-bound `llm.RoleClient`
-implements `structuredoutput.Client`; proposal and validator contracts alias that
-interface. Both roles share engine-local backend capacity.
+Each resolved pipeline entry receives role-bound clients with its selected
+profiles and effective budgets. Clients share engine-local backend admission.
+The adapter uses `PrepareExecution` and `RunPrepared` on the same handle, passes
+Audita's per-call schema and repair budget, and decodes only validated results.
+PromptKit owns backend and credential selection. The adapter uses captured
+credential source names for artifact redaction without inspecting unrelated
+environment values. See the [integration contract](../integrations/openai-compatible-llm.md)
+for failure behavior and the [configuration reference](../config.md) for sources.
 
-For each logical call, the adapter starts an operation context and a diagnostic
-record before preparation. It supplies the reserved hardening text, the selected
-profile and resolved backend credential, and the complete embedded schema/repair
-contract. `PrepareExecution` produces the exact messages and hashes retained in
-an Audita snapshot. The adapter checks the prepared backend and endpoint before
-`RunPrepared`. It records available final content, usage, model, and profile
-metadata and decodes only a validated result. Call hooks expose logical
-start/finish records and PromptKit execution events for debug utilization.
+When correction repair is enabled, the proposal call retains its prompt,
+effective variables, prepared messages, and full final response for section-local
+replay. The adapter renders the repair definition with the selected profile,
+appends only that branch’s history, and checks the original prepared prefix
+before execution. The complete conversation is sent to the selected provider;
+provider rejection ends that branch as unavailable. The requested repair
+definition is retained in call attribution alongside native base-prompt metadata.
 
-The [integration contract](../integrations/openai-compatible-llm.md) describes
-wire ownership and failure behavior. `structuredoutput.Failure` has a safe
-message, fixed reason code, typed cause, and recoverable/fatal/canceled class.
-Counts distinguish provider attempts, transient retries, and structural
-repairs, including on errors. Secrets from all configured backends, including unselected
-ones, are available to the diagnostics redaction boundary.
-
-## Orchestration
-
-CLI processing supplies two role clients from the same engine to the runner.
-PromptKit's per-backend admission applies to both roles and every generation,
-retry, and repair. The runner still processes module instances in order,
-collects concurrent section work deterministically, and cancels remaining
-section work only on fatal failures. `llm.DiagnosticsWriter` remains the protected
-request/response artifact writer. `llm.ObservationCollector` captures metadata
-events under a short mutex and freezes them after runner work joins. Its logical
-records include preparation failures; summary usage comes from terminal events
-once per call and retains knownness and completeness for each field. Runner wall
-and validator timings remain separate from provider attempts. Ordinary reports
-derive compact runner outcomes; full observations are debug-only.
+The observation collector tracks logical calls and execution events. Ordinary
+reports use compact safe outcomes; request and response evidence is optional
+debug material. The runner preserves ordered pipeline traversal and deterministic
+section collection while canceling and joining peers on fatal errors.

docs/internal/modules.md

@@ -13,6 +13,9 @@ Modules implement `contracts.TranscriptModule`:
 - `Validators()`
 - `Propose(ctx, req)`
 
+Built-in modules also expose `RepairPromptID()` for the runner to select their
+repair definitions; proposal-only callers retain the existing interface.
+
 Runner resolves configured module specs to module instances through `internal/framework/modules`.
 
 ## Built-In Modules
@@ -37,9 +40,9 @@ Shared proposal-generation plumbing is centralized in:
 Module packages own:
 - prompt selection (`internal/prompts` prompt IDs).
 
-`proposal_generation.BuildProposalVariables` encodes the glossary, selected
-transcript section, and trimmed description once for all four modules. PromptKit
-renders their embedded definitions from those variables and validates the
+Each stage prepares the encoded glossary context and protected spellings once.
+Proposal generation adds the selected transcript section and trimmed description
+for each request. PromptKit renders the selected definition and validates the
 correction-set schema before Audita maps proposals. Domain validators still
 check confidence, applicability, protected glossary terms, and replacement
 policy. Model-facing segment IDs are one-based positions within the proposal
@@ -61,6 +64,10 @@ Module packages call the built-in chain resolver at construction.
 
 ## Failure and Outcome Behavior
 
+Each actionable rejection can be revised or withdrawn within its original
+section. A revision retains the original proposal identity and must pass the
+full validator chain before application.
+
 Module construction failures are fatal. Recoverable proposal model failures
 record an unsuccessful operation and yield no candidates for that section;
 other sections and module instances continue. Fatal adapter or application
@@ -88,4 +95,4 @@ outcomes are defined by the [report contract](../integrations/output-files.md).
 - `internal/modules/*/module_test.go`
 - `internal/framework/modules/registry_test.go`
 - `internal/framework/proposal_generation/*_test.go`
-- `internal/cli/run_test.go` (pipeline/report integration)
+- `internal/cli/process_ordered_integration_test.go` (pipeline/report integration)

docs/internal/output-schemas.md

@@ -12,7 +12,7 @@ selectable values and defaults belong to
 
 Configuration validation checks registry support. CLI orchestration resolves the
 selected encoder, passes the final transcript to it, and routes the encoded bytes
-to the destination defined by the [CLI contract](../cli.md#streams-and-exit-status).
+to the destination defined by the [CLI contract](../cli.md#inspection-and-outcomes).
 An unsupported key fails validation or resolution rather than selecting an
 implicit fallback.
 

docs/internal/overview.md

@@ -14,6 +14,7 @@ Executable and command orchestration:
 
 Core deterministic components:
 - `internal/core/config`
+- `internal/core/glossary`
 - `internal/core/schema`
 - `internal/core/normalization`
 - `internal/core/chunking`
@@ -24,6 +25,7 @@ Core deterministic components:
 
 Framework orchestration and contracts:
 - `internal/framework/contracts`
+- `internal/framework/preflight`
 - `internal/framework/modules`
 - `internal/framework/proposal_generation`
 - `internal/framework/proposals`
@@ -66,7 +68,7 @@ artifact lifecycle.
 ## Component Responsibilities
 
 Core components implement configuration defaults/loading/validation/redaction,
-transcript and glossary schemas, normalization and chunking, output encoding,
+transcript schemas and derived glossary views, normalization and chunking, output encoding,
 diagnostics artifact helpers, and public report structures.
 
 Framework components implement module and validator contracts, proposal

docs/internal/pipeline.md

@@ -4,8 +4,9 @@ The [input contract](../integrations/transcript-glossary-files.md) owns input
 formats; [configuration](../config.md) owns settings; the
 [output contract](../integrations/output-files.md) owns serialized results.
 
-1. CLI filesystem adapters read transcript and glossary files. Schema parsing
-   produces source objects; transcript segments enter canonical normalization.
+1. CLI loads resolved configuration and transcript input. Preflight checks all
+   selected glossary views and roles before the output session prepares resources.
+   Transcript segments then enter canonical normalization.
 2. Normalization sorts and merges segments using configured time and token
    limits, reassigning IDs where needed.
 3. The runner partitions the normalized transcript exactly once before its
@@ -18,10 +19,14 @@ formats; [configuration](../config.md) owns settings; the
    may preserve a checked subset of completed decisions as diagnostic evidence.
    Recoverable failed batches mark their candidates unavailable; successful
    survivors continue through all required validators.
-6. Only fully approved proposals reach application. Corrections apply in
+6. Actionable rejections can enter independent section-local repair branches.
+   Each revision is mapped to the original section and revalidated from the
+   start. Withdrawal, exhaustion, and recoverable failures finish the branch
+   without affecting independent approvals.
+7. Only fully approved proposals reach application. Corrections apply in
    proposal-index order within their owning section. Existing replacement
    policies and apply-time safety checks resolve stale conflicts.
-7. CLI encodes the final transcript and publishes active files through the
+8. CLI encodes the final transcript and publishes active files through the
    output session. `framework/processreport` builds one snapshot for YAML,
    Markdown, and CLI totals. Debug evidence is captured separately when enabled.
 

docs/internal/prompts.md

@@ -1,28 +1,43 @@
 # Audita Prompt Registry
 
-`internal/prompts` embeds seven PromptKit YAML definitions under
-`assets/prompts`. The IDs and selected version remain:
+`internal/prompts` embeds eleven PromptKit definitions in the `audita`
+collection. The four proposal IDs are `audita/modules.glossary.proposal`,
+`audita/modules.homophones.proposal`, `audita/modules.spoken_word.proposal`,
+and `audita/modules.grammar.proposal`; the corresponding repair IDs replace
+`.proposal` with `.repair`. The three validator IDs are
+`audita/validators.spoken_form_plausibility`,
+`audita/validators.meaning_reversal_review`, and
+`audita/validators.editorial_review`.
 
-- `modules.glossary.proposal` (`v1`)
-- `modules.homophones.proposal` (`v1`)
-- `modules.spoken_word.proposal` (`v1`)
-- `modules.grammar.proposal` (`v1`)
-- `validators.spoken_form_plausibility` (`v1`)
-- `validators.meaning_reversal_review` (`v1`)
-- `validators.editorial_review` (`v1`)
+PromptKit composes embedded defaults with operator prompt sources. Shared
+instructions come from the embedded fragments in `assets/shared`; the request
+shared-variable helper fills absent `HardeningPolicy`, `ProposalContract`,
+`RepairContract`, and `ValidationContract` variables. The processing adapter
+supplies the embedded instruction fragments for those names. Processing supplies
+Audita's response-schema contract separately.
+The operator's prompt definition controls which variables its template uses.
+
+Proposal focus and validator acceptance intentionally differ: minor editorial
+cleanup may be accepted even when the proposing module was not asked to perform
+it. Follow the [architecture boundary](../policy/architecture.md#correction-and-concurrency-invariants)
+when maintaining proposal, validation, and repair instructions; the difference
+alone is not a reason to tighten validation. The testing rationale is recorded in
+[ADR 0003](../adr/0003-module-focus-and-editorial-acceptance.md).
+
+For a standard request preview or validation, select a native PromptKit profile
+and supply the template variables used by the selected prompt. The shipped
+proposal definitions use `TranscriptDescriptionBlock`, `GlossaryJSON`,
+`ProtectedTermsJSON`, and `SectionJSON`. Glossary entries provide context,
+and the separate spelling list defines protection. Preview defaults the
+spelling list to `[]` when omitted. The validator definitions use `TranscriptDescriptionBlock` and
+`PayloadJSON`. The latter is supplied candidate JSON and does not require a
+proposal inference call. Repair definitions use `RepairContract` and
+`RepairRequestJSON`, containing the original proposal reference, current
+correction, and ordered findings. An operator replacement may use different
+variables.
+See the [upstream CLI reference](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/f369d6a78253b6e6fcb1e023fb2e9c3af1d20ff0/docs/cli.md)
+for the standard preview, validation, and smoke commands.
 
-PromptKit reads the embedded definitions and renders their system and user
-messages from named string variables. The role-bound adapter supplies
-`HardeningPolicy` alongside `ProposalContract` and `ValidationContract` from
-embedded fragments under `assets/shared`, after caller variables so callers cannot replace those
-instructions. Common literal-span and identity guidance lives in the proposal
-fragment; shared candidate-reference, context, and confidence guidance lives in
-the validation fragment. Module-specific policies and examples remain in YAML.
-Proposal prompts receive the section JSON, glossary JSON where used, and transcript description block.
-Validator prompts receive the correction payload and description block.
-The prompt assets retain the prior task instructions and output-schema
-association. The role-bound runtime supplies the complete JSON Schema output contract
-and repair count; the definition does not own an operator-facing repair default.
 The correction-set schema requires a string replacement and accepts an empty
 string. Proposal guidance uses it for eligible span deletion and permits literal
 spacing edits; validator guidance evaluates the full before/after segment under
@@ -30,14 +45,14 @@ each validator's existing remit. A blank resulting segment remains a domain
 rejection, not a structural schema error.
 
 `internal/framework/responseschema` remains the only embedded source for
-`correction_set.v1.json` and `validator_decision_set.v1.json`. It exposes that
+`correction_set.v1.json`, `correction_repair.v1.json`, and
+`validator_decision_set.v1.json`. It exposes that
 filesystem to PromptKit and retains Audita's schema-key lookup. PromptKit's
 prepared execution supplies definition and rendered hashes; Audita does not
 recompute or promise equality with hashes from the removed template renderer.
-The small Audita registry records only prompt ID, version, source, and embedded
-path. Prepared runtime metadata belongs in diagnostics rather than the registry.
+The small Audita registry records only prompt ID, source, and embedded path. Prepared runtime metadata belongs in diagnostics rather than the registry.
 
-The structured-call contract carries prompt ID/version, string variables,
+The structured-call contract carries prompt ID, string variables,
 response-schema key, and logical-call attribution. Module and validator callers
 pass these values through the role-bound adapter. See the
 [LLM runtime](llm-runtime.md) for runtime assembly and

docs/internal/validators.md

@@ -46,6 +46,14 @@ For each module section:
 3. record decisions and compact operation outcomes;
 4. carry only approved proposals forward.
 
+When correction repair is enabled, the runner also gathers independent findings
+for rejected candidates when a validator has usable evidence. Unavailable
+assessments remain unavailable, and only candidates that pass every applicable
+check can advance. A known rejection can enter repair even when another
+assessment is unavailable; an unavailable assessment alone does not. Revised
+candidates run the applicable checks again. A zero repair budget retains the
+original shortlist flow.
+
 Decision cardinality is enforced inside Audita: each candidate proposal must
 receive exactly one outcome per validator it reaches. The runner still rejects
 duplicate, missing, or unknown identities in an internal validator result.
@@ -116,19 +124,21 @@ is covered by [report assembly](diagnostics-reporting.md).
 - `internal/validators/*_test.go`
 - `internal/framework/validators/*_test.go`
 - `internal/framework/processreport/correction_ledger_test.go`
-- `internal/cli/run_test.go`
+- `internal/cli/process_ordered_integration_test.go`
 
 ## Supplemental Validation Context
 
-Request construction prepares one segment-position lookup and protected vocabulary
-for all candidates. Glossary selection remains candidate-specific, including the
-proposed replacement text.
+Each stage prepares a context matcher and indexes its selected glossary entries
+by identity. Request construction uses a segment-position lookup and returns
+matched entries in selection order for each candidate, including matches in the
+replacement text. The deterministic guard and application check share the
+stage's separate protection matcher.
 
 Each candidate includes the immediately preceding and following source segments
 available within its fixed chunk, labeled `preceding` or `following` with speaker,
 text, and categories, plus glossary entries whose names, aliases, or
 recognized plurals appear in its original/resulting text or those neighbors.
-Glossary matching reuses the protected vocabulary; entries retain glossary order.
+Glossary matching uses the same recognition rules; entries retain selection order.
 Model-facing candidate and neighboring context omit internal segment IDs.
 This supplies evidence such as a troupe definition for a proposed `Jesters`
 correction or an adjacent speaker turn explaining deliberate repetition. A correction
@@ -140,7 +150,8 @@ payload token estimate. If one enriched item exceeds the configured limit, optio
 neighbors are removed from the end first, then glossary entries from the end,
 until it fits or only required candidate data remains. Required before/after text
 is never truncated. Existing oversized-candidate handling still applies if that
-required data does not fit. Context is supplemental, not a promise that every
+required data does not fit. The built-in estimator reuses encoded fragment
+counts for fitting and batching. Context is supplemental, not a promise that every
 relevant definition or neighboring utterance always fits. This uses the existing
 payload estimator, not a new guarantee about the provider's full context window.
 

docs/migrations/v2.md

@@ -2,8 +2,8 @@
 
 Audita v2 adopts ConfigKit for configuration and PromptKit for LLM execution.
 Version-1 configuration files, environment overlays, and retired flags are not
-accepted. Copy a maintained [local](../../examples/minimal-config.yml) or
-[service](../../examples/production-config.yml) example, then select real models
+accepted. Copy a maintained [local](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.1/examples/minimal-config.yml) or
+[service](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.1/examples/production-config.yml) example, then select real models
 in the accompanying `examples/profiles/` files. A testing overlay is shown at
 `examples/overlays/testing.yml`; its model choice carries no cost, speed, or
 quality guarantee.
@@ -122,7 +122,7 @@ capacity and usage fields retain known/complete flags. Debug runs write
 `effective-config.redacted.yaml`, `selected-profiles.yaml`,
 `config-origins.yaml`, `utilization-diagnostics.json`, and
 `llm-execution.json`. Request and response artifacts remain redacted debugging
-material. See [operations](../operations.md#diagnostics-directory) for placement
+material. See [operations](../operations.md#debug-evidence) for placement
 and paths, [configuration](../config.md) for all settings, and the
 [CLI reference](../cli.md) for current flags.
 

docs/migrations/v3.md

@@ -0,0 +1,27 @@
+# Migrating to application configuration v3
+
+Audita 3.1.x uses application configuration schema v2. For the cutover to schema
+v3, set `version: 3` in the application file and move glossary entries into
+configuration. Use the [configuration reference](../config.md) and
+[maintained examples](../../examples/) for the new formats.
+
+- Replace `pipeline.modules` with ordered `pipeline.stages` records containing
+  `module` and any per-entry overrides. An explicit empty list runs normalization.
+- Define named `glossary_collections` in configuration or its companion imports;
+  select them using `glossaries` and `protected_terms`. Rename each legacy
+  entry's `summary` to `description` to preserve its prompt context. Remove
+  `--glossary` and `--modules` from invocations.
+- Move profiles and backends out of the application configuration and retired
+  `profiles_dir` layout into PromptKit resources. Use its current list records,
+  IDs, credential sources, and backend admission settings. Select proposal and
+  validation profiles in application `llm` settings.
+- Use the shared `--debug` flag for capture; `diagnostics.work_dir` remains the
+  parent directory. Review report and output destinations before running.
+- Completion counts are hidden by default. Use `--verbose` to see them on
+  stderr, including when ordinary reports are disabled. `--debug` also shows
+  counts unless followed by `--quiet`. See [CLI reporting](../cli.md#processing).
+
+Inspect configuration and resources before processing, then try a controlled
+small transcript. Processing preflight checks every glossary correction and
+selected role before preparing outputs or invoking a model. See [operations](../operations.md)
+for lifecycle and recovery.

docs/operations.md

@@ -1,83 +1,66 @@
 # Audita Operations
 
-This guide owns physical output placement and failure handling. The
-[CLI reference](cli.md) owns flags and streams, [configuration](config.md) owns
-settings, and the [output contract](integrations/output-files.md) owns schemas.
+This guide owns output placement and failure handling. The [CLI reference](cli.md)
+owns invocation, [configuration](config.md) owns settings, and the
+[output contract](integrations/output-files.md) owns serialized formats.
 
-## Normal Workflow
+## Processing
 
-1. Validate a version-2 configuration and its selected profiles with
-   `audita config validate --config config.yml`.
-2. Prepare a transcript and glossary following the [input contract](integrations/transcript-glossary-files.md).
-3. Run `audita process input.json --config config.yml --glossary glossary.yaml --output corrected.json`.
-4. Check the exit status, stderr summary, corrected transcript, and reports.
-   A completed run can contain recoverable model errors and still apply
-   corrections that passed every required validator.
+Inspect the application and PromptKit resources, prepare a transcript, then run
+`audita process` with the desired destination. The [examples](../examples/README.md)
+show complete projects. Processing preflight checks every configured glossary
+correction and selected profile before output preparation and model work. Empty
+protection and an empty pipeline are valid. A completed run can contain
+recoverable model errors while still applying independently validated edits.
+Correction repair sends the complete original proposal exchange and branch
+history to the selected repair provider. A provider rejection ends that branch
+as unavailable; other approved edits can still be applied. See
+[configuration](config.md#settings) for the attempt budget and profile selection.
 
-## Required Output Files
+## Outputs and lifecycle
 
-Reporting is enabled by default. For file transcript output, `errors.yml`,
-`recoveries.yml`, and `report.md` go in the transcript output's parent directory.
-For stdout transcript output, they go in `reporting.stdout_dir` (default `.`),
-overridden by `--report-dir`. `--reporting=false` suppresses all three reports
-and removes their path requirements. It does not suppress the stderr summary or
-fatal errors. Stdout contains only transcript JSON; file output leaves it empty.
+Reporting is enabled by default. For transcript file output, `errors.yml`,
+`recoveries.yml`, and `report.md` are placed beside that file unless `--report-dir`
+is supplied. For stdout transcript output they use the effective report directory.
+Disabling reporting leaves its destination inactive and unprobed. Quiet mode
+requires a transcript file or `/dev/null`; it suppresses optional messages, not
+failures. Stdout carries transcript JSON when selected.
 
-Existing report directories and parents for regular transcript files must be
-writable. Audita prevents report writes from overwriting transcript, glossary,
-loaded configuration, or loaded profile sources, and rejects conflicting output
-destinations. The final transcript may intentionally replace its own input after
-successful processing; other input/configuration/profile sources remain protected.
-Preparation never truncates an existing transcript. Device and pipe destinations
-(such as `/dev/null` and named pipes) receive ordinary writes at publication time;
-they are not opened during preflight or replaced with regular files. A pipe write
-can wait for its reader, and stream write errors are fatal. With reporting enabled,
-reports still use the output path's parent; disable reporting when that placement
-is unsuitable for a stream destination.
+Before processing, Audita checks destination collisions against the transcript,
+consumed application and PromptKit sources, and effective host message files. An
+intentional in-place transcript replacement is allowed. A regular transcript
+output is prepared in a sibling temporary file, leaving the final destination
+untouched until successful publication. Pipes and devices are opened only for
+delivery, and a pipe can wait for its reader. If a transcript destination changes
+between a regular file and a pipe or device during processing, Audita can report a
+delivery failure while preserving the new destination. Parent directories for
+required outputs must already exist.
 
-With reporting enabled, all three reports are initialized as `in_progress` before
-input processing. Output is encoded fully before publication. Each regular output
-file is replaced through a temporary file on its destination filesystem:
-transcript first, then `errors.yml`,
-`recoveries.yml`, and `report.md`. This is per-file replacement, not a
-multi-file transaction. New files honor the process umask; replacing an existing
-file preserves its permission bits. A late report error may leave the transcript
-published; the process exits nonzero and attempts failed-status reports. On fatal processing
-or cancellation, no completed transcript is published, but partial reports are
-finalized where possible. An uncatchable termination can leave `in_progress`.
+Enabled reports are initialized as `in_progress` before processing. The
+transcript is published before final reports; the files do not form a single
+transaction. A late report failure may therefore leave a published transcript.
+Fatal errors and cancellation clean unpublished temporary resources and attempt
+failed-status final reports. An uncatchable termination can leave `in_progress`
+evidence. Read exit status and reports together rather than treating a file's
+existence as proof of success.
 
-## Diagnostics Directory
+## Debug evidence
 
-`--debug` enables detailed evidence independently of reporting. One directory
-named `run-<id>` is created under `diagnostics.work_dir` (default `/tmp/audita`)
-and retained on success or failure. Without debug, no directory or payload
-files are created. The parent is created when needed only for debug. Failure to
-write optional debug evidence prints a redacted stderr diagnostic but does not
-change correction decisions or the exit status.
+The shared `--debug` flag enables retained artifacts in a run directory beneath
+`diagnostics.work_dir`; selecting a work directory alone does not enable capture.
+Optional debug preparation or writes can produce redacted warnings without
+changing correction decisions or the required output result. Debug material can
+include transcript content, prompts, responses, and correction decisions. It is
+not anonymized; protect it according to the input's sensitivity. Configured
+credential values are redacted at the diagnostic boundary. Repair interactions
+and revalidation artifacts include proposal and attempt coordinates; the
+correction ledger connects them to the original edit.
 
-Debug evidence includes invocation and effective settings, configuration
-origins, selected profiles, redacted source and normalized snapshots,
-normalization and initial chunk summaries, all captured proposed candidates
-and validator decisions in `correction-ledger.json`, execution/utilization
-records, and model interaction files. Individual artifact writes can fail; a
-directory's existence does not prove every file was written. These files can
-contain transcript text and prompt/response payloads. Configured backend
-credentials are redacted, but the transcript itself is not anonymized. Protect
-and retain the directory according to the sensitivity of the input.
+## Recovery
 
-## Failure Inspection and Recovery
-
-Exit `0` means processing and every enabled required output completed. Exit
-`1` means cancellation, fatal processing, or required-output failure. Exit `2`
-identifies usage or configuration/destination selection errors. Recoverable
-model-operation failures appear in `errors.yml` as one record per affected
-work unit; they do not automatically make the run fail. `recoveries.yml`
-records successful operations that needed retry, repair, or proposal filtering.
-`report.md` shows every initial chunk and configured module instance, including
-interrupted and unattempted work. Ordinary reports omit transcript excerpts and
-full decision ledgers; enable debug when those are needed.
-
-Read stderr and report status first. If a required output failed after a
-transcript was published, do not treat the file alone as proof of a completed
-run. Fix the input, service, or destination problem and rerun. Audita has no
-resume/checkpoint API.
+Exit `0` indicates completion of processing and required outputs; nonzero status
+indicates an input, processing, cancellation, or required-output failure.
+Recoverable model-operation failures and successful repairs or retries are
+recorded separately in the ordinary YAML reports. The Markdown matrices identify
+pipeline position, module, and optional operator ID. Fix the input, service, or
+destination and rerun when necessary; Audita has no resume or checkpoint API.

docs/oss/attribution.md

@@ -0,0 +1,272 @@
+# Open Source Attribution Notices
+
+## Standard Repository Policies
+
+Material: All documents under `docs/policy/`, root `AGENTS.md`, and the Policy
+Reading Guide in `docs/development.md`, adapted for this repository.
+`docs/policy/documentation.md`, `docs/policy/oss.md`, and `docs/policy/release.md`
+incorporate revision `593c9b52273c5c879785ae9e995d21026df467b4`.
+The remaining listed material incorporates revision
+`d84a38ebab26f048cafbe59a2246700c35d29843`.
+
+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) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/policy/src/commit/593c9b52273c5c879785ae9e995d21026df467b4/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/policy/src/commit/593c9b52273c5c879785ae9e995d21026df467b4/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843).
+
+[Source](https://gitea.maximumdirect.net/eric/policy/src/commit/593c9b52273c5c879785ae9e995d21026df467b4).
+
+## ConfigKit
+
+Selected module: `go.maximumdirect.net/configkit` at `v1.2.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://forge.maximumdirect.net/base-layer/configkit/src/commit/c1c7e87f2cdf77a0cbf3327831ac05578e756b9e/COPYRIGHT).
+
+[Source](https://forge.maximumdirect.net/base-layer/configkit/src/commit/c1c7e87f2cdf77a0cbf3327831ac05578e756b9e).
+
+## ReleaseKit
+
+Selected module: `go.maximumdirect.net/releasekit` at `v0.9.0`.
+
+Material: ReleaseKit runtime and adapted launcher and tag-delivery recipes in
+`scripts/release.sh` and `.woodpecker/release.yml`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/COPYRIGHT).
+
+[Source](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4).
+
+## CommandKit
+
+Selected module: `go.maximumdirect.net/commandkit` at `v0.6.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/1613ff95cab60581de5d86f6e9e2a3cc091a44a0/COPYRIGHT).
+
+[Source](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/1613ff95cab60581de5d86f6e9e2a3cc091a44a0).
+
+## CommandKit ckconfig
+
+Selected module: `go.maximumdirect.net/ckconfig` at `v0.7.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/64f6453b8453f914f272d427bb4ae6f59deacd2b/integrations/ckconfig/COPYRIGHT).
+
+[Source](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/64f6453b8453f914f272d427bb4ae6f59deacd2b).
+
+## CommandKit ckprompt
+
+Selected module: `go.maximumdirect.net/ckprompt` at `v0.7.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/f369d6a78253b6e6fcb1e023fb2e9c3af1d20ff0/integrations/ckprompt/COPYRIGHT).
+
+[Source](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/f369d6a78253b6e6fcb1e023fb2e9c3af1d20ff0).
+
+## Go runtime and standard library
+
+Selected toolchain: Go 1.27.3 for the distributed Linux binaries.
+
+Copyright 2009 The Go Authors.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause-Go.txt) |
+[LICENSE](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/PATENTS).
+
+[Source](https://github.com/golang/go/commit/2aae1000ea1d4b28923b96db28acf4e3b99d6aff).
+
+## Go vendored golang.org/x/crypto
+
+Material: `golang.org/x/crypto` at `v0.52.1-0.20260526024921-9beb694f9766` in the Go 1.27.3 standard library.
+
+Copyright 2009 The Go Authors.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause-Go.txt) |
+[LICENSE](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/src/vendor/golang.org/x/crypto/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/src/vendor/golang.org/x/crypto/PATENTS).
+
+[Source](https://github.com/golang/go/commit/2aae1000ea1d4b28923b96db28acf4e3b99d6aff).
+
+## Go vendored golang.org/x/net
+
+Material: `golang.org/x/net` at `v0.55.1-0.20260731170536-c1d18010be90` in the Go 1.27.3 standard library.
+
+Copyright 2009 The Go Authors.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause-Go.txt) |
+[LICENSE](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/src/vendor/golang.org/x/net/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/src/vendor/golang.org/x/net/PATENTS).
+
+[Source](https://github.com/golang/go/commit/2aae1000ea1d4b28923b96db28acf4e3b99d6aff).
+
+## Go vendored golang.org/x/sys
+
+Material: `golang.org/x/sys` at `v0.45.0` in the Go 1.27.3 standard library.
+
+Copyright 2009 The Go Authors.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause-Go.txt) |
+[LICENSE](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/src/vendor/golang.org/x/sys/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/src/vendor/golang.org/x/sys/PATENTS).
+
+[Source](https://github.com/golang/go/commit/2aae1000ea1d4b28923b96db28acf4e3b99d6aff).
+
+## Go vendored golang.org/x/text
+
+Material: `golang.org/x/text` at `v0.37.0` in the Go 1.27.3 standard library.
+
+Copyright 2009 The Go Authors.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause-Go.txt) |
+[LICENSE](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/src/vendor/golang.org/x/text/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/2aae1000ea1d4b28923b96db28acf4e3b99d6aff/src/vendor/golang.org/x/text/PATENTS).
+
+[Source](https://github.com/golang/go/commit/2aae1000ea1d4b28923b96db28acf4e3b99d6aff).
+
+## 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: Apache-2.0 AND MIT
+
+License and notices: [Apache 2.0](licenses/Apache-2.0.txt) |
+[MIT](licenses/MIT-libyaml-v4.txt) |
+[NOTICE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/NOTICE).
+
+[Source](https://github.com/yaml/go-yaml/commit/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125).
+
+## golang.org/x/text
+
+Selected module: `golang.org/x/text` at `v0.14.0`.
+
+Copyright (c) 2009 The Go Authors. All rights reserved.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause-x-text.txt) |
+[LICENSE](https://github.com/golang/text/blob/6c97a165dd661335ff7bce6104a008558123c353/LICENSE) |
+[PATENTS](https://github.com/golang/text/blob/6c97a165dd661335ff7bce6104a008558123c353/PATENTS).
+
+[Source](https://github.com/golang/text/commit/6c97a165dd661335ff7bce6104a008558123c353).
+
+## jsonschema/v6
+
+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).
+
+[Source](https://github.com/santhosh-tekuri/jsonschema/commit/29cbed948d24a04700eb94436416b18a07953b71).
+
+## PromptKit
+
+Selected module: `go.maximumdirect.net/promptkit` at `v0.21.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL v3](licenses/LGPL-3.0.txt) |
+[GPL v3](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/171fb11f4e967a1da3af57843c6467954b14ba09/COPYRIGHT).
+
+[Source](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/171fb11f4e967a1da3af57843c6467954b14ba09).
+
+## 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: Apache-2.0 AND MIT
+
+License and notices: [Apache 2.0](licenses/Apache-2.0.txt) |
+[MIT](licenses/MIT-libyaml.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).
+
+## Cobra
+
+Selected module: `github.com/spf13/cobra` at `v1.10.1`.
+
+Copyright 2013-2023 The Cobra Authors
+
+SPDX-License-Identifier: Apache-2.0
+
+License and notices: [Apache 2.0](licenses/Apache-2.0.txt) |
+[LICENSE](https://github.com/spf13/cobra/blob/7da941c3547e93b8c9f70bbd3befca79c6335388/LICENSE.txt).
+
+[Source](https://github.com/spf13/cobra/tree/7da941c3547e93b8c9f70bbd3befca79c6335388).
+
+## pflag
+
+Selected module: `github.com/spf13/pflag` at `v1.0.9`.
+
+Copyright (c) 2012 Alex Ogier. All rights reserved.
+
+Copyright (c) 2012 The Go Authors. All rights reserved.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause-Go.txt) |
+[LICENSE](https://github.com/spf13/pflag/blob/10438578954bba2527fe5cae3684d4532b064bbe/LICENSE).
+
+[Source](https://github.com/spf13/pflag/tree/10438578954bba2527fe5cae3684d4532b064bbe).

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-Go.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/BSD-3-Clause-x-text.txt

@@ -0,0 +1,27 @@
+Copyright (c) 2009 The Go Authors. All rights reserved.
+
+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 Inc. 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-libyaml-v4.txt

@@ -0,0 +1,19 @@
+Copyright (c) 2006-2010 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-libyaml.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/policy/agents.md

@@ -1,12 +1,13 @@
 # Agent Policy
 
-**Base Policy Version:** 1.0
+**Base Policy Version:** 1.3
 
-**Last Updated**: 2026-09-23
+**Last Updated**: 2026-09-28
+**Upstream Source:** [Standard Repository Policies agents](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/agents.md)
 
 ## Purpose
 
-Agents working in this repository must read and adhere to the following house rules.
+Agents must read and follow these rules.
 
 ## Implementation Discipline
 
@@ -66,15 +67,15 @@ Examples:
 
 ## Git Commit Policy
 
-By default, create a commit after completing each coherent unit of work, using a
+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. Do not commit after every intermediate edit or create empty commits.
+documentation.
 Complete the appropriate validation before committing. If work is incomplete or
-validation is blocked, report that state rather than presenting it as completed.
+validation is blocked, report that state accurately.
 
 Before committing:
 
@@ -82,10 +83,10 @@ Before committing:
    changes. Identify changes that predate the current unit of work.
 2. Exclude secrets, local environment files, generated junk, and unrelated changes.
 3. Stage only the files or hunks belonging to the completed unit. Use `git add .`
-   only when every included change belongs to that unit. Do not disturb unrelated
-   staged or unstaged work.
-4. Review `git diff --staged` and run appropriate checks for the change. Do not
-   repeat checks already passed for unchanged content merely to create a commit.
+   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.

docs/policy/architecture.md

@@ -1,10 +1,42 @@
 # Architecture Policy
 
-**Base Policy Version:** 1.0
+**Base Policy Version:** 1.3
 
-**Last Updated**: 2026-09-24
+**Last Updated**: 2026-11-11
+**Upstream Source:** [Standard Repository Policies architecture](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/architecture.md)
 
-## Purpose and System Shape
+## 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.
+
+## Application-Specific Topics
 
 Audita is a single-process Go CLI for transcript polishing. Its architecture
 separates deterministic transcript processing from external LLM effects through
@@ -40,13 +72,19 @@ hidden global state.
 
 ## Correction and Concurrency Invariants
 
+- Module focus guides proposal generation; it is not an exclusive acceptance
+  boundary. Validators permit otherwise acceptable minor editorial cleanup even
+  when the originating module did not request it. Existing applicability,
+  protection, and meaning checks still apply. See
+  [ADR 0003](../adr/0003-module-focus-and-editorial-acceptance.md) for the empirical
+  rationale and rejected strict-scope alternative.
 - Treat LLM responses as nondeterministic inputs. Preserve deterministic proposal
   indexing, validator ordering, transcript mutation, reports, and serialization.
 - Validate corrections before final mutation, including local proposal checks,
   decision cardinality, and apply-time safety. Provider-side schema enforcement
   does not replace these checks.
-- Keep LLM concurrency bounded and context-aware through PromptKit's engine-local
-  per-backend admission. Proposal and validation calls selecting the same backend
+- Use PromptKit's context-aware, engine-local per-backend admission for
+  LLM concurrency. Proposal and validation calls selecting the same backend
   share that capacity, including retries and repairs. Preserve deterministic
   collection order. Recoverable model-operation failures stay local to their
   proposal response or validation batch; fatal invariant/application failure
@@ -74,7 +112,7 @@ future changes should treat those current contracts deliberately. Current implem
 limits are documented in the [internal overview](../internal/overview.md#current-scope);
 they are not additional prohibitions on future development.
 
-## Errors and Secret Handling
+## Trust Boundaries And Threat Scope
 
 Errors should identify the failed processing phase sufficiently for users and
 subprocess callers. Preserve the stream and exit behavior defined by the
@@ -88,13 +126,19 @@ responsibilities and should remain separate. Implementation details belong in
 
 ## Dependencies
 
-Keep Audita dependency-light and prefer the Go standard library for CLI parsing,
-filesystems, synchronization, and tests. ConfigKit owns configuration loading,
-presence, provenance, and secret resolution; PromptKit owns prompt/profile
-loading, OpenAI-compatible transport, retries, repairs, and backend admission.
-Audita owns domain meaning, role selection, and deterministic processing.
+Keep Audita dependency-light and prefer the Go standard library where no adopted
+library owns the boundary. ConfigKit owns configuration composition, presence,
+recorded resolution, and provenance. PromptKit owns prompt, profile, backend,
+credential, transport, retry, repair, and admission behavior. CommandKit and its
+integrations own command routing and their standard inspection and request
+surfaces. Audita owns domain meaning, role selection, transcript processing,
+and presentation of its processing results.
 
-Do not introduce broad CLI, dependency-injection, workflow, logging, or plugin
+Pass resolved typed configuration to preflight and processing. Preflight checks
+execution readiness before output preparation or model work; the output session
+owns resources, cleanup, and publication. The glossary and readiness decision is
+recorded in [ADR 0002](../adr/0002-glossary-configuration-and-preflight.md).
+Do not introduce broad dependency-injection, workflow, logging, or plugin
 frameworks without a concrete implemented need and focused tests.
 
 ## Testing and Documentation

docs/policy/documentation.md

@@ -1,8 +1,9 @@
 # Documentation Policy
 
-**Base Policy Version:** 1.1
+**Base Policy Version:** 1.12
 
-**Last Updated**: 2026-09-23
+**Last Updated**: 2026-11-11
+**Upstream Source:** [Standard Repository Policies documentation](https://gitea.maximumdirect.net/eric/policy/src/commit/593c9b52273c5c879785ae9e995d21026df467b4/docs/policy/documentation.md)
 
 ## Purpose
 
@@ -16,7 +17,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
@@ -28,24 +29,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.
+
+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.
@@ -61,40 +64,43 @@ secret values.
 
 | Topic | Canonical owner | Owned content | Content owned elsewhere |
 | --- | --- | --- | --- |
-| Product orientation and minimal end-to-end quickstart | `README.md` | What this application 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. |
-| Application architecture policy | `docs/policy/architecture.md` | System shape, normative ownership, dependency direction, architectural boundaries, invariants, safety properties, and non-goals. | Concrete package inventory, implementation mechanics, contributor procedures, decision history, future work. |
-| Agent policy | `docs/policy/agents.md` | Implementation discipline for coding agents, including proportionality, idiomatic simplicity, code discovery, Git commit restrictions, and rules against inventing requirements, restrictions, guarantees, or repository policy. | Application contracts, architecture, testing policy, and contributor procedures. |
+| 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; graph-first code discovery, commit discipline, and 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-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. |
-| Release policy | `docs/policy/release.md` | Versioning and compatibility rules, release integrity and immutability requirements, release-documentation policy, required gates, publication controls, verification requirements, and exception policy. | Repository-specific commands, product installation guidance, CLI version semantics, historical release summaries, and CI implementation detail. |
-| Repository-specific release procedure | `docs/release.md` | Maintainer prerequisites, candidate preparation, concrete validation and publication commands, repository and registry guards, deliverable publication, consumer-facing verification, and failure recovery. | General release requirements, product installation guidance, historical release summaries, and current compatibility contracts. |
-| 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, cleanup, permissions, recovery, and operational limits. | CLI flag syntax, configuration field definitions, logical output schemas, implementation mechanics. |
-| Integration contracts for external components | `docs/integrations/`, including `docs/integrations/output-files.md` for serialized outputs | 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. |
-| Inventory of implemented internal packages | `docs/internal/overview.md` | Current packages and components, their implemented 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, internal collaborators and state transitions, package-local guarantees and failures, and relevant tests. | Global architecture invariants, configuration definitions and defaults, external schemas, operator procedures. |
+| 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 publication commands and automated guards, asynchronous deliverables, delivery status, 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. |
+| Integration contracts for external components (if applicable) | `docs/integrations/`, including `docs/integrations/output-files.md` for serialized outputs | 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. |
 | Contributor change recipes | Relevant files under `docs/internal/`, including `docs/internal/cli-config.md`, `docs/internal/modules.md`, and `docs/internal/validators.md` | Concrete editing and validation steps for each component. | Contributor orientation, global policy, and definitions of external contracts. |
-| 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 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. |
-| Complete copyable artifacts | `examples/` | Maintained configuration, inputs, and other files intended to be copied or run. | Field-by-field reference, command reference, prose explanation. |
+| Architectural decision records | `docs/adr/` | Records of significant architectural decisions and supporting rationale. | Ordinary design choices, current behavior reference, implementation status, task sequencing. |
+| Future work and implementation status | `docs/roadmap/` | Proposed, accepted, or future 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. Audita has
-retired its standalone troubleshooting guide; concrete operating and recovery
-procedures belong in `docs/operations.md`.
+Create supporting documents for existing interfaces and responsibilities when
+substantive content is available.
+Audita has retired its standalone troubleshooting guide; concrete operating and
+recovery procedures belong in `docs/operations.md`.
 
 ## 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
 
@@ -108,12 +114,16 @@ other contracts.
 
 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 are immutable
-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 procedure or
-release note to weaken policy, redefine current behavior, or defer required
-documentation updates.
+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
 
@@ -144,8 +154,15 @@ Use sequentially numbered ADR filenames such as
 
 Treat the decision content of an accepted ADR as immutable. When a decision
 changes, create a new ADR and update the earlier ADR's status to superseded.
-Rejected architectural alternatives belong in the ADR; rejected product ideas
-belong in the roadmap.
+
+ADRs should be reserved for major architectural decisions, such as ownership
+boundaries, large-scale architectural features, or invariants that rise to
+the level of architectural significance. Routine choices, implementation
+decisions, and rejected suggestions do not warrant an ADR unless they
+otherwise represent a significant architectural decision.
+
+Roadmaps should preserve plausible future work, not rejected product
+ideas.
 
 ## Maintenance
 

docs/policy/meta.md

@@ -0,0 +1,26 @@
+# Policy Set Provenance
+
+**Base Policy Version:** 1.0
+
+**Last Updated**: 2026-09-28
+**Upstream Source:** [Standard Repository Policies meta](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,222 @@
+# Open Source Licensing And Attribution Policy
+
+**Base Policy Version:** 1.9
+
+**Last Updated**: 2026-11-11
+**Upstream Source:** [Standard Repository Policies oss](https://gitea.maximumdirect.net/eric/policy/src/commit/593c9b52273c5c879785ae9e995d21026df467b4/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.
+
+Audita uses the existing GPL-3.0-or-later application grant in
+[`COPYRIGHT`](../../COPYRIGHT). The Gitea distribution and publication procedure
+are documented in the [release runbook](../release.md).
+
+## 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
+
+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 the COPYRIGHT examples exactly as provided, except for placeholder
+substitutions and changes expressly required or authorized by this policy or
+the author.
+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.
+
+## 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.
+
+When the toolchain used for distributed binaries changes, check the Go runtime
+and standard-library entries against that toolchain's exact source revision,
+including any vendored packages incorporated into those binaries.
+
+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

@@ -1,40 +1,50 @@
 # Release Policy
 
-**Base Policy Version:** 1.0
+**Base Policy Version:** 1.7
 
-**Last Updated**: 2026-09-23
+**Last Updated**: 2026-11-11
+**Upstream Source:** [Standard Repository Policies release](https://gitea.maximumdirect.net/eric/policy/src/commit/593c9b52273c5c879785ae9e995d21026df467b4/docs/policy/release.md)
 
 ## Purpose
 
-This policy defines the minimum requirements for selecting, validating,
-publishing, verifying, and correcting releases. Its goal is to make every
-release intentional, reproducible from an exact source revision, documented
-for consumers, and safe from retrospective replacement.
+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 that implement these requirements belong in
-`docs/release.md`. Historical release summaries belong in `docs/releases/`.
-This is an Audita-specific adaptation of the base policy, not a requirement to
-implement the standard unchanged. Adapt it further when Audita's needs warrant;
-the canonical procedure must agree with the adopted policy.
+Adopt stronger verification or reproducibility requirements through an explicit
+project-specific decision justified by the intended audience and support needs.
 
-## Release Model
+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.
 
-A release identifies one exact source commit with an immutable version tag and
-its checked-in release note. The primary release branch is `main`.
+## Release Model And Completion
 
-Release success means that the intended version tag has been created and
-successfully pushed to the authoritative remote with its source commit. The
-release procedure ends at that point. It must never wait for CI to complete or
-require successful CI status, artifact publication, or consumer installation as
-a completion gate.
+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` unless the adopted policy specifies otherwise.
+The procedure must name the authoritative publication remote.
 
-CI builds and publishes binaries and checksums asynchronously from the tagged
-source. Delayed or failed automation does not reverse release success. Artifact
-availability is a separate status and must not be claimed merely because the tag
-was pushed. Published artifacts must be traceable to the tagged source.
+A successful push of the intended tag, with its source commit available on the
+authoritative primary branch, completes the release. The source commit may be
+pushed before the tag or published together with it through an atomic push.
+The procedure must choose and document the supported approach.
 
-Automation must not silently change the source candidate, move a published tag,
-or replace an existing published artifact.
+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.
+
+Repositories may publish source only. Additional binaries, images, packages,
+checksums, or other declared deliverables may be published asynchronously from
+the tagged source. The procedure must identify those deliverables and the
+responsibility of their automation. Published deliverables must be traceable
+to that source and identify the same version.
+
+Track source-release completion and artifact delivery separately. Report delivery
+failures and optional investigations under artifact-delivery status.
 
 ## Supported Platforms
 
@@ -42,127 +52,217 @@ or replace an existing published artifact.
 | --- | --- |
 | Linux amd64 | Required production target |
 | Linux arm64 | Required production target |
-| macOS arm64 | Best effort for local development; failures do not block a release or Linux artifact publication |
+| macOS arm64 | Best effort for local development; development failures do not block a release or Linux artifact publication |
 
 Windows and macOS amd64 are unsupported. Neither their builds nor tests are
 release requirements. Native macOS testing and access to a Mac are not release
 prerequisites.
 
+Linux amd64 and arm64 remain the required production targets. Publication from
+a host outside the selected target set must pass ReleaseKit's temporary native
+version check. This check does not require access to a Mac or native tests on
+every delivery target.
+
 ## Versioning And Compatibility
 
 Stable releases use Semantic Versioning in the form `vMAJOR.MINOR.PATCH`, with
-no leading zeroes. Each version must be unused locally and on the authoritative
-remote before publication begins.
+no leading zeroes. Prereleases require an explicit adopted policy defining
+their format and use.
 
-Unless an adopted policy explicitly supports and defines prereleases,
-prerelease versions are not permitted.
+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 minor release may add backward-compatible behavior or raise the Go consumer
+  minimum as described below; and
 - a patch release may make backward-compatible fixes.
 
+In this context, "backward-compatible" means only that pre-existing, valid
+configurations will continue to work following the release. Behavior need not
+remain strictly identical.
+
+Audita's minor and patch releases also preserve the documented
+[subprocess integration](../integrations/subprocess.md) and
+[output-file](../integrations/output-files.md) contracts.
+
 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.
 
-A repository with additional compatibility promises must define them in its
-adopted policy or canonical contract documentation. A release note may explain
-a compatibility change, but it must not redefine the current compatibility
-contract.
+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
+## Consumer Minimum And Release Toolchain
 
-Every release made under this policy must include
-`docs/releases/<version>.md` in the tagged source tree. The filename must use
-the complete version tag, and the document must begin with a title containing
-the product name and that exact version.
+Distinguish the minimum toolchain supported for consumers from the toolchain
+maintainers use to build and validate a release. Record the consumer minimum in
+the language's standard metadata and explain its support meaning in canonical
+documentation. Define the selected release toolchain and its setup commands in
+`docs/release.md`. Toolchain selection and upgrade cadence are repository-specific
+choices.
 
-Release notes must contain a short summary and any relevant compatibility or
-upgrade instructions. Fixed sections and explicit no-action boilerplate are not
-required. Keep notes proportionate to the change.
+For Go repositories, normally declare the initial stable release of the selected
+series as the consumer minimum, such as `go 1.26.0`. Use a higher patch minimum
+when a dependency or an identified correctness fix requires it, and document
+the reason.
 
-Release notes are immutable historical summaries. They should link to current
-canonical documentation for exact behavior. Every affected canonical document
-must be updated in the same candidate; a release note must not substitute for
-current documentation or defer required documentation changes.
+For release-policy purposes, successful build and release validation on the
+selected Go patch release are sufficient to presume support across that Go
+series, subject to the declared consumer minimum and concrete evidence of
+incompatibility. Investigate specific compatibility concerns as they arise.
 
-## Candidate Preparation And Validation
+Use the selected release toolchain for candidate validation and release builds,
+including CI jobs performing those tasks. A newer validation patch version alone
+leaves the consumer minimum unchanged.
 
-Use the minimum gates needed for confidence in Audita's release. Provide one
-local command for the selected automated checks, following the
-[testing policy](testing.md). Run the deterministic, offline default test suite
-once for the candidate and verify that both required Linux targets build.
-Avoid duplicate test runs solely to satisfy separate release phases.
+A minor release may raise the Go consumer minimum, including from one Go series
+to the next, both before and after `v1.0.0`. This is an explicit exception to the
+backward-compatibility requirement for minor releases. Patch releases preserve
+the consumer minimum. Explain an increase's impact and required consumer action
+in the release note. Other incompatible changes remain subject to the versioning
+rules above.
 
-Additional checks must address a concrete risk not already covered. Do not
-inherit a mandatory linting, documentation audit, platform matrix, or live-service
-checklist solely from the base policy. Documentation migration validation is
-separate work, not automatically a recurring release gate.
+## Release Documentation And Preparation
 
-Automate mechanical guards. Do not require manual approvals, sign-offs, laptop
-testing, or post-publication inspection as release gates. Version selection and
-a concise release summary remain preparation inputs, not separate approval rounds.
+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. If annotated tags are used, derive their summary from the
+checked-in note.
+
+Include the release footer defined by the [OSS policy](oss.md#discoverability)
+in each new release document and preserve it on the hosted download page. The
+release procedure defines the concrete URLs and publication mechanics. Prepare
+these links with the release note; they do not add a network check or approval
+gate.
+
+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.
+
+## Audita's Selected Candidate Checks
+
+Audita uses ReleaseKit v0.9.0 with race-enabled offline tests, full Go vet,
+formatting, Markdown links, module distribution checks, and the required target
+builds. Race checks address shared processing and client state; vet and format
+checks catch common defects and mechanical drift; link and module checks protect
+the distributed source tree. The [runbook](../release.md) specifies the selected
+toolchain, native commands, and asynchronous recovery.
 
 ## Publication Guards
 
-The procedure must automate the small set of checks needed to publish the
-intended source under a fresh version:
+Automate the checks needed to publish the intended source under a fresh version:
 
-- valid, unused version on the authoritative remote;
-- clean worktree and index on the primary release branch;
-- the exact candidate that passed the local checks, including its matching note;
-- publication of that source commit and the exact intended tag.
+- the version has the adopted format and is unused locally and on the
+  authoritative remote;
+- the worktree and index are clean on the primary release branch;
+- the source being published is the exact candidate that passed validation,
+  including its matching release note;
+- the remote primary branch already identifies that candidate, or an atomic
+  source/tag push will advance it to that candidate without discarding remote
+  history; and
+- the tag identifies the validated candidate and only the intended refs are
+  published.
 
-Do not require remote CI success. Avoid an additional manual confirmation for
-each mechanical guard. Publish explicit refs rather than all local tags.
-A successful push is the completion signal; a failed or ambiguous push must be
-resolved against remote ref state before declaring success or retrying.
+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 Correction
+## Immutability And Failure Recovery
 
-Published version tags and published deliverables are immutable. Do not move,
-overwrite, recreate, or delete a published tag. Do not replace an artifact,
-image, package, checksum, signature, provenance statement, or release note
-under an already published version.
+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, then
-rerun the release command. Validation must apply to the exact candidate. An
-unpublished local tag may be removed after confirming that it was never published
-or used by a release channel.
+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.
 
-If a defect is discovered after publication, leave the published release intact. Correct the defect on the primary branch, choose a
-new patch version or other semantically appropriate new version, write a new
-matching release note, and perform the complete release procedure again.
+Transient network, authentication, CI, or consumer-availability failures do not
+by themselves require a new version. Asynchronous delivery may be retried from
+the same immutable tag. Missing artifacts may be published later, provided
+existing published contents are not replaced and the additions remain consistent
+with the tagged source and any already-published checksum manifest. If that
+cannot be achieved, publish a new version.
 
-A distribution channel's supported yank, deprecation, or advisory mechanism
-may warn consumers away from a defective release, but it must not replace that
-release's contents or reuse its version.
+A defect requiring changes to published source or contents requires a corrected
+commit, a new semantically appropriate version, a matching release note, and
+the release procedure again. Leave the original release intact. A channel's
+yank, deprecation, or advisory mechanism may warn consumers away from a defective
+release without replacing its contents or reusing its version.
 
 ## Repository Release Procedure
 
-Maintain [docs/release.md](../release.md) as a short, executable maintainer runbook.
-It must identify prerequisites, authoritative remote, version and note preparation,
-one local validation command, automated source/tag guards, exact publication
-commands, and failure handling. It must name the asynchronous automation and link
-to this policy for supported platforms and release-success semantics.
+Maintain `docs/release.md` as a short, executable maintainer runbook. It must
+identify:
 
-Describe how to diagnose or retry failed artifact delivery separately from release
-completion. Missing artifacts may be published later from the same immutable tag;
-existing published artifacts must not be overwritten. A source defect requires a
-new version. No polling or CI waiting belongs in the release command.
+1. prerequisites, selected release toolchain, primary branch, and authoritative
+   remote;
+2. version and release-note preparation;
+3. one publication command with its selected local checks and automated guards;
+4. declared deliverables, required build targets, and automation responsibilities;
+5. the successful-push completion point and separately reported delivery status;
+   and
+6. failure handling, ambiguous-push recovery, and asynchronous delivery retries.
 
-## Audita Adaptations
-
-The maintainer approved these deviations from the base policy on 2026-09-23:
-
-- Audita's needs govern policy adaptation rather than strict template compliance.
-- Only Linux amd64 and arm64 are required; macOS arm64 is best effort.
-- A successful tag push completes the release; asynchronous CI cannot block it.
-- Gates are minimal, automated where practical, and avoid redundant validation
-  and human intervention.
-
-The [release procedure](../release.md) and its linked scripts implement these
-requirements. CI delivery remains asynchronous.
+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,43 +1,31 @@
 # Testing Policy
 
-**Base Policy Version:** 1.0
+**Base Policy Version:** 1.3
 
-**Last Updated**: 2026-09-23
+**Last Updated**: 2026-09-28
+**Upstream Source:** [Standard Repository Policies testing](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
 
@@ -69,15 +57,27 @@ To the extent the following features are present in the application, prioritize
 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:
 
@@ -85,28 +85,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. A test must not memorialize the current implementation.
+A test should protect a selected decision, contract, or invariant.
 
-Before adding or retaining a test, ask:
+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.
 
-> 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 sufficient; 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
 
@@ -123,12 +110,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:
@@ -146,25 +134,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.
@@ -174,9 +167,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
 
@@ -197,104 +188,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,130 +1,160 @@
 # Releasing Audita
 
-The [release policy](policy/release.md) defines versioning, supported platforms,
-immutability, and success. This runbook implements it with
-[scripts/release.sh](../scripts/release.sh). Publication ends after a successful
-source/tag push; binary delivery runs asynchronously.
+The [release policy](policy/release.md) owns release requirements. This runbook
+uses the native commands in [scripts/release.sh](../scripts/release.sh), which
+invokes the module-selected ReleaseKit tool. A confirmed source tag completes
+the release; Woodpecker reports binary delivery separately.
 
 ## Prerequisites
 
-Use Bash, Git, and Go 1.25.5 or newer (CI uses Go 1.25.5 or newer), with dependencies available
-locally or downloadable. Tests themselves are offline. Work from a
-checkout of `main` with permission to push that branch and tags to `origin`.
-For this repository, `origin` is `https://gitea.maximumdirect.net/eric/audita.git`.
-The script uses the checkout's configured `origin`; set it correctly before use.
-The remote must support atomic pushes. No CI credentials or Mac are needed locally.
+Use Bash, Git, a C compiler, and cgo for race detection. The authoritative
+remote is `origin`, which must point to `https://gitea.maximumdirect.net/eric/audita.git`; the
+primary branch is `main`. Source publication needs no delivery credential.
+Woodpecker uses the existing `GITEA_RELEASE_TOKEN` secret for delivery.
 
-CI uses the existing `GITEA_RELEASE_TOKEN` secret for asynchronous asset delivery.
-macOS arm64 is a best-effort development environment; no macOS binary is published.
-
-## Prepare the Candidate
-
-Choose an unused version following the policy. Write
-`docs/releases/<version>.md`, beginning with `# Audita <version>`, followed by a
-short summary and any compatibility or upgrade instructions relevant to the
-release. There are no mandatory boilerplate sections. Update affected canonical
-documentation with behavior changes.
-
-Commit the intended changes, including the note, on `main`. The release script
-requires a clean index and worktree and does not create commits. There is no
-separate approval round. Published notes describe their tagged release; existing
-release history does not need to be reconstructed.
-
-## Validate and Publish
-
-From the repository root, substitute the chosen version:
+The source-build minimum is Go 1.27.0, declared in [go.mod](../go.mod).
+This minimum is required by the selected application dependencies.
+Distributed executables do not require a Go installation. The selected release
+toolchain is Go 1.27.3, matching the current Woodpecker image and distributed
+runtime notices. Use that local installation for tool bootstrap, candidate
+validation, and release builds. Replace the installation path below with its
+actual directory:
 
 ```sh
-bash scripts/release.sh --publish v0.2.0
+export PATH="/path/to/go1.27.3/bin:$PATH"
+export GOTOOLCHAIN=local
+go version
 ```
 
-This single invocation:
+Record the reported toolchain with the validation results. The
+[release policy](policy/release.md#consumer-minimum-and-release-toolchain)
+governs the distinction between the consumer minimum and release toolchain,
+support across a Go series, and versioning of minimum increases. When selecting
+a different release toolchain, update the CI image and applicable runtime
+attribution together; a newer build patch alone need not raise the minimum.
 
-1. Checks the version, branch, clean candidate, matching note title, and tag absence.
-2. Runs the default offline test suite once, then builds both required Linux targets
-   in a temporary directory using the same build script as CI.
-3. Checks that the candidate and worktree are unchanged and that it includes the
-   current `origin/main` history.
-4. Creates the version tag at that commit and atomically pushes the exact source
-   commit to `main` and the exact tag to `origin`.
-5. Reports release success and exits without polling CI or checking asset availability.
-
-To validate a prepared candidate without remote access, creating a tag, or pushing:
+Prepare dependencies before offline candidate validation:
 
 ```sh
-bash scripts/release.sh --check v0.2.0
+GOWORK=off GOTOOLCHAIN=local go mod download
 ```
 
-This is an optional diagnostic command, not a required step before `--publish`.
-Publication validates within its own invocation; it does not use persistent cached
-results. Both modes require the candidate note and a clean `main` checkout.
+If dependency preparation changes `go.mod` or `go.sum`, include those changes in
+the committed candidate. ReleaseKit's CLI is registered as a Go tool dependency;
+`go mod tidy` retains its dependencies and checksums. The release wrapper changes
+to the repository root, selects the host target, and invokes the full
+`go.maximumdirect.net/releasekit/cmd/releasekit` tool path with workspace
+discovery and automatic toolchain downloads disabled. Go builds or reuses the selected
+tool from its normal build cache. Tool preparation precedes offline candidate
+validation.
 
-## Artifact Delivery
+## Prepare and publish the candidate
 
-[Woodpecker](../.woodpecker/release.yml) runs on tag events. It invokes
-[scripts/build-release.sh](../scripts/build-release.sh), then publishes:
+Choose an unused version under the [release policy](policy/release.md), write
+`docs/releases/<version>.md`, and begin it with `# Audita <version>`. Include a
+short summary, relevant compatibility or upgrade instructions, and the required
+`COPYRIGHT | LICENSE | ATTRIBUTION` footer with links for the selected version.
+Update affected canonical documentation with behavior changes.
+
+End each note with this footer, substituting its complete tag for `<version>`:
+
+```markdown
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/audita/src/tag/<version>/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/audita/src/tag/<version>/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/audita/src/tag/<version>/docs/oss/attribution.md)
+```
+
+Commit the complete candidate on `main`, including the release note, then push
+the branch first:
+
+```sh
+git push origin main
+```
+
+Record the candidate commit. Before publication, remote `main` must identify
+that exact commit. ReleaseKit checks this along with the clean candidate, note,
+version, and remote tag state.
+
+Publish from the repository root, substituting the selected version:
+
+```sh
+bash scripts/release.sh publish VERSION
+```
+
+The command runs the offline Go test suite with race detection, full Go vet,
+formatting, Markdown link, and module distribution checks. Race detection covers
+shared processing and client state; vet and formatting catch common Go defects and
+mechanical drift; the link and module checks protect the distributed source tree. It builds the
+profile's Linux amd64 and arm64 targets and checks the native version output. It creates an annotated tag whose
+message comes from the committed note, then pushes the exact tag object. A
+successful publication completes the source release without waiting for CI or
+checking artifact availability.
+
+`bash scripts/release.sh check VERSION` is an optional local diagnostic. It
+does not inspect remote availability or publish a tag, and it is not a required
+step before `publish`, which performs its own candidate validation.
+
+The wrapper preserves ReleaseKit's exit status: `0` means confirmed publication;
+`1` means a known validation or publication failure/conflict; `2` means usage,
+profile, or version input error; and `3` means the push outcome remains unknown.
+
+## Binary delivery
+
+Woodpecker runs ReleaseKit's `ci-deliver` command for tags under
+`refs/tags/v*`. The tagged `go.mod` selects the ReleaseKit version, and
+`releasekit.json` supplies Audita's build and delivery settings:
 
 - `audita-<version>-linux-amd64`
 - `audita-<version>-linux-arm64`
 - `SHA256SUMS`
 
-Builds disable CGO and use the shared script's release flags. The version is in the
-asset name and source tag; Audita has no CLI version command. Cross-compilation
-checks compilation, not native execution on each architecture.
+Before running Go, the workflow fetches and verifies the event tag, checks it
+out detached, and confirms the source tree is clean. It peels the event object
+ID to its commit before comparing it with the tag's commit, accepting both
+annotated tag objects and commit IDs from Woodpecker. It copies the tagged
+`go.mod` and `go.sum` into temporary module metadata outside the checkout. Go
+confirms that this configuration selects ReleaseKit, then invokes its CLI
+using an alternate `-modfile` and the host target. Temporary metadata remains
+outside the tagged source. The workflow runs with the selected Go 1.27.3 image,
+`GOWORK=off`, and `GOTOOLCHAIN=local`.
 
-The CI job status and logs show delivery progress or failure. Assets appear on
-the matching Gitea release page when delivery succeeds. A successful tag push
-must not be reported as confirmation that these files are available.
+Delivery uses prepared-checkout mode to verify the existing tag, HEAD, and clean
+worktree without repeating the bootstrap's fetch and checkout.
 
-Consumers can download the binary for their Linux architecture and `SHA256SUMS`
-from that page, check its listed SHA-256 digest with `sha256sum`, and make it
-executable. Optional consumer checks are not maintainer release gates. Digests
-detect file mismatches; they are not an independent signature of authenticity.
-
-## Failure and Retry
-
-**Local validation fails:** correct the issue, commit any changes, and rerun the
-publication command. A failure before tag creation publishes nothing. Temporary
-local build files are removed on exit.
-
-**Push fails or the connection is interrupted:** the script retains the local tag
-and reports failure rather than guessing whether publication succeeded. Inspect
-remote state with the actual version:
+The resulting executable receives:
 
 ```sh
-git rev-parse 'v0.2.0^{commit}'
-git ls-remote origin refs/heads/main refs/tags/v0.2.0
+go tool -modfile="$${bootstrap_dir}/releasekit.mod" "$${releasekit_module}/cmd/releasekit" ci-deliver \
+  --repo "$${CI_WORKSPACE}" \
+  --prepared \
+  --commit "$${expected_commit}" \
+  "$${CI_COMMIT_TAG}"
 ```
 
-If the remote tag identifies the intended candidate and its source is on remote
-`main`, the release succeeded; no CI waiting is needed. An atomic push normally
-updates both refs or neither. If `main` has advanced since publication, fetch it
-and check candidate ancestry rather than requiring tip equality.
+The workflow maps the existing `GITEA_RELEASE_TOKEN` secret to
+`RELEASEKIT_GITEA_TOKEN`. The complete checked-in release note, including its
+licensing footer, supplies the hosted release body. Delivery runs independently
+after source publication; its status and logs report delivery progress or
+failure.
 
-If the tag is absent remotely and was never published or used by a release
-channel, remove only that unpublished local tag (`git tag -d v0.2.0`), resolve
-any rejected branch update, and rerun the command. If the remote tag has a
-different target, do not overwrite it; choose a fresh version. Never force a
-branch or tag update to bypass the guards.
+ReleaseKit handles content-aware retries and retained-artifact recovery. See
+the pinned [publication recovery guide](https://forge.maximumdirect.net/base-layer/releasekit/src/tag/v0.9.0/docs/consumers/publish.md)
+and [delivery guide](https://forge.maximumdirect.net/base-layer/releasekit/src/tag/v0.9.0/docs/consumers/delivery.md)
+for those mechanics. A delivery failure does not undo a confirmed source
+release. Retry the same immutable tag after resolving the reported state; do not
+replace published files or a checksum manifest.
 
-**CI delivery fails:** the release remains successful. Inspect the failed tag
-job's logs and retry that same tagged job for a transient failure. Publication is
-configured to skip existing filenames and not overwrite assets. Keep the same
-source and build environment when retrying; inspect any existing assets/checksum
-manifest before filling gaps. Do not regenerate and replace a published manifest
-or binary. If an existing manifest cannot describe the missing rebuilt assets,
-use a new version instead. A pipeline or source defect also requires a corrected
-commit and new version. An outage does not require moving the tag.
+## Failure and recovery
 
-**A released source defect is discovered:** fix it on `main` and publish a new
-appropriate version with a note explaining the correction. Leave the old tag and
-published files intact.
+Fix validation failures in a new committed candidate, then rerun `publish`.
+After a failed push, ReleaseKit retains the local annotated tag and reports the
+captured authoritative endpoint and publication state. Resolve the result
+against that endpoint before retrying. An exact remote tag-object match, with
+its source available on remote `main`, can confirm publication. If the remote
+state cannot be read, the result remains unknown; do not remove or replace the
+tag while uncertain. Follow the pinned [publication recovery guide](https://forge.maximumdirect.net/base-layer/releasekit/src/tag/v0.9.0/docs/consumers/publish.md)
+for object-level recovery details.
 
-## Maintaining the Release Workflow
-
-The shared build script keeps local and CI build settings aligned. Tests in
-[scripts/release_test.go](../scripts/release_test.go) exercise publication against
-temporary local Git remotes, including guard failures and rejected pushes, with
-Go execution stubbed to avoid recursive builds/tests. They run in `go test ./...`.
-Changes to CI delivery should preserve explicit asset names, checksums, and
-non-overwriting publication. CI delivery is separate from the local success path.
+A source-release success and artifact-delivery status are separate. For a
+partial or uncertain delivery, inspect the job output and follow the pinned
+[delivery recovery guidance](https://forge.maximumdirect.net/base-layer/releasekit/src/tag/v0.9.0/docs/consumers/delivery.md).
+A source or published-content correction requires a new appropriate version;
+leave the original tag and its contents intact.

docs/releases/README.md

@@ -1,9 +1,14 @@
 # Release Notes
 
+- [Audita v3.1.1](v3.1.1.md)
+- [Audita v3.1.0](v3.1.0.md)
+- [Audita v3.0.1](v3.0.1.md)
+- [Audita v3.0.0](v3.0.0.md)
+- [Audita v2.0.1](v2.0.1.md)
 - [Audita v2.0.0](v2.0.0.md)
 - [Audita v1.1.0](v1.1.0.md)
 
-See the [release documentation requirements](../policy/release.md#release-documentation).
+See the [release documentation requirements](../policy/release.md#release-documentation-and-preparation).
 Use the [release procedure](../release.md) to prepare and publish new releases.
 
 This index does not reconstruct or replace records for existing tags.

docs/releases/v2.0.1.md

@@ -0,0 +1,15 @@
+# Audita v2.0.1
+
+This patch release updates the selected ConfigKit and PromptKit libraries and
+adds complete licensing and attribution information to the source tree. Release
+notes are now used as the body of new hosted releases.
+
+- ConfigKit is updated to v0.4.2 and PromptKit to v0.11.2. The selected
+  OpenRouter and Rakestrawhome catalogs are updated to v2.20260926.0.
+- The [project grant](../../COPYRIGHT) and [upstream attribution](../oss/attribution.md)
+  now identify the application's license, incorporated components, and the
+  separately licensed policy material.
+- The [release procedure](../release.md) describes the source release and
+  asynchronous Linux binary delivery. Existing release records remain intact.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/audita/src/tag/v2.0.1/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/audita/src/tag/v2.0.1/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/audita/src/tag/v2.0.1/docs/oss/attribution.md)

docs/releases/v3.0.0.md

@@ -0,0 +1,59 @@
+# Audita v3.0.0
+
+Audita v3 adopts native configuration inheritance and layered PromptKit
+definitions, and allows transcript and report destinations to be selected
+independently. This is an intentional breaking release: existing PromptKit
+profile files require migration from the v2 release format.
+
+## Changes
+
+- ConfigKit is updated from v0.4.2 to v0.5.0. Application configuration supports
+  native sibling inheritance, and configuration explanations include value-free
+  inheritance provenance.
+- PromptKit is updated from v0.11.2 to v0.12.0, with both backend catalogs at
+  `v3.20260930.0`. Native keyed definitions support profile inheritance and
+  operator prompt overrides. The selected `profiles_dir` can contain profiles,
+  backends, and prompts; application backend endpoints, capacity, and credentials
+  remain authoritative.
+- Effective definitions and referenced prompt message contents are captured at
+  runtime construction. Consumed host configuration and message files are
+  protected from output collisions. Audita retains its per-call schemas, domain
+  validators, retry and repair budgets, and resilient processing behavior.
+- An explicit `--report-dir` now selects reports for either file or stdout
+  transcript output. File output without that flag still places reports beside
+  the transcript. This supports Narratio's independent output destinations;
+  debug capture remains independently selectable.
+
+## Upgrading from v2
+
+1. Convert each old PromptKit profile to a keyed definition under
+   `profiles: {<profile-id>: ...}`, remove its inner `id`, and replace
+   `base_profile` with `extends`. Profile IDs come from mapping keys rather than
+   filenames. No compatibility loader or automatic conversion is provided.
+2. Review explicit zero, omitted, and null generation controls. For example,
+   `temperature: 0` now sends an explicit zero, omission leaves the control
+   unspecified, and null suppresses an inherited control. A zero profile timeout
+   disables PromptKit's generation deadline; Audita's operation deadline still
+   applies.
+3. Select a configuration root whose final definitions are valid. PromptKit now
+   validates unused definitions too, including backend references, and conflicting
+   values within a directory source group are errors. The maintained examples
+   use separate [local](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/examples/profiles/local/) and
+   [service](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/examples/profiles/service/) roots. Runtime source edits take
+   effect on the next invocation.
+4. Rename any application backend literally named `extends` and update its
+   profile references. ConfigKit now reserves that key for inheritance.
+5. Validate the migrated installation with
+   `audita config validate --config /path/to/config.yml`, including any selected
+   testing overlay. Application configuration continues to use `version: 2`.
+
+The [v3.0.0 configuration reference](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/docs/config.md#promptkit-profiles-and-operator-prompts)
+contains the migrated format and presence rules. Start from the
+[local](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/examples/minimal-config.yml),
+[service](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/examples/production-config.yml), or
+[application inheritance](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/examples/configkit-inheritance.yml) examples.
+The [CLI reference](../cli.md) describes report selection, and the
+[release procedure](../release.md) describes source publication and asynchronous
+Linux binary delivery.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.0/docs/oss/attribution.md)

docs/releases/v3.0.1.md

@@ -0,0 +1,14 @@
+# Audita v3.0.1
+
+This patch release adds a configuration-free version command and adopts
+ReleaseKit for source publication and Linux binary delivery. Transcript
+processing, configuration, and LLM behavior are unchanged.
+
+## Changes
+
+- `audita version` prints the application version without loading application
+  configuration or contacting an LLM provider.
+- Release publication and Linux artifact delivery now use ReleaseKit v0.1.0.
+  The release runbook describes the maintainer workflow and delivery recovery.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.1/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.1/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.0.1/docs/oss/attribution.md)

docs/releases/v3.1.0.md

@@ -0,0 +1,42 @@
+# Audita v3.1.0
+
+This minor release updates Audita's configuration, LLM, and release libraries
+and raises the minimum Go version for source builds to 1.26.0. Existing Audita
+configuration files, PromptKit profiles, and command behavior require no
+migration.
+
+## Changes
+
+- ConfigKit is updated from v0.5.0 to v0.7.1, with improvements to configuration
+  loading, resolution, provenance, and inspection efficiency.
+- PromptKit is updated from v0.12.0 to v0.14.0, reducing avoidable allocations in
+  preparation, rendering, and execution. Audita retains its existing schemas,
+  validation, retry and repair budgets, and resilient processing behavior.
+  The libraries' new discovery and configuration-comparison APIs remain unused
+  by Audita.
+- ReleaseKit is updated from v0.1.0 to v0.4.1. The local release launcher now
+  invokes the module-selected Go tool, and CI selects the tool from the tagged
+  module metadata. Prepared-checkout delivery reuses the tag checkout already
+  verified during CI bootstrap. Source publication still completes at a
+  successful tag push; Linux binary delivery remains asynchronous.
+- Release builds and CI use Go 1.26.8, with corresponding runtime attribution
+  updated. The source-build minimum is tracked separately from that build
+  toolchain patch version.
+
+## Upgrading from v3.0.1
+
+Source builders must upgrade from the previous Go 1.25.5 minimum to **Go 1.26.0
+or newer**, including any build environments still using Go 1.25. Maintainers
+should follow the updated [release procedure](../release.md) for toolchain setup,
+publication, and delivery recovery.
+
+Go module consumers must use the v3 module path. For example:
+`go install gitea.maximumdirect.net/eric/audita/v3/cmd/audita@v3.1.0`. This
+aligns the module path with the v3 release line. Downloaded binaries and
+commands run from a source checkout are unaffected.
+
+Users of distributed Linux binaries need no Go installation. No configuration,
+profile, transcript-format, or command-behavior migration is required for this
+release.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.0/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.0/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.0/docs/oss/attribution.md)

docs/releases/v3.1.1.md

@@ -0,0 +1,20 @@
+# Audita v3.1.1
+
+This patch fixes the Woodpecker bootstrap failure that prevented Linux binary
+delivery for v3.1.0. Audita's transcript processing and configuration are unchanged.
+
+## Changes
+
+- Resolve Woodpecker's tag-event object ID to its source commit before checking
+  the tagged checkout and invoking ReleaseKit. Annotated tag events previously
+  failed a comparison between the tag object and commit, stopping the workflow
+  before binary builds began.
+- Add offline regression coverage for annotated and lightweight tag events,
+  including rejection of an unrelated source commit.
+
+No configuration, profile, transcript-format, or command-behavior migration is
+required from v3.1.0. The Go source-build minimum remains 1.26.0. Linux amd64 and
+arm64 binary delivery follows the existing asynchronous
+[release procedure](../release.md#binary-delivery).
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.1/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.1/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.1/docs/oss/attribution.md)

docs/roadmap/configkit.md

@@ -1,171 +0,0 @@
-# ConfigKit Adoption Roadmap
-
-**Last updated:** 2026-09-24
-
-**Status:** Production implementation complete. The selected configuration and
-overlay model is implemented; [implementation evidence](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md)
-records verification. No release has been published.
-
-## Purpose and Direction
-
-Adopt ConfigKit to harmonize Audita's configuration policy with the other
-applications in the suite. Consistent configuration conventions are the primary
-benefit; reducing application-owned configuration infrastructure is a secondary
-benefit and a useful measure of integration quality.
-
-This is an intentional breaking migration. There is no goal of backward
-compatibility with existing installations, configuration files, CLI flags,
-environment variables, or configuration-inspection output. Provide a migration
-guide instead of legacy loaders, aliases, dual operating modes, or an ongoing
-compatibility layer. Retain existing syntax only when it independently suits the
-new model, not because compatibility requires it.
-
-The initial review and prototype used ConfigKit v0.3.1, then verified v0.4.0
-selected overlays. Those findings remain historical; the prototype was removed
-after production integration. The application depends on a versioned module,
-without a sibling checkout or local module replacement.
-
-The shared boundary/prototype unit is complete. Its [selected contract, inventory,
-and evidence](library-boundary-findings.md) define the detailed target alongside
-this roadmap. Production configuration migration is complete.
-
-## Target End State
-
-- ConfigKit owns strict YAML loading, input presence, default application, explicit
-  override mechanics, recorded resolution, secret references, and safe inspection.
-- Audita owns its configuration types, field meanings, defaults, schema-version
-  policy, file selection, CLI parsing, domain validation, and runtime initialization.
-- Adopt ConfigKit's precedence and validation lifecycle rather than reproduce
-  Audita's current per-layer validation and environment-overlay behavior.
-- General configuration environment overrides are retired. Credentials use typed
-  environment-name secret references; supplied references must resolve according
-  to ConfigKit's contract. File selection follows the application-owned
-  discovery rules in the selected boundary.
-- Standardize duration representations, explicit empty/null/zero handling, and
-  inheritance on the shared conventions. Express genuine Audita domain rules
-  through the supported resolution and validation APIs.
-- Retained domain-setting flags and proposal/validation profile flags become
-  explicit ConfigKit overrides according to the migration inventory. Remove old
-  provider/key/retry/concurrency flags and aliases. Credentials use secret references.
-- Use ConfigKit's redacted effective output and provide source/explanation access
-  through the selected views below. Legacy JSON inspection is replaced.
-  Diagnostic configuration snapshots use the same new model.
-- Delete superseded loading and override machinery. Do not hide the old model
-  behind adapters that defeat the adoption's consistency benefit.
-
-Keep Audita's domain capabilities, such as ordered and repeated correction modules,
-expressible in the new model. Their existing configuration spelling is not binding.
-Transcript/glossary formats, processing algorithms, and output schemas are outside
-this migration unless later planning identifies a concrete dependency or an
-explicitly coordinated change.
-
-## Selected Overlays for Testing
-
-Enable ConfigKit's optional selected-overlay feature in the migration. A testing
-configuration that selects cheaper, faster LLMs is the initial use case. ConfigKit
-**overlays** modify application settings; PromptKit **execution profiles** still
-own model and generation settings. Keep `profiles_dir`, the PromptKit `profiles/`
-directory, and proposal/validation profile names unchanged by this terminology
-change.
-
-The planned interface is `--overlay <name>` on `process`, `config validate`, and
-`config print-effective`. Treat selection as invocation state passed to
-`Options.Overlay`, not as another persistent setting or environment overlay.
-Follow ConfigKit v0.4.0's selection contract: omission, an empty name, or `default`
-selects no overlay; a named selection loads `overlays/<name>.yml` beneath the selected
-configuration root. A missing selected overlay is an error. Use the library's
-single-overlay semantics without adding stacking, inheritance, or legacy-directory
-fallback.
-
-Precedence is application defaults, main configuration, selected overlay, then
-explicit setting flags. Perform Audita's role inheritance and semantic validation
-on the resolved configuration. ConfigKit's base parsing and schema-version checks
-still precede overlay application; overlays cannot replace the schema version or
-contain ConfigKit directives. General environment-variable overrides remain retired.
-Imports and secret-directory bootstrap remain disabled.
-
-Provide a maintained `overlays/testing.yml` example that selects testing execution
-profiles through `llm.proposal_profile` and `llm.validation_profile`. Model names and
-generation controls belong in the corresponding PromptKit profile files. Set both
-role selections in this example so a base configuration's explicit validation
-profile cannot accidentally retain the production model. Normal omission-based
-validation-profile inheritance continues to apply to the final effective settings.
-The example must make its backend/credential requirements clear and use no real
-secrets. Model choice is operator-controlled; “testing” does not promise a price,
-performance level, or equivalent correction quality.
-
-Overlays may modify other ordinary application settings supported by the schema;
-they are not restricted to profile selection. The resulting configuration must
-still satisfy shared backend capacity, credential, and domain rules. Validation,
-effective-config inspection, selected-profile inspection, and processing must all
-use the same selected overlay. Preserve overlay provenance in configuration
-explanations and diagnostics while retaining secret redaction.
-
-The [recorded overlay results](library-boundary-findings.md#selected-overlay-extension-2026-09-24)
-prove the representative load, inspection, and HTTP path. Production acceptance
-requires the same selection to reach both actual LLM roles, with explicit flags
-winning over overlays and surviving secret references resolved/redacted correctly.
-The isolated prototype is evidence, not a second supported runtime.
-
-## Inspection and Invocation Contract
-
-`process`, `config validate`, and `config print-effective` share file/overlay
-selection and retained setting overrides. Invocation I/O paths remain process-only.
-Only explicitly supplied flags override settings. Validation requires an explicit
-config file; processing and inspection use the selected discovery order. Help is
-available before configuration loading. All three commands validate selected
-profiles without requiring a provider call during setup.
-
-`config print-effective --view settings|profiles|explain` exposes three YAML views:
-
-- `settings` (default): ConfigKit's redacted effective configuration.
-- `profiles`: an Audita-owned summary of each selected role's profile, backend,
-  model, temperature, token limit, top-p, timeout, service tier, and reasoning
-  effort where present. Arbitrary extra provider parameters and credentials are
-  omitted; this is a selected-controls view, not every execution input.
-- `explain`: field paths, sources, and derivation records from ConfigKit, without
-  resolved secret values.
-
-A ConfigKit snapshot alone does not describe profile-owned controls. Profile
-inspection must enforce the registered-backend and credential boundary. Diagnostic
-snapshots use these safe views and preserve overlay/explicit-override provenance.
-The migration guide explains the intentional replacement of legacy inspection JSON.
-
-## Integration and Completion Criteria
-
-ConfigKit and PromptKit form one intentional breaking refactor. Intermediate
-commits need not build or run. The target contains no temporary old-runtime adapter,
-compatibility shim, processing gate, dual loader, or automatic legacy conversion.
-The [combined feature roadmap](library-adoption.md) owns execution/reporting intent;
-[implementation.md](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md) alone owns stage order and implementation tasks.
-
-The final application loads all retained domain settings, assembles both selected
-profiles, and processes through PromptKit. Controlled HTTP evidence must connect
-configuration selection to actual requests, domain outcomes, safe diagnostics,
-and shared finite backend capacity. Maintained examples and one migration guide
-cover the complete file/flag/environment transition. Obsolete application-owned
-loading, transport, rendering, and scheduler machinery is removed.
-
-The combined target is Audita v2.0.0. Release compliance and publication remain
-last and separate from implementing the refactor. Retention and transcript timestamp
-changes are not included; the selected retry/repair contract resolves the retry
-follow-up in [runtime behavior](runtime-behavior.md).
-
-## Scope Boundaries
-
-- Pin ConfigKit v0.4.0 in production and align Go/toolchain requirements. ConfigKit requires
-  Go 1.25; the combined PromptKit prototype requires Go 1.25.5. Adopting these libraries
-  does not automatically remove Audita's existing YAML dependency used for glossary parsing.
-- Implement the selected configuration and final PromptKit runtime directly,
-  without temporary runtime adapters, compatibility shims, or process gates.
-- Enable selected overlays as specified above. Keep imports and secret-directory
-  bootstrap disabled unless a separate concrete requirement justifies them.
-- Validation and inspection resolve surviving credential references and fail on
-  missing or empty values; no credential-free bypass is planned.
-- Inspection and diagnostics use the safe selected-profile view and ConfigKit
-  provenance described above. Changed formats are covered by the migration guide.
-
-The eventual completion test is that Audita follows the suite's ConfigKit
-conventions while retaining its intended domain capabilities, with a clear
-migration guide and no ongoing obligation to support the previous configuration
-model.

docs/roadmap/decision-set-reconciliation.md

@@ -1,162 +0,0 @@
-# Partial Success for Validator Decision Sets
-
-**Last updated:** 2026-09-25
-
-**Status:** Implemented. This document owns the target behavior and user intent.
-[implementation.md](implementation.md) owns concrete decisions, ordered work,
-and verification.
-
-## Purpose and User Intent
-
-Preserve usable validator decisions when other entries in the same model response
-have missing, duplicate, or unexpected correction indices. One defective entry
-should not prevent unrelated candidates from completing their required validation.
-This extends Audita's existing partial-success approach without another model call.
-
-Implement this simpler improvement before reconsidering guided domain recovery.
-Missing validation must never authorize applying a correction, but neither should
-it invalidate a different candidate's unambiguous approval or editorial rejection.
-The existing [resilience design](resilience.md) remains the foundation.
-
-## Historical Baseline
-
-The reviewed application baseline is `d2a6fcf`:
-
-- PromptKit validates the complete model response against Audita's embedded JSON
-  Schema and performs its configured structural repairs. Only structurally valid,
-  decoded responses reach domain decision mapping.
-- `mapLLMResponseToDecisions` in
-  [`llm_validators.go`](../../internal/framework/validators/llm_validators.go)
-  requires exactly one decision for every requested correction index. An empty
-  decision list, missing index, duplicate index, or unexpected index returns an
-  error instead of retaining usable decisions.
-- `LLMBackedValidator.Validate` consequently marks the entire batch unavailable
-  with `validation_decisions_invalid`. Other batches continue, but usable decisions
-  within that batch are lost.
-- The runner's cardinality checks enforce an internal contract: each candidate
-  receives one outcome from each validator it reaches. These checks apply to
-  Audita-owned results, not directly to raw model entries.
-- Deterministic validators already filter individual proposals. Unpreviewable
-  candidates and oversized validation inputs are isolated; recoverable provider
-  failures remain batch-local; application skips individual conflicts.
-- Ordinary reports distinguish failed operations from successful operations with
-  recoveries. Several failed operations in one stage/chunk share one work-unit
-  error record. The [output contract](../integrations/output-files.md) owns the
-  current counts and serialized representation.
-
-The defect addressed here is the all-or-nothing domain mapping boundary, not
-validation itself or the runner's internal consistency checks.
-
-## Target Decision Semantics
-
-Reconcile each structurally valid response against the indices actually requested
-in that particular validator batch. Correction indices, rather than segment IDs
-or positions in the response array, identify candidates. Several corrections may
-legitimately target the same segment.
-
-| Response condition | Target behavior |
-| --- | --- |
-| Exactly one valid decision for a requested index | Preserve its approval or rejection and associated decision evidence. |
-| Requested index omitted | Produce an explicit validation-unavailable outcome for that candidate. |
-| Requested index appears more than once | Treat that candidate's validation as unavailable; preserve unrelated decisions. |
-| Index was not requested in this batch | Ignore the extraneous entry and record the handled defect. |
-| Empty decision list for a nonempty request | Mark all requested candidates unavailable; do not fail the run. |
-| Decisions appear in a different order | Match by identity and retain deterministic internal results. |
-
-Duplicate handling does not choose the first or last answer, nor infer a verdict
-by voting. Even identical duplicates follow the agreed duplicate-index handling;
-accepting them specially is not needed for this feature. Duplicate extraneous
-indices remain extraneous entries, not reasons to invalidate requested candidates.
-
-An unavailable candidate remains unapplied and does not proceed as approved to
-later validators. It is distinct from a valid `approved: false` decision, which
-is ordinary editorial processing. Valid approvals continue through the remaining
-required validators and apply-time checks; this feature grants no bypass.
-
-The mapper returns one internal outcome for every requested candidate and no
-outcome for an extraneous index. Preserve strict runner cardinality checks so
-application bugs are still detected. Do not convert genuine internal invariant
-failures, cancellation, or fatal setup failures into tolerated model defects.
-
-## Outcomes and Reporting
-
-Keep existing work-unit aggregation and operation accounting:
-
-- If any requested candidate lacks an unambiguous usable decision, record a
-  validation-operation error identifying the affected requested indices. Other
-  candidates' usable decisions from that operation remain effective. An operation
-  error does not mean every candidate in its batch failed.
-- If all requested candidates have usable decisions and extra entries were
-  ignored, record a successful operation with a recovery for that handled defect.
-  This remains a recovery even if all legitimate decisions are editorial rejections.
-- If missing/duplicate requested decisions and ignored extras coexist, retain the
-  operation error. Follow the existing rule that failed operations do not also
-  produce recovery records; retain extra-entry details in debug evidence.
-- A valid complete response with no handled defect adds neither error nor recovery.
-  Valid editorial rejection alone never adds either category.
-- Preserve actual structural repair and service-retry counts. On successful
-  operations, consolidate applicable recovery reasons in one recovery record.
-  Do not count reconciliation as another LLM operation or structural repair.
-
-Error attribution must distinguish affected candidates from the rest of the batch.
-Debug evidence should preserve supplied decisions, ignored entries, and the reason
-an expected candidate became unavailable. Do not fabricate candidate ledger entries
-for unknown indices or mislabel missing decisions as deliberate editorial rejection.
-Ordinary reports must retain safe metadata without raw transcript or response text.
-
-Use a decision-specific recovery reason rather than treating ignored validator
-entries as defective correction proposals. Concrete reason names and minimal data
-model changes belong in the implementation plan. Keep YAML, Markdown, and CLI
-counts consistent, with the existing reporting-disable and independent debug options.
-
-## Ownership and Target Architecture
-
-Audita's validator layer reconciles structurally valid model responses into
-complete internal candidate outcomes. The runner preserves strict internal
-cardinality and advances only approved candidates. Reporting consumes operation
-facts without treating partial validation failure as loss of every decision.
-Debug evidence distinguishes unavailable validation from editorial rejection.
-
-The schema/transport boundary remains with PromptKit; reconciliation needs no
-additional model call. Concrete helper structures, reason names, mapping changes,
-and verification steps belong in the [implementation plan](implementation.md).
-
-## Scope Boundaries
-
-PromptKit's whole-response structural validation and repair remain unchanged.
-A malformed entry, including an extraneous entry that violates the schema, may
-still invalidate the response and exhaust structural repairs before reconciliation
-can run. Ignoring schema-valid extras does not promise salvage from malformed JSON,
-missing required fields, wrong types, or out-of-range values.
-
-General per-entry structural salvage is a separate design question, not part of
-this fix. Likewise, guided regeneration remains deferred for reconsideration after
-this change; no new retries, feedback prompts, budgets, upstream dependency changes,
-or operator controls are required here.
-
-Preserve module scope, literal replacement behavior, fixed chunks, stage barriers,
-span-deletion safeguards, backend capacity limits, and fatal cancellation behavior.
-No additional restrictions on valid corrections or guarantees about model judgment
-are introduced. This work does not itself authorize tagging or publishing v2.0.0.
-
-## Acceptance Criteria
-
-- A schema-valid response can retain usable decisions despite missing, duplicate,
-  or unexpected indices elsewhere in the same batch.
-- Only the affected requested candidates become unavailable; extras never create
-  candidates or attach decisions to a different batch's candidates.
-- Valid negative decisions remain editorial outcomes, and every applied correction
-  completes all required validation.
-- Internal validator results satisfy existing strict cardinality checks.
-- Missing/duplicate requested decisions yield accurately attributed errors without
-  losing valid work. Extra-only defects yield a consolidated recovery; mixed
-  defects follow existing failed-operation reporting semantics.
-- Final transcript, debug evidence, YAML reports, Markdown counts, and CLI summary
-  agree about applied work and failures/recoveries.
-- Reconciliation makes no additional provider calls. Existing structural failures,
-  provider failures, and cancellation retain their documented handling.
-
-## Open Questions
-
-No unresolved product-policy questions block implementation. Guided recovery and
-structural salvage remain separate future decisions.

docs/roadmap/future.md

@@ -1,19 +1,20 @@
 # Deferred Feature Work
 
-**Last updated:** 2026-09-25
+**Last updated:** 2026-11-11
 
 **Status:** Deferred or exploratory work; not implemented or scheduled. These
-entries preserve scope outside the [resilience roadmap](resilience.md) and
-[span-deletion consistency roadmap](span-deletion.md). Each entry states its
-intent; inclusion does not commit us to implementing every capability.
+entries preserve work beyond completed feature and library upgrades.
+Each entry states its intent; inclusion does not commit us to
+implementing every capability.
 
 ## Domain-Aware Response Recovery
 
-The [partial-success decision reconciliation](decision-set-reconciliation.md)
-preserves usable decisions without another model call. Guided recovery remains
-deferred pending evidence from failures that remain. General per-entry
-salvage from structurally invalid responses is also a separate design question;
-the accepted reconciliation feature retains whole-response structural validation.
+The implemented [partial-success decision reconciliation](../internal/validators.md#llm-validator-batching)
+preserves usable decisions without another model call. Revision of rejected
+correction proposals is implemented with substantive
+validator feedback and explicit proposal withdrawal; see the
+[pipeline guide](../internal/pipeline.md).
+It is distinct from recovering an unavailable validator decision.
 
 Consider bounded feedback and regeneration for model responses that satisfy the
 structural schema but leave requested decisions unavailable after reconciliation.
@@ -30,11 +31,15 @@ secrets, and how regeneration fits bounded budgets and operation deadlines. Reus
 shared library capabilities where appropriate; do not introduce an uncoordinated
 outer retry loop that multiplies existing retry/repair budgets.
 
-Ordinary editorial rejection is a valid decision, not a reason to regenerate until
-an edit is approved. Recovery must preserve required validation, candidate identity,
-partial-success safety, and truthful error/recovery reporting. Validate with
-controlled responses that distinguish recoverable protocol defects from valid
-negative decisions. Exact APIs, budgets, and sequencing remain undecided.
+Editorial rejection remains a valid decision about the evaluated proposal. The
+implemented correction repair loop handles subsequent revision and full
+revalidation; this deferred entry concerns unavailable decisions. Decision recovery
+must preserve required validation, candidate identity, partial-success safety,
+and truthful error/recovery reporting. Validate with controlled responses that
+distinguish protocol defects from valid negative decisions. Exact APIs, budgets,
+and sequencing remain undecided. General per-entry salvage from structurally
+invalid responses also remains a separate design question; current reconciliation
+retains whole-response structural validation.
 
 ## Independent Whole-Pipeline Traversal by Chunk
 
@@ -59,7 +64,7 @@ No new scheduler, global limiter, or execution mode is selected by this entry.
 
 Potential future work, subject first to evaluating whether it is worth implementing
 at all. Empty replacement text and deletion of a span within a surviving segment
-are covered by the accepted [span-deletion consistency roadmap](span-deletion.md).
+are covered by the implemented [span-deletion behavior](../internal/modules.md#proposal-generation-ownership).
 That feature does not remove segment records or permit blank resulting segments.
 
 Before designing segment removal, review representative production examples to

docs/roadmap/implementation.md

@@ -1,287 +0,0 @@
-# Implementation Plan: Partial Validator Decision Sets
-
-**Last updated:** 2026-09-25
-
-**Status:** Implemented; all stages completed.
-**Source baseline:** `60e2fe7`.
-**Audience:** gpt-5.6-terra coding agent.
-
-## Scope and Execution
-
-Implement [partial success for validator decision sets](decision-set-reconciliation.md).
-That roadmap owns product intent and target semantics; this document selects the
-implementation and verification work. Follow Stage 1 through Stage 3 in order and
-record completion evidence beneath each stage. Each stage is a focused agent task.
-
-Read [development guidance](../development.md) and all policies under
-[docs/policy](../policy/): [agents](../policy/agents.md),
-[architecture](../policy/architecture.md), [documentation](../policy/documentation.md),
-[testing](../policy/testing.md), and [release](../policy/release.md). Use graph-first
-code discovery, preserve unrelated work, and commit completed coherent units with
-plain English messages. Do not introduce approval rounds between stages.
-
-Aim directly at the final implementation. No temporary modes, compatibility shims,
-new configuration, extra model calls, or upstream dependency work is required.
-Keep PromptKit structural validation/repair and the runner's internal cardinality
-checks. Implement the agreed outcomes, not extra restrictions suggested by existing
-tests or incidental internal structure. Internal helper signatures and layout can
-be adjusted idiomatically while preserving the decisions below.
-
-This replaces the completed span-deletion plan, available in Git at
-`60e2fe7:docs/roadmap/implementation.md`. It does not reopen that feature. The final
-stage includes correcting historical links that otherwise point to this new plan.
-No release preparation, tag, push, CI wait, or paid-provider evaluation is included.
-
-## Selected Implementation Decisions
-
-### Reconciliation boundary
-
-Keep reconciliation in `internal/framework/validators`, after successful structured
-completion and before converting the batch into runner-facing results. Replace
-`mapLLMResponseToDecisions` with a small pure reconciliation helper; use an ordinary
-private result struct containing:
-
-- `Decisions []Decision`: one outcome per requested item, in request order;
-- `UnavailableIndices []int`: requested indices without a usable verdict;
-- `IgnoredIndices []int`: unexpected indices encountered in response order, including
-  repeated unexpected entries, for debug attribution.
-
-No generic reconciliation framework or new shared abstraction is needed. Requested
-identities come from `batch.Items`, not transcript segment IDs, the whole section,
-or any other batch. Expected input identities remain an Audita internal contract.
-
-First collect response entries by requested index and count occurrences, separating
-unexpected indices. Then walk requested items once to construct outcomes. This
-avoids accepting an early duplicate before seeing a conflicting later entry.
-
-Use these candidate-level reason codes in `validators/models.go`:
-
-| Condition | Internal outcome/reason |
-| --- | --- |
-| Missing requested entry | `DispositionUnavailable`, `missing_validation_decision` |
-| More than one entry for a requested index | `DispositionUnavailable`, `duplicate_validation_decision` |
-| Single requested entry failing the existing confidence range check | `DispositionUnavailable`, `invalid_validation_decision` |
-| Single usable entry | Existing approved or `llm_rejected` decision with its model reason. |
-
-Unavailable outcomes have `Approved: false` and fixed safe explanatory messages.
-Duplicate classification takes precedence over inspecting individual duplicate
-values; identical duplicates follow the same rule. Unexpected entries are ignored
-before inspecting confidence. Retain the existing confidence check as a local
-check for decoded callers/test doubles, scoped to that candidate; do not broaden
-this into structural salvage, confidence thresholds, or new semantic validation.
-The production JSON Schema still rejects out-of-range confidence before mapping.
-
-An empty response list makes every requested item unavailable. Response ordering
-must not change verdicts or which candidate is affected. Preserve the existing
-handling of valid negative decisions, including reason text. No candidate may
-advance merely because another candidate was approved.
-
-### Operation accounting and ordinary reports
-
-Each actual validation batch remains one `outcomes.Operation`. Use existing
-`ReasonValidationDecisionsInvalid` (`validation_decisions_invalid`) for a batch
-with unavailable requested candidates. Set `Succeeded: false`, set `ProposalIndices`
-to only those unavailable indices, retain execution counts, and leave recovery
-reasons empty. Still return usable decisions from that batch alongside explicit
-unavailable outcomes, with no Go error for the reconciled model defect.
-
-If no requested candidates are unavailable, set `Succeeded: true`. Add
-`outcomes.RecoveryValidationDecisionsFiltered` with serialized value
-`validation_decisions_filtered` when extras were ignored. Merge it with actual
-`output_repaired` and `service_recovered` reasons in the same recovery operation.
-Valid negative decisions do not prevent operation success. A clean response creates
-no new recovery reason.
-
-When unavailable candidates and extras coexist, record the failed operation only;
-keep ignored-entry evidence in debug. Do not create both an error and a recovery
-for that operation. Successful survivors must continue even though the operation
-itself records a failure. Retain actual execution counts on all paths.
-
-Reuse existing ordinary YAML structures and version 1. The only new public report
-value is the decision-specific recovery reason; affected error indices already fit
-`Failure.ProposalIndices`. Do not add ignored entries to `Operation.Filtered` or
-`filtered_proposals`, which describe correction proposals, and do not increment
-`proposal_responses_with_filtering`. The recovery reason and existing operation
-identity suffice for ordinary reporting; detailed extra indices belong in debug.
-
-Update `processreport.safeMessage` for `validation_decisions_invalid` to explain
-that some required decisions were unavailable without claiming all batch decisions
-were discarded. Generalize the recovery message to include response filtering,
-rather than only proposal filtering. Exact prose is not a test contract. Preserve
-work-unit error grouping, operation counts, and existing YAML/Markdown/CLI totals.
-
-### Debug evidence and runner records
-
-Existing interaction diagnostics already retain the full decoded response and final
-content. Add the reconciliation result to the response diagnostic payload for a
-successfully decoded validation response. Perform reconciliation before writing
-that diagnostic; retain existing call-error diagnostics and diagnostic-write failure
-handling. All reconciled decisions, including unavailable outcomes, receive the
-returned response artifact path. This records unexpected indices and duplicates
-without inventing candidate ledger entries or an additional debug file.
-
-Carry `validators.DecisionDisposition` through `runner.ValidatorDecisionRecord`
-and `runner.ValidatorRejectedChange` in an additive `disposition` field. Populate
-it from each actual `Decision`, including partial decision evidence returned on
-fatal paths. Keep the existing collection names and application flow; no parallel
-unavailable-candidate collection is necessary.
-
-In `processreport`, add `disposition` to `LedgerValidatorDecisionRecord` and map
-unavailable candidates to a top-level ledger disposition `unavailable`, instead
-of `rejected`. Ordinary editorial/deterministic rejections remain `rejected`.
-Use the explicit disposition, not a reason-code allowlist, so existing timeout,
-provider-failure, and oversized-input outcomes retain the same distinction too.
-Update affected test fixtures to supply dispositions where they represent real
-validator outputs. Do not invent a fatal check or compatibility subsystem for a
-zero-value disposition in handcrafted fixtures.
-
-Retain candidate identity, literal proposed replacements (including explicit empty
-strings), and omission of applied replacements for unapplied candidates. Existing
-fatal/interrupted/module-failure handling and debug-off behavior remain. Supplied
-model decisions remain visible in interaction evidence even when reconciliation
-cannot accept them as authoritative verdicts.
-
-## Stage 1 — Reconcile Model Decisions and Preserve Valid Work
-
-**Completed:** 2026-09-25. Reconciliation preserves usable decisions, attributes
-unavailable requested indices and ignored extras, and keeps strict runner
-cardinality. Validator and runner boundary checks passed with
-`go test ./internal/framework/validators ./internal/framework/runner`.
-
-**Work**
-
-1. Read the validator models, `llm_validators.go`, existing partial-batch tests,
-   `outcomes/outcomes.go`, and `runner.validateSectionCandidates`.
-2. Implement the reconciliation result/helper and candidate reason codes selected
-   above. Replace the whole-batch mapping-error branch with outcome construction
-   and correct batch accounting. Add the decision-specific recovery constant.
-3. Move successful-response diagnostic assembly after reconciliation and include
-   its result. Preserve raw/decoded response evidence and diagnostic paths; keep
-   recoverable call errors, fatal errors, and cancellation on their existing paths.
-4. Keep `EnforceDecisionCardinality` and `EnforcePartialDecisionCardinality` strict.
-   Ensure final validator decisions are complete and unique internally. The runner
-   should continue passing only approved candidates onward without treating an
-   operation's failure metadata as a reason to discard valid decisions.
-5. Replace obsolete batch-rejection expectations in `llm_validators_test.go` and
-   relevant runner tests. Preserve cardinality tests that exercise broken internal
-   validators. Update the repaired-but-domain-invalid tests so actual unavailable
-   cases remain errors with counts retained and no recovery record.
-
-**Focused verification**
-
-Use a small table at the validator boundary for mixed missing/extra indices,
-conflicting and identical requested duplicates, extra-only responses, empty lists,
-reordered responses, and a single invalid-confidence decoded test-double entry.
-Include noncontiguous expected indices and valid negative decisions. Assert semantic
-outcomes and affected indices, not helper layout or exact messages. Include one
-controlled case combining successful structural/service recovery facts with ignored
-extras and one failed reconciliation retaining counts without recovery reasons.
-
-At the runner boundary, use the real LLM-backed validator with a controlled client
-and a later validator: prove a survivor reaches later required validation, a later
-rejection prevents application, and unavailable candidates never reach that later
-validator as approved. Use successful proposal operation facts where accounting is
-asserted; do not check an empty operation list. Reuse existing fixtures/tests rather
-than creating a second framework or duplicating every table case.
-
-Run `go test ./internal/framework/validators ./internal/framework/runner`.
-
-**End state:** Usable decisions survive model indexing defects, strict internal
-cardinality remains satisfied, and operation facts explain partial failure or
-successful extra filtering. No extra model generation is introduced.
-
-## Stage 2 — Carry Dispositions Through Debug and Report Partial Outcomes
-
-**Completed:** 2026-09-25. Runner and ledger records carry explicit
-dispositions; ordinary reports distinguish unavailable decision errors from
-extra-index filtering recoveries. Focused report, ledger, runner, and YAML
-checks passed with `go test ./internal/framework/runner
-./internal/framework/processreport ./internal/core/reporting`.
-
-**Work**
-
-1. Add and populate disposition fields through the runner and ledger as selected
-   above. Map unavailable candidates distinctly and preserve empty replacement
-   serialization. Check both normal and fatal partial-evidence paths.
-2. Update `processreport` messages and review `Build`, `mapFailure`, and `mapRecovery`.
-   Reuse their existing aggregation; change only assumptions that would misreport
-   the new operation facts. Core YAML structures and Markdown table layout remain.
-3. Extend existing report/ledger tests for an operation with surviving work plus
-   unavailable indices, extra-only recovery, and a mixed defect operation. Verify
-   error indices exclude survivors, extra filtering does not count as proposal
-   filtering, and failed operations do not also generate recovery records.
-4. Verify debug ledger entries distinguish genuine rejection from unavailability,
-   and interaction diagnostics preserve ignored entries and reconciliation reasons.
-   Unknown response indices must not create fake ledger candidates. Retain existing
-   redaction and optional-debug-failure tests rather than reproducing them all.
-5. Update `docs/integrations/output-files.md` for the new recovery reason and debug
-   disposition, and `docs/internal/diagnostics-reporting.md` for the mapping changes.
-   Explain that validation failure indices identify unavailable candidates, not
-   necessarily every candidate submitted to that batch.
-
-**Validation**
-
-Run `go test ./internal/framework/runner ./internal/framework/processreport ./internal/core/reporting`.
-Use semantic YAML/summary assertions; no whole-report prose golden, exact message
-snapshot, new schema version, or new rendering mode is needed.
-
-**End state:** Reports and debug evidence accurately describe partial validation
-success and handled extras through existing reporting mechanisms.
-
-## Stage 3 — Verify the Assembled Workflow and Finalize Documentation
-
-**Completed:** 2026-09-25. Controlled subprocess runs covered a mixed decision
-response and an extra-only response through the CLI, transcript, YAML, Markdown,
-debug ledger, and interaction evidence. Fixture execution facts showed one
-provider attempt and zero structural repairs per logical call. `go test
-./cmd/audita` and `go test ./...` passed. Canonical validator guidance and
-roadmap status were updated; the two span-deletion plan links now target the
-historical plan at `60e2fe7`.
-
-**Work**
-
-1. Extend the existing local-provider subprocess fixtures in
-   `cmd/audita/main_integration_test.go`. Add a representative mixed-decision run
-   with an applied survivor, a legitimate rejection, a missing requested decision,
-   a duplicate requested decision, and an extra index. Return responses by the
-   requested correction identities; do not freeze incidental validator call order.
-   Ensure the survivor passes all remaining required validation. Assert successful
-   CLI completion, correct transcript, one work-unit error with only unavailable
-   indices, no reconciliation recovery for the failed operation, and debug
-   evidence distinguishing rejection/unavailability without unknown candidates.
-2. Add or adapt a compact extra-only case proving usable work survives and one
-   `validation_decisions_filtered` recovery appears. Verify YAML, Markdown, and CLI
-   agree on totals using semantic assertions. Keep proposal-filtering counts separate.
-   Existing reporting-disable/debug selection tests remain the owners of those options.
-3. In these fixtures give PromptKit its normal configured structural repair allowance,
-   but supply schema-valid responses. Verify reconciliation adds no generations or
-   structural repairs using fixture requests/execution facts, without encoding today's
-   total validator count as a permanent contract. Keep structural-malformation tests
-   and recoverable batch-failure tests; do not relax the schema to make fixtures pass.
-4. Update `docs/internal/validators.md` and any affected canonical descriptions found
-   by searching for whole-batch rejection claims. Explain tolerant external response
-   reconciliation versus strict internal cardinality. The structural-validation
-   boundary remains explicit, and guided recovery remains deferred in `future.md`.
-5. Mark the feature roadmap implemented only after the assembled checks pass, and
-   record actual completion evidence in this plan. Repair the two span-deletion
-   roadmap links to the old plan with the historical URL
-   `https://gitea.maximumdirect.net/eric/audita/src/commit/60e2fe7/docs/roadmap/implementation.md`.
-   Preserve historical release notes and unrelated roadmaps.
-
-**Validation**
-
-Run `go test ./cmd/audita` while developing the fixture, then `go test ./...` once
-for the completed implementation. Run `git diff --check` and verify affected
-Markdown links. Do not add live-provider checks, a platform matrix, repeated full
-suite runs, or release gates solely for this feature. No code is implemented by
-this planning pass; these commands are instructions for the implementation sprint.
-
-**End state:** The accepted partial-success behavior is exercised through the real
-CLI/library boundary, canonical documentation matches it, and coherent changes
-are committed for subsequent release consideration.
-
-## Open Questions
-
-None required before implementation. The implementation decisions above preserve
-the agreed product scope. General structural salvage and guided regeneration remain
-separate future decisions, not unresolved prerequisites for this work.

docs/roadmap/library-adoption.md

@@ -1,129 +0,0 @@
-# Coordinated ConfigKit and PromptKit Adoption
-
-**Last updated:** 2026-09-24
-
-**Status:** Production implementation complete. ConfigKit v0.4.0 and PromptKit
-v0.11.0 are adopted; [historical implementation evidence](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md) records the
-completed checks. The current `implementation.md` covers span deletion instead.
-Release compliance and publication remain separate work.
-
-## Goal and Ownership
-
-Adopt ConfigKit and PromptKit to align Audita with the application suite's shared
-configuration and LLM execution conventions. Consistency is the primary benefit;
-removing overlapping application infrastructure is a secondary benefit. Preserve
-Audita's transcript-correction capabilities and domain protections.
-
-| Owner | Responsibilities |
-| --- | --- |
-| ConfigKit | Strict application configuration loading, presence/default semantics, explicit overrides, recorded resolution, secret references, and safe inspection |
-| PromptKit | Prompt/profile formats and rendering, provider calls, structural output validation and repair, transient retries, engine-local backend admission, and execution observations |
-| Audita | Setting meanings, file/CLI selection, role/profile association, normalization/chunking, ordered modules, domain validation, correction application, reports, diagnostic redaction, and artifact lifecycle |
-
-The [configuration roadmap](configkit.md) owns configuration and inspection policy.
-The [boundary findings](library-boundary-findings.md) own the selected defaults,
-full migration inventory, failure mapping, and prototype evidence. The selected
-production versions are ConfigKit v0.4.0 and PromptKit v0.11.0, with Go 1.25.5 as
-the minimum. Use published modules, never sibling checkouts or local replacements.
-The existing YAML dependency remains while glossary parsing needs it.
-
-## Migration Posture
-
-This is an intentional breaking transition targeting Audita v2.0.0. No backward
-compatibility is required for existing installations, config files, CLI flags,
-environment overlays, or inspection output. Provide one migration guide, without
-legacy loaders, aliases, dual modes, or automatic conversion tooling.
-
-Both libraries belong to one refactor. Intermediate commits need not build or run;
-there is no supported intermediate product state. No temporary adapters, compatibility
-shims, or processing gates are needed. The complete application must work and pass
-its checks before the refactor is finished. Release compliance and publication
-come last, with no intermediate public release.
-
-## Configuration and Execution Target
-
-ConfigKit selected overlays enable a testing configuration that chooses cheaper or
-faster models. The example selects both proposal and validation profiles. ConfigKit
-application overlays and PromptKit execution profiles remain separate concepts.
-Complete operator-maintained profiles own model/generation controls; embedded
-application prompts and schemas are not operator-selected files. No catalog wiring,
-profile-inheritance feature, ConfigKit imports, or secret-directory bootstrap is
-part of this migration.
-
-Capacity controls serve two needs: respecting a local service's hard simultaneous-
-query limit and bounding concurrent paid API activity. One finite limit per backend
-is shared across both roles and every initial, retry, and repair attempt. Limits
-are engine-local, not coordinated across processes. No additional global or
-per-role limiter or fine-grained scheduling policy is required. Profiles must use
-registered backends and ConfigKit-resolved credentials; endpoint-only bypass and
-competing profile credential lookup are excluded.
-
-Structural repair is enabled by default for both roles because additional attempts
-to obtain valid output are desired. Transient retries and structural repairs have
-separate budgets; explicit zero disables the respective behavior. Each generation,
-including a repair, receives its own transient-retry budget. The Audita logical-call
-deadline covers preparation, waiting, backoff, all generations, and repairs; profile
-HTTP timeouts apply per attempt. Exact defaults and bounds are in the
-[selected contract](library-boundary-findings.md#configuration-and-profile-contract).
-No Audita outer retry loop restores the old broader retry policy.
-
-Audita retains all four correction modules, five LLM-validator prompts,
-deterministic validators, confidence/applicability checks, glossary protection,
-validation batching/cardinality, deterministic proposal and ledger ordering,
-transcript encoders, and artifact retention. PromptKit-valid JSON still passes
-Audita's domain checks. Repair exhaustion, provider failure, and domain rejection
-follow the [selected failure table](library-boundary-findings.md#execution-and-failure-mapping).
-Retention and transcript timestamp changes remain separate work; this migration
-resolves the [retry-count follow-up](runtime-behavior.md).
-
-## Reporting and Diagnostic Target
-
-Keep stable Audita-owned serialized records; do not expose raw library structs.
-Use process report schema `v2` with the existing domain outcomes and a new
-`llm_summary` separating logical calls, dispatched provider attempts, transient
-retries, structural repairs, and usage. Transcript schema versions remain unchanged.
-The implementation plan specifies the concrete new fields and artifact wiring.
-
-Usage distinguishes known zero, unknown, and incomplete totals. Preserve observations
-from failed calls even when no final result exists. Count terminal totals once;
-attempt observations provide diagnosis without being added to those totals again.
-This is operational evidence, not a complete billing ledger.
-
-Replace global/role scheduler utilization with per-backend configured capacity and
-observed queue/generation/retry/logical-call timing. Do not fabricate measurements
-that the event API does not provide. Keep domain timing and deterministic correction
-ledger ordering. Record prompt definition/rendered hashes and selected profile/model
-without promising the old hash values. Callbacks are short, concurrency-safe, and
-free of blocking I/O or waits on their own execution.
-
-Effective configuration and selected-profile snapshots remain distinct safe views.
-Secret values must not escape through inspection, logs, reports, runtime errors,
-or retained diagnostic files. Observation records exclude payloads, URLs, raw
-provider messages, prompts, and credentials. Existing artifact lifecycle and
-partial-failure handling remain Audita responsibilities.
-
-## Completion Criteria and Release Boundary
-
-- Both libraries own their selected responsibilities in the production application.
-  Superseded loaders, transport, renderers, schedulers, aliases, and the isolated
-  prototype are gone once its useful evidence is represented in production tests.
-- Offline tests prove configuration-to-execution routing for both roles, selected
-  overlays and explicit overrides, shared backend capacity, retry/repair outcomes,
-  cancellation/deadlines, domain decisions, redaction, and truthful partial reports.
-  Tests exercise real internal collaborators and controlled HTTP boundaries.
-- Maintained examples and canonical docs describe the implemented final model.
-  One migration guide covers files, flags, environment inputs, profiles, credentials,
-  overlays, inspection, and changed runtime/report/diagnostic semantics.
-- The assembled application passes its required checks; Linux amd64 and arm64 build.
-  macOS arm64 remains best effort. No live-provider or CI-success gate is added.
-
-PromptKit v0.11.0's reviewed retry, observation, and capacity APIs remove the earlier
-upstream feature prerequisites; no upstream edit is required for adoption. The
-prototype proved representative behavior, not release compliance or model quality.
-
-The selected PromptKit release uses LGPL-3.0-or-later. A later release unit must
-review the actual production dependency graph and distribution requirements,
-including notices and source/rebuild materials, before binary publication. This
-implementation plan does not claim that review is complete. Release publication
-uses the existing [procedure](../release.md) and completes on successful source/tag
-push, without waiting for CI or artifact delivery.

docs/roadmap/library-boundary-findings.md

@@ -1,392 +0,0 @@
-# Shared Library Boundary: Decisions and Evidence
-
-**Status:** Boundary and offline prototype completed, 2026-09-23. Selected prototype contract and proposed
-production migration target; not the current Audita configuration contract.
-The [bounded roadmap](library-boundary.md) owns scope and completion criteria.
-
-**Subsequent scope decision:** The [ConfigKit overlay plan](configkit.md#selected-overlays-for-testing)
-adds optional selected overlays, with v0.4.0 as the migration baseline. It supersedes
-the original no-overlay decision and adds an input layer between the main file and
-explicit setting overrides. The v0.3.1 prototype results below remain historical
-evidence; they do not establish overlay integration.
-
-## Selected Boundary
-
-The former prototype is retained in Git history at `590604b`; it was a separate
-Go module using published ConfigKit v0.4.0, PromptKit v0.11.0, and
-Audita v1.1.0. The Audita dependency lets this consumer reuse actual internal domain
-helpers through its Audita module namespace without a local replacement. It does
-not make those internal packages a new public API. Remove this dependency along
-with the prototype after equivalent production integration tests landed.
-
-The initial prototype results below were recorded with ConfigKit v0.3.1. On
-2026-09-24, upgrading only its ConfigKit pin and sums to v0.4.0 required no source
-changes. With Go 1.26.8 on linux/amd64, the nested offline `go test ./...` passed
-and `go run .` still reported one accepted correction, four attempts, zero
-transient retries, and two structural repairs. This verifies the dependency
-upgrade, not selected-overlay behavior.
-
-ConfigKit owns loading, presence, explicit overrides, secret resolution, and
-redacted effective settings. PromptKit owns profile parsing, rendering, provider
-execution, transient retries, structural repair, and backend admission. Audita
-owns file selection, setting meanings, role selection, domain acceptance, and
-mapping execution facts into reports. Production CLI and runtime remain unchanged.
-
-## Configuration and Profile Contract
-
-Selected for the prototype and recommended for production:
-
-- Main YAML requires integer `version: 2`; absent, null, unknown fields, and older
-  versions fail. No legacy parser, aliases, environment overlays, or automatic
-  conversion. Defaults precede the selected file; explicitly supplied CLI settings
-  become ConfigKit overrides. Validation runs on the resolved result, so an override
-  may repair an invalid lower-precedence setting when decoding succeeds.
-- Production file selection: explicit `--config`, then
-  `/usr/local/etc/audita/config.yml`, then `/etc/audita/config.yml`. Select one file;
-  do not merge them. Missing system files are skipped; explicit missing or empty
-  paths and inaccessible selected files fail. No selected file fails with a request
-  to configure backend/profile selection: no hidden provider or model default.
-  Remove `AUDITA_CONFIG`. The prototype loads its explicit fixture only; discovery
-  and command parsing belong to the ConfigKit implementation stage.
-- `profiles_dir` defaults to `profiles`, resolved relative to the selected main
-  configuration file, with absolute paths accepted. PromptKit reads that directory.
-  Prompts and schemas are application-embedded, not operator-selected prompt files.
-  The prototype uses complete application-owned profile files. Catalog profiles and
-  profile inheritance are not needed for this migration; do not add catalog wiring.
-- `backends.<id>.endpoint` is required. Use one application backend identity per
-  service capacity pool. Do not split proposal and validation into different backend
-  IDs when they use the same service. Limits are engine-local, not shared across
-  multiple Audita processes or other applications.
-- `backends.<id>.concurrency` defaults to **1**, must be positive, and is shared by
-  both roles and all initial/retry/repair attempts. Operators can select **4** for
-  the described local backend or a suitable finite paid API limit. There is no
-  additional global or per-role limiter. `queue_capacity` defaults to **1024**,
-  following PromptKit; non-negative, with zero meaning no waiting admission.
-  This is an operational escape hatch rather than a second scheduling hierarchy.
-- `backends.<id>.credential` is an optional ConfigKit secret reference: a scalar
-  environment variable name. Omission or null means no credential. A supplied
-  reference must resolve to a nonempty value, including during validation and
-  inspection. There is no direct key field or CLI key flag. ConfigKit resolves it
-  once and Audita supplies `RunRequest.APIKey`. Profiles must not introduce another
-  `api_key_env` lookup. Backend credentials also support unauthenticated local use.
-- Profiles own model, temperature, output token limit, top-p, per-generation timeout,
-  service tier, reasoning effort, and extra provider parameters using PromptKit's
-  format. They select the application `backend`; their effective endpoint must
-  equal that backend's endpoint. Endpoint-only execution is rejected because it
-  bypasses the requested finite capacity boundary. A named registered backend is
-  mandatory even if both roles use the same profile.
-- `llm.proposal_profile` is required. Omitted `llm.validation_profile` inherits the
-  final proposal profile as a whole, with ConfigKit recording the derivation.
-  Explicit empty or null values fail; no individual model/endpoint/key inheritance.
-- `llm.transient_retries` defaults to **2** additional attempts per generation;
-  explicit zero disables retries; negative is invalid. PromptKit owns which failures
-  are eligible. Do not add an Audita retry loop.
-- `llm.repair_attempts` defaults to **2** additional generations for both roles;
-  explicit zero disables repair when deliberately requested. PromptKit supports
-  0–3. Positive defaults are exercised in the prototype. Audita owns this common
-  setting and supplies a complete request output contract with the role's embedded
-  schema, avoiding separate user-facing repair defaults in each prompt.
-- `llm.operation_timeout` defaults to **15m**, must be positive, and uses a Go
-  duration string. It starts before each logical proposal/assessment call and covers
-  preparation, capacity waiting, transient backoff, generation, and repairs. It is
-  separate from whole-process cancellation. Profile `timeout_seconds` defaults to
-  PromptKit's **600** seconds and is applied afresh to each built-in HTTP attempt.
-  It does not bound the combined retry/repair sequence. A stricter caller/transport timeout can
-  also end execution. The two defaults are selected starting points, not throughput
-  measurements. With the default T=2 and R=2, each logical call dispatches at most
-  **9** attempts before deadline/cancellation; proposal plus assessment may use 18.
-- Omission retains static defaults or invokes the recorded role/backend derivations.
-  Null is not a general synonym for omission: nonoptional scalars reject it. Optional
-  credentials and the future optional section target accept null. Explicit empty
-  module lists will mean an empty correction pipeline, not “restore defaults.”
-  Repeated modules retain their existing ordered meaning.
-- The original prototype disabled ConfigKit imports, selected configuration layers
-  (then called configuration profiles), and secret-directory bootstrap. Selected
-  overlays are now verified under the linked overlay decision; the other two
-  features remain disabled. PromptKit execution profiles retain their meaning.
-
-Configuration validation/inspection must assemble and inspect both selected profiles
-without provider calls. ConfigKit's effective YAML describes only its loaded state;
-a separate selected-profile view shows effective model controls/backend selection.
-Do not imply either snapshot alone represents the full execution configuration.
-The prototype exercises the two APIs but does not implement production subcommands.
-Do not serialize raw profile/library objects as a permanent Audita report schema.
-
-## Migration Inventory
-
-This inventory covers the current configuration and process flags documented in
-[configuration](../config.md) and [CLI](../cli.md), including environment-only fields.
-“Retain” below means retain domain meaning in the new schema, not accept old files.
-All legacy environment overlays listed afterward are removed.
-
-| Current file field / setting | Current CLI flag(s) | Target and rationale |
-| --- | --- | --- |
-| File selection | `--config` | Retain explicit invocation flag; discovery described above. |
-| Transcript input | positional path | Invocation only; retain one transcript path. |
-| Glossary input | `--glossary` | Invocation only; retain required glossary path. |
-| Corrected output | `--output` | Invocation only; retain stdout fallback. |
-| Report output | `--report-json` | Invocation only; retain separate report file. |
-| `pipeline.modules` | `--modules` | Retain sequence/default `[glossary, homophones, glossary, spoken_word, grammar]`; explicit empty clears rather than inherits. |
-| `output.schema` | `--output-schema` | Retain encoder selection/default `bare-segments`. |
-| `llm.proposal.base_url`, `llm.validation.base_url` | `--base-url`, `--validation-base-url` | Replace with backend endpoint; remove per-role endpoint flags. |
-| Both `llm.*.model` | `--model`, `--validation-model` | Replace with profile model; new `--proposal-profile` / `--validation-profile` select whole profiles. |
-| Both `llm.*.api_key_env`, direct runtime keys | `--llm-api-key`, `--validation-llm-api-key` | Replace with backend ConfigKit secret reference; remove direct key flags. |
-| Both `llm.*.timeout` | `--llm-timeout-seconds`, `--validation-llm-timeout-seconds` | Replace with profile `timeout_seconds`, plus `llm.operation_timeout`; no duplicate timeout flags. |
-| Both `llm.*.max_retries` | `--max-retries`, `--validation-max-retries` | Replace with common `llm.transient_retries` and distinct `llm.repair_attempts`; remove misleading old flags. |
-| `concurrency.total_llm` | `--total-llm-concurrency`, `--llm-concurrency` | Replace with per-backend concurrency; remove global/alias flags. |
-| `concurrency.proposal_llm`, `concurrency.validation_llm` | `--proposal-llm-concurrency`, `--validation-llm-concurrency` | Remove role budgets; shared backend handles service capacity. |
-| Validation prompt budget (no old YAML field) | `--validation-max-prompt-tokens` | Add `validation.max_prompt_tokens`, default 2048, positive; retain explicit flag override. Audita owns batching. |
-| `chunking.target_sections` | `--target-sections` | Retain optional positive target; omission/null means automatic, zero invalid. |
-| `chunking.max_section_tokens` | `--max-section-tokens` | Retain 8192, positive. |
-| `chunking.min_section_tokens` | `--min-section-tokens` | Retain 2048, positive, no greater than maximum. |
-| `normalization.max_segment_gap` | `--normalize-max-segment-gap` | Retain 4.0 numeric seconds, non-negative; drop alternate YAML duration syntax for these domain numeric fields. |
-| `normalization.ellipsis_gap` | `--normalize-ellipsis-gap` | Retain 3.5 numeric seconds, non-negative. |
-| `normalization.max_segment_duration` | `--normalize-max-segment-duration` | Retain 60.0 numeric seconds, positive. |
-| `normalization.max_segment_tokens` | `--normalize-max-segment-tokens` | Retain 2048, positive. |
-| `thresholds.glossary` | `--glossary-confidence-threshold` | Retain 0.8 in [0,1]. |
-| `thresholds.homophones` | `--homophones-confidence-threshold` | Retain 0.8 in [0,1]. |
-| `thresholds.spoken_word` | `--spoken-word-confidence-threshold` | Retain 0.8 in [0,1]. |
-| `thresholds.grammar` | `--grammar-confidence-threshold` | Retain 0.8 in [0,1]. |
-| `context.description` | `--transcript-description` | Retain trimming and 500-byte limit; empty clears context. |
-| `diagnostics.work_dir` | `--work-dir` | Retain `/tmp/audita`, nonempty; artifact lifecycle remains Audita-owned. |
-| `diagnostics.retention` | `--work-dir-retention` | Retain `auto` default and selection; existing `never` follow-up is separate. |
-| Help/version/config commands | `--help`, `-h` | Retain command purpose; help should parse before loading configuration. Effective-config output intentionally becomes ConfigKit YAML, not legacy JSON. |
-
-Retained setting flags become explicit ConfigKit overrides only when supplied;
-CLI parser defaults must not overwrite file values. Normalization flag values stay
-numeric seconds. Domain values convert into existing domain structs after validation;
-do not spread ConfigKit or PromptKit types into correction algorithms.
-
-Complete environment removal map (names remain permissible if explicitly named as
-secret references; none have implicit configuration meaning):
-
-| Old environment names | Replacement |
-| --- | --- |
-| `AUDITA_CONFIG` | File selection above. |
-| `AUDITA_MODULES` | `pipeline.modules` / explicit flag. |
-| `AUDITA_LLM_API_KEY`, `OPENROUTER_API_KEY`, `AUDITA_VALIDATION_LLM_API_KEY` | Explicit backend credential references; no implicit fallback. |
-| `AUDITA_MODEL`, `AUDITA_VALIDATION_MODEL` | Profile files and role selection. |
-| `AUDITA_BASE_URL`, `AUDITA_VALIDATION_BASE_URL` | Backend endpoints. |
-| `AUDITA_LLM_TIMEOUT_SECONDS`, `AUDITA_VALIDATION_LLM_TIMEOUT_SECONDS` | Profile timeout and operation deadline. |
-| `AUDITA_MAX_RETRIES`, `AUDITA_VALIDATION_MAX_RETRIES` | Common transient/repair settings. |
-| `AUDITA_TOTAL_LLM_CONCURRENCY`, `AUDITA_LLM_CONCURRENCY`, `AUDITA_PROPOSAL_LLM_CONCURRENCY`, `AUDITA_VALIDATION_LLM_CONCURRENCY` | Backend concurrency; remove alias/role budgets. |
-| `AUDITA_VALIDATION_MAX_PROMPT_TOKENS` | `validation.max_prompt_tokens` / explicit flag. |
-| `AUDITA_TARGET_SECTIONS`, `AUDITA_MAX_SECTION_TOKENS`, `AUDITA_MIN_SECTION_TOKENS` | Corresponding chunking fields / flags. |
-| `AUDITA_NORMALIZE_MAX_SEGMENT_GAP`, `AUDITA_NORMALIZE_ELLIPSIS_GAP`, `AUDITA_NORMALIZE_MAX_SEGMENT_DURATION`, `AUDITA_NORMALIZE_MAX_SEGMENT_TOKENS` | Corresponding normalization fields / flags. |
-| `AUDITA_GLOSSARY_CONFIDENCE_THRESHOLD`, `AUDITA_HOMOPHONES_CONFIDENCE_THRESHOLD`, `AUDITA_SPOKEN_WORD_CONFIDENCE_THRESHOLD`, `AUDITA_GRAMMAR_CONFIDENCE_THRESHOLD` | Corresponding threshold fields / flags. |
-| `AUDITA_WORK_DIR`, `AUDITA_WORK_DIR_RETENTION` | Diagnostics fields / flags. |
-
-## Execution and Failure Mapping
-
-The executable uses grammar proposal plus grammar review, current response schemas,
-current hardening text, transcript-section/description helpers, proposal preview, and
-actual decision-cardinality enforcement from Audita v1.1.0. PromptKit renders the
-adapted templates; the custom HTTP transport supplies OpenAI-compatible responses.
-The prototype pre-expands Audita's `hardening` template function into the embedded
-PromptKit definitions; it passes existing named string variables unchanged. No
-provider, paid call, or injected high-level LLM client participates.
-
-Generated JSON is structurally validated/repaired by PromptKit before Audita decodes
-it. Audita then checks proposal applicability, confidence, and decision identity and
-cardinality. The demonstration previews corrections without mutation. Production
-retains every module's full validator chain, glossary protection, batching, and
-apply-time checks; the representative prototype does not claim to replace them.
-
-| Outcome | Section/batch effect | Overall run |
-| --- | --- | --- |
-| Structural repair succeeds | Continue domain validation. | Normal execution. |
-| Proposal repair exhausted | No proposals from this section; malformed-output warning. | Continue other work; successful completion may include warnings. |
-| Assessment repair exhausted | Reject this batch; malformed-output warning. | Continue other work. |
-| Schema-valid invalid/missing/duplicate decision indices | Reject batch and warn; no semantic retry/repair. | Continue other work. |
-| Inapplicable/low-confidence proposal or negative assessment | Reject affected proposal; preserve domain reasons. | Continue other work. |
-| Provider failure, retry exhaustion, transport or malformed HTTP response | Stop affected operation; retain available observations. | Runtime failure; cancel remaining work, retain existing Audita diagnostic handling. |
-| Deadline, caller cancellation, capacity admission failure | Stop affected operation; no outer retry or fabricated output. | Runtime failure with distinct classified cause. |
-| Invalid settings/profile/schema setup | Fail before processing where detectable. | Configuration error for user input, runtime error for broken embedded assets. |
-
-Zero transient retries produces one ordinary provider failure, not
-`ErrRetriesExhausted`; the latter signals an exhausted **positive** budget.
-Provider failures retain a typed cause. Do not expose raw provider messages through
-user diagnostics: continue Audita's separate secret-redaction boundary. A failed
-logical call may return no result while its observations still record completed
-attempts or an earlier successful generation. Already completed domain results can
-remain in diagnostics; failure must not be presented as a fully corrected output.
-
-## Observation and Report Handoff
-
-The prototype maps library events into Audita-owned records under a short mutex.
-Records contain logical run/role/backend/profile identity, generation and attempt
-indices, dispatch state, queue/generation/retry/wall timing, classified outcomes,
-HTTP status, exhaustion, repair/retry counts, and each usage field's value,
-knownness, and completeness. It omits URLs, credentials, payloads, raw provider
-errors, and prompt text. Identifiers themselves are metadata, not a secret channel.
-
-Use terminal records once for logical totals; retain attempt records for diagnosis
-without adding them to terminal totals. A known zero is distinct from unknown;
-partial totals remain incomplete after unmetered failed attempts. These observations
-are not a billing ledger. Callback code must not wait on its own run's progress.
-
-Production report changes must distinguish logical calls from dispatched provider
-attempts. Replace scheduler utilization fields based on global/proposal/validation
-pools with per-backend admission/active timing. Preserve deterministic ledger and
-validator ordering. Map prompt definition/rendered hashes and selected profile/model
-into request metadata, but do not promise equality with legacy prompt hashes or
-serialize PromptKit's raw event struct as the stable report contract. Update the
-output integration reference, report mapper tests, and downstream migration guide
-when the production representation is implemented.
-
-## Verification and Remaining Handoff
-
-The focused matrix is implemented in the nested module:
-
-| Roadmap scenario | Evidence |
-| --- | --- |
-| Successful assembled path | `go run .`; `TestWorkflowBoundaries/repair_both_roles`; actual Audita domain helpers and both selected profiles. |
-| Presence, overrides, inheritance | `TestConfigurationContract`: omitted role/backend values, explicit zero, null/empty, version, unknown keys, and explicit overrides. |
-| Credentials | Missing/unset and empty references fail; optional null accepted; effective/profile inspection redacted; HTTP authorization verified; no secret/prompt text in observations. `TestProfilesRespectSharedBackendBoundary` rejects competing lookup and capacity bypass. |
-| Both roles repaired | `repair_both_roles`: four attempts, two repairs, one accepted correction. |
-| Repair exhausted | Proposal and assessment exhaustion subtests: bounded counts and selected warning/rejection outcomes. |
-| Semantic boundary | Missing span, missing/duplicate decision indices, negative assessment; no semantic repair loop. |
-| Retry/zero/exhaustion | 429 recovery, zero-budget 503, positive-budget exhaustion after completed proposal; typed error assertions. |
-| Combined budgets | 503 → invalid JSON → repair 503 → valid proposal → assessment: five attempts, two transient retries, one repair. |
-| Shared capacity | `TestSharedCapacityAndRecovery`: caps four and two, both roles, a retry and repair, queue rejection, measured peak equal to cap, later successful call. |
-| Waiting/cancellation/deadline | `TestQueuedCancellationAndDeadline`; `TestDeadlineStopsRetryAfter`: no queued dispatch after cancellation/deadline and a 60-second provider retry delay interrupted by the operation deadline. |
-| Failed-run observations | `TestPartialUsageOnFailedRun`: valid HTTP output with known-zero usage followed by repair failure; nil result, retained events, incomplete known aggregate, correct counts. |
-| Representative assets | `TestRealPromptRenderingParity` compares both rendered message pairs to Audita v1.1.0; `TestSchemaFixturesMatchAudita` compares schema bytes. |
-
-Commands executed from `examples/library-adoption` on Linux amd64 with Go 1.26.8:
-
-```sh
-GOWORK=off go mod download all
-GOWORK=off GOPROXY=off GOSUMDB=off go mod verify
-GOWORK=off GOPROXY=off GOSUMDB=off go run .
-GOWORK=off GOPROXY=off GOSUMDB=off go test -race ./...
-GOWORK=off GOPROXY=off GOSUMDB=off go vet ./...
-```
-
-All passed. The demonstration reports accepted=1, rejected=0, attempts=4,
-transient_retries=0, structural_repairs=2. Module verification reports all modules
-verified. Published tag availability was checked with `git ls-remote --tags` for
-ConfigKit v0.3.1 and PromptKit v0.11.0; successful module acquisition verifies this
-is not merely a local-checkout experiment. The module has no replacements.
-
-The minimum Go 1.25.5 toolchain was also exercised with offline tests and the same
-successful demonstration. The exact installed-toolchain invocation was:
-
-```sh
-GOTOOLCHAIN=local GOWORK=off GOPROXY=off GOSUMDB=off /home/eric/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.25.5.linux-amd64/bin/go test ./...
-GOTOOLCHAIN=local GOWORK=off GOPROXY=off GOSUMDB=off /home/eric/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.25.5.linux-amd64/bin/go run .
-```
-
-An initial attempt to select that cached toolchain through `GOTOOLCHAIN=go1.25.5`
-with checksum verification disabled was rejected by Go's toolchain verifier. Using
-the installed binary with `GOTOOLCHAIN=local` proved offline execution without
-weakening dependency checks. The portable README commands assume an installed
-sufficiently new Go executable on PATH and disable toolchain switching.
-
-From the Audita root, `go test ./...` and
-`go build -o ./bin/audita ./cmd/audita` passed. These check existing production code;
-they do not cover the nested module. Affected relative documentation links,
-inventory coverage, and `git diff --check` were checked separately.
-
-### Findings and Limits
-
-No adoption-blocking upstream API gap was found. Two integration details deserve
-explicit attention: PromptKit's profile GoDoc calls `timeout_seconds` a generation
-deadline, but its built-in HTTP path applies it separately to each attempt; the
-consumer therefore needs the selected total-operation deadline. Also,
-`APIKeyRequired` is an in-memory profile facility, not a profile-YAML field. The
-file-profile design uses the presence of ConfigKit's optional credential reference
-to require local secret resolution; it does not invent a new PromptKit YAML key.
-
-The chosen defaults are proposed operational policy, not measured model-quality or
-cost recommendations. Tests use controlled transport responses and synthetic data;
-they do not establish real provider compatibility, model quality, network behavior,
-throughput, cross-process coordination, complete billing, or release compliance.
-Only the representative LLM-facing subset is implemented in the prototype; the
-inventory specifies the remaining domain fields for the ConfigKit migration.
-Production file discovery, CLI parsing, full module chains, all nine prompts,
-filesystem diagnostics/redaction, and serialized report migration remain their
-assigned production tasks. Those are deliberate scope boundaries, not missing
-claims of completion for the prototype.
-
-The new profile/credential/capacity and deadline choices are explicit above; no
-unresolved upstream requirement prevents starting the ConfigKit implementation
-plan. Production report field names and final runtime wiring are selected in the
-[implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md), following the outcome and observation
-contract here. The coordinated refactor targets both libraries directly; intermediate commits do not require a working legacy runtime.
-
-### Production Implementation Reference
-
-The [implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md) owns ordered production work,
-component changes, tests, and acceptance criteria. The [combined roadmap](library-adoption.md)
-and [configuration roadmap](configkit.md) own the final target. This evidence does
-not require an interim runtime bridge or separately runnable configuration migration.
-
-Retained domain scope includes transcript/glossary schemas, normalization/chunking,
-output encoding, proposals and apply-time checks, deterministic validators, ordered
-modules, LLM-validator batching/cardinality, ledger ordering, and artifact lifecycle.
-The production integration replaces loading, provider execution, prompt rendering,
-and scheduler composition while preserving those responsibilities. Retention and
-timestamp changes remain separate work.
-
-### Distribution Follow-Up
-
-The pinned graph includes ConfigKit, PromptKit, both PromptKit backend catalogs,
-jsonschema/v6, yaml.v3, yaml.v4, x/text, and kr/text (including module/test dependency
-edges). Before distribution, review the actual production dependency graph and
-its license files, including PromptKit/catalog LGPL-3.0-or-later terms. Decide and
-verify the notices, license copies, corresponding library source/modifications,
-and rebuild/relink materials needed for Audita's Go binary/container distribution.
-This unit does not publish binaries or claim that release compliance is complete.
-No upstream relicensing request or library implementation change is required for
-this prototype.
-
-## Selected-Overlay Extension: 2026-09-24
-
-The isolated prototype now pins published ConfigKit v0.4.0. ConfigKit loads
-`overlays/testing.yml` relative to the selected main file; the overlay selects
-complete PromptKit execution profiles from the separate `profiles/` directory.
-The original v0.3.1 observations above are historical and do not prove this
-extension. No production Audita behavior changed.
-
-With Go 1.26.8 on linux/amd64, from `examples/library-adoption/`, these offline
-checks passed with `GOTOOLCHAIN=local GOWORK=off GOPROXY=off GOSUMDB=off`:
-
-```sh
-go test ./...
-go test -race ./...
-go vet ./...
-go run .
-go run . --overlay testing
-go run . --overlay testing --proposal-profile proposal
-```
-
-Each demonstration reported one accepted correction, four attempts, zero
-transient retries, and two structural repairs. The base run selected
-`synthetic-grammar`/`synthetic-review`; testing selected
-`synthetic-grammar-testing`/`synthetic-review-testing`; the explicit proposal
-override restored only `synthetic-grammar`. These are synthetic routing IDs,
-not price, latency, quality, or provider-compatibility measurements.
-
-| Requirement | Consumer evidence |
-| --- | --- |
-| Base, empty/default, testing selection, role overrides, final inheritance, and relative profile resolution | `TestSelectedOverlayConfiguration` loads temporary on-disk layouts and assembles both roles. |
-| Actual base/testing/override HTTP models and repairs | `TestDemonstrationSelectsOutboundModels` captures every request body and matches model IDs to the reported selections and domain outcome. |
-| Missing/invalid selection, version/directive rejection, and ordinary backend-setting validation | `TestOverlayFailuresAndApplicationValidation` checks ConfigKit diagnostic codes and effective backend limits. |
-| Surviving credential resolution, absent/empty failures, null unauthenticated use, and profile-only switching | `TestOverlayCredentialResolutionAndInspection` controls synthetic environment values and observes HTTP Authorization. |
-| Redacted effective output, explanation and metadata origin, profile inspection, and observations | `TestOverlayCredentialResolutionAndInspection` and `TestOverlaySelectionProvenance` inspect safe output and overlay/CLI origins. |
-| Existing retry, repair, domain, capacity, and concurrent-observation behavior | `TestWorkflowBoundaries`, `TestSharedCapacityAndRecovery`, `TestQueuedCancellationAndDeadline`, `TestDeadlineStopsRetryAfter`, and `TestPartialUsageOnFailedRun` pass, including under `-race`. |
-
-Changing a profile does not remove a backend credential reference from the
-effective configuration. ConfigKit validates a surviving reference when only
-profile selection changes. Replacing the reference in an
-overlay resolves only the replacement; explicit null allows unauthenticated use.
-This distinction is part of the selected configuration boundary, not an
-application fallback. Imports and secret-directory bootstrap remain disabled.
-
-The tests use a controlled built-in HTTP transport and synthetic credentials;
-there were no live provider calls. The prototype still covers one representative
-proposal/assessment pair, not all production modules, prompts, CLI paths, or
-diagnostic artifacts. Root `go test ./...` does not run this nested module. No
-upstream API gap appeared in this extension. The [production implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md)
-keeps implementation and release pending.

docs/roadmap/library-boundary.md

@@ -1,269 +0,0 @@
-# Library Adoption: Shared Boundary and Prototype
-
-**Last updated:** 2026-09-24
-
-**Status:** Original boundary-design and offline-prototype unit completed;
-overlay extension and production-planning handoff completed, 2026-09-24.
-The work packages below retain the original scope;
-[decisions, evidence, limitations, and handoff](library-boundary-findings.md)
-record the outcome. The executable prototype was removed after production
-integration; Git history at `590604b` retains it. No publication or upstream
-changes were made in that historical unit.
-
-## Next Unit: Testing Overlays and Production Migration Plan
-
-**Status:** Complete. The [production implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md)
-owns subsequent work; the [overlay findings](library-boundary-findings.md#selected-overlay-extension-2026-09-24)
-record this unit's checks. The original work packages below remain
-historical scope for the completed first unit.
-
-Extend the existing prototype to prove the [selected-overlay contract](configkit.md#selected-overlays-for-testing)
-with ConfigKit v0.4.0, then turn the verified findings into a detailed production
-ConfigKit migration plan. Do not repeat the original inventory or redesign the
-established library boundary without new evidence.
-
-Required work:
-
-- Upgrade only the nested prototype module from ConfigKit v0.3.1 to v0.4.0.
-- Pass an explicit overlay selection through ConfigKit and add `overlays/testing.yml`
-  plus two PromptKit testing profiles. Select both roles and retain one shared
-  finite backend. Synthetic model names demonstrate routing; they do not benchmark
-  real model cost, speed, or quality.
-- Make the offline executable accept overlay and explicit role-profile selections,
-  and show the selected models alongside domain outcomes and retry/repair counts.
-- Verify base/overlay/CLI precedence, role inheritance, invalid selections,
-  surviving credential references, safe inspection, and overlay provenance.
-  Prove the actual HTTP request models for both roles; loading changed strings
-  alone is insufficient evidence.
-- Record new results separately from the historical v0.3.1 findings. Expand the
-  existing ConfigKit roadmap into a concrete production implementation handoff,
-  including final runtime integration and removal of legacy configuration.
-
-Target end state: reviewers can run the prototype with and without the testing
-selection and see both LLM roles switch models. The offline test suite establishes
-that selection, inspection, and execution agree, and the production ConfigKit work
-has bounded tasks with explicit acceptance criteria.
-
-Acceptance criteria:
-
-- The published v0.4.0 dependency is pinned without local replacements; the original
-  no-overlay path and existing integration tests continue to pass.
-- `testing` switches both roles, explicit profile flags override its selections,
-  and omission/empty/`default` retains base selection according to ConfigKit.
-- Invalid overlays fail clearly; inheritance and secret resolution use surviving
-  effective settings. Inspection records overlay origin without disclosing keys.
-- Both selected testing models reach the controlled HTTP transport; structural
-  repair, shared capacity, observations, and Audita domain checks remain active.
-- Updated examples, executable instructions, findings, and a detailed production
-  migration plan are reviewable. Exact verification commands and limitations are
-  recorded, including the fact that root tests do not cover the nested module.
-- Production code, root dependencies, and upstream libraries remain unchanged.
-  No release or live provider call is part of this unit.
-
-This unit ends with a production migration **plan**, not production implementation.
-The ConfigKit → PromptKit → combined release sequence remains unchanged. Imports
-and secret-directory bootstrap remain disabled; PromptKit execution profiles keep
-their existing names and meaning.
-
-## Objective
-
-Define and prove the boundary between Audita, ConfigKit, and PromptKit before
-replacing Audita's production configuration or LLM runtime. This unit covers the
-shared design and representative prototype supporting the
-[coordinated adoption roadmap](library-adoption.md). The
-[ConfigKit roadmap](configkit.md) continues to own the broader configuration scope.
-
-The deliverable is a concrete target contract supported by an offline executable
-prototype, sufficient to implement the ConfigKit migration without subsequently
-redesigning its LLM-facing settings. A successful prototype is not completion of
-either production migration.
-
-## Established Direction
-
-- This is an intentional breaking migration with a migration guide, not legacy
-  configuration support, aliases, or a permanent compatibility mode.
-- ConfigKit owns shared configuration mechanics; PromptKit owns shared prompt and
-  generation mechanics; Audita retains domain meaning and transcript correction.
-- Structural repair is enabled from the outset for proposal and LLM-validator calls.
-  Positive default repair budgets must be selected, not silently left at zero.
-- Transient retries and structural repair are separate. Explicit zero disables
-  transient retries; Audita must not add a second automatic retry loop.
-- One finite concurrency limit per backend protects local capacity and bounds paid
-  API activity. Calls from both roles share that limit. Fine-grained role budgets
-  and an additional global concurrency control are unnecessary.
-- Keep the sequence: boundary/prototype, ConfigKit migration, PromptKit migration,
-  then combined major release. No intermediate public release is planned.
-
-## Scope and Deliverables
-
-| Deliverable | Required result |
-| --- | --- |
-| Configuration inventory and migration map | Every existing setting and invocation option has a proposed destination, replacement, or removal, with rationale. |
-| Boundary specification | One authoritative source for each setting, explicit precedence/defaults, credential flow, runtime conversion, and failure handling. |
-| Representative executable prototype | New-style configuration drives one proposal and one assessment through released libraries and a controlled provider. |
-| Focused behavioral evidence | Retry, repair, capacity, credential, observation, and domain-boundary scenarios below are demonstrated. |
-| Decision and integration handoff | Concrete choices, measured limitations, affected components, removal plan, and next implementation tasks are recorded. |
-
-Do not switch the production CLI to the prototype, migrate every module/prompt,
-redesign transcript/glossary formats, change correction algorithms, modify retention
-or timestamp behavior, or publish a release in this unit. Do not reproduce the
-libraries' full test suites. Upstream changes require a separately scoped task if
-an actual gap is found.
-
-## Work Package 1: Inventory and Decide Ownership
-
-Read the current [configuration](../config.md), [CLI](../cli.md),
-[LLM runtime](../internal/llm-runtime.md), [prompts](../internal/prompts.md),
-[validators](../internal/validators.md), and [output contracts](../integrations/output-files.md).
-Use graph-first discovery to verify the relevant code and tests, especially
-configuration application, prompt construction, structured responses, scheduling,
-and report assembly.
-
-Build a migration table grouped by application/domain settings, invocation state,
-backend settings, execution profiles, output contracts, and inspection. Include
-current environment settings and aliases without treating their existence as a
-requirement to preserve them. Identify report fields whose meanings change when
-one logical generation contains multiple provider attempts.
-
-Resolve these design decisions explicitly:
-
-| Decision | Proposed direction to prove |
-| --- | --- |
-| File selection and version | Audita selects the main configuration and validates a new schema version; specify discovery and the treatment of old versions. |
-| Application versus invocation state | ConfigKit loads persistent settings; Audita parses invocation-only input/output paths and translates explicitly supplied setting flags into supported overrides. |
-| Backend identity | One registration represents the service capacity shared by proposal and validation calls. Avoid separate identities for the same service merely because roles differ. |
-| Endpoint and capacity ownership | Define them once per backend, with finite limits and an explicit policy for waiting capacity/exhaustion. Do not expose endpoint-only unlimited execution accidentally. |
-| Execution profiles | Prefer complete application-owned profiles using PromptKit conventions. Decide their source and selection without duplicating model/settings fields in application configuration. Catalog selection remains a deliberate option. |
-| Role selection and inheritance | Specify how proposal and validation choose profiles, including omission and any inheritance. Do not inherit old behavior solely for compatibility. |
-| Credentials | Prefer one ConfigKit-owned secret-resolution path passed through PromptKit's supported request credential field. Define backend/profile credential association and avoid competing environment lookups. Validate this against profile requirements. |
-| Retry, repair, and deadlines | Assign one owner and explicit defaults for each control. Use positive structural-repair defaults and document combined limits and total-operation scope. |
-| Optional library features | The original prototype omitted imports, selected configuration layers, and secret-directory bootstrap. Selected overlays are now planned for testing; see the [overlay plan](configkit.md#selected-overlays-for-testing). Imports and secret-directory bootstrap remain out. |
-| Inspection | Define effective configuration and selected-profile inspection without implying that one library's snapshot contains the other's complete state. |
-
-Choose concrete field names, example values, defaults, units, and omission/null/zero
-semantics for the prototype. In particular, decide what validation and inspection
-do when configured credentials are unavailable. Classify choices as proposed,
-selected, or unresolved; do not present candidates as implemented contracts.
-
-## Work Package 2: Specify Execution and Reporting Semantics
-
-Document the flow from selected configuration through backend/profile assembly,
-prompt inputs, generation, structural validation/repair, typed decoding, and Audita
-domain validation. Identify which values cross the boundary and which component
-owns each conversion. Keep library types out of unrelated domain code where a
-small existing domain value is sufficient.
-
-Use the current correction-set and validator-decision schemas as representative
-inputs. Reuse domain checks where practical. Select one real proposal/validator
-pair; account for prompt helpers, template variables, shared fragments, and schema
-references rather than testing only an unrelated hello-world prompt.
-
-Record the following distinctions:
-
-- Repair seeks output conforming to its structural contract. Success does not
-  establish semantic correctness or authorize applying a correction.
-- A schema-valid decision set still requires Audita's cardinality and proposal
-  identity checks. Semantic rejection is not automatically another repair request.
-- Exhausted structural repair yields failed content validation; provider failures,
-  retry exhaustion, cancellation, and capacity rejection have separate outcomes.
-- Specify each outcome's intended effect on an Audita section/batch and overall run,
-  including warnings, rejected work, partial domain results, and terminal failures.
-  Preserve domain intent without preserving obsolete transport behavior by accident.
-- For transient retry budget T and structural repair budget R, one logical call can
-  dispatch up to `(T + 1) * (R + 1)` provider attempts. For example, T=2 and R=2
-  permits nine attempts; these illustrative values do not select production defaults.
-- Choose the total-operation deadline scope for a logical proposal or assessment;
-  distinguish it from per-attempt timeouts and whole-process cancellation. Provider
-  retry timing may exceed local backoff, so deadline behavior must be explicit.
-
-Design the Audita observation record and aggregation rules. Include logical-call
-and attempt identity, role/backend correlation, queue/generation/retry timing,
-repair and retry counts, outcomes, and available usage. Preserve unknown/incomplete
-usage rather than inventing zeros or complete costs. Do not add terminal totals to
-attempt totals. Collect events safely across concurrent calls, without blocking
-callbacks on progress by the same run or persisting raw library events as a stable
-Audita schema. Transcript-bearing artifacts remain separately governed by Audita.
-
-## Work Package 3: Build the Bounded Offline Prototype
-
-Use ConfigKit v0.3.1 and PromptKit v0.11.0 as reviewed starting points; verify their
-published availability and APIs before pinning the prototype. Recheck the combined
-Go minimum (the reviewed PromptKit release requires Go 1.25.5). Do not depend on
-sibling checkouts, an active Go workspace, or committed local module replacements.
-
-A proposed home is `examples/library-adoption/` as an explicitly experimental,
-standalone Go module, isolating prototype dependencies from the production binary.
-Confirm this placement during execution. Its README must give exact offline run
-and test commands after dependency acquisition; root `go test ./...` must not be
-claimed to cover a nested module. Keep complete proposed configuration and prompt
-fixtures with it and clearly label them as prototype-only.
-
-The prototype should:
-
-1. Load representative application settings with ConfigKit, using synthetic secret
-   values supplied by the test environment and an application-owned version rule.
-2. Assemble shared backend registrations and proposal/validation profile selections.
-3. Supply representative transcript/proposal inputs to PromptKit definitions and
-   actual response schemas using supported sources.
-4. Use the built-in HTTP generation path with a controlled local endpoint or
-   transport. An injected LLM client alone cannot prove built-in HTTP retry behavior.
-5. Run proposal generation, decode and check candidates, run assessment, and perform
-   the selected Audita decision checks without modifying real transcript files.
-6. Collect selected safe observations and show a compact result understandable to a
-   reviewer, including repaired output and final domain acceptance/rejection.
-
-No paid calls, real credentials, host environment assumptions, persistent caches,
-or general-purpose test framework are needed. Make concurrency and cancellation
-checks deterministic through controlled synchronization. Keep delays bounded and
-use library-supported controls; do not patch library internals to make tests pass.
-
-## Focused Verification Matrix
-
-| Scenario | Evidence required |
-| --- | --- |
-| Successful assembled path | ConfigKit-loaded selections drive both real prompt roles through PromptKit and Audita checks. |
-| Presence, overrides, and inheritance | Representative omission, explicit values, and role selection follow the proposed contract; unknown fields and unsupported versions fail clearly. |
-| Credentials | Required missing/empty references fail as intended; controlled calls receive the chosen synthetic credential; inspection and observations do not expose it. |
-| Structural repair succeeds | Invalid proposal output and invalid assessment output are repaired in their respective workflows; positive budgets are actually exercised. |
-| Repair exhausted | Repeated invalid output produces the selected Audita outcome and accurate accounting, without an unbounded outer retry. |
-| Domain rejection | Structurally valid but unacceptable correction or decision is rejected by Audita, demonstrating the semantic boundary. |
-| Transient retry and explicit zero | An eligible temporary status recovers; zero makes one attempt. Exhaustion retains a useful classified cause. |
-| Combined repair and retry | A repaired generation encountering a transient failure respects both budgets and reports distinct counts. |
-| Shared capacity | Concurrent calls from both roles, including retry/repair activity, stay within one selected backend cap; test a representative local cap of four and a finite API cap. |
-| Waiting, cancellation, and deadline | Cancellation/deadline stops pending work and retry waits; capacity exhaustion has the intended application outcome and later calls can still proceed. |
-| Failed-run observations | Completed work remains observable after later failure; unknown usage, known zero, and aggregate counts are mapped correctly. |
-
-Tests should protect Audita's integration decisions and important assembled behavior.
-Rely on PromptKit's tests for exhaustive HTTP-status, backoff, and scheduler details;
-rely on ConfigKit's tests for its parser and presence machinery. Use race testing for
-new concurrent observation collection. Keep consumer checks offline and credential-free.
-
-## Completion Criteria and Handoff
-
-This unit is complete only when:
-
-- The settings/ownership table and migration inventory are concrete enough to start
-  the ConfigKit migration, including file/profile sources, CLI scope, credentials,
-  defaults, finite backend limits, positive repair budgets, and deadline policy.
-- The offline prototype and focused matrix demonstrate the selected boundary with
-  both libraries together, including both LLM roles and Audita domain checks.
-- Exact verification commands, results, limitations, and unresolved upstream gaps
-  are recorded. Missing evidence is not reported as successful integration.
-- No adoption-critical decision remains hidden in prototype code. If a gap prevents
-  settling the boundary, record it and revise the plan before declaring readiness.
-- The existing Audita production behavior remains intact in this unit. Temporary
-  code is clearly isolated and has a removal/integration destination during the
-  production migrations; no second supported runtime is introduced.
-- A component-level follow-up identifies code to replace, domain code to retain,
-  tests to update, documentation/migration-guide work, and direct integration of
-  the final configuration and PromptKit runtime.
-- Licensing/distribution follow-up for the selected dependency graph is identified
-  for the later release stage; this prototype does not claim release compliance.
-- Roadmap links and examples resolve, appropriate checks pass, and commits contain
-  only this unit's work. Significant settled architectural choices may be recorded
-  in an ADR under the [documentation policy](../policy/documentation.md), while
-  implementation status stays in the roadmaps.
-
-Retain the overall adoption order unless evidence or the other planned large changes
-justifies revising it. Completing this unit enables detailed production migration;
-it does not authorize an intermediate release or require unrelated runtime fixes.

docs/roadmap/prompt-quality.md

@@ -0,0 +1,103 @@
+# Prompt Quality Roadmap
+
+**Updated:** 2026-11-11
+
+**Status:** Topic 1 resolved in ADR 0003; topics 2–6 remain for discussion.
+Work through the remaining topics in order. Their recommendations are starting
+points for discussion, not newly adopted restrictions or guarantees.
+
+## Baseline and Intended Direction
+
+The review of revision `6d34602` covered all eleven
+[prompt definitions](../internal/prompts.md), their shared instructions, and
+the context and response handling for proposals, validation, and repair.
+It was a design review, not a measurement of live-model quality.
+
+Retain the strengths: conservative transcript editing, explicit literal-span and
+deletion semantics, distinct glossary context and protection, full before/after
+validation, independent repair conversations with withdrawal, and native
+PromptKit/ConfigKit prompt replacement. Improve consistency across the three
+roles, useful rejection feedback, and maintainability.
+
+## Discussion and Work Order
+
+### 1. Module Focus and Editorial Acceptance — Resolved
+
+The intentional distinction between requested module focus and acceptance of
+minor editorial cleanup is recorded in
+[ADR 0003](../adr/0003-module-focus-and-editorial-acceptance.md). The maintainer's
+testing found that strict scope instructions also suppress desirable edits.
+Apply the accepted distinction throughout the remaining prompt work.
+
+### 2. Make Rejection Reasons Useful for Repair
+
+Validator explanations now become repair feedback, but current instructions give
+little guidance about producing actionable reasons.
+
+**Recommendation:** ask for a concise description of the specific change, the
+applicable criterion, and relevant evidence, within the validator's remit.
+For example: removing "might" turns a tentative statement into a definite one;
+preserve the speaker's uncertainty. Start with the existing `reason` field.
+Discuss examples and sufficient detail before considering schema expansion.
+
+### 3. Make Repair a Reconsideration of the Edit's Merits
+
+Withdrawal is already explicit. Clarify when the model should use it and how it
+should respond when the original evidence remains insufficient.
+
+**Recommendation:** ask the model to reassess the correction from the supplied
+evidence, retain the module's focus and the accepted editorial allowance, and
+withdraw unsupported proposals. Address the risk that numerical confidence
+feedback merely encourages raising the score.
+Do not automatically prohibit confidence-only revisions: legitimate reassessment
+is possible. Discuss and evaluate that behavior before adding a business rule.
+Retain the agreed full-history conversation model and existing repair lifecycle.
+
+### 4. Simplify Instructions and Improve Examples
+
+Restrictions and examples recur across proposal, validation, and repair assets;
+the grammar prompt repeats its word-substitution boundary several ways.
+
+**Recommendation:** distinguish shared editing principles, requested module focus,
+validator acceptance criteria, and task-specific response contracts. Use small
+shared fragments where they reduce drift. Replace some repetitive example lists
+with contextual contrasts, such as
+accidental repetition versus deliberate emphasis. Preserve useful distinctions;
+shorter prompts alone are not the objective. Discuss what belongs in shared
+fragments and what remains local to each definition.
+
+### 5. Evaluate Editorial Quality
+
+Rendering, schema, and controlled-response tests establish integration behavior,
+but do not establish the quality of model editorial judgments.
+
+**Recommendation:** assemble a modest evaluation set containing both needed edits
+and text that should remain unchanged. Include ambiguous glossary matches,
+intentional repetition, meaningful uses of apparent filler, punctuation that
+changes meaning, and repairs that should be withdrawn. Compare unnecessary edits,
+missed corrections, validator disagreement, and repair outcomes using independent
+editorial assessment; validator approval alone is insufficient evidence.
+
+Capture candidate examples during topics 1–4 and establish a baseline before
+changing prompts. Discuss representative models, expected outcomes, and how to
+run evaluations. Keep model-dependent evaluation separate from the default
+offline test suite; no numerical quality gate is selected here.
+
+### 6. Revisit Broader Product Choices
+
+Use the preceding decisions and evaluation evidence to discuss these in order:
+
+1. **Grammar naming and scope:** the current module is close to copy editing,
+   with an isolated article exception. Decide whether its name and scope convey
+   the intended requested work, preserving the accepted editorial allowance.
+2. **Glossary/homophone overlap:** assess the benefit of their overlapping remit
+   and repeated glossary passes before changing the default sequence.
+3. **Language and examples:** decide whether spoken English and campaign-specific
+   examples are the right bundled defaults, and how broadly those defaults
+   should apply.
+4. **Meaning-reversal policy:** the guard can also exclude a genuine correction
+   of a mistranscription. Initially retain the conservative default while
+   explicitly evaluating that tradeoff.
+
+These are product discussions, not selected renames, broader editing permissions,
+language-support promises, or changes to validation policy.

docs/roadmap/remediation.md

@@ -1,161 +0,0 @@
-# Maintainability Audit: Findings and Recommended Changes
-
-**Reviewed:** 2026-09-25, source commit `011b021`.
-**Scope:** Recent partial-decision reconciliation, validation context, prompt
-alignment, and request-local reference changes, including related existing code.
-**Status:** R27–R30 addressed; see the resolution record below. Previous findings and resolution records remain in Git
-history through `011b021`.
-
-## Architecture Assessment
-
-The recent changes fit Audita's existing boundaries. Proposal generation,
-validation, prompt assets, and outcome reporting already have suitable owners;
-this audit does not recommend a new common package or a broad refactor.
-
-The strongest opportunities are shared prompt instructions and request-scoped
-validation context preparation. Two smaller improvements concern recovery-reason
-classification and partial-result assembly; both predate the latest commits.
-These are bounded maintenance recommendations, not new release gates or changes
-to correction policy, response acceptance, or reporting semantics.
-
-## R27 — P2: Consolidate Shared Prompt Instructions
-
-**Category:** Repeated behavioral-contract text; risk of future drift.
-
-**Evidence:** The four [proposal prompts](../../internal/prompts/assets/prompts/modules.grammar.proposal.yaml)
-repeat literal source-span matching, request-local identity, replacement-text,
-source-based proposal, and confidence instructions. The three active
-[validator prompts](../../internal/prompts/assets/prompts/validators.editorial_review.yaml)
-repeat candidate-reference, supplemental-context, and verdict-confidence guidance.
-Recent contract changes required coordinated edits across these assets. The
-[prompt registry](../../internal/prompts/registry.go) already provides a shared
-hardening fragment supplied through the role-bound adapter.
-
-**Recommended change:** Extract genuinely common passages into embedded fragments
-under `internal/prompts/assets/shared`, following the existing fragment-supply
-approach. Keep the fragments owned by `internal/prompts` and use the existing
-PromptKit rendering path. Keep module-specific examples, replacement-policy
-instructions, protected-name exceptions, and semantic criteria in their individual
-prompt definitions. Do not merge similar-looking rules with different meanings.
-
-**Acceptance:** Common instructions have one maintained source and appear in all
-intended rendered prompts. The existing module and validator distinctions remain
-intact, including glossary replace-all behavior and the spoken-word protected-name
-exception. Focused rendering checks cover fragment inclusion and representative
-module-specific guidance without requiring exact-prose snapshots or introducing
-a separate templating framework.
-
-## R28 — P2: Prepare Validation Context Once Per Request
-
-**Category:** Repeated computation and overlapping segment lookup.
-
-**Evidence:** [BuildLLMValidationRequest](../../internal/framework/validators/llm_validators.go)
-already indexes transcript segments, but
-[validationContext](../../internal/framework/validators/llm_context.go) scans the
-transcript again for each candidate. It also calls
-[NewProtectedVocabulary](../../internal/framework/validators/protected_terms.go)
-for each candidate, rebuilding the same vocabulary and compiling its matching
-expression repeatedly. This is duplicated preparation rather than copied code.
-
-**Recommended change:** Prepare a segment-position lookup and protected vocabulary
-once per validation request, then pass that prepared context into the existing
-context-selection helper. Keep the implementation within `framework/validators`.
-Continue selecting glossary evidence for each candidate individually because its
-proposed replacement can mention different terms. A process-wide cache or new
-context-management package is unnecessary for this cleanup.
-
-**Acceptance:** Candidates in one validation request reuse the prepared lookup and
-vocabulary. Context still consists of the available immediate neighbors within the
-current chunk and relevant glossary entries in glossary order. Candidate-specific
-replacement text still participates in glossary selection. Existing optional-context
-trimming, token estimation, and oversized-input handling retain their behavior.
-Verify these outcomes with focused behavioral tests rather than assertions about
-private helper call counts or unmeasured performance guarantees.
-
-## R29 — P3: Share Execution-Recovery Classification
-
-**Category:** Duplicate reporting rule; predates the latest commits.
-
-**Evidence:** [Proposal generation](../../internal/framework/proposal_generation/generate.go)
-and [LLM validation](../../internal/framework/validators/llm_validators.go)
-independently translate structural-repair and transient-retry counts into
-`output_repaired` and `service_recovered` reasons. The conversion is the same in
-both locations; the surrounding success and domain-outcome decisions differ.
-
-**Recommended change:** Place a small conversion helper in the existing
-`framework/outcomes` package and use it from both callers. Keep the decision to
-record recoveries at the call sites, along with domain-specific reasons such as
-filtered validator decisions. Do not combine proposal and validation orchestration
-or move domain-success classification into this helper.
-
-**Acceptance:** Both callers use the same execution-count conversion. Existing
-reason ordering, successful-operation reporting, and domain-specific additions
-remain intact. A partially unavailable validation batch continues to record its
-failure and execution counts without acquiring recovery records merely because a
-repair or retry occurred. Existing outcome tests should continue to protect these
-distinctions.
-
-## R30 — P3: Centralize Partial Validator Result Assembly
-
-**Category:** Repeated early-return construction; predates the latest commits.
-
-**Evidence:** Several early returns in
-[LLMBackedValidator.Validate](../../internal/framework/validators/llm_validators.go)
-repeat nested slice appends to combine immediate decisions, oversized-input
-decisions, and decisions from completed model batches, together with accumulated
-operation outcomes. This makes it easier for a future failure path to omit facts
-already collected by the validator.
-
-**Recommended change:** Use a small local result-building helper to assemble the
-partial result consistently. Keep error handling, batching, success-path ordering,
-and cardinality enforcement explicit. A general-purpose result-aggregation package
-is not needed.
-
-**Acceptance:** Cancellation and failure paths retain the same previously collected
-decisions and operations. Result ordering and cardinality behavior remain unchanged;
-the helper does not enforce complete cardinality on interrupted work. Retain the
-existing partial-progress and fatal-failure coverage, adding tests only for a
-material gap exposed by the refactor.
-
-## Boundaries to Preserve
-
-- Keep proposal and validator reference mapping separate. Proposals can target the
-  same segment repeatedly; duplicate validator decisions make that candidate
-  unavailable. Similar indexing arithmetic alone does not justify a generic
-  reference-management abstraction.
-- Keep distinct protected-term policy checks separate. They already share the
-  vocabulary implementation and intentionally apply different policies.
-- Preserve exact source-span matching, request-local references, batching, and
-  partial-success behavior. Consolidation is not a reason to strengthen contracts
-  or broaden the accepted correction scope.
-
-## Review Verification and Limits
-
-- This is a source-level maintainability audit, not a finding of demonstrated
-  production failures or a measured performance assessment.
-- No application tests were rerun for the original read-only audit; its roadmap
-  update used documentation link and whitespace checks. Implementation validation
-  is recorded below.
-- Future remediation should run focused behavioral tests and the broader suite
-  appropriate to the actual change, following the testing policy. No live-provider
-  evaluation or new evaluation framework is required by these recommendations.
-- The findings above describe the audited baseline. Implementation and validation
-  are recorded below; no release publication is included.
-
-## Resolution Record
-
-Implemented as focused changes within the existing packages. Proposal and validator
-reference mapping and distinct protected-term policies remain separate.
-
-| Finding | Resolution and evidence |
-| --- | --- |
-| R27 | Common proposal and validation instructions live in two embedded shared fragments, supplied through the existing role-bound PromptKit adapter. Individual YAML definitions retain policy differences and examples. Rendering tests check fragment inclusion once per applicable prompt and representative module-specific guidance. |
-| R28 | Validation request construction builds one segment-position lookup and protected vocabulary, reused by context selection for every candidate. A new test verifies that two replacements of the same source span receive their own relevant glossary entries. Existing neighbor, glossary-order, chunk-boundary, and budget tests pass. |
-| R29 | Both proposal generation and validation use `outcomes.ExecutionRecoveries`. Call sites still control success and domain-specific recovery reasons. Existing tests cover combined recoveries and failed validation with repair counts but no recovery record. |
-| R30 | A local result builder combines collected decisions and operation outcomes for partial returns and completed validation. Sorting and full cardinality checks remain outside it. Existing fatal-batch, partial-progress, runner, and reporting tests pass. |
-
-Validation: `go test ./...` passed, including PromptKit preparation, partial-decision
-reconciliation, subprocess reports, and fatal-progress coverage. Documentation
-links and whitespace checks passed. No live model evaluation or performance
-measurement was performed; the changes make no new model-quality or latency
-promise.

docs/roadmap/resilience.md

@@ -1,290 +0,0 @@
-# Resilient Processing and Focused Run Reports
-
-**Last updated:** 2026-09-24
-
-**Status:** Implemented. This document records the selected behavior and user
-intent. Concrete design decisions and completion evidence are in
-[historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/a83a518/docs/roadmap/implementation.md).
-
-## Purpose and User Intent
-
-Audita should reliably produce a useful transcript even when its LLM services
-cannot improve it. Exhausted retries or unusable model responses must not turn
-an otherwise processable transcript into a failed production run.
-
-> Failure of every LLM operation across every stage and chunk still produces a
-> successful output containing the deterministically normalized transcript, with
-> no LLM corrections applied. Partial success preserves as many fully validated,
-> applicable corrections as possible.
-
-Deterministic normalization remains intentional and may change segment layout,
-identifiers, and text before LLM work begins. Output uses the selected transcript
-encoder; byte-for-byte preservation of the original input and mapping corrections
-back to pre-normalization segmentation are not requirements.
-
-The overriding goal is to minimize how much useful processing is lost because of
-one problematic transcript segment. A stage/chunk work unit is an attribution
-boundary, not an all-or-nothing transaction.
-
-Existing reports contain useful information, but there are no compatibility
-obligations for reporting or debug output. Reuse existing machinery only when it
-makes the implementation simpler and clearer; preservation is not itself a goal.
-Internal structures and measurements must serve Audita's processing workflow.
-The reporting package adapts those outcomes to structured and human-facing
-presentations, rather than reshaping processing around a reporting convenience.
-
-## Historical Baseline and Implemented Change
-
-The [pipeline](../internal/pipeline.md), [LLM integration](../integrations/openai-compatible-llm.md),
-[report assembly](../internal/diagnostics-reporting.md), and
-[artifact lifecycle](../operations.md) describe current behavior.
-
-Before this work, exhausted structural repairs could become warnings and skipped
-proposals or rejected validation batches. Other model runtime failures canceled
-peer work, stopped subsequent modules, and prevented final transcript output.
-Successful repairs appeared in execution observations rather than a dedicated
-recovery classification. Detailed artifacts were written during ordinary runs
-and could later be removed by retention. The working transcript was re-chunked
-between modules.
-
-This feature changed those behaviors. It builds on the completed
-[library adoption](library-adoption.md) and [review remediation](remediation.md).
-Fatal cancellation remains necessary; unsuccessful model work must be separated
-from failures that actually require cancellation of the run.
-
-## Fixed Chunks and Ordered Stages
-
-Normalize first, then partition the transcript once. Preserve chunk boundaries,
-segment membership, segment identity, and ordering throughout LLM processing.
-Text evolves as accepted corrections are applied. Recombine chunks in original
-order after the LLM stages finish.
-
-A stage is a configured module instance. Repeated instances of the same module
-have distinct identities. Proposal generation and each validator are operations
-within a stage; validation may use multiple batches within a chunk. A work unit
-is one stage instance applied to one chunk.
-
-Preserve the overall stage sequence: finish a stage across its chunks before
-advancing to the next stage. Concurrent chunk work shares PromptKit's backend
-capacity. Failure in one unit does not prevent other chunks or later stages
-from executing.
-
-Retain operator control over chunk size and the current defaults. Production
-experience indicates that chunk size affects model latency nonlinearly and that
-useful settings are well below backend context limits. Tuning is an empirical
-operator decision. Do not add automatic headroom calculations, cross-profile
-sizing, adaptive repartitioning, or automatic tuning in this feature. A later
-operation that cannot process its input follows the same safe error handling;
-it does not silently alter chunk boundaries. Validation batching within a chunk
-remains supported.
-
-Independent whole-pipeline traversal by chunks and domain-aware response repair
-are explicitly deferred in [future work](future.md). Read-only neighboring
-context, cross-chunk edits, and transcript-wide restructuring are outside this
-unit, without becoming permanent prohibitions on future capabilities.
-
-## Partial Success and Failure Isolation
-
-- Keep bounded transport retries, structural repairs, operation deadlines, and
-  shared backend capacity. Completion comes from safe fallback, not unlimited
-  attempts or an outer retry loop around PromptKit.
-- Apply a correction only after it passes every required validator and the
-  application checks. Failed validation must never be treated as approval.
-- If a validation batch fails, exclude its affected candidates while allowing
-  other candidates to continue through the remaining validators. Preserve fully
-  validated, applicable corrections from successful batches in the same unit.
-- Track candidates by stable proposal identity. Batch membership can change
-  between validators; equal batch numbers do not establish candidate identity.
-- A failed proposal-generation operation leaves its chunk unchanged for that
-  stage because there are no reliable proposals to salvage. Failures later in
-  validation need not discard unrelated successful candidates.
-- Preserve earlier stages' corrections and other chunks' successful work.
-  Record partial success explicitly; a unit can apply corrections and have errors.
-- Continue despite model-operation failures, including exhausted repairs/retries,
-  unusable model decisions, provider/transport failures, local operation deadlines,
-  and admission failures. An operation need not exhaust its attempt budget to fail.
-- A valid empty proposal list or valid assessments rejecting all corrections is
-  successful processing. Correction count alone does not determine failure.
-- Keep safe filtering of defective proposals. Do not retry ordinary editorial
-  rejections. For now, an unusable validator decision set excludes the affected
-  candidates and records an error after existing permitted recovery. New bounded
-  feedback/regeneration for domain-invalid responses belongs to future work.
-- Retain fatal treatment for invalid input/configuration, internal defects,
-  explicit run cancellation, and inability to produce/write the transcript.
-  Caller cancellation is distinct from a local model-operation timeout.
-- Completed runs with model errors return success. Required report-write failures
-  are an additional fatal output condition when reporting is enabled, as below.
-
-PromptKit owns transport, transient retries, structural repair, and admission.
-Audita owns domain acceptance, partial outcomes, fallback, and classification.
-ConfigKit owns configuration resolution. Debug and reporting choices must not
-change correction decisions, retry budgets, or continuation.
-
-## Errors, Recoveries, and Debug
-
-Classify by eventual outcome and impact. These are three reporting categories;
-debug is evidence, not a failure severity. Whether execution continues is a
-separate property.
-
-| Category | Meaning | Representative cases |
-| --- | --- | --- |
-| Errors | Intended work could not complete reliably, or a fatal run-level operation failed. Affected candidates are excluded; other corrections can succeed. | Exhausted repair; unavailable provider; unusable validation decisions; operation deadline. |
-| Recoveries | A problem was handled successfully through retries, repair, or safe filtering. No operator intervention is implied. | Invalid output repaired; transient service failure recovered; defective proposals safely discarded. |
-| Debug | Detailed evidence of processing and ordinary decisions. | Proposals, applied corrections, validator decisions, prompts/responses, individual attempts, execution traces. |
-
-Normal editorial disagreement belongs in debug. A validator correctly rejecting
-a meaning-changing edit is expected behavior. A proposal referring to nonexistent
-original text is defective; safely filtering it is a recovery. An unresolved
-missing/duplicate decision-index response is an error, not a recovery.
-
-Record an operation's eventual outcome once. Several failed attempts followed by
-success produce a consolidated recovery. Attempts ending in failure contribute
-to error details, not additional recoveries. Earlier operations that recovered
-remain recorded if a later operation introduces an error in the same unit.
-
-Separate output-quality recovery, defective-proposal filtering, and service
-recovery with structured reasons. Network instability must not look like a prompt
-defect. Do not introduce an arbitrary warning threshold or a fourth category.
-
-### Counting and Processing Volume
-
-- Count error-bearing work units once per stage/chunk, consolidating underlying
-  operation failures as details. A partially successful unit still counts once.
-- Count recoveries once per recovered operation. Aggregate defective-proposal
-  filtering per proposal response, retaining affected-proposal counts as detail.
-  Attempts and individual discarded proposals are not independent incidents.
-- Keep work-unit coverage separate from operation/recovery counts. Show processing
-  volume with explicitly labeled denominators; do not divide recovered-operation
-  counts by work-unit counts and call that a recovery rate.
-- Report fatal run-level errors separately from the stage/chunk grid when they
-  cannot be attributed to a work unit. Do not invent a chunk to accommodate them.
-- Derive YAML records, Markdown summaries, and CLI counts from actual processing
-  outcomes with deterministic ordering, rather than independently calculating them.
-
-## Production Outputs, Placement, and Lifecycle
-
-Reporting is enabled by default. The ordinary bundle is:
-
-- `errors.yml`: structured error-bearing units, their underlying failures, and
-  applicable run-level failures.
-- `recoveries.yml`: structured recovered operations and pertinent counts.
-- `report.md`: a concise human-facing summary of outcome, corrections, processing
-  volume, errors, recoveries, and their locations in the pipeline.
-
-Write all three documents, including empty event lists for uneventful completed
-runs. Use Audita-owned schemas with safe explanations and stable reason codes;
-retain run, stage-instance, chunk, operation, and validator/batch identities where
-applicable. The implementation plan specifies the versioned schemas; neither old
-report formats nor raw library structures define the new output contract.
-
-Place reports beside the output transcript. Retain transcript-to-stdout support
-with an explicit report-directory selection, defaulting to the invocation working
-directory. Preserve the existing overwrite convention: a new run can replace files
-at its selected destinations. Do not add a mandatory fresh-directory restriction
-or compatibility exports.
-
-Before model work, create initial versions of all three reports carrying a common
-run identifier and explicit `in_progress` status (rendered as prose in Markdown).
-Fail immediately if initialization fails. Also check the transcript destination;
-creating neighboring reports does not prove that an existing transcript file is
-writable. Preflight must not prematurely destroy an existing transcript.
-
-Finalize all required outputs and check every final write. Initial write success
-cannot guarantee later success if space or permissions change. Failure to write
-the transcript or finalize a required report returns nonzero and must not erase
-an already produced transcript. Where possible, finalize available reports with
-an explicit failed status on fatal termination. Abrupt termination may leave
-`in_progress`; elaborate crash-recovery machinery is not required.
-
-Provide an option to disable reporting entirely. It suppresses all three files
-(`errors.yml`, `recoveries.yml`, and `report.md`), including initialization and
-final writes, while retaining the brief CLI summary and independently selectable
-debug output. Disabled reporting must not create or require a writable report
-destination, and must not remove reports from earlier runs.
-Transcript output failures remain fatal regardless of reporting selection.
-
-Ordinary reports survive independently of debug cleanup. Reporting configuration
-and finalization must not depend on retaining a debug run directory.
-
-## Debug and Internal Boundaries
-
-Production issue records are compact. Full responses, transcript excerpts,
-correction lists, and complete validation decisions are opt-in debug evidence.
-Use a single ConfigKit-backed debug boolean with a `--debug` CLI override. Debug
-artifacts may use JSON where useful. Preserve configured-secret redaction in every
-presentation.
-
-Debug-off prevents detailed artifact persistence; writing and later deleting
-those files is insufficient. In-memory domain state needed to process candidates
-correctly is not debug output. Debug and ordinary reporting are independent
-selections and do not alter processing behavior.
-
-There is no obligation to retain `--report-json`, old artifact layouts, parallel
-exports, or old retention settings. Reuse code only where useful to the new
-workflow. Enabled debug output is retained on success or failure; disabled debug
-creates no debug directory. This supersedes the retention question in the
-[runtime follow-up](runtime-behavior.md). The legacy `never` behavior is not the
-meaning of the new reporting-disable option. Optional debug-write failures produce
-a safe stderr diagnostic without changing correction decisions or the run exit
-status; ordinary report and transcript-write failures retain their fatal semantics.
-
-## Deterministic Human-Facing Presentation
-
-Use the CLI style:
-
-> Completed: 18 corrections applied; 3 work units with errors; 7 recoveries.
-
-Do not say that all error-bearing units were skipped: some apply valid corrections.
-Include report locations when reporting is enabled and the files exist. Send the
-summary to stderr so stdout remains exclusively available for transcript output.
-Disabled reporting does not suppress the summary or fatal-error messages.
-
-Keep `report.md` concise and high-level. Use separate error and recovery matrices
-with stages as columns and chunks as rows. Include every chunk in fixed order;
-retain configured stage order and distinct labels for repeated module instances.
-No automatic width detection, thresholds, adaptive omission, or table splitting.
-A wide or long table is acceptable.
-
-The error matrix counts error-bearing work units: each attempted cell is 0 or 1.
-Recovery cells count recovered operations and can exceed 1. An error cell may
-coexist with recoveries and successfully applied corrections in the same unit.
-Distinguish completed work with zero events from unattempted work; do not portray
-canceled/unavailable processing as clean completion. Include totals, processing
-volume, and a short reason breakdown. Detailed inspection belongs in YAML or debug.
-
-## Target Acceptance Criteria
-
-- Total LLM failure still returns success and the encoded normalized transcript,
-  provided required output writes succeed.
-- Mixed-success runs preserve independently validated, applicable corrections
-  within the same stage/chunk as a failed batch. No candidate bypasses a required
-  validator; later validators handle survivors by stable proposal identity.
-- Subsequent stages and unaffected chunks execute after recoverable failures.
-  Fatal errors and explicit cancellation stop and join active work appropriately.
-- Chunk boundaries and identity remain fixed, with operator-selected sizing and
-  unchanged defaults; final recombination preserves ordering.
-- Valid no-change/editorial-rejection outcomes are successful. Repaired/filtered
-  output and unresolved failures receive distinct classifications and counts.
-- YAML, Markdown, and CLI agree on partial outcomes and totals; error matrices
-  count affected work units, recovery matrices count recovered operations.
-- With reporting enabled, all three reports are initialized before model work,
-  finalized and retained, including empty lists. Initial or final required-output
-  write failures produce nonzero exits without destroying completed transcript output.
-- Reporting can be disabled without requiring its destination. Debug can be enabled
-  independently; neither selection changes processing outcomes. Debug-off writes
-  no detailed debug artifacts, and stdout transcript output remains supported.
-- Reports use the fixed deterministic layout without adaptive presentation logic.
-- Meaningful controlled-provider tests cover exhausted recovery, failed validation
-  batches with successful survivors, total failure, fatal cancellation, output
-  failures, and reporting/debug selections. Preserve domain safeguards, capacity
-  limits, and redaction.
-- Canonical CLI, configuration, operations, integration, internal, and architecture
-  documentation describes the implemented final behavior.
-
-## Implementation Reference
-
-The product decisions are settled. The [historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/a83a518/docs/roadmap/implementation.md) defines
-the selected settings and precedence, YAML schemas, counts and ordering, interrupted
-work presentation, destination checks, and output finalization. It also owns the
-ordered implementation stages and validation work. This document remains the
-reference for the desired behavior and its acceptance criteria.

docs/roadmap/runtime-behavior.md

@@ -1,18 +0,0 @@
-# Runtime Behavior Decisions
-
-**Last updated:** 2026-09-24
-
-The documentation migration identified existing behaviors for separate product
-consideration. The resilience implementation resolved the diagnostics-retention
-question; the input-timestamp question remains open.
-
-- Resolved: legacy `auto`/`always`/`never` retention settings were removed.
-  Debug is explicitly enabled with `diagnostics.debug` or `--debug`, creates no
-  directory when disabled, and retains its directory on every outcome when enabled.
-- Resolved: [configuration](../config.md) now treats explicit zero as disabling
-  transient retries or structural repair independently; PromptKit performs both.
-- Decide whether missing or null input timestamps should be rejected; current
-  decoding is documented in the [input contract](../integrations/transcript-glossary-files.md).
-
-These decisions are independent of the completed documentation migration and
-release workflow.

docs/roadmap/span-deletion.md

@@ -1,203 +0,0 @@
-# Consistent Span Deletion
-
-**Last updated:** 2026-09-25
-
-**Status:** Implemented. This document owns the desired behavior and user intent.
-The [historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/60e2fe7/docs/roadmap/implementation.md)
-records the concrete steps, selected implementation details, and completion
-evidence.
-
-## Purpose and User Intent
-
-Align proposal prompts, the LLM response schema, internal validation, and
-application behavior so legitimate text-span deletions can be considered and
-applied through the ordinary correction workflow. An empty replacement should
-not trigger structural repair merely because it is empty, nor invalidate other
-usable corrections returned alongside it.
-
-This is a consistency fix within Audita's current editing scope. It does not
-authorize whole-segment removal, broaden module responsibilities, or introduce
-new recovery machinery. The accepted [resilience behavior](resilience.md) remains
-in effect, including partial success, fixed chunks, and validation before mutation.
-
-## Historical Baseline (`0b6cd98`)
-
-The source reviewed at `0b6cd98` contains a mismatch:
-
-- The [spoken-word prompt](../../internal/prompts/assets/prompts/modules.spoken_word.proposal.yaml)
-  permits removing fillers and asks for the exact affected span and replacement,
-  without explaining how to represent deletion. Grammar permits punctuation and
-  spacing changes, which can also naturally involve deletion.
-- The shared [correction response schema](../../internal/framework/responseschema/assets/correction_set.v1.json)
-  requires `corrected_text` to have at least one character. Every built-in proposal
-  module uses that schema. An empty replacement invalidates the response before
-  Audita evaluates individual proposals.
-- PromptKit performs bounded structural repair. If repair does not produce a
-  valid response, the proposal operation fails and yields no candidates, including
-  otherwise valid proposals in the same response. The current resilience path
-  records the error and continues other work.
-- [CorrectionProposal](../../internal/framework/proposals/proposal.go) already
-  allows empty replacement text. The
-  [preview/application logic](../../internal/framework/proposals/preview.go)
-  supports literal span deletion when the resulting segment remains nonblank.
-- Domain shape checks currently reject whitespace-only original spans, although
-  the response schema permits them and grammar prompts permit spacing cleanup.
-  This is another restriction to align with the target contract below.
-- The validator named `non_empty_corrected_text` actually checks the resulting
-  segment, not the replacement string. Both this check and application prevent
-  a segment from becoming empty or whitespace-only. Application changes segment
-  text; it does not remove segment records.
-
-A temporary controlled-provider review reproduced whole-response rejection for
-an empty replacement alongside a valid correction, and immediate schema acceptance
-for a space-only replacement. Existing proposal tests confirm internal support for
-partial deletion and rejection of blank resulting segments. These observations
-explain a plausible production failure mechanism; they do not establish the cause
-of any particular historical incident without its payload and running version.
-
-## Target Correction Contract
-
-- `original_text` identifies an existing, nonempty literal span in the current
-  target segment. Whitespace-only spans are eligible; an empty string identifies
-  no source span and remains invalid. Matching and ambiguity checks still apply
-  under the module's replacement policy: `require_unique` for grammar, spoken-word,
-  and homophones; `replace_all` for glossary.
-- `corrected_text` remains a required string. An empty string means delete the
-  identified span; it does not mean remove the segment record or skip validation.
-  Missing fields and non-string values remain structurally invalid.
-- After applying a correction, the segment must contain non-whitespace text.
-  Enforce this using the source segment and replacement result in Audita, not a
-  minimum replacement length in the structural schema.
-- Every accepted deletion passes the same required validators as other edits in
-  its module, including confidence, protected terms, editorial review, and meaning
-  preservation where applicable. Empty replacement is neither automatic approval
-  nor an automatic rejection.
-- Application preserves segment identity, speaker, timing, membership, ordering,
-  and fixed chunk boundaries. Recheck applicability against text produced by
-  earlier accepted corrections, retaining existing conflict handling.
-- Preserve literal replacement behavior. Prompts should select spans and
-  replacements that handle adjacent whitespace and punctuation appropriately;
-  this feature does not add automatic trimming or a second normalization pass.
-  Neither side of a correction is rejected solely for containing only whitespace.
-  For example, reducing a uniquely identified run of two spaces to one space may
-  be appropriate; validity still depends on the resulting text and domain checks.
-
-Preserve the intended safeguards and outcomes, not every detail of the current
-implementation. Validator ordering, internal structure, and payload construction
-may change when needed to achieve this consistent contract. Existing behavior or
-a passing test does not justify retaining a conflicting restriction.
-
-Illustrative cases:
-
-| Segment | Original span | Replacement | Intended handling |
-| --- | --- | --- | --- |
-| `uh hello` | `uh ` | empty string | Structurally valid; may produce `hello` after required validation. |
-| `uh hello` | `uh hello` | `hello` | Remains a valid representation of the same cleanup, subject to validation. |
-| `hello  world` | two spaces | one space | Eligible spacing correction, subject to unique matching and required validation. |
-| `uh` | `uh` | empty string | Structurally valid proposal, then filtered because the resulting segment would be blank. |
-| `hello world` | `hello world` | spaces only | Filtered because the resulting segment would be blank. |
-
-These examples describe eligibility and mechanical results, not unconditional
-editorial approval. An unchanged segment or valid empty correction list remains
-a successful no-change outcome.
-
-## Prompt and Module Alignment
-
-Review relevant prompt definitions for consistency and edit only those needing
-clarification. Where needed, explain empty-string deletion, whitespace-only spans,
-and the resulting-segment limit with a concise, module-appropriate example. The
-model should omit a correction that would leave a blank segment rather than invent
-padding or replacement content. Consistent guidance is the goal; adding deletion
-language to every prompt is not a requirement.
-
-Retain each module's existing scope:
-
-- Spoken-word cleanup can propose appropriate filler or dysfluency deletion while
-  preserving substantive content and intentional emphasis.
-- Grammar can propose permitted punctuation or spacing deletion; allowing an
-  empty replacement does not authorize word removal or spoken-word cleanup.
-- Glossary and homophone modules retain their existing correction purposes.
-  Shared deletion syntax does not grant them new editorial responsibilities.
-
-Review the active LLM-validator prompts and their input construction as well as
-proposal prompts. Validators must understand the before/after effect of deletion
-and assess it under their existing criteria. A correct negative editorial decision
-remains ordinary processing, not a defect that should be regenerated until approved.
-
-The resulting-segment validator's name and documented identity should describe
-that responsibility accurately, rather than imply that the replacement string
-itself must be nonempty. Preserve the existing blank-result failure reason and
-safeguard while making that deliberate identity change; current chain position
-and preview implementation are not independent product requirements.
-
-## Outcomes and Reporting
-
-A legitimate deletion is an ordinary correction. Empty replacement alone must
-produce neither structural repair nor a recovery classification. If another
-problem required successful repair or filtering, retain that actual recovery.
-
-A schema-valid proposal that would blank its stage-input segment is a defective
-proposal handled through existing safe filtering. Preserve the
-`empty_resulting_segment` reason
-and consolidated `proposals_filtered` recovery behavior; other usable proposals
-in the response continue through required validation. Ordinary editorial rejection
-remains debug evidence rather than a model error or filtering recovery.
-
-A stage can propose several edits to one segment in the same response. Each edit
-is evaluated against the stage input, then approved edits are applied sequentially.
-If a proposal was applicable to that input but an earlier accepted edit makes it
-unsafe, skip it as an apply-time conflict. Do not count that conflict as a defective
-proposal, model error, or filtering recovery. For example, in `"uh um"`, deleting
-`"uh "` and deleting `"um"` each leaves text individually; after the first deletion,
-the second must be skipped to prevent a blank result. Retain the skipped decision
-in debug evidence. The existing runner already distinguishes this situation.
-
-Debug evidence must accurately retain the empty replacement and the corresponding
-validation/application outcome. Ordinary reports retain their existing counts and
-purpose; no new report schema, incident category, or deletion-specific counter is
-needed. Unrelated structural defects may still exhaust PromptKit repair and produce
-an error for the operation, as today.
-
-## Acceptance Criteria
-
-- A controlled valid response containing an empty replacement reaches Audita's
-  domain validation without structural repair solely due to that empty string.
-- A permitted span deletion can pass the required validators and reach the final
-  transcript while preserving segment metadata and fixed chunk membership.
-- A mixed response can apply an approved deletion and another approved correction;
-  an empty replacement does not invalidate the whole response.
-- A proposal that would blank its stage-input segment is filtered independently,
-  retains the existing reason, and does not prevent unrelated valid candidates
-  from succeeding. A proposal made unsafe only by an earlier accepted edit is
-  skipped without adding an error or filtering recovery; a blank result is still
-  prevented and the conflict remains visible in debug evidence.
-- A uniquely matching whitespace-only original span can reach validation and
-  application. Empty originals remain invalid, ambiguous matches remain subject
-  to module policy, and whitespace-only resulting segments remain disallowed.
-- Protected-term and meaning-changing deletions remain subject to their normal
-  rejection rules. No candidate bypasses required validation.
-- A deletion needing no recovery counts as an ordinary applied correction; actual
-  repair/filtering and editorial rejection retain their existing classifications.
-  Debug evidence represents the empty replacement faithfully.
-- Schema and domain tests distinguish an empty string from missing/non-string
-  replacement values and distinguish empty replacement from blank resulting text.
-- Prompt guidance and validator naming express the same contract as the code.
-  Tests protect outcomes rather than exact prompt prose or incidental formatting.
-
-Use deterministic, offline controlled responses for behavioral integration tests;
-no live-provider or paid evaluation is a prerequisite. Representative production
-examples can inform prompt quality without expanding this into an evaluation
-framework or guaranteeing that models always follow the instructions.
-
-## Deferred Work
-
-[Whole-segment removal](future.md#whole-segment-removal) is only potential future
-work and first requires deciding whether its benefit warrants implementation.
-Domain-aware regeneration and independent whole-pipeline traversal also remain
-in [future.md](future.md). This feature changes neither retry budgets nor the
-Audita/PromptKit ownership boundary and requires no upstream library feature.
-
-Implementation sequencing and concrete names belong to the
-[historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/60e2fe7/docs/roadmap/implementation.md).
-The target remains consistent deletion of spans within surviving segments, with
-no new operator controls or report types.

examples/README.md

@@ -0,0 +1,82 @@
+# Maintained examples
+
+Build Audita from the repository root with Go 1.27 or newer. The commands below
+assume the executable is on `PATH`. Each project selects its main file from its
+own directory, which also determines companion resources and overlay context.
+All models, credentials, names, and endpoints are illustrative.
+
+## Local processing
+
+From `examples/local`, edit `prompts.yml` to match a reachable OpenAI-compatible
+local service and its model. Then run:
+
+```sh
+audita config validate --config config.yml
+audita process --config config.yml --output corrected.json transcript.json
+```
+
+Processing makes model requests. Reports are written beside the selected output
+unless disabled. For an offline validator preview, from the same directory:
+
+```sh
+audita promptkit show prepared audita/validators.meaning_reversal_review \
+  --config config.yml --profile local \
+  --var "PayloadJSON=$(cat validation-candidate.json)" \
+  --var 'TranscriptDescriptionBlock='
+```
+
+To preview the repair instruction and its output schema without inference:
+
+```sh
+audita promptkit show prepared audita/modules.grammar.repair \
+  --config config.yml --profile local \
+  --var 'RepairRequestJSON={"proposal_ref":1,"correction":{"id":1,"original_text":" ","corrected_text":"","confidence":0.9},"findings":[]}'
+```
+
+These previews render supplied data without inference. The native command help
+and [CLI reference](../docs/cli.md) describe additional inspection and validation.
+
+## Service and overlay
+
+From `examples/service`, edit the synthetic endpoint and models in `prompts.yml`.
+Set `AUDITA_EXAMPLE_KEY` to your service credential before a real request. Inspect
+without a provider call:
+
+```sh
+audita config validate --config config.yml --overlay testing
+audita promptkit show profile service-test --config config.yml
+```
+
+The example does not promise a provider's model availability, price, or quality.
+
+## Edit a prompt and run again
+
+From `examples/prompt-edit`, inspect the operator replacement:
+
+```sh
+audita promptkit show prompt audita/modules.grammar.proposal --config config.yml
+```
+
+Edit its message in `prompts.yml`, repeat the inspection, and run `audita process
+--config config.yml --output corrected.json transcript.json` against a configured
+local service. Each invocation captures the files anew.
+
+## Shared glossary library
+
+From `examples/campaigns`, `first.yml` and `second.yml` each consume the common
+`shared.yml` through the companion `glossary.yml`. Inspect each configuration:
+
+```sh
+audita config validate --config first.yml
+audita config validate --config second.yml
+```
+
+With a local service configured, process either campaign:
+
+```sh
+audita process --config first.yml --output first-output.json transcript.json
+audita process --config second.yml --output second-output.json transcript.json
+```
+
+Edit `prompts.yml` for a local service before processing either campaign. The
+first uses separate party and spell corrections; the second selects only party.

examples/campaigns/first.yml

@@ -0,0 +1,8 @@
+version: 3
+llm: {proposal_profile: local}
+glossaries: [party, spells]
+pipeline:
+  stages:
+    - {id: names, module: glossary, glossaries: [party]}
+    - {id: magic, module: glossary, glossaries: [spells]}
+    - {module: grammar}

examples/campaigns/glossary.yml

@@ -0,0 +1,4 @@
+config:
+  imports:
+    - path: shared.yml
+      required: true

examples/campaigns/prompts.yml

@@ -0,0 +1,5 @@
+profiles:
+  - id: local
+    endpoint: http://localhost:11434/v1
+    model: example-model
+    api_key_required: false

examples/campaigns/second.yml

@@ -0,0 +1,7 @@
+version: 3
+llm: {proposal_profile: local}
+glossaries: [party]
+pipeline:
+  stages:
+    - {id: names, module: glossary}
+    - {module: grammar}

examples/campaigns/shared.yml

@@ -0,0 +1,12 @@
+party:
+  entries:
+    - id: lyra
+      name: Lyra
+      category: character
+      description: A fictional adventurer.
+spells:
+  entries:
+    - id: shield
+      name: Shield
+      category: spell
+      aliases: [Ward]

examples/campaigns/transcript.json

@@ -0,0 +1,9 @@
+[
+  {
+    "id": 1,
+    "speaker": "Narrator",
+    "start": 0,
+    "end": 2,
+    "text": "Lyra raises a ward before the journey."
+  }
+]

examples/local/config.yml

@@ -0,0 +1,8 @@
+version: 3
+llm:
+  proposal_profile: local
+pipeline:
+  stages:
+    - module: glossary
+    - module: grammar
+glossaries: [party]

examples/local/glossary.yml

@@ -0,0 +1,7 @@
+party:
+  entries:
+    - id: jesters
+      name: Jesters
+      category: faction
+      description: A traveling group of performers.
+      aliases: [Jester]

examples/local/prompts.yml

@@ -0,0 +1,5 @@
+profiles:
+  - id: local
+    endpoint: http://localhost:11434/v1
+    model: example-model
+    api_key_required: false

examples/local/transcript.json

@@ -0,0 +1,9 @@
+[
+  {
+    "id": 1,
+    "speaker": "Narrator",
+    "start": 0,
+    "end": 2,
+    "text": "The gestures gather beside the stage."
+  }
+]

examples/local/validation-candidate.json

@@ -0,0 +1 @@
+[{"correction_index":1,"original_text":"not open","corrected_text":"open","original_segment_text":"The door is not open.","corrected_segment_text":"The door is open."}]

examples/minimal-config.yml

@@ -1,12 +0,0 @@
-version: 2
-backends:
-  local:
-    endpoint: http://127.0.0.1:11434/v1
-    concurrency: 1
-llm:
-  proposal_profile: local-proposal
-  validation_profile: local-validation
-pipeline:
-  modules: [grammar]
-output:
-  schema: bare-segments

examples/overlays/testing.yml

@@ -1,3 +0,0 @@
-llm:
-  proposal_profile: service-proposal-testing
-  validation_profile: service-validation-testing

examples/production-config.yml

@@ -1,40 +0,0 @@
-version: 2
-backends:
-  service:
-    endpoint: https://openrouter.ai/api/v1
-    credential: AUDITA_SERVICE_KEY
-    concurrency: 2
-    queue_capacity: 1024
-llm:
-  proposal_profile: service-proposal
-  validation_profile: service-validation
-  transient_retries: 2
-  repair_attempts: 2
-  operation_timeout: 15m
-pipeline:
-  modules: [glossary, homophones, glossary, spoken_word, grammar]
-output:
-  schema: audita-v1
-chunking:
-  # Requires at least this many normalized segments; omit for automatic chunking.
-  target_sections: 8
-  max_section_tokens: 8192
-  min_section_tokens: 2048
-normalization:
-  max_segment_gap: 4.0
-  ellipsis_gap: 3.5
-  max_segment_duration: 60.0
-  max_segment_tokens: 2048
-thresholds:
-  glossary: 0.8
-  homophones: 0.8
-  spoken_word: 0.8
-  grammar: 0.8
-context:
-  description: "General context for domain vocabulary and speaker names."
-reporting:
-  enabled: true
-  stdout_dir: .
-diagnostics:
-  debug: false
-  work_dir: /tmp/audita

examples/profiles/local-proposal.yaml

@@ -1,7 +0,0 @@
-id: local-proposal
-backend: local
-model: replace-with-local-model
-temperature: 0
-max_tokens: 2048
-top_p: 1
-timeout_seconds: 120

examples/profiles/local-validation.yaml

@@ -1,7 +0,0 @@
-id: local-validation
-backend: local
-model: replace-with-local-model
-temperature: 0
-max_tokens: 1024
-top_p: 1
-timeout_seconds: 120

examples/profiles/service-proposal-testing.yaml

@@ -1,7 +0,0 @@
-id: service-proposal-testing
-backend: service
-model: replace-with-testing-model
-temperature: 0
-max_tokens: 2048
-top_p: 1
-timeout_seconds: 120

examples/profiles/service-proposal.yaml

@@ -1,7 +0,0 @@
-id: service-proposal
-backend: service
-model: replace-with-provider-model
-temperature: 0
-max_tokens: 2048
-top_p: 1
-timeout_seconds: 120

examples/profiles/service-validation-testing.yaml

@@ -1,7 +0,0 @@
-id: service-validation-testing
-backend: service
-model: replace-with-testing-model
-temperature: 0
-max_tokens: 1024
-top_p: 1
-timeout_seconds: 120

examples/profiles/service-validation.yaml

@@ -1,7 +0,0 @@
-id: service-validation
-backend: service
-model: replace-with-provider-model
-temperature: 0
-max_tokens: 1024
-top_p: 1
-timeout_seconds: 120

examples/prompt-edit/config.yml

@@ -0,0 +1,8 @@
+version: 3
+llm:
+  proposal_profile: local
+pipeline:
+  stages:
+    - module: glossary
+    - module: grammar
+glossaries: [party]

examples/prompt-edit/glossary.yml

@@ -0,0 +1,7 @@
+party:
+  entries:
+    - id: jesters
+      name: Jesters
+      category: faction
+      description: A traveling group of performers.
+      aliases: [Jester]

examples/prompt-edit/prompts.yml

@@ -0,0 +1,23 @@
+profiles:
+  - id: local
+    endpoint: http://localhost:11434/v1
+    model: example-model
+    api_key_required: false
+collections:
+  audita:
+    prompts:
+      - id: modules.grammar.proposal
+        messages:
+          - role: system
+            content: Correct only clearly supported grammatical errors.
+          - role: user
+            content: |
+              {{ .ProposalContract }}
+              {{ .HardeningPolicy }}
+              {{ .TranscriptDescriptionBlock }}
+              Glossary: {{ .GlossaryJSON }}
+              Transcript: {{ .SectionJSON }}
+        output:
+          format: json
+          validation_mode: json_schema
+          schema_path: correction_set.v1.json

examples/prompt-edit/transcript.json

@@ -0,0 +1,9 @@
+[
+  {
+    "id": 1,
+    "speaker": "Narrator",
+    "start": 0,
+    "end": 2,
+    "text": "The gestures gather beside the stage."
+  }
+]

examples/service/config.yml

@@ -0,0 +1,7 @@
+version: 3
+llm:
+  proposal_profile: service-proposal
+  validation_profile: service-review
+pipeline:
+  stages:
+    - module: grammar

examples/service/overlays/testing.yml

@@ -0,0 +1,3 @@
+llm:
+  proposal_profile: service-test
+  validation_profile: service-test

examples/service/prompts.yml

@@ -0,0 +1,16 @@
+backends:
+  - id: service
+    endpoint: https://example.invalid/v1
+    api_key_env: AUDITA_EXAMPLE_KEY
+    concurrency_limit: 2
+    queue_capacity: 8
+profiles:
+  - id: service-proposal
+    backend: service
+    model: example-proposal-model
+  - id: service-review
+    backend: service
+    model: example-review-model
+  - id: service-test
+    extends: {id: service-proposal}
+    model: example-testing-model

examples/service/transcript.json

@@ -0,0 +1,9 @@
+[
+  {
+    "id": 1,
+    "speaker": "Narrator",
+    "start": 0,
+    "end": 2,
+    "text": "The gestures gather beside the stage."
+  }
+]

examples/tiny-glossary.yaml

@@ -1,6 +0,0 @@
-glossary:
-  - name: Audita
-    aliases:
-      - audita
-    category: product
-    summary: The Audita transcript correction CLI.

go.mod

@@ -1,20 +1,29 @@
-module gitea.maximumdirect.net/eric/audita
+module gitea.maximumdirect.net/eric/audita/v3
 
-go 1.25.5
+go 1.27.0
 
 require (
-	gitea.maximumdirect.net/eric/ConfigKit v0.4.0
-	gitea.maximumdirect.net/eric/promptkit v0.11.0
+	go.maximumdirect.net/ckconfig v0.7.0
+	go.maximumdirect.net/ckprompt v0.7.0
+	go.maximumdirect.net/commandkit v0.6.0
+	go.maximumdirect.net/configkit v1.2.0
+	go.maximumdirect.net/promptkit v0.21.0
+	go.maximumdirect.net/releasekit v0.9.0
 	gopkg.in/yaml.v3 v3.0.1
 )
 
 require (
-	gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1 // indirect
-	gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0 // indirect
+	github.com/inconshreveable/mousetrap v1.1.0 // indirect
 	github.com/kr/pretty v0.3.1 // indirect
 	github.com/rogpeppe/go-internal v1.14.1 // indirect
 	github.com/santhosh-tekuri/jsonschema/v6 v6.0.2 // indirect
+	github.com/spf13/cobra v1.10.1 // indirect
+	github.com/spf13/pflag v1.0.9 // indirect
+	github.com/yuin/goldmark/v2 v2.1.6 // indirect
 	go.yaml.in/yaml/v4 v4.0.0-rc.6 // indirect
+	golang.org/x/mod v0.40.0 // indirect
 	golang.org/x/text v0.14.0 // indirect
 	gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c // indirect
 )
+
+tool go.maximumdirect.net/releasekit/cmd/releasekit

go.sum

@@ -1,14 +1,9 @@
-gitea.maximumdirect.net/eric/ConfigKit v0.4.0 h1:fo+vKff3zTGeWqJIA38NtT84b6OUP//9ZmBH3lFuKgk=
-gitea.maximumdirect.net/eric/ConfigKit v0.4.0/go.mod h1:tYWpsrbLyu05r8+1MapWp5fN6ZrX9I8hU2xEPedYmYk=
-gitea.maximumdirect.net/eric/promptkit v0.11.0 h1:x7JguOUiInPVXK0GEitjyoRFqqvcuSTjYUvqJ+whtik=
-gitea.maximumdirect.net/eric/promptkit v0.11.0/go.mod h1:0zEBVlJJC+ldDdXazAgybYBXNSe74vwFx5dyOuSos/w=
-gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1 h1:S2/Q/JDE+m8Ca3pDhAjVbfYrdlEhs9blj0STgNopHo0=
-gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1/go.mod h1:a3VBbh9oaGXD6ruxhtwHj+AWW6DY/SSyby1QtMmYSUo=
-gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0 h1:Y0EXc3eh12eKW2NrOviVqdk3oBo6UUjopt1YAa1B3Oc=
-gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0/go.mod h1:mtgD1E0SGm0e/I8Ffhz+AYX7GN7RKUWJXehNFIKHs4Y=
+github.com/cpuguy83/go-md2man/v2 v2.0.6/go.mod h1:oOW0eioCTA6cOiMLiUPZOpcVxMig6NIQQ7OS05n1F4g=
 github.com/creack/pty v1.1.9/go.mod h1:oKZEueFk5CKHvIhNR5MUki03XCEU+Q6VDXinZuGJ33E=
 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/inconshreveable/mousetrap v1.1.0 h1:wN+x4NVGpMsO7ErUn/mUI3vEoE6Jt13X2s0bqwp9tc8=
+github.com/inconshreveable/mousetrap v1.1.0/go.mod h1:vpF70FUmC8bwa3OWnCshd2FqLfsEA9PFc4w1p2J65bw=
 github.com/kr/pretty v0.2.1/go.mod h1:ipq/a2n7PKx3OHsz4KJII5eveXtPO4qwEXGdVfWzfnI=
 github.com/kr/pretty v0.3.1 h1:flRD4NNwYAUpkphVc1HcthR4KEIFJ65n8Mw5qdRn3LE=
 github.com/kr/pretty v0.3.1/go.mod h1:hoEshYVHaxMs3cyo3Yncou5ZscifuDolrwPKZanG3xk=
@@ -20,10 +15,31 @@ github.com/pkg/diff v0.0.0-20210226163009-20ebb0f2a09e/go.mod h1:pJLUxLENpZxwdsK
 github.com/rogpeppe/go-internal v1.9.0/go.mod h1:WtVeX8xhTBvf0smdhujwtBcq4Qrzq/fJaraNFVN+nFs=
 github.com/rogpeppe/go-internal v1.14.1 h1:UQB4HGPB6osV0SQTLymcB4TgvyWu6ZyliaW0tI/otEQ=
 github.com/rogpeppe/go-internal v1.14.1/go.mod h1:MaRKkUm5W0goXpeCfT7UZI6fk/L7L7so1lCWt35ZSgc=
+github.com/russross/blackfriday/v2 v2.1.0/go.mod h1:+Rmxgy9KzJVeS9/2gXHxylqXiyQDYRxCVz55jmeOWTM=
 github.com/santhosh-tekuri/jsonschema/v6 v6.0.2 h1:KRzFb2m7YtdldCEkzs6KqmJw4nqEVZGK7IN2kJkjTuQ=
 github.com/santhosh-tekuri/jsonschema/v6 v6.0.2/go.mod h1:JXeL+ps8p7/KNMjDQk3TCwPpBy0wYklyWTfbkIzdIFU=
+github.com/spf13/cobra v1.10.1 h1:lJeBwCfmrnXthfAupyUTzJ/J4Nc1RsHC/mSRU2dll/s=
+github.com/spf13/cobra v1.10.1/go.mod h1:7SmJGaTHFVBY0jW4NXGluQoLvhqFQM+6XSKD+P4XaB0=
+github.com/spf13/pflag v1.0.9 h1:9exaQaMOCwffKiiiYk6/BndUBv+iRViNW+4lEMi0PvY=
+github.com/spf13/pflag v1.0.9/go.mod h1:McXfInJRrz4CZXVZOBLb0bTZqETkiAhM9Iw0y3An2Bg=
+github.com/yuin/goldmark/v2 v2.1.6 h1:igy0q9JcqovoFXFx/XjtU8sHVhcUHavPj2sA3EoKJUE=
+github.com/yuin/goldmark/v2 v2.1.6/go.mod h1:G6M4/qOFtfn01/o14BU1UR2Lo5N3S9Qo7xCuz/sHjGQ=
+go.maximumdirect.net/ckconfig v0.7.0 h1:jRmKqgReLYIRHJl7Pr4+TlucifFirGANcsoC+5WrW7A=
+go.maximumdirect.net/ckconfig v0.7.0/go.mod h1:ZBKCi0Z72+C6kQV+1HJHXFGcZTc11FYyaH1pQDSZFl8=
+go.maximumdirect.net/ckprompt v0.7.0 h1:iACE8fZIaq9+/DF8zt1C1JwVPgZh12F2xJmlin2r45U=
+go.maximumdirect.net/ckprompt v0.7.0/go.mod h1:IuCIwxqKVjpZ+Rcd2JO2xmJ1QVtmPki5dV5PnzbD8CY=
+go.maximumdirect.net/commandkit v0.6.0 h1:4PHhMIlZuuvreIxZhUazeweg6zoYixEvhM9LJnkbGNA=
+go.maximumdirect.net/commandkit v0.6.0/go.mod h1:ZS98DewKNVBygKVDoh5MFD09CnPlP37dS9pVsID5Eoc=
+go.maximumdirect.net/configkit v1.2.0 h1:c4tDJ6Xeh/Jg90UZplLxsnf500lvrZBVj0E3i1ysir8=
+go.maximumdirect.net/configkit v1.2.0/go.mod h1:s1zLJ9GGB/1Q4a+aOHMLISonJxWFgNWpA6SpPlOafeA=
+go.maximumdirect.net/promptkit v0.21.0 h1:Ws4y28lnW+lIXAq4tGhXVFnQV/6AqkDChhg8knIZFrU=
+go.maximumdirect.net/promptkit v0.21.0/go.mod h1:pi9acdCi80HWyzY+XYwRvMEoCiTcDWKyeBh3mzHdIFo=
+go.maximumdirect.net/releasekit v0.9.0 h1:sK+Aoj6gS6ATU/1reocjwBekp4YETYENwkcX5ti6mrE=
+go.maximumdirect.net/releasekit v0.9.0/go.mod h1:QE4BLrAhVJTzi+/YTcVl21K/qZp9ojRLg5kuoy3Zb44=
 go.yaml.in/yaml/v4 v4.0.0-rc.6 h1:1h7H1ohdUh93/FyE4YaDa1Zh64K6VVbjF4K6WUxMtH4=
 go.yaml.in/yaml/v4 v4.0.0-rc.6/go.mod h1:aZqd9kCMsGL7AuUv/m/PvWLdg5sjJsZ4oHDEnfPPfY0=
+golang.org/x/mod v0.40.0 h1:hUv+3cXcdRHz08UmSiOob7sadHig73uo5bkXxQ/tvUs=
+golang.org/x/mod v0.40.0/go.mod h1:0/weTWkPWGBikyTWAX3dkjVztMmBA5hM0DH6BElSupE=
 golang.org/x/text v0.14.0 h1:ScX5w1eTa3QqT8oi6+ziP7dTV1S2+ALU0bI+0zXKWiQ=
 golang.org/x/text v0.14.0/go.mod h1:18ZOQIKpY8NJVqYksKHtTdi31H5itFRjB5/qKTNYzSU=
 gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=

internal/cli/app_wiring.go

@@ -0,0 +1,110 @@
+package cli
+
+import (
+	"context"
+	"fmt"
+	"net/http"
+	"reflect"
+	"strings"
+
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/config"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/framework/llm"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/prompts"
+	"go.maximumdirect.net/ckconfig"
+	"go.maximumdirect.net/ckprompt"
+	commandkit "go.maximumdirect.net/commandkit"
+	ck "go.maximumdirect.net/configkit"
+	pk "go.maximumdirect.net/promptkit"
+	"go.maximumdirect.net/releasekit/buildinfo"
+)
+
+type invocationState struct {
+	engines []engineEntry
+	client  *http.Client
+}
+type engineEntry struct {
+	selection ckconfig.Selection
+	engine    *pk.Engine
+}
+
+func loadApplication(ctx context.Context, selection ckconfig.Selection, _ struct{}, _ *invocationState) (*ck.Result[config.Config], error) {
+	if err := ctx.Err(); err != nil {
+		return nil, err
+	}
+	var source ck.Source
+	if selection.Config.Set {
+		if strings.TrimSpace(selection.Config.Value) == "" {
+			return nil, fmt.Errorf("--config requires a nonempty path")
+		}
+		source = ck.File(selection.Config.Value)
+	} else {
+		source = ck.SearchConfig("audita", ck.Searches(ck.WorkingDirectory(), ck.UserConfigDirectory(), ck.UnixSystemDirectories()))
+	}
+	return config.Load(ck.Input{Source: source}, selection.Overlay.Value, selection.Overrides...)
+}
+
+func loadPromptEngine(ctx context.Context, selection ckconfig.Selection, input struct{}, state *invocationState) (*pk.Engine, error) {
+	loaded, err := loadApplication(ctx, selection, input, state)
+	if err != nil {
+		return nil, err
+	}
+	var client *http.Client
+	if state != nil {
+		client = state.client
+	}
+	return llm.NewEngine(ctx, loaded, client)
+}
+
+func capturePromptEngine(ctx context.Context, selection ckconfig.Selection, input struct{}, state *invocationState) (*pk.Engine, error) {
+	if state != nil {
+		for _, entry := range state.engines {
+			if reflect.DeepEqual(entry.selection, selection) {
+				return entry.engine, nil
+			}
+		}
+	}
+	engine, err := loadPromptEngine(ctx, selection, input, state)
+	if err != nil {
+		return nil, err
+	}
+	if state != nil {
+		state.engines = append(state.engines, engineEntry{selection: selection, engine: engine})
+	}
+	return engine, nil
+}
+
+func buildApplication(extra ...commandkit.Declaration) (*commandkit.App, error) {
+	return buildApplicationWithClient(nil, extra...)
+}
+
+func buildApplicationWithClient(client *http.Client, extra ...commandkit.Declaration) (*commandkit.App, error) {
+	appScope := ckconfig.FromConfigKit("app", "Audita application settings.", loadApplication)
+	appScope.Features.Overrides = true
+	promptScope := ckprompt.ConfigScope(loadPromptEngine)
+	configCommand := ckconfig.Command(ckconfig.Suite[struct{}, *invocationState]{NewState: func() *invocationState { return &invocationState{client: client} }, Scopes: []ckconfig.Scope[struct{}, *invocationState]{appScope, promptScope}})
+	definitions := ckprompt.WithNamespaces(ckprompt.FromEngine(capturePromptEngine), pk.Namespaces{})
+	definitions.NewState = func() *invocationState { return &invocationState{client: client} }
+	definitions = ckprompt.WithRequestValidation(definitions, capturePromptEngine, func(_ context.Context, seed ckprompt.ValidationRequest, _ struct{}, _ *invocationState) (pk.RunRequest, error) {
+		return applicationPromptRequest(seed.Request, seed.Namespaces), nil
+	})
+	definitions = ckprompt.WithRequestPreparation(definitions, capturePromptEngine, func(_ context.Context, seed ckprompt.PreparationRequest, _ struct{}, _ *invocationState) (pk.RunRequest, error) {
+		return applicationPromptRequest(seed.Request, seed.Namespaces), nil
+	})
+	definitions = ckprompt.WithSmokeTesting(definitions, capturePromptEngine, nil)
+	declarations := []commandkit.Declaration{configCommand, commandkit.Completion("audita"), processCommand()}
+	declarations = append(declarations, ckprompt.Declarations(definitions)...)
+	declarations = append(declarations, extra...)
+	return commandkit.New(commandkit.Identity{Name: "audita", Version: buildinfo.Version()}, declarations...)
+}
+
+// applicationPromptRequest supplies instructions only for Audita's maintained prompts.
+func applicationPromptRequest(request pk.RunRequest, namespaces *pk.Namespaces) pk.RunRequest {
+	id := request.PromptID
+	if !strings.Contains(id, "/") && namespaces != nil && namespaces.Prompt != "" {
+		id = namespaces.Prompt + "/" + id
+	}
+	if _, ok := prompts.LookupMetadata(id); ok {
+		request.Vars = prompts.WithSharedVariables(request.Vars)
+	}
+	return request
+}

internal/cli/app_wiring_test.go

@@ -0,0 +1,232 @@
+package cli
+
+import (
+	"bytes"
+	"context"
+	"encoding/json"
+	"io"
+	"net/http"
+	"os"
+	"path/filepath"
+	"strings"
+	"testing"
+
+	"go.maximumdirect.net/ckconfig"
+	"go.maximumdirect.net/ckprompt"
+	commandkit "go.maximumdirect.net/commandkit"
+	pk "go.maximumdirect.net/promptkit"
+)
+
+func TestNativeConfigurationAndResourceCommands(t *testing.T) {
+	dir := t.TempDir()
+	file := filepath.Join(dir, "config.yml")
+	if err := os.WriteFile(file, []byte("version: 3\ncontext:\n  description: example\n"), 0644); err != nil {
+		t.Fatal(err)
+	}
+	app, err := buildApplication()
+	if err != nil {
+		t.Fatal(err)
+	}
+	for _, tc := range []struct {
+		args     []string
+		contains string
+	}{
+		{[]string{"--help"}, "audita"},
+		{[]string{"version"}, "audita"},
+		{[]string{"process", "--help"}, "transcript"},
+		{[]string{"config", "show", "--scope", "app", "--config", file}, "example"},
+		{[]string{"promptkit", "list", "prompts", "--config", file}, "audita/modules.grammar.proposal"},
+	} {
+		var out, stderr bytes.Buffer
+		result := app.Execute(context.Background(), tc.args, commandkit.Streams{Out: &out, Err: &stderr})
+		if result.Status != 0 || !strings.Contains(out.String(), tc.contains) {
+			t.Errorf("%v: status=%d out=%q err=%q", tc.args, result.Status, out.String(), stderr.String())
+		}
+	}
+}
+
+func TestNativeConfigurationSelectionsAndComparison(t *testing.T) {
+	dir := t.TempDir()
+	first, second := filepath.Join(dir, "first.yml"), filepath.Join(dir, "second.yml")
+	for name, data := range map[string]string{first: "context:\n  description: before\n", second: "context:\n  description: after\n"} {
+		if err := os.WriteFile(name, []byte(data), 0644); err != nil {
+			t.Fatal(err)
+		}
+	}
+	app, err := buildApplication()
+	if err != nil {
+		t.Fatal(err)
+	}
+	var out, stderr bytes.Buffer
+	outcome := app.Execute(context.Background(), []string{"config", "diff", "--details", "--check", "--scope=app", "--config", first, "--against-config", second, "--set=/context/description=\"left\"", "--against-set=/context/description=\"right\""}, commandkit.Streams{Out: &out, Err: &stderr})
+	if outcome.Status != 3 || !strings.Contains(out.String(), "left") || !strings.Contains(out.String(), "right") {
+		t.Fatalf("status=%d output=%q err=%q", outcome.Status, out.String(), stderr.String())
+	}
+	out.Reset()
+	stderr.Reset()
+	outcome = app.Execute(context.Background(), []string{"config", "show", "--scope=app", "--config", filepath.Join(dir, "missing.yml")}, commandkit.Streams{Out: &out, Err: &stderr})
+	if outcome.Status == 0 {
+		t.Fatalf("missing file accepted: %s", out.String())
+	}
+}
+
+func TestExplicitEmptyConfigurationPathFails(t *testing.T) {
+	app, err := buildApplication()
+	if err != nil {
+		t.Fatal(err)
+	}
+	var out, stderr bytes.Buffer
+	result := app.Execute(context.Background(), []string{"config", "show", "--scope=app", "--config="}, commandkit.Streams{Out: &out, Err: &stderr})
+	if result.Status == 0 {
+		t.Fatal("explicit empty path accepted")
+	}
+}
+
+func TestPromptConfigurationComparisonAcquiresEqualSelectionsIndependently(t *testing.T) {
+	dir := t.TempDir()
+	main := filepath.Join(dir, "config.yml")
+	if err := os.WriteFile(main, []byte("version: 3\n"), 0600); err != nil {
+		t.Fatal(err)
+	}
+	resource := filepath.Join(dir, "prompts.yml")
+	writeProfile := func(model string) {
+		t.Helper()
+		if err := os.WriteFile(resource, []byte("profiles: [{id: local, model: "+model+"}]\n"), 0600); err != nil {
+			t.Fatal(err)
+		}
+	}
+	writeProfile("before")
+	scope := ckprompt.ConfigScope(func(ctx context.Context, selection ckconfig.Selection, input struct{}, state *invocationState) (*pk.Engine, error) {
+		engine, err := loadPromptEngine(ctx, selection, input, state)
+		writeProfile("after")
+		return engine, err
+	})
+	side := ckconfig.ComparisonSide[struct{}]{Selection: ckconfig.Selection{
+		Config: commandkit.Supplied[string]{Value: main, Set: true},
+	}}
+	result, err := scope.Compare(context.Background(), ckconfig.ComparisonRequest[struct{}]{Left: side, Right: side}, &invocationState{})
+	if err != nil {
+		t.Fatal(err)
+	}
+	for _, difference := range result.Value {
+		if strings.Contains(difference.Left.YAML, "before") && strings.Contains(difference.Right.YAML, "after") {
+			return
+		}
+	}
+	t.Fatal("comparison did not capture the model before and after the resource changed")
+}
+
+func TestRequestInspectionAndExplicitSmokeUseSameSources(t *testing.T) {
+	dir := t.TempDir()
+	file := filepath.Join(dir, "config.yml")
+	if err := os.WriteFile(file, []byte("version: 3\n"), 0644); err != nil {
+		t.Fatal(err)
+	}
+	resources := `backends:
+  - id: local
+    endpoint: https://example.invalid/v1
+    smoke_tests:
+      default_profile: fixture
+      authentication:
+        kind: none
+profiles:
+  - id: fixture
+    backend: local
+    model: sample
+collections:
+  audita:
+    prompts:
+      - id: modules.grammar.proposal
+        messages:
+          - role: user
+            content: 'Replacement {{.HardeningPolicy}} {{.SectionJSON}}'
+        output:
+          format: text
+          validation_mode: none
+`
+	if err := os.WriteFile(filepath.Join(dir, "prompts.yml"), []byte(resources), 0644); err != nil {
+		t.Fatal(err)
+	}
+	calls := 0
+	client := &http.Client{Transport: roundTripFunc(func(req *http.Request) (*http.Response, error) {
+		calls++
+		body := `{}`
+		if req.Method == http.MethodPost {
+			requestBody, err := io.ReadAll(req.Body)
+			if err != nil {
+				t.Fatal(err)
+			}
+			content := "PROMPTKIT_OK"
+			if strings.Contains(string(requestBody), "response_format") {
+				content = `{"status":"ok"}`
+			}
+			encoded, err := json.Marshal(content)
+			if err != nil {
+				t.Fatal(err)
+			}
+			body = `{"model":"sample","choices":[{"message":{"content":` + string(encoded) + `}}]}`
+		}
+		return &http.Response{StatusCode: 200, Header: make(http.Header), Body: io.NopCloser(strings.NewReader(body)), Request: req}, nil
+	})}
+	app, err := buildApplicationWithClient(client)
+	if err != nil {
+		t.Fatal(err)
+	}
+	execute := func(args ...string) (commandkit.Outcome, string, string) {
+		t.Helper()
+		var out, stderr bytes.Buffer
+		result := app.Execute(context.Background(), args, commandkit.Streams{Out: &out, Err: &stderr})
+		return result, out.String(), stderr.String()
+	}
+	common := []string{"--config", file, "--llm-profile", "fixture"}
+	args := append([]string{"promptkit", "show", "prepared", "audita/modules.grammar.proposal"}, common...)
+	args = append(args, "--llm-var", "SectionJSON=[]", "--llm-var", "HardeningPolicy=custom-instruction")
+	outcome, out, stderr := execute(args...)
+	if outcome.Status != 0 || !strings.Contains(out, "Replacement custom-instruction") {
+		t.Fatalf("preview status=%d out=%q err=%q", outcome.Status, out, stderr)
+	}
+	args = append([]string{"promptkit", "requirements", "validate", "audita/validators.editorial_review"}, common...)
+	args = append(args, "--llm-var", `PayloadJSON=[{"correction_index":1,"original_segment_text":"teh cat","corrected_segment_text":"the cat"}]`, "--llm-var", "TranscriptDescriptionBlock=")
+	outcome, out, stderr = execute(args...)
+	if outcome.Status != 0 {
+		t.Fatalf("validator status=%d out=%q err=%q", outcome.Status, out, stderr)
+	}
+	validatorPreview := append([]string{"promptkit", "show", "prepared", "audita/validators.editorial_review"}, common...)
+	validatorPreview = append(validatorPreview, "--llm-var", `PayloadJSON=[{"correction_index":1,"original_segment_text":"teh cat","corrected_segment_text":"the cat"}]`, "--llm-var", "TranscriptDescriptionBlock=")
+	outcome, out, stderr = execute(validatorPreview...)
+	if outcome.Status != 0 || !strings.Contains(out, "teh cat") {
+		t.Fatalf("validator preview status=%d out=%q err=%q", outcome.Status, out, stderr)
+	}
+	if calls != 0 {
+		t.Fatalf("inspection made %d provider calls", calls)
+	}
+	outcome, out, stderr = execute("promptkit", "test", "reachability", "--config", file, "--llm-backend", "local")
+	if outcome.Status != 0 || calls == 0 {
+		t.Fatalf("smoke status=%d calls=%d out=%q err=%q", outcome.Status, calls, out, stderr)
+	}
+	previous := calls
+	outcome, out, stderr = execute("promptkit", "test", "all", "--config", file, "--llm-backend", "local", "--llm-profile", "fixture", "--format=json")
+	if outcome.Status != 0 || calls <= previous || !strings.Contains(out, "structured_output") || !strings.Contains(out, "text_inference") {
+		t.Fatalf("aggregate status=%d calls=%d out=%q err=%q", outcome.Status, calls, out, stderr)
+	}
+}
+
+type roundTripFunc func(*http.Request) (*http.Response, error)
+
+func (f roundTripFunc) RoundTrip(req *http.Request) (*http.Response, error) { return f(req) }
+
+func TestRequestDefaultsRespectNamespaceAndCallerVariables(t *testing.T) {
+	request := pk.RunRequest{PromptID: "modules.grammar.proposal", Vars: map[string]string{"HardeningPolicy": "caller"}}
+	result := applicationPromptRequest(request, &pk.Namespaces{Prompt: "audita"})
+	if result.Vars["HardeningPolicy"] != "caller" || result.Vars["ProposalContract"] == "" {
+		t.Fatalf("variables=%v", result.Vars)
+	}
+	if _, changed := request.Vars["ProposalContract"]; changed {
+		t.Fatal("input variables mutated")
+	}
+	generic := pk.RunRequest{PromptID: "generic", Vars: map[string]string{"x": "y"}}
+	result = applicationPromptRequest(generic, nil)
+	if len(result.Vars) != 1 || result.Vars["x"] != "y" {
+		t.Fatalf("generic request changed: %v", result.Vars)
+	}
+}