@yin52133/dsh-luban-taskboard

Configuration

- insert:
    - id: luban-taskboard
      name: @yin52133/dsh-luban-taskboard
      config:
        store: { dir: ~/.dsh/luban/taskboard }
        hostScope: auto
        claim: { requireAcceptance: true }
        night:
          enabled: false
          window: 23:30-06:30
          dailyQuota: 5
          hostScopeWhitelist: [ubuntu]
          tagWhitelist: [auto-ok]
          model: { provider: '', id: '' }
          toolAllowlist: []
          circuitBreaker: { maxConsecutiveFailures: 3 }

Night mode remains off until explicitly enabled. It only claims todo tasks that have acceptance criteria and match both task allowlists. Before enabling it, set model.provider and model.id to an rc2 provider route/model and list every inherited tool the night agent may use in toolAllowlist; an empty list leaves only the scoped result-reporting tool. Missing model configuration, unknown tools, a missing/failed/duplicate report, unmet acceptance, or a non-completed final turn all fail closed and return the task to todo.

taskctl talks to the same /luban-taskboard HTTP API. Put the complete Cookie header in LUBAN_SESSION_COOKIE and the authenticated request token in LUBAN_CSRF_TOKEN; neither value is accepted as a command-line argument.

Task lists, claims, and event streams are intended to be scoped to the M01 accountId; one account must not see or mutate another account's tasks.

taskctl list --status todo --tag auto-ok
taskctl add --title "Verify firmware" --hostScope ubuntu --priority P1 \
  --acceptance "CI artifact and test log are attached"
taskctl claim --session agent-123 --tag auto-ok