@jstn-sdk/rcs 0.1.6 → 0.1.8

package/src/scripts/surface-taxonomy.ts

@@ -260,14 +260,9 @@ export function buildSurfaceMapMarkdown(records: SurfaceTaxonomyRecord[]): strin
     '',
     ...renderTable(internal),
     '',
-    '## Historical Surfaces',
-    '',
-    ...renderTable(historical),
-    '',
     '## Additional Repo Lanes',
     '',
     '- `AGENTS.md` and `templates/AGENTS.md` remain the orchestration brain and guidance authority.',
-    '- `docs/archive/` is the historical lane; archive content may describe removed surfaces but must not act as active onboarding.',
     '- `src/catalog/manifest.json`, `templates/catalog-manifest.json`, and `src/catalog/generated/public-catalog.json` are the catalog source/generated contract lane.',
     '- `dist/` is generated runtime output and should reflect the taxonomy, not redefine it.',
     '',

package/templates/roblox/llm-provider-routing.json

@@ -0,0 +1,42 @@
+{
+  "providers": {
+    "openrouter": {
+      "base_url": "https://openrouter.ai/api/v1",
+      "api_format": "openai-compatible",
+      "env_key": "OPENROUTER_API_KEY",
+      "capabilities": [
+        "chat",
+        "reasoning"
+      ],
+      "label": "OpenRouter"
+    },
+    "anthropic_proxy": {
+      "base_url": "https://proxy.example.com/anthropic",
+      "api_format": "anthropic",
+      "env_key": "ANTHROPIC_PROXY_KEY",
+      "capabilities": [
+        "chat",
+        "long-context"
+      ],
+      "label": "Anthropic Proxy"
+    }
+  },
+  "routing": {
+    "default_provider": "openrouter",
+    "mode_providers": {
+      "forge": "openrouter",
+      "team": "anthropic_proxy"
+    },
+    "fallback_providers": [
+      "openrouter"
+    ],
+    "mode_fallback_providers": {
+      "forge": [
+        "openrouter",
+        "anthropic_proxy"
+      ]
+    },
+    "hot_swap": true,
+    "failover": true
+  }
+}

package/templates/roblox/reference-sources.md

@@ -0,0 +1,33 @@
+# Roblox Reference Sources
+
+Use this inventory when a Roblox task needs external grounding before implementation.
+
+## Official platform truth
+
+- `https://github.com/Roblox/creator-docs`
+- `https://gitmcp.io/Roblox/creator-docs`
+
+## Roblox implementation guidance
+
+- `https://github.com/sentinelcore/roblox-skills`
+- `https://gitmcp.io/sentinelcore/roblox-skills`
+- `https://github.com/greedychipmunk/agent-skills/tree/main/roblox-game-developer`
+- `https://github.com/omer-metin/skills-for-antigravity/tree/main/skills/roblox-development`
+- `https://github.com/dig1t/skills`
+- `https://github.com/Corecii/Devprod`
+- `https://gitmcp.io/Corecii/Devprod`
+
+## Raw script / corpus support
+
+- `https://github.com/retpirato/Roblox-Scripts`
+- `https://gitmcp.io/retpirato/Roblox-Scripts`
+- `https://gitmcp.io/frosteen/Roblox_LUA_Weapon_Scripts`
+- `https://gitmcp.io/uhub/awesome-lua`
+- `https://gitmcp.io/LewisJEllis/awesome-lua`
+- `https://gitmcp.io/forhappy/awesome-lua`
+- `http://lua-users.org/wiki/SampleCode`
+
+Rules:
+- official docs define correctness
+- skill repos improve implementation awareness
+- corpora are not trusted production code

package/docs/archive/README.md

