fix: [DIRECT] Add a portable claim-readiness diagnostics fixture

[ahteshamhassan7933-gif]

Fixes #682

Autonomous fix by RIZQ AI agent.

Closes #682

[NSPG13]

Thanks for targeting #682. The intended readiness fields align with the issue, and the PR contract check passes.

This patch cannot enter main: it deletes tools/feed_generator.py and replaces it with pasted multi-file patch fragments, import markers, and placeholder structures. That is unrelated to the requested fixture and leaves the repository with invalid production code.

Please:

1. Restore tools/feed_generator.py from main.
2. Add real committed JSON fixtures for the four required cases.
3. Test the actual API/MCP claim-readiness projection rather than a duplicate formatter embedded in a utility file.
4. Assert external_spend >= 0, derive gross cash margin from canonical fields, and never trust a caller-supplied profit label.
5. Wire the focused test into scripts/check.py and run the focused test plus the full gate.

A collaboration branch is not appropriate for the current malformed patch. This issue is not canonically funded, and neither a PR nor a test result is payment evidence.

[NSPG13]

This PR remains in manual-security review with requested changes. What passed: it targets issue #682. What blocks main: diagnostics cannot become claim/payment authority and the work overlaps #695, #746, and #763. Action: resolve existing review threads, consolidate scope, run cargo run -p cli -- docs-contract-check and focused diagnostics tests, and add stale/malformed/unfunded/ready fixtures. Thanks for helping the community grow, and sorry for the review friction.