Add Node Developers reference and Home workspace support

[QuickMythril]

Node had no in-app developer contract for its Core inspection and settings workflows. This adds a public English Developers tab in Node 1.4.5, covering bridge capabilities, status/peer reads, writable metadata, units and validation, approval, saving and restart effects. Node remains Qortium-only.

The canonical ?view=developers route accepts developer/reference aliases, retains settings context and host/query/fragment parameters, and supports Home Back/Forward without losing unsaved drafts. Copy controls announce results; the reference supports Home appearance and stays usable without admin authority or a working Core. The existing settings allowlist and write/restart permissions are unchanged.

Validation:

• Dependabot deps: bump @vitest/mocker and vitest #23 merged first; its 39 tests and build passed.
• All GitHub CI/CodeQL checks pass at 5959eb178542173a7593ab766592f7fbdc20fb16.
• 57 tests and TypeScript/Vite production build pass, including real React workspace/history/draft regressions and executable reference examples.
• Home 2.1 beta desktop and physical Android: 24 desktop + 12 phone appearance cases, section navigation, history, RTL shell with English reference, clipboard, and final-bundle loading pass. Standalone read-only/offline reference passes.
• Physical Android using Home's protected custom-node credential and real approval dialogs: save denial retains the draft; approved apiDocumentationEnabled change and restoration pass; restart denied. The acceptance proxy blocks actual restart and all mutations except this one boolean setting. No Core restart occurred; temporary credential/connection removed.
• Desktop live admin writes were unavailable because the isolated profile correctly refused key storage without OS protected storage. Desktop read-only checks passed; real writes were verified on Android, with component/adapter tests covering the shared app behavior.
• Independent review found one inaccurate metadata-shape claim; corrected to the supported map/JAXB forms and covered by a regression test.

The live test clarified an existing Core distinction documented here: saving reloads the settings object, while restart-dependent services may still use earlier values. Core retains pendingRestart after restoring the original setting, even when the file and loaded object match. The original apiDocumentationEnabled=true is restored; the marker remains and no restart was performed. Core/Node presentation semantics are recorded as a separate follow-up.

Ready for review; this feature has not been merged or published to QDN.