[witbrock]

Merge decision: ready — ordinary conversation task creation can preserve an authorised coding-agent assignment and execution preferences in one native record, and recovery reports distinguish confirmed task fields from an unresolved relationship. Runtime activation remains separate.

User outcome

Fix JVNAUTOSCI-2750: task_create previously overwrote the selected coding agent with the authenticated actor, cleared reporting, and silently ignored a supplied parent. The installed worker's older backend also omitted task model/reasoning preferences.

Material changes

• Reuse the existing continuation assignment checks: trusted creator/org/source binding, eligible same-organisation coding agents, and self reporting. Include assignment intent in turn retry identity and verify canonical identity, assignment, reporting, preferences and source on creation/retry. Preserve progressed tasks without creating duplicates.
• Reject unsupported parent creation before writing, with the existing authorised hierarchy routes identified. Keep hierarchy edits outside the ordinary parity editor.
• Reconcile later verified fields on the same task. The outcome report includes a task link and confirmed assignment/preferences while retaining unresolved required fields and the distinction between task creation and worker pickup.
• Add --backend-root for copied worker bundles and reject canonical readers missing execution-preference keys before pickup. Document compatible installation and rollback without changing defaults, schedules or live state.

Evidence

• 415 targeted tests passed, including all 263 adaptive-turn tests; the catalogue-wide stale expected-tool-list assertion is deselected and reproduced failing with its unchanged baseline test.
• Isolated in-memory replay uses production trusted payload construction, gateway/handlers and canonical task/text persistence. It verifies one record, retry identity, assignment/preferences/source, negative membership and creator boundaries, missing-parent rejection, failed-update/recovery reporting, and conversation invitation separation. No real work or model request is launched.
• The installed worker adapter also passes the isolated replay with the candidate canonical reader: standalone eligibility and Astra/high, both source=task. The installed backend was inspected at ab7394ae7c6caa168bf643e616f5772b784feea6, which lacks preference hydration. This is compatibility evidence, not activation or pickup evidence.
• Python 3.11 syntax check and pdm lock --check pass. A worker test now checks local Git configuration explicitly so the operator's inherited credential helper does not cause a false failure.

Ship boundary

Stop shipment for wrong scope/assignee, duplicate work, silent parent loss, or false creation/execution claims. Tier 2 overall, with successful trusted binding and negative tests local to the changed authority boundary.

No public deployment or worker activation is requested. An authorised operator must install a compatible backend/bundle, select it with --backend-root, preserve the existing shared lock/state and active work, and verify preferences before resuming scheduled pickup. No migration or global model change is required. Semantic related-versus-child judgement stays with the model; the observed failures and this repair are deterministic, so no additional model comparison was needed.

Jira read/update is unavailable because its connector requires reauthentication; close-out is handed back separately. Existing UI tasks and unrelated inbox work are outside this change.