@@ -1,15 +0,0 @@
-# Archive Docs
-
-This directory holds historical or migration-only collateral that is **not** part of the active
-RCS product surface.
-
-Archive docs may include:
-- migration changelogs
-- old release-body collateral
-- transitional QA snapshots
-- historical restructuring notes
-
-Rules:
-- do not use archive docs as active onboarding or canonical runtime guidance
-- if a file in `docs/archive/` is still needed by active runtime/code/tests, it should move back out
-- active source-of-truth docs stay under the main `docs/`, `docs/reference/`, `docs/contracts/`, and `docs/qa/` surfaces

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

@@ -1,90 +0,0 @@
-# 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/archive/prompt-migration-changelog.md

@@ -1,141 +0,0 @@
-# Prompt Migration Changelog
-
-## Scope
-
-- Migration window: `e21cb5e` -> `ff7ee14`
-- Surface: `prompts/*.md` (30 files)
-- Goal: document the prior XML-to-Markdown migration while reaffirming that prompt files remain the canonical XML-tagged subagent role surfaces for RCS.
-
-## Global Changes (Applied to All Prompt Files)
-
-- Preserved frontmatter metadata (`description`, `argument-hint`).
-- Replaced wrapper tags such as `<Agent_Prompt>`, `<Role>`, `<Constraints>`, `<Output_Format>`, `<Final_Checklist>` with Markdown section headings.
-- Flattened nested XML-like sections into readable Markdown bullets/numbered steps.
-- Kept role semantics, tool usage intent, guardrails, and checklist expectations functionally equivalent.
-- Important current-state clarification: although the prompt text is now Markdown-first, each file in `prompts/*.md` is still the canonical XML-tagged subagent role surface consumed by RCS install/generation flows.
-
-## Behavior Notes
-
-- No intentionally introduced functional behavior changes were made in this migration commit.
-- Behavior-relevant content (constraints, verification expectations, output templates) was preserved while syntax/formatting was normalized.
-- Any post-migration behavior differences are expected to come from readability and parser-compatibility improvements, not policy changes.
-
-## Per-File Matrix
-
-| Prompt File | Added | Removed | Structural Highlights | Behavior Delta |
-|---|---:|---:|---|---|
-| `prompts/analyst.md` | 102 | 105 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/architect.md` | 102 | 104 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/build-fixer.md` | 81 | 84 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/code-reviewer.md` | 98 | 100 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/critic.md` | 79 | 82 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/debugger.md` | 85 | 88 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/deep-executor.md` | 105 | 107 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/dependency-expert.md` | 91 | 94 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/designer.md` | 96 | 98 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/executor.md` | 92 | 94 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/explore.md` | 104 | 107 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/git-master.md` | 84 | 87 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/planner.md` | 108 | 111 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/researcher.md` | 88 | 91 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/scientist.md` | 84 | 87 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/security-reviewer.md` | 119 | 121 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/test-engineer.md` | 96 | 98 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/verifier.md` | 87 | 90 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/vision.md` | 67 | 70 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-| `prompts/writer.md` | 78 | 81 | XML-like wrapper blocks converted to Markdown section hierarchy; output/checklist sections normalized. | No intentional functional delta in migration commit. |
-
-## Validation
-
-- Commit diff summary: `30 files changed, 2439 insertions(+), 2511 deletions(-)`
-- Spot-checks performed on role-heavy prompts (`planner`, `executor`, `explore`) confirmed semantic parity with formatting normalization.
-
----
-
-## Orchestration Brain Migration (`AGENTS.md`, `templates/AGENTS.md`)
-
-### Summary
-
-These files are the instruction root that RCS expects Codex to follow across a workspace.
-Changes here are primarily about aligning instructions with Codex CLI tool contracts.
-
-### Key Deltas
-
-- Updated child-agent delegation guidance to reflect the Codex `spawn_agent` API:
-  - Use `spawn_agent(message: "<role prompt>\n\nTask: ...")` conventions.
-  - Removed legacy "instructions" phrasing.
-- Expanded MCP tooling catalog and mode lifecycle expectations so orchestrators can use the full MCP surface correctly.
-- `templates/AGENTS.md` header normalized to match `AGENTS.md` and removed the non-compliant template opener.
-
-### Diff Stats
-
-| File | Added | Removed | Notes |
-|---|---:|---:|---|
-| `AGENTS.md` | 42 | 10 | Tooling + delegation guidance expanded; semantics preserved. |
-| `templates/AGENTS.md` | 7 | 7 | Header/tone normalized; still intended as a template copy. |
-
-### Unified Guidance Schema Follow-Up (AGENTS + Runtime/Worker Alignment)
-
-- Added canonical schema document: `docs/guidance-schema.md`.
-- Added explicit schema-contract sections to:
-  - `AGENTS.md`
-  - `templates/AGENTS.md`
-- Normalized worker task guidance in `AGENTS.md` runtime worker overlay:
-  - file path now uses `tasks/task-<id>.json`
-  - API id rule now explicitly requires bare id `task_id: "<id>"` (never `"task-<id>"`).
-- Marker contracts remain unchanged:
-  - `<!-- RCS:RUNTIME:START --> ... <!-- RCS:RUNTIME:END -->`
-  - `<!-- RCS:TEAM:WORKER:START --> ... <!-- RCS:TEAM:WORKER:END -->`
-
-Behavior note: this follow-up is additive and wording-focused; no task-state model or MCP API contract changes were introduced.
-
----
-
-## Skill Prompt Migration (`skills/*/SKILL.md`)
-
-### Summary
-
-Skill docs are operational runbooks. The migration focused on:
-- Removing Claude-era paths/terminology
-- Aligning config guidance with Codex-first paths (`~/.codex/…`, `CODEX_HOME`)
-- Preserving each skill's contract/intent while improving correctness for Codex CLI users
-
-### Behavior Notes
-
-- These are documentation / instruction changes; they do not directly change runtime logic.
-- One meaningful correction was made: the "agent teams" enablement guidance in `skills/rcs-setup/SKILL.md` was updated to enable Codex features via `~/.codex/config.toml` rather than legacy `settings.json` env vars.
-
-### Per-File Matrix
-
-| Skill File | Added | Removed | Structural Highlights | Behavior Delta |
-|---|---:|---:|---|---|
-| `skills/analyze/SKILL.md` | 1 | 1 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/autopilot/SKILL.md` | 11 | 16 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/code-review/SKILL.md` | 1 | 1 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/configure-notifications/SKILL.md` | 0 | 0 | Canonical notification setup skill replacing standalone configure-* variants. | Catalog/install surface now converges on one entry point. |
-| `skills/doctor/SKILL.md` | 47 | 45 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/ecomode/SKILL.md` | 1 | 1 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/help/SKILL.md` | 1 | 1 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/learner/SKILL.md` | 5 | 5 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/rcs-setup/SKILL.md` | 144 | 156 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/plan/SKILL.md` | 1 | 1 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/project-session-manager/SKILL.md` | 5 | 5 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/release/SKILL.md` | 3 | 3 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/research/SKILL.md` | 10 | 15 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/security-review/SKILL.md` | 1 | 1 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/skill/SKILL.md` | 20 | 20 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/tdd/SKILL.md` | 1 | 1 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/ultrapilot/SKILL.md` | 11 | 16 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-| `skills/writer-memory/SKILL.md` | 1 | 1 | Codex path/terminology normalization; examples updated to Codex-first conventions. | No direct runtime behavior change; instruction correctness improved. |
-
-### Hotspots Worth Reviewing
-
-- `skills/rcs-setup/SKILL.md`: largest edit surface; includes team enablement guidance (`~/.codex/config.toml` `[features]` flags) and teammate display preference storage (`~/.codex/.rcs-config.json`).
-- `skills/doctor/SKILL.md`: updated hook/config inspection language; still contains optional legacy remediation guidance.
-- `skills/autopilot/SKILL.md`, `skills/research/SKILL.md`, `skills/ultrapilot/SKILL.md`: config examples updated to TOML.
-
-## Follow-up Classification Notes
-
-- `prompts/*.md` should be treated as the canonical source set for XML-tagged subagent role prompts, even when install/runtime layers wrap them in TOML or other launcher-specific envelopes.
-- `prompts/sisyphus-lite.md` is intentionally classified as a specialized worker behavior prompt. It is not part of the primary public role catalog alongside prompts such as `executor`, `planner`, or `architect`.
-- Team worker/runtime overlays may borrow Sisyphus-lite behavior patterns, but that does not promote it to a first-class routed role.

package/docs/archive/qa-plan-0.4.2.md

@@ -1,85 +0,0 @@
-# QA Plan — v0.4.2 (dev vs deployed main)
-
-Date: 2026-02-18  
-Scope: validate delta between `origin/main` (deployed, `v0.4.1`) and current `dev`.
-
-## 1) Parity Validation Summary
-
-Run:
-
-```bash
-git fetch origin --prune
-git rev-list --left-right --count origin/main...dev
-git log --oneline origin/main..dev
-git diff --name-status origin/main...dev
-```
-
-Expected at time of writing:
-- `origin/main` is deployed at `v0.4.1`.
-- `dev` is ahead with feature/fix/test commits (auto-nudge improvements, all-workers-idle leader notification, tmux input/scrolling fixes, and coverage expansion).
-- No non-merge functional commits were found on `main` that are missing from `dev`.
-
-## 2) Risk-Based Focus Areas
-
-1. **Notify hook behavior**
-   - Expanded stall phrase detection and new hot-zone detection logic.
-   - All-workers-idle leader notification with cooldown/event logging.
-2. **Tmux team UX/reliability**
-   - Mouse scrolling enabled by default for team sessions.
-   - `sendToWorker` timing changes around submit rounds.
-3. **Config compatibility**
-   - `collab` -> `multi_agent` migration in generated config + tests/docs.
-4. **Lifecycle/process handling**
-   - `bin/rcs.js` now awaits `main(...)` and exits explicitly.
-
-## 3) Automated QA
-
-```bash
-npm run test:run
-```
-
-Pass criteria:
-- Full suite passes.
-- New/updated suites specifically pass:
-  - `src/hooks/__tests__/notify-hook-all-workers-idle.test.ts`
-  - `src/hooks/__tests__/notify-hook-auto-nudge.test.ts`
-  - `src/team/__tests__/tmux-session.test.ts`
-  - `src/config/__tests__/generator-notify.test.ts`
-  - newly added extensibility/HUD/utils/verifier test files
-
-## 4) Manual QA Checklist
-
-### A. All workers idle notification
-- Start a team session with >=2 workers.
-- Let all workers transition to `idle` or `done`.
-- Verify leader receives one idle-summary prompt.
-- Re-trigger within cooldown window: verify no duplicate notification spam.
-- Verify event/log entries are emitted.
-
-### B. Auto-nudge pattern detection
-- Feed outputs containing new phrases (e.g., "say go", "next I can", "keep driving").
-- Verify stall detection triggers in the last-lines hot zone.
-- Verify unrelated text does not false-trigger.
-
-### C. Tmux input reliability + mouse scrolling
-- In team mode, verify mouse wheel scrolls pane history.
-- Confirm arrow keys still work for CLI input history.
-- Send repeated worker prompts and verify submission consistency.
-- Set `RCS_TEAM_MOUSE=0`, restart session, verify mouse mode is not forcibly enabled.
-
-### D. Config generator migration
-- Run setup/generator path on fresh and existing configs.
-- Verify `[features]` includes `multi_agent = true` and `child_agents_md = true`.
-- Verify deprecated `collab` key is not reintroduced.
-
-### E. `/exit` process termination
-- Launch `rcs` and invoke `/exit`.
-- Verify process exits cleanly without hanging.
-
-## 5) Release Gate
-
-Release is approved only if:
-- [ ] Automated tests pass.
-- [ ] Manual checklist A–E passes.
-- [ ] Changelog entry matches shipped behavior.
-- [ ] Version is bumped consistently (`package.json`, `package-lock.json`).

package/docs/archive/qa-report-0.4.2.md

@@ -1,55 +0,0 @@
-# QA Execution Report — v0.4.2
-
-Date: 2026-02-18
-
-## Team Execution
-
-- Team run executed via `$team`.
-- Initial stale workers were detected and cleaned (`%1749`, `%1750` panes removed).
-- QA team completed with all tasks terminal (`completed=3, failed=0`) and was shut down cleanly.
-
-## Parity Validation (deployed `main` vs `dev`)
-
-Commands:
-
-```bash
-git rev-list --left-right --count origin/main...dev
-git rev-list --left-right --count --no-merges origin/main...dev
-git log --oneline --no-merges dev..origin/main
-```
-
-Result:
-- Merge-aware divergence: `6 18`
-- Non-merge divergence: `0 15`
-- No non-merge commits on `main` missing from `dev`.
-
-## Automated QA
-
-Command executed:
-
-```bash
-npm test
-```
-
-Result:
-- PASS — `664` tests passed, `0` failed.
-
-Notes:
-- `npm run test:run` is referenced in the QA plan but is not a script in current `package.json`.
-
-## Release-Metadata Checks
-
-- `package.json` version: `0.4.2`
-- `package-lock.json` version: `0.4.2`
-- `CHANGELOG.md` contains `## [0.4.2] - 2026-02-18`
-
-## Manual QA Checklist (A–E)
-
-- A/B/C/E require interactive runtime validation and were only partially validated through automated tests + code-path checks in this execution.
-- D (config migration) covered by automated tests (`generator-notify` + config generator suite) and passed.
-
-## Overall
-
-- Automated quality gate: **PASS**
-- Parity validation gate: **PASS**
-- Manual interactive gate: **PARTIAL (requires explicit interactive pass if required before release)**

package/docs/archive/release-body-0.9.0.md

@@ -1,86 +0,0 @@
-# RCS v0.9.0
-
-<p align="center">
-  <img src="./shared/rcs-character-spark-initiative.jpg" alt="RCS character sparked for the Spark Initiative" width="720">
-</p>
-
-`0.9.0` is the Spark Initiative release: RCS now has a stronger native fast path for repository discovery, shell-native inspection, and cross-platform native distribution.
-
-## Highlights
-
-### `rcs explore`
-
-- adds a dedicated read-only exploration entrypoint
-- uses a Rust-backed explore harness
-- keeps shell-native exploration constrained, allowlisted, and read-only
-- supports packaged native resolution plus source/repo-local fallback paths
-
-### `rcs sparkshell`
-
-- adds an operator-facing native shell sidecar
-- supports direct command execution
-- summarizes long output into compact sections
-- supports explicit tmux-pane summarization:
-
-```bash
-rcs sparkshell --tmux-pane %12 --tail-lines 400
-```
-
-### Explore ↔ sparkshell integration
-
-- qualifying read-only shell-native `rcs explore` prompts can route through `rcs sparkshell`
-- fallback behavior remains explicit and hardened
-- guidance/docs/tests were aligned around this contract
-
-### Worker follow-through polish
-
-- worker mailbox guidance now asks for concrete progress updates without implying work should stop after replying
-- inbox/mailbox trigger wording now tells workers to continue assigned or next feasible work after reporting status
-- runtime/bootstrap wording and associated tests were aligned around this behavior
-
-### Release pipeline upgrades
-
-- cross-platform native publishing for:
-  - `rcs-explore-harness`
-  - `rcs-sparkshell`
-- native release manifest generation with per-target metadata
-- packed-install smoke verification in the release workflow
-- `build:full` validated as the one-shot release-oriented build path
-
-## Important Spark Initiative notes
-
-- Users can install RCS normally with `npm install -g @jstn-sdk/rcs`.
-- The npm tarball intentionally excludes staged cross-platform native binaries.
-- Tagged releases publish verified native archives for `rcs-explore-harness` and `rcs-sparkshell`.
-- Packaged installs hydrate the matching native binary through `native-release-manifest.json`.
-- CI now hardens the Rust path with explicit toolchain setup, `cargo fmt --all --check`, and `cargo clippy --workspace --all-targets -- -D warnings`.
-
-## Upgrade note
-
-If you use project-scoped RCS installs, rerun:
-
-```bash
-rcs setup --force --scope project
-```
-
-after upgrading so managed config/native-agent paths are refreshed.
-
-## Local release verification summary
-
-Validated locally on `dev` before tagging:
-
-- `node scripts/check-version-sync.mjs --tag v0.9.0`
-- `npm run lint`
-- `npx tsc --noEmit`
-- `npm run check:no-unused`
-- `npm test`
-- `npm run build:full`
-- `npm run test:explore`
-- `npm run test:sparkshell`
-- `node bin/rcs.js doctor`
-- `node bin/rcs.js setup --dry-run`
-- `npm pack --dry-run`
-
-## Historical note
-
-This archived release note is retained for product history, but current first-party release ownership lives on the current RCS repository and package coordinates.

package/docs/archive/release-body-0.9.1.md

@@ -1,41 +0,0 @@
-# RCS v0.9.1
-
-<p align="center">
-  <img src="./shared/rcs-character-spark-initiative.jpg" alt="RCS character sparked for the Spark Initiative" width="720">
-</p>
-
-`0.9.1` is a targeted Spark Initiative hotfix release.
-
-## Why this release exists
-
-- `v0.9.0` remains historically red.
-- The required packed-install smoke hydration fix landed in the post-0.9.0 line and is reflected here as the superseding hotfix cut.
-- `v0.9.1` is the clean superseding release cut from `main` with that fix applied.
-
-## Included fix
-
-### Localize smoke hydration assets
-
-The packed-install smoke workflow now copies and resolves hydration assets from the local smoke workspace so release verification matches packaged-install behavior more reliably.
-
-Changed files:
-- `scripts/smoke-packed-install.mjs`
-- `scripts/__tests__/smoke-packed-install.test.mjs`
-
-## Local release verification summary
-
-Planned local release-critical validation for `0.9.1`:
-
-- `node scripts/check-version-sync.mjs --tag v0.9.1`
-- `npm run lint`
-- `npx tsc --noEmit`
-- `npm run check:no-unused`
-- `npm test`
-- `node --test scripts/__tests__/smoke-packed-install.test.mjs`
-- `npm run build:full`
-- `npm run smoke:packed-install`
-- `npm pack --dry-run`
-
-## Historical note
-
-`v0.9.0` remains historically red; `v0.9.1` is the clean superseding release.

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

@@ -1,38 +0,0 @@
-# Issue Draft: Make `blueprint` first-class for `team` follow-up planning
-
-## Title
-[Feature] Make `blueprint` emit explicit `team` follow-up guidance (for example `--followup team`)
-
-## Problem
-RCS already has the ingredients for a strong high-control workflow: `blueprint` for scoped planning and `team` for durable multi-worker execution with its own verification lanes. 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 `blueprint`, then launch `team`, and let team own delivery plus verification unless a later single-owner follow-up is genuinely needed. 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 `blueprint` 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 standalone `team` execution path, plus optional later Forge follow-up guidance only when needed
-
-This would make the intended workflow clearer:
-
-```text
-blueprint -> team
-```
-
-## 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 coordination flow.
-- Makes one of RCS's strongest workflows more discoverable for advanced users.
-- Improves execution quality on runtime-edge-case and workflow-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 `blueprint`, sees a plan that is already shaped for team execution, launches `team` with less guesswork, and only escalates to `forge` later if a persistent single-owner follow-up is still needed after team execution.