Quarantine notice

Veritas Kanban 6.0.0 was published prematurely and is now marked as a prerelease. Do not promote it as the stable release. The live backlog audit found unresolved release:v6.0 issues, including critical desktop navigation behavior. Homebrew is temporarily pinned to 5.2.5 while the blockers are completed and verified for 6.0.1.

Track remediation in release tracker #924.

Veritas Kanban v6 Release Notes

Veritas Kanban 6.0.0 makes agent runtimes explicit, evidence-backed, and
fail-closed. It adds first-class Buzz integration and puts Grok Build, OpenAI
Codex, Claude Code, and GitHub Copilot CLI behind the same provider-neutral run,
approval, credential, tool, worktree, event, and completion contracts.

• Release tracker:
  Veritas Kanban 6.0.0 harness parity and Buzz integration
• Buzz epic:
  First-class Buzz integration
• Harness epic:
  Equal-footing agent harness support
• Detailed compatibility record: Harness Compatibility
• Versioned architecture:
  v6 Agent Runtime Control Plane
• Retained validation record: v6 Release Candidate Evidence Packet
• Documentation freshness: 2026-07-24 for Veritas Kanban 6.0.0

What Changed For Users

• Settings, vk doctor --json, API diagnostics, telemetry, and dispatch now
  use one harness-support-profile/v1 state: Detected, Configured, Certified,
  Degraded, or Unsupported.
• Buzz can connect a pinned Nostr community to Squad Chat, import signed public
  persona and team definitions, run buzz-agent through generic ACP, expose a
  narrow run-scoped Veritas MCP bridge, and trigger allowlisted workflows from
  root messages.
• Grok Build, Buzz Agent, and GitHub Copilot CLI reuse the generic ACP v1 stdio
  adapter. Codex app-server uses its richer JSON-RPC v2 lifecycle adapter.
  Claude Code uses a supervised bare-mode stream-json adapter.
• Runs persist causal events, exact launch evidence, provider conversation
  identity, completion evidence, approval decisions, credential boundaries,
  and supervised ownership so reconnect and restart do not silently duplicate
  work.
• Provider versions, builds, capability digests, probe revisions, and fixtures
  invalidate stale certification instead of inheriting an old green state.
• Packaged SQLite startup now defers run-supervisor repository lookup until
  storage is initialized, and the desktop updater refuses older release
  metadata instead of offering a downgrade.

Tested Harness Baselines

The table states the reviewed baseline, not the current machine's live tier.
Only runtime evidence that matches the installed version, build, profile,
probe revision, capability digest, and passing deterministic fixtures can
report Certified. Credential-gated smoke is separate evidence and is recorded
in the release packet when available.

Architecture

Every executable run follows the same authority chain:

1. Normalize the selected profile to harness-support-profile/v1.
2. Probe and persist provider-runtime-manifest/v1.
3. Render one immutable task-envelope/v1 through the provider-owned
   transport.
4. Allocate a transactional worktree-manifest/v1.
5. Compile run-launch-manifest/v1, including sandbox, tools, MCP, approvals,
   environment key names, credential references, and budgets.
6. Supervise the local process or remote handle through run-supervisor/v1.
7. Persist redacted causal run-event/v1 records before projecting legacy
   output.
8. Broker exact actions through run-approval/v1 and one-shot credential
   leases through the system-owned veritas-run bridge.
9. Finish once through the idempotent completion-result/v1 contract.

The generic ACP adapter and the inverse vk acp serve --stdio view reuse that
chain. Buzz relay delivery remains a communication adapter and never becomes a
task or completion authority.

Breaking Changes And Migration Warnings

• Provider-less or adapter/profile-mismatched records no longer fall through to
  OpenClaw. Only known legacy Codex, Hermes, and Claude records with matching
  built-in type and command identity may infer an adapter during normalization.
• Claude Code no longer uses --dangerously-skip-permissions. Existing custom
  arguments that attempt to bypass permissions, inject configuration, inherit
  plugins, or select unrelated sessions are rejected.
• Unknown or changed provider builds lose certification. An enabled Degraded or
  Unsupported profile blocks dispatch until the operator fixes, disables, or
  replaces it.
• Credential-bound MCP servers are omitted from provider-native configuration.
  They run only through the one-shot Veritas bridge with an exact catalog,
  action, approval, and lease binding.
• Generic process stdin is not treated as a successful follow-up path.
  Conversation controls are available only when the persisted adapter evidence
  says the provider supports them.
• The public REST API remains v1; v6 adds contracts and endpoints without
  renaming the API mount. CLI, MCP, server, web, shared, and desktop package
  versions must all be 6.0.0.

Back up the current workspace before upgrading. Keep the complete v5.2.5
backup until v6 runtime verification is accepted. App rollback is safe only
when the older binary can open the current schema and profile records; otherwise
restore the pre-upgrade backup. See the
v6 Upgrade, Install, Remote, And Admin Guide.

Security Model

• Provider processes start without a shell in the exact assigned worktree.
• Environment values are allowlisted. Manifests, APIs, logs, telemetry,
  fixtures, screenshots, and issue evidence contain key names and opaque
  references, never secret values.
• Approval decisions bind to an exact action digest, reviewer, freshness
  requirement, expiry, attempt, and provider request. Drift, replay,
  cancellation, interruption, and duplicate terminal ownership fail closed.
• Tool calls bind to the immutable run catalog. Credential values resolve only
  inside a one-shot downstream MCP connection and credential-bearing results
  are rejected.
• Protocol frames, stdout, stderr, retained payloads, retries, and timeouts are
  bounded and redacted before durable storage.
• Required network rules block when runtime evidence cannot enforce them.
  Fine-grained method/path/domain proxy enforcement remains deferred to
  run-scoped egress gateway.

Known Limitations

• Grok Build's released artifact is not fully traceable to the public source
  tree and self-reports alpha.
• GitHub Copilot CLI ACP is public preview. Its public tag, commit message, and
  runtime version do not provide complete binary-to-source provenance.
• Claude Code's complete CLI implementation is not public. Certification is
  bound to exact release behavior and checked-in stream fixtures.
• Buzz Agent sessions are in-memory and do not support ACP session load/resume.
  Buzz files, reactions, forums, DMs, and destructive edit/delete projection
  are not bridged.
• Hermes and OpenClaw do not gain unsupported interactive lifecycle controls.
• Linux and Windows desktop artifacts are unsigned preview evidence. Signed,
  notarized macOS arm64 remains the supported desktop distribution.
• A deterministic passing fixture does not prove provider authentication,
  subscription availability, quota, or live inference. Live smoke results are
  reported separately and never fabricated.

Release Artifacts

The supported v6.0.0 publication set is:

• annotated source tag and GitHub release v6.0.0;
• signed and notarized Veritas-Kanban-6.0.0-mac-arm64.dmg;
• signed and notarized Veritas-Kanban-6.0.0-mac-arm64.zip;
• DMG and ZIP blockmaps;
• latest-mac.yml;
• SHA-256 sidecars; and
• Homebrew cask bradgroux/tap/veritas-kanban.

Final asset sizes, hashes, workflow URL, release URL, signed-runtime proof, and
Homebrew PR are written to the
v6 Release Candidate Evidence Packet after
publication. Source preparation does not count as signed distribution proof.

Deferred v6.x Work

• Run-scoped egress gateway
  remains a v6.x enhancement for fine-grained outbound HTTP enforcement.
  v6.0.0 already blocks any required rule that the selected provider cannot
  prove it enforces.