Index the v3.1.1 release notes

.gitignore

@@ -12,7 +12,6 @@ build/
 
 # ---> Codex
 .codex
-AGENTS.md
 
 # ---> Go
 # If you prefer the allow list template instead of the deny list, see community template:

.woodpecker/release.yml

@@ -1,50 +1,50 @@
+matrix:
+  include:
+    - GO_IMAGE: golang:1.26.8-bookworm
+
 when:
   - event: tag
+    ref: refs/tags/v*
 
 steps:
-  - name: build-release-assets
-    image: golang:1.25
+  - name: deliver
+    image: ${GO_IMAGE}
+    environment:
+      RELEASEKIT_GITEA_TOKEN:
+        from_secret: GITEA_RELEASE_TOKEN
     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)"
 
-        version="$CI_COMMIT_TAG"
-        dist="dist"
-        pkg="gitea.maximumdirect.net/eric/audita/cmd/audita"
+        bootstrap_dir=$(mktemp -d "$${CI_WORKSPACE%/*}/.releasekit-bootstrap.XXXXXX")
+        trap 'rm -rf "$${bootstrap_dir}"' EXIT
+        cp go.mod "$${bootstrap_dir}/go.mod"
+        if [ -f go.sum ]; then
+          cp go.sum "$${bootstrap_dir}/go.sum"
+        else
+          : > "$${bootstrap_dir}/go.sum"
+        fi
+        cp "$${bootstrap_dir}/go.mod" "$${bootstrap_dir}/releasekit.mod"
+        cp "$${bootstrap_dir}/go.sum" "$${bootstrap_dir}/releasekit.sum"
 
-        rm -rf "$dist"
-        mkdir -p "$dist"
-
-        build_binary() {
-          goos="$1"
-          goarch="$2"
-          suffix="$3"
-          output="$dist/audita-$version-$goos-$goarch$suffix"
-
-          CGO_ENABLED=0 GOOS="$goos" GOARCH="$goarch" \
-            go build -trimpath -ldflags "-s -w -X gitea.maximumdirect.net/eric/audita/internal/buildinfo.Version=$version" \
-            -o "$output" "$pkg"
-        }
-
-        build_binary linux amd64 ""
-        build_binary linux arm64 ""
-        build_binary darwin amd64 ""
-        build_binary darwin arm64 ""
-        build_binary windows amd64 ".exe"
-        build_binary windows arm64 ".exe"
-
-  - name: publish-release
-    image: woodpeckerci/plugin-release
-    depends_on:
-      - build-release-assets
-    settings:
-      api_key:
-        from_secret: GITEA_RELEASE_TOKEN
-      files:
-        - dist/audita-*
-      checksum: sha256
-      checksum-file: SHA256SUMS
-      checksum-flatten: true
-      file-exists: skip
-      overwrite: false
-      prerelease: false
+        export GOWORK=off
+        export GOTOOLCHAIN=local
+        releasekit_module=gitea.maximumdirect.net/eric/ReleaseKit
+        go list -mod=mod -modfile="$${bootstrap_dir}/releasekit.mod" -m "$${releasekit_module}"
+        go build -mod=mod -modfile="$${bootstrap_dir}/releasekit.mod" \
+          -o "$${bootstrap_dir}/releasekit" "$${releasekit_module}/cmd/releasekit"
+        "$${bootstrap_dir}/releasekit" ci-deliver \
+          --repo "$${CI_WORKSPACE}" \
+          --prepared \
+          --commit "$${expected_commit}" \
+          "$${CI_COMMIT_TAG}"

AGENTS.md

@@ -0,0 +1,6 @@
+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.
+
+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. 
+                    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,305 +1,62 @@
 # Audita
 
-Audita is a transcript polishing CLI.
+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 process` validates transcript/glossary input, normalizes and chunks transcript segments, runs the default correction pipeline, and emits corrected transcript output plus machine-readable diagnostics and reports.
+## Quickstart
 
-## What Audita Does
-
-Default module sequence:
-- `glossary`
-- `homophones`
-- `glossary`
-- `spoken_word`
-- `grammar`
-
-Pipeline behavior includes:
-- glossary-backed domain/acoustic corrections
-- conservative homophone and mistranscription corrections
-- conservative spoken-word dysfluency cleanup with semantic guardrails
-- grammar/punctuation/capitalization/formatting cleanup
-- validator-chain enforcement before application
-- malformed module-stage LLM payloads degrade to warnings/rejections instead of failing the run
-- run reports and diagnostics artifacts with secret redaction
-
-## Build and Install
-
-Build a local binary:
+From a checkout, build with Go 1.26.0 or newer:
 
 ```sh
 go build -o ./bin/audita ./cmd/audita
 ```
 
-Install into your Go bin directory:
+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/local/) 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:
 
 ```sh
-go install ./cmd/audita
+./bin/audita config validate --config examples/minimal-config.yml
+./bin/audita config print-effective --config examples/minimal-config.yml --view profiles
 ```
 
-CLI help:
+Run the included small input with the minimal config:
 
 ```sh
