test(integration): M013 fee-router → M012 dynamic-supply burn flow

[brawlaphant]

Summary

Adds a new integration test that exercises the canonical Economic Reboot flow: fees are collected by M013 fee-router, the burn portion accumulates in its burn pool, and an off-chain aggregator hands that burn amount to M012 dynamic-supply as the `burn_amount` argument to `ExecutePeriod`. The two contracts do not message each other on-chain in v0 — but their data contract at the boundary must be bit-exact.

Now possible because #90 wired both contracts into the workspace members list. Before that, they couldn't be imported by `integration-tests`.

• Lands in: `contracts/integration-tests/`
• Changes: new burn flow test (222 LOC) + two `Cargo.toml` dep lines
• Validate: `cd contracts && cargo test --workspace`

What this test pins

Invariant	How
Workspace coexistence	Both contracts deploy in the same App without collisions
Fee Conservation inside m013	`burn + validator + community + agent == fee_amount`. A 10B uregen marketplace trade at 1% produces fee 100M split 30M/40M/25M/5M — pins Model A distribution (30/40/25/5)
Supply conservation inside m012	`current_supply == supply_before + total_minted - total_burned`. Asserted as an identity, not a hardcoded number, so the test doesn't pin the regrowth math as a side effect
m013 → m012 hand-off is bit-exact	The burn amount m012 records via `total_burned` equals the burn amount we read from m013's `pools.burn_pool`. No off-by-one, no rounding drift

The bit-exactness assertion is the single most important one in the test — if the two contracts' uregen accounting ever drifts, the Economic Reboot burn ladder breaks silently.

What this test does NOT do

Not a cross-contract MESSAGE flow — m012 does not call m013 and vice versa. The hand-off is off-chain in v0. A future upgrade that adds a real IBC or Wasm-level query can extend this test to cover that path; for now the test guards the workspace wiring and the uregen data contract at the boundary.

Validation

```
$ cd contracts && cargo test --package integration-tests test_fee_router_to_dynamic_supply_burn_flow
test result: ok. 1 passed; 0 failed

$ cd contracts && cargo test --workspace
(180 tests passed — +1 after #101 which added the M010/M011 test)
```

PR relationship

Based on #90 (contracts CI fix — where `fee-router` and `dynamic-supply` were added to workspace members). Sibling to #101 (M010 reputation-signal coexistence with M011 curation). The two integration tests together exercise two of the three conceptual flows in the Economic Reboot design. The third (M009 escrow → M015 rewards) is a future follow-up.

Refs `mechanisms/m013-value-based-fee-routing/SPEC.md` §5
Refs `mechanisms/m012-fixed-cap-dynamic-supply/SPEC.md` §5.3

[gemini-code-assist]

Code Review

This pull request integrates new contract modules—dynamic-supply, fee-router, and reputation-signal—into the workspace and adds a comprehensive integration test for the fee-to-burn flow. It also includes several idiomatic Rust refactorings, such as using is_none_or and range contains, and suppresses clippy warnings for functions with many arguments. A review comment suggests enhancing the integration test by including actual tokens in the CollectFee call to ensure the contract's fee validation logic is properly exercised.

[gemini-code-assist]

The CollectFee execution is called with an empty funds array (&[]). If the fee-router contract is intended to manage real token balances (as implied by the PoolBalances query and the PR description), this call should likely include the actual fee tokens. If the test passes without sending funds, it suggests that the fee-router contract might be missing a validation check to ensure that the tokens sent match the calculated fee, which could be a security concern in the contract itself.

Suggested change

	app.execute_contract(
	admin.clone(),
	fr_addr.clone(),
	&fee_router::msg::ExecuteMsg::CollectFee {
	tx_type: fee_router::msg::TxType::MarketplaceTrade,
	value: trade_value,
	},
	&[],
	)
	.unwrap();
	app.execute_contract(
	admin.clone(),
	fr_addr.clone(),
	&fee_router::msg::ExecuteMsg::CollectFee {
	tx_type: fee_router::msg::TxType::MarketplaceTrade,
	value: trade_value,
	},
	&[Coin::new(calc.fee_amount.u128(), DENOM)],
	)
	.unwrap();