[FR]: Inherit contexts (and optionally other properties) from the source note during instant conversion #2315

Feature Description

Feature Category

Task Management (creating, editing, organizing tasks)
Problem Statement

When I convert a checkbox to a TaskNotes task inside a project note, the "Use parent note for inline/instant conversion" setting links the source note as a project. That covers the "what", but not the "where": my project notes carry contexts in their frontmatter (e.g. contexts: ["@garage"]), and every converted task has to have those added by hand, or typed as @context on each checkbox line.

TaskNotes already solves this for subtasks: since 4.8.0 there is an opt-in setting for Create subtask to inherit the parent task's projects, contexts, priority and non-identifying tags (#518, #1710, #1785). Instant conversion from a project note is the same parent/child relationship, but has no equivalent.
Proposed Solution

An opt-in setting under instant conversion, alongside "Use parent note for inline/instant conversion":

Inherit contexts from source note: when converting, read contexts from the source note's frontmatter and add them to the new task.

Nice to have: the same per-property choice as subtask inheritance (contexts, tags, priority, custom fields), so both flows behave consistently. If the "closest heading as project" option is used, inheritance should still come from the source note's frontmatter.

Values typed inline on the checkbox line (@context) should be merged with, not replaced by, the inherited ones.
Alternatives Considered

Typing @context on every checkbox line: works, but repetitive and easy to forget.
Making the project note itself a TaskNotes task and using Create subtask: gets inheritance, but loses the checkbox-in-note workflow, and not every project note should be a task.
Global default contexts: apply to every task, not per project.