Implement period close reconciliation markers

[edehvictor]

Summary

Add period close markers that record whether expected payroll batches, reservations, holds, and audit references are reconciled.

Why This Matters

Teams need a reliable way to know a payroll period is operationally complete before archiving or reporting.

Suggested Files

• contracts/src/reconciliation.rs
• contracts/src/payroll.rs
• contracts/src/audit.rs
• contracts/tests/period_close.rs

Tasks

• Create period close record structure.
• Validate unresolved holds, reservations, and disputes before close.
• Emit period closed events with safe counts.
• Add tests for complete and incomplete periods.

Acceptance Criteria

• Complete periods can be closed once.
• Incomplete periods report the blocking category.
• Period close events avoid private payroll amounts.
• Tests cover holds, reservations, disputes, and success.

Coordination

Join the Telegram channel for proper coordination: https://t.me/zkpayroll

[AgentX010]

@AgentX010 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’m interested in working on this issue and would love the opportunity to contribute. I’ve reviewed the requirements and understand the expected outcome. I’m confident I can deliver a clean and well-tested implementation within the required timeframe.

Thank you for considering my application.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AgentX010 to this issue.

[TheHalalHunter]

@TheHalalHunter has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer
I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheHalalHunter to this issue.

[drips-wave]

Congratulations, @TheHalalHunter! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @TheHalalHunter: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

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

@TheHalalHunter's PR #394 was approved and merged by @edehvictor.

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

👏 Great work, @TheHalalHunter! Keep contributing to zkpayroll.

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @TheHalalHunter as part of the Stellar Wave Program's 8th Wave 🥳

Moderator's reason: [Auto-assessed] The PR was approved and merged by repository maintainer @edehvictor as noted in issue comment #359, successfully implementing period close reconciliation markers with comprehensive testing.

😎 @TheHalalHunter: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.