Merge origin/main into feature/contextual-safety-review

Integration fixes the merge required:
- guard tools after the strict-schema downgrade, so the copy
  dataclasses.replace returns is the object the safety wrapper mutates
- await _ctx_client, which main made async for the Caido bootstrap handle
- pass main's extra_files through with the isolated local sources
- keep DEFAULT_SAFETY_MODE alongside main's new report/state imports
- rebuild the committed viewer bundle from the merged frontend sources
- pin the browser-session safety phrase in test_safety_prompt so it no
  longer matches unrelated prompt text, and stamp safety_mode on the
  workspace-file resume record

docs/integrations/coding-agents.mdx

@@ -19,6 +19,11 @@ npx skills add usestrix/strix
 | `managed-pentesting-with-strix` | Drive the managed [app.strix.ai](https://app.strix.ai) platform over REST — no local Docker or LLM key needed |
 | `fix-security-vulnerabilities-with-strix` | Triage findings, fix root causes, and re-run Strix to verify each fix |
 | `ci-security-scanning-with-strix` | Add PR security scanning to GitHub Actions or any CI (self-hosted CLI or managed app) |
+| `application-security-testing` | Assess a whole product: choose the right test for each asset, then rank the findings into one remediation plan |
+| `web-app-penetration-testing` | Black-box pentest of a live web app or staging site — scope, credentials, and multi-account access-control testing |
+| `api-security-testing` | Test a REST/GraphQL API against the OWASP API Security Top 10 — schema-driven enumeration, BOLA/IDOR, authz |
+| `owasp-top-10-testing` | Systematic OWASP Top 10 assessment with honest per-category coverage |
+| `find-security-vulnerabilities-in-code` | White-box security review of a repo or working tree, with exploits to confirm findings |
 
 Install a single skill with `npx skills add usestrix/strix --skill penetration-testing-with-strix`, or use one without installing:
 

docs/usage/cli.mdx

@@ -37,6 +37,13 @@ strix (--target <target> | --target-list <path>) [options]
   Path to a file containing detailed instructions.
 </ParamField>
 
+<ParamField path="--workspace-file" type="string">
+  Path to a file on your machine to place into the sandbox workspace before the
+  scan starts. Repeat the option for more files. Write `PATH:DEST` to choose the
+  destination inside `/workspace`. `DEST` defaults to the file name. See
+  [Workspace files](/usage/instructions#workspace-files).
+</ParamField>
+
 <ParamField path="--scan-mode, -m" type="string" default="deep">
   Scan depth: `quick`, `standard`, or `deep`.
 </ParamField>
@@ -149,6 +156,10 @@ strix -t "postman://<collection-uuid>?env=<environment-uuid>"
 
 # Targets from a file
 strix --target-list ./targets.txt
+
+# Extra files placed in the sandbox workspace
+strix --target ./my-project --workspace-file ./wordlist.txt
+strix --target https://app.com --workspace-file ./openapi.yaml:specs/openapi.yaml
 ```
 
 ## Exit Codes

docs/usage/instructions.mdx

@@ -71,3 +71,43 @@ strix --target https://api.example.com \
 <Tip>
 Be specific. Good instructions help Strix prioritize the most valuable attack paths.
 </Tip>
+
+## Workspace files
+
+Instructions become part of the prompt. To give Strix a file to work with, such
+as a wordlist, an API specification, or notes, use `--workspace-file`. Strix
+places the file into the sandbox workspace before the scan starts.
+
+```bash
+strix --target https://app.com --workspace-file ./wordlist.txt
+```
+
+The file lands at `/workspace/<file name>`. To choose the destination, write
+`PATH:DEST`. `DEST` is a path inside `/workspace`.
+
+```bash
+strix --target https://app.com \
+  --workspace-file ./openapi.yaml:specs/openapi.yaml \
+  --workspace-file ./notes.md
+```
+
+Repeat the option for every file you want to place. Strix lists the files in the
+agent task, so the agent knows where to read them.
+
+Rules that apply to every workspace file:
+
+- The file is read-only inside the sandbox.
+- The destination must stay inside `/workspace`.
+- The destination must not fall inside a target directory, because target files
+  come from the target itself. Strix skips such a file and logs a warning.
+- Two files cannot claim the same destination.
+
+<Note>
+A workspace file is data for the agent to use. It is not a scan target, and its
+contents do not change the instructions.
+</Note>
+
+<Warning>
+Do not place secrets in a workspace file. The sandbox runs untrusted target
+code, so treat anything you place there as readable by the target.
+</Warning>