Skip to content
Resource
DocsTourSlicesBest PracticeAgentsInstall

Command Palette

Search for a command to run...

New
  • Changelog

Changelog

Release notes

Changelog

What changed in each rr release — page 8 of 25. Full prose history in CHANGELOG.md.

SEP132026
Featurefile-upload@0.4.0Sep 13, 2026

SvelteKit File Upload slice distribution

Related: https://resource.rahmanef.com/slices/file-upload — [before: file-upload pointed default installs at the missing frontend/slices/files path and exposed upload/UI behavior only through React hooks/components] → [after: React/Next remains the default on the real source path while an additive Svelte 5 / SvelteKit distribution preserves FileRef parsing, upload/remove, URL resolution, localStorage demo storage, file chips, upload controls, and bounded file tools]. Select it explicitly with rr add file-upload --framework sveltekit (or svelte).

Portable storage adapter parity

  • The React default path is corrected to frontend/slices/file-upload, while explicit SvelteKit installs copy a self-contained Svelte 5 distribution with no React, react-dom, Lucide, or React shadcn dependency.
  • The Svelte FilesAdapter replaces React-only useUrl hook semantics with resolveUrl plus optional subscribeUrl, preserving live URL invalidation capability while upload/remove/FileRef and dangerous files.remove tool semantics stay bounded.
SEP132026
Featureselection@0.3.0Sep 13, 2026

SvelteKit Selection slice distribution

Related: https://resource.rahmanef.com/slices/selection — [before: selection shipped only as a React/Next provider + marquee implementation] → [after: React/Next remains the default while an additive Svelte 5 / SvelteKit distribution preserves range/toggle selection, keyboard and bulk actions, selected-state attributes, and AutoCAD-style window/crossing marquee behavior]. Select it explicitly with rr add selection --framework sveltekit (or svelte).

Cross-framework selection parity

  • The Svelte selection model keeps select-only, toggle, contiguous range, clear, snapshot, and subscribable revision semantics while the provider preserves Escape/Delete/Backspace and click-outside behavior plus optional duplicate/delete actions.
  • The marquee keeps the 4px drag threshold, ignores touch and interactive descendants, supports additive Shift/Cmd/Ctrl baselines, and preserves rightward window versus leftward crossing hit-testing without React or react-dom.
SEP132026
Featurebooking@1.1.0Sep 13, 2026

SvelteKit Booking slice distribution

Related: https://resource.rahmanef.com/slices/booking — [before: booking shipped only as a React/Next form + owner inbox and mounted consumers did not react when the injected adapter was replaced at runtime] → [after: React/Next remains the default with reactive adapter replacement, while an additive Svelte 5 / SvelteKit distribution preserves the public form, owner inbox, triage actions, and injectable backend contract]. Select it explicitly with rr add booking --framework sveltekit (or svelte).

Cross-framework booking parity

  • The Svelte 5 component preserves required name/email/topic validation, optional preferred time/note fields, success/error feedback, owner inbox visibility, and Confirm/Decline actions through the same BookingAdapter semantics.
  • The Svelte distribution uses native controls and a stable subscribable host API; the React host now uses the established external-store revision pattern so runtime adapter replacement refreshes mounted consumers.
SEP132026
Featureseo@0.3.0Sep 13, 2026

SvelteKit SEO service distribution

Related: https://resource.rahmanef.com/slices/seo — [before: seo was installable only through the default React/Next framework contract even though its public service surface is framework-neutral TypeScript] → [after: React/Next remains the default while explicit Svelte/SvelteKit installs reuse the same framework-neutral SEO service contract without duplicated source or invented UI]. Select it explicitly with rr add seo --framework sveltekit (or svelte).

Shared framework-neutral service contract

  • The persona factory and typed SEO tool bindings remain one canonical pure-TypeScript source; the Svelte descriptor points to that same path instead of forking equivalent files.
  • No Svelte, React, Lucide, or shadcn UI dependency is introduced for the explicit SvelteKit distribution; existing Convex environment and convex-auth peer requirements continue unchanged.
SEP122026
Featurestart-here@1.0.0Sep 12, 2026

SvelteKit Start Here slice distribution

