[witbrock]

Merge decision: ready — actor-only Jira imports now map the configured Jira account to its governed Von owner, avoiding a separate imported person record for that owner.

User outcome

Bulk migrations provide an actor without a legacy namespace. The account mapping previously ran only when a namespace was present, so assignments and watchers could refer to an imported Jira person instead of the account owner's existing Von identity. That breaks the expected "assigned to me" view after migration.

Material changes

Use the existing governed Jira account binding to enable owner mapping for actor-only imports. A local operator importing for a different actor does not acquire this automatic mapping. Explicit participant mappings still take precedence, and the existing opt-out and legacy namespace path retain their behaviour. No login binding, visibility or account permission is changed.

Part of JVNAUTOSCI-2737.

Evidence

• 82 targeted gateway, importer, retention and Jira authority tests passed.
• A live source-preserving dry run without a namespace resolved the Jira assignee to the governed Von owner with mapped_from_account_map.
• No new Ruff findings relative to the parent revision; diff checks passed.

Ship boundary

The minimum criterion is correct actor-only owner mapping with an independently verified account binding. Mapping another account owner to the caller, ignoring an explicit map, or enabling mapping despite opt-out would block shipment. Existing task repair and whole-estate migration/cutover verification remain separate operational work. No captured data or migration reports are included.