docs(operating): land EverOS lead bridge v0 contract

[Fearvox]

Lands the Supervisor-PASSed EverOS Lead Bridge v0 operating contract from
DAS-2660 comment 5330f3f9-d74b-4896-a327-735be3bdfe05
as a repo-current Markdown file. Tracked in DAS-2665.

What's in this PR

• New file: docs/operating/everos-bridge-v0.md
• Content: verbatim from the Supervisor-accepted contract body — no wording edits.
• Branch: workbench/DAS-2660-everos-bridge-v0 per the contract's §3 fork-side rule.

What this PR explicitly does NOT do

• No CI workflow files, GitHub Actions, repo settings, branch protection,
  label/template setup, or skill mutation.
• No upstream EverMind-AI/EverOS mutations of any kind.
• No autopilot reactivation.

Public-safety check

No secrets, OAuth tokens, PATs, private host/IPs, SSH/tmux session names, raw
transcripts, raw screenshots, operator-only commands, or private local paths
included. UUIDs in the doc are workspace-internal identifiers already visible
to all workspace members, retained to preserve traceability per the issue's
landing guidance.

Verification

• File renders as Markdown at docs/operating/everos-bridge-v0.md.
• Diff is a pure addition (1 file changed, 129 insertions(+)).
• mention:// links in the body are MUW-platform links; on GitHub they
  render as inactive link text, which is expected for a fork-side artifact.

Refs: DAS-2665, DAS-2660, DAS-2658.

[Copilot]

Pull request overview

VERDICT: FLAG
VERDICT_SUMMARY: The PR adds the intended EverOS bridge v0 Markdown contract, but the published doc still contains pre-landing closeout text that is now stale. Next action: update or remove the closeout-only section before treating this as repo-current operating guidance.
EVIDENCE:

Changes:

• Adds docs/operating/everos-bridge-v0.md as a new operating contract.
• Documents MUW-side intake, GitHub association, closeout evidence, review handoff, and public-safety boundaries.
• Includes source/verification metadata from the original contract packet.

Finding:

• Moderate documentation issue in docs/operating/everos-bridge-v0.md: lines 117–124 still say the contract is not repo-current and instruct a future issue to commit this same file, which is no longer accurate in this PR.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Fearvox]

Capy /capy: Please run a bounded review on the current HEAD d5f52a2d398efd06555273ee8f423fd2e0293e65 only. Findings first. Focus on stale closeout tail, contract-vs-published-doc drift, public-safety wording, and any anti-LGTM reason this should stay FLAG instead of moving forward.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Fearvox]

Codex verification before merge:

• git diff --check main...HEAD PASS for the repo-landed tail fix
• branch is pushed and PR is open: workbench/DAS-2660-everos-bridge-v0 -> PR docs(operating): land EverOS lead bridge v0 contract #27
• scope check PASS: the follow-up diff only updates the stale pre-landing closeout tail in docs/operating/everos-bridge-v0.md; no workflows, settings, skills, or upstream mutations
• repo-current association PASS: the published copy now carries the actual branch / commit / PR values instead of the old pre-landing placeholders

Verdict: PASS for source review surface. External anti-LGTM remains pending; no merge claim.

[Fearvox]

Reviewer surface status update:

• The substantive stale-tail finding on this PR was addressed on-branch (d5f52a2) and replied to inline.
• Capy silence is currently explained by the MUW repo's last known disabled Git Dialogue responder posture rather than by an unhandled landing defect on this PR.
• The remaining blocker is Copilot review availability only; follow-up requests have so far produced transient unable to review responses and no new substantive findings.

Verdict: FLAG until Copilot produces either a fresh finding or an explicit clean pass.