Remove the Editor deployment admin page at /processor/editor (#7859)

## Description of Changes

Removes the `/processor/editor` **Editor deployment** admin page and the
one button that navigated to it.

The page (`EditorAdmin`) covered deployment targets, instance pairing,
instance health, service-token rotation and offline activation. It was
mock-only — there is no backend behind `GET /v1/editor/deployment`; it
is served solely by MSW. It was reachable from exactly one place: a
**Manage Editor deployment** button in the Infrastructure page header.
It was never in the sidebar, search, or onboarding.

### Removed

- `portal/views/EditorAdmin.tsx` + `EditorAdmin.css`
- All of `portal/components/editor-admin/` — 6 components and their 6
co-located stories
- The route in `portal/ViewRouter.tsx`, and the `"editor"` member of
`ViewId` / `VIEW_PATHS` in `portal/contexts/ViewContext.tsx`
- The **Manage Editor deployment** button in
`portal/views/Infrastructure.tsx`, plus its now-unused `Button` /
`useView` imports
- The 15 `[portal.editorAdmin.*]` tables and
`portal.infrastructure.manageEditorDeployment` from **en-US only** (the
other 41 locales are rebuilt from the reference by the sync workflow)
- The presentation-only constants in `portal/api/editorDeploy.ts`
(`TARGET_META`, `INSTANCE_STATUS_TONE`, `INSTANCE_STATUS_LABEL`,
`TargetMeta`) that had no consumer left and pointed at the deleted i18n
keys, and the matching `ignoredKeyPatterns` entry in
`core/i18n/translationAudit.ts`

With the route gone, `/processor/editor` falls through the portal's
existing catch-all to Home.

### Deliberately kept

`portal/api/editorDeploy.ts`, `useEditorDeployment`, and the MSW mocks
stay. `portal/components/EditorStatusCard.tsx` — the **PDF Editor**
deployment rail on the portal Home hero — still reads them. An in-code
comment claiming onboarding was a third consumer was wrong and has been
corrected.

The mock-only `targets` / `pairings` fields of
`EditorDeploymentResponse` also have no reader now, but reshaping a
documented endpoint contract is a separate decision from removing a
page, so they are left alone here.

## Verification

Ran the app against a live backend and drove the portal with Playwright:

- `/processor/editor` lands on the portal Home with none of the old copy
- Infrastructure renders with no **Manage Editor deployment** button
- The Home hero **PDF Editor** rail still renders — the shared data
layer survived

`task fix` and `task check` both pass: backend spotless + tests,
frontend typecheck (proprietary/saas/portal/storybook/core), oxlint at
`--max-warnings=0`, theme-lint, stylelint, oxfmt, 350 frontend test
files, engine pyright + ruff + 430 tests. Both translation gates are
green, which confirms the en-US key removal was exactly complete — no
orphans, nothing still referenced.

## Checklist

- [x] I have read the [Contribution
Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md)
- [x] My changes generate no new warnings

Author: Frooodle

frontend/editor/public/locales/en-US/translation.toml

@@ -8032,86 +8032,6 @@ status = "Status"
 time = "Time"
 user = "User"
 
-[portal.editorAdmin]
-subtitle = "Deploy the Stirling PDF Editor, pair self-hosted instances to your org, and operate the running fleet — targets, health, credentials, and offline activation in one place."
-title = "Editor deployment"
-
-[portal.editorAdmin.health.columns]
-activeUsers = "Active users"
-host = "Host"
-lastSeen = "Last seen"
-region = "Region"
-status = "Status"
-target = "Target"
-version = "Version"
-
-[portal.editorAdmin.health.empty]
-description = "Deploy a target and pair it to see live instance health here."
-title = "No instances reporting"
-
-[portal.editorAdmin.offlineActivation]
-enterpriseTag = "Enterprise"
-generateButton = "Generate offline bundle"
-lockCopy = "Offline and on-prem activation is part of Enterprise."
-subtitle = "Generate a signed activation bundle for an offline or on-prem install with no outbound network path. Transfer it to the instance and apply it during first-run setup."
-talkToSales = "Talk to sales"
-title = "Air-gapped activation"
-
-[portal.editorAdmin.offlineActivation.readyBanner]
-description = "{{file}} is signed and ready to transfer. It activates one instance and expires in 14 days."
-title = "Bundle ready"
-
-[portal.editorAdmin.pairing]
-generated = "Generated ✓"
-generateNewCode = "Generate new code"
-lockCopy = "IaC provisioning is part of Enterprise."
-rotate = "Rotate"
-talkToSales = "Talk to sales"
-
-[portal.editorAdmin.sections.health]
-sub = "Every Editor instance reporting in — version, region, status, last seen, and active users."
-title = "Instance health"
-
-[portal.editorAdmin.sections.pairing]
-sub = "Connect a self-hosted editor to this org. Generate a token, hand off a short code, or wire it through IaC."
-title = "Pairing"
-
-[portal.editorAdmin.sections.targets]
-sub = "Where the Editor runs. Copy a snippet to stand up a self-hosted instance, or use Managed Cloud with no ops."
-title = "Deployment targets"
-
-[portal.editorAdmin.serviceToken]
-currentToken = "Current token"
-lastRotated = "Last rotated"
-rotateButton = "Rotate service token"
-subtitle = "Instances authenticate to the org with this credential. Rotate it on a schedule or immediately after a suspected leak."
-title = "Service token"
-
-[portal.editorAdmin.serviceToken.rotatedBanner]
-description = "A new token was issued. Update each self-hosted instance's STIRLING_SERVICE_TOKEN within the 24h grace window or they'll drop offline."
-title = "Rotate running instances"
-
-[portal.editorAdmin.status]
-degraded = "Degraded"
-healthy = "Healthy"
-offline = "Offline"
-pairing = "Pairing"
-
-[portal.editorAdmin.targets]
-instanceCount_one = "{{count}} instance"
-instanceCount_other = "{{count}} instances"
-talkToSales = "Talk to sales"
-upgradePlan = "Upgrade plan"
-
-[portal.editorAdmin.targets.lock]
-enterprise = "On-prem and Kubernetes self-hosting are part of Enterprise."
-paid = "Self-hosting with Docker and Kubernetes unlocks on a paid plan."
-
-[portal.editorAdmin.targets.state]
-available = "Available"
-locked = "Locked"
-running = "Running"
-
 [portal.errorBoundary]
 description = "This view hit an unexpected error. Try again, or pick another section from the sidebar."
 retry = "Try again"
@@ -8249,7 +8169,6 @@ evening = "Good evening"
 morning = "Good morning"
 
 [portal.infrastructure]
-manageEditorDeployment = "Manage Editor deployment"
 sectionsAriaLabel = "Infrastructure sections"
 subtitle = "API credentials and the audit trail for your Stirling workspace."
 title = "Infrastructure"

frontend/editor/src/core/i18n/translationAudit.ts

@@ -98,7 +98,6 @@ export const I18N_PROJECTS: TranslationProject[] = [
       // (label maps, role/policy/journey catalogues) and rendered via
       // t(constant), invisible to the static scan.
       /^portal\.documents\.(status|audit)\./,
-      /^portal\.editorAdmin\.status\./,
       /^portal\.components\.(maturity|billingUnit)\./,
       /^portal\.home\.(pipelineTemplates|pipelineStages)\./,
       /^portal\.procurement\.journeySteps\./,

frontend/editor/src/portal-saas/views/Infrastructure.test.tsx

@@ -29,12 +29,9 @@ describe("Infrastructure (SaaS)", () => {
     enterprise.loading = false;
   });
 
-  it("defaults to the live API keys tab and drops the manage-editor button", () => {
+  it("defaults to the live API keys tab", () => {
     render(<Infrastructure />);
     expect(screen.getByTestId("api-keys-tab")).toBeInTheDocument();
-    expect(
-      screen.queryByText("portal.infrastructure.manageEditorDeployment"),
-    ).not.toBeInTheDocument();
   });
 
   it("renders the not-yet-shipped tabs as disabled 'coming soon'", () => {

frontend/editor/src/portal-saas/views/Infrastructure.tsx

@@ -8,8 +8,7 @@ import "@portal/views/Infrastructure.css";
 
 // SaaS pre-release: only API keys + Audit are shipped. Deployments, Security,
 // Models and Storage are shown as disabled "coming soon" tabs (greyed, to the
-// right of the live ones), and the self-hosted-only "Manage editor deployment"
-// header button is dropped. Selection is never one of the coming-soon keys — the
+// right of the live ones). Selection is never one of the coming-soon keys — the
 // Tabs primitive renders them as native-disabled buttons, so onChange can't fire.
 type InfraTab =
   | "api-keys"

frontend/editor/src/portal/ViewRouter.tsx

@@ -7,7 +7,6 @@ import { Pipelines } from "@portal/views/Pipelines";
 import { PipelineBuilder } from "@portal/views/PipelineBuilder";
 import { Sources } from "@portal/views/Sources";
 import { Integrations } from "@portal/views/Integrations";
-import { EditorAdmin } from "@portal/views/EditorAdmin";
 import { Infrastructure } from "@portal/views/Infrastructure";
 import { PortalBillingGate } from "@portal/components/billing/PortalBillingGate";
 import { ConnectGuardedRoute } from "@portal/components/account-link/ConnectGuardedRoute";
@@ -79,7 +78,6 @@ export function ViewRouter() {
           path working, preserving its query (e.g. onboarding's ?setup=<category>). */}
       <Route path={rel(VIEW_PATHS.policies)} element={<PoliciesRedirect />} />
       <Route path={rel(VIEW_PATHS.documents)} element={<Documents />} />
-      <Route path={rel(VIEW_PATHS.editor)} element={<EditorAdmin />} />
       <Route
         path={rel(VIEW_PATHS.infrastructure)}
         element={<Infrastructure />}

frontend/editor/src/portal/api/editorDeploy.ts

@@ -114,38 +114,6 @@ export interface EditorDeploymentResponse {
   instances: EditorInstance[];
 }
 
-/* ──────────────────────────────────────────────────────────────────────── */
-/*  Presentation metadata (lives client-side — product copy, not data)       */
-/* ──────────────────────────────────────────────────────────────────────── */
-
-export interface TargetMeta {
-  tone: "neutral" | "blue" | "purple";
-}
-
-export const TARGET_META: Record<TargetKind, TargetMeta> = {
-  cloud: { tone: "blue" },
-  docker: { tone: "neutral" },
-  kubernetes: { tone: "purple" },
-};
-
-export const INSTANCE_STATUS_TONE: Record<
-  InstanceStatus,
-  "success" | "warning" | "danger" | "info" | "neutral"
-> = {
-  healthy: "success",
-  degraded: "warning",
-  offline: "danger",
-  pairing: "info",
-};
-
-/** Values are i18n keys — render with t(). */
-export const INSTANCE_STATUS_LABEL: Record<InstanceStatus, string> = {
-  healthy: "portal.editorAdmin.status.healthy",
-  degraded: "portal.editorAdmin.status.degraded",
-  offline: "portal.editorAdmin.status.offline",
-  pairing: "portal.editorAdmin.status.pairing",
-};
-
 /* ──────────────────────────────────────────────────────────────────────── */
 /*  Endpoints                                                                */
 /* ──────────────────────────────────────────────────────────────────────── */