Proposed additions to the openstack-cloud-ops skill (GATED: apply in audit

Phase 5, reconciled against the RATIFIED GA-R text, not this draft)

Add one section. Keep it under ~35 lines in the skill -- the skill is itself record surface, and every session pays its length.

Record authority and session discipline (GA rulings)

docs/CURRENT-STATE.md is the ONLY status authority. Stage, applied-vs- authored, gates, plan counts, version pins live THERE and nowhere else. Never hand-write a status claim in any other document; point at CURRENT-STATE.md. Update it in the same commit as the change that alters status.
Plan counts and versions are quoted only from captured command output (a committed plan capture, a --version capture) -- never from memory, never from another document's prose.
Changelogs are session-scoped scratch. They are consolidated per-stage at stage close and are NEVER citable as status or decision authority. If a changelog and CURRENT-STATE.md disagree, the changelog is wrong by definition.
One ruling per operator exchange. A decision's ADOPTED status line must quote the exact operator utterance that ruled it. Never batch-adopt. Never adopt from an inferred or reconstructed ruling -- an operator ruling is a value under hard rule 2: if it would be inferred, STOP and ask the A/B question in one line.
D-number admission bar: a D-number requires architectural consequence beyond one stage, OR a Roosevelt-delta implication, OR supersession of an existing D. Tool options, service settings, plugin lists, and process notes get a changelog line or a runbook edit, not a D-number.
Session bookends. OPEN: read CURRENT-STATE.md in full before any other doc. CLOSE: write a ledger summary of at most 15 lines; commit and push; a session that ends without its bookend is treated as NOT durable by the next session.
Reconciliation circuit-breaker. If you have been reconciling records -- fixing docs to match docs -- for more than one cycle without touching the actual deliverable, STOP and report to the operator. Record-churn presenting as progress is this project's known failure mode; escalating it is the correct move, not continuing.