6 Commits

Include renames

Author	SHA1	Message	Date
archipelagoandClaude Opus 5	24ce8b39e8	feat(security): require the node password to grant Trusted ... Promotion to Trusted is a privilege escalation — a Trusted peer can read node state, be deployed to, and is exempt from the `!= Untrusted` gates federation/DWN/messaging use. It must therefore cost a fresh proof that the person at the keyboard is the operator, not merely that a session cookie exists. Same reasoning as node.rotate-identity and TOTP setup, both of which already re-verify. Both entry points are covered: - `federation.invite` gates on the RESOLVED level, not on an explicit request for Trusted: "Link Your Nodes" sends no `trust_level` at all and falls through to the Trusted default. The invite is a bearer grant of Trusted to whoever redeems it, so minting it IS the escalation. Observer invites are untouched. - `federation.set-trust` gates only when the peer is not already Trusted, so the dropdown re-emitting its own value doesn't demand a password for a no-op. Demotion is deliberately NOT gated: making something less privileged must never be harder than leaving it alone, or the safe action becomes the inconvenient one. The backend is the sole authority on what counts as an escalation — it returns a `PASSWORD_REQUIRED:`-prefixed error and the UI prompts and retries only on that, so the rule lives in exactly one place and the frontend never pre-judges. TrustPasswordModal.vue (modelled on RotateDidModal.vue) serves both flows. NodeDetailModal's select snaps back to the node's real level on change, since a cancelled or failed promotion would otherwise leave the dropdown displaying a level the node never accepted. The operator path stamps TrustSource::Manual; set_trust_level grew an `Option<TrustSource>` so automatic adjustments (the discovery-handshake demotion safety net) pass None and leave the recorded provenance alone rather than laundering an uninvited-join peer into looking approved. Follow-up, deliberately out of scope: `federation.join` also reaches Trusted when redeeming someone else's Trusted invite, with no re-auth. Tests: 44/44 federation, 79/79 rpc-client, vue-tsc clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-03 13:07:21 -04:00
archipelago	1a3d726eac	frontend: polish app launch and release experience	2026-06-11 00:24:40 -04:00
DorianandClaude Opus 4.6	f25ee5a00b	test: fix all 10 failing frontend tests ... Updated appLauncher tests to match current session-based routing. Fixed settings test to use h2 instead of h1. Fixed RPC client test to expect 'Session expired' on 401. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-15 04:49:41 +00:00
DorianandClaude Opus 4.6	1697af725b	test: achieve 80%+ branch/function coverage on frontend logic (E2E-03) ... 515 tests across 38 files. Branch coverage 88%, function coverage 83% on testable logic (stores, composables, api, utils, services, router). New test files: websocket, useLoginSounds, useMobileBackButton, useControllerNav, routes. Extended: rpc-client (99.5%), container store (100%). Fixed: useNavSounds AudioContext mock, type errors across tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-11 17:18:37 +00:00
DorianandClaude Opus 4.6	55a12e9bec	fix: replace path-option-card with glass-card in Settings.vue ... Also fix TypeScript errors in test files. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-10 23:58:33 +00:00
DorianandClaude Opus 4.6	5b08aa515d	test: add RPC client unit tests with 13 test cases ... Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-10 23:35:26 +00:00