Add the managed documentation-update process #163

Target

Implement this ticket in lastobelus/lastCode after the docs capture and validation commands exist.

Acceptance

• Run the docs update as a sibling of the checkpoint process. A docs failure must not block or roll back a checkpoint, build, or promotion.
• Use one guarded docs checkout, one durable docs thread, one fixed branch, and one open pull request.
• Send the exact LastCode commit range, affected feature IDs, and bounded changed paths to the docs thread.
• Coalesce a change that arrives during active work into a later turn.
• Verify the pull-request branch freshness record before reporting completion.
• Keep only active request, wait correlation, and incident-delivery data locally.
• Test a no-op range, a relevant range, an overlapping arrival, an agent failure, and a docs-validation failure.
• Commit no machine names, checkout paths, thread IDs, schedules, or private endpoints.

Only one machine runs this process. Start with one owner and one pending-update slot. If implementation or PR review keeps finding coordination bugs, remove automatic overlap handling or serialize the step before adding locks, queues, leases, or distributed state.