verify automation interruption recovery and manual debug lifecycle
This commit is contained in:
@@ -139,6 +139,19 @@ NOT release control. Closing the project or Studio MUST revoke authority and
|
||||
stop managed processes before teardown of their providers/executors. Reopening
|
||||
MUST start in manual control, even when restoring DEV as the selected workspace.
|
||||
|
||||
The application-owned project-session factory tracks sessions and closes all of
|
||||
them before its LSP/executor dependencies are destroyed, including sessions not
|
||||
currently represented by a window. Closing one project removes it from that set;
|
||||
application teardown rejects new opens and attempts every remaining project even
|
||||
if another close reports failure.
|
||||
|
||||
If shutdown required forced termination, the first return attempt reports cleanup
|
||||
failure and retains the manual guard. A subsequent explicit human reclaim may
|
||||
acknowledge cleanup only after the gateway confirms that its owned process tree
|
||||
is dead. A cached failed shutdown must not make a dead session permanently
|
||||
unreclaimable. Cancellation racing a process crash must still allow the owner to
|
||||
await worker termination and shutdown; it must not bypass that cleanup sequence.
|
||||
|
||||
Studio cannot stop direct writes by the external coding client. The UI and
|
||||
connection instructions MUST tell the developer to stop that client separately;
|
||||
reclaim is not an operating-system filesystem lock or a rollback guarantee.
|
||||
|
||||
@@ -466,7 +466,19 @@ an empty result with the current language service; the gate does not claim SDK
|
||||
symbol navigation where no location is returned. This is a language tooling
|
||||
limitation, not a headless or MCP execution fallback.
|
||||
|
||||
The automated client is not an external coding agent. Adversarial integrated
|
||||
lifecycle, real-agent compatibility and final packaging acceptance remain later
|
||||
gates. API/Core and JavaFX MUST NOT import MCP/HTTP implementations; architecture
|
||||
tests enforce it.
|
||||
Step 25 extends that real desktop/HTTP gate with active-operation cancellation,
|
||||
connection deletion/reconnection and duplicate receipts, waiting/active revoke,
|
||||
late-call rejection, project closure/reopening and application-context shutdown.
|
||||
A controlled document participant delays refresh acknowledgement to prove that
|
||||
manual control remains blocked until process cleanup and disk refresh complete;
|
||||
it also checks that no revoked frame or old source buffer is applied afterward.
|
||||
The real runtime is killed or suspended in test-owned processes to verify known
|
||||
progress, no implicit restart/replay, forced cleanup and explicit human retry.
|
||||
Compile errors and guest faults are corrected over HTTP within the same task.
|
||||
The normal desktop Debug process starts after release and blocks a new grant.
|
||||
The suspension/manual-Debug scenarios require a POSIX desktop and a free Debug
|
||||
port 7777; the gate never attaches to an existing user's Debug process.
|
||||
|
||||
The automated client is not an external coding agent. Real-agent compatibility
|
||||
and final packaging acceptance remain later gates. API/Core and JavaFX MUST NOT
|
||||
import MCP/HTTP implementations; architecture tests enforce it.
|
||||
|
||||
Reference in New Issue
Block a user