Ilia Denisov
87a272166b
Tests · Go / test (push) Successful in 1m59s
Add the operator-management page over *admin.Service (no new business logic).
- GET/POST /_gm/operators list + create operator
- POST /_gm/operators/{user}/disable|enable toggle access
- POST /_gm/operators/{user}/reset-password set a new password
Console depends on an OperatorAdmin interface (satisfied by *admin.Service) so
the page renders in tests without a database. Create POST is mounted on the
collection path; per-row disable/enable/reset are guarded by the CSRF middleware
and redirect back. Passwords are never logged.
Tests: list render, create (+ username/password assertions), username-taken
conflict, disable/enable, reset (+ password assertion), missing-password 400,
bad-CSRF 403, and unavailable 503.
Docs: backend/docs/admin-console.md page inventory extended.
Backend Service Docs
This directory keeps service-local documentation that is too detailed for the workspace-level architecture document and too diagram-heavy for the module README.
Sections:
- Runtime and components
- Domain and protocol flows
- Operator runbook
- Configuration and contract examples
Primary references:
../README.md— service scope, contracts, configuration, operational behaviour.../openapi.yaml— REST contract.../PLAN.md— historical staged build-up; kept for archaeology, not as a source of truth.../../docs/ARCHITECTURE.md— workspace-level architecture.