* ADD: requirement of change-runbooks
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD: specification of change-runbooks
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD: plan of change-runbooks
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD: runbook guide with seven runbooks and the material test
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD: stopped-change and reversal rules, and coordinator runbook rows
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD: specification amendment of change-runbooks (renumber resolves the version record conflict)
A replay in a disposable clone showed that a moved protected branch always conflicts in the version record when another change of the artifact merged first; the runbook stopped on that conflict.
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD: renumber resolves the version record conflict; after-merge stops worktree processes
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD 3.1.0: version record and validation evidence of change-runbooks
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD: large tier and impact reconciliation of change-runbooks
The change amends specifications/knowledge-layout.md, which Artifact Plane references; the eight reached flows keep their steps.
Co-Authored-By: Claude <noreply@anthropic.com>
* ADD: PR evidence of change-runbooks
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>