Add Aegis Contracts CI pass requirement guidance

[El-swaggerito]

Description

Difficulty: Hard

Type: Documentation

Summary

Add guidance explaining CI pass requirements for Aegis Contracts PRs.

Current Behaviour

Contributors may believe that a PR with failing checks can still be considered complete after merge.

Expected Behaviour

The repo should clearly state that failing CI can affect evaluation and contributors are expected to fix failing checks before approval.

Suggested Implementation

Document common CI failures, local reproduction commands, fix expectations, and reviewer responsibilities.

Files or Areas Likely Affected

• src/
• tests/
• docs/
• README.md
• Makefile

Acceptance Criteria

• CI pass requirement guidance is added.
• Guidance states that failing CI can affect evaluation.
• Common failure types are listed.
• Local reproduction commands are included.
• Contributor fix expectations are documented.
• README links to the guidance.

Additional Notes

This directly addresses the issue of PRs with failing checks.

[bonaventure001]

I've been working through the GrantFox OSS documentation track on a sibling repo (AnchorKit) and understand the general shape this kind of guidance doc takes — plain-language CI requirements, mapped to the repo's actual workflow files rather than generic advice. I'd start by reading the repo's .github/workflows/ to ground the guidance in what actually runs, then draft accordingly. Can turn around within a day.

[grantfox-oss]

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

Good luck! Track your progress on GrantFox.

[El-swaggerito]

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