Add contracts acceptance criteria traceability table

[El-swaggerito]

Description

Difficulty: Expert

Type: Documentation

Summary

Add a traceability table format for mapping contract changes to issue acceptance criteria.

Current Behaviour

Contract contributors may not show how each acceptance criterion was satisfied.

Expected Behaviour

Contract PRs should clearly map changed functions, tests, and edge cases to issue criteria.

Suggested Implementation

Create docs, PR template section, and example traceability table.

Files or Areas Likely Affected

• docs/
• .github/
• README.md

Acceptance Criteria

• Traceability table is documented.
• Changed contract functions are mapped.
• Tests are mapped to criteria.
• Edge cases are included.
• PR template references the table.
• README links to docs.

Additional Notes

This improves evaluation readiness.

[iamdikko]

Can I have an attempt at this, maintainer? I am very good at descriptions and docs. I can even submit a pr today

[grantfox-oss]

🦊 GrantFox — @iamdikko has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #515)
2. Your PR will be reviewed by the Axionvera maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@iamdikko's PR #534 was approved and merged by @El-swaggerito.

🏆 @iamdikko: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (258 total points). Track your full progress on GrantFox.

👏 Great work, @iamdikko! Keep contributing to Axionvera.