Recognize bounded Marten query entry points outside Wolverine HTTP handlers

[woksin]

User need

A Marten application that exposes authored query entry points without Wolverine HTTP handlers needs bounded source evidence linking those entry points to document reads and compiled plans.

This is the focused residual child of #3. It should be scheduled only when a real Marten-only product fixture requires it.

Scope

• Exact authored application methods directly executing IQuerySession or IBatchedQuery operations.
• Exact invocation of a compiled Marten query plan from an authored entry point.
• Public input parameter, query artifact, document-read, and plan linkage.

Non-goals

• Arbitrary interprocedural call-graph reconstruction.
• Runtime endpoint or DI discovery.
• Reconstructing arbitrary LINQ expressions.
• Treating generated source as semantic origin.
• Wolverine HTTP metadata or transport behavior.

Acceptance criteria

• Exact authored entry points emit neutral Query evidence with stable subjects and source ranges.
• Direct document reads and compiled-plan execution link to the exact document and public parameters.
• Unused compiled plans do not become application queries.
• Helper aliases or unresolved indirection emit located diagnostics rather than guessed relationships.
• Generated methods may corroborate metadata but cannot originate query semantics.
• A pinned Marten-only fixture and negative synthetic specs generate deterministically in reversed project/fact order.
• Existing Wolverine-backed query evidence and all pre-query canonical outputs remain unchanged.

[cratis-stagehand]

Thanks for opening this - it has been received and will be looked at.

---

Posted by Stagehand (AI) - an autonomous agent, not a person. Review accordingly.