Document browser reliability layer and roadmap progress

README.md

@@ -951,12 +951,18 @@ Flynn ships these browser tools:
 - `browser.click`
 - `browser.type`
 - `browser.content`
+- `browser.wait_for`
+- `browser.assert`
+- `browser.extract`
+- `browser.checkpoint.save`
+- `browser.checkpoint.resume`
 - `browser.eval`
 - `browser.evaluate` (alias of `browser.eval`)
 
 These tools are backed by a Puppeteer/CDP browser manager and are only registered when `browser.enabled: true`.
 They can still be filtered out by tool policy (`tools.profile`, `tools.allow`, `tools.deny`).
 At startup, Flynn logs the browser tools that remain available after policy filtering.
+Browser runtime guardrails support domain allowlists, explicit high-risk-domain confirmation, retry controls, and a bounded workflow step budget.
 
 ```yaml
 browser:
@@ -964,6 +970,13 @@ browser:
   headless: true
   max_pages: 5
   default_timeout: 30000
+  allowed_domains: ["*.example.com"]
+  high_risk_domains: ["bank.example.com"]
+  require_confirmation_for_high_risk: true
+  max_workflow_steps: 120
+  default_retry_attempts: 1
+  max_retry_attempts: 5
+  retry_delay_ms: 250
   # executable_path: /usr/bin/google-chrome
   # ws_endpoint: ws://127.0.0.1:9222/devtools/browser/<id>