Exercise federated directories and browser-local signing

[jt55401]

Summary

• replace the single trust directory with isolated alpha and beta stores plus weighted browser subscriptions
• exercise conflicting opinions, malformed responses, and planned directory outages
• publish and verify a real WordPress browser-local signature through Web Crypto, IndexedDB, and the public key resolver
• test the production DOM walker in Chromium, Firefox, and WebKit
• load the built MV3 extension in Chromium and verify its service-worker result
• validate trust indicators against the effective weighted directory score
• raise rate limits only inside the synthetic E2E environment so 1,000 consumers can share one Playwright container address
• pin every sibling revision and Docker image used by the frozen run

Validation

• npm test: 43 Vitest tests
• npm run build: TypeScript build, including test scripts
• docker compose config --quiet
• npm run test:browser: Chromium, Firefox, and WebKit lifecycle checks
• exact-pin ./scripts/run-e2e.sh scenario.yaml from a clean Docker state
• 74 of 74 publications served with signed sections
• live Chromium extension check: one cryptographically valid, source-verified section
• real WordPress browser-local signing through the public key endpoint
• 1,050 sessions and 5,804 page visits
• 5,804 successful verifications and zero signature failures
• 11,608 directory queries, including 42 planned availability failures
• 1,169 visits with conflicting directory contributions
• all three malicious author profiles detected, with zero false positives

Frozen sibling hashes are listed in the README and enforced by the runner.