Skip to content

feat: establish standalone Rstack Context runtime - #1

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

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

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Aug 14, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Make @rstackjs/context the standalone owner of the MCP server, producer adapters, immutable evidence store, and queries. Agent hosts use the programmatic @rstackjs/context/mcp entry point. Explicit lint and test captures use native tool configuration.

Passive build capture now uses Rstack's released define.extends() API. The shared-config factory checks against the public RstackConfig type without adding a runtime or peer dependency on Rstack. Rstack owns config loading, merging, and test inheritance. Context adds observers to the selected App and Lib configs.

The integration is tested with rstack@0.8.5, @rslib/core@1.0.4, and @rsbuild/core@2.2.14. The upstream API blocker from RFC #504 is resolved.

Execution evidence binds to source bytes captured during compilation, including restored cached modules. Source changes after test execution cannot become fresh positive evidence. Lint freshness includes recorded config inputs and remains partial when the producer's full dependency set is unavailable.

File/glob Rstest projects still run and retain coverage counts, but their aggregate coverage cannot establish source-bound execution evidence with the currently supported observer hooks.

All direct dependencies and compatible transitive dependencies were refreshed against npm on October 22, 2026, with pnpm 12.15.0. @rsdoctor/agent-cli remains at 0.1.2 because its latest tag points to the older 0.1.1 release.

Verification

  • Frozen dependency install.
  • Lint, type checking, formatting, and Rslib build with declaration generation.
  • 198 passing tests with coverage enabled, including native rs build, rs lib build, and rs test run fixtures.
  • App/Lib tests cover nested shared layers, local overrides, disabled capture, monorepo provenance, both ESM and CJS library outputs, and automatic test inheritance.
  • Package checks ensure Rstack is absent from runtime/peer dependencies and published shared-config declarations.
  • CI passes. Both native App/Lib fixtures also pass against the downloaded pkg.pr.new package.

Related work

@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: 9bcfaca

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>
@ScriptedAlchemy ScriptedAlchemy changed the title feat: establish standalone Rstack context runtime feat: establish standalone Rstack Context runtime Sep 24, 2026
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