SDK LxcNetworkConfig types a mode-only network config as unrestricted when the backend applies default-DROP

[dhoehna]

sdk/node/src/state-aware-types.ts types a config carrying only enforcementMode as unrestricted, but the backend defaults to block and installs a default-DROP chain.

[github-actions]

Triage complete.

Labels applied: OS-Linux, Area-SDK-Api, Area-Executor-LXC

Owners assigned: @SohamDas2021 (LXC/Linux backend) and @huzaifa-d (SDK API / executor schema)

The issue describes a type-safety mismatch in the exported LxcNetworkConfig SDK type — the unrestricted arm admits a bare enforcementMode, but the Rust backend defaults to Block/DROP when only a mode is supplied, making the behavior maximally restrictive rather than unrestricted. This is a breaking SDK contract change spanning both the TypeScript SDK API layer and the LXC executor.

Maintainers: Comment /investigate to check whether this issue or bug is valid against the most current code. Copilot will also produce a report with the changes that will be needed. For a small, unambiguous documentation or test fix, it may also create one draft PR.

Generated by 🏷️ Issue Triage for #893 · sonnet46 · 19 AIC · ⌖ 5.46 AIC · ⊞ 7.4K · ◷

[dhoehna]

Consolidated into #901 -- [SDK] Type and schema surfaces disagree with what the engine accepts and enforces.

The backlog now carries one issue per area instead of one per finding. This report is reproduced there in full and unedited; nothing here is dropped. Track and fix it at #901.