RSP 3.2.0

RSP 3.2.0

RSP 3.2.0 makes agent control flow easier to reason about and everyday work easier to scan. It unifies route and ownership decisions across Core and Manage, adds human-readable work summaries without weakening stable identities, and reduces routine Skill context while preserving the existing authority boundaries.

Explicit control and managed execution

• Use one transient control model across Core, Shape, Discipline Skills, and Manage, with explicit route, owner, stop, resume, acceptance, and closeout outcomes.
• Keep Core responsible for resolving the WorkRef owner and selecting direct, specialist, managed, shaping, or stopped routes.
• Let a selected Manage run own same-goal execution, evidence-frontier decisions, review convergence, acceptance, and eligible closeout until a real route boundary changes.
• Select automatic Manage for non-small and multi-surface completion work while keeping settled one-step work direct.
• Preserve specialist routing for fixed-scope review, release operations, and isolated design questions.
• Keep controller state transient: Changes, Group Briefs, Specs, Decision Records, Git history, and published artifacts remain the durable owners.

Clearer work identity and presentation

• Add human-readable Change and Group summaries to rsp status --json, plain status, the terminal dashboard, and archive history.
• Keep canonical WorkRefs unchanged as stable machine identities, even when their summaries or surrounding narration use another language.
• Default newly inferred WorkRefs to ASCII lowercase kebab-case when neither the user nor project authority specifies a naming convention.
• Preserve explicit Unicode WorkRefs, project-owned naming policies, and every existing open or archived identity.
• Localize human-facing progress, route, stop, and handoff narration independently from artifact language, commit language, canonical commands, paths, and enum values.

Leaner Skill loading

• Clarify the distinction between default suite Skills and optional project Skills without changing the packaged inventory.
• Reduce the generated fallback protocol to the safety kernel needed when the full rsp Skill cannot be loaded.
• Move inactive Manage interruption, review-convergence, and closeout procedures behind conditional loading.
• Let code-only and document-only reviews load only their applicable detailed pipeline while mixed reviews retain both.
• Replace high-amplification wording assertions with semantic contract helpers where exact prose is not itself the public contract.

Upgrade

RSP 3.2 requires Node.js 22 or later. Existing 3.1 projects need no dedicated migration. Use the stable package, then refresh the managed fallback and package-owned Skills separately:

npx -y @oevery/rsp@latest update
npx -y @oevery/rsp@latest skills install --dry-run
npx -y @oevery/rsp@latest skills install
npx -y @oevery/rsp@latest doctor

Existing Change, Group, archive, Spec, Decision Record, configuration, and WorkRef identities remain compatible. The new summary projections are additive presentation fields derived from existing authored content.

Compatibility and known limitations

• Automatic Manage activation selects a controller only; it does not grant planning, product mutation, lifecycle, Git, publication, deployment, approval, or human-acceptance authority.
• ASCII lowercase kebab-case is only the fallback for newly inferred WorkRefs. RSP does not rename existing identities or override an explicit user or project convention.
• Human-readable summaries are derived from authored frontmatter, Proposal outcomes, or Group goals. Missing or placeholder summaries remain absent rather than replacing canonical identities.
• The managed control model is covered by deterministic contracts and bounded repository evaluations. Provider behavior, broad productivity comparisons, and real-world acceptance outside the observed scenarios remain unclaimed.
• Commit, tag, push, hosted release creation, registry publication, deployment, and approval remain separately authorized operations.

Full comparison: v3.1.1...v3.2.0