@jstn-sdk/rcs 0.1.0

package/docs/hooks-extension.md

@@ -0,0 +1,146 @@
+# Hooks Extension (Custom Plugins)
+
+RCS supports an additive hooks extension point for user plugins under `.rcs/hooks/*.mjs`.
+
+The official packaged Codex plugin at `plugins/roblox-ai-os-creator-skills` also ships plugin-scoped
+companion metadata files (`.mcp.json`, `.app.json`) so the plugin bundle describes those
+surfaces from inside the plugin root. Native/runtime hooks are intentionally separate:
+they stay on the runtime/config side (`.codex/hooks.json` plus `.rcs/hooks/*.mjs`) rather
+than inside the installable plugin manifest.
+
+Native Codex hook ownership is documented separately in
+[Codex native hook mapping](./codex-native-hooks.md). In short:
+
+- `.codex/hooks.json` = native Codex hook registrations installed by `rcs setup`
+- `.rcs/hooks/*.mjs` = RCS plugin hooks dispatched by runtime/native events
+- `rcs tmux-hook` / notify-hook / derived watcher = tmux/runtime fallback surfaces
+
+`rcs setup` treats `.codex/hooks.json` as a shared-ownership file: it refreshes only the RCS-managed
+wrapper entries that invoke `dist/scripts/codex-native-hook.js` and preserves user hook entries in the
+same file. `rcs uninstall` removes only those RCS-managed wrappers and leaves `.codex/hooks.json` in
+place when user hooks remain.
+
+> Compatibility guarantee: `rcs tmux-hook` remains fully supported and unchanged.
+> The new `rcs hooks` command group is additive and does **not** replace tmux-hook workflows.
+
+## Quick start
+
+```bash
+rcs hooks init
+rcs hooks status
+rcs hooks validate
+rcs hooks test
+```
+
+This creates a scaffold plugin at:
+
+- `.rcs/hooks/sample-plugin.mjs`
+
+## Enablement model
+
+Plugins are **enabled by default**.
+
+Disable plugin dispatch explicitly:
+
+```bash
+export RCS_HOOK_PLUGINS=0
+```
+
+Optional timeout tuning (default: 1500ms):
+
+```bash
+export RCS_HOOK_PLUGIN_TIMEOUT_MS=1500
+```
+
+## Native event pipeline (v1)
+
+Native/derived plugin events come from two places:
+
+1. Existing lifecycle/notify paths
+2. Native Codex hook entrypoint dispatch (`dist/scripts/codex-native-hook.js`)
+
+Current event vocabulary exposed to RCS plugins:
+
+- `session-start`
+- `keyword-detector`
+- `pre-tool-use`
+- `post-tool-use`
+- `stop`
+- `session-end`
+- `turn-complete`
+- `session-idle`
+
+RCS keeps this existing event vocabulary rather than exposing raw Codex hook names directly.
+That lets native Codex hooks and fallback/derived paths feed one shared plugin/runtime surface.
+
+For clawhip-oriented operational routing, see [Clawhip Event Contract](./clawhip-event-contract.md).
+
+Envelope fields include:
+
+- `schema_version: "1"`
+- `event`
+- `timestamp`
+- `source` (`native` or `derived`)
+- `context`
+- optional IDs: `session_id`, `thread_id`, `turn_id`, `mode`
+
+## Derived signals (opt-in)
+
+Best-effort derived events are gated and disabled by default.
+
+```bash
+export RCS_HOOK_DERIVED_SIGNALS=1
+```
+
+Derived signals include:
+
+- `needs-input`
+- `pre-tool-use`
+- `post-tool-use`
+
+Derived events are labeled with:
+
+- `source: "derived"`
+- `confidence`
+- parser-specific context hints
+
+## Team-safety behavior
+
+In team-worker sessions (`RCS_TEAM_WORKER` set), plugin side effects are skipped by default.
+This keeps the lead session as the canonical side-effect emitter and avoids duplicate sends.
+
+## Plugin contract
+
+Each plugin must export:
+
+```js
+export async function onHookEvent(event, sdk) {
+  // handle event
+}
+```
+
+SDK surface includes:
+
+- `sdk.tmux.sendKeys(...)`
+- `sdk.log.info|warn|error(...)`
+- `sdk.state.read|write|delete|all(...)` (plugin namespace scoped)
+- `sdk.rcs.session.read()`
+- `sdk.rcs.hud.read()`
+- `sdk.rcs.notifyFallback.read()`
+- `sdk.rcs.updateCheck.read()`
+
+`sdk.rcs` is intentionally narrow and read-only in pass one. These helpers read the
+repo-root `.rcs/state/*.json` runtime files for the current workspace.
+
+Compatibility notes:
+
+- `rcs tmux-hook` remains a CLI/runtime workflow, not `sdk.rcs.tmuxHook.*`
+- pass one does not add `sdk.rcs.tmuxHook.*`; tmux plugin behavior stays on `sdk.tmux.sendKeys(...)`
+- pass one does not add generic `sdk.rcs.readJson(...)`, `sdk.rcs.list()`, or `sdk.rcs.exists()`
+- pass one does not add `sdk.pluginState`; keep using `sdk.state`
+
+## Logs
+
+Plugin dispatch and plugin logs are written to:
+
+- `.rcs/logs/hooks-YYYY-MM-DD.jsonl`

