Add product-owned CENTRAL operational reset

docs/development/ENGINEERING_PLATFORM_ROADMAP.md

@@ -461,6 +461,32 @@ Not required unless the canary proves otherwise: generalized Agent separation; m
 
 After standalone + self-development proofs, continue separately with generalized Project-Agent separation/dispatch, multi-host routing, richer queue policy/capacity/ordering, multi-repository leases/parallelism, broader recovery/retry and remaining B8E parity/productization.
 
+## Bounded clean-CENTRAL preparation
+
+`EP::CENTRAL_OPERATIONAL_RESET_V1` is the small product-owned maintenance
+slice needed before a later clean-state Mission preflight. It preserves
+installation/configuration/security authority, archives and removes only
+schema-classified operational history, advances dataset generation, retains
+anti-replay tombstones and uses a verified protected backup plus durable
+writer fence. Its implementation does not require the full Operations Console,
+generalized Project-Agent topology, universal installer or Workspace UI.
+
+The lane is:
+
+```text
+schema-68 implementation + fixture qualification
+  -> protected review/full EP gates
+  -> 2.3.81 exact-artifact release and authorized installation
+  -> installed read-only preview
+  -> later explicit coordinated Forge+EP clean-CENTRAL preflight
+```
+
+Source implementation, qualification, release, installation, preview and
+destructive apply remain distinct evidence states. The present slice must not
+turn an unstarted Mission/telemetry trial into a reported runtime failure and
+does not reopen the closed #271/#272 reporting/telemetry work without a new
+defect.
+
 ## Forge integration after standalone/self-development proof
 
 ```text

docs/engineering/EP_SERVER_PRODUCTION_RELEASE.md

@@ -9,6 +9,14 @@ the exclusive source of a published version change.
 Any historic branch-create workflow remains evidence for prior releases only.
 It is not authority to publish, re-publish, or rewrite EP release bytes.
 
+The 2.3.81 patch candidate adds schema-68 CENTRAL operational-reset support.
+Its release uses this unchanged protected main-first policy. Schema activation
+may retarget chat evidence to its canonical run parent and install dormant
+maintenance controls; neither publication nor installation authorizes
+`prepare`/`apply`, orphan deletion, submission creation or a Mission. Exact
+artifact qualification and an installed read-only preview are required before
+the capability can be reported installed.
+
 ## Release-operation lifecycle V1
 
 After both the production-wheel and dashboard qualifications succeed, the

docs/engineering/EXECUTION_HOST_OPERATIONS.md

@@ -458,3 +458,12 @@ creating an autonomous retry loop.
 
 Neither control rewrites history, stashes work, or deletes a branch without
 the explicit second confirmation.
+
+## CENTRAL operational-history maintenance
+
+The product-owned local reset route, exact preservation/purge mapping,
+protected backup protocol and stopped-Server command sequence are specified in
+[EP CENTRAL operational reset V1](EP_CENTRAL_OPERATIONAL_RESET_V1.md). The
+installed entry point is `engineering-platform-maintenance`; preview is
+read-only, while prepare activates a durable writer fence and apply is
+destructive. Normal Server startup and package installation never invoke it.

package.json

@@ -1,7 +1,7 @@
 {
   "name": "engineering-platform-browser-validation",
   "private": true,
-  "version": "2.3.80",
+  "version": "2.3.81",
   "scripts": {
     "test:engineering-dashboard": "PYTHONPATH=src python3 -m engineering_platform.dashboard_browser_validation",
     "test:engineering-dashboard-logic": "node --test tests/engineering/dashboard_status_store.test.mjs tests/engineering/ui_localization_contract.test.mjs tests/engineering/dashboard_translation.test.mjs",

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "engineering-platform"
-version = "2.3.80"
+version = "2.3.81"
 description = "Local-first Engineering Platform execution operations runtime"
 readme = "README.md"
 requires-python = ">=3.14,<3.15"
@@ -19,6 +19,7 @@ engineering-platform-server = "engineering_platform.server:main"
 engineering-platform = "engineering_platform.submission_cli:main"
 engineering-project-agent = "engineering_platform.project_agent:main"
 engineering-reconciliation-adopt = "engineering_platform.reconciliation_adoption:main"
+engineering-platform-maintenance = "engineering_platform.central_operational_reset:main"
 
 [tool.setuptools]
 package-dir = {"" = "src"}

src/engineering_platform/ENGINEERING_PLATFORM_CONFIG.json

@@ -3,7 +3,7 @@
   "platform": {
     "id": "engineering-platform",
     "name": "Engineering Platform",
-    "version": "2.3.80",
+    "version": "2.3.81",
     "generation": 2,
     "documentation_namespace": "engineering-platform",
     "capability_registry_version": 1

src/engineering_platform/ENGINEERING_PLATFORM_VERSION.json

@@ -1,15 +1,15 @@
 {
   "bootstrap_contract": "2026.12",
   "checkpoint_format": 1,
-  "dashboard_version": "2.3.80",
+  "dashboard_version": "2.3.81",
   "handoff_protocol": 1,
   "memory_format": 2,
   "minimum_codex_cli": "0.146.0",
   "inbox_protocol": 1,
-  "platform_version": "2.3.80",
+  "platform_version": "2.3.81",
   "report_format": 2,
-  "runner_version": "2.3.80",
+  "runner_version": "2.3.81",
   "status_model": 1,
   "storage_schema": 45,
-  "watcher_version": "2.3.80"
+  "watcher_version": "2.3.81"
 }