gald3r v5.0.0-beta.46
·
7 commits
to main
since this release
Download
This repo carries the release notes. The installers live on the engine repo:
Download gald3r v5.0.0-beta.46 — all files
| OS | gald3r engine |
|---|---|
| Windows | installer (.msi) · portable (.zip) |
| macOS (Apple Silicon) | gald3r-macos-arm64.pkg |
| macOS (Intel) | gald3r-macos-x86_64.pkg |
| Linux | gald3r-linux-x86_64.tar.gz |
Verify your download against SHA256SUMS.txt.
Your project's agent can now address another project's agent on the event
wire — delivery still waits on a server catalog deploy.
Ask another project
- Same-machine asks still write the local mailbox, as before.
gald3r project-agent ask --to-project <id> …queues a remote question and
flushes the outbox immediately.- The resident Valkyrie inbox loop now drains that same outbox on every tick,
so answers are not stranded on disk. - You need a signed-in session. Team coordination (or the Redis coordination
add-on) is required; solo and harvest keys are refused. - Production
api.gald3r.aidoes not yet list the new event types in its
catalog (checked against the live OpenAPI enum). Source has them; the
running API does not. Until that deploy, a remote publish will be rejected.
Board collisions, not folder sync
- Incoming field-level collisions are kept as a visible conflict log.
Nothing last-write-wins. Status reports a pending-conflict count. - This is not instant sync of
.gald3r/folders, task files, or the local
database. Server board writers stay gated. - Do not treat this cut as a multi-user coordination product. The
verification ladder is still the wedge.
Left out on purpose
- No
task claimalias, Longship chat-join, entitlement-flag seed, or
error-intake work in this binary. - No Postgres ingest for mailbox or conflict rows.