Skip to content

feat: establish standalone Rstack context runtime - #1

Draft
ScriptedAlchemy wants to merge 40 commits into
mainfrom
codex/extract-context
Draft

feat: establish standalone Rstack context runtime#1
ScriptedAlchemy wants to merge 40 commits into
mainfrom
codex/extract-context

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • preserve the focused packages/context history from Rstack CLI
  • establish @rstackjs/context as a standalone Rslib/Rstest/Rslint package
  • add CI, pkg.pr.new previews, MCP smoke coverage, and runtime architecture docs
  • keep Rstack CLI as the thin command/config host and Agent Skills as plugin distribution

Verification

  • pnpm install --frozen-lockfile
  • pnpm check
  • pnpm build
  • pnpm test (177 passed)
  • clean packed-package root and ./mcp import smoke
  • exact pkg.pr.new preview built against the stacked Rsdoctor Agent CLI preview

Integration

The current preview is https://pkg.pr.new/rstackjs/context/@rstackjs/context@711b987. Its repository-only validation override uses the exact stacked Rsdoctor preview while the packed manifest retains the ordinary semver peer contract.

@pkg-pr-new

pkg-pr-new Bot commented Aug 14, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/rstackjs/context/@rstackjs/context@1

commit: 711b987

ScriptedAlchemy and others added 13 commits August 14, 2026 23:50
The pkg.pr.new override never propagated to consumers, so downstream
installs resolved the published 0.1.1 whose omitted-section semantics
this package cannot ship against. Declaring the commit-pinned canary of
web-infra-dev/rsdoctor#1903 directly makes every install resolve the
build the tests certify. Swap for a release version once the PR ships.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Revert the URL dependency from c01fd3b: published previews must carry
ordinary semver dependencies because blockExoticSubdeps consumers reject
URL-resolved subdependencies (rstack-cli context-plugin-boundary design,
"Preview dependency policy" — adopting it broke rstack-cli installs with
ERR_PNPM_EXOTIC_SUBDEP). Local validation still resolves the pinned
canary of web-infra-dev/rsdoctor#1903, now commit-addressed instead of
floating on the PR ref; consumers on 0.1.1 fall back to the existing
zero-shape degraded reporting for omitted sections.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant