verify automation interruption recovery and manual debug lifecycle

This commit is contained in:
2026-09-29 12:06:48 +01:00
parent 4f148a50de
commit e6a83c94e0
10 changed files with 300 additions and 17 deletions
@@ -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.