disable the admin/brencher remote for the main brencher profile
document backend/API use cases in docs/USE_CASES_BACKEND.md
document UI/state use cases in docs/USE_CASES_UI.md
preserve the application goal section in both documents
document the actual boundary: REST is read-only (/state, /branches); mutations are currently sent through /ws
Verification
git diff --check
python3 -m compileall -q backend
backend scenarios: B-01..B-19
UI scenarios: U-01..U-21
main profile no longer contains admin/brencher; brencher2 remains unchanged
Notes
The PR head is hermes/docs/exhaustive-use-cases and the target is admin/main.
## Summary
- disable the `admin/brencher` remote for the main `brencher` profile
- document backend/API use cases in `docs/USE_CASES_BACKEND.md`
- document UI/state use cases in `docs/USE_CASES_UI.md`
- preserve the application goal section in both documents
- document the actual boundary: REST is read-only (`/state`, `/branches`); mutations are currently sent through `/ws`
## Verification
- `git diff --check`
- `python3 -m compileall -q backend`
- backend scenarios: `B-01..B-19`
- UI scenarios: `U-01..U-21`
- main profile no longer contains `admin/brencher`; `brencher2` remains unchanged
## Notes
The PR head is `hermes/docs/exhaustive-use-cases` and the target is `admin/main`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
admin/brencherremote for the mainbrencherprofiledocs/USE_CASES_BACKEND.mddocs/USE_CASES_UI.md/state,/branches); mutations are currently sent through/wsVerification
git diff --checkpython3 -m compileall -q backendB-01..B-19U-01..U-21admin/brencher;brencher2remains unchangedNotes
The PR head is
hermes/docs/exhaustive-use-casesand the target isadmin/main.@@ -0,0 +31,4 @@3. Через 5 секунд интерфейс повторяет подключение.4. После подключения сервер снова отправляет полное состояние.### UC-03. Посмотреть версию приложенияВерсия чего отображается