fix: align fee split to resolved 28/25/45/2 across spec docs

[ToknWrks]

Summary

Two spec documents still referenced the old unresolved Model A fee distribution (30/40/25/5). The WG has since resolved OQ-M013-1 with a compromise split documented in open-questions-resolution.md and economic-reboot-proposals.md.

This PR updates the remaining spec docs to match:

• docs/economics/token-economics-synthesis.md — updated fee distribution list, ASCII diagram, and agent infrastructure funding reference
• phase-2/2.6-economic-reboot-mechanisms.md — marked OQ-M013-1 as resolved, added resolved split table, kept Model A and B for historical context marked as superseded

Changes

File	Before	After
token-economics-synthesis.md	30/40/25/5	28/25/45/2
2.6-economic-reboot-mechanisms.md	Unresolved models	Resolved 28/25/45/2 + superseded models preserved

No functional changes

This is a documentation consistency fix only. No mechanism parameters are being proposed or changed.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the token economics documentation to reflect a resolved fee distribution model. Specifically, it adjusts the allocation percentages to 28% for the Burn Pool, 25% for the Validator Fund, 45% for the Community Pool, and 2% for Agent Infrastructure across token-economics-synthesis.md and economic-reboot-mechanisms.md. Feedback indicates that several related documents, including the fee routing specification and governance resolution files, need to be updated to maintain consistency and ensure a single source of truth for these parameters.

[gemini-code-assist]

While you've marked OQ-M013-1 as resolved here, several related documents are out of sync. To improve clarity and ensure consistent state definitions across the repository, please update the following:

• mechanisms/m013-value-based-fee-routing/SPEC.md: Update the v0 default fee split and resolve the open question.
• docs/governance/open-questions-resolution.md and docs/governance/economic-reboot-proposals.md: Update the status from NEEDS_GOVERNANCE to resolved.

Maintaining a single source of truth for these transitions prevents implementation ambiguity and aligns with the project's documentation standards.

References

1. To improve document clarity, co-locate all state definitions and transitions within the primary state machine documentation, including definitions for edge-case flows like escalations.