You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 681c882
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: structure/05_gui-and-management-api.md
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,6 +197,29 @@ the effective-token elevation probe may classify it as access denied only when t
197
197
to be non-elevated. An unavailable probe remains `other` and cannot trigger UAC. Query, run, delete,
198
198
native-service, file-write, and foreign task failures never use this fallback.
199
199
200
+
For a fresh scheduler install whose task is proven absent, registration is the non-destructive
201
+
first phase. OpenCodex writes a unique temporary XML definition and asks Task Scheduler to create
202
+
the owned task without running it. Only after that succeeds may service-manager cleanup stop the
203
+
existing proxy, publish the canonical scheduler assets, run the task, and write install state.
204
+
UAC cancellation or create failure removes the temporary XML before any manager/proxy stop, so the
205
+
working proxy's shutdown cleanup cannot strip Codex routing merely because elevation was refused.
206
+
The Dashboard does not apply its ordinary 60-second child timeout to this Windows service command:
207
+
killing only the CLI could orphan the already-launched elevated child, which might register a task
208
+
after the UI reported failure. The asynchronous request and install-attempt lock remain pending
209
+
until Windows returns approval or cancellation; other proxy requests keep running normally.
210
+
Existing or conflicting registrations stay on the older fail-closed path because deleting or
211
+
replacing them cannot be called a rollback without an exact prior-registration snapshot.
212
+
213
+
```text
214
+
[Decision Log]
215
+
- 목적과 의도: Keep a refused fresh Windows service install from stopping a working proxy and removing managed Codex routing.
216
+
- 기존 구현 및 제약 조건: The generic installer stopped service managers and the standalone proxy before the first scheduler create attempt; the Dashboard UAC path depended on assets produced by that already-destructive failure.
217
+
- 검토한 주요 대안: Reject every non-elevated caller up front, restart and re-inject after failure, snapshot every runtime/config artifact for rollback, or separate registration approval from the destructive commit.
218
+
- 선택한 방식: When scheduler absence is proven, create but do not run the owned registration from a temporary XML first; cleanup and canonical asset publication begin only after registration succeeds.
219
+
- 다른 대안 대신 이 방식을 선택한 이유: An early rejection breaks Dashboard UAC, while a best-effort restart cannot prove that manager, proxy, and routing state were restored. The two-phase boundary makes denial/cancellation a real pre-commit failure.
220
+
- 장점, 단점 및 영향: Fresh-install UAC failure preserves the live proxy and routing. Failures after registration remain explicit partial-install cases, and existing/conflicting scheduler recovery remains conservative until exact prior-state restoration is available.
221
+
```
222
+
200
223
```text
201
224
[Decision Log]
202
225
- 목적과 의도: Make Windows scheduler installation recovery work on non-English systems without broadening the commands that may request UAC.
0 commit comments