v0.3.0

Added

• An agent can read the surface it is already on.
• The job body contract says what a body finds on disk.
• A scheduled job can read the agent's repository checkouts.
• A post can wake one person or agent.
• What the addressed principal answers comes home to the conversation that asked.
• A job that outlasts the turn answers the conversation that asked.

Changed

• A SageOx credential refreshed under the agent's secrets mount is picked up without a Deployment restart.
• A GitHub Release leads with one line per entry here, not the whole section.

Fixed

• A dead SageOx credential no longer degrades an agent in silence.
• The agent-to-agent chain cap now applies on Buzz.

Each entry in full: CHANGELOG.md.

Runtime image

ghcr.io/sageox/agent-base@sha256:d42a7ae0cbd2252caa1f29f3ab9f2ca9f70a7aed599b7731f8211d230c0ef53f

Pullable anonymously, linux/amd64,linux/arm64. Pin the digest in production: the 0.3.0 tag is immutable and is never republished.

What's Changed

• Lead a release with one line per CHANGELOG entry, not the whole section by @shrimalmadhur in #21
• Say what a job body finds on disk, since one door has a workspace and the other does not by @shrimalmadhur in #26
• Latch what a team lookup proved, so a dead credential is not silent by @shrimalmadhur in #27
• Read the team brain's token per lookup, so a rotated secret self-heals by @shrimalmadhur in #28
• Address a principal from any door, and bring the answer home by @shrimalmadhur in #31
• Let a job Pod read the agent's checkouts, since the index cannot travel read-only by @shrimalmadhur in #33
• Let an agent read the surface it is on, since a second client means a second credential by @shrimalmadhur in #34
• Read the roster the relay keeps, since an agent's own record is not membership by @shrimalmadhur in #36
• Cut the CHANGELOG section for 0.3.0 and move the chart to 0.11.0 by @shrimalmadhur in #37

Full Changelog: v0.2.0...v0.3.0