tasks don't expose "sections" something that embeded query does

[grotesque]

Simple embed query example:

query  
task:"" path:"" section:"" 

Here I can mention anything in section and I will get all tasks inside a section of that name
A section here can be a heading, a bullet etc.

But we cannot do that with tasks plugin. Only Heading is exposed. A tasks might have a parent section that's not a heading, eg. a simple bullet.

There is no reason not to expose the parent section attribute of a task since embed search query already uses it, why not the more advanced tasks plugin?

tasks plugin:
We should be able to do :

show tree
section includes bulletname
explain

[claremacrae]

I don't understand the question.

But if you are wanting to make a Feature Request, it should go in Issues please.

It would need to be rather more specific than the above:

• including concrete real-world examples of the use of that first feature that you mentioned, which I guess might be the built in Obsidian search facility.
• give concrete examples of "sections", as Markdown that we can copy for testing - again, real-world examples.

In other words, requests should not need knowledge of things other than the Tasks plugin, in order to understand them.