Add Aegis dashboard acceptance criteria traceability table

[El-swaggerito]

Description

Difficulty: Hard

Type: Documentation

Summary

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

Current Behaviour

Contributors may not show how each requirement is satisfied.

Expected Behaviour

PRs should map pages, components, states, tests, screenshots, and behaviours to acceptance criteria.

Suggested Implementation

Create docs, PR template section, and examples.

Files or Areas Likely Affected

• docs/
• .github/
• README.md

Acceptance Criteria

• Traceability table is documented.
• Pages and components are mapped.
• Tests are mapped.
• Screenshots are mapped where relevant.
• PR template references table.
• README links to docs.

Additional Notes

This improves review clarity.

[deepak0x]

Hi, I'd like to take this one. I'm comfortable with the area this issue touches. I'll review the current code, implement the change to meet the acceptance criteria, add tests for the success and failure paths, and link the PR with Closes #ISSUE. Could you assign it to me?

[grantfox-oss]

🦊 GrantFox — @deepak0x 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 #101)
2. Your PR will be reviewed by the Axionvera maintainers

Good luck! Track your progress on GrantFox.

[El-swaggerito]

Assigned to @deepak0x. Please follow the acceptance criteria and submit a clean PR linked to this issue.