package/docs/index.html

@@ -0,0 +1,117 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>RCS Docs</title>
+    <link rel="stylesheet" href="./style.css" />
+  </head>
+  <body>
+    <header>
+      <nav class="container nav" aria-label="Primary">
+        <a class="brand" href="./index.html">RCS</a>
+        <a class="active" href="./index.html">Home</a>
+        <a href="./getting-started.html">Getting Started</a>
+        <a href="./agents.html">Agents</a>
+        <a href="./skills.html">Skills</a>
+        <a href="./integrations.html">Integrations</a>
+      </nav>
+    </header>
+
+    <main class="container">
+      <section class="hero">
+        <span class="badge">Roblox Creator Skills</span>
+        <h1>RCS</h1>
+        <p>Creator workflow runtime for OpenAI Codex CLI.</p>
+        <pre><code>npm install -g @openai/codex @jstn-sdk/rcs</code></pre>
+        <p>Real global version bumps now print an explicit reminder instead of auto-launching <code>rcs setup</code>. When you're ready, run <code>rcs setup</code> manually or use <code>rcs update</code> to check npm and then run the same setup refresh path. Fresh RCS-managed <code>gpt-5.5</code> configs recommend <code>250000 / 200000</code> only when those keys are missing.</p>
+      </section>
+
+      <section aria-labelledby="whats-new-010">
+        <h2 id="whats-new-010">What's New in v0.1.0</h2>
+        <div class="grid">
+          <article class="card">
+            <h3>Creator Workflow</h3>
+            <p>
+              The canonical public workflow is now <code>$brief</code>, <code>$blueprint</code>, <code>$forge</code>, <code>$crew</code>, and <code>$autoforge</code>.
+            </p>
+          </article>
+          <article class="card">
+            <h3>Psychology Layer</h3>
+            <p>
+              RCS now ships a formal player-psychology design family for progression, status, FOMO, mastery, and community.
+            </p>
+          </article>
+          <article class="card">
+            <h3>Roblox Pre-Action Gate</h3>
+            <p>
+              Roblox implementation work now requires reference gathering, terminology normalization, and modular file-tree design before code generation.
+            </p>
+          </article>
+          <article class="card">
+            <h3>Owned Product Surface</h3>
+            <p>
+              Canonical ownership now points at <code>JustineDevs</code>, <code>@jstn-sdk/rcs</code>, and <code>https://github.com/JustineDevs/roblox-ai-os</code>.
+            </p>
+          </article>
+        </div>
+      </section>
+
+      <h2>Core Features</h2>
+      <div class="grid">
+        <article class="card"><h3>Agent Prompts</h3><p>Specialized roles for implementation, review, design, and planning.</p></article>
+        <article class="card"><h3>Skills</h3><p>Composable creator workflows for briefing, blueprinting, forging, psychology design, setup, and tracing.</p></article>
+        <article class="card"><h3>Team Orchestration</h3><p>Staged execution pipeline with verification and fix loops.</p></article>
+        <article class="card"><h3>MCP State Management</h3><p>Persistent lifecycle state, notepad, and project memory across sessions.</p></article>
+      </div>
+
+      <h2>Quick Start</h2>
+      <ol>
+        <li><code>npm install -g @openai/codex @jstn-sdk/rcs</code></li>
+        <li>After install or real version bumps, run <code>rcs setup</code> yourself when you're ready, or use <code>rcs update</code> when you also want npm to update RCS first.</li>
+        <li><code>rcs doctor</code></li>
+        <li><code>rcs --xhigh --madmax</code> (trusted environments) or <code>rcs</code></li>
+      </ol>
+
+      <h2>Reference Guides</h2>
+      <ul>
+        <li><a href="./reference/rcs-config-schema-routing.md">.rcs-config.json model/env routing reference</a></li>
+      </ul>
+
+      <h2>Integration Guides</h2>
+      <p>OpenClaw / notification gateway setup and prompt-tuning guides by language:</p>
+      <p><a href="./integrations.html">Open dedicated Integrations page</a></p>
+      <ul>
+        <li><a href="./openclaw-integration.md">English</a></li>
+        <li><a href="./openclaw-integration.ko.md">한국어</a></li>
+        <li><a href="./openclaw-integration.ja.md">日本語</a></li>
+        <li><a href="./openclaw-integration.zh.md">简体中文</a></li>
+        <li><a href="./openclaw-integration.zh-TW.md">繁體中文</a></li>
+        <li><a href="./openclaw-integration.vi.md">Tiếng Việt</a></li>
+        <li><a href="./openclaw-integration.es.md">Español</a></li>
+        <li><a href="./openclaw-integration.pt.md">Português</a></li>
+        <li><a href="./openclaw-integration.ru.md">Русский</a></li>
+        <li><a href="./openclaw-integration.tr.md">Türkçe</a></li>
+        <li><a href="./openclaw-integration.de.md">Deutsch</a></li>
+        <li><a href="./openclaw-integration.fr.md">Français</a></li>
+        <li><a href="./openclaw-integration.it.md">Italiano</a></li>
+        <li><a href="./openclaw-integration.uk.md">Українська</a></li>
+      </ul>
+
+      <h2>Architecture</h2>
+      <pre><code>User
+  -> Codex CLI
+     -> AGENTS.md (orchestration brain)
+     -> ~/.codex/prompts/*.md (installable active/internal agent prompt catalog)
+     -> ~/.codex/skills/*/SKILL.md (skill catalog)
+     -> ~/.codex/config.toml (features, notify, MCP)
+     -> .rcs/ (runtime state, memory, plans, logs)</code></pre>
+    </main>
+
+    <footer>
+      <div class="container">
+        <span class="muted">GitHub: <a href="https://github.com/JustineDevs/roblox-ai-os">JustineDevs/roblox-ai-os</a></span>
+      </div>
+    </footer>
+  </body>
+</html>

