Make File observations the sole file-matching source

[frap129]

Parent

#38

What to build

Make normalized File observations from successful supported operations the exclusive source for glob and content matching, removing incidental paths from prose and unsupported tools from the file-matching trust boundary.

Acceptance criteria

• Glob-only and content-scoped Rules obtain file context exclusively from successful Read, Write, Edit, Apply Patch, and path-associated LSP observations.
• Grep, Glob, shell, custom and MCP tools contribute neither paths nor content, whether successful or failed.
• User and assistant prose, attachments, metadata, diagnostics, and incidental path-like text cannot select file-scoped Rules.
• Existing condition families retain their current algebra, lifetime, identity, framing, and delivery semantics.
• Legacy path extraction is removed from production matching and compatibility tests are updated to assert the intentional trust-boundary change.
• No proactive, hidden, startup, or historical filesystem scan is introduced.

Blocked by

• Match Rules from successful Write and Edit observations #57
• Match Rules from successful Apply Patch observations #55
• Match Rules from successful LSP observations #56