@jstn-sdk/rcs 0.1.0

package/.agents/plugins/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "rcs-local",
+  "interface": {
+    "displayName": "RCS Local Plugins"
+  },
+  "plugins": [
+    {
+      "name": "roblox-ai-os-creator-skills",
+      "source": {
+        "source": "local",
+        "path": "./plugins/roblox-ai-os-creator-skills"
+      },
+      "policy": {
+        "installation": "AVAILABLE",
+        "authentication": "ON_INSTALL"
+      },
+      "category": "Developer Tools"
+    }
+  ]
+}

package/Cargo.lock

@@ -0,0 +1,174 @@
+# This file is automatically @generated by Cargo.
+# It is not intended for manual editing.
+version = 3
+
+[[package]]
+name = "fs2"
+version = "0.4.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9564fc758e15025b46aa6643b1b77d047d1a56a1aea6e01002ac0c7026876213"
+dependencies = [
+ "libc",
+ "winapi",
+]
+
+[[package]]
+name = "itoa"
+version = "1.0.17"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "92ecc6618181def0457392ccd0ee51198e065e016d1d527a7ac1b6dc7c1f09d2"
+
+[[package]]
+name = "libc"
+version = "0.2.183"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b5b646652bf6661599e1da8901b3b9522896f01e736bad5f723fe7a3a27f899d"
+
+[[package]]
+name = "memchr"
+version = "2.8.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f8ca58f447f06ed17d5fc4043ce1b10dd205e060fb3ce5b979b8ed8e59ff3f79"
+
+[[package]]
+name = "proc-macro2"
+version = "1.0.106"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8fd00f0bb2e90d81d1044c2b32617f68fcb9fa3bb7640c23e9c748e53fb30934"
+dependencies = [
+ "unicode-ident",
+]
+
+[[package]]
+name = "quote"
+version = "1.0.45"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "41f2619966050689382d2b44f664f4bc593e129785a36d6ee376ddf37259b924"
+dependencies = [
+ "proc-macro2",
+]
+
+[[package]]
+name = "rcs-explore-harness"
+version = "0.1.0"
+
+[[package]]
+name = "rcs-mux"
+version = "0.1.0"
+dependencies = [
+ "serde",
+ "serde_json",
+]
+
+[[package]]
+name = "rcs-runtime"
+version = "0.1.0"
+dependencies = [
+ "rcs-mux",
+ "rcs-runtime-core",
+ "serde_json",
+]
+
+[[package]]
+name = "rcs-runtime-core"
+version = "0.1.0"
+dependencies = [
+ "fs2",
+ "serde",
+ "serde_json",
+]
+
+[[package]]
+name = "rcs-sparkshell"
+version = "0.1.0"
+dependencies = [
+ "rcs-mux",
+]
+
+[[package]]
+name = "serde"
+version = "1.0.228"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9a8e94ea7f378bd32cbbd37198a4a91436180c5bb472411e48b5ec2e2124ae9e"
+dependencies = [
+ "serde_core",
+ "serde_derive",
+]
+
+[[package]]
+name = "serde_core"
+version = "1.0.228"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "41d385c7d4ca58e59fc732af25c3983b67ac852c1a25000afe1175de458b67ad"
+dependencies = [
+ "serde_derive",
+]
+
+[[package]]
+name = "serde_derive"
+version = "1.0.228"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d540f220d3187173da220f885ab66608367b6574e925011a9353e4badda91d79"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "serde_json"
+version = "1.0.149"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "83fc039473c5595ace860d8c4fafa220ff474b3fc6bfdb4293327f1a37e94d86"
+dependencies = [
+ "itoa",
+ "memchr",
+ "serde",
+ "serde_core",
+ "zmij",
+]
+
+[[package]]
+name = "syn"
+version = "2.0.117"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e665b8803e7b1d2a727f4023456bbbbe74da67099c585258af0ad9c5013b9b99"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "unicode-ident",
+]
+
+[[package]]
+name = "unicode-ident"
+version = "1.0.24"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e6e4313cd5fcd3dad5cafa179702e2b244f760991f45397d14d4ebf38247da75"
+
+[[package]]
+name = "winapi"
+version = "0.3.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
+dependencies = [
+ "winapi-i686-pc-windows-gnu",
+ "winapi-x86_64-pc-windows-gnu",
+]
+
+[[package]]
+name = "winapi-i686-pc-windows-gnu"
+version = "0.4.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
+
+[[package]]
+name = "winapi-x86_64-pc-windows-gnu"
+version = "0.4.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
+
+[[package]]
+name = "zmij"
+version = "1.0.21"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b8848ee67ecc8aedbaf3e4122217aff892639231befc6a1b58d29fff4c2cabaa"

