Lucifer Workspace

Three crates, wired together, growing v0.2 into the v2.6 architecture:

• lucifer_v02_simulation/ — the shared, dependency-light core extracted from v0.2: PhysicalClaim, PhysicsSimulator, TruthVerifier. Only depends on meval + serde.
• lucifer-ai/ — the v0.2 REPL prototype, now consuming the shared crate above instead of its own copies.
• lucifer_core/ — the v2.6 LuciferCore orchestrator, whose Triple-Lock Simulation stage is now backed by the same lucifer_v02_simulation crate (src/v02_triple_lock.rs), not a mock.

Build/test each independently (they're path-dependent siblings, not a Cargo workspace, so build from within each directory):

cd lucifer_v02_simulation && cargo test   # 17 tests
cd ../lucifer-ai && cargo test            # 30 tests
cd ../lucifer_core && cargo test          # 42 tests

On a modern Rust toolchain, lucifer-ai's reqwest/tokio dependencies should resolve without any special handling. This sandbox's older Rust 1.75 toolchain needed rustls-tls (instead of native OpenSSL) and a few transitive-dependency pins — see prior deliverables in this conversation for details; none of that should be necessary on a current toolchain.