-audita --help
-audita process --help
-audita config --help
-```
-
-## Test
-
-Run all tests:
-
-```sh
-go test ./...
-```
-
-## Basic Usage
-
-Required inputs:
-- transcript JSON path (positional argument)
-- `--glossary <glossary.yaml>`
-
-Recommended run:
-
-```sh
-audita process transcript.json \
-  --glossary glossary.yaml \
-  --output corrected.json \
-  --report-json report.json
-```
-
-Select an explicit output schema (default is `bare-segments`):
-
-```sh
-audita process transcript.json \
-  --glossary glossary.yaml \
-  --output-schema audita-v1 \
-  --output corrected.json \
-  --report-json report.json
-```
-
-Recommended config-based run:
-
-```sh
-audita process transcript.json \
-  --glossary glossary.yaml \
-  --config audita.yml \
-  --output corrected.json \
-  --report-json report.json
-```
-
-Explicit module override:
-
-```sh
-audita process transcript.json \
-  --glossary glossary.yaml \
-  --modules glossary,homophones,grammar \
-  --output corrected.json \
-  --report-json report.json
-```
-
-Optional transcript background context:
-
-```sh
-audita process transcript.json \
-  --glossary glossary.yaml \
-  --transcript-description "Brief context that may help resolve ambiguous terms." \
+./bin/audita process examples/tiny-transcript.json \
+  --config examples/minimal-config.yml \
+  --glossary examples/tiny-glossary.yaml \
   --output corrected.json
 ```
 
-The transcript description is background context only and does not override transcript content.
-
-Write transcript JSON to stdout (no `--output`):
-
-```sh
-audita process transcript.json --glossary glossary.yaml
-```
-
-Control diagnostics location/retention:
-
-```sh
-audita process transcript.json \
-  --glossary glossary.yaml \
-  --work-dir /tmp/audita \
-  --work-dir-retention auto \
-  --output corrected.json \
-  --report-json report.json
-```
-
-## Stdout/Stderr Contract
-
-- With `--output`, stdout is expected to be empty on success.
-- Without `--output`, stdout contains transcript JSON only on success.
-- `--report-json` writes a file and is never printed to stdout.
-- stderr is human-readable diagnostics/errors.
-- successful runs remain quiet on stderr even when module warnings are recorded in report/diagnostics artifacts.
-
-For subprocess orchestration guidance, see [`docs/subprocess-operations.md`](docs/subprocess-operations.md).
-
-## Configuration
-
-Precedence:
-1. defaults
-2. config file (`--config`, `AUDITA_CONFIG`, or default search paths when present: `/usr/local/etc/audita/config.yml`, then `/etc/audita/config.yml`)
-3. environment (`AUDITA_*`)
-4. CLI flags
-
-Config commands:
-
-```sh
-audita config validate --config audita.yml
-audita config print-effective --config audita.yml
-```
-
-For full config-file schema and examples, see [`docs/configuration.md`](docs/configuration.md).
-For output-schema details, see [`docs/architecture/output-schemas.md`](docs/architecture/output-schemas.md).
-For built-in validator keys and chain definitions, see [`docs/architecture/validators.md`](docs/architecture/validators.md).
-For embedded prompt assets and prompt metadata behavior, see [`docs/architecture/prompts.md`](docs/architecture/prompts.md).
-For CLI/process compatibility guarantees, see [`docs/architecture/public-contract.md`](docs/architecture/public-contract.md).
-
-### Modules
-
-- `AUDITA_MODULES` (CSV)
-- CLI: `--modules`
-
-### Transcript Description
-
-CLI:
-- `--transcript-description`
-
-Behavior:
-- optional background context for proposal and LLM-validator prompts;
-- trimmed and length-limited by CLI validation;
-- does not override transcript content;
-- no `AUDITA_*` environment variable is currently defined for this setting.
-
-### Primary LLM
-
-Environment:
-- `AUDITA_LLM_API_KEY` (or `OPENROUTER_API_KEY` fallback)
-- `AUDITA_MODEL`
-- `AUDITA_BASE_URL`
-- `AUDITA_LLM_TIMEOUT_SECONDS`
-- `AUDITA_MAX_RETRIES`
-
-CLI:
-- `--llm-api-key`
-- `--model`
-- `--base-url`
-- `--llm-timeout-seconds`
-- `--max-retries`
-
-### Validation LLM
-
-Environment:
-- `AUDITA_VALIDATION_LLM_API_KEY`
-- `AUDITA_VALIDATION_MODEL`
-- `AUDITA_VALIDATION_BASE_URL`
-- `AUDITA_VALIDATION_LLM_TIMEOUT_SECONDS`
-- `AUDITA_VALIDATION_MAX_RETRIES`
-- `AUDITA_VALIDATION_LLM_CONCURRENCY`
-- `AUDITA_VALIDATION_MAX_PROMPT_TOKENS`
-
-CLI:
-- `--validation-llm-api-key`
-- `--validation-model`
-- `--validation-base-url`
-- `--validation-llm-timeout-seconds`
-- `--validation-max-retries`
-- `--validation-llm-concurrency`
-- `--validation-max-prompt-tokens`
-
-### LLM Concurrency
-
-Environment:
-- `AUDITA_TOTAL_LLM_CONCURRENCY`
-- `AUDITA_PROPOSAL_LLM_CONCURRENCY`
-- `AUDITA_VALIDATION_LLM_CONCURRENCY`
-- `AUDITA_LLM_CONCURRENCY` (legacy alias for `AUDITA_TOTAL_LLM_CONCURRENCY`)
-
-CLI:
-- `--total-llm-concurrency`
-- `--proposal-llm-concurrency`
-- `--validation-llm-concurrency`
-- `--llm-concurrency` (legacy alias for `--total-llm-concurrency`)
-
-Behavior:
-- all proposal and validation LLM calls are bounded by total LLM concurrency
-- proposal LLM calls are additionally bounded by proposal LLM concurrency
-- when validation concurrency is unset, it inherits total LLM concurrency
-- when explicitly set, proposal and validation concurrency must each be `<= total-llm-concurrency`
-- canonical total settings win when both canonical and legacy alias settings are provided at the same precedence layer
-
-### Confidence Thresholds
-
-Environment:
-- `AUDITA_GLOSSARY_CONFIDENCE_THRESHOLD`
-- `AUDITA_HOMOPHONES_CONFIDENCE_THRESHOLD`
-- `AUDITA_SPOKEN_WORD_CONFIDENCE_THRESHOLD`
-- `AUDITA_GRAMMAR_CONFIDENCE_THRESHOLD`
-
-CLI:
-- `--glossary-confidence-threshold`
-- `--homophones-confidence-threshold`
-- `--spoken-word-confidence-threshold`
-- `--grammar-confidence-threshold`
-
-### Normalization and Chunking
-
-Environment:
-- `AUDITA_NORMALIZE_MAX_SEGMENT_GAP`
-- `AUDITA_NORMALIZE_ELLIPSIS_GAP`
-- `AUDITA_NORMALIZE_MAX_SEGMENT_DURATION`
-- `AUDITA_NORMALIZE_MAX_SEGMENT_TOKENS`
-- `AUDITA_MAX_SECTION_TOKENS`
-- `AUDITA_MIN_SECTION_TOKENS`
-- `AUDITA_TARGET_SECTIONS`
-
-CLI:
-- `--normalize-max-segment-gap`
-- `--normalize-ellipsis-gap`
-- `--normalize-max-segment-duration`
-- `--normalize-max-segment-tokens`
-- `--max-section-tokens`
-- `--min-section-tokens`
-- `--target-sections`
-
-### Work Directory
-
-Environment:
-- `AUDITA_WORK_DIR`
-- `AUDITA_WORK_DIR_RETENTION` (`auto`, `always`, `never`)
-
-CLI:
-- `--work-dir`
-- `--work-dir-retention`
-
-Retention behavior:
-- `always`: keep all run directories
-- `never`: keep successful run directories
-- `auto`: keep failed runs and successful runs with skipped/rejected corrections
-
-## Reports and Diagnostics
-
-Per-run diagnostics include:
-- source transcript artifacts
-- normalized transcript artifact
-- normalization summary
-- chunking summary
-- utilization diagnostics summary
-- correction ledger
-- invocation metadata
-- redacted effective config
-- module/validator prompt-response diagnostics
-- `report.json`
-- `error.log` on failure
-
-Optional external report output:
-- `--report-json <path>`
+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.
 
 ## Documentation
 
-- Architecture: [`docs/architecture.md`](docs/architecture.md)
-- Diagnostics: [`docs/diagnostics.md`](docs/diagnostics.md)
-- Structured LLM adapter: [`docs/structured-llm.md`](docs/structured-llm.md)
-- Subprocess operations: [`docs/subprocess-operations.md`](docs/subprocess-operations.md)
-- Release checklist: [`docs/release-checklist.md`](docs/release-checklist.md)
+- [CLI reference](docs/cli.md)
+- [Configuration and maintained examples](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/main.go

@@ -1,11 +1,20 @@
 package main
 
 import (
+	"context"
 	"os"
+	"os/signal"
+	"syscall"
 
-	"gitea.maximumdirect.net/eric/audita/internal/cli"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/cli"
 )
 
 func main() {
-	os.Exit(cli.Run(os.Args[1:], os.Stdout, os.Stderr))
+	os.Exit(run())
+}
+
+func run() int {
+	ctx, stop := signal.NotifyContext(context.Background(), os.Interrupt, syscall.SIGTERM)
+	defer stop()
+	return cli.Run(ctx, os.Args[1:], os.Stdout, os.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/README.md

@@ -0,0 +1,12 @@
+# Architectural Decision Records
+
+## Accepted
+
+- [ADR 0001: Adopt ReleaseKit for release management](0001-releasekit.md) —
+  accepted 2026-10-07.
+
+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
+[roadmap documents](../roadmap/).

docs/architecture.md

@@ -1,14 +0,0 @@
-# Audita Architecture Index
-
-This file is the entrypoint for architecture documentation.
-
-Core architecture overview:
-- [Architecture Overview](./architecture/architecture.md)
-
-Focused architecture contracts:
-- [Public Contract](./architecture/public-contract.md)
-- [Diagnostics](./architecture/diagnostics.md)
-- [Structured LLM](./architecture/structured-llm.md)
-- [Validators](./architecture/validators.md)
-- [Prompts](./architecture/prompts.md)
-- [Output Schemas](./architecture/output-schemas.md)

docs/architecture/architecture.md

@@ -1,153 +0,0 @@
-# Audita Architecture
-
-## Scope
-This document describes the production architecture implemented in this repository today.
-
-Audita is a single-process Go CLI that:
-- loads effective runtime configuration;
-- reads transcript and glossary inputs;
-- normalizes and sections transcripts;
-- runs a built-in module pipeline with validator chains;
-- writes transcript output and run diagnostics.
-
-## Runtime entrypoints
-Primary CLI commands:
-- `audita process <transcript.json> --glossary <glossary.yaml> [flags]`
-- `audita config validate --config <config.yml>`
-- `audita config print-effective [--config <config.yml>]`
-
-Command ownership lives in `internal/cli/run.go`.
-
-## Configuration model
-`internal/core/config` owns defaults, file parsing, environment overrides, CLI overrides, and validation.
-
-Effective-config loading for `process` and `config print-effective` is centralized in:
-- `ResolveConfigPath`
-- `LoadEffectiveConfig`
-
-Effective precedence for `audita process`:
-1. defaults
-2. config file
-3. environment overrides
-4. CLI overrides
-
-`audita config validate` is intentionally file-only validation:
-- load versioned file;
-- apply onto defaults;
-- validate;
-- do not apply environment overrides.
-
-Supported module and output-schema keys are validated through shared catalogs:
-- module keys: `internal/core/modulecatalog`
-- output schemas: `internal/core/outputschema`
-
-## Pipeline and module orchestration
-The built-in module sequence is configured in runtime config and executed by `internal/framework/runner` through resolved module specs.
-
-Current default sequence:
-- `glossary`
-- `homophones`
-- `glossary`
-- `spoken_word`
-- `grammar`
-
-Execution behavior:
-- modules execute serially over the working transcript;
-- section proposal work can run concurrently within a module;
-- validator execution happens on generated proposals before application;
-- approved proposals are applied once per module in deterministic proposal-index order.
-
-Production modules remain separate packages:
-- `internal/modules/glossary`
-- `internal/modules/homophones`
-- `internal/modules/spoken_word`
-- `internal/modules/grammar`
-
-## Proposal generation and prompt context
-Shared proposal plumbing is centralized in `internal/framework/proposal_generation`.
-
-Module packages provide:
-- module identity and replacement policy;
-- module-specific prompt message building;
-- built-in validator chain selection.
-
-Shared prompt payload helpers are in `internal/framework/promptcontext`.
-
-## Validator architecture
-Built-in validator construction and chain composition live in `internal/validators`.
-
-Shared validator runtime mechanics live in `internal/framework/validators`.
-
-Execution class metadata (deterministic vs LLM-backed) is centralized in `internal/validators/metadata` and used for ordering and reporting classification.
-
-## Structured LLM boundary
-All production LLM calls go through the internal contract:
-- `contracts.StructuredLLMClient`
-- `CompleteStructured(ctx, req, out)`
-
-The OpenAI-compatible HTTP adapter is implemented in `internal/framework/llm`.
-
-Structured response schemas are registered in `internal/framework/responseschema` and attached to requests via `response_format` metadata.
-
-Malformed structured-output detection is centralized in `internal/framework/structuredoutput` and reused by proposal generation and validator execution so downgrade behavior stays consistent.
-
-## Stage naming and diagnostics metadata
-Diagnostics stage naming is centralized in `internal/framework/stagename`:
-- module proposal stage names;
-- proposal-generation stage names;
-- validator batch stage names.
-
-Prompt metadata and response-schema metadata each expose canonical diagnostics maps via:
-- `prompts.Metadata.DiagnosticsMap()`
-- `responseschema.Schema.DiagnosticsMap()`
-
-## Diagnostics and reporting
-Run-directory artifacts are owned by `internal/core/diagnostics`.
-
-Stable artifact names are centralized constants (for example transcript artifacts, `invocation.json`, `effective-config.json`, `utilization-diagnostics.json`, `correction-ledger.json`, `report.json`, `error.log`).
-
-Report diagnostics path metadata is constructed through `BuildDiagnosticsMetadata`, which keeps run-directory artifact references consistent between success and failure reports.
-
-## Secret redaction
-Redaction responsibilities are split by concern:
-- structural config redaction: `config.Config.Redacted()`
-- byte/string payload redaction for diagnostics and surfaced errors: framework redaction utilities.
-
-Configured LLM secret extraction is centralized in `llm.ConfiguredSecrets(cfg)` and reused across proposal and validator diagnostics paths.
-
-## Output contracts
-Transcript output schema selection is owned by `internal/core/outputschema`.
-
-Supported schemas:
-- `bare-segments`
-- `audita-v1`
-
-Unknown schema keys fail validation and runtime resolution.
-
-## Key package map
-Core packages:
-- `internal/core/config`
-- `internal/core/schema`
-- `internal/core/normalization`
-- `internal/core/chunking`
-- `internal/core/diagnostics`
-- `internal/core/reporting`
-- `internal/core/modulecatalog`
-- `internal/core/outputschema`
-
-Framework packages:
-- `internal/framework/contracts`
-- `internal/framework/proposals`
-- `internal/framework/proposal_generation`
-- `internal/framework/promptcontext`
-- `internal/framework/runner`
-- `internal/framework/validators`
-- `internal/framework/llm`
-- `internal/framework/responseschema`
-- `internal/framework/stagename`
-- `internal/framework/structuredoutput`
-
-Domain packages:
-- `internal/modules/*`
-- `internal/validators/*`
-- `internal/prompts`

docs/architecture/diagnostics.md

@@ -1,104 +0,0 @@
-# Audita Diagnostics
-
-This document describes the run-directory diagnostics artifacts produced by `audita process`.
-
-## Purpose
-
-Diagnostics provide machine-readable run context and execution artifacts for:
-- failure debugging;
-- validator/correction review;
-- post-run performance analysis.
-
-Diagnostics are written under the configured work directory (`--work-dir`) when run-directory initialization succeeds.
-
-## Core artifacts
-
-Typical artifacts in each run directory:
-- `source-transcript.json`
-- `source-transcript-parsed.json`
-- `normalized-transcript.json`
-- `normalization-summary.json`
-- `chunking-summary.json`
-- `invocation.json`
-- `effective-config.json` (redacted)
-- module/validator LLM interaction artifacts
-- `report.json`
-- `error.log` on failure
-
-## Utilization diagnostics artifact
-
-Artifact:
-- `utilization-diagnostics.json`
-
-High-level fields:
-- `effective_concurrency`:
-  - total/proposal/validation LLM concurrency limits in effect.
-- `run_timing`:
-  - run wall time;
-  - scheduler queue wait time;
-  - LLM execution time;
-  - deterministic validator time;
-  - max/average in-flight LLM calls.
-- `llm_calls`:
-  - total proposal and validation LLM call counts.
-- `modules`:
-  - module-level timing summaries.
-- `validators`:
-  - per-validator timing summaries keyed by stable validator key.
-
-## Correction ledger artifact
-
-Artifact:
-- `correction-ledger.json`
-
-Ledger records are flattened review entries derived from module results and include:
-- module/proposal identity (`module_key`, `module_instance`, `proposal_index`, `segment_id`);
-- correction text fields and replacement policy when available;
-- disposition:
-  - `applied`
-  - `rejected`
-  - `skipped`
-  - `failed`
-- stable reason codes/messages;
-- deterministic and LLM validator decision snapshots using stable validator keys.
-
-Validator rejection and proposal-application skip are distinct dispositions.
-Module warnings are reported in module results and diagnostics metadata, but do not create standalone correction-ledger rows.
-
-## Report references
-
-`report.json` and optional `--report-json` output include diagnostics metadata paths for:
-- utilization diagnostics artifact;
-- correction ledger artifact;
-- existing transcript/normalization/chunking/invocation/effective-config artifacts.
-
-Module report entries also include warning records for malformed proposal-generation payloads and malformed validator batches.
-
-## Retention behavior
-
-Run-directory retention follows configured policy:
-- `always`: keep all run directories;
-- `never`: keep successful run directories;
-- `auto`: keep failed runs and successful runs with skipped/rejected corrections.
-
-## Redaction guarantees
-
-API keys and other configured secrets are redacted from:
-- `effective-config.json`;
-- LLM interaction diagnostics artifacts;
-- reports and surfaced errors.
-
-## Debugging guide
-
-When debugging:
-- slow runs:
-  - inspect `utilization-diagnostics.json` (`run_timing`, `modules`, `validators`, in-flight metrics).
-- validator rejections:
-  - inspect `correction-ledger.json` rejected entries and matching validator decisions;
-  - inspect validator response diagnostics payloads.
-- module warnings:
-  - inspect module `warnings` entries in `report.json` or `--report-json`;
-  - follow any diagnostic artifact path on the warning to the recorded error/response payload.
-- application skips:
-  - inspect `correction-ledger.json` skipped entries and skip reason codes;
-  - compare with validator decisions to distinguish validation rejection vs apply-time skip.

docs/architecture/output-schemas.md

@@ -1,88 +0,0 @@
-# Audita Output Schemas
-
-This document describes the built-in transcript output schema registry used by `audita process`.
-
-## Supported schema names
-
-### `bare-segments`
-
-Status:
-- implemented
-- default output schema
-
-Shape:
-- top-level JSON array of transcript segments
-
-Segment fields:
-- `id`
-- `speaker`
-- `start`
-- `end`
-- `text`
-- optional `categories`
-
-Compatibility:
-- this preserves the long-standing output shape used by existing consumers.
-
-### `audita-v1`
-
-Status:
-- implemented
-
-Shape:
-- top-level JSON object:
-  - `schema`: `"audita-v1"`
-  - `version`: `"v1"`
-  - `segments`: transcript segment array
-
-Segment fields inside `segments` match `bare-segments` segment fields.
-
-Compatibility:
-- this is the Audita-native object format with explicit schema/version metadata.
-
-### `seriatim-intermediate`
-
-Status:
-- deferred / not implemented
-
-Current behavior:
-- selecting `seriatim-intermediate` fails clearly as an unsupported output schema.
-
-Reason:
-- a concrete, repository-backed contract for this schema has not been finalized yet.
-
-## Selection
-
-Choose output schema with CLI:
-
-```sh
-audita process <transcript.json> --glossary <glossary.yaml> --output-schema audita-v1
-```
-
-Or in file config:
-
-```yaml
-version: 1
-output:
-  schema: audita-v1
-```
-
-Precedence remains:
-1. defaults
-2. file config
-3. environment overrides
-4. CLI overrides
-
-`--output-schema` overrides `output.schema` when both are supplied.
-
-## Output routing behavior
-
-- With `--output`, transcript JSON is written to file using the selected schema and stdout stays empty on success.
-- Without `--output`, stdout contains transcript JSON only, using the selected schema.
-- `--report-json` writes report JSON to file and does not write report payloads to stdout.
-
-## Backward-compatibility expectations
-
-- default schema stays `bare-segments` for compatibility unless explicitly changed in a future breaking release;
-- supported schema names are treated as stable public contract values;
-- unsupported schema names fail before output write.

docs/architecture/prompts.md

@@ -1,118 +0,0 @@
-# Audita Prompts
-
-This document describes Audita's built-in embedded prompt assets and prompt registry behavior.
-
-## Why embedded prompt assets
-
-Audita embeds production prompt text into the binary so runtime behavior is:
-- deterministic;
-- auditable;
-- dependency-light;
-- not dependent on external prompt files at execution time.
-
-Prompt text is authored as Markdown assets and rendered by Go code using typed template data.
-
-## Built-in prompt registry
-
-The prompt registry lives in `internal/prompts` and is responsible for:
-- loading embedded prompt assets;
-- registering stable prompt IDs and versions;
-- recording prompt source metadata;
-- computing deterministic SHA-256 source hashes;
-- rendering system/user prompts with strict missing-key failures.
-
-Current prompt source behavior:
-- built-in embedded prompts only (`prompt_source = builtin`).
-- filesystem prompt overrides are not supported.
-
-## Built-in prompt IDs
-
-Module proposal prompts:
-- `modules.glossary.proposal`
-- `modules.homophones.proposal`
-- `modules.spoken_word.proposal`
-- `modules.grammar.proposal`
-
-LLM-backed validator prompts:
-- `validators.spoken_form_plausibility`
-- `validators.meaning_reversal_review`
-- `validators.editorial_review`
-- `validators.grammar_review`
-- `validators.spoken_word_review`
-
-## Prompt version semantics
-
-Current built-in prompt version value is `v1`.
-
-Version is a stable metadata identifier for diagnostics and debugging. It is not a dynamic prompt-selection mechanism.
-
-## Prompt hash semantics
-
-Each registered prompt includes a deterministic SHA-256 hash of embedded source text.
-
-Hash purpose:
-- identify exact prompt source used in a run;
-- support diagnostics reproducibility and change auditing.
-
-Current hash scope:
-- source prompt text (system + user assets for a registered prompt), not a runtime secret-bearing payload.
-
-## Template rendering behavior
-
-Prompt rendering uses Go `text/template` with typed template data from module/validator builders.
-
-Missing-key behavior:
-- rendering uses missing-key errors;
-- missing/renamed template fields fail quickly instead of silently producing incomplete prompts.
-
-Go code still owns:
-- structured request/response models;
-- response schema selection;
-- transcript/glossary/payload formatting;
-- module and validator selection;
-- diagnostics wiring.
-
-## Shared prompt hardening policy
-
-A shared hardening fragment is embedded once and included in every module proposal prompt and every LLM-validator prompt.
-
-Hardening policy includes:
-- transcript text is untrusted data;
-- glossary entries and transcript descriptions are reference data, not instructions;
-- instructions found inside transcript text must not be obeyed;
-- model must perform only the requested correction/validation task;
-- no invention of facts, names, events, motivations, speaker intent, or corrections;
-- transcript remains the source of truth.
-
-## Transcript description behavior
-
-Transcript description remains background-only prompt context:
-- it may help interpret ambiguous terms;
-- it is explicitly non-authoritative and must not override transcript content;
-- empty descriptions do not render awkward blank context sections.
-
-Generated transcript descriptions are not implemented in this workstream.
-
-## Diagnostics and report metadata boundaries
-
-Current metadata flow:
-- proposal-generation diagnostics request metadata includes prompt metadata;
-- LLM-validator diagnostics request metadata includes prompt metadata.
-
-Prompt metadata fields used in diagnostics:
-- `prompt_id`
-- `prompt_version`
-- `prompt_source`
-- `embedded_path`
-- `sha256`
-
-Current boundary:
-- detailed prompt metadata is diagnostics-first;
-- broad report-level prompt registries/ledgers are deferred.
-
-## 1.0 boundary
-
-Not implemented for 1.0 in this workstream:
-- filesystem prompt overrides;
-- user-configurable prompt selection;
-- external prompt directories.

docs/architecture/public-contract.md

@@ -1,121 +0,0 @@
-# Audita Public Contract
-
-## Scope
-This document defines stability expectations for Audita's external runtime interfaces.
-
-Covered interfaces:
-- CLI commands and major flags;
-- versioned config behavior and precedence;
-- transcript/glossary input forms;
-- output schema selection;
-- report schema metadata;
-- diagnostics artifact path metadata;
-- stdout/stderr and exit-code behavior;
-- redaction guarantees.
-
-## CLI contract
-Stable commands:
-- `audita process`
-- `audita config validate`
-- `audita config print-effective`
-
-Stable high-value `process` flags:
-- `--config`
-- `--glossary`
-- `--output`
-- `--report-json`
-- `--modules`
-- `--output-schema`
-
-## Config contract
-Supported config format:
-- YAML;
-- `version: 1`;
-- strict unknown-field rejection.
-
-Path resolution for `process` and `config print-effective`:
-1. `--config`
-2. `AUDITA_CONFIG`
-3. `/usr/local/etc/audita/config.yml`
-4. `/etc/audita/config.yml`
-
-Missing explicit path is an error. Missing default paths is non-fatal.
-
-Precedence for `process`:
-1. defaults
-2. file config
-3. environment overrides
-4. CLI overrides
-
-`config validate` remains file-only validation (defaults + file config; no env overrides).
-
-Module and output-schema keys are validated against built-in catalogs. Unknown keys fail validation.
-
-## Input contract
-Supported transcript JSON top-level forms:
-- array of segments
-- object with `segments` array
-
-Supported glossary YAML form:
-- top-level `glossary` list with required entry fields validated by schema parsing.
-
-## Output schema contract
-Supported transcript output schemas:
-- `bare-segments` (default)
-- `audita-v1`
-
-Unknown schema keys fail before output write.
-
-## Report metadata contract
-Process reports include stable report metadata fields:
-- `report_schema_name`
-- `report_schema_version`
-- `output_schema`
-- `config_version` (when file config is loaded)
-
-Current values:
-- `report_schema_name = audita-process-report`
-- `report_schema_version = v1`
-
-`--report-json` output and run-directory `report.json` use the same report schema metadata.
-
-Validator decision/rejection records use stable validator keys via `validator_name`.
-
-## Diagnostics metadata contract
-When run-directory initialization succeeds, diagnostics metadata paths reference stable artifacts, including:
-- transcript and normalization artifacts;
-- chunking summary;
-- invocation metadata;
-- redacted effective config;
-- utilization diagnostics;
-- correction ledger;
-- `error.log` on failures.
-
-LLM interaction diagnostics include stable prompt and structured-schema identifiers where applicable.
-
-## Stdout/stderr and exit codes
-Success:
-- with `--output`, stdout is empty;
-- without `--output`, stdout contains transcript JSON only;
-- report JSON is not written to stdout.
-
-Failures:
-- nonzero exit;
-- human-readable stderr summary;
-- diagnostics directory path on stderr when available.
-
-Exit codes:
-- `0` success
-- nonzero failure
-
-## Redaction contract
-Configured secrets are redacted from:
-- effective config outputs;
-- diagnostics artifacts;
-- report artifacts;
-- surfaced adapter/runtime errors.
-
-## Compatibility policy
-Stable command behavior, schema names, report metadata keys, diagnostics-path field semantics, and validator key identities are treated as public contract.
-
-Additive fields are acceptable when existing fields and behavior remain compatible.

docs/architecture/structured-llm.md

@@ -1,72 +0,0 @@
-# Structured LLM Architecture
-
-## Scope
-This document describes Audita's structured LLM runtime boundary and adapter behavior.
-
-## Runtime boundary
-Production LLM integration depends on the internal contract only:
-- `contracts.StructuredLLMClient`
-- `CompleteStructured(ctx, req, out)`
-
-Provider SDK types do not leak past this boundary.
-
-## Adapter ownership
-`internal/framework/llm` owns the OpenAI-compatible HTTP adapter and shared LLM runtime utilities.
-
-Key responsibilities:
-- request assembly;
-- timeout/cancellation propagation;
-- bounded retry behavior;
-- scheduler integration;
-- provider response decoding;
-- error redaction.
-
-## Structured schema registry
-Structured response schemas are registered in `internal/framework/responseschema` and include stable metadata:
-- `id`
-- `version`
-- `name`
-- `json_schema`
-- `sha256`
-
-Current schema keys:
-- `correction_set`
-- `validator_decision_set`
-
-Schema metadata is attached to diagnostics through `Schema.DiagnosticsMap()`.
-
-## Request shape assumptions
-Audita targets OpenAI-compatible chat-completions endpoints and sends structured requests with:
-- model;
-- chat messages;
-- `response_format.type = json_schema`;
-- schema name and JSON schema payload.
-
-## Local validation remains mandatory
-Provider schema enforcement is treated as transport-level guardrails.
-
-Audita still validates output locally before applying behavior changes:
-- proposal decoding and proposal invariants;
-- validator decision decoding and cardinality checks;
-- deterministic validation and apply-time rules.
-
-## Shared malformed-output policy
-Malformed structured-output classification is centralized in `internal/framework/structuredoutput`.
-
-Proposal generation and validator execution both use this shared classifier so downgrade behavior cannot drift between the two paths.
-
-## Secrets and redaction
-Secret extraction for LLM redaction is centralized in `llm.ConfiguredSecrets(cfg)` and reused by proposal and validator diagnostics writers.
-
-Secrets are redacted from:
-- diagnostics artifacts;
-- report artifacts;
-- surfaced adapter/runtime errors.
-
-## Concurrency and scheduling
-LLM execution is constrained by composed scheduler limits:
-- total LLM concurrency;
-- proposal LLM concurrency;
-- validation LLM concurrency.
-
-The scheduler is FIFO and context-aware so permits are released on success, failure, and cancellation.

docs/architecture/validators.md

@@ -1,96 +0,0 @@
-# Audita Validators
-
-## Scope
-This document defines the built-in validator system used by production module runs.
-
-## Ownership boundaries
-Built-in validator keys, constructors, and module chains are owned by `internal/validators`.
-
-Shared runtime execution mechanics are owned by `internal/framework/validators`, including:
-- validator request/result models;
-- deterministic proposal checks;
-- LLM validator batching and execution;
-- decision-cardinality enforcement;
-- diagnostics integration.
-
-Execution class metadata is owned by `internal/validators/metadata`.
-
-## Stable validator keys
-Deterministic:
-- `proposal_shape`
-- `confidence_threshold`
-- `original_text_presence`
-- `non_empty_corrected_text`
-- `no_effect`
-- `protected_terms`
-
-LLM-backed:
-- `spoken_form_plausibility`
-- `meaning_reversal_review`
-- `editorial_review`
-
-## Built-in module chains
-`glossary`:
-- `proposal_shape`
-- `no_effect`
-- `original_text_presence`
-- `confidence_threshold`
-- `protected_terms`
-- `non_empty_corrected_text`
-- `spoken_form_plausibility`
-- `meaning_reversal_review`
-
-`homophones`:
-- `proposal_shape`
-- `no_effect`
-- `original_text_presence`
-- `confidence_threshold`
-- `protected_terms`
-- `non_empty_corrected_text`
-- `spoken_form_plausibility`
-- `meaning_reversal_review`
-
-`spoken_word`:
-- `proposal_shape`
-- `no_effect`
-- `original_text_presence`
-- `confidence_threshold`
-- `protected_terms`
-- `non_empty_corrected_text`
-- `editorial_review`
-- `meaning_reversal_review`
-
-`grammar`:
-- `proposal_shape`
-- `no_effect`
-- `original_text_presence`
-- `confidence_threshold`
-- `protected_terms`
-- `non_empty_corrected_text`
-- `editorial_review`
-- `meaning_reversal_review`
-
-## Ordering and execution semantics
-Validator ordering is based on canonical metadata:
-- deterministic validators run before LLM-backed validators.
-
-Within each module stage:
-- proposals are generated per section;
-- validator chains execute on those proposals;
-- approved proposals are applied once after section work settles.
-
-## Malformed payload behavior
-Malformed structured-output from proposal generation and LLM validator calls is downgraded, not treated as a process-fatal transport error.
-
-Current outcomes:
-- malformed proposal-generation payloads produce section/module warnings and zero proposals for the affected section;
-- malformed validator decision payloads reject the affected validator batch with warnings;
-- deterministic validator behavior and runner order remain unchanged.
-
-## Reporting identity
-Reports and diagnostics use stable validator keys as identifiers.
-
-Correction-ledger deterministic-vs-LLM classification is derived from canonical validator metadata, not package-local hardcoded maps.
-
-## Prompt assets
-LLM validator prompt assets and prompt metadata are documented in [Prompts](./prompts.md).

docs/cli.md

@@ -0,0 +1,116 @@
+# 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.
+
+## Commands and help
+
+```sh
+audita process <transcript.json> --glossary <glossary.yml> [flags]
+audita config validate --config <config.yml> [flags]
+audita config print-effective [flags]
+audita version
+```
+
+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.
+
+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.
+
+`audita version` prints `audita <version>` and a newline to stdout, with no
+application configuration or provider setup. It returns `0` on success with
+empty stderr. `help version`, `version -h`, and `version --help` print command
+usage to stdout and return `0`. Help follows standard flag parsing and can
+short-circuit trailing arguments. Other invalid invocations return `2` with a
+usage error on stderr. The command uses ReleaseKit's public
+`buildinfo.Version()` accessor. It reports an injected release identifier when
+present, otherwise the executable's main-module version when available and not
+`(devel)`, and `dev` when neither source provides a release identifier.
+
+## Setting overrides
+
+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:
+
+| 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. For stdout
+output, reports use the effective `reporting.stdout_dir`, which defaults to the
+invocation working directory. For file output, they go beside the transcript
+unless `--report-dir` is explicitly supplied. The flag selects the report
+directory for either transcript destination; a config-file or overlay value for
+`reporting.stdout_dir` alone affects stdout output only. A selected report
+directory must be nonblank when reporting is enabled. With reporting disabled,
+the report destination is inactive and is not probed. `--debug` separately
+enables retained detailed artifacts under `--work-dir`; selecting `--work-dir`
+alone does not enable capture. 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. An inherited field may also include an `inheritance`
+sequence; each step identifies `from`, `to`, and `reference` paths as JSON
+pointers. These fields describe the effective inheritance chain without
+including configuration values. A direct child override reports its own source
+instead. Debug configuration origins use the same explanation shape. 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.

docs/config.md

@@ -0,0 +1,192 @@
+# 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 separately
+selected [local profiles](../examples/profiles/local/) and
+[service profiles](../examples/profiles/service/), plus the optional
+[testing overlay](../examples/overlays/testing.yml).
+The [ConfigKit inheritance example](../examples/configkit-inheritance.yml)
+shows a local child backend reusing and overriding sibling settings.
+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.
+
+## Loading and precedence
+
+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.
+
+After overlay and explicit CLI override precedence is applied, ConfigKit resolves
+native sibling inheritance before typed decoding. Any input mapping may use
+`extends: <sibling-name>`; the child keeps its key, inherits parent settings, and
+overrides them with its own settings. Selected overlay and CLI values therefore
+participate in inheritance at their normal precedence. The generic syntax and
+resolution rules are defined by ConfigKit v0.7.1's
+[sibling inheritance contract](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.7.1/docs/config.md#sibling-inheritance).
+
+`extends` is reserved structural input in base files, imports, overlays, and
+other application input mappings, including mapping values supplied by explicit
+CLI setting overrides. ConfigKit consumes it before typed decoding. A previously
+valid backend whose ID is literally `extends` cannot be represented under this
+rule. Rename that backend to a non-conflicting ID and update every PromptKit
+profile that selects it. This compatibility impact means the upgrade does not
+promise that every previously valid configuration remains valid.
+
+Inherited values count as explicit input, including zero, false, empty, and
+null. Existing field rules still apply: for example, inherited backend
+concurrency must be positive, while an inherited queue capacity of zero is
+valid. Parent backends undergo the same decoding and application validation as
+other backends, whether or not a selected profile uses them. A child
+`credential: null` removes the child's inherited credential; it does not remove
+the parent's credential reference, which remains subject to ordinary secret
+resolution.
+
+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.
+
+### PromptKit profiles and operator prompts
+
+`profiles_dir` selects a PromptKit configuration root, resolved against the
+selected main file's directory unless it is absolute. The root may contain
+keyed `profiles`, `backends`, and `prompts` definitions; it is not limited to
+profile-only files. IDs come from literal YAML mapping keys, never filenames.
+Multiple definitions may share a document, and a document may contribute to any
+of the supported mappings. Directory discovery is recursive, but discovery
+order does not establish field precedence. Contributions within each source
+group must compose without conflicting values.
+
+PromptKit assembles sources in this order: its selected catalogs and owned
+defaults, Audita's embedded prompt/schema inputs, operator documents under
+`profiles_dir`, then the application backend mapping. The application mapping
+owns each configured endpoint, concurrency limit, queue capacity, and credential
+environment lookup. Other supported provider fields can be contributed by the
+operator documents. Imports remain disabled. The current maintained examples
+select separate roots: [local](../examples/profiles/local/) and
+[service](../examples/profiles/service/), so definitions for one backend do not
+enter the other example's final configuration.
+
+Both selected roles must resolve to an existing profile, registered backend,
+nonblank effective model, and nonblank endpoint. The normalized effective
+endpoint must match the application backend endpoint. A selected profile cannot
+introduce a competing `api_key_env` lookup; the application backend credential
+supplies the runtime key when required. Other unselected profiles may be
+partial, but every final backend, profile, and prompt definition is validated
+when the engine is constructed. A malformed or conflicting unused definition
+can therefore make the selected root invalid. A missing selected root is an
+operator configuration error; an empty root may contribute no definitions.
+
+Profile IDs and parent IDs are exact, literal keys. PromptKit profiles can use
+native `extends` inheritance; child fields override inherited fields, while
+unmentioned controls survive changes to model or backend. For example:
+
+```yaml
+profiles:
+  "shared~base":
+    backend: service
+    model: example-model
+    temperature: 0.4
+    top_p: 0.8
+  "proposal fast":
+    extends: "shared~base"
+    model: faster-model
+    temperature: 0
+```
+
+Presence matters. Explicit `temperature: 0` is sent as zero; omission leaves it
+unspecified; null suppresses an inherited temperature. Other fields have their
+own native null and omission rules. Provider `extra_params` maps merge
+recursively, and a null provider value is sent as JSON null. See the pinned
+[PromptKit format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.14.0/docs/formats.md)
+for the complete field semantics.
+
+Operator documents can also override an embedded prompt/version, including its
+messages and definition-level output settings. Shared variables supplied by the
+adapter are rendered only when an effective message references them; Audita does
+not append omitted shared text. Audita's per-call schemas, structural repair
+budget, and downstream domain validators remain in force. The engine captures
+effective definitions and message-file contents when constructed, so edits are
+observed only by a newly constructed runtime.
+
+### Migrating PromptKit profile documents
+
+For the PromptKit v0.11 format, wrap each profile's fields under
+`profiles: {<literal-id>: ...}`, remove inner `id`, and replace
+`base_profile` with `extends`. Profile and prompt IDs are mapping keys, so they
+need not match source filenames. Review zeros, omitted values, and nulls against
+the native presence rules before deploying. Select a root whose final
+definitions have valid backend references; eager validation applies even to
+unselected definitions. See the complete maintained [local](../examples/minimal-config.yml)
+and [service](../examples/production-config.yml) examples and the pinned
+[consumer migration guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.14.0/docs/consumers/pkg-promptkit.md#migrate-from-the-previous-configuration-api).
+This incompatible profile-format migration is intended for an Audita major
+release; no automatic file conversion is provided.
+
+The [CLI inspection views](cli.md#streams-and-exit-status) show selected
+controls and field provenance separately from ConfigKit's redacted settings
+YAML. Inspection resolves both roles without provider calls.
+
+## Settings
+
+| Field | Default | Rule |
+| --- | --- | --- |
+| `profiles_dir` | `profiles` | Nonempty PromptKit document root; resolved relative to the selected main file, or absolute. |
+| `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). |
+| `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; a `--report-dir` flag can select reports for either transcript destination. |
+| `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. |
+
+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 when it supplies the active report
+destination: for stdout output, or for file output when `--report-dir` is
+explicitly supplied. File output without that flag uses the transcript's parent,
+so the configured value is inactive. Reporting-disabled runs do not select a
+report directory. `diagnostics.work_dir` must be nonblank only with debug
+enabled. These path requirements are checked when choosing process destinations,
+not during configuration inspection.
+
+## Credentials
+
+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).

docs/configuration.md

@@ -1,149 +0,0 @@
-# Audita Configuration
-
-## Scope
-This document defines the supported versioned YAML configuration model and runtime precedence behavior.
-
-## Supported file version
-Current supported config file version:
-- `version: 1`
-
-Validation rules:
-- missing `version` fails;
-- unsupported version fails;
-- unknown YAML fields fail (strict decoding).
-
-## Config path resolution
-For `audita process` and `audita config print-effective`, path resolution order is:
-1. `--config <path>`
-2. `AUDITA_CONFIG`
-3. `/usr/local/etc/audita/config.yml` (if present)
-4. `/etc/audita/config.yml` (if present)
-
-Missing-path behavior:
-- missing `--config` path is an error;
-- missing `AUDITA_CONFIG` path is an error;
-- missing both default paths is non-fatal.
-
-## Effective precedence
-`audita process` effective precedence:
-1. defaults
-2. file config
-3. environment overrides
-4. CLI overrides
-
-`audita config print-effective` uses:
-1. defaults
-2. file config
-3. environment overrides
-
-`audita config validate` intentionally uses file-only validation:
-1. defaults
-2. file config
-
-Environment overrides are not applied in `config validate`.
-
-## Supported top-level YAML fields
-```yaml
-version: 1
-
-pipeline:
-  modules: [glossary, homophones, glossary, spoken_word, grammar]
-
-output:
-  schema: bare-segments
-
-llm:
-  proposal:
-    base_url: https://openrouter.ai/api/v1
-    model: openrouter/google/gemma-4-31b-it
-    api_key_env: AUDITA_LLM_API_KEY
-    timeout: 120s
-    max_retries: 3
-  validation:
-    base_url: https://openrouter.ai/api/v1
-    model: openrouter/google/gemma-4-31b-it
-    api_key_env: AUDITA_VALIDATION_LLM_API_KEY
-    timeout: 120s
-    max_retries: 3
-
-concurrency:
-  total_llm: 2
-  proposal_llm: 2
-  validation_llm: 1
-
-chunking:
-  target_sections: 8
-  max_section_tokens: 8192
-  min_section_tokens: 2048
-
-normalization:
-  max_segment_gap: 4s
-  ellipsis_gap: 3.5s
-  max_segment_duration: 60s
-  max_segment_tokens: 2048
-
-thresholds:
-  glossary: 0.8
-  homophones: 0.8
-  spoken_word: 0.8
-  grammar: 0.8
-
-context:
-  description: "optional transcript background context"
-
-diagnostics:
-  work_dir: /tmp/audita
-  retention: auto
-```
-
-## Module and output-schema validation
-`pipeline.modules` keys are validated against the built-in supported module catalog.
-
-Supported module keys:
-- `glossary`
-- `homophones`
-- `spoken_word`
-- `grammar`
-
-Repeated supported module keys are allowed.
-
-`output.schema` is validated against the built-in output schema catalog.
-
-Supported output schema keys:
-- `bare-segments`
-- `audita-v1`
-
-Unknown module keys and unknown output schema keys fail validation.
-
-## Duration field parsing
-Duration-like fields support:
-- numeric seconds (for example `120`, `3.5`)
-- duration strings (for example `120s`, `2m`)
-
-LLM timeout duration strings must resolve to whole seconds.
-
-## Secret handling
-Use `api_key_env` fields for secrets:
-- `llm.proposal.api_key_env`
-- `llm.validation.api_key_env`
-
-These fields store environment variable names, not secret values.
-
-Resolved secret values are redacted from:
-- `audita config print-effective` output;
-- diagnostics `effective-config.json`;
-- report and diagnostics payloads.
-
-## Commands
-Validate a file config:
-```sh
-audita config validate --config ./audita.yml
-```
-
-Print redacted effective config:
-```sh
-audita config print-effective --config ./audita.yml
-```
-
-## Compatibility notes
-Legacy compatibility flags and environment aliases remain available where implemented, but the stable configuration surface is the versioned YAML model described above.

docs/development.md

@@ -1,33 +1,72 @@
-# Audita Development Workflow
+# Developing Audita
 
-## Scope
-This document defines the canonical contributor workflow and engineering conventions for this repository.
+Audita is a Go CLI for transcript polishing. Start with the
+[README](../README.md) for product orientation and the
+[internal overview](internal/overview.md) for the implemented component map.
 
-## Workflow
-1. Start from a clean understanding of scope and constraints.
-2. Make focused changes that preserve existing public behavior unless behavior change is explicitly intended.
-3. Run targeted tests for touched packages.
-4. Run `go test ./...` before finalizing substantial changes.
-5. Update affected documentation so it describes current behavior only.
+## Before Changing the Repository
 
-## Engineering conventions
-- Keep module packages separate: `glossary`, `homophones`, `spoken_word`, `grammar`.
-- Prefer narrow shared helpers and catalogs over broad abstractions.
-- Preserve diagnostics artifact naming and report field contracts unless intentionally changed.
-- Preserve CLI/config precedence semantics unless intentionally changed.
-- Treat stable validator keys, prompt identifiers, and output-schema keys as contract surfaces.
+Coding agents must read and follow the [agent policy](policy/agents.md) before
+recommending, planning, or implementing changes. Use the policy reading guide
+below to select the policies applicable to the task.
 
-## Configuration and runtime expectations
-- `audita process` precedence is defaults -> file -> env -> CLI.
-- `audita config validate` validates file config merged onto defaults only.
-- `audita config print-effective` includes environment overrides and prints redacted JSON.
+Confirm the requested scope and behavior contract, make focused changes in the
+owning component, and update the relevant tests and canonical documentation
+when behavior changes. The [testing policy](policy/testing.md) governs test
+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).
 
-## Testing expectations
-- Add tests for new behavior and for bug fixes.
-- Keep deterministic fixtures stable.
-- Do not reduce existing parity, release-fixture, subprocess, or module-specific coverage without equivalent replacement.
+## Policy Reading Guide
 
-## Commit discipline
-- Keep commits scoped and reviewable.
-- Avoid mixing unrelated refactors with behavior changes.
-- Use clear plain-English commit messages.
+| 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.26.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
+go test ./...
+```
+
+Run targeted package tests for touched behavior and the complete suite for
+substantial changes. Documentation-only work normally needs affected-link,
+example, and whitespace checks; use `git diff --check`. Detailed component
+validation belongs with the change recipes below.
+
+## Task-Specific Reading Guide
+
+| Task | Read |
+| --- | --- |
+| Locate components or change orchestration | [Internal overview](internal/overview.md), then [pipeline](internal/pipeline.md) |
+| Change configuration or CLI behavior | [Configuration contract](config.md), [CLI contract](cli.md), and [configuration/CLI change recipes](internal/cli-config.md) |
+| Change modules or validators | [Modules](internal/modules.md) or [validators](internal/validators.md); follow their prompt, registry, and test references |
+| Change LLM transport or concurrency | [LLM integration contract](integrations/openai-compatible-llm.md), [LLM runtime](internal/llm-runtime.md), and [pipeline](internal/pipeline.md) |
+| Change prompts | [Prompt registry](internal/prompts.md) and the consuming [module](internal/modules.md) or [validator](internal/validators.md) |
+| Change input/output formats | [Input file contracts](integrations/transcript-glossary-files.md), [output-file contract](integrations/output-files.md), [encoder internals](internal/output-schemas.md), and [configuration](config.md) |
+| Change reports or diagnostics | [Operations](operations.md), [output-file contract](integrations/output-files.md), [subprocess integration](integrations/subprocess.md), and [diagnostics/reporting internals](internal/diagnostics-reporting.md) |
+| Change tests | [Testing policy](policy/testing.md) and the affected component's internal documentation |
+| Change docs or examples | [Documentation policy](policy/documentation.md), the canonical topic owner, and [example validation](internal/cli-config.md#validating-examples) |
+| Prepare a release | [Release policy](policy/release.md) and [release procedure](release.md) |
+| Record a significant architectural decision | [ADR lifecycle](policy/documentation.md#architecture-decision-records) and [ADR index](adr/README.md) |

docs/documentation/policy.md

@@ -1,27 +0,0 @@
-# Documentation Policy
-
-## Scope
-This policy defines how project documentation should be authored and maintained.
-
-## Core rules
-- Document the current behavior of the codebase.
-- Remove stale behavior descriptions promptly when code changes.
-- Do not describe development history in architecture or behavior docs unless a document is explicitly historical.
-- Do not use architecture or behavior docs as changelogs.
-- Prefer rewriting stale sections from scratch when substantial behavior or ownership changes occur.
-
-## Consistency requirements
-- Keep command examples aligned with current CLI surfaces.
-- Keep configuration examples aligned with supported fields and precedence.
-- Keep architecture package ownership descriptions aligned with current code layout.
-- Keep stable contract identifiers accurate (module keys, validator keys, output-schema keys, report metadata fields).
-
-## Cross-document expectations
-- `docs/architecture/*` documents runtime behavior and package ownership.
-- `docs/configuration.md` documents config schema and precedence.
-- `docs/development.md` documents contributor workflow and engineering conventions.
-
-## Review expectations for documentation changes
-- Verify referenced files and links exist.
-- Verify examples match current behavior.
-- Prefer concise, direct language and avoid speculative future claims.

docs/integration/subprocess-operations.md

@@ -1,96 +0,0 @@
-# Audita Subprocess Operations
-
-This document describes how parent processes should invoke `audita process` safely in production orchestration.
-
-## Recommended command form
-
-Use explicit file outputs for orchestrated runs:
-
-```sh
-audita process <transcript.json> \
-  --transcript-description "Brief context that may help resolve ambiguous terms." \
-  --glossary <glossary.yaml> \
-  --output <output-transcript.json> \
-  --report-json <report.json>
-```
-
-Additional flags that may be situationally appropriate:
-- `--config <path>` to select an explicit versioned config file.
-- `--output-schema <bare-segments|audita-v1>` to select transcript output shape.
-- `--work-dir <dir>` to control diagnostics location.
-- `--work-dir-retention <always|auto|never>` to control retained run directories.
-- `--total-llm-concurrency`, `--proposal-llm-concurrency`, and `--validation-llm-concurrency` when orchestration needs to set explicit LLM throughput controls.
-- `--modules ...` only when intentionally overriding the default sequence.
-
-For config-driven orchestration, validate config files in CI/preflight:
-
-```sh
-audita config validate --config <path>
-```
-
-## Stdout behavior
-
-- With `--output`: stdout is expected to be empty on success.
-- Without `--output`: stdout contains transcript JSON only on success.
-- Report JSON is never written to stdout.
-
-## Stderr behavior
-
-- Success path should be quiet or minimal human-readable logs.
-- Failure path writes concise human-readable errors.
-- When a diagnostics run directory exists, failure stderr includes its path.
-- Prompt/response diagnostic payloads are not streamed to stderr.
-
-## Output file behavior
-
-- `--output` writes transcript JSON in the selected output schema to the provided path.
-- Output write failures return nonzero and surface actionable errors.
-- The command does not silently ignore output write errors.
-
-## Report JSON behavior
-
-- `--report-json` writes a machine-readable process report to the requested path.
-- Run-directory `report.json` is written independently under diagnostics.
-- Best-effort failure reports are emitted when possible without masking the primary failure.
-- Report write failures return nonzero with clear stderr messaging.
-- Report diagnostics metadata references run-directory artifacts including utilization diagnostics and correction ledger paths when available.
-
-## Diagnostics directory behavior
-
-- Each run creates (when possible) a per-run diagnostics directory.
-- Typical artifacts include transcript, normalization, chunking, invocation, effective config, LLM diagnostics, `utilization-diagnostics.json`, `correction-ledger.json`, `report.json`, and `error.log` on failure.
-- Failed runs retain diagnostics.
-- Under `auto` retention, successful runs with skipped/rejected corrections are retained; clean successful runs may be removed.
-
-## Exit codes
-
-- `0`: success.
-- Nonzero: failure (input/schema/config/module/LLM/runtime/output/report/diagnostics errors).
-
-Treat any nonzero as a failed subprocess invocation.
-
-## Timeout and cancellation
-
-- Runtime operations propagate context cancellation and request timeouts through LLM/scheduler paths.
-- On cancellation or timeout, the process exits nonzero and should not hang.
-- If diagnostics were initialized before failure, failure artifacts remain available for debugging.
-
-## Secret redaction expectations
-
-API keys and configured secret values are redacted from:
-- reports (`--report-json` and run-dir `report.json`);
-- diagnostics artifacts (including effective config and LLM interaction artifacts);
-- surfaced adapter/runtime errors;
-- test fixtures and regression outputs.
-
-Parent-process logs should still avoid printing raw environment variables.
-
-## Parent-process pipe guidance
-
-To avoid deadlocks in orchestrators:
-- always read both stdout and stderr concurrently when invoking as a subprocess;
-- prefer file outputs (`--output`, `--report-json`) for machine workflows;
-- treat stderr as human-readable diagnostics, not structured data;
-- parse structured results from output/report files.
-
-For Go callers, prefer `exec.CommandContext` with explicit timeout/cancellation and buffered/streamed readers for both pipes.

docs/integrations/openai-compatible-llm.md

@@ -0,0 +1,34 @@
+# OpenAI-Compatible LLM Integration
+
+Audita uses the pinned [PromptKit](https://gitea.maximumdirect.net/eric/promptkit)
+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.
+
+`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 v0.14.0's consumer contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.14.0/docs/consumers/pkg-promptkit.md)
+for the pinned protocol and retry details.
+
+A model operation that exhausts structural repair, a live-parent local operation
+timeout, capacity rejection, transport failure, malformed provider response,
+or provider HTTP failure is recoverable for that operation. Proposal generation
+then contributes no candidates from that response; a failed validation batch
+marks its candidates unavailable while other batches and later modules can
+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).

docs/integrations/output-files.md

@@ -0,0 +1,112 @@
+# Output Files and Reports
+
+## Corrected Transcript
+
+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.
+
+With reporting enabled, Audita produces three ordinary files:
+
+- `errors.yml`: affected work units and run-level failures;
+- `recoveries.yml`: successful logical model operations with repair, service
+  retry, or response filtering;
+- `report.md`: a concise overview and complete per-chunk matrices.
+
+The YAML documents have Audita-owned schemas `audita-errors` and
+`audita-recoveries`, each with integer `version: 1`. Both contain, in order,
+`schema`, `version`, `run_id`, `status`, `started_at`, `completed_at`, `summary`,
+and an always-present `errors` or `recoveries` sequence. Status is
+`in_progress`, `completed`, or `failed`. Times are UTC RFC3339 strings;
+`completed_at` is null until finalization. A recoverable model error can appear
+with `status: completed`.
+
+## Summary Counts
+
+Both documents carry the same summary, in this order:
+
+| Count | Meaning |
+| --- | --- |
+| `work_units_total` | Configured module instances × initial chunks. |
+| `work_units_started`, `work_units_completed`, `work_units_interrupted`, `work_units_not_started` | Explicit processing states. |
+| `work_units_with_errors` | Distinct units with recoverable operation failures. |
+| `run_errors` | Fatal processing or output failures outside that unit count. |
+| `corrections_applied` | Approved proposals applied, not replacement occurrences. |
+| `llm_operations` | Structured-client invocations, including pre-dispatch failures. |
+| `proposal_responses` | Structurally usable proposal responses. |
+| `recoveries` | Successful operations with one or more recovery reasons. |
+| `proposal_responses_with_filtering` | Proposal responses that filtered at least one defective proposal. |
+
+Unknown counts before processing are `null`; completed empty counts are `0`.
+Retries and repair generations are details of one operation, not additional
+operations. Provider token usage, execution timing, and attempt-level evidence
+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
+count, and a `failures` sequence. Each failure identifies the operation
+(`proposal`, `validation`, or `validation_input`), 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
+and message, optional origin, and output path where relevant. It can describe
+a fatal error or secondary output-write failure without inventing a failed
+model work unit. Raw provider errors and transcript text are absent.
+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
+`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,
+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
+modules change its text.
+`validation_decisions_filtered` records unexpected validator decision indices
+ignored from a successful validation batch. It may accompany repair or service
+recovery reasons, but it does not add `filtered_proposals` or increment
+`proposal_responses_with_filtering`. A batch with unavailable requested decisions
+is an error even when unexpected indices were also ignored.
+
+## Markdown Overview
+
+`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
+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.
+
+## 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.
+These files are diagnostic evidence, not an alternate ordinary report schema.
+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.
+Rejected, unavailable, skipped, and interrupted entries omit the applied field; a module
+failure without a candidate omits both. These fields are replacement spans,
+not full resulting-segment text. Deterministic decision records now identify
+the blank-result guard as `non_empty_resulting_segment` (formerly
+`non_empty_corrected_text`); its `empty_resulting_segment` reason is unchanged.
+Validator decision records carry `disposition`: `approved`, `rejected`, or
+`unavailable`. A missing or duplicate required decision is `unavailable`, not
+an editorial rejection. The candidate ledger uses the same distinction in its
+top-level disposition. Interaction response artifacts retain supplied model
+decisions and the reconciliation result, including unavailable and ignored
+indices; unexpected indices never create candidate ledger entries.

docs/integrations/subprocess.md

@@ -0,0 +1,52 @@
+# Subprocess Integration
+
+This guide explains how a parent process can invoke Audita and consume its results.
+The [CLI reference](../cli.md) owns command syntax, streams, and exit semantics;
+[configuration](../config.md) owns discovery and precedence.
+
+## 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,
+select an explicit transcript file destination and a configuration path. Reports
+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
+configuration or `--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.
+Read stdout and stderr concurrently to avoid pipe blocking, and impose timeout
+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).
+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 and use the same selected 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).
+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
+termination can leave `in_progress` reports. Neither the existence of an output
+file nor a debug directory alone establishes successful completion.
+
+## Related Contracts
+
+- [Transcript and glossary inputs](transcript-glossary-files.md)
+- [LLM endpoint compatibility](openai-compatible-llm.md)
+- [Configuration inspection commands](../cli.md#commands-and-help)

docs/integrations/transcript-glossary-files.md

@@ -0,0 +1,50 @@
+# Transcript and Glossary Input Files
+
+This document owns accepted input formats. Use the [CLI reference](../cli.md) for
+invocation and error exit semantics, [operations](../operations.md) for artifact
+handling, and [output files](output-files.md) for corrected-transcript serialization.
+
+## Transcript JSON Contract
+
+Accepted top-level shapes are an array of segments or an object containing a
+`segments` array. The array must contain at least one segment. Unknown object
+fields are ignored by the current parser; an input envelope does not require a
+schema/version marker.
+
+| Segment field | Type and validation |
+| --- | --- |
+| `id` | Optional integer (or null). Supplied IDs must be unique; missing IDs are accepted. |
+| `speaker` | Non-empty string |
+| `start`, `end` | Numeric seconds, finite and non-negative; end must be at least start |
+| `text` | Non-empty string |
+| `categories` | Optional array of non-empty strings |
+
+Supply explicit start and end times for meaningful timing. The current decoder
+uses zero for missing or null timestamps rather than enforcing their presence.
+String validation checks empty values, not whitespace trimming. Normalization can
+merge segments and reassign IDs, so source IDs need not match output IDs.
+
+The [tiny transcript](../../examples/tiny-transcript.json) is a complete copyable
+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
+
+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.

docs/internal/cli-config.md

@@ -0,0 +1,78 @@
+# Configuration and CLI Change Recipes
+
+This document owns contributor editing and validation steps for configuration,
+CLI wiring, and maintained examples. Definitions of behavior belong to the
+[configuration](../config.md) and [CLI](../cli.md) contracts.
+
+## Changing Configuration
+
+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
+   distinct validation and effective-config commands.
+3. Update redaction when secrets are involved.
+4. Review configuration tests and related CLI tests for precedence, validation,
+   and source-specific behavior. Add or adjust tests for the changed contract
+   according to the [testing policy](../policy/testing.md).
+5. Update the configuration reference and affected [examples](../../examples/).
+
+## Changing CLI Behavior
+
+1. Implement parsing and wiring in `internal/cli`.
+2. Preserve [stream and exit contracts](../cli.md) unless a change is intentional
+   and documented. Review [subprocess integration](../integrations/subprocess.md)
+   when changing output, error, or report handling.
+3. Review `internal/cli` tests and `cmd/audita` subprocess tests; update coverage
+   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#commands-and-help) 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
+go run ./cmd/audita config validate --config examples/configkit-inheritance.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
+go run ./cmd/audita config print-effective --config examples/configkit-inheritance.yml --view explain
+```
+
+The local and ConfigKit inheritance files select `profiles/local`; the service
+file selects `profiles/service`, including the service testing profiles. Keep
+these roots separate because PromptKit validates every final definition in a
+selected root, including definitions that are not selected for a role.
+
+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.
+
+## Runtime Change Checks
+
+Select checks according to the [testing policy](../policy/testing.md):
+
+- Configuration or CLI changes: inspect `internal/core/config` tests,
+  `internal/cli` tests, and `cmd/audita` integration tests.
+- Process/output changes: verify stdout, stderr, exit, output-file, and report
+  behavior against the [CLI contract](../cli.md) and
+  [subprocess guidance](../integrations/subprocess.md), including failures.
+- Report or diagnostics changes: review [report assembly tests and redaction
+  checks](diagnostics-reporting.md#key-tests), metadata fields, and artifact paths.
+- Schema or serialization changes: review [output-schema tests](output-schemas.md#key-tests)
+  and `internal/core/schema` tests, including supported formats and rejection of
+  unsupported schemas.
+- Changes affecting assembled output: inspect controlled HTTP subprocess workflows
+  and retained report/artifact assertions.
+
+Use the [contributor guide](../development.md#baseline-validation) for baseline
+commands. These recipes supplement, rather than duplicate, public contracts.

docs/internal/diagnostics-reporting.md

@@ -0,0 +1,63 @@
+# Diagnostics and Reporting Internals
+
+The [output-file contract](../integrations/output-files.md) owns public
+schemas and the [operations guide](../operations.md) owns physical placement.
+
+`internal/framework/outcomes` contains processing-owned operation references,
+counts, failure reasons, filtering details, and work states. It imports no
+reporting, CLI, or provider package. The runner records those facts per initial
+section and module instance. `internal/framework/processreport` maps them once
+into `internal/core/reporting.Snapshot`, including nullable counts, grouped
+work-unit errors, separate run errors, and one recovery per successful logical
+operation. Reports order stages, sections, validators, and batches by semantic
+identity, never concurrent completion time. The core reporting package owns
+Audita's versioned YAML DTOs, fixed Markdown rendering, and brief CLI
+completion formatter. YAML redaction walks serialized string nodes so numeric
+and boolean values retain their types. Ordinary reports omit raw causes,
+transcript text, complete decisions, and token/timing payloads.
+Validation operations with unavailable decisions report only affected requested
+indices, even when other candidates in the batch continue. Ignored extra
+validator entries yield `validation_decisions_filtered` only for a successful
+operation; they do not count as filtered correction proposals. Failed operations
+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;
+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.
+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
+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.
+
+## Key Tests
+
+Useful tests: `internal/core/reporting/*_test.go`,
+`internal/core/diagnostics/*_test.go`,
+`internal/framework/processreport/*_test.go`, and
+`cmd/audita/main_integration_test.go`.

docs/internal/llm-runtime.md

@@ -0,0 +1,60 @@
+# Audita LLM Runtime
+
+## Client Boundary
+
+`llm.NewRuntime` assembles one PromptKit engine for both roles. PromptKit's
+catalogs and defaults are followed by Audita's embedded prompt and schema
+inputs, operator documents from `profiles_dir`, and the highest-priority
+application backend mapping. Audita owns backend endpoints, capacity settings,
+and resolved credentials; native PromptKit layering owns profile inheritance,
+prompt overrides, and provider-specific fields. Imports are disabled. The
+runtime inspects both selected roles offline, requiring complete model and
+endpoint values and rejecting competing profile credential lookups. A
+role-bound `llm.RoleClient` implements `structuredoutput.Client`; proposal and
+validator contracts alias that interface. Both roles share engine-local backend
+capacity.
+
+Successful construction captures the final definitions and referenced message
+contents. The runtime does not reload operator documents or message files during
+calls. If final engine construction fails, an embedded-only diagnostic
+construction distinguishes shipped asset failures from invalid operator input.
+An asset failure remains an asset error; when embedded construction succeeds,
+the original failure remains a configuration error. The diagnostic engine
+never replaces or executes the requested configuration, and caller cancellation
+skips this path. The captured inspection also supplies an internal source
+ledger: all loaded host YAML plus effective, source-relative host
+`content_file` resources are tracked for output-collision checks.
+
+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.
+
+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.
+
+CLI explain output and debug configuration origins share a value-free projection
+of effective field origins. The [CLI contract](../cli.md) defines its optional
+inheritance evidence fields.
+
+## 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.

docs/internal/modules.md

@@ -0,0 +1,91 @@
+# Audita Modules
+
+## Scope
+
+This document covers internal module contracts and packages. User-selectable keys
+and the default sequence belong to [configuration](../config.md#settings).
+
+## Module Contract
+
+Modules implement `contracts.TranscriptModule`:
+- `Key()`
+- `ReplacementPolicy()`
+- `Validators()`
+- `Propose(ctx, req)`
+
+Runner resolves configured module specs to module instances through `internal/framework/modules`.
+
+## Built-In Modules
+
+Current module packages:
+- `internal/modules/glossary`
+- `internal/modules/homophones`
+- `internal/modules/spoken_word`
+- `internal/modules/grammar`
+
+Current replacement policies:
+- `glossary`: `replace_all`
+- `homophones`: `require_unique`
+- `spoken_word`: `require_unique`
+- `grammar`: `require_unique`
+
+## Proposal Generation Ownership
+
+Shared proposal-generation plumbing is centralized in:
+- `internal/framework/proposal_generation`
+
+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
+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
+request. Generation maps returned references back to the current chunk's actual
+segment IDs, preserving response order and multiple proposals per segment.
+Unknown references become invalid-target candidates for the existing domain
+checks; they are never interpreted as actual transcript IDs. Debug request
+metadata records `segment_ids` in local-reference order (reference 1 is the
+first entry). Shared context encoding lives in `internal/framework/promptcontext`.
+An empty `corrected_text` deletes the identified span when the resulting segment
+remains nonblank. Whitespace-only original spans can express spacing corrections;
+matching stays literal under each module's replacement policy. No automatic
+whitespace cleanup follows application.
+
+## Validator Chain Ownership
+
+Built-in chains are resolved in `internal/validators` per module key.
+Module packages call the built-in chain resolver at construction.
+
+## Failure and Outcome Behavior
+
+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
+failures cancel peers and retain partial observations. Consumer-visible
+outcomes are defined by the [report contract](../integrations/output-files.md).
+
+## Changing Modules
+
+1. Add or update the narrowly scoped package under `internal/modules/<module_key>`.
+2. Keep module prompt selection in the module and its definition in
+   `internal/prompts`; see [prompt assets](prompts.md).
+3. Wire module registration and catalog resolution through framework module
+   registration and the core module catalog. Update selectable keys in the
+   [configuration contract](../config.md) when they change.
+4. Verify replacement policy and validator-chain selection against the
+   [architecture requirements](../policy/architecture.md#correction-and-concurrency-invariants).
+5. Review module, prompt-variable, and proposal-generation tests. Inspect parity
+   and release fixtures when public output changes, choosing sufficient coverage
+   under the [testing policy](../policy/testing.md).
+6. Update this document for implementation changes and the appropriate public
+   contract owner for externally visible changes.
+
+## Key Tests
+
+- `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)

docs/internal/output-schemas.md

@@ -0,0 +1,34 @@
+# Output Encoding Internals
+
+## Scope and Ownership
+
+`internal/core/outputschema` owns encoder registration and resolution. External
+JSON envelopes and segment fields are defined by the
+[output-file contract](../integrations/output-files.md#corrected-transcript);
+selectable values and defaults belong to
+[configuration](../config.md#settings).
+
+## Resolution and Encoding
+
+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).
+An unsupported key fails validation or resolution rather than selecting an
+implicit fallback.
+
+The registry delegates bare segment serialization to the transcript schema
+package and uses an envelope encoder for the versioned form. Report construction
+receives the selected key separately; see [report assembly](diagnostics-reporting.md).
+
+## Changing an Encoder
+
+Update registration, configuration validation, and serialization together. Inspect
+round-trip and shape tests, then update the external output-file contract if the
+serialized form changes. Keep internal helper changes separate from decisions
+about externally visible compatibility.
+
+## Key Tests
+
+- `internal/core/outputschema/registry_test.go`
+- `internal/core/config/config_test.go`
+- `internal/cli/run_test.go`

docs/internal/overview.md

@@ -0,0 +1,97 @@
+# Audita Internal Overview
+
+## Scope
+
+This document owns the implemented component map. For normative boundaries, see
+[architecture policy](../policy/architecture.md); for task-specific reading and
+baseline commands, see the [contributor guide](../development.md).
+
+## Package Map
+
+Executable and command orchestration:
+- `cmd/audita`: executable entry point.
+- `internal/cli`: argument parsing, config commands, streams, filesystem wiring, and process orchestration.
+
+Core deterministic components:
+- `internal/core/config`
+- `internal/core/schema`
+- `internal/core/normalization`
+- `internal/core/chunking`
+- `internal/core/outputschema`
+- `internal/core/diagnostics`
+- `internal/core/reporting`
+- `internal/core/modulecatalog`
+
+Framework orchestration and contracts:
+- `internal/framework/contracts`
+- `internal/framework/modules`
+- `internal/framework/proposal_generation`
+- `internal/framework/proposals`
+- `internal/framework/runner`
+- `internal/framework/validators`
+- `internal/framework/llm`
+- `internal/framework/responseschema`
+- `internal/framework/structuredoutput`
+- `internal/framework/processreport`
+- `internal/framework/promptcontext`
+- `internal/framework/stagename`
+
+Domain implementations:
+- `internal/modules/*`
+- `internal/validators/*`
+- `internal/prompts`
+
+Supporting areas:
+- `docs/`: canonical documentation.
+- `examples/`: maintained copyable inputs and configuration.
+
+## Current Scope
+
+Runtime state is held in memory; optional debug artifacts are retained only
+when requested. Audita does
+not currently implement a plugin framework, generic workflow engine,
+resume/checkpoint/manifest system, remote storage, or multi-process service mode.
+Its role-bound PromptKit adapter implements the structured LLM client contract.
+These are current implementation boundaries, not bans on future work.
+
+## Main Execution Path (`audita process`)
+
+The CLI inspects configuration and profiles, preflights and initializes active
+outputs, optionally creates debug evidence, invokes the runner, and finalizes
+transcript and reports.
+The [pipeline](pipeline.md) owns detailed state transitions; the
+[operations guide](../operations.md) owns the operator workflow and physical
+artifact lifecycle.
+
+## Component Responsibilities
+
+Core components implement configuration defaults/loading/validation/redaction,
+transcript and glossary schemas, normalization and chunking, output encoding,
+diagnostics artifact helpers, and public report structures.
+
+Framework components implement module and validator contracts, proposal
+generation and application, prompt context, runner orchestration, PromptKit
+execution and observation mapping, response schemas, and process-report/correction-ledger assembly.
+Domain packages provide correction modules, built-in validator chains and
+execution metadata, and embedded prompt assets.
+
+These describe the implementation; dependency and ownership requirements belong
+to the [architecture policy](../policy/architecture.md#ownership-and-dependency-direction).
+
+## Change Recipes
+
+- [Configuration, CLI, and example changes](cli-config.md)
+- [Module changes](modules.md#changing-modules)
+- [Validator changes](validators.md#changing-validators)
+- Runtime orchestration changes: use [pipeline](pipeline.md), [LLM runtime](llm-runtime.md),
+  or [diagnostics/reporting](diagnostics-reporting.md) and their test references.
+
+## Related Internal Docs
+
+- [`docs/internal/pipeline.md`](pipeline.md)
+- [`docs/internal/modules.md`](modules.md)
+- [`docs/internal/validators.md`](validators.md)
+- [`docs/internal/llm-runtime.md`](llm-runtime.md)
+- [`docs/internal/diagnostics-reporting.md`](diagnostics-reporting.md)
+- [`docs/internal/prompts.md`](prompts.md)
+- [`docs/internal/output-schemas.md`](output-schemas.md)

docs/internal/pipeline.md

@@ -0,0 +1,45 @@
+# Audita Internal Pipeline
+
+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.
+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
+   module loop. Initial section identity, segment membership, and token
+   estimates stay fixed while text evolves.
+4. Module instances execute in configured order. Sections may propose
+   concurrently, but proposal indices follow section order and response order.
+5. Deterministic validators precede LLM-backed validators. Every submitted
+   candidate receives one decision per validator on a normal return. Fatal returns
+   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
+   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
+   output session. `framework/processreport` builds one snapshot for YAML,
+   Markdown, and CLI totals. Debug evidence is captured separately when enabled.
+
+`runner.Run` returns the final working transcript, initial section inventory,
+explicit `not_started`/`interrupted`/`completed` work units, compact model
+operation outcomes, and per-module results. Candidate payloads are retained
+in the returned output only when debug capture is requested. A work unit can
+complete with model errors and applied corrections. Recoverable model failures
+never trigger shared cancellation. Fatal setup, internal, application, or
+parent-cancellation errors cancel peers, join workers, and preserve earlier
+committed module text for partial reports; no completed transcript is published.
+
+Required transcript/report write failures are fatal. Optional debug writes
+report safely to stderr without changing decisions or exit status. See
+[operations](../operations.md) for file placement and failure handling, and
+[architecture policy](../policy/architecture.md#correction-and-concurrency-invariants)
+for invariants.
+
+Key tests: `internal/framework/runner/*_test.go`,
+`internal/framework/validators/*_test.go`, and
+`cmd/audita/main_integration_test.go`.

docs/internal/prompts.md

@@ -0,0 +1,68 @@
+# Audita Prompt Registry
+
+`internal/prompts` embeds seven PromptKit YAML definitions under
+`assets/prompts`. The IDs and selected version remain:
+
+- `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 reads the embedded definitions as shipped defaults and renders their
+messages from named string variables. Operator documents in `profiles_dir` may
+contribute native keyed prompt definitions and override an embedded
+prompt/version, including its messages and definition-level output settings.
+The effective operator text is captured when the runtime is constructed; the
+embedded assets remain the source of Audita's shipped task instructions. 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 embedded prompt assets retain the shipped task instructions and
+output-schema association. An operator override controls which template
+variables its messages reference: supplying a shared variable does not append
+its text when the effective message omits that reference. 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
+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
+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 structured-call contract carries prompt ID/version, 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
+[configuration](../config.md) for operator-selected profiles.
+
+Proposal instructions describe literal matching, each module's replacement policy,
+source-based proposal identity, and confidence in whether an edit is warranted.
+Proposal `id` and validator `correction_index` values are short, one-based
+references scoped to each request, not internal transcript/proposal identities.
+Mapping belongs to [proposal generation](modules.md) and
+[validator reconciliation](validators.md). Validator instructions distinguish
+confidence in the verdict from the verdict itself. Compact output examples
+illustrate the supplied schema without requiring fixed JSON formatting or key
+order. The grammar article exception and glossary mishearing exception apply
+consistently across their instructions.
+
+Only the three active validator definitions are retained. The unused internal
+`grammar_review` and `spoken_word_review` definitions and type selections were
+removed; built-in chains and operator configuration are unchanged.

docs/internal/validators.md

@@ -0,0 +1,156 @@
+# Audita Validators
+
+## Scope
+
+This document describes internal validator composition, execution order, and
+decision handling. These registry keys identify implementation components; they
+are not independently selectable through [configuration](../config.md#settings).
+
+## Ownership
+
+Built-in validator keys and chains:
+- `internal/validators`
+
+Shared validator runtime mechanics:
+- `internal/framework/validators`
+
+Execution-class metadata:
+- `internal/validators/metadata`
+
+## Built-In Validator Keys
+
+Deterministic:
+- `proposal_shape`
+- `confidence_threshold`
+- `original_text_presence`
+- `non_empty_resulting_segment` — rejects edits that would leave the segment
+  blank, regardless of replacement-span length.
+- `no_effect`
+- `protected_terms`
+
+LLM-backed:
+- `spoken_form_plausibility`
+- `meaning_reversal_review`
+- `editorial_review`
+
+## Built-In Chains
+
+Module chains are defined in `internal/validators/chains.go`.
+Glossary, homophones, spoken_word, and grammar each resolve a fixed ordered chain.
+
+## Runtime Execution
+
+For each module section:
+1. run deterministic validators;
+2. run LLM-backed validators;
+3. record decisions and compact operation outcomes;
+4. carry only approved proposals forward.
+
+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.
+
+## LLM Validator Batching
+
+LLM validators:
+- build canonical validation request payloads;
+- batch using `validation.max_prompt_tokens` and the existing domain token estimator;
+- select an embedded prompt ID and pass payload/description variables to the
+  role-bound structured client with the validator-decision schema.
+
+Oversized single inputs are rejected with a consolidated
+`validation_input_too_large` operation, without a provider call. Recoverable
+model failures make only their batch candidates unavailable while other
+batches continue. PromptKit validates each complete response against the
+validator-decision JSON Schema and performs configured structural repair before
+Audita receives decoded decisions. Each actual batch presents candidates
+numbered from 1, independent of their internal proposal indices. Audita then
+reconciles those local references: one usable entry keeps its
+approval or editorial rejection; a missing or duplicate requested entry makes
+only that candidate unavailable; unexpected indices are ignored. An empty list
+makes all requested candidates unavailable. Decisions and unavailable indices
+map back to internal proposal identities; results are ordered by request identity
+and satisfy strict internal cardinality before the runner advances
+approved candidates. An unavailable candidate never advances as approved.
+Invalid confidence in a decoded test double also makes only its candidate
+unavailable; production schema validation still rejects out-of-range confidence
+before reconciliation. A partially unavailable batch records one failed
+operation with only those requested indices, while a successful batch with
+ignored extras records a decision-filtering recovery. Fatal errors stop the
+chain without returning unchecked candidates as approved. A local result builder
+retains already-collected decisions and operations on early returns; full
+cardinality checks and final sorting remain explicit on completed paths.
+Reconciliation makes no semantic retry or extra model call; guided recovery remains
+[deferred](../roadmap/future.md#domain-aware-response-recovery).
+
+Debug request metadata records `proposal_indices` in local-reference order
+(reference 1 is the first entry). Raw decoded responses and ignored indices use
+local references; reconciled decisions and unavailable indices use internal
+proposal indices. Batch token estimates use the same locally numbered payload
+as prompt encoding.
+
+## Decision and Rejection Reporting
+
+Runner collects decisions, rejected candidates, and operation outcomes. Ledger
+assembly groups decisions by deterministic versus LLM-backed execution metadata.
+The serialized names and fields belong to the
+[report and ledger contract](../integrations/output-files.md); implementation mapping
+is covered by [report assembly](diagnostics-reporting.md).
+
+## Changing Validators
+
+1. Implement validator behavior under `internal/validators/<validator_key>`;
+   update registry and chain wiring in `internal/validators`.
+2. Put shared runtime mechanics in `internal/framework/validators` only when
+   needed. Keep deterministic versus LLM-backed execution metadata explicit.
+3. Preserve exposed identities and decision semantics under the
+   [architecture policy](../policy/architecture.md#correction-and-concurrency-invariants).
+4. Review validator, registry, chain, batching, malformed-output, diagnostics,
+   and decision-cardinality tests; update meaningful coverage under the
+   [testing policy](../policy/testing.md).
+5. Update implementation guidance here and any affected external contract in its
+   [canonical owner](../policy/documentation.md#canonical-ownership).
+
+## Key Tests
+
+- `internal/validators/*_test.go`
+- `internal/framework/validators/*_test.go`
+- `internal/framework/processreport/correction_ledger_test.go`
+- `internal/cli/run_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 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.
+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
+already clear from its own segment does not require such evidence. No audio,
+out-of-chunk context, or complete transcript is implied.
+
+Context is serialized inside the validation item and included in the existing
+payload token estimate. If one enriched item exceeds the configured limit, optional
+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
+relevant definition or neighboring utterance always fits. This uses the existing
+payload estimator, not a new guarantee about the provider's full context window.
+
+## Protected-Name Repetition
+
+Spoken-word cleanup may reduce repeated protected-name occurrences when every
+original protected identity still appears in the resulting segment and surviving
+spellings satisfy existing capitalization checks. Full-segment preview supports
+both a replacement of the repeated phrase and deletion of a redundant span. This
+exception only relaxes the deterministic count guard; editorial and meaning-reversal
+validation still decide whether the repetition was accidental and the edit preserves
+meaning. Intentional emphasis and substantive references remain protected by those
+reviews. Other modules retain their existing protection rules.

docs/migrations/v2.md

@@ -0,0 +1,135 @@
+# Migrating to Audita v2
+
+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
+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.
+
+## Configuration and invocation
+
+Use `version: 2` in a YAML main file. `--config` selects that file; otherwise
+`process` and `config print-effective` look at
+`/usr/local/etc/audita/config.yml`, then `/etc/audita/config.yml`.
+`config validate` requires `--config`. `AUDITA_CONFIG` no longer selects a file.
+Settings resolve from defaults, main file, optional `--overlay <name>` in
+`overlays/<name>.yml`, then explicitly supplied setting flags. General `AUDITA_*`
+environment overlays no longer apply. Unknown fields and version-1 files fail;
+there is no automatic converter.
+
+Keep transcript as the positional path and `--glossary` and `--output` as
+invocation paths. The former `--report-json` output has been replaced by the
+default `errors.yml`, `recoveries.yml`, and `report.md` bundle; use
+`--reporting=false` to disable it or `--report-dir` for stdout output. Keep
+`pipeline.modules` / `--modules` and
+`output.schema` / `--output-schema`. An explicit `pipeline.modules: []` or
+`--modules ''` runs no correction modules; omission uses the default sequence.
+Ordered repetitions still matter.
+
+Move `llm.proposal.base_url` and `llm.validation.base_url` to a shared
+`backends.<id>.endpoint` when both roles use one service. Move old role models to
+PromptKit profile files and select them with `llm.proposal_profile` and
+`llm.validation_profile`, or `--proposal-profile` and
+`--validation-profile`. Omitted validation selection inherits the final proposal
+selection; explicit empty or null is invalid. `profiles_dir` defaults to
+`profiles` beside the main config. Complete profiles name a registered backend
+and model. Per-role `--base-url`, `--validation-base-url`, `--model`, and
+`--validation-model` are retired.
+
+Move old `llm.*.api_key_env` to `backends.<id>.credential`, a scalar name of a
+nonempty environment variable, such as `credential: AUDITA_SERVICE_KEY`.
+Credentials on every surviving backend must resolve, including unselected
+backends. Omit or set null for an unauthenticated local backend. Profiles cannot
+perform another key lookup. `--llm-api-key` and `--validation-llm-api-key` are
+retired. `AUDITA_LLM_API_KEY`, `OPENROUTER_API_KEY`, and
+`AUDITA_VALIDATION_LLM_API_KEY` have no implicit meaning, though any of those
+names can be used explicitly as a credential reference.
+
+Replace `concurrency.total_llm`, `.proposal_llm`, and `.validation_llm` plus
+`--total-llm-concurrency`, `--llm-concurrency`,
+`--proposal-llm-concurrency`, and `--validation-llm-concurrency` with
+`backends.<id>.concurrency` (default 1) and optional `queue_capacity` (default
+1024; zero means no waiting admission). One backend capacity is shared by both
+roles and all retry/repair attempts within this Audita process. It does not
+coordinate other processes.
+
+Move old role `timeout` values and `--llm-timeout-seconds` /
+`--validation-llm-timeout-seconds` to profile `timeout_seconds`, a per-attempt
+limit, and `llm.operation_timeout`, a Go duration such as `15m` covering the
+whole logical call. Replace old `max_retries` and `--max-retries` /
+`--validation-max-retries` with common `llm.transient_retries` (additional
+eligible attempts per generation) and `llm.repair_attempts` (additional
+generations for structurally invalid JSON). Explicit zero disables either
+feature. Cancellation and the operation deadline cover capacity waiting,
+backoff, generation, and repairs. PromptKit owns which failures can retry or
+repair; Audita does not retry semantic rejections.
+
+The following domain settings and explicit flags retain their meaning:
+
+| File field | Explicit flag |
+| --- | --- |
+| `validation.max_prompt_tokens` | `--validation-max-prompt-tokens` |
+| `chunking.target_sections` | `--target-sections` |
+| `chunking.max_section_tokens`, `.min_section_tokens` | `--max-section-tokens`, `--min-section-tokens` |
+| `normalization.max_segment_gap`, `.ellipsis_gap`, `.max_segment_duration`, `.max_segment_tokens` | `--normalize-max-segment-gap`, `--normalize-ellipsis-gap`, `--normalize-max-segment-duration`, `--normalize-max-segment-tokens` |
+| `thresholds.glossary`, `.homophones`, `.spoken_word`, `.grammar` | `--glossary-confidence-threshold`, `--homophones-confidence-threshold`, `--spoken-word-confidence-threshold`, `--grammar-confidence-threshold` |
+| `context.description` | `--transcript-description` |
+| `reporting.enabled`, `.stdout_dir` | `--reporting[=true\|false]`, `--report-dir` |
+| `diagnostics.debug`, `.work_dir` | `--debug[=true\|false]`, `--work-dir` |
+
+Normalization gaps and durations are **numeric seconds**, so replace `4s`,
+`3.5s`, and `60s` with `4.0`, `3.5`, and `60.0`. The operation timeout remains a
+Go duration string. `chunking.target_sections` may be omitted or null for
+automatic chunking; zero is invalid. Null is not a general synonym for omission:
+nonoptional scalar settings reject it. Empty `context.description` clears
+context. Legacy `diagnostics.retention` and `--work-dir-retention` are removed.
+Debug is off by default and its directory is retained whenever enabled.
+
+Remove old implicit variables `AUDITA_MODULES`, `AUDITA_MODEL`,
+`AUDITA_VALIDATION_MODEL`, `AUDITA_BASE_URL`, `AUDITA_VALIDATION_BASE_URL`,
+`AUDITA_LLM_TIMEOUT_SECONDS`, `AUDITA_VALIDATION_LLM_TIMEOUT_SECONDS`,
+`AUDITA_MAX_RETRIES`, `AUDITA_VALIDATION_MAX_RETRIES`,
+`AUDITA_TOTAL_LLM_CONCURRENCY`, `AUDITA_LLM_CONCURRENCY`,
+`AUDITA_PROPOSAL_LLM_CONCURRENCY`, `AUDITA_VALIDATION_LLM_CONCURRENCY`,
+`AUDITA_VALIDATION_MAX_PROMPT_TOKENS`, `AUDITA_TARGET_SECTIONS`,
+`AUDITA_MAX_SECTION_TOKENS`, `AUDITA_MIN_SECTION_TOKENS`,
+`AUDITA_NORMALIZE_MAX_SEGMENT_GAP`, `AUDITA_NORMALIZE_ELLIPSIS_GAP`,
+`AUDITA_NORMALIZE_MAX_SEGMENT_DURATION`, `AUDITA_NORMALIZE_MAX_SEGMENT_TOKENS`,
+`AUDITA_GLOSSARY_CONFIDENCE_THRESHOLD`,
+`AUDITA_HOMOPHONES_CONFIDENCE_THRESHOLD`,
+`AUDITA_SPOKEN_WORD_CONFIDENCE_THRESHOLD`,
+`AUDITA_GRAMMAR_CONFIDENCE_THRESHOLD`, `AUDITA_WORK_DIR`, and
+`AUDITA_WORK_DIR_RETENTION`. Put those values in the named fields above or pass
+their surviving explicit flags.
+
+## Inspecting and operating
+
+Run `audita config validate --config <file>` before processing. Use
+`audita config print-effective --config <file> --view settings|profiles|explain`
+to inspect redacted ConfigKit YAML, selected PromptKit profile controls, or
+field origins and derivations. Each view resolves both roles offline without
+calling a provider. `--overlay testing` selects the same overlay for validation,
+inspection, and processing. The old effective-config JSON format is replaced by
+YAML; settings YAML alone does not show profile-owned model controls.
+
+The [ordinary output contract](../integrations/output-files.md) now uses
+version-1 `audita-errors` and `audita-recoveries` YAML documents plus a fixed
+Markdown overview. Compact outcomes distinguish logical operations from
+provider attempts. With debug enabled, utilization remains grouped by backend
+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
+and paths, [configuration](../config.md) for all settings, and the
+[CLI reference](../cli.md) for current flags.
+
+Debug ledger consumers should recognize the deterministic validator key
+`non_empty_resulting_segment` in place of `non_empty_corrected_text`. The
+`empty_resulting_segment` reason is unchanged. Candidate-backed ledger entries
+now include `proposed_corrected_text: ""` for an empty replacement, and applied
+deletions also include `applied_corrected_text: ""`; omitted fields still mean
+there was no candidate or no applied edit, respectively. See the
+[debug artifact contract](../integrations/output-files.md#debug-only-files).

docs/operations.md

@@ -0,0 +1,94 @@
+# 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.
+
+## Normal Workflow
+
+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.
+
+## Required Output Files
+
+Reporting is enabled by default. For file transcript output, `errors.yml`,
+`recoveries.yml`, and `report.md` go in the transcript output's parent directory
+unless `--report-dir` is explicitly supplied. For stdout transcript output, they
+go in the effective `reporting.stdout_dir` (default `.`), including a
+`--report-dir` override. A config-file or overlay value for
+`reporting.stdout_dir` alone does not redirect file-output reports. An active
+selected report directory must be nonblank. `--reporting=false` suppresses all
+three reports and leaves their destination inactive, so it is not probed merely
+because `--report-dir` was supplied. It does not suppress the stderr summary or
+fatal errors. Stdout contains only transcript JSON; file output leaves it empty.
+
+Existing report directories and parents for regular transcript files must be
+writable. Audita prevents report writes from overwriting transcript, glossary,
+loaded application configuration, host YAML discovered under `profiles_dir`,
+or host message files referenced by effective PromptKit `content_file` fields,
+and rejects conflicting output destinations. Source paths come from the
+runtime's captured configuration; unrelated files in the selected directory
+remain eligible 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 unless an explicit `--report-dir`
+selects another directory; disable reporting when that placement is unsuitable
+for a stream destination.
+
+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`.
+
+## Diagnostics Directory
+
+`--debug` or `diagnostics.debug` enables detailed evidence independently of
+reporting. One directory named `run-<id>` is created under
+`diagnostics.work_dir` (default `/tmp/audita`), which `--work-dir` can override,
+and retained on success or failure. Selecting `--work-dir` alone does not enable
+capture. 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.
+
+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.
+
+## 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.

docs/oss/attribution.md

@@ -0,0 +1,226 @@
+# 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/release.md` incorporates revision
+`e833faddf120c789a9b45348edaf75720de16348`; 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/e833faddf120c789a9b45348edaf75720de16348/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/policy/src/commit/e833faddf120c789a9b45348edaf75720de16348/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843).
+
+[Source](https://gitea.maximumdirect.net/eric/policy/src/commit/e833faddf120c789a9b45348edaf75720de16348).
+
+## ConfigKit
+
+Selected module: `gitea.maximumdirect.net/eric/ConfigKit` at `v0.7.1`.
+
+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://gitea.maximumdirect.net/eric/ConfigKit/src/commit/6fffde4af8f31f99d3ee295c426eb3234cb0fb77/COPYRIGHT).
+
+[Source](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/6fffde4af8f31f99d3ee295c426eb3234cb0fb77).
+
+## ReleaseKit
+
+Selected module: `gitea.maximumdirect.net/eric/ReleaseKit` at `v0.4.1`.
+
+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://gitea.maximumdirect.net/eric/ReleaseKit/src/commit/2d5a8110c61e31daf8698766114ae305d0e0e469/COPYRIGHT).
+
+[Source](https://gitea.maximumdirect.net/eric/ReleaseKit/src/commit/2d5a8110c61e31daf8698766114ae305d0e0e469).
+
+## Go runtime and standard library
+
+Selected toolchain: Go 1.26.8 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/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/PATENTS).
+
+[Source](https://github.com/golang/go/commit/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e).
+
+## Go vendored golang.org/x/crypto
+
+Material: `golang.org/x/crypto` at `v0.46.1-0.20251210140736-7dacc380ba00` in the Go 1.26.8 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/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/src/vendor/golang.org/x/crypto/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/src/vendor/golang.org/x/crypto/PATENTS).
+
+[Source](https://github.com/golang/go/commit/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e).
+
+## Go vendored golang.org/x/net
+
+Material: `golang.org/x/net` at `v0.47.1-0.20260731170545-cb1d721f7fb3` in the Go 1.26.8 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/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/src/vendor/golang.org/x/net/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/src/vendor/golang.org/x/net/PATENTS).
+
+[Source](https://github.com/golang/go/commit/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e).
+
+## Go vendored golang.org/x/sys
+
+Material: `golang.org/x/sys` at `v0.39.0` in the Go 1.26.8 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/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/src/vendor/golang.org/x/sys/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/src/vendor/golang.org/x/sys/PATENTS).
+
+[Source](https://github.com/golang/go/commit/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e).
+
+## Go vendored golang.org/x/text
+
+Material: `golang.org/x/text` at `v0.32.0` in the Go 1.26.8 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/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/src/vendor/golang.org/x/text/LICENSE) |
+[PATENTS](https://github.com/golang/go/blob/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e/src/vendor/golang.org/x/text/PATENTS).
+
+[Source](https://github.com/golang/go/commit/c293dd49cbe25e1fe8d97d94a5cb618e7b6d831e).
+
+## 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: `gitea.maximumdirect.net/eric/promptkit` at `v0.14.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://gitea.maximumdirect.net/eric/promptkit/src/commit/143c6e9b3a675872117b0471e2ff8bcb25055a54/COPYRIGHT).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit/src/commit/143c6e9b3a675872117b0471e2ff8bcb25055a54).
+
+## Promptkit OpenRouter Catalog
+
+Selected module: `gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v3` at `v3.20260930.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: MIT
+
+License and notices: [MIT](licenses/MIT-Catalogs.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/f17d208cb7ad1fb043cda2266cd3011d11b40aa0/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/f17d208cb7ad1fb043cda2266cd3011d11b40aa0/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/f17d208cb7ad1fb043cda2266cd3011d11b40aa0).
+
+## Promptkit Rakestrawhome Catalog
+
+Selected module: `gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v3` at `v3.20260930.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: MIT
+
+License and notices: [MIT](licenses/MIT-Catalogs.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/993443d88c451901f4c917fa00c204fd3b54d28d/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/993443d88c451901f4c917fa00c204fd3b54d28d/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/993443d88c451901f4c917fa00c204fd3b54d28d).
+
+## 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).

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-Catalogs.txt

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

docs/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

@@ -0,0 +1,101 @@
+# Agent Policy
+
+**Base Policy Version:** 1.3
+
+**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 must read and follow these rules.
+
+## Implementation Discipline
+
+**KEY PRINCIPLES:** Write the simplest idiomatic code that satisfies the user's
+request. Do not implicitly strengthen requirements, restrictions, or guarantees
+beyond what the user actually requested.
+
+**Keep implementation machinery proportionate.** Use straightforward,
+idiomatic code and introduce only the machinery needed to support the requested
+behavior and flexibility. Optimize for conceptual simplicity and
+maintainability, not for the fewest lines, fewest options, or narrowest product
+surface.
+
+**Do not invent restrictions.** Do not reject, prohibit, constrain, cap,
+harden, or otherwise narrow behavior unless required by the user, an explicit
+repository contract, or an unavoidable correctness constraint. Preserve
+operator and caller choice where policy has not been established. If an
+additional restriction appears advisable, present it as a decision rather than
+silently implementing it.
+
+**Do not invent guarantees.** Do not strengthen public contracts, guarantees,
+or invariants beyond those expressly requested by the user.
+
+**Use the standard library.** For example: in almost every case, the best
+approach to copying files is to use the standard library. Writing custom code to
+implement power-loss protection at the application level, or to guard against
+bad actors with privileged and concurrent access to the host's filesystem,
+is wasteful, unnecessary, and not idiomatic. Stick to the simple, standard, and
+idiomatic approach unless another path is expressly requested by the user.
+
+**An implementation detail is not repository policy.** Tests and documentation
+must not elevate incidental behavior into a durable guarantee or restriction
+unless that behavior was expressly selected as part of the contract.
+
+## Codebase Discovery
+
+This project uses codebase-memory-mcp to maintain a knowledge graph of the
+codebase. Always prefer its graph tools over grep, glob, or file search for code discovery.
+If the project is not indexed, run `index_repository` first.
+
+Use this order:
+
+1. `search_graph` to find functions, classes, routes, and variables by pattern.
+2. `trace_path` to trace callers and callees.
+3. `get_code_snippet` to read a specific function or class.
+4. `query_graph` for complex graph queries.
+5. `get_architecture` for the high-level project summary.
+
+Fall back to grep or glob for string literals, error messages, configuration
+values, non-code files, or when the graph tools return insufficient results.
+
+Examples:
+
+- Find a handler: `search_graph(name_pattern=".*OrderHandler.*")`.
+- Find callers: `trace_path(function_name="OrderHandler", direction="inbound")`.
+- Read source: `get_code_snippet(qualified_name="pkg/orders.OrderHandler")`.
+
+## Git Commit Policy
+
+By default, commit each completed, nonempty unit of work using a
+concise, plain-English message describing what changed. This policy is standing
+authorization to create those local commits; a separate user request is not
+required. An explicit user instruction to leave work uncommitted takes precedence.
+
+A unit of work is a focused, reviewable outcome, including its relevant tests and
+documentation.
+Complete the appropriate validation before committing. If work is incomplete or
+validation is blocked, report that state accurately.
+
+Before committing:
+
+1. Run `git status --short` and review the relevant diff, including any staged
+   changes. Identify changes that predate the current unit of work.
+2. Exclude secrets, local environment files, generated junk, and unrelated changes.
+3. Stage only the files or hunks belonging to the completed unit. Use `git add .`
+   only when every included change belongs to that unit. Preserve unrelated
+   staged and unstaged work.
+4. Review `git diff --staged` and run appropriate checks for the change. Reuse
+   successful checks for unchanged content.
+5. Review `git log --oneline -n 10` and use
+   `git commit -m "<concise plain-English commit message>"`.
+6. Report the commit identifier and any remaining uncommitted work.
+
+If the unit cannot be safely separated from pre-existing work, leave it uncommitted
+and explain the overlap rather than silently including that work. If a commit
+fails, preserve the changes and report the failure; do not bypass hooks.
+
+Default commit authorization does not authorize pushing, publishing, amending,
+resetting, reverting, or rewriting history. Those actions require a separate user
+instruction. Do not use `git commit -a` or `git commit --no-verify` to bypass the
+staging and validation discipline above.

docs/policy/architecture.md

@@ -0,0 +1,143 @@
+# Architecture Policy
+
+**Base Policy Version:** 1.3
+
+**Last Updated**: 2026-09-28
+**Upstream Source:** [Standard Repository Policies architecture](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/architecture.md)
+
+## Purpose And Ownership
+
+The adopted policy defines the application's purpose and the architectural
+constraints contributors must follow. It owns system boundaries, responsibility
+and dependency rules, established invariants, and explicit non-goals.
+
+Describe the concrete package inventory and implementation mechanics in internal
+documentation. Link to canonical public contracts for their exact behavior and
+to ADRs for decision rationale.
+
+## Architectural Approach
+
+Hexagonal architecture is strongly recommended, including encapsulating external
+integrations and APIs within internal adapters. Keep domain and application
+logic independent of external integration details, and make dependency direction
+clear in the adopted policy.
+
+Implement that separation with proportionate, idiomatic code. Choose interfaces
+and package layout to serve the application's actual boundaries. Use adapters
+for collaborators with external integration responsibilities.
+
+## Adopted Constraints And Implemented Structure
+
+Architectural constraints govern current and future development. Record
+implemented structure accurately, proposals and implementation status in the
+roadmap, and significant decisions and rationale in ADRs. Describe a target
+structure as implemented when its changes land.
+
+Constraints must reflect deliberately selected requirements and decisions.
+Do not promote incidental implementation choices into architectural invariants.
+
+## Application-Specific Topics
+
+Audita is a single-process Go CLI for transcript polishing. Its architecture
+separates deterministic transcript processing from external LLM effects through
+narrow contracts and adapters. Correction modules and validators remain explicit,
+composable components in an ordered processing pipeline.
+
+This policy owns architectural requirements. The [internal overview](../internal/overview.md)
+owns the implemented component inventory and links to runtime mechanics.
+[CLI](../cli.md), [configuration](../config.md), [operations](../operations.md),
+and [integration documentation](../integrations/subprocess.md) own external contracts.
+
+## Ownership and Dependency Direction
+
+- **Core:** owns domain data handling and reusable configuration, schema,
+  normalization, chunking, output, diagnostics, and reporting contracts. Domain
+  behavior must not require CLI or provider-transport knowledge.
+- **Framework:** owns orchestration contracts and shared runtime mechanics for
+  modules, validators, proposals, LLM adapters, and report assembly.
+  It composes domain operations through explicit inputs and outputs.
+- **Modules:** own narrowly scoped correction behavior and module-specific prompt
+  choices. Keep module packages separate rather than collapsing their distinct
+  responsibilities into a broad generic stage abstraction.
+- **Validators:** own validation behavior and composition. Deterministic and
+  LLM-backed validators remain explicit, independently composable elements.
+- **Prompts:** own embedded prompt assets and metadata used by the runtime.
+- **CLI and adapters:** own command parsing, streams, filesystem wiring, and
+  transport. Keep these concerns outside module, validator, and schema logic.
+
+LLM transport belongs behind `StructuredLLMClient` and framework adapter
+boundaries. Prefer small shared helpers over broad rewrites. Keep module and
+validator inputs, outputs, and configuration dependencies explicit, without
+hidden global state.
+
+## Correction and Concurrency Invariants
+
+- 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
+  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
+  and parent cancellation stop peers and join them.
+- Keep module and validator identities, reason codes, and execution-class
+  distinctions stable where exposed as contracts.
+
+The [pipeline](../internal/pipeline.md), [modules](../internal/modules.md),
+[validators](../internal/validators.md), and [LLM runtime](../internal/llm-runtime.md)
+describe how these requirements are implemented.
+
+## State and Compatibility
+
+Keep transcript mutation and output handling deterministic around external
+calls. Reports and correction ledgers are derived from processing results.
+Preserve the separation between transient processing state and filesystem
+adapters; physical report placement and optional debug retention belong to
+[operations](../operations.md).
+
+Public CLI, configuration, output-schema, diagnostics, report, prompt, module,
+and validator contracts should remain stable unless a change is deliberate and
+tested. The resilience work intentionally replaced the earlier JSON process
+report with versioned errors/recoveries YAML and a fixed Markdown overview;
+future changes should treat those current contracts deliberately. Current implementation
+limits are documented in the [internal overview](../internal/overview.md#current-scope);
+they are not additional prohibitions on future development.
+
+## 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
+[CLI contract](../cli.md) and the artifact handling defined by
+[operations](../operations.md).
+
+Diagnostics, reports, and surfaced errors must not leak configured LLM secrets.
+Configuration redaction and LLM payload/error redaction have separate
+responsibilities and should remain separate. Implementation details belong in
+[diagnostics and reporting](../internal/diagnostics-reporting.md).
+
+## 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.
+
+Do not introduce broad CLI, dependency-injection, workflow, logging, or plugin
+frameworks without a concrete implemented need and focused tests.
+
+## Testing and Documentation
+
+Follow the [testing policy](testing.md) for risk-based sufficiency and stable test
+boundaries. Keep tests close to the behavior they protect; shared helpers should
+remove duplication without obscuring component-specific behavior. Relevant
+internal docs identify component tests and change recipes; the
+[contributor guide](../development.md) provides baseline validation commands.
+
+Follow the [documentation policy](documentation.md) for ownership, current versus
+future behavior, and the ADR lifecycle. Keep architecture concise and normative;
+use the roadmap for implementation plans rather than maintaining a changelog or
+future-feature specification here.

docs/policy/documentation.md

@@ -0,0 +1,174 @@
+# Documentation Policy
+
+**Base Policy Version:** 1.11
+
+**Last Updated**: 2026-09-28
+**Upstream Source:** [Standard Repository Policies documentation](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/documentation.md)
+
+## Purpose
+
+This policy assigns each documentation topic to one canonical owner. Its goal is
+to keep this application's documentation accurate, concise, discoverable, and resistant
+to drift for users, operators, developers, integrators, and LLM coding agents.
+
+## Core Rules
+
+### One Canonical Owner
+
+Each authoritative fact belongs in one document. A non-owning document may give
+a short, stable summary for orientation, but it must link to the canonical owner
+for volatile details.
+
+Volatile details include commands, flags, configuration fields and defaults,
+module keys, schemas, file names, paths, status codes, retry behavior, and
+runtime guarantees. If readers could reasonably treat a statement as a
+contract, maintain it only in the owning document.
+
+### Current And Future Behavior
+
+Outside `docs/roadmap/`, documentation describes implemented behavior only.
+Partial features may be described only to their implemented boundary.
+
+Architectural constraints may govern future changes. 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. 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 for complete copyable files.
+
+Examples must be valid, secret-free, and tested where practical. Commands and
+configuration used in documentation should match the application.
+
+### Security And Privacy
+
+Documentation and examples must not contain real credentials, private keys,
+private environment dumps, sensitive source material, or private infrastructure
+details unless intentionally public. Document secret-handling mechanisms, not
+secret values.
+
+## Canonical Ownership
+
+| Topic | Canonical owner | Owned content | Content owned elsewhere |
+| --- | --- | --- | --- |
+| Product orientation and minimal end-to-end quickstart | `README.md` | 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 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 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. |
+
+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
+
+Link among orientation, architecture, and internal documents; maintain each
+package or behavior description in its canonical owner.
+
+### Commands, Configuration, And Operations
+
+CLI documentation answers how to invoke the application. Configuration
+documentation answers what settings mean. Operations answers what happens to
+runtime state and how to operate or recover the application. When a workflow
+crosses these topics, choose the document that owns the task and link to the
+other contracts.
+
+### Releases
+
+The release policy defines requirements and invariants that every release must
+satisfy. The repository-specific release procedure defines the commands and
+workflow maintainers use to satisfy that policy. Release notes record history
+at immutable tags. Maintain current behavior in its canonical documentation,
+update it with the corresponding behavior changes, and keep release procedures
+consistent with adopted policy.
+
+### Project Licensing And Upstream Attribution
+
+README and release documents link to the canonical licensing and attribution
+materials under the [OSS policy](oss.md). The release procedure owns URL
+construction and publication mechanics.
+
+### Contracts And Implementation
+
+Integration and API documents define externally observable shapes and
+semantics. Internal documents explain how this application implements or consumes those
+contracts. Internal docs may name a field, file, or protocol to identify a
+dependency, but must link to its canonical contract for the definition.
+
+### Security Topics
+
+This policy owns what documentation and examples may contain. Architecture owns
+application security invariants. Configuration owns credential-supply
+mechanisms. Operations owns permissions and handling of sensitive runtime
+artifacts. Internal docs own implementation mechanisms only.
+
+## Architecture Decision Records
+
+Use sequentially numbered ADR filenames such as
+`0001-record-architecture-decisions.md`. Follow the lightweight Nygard format:
+
+1. title;
+2. status;
+3. date;
+4. context;
+5. decision;
+6. alternatives considered;
+7. consequences.
+
+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.
+
+## Maintenance
+
+When behavior changes, update its canonical owner in the same change. If
+ownership moves, remove the old definition and replace it with a link where
+navigation remains useful.
+
+Before completing documentation work:
+
+- verify affected behavior and examples;
+- check commands, flags, fields, defaults, schemas, and paths against their
+  implementation;
+- keep unimplemented behavior in the roadmap, subject to the ADR exception;
+- remove stale references and validate links;
+- confirm that non-owning documents summarize and link rather than redefine;
+- confirm that no secrets or sensitive private data were added.

docs/policy/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,219 @@
+# Open Source Licensing And Attribution Policy
+
+**Base Policy Version:** 1.8
+
+**Last Updated**: 2026-09-28
+**Upstream Source:** [Standard Repository Policies oss](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/oss.md)
+
+## Purpose And Scope
+
+This policy defines project licensing conventions and a repeatable House Format
+for upstream attribution and license notices. It covers the project's own code
+and upstream components incorporated into or distributed with the application
+or library, including relevant transitive dependencies and copied code,
+documentation, or assets.
+Determine treatment from the component's terms and actual use.
+
+Consulting development guidance or using tooling alone does not require an
+attribution entry. Copying or adapting documentation for inclusion in the
+repository is different: preserve its applicable attribution and license terms.
+A material's role as development guidance does not exempt copied documents.
+Apply any express permissions for attribution-free reuse of example formatting.
+
+The baseline is a publicly available source repository with releases published
+alongside it. The format is independent of language, forge, and build system.
+It does not require attribution for every development tool, establish license
+compatibility, or resolve every obligation arising from use or distribution.
+
+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/d84a38ebab26f048cafbe59a2246700c35d29843/examples/licensing/application/COPYRIGHT)
+or [library COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/examples/licensing/library/COPYRIGHT)
+to create the project’s root `COPYRIGHT` file.
+Use verified project names, contribution years, and copyright holders.
+For another selected license, adapt the grant, SPDX expression, disclaimer, and
+text references together to reflect the author's selected grant.
+
+For GPLv3 projects, copy the complete GPLv3 text into `LICENSE`. For LGPLv3
+projects, place the complete LGPLv3 text followed by the complete GPLv3 text in
+`LICENSE`; the LGPL incorporates the GPL terms. Keep the texts unmodified and
+place project-specific statements in `COPYRIGHT`. For the default grants, the
+grant and SPDX expression in `COPYRIGHT` must expressly identify `or-later`;
+follow the author’s choice if a different grant is selected.
+
+For other licenses, provide their complete text and any required project-specific
+fields; the standard reference collection remains unchanged. Keep `COPYRIGHT`,
+`LICENSE`, SPDX expressions, and README descriptions consistent with the actual
+grant. This convention introduces no blanket requirement for per-file headers;
+preserve notices or add them where the applicable terms require them.
+
+Identify separately licensed documentation or assets in the project grant, with
+links to their attribution and license information. An application's default
+code license does not override the terms of incorporated documentation.
+
+## Upstream Attribution House Format
+
+Begin `docs/oss/attribution.md` with `# Open Source Attribution Notices`,
+followed directly by component entries. These comprise the complete document.
+
+Each entry presents these five fields in order, with blank lines between them:
+
+1. **Project name** as a level-two heading. An optional identification paragraph
+   may follow, such as `Selected module: MODULE at VERSION.` with the module and
+   version in backticks. For copied documentation, a concise `Material:` sentence
+   may identify the affected files and whether they were adapted or copied
+   without modification. A factual qualifier such as `(transitive dependency)`
+   is permitted. Limit optional identification prose to factual component and
+   material scope.
+2. **Upstream copyright statement or statements**, preserving their wording.
+   Put multiple statements in separate paragraphs. Include this field when the
+   selected upstream source supplies an applicable statement; otherwise, omit it.
+3. **SPDX license identifier or expression**, when applicable, using
+   `SPDX-License-Identifier: EXPRESSION`.
+4. **License and notice links**, beginning `License and notices:`, separated
+   by ` | `, and ending with a period. Label local standard texts by license
+   name, such as `MIT` or `Apache 2.0`. Label upstream files by their actual
+   filenames, such as `COPYRIGHT`, `LICENSE`, `NOTICE`, or `PATENTS`.
+5. **Source repository link**, rendered exactly as `[Source](COMMIT_URL).`.
+
+Use the upstream [attribution example](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/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

@@ -0,0 +1,251 @@
+# Release Policy
+
+**Base Policy Version:** 1.6
+
+**Last Updated**: 2026-10-08
+**Upstream Source:** [Standard Repository Policies release](https://gitea.maximumdirect.net/eric/policy/src/commit/e833faddf120c789a9b45348edaf75720de16348/docs/policy/release.md)
+
+## Purpose
+
+This policy defines a proportionate workflow for validating and publishing an
+intended source revision under a fresh version. Releases should require little
+routine intervention, avoid repeated work, and preserve published contents.
+
+Adopt stronger verification or reproducibility requirements through an explicit
+project-specific decision justified by the intended audience and support needs.
+
+The repository-specific commands belong in `docs/release.md`. Historical release
+summaries belong in `docs/releases/`. The procedure must agree with the adopted
+policy and link to it rather than introduce additional release requirements.
+
+## Release Model And Completion
+
+A source release identifies one exact committed source revision through an
+immutable version tag and a version-matched, checked-in release note. The
+primary release branch is `main` unless the adopted policy specifies otherwise.
+The procedure must name the authoritative publication remote.
+
+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.
+
+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
+
+| Platform | Support |
+| --- | --- |
+| Linux amd64 | Required production target |
+| Linux arm64 | Required production target |
+| 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. Prereleases require an explicit adopted policy defining
+their format and use.
+
+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 or raise the Go consumer
+  minimum as described below; and
+- a patch release may make backward-compatible fixes.
+
+Before `v1.0.0`, a minor release may change a documented public, operational,
+configuration, data, integration, or compatibility contract when the release
+note explains the impact and required consumer action. A patch release must
+not intentionally break those contracts within its minor line.
+
+Additional compatibility promises and deliberate exceptions belong in the
+adopted policy or canonical contract documentation. Release notes explain
+changes; they do not redefine current compatibility contracts.
+
+## Consumer Minimum And Release Toolchain
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+## Release Documentation And Preparation
+
+Every new release must include `docs/releases/<version>.md` in the tagged
+source tree. Use the complete version tag as the filename and begin with a
+title containing the product name and that exact version.
+
+Include a short summary and any relevant compatibility impact or upgrade
+instructions. Choose sections suited to the release and keep the note
+proportionate to the change.
+
+Keep exact current contracts in their canonical documents and update affected
+documentation with the behavior change. Link to those documents from the note
+where useful. 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.
+
+## Publication Guards
+
+Automate the checks needed to publish the intended source under a fresh version:
+
+- the version has the adopted format and is unused locally and on the
+  authoritative remote;
+- the worktree and index are clean on the primary release branch;
+- the source being published is the exact candidate that passed validation,
+  including its matching release note;
+- the remote primary branch already identifies that 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.
+
+Fetch the authoritative branch and tag state as needed for these checks.
+Do not force branch or tag updates to bypass a failed guard. Publish explicit
+refs rather than all local tags. Do not require CI success, publication-service
+availability checks, or a separate manual confirmation for each guard.
+
+## Immutability And Failure Recovery
+
+Published version tags and published contents are immutable. Do not move,
+overwrite, recreate, or delete a published tag, or replace a published artifact,
+checksum, signature, provenance statement, or release note under that version.
+The checked-in note at the immutable tag is that release's historical record.
+
+If validation fails before publication, correct and commit the candidate and
+rerun the publication command. If a push fails or its outcome is ambiguous,
+inspect the authoritative remote before retrying. Remove an unpublished local
+tag only after confirming it was never published or used by a release channel.
+An unavailable remote leaves publication status unknown; do not overwrite a tag
+to resolve uncertainty.
+
+Transient network, authentication, CI, or consumer-availability failures do not
+by themselves require a new version. Asynchronous delivery may be retried from
+the same immutable tag. Missing artifacts may be published later, provided
+existing published contents are not replaced and the additions remain consistent
+with the tagged source and any already-published checksum manifest. If that
+cannot be achieved, publish a new version.
+
+A defect requiring changes to published source or contents requires a corrected
+commit, a new semantically appropriate version, a matching release note, and
+the release procedure again. Leave the original release intact. A channel's
+yank, deprecation, or advisory mechanism may warn consumers away from a defective
+release without replacing its contents or reusing its version.
+
+## Repository Release Procedure
+
+Maintain `docs/release.md` as a short, executable maintainer runbook. It must
+identify:
+
+1. prerequisites, 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.
+
+Use copyable commands where practical. Keep optional diagnostics and consumer
+verification clearly optional. The procedure must not turn preparation work,
+ordinary change review, or post-publication investigation into additional
+release gates.

docs/policy/testing.md

@@ -0,0 +1,263 @@
+# Testing Policy
+
+**Base Policy Version:** 1.3
+
+**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 optimize for sufficient confidence in important behavior while minimizing friction on future development.
+
+## Every test has a cost
+
+Every test has an immediate and continuing cost: writing, review, execution,
+diagnosis, fixture maintenance, and updates when legitimate behavior changes.
+Tests can also constrain refactoring, duplicate policy, and add failure noise.
+
+A test is warranted only when the confidence it provides justifies these costs.
+Evaluate that tradeoff at two levels:
+
+1. **Per test:** What realistic defect does this test detect, how consequential would that defect be, and is that protection worth the test's lifetime cost?
+2. **Across the suite:** Does this collection provide materially more confidence than a smaller, simpler suite would?
+
+Some friction is intentional. Tests should make dangerous changes—such as breaking compatibility, corrupting data, violating security boundaries, or reintroducing subtle bugs—require deliberate review. Keep ordinary internal changes inexpensive.
+
+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
+
+Use a **classical/Detroit-style** approach:
+
+- Test observable behavior, resulting state, contracts, and invariants.
+- Use real internal collaborators when they are fast and deterministic.
+- Use fakes, stubs, or mocks primarily at expensive, nondeterministic, destructive, or external boundaries.
+- Prefer package-level behavioral tests over tests coupled to private helpers or internal call sequences.
+- Treat exact collaborator interactions as testable behavior only when the interaction itself is a requirement.
+
+Examples of appropriate seams include clocks, randomness, subprocesses, remote APIs, object storage, email, and paid LLM calls.
+
+## Test execution requirements
+
+Tests in the default suite must be deterministic, offline, and independent of real credentials. They must not invoke paid APIs or depend on mutable external services. Tests that require live infrastructure must be explicitly opt-in and clearly separated from the default suite.
+
+Control clocks, randomness, environment variables, and other process-global or machine-specific state when they affect behavior. Tests should be safe to run repeatedly and alongside other tests without depending on execution order or state left by an earlier test.
+
+## What deserves tests
+
+To the extent the following features are present in the application, prioritize tests for:
+
+1. Public and package-level contracts.
+2. Domain rules and important invariants.
+3. Boundary conditions and malformed input.
+4. Failure handling, cancellation, retries, recovery, and partial success.
+5. Serialization, schemas, compatibility, and round trips.
+6. Previously observed or plausible regressions.
+7. Representative integration and end-to-end workflows.
+
+A package-level contract comprises behavior relied upon by another package or major collaborator.
+
+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
+
+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:
+
+- a smaller pure function when dense domain logic is most clearly isolated there;
+- a package-level operation when several internal collaborators jointly produce the behavior; or
+- a larger integration boundary when correctness emerges from interaction with a real dependency.
+
+## Test behavior, not implementation
+
+A test should protect a selected decision, contract, or invariant.
+
+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.
+
+Behavioral tests should normally remain stable through internal refactoring that preserves the contract.
+
+## Expected effects of different changes
+
+Use the following expectations when evaluating test failures and test maintenance:
+
+| Change | Expected effect on tests |
+|---|---|
+| Internal refactor that preserves behavior | Existing tests should normally remain unchanged and continue to pass. |
+| Change to an internal default with no contractual significance | Behavioral tests should normally remain unchanged; tests should derive expectations from configuration or relationships rather than duplicate the old value. |
+| Intentional change to public behavior, policy, schema, or compatibility guarantees | The relevant tests should be reviewed and changed deliberately. |
+| Accidental violation of a contract or invariant | Tests should fail; fix the production code rather than rewriting the tests to accept the defect. |
+
+A test failing is not the same as a test needing to be edited. Many tests may correctly fail because of one production defect. The maintenance smell is a correct internal change that requires unrelated expectation updates throughout the suite.
+
+## Separate mechanism from policy
+
+Derive expectations from test-controlled configuration and relationships.
+
+For this example, assume the selected contract rejects a request to start more
+processes than a configured limit. Do not encode its production default indirectly:
+
+```go
+// Production default:
+const maxConcurrency = 4
+
+// Brittle test:
+err := startProcesses(5)
+require.Error(t, err)
+```
+
+Instead, test the mechanism relationally:
+
+```go
+const limit = 2
+runner := NewRunner(limit)
+
+require.NoError(t, runner.Start(limit))
+require.ErrorIs(t, runner.Start(limit+1), ErrTooMuchConcurrency)
+```
+
+For this selected contract, the test should prove:
+
+- the configured limit is accepted; and
+- one beyond the configured limit is rejected.
+
+Rejection is not a general requirement for concurrency control. If the selected
+contract queues excess work or limits active workers while accepting larger
+batches, test that behavior instead. Do not add rejection or a configurable
+limit solely to reproduce this example.
+
+The production default should be tested exactly only when its literal value is itself a public, operational, safety, protocol, or compatibility requirement.
+
+Apply the same rule to limits, timeouts, capacities, retry counts, and ranges: test relationships and behavior.
+
+For established concurrency limits, distinguish these behaviors where the contract requires them:
+
+1. **Configuration handling:** values are accepted or rejected according to the selected contract.
+2. **Runtime enforcement:** observed peak concurrency never exceeds the configured limit.
+
+Use a test-controlled limit and measure the behavior relative to that limit.
+
+## Assign each behavior a test owner
+
+Where these layers exist, assign ownership as follows:
+
+- Parser tests own parsing cases.
+- Validator tests own validation rules.
+- Domain tests own transformations and invariants.
+- Adapter tests own external integration behavior.
+- Orchestrator tests own coordination and failure propagation.
+- CLI tests own argument and configuration mapping.
+- End-to-end tests prove that representative assembled workflows work.
+
+Give each layer its distinct responsibility and keep expectation updates localized to the contract being changed.
+
+## Use test doubles deliberately
+
+Choose the least elaborate test double that provides the required control or observation.
+
+As a default:
+
+1. Prefer real collaborators when they are fast and deterministic.
+2. Use small in-memory fakes when realistic stateful behavior is helpful.
+3. Use stubs when a dependency only needs to provide controlled responses.
+4. Use mocks when the interaction itself is contractual.
+
+Mocks are appropriate when the contract includes facts such as:
+
+- a notification is sent exactly once;
+- a transaction is committed only after successful writes;
+- cancellation reaches a subprocess;
+- an expensive API is called no more than once; or
+- a security audit event is emitted.
+
+## Go-specific guidance
+
+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 when exploring broad input spaces, such as parsers or path handling, adds useful protection beyond representative cases;
+- golden files only when the complete output is intentionally stable;
+- integration tests where correctness depends on component interaction; and
+- a small number of representative end-to-end tests when assembled workflows expose meaningful risks not adequately covered at narrower boundaries.
+
+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. 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. Size test helpers and fixture frameworks to the maintenance benefit they provide.
+
+## Coverage
+
+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.
+
+## 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.
+
+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
+
+Delete or rewrite tests when maintenance cost exceeds their continuing
+protective value.
+
+Strong candidates include tests that:
+
+- require updates after harmless internal changes;
+- assert incidental private constants or snapshot large amounts of incidental output;
+- verify mock choreography rather than outcomes;
+- 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. Consolidate them into one durable behavior-level or invariant test.
+
+## Reviewing a proposed 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. Which requested behavior or established contract does it protect, and what realistic defect would violate it?
+2. How likely and consequential is that defect, and is it already protected elsewhere?
+3. What is the narrowest stable boundary that can test it clearly?
+4. Would a correct internal refactor or a change to an incidental default require test edits?
+5. Does its confidence justify its maintenance, execution, and diagnostic cost, or would a smaller test suffice?
+
+## Definition of sufficient
+
+A test suite is sufficient when:
+
+- important requested behavior and established contracts are protected against realistic, consequential failures;
+- boundaries and component interactions have coverage where they introduce meaningful risks not protected elsewhere;
+- failures provide useful, distinct signals;
+- tests usually remain stable through legitimate internal changes; and
+- additional tests would mostly repeat existing protection or preserve inconsequential implementation details.
+
+Reassess sufficiency as the application, its users, and the consequences of
+failure evolve.

docs/release-checklist.md

@@ -1,128 +0,0 @@
-# Audita Release Checklist
-
-Use this checklist before cutting a pre-1.0 or 1.0 release candidate.
-
-## Core test pass
-
-- Run:
-  - `go test ./...`
-- Confirm tests pass without live LLM credentials and without Python dependencies.
-
-## Config validation and precedence
-
-- Validate a representative config:
-  - `audita config validate --config <path>`
-- Inspect redacted effective config:
-  - `audita config print-effective --config <path>`
-- Confirm precedence behavior:
-  - defaults -> file config -> environment -> CLI.
-- Confirm default config search order:
-  - `/usr/local/etc/audita/config.yml` first, then `/etc/audita/config.yml`.
-- Confirm missing both default-path config files is non-fatal when `--config`/`AUDITA_CONFIG` are unset.
-
-## Output schema checks
-
-- Verify default output schema remains `bare-segments`.
-- Verify `--output-schema audita-v1` emits object payload with `schema` and `version`.
-- Verify unknown schema (for example `seriatim-intermediate`) fails clearly.
-
-## Subprocess contract checks
-
-- With `--output`, verify stdout is empty on success.
-- Without `--output`, verify stdout contains transcript JSON only.
-- Verify `--report-json` writes file output and does not write report JSON to stdout.
-- Verify failure stderr remains human-readable and includes diagnostics path when available.
-- Verify nonzero exit on failures.
-
-## Structured LLM checks
-
-- Verify runtime uses the Audita-owned OpenAI-compatible adapter.
-- Verify structured response schemas are attached via `response_format.type=json_schema`.
-- Verify diagnostics metadata includes structured schema `id/version/name/sha256`.
-- Verify provider output is still locally decoded/validated before use.
-- Verify malformed module-stage structured payloads degrade to warnings/rejections instead of failing the run.
-
-## Report and diagnostics schema checks
-
-- Verify report metadata fields:
-  - `report_schema_name`
-  - `report_schema_version`
-  - `output_schema`
-  - `config_version` when file config is used.
-- Verify diagnostics artifact references exist in reports:
-  - transcript/normalization/chunking/invocation/effective-config artifacts
-  - utilization diagnostics artifact
-  - correction ledger artifact
-  - error log on failures.
-
-## Redaction checks
-
-- Verify secrets are redacted from:
-  - `effective-config.json`
-  - run-dir and `--report-json` reports
-  - LLM request/response/error diagnostics payloads.
-- Verify no API keys/bearer tokens leak into fixtures or outputs.
-
-## Prompt and validator metadata checks
-
-- Verify prompt metadata appears in LLM request metadata diagnostics:
-  - `prompt_id`, `prompt_version`, `prompt_source`, `embedded_path`, `sha256`.
-- Verify stable validator keys appear in report decisions/rejections.
-- Verify module warning records appear in reports for malformed proposal-generation payloads and malformed validator batches.
-- Verify built-in validator chains resolve and execute for default and explicit module runs.
-
-## Utilization diagnostics checks
-
-- Verify `utilization-diagnostics.json` exists on successful runs.
-- Verify partial utilization artifact behavior on controlled failure paths.
-- Verify utilization fields are structurally present and nonnegative:
-  - effective concurrency
-  - run timing
-  - module timing summaries
-  - per-validator timing summaries.
-
-## Correction ledger checks
-
-- Verify `correction-ledger.json` exists on successful runs.
-- Verify report references ledger artifact path.
-- Verify ledger dispositions include applied/rejected and skipped/failed where exercised.
-- Verify validator rejection and proposal-application skip remain distinct.
-
-## Pipeline behavior checks
-
-- Verify default full pipeline run remains:
-  - `glossary`, `homophones`, `glossary`, `spoken_word`, `grammar`
-  - with deterministic repeated instance naming (`glossary_1`, `glossary_2`).
-- Verify explicit module runs (`--modules`) still work.
-
-## Failure and cancellation checks
-
-- Verify controlled failure paths retain diagnostics and produce best-effort failure reports.
-- Verify malformed proposal-generation payloads keep exit code `0`, keep stderr empty on success, and record warnings in reports/diagnostics.
-- Verify malformed validator payloads reject only the affected batch and do not fail the module.
-- Verify timeout/cancellation paths exit nonzero, do not hang, and retain failure diagnostics when initialized.
-
-## Release fixture/idempotence checks
-
-- Run release fixtures (`internal/cli/testdata/release`) through `go test ./...`.
-- Confirm fixture checks cover:
-  - must-apply and must-not-apply expectations
-  - protected-term survival
-  - report and diagnostics contracts
-  - output-schema checks
-  - prompt/schema metadata diagnostics
-  - utilization/ledger artifacts
-  - idempotence-oriented second pass no-op behavior with deterministic fake responses.
-
-## Deferred-feature guardrail
-
-- Confirm release docs do not claim support for deferred items:
-  - filesystem prompt overrides
-  - user-configurable validator chains
-  - arbitrary user-supplied output schemas
-  - resume/start-at/stop-after execution
-  - diff/check/propose-only modes
-  - generated transcript descriptions enabled by default
-  - interactive review UI
-  - UI/server wrapper
-  - provider benchmarking harness.

docs/release.md

@@ -0,0 +1,157 @@
+# Releasing Audita
+
+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 and Git. 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.
+
+The source-build minimum is Go 1.26.0, declared in [go.mod](../go.mod).
+This minimum is required by the selected ReleaseKit dependency.
+Distributed executables do not require a Go installation. The selected release
+toolchain is Go 1.26.8, 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
+export PATH="/path/to/go1.26.8/bin:$PATH"
+export GOTOOLCHAIN=local
+go version
+```
+
+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.
+
+Prepare dependencies before offline candidate validation:
+
+```sh
+GOWORK=off GOTOOLCHAIN=local go mod download
+```
+
+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 and invokes `go tool releasekit` 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.
+
+## Prepare and publish the candidate
+
+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 `go test -mod=readonly -count=1 ./...` once with module and
+toolchain network access disabled, 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`
+
+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 builds its CLI using
+an alternate `-modfile`. The bootstrap executable and temporary files remain
+outside the tagged source. The workflow runs with the selected Go 1.26.8 image,
+`GOWORK=off`, and `GOTOOLCHAIN=local`.
+
+Delivery uses prepared-checkout mode to verify the existing tag, HEAD, and clean
+worktree without repeating the bootstrap's fetch and checkout.
+
+The resulting executable receives:
+
+```sh
+"$${bootstrap_dir}/releasekit" ci-deliver \
+  --repo "$${CI_WORKSPACE}" \
+  --prepared \
+  --commit "$${expected_commit}" \
+  "$${CI_COMMIT_TAG}"
+```
+
+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.
+
+ReleaseKit handles content-aware retries and retained-artifact recovery. See
+the pinned [publication recovery guide](https://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.4.1/docs/consumers/publish.md)
+and [delivery guide](https://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.4.1/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.
+
+## Failure and recovery
+
+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://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.4.1/docs/consumers/publish.md)
+for object-level recovery details.
+
+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://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.4.1/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

@@ -0,0 +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-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/v1.1.0.md

@@ -0,0 +1,22 @@
+# Audita v1.1.0
+
+This release refreshes Audita's documentation and repository policies and adds a
+small, automated release workflow. Transcript-processing behavior, CLI syntax,
+configuration, and serialized output formats are unchanged from v1.0.0.
+
+- Consolidated CLI, configuration, operations, and integration references, including
+  a dedicated reference for output files and reports.
+- Added contributor navigation and agent, testing, and release policies; retired
+  speculative troubleshooting documentation and the completed migration roadmap.
+- Added local release validation and publication scripts, with publication complete
+  after the source and version tag are pushed. CI delivers binaries asynchronously.
+- Isolated CLI tests from host configuration for a reliable local test baseline.
+
+Release binaries are now provided only for Linux amd64 and Linux arm64. Windows
+and Intel macOS are no longer supported. macOS arm64 remains a best-effort local
+build/development environment; macOS binaries are no longer published.
+
+Linux users need no configuration or data migration. Users of previously published
+Windows or macOS binaries should account for the distribution changes above before
+upgrading. See the [release procedure](../release.md) for artifact delivery and the
+[contributor guide](../development.md) for local build instructions.

docs/releases/v2.0.0.md

@@ -0,0 +1,38 @@
+# Audita v2.0.0
+
+Audita v2 adopts ConfigKit for configuration and PromptKit for LLM execution,
+adds resilient processing and focused reports, and improves correction prompts
+and validation. This is an intentional breaking release; existing installations
+must migrate their configuration and invocation settings.
+
+- Configuration uses `version: 2` YAML, named backends, PromptKit model profiles,
+  and optional named overlays. Offline configuration validation and inspection
+  expose effective settings, selected profiles, and provenance.
+- Proposal and validation calls share per-backend capacity. PromptKit handles
+  transport retries and structural response repair within bounded operation
+  timeouts.
+- Transcript chunks remain fixed through the LLM stages. Recoverable model
+  failures preserve progress and allow other work to continue. If every LLM
+  operation fails recoverably, processing still produces the deterministically
+  normalized transcript without LLM corrections. Cancellation, application
+  failures, and required output failures remain fatal.
+- Ordinary output includes `errors.yml`, `recoveries.yml`, and `report.md`, plus
+  a brief completion summary. Detailed correction and LLM diagnostics are opt-in
+  with `--debug`; `--reporting=false` suppresses all three ordinary reports.
+- Empty replacement text supports validated span deletion while preserving a
+  nonblank segment. Validator responses retain usable decisions despite missing,
+  duplicate, or extraneous entries; unavailable decisions never approve an edit.
+- Prompts use short request-local references, consistent shared instructions,
+  and relevant neighboring/glossary context for validation. Spoken-word cleanup
+  can reduce accidental protected-name repetition subject to validation.
+
+Follow the [v2 migration guide](../migrations/v2.md) before upgrading. Version-1
+configuration, implicit environment-setting overlays, retired model/credential/
+concurrency flags, and the former JSON report interface have no compatibility
+shim. Start from the maintained examples linked in that guide, configure profiles
+and credential references, and validate the new configuration. Update report and
+debug consumers for the [current output contract](../integrations/output-files.md).
+
+Linux amd64 and arm64 remain the production targets; macOS arm64 is best effort
+for development. Binary and checksum delivery runs asynchronously after source/tag
+publication, as described in the [release procedure](../release.md).

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](../../examples/profiles/local/) and
+   [service](../../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 [configuration reference](../config.md#promptkit-profiles-and-operator-prompts)
+contains the migrated format and presence rules. Start from the maintained
+[local](../../examples/minimal-config.yml),
+[service](../../examples/production-config.yml), or
+[application inheritance](../../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/audit.md

@@ -1,791 +0,0 @@
-# Pre-1.0 Code Quality and Deduplication Audit
-
-## 1. Executive summary
-
-Audita is in good shape for a limited pre-1.0 cleanup pass. The repository is small, package boundaries are mostly explicit, and the core public contract is already documented around `audita process`, config loading, output schemas, diagnostics, reports, embedded prompts, modules, and validators. The highest-value improvements are targeted centralization, not a rewrite.
-
-Top three refactoring targets before 1.0:
-
-1. Centralize module proposal plumbing and prompt payload construction across the four production modules.
-2. Centralize effective config loading plus schema/module catalog validation so `process`, `config print-effective`, and `config validate` cannot drift.
-3. Centralize diagnostics artifact names, stage names, and validator classification metadata used by reports and the correction ledger.
-
-No major architectural risk is apparent. The main pre-1.0 risk is public-behavior drift from repeated policy strings, catalog values, artifact paths, and nearly identical command/module scaffolding.
-
-This report was written to `docs/roadmap/audit.md`. `docs/roadmap/` already exists in the repository, although its previous `publish.md` file is currently deleted in the worktree by an unrelated change.
-
-## 2. Repository map reviewed
-
-Reviewed documentation:
-
-- `README.md`
-- `docs/configuration.md`
-- `docs/architecture/architecture.md`
-- `docs/architecture/public-contract.md`
-- `docs/architecture/diagnostics.md`
-- `docs/architecture/output-schemas.md`
-- `docs/architecture/prompts.md`
-- `docs/architecture/validators.md`
-- `docs/architecture/structured-llm.md`
-- `docs/integration/subprocess-operations.md`
-- `docs/release-checklist.md`
-
-Reviewed implementation areas:
-
-- `cmd/audita`
-- `internal/cli`
-- `internal/core/config`
-- `internal/core/schema`
-- `internal/core/io`
-- `internal/core/normalization`
-- `internal/core/chunking`
-- `internal/core/diagnostics`
-- `internal/core/outputschema`
-- `internal/core/reporting`
-- `internal/framework/contracts`
-- `internal/framework/modules`
-- `internal/framework/proposal_generation`
-- `internal/framework/proposals`
-- `internal/framework/runner`
-- `internal/framework/validators`
-- `internal/framework/llm`
-- `internal/framework/responseschema`
-- `internal/framework/promptcontext`
-- `internal/framework/warnings`
-- `internal/modules/glossary`
-- `internal/modules/homophones`
-- `internal/modules/spoken_word`
-- `internal/modules/grammar`
-- `internal/prompts`
-- `internal/validators`
-- package tests and CLI parity/release fixtures under `internal/cli/testdata`
-
-Major execution paths reviewed:
-
-- `audita process <transcript.json> --glossary <glossary.yaml>`
-- `audita config validate --config <path>`
-- `audita config print-effective [--config <path>]`
-- default module sequence resolution and repeated glossary instance naming
-- proposal generation, validator execution, proposal application, report writing, diagnostics writing, and retention
-
-Important absent or not-applicable areas:
-
-- No `pkg/` directory exists.
-- No `examples/` directory exists.
-- No `docs/internal/` directory exists.
-- No `internal/app`, `internal/stage`, `internal/storage`, `internal/artifacts`, or `internal/manifest` packages exist. Their closest equivalents are `internal/cli`, `internal/framework/runner`, `internal/core/diagnostics`, and `internal/core/reporting`.
-
-## 3. High-confidence deduplication opportunities
-
-### 3.1 Module proposal plumbing is duplicated across all production modules
-
-Affected files/packages:
-
-- `internal/modules/glossary/module.go`
-- `internal/modules/homophones/module.go`
-- `internal/modules/spoken_word/module.go`
-- `internal/modules/grammar/module.go`
-- `internal/modules/*/prompt.go`
-- `internal/framework/proposal_generation`
-- `internal/framework/promptcontext`
-
-Duplicated or near-duplicated behavior:
-
-- Each module has the same `Module` struct shape, `Validators` copy behavior, `Propose` flow, section transcript extraction, transcript description extraction, `proposal_generation.GenerateCandidates` request construction, prompt metadata map construction, and stage-name formatting.
-- Each module also has a near-identical prompt payload builder with local `promptSegment` and `promptTranscriptSection` types, glossary JSON marshaling, transcript section JSON marshaling, transcript description block rendering, and two-message return shape.
-- `collectSectionProposals` already passes a section transcript to each module, but each module then filters that transcript again by section metadata.
-
-Why it matters:
-
-- A diagnostics or prompt-context bug fix would need to be repeated in four modules.
-- Prompt metadata fields and stage names are diagnostics-visible and could drift by module.
-- The double section filtering is currently harmless, but it obscures the runner/module contract.
-
-Recommended refactor:
-
-- Add a small shared helper for module proposal execution, likely in `internal/framework/proposal_generation` or a narrow `internal/modules/modulekit` package.
-- Keep domain-specific prompt IDs and prompt text local to each module.
-- Move transcript section prompt payload construction into a shared prompt-context helper, for example `promptcontext.MarshalTranscriptSection`.
-- Provide one helper for prompt metadata maps instead of manually expanding `prompt_id`, `prompt_version`, `prompt_source`, `embedded_path`, and `sha256` in every module.
-- Preserve current module `Key`, replacement policy, and validator chain ownership.
-
-Suggested tests:
-
-- Keep one golden or table-driven prompt payload test per module for domain-specific wording.
-- Add shared tests for transcript section JSON shape, empty transcript handling, categories copy behavior, and prompt metadata fields.
-- Add a parity test that all four module `Propose` methods still write diagnostics under the same module instance directory and produce the same correction mapping.
-
-Risk level:
-
-- Low to medium. The behavior is highly duplicated, but prompt and diagnostics behavior is sensitive. Refactor behind existing module tests and CLI parity fixtures.
-
-### 3.2 Effective config loading is repeated between commands
-
-Affected files/packages:
-
-- `internal/cli/run.go`
-- `internal/core/config`
-
-Duplicated or near-duplicated behavior:
-
-- `runProcess` and `runConfigPrintEffective` both resolve config path, start from defaults, optionally load/apply file config, then apply environment overrides.
-- `runConfigValidate` separately loads a file, applies it to defaults, and validates it.
-- Path source metadata is computed in `internal/cli`, not `internal/core/config`, even though the precedence contract is documented as config behavior.
-
-Why it matters:
-
-- Config precedence is part of the public contract. If a future setting is added, three command paths may need coordinated updates.
-- `config print-effective` is the user-visible diagnostic for effective config. It should use the same loader as `process`, except for intentionally omitted CLI overrides.
-- The current code is understandable, but the behavior is repeated in a way that makes drift likely as config grows.
-
-Recommended refactor:
-
-- Add a narrow effective-config loader in `internal/core/config`, returning `Config`, source path, source type, and version metadata.
-- Keep command-specific CLI flag parsing in `internal/cli`.
-- Model the intentional differences explicitly:
-  - `process`: defaults + file + env + CLI overrides
-  - `config print-effective`: defaults + file + env
-  - `config validate`: file schema + default-backed config validation, no env
-- Move `resolveConfigPath` or an equivalent path resolver into `internal/core/config`.
-
-Suggested tests:
-
-- One table-driven config loader test covering explicit `--config`, `AUDITA_CONFIG`, default search paths, missing explicit paths, and missing default paths.
-- CLI tests asserting `process` and `print-effective` share file+env behavior.
-- A regression test that `config validate` remains file-only and does not read environment overrides.
-
-Risk level:
-
-- Low. Behavior is already explicit and well tested; the refactor can be done by moving code without changing precedence.
-
-### 3.3 Module catalog validation is split across config, contracts, and module factory
-
-Affected files/packages:
-
-- `internal/core/config/validation.go`
-- `internal/framework/contracts/contracts.go`
-- `internal/framework/modules/registry.go`
-- `internal/validators/chains.go`
-- `internal/framework/validators/models.go`
-
-Duplicated or near-duplicated behavior:
-
-- Module keys appear in multiple places:
-  - config default CSV: `glossary,homophones,glossary,spoken_word,grammar`
-  - module factory constants and known-key map
-  - built-in validator chains
-  - confidence threshold lookup
-  - individual module `Key()` methods
-- `Config.Validate` checks only that module names are non-empty. An unsupported configured module can pass `audita config validate` and fail later in `process` runner setup.
-- `contracts.ResolveModuleRunSpecs` only assigns instance names; it does not validate production module support.
-
-Why it matters:
-
-- `audita config validate` is documented as a CI/preflight command. Letting unsupported modules pass weakens that preflight.
-- Module key drift could affect thresholds, validator chains, reports, and unsupported-module errors.
-
-Recommended refactor:
-
-- Introduce a small canonical module catalog or key package that can be imported by config validation, module factory construction, validator chain resolution, and threshold lookup without creating a cycle.
-- Keep module construction in `internal/framework/modules`; the catalog should expose keys and validation only.
-- Make `Config.Validate` reject unknown built-in module keys through that catalog.
-- Keep repeated module instances valid.
-
-Suggested tests:
-
-- `internal/core/config` test: unknown `pipeline.modules` fails validation.
-- `internal/cli` test: `audita config validate --config` rejects an unsupported module before runtime.
-- Existing `internal/framework/modules` unknown-module tests should continue to pass.
-- Validator chain tests should assert every catalog module has a built-in chain.
-
-Risk level:
-
-- Medium. This tightens validation behavior. It is desirable before 1.0, but if unknown modules were intentionally allowed for future extension, document that explicitly instead.
-
-### 3.4 Output schema support is hardcoded in config validation and registry
-
-Affected files/packages:
-
-- `internal/core/config/validation.go`
-- `internal/core/outputschema/registry.go`
-- `docs/architecture/output-schemas.md`
-
-Duplicated or near-duplicated behavior:
-
-- `Config.Validate` hardcodes `bare-segments` and `audita-v1`.
-- `outputschema.Resolve` owns the actual output schema registry and returns the runtime error for unsupported schema names.
-
-Why it matters:
-
-- Adding or deferring a schema requires updating multiple places.
-- Public behavior could drift: a schema might validate in config but fail at output time, or vice versa.
-
-Recommended refactor:
-
-- Make `internal/core/outputschema` expose `IsSupported`, `SupportedKeys`, or a validation function.
-- Have config validation call that helper or consume shared constants.
-- Keep actual encoding logic in `outputschema`; config should not know encoder details.
-
-Suggested tests:
-
-- Config validation test for every output schema returned by the registry.
-- Output schema registry test that unsupported `seriatim-intermediate` still fails clearly until implemented.
-- CLI test that unsupported `--output-schema` fails before output write.
-
-Risk level:
-
-- Low. This is a straightforward catalog centralization.
-
-### 3.5 Diagnostics artifact names and report metadata paths are repeated
-
-Affected files/packages:
-
-- `internal/core/diagnostics/run_dir.go`
-- `internal/cli/run.go`
-- `internal/core/reporting/report.go`
-- docs under `docs/architecture` and `docs/integration`
-
-Duplicated or near-duplicated behavior:
-
-- Artifact filenames such as `source-transcript.json`, `source-transcript-parsed.json`, `normalized-transcript.json`, `normalization-summary.json`, `chunking-summary.json`, `utilization-diagnostics.json`, `correction-ledger.json`, `invocation.json`, `effective-config.json`, `report.json`, and `error.log` are repeated between run-directory writers and `buildProcessReport`.
-- `runProcess` writes `utilization-diagnostics.json` and `correction-ledger.json` by raw string on both success and failure paths.
-
-Why it matters:
-
-- These names are part of the documented diagnostics contract.
-- A filename change would need to be made in multiple places, and report metadata could point at files that are no longer written.
-
-Recommended refactor:
-
-- Define diagnostics artifact name constants in `internal/core/diagnostics`.
-- Add a helper that returns `reporting.DiagnosticsMetadata` for a run directory and status.
-- Add named methods for utilization diagnostics and correction ledger writes, or at least constants used by `WriteJSONArtifact`.
-
-Suggested tests:
-
-- Unit test that `diagnostics.MetadataForRunDirectory` matches files written by `RunDirectory`.
-- CLI success/failure tests should continue to assert report metadata paths and actual file existence.
-- Add a test for failure report metadata including `error.log`.
-
-Risk level:
-
-- Low. This is mostly string centralization, with high public-contract value.
-
-### 3.6 Validator execution class is duplicated and partially hardcoded
-
-Affected files/packages:
-
-- `internal/validators/registry.go`
-- `internal/validators/metadata/metadata.go`
-- `internal/validators/*/validator.go`
-- `internal/framework/runner/runner.go`
-- `internal/cli/review_artifacts.go`
-
-Duplicated or near-duplicated behavior:
-
-- Validator constructors wrap validators with execution class metadata.
-- `BuiltInValidatorDefinition` also has an `LLMBacked` field.
-- Runner uses `metadata.ClassOf` to order deterministic validators before LLM-backed validators.
-- Correction ledger classification uses a local hardcoded map of LLM-backed validator names.
-
-Why it matters:
-
-- Adding a new LLM-backed validator could be ordered correctly by runner metadata but appear in the wrong correction-ledger section.
-- Validator class is domain metadata, not report-building policy. It should have one source of truth.
-
-Recommended refactor:
-
-- Make validator classification resolvable by validator instance or stable key from a single metadata source.
-- Remove the unused or redundant `LLMBacked` field, or make it the canonical source used by constructors, runner ordering, and ledger formatting.
-- Replace the local ledger map with `metadata.ClassOf` when possible, or a registry lookup by stable key.
-
-Suggested tests:
-
-- Correction ledger test that LLM-backed decisions are classified from validator metadata, not a local string map.
-- Registry test that every registered LLM-backed validator reports the same class through every public metadata path.
-- Runner ordering test should remain in place.
-
-Risk level:
-
-- Low to medium. The implementation is small, but correction-ledger shape is diagnostics-visible.
-
-### 3.7 Malformed structured-output classification is duplicated
-
-Affected files/packages:
-
-- `internal/framework/proposal_generation/generate.go`
-- `internal/framework/validators/llm_validators.go`
-- `internal/framework/llm/openai_compatible_client.go`
-
-Duplicated or near-duplicated behavior:
-
-- Proposal generation and LLM validators both classify malformed structured-output errors by scanning error message substrings.
-- The marker lists are currently the same, but they are maintained independently.
-- The actual errors originate in the LLM adapter.
-
-Why it matters:
-
-- Proposal-generation malformed payloads become warnings with zero proposals, while validator malformed payloads reject affected batches with warnings. If classifiers drift, similar adapter failures could be downgraded in one workflow and hard-fail in another.
-
-Recommended refactor:
-
-- Prefer a typed error or exported classifier from `internal/framework/llm`.
-- If typed errors are too invasive, create one shared classifier function in a lower framework package used by both proposal generation and validators.
-- Preserve the different handling semantics at each call site.
-
-Suggested tests:
-
-- Shared classifier table for all adapter malformed-output errors.
-- Proposal-generation test and validator test should assert the same representative malformed adapter errors are downgraded.
-- Adapter tests should assert typed/classified errors wrap useful context and still redact secrets.
-
-Risk level:
-
-- Medium. Error typing can accidentally affect retry and wrapping behavior; do this with focused tests.
-
-## 4. Medium-confidence opportunities
-
-### 4.1 CLI flag registration and override extraction are large and repetitive
-
-Affected files/packages:
-
-- `internal/cli/run.go`
-- `internal/core/config/flags.go`
-
-Duplicated or near-duplicated behavior:
-
-- Each process flag has a field in `processFlags`, a registration entry in `newProcessFlagSet`, a case in `fs.Visit`, and an assignment in `config.ApplyCLIOverrides`.
-- File config and environment config also set many of the same effective config fields.
-
-Why it matters:
-
-- Adding a new config option requires multiple edits. Missing one edit could create a flag that displays but does not override, or a config field with no CLI override.
-
-Recommended refactor:
-
-- Avoid a generic reflection-heavy flag system before 1.0.
-- Consider a small metadata table only for simple scalar flags, or a focused helper that maps visited flags to `CLIOverrides`.
-- Keep nontrivial semantics, such as legacy concurrency alias precedence, explicit in code.
-
-Suggested tests:
-
-- CLI override parity test for every stable flag that mutates config.
-- A test that default flag values reflect file+env effective config before CLI overrides.
-
-Risk level:
-
-- Medium. A broad flag abstraction would be riskier than the current duplication. Do only a small helper if it clearly reduces missed updates.
-
-### 4.2 Config source application repeats field-level assignments
-
-Affected files/packages:
-
-- `internal/core/config/file_config.go`
-- `internal/core/config/env.go`
-- `internal/core/config/flags.go`
-
-Duplicated or near-duplicated behavior:
-
-- The same effective fields are assigned from file config, env vars, and CLI overrides.
-- Some semantics differ intentionally: file config supports `api_key_env`, env supports `OPENROUTER_API_KEY` fallback, CLI uses direct values.
-
-Why it matters:
-
-- Field additions are easy to miss in one source.
-- Error messages and trimming behavior can drift.
-
-Recommended refactor:
-
-- Do not force all config sources through one generic mapper.
-- Add small setter helpers for repeated config subdomains such as LLM target, concurrency, thresholds, normalization, and diagnostics.
-- Keep source-specific parsing and error labels local.
-
-Suggested tests:
-
-- Cross-source table proving file, env, and CLI all reach the same effective fields where they are meant to.
-- Tests for intentional differences: API key env resolution, `OPENROUTER_API_KEY` fallback, CLI direct API key, and transcript description trimming.
-
-Risk level:
-
-- Medium. Useful, but only after the effective loader and catalog cleanup.
-
-### 4.3 Prompt metadata and response schema metadata map construction repeats
-
-Affected files/packages:
-
-- `internal/modules/*/module.go`
-- `internal/framework/proposal_generation/generate.go`
-- `internal/framework/validators/llm_validators.go`
-- `internal/prompts`
-- `internal/framework/responseschema`
-
-Duplicated or near-duplicated behavior:
-
-- Prompt metadata maps are manually expanded in module proposal generation and validator diagnostics.
-- Response schema metadata maps are built independently in proposal generation and validator diagnostics.
-
-Why it matters:
-
-- Metadata fields are diagnostics-visible and useful for reproducibility.
-- Adding a metadata field requires updating multiple call sites.
-
-Recommended refactor:
-
-- Add `Metadata.Map()` or a typed diagnostics metadata struct in `internal/prompts`.
-- Add `responseschema.Metadata()` or a method returning a stable diagnostics shape.
-- Prefer typed structs over `map[string]any` where possible.
-
-Suggested tests:
-
-- Prompt metadata rendering test should assert all registered prompts expose stable metadata.
-- Proposal and validator diagnostics tests should assert the shared metadata helper is used.
-
-Risk level:
-
-- Low.
-
-### 4.4 Secret redaction logic is split across config, LLM diagnostics, and adapter errors
-
-Affected files/packages:
-
-- `internal/core/config/redaction.go`
-- `internal/framework/llm/diagnostics.go`
-- `internal/framework/llm/client_common.go`
-- `internal/framework/proposal_generation/generate.go`
-- `internal/framework/runner/runner.go`
-
-Duplicated or near-duplicated behavior:
-
-- Config redaction replaces non-empty API keys with `[REDACTED]`.
-- LLM diagnostics replace configured secret values and `Bearer <secret>`.
-- Adapter error sanitization separately replaces secrets and bearer values.
-- Proposal and validator paths separately assemble secret lists.
-
-Why it matters:
-
-- Secret redaction is a public guarantee.
-- New secret-bearing config fields could be missed in one path.
-
-Recommended refactor:
-
-- Add a small redaction helper package or keep it in `internal/framework/llm` only if it remains LLM-specific.
-- Centralize `[]string` secret extraction from `config.Config`.
-- Keep config structural redaction separate from byte/string payload redaction, but share the redaction token and value replacement behavior.
-
-Suggested tests:
-
-- One test that a proposal-generation error, validator diagnostic artifact, effective config artifact, and surfaced provider error all redact the same configured secrets.
-- Existing subprocess no-secret-leak test should remain as an end-to-end guard.
-
-Risk level:
-
-- Medium. The current coverage appears strong; change carefully.
-
-### 4.5 Test fakes and fixture helpers are duplicated across packages
-
-Affected files/packages:
-
-- `internal/modules/*/module_test.go`
-- `internal/framework/proposal_generation/generate_test.go`
-- `internal/framework/validators/llm_validators_test.go`
-- `internal/cli/run_test.go`
-- `cmd/audita/main_integration_test.go`
-- `internal/cli/release_fixtures_test.go`
-- `internal/cli/parity_test.go`
-
-Duplicated or near-duplicated behavior:
-
-- Several packages define fake structured LLM clients, fixture path helpers, read/write helpers, diagnostics glob assertions, and run-directory helpers.
-- The four module test files have particularly similar fake clients and proposal-diagnostics assertions.
-
-Why it matters:
-
-- Refactors in LLM or diagnostics behavior require updating many tests.
-- Some duplicated tests are valuable because they preserve per-module public behavior; the issue is helper duplication, not coverage volume.
-
-Recommended refactor:
-
-- Add package-local helper files where duplication is within a package.
-- For cross-package fakes, prefer a small internal test support package only if it does not create import cycles or hide test intent.
-- Keep module-specific assertions local.
-
-Suggested tests:
-
-- This is test infrastructure cleanup. Existing tests should remain semantically equivalent.
-- Add helper tests only if helpers contain nontrivial behavior, such as fake response sequencing.
-
-Risk level:
-
-- Low.
-
-### 4.6 Stage-name construction is inconsistent enough to centralize, but not enough to redesign
-
-Affected files/packages:
-
-- `internal/modules/*/module.go`
-- `internal/framework/proposal_generation/generate.go`
-- `internal/framework/validators/llm_validators.go`
-- `internal/framework/runner/observability.go`
-
-Duplicated or near-duplicated behavior:
-
-- Modules pass stage names like `<module_instance>:proposal:section-0001`.
-- `proposal_generation` has a default builder using `<module_instance>:proposal-generation:section-0001`, but production modules bypass it.
-- Validators build `<module_instance>:<validator>:batch-0001`.
-- Utilization extracts module instance by splitting stage names on `:`.
-
-Why it matters:
-
-- Stage names affect diagnostics filenames and observability grouping.
-- Current behavior works, but the naming grammar is implicit.
-
-Recommended refactor:
-
-- Add narrow helpers for proposal and validator stage names.
-- Preserve current production stage names unless there is a deliberate pre-1.0 diagnostics compatibility decision.
-- Keep filename sanitization in `internal/framework/llm`.
-
-Suggested tests:
-
-- Unit tests for stage-name helper output.
-- Utilization test that module instance extraction still works for proposal and validator stage names.
-
-Risk level:
-
-- Medium. Renaming stages can change diagnostics filenames, so avoid unnecessary churn.
-
-## 5. Boundary and responsibility concerns
-
-### CLI owns too much report and diagnostics metadata assembly
-
-`internal/cli/run.go` is doing orchestration, command parsing, config loading, output routing, report assembly, diagnostics metadata path assembly, and correction-ledger construction. This is acceptable for a small CLI, but two pieces are drifting beyond command responsibility:
-
-- diagnostics artifact path metadata belongs closer to `internal/core/diagnostics`;
-- report assembly and correction-ledger mapping belong closer to `internal/core/reporting` or a narrow reporting adapter package.
-
-Recommended home:
-
-- `internal/core/diagnostics`: artifact constants and diagnostics metadata path construction.
-- `internal/core/reporting`: pure mapping from runner/config/diagnostics state into report payloads.
-- `internal/cli`: command parsing, invocation wiring, exit codes, stdout/stderr behavior.
-
-### Config validation lacks catalog ownership
-
-`internal/core/config` currently validates only generic module list shape and hardcodes output schema keys. Because modules and output schemas are public contract values, config validation should use a catalog owned by the relevant domain.
-
-Recommended home:
-
-- output schema validation: `internal/core/outputschema`;
-- module key validation: a small catalog package or lower-level constants package importable by config, module factory, validator chains, and threshold lookup.
-
-### Runner owns adapter shims between contracts and validator framework
-
-`internal/framework/runner` contains `validationLLMClientAdapter` and `llmDiagnosticsWriterAdapter`. This is not a serious problem today because runner wires proposal and validation workflows. If these adapters grow, move them to `internal/framework/validators` or a small integration package so runner remains focused on orchestration.
-
-### LLM malformed-output policy is spread across callers
-
-The LLM adapter emits the errors, while proposal generation and validators classify them by message text. The policy decision is caller-specific, but the classification should live with the LLM/framework error type.
-
-## 6. Path, key, and naming construction review
-
-Centralized enough:
-
-- LLM diagnostics artifact suffixes and stage sanitization are centralized in `internal/framework/llm/diagnostics.go`.
-- Output file writing is routed through `internal/core/io.WriteFile`.
-- Run directories are created in `internal/core/diagnostics.NewRunDirectory`.
-
-Needs cleanup:
-
-- Core diagnostics artifact names are repeated between `RunDirectory` writer methods and `buildProcessReport`.
-- `utilization-diagnostics.json` and `correction-ledger.json` are raw strings in both success and failure paths.
-- Proposal and validator diagnostics subdirectory construction repeats `filepath.Join(diagnosticsDir, moduleInstance)`.
-- Proposal and validator stage names are manually formatted in multiple packages.
-- Module keys are repeated across config defaults, module factory, validator chains, confidence threshold lookup, and module implementations.
-- Output schema names are repeated between config validation and `outputschema`.
-
-Recommendation:
-
-- Start with artifact constants and metadata helpers because that is the lowest-risk path/key cleanup.
-- Then centralize stage-name helpers without changing current production naming.
-- Defer any broader "path manager" abstraction.
-
-## 7. Resolution and catalog review
-
-Modules:
-
-- Runtime module construction has a production registry in `internal/framework/modules`.
-- Instance naming for repeated modules is centralized in `contracts.ResolveModuleRunSpecs`.
-- Unknown module failure exists in the factory, but config validation does not catch unknown modules.
-- Built-in validator chain resolution separately maps module key to validator keys.
-
-Output schemas:
-
-- Encoding is centralized in `internal/core/outputschema`.
-- Validation is duplicated in config.
-
-Prompts:
-
-- Prompt asset lookup and metadata are centralized in `internal/prompts`.
-- Prompt metadata map construction is repeated at call sites.
-- Prompt source selection is intentionally built-in only and should remain that way for 1.0.
-
-Validators:
-
-- Validator construction is package-owned under `internal/validators`.
-- Chains are centralized in `internal/validators/chains.go`.
-- Execution class metadata exists, but reporting/correction-ledger classification does not fully use it.
-
-Schemas:
-
-- Transcript and glossary parsing/validation are centralized in `internal/core/schema`.
-- Structured LLM response schemas are centralized in `internal/framework/responseschema`.
-- Output schema registry and response schema registry are appropriately separate.
-
-Recommendation:
-
-- Introduce only small catalog helpers for module keys, output schema keys, prompt metadata maps, response schema metadata maps, and validator execution class.
-- Avoid user-configurable modules, validators, prompts, or schemas before 1.0 unless already planned elsewhere.
-
-## 8. Config and command-loading review
-
-Consistent behavior:
-
-- The documented precedence for `process` is implemented: defaults, file config, environment, CLI.
-- `config print-effective` intentionally omits CLI process flags and uses defaults, file config, and environment.
-- `config validate` intentionally requires `--config` and does not require transcript/glossary inputs.
-- Missing explicit config paths are hard failures; missing default paths are non-fatal.
-- Environment parsing and CLI parsing both preserve legacy total-concurrency alias behavior.
-
-Likely accidental or high-risk differences:
-
-- Unsupported module names pass `Config.Validate` and `audita config validate`.
-- Output schema support is duplicated instead of delegated to the output schema registry.
-- Config path resolution lives in CLI even though it is part of config behavior.
-
-Intentional differences:
-
-- File config resolves `api_key_env`; env and CLI set direct API key values.
-- `OPENROUTER_API_KEY` is an environment fallback only for the primary LLM.
-- `transcript-description` has CLI/config support but no `AUDITA_*` environment variable, matching documentation.
-
-Recommendation:
-
-- Build a shared effective config context helper and keep source-specific parsing semantics explicit.
-- Tighten catalog validation before 1.0 if unknown modules are not meant to be accepted.
-
-## 9. State, manifest, or progress handling review
-
-Audita does not currently have a manifest/checkpoint/resume model. State is per-run diagnostics and report artifacts.
-
-Consistent behavior:
-
-- `process` creates one diagnostics run directory when diagnostics initialization succeeds.
-- Failures after run-dir creation write `error.log`, best-effort report artifacts, and retain diagnostics.
-- Success writes optional `--report-json`, run-dir `report.json`, utilization diagnostics, and correction ledger.
-- Retention is centralized in `diagnostics.ShouldRetainRunDirectory`.
-- There is no resume/retry/force behavior to preserve.
-
-Drift risks:
-
-- Success and failure paths both write utilization and correction-ledger artifacts with duplicated raw filenames.
-- Report diagnostics metadata is assembled independently from the run-directory writer methods.
-- Retention mode `never` currently still retains successful run directories in `ShouldRetainRunDirectory`, which may be intentional per tests or a naming/documentation mismatch. Do not change it in a dedup pass without first confirming semantics.
-
-Recommendation:
-
-- Centralize artifact names and report metadata path construction.
-- Keep retention behavior unchanged unless a separate bug review confirms the intended meaning of `never`.
-
-## 10. Refactors to avoid before 1.0
-
-- Do not introduce a generic workflow engine. The current sequential runner is clear and explicit.
-- Do not add a plugin architecture for modules, validators, prompts, or schemas before 1.0.
-- Do not redesign the CLI or replace `flag` with a larger framework only for deduplication.
-- Do not collapse all config source parsing into a reflection-based mapper; source semantics differ intentionally.
-- Do not merge module packages into one generic module type. Keep domain-specific prompt assets, keys, validator chains, and replacement policies visible.
-- Do not rewrite diagnostics or reporting schemas broadly. Centralize names and mapping helpers first.
-- Do not change diagnostics stage names casually; they affect artifact filenames and debugging workflows.
-- Do not consolidate deterministic and LLM validator behavior just because both return decisions. Their failure and batching semantics differ.
-- Do not generalize transcript/glossary schema parsing into a broad schema framework.
-- Do not reduce duplicated tests where the duplication protects distinct public command/module behavior.
-
-## 11. Recommended implementation sequence
-
-1. Centralize diagnostics artifact constants and diagnostics metadata path construction.
-2. Centralize output schema validation through `internal/core/outputschema`.
-3. Introduce a small module key catalog and use it in config validation, module factory, validator chains, and threshold lookup.
-4. Add an effective config loading context helper for defaults + file + env, then update `process` and `config print-effective`.
-5. Extract shared module proposal plumbing and prompt transcript-section payload construction.
-6. Centralize prompt metadata and response schema metadata map construction.
-7. Centralize validator execution-class lookup and update correction-ledger classification.
-8. Centralize malformed structured-output classification through a typed/shared LLM error helper.
-9. Add or consolidate focused test helpers for module LLM fakes, diagnostics assertions, and fixture paths.
-10. Do a final dead-code and legacy sweep for redundant helper fields such as unused validator definition metadata.
-
-Each item can be a separate commit with package-level tests and at least one CLI regression where public behavior is involved.
-
-## 12. Test strategy
-
-Tests to add before refactoring:
-
-- `internal/core/config`: unknown module key fails validation, if unsupported modules are not intended to be accepted.
-- `internal/core/config`: every output schema registry key validates through config.
-- `internal/core/diagnostics`: report metadata paths match run-directory artifact names.
-- `internal/validators`: validator class by key/instance is consistent for all registered validators.
-- `internal/framework/llm`: shared malformed structured-output classifier covers all current adapter malformed errors.
-
-Tests to add during refactoring:
-
-- `internal/framework/promptcontext`: transcript section prompt payload preserves IDs, speaker, timestamps, text, and categories.
-- `internal/framework/proposal_generation`: shared module proposal helper preserves current stage name, diagnostics dir, schema metadata, and malformed-output warning behavior.
-- `internal/cli`: `process` and `config print-effective` share defaults+file+env behavior.
-- `internal/cli`: `config validate` remains file-only and does not read env overrides.
-- `internal/cli`: correction ledger classifies deterministic and LLM validator decisions through canonical metadata.
-
-Existing tests to run after each cleanup:
-
-- `go test ./internal/core/config ./internal/core/outputschema`
-- `go test ./internal/core/diagnostics ./internal/core/reporting`
-- `go test ./internal/framework/proposal_generation ./internal/framework/validators ./internal/framework/runner`
-- `go test ./internal/validators/...`
-- `go test ./internal/modules/...`
-- `go test ./internal/cli ./cmd/audita`
-- Run `go test ./...` before merging a multi-package cleanup.
-
-Validation note:
-
-- During this report-only pass, no full test suite was run. A lightweight `go list ./...` completed package listing but emitted a sandbox warning while trying to write the Go module stat cache outside the repository.
-
-## 13. Appendix: findings not worth acting on
-
-### Separate module packages
-
-The four production module packages contain visible repetition, but keeping separate packages is useful. The module domains, prompt assets, validator chains, and tests are distinct enough that a single generic module package would hide important behavior.
-
-Do not refactor now beyond shared proposal/prompt plumbing.
-
-### Report type duplication between runner and reporting
-
-`runner.ModuleResult` and `reporting.ModuleReport` look similar. Keeping separate runtime and public report shapes is reasonable because runner owns execution state and reporting owns serialized public schema.
-
-Only centralize mapping helpers; do not merge the types.
-
-### Transcript and glossary parsing stay separate
-
-Transcript JSON and glossary YAML parsing have different formats, validation rules, and error messages. There is no useful shared parser abstraction to extract.
-
-### Response schema registry and output schema registry stay separate
-
-Structured LLM response schemas and transcript output schemas are both "schemas", but they serve different users and have different lifecycles. Do not combine their registries.
-
-### `flag` package usage
-
-The CLI command surface is small. Replacing `flag` with a larger CLI framework would not pay for itself before 1.0.
-
-### Local test duplication that protects public behavior
-
-Some test duplication in CLI, subprocess, parity, and release fixtures is intentional. These tests exercise different public surfaces and should remain explicit even if helpers are shared.
-
-### Filesystem state as diagnostics state
-
-Audita has no resume/checkpoint semantics. Treating diagnostics artifacts as filesystem outputs is currently acceptable. A manifest system would be speculative before there is a resume or audit workflow that needs it.

docs/roadmap/future.md

@@ -0,0 +1,96 @@
+# Deferred Feature Work
+
+**Last updated:** 2026-10-11
+
+**Status:** Deferred or exploratory work; not implemented or scheduled. These
+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 implemented [partial-success decision reconciliation](../internal/validators.md#llm-validator-batching)
+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.
+
+Consider bounded feedback and regeneration for model responses that satisfy the
+structural schema but leave requested decisions unavailable after reconciliation.
+The goal would be to recover more usable work before excluding affected
+candidates, when doing so materially improves outcomes.
+
+This capability is explicitly deferred. Current behavior retains PromptKit
+structural repair and per-candidate reconciliation; unavailable requested
+decisions produce errors while other candidates can succeed.
+
+Before implementation, define the Audita/PromptKit ownership boundary, which
+checks are eligible for feedback, how feedback identifies defects without exposing
+secrets, and how regeneration fits bounded budgets and operation deadlines. Reuse
+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.
+
+## Independent Whole-Pipeline Traversal by Chunk
+
+Explore allowing each fixed chunk to advance through its ordered stages without
+waiting for other chunks to finish the current stage. This could reduce waiting
+behind a slow chunk and improve utilization while preserving stage order within
+each chunk and deterministic final recombination.
+
+The resilience feature deliberately retains stage barriers: finish a stage across
+chunks before advancing to the next stage. Fixed boundaries alone do not authorize
+independent traversal.
+
+A future design must establish that stages do not depend on other chunks' evolving
+state, preserve stable identities and partial-success rules, and continue to share
+PromptKit's per-backend capacity across all roles and stages. Reporting must remain
+deterministic despite different completion orders, and fatal cancellation must
+still stop and join active work. Assess whether the scheduling change materially
+improves real workloads before introducing additional orchestration machinery.
+No new scheduler, global limiter, or execution mode is selected by this entry.
+
+## Whole-Segment Removal
+
+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 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
+establish whether whole-segment deletion is a meaningful unmet need. An empty
+replacement alone does not establish that intent: it can express ordinary filler
+or punctuation deletion within a larger segment. Assess how often genuinely
+expendable whole segments occur after deterministic normalization, the transcript
+quality benefit of removing them, and the risk of losing substantive speech.
+Compare those benefits with the implementation and ongoing maintenance costs.
+Retaining the segment and declining the edit is a valid outcome if the benefit is
+small or uncertain. No numerical adoption threshold is selected.
+
+Only if that evaluation supports proceeding should a separate feature design
+choose a representation, authorization and validation rules, and reporting
+semantics. It must address meaning preservation and the effects on segment
+identity, timestamps, fixed chunks, subsequent stages, recombination, and output
+consumers. Do not infer authorization to remove a segment from an empty string
+or introduce segment-removal machinery as part of span-deletion consistency.
+
+## Library Inspection and Configuration Comparison
+
+ConfigKit and PromptKit provide effective-configuration comparison; PromptKit
+also provides prompt/profile listings and contextual prompt requirement
+inspection. Exposing these capabilities in Audita is deferred until a concrete
+operator or development need arises. The dependency upgrade did not select new
+inspection commands.
+
+If a need emerges, define command ownership, selection syntax, report scope, and
+disclosure before implementation. Reuse the libraries' public APIs and consider
+shared CLI conventions alongside any separately selected CommandKit adoption.
+Requirement discovery is advisory evidence rather than proof of execution
+readiness; an empty configuration diff does not prove equivalent execution.
+The library-upgrade review remains available in
+[Git history](https://gitea.maximumdirect.net/eric/audita/src/commit/4c5536ab78c72dea58d03b3c51834138d429a59a/docs/roadmap/imports.md).

docs/roadmap/implementation.md

@@ -1,329 +0,0 @@
-# Pre-1.0 Deduplication Implementation Plan
-
-This plan turns `docs/roadmap/audit.md` into staged, prompt-sized cleanup work for an LLM coding agent. Each stage should be implemented in order and kept small enough to review as an independent commit.
-
-## Operating rules
-
-- Read `docs/roadmap/audit.md` before starting any stage.
-- Preserve public CLI, report, diagnostics, config precedence, prompt metadata, and output-schema behavior unless a stage explicitly calls out an intended behavior change.
-- Keep the four production module packages separate: `glossary`, `homophones`, `spoken_word`, and `grammar`.
-- Do not introduce plugin systems, generic workflow engines, broad CLI framework rewrites, reflection-heavy config mappers, or merged module packages.
-- Prefer narrow helpers, catalogs, constants, and pure mapping functions over broad abstractions.
-- Run the targeted tests listed in each stage before moving to the next stage.
-- Run `go test ./...` before declaring the full sequence complete.
-- Ignore unrelated worktree changes, including the existing deletion of `docs/roadmap/publish.md`, unless the user explicitly asks to handle them.
-- Do not reduce parity, release-fixture, subprocess, or module-specific behavior coverage while consolidating helpers.
-
-## Stages
-
-### Stage 1: Diagnostics artifact constants and metadata paths
-
-Goal:
-
-- Centralize diagnostics artifact names and report diagnostics metadata path construction without changing any filenames or report fields.
-
-Key edits:
-
-- Define constants in `internal/core/diagnostics` for:
-  - `source-transcript.json`
-  - `source-transcript-parsed.json`
-  - `normalized-transcript.json`
-  - `normalization-summary.json`
-  - `chunking-summary.json`
-  - `utilization-diagnostics.json`
-  - `correction-ledger.json`
-  - `invocation.json`
-  - `effective-config.json`
-  - `report.json`
-  - `error.log`
-- Add a diagnostics helper that builds `reporting.DiagnosticsMetadata` from a run directory path and failure/success status.
-- Update `RunDirectory` methods to use the constants.
-- Update CLI report assembly and utilization/correction-ledger writes to use the constants/helper instead of raw strings.
-
-Behavior changes:
-
-- None. All artifact names, report JSON keys, and path values must remain byte-for-byte compatible except for normal timestamp/order differences in existing outputs.
-
-Tests:
-
-- Add or update `internal/core/diagnostics` tests proving metadata helper paths match the artifact constants.
-- Run `go test ./internal/core/diagnostics ./internal/core/reporting ./internal/cli`.
-- Run any existing CLI report/diagnostics tests touched by this stage.
-
-Acceptance criteria:
-
-- No raw core diagnostics artifact filename strings remain in CLI report metadata assembly.
-- Existing success and failure reports still point to files that are actually written.
-- Retention behavior is unchanged.
-
-### Stage 2: Output schema validation and module catalog
-
-Goal:
-
-- Move public key validation to small canonical catalogs so config validation, runtime resolution, and factory behavior cannot drift.
-
-Key edits:
-
-- Add `SupportedKeys`, `IsSupported`, or an equivalent validation helper to `internal/core/outputschema`.
-- Update `config.Validate` to use `internal/core/outputschema` for output schema validation.
-- Add a small canonical module key catalog that is importable by:
-  - `internal/core/config`
-  - `internal/framework/modules`
-  - `internal/validators`
-  - `internal/framework/validators`
-- Use the module catalog for default module key constants, known-key checks, validator chain keys, and confidence-threshold lookup.
-- Keep module construction in `internal/framework/modules`; the catalog must not construct modules.
-
-Behavior changes:
-
-- Intended behavior change: unsupported configured module keys should fail during config validation, including `audita config validate`.
-- Repeated supported module keys remain valid.
-- Output schema behavior remains unchanged for `bare-segments`, `audita-v1`, and unsupported names.
-
-Tests:
-
-- Add `internal/core/config` tests for unsupported module keys and repeated supported module keys.
-- Add config validation tests that every supported output schema validates.
-- Add or update output schema registry tests for supported and unsupported schemas.
-- Update module registry and validator chain tests to use the shared catalog where appropriate.
-- Run `go test ./internal/core/config ./internal/core/outputschema ./internal/framework/modules ./internal/framework/validators ./internal/validators/... ./internal/cli`.
-
-Acceptance criteria:
-
-- Unknown modules fail before runner setup in config validation paths.
-- No duplicated hardcoded output schema support list remains in config validation.
-- No import cycle is introduced.
-
-### Stage 3: Effective config loading context
-
-Goal:
-
-- Centralize config path resolution and defaults+file+env loading while keeping command-specific CLI overrides explicit.
-
-Key edits:
-
-- Move config path resolution from `internal/cli` into `internal/core/config` or add an equivalent exported helper there.
-- Add an effective config loader that returns:
-  - effective `config.Config`
-  - config path
-  - config source (`flag`, `env`, `default`, or empty)
-  - config version pointer when a file was loaded
-- Use the shared loader in `audita process` before applying CLI overrides.
-- Use the shared loader in `audita config print-effective`.
-- Keep `audita config validate` as file-only: load file, apply to defaults, validate, and do not apply environment overrides.
-
-Behavior changes:
-
-- None. Preserve existing precedence:
-  - `process`: defaults, file config, environment, CLI flags
-  - `config print-effective`: defaults, file config, environment
-  - `config validate`: file config applied to defaults only
-- Preserve explicit config path failure behavior and missing default path non-fatal behavior.
-
-Tests:
-
-- Add table-driven config loader tests for:
-  - explicit `--config`
-  - `AUDITA_CONFIG`
-  - default search paths
-  - missing explicit path
-  - missing env path
-  - missing default paths
-- Add or update CLI tests proving `process` and `config print-effective` share file+env behavior.
-- Add or update CLI tests proving `config validate` ignores environment overrides.
-- Run `go test ./internal/core/config ./internal/cli ./cmd/audita`.
-
-Acceptance criteria:
-
-- Config precedence is unchanged.
-- Config source/path/version metadata in invocation and reports is unchanged.
-- Config command stdout/stderr and exit-code behavior is unchanged except for the intended unknown-module validation from Stage 2.
-
-### Stage 4: Prompt/schema metadata and stage-name helpers
-
-Goal:
-
-- Centralize diagnostics-visible metadata and stage-name construction without changing production diagnostics names.
-
-Key edits:
-
-- Add a helper or method in `internal/prompts` that returns the stable prompt metadata diagnostics shape currently expanded by call sites.
-- Add a helper or method in `internal/framework/responseschema` that returns the stable response schema metadata diagnostics shape currently expanded by call sites.
-- Add shared proposal and validator stage-name helpers in the lowest package that avoids import cycles.
-- Use the helpers in proposal generation, LLM validators, and production modules.
-
-Behavior changes:
-
-- None. Preserve current production stage names:
-  - module proposal stages keep their existing `proposal` naming form;
-  - validator batch stages keep their existing validator/batch naming form.
-- Preserve all prompt metadata and response schema metadata field names and values.
-
-Tests:
-
-- Add prompt metadata helper tests covering every registered prompt.
-- Add response schema metadata helper tests covering every registered response schema.
-- Add stage-name helper tests for no-section, section, and validator batch cases.
-- Run `go test ./internal/prompts ./internal/framework/responseschema ./internal/framework/proposal_generation ./internal/framework/validators ./internal/modules/...`.
-
-Acceptance criteria:
-
-- No manual prompt metadata map expansion remains in production module proposal plumbing.
-- No duplicated response schema metadata map construction remains in proposal generation and LLM validators.
-- Existing diagnostics fixture/path assertions still pass.
-
-### Stage 5: Shared module proposal and prompt payload plumbing
-
-Goal:
-
-- Remove duplicated proposal execution and transcript-section prompt payload construction while preserving module-specific domain behavior.
-
-Key edits:
-
-- Add a narrow shared proposal execution helper, preferably in `internal/framework/proposal_generation` unless import cycles require a small module helper package.
-- The helper should own:
-  - transcript description extraction from config;
-  - `GenerateCandidates` request construction;
-  - prompt metadata attachment;
-  - stage-name selection;
-  - conversion from generated corrections/warnings to `contracts.ProposalResult`.
-- Add shared transcript-section prompt payload construction in `internal/framework/promptcontext`.
-- Update each production module to provide only:
-  - module key;
-  - replacement policy;
-  - validator chain;
-  - prompt ID;
-  - domain-specific `BuildProposalMessages` call or message builder.
-- Remove each module's redundant section transcript filtering if the runner already passes section-limited transcripts.
-
-Behavior changes:
-
-- None. Preserve module keys, replacement policies, validator chains, prompt IDs, diagnostics directories, proposal indexes, warning behavior, and correction mapping.
-
-Tests:
-
-- Add promptcontext tests for transcript section payload shape, empty transcript handling, section index, and category copying.
-- Keep one module-specific prompt test per production module for domain wording and constraints.
-- Add or update module proposal tests proving diagnostics are still written under the same module instance directory.
-- Run `go test ./internal/framework/promptcontext ./internal/framework/proposal_generation ./internal/modules/... ./internal/cli`.
-
-Acceptance criteria:
-
-- Four production modules share proposal execution plumbing.
-- Module packages remain separate and readable.
-- CLI parity and release fixture behavior is unchanged.
-
-### Stage 6: Validator classification and malformed LLM output policy
-
-Goal:
-
-- Use one source of truth for validator execution class and one shared classifier for malformed structured-output errors.
-
-Key edits:
-
-- Make validator execution class resolvable by stable validator key and by validator instance.
-- Replace the correction-ledger hardcoded LLM-backed validator map with the canonical metadata source.
-- Remove redundant validator metadata fields only after all call sites use the canonical source.
-- Add a shared malformed structured-output classifier in `internal/framework/llm` or another low-level framework package.
-- Update proposal generation and LLM validators to use the shared classifier while preserving their different handling outcomes.
-
-Behavior changes:
-
-- None. Proposal-generation malformed payloads still downgrade to warnings with zero proposals for affected sections.
-- Validator malformed payloads still reject affected batches with warnings.
-- Correction-ledger deterministic vs LLM validator sections should be unchanged for current validators.
-
-Tests:
-
-- Add validator metadata tests proving every registered validator has the expected execution class by key and instance.
-- Add correction-ledger tests proving deterministic and LLM-backed decisions are classified through canonical metadata.
-- Add shared malformed-output classifier tests covering current adapter malformed-output messages.
-- Update proposal-generation and validator tests to assert representative malformed adapter errors are still downgraded.
-- Run `go test ./internal/validators/... ./internal/framework/validators ./internal/framework/proposal_generation ./internal/framework/llm ./internal/cli`.
-
-Acceptance criteria:
-
-- No local hardcoded LLM-backed validator map remains in correction-ledger construction.
-- Proposal-generation and validator malformed-output classifier lists cannot drift.
-- Existing runner validator ordering is unchanged.
-
-### Stage 7: Redaction and adapter workflow cleanup
-
-Goal:
-
-- Reduce duplicated secret extraction/redaction setup while preserving all no-secret-leak guarantees.
-
-Key edits:
-
-- Add a shared helper that extracts all configured LLM secret values from `config.Config`.
-- Use the helper in proposal-generation diagnostics and validator diagnostics setup.
-- Keep config structural redaction (`Config.Redacted`) separate from byte/string payload redaction.
-- Keep adapter error redaction behavior compatible with current surfaced errors.
-- Move runner adapter shims only if Stage 6 or this stage makes them materially larger; otherwise leave them in runner.
-
-Behavior changes:
-
-- None. Redaction token and no-secret-leak behavior remain unchanged.
-
-Tests:
-
-- Add or update tests proving proposal diagnostics, validator diagnostics, effective config artifacts, and surfaced adapter errors redact the same configured secrets.
-- Keep existing subprocess no-secret-leak tests.
-- Run `go test ./internal/core/config ./internal/framework/llm ./internal/framework/proposal_generation ./internal/framework/validators ./internal/cli ./cmd/audita`.
-
-Acceptance criteria:
-
-- Secret-list assembly is no longer duplicated between proposal and validator paths.
-- No plaintext configured API key appears in diagnostics, reports, stdout, or stderr in existing redaction tests.
-- No unrelated adapter behavior changes.
-
-### Stage 8: Test helper cleanup and dead-code sweep
-
-Goal:
-
-- Consolidate test-only duplication and remove dead/redundant code left by prior stages.
-
-Key edits:
-
-- Consolidate package-local fake LLM clients, fixture readers, diagnostics glob helpers, and run-directory helpers where duplication is clear.
-- Use cross-package test support only if it does not obscure test intent or introduce awkward imports.
-- Remove redundant metadata fields, constants, or helper functions made obsolete by earlier stages.
-- Keep module-specific prompt and behavior assertions local to each module package.
-
-Behavior changes:
-
-- None.
-
-Tests:
-
-- Run all package tests touched by helper cleanup.
-- Run `go test ./internal/modules/... ./internal/framework/... ./internal/cli ./cmd/audita`.
-- Run `go test ./...` before completing the full sequence.
-
-Acceptance criteria:
-
-- Test helpers are simpler without reducing coverage.
-- No parity or release fixture assertions are removed unless replaced by equivalent or stronger assertions.
-- No production behavior changes.
-
-## Final verification
-
-Before declaring the staged cleanup complete:
-
-- Run:
-  - `go test ./internal/core/config ./internal/core/outputschema`
-  - `go test ./internal/core/diagnostics ./internal/core/reporting`
-  - `go test ./internal/framework/proposal_generation ./internal/framework/validators ./internal/framework/runner`
-  - `go test ./internal/validators/...`
-  - `go test ./internal/modules/...`
-  - `go test ./internal/cli ./cmd/audita`
-  - `go test ./...`
-- Inspect `git diff` for accidental public CLI, config, report, diagnostics, prompt metadata, stage-name, or output-schema changes.
-- Update docs only when behavior intentionally changes, especially the intended Stage 2 unknown-module validation change.
-- Keep commits stage-sized and mention behavior-preservation tests in each commit message or PR description.
-
-## Assumptions
-
-- Unknown configured module keys should become config-validation failures before 1.0.
-- Diagnostics filenames and stage names are public enough to preserve unless a stage explicitly says otherwise.
-- Each stage should be implemented and reviewed separately.

examples/configkit-inheritance.yml

@@ -0,0 +1,15 @@
+version: 2
+profiles_dir: profiles/local
+backends:
+  local-base:
+    endpoint: http://127.0.0.1:11434/v1
+    concurrency: 4
+    queue_capacity: 0
+  local:
+    extends: local-base
+    concurrency: 2
+llm:
+  proposal_profile: local-proposal
+  validation_profile: local-validation
+pipeline:
+  modules: [grammar]

examples/minimal-config.yml

@@ -0,0 +1,13 @@
+version: 2
+profiles_dir: profiles/local
+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

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

examples/production-config.yml

@@ -0,0 +1,41 @@
+version: 2
+profiles_dir: profiles/service
+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/local-proposal.yaml

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

examples/profiles/local/local-validation.yaml

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

examples/profiles/service/service-proposal-testing.yaml

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

examples/profiles/service/service-proposal.yaml

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

examples/profiles/service/service-validation-testing.yaml

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

examples/profiles/service/service-validation.yaml

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

examples/tiny-glossary.yaml

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

examples/tiny-transcript.json

@@ -0,0 +1,9 @@
+[
+  {
+    "id": 1,
+    "speaker": "A",
+    "start": 0.0,
+    "end": 1.2,
+    "text": "hello world"
+  }
+]

go.mod

@@ -1,11 +1,25 @@
-module gitea.maximumdirect.net/eric/audita
+module gitea.maximumdirect.net/eric/audita/v3
 
-go 1.24.0
-
-require gopkg.in/yaml.v3 v3.0.1
+go 1.26.0
 
 require (
+	gitea.maximumdirect.net/eric/ConfigKit v0.7.1
+	gitea.maximumdirect.net/eric/ReleaseKit v0.4.1
+	gitea.maximumdirect.net/eric/promptkit v0.14.0
+	golang.org/x/mod v0.40.0
+	gopkg.in/yaml.v3 v3.0.1
+)
+
+require (
+	gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v3 v3.20260930.0 // indirect
+	gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v3 v3.20260930.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/yuin/goldmark/v2 v2.1.6 // indirect
+	go.yaml.in/yaml/v4 v4.0.0-rc.6 // indirect
+	golang.org/x/text v0.14.0 // indirect
 	gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c // indirect
 )
+
+tool gitea.maximumdirect.net/eric/ReleaseKit/cmd/releasekit

go.sum

@@ -1,4 +1,16 @@
+gitea.maximumdirect.net/eric/ConfigKit v0.7.1 h1:q3HrX4WWCPt1WfMydqFEaAmCf9s6Dq+vknJj0C/mdcI=
+gitea.maximumdirect.net/eric/ConfigKit v0.7.1/go.mod h1:C82sbyKHYMV1OwaD2GJanFrwTfcZfjlW2JsGze5b0kA=
+gitea.maximumdirect.net/eric/ReleaseKit v0.4.1 h1:Qn+mdebYOzCVCEXgCbuGSO/WHmJtItwaQ8e3XwY3qtI=
+gitea.maximumdirect.net/eric/ReleaseKit v0.4.1/go.mod h1:LVodqNQ3OIKv9NBq+fFeyMByd1lHY25YOmmpah/NaNI=
+gitea.maximumdirect.net/eric/promptkit v0.14.0 h1:HUzlcrFk18dNGPBgnHqjAw87O0c9Wl/IC1xc/VmzL10=
+gitea.maximumdirect.net/eric/promptkit v0.14.0/go.mod h1:2YGvNca3bNXZP+e+pJeGzsNUcxwkHvzvuoc+LNNiT3E=
+gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v3 v3.20260930.0 h1:lzfCDbzJQRGzIlRPRprnAV9hVVL5zUQy80VMQ0kbYa0=
+gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v3 v3.20260930.0/go.mod h1:HjS0f+3q0IdHCTEz+VVAEgIwIWJFAZUjuKdAtvtqKdg=
+gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v3 v3.20260930.0 h1:h12ZTRldAmpLAomj0oQRGteFxHLN1LPE6XDl9zJNbm8=
+gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v3 v3.20260930.0/go.mod h1:OEFBeKdjTsLzqJwLmXI2O5gG3r64FktcVJVb3mBrRfg=
 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/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=
@@ -10,6 +22,16 @@ 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/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/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.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=
 gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c h1:Hei/4ADfdWqJk1ZMxUNpqntNwaWcugrBjAiHlqqRiVk=
 gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c/go.mod h1:JHkPIbrfpd72SG/EVd6muEfDQjcINNoR0C8j2r3qZ4Q=

internal/cli/config_input.go

@@ -0,0 +1,233 @@
+package cli
+
+import (
+	"errors"
+	"flag"
+	"fmt"
+	"io"
+	"os"
+	"path/filepath"
+	"strconv"
+	"strings"
+
+	ck "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/config"
+)
+
+var systemConfigPaths = []string{"/usr/local/etc/audita/config.yml", "/etc/audita/config.yml"}
+
+type configInput struct {
+	ConfigPath     string
+	ConfigPathSet  bool
+	Overlay        string
+	View           string
+	TranscriptPath string
+	GlossaryPath   string
+	OutputPath     string
+	ReportDirSet   bool
+	Overrides      []ck.Override
+}
+
+type selectedConfig struct {
+	Path   string
+	Source string
+	Result *ck.Result[config.Config]
+}
+
+// parseConfigInput owns the common setting flags and process-only path flags.
+// A transcript before flags and one after flags are both accepted.
+func parseConfigInput(command string, args []string, output io.Writer) (configInput, bool, error) {
+	var input configInput
+	fs := flag.NewFlagSet(command, flag.ContinueOnError)
+	fs.SetOutput(output)
+	configPath := fs.String("config", "", "Main configuration YAML file")
+	overlay := fs.String("overlay", "", "Selected configuration overlay")
+	if command == "print-effective" {
+		fs.String("view", "settings", "Effective view: settings, profiles, or explain")
+	}
+	settingPaths := map[string]ck.Path{
+		"proposal-profile":                 ck.Keys("llm", "proposal_profile"),
+		"validation-profile":               ck.Keys("llm", "validation_profile"),
+		"output-schema":                    ck.Keys("output", "schema"),
+		"validation-max-prompt-tokens":     ck.Keys("validation", "max_prompt_tokens"),
+		"target-sections":                  ck.Keys("chunking", "target_sections"),
+		"max-section-tokens":               ck.Keys("chunking", "max_section_tokens"),
+		"min-section-tokens":               ck.Keys("chunking", "min_section_tokens"),
+		"normalize-max-segment-gap":        ck.Keys("normalization", "max_segment_gap"),
+		"normalize-ellipsis-gap":           ck.Keys("normalization", "ellipsis_gap"),
+		"normalize-max-segment-duration":   ck.Keys("normalization", "max_segment_duration"),
+		"normalize-max-segment-tokens":     ck.Keys("normalization", "max_segment_tokens"),
+		"glossary-confidence-threshold":    ck.Keys("thresholds", "glossary"),
+		"homophones-confidence-threshold":  ck.Keys("thresholds", "homophones"),
+		"spoken-word-confidence-threshold": ck.Keys("thresholds", "spoken_word"),
+		"grammar-confidence-threshold":     ck.Keys("thresholds", "grammar"),
+		"transcript-description":           ck.Keys("context", "description"),
+		"reporting":                        ck.Keys("reporting", "enabled"),
+		"report-dir":                       ck.Keys("reporting", "stdout_dir"),
+		"debug":                            ck.Keys("diagnostics", "debug"),
+		"work-dir":                         ck.Keys("diagnostics", "work_dir"),
+		"modules":                          ck.Keys("pipeline", "modules"),
+	}
+	for name := range settingPaths {
+		switch name {
+		case "reporting", "debug":
+			fs.Bool(name, false, "Setting override")
+		case "validation-max-prompt-tokens", "target-sections", "max-section-tokens", "min-section-tokens", "normalize-max-segment-tokens":
+			fs.Int(name, 0, "Setting override")
+		case "normalize-max-segment-gap", "normalize-ellipsis-gap", "normalize-max-segment-duration", "glossary-confidence-threshold", "homophones-confidence-threshold", "spoken-word-confidence-threshold", "grammar-confidence-threshold":
+			fs.Float64(name, 0, "Setting override")
+		default:
+			fs.String(name, "", "Setting override")
+		}
+	}
+	if command == "process" {
+		fs.String("glossary", "", "Glossary YAML file")
+		fs.String("output", "", "Corrected transcript output file")
+	}
+	parseArgs := args
+	front := ""
+	if command == "process" && len(args) > 0 && !strings.HasPrefix(args[0], "-") {
+		front, parseArgs = args[0], args[1:]
+	}
+	if err := fs.Parse(parseArgs); err != nil {
+		if errors.Is(err, flag.ErrHelp) {
+			return configInput{}, true, nil
+		}
+		return configInput{}, false, err
+	}
+	positions := fs.Args()
+	if front != "" {
+		positions = append([]string{front}, positions...)
+	}
+	if command == "process" {
+		if len(positions) != 1 {
+			return configInput{}, false, fmt.Errorf("expected exactly one transcript JSON path")
+		}
+		input.TranscriptPath = positions[0]
+		input.GlossaryPath = fs.Lookup("glossary").Value.String()
+		input.OutputPath = fs.Lookup("output").Value.String()
+		if strings.TrimSpace(input.GlossaryPath) == "" {
+			return configInput{}, false, fmt.Errorf("--glossary is required")
+		}
+	} else if len(positions) != 0 {
+		return configInput{}, false, fmt.Errorf("unexpected positional arguments")
+	}
+	input.ConfigPath, input.Overlay = *configPath, *overlay
+	if command == "print-effective" {
+		input.View = fs.Lookup("view").Value.String()
+		switch input.View {
+		case "settings", "profiles", "explain":
+		default:
+			return configInput{}, false, fmt.Errorf("unknown effective view %q", input.View)
+		}
+	}
+	fs.Visit(func(f *flag.Flag) {
+		if f.Name == "config" {
+			input.ConfigPathSet = true
+		}
+		if f.Name == "report-dir" {
+			input.ReportDirSet = true
+		}
+		path, ok := settingPaths[f.Name]
+		if !ok {
+			return
+		}
+		var value any = f.Value.String()
+		switch f.Name {
+		case "reporting", "debug":
+			value, _ = strconv.ParseBool(f.Value.String())
+		case "modules":
+			modules, err := config.ParseModulesCSV(f.Value.String())
+			if err != nil {
+				value = err
+			} else {
+				values := make([]any, len(modules))
+				for i, module := range modules {
+					values[i] = module
+				}
+				value = values
+			}
+		case "validation-max-prompt-tokens", "target-sections", "max-section-tokens", "min-section-tokens", "normalize-max-segment-tokens":
+			value, _ = strconv.Atoi(f.Value.String())
+		case "normalize-max-segment-gap", "normalize-ellipsis-gap", "normalize-max-segment-duration", "glossary-confidence-threshold", "homophones-confidence-threshold", "spoken-word-confidence-threshold", "grammar-confidence-threshold":
+			value, _ = strconv.ParseFloat(f.Value.String(), 64)
+		}
+		input.Overrides = append(input.Overrides, ck.Override{Path: path, Value: value, Flag: "--" + f.Name})
+	})
+	for _, override := range input.Overrides {
+		if err, ok := override.Value.(error); ok {
+			return configInput{}, false, fmt.Errorf("%s: %w", override.Flag, err)
+		}
+	}
+	return input, false, nil
+}
+
+func selectConfigPath(explicit string, set bool, stat func(string) (os.FileInfo, error), candidates []string) (string, string, error) {
+	if set {
+		if strings.TrimSpace(explicit) == "" {
+			return "", "", fmt.Errorf("--config requires a nonempty path")
+		}
+		if _, err := stat(explicit); err != nil {
+			return "", "", fmt.Errorf("config file %q: %w", explicit, err)
+		}
+		return explicit, "flag", nil
+	}
+	for _, path := range candidates {
+		if _, err := stat(path); err == nil {
+			return path, "default", nil
+		} else if !os.IsNotExist(err) {
+			return "", "", fmt.Errorf("config file %q: %w", path, err)
+		}
+	}
+	return "", "", fmt.Errorf("no configuration file found; select a config with backend and profile settings")
+}
+
+func loadConfigInput(input configInput, command string) (selectedConfig, error) {
+	if command == "validate" && (!input.ConfigPathSet || strings.TrimSpace(input.ConfigPath) == "") {
+		return selectedConfig{}, fmt.Errorf("--config is required")
+	}
+	path, source, err := selectConfigPath(input.ConfigPath, input.ConfigPathSet, os.Stat, systemConfigPaths)
+	if err != nil {
+		return selectedConfig{}, err
+	}
+	loaded, err := config.Load(ck.File(path), input.Overlay, input.Overrides...)
+	if err != nil {
+		return selectedConfig{}, err
+	}
+	return selectedConfig{Path: path, Source: source, Result: loaded}, nil
+}
+
+func configInputError(err error) string {
+	var loadErr *ck.LoadError
+	if !errors.As(err, &loadErr) {
+		return err.Error()
+	}
+	var messages []string
+	for _, diagnostic := range loadErr.Diagnostics() {
+		messages = append(messages, diagnostic.Message)
+	}
+	if len(messages) == 0 {
+		return err.Error()
+	}
+	return strings.Join(messages, "; ")
+}
+
+func selectedReportDir(cfg config.Config, outputPath string, reportDirSet bool) (string, error) {
+	if !cfg.Reporting.Enabled {
+		return "", nil
+	}
+	var reportDir string
+	if outputPath != "" {
+		if reportDirSet {
+			reportDir = cfg.Reporting.StdoutDir
+		} else {
+			reportDir = filepath.Dir(outputPath)
+		}
+	} else {
+		reportDir = cfg.Reporting.StdoutDir
+	}
+	if strings.TrimSpace(reportDir) == "" {
+		return "", fmt.Errorf("report directory is required when reporting is enabled for the selected destination")
+	}
+	return reportDir, nil
+}

internal/cli/config_input_test.go

@@ -0,0 +1,280 @@
+package cli
+
+import (
+	"errors"
+	"io"
+	"os"
+	"path/filepath"
+	"strings"
+	"testing"
+
+	ck "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/config"
+)
+
+func TestSharedConfigInput(t *testing.T) {
+	for _, command := range []string{"process", "validate", "print-effective"} {
+		t.Run(command, func(t *testing.T) {
+			args := []string{"--config", "main.yml", "--overlay", "testing", "--proposal-profile", "economy", "--modules", "", "--target-sections", "0"}
+			if command == "process" {
+				args = append([]string{"transcript.json", "--glossary", "glossary.yml"}, args...)
+			}
+			input, help, err := parseConfigInput(command, args, io.Discard)
+			if err != nil || help {
+				t.Fatalf("parse: %+v %v %v", input, help, err)
+			}
+			if !input.ConfigPathSet || input.ConfigPath != "main.yml" || input.Overlay != "testing" || len(input.Overrides) != 3 {
+				t.Fatalf("selection: %+v", input)
+			}
+			for _, override := range input.Overrides {
+				switch override.Path.String() {
+				case ck.Keys("pipeline", "modules").String():
+					if values, ok := override.Value.([]any); !ok || len(values) != 0 {
+						t.Fatalf("empty modules: %#v", override.Value)
+					}
+				case ck.Keys("chunking", "target_sections").String():
+					if override.Value != 0 {
+						t.Fatalf("zero target: %#v", override.Value)
+					}
+				}
+			}
+		})
+	}
+}
+
+func TestConfigInputRejectsRemovedAndProcessOnlyFlags(t *testing.T) {
+	for _, command := range []string{"process", "validate", "print-effective"} {
+		for _, flag := range []string{"--model", "--llm-api-key", "--max-retries", "--llm-concurrency", "--report-json", "--work-dir-retention"} {
+			args := []string{flag, "value"}
+			if command == "process" {
+				args = append([]string{"transcript.json", "--glossary", "glossary.yml"}, args...)
+			}
+			if _, _, err := parseConfigInput(command, args, io.Discard); err == nil {
+				t.Fatalf("%s accepted %s", command, flag)
+			}
+		}
+	}
+	for _, command := range []string{"validate", "print-effective"} {
+		if _, _, err := parseConfigInput(command, []string{"--glossary", "glossary.yml"}, io.Discard); err == nil {
+			t.Fatalf("%s accepted process path", command)
+		}
+		if _, _, err := parseConfigInput(command, []string{"transcript.json"}, io.Discard); err == nil {
+			t.Fatalf("%s accepted positional", command)
+		}
+	}
+	for _, command := range []string{"process", "validate", "print-effective"} {
+		_, help, err := parseConfigInput(command, []string{"--help"}, io.Discard)
+		if err != nil || !help {
+			t.Fatalf("%s help: %v %v", command, help, err)
+		}
+	}
+}
+
+func TestConfigSelection(t *testing.T) {
+	dir := t.TempDir()
+	first, second := filepath.Join(dir, "first.yml"), filepath.Join(dir, "second.yml")
+	if err := os.WriteFile(second, []byte("version: 2\n"), 0600); err != nil {
+		t.Fatal(err)
+	}
+	path, source, err := selectConfigPath("", false, os.Stat, []string{first, second})
+	if err != nil || path != second || source != "default" {
+		t.Fatalf("discovery: %q %q %v", path, source, err)
+	}
+	for _, tc := range []struct {
+		explicit   string
+		set        bool
+		candidates []string
+	}{
+		{"", true, []string{second}}, {first, true, []string{second}}, {"", false, []string{first}},
+	} {
+		if _, _, err := selectConfigPath(tc.explicit, tc.set, os.Stat, tc.candidates); err == nil {
+			t.Fatalf("accepted unavailable selection: %+v", tc)
+		}
+	}
+	statDenied := func(string) (os.FileInfo, error) { return nil, os.ErrPermission }
+	if _, _, err := selectConfigPath("", false, statDenied, []string{first}); !errors.Is(err, os.ErrPermission) {
+		t.Fatalf("inaccessible candidate: %v", err)
+	}
+	path, source, err = selectConfigPath(second, true, os.Stat, []string{first})
+	if err != nil || path != second || source != "flag" {
+		t.Fatalf("explicit path: %q %q %v", path, source, err)
+	}
+}
+
+func TestLegacyEnvironmentDoesNotSelectConfig(t *testing.T) {
+	t.Setenv("AUDITA_CONFIG", filepath.Join(t.TempDir(), "legacy.yml"))
+	_, _, err := selectConfigPath("", false, os.Stat, []string{filepath.Join(t.TempDir(), "missing.yml")})
+	if err == nil || !strings.Contains(err.Error(), "no configuration file") {
+		t.Fatalf("legacy environment changed discovery: %v", err)
+	}
+}
+
+func TestEffectiveViewParsing(t *testing.T) {
+	for _, view := range []string{"settings", "profiles", "explain"} {
+		input, _, err := parseConfigInput("print-effective", []string{"--view", view}, io.Discard)
+		if err != nil || input.View != view {
+			t.Fatalf("%q: %+v %v", view, input, err)
+		}
+	}
+	if _, _, err := parseConfigInput("print-effective", []string{"--view", "raw"}, io.Discard); err == nil {
+		t.Fatal("unknown view accepted")
+	}
+	if _, _, err := parseConfigInput("validate", []string{"--view", "profiles"}, io.Discard); err == nil {
+		t.Fatal("validate accepted inspection-only flag")
+	}
+}
+
+func TestSharedLoadingUsesSelectedFileOverlayAndVisitedOverrides(t *testing.T) {
+	dir := t.TempDir()
+	if err := os.Mkdir(filepath.Join(dir, "overlays"), 0700); err != nil {
+		t.Fatal(err)
+	}
+	main := filepath.Join(dir, "config.yml")
+	base := "version: 2\nbackends:\n  local:\n    endpoint: https://local.invalid/v1\nllm:\n  proposal_profile: base\nchunking:\n  max_section_tokens: 900\n"
+	if err := os.WriteFile(main, []byte(base), 0600); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(dir, "overlays", "testing.yml"), []byte("llm:\n  proposal_profile: testing\n"), 0600); err != nil {
+		t.Fatal(err)
+	}
+	for _, command := range []string{"process", "validate", "print-effective"} {
+		args := []string{"--config", main, "--overlay", "testing", "--min-section-tokens", "500"}
+		if command == "process" {
+			args = append([]string{"input.json", "--glossary", "glossary.yml"}, args...)
+		}
+		input, _, err := parseConfigInput(command, args, io.Discard)
+		if err != nil {
+			t.Fatal(err)
+		}
+		selected, err := loadConfigInput(input, command)
+		if err != nil {
+			t.Fatal(err)
+		}
+		c := selected.Result.Config
+		if c.LLM.ProposalProfile != "testing" || c.LLM.ValidationProfile != "testing" || c.Chunking.MinSectionTokens != 500 || c.Chunking.MaxSectionTokens != 900 {
+			t.Fatalf("%s resolved %+v", command, c)
+		}
+	}
+	input, _, err := parseConfigInput("validate", []string{"--overlay", "testing"}, io.Discard)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if _, err := loadConfigInput(input, "validate"); err == nil {
+		t.Fatal("validate accepted discovery")
+	}
+	input, _, err = parseConfigInput("validate", []string{"--config", main}, io.Discard)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if _, err := loadConfigInput(input, "validate"); err == nil {
+		t.Fatal("unmodified invalid lower-precedence section relation accepted")
+	}
+}
+
+func TestReportingAndDebugOverridesRemainIndependent(t *testing.T) {
+	dir := t.TempDir()
+	if err := os.Mkdir(filepath.Join(dir, "overlays"), 0700); err != nil {
+		t.Fatal(err)
+	}
+	main := filepath.Join(dir, "config.yml")
+	base := "version: 2\nbackends:\n  local:\n    endpoint: https://local.invalid/v1\nllm:\n  proposal_profile: base\n"
+	if err := os.WriteFile(main, []byte(base), 0600); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(dir, "overlays", "testing.yml"), []byte("reporting:\n  enabled: true\n  stdout_dir: reports\ndiagnostics:\n  debug: true\n"), 0600); err != nil {
+		t.Fatal(err)
+	}
+	defaultInput, _, err := parseConfigInput("validate", []string{"--config", main}, io.Discard)
+	if err != nil {
+		t.Fatal(err)
+	}
+	defaults, err := loadConfigInput(defaultInput, "validate")
+	if err != nil {
+		t.Fatal(err)
+	}
+	if !defaults.Result.Config.Reporting.Enabled || defaults.Result.Config.Reporting.StdoutDir != "." || defaults.Result.Config.Diagnostics.Debug {
+		t.Fatalf("unexpected defaults: %+v", defaults.Result.Config)
+	}
+	for _, command := range []string{"process", "validate", "print-effective"} {
+		args := []string{"--config", main, "--overlay", "testing", "--reporting=false", "--debug=false"}
+		if command == "process" {
+			args = append([]string{"input.json", "--glossary", "glossary.yml"}, args...)
+		}
+		input, _, err := parseConfigInput(command, args, io.Discard)
+		if err != nil {
+			t.Fatal(err)
+		}
+		if len(input.Overrides) != 2 || input.Overrides[0].Value != false || input.Overrides[1].Value != false {
+			t.Fatalf("boolean overrides must remain typed: %+v", input.Overrides)
+		}
+		selected, err := loadConfigInput(input, command)
+		if err != nil {
+			t.Fatal(err)
+		}
+		if selected.Result.Config.Reporting.Enabled || selected.Result.Config.Diagnostics.Debug || selected.Result.Config.Reporting.StdoutDir != "reports" {
+			t.Fatalf("%s did not honor explicit false: %+v", command, selected.Result.Config)
+		}
+	}
+	processInput, _, err := parseConfigInput("process", []string{"input.json", "--glossary", "glossary.yml", "--config", main, "--overlay", "testing"}, io.Discard)
+	if err != nil {
+		t.Fatal(err)
+	}
+	processConfig, err := loadConfigInput(processInput, "process")
+	if err != nil {
+		t.Fatal(err)
+	}
+	if got, err := selectedReportDir(processConfig.Result.Config, filepath.Join("out", "corrected.json"), processInput.ReportDirSet); err != nil || got != "out" {
+		t.Fatalf("overlay stdout directory redirected file output: %q %v", got, err)
+	}
+}
+
+func TestReportDirectorySelectionOnlyUsesActiveDestination(t *testing.T) {
+	cfg := config.Config{Reporting: config.Reporting{Enabled: true, StdoutDir: "reports"}}
+	if got, err := selectedReportDir(cfg, "", false); err != nil || got != "reports" {
+		t.Fatalf("stdout destination: %q %v", got, err)
+	}
+	if got, err := selectedReportDir(cfg, filepath.Join("out", "corrected.json"), false); err != nil || got != "out" {
+		t.Fatalf("file destination ignored stdout setting: %q %v", got, err)
+	}
+	if got, err := selectedReportDir(cfg, filepath.Join("out", "corrected.json"), true); err != nil || got != "reports" {
+		t.Fatalf("explicit file report directory: %q %v", got, err)
+	}
+	cfg.Reporting.StdoutDir = ""
+	if got, err := selectedReportDir(cfg, filepath.Join("out", "corrected.json"), false); err != nil || got != "out" {
+		t.Fatalf("inactive blank configured report directory rejected for file output: %q %v", got, err)
+	}
+	if _, err := selectedReportDir(cfg, filepath.Join("out", "corrected.json"), true); err == nil {
+		t.Fatal("active explicit blank report directory accepted for file output")
+	}
+	if _, err := selectedReportDir(cfg, "", false); err == nil {
+		t.Fatal("enabled stdout reporting accepted blank destination")
+	}
+	cfg.Reporting.Enabled = false
+	if got, err := selectedReportDir(cfg, filepath.Join("out", "corrected.json"), true); err != nil || got != "" {
+		t.Fatalf("disabled reporting probed destination: %q %v", got, err)
+	}
+}
+
+func TestBareBooleanFlagsAndReportDirectoryOverride(t *testing.T) {
+	input, _, err := parseConfigInput("process", []string{"input.json", "--glossary", "glossary.yml", "--reporting", "--debug", "--report-dir", "reports"}, io.Discard)
+	if err != nil {
+		t.Fatal(err)
+	}
+	values := map[string]any{}
+	for _, override := range input.Overrides {
+		values[override.Path.String()] = override.Value
+	}
+	if values[ck.Keys("reporting", "enabled").String()] != true || values[ck.Keys("diagnostics", "debug").String()] != true || values[ck.Keys("reporting", "stdout_dir").String()] != "reports" {
+		t.Fatalf("incorrect visited overrides: %+v", values)
+	}
+	if !input.ReportDirSet {
+		t.Fatal("explicit --report-dir presence was not recorded")
+	}
+	withoutReportDir, _, err := parseConfigInput("process", []string{"input.json", "--glossary", "glossary.yml"}, io.Discard)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if withoutReportDir.ReportDirSet {
+		t.Fatal("absent --report-dir was recorded as explicit")
+	}
+}

internal/cli/parity_test.go

@@ -1,338 +0,0 @@
-package cli
-
-import (
-	"bytes"
-	"encoding/json"
-	"os"
-	"path/filepath"
-	"reflect"
-	"strings"
-	"testing"
-
-	"gitea.maximumdirect.net/eric/audita/internal/core/reporting"
-)
-
-type parityFixtureCase struct {
-	Name                    string            `json:"name"`
-	TranscriptFile          string            `json:"transcript_file"`
-	GlossaryFile            string            `json:"glossary_file"`
-	ModulesCSV              string            `json:"modules_csv,omitempty"`
-	ProposalResponsesFile   string            `json:"proposal_responses_file,omitempty"`
-	ValidationResponsesFile string            `json:"validation_responses_file,omitempty"`
-	Env                     map[string]string `json:"env,omitempty"`
-	Expect                  parityExpectation `json:"expect"`
-}
-
-type parityExpectation struct {
-	ExitCode                     int      `json:"exit_code"`
-	Status                       string   `json:"status,omitempty"`
-	ErrorPhase                   string   `json:"error_phase,omitempty"`
-	StdoutMode                   string   `json:"stdout_mode,omitempty"` // empty|json
-	StderrContains               string   `json:"stderr_contains,omitempty"`
-	OutputTranscriptFile         string   `json:"output_transcript_file,omitempty"`
-	ModuleInstances              []string `json:"module_instances,omitempty"`
-	ModuleCount                  int      `json:"module_count,omitempty"`
-	TotalAppliedChanges          int      `json:"total_applied_changes,omitempty"`
-	TotalSkippedChanges          int      `json:"total_skipped_changes,omitempty"`
-	FailedModuleInstance         string   `json:"failed_module_instance,omitempty"`
-	ValidatorRejectedReasonCodes []string `json:"validator_rejected_reason_codes,omitempty"`
-	ApplicationSkipReasonCodes   []string `json:"application_skip_reason_codes,omitempty"`
-	RequireErrorLog              bool     `json:"require_error_log,omitempty"`
-	SecretMarkers                []string `json:"secret_markers,omitempty"`
-	ExpectedProposalCalls        []string `json:"expected_proposal_calls,omitempty"`
-	ExpectedValidationCalls      []string `json:"expected_validation_calls,omitempty"`
-	ModuleAppliedCounts          []int    `json:"module_applied_counts,omitempty"`
-	ModuleRejectedCounts         []int    `json:"module_rejected_counts,omitempty"`
-	ModuleSkipCounts             []int    `json:"module_skip_counts,omitempty"`
-	MinResponsePayloadArtifacts  int      `json:"min_response_payload_artifacts,omitempty"`
-}
-
-func TestParityFixtures(t *testing.T) {
-	casePaths, err := filepath.Glob(parityFixturePath("*.case.json"))
-	if err != nil {
-		t.Fatalf("glob parity fixtures: %v", err)
-	}
-	if len(casePaths) == 0 {
-		t.Fatal("expected at least one parity fixture case")
-	}
-
-	for _, casePath := range casePaths {
-		fx := loadParityFixtureCase(t, casePath)
-		t.Run(fx.Name, func(t *testing.T) {
-			runParityFixtureCase(t, filepath.Dir(casePath), fx)
-		})
-	}
-}
-
-func loadParityFixtureCase(t *testing.T, casePath string) parityFixtureCase {
-	t.Helper()
-	var fx parityFixtureCase
-	raw := readFile(t, casePath)
-	if err := json.Unmarshal(raw, &fx); err != nil {
-		t.Fatalf("parse parity case %q: %v", casePath, err)
-	}
-	if strings.TrimSpace(fx.Name) == "" {
-		t.Fatalf("parity case %q missing name", casePath)
-	}
-	return fx
-}
-
-func runParityFixtureCase(t *testing.T, caseDir string, fx parityFixtureCase) {
-	t.Helper()
-	for k, v := range fx.Env {
-		t.Setenv(k, v)
-	}
-
-	proposalClient := &fakeStructuredLLMClient{}
-	validationClient := &fakeStructuredLLMClient{}
-
-	if strings.TrimSpace(fx.ProposalResponsesFile) != "" {
-		raw := readFile(t, filepath.Join(caseDir, fx.ProposalResponsesFile))
-		if err := json.Unmarshal(raw, &proposalClient.proposalResponses); err != nil {
-			t.Fatalf("parse proposal responses: %v", err)
-		}
-		processProposalLLMClient = proposalClient
-	}
-	if strings.TrimSpace(fx.ValidationResponsesFile) != "" {
-		raw := readFile(t, filepath.Join(caseDir, fx.ValidationResponsesFile))
-		if err := json.Unmarshal(raw, &validationClient.validationResponses); err != nil {
-			t.Fatalf("parse validation responses: %v", err)
-		}
-		processValidationLLMClient = validationClient
-	}
-	t.Cleanup(func() {
-		processProposalLLMClient = nil
-		processValidationLLMClient = nil
-	})
-
-	var stdout, stderr bytes.Buffer
-	workDir := t.TempDir()
-	outputPath := filepath.Join(t.TempDir(), "out.json")
-	reportPath := filepath.Join(t.TempDir(), "report.json")
-	args := []string{
-		"process",
-		filepath.Join(caseDir, fx.TranscriptFile),
-		"--glossary",
-		filepath.Join(caseDir, fx.GlossaryFile),
-		"--report-json",
-		reportPath,
-		"--work-dir",
-		workDir,
-		"--work-dir-retention",
-		"always",
-	}
-	// Keep stdout shape deterministic for parity tests.
-	if fx.Expect.StdoutMode != "json" {
-		args = append(args, "--output", outputPath)
-	}
-	if strings.TrimSpace(fx.ModulesCSV) != "" {
-		args = append(args, "--modules", fx.ModulesCSV)
-	}
-
-	exitCode := Run(args, &stdout, &stderr)
-	if exitCode != fx.Expect.ExitCode {
-		t.Fatalf("expected exit code %d, got %d stderr=%q", fx.Expect.ExitCode, exitCode, stderr.String())
-	}
-
-	switch fx.Expect.StdoutMode {
-	case "json":
-		if _, err := json.Marshal(stdout.String()); err != nil {
-			t.Fatalf("unexpected stdout marshal error: %v", err)
-		}
-		if !json.Valid(stdout.Bytes()) {
-			t.Fatalf("expected JSON stdout, got %q", stdout.String())
-		}
-	default:
-		if stdout.Len() != 0 {
-			t.Fatalf("expected empty stdout, got %q", stdout.String())
-		}
-	}
-
-	if fx.Expect.StderrContains != "" && !strings.Contains(stderr.String(), fx.Expect.StderrContains) {
-		t.Fatalf("expected stderr to contain %q, got %q", fx.Expect.StderrContains, stderr.String())
-	}
-
-	report := readProcessReport(t, reportPath)
-	assertParityReport(t, report, fx.Expect)
-
-	runDir := onlyRunDir(t, workDir)
-	runDirReport := readProcessReport(t, filepath.Join(runDir, "report.json"))
-	assertParityReport(t, runDirReport, fx.Expect)
-
-	if fx.Expect.RequireErrorLog {
-		if _, err := os.Stat(filepath.Join(runDir, "error.log")); err != nil {
-			t.Fatalf("expected error.log: %v", err)
-		}
-	}
-
-	if strings.TrimSpace(fx.Expect.OutputTranscriptFile) != "" && fx.Expect.ExitCode == 0 {
-		got := readFile(t, outputPath)
-		want := readFile(t, filepath.Join(caseDir, fx.Expect.OutputTranscriptFile))
-		assertJSONSemanticEqual(t, want, got)
-	}
-
-	if len(fx.Expect.ExpectedProposalCalls) > 0 && !reflect.DeepEqual(proposalClient.calls, fx.Expect.ExpectedProposalCalls) {
-		t.Fatalf("unexpected proposal calls: got %v want %v", proposalClient.calls, fx.Expect.ExpectedProposalCalls)
-	}
-	if len(fx.Expect.ExpectedValidationCalls) > 0 && !reflect.DeepEqual(validationClient.calls, fx.Expect.ExpectedValidationCalls) {
-		t.Fatalf("unexpected validation calls: got %v want %v", validationClient.calls, fx.Expect.ExpectedValidationCalls)
-	}
-
-	if len(fx.Expect.SecretMarkers) > 0 {
-		assertNoSecretMarkers(t, reportPath, fx.Expect.SecretMarkers)
-		assertNoSecretMarkersInTree(t, runDir, fx.Expect.SecretMarkers)
-	}
-	if fx.Expect.MinResponsePayloadArtifacts > 0 {
-		matches, err := filepath.Glob(filepath.Join(runDir, "*", "*response-payload.json"))
-		if err != nil {
-			t.Fatalf("glob response payload artifacts: %v", err)
-		}
-		if len(matches) < fx.Expect.MinResponsePayloadArtifacts {
-			t.Fatalf("expected at least %d response payload artifacts, got %d", fx.Expect.MinResponsePayloadArtifacts, len(matches))
-		}
-	}
-}
-
-func assertParityReport(t *testing.T, report reporting.ProcessReport, exp parityExpectation) {
-	t.Helper()
-	if exp.Status != "" && report.Status != exp.Status {
-		t.Fatalf("expected report status %q, got %q", exp.Status, report.Status)
-	}
-	if exp.ErrorPhase != "" && report.ErrorPhase != exp.ErrorPhase {
-		t.Fatalf("expected report error_phase %q, got %q", exp.ErrorPhase, report.ErrorPhase)
-	}
-	if len(exp.ModuleInstances) > 0 {
-		got := make([]string, 0, len(report.ModuleResults))
-		for _, mr := range report.ModuleResults {
-			got = append(got, mr.ModuleInstance)
-		}
-		if !reflect.DeepEqual(got, exp.ModuleInstances) {
-			t.Fatalf("unexpected module instances: got %v want %v", got, exp.ModuleInstances)
-		}
-	}
-	if exp.ModuleCount > 0 {
-		if report.ModulesSummary == nil || report.ModulesSummary.ModuleCount != exp.ModuleCount {
-			t.Fatalf("expected module_count=%d, got %+v", exp.ModuleCount, report.ModulesSummary)
-		}
-	}
-	if exp.TotalAppliedChanges > 0 {
-		if report.ModulesSummary == nil || report.ModulesSummary.TotalAppliedChanges != exp.TotalAppliedChanges {
-			t.Fatalf("expected total_applied_changes=%d, got %+v", exp.TotalAppliedChanges, report.ModulesSummary)
-		}
-	}
-	if exp.TotalSkippedChanges > 0 {
-		if report.ModulesSummary == nil || report.ModulesSummary.TotalSkippedChanges != exp.TotalSkippedChanges {
-			t.Fatalf("expected total_skipped_changes=%d, got %+v", exp.TotalSkippedChanges, report.ModulesSummary)
-		}
-	}
-	if exp.FailedModuleInstance != "" {
-		if report.ModulesSummary == nil || report.ModulesSummary.FailedModuleInstance != exp.FailedModuleInstance {
-			t.Fatalf("expected failed_module_instance=%q, got %+v", exp.FailedModuleInstance, report.ModulesSummary)
-		}
-	}
-
-	if len(exp.ValidatorRejectedReasonCodes) > 0 {
-		got := collectValidatorRejectedReasonCodes(report.ModuleResults)
-		if !reflect.DeepEqual(got, exp.ValidatorRejectedReasonCodes) {
-			t.Fatalf("unexpected validator rejected reason codes: got %v want %v", got, exp.ValidatorRejectedReasonCodes)
-		}
-	}
-	if len(exp.ApplicationSkipReasonCodes) > 0 {
-		got := collectApplicationSkipReasonCodes(report.ModuleResults)
-		if !reflect.DeepEqual(got, exp.ApplicationSkipReasonCodes) {
-			t.Fatalf("unexpected application skip reason codes: got %v want %v", got, exp.ApplicationSkipReasonCodes)
-		}
-	}
-	if len(exp.ModuleAppliedCounts) > 0 {
-		got := make([]int, 0, len(report.ModuleResults))
-		for _, mr := range report.ModuleResults {
-			got = append(got, len(mr.AppliedChanges))
-		}
-		if !reflect.DeepEqual(got, exp.ModuleAppliedCounts) {
-			t.Fatalf("unexpected per-module applied counts: got %v want %v", got, exp.ModuleAppliedCounts)
-		}
-	}
-	if len(exp.ModuleRejectedCounts) > 0 {
-		got := make([]int, 0, len(report.ModuleResults))
-		for _, mr := range report.ModuleResults {
-			got = append(got, len(mr.ValidatorRejected))
-		}
-		if !reflect.DeepEqual(got, exp.ModuleRejectedCounts) {
-			t.Fatalf("unexpected per-module rejected counts: got %v want %v", got, exp.ModuleRejectedCounts)
-		}
-	}
-	if len(exp.ModuleSkipCounts) > 0 {
-		got := make([]int, 0, len(report.ModuleResults))
-		for _, mr := range report.ModuleResults {
-			got = append(got, len(mr.SkippedChanges))
-		}
-		if !reflect.DeepEqual(got, exp.ModuleSkipCounts) {
-			t.Fatalf("unexpected per-module skip counts: got %v want %v", got, exp.ModuleSkipCounts)
-		}
-	}
-}
-
-func collectValidatorRejectedReasonCodes(results []reporting.ModuleReport) []string {
-	out := make([]string, 0)
-	for _, mr := range results {
-		for _, vr := range mr.ValidatorRejected {
-			out = append(out, vr.ReasonCode)
-		}
-	}
-	return out
-}
-
-func collectApplicationSkipReasonCodes(results []reporting.ModuleReport) []string {
-	out := make([]string, 0)
-	for _, mr := range results {
-		for _, sk := range mr.SkippedChanges {
-			out = append(out, string(sk.SkipReason))
-		}
-	}
-	return out
-}
-
-func assertJSONSemanticEqual(t *testing.T, expected []byte, actual []byte) {
-	t.Helper()
-	var exp any
-	var act any
-	if err := json.Unmarshal(expected, &exp); err != nil {
-		t.Fatalf("unmarshal expected json: %v", err)
-	}
-	if err := json.Unmarshal(actual, &act); err != nil {
-		t.Fatalf("unmarshal actual json: %v", err)
-	}
-	if !reflect.DeepEqual(exp, act) {
-		t.Fatalf("JSON mismatch\nexpected=%s\nactual=%s", string(expected), string(actual))
-	}
-}
-
-func assertNoSecretMarkers(t *testing.T, filePath string, markers []string) {
-	t.Helper()
-	raw := string(readFile(t, filePath))
-	for _, marker := range markers {
-		if marker != "" && strings.Contains(raw, marker) {
-			t.Fatalf("secret marker %q leaked in %s", marker, filePath)
-		}
-	}
-}
-
-func assertNoSecretMarkersInTree(t *testing.T, root string, markers []string) {
-	t.Helper()
-	_ = filepath.WalkDir(root, func(path string, d os.DirEntry, err error) error {
-		if err != nil || d == nil || d.IsDir() {
-			return nil
-		}
-		raw := string(readFile(t, path))
-		for _, marker := range markers {
-			if marker != "" && strings.Contains(raw, marker) {
-				t.Fatalf("secret marker %q leaked in %s", marker, path)
-			}
-		}
-		return nil
-	})
-}
-
-func parityFixturePath(name string) string {
-	return filepath.Join("testdata", "parity", name)
-}

internal/cli/process.go

@@ -0,0 +1,442 @@
+package cli
+
+import (
+	"bytes"
+	"context"
+	"crypto/rand"
+	"encoding/hex"
+	"errors"
+	"fmt"
+	"io"
+	"strings"
+	"sync"
+	"time"
+
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/chunking"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/config"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/diagnostics"
+	coreio "gitea.maximumdirect.net/eric/audita/v3/internal/core/io"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/normalization"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/outputschema"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/redaction"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/reporting"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/core/schema"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/framework/contracts"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/framework/llm"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/framework/modules"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/framework/outcomes"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/framework/processreport"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/framework/runner"
+	"gitea.maximumdirect.net/eric/audita/v3/internal/framework/structuredoutput"
+)
+
+func runProcess(ctx context.Context, args []string, stdout, stderr io.Writer) int {
+	input, help, err := parseConfigInput("process", args, stderr)
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", configInputError(err))
+		return 2
+	}
+	if help {
+		writeProcessUsage(stdout)
+		return 0
+	}
+	selected, err := loadConfigInput(input, "process")
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", configInputError(err))
+		return 2
+	}
+	cfg := selected.Result.Config
+	reportDir, err := selectedReportDir(cfg, input.OutputPath, input.ReportDirSet)
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", llm.RedactError(err, cfg))
+		return 2
+	}
+	if cfg.Diagnostics.Debug && strings.TrimSpace(cfg.Diagnostics.WorkDir) == "" {
+		fmt.Fprintln(stderr, "audita process: debug work directory is required")
+		return 2
+	}
+	if err := ctx.Err(); err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", err)
+		return 1
+	}
+	runtime, err := llm.NewRuntime(ctx, cfg, selected.Path, nil)
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", llm.RedactError(err, cfg))
+		if ctx.Err() != nil || llm.IsAssetError(err) {
+			return 1
+		}
+		return 2
+	}
+	specs, err := contracts.ResolveModuleRunSpecs(cfg.Pipeline.Modules)
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", llm.RedactError(err, cfg))
+		return 2
+	}
+	runID, err := generateRunID()
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: run ID: %s\n", llm.RedactError(err, cfg))
+		return 1
+	}
+	started := time.Now().UTC()
+	state := &processState{cfg: cfg, runtime: runtime, specs: specs, runID: runID, started: started,
+		transcriptPath: input.TranscriptPath, glossaryPath: input.GlossaryPath, outputPath: input.OutputPath,
+		selected: selected, overlay: input.Overlay, stderr: stderr, stdout: stdout, ctx: ctx}
+	protected := []string{input.GlossaryPath}
+	for _, source := range selected.Result.Sources() {
+		if source.Path != "" {
+			protected = append(protected, source.Path)
+		}
+	}
+	protected = append(protected, runtime.SourcePaths...)
+	session, err := diagnostics.PrepareOutput(diagnostics.OutputSelection{InputTranscriptPath: input.TranscriptPath, TranscriptPath: input.OutputPath,
+		ReportDir: reportDir, ReportingEnabled: cfg.Reporting.Enabled, ProtectedPaths: protected})
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", llm.RedactError(err, cfg))
+		return 2
+	}
+	state.session = session
+	initial := state.snapshot(reporting.StatusInProgress, nil, nil)
+	initialBundle, err := state.bundle(initial)
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", llm.RedactError(err, cfg))
+		return 1
+	}
+	initFailure := []processreport.RunFailure{{Phase: "initialization", Reason: outcomes.ReasonInternalFailure}}
+	failedInit, err := state.bundle(state.snapshot(reporting.StatusFailed, nil, initFailure))
+	if err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", llm.RedactError(err, cfg))
+		return 1
+	}
+	if err := session.Initialize(initialBundle, failedInit); err != nil {
+		fmt.Fprintf(stderr, "audita process: %s\n", llm.RedactError(err, cfg))
+		return 1
+	}
+	state.startDebug()
+	return state.execute()
+}
+
+type processState struct {
+	cfg            config.Config
+	runtime        *llm.Runtime
+	specs          []contracts.ModuleRunSpec
+	runID          string
+	started        time.Time
+	transcriptPath string
+	glossaryPath   string
+	outputPath     string
+	selected       selectedConfig
+	overlay        string
+	ctx            context.Context
+	stdout         io.Writer
+	stderr         io.Writer
+	session        *diagnostics.OutputSession
+	debugDir       *diagnostics.RunDirectory
+	debugWarnings  []string
+	debugMu        sync.Mutex
+	runOutput      *runner.RunOutput
+}
+
+func generateRunID() (string, error) {
+	var random [12]byte
+	if _, err := rand.Read(random[:]); err != nil {
+		return "", err
+	}
+	return "run-" + hex.EncodeToString(random[:]), nil
+}
+
+func (s *processState) snapshot(status string, completed *time.Time, failures []processreport.RunFailure) reporting.Snapshot {
+	return processreport.Build(processreport.BuildInput{RunID: s.runID, Status: status, StartedAt: s.started,
+		CompletedAt: completed, TranscriptPath: s.transcriptPath, GlossaryPath: s.glossaryPath,
+		OutputPath: s.outputPath, ModuleSpecs: s.specs, RunOutput: s.runOutput, RunFailures: failures})
+}
+
+func (s *processState) bundle(snapshot reporting.Snapshot) (diagnostics.ReportBundle, error) {
+	if !s.cfg.Reporting.Enabled {
+		return diagnostics.ReportBundle{}, nil
+	}
+	secrets := llm.ConfiguredSecrets(&s.cfg)
+	errorsYAML, err := reporting.YAML(snapshot.ErrorsDocument(), secrets...)
+	if err != nil {
+		return diagnostics.ReportBundle{}, err
+	}
+	recoveriesYAML, err := reporting.YAML(snapshot.RecoveriesDocument(), secrets...)
+	if err != nil {
+		return diagnostics.ReportBundle{}, err
+	}
+	return diagnostics.ReportBundle{Errors: errorsYAML, Recoveries: recoveriesYAML,
+		Markdown: reporting.Markdown(snapshot, secrets...)}, nil
+}
+
+func (s *processState) debugWrite(label string, write func(*diagnostics.RunDirectory) error) {
+	if s.debugDir == nil {
+		return
+	}
+	if err := write(s.debugDir); err != nil {
+		s.reportDiagnosticError(fmt.Errorf("%s: %w", label, err))
+	}
+}
+
+func (s *processState) startDebug() {
+	if !s.cfg.Diagnostics.Debug {
+		return
+	}
+	dir, err := diagnostics.NewRunDirectory(s.cfg.Diagnostics.WorkDir, s.runID, llm.ConfiguredSecrets(&s.cfg)...)
+	if err != nil {
+		s.reportDiagnosticError(fmt.Errorf("directory: %w", err))
+		return
+	}
+	s.debugDir = dir
+	s.debugWrite("invocation", func(d *diagnostics.RunDirectory) error {
+		return d.WriteInvocationMetadata(diagnostics.InvocationMetadata{
+			Operation: "process", TranscriptPath: s.transcriptPath, GlossaryPath: s.glossaryPath,
+			OutputPath: s.outputPath, ConfigPath: s.selected.Path, ConfigSource: s.selected.Source,
+			Overlay: s.overlay, ConfigVersion: &s.cfg.Version, TranscriptDescription: s.cfg.Context.Description,
+			Modules: append([]string(nil), s.cfg.Pipeline.Modules...), RunID: s.runID, StartedAt: s.started,
+		})
+	})
+	var effective bytes.Buffer
+	if err := s.selected.Result.WriteEffective(&effective); err == nil {
+		s.debugWrite("effective settings", func(d *diagnostics.RunDirectory) error { return d.WriteEffectiveConfig(effective.Bytes()) })
+	} else {
+		s.reportDiagnosticError(fmt.Errorf("effective settings: %w", err))
+	}
+	if origins, err := llm.ExplanationYAML(s.selected.Result); err == nil {
+		s.debugWrite("configuration origins", func(d *diagnostics.RunDirectory) error {
+			return d.WriteYAMLArtifact(diagnostics.ArtifactConfigOrigins, origins)
+		})
+	} else {
+		s.reportDiagnosticError(fmt.Errorf("configuration origins: %w", err))
+	}
+	if profiles, err := s.runtime.SelectedProfilesYAML(); err == nil {
+		s.debugWrite("selected profiles", func(d *diagnostics.RunDirectory) error {
+			return d.WriteYAMLArtifact(diagnostics.ArtifactSelectedProfiles, profiles)
+		})
+	} else {
+		s.reportDiagnosticError(fmt.Errorf("selected profiles: %w", err))
+	}
+}
+
+func (s *processState) debugPath() string {
+	if s.debugDir == nil {
+		return ""
+	}
+	return s.debugDir.Path()
+}
+
+func (s *processState) execute() int {
+	transcriptBytes, err := coreio.ReadRequiredFile(s.transcriptPath, "transcript")
+	if err != nil {
+		return s.fail("input", outcomes.ReasonInternalFailure, err)
+	}
+	glossaryBytes, err := coreio.ReadRequiredFile(s.glossaryPath, "glossary")
+	if err != nil {
+		return s.fail("input", outcomes.ReasonInternalFailure, err)
+	}
+	source, err := schema.ParseSourceTranscriptJSON(transcriptBytes)
+	if err != nil {
+		return s.fail("input", outcomes.ReasonInputInvalid, err)
+	}
+	glossary, err := schema.ParseGlossaryYAML(glossaryBytes)
+	if err != nil {
+		return s.fail("input", outcomes.ReasonInputInvalid, err)
+	}
+	s.debugWrite("source transcript", func(d *diagnostics.RunDirectory) error { return d.WriteSourceTranscript(source, transcriptBytes) })
+	normalizer := normalization.NewNormalizer(normalization.NormalizationConfig{
+		MaxSegmentGap: s.cfg.Normalization.MaxSegmentGap, EllipsisGap: s.cfg.Normalization.EllipsisGap,
+		MaxSegmentDuration: s.cfg.Normalization.MaxSegmentDuration, MaxSegmentTokens: s.cfg.Normalization.MaxSegmentTokens,
+	})
+	normalized, normSummary := normalizer.Normalize(sourceToCanonicalTranscript(source))
+	s.debugWrite("normalized transcript", func(d *diagnostics.RunDirectory) error { return d.WriteNormalizedTranscript(normalized) })
+	s.debugWrite("normalization summary", func(d *diagnostics.RunDirectory) error { return d.WriteNormalizationSummary(normSummary) })
+	if err := s.ctx.Err(); err != nil {
+		return s.fail("processing", outcomes.ReasonCanceled, err)
+	}
+	observations := llm.NewObservationCollector()
+	proposalClient, err := s.runtime.NewRoleClient("proposal", observations.Hooks())
+	if err != nil {
+		return s.fail("processing", outcomes.ReasonSetupFailure, err)
+	}
+	validationClient, err := s.runtime.NewRoleClient("validation", observations.Hooks())
+	if err != nil {
+		return s.fail("processing", outcomes.ReasonSetupFailure, err)
+	}
+	factory := modules.NewFactory(modules.Dependencies{Config: &s.cfg, Glossary: glossary, DiagnosticsDir: s.debugPath()})
+	result, runErr := runner.New(factory).Run(s.ctx, runner.RunInput{
+		Config: &s.cfg, Transcript: normalized, Glossary: glossary, ModuleSpecs: s.specs,
+		ProposalLLMClient: proposalClient, ProposalDiagnosticsDir: s.debugPath(),
+		ValidationLLMClient: validationClient, ValidationDiagnosticsDir: s.debugPath(),
+		CaptureCandidates:     s.debugDir != nil,
+		ReportDiagnosticError: s.reportDiagnosticError,
+	})
+	result.Observations = observations.Snapshot()
+	result.ObservationsAvailable = true
+	result.LLMSummary = llm.Summarize(result.Observations)
+	s.runOutput = &result
+	s.writeExecutionEvidence()
+	if len(result.Sections) > 0 || runErr == nil {
+		s.writeChunkSummary(result.Sections)
+	}
+	if runErr != nil {
+		return s.fail("processing", fatalReason(s.ctx, runErr), runErr)
+	}
+	encoder, err := outputschema.Resolve(s.cfg.Output.Schema)
+	if err != nil {
+		return s.fail("encoding", outcomes.ReasonSetupFailure, err)
+	}
+	outputBytes, err := encoder.Encoder(result.FinalTranscript)
+	if err != nil {
+		return s.fail("encoding", outcomes.ReasonInternalFailure, err)
+	}
+	return s.finish(outputBytes)
+}
+
+func (s *processState) writeChunkSummary(inventory []contracts.SectionMetadata) {
+	if s.debugDir == nil {
+		return
+	}
+	sections := make([]chunking.Section, len(inventory))
+	for i, metadata := range inventory {
+		sections[i] = chunking.Section{Index: metadata.Index, StartSegmentID: metadata.StartSegmentID,
+			EndSegmentID: metadata.EndSegmentID, EstimatedTokens: metadata.EstimatedTokens,
+			Segments: make([]schema.Segment, metadata.SegmentCount)}
+	}
+	config := chunking.ChunkingConfig{TargetSections: s.cfg.Chunking.TargetSections,
+		MaxSectionTokens: s.cfg.Chunking.MaxSectionTokens, MinSectionTokens: s.cfg.Chunking.MinSectionTokens}
+	summary := chunking.ComputeDetailedSummary(sections, config)
+	s.debugWrite("chunking summary", func(d *diagnostics.RunDirectory) error { return d.WriteChunkingSummary(&summary) })
+}
+
+func (s *processState) writeExecutionEvidence() {
+	if s.debugDir == nil || s.runOutput == nil {
+		return
+	}
+	output := s.runOutput
+	s.debugWrite("model execution", func(d *diagnostics.RunDirectory) error {
+		return d.WriteJSONArtifact(diagnostics.ArtifactLLMExecution, processreport.BuildLLMExecution(output.Observations))
+	})
+	s.debugWrite("utilization", func(d *diagnostics.RunDirectory) error {
+		return d.WriteJSONArtifact(diagnostics.ArtifactUtilizationSummary, processreport.BuildUtilization(output, s.cfg.Backends))
+	})
+	s.debugWrite("correction ledger", func(d *diagnostics.RunDirectory) error {
+		return d.WriteJSONArtifact(diagnostics.ArtifactCorrectionLedger, processreport.BuildCorrectionLedger(processreport.CorrectionLedgerInput{
+			RunDirectoryPath: d.Path(), RunOutput: output}))
+	})
+}
+
+func fatalReason(ctx context.Context, err error) outcomes.ReasonCode {
+	if ctx.Err() != nil || errors.Is(err, context.Canceled) {
+		return outcomes.ReasonCanceled
+	}
+	var failure *structuredoutput.Failure
+	if errors.As(err, &failure) && failure.Reason != "" {
+		return failure.Reason
+	}
+	return outcomes.ReasonInternalFailure
+}
+
+func (s *processState) fail(phase string, reason outcomes.ReasonCode, cause error) int {
+	s.debugWrite("error log", func(d *diagnostics.RunDirectory) error {
+		return d.WriteErrorLog(phase + ": " + llm.RedactError(cause, s.cfg))
+	})
+	failures := []processreport.RunFailure{{Phase: phase, Reason: reason}}
+	completed := time.Now().UTC()
+	base, err := s.bundle(s.snapshot(reporting.StatusFailed, &completed, failures))
+	if err != nil {
+		fmt.Fprintf(s.stderr, "audita process: %s\n", llm.RedactError(err, s.cfg))
+	}
+	writeFailures := s.session.Finalize(nil, base, func(extra []diagnostics.FileFailure) diagnostics.ReportBundle {
+		all := append(append([]processreport.RunFailure(nil), failures...), mapWriteFailures(extra)...)
+		bundle, renderErr := s.bundle(s.snapshot(reporting.StatusFailed, &completed, all))
+		if renderErr != nil {
+			return base
+		}
+		return bundle
+	})
+	fmt.Fprintf(s.stderr, "audita process: %s\n", llm.RedactError(cause, s.cfg))
+	s.printFailures(writeFailures)
+	s.printDebugWarnings()
+	if s.debugDir != nil {
+		fmt.Fprintf(s.stderr, "audita process: diagnostics: %s\n", s.safePath(s.debugDir.Path()))
+	}
+	return 1
+}
+
+func (s *processState) finish(outputBytes []byte) int {
+	completed := time.Now().UTC()
+	snapshot := s.snapshot(reporting.StatusCompleted, &completed, nil)
+	complete, err := s.bundle(snapshot)
+	if err != nil {
+		return s.fail("report_write", outcomes.ReasonInternalFailure, err)
+	}
+	if s.session.TranscriptPath() == "" {
+		if _, err := s.stdout.Write(outputBytes); err != nil {
+			return s.fail("transcript_write", outcomes.ReasonInternalFailure, err)
+		}
+		outputBytes = nil
+	}
+	writeFailures := s.session.Finalize(outputBytes, complete, func(extra []diagnostics.FileFailure) diagnostics.ReportBundle {
+		failed, renderErr := s.bundle(s.snapshot(reporting.StatusFailed, &completed, mapWriteFailures(extra)))
+		if renderErr != nil {
+			return diagnostics.ReportBundle{}
+		}
+		return failed
+	})
+	if len(writeFailures) > 0 {
+		s.printFailures(writeFailures)
+		s.printDebugWarnings()
+		if s.debugDir != nil {
+			fmt.Fprintf(s.stderr, "audita process: diagnostics: %s\n", s.safePath(s.debugDir.Path()))
+		}
+		return 1
+	}
+	fmt.Fprintln(s.stderr, reporting.CompletionLine(snapshot))
+	for _, path := range s.session.ReportPaths() {
+		fmt.Fprintf(s.stderr, "Report: %s\n", s.safePath(path))
+	}
+	if s.debugDir != nil {
+		fmt.Fprintf(s.stderr, "Debug: %s\n", s.safePath(s.debugDir.Path()))
+	}
+	s.printDebugWarnings()
+	return 0
+}
+
+func mapWriteFailures(failures []diagnostics.FileFailure) []processreport.RunFailure {
+	out := make([]processreport.RunFailure, len(failures))
+	for i, failure := range failures {
+		phase := "report_write"
+		if failure.Kind == "transcript write" {
+			phase = "transcript_write"
+		}
+		out[i] = processreport.RunFailure{Phase: phase, Reason: outcomes.ReasonInternalFailure, OutputPath: failure.Path}
+	}
+	return out
+}
+
+func (s *processState) printFailures(failures []diagnostics.FileFailure) {
+	for _, failure := range failures {
+		fmt.Fprintf(s.stderr, "audita process: %s\n", llm.RedactError(failure, s.cfg))
+	}
+}
+
+func (s *processState) printDebugWarnings() {
+	s.debugMu.Lock()
+	defer s.debugMu.Unlock()
+	for _, warning := range s.debugWarnings {
+		fmt.Fprintf(s.stderr, "audita process: %s\n", warning)
+	}
+}
+
+// safePath sanitizes presentation only; filesystem destinations remain literal.
+func (s *processState) safePath(path string) string {
+	return redaction.New(llm.ConfiguredSecrets(&s.cfg)).String(path)
+}
+
+func (s *processState) reportDiagnosticError(err error) {
+	if err == nil {
+		return
+	}
+	message := "debug " + llm.RedactError(err, s.cfg)
+	s.debugMu.Lock()
+	defer s.debugMu.Unlock()
+	s.debugWarnings = append(s.debugWarnings, message)
+}

internal/cli/release_fixtures_test.go

@@ -1,469 +0,0 @@
-package cli
-
-import (
-	"bytes"
-	"encoding/json"
-	"os"
-	"path/filepath"
-	"reflect"
-	"strings"
-	"testing"
-
-	"gitea.maximumdirect.net/eric/audita/internal/core/reporting"
-	"gitea.maximumdirect.net/eric/audita/internal/core/schema"
-	"gitea.maximumdirect.net/eric/audita/internal/framework/proposal_generation"
-	"gitea.maximumdirect.net/eric/audita/internal/framework/validators"
-)
-
-type releaseFixtureExpectations struct {
-	MustApplyTexts         []string `json:"must_apply_texts"`
-	MustNotApplyTexts      []string `json:"must_not_apply_texts"`
-	ProtectedTerms         []string `json:"protected_terms"`
-	ExpectedModuleInstance []string `json:"expected_module_instances"`
-	MinimumCounts          struct {
-		Applied  int `json:"applied"`
-		Rejected int `json:"rejected"`
-		Skipped  int `json:"skipped"`
-	} `json:"minimum_counts"`
-}
-
-func TestReleaseFixtureDefaultPipelineReadiness(t *testing.T) {
-	base := fixturePath(filepath.Join("release", "default-release"))
-
-	var expectations releaseFixtureExpectations
-	if err := json.Unmarshal(readFile(t, base+".expectations.json"), &expectations); err != nil {
-		t.Fatalf("unmarshal release expectations: %v", err)
-	}
-
-	proposalResponses := readProposalResponses(t, base+".proposals.json")
-	validationResponses := readValidationResponses(t, base+".validations.json")
-
-	// First pass: default full pipeline with deterministic fake LLM responses.
-	first := runReleaseFixturePass(t, releaseRunConfig{
-		transcriptPath:         base + ".transcript.json",
-		glossaryPath:           base + ".glossary.yaml",
-		outputSchema:           "bare-segments",
-		proposalResponses:      proposalResponses,
-		validationResponses:    validationResponses,
-		expectedProposalCalls:  []string{"glossary_1:proposal", "homophones:proposal", "glossary_2:proposal", "spoken_word:proposal", "grammar:proposal"},
-		reportSchemaName:       reporting.DefaultProcessReportSchemaName,
-		reportSchemaVersion:    reporting.DefaultProcessReportSchemaVersion,
-		expectedOutputSchema:   "bare-segments",
-		expectModuleInstances:  expectations.ExpectedModuleInstance,
-		expectUtilizationPaths: true,
-	})
-
-	gotTranscript := mustReadTranscript(t, first.outputPath)
-	expectFinalTranscriptContains(t, gotTranscript, expectations.MustApplyTexts)
-	expectFinalTranscriptDoesNotContain(t, gotTranscript, expectations.MustNotApplyTexts)
-	expectFinalTranscriptContains(t, gotTranscript, expectations.ProtectedTerms)
-
-	assertReleaseCounts(t, first.report, expectations)
-	assertPromptAndSchemaMetadataPresent(t, first.runDir)
-	assertReleaseLedgerShape(t, first.report)
-	assertReleaseUtilizationShape(t, first.report)
-	assertStableValidatorKeysPresent(t, first.report)
-	assertStdoutStderrContract(t, first.stdout, first.stderr)
-	assertNoSecretMarkersInTree(t, first.runDir, []string{"release-secret"})
-	assertNoSecretMarkers(t, first.reportPath, []string{"release-secret"})
-
-	// Output schema check: audita-v1 object payload.
-	auditaV1 := runReleaseFixturePass(t, releaseRunConfig{
-		transcriptPath:         base + ".transcript.json",
-		glossaryPath:           base + ".glossary.yaml",
-		outputSchema:           "audita-v1",
-		proposalResponses:      proposalResponses,
-		validationResponses:    validationResponses,
-		expectedProposalCalls:  []string{"glossary_1:proposal", "homophones:proposal", "glossary_2:proposal", "spoken_word:proposal", "grammar:proposal"},
-		reportSchemaName:       reporting.DefaultProcessReportSchemaName,
-		reportSchemaVersion:    reporting.DefaultProcessReportSchemaVersion,
-		expectedOutputSchema:   "audita-v1",
-		expectModuleInstances:  expectations.ExpectedModuleInstance,
-		expectUtilizationPaths: true,
-	})
-	assertAuditaV1OutputShape(t, auditaV1.outputPath)
-
-	// Idempotence-oriented second pass:
-	// run again on first output with deterministic no-op responses.
-	noOpProposals := make([]proposal_generation.StructuredCorrectionSet, 5)
-	for i := range noOpProposals {
-		noOpProposals[i] = proposal_generation.StructuredCorrectionSet{Corrections: nil}
-	}
-	second := runReleaseFixturePass(t, releaseRunConfig{
-		transcriptPath:         first.outputPath,
-		glossaryPath:           base + ".glossary.yaml",
-		outputSchema:           "bare-segments",
-		proposalResponses:      noOpProposals,
-		validationResponses:    nil,
-		expectedProposalCalls:  []string{"glossary_1:proposal", "homophones:proposal", "glossary_2:proposal", "spoken_word:proposal", "grammar:proposal"},
-		reportSchemaName:       reporting.DefaultProcessReportSchemaName,
-		reportSchemaVersion:    reporting.DefaultProcessReportSchemaVersion,
-		expectedOutputSchema:   "bare-segments",
-		expectModuleInstances:  expectations.ExpectedModuleInstance,
-		expectUtilizationPaths: true,
-	})
-	firstSegments := mustReadTranscript(t, first.outputPath)
-	secondSegments := mustReadTranscript(t, second.outputPath)
-	if !reflect.DeepEqual(firstSegments, secondSegments) {
-		t.Fatalf("expected idempotent second pass transcript; first=%+v second=%+v", firstSegments, secondSegments)
-	}
-	if second.report.ModulesSummary == nil {
-		t.Fatalf("expected modules summary on second pass")
-	}
-	if second.report.ModulesSummary.TotalAppliedChanges != 0 {
-		t.Fatalf("expected no-op second pass (0 applied), got %+v", second.report.ModulesSummary)
-	}
-}
-
-type releaseRunConfig struct {
-	transcriptPath         string
-	glossaryPath           string
-	outputSchema           string
-	proposalResponses      []proposal_generation.StructuredCorrectionSet
-	validationResponses    []validators.LLMValidationResponse
-	expectedProposalCalls  []string
-	reportSchemaName       string
-	reportSchemaVersion    string
-	expectedOutputSchema   string
-	expectModuleInstances  []string
-	expectUtilizationPaths bool
-}
-
-type releaseRunResult struct {
-	stdout     string
-	stderr     string
-	outputPath string
-	reportPath string
-	report     reporting.ProcessReport
-	runDir     string
-}
-
-func runReleaseFixturePass(t *testing.T, cfg releaseRunConfig) releaseRunResult {
-	t.Helper()
-
-	processProposalLLMClient = &fakeStructuredLLMClient{proposalResponses: append([]proposal_generation.StructuredCorrectionSet(nil), cfg.proposalResponses...)}
-	processValidationLLMClient = &fakeStructuredLLMClient{validationResponses: append([]validators.LLMValidationResponse(nil), cfg.validationResponses...)}
-	t.Cleanup(func() {
-		processProposalLLMClient = nil
-		processValidationLLMClient = nil
-	})
-
-	workDir := t.TempDir()
-	reportPath := filepath.Join(t.TempDir(), "report.json")
-	outputPath := filepath.Join(t.TempDir(), "out.json")
-	configPath := writeFile(t, "release-config.yml", "version: 1\n")
-
-	args := []string{
-		"process",
-		cfg.transcriptPath,
-		"--glossary",
-		cfg.glossaryPath,
-		"--config",
-		configPath,
-		"--output",
-		outputPath,
-		"--output-schema",
-		cfg.outputSchema,
-		"--report-json",
-		reportPath,
-		"--work-dir",
-		workDir,
-		"--work-dir-retention",
-		"always",
-	}
-
-	var stdout, stderr bytes.Buffer
-	exitCode := Run(args, &stdout, &stderr)
-	if exitCode != 0 {
-		t.Fatalf("expected success, got %d stderr=%q", exitCode, stderr.String())
-	}
-
-	report := readProcessReport(t, reportPath)
-	if report.ReportMetadata.ReportSchemaName != cfg.reportSchemaName || report.ReportMetadata.ReportSchemaVersion != cfg.reportSchemaVersion {
-		t.Fatalf("unexpected report schema metadata: %+v", report.ReportMetadata)
-	}
-	if report.ReportMetadata.OutputSchema != cfg.expectedOutputSchema {
-		t.Fatalf("unexpected output schema metadata: got %q want %q", report.ReportMetadata.OutputSchema, cfg.expectedOutputSchema)
-	}
-	if len(cfg.expectModuleInstances) > 0 {
-		got := make([]string, 0, len(report.ModuleResults))
-		for _, mr := range report.ModuleResults {
-			got = append(got, mr.ModuleInstance)
-		}
-		if !reflect.DeepEqual(got, cfg.expectModuleInstances) {
-			t.Fatalf("unexpected module instances: got %v want %v", got, cfg.expectModuleInstances)
-		}
-	}
-	if report.Diagnostics == nil {
-		t.Fatalf("expected diagnostics metadata")
-	}
-	if cfg.expectUtilizationPaths {
-		if report.Diagnostics.UtilizationSummaryPath == "" || report.Diagnostics.CorrectionLedgerPath == "" {
-			t.Fatalf("expected utilization/ledger artifact paths in report diagnostics: %+v", report.Diagnostics)
-		}
-	}
-
-	runDir := onlyRunDir(t, workDir)
-	if _, err := os.Stat(filepath.Join(runDir, "report.json")); err != nil {
-		t.Fatalf("expected run-dir report: %v", err)
-	}
-
-	if c, ok := processProposalLLMClient.(*fakeStructuredLLMClient); ok {
-		if !reflect.DeepEqual(c.calls, cfg.expectedProposalCalls) {
-			t.Fatalf("unexpected proposal call order: got %v want %v", c.calls, cfg.expectedProposalCalls)
-		}
-	}
-
-	return releaseRunResult{
-		stdout:     stdout.String(),
-		stderr:     stderr.String(),
-		outputPath: outputPath,
-		reportPath: reportPath,
-		report:     report,
-		runDir:     runDir,
-	}
-}
-
-func readProposalResponses(t *testing.T, path string) []proposal_generation.StructuredCorrectionSet {
-	t.Helper()
-	var out []proposal_generation.StructuredCorrectionSet
-	if err := json.Unmarshal(readFile(t, path), &out); err != nil {
-		t.Fatalf("unmarshal proposal responses: %v", err)
-	}
-	return out
-}
-
-func readValidationResponses(t *testing.T, path string) []validators.LLMValidationResponse {
-	t.Helper()
-	var out []validators.LLMValidationResponse
-	if err := json.Unmarshal(readFile(t, path), &out); err != nil {
-		t.Fatalf("unmarshal validation responses: %v", err)
-	}
-	return out
-}
-
-func mustReadTranscript(t *testing.T, path string) []schema.Segment {
-	t.Helper()
-	transcript, err := schema.ParseTranscriptJSON(readFile(t, path))
-	if err != nil {
-		t.Fatalf("parse transcript output: %v", err)
-	}
-	return transcript.Segments
-}
-
-func expectFinalTranscriptContains(t *testing.T, segments []schema.Segment, needles []string) {
-	t.Helper()
-	joined := flattenTranscriptText(segments)
-	for _, needle := range needles {
-		if !strings.Contains(joined, needle) {
-			t.Fatalf("expected transcript to contain %q, got %q", needle, joined)
-		}
-	}
-}
-
-func expectFinalTranscriptDoesNotContain(t *testing.T, segments []schema.Segment, needles []string) {
-	t.Helper()
-	joined := flattenTranscriptText(segments)
-	for _, needle := range needles {
-		if strings.Contains(joined, needle) {
-			t.Fatalf("expected transcript to not contain %q, got %q", needle, joined)
-		}
-	}
-}
-
-func flattenTranscriptText(segments []schema.Segment) string {
-	parts := make([]string, 0, len(segments))
-	for _, s := range segments {
-		parts = append(parts, s.Text)
-	}
-	return strings.Join(parts, "\n")
-}
-
-func assertReleaseCounts(t *testing.T, report reporting.ProcessReport, exp releaseFixtureExpectations) {
-	t.Helper()
-	if report.ModulesSummary == nil {
-		t.Fatalf("expected modules_summary")
-	}
-	if report.ModulesSummary.TotalAppliedChanges < exp.MinimumCounts.Applied {
-		t.Fatalf("expected at least %d applied changes, got %+v", exp.MinimumCounts.Applied, report.ModulesSummary)
-	}
-	validatorRejected := 0
-	skipped := 0
-	for _, mr := range report.ModuleResults {
-		validatorRejected += len(mr.ValidatorRejected)
-		skipped += len(mr.SkippedChanges)
-	}
-	if validatorRejected < exp.MinimumCounts.Rejected {
-		t.Fatalf("expected at least %d validator rejections, got %d", exp.MinimumCounts.Rejected, validatorRejected)
-	}
-	if skipped < exp.MinimumCounts.Skipped {
-		t.Fatalf("expected at least %d application skips, got %d", exp.MinimumCounts.Skipped, skipped)
-	}
-}
-
-func assertReleaseUtilizationShape(t *testing.T, report reporting.ProcessReport) {
-	t.Helper()
-	var payload struct {
-		EffectiveConcurrency struct {
-			TotalLLM int `json:"total_llm"`
-		} `json:"effective_concurrency"`
-		RunTiming struct {
-			SchedulerQueueWaitMS      int64 `json:"scheduler_queue_wait_ms"`
-			LLMExecutionTimeMS        int64 `json:"llm_execution_time_ms"`
-			DeterministicValidationMS int64 `json:"deterministic_validation_time_ms"`
-		} `json:"run_timing"`
-		Modules    []map[string]any `json:"modules"`
-		Validators []map[string]any `json:"validators"`
-	}
-	if err := json.Unmarshal(readFile(t, report.Diagnostics.UtilizationSummaryPath), &payload); err != nil {
-		t.Fatalf("unmarshal utilization diagnostics: %v", err)
-	}
-	if payload.EffectiveConcurrency.TotalLLM <= 0 {
-		t.Fatalf("expected positive total llm concurrency, got %+v", payload.EffectiveConcurrency)
-	}
-	if payload.RunTiming.SchedulerQueueWaitMS < 0 || payload.RunTiming.LLMExecutionTimeMS < 0 || payload.RunTiming.DeterministicValidationMS < 0 {
-		t.Fatalf("expected non-negative run timing values, got %+v", payload.RunTiming)
-	}
-	if len(payload.Modules) == 0 {
-		t.Fatalf("expected module timing summaries")
-	}
-	if len(payload.Validators) == 0 {
-		t.Fatalf("expected validator timing summaries")
-	}
-}
-
-func assertReleaseLedgerShape(t *testing.T, report reporting.ProcessReport) {
-	t.Helper()
-	var entries []struct {
-		ModuleKey            string `json:"module_key"`
-		ModuleInstance       string `json:"module_instance"`
-		ProposalIndex        int    `json:"proposal_index"`
-		Disposition          string `json:"disposition"`
-		DispositionReason    string `json:"disposition_reason_code"`
-		OriginalText         string `json:"original_text"`
-		ProposedCorrected    string `json:"proposed_corrected_text"`
-		ReplacementPolicy    string `json:"replacement_policy"`
-		DeterministicResults []struct {
-			ValidatorKey string `json:"validator_key"`
-		} `json:"deterministic_validator_decisions"`
-		LLMResults []struct {
-			ValidatorKey string `json:"validator_key"`
-		} `json:"llm_validator_decisions"`
-	}
-	if err := json.Unmarshal(readFile(t, report.Diagnostics.CorrectionLedgerPath), &entries); err != nil {
-		t.Fatalf("unmarshal correction ledger: %v", err)
-	}
-	if len(entries) == 0 {
-		t.Fatalf("expected correction ledger entries")
-	}
-	hasApplied := false
-	hasRejected := false
-	hasSkipped := false
-	for _, entry := range entries {
-		if entry.ModuleInstance == "" || entry.ModuleKey == "" {
-			t.Fatalf("expected module identity in ledger entry: %+v", entry)
-		}
-		switch entry.Disposition {
-		case "applied":
-			hasApplied = true
-		case "rejected":
-			hasRejected = true
-		case "skipped":
-			hasSkipped = true
-		}
-	}
-	if !hasApplied || !hasRejected {
-		t.Fatalf("expected applied and rejected entries in correction ledger, got %+v", entries)
-	}
-	if !hasSkipped {
-		// Some deterministic fixture paths do not trigger apply-time skips;
-		// rejections are still captured separately from application skips.
-	}
-}
-
-func assertPromptAndSchemaMetadataPresent(t *testing.T, runDir string) {
-	t.Helper()
-	metadataPaths, err := filepath.Glob(filepath.Join(runDir, "*", "*request-metadata.json"))
-	if err != nil {
-		t.Fatalf("glob request metadata artifacts: %v", err)
-	}
-	if len(metadataPaths) == 0 {
-		t.Fatalf("expected request metadata artifacts with prompt metadata")
-	}
-
-	foundPromptMetadata := false
-	foundSchemaMetadata := false
-	for _, path := range metadataPaths {
-		var payload map[string]any
-		if err := json.Unmarshal(readFile(t, path), &payload); err != nil {
-			t.Fatalf("unmarshal request metadata artifact %q: %v", path, err)
-		}
-		if pm, ok := payload["prompt_metadata"].(map[string]any); ok {
-			if pm["prompt_id"] != nil && pm["prompt_version"] != nil && pm["sha256"] != nil {
-				foundPromptMetadata = true
-			}
-		}
-		if sm, ok := payload["response_schema"].(map[string]any); ok {
-			if sm["id"] != nil && sm["version"] != nil && sm["name"] != nil && sm["sha256"] != nil {
-				foundSchemaMetadata = true
-			}
-		}
-	}
-	if !foundPromptMetadata {
-		t.Fatalf("expected prompt metadata in request metadata artifacts")
-	}
-	if !foundSchemaMetadata {
-		t.Fatalf("expected structured response schema metadata in request metadata artifacts")
-	}
-}
-
-func assertStableValidatorKeysPresent(t *testing.T, report reporting.ProcessReport) {
-	t.Helper()
-	seen := map[string]bool{}
-	for _, module := range report.ModuleResults {
-		for _, decision := range module.ValidatorDecisions {
-			seen[decision.ValidatorName] = true
-		}
-		for _, rejected := range module.ValidatorRejected {
-			seen[rejected.ValidatorName] = true
-		}
-	}
-	expectedAny := []string{
-		"confidence_threshold",
-		"original_text_presence",
-		"no_effect",
-	}
-	for _, key := range expectedAny {
-		if !seen[key] {
-			t.Fatalf("expected stable validator key %q in report decisions/rejections; seen=%v", key, seen)
-		}
-	}
-}
-
-func assertStdoutStderrContract(t *testing.T, stdout, stderr string) {
-	t.Helper()
-	if stdout != "" {
-		t.Fatalf("expected empty stdout with --output, got %q", stdout)
-	}
-	if strings.Contains(stderr, `"module_results"`) || strings.Contains(stderr, `"report_metadata"`) {
-		t.Fatalf("stderr should remain human-readable, not report JSON: %q", stderr)
-	}
-}
-
-func assertAuditaV1OutputShape(t *testing.T, outputPath string) {
-	t.Helper()
-	var payload struct {
-		Schema   string           `json:"schema"`
-		Version  string           `json:"version"`
-		Segments []schema.Segment `json:"segments"`
-	}
-	if err := json.Unmarshal(readFile(t, outputPath), &payload); err != nil {
-		t.Fatalf("unmarshal audita-v1 output: %v", err)
-	}
-	if payload.Schema != "audita-v1" || payload.Version != "v1" {
-		t.Fatalf("unexpected audita-v1 metadata: %+v", payload)
-	}
-	if len(payload.Segments) == 0 {
-		t.Fatalf("expected non-empty audita-v1 segments")
-	}
-}

internal/cli/review_artifacts_test.go

@@ -1,46 +0,0 @@
-package cli
-
-import (
-	"testing"
-
-	"gitea.maximumdirect.net/eric/audita/internal/framework/proposals"
-	"gitea.maximumdirect.net/eric/audita/internal/framework/runner"
-)
-
-func TestBuildCorrectionLedgerClassifiesValidatorDecisionsFromCanonicalMetadata(t *testing.T) {
-	output := &runner.RunOutput{
-		ModuleResults: []runner.ModuleResult{
-			{
-				ModuleKey:         "glossary",
-				ModuleInstance:    "glossary",
-				ReplacementPolicy: proposals.ReplacementPolicyReplaceAll,
-				ValidatorDecisions: []runner.ValidatorDecisionRecord{
-					{ValidatorName: "proposal_shape", ProposalIndex: 3, Approved: true, ReasonCode: "approved"},
-					{ValidatorName: "spoken_form_plausibility", ProposalIndex: 3, Approved: true, ReasonCode: "approved"},
-				},
-				AppliedChanges: []proposals.AppliedChange{
-					{
-						ProposalIndex:   3,
-						ModuleKey:       "glossary",
-						ModuleInstance:  "glossary",
-						TargetSegmentID: 1,
-						OriginalText:    "gestures",
-						CorrectedText:   "Jesters",
-					},
-				},
-			},
-		},
-	}
-
-	ledger := buildCorrectionLedger("/tmp/audita-run-id", output)
-	if len(ledger) != 1 {
-		t.Fatalf("expected one ledger entry, got %d", len(ledger))
-	}
-	entry := ledger[0]
-	if len(entry.DeterministicValidatorResults) != 1 || entry.DeterministicValidatorResults[0].ValidatorKey != "proposal_shape" {
-		t.Fatalf("unexpected deterministic decision split: %+v", entry.DeterministicValidatorResults)
-	}
-	if len(entry.LLMValidatorResults) != 1 || entry.LLMValidatorResults[0].ValidatorKey != "spoken_form_plausibility" {
-		t.Fatalf("unexpected llm-backed decision split: %+v", entry.LLMValidatorResults)
-	}
-}

internal/cli/runtime_errors_test.go

@@ -0,0 +1,76 @@
+package cli
+
+import (
+	"bytes"
+	"context"
+	"os"
+	"path/filepath"
+	"strings"
+	"testing"
+)
+
+func writeRuntimeErrorConfig(t *testing.T, operatorDocument string) string {
+	t.Helper()
+	dir := t.TempDir()
+	profiles := filepath.Join(dir, "profiles")
+	if err := os.Mkdir(profiles, 0700); err != nil {
+		t.Fatal(err)
+	}
+	main := filepath.Join(dir, "config.yml")
+	configText := "version: 2\nprofiles_dir: profiles\nbackends:\n  offline:\n    endpoint: http://127.0.0.1:1/v1\n    credential: AUDITA_TEST_PROVIDER_KEY\nllm:\n  proposal_profile: proposal\n"
+	if err := os.WriteFile(main, []byte(configText), 0600); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(profiles, "operator.yml"), []byte(operatorDocument), 0600); err != nil {
+		t.Fatal(err)
+	}
+	return main
+}
+
+func TestConfigCommandsClassifyOperatorPromptErrorsAsInputErrors(t *testing.T) {
+	t.Setenv("AUDITA_TEST_PROVIDER_KEY", "synthetic-cli-redaction-secret")
+	definitions := map[string]string{
+		"malformed operator YAML":           "profiles:\n  proposal: [\n",
+		"invalid operator template":         "profiles:\n  proposal:\n    backend: offline\n    model: local-model\nprompts:\n  modules.grammar.proposal:\n    v1:\n      messages:\n        - role: user\n          content: '{{'\n",
+		"missing operator message resource": "profiles:\n  proposal:\n    backend: offline\n    model: local-model\nprompts:\n  modules.grammar.proposal:\n    v1:\n      messages:\n        - role: user\n          content_file: missing-instruction.md\n",
+	}
+	commands := []struct {
+		name string
+		args []string
+	}{
+		{name: "validate", args: []string{"config", "validate"}},
+		{name: "print effective", args: []string{"config", "print-effective", "--view", "profiles"}},
+	}
+	for definition, document := range definitions {
+		for _, command := range commands {
+			t.Run(definition+"/"+command.name, func(t *testing.T) {
+				main := writeRuntimeErrorConfig(t, document)
+				args := append(append([]string(nil), command.args...), "--config", main)
+				var stdout, stderr bytes.Buffer
+				if code := Run(context.Background(), args, &stdout, &stderr); code != 2 {
+					t.Fatalf("exit=%d, stdout=%q, stderr=%q", code, stdout.String(), stderr.String())
+				}
+				if strings.Contains(stderr.String(), "synthetic-cli-redaction-secret") {
+					t.Fatalf("configured secret leaked: %q", stderr.String())
+				}
+			})
+		}
+	}
+}
+
+func TestConfigCommandsKeepCallerCancellationAsRuntimeExit(t *testing.T) {
+	t.Setenv("AUDITA_TEST_PROVIDER_KEY", "synthetic-cli-redaction-secret")
+	main := writeRuntimeErrorConfig(t, "profiles:\n  proposal:\n    backend: offline\n    model: local-model\n")
+	commands := [][]string{
+		{"config", "validate", "--config", main},
+		{"config", "print-effective", "--config", main, "--view", "profiles"},
+	}
+	for _, args := range commands {
+		ctx, cancel := context.WithCancel(context.Background())
+		cancel()
+		var stdout, stderr bytes.Buffer
+		if code := Run(ctx, args, &stdout, &stderr); code != 1 {
+			t.Fatalf("args=%v exit=%d, stdout=%q, stderr=%q", args, code, stdout.String(), stderr.String())
+		}
+	}
+}

internal/cli/subprocess_test_hooks.go

@@ -1,110 +0,0 @@
-package cli
-
-import (
-	"context"
-	"errors"
-	"os"
-	"strconv"
-	"strings"
-	"sync"
-	"time"
-
-	"gitea.maximumdirect.net/eric/audita/internal/framework/contracts"
-	"gitea.maximumdirect.net/eric/audita/internal/framework/proposal_generation"
-	"gitea.maximumdirect.net/eric/audita/internal/framework/validators"
-)
-
-const (
-	subprocessTestLLMModeEnv      = "AUDITA_SUBPROCESS_TEST_LLM_MODE"
-	subprocessTestRunTimeoutMSEnv = "AUDITA_SUBPROCESS_TEST_RUN_TIMEOUT_MS"
-)
-
-// ConfigureSubprocessTestHooksFromEnv enables deterministic test-only hooks for
-// subprocess integration tests that run through the Go test binary helper path.
-func ConfigureSubprocessTestHooksFromEnv() {
-	mode := strings.TrimSpace(os.Getenv(subprocessTestLLMModeEnv))
-	timeoutMSRaw := strings.TrimSpace(os.Getenv(subprocessTestRunTimeoutMSEnv))
-	// Only activate in explicit subprocess test mode.
-	if mode == "" && timeoutMSRaw == "" {
-		return
-	}
-
-	if mode != "" {
-		client := &subprocessTestLLMClient{mode: mode}
-		processProposalLLMClient = client
-		processValidationLLMClient = client
-	}
-
-	if timeoutMSRaw == "" {
-		return
-	}
-	timeoutMS, err := strconv.Atoi(timeoutMSRaw)
-	if err != nil || timeoutMS <= 0 {
-		return
-	}
-	processRunnerContext = func() (context.Context, context.CancelFunc) {
-		return context.WithTimeout(context.Background(), time.Duration(timeoutMS)*time.Millisecond)
-	}
-}
-
-type subprocessTestLLMClient struct {
-	mode      string
-	mu        sync.Mutex
-	proposals int
-}
-
-func (c *subprocessTestLLMClient) CompleteStructured(ctx context.Context, req contracts.StructuredCompletionRequest, out any) (contracts.StructuredCompletionResponse, error) {
-	_ = req
-
-	switch c.mode {
-	case "backend_error":
-		return contracts.StructuredCompletionResponse{}, errors.New("synthetic backend failure")
-	case "block_until_cancel":
-		<-ctx.Done()
-		return contracts.StructuredCompletionResponse{}, ctx.Err()
-	case "malformed_structured":
-		switch target := out.(type) {
-		case *proposal_generation.StructuredCorrectionSet:
-			*target = proposal_generation.StructuredCorrectionSet{
-				Corrections: []proposal_generation.StructuredCorrectionProposal{
-					{TargetSegmentID: 0, OriginalText: "x", CorrectedText: "y", Confidence: 0.99},
-				},
-			}
-		case *validators.LLMValidationResponse:
-			*target = validators.LLMValidationResponse{
-				Validations: []validators.LLMValidationDecision{
-					{CorrectionIndex: 999, Approved: true, Confidence: 0.9, Reason: "bad index"},
-				},
-			}
-		}
-	case "mid_pipeline_fail":
-		if _, ok := out.(*proposal_generation.StructuredCorrectionSet); ok {
-			c.mu.Lock()
-			c.proposals++
-			proposalCall := c.proposals
-			c.mu.Unlock()
-
-			if proposalCall >= 3 {
-				return contracts.StructuredCompletionResponse{}, errors.New("synthetic mid-pipeline failure")
-			}
-		}
-		switch target := out.(type) {
-		case *proposal_generation.StructuredCorrectionSet:
-			*target = proposal_generation.StructuredCorrectionSet{
-				Corrections: []proposal_generation.StructuredCorrectionProposal{
-					{TargetSegmentID: 1, OriginalText: "Segment", CorrectedText: "Segment", Confidence: 0.99},
-				},
-			}
-		case *validators.LLMValidationResponse:
-			*target = validators.LLMValidationResponse{Validations: nil}
-		}
-	default:
-		switch target := out.(type) {
-		case *proposal_generation.StructuredCorrectionSet:
-			*target = proposal_generation.StructuredCorrectionSet{Corrections: nil}
-		case *validators.LLMValidationResponse:
-			*target = validators.LLMValidationResponse{Validations: nil}
-		}
-	}
-	return contracts.StructuredCompletionResponse{}, nil
-}

internal/cli/testdata/parity/application-skip-ambiguous.case.json

@@ -1,22 +0,0 @@
-{
-  "name": "ambiguous_match_rejected_before_application",
-  "transcript_file": "application-skip-ambiguous.transcript.json",
-  "glossary_file": "default-handoff.glossary.yaml",
-  "modules_csv": "homophones",
-  "proposal_responses_file": "application-skip-ambiguous.proposals.json",
-  "validation_responses_file": "application-skip-ambiguous.validations.json",
-  "expect": {
-    "exit_code": 0,
-    "status": "success",
-    "output_transcript_file": "application-skip-ambiguous.expected-transcript.json",
-    "module_instances": ["homophones"],
-    "module_count": 1,
-    "total_applied_changes": 0,
-    "total_skipped_changes": 1,
-    "module_applied_counts": [0],
-    "module_rejected_counts": [1],
-    "module_skip_counts": [0],
-    "validator_rejected_reason_codes": ["ambiguous_original_text"],
-    "expected_proposal_calls": ["homophones:proposal"]
-  }
-}

internal/cli/testdata/parity/application-skip-ambiguous.expected-transcript.json

@@ -1,3 +0,0 @@
-[
-  {"id":1,"speaker":"Alice","start":0,"end":1,"text":"the site near another site"}
-]

internal/cli/testdata/parity/application-skip-ambiguous.proposals.json

@@ -1,3 +0,0 @@
-[
-  {"corrections": [{"id": 1, "original_text": "site", "corrected_text": "sight", "confidence": 0.99}]}
-]

internal/cli/testdata/parity/application-skip-ambiguous.transcript.json

@@ -1,3 +0,0 @@
-[
-  {"id":1,"speaker":"Alice","start":0.0,"end":1.0,"text":"the site near another site"}
-]

internal/cli/testdata/parity/application-skip-ambiguous.validations.json

@@ -1,4 +0,0 @@
-[
-  {"validations": [{"correction_index": 0, "approved": true, "confidence": 0.99, "reason": "ok"}]},
-  {"validations": [{"correction_index": 0, "approved": true, "confidence": 0.99, "reason": "ok"}]}
-]

internal/cli/testdata/parity/default-full-pipeline.case.json

@@ -1,28 +0,0 @@
-{
-  "name": "default_full_pipeline_shape_and_reports",
-  "transcript_file": "default-full-pipeline.transcript.json",
-  "glossary_file": "default-full-pipeline.glossary.yaml",
-  "proposal_responses_file": "default-full-pipeline.proposals.json",
-  "validation_responses_file": "default-full-pipeline.validations.json",
-  "env": {
-    "AUDITA_LLM_API_KEY": "parity-secret",
-    "AUDITA_VALIDATION_LLM_API_KEY": "parity-secret"
-  },
-  "expect": {
-    "exit_code": 0,
-    "status": "success",
-    "output_transcript_file": "default-full-pipeline.expected-transcript.json",
-    "module_instances": ["glossary_1", "homophones", "glossary_2", "spoken_word", "grammar"],
-    "module_count": 5,
-    "total_applied_changes": 3,
-    "total_skipped_changes": 3,
-    "secret_markers": ["parity-secret"],
-    "expected_proposal_calls": [
-      "glossary_1:proposal",
-      "homophones:proposal",
-      "glossary_2:proposal",
-      "spoken_word:proposal",
-      "grammar:proposal"
-    ]
-  }
-}

internal/cli/testdata/parity/default-full-pipeline.expected-transcript.json

@@ -1,9 +0,0 @@
-[
-  {
-    "id": 1,
-    "speaker": "Alice",
-    "start": 0,
-    "end": 1,
-    "text": "Hello, there were Jesters hmm"
-  }
-]