Feedback: session preflight receipts for required-first-tool workflows

[caioribeiroclw-pixel]

Live market signal: Cursor Forum users are asking for a required first tool / pre-tool hook because .cursor/rules can tell an agent to read MEMORY.md, but cannot prove or enforce that the run initialized context before Grep/Shell/Write.

Artifact shipped in abb2287:

• docs: https://github.com/caioribeiroclw-pixel/pluribus/blob/main/docs/session-preflight-receipts.md
• copyable example/rule: https://github.com/caioribeiroclw-pixel/pluribus/tree/main/examples/session-preflight-receipts

Question for Cursor / Claude Code / MCP users:

1. Should a preflight receipt be produced by the MCP guard server, by the client/IDE, or by a lightweight CLI before work starts?
2. Which tools should be blocked until preflight: only side-effecting tools (Write, Shell) or also search/retrieval tools?
3. Is a non-secret fingerprint of loaded context enough, or do teams need richer provenance such as rule file version, branch, and timestamp?

Hypothesis: if required-first-tool workflows matter, users will ask for a concrete enforcement/receipt boundary rather than another memory-store feature.