docs: fix

docs/user/add-new-service.md

@@ -23,18 +23,6 @@ agebd --help
 agebd service add --help
 ```
 
-Required options:
-
-- `--name` / `-n`: CamelCase service name (e.g. `MyService`). Used as-is in the GUI, and
-  converted to upper/lowercase where needed elsewhere.
-- `--ioc-owner` / `-o`: who to contact if the picket service flags an issue with this IOC.
-- `--ioc-description` / `-d`: short description for the [IOC overview](ioc/iocs_overview.md).
-
-Optional:
-
-- `--gui` / `-g`: `new` (default, scaffolds a new `.ui` file), `existing` (reuse another
-  service's GUI, requires `--gui-existing-service-name`), or `none`.
-
 **This command has side effects you should know about before running it.** It requires a
 clean working tree, then it:
 
@@ -90,13 +78,6 @@ PVs owned by another service (including another AGEBD service, e.g. `AGEBD-PARAM
 from a different service) or by real accelerator hardware (e.g. `ARS01-MOCT-...`) are used
 verbatim — no `-DEV` suffix is ever added, even in `dev`.
 
-Note that, as of writing, there is **no dev/prod read/write restriction enforced anywhere**
-for these PVs — `dev` code can write to them exactly like `prod` code can. A
-`get_pv_external_class()` helper exists in `pv.py` with a "read-only in dev" intent in its
-docstring, but no service currently uses it, and there's no EPICS Access Security (`.acf`)
-configuration in this repo either. Be careful writing to external PVs from `dev` — nothing
-stops you from affecting the real machine.
-
 #### PVs - Examples
 
 |  Environment | Service Specific | External |