[ericksondelacruz]

Summary

This PR adds the rationale for OBS-009..012, the agent-reliability-otel-labels correctness rules.

LC-116 landed on main separately, so this branch no longer carries the LC-116 doc or the index regeneration. It is rebased on the latest main and changes one file.

Changes

• OBS-009..012 (docs/Policy/observability/quality.md). Each rule gets a defense block with front-matter matching the shipped YAML:
  • OBS-009: a shared Run. Medium, 0.6.
  • OBS-010: a tool span labelled only on success. Low, 0.55.
  • OBS-011: a constant attempt. Low, 0.7.
  • OBS-012: a run end recorded only on success. Low, 0.55.

Checks

• check_links.py: OK.
• check_rulebook.py --strict against rules main with the feat/otel-labels-correctness rules commit applied: 42 errors, none naming an OBS rule. All 42 are the existing backlog of rules with no rationale doc, which this PR doesn't address.
• Against rules main alone, the gate also reports OBS-009..012 as documented but not in the pack, until the rules PR lands.

Merge order

1. Publish agent-reliability-otel-labels 0.1.1: the 0.1.0 README example trips OBS-009..012.
2. Merge the rules PR (Add OBS-009..012 for agent-reliability-otel-labels label correctness agent-reliability-rules#184). It needs rebasing on rules main first.
3. Regenerate the index (python tools/gen_index.py) here, then merge this PR with the engine PR.

🤖 Generated with Claude Code

[ivanpaghubasan]

Hi @ericksondelacruz, a heads-up on this one: LC-116 landed on main while this PR was open, and I added it to agent_safety.md. The LC-116 and POLICY_INDEX commits now conflict with main.

Could you drop those two commits and rebase on the latest main?

The OBS-009..012 docs can wait for the rules PR to merge. After that, we can regenerate the index and land the docs.