v0.8.0 — qualified corpus capture, resilient complete pulls, and pre-release agent evaluation

Highlights

• Strengthened complete Jira and Confluence pulls with qualification, resumable recovery, and opt-in bounded comments and attachment evidence.
• Added bounded Confluence attachment discovery and space-tree reads, qualified Jira complete-project pulls, inverse reference search, and compact Jira issue-graph output.
• Added qualified local corpus workflows for build, export, comparison, handoff, and cache management.
• Introduced the standalone, source-built agent-eval coordinator as a pre-release capability, with deterministic provider-free reference execution and reporting.
• Improved agent and MCP integration with runtime safety metadata, protocol compatibility handling, offline capability/effect discovery, and service-scoped health reporting.
• Added explicit JSON-valued Jira fields while preserving legacy scalar string fields, normalized Jira create type resolution to immutable IDs with outcome diagnostics, and qualified Jira graph self-reference handling.
• Hardened Confluence completeness handling and treats unambiguous schemeless backend hostnames as HTTPS.

Upgrade notes

• No configuration migration is required. Explicit HTTP remains refused under the existing transport policy; a bare unambiguous hostname now defaults to HTTPS.
• Complete-pull and search workflows may now report incomplete evidence instead of accepting an ambiguous result. Callers that need optional artifact retention should use the documented partial-artifact policy.
• agent-eval is pre-release only: it does not yet claim stable external-consumer support or publication authority.
• Modern MCP protocol support may require the documented client-side feature gate; legacy invocation remains supported.

Full Changelog: v0.7.1...v0.8.0