{
  "module": "screen-lock",
  "version": "1",
  "capabilities": [
    "package-manager"
  ],
  "requires": [
    "x11-display"
  ],
  "claims": [
    {
      "name": "node-lock-screen",
      "scope": "node",
      "serves": [
        "lock"
      ]
    }
  ],
  "tools": [
    "screen_lock_idle",
    "screen_lock_inhibit",
    "screen_lock_locked"
  ],
  "shell": [
    {
      "for": "xinitrc",
      "slot": "normal",
      "code": "# The lock screen (module screen-lock, novox/hq ADR 0208): the session locks after 30 minutes idle,\n# the displays go to standby and suspend then and off after an hour, and xss-lock runs the locker on\n# idle, before suspend and on logind's Lock. xss-lock needs this login session, so it starts here and\n# not as a unit. It is started again if it exits, for as long as this session lasts ($$ is the\n# session's own process, which becomes the window manager).\nxset s 1800 1800\nxset dpms 1800 1800 3600\n(while kill -0 $$ 2>/dev/null; do xss-lock --transfer-sleep-lock -- \"$HOME/.local/bin/screen-lock\"; sleep 2; done) &\n"
    }
  ],
  "resources": [
    {
      "id": "colour-locker",
      "type": "package",
      "package": "i3lock-color",
      "absent": true
    },
    {
      "id": "screensaver",
      "type": "package",
      "package": "xscreensaver",
      "absent": true
    },
    {
      "id": "watcher",
      "type": "package",
      "package": "xss-lock"
    },
    {
      "id": "locker",
      "type": "package",
      "package": "i3lock"
    },
    {
      "id": "wrapper",
      "type": "file",
      "path": "${machine:account-home}/.local/bin/screen-lock",
      "owner": "${machine:account}",
      "mode": "0755",
      "content": "#!/usr/bin/env bash\n# screen-lock (module screen-lock, novox/hq ADR 0208): the locker. xss-lock runs it on idle, before\n# suspend and on logind's Lock, and node-lock-screen's `lock` ends in it.\n#\n# The distribution's i3lock: a black screen, failed attempts shown, an empty Enter ignored. The colour\n# build the predecessor used is not in the distribution; it can come back as a pinned archive\n# (ADR 0205), and then only these options change.\n#\n# Before a suspend, xss-lock hands this script a lock on the sleep (XSS_SLEEP_LOCK_FD) and suspends\n# once it is released. The locker must not inherit it, or the machine would wait for the unlock\n# before sleeping; it is released once i3lock is up, so the machine never sleeps unlocked. This is\n# xss-lock's own documented pattern for i3lock.\nset -u\n\noptions=(--color=000000 --show-failed-attempts --ignore-empty-password)\n\n# One locker: a second press of the key, or a lock while locked, changes nothing.\nif pgrep -xu \"$EUID\" i3lock >/dev/null; then\n\texit 0\nfi\n\nif [[ -e /dev/fd/${XSS_SLEEP_LOCK_FD:--1} ]]; then\n\tkill_i3lock() { pkill -xu \"$EUID\" \"$@\" i3lock; }\n\ttrap kill_i3lock TERM INT\n\ti3lock \"${options[@]}\" {XSS_SLEEP_LOCK_FD}<&-\n\texec {XSS_SLEEP_LOCK_FD}<&-\n\twhile kill_i3lock -0; do\n\t\tsleep 0.5\n\tdone\nelse\n\ttrap 'kill %%' TERM INT\n\ti3lock --nofork \"${options[@]}\" &\n\twait\nfi\n"
    }
  ],
  "build": {
    "artifacts": [
      {
        "name": "tools",
        "kind": "bundle",
        "language": "go",
        "system": "arch",
        "from": "cmd/screen-lock-tools",
        "binary": "screen-lock-tools",
        "loads": [
          "screen-lock-tools"
        ]
      }
    ]
  }
}