revert: the remote optimize RFC, which merged before its review closed

docs/rfcs/0011-cli-addressing-and-config.md

@@ -7,7 +7,7 @@ implementation: complete
 authors:
   - OmniGraph maintainers
 created: 2026-06-14
-updated: 2026-10-29
+updated: 2026-10-20
 discussion: null
 supersedes: ["0010"]
 superseded_by: []
@@ -790,11 +790,3 @@ duplicated here.
 - 2026-10-05: `schema apply` is direct-only; the unused served schema-apply
   route is removed. Served changes use cluster deployment. Decision 10 and
   the capability taxonomy now reflect that boundary.
-
-- 2026-10-29: Pending amendment. [Remote optimize through the serving
-  owner](2026-10-29-remote-optimize-through-the-serving-owner.md), a draft, executes a served root's
-  `optimize` in the serving owner rather than an out-of-band worker. Once it
-  is accepted, Decision 11's "Runs out-of-band … never inline in serving"
-  gives way for `optimize` only; `cleanup` and `repair` are unchanged, and the
-  worker remains the later offload shape. Decision 11 stands unchanged until
-  acceptance.

docs/rfcs/2026-09-29-server-runtime-and-online-deployment.md

@@ -7,7 +7,7 @@ implementation: in-progress
 authors:
   - OmniGraph maintainers
 created: 2026-09-29
-updated: 2026-10-29
+updated: 2026-10-20
 discussion: https://github.com/ModernRelay/omnigraph/pull/799
 supersedes:
   - "0034"
@@ -1655,12 +1655,3 @@ Before enabling an affected increment, its owners must implement and qualify:
   The [HTTP admission decision](2026-09-30-v012-http-admission.md) owns the
   discriminator change and refusal rules; historical decision-log entries retain
   their original release scope. No storage-format change follows from the wire bump.
-
-- 2026-10-29: Pending amendment. [Remote optimize through the serving
-  owner](2026-10-29-remote-optimize-through-the-serving-owner.md), a draft, adds one bounded durable
-  record for maintenance operations, `__cluster/maintenance.json`, written
-  only by the lock holder. Once it is accepted, it supersedes the sentence "No
-  job queue, background poller or second durable operation record is
-  introduced." for maintenance operations only: one durable record is added,
-  but no job queue or background poller. The sentence still holds for
-  deployment. The body stands unchanged until acceptance.

docs/rfcs/2026-10-16-graph-access-serving-and-cross-process-writes.md

@@ -7,7 +7,7 @@ implementation: in-progress
 authors:
   - ragnorc
 created: 2026-10-16
-updated: 2026-10-29
+updated: 2026-10-25
 discussion: https://github.com/ModernRelay/omnigraph/pull/1017
 supersedes: []
 superseded_by: []
@@ -1596,12 +1596,3 @@ proposal.
   credentials" for that case only: the rule stays in force for self-hosted
   OIDC servers and every other client, and the launcher's refusal of a managed
   target (the target table and Opening Studio) is unchanged.
-
-- 2026-10-29: Pending amendment. [Remote optimize through the serving
-  owner](2026-10-29-remote-optimize-through-the-serving-owner.md), a draft, runs a served
-  cluster root's `optimize` in the process that holds the cluster lock,
-  through graph-scoped routes with a durable operation record. Once it is
-  accepted, `optimize` leaves the "Runs where the storage is" row of the
-  exception table for served cluster roots and stays there for direct
-  targets. The other commands in that row are unchanged. The table stands
-  unchanged until acceptance.