v0.6.4

Fixed

• brain/generated-drift no longer reports a projection nobody has touched.
  CURRENT.md carries the day it was rendered and an age in days for every
  record, both from the clock, and the check compared it against a re-render
  made with today's clock — so it failed on the first run of every new calendar
  day. Two of the three workspaces running vat were in that state: clean trees,
  CURRENT.md committed beside the records it was built from, no commits since,
  red the next morning. The remedy works, which is why it went unexamined:
  vat brain build rewrites the date, so the error cleared every day and
  returned every night. The question is now asked as of the day the file itself
  says it was built, which leaves the records as the only thing that can differ.
• docs/SPEC.md §4.1 names the policy block. Five groups and sixteen fields
  were in the schema and in docs/MANIFEST.md and named nowhere in the
  normative field table, from the manifest's first commit; workspace.description
  was missing from it too while appearing in the same file's own example. Both
  documents are now held to the code by a test, each by the convention it uses.
• The runner suite runs on Windows. Seven of its eight tests skipped there
  because their fixtures were POSIX shell, so cmd /C — the branch
  docs/FAQ.md says vat.yaml commands run through — had no coverage on any
  platform, and CI on three operating systems was running the skip.

Full Changelog: v0.6.3...v0.6.4

v0.6.3

Added

• vat upgrade installs the newest published release the way this binary was
  installed, and vat doctor --network reports when one exists.

  requires.vat could not answer this. It asks whether a binary is acceptable
  to the workspace, and a range stays satisfied by the version it was written
  against for as long as it stands — so every release inside >=0.6.1 <0.7.0
  arrived unannounced to the two workspaces that pinned it, and both were still
  on the version they pinned at with nothing anywhere saying otherwise.

  vat replaces nothing itself. Homebrew keeps a manifest of the files in its
  Cellar and go install records the module version, so a binary that
  overwrote itself would leave both describing a file they did not write. The
  installer is asked to do its own job, and an install vat cannot account for
  is reported with the release to fetch rather than guessed at. Diagnosis stays
  in doctor and the repair is its own command, as everywhere else here.

Full Changelog: v0.6.2...v0.6.3

v0.6.2

Fixed

• workspace/layer-unchecked now recognises a workspace with canonical skills
  and no roles as using the harness layer. Those skills render runtime adapters
  that can drift, but the rule only looked under .agents/roles/, so a
  skill-only workspace received no prompt to add vat harness check.

  The procedures vat init seeds are not adoption on their own. Counting them
  put the warning on every workspace vat had just created, for files vat wrote
  itself, on the first command a new user runs — and the obvious repair was not
  vat's to apply, because workspace.checks is the evidence
  vat changeset verify consumes and a value seeded there would record the
  control plane as proven by a check nobody chose. A skill somebody wrote is
  adoption; a starter left where vat init put it is not. Whether a seeded
  procedure still matches its adapter is harness/adapter-drift's question,
  asked directly and on the file itself.

• The normative harness format now lists the Codex skill adapter added in
  v0.6.0. The implementation and harness guide already described both runtime
  adapters, while docs/SPEC.md still stated the pre-v0.6.0 contract.

Upgrading

• The first vat lint after upgrading reports workspace/layer-unchecked on a
  workspace that defines skills of its own, no roles, and no vat harness check
  in workspace.checks. That combination was invisible to the rule before.
  Adding the check ends it, and nothing that passed before fails now: the
  finding is a warning and vat lint leaves the exit code alone for warnings.
• A workspace holding only the two procedures vat init seeds is not asked, so
  a newly created workspace is silent on its first run.

Full Changelog: v0.6.1...v0.6.2

v0.6.1

Full Changelog: v0.6.0...v0.6.1

v0.6.0

Full Changelog: v0.2.1...v0.6.0

v0.5.2

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Full Changelog: v0.4.2...v0.5.0

v0.4.2

Full Changelog: v0.4.1...v0.4.2

v0.4.1

Full Changelog: v0.4.0...v0.4.1