Related: https://resource.rahmanef.com/slices/start-here — [before: start-here was available only through the React/Next distribution] → [after: React/Next remains the default and an additive Svelte 5 / SvelteKit distribution shares the injected journey contract]. Explicit Svelte installs use rr add start-here --framework sveltekit (or svelte) and require only svelte@^5.

Framework-specific guided onboarding

  • Authored stage IDs resolve against the injected app catalog; unknown IDs and empty stages are filtered, visible numbering stays contiguous, and unplaced apps append automatically to Everything else.
  • The Svelte host keeps a stable delegated API identity while adapter replacement notifies subscribers, and each app action preserves aria-label="Open <title>" plus open(app.id) parity.
SEP112026
Featurefull-width-toggle@0.2.0Sep 11, 2026

SvelteKit Full Width Toggle slice distribution

Related: https://resource.rahmanef.com/slices/full-width-toggle — [before: full-width-toggle shipped only as the React/Next slice] → [after: React/Next remains the default and an additive Svelte 5 / SvelteKit distribution preserves the same width modes and persistence semantics]. Select it explicitly with rr add full-width-toggle --framework sveltekit (or svelte).

Framework-specific layout preference UI

  • Both distributions preserve contained, wide, and full layout classes plus the existing layout:widthMode localStorage key for per-device persistence.
  • The Svelte source keeps same-tab notification and cross-tab storage synchronization, uses native buttons/SVG icons, and requires only svelte@^5.
SEP112026
Featurefeedback-states@0.2.1Sep 11, 2026

SvelteKit Feedback States slice distribution

Related: https://resource.rahmanef.com/slices/feedback-states — [before: feedback-states shipped only as the React/Next slice] → [after: React/Next remains the default and an additive Svelte 5 / SvelteKit distribution provides equivalent loading, empty, and error-state primitives]. Select it explicitly with rr add feedback-states --framework sveltekit (or svelte).

Framework-specific source and dependencies

  • The Svelte source ships loading skeletons and spinners plus empty and error states without React, Next, shadcn, or icon dependencies; it requires only svelte@^5.
  • Both framework distributions retain loading and empty variant selection, so explicit framework choice changes only the copied source and declared dependencies.
SEP112026
Featuresite@framework-aware-slice-distributionSep 11, 2026

Framework-aware React/Next and Svelte/SvelteKit slice distribution

Related: https://resource.rahmanef.com/slices — [before: slice distribution had one implicit React/Next source path] → [after: each slice can declare deterministic framework availability, aliases, paths, and dependency overrides while React/Next stays the default]. Generated CLI and MCP manifest entries expose availability, defaults, aliases and dependency overrides without removing legacy fields.

CLI selection and validation

  • rr add and rr lift accept --framework. An explicit unavailable framework fails with the available choices; it never falls back silently.
  • Validation rejects missing declared framework paths, invalid or ambiguous defaults, and duplicate aliases. Framework-specific dependency descriptors can override npm, shadcn, env, peers, and sharedFiles before Svelte slice waves land.
SEP112026
Improvementsite@deterministic-vitestSep 11, 2026

Deterministic Vitest test environments

Vitest now runs consistently across hosts: repository test scripts force NODE_ENV=test, Node-only suites opt into the Node environment, and Vite path resolution uses ESM-native paths.

SEP092026
Improvementsite@oauth-first-integrationsSep 9, 2026

OAuth-first integration onboarding contract

Provider and plugin onboarding now leads with OAuth/OIDC whenever it is supported. The contract keeps client secrets server-side and requires exact callbacks, least privilege, state, PKCE and nonce where applicable, encrypted token custody, plus refresh, disconnect and revoke lifecycle handling. Manual API keys and bearer tokens remain an explicit fallback rather than a parallel default.

Fallback credentials

  • Every manual secret field must include the official provider URL, 3–6 numbered acquisition steps, minimum scopes or permissions, rotation guidance, exact paste location, masked server-side storage, and verification plus disconnect/revoke instructions.

Remote MCP

  • Prefer advertised OAuth discovery; bearer/manual authentication is fallback and may not weaken workspace authorization or tool approval.

Coverage

  • Generated Next and Svelte/Convex best-practice prompts both carry the OAuth-first contract.
NewerPage 8 / 25Older