doc-exec-log-append

You can append execution logs without reading history by using an append-only template that writes facts directly to the target log file's end. This prevents context pollution while maintaining traceability across batch tasks.

Maintaining an audit trail without context pollution requires an append-only execution log mechanism. By default, it avoids reading previous content during the append action, keeping the context clean and independent across tasks.

Batch logging execution facts involves supplying the required log file path and batch metadata to an append-only template. The system validates required fields and appends self-contained records to the target file in one operation.

Yes, you can automatically create a log file template if the target file does not exist. When triggered to append execution facts, the script initializes a centralized log with a standard header template before adding the first record.

Required fields for an append-only execution log record include target, code changes, validation commands, artifacts, results, and mainline mapping. The system validates these self-contained fields before appending to ensure complete traceability.