feat(boardreadyops): integrate current readiness, evidence, review, and release workflows

[oaslananka]

Summary

Upgrade the KiCad Studio integration from a basic BoardReadyOps check/report bridge to the current versioned readiness, remediation, evidence, review, and release-handoff contract.

Context

The existing Studio integration is intentionally small and currently centers check, configure, showReport, and documentation actions. Current BoardReadyOps 1.35.0 has grown into a broader lifecycle with plan, release evidence bundles, manufacturer handoff, baselines, and review publish/verify workflows.

Studio should orchestrate those capabilities without reimplementing the BoardReadyOps web product or governance backend.

Relevant extension code: apps/vscode-extension/src/commands/boardReadyOpsCommands.ts, Task Hub catalog, diagnostics, MCP tools view, and release workflows.

Scope

• Define a versioned Studio ↔ BoardReadyOps CLI/JSON capability contract.
• Surface readiness verdict, blocking findings, remediation plan, evidence state, and release-handoff state in task-oriented Studio workflows.
• Use structured JSON instead of parsing human-oriented output.
• Deep-link to BoardReadyOps web review/governance surfaces where approvals, discussion, or organization policy belong outside VS Code.
• Keep BoardReadyOps optional and fail closed when disabled, unavailable, or contract-incompatible.
• Avoid duplicating BoardReadyOps business logic in the extension.

Acceptance criteria

• Studio performs explicit BoardReadyOps version/capability discovery before invoking advanced workflows.
• Readiness findings map deterministically to VS Code diagnostics/actions with stable identifiers.
• A remediation/plan view can present the shortest next actions without requiring AI.
• Evidence/review/release state is visible when supported, with deep links for web-only governance actions.
• Release workflows can consume verified BoardReadyOps evidence without treating a numeric score as sufficient when blockers exist.
• Disabled, missing, old, malformed, and partial-result states have tested remediation paths.
• No credentials, private evidence, or internal service details are exposed in logs or diagnostics.

Validation

• Contract fixtures for supported and incompatible BoardReadyOps versions.
• CLI integration tests against current published/staged JSON schemas.
• Extension-host tests for disabled, configured, finding, pass, and evidence states.
• Release-path regression tests proving BoardReadyOps cannot silently weaken existing DRC/ERC/manufacturing gates.

Non-goals

• Recreating BoardReadyOps approvals, comments, policy administration, or evidence storage inside VS Code.
• Making BoardReadyOps mandatory for base KiCad Studio functionality.

[oaslananka]

2026-08-31 compatibility revalidation while preparing the next implementation slice:

• Published boardreadyops is now 1.37.0 (the issue context still references 1.35.0).
• The current CLI surface includes run, plan, doctor, release, handoff, policy, baseline, and review; there is no standalone capabilities command to rely on.
• doctor --format json exposes a versioned schema (schemaVersion: 1) and tool.version; the package also ships agent-plan v1, evidence v2, release-manifest v1, and doctor v1 JSON schemas.
• @oaslananka/kicad-protocol-schemas is now 1.4.1; kicad-mcp-pro remains 3.33.3.

Implementation should therefore discover BoardReadyOps compatibility from the versioned doctor/schema contract and fail closed on unsupported/malformed versions, rather than inventing or shell-parsing a human capability command. This is only a revalidation note; #623 acceptance criteria remain open.

[oaslananka-ops-github-app]

2026-08-31 implementation progress: added a local, signed regression slice that validates the versioned BoardReadyOps findings/readiness payload before diagnostics consume it. Partial or unsupported findings schemas now fail closed with a sanitized error; malformed JSON remains sanitized. Fresh verification: extension lint + typecheck passed, full unit suite 130/130 suites and 1033/1033 tests passed. Local commit: 316540a (fix(kicad-studio): validate BoardReadyOps readiness contract). Publishing is currently blocked because the maintenance workspace has read-only Git remote access (git push cannot obtain GitHub credentials). The remote branch feat/623-boardreadyops-run-contract has been reserved from current main; no PR was opened because the implementation commit is not yet published.