sync: update from private repo (ce93095)

docs/user-folder-layout.md

@@ -9,7 +9,7 @@ tied to a single run), the user folder **persists indefinitely** across tasks,
 sessions, and server restarts.
 
 The primary use-cases are:
-- Storing reusable scripts (`scripts/`) and browser macros (`browser-macros/`) that any of your tasks can invoke via `RunUserScript`.
+- Storing reusable browser macros (`browser-macros/`) that any of your tasks can invoke via `RunUserScript`.
 - Keeping template files and reference documents you want agents to access without uploading them every time.
 - Holding auto-generated recordings of browser sessions so you can review or convert them later.
 - Managing saved browser login sessions (`browser-sessions/`) that macros can use.
@@ -22,32 +22,21 @@ created on first login and is never shared between accounts.
 
 ## Subdirectories
 
-### `scripts/`
-
-**AI-generated plain Node.js programs.** No Chromium. Signature: `main({ params })`.
-
-Best for: data processing, API calls, computation, file conversion, scheduled task helpers — anything that does not need a browser.
-
-Files are edited directly in the **User Folder → scripts/** panel. The agent writes and runs these via `RunUserScript({ name, kind: 'script' })` (the default `kind`).
-
-See [docs/tools/runuserscript.md](tools/runuserscript.md) for the exact file format and invocation details.
-
 ### `browser-macros/`
 
 **Playwright-based browser automation scripts.** Launches Chromium. Signature: `main({ context, params })`.
 
-Generated automatically by the **Save as Script** button in the recordings panel (previously these went to `scripts/`). Can also be written manually in the UI. The agent runs them via `RunUserScript({ name, kind: 'browser-macro' })`.
+> **Retired (2026-06):** the former `scripts/` (plain Node) and `templates/`
+> subdirectories were removed. Reusable procedures/boilerplate belong in
+> **Skills**; ad-hoc code runs via the agent's **Bash** tool. Existing files
+> remain on disk but are no longer listed or runnable.
+
+Generated automatically by the **Save as Script** button in the recordings panel. Can also be written manually in the UI. The agent runs them via `RunUserScript({ name })`.
 
 If a `session_profile_id` is declared in the frontmatter, the corresponding saved browser session (from `browser-sessions/`) is loaded automatically.
 
 **Self-healing patches**: when a macro fails, the agent auto-enables the BrowseWeb recorder; on task completion a candidate patch is staged as `browser-macros/{name}.next.js`. The Diff review pane lets you accept or reject it. See [Self-Healing Patches](#self-healing-script-patches) below.
 
-### `templates/`
-
-Static files — Markdown snippets, HTML skeletons, CSV headers, prompt
-fragments — that you want to reuse across tasks. Agents can read these with
-the standard `Read` tool by referencing the path the API returns.
-
 ### `recordings/`
 
 Browser-session recordings produced by `BrowseWeb` when the `record_to`
@@ -126,25 +115,7 @@ editor — the agent picks up the latest version at the start of each task.
 
 ---
 
-## Script vs Browser-Macro Format
-
-### Plain scripts (`scripts/`)
-
-```js
----
-description: "Fetch and summarise data"
-params:
-  - name: url
-    type: string
----
-async function main({ params }) {
-  const data = await fetch(params.url).then(r => r.json());
-  return data.summary;
-}
-module.exports = main;
-```
-
-Invocation: `RunUserScript({ name: 'my-script', kind: 'script', params: { url: '...' } })`
+## Browser-Macro Format
 
 ### Browser macros (`browser-macros/`)