caelum0x ac68067b17 fix(release): correct crates.io repository URL and gate internal crates from publish
The workspace repository metadata pointed at a 404 (lawsynth/lawsynth instead
of caelum0x/lawsynth). RELEASE.md documents 12 crates plus all services/apps
as explicitly internal for v0.1 (not part of the published surface), but only
lawsynth-integration actually carried `publish = false` — add the missing
flag to the other 16 internal crates/services/apps so a future `cargo
publish` run can't accidentally ship them.

Also fix the two cargo clippy -D warnings failures blocking CI on main since
the 2026-10-12 release-cut merge: lawsynth-information-diffusion's forecast()
needlessly indexes `totals` by a range-loop variable (needless_range_loop)
and exceeds clippy's argument-count lint (too_many_arguments, same pattern
already used elsewhere in the workspace for fixed simulation-contract
surfaces). Verified: cargo fmt --check, cargo clippy --workspace --all-targets
-- -D warnings, and cargo test --workspace (388 suites, 0 failures) all pass
clean; cargo build --locked --release -p lawsynth-cli succeeds.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-15 16:53:00 +03:00
..
2026-08-16 23:40:41 +03:00
2026-08-16 23:40:41 +03:00
2026-08-16 23:40:41 +03:00
2026-08-16 23:40:41 +03:00
2026-08-16 23:40:41 +03:00

LawSynth worker

lawsynth-worker is a synchronous, local execution boundary for typed LawSynth jobs. It accepts validated JobEnvelope values and executes the engine's real discovery pipeline or deterministic RK4 simulator. It is a library first; the executable only states the supported surface and deliberately does not open a listener.

Each accepted job reserves its declared CPU, memory, and disk budget through lawsynth-runner, then writes a durable lifecycle record to an ObjectStore before and after execution. The local LocalStore implementation makes those records survive a worker restart. Job results remain typed in memory rather than being silently converted to an incomplete queue codec.

The only supported transport is TransportSurface::LocalDirect. Queue, HTTP/RPC, plugins, uploads, OS sandboxing, and distributed leases are not linked and are reported as unavailable rather than represented by placeholders.

Run the focused verification with cargo test -p lawsynth-worker.