Module commit_conclusion 

The conclusion of a settled commit transaction: preparation, landing and post-landing completion. What: The conclusion of a settled commit transaction: the normalization-only landing when the corrections removed every change, otherwise the hook dispatcher, native preparation in the shadow, the prepared record, the landing loop and the post-landing completion. Why: The incumbent’s commit-transaction-conclusion.ts runs these steps in this order: the tree is written from the stable private index, the dispatcher shim is shared by preparation and the post-landing post-commit, the prepared record is durable before the preparation marker, and the transaction directory is removed only after the worktree copies are installed.

In TS you’d write (pseudocode):

return await concludeCommitTransaction(settled);

Structs

ConclusionInput

What: Everything the conclusion reads from the settled transaction. Why: The steps share the workspace, the capture, the policies’ settled pass and the selection facts.

Functions

conclude_commit_transaction

What: Complete a settled policy pass through a landed commit or a normalization-only reconciliation. Why: This is the incumbent’s concludeCommitTransaction.

events_with_changed_summary

What: The settled pass’s events with the fix summary the corrections earned. Why: The summary appears only after some pass changed candidate bytes, naming each changed path once in byte order.

events_with_summary

What: The events with a fix summary appended whatever the pass count. Why: A normalization that removed every change always reports its summary.