Require an explicit transcript destination for quiet processing

This commit is contained in:
2026-11-08 14:31:44 +00:00
parent 68e16f6aac
commit 9dba2d506a
2 changed files with 76 additions and 55 deletions

View File

@@ -103,9 +103,10 @@ an ordinary compatibility review, not an assumption that later releases are
interchangeable.
**CommandKit release gate:** adoption implementation waits for a published core
version providing the independent shared debug binding required by the
[CommandKit outline](commandkit.md#adoption-gate-released-shared-debug-binding).
The resolved-mode accessor alone is insufficient. Replace the reviewed v0.5.0
version providing both the independent shared debug binding for capture and the
resolved reporting-mode accessor for quiet destination validation, as required by
the [CommandKit outline](commandkit.md#adoption-gate-released-debug-binding-and-reporting-mode-access).
Either API alone is insufficient. Replace the reviewed v0.5.0
core target with that release and record compatible released integration versions
and exact source revisions after review. No replacement version is selected yet.
@@ -144,7 +145,7 @@ for Audita's complete release workflow.
Identify and remove local code made redundant by the adopted facilities as
part of each migration, rather than leaving cleanup as an unspecified follow-up.
4. **After the CommandKit release gate opens, integrate core and both standard
integrations.** Confirm the required shared debug binding is published and
integrations.** Confirm both required public APIs are published and
select the released dependency set as described above before starting this
implementation stage. Complete the previously designed operator interface,
adapting Audita domain handlers and resolving upstream issues. Earlier design