v0.9.0

Highlights

• Jira issue creation, targeted native-wiki description edits, labels, and
  links now use preview → review → hash-confirmed apply. Proposals bind fresh
  qualified evidence and immutable identities, allow at most one write attempt,
  and reconcile through bounded readback without automatic replay.
• Existing guarded comment and custom-field workflows now qualify stricter
  evidence, reject lossy JSON and invalid Unicode, and report closed outcomes
  without exposing backend responses. Comment output and custom-field text stay
  value-free; custom-field JSON intentionally carries the proposed review
  value.
• The legacy Jira CSV executor is replaced by read-only jira issue plan preview and execution-only plan apply. Schema-v2 plans qualify every row
  behind one aggregate authorization/hash barrier and stop immediately if a
  write outcome becomes ambiguous.
• New qualified read surfaces include jira issue create-metadata and JSON-only
  jira issue field batch, which returns an ordered matrix for up to 25 issues
  and eight fields while distinguishing absent, null, empty, populated, and
  clipped cells.
• Shipped Jira skills and the offline capability catalog now route field batch,
  guarded create/link, and batch-plan work through their dedicated surfaces.
• Evaluator process-output bounds now have deterministic stderr overflow and
  accurate io.Writer accounting.

Upgrade notes

• Jira plan CSV schema v1 is no longer accepted or migrated. Use the exact
  header:

  schema_version,operation,source,target,type,field,value

  Run atl jira issue plan preview --csv plan.csv with the required allow
  inputs and review its aggregate proposal_hash. Repeat the same CSV and allow
  inputs for apply, adding
  --confirm APPLY --expected-proposal-hash '<reviewed hash>'.

• Scripts that expected Jira create, edit, label, or link commands to mutate
  immediately must adopt preview and hash-confirmed apply. Generate fresh
  v0.9.0 proposals; older proposal hashes are not reusable.

• Guarded links require exact kind:link authorization for both endpoints.
  Existing issue-only grants do not authorize those mutations.

• Exact capability-catalog/task-filter bytes change intentionally: field batch
  becomes the primary jira/batch-analysis route, and plan capabilities move
  from jira/edit to jira/batch-edit.

• No configuration, durable mirror, or MCP tool-schema migration is required.
  Existing read/list surfaces remain available, and no new MCP write tool is
  introduced.

Verification and supply chain

The release was qualified by the complete root build, test, race, lint, vet,
documentation, generated-plugin, privacy, and standalone evaluator contours,
plus hosted Linux, macOS, Windows, CodeQL, and vulnerability checks.

Assets are built from the tagged commit for Linux and macOS on amd64 and arm64.
Publication includes per-asset SHA-256 files, a signed update manifest, SLSA
provenance, the installer, and a generated Homebrew formula.

Full changelog: v0.8.0...v0.9.0