Finish this task with an evidence-backed contribution to the configured private brain.
Respect this source repository's instructions and checkout owner; preserve others' edits.
Read the brain index and relevant pages using bounded query/read/map calls, recording the
brain revision, retrieval time and any access/freshness limits. Use original code contracts
and the work tracker for their subjects. Do not rewrite shared company pages as a side
effect of application work.

At a meaningful milestone, create a v2 draft with python -m librarian update draft.
Complete actual author/session/machine identity and observed time. Describe what changed,
why it matters, repository/module, exact changed paths, before/after behavior and evidence
for each path. Include the base/change revisions, actual commits and PRs if present,
acceptance criteria, tests and real results. Distinguish implementation, test, merge,
deployment and client qualification. For a decision, name its maker and authority evidence;
an unapproved proposal stays proposed. Do not invent missing IDs, tests or outcomes.

Run update lint and update submit with --source-checkout for code changes, following the
installed help and docs/CLI-AUDIT.md. A generated draft must be completed before submission.
Redact secrets/customer material; references must be accessible to the intended reviewer.
Preserve existing v1 history and exact retries. Changed content requires a new event ID
and a correction/supersession reference. Share through the authorized private repository.

Hand off the event ID, source repository/revisions/PR, verification result, persistence
state (local/pushed/merged), pending decisions and exact evidence still needed. Local intake
is not shared delivery. If no material company fact changed, say so. The librarian records
operator/run-attributed receipts and drafts page changes within its configured authority.