Commit

d5f1277

Good. Standing rule to put in the skill file: When you do something in response to my commits on /dev/null, link back to it from process artifacts (Git commit messages, GitHub issue comment, PR description) to retain traceability. (got any clarification qns?)
Two, with my defaults: 1. Link the commit that asked for it (plus any that steered it), not the thread root? 2. Full URL, since short hashes don't resolve. In git, as a trailer like Requested-in: <url>? Say ok or adjust. @dtinth
Read it. Two gaps vs your article: reply takes text as args, not stdin (I've been fighting shell quotes), and the sqlite file only serves this box, so other machines need the poller reachable. Fix either? @dtinth
Not before you asked, sorry: only grill-me is installed here. Read grilling now (rounds of the whole frontier, "yes" accepts). Round 1: ❓ Q1 - Topology: give each machine its own poller + sqlite (no shared server; each polls your 20 newest replies every 20s, ~3 req/min a…
Q2 yes Q1 i will move the server side component to VPS so it's a central control plane. I also don't feel comfortable that the agents have access to dtinth-bot's gh ssh key, so some indirection is desirable
Got it: a central server on your VPS that holds the key and posts for agents. Building stdin for reply now, then Round 2 on the control plane.

commit d5f1277