Skip to content

refactor(session): set reply gates through Wolfram - #59

Merged
ewanc26 merged 2 commits into
mainfrom
refactor/use-wolfram-reply-gate
Oct 7, 2026
Merged

ewanc26 merged 2 commits into
mainfrom
refactor/use-wolfram-reply-gate

Conversation

@ewanc26

@ewanc26 ewanc26 commented Oct 7, 2026

Copy link
Copy Markdown
Owner

What this changes

Replaces Indigo's hand-built threadgate rules in do_publish with Wolfram v0.34.0's wf_agent_set_reply_gate (pinned in the first commit). A failure is still only logged and the post stays public; an out-of-range gate is now refused by Wolfram rather than by a local check. Cobalt did the same in cobalt#191. Part of indigo#53.

Verification

Host: make test (4002 checks, 0 failures) and the 3DS build (devkitARM, against a Wolfram v0.34.0 build) links. The gate call is tested in Wolfram against a mock PDS; the host tests here do not reach do_publish, and nothing ran on Azahar or a 3DS.

Docs

AGENTS.md and CHANGELOG updated.

Checklist

  • CI is green (CI gate and flow / conventions)
  • No secrets, tokens or signing keys in the diff
  • Tests added or changed with the behaviour; none skipped, disabled or deleted

🤖 Generated with Claude Code

ewanc26 and others added 2 commits October 7, 2026 08:35
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Delete the threadgate rules from session.c.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@ewanc26
ewanc26 merged commit f816255 into main Oct 7, 2026
9 checks passed
@ewanc26
ewanc26 deleted the refactor/use-wolfram-reply-gate branch October 7, 2026 07:40
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.

1 participant