botspec.go RawHistoryFolder

1package agent
2
3import (
4	"github.com/bnema/zut/packages/agent/modes/bot"
5)
6
7// botSpec describes one bot protocol to the generic daemon CLI in
8// botcmd.go. Everything protocol-specific (setup flow, status text,
9// adapter construction, state files) hangs off this struct; the
10// subcommand plumbing (run/start/stop/logs) is shared.
11type botSpec struct {
12	name       string   // "telegram", "matrix" — used in messages
13	subcommand string   // "telegram-bot", "matrix-bot"
14	aliases    []string // {"tg"}, {"mx"}
15
16	pidPath func(zutHome string) string
17	logPath func(zutHome string) string
18
19	// configured reports whether setup has been completed (e.g. a
20	// token is present), with a hint error message when it hasn't.
21	configured func(zutHome string) (bool, error)
22
23	printHelp func()
24	setup     func(tail []string) error
25	status    func() error
26	reset     func() error
27
28	// newAdapter builds the protocol adapter for the standalone
29	// daemon. Credential refresh stays generic in botRun.
30	newAdapter func(zutHome string) (bot.BotAdapter, error)
31}
32
33// botSpecs is the registry the dispatcher walks. Matrix is appended
34// in matrixcmd.go's init.
35var botSpecs = []*botSpec{telegramSpec()}
36
37// specFor returns the spec matching subcommand or one of its aliases.
38func specFor(subcommand string) *botSpec {
39	for _, s := range botSpecs {
40		if s.subcommand == subcommand {
41			return s
42		}
43		for _, a := range s.aliases {
44			if a == subcommand {
45				return s
46			}
47		}
48	}
49	return nil
50}