docs: clarify receipt chain state and review roles

[aDragon0707]

Summary

This PR turns a recent real multi-window SACP usage friction into docs-only guidance and a public-safe corpus receipt.

It clarifies that long-running Receipt Chain handoffs should not overload one status label like latest_stable_commit when a workflow needs to distinguish:

• current workspace/head state
• latest verified content commit
• latest verified handoff/state commit
• formal external review authority vs coordinator-local preflight

The goal is to make the example sharper before making the protocol bigger.

Changes

• Add a Role And State Clarity section to SACP_RECEIPT_CHAIN.md with bad/better handoff examples.
• Add an ergonomics note to PROTOCOL_EVOLUTION.md encouraging sharper examples before new core fields.
• Add public-safe sample corpus feedback note 034_receipt_chain_state_role_feedback.
• Add translated SACP receipt for the same feedback case.

Why

In a real coordinator/reviewer workflow, SACP helped reduce context drift and made handoff state easier to audit. The remaining friction was not that SACP needed a new core field immediately. It was that the docs needed a more vivid example for state labels and review authority.

Validation

• python validator.py --examples --strict
• python validator.py sample-corpus\translated-receipts\034_receipt_chain_state_role_feedback.yaml --strict
• PowerShell corpus validation: python validator.py @files --strict
• python -m py_compile validator.py agentops-doctor\multi_model_dirty_run.py sample-corpus\collect_dirty_outputs.py agentops-doctor-skill\agentops_doctor.py
• git diff --check