RuleSpoolMake the application question concrete
Suppose your agent maintains a staging signup form and a QA command stopped at a permission prompt. Capture that native request and the relevant resolved rules. In RuleSpool, compare a narrow draft change with the original and keep an unrelated request as a regression case.
After your own review, apply the chosen change in your local setup and verify the real runtime action. This site cannot perform that step. A supplied-layer allow does not establish that the command started, that a test passed or that the staging site was deployed.
Look at the form in a fresh browser
Open WebTraceCheck to inspect your own public staging page in a separate browser session. Check the visible inputs, validation, submit result and expected navigation. Record the actual browser environment; a remote Chromium result does not prove behavior on Safari or a device-bound account.
This step tests a user path independently of the agent's permission preview. WebTraceCheck does not receive your imported rule snapshot or connect to your local OpenCode server through this page.
Observe one harmless receipt
If the form sends email through your application's existing sender, use CleanTempMail for a disposable staging address. Use a non-sensitive test identifier, submit the form once and check whether the expected message arrives. Keep recipient, time and outcome in your own test record.
Do not use a disposable inbox for an important account's recovery. If your app rejects the address, that is an application-policy result. CleanTempMail receives the test email; it does not send on behalf of the app, execute an agent task or establish general deliverability.
Keep the evidence chain separate
- RuleSpool: which supplied rules explain the request, and what does the proposed order change?
- Your local runtime: did the intended agent action actually complete?
- Your staging page: did the visible browser flow work?
- Your test inbox: did this particular receipt arrive?
The two linked services are related products promoted by this site. Their links carry source and placement tags. They are optional and are relevant only when your own task has this browser-and-email acceptance flow; an arbitrary permission question may have neither.