Skip to content

[rei] One program, two bots: Tracer beside ReiWimsy - #54

Draft
DraChimeraVee wants to merge 7 commits into
dravee/tracer/issue-linksfrom
dravee/rei/tracer-in-one
Draft

DraChimeraVee wants to merge 7 commits into
dravee/tracer/issue-linksfrom
dravee/rei/tracer-in-one

Conversation

@DraChimeraVee

@DraChimeraVee DraChimeraVee commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

One program, two bots: reiwimsy runs Tracer beside ReiWimsy when its env file has TRACER_TOKEN. Stacked on #53.

  • [rei] A Tracer report's number is no issue: "report #74", "Tracer #12": ReiWimsy linked ScarletNX's issue 12 for @Tracer delete #12, a command of Tracer's, and issue 74 for "Tracer report #74": the numbers the two bots would fight over. A number after report, reports or Tracer is Tracer's.
  • [rei] Each log line names its bot, whole, and each gateway is watched apart: the shared pieces for one process with two bots. rei_log names the bot its file is built for and keeps a line whole across threads, Discord's refusals name the bot that asked, and the gateway's watch follows each Concord client.
  • [tracer] A worker's environment holds no bot's settings or tokens: a worker lost the TRACER_ keys alone; beside ReiWimsy, REIWIMSY_TOKEN and GITHUB_TOKEN would have reached the code that reads strangers' files.
  • [rei] One program, two bots: reiwimsy runs Tracer beside ReiWimsy: two Concord clients in one process, each with its own token, gateway and name, Tracer's on a thread of its own; the first gateway that stops ends the program as before. ReiWimsy leaves a message that mentions Tracer to it. Each bot is a bot.c of its own; tracer alone stays (its main.c a few lines), and reiwimsy links libtracer.a.
  • [dist] reiwimsy's package runs Tracer, and the docs say how to move it there: the package holds the site's files and depends on sqlite3; the service gives Tracer its folders when the env file has TRACER_TOKEN; Install says how a Tracer running alone moves into discordbots.
  • [status] Tracer is up as ReiWimsy is, once its token is in ReiWimsy's env: the status page read the tracer jail's own service, off since Tracer moved into reiwimsy, and showed it down.

A new gateway test, both: the fake Discord knows two tokens and users, sends both bots <@200> delete #12 and see #12, and Tracer must answer the first and ReiWimsy the second, each with its own token, ReiWimsy never the first (it fails with the mention check taken out). The other nine gateway tests pass, and CI runs both too.

@DraChimeraVee
DraChimeraVee force-pushed the dravee/rei/tracer-in-one branch from 049658c to 0592278 Compare November 17, 2026 16:11
@DraChimeraVee
DraChimeraVee force-pushed the dravee/tracer/issue-links branch from 1af7eb0 to aad5819 Compare November 17, 2026 16:11
ReiWimsy linked ScarletNX's issue 74 for "Tracer report #74", and issue 12
for "@tracer delete #12", a command of Tracer's: the number Fuddles feared
the two bots would fight over. A number after report, reports or Tracer is
left to Tracer.

Signed-off-by: AO55 <AO55@reden-emu.dev>
… apart

The shared pieces for one program that runs both bots: rei_log names the
bot its file is built for (REI_NAME) and keeps a line whole whatever the
threads, Discord's refusals name the bot whose Dc asked, and the gateway's
watch follows each Concord client of the program, its line naming which.

Signed-off-by: AO55 <AO55@reden-emu.dev>
A worker lost the TRACER_ keys alone: in a program that runs ReiWimsy too,
REIWIMSY_TOKEN and GITHUB_TOKEN would reach the code that reads strangers'
files. It loses every TRACER_, REIWIMSY_ and GITHUB_ key, and any name that
holds TOKEN, KEY or SECRET.

Signed-off-by: AO55 <AO55@reden-emu.dev>
DraVee asked for ReiWimsy and Tracer in one program that answers as two
bots. With TRACER_TOKEN in its env file, reiwimsy runs Tracer in its own
process: two Concord clients, each with its own token, gateway and name on
Discord, Tracer's on a thread of its own, the first gateway that stops
ending the program as before. ReiWimsy leaves a message that mentions
Tracer to it. Each bot is a bot.c of its own (rb_, tb_); tracer alone
stays, its main.c a few lines, and reiwimsy links libtracer.a.

Signed-off-by: AO55 <AO55@reden-emu.dev>
…t there

The package holds the site's files under share/reiwimsy/tracer and depends
on sqlite3; its service makes Tracer's folders and gives it TRACER_DB,
TRACER_SITE and TRACER_ASSETS when the env file has TRACER_TOKEN. Install
says how a Tracer that runs alone in its jail moves into discordbots, and
the pages say what one process with two bots does.

Signed-off-by: AO55 <AO55@reden-emu.dev>
rei_log became a macro of rei.h, and Tracer's Makefile named rei.h for
rei_util.o alone: an object built before linked against a function that
is no more. Every object of Tracer's now follows rei.h.

Signed-off-by: AO55 <AO55@reden-emu.dev>
@DraChimeraVee
DraChimeraVee force-pushed the dravee/rei/tracer-in-one branch from 0592278 to aa13311 Compare November 17, 2026 16:11
… env

Tracer runs inside reiwimsy now; the tracer jail's own service stays off, so
the page showed it down.

Signed-off-by: AO55 <AO55@reden-emu.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants