Improve repository credibility and benchmark docs

[shivansh2511]

Summary

• Rework README positioning, quick start, benchmark snapshot, and contribution guidance
• Add benchmark specification, scoring rubric, limitations, and current results summary
• Add demo/community trust docs plus benchmark and integration issue templates
• Tone down benchmark claims on the docs homepage

Validation

• npm.cmd run typecheck
• npm.cmd test
• npm.cmd run build
• npm.cmd run memory:check
• git diff --check

[gaurav-1302]

Approved.

This PR improves the project’s public presentation and credibility in the right direction. The README now explains the project more clearly, makes the benchmark snapshot visible early, and keeps the benchmark claims appropriately scoped as maintainer-run results rather than broad validation.

I also like the addition of benchmark methodology docs, scoring rubric, limitations, demo planning, community trust notes, and the new issue templates for benchmark reproduction and agent integrations.

Validation notes look good:

• typecheck passed
• tests passed
• build passed
• memory check passed
• diff check passed

No runtime behavior changes are included, so this is a good documentation and repository-trust improvement to merge.