Reverse engineer anything with agents, from app behavior down to native binaries.
TypeScript agent-skillsai-agentsbinary-analysisclaude-codeclicodexcordisdecompilerdeveloper-toolsdshdsh-pluginghidrahopperllmmcpmodel-context-protocolreareverse-engineeringstatic-analysistouhou
docs(browser): clarify scenario cleanup after termination
morlutod09be9cfa2ee
diff --git a/docs/browser-scenario-contract.md b/docs/browser-scenario-contract.mdindex f6d6a40a7..067fb9409 100644--- a/docs/browser-scenario-contract.md+++ b/docs/browser-scenario-contract.md@@ -144,6 +144,18 @@ distinction: it closes and deletes provider-owned profiles, but only disconnectsfrom an external CDP browser. Real-browser verification checks both outcomes andconfirms that an attached external browser remains alive.+That cleanup requires REA to remain running. Abrupt termination, including+Windows process-tree termination or POSIX `SIGKILL`, can leave the launch+profile and Playwright artifacts behind. A profile can retain cookies, history,+cache and origin storage. Later REA runs currently do not reclaim these paths.+Playwright 1.58.2 can also leave an artifacts directory when launch preparation+fails before a browser process exists, such as for a missing executable.+POSIX wrappers can request awaited cancellation with `SIGINT` or `SIGTERM`;+Windows process termination is not an equivalent graceful-cancellation channel.+Do not identify owned artifacts by directory prefix or creation time alone.+See [#4659](https://github.com/morluto/rea/issues/4659) for the remaining recovery+and wrapper-cancellation work.+Keeping that browser alive does not guarantee its emulation state survives.Chromium can clear caller-owned `navigator.platform` emulation when a page CDPsession disconnects, including sessions that sent no emulation commands. REA