fulcra-agent-roles

# Fulcra Agent Roles Enhances the [`fulcra-agent-teams`](https://github.com/fulcradynamics/agent-skills) skill. A team's `member/<agent>/role.md` says what a *member* does, but teams has no notion of a **durable role** that outlives any one session — "who is the reviewer right now?", "is anyone on-call?", "this role has been unattended too long." This skill adds that, as a pure OKF-markdown convention over the team namespace (lease mechanics via `coord-engine roles` verbs; everything else plain `fulcra-api file` + the OKF standard). ## Where to start — the re-entrancy probes Before claiming, escalating, or reading a role's status, probe where this role stands. Enter at the **first probe that fails** (per the repo's skill-quality pattern, `docs/skill-quality-pattern.md`); `roles claim` is a refresh, so re-entry is always safe: | Probe (run in order) | Command | Passes when | If it fails, enter at | |---|---|---|---| | Role doc registered? | `fulcra-api file download team/<team>/roles/<role>.md -` | prints a doc with `type: Role` (NON-mutating — do not probe registration via `roles claim`: claiming writes your lease before you've read the prior one, destroying same-id takeover evidence per "Role-as-identity" below) | **Establish a role** — write `roles/<role>.md` (`type: Role` + policy/SLA/maintainer) | | Lease held by you? | `coord-engine roles status <team> <role>` | prints `role <role> in team/<team>: HELD` and your agent id is among the `fresh holders:` line | **Claim /...