fix(crane): separate crane and jira issue references

[astyfx]

Summary

Separate Crane issue references from Jira issue references so linked Jira work drives branch and task naming while the Information panel keeps Crane links in their own section.

Changes

Features

• crane: add the forward-compatible issue.links dispatch contract with ordered relationship handling
• workspace: add the connector-gated Crane Issues section, resource registration, mentions, and intent context

Fixes

• crane: prefer the declared Jira issue for branch, task, and PR naming
• information: prevent Crane URLs from being stored as Jira issues and reroute them to the Crane section
• contract: strip additive unknown fields while rejecting nested host-control fields

Test Evidence

• bun run test:ci — license, reliability, documentation, type, isolated test, renderer build, and desktop build checks passed
• Targeted Crane, Jira, Information panel, and MCP regression tests: 182 passed, 0 failed

Notes

• issue.links is the supported Crane-to-Stave association shape; Stave consumes the first case-insensitive rel: "jira" entry and leaves other relationships extensible.
• The dispatch envelope remains at version 1. Unknown additive fields are stripped, while local execution choices remain controlled by Stave's approval flow.

[heath-s]

Approved