Align Minting Developers navigation and protocol reference

[QuickMythril]

Minting’s Developers workspace now uses ?view=developers, preserving tab=reference as a read alias and existing Minters/Blocks links. Recognized Developers views take precedence; Home parameters, repeated unknown keys and fragments survive navigation and Home Back/Forward.

The reference shares actual group, page, identity, avatar, payout and timeout constants with the implementation. Its executable Minters example covers both GET_GROUP_MEMBERS and checked FETCH_NODE_API envelopes with pagination. It also corrects capability detection, minting authorization and confirmation wording, and adds accessible copying and Home-safe section navigation. Candidate version: 1.4.4, Qortium only.

Validation:

• 63 tests, strict TypeScript/production build, and diff checks pass, including rendered contract, route aliases/precedence, clipboard fallback, and executing both pagination example paths.
• Real Home desktop and physical Android 13 compatibility APK: Developers links, section navigation, Home Back/Forward, and live Minters loading through Home’s real bridge.
• Classic/Modern/Fun × medium/huge text × light/dark; desktop 1280/390 widths and physical phone. No document overflow or Home outer-frame scrolling from section links.
• Candidate assets served through a read-only loopback test route with real Core data. Home test build is beta.1 plus merged compatibility fixes, including the group-member limit fix. No minting administration, group joins or QDN publication performed.
• No open Dependabot PRs when this work began. Bounded read-only Claude review findings were independently verified.

Published 2026-09-09 after owner approval: 1.4.4, Qortium APP/Minting/Minting, merged main 08ba8d0, confirmed at block 123602, fee 0. Merged-main build matches the tested candidate. Published Home desktop and physical Android read, navigation/history, display and clipboard acceptance passed using the existing compatibility test builds. No Qortal integration or publication.
All 7/7 files match on local Core and node2. Node1 (Regxa) remains DOWNLOADING at 1/2 chunks after a bounded readiness wait; this is tracked as a seed replication follow-up. No seed configuration or service restart was performed.