Files
pulse/docs/release-control
rcourtman ec91dd43ea Deliver cloud-safe operational context to the model on the resource handoff path
The drawer "Ask Assistant" handoff anchored a resource but never delivered its
operational context (access command, config/data/log paths, ports) to the model
— that only reached the model via @-mentions. Route handoff resources through
the same prefetch path so the proactive path matches the @-mention path on cloud
turns; PII (hostname/IP/alias) stays redacted at the model boundary.

- Reconcile the handoff Data Boundary directive: the model may use the PII-free
  operational context to answer and guide the user, while still never revealing
  raw hostnames/IPs/aliases/secrets. Action Boundary unchanged (read-only; any
  mutation goes through the governed approval flow).
- Fix a pre-existing clobber: the plain-text resource resolver overwrote the
  prefetch summary on the @-mention path, dropping the operational context
  before it reached the model. Run it only as a fallback when no structured
  mention resolved.
- Add the first end-to-end test asserting the operational context reaches a
  cloud model on BOTH the handoff and @-mention paths while PII is redacted.
- Update the ai-runtime contract to reflect the reconciled handoff data boundary,
  handoff operational-context parity, and the plain-text fallback ordering.
2026-06-09 10:18:52 +01:00
..