per-user linux accounts are not optional any more

OFFICER_OS_USERS is gone. The platform behaves as it always would have with the
flag on, and there is nothing to enable.

Six conditionals, five of which were dead weight — provisionOsAccount,
deprovisionOsAccount and the create/delete paths each opened with an early
"not enabled on this server" return, and the API told the frontend whether to
render the Linux controls at all. Those go, along with the 'disabled'
DeprovisionResult stage, which nothing can produce now.

The sixth is the one with teeth. assertSecretsClosed opened with
`if (!OS_USERS_ENABLED) return`, described in its own comment as "a no-op when
the feature is off, so an existing install is unaffected until the owner opts
in". It is now unconditional: the server refuses to boot while any .env in the
project root is group- or world-readable. A member's shell reading .env and
printing JWT_SECRET was confirmed exploitable when this check was written, and a
prerequisite that only holds when somebody remembers to set a variable is not a
prerequisite.

Nothing to remove on the environment side — the flag was never in .env.example
or in the setup script.

Not typechecked: node_modules is empty in this tree and installs are frozen, so
tsgo could not run. All six files parse under `bun build --no-bundle`, and the
changes are deletions of dead branches plus one removed early return. Formatted
with prettier 3.9.6 via bunx rather than the pinned resolution, for the same
reason; its one unrelated reformat was reverted by hand.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/servers/api/users/provision-os.ts

@@ -1,5 +1,5 @@
 import { updateUser } from 'officerdb';
-import { OS_USERS_ENABLED, ensureOsUser, osUserHome } from '@@/os-user';
+import { ensureOsUser, osUserHome } from '@@/os-user';
 import { provisionSshAccess } from '@@/os-user-ssh';
 import { seedShellConfig } from '@@/os-user-shell';
 import { provisionClaudeCli } from '@@/os-user-claude';
@@ -12,7 +12,7 @@ import { provisionUserDirs } from '@@/data-path';
 // it has to happen at — the same reasoning as app-store/members.ts. The list of reasons a retry is needed is
 // not exotic:
 //
-//   - the host was not set up for it when the account was made (`OFFICER_OS_USERS` off, no sudoers entry)
+//   - the host was not set up for it when the account was made (no sudoers entry for the service user)
 //   - an ancestor directory was not traversable, which is the one everybody hits once
 //   - the owner wants to replace the inbound SSH key
 //
@@ -42,10 +42,6 @@ export async function provisionOsAccount(params: {
   /** Inbound SSH key for `authorized_keys`. Already validated by the caller. */
   inboundKey?: string | null;
 }): Promise<OsProvisionOutcome> {
-  if (!OS_USERS_ENABLED) {
-    return { osUser: null, sshPublicKey: null, error: 'per-user Linux accounts are not enabled on this server' };
-  }
-
   // First, because a missing skeleton is the reason `useradd --home-dir … -M` would have nothing to point at.
   try {
     provisionUserDirs(params.email);