AtlatestRepositoryminder
1
;;; Minder - Scheduled task channel server for Claude Code2
;;;3
;;; MCP channel server that manages cron-based scheduled tasks4
;;; and pushes events into a running Claude Code session.6
(package7
name: "minder"8
version: "0.3.0"9
sigil: "0.23"10
description: "Scheduled task channel server for Claude Code sessions"11
url: "https://codeberg.org/sigil/minder"12
license: "BSD-3-Clause"13
authors: (list "David Wilson <david@daviwil.com>")15
entry: '(minder main)16
bundle-name: "minder"18
configs: (list19
(config20
name: 'dev21
output-dir: "build/dev"22
debug?: #t23
optimize: 024
bundle?: #t)25
(config26
name: 'release27
output-dir: "build/release"28
backend: 'native29
;; Keep release binaries usable on CPUs without AVX/AVX-512.30
c-compiler: "gcc"31
c-flags: '("-std=c11" "-D_GNU_SOURCE" "-O2"32
"-ffunction-sections" "-fdata-sections"33
"-march=x86-64" "-mtune=generic")34
debug?: #f35
optimize: 236
bundle?: #t))38
dependencies: (list39
;; Explicit sigil-lib pin. Two independent reasons, both measured:40
;; 1. Without it, sigil-lib is derived transitively and does not track41
;; the `sigil:` field, so a relock can silently leave the C runtime42
;; behind while `sigil deps install` exits 0.43
;; 2. sigil-lib's resolution does NOT respect its declared range: with44
;; no explicit pin, a fresh resolve records `ref: "^0.17"` alongside45
;; `version: "0.18.2"` in the same lock entry, on any toolchain,46
;; while sigil-stdlib in that same resolve correctly stays at 0.17.20.47
;; Verify in sigil.lock (the `version:`/`sha:` fields, not `ref:`).48
(from-git url: "codeberg:sigil/sigil"49
package: "sigil-lib" version: ">=0.23")50
(from-git url: "codeberg:sigil/sigil" package: "sigil-run" version: ">=0.23")51
(from-git url: "codeberg:sigil/sigil-json" version: "^0.16.2")52
(from-git url: "codeberg:sigil/sigil-log" version: "^0.17.0")53
;; sigil-mcp 0.18.2+ keeps channel servers on the legacy handshake:54
;; Claude Code rejects claude/channel on a 2026-07-28 connection.55
;; sigil-mcp ^0.18.1 (first release correct on MCP protocol 2026-07-28 over56
;; stdio), never ^0.16. The 0.16 line contains BOTH a release57
;; requiring the 0.18 runtime (v0.16.5) and one requiring 0.17 (v0.16.6, a58
;; deliberate compatibility revert), so ^0.16 no longer determines which59
;; runtime you need. The 0.17 line is the unambiguous 0.18-runtime line.60
(from-git url: "codeberg:sigil/sigil-mcp" version: "^0.18.4")61
(from-git url: "codeberg:sigil/sigil-yaml" version: "^0.9.2")62
(from-git url: "codeberg:sigil/sigil-later" version: "^0.3.0"))64
;; sigil-mcp 0.18 depends on sigil-http, which brings native TLS code into65
;; the graph, and `sigil test` requires an explicit harness for any package66
;; with native code. Test-only; does not reach the binary.67
dev-dependencies: (list68
(from-git url: "codeberg:sigil/sigil"69
package: "sigil-test" version: ">=0.23")70
(from-git url: "codeberg:sigil/sigil"71
package: "sigil-test-runner" version: ">=0.23")72
;; Registry packages do not resolve the runner's workspace-only deps.73
(from-git url: "codeberg:sigil/sigil" package: "sigil-package" version: ">=0.23")74
(from-git url: "codeberg:sigil/sigil" package: "sigil-build" version: ">=0.23")75
(from-git url: "codeberg:sigil/sigil" package: "sigil-deps" version: ">=0.23")76
(from-git url: "codeberg:sigil/sigil" package: "sigil-store" version: ">=0.23")77
(from-git url: "codeberg:sigil/sigil-git" version: "^0.16.1"))79
tasks: (list80
(task81
name: 'build82
description: "Compile minder modules"83
steps: (list84
(compile-sigil-modules sources: "src/**/*.sgl"85
output-dir: (config-output-subdir "lib"))))))