# The dsh-base Windows platform layer: applied by the dsh launcher on win32
# hosts, between the bundle layers and the user layers. Windows cannot run
# the POSIX-only sandboxed stacks, so this layer swaps the shipped bash stack
# for the PowerShell stack AND drops the sandbox entirely: no OS runner
# exists on Windows (landlock/bwrap/seatbelt are POSIX-only), so any policy
# would be theater — the unconfined shell could bypass fs-only path rules
# with one command. Windows therefore degrades to danger-full-access:
# unconfined pwsh + unconfined fs (`dsh-fs-local`), no permission switcher
# (dsh-permission requires a confining executor), approval policy `never`.
# The launcher reads THIS file from the base bundle package (never through
# dsh.bundle.patch — that field names the one universal layer). A Windows
# host that prefers bash or confinement overrides these rows through its
# profile or home cordis.patch.yml.

- id: bash-sandbox
  disabled: true

- id: tool-bash
  disabled: true

- id: permission
  disabled: true

- id: ui-permission
  disabled: true

- id: sandbox
  disabled: true

- id: sandbox-policy
  disabled: true

- id: fs-sandbox
  disabled: true

- id: approval
  config:
    policy: never

- insert:
    - id: pwsh-local
      name: '@deepseek-ai/dsh-pwsh-local'

    - id: tool-pwsh
      name: '@deepseek-ai/dsh-tool-pwsh'

    - id: fs-local
      name: '@deepseek-ai/dsh-fs-local'