package/docs/integrations.html

@@ -0,0 +1,59 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>Integrations - RCS Docs</title>
+    <link rel="stylesheet" href="./style.css" />
+  </head>
+  <body>
+    <header>
+      <nav class="container nav" aria-label="Primary">
+        <a class="brand" href="./index.html">RCS</a>
+        <a href="./index.html">Home</a>
+        <a href="./getting-started.html">Getting Started</a>
+        <a href="./agents.html">Agents</a>
+        <a href="./skills.html">Skills</a>
+        <a class="active" href="./integrations.html">Integrations</a>
+      </nav>
+    </header>
+
+    <main class="container">
+      <h1>Integrations</h1>
+      <p class="muted">OpenClaw and notification gateway setup + localized prompt-tuning guides.</p>
+
+      <h2>Primary Guide (English)</h2>
+      <ul>
+        <li><a href="./openclaw-integration.md">OpenClaw / Generic Notification Gateway Integration Guide</a></li>
+      </ul>
+
+      <h2>Operator Troubleshooting</h2>
+      <ul>
+        <li><a href="./troubleshooting.md">Execution readiness after setup and doctor</a></li>
+      </ul>
+
+      <h2>Localized Prompt-Tuning Guides</h2>
+      <ul>
+        <li><a href="./openclaw-integration.ko.md">한국어</a></li>
+        <li><a href="./openclaw-integration.ja.md">日本語</a></li>
+        <li><a href="./openclaw-integration.zh.md">简体中文</a></li>
+        <li><a href="./openclaw-integration.zh-TW.md">繁體中文</a></li>
+        <li><a href="./openclaw-integration.vi.md">Tiếng Việt</a></li>
+        <li><a href="./openclaw-integration.es.md">Español</a></li>
+        <li><a href="./openclaw-integration.pt.md">Português</a></li>
+        <li><a href="./openclaw-integration.ru.md">Русский</a></li>
+        <li><a href="./openclaw-integration.tr.md">Türkçe</a></li>
+        <li><a href="./openclaw-integration.de.md">Deutsch</a></li>
+        <li><a href="./openclaw-integration.fr.md">Français</a></li>
+        <li><a href="./openclaw-integration.it.md">Italiano</a></li>
+        <li><a href="./openclaw-integration.uk.md">Українська</a></li>
+      </ul>
+    </main>
+
+    <footer>
+      <div class="container">
+        <span class="muted">GitHub: <a href="https://github.com/JustineDevs/roblox-ai-os">JustineDevs/roblox-ai-os</a></span>
+      </div>
+    </footer>
+  </body>
+</html>

