docs: add evidence package manifest appendix

[Hinotoi-agent]

Summary

• add a non-normative evidence package manifest appendix with YAML/JSON examples
• link the appendix from the standard README plus the Auditability and Reporting implementation guides
• extend the Vendor Evaluation Guide with a concrete evidence-package review prompt

Why

Issue #6 asks for a practical manifest example that ties together evidence integrity, provenance, review state, and downstream handoff without making one format mandatory.

Affected sections

• standard/appendix/Evidence_Package_Manifest.md
• standard/README.md
• standard/5_Auditability/Implementation_Guide.md
• standard/8_Reporting/Implementation_Guide.md
• standard/appendix/Vendor_Evaluation_Guide.md

Contributing.md checklist

• describe what changed and why: included above
• link related issue: Closes Proposal: add an evidence package manifest schema for findings and audit artifacts #6
• list affected sections: included above
• formatting and links: checked locally for the touched Markdown files
• AI assistance disclosure: drafted with AI assistance and reviewed by the submitting human

Notes

• informative appendix only; no new normative requirements added
• writing kept vendor-neutral and organization-neutral
• terminology follows the existing style guide

Closes #6

[jinsonvarghese]

@Hinotoi-agent Good work on this! One change needed before merge:

1. A row needs to be added for the new appendix in standard/Getting_Started.md under the Document Map table

Also heads up; this PR and #9 both modify standard/README.md and Vendor_Evaluation_Guide.md, so whichever merges second will need a rebase.

[Hinotoi-agent]

Thanks — I addressed the requested change by adding a Document Map row for the new appendix in standard/Getting_Started.md.

I also removed the cross-cutting standard/README.md and Vendor_Evaluation_Guide.md edits from this branch to reduce merge conflicts with the other appendix PRs.

Updated on commit 85e0b6d.