package/Cargo.toml

@@ -0,0 +1,23 @@
+[workspace]
+members = [
+  "crates/rcs-explore",
+  "crates/rcs-mux",
+  "crates/rcs-runtime-core",
+  "crates/rcs-runtime",
+  "crates/rcs-sparkshell",
+]
+resolver = "2"
+
+[workspace.package]
+
+version = "0.1.0"
+
+edition = "2021"
+rust-version = "1.73"
+license = "MIT"
+repository = "https://github.com/JustineDevs/roblox-ai-os"
+
+# The profile that 'dist' will build with
+[profile.dist]
+inherits = "release"
+lto = "thin"

package/README.md

@@ -0,0 +1,403 @@
+# RCS - Roblox Creator Skills
+
+[![npm version](https://img.shields.io/npm/v/%40jstn-sdk%2Frcs)](https://www.npmjs.com/package/@jstn-sdk/rcs)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Node.js](https://img.shields.io/badge/node-%3E%3D20-brightgreen)](https://nodejs.org)
+
+RCS is the Roblox Creator Skills runtime and workflow layer for [OpenAI Codex CLI](https://github.com/openai/codex). It is owned by **JustineDevs** and ships creator-oriented briefing, blueprinting, forging, crew orchestration, and psychology-aware design workflows on top of Codex.
+
+**Package:** `@jstn-sdk/rcs`  
+**Repo:** `https://github.com/JustineDevs/roblox-ai-os`  
+**Docs:** [Getting Started](./docs/getting-started.html) · [Skills](./docs/skills.html) · [Agents](./docs/agents.html) · [Integrations](./docs/integrations.html) · [OpenClaw guide](./docs/openclaw-integration.md)
+
+<table>
+<tr>
+<td><strong>🚨 CAUTION — RECOMMENDED DEFAULT ONLY: macOS or Linux with Codex CLI.</strong><br><br><strong>RCS is primarily designed and actively tuned for that path.</strong><br><strong>Native Windows and Codex App are not the default experience, may break or behave inconsistently, and currently receive less support.</strong></td>
+</tr>
+</table>
+
+It keeps Codex as the execution engine and makes it easier to:
+- start a stronger Codex session by default
+- run one consistent workflow from briefing to execution handoff
+- invoke creator-facing workflows with `$brief`, `$blueprint`, `$crew`, `$forge`, and `$autoforge`
+- design Roblox loops from player desire backward with psychology-aware commands for audience, motivation, progression, status, FOMO, mastery, community, retention, and LiveOps
+- force Roblox work through a mandatory pre-action gate before any code generation or refactor
+- keep project guidance, plans, logs, and state in `.rcs/`
+
+## Recommended default flow
+
+If you want the default RCS experience, start here:
+
+```bash
+npm install -g @openai/codex @jstn-sdk/rcs
+rcs --madmax --high
+```
+
+On a real RCS version bump, the global npm install prints an explicit reminder instead of auto-running setup. When you're ready, run `rcs setup` manually or use `rcs update` to refresh the install and setup path together.
+
+**Codex plugin install note:** this repo also ships an official Codex plugin layout at `plugins/roblox-ai-os-creator-skills` with marketplace metadata in `.agents/plugins/marketplace.json`. That plugin bundles the mirrored skill surface plus plugin-scoped companion metadata for MCP servers and apps. Native/runtime hooks still stay on the setup/runtime side rather than the installable plugin manifest. It is still **not** a replacement for `npm install -g @jstn-sdk/rcs` plus `rcs setup`: setup/runtime wiring remains a first-class part of the product surface. Legacy setup mode installs native agents/prompts, while plugin setup mode archives stale legacy prompt/native-agent files and keeps runtime wiring current.
+
+Then work normally inside Codex:
+
+```text
+$brief "clarify the creator workflow change"
+$blueprint "approve the plan and review tradeoffs"
+$forge "carry the approved plan to completion"
+$crew "execute the approved plan in parallel"
+$autoforge "take a scoped creator workflow from brief to ship-ready outputs"
+```
+
+That is the main path.
+Before you treat the runtime as ready, run the quick-start smoke test below: `rcs doctor` verifies the install shape, while `rcs exec` proves the active Codex runtime can actually authenticate and complete a model call from the current environment.
+Start RCS strongly, clarify first when needed, approve the plan, then choose `$crew` for coordinated parallel execution or `$forge` for the persistent completion loop.
+
+## What RCS is for
+
+Use RCS if you already like Codex and want a better day-to-day runtime around it:
+- a standard workflow built around `$brief`, `$blueprint`, `$crew`, and `$forge`
+- a structured player-psychology design layer for retention, motivation, social stickiness, and monetization fit
+- specialist roles and supporting skills when the task needs them
+- project guidance through scoped `AGENTS.md`
+- durable state under `.rcs/` for plans, logs, memory, and mode tracking
+
+If you want plain Codex with no extra workflow layer, you probably do not need RCS.
+
+## Quick start
+
+### Requirements
+
+- Node.js 20+
+- Codex CLI installed: `npm install -g @openai/codex`
+- Codex auth configured and visible in the same shell/profile that will run RCS
+- `tmux` on macOS/Linux if you want the recommended durable team runtime
+- `psmux` on native Windows only if you intentionally want the less-supported Windows team path
+
+### A good first session
+
+After install, check both boundaries:
+
+```bash
+rcs doctor
+codex login status
+rcs exec --skip-git-repo-check -C . "Reply with exactly RCS-EXEC-OK"
+```
+
+`rcs doctor` catches missing RCS files, hooks, and runtime prerequisites. The real smoke test catches auth, profile, and provider/base-URL problems that only appear when Codex performs an actual request.
+
+Launch RCS the recommended way:
+
+```bash
+rcs --madmax --high
+```
+
+On macOS/Linux interactive terminals with `tmux` available, this starts the
+leader in RCS-managed detached tmux by default so the HUD/runtime panes can be
+created and recovered.
+
+If you want a one-off launch with no RCS tmux/HUD management, use `--direct`:
+
+```bash
+rcs --direct --yolo
+```
+
+For a persistent shell/profile preference, set an environment policy:
+
+```bash
+RCS_LAUNCH_POLICY=direct rcs --yolo
+```
+
+Return to the auto/default behavior with:
+
+```bash
+unset RCS_LAUNCH_POLICY
+```
+
+CLI policy flags win over the environment, and the last CLI policy flag before
+`--` wins:
+
+```bash
+RCS_LAUNCH_POLICY=direct rcs --tmux --yolo
+```
+
+Use `RCS_LAUNCH_POLICY=direct|tmux|detached-tmux|auto`. This iteration only
+adds CLI and environment controls; it intentionally does not add a config-file
+setting. If you run `--direct` from inside an existing tmux pane, RCS will not
+create HUD splits, enable mouse mode, or wrap extended-key handling, but the
+process still runs inside that already-open terminal pane.
+
+Then try the canonical creator workflow:
+
+```text
+$brief "clarify the creator workflow change"
+$blueprint "approve the safest implementation path"
+$forge "carry the approved plan to completion"
+$crew "execute the approved plan in parallel"
+```
+
+Use `$crew` when the approved plan needs coordinated parallel work, `$forge` when one persistent owner should keep pushing to completion, and `$autoforge` when you want the end-to-end creator workflow with minimal supervision.
+
+## A simple mental model
+
+RCS does **not** replace Codex.
+
+It adds a better working layer around it:
+- **Codex** does the actual agent work
+- **RCS role keywords** make useful roles reusable
+- **RCS skills** make common workflows reusable
+- **`.rcs/`** stores plans, logs, memory, and runtime state
+
+Most users should think of RCS as **better task routing + better workflow + better runtime**, not as a command surface to operate manually all day.
+
+## Start here if you are new
+
+1. Install or update RCS with `npm install -g @openai/codex @jstn-sdk/rcs`
+2. After install or real RCS version bumps, run `rcs setup` yourself when you're ready, or use `rcs update` when you also want npm to check for and install the latest build before refreshing setup
+3. Run `rcs doctor`
+4. Run a real execution smoke test: `codex login status` and `rcs exec --skip-git-repo-check -C . "Reply with exactly RCS-EXEC-OK"`
+5. Launch with `rcs --madmax --high`
+6. Use `$brief "..."` when the request or boundaries are still unclear
+7. Use `$blueprint "..."` to approve the plan and review tradeoffs
+8. Choose `$crew` for coordinated parallel execution or `$forge` for persistent completion loops
+
+## Recommended workflow
+
+1. `$brief` — clarify scope when the request or boundaries are still vague.
+2. `$blueprint` — turn that clarified scope into an approved architecture and implementation plan.
+3. `$crew` or `$forge` — use `$crew` for coordinated parallel execution, or `$forge` when you want a persistent completion loop with one owner.
+
+## Roblox Pre-Action Gate
+
+RCS does not allow Roblox implementation to begin from memory or improvisation. Before any Roblox code generation, asset logic, UI system, monetization design, plugin work, or refactor, the workflow must first:
+
+1. gather Roblox references
+2. synthesize understanding
+3. standardize official terms
+4. design modular architecture and file tree
+5. then implement
+
+The required planning shape is documented in:
+- [Roblox Pre-Action Protocol](./docs/reference/roblox-pre-action-protocol.md)
+- [Roblox Pre-Action Plan Template](./templates/roblox/pre-action-plan.md)
+
+`PRE_ACTION_COMPLETE` must be `true` before Roblox code generation is allowed.
+
+## Psychology-aware workflow
+
+RCS v0.1.0 adds a formal player-psychology layer for Roblox experience design. The system is behavior-first: define player desire, loop tension, social fit, progression pressure, and monetization guardrails before building feature count.
+
+### Briefing surfaces
+
+```text
+$brief:audience "farming simulator for short mobile sessions"
+$brief:motivation "anime battler with collection, flex, and co-op raid goals"
+```
+
+### Blueprint surfaces
+
+```text
+$blueprint:psych "social roleplay town with repeat visits and identity expression"
+$blueprint:loop "define session, daily, weekly, and comeback loops for a tycoon"
+$blueprint:retention "plan D1/D7/D30 assumptions for a pet collection simulator"
+$blueprint:social "turn a hangout game into a social machine"
+```
+
+### Forge surfaces
+
+```text
+$forge:reward-loop "reward spec for a farming loop with escalation and fail states"
+$forge:daily-loop "daily return plan for a creature collector"
+$forge:event-loop "limited-time summer event with urgency and re-entry logic"
+$forge:progression "progression ladder for a rebirth-heavy simulator"
+$forge:status "prestige and flex systems for a social roleplay game"
+$forge:fomo "fair urgency mechanics for a seasonal shop"
+$forge:mastery "skill-expression systems for a combat tactics game"
+$forge:community "social retention systems for guild, co-op, and party play"
+```
+
+The canonical framework covers five drivers:
+
+1. Progression
+2. Status
+3. FOMO
+4. Mastery
+5. Community
+
+Each driver is evaluated through player desire, mechanic patterns, UI feedback, economy effects, retention effects, monetization fit, abuse risk, and Roblox fit.
+
+## Common in-session surfaces
+
+| Surface | Use it for |
+| --- | --- |
+| `$brief "..."` | clarifying intent, boundaries, and non-goals |
+| `$brief:audience "..."` | target fantasy, session habits, pain/desire language, and return motive |
+| `$brief:motivation "..."` | dominant psychology drivers and anti-pattern risks |
+| `$blueprint "..."` | approving the implementation plan and tradeoffs |
+| `$blueprint:psych "..."` | player psychology blueprint from desire backward |
+| `$blueprint:loop "..."` | session/daily/weekly/comeback loop design |
+| `$blueprint:retention "..."` | D1/D7/D30 assumptions, cadence, and comeback hooks |
+| `$blueprint:social "..."` | party/trade/guild/co-op/social-presence design |
+| `$forge "..."` | persistent completion and verification loops |
+| `$forge:reward-loop "..."` | concrete reward-loop specs |
+| `$forge:daily-loop "..."` | return motivator specs |
+| `$forge:event-loop "..."` | event and urgency structures |
+| `$forge:progression "..."` | XP/level/prestige/rebirth ladders |
+| `$forge:status "..."` | visible prestige/flex systems |
+| `$forge:fomo "..."` | fair urgency mechanics with anti-frustration guardrails |
+| `$forge:mastery "..."` | skill-expression and optimization systems |
+| `$forge:community "..."` | social stickiness systems |
+| `$crew "..."` | coordinated parallel execution when the work is big enough |
+| `$autoforge "..."` | end-to-end creator workflow with minimal supervision |
+| `/skills` | browsing installed skills and supporting helpers |
+
+## Advanced / operator surfaces
+
+These are useful, but they are not the main onboarding path.
+
+### Lower-level team runtime
+
+Use the team runtime when you specifically need durable tmux/worktree coordination, not as the default way to begin using RCS. The public creator workflow remains `$brief -> $blueprint -> $forge / $crew -> $autoforge`. In Codex App or plain outside-tmux sessions, treat `rcs team` as a lower-level tmux-runtime shell surface rather than a directly available in-app workflow; launch RCS CLI from shell first if you actually want team execution.
+
+```bash
+rcs team 3:executor "fix the failing tests with verification"
+rcs team status <team-name>
+rcs team resume <team-name>
+rcs team shutdown <team-name>
+```
+
+### Setup, doctor, and HUD
+
+These are operator/support surfaces:
+- Codex plugin marketplace install/discovery can cache the plugin under `${CODEX_HOME:-~/.codex}/plugins/cache/$MARKETPLACE_NAME/roblox-ai-os-creator-skills/$VERSION/` (local installs may use `local` as the version identifier); that packaged plugin includes plugin-scoped companion metadata for MCP servers and apps, while native/runtime hooks remain setup-owned, so it is still not the full RCS runtime setup
+- `rcs setup` installs prompts, skills, AGENTS scaffolding, `.codex/config.toml`, and RCS-managed native Codex hooks in `.codex/hooks.json`
+  - setup refresh preserves non-RCS hook entries in `.codex/hooks.json` and only rewrites RCS-managed wrappers
+  - `rcs setup --merge-agents` preserves existing `AGENTS.md` guidance while inserting or refreshing generated RCS sections between `<!-- RCS:AGENTS:START -->` / `<!-- RCS:AGENTS:END -->`; without `--merge-agents` or `--force`, non-interactive setup keeps skipping existing `AGENTS.md` files
+  - `rcs uninstall` removes RCS-managed wrappers from `.codex/hooks.json` but keeps the file when user hooks remain
+- `rcs update` checks npm immediately, installs the newest global RCS build, then reruns the same interactive setup refresh path
+- fresh RCS-managed `gpt-5.5` config seeding now recommends `model_context_window = 250000` and `model_auto_compact_token_limit = 200000`, but only when those keys are missing
+- `.rcs-config.json` model/env routing is documented in [the model/env routing reference](./docs/reference/rcs-config-schema-routing.md); only edit keys supported by your installed RCS version
+- `rcs doctor` verifies the install when something seems wrong; it does not prove that the active Codex profile can make an authenticated model call
+- `rcs hud --watch` is a monitoring/status surface, not the primary user workflow
+
+For non-team sessions, native Codex hooks are now the canonical lifecycle surface:
+- `.codex/hooks.json` = native Codex hook registrations
+- `.rcs/hooks/*.mjs` = RCS plugin hooks
+- `rcs tmux-hook` / notify-hook / derived watcher = tmux + runtime fallback paths
+
+See [Codex native hook mapping](./docs/codex-native-hooks.md) for the current native / fallback matrix.
+
+
+### Troubleshooting false-green readiness
+
+A green `rcs doctor` means the install and local runtime wiring look sane. If real execution still fails, check the environment Codex actually uses:
+
+- Run `codex login status` and `rcs exec --skip-git-repo-check -C . "Reply with exactly RCS-EXEC-OK"` from the same shell/profile that will launch RCS.
+- In custom HOME, profile, container, or service shells, confirm the active `~/.codex` (or `CODEX_HOME`) is the one with the expected auth and config. Do not assume your normal user `~/.codex` is visible there.
+- If you depend on a local OpenAI-compatible proxy, confirm the active `~/.codex/config.toml` includes the expected `openai_base_url`; otherwise a proxy-issued key can be sent to the default endpoint and fail with `401 Unauthorized`, `Missing bearer or basic authentication in header`, or `Incorrect API key provided`.
+- If `rcs doctor --team` or resume reports a stale team such as `resume_blocker` or a missing tmux session, clean the dead runtime state before retrying:
+
+```bash
+rcs team shutdown <team-name> --force --confirm-issues
+rcs cancel
+rcs doctor --team
+```
+
+Only use the forced team shutdown for a team you have confirmed is dead or intentionally abandoned.
+
+If `Shift+Enter` still submits instead of inserting a newline inside an RCS-managed tmux session, see [Troubleshooting execution readiness](./docs/troubleshooting.md#shiftenter-submits-instead-of-inserting-a-newline-in-tmux-backed-rcs-sessions). Current RCS already enables tmux extended-key forwarding around its own Codex launch paths, so a persistent failure is usually a tmux terminal-capability/discoverability problem rather than a net-new RCS feature gap.
+
+### Explore and sparkshell
+
+- `rcs explore --prompt "..."` is for read-only repository lookup
+- `rcs sparkshell <command>` is for shell-native inspection and bounded verification
+- when `.rcs/wiki/` exists, `rcs explore` can inject wiki-first context before falling back to broader repository search
+- fallback boundaries are explicit: sparkshell-backend fallback is reported on stderr, and spark-model fallback emits stderr metadata plus an `## RCS Explore fallback` notice in stdout so users can see when cost/behavior may differ from the low-cost path
+
+Examples:
+
+```bash
+rcs explore --prompt "find where team state is written"
+rcs sparkshell git status
+rcs sparkshell --tmux-pane %12 --tail-lines 400
+```
+
+### Wiki
+
+- `rcs wiki` is the CLI parity surface for the RCS wiki MCP server
+- wiki data lives locally under `.rcs/wiki/`
+- the wiki is markdown-first and search-first, not vector-first
+
+Examples:
+
+```bash
+rcs wiki list --json
+rcs wiki query --input '{"query":"session-start lifecycle"}' --json
+rcs wiki lint --json
+rcs wiki refresh --json
+```
+
+### Platform notes for the lower-level team runtime
+
+`rcs team` works best on macOS/Linux with `tmux`.
+Native Windows remains a secondary path, and WSL2 is generally the better choice if you want a Windows-hosted setup.
+On native Windows, RCS accepts `psmux` as the tmux-compatible binary for the existing tmux-backed paths it already uses.
+
+| Platform | Install |
+| --- | --- |
+| macOS | `brew install tmux` |
+| Ubuntu/Debian | `sudo apt install tmux` |
+| Fedora | `sudo dnf install tmux` |
+| Arch | `sudo pacman -S tmux` |
+| Windows | `winget install psmux` |
+| Windows (WSL2) | `sudo apt install tmux` |
+
+## Known issues
+
+### Intel Mac: high `syspolicyd` / `trustd` CPU during startup
+
+On some Intel Macs, RCS startup — especially with `--madmax --high` — can spike `syspolicyd` / `trustd` CPU usage while macOS Gatekeeper validates many concurrent process launches.
+
+If this happens, try:
+- `xattr -dr com.apple.quarantine $(which rcs)`
+- adding your terminal app to the Developer Tools allowlist in macOS Security settings
+- using lower concurrency (for example, avoid `--madmax --high`)
+
+## Documentation
+
+- [Getting Started](./docs/getting-started.html)
+- [Demo guide](./DEMO.md)
+- [Wiki feature](./docs/wiki-feature.md)
+- [Agent catalog](./docs/agents.html)
+- [Skills reference](./docs/skills.html)
+- [Codex native hook mapping](./docs/codex-native-hooks.md)
+- [Integrations](./docs/integrations.html)
+- [Troubleshooting execution readiness](./docs/troubleshooting.md)
+- [OpenClaw / notification gateway guide](./docs/openclaw-integration.md)
+- [Contributing](./CONTRIBUTING.md)
+- [Changelog](./CHANGELOG.md)
+
+## Languages
+
+- [English](./README.md)
+- [한국어](./docs/readme/README.ko.md)
+- [日本語](./docs/readme/README.ja.md)
+- [简体中文](./docs/readme/README.zh.md)
+- [繁體中文](./docs/readme/README.zh-TW.md)
+- [Tiếng Việt](./docs/readme/README.vi.md)
+- [Español](./docs/readme/README.es.md)
+- [Português](./docs/readme/README.pt.md)
+- [Русский](./docs/readme/README.ru.md)
+- [Türkçe](./docs/readme/README.tr.md)
+- [Deutsch](./docs/readme/README.de.md)
+- [Français](./docs/readme/README.fr.md)
+- [Italiano](./docs/readme/README.it.md)
+- [Ελληνικά](./docs/readme/README.el.md)
+- [Polski](./docs/readme/README.pl.md)
+- [Українська](./docs/readme/README.uk.md)
+
+## Ownership
+
+RCS is owned and maintained by **JustineDevs** for Roblox creator workflows.
+
+## License
+
+MIT

package/crates/rcs-explore/Cargo.toml

@@ -0,0 +1,11 @@
+[package]
+name = "rcs-explore-harness"
+version.workspace = true
+edition.workspace = true
+rust-version.workspace = true
+license.workspace = true
+repository.workspace = true
+
+[[bin]]
+name = "rcs-explore-harness"
+path = "src/main.rs"