package/docs/interop-team-mutation-contract.md

@@ -0,0 +1,98 @@
+# RCS Team Mutation Contract for Interop Brokers
+
+This document defines the supported **mutation path** for external interoperability brokers.
+
+## Rule of record
+
+External systems must mutate team state through CLI interop:
+
+```bash
+rcs team api <operation> --input '<json-object>' --json
+```
+
+Legacy `team_*` MCP APIs are hard-deprecated and return a deprecation error with a CLI hint.
+Direct writes to `.rcs/state/team/...` are unsupported and may violate runtime invariants.
+
+## Required task mutation flow
+
+1. Read current task:
+   - `rcs team api read-task --json`
+2. Claim with optimistic version:
+   - `rcs team api claim-task --json`
+3. Transition terminal state with claim token:
+   - `rcs team api transition-task-status --json` (`in_progress -> completed|failed`)
+4. Use `rcs team api release-task-claim --json` only for rollback/requeue-to-pending flows.
+
+## Legacy MCP -> CLI migration table
+
+| Legacy `team_*` tool | CLI operation |
+|---|---|
+| `team_send_message` | `rcs team api send-message --json` |
+| `team_broadcast` | `rcs team api broadcast --json` |
+| `team_mailbox_list` | `rcs team api mailbox-list --json` |
+| `team_mailbox_mark_notified` | `rcs team api mailbox-mark-notified --json` |
+| `team_mailbox_mark_delivered` | `rcs team api mailbox-mark-delivered --json` |
+| `team_create_task` | `rcs team api create-task --json` |
+| `team_read_task` | `rcs team api read-task --json` |
+| `team_list_tasks` | `rcs team api list-tasks --json` |
+| `team_update_task` | `rcs team api update-task --json` |
+| `team_claim_task` | `rcs team api claim-task --json` |
+| `team_transition_task_status` | `rcs team api transition-task-status --json` |
+| `team_release_task_claim` | `rcs team api release-task-claim --json` |
+| `team_read_config` | `rcs team api read-config --json` |
+| `team_read_manifest` | `rcs team api read-manifest --json` |
+| `team_read_worker_status` | `rcs team api read-worker-status --json` |
+| `team_read_worker_heartbeat` | `rcs team api read-worker-heartbeat --json` |
+| `team_update_worker_heartbeat` | `rcs team api update-worker-heartbeat --json` |
+| `team_write_worker_inbox` | `rcs team api write-worker-inbox --json` |
+| `team_write_worker_identity` | `rcs team api write-worker-identity --json` |
+| `team_append_event` | `rcs team api append-event --json` |
+| `team_get_summary` | `rcs team api get-summary --json` |
+| `team_cleanup` | `rcs team api cleanup --json` |
+| `team_write_shutdown_request` | `rcs team api write-shutdown-request --json` |
+| `team_read_shutdown_ack` | `rcs team api read-shutdown-ack --json` |
+| `team_read_monitor_snapshot` | `rcs team api read-monitor-snapshot --json` |
+| `team_write_monitor_snapshot` | `rcs team api write-monitor-snapshot --json` |
+| `team_read_task_approval` | `rcs team api read-task-approval --json` |
+| `team_write_task_approval` | `rcs team api write-task-approval --json` |
+
+## Message lifecycle operations
+
+- send: `send-message`, `broadcast`
+- inspect: `mailbox-list`
+- delivery markers: `mailbox-mark-notified`, `mailbox-mark-delivered`
+
+## Dispatch policy (authoritative path)
+
+- Use `rcs team api ... --json` + team state files as the authoritative delivery/control path.
+- Direct tmux typing (`tmux send-keys`, repeated Enter injection) is operational fallback only, not a mutation contract.
+- Interop brokers and worker automations should never assume tmux keystroke delivery implies successful mailbox/task mutation; always verify via JSON envelope + state reads.
+- Rust-core + thin-adapter reader compatibility and release gating are documented in
+  `docs/contracts/rust-runtime-thin-adapter-contract.md` and
+  `docs/qa/rust-runtime-thin-adapter-gate.md`.
+
+## Event read / wakeability contract
+
+When brokers inspect team events via `read-events` / `await-event`:
+
+- Events are returned in canonical form. Legacy `worker_idle` log entries normalize to `worker_state_changed` and keep `source_type: "worker_idle"`.
+- `wakeable_only=true` mirrors `rcs team await` semantics. Wakeable events include terminal task events, worker state changes, `leader_notification_deferred`, `all_workers_idle`, `team_leader_nudge`, `worker_merge_conflict`, and the per-signal stale alerts.
+- Audit-only diff/report events such as `worker_diff_report` and `worker_merge_report` stay durable but non-wakeable.
+- `worker_merge_conflict` remains the compatibility event for actionable integration conflicts; consumers should continue routing conflict handling on that event type while reading richer `metadata` when present.
+
+## JSON envelope contract
+
+`--json` output is machine-readable and stable:
+
+- success:
+  - `{"schema_version":"1.0","timestamp":"<ISO>","command":"rcs team api <operation>","ok":true,"operation":"<operation>","data":{...}}`
+- failure:
+  - `{"schema_version":"1.0","timestamp":"<ISO>","command":"rcs team api ...","ok":false,"operation":"<operation|unknown>","error":{"code":"<code>","message":"<message>"}}`
+
+## Notes
+
+- `transition-task-status` is the claim-safe terminal transition path.
+  - Runtime enforces `in_progress -> completed|failed`; other transitions return `invalid_transition`.
+- `release-task-claim` intentionally resets the task to `pending`; it is not a completion operation.
+- `update-task` only accepts `subject`, `description`, `blocked_by`, and `requires_code_change` as mutable fields.
+- `append-event.type` and `write-task-approval.status` enforce strict enum validation.

package/docs/issues/team-ralph-followup-team.md

@@ -0,0 +1,38 @@
+# Issue Draft: Make `ralplan` first-class for `team` follow-up planning
+
+## Title
+[Feature] Make `ralplan` emit explicit `team` follow-up guidance (for example `--followup team`)
+
+## Problem
+RCS already has the ingredients for a strong high-control workflow: `ralplan` for scoped planning, `team` for durable multi-worker execution, and `ralph` for persistence plus verification. What is still under-explained and under-productized is the handoff between planning and team execution.
+
+Today, experienced users can manually infer the pattern: run `ralplan`, then launch `team`, then keep the work alive with `ralph`. But the workflow's biggest advantage is not just parallelism. It is coordinated execution: teammates can surface blockers early, redistribute work, and stay inspectable through panes plus runtime state. That benefit should be reflected directly in planning output.
+
+## Proposed solution
+Teach `ralplan` to support an explicit team-oriented follow-up mode, such as `--followup team`, that produces:
+
+1. a normal implementation plan and acceptance criteria
+2. recommended worker lanes / role allocation
+3. suggested reasoning levels by lane
+4. explicit follow-up commands or launch hints for `rcs team` / `$team`
+5. verification expectations that fit a `team -> ralph` execution path
+
+This would make the intended workflow clearer:
+
+```text
+ralplan -> team -> ralph
+```
+
+## Why this is good
+- Clarifies why `team` exists alongside `ultrawork`: team mode is about coordination and runtime control, not only fanout.
+- Reduces the gap between planning output and actual orchestration.
+- Makes one of RCS's strongest workflows more discoverable for advanced users.
+- Improves execution quality on runtime-edge-case and orchestration-edge-case work, where durable coordination matters more than raw task splitting.
+- Fits RCS's architecture well because the runtime already supports worker roles, mixed CLIs, runtime state, and inspectable team lifecycle commands.
+
+## Alternatives considered
+- Keep the pattern implicit in docs only. This helps discovery, but still leaves users to translate plans into worker lanes manually.
+- Fold everything into `autopilot`. Useful for default automation, but weaker for users who want direct control over planning, staffing, and verification.
+
+## Additional context
+Expected user outcome: a user runs `ralplan`, sees a plan that is already shaped for team execution, launches `team` with less guesswork, and uses `ralph` to keep the workflow honest until evidence-backed completion.

package/docs/migration-mainline-post-v0.4.4.md

@@ -0,0 +1,90 @@
+# Migration Guide: post-v0.4.4 mainline changes
+
+This guide covers migration from **v0.4.4** to the current mainline changes merged after it (including PR #137 and follow-up fixes).
+
+## Who is affected
+
+You are affected if you:
+
+- invoke removed prompts or skills from old notes/scripts,
+- depend on pre-consolidation catalog names,
+- use `rcs setup` and need predictable install scope behavior,
+- run `rcs team`/tmux workflows and want the latest reliability fixes,
+- use notifier output and need verbosity control.
+
+## What changed (high level)
+
+- Catalog consolidation for prompts/skills and cleanup of deprecated entries.
+- `rcs setup` now supports scope-aware install modes (`user`, `project`). Legacy `project-local` values are auto-migrated.
+- Spark worker routing added for team workers (`--spark`, `--madmax-spark`).
+- Notifier verbosity controls added.
+- tmux runtime hardening updates landed, including post-review pane capture/input hardening.
+- Stale references to removed `scientist`/`pipeline` were cleaned up.
+
+## Removed prompts and skills
+
+### Removed prompts
+
+- `deep-executor`
+- `scientist`
+
+### Removed skills
+
+- `deepinit`
+- `learn-about-rcs`
+- `learner`
+- `pipeline`
+- `project-session-manager`
+- `psm`
+- `release`
+- `ultrapilot`
+- `writer-memory`
+
+## Mapping old references to current ones
+
+Use these replacements in docs, scripts, and personal shortcuts.
+
+| Old reference | Use now | Notes |
+|---|---|---|
+| `/prompts:deep-executor` | `/prompts:executor` | `deep-executor` was a deprecated alias to executor behavior. |
+| `/prompts:scientist` | `/prompts:researcher` | Use researcher for research-focused workflows in current catalog. |
+| `$pipeline` | `$team` (or explicit `/prompts:*` sequencing) | Team is the default orchestrator pipeline surface. |
+| `$ultrapilot` | `$team` | Use team-based parallel orchestration. |
+| `$psm` / `$project-session-manager` | No in-repo replacement | Remove from automation or maintain out-of-tree tooling. |
+| `$release` | No in-repo replacement | Use your project release process directly. |
+| `$deepinit` | `rcs agents-init [path]` | Lightweight CLI successor for AGENTS.md bootstrap only; immediate child directories only, unmanaged files preserved unless `--force`. |
+| `$learn-about-rcs` / `$learner` / `$writer-memory` | No in-repo replacement | Remove stale references from workflows/docs. |
+
+## Verification checklist after upgrade
+
+Run this checklist after pulling latest mainline:
+
+- [ ] Confirm removed references are gone from local notes/scripts:
+  ```bash
+  rg -n "deep-executor|scientist|pipeline|project-session-manager|\bpsm\b|ultrapilot|learn-about-rcs|writer-memory|learner|deepinit|\brelease\b" README.md docs scripts .rcs -S
+  ```
+- [ ] Confirm current prompt catalog no longer contains removed prompts:
+  ```bash
+  ls prompts
+  ```
+- [ ] Confirm current skill catalog no longer contains removed skills:
+  ```bash
+  ls skills
+  ```
+- [ ] Validate setup scope options are available:
+  ```bash
+  rcs help | rg -e "--scope|project"
+  ```
+- [ ] Validate team/tmux health checks:
+  ```bash
+  rcs doctor --team
+  ```
+- [ ] If using spark worker routing, verify flags are available:
+  ```bash
+  rcs --help | rg "spark|madmax-spark"
+  ```
+
+## Related docs
+
+- Release notes: [CHANGELOG.md](../CHANGELOG.md)
+- Main overview: [README.md](../README.md)

package/docs/openclaw-integration.de.md

@@ -0,0 +1,44 @@
+# OpenClaw-Integrationsleitfaden (lokalisierte Prompt-Optimierung)
+
+> [← Back to Docs Home](./index.html) · [Integrations Landing](./integrations.html)
+
+**Language Switcher:** [English](./openclaw-integration.md) | [한국어](./openclaw-integration.ko.md) | [日本語](./openclaw-integration.ja.md) | [简体中文](./openclaw-integration.zh.md) | [繁體中文](./openclaw-integration.zh-TW.md) | [Tiếng Việt](./openclaw-integration.vi.md) | [Español](./openclaw-integration.es.md) | [Português](./openclaw-integration.pt.md) | [Русский](./openclaw-integration.ru.md) | [Türkçe](./openclaw-integration.tr.md) | [Deutsch](./openclaw-integration.de.md) | [Français](./openclaw-integration.fr.md) | [Italiano](./openclaw-integration.it.md) | [Українська](./openclaw-integration.uk.md)
+
+
+Diese Seite lokalisiert den Abschnitt **„Prompt tuning guide (concise + context-aware)”** aus der englischen Hauptdokumentation.
+
+Für die vollständige Integrationsdokumentation (Gateways, Hooks, Verifikation) siehe [English guide](./openclaw-integration.md).
+
+## Prompt-Optimierung (prägnant + kontextbewusst)
+
+## Wo Prompt-Vorlagen bearbeitet werden
+
+- `notifications.openclaw.hooks["session-start"].instruction`
+- `notifications.openclaw.hooks["session-idle"].instruction`
+- `notifications.openclaw.hooks["ask-user-question"].instruction`
+- `notifications.openclaw.hooks["stop"].instruction`
+- `notifications.openclaw.hooks["session-end"].instruction`
+
+## Empfohlene Kontext-Token
+
+- Immer: `{{sessionId}}`, `{{tmuxSession}}`
+- Ereignisabhängig: `{{projectName}}`, `{{question}}`, `{{reason}}`
+
+## Ausführlichkeitsstrategie
+
+- `minimal`: sehr kurze Signale
+- `session`: kompakter Betriebs-Kontext (empfohlen)
+- `verbose`: mehr Status-, Aktions- und Risikokontext
+
+## Schnellupdate-Befehl (jq)
+
+```bash
+CONFIG_FILE="$HOME/.codex/.rcs-config.json"
+
+jq '.notifications.verbosity = "verbose" |
+    .notifications.openclaw.hooks["session-start"].instruction = "[session-start|exec]\nproject={{projectName}} session={{sessionId}} tmux={{tmuxSession}}\n요약: 시작 맥락 1문장\n우선순위: 지금 할 일 1~2개\n주의사항: 리스크/의존성(없으면 없음)" |
+    .notifications.openclaw.hooks["session-idle"].instruction = "[session-idle|exec]\nsession={{sessionId}} tmux={{tmuxSession}}\n요약: idle 원인 1문장\n복구계획: 즉시 조치 1~2개\n의사결정: 사용자 입력 필요 여부" |
+    .notifications.openclaw.hooks["ask-user-question"].instruction = "[ask-user-question|exec]\nsession={{sessionId}} tmux={{tmuxSession}} question={{question}}\n핵심질문: 필요한 답변 1문장\n영향: 미응답 시 영향 1문장\n권장응답: 가장 빠른 답변 형태" |
+    .notifications.openclaw.hooks["stop"].instruction = "[session-stop|exec]\nsession={{sessionId}} tmux={{tmuxSession}}\n요약: 중단 사유\n현재상태: 저장/미완료 항목\n재개: 첫 액션 1개" |
+    .notifications.openclaw.hooks["session-end"].instruction = "[session-end|exec]\nproject={{projectName}} session={{sessionId}} tmux={{tmuxSession}} reason={{reason}}\n성과: 완료 결과 1~2문장\n검증: 확인/테스트 결과\n다음: 후속 액션 1~2개"'   "$CONFIG_FILE" > "$CONFIG_FILE.tmp" && mv "$CONFIG_FILE.tmp" "$CONFIG_FILE"
+```

package/docs/openclaw-integration.es.md

@@ -0,0 +1,44 @@
+# Guía de integración de OpenClaw (ajuste de prompts localizado)
+
+> [← Back to Docs Home](./index.html) · [Integrations Landing](./integrations.html)
+
+**Language Switcher:** [English](./openclaw-integration.md) | [한국어](./openclaw-integration.ko.md) | [日本語](./openclaw-integration.ja.md) | [简体中文](./openclaw-integration.zh.md) | [繁體中文](./openclaw-integration.zh-TW.md) | [Tiếng Việt](./openclaw-integration.vi.md) | [Español](./openclaw-integration.es.md) | [Português](./openclaw-integration.pt.md) | [Русский](./openclaw-integration.ru.md) | [Türkçe](./openclaw-integration.tr.md) | [Deutsch](./openclaw-integration.de.md) | [Français](./openclaw-integration.fr.md) | [Italiano](./openclaw-integration.it.md) | [Українська](./openclaw-integration.uk.md)
+
+
+Esta página localiza la sección **“Prompt tuning guide (concise + context-aware)”** de la documentación principal en inglés.
+
+Para la guía completa de integración (gateways, hooks, verificación), consulta [English guide](./openclaw-integration.md).
+
+## Ajuste de prompts (conciso y consciente del contexto)
+
+## Dónde editar las plantillas de prompt
+
+- `notifications.openclaw.hooks["session-start"].instruction`
+- `notifications.openclaw.hooks["session-idle"].instruction`
+- `notifications.openclaw.hooks["ask-user-question"].instruction`
+- `notifications.openclaw.hooks["stop"].instruction`
+- `notifications.openclaw.hooks["session-end"].instruction`
+
+## Tokens de contexto recomendados
+
+- Siempre: `{{sessionId}}`, `{{tmuxSession}}`
+- Según evento: `{{projectName}}`, `{{question}}`, `{{reason}}`
+
+## Estrategia de verbosidad
+
+- `minimal`: avisos muy cortos
+- `session`: contexto operativo conciso (recomendado)
+- `verbose`: más contexto de estado, acción y riesgo
+
+## Comando rápido de actualización (jq)
+
+```bash
+CONFIG_FILE="$HOME/.codex/.rcs-config.json"
+
+jq '.notifications.verbosity = "verbose" |
+    .notifications.openclaw.hooks["session-start"].instruction = "[session-start|exec]\nproject={{projectName}} session={{sessionId}} tmux={{tmuxSession}}\n요약: 시작 맥락 1문장\n우선순위: 지금 할 일 1~2개\n주의사항: 리스크/의존성(없으면 없음)" |
+    .notifications.openclaw.hooks["session-idle"].instruction = "[session-idle|exec]\nsession={{sessionId}} tmux={{tmuxSession}}\n요약: idle 원인 1문장\n복구계획: 즉시 조치 1~2개\n의사결정: 사용자 입력 필요 여부" |
+    .notifications.openclaw.hooks["ask-user-question"].instruction = "[ask-user-question|exec]\nsession={{sessionId}} tmux={{tmuxSession}} question={{question}}\n핵심질문: 필요한 답변 1문장\n영향: 미응답 시 영향 1문장\n권장응답: 가장 빠른 답변 형태" |
+    .notifications.openclaw.hooks["stop"].instruction = "[session-stop|exec]\nsession={{sessionId}} tmux={{tmuxSession}}\n요약: 중단 사유\n현재상태: 저장/미완료 항목\n재개: 첫 액션 1개" |
+    .notifications.openclaw.hooks["session-end"].instruction = "[session-end|exec]\nproject={{projectName}} session={{sessionId}} tmux={{tmuxSession}} reason={{reason}}\n성과: 완료 결과 1~2문장\n검증: 확인/테스트 결과\n다음: 후속 액션 1~2개"'   "$CONFIG_FILE" > "$CONFIG_FILE.tmp" && mv "$CONFIG_FILE.tmp" "$CONFIG_FILE"
+```