1504 hand-written ranges pointing at workspace members become workspace:^, so pnpm pack substitutes each member's real version at publication: sibling peerDependencies follow the family version instead of being pinned at ^0.0.1, and a reference to a vendored package follows that package's own line. Without this, publishing 0.0.2 ships peer ranges naming a version that does not exist, and 0.0.1-rc.1 does not satisfy ^0.0.1 either. It also retires ranges that had gone stale against the workspace: ^4.0.0-rc.6 for a 4.0.0-rc.7 checkout, ^3.17.0 for schemastery 3.18.0. workspace:* stays where an exact published version is the point, which is how the Landlock entry pins its platform packages. A workspace constraint now requires the protocol, so a new package cannot reintroduce a hand-written range. The same constraint caught packages/boot/cmdline arriving on master without the publishable trio, which this change completes.
context/ — request-context extensions
English | 中文
Product plugins that add model-visible request context without defining a tool. workspace-context is included by the default dsh-agent-spine-demo bundle and can be disabled through bundle config; time-context, tmux-context, and session-reference are opt-in.
| Package | Role | ctx key |
|---|---|---|
session-reference/ |
Bounded snapshots of other sessions | ctx.sessionReferences |
time-context/ |
Current-time and elapsed-time context | — |
tmux-context/ |
tmux location context | — |
workspace-context/ |
Workspace-instruction context | — |
Session references are documented in docs/subsystems/session-reference.md; the workspace-context decision record owns its per-agent/session isolation and lifecycle split.