Hosted QA: separate conversation isolation after #122

[boudra]

Maintainer-authorized hosted QA for #118 after deployment.

This issue records a narrowly scoped test of GitHub-triggered agent continuation: initial reply, retained conversation after workspace archival, and isolation from another issue. Test agents are instructed to make no code or service changes. It will be closed after evidence is collected.

[boudra]

CONTINUATION-QA-118 Isolation check. From your conversation memory alone, what value did I previously ask you to remember? If this conversation has no such earlier request, reply ISOLATION recalled=NONE and the current executionId, then finish this execution. Do not retrieve prior comments or read files.

[paseo-bot]

ISOLATION recalled=NONE executionId=daaf8466-b24f-53bc-bf53-af7f444a6da2

[boudra]

Closing this temporary QA fixture; the evidence stays in the comments.

Hosted Hub is deployed with the reply-tool and legacy-workflow corrections in #122. Existing legacy execution and separate-issue isolation passed. Archive continuation exposed a daemon writer-ownership bug, tracked and fixed in getpaseo/paseo#4512.

The built daemon fix passed actual hosted GitHub continuation in #125: same agent/session, restored workspace, recalled the earlier value, replied, finished, and archived again. The main development daemon remains unchanged and still needs the fix before its restore failure can be certified resolved. Temporary QA triggers have been disabled.