ops-client ยท diff

git:20260915.3d7652b to git:20260917.5cfe6d9

5 added, 1 removed. Audit A to A.

---
name: ops-client
- description: "Use when explicitly authorized desktop-client operation or native-window evidence is needed; not for browser proxies, source implementation, diagnosis-only work, or Git delivery."
+ description: "Operate desktop clients and capture native-window evidence within task authority."
---
# Client Operations
## Entry Gate
Operate a named desktop client only after confirming target process/window/build, adapter capability, allowed side effects, and evidence boundary. Installation, process, window, menu, and runtime behavior are separate claims.
+
+ Reuse existing task authority for requested local client acceptance. An implementation
+ handoff does not require renewed approval; installs, account changes, external writes,
+ and destructive actions still require their own applicable authority.
## Route Map
| Request condition | Read | Result |
| --- | --- | --- |
| Launch/inspect/interact/capture a client | [usage](references/usage.md) | Verified client-layer evidence or safe stop |
| Need examples/edge cases | [usage](references/usage.md) | Correct mode/boundary |
## Invariants
- Do not substitute browser, build, process, or menu evidence for real native-window acceptance.
- Attempt the user-named app before aliasing; report checked sources rather than declaring machine-wide absence.
- Keep diagnostics, source fixes, browser behavior, and Git mutation with their owners; clean disposable probes.
## Output Map
Return app/process/window/build identity, authorized actions, direct evidence, cleanup, and `Not verified` claims.
## Reference Map
- Read [usage](references/usage.md) for client modes, targeting, safety, evidence, and stop conditions.
- Maintainers only: read [eval cases](references/eval-cases.md); do not load it during ordinary runtime.