maziyarpanahi/openmed

Problem and existing coverage js/openmedkit-tauri defines npm test (typecheck plus tests/desktop/test_tauri_client.ts) and a Rust crate (src-tauri/lib.rs, sidecar_command.rs), but no workflow runs either. React Native and Electron package checks run through pytest bridges (tests/mobile/test_rn_bridge_parity.py, tests/web/test_electron_ipc.py) and the web package through the Pages and publish workflows, while Tauri has no bridge and no cargo step exists anywhere in .github/workflows/. Regressions in the typed client or the Rust command can merge unnoticed. Related work: #823, #3712. Release scope: #3604. Implementation Add a pytest bridge mirroring the Electron one (skipping when node or npm are absent) and a path-filtered job running the package tests plus cargo check --locked and cargo test --locked for the sidecar crate. Pin toolchain versions and keep the job offline after dependency installation. Acceptance criteria Breaking the client contract or the Rust command fails CI. Th

Problem and existing coverage RedactionShareViewController hard-codes English user-facing strings (loading, status, "Redact and Return", "Cancel") and displays policy profiles by replacing underscores and capitalizing, so identifiers render as "Hipaa Safe Harbor". The package has no string catalog, the labels use preferred fonts without adjustsFontForContentSizeCategory, so text does not resize while the extension is open, and the policy picker has no accessibility label. OpenMed's documentation already ships Chinese and Hindi locales, but the native extension UI cannot be localized. Related work: #835, #651. Release scope: #3604. Implementation Move user-facing strings into a localized string catalog with English as the base and the existing documentation locales as initial translations. Provide display names for bundled policy profiles from the catalog, enable Dynamic Type adjustment and add accessibility labels and hints. Add tests that every key resolves and that display names cov

Problem and existing coverage The browser demos ship a strict Content-Security-Policy (same-origin scripts, workers and connections, 'wasm-unsafe-eval' for WebAssembly), but js/openmedkit-web/README.md and the runtime guides document only cross-origin isolation headers. Integrators therefore have no supported CSP for ONNX Runtime Web, WebGPU and worker-based inference, although a connect-src restriction is the browser's own enforcement of the no-upload invariant and a policy that is too strict silently breaks threaded WebAssembly. Related work: #799, #862, #3710, #3718. Release scope: #3604. Implementation Document a minimal CSP and cross-origin isolation profile for the package (scripts, workers, WebAssembly, model assets and connections) and the directives each runtime feature needs. Add a browser test page served with that profile that runs a synthetic inference and verifies that a cross-origin fetch from the page is refused while local inference still works. Acceptance criteria

Problem and existing coverage loadTokenClassificationPipeline writes runtime.env.allowRemoteModels and allowLocalModels on the shared Transformers.js module, awaits pipeline creation and restores a snapshot in finally. With two overlapping loads in a synthetic harness (a local path, then a Hub ID), the local-only load was created while the global flag was true, and after both finished the host environment was left at allowRemoteModels: false and allowLocalModels: true although the host had set neither. Applications that also use Transformers.js directly inherit the corrupted setting. Related work: #799, #3718. Release scope: #3604. Implementation Stop mutating shared runtime configuration per call: rely on per-call options, or serialize loads that must change the environment and restore exactly what was present, including absent keys. Add a concurrency test with controllable pipeline promises. Acceptance criteria Overlapping local and remote loads leave the runtime environment exac

Problem and existing coverage OpenMedKit's library and extension products ship no PrivacyInfo.xcprivacy; the only manifest is in the scan demo, and it declares no accessed API types although the demo reads and writes UserDefaults.standard (ScanFlowViewModel, ClinicalPresetsStore), a required-reason API category checked at App Store submission. A privacy-first SDK should declare no tracking and no collected data explicitly, and future use of required-reason APIs (user defaults, file timestamps, disk space, system boot time) in kit or demo sources should be caught before submission. Related work: #835, #955. Release scope: #3604. Implementation Add privacy manifests as processed resources of the OpenMedKit and extension targets in both package manifests, declaring no tracking, no collected data and any required-reason API usage. Correct the scan demo manifest's user-defaults declaration. Add an offline source scan mapping required-reason API symbols in Swift sources to declared categori