dsh-lifeboat

LIMITATIONS

Known limitations

- The server binds only to `127.0.0.1`, rejects non-loopback Host headers, sends a restrictive CSP, and requires a random per-process token for writes. - Config mode does not mount plugin rows. Runtime mode does execute installed plugin code with the current operating-system user permissions and therefore requires an explicit acknowledgement. The temporary Home isolates configuration and runtime data; it is not an operating-system sandbox for plugin source code. - Probe processes receive a credential-scrubbed environment. A plugin that requires an API key may therefore fail for an environmental reason; the report preserves this distinction as far as the process result allows. - Runtime survival is a health heuristic, not proof of full application correctness. Prefer config mode for deterministic loader/configuration failures. - A boot success window must end at least 250 ms before the overall probe timeout. Invalid combinations are rejected instead of silently shortening the requested window. - Relative profile assets are copied up to 32 MiB. Links are skipped and reported, so a profile built around linked local sources may require `--keep-artifacts` and manual inspection. - On POSIX, probes run in their own process group and cleanup targets that complete group, including descendants that remain in it after the group leader exits. Windows uses `taskkill /T` while the owned probe process is alive. - Package-resolution fingerprints include captured real targets and package manifests; installed package source trees are linked rather than fully copied. In-place source edits that leave `package.json` unchanged are outside the immutable configuration snapshot and should be avoided during diagnosis. - The current candidate classifier follows the Harness profile contract: out-of-tree bundle names are active bundles also listed in `dependencies`. Installation-owned bundles are never automatically disabled. - The current release targets the `dsh.profile.bundles` format used by current pre-release Harness builds. It has not been validated against every historical release.