19 lines
1.5 KiB
Markdown
19 lines
1.5 KiB
Markdown
# 05 — Control the GNOME desktop proxy Target
|
|
|
|
**What to build:** A GNOME desktop Target that applies the Active Profile through GNOME's official settings model, restores prior desktop proxy settings safely, and appears only when the required settings schema is available.
|
|
|
|
**Blocked by:** 02 — Safely control the Shell Target.
|
|
|
|
**Status:** done
|
|
|
|
- [ ] The Target is Available only when the expected GNOME settings command and proxy schema are usable for the owning user.
|
|
- [ ] The explanation states that it affects applications consuming GNOME system network settings and does not promise coverage of every graphical application.
|
|
- [ ] Enabling records the recognized original proxy mode and values before applying the Active Profile.
|
|
- [ ] Disabling restores the recorded original settings when managed values remain under `proxyctl` ownership.
|
|
- [ ] Inspection distinguishes Enabled, Disabled, External, and Drifted using positive evidence from GNOME settings.
|
|
- [ ] HTTP, HTTPS, SOCKS, and Bypass values are translated only when their semantics can be preserved.
|
|
- [ ] Any unrepresentable protocol or Bypass rule rejects the operation before mutation with an actionable explanation.
|
|
- [ ] Running through `sudo` operates on the invoking user's GNOME settings rather than root's desktop settings.
|
|
- [ ] Command, session-bus, schema, and permission failures are reflected immediately without false success.
|
|
- [ ] Adapter contract and Target-specific tests use a fake settings command and never modify the active desktop session.
|