rcourtman 9ec52406ad Carry discovery freshness into the cloud-safe context ...

The pushed cloud-safe operational context told the model a resource's access
pattern, paths, and ports but not how OLD the discovery was — so the Assistant
could present a 2-week-old cached scan as current. For a monitoring assistant,
recency is the most important provenance signal.

FormatCloudSafeContext now appends "Last discovered: <age>" (via the existing
FormatDiscoveryAge helper, previously unused) when the timestamp is known, and
the push-path conversion (cloudSafeOperationalContext) carries UpdatedAt through.
A timestamp is non-identifying, so it adds no PII. Omitted when unknown.

- Tests: FormatCloudSafeContext freshness present/absent; cloudSafeOperationalContext
  carries UpdatedAt end of the push conversion (and still emits no PII).
- Contract: ai-runtime cloud-safe context must carry discovery age when known.

Follow-up: same freshness line on the local/full path (formatSingleDiscovery).

2026-06-09 10:46:10 +01:00

..

internal

Clear v6 prerelease-to-GA promotion gate

2026-04-20 16:33:03 +01:00

v6

Carry discovery freshness into the cloud-safe context

2026-06-09 10:46:10 +01:00

control_plane.json

Capture continuous discovery reconciliation

2026-05-28 16:42:01 +01:00

control_plane.schema.json

Map legacy stable releases in control plane

2026-04-11 13:23:07 +01:00