octoturge
99c1d038f9
The rest of proto/bambulab/ was pure boilerplate/comments with nothing concrete to copy from. This one message (sequence_id + command, matching Bambu's real get_version request) is wired all the way through: real proto, real generated Rust struct, lib.rs actually include!'d instead of commented out. continuum-proxy's bambu_protocol_demo example serializes it and diffs the output against Bambu's actual wire JSON byte for byte. Verified with cargo build (this crate) and cargo run --example bambu_protocol_demo (continuum-proxy) - output matches exactly.
continuum-schemas
Single source of truth for the Continuum data model. Protobuf definitions in
proto/ are compiled into two consumer packages:
packages/ts-types— TypeScript types generated viats-proto, plus hand-written TypeBox schemas undersrc/schemas/used for runtime validation incontinuum-backend's ElysiaJS routes.packages/rust-types— a Rust crate (continuum-rust-types) that compiles the same.protofiles withprost-build(viabuild.rs), producingserde-derived structs forcontinuum-proxyandcontinuum-ai-worker.
Layout
proto/continuum/v1/ canonical .proto message definitions
packages/ts-types/ TypeBox schemas + generated TS proto types
packages/rust-types/ prost-generated Rust structs (build.rs codegen)
Build
Requires protoc on PATH and npm install run at the repo root first.
npm install
npm run build:ts # protoc + ts-proto -> packages/ts-types/src/generated
npm run build:rust # cargo build, runs build.rs -> prost-generated structs
npm run build # both
Generated TS output under packages/ts-types/src/generated is build-derived
and gitignored. The Rust crate's generated code lands in OUT_DIR per
standard prost-build conventions and is never committed.