Skip to content

feat: a per-call requested context on the call frame, accepted, narrowed or refused by a serve({ context }) host check and merged under the principal's keys, all protected, into the call's scope (#79) - #80

Open
cldmv-bot[bot] wants to merge 5 commits into
nextfrom
feat/call-context

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

🐛 Bug Fixes

No bug fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

👥 Contributors

…, narrowed or refused by a serve({ context }) host check and merged under the principal's keys, all protected, into the call's scope (#79)

The call frame gains an optional, data-only context and the surface frame an
optional context: true flag, advertised only by a serve with a check; no
FRAME_VERSION change. The check runs after the principal is resolved and before
the gate, fails closed (a throw or a non-plain-object answer is VINE_DENIED),
and a serve without a check refuses a frame that carries one. around receives
the accepted context.
…all requested context, refused locally when the far side does not accept one (#79)
…eck configured, data-only violations, old/new interop, loopback and websocket (#79)
…and link.with()/grow({ context }), the refuse-without-a-check default, interop, and no context on subscriptions in v1 (#79)
@cldmv-bot cldmv-bot Bot added ! feature → next v4 flow: contributor PR targeting the next integration branch type: feature Implements new functionality — a PR or issue that adds a feature area: core Touches core library / runtime source code area: tests Touches test files, fixtures, or test infrastructure type: documentation Relates to docs, README updates, guides, or inline code comments labels Oct 7, 2026
@cldmv-bot cldmv-bot Bot changed the title docs: the per-call requested context — wire keys, serve({ context }) and link.with()/grow({ context }), the refuse-without-a-check default, interop, and no context on subscriptions in v1 (#79) feat: a per-call requested context on the call frame, accepted, narrowed or refused by a serve({ context }) host check and merged under the principal's keys, all protected, into the call's scope (#79) Oct 7, 2026
@cldmv-bot

cldmv-bot Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor Author

Auto-normalized PR title: rewrote PR title to match the highest-priority commit type (feat).

  • Before: docs: the per-call requested context — wire keys, serve({ context }) and link.with()/grow({ context }), the refuse-without-a-check default, interop, and no context on subscriptions in v1 (#79)
  • After: feat: a per-call requested context on the call frame, accepted, narrowed or refused by a serve({ context }) host check and merged under the principal's keys, all protected, into the call's scope (#79)

If this isn't what you want, edit the title — the normalizer won't re-fire as long as the title stays conventional.

…distinct from VINE_DENIED for a rules refusal (#79)

The serve's context check refusing (a non-object answer, a throw or a
rejection), a serve with no check, and the grow's local refusal when the far
side does not accept requested contexts now answer VINE_CONTEXT. VINE_DENIED
stays the principal/permission refusal, including for an accepted context the
rules then refuse.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: core Touches core library / runtime source code area: tests Touches test files, fixtures, or test infrastructure ! feature → next v4 flow: contributor PR targeting the next integration branch type: documentation Relates to docs, README updates, guides, or inline code comments type: feature Implements new functionality — a PR or issue that adds a feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant