feat: add edf to docs

[chasingrainbows]

Please, go through these steps before you request a review:

📝 Describe your changes

1. EDF manual added
2. EDF security policy added

🔎 Attach a source of truth or evidence that allows reviewers to confirm the changes independently

• LIP-37: Execution Delegation Framework — the proposal
• execution-delegation-framework — the contracts, architecture, usage guide

[Copilot]

Pull request overview

Adds new Execution Delegation Framework (EDF) operator documentation to the guides section, covering setup, key custody requirements, and rotation/incident procedures.

Changes:

• Adds an “Execution Delegation Framework” category to the Guides sidebar.
• Introduces an EDF Operator Guide covering multisig setup, DelegationContract deployment/verification, monitoring, and Oracle/Council daemon configuration.
• Adds EDF rotation/incident runbook and a draft operator key-custody policy.

Reviewed changes

Copilot reviewed 4 out of 14 changed files in this pull request and generated 3 comments.

File	Description
sidebars.js	Adds an EDF guides category and links the new EDF docs into navigation.
docs/guides/edf/edf-operator-guide.md	New end-to-end operator setup guide for EDF (multisig, deployment, monitoring, daemon config).
docs/guides/edf/edf-rotation-and-incidents.md	New runbook for routine rotations and emergency revocation/termination.
docs/guides/edf/key-custody-policy-for-edf-operators.md	New draft key custody policy for EDF owner/delegate keys, rotation cadence, and incident response.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 14 changed files in this pull request and generated no new comments.

Suppressed comments (1)

docs/guides/edf/key-custody-policy-for-edf-operators.md:112

• The initial-migration key described here contradicts the setup guide: edf-operator-guide.md:81-83 requires a fresh delegate, and its deployment/configuration steps use that new key while retaining the existing seat EOA only until governance cutover. Calling the existing EOA the initial delegate could lead operators to deploy with the key this policy says not to reuse.

This section applies to delegate rotations after the EDF migration is complete. During the initial migration, the existing hot EOA is configured as the initial delegate and is effective immediately; the governance action reassigning the seat from that EOA to its `DelegationContract` is the migration cutover.