GameCult/VoidBot
Watch
9
0
Fork
You've already forked VoidBot
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record Nightwing swarm surface split

Browse source
This commit is contained in:
Meta Vens 2026-06-05 15:23:07 +01:00
commit faa68e4083
1 changed files with 1 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
state/evidence.jsonl
View file

@ -350,3 +350,4 @@
{"ts":"2026-06-04T22:36:57Z","type":"implementation","status":"ok","note":"Void moderation delivery now requires Bifrost instead of falling back to VoidBot-native Discord transport: run-void-moderator-rumination rejects VOID_DISCORD_TRANSPORT=direct, candidate speech and moderation-status DMs call bifrost-bridge only, and speech/status fixtures use fake Bifrost bridges."}
{"ts":"2026-06-05T13:52:45Z","type":"implementation","status":"ok","note":"Restored Odin visibility for voidbot.swarm: Odin/VoidBot CultMesh consumers now import cultmesh-ts and cultcache-ts package roots instead of private dist subpaths, normal swarm dashboard publication writes the CultMesh witness again, and CTB Eve text now shows due time plus anchored/unanchored mention markers (m1 vs m?1)."}
{"ts":"2026-06-05T14:16:31Z","type":"ops","status":"blocked","note":"Nightwing dashboard not visible because Nightwing host is unreachable from Starfire: Nightwing.Home resolves to 192.168.1.75, but ping, SSH 22, Eve dashboard 8795, and browser 8891 do not answer; a quick LAN TCP sweep only found Starfire 8795 and EVE/iPad SSH on 192.168.1.72."}
{"ts":"2026-06-05T14:23:01Z","type":"ops","status":"warn","note":"Nightwing reboot restored host reachability and visible-ops, but the Nightwing-local voidbot.swarm broker tab is not the live Odin/CultMesh swarm surface: ws://192.168.1.75:8795/eve/deck/voidbot.swarm renders 'VoidBot Swarm snapshot missing' from /srv/gamecult/eve-dashboard/state/voidbot-swarm-state.json, while Odin at 192.168.1.66:8797 exposes the live voidbot.swarm CultMesh lowering."}