docs: treat explicit email target as send authorization
This commit is contained in:
@@ -33,6 +33,11 @@ scripts/property-assessor --help
|
||||
|
||||
The wrapper script uses the skill-local Node dependencies under `node_modules/`.
|
||||
|
||||
Delivery rule:
|
||||
|
||||
- If the user explicitly says to email or send the finished PDF to a stated target address, that counts as delivery authorization once the report is ready.
|
||||
- The agent should not ask for a second `send it` confirmation unless the user changed the destination or showed uncertainty.
|
||||
|
||||
## Commands
|
||||
|
||||
```bash
|
||||
@@ -71,6 +76,7 @@ Operational rule:
|
||||
- In those messaging runs, reserve subprocess use for a single final `render-report` attempt after the verdict and fair-value range are complete.
|
||||
- In those messaging runs, do not start Gmail/email-send skill discovery or delivery tooling until the report content is complete and the PDF is ready to render or already rendered.
|
||||
- Treat a silent helper as a failed helper in messaging runs. If a helper produces no useful output within a short bound, abandon it and continue with the chat-native path instead of repeatedly polling it.
|
||||
- If the original request already authorized sending the finished PDF to a stated email address, do not pause for a redundant send-confirmation prompt after rendering.
|
||||
- If final PDF render/send fails, return the completed decision-grade report in chat and report delivery failure separately rather than restarting the whole assessment.
|
||||
|
||||
### `assess`
|
||||
|
||||
Reference in New Issue
Block a user