Add compliant minting invariant tests

[El-swaggerito]

Description

Difficulty: Expert

Type: Test

Summary

Add invariant-style tests proving minting only succeeds for compliant assets, authorised issuers, and whitelisted recipients.

Current Behaviour

Minting paths may have basic tests but not enough coverage for compliance and authorisation interactions.

Expected Behaviour

The test suite should prove non-compliant recipients, unauthorised issuers, invalid assets, and paused states cannot mint.

Suggested Implementation

Create deterministic scenario matrix tests for minting success, rejected recipient, wrong issuer, invalid asset, revoked compliance, and repeated actions.

Files or Areas Likely Affected

• tests/
• src/
• docs/

Acceptance Criteria

• Compliant minting success path is tested.
• Non-whitelisted recipient minting is rejected.
• Unauthorised issuer minting is rejected.
• Invalid asset minting is rejected.
• Revoked compliance state is tested.
• State remains consistent after failed minting.

Additional Notes

This supports audit readiness.

[jd5073356-max]

I can implement the invariant-style test suite for compliant minting under tests/ and src/. My approach: construct a deterministic scenario matrix to test success paths alongside rejection cases for non-whitelisted recipients, unauthorized issuers, invalid assets, and revoked compliance, ensuring state consistency and idempotency across failed mint attempts. I can deliver a clean, audit-ready PR within 2 days.

[grantfox-oss]

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

Good luck! Track your progress on GrantFox.

[jd5073356-max]

PR: #151

Added the requested deterministic scenario matrix in src/test.rs: compliant success, non-whitelisted recipient, unauthorised issuer, invalid asset state, revoked compliance, and repeated rejected attempts — every rejection case asserts both the specific error and that balance/total supply are left unchanged.

Found and fixed along the way (see PR for full detail):

• main didn't compile (2 orphaned closing braces in src/test.rs).
• A real production bug directly tied to this issue's "invalid asset minting is rejected" criterion: asset::get_asset_status_internal defaulted an unset asset status to Active while lifecycle::get_asset_status (used by the writer, set_asset_status) defaults the same storage key to Draft — the documented intended default. This meant a freshly-initialized contract could be minted against immediately without the admin ever explicitly activating it. Verified with a probe test before fixing, then corrected the default and updated the tests (a shared test helper, setup_transferable(), only "worked" before because of this bug).
• 16 pre-existing failing tests, once the above got the suite compiling and consistent — mostly a stale error taxonomy (AssetLifecyclePaused/AssetRetired/AssetBlocked → the newer *Restriction variants the code actually returns) and a couple of hardcoded counts/codes that had drifted from the current implementation.

cargo test --lib is now 180/180 (was uncompilable before any fix). One thing left unfixed and flagged transparently in the PR: tests/sdk_fixtures.rs (a separate integration target) has 2 pre-existing fixture-drift failures unrelated to